haskellPackages.foundation: remove outdated patch

Description of changes
The PR that this patch came from was not accepted. The code has since diverged, so the patch now fails to apply.
See discussion here: https://github.com/haskell-foundation/foundation/pull/572
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.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

[ ] Fits CONTRIBUTING.md.

Neat, thanks.


feat(#146): finish with assertions

Finish implementation of Assertions checking.
Closes: #146

PR-Codex overview
This PR adds two new rules for enforcing assertions in tests, with a focus on meaningful assertion messages.
Detailed summary

Adds RuleAssertionMessage to enforce meaningful assertion messages
Adds no-assertions.md and empty-assertion-message.md to document the new rules

✨ Ask PR-Codex anything about this PR by commenting with /codex {your question}

@rultor merge

@rultor merge

@volodya-lombrozo OK, I'll try to merge now. You can check the progress of the merge here

@rultor release, tag is 0.1.15, title is 0.1.15

@rultor release, tag is 0.1.15, title is 0.1.15

@volodya-lombrozo OK, I will release it now. Please check the progress here

@rultor release, tag is 0.1.15, title is 0.1.15

@volodya-lombrozo Done! FYI, the full log is here (took me 3min)


GitHub Pipeline TestVerifySECP256K1 test failed without known cause

Unknown what the root cause was, copying a comment from here

Something very strange is going on. Tests are failing on this branch; the TestVerifySECP256K1 test is failing with an error failed to parse public key: malformed public key: invalid length: 64. I tried re-running the workflow, but it failed again. Tests from the prior commit are passing, but all that was changed in the most recent commit was a README. Tests are passing locally. I branched off of this branch and reran the tests in the GitHub Pipeline and the tests passed.
I suspect we have some weird cryptographic issue going on where something to do with this particular commit, and the random generation made available in our GitHub Pipelines.

...aaaaand the mystery continues, because the tests on the merge into main commit pass without issue


Check that feature gates are correct

In some places, code was falsely feature gated through a directive like #[feature(...)]. Correct usage would be #[cfg(feature = "...")] and we should make sure (by calling rg or similar) that no instances of the incorrect usage remain.

Yes, they are correct :).


JavaFileManager is not closed after usage

JavaFileManager is not closed by org.gradle.api.internal.tasks.compile.JdkJavaCompiler after compilation is done. This seems to be an issue with JDK8, I am not sure if JDK9+ has the same problem.
Typically, not closing the JavaFileManager has no consequences, because javac will close all jars from the classpath it opens. However, if an empty jar is in the classpath, it will use ZipFile to load the entries, and it will not close the file after usage.
To verify the issue, run the following on Windows (this is roughly what JdkJavaCompiler is doing):
import java.io.IOException;
import java.nio.file.Files;
import java.nio.file.Path;
import java.util.ArrayList;
import java.util.List;
import java.util.jar.JarOutputStream;
import javax.tools.JavaCompiler;
import javax.tools.JavaFileObject;
import javax.tools.StandardJavaFileManager;
import javax.tools.ToolProvider;

public class Main {
  public static void main(String[] args) throws IOException {
    Path dir = Files.createTempDirectory("repro");
    Path emptyLib = dir.resolve("lib.jar");
    try (JarOutputStream jos = new JarOutputStream(Files.newOutputStream(emptyLib))) { }

    List<String> options = new ArrayList<>();
    options.add("-cp");
    options.add(emptyLib.toString());

    Path src = Files.write(dir.resolve("Main.java"), "public class Main {}".getBytes());
    JavaCompiler compiler = ToolProvider.getSystemJavaCompiler();
    StandardJavaFileManager fc = compiler.getStandardFileManager(null, null, null);
    Iterable<? extends JavaFileObject> fileObjects = fc.getJavaFileObjects(src.toFile());

    compiler.getTask(null, fc, null, options, null, fileObjects).call();
    Files.delete(emptyLib);
  }
}

This is already fixed on master. Btw java will keep all jars open by default, I also had to add a hack to clear out the zip file index cache.

See https://github.com/gradle/gradle/blob/master/subprojects/language-java/src/main/java/org/gradle/api/internal/tasks/compile/ResourceCleaningCompilationTask.java

Looks great, thanks!


Add Show Output Channel command for VSCode extension

Motivation
Closes https://github.com/Shopify/ruby-lsp/issues/2958
Implementation

Added a new command to package.json for showOutput
Utilized the existing client in the workspace to open up the output channel

Automated Tests
No automated tests - I did not see any instances of automated testing for similar commands (collectRubyLspInfo for example). I'd be happy to add some but I didn't really see a pattern for something as straight forward as this.
Manual Tests

Open VS Code -> Run and Debug -> Run Extension
Ensure existing Ruby LSP is disabled in new VS Code window
Open the command palette and search for Ruby LSP: Show Output Channel

https://github.com/user-attachments/assets/e777b1ac-684e-47cc-874b-cad8e5049ae4

I have signed the CLA!


Thank you for this plugin!

I can finally ditch classic release pipelines (along with the awful Azure Pipelines for Jira app)!


Add prescient-aggressive-file-save

Hi!
I have checked the discussion on prescient--save (https://github.com/raxod502/prescient.el/issues/17), and I agree to the idea on the additional implementation for the functionality to save the cache data more frequently because some users will not kill Emacs frequently if they use emacsclient.
So I suggest to add a new flag to control the frequency so that the cache can be saved when any commands are executed.
In my PR, since the value of prescient-aggressive-file-save is nil so nothing will be happened, but if user specifies t to the flag, then prescient-save will be called after executing prescient-remember.
I'd be glad if you check the proposed code. Thanks.
Best,
Takaaki

That looks fine to me. Add a changelog entry and I will be happy to merge it.
That being said, I personally think it would make more sense to instead use an idle timer or something similar (e.g. save after five seconds of inactivity, or save every 24 hours), to reduce command execution latency. What do you think?

Thanks, I'll change ChangeLog later.
For implementing an idle timer for saving the cache data, I personally don't like it because adding a timer is normally making the system more complex and, in this case, user cannot call prescient-remember sequentially because the user will select an item on the list in the minibuffer and we have sufficient waiting time for the next user selection in the minibuffer.
Do you have any further concerns on the frequency for calling prescient-remember?

user cannot call prescient-remember sequentially because the user will select an item on the list in the minibuffer and we have sufficient waiting time for the next user selection in the minibuffer.

I am afraid I just can't figure out what you mean by this. Could you clarify?

For example,

a user calls M-x counsel-find-library and selects a library in minibuffer.
right after the action, prescient-remember will be called and also the cache will be saved.
a user can call M-x counsel-find-library again and selects a library.
the cache will be saved again.

In this case, between 2. and 4. I believe Emacs can safely update the cache and dump it to prescient-save-file. No conflict will be happened because a user cannot repeat 1. and 3. in a short amount of time. So I think no need to take care of the command execution latency.

By command execution latency, I mean that it takes longer to execute a command before control is returned to the user, because we are performing disk IO after every command. In general, putting anything that takes any amount of time on post-command-hook (or similar) will make the editor less responsive.

Yes. That's the issue exactly I concerned. But at least for using ivy-prescient.el, I have not faced such situation so far. Loosing operability could be occurred when using company-prescient.el or in a combination of other packages. Unfortunately, I'm not a dedicated user of company-mode so I have not tested company-prescient.el well.
Introducing the prescient-aggressive-file-save option intends to provide an aggressive data storing capability for user like aggressive-indent-mode.el. Because the design concept is different, the functionally of a scheduled cache saving and/or auto saving with a timer should be implemented as another user option. I believe I can provide such capabilities by adding new functions if you want.

Fair enough.

Thanks for your contribution! I appreciate the help.

Thanks! I love this package :)


Dev

Changes implemented since version 0.0.3

Support provided for file paths with spaces.
run_conversion.py replaces batchconvert_cli.sh and construct_cli.py, uniting them.
Support for single file import from s3 (parse_s3_filenames.py modified).
Support for globbing filenames from s3 for one-to-one conversion (parse_s3_filenames.py modified).

v0.0.4


Normalization layer masking

System information.
TensorFlow version (you are using): tf-nightly (on CoLab), locally 2.7.0 (built locally with ROCm support, a few weeks behind)
Are you willing to contribute it (Yes/No) : Yes, after maintainers evaluate proposal
Describe the feature and the current behavior/state.
tf.keras.layers.Normalization() does not ignore masked values.
Will this change the current api? How?
Only additional parameters, should not contain any non-backwards compatible changes.
Who will benefit with this feature?
People working with ragged data who want to include a preprocessing layer to normalize in model.
Colab gist testing current behavior

Do you want to contribute a PR? (yes/no): yes
Briefly describe your candidate solution(if contributing):

add parameter to .adapt() method (mask_value=0.0 and/or boolean mask)
add call(..., mask=None) and tensor multiply to allow masking during model fitting/evaluation

An attempt at masked normalization (does NOT generalize to any input shape)
class MaskedNormalization(tf.keras.layers.Layer):
    """custom masked normalization layer"""

    def __init__(
        self,
        mask_value: int = 999,
        input_dims: tuple = (51, 3),
        name: str = "masked_normalizer",
    ):
        super(MaskedNormalization, self).__init__()

        self.mask_value = mask_value
        self.supports_masking = True

        self.normalization = tf.keras.layers.experimental.preprocessing.Normalization(axis=2)

    def adapt(self, inputs):
        """redefined adapt to ignore masked values"""
        if not self.normalization.built:
            raise RuntimeError("layer must be \"built\" prior to calling `.adapt()`, see `model.build_graph()`")

        mask = inputs != self.mask_value

        float_mask = tf.cast(mask, dtype=tf.dtypes.float32)

        mean = tf.reduce_sum(inputs * float_mask, axis=[0, 1]) / tf.reduce_sum(
            float_mask, axis=[0, 1]
        )
        # sample variance (divide by: n-1)
        var = tf.reduce_sum(((inputs - mean) ** 2) * float_mask, axis=[0, 1]) / (
            tf.reduce_sum(float_mask, axis=[0, 1])
            - tf.constant(1, dtype=tf.dtypes.float32, shape=(3,))
        )
        count = tf.experimental.numpy.count_nonzero(
            float_mask
        )

        self.normalization.adapt_mean.assign(mean)
        self.normalization.adapt_variance.assign(var)
        self.normalization.count.assign(count)

        self.normalization.finalize_state()
        self.normalization._is_adapted = True

    def call(self, inputs, mask=None):

        # if mask provided mask output values (multiply by zero)
        if mask is not None:
                reshape_mask = tf.transpose(
                    tf.expand_dims(tf.cast(mask, dtype=tf.dtypes.float32), axis=0),
                    perm=[1, 2, 0],
                )
            return self.normalization(inputs) * reshape_mask

        return self.normalization(inputs)

    def compute_mask(self, inputs, mask=None):
        """return the input_mask directly"""
        return mask

