Installing uv in Termux: Linux-aarch64 (by pip & curl)

Hi
In Termux, I had an issue installing: pip install uv, due to not being able to build a wheel. My python-pip is up to date with Termux repository, but Termux may be behind in packaging a new python-pip release.  All my Termux packages are up to date.
❯ pip install uv
Collecting uv
  Using cached uv-0.1.24.tar.gz (598 kB)
  Installing build dependencies ... error
  error: subprocess-exited-with-error

  × pip subprocess to install build dependencies did not run successfully.
  │ exit code: 1
  ╰─> [57 lines of output]
      Collecting maturin<2.0,>=1.0
        Using cached maturin-1.5.1.tar.gz (181 kB)
        Installing build dependencies: started
        Installing build dependencies: finished with status 'done'
        Getting requirements to build wheel: started
        Getting requirements to build wheel: finished with status 'done'
        Preparing metadata (pyproject.toml): started
        Preparing metadata (pyproject.toml): finished with status 'done'
      Building wheels for collected packages: maturin
        Building wheel for maturin (pyproject.toml): started
        Building wheel for maturin (pyproject.toml): finished with status 'error'
        error: subprocess-exited-with-error

        × Building wheel for maturin (pyproject.toml) did not run successfully.
        │ exit code: 1
        ╰─> [35 lines of output]
            /data/data/com.termux/files/usr/tmp/pip-build-env-yo2nrytm/overlay/lib/python3.11/site-packages/setuptools/config/_apply_pyprojecttoml.py:83: SetuptoolsWarning: `install_requires` overwritten in `pyproject.toml` (dependencies)
              corresp(dist, value, root_dir)
            running bdist_wheel
            running build
            running build_py
            creating build
            creating build/lib.linux-aarch64-cpython-311
            creating build/lib.linux-aarch64-cpython-311/maturin
            copying maturin/__init__.py -> build/lib.linux-aarch64-cpython-311/maturin
            copying maturin/__main__.py -> build/lib.linux-aarch64-cpython-311/maturin
            copying maturin/import_hook.py -> build/lib.linux-aarch64-cpython-311/maturin
            running egg_info
            creating maturin.egg-info
            writing maturin.egg-info/PKG-INFO
            writing dependency_links to maturin.egg-info/dependency_links.txt
            writing requirements to maturin.egg-info/requires.txt
            writing top-level names to maturin.egg-info/top_level.txt
            writing manifest file 'maturin.egg-info/SOURCES.txt'
            reading manifest file 'maturin.egg-info/SOURCES.txt'
            reading manifest template 'MANIFEST.in'
            warning: no files found matching '*.json' under directory 'src/python_interpreter'
            writing manifest file 'maturin.egg-info/SOURCES.txt'
            running build_ext
            running build_rust
            error: can't find Rust compiler

            If you are using an outdated pip version, it is possible a prebuilt wheel is available for this package but pip is not able to install from it. Installing from the wheel would avoid the need for a Rust compiler.

            To update pip, run:

                pip install --upgrade pip

            and then retry package installation.

            If you did intend to build this package from source, try installing a Rust compiler from your system package manager and ensure it is on the PATH during installation. Alternatively, rustup (available at https://rustup.rs) is the recommended way to download and update the Rust compiler toolchain.
            [end of output]

        note: This error originates from a subprocess, and is likely not a problem with pip.
        ERROR: Failed building wheel for maturin
      Failed to build maturin
      ERROR: Could not build wheels for maturin, which is required to install pyproject.toml-based projects
      [end of output]

  note: This error originates from a subprocess, and is likely not a problem with pip.
error: subprocess-exited-with-error

× pip subprocess to install build dependencies did not run successfully.
│ exit code: 1
╰─> See above for output.

note: This error originates from a subprocess, and is likely not a problem with pip.

So, I navagated to the uv GitHub repository, and tried to install it with curl, and the shell installation script:
❯ mkdir uv
mkdir: created directory 'uv'
❯ zz uv
/data/data/com.termux/files/home/uv
❯ l
❯ curl -LsSf https://astral.sh/uv/install.sh | sh
sh: 604: ldd: not found
System glibc version (`') is too old; using musl
ERROR: there isn't a package for aarch64-linux-android

I note that, there was no warning as to required dependencies in README.md, such as: lld.
So, I then checked for glibc ( aka ldd):
❯ ldd --version
zsh: correct 'ldd' to 'ld' [nyae]? n
The program ldd is not installed. Install it by executing:
 pkg install ldd
❯ pkg install ldd

The lld package installed correctly. So, I re-tried curl:
❯ curl -LsSf https://astral.sh/uv/install.sh | sh
readelf: Error: 'readlink (GNU coreutils) 9.4
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Dmitry V. Levin.': No such file
readelf: Error: 'readlink (GNU coreutils) 9.4
Copyright (C) 2023 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <https://gnu.org/licenses/gpl.html>.
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.

Written by Dmitry V. Levin.': No such file
System glibc version (`') is too old; using musl
ERROR: there isn't a package for aarch64-linux-android

I just want to successfully install uv in my host environment in Termux on Android. How should I proceed?
Any assistance is greatly apprecisted.
Thanking you in anticipation
Beauford

Thanks for the thorough report! We'll look into this, I'm not sure we support Android right now.

This is a duplicate of #2408. The relevant in the error log is "error: can't find Rust compiler", after installing rust with rustup you should get the same error as in #2408


Add support for windows container app

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[x] I adhere to the Command Guidelines.

 Is this for ignite?

- FAIL: missing_parameter_help
    Parameter: functionapp config set, `windows_fx_version` - Missing help
    Parameter: webapp config set, `windows_fx_version` - Missing help

This CI is still failing.

Ping, what's the progress?

@troydai , Ashraf is OOF.

Ok.

@jvano / @vinisoto - FYI given Ashraf is OOF ,& you want this in for the next release.

@vinisoto is added to the review. #Closed

@vinisoto will take care of it. We still want to merge for this release if possible

In reply to: 422984487 [](ancestors = 422984487)

Since Ashraf is OOF, please expect a new PR with my changes

Per @vinisoto's comments, I will close this pull request in order to prevent distractions.


Fix: Check all steps for MetaflowCode and return if any

Loops over steps of the run and return step.task.code if present.
Test flow with intermediate non-local step.
from metaflow import step, FlowSpec, conda_base, kubernetes

class HelloFlow(FlowSpec):
    @step
    def start(self):
        print("Starting 👋")
        self.next(self.eat)

    @kubernetes
    @step
    def eat(self):
        print("Eating 🍜")
        self.next(self.end)

    @step
    def end(self):
        print("Done! 🏁")

if __name__ == "__main__":
    HelloFlow()

Checking code with metadata
In [1]: from metaflow import Flow

In [2]: run = Flow("HelloFlow").latest_successful_run

In [3]: run.code
Out[3]: <metaflow.client.core.MetaflowCode at 0x7f28273010a0>

closes #1322

I have updated the docstrings for MetaflowCode and Run. I searched the repo and did not find other mentions of the requirement for Run(...).code to work.  Not sure about test cases given that steps need to run remotely.

@saikonen Any idea how to fix these "transient s3" errors, is it just rerunning them?

@saikonen Any idea how to fix these "transient s3" errors, is it just rerunning them?

usually rerunning them works, as long as the failure is not code-related. Let's see if this time we get the run to pass, but I've seen a lot of failures regarding the 5gb s3 test lately so that might need some looking into if it keeps being an issue. Not in the scope of this PR though

As a quick comment, the transient failures are by design (we "simulate" transient failures to test the retry mechanism). They should not be causing permanent failures typically and looking at the error here, it looks to be something else (not sure what though but it says Invalid Argument). A transient failure is retried up to 10 times. Here you can see that the previous test with transient failures seems to pass but the next one does not for some reason.


[Fonts styling ]

Description:
[I would like to work upon the font sizing and styling as fonts are not adding up good UI to the page.]
Reason for Change:
[I think better sizing and style will help in good user experience being a UI/UX designer i can work upon this.]
Current Styling:
[current styling has irregular distribution and size issues  and while changing the size of the screen it is not giving good impression .]
Priority Level (optional):

[ ] Low
[ X] Medium
[ ] High

Please assign this issue to me under GSSoC 2023

Can you share some screenshots

here the font size can be changed as it is covering the whole box. if we follow the whitespace rule, it will look much better.

here the text can be center aligned, it will look good.

the irregular distribution of text and alignment of para.

the color styling and font type and aize.

i can work upon the styling of 2 pages ,home and features>iskcon events page.
please assign this issue to me under GSSoC'23


[WIP] Multiple improvements, fixes and implemented missing features

This is an attempt to make this backend more complete. Please see individual commits for details.
I didn't commit for a long time when I did these changes and thus had to create commits from the huge bunch of pending changes in one go. This means that I can't guarantee that commits work on its own (I know for sure that they don't actually). Only the whole PR with all changes will work properly.
I can also not guarantee any compatibility to the old version. Especially if identifiers were stored externally or in plugins, these won't work anymore due to the way these were handled before. If compatibility is an issue, a fork of this repo might be the better solution so that it's very clear that there is no compatibility.

@vasilcovsky Did you try to go through the PR on commit level? I understand that looking at everything at once is impossible to properly review. I tried to cut commits in a way that they are at least separated by intention.
The problem is, that I started creating commits too late, which makes it impossible for me to create intermediate PRs that would work on their own.
I will go through the comments you made so far when I find time (I hope this year...). While working on my bot, I also find more stuff that needs to be modified in the backend, for example I realised that account ids are not persistent across bot registrations (everyone gets a new id when the bot is re-registered in Azure). This made me switch to using userPrincipalName for the id, which in turn required bookkeeping of urn->account mappings.
All this looks like this PR won't be ready for quite some time. I'll keep it open and change the title to include "[WIP]". I might even decide to completely ditch everything and go for a new backend that is based on the python botframework libs...depending on how much I encounter that needs to be implemented while I see that it's a lot easier in the botframework lib.

I decided a very long time ago that I'm not going to use errbot and/or botframework anymore, which means I'm unable to further support this PR. I'm closing it for this reason.


[Bug]: Error in generateTyping

What happened?
Expected a js type file to be generated.
What version of the tool are you using?
2.2.2
What version of Visual Studio Code are you running?
1.96.2
Any relevant session id from VSCode?
68ded5a7-63b3-4c58-83c0-32e666c2c6a01735666904738
Relevant log output
VSCode version: 1.96.2.
Extension version: 2.2.2.
Error occured in generateTyping command.
Error code: ERR_BAD_REQUEST.
Error message: Request failed with status code 400.
Error stack: undefined.

Found the issue - I wasn't connected to my environment.  This wasn't obvious as the connection icon was green.


group chat profile

there are 2 line normally for first and last name, but for group chats only one is needed, also maybe change the design of the profile of personal and group chats

fix design first before editing this page


Contributing on Official Website Wiki vs. In the Repo

So there are two copies of the concept of contributing to Hypatia:

Contributing on the wiki: http://hypatia-engine.github.io/wiki/contributing.html
"In the repo" meaning: CONTRIBUTING.md

I think the best approach may be to simply link to the official website wiki in the repo's contributing.md file?
Alternitively, we could just automatically update the website's wiki page BASED on the CONTRIBUTING.md file... but I feel like the developer's contributor file should be more... plaintext?
What are your thoughts on all of this?

I'm going to update CONTRIBUTING.md per our discussion on issue #75, and I believe we can write the file in such a way that it is "plain enough" to be easily read by other developers, while at the same time being formatted in Markdown in such a way that we can use a tool like Pandoc to automatically generate the wiki HTML version of that page from the Markdown document.
So my vote would be to automatically generate the wiki page from the document in the repository.  And personally I like to have as much documentation for projects available without requiring an Internet connection, e.g. I was on the road about seven hours today and being able to read all the notes and documentation in the repository was very useful since I had no Internet connection while going down the interstate.

You wouldn't even need something like Pandoc, the website is completely markdown and the website is autogenerated - all that would be required is submoduling the main repo and symlinking it in. I would say that it might be better to have it on the wiki and then if you want to read the docs just clone the website repo - again, it's all markdown, so you can just read it as is.

You wouldn't even need something like Pandoc, the website is completely markdown...

True, but the wiki may not always be hosted on GitHub or some site which automatically handles Markdown.  Regardless, I think it's a benefit to be able to easily convert documentation into as many forms and formats as possible.

What do you think about providing a Python script to handle this? Ideas? Or is this something that'd just be better handled /manually/? As in--there are perhaps some things which are more suited  to being mentioned or illustrated on the website, vs. the CONTRIBUTING.md file in the repo.

I say it's best to keep them separate just for that reason, things are better suited to one or the other and handling them manually is easy
-----Original Message-----
From: "Lillian Lemmer"<EMAIL_ADDRESS>Sent: 10/1/2015 5:06 PM
To: "hypatia-engine/hypatia"<EMAIL_ADDRESS>Cc: "Alice Jenkinson"<EMAIL_ADDRESS>Subject: Re: [hypatia] Contributing on Official Website Wiki vs. In the Repo(#76)
What do you think about providing a Python script to handle this? Ideas? Or is this something that'd just be better handled /manually/? As in--there are perhaps some things which are more suited to being mentioned or illustrated on the website, vs. the CONTRIBUTING.md file in the repo.
—
Reply to this email directly or view it on GitHub.

@alxcenz I'll trust the webmaster on this one! Closed!


Database lost on Unraid docker

I run my Spoolman docker on my Unraid server, and when I updated the the docker, all of my data went lost.
The appdata/spoolman folder is empty. Is this an issue with the docker not finding my old database, or is my database lost? If it is lost, how could I prevent it to happen again?

Correct.
Unless it was put in a persistent storage or external database, then the data is gone.

I have now put in place two measures for the next release to help reduce this issue in the future:

Spoolman will now crash with a helpful error if it doesn't have permissions to write to the data dir
A big warning will appear in the logs if you haven't mounted the data dir correctly


diagrams library not present in lts-11.0

What is the best way to find out what resulted in dropping the diagrams library from the new LTS series?
E.g. is there a specific command we can run locally to observe a build breakage (and therefore possibly contribute a fix)?

In LTS 11, we upgraded to lens-4.16, but diagrams-lib requires lens < 4.16.
It can take some getting used to in order to figure out that this was the reason, but the simplest method I can recommend is:
stack unpack diagrams
cd diagrams-1.4
echo 'resolver: lts-11.0' > stack.yaml
stack build

Note the missing dependencies, and repeat the process for each of those in turn to see why they were excluded.
Eventually you get
In the dependencies for diagrams-lib-1.4.2:
    diagrams-solve must match >=0.1 && <0.2, but the stack configuration has
                   no specified version (latest matching version is 0.1.1)
    dual-tree must match >=0.2 && <0.3, but the stack configuration has no
              specified version (latest matching version is 0.2.1)
    lens-4.16 from stack configuration does not match >=4.6 && <4.16 (latest
              matching version is 4.15.4)

A good way to find out why something has been removed is usually to grep it in Stackage's build-constraints.yaml file. In most cases there will be a comment pointing you in the right direction. However there were many removals in order to get LTS 11 out the door so I'm not confident that they were all well commented.


🐛 Bug ➾ taqueria does not properly forward error message from Michelson error message

🚥 Status (Internal Taqueria Team Use Only)

[ ] 🔬 Investigated and Verified
[ ] ⚗ Solution Identified and Designed
[ ] 🧫 Dev Implementation of Fix
[ ] 🧪 Fix Tested and Validated
[ ] 🏆 PR Merged

🆘 What happened?
TAQ_LIGO_IMAGE=ligolang/ligo:next taq compile main.jsligo
=== Error messages for main.jsligo ===
stderr maxBuffer length exceeded

===
┌─────────────┬──────────────┐
│ Contract    │ Artifact     │
├─────────────┼──────────────┤
│ main.jsligo │ Not compiled │
└─────────────┴──────────────┘

If I run with ligo
ligo compile contract ./contracts/main.jsligo

logs :
{ "id": "proto.015-PtLimaPt.michelson_v1.entrypoint_name_too_long",
  "description":
    "An entrypoint name exceeds the maximum length of 31 characters.",
  "data":
    { "name": "AAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAorgMemberRequestsUpdated" } }

🆘 Steps to Reproduce?
real issue is that the event name lenght is too long , ligo can show the actual error
Taqueria does not propagates the real error to the developer
🪵 Relevant log output
No response
🐘 How impactful is this bug?
None
⏱ Prevalance
No response
💻 Operating System
None
🕸 System Architecture
None
🌮 Taqueria Version
0.28.4
🌿 Node.js Version
No response
☎ Contact Details
No response
Code of Conduct

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

@zamrokk do you have an example contract I can use to test with please?

I couldn't repro this myself. Even with older ligo docker images. But, looking at the report, it looks like the issue stems from maxBuffer of exec'd child processes.

=== Error messages for main.jsligo ===
stderr maxBuffer length exceeded

This could be because either, node.js was older and supported a smaller stderr buffer (recent ones support 1024 * 1024 chars) or if older lima protocol was throwing a long error message.
Ref: https://nodejs.org/api/child_process.html#maxbuffer-and-unicode
@mweichert Would you like me to open a PR raising the maxBuffer limit?

I cannot reproduce either on last ligoV1 version on nairobi

I close it so


Is it possible to make such an effect of turning over?

This is a (multiple allowed):

[ ] bug

[ ] enhancement

[x] feature-discussion (RFC)

Swiper Version: Swiper 3.4.2

Platform/Target and Browser Versions: iOS, Chrome, Android

Hello ! Sorry for asking such a strange question. I spent the whole day to add it to the swiper https://codepen.io/balapa/pen/JXrjXK

Do you want to ask a question? Are you looking for support? The Swiper forum and Stack Overflow are the best places for getting support

Please, don't use GitHub issues for questions


Alternate way of reading prompts from an external file

Could an alternate version of the external prompt input be made? On progrockdiffusion (discodiffusion) I had an external file that had a list of prompts, artists, ect all on different lines that I would comment on / off to append to a single prompt once run. I personally find it way easier and faster to manage prompts this way and it would be awesome if this could be incorporated here! Also could reading from an external prompt be changed so that we don't have to initialize and reload the model every time we want to run?
Example of prompt file:
        "by Ivan Aivazovsky:2", //landscapes, ocean, ships
        //"by M.C. Escher:2",
        //"by Karol Bak:2", //feminine portraits
        //"by John Berkey:2", //sci fi ships
        //"by Zdzisław Beksiński:2", //dark dire dread
        //"by AlbertBierstadt:3", //landscapes
        //"by Johfra Bosschart:6", //landscapes, fungi, jagged

        "trending on ArtStation:3",

        //"bicycle:20",
        //"alchemy shop interior:6",
        //"ball on table:6",
        //"fantasy castle in a large field:4",
        "pastel | pretty:6",
        "forest:2",
        "river flowing through a doorway:4",
        "shrine:6",
        //"vast distant:3",
        //"stone bridge in the foreground and mountains in the background:2",
        //"river flowing down the center of a field with a castle in the distance:2",
        //"crystal coral reef:3",
        //"crystals:3",
        //"tombstones:4",
        //"a cottage in the distance:4",
        //"frozen:3",
        //"clouds:4",
        //"moon:2",
        //"mountains in the distance:4",
        //"tree roots:2",
        //"lantern:8",
        //"sacred:2",
        //"staircase:2",
        //"watercolor:2",
        //"cyberpunk:6",
        //"diorama:8",
        "godrays through the trees:6",

        "text:-30.1",

Could you point me at the documentation for this format? I think I followed it all the way to the last line, and then flipped out on "text: -30.1".

Could you point me at the documentation for this format? I think I followed it all the way to the last line, and then flipped out on "text: -30.1".

Here's the diffusion repo this prompt was used in.
Discodiffusion prompt weights worked pretty different than they currently do in SD (I have another issue opened about that). But the text:-30.1 was used to try to decrease the likelihood of artist signatures appearing in pictures. I used a float only on the text tag to make sure the weight sum never added up to 0 which would cause issues.
I cant really be more specific for the documentation because I'm not a coder, sorry lol.


fix: wait for server to stop

wait for listener thread to die

 Here is an overview of what got changed by this pull request:

Issues
======
- Added 1

See the complete overview on Codacy

 Here is an overview of what got changed by this pull request:

Complexity increasing per file
==============================
- Assets/Mirror/Runtime/Transport/Telepathy/Server.cs  1

See the complete overview on Codacy


Bug Reporter (and Feature Suggester) in organization groups?

I was thinking that there should be a Bug Reporter group, and possibly a Feature Suggester group as well, but maybe merge that with Bug Reporter.
Is it possible for me to join two groups at once?

Can we not just report bugs when we come across them though? :P

We dont really need those groups to be honest, we just need extra hands and if we come to an issue we can report them ourselves

Everyone reports bugs :P


Theme var root() not working

Hi there,
I'm trying to use the theme var root()
https://learn.getgrav.org/themes/theme-vars#root
As the Grav doc say it suppose to returns true or false based on whether or not this page is the root page of the tree hierarchy.
I tested it with {{ page.root() }} on the home page and all first parent page of my website but it always return me false.
Am I doing something wrong or it is a bug?
Thank you for your help, cheers!

You mean page.route()??? it's not page.root().

Sorry you linked to route in the URL and thought you had a typo.  root() is a valid method and should work fine:
    public function root()
    {
        if (!$this->parent && !$this->name && !$this->visible) {
            return true;
        } else {
            return false;
        }
    }

Sorry @rhukster, I understand it was confusing... I've just corrected it!

Little update from Slack: apparently I'm not the only one to have this problem.

Well, this is being used successfully in several places in Grav.  It's actually for testing the true root of the pages folder, not necessarily the top-level pages. See Page::activeChild() for example

Hi @rhukster!
I found that this solution was working for me to get top-level pages:
page.parent.root()


Rewrite LDLT code

Summary:
The LDLT code is non-idiomatic relative to the Stan code-base. It constructs an object that isn't valid and it's on the caller to verify that it's correct. This leads to more difficult testing and maintenance than necessary.
Description:
I'm finding it very difficult to test behavior of this function. We should rewrite it.
Additional Information:
The code is pretty fast. Whatever we do, we don't want to give up the speed.
Current Version:
v2.12.0

Where exactly is this LDLT code and what should the behavior be?  Do you want it to test internally and throw exceptions so that any returned result is guaranteed to be valid?

The code is here:

stan/math/rev/mat/fun/LDLT_alloc.hpp
stan/math/rev/mat/fun/LDLT_factor.hpp

The pattern is different from the way almost all of the math library code works. It can be constructed in a state where it shouldn't be usable and the client to the code needs to check an error condition to see if it was constructed correctly. I'd prefer failure on construction because there's really no recovery from that error.
So yes:

I want it to test internally
I want it to throw exceptions
I want a constructed LDLT thing to be valid and usable.

Is that closer to actionable?


Procaml Implementation

PR for the Procaml type inference algorithm implementation.

Implemented types and typedtree for Procaml. Implements an elaborated form of System F, mimicking the design of OCaml's types and typedtree modules.

The above commits implement the interfaces required for the constraint library functors.
Note: Given that Type_former essentially states that t forms an initial algebra, it might be
useful simply defining map (or a traversal function) and attempting to generate the rest.

A couple of updates.
The first constraint refactors are in!

The first one implements sized lists in the quantifier constraints (exists, forall), allowing us to safely bind n variables and match on those without using dynamic checks!
The second adds a decoding constraint that decodes a given constraint type into an output type while solving. This is required for type reconstruction on the pat_type/exp_type fields in pattern/expression respectively.

The second update is an experimental implementation of inferences of patterns using the notion of the binder (a continuation that binds n variables). I'm finding the code a bit unwieldy (really missing Haskell's do notion + type classes here).

Implemented majority of expression type inference.
We currently use a continuation monad for most of the heavy work. This works surprisingly well, but I'm not convinced it's required for infer_exp.
Current problems w/ readability are due to the clash between the applicative functor for Constraints and the monadic syntax for Continuation. Current solutions that come to mind is some form of functor/monadic transformer or a ppx for Constraints.

Latest commit completes this PR.
The implementation works, however, I expect a refactor before implementing GADTs. Mainly due to the evolving type system of this project and due to some optimizations that I think would be worth taking advantage of.
Improvements to be performed in later PRs:

Explicit sharing of types in constraints via variables. This ensures that concrete types can only be introduced using existential constructors in the constraints system. This mimic's the "shared view" of Ambivalent types and will reduce the size of the generated constraint.
Smart constructors! I believe more "peep-hole" style optimizations can be made in constraint generation using smart constructors.
Stylistic changes: infer.ml needs to be split up. Several renaming changes for consistency.
Code should reflect the theory more.
Improved handling of patterns and binders. Incorporating infrastructure for "mode checking", etc.


Remove Travis condition making test fail locally

What was the end-user problem that led to this PR?
I tried running the specs locally and I got two failures.
What was your diagnosis of the problem?
My diagnosis was that the tests were artificially only doing the right thing on Travis.
What is your fix for the problem, implemented in this PR?
My fix was to remove the condition to check whether we're in Travis or not, so that the correct assertion is made.
Why did you choose this fix out of the possible options?
I chose this fix because it works for me and it simplifies the test.

I'm having the opposite effect, this change is breaking my tests on MacOS.

Retried examples: 0

Pending: (Failures listed here are expected and do not affect your suite's status)

  1) bundle exec `load`ing a ruby file instead of `exec`ing regarding $0 and __FILE__ when the path is relative with a leading ./ relative paths with ./ have absolute __FILE__
     # Not yet implemented
     # ./spec/commands/exec_spec.rb:723

Failures:

  1) bundle exec `load`ing a ruby file instead of `exec`ing the executable exits by SignalException behaves like it runs like a normally executed executable
     Failure/Error: expect(last_command.stderr).to eq(expected_err)

       expected: "Terminated"
            got: ""

       (compared using ==)

       Commands:
       $ /Users/colby/.rubies/ruby-2.5.1/bin/ruby -I/Users/colby/Projects/bundler/lib -e  \
         <<EOS
                   require "bundler"
                   begin
                     puts Bundler.bundle_path
                   rescue Bundler::GemfileNotFound
                     ENV["BUNDLE_GEMFILE"] = "Gemfile"
                     retry
                   end

       EOS
       /Users/colby/Projects/bundler/tmp/bundled_app/.bundle/ruby/2.5.0
       # $? => 0

       $ /Users/colby/.rubies/ruby-2.5.1/bin/ruby -rrubygems -S gem --backtrace install --no-document \
         --ignore-dependencies /Users/colby/Projects/bundler/tmp/gems/remote1/gems/rack-1.0.0.gem
       Rack's post install message
       Successfully installed rack-1.0.0
       1 gem installed
       # $? => 0

       $ /Users/colby/.rubies/ruby-2.5.1/bin/ruby -rrubygems -S gem --backtrace install --no-document \
         --ignore-dependencies /Users/colby/Projects/bundler/tmp/gems/remote1/gems/rack-0.9.1.gem
       Rack's post install message
       Successfully installed rack-0.9.1
       1 gem installed
       # $? => 0

       $ /Users/colby/.rubies/ruby-2.5.1/bin/ruby \
         -I/Users/colby/Projects/bundler/lib:/Users/colby/Projects/bundler/spec -rsupport/hax \
         -r/Users/colby/Projects/bundler/spec/support/artifice/fail \
         /Users/colby/Projects/bundler/exe/bundle install --retry 0 --no-color
       Resolving dependencies...
       Bundle complete! 1 Gemfile dependency, 2 gems now installed.
       Bundled gems are installed into `./.bundle`
       Removing rack (0.9.1)
       # $? => 0

       $ RUBYOPT\=-r/Users/colby/Projects/bundler/spec/support/hax /Users/colby/.rubies/ruby-2.5.1/bin/ruby \
         -I/Users/colby/Projects/bundler/lib:/Users/colby/Projects/bundler/spec -rsupport/hax \
         -r/Users/colby/Projects/bundler/spec/support/artifice/fail \
         /Users/colby/Projects/bundler/exe/bundle exec \
         /Users/colby/Projects/bundler/tmp/bundled_app/ruby_executable arg1 arg2
       EXEC: load
       ARGS: /Users/colby/Projects/bundler/tmp/bundled_app/ruby_executable arg1 arg2
       RACK: 1.0.0
       PROCESS: /Users/colby/Projects/bundler/tmp/bundled_app/ruby_executable arg1 arg2
     Shared Example Group: "it runs" called from ./spec/commands/exec_spec.rb:570
     # ./spec/commands/exec_spec.rb:532:in `block (4 levels) in <top (required)>'

Finished in 2 minutes 16.7 seconds (files took 0.29405 seconds to load)
88 examples, 1 failure, 1 pending

Failed examples:

rspec './spec/commands/exec_spec.rb[1:26:3:1:1]' # bundle exec `load`ing a ruby file instead of `exec`ing the executable exits by SignalException behaves like it runs like a normally executed executable

@colby-swandale One question (I would try it but I don't have MacOS), what happens if you force STDOUT.flush to be run before the signal being raised, like in https://github.com/bundler/bundler/pull/6685/files#diff-c8368afb57352da544970a66e373c3edL559?

I'm not sure what change i need to make, can you post a diff?

Yeah, sorry. I was thinking
diff --git a/spec/commands/exec_spec.rb b/spec/commands/exec_spec.rb
index 492907743..b8f25cdbf 100644
--- a/spec/commands/exec_spec.rb
+++ b/spec/commands/exec_spec.rb
@@ -553,7 +553,7 @@ RSpec.describe "bundle exec" do
       let(:executable) do
         ex = super()
         ex << "\n"
-        if LessThanProc.with(RUBY_VERSION).call("1.9")
+        if LessThanProc.with(RUBY_VERSION).call("1.9") || RUBY_PLATFORM =~ /darwin/
           # Ruby < 1.9 needs a flush for a exit by signal, later
           # rubies do not
           ex << "STDOUT.flush\n"
@@ -561,7 +561,7 @@ RSpec.describe "bundle exec" do
         ex << "raise SignalException, 'SIGTERM'\n"
         ex
       end
-      let(:expected_err) { RUBY_PLATFORM =~ /darwin/ ? "" : "Terminated" }
+      let(:expected_err) { "Terminated" }
       let(:exit_code) do
         # signal mask 128 + plus signal 15 -> TERM
         # this is specified by C99

Or even just
diff --git a/spec/commands/exec_spec.rb b/spec/commands/exec_spec.rb
index 492907743..872abb0ed 100644
--- a/spec/commands/exec_spec.rb
+++ b/spec/commands/exec_spec.rb
@@ -553,15 +553,11 @@ RSpec.describe "bundle exec" do
       let(:executable) do
         ex = super()
         ex << "\n"
-        if LessThanProc.with(RUBY_VERSION).call("1.9")
-          # Ruby < 1.9 needs a flush for a exit by signal, later
-          # rubies do not
-          ex << "STDOUT.flush\n"
-        end
+        ex << "STDOUT.flush\n"
         ex << "raise SignalException, 'SIGTERM'\n"
         ex
       end
-      let(:expected_err) { RUBY_PLATFORM =~ /darwin/ ? "" : "Terminated" }
+      let(:expected_err) { "Terminated" }
       let(:exit_code) do
         # signal mask 128 + plus signal 15 -> TERM
         # this is specified by C99

Just a raw guess, probably wrong.

I had the thought that maybe the fact that the "Terminated" string is not printed is because that platform needs the STDOUT.flush as well.


Caught by ReCaptcha in headless mode

Hi there,
Thanks for this awesome project.
I am trying to scraping this page: https://www.dermstore.com/product_Glycolic+10+Renew+Overnight_79132.htm
But I am always detected as a bot when using headless mode.

Any tips?

I just tried and did not get blocked. Maybe the IP you're using has already sent too many requests ?

I found it weird because it only happens if I use the headless mode, if I use the headful mode I am not detected.
Anyway, thanks for your answer.

@cpatrickalves It because you are using the latest Chrome. see this https://github.com/towry/n/issues/148

@cpatrickalves It because you are using the latest Chrome. see this https://github.com/towry/n/issues/148


Layers switcher uses form and prevents using map inside a form

The layer switcher control adds a form to the html code.
The html specifications forbid to put a form inside another form html nesting.
So it is not possible to put a Leaflet map inside a form.
maxx

According to the HTML 5.3 specs, <input> elements may be placed in any phrasing context, i.e. outside of forms. The approach to fix this would be to just remove the form and create a block container instead.
I expect the input fields were wrapped into a form originally (this dates back 7 years ago) due to browser support, but I expect even IE9 to behave with input controls outside forms nowadays.

Is a form even semantically necessary? I mean, you POST something when you want to change the state of the server but here you're only changing thing client-side. You're only asking a server to serve you a different type of data.


Awesome! But could you please build a release exe?

@ImaginationWork  Sure, this is what you need:
https://github.com/ImplFancy/WaaCaa/releases/download/v1.0/WaaCaa.exe
https://github.com/ImplFancy/WaaCaa-Client-Cpp/releases/download/v1.0/Build.zip


Chat Rich Text Filtering and Unit Tests

This PR prevents invalid tags from breaking the rich text rendering:

Add a closing tag where one is missing
Remove a closing tag when there is no corresponding opening tag
New unit tests to validate the chat filtering

Input text:

Current rendering behavior:

Behavior with new filtering enhancement:

Unit tests:

Also, when adding this, please also add this when a user set's their name/after the bracket color format is transformed into all rich text tags as people end up breaking stuff by mixing together both rich text and the color tags.


Restructure ROM with new ROM interface API

Pull Request Description
What issue does this change request address? (Use "#" before the issue to link it, i.e., #42.)
close #1606
What are the significant changes in functionality due to this change request?

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

@PaulTalbot-INL @dylanjm This is the new PR for ROM API restructure.

All jobs on 2a71201 : invalidated by @wangcj05
testing failed case

@aalfonsi Could you take a look at this PR?

It looks like the CrossValidation node (CV) is shown as viable for all SVLs; however, since it splits the sampling space, it won't work out-of-the-box with pre-defined sampling ROMs such as the GaussPolynomial and HDMR ROM.
One solution would be to remove <CV> as an acceptable node for these SVLs in the InputSpecs setup, so it doesn't show up as acceptable in the manual.

@wangcj05  reviewed all the files...there are no "major issues" in my opinion. Just few questions.
Thank you for putting this together.

@aalfonsi @dylanjm @PaulTalbot-INL Thanks for your reviews. Let's postpone this PR until we have RAVEN 2.1 release (Target early Oct. 2021).

@wangcj05 okay. Just a FY, there are ANL folks waiting for this to be merged in order to finalize the DMDc.

I see, I will try to release our code ASAP. Mohammad would like to add some analytic tests for GA before the new release. @Jimmy-INL Have you started to work on your analytic test for GA?

I was planning to do that first week of October as we agreed. I can start today if there is change of plans.
Mohammad G. Abdo, Ph.D.
Modeling and Simulation Scientist   |  Digital Reactor Technology and Development (C160)
Reactor Systems Design and Analysis   |   NS&T
<EMAIL_ADDRESS> |  REC EROB IF-654 3EM402  |  Phone:<PHONE_NUMBER>
Idaho National Laboratory   |   2525 Fremont Ave.   |   Idaho Falls, ID   |   83415
[6GC4jc7QCCEAAAAASUVORK5CYII=]https://www.linkedin.com/in/mohammad-abdo-a7625082/.               [PXly9OZ1PK9LcRv4PSG3pAb9jevQAAAAASUVORK5CYII=] https://www.researchgate.net/profile/Mohammad_Abdo/research                 [RPr5ytnPx9Cc691m9I+4T+nIo7v4HxgxndxMwKP8AAAAASUVORK5CYII=] https://github.com/Jimmy-INL

[wYtJH347IiIiAYVYS1skEvgxC4KpkYRTFRBbsT51peEIp5j0ExRuvWouzr1J+za4DYirM+SlQmTZXUTsvjtVtouILWngWSxC+xJbAP86Fg5oVmy2ERH1w38A8nnHfeT8na8AAAAASUVORK5CYII=]
From: Congjian Wang - INL @.>
Date: Tuesday, September 28, 2021 at 10:11 AM
To: idaholab/raven @.>
Cc: Mohammad G. Abdo @.>, Mention @.>
Subject: [EXTERNAL] Re: [idaholab/raven] Restructure ROM with new ROM interface API (#1607)
@wangcj05https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fwangcj05&data=04|01|mohammad.abdo%40inl.gov|edb95c6db0c6497d874508d9829aab2b|4cf464b7869a42368da2a98566485554|0|0|637684423082610318|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=OiSlPhOMrJgbWIaYUcB194r62VykDKetSIqAlufup9w%3D&reserved=0 okay. Just a FY, there are ANL folks waiting for this to be merged in order to finalize the DMDc.
I see, I will try to release our code ASAP. Mohammad would like to add some analytic tests for GA before the new release. @Jimmy-INLhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FJimmy-INL&data=04|01|mohammad.abdo%40inl.gov|edb95c6db0c6497d874508d9829aab2b|4cf464b7869a42368da2a98566485554|0|0|637684423082610318|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=vzeTyTtxzTqRHC6yqT%2BdevzfsFyaCh0HXC03gItpZeQ%3D&reserved=0 Have you started to work on your analytic test for GA?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fidaholab%2Fraven%2Fpull%2F1607%23issuecomment-929373812&data=04|01|mohammad.abdo%40inl.gov|edb95c6db0c6497d874508d9829aab2b|4cf464b7869a42368da2a98566485554|0|0|637684423082620270|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=w08AO0RtTHSjKdyhP0zIp3goN%2FeBQcIncwNZt0OuXr0%3D&reserved=0, or unsubscribehttps://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAMP5ECS4VB3U3C37LZDBLFLUEHSMDANCNFSM5AIH3OYA&data=04|01|mohammad.abdo%40inl.gov|edb95c6db0c6497d874508d9829aab2b|4cf464b7869a42368da2a98566485554|0|0|637684423082620270|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=h1qjlZ1ERD2jBIvRjvbj5Q6OtQFP%2B%2BwDr%2BH7w4xcAwg%3D&reserved=0.

Hello,
Sorry to bother, is there any update on the merge?
Thanks, Haoyu

@PaulTalbot-INL @aalfonsi @dylanjm This PR is ready to be merged.

@wanghy-anl We have merged this PR into devel. Please let us know if you have any issue.


Web smoketest broken

I tried running it on Windows and Ubuntu. Ben tried running it on Mac. On all:

I couldn't point it to a build with --build.
The folder fails to load with "Can't resolve workspace folder"

@Tyriar also, I cannot run these tests with node 12 installed. I get an error asking to use node <=10.

They've been broken since https://github.com/microsoft/vscode/issues/80308


Fixed links in issue 63

Fixed links for https://www.lowrisc.org/docs/untether-v0.2/linux_compile/ in issue #63

Sorry, this PR somehow got lost in my inbox. Thanks!


How we handle image files in google sheet?

I would like to ask about how to handle images using Google Sheet as a database.
In the first method, I inserted the image file directly into the cell of the Google Sheet.
I expected an object return from the Google sheet like image: {path: string, id: string}, but it returned empty data.
In the second way, I put the URL of the image as string in the cell of the Google sheet.
Then, by specifying it as the value of src in the  tag, we can successfully display the image in the React component with the data retrieved from Google Sheets.

For example, how about saving an image in Google Drive and putting its URL in a Google Sheet cell?
I think this way, even a non-engineer can add and update content.
What do you think? Also, is there any other better way?

@newt0 apologies for the delayed response. your second way is the more appropriate way to handle the insertion of images, considering what this library currently supports. you can host your images wherever you like, and use the url in the db, to be passed on to the src attribute of the img tag.


gccgo compile fix and support for perfstat_cpu_util

when compiling with gccgo - for cpus < power8 i've got an error:
vendor/github.com/power-devops/perfstat/types_fs.go:130:22: error: integer constant overflow
130 |         case f.Flags&VFS_DIO != 0:
The other commit is a feature: To get the correct cpu usage of an lpar i had to call perfstat_cpu_util()
I implemented only the TotalStat, not the usage per cpu

thank you very much for the fix and the pull request!
regarding your feature request, I think it repeats the same functionality as in CpuUtilStat(). If we split CpuUtilStat() in 2 functions - one gets old CPU data (what you've done in init()) and the second calculates the difference (your CpuUtilTotalStat()), and then you can use the first function whenever you need it to start counting, would it suit your needs?
Not everyone uses libperfstat to get CPU data from it and that is my problem with init(). Why should we save some data in a global variable for a possible future use?


Fix build of Jupyter extension and test that it works

If you look in the build logs of the current 0.6.1 package, there's an error in the pip install command because npm isn't available. Somewhat annoyingly, this error doesn't actually cause the installation to exit with an error.
However, this PR doesn't bump the build number because the 0.6.1 release tarball doesn't contain the files needed to actually build the JavaScript files, so we still can't install the extension successfully. We'll need a new ipyevents tarball for that to work.

Checklist

[x] Used a fork of the feedstock to propose changes
[ ] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks @pkgw, I released 0.6.2 with your fixes and updated this recipe to point at that version, merging!


Port Buzzwords to Ruby

I've tried to follow Jeff Jetton's lead with the comments and
suggestions for improvement in the Python port.

Fantastic! Thank you! 🙌


DROPZONE_MAX_FILE_EXCEED

Change:
"Your can't upload any more files."
"You can't upload any more files."

Also, replace the token in dropzone.config(max_file_exceed='New label') doesn't work for this attribute. Only with app.config['DROPZONE_MAX_FILE_EXCEED'] = 'New label'

Fixed, thanks!


FEAT-#2520: add most important operations for asv benchmarks

Signed-off-by: Anatoly Myachev<EMAIL_ADDRESS>
What do these changes do?

Removed extra code: pd.DEFAULT_NPARTITIONS = CpuCount.get(). To manipulate the number of partitions, it is enough to define MODIN_CPUS env variable.
Unified datasets for binary and unary operations:

For binary operations added a more general case of source data when left.shapes != right.shapes
By default, the comparison with Pandas is removed to save resources. To get the results of the pandas, just override ASV_USE_IMPL="pandas" variable in sources.
Removed all tests that, for various combinations of parameters, fall back to the pandas implementation.


Is there any way to protect only a specific path?

I would like to protect only my /api/ path, this means that I want to protect the GET method also
If I don't ignore the GET method, the csrf token will not be created and inserted in the header of a normal page.
How to work around this?

You can selectively enable edge-csrf only for certain routes in the middleware file:
// middleware.ts

import csrf from 'edge-csrf';
import { NextResponse } from 'next/server';
import type { NextRequest } from 'next/server';

// initalize protection function
const csrfProtect = csrf({
  cookie: {
    secure: process.env.NODE_ENV === 'production',
  },
});

export async function middleware(request: NextRequest) {
  const response = NextResponse.next();

  if request.url.startsWith('/api/') {
    // csrf protection
    const csrfError = await csrfProtect(request, response);

    // check result
    if (csrfError) {
      return new NextResponse('invalid csrf token', { status: 403 });
    }
  }

  return response;
}

This solution is url based so it will run both GET and POST requests through the edge-csrf middleware.

The problem with this code is that I need to protect my GET api routes and if you execute this code, the other pages will not create the csrfToken to pass to my api route.

You might be able to hack together a solution with edge-csrf but this library is designed to generate CSRF tokens on GET's and validate them on POST's so it doesn't sound like it will work for you. Are you sure there isn't a way to use POST handlers on your API routes?

These API routes are only to get some data, so I don't think using POST is a good idea.
If the owner could not give me a solution I will try to find another package :(

OWASP guidance is to consider GET, HEAD, and OPTIONS as safe methods that do not need to be appended with a CSRF token and POST, PUT, PATCH, and DELETE methods, as state changing verbs that should have a CSRF token attached to the request. If you're using javascript you can use fetch() to send data via POST easily.

You can selectively enable edge-csrf only for certain routes in the middleware file:
// middleware.ts

import csrf from 'edge-csrf';
import { NextResponse } from 'next/server';
import type { NextRequest } from 'next/server';

// initalize protection function
const csrfProtect = csrf({
  cookie: {
    secure: process.env.NODE_ENV === 'production',
  },
});

export async function middleware(request: NextRequest) {
  const response = NextResponse.next();

  if request.url.startsWith('/api/') {
    // csrf protection
    const csrfError = await csrfProtect(request, response);

    // check result
    if (csrfError) {
      return new NextResponse('invalid csrf token', { status: 403 });
    }
  }

  return response;
}

This solution is url based so it will run both GET and POST requests through the edge-csrf middleware.

Hello, do this also apply if I only need to have the edge-csrf enabled on api routes. I have supabase and I don't need the csrf but only on the api routes alone.

Hello, do this also apply if I only need to have the edge-csrf enabled on api routes. I have supabase and I don't need the csrf but only on the api routes alone.

If you only want to apply it to API routes then you can use the same strategy but looking the code again I would suggest doing this instead in order for the cookie to get set on non-api GET requests:
export async function middleware(request: NextRequest) {
  const response = NextResponse.next();

  // csrf protection
  const csrfError = await csrfProtect(request, response);

  // check result
  if (csrfError && request.url.startsWith('/api/')) {
    return new NextResponse('invalid csrf token', { status: 403 });
  }

  return response;
}


More dependency updates

Scala steward not updating a few dependencies
Found a few dependencies scala steward may not have caught.
Found with mill mill.scalalib.Dependency/showUpdates
Some are quite new

fansi 0.4.0, 2 days ago (which in fact has been picked up by Scala Steward, so I remove it from the PR)

some are quite a bit older

scalafmt-dynamic 3.4.3 (feb 2022) -> 3.5.8 (jun 2022). Both 2.12/2.13 compatible. mvnrepository.com

I don't see anything intentionally pinning the scalafmt-dynamic update to an older version in .scala-steward.conf.
This bit of the PR aims to give a bit of data to help with https://github.com/scala-steward-org/scala-steward/issues/2664

Update a few hidden dependencies
My local test/compilation was also failing on JDK17. I found a few "hidden" dependencies that Scala-steward wouldn't find in the contrib modules, like proguard and scala-parser-combinators (the latter should let latest twirllib work, on Scala 2.13).

https://github.com/cbeust/testng/blob/master/CHANGES.txt
7.6.0 Fixed: GITHUB-2637: Upgrade to JDK11 as the minimum JDK requirements (Krishnan Mahadevan), reverted this upgrade.

Hi @IdiosApps, I really appreciate your efforts to bump dependencies. I'd prefer to submit bumps in dedicated pull requests (unless they are required for a special feature). This allows us to better track their impact and isolate issues. Also, most of them are automatically bumped by Scala Steward, and some are simply incompatible. When done in separate PRs, is't easier to find previous (historic) issues, findings and dicissions.

Hi @IdiosApps, I really appreciate your efforts to bump dependencies. I'd prefer to submit bumps in dedicated pull requests (unless they are required for a special feature). This allows us to better track their impact and isolate issues. Also, most of them are automatically bumped by Scala Steward, and some are simply incompatible. When done in separate PRs, is't easier to find previous (historic) issues, findings and dicissions.

Sure. The PR kind of changed into something more useful as I tried to fix CI jobs. I can split out updates scala steward would never hit (proguard, twirrlib, flway?) into their own PRs

This has now all been split out. Closing the PR, thanks.


Btccomapi converter

Transforming the btccom api to blocktrail api format

Coverage increased (+1.3%) to 68.459% when pulling 179d8a5c1278542109738a9cc7f6330a4d01d162 on btccomapi into 3f33f1e83e16b813148ac817ac34f60a5157eef5 on master.


Request: Add Callback Prop for playing event

Thanks in advance for your awesome suggestion of new feature for this library.
Is your feature request related to a problem? Please describe.
If I am not mistaken, the playing event can be used to detect if the buffering process has ended.
Here is the official description of the event:

The media is no longer blocked from playback and has started playing.

I need that feature for tracking purposes. Right now, there is only onWaiting prop that can be used to detect if the video starting to buffer. Thanks
Describe the solution you'd like
Add onPlaying props for playing event in videoJs player
Describe alternatives you've considered

Additional context

Hi, and it's nice to see who uses this library!
I was late for checking you open this issue, and thank you for your work.


Add and configure tracee to our local minikube setup for debugging

https://github.com/aquasecurity/tracee

https://github.com/aquasecurity/tracee/blob/main/docs/tutorials/setup-development-machine-with-vagrant.md
https://github.com/aquasecurity/tracee/blob/main/docs/install/kubernetes.md
https://github.com/aquasecurity/postee


Moved GranadaLayout to /Layout

Project URL

https://github.com/gskbyte/GranadaLayout
Category

/Layout
Description

An alternative layout system for iOS

          1 Warning

:warning:
Found 2 link issues, a project collaborator will take care of these, thanks :)

Link issues by awesome_bot

Line
Status
Link

2843
Error
https://www.natashatherobot.com/  Connection timed out - connect(2) for "www.natashatherobot.com" port 443

2877
302
http://www.ios-blog.co.uk/ redirects tohttp://www.ios-blog.co.uk/cgi-sys/suspendedpage.cgi

  Generated by :no_entry_sign: Danger


test(k8s): Correct prometheus template

The original template prometheus.yaml was changed as part of
https://github.com/cilium/cilium/pull/6706.
Update path to point to monitoring-example.yaml instead.
Closes #11522
Signed-off-by: Tam Mach<EMAIL_ADDRESS>Correct prometheus template in integration test

Coverage decreased (-0.02%) to 37.073% when pulling 4f58ea45e27675f1d9650158870234db53d13193 on sayboras:bugfix/fix-prometheus-path into 157632f617083f67481a1c2c024b68f8da805d7d on cilium:master.


[Event Request] COD 80 / 90 - CalcDeferralAmounts - OnBeforeTempDeferralLineInsert

In COD 80 and 90, function CalcDeferralAmounts, we would like to include the description of the purchase line and deferral no vs the total no. of deferrals (e.g. 1/12) as part of the deferral description. To achieve this, we customized the TempDeferralLine.description. Not the most elegant way, but at least here we got access to DeferralCount and TotalDeferralCount
..
        //NVTBE/Deferral description from original line description
        TempDeferralLine.Description := COPYSTR(NVTBETools.StringReplace(DeferralLine.Description,'%99',PurchLine.Description),1,MAXSTRLEN(TempDeferralLine.Description));
        //NVTBE/Deferral description with No. of deferral mentioned
        TempDeferralLine.Description := COPYSTR(NVTBETools.StringReplace(TempDeferralLine.Description,'%98',STRSUBSTNO('%1/%2',DeferralCount,TotalDeferralCount)),1,MAXSTRLEN(TempDeferralLine.Description));

        >> Add OnBeforeTempDeferralLineInsert here
        TempDeferralLine.INSERT;
      UNTIL NEXT = 0;
...

Can you provide an OnBeforeTempDeferralLineInsert event with VAR access to TempDeferralLine, as well as access to PurchLine (cod 90), SalesLine (cod 80) DeferralCount, TotalDeferralCount?
An alternative solution might be to already set the description in COD 1720 where 'CreateRecurringDescription' is called. However, this misses the 'Period No' vs 'Total Periods'. Would be interesting if we could subscribe to 'OnAfterCreateRecurringDescription' as well, with access to 'PeriodicCount' + total no. of periods.

We already have event here OnBeforeTempDeferralLineInsert(TempDeferralLine,DeferralLine,SalesLine,DeferralCount,TotalDeferralCount);


Create trinity-college-dublin.md

New entry for Trinity College Dublin

Yes, this adds it. But there's no content. Do you have that?

This is a work in progress - hold off on emerging for now

PLease merge if you think it looks OK (and I'll do a little dance! :)

Merged. :)


Make the file extract more inclusive.

Given that mimetype is not reliable in general:
Added check for application/octet-strea mimetype too.
Added check for .txt extension.

#161


Don't save space for a burger icon when drawer is fixed (fixes #1032)

That commit message made me hungry.
Before:

After:

Good thing I just had lunch.
lgtm

Lgtm


Desktop notifications Ubuntu?

Is this a planned feature or should they work already?

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/28634759-desktop-notifications-ubuntu?utm_campaign=plugin&utm_content=tracker%2F19476668&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F19476668&utm_medium=issues&utm_source=github).

They work already (tested this).


peer dependency conflict between @langchain/community and langchain on pupeeter

Checked other resources

[X] I added a very descriptive title to this issue.
[X] I searched the LangChain.js documentation with the integrated search.
[X] I used the GitHub search to find a similar question and didn't find it.
[X] I am sure that this is a bug in LangChain.js rather than my code.
[X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

Example Code
Run this command to reproduce:
npm i langchain@latest @langchain/community@latest

Error Message and Stack Trace (if applicable)
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/puppeteer
npm ERR!   dev<EMAIL_ADDRESS>from the root project
npm ERR!   peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   node_modules/@langchain/community
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!     peerOptional @langchain/community@"*" from<EMAIL_ADDRESS>npm ERR!     node_modules/langchain
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR!       2 more (@langchain/community, @getzep/zep-cloud)
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peerOptional<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR! node_modules/langchain
npm ERR<EMAIL_ADDRESS>from the root project
npm ERR<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   1 more (@getzep/zep-cloud)

Description
When using latest langchain and community packages, there's a peer dependency conflict around the pupeeter package version.
My langchain versions:
<EMAIL_ADDRESS><EMAIL_ADDRESS>
System Info
npm list langchain @langchain/community
<EMAIL_ADDRESS>/Users/sinedied/projects/serverless-chat-langchainjs
└─┬<EMAIL_ADDRESS>-> ./packages/api
  ├─┬<EMAIL_ADDRESS>  │ ├──<EMAIL_ADDRESS>deduped
  │ └─┬<EMAIL_ADDRESS>  │   └──<EMAIL_ADDRESS>deduped
  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>deduped

npm i -v
10.8.2

I am also struggling with this bug today...
Had to add --legacy-peer-deps flag to workaround the issue and keep developing, but this is not acceptable for production...


Issues following tutorial

Hi!
I'm attempting to implement your bls package, but have run into an error while following the tutorial you uploaded. When attempting to import bls, Python returns:

from bls import BLS

Traceback (most recent call last):
File "<pyshell#21>", line 1, in
from bls import BLS
File "/run/media/thomson/920A-4120/MASCARA/bls/init.py", line 14, in
from .core import BLS, BLSResults
File "/run/media/thomson/920A-4120/MASCARA/bls/core.py", line 11, in
from . import methods
File "/run/media/thomson/920A-4120/MASCARA/bls/methods.py", line 8, in
from ._impl import bls_impl
ImportError: No module named _impl
I've tried looking into the files to see if I can resolve the issue, but to no avail. Any chance you can update the file or indicate what I need to change in order to make it work?
Thanks in advance!

I'd recommend trying out the development version of astropy because there's a better implementation (based on this one) there: https://astropy.readthedocs.io/en/latest/stats/bls.html
But, if you definitely want to use this, you're probably getting that error because you're trying to run within the git directory and the compiled extension isn't in the right place. To fix that you'll need to install using python setup.py develop or python setup.py build_ext --inplace.

Hi Dan,
Thanks for getting back to me! I'll give the Astropy option a go first, and
see how I go. I honestly didn't think there it had a BLS class which was
confirmed, or at least I thought, by doing a quick google search.
Thanks again!
Keegan
On Wed, Nov 14, 2018 at 12:30 AM Dan Foreman-Mackey <
<EMAIL_ADDRESS>wrote:

I'd recommend trying out the development version of astropy because
there's a better implementation (based on this one) there:
https://astropy.readthedocs.io/en/latest/stats/bls.html
But, if you definitely want to use this, you're probably getting that
error because you're trying to run within the git directory and the
compiled extension isn't in the right place. To fix that you'll need to
install using python setup.py develop or python setup.py build_ext
--inplace.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/dfm/bls.py/issues/5#issuecomment-438478442, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AK44cPJUHDm8zWOAvntJ4hyAMjpq9tqiks5uu1YLgaJpZM4YcXFP
.


TestCafe cursor is not visible

Are you requesting a feature or reporting a bug?
Bug
What is the current behavior?
TestCafe mouse cursor is not visible when performing actions.
What is the expected behavior?
TestCafe mouse cursor should be visible when performing actions.
How would you reproduce the current behavior (if this is a bug)?
Run any test
Specify your

operating system: Ubuntu 14.04, Windows 10
testcafe version: 0.12.0
node.js version: 7.2.0

https://github.com/DevExpress/testcafe/commit/1cb440a956f32798a7afb526d62ca876566386e0


Add datafusion-python

This is a PR with the source code of python-datafusion, currently available at https://github.com/jorgecarleitao/datafusion-python and released in pypi as datafusion.
The goal of this PR is to gauge interest of moving that code base closer to datafusion and to within ASF.
Some notes:

The documentation is lacking, but I would hope to have the docs published somewhere via readthedocs.
The release builds wheels for windows, mac, and manylinux2010, which cover some of the user-base

Codecov Report

Merging #69 (5fc75a0) into master (9ba214a) will decrease coverage by 0.54%.
The diff coverage is 0.00%.

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

Thank you @jorgecarleitao I am really excited to see this and would love to see this merged into arrow-datafusion.

Some notes:

this points to a rather old commit in DataFusion. We need to work on that
the CI did not run for some reason; I need to fix that
I need to push the Apache license and headers to flag that this is being licensed to ASF via Apache 2 and not MIT

Ok, I have now fixed the CI, pushed the license headers, and bumped to latest datafusion.
There was a regression, documented in #226.
Once we fix the regression, this can be released in pypi as 0.2.2 since there were no backward incompatible changes on it 🎉

@alamb @Dandandan Any objection to merging this PR?

@andygrove please go ahead 🚀

I hate to be a nuisance, but didn't this need to go through IP clearance?

I hate to be a nuisance, but didn't this need to go through IP clearance?

We can revert if this is the case, but because Jorge was the only contributor (except for one contribution fixing a typo in a README) this didn't seem to be required in this case?

Probably best to check with general@incubator to determine the preferred protocol in this situation. I don't want to subject you to unneeded process, but would be good to go by the book

@wesm thank you. Not a nuisance at all, it is important to have this done correctly.
The rational here:
I hold the copyright over the whole code base, except for a 1 word typo fix on the README. The code was MIT licensed on jorgecarleitao/python-datafusion.
As part of this PR, I pushed a commit that added the license headers to every file in the source code. As copyright holder, I thereby licensed all this code to ASF under the ICA.

PR to revert: https://github.com/apache/arrow-datafusion/pull/257

Thanks, I'm not enough of an expert to know what is the correct protocol, a vote may not be needed at all but let's double check

Yeah, my interpretation was that since @jorgecarleitao  authored this code, I was treating this as "just a normal PR" (it happens to have lived somewhere else for a while but from an IP provenance perspective it seemed no different to a normal PR to me).
However, I am not an expert in such matters.


Tokens: New disabled token for text and icons

Summary
Added disabled text and icon token and updated the Color docs.
What changed?
Added disabled token to the base.js file. And updated the color Usage page to reflect the new token. Also re-worded the typography section to match the style of the rest of the doc.

Why?
A color that looks more disabled than our subtle color is needed. Subtle is for secondary text, but there is a conflict when there is a subhead or helper text in a subtle color on the page, then also a disabled element with the same color. Android and iOS devs also need the token so they can implement on their end.
Links

Jira
Figma

Checklist

[x] Added unit and Flow Tests
[x] Added documentation + accessibility tests
[x] Verified accessibility: keyboard & screen reader interaction
[x] Checked dark mode, responsiveness, and right-to-left support
[ ] Checked stakeholder feedback (e.g. Gestalt designers)

Re a11y test, on the page add
await expectAccessiblePage({
    page,
    rules: {
      'color-contrast': { enabled: false },
    },
  });

We should fix this in a more targeted way.

Re Prettier,
Install in VScode https://marketplace.visualstudio.com/items?itemName=esbenp.prettier-vscode
The cmd + Shift + P ==> Format document (force)

Also, can we run this through the meeting w/ engs?
Why?
We should not add a token and document it but not add it to Text, Button, etc.
I think this kind of changes need to be passed by eng so we can evaluate the best way of implementing them.
We could merge and document this, but then there would be no way of accessing them

Let's meet first. I've added it to the agenda for next Monday. Sorry, wasn't sure if we could add tokens and then handle applying it later.


Enable TagPolicy in LZA for GovCloud

Describe the bug
Attempting to apply an Organization tag policy fails during the Organization action in CodePipeline. The same tag policy attaches to the same OU when done manually in the AWS Console.
To Reproduce
Create a JSON tag policy in LZA and define a TaggingPolicyConfig object in the GovCloud LZA configuration. Commit the change and when the CodePipeline reaches the Organization action the following error occurs:
taggingPolicies:
  - name: OrganizationPolicy
    description: Organization Tagging Policy
    policy: tagging-policies/org-tag-policy.json
    deploymentTargets:
      organizationalUnits:
        - Infrastructure

{
    "tags": {
        "Team": {
            "tag_key": {
                "@@assign": "Team"
            },
            "tag_value": {
                "@@assign": [
                    "sysops",
                    "dbops",
                    "webops"
                ]
            },
            "enforced_for": {
                "@@assign": [
                    "ec2:instance"
                ]
            }
        },
        "Name": {
            "tag_key": {
                "@@assign": "Name"
            },
            "tag_value": {
                "@@assign": []
            }
        },
        "Owner": {
            "tag_key": {
                "@@assign": "Owner"
            },
            "tag_value": {
                "@@assign": []
            }
        },
        "Cluster": {
            "tag_key": {
                "@@assign": "Cluster"
            },
            "tag_value": {
                "@@assign": [
                    "gov",
                    "govdev",
                    "govstg"
                ]
            }
        },
        "Environment": {
            "tag_key": {
                "@@assign": "Environment"
            },
            "tag_value": {
                "@@assign": [
                    "production",
                    "staging",
                    "development",
                    "il4"
                ]
            }
        },
        "CostCenter": {
            "tag_key": {
                "@@assign": "CostCenter"
            },
            "tag_value": {
                "@@assign": [
                    "datacenteroperations"
                ]
            }
        }
    }
}

AWSAccelerator-OrganizationsStack-<redacted_org_id>-us-gov-east-1 \| 11:12:32 PM \| CREATE_FAILED        \| Custom::EnablePolicyType                          \| enablePolicyTypeTag/Resource/Default (enablePolicyTypeTagB9F93488) Received response status [FAILED] from custom resource. Message returned: Error: Policy Type TAG_POLICY not supported.
--
363 | at pm (/var/task/index.js:32:17362)
364 | at Runtime.handler (/var/task/__entrypoint__.js:1:938)
365 | at Runtime.handleOnceNonStreaming (file:///var/runtime/index.mjs:1016:29) (RequestId: 009e19f2-59b8-4104-be58-b0683134dc7f)
366 | new CustomResource (/codebuild/output/src3334/src/s3/00/source/node_modules/aws-cdk-lib/core/lib/custom-resource.js:1:823)
367 | \_ new EnablePolicyType (/codebuild/output/src3334/src/s3/00/source/packages/@aws-accelerator/constructs/lib/aws-organizations/enable-policy-type.ts:88:22)
368 | \_ OrganizationsStack.addTaggingPolicies (/codebuild/output/src3334/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/organizations-stack.ts:599:35)
369 | \_ new OrganizationsStack (/codebuild/output/src3334/src/s3/00/source/packages/@aws-accelerator/accelerator/lib/stacks/organizations-stack.ts:164:10)
370 | \_ main (/codebuild/output/src3334/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:572:35)
371 | \_ processTicksAndRejections (node:internal/process/task_queues:96:5)
372 | \_ async /codebuild/output/src3334/src/s3/00/source/packages/@aws-accelerator/accelerator/bin/app.ts:1017:5

Expected behavior
I expected my organization tag policy to be successfully enabled and attached to the OU I specified as this works when done manually in the AWS Console.
Please complete the following information about the solution:

[ ] Version: [v1.4.2]
[ ] Region: [e.g. us-gov-east-1] (The action fails after attempting in this region.
[ ] Was the solution modified from the version published on this repository? Yes
[ ] If the answer to the previous question was yes, are the changes available on GitHub? No
[ ] Have you checked your service quotas for the services this solution uses? No
[ ] Were there any errors in the CloudWatch Logs? Yes. Only what I see in the CodePipeline output for the Organization action.

Hello, thank you for creating this issue! I have added this feature request to the team's backlog, I will update this issue accordingly. Thank you again for your interest in the Landing Zone Accelerator on AWS.

Hello,
This fix was implemented as part of our v1.5.0 release. Please update at your convenience and you will be unblocked from this error.
Thank you for your support of the LZA solution!

After updating to v1.5.2 this still happens:
`

AWSAccelerator-OrganizationsStack-125656955281-us-gov-west-1 | 15/22 | 1:41:25 AM | CREATE_FAILED        | Custom::EnablePolicyType                          | enablePolicyTypeTag/Resource/Default (enablePolicyTypeTagB9F93488) Received response status [FAILED] from custom resource. Message returned: Error: Policy Type TAG_POLICY not supported.

180

181

182

183

184

185

186

187

188

189

190

191

`
`taggingPolicies:
This Tag policy is already manually applyed due to LZA solution bug:
https://github.com/awslabs/landing-zone-accelerator-on-aws/issues/191

name: tagging-policy
description: Organization Tagging Policy
policy: tagging-policies/org-tag-policy.json
deploymentTargets:
organizationalUnits:
- Root`


Hello i m having issue in flutter with ios

when i create fresh new project, then working smoothly,
but when i copy from project my window to mac ,  and run flutter command  flutter run.
i m getting the following issues, i m not sure hw to resolved these ?
DU243170:fffdesign admin$ flutter run
Launching lib/main.dart on iPhone 11 in debug mode...
Running pod install...                                              4.2s
CocoaPods' output:
↳
      Preparing

    Analyzing dependencies

    Inspecting targets to integrate
      Using `ARCHS` setting to build architectures of target `Pods-Runner`: (``)

    Fetching external sources
    -> Fetching podspec for `Flutter` from `Flutter`
    -> Fetching podspec for `flutter_braintree` from `.symlinks/plugins/flutter_braintree/ios`
    -> Fetching podspec for `flutter_country_picker` from
    `.symlinks/plugins/flutter_country_picker/ios`
    -> Fetching podspec for `flutter_facebook_login` from
    `.symlinks/plugins/flutter_facebook_login/ios`
    -> Fetching podspec for `flutter_keyboard_visibility` from
    `.symlinks/plugins/flutter_keyboard_visibility/ios`
    -> Fetching podspec for `google_sign_in` from `.symlinks/plugins/google_sign_in/ios`
    -> Fetching podspec for `google_sign_in_web` from `.symlinks/plugins/google_sign_in_web/ios`
    -> Fetching podspec for `shared_preferences` from `.symlinks/plugins/shared_preferences/ios`
    -> Fetching podspec for `shared_preferences_macos` from
    `.symlinks/plugins/shared_preferences_macos/ios`
    -> Fetching podspec for `shared_preferences_web` from
    `.symlinks/plugins/shared_preferences_web/ios`

    Resolving dependencies of `Podfile`
      CDN: trunk Relative path: CocoaPods-version.yml exists! Returning local because checking is
      only perfomed in repo update
    [!] CocoaPods could not find compatible versions for pod "flutter_braintree":
      In Podfile:
        flutter_braintree (from `.symlinks/plugins/flutter_braintree/ios`)

    Specs satisfying the `flutter_braintree (from `.symlinks/plugins/flutter_braintree/ios`)`
    dependency were found, but they required a higher minimum deployment target.

    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:328:in
    `raise_error_unless_state'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:310:in `block in
    unwind_for_conflict'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:308:in `tap'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:308:in
    `unwind_for_conflict'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:684:in
    `attempt_to_activate'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:254:in
    `process_topmost_state'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolution.rb:182:in `resolve'
    /Library/Ruby/Gems/2.6.0/gems/molinillo-0.6.6/lib/molinillo/resolver.rb:43:in `resolve'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/resolver.rb:94:in `resolve'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer/analyzer.rb:1065:in
    `block in resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/user_interface.rb:64:in `section'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer/analyzer.rb:1063:in
    `resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer/analyzer.rb:124:in
    `analyze'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer.rb:410:in `analyze'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer.rb:235:in `block in
    resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/user_interface.rb:64:in `section'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer.rb:234:in
    `resolve_dependencies'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/installer.rb:156:in `install!'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/command/install.rb:52:in `run'
    /Library/Ruby/Gems/2.6.0/gems/claide-1.0.3/lib/claide/command.rb:334:in `run'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/lib/cocoapods/command.rb:52:in `run'
    /Library/Ruby/Gems/2.6.0/gems/cocoapods-1.9.3/bin/pod:55:in `<top (required)>'
    /usr/local/bin/pod:23:in `load'
    /usr/local/bin/pod:23:in `<main>'

Error output from CocoaPods:
↳

    [!] Automatically assigning platform `iOS` with version `8.0` on target `Runner` because no
    platform was specified. Please specify a platform for this target in your Podfile. See
    `https://guides.cocoapods.org/syntax/podfile.html#platform`.

Error running pod install
Error launching application on iPhone 11.
DU243170:fffdesign admin$

Hi @atta1234
First clean your project with flutter clean and open ios folder in terminal and execute pod init, pod install and pod update. Make sure you've iOS configuration for your packages
After this if the problem persist, Can you please provide your flutter doctor -v your flutter run --verbose and code smaple
Thank you

nothing work still same issue

Hi @atta1234
Please provide the details https://github.com/flutter/flutter/issues/60857#issuecomment-654085615
Thank you

sir i use online mac https://www.macincloud.com/, i can give the login details, everything is installed, and my project is on desktop,

here is the error of commands you said,
The default interactive shell is now zsh.
To update your account to use zsh, please run chsh -s /bin/zsh.
For more details, please visit https://support.apple.com/kb/HT208050.
DU243170:ios admin$ pod init
[!] Existing Podfile found in directory
DU243170:ios admin$ pod install
[!] Invalid Podfile file: Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first.
from /Users/admin/Desktop/fffdesign/ios/Podfile:51
-------------------------------------------
unless File.exist?(generated_xcode_build_settings_path)

   raise "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first"

end
-------------------------------------------
DU243170:ios admin$ pod install
[!] Invalid Podfile file: Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first.
from /Users/admin/Desktop/fffdesign/ios/Podfile:51
-------------------------------------------
unless File.exist?(generated_xcode_build_settings_path)

   raise "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first"

end
-------------------------------------------
DU243170:ios admin$

The default interactive shell is now zsh.
To update your account to use zsh, please run `chsh -s /bin/zsh`.
For more details, please visit https://support.apple.com/kb/HT208050.
DU243170:ios admin$ pod init
[!] Existing Podfile found in directory
DU243170:ios admin$ pod install

[!] Invalid `Podfile` file: Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first.

 #  from /Users/admin/Desktop/fffdesign/ios/Podfile:51
 #  -------------------------------------------
 #      unless File.exist?(generated_xcode_build_settings_path)
 >        raise "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first"
 #      end
 #  -------------------------------------------
DU243170:ios admin$ pod install

[!] Invalid `Podfile` file: Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first.

 #  from /Users/admin/Desktop/fffdesign/ios/Podfile:51
 #  -------------------------------------------
 #      unless File.exist?(generated_xcode_build_settings_path)
 >        raise "Generated.xcconfig must exist. If you're running pod install manually, make sure flutter pub get is executed first"
 #      end
 #  -------------------------------------------
DU243170:ios admin$

Hi @atta1234
Looks like an issue with your. pod file
Please try
$  brew upgrade ruby
$  gem uninstall cocoapods
$  gem install cocoapods

and then delete pod files from your ios folder of your project then execute following root of your ios folder
pod init
pod install
pod update
try running the app now with flutter run --verbose
After trying this if problem persist and please try new project
Thank you

the issue was with braintree sdk i removed that, and clean rerun it works

Hi  @atta1234
given your last message I feel safe to close this issue, if you disagree please write in the comments and I will reopen it.
Thank you


No supported encrypter found. The cipher and / or key length are invalid after install

I am getting the error "No supported encrypter found. The cipher and / or key length are invalid". I have tried regenerating my key and nothing seems to work.

You need to clear the config cache after generating.


feat: [#6865] Provide two new invoke handlers, (message/fetchTask, message/submitAction) for Custom Feedback Loops

Fixes #6865
Description
This PR introduces two new Teams handlers, submitAction and fetchTask, alongside with the respective feedback loop classes.
Specific Changes

Added submitAction and fetchTask handlers for teams.
Added new classes for strong-type the new handlers' data.
Added new class for TeamsChannelData to enable feedback loops.
Added unit tests for the new handlers.

Testing
The following image shows a teams sample working with the new submitAction handler, fetchTask couldn't be tested since it is only available in ring0.

@jk-msft, @sw-joelmut , Can some text be included in the TeamsActivityHandler OnTeamsMessageFetchTaskAsync and OnTeamsMessageSubmitActionAsync response are?

@jk-msft, @sw-joelmut , Can some text be included in the TeamsActivityHandler OnTeamsMessageFetchTaskAsync and OnTeamsMessageSubmitActionAsync response are?

Thanks for the feedback, we added the "returns" documentation and improved the summary for the FetchTask, adding code examples for Adaptive Cards and website URL (extracted from the issue information) so the customer knows what should be returned.

The SubmitAction didn't require any update, since it doesn't require any value to be returned by a customer (it returns void).


Remember interface DPI settings

I've compiled Shadered 1.3.4 on Ubuntu 20.04 on a Dell XPS 13 laptop. When I launch the application the interface is scaled too large.

I can untick the DPI aware button in the options but when I reopen the application the scale is back to being large. Can there be a way to remember the settings?

I've tested this and it should save the UI scale... Are you sure you properly closed SHADERed?
You can also edit the settings.ini file directly (edit the "uiscale=" line and make sure "autoscale" is turned off (line above)).

I've just tested it again and the UI scale isn't remembered. I tried closing it using alf + f4, File > Exit, and pressing the close button on the window itself. Each time I set the UI scale and each time I reopen it the scale isn't remembered.
Here's a screen recording I did showing this https://youtu.be/R-is_Y298ys

Thank you so much for the screen recording. That changelog window should open only once. It doesn't save the settings and various other info (for example: that it has already shown the changelog window, which is located in a completely different file)...
Which leads me to believe that SHADERed doesn't have write permissions?
It does find the files (because it loads the correct fonts and workspace state), but it seems that it cannot write to them.

When I installed I did do sudo make install as the final step, so in theory it should have write permissions.
I've just tried compiling and installing again on my other computer (Dell XPS 15 Ubuntu 20.04) and still the same issue occurs.
Where is settings.ini supposed to be located? I've looked in /usr/local/share/shadered and my home folder and nothing is there

I've actually just tested this on my Ubuntu machine too, it happens to me too.. I'll look into this issue later tonight. Sorry for inconvenience and thank you for opening this issue!

The settings.ini should be in /usr/local/share/shadered but it is created after the first run (but since SHADERed can't write it isn't created).
Anyway, when running shadered as superuser everything works fine (do "sudo shadered" in terminal).
I guess possible fix could be to also search for such files in user's home directory. I'll try to implement this in v1.3.5

@hellocatfood This should be fixed in the latest commit ( b4397f561abffd0dc3ddc62559086e9a19ff1012 ). Some files should now be located in the $HOME/.local/share/shadered directory.
Closing.


Use schema template for 403 errors

I noticed that https://docs.getodk.org/central-api-entity-management/#updating-an-entity has a 403 example with code and message both set to pencil. I imagine that's some fallback when no examples are specified.
We have a nice schema template for 403 errors so I went through and used that everywhere.
Some endpoints like the one above had 403s defined with json and json/extended response types. In those cases, I removed the json/extended one.
Some endpoints redundantly specified an example along with the schema reference which itself specifies the same examples. I removed the redundant ones.
Some endpoints have 403 responses with other response types (e.g. https://docs.getodk.org/central-api-form-management/#draft-form). I think that's also a mistake but didn't want to look too deeply into it for now.
What has been done to verify that this works as intended?
Rendered docs with make api-docs, spot checked a few 403s.
Why is this the best possible solution? Were any other approaches considered?
Yay for reduction of duplication.
How does this change affect users? Describe intentional changes to behavior and behavior that could have accidentally been affected by code changes. In other words, what are the regression risks?
Docs-only.
Does this change require updates to the API documentation? If so, please update docs/api.yaml as part of this PR.
This does update it.
Before submitting this PR, please make sure you have:

[x] run make test and confirmed all checks still pass OR confirm CircleCI build passes
[x] verified that any code from external sources are properly credited in comments or that everything is internally sourced

This is only sort of related, but one thing I'm wondering about is the code property of the Error403 schema. It looks to be a string, but Problem codes are actually numbers.

Great, we now have a single place to fix it! Let's roll it into this change.


@import in media query doesn't find variables

I have the following setup:
base.less:
@import "colors.less";

@media only screen and (min-width: 481px) {
	@import "style.less";
}

colors.less:
@color: red;

style.less:
.class {
    color: @color;
}

When compiling I get:
variable @color is undefined on line 2 in file 'style.less':
  [1]: .class {
  [2]:     color: @color;
       -----------^
  [3]:    }
[Done - Failed]
[Finished in 1.2s with exit code -5]

I'm using the latest compiled dll from here dotless-v<IP_ADDRESS>.zip

Closing as duplicate.