Idea: Using Query Builder / ORM for database access like SQLAlchemy or Peewee

Is your feature request related to a problem? Please describe.
Thanks for putting this together!
One thing which annoys me about Supabase-Py is the lack of Query Builder / ORM which feels like makes the queries fragile OR you have to have a full CRUD test for it.
Describe the solution you'd like
Did you consider generating models out of the Postgres Database with say sqlacodegen?
I.e. instead of doing
supabase.table("countries").select("*").eq("country", "IL").execute()

you could with SQLAlchemy or Peewee ORMs do like:
Countries.get(country == "IL")

which catches query problems at build time.
Describe alternatives you've considered
Current solution feels good enough.
Additional context
I have started executing on this idea with Peewee, but it ain't yet fully production ready. Just wanted to give you an idea
https://github.com/petercsiba/supawee?tab=readme-ov-file#example-models

Sorry to have u waiting for few weeks! busy for the bottom of the year. i am very appreciated for your instructive suggestion.

One thing which annoys me about Supabase-Py is the lack of Query Builder / ORM which feels like makes the queries fragile OR you have to have a full CRUD test for it.

you are definitely right dude! i  did  find the discussion about ORM in the supabase-py issues, and looks no plan for integrating supabase with ORM style query, but i think it deserves a try. causes i genuinely prefer the object-oriented mode, and i thinks it should have a plan for it.

this idea with Peewee
the idea will help us reduce too much time on writing ORM model manually.sounds great!
tiangolo who created the FastAPI also build the ORM tools called sqlmodel , it looks like a good high-level abstraction for SQLAlchemy with pydantic so i think this one maybe suitable for fastapi, sqlacodegen suit for it i think

in short, the following works:

[ ] SqlModel ORM  instead  of supabase.table("countries").select("*").eq("country", "IL").execute()
[ ] sqlacodegen for sqlmodel

your ideas do help a lot!

NP thanks for the thoughtful response and research Atticuszz!
Good point +1, yes for a Fastapi library like yours sqlmodel w/ sqlacodegen feels like the best integration,
since it is most likely to match "vibes" of FastAPI.
(Just rambling lol)
Was thinking if adding sqlmodel to this template si too "opinionated",
but then this is a template, so from a projects lifespan perspective forking this template might be the best point-of-time to commit to a way to interact with the database.
That said, this is just an idea, thanks again for putting this repo together!

Hey, thanks for bringing this up. After thinking it over, I'm leaning towards implementing SQLModel. Here's why:
We could use Supabase primarily as a database UI tool, while handling database operations through a more universal approach like SQLModel. This gives us much more flexibility and portability. It avoids tying us too closely to Supabase-specific implementations, which could be limiting in the long run.
SQLModel offers the best of both worlds - we can use object-oriented queries or fall back to SQL-like syntax when needed. This versatility is key for a template that needs to cater to various project requirements.
The project's roadmap is promising too, with async support coming up. This forward-thinking approach aligns well with our need for a future-proof solution.
What are your thoughts on this approach? It seems to strike a good balance between providing a solid starting point and maintaining flexibility for different project needs.

it starts on #143 now ,coming soon together with self-host supabase  and sqlmodel orm 😆


 before

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Expected Behavior
<meta charset="utf-8"> should be the first element in the <head>
Current Behavior
<NextScript /> prepends the preloadDynamicChunks in the head.
https://github.com/zeit/next.js/blob/canary/server/document.js#L87
Context
https://sonarwhal.com/docs/user-guide/rules/meta-charset-utf-8/
Your Environment

Tech
Version

next
4.1.3

node
8.4.0

@timneutkens this PR doesn't solve this issue. sadly.

@schoenwaldnils it's not released yet. Have you tried the branch?


add residue at a pole and cauchy residue theorem and methods to find residue

I would like to add residue at a pole and cauchy residue theorem and methods to find residue in complex numbers section

@sairish2001 @shrey27tri01 @apekshamanchanda Shalli i Work on this?


Permissions and private topics

Migrates to the new permissions model. #126
Un-ties private topics from messageboards. #138
Splits out PrivatePost from Post.
Splits the views and mailers of private topics. They just point to
the common topic views, but the user can nowoverride them separately.

Not in this PR:

Notification preferences for private topics.
Permissions documentation.

Also in this PR:

Minore style tweaks.
A rake test_all_gemfiles task (works as advertised).

The gist of the new permissions system is in app/models/thredded/user_permissions/.
Sorry about a huge PR. In my defence, ripping out the previous roles system was an involved job.
@jayroh @cgunther

Just pulled down the branch and gave things a run through and, first comment - this is looking phenomenal. Really really really damn nice. Thank you @glebm for all this work. Thank you @cgunther for the work as of late. I'm super impressed with where things have gotten recently.
@glebm, I have some updates I've made locally to get db:truncate working (some recently added foreign keys necessitate our needing a CASCADE amidst our TRUNCATE statement), and dev:seed working again.  Would you prefer a pull request on top of your branch or should I just push a commit up to this branch? I ask so that I may have as good git(hub) etiquette as possible :smile:
I haven't looked through the implementation with a fine-grained set of eyeballs yet, and will do so within the next 24 hours. A first pass, though, and I'm confident things will be ready to go sooner rather than later

@jayroh Since this is a huge PR, a good GitHub etiquette would be a separate PR targeting this branch, but you can just push it on top of permissions in this case. :+1:

This is pretty epic, A+ Gleb!

Merged! If there are any other concerns, I can address them later.

I'll be pulling down thredded.com and running it against master to see if
there are any edges that need to be smoothed over. Once I do that it should
be pretty obvious what/where needs attention.
On Sat, Mar 26, 2016 at 12:08 PM, Gleb Mazovetskiy<EMAIL_ADDRESS>
wrote:

Merged! If there are any other concerns, I can address them later.
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/thredded/thredded/pull/161#issuecomment-201873295


10_final_SviatoslavTaranenko

Link to deployed project - https://sviatoslavtaranenko.github.io/fe-course-basic-2023/
Without filters

Thanks for a good work 😎

OK, @SviatoslavTaranenko, thanks for your fixes.
The last step here is to fix linters errors, to make possible to merge  your pr
https://sviatoslavtaranenko.github.io/fe-course-basic-2023/
https://github.com/MastersAcademy/fe-course-basic-2023/actions/runs/7439250759/job/20238920637?pr=442
https://github.com/MastersAcademy/fe-course-basic-2023/actions/runs/7439250759/job/20238920483?pr=442

@vladyslav-yermolin-moc thanks for understanding and for your help))


Maybe Bug - function toTimeZone argument 2 can't use field as dynamic value.