Hey there!  We are interested in this feature, please go ahead and prepare a pull request if you are willing!

I would like to work on this

Go for it! This fell on my back burner

Related if you're here looking for a workaround: created this version that plays nicely with tf.data.Dataset: https://gist.github.com/kydonian/ddda453c8707cabb1eb9fbcbbd335ffa

Hello, Thank you for reporting an issue.
We're currently in the process of migrating the new Keras 3 code base from keras-team/keras-core to keras-team/keras.
Consequently, This issue may not be relevant to the Keras 3 code base . After the migration is successfully completed, feel free to reopen this Issue at keras-team/keras if you believe it remains relevant to the Keras 3 code base. If instead this Issue is a bug or security issue in legacy tf.keras, you can instead report a new issue at keras-team/tf-keras, which hosts the TensorFlow-only, legacy version of Keras.
To know more about Keras 3, please read https://keras.io/keras_core/announcement/


Update useConfig to return a function instead of the promise

Trello card: https://trello.com/c/UfqGqE5w/507-fix-cold-start-of-ssr-functions
Fix an issue with server side rendering (with cloud function) because of an unterminated promise.
This is because of the config promise that does not has time to be resolved before the function finishes.
Instead of now returning directly the promise to the config, the useConfig returns a function returning a payload containing the data.
This is a breaking change and requires all the calls of useConfig to be updated as follow
Before
const config = useConfig()
...
(await config).xxx

After
const { data: config } = useConfig()
...
config?.xxx

fixed all the comments, also added a loading state as I realized that could be needed for a loader during the fetch to avoid having flickering effect


Improving the contact page

Hii @khushi-joshi-05
The contact page is looking very simple I want to make it more attractive by adding some color and hover
Can you please assign this task to me under gssoc24

@khushi-joshi-05  can i get assigned to this task  under gssoc .

@Manishar55 I have assigned you this issue. Can u make this page similar to other pages in design and also the footer isn't aligned properly.
Do your best!

@Manishar55 I have assigned you this issue. Can u make this page similar to other pages in design and also the footer isn't aligned properly. Do your best!

Thank you for assigning i will do my best to solve it  can you please add level 2 in this issue

issue

UI of Contact Us page does not matches with the website theme and also improving the contact page

Solution

If the Contact Us page header is the same as the home or menu page and a transition is applied to the form box on the Contact Us page and the send button is edited slightly, the theme could match. and looking more attractive.
Are you contributing under any open-source program ?

Yes, GSSOC'24.
@khushi-joshi-05 please assign me this issue , resolving it would increase attractiveness and look good.

hey @khushi-joshi-05 ,
My name is Harshwardhan Singh Panwar and I'm a contributor at GSSOC'24 .
idea:- By incorporating div CSS and animations, I can design the contact page in an interactive manner, making it visually appealing.
Please assign this task to me, GSSOC'24 .

Please assign this task to me, GSSOC'24 .
I am Priya Kumari and I am a Contributor at GSSOC'24


Enforce valid modulus for Residue and associated macros

This PR follows in the footsteps of #240 and enforces a valid (odd) modulus for compile-time constructions.
It updates impl_modulus! to panic on an invalid modulus.
For Residue, it adds a panic to new and deprecates it, and adds a new_checked constructor that returns a CtOption based on the modulus validity. This is added since it's possible to define a modulus without impl_modulus! and use Residue directly.
It also updates const_residue! to use Residue::new_checked and unwrap, so it will also panic on an invalid modulus.

@fjarri: Would appreciate a review if you're available.

@fjarri: I'll wait to address your review comments until we decide on a common deprecation strategy, as suggested by @tarcieri in #240.

Ok, I guess I'll go ahead and merge this, although I'd really, really like to find a way to get rid of new_checked

Ok, I guess I'll go ahead and merge this, although I'd really, really like to find a way to get rid of new_checked

Agreed. Being able to rely solely on compile-time checks would be much more elegant and in line with the intent of the design, for sure.


musescore: set meta.platforms, fix typo

Description of changes
It's a bit confusing to have to build it yourself without Hydra cache, only to find that the main program doesn't exist because of a typo.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] 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

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

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

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Setting meta.platforms is required for the package to be built on Hydra on platforms other than x86_64-linux. This also helps to avoid misleading info here: https://search.nixos.org/packages?channel=unstable&show=musescore&from=0&size=50&sort=relevance&type=packages&query=musescore


Add missing team member

This revision includes:

Add missing team member

Seokwon Moon

Codecov Report

Merging #41 (58c0498) into main (71bc241) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #41   +/-   ##
=======================================
  Coverage   93.08%   93.08%
=======================================
  Files          20       20
  Lines         868      868
  Branches       20       20
=======================================
  Hits          808      808
  Misses         49       49
  Partials       11       11


WIP: PAPP-25307: Cherwell SaaS compatibility

Please ensure your pull request (PR) adheres to the following guidelines:

Please refer to our contributing documentation for any questions on submitting a pull request, link: Contribution Guide

Pull Request Checklist
Please check if your PR fulfills the following requirements:

[ ] Testing of all the changes has been performed (for bug fixes / features)
[ ] The readme.html has been reviewed and added / updated if needed (for bug fixes / features)
[ ] Use the following format for the PR description: <App Name>: <PR Type> - <PR Description>
[ ] Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.
[ ] Verify all checks are passing.
[ ] Do NOT use the next branch of the forked repo. Create separate feature branch for raising the PR.
[ ] Do NOT submit updates to dependencies unless it fixes an issue.

Pull Request Type
Please check the type of change your PR introduces:

