TransientLifetimeManager could be one instance for all of the policies

The manager does not hold any reference so it could be reused for all registrations

Implemented in 6e77a7b265bead46f0b3f616c84714c467712972

Duplicate unitycontainer/container#18


⚠ Bofrost.at has degraded performance

In 9771150, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1775 ms

Resolved: Bofrost.at performance has improved in bee7f37 after 14 minutes.


add watchers to imports within vue files

Related plugins

[X] plugin-vue

[ ] plugin-vue-jsx

Description
The watcher should rebuild vue files when the file's imports are updated. Without this, the rollup build doesn't rebuild when you update .ts and .scss/sass files that are in your build. This was fixed in vuejs/rollup-plugin-vue
Suggested solution
In plugin-vue/src/index.ts line 291, add this code snippet
if (query.src) {
this.addWatchFile(query.filename);
}
Alternative
No response
Additional context
Original Issues: https://github.com/vuejs/rollup-plugin-vue/issues/396
Original Fixes: https://github.com/vuejs/rollup-plugin-vue/pull/385
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

[@vitejs+plugin-vue+5.0.4.patch](https://github.com/vitejs/vite-plugin-vue/files/15098461/%40vitejs%2Bplugin-vue%2B5.0.4.patch)


Change 'on' to 'heat' as fallback thermostat mode

'on' isn't recognised as a mode by Google Assistant, rather is used as a method to return a thermostat to a previous mode. In the case where a thermostat doesn't support the standard google modes (e.g. A homematic radiator thermostat) this means the set_temperature doesn't get returned to the user on a request.
Description:
Related issue (if applicable): fixes #
Pull request in home-assistant.github.io with documentation (if applicable): home-assistant/home-assistant.github.io#<home-assistant.github.io PR number goes here>
Example entry for configuration.yaml (if applicable):

Checklist:
If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] New dependencies have been added to the REQUIREMENTS variable (example).
[ ] New dependencies are only imported inside functions that use them (example).
[ ] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

Hi @andrewdolphin,
It seems you haven't yet signed a CLA. Please do so here.
Once you do that we will be able to review and accept this pull request.
Thanks!


Dates with high precision (nanoseconds) fails to train

I was testing on some data, and I kept getting exceptions saying train failed, after looking around I realized that it was because of the high precision dates.

INFO:pyaf.std:START_TRAINING 'value'
Traceback (most recent call last):
  File "C:\PYTHON3\lib\site-packages\pyaf\ForecastEngine.py", line 25, in train
    self.mSignalDecomposition.train(iInputDS, iTime, iSignal, iHorizon, iExogenousData);
  File "C:\PYTHON3\lib\site-packages\pyaf\TS\SignalDecomposition.py", line 631, in train
    self.checkData(iInputDS, iTime, iSignal, iHorizon, iExogenousData);
  File "C:\PYTHON3\lib\site-packages\pyaf\TS\SignalDecomposition.py", line 604, in checkData
    type1 = np.dtype(iInputDS[iTime])
TypeError: Cannot interpret '0     2021-08-01 00:14:36.879515613+00:00
1     2021-08-01 00:13:22.755664335+00:00
2     2021-08-01 00:12:08.483382948+00:00
3     2021-08-01 00:10:54.242433585+00:00
4     2021-08-01 00:09:40.135882425+00:00
                      ...
115   2021-07-31 21:51:43.580248426+00:00
116   2021-07-31 21:50:29.020741582+00:00
117   2021-07-31 21:49:15.175994058+00:00
118   2021-07-31 21:48:00.528170592+00:00
119   2021-07-31 21:46:46.214305238+00:00
Name: date, Length: 120, dtype: datetime64[ns, UTC]' as a data type

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\PYTHON3\lib\site-packages\pyaf\ForecastEngine.py", line 30, in train
    raise tsutil.PyAF_Error("TRAIN_FAILED");
pyaf.TS.Utils.PyAF_Error: TRAIN_FAILED

I changed the precision by casting my dates up to seconds and then train worked fine:
df['date']  = df['date'].values.astype('<M8[s]')
Seems that the underlying problem is some numpy function, not too sure..

Hi @artrune
Interesting issue. I need to know the version of numpy / pyaf you are using. An anonymized version of your data and/or a script that fails are also welcome.
The basic requirements are here :
https://github.com/antoinecarme/pyaf/blob/master/ISSUE_TEMPLATE.md

Here's a subset of the data I was using:
{
    "results": [
        {
            "statement_id": 0,
            "series": [
                {
                    "name": "temperature",
                    "columns": [
                        "time",
                        "value"
                    ],
                    "values": [
                        [
                            "2021-08-01T15:19:40.791108016Z",
                            43.5901031494
                        ],
                        [
                            "2021-08-01T15:18:26.407537578Z",
                            43.5352668762
                        ],
                        [
                            "2021-08-01T15:17:12.252326253Z",
                            43.6632194519
                        ],
                        [
                            "2021-08-01T15:15:57.981777501Z",
                            43.4987106323
                        ],
                        [
                            "2021-08-01T15:14:43.74242866Z",
                            43.5535430908
                        ],
                        [
                            "2021-08-01T15:13:29.624277764Z",
                            43.5718231201
                        ],
                        [
                            "2021-08-01T15:12:15.401747322Z",
                            43.7363357544
                        ],
                        [
                            "2021-08-01T15:11:01.165682994Z",
                            43.480430603
                        ],
                        [
                            "2021-08-01T15:09:46.742506101Z",
                            43.4621505737
                        ],
                        [
                            "2021-08-01T15:08:32.613850591Z",
                            43.5535430908
                        ]
                    ]
                }
            ]
        }
    ]
}

Here are the versions of the packages:
numpy: 1.19.2
pandas: 1.2.4
pyaf: 2.0.1

I was loading the data into a dataframe using:
df_result = pd.DataFrame(json['results'][0]['series'][0]['values'], columns=['time', 'value'])
df_result ['date'] = pd.to_datetime(df_result ['time'], utc=True)

training was failing so I added the cast
df_result ['date']=df_result ['date'].values.astype('<M8[s]')

@artrune
Thanks for the data. I will see what I can do with that.

A new version of PyAf (3.0) is available now. Not sure this will help here, but it is always better to test the latest versions. Please upgrade numpy and pandas to the latest versions too.
Numpy and Pandas do not like nanoseconds. I will say more taht that later (need some time, in a separate comment). Nanoseconds are not good for business data (IRL, It does not always make sense to wait for 12 nanoseoconds ;)
Nice to seee that it works when nanoseconds are removed. What about "utc" flag ?
Even if there will not be a "real" fix, I will try to make PyAf robust to this kind of stuff (ignore nanoseconds and a warning message).

Thanks, I have no real interest in dealing with nanoseconds, the underlying database I was polling (influx 1.8) stores dates with that precision.
I remember trying to remove the utc flag, I don't think it helped.

Ok for the nanoseconds,. Will help with prioritizing this issue. Seems to be a numpy issue as you noted in the first commit.
As long as we have a workaround, this bug will be fixed in PyAF 4.0 (release date : July 2022 ;).

Thanks for this feedback. I have been interested at some time (long time ago) in IoT and Time series usage with PyAF
https://github.com/antoinecarme/pyaf/issues/3
Do you have some pointers/demos or notebook links to your usage of PyaF with InfluxDB ?

To be honest I wasn't using any demo data, I just happened to have been collecting my raspberry pi temperature from some months now, if you want that data I can share it without any problem.

@artrune
LOL. So, just by playing with your Raspberry Pi and a Time Series database, you are helping fix a problem for PyAF and probably numpy users. Don't underestimate the power of usage !!!
Thank you very much for helping make PyAF better and don't hesitate to come back and report similar issues.

Antoine

Absolutely! I'll let my RaspberryPi know he's a good boy!
Thanks and stay safe-


I would like to specify user that never lock after user reach out of number of login allow

Hi,
I would like to except admin user that can login unlimit and never lock after user reach out number of login allow
Thanks

Is that really sensible? If you're getting a number of unnecessary logins you probably

have a user that is used by multiple people who typo the password; split the account
have a user that typos his or her password a lot; instruct them to use a better password
have someone bruteforcing a user; they should be locked out

You can also use the lock out by combination of username and IP option.


Include dataflows as deployable items

Dataflows are also possible to deploy through deployment pipelines. Previously, this was not listed in the introduction section of deployment pipelines.

@marclelijveld : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"


typo: meesage -> message

Docs Build status updates of commit 970ee63:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/databricks-monitoring/application-logs.md
:white_check_mark:Succeeded
View

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


Remove non functional options from navbar

Fixes issue #65

@KaizenGirl1111 mam can u review this

@ayush25102001 where do you plan to put those non functional links?
You may comment here the things you removed, so that if we ever need to build them, we'll have a reference.

@ayush25102001 where do you plan to put those non functional links?
You may comment here the things you removed, so that if we ever need to build them, we'll have a reference.

@KaizenGirl1111 mam AboutUs,Services and review links are non functional and thus removed them for now to make the navbar clean

ok @ayush25102001


fix tail docs

clarify that tail always returns a Seq as its signature already correctly shows

Thanks a lot!


UITabBarController loosing VCs

Looks like tapping quickly to switch tabs while an animation is in progress causes the lost of all the controllers. I ended up with a white screen for all the tabs.

Is there a way to disable user interaction while in progress here, or forcing it to complete before triggering a new one?

a same issueO.O

Fixed in the develop branch.

thanks @lkzhao do you have an idea and when you'll make a new release?

Should be soon. maybe by the end of this week. I am doing a major cleanup internally to prepare for the real 1.0 release. want to be more developer friendly and support iOS 11 as well.


Error for blogdown::install_hugo()

The latest Hugo version is 0.54.0
trying URL 'https://github.com/gohugoio/hugo/releases/download/v0.54.0/hugo_extended_0.54.0_Windows-64bit.zip'
trying URL 'https://github.com/gohugoio/hugo/releases/download/v0.54.0/hugo_extended_0.54.0_Windows-64bit.zip'
Content type 'application/octet-stream' length 18187152 bytes (17.3 MB)
downloaded 17.3 MB
Hugo has been installed to C:\Users.................................
Warning message:
In download.file(url, output, ..., method = method) :
URL 'https://github.com/gohugoio/hugo/releases/download/v0.54.0/hugo_extended_0.54.0_Windows-64bit.zip': status was 'SSL connect error'

What is the issue? If you have SSL connect issues I think you must take this with GitHub?

In addition to the previous comment: You should really report these kinds of problems in the blogdown repository and not here, since it obviously has nothing to do with hugo itself.


Cite using "shorthand"

I have some bib files that provide the shorthand attribute. E.g.,
%ISO 31000:2009(E)
@techreport{iso:31000,
  author = {ISO},
  institution = {International Organization for Standardization},
  address = {Geneva, Switzerland},
  title = {Risk management---Principles and guidelines},
  number = {31000:2009},
  shorthand = {ISO 31000:2009},
  type = {ISO},
  year = {2009}
}