(you don't have to strictly follow this form)
Describe the bug or unexpected behaviour
A clear and concise description of what works not as it is supposed to.
How to reproduce

Which ClickHouse server version to use
<IP_ADDRESS>
Which interface to use, if matters
Non-default settings, if any
CREATE TABLE statements for all tables involved
Sample data for all these tables, use clickhouse-obfuscator if necessary
Queries to run that lead to unexpected result

SELECT
    created_at,
    time_zone,
    toTimeZone(created_at, time_zone)
FROM stores
WHERE id = 22693
LIMIT 1

┌──────────created_at─┬─time_zone──────┬─toTimeZone(created_at, time_zone)─┐
│ 2017-08-09 10:15:01 │ Asia/Hong_Kong │               2017-08-09 10:15:01 │
└─────────────────────┴────────────────┴───────────────────────────────────┘

Expected behavior
A clear and concise description of what you expected to happen.
Error message and/or stacktrace
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.

It is known issue / limitation, but maybe it should be fixed someday.

@filimonov It cannot be fixed, because time zone is characteristic of data type, not value.
The value is stored as unix timestamp and independent of time zone. Time zone affects operations on DateTime components and converson to and from string.

There are a lot of cases then it's not a type issue: toDate, toString, toStartOfDay, toHour etc.
Typical usecase - timestamp (usual unixtime) of event and separate client timezone field. And we need to get hours when users are the most active (in their tz)

storing TZ in string form in that case is suboptimal

Probably the best way is to provide predefined Enum with stable identifiers for every time zone.

And currently the best workaround i can imagine - is to store current utc offset instead of timezone

Yes, it is viable solution if you store UTC offset at the specified moment of time.

How metrika solves that task? Or tz is set up per account, not per visitor?

We have primary EventTime field. It is recorded by server time in unix timestamp. The owner can choose timezone to display their data in reports. We have EventDate field that is calculated from EventTime using this timezone.
In addition we also have ClientEventTime field that stores unix timestamp on website visitor machine (from JavaScript code). And also we have ClientTimeZone that store UTC offset on user machine at this moment of time. These fields are not widely used: we cannot trust JavaScript code running in visitor's browser. But Yandex.Metrica user can use these fields for custom reports.
Also the difference in ClientEventTime is used for correcting of EventTime of events buffered in web browser that will be sent later.

@imiskolee can you please descibe your usecase? The best workaround in Common case is to store offset in minutes in separate field.
I.e.
create table x (
time_utc DateTime,
tz_offset Int32) engine=Log;

Insert into x values (now(), 3600), (now() + 1, -7200):

Select toString(time_utc + tz_offset) from x;

@filimonov I using a string timezone field like "HongKong/Asia". but we also can be try using offset,but need migrate. thanks!


fix: bump to Edge Runtime 1.5.1

What kind of change does this PR introduce?

add navigator global (77ebaf1)
handling concurrent requests to workers (d47f05d)

Also, set the worker timeout to 1 min.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
7 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 61.801%

Files with Coverage Reduction
New Missed Lines
%

internal/gen/keys/keys.go
7
7.94%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
4750

Relevant Lines:
7686

💛  - Coveralls

Let's merge this after stable release tmr to give it more time for testing.


Pass runtime variables to test functions

Is your feature request related to a problem? Please describe.
As a user I would like to access runtime variables in test functions
Describe the solution you'd like
The test functions should accept a kwargs argument like other block functions:
@test
def test_data_readiness(df: pd.DataFrame, *args, **kwargs) -> None:
  pass

Describe alternatives you've considered
Additional context

heyr @lucafaggianelli, a fix for this issue is included in the latest mage version. let me know if you have any further issues


Automated cherry pick of #8640: fix(notify): customize the title of the verification email based on the copyright

Cherry pick of #8640 on release/3.5.
#8640: fix(notify): customize the title of the verification email based on the copyright

Codecov Report

Merging #8641 into release/3.5 will increase coverage by 11.88%.
The diff coverage is 0.00%.

@@               Coverage Diff                @@
##           release/3.5    #8641       +/-   ##
================================================
+ Coverage         6.14%   18.02%   +11.88%
================================================
  Files              761       84      -677
  Lines           118373     8827   -109546
================================================
- Hits              7269     1591     -5678
+ Misses          110445     7067   -103378
+ Partials           659      169      -490

Flag
Coverage Δ

aFlag
18.02% <0.00%> (+11.88%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/apigateway/handler/init.go
100.00% <ø> (ø)

pkg/monitor/alerting/conditions/metricquery.go
0.00% <0.00%> (ø)

pkg/keystone/models/idp_remote_ids.go

pkg/mcclient/options/routetables.go

pkg/compute/models/elasticcacheresource.go

pkg/monitor/alerting/result_handler.go

pkg/multicloud/ucloud/network.go

pkg/compute/models/groupguests.go

pkg/cloudprovider/securitygroup.go

pkg/cloudcommon/db/quotas/errors.go

... and 616 more

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 b5b1ce6...835a4c4. Read the comment docs.


Suppress CVE-2022-46337 and CVEs below score of 9 for the patch branch

Suppress CVE-2022-46337 and CVEs below the score of 9 for the patch branch to ensure that the build process goes smoothly since this is a patch release on top of 28.0.0.
CVE-2022-46337 has a high CVSS score (>9), however, it is suppressed in the master branch since it doesn't apply to Druid, but the patch couldn't be backported cleanly

Failures are unrelated.


Generated standalone parsers are not always identical for the same input

Given a fixed grammar file to generate a standalone parser using lark.tools.standalone, the resulting generated code is not always identical despite setting PYTHONHASHSEED.
Note that the syntax tree given by the parser is fine. This is just about the generated code not being static. People who try to generate a standalone parser and commit the code to their repository will find diff just by regenerating the parser, even if the grammar file has not changed.
To Reproduce
Grammar grammar.lark:
?start: item1* item2

item1: "a"
item2: "b"

Script to generate standalone parser:
export PYTHONHASHSEED=1
python -m lark.tools.standalone grammar.lark > file1.py
python -m lark.tools.standalone grammar.lark > file2.py
diff file1.py file2.py

Ideally, the diff should report nothing. However the diff almost always reports some differences. It seems those differences always appear in DATA and MEMO.
lark-parser version: 0.8.5
Python version: 3.8
OS version: Mac OSX 10.15

Ah, a simpler grammar file would also reproduce this:
start: item
item: "a"

But the differences occur less often.

Can not reproduce when PYTHONHASHSEED is set. Without (or with =random, or with -R flag), can reproduce.

This can happen because the hashes change between runs (which PYTHONHASHSEED should solve) but also because the id() function returns different values. That causes certain operations to occur at arbitrary order.
I don't consider this a bug, but I will accept a PR that fixes it.
Probably the easiest fix would be sorting the culprits during serialization, but that might not be enough. Possibly some of the id() calls will have to be replaced with more deliberate indexing.
Meanwhile I can recommend only generating the standalone parser if the file is modified (can be tested by date or hash of grammar).


add crd for dynamic provisioning

Description
Adds the CRD for dynamic provisioning and kubebuilder boilerplate
Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Tested all gen code and generated crd is correct. That's all this PR does for now.
Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

8 of 10 (80.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.05%) to 88.669%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controller/controller.go
8
10
80.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.05%

Covered Lines:
1972

Relevant Lines:
2224

💛  - Coveralls

// ObjectReference contains enough information to let you inspect or modify the referred object.
// ---
// New uses of this type are discouraged because of difficulty describing its usage when embedded in APIs.
//  1. Ignored fields.  It includes many fields which are not generally honored.  For instance, ResourceVersion and FieldPath are both very rarely valid in actual usage.
//  2. Invalid usage help.  It is impossible to add specific help for individual usage.  In most embedded usages, there are particular
//     restrictions like, "must refer only to types A and B" or "UID not honored" or "name must be restricted".
//     Those cannot be well described when embedded.
//  3. Inconsistent validation.  Because the usages are different, the validation rules are different by usage, which makes it hard for users to predict what will happen.
//  4. The fields are both imprecise and overly precise.  Kind is not a precise mapping to a URL. This can produce ambiguity
//     during interpretation and require a REST mapping.  In most cases, the dependency is on the group,resource tuple
//     and the version of the actual struct is irrelevant.
//  5. We cannot easily change it.  Because this type is embedded in many locations, updates to this type
//     will affect numerous schemas.  Don't make new APIs embed an underspecified API type they do not control.
//
// Instead of using this type, create a locally provided and used type that is well-focused on your reference.
// For example, ServiceReferences for admission registration: https://github.com/kubernetes/api/blob/release-1.17/admissionregistration/v1/types.go#L533 .

Probably need to switch from the ObjectReference type


Comparison operators on dtypes

@jit(nopython=True)
def delta_mat(m,d):

	size = m.size

	if size == 1:
		return np.full(fill_value=np.nan,shape=(1,1),dtype=np.float32)

	if m.dtype != np.float32:
		return np.full(fill_value=np.nan,shape=(1,1),dtype=np.float32)

	rowNum = m.shape[0]
	colNum = m.shape[1]

	if rowNum <= d + 20:
		return np.full(fill_value=np.nan,shape=(rowNum,colNum),dtype=np.float32)

	return m[d:] - m[:(rowNum-d)]

m1 = np.random.randn(400,4000).astype(np.float32)
ans = delta_mat(m1,10)

TypingError: Failed in nopython mode pipeline (step: nopython frontend)
Invalid use of Function(<built-in function ne>) with argument(s) of type(s): (dtype(float32), class(float32))
Known signatures:
 * (bool, bool) -> bool
 * (int8, int8) -> bool
 * (int16, int16) -> bool
 * (int32, int32) -> bool
 * (int64, int64) -> bool
 * (uint8, uint8) -> bool
 * (uint16, uint16) -> bool
 * (uint32, uint32) -> bool
 * (uint64, uint64) -> bool
 * (float32, float32) -> bool
 * (float64, float64) -> bool
 * (complex64, complex64) -> bool
 * (complex128, complex128) -> bool
 * parameterized
In definition 0:
    All templates rejected with literals.
In definition 1:
    All templates rejected without literals.
In definition 2:
    All templates rejected with literals.
In definition 3:
    All templates rejected without literals.
In definition 4:
    All templates rejected with literals.
In definition 5:
    All templates rejected without literals.
In definition 6:
    All templates rejected with literals.
In definition 7:
    All templates rejected without literals.
In definition 8:
    All templates rejected with literals.
In definition 9:
    All templates rejected without literals.
In definition 10:
    All templates rejected with literals.
In definition 11:
    All templates rejected without literals.
In definition 12:
    All templates rejected with literals.
In definition 13:
    All templates rejected without literals.
In definition 14:
    All templates rejected with literals.
In definition 15:
    All templates rejected without literals.
In definition 16:
    All templates rejected with literals.
In definition 17:
    All templates rejected without literals.
In definition 18:
    All templates rejected with literals.
In definition 19:
    All templates rejected without literals.
In definition 20:
    All templates rejected with literals.
In definition 21:
    All templates rejected without literals.
In definition 22:
    All templates rejected with literals.
In definition 23:
    All templates rejected without literals.
In definition 24:
    All templates rejected with literals.
In definition 25:
    All templates rejected without literals.
In definition 26:
    All templates rejected with literals.
In definition 27:
    All templates rejected without literals.
This error is usually caused by passing an argument of a type that is unsupported by the named function.
[1] During: typing of intrinsic-call at <ipython-input-828-786c27396a32> (9)

File "<ipython-input-828-786c27396a32>", line 9:
def delta_mat(m,d):
    <source elided>

	if m.dtype != np.float32:
 ^

np.version  : '1.17.2'
numba.version:  '0.48.0'

If you'd like to have a function behave differently for different dtypes of the arguments, you can use generated_jit to specify the implementation for each different dtype - rewriting your example using it gives:
from numba import generated_jit
from numba.types import float32
import numpy as np

@generated_jit(nopython=True)
def delta_mat(m, d):
    if m != float32:
        def impl(m, d):
            return np.full(fill_value=np.nan, shape=(1, 1), dtype=np.float32)
    else:
        def impl(m, d):
            size = m.size
            if size == 1:
                return np.full(fill_value=np.nan, shape=(1, 1),
                               dtype=np.float32)

            rowNum = m.shape[0]
            colNum = m.shape[1]

            if rowNum <= d + 20:
                return np.full(fill_value=np.nan, shape=(rowNum, colNum),
                               dtype=np.float32)

            return m[d:] - m[:(rowNum-d)]

    return impl

m1 = np.random.randn(400, 4000).astype(np.float32)
ans = delta_mat(m1, 10)

Here when delta_mat is called, the delta_mat function is called with the types of the arguments, which it uses to choose which implementation to return - the returned implementation is then compiled and called on the actual arguments to the delta_mat function.
The generated_jit decorator is mentioned here in the documentation: http://numba.pydata.org/numba-doc/dev/reference/jit-compilation.html?highlight=generated_jit#generated-jit-functions

Reminder for me... think this is a candidate for a branch pruning enhancement, the dtype's are available at compile time? May get strange due to dtype types though.

I was also thinking it would be good for that, but I couldn't see a way to write the branch condition in nopython mode.

Probably needs some overloads adding for operator.<comparator>. e.g.
from numba import njit, types
import numpy as np
import operator

from numba.extending import overload

@overload(operator.eq)
def ol_eq_dtype(a, b):
    if (isinstance(a, types.functions.NumberClass) and
        isinstance(b, types.functions.NumberClass)):
        pred = a is b
        def impl(a, b):
            return pred
        return impl

@njit
def foo(ty1, ty2):
    if ty1 == ty2:
        return 1
    else:
        return 2

print(foo(np.float32, np.float32))
print(foo(np.float32, np.float64))

@stuartarchibald Just to confirm, are you suggesting that these could / should also be added to Numba itself, and not just something the user is expected to include in their code?

@gmarkall I think comparison operators for dtype types is something Numba {c,sh}ould support, it seems reasonable to want to do something like this in user defined code and it looks like it's possible to make it work. I think it ought to be part of Numba core, users shouldn't have to write this.

@stuartarchibald   Yes you are right.
And I also report a bug which is also about dtype comparison
in :
dtype('<type_as_str>') == 'type_as_str' incorrectly evaluates to False when compiled. #5255
#5255

Updated title to reflect issue.

Removing the question label so the bot won't mark it stale again.


Shake can't handle ninja line continuation between : and rule on build line

This is a snippet from a larger build.ninja file that shake seems to choke on. If I remove the $ and join the lines, it seems to succeed (or at least gets further).
rule COMPILER_TIMESTAMPS
  command = $PYTHON src/mongo/db/modules/ninja/touch_compiler_timestamps.py $in $out
  description = Checking for compiler upgrades
  pool = local
  restat = 1

build build/compiler_timestamps/_bin_g++.mtime build/compiler_timestamps/_bin_g++.last_update: $
    COMPILER_TIMESTAMPS /bin/g++

shake: Error when running Shake build system:
* +bson_obj_test
* build/ninja/mongo/bson/bson_obj_test
* build/ninja/mongo/util/debugger.o
* build/compiler_timestamps/_bin_g++.last_update
* build/compiler_timestamps/_bin_g++.mtime build/compiler_timestamps/_bin_g++.last_update
* COMPILER_TIMESTAMPS
Error, file does not exist and no rule available:
  COMPILER_TIMESTAMPS
CallStack (from HasCallStack):
  error, called at src/Development/Shake/Internal/Rules/File.hs:171:58 in main:Development.Shake.Internal.Rules.File

> shake --version
Shake build system, version 0.16

Fixed! Thanks for the report.


feat(esm): move to ESM

Current dependencies on/for this PR:

main

PR #22   👈

This comment was auto-generated by Graphite.


async-loaded scripts in v3 throw invariant errors

Example at: https://github.com/exoplay/exobot-docs (npm run build)
next server works great, and next export works great when loading docs/index.html locally. however, as soon as you push the static site generated by next.js to a remote server - in my case, github pages - all kinds of react errors occur, such as invariant errors relating to "not finding element id of undefined". If you remove the async="" property from the script tags that load each page's code, everything works perfectly fine.
I haven't started tracking down the error yet, but did want to make you aware that at least in v3.0.0-beta.8, async-loading scripts is broken. I don't think I'm doing anything weird in my project. It's fairly simple to set up and run the example, but let me know if you have any questions about what I've written if I haven't updated this issue with more detail by the time you look at this.

Interesting.
I'd like to have a look at this first.

There are some issues in this repo. I can't work properly.
Remove your node_modules directory and run it.
You'll see the errors.
Fix me and send that to me.
But I'm guessing the issue with deploying the app into a sub directory.
We haven't address that yet in whole Next.js deployments.
We need to do it separately. May be after 3.

Re-open this when you update the repo.

Updated; bumped next.js and added react to the package.json.

I'm guessing the issue with deploying the app into a sub directory.

That would cause async loading issues? The files get loaded, but the dependencies are out of order.

You didn't push changes to github.
And try to do npm run export as well.
Also check the browser console. There are some errors as well.

That would cause async loading issues? The files get loaded, but the dependencies are out of order.
I can't tell anything without looking at this.

 Done - npm run build runs the export.
You'll need to update siteRoot to "." in pages/routes to run locally, or leave empty for a web server running from/.

I'm going to close this as it's over a year old and from the sound of it can now be handled by using assetPrefix and the multi-zones feature


[Bug]: Banner plugin

Feature Requested
Hi, I would like to know if you could fix the way the banner plugin behaves inside the shimmering theme. The problem is that the images appear centered, I guess the theme uses by default the default cssclass for images of the theme and therefore does not use the plugin settings.
Relevant Screenshot
Right now it looks like this

It should look like this (Minimal Theme)

Relevance

[x] The feature would be useful to more users than just me.

Style Settings

[X] I have checked that the feature is not already available via the Style Settings plugin.

fixed in latest release

There is a gap at the top of the banner, is this intentional ?
https://user-images.githubusercontent.com/38974541/166684982-3957ad07-500a-4135-9d16-d425c8ebf91a.mov

Probably not, that space is actually the hot zone that actives the hidden header bar. The css for the hidden header bar is kinda tricky, I don't know whether it is possible to have a hidden header bar and the banners plugin active at the same time.

The gap persists even if the header bar is visible.

Alright.


Transform notifications (NOTIFICATION_TRANSFORM_CHANGED) are no longer received once a Tween has been used

Godot version:
3.1.2 (Mono)
OS/device including version:
Windows 10
Issue description:
If a Tween is used to translate a node (or a parent of that node), then notifications of type NOTIFICATION_TRANSFORM_CHANGED stop being sent for that node.
I am unsure if other notifications are also interfered with.
Steps to reproduce:

Listen for transformation changes on a node by calling set_notify_transform(true).
Scale the node with the 'scale' property, and notice a transformation notification is received (via the func _notification(what): callback).
Use a tween to adjust the scale property on the same node . Notice no transformation notification is received.
(Optional) Scale the node again directly with scale property. Notice no transformation notification is received.

Minimal reproduction project:
Testing-TweenNotification.zip
Object listening for notifications is in ListeningNode.gd. Tween via code in Scene.gd.

Seems to be related to this lines:
https://github.com/godotengine/godot/blob/a7f49ac9a107820a62677ee3fb49d38982a25165/scene/2d/canvas_item.cpp#L955-L957
Basically, when the global_invalid flag is raised, the node will no longer propagate transform changes. global_invalid is set to true whenever the global_transform is known to be invalid, and is reset to false when global_transform's getter is invoked.
This means that changing scale to global_scale in the print on the listening node in the project happens to resolve the issue. And indeed, it does.

Still valid in d395f7082

Still valid in 78e3e65
After some testing, this is not related to Tweens (happens also in _proces()). The problem is wrong documentation and unexposed NOTIFICATION_LOCAL_TRANSFORM_CHANGED constant. When changing global transform (position/rotation/scale), the NOTIFICATION_TRANSFORM_CHANGED is received properly. But the example project is changing local transform, so I assume this is why the notification isn't sent. It should use set_notify_local_transform(). The notification is not exposed as constant, but it's properly received (35).
The documentation wrongly states that NOTIFICATION_TRANSFORM_CHANGED is received both with set_notify_local_transform and set_notify_transform.

If I try to change a transform using interpolate_method, the rotation doesn't get updated until the Tween is finished, is that related to this issue, perhaps? I've included a test project here.
error.zip

If I try to change a transform using interpolate_method, the rotation doesn't get updated until the Tween is finished, is that related to this issue, perhaps? I've included a test project here.
error.zip

This was a user error, sorry about that! 🤦♂

I have a Sprite, and Node2D node as a parent of the sprite
I change Node2D position (position.x) using Timer.
And I expect sprite will be notified
But this doesn't happen (it seems this happens only once or twice).
So NOTIFICATION_TRANSFORM_CHANGED is broken.

I have a Sprite, and Node2D node as a parent of the sprite I change Node2D position (position.x) using Timer.
And I expect sprite will be notified But this doesn't happen (it seems this happens only once or twice). So NOTIFICATION_TRANSFORM_CHANGED is broken.
Tested on Godot standard, 3.4.2, 3.5.beta.

Still encountering same issue in 4.2.beta

also tried, still happening on 4.2.1 stable


Added new widget that can be used in forms/validation on either platform.

Was missing having TextField easily usable in Forms, like in the Material widgets, so I adapted PlatformTextField into a FormField.

I was just missing this and found this PR while looking for a solution on how to handle validation.
I just don't think that another widget is required, since PlatformTextField could simply be updated to work with forms.

PlatformTextField is just delegating to the Material and Cupertino equivalent widgets. As with how flutter does it it probably would be better to have a separate widget, though this PR although a great contribution is going beyond my initial intent of the project to be a simple delegation to the underlying Material and Cupertino widgets,

@aqwert I have just checked the documentation and found out what my confusion could be about:
There's a platform agnostic FormField widget that should be used in forms for validation and other Form related needs. There is also a Material widget TextFormField, which is nothing but a Material TextField wrapped in a FormField, that is described here like this:

To integrate the TextField into a Form with other FormField widgets, consider using TextFormField.

The issue is that there's no Cupertino version of the Material TextFormField, which would be called CupertinoTextFormField and, as the Material counterpart, be a CupertinoTextField wrapped in FormField. There is already an open issue asking for this and some complaints too.
As I understand, what @eyecreate has done in the PR is to wrap the PlatformTextField in a FormField, but actually what needs to be done is to implement the missing wrapper directly in flutter, so that flutter_platform_widgets can simply have a PlatformTextFormField that would delegate to either TextFormField or CupertinoTextFormField, instead of any actual implementation. So I have created a PR there with the necessary implementation and, as soon as it reaches the stable channel, we can update this PR so that the PlatformTextFormField is changed to be a simple the delegation.
Until then, the solution is to implement the validation either using the onChanged (for simple cases) or the controller (for more complex cases) properties (docs for these options), depending on your needs.
Here is an example using the PlatformTextField with both manual validation methods:
import 'package:flutter/widgets.dart';
import 'package:flutter_platform_widgets/flutter_platform_widgets.dart';

class MyWidget extends StatefulWidget {
  MyWidget({Key key}) : super(key: key);

  @override
  _MyWidgetState createState() => _MyWidgetState();
}

class _MyWidgetState extends State<MyWidget> {
  final _inputTextController = TextEditingController();

  @override
  void initState() {
    super.initState();

    // Start listening to changes.
    _inputTextController.addListener(_handleInputChange);
  }

  @override
  void dispose() {
    // Clean up the controller when the widget is removed from the widget tree.
    // This also removes the _handleInputChange listener.
    _inputTextController.dispose();
    super.dispose();
  }

  bool _myValidationMethod(String text) {
    // Just an example of a validation that can be done
    return text.isNotEmpty;
  }

  void _handleInputChange() {
    print("Is input from `controller` valid? ${_myValidationMethod(_inputTextController.text)}");
  }

  @override
  Widget build(BuildContext context) {
    return Container(
      child: PlatformTextField(
        controller: _inputTextController,
        onChanged: (value) => {
          print("Is input from `onChanged` valid? ${_myValidationMethod(value)}")
        },
      ),
    );
  }
}

Cheers!

Having a Cupertino TextFormField in flutter is likely a better way to handle this, considering what @aqwert wants in this project.
That being said, one thing missing from what you have submitted to flutter is validation error handling like in the material widget. Arguably, this isn't supported natively on the iOS widget and so shouldn't be implemented(cupertino widget has no decoration for error text), but it leaves functionally different implementations for each platform where one platform user knows the validation errors made and one doesn't. I could see doing manual validation for cupertino if the rest of the interface knew it was cupertino, but these widgets wrap both. Should there then be something like CupertinoTextFormFieldData with something like a callback function to handle error responses in the style of other platform specific data other widgets in this library use?

Yes @eyecreate, I think that what you're looking for is not going to be neither a part of this project nor of the flutter itself.
The validation errors handlers are part of the Material Design Guidelines and the iOS guidelines do not say anything about this topic, so it doesn't make sense for anyone to make assumptions and enforce a single way of doing it.
You probably will have to create your own solution (a wrapper, maybe?) using the isCupertino method from this package to handle this on the iOS side, since the decoration property is a whole widget (InputDecorator) that handles the validation errors in the TextField, while in the CupertinoTextField it is a simple BoxDecoration, so you can't actually do much there.
In any case, I may need a solution for this myself really soon and I can share it here as soon as I have it.
Cheers!

Closing this as this seems unlikely to be merged and some upstream flutter PRs could make this irrelevant.


Fix for wrong docker version in Readme.md and docker-compose-deploy.yml

Examples of docker-compose.yml in Readme.md are not working since the version of docker image (1.5.0) doesn't exist, it is actually labeled with v1.5.0.

Thanks for the fix!
I switch the build from docker autobuilds to Circle CI and I missed this part.

Awesome, thanks you, this is a great product :D


Default custom transitions

It would be nice to have custom transitions in flutter_navigation_generator so you don't have to write them again in different projects.
In https://github.com/ikbendewilliam/get_x_navigation_generator we had transiation which makes it easier to play around with different transitions without having to write everything again from scratch

Basic native animations have been added in a new package https://pub.dev/packages/flutter_navigation_generator_animations/


HTTP Service invocation: Add native synchronous execution

When the loop is already running, the following line will raise the RuntimeError: This event loop is already running:
https://github.com/dapr/python-sdk/blob/033acbc92b4c4b40577c603aa5b03694eb74e295/dapr/clients/http/dapr_invocation_http_client.py#L161
This happens when the following line returns an already running loop:
https://github.com/dapr/python-sdk/blob/033acbc92b4c4b40577c603aa5b03694eb74e295/dapr/clients/http/dapr_invocation_http_client.py#L147

This is too much work to fix for the upcoming release. Clearly calling the asynchronous implementation from a synchronous context isn't working for every situation.
Can you please call async def invoke_method_async instead?

We basically need synchronous method implementation of DaprHttpClient and then use that in the invoke_method implementation in DaprInvocationHttpClient. And we need additional tests for this.

For the time being, please use the example shown here which uses Python requests directly for a basic service invocation call. As long as you set the dapr-app-id header and specify the sidecar address as destination, any path will be routed to the target app and invoked accordingly. There is no need to use the Python SDK.
https://github.com/dapr/quickstarts/blob/master/service_invocation/python/http/checkout/app.py


Add more documentation links

https://github.com/sindresorhus/awesome-nodejs/blob/master/contributing.md

Make an individual pull request for each suggestion.

I also highly doubt all those are awesome. This is a curation. Pick the best one(s).

Hah, sorry for that. I was essentially mirroring it from other existing awesome-lists.


Remove unused snippets.

These snippets have been moved to firebase-admin-python
cc @hiranya911 @avishalom

LGTM 👍


Add a representation to the class

This enables users to do a print(folio_client) and get more than a class name and a memory reference

Big thanks, @JensHeinrich!


goto api hangs up

Expected behavior
goto api should navigate to the required url successfully.
Actual behavior
goto api hangs up. Unable to navigate required url.
Steps to reproduce

openBrowser()
goto("Google.com")
openTab()
closeTab("Google")
goto("taiko.gauge.org")

Versions
Version: 1.0.2 (Chromium: 76.0.3803.0) 22a7d58c629864e04042d4661046d0c3e8e802cd

This issue has been verified and found fixed.
Tested version:
Version: 1.0.2 (Chromium: 76.0.3803.0) 385bada65f371641fe775b2ee5a79ca5aaf2bd71


Unexpected "statements are not aligned" error for unnecessary semicolon

Bug Report
The align rule is reporting "statements are not aligned" for unnecessary semicolons.  This isn't a huge problem, because one should not use unnecessary semicolons anyway, but it is confusing and it would be better if the align rule left that up to the semicolons rule, whose complaint "Unnecessary semicolon" is more to the point.

TSLint version: 5.1.0
TypeScript version: 2.2.2
Running TSLint via: CLI

TypeScript code being linted
function test() {
};

with tslint.json configuration:
{
  "rules": {
      "align": [true, "statements"]
  }
}

Actual behavior
ERROR: test.ts[2, 2]: statements are not aligned

Expected behavior
No error.

I looked into this.  I think this behavior began at commit c1a167e, where the align statements test was updated to make sure this behavior happens.  Looks like this was either part of fixing #2366, or of a general enhancement to the align rule.
I think this particular behavior is incorrect.  Yes, technically the empty statement created by the semicolon is a statement, and yes it doesn't align with the previous statement.  But I think this results in a confusing message to the user.
I suspect it can be easily avoided by ignoring empty statements in this rule.  For instance, by changing node.statements at alignRule.ts:85 to node.statements.filter(s => !isEmptyStatement(s)).

I suspect it can be easily avoided by ignoring empty statements in this rule. For instance, by changing node.statements at alignRule.ts:85 to node.statements.filter(s => !isEmptyStatement(s)).

@sbj42 You're right, that's the only thing needed to fix this. Would you mind to submit a PR with that fix?
Unnecessary semicolons in classes will result in a similar problem with option "members". There should be a filter for SemicolonClassElement added to line 138.

Done.  So far I can't seem to get "members" to work.  I might be just doing it wrong.

I'm satisfied with the resolution of this issue.  @ajafff mentioned a possible related issue at this comment, but I don't know how to cause it - perhaps that can be submitted as a separate issue if someone produces a test case for it.

@sbj42 I just opened #2668 to fix the problem with SemicolonClassElement that I mentioned above


GRPC and protos

Description of changes
Summarize the changes made by this PR.

Improvements & Bug fixes

...

New functionality

...

Test plan
How are these changes tested?

[ ] Tests pass locally with pytest for python, yarn test for js, cargo test for rust

Documentation Changes
Are all docstrings for user-facing APIs updated if required? Do we need to make documentation changes in the docs repository?

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#2396  👈
#2338
#2300 : 1 other dependent PR (#2265 )
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @atroyn and the rest of your teammates on  Graphite


Wagtail 5 breaks project

under wagtail 5 the project will not load as its using removed / changed namespace references - I tested changing the namespaces and the code runs - but the custom menu registration functions don't work under wagtail 5 (or 4.2)

Anyone working on this? I'm happy to attempt a fix if not.

Anyone working on this? I'm happy to attempt a fix if not.

Not currently no, feel free to take it on.
I also don't mind doing a new release with a minimum version of 5.0+ is backwards compatibility is too much of a problem. People can always install older version of birdsong for older versions of wagtail

I opened a pull request on this regard.
https://github.com/neon-jungle/wagtail-birdsong/pull/42


Add ColorFilter.cube to apply 3D lookup table

Blocked by https://github.com/flutter/flutter/issues/94235
Use case
It would be nice to be able to add 3D LUT based, artistic color filters on any widget. Especially Image, VideoPlayer and CameraPreview widgets. 3D Lookup Tables are heavily used in the film and game industry for color correction and creative color grading. On mobile platforms they would be especially useful for all kinds of photo / video editor type tools.

image by Caique Silva LUTs: KURO B&W by David Morgan Jones, Arabica 12 and Lenox 340 by rocketstock
Alternatives

On still images the dart_lut plugin could be used.

On iOS and macOS one could fork the video_player plugin and use a CIColorCube filter.

ColorFilter.matrix can not be used as an alternative as it is not as precise.
Proposal
Convince the Skia team to revert https://github.com/google/skia/commit/efaad3cd53330f063e6feaee8b14ad43ca251184 so SkColorCubeFilter could be used by Flutter. Relevant discussion could be found here.

@iapicca I don't think this can be done in a package. As far as I understand it would need to be added to the engine and even to Skia. If you see a way to do it from a package or in a simpler way please let me know.

Skia team kindly added an example of how to implement a 3D LUT filter using SkRuntimeEffect: https://github.com/google/skia/blob/master/gm/runtimeshader.cpp#L241-L333

Adding a 3D LUT is now possible in the main and dev branch using FragmentProgram with an ImageShader and toImage methods of the render layer as an input.
Creating a ColorFilter needs some more work and is tracked in https://github.com/flutter/flutter/issues/94235.

From feature request triage: The equivalent functionality should be provided using a fragment program rather than the old Skia API.

@zanderso it seems like the main blocker here of using a FragmentProgram versus a ColorFilter is that there are no ways to synchronously obtain Image objects holding the content of a widget that can be provided to shaders. (every toImage method returns a Future<Image>. To me this implies that using a FragmentProgram to process the contents of a widget must be non-realtime - Providing an alternate, synchronous toImage method or allowing the construction of ColorFilters are the only solutions I'm aware of right now, is there an alternative?

Are there any code examples of how to apply a LUT to a Widget?

On flutter beta and master there are RenderRepaintBoundary.toImageSync  and friends.

We're not going to write this particular filter in the engine, but we will be exposing mechanisms to make writing these filters much simpler. Closing as dupe of https://github.com/flutter/flutter/issues/16296


sliderPerView: 'auto' is moving slides too far to the left

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: 4.2.2

Platform/Target and Browser Versions: Platform all, target IE11, Edge, Chrome, Safari

https://www.sff.org.au/program/browse/ghost-stories (swiper instance is accessible at window.slider)

What you did
this.slider = new Swiper(this.element[0], {
   speed: 600,
   slideToClickedSlide: true,
   autoplay: {
     delay: 5000,
     disableOnInteraction: false
   },
   preloadImages: false,
   watchSlideVisibility: true,
   loop: true,
   loopedSlides: this.children.length,
   slidesPerView: 'auto',
   loopAdditionalSlides: this.children.length,
   keyboard: {
      enabled: true,
      onlyInViewport: false
   },
   on: {
      slideChangeTransitionEnd: animateButton(this, $),
         lazyImageReady: function (...els) {
            // Fade in animation
            anime({
               targets: els,
               opacity: [0, 1],
               duration: 600,
               easing: 'easeOutQuad'
            })
         }
      }
   })

this.slider = new Swiper(this.element[0], {
   speed: 600,
   slideToClickedSlide: true,
   autoplay: {
     delay: 5000,
     disableOnInteraction: false
   },
   preloadImages: false,
   watchSlideVisibility: true,
   loop: true,
   loopedSlides: this.children.length,
   // slidesPerView: 'auto',
   loopAdditionalSlides: this.children.length,
   keyboard: {
      enabled: true,
      onlyInViewport: false
   },
   on: {
      slideChangeTransitionEnd: animateButton(this, $),
         lazyImageReady: function (...els) {
            // Fade in animation
            anime({
               targets: els,
               opacity: [0, 1],
               duration: 600,
               easing: 'easeOutQuad'
            })
         }
      }
   })

Expected Behavior
Slides should be at the same position when slidesPerView is set and unset
Actual Behavior
On slidesPerView: 'auto' slides are being positioned incorrectly to the left

Live example or JSFiddle with the issue?

I'm having this issue too. The demo shows  slidesPerView:'auto' and centerSlides:true, and the first slide is centered
When i do the same thing the first slide is all the way to the left of the container, not in the center.


Disable .NET Core tiered compilation

I got worse perf with tiered compilation enabled. It will be enabled by default in .NET Core 3.0.

Is this something that you were able to report to CoreCLR?

Enabling AggressiveOptimization didn't do much. Possibly related to:
https://github.com/dotnet/coreclr/issues/20282
https://github.com/dotnet/coreclr/issues/19752


Improve logging when adding worker when there is no etcd/controlplane node present

Rancher versions:
rancher/server: v2.0.0-beta1
rancher/agent: agent:v2.0.0-beta1
Docker version:
Server Version: 17.03.2-ce
Operating system and kernel:
Ubuntu 16.04.4 LTS (Xenial Xerus)"
4.13.0-38-generic
Type/provider of hosts:
VMware vSphere
Setup details:
1 master
3 workers
Steps to Reproduce:

Create new cluster
Add custom worker only node
copy and paste custom docker run command on the worker node
agent container starts, but can not register with master
Results:
Docker Logs output (worker):

time="2018-04-06T09:59:44Z" level=info msg="Option worker=true"
time="2018-04-06T09:59:44Z" level=info msg="Option requestedHostname=worker02"
time="2018-04-06T09:59:44Z" level=info msg="Option customConfig=map[address:<IP_ADDRESS> internalAddress: roles:[worker]]"
time="2018-04-06T09:59:44Z" level=info msg="Option etcd=false"
time="2018-04-06T09:59:44Z" level=info msg="Option controlPlane=false"
time="2018-04-06T09:59:44Z" level=info msg="Connecting to wss://master01.<domain>/v3/connect/register with token zgbp6fr46ncqvxjbk2z76jtc4l2lmpfkb4krq6hj7mdfnwvb6bfpr6"
time="2018-04-06T09:59:44Z" level=info msg="Connecting to proxy" url="wss://master01.<domain>/v3/connect/register"
time="2018-04-06T10:20:45Z" level=info msg="Error while getting agent config: invalid response 500: secrets \"c-cluster-lwvm6\" not found"
time="2018-04-06T10:20:50Z" level=info msg="Error while getting agent config: invalid response 500: secrets \"c-cluster-lwvm6\" not found"

Hi,
You don't need to have at least 1 etcd and 1 controlplane ?
You can't have just 3 workers.

@cuseinovic Fixed. Could be a improvement for the dashboard when creating a new cluster.

@gwiersma Your welcome :)
Indeed, it will be great to know in the Dashboard the number of etcd, controlplane, workers like in rancher 1.6

I ran into the same problem. From the comments, I can't work out what is the solution - do I need separate nodes for etcd / control? In the latest version, there are checkboxes for them and looks like you can create an agent to do all three - that's what I was trying to do, but still get the same error message. What can I try next?

I'm getting the same issue as @ipeevski
I spin up the server, add a cluster with custom as I am installing on baremetal, check all three boxes, copy the docker command and I still get the same error message:
"Error while getting agent config: invalid response 500: secrets \"c-cluster-p65j5\" not found"

I  think after installing kubernetes on the underlying machine, it started working for me ...

Please share complete logging of the rancher/server and rancher/agent container when this happens.

Hi!
Having the same problem here when trying to create a new cluster. here's the output from the agent:
time="2018-04-11T13:39:49Z" level=info msg="Option worker=true"
time="2018-04-11T13:39:49Z" level=info msg="Option requestedHostname=*********"
time="2018-04-11T13:39:49Z" level=info msg="Option customConfig=map[address:******** internalAddress: roles:[etcd worker controlplane]]"
time="2018-04-11T13:39:49Z" level=info msg="Option etcd=true"
time="2018-04-11T13:39:49Z" level=info msg="Option controlPlane=true"
time="2018-04-11T13:39:49Z" level=info msg="Connecting to wss://rancher.********/v3/connect/register with token tlpbmlz4sknzqlfbx44kdbs9264rd7rwv9qktngqr6gdkk5j6sbrjt"
time="2018-04-11T13:39:49Z" level=info msg="Connecting to proxy" url="wss://rancher.********/v3/connect/register"
time="2018-04-11T13:39:49Z" level=info msg="Error while getting agent config: invalid response 500: secrets \"c-cluster-jjqnx\" not found"
time="2018-04-11T13:39:54Z" level=info msg="Error while getting agent config: invalid response 500: secrets \"c-cluster-jjqnx\" not found"
time="2018-04-11T13:39:59Z" level=info msg="Error while getting agent config: invalid response 500: secrets \"c-cluster-jjqnx\" not found"
time="2018-04-11T13:40:04Z" level=info msg="Error while getting agent config: invalid response 500: secrets \"c-cluster-jjqnx\" not found"
time="2018-04-11T13:40:09Z" level=info msg="Error while getting agent config: invalid response 500: secrets \"c-cluster-jjqnx\" not found"

And here are the logs from the rancher master:
E0411 13:34:11.318478       1 tokens_controller.go:259] error synchronizing serviceaccount project-j7grp/default: secrets "default-token-nd4bn" is forbidden: unable to create new content in namespace project-j7grp because it is being terminated.
E0411 13:34:11.330094       1 tokens_controller.go:259] error synchronizing serviceaccount project-j7grp/default: secrets "default-token-hzcg5" is forbidden: unable to create new content in namespace project-j7grp because it is being terminated.
E0411 13:34:11.346113       1 tokens_controller.go:259] error synchronizing serviceaccount project-j7grp/default: secrets "default-token-h74zj" is forbidden: unable to create new content in namespace project-j7grp because it is being terminated.
2018/04/11 13:34:58 [INFO] Handling backend connection request.
2018/04/11 13:35:33 [INFO] Handling backend connection request.
2018/04/11 13:36:36 [INFO] Handling backend connection request.
2018-04-11 13:37:58.212861 I | mvcc: store.index: compact 21591
2018-04-11 13:37:58.214008 I | mvcc: finished scheduled compaction at 21591 (took 694.774µs)
2018/04/11 13:39:49 [INFO] Handling backend connection request.

