Ss 558 create empty folders and gitkeep simplify local dev setup

Status

[X] Ready
[ ] Draft
[ ] Hold

Description
I have added empty folders with .gitkeep files as per Nikitas suggestion. I've also added these to the .dockerignore file.
Types of changes
What types of changes does your code introduce to STACKn?

[ ] Hotfix (fixing a critical bug in production)
[ ] Bugfix
[X] New feature
[ ] Documentation update

Checklist
If you're unsure about any of the items below, don't hesitate to ask. We're here to help!
This is simply a reminder of what we are going to look for before merging your code.

[X] This pull request is against develop branch (not applicable for hotfixes)
[ ] I have included a link to the issue on GitHub or JIRA (if any)
[ ] I have included migration files (if there are changes to the model classes)
[ ] I have read the CONTRIBUTING doc
[ ] I have included, reviewed and executed tests (unit and end2end) to complement my changes
[ ] I have updated the related documentation (if necessary)
[ ] I have updated the release notes (docs/releasenotes.md)
[X] I have added a reviewer for this pull request
[X] I have added myself as an author for this pull request

Really nice work. The reason why the build and test workflow fails is that it contains a step that attempts to create a media folder, from before this change when this folder was missing from the repo.
mkdir: cannot create directory ‘media’: File exists

Really nice work. The reason why the build and test workflow fails is that it contains a step that attempts to create a media folder, from before this change when this folder was missing from the repo.
mkdir: cannot create directory ‘media’: File exists

Yes. But I thought that .dockerignore file file would fix this. It's seems like it is being ignored as it contains media/ folder

Really nice work. The reason why the build and test workflow fails is that it contains a step that attempts to create a media folder, from before this change when this folder was missing from the repo.
mkdir: cannot create directory ‘media’: File exists

Yes. But I thought that .dockerignore file file would fix this. It's seems like it is being ignored as it contains media/ folder. Or it's not and there is an issue with folder itself not being ignored.
Either way, it's not working :)

It could be that it is working correctly for docker (i.e. ignoring the folder). The github action is simply checking out the repo (with the media folder and all) and then attempting to create the media folder, which fails. If the media folder is pre-created and stored in the repo and probably the github action should not also create it.

Hej great feedback! Will fix this tomorrow!


Dep/update

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


ensure linux sees all physical drives connected to marvell controller upon reset

Description
After clearing the Marvell raid configuration, some time is needed for
the individual drives to register again in linux.
By not waiting, during a deprovision, we may not discover all the
necessary drive to wipe or a wipe may start before the drives are
available to the os.

Have you been able to test this as a custom osie and see it loop and recover?

During testing I've seen the code which causes it to loop work correctly, however the way it was looking for serials was not working as expected which is why it loop. Since getting the serials the way it's done now, it has not needed to loop as the mvcli command has been slow enough to return that by the time it's completed the disks are available to the os.
Here is output from the SOL
++ mvcli info -o pd
++ awk '/Serial:/ { print $NF }'
+ pd_serials='203329F89422
203329F893F9'
+ udevadm settle
+ pd_missing=true
+ true
+ sleep 1
+ pd_missing=false
+ echo 'Marvell-Reset: Checking for drives...'
Marvell-Reset: Checking for drives...
+ for serial in '$pd_serials'
+ grep -q 203329F89422 /sys/class/block/sda/device/wwid /sys/class/block/sdb/device/wwid
+ for serial in '$pd_serials'
+ grep -q 203329F893F9 /sys/class/block/sda/device/wwid /sys/class/block/sdb/device/wwid
+ false

I wonder if this would apply to other raid cards too?


PATCH-1: Update packages

Reinstall all NPM packages from scratch (to get rid of all the old packages)
Migrate impacted code to work with the newer versions (including React 18 and Next 13)
Remove all unused packages and packages we always remove anyways
Remove @jam3 packages (they are outdated and will be reintroduced later on with a monorepo approach)
Update linter rules, they were really outdated!. In the process also removed the old and unnecessary semi-colons.
Enable Git LFS by default
Storybook V7

[AUTOMATED] Latest version has been pushed to preview.
Preview deployed at https://preview-52ebcf7.dev.nextjs-boilerplate.jam3.cloud.jam3.net


Allow conversions to and from int8 and uint8

Looks like int8 and uint8 got missed in the types that can be converted to bool and each other.

This change is

Reviewed 2 of 2 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Add cupy.isneginf and cupy.isposinf

Follows issue: https://github.com/cupy/cupy/issues/6078#issue-1051191869
Aim of the PR: To implement cupy.isneginf and cupy.isposinf.
Thanks!

Hi, @kmaehashi!
I added the API and their tests. Currently, I'm stuck in the following error.
  Please use the builtin `{name}` or its corresponding '
                f'NumPy scalar type `{eq_attr}` instead.',
                DeprecationWarning, stacklevel=2
            )
            return attr

        if name in _deprecated_apis:
            return getattr(_numpy, name)

>       raise AttributeError(f"module 'cupy' has no attribute {name!r}")
E       AssertionError: Only cupy raises error
E
E       Traceback (most recent call last):
E         File "/home/khushi/.local/lib/python3.9/site-packages/cupy/testing/_loops.py", line 43, in _call_func
E           result = impl(*args, **kw)
E         File "/home/khushi/Documents/cupy/tests/cupy_tests/logic_tests/test_content.py", line 17, in check_unary_inf
E           return getattr(xp, name)(a)
E         File "/home/khushi/.local/lib/python3.9/site-packages/cupy/__init__.py", line 901, in __getattr__
E           raise AttributeError(f"module 'cupy' has no attribute {name!r}")
E       AttributeError: module 'cupy' has no attribute 'isposinf'

../../.local/lib/python3.9/site-packages/cupy/__init__.py:901: AssertionError
----------------------------------------- Captured stdout call -----------------------------------------
dtype is e
======================================= short test summary info ========================================
FAILED tests/cupy_tests/logic_tests/test_content.py::TestContent::test_isneginf - AssertionError: Onl...
FAILED tests/cupy_tests/logic_tests/test_content.py::TestContent::test_isposinf - AssertionError: Onl...
===================================== 2 failed, 3 passed in 1.24s ======================================

My viewpoints
The test's output is AttributeError: module 'cupy' has no attribute 'isposinf' and AttributeError: module 'cupy' has no attribute 'isneginf'.

It seems like the error is due to adding the new API at the wrong location. But I am pretty sure about the location since I did the same as the comment suggested.
The other reason could be it imported cupy from the installed version instead of developing from the source version. (I don't know-how. It worked adequately in other PR's). What do you think?

Could you please take a look and give some tips? Thanks!

@khushi-411

The other reason could be it imported cupy from the installed version instead of developing from the source version. (I don't know-how. It worked adequately in other PR's). What do you think?
I think this is likely. I'd suggest uninstalling CuPy, then use pip install -e . for development.

Thanks, @kmaehashi! It worked (:
I will soon update the tests. Thank you!

Hi, @kmaehashi!
The PR is ready for review. Will you please review it? Would you mind telling me if any modifications are to be made? I would be happy to learn (:

Hi, @kmaehashi,
A gentle ping to you, requesting to review the PR. Thanks

Hi, @kmaehashi!
Thank you so much for reviewing and for your patience :)
I hope it is good to go now. Thanks again!

Hi, @kmaehashi!
Gentle ping :)
Thanks

/test mini

Hi, @kmaehashi!
One of the tests failed. But it seems unrelatable to the PR.
Warning, treated as error: |
-- | --
00:18:07.623323 STDOUT 1609] | failed to reach any of the inventories with the following issues: |
00:18:07.623332 STDOUT 1609] | intersphinx inventory 'https://docs.scipy.org/doc/scipy/objects.inv' not fetchable due to <class 'requests.exceptions.HTTPError'>: 404 Client Error: Not Found for url: https://docs.scipy.org/doc/scipy/objects.inv |
00:18:07.885845 STDOUT 1609] | make: *** [Makefile:176: doctest] Error 2

Warning, treated as error:
[00:18:07.623323 STDOUT 1609]](https://ci.preferred.jp/cupy.linux.cuda-example/94067/#L11271)	failed to reach any of the inventories with the following issues:
[00:18:07.623332 STDOUT 1609]](https://ci.preferred.jp/cupy.linux.cuda-example/94067/#L11272)	intersphinx inventory 'https://docs.scipy.org/doc/scipy/objects.inv' not fetchable due to <class 'requests.exceptions.HTTPError'>: 404 Client Error: Not Found for url: https://docs.scipy.org/doc/scipy/objects.inv
[00:18:07.885845 STDOUT 1609]](https://ci.preferred.jp/cupy.linux.cuda-example/94067/#L11274)	make: *** [Makefile:176: doctest] Error 2

This failure is due to the scipy's server problem. Waiting for your viewpoints. Thanks!

Right, let me merge this one manually.
SciPy team seems already aware and working on this issue: https://github.com/scipy/scipy/issues/15540
I'll consider adding mitigation in CuPy side if the problem does not get fixed in a day.


Query crashes process

If I do a search like /indexes/{index}/search?q=lala meilisearch crashes showing this error:
thread 'async-std/executor' panicked at 'called `Result::unwrap()` on an `Err` value: NotDedup', meilisearch-core/src/query_tree.rs:534:46

It is specific to the query 'lala' everything else I tried works as expected.
I'm using the latest version from the master branch built with the included Dockerfile.
Sadly I know next to nothing about Rust...
What can I do to narrow this down and provide a better bug report?
The json dataset I'm using is about 350MB in size.
I can share it (its will become public information soon anyway...) if that helps.

Hey @piccaso,
Wooow, this is bad, I know this kind of error but it must have never occured, would it be possible that you add the RUST_BACKTRACE=1 environement variable when you run the server please?
For your information this is an error that occurs when an array of elements that must be ordered and deduplicated is not deduplicated. That kind of error must never occur!
PS: I would be glad you you can point me to the dataset :)
Thank you very much ❤

Anyway, I found the line in the report you already provide, I will fix that soon.
Thank you again for your report.


Privileged configurable generic derivation

From your post https://meta.plasm.us/posts/2016/01/14/configuring-generic-derivation/
I was wondering if perhaps in a codebase, where there is a set convention (in my case snake_case over camelCase keys), it would be possible to configure that the priviledged .asJson to would always mean use SnakeCaseKeys, and do the same also for the decoding API.

It's possible to do this now:
import io.circe._, io.circe.generic.auto._, io.circe.generic.config._

implicit def snakeCaseDecoder[A](implicit
  decoder: ConfiguredDecoder[SnakeCaseKeys, A]
): export.Export0[Decoder[A]] = new export.Export0(decoder)

This exports instances configured to use snake-case at a higher priority that the default for exported instances. These won't take priority over custom instances, but they do outrank the default unconfigured derived instances.
(Note that this is just a demonstration—in real code you'd probably want to define something like a SnakeCaseDecoder subclass of Decoder and export instances with @exports(HighPriority)).

That's awesome, especially the priority over custom instances part. Thank you.

I'm going to reopen this issue because I can imagine providing explicit support for this—e.g. something like:
import io.circe.generic._, io.circe.generic.config._

val deriver: ConfiguredDeriver[SnakeCaseKeys] = ConfiguredDeriver[SnakeCaseKeys]

import deriver._

I'm not 100% sure I like this, but I think it's worth discussing.

That would be great to be able to make the whole scope to use snake case keys because usually APIs accept keys encoded in exactly one style.

Using a package object at the root and declaring the package as such:
package myrootpackage
package foo


Remove moot version property from bower.json

Per bower/bower.json-spec@a325da3
Also their maintainer says they probably won't ever use it: http://stackoverflow.com/questions/24844901/bowers-bower-json-file-version-property

Thanks, @kkirsche!


⚠ Secret Website 2 has degraded performance

In fee36c8, Secret Website 2 ($SECRET_WEBSITE_2) experienced degraded performance:

HTTP code: 200
Response time: 21005 ms

Resolved: Secret Website 2 performance has improved in 7a49092.


make email address an optional field in ACME issuers

What this PR does / why we need it:
Email addresses aren't required by the acme standard. Bring the configuration into line with the spec
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged):
fixes #1428
Special notes for your reviewer:
Release note:

Make ACME email addresses optional

/retest

/test all

/test all

/retest

/lgtm
/approve

/override pull-cert-manager-e2e-v1-13


Mac custom hints cannot be read when using base nodes

But with advanced nodes, you can read the defined style.

The image seem to be missing.


Intro mobilebkend

README and changes for the Android Mobile Backend.

TODO: Remove superfluous changes, e.g. update files under fedscale/core to reflect changes on master instead of intro_mobilebackend.

Are we pushing more code in this PR? Btw, we need one example at least and README.

Where is the app that supposedly can talk to FedScale?

Where is the app that supposedly can talk to FedScale?

Are we pushing more code in this PR? Btw, we need one example at least and README.

What are the remaining tasks?

Please try to merge ASAP. Thanks! @singam-sanjay

Please check it out @fanlai0990


Modularization chapter one

Hi Geoffrey,
I have created the modular files for Chapter One. However, while the book builds, there is a level Warning that comes up and the subsections are not appearing in the TOC. I'm not sure why this is happening. I'm submitting this to you so you can take a look and see if we can figure out how to address this.
Thanks,
Gemma.

Can I presume there are no other changes here except than splitting up the file?

Yes, correct. I've just split up the exact same file we had, no other changes at all :)

I am merging this manually and reviewing/adjusting it further locally.

I get these warnings during "mvn clean install" of "optaplanner-docs"

[INFO] --- asciidoctor-maven-plugin:1.5.3:process-asciidoc (generate-single-html) @ optaplanner-docs ---
asciidoctor: WARNING: Chapter-Planner_introduction/Section-whatIsOptaPlanner.adoc: line 2: section title out of sequence: expected level 2, got level 4
asciidoctor: WARNING: Chapter-Planner_introduction/Section-whatIsAPlanningProblem.adoc: line 2: section title out of sequence: expected level 2, got level 4
asciidoctor: WARNING: Chapter-Planner_introduction/Section-requirements.adoc: line 2: section title out of sequence: expected level 2, got level 4
asciidoctor: WARNING: Chapter-Planner_introduction/Section-governance.adoc: line 2: section title out of sequence: expected level 2, got level 4
asciidoctor: WARNING: Chapter-Planner_introduction/Section-downloadandruntheexamples.adoc: line 2: section title out of sequence: expected level 2, got level 4
[INFO] Rendered /home/ge0ffrey/projects/jboss/just-optaplanner/optaplanner/optaplanner-docs/src/main/asciidoc/index.adoc

The cause is clear: the sections start with "==" but their included as "leveloffset=+2". I'll fix.

The naming of the files is an insconsitent mess:

Section-downloadandruntheexamples.adoc uses no case
Section-whatIsAPlanningProblem.adoc uses camel case
All existing chapter files use this convention: Chapter-Planner_introduction.adoc

I'll fix, probably for now do it the existing way, although going to a denser format (camelcase, drop "Chapter" prefix etc) is probably desirable.

Merged manually, see https://github.com/kiegroup/optaplanner/tree/master/optaplanner-docs/src/main/asciidoc/Chapter-Planner_introduction


Implement unions as annotated types

Description
Replace strawberry.union direct usage with typing.Annotated for better type hints

[ ] Add test for warning over multiple args in tests/types/resolving/test_unions.py
[ ] Add tests for unions new api equivalent to those of the old api in tests/types/resolving/test_unions.py

Types of Changes

[ ] Core
[ ] Bugfix
[ ] New feature
[x] Enhancement/optimization
[ ] Documentation

Issues Fixed or Closed by This PR

Checklist

[x] My code follows the code style of this project.
[x] My change requires a change to the documentation.
[x] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] I have tested the changes and verified that they work and don't break anything (as well as I can manage).

Hi, thanks for contributing to Strawberry 🍓!
We noticed that this PR is missing a RELEASE.md file. We use that to automatically do releases here on GitHub and, most importantly, to PyPI!
So as soon as this PR is merged, a release will be made 🚀.
Here's an example of RELEASE.md:
Release type: patch

Description of the changes, ideally with some examples, if adding a new feature.

Release type can be one of patch, minor or major. We use semver, so make sure to pick the appropriate type. If in doubt feel free to ask :)
Here's the tweet text:
🆕 Release (next) is out! Thanks to Nahuel Ambrosini for the PR 👏

Get it here 👉 https://github.com/strawberry-graphql/strawberry/releases/tag/(next)

I've worked on this a bit more, I think it is almost ready to go, I want to improve the errors, but shouldn't take too long 😊

/pre-release

Pre-release
:wave:
Releasing commit [f6f04d2bdd952a7abd9f6a6d5d642dcf6878635d] to PyPi as pre-release! :package:

Pre-release
:wave:
Pre-release 0.189.1.dev.1687473609 [f6f04d2bdd952a7abd9f6a6d5d642dcf6878635d] has been released on PyPi! :rocket:
You can try it by doing:
poetry add strawberry-graphql==0.189.1.dev.1687473609

This should be ready now 😊

this is ready!

@bellini666 let's merge yours first and then this one later today or tomorrow 😊


Add Filter to People Search Page

In the sidebar of the people search page add the ability to filter based on a wide range of criteria.  This filtering cneeds to happen server side.  The client will pass the filter criteria.  We may expand this later but for now, include options for:

Display Name
First Name
Last Name
Has photo
Age
Address
City
State
Birth Date (with and without year)
Anniversary (with and without year)
Age
Gender
Membership Status
Marital Status

Some rules on how these work.

All strings should have options for equals, starts with, ends with or contains
All numbers and dates should include equals, greater than, less than and range
Booleans should have yes, no
We will also need a include/exclude option for each of these criteria.

Example filter:
Include - Age between 18-34
AND
Include - Gender = "Male"
AND
Include - Membership Status = "Member"

Completed with #174


Fix restic tags for game names containing a comma

https://github.com/sharkusmanch/playnite-ludusavi-restic/issues/55


Supress download logging maven

@enmasse-ci run tests profile=smoke test_only

:heavy_exclamation_mark: Build Failed :heavy_exclamation_mark:

@enmasse-ci run tests profile=smoke test_only

:heavy_check_mark: Test Summary :heavy_check_mark:
TEST_PROFILE: smoke
TEST_CASE:
TOTAL: 3
PASS: 3
FAIL: 0
SKIP: 0

@kornys I didn't realize this would affect running tests locally as well. I think we shouldn't require everyone to upgrade to maven 3.6 in order to run tests at all.

@lulf hmmm, I think it is ok to require latest tool version, anyway I will open an PR

#3488

@kornys IMO the rule of thumb is what is available in latest package managers :) maybe it can be detected by script?

@kornys alternatively add an environment variable that CI can pass?