% ISO Guide 73:2009
@techreport{iso:guide73,
  author = {ISO},
  institution = {International Organization for Standardization},
  address = {Geneva, Switzerland},
  title = {Risk management---Vocabulary},
  number = {73:2009(E/F)},
  shorthand = {ISO Guide 73:2009},
  type = {ISO Guide},
  year = {2013}
}

I'd like to have a mode that provides a citation using the shorthand, e.g., "[ISO:31000:2009]", instead of "[16]". With this mode obviously not all bib infos have the "shorthand" which could fall back to "authoryear" or just pure numbers ("[16]").

Writing the ISO CSL style and using a switch to prefill the citation-label using shorthand is the best way to go.

Agree. There does not seem to be an agreed practice on how to BibTeX cite ISO documents yet. Perhaps you can formalize a method based on ISO 690?
http://dominiodelasciencias.com/ojs/documentos/ISO690-2010.pdf

@paolobrasolin is this issue still valid? Thanks

It is. I gave this some thought.
I think the best way to handle this kind of situation, since there is no fixed convention for BibTeX data structure, would be to introduce an option like
cite[iso:31000, by=shorthand]

that would produce an (hyperlinked if necessary) citation text [ISO 21000:2009].
That is, we let the user specify an arbitrary (text) field to use as a citation body.
This has the bonus of solving some other weird edge cases too without introducing extra specialization.
Allowing more flexibility would probably be more fruitful than trying to enforce a convention, despite some extra verbosity (e.g. compare with a more rigid citeiso[iso:31000]).
Also, this is perfectly in line with the idea in #59.
My only doubts about the usability of this are about multiple citations and wrapping brackets.
What are your thought on this?

@paolobrasolin I agree with this approach since the “by” keyword could also refer to other bibtex keys too. And in any case, the gem should support bibliography databases beyond just bibtex in the future!

Hi, is this idea still being considered?  Asking cuz this would be something we would start using right away.


pcre:x64-windows not copying dll into project

Hi
I am trying to use pcre in a cmake project however it doesn't copy the pcre.dll across post build, the pcre:x64-windows-static works fine.  I can make a PR to fix if I know how to change port file.
Thanks

Hi @simon-p-r , thanks for reporting this issue!
This issue may be fixed in the recent PR. So plz update vcpkg and rebuild pcre.
Thanks.


Create new branch in the Kuadra project

WHAT
Create a new github branch that will be the base branch for https://github.com/Kuadrant/kuadra/issues/29 https://github.com/Kuadrant/kuadra/issues/30

Branch temp_base has been created on the origin kuadra. @ehearneRedHat lead the pair programming and @dlaw4608 observed.


Cleanup Log4J2Logger

Motivation:
Log4J2Logger had some code-duplication with AbstractInternalLogger
Modifications:
Reuse AbstractInternaLogger.EXCEPTION_MESSAGE in Log4J2Logger and so remove some code-duplication
Result:
Less duplicated code.

Just some cleanup


Better database schema handling

Description
We need a better database schema handling mechanism as there are a few problems with the current one.
No place to look for the schema in the source
Right now, even if the database is a new one, the schema is pieced together by running a number of migrations from sql/migrations/{local,state}. The resulting full schema can be observed by running sqlite3 ... .schema command on a database, but that's not very convenient, and schema evolution across different go-spacemesh versions can't be easily seen by inspecting history of a schema file.
Schema drift
If the database schema is changed in an unexpected way for whatever reason, this may go undetected and cause some hard to debug issues. Suppose a user has run a go-spacemesh version built from develop that added a migration, and then switched to a later stable version which also has this migration, but a newer version of it that adds an index. PRAGMA user_version tells go-spacemesh the database schema is up-to-date, yet actually the index is missing. This leads to a substantial performance degradation, but given that we don't know that the user has used an unreleased version, we might spent a lot of time trying to understand why this particular go-sm instance is THAT slow.
Granted, we strongly recommend against using unreleased versions on normal nodes, yet the user might have done that by mistake and/or forgotten about it.
Package inconsistency
sql package used for the state database and sql/localsql package used for the local database. The database type for localsql.Database builds on sql.Database while database type for the state database uses sql.Database directly.
Inconvenient coded migrations
When a migration has to be implemented as Go code, it cannot be placed in sql or sql/localsql package, and thus cannot be automatically used by {sql,localsql}.{Open,InMemory} methods which open a database; this is because coded migration use sql package for accessing the database along with some packages that might import sql, and Open / InMemory functions using them would cause a cyclic dependency. The places in the code where the databases are opened, such as node.go, tests and the merge tool, have to import the migrations and add them via options to the Open / InMemory calls. It would be much better if the code that uses the database could avoid concerns about internal DB schema workings such as particular migrations.
Suggested implementation and its problems
The suggested implementation of new database schema handling is here: #6003
Additional description link (README): https://github.com/spacemeshos/go-spacemesh/blob/aada7c61b5e61505404bbd4cfdd7b4deeb7ca45a/README.md#handling-database-schema-changes
The crux of the new approach is this (but still please read the above descriptions before proceeding to the following sections):

the state database is handled by sql/statesql and the local database handled by sql/localsql package. These files are NOT supposed to be ever edited by hand
the full database schema is stored in sql/{statesql,localsql}/schema/schema.sql file and is not supposed to be edited directly
when a new database is created, the corresponding schema file is used to initialize it
when an existing database is opened and its PRAGMA user_version is old, the required migrations are run
in both cases the actual database schema is diffed against the corresponding schema files, and any differences are reported as schema drift
the consistency of the schema files in both locations is verified by tests that run all the migrations on an empty database, capture the schema and compare it with the stored schema file
in case if a schema consistency test fails, it creates an updated schema file with an .updated suffix (sql/{statesql,localsql}/schema/schema.sql.updated) which can be used to update the schema file with a single mv command

There are numerous possible problems with the PR #6003 though which are discussed below. I try to provide rationales for the existing decisions and also describe what's still possibly missing.
Golden test approach
One possible approach to maintaining the schema.sql files would be a dedicated tool that could be run as a part of CI pipeline, along with the linter, checking source formatting and generated Go files. That sounds cleaner, but on the other hand, that would require building an extra tool that would have to be invoked separately when dealing with code changes that involve database migrations. In my opinion, that would add some hassle to the development workflow.
Because of that, I decided to cut some corners and have a test that verifies the consistency of the schema of each database. Moreover, in case of any differences between the schema that is created by running all the migrations and the schema stored in the schema.sql file, the test produces schema.sql.updated which can be used to "accept" the changes easily (replace schema.sql with it). This is essentially the Golden test approach. The difference is that the schema.sql file is used not just for testing, but also for initialization of fresh databases.
I'm not 100% sure the golden test approach involving a Go test is the best. Maybe we should just have the schema tool and make check-db-schema and make update-db-schema commands that run the tool under the hood, and have the CI do make check-db-schema.
Avoiding code duplication in the tests
Each of the sql/statesql and sql/localsql packages need to have a pair of tests (statesql, localsql) that verify the same thing, but with different schemas:

Idempotent migrations: reopening a database after migrations are run on it should not cause any schema changes
Schema consistency: after a fresh database is opened, it schema exactly matches the schema in schema.sql; the same holds for the case when migrations are forced to run on the fresh database instead of using schema.sql script.

The corresponding tests in sql/localsql and sql/statesql are merely stubs that call the actual test code in sql/test package. This arguably hinders readability and in other cases, it would probably make sense to inline the tests in sql/localsql and sql/statesql and remove the sql/test package. But in this case, the tests double as a tool for schema consistency verification due to aforementioned "corner cutting" with schema tests serving as the "schema tool".
So: not just tests, but the schema tool. It would be really undesirable for the schema tool implementation to drift apart in sql/statesql and sql/localsql packages. Arguably, it could be said that then mostly duplicated InMemory / Open / Schema functions in the sql/{statesql,localsql} don't make sense either, but that's not really the case, as these are supposed to be allowed to drift apart, wrt e.g. the set of migrations and connection pool size, whereas the schema tests verify the fundamental schema properties which should always be the same for both sql/statesql and sql/localsql. Should sql/{statesql,localsql} need tests that verify things that are different between the databases, these can be added to the packages along in addition to the stubs that use sql/test.
Circular dependencies in coded migrations not fully fixed
One of the issues with existing database schema handling mechanism is that the coded migrations placed in sql and sql/localsql packages may cause circular dependencies. With the new mechanism, the situation is somewhat improved, but it is still problematic. All the code that used *sql.Database package previously is switched to using *statesql.Database, and the local database code still uses *localsql.Database. If a migration imports some package that happens to import sql/{statesql,localsql}, we've still got a circular dependency.
One way around it is making sql.Database an interface (instead of a struct) which includes sql.Executor but also provides other methods: Tx, WithTx, WithTxImmediate, QueryCount, QueryCache and Close. Using this interface in all the non-test files instead of *statesql.Database and *localsql.Database will resolve the circular dependency as the coded migrations in sql/{statesql,localsql} will be able to import the packages that only use sql package. The tests in the packages that use sql.Database interface may still import sql/{statesql,localsql} packages to use their InMemory / Open / Schema functions as this does not constitute a circular dependency (importing these packages ignores tests in them).
The problem with such an improvement is that it loses the type-based distinction between *statesql.Database and *localsql.Database. This can be mitigated by having sql.StateDatabase and sql.LocalDatabase interfaces that differ in some dummy method, e.g. IsStateDB() bool vs IsLocalDB() bool. This sounds somewhat hacky and I'm not sure it's the way to go; on the other hand, the errors caused by mistakenly using *localsql.Database instead of *statesql.Database and vice versa are usually very easily caught by tests, so the value of these additional interfaces can be disputed.
Allowing "some" schema drift
Some databases may contain artifacts of additional tooling used, such as _litestream* table from Litestream SQLite replication. Having a way to avoid it is rather useful for infra maintenance purposes, thus I think having main.db-schema-ignore-rx setting for ignoring certain tables and indices when checking for schema drift does make sense. I think a single regexp is enough as it can include multiple name prefixes with |.
Failing upon schema drift by default
An open question is whether go-spacemesh should fail if schema drift is detected, if this behavior needs to be configurable, and if it should fail by default if it is so.
What I'm afraid of is that if the schema drift happens due to some table added by accident to a quicksync db or some other unanticipated effect like this, we can get a lot of complaints about Smapp failures because of schema drift, with reasons that may be very confusing to the end-user. On the other hand, if we just log a warning upon schema drift (like it's done currently in #6003) we can still see schema drift warning easily when we look at go-spacemesh logs.
Programmers' docs for database schema handling
README.md already contains some information on the devenv, such as using different make commands, running the tests and setting up the build environment. I've added a section on handling DB schema changes to README.md, but it seems to be somewhat out of place. CONTRIBUTING.md seems to be also not very well suited for such detailed descriptions.
Should we have a separate HACKING.md or something like that?
Printing schema diffs
It is argued that in the schema consistency test, we can rely on plain require.Equal for printing schema diff instead of using go-cmp-based schema differ that is used to generate schema drift warnings. While such approach would probably simplify the test a bit, it would also produce the full schema.sql script (original and updated) printed as a big unreadable wall of escape text (\n instead of newlines) before the actual diff. In my opinion, that would reduce the usability of the schema consistency test by cluttering the terminal with too much unusable output and thus the trade-off is not worth it.