I'm kinda lost. Anyone got any idea how to proceed?

I have made a pr to show better error message when agent failed to register. Can you check if you are still seeing that error message time="2018-04-11T13:40:09Z" level=info msg="Error while getting agent config: invalid response 500: secrets \"c-cluster-jjqnx\" not found" in the latest release? This might be related to an improvement fix we recently merged. (https://github.com/rancher/rancher/pull/14567)

Deployed a new cluster yesterday. I haven't seen any errors.

Re-opening to validate the fix in https://github.com/rancher/rancher/pull/15257

Improvement is validated on Rancher:master 1/4
Steps:

Create a new custom cluster
Add one worker only node
copy and paste custom docker run command on the worker node
agent container starts, check its log

Result:
see the following message in the log:
time="2019-01-04T21:32:01Z" level=info msg="waiting for node to register. Either cluster is not ready for registering or etcd and controlplane node have to be registered first"

I have the same error yet and lost a couple of hours but still no solution.
waiting for node to register. Either cluster is not ready for registering or etcd and controlplane node have to be registered first


Support for contextual tuples in model tests

Currently the contextual tuples don't seem to be supported in the model tests, although it is possible using API requests with curl, Postman, etc.
Example:
  - name: User can see account from specific branch
    check:
    - user: user:anne
      object: account:1
      contextual_tuples:
        - user: user:anne
          relation: assignee
          object: branch:lisbon
      assertions:
        can_view: true

It appears this is already supported with the tuple_file: field at the global test and per test level. See the example for fga model test
name: Store Name # store name, optional
# model_file: ./model.fga # a global model that would apply to all tests, optional
# model can be used instead of model_file, optional
model: |
  model
    schema 1.1
  type user
  type folder
    relations
      define owner: [user]
      define parent: [folder]
      define can_view: owner or can_view from parent
      define can_write: owner or can_write from parent
      define can_share: owner
# tuple_file: ./tuples.yaml # global tuples that would apply to all tests, optional
tuples: # global tuples that would apply to all tests, optional
  - user: folder:1
    relation: parent
    object: folder:2
tests: # required
  - name: test-1
    description: testing that the model works # optional
    # tuple_file: ./tuples.json # tuples that would apply per test
    tuples:
      - user: user:anne
        relation: owner
        object: folder:1
    check: # a set of checks to run
      - user: user:anne
        object: folder:1
        assertions:
          # a set of expected results for each relation
          can_view: true
          can_write: true
          can_share: false

Thanks for the issue @mbarralo. @PatrickMunsey is correct that this is achievable using the tuples or tuple_file per test, these tuples will then be used as part of the assertions ran during that test.
Please let us know if you have any further questions about the usage.

Thank you for the reply. For me it seemed more intuitive to think about contextual tuples as something that would be part of the check itself and not part of the tuples that model all checks of the test (hence my example). The distinction of persisted tuples (tuples) and runtime (contextual) tuples could be of value.

For what is worth, is currently at the test level too, just not at each check level, so you can reuse the same contextual tuples for more than one check:
tests: # required
  - name: test-1
    description: testing that the model works # optional
    # tuple_file: ./tuples.json # tuples that would apply per test
    tuples:
      - user: user:anne
        relation: owner
        object: folder:1
    check: # a set of checks to run
      - user: user:anne
        object: folder:1
        assertions:
          # a set of expected results for each relation
          can_view: true
          can_write: true
          can_share: false

If I understand correctly, if you write one test per check, then you can achieve what you want.

Hello @aaguiarz . True. I guess i can consider the tuples of the tests as contextual and the global tuples the "persisted" ones. Like you said, there are different strategies that can be leveraged. Thanks again.

FYI, the proposed approach doesn't behave quite the same as passing contextual tuples in the check call. I think this issue could/should be reopened.
When making a Check API call with contextual tuples if any of those tuples duplicate persisted tuples they're ignored, which allows callers to pass context which may have optionally been persisted. It isn't possible to replicate this behaviour in tests as it seems like all the tuples are merged before use, raising a duplicate tuple in write error.
I can work around this by not including the contextual tuples in my tests when I know they've been "persisted", but I'd prefer to have the checks in the tests mirror the actual check calls as they'd be made.


chat ui first version

Can you please use the Prettier extension to format the file you have edited so that the CI is green? @manojk242003

Please resolve the conflicts!

Fixing the chat UI

Thanks, but the CI is still not green, please fix that too!


eta parameters are trainable

All etas are trainable parameters. You cannot set requires_grad=False for them.

Right! When I was playing around with the author's TF implementation, I noticed that the eta's were staying very close to 1. So for both the TF implementation and my PyTorch implementation, I experimented with fixing them at 1. From the plot in the README, on the simple binarized MNIST problem, the author's TF implementation of REBAR is still able to do quite well without optimizing the etas. So, I think the issue with my code is something else. I'll add the objective for optimizing the etas to my code soon, though. Thanks!


added St. Charles County, MO

Fixed #1996

Testing out the new preview render:

So pretty :)