[ ] New App
[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Documentation
[ ] Other (please describe):

Security Considerations (REQUIRED)

[ ] If you are exposing any endpoints using a REST handler,
please document them in the readme.html.
[ ] If this is a new connector or you are adding new actions

[ ] Please document in the readme.html all methods (eg, OAuth) used to authenticate
with the service that the connector is integrating with.
[ ] If any actions are unable to run on SOAR Cloud, please document this in the readme.html.

[ ] Are you introducing any new cryptography modules? If yes, please elaborate their purpose:
[ ] Are you are accessing the file system? If yes, please verify that you are only accessing paths returned through
the Vault API.
[ ] Are you are marking code to be ignored by Semgrep with nosemgrep?
If yes, please provide justification in an additional comment next to the ignored code.

Release Notes (REQUIRED)

Provide release notes as part of the PR submission which describe high level points about the changes for the upcoming GA release.

What is the current behavior? (OPTIONAL)

Describe the current behavior that you are modifying.

What is the new behavior? (OPTIONAL)

Describe the behavior or changes that are being added by this PR.

Other information (OPTIONAL)

Any other information that is important to this PR such as screenshots of how the component looks before and after the change.

Pay close attention to (OPTIONAL)

Any specific code change or test case points which must be addressed/reviewed at the time of GA release.

Screenshots (if relevant)

Thanks for contributing!

We will be releasing this app as community since our asset stopped working.
Reason for pipeline failures.

Static tests are failing because minimum phantom version is kept at 5.2.0 instead of the required 5.3.4 because we tested this app on v5.2.0 before our asset got expired.
Integration and static tests are failing because of the same issue with our asset.


Date range in Apple Order widget

The widget might display weird things, if Apple offers a time range as the remaining time. If it takes Apple longer than the “from” time, the widget displays a negative remaining time.

I therefore propose two improvements:
If the remaining time becomes negative, it should be set to 0 by just using something like max(0, whatever calculation). Or maybe you should set it to 1 if it is lower than 1, I’m not really sure about Apple’s logic here.
If a time range is used, the widget always uses an optimistic estimation, that is, it takes the “from” time for the calculation of the remaining time. You could offer a pessimistic estimation (selectable by some parameter in the code’s config section) by using the “to” date as the basis for the calculation of the remaining time.
I tried to make a proposal, but after looking at the code for a while I had to admit my programming skills are too weak to help. Sorry about that.

Hi @Bernd95 thanks for reporting this bug. I will try to find some time in the next days to fix this issue. I hope i'm able to fix it without test data.


How to Stop Generating through Curl + Sockets

Hello H2OGPT Team,
Many thanks for this wonderful implementation!
As title suggest, I have to find a way to stop generating via Sockets + Curl.
How exactly does the Stop Button works in UI?
Apologies if this is a silly question.

@pseudotensor please guide

Hi, the stop in UI works by stopping the async call, but the thread doing the generation still continues.  It's challenging in general to do an actual stop.  This is not possible for vLLM or OpenAI or other platforms either.  Same with GGUF, AWQ, etc.  No way to stop them.
For torch itself, I can hack something like this: https://github.com/h2oai/h2ogpt/issues/298  .  But it's not general.  However, I can potentially apply for the streaming case if used and use for all (or most)  model types.  However, this won't work for vLLM

However, I can potentially apply for the streaming case if used and use for all (or most) model types.

That would be wonderful and very helpful!
Where can I find documentation of CLI arguments? I'm interested to know what --early_stopping do


Update docs

Some of the code samples in the Readme are obsolete. Also, some new features aren't documented in Readme. See this and this.

From your comment in #35, we have the following points we can do easily:

[ ] But some of the code examples are out of date so they need to be fixed by looking at the tests I mentioned before.
[ ] Secondly there are some new features added like more protocols for range proofs which you can see in these tests but missing in the Readme.
[ ] The API described in the Readme is low-level and a higher level abstraction exists and is documented here conceptually but lacks code examples which could be written referring these tests, mostly this one. If you haven't seen this abstraction, I'll suggest taking a look. Its more ergonomic than the code examples in the main Readme.

Regarding the BBS/BBS+ threshold part, we did not use that and wouldn't know how to correctly document it.
For your last point, where you ask us what would help us, I think the following would be great, what do you think? We would be happy to take on that part, too, after we finished with the above points.

Add an automatic API documentation generation like typedoc
Write the corresponding API documentation for the anonymous credentials
Re-write the README by distributing the current documentation throughout the code tree and making sure that the typedoc (or whatever we'll use) integrates these texts as well

Hey @lovesh, I actually discussed this with Linus, so I can respond since he seems busy..
Both 2. and 3. assume using a CLI tool that generates API interface documentation from the code rather than writing it manually.
This morning, I was looking at https://typedoc.org/ (for the first time), and it generated a documentation just like this https://typedoc.org/example/ but with a less good UI.
What I know so far is that typedoc can import a readme file automatically, but I don't know if it can import multiple markdown files from different locations in the repo.
I'm attaching a screenshot of how using typedoc looks like on my machine now:

I think it can be easily hosted on github pages.

On a related topic, I'm starting on the first point you mentioned before

But some of the code examples are out of date so they need to be fixed by looking at the tests I mentioned before.

and I wanted to check if this change would be good.
Basically, the current examples use the schema from the tests, but since it doesn't work outside the tests, the examples were broken. Now the question is, should all the examples now follow one specific signature scheme (BBS/BBS+/PS/..) or how do you like to happen?

Hi @lanterno

What I know so far is that typedoc can import a readme file automatically, but I don't know if it can import multiple markdown files from different locations in the repo.

What i understood from Linus's comment was the opposite, i.e. typedoc will somehow take the code comments (say on top of a function) and render that in a readme. Found this plugin that can generate markdown from typedoc. But either way, yes, we can host the generated docs on github.

but with a less good UI.

There are themes and plugins that can help.

and I wanted to check if this type of change would be good (for example).

Yes.

Now the question is, should all the examples now follow one specific signature scheme (BBS/BBS+/PS/..) or how do you like it to look?

Yes, we should pick one scheme say BBS+ and put a note on top saying that other schemes can be used similarly and link to the tests to show signature of functions of other schemes.

What i understood from Linus's comment was the opposite, i.e. typedoc will somehow take the code comments (say on top of a function) and render that in a readme

It does both. It builds a home page from the readme, and then uses the code along with its comments to build a reference API.

Found this plugin that can generate markdown from typedoc
There are themes and plugins that can help.

Nice!

Yes, we should pick one scheme say BBS+ and put a note on top saying that other schemes can be used similarly and link to the tests to show signature of functions of other schemes.

Perfect! I can do that! Do you have a preference for one of them? I like the BBS variant because it has shorter names.

It does both. It builds a home page from the readme, and then uses the code along with its comments to build a reference API.

Nice. Will check more.

I like the BBS variant because it has shorter names and the differences with BBS+ will be minimal.

Yes, BBS is fine.

What i understood from Linus's comment was the opposite, i.e. typedoc will somehow take the code comments (say on top of a function) and render that in a readme. Found this plugin that can generate markdown from typedoc. But either way, yes, we can host the generated docs on github.

Sorry for the confusion. I actually meant:

split the main README in different READMEs
add API documentation
have a tool which merges all of this into (a) nice html page(s)

Even though creating the READMEs from the code might also be nice. But I think it will get complicated to know what to update...

@lanterno @ineiti PR for points 1 and 2. For 2, most significant changes are in this Readme.

@lanterno @ineiti  typedoc has been integrated in github workflow and docs are deployed here.


[AUTOPATCHER-CORE] Upgrade nasm to 2.16 patch CVE-2022-44370 -

[AUTOPATCHER-CORE] Upgrade nasm to 2.16 patch CVE-2022-44370
Upgrade pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=365806&view=results
AMD64 build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=365807&view=results
ARM64 build -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=365808&view=results

Whoever reviews this, please do manual verification that the correct fix is present in this version. I'm skeptical that this actually fixes the issues, since the advisory does say "NASM v2.16 was discovered to contain a heap buffer overflow..."

Whoever reviews this, please do manual verification that the correct fix is present in this version. I'm skeptical that this actually fixes the issues, since the advisory does say "NASM v2.16 was discovered to contain a heap buffer overflow..."

This is fixed in nasm-2.16rc1 which is a release candidate.
$ git describe --tags 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d
nasm-2.16rc1-8-g2d4e6952

https://www.nasm.us/pub/nasm/releasebuilds/2.16.02rc1/

This is fixed in nasm-2.16rc1 which is a release candidate.
$ git describe --tags 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d
nasm-2.16rc1-8-g2d4e6952

https://www.nasm.us/pub/nasm/releasebuilds/2.16.02rc1/
Knowing that its a release candidate, I would be in favor to backport (if feasible) the patch that address the CVE instead of an upgrade.

The commit 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d seems already merged into the release nasm-2.16. Please look at the below output.
/CVEWork/nasm/nasm (master=) git tag --contains 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d
nasm-2.16
nasm-2.16.01
nasm-2.16.02rc1
nasm-2.16rc10
nasm-2.16rc11
nasm-2.16rc12
nasm-2.16rc2
nasm-2.16rc3
nasm-2.16rc4
nasm-2.16rc5
nasm-2.16rc6
nasm-2.16rc7
nasm-2.16rc8
nasm-2.16rc9

I have initially have taken the path of backporting the patch which resulted into build issues and hence chosen the patch of upgrading.

This is fixed in nasm-2.16rc1 which is a release candidate.
$ git describe --tags 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d
nasm-2.16rc1-8-g2d4e6952

https://www.nasm.us/pub/nasm/releasebuilds/2.16.02rc1/
Knowing that its a release candidate, I would be in favor to backport (if feasible) the patch that address the CVE instead of an upgrade.

The commit 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d seems already merged into the release nasm-2.16. Please look at the below output.
/CVEWork/nasm/nasm (master=) git tag --contains 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d
nasm-2.16
nasm-2.16.01
nasm-2.16.02rc1
nasm-2.16rc10
nasm-2.16rc11
nasm-2.16rc12
nasm-2.16rc2
nasm-2.16rc3
nasm-2.16rc4
nasm-2.16rc5
nasm-2.16rc6
nasm-2.16rc7
nasm-2.16rc8
nasm-2.16rc9

I have initially taken the path of backporting the patch which resulted into build issues and hence chosen the path of upgrading.

Interesting, how come we come up with different result ? What is the upstream git repo project that you cloned ?
Here's the details of mine:
$ git branch
* master
$ git remote -v
origin  https://github.com/netwide-assembler/nasm.git (fetch)
origin  https://github.com/netwide-assembler/nasm.git (push)
$ git describe --contains 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d
nasm-2.16rc2~26

Can you manually check that the desired CVE fix code is present in the tarball you have upgraded to ?

This is fixed in nasm-2.16rc1 which is a release candidate.
$ git describe --tags 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d
nasm-2.16rc1-8-g2d4e6952

https://www.nasm.us/pub/nasm/releasebuilds/2.16.02rc1/
Knowing that its a release candidate, I would be in favor to backport (if feasible) the patch that address the CVE instead of an upgrade.

The commit 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d seems already merged into the release nasm-2.16. Please look at the below output.
/CVEWork/nasm/nasm (master=) git tag --contains 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d
nasm-2.16
nasm-2.16.01
nasm-2.16.02rc1
nasm-2.16rc10
nasm-2.16rc11
nasm-2.16rc12
nasm-2.16rc2
nasm-2.16rc3
nasm-2.16rc4
nasm-2.16rc5
nasm-2.16rc6
nasm-2.16rc7
nasm-2.16rc8
nasm-2.16rc9

I have initially taken the path of backporting the patch which resulted into build issues and hence chosen the path of upgrading.

Interesting.
What is the upstream git repo project that you cloned ? Here's the details of mine:
$ git branch
* master
$ git remote -v
origin  https://github.com/netwide-assembler/nasm.git (fetch)
origin  https://github.com/netwide-assembler/nasm.git (push)
$ git describe --contains 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d
nasm-2.16rc2~26

Can you manually check that the desired CVE fix code is actually present in the 2.16 tarball to double confirm what your git result provides ?
If it is present then I am fine, if its only found in the rc tarball, then we need to find another way.

I am also using the same GitHub project. In order to make sure I checked out the tag nasm-2.16 and verified that the commit id we are looking for is actually present by doing git log and searching for the commit
commit 2d4e6952417ec6f08b6f135d2b5d0e19b7dae30d
Author: H. Peter Anvin<EMAIL_ADDRESS>Date:   Mon Nov 7 10:26:03 2022 -0800

    quote_for_pmake: fix counter underrun resulting in segfault

    while (nbs--) { ... } ends with nbs == -1. Rather than a minimal fix,
    introduce mempset() to make these kinds of errors less likely in the
    future.

    Fixes: https://bugzilla.nasm.us/show_bug.cgi?id=3392815
    Reported-by<EMAIL_ADDRESS>    Signed-off-by: H. Peter Anvin<EMAIL_ADDRESS>

I have also manually verified that the code changes are present in nasm-2.16 tar ball that we have downloaded.

Appreciate the thorough review, @suresh-thelkar!

Thank you @oliviacrain  and @jslobodzian  for taking this PR further.


Check if MPV is installed

Bug Description
My new PC does not have MPV installed. That's fine, I don't need it, I want to run my NodeJS project and develop other features. But it crashes because of that.
2021-10-05 16:27:31:203 info: --- Env: development ---
error: uncaughtException: Command failed: mpv --version
/bin/sh: mpv: command not found

Error: Command failed: mpv --version
/bin/sh: mpv: command not found

    at ChildProcess.exithandler (node:child_process:397:12)
    at ChildProcess.emit (node:events:394:28)
    at maybeClose (node:internal/child_process:1064:16)
    at Socket.<anonymous> (node:internal/child_process:450:11)
    at Socket.emit (node:events:394:28)
    at Pipe.<anonymous> (node:net:672:12) {"error":{"killed":false,"code":127,"signal":null,"cmd":"mpv --version"},"stack":"Error: Command failed: mpv --version\n/bin/sh: mpv: command not found\n\n    at ChildProcess.exithandler (node:child_process:397:12)\n    at ChildProcess.emit (node:events:394:28)\n    at maybeClose (node:internal/child_process:1064:16)\n    at Socket.<anonymous> (node:internal/child_process:450:11)\n    at Socket.emit (node:events:394:28)\n    at Pipe.<anonymous> (node:net:672:12)","exception":true,"date":"Tue Oct 05 2021 16:27:31 GMT+0200 (heure d’été d’Europe centrale)","process":{"pid":22510,"uid":501,"gid":20,"cwd":"/Volumes/SSD/Sites/quiz/backend","execPath":"/Users/dimitribocquet/.nvm/versions/node/v16.9.1/bin/node","version":"v16.9.1","argv":["/Users/dimitribocquet/.nvm/versions/node/v16.9.1/bin/node","/Volumes/SSD/Sites/quiz/backend/app.js"],"memoryUsage":{"rss":101367808,"heapTotal":68894720,"heapUsed":38808248,"external":24276234,"arrayBuffers":20872713}},"os":{"loadavg":[1.34521484375,1.72314453125,1.64697265625],"uptime":4572},"trace":[{"column":12,"file":"node:child_process","function":"ChildProcess.exithandler","line":397,"method":"exithandler","native":false},{"column":28,"file":"node:events","function":"ChildProcess.emit","line":394,"method":"emit","native":false},{"column":16,"file":"node:internal/child_process","function":"maybeClose","line":1064,"method":null,"native":false},{"column":11,"file":"node:internal/child_process","function":null,"line":450,"method":null,"native":false},{"column":28,"file":"node:events","function":"Socket.emit","line":394,"method":"emit","native":false},{"column":12,"file":"node:net","function":null,"line":672,"method":null,"native":false}],"timestamp":"2021-10-05 16:27:31:220"}
error: uncaughtException: Command failed: mpv --version

I tried to embed the require with a try-catch, but it does not work (I am never in the catch):
let mpvAPI;
try {
    mpvAPI = require('node-mpv');
} catch (error) {
    console.log("MPV not installed");
    console.log(error);
}

Do we have a way to verify if MPV is installed?

Hey there,
MPV needs  to be installed on your system for this module to work. It's a wrapper around it and it sends commands to the running MPV binary.
Whether you have MPV installed depends on what OS you're using, I'm assuming either Linux or macOS judging from the /bin/sh output. On either, just open a terminal and enter mpv and press enter. If it works, awesome you have mpv, if it says something along the lines of command not found you either don't have  MPV installed or it's not in your path.
On Linux, use your distributions package manager. For example apt-get on Ubuntu as in sudo apt-get install mpv. Let's just hope it does install a new enough version, if I remember correctly, you need at least 0.7 or something that (which is really old, but on some Linux distros such as Debian you never know).
For macOS brew is a great third party package manager that can be used to install various packages and tools, such as MPV.
Of course you can also just check the installation section on the mpv website, this should get you covered.
I don't think this is a bug as not working when mpv isn't installed is expected behaviour, that's why I will close this issue for now. Please feel free to re-open it if you see fit. And hit me up if you got any questions : )
Cheers!


update azure to Xcode 11.2 and OIDN to 1.2.0

Azure will now compile with Xcode 11.2 due to permission problems with Xcode 10 concerning code signing.
changes for OIDN 1.2 and updated MacOsDistFiles link.

Look like i need permission to access the secure file location for the certificate


Image Cropper

Script Title - Image Cropper
Brief - Script to crop images
Instructions

Create a new folder for your script and file/folder name should be appropriate.
Create a README.md (using this template) in your folder for program Instructions
add requirements.txt if needed

Programming Language

[x] Python

Happy Coding
Kindly assign me to this issue

Hello! Can you please assign me to work on this issue? Would be happy to solve it.

#812


Given a tool/framework & version number fetch the API documentation and create embeddings

Create a thin-slice MVP. Given a library name and version, we should fetch the latest documentation and create embeddings for LLM so that it can be accessed and searched.

@Chakit22 this is yours

Thanks @nraychaudhuri !
But, Can I get more info on this? I'm not sure exactly what should I do and how should I proceed?


General question about getting started with Twilio Video in React

This seems to be the only resource I can find for building out Twilio Video in React. It also seems like a lot of assumptions were made in this example application that make it impossible to tell how to just add Twilio Programmable Video into an existing React app.
This app includes firebase... Are you saying we need firebase in order to use Twilio Programmable Video?
Why not just publish an npm package with all of the hooks and a few of the base components in this app for developers to consume in their own apps?
The Twilio marketing material for this says "Launch your own video app with text-based chat in minutes with the updated Twilio Video Open Source ReactJS application". It should say "Launch this demo app we built in minutes and then spend weeks trying to figure out how to get it to work in your own application".
Am I missing something? Where is the documentation on just the core components needed to build out video chat, without an entire app built around it?

aren't you looking for https://github.com/twilio/twilio-video.js/ ?

Hi @jtweaver - thanks for the question! This repo demonstrates a fully-featured app focused on the group collaboration, so it might not fit your use case perfectly or be the best place to start if you are just getting started with Twilio Video.
We do plan to add getting started documentation for React (you aren't the first person with this type of feedback), but a good starting spot is the JavaScript Getting Started docs and then we have a number of blog posts for building with React:

Build a Custom Video Chat App with React and Twilio Programmable Video
Build a Video Chat with React Hooks
Build a Video Application with Breakout Rooms Using Twilio Programmable Video, React, TypeScript, and Express — Part 1
Build a Video Application with Breakout Rooms Using Twilio Programmable Video, React, TypeScript, and Express — Part 2
... might be more.

Per Firebase, you don't have to use it (see here in the readme). Including that functionality serves as an example for adding user authentication, and if someone is already using/wants to use Firebase... even better.
For your point on the NPM package, we are looking for some early feedback from the community on an ongoing initiative in this area. If you (or anyone reading this) is interested in helping us define this, send me an email at scoleman at twilio.com.
Thanks, and let me know if you have any other questions!


WNet Batch initialization Error

Hello,
I have tried using the wnet code but each time i try to train it, it says :
Initializing Batch Dataset Reader...                                                                                Traceback (most recent call last):
File "src\UNet.py", line 355, in                                                                                train_dataset_reader, validation_dataset_reader = create_BatchDatset()
File "D:\alex\Documents\Workspace py\seg\unsupervised-image-segmentation-by-WNet-with-NormalizedCut-master\src\data_io\BatchDatsetReader_VOC.py", line 109, in create_BatchDatset                                                                                train_dataset = BatchDatset(data_record['training'],
File "D:\alex\Documents\Workspace py\seg\unsupervised-image-segmentation-by-WNet-with-NormalizedCut-master\src\data_io\BatchDatsetReader_VOC.py", line 127, in init                                                                                self.read_data_to_self(data_records)
File "D:\alex\Documents\Workspace py\seg\unsupervised-image-segmentation-by-WNet-with-NormalizedCut-master\src\data_io\BatchDatsetReader_VOC.py", line 135, in read_data_to_self                                                                                [resize_size, resize_size], interp='bilinear') for datum in data_records])
File "D:\Programmes\Anaconda\lib\site-packages\numpy\core\shape_base.py", line 349, in stack                                                                raise ValueError('need at least one array to stack')                                                                                ValueError: need at least one array to stack

Hi,
I have the same problem, were you able to resolve it?
If you were could you please share how you managed to?
Thx in advance

Hello,
If i were t guess, i would say that you're on windows, in my case, the os.path.join putted "" in pathfiles and it didn't worked because of that, i just used filepath.replace("\", "/") exery time i see the os path join.
It worked then.

First of all thank you for your help!
Unfortunately your tip hasn't solved my issue.
Can you specify which command line options you used to run the program and which file you executed?
Thanks

I just used the normal options, also, it is a double backslash on the replace, github removed the second one

I used the double backslash, however it hasn't worked.
I used "python WNet_naive.py --mode train --num_layers 9 --debug True"
Did you run the WNet_bright.py file?

@robertkirsten
The blackslash solution works fine. If think your issue is due to the fact, that you created a empty pickle file while running the code the first time.
If you delete the pickle file, it should work.


Testing the difference between learning responses and ellipticities

This issue is to track the investigation/comparison between training the model to have a unitary response matrix and just calculating ellipticities out of galaxy stamps.

So how are we doing here? Does it train with our loss on response matrices?


Ability to Duplicate Notifications

Checklist

[x] I checked for similar existing requests (both open and closed) before posting.
[x] My request is generic, other users may benefit from it too.

Proposal
I've setup a number of notifications to send to myself, but in order to setup the same notifications for my wife, I need to re-create each one by hand. It would be great if there was an option to duplicate each notification and then I'd only need to adjust the target for each one. All of the notification wording and other settings would be copied.
Additional info
Similar functionality to the Home Assistant Automations 'duplicate' function.

I'm sorry, I did not have any time to work on this project recently. I will see if this can be added.


Switch CI to Github Actions

From what I can gather on Discord there seems to be a consensus to switch to GH Actions (and away from TravisCI).
Some of the goals:
Build on

[x] Linux (added in #44)
[x] macOS (added in #44)
[x] Windows (unfinished version added in #44)
[ ] Automatic publish on pushed tags

Do you want to tackle this @CGMossa ? Otherwise I'd take a stab at it soon(-ish).

Please take a stab at it.
I tried to download act to test this locally, but it doesn't support
Windows.
On Wed, 25 Nov 2020 at 14:44, Maximilian Goisser<EMAIL_ADDRESS>wrote:

From what I can gather on Discord there seems to be a consensus to switch
to GH Actions (and away from TravisCI).
Some of the goals:

Build on Linux, macOS and Windows
Automatic publish on pushed tags

Do you want to tackle this @CGMossa https://github.com/CGMossa ?
Otherwise I'd take a stab at it soon(-ish).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/extendr/extendr/issues/42, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAIDVSCSI7BQ3RUL7LRDWQLSRUC3TANCNFSM4UCNLLSQ
.

@CGMossa FYI, there shouldn't be any need to test anything locally. Just drop a .yaml file into .github/workflows and see what happens when you push. If the build doesn't work, you amend the commit and try again. Can be a bit cumbersome, but that's the process everybody uses.

Build on windows works now. I've checked the box.

Automatic publish on pushed tags

I've never published a crate, but it seems it's as simple as just executing cargo publish with a secret.
e.g. https://github.com/rust-windowing/winit/blob/master/.github/workflows/publish.yml
The question is, is it always the case that all the crates in this repo are published all together? Or, is there a chance that you want to publish only some of these with a small patch? If so, a better shell script might be needed.

I think it's best to keep think of all the crates in the extendr workspace as one unit that gets published all at the same time with the same version. Note that if we merge https://github.com/extendr/extendr/pull/50 there'll be one more crate in the workspace.

I see. Then, maybe CI should check all the versions are the same?

Ah, yes, that sounds like a good idea. The versions and the dependency statements should all be the same. Otherwise you end up with issues such as this one: https://github.com/extendr/extendr/issues/28

cargo-workspace looks useful both for publishing and version check.
❯ cargo ws list --json
[
  {
    "name": "extendr-api",
    "version": "0.1.10",
    "location": "/home/yutani/repo/extendr/extendr-api",
    "private": false,
    "independent": false
  },
  {
    "name": "extendr-macros",
    "version": "0.1.10",
    "location": "/home/yutani/repo/extendr/extendr-macros",
    "private": false,
    "independent": false
  }
]

Oh yes, this looks very useful.

This has been a stunning success.
Should we shift the automatic publish to another Issue? I'm keen to close as many issues as possible
to keep them fresh.

Yes, I think automatic publish can be deferred to some other time in the future, and in a different issue.

Closing this as GH actions are working now.


Automate build and publish of the user guide

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
The main datafusion documentation site at https://arrow.apache.org/datafusion is good because:

They look good and follow the best practice for open source project documentation
They are associated clearly with the overall arrow.apache.org

The documentation source is at https://github.com/apache/arrow-datafusion/tree/main/docs.
https://arrow.apache.org/datafusion is updated (typically by @andygrove) when new releases of arrow-datafusion are published to crates.io (for example,  https://github.com/apache/arrow-site/pull/313)
However, the current setup has a few notable issues:

It is behind what is in the repo as it is only updated every release (every 2 weeks at the time of writing)
The content of the landing page in the repo (README): https://github.com/apache/arrow-datafusion has diverged from the user guide (as I believe developers want the latest content and the only way to see that without building the docs locally is README.md)
The manual update process is somewhat cumbersome

I think if the user guide was more immediately updated, people would be more likely to contribute to it as well.
Describe the solution you'd like
I would like some mechanism to see the latest, rendered version of the user guide as a webpage.

[ ] On every commit to main, the site would be updated with the latest version of the user guide
[ ] The main README.md page in arrow-datafusion would redirect to the hosted site

Bonus points for
Describe alternatives you've considered
Perhaps we could make a github pages site https://pages.github.com/ ?
Additional context

Leaving a note to myself (and maybe others) from @martin-g to check out how the apache-datafusion-python module works

Maybe we can make it like the apache-datafusion-python module

Just to make sure I understand correctly: The DataFusion team prefers commits to main to update the main site immediately, right ?

Just to make sure I understand correctly: The DataFusion team prefers commits to main to update the main site immediately, right ?

This is my preference. Any thoughts @andygrove @Dandandan or @thinkharderdev ?
Eventually, perhaps when we have longer term stable versions of datafusion, hosting snapshots of the docs for older releases might be useful. But I think the most important first thing is to get the most up to date docs published first

The docs build fails for me with:
./build.sh
Running Sphinx v6.1.3
making output directory... done
[autosummary] generating autosummary for: contributor-guide/communication.md, contributor-guide/index.md, contributor-guide/quarterly_roadmap.md, contributor-guide/roadmap.md, contributor-guide/specification/index.rst, contributor-guide/specification/invariants.md, contributor-guide/specification/output-field-name-semantic.md, index.rst, user-guide/cli.md, user-guide/configs.md, ..., user-guide/sql/aggregate_functions.md, user-guide/sql/data_types.md, user-guide/sql/ddl.md, user-guide/sql/explain.md, user-guide/sql/index.rst, user-guide/sql/information_schema.md, user-guide/sql/scalar_functions.md, user-guide/sql/select.md, user-guide/sql/sql_status.md, user-guide/sql/subqueries.md
myst v1.0.0: MdParserConfig(commonmark_only=False, gfm_only=False, enable_extensions={'tasklist'}, disable_syntax=[], all_links_external=False, url_schemes=('http', 'https', 'mailto', 'ftp'), ref_domains=None, fence_as_directive=set(), number_code_blocks=[], title_to_header=False, heading_anchors=3, heading_slug_func=None, html_meta={}, footnote_transition=True, words_per_minute=200, substitutions={}, linkify_fuzzy_links=True, dmath_allow_labels=True, dmath_allow_space=True, dmath_allow_digits=True, dmath_double_inline=False, update_mathjax=True, mathjax_classes='tex2jax_process|mathjax_process|math|output_area', enable_checkboxes=False, suppress_warnings=[], highlight_code_blocks=True)
building [mo]: targets for 0 po files that are out of date
writing output...
building [html]: targets for 26 source files that are out of date
updating environment: [new config] 26 added, 0 changed, 0 removed
reading sources... [100%] user-guide/sql/subqueries
looking for now-outdated files... none found
pickling environment... done
checking consistency... done
preparing documents... done
writing output... [  3%] contributor-guide/communication
Theme error:
An error happened in rendering the page contributor-guide/communication.
Reason: UndefinedError("'logo' is undefined")
make: *** [Makefile:38: html] Error 2

https://github.com/martin-g/arrow-datafusion/actions/runs/4448158011/jobs/7810591628?pr=1
Do I need to do something more than https://github.com/martin-g/arrow-datafusion/pull/1/files#diff-d54d69dbb27e75dae25cb4b2384310cb57707e419377cf572d5cb0ecc1f16877R31-R43 ?

I've removed temporarily the usage of logo to be able to build: https://github.com/martin-g/arrow-datafusion/pull/1/commits/a3a3107dd56fddf87eb49fe40da34d28876dc588

Just to make sure I understand correctly: The DataFusion team prefers commits to main to update the main site immediately, right ?

This is my preference. Any thoughts @andygrove @Dandandan or @thinkharderdev ?
Eventually, perhaps when we have longer term stable versions of datafusion, hosting snapshots of the docs for older releases might be useful. But I think the most important first thing is to get the most up to date docs published first

Agreed

I am happy to report I have tested this and confirmed that the process is working as expected!
Here is an example PR https://github.com/apache/arrow-datafusion/pull/5684
And the content has appeared at https://arrow.apache.org/datafusion/user-guide/introduction.html 🎉


Visualisation notebook throws UnimplementedError:  Fused conv implementation does not support grouped convolutions for now

I am getting an error when running model_test.evaluate(mnist_dataset.X_test, mnist_dataset.y_test) in the dynamic visualisations notebook. The first time I installed the requirements there were a couple of warnings, about incompatible versions. I tried installing again and everything was then OK.
The notebook runs fully on Colab, thanks, but I would like to get it working locally. Any ideas to try and fix this please?

UnimplementedError                        Traceback (most recent call last)
 in
----> 1 model_test.evaluate(mnist_dataset.X_test, mnist_dataset.y_test)
C:\DSAI\Dissertation\Efficient-CapsNet\models\model.py in evaluate(self, X_test, y_test)
94             acc = np.mean(acc)
95         else:
---> 96             y_pred, X_gen =  self.model.predict(X_test)
97             acc = np.sum(np.argmax(y_pred, 1) == np.argmax(y_test, 1))/y_test.shape[0]
98         test_error = 1 - acc
~\miniconda3\envs\dsai_py3.8\lib\site-packages\tensorflow\python\keras\engine\training.py in predict(self, x, batch_size, verbose, steps, callbacks, max_queue_size, workers, use_multiprocessing)
1627           for step in data_handler.steps():
1628             callbacks.on_predict_batch_begin(step)
-> 1629             tmp_batch_outputs = self.predict_function(iterator)
1630             if data_handler.should_sync:
1631               context.async_wait()
~\miniconda3\envs\dsai_py3.8\lib\site-packages\tensorflow\python\eager\def_function.py in call(self, *args, **kwds)
826     tracing_count = self.experimental_get_tracing_count()
827     with trace.Trace(self._name) as tm:
--> 828       result = self._call(*args, **kwds)
829       compiler = "xla" if self._experimental_compile else "nonXla"
830       new_tracing_count = self.experimental_get_tracing_count()
~\miniconda3\envs\dsai_py3.8\lib\site-packages\tensorflow\python\eager\def_function.py in _call(self, *args, **kwds)
892               *args, **kwds)
893       # If we did not create any variables the trace we have is good enough.
--> 894       return self._concrete_stateful_fn._call_flat(
895           filtered_flat_args, self._concrete_stateful_fn.captured_inputs)  # pylint: disable=protected-access
896
~\miniconda3\envs\dsai_py3.8\lib\site-packages\tensorflow\python\eager\function.py in _call_flat(self, args, captured_inputs, cancellation_manager)
1916         and executing_eagerly):
1917       # No tape is watching; skip to running the function.
-> 1918       return self._build_call_outputs(self._inference_function.call(
1919           ctx, args, cancellation_manager=cancellation_manager))
1920     forward_backward = self._select_forward_and_backward_functions(
~\miniconda3\envs\dsai_py3.8\lib\site-packages\tensorflow\python\eager\function.py in call(self, ctx, args, cancellation_manager)
553       with _InterpolateFunctionError(self):
554         if cancellation_manager is None:
--> 555           outputs = execute.execute(
556               str(self.signature.name),
557               num_outputs=self._num_outputs,
~\miniconda3\envs\dsai_py3.8\lib\site-packages\tensorflow\python\eager\execute.py in quick_execute(op_name, num_outputs, inputs, attrs, ctx, name)
57   try:
58     ctx.ensure_initialized()
---> 59     tensors = pywrap_tfe.TFE_Py_Execute(ctx._handle, device_name, op_name,
60                                         inputs, attrs, num_outputs)
61   except core._NotOkStatusException as e:
UnimplementedError:  Fused conv implementation does not support grouped convolutions for now.
[[node Efficinet_CapsNet_Generator/Efficient_CapsNet/primary_caps_2/conv2d/BiasAdd (defined at C:\DSAI\Dissertation\Efficient-CapsNet\utils\layers.py:129) ]] [Op:__inference_predict_function_3999]
Function call stack:
predict_function

Turned out to be due to not finding my GPU. I fixed that and the notebook now runs fine :)

Yes, the current version of TensorFlow hasn't the CPU kernel for that specific operation. We should add a hint to use the GPU runtime.
Thanks!


Disappearing Mass

I have been attempting to model gravitational instability for filaments with an Ostriker density profile.
My simulations have recently encountered an interesting error where the mass goes to zero after the simulation runs for a period of time.  I am using the FFT gravity method thus all the boundary conditions are periodic, so I don't think the mass is flowing out at the boundary.
I should be clear that athena does not output an error message, I am just under the impression that under periodic boundary conditions the mass should be conserved and even if it weren't there would be some time for the mass to `escape', it wouldn't happen instantaneously.
My current suspicion is that there is some maximum density which if exceeded will cause some variable to return NaN and in turn removes the mass somehow, or the self gravity returns some error due to an attempt to resolve sub-voxel structure and that removes the mass.
The .hst output I have returns NaN for the momenta, kinetic energy, and total energy after the mass `escapes'.  It gives 0.00000e+00 for the gravitational energy.
Has anyone else encountered behaviour like this?  I'm very new to simulation and am not entirely sure where to look to resolve this.
Thanks in advance.

Could you provide more details? It would help to have the problem generator, input file, and time by which things have gone wrong.

Is this a gravitationally unstable case? I won't be surprising if density becomes NaN due to runaway collapse. Yes, we need more information.

Here is the problem generator I used.  I'm trying to model adiabatic perturbations on top of a isothermal cylinder.  The conceit is the cylinder is initially at some isothermal equilibrium (it has the Ostriker density profile) and there is an adiabatic perturbation on top.  That's why we set the initial pressure to be the square of the isothermal sound speed times the density.  The sinusoidal perturbation is basically an anzatz (we know how a perturbation would develop).  The randomized density perturbations are to simulate anisotropy, they're from an older version where I was hoping the small variations would be enough to seed a collapse on their own.  This problem generator is a modified version of a problem generator a colleague of mine was using to make a Bonnor Ebert sphere, which is a modified shock cloud.
//Bonnor Ebert problem generator

// C++ headers
#include <cmath>      // sqrt()
#include <iostream>   // endl
#include <sstream>    // stringstream
#include <stdexcept>  // runtime_error
#include <string>     // c_str()
#include <time.h>     // srand(time)

// Athena++ headers
#include "../athena.hpp"
#include "../athena_arrays.hpp"
#include "../bvals/bvals.hpp"
#include "../coordinates/coordinates.hpp"
#include "../eos/eos.hpp"
#include "../field/field.hpp"
#include "../hydro/hydro.hpp"
#include "../mesh/mesh.hpp"
#include "../parameter_input.hpp"
#include "../gravity/gravity.hpp"

namespace {
Real gmma1, dl, pl, ul;
Real bxl, byl, bzl;
Real gconst;
} // namespace

//========================================================================================
//! \fn void Mesh::InitUserMeshData(ParameterInput *pin)
//  \brief Function to initialize problem-specific data in mesh class.  Can also be used
//  to initialize variables which are global to (and therefore can be passed to) other
//  functions in this file.  Called in Mesh constructor.
//========================================================================================

void Mesh::InitUserMeshData(ParameterInput *pin) {

  if (SELF_GRAVITY_ENABLED) {
    Real fourPiG = pin->GetReal("problem","fourPiG");
    SetFourPiG(fourPiG);
    //Real eps = pin->GetOrAddReal("problem","grav_eps", 0.0);
    //SetGravityThreshold(eps);
    SetMeanDensity(0.0);
  }
  return;
}

//========================================================================================
//! \fn void MeshBlock::ProblemGenerator(ParameterInput *pin)
//  \brief Problem Generator for the shock-cloud interaction test
//========================================================================================

void MeshBlock::ProblemGenerator(ParameterInput *pin) {
  Real gmma  = peos->GetGamma();
  gmma1 = gmma - 1.0;

  // Read input parameters
  Real rad    = pin->GetReal("problem","radius");
  Real mach = pin->GetReal("problem","Mach");
  Real drat = pin->GetReal("problem","drat");
  Real iso_sp = pin->GetReal("hydro","iso_sound_speed");
  Real pil = pin->GetReal("problem","pil");
  Real maxn = pin->GetReal("problem","maxn");
  Real amp = pin->GetReal("problem","amp");

  // Set paramters in ambient medium
  Real dr = std::pow((1+SQR(rad)/8),-2);
  Real pr = 1.0/(peos->GetGamma());
  Real ur = 0.0;

  // Initialize the grid
  for (int k=ks; k<=ke; k++) {
    for (int j=js; j<=je; j++) {
      for (int i=is; i<=ie; i++) {
         // ambient gas
         phydro->u(IDN,k,j,i) = dr;
         phydro->u(IM1,k,j,i) = ur*dr;
         phydro->u(IM2,k,j,i) = 0.0;
         phydro->u(IM3,k,j,i) = 0.0;
         //phydro->u(IEN,k,j,i) = pr/gmma1 + 0.5*dr*(ur*ur);
         phydro->u(IPR,k,j,i) = SQR(iso_sp)*phydro->u(IDN,k,j,i);

        // cloud interior
        Real diag = std::sqrt(SQR(pcoord->x1v(i)) + SQR(pcoord->x2v(j))
                              );
	Real profile =std::pow((1+SQR(diag)/8),-2);
        if (diag < rad) {
          phydro->u(IDN,k,j,i) = profile*(1+amp*std::cos(pil*maxn*pcoord->x3v(k)));
          phydro->u(IM1,k,j,i) = ur*dr*drat;
          phydro->u(IM2,k,j,i) = 0.0;
          phydro->u(IM3,k,j ,i) = 0.0;
          //phydro->u(IEN,k,j,i) = pr/gmma1 + 0.5*dr*drat*(ur*ur);
	  phydro->u(IPR,k,j,i) = SQR(iso_sp)*phydro->u(IDN,k,j,i);
        }
	std::srand(time(0));
	if (diag < rad/3) {
          phydro->u(IDN,k,j,i) = profile*(1+amp*std::cos(pil*maxn*pcoord->x3v(k)))+0.0001*(rand()/RAND_MAX);
          phydro->u(IM1,k,j,i) = ur*dr*drat;
          phydro->u(IM2,k,j,i) = 0.0;
          phydro->u(IM3,k,j ,i) = 0.0;
          //phydro->u(IEN,k,j,i) = pr/gmma1 + 0.5*dr*drat*(ur*ur);
	  phydro->u(IPR,k,j,i) = SQR(iso_sp)*phydro->u(IDN,k,j,i);
        }
      }
    }
  }

  return;
}

//----------------------------------------------------------------------------------------

Here is the input file
<comment>
problem   = shock cloud interaction
reference = Shin,M.-S., Snyder, G., & Stone, J.M.
configure = --prob=shk_cloud_NoWave

<job>
problem_id = Cloud_NoWave      # problem ID: basename of output filenames

<output1>
file_type  = hst        # History data dump
dt         = 0.01       # time increment between outputs

<output2>
file_type  = hdf5       # data dump
variable   = prim       # variables to be output
dt         = 0.1        # time increment between outputs

<time>
cfl_number = 0.4        # The Courant, Friedrichs, & Lewy (CFL) Number
nlim       = 100000     # cycle limit
tlim       = 15.00      # time limit
integrator  = vl2       # time integration algorithm
xorder      = 2         # order of spatial reconstruction
ncycle_out  = 1         # interval for stdout summary info

<mesh>
nx1        = 200         # Number of zones in X1-direction
x1min      = -20.0       # minimum value of X1
x1max      = 20.0        # maximum value of X1
ix1_bc     = periodic     # inner-X1 boundary flag
ox1_bc     = periodic     # outer-X1 boundary flag

nx2        = 200         # Number of zones in X2-direction
x2min      = -20.0       # minimum value of X2
x2max      = 20.0        # maximum value of X2
ix2_bc     = periodic     # inner-X2 boundary flag
ox2_bc     = periodic     # outer-X2 boundary flag

nx3        = 400          # Number of zones in X3-direction
x3min      = -20.0       # minimum value of X3
x3max      = 20.0        # maximum value of X3
ix3_bc     = periodic    # inner-X3 boundary flag
ox3_bc     = periodic    # outer-X3 boundary flag

<meshblock>
nx1 = 100
nx2 = 100
nx3 = 100

<hydro>
iso_sound_speed = 1.0
gamma      = 1.3333    # gamma = C_p/C_v

<problem>
Mach       = 0.0       # Mach number of shock
drat       = 50000.0   # density ratio of cloud
beta       = 1.0       # plasma beta in upstream gas
fourPiG    = 1.0       #four pi g
radius     = 20.0      #cloud radius
maxn       = 4         #number of maxima
pil        = 0.07853981633 #kfactor
amp        = 0.125     #perturbed

<meshblock>
nx1=100
nx2=100
nx3=100

The hope is that I'll be able to observe the collapse over a few freefall times, once the behaviour of the collapse in this simpler version starts making more sense to me I'll add more complexity (initial rotation and magnetic fields).  Generally we use a polytropic equation of state where gamma is even closer to 1, but due to the way gamma is used to find the internal energy of the cloud I lowered it only a little from the 5/3 to 4/3.  The mass tends to disappear around t=10, the instability has definitely had time to develop but the change is so drastic.  I was hoping somehow there would be some indication that mass was escaping or the coalescing cores were getting too dense.
Thank you very much for your prompt replies.  I'm a novice and every bit of advice is very helpful.

I found one issue in your problem generator.  In Mesh::InitUserMeshData, you set the mean density (i.e., grav_mean_rho) to zero.  Instead, it is imperative that you set this value to the mean density of the mesh.
The (default) FFT self-gravity solver in Athena++ (a) employs Jeans' swindle to solve for the gravitational potential subject to fully periodic boundary conditions and (b) applies a momentum conserving numerical technique to apply gravitational accelerations using "gravity fluxes".    These fluxes are computed by taking the divergence of the gravitational stress tensor, thus, when in combination with Jeans' swindle, the (non-zero) mean density actually appears in the equations of motion.
After setting the mean density to the true mean density on the mesh, I was able to run your problem out to tlim = 15.00.  The corresponding history file is attached.
Cloud_NoWave.hst.txt

Thank you very much, I have just finished a simulation out to tlim =15.00 as well and found that the mass did not disappear.
Thank you all for your suggestions.


How do I delete a cell?

I accidentally added a new cell locally in the endgame issues notebook but I don't know how to delete it while in notebooks view :c

Edit: I'm on Codespaces. There also is a rendering glitch at the bottom since I resized the window to record the demo, but I'm assuming that's another issue.

/duplicate of https://github.com/microsoft/vscode/issues/117693 thanks!


Allow resolvers not defined in the schema

This work is a continuation of #379.
I merged master into it, made some cleaning of the code, and added tests as requested by @stubailo
TODO:

[x] If this PR is a new feature, reference an issue where a consensus about the design was reached (https://github.com/apollographql/graphql-tools/pull/379#issuecomment-322573985)
[x] Make sure all of the significant new logic is covered by tests
[x] Rebase your changes on master so that they can be merged easily
[x] Make sure all tests and linter rules pass
[x] Update CHANGELOG.md with your change

is there anything else I can do to help moving this PR forward?

Thanks a ton. Really sorry about the delay here - we had GraphQL summit around the end of October, so the whole team was super super occupied.


feat: filter stickers by type

As discussed in #334

Codecov Report
Base: 36.86% // Head: 36.93% // Increases project coverage by +0.07% :tada:

Coverage data is based on head (154f360) compared to base (b15a9b2).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #335      +/-   ##
==========================================
+ Coverage   36.86%   36.93%   +0.07%
==========================================
  Files          17       17
  Lines        4359     4364       +5
  Branches      157      157
==========================================
+ Hits         1607     1612       +5
  Misses       2750     2750
  Partials        2        2

Impacted Files
Coverage Δ

src/filter.ts
90.63% <100.00%> (+0.15%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

There should be another one is_static but it is not available in sticker object.
So not sure if it's possible.
Maybe we can add is_static in the sticker object internally when is_animation and is_video both are false.

This is not possible. This will break if a new sticker type is added. People can already filter for static stickers using bot.drop in combination with the filter queries introduced in this pull request :)

Correct, bot.drop does make sense.
So it seems complete.

@all-contributors add @ak4zh for this idea and the code contribution!

@ak4zh we usually require all contributors to sign their commits, please consider setting this up in the future :)
I will merge anyway now.


Fix Nest Anchor in Paragraph Test

Closes #4012 and closes #3989

@ltegman thanks for the PR. Verified and merged!


Character mesh hovers when a visibility blocking volume is spawned.

In my use case, I toss a flashbang grenade at the enemy character, which is supposed to block it from seeing the player. The enemy then hovers above the ground for a few seconds.
The enemy character should not hover.
AFAIK this happens after the commit from 6 oct 18:34 SHA  5fa18e5
This commit changed the character control rig.
The control rig ALS\Character\CR_Als contains a function TraceFootOffset which calls a function Foot Offset Trace. This in turn uses a hardcoded Trace Channel = Visibility.
When I change this trace channel value to my custom trace channel, the problem is fixed,
Suggested Solution
Promote Trace Channel to a variable, allowing it to be easily configurable to project-specific requirements.

Workaround

It is not hardcoded. As you showed, you can change this setting in the asset or create a variable for it :)


[DOCFIX] Update EC2 HA doc

Fix Vagrant installation instruction regarding getting the deployment script.

@aaudiber PTAL. Thanks!


Get-BestBcContainerImageName returns image name without ltsc2019

Describe the issue
2004 is both tag for BC version (2020 Wave I) and Windows build 2004. Because of that cmdlet does not append ltsc2019 when it should.
See first if in https://github.com/microsoft/navcontainerhelper/blob/master/ContainerHandling/Get-BestNavContainerImageName.ps1.
Example
Get-BestBcContainerImageName -imageName mcr.microsoft.com/businesscentral/onprem:2004 returns mcr.microsoft.com/businesscentral/onprem:2004,
but Get-BestBcContainerImageName -imageName mcr.microsoft.com/businesscentral/onprem:1910 returns mcr.microsoft.com/businesscentral/onprem:1910-ltsc2019.
Additional context
navcontainerhelper v<IP_ADDRESS>

For now adding ltsc2019 manually. I only needed that our in devops pipeline where we manually pull image (with some timeout for ALOps).

Thanks.
As you might have seen on my blog (http://www.freddysblog.com) we are changing from images to artifacts.
This means that soon we will stop building images altogether and eventually we will delete the existing images.
I know ALOps has support for artifacts already, you should switch.

Thanks. Will checkout ALOps.


mixed indentation with tab and spaces

Your files have a lot of tabs in them and python is complaining pretty hard about that.
I can take a crack at fixing the indentation if you like.

Thanks! I'll take a look when I can. Please take a crack if you want to.

closed via #2


[Bug]: Edit appearance, report primary key conflict

ODC version
ODC431
OB version
independent
What happened?
Edit appearance, report primary key conflict

What did you expect to happen?
。
How can we reproduce it (as minimally and precisely as possible)?
。
Anything else we need to know?
No response

fixed in 4.3.1

pass


Made failedRequest a static method

Thanks for this.
I’d thought is should be an instance method in order to leave the door open to future API support for asking which resource a response came from, which this change rules out. However, the use cases for that are fuzzy and might be achieved through other means as well. So let me know if making this static solves a concrete problem for you.

Using it when I cannot construct a correct resource endpoint. eg:
  public static func updateBusiness(business: Business) -> Request {
    guard let id = business.serverId else {
      return Resource.failedRequest(Siesta.Error(userMessage: "Object does not exist on server", cause: Error.objectNotOnServer))
    }
    return service.resource(.Businesses).child(id).request(.PUT, json: business, options: [.noSkipNull])
  }

Right — in the first example, the very reason the request fails is that there is no resource on which you could call a failedRequest() instance method. That seems decisive.


Markdown include not rendering on docs website

URL: https://devenv.sh/services/

https://github.com/cachix/devenv/blob/7128be003e2fc3a9a2e5bcaddc42cf86cf5a6972/docs/services.md?plain=1#L38C1-L38C1

Also in https://devenv.sh/languages/#supported-languages

fixed, thanks!


I have a question about php-gcm.

I'm using the PHP CI framework should be sure to use the composer?
Is there any way to run without using the composer?
If you have more detailed usage it seems to be good.
$ Sender = new Sender ($ gcmApiKey);
$ Message = new Message ($ collapseKey, $ payloadData);
try {
$ Result = $ sender-> send ($ message, $ deviceRegistrationId, $ numberOfRetryAttempts);
} Catch (\ InvalidArgumentException $ e) {
// $ DeviceRegistrationId was null
} Catch (PHP_GCM \ InvalidRequestException $ e) {
// Server returned HTTP code other than 200 or 503
} Catch (\ Exception $ e) {
// Message could not be sent
}
What methods can be used to add a phrase in getBodyLocKey?

Composer is recommended, but it is possible to download the PHP files and include them yourself to use it.
Take a look at the PHP doc for bodyLocKey and bodyLocArgs for more information about using those methods.


Return directly when initializing FileSystem again

When HBase gets FileSystem through Hadoop, both Hadoop and HBase will call initialize.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2295/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2312/
Test PASSed.

This looks good, after getting rid of the extraneous changes/variables that @calvinjia  mentioned.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2347/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/2353/
Test PASSed.


Schematic and PCB fixes per email discussion

Updates FE310 symbol for pin swap.
Moves R2 on schematic and PCB per pin swap.
Removes GND from PLL_AVSS.
Moves C5 to facilitate routing.
Placement and routing tweaks.
Close soldermask openings a bit.

Signed-off-by: Michael Welling<EMAIL_ADDRESS>

Thank you so much for these updates!


Tag without description

When I create a new tag, assign the description and use push (follow tags) I have my tag on Github.
But if I (consciously or accidentally) omit the description and use push (follow tags) again, my tag is not on Github.
I can't recreate the tag afterwards either since it already exists in vscode.
Is this a bug, or what would be the correct procedure after that?

I have used VSCode directly. But with the new version I had not discovered the problem anymore.

@Pixolantis thank you very much for the update.
I will go ahead and close the issue but please feel free to reopen it in case you run into this again. Thank you!


Add support for settings and retrieving exception cause

I do have a use case for this, consider that a Rust extension module that accepts and calls a user supplied Python callback, the Python callback can raise many kind of exceptions, but the Rust extension module will wrap them as an unified exception for example RuntimeError, it'd be nice to set the exception cause to whatever exception the Python callback throws so it's easier to debug.


install hooks

This issue follows #84. Also related to #81

Introduce a hook system
call hooks each time a metric is updated in barrel_metrics

This is the wrap up of todays discussion about metrics plugin.
The objective is to install a stats plugin infrastructure for metrics inspired by the fuse stats plugin system.

design a behaviour for metrics (such as fuse_stats_plugin)
Instantiate the implementation of the plugin at startup, based on rebar.config
take over the plugins available in fuse
add a plugin to send metrics over UDP statsd

The metrics counter will be identified by path such as:
InitialValue = 0,
Name = ["replicate", <<"repid">>, "doc_read"],
barrel_metrics:init(Name, InitialValue),

Issue has been moved to Gitlab. Please follow the changes there:
https://gitlab.com/barrel-db/barrel-platform/issues/87


Fix CLI response code

Fixes #236

Coverage remained the same at 89.035% when pulling fc4e349b8b07e22270b953064d9009a26ab57c99 on safesoftware:bugfix/cli-response-code into 637b264c8c2f5e304bc129c07c7c11ef7bda0798 on Miserlou:master.


Add integration tests(1)

Summary of changes
Changes introduced in this pull request

Implement the integration tests using CosmJS + (local) juno
Add the integration tests for TokenWrapper, mixer & anchor contracts

Reference issue to close (if applicable)
Closes

I will take another review, but this PR needs a lot of cleanups
remove test-scripts/.DS_Store and all .DS_Store files. and also, would be could to remove all *.wasm files, this could be generated/compiled later during the tests.

Done https://github.com/webb-tools/protocol-cosmwasm/pull/53/commits/7c37a80e029b07c53071a17b7f4798f6b3fddde9


flutter 3.22

in flutter 3.22 playercontroller doesnt work correctly. All player has same instances

I have the same bug, as far as I realize it's working fine on debug mode but using same playercontroller instances at release mode. For release mode key string value isn't printed like before, now it only shows 'Instance of UniqueKey'. That string value is used for finding/filtering streaming players at source code instead of UniqueKey object itself, that's the issue.

@egorOztmz  i have the exactly the same issue.
How did you manage this ? Downgrading flutter ?
My app is in production so this is very important for me. Thanks in advance

Unfortunately yes @Nico3652, we downgraded flutter to 3.19.6 until this is fixed hopefully.

+1

+1

+1

Unfortunately yes @Nico3652, we downgraded flutter to 3.19.6 until this is fixed hopefully.

The issue is fixed in the package or the issue is fixed when you downgraded the flutter to 3.19.6

Unfortunately yes @Nico3652, we downgraded flutter to 3.19.6 until this is fixed hopefully.

The issue is fixed in the package or the issue is fiexed when you downgraded the flutter to 3.19.6

This seems like a flutter issue that was solved in the master channel:
https://github.com/flutter/flutter/issues/148401#issuecomment-2172720783

The issue happens only on Android release mode !

This issue has been resolved with #310. Currently it has been merged to main. For now, you can use the main branch in your pubspec.yaml until it has been released.

@ujas-m-simformsolutions Please release the fix as a version if possible.


tailwindcss + laravel-spark

I'm trying to integrate tailwindcss into an existing site that is built with laravel-spark using less and laravel-mix
When I add @tailwind preflight; and @tailwind utilities; to my app.less file, I get the following error from npm run watch:
error in ./resources/assets/less/app.less

Module build failed: ModuleBuildError: Module build failed: TypeError:
atRule.before is not a function
at css.walkAtRules.atRule
(/var/www/html/node_modules/tailwindcss/lib/lib/substitutePreflightAtRule.js:13:16)

...

here is my webpack.mix.js:
mix.less('resources/assets/less/app.less', 'public/css')
  .options({
    postCss: [
      tailwindcss('./tailwind.js'),
    ]
  })
  .copy('node_modules/sweetalert/dist/sweetalert.min.js', 'public/js/sweetalert.min.js')
  .copy('node_modules/sweetalert/dist/sweetalert.css', 'public/css/sweetalert.css')
  .js('resources/assets/js/app.js', 'public/js')
  .webpackConfig({
      resolve: {
          modules: [
              path.resolve(__dirname, 'vendor/laravel/spark/resources/assets/js'),
              'node_modules'
          ],
          alias: {
              'vue$': 'vue/dist/vue.js'
          }
      }
  });

Any thoughts/suggestions? Much obliged.

I had this exact same issue! I installed Yarn globally and everything worked well, why? I have no clue, but try that

+1
Experiencing this as well!! Tried to use yarn, yarn run dev same problem
yarn: 1.3.2
npm: 5.5.1
node: 9.1.0
tailwind: 0.1.6
app.less: (pretty much the base Spark one, but trying to add @tailwind stuff
@import "./../../../node_modules/bootstrap/less/bootstrap";

// @import "./spark/spark";
@import "./../../../vendor/laravel/spark/resources/assets/less/spark";

@tailwind preflight;

@tailwind utilities;

package.json:
 "dependencies": {
    "axios": "^0.15.2",
    "bootstrap": "^3.0.0",
    "cross-env": "^3.2.3",
    "jquery": "^2.1.4",
    "js-cookie": "^2.1.0",
    "laravel-mix": "0.*",
    "moment": "^2.10.6",
    "promise": "^7.1.1",
    "sweetalert": "^1.1.3",
    "tailwindcss": "^0.1.6",
    "underscore": "^1.8.3",
    "urijs": "^1.17.0",
    "vue": "2.*"
  },
  "devDependencies": {}
}

No customizations to tailwind.js either

Laravel 5.5
Spark 5.0.1
Also, did a fresh install of Laravel 5.5, NO SPARK, was able to follow the installation instructions with no problems at all, so there is something in the Spark config or setup, that is causing an issue...or I am thinking that is what is going on since the instructions worked correctly and pretty much only difference is Spark.
Spark uses Less for styles, where regular Laravel comes with Sass, anyone think that might have something to do with it? I will point out that I was using the Less instructions for my Spark install, and using the Sass instructions for this new standard Laravel install.

I tried the Less instructions on the tailwind page, but my experience was same as yours, Andrew.
Perhaps there is one more step or trick needed to make spark play nicely with tailwind.

The error message lead me to look at the function that "replaces" the directive with the actual code:
https://github.com/tailwindcss/tailwindcss/blob/master/src/lib/substitutePreflightAtRule.js
From the error, it looks like the code in these lines: https://github.com/tailwindcss/tailwindcss/blob/master/src/lib/substitutePreflightAtRule.js#L8-L10
atRule.before(
         postcss.parse(fs.readFileSync(`${__dirname}/../../css/preflight.css`, 'utf8'))
       )

The error says that .before is not a function. Which from the postcss site: http://api.postcss.org/AtRule.html Looks to be correct. Maybe there is a different version of postcss that is being installed?

Looking at Tailwind in node_modules in Spark install, says "postcss": "^6.0.9", but then when I go to postcss in node_modules it's version is "version": "5.2.18",
This might be our issue

@coroin Can you confirm a similar situation in your Spark install as my previous comment? Thanks in advance!

Or maybe not...looks like npm installs versions of packages that a package needs in its own node_modules folder. Looking in Spark app/node_modules/tailwindcss/node_modules/postcss   the version is 6.0.14

yes, confirmed ... my postcss versiuon in package-lock.json is 5.2.18, same as yours
there is no specific install requested in package.json, so maybe we need to install postcss explicitly?

Maybe, tried that, still getting the same thing...but I do think it is related to the version of postcss, I just can't quite figure out which one is being used.

You want the newer version of PostCSS; try manually adding that version. If
we don’t currently list it as a dependency that’s a big whoopsie, I’ll
check into that.
On Thu, Nov 9, 2017 at 6:19 PM Andrew Huggins<EMAIL_ADDRESS>wrote:

Maybe, tried that, still getting the same thing...but I do think it is
related to the version of postcss, I just can't quite figure out which one
is being used.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/tailwindcss/discuss/issues/39#issuecomment-343324202,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AEH3bE6OaoNg-5QQbDKSj7nFp8KanHanks5s04iYgaJpZM4QVTwL
.

Was able to get passed the atRule issue, the version of postcss-loader was out of date as well, so that packages postcss in its node_modules folder was the v5.x.x, so I did npm install<EMAIL_ADDRESS>(latest version for that package...and now get No PostCSS Config found

@adamwathan Which version of postcss-loader do you have?

Hmmm...Thinking it might be something with sweetalert, which an older version is installed by Spark and then its package.json requires old postcss packages, https://github.com/t4t5/sweetalert/blob/master/package.json#L56-L60

Hey there,
I installed postcss-load-config, added a postcss.config.js in the directory off the file (in my case it was a folder named less) and everything works. Kinda hacky...The config file just contains module.exports = {};
for reference this what my mix file looks like
`let mix = require('laravel-mix');
var path = require('path');
var tailwindcss = require('tailwindcss');
mix.js('resources/assets/js/app.js', 'public/js')
.less('resources/assets/less/base.less', 'public/css/dev/')
.options({
postCss: [
tailwindcss(require('./tailwind'))
]
})
.webpackConfig({
resolve: {
modules: [
path.resolve(__dirname, 'vendor/laravel/spark/resources/assets/js'),
'node_modules'
],
alias: {
'vue$': 'vue/dist/vue.js'
}
}
})
.version();`
and what my package.json looks like
{   "private": true,   "scripts": {     "dev": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",     "watch": "cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js",     "hot": "cross-env NODE_ENV=development node_modules/webpack-dev-server/bin/webpack-dev-server.js --inline --hot --config=node_modules/laravel-mix/setup/webpack.config.js",     "production": "cross-env NODE_ENV=production node_modules/webpack/bin/webpack.js --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js"   },   "dependencies": {     "axios": "^0.15.2",     "bootstrap": "^3.0.0",     "cross-env": "^3.2.3",     "jquery": "^2.1.4",     "js-cookie": "^2.1.0",     "laravel-mix": "0.*",     "moment": "^2.10.6",     "postcss-load-config": "^1.2.0",     "postcss-loader": "^2.0.8",     "promise": "^7.1.1",     "sweetalert": "^1.1.3",     "tailwindcss": "^0.1.3",     "underscore": "^1.8.3",     "urijs": "^1.17.0",     "vue": "^2.5.3"   },   "devDependencies": {} }
have you tried to add a postcss.config.js

I tried similar, it compiles, but if you look in your public/css/app.css file, does it have the @tailwind preflight; ?? Mine does. Which means it compiles, but doesn't actually bring the TailwindCss into your css. But maybe yours does?

Yeah, No I just tried recompiling and I'm getting the @tailwind preflight and such. Humm.

Welp, tried doing everything again on a fresh install of Laravel, works fine, try adding Spark, and things break as described above. Giving up on it for the night. If anyone makes some progress, please post!! This stuff looks great and would love to add it to Spark installs.

The fix is just to update Laravel Mix.
# Using npm
npm install<EMAIL_ADDRESS>
# Using Yarn
yarn add<EMAIL_ADDRESS>

@adamwathan THANK YOU!!! That gets it working.

Sounds like upgrading Laravel Mix fixes this; perhaps this issue could be closed now?

I have created a Laravel Spark Preset for tailwindcss, (https://github.com/centrality-labs/spark-tailwindcss) in case anyone needs it in future.


fix(docs): Use correct method for redirect

There is no such method .redirect() on Router. Update to correct one.

Thanks!


fixes issues on Mac

Thanks for the PR.
Can you document which version of OS an compiler this fixes for? Certainly it's true that the old code worked for macOS. I suspect it must be an environment difference between that and this.

The build causes a segmentation fault due to a null pointer. In the change log, you can see struct timespec *t; is declared but not alloc'd.


Fixed subclasses not being able to define defaults

Also fixes: http://www.deadlybloodyserious.com/2008/05/default-argument-blunders/

Changed the init function back to the way it was, but with the possibility to set default properties in subclasses. Now autocompletion in my IDE works again :)


fix: do not retry on 501

The other SDK cores skip retry for 501,
so the Node core should behave the same way.

Checklist

[x] npm test passes (tip: npm run lint-fix can correct most style issues)
[x] tests are included

@padamstx What happened to Travis?

@pyrooka

What happened to Travis?
We are working on it, not sure what happened, but updates when we have them.

:tada: This PR is included in version 2.17.14 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


what is the utility of backend='subprocess'

Hi Dear Anthony,
Thanks for your great software, I have another two quick questions that,

what is the utility of

backend='subprocess'?

Because when I using pymetamap to extract concepts, the screen will show a lot of intermediate processes, is this 'backend='subprocess'' used to make the process silent?

Is it possible to get concepts by multi-threading?

Because I am working on a pretty large dataset, thus if I extract their concepts one by one, it will take pretty long time, thus I am thinking is there any chance to use the python multi-threading feature, like this:

from multiprocessing import Pool
p = Pool(5)
def f(x):       <--------------in the function I will extract concepts
...     return x*x
...
p.map(f, [1,2,3])

Thanks a million in advance!

Hi Chao6,
The backend parameter only works with the subprocess command right now. The reason for the backend parameter is that I have future plans to wrap the complete Metamap java interface and I was trying to make sure I did not have to write the basic structure of my code. I don't have a method to make everything silent.
You should be able to use the multiprocessing concepts in python. I don't have code to do this, so you would need to write it yourself. You will probably need to close processes that take too long to run and to handle ghost processes. When I was playing with this in the past, I had issues with cleanup, but that should not be to much of a problem.

Hi, I have tried the multi-threads feature and it worked perfectly.
No goest process!
Thanks for your excellent work!

I'm glad it all worked out for you! Feel free to make a pull request if you have time ;)


Alarm card: allow "auto enter" after set number of digits

After a configured number of digits are entered, say 4, automatically call the service with the code. Allow the user to press "away", "home", etc before code is submitted and that becomes the arm type that is sent with the code.
Example config:
auto_arm_length: 4
default_auto_arm: arm_away
Example UX:
User presses "Arm home" (this changes from the default arm_away)
User presses 4 digits and after pressing the 4th digit service is called with arm_home and the 4 digits.
Text field clears, arm_away set as default button again. Card updates according to whatever state changes as it does now.

I don't think I will implement in first iteration overriding of default button from the UI. I think config should look like:
auto_arm:
  code_length: 4
  action: arm_away

I would think an auto_disarm configuration would fall within this scope as well?

I have an implementation of this. It supports both the existing UX and the "auto_arm" UX. The code is heavily refactored from the existing. It support both arm/disarm automatically when the set number of digits are entered.
I will be posting it on my GitHub account, probably tonight. There's at least one bug that I know of in my testing. I'd be just as happy if this merges with the existing, but I have not communicated with @ciotlosm about that yet.
I was going to switch auto_arm to auto_enter. I was also going to switch action to arm_action.
Feedback welcome.

I will have a look latest on Monday in more details. Sounds like a great idea and happy to get a PR for this. I'm currently away because of a big festival in town so less time to look at code with proper attention.

I will merge in master once last of TODO in dev are complete.


[feature request] add option to filter content instead of report/remove

Currently only AutoModerator and native Reddit filters can filter content to the Modqueue. Devvit apps are limited to the capabilities of the Reddit API, which only allows for reporting or removing. While the option to filter content has been requested, it seems unlikely that that feature will be added anytime soon.

See relevant Devvit issue here