Regarding Avoiding code duplication in the tests:
I don't see any reason to have a generic test for two different packages/implementations. Either we should make the package itself generic and have a single test that covers the general case (and is not generic) or we have 2 packages with two separate test implementations.
I don't see an issue in having duplicated code in tests - quite the contrary. I think we should avoid DRY-ing up tests, because each test should stand for itself as much as possible (besides a general setup / teardown approach). Making tests dry quickly makes them hard to change & debug.

duplicated InMemory / Open / Schema functions in the sql/{statesql,localsql} don't make sense either, but that's not really the case, as these are supposed to be allowed to drift apart, wrt e.g. the set of migrations and connection pool size, whereas the schema tests verify the fundamental schema properties which should always be the same for both sql/statesql and sql/localsql.

This makes no sense to me - the implementation is the same but is allowed to differ in the future, but although tests are also the same they must not diverge?
Regarding Allowing "some" schema drift:

Some databases may contain artifacts of additional tooling used, such as _litestream* table from Litestream SQLite replication.

I fear this being used by members of the community to bypass the exact thing we are trying to avoid: schema drifts. If for some reason (manually editing the DB, using unreleased builds, etc.) the schema drifts users will "fix" this by just using this configuration to ignore the DBs that differ.
And if the default action upon a schema drift is to only log a warning - which in my opinion it should not be, since a drift can can lead to data corruption - then there is no reason to allow users to get rid of that warning by ignoring tables that differ from the expected schema.
Regarding generating a new schema:
The current suggested workflow is to execute a test that will fail if the schema was updated and produce a file that then has to be renamed and committed. This is a bit clunky to me. We do have make generate which internally calls go generate. A //go:generate sh -c "<command that builds schema form migration files and puts it where it belongs>" would better fit the existing workflow on how to deal with generated files.
It would still serve as a check against unintended schema changes since our CI checks if make generate modifies files or not.

This makes no sense to me - the implementation is the same but is allowed to differ in the future, but although tests are also the same they must not diverge?

Thing is these are not just tests, but rather essentially the schema tool that helps maintaining schema.sql in sync with migrations. That must happen in the exactly same way for both localsql and statesql.
I'd prefer the separate schema tool route to duplication of that code, so indeed I should probably update the PR to use go:generate approach.
Re failing by default upon schema drift: I'd welcome @pigmej's opinion on that. As I described in the issue, the scenario I'm afraid of is some stray table in quicksync db that breaks every Smapp installation. With schema drift producing just a warning, it's still useful for diagnostics given that we usually request the application log from the users.
Re not allowing schema drift exceptions: there are a lot of advanced options in go-spacemesh that one can utilize as a footgun ;) This particular option I'd rather keep as it can be useful under various circumstances. In different ops related scenarios the need for such exceptions may arise, and another option (just ignoring the warning b/c some kind of schema drift is expected) may lead to missing unexpected schema drifts. We may add a warning to the docs that mention that option, stating explicitly that one needs to know what (s)he's doing when changing its value.

if the litestream is the issue, then we can get rid of it. We can disable it, and / or clear the schema.

@pigmej litestream is easy to ignore. The problem is a bit more general: is it ok for go-spacemesh to stop immediately when schema drift is detected, unless this behavior is explicitly disabled in the config, or are our chances of messing this up a bit too high?

Hard to say, if it can be disabled in the config then imo its ok to crash

I would also say return an error when opening a DB and the schema doesn't match (that error should gracefully shut down the node before it even fully started) and allow to disable that behavior in which case it logs with a warning that the schema is different and how it is different, no need to add another config to disable this warning in some cases where a drift is expected / desired in my opinion.

Ok, you convinced me :) So I'll do the following changes to the current implementation:

instead of tests that verify schema.sql files, the schema generation from migrations will be done via go:generate and checked by CI along with other generated files
the idempotent migration test in statesql and localsql will be inlined
the ignore regexp config option will be removed
the default behavior will be to fail upon schema drift
there will be an option to make schema drift non-fatal, in which case a warning with schema diff will be logged

One thing that was not fully decided above is where to put the developer docs for schema handling, which I'd prefer to have somewhere (README.md seems not to be very appropriate place for that). Perhaps should indeed add HACKING.md for that purpose?

One thing that was not fully decided above is where to put the developer docs for schema handling, which I'd prefer to have somewhere (README.md seems not to be very appropriate place for that). Perhaps should indeed add HACKING.md for that purpose?

Normally I would expect something like this in CONTRIBUTING.md maybe under Code Guidelines or a similar section. That file however is a bit outdated 🤔


Support 'less than' operator in compilation conditions

Implementation: https://github.com/apple/swift/pull/17960

This is scheduled for review on August 13.

@danielmartin The proposal doesn't make it clear if <= is supported. I can't see it be very useful, but it would be consistent with >=.

@danielmartin I am kicking off this review.


Geo code receiving error message

I've been using geo codes for awhile now and love using it but recently i'm getting this error message:
UiApp has been deprecated. Please use HtmlService instead.
Can you specify?
Thanks,
Lorry

I've just started receiving this error as well. Too bad as this is a great script - but I don't know enough of how it's put together to know what needs to be done to fix this. Hopefully someone sees this.

Having the same problem.

Same problem

Same... seems to be depracted now.

I will note to others running into this problem - I've been able to solve the issue by simply exporting the Google Sheets as a .csv (I have a separate sheet with functions that auto-parses out the data I actually want to export). Then you can import that .csv into Mapbox. It's not as clean of a process, but it does work while this plugin is down.

I also have the same problem
I cannot neither use geocode tool nor save as a GeoJSON file due to the info above.
Any hints how to solve it?

👍 +1:

same problem

same problem

2021 - script is not updated. I used Addon "Geocode by Awesome Table" - worked, no cost.


Problem building OpenEXR-2.2.1 in Visual Studio 2015 x64: error MSB6006: "cmd.exe" exited with code -1073741515.

I encountered an error when building the IlmImf  project in OpenEXR 2.2.1
My environment:

Windows 10 version 1803 64bit
Visual Studio 2015 Update 3
CMake 3.10.1

Steps towards the error:

Download ilmbase-2.2.1.tar.gz and openexr-2.2.1.tar.gz from http://www.openexr.com/downloads.html
Uncompress the two packages
Build ilmbase-2.2.1
3.1) create build and install_ folder in the root directory of ilmbase
3.2) In command line window of Windows, run cd build
3.3) In command line window of Windows, run:
cmake -DCMAKE_CONFIGURATION_TYPES=Release -DCMAKE_INSTALL_PREFIX=C:\...\ilmbase-2.2.1\install_ -G "Visual Studio 14 2015 Win64" ..
3.4) open ilmbase.sln in Visua Studio 2015 and build INSTALL project. I can see files created in the install_ folder.
Build openexr-2.2.1
4.1) create build and install_ folder in the root directory of openexr
4.2) In command line window of Windows, run cd build
4.3) In command line window of Windows, run:
cmake -DCMAKE_CONFIGURATION_TYPES=Release -DILMBASE_PACKAGE_PREFIX=C:\...\ilmbase-2.2.1\install_ -DCMAKE_INSTALL_PREFIX=C:\...\openexr-2.2.1\install_ -DZLIB_LIBRARY=C:\...\zlib.lib -DZLIB_INCLUDE_DIR=C:\...\include -G"Visual Studio 14 2015 Win64" ..
Note: ZLib has been built before; I don't see any problem with Zlib.
4.4) open openexr.sln in Visua Studio 2015 and build all (or IlmImf project specifically).

The error occurs when IlmImf project is being built. The errors are:

4>------ Rebuild All started: Project: IlmImf, Configuration: Release x64 ------
4>  Building Custom Rule C:/.../openexr-2.2.1/IlmImf/CMakeLists.txt
4>  CMake does not need to re-run because C:/.../openexr-2.2.1/build/IlmImf/CMakeFiles/generate.stamp is up-to-date.
4>  Generating b44ExpLogTable.h
4>C:\Program Files (x86)\MSBuild\Microsoft.Cpp\v4.0\V140\Microsoft.CppCommon.targets(171,5): error MSB6006: "cmd.exe" exited with code -1073741515.
========== Rebuild All: 3 succeeded, 1 failed, 0 skipped ==========

The dependencies of the IlmImf project -- b44ExpLogTable, dwaLookups and ZERO_CHECK -- can all be built successfully. I also added the path to the ilmbase's lib which contains various .dll files into PATH environment variable but of no avail. I have no idea what the matter is, so I post an issue thread here in hope that someone can help me with it. If I missed anything needed to reproduce the error, please let me know. Thank you.

Just tried the develop branch downloaded here. It can build successfully. Oops ... So my problem should have already been found before and fixed in some version between the develop branch and the one in the http://www.openexr.com/downloads.html. But I still have two questions to ask before closing this issue:

I don't wanna build my application on develop version. What is the downloadable branch that is reliable for release and fixes my aforementioned problem?
What is the branch of the packages downloadable from http://www.openexr.com/downloads.html?

The issue you encountered has been on the master branch for some time. Until then the fix is merged to master, it exists only on the develop branch.

You can check the Releases page to find the commits corresponding to various versions.

https://github.com/openexr/openexr/releases

Thanks. The thread can be closed now.


Export template error "There are no mirrors available"

Godot version
v4.1.beta2.official [a2575cba4]
System information
Windows 7 64 bits
Issue description
When trying to install export templates from Godot editor,
I got

Error getting the list of mirrors.

error when opening the template manager and also when I click on "Download and install" button
and

There are no mirrors available.

for "open in web browser" and "copy Mirror URL" action.
Export template archive is located as the usual location:
https://downloads.tuxfamily.org/godotengine/4.1/beta2/Godot_v4.1-beta2_export_templates.tpz (this one may not work)
https://downloads.tuxfamily.org/godotengine/4.1/dev2/Godot_v4.1-dev2_export_templates.tpz (this one worked before)
https://downloads.tuxfamily.org/godotengine/4.1/dev4/Godot_v4.1-dev4_export_templates.tpz
install export templates from file work.
Steps to reproduce
Open Godot editor
click on project/export
try to load template from the web
Minimal reproduction project
N/A

@YuriSizov Seems like you forgot to copy the mirrorlist to the new website host (godotengine.org/mirrorlist).

I copied it manually from TF, should be fixed for now. We should discuss how we want to keep it properly synced going further.

We should discuss how we want to keep it properly synced going further.

I think we can just generate them with the website, it's all static information and we already track various version information with the website to generate download pages. I will implement it on Monday.

Seeing this in 4.1.rc1.official.