On Oct 31, 2016, at 10:39, migurski<EMAIL_ADDRESS>wrote:
Testing out the new preview render:
―
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Failure to start with Home Assistant 2022.7.0

After updating to Home Assistant 2022.7.0 I get the following error and no myenergi sensors work anymore. I suspect this to be related to the upgrade to python 3.10 in Home Assistant 2022.7.0.
Setup failed for custom integration myenergi: Unable to import component: No module named 'pymyenergi'
I am happy to provide more information if needed.

I think the problem could be caused by a regression in homeassistant.util.package which I reported in this issue. So presumably there is not much that can be done on the end of this integration.

Thanks for reporting this! I had a look at your reported issue and it seems to have been closed, is the issue resolved?

Yes, HA 7.4 fixes the issue for me. Note however that the issue vanished only after an additional restart of Home Assistant after the restart during upgrade.


20oneprovideronezone_scenario2

Hi,
I am trying to start  the provider service and I am getting:
Attaching to onezone-1
onezone-1                  | Starting oz_panel	[  OK  ]
onezone-1                  |
onezone-1                  | HTTPSConnectionPool(host='<IP_ADDRESS>', port=9444): Max retries exceeded with url: /api/v3/onepanel/zone/configuration (Caused by ProxyError('Cannot connect to proxy.', error('Tunnel connection failed: 403 Forbidden',)))
onezone-1 exited with code 1
I do have no_proxy=”localhost,<IP_ADDRESS>”  configured as well.
How this can be corrected?