You shouldn't hammer the Apache archive by downloading maven from it on every build.
You could use the travis cache (https://docs.travis-ci.com/user/caching/) to avoid re-downloading it every time (which could similarly apply to deps themselves even without this PR).
You could also get it from maven central (http://repo2.maven.org/maven2/org/apache/maven/apache-maven/3.6.2/apache-maven-3.6.2-bin.zip).
Or best of all, both.

@gemmellr thanks! will fix that


Consider doing Sanity check before attempt of crawling & deployment

A user (like me) who want to accept guest post and comment wont hesitate keeping http-auth/IP protected development area and proxied with CF, there are some areas where things can improve
1. WP2Static should check if Development Area is reachable or not
For Cloudflare proxied Development Site

If dev site HTTP response indicate Server: Cloudflare? Ask user to whitelist development Server IP in Cloudflare Firewall rule

(But, why? There are chances when CF WAF settings can prevent crawling.
If I am not wrong, they use Maxmind IP geo data.

It was considering Russia but my original Server Location was Singapore.
And, I had a rule to force JavaScript validation for all Russian visitors because so many incoming spam.
Result: I accidently blocked my server and caused failure of crawling message. Intrestingly, crawling was still in the progress (as I seen NGINX logs, it was just browser end failure of loading ajax requests)

or, this can be avoided by hardcoded IP in hosts file.
Hinting user to setting up whitelist will allow free-road for crawling.

Suggest user do not use ignore query string cache level because plugin uses query string while making ajax request, or ask user to add a page rule to bypass cache for

*example.com/wp-content/uploads/WP-STATIC-PROGRESS.txt*

2. Is development site HTTP Auth protected?

If response is not 200 but 401 (Unauthorised) due to HTTP-Auth? Hint user to fill HTTP auth details.
If 500, return error
Also, do check either entries are correct or wrong because Chrome saved pass can forcefully add /wp-login.php credential and cause error. Some user won't even realize what caused until they would check HTTP web server log (tail -f /var/log/nginx/error.log)

3. Validate Deployment Credential before starting 'crawling ...' before user click on "Deploy" button

After clicking Deploy, first thing shouldn't be crawling intial file list instead 'validate credentials' to prevent showing 'Failure to deploy' at last due to user mistake.
After this, there is no need of "Test" button.

A bit off-topic; I noticed if someone using NGINX Rate Limiting it can also cause crawling failure kind of message.  What I seen Webinoly based dev stack add limitation for wp-admin/admin-ajax.php request. I was able to fix by commenting out those rules.
I feel these suggestion will help beginners to avoid client and proxy side common pitfalls.
Thanks

I initially had something like this in WP2Static V7 diagnostics, but removed it as wasn't smoothly implemented. So, I am in the same mindset of wanting such a check.
Related issue in WP2Static: https://github.com/WP2Static/wp2static/issues/309
I think that's still useful and captures the rate limiting issues. ie, rate limiting won't fail in the beginning, but after n requests in succession, so n successive failures seems a good point to throw this error. Either n successive or first n requests all failing.


Add possibilty to get ResultMessage

Hi,
Can you please review this ?
Thanks, Paul.

Hi Paul, sorry for the delay - we're not going to be able to review this in the next couple of weeks, so I suggest you update your SDK fork and I'll update via this thread when we have more news.


Release v2.1.0 final to unlock Scala Center's SCP-026

Hello,
Coursier v2.1.0-M1 was released 2 months ago, with an M2 a couple weeks later. Since then, there does not appear to have been any changes in the master branch, and it also seems that no critical regression was reported.
May I kindly ask to release Coursier v2.1.0 final?
As long as there is no final release, we cannot merge the following PRs in coursier/apps:

https://github.com/coursier/apps/pull/119
https://github.com/coursier/apps/pull/113

Merging those PRs is required to move forward with the Scala Center Recommendation SCP-026, which has therefore been blocked.
Using the milestone is, in theory, possible. But you need to create your own channel with the changes brought by the two PRs above. This is not something we can recommend to newcomers.
/cc @adpi2 @ckipp01 @tpolecat

As discussed via other channels, I don't think we really need a "stable" version for the CLI.
I'd like to change the API a bit more before going back to stable version numbers (I'd like to rely on coursier/dependency and coursier/versions in particular, and drop the former APIs these replace).
To me, the coursier version reflects only the stability of the API. The CLI itself is stable enough (there's plenty of non regression tests, ensuring it is), and doesn't really break its "public interface", that is its CLI options.
I'm not sure, but it seems to me that part of your wish for a "stable" version may originate from the coursier website not being updated recently (it had been on 2.0.13 for a while, and only changed during the last two days). The CI jobs updating the website had issues since the switch of the coursier build to Mill. These are fixed now, by https://github.com/coursier/coursier/pull/2347 in particular.
I still need to update coursier/setup-action (its master is already using the latest launchers, only a stable release of coursier/setup-action should be needed IIRC).

Thank you for your response. Let me clarify what I mean by a “stable” release of the CLI. Basically, we would like to fix a couple of issues with the current behavior of cs. Notably, #1957, which is addressed by coursier/apps#119. There are a couple of other PRs open in coursier/apps, such as coursier/apps#113 and coursier/apps#122. I am not sure what are the blockers for these PRs to be merged, maybe they don’t need a new stable release of Coursier. It would be good to clarify how we could get them merged.

I'm not sure, but it seems to me that part of your wish for a "stable" version may originate from the coursier website not being updated recently (it had been on 2.0.13 for a while, and only changed during the last two days). The CI jobs updating the website had issues since the switch of the coursier build to Mill. These are fixed now, by #2347 in particular.

I just tried again from scratch, following the installation instructions, and what is installed is still cs 2.0.13. That means that we cannot merge https://github.com/coursier/apps/pull/119 and https://github.com/coursier/apps/pull/113, and that cs --help still shows the help menus before all the beginner-friendly improvements.
--> So my wish for a stable version is really that, if I follow the standard instructions on the website, I get a version of cs that has all the improvements that are currently in the Milestones. So that we can merge the above two PRs in coursier/apps.
If following the standard instructions installs cs 2.1.0-Mx, then I'm fine with it, and we should merge the two PRs. Ideally, for people who have already installed a previous version, cs update` should also install 2.1.0-Mx then. Otherwise we need to tell everyone to reinstall it, or force-update or something.

I'm a bit confused by what the plan is here now I see https://github.com/coursier/apps/pull/119 was merged, but I was under the assumption it wouldn't be until a stable release or everything was on the latest milestone.  CI builds that are using coursier/setup-action are now failing with the issue mentioned here: https://github.com/coursier/coursier/issues/2351.
Are we forcing the Milestone on people? Are we doing a stable release?

(on Windows)
OK, so, trying any combination cs update something, including with cs being the newest installer, did not update cs to the latest milestone, even I explicitly specified it.
However, after deleting AppData\Local\Coursier\data\bin entirely, and doing a new ".\cs-x86_64-pc-win32.exe" setup from scratch, I received what must be cs 2.1.0-something, along with the native sbt launcher. This was not the case a couple days ago when I last tried. So something definitely seems to have progressed here.
Thank you!

It turned out that releasing a final v2.1.0 was not necessary to ship the work done by the Scala Center into the hands of the Scala users. This issue can be closed.

Closing this, as the root of the issue (benefitting from fixes in the "default" CLI) has been fixed, with apparently non-stable version of the CLI being recommended in most places (being understood that version numbers stability applies less to the CLI, and more to the API stability).

For what it's worth, I'd still recommend doing a stable release. There are places that use coursier that have strict policies on versions that they can use. For example at the client I work at we aren't allowed to use non-stable versions, meaning we can't use anything newer than 2.0.16 because everything else is seen as a non-stable version. Please reconsider this. I know "it's just a number", but that doesn't work in a ton of enterprise-type companies. If it doesn't matter to you like you say, then just release a new stable version.

2.0.16

Which happened more than one and half year ago https://github.com/coursier/coursier/releases/tag/v2.0.16
New stable release would surely be warmly welcomed :heart:

I might cut 2.1.0 final then (and probably start using 2.2.0 milestone versions soon after).

2.1.0-RC6 came out yesterday. Do all these PCs mean 2.1.0 is now imminent? Or we have we replaced a potentially endless series of milestones with a potentially endless series of RCs...?

yayyy!!! https://github.com/coursier/coursier/releases/tag/v2.1.0  👏😍


Improve error message / binary chars in output

⌂73% [pablo:/tmp/foo] 1 $ ./vault add D39DC0E3:foo
Supplied fingerprint "ӝ��" does not have the correct size

:+1:


The AZ cli and Powershell command results are wrong

It's currently impossible to publish a B2S VM on the WestEurope zone 2 and 3, but the CLI return the following:
az vm list-skus --location westeurope --size B2 --all --output table
ResourceType     Locations    Name               Zones    Restrictions

virtualMachines  westeurope   Standard_B20ms     1,2,3    None
virtualMachines  westeurope   Standard_B2als_v2  1,2,3    None
virtualMachines  westeurope   Standard_B2as_v2   1,2,3    None
virtualMachines  westeurope   Standard_B2ats_v2  1,2,3    None
virtualMachines  westeurope   Standard_B2ls_v2   1,2,3    None
virtualMachines  westeurope   Standard_B2ms      1,2,3    None
virtualMachines  westeurope   Standard_B2pls_v2  1,2,3    None
virtualMachines  westeurope   Standard_B2ps_v2   1,2,3    None
virtualMachines  westeurope   Standard_B2pts_v2  1,2,3    None
virtualMachines  westeurope   Standard_B2s       1,2,3    None
virtualMachines  westeurope   Standard_B2s_v2    1,2,3    None
virtualMachines  westeurope   Standard_B2ts_v2   1,2,3    None
When looking at the "seel all sizes" in the portal, the following size doesn't support Zone 2 and 3:
b2als_v2
b2as_v2
b2ats_v2
b2ls_v2
b2s_v2
b2ts_v2
So the AZ CLI command doesn't look at the correct SKU table.
PS: I've tested the same with Powershell, and same mistake in the results
[Enter feedback here]

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

ID: 6fbce451-6278-4fe9-8f45-de3fdc615afe
Version Independent ID: 1c7c32b4-213f-ad36-3a86-9de745b2919a
Content: SKU not available errors - Azure Resource Manager
Content Source: articles/azure-resource-manager/troubleshooting/error-sku-not-available.md
Service: azure-resource-manager
Sub-service: troubleshooting
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@adrienmaugard
Thanks for your feedback! We will investigate and update as appropriate.

@adrienmaugard, thank you for sharing this feedback here.
@tfitzmac, could you please review this and share your thoughts. Thank you

@adrienmaugard - I was able to create a B2s_v2 in West Europe with zone 3. Is this what you were trying to do?

@tfitzmac no I was trying the B2S "v1" version. I know it's going to be replaced and it's not the best choice.
But it just show that the script return the wrong SKU compatibility (meaning it can be very wrong for other workload too)
The line I'm working on is:
virtualMachines westeurope Standard_B2s 1,2,3 None

r

Hello, do you have news on this?

@adrienmaugard - I was able to create a B2s_v2 in West Europe with zone 3. Is this what you were trying to do?

Hello, to you have news since my last reply?

I was able to create Standard B2s in West Europe Zone 3. I don't see any content update to make currently. I suspect the issue would require assistance from support to identify the cause.
#please-close


Support for easy-connect

The helper library easy-connect offers a way to more abstractly
define the networks being used.

This raises the question do we want users to use easy-connect in their product. When asked previously, the answer was no, because it adds unnecessary dependencies.
The goal of the example shouldn't be to make OOB easy, but to make building a new product easy. Using easy-connect here hides the interface that a user needs to interact with if they are needing to use their own network stack or a library not supported by easy-connect.
IMO we should have a separate example for easy-connect. It's probably even a good idea to point to the easy-connect example from this example's readme and use easy-connect in other examples demonstrating different APIs (for example client). But using easy-connect in this example is counterproductive for the goal of demonstrating the socket API.

@SeppoTakalo  - you will not get rid of easy-connect (or some other variant of it), due to the fact the the WiFi-stacks are not included in Mbed OS!
You must somewhere, somehow have the *.lib references that pull those drivers in. Would it make sense to pull all of them in one go (and fix the memory issue we're having) and just keep that one common place up-to-date with "known to be OK version of the drivers" vs. having multiple repos with MULTIPLE '.lib pulls and everyone trying to keep those in place?

We should @SeppoTakalo  make easy-connect v2.0 that uses the default interfaces, rather than stop using easy-connect. That would change the role of easy-connect to be more like "I collect the network interfaces/repos into one place". So, in the end - you will have to pull it in here. We can do that with easy-connect 2.0, though.

You must somewhere, somehow have the *.lib references that pull those drivers in. Would it make sense to pull all of them in one go (and fix the memory issue we're having) and just keep that one common place up-to-date with "known to be OK version of the drivers" vs. having multiple repos with MULTIPLE '.lib pulls and everyone trying to keep those in place?

This doesn't make sense from a user's perspective. A user will have 1 wifi chip and 1 board. Why should the download 8 different libraries?
What if they have their own wifi chip + their own wifi driver? The example as is allows them to easily plug in their driver to see what it would look like inside of mbed-os.

Especially since none of the WiFi repos seem to have any PR checks in them. @teetak01 at least has done PR checks for the easy-connect repo!

We should add CI to the wifi repos :)
Look at it this way, now we can add very aggressive tests running against UBLOX wifi without having to wait for esp8266 to catch up.


rethink default mode for SetConsoleMode

Currently the previous mode will be used just as it was:
https://github.com/kumavale/getch-rs/blob/f0611a226a6660f03d30033bf8b0a5f1d3dbf840/src/lib.rs#L83-L88
but I noticed for example, that ctrl + c will not be passed to the application, but instead windows handels it.
This is due ENABLE_PROCESSED_INPUT is set: https://learn.microsoft.com/en-us/windows/console/setconsolemode
I think we should set a reasonable default for the terminal, instead of relying the previous behavior.
I currently can only think of the ENABLE_VIRTUAL_TERMINAL_INPUT as a valid value, all others don't really fit in here.
What do you think?

Thanks for the issue.
Surely you are correct in setting only ENABLE_VIRTUAL_TERMINAL_INPUT as a valid value.


🧑💻 feat(core): Improve message when no setup files are found

Current dependencies on/for this PR:

new-dawn

PR #1050   👈

This stack of pull requests is managed by Graphite.

Current dependencies on/for this PR:

new-dawn

PR #1050   👈

This stack of pull requests is managed by Graphite.


Implement Rocket Booking

When a user clicks the "Reserve rocket" button, action needs to be dispatched to update the store. It gets the ID of the reserved rocket and update the state. It returns a new state object with all rockets, but the selected rocket will have an extra key reserved with its value set to true.

Hi @meryemsanem ,
Your project is complete!  There is nothing else to say other than... it's time to merge it :shipit:
Congratulations! 🎉

Highlights
✔ No linter errors
✔ Passed all requirements
✔ Clean code
Cheers, and Happy coding!👏👏👏
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me in your question so I can receive the notification.


Open Front Camera directly while clicking a picture

Hi dev,
Is there a function in the library which let the user to take a picture with the front camera directly without having the trouble to switch.
Thanks in advance.

no, but if you find a way and put a PR that would be great


Can't import my google location history

Version

Type of phone: Android
OS Version: Andorid 10
Model: e.g.  Pixel 3a

Steps to reproduce
Download google location history
Close app
Reopen app
Expected Behavior
Location history is imported
Actual Behaviour
Exception is visible on primary app scren in yellow.  Exception is in full below from logcatW ReactNativeJS: Can't open url: intent:#Intent;package=com.google.android.gms;action=com.google.android.gms.accountsettings.action.BROWSE_SETTINGS;S.extra.fallbackUrl=https%3A%2F%2Fmyaccount.google.com%2Fsecurity-checkup%3Fcontinue%3Dhttps%3A%2F%2Fmyaccount.google.com%2F%3Fpli%253D1;S.browser_fallback_url=https%3A%2F%2Fmyaccount.google.com%2Fsecurity-checkup%3Fcontinue%3Dhttps%3A%2F%2Fmyaccount.google.com%2F%3Fpli%253D1;i.extra.screenId=400;B.extra.fallbackAuth=true;S.extra.accountName=redacted%40gmail.com;end
:

Note that my google location history contains more than 1.7 million data points going back years...  This may be related.

@AdamLeonSmith thanks for addressing this issue. Did you export your data with Google Takeout and the following settings?

Delivery method: "Add to Drive"
Frequency: "Export once"
File type & size: ".zip" and "1GB"

After a chat on with @AdamLeonSmith to breakdown the problem, I could recreate this issue on iOS V0.5.19.
Here's the reproduction video:

Screenshot of the error
Steps to get this error

I just tested this on develop (2aa0dea277d63e4f29b402702f50c8a598660946) and it works fine!


AOD values can sometimes be large and in string format from Hist files

ADF run type
Model vs. Model
What happened?
When variables (in this case AODDUST and AODVIS) have fill values or missing values assigned like 1e36, etc. the data going into time series files, originally from the history files, takes on the scientific notation as a string and not a float.
When this happens the mean values get way over (or under) calculated and the AMWG table values (calculated from time series) are incorrect while the comp tables break when dealing with the strings.
Additionally, the mean values for the plots also are incorrect since the values in the time series go into calculating climo and regridded files, while the plots use regridded files.

I propose that the fill/missing values need to be addressed either before time series creation or after and re-calculate them. This will solve downstream fixes to climo and regridded files as well.
I am testing using ncap2 to change fill/missing values to Nan for only AODDUST and AODVIS time series at the moment:
cmd = ["ncap2", "-v", "-O", "-s", f'where({var}>1.e+26) {var}=nan;', ts_outfil_str, ts_outfil_str]
But considering this solution is for a certain set of know missing values for certain variables, I would be interested if there is a better, more encapsulating way to fix this.
ADF Hash you are using
430a861
What machine were you running the ADF on?
CISL machine
What python environment were you using?
NPL (CISL machines only)
Extra info
Example dataset:
b.cesm3_cam058_mom_e.B1850WscMOM.ne30_L58_t061.camdev_cice5.026c
hist files loc: /glade/scratch/hannay/archive/b.cesm3_cam058_mom_e.B1850WscMOM.ne30_L58_t061.camdev_cice5.026c/atm/hist
ADF generated time series loc:
/glade/scratch/richling/adf-output/ADF-data/timeseries/bad/b.cesm3_cam058_mom_e.B1850WscMOM.ne30_L58_t061.camdev_cice5.026c/11-21/
Sample images:

This seems to step on the toes of Issue #193.


DebugView and custom visualizers on expression trees

Summary

Accurately describes how to use the DebugView property
Describes how to use custom visualizers on the expression tree itself
Provides links and screenshots to two custom visualizers -- ReadableExpressions and my own ExpressionTreeVisualizer.

Fixes #10521
Pinging @BillWagner (sorry it took me so long.)

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


SyntaxError: Unexpected strict mode reserved word

Following the tutorial:

npm install sweet.js
test.js = syntax hi = function(ctx) ... and so on
node_modules/.bin/sjs test.js

/home/sustrik/node_modules/sweet.js/dist/sweet.js:59
let options_764 = arguments.length <= 1 || arguments[1] === undefined ? {} :
^^^
SyntaxError: Unexpected strict mode reserved word
at Module._compile (module.js:439:25)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)
at Function.Module._load (module.js:312:12)
at Module.require (module.js:364:17)
at require (module.js:380:17)
at Object. (/home/sustrik/node_modules/sweet.js/bin/sjs:21:15)
at Module._compile (module.js:456:26)
at Object.Module._extensions..js (module.js:474:10)
at Module.load (module.js:356:32)

Hi, I also had this problem. It turned out to be due to the way NodeJS was installed on my system.
If you look inside SweetJS's package.json, you'll see that the minimum version of NodeJS it requires is 5.0. Type nodejs -v to see what version you have installed. In my case it was somewhere around v.0.6 or so. You probably have to finagle the package manager. Check the NodeJS instructions for this.
The following fixed it for me:
npm uninstall sweet.js
sudo apt-get remove nodejs
curl -sL https://deb.nodesource.com/setup_4.x | sudo -E bash -
sudo apt-get install -y nodejs
npm install sweet.js

@disnet It might make sense to add a .npmrc file with engine-strict set to true. This is the second time I've seen someone stumble on this one.

Nevermind. I see that a user has to set engine-strict in their configuration. But a preinstall script could be used to match the installed version against package.json.

Fixed by #585


Nimble-arduino supports coded phy in connectable mode

Hi
My question is that Nimble-Arduino supports coded PHY in connectable mode or not? If yes can you please help me to point out which files need to change?
Thanks, And Regards,

Support for that is currently in progress. I should have an update soon.

Hi @h2zero
thank you! i will wait for it


[Deploy] Deploy the game to the free Vercel Domain

The first deploy will use the free domain at Vercel.


upgrade alpine to v3.9 in docker image

Current version (v3.6) will be end support on 2019-05-01.
see: https://wiki.alpinelinux.org/wiki/Alpine_Linux:Releases

Coverage remained the same at ?% when pulling 2ea87c9c229aed8f09552008b4fe75c96491f5c3 on imcotton:patch-1 into 0bf2b94d92920d8ef56a98827c42166df47217e6 on xtaci:master.


Cannot customize winsize when startup

I read the doc and found no way to predefine window size. I also tried set lines=,  but didn't work.

Try --geometry={rows}x{cols}, it sets the number of rows and columns it should display, but it can be inaccurate since it's not based on the font you're using in Neovim.

I added the --size option on master to specify pixel size, so you can do for example nvui --size=1600x900 to start with a width of 1600 and a height of 900 pixels.


Lone-ops shouldn't be able to call reinforcements

Description

Kinda ruins the whole point of it.
Reproduction

Screenshots

Additional context

they lose s lot of tc they could spend on equipment so its a fair tradeoff


SELECT Authorizations on Participant table must be restricted to allow use of ODXL

For the export of the participant list to Excel (XLSX) or CSV it would be the easiest to leverage the ODXL project. But after installing the tool I've discovered that the current authorizations would allow even the annonymous user to download all participant details as SELECT authorizations are granted to the Participant table.
The authorizations must be restricted to annonymous users and participants can only see the public information, organizers and defined co-organizers can only download participants of events there are involved in.

Hi Gregor! Thanks again for the invite, much appreciated :) I am now back for a week and if you need me I can try and help out on this issue. It noticed you already have a number of roles in place. It occurred to me in addition to locking down the data with database object privileges, it might also be a good idea to add an application privillege (https://help.sap.com/saphelp_hanaplatform/helpdata/en/4d/6ed4dc3db6423abd9f9a52a626618f/content.htm) to lock down access to the odxl service. I have never tried using those but if you like I can explore this option as well. I believe this would be a complementary measure - you would probably still need to secure things from the database end as well.

Hi Roland,
thank you for the comment. I think we're on a good way to lock down the authorizations that users can only see what they should see. I've moved most of the SELECT privileges away from the plain tables to restricted views. Perhaps it might be worth a note in the ODXL project that users should double check the table SELECT privileges.
Best regards
Gregor

Hi Gregor! Ok - good to hear and thanks for the suggestion. Yes, I agree - ODXL doc should get some cautionary note as well as some suggestions on how to manage privileges. Best regards, and thanks again for your interest! I really appreciate you including it and I hope it will help further your project :)

To allow the participant to update his registration information I was forced to define a wrapper hdbtablefunction and then call the update in a hdbtablefunction with "SQL SECURITY DEFINER". Because I can't provide the user read to the original table the update fails. Would be great if you can check commit b632fc5a4c83135eec1c2fa687f38ae4059b9452


Support Ubuntu 22.04

Hi @erkinalp
Thanks for reaching out.
As ROCm supports LTS versions of Ubuntu always and once 22.04 is out, we will support it officially.
Thank you.

20 days to Ubuntu release and Python dependencies are still not updated.

@ROCmSupport Can we reopen this, as Ubuntu's code freeze has happened?

Hi @erkinalp
We will be supporting 22.04 officially, once we get GA build.

@ROCmSupport By "GA" you most likely mean "General Availability". In the case of Ubuntu LTS, this is the release version of 22.04, set to be published on April 21st, 2022. ... Are you saying that AMD will have day-1-support for the next LTS version of Ubuntu?!

It would be good to have some preview support already so people can test right now, otherwise it is likely that there will be some bugs when people upgrade their machine with Ubuntu 22.04 final release.

Hi @erkinalp Thanks for reaching out. As ROCm supports LTS versions of Ubuntu always and once 22.04 is out, we will support it officially. Thank you.

Ok, you didn't @ROCmSupport. Regardless the release notes, there is no way to install ROCm stack on Ubuntu 22.4.x. And i'ts being like 4 months since Ubuntu 22.04 release now :disappointed:

I will soon upgrade the machines of my team at AMD to Ubuntu 22.10 so I do not care about this issue anymore. :-(
@saadrahim It is kind of sad to have to use GPU from my competitors because we do not deliver our software up to the last mile. :-(


Merge and updated the PR#8

Merge and updated the PR#8

@ridewindx added your fix with minor changes


Questions about memory consumption.

hank you for your work.
I have a few questions about your paper related to the memory consumption of the training.
1.What kind/How many GPUS did you use in your experiments?
2.How many GB of GPU memory do you use at each step?
3.May I ask you how much time in hours/days lasts the full training
Thanks in advance.

single 3090 GPU
about 18G
100epochs took about 19 hours, CAMUS dataset.

单个 3090 GPU
约18G
100epochs大约需要19个小时，CAMUS数据集。

thanks a lot

My lab has 3090 GPU, but I cannot train the model
python train_video.py --modelname MemSAM --task CAMUS_Video_Semi
Namespace(modelname='MemSAM', encoder_input_size=256, low_image_size=256, task='CAMUS_Video_Semi', vit_name='vit_b', sam_ckpt='checkpoints/sam_vit_b_01ec64.pth', batch_size=1, n_gpu=1, epochs=100, base_lr=0.0001, warmup=False, warmup_period=250, keep_log=False, disable_memory=False, disable_reinforce=False, disable_point_prompt=False)
Single object mode: False
Total_params: 58047159
Segmentation fault

Namespace(modelname='MemSAM', encoder_input_size=256, low_image_size=256, task='CAMUS_Video_Full', vit_name='vit_b', sam_ckpt='checkpoints/sam_vit_b_01ec64.pth', device='cuda', epoch=100, batch_size=2, n_gpu=1, base_lr=0.005, warmup=False, warmup_period=250, keep_log=False, frame_length=10, point_numbers=1, enable_memory=False, semi=False, reinforce=False, disable_point_prompt=False)
but
torch.OutOfMemoryError: CUDA out of memory. Tried to allocate 318.00 MiB. GPU 0 has a total capacity of 23.68 GiB of which 266.69 MiB is free. Process 787029 has 23.42 GiB memory in use. Of the allocated memory 22.33 GiB is allocated by PyTorch, and 802.83 MiB is reserved by PyTorch but unallocated. If reserved but unallocated memory is large try setting PYTORCH_CUDA_ALLOC_CONF=expandable_segments:True to avoid fragmentation.  See documentation for Memory Management  (https://pytorch.org/docs/stable/notes/cuda.html#environment-variables)


Promote - https://opensource.builders

https://opensource.builders

https://github.com/junaid33/opensource.builders/issues/222


refactor: Namespace to avoid aliasing

Please read contributing guidelines and remove this line.

Benchmark results
Metrics with a significant change:

note_successful_decrypting_time_in_ms (8): 243 (+16%)
note_trial_decrypting_time_in_ms (8): 45.2 (+380%)

Detailed results
All benchmarks are run on txs on the Benchmarking contract on the repository. Each tx consists of a batch call  to create_note and increment_balance, which guarantees that each tx has a private call, a nested private call, a public call, and a nested public call, as well as an emitted private note, an unencrypted log, and public storage read and write.
This benchmark source data is available in JSON format on S3 here.
Values are compared against data from master at commit d827705f and shown if the difference exceeds 1%.
L2 block published to L1
Each column represents the number of txs on an L2 block published to L1.

Metric
8 txs
32 txs
64 txs

l1_rollup_calldata_size_in_bytes
676
676
676

l1_rollup_calldata_gas
6,376 (-1%)
6,424
6,424

l1_rollup_execution_gas
585,709
585,757
585,757

l2_block_processing_time_in_ms
1,316 (+1%)
4,746 (-2%)
9,458

note_successful_decrypting_time_in_ms
:warning: 243 (+16%)
622 (+1%)
949 (+1%)

note_trial_decrypting_time_in_ms
:warning: 45.2 (+380%)
29.5 (+57%)
68.5 (+12%)

l2_block_building_time_in_ms
11,856 (-1%)
43,426 (+1%)
84,887

l2_block_rollup_simulation_time_in_ms
7,091 (-1%)
24,680 (+1%)
47,429 (+1%)

l2_block_public_tx_process_time_in_ms
4,727 (-1%)
18,624
37,220 (-1%)

L2 chain processing
Each column represents the number of blocks on the L2 chain where each block has 16 txs.

Metric
5 blocks
10 blocks

node_history_sync_time_in_ms
13,852 (-9%)
26,299 (-4%)

note_history_successful_decrypting_time_in_ms
1,191 (-4%)
2,303 (-2%)

note_history_trial_decrypting_time_in_ms
39.3 (-47%)
90.5 (+8%)

node_database_size_in_bytes
18,595,920
34,865,232 (-1%)

pxe_database_size_in_bytes
29,859
59,414

Circuits stats
Stats on running time and I/O sizes collected for every circuit run across all benchmarks.

Circuit
circuit_simulation_time_in_ms
circuit_input_size_in_bytes
circuit_output_size_in_bytes

private-kernel-init
177 (-2%)
44,377
26,164

private-kernel-ordering
158 (-2%)
50,830
39,325

base-parity
4,049 (-4%)
128
311

root-parity
1,157 (+2%)
1,244
311

base-rollup
14,364 (-1%)
116,608
861

root-rollup
49.5 (-3%)
4,359
725

private-kernel-inner
214 (-2%)
71,744
26,164

public-kernel-app-logic
117 (-2%)
47,695
40,661

public-kernel-tail
160 (-2%)
53,372
13,269

merge-rollup
10.6 (+2%)
2,568
861

public-kernel-teardown
118 (+1%)
47,695
40,661

public-kernel-setup
116
47,695
40,661

Tree insertion stats
The duration to insert a fixed batch of leaves into each tree type.

Metric
1 leaves
16 leaves
64 leaves
128 leaves
512 leaves
1024 leaves
2048 leaves
4096 leaves
32 leaves

batch_insert_into_append_only_tree_16_depth_ms
9.97 (-1%)
16.0
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_count
16.8
31.6
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_16_depth_hash_ms
0.581
0.492
N/A
N/A
N/A
N/A
N/A
N/A
N/A

batch_insert_into_append_only_tree_32_depth_ms
N/A
N/A
45.2 (-1%)
75.2 (+5%)
233
430 (-2%)
882 (+1%)
1,762 (+2%)
N/A

batch_insert_into_append_only_tree_32_depth_hash_count
N/A
N/A
96.0
159
543
1,055
2,079
4,127
N/A

batch_insert_into_append_only_tree_32_depth_hash_ms
N/A
N/A
0.464 (-1%)
0.463 (+5%)
0.425 (+1%)
0.402 (-2%)
0.419 (+1%)
0.421 (+2%)
N/A

batch_insert_into_indexed_tree_20_depth_ms
N/A
N/A
53.6 (-1%)
107
340
638 (-2%)
1,310
2,612
N/A

batch_insert_into_indexed_tree_20_depth_hash_count
N/A
N/A
105
207
691
1,363
2,707
5,395
N/A

batch_insert_into_indexed_tree_20_depth_hash_ms
N/A
N/A
0.473 (-1%)
0.483
0.463
0.439 (-2%)
0.454
0.455
N/A

batch_insert_into_indexed_tree_40_depth_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
60.1 (-2%)

batch_insert_into_indexed_tree_40_depth_hash_count
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
109

batch_insert_into_indexed_tree_40_depth_hash_ms
N/A
N/A
N/A
N/A
N/A
N/A
N/A
N/A
0.525 (-1%)

Miscellaneous
Transaction sizes based on how many contract classes are registered in the tx.

Metric
0 registered classes
1 registered classes

tx_size_in_bytes
40,548
501,142

Transaction size based on fee payment method

Metric
native fee payment method
fpc_public fee payment method
fpc_private fee payment method

tx_with_fee_size_in_bytes
905
1,161
1,377

Transaction processing duration by data writes.

Metric
0 new note hashes
1 new note hashes
2 new note hashes

tx_pxe_processing_time_ms
1,716 (-1%)
1,062 (-3%)
5,427

Metric
1 public data writes
2 public data writes
3 public data writes
4 public data writes
5 public data writes
8 public data writes

tx_sequencer_processing_time_ms
565 (-2%)
439 (+1%)
1,078 (+1%)
528
1,756 (+1%)
592 (+1%)

closed as stale


Inconsistent boundary setting within the evolution process and out of the evolution process

Hey Maxime,
We noticed that the default boundary for C used within the evolutionary process might be different from the boundary used when returning the output circuit.
Within the evolutionary process, the boundary for C is
parameter_bounds = Dict('R'=>[0,1.0e9],'C'=>[0,10],'L'=>[0,5],'P'=>[[0,0],[1.0e9,1]],'W'=>[0,1.0e9],'+'=>[0,0],'-'=>[0,0])
When outputting the final results, the boundary for C is
EquivalentCircuit(best_circuit,parameteroptimisation(best_circuit,measurements,frequencies))
...
get_parameter_upper_bound
...
Dict('R'=>1.0e9,'C'=>0.01,'L'=>5,'P'=>[1.0e9,1],'W'=>1.0e9,'+'=>0,'-'=>0)
...

:)

That's a good point. Also, in the present code, the circuit_evolution  function calls parameteroptimisation in the end (as you mentioned in your other issue), but does not allow a custom parameter bounds input. I'll have to make some adjustments by making the default values the same and either not calling parameteroptimisation in the circuit_evolution  function or adjusting it so that it also uses custom parameter bounds.


Name Entity Recognition function added

name: b) New feature: Name Entity Recognition
about: Select this if you're adding a new feature to libra.
labels: ner

This pull request closes #issue_number_here .
- What I did

I added a new functionality to detect name entities from input dataframe

- How I did it

I used the huggingface library which provides multi-lingual BERT based models for entity recognition.

- How to verify it

test cases added in tests.

Inorder to use it, you can run below commands:
newClient = client('location of csv file')
ouput_dictionary_of_ners = newClient.get_ner()
<even self.model['ner'] contains the output along with pretrained model and tokenizer>

[ ] I updated the docs.

can you please, let me know what needs to be done here?

This pull request adds a new feature to libra. @Palashio, could you please take a look at it?

it failed due to wrong dataset in test, I have updated the test file now


text.replace is not a function

Full Log:
[12:46:31] Starting 'generate_pot'...
/Users/joelworsham/Sites/www/wordpress-develop/public_html/src/wp-content/plugins/learndash-gradebook/node_modules/wp-pot/index.js:361
  text = text.replace(/\\([\s\S])|(")/g, '\\$1$2');
              ^

TypeError: text.replace is not a function
    at escapeQuotes (/Users/joelworsham/Sites/www/wordpress-develop/public_html/src/wp-content/plugins/learndash-gradebook/node_modules/wp-pot/index.js:361:15)
    at getPotMsgId (/Users/joelworsham/Sites/www/wordpress-develop/public_html/src/wp-content/plugins/learndash-gradebook/node_modules/wp-pot/index.js:378:13)
    at translationToPot (/Users/joelworsham/Sites/www/wordpress-develop/public_html/src/wp-content/plugins/learndash-gradebook/node_modules/wp-pot/index.js:434:32)
    at generatePot (/Users/joelworsham/Sites/www/wordpress-develop/public_html/src/wp-content/plugins/learndash-gradebook/node_modules/wp-pot/index.js:475:28)
    at wpPot (/Users/joelworsham/Sites/www/wordpress-develop/public_html/src/wp-content/plugins/learndash-gradebook/node_modules/wp-pot/index.js:514:23)
    at DestroyableTransform._flush (/Users/joelworsham/Sites/www/wordpress-develop/public_html/src/wp-content/plugins/learndash-gradebook/node_modules/gulp-wp-pot/index.js:51:25)
    at DestroyableTransform.<anonymous> (/Users/joelworsham/Sites/www/wordpress-develop/public_html/src/wp-content/plugins/learndash-gradebook/node_modules/through2/node_modules/readable-stream/lib/_stream_transform.js:115:49)
    at DestroyableTransform.g (events.js:260:16)
    at emitNone (events.js:67:13)
    at DestroyableTransform.emit (events.js:166:7)

Process finished with exit code 1

Issue was on my end. I was interpolating a var into the string to be translated, rather than using sprintf().


transaction pool nonces inconsistent

There are transactions in the pool which are invalid against the current best tip.
This is probably due to a race condition. This causes the daemon to crash because there is an assertion that those transactions should be valid.

To make the transaction poor behave correctly wrt concurrency we need to do #3644 and #4071. Pretty sure the crash is caused by #4071, but both are important.

Adding this related crash error here for search:
exn: "(monitor.ml.Error\n (Failure\n \"Tried to handle a committed transaction in the pool but its nonce doesn't match the head of the queue for that sender.\")\n (\"Raised at file \\\"stdlib.ml\\\", line 33, characters 17-33\"\n \"Called from file \\\"lib/network_pool/transaction_pool.ml\\\", line 260, characters 14-107\"\n \"Called from file \\\"list.ml\\\", line 117, characters 24-34\"\n \"Called from file \\\"src/list0.ml\\\" (inlined), line 22, characters 40-81\"\n \"Called from file \\\"lib/network_pool/transaction_pool.ml\\\", line 232, characters 8-1023\"\n \"Called from file \\\"lib/pipe_lib/broadcast_pipe.ml\\\", line 83, characters 25-28\"\n \"Called from file \\\"src/pipe.ml\\\", line 827, characters 4-56\"\n \"Called from file \\\"src/job_queue.ml\\\" (inlined), line 131, characters 2-5\"\n \"Called from file \\\"src/job_queue.ml\\\", line 171, characters 6-47\"\n \"Caught by monitor coda\"))"


StateVar-<IP_ADDRESS> missing

$ /home/ggreif/bin/stack repl
Didn't see StateVar-<IP_ADDRESS>@sha256:5136d2d5c8c7550782426367524a83bd11f8858aa24a92c756cdcf6224a1814e,1402 in your package indices.
Updating and trying again.
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
Downloading timestamp
No updates to your package index were found
Update complete
Unable to load cabal files for snapshot

----
Deleting cached snapshot file: /home/ggreif/.stack/build-plan/nightly-2018-04-24.yaml
Recommendation: try running again. If this fails again, open an upstream issue at:
https://github.com/fpco/stackage-nightly/issues/new
----

The following package identifiers were not found in your indices: StateVar-<IP_ADDRESS>@sha256:5136d2d5c8c7550782426367524a83bd11f8858aa24a92c756cdcf6224a1814e,1402
Possible candidates: StateVar-<IP_ADDRESS>, StateVar-<IP_ADDRESS>, StateVar-<IP_ADDRESS>, StateVar-<IP_ADDRESS>, StateVar-<IP_ADDRESS>.

What is your stack version? I'm not sure if it matters but you could try upgrading. I couldn't reproduce this
$ stack build StateVar --resolver nightly
Selected resolver: nightly-2018-04-24
Downloaded nightly-2018-04-24 build plan.
Didn't see brick-0.36.2@sha256:ddf055365a5ab747d2df313e837271e9f8d96f05832e02789a6436778de07b9a,13368 in your package indices.
Updating and trying again.
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
Downloading timestamp
Downloading snapshot
Updating index
Updated package index downloaded
Update complete
Populated index cache.
StateVar-<IP_ADDRESS>: configure
StateVar-<IP_ADDRESS>: build
StateVar-<IP_ADDRESS>: copy/register

$ /home/ggreif/bin/stack --version
Version 1.6.3 x86_64 hpack-0.20.0

I tried the command you pasted, it worked!
$ /home/ggreif/bin/stack build StateVar --resolver nightly
Selected resolver: nightly-2018-04-24
Didn't see StateVar-<IP_ADDRESS>@sha256:5136d2d5c8c7550782426367524a83bd11f8858aa24a92c756cdcf6224a1814e,1402 in your package indices.
Updating and trying again.
Selected mirror https://s3.amazonaws.com/hackage.fpcomplete.com/
Downloading timestamp
Downloading snapshot
Updating index
Updated package index downloaded
Update complete
Populated index cache.
[1 of 2] Compiling Main             ( /home/ggreif/.stack/setup-exe-src/setup-mPHDZzAJ.hs, /home/ggreif/.stack/setup-exe-src/setup-mPHDZzAJ.o )
[2 of 2] Compiling StackSetupShim   ( /home/ggreif/.stack/setup-exe-src/setup-shim-mPHDZzAJ.hs, /home/ggreif/.stack/setup-exe-src/setup-shim-mPHDZzAJ.o )
Linking /home/ggreif/.stack/setup-exe-cache/x86_64-linux/tmp-Cabal-simple_mPHDZzAJ_<IP_ADDRESS>_ghc-8.4.2 ...
StateVar-<IP_ADDRESS>: download
StateVar-<IP_ADDRESS>: configure
StateVar-<IP_ADDRESS>: build
StateVar-<IP_ADDRESS>: copy/register

Now my build seems to work again :-)
Thanks!


fix(ci): 🐛 Enable GPL on linux build and remove AppImage from CI

Same deal as on nightlies
Merge only after it gets tested at least on nightlies, otherwise i don't know if it works on nvidia (double-checking removal of nc-codec-headers)

...theres literally no code change, and it ran just fine before i change commit name
ignore macos check?...

Yeah it likes to fail on alvr_packets for some reason

Sry for asking but why removing AppImages? They worked just fine for me on nvidia.

I'm interested in why as well.

AppImages weren't required anymore (almost everything is bundled into alvr as static library now, appimage reason for being portable is nulled at this point) and it was maintenance burden that no one knew how to properly maintain, thus it was removed as unnecessary.

Hey, so I am trying to run the linux build and its crashing. I am not sure why, but this did not happen with the appimage. Is there a way to figure what is missing in the native build?

@guysoft please open new issue and provide output of ldd bin/alvr_dashboard and lib64/alvr/bin/linux64/driver_alvr_server.so with it

@Meister1593 for the same reason please remove flatpack, as the exact same logic applies

Flatpak is made fairly differently but removing flatpak build is planned as well. Just need to update instructions how to use with tar instead of it. It might be also possible to use it with nvidia that way.

Updating that my issue was fixed. I am now using the static build which works for me.


Add Oxygen to Techempower

Adding Oxygen to Techempower's benchmarks would provide visibility to the package as it would make it the only Julia package there, plus it would also give us a good idea of where we are with respect to other languages and give insight into what we're lacking

I just did a simple port of the HTTP.jl benchmark. Anyone interested can add other tests.

Hi everyone, I've opened a pr here: https://github.com/TechEmpower/FrameworkBenchmarks/pull/8789


seo keywords

Can you remove the unrelated changes please?

package.json and package-lock.json are still modified.

it not modified same code as it


Add property Dialog.LightBackground

Is your feature request related to a problem? Please describe.
The Overlay component supports the LightBackground property.
I think it makes sense that the Dialog component also has this same feature,
in order to use the themes light overlay color in a consistent way.

This issue is now organized in our feature requests project
Note: the issue is closed but that doesn't mean that this won't be implemented. Check the project to see how it is scheduled. If enough users vote for a different scheduling it can be changed. Also, if you want to PR this feature you may do so any time.
You can still discuss this feature here!

@Yomodo Are you interested in implementing this?
Original PR: #3669
See comment: https://github.com/MudBlazor/MudBlazor/issues/8487#issuecomment-2030292474

@Yomodo Are you interested in implementing this?

Sure, I'll start on this tonight.


Scheduled Job fails to run in next branch

Environment

Nautobot version (Docker tag too if applicable): 2.0.0alpha1
Python version: 3.10
Database platform, version: postgres 13
Middleware(s):

Beat scheduler raises an exception with traceback:
nautobot-celery_beat-1    | Traceback (most recent call last):
nautobot-celery_beat-1    |   File "/usr/local/lib/python3.10/site-packages/celery/apps/beat.py", line 105, in start_scheduler
nautobot-celery_beat-1    |     service.start()
nautobot-celery_beat-1    |   File "/usr/local/lib/python3.10/site-packages/celery/beat.py", line 645, in start
nautobot-celery_beat-1    |     interval = self.scheduler.tick()
nautobot-celery_beat-1    |   File "/usr/local/lib/python3.10/site-packages/celery/beat.py", line 341, in tick
nautobot-celery_beat-1    |     not self.schedules_equal(self.old_schedulers, self.schedule)):
nautobot-celery_beat-1    |   File "/usr/local/lib/python3.10/site-packages/django_celery_beat/schedulers.py", line 361, in schedule
nautobot-celery_beat-1    |     self._schedule = self.all_as_schedule()
nautobot-celery_beat-1    |   File "/usr/local/lib/python3.10/site-packages/django_celery_beat/schedulers.py", line 247, in all_as_schedule
nautobot-celery_beat-1    |     s[model.name] = self.Entry(model, app=self.app)
nautobot-celery_beat-1    |   File "/source/nautobot/core/celery/schedulers.py", line 33, in __init__
nautobot-celery_beat-1    |     self.schedule = model.scheduled_job
nautobot-celery_beat-1    | AttributeError: 'ScheduledJob' object has no attribute 'scheduled_job'

Fixed by #3459


Add failing spec for Tailwind v4

This PR adds a failing assertion to the integration test. The new test:

Adds a @theme block
inserts a custom property
runs the build command
asserts that the custom property is in the output file.

I'm completely new to the codebase so there's probably a lot that's missing here but I wanted to start the conversation with a failing spec to get things going.

Thank you for this! This is essentially the same test I wrote in #423 so that PR includes this coverage and fixes it. I'm glad we validated that.


Session id is not regenerated after successful login

To mitigate session fixation attacks, the session id should be regenerated after a user logins

Fixed in 6cea1f88fc4651f7b618149bea06d8d9db89bb7b


Add test for UglifyJsPlugin

What kind of change does this PR introduce?
Tests for UglifyJsPlugin
Did you add tests for your changes?
That's all I did
If relevant, link to documentation update:
-nil-
Summary
Sets UglifyJsPlugin's coverage to above 80% as mentioned in #3716.
Does this PR introduce a breaking change?
No
Other information

Thanks


Support older browsers in the wizard

I'm submitting a...

[ ] Bug report
[x] Feature request
[ ] Documentation issue or request

Current behavior

There is no coverage of this problem
Expected behavior

I would like a choice for supporting older browsers like IE 9/11 in the wizard, with automatic polyfill inclusion, updated browserlist file state and Angular 8 conditional bundle setup and generation

This could be added to the list of "additional tools" question ("Old browsers support (IE 9+)" option).
Feel free to propose a PR with 👍

With Angular support for all IE browsers (incl. IE11) being dropped, I'm closing this as it's relevant anymore.


Update MD file on new branch 2017-25-27_05-11-35

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestRef.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


setup: use find_packages to fix import error on paikkala.models while installed using pip

fixes
ModuleNotFoundError: No module named 'paikkala.models'

Codecov Report

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

@@           Coverage Diff           @@
##           master      #14   +/-   ##
=======================================
  Coverage   95.35%   95.35%
=======================================
  Files          27       27
  Lines         667      667
=======================================
  Hits          636      636
  Misses         31       31

Continue to review full report at Codecov.

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


Allow base errors to link to supplied fields

In the case where errors are added to the object's :base, linking items in the error summary list to a field is impossible. The GOV.UK Design System guidance states that such errors should link to the first field.
This change adds a link_base_errors_to argument to the error_summary helper that will override the link when errors on the object base are detected.
There's a new section on the guide covering the behaviour in more detail.
Refs #208

LGTM 👍
Thank you for doing this.


Review redundant requires

Many requires are redundant (especially in the Marketplace contract). We could remove them in order to save gas.

Duplicate of #12.


Dataset for supervised baseline

I would to know, for supervised baseline , we must use only labeled subset(like finetune) or all dataset (labeled+unlabeled).

Hi @SuryanarayanaY ,
For Supervised base line model we will use labelled dataset which can create a simple model. For semi supervised learning we can use partially labelled dataset (labeled+unlabeled). You may refer one example tutorial for semi supervised learning here for more details.
Please confirm if you are still looking for any more details.
Thanks!


Bug: requestURL when body is arraybinary or formdata, I try to transform formdata to array put it in body of request, but failed.

Steps to reproduce:
First

Here is some reproduction info.

Second
I don't know why the server ip is not same when I use obsidian reqestUrl and python command line, here are some I debug info ( print info and wireshark info), it related the formdata and upload a image file to server (and material/add_material?  interface),  I handle my self in the obsidian, but I have been triple checked, and sure, they are same binary body in two method.
first, I try my best to make the body the same in two methods. but IP is not same in two methods. It's becouse DNS ? ?  I don't know why.

python shell command line,   pass

requests.request("POST", url, headers=headers, data=payload, files=files)

obsidian requestUrl,  fail

python wireshark,  true data

obsidian requestUrl wireshark, not see true data

Three
I have try python code and nodejs request the interface upload a file all are oks.  But using requestUrl in obsidian fail, some sourcecode in here.

requestUrl does not support FormData. You must supply the full http request body either as a string or as an ArrayBuffer. Unfortunately this does make it quite a bit tedious to work with multipart form data.

Thx, I fix this problem, just replace body: post_typedArray using body: post_typedArray.buffer.

Is there a possibility of this getting patched to accept multipart form data?

Is there a possibility of this getting patched to accept multipart form data?

You can simulate a multipart form data request, as follows.

go to my project and give it a star, thx
then click here to watch some details about how to handle using form-data

then click here to watch some details about how to handle using form-data

Yep, I've looked over your code a bunch of times. It's the only reference I've been able to find. It has not worked for my use case. See the code and my attempts here

Sorry to hear about that, You can try other ways more. I am working now, so I may check out your code details when I am not busy.


Bug Adding Legend to Line Chart

When I add a legend to a line chart, the line is pushed below the boundary of the card.
LineChartView(data: [8,23,54,32,12,37,7,23,43], title: "Title", legend: "Legend")
Expected behavior is that it doesn't do this, like the demo gif on the repo home.

V2 beta 1 should fix this


Create adti.txt

Andijan State Medical Institute
https://adti.uz/en/

@dasturchiuz First stage of verification passed, official domain is adti.uz as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@dasturchiuz Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Add gaugeId: "29822" to 788 pool.

As far as I know this gauge duration is 24 hours and has 250k. How can I
check itt?
On Thu, Oct 27, 2022, 23:13 JeremyParish69 @.***> wrote:

@.**** requested changes on this pull request.
This gauge has not coins and is perpetual. Instead, the gauge(s) should be
fixed duration and have coins added.
—
Reply to this email directly, view it on GitHub
https://github.com/osmosis-labs/osmosis-frontend/pull/931#pullrequestreview-1159052657,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMQ5R6QWRFOUNS3RXQR4DRLWFLV6BANCNFSM6AAAAAARQJJPC4
.
You are receiving this because you were mentioned.Message ID:
@.***>

@manolius148
cmd osmosisd q incentives gauge-by-id 29476 reveals:
gauge:
  coins: []
  distribute_to:
    denom: gamm/pool/788
    duration: 86400s
    lock_query_type: ByDuration
    timestamp: "0001-01-01T00:00:00Z"
  distributed_coins: []
  filled_epochs: "0"
  id: "29476"
  is_perpetual: true
  num_epochs_paid_over: "1"
  start_time: "2022-08-15T02:09:52.710101768Z"

which is problematic. I should've been more clear; when I said 'duration', I really meant 'num_epochs_paid_over', which is how long the gauge distributes for (which in this case is only 1 day, but repeats perpetually), rather than how long the user bonds their LP tokens for (which in this case is 86400s == 1day). This gauge should not be perpetual, and num_epochs_paid_over should probably be at least 30 (days/epochs). Also, there are no coins listed under 'coins', so I cannot confirm the type of coin. Would you please create a new gauge that is not perpetual?

osmosisd tx incentives create-gauge gamm/pool/788
250000000000ibc/FFA652599C77E853F017193E36B5AB2D4D9AFC4B54721A74904F80C9236BF3B7
--duration 24h  --epochs 90 --from osmosis --chain-id "osmosis-1" --fees
350uosmo
I created the gauge with this command. That's why it seems so strange. Did
I do anything wrong?
[image: Mailtrack]
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
Sender
notified by
Mailtrack
https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&
10/28/22,
12:00:05 AM
El jue, 27 oct 2022 a las 23:48, JeremyParish69 @.***>)
escribió:

@manolius148 https://github.com/manolius148
cmd osmosisd q incentives gauge-by-id 29476 reveals:
gauge:
coins: []
distribute_to:
denom: gamm/pool/788
duration: 86400s
lock_query_type: ByDuration
timestamp: "0001-01-01T00:00:00Z"
distributed_coins: []
filled_epochs: "0"
id: "29476"
is_perpetual: true
num_epochs_paid_over: "1"
start_time: "2022-08-15T02:09:52.710101768Z"
which is problematic. I should've been more clear; when I said 'duration',
I really meant 'num_epochs_paid_over', which is how long the gauge
distributes for (which in this case is only 1 day, but repeats
perpetually), rather than how long the user bonds their LP tokens for
(which in this case is 86400s == 1day). This gauge should not be perpetual,
and num_epochs_paid_over should probably be at least 30 (days/epochs).
Also, there are no coins listed under 'coins', so I cannot confirm the type
of coin. Would you please create a new gauge that is not perpetual?
—
Reply to this email directly, view it on GitHub
https://github.com/osmosis-labs/osmosis-frontend/pull/931#issuecomment-1294112757,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMQ5R6WIEINYJOVSLTMWTB3WFL2CHANCNFSM6AAAAAARQJJPC4
.
You are receiving this because you were mentioned.Message ID:
@.***>

--

LuckyStar *

Already in order. Please check it again and merge it if it's alright
El sáb, 29 oct 2022 a las 0:26, JeremyParish69 @.***>)
escribió:

@.**** commented on this pull request.
In packages/web/config/feature-flag.ts
https://github.com/osmosis-labs/osmosis-frontend/pull/931#discussion_r1008550757
:

@@ -81,6 +81,13 @@ export const ExternalIncentiveGaugeAllowList: {
denom:
"ibc/A0CC0CF735BFB30E730C70019D4218A1244FF383503FF7579C9201AB93CA9293",
},

],
"788": [
{

 gaugeId: "29476",

I think you made the gauge correctly, and that this gauge ID is just a
typo. Looks like it should be 29872 based on the tx you gave to support. If
you could just correct the gauge ID and move this pool object in
chronological order (so, after pool 787), then this should be good to merge.
—
Reply to this email directly, view it on GitHub
https://github.com/osmosis-labs/osmosis-frontend/pull/931#pullrequestreview-1160808802,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AMQ5R6R4CBIXKAF7MKHJKADWFRHKLANCNFSM6AAAAAARQJJPC4
.
You are receiving this because you modified the open/close state.Message
ID: @.***>

--

LuckyStar *


fix nan interpolation to catch edge cases and remove time dimension f…

This fixes a few headaches in the initial condition interpolater. These are important for running with a newer executable where more netcdf variable type checks are done

Ok I ran black and then pushed again but the test fails and idk why

Seems that the first commit you did black was not even able to run!
https://github.com/COSIMA/mom6-regional/actions/runs/5264807245/jobs/9516578361#step:3:23
There were 2 parentheses in line 635 of this commit? 254d848

That was a parse error -- I think not even python could parse that.

OK! I think you have some WEIRD characters at the end of your file!

I think it originated because you had a parsing error with 2 parentheses in your first commit....

That's good...
But I'd have to trust you that you fixed a bug. This is the type of things that a test should have caught ;)

Gotcha!

Note: If this was part of dealing with #34 then just feel free to commit there. :)


OnStartup:  Alignment of "Add a new page" button

With longer text the button should expand to the left and not to the right, to maintain alignment
Current:

Proposal:

@XPoppyX Upon checking the latest beta release, it looks like the button is already lined up.

with the latest changes, it still looks like this


dependabot: create new PRs weekly

Daily PRs to bump FCOS in master branch are too frequent, resetting this to weekly

/override ci/prow/e2e-aws-upgrade
Previous version cannot be installed


update:   ✅ Added gradient background feature & fixed Overflow on right error w…

I have added gradient background. if user send gradient, that it shows gradient as background else color.
also i fixed the error  like "OverFlow right some pixels" when i going to decrease height less than 54.

@kh1amirhamza Please add documentation on Readme, and solve the conflict files

Bro,
I have resolved the conflict and added the documentation to the readme.
Check it out…
Thank You
On Mon, Sep 30, 2024 at 10:10 PM Aarón J. Montes @.***>
wrote:

@kh1amirhamza https://github.com/kh1amirhamza Please add documentation
on Readme, and solve the conflict files
—
Reply to this email directly, view it on GitHub
https://github.com/ajomuch92/flutter-scrolling-fab-animated/pull/14#issuecomment-2383619383,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AREGBZRMWPS5EHI5HB2QHRLZZFZXRAVCNFSM6AAAAABPBKAIW6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBTGYYTSMZYGM
.
You are receiving this because you were mentioned.Message ID:
@.***>


Missed Optimization Opportunity with Mux and Invalid

The following Chisel:
class DontCareMux extends Module {
  val io = IO(new Bundle {
    val en = Input(Bool())
    val out = Output(UInt(8.W))
  })
  io.out := Mux(io.en, 123.U, DontCare)
}

Gives the following FIRRTL:
circuit DontCareMux :
  module DontCareMux :
    input clock : Clock
    input reset : UInt<1>
    output io : {flip en : UInt<1>, out : UInt<8>}

    wire _T_1 : UInt<7>
    _T_1 is invalid
    node _T = mux(io.en, UInt<7>("h07b"), _T_1)
    io.out <= _T

Which results in the following Verilog:
module DontCareMux(
  input        clock,
  input        reset,
  input        io_en,
  output [7:0] io_out
);
  wire [6:0] _T;
  assign _T = io_en ? 7'h7b : 7'h0;
  assign io_out = {{1'd0}, _T};
endmodule

Unfortunately, because FIRRTL introduced the 0 instead of optimizing, synthesis cannot remove this mux.
Type of issue: other enhancement
What is the use case for changing the behavior?
Improved QoR
Impact: no functional change
Development Phase: request
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. Stack Overflow, gitter, etc)

Note, handling muxes the same way whens are handled in ExpandWhens is not sufficient, this same issue can happen to whens:
    wire w : UInt<8>
    w is invalid
    io.out <= w
    when io.en :
      io.out <= UInt<7>("h07b")
      skip

This keeps the mux to Verilog.
I think the solution is to delay the replacing of validif with 0, and propagate validif in Constant Propagation, then we have enough information to Constant Propagate the muxes then.


fortran-src <IP_ADDRESS>

camfort, ping @dorchard
Preprocessing library camfort-0.802...
unused terminals: 2
[ 1 of 42] Compiling Camfort.Helpers.Vec ( src/Camfort/Helpers/Vec.hs, dist/build/Camfort/Helpers/Vec.o )
[ 2 of 42] Compiling Camfort.Helpers  ( src/Camfort/Helpers.hs, dist/build/Camfort/Helpers.o )
[ 3 of 42] Compiling Camfort.Analysis.CommentAnnotator ( src/Camfort/Analysis/CommentAnnotator.hs, dist/build/Camfort/Analysis/CommentAnnotator.o )
[ 4 of 42] Compiling Camfort.Specification.Units.Parser ( dist/build/Camfort/Specification/Units/Parser.hs, dist/build/Camfort/Specification/Units/Parser.o )
[ 5 of 42] Compiling Camfort.Specification.Stencils.Syntax ( src/Camfort/Specification/Stencils/Syntax.hs, dist/build/Camfort/Specification/Stencils/Syntax.o )
[ 6 of 42] Compiling Camfort.Specification.Stencils.Grammar ( dist/build/Camfort/Specification/Stencils/Grammar.hs, dist/build/Camfort/Specification/Stencils/Grammar.o )
[ 7 of 42] Compiling Camfort.Specification.Stencils.Model ( src/Camfort/Specification/Stencils/Model.hs, dist/build/Camfort/Specification/Stencils/Model.o )
[ 8 of 42] Compiling Camfort.Specification.Stencils.InferenceBackend ( src/Camfort/Specification/Stencils/InferenceBackend.hs, dist/build/Camfort/Specification/Stencils/InferenceBackend.o )
[ 9 of 42] Compiling Camfort.Specification.Units.Environment ( src/Camfort/Specification/Units/Environment.hs, dist/build/Camfort/Specification/Units/Environment.o )
[10 of 42] Compiling Camfort.Specification.Units.SolveHMatrix ( src/Camfort/Specification/Units/SolveHMatrix.hs, dist/build/Camfort/Specification/Units/SolveHMatrix.o )
[11 of 42] Compiling Camfort.Specification.Units.Solve ( src/Camfort/Specification/Units/Solve.hs, dist/build/Camfort/Specification/Units/Solve.o )
[12 of 42] Compiling Camfort.Analysis.IntermediateReps ( src/Camfort/Analysis/IntermediateReps.hs, dist/build/Camfort/Analysis/IntermediateReps.o )
[13 of 42] Compiling Camfort.Analysis.Annotations ( src/Camfort/Analysis/Annotations.hs, dist/build/Camfort/Analysis/Annotations.o )
[14 of 42] Compiling Camfort.Traverse ( src/Camfort/Traverse.hs, dist/build/Camfort/Traverse.o )
[15 of 42] Compiling Camfort.Analysis.Syntax ( src/Camfort/Analysis/Syntax.hs, dist/build/Camfort/Analysis/Syntax.o )
[16 of 42] Compiling Camfort.Analysis.CallGraph ( src/Camfort/Analysis/CallGraph.hs, dist/build/Camfort/Analysis/CallGraph.o )
[17 of 42] Compiling Camfort.Analysis.Types ( src/Camfort/Analysis/Types.hs, dist/build/Camfort/Analysis/Types.o )
[18 of 42] Compiling Camfort.Transformation.Syntax ( src/Camfort/Transformation/Syntax.hs, dist/build/Camfort/Transformation/Syntax.o )
[19 of 42] Compiling Camfort.Analysis.LVA ( src/Camfort/Analysis/LVA.hs, dist/build/Camfort/Analysis/LVA.o )
[20 of 42] Compiling Camfort.Analysis.Loops ( src/Camfort/Analysis/Loops.hs, dist/build/Camfort/Analysis/Loops.o )
[21 of 42] Compiling Camfort.Specification.Stencils.Annotation ( src/Camfort/Specification/Stencils/Annotation.hs, dist/build/Camfort/Specification/Stencils/Annotation.o )
[22 of 42] Compiling Camfort.Specification.Stencils.CheckBackend ( src/Camfort/Specification/Stencils/CheckBackend.hs, dist/build/Camfort/Specification/Stencils/CheckBackend.o )
[23 of 42] Compiling Camfort.Specification.Stencils.Synthesis ( src/Camfort/Specification/Stencils/Synthesis.hs, dist/build/Camfort/Specification/Stencils/Synthesis.o )
[24 of 42] Compiling Camfort.Specification.Units.Debug ( src/Camfort/Specification/Units/Debug.hs, dist/build/Camfort/Specification/Units/Debug.o )
[25 of 42] Compiling Camfort.Transformation.CommonBlockElim ( src/Camfort/Transformation/CommonBlockElim.hs, dist/build/Camfort/Transformation/CommonBlockElim.o )
[26 of 42] Compiling Camfort.Transformation.CommonBlockElimToCalls ( src/Camfort/Transformation/CommonBlockElimToCalls.hs, dist/build/Camfort/Transformation/CommonBlockElimToCalls.o )
[27 of 42] Compiling Camfort.Transformation.DeadCode ( src/Camfort/Transformation/DeadCode.hs, dist/build/Camfort/Transformation/DeadCode.o )
[28 of 42] Compiling Camfort.Transformation.DerivedTypeIntro ( src/Camfort/Transformation/DerivedTypeIntro.hs, dist/build/Camfort/Transformation/DerivedTypeIntro.o )
[29 of 42] Compiling Camfort.PrettyPrint ( src/Camfort/PrettyPrint.hs, dist/build/Camfort/PrettyPrint.o )
[30 of 42] Compiling Camfort.Reprint  ( src/Camfort/Reprint.hs, dist/build/Camfort/Reprint.o )
[31 of 42] Compiling Camfort.Output   ( src/Camfort/Output.hs, dist/build/Camfort/Output.o )
[32 of 42] Compiling Camfort.Input    ( src/Camfort/Input.hs, dist/build/Camfort/Input.o )
[33 of 42] Compiling Camfort.Specification.Stencils.InferenceFrontend ( src/Camfort/Specification/Stencils/InferenceFrontend.hs, dist/build/Camfort/Specification/Stencils/InferenceFrontend.o )

src/Camfort/Specification/Stencils/InferenceFrontend.hs:158:13: error:
    Not in scope: ‘FAT.inferTypes’
    Module ‘Language.Fortran.Analysis.Types’ does not export ‘inferTypes’.

src/Camfort/Specification/Stencils/InferenceFrontend.hs:598:24: error:
    Not in scope: type constructor or class ‘FAT.TypeScope’
    Module ‘Language.Fortran.Analysis.Types’ does not export ‘TypeScope’.

src/Camfort/Specification/Stencils/InferenceFrontend.hs:601:21: error:
    Not in scope: data constructor ‘FAT.Local’
    Module ‘Language.Fortran.Analysis.Types’ does not export ‘Local’.

src/Camfort/Specification/Stencils/InferenceFrontend.hs:601:59: error:
    Not in scope: data constructor ‘FAT.Global’
    Module ‘Language.Fortran.Analysis.Types’ does not export ‘Global’.

Sorry about that, we were mixing the latest version on hackage. Now fixed. Camfort v.804 on Hackage requires fortran-src = <IP_ADDRESS>. Should I fix the upper bound?

For stackage the only thing that matters is that the latest versions of everything build together.


Add Python import auto-fix when module path changes

As in JS and TS support, VSCode should be able to fix the related imports once a module's path has changed within the workspace.

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.

Thank you for the suggestion! We have marked this issue as "needs decision" to make sure we have a conversation about your idea. We plan to leave this feature request open for at least a month to see how many 👍 votes the opening comment gets to help us make our decision.


Update README.md

The title of the README.md was still set to AshCsv.
Contributor checklist

[ ] Bug fixes include regression tests
[ ] Features include unit/acceptance tests

🚀 Thank you for your contribution! 🚀


Getting geckodriver in the PATH

Getting the following output when trying to run...
Traceback (most recent call last):
File "C:\Users<hidden>\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\site-packages\selenium\webdriver\common\service.py", line 72, in start
self.process = subprocess.Popen(cmd, env=self.env,
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.8_3.8.1520.0_x64__qbz5n2kfra8p0\lib\subprocess.py", line 854, in init
self._execute_child(args, executable, preexec_fn, close_fds,
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.8_3.8.1520.0_x64__qbz5n2kfra8p0\lib\subprocess.py", line 1307, in _execute_child
hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
FileNotFoundError: [WinError 2] The system cannot find the file specified
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "comdown.py", line 68, in
browser = webdriver.Firefox(options = options, executable_path=r"PATH\TO\geckodriver.exe")
File "C:\Users<hidden>\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\site-packages\selenium\webdriver\firefox\webdriver.py", line 164, in init
self.service.start()
File "C:\Users<hidden>\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.8_qbz5n2kfra8p0\LocalCache\local-packages\Python38\site-packages\selenium\webdriver\common\service.py", line 81, in start
raise WebDriverException(
selenium.common.exceptions.WebDriverException: Message: 'geckodriver.exe' executable needs to be in PATH.

browser = webdriver.Firefox(options = options, **executable_path=r"PATH\TO\geckodriver.exe"**)
You have to put the path of geckodriver in the executable_path argument. You can download the driver from here: https://github.com/mozilla/geckodriver/releases. Let me see if I can use a drivermanager library to get rid of all this weird path stuff. Wait for the updates, until then you can try doing it manually as I have shown above.

The update did automatically download geckodriver.exe to the cache...which was cool.  So this problem done. :)


get_builtins_host_obj_path requires lib/ when that doesn't make sense for the platform

As of 43f9e2a7 (#1848), Roc requires a lib directory to be present by requiring it with an expect in get_builtins_host_obj_path in crates/compiler/builtins/src/bitcode.rs. This doesn't always make sense, for example in Rust platforms. Should that function return an Option<String> or something?
cc @Anton-4 since you were working on that PR

Also, just to be fair, most language compilers are not standalone binaries. They really on standard libraries and etc. Even zig has a lib folder that must be copied around. So I think it is the exception not the rule that a compiler can be a standalone binary. Just when installing both the library and the binary get placed in the correct spot. Roc may be one of the few compilers where we can avoid this, but that is cause our standard library for host will be pulled in by the host and our standard library for apps should be fully ingested (small load time cost).

Oh shoot, I forgot that this is used for the host object and the zig source files.
So another addition. The host object file doesn't make sense and needs to be remove. Host is a very specific target and does not makes senses to distribute. It could use instructions that are not available to the end user.
I am pretty sure this object file is only needed for the dev backend. This code is generated with llvm bytecode in the main backend. It might be reasonable to generate generic versions of this file for each architecture and ingest them into the roc app, but that would bloat the roc app for every single target we want to support (currently by about 260k). Not huge, but would add up across os, cpu architecture pairs.
We don't want Roc to depend on zig being installed, so we don't want to ingest the zig files directly. Though that would be a simple solution. Ingest the zig files and compile them into an object file on the host. Instead, I think the best solution here is to use the ingested llvm bytecode to generate this object the first time that roc is run per target. Then we dump it to disk in some sort of global roc related cache and it will only need to be generated again when Roc updates.

It might be reasonable to generate generic versions of this file for each architecture and ingest them into the roc app, but that would bloat the roc app for every single target we want to support (currently by about 260k). Not huge, but would add up across os, cpu architecture pairs.

This is the solution I prefer.
It's been a goal from day one of the project to have one single binary that you can download anywhere and immediately execute on any of the major operating systems.
I also think that since surgical linking lets us support cross-compiling, we'll want to bundle stdlib implementations for all the different targets anyway; they won't sit unused if you're cross-compiling!
Bundling Zig is always an option, but at +40MB we'd need quite a lot of target combinations before that was a cost savings!

Since we have to ingest the llvm bytecode files anyway, is there an advantage to ingesting both the object files and the bytecode files? With the bytecode files there is just an extra step on the first compile with a dev backend. It has no cost to the llvm backend.

we'll want to bundle stdlib implementations for all the different targets anyway

I'm not sure I undestand what you mean here. What do you mean by stdlib? Our standard library to my understanding is these llvm bytecode or object files. So this discussion is already about bundling them.

Oh yeah, sorry - we are talking about the same thing! My wording wasn't ideal. 😅

Since we have to ingest the llvm bytecode files anyway, is there an advantage to ingesting both the object files and the bytecode files? With the bytecode files there is just an extra step on the first compile with a dev backend. It has no cost to the llvm backend.

This makes sense to me! 👍
We'll want a global ~/.roc-cache (or whatever) directory to store things like downloaded packages, so bundling the .bc files into the executable and then using LLVM to go from .bc to object files on a per-(target + compiler version) basis and caching them in that directory sounds like a good approach!

hopefully it will be .cache/roc


Create google/cloud/storage/{README.md,quickstart/}

We want each per-library area to contain its own README.md and quickstart/ area. The build instructions that currently exist in the top-level README.md file would be replaced by the instructions in the google/cloud/storage/quickstart/ folder.
The google/cloud/storage/README.md should follow a pattern similar to https://github.com/googleapis/google-cloud-cpp-spanner/blob/master/README.md
The google/cloud/storage/quickstart/ directory should follow a pattern similar to https://github.com/googleapis/google-cloud-cpp-spanner/tree/master/quickstart
Tasks:

[ ] Created/updated google/cloud/storage/README.md
[ ] Created google/cloud/storage/quickstart/
[ ] Build scripts test google/cloud/storage/quickstart/

Note that there is a quickstart program in google/cloud/storage/examples/storage_quickstart.cc which is probably suitable for this, it is referenced by the cloudsite documentation too.