That's weird, because the mirrorlist seems to be properly configured: https://godotengine.org/mirrorlist/4.1.rc1.json

GitHub was down for awhile earlier today. I wonder if that's the cause

Retrying now. Yes it seems it was just temporary. Sorry about that. Thanks.


feat(client): support discarding query results

Change Summary
Please summarise the changes this pull request is making here.
Checklist

[ ] Unit tests for the changes exist
[ ] Tests pass without significant drop in coverage
[ ] Documentation reflects changes where applicable
[ ] Test snapshots have been updated if applicable

Agreement
By submitting this pull request, I confirm that you can use, modify, copy and redistribute this contribution, under the terms of your choice.

@RobertCraigie regarding this test, should I add discard_result to Batcher.create's signature, and ignore the arg?

@RobertCraigie regarding this test, should I add discard_result to Batcher.create's signature, and ignore the arg?

Yes please. The current behaviour I'm going for is to maintain the same arguments for both batch queries and standard queries, even if it is redundant. I may change this in the future but for now I want to keep it like that.

Thank you for working on this!


HAWQ-1417. Fixed crash when ANALYZE after COPY because of invalid res…

…ource owner
The root cause is:  when ANALYZE is running, it will commit previous transaction, and begin one transaction for each relation to process analyze. However some code added before begining transactions, which means in this time, no transaction, and no resource owner neither.
The solution is to: create one resource owner for analyzeStmt(), and delete it after processing it.

+1

The fix looks good. Is it possible to add unit test for it in src/test/unit/mock/backend/commands/analyze_mock.c?

(1) no file in master branch: src/test/unit/mock/backend/commands/analyze_mock.c
(2) Do we run CI on these mock test now?

@liming01, the mock file for analyze is generated. The way to add mock is at: https://github.com/apache/incubator-hawq/blob/master/src/test/unit/README.txt. Please take a look and see if it is good to leverage mock for your fix.
The mock test is covered in hawq ci. You can do that in local environment also: cd src/backend; make unittest-check
If it is hard to reproduce the issue with sql, I think mock is an option we can try.

After investigation, it seems we can not use cmock to reproduce HAWQ-1417.
The reason is: we need to mock all functions called in these functions, and also we need make one relation with catalog in memory, and data on disk.
I looked into some unit tests exists in backend, all tests are testing simple logic, and calling some independent modules, so the functions need to be mocked is very limited.

+1 for the fix as the mock of the verification is not feasible


Why can I prevent damage from low body temperature by wearing any leather armors?

I played version <IP_ADDRESS> of Homeostatic.Thank you for making the adjustments for Primal Winter, making my modpack more realistic and challenging.
But I wonder that why is it that even though my body temperature is already so low, I am still unharmed while wearing a leather helmet?
Through testing, other materials of armor with insulation properties did not have this effect.Is this a characteristic that leather armor should have in Homeostatic?

In addition, I found that in the new mechanism of Homeostatic, satiety clearing does not seem to cause damage to players.
This seems unique to Homeostatic <IP_ADDRESS>.
I think it can reduce the frequency of damage caused by lack of satiety, but completely avoiding it is not good. This means that players can stay next to heat sources and live without eating anything.

I know about the leather armor thing. It is the Minecraft mechanic for frost damage. I could potentially change it, but it is intentional. As for not taking damage with food. That may be a Minecraft bug when wearing leather armor and freezing. Let me test. The mod is not doing anything special here. I will do some testing and see what the issue is.
What version of Minecraft are you using specifically?

I know about the leather armor thing. It is the Minecraft mechanic for frost damage. I could potentially change it, but it is intentional. As for not taking damage with food. That may be a Minecraft bug when wearing leather armor and freezing. Let me test. The mod is not doing anything special here. I will do some testing and see what the issue is.
What version of Minecraft are you using specifically?
I use Minecraft 1.19.2, and the version of Forge is 43.2.21.

I use Minecraft 1.19.2, and the version of Forge is 43.2.21.

Ok, the not taking damage thing when out of food is not from this mod. Are you using Healing Campfires mod? That would explain. It does appear that hunger is reduced very quickly (this is because of shivering).

Ok, I think I should set the maximum amount of food that is reduced quite a bit lower.
I would need to bypass the Minecraft mechanic when using leather armor to ignore freezing... thoughts?

I am going to reduce the maximum hunger loss by half. I'm looking into what to do about the freezing bypass for leather armor.

Thank you for your willingness to try my question! But when I use Homeostatic version <IP_ADDRESS>, it is normal for me to suffer damage when my satiety is 0. I haven't added any modules for healing campfires and modifying satiety mechanisms, perhaps there are some undiscovered conflicts? I will try it with you.

I think your adjustment to the maximum hunger loss is excellent. But what do you think about adjusting to the hunger threshold (below 6)? I feel that this will make the negative effects of the cold even more severe and more realistic.

Okay, I got it
Thank you very much. Your efforts have freed me from the torment of TAN anymore:)

I literally wrote this mod because of frustration with TAN. I wanted temperature to not be a magic thing, but something that tries to mimic how the human body works (within reason).

So Homeostatic does!
Expect the new version

After thinking on this a bit, I'm going to override the vanilla behavior for the tag that leather armor uses. It's way too overpowered.


Add resource limits for cattle-cluster-agent and cattle-node-agent to support Gatekeeper

What kind of request is this (question/bug/enhancement/feature request):
enhancement
Steps to reproduce (least amount of steps as possible):

Running Rancher v2.4.2
Deploy default custom cluster
Install Gatekeeper using Link

Result:

cattle-cluster-agent, cattle-node-agent, and kube-api-auth all will configured with no CPU/MEM limits and requests
Gatekeeper will block these pods from being deployed or upgraded due to the missing limits and requests

Other details that may be helpful:
The default enforce policy includes the rule "All pods must have resource limits"
Workaround
A) Exempt cattle-system namespace from Gatekeeper Link
B) Edit the workloads to include the following limits
cattle-cluster-agent
        resources:
          limits:
            cpu: "1"
            memory: 256Mi
          requests:
            cpu: 500m
            memory: 128Mi

cattle-node-agent
        resources:
          limits:
            cpu: "1"
            memory: 256Mi
          requests:
            cpu: 500m
            memory: 128Mi

kube-api-auth
        resources:
          limits:
            cpu: "1"
            memory: 256Mi
          requests:
            cpu: 500m
            memory: 128Mi

NOTE: These limits are only starting points and may need to be tuned for your environment and requirements.
Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI): v2.4.2
Installation option (single install/HA): HA

Any news on progress?


Ensure that multiple impls of UriBuilder don't cause a CCE

This is needed because the client should be usable
regardless of the server implementation of JAX-RS
that might be in use

It would be great to get this in 4.x. I assume I need to do another PR for that? If so, what branch would it target?

cc @asoldano

@geoand can you clarify which branch you're actually referring to? Ideally, next version of RESTEasy from master would be 4.6.0 and it would be meant for Quarkus.

And would that be created from master? If so, then I'm all good :)

And would that be created from master? If so, then I'm all good :)

Yes it will

Thanks 👍


Use k8s-test-infra devel image

This uses the images defined in https://github.com/NVIDIA/k8s-test-infra over per-project images.

Please also see the related comments here: https://github.com/NVIDIA/k8s-test-infra/pull/3#discussion_r1466644781

Please also see the related comments here: NVIDIA/k8s-test-infra#3 (comment)

https://github.com/NVIDIA/k8s-test-infra/pull/4

The linked PR looks good. Please update the use of GOLANG_VERSION.


Remove fetching of deleted channels on page load

Summary

Ticket Link
tba
Related Pull Requests

Has server changes (please link here)
Has mobile changes (please link here)

Screenshots
n/a
Release Note

NONE

/e2e-test

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

E2E tests not automatically triggered, because PR has no approval yet. Please ask a developer to review and then try again to attach the QA label.

/e2e-test MM_ENV="MM_FEATUREFLAGS_GRAPHQL=true"

Triggering E2E testing with options:
&map[MM_ENV:MM_FEATUREFLAGS_GRAPHQL=true]

Successfully triggered E2E testing!
GitLab pipeline | Test dashboard

Are you sure this isn't still needed? Archived channels can still be accessible in the UI depending on the server settings, so I'd think we'd still need them.
Isn't this action also used to resync after the websocket reconnects? It's possible that we'd need it to mark a channel as deleted if it was deleted while the websocket was disconnected

Heads up that as part of our efforts to move to a monorepo, we're closing out a number of older pull requests like this one to help streamline the effort.
If you'd like to preserve these changes -- even if you're not the original author! -- feel free to resubmit the pull request against the monorepo once it's ready. You can subscribe to mattermost-server-issue-22420 for status updates on this effort.

@M-ZubairAhmed, can you re-open this as a PR against https://github.com/mattermost/mattermost-server/tree/mono-repo? Any QA review we do here may not be valid after we make the mono-repo live: currently targeting Wednesday.


[Bug] Java client failed to handle duplicate data points

Search before asking

[X] I had searched in the issues and found no similar issues.

Apache SkyWalking Component
BanyanDB (apache/skywalking-banyandb)
What happened
BanyanDB identifies unique data points by their metadata(name and group), entity id, and timestamp. For points with the same of them, the database server uses the new value to override the old one.
Since the java client accepts the milliseconds as the timestamp's unit from the document, we should handle the same points on this part.
The possible solution is the influxdb module: https://github.com/apache/skywalking/blob/master/oap-server/server-storage-plugin/storage-influxdb-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/influxdb/base/RecordDAO.java#L53
What you expected to happen
None
How to reproduce
None
Anything else
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

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

BanyanDB identifies unique data points by their metadata(name and group), entity id, and timestamp. For points with the same of them, the database server uses the new value to override the old one.

This is what we expect, and trace segment ID would be duplicated. What is the issue about exactly?

The possible solution is the influxdb module: https://github.com/apache/skywalking/blob/master/oap-server/server-storage-plugin/storage-influxdb-plugin/src/main/java/org/apache/skywalking/oap/server/storage/plugin/influxdb/base/RecordDAO.java#L53

This is really not a good example to refer. I am talking with @dmsolr to get this out.

I have confirmed this is a bug in InfluxDB storage implementation. I have asked @dmsolr to adjust codes to fix this.
So, what is the case of BanyanDB actually?

As I mentioned, the data point id is a combination of metadata, entity_id, and timestamp. If an instance sends several segments in one millisecond, the last one that reaches banyandb will win, and each previous data point is dropped.

I have asked @dmsolr to adjust codes to fix this.

I would like to know how to fix this. banyandb could get benefits from the same solution. @dmsolr Would you please elaborate it a bit in this thread?

I have discussed this with @wu-sheng, and will be working on it.

@lujiajing1126 I will add a new annotation and attributed in storage model to define the global indices, such as trace id in trace and log, segment id + span id(you may miss before) in log.

@lujiajing1126 I will add a new annotation and attributed in storage model to define the global indices, such as trace id in trace and log, segment id + span id(you may miss before) in log.