@luda171 did you manage to resolve that issue? Also, you say you were trying to start a provider, while in fact the like Attaching to onezone-1 says you are starting a onezone.


Improve documentation

In file https://github.com/pachyderm/pfs/blob/master/README.md it wasn't very clear that pfs in
 curl -XPOST pfs/file/<file>?branch=<branch> -T local_file

Means the host full address of the running pachyderm instance (including port number). Of course it is easy to guess that from https://github.com/pachyderm/chess/blob/master/install/pachyderm/local but it might be worth improving.

It'd be also very useful to add to How do I hack on pfs? section. In particular, I imagine it's possible to git clone pachyderm in some special container, modify go code, recompile and restart server and keep using curl for communication.
Right now I just tried cloning this repo, docker build . and then modifying launch script with the just built image. Highly inefficient.

Definitely agree on both of these points.
What do you think would make it clear in the first case? My instinct would be PFS_HOST, since it makes it clear that we're talking about a hostname and the fact that it's all caps will hopefully indicate that it's not meant literally like the rest of the parts of the path.
As for the second one, what if we had a script scripts/launch-dev which builds an image using the contents of the local directory and then runs the launch script with it as the target?

The PR above contains code which should address this issue.

We're going to a massive documentation improvement this release cycle.


Correct set values for the gateways