Also, could you please add index type annotation to indicate which type of index should be used. For numeric type, we have two kinds of indexes,

TREE, (for range search)
INVERTED

I can, are these type available for global index or just general index(tag)?

I can, are these types available for global index or just general index(tag)?

I suppose it's OK to support simply general indexes, since currently we only have one global index, i.e. TraceID (String + inverted index).

One type, yes. But not just trace id, read https://github.com/apache/skywalking/issues/8845#issuecomment-1094453157
We need to add a virtual column for segment + span id, named as global_span_id. You will need them in trace and log correlation search


Fix leaks from Bison memory allocations

The Bison code creates a lot of objects with the new operator. These all end up causing memory leaks, because there is no corresponding call to delete. This change resolves this issue by using std::unique_ptr to create managed objects that will be destroyed once they are no longer needed.

Checklist

[ ] Language changes are updated in docs/reference_guide.md
[ ] User-visible and non-trivial changes updated in CHANGELOG.md
[ ] The new behaviour is covered by tests

Thanks for looking into this? Have you seen the discussion in #1055 ?

Thanks for looking into this! Have you seen the discussion in #1055 ?

@fbs I had not seen #1055, so thanks for pointing that out! Looks like I've gone down a very similar road to what was discussed in that thread, so happy to see that (provides some confirmation that it's the right approach).
This particular PR still has some issues that I have not been able to reproduce locally, so it's not passing the checks. Once I get things figured out, I can push out an update community to review and discuss, as a potential fix. If there's a pending fix from #1055, I'm obviously happy to go with that as well.

Looks like the build issue is exactly the thing discussed in #1055, a bison doesn't move http://www.comrite.com/wp/c11-stdunique_ptr-as-semantic-value-in-bison-c-mode/ .
It looks like we'd loose ubuntu 18.04 (lts) if we do this as it still has 3.0.x and no backports, so this might have to wait a few more years.
I think the delete approach from 1055 is better for now.

The  manual memory management is in  so I think thats the way to go for now. Moving to smart pointers would be nice but bumping bison versions means dropping ubuntu which we can't do just yet.
Maybe we can have AST constructors dedicated to the parser  that convert the raw pointers into smart pointers untill we can update bison.


fix: change dynamodb2 batch write response

Updating the Dynamodb2 Batch Write response format to match the official documentation:
http://docs.aws.amazon.com/amazondynamodb/latest/APIReference/API_BatchWriteItem.html

Coverage remained the same at 94.323% when pulling bd3dd23c6b3877b397d431402b7aa89bf0bcbac7 on skygeo:fix_dynamodb_batch_write into 79fe9df6cc58eb1192ae7ceb83ff956e59aa5537 on spulec:master.

Thanks!


AFR & ESP32: coreHTTP demo generates CMake Error - list GET given empty list

Describe the bug
The AFR Version 202012.00 generates the below
CMake Error at vendors/espressif/esp-idf/tools/cmake/scripts/expand_requirements.cmake:144 (list):
list GET given empty list
System information