Fixes https://github.com/istio/istio/issues/7402

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: ymesika
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: sdake
If they are not already assigned, you can assign the PR to them by writing /assign @sdake in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

content/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Serializing refs

The way the serialise package is currently written, you can serialize any box.  That seems a little weird to me, since it means you can share a ref.  Of course, it will be treated as an iso^ on the other side and so there shouldn't be memory conflicts.  But I'm wondering if there is a reason to limit serializing to val and iso^ only.

If this was closed because you came upon new information or a different perspective, please share what you found so that others who may have the same question can understand.

Good point.  I'll leave it open to hear other opinions.  Talking to @SeanTAllen, it's true that serializing is a form of copying.  My concern was that even given this, it feels weird to send a ref across the wire, even though since you're actually copying, it's still safe.

I closed it because I wasn't sure I had a point.

@jtfmumm i dont think you have a point ;)

Thanks for the explanation - I wasn't asking you to re-open it, just to make the explanation public for others.


Adding tyk capabilities

Changes
Adding different Tyk capabilities to the Tyk APIs.
Merge Requirements
For new features contributions please make sure you have completed the following
essential items:

[ ] CHANGELOG.md updated to document new feature additions
[ ] Appropriate documentation updates in the docs folder

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

In this PR we're adding some Tyk capabilities to our OpenTelemetry Demo project, running with an embedded Tyk Gateway instance.

Go Plugin was added: a simple plugin that prints some text on Gateway's console and adds a dummy attribute to the span.
Rate Limit: we added a rate limit through Tyk's dashboard to see how it looks in Jaegger when a request fails because of this.
Authorization: we added an authorization method to one of the APIs to see how it fails when the API that consumes it sends a request without a valid key.
Caching: all the APIs have caching middleware enabled and we're showing how it looks in Jaeger between different spans.
Internal Middleware: one of the APIs has a "Method transform" middleware, so we're showing how it changes from the "POST" method to the "DELETE" method, and how API fails because of this.

Most of these changes will probably make your demo project fail because we focused on how Tyk capabilities could work with Open Telemetry, and how we could be aware of different errors happening in the system.


Protection against array / drive disconnection

I've been looking for something like this for years as remembering to manually empty trash is a pain (usually when something won't play because I forgot to do it) so this is great thanks and seems to be ticking along right now (I used the CRON variable to increase the frequency).  I just wondered if there's any protection built in (or if not whether it is possible to add it) for a situation where the RAID array (or drive) hosting the media goes down unexpectedly for any reason.  Would plex-auto-trash keep running and essentially nuke the library?  I think I remember seeing that even with auto-empty on in the Plex server settings it won't do it if the library path isn't available.  Does this mean I'm safe even with plex-auto-trash? If not is it possible to add some sort of check before running the empty that will prevent it if the library path is unavailable?  Sorry if I haven't explained it well or used the correct terminology. Thanks.

This is not currently implemented but it could be optionally added.

Thanks for the reply, that's great to hear that this is a possibility. Would love to have that protection as an option. > This is not currently implemented but it could be optionally added.


Fix flattening example

I've been confused for several years what it means to "flatten" an array, due to this example. I finally bothered to type it into a compiler, and now think the example is wrong.
I was inspired to look at this by recent discussion over at #365.

I think you're right this is an error, but perhaps changing g[2] to g[1] would make it a better example, as it shows an examples of cases that will be passed according to the special case ABI rules being discussed.

The case is correct, it's an array of two structs, each of which contains an array of a single float.

Renaming it to be less confusing:

[...] struct { struct { float f[1]; } a[2]; } and struct { float f0; float f1; } are [...]

Oh good, I was worried I'd missed (and perhaps introduced?) a mistake via typo here. I like Jessica's suggested renaming.

:facepalm: Sorry team.


Loosen interface, additional proptests

Codecov Report

Merging #5 (2881c96) into main (cc21e7d) will not change coverage.
The diff coverage is 100.0%.

Additional details and impacted files

Files Changed
Coverage Δ

src/new_id.rs
100.0% <100.0%> (ø)


chore: idempotent merge functions

Motivation
Implements https://github.com/farcasterxyz/hub/issues/43
Change Summary
All sets' merge methods are now idempotent, because messages may be received out of order or many times. Messages that are over-written by existing ones, successfully merge without modifying the state of the set.
Merge Checklist

[x] The title of this PR adheres to the conventional commits standard
[x] The PR has been tagged with the appropriate change type label(s) (i.e. documentation, feature, bugfix, or chore)

Codecov Report

Merging #82 (f05ada2) into main (7fc3a7b) will increase coverage by 0.21%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main      #82      +/-   ##
==========================================
+ Coverage   88.27%   88.49%   +0.21%
==========================================
  Files          11       11
  Lines         930      913      -17
  Branches      224      220       -4
==========================================
- Hits          821      808      -13
+ Misses        108      105       -3
+ Partials        1        0       -1

Impacted Files
Coverage Δ

src/sets/castSet.ts
83.33% <100.00%> (-0.99%)
:arrow_down:

src/sets/reactionSet.ts
83.63% <100.00%> (-1.61%)
:arrow_down:

src/sets/verificationSet.ts
87.09% <100.00%> (+4.23%)
:arrow_up:

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


Porting FlashDevelop to Linux and MacOS X?

I've tried compiling the FlashDevelop 4.7.2 and it worked (after renaming Strings.resX to Strings.resx in PluginCore/DockPanelSuite/Strings.resx, and by deleting the .rev extension in FlashDevelop/Properties/AssemblyInfo.cs.rev)...
Sadly it did not run since it uses some native methods in the class WeifenLuo.WinFormsUI.Docking.NativeMethods.
Please consider porting FlashDevelop to Linux and MacOS X, if there is enough interest in this...
Thanks! :)
Build successful

The Dock Panel Suite is the least of the problems, in fact you can get it running on Mono without much problem. The actual headache is getting Scintilla to work.

Also, forgot to say. You can get FD working on Linux/Mac using CrossOver: https://www.youtube.com/watch?v=lZOfBnmetVs
Compatibility for it is improving constantly.

Wine is not solution when a project is still maintained, better to put effort on porting instead of trying to use hack
Just my opinion


Embedibility: Can opensplice be combined on embedded devices?

I am looking for an open source pub/sub protocol that can be compiled on embedded systems. I need the system to fit comfortably on devices with <32k of RAM and < 128k of flash.
Can opensplice do this currently? How difficult would you estimate it is to port it?
DDS looks like just about the perfect protocol for every level of communication. Thanks a lot!

OpenSplice (and any OMG-DDS compliant) implementation will not fit in that footprint, but there's an interesting DDS-related technology that does fit and integrates fine with DDS.
See: https://github.com/atolab/zhe


Core PHP Supports

If laradock supports running a Core Php project using Docker? If yes how? Please help me by providing all steps to Clone and Run a Core Php application using Laradock+Docker

What does it mean about "Core PHP application"?
It look like wordpress application. Right?

Its means NO php framework is used and application is just written in plain
php code with simple html and css
On Fri, Jul 2, 2021 at 4:18 PM Minkbear @.***> wrote:

What does it mean about "Core PHP application"?
It look like wordpress application. Right?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/laradock/laradock/issues/3007#issuecomment-872922324,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUVUEYL3BFEU7ERZ5EP4TL3TVWN6VANCNFSM47T5GIXA
.

you should follow this: https://laradock.io/getting-started/#installation


RC721-32 | Create a STORAGE version of walletOfOwner (as an extension)

Testing?
Transfers?
Burn ?

You can make that loop in removeTokenFromWallet more efficient:
Swap the found element directly with the last element, then pop, then break the loop


feat(conference): add keynote videos for MEC2021