Hardware board: ESP32-DevKitC
IDE used: N/A
Operating System [Windows 10 x64 -- Version: 20H2 -- OS Build: 19042.685]
Version of FreeRTOS: AFR Version 202012.00 downloaded from console.aws.amazon.com
Project: coreHTTP demo (#define CONFIG_CORE_HTTP_MUTUAL_AUTH_DEMO_ENABLED)

Expected behavior
The below cmake command should execute without errors.
cmake -DVENDOR=espressif -DBOARD=esp32_devkitc -DCOMPILER=xtensa-esp32 -DAFR_ESP_LWIP=1 -GNinja -S . -B build
Screenshots or console output
Below is the console log
E:\FreeRTOS Device Software Configurations\coreHTTP_demo-1608663093143\FreeRTOS>cmake -DVENDOR=espressif -DBOARD=esp32_devkitc -DCOMPILER=xtensa-esp32 -DAFR_ESP_LWIP=1 -GNinja -S . -B build
-- The C compiler identification is GNU 5.2.0
-- The CXX compiler identification is GNU 5.2.0
-- The ASM compiler identification is GNU
-- Found assembler: C:/Program Files/Espressif/ESP-IDF Tools/tools/bin/xtensa-esp32-elf-gcc.exe
-- Found Git: C:/Program Files/Git/cmd/git.exe (found version "2.29.2.windows.3")
-- Checking Python dependencies...
Python requirements from E:/FreeRTOS Device Software Configurations/coreHTTP_demo-1608663093143/FreeRTOS/vendors/espressif/esp-idf\requirements.txt are satisfied.
-- IDF_TARGET not set, using default target: esp32
-- Building for target esp32
CMake Error at vendors/espressif/esp-idf/tools/cmake/scripts/expand_requirements.cmake:144 (list):
  list GET given empty list
Call Stack (most recent call first):
  vendors/espressif/esp-idf/tools/cmake/scripts/expand_requirements.cmake:199 (filter_components_list)

CMake Error at vendors/espressif/esp-idf/tools/cmake/idf_functions.cmake:339 (message):
  Failed to expand component requirements
Call Stack (most recent call first):
  vendors/espressif/boards/esp32/CMakeLists.txt:536 (idf_import_components)
  CMakeLists.txt:70 (include)

-- Configuring incomplete, errors occurred!
See also "E:/FreeRTOS Device Software Configurations/coreHTTP_demo-1608663093143/FreeRTOS/build/CMakeFiles/CMakeOutput.log".
See also "E:/FreeRTOS Device Software Configurations/coreHTTP_demo-1608663093143/FreeRTOS/build/CMakeFiles/CMakeError.log".

E:\FreeRTOS Device Software Configurations\coreHTTP_demo-1608663093143\FreeRTOS>

To reproduce
Steps to reproduce the behaviour:

Login and download FreeRTOS from the FreeRTOS console.
Create a new software configuration with

FreeRTOS Version - 202012.00 (Latest)
Hardware Platform - ESP32 DevKitC
Library - coreHTTP

Download and unzip to extract the folder contents.
Open Command Prompt.
Change the current working directory path to ..\FreeRTOS\
Run the cmake command and observe the error generated. Cmake command and logs are shared above.

Code to reproduce the bug
N/A
Additional context
The CMakeError.log and CMakeOutput.log files are enclosed.
CMakeError.log
CMakeOutput.log
Thank you!
Dipen

Namaste Community Member,
Update:
The same observation/ error holds true for https_client_demo downloaded from the AWS IoT Console with AFR Version 202002.00.
The cmake command is failing when attempting to generate the build-system before running the actual ninja command for code compilation. Also please note, the cmake command is run "as is" on the demo project downloaded, w/o any file modifications.
Thanks | Regards,
Dipen

Hi @dipen-1337lab,
I followed your step and downloaded the code from the console. But it works with my local setup.
I found there is a similar issue with what you are having now: https://github.com/aws/amazon-freertos/issues/2286
I looks  the path cannot contain spaces, and your path "E:\FreeRTOS Device Software Configurations\coreHTTP_demo-1608663093143\FreeRTOS" does contain the space. Please try to remove the space in your and see if it works.
Thank you!
Ming

Namaste @mingyue86010,
Thank you for your assistance on this issue. Looks like the issue is indeed related to spaces in path.
Below is the console log confirming the successful generation of the binary image, when the path does not contain any spaces.
[55/55] Generating bootloader.bin
esptool.py v2.8
[820/829] Building C object CMakeFiles/aws_demos.dir/vendors/espressif/boards/esp32/aws_demos/application_code/main.c.obj
../vendors/espressif/boards/esp32/aws_demos/application_code/main.c: In function 'prvMiscInitialization':
../vendors/espressif/boards/esp32/aws_demos/application_code/main.c:174:13: warning: unused variable 'uartRet' [-Wunused-variable]
     int32_t uartRet;
             ^
[829/829] Generating aws_demos.bin
esptool.py v2.8

E:\FreeRTOS_Device_Software_Configurations\coreHTTP_demo-1608663093143\FreeRTOS\build>

Thanks | Regards,
Dipen

Namaste @mingyue86010,
Thank you for your assistance on this issue. Looks like the issue is indeed related to spaces in path.
Below is the console log confirming the successful generation of the binary image, when the path does not contain any spaces.
[55/55] Generating bootloader.bin
esptool.py v2.8
[820/829] Building C object CMakeFiles/aws_demos.dir/vendors/espressif/boards/esp32/aws_demos/application_code/main.c.obj
../vendors/espressif/boards/esp32/aws_demos/application_code/main.c: In function 'prvMiscInitialization':
../vendors/espressif/boards/esp32/aws_demos/application_code/main.c:174:13: warning: unused variable 'uartRet' [-Wunused-variable]
     int32_t uartRet;
             ^
[829/829] Generating aws_demos.bin
esptool.py v2.8

E:\FreeRTOS_Device_Software_Configurations\coreHTTP_demo-1608663093143\FreeRTOS\build>

Thanks | Regards,
Dipen


REFACTORING: list of small issues

[ ] get rid of renderer.js cause it is just an helper now.
[ ] move the editor-resize section (line 420 app.js) away . in editor.js i guess...
[x] get rid of loadVersion (line 994 - app.js) and move to the settings tabs.
[x] chromeCloudSync (line 280) but that should in his own file i guess (btw could you check how it works?)
[ ] refactor all the resizing functions.
[ ] UniversalDapp does not trigger anymore debugRequested, we should remove the comment and the registering to that event.
[ ] Test and refactor Copy file to another instance

window.addEventListener('message', function (ev) {
    if (typeof ev.data === typeof [] && ev.data[0] === 'loadFiles') {
      loadFilesCallback(ev.data[1])
    }
  }, false)

[ ] move loadingFromGist to helper

[ ] check whether every function API are actually used and remove unused

@serapath could you check please what is already done / should be done here?


Use wsl.exe instead of bash.exe on newer versions of Windows

I think from 1709 we should be using wsl.exe instead of bash.exe?
https://github.com/Microsoft/vscode/blob/b220a05fc30a99e057b70e2977e40e8a9ecaeb9f/src/vs/workbench/parts/terminal/electron-browser/terminalService.ts#L219
Could be related to issues like this? https://github.com/Microsoft/vscode/issues/48331

@bitcrazed from what version of Windows should we start recommending wsl.exe instead of bash.exe?

I believe the first stable build it was available in is build 16299. Oh and I noticed your commit says wsl.exe and ubuntu.exe. You better add Debian, OpenSuse, and Kali to the list (yes Kali might be a bit more questionable but let's just roll with it as it's an available rolling distro for WSL).
You should also probably put a checker out there for other .exe distros since we can now build our own distro apps but that can be a separate issue/commit.

@DarthSpock so it's not super important if these are missing from the list in https://github.com/Microsoft/vscode/commit/e1a2ea39c9fbc434f57b4909efd4320364db7624, I don't think it's worth adding a setting or anything for extra distros (yet?).
We can add the other standard distros now though, do you know the exact case-sensitive exe names for them?

Looks like this is fixed:
			'WSL Bash': [${system32Path}\${useWSLexe ? 'wsl.exe' : 'bash.exe'}],
useWSLexe checks the windows version.

@alexr00 thanks for checking!

We'd recommend wsl.exe instead of bash.exe for Spring 2018 Update or later.
Rich Turner | Sr. Program Manager | Windows Console & Command-Line | Microsoft
e: richturn<EMAIL_ADDRESS>| t: @richturn_mshttps://twitter.com/richturn_ms | c: +1<PHONE_NUMBER>

From: Daniel Imms<EMAIL_ADDRESS>Sent: Friday, May 11, 2018 11:03
To: Microsoft/vscode
Cc: Rich Turner; Mention
Subject: Re: [Microsoft/vscode] Use wsl.exe instead of bash.exe on newer versions of Windows (#49713)
@bitcrazedhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fbitcrazed&data=02|01|richturn%40microsoft.com|5810b12bdfb14acf131c08d5b7698e33|72f988bf86f141af91ab2d7cd011db47|1|0|636616586337597640&sdata=qw7J31O%2FR16I3MBvwpIcAovGvNvJnn3e0dlc%2BA1EZlA%3D&reserved=0 from what version of Windows should we start recommending wsl.exe instead of bash.exe?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoft%2Fvscode%2Fissues%2F49713%23issuecomment-388440409&data=02|01|richturn%40microsoft.com|5810b12bdfb14acf131c08d5b7698e33|72f988bf86f141af91ab2d7cd011db47|1|0|636616586337597640&sdata=7Jv33l2k%2FGWzO7KbE%2By5kbOo9gYjoqRViRETxixldNk%3D&reserved=0, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAA6tnrf-YRoHWSzeWgUb6mUTFp1HR1Leks5txdKIgaJpZM4T71fZ&data=02|01|richturn%40microsoft.com|5810b12bdfb14acf131c08d5b7698e33|72f988bf86f141af91ab2d7cd011db47|1|0|636616586337597640&sdata=aRcDGcoNDX0EhKbg%2FAtKLYr8EWigD8gpZENrEEoT6po%3D&reserved=0.


Map shows up on Windows 10, but not on Android 14

Mapsui Version
5.0.0-beta.4
Mapsui Platform
MAUI
Device
Android 14
Describe the bug
Map is blank on Android
To Reproduce
Make a grid
        <Grid x:Name="EventMapGrid"
              ColumnDefinitions="*"
              RowDefinitions="*, auto"
              Margin="16">

Use the get started code to make the map and put it in the grid
        var mapControl = new Mapsui.UI.Maui.MapControl();
        mapControl.Map.Layers.Add(
            Mapsui.Tiling.OpenStreetMap.CreateTileLayer()
            );
        EventMapGrid.Add(mapControl, row:0);

Expected behavior
The map to be displayed like it is on Windows 10.

It turns out to be a MAUI bug.
This code in the manifest
	<uses-permission android:name="android.permission.ACCESS_FINE_LOCATION" />
	<uses-permission android:name="android.permission.ACCESS_COARSE_LOCATION" />

and this code here
        status = await Permissions.RequestAsync<Permissions.LocationWhenInUse>();

does not open a permission dialog.

Never mind, it still does not work when there is location permission.


perspective divide for shadow maps

perspective divide is necessary for perspective cameras and is still correct for orthographic cameras since for ortho w is always 1. This change would allow users making shadow maps for point lights to use the depth.vertex.glsl and default.vertex.glsl vertex shaders if they want

Thanks @ryanastout, implemented here https://github.com/libgdx/libgdx/commit/bc864a01de2e9ff37ce958ace597e31f944dd39a


PDX-357: Adding tag while publishing npm plugin

Adding tag while publishing npm plugin

@Palak-Bansal-Provar Please add reference of the PR/commit which Himanshu did.


DataBackground: using an image decreases performance

Question: I included a background image to the FormsPlot component.
I'm making a heatmap graph that updates 25 times per second.
The data matrix is 96x96.
When I maximize the window the refresh rate drops drastically to approximately 10 Hz.
Making HMap.Smooth = false; It seems to improve a little.
ScottPlot Version: 5.026
Code Sample: I used the HeatmapLive as code samples
I inclued a checkBox called chkShowBackground to enable and disable the bacground
using ScottPlot;
namespace WinForms_Demo.Demos;

public partial class HeatmapLive : Form, IDemoWindow
{
    readonly ScottPlot.Plottables.Heatmap HMap;
    readonly System.Windows.Forms.Timer Timer;
    readonly double[,] HeatmapData;
    int UpdateCount = 0;
    private long _lastTickCount = 0;

    public string Title => "Live Heatmap";

    public string Description => "Demonstrates how to display a heatmap with data that changes over time";

    public HeatmapLive()
    {
        InitializeComponent();

        HeatmapData = ScottPlot.Generate.Sin2D(96, 96, multiple: 3);
        HMap = new ScottPlot.Plottables.Heatmap(HeatmapData);
        // Add opacity to the heatmap
        HMap.Opacity = 0.7;
        HMap.Smooth = false;

        formsPlot1.Plot.PlottableList.Add(HMap);

        Timer = new() { Enabled = true, Interval = 40 };
        Timer.Tick += (s, e) => ChangeData();
        _lastTickCount = System.Diagnostics.Stopwatch.GetTimestamp();
    }

    private void ChangeData()
    {
        UpdateCount++;
        if (UpdateCount % 5 == 0)
        {
            long tickCount = System.Diagnostics.Stopwatch.GetTimestamp();
            long dif = tickCount - _lastTickCount;
            _lastTickCount = tickCount;
            double frequency = 1000 * 5 / new TimeSpan(dif).TotalMilliseconds;
            Text = $"Updated {frequency} times";
        }

        Random rand = new();
        for (int y = 0; y < HeatmapData.GetLength(0); y++)
        {
            for (int x = 0; x < HeatmapData.GetLength(1); x++)
            {
                HeatmapData[y, x] += rand.NextDouble() - .5;
            }
        }

        HMap.Update();
        formsPlot1.Refresh();
    }

    private void chkShowBackground_CheckedChanged(object sender, EventArgs e)
    {
        if (chkShowBackground.Checked)
        {
            formsPlot1.Plot.DataBackground.Image = SampleImages.MonaLisa();
            formsPlot1.Plot.DataBackground.ImagePosition = ImagePosition.Stretch;
        }
        else
        {
            formsPlot1.Plot.DataBackground.Image = null;
        }
    }
}

For anything involving Bitmaps, you really want to be using hardware acceleration. Sampling textures on the CPU is really slow.
In short, try experimenting with the GLElement in SP5

Thanks for reporting this!
I'm going to re-state the core issue reported: assigning Plot.DataBackground.Image slows down rendering.
I suspect this topic is unrelated to heatmpaps.
I agree that rendering bitmaps over large areas can be slow. This is the method that renders the plot's data background image. I'm not sure if there's much that can be done to improve performance:
https://github.com/ScottPlot/ScottPlot/blob/028cd0e79e07af7b9c1d9a10aa09368034561044/src/ScottPlot5/ScottPlot5/Primitives/BackgroundStyle.cs#L38-L48


Read DPI component quantities from on-chain via set.js

Summary of Changes

This change reads DPI and MVI streaming fees from on-chain

To-do

[ ] unit tests with a mock set.js provider

Local development

yarn start
Navigate to https://www.indexcoop.com/dpi
Connect Metamask wallet
Observe streaming fees is 0.0 and console logs

In testing I observed no difference between the Token sets server quantity and the on-chain quantity:

WIP. I'm observing that streaming fees for DPI and MVI appear to be 0 when read from on-chain. I need to investigate if set.js is actually fetching these values

Noting that we should make a PR to display mint/redeem fees on BTC/ETH2x-FLI in the future. Not sure those are exposed by set.js atm though.

Added to google doc


First error: dlrs:Too many query rows: 50001

A little background, we have 100 or so custom rollups in our organization, and we are trying to consolidate into one scheduled job using the RollupJob class instead of scheduling each one individually, since we hit the scheduled apex job limit of 100. However we have been getting the error "First error: dlrs:Too many query rows: 50001". Thinking it was a query size issue, we incrementally disabled scheduled rollups and eventually realtime calculations down to 0, and we still get the same number of errors (7).
Is this an erroneous or expected error? Running the scheduled job with nothing to calculate should not give any query errors yet it continues to do so.

@ehebert7 are you still having trouble with this? Were you able to figure out where the errors were coming from?

Closing due to lack of response. @ehebert7 we can for sure re-open anytime! 👍


Could not open '/var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2': Permission denied

What happened:
The VM will be terminated because of Could not open '/var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2': Permission denied, I have to execute chmod 777 -R /var/lib/kubelets/pods timely to avoid the problem.
What you expected to happen:
I want this error disappear
How to reproduce it (as minimally and precisely as possible):
I create the container image by this way following the user-guide([Disks and Volumes - KubeVirt User-Guide](https://kubevirt.io/user-guide/virtual_machines/disks_and_volumes/#containerdisk-workflow-example)) :
cat << END > Dockerfile
FROM scratch
ADD --chown=107:107 fedora25.qcow2 /disk/
END

docker build -t vmidisks/fedora25:latest .

Then I create the VMI by this way:
kubectl create -f vmi.yaml
---
apiVersion: kubevirt.io/v1
kind: VirtualMachineInstance
metadata:
  labels:
    special: vmi-fedora
  name: vmi-fedora
spec:
  domain:
    devices:
      disks:
      - disk:
          bus: virtio
        name: containerdisk
      - disk:
          bus: virtio
        name: cloudinitdisk
      rng: {}
    resources:
      requests:
        memory: 1024M
  terminationGracePeriodSeconds: 0
  volumes:
  - containerDisk:
      image: zhlhahaha/fedora-cloud-container-disk-demo:aarch64
    name: containerdisk
  - cloudInitNoCloud:
      userData: |-
        #cloud-config
        password: fedora
        chpasswd: { expire: False }
    name: cloudinitdisk

kubectl logs virt-launcher-vmi-fedora-mncs9
{"component":"virt-launcher","level":"error","msg":"internal error: qemu unexpectedly closed the monitor: 2022-05-11T01:35:41.666600Z qemu-kvm: -blockdev {\"driver\":\"file\",\"filename\":\"/var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2\",\"node-name\":\"libvirt-2-storage\",\"cache\":{\"direct\":true,\"no-flush\":false},\"auto-read-only\":true,\"discard\":\"unmap\"}: Could not open '/var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2': Permission denied","pos":"qemuProcessReportLogError:2051","subcomponent":"libvirt","thread":"211","timestamp":"2022-05-11T01:35:41.718000Z"}

Few seconds later,  VM will be terminated.
Additional context:
I execute ls command on virt-launcher-pod, and I noticed that the user and group of disk.qcow2 are root rather than qemu.
I think this might be the reason why qemu cannot open it,  but I don't know how to solve this problem.
[root@localhost fedora]# kubectl get pods
kuNAME                             READY   STATUS      RESTARTS   AGE
virt-launcher-vmi-fedora-mncs9   0/2     Completed   0          7m50s

[root@localhost fedora]# kubectl exec pod/virt-launcher-vmi-fedora-mncs9 -- /usr/bin/ls -la /var/run/kubevirt-ephemeral-disks/disk-data/containerdisk
total 204
drwxr-x--- 2 root root   4096 May 11 01:35 .
drwxr-x--- 3 root root   4096 May 11 01:35 ..
-rw-r----- 1 root root 196672 May 11 01:35 disk.qcow2

And this problem might be related to my os-release(openEuler 22.03 LTS), I guess, because on my fedora environment, it works fine.
Environment:

KubeVirt version (use virtctl version):
$ LATEST=$(curl -L https://storage.googleapis.com/kubevirt-prow/devel/nightly/release/kubevirt/kubevirt/latest-arm64)
LATEST=20220509

Kubernetes version (use kubectl version):
Client Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.1", GitCommit:"86ec240af8cbd1b60bcc4c03c20da9b98005b92e", GitTreeState:"clean", BuildDate:"2021-12-16T11:41:01Z", GoVersion:"go1.17.5", Compiler:"gc", Platform:"linux/arm64"}

VM or VMI specifications:
---
apiVersion: kubevirt.io/v1
kind: VirtualMachineInstance
metadata:
  labels:
    special: vmi-fedora
  name: vmi-fedora
spec:
  domain:
    devices:
      disks:
      - disk:
          bus: virtio
        name: containerdisk
      - disk:
          bus: virtio
        name: cloudinitdisk
      rng: {}
    resources:
      requests:
        memory: 1024M
  terminationGracePeriodSeconds: 0
  volumes:
  - containerDisk:
      image: zhlhahaha/fedora-cloud-container-disk-demo:aarch64
    name: containerdisk
  - cloudInitNoCloud:
      userData: |-
        #cloud-config
        password: fedora
        chpasswd: { expire: False }
    name: cloudinitdisk

Cloud provider or hardware configuration: N/A

OS (e.g. from /etc/os-release):
NAME="openEuler"
VERSION="22.03 LTS"
ID="openEuler"
VERSION_ID="22.03"
PRETTY_NAME="openEuler 22.03 LTS"
ANSI_COLOR="0;31"

Kernel (e.g. uname -a):
Linux localhost.localdomain 5.10.0-<IP_ADDRESS>.oe2203.aarch64 #1 SMP Wed Apr 13 10:27:16 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux

Install tools:
$ LATEST=$(curl -L https://storage.googleapis.com/kubevirt-prow/devel/nightly/release/kubevirt/kubevirt/latest-arm64)
$ kubectl apply -f https://storage.googleapis.com/kubevirt-prow/devel/nightly/release/kubevirt/kubevirt/${LATEST}/kubevirt-operator-arm64.yaml
$ kubectl apply -f https://storage.googleapis.com/kubevirt-prow/devel/nightly/release/kubevirt/kubevirt/${LATEST}/kubevirt-cr-arm64.yaml

Others: N/A

After I tried it again, I noticed another confusing phenomenon:
disk.qcow2 belongs to qemu fleetingly, at first. Then the owner turn into root.
[root@localhost fedora]# kubectl create -f vmi.yaml
virtualmachineinstance.kubevirt.io/fedora created
[root@localhost fedora]# kubectl exec `kubectl get pods | awk '{print $1}' | sed -n 2p` -- /usr/bin/ls -la /var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2
-rw-r----- 1 qemu qemu 196688 May 11 07:55 /var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2
[root@localhost fedora]# kubectl exec `kubectl get pods | awk '{print $1}' | sed -n 2p` -- /usr/bin/ls -la /var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2
-rw-r----- 1 root root 196688 May 11 07:55 /var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2
[root@localhost fedora]# kubectl exec `kubectl get pods | awk '{print $1}' | sed -n 2p` -- /usr/bin/ls -la /var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2
-rw-r----- 1 root root 196688 May 11 07:55 /var/run/kubevirt-ephemeral-disks/disk-data/containerdisk/disk.qcow2

Hi @carpediemtal ,
can you check the permission in the containerdisk container?

I tried it on Ubuntu OS on Arm64 server. The issue does not happen. Can you try to attach the VM image as a normal volume to a kubernetes pods (not using kubevirt) and see if the ownership of disk is right?

Hi @carpediemtal , can you check the permission in the containerdisk container?
@xpivarc
Thanks for your reply.
I'm quite new to kubernetes and I don't know how to do what you told me. Would you mind to tell me more?

I tried it on Ubuntu OS on Arm64 server. The issue does not happen. Can you try to attach the VM image as a normal volume to a kubernetes pods (not using kubevirt) and see if the ownership of disk is right?

@zhlhahaha
emmm, I don't know how to do it correctly... Would you mind to give me a pod.yaml  or something else?

@carpediemtal it isn't easy too achieve as the VM disk is delivered as a container image. If you want to check the permission of the original disk (not the snapshot), you can try to access the disk from the host. Here, the steps after you logged as root on the node where the virt-launcher pod is running:
$ ls -lsh disk/
total 16M             crictl ps |grep volumecontainerdisk
74b9d1bd65d7a       3d3efa4bd1d34c2578a000183a8a9de7b5608fc5e202052c090cc456cfd0bdae                                                       6 minutes ago       Running             volumecontainerdisk       0                   762c87cb6e63a
$ crictl inspect 74b9d1bd65d7a |grep path |grep overlay
        "path": "/var/lib/containers/storage/overlay/59ca64fe20dc8cd3ca10183cb058b45001efa616b73d24bd69793860ddc84d2e/merged"
$ /var/lib/containers/storage/overlay/59ca64fe20dc8cd3ca10183cb058b45001efa616b73d24bd69793860ddc84d2e/merged
$  ls -slh disk/
total 16M
16M -r--r-----. 1 107 107 16M Jan  1  1970 downloaded

I confirmed this issue still happen on Eular
The root cause is the kubernetes.io~empty-dir/ephemeral-disks/disk-data/disk-0/ and kubernetes.io~empty-dir/ephemeral-disks/disk-data under /var/lib/kubelet/pods/ is not auto set as '755'
e.g.
drwxr-x--- 2 root root 24 Aug 15 17:00 disk-0
Can walk around by changing manually, but still want someone can fix it.


[BUG] Get-PnPPage not workin on a subsite

Reporting an Issue
I am connection with PnP-Powershell to a SharePoint Online Subsite and trying to get a page with Get-PnpPage and it wont find any page.
I am connecting with interactive or useWeblogin because of MFA
Expected behavior
Running Get-PnPPage to retrive page data with webparts etc.
Actual behavior
The command wont find any page.
Steps to reproduce behavior
Connect to a subsite in SharePoint online and try to get Get-PnPPage Home
What is the version of the Cmdlet module you are running?
1.11.0
Which operating system/environment are you running PnP PowerShell on?

[ x] Windows
[ ] Linux
[ ] MacOS
[ ] Azure Cloud Shell
[ ] Azure Functions
[ ] Other : please specify

Error with Export-PnPPage
Message          : Object reference not set to an instance of an object.
Stacktrace       :    at PnP.Framework.Provisioning.ObjectHandlers.Utilities.ClientSidePageContentsHelper.ExtractClientSidePage(Web web,
ProvisioningTemplate template, ProvisioningTemplateCreationInformation creationInfo, PnPMonitoredScope scope, PageToExport page)
at PnP.PowerShell.Commands.Provisioning.Tenant.ExportPage.ExtractTemplate(String dirName, String fileName, ExtractConfiguration
configuration)
at PnP.PowerShell.Commands.Provisioning.Tenant.ExportPage.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
ScriptLineNumber : 1

I just testet Add-PnPPage on a subsite and it was created on the SiteCollection level. I just connected to the subsite. I even used it with the -Web parameter.

I think i found out that this problem does not have anything to do with the subsite architecture.
I had two other sitepage libraries from an migration on the side.
After i moved the pages and deleted the libraries the command works as expected.


Pagination and Sorting Support

Investigate ways to support Pagination, for example connecting to pagination support in Spring Data repositories. There is also a specification as well. There are a different ways to control navigation, typically offset or cursor based. Spring Data currently supports offset based pagination.
Pagination depends on a predictable sort order. There doesn't seem to be any spec or ongoing effort to converge on a common approach. There is a talk on the topic that provides a good overview.

[x] #619
[x] #620
[x] #597
[x] #656

I'm trying to implement this, but just wanted to check before. When is this feature going to come out if ever?

@SeriousSamV I don't think this is an easy issue to tackle and we probably need to spend some time designing and iterating on that problem. This issue is not scheduled yet so we don't have a concrete plan for it. Voting for this issue and sharing useful information about use cases (see previous comments) is a way to help us make progress on this.

Thanks again for the fantastic work on this project, it has greatly simplified the integration of graphql-java into an existing SpringBoot project.
I don't see much movement on this issue and it doesn't look like it'll be tackled as part of RC1 so I figured I'll give it a push. Pagination support is a pretty common requirement for APIs.
In terms of use-cases, we are in the process of transitioning some GET endpoints from REST to GraphQL. Previously, these endpoints return a org.springframework.data.domain.Page object, while consuming a Pageable query parameter. This is a relatively common approach for implementing paging support.
As part of the initial transition, we are utilizing an offset-based approach supported by our client. This was straightforward to implement by exposing offset/limit query arguments and creating a Pageable object from these arguments. This object can then be directly passed into a Repository.findAll method.
Ideally though, a cursor-based implementation such the relay cursor connections specification should be chosen. Besides relay, there seems to be a shift towards clients supporting that specification as a standard (e.g. see apollo).
If the full relay connections specification looks too daunting, perhaps simpler offset/cursor-based pagination implementations can be first supported? It'll be nice to rely on an official implementation vs. hand-rolling our own.

Is there any "temporary" of implementing pagination while this issue is addressed?

Hi! Is there any update of this issue?
We were using https://github.com/graphql-java-kickstart/graphql-spring-boot in some of our projects. It already provides pagination using relay classes -> https://www.graphql-java-kickstart.com/tools/relay. These relay classes are already defined in com.graphql-java library, so would be available in this project too. It's not necessary to reinvent the wheel :)
Probably the first step to support relay/pagination is to recognize relay directives in the schema.graphqls dinamically, generating the necessary classes.

Hello, I'd like to share my workaround for Pagination and Sorting Support for Spring GraphQL, using Kotlin, although it doesn't work with cursors (as per https://github.com/spring-projects/spring-data-commons/issues/2151).
https://gist.github.com/Michal-Kucera/a0ad1572a0c212dc8b67b8136c7cb78c
P.S. I didn't try it out with nested schemas..
Once Spring data common supports cursors, we may reuse classes from graphql-java, relay package, i.e.:

graphql.relay.Connection
graphql.relay.Edge
graphql.relay.PageInfo
graphql.relay.ConnectionCursor

There is also an interesting class graphql.relay.Relay, which might be worth investigating further.
Cheers!
Michal

Hi. I am also interested in the pagination support. Especially in the QuerydslDataFetcher context.
For adding ability to customize QuerydslDataFetcher would be sufficient. right now I don't see a way to add any code that would run at the end of ManyEntityFetcher.get method, without reimplementing big part of QuerydslDataFetcher and unexposed classes it uses.

Thanks for the comment, @cezary-butler. I've created #597 as a more specific issue for now. Let's continue the discussion there.

I've turned this into an umbrella issue. See issue description at the top for a list of sub-tasks for the actual work.

@chop-sui this new feature will be  available as of Spring for GraphQL 1.2.0 (so Spring Boot 3.1.0). We don't backport new features.

It also depends on what exactly you need from pagination. If using Spring Data pagination, then yes we'll have 1st class support for that in 1.2 (only), but that in turn depends on Spring Data's cursor support that's also in development. You can also adapt other persistence pagination mechanisms, but obviously that can't be built in.
If it's just Connection schema type generation, then it's straight forward, see ConnectionTypeDefinitionConfigurer for example.

@bclozel @rstoyanchev Thank you for comfirming. I am planning to use Spring Data pagination with connection style GraphQL pagination. I will look into migrating to Spring Boot 3 as the project has started only recently.

I'm closing this umbrella issue since all sub-tasks are now complete.


The term "one-shot" is not defined in the documentation.

A one-shot, futures-aware channel

Creates a new futures-aware, one-shot channel.

It's unclear to me if this means single consumer single producer or if this means you can only send one message on the channel and not two or whether only one message can exist inside the channel at a time.
Seems like this would be a very useful piece of information to add to the documentation.

Yup, I'd be happy to accept a PR clarifying! :)

I created a PR(#2198) to update the docs regarding this issue. Please take a look! Thank you :cat2:


NullPointerException on loading XmlSuites programmatically

A "NullPointerException" dropped by TestNG on loading XML suites.
This problem does NOT occur, when we use 6.9.9 version.
But, as long as 6.9.10 version is loaded, the problem starts happening.
STEPS TO REPRODUCE

Run testng programmatically by creating instance: TestNG testng = new TestNG();
Add XML suites programmatically, like:
ArrayList runSuitesList = new ArrayList<>(some_length);
runList.add(suite);   //wehere evaluated in runtime    suite = C:\test\suites\smokeSuite.xml
XmlSuite suites = new XmlSuite();
suites.setSuiteFiles(runSuitesList);
testng.setXmlSuites(Arrays.asList(suites));
testng.run();

ACTUAL RESULT: During execution it drops following exception in the following block of code:
CODE (class = testng, line281):
Path rootPath = Paths.get(s.getFileName()).getParent();
EXCEPTION
Exception in thread "main" java.lang.NullPointerException
at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:98)
at sun.nio.fs.WindowsPathParser.parse(WindowsPathParser.java:77)
at sun.nio.fs.WindowsPath.parse(WindowsPath.java:94)
at sun.nio.fs.WindowsFileSystem.getPath(WindowsFileSystem.java:255)
at java.nio.file.Paths.get(Paths.java:84)
at org.testng.TestNG.initializeSuitesAndJarFile(TestNG.java:281)
at org.testng.TestNG.run(TestNG.java:1036)
at tests.TestRunner.main(TestRunner.java:79)
NOTE: the "String suiteFile" variable within following loop shows correct valid path to XML file
for (String suiteFile : s.getSuiteFiles()) {
Path rootPath = Paths.get(s.getFileName()).getParent();
try {
Collection childSuites = getParser(rootPath.resolve(suiteFile).normalize().toString()).parse();
for (XmlSuite cSuite : childSuites){
cSuite.setParentSuite(s);
s.getChildSuites().add(cSuite);
}
} catch (ParserConfigurationException | IOException | SAXException e) {
e.printStackTrace(System.out);
}
}

is this issue resolved? still getting the error in 6.9.10

@gvenkat91 - Please retry using the latest released version of TestNG viz., 6.14.2

@testng-team hi mahadevan, as of now downgraded testng as a work around. Will try with latest and let you know the results. Thanks a ton for your response!


[bug]: RuntimeError: The size of tensor (on Development and release-candidate-2-1-3 Branch)

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Linux
GPU
cuda
VRAM
12gb
What happened?
starting with commit d05b1b3 on development and release-candidate-2-1-3 branch, on ubuntu 22.04 running cuda, it causes an error when using hires and fails to make image
happens just after the first smaller image its made as its about to change to the larger size it throw an error
(changing to the commit before this one it works normally)
Traceback (most recent call last):
File "/InvokeAI/ldm/generate.py", line 459, in prompt2image
results = generator.generate(
File "/InvokeAI/ldm/invoke/generator/base.py", line 90, in generate
image = make_image(x_T)
File "/opt/conda/envs/invokeai/lib/python3.10/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/InvokeAI/ldm/invoke/generator/txt2img2img.py", line 93, in make_image
z_enc = ddim_sampler.stochastic_encode(
File "/opt/conda/envs/invokeai/lib/python3.10/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
return func(*args, **kwargs)
File "/InvokeAI/ldm/models/diffusion/sampler.py", line 131, in stochastic_encode
extract_into_tensor(sqrt_alphas_cumprod, t, x0.shape) * x0
RuntimeError: The size of tensor a (88) must match the size of tensor b (96) at non-singleton dimension 3
Screenshots
No response
Additional context
No response
Contact Details
No response

I was having this issue on Mac as well on the development branch. Main worked fine. I reinstalled from scratch and now have this issue too https://github.com/invoke-ai/InvokeAI/issues/1422

In scripts/preload_models.py", line 503, and ldm/invoke/txt2mask.py , line 32
Swapped this line back

from clipseg_models.clipseg import CLIPDensePredT

from clipseg.clipseg import CLIPDensePredT

And it seems to work again.

Is the bug still present? I cannot reproduce it.

Never mind. I was able to reproduce it on a different machine. I will revert the offending PR now.

Fixed on development for me, but still happening on release-candidate-2-1-3

For posterity - this is not a MacOS issue; I have it on Windows as well

I've pulled the fix over from development into the release candidate and it will be OK for the release.


Attach replica set to workflow

Let me describe a high view sequence of my commands...
I've installed the workflow with helm, created two apps, made some git push at these apps, deleted the release, deleted the namespace because of Error: secrets "builder-key-auth" already exists, deleted the registry, database and builder s3 buckets because of the below deis-controller logs and finally reinstalled the workflow to the cluster with all necessary deis configuration.
Is there any way I could attach the running apps (started from the old release) to this new release so I could do deis apps and see them?
$ kubectl -n deis logs deis-controller-3875226455-sz1p8 -f
system information:
Django Version: 1.10.6
Python 3.5.2

Django checks:
System check identified no issues (2 silenced).

Health Checks:
Checking if database is alive
There was a problem connecting to the database
FATAL:  password authentication failed for user "XXXXXXXXXXXXXXX"

This issue was moved to teamhephy/workflow#22


net.sf.json.JSONException: 'object' is an array. Use JSONArray instead

Hello... looks like the plugin is having problem to parse a list respond.
client inteface: runner
target: noused
function: manage.present

from jenkins log:
Sending JSON: [{"client":"runner","mods":"","tgt":"notused","expr_form":"list","fun":"manage.present"}]
Jul 29, 2016 1:40:45 PM FINE com.waytta.saltstack
Received response: [["minion1","minion2","salt"]]

Errors:
Started by user admin
Building in workspace /var/lib/jenkins/workspace/_pull_minion_list_
ERROR: Build step failed with exception
net.sf.json.JSONException: 'object' is an array. Use JSONArray instead
    at net.sf.json.JSONObject.fromObject(JSONObject.java:167)
    at net.sf.json.JSONObject.fromObject(JSONObject.java:132)
    at com.waytta.Utils.validateFunctionCall(Utils.java:151)
    at com.waytta.SaltAPIBuilder.perform(SaltAPIBuilder.java:378)
    at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20)
    at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779)
    at hudson.model.Build$BuildExecution.build(Build.java:205)
    at hudson.model.Build$BuildExecution.doRun(Build.java:162)
    at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534)
    at hudson.model.Run.execute(Run.java:1720)
    at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43)
    at hudson.model.ResourceController.execute(ResourceController.java:98)
    at hudson.model.Executor.run(Executor.java:404)
Build step 'Send a message to Salt API' marked build as failure
Finished: FAILURE

Well, bummer. Most API results are returned in a different format which is what the plugin looks for. So in this case, it is choking on the result as it's a bit terse. Right now, I'm not sure what the best path forward is. I'll file an upstream bug report, but we're unlikely to get a API response normalization in the near future.

Just added a bit to master branch to support this case.

Released 2.0


not opening file and folder

Type: Bug
i can't add new file and folder in project. i do reinstalling app also.
 Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!


chore(cd): enable ubuntu-22.04-arm64 and alpine-x86_64 cross build

https://github.com/Kong/kong/actions/runs/3933773728 for artifact that includes new matrix in this PR


Start fleshing out a back end.

Start a simple skeleton backend
Needs to store card info and user info
Look into using firebase for this

Sort of relevant to #7


raftstore: allow querying if a peer is hibernated

What is changed and how it works?
What's Changed:
This PR adds a field to the response of status query /region/id that
indicates if the queried peer is hibernated.
Close #9556.
Check List
Tests

Manual test

tiup playground --kv.binpath bin/tikv-server &
curl <IP_ADDRESS>:20180/region/2

Release note

Add a field in region query response to show whether it's hibernated

LGTM

LGTM

/LGTM

/LGTM

/merge

/merge


subaccount-consumer: SubaccountDerivativeConsumer fetchPositions() is returning DerivativeLimitOrder

Hello, I noticed that in SubaccountDerivativeConsumer.ts, the fetchPositions() function is returning orders and not positions as expected.
fetchPositions() is actually using the same code as fetchOrders().

You are right, the fetchPositions() function should not exist in this consumer. If you want to get Subaccount's position it has to go through the fetchPositions() function in the DerivativeMarketConsumer.ts and pass the subaccountId as a parameter.


New bot: detect red-pill contracts

Here's the second bot of the "evasion-detection" flavor!
It detects "red-pill" contracts that detect simulation-env by checking the global variables against default values.
The detection happens on contract creation by static analysis.

I just force pushed to get back on top of the main branch ^^


Change the  callback to support jQuery (or any third party lib) onchange events

Currently there is no way to attach event handlers to select elements because of the way you dynamically create your own structure to display the select.
This callback adds this functionality through an alternative way, you can do:
$('#mySelect').material_select(myCallBackFunction);
Ofcourse, $('select').material_select(someFunction) wouldn't make sense since you would have a single function handling every select's change event, so you should just use this on a single element.
Accepting this pull request will not break any current code. Not passing in a callback simply doesn't fire it.

Please see c775467

Thanks for the help!

Glad i could be of help!