This PR adds a keynote page to the MEC 2021 conference section with the embedded video of the opening keynote.

@musicEnfanthen It's correct. Please, merge it

Thank you both, @davidrizo for approval, and @rettinghaus for merging!


Can synchronize the folder to github?

it would be nicer if we can synchronize the folder to github or google driver

Workspace sync wouldn’t work with GitHub I’m afraid.


migrate wiki to docusaurus

The current progress of the migration to Docusaurus.
This PR supersedes the inactive #198. (closes #198)
Also fixes #185 and closes #186.
Preview: https://chew-geyserwiki.pages.dev
To Do:

[x] Fix setup pages
[x] Fix supported hosting providers pages
[x] Fix FAQ page
[x] Support data variables
[x] Finish (or remove) home page
[ ] Algolia searching
[x] Make theme match old wiki
[x] Setup i18n support

Geyser setup page should more or less work now just needs some CSS for the icons and selectors, and maybe updated links. Version variables also work now with, for example:
import { Versions } from '~/components/Versions'

<Versions platform="java"/>

This displays 1.20.4.
Will try to tackle Floodgate setup and FAQ tomorrow.

Will be done in a separate repo: https://github.com/GeyserMC/GeyserWebsite/


Slim Skeleton shows 500 error right after setup

Right after composer create-project slim/slim-skeleton myslimsite, I ran composer start and went to localhost:8080/users/ which returned a json object as below.
{
    "statusCode": 404,
    "error": {
        "type": "RESOURCE_NOT_FOUND",
        "description": "Not found."
    }
}{
    "statusCode": 500,
    "error": {
        "type": "SERVER_ERROR",
        "description": "ERROR: ob_clean(): failed to delete buffer. No buffer to delete on line 28 in file \/Volumes\/WD Mac\/work\/test\/slim-project\/myslimsite\/src\/Application\/ResponseEmitter\/ResponseEmitter.php."
    }
}

Any help on this much appreciated.

Update:
I just changed the line 28 of ResponseEmitter.php to if(ob_get_contents()) ob_clean(); which took off the 500 Server Error, but still have problem with route /users/ (Trailing Slash) but no 404 with route /users.
I installed Trailing Slash middleware as mentioned in the documentation by
composer require middlewares/trailing-slash

and changing /app/middleware.php to
<?php
declare(strict_types=1);

use App\Application\Middleware\SessionMiddleware;
use Middlewares\TrailingSlash;
use Slim\App;

return function (App $app) {
    $app->add(new TrailingSlash(true));
    $app->add(SessionMiddleware::class);
};

Still no luck with trailing slashes, shows 404 for routes with /.

Same here I got 404 after installation. Any help?

Oh thats my Nginx config @gopumon check your webserver config. It might be wrong with your web server configuration

Come on to the Slim slack and maybe someone can help you:
slimphp.slack.com

Come on to the Slim slack and maybe someone can help you:
slimphp.slack.com

Thanks @timogoosen , but I don't have an invitation on that Slack workspace.
The issue I face is the middleware TrailingSlash is not modifying the routes. The uri without trailing slashes works. The middleware have no effect. Initiates middleware on routes without trailing slashes.
I got rid of the 500 error with a simple if statement as mentioned above, don't know why that ob_clean() is called there and my fix is good or not.

This question is better asked on our Slack and/or our discourse forum.

@gopumon you can join the slack here:
https://join.slack.com/t/slimphp/shared_invite/enQtNjMxMjExMzYxMTU0LWVmNWQ1MWMxODA0ZjI2YTdkYzIyYjcxYTA3ZGQ2ZDNhZjdmMGVlODhlYWQ1ZmNhNTdiOWNlNmEzNGRiMjA1Yzc

I just changed the line 28 of ResponseEmitter.php to if(ob_get_contents()) ob_clean(); which took off the 500 Server Error

This has been fixed via https://github.com/slimphp/Slim-Skeleton/pull/117
I haven't tagged a new release yet. I will later this week.

Just released 4.0.1. I'm closing this as resolved. Please join our Slack group for further help.


Make error less confusing

Description
file command is not available everywhere, so it may fail.
This is to change the corresponding error message to something less confusing, since the exception is properly handled in the code.
(Found during hackathon. Since previously stacktrace was logged, people believed this was the reason workers were crashing... but it wasn't since, when you continue reading logs, you see the error is handled. Hence the change to clarify that).
Fixes # (issue)
Types of changes

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

Checklist:

[x] I have signed the Adobe Open Source CLA.
[x] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have read the CONTRIBUTING document.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.

Note that 27.1.0 was an erroneous release. It was unpublished.


How to compute the J and JDotNu for contact vertices

We need $J$ and $\dot{J} \nu$ of the contact vertices for computing the forward dynamics of the system. Actually, we need just the part of these terms that relates to the linear velocity and linear acceleration of the contact vertices.
Considering $f$ as the foot frame, we can write the linear velocity of a contact vertex of the frame $f$ like $i$ as:
\begin{equation}
v_i = v_f - S(r_{if}) \omega_f
\end{equation}
As $v = J_L \nu$ and $\omega_f = J_A \nu$ where $J_L$ and $J_A$ are the linear and angular parts of the Jacobian matrix of the frame $f$, we have
\begin{equation}
J_{L_i} = J_{L_f} - S(r_{if}) J_{A_f}
\end{equation}
Differentiating the above equation and multiplying it by $\nu$, we have
\begin{equation}
\dot{J}_{L_i} \nu = \dot{J}_{L_f} \nu - S(v_{if}) J_{A_f} \nu - S(r_{if}) \dot{J}_{A_f} \nu
\end{equation}
However, in https://github.com/ami-iit/matlab-whole-body-simulator/blob/master/lib/%2Bmwbs/%40Contacts/compute_J_and_JDot_nu_in_contact_frames.m, we used the following relations:
\begin{equation}
J_{L_i} = J_{L_f} - S(r_{if}) J_{A_f}, \
\dot{J}_{L_i} \nu = \dot{J}_{L_f} \nu - S(r_{if}) \dot{J}_{A_f} \nu
\end{equation}
I can not understand why the term $- S(v_{if}) J_{A_f} \nu$ is ignored. This term is equal to $- (\omega_f \times r_{if}) \times \omega_f$. Does any body have any idea on it?
cc: @traversaro, @nunoguedelha, @GiulioRomualdi

@VenusPasandi I believe that the math is not rendering properly

@VenusPasandi I believe that the math is not rendering properly

Sorry @DanielePucci. I tried to correct the rendering issue. It seems there is a rendering issue with writing $\dot{J}_i$!! I don't know if anyone has a solution for it?
cc: @ami-iit/artificial-mechanical-intelligence

It is rendering fine for me. Anyhow, when you have a problem in some formula involving a _, you can tipically change it to \_ to avoid the problems.

It is rendering fine for me. Anyhow, when you have a problem in some formula involving a _, you can tipically change it to \_ to avoid the problems.

Thank you @traversaro, your trick works nice :)

This term is equal to $- (\omega_f \times r_{if}) \times \omega_f$. Does any body have any idea on it?

Are you sure that that term does not evalute to 0 due to some formulas such as the one https://en.wikipedia.org/wiki/Triple_product ? Intuitively I would say now, but it may be worth to check ?

Is  $S(r_{if})$ changing? If $r_{if}$ is the relative position between the vertex and the center, then this would not change, right?

Is S(rif) changing? If rif is the relative position between the vertex and the center, then this would not change, right?

Yes, $r_{if}$ is the relative position of the vertex in the foot frame. So, its magnitude is constant and does not change. But, its direction changes.

Is S(rif) changing? If rif is the relative position between the vertex and the center, then this would not change, right?

Yes, $r_{if}$ is the relative position of the vertex in the foot frame. So, its magnitude is constant and does not change. But, its direction changes.

It depends on the frame where it is measured. If it is measured in the frame attached to the foot, then also the direction is constant

Is S(rif) changing? If rif is the relative position between the vertex and the center, then this would not change, right?

Yes, $r_{if}$ is the relative position of the vertex in the foot frame. So, its magnitude is constant and does not change. But, its direction changes.

It depends on the frame where it is measured. If it is measured in the frame attached to the foot, then also the direction is constant

Actually, the first time that I read the code, I thought the same as you.
But we are computing the time derivative with respect to the inertial/world frame. So, even if it is defined in the local frame, because of the rotation of the local frame, its time derivative is not  zero.

Hi @VenusPasandi!
The math should be here https://github.com/ami-iit/matlab-whole-body-simulator/issues/1#issue-693202831
Maybe there is something wrong there. This is a good occasion to double check it! :)

Hi @VenusPasandi!
The math should be here #1 (comment)
Maybe there is something wrong there. This is a good occasion to double check it! :)

Hi @Giulero!
Thank you for your reference. Unfortunately, in https://github.com/ami-iit/matlab-whole-body-simulator/issues/1#issue-693202831 the part related to the JDotNu is ignored and only the final relation is written! But, there is a hint which says that we obtain the relation in the same way as the relation of J, so, not with the differentiation of the relation of $J$. So, let us try in this way: The acceleration of the point i is as
\begin{equation}
\begin{aligned}
a_i = a_f + \alpha_f \times r_{if} + \omega_f \times (\omega_f \times r_{if}) \
= (\dot{J}_{L_f} \nu + J_{L_f} \dot{\nu}) + (\dot{J}_{A_f} \nu + J_{A_f} \dot{\nu}) \times r_{if}  -  (J_{A_f} \nu \times r_{if}) \times J_{A_f} \nu \
= (\dot{J}_{L_f} - S(r_{if}) \dot{J}_{A_f}  - S(J_{A_f} \nu \times r_{if}) J_{A_f}) \nu + ( J_{L_f} - S(r_{if}) J_{A_f} ) \dot{\nu}
\end{aligned}
\end{equation}
So,
\begin{equation}
\begin{aligned}
J_i = J_{L_f} - S(r_{if}) J_{A_f} \
\dot{J}_i = \dot{J}_{L_f} - S(r_{if}) \dot{J}_{A_f}  - S(J_{A_f} \nu \times r_{if}) J_{A_f}
\end{aligned}
\end{equation}
So, again we have the term $S(J_{A_f} \nu \times r_{if}) J_{A_f}$ in the JDotNu expression. Note that, this term is the centrifugal acceleration of point i. So, if we don't have any assumption for the motion of the foot, in general, the centrifugal term is not zero.

TLDR

This term is equal to $- (\omega_f \times r_{if}) \times \omega_f$. Does any body have any idea on it?

I do not know if it helps you @VenusPasandi, but notice that
$- (\omega_f \times r_{if}) \times \omega_f = \omega_f \times (\omega_f \times r_{if}) = S(\omega_f )^2\times r_{if} = (\omega_f \omega^\top_f - |\omega_f|^2 I)r_{if}$

TLDR

This term is equal to $- (\omega_f \times r_{if}) \times \omega_f$. Does any body have any idea on it?

I do not know if it helps you @VenusPasandi, but notice that
$- (\omega_f \times r_{if}) \times \omega_f = \omega_f \times (\omega_f \times r_{if}) = S(\omega_f )^2r_{if} = (\omega_f \omega^\top_f - |\omega_f|^2 I)r_{if}$

Thank you @DanielePucci. This relation is really useful if we want to add this term to current implemented equation.

I couldn't find any reason/assumption explaining that the term $ \omega_f \times (\omega_f \times r_{if}) $ is equal to zero. So, to be sure, I tested this term in a simulation. I performed two simulations; first by ignoring this term and second by considering this term (where I implemented this term by using the formula that @DanielePucci mentioned in https://github.com/ami-iit/matlab-whole-body-simulator/issues/67#issuecomment-1082210907). The results are as the following where the red dotted curves denote the first case (ignoring this term) and the blue curves denote the second case (considering this term).

So, this term is not equal to zero and ignoring or considering it affects the robot velocity vector and contact wrenches. So, I think this term is ignored by a simple mistake like https://github.com/ami-iit/matlab-whole-body-simulator/issues/67#issuecomment-1081796461 if the reasoning explained in https://github.com/ami-iit/matlab-whole-body-simulator/issues/67#issue-1184596992 is correct.
So, I kindly ask @Giulero, @traversaro  and @DanielePucci  to check the math in https://github.com/ami-iit/matlab-whole-body-simulator/issues/67#issue-1184596992.

@VenusPasandi!
I did the computations again. We know that:
$$
J_i \nu = \begin{bmatrix} I & -S({}^I R_\text{foot} {}^\text{foot} p_I) \end{bmatrix} J \nu
$$
so $J_i = \begin{bmatrix} I & -S({}^I R_\text{foot} {}^\text{foot} p_I) \end{bmatrix} J$.
Differentiating $J_i$ leads to:
$$
\dot{J_i} = \begin{bmatrix} I & -S({}^I R_\text{foot} {}^\text{foot} p_I) \end{bmatrix}  \dot{J}+ \begin{bmatrix} 0 & - S(S(J_A \nu) {}^I R_\text{foot} {}^\text{foot} p_I ) \end{bmatrix} J
$$
If we inject back $\nu$ and do some manipulations the following term appears:
$$
S(J_A \nu) S(J_A \nu) {}^I R_\text{foot} {}^\text{foot} p_I ,
$$
that's what you call $\omega \times \omega \times r$.
Now my main concern is that $\nu$ is an optimization variable, and with this new term we lose the linear relationship with $\nu$. It seems that using https://github.com/ami-iit/matlab-whole-body-simulator/issues/67#issuecomment-1082210907 we can extract a quadratic relationship, but how do we compute the 2-norm?

Ah, I missed your comment! :D
How do you write the optimization problem?

Thank you @Giulero

Now my main concern is that $\nu$ is an optimization variable, and with this new term we lose the linear relationship with $\nu$. It seems that using https://github.com/ami-iit/matlab-whole-body-simulator/issues/67#issuecomment-1082210907 we can extract a quadratic relationship,

Actually, the time derivative of $\nu$ i.e $\dot{\nu}$ is the optimisation variable. If you remember in https://github.com/ami-iit/matlab-whole-body-simulator/issues/1#issue-693202831, we have $\dot{J} \nu + J \dot{\nu}$ where $\dot{\nu}$ is an optimisation variable. So, we don't need the linear relationship with respect to $\nu$.

Yes, I went through the math and the code and my memory went back! :)
Thank you!

Thank you all for the nice discussion. I added the missing term into the dynamics block via #71

Very well done @VenusPasandi and @Giulero !

Ignore this comment, necessary to render math with


IOS Version Bump to 16

This will need to be updated to version 17 as 16 wasn't build correctly and then Im going to bump android to 17 too


Update BasicMovementController.cs

Replace magnitude calculation with square magnitude for marginally better performance.

The controller scripts were updated in a previous commit to support different types of input types. Therefore, this pull request cannot be merged. The change has been implemented in the commit c3b4512.
I plan on developing new movement scripts that support Unity's Input System when I get the time.


Please help! Getting error no such module 'minizip' during builds

Hello all,
I am trying to incorporate this library into my project and my pod reference looks like this below:
pod 'Zip', git: 'https://github.com/marmelroy/Zip', branch: ‘master’, submodules: true
However, when my swift 3.0 source uses import minizip, I get the following error.

I get the same error. "Missing required module 'minizip'"
I'm developing a Swift framework with a wrapped c library and the client project can't find the sub module. So I tried Zip but no luck either.
Not using cocoapods but manual setup.

Can you create an example project that reproduces this error so we can help ?
also, can you mention your cocoapods and Xcode versions ?

@juxs You are having a different issue, please open a new issue and we can take it from there.

juxs, here is how to solve:

Create folder "minizip\aes"
Copy . from https://github.com/nmoinvaz/minizip/tree/master/aes to yours one from step 1
Copy crypt.h, ioapi.c, ioapi.h, module.modulemap, unzip.c, unzip.h, zip.c, zip.h from https://github.com/nmoinvaz/minizip to yours minizip root

@mostafaberg , i am getting the same issue. I am using Zip 0.7 version &  Carthage.
It builds correctly if i build it in my local environment .
But in my scenario , i am having my own framework with nested frameworks & it supports Gitlab build automation . So whenever a commit happen in my gitlab server , the gitlab runner clones the latest code & tries to built my framework & as well all the dependencies . The built works fine as expected . But if i try to use the built framework, it shows missing required module 'minizip' . But all other nested frameworks (alamofire ,..) fine except Zip . Am i missing something ?

I'm having this too.  None of the workaround in the other similar issues are working for me.
What should I do to be able to check-in the Carthage directory and have it work without having to run carthage update? This is a requirement for our CI and production building process (where we are not allowed to obtain libs external to the network).

hi @mostafaberg , I am not using Cocoapod or Carthage. I just added the zip.framework into my Swift demo project. It shows error "** Missing required module 'minizip'** when I tried to build it. Here is the demo project
here is screenshot
https://monosnap.com/file/3n1CdzKhX7VUxEfBJITJsXSvnGjWhy
I found If I ever run&build the zip framework in my Mac, zipdemo project building will succeed.
Otherwise it shows "Missing required module 'minizip' . Just like the problem that guys has in Stackoverflow: https://stackoverflow.com/questions/42085217/swift-project-missing-required-modules-when-import-a-modular-framework
Please help, many thanks to you.

This should be fixed with #119.


Update examples to use newer QPU

Re-opening to trigger CI.

CI test failures are caused by https://github.com/kevin1024/vcrpy/issues/688.
A temporary fix is to pin urllib3<2, and a long term fix is to wait for https://github.com/kevin1024/vcrpy/pull/689 to be released.


NQD High School

nqdieu.txt

@MNguyen1302 First stage of verification passed, official domain is hinchingbrookeschool.net 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. Proof of domain ownership: https://www.hinchingbrookeschool.net/page/?title=Contact+The+Team&pid=477

@MNguyen1302 I am sorry, this is either duplicated or incorrect request. I have to close it without merging.
Please apply for free educational license with an official document which proves that you are a student. You can do it using "OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students.


⚠ ClamAV has degraded performance

In dab6e3e, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 195 ms

Resolved: ClamAV performance has improved in b6b655f after 14 minutes.


Export Type.* Namespace on Provider

Checklist

[x] run npm run test and npm run benchmark
[x] tests and/or benchmarks are included
[x] documentation is changed or added
[x] commit message and code follows the Developer's Certification of Origin
and the Code of conduct

This PR exports the Type.* namespace on this Type Provider and provides a Type.Date() extension type by way of a custom FastifyTypeBuilder implementation. The aim of this PR is to provide a mechanism for additional extension types to be added for custom Ajv schema/value refinement (as configured in Fastify), as well as to streamline the developer experience by only requiring a single import to bring in both TypeProvider and Type infrastructure.
Note: While this PR only implements the Type.Date() extension type, other types can be added if necessary (with some consideration given to Type.StringEnum(..), Type.Nullable(...) and other Open API schema representations that are not provided by TypeBox)
Current
import { Type } from '@sinclair/typebox'
import { TypeBoxTypeProvider } from '@fastify/type-provider-typebox'

Proposed
import { Type, Static, TypeBoxTypeProvider } from '@fastify/type-provider-typebox'

// ----------------------------------------------------
// Extension Type: Type.Date()
// ----------------------------------------------------

const T = Type.Date()     // const T = { type: 'string', format: 'Date' }

type T = Static<typeof T> // type T = Date | string

The exporting the Type.* namespace on this provider was discussed https://github.com/fastify/fastify-type-provider-typebox/issues/29.
Submitting for consideration

@RafaelGSS Hi

Could you include a Date use-case in the docs as well? It might be inside a FastifyTypeBuilder section

Ah, I was thinking about actually removing the Type.Date() type as it doesn't appear as though Fastify automatically coerces strings into Dates. I added the Type.Date()  function on the assumption that Fastify would pass Dates on properties into route handlers, but the tests revealed that it's actually just passing the iso8601 string representation for the Date (which is expected default behaviour). In this regard, there doesn't appear to be a scenario (afaik) where Fastify would pass a Date into a route, so inferring for Date | string doesn't seem right if there isn't potential for Date to be passed.
I think the correct type would statically infer as Date only (no union), and only if Fastify automatically coerced iso8601 strings into Date objects.
const D = Type.Date()       // { format: 'date' }
const DT = Type.DateTime()  // { format: 'date-time' }

type D = Static<typeof D>   // Date
type DT = Static<typeof DT> // Date

Link to Ajv coersion rules for reference below
https://ajv.js.org/coercion.html
What are your thoughts on removing the Date type? And also, I'm still pondering the inclusion of Type.StringEnum() and Type.Nullable() for OpenAPI users (which would be incompatible with the TypeCompiler, but may make life easier for OpenAPI users on Ajv). So interested to get some additional thoughts on those.
Still think exporting the Type.* is a good call even if it doesn't expose extension types as of this PR, as having Type.* expressed as a FastifyTypeBuilder would allow easy addition of custom types should Fastify need them in future.
Open to thoughts

Sorry for the delay @sinclairzx81, busy week. I concur with exporting the Type.* under type-provider-typebox even without a specific type such as Type.Date(). As you mentioned in #29, we can leverage the builder in many ways. We just need to make sure to create proper documentation for that so the users will understand how to use it.