Add support for uploading file stream

上传文件流：
$handle = fopen('abc.txt', 'rb');
$client->uploadStream($bucket, $object, $handle);

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

如何在 drupal上  安装  这个模块啊

如何在 drupal上 安装 这个模块啊

在 composer.json 里添加
"require": {
    ...
    "drupal/ossfs": "1.x-dev",
    ...
}

PS: 已经离开了 Drupal 社区和 PHP 开发


[5.1] Use tinyint(1) for boolean type definition

Using tinyint(1) instead of just tinyint for SQLite boolean type works better. SQLite doesn't natively support boolean data type. A tinyint field without a size could be an integer but when using tinyint(1) then it's much safer to treat this as boolean.
Currently when I am running my app using MySql database I can easily identify my boolean fields with the type tinyint(1). However, when running my app using SQLite the same field shows up with type tinyint. So, basically getting different results when switching databases.

Please see the other rejections.

Oh wait. Missread this.

Please update the test case.
There was 1 failure:
1) DatabaseSQLiteSchemaGrammarTest::testAddingBoolean
Failed asserting that two strings are equal.
--- Expected
+++ Actual
@@ @@
-'alter table "users" add column "foo" tinyint not null'
+'alter table "users" add column "foo" tinyint(1) not null'
/home/travis/build/laravel/framework/tests/Database/DatabaseSQLiteSchemaGrammarTest.php:327


Issue with installing tinycudann on windows

Has anyone set up the environment on Windows? Getting an error when installing requirements when it tries to install tinycudann:
  DEPRECATION: tinycudann is being installed using the legacy 'setup.py install' method, because it does not have a 'pyproject.toml' and the 'wheel' package is not installed. pip 23.1 will enforce this behaviour change. A possible replacement is to enable the '--use-pep517' option. Discussion can be found at https://github.com/pypa/pip/issues/8559
  Running setup.py install for tinycudann ... \

And the error:
      nvcc warning : incompatible redefinition for option 'std', the last value of this option was used

      fully_fused_mlp.cu

      ninja: build stopped: subcommand failed.
      Traceback (most recent call last):
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\torch\utils\cpp_extension.py", line 2100, in _run_ninja_build
          subprocess.run(
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\subprocess.py", line 571, in run
          raise CalledProcessError(retcode, process.args,
      subprocess.CalledProcessError: Command '['ninja', '-v']' returned non-zero exit status 1.

      The above exception was the direct cause of the following exception:

      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File "C:\Users\User\AppData\Local\Temp\pip-req-build-mpc0_p7f\bindings/torch\setup.py", line 189, in <module>
          setup(
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\__init__.py", line 103, in setup
          return distutils.core.setup(**attrs)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\core.py", line 185, in setup
          return run_commands(dist)
                 ^^^^^^^^^^^^^^^^^^
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\core.py", line 201, in run_commands
          dist.run_commands()
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\dist.py", line 963, in run_command
          super().run_command(command)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\dist.py", line 988, in run_command
          cmd_obj.run()
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\command\install.py", line 78, in run
          return orig.install.run(self)
                 ^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\command\install.py", line 697, in run
          self.run_command('build')
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\dist.py", line 963, in run_command
          super().run_command(command)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\dist.py", line 988, in run_command
          cmd_obj.run()
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\command\build.py", line 131, in run
          self.run_command(cmd_name)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\cmd.py", line 318, in run_command
          self.distribution.run_command(command)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\dist.py", line 963, in run_command
          super().run_command(command)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\dist.py", line 988, in run_command
          cmd_obj.run()
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\command\build_ext.py", line 88, in run
          _build_ext.run(self)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 345, in run
          self.build_extensions()
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\torch\utils\cpp_extension.py", line 873, in build_extensions
          build_ext.build_extensions(self)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 467, in build_extensions
          self._build_extensions_serial()
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 493, in _build_extensions_serial
          self.build_extension(ext)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\command\build_ext.py", line 249, in build_extension
          _build_ext.build_extension(self, ext)
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\setuptools\_distutils\command\build_ext.py", line 548, in build_extension
          objects = self.compiler.compile(
                    ^^^^^^^^^^^^^^^^^^^^^^
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\torch\utils\cpp_extension.py", line 845, in win_wrap_ninja_compile
          _write_ninja_file_and_compile_objects(
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\torch\utils\cpp_extension.py", line 1774, in _write_ninja_file_and_compile_objects
          _run_ninja_build(
        File "C:\Users\User\AppData\Local\Programs\Python\Python311\Lib\site-packages\torch\utils\cpp_extension.py", line 2116, in _run_ninja_build
          raise RuntimeError(message) from e
      RuntimeError: Error compiling objects for extension
      [end of output]

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

× Encountered error while trying to install package.
╰─> tinycudann

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.

Just installed it on WSL instead


_posts/0000-01-02-Abdel896.md

Just made a change

Just made a change

okay this should work

okay this should work

oh no

oh no

this is good puoo

this is good puoo


Marking JAVA model,property @Deprecated

How to achieve this. I was able to deprecate the REST Controller methods.

Really this doesn't belong in the core product/library. There is extensibility hooks to implement this.
This should be simple to implement as a ModelPropertyBuilderPlugin. However there is no place to mark a property deprecated in the swagger spec.

@dilipkrish just curious, when the https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#operationObject can have a deprecated field. Why isn't the spec contain one for the https://github.com/swagger-api/swagger-spec/blob/master/versions/2.0.md#schemaObject ?. Is it something which I need file for a bug with the swagger-spec?


[Backport] Remove stray reference to fix OOM while merging sketches (#13475)

Backports https://github.com/apache/druid/pull/13475

https://github.com/apache/druid/pull/13475#issuecomment-1341856200

LGTM


How can we avoid vite config ssl secret ending up on github

Thanks for the post and git repo for doing this.
https://github.com/AlexJPotter/.NET-6-and-Vue-3-sample-app/blob/e8004b405b14278502fcbaba64f8e09cfd020ceb/ClientApp/vite.config.ts#L12
The above line seems to be there because of SSL setup for Vite.
Can we not put this in another file and load from there in vite config and ignore that file so each dev in team can have their own secret exported from sslsecret.ts file or something.  If you have solved it already in different way please share.

Hi @mfsbo - you are free to choose your own passphrase for the exported .pfx file and store that in a separate file or environment variable. The certificate is only a developer certificate for localhost, so the tangible risk is very low, but there's no reason why you can't make it more secure if you have specific security concerns.
A reminder that a full walkthrough of how the repo was put together can be found on my blog:
https://alexpotter.dev/net-6-with-vue-3/


Don't store events without user_message_id

Currently, if Junebug gets sent an event by the transport, but the user_message_id of the event is null, the event processing crashes and gets stuck. We should just log that the event doesn't have a message id, don't store it, and carry on.

Ready for review.

:+1:


Fix bug ReferenceError when using Groovy and use JSyntaxtTextArea ins…

…tead of JEditor
This PR fixes the bug reported on google group.
Sampler has possibility to select an alternative to javascript, but when you select Groovy
an error occurs when selecting another element and then select WDS again, see attached screenshot.
Issue was due to DefaultSyntaxKit.initKit().
So I switched to the JSyntaxtTextArea component which is anyway more uniform.
Note that it would be nice to drop 2.13 support which would allow using JMeter core JSyntaxTextArea#getInstance() which will handle correctly the new Darcula LAF.
Regards
Philippe M. from UbikLoadPack Team

Please review unit test failures

Hi @undera,
Are you sure there are test failures on this one?
Or so you mean codacy which I fixed except for visibility for unit tests.
Thanks

There are NPEs in Travis log seen...

Thanks for contributing!

Hi @undera,
Any release of plugins expected soon for webdriver and jmeter plugins manager ?
Thanks

It's easier with webdriver plugin, we can release it independently.
With Plugins Manager it is harder, since it is central part of infrastructure and we prefer to release it more rarely.
I'm on 2 week business trip anyway, so can't commit to anything right now.

Hi @undera,
Regarding webdriver you should have a look at rultor, it’s very nice to release with it.
For jmeter-plugins-manager, What infrastructure is concerned ? The reported bug is really nasty as whenever network is slow, you end up having a freezed jmeter and need to kill it.
Regards

It's really more about me being busy, I'm in the middle of flights... I'll take a look once I have some time.


[ETFE-1588] add ChooseShortageExcessItem page

[ETFE-1591] Adding the Item-Amount page.
[ETFE-1591] Add scoverageOff to views and correct name of model
[ETFE-1588] WIP choose-shortage-excess-item
[ETFE-1588] added ChooseShortageExcessItem page

Changing to draft as I've noticed a couple of inconsistencies between the prototype/copydeck/ticket which I want ironing out before it's merged. Will reopen once they're sorted out


MMD: PyDictKeyEntry not found on 2.7

Mixed-mode debugging is broken on Python 2.7, because it tries to load missing type PyDictKeyEntry (it exists in 2.7, but is called PyDictEntry).

This is a regression from 3.6 dict updates.


getColValues optimisation from @rimace

Remove unnecessary loop in getColValues method on TableFilter (#481)
Make gh-publish replace the distribution files (remove and all files)

Codecov Report

Merging #482 into master will decrease coverage by <.01%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #482      +/-   ##
==========================================
- Coverage   87.54%   87.54%   -0.01%
==========================================
  Files          38       38
  Lines        4393     4391       -2
  Branches      333      336       +3
==========================================
- Hits         3846     3844       -2
  Misses        526      526
  Partials       21       21

Impacted Files
Coverage Δ

src/tablefilter.js
91.83% <100%> (-0.02%)
:arrow_down:

Continue to review full report at Codecov.

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


Only show Edit project button/screen if user has edit permission for project

Via https://github.com/fastlane/ci/blob/master/docs/use_cases/access_project_details.md

Moved to V1, let me know if you feel like we should do it for Beta


Replace deprecated FILTER_SANITIZE_STRING

PHP 8.1 deprecates FILTER_SANITIZE_STRING and recommends htmlspecialchars() instead, however in this case we are not filtering for XSS.
I've replaced the filter to instead strip characters outside the allowed ASCII range. This is documented in the specs here: https://openid.net/specs/openid-authentication-2_0.html#positive_assertions
An example nonce returned by steam:
2024-10-08T22:41:16ZT4LvYmNS5X//lKaQyJtqT4i0a44=

thank you stranger!!


Fix Android crashes

This fixes two Android crashes.
The first crash is caused by a race condition in barcode scanner mode.  When onPreviewFrame() is called, which happens multiple times per second, it fires off an async task which calls getParameters() on the Camera object.  There is always a delay between onPreviewFrame() and the async task; usually it's a millisecond or less, but I've seen it go as high as 800 milliseconds.  If the Camera object is released in that delay window (e.g. if the user pauses the app), the call to getParameters() will throw an exception that crashes the app.  The fix for this is to simply catch and ignore that exception.
The second crash is similar, being caused by a call to getParameters() on a released, or possible null, Camera object.  This one happens if the Camera has been released but the viewfinder is still active; for example, when switching between front and back cameras.  If the user then initiates a touch event in the viewfinder, an exception will be thrown that crashes the app.  Again, the fix is to catch and ignore that exception.
(The change in startCamera() was not actually required for either fix, but was made simply for completeness and consistency.)

This seems to fix the crash, but breaks the barcode scanning

@burgalon, what specifically is breaking for you?  We've been using this commit in our RN app, which relies heavily on barcode scanning, for several weeks with no issues.

Yes, we have same crash with getParameters.

@Fweeper for some reason the barcode scan callback didn't trigger

@burgalon could you supply a code example in which the barcode scanning does not work?  Here is an example that is working just fine for me:
<RNCamera
	style={{ flex: 1 }}
	barCodeTypes={[ 'org.iso.DataMatrix' ]}
	onBarCodeRead={ (e) => console.log(e.data) }
/>


add publish workflows

The 0.2 service crates were published using revisions of these workflows.  This makes it possible to check all the services in parallel jobs. The workflow definitions can be generated when the services are updated.

I was hoping it would publish 1 job at a time. Looks like it is doing 20 concurrently. :/
https://docs.github.com/en/actions/learn-github-actions/usage-limits-billing-and-administration

crates.io had to problem with the concurrent crate updates. The backoff appears that it was just for new crates. docs.rs put the azure_mgmt crates in a "priority: -1, so they get processed when capacity is available. It may take a few days. https://docs.rs/releases/queue

Given these have access to CARG_REGISTRY_TOKEN, this should probably include documentation as to who has access to run these and what the process is to enable giving someone access to run these.

The publish actions are intended for running in your own fork where only you have access to run the actions.  Do not add the CARGO_REGISTRY_TOKEN to the main repository.  Only add it to your repository.
How is that ^^^?

Discussion moved to the internal Teams instance for Azure SDK For Rust.


How to install this under Linux

Only a Windows .exe file is released.
Please consider adding instructions to install this on a Linux machine running a Debian variant.

Currently it is difficult to create a Linux version as we are busy implementing other features.
I will create a Linux version when I have time.

When I create a Linux version, I will let you know here.


Clean up the "Getting Started with GitHub" landing page

Currently this page: https://foundations.projectpythia.org/foundations/getting-started-github.html
still says "under construction".

This is the last piece of business to fix up before we do a thorough review in #214.
I'll try to put something together today.


Adding Retries to node and pod actions

To fix: https://github.com/powerfulseal/powerfulseal/issues/295
This will add in retries based on count or a timeout to both pod and node actions.  This is an optional addition to the schema

Hey @paigerube14 thanks for the PR! I left a few comments, let me know what you think.


[FileAccess] Add method to abort backup save without overwriting original file, fail editor save operations on write errors.

Adds abort_backup_save_and_close method to close and delete temporary file without overwriting original file (when OS.set_use_file_access_save_and_swap is enabled).
Fail various editor save operations on write errors, and use aforementioned method to ensure original file is not overwritten.

TODO:

[x] Apply to all save operations.

Apply to all save operations.

I was going to ask if it shouldn't make more sense to unset the save_path variable on any write error, i.e. inside FileAccess::store_buffer et al. but looks like that's the plan already?

was going to ask if it shouldn't make more sense to unset the save_path variable on any write error, i.e. inside FileAccess::store_buffer et al. but looks like that's the plan already?

While it can be unset in store_buffer, and this will prevent overwriting the original file, I prefer to do it where store_* is called, since it additionally allows producing more meaningful errors and cancel more complex operations on write error, checking results of store_* should be done anyway. Also, not every case should be fully aborted, for something like logs it's better to have it partially written then not written at all.

Gotcha.
A footnote on write error handling: When dealing with raw file write errors (i.e. not compressed, not encrypted writes), errors are often delayed and the underlying API (including std's FILE o fstream) lie. This is because of the highly async nature of IO.
Imagine the following:

write 32 bytes - returns success.
The underlying OS or disk encounters an error.
write 16 bytes - returns failure. However this failure is actually from step 1.

Flushing the descriptor (fflush) can help. However there are many types of failures:

File / folder removed. Highly depends on the OS. Probably detected after fflush. Most likely to be spotted when opening the file (due to how most file systems work) rather than on write().
Underlying API is out of RAM. IO is probably the least of your problems. Probably the process crashes before the error is successfully reported to the user.
Disk removed. E.g. USB cable got yanked out, network share went down, etc.
Out of Space - probably detected after fflush, as the usually OS knows this (it may not due to the parallel nature of IO).
Bus error - It may not be detected in time, as the OS delays the writeout to disk until it has enough data (or the OS is very far behind because the disk write speed cannot keep up with all the data piled up).
Disk Controller error - probably detected much later, as the disk also async returns "everything ok" to the OS but later on reports a physical error. This error may not even be detected at all by the process (e.g. fclose() returned everything ok).
In theory full disk sync ensures fully synchronous & accurate error reporting; but that also depends on the drive's firmware. Also full sync on network shares is practically impossible (e.g. Samba / NFS may return "everything ok" but that computer has its own caches to flush).

Flushing excessively is bad for throughput performance and it still doesn't guarantee the error is spotted.
Plus 99.99% of the time it doesn't matter; because what really matters is whether the whole file was written successfully or not. It doesn't matter if the first 10 bytes succeeded but the next 4 bytes did not. There are exceptions such as torrent SW which downloads large data in chunks; backup SW also does care about which bytes are OK. But the general case only cares about the whole file succeeding.
And in almost all cases, the reasons for failure are extremely bad (either out of space which can be really bad if it's the system drive, or a serious HW error).
This is not a comment saying what you're doing is futile: I'm just pointing out that you need to have clear what's the goal with the error checks and how obsessive & paranoid you want it to be, and be aware of the issues with IO writes when the code is running in the real world.
Compressed or Encrypted files is a different issue, since there can be a myriad of other errors (it's much more common to run out of RAM, there can be bugs in the encoding process, unsupported data patterns, wrong settings, etc)


Fix components composition

There were a few problems of components separation in https://github.com/browserslist/browsersl.ist/pull/482

Form_messages was styles in one component, but JS was added in another
Alert knew too many things about Form. For instance, alert works with form’s textarea directly.

This PR split logic between component in a more gentle way. Yes, we have a problem with huge Form component.
I also changed error color, so it is more red-ish and closer to warning’s yellow in terms of chroma.

I also changed error color, so it is more red-ish and closer to warning’s yellow in terms of chroma.

I like it better too.

Thank you for making corrections.

I agree that onFormSubmit and textarea made it harder to read.


[AvatarGroup] Improve limit display

Display extra avatar if only one left (instead of showing the +1, let's just show the last avatar)

[x] I have followed (at least) the PR section of the contributing guide.

@let-aurn This sounds smart, thanks for raising the idea. Atlaskit has the same tradeoff: https://codesandbox.io/s/lucid-lehmann-b8wik?file=/src/App.js:0-171.

@let-aurn I have updated the demo to better illustrate the behavior. If you could add unit tests to ensure the logic is correct, it would be perfect. I believe the index change I did was required.

@oliviertassinari, I can't make your version working
const extraAvatars = children.length > max ? children.length - max + 1 : 0
//                                                                   👆

IMO The +1 should be in the comparison
children.length + 1 > max ? (...) : (...)

So, PR updated.
I suggest you start by reading the tests AvatarGroup/AvatarGroup.test.js before reading the actual change.


ENH: Dask integration

It would be good to have dask integration with EventStreams

See https://github.com/mrocklin/streams/pull/37 for the streams discussion

This may be tricky to implement. We store a fair amount of state in our objects so we can pass important information around (uids, mostly). We would need to make certain that that data was passed to the dask tasks appropriately.
This may be possible so long as we scatter the data to the cluster properly.
One way that this may work is by running start, descriptor, and stop locally and creating the needed UIDs. The event data processing (and potentially issuing) will be handled on the cluster as they are generally in parallel (or can be handled in the scheduler).
One potential problem is that the Future objects don't really follow the ('name', dict) system that we have. We may need to monkey patch the Future objects to have a name attribute for us to look at.

It may be possible for us to run a gather upon getting a stop document and pull all the information in and emitting all the event documents.

This is solved by streamz


Errors in running in localhost but not in cloud

Hi, I tried using this in Replit, it worked perfectly. But when I try to use in my localhost it is giving error. I need this really important
Here is the error:
cause: Error: read ECONNRESET
at TLSWrap.onStreamRead (node:internal/stream_base_commons:217:20) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'
}
Kind Regards,

@junhoyeo
In VPS it is working perfectly fine. But when I try to run in localhost host it throws the error


vue-js-cron/light crashes for Vue 2

After installing the<EMAIL_ADDRESS>and initializing it, app crashes.
Error:
Module not found: Error: Can't resolve '@vue-js-cron/core/src/fields/multiple' in 'C:\Users\user\Desktop\vue-js-cron-test\node_modules\@vue-js-cron\light\dist'

Thank you for reporting this issue.
solved by: d4f432d34fddf26164c9d8b155ce25d03e202af4
<EMAIL_ADDRESS>should work.


Requires reauthentication after every deployment

I am using proxy to authenticate with my Amazon account.
However, every time I do a deploy (even after the most trivial change), it loses connection and requires manual re-authentication.
I tried setting a 'File Path' to save the cookies but no matter what path I use, I get an error of form "Port 3456 already in use"
I am running node-red as a HACS add-on to Home Assistant on a RPi5.
I have tried  file paths such as /opt/file_name and /config/file_name and others.
The "Port 3456" message appears even though netstat and lsof seem to show that there is only one process running.
So,

Why is (manual) re-authentication required after each deployment?
What do I need to do to set a valid cookie path that doesn't create a "Port 3456 already in use" error

Never mind.
It seems like the problem is that I had imported someone else's code and thus had 2 accounts which I suppose conflicted...


Support any type of token (erc20, erc721, erc1155)

Now supports any type of tokens (ERC20, ERC721, ERC1155)! Just replace the contract address in yourDetails.js file.

Could you give the readme a quick update? I'll also change the name of this template to token-gated-website

On it!


List nodes

PR for #606
first real pull so hopefully everything is in order

I tested it in devhaas and it looks fine, so +1.

is everyone cool with this now?

This works. merging and closing it.


#1934 Project Navigator does not show external updates to files and folders

Description
Fixed issues relating to project navigator; Project Navigator UI now responds to external filesystem updates (i.e. add file button now adds file to view, anything done to files in finder will update in view)
Related Issues

#1934

Checklist

[x] I read and understood the contributing guide as well as the code of conduct
[x] The issues this PR addresses are related to each other
[x] My changes generate no new warnings
[x] My code builds and runs on my machine
[x] My changes are all related to the related issue above
[x] I documented my code

Screenshots
https://github.com/user-attachments/assets/8371d620-6971-44b4-8f3e-76751832bead
Internal Filesystem Updates
https://github.com/user-attachments/assets/b56b5b46-f584-4b85-be14-db5fa0f2f91c
External Filesystem Updates

@songemma Thank you for fixing this! I wonder if there is a bigger issue here though. In #1826 we see that when files are updated externally, the contents on their corresponding open editor in CodeEdit do not get updated in response.
After discussing this with other maintainers, we believe this is a result of an underlying issue where some updates are not making their way to the UI. You are welcome to dig into this further if you'd care to, otherwise please let us know and we can later on.


tests: Move storage helpers from utils

What this PR does
Move storage helpers from utils to the storage tests using them.

Fixes #
Why we need it and why it was done in this way
The following tradeoffs were made:
The following alternatives were considered:
Links to places where the discussion took place:
Special notes for your reviewer

Checklist
This checklist is not enforcing, but it's a reminder of items that could be relevant to every PR.
Approvers are expected to review this list.

[ ] Design: A design document was considered and is present (link) or not required
[ ] PR: The PR description is expressive enough and will help future contributors
[ ] Code: Write code that humans can understand and Keep it simple
[ ] Refactor: You have left the code cleaner than you found it (Boy Scout Rule)
[ ] Upgrade: Impact of this change on upgrade flows was considered and addressed if required
[ ] Testing: New code requires new unit tests. New features and bug fixes require at least on e2e test
[ ] Documentation: A user-guide update was considered and is present (link) or not required. You want a user-guide update if it's a user facing feature / API change.
[ ] Community: Announcement to kubevirt-dev was considered

Release note

NONE

/approve

:stop_sign: please refrain from manual retesting.
:warning: this PR is being held to stop automatic retesting. Quarantine PR https://github.com/kubevirt/kubevirt/pull/11244 is given priority.
/hold

:warning: removing hold since https://github.com/kubevirt/kubevirt/pull/11244 got merged.
/unhold


kdeconnect: [WIP/RFC] let dbus activate via systemd

Motivation for this change
This is proof of concept and VERY much open to comments.
The next version of systemd will give us the standard targets for launching the entire graphical session using systemd, but we can (and I have here) been taking advantage of having dbus launch dbus activated services via systemd instead of doing it directly.
 Since it triggers systemd to spawn the service, they are not direct children of dbus and thus survive the dbus process dying.
Auto-spawn if they get killed - I used this a lot when xembedsniproxy was in early stages and quite crashy.
Resource management for something like "baloo" where it is very nice to be able to down prioritize both CPU and IO.

In order to have dbus spawn the processes via systemd, we need to make the following changes:

the dbus service file for each service needs to be augmented with "systemdservice=name-of-service.service"
create a service file each service
create an alias for the dbus activatable service

Item 3 is technically not necessary, but simply to play nice with how other distributions are doing it.
This PR implements items 1 to 3 for kdeconnect in a very non-reusable and naive way, but as mentioned this is simply proof of concept.
I have used kdeconnect for this experiment as there is nothing else that depends on this, but I have tried with both kwallet and baloo here using the same approach and they work fine. They just require a rebuild of the entire KDE environment.
cc: @ttuegel @fridh @groxxda
Things done

[X] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[X] NixOS
[ ] OS X
[ ] Linux

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[X] Tested execution of all binary files (usually in ./result/bin/)
[X] Fits CONTRIBUTING.md.

I forgot to add, that in order to actually activate the configuration on nixos, you need the following:
{
services.dbus.packages = with pkgs; [ kdeconnect ];
systemd.packages = with pkgs; [ kdeconnect ];
}

I don't know kdeconnect, so pardon my ignorance: Is it really meant as system wide service? I thought the work on systemd to enable graphical-session is merely about user sessions.
Thanks for your work on dbus activation and this poc :+1:.
What are the next steps?

Create a module for kdeconnect and move the systemd and dbus units there (would be even better if upstream shipped those files and we could just pick them up. The aliasing still needs to be done manually though.

kdeconnectd is a user session service - this PR only deals with user sessions services.
But you are absolutely right, upstream should be shipping all of this (they are shipping the dbus files but without the crucial SystemdService part).
The way I understand it is where KDE wants to go, but haven't yet (gnome has afaik already started).
We can however start slowly now. What I propose to do:

abstract my ugly hard-coded "solution" unto a proper derivation under build-support
use the abstracted function in the postInstall phase for kdeconnectd
if that works properly, convert other non-critical user services to this one at a time

Of course, one can also argue that this is not worth the effect as we simply need to wait for upstream but as I see this as a nix learning experience, I don't mind doing the work.

This sounds good to me! It would be a nice abstraction to have.

we also now better integration of systemd user applications requiring x11: https://github.com/NixOS/nixpkgs/pull/26094

What is the status of this pull request?

This needs to either:

Be generalized so we can easily the same patches to others, or
We simply wait for upstream

In the mean time, this is working fine.

So yeah, 4 years later - I'll get to this any time now....

I'm going to close this and just wait for upstream to get proper support. It's otherwise a lot of work on our side.


Enhancement to prevent cargo from recompiling allowlisted dependencies.

Issue
We are facing the following problem today when using allowlisted dependencies.
We understand that all the dependency crates of pgrx (and those of the allowlisted crates) need to be compiled on cold start and that's a fixed cost. Suppose we have a fixed list of allowlisted crates, we want to prevent cargo from re-compiling any dependencies on consecutive build of plrust functions.
The way PL/Rust works today is that it adds crates into the Cargo.toml  [dependencies] section based on what is specified in the  [dependencies] section of the function definition. I believe we could suffer from the feature unification problem in certain cases.
For example, given crateA , crateB as allowlisted crates, and assume they both depends on crateC but crateA requires featureX in crateC and crateB requires featureY in crateC.
If we first create a function with just using crateA, the Rust fingerprint of crateC would say featureX is enabled. However, if we then create a function with just crateB, then the existing rlib for crateC cannot be re-used because now crateC needs to have featureY enabled which is not the case here. Similarly, if it is followed by creating a function which uses both crateA and crateB, the existing 2 version of rlib for crateC would not be compatible, and again needs to be recompiled because we need a crateC to to have both featureX and featureY enabled.
Proposal
The proposal i have is to use the same dependency set in Cargo.toml for every new function creates when allowlisted dependencies is a non-empty set.
E.g. Suppose the allowlist looks like this
CrateA = { version = "1.0", features = [ "featureX", "featureY" ] }
CrateB = "2.0"

When user request to create a function which uses dependencies with the above allowlist, plrust still checks if the requested dependencies are allowed. But when plrust creates the crate for it, we always use the same value for "dependencies" in Cargo.toml
CrateA = { version = "1.0", features = [ "featureX", "featureY" ] }
CrateB = "2.0"

I believe this is also how Rust playground manage to avoid rebuilding any dependencies with its top 100 crates that are supported by it.

@anth0nyleung This is an interesting problem!
The slight problem is that sometimes a crate has multiple features, like... oh... notorious crate pgrx... that has "non-additive features". The reason the resolver has moved to a slightly different logic of how it splits up crates and does multiple compilations of them is partly that it was simply too eager in cases where unification is never useful, but also that if they are incorrectly unified, two sets of crate features can cause this sort of thing to be reached:
https://github.com/rhaiscript/rhai/blob/6d6390dee1e7d8f66ce27340246a0e02905795e1/src/lib.rs#L461-L463
Otherwise it is fairly eager to unify crate features, but this can cause other problems even if we don't hit compile errors, as enabling features can subtly change the behavior of a crate!
I suppose we could have this as a configurable option? There are some allowlists for which following this proposal will Basically Always Be Okay. There are others which it would not be. We'd have to rely on the admin being thoughtful about that.

That's interesting.
The biggest problem im trying to avoid is re-building pgrx-pg-sys which is a very costly operation. It's very undesirable when this kind of unification problem happen because of say we support the serde crate that yields a different set of unified feature and at the end result in re-building pgrx-pg-sys. To make it worse, it takes quite some effort and time to find out what is causing the rebuild if it happens. I feel like there is a general lack of useful tools to debug this kind of issue.
I think making it configurable makes sense since this falls into the bucket of a nice-to-have feature. We will also make it clear in the documentation that this does not guarantee to completely avoid such problem but in most cases it should work like you said.

Hm. If the primary issue is pgrx-pg-sys, one of the things we can do is pay close attention to the features used by pgrx-pg-sys and its dependencies a bit more, so that it is more cagey about unifying them. I would be happy to review this feature but I would prefer a first-pass on the cargo tree there.
$ cargo tree -p pgrx-pg-sys
pgrx-pg-sys v0.12.0-alpha.1 (~/pgrx/pgrx-pg-sys)
├── libc v0.2.152
├── memoffset v0.9.0
│   [build-dependencies]
│   └── autocfg v1.1.0
├── pgrx-macros v0.12.0-alpha.1 (proc-macro) (~/pgrx/pgrx-macros)
│   ├── pgrx-sql-entity-graph v0.12.0-alpha.1 (~/pgrx/pgrx-sql-entity-graph)
│   │   ├── convert_case v0.6.0
│   │   │   └── unicode-segmentation v1.10.1
│   │   ├── eyre v0.6.11
│   │   │   ├── indenter v0.3.3
│   │   │   └── once_cell v1.19.0
│   │   ├── petgraph v0.6.4
│   │   │   ├── fixedbitset v0.4.2
│   │   │   └── indexmap v2.1.0
│   │   │       ├── equivalent v1.0.1
│   │   │       └── hashbrown v0.14.3
│   │   ├── proc-macro2 v1.0.78
│   │   │   └── unicode-ident v1.0.12
│   │   ├── quote v1.0.35
│   │   │   └── proc-macro2 v1.0.78 (*)
│   │   ├── syn v2.0.52
│   │   │   ├── proc-macro2 v1.0.78 (*)
│   │   │   ├── quote v1.0.35 (*)
│   │   │   └── unicode-ident v1.0.12
│   │   ├── thiserror v1.0.56
│   │   │   └── thiserror-impl v1.0.56 (proc-macro)
│   │   │       ├── proc-macro2 v1.0.78 (*)
│   │   │       ├── quote v1.0.35 (*)
│   │   │       └── syn v2.0.52 (*)
│   │   └── unescape v0.1.0
│   ├── proc-macro2 v1.0.78 (*)
│   ├── quote v1.0.35 (*)
│   └── syn v2.0.52 (*)
├── pgrx-sql-entity-graph v0.12.0-alpha.1 (~/pgrx/pgrx-sql-entity-graph) (*)
├── serde v1.0.197
│   └── serde_derive v1.0.197 (proc-macro)
│       ├── proc-macro2 v1.0.78 (*)
│       ├── quote v1.0.35 (*)
│       └── syn v2.0.52 (*)
└── sptr v0.3.2
[build-dependencies]
├── bindgen v0.69.4
│   ├── bitflags v2.4.2
│   ├── cexpr v0.6.0
│   │   └── nom v7.1.3
│   │       ├── memchr v2.7.1
│   │       └── minimal-lexical v0.2.1
│   ├── clang-sys v1.7.0
│   │   ├── glob v0.3.1
│   │   ├── libc v0.2.152
│   │   └── libloading v0.8.1
│   │       └── cfg-if v1.0.0
│   │   [build-dependencies]
│   │   └── glob v0.3.1
│   ├── itertools v0.12.1
│   │   └── either v1.9.0
│   ├── lazy_static v1.4.0
│   ├── lazycell v1.3.0
│   ├── proc-macro2 v1.0.78 (*)
│   ├── quote v1.0.35 (*)
│   ├── regex v1.10.3
│   │   ├── regex-automata v0.4.5
│   │   │   └── regex-syntax v0.8.2
│   │   └── regex-syntax v0.8.2
│   ├── rustc-hash v1.1.0
│   ├── shlex v1.3.0
│   └── syn v2.0.52 (*)
├── clang-sys v1.7.0 (*)
├── eyre v0.6.11 (*)
├── pgrx-pg-config v0.12.0-alpha.1 (~/pgrx/pgrx-pg-config)
│   ├── cargo_toml v0.19.1
│   │   ├── serde v1.0.197 (*)
│   │   └── toml v0.8.10
│   │       ├── serde v1.0.197 (*)
│   │       ├── serde_spanned v0.6.5
│   │       │   └── serde v1.0.197 (*)
│   │       ├── toml_datetime v0.6.5
│   │       │   └── serde v1.0.197 (*)
│   │       └── toml_edit v0.22.6
│   │           ├── indexmap v2.1.0 (*)
│   │           ├── serde v1.0.197 (*)
│   │           ├── serde_spanned v0.6.5 (*)
│   │           ├── toml_datetime v0.6.5 (*)
│   │           └── winnow v0.6.5
│   ├── eyre v0.6.11 (*)
│   ├── home v0.5.9
│   ├── owo-colors v3.5.0
│   ├── pathsearch v0.2.0
│   │   ├── anyhow v1.0.79
│   │   └── libc v0.2.152
│   ├── serde v1.0.197 (*)
│   ├── serde_derive v1.0.197 (proc-macro) (*)
│   ├── serde_json v1.0.112
│   │   ├── itoa v1.0.10
│   │   ├── ryu v1.0.16
│   │   └── serde v1.0.197 (*)
│   ├── thiserror v1.0.56 (*)
│   ├── toml v0.8.10 (*)
│   └── url v2.5.0
│       ├── form_urlencoded v1.2.1
│       │   └── percent-encoding v2.3.1
│       ├── idna v0.5.0
│       │   ├── unicode-bidi v0.3.15
│       │   └── unicode-normalization v0.1.22
│       │       └── tinyvec v1.6.0
│       │           └── tinyvec_macros v0.1.1
│       └── percent-encoding v2.3.1
├── proc-macro2 v1.0.78 (*)
├── quote v1.0.35 (*)
├── shlex v1.3.0
├── syn v2.0.52 (*)
└── walkdir v2.4.0
    └── same-file v1.0.6

@anth0nyleung Can you relate any examples on what features appearing in dependency sets are triggering pgrx-pg-sys rebuilds, specifically?

@workingjubilee - sorry it took me a while to get back to you
I think our goal is to avoid any dependencies rebuilds, not specifically to pgrx-pg-sys, but we would really like pgrx-pg-sys to not ever rebuild (unless we upgrade it to a new version)
One example i can give is the rand crate.
When rand crate is used in a function. The crate getrandom enables the std feature.
(24-03-20 2:23:59) <0> [~/plrust-crate]
~/plrust-crate $ cat with-rand | grep getrandom
│           │   │   │   └── getrandom feature "default"
│           │   │   │       └── getrandom v0.2.12
    │   │           └── getrandom feature "default" (*)
    │   ├── rand feature "getrandom"
    │   │   └── rand_core feature "getrandom"
    │       ├── getrandom feature "std"
    │       │   └── getrandom v0.2.12 (*)
    │       └── rand_core feature "getrandom" (*)

However, plrust-trusted-pgrx also depends on getrandom, but the getrandom crate in this case only enables the default feature, which does not include std.
(24-03-20 2:26:03) <0> [~/plrust-crate]
~/plrust-crate $ cat only-plrust-trusted-pgrx | grep getrandom
            │   │   │   └── getrandom feature "default"
            │   │   │       └── getrandom v0.2.12

In this case, suppose i have a function that was created without using rand. Now the fingerprint of getrandom does not have std. But when rand is used as dependencies in a new function, it'll case a rebuild on these dependencies
Compiling getrandom v0.2.12
Compiling uuid v1.8.0
Compiling pgrx v0.11.0
Compiling plrust-trusted-pgrx v1.2.7
...

When this happens on a host with limited CPU, this can make a huge differences. We observed that a function can take close to 3 mins to compile when this rebuild happens, as opposed to just 5 seconds.

Hmm. I wonder how https://github.com/pgcentralfoundation/pgrx/pull/1616 will affect the build times of PL/Rust functions.

That looks like a pretty nice improvement. Looks like plrust 1.2.8 is still on pgrx 0.11.0. Can it work with 0.11.3 or develop branch of pgrx? I can try testing it. In the past my experience of compiling a PL/Rust function in the worst case is 45 hours... This is caused by pgrx-pg-sys, wondering how much improvement that change can bring


No CMAKE_CXX_COMPILER could be found.

I've a problem while trying to run/build my flutter app on windows.
It has stopped working from nonwhere
I've tried to change the channel, upgrade flutter, create new project and drop the lib folder into it but nothing make it works.
http://prntscr.com/w60piy
Flutter doctor

flutter doctor -v
[√] Flutter (Channel dev, 1.26.0-1.0.pre, on Microsoft Windows [versÃ£o 10.0.19041.685], locale pt-BR)
    • Flutter version 1.26.0-1.0.pre at D:\Programs\flutter
    • Framework revision 63062a6443 (6 days ago), 2020-12-13 23:19:13 +0800
    • Engine revision 4797b06652
    • Dart version 2.12.0 (build 2.12.0-141.0.dev)

[√] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at D:\Programs\AndroidSDK
    • Platform android-30, build-tools 30.0.0
    • Java binary at: D:\Programs\Android\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Chrome - develop for the web
    • Chrome at C:\Program Files (x86)\Google\Chrome\Application\chrome.exe

[!] Visual Studio - develop for Windows (Visual Studio Community 2019 16.7.4)
    • Visual Studio at D:\Programs\VisualStudio\VisualStudio
    • Visual Studio Community 2019 version 16.7.30517.126
    ! Unable to locate a Windows 10 SDK. If building fails, install the Windows 10 SDK in Visual Studio.

[√] Android Studio (version 4.0)
    • Android Studio at D:\Programs\Android
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code (version 1.52.1)
    • VS Code at C:\Users\Gustavo\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 3.17.0

[√] Connected device (3 available)
    • Windows (desktop) • windows • windows-x64    • Microsoft Windows [versÃ£o 10.0.19041.685]
    • Chrome (web)      • chrome  • web-javascript • Google Chrome 87.0.4280.88
    • Edge (web)        • edge    • web-javascript • Microsoft Edge 87.0.664.60

Hi @GustavoRolimSantos
Looks like you've incomplete Visual Studio setup
[!] Visual Studio - develop for Windows (Visual Studio Community 2019 16.7.4)
    • Visual Studio at D:\Programs\VisualStudio\VisualStudio
    • Visual Studio Community 2019 version 16.7.30517.126
    ! Unable to locate a Windows 10 SDK. If building fails, install the Windows 10 SDK in Visual Studio.

Make sure you have the following components installed in your Visual Studio Installer,  Search Visual Studio Installer in your start menu.

Thank you

I've it installed :/

I've reinstalled the Windows 10 SDK and it worked. Thanks


Dynamic local filtering?

Hi,
Very interesting work! I have some problems about dynamic local filtering.
Line 23 in resnet_dilate.py. In my understanding, shift with different dilation rates (e.g., 1) should only operate on the depth feature. However, in this code, it seems that both the pad_depth and pad_x have the same shift step size. If so, it may be more like direct element-wise product between pad_depth and pad_x. Is there something wrong with my understanding?
Actually, this is a very thoughful idea about depth-guided conv.

Hi,
Thanks.

To achieve local conv, we perform element-wise product before the shift. There maybe some misleads  in our Figure.

It should be if not (i==0 and j==0), which means i != 0 or j !=0.

Regards,
Mingyu

On Jun 2, 2020, at 15:21, CVer<EMAIL_ADDRESS>wrote:

Hi,
Very interesting work! I have some problems about dynamic local filtering.
Line 23 in resnet_dilate.py. In my understanding, shift with different dilation rates (e.g., 1) should only operate on the depth feature. However, in this code, it seems that both the pad_depth and pad_x have the same shift step size. If so, it may be more like direct element-wise product between pad_depth and pad_x. Is there something wrong with my understanding?
Line 22 in the same file, maybe it should be if i != 0 and j != 0?
Actually, this is a very thoughful idea about depth-guided conv.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


uildFHSUserEnv: symlink /etc/nix

Motivation for this change
this fixes experimental-features option not being available in fhs
and breaking the flakes feature
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[ ] Fits CONTRIBUTING.md.

Please change the commit and PR title to include a b in the beginning.


Plugin does not load on intellij 2016.1.2

In \src\main\java\com\appian\intellij\k\KIcons.java, it references a path for the icon.  When plugin is loaded into intelliJ and you click on file types, you get an error - could not load class com.appian.intellij.k.KIcons.java.
I had to update it to be:
``
from: IconLoader.getIcon("/com/appian/intellij/k/k.png");
to :    IconLoader.getIcon("icon.png");
``
Also made resources marked as resources root

@mittonsimon sorry, I just saw this. It should be fixed now. Thanks!


Fix issue where errors would be logged when the /health endpoint was called (#1281).

Fixes #1281
Perhaps we have this issue in other cowboy_rest endpoints as well - I'll investigate.

Ill check from the computer later, seems like the error happens due to the
content type, request was made with html content type and this responds to
json only.
On Wed, Aug 7, 2019, 04:36 Lars Hesel Christensen<EMAIL_ADDRESS>wrote:

@larshesel https://github.com/larshesel requested your review on: #1283
https://github.com/vernemq/vernemq/pull/1283 Fix issue where errors
would be logged when the /health endpoint was called (#1281
https://github.com/vernemq/vernemq/issues/1281)..
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/vernemq/vernemq/pull/1283?email_source=notifications&email_token=AABJD6GUOGZGTIYZOWGDCVTQDKCRFA5CNFSM4IJ5ZPF2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOS5M6MYA#event-2539251296,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AABJD6C447YBL5HWLF4OMCLQDKCRFANCNFSM4IJ5ZPFQ
.

Ill check from the computer later, seems like the error happens due to the content type, request was made with html content type and this responds to json only.

I'm not so sure - the issue says that the body was correctly returned, but afterwards there's an error/crash logged.

Weirdly, the issue happens only when calling the endpoint from a browser. Neither "curl --header "Content-Type: application/json" http://localhost:8888/health" or "curl http://localhost:8888/health" cause the issue.

Hi, thank you for looking into this. I came to this bug as i was reviewing the clustered setup. The loadbalancer checks the /health URL and i so many many of these errors caused by the probe, every 5 seconds.
So yes, i’m getting the issue by browser requests, but main concern is the LB probes, as the error logs would grow over time significantly.
Thank you

curl http://localhost:8888/health

I can reproduce it every time with both the curl --header "Content-Type: application/json" http://localhost:8888/health and curl http://localhost:8888/health.
I think we'll merge this fix for now.

Sounds good


Support AppCDS to improve startup time of test resource server

This PR allows the server to be optimised with AppCDS
Unfortunately due to issues with the server we have to limited the classes in the class list when creating the archive, but this doesn't seem to impact startup time.

Most of this should really belong to https://github.com/micronaut-projects/micronaut-test-resources/tree/master/test-resources-build-tools

yeah it is a draft to just get it working... Cedric will look when he is back from holiday

FWIW it cuts startup time for me from 650ms to 280ms

Most of this should really belong to https://github.com/micronaut-projects/micronaut-test-resources/tree/master/test-resources-build-tools

It's actually hard to make it part of the common code, since this belongs to the invocation logic: we're already in the build tool specific code.

Superceded by #508


R-T5.4-1: The data pipeline module of the Orchestrator must be able to orchestrate data pipelines

ID:
R-T5.4-1

Type:
FUNCTIONAL_SUITABILITY

User   story:
As an Operations Engineer, I want to be   able to deploy data pipelines and control their life-cycle using RADON   toolchain

Requirement:
The data pipeline module of the Orchestrator must be able to orchestrate data pipelines

Extended   Description:
Orchestrator  must provide support for orchestrating data   pipelines.

Priority:
Must have

Affected   Tools:
ORCHESTRATOR

Means   of Verification:
Evaluate whether the tool is able to   successully deploy data pipelines which have been defined using RADON models.

@cankarm , Can you please add "Data Pipeline" label to this issue?

The required basic templates, implementation file and other related files are ready and can be orchestrated with the RADON Orchestrator. A demo can be seen here. Please verify for approval @gcasale .

This unlikely to be the final version, if so the requirement needs to remain open.

All the requirements are fulfilled.
Some are waiting for approval (#18 , #19 , #21 , #22 ), some are approved to be closed (#50 , #17 , #20 ) and requirement #23 is closed.
This final issue can be closed if above-mentioned are approved. @gcasale

Approved


[Android] Nested ViewPagers with same orientation are not scrollable

Environment

React Native 0.63.4
Android 10
ViewPager 5.0.12

Description

In versions 3 and 4 of this library, it is possible to have one ViewPager inside another, with the same orientation, and either one can be scrolled depending on where the user swipes the screen.
In version 5, the inner ViewPager is not scrollable: swiping it scrolls the outer one.
This issue doesn't occur if the inner and outer ViewPagers have different orientations.
Reproducible Demo
Here is a fork demonstrating the bug in the example app (it's the "Nested ViewPagers Example" at the bottom):
https://github.com/brsaylor2/react-native-viewpager/tree/nested-demo
Here's the actual demo code, based on BasicViewPagerExample.tsx: https://github.com/brsaylor2/react-native-viewpager/blob/nested-demo/example/src/NestedViewPagersExample.tsx
Here's a version showing that the same thing works in v4:
https://github.com/brsaylor2/react-native-viewpager/tree/nested-demo-v4

same here... any workaround ?

I have the same problem. Is there any solution to fix it?

React Native 0.64
Android 10
ViewPager 5.1.3

@troZee Do you have any plans for this issue? This is the biggest reason for not using the new version. :-(

Hello, I got this bug too, using react-native-tab-view along with react-native-page-view 5.4.0, here is a snack repro link https://snack.expo.dev/Q6wjaGD99 I provided in a misplaced  issue here : https://github.com/satya164/react-native-tab-view/issues/1233 . This does not happen in v4

Is there any solution?

I tried to fix this issue: #423

This issue is fixed for me in the current version. Thanks, @NiuGuohui!

ViewPager2 doesn't support nested scrolling with same orientation but ViewPager does. That's why react-native-pager-view lost support in version 4.
The only reason that I can see to switch to ViewPager2 is to bring RTL (right-to-left) support. So, in the Navigation router I continue to use ViewPager for LTR and only use ViewPager2 for RTL. @NiuGuohui I thought you might be interested in seeing an alternative approach.


No limit for Standard?

Given that:

the intake rate limit is 1 MB/sec
Retention can be set up to 7 days

Does that mean that the maximum volume retention for the standard tier is around 590 GB per CU?

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

ID: b6d43eb3-6a80-b8c4-8536-f4f8b79aa453
Version Independent ID: 3e8dec68-44ac-aca8-5b07-470050878ae5
Content: Quotas and limits - Azure Event Hubs - Azure Event Hubs
Content Source: articles/event-hubs/event-hubs-quotas.md
Service: event-hubs
GitHub Login: @spelluru
Microsoft Alias: spelluru

@Leonardo-Ferreira Thanks for your feedback! We will investigate and update as appropriate.

@Leonardo-Ferreira I think you are correct but deferring to the author for the correct answer.
Thanks
Saurabh

@kasun04 - could you please confirm when you get a chance? Thanks.

Hi @Leonardo-Ferreira - I just confirmed with our dev manager that there is no limit for the amount of storage data for retention. I am removing the limits for other tiers in the article. The updated article will go live in 3 hours. Thanks.

The updated article is live now.
#please-close


removed file dictionary, and use full path for files in existing code…

This PR is a cleanup of the Existing Code PR.  In the original implementation there was a dictionary with file names as keys and file full paths as values.  For example:
main.py --> /Users/boss/gpt-engineer/projects/example/archive/20230816_103041/workspace/main.py
The problem with this is that there could be collision in the dict if files in different folders have the same name.  (For example util.py in multiple folders could cause a collision).  This dict has been completely removed and now the full paths are passed to the AI and returned.

You can see CI being red above below:

The security issue has been addressed, now files paths are sent over relative to the working directory.  I believe I have addressed everything.
I fixed the pre-checks, thanks for the info I did not know how to do that.


-v in 1.36

There is something wrong with version 1.36
Without -v parameter it seems to not work properly.

Sorry for the confusion!


Issue with parsing Samsung reply

When trying to parse this:
This is pretty awesome, nice work!Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From...

(I excluded the quoted reply, but it is there)
I would expect the output to be:
This is pretty awesome, nice work!

But instead I get the whole text.
I'm not sure what you can do about the Sent from... part because you probably don't want to cut off sentences that just happen to start with "Sent from". But I think you can add optional spaces to the regex and remove the end of line requirement like so:
/^-{1,10} ?Original message ?-{1,10}/

To at least handle the reply.

Can you provide a bigger extract of this email?
I see two things here:

Adding a regex for Sent from my (.), (.) smartphone
Updating the Original message regex

Sure, I have edited the emails and original text for privacy.
This is pretty awesome, nice work!Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From<EMAIL_ADDRESS>Date: 1/13/22  3:52 PM  (GMT-06:00) To<EMAIL_ADDRESS>Cc<EMAIL_ADDRESS>Subject: Status Updated

blah blah blah

I think those are both good options. The original message regex seems more important because the chain of previous messages could be very long.

Hello!
Issue should be solved now :)


Stuck while building Alexa Device SDK for Android .

Briefly summarize your issue:
I am trying to build Alexa SDK for Android by following this link. I have build SDK but not able to find startsample.sh as mentioned in process. I am not able to figure out about the Android Sample (Where can i get it).
What is the expected behavior?
I should be able to find startsample.sh
What behavior are you observing?
Not able to find startsample.sh
Provide the steps to reproduce the issue, if applicable:

Tell us about your environment:
Ubuntu 16.4 - For Installing Alexa Device SDK
What version of the AVS Device SDK are you using?
Latest
Tell us what hardware you're using:

[ ] Desktop / Laptop
[ ] Other - tell us more: Android

Tell us about your OS (Type & version):

[ ] Linux
[ ] Other - tell us more: Android

I have resolved this issue as SDK build process was not getting complete.


⚠ DesiTorrents has degraded performance

In 2cd2a55, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 200
Response time: 2660 ms

Resolved: DesiTorrents performance has improved in 4f011b5.


Url cache

Spike on making gradle cache URL's when you do an apply from: 'bla-bla-bla'
Tested it locally, by running a simple python server that sets the cache timeout:
#!/usr/bin/env python
import SimpleHTTPServer

class MyHTTPRequestHandler(SimpleHTTPServer.SimpleHTTPRequestHandler):
    def end_headers(self):
        self.send_my_headers()
        SimpleHTTPServer.SimpleHTTPRequestHandler.end_headers(self)

    def send_my_headers(self):
        self.send_header("Cache-Control", "public, max-age=2592000")

if __name__ == '__main__':
    SimpleHTTPServer.test(HandlerClass=MyHTTPRequestHandler)

I added a test.gradle file that contains println 'test 123' that was in the same dir that I ran the python script from.
Then I told gradle to apply from: 'http://localhost/test.gradle'
When it happened you saw that Gradle only requested the file once. Then looking into the cache you see that ~/.gradle/caches/modules-2/files-2.1/localhost/b04373003d5942567b9c1d7835245bd591f281b6/test.gradle file exists (how i did the caching).

@bigdaz as you've been heavily involved in the resources stuff, would you be able to help out with this review?

@ethankhall it will be safe to start working on some integ tests that execute builds that apply remote scripts. These tests should be agnostic to any implementation details, so they shouldn't need to be reworked as we refine the implementation.

@adammurdoch you'll probably need to be involved here too.

Will do. I'll make the changes you commented on. Do you want me to pull the isOffline bit? If that's something we want to do, we could put it as part of Gradle 4. I'll try to get this rolled around to you guys in the next week. Thanks for the review!

@alkemist Sorry for the delay, I've done the things you requested. I have a strange GET .sha1 happening, and I don't know why. Any thoughts? Let me know if you have any more requests.

Adding @oehme too.

@adammurdoch This PR touches dependency management a bit. Please let me know if you'd like to review it when you're back.

Is this superseded by https://github.com/gradle/gradle/pull/1900?

I'm splitting this into two PRs. I'll close


Add params for IBMId and password

IBMId and password will be used to validate WAS entitlement
Password should be encrypted

@git4rk Could you pls assign the issue to me?


Include TypeScript type definitions on npm package

Description
I'm using this module on a TypeScript React app through npm and I've noticed that it is missing its type definitions.
More specifically, I'm interested in using the Scene Graph API without having to debug or deep dive into the examples and glTF documentation.
I'm currently using the following:
declare global {
  namespace JSX {
    interface IntrinsicElements {
      'model-viewer': ModelViewerJSX & React.DetailedHTMLProps<React.HTMLAttributes<HTMLElement>, HTMLElement> ;
    }
  }
}

interface ModelViewerJSX {
  src: string
  poster?: string
  // ... others
}

interface ModelViewerElement extends Element {
  model: {
    materials: Array<{
      name: string,
      pbrMetallicRoughness: {
        setBaseColorFactor: ((x: [number, number, number, number]) => void),
        setMetallicFactor: ((x: number) => void),
        setRoughnessFactor: ((x: number) => void),

        baseColorTexture: null | {
          texture: {
            source: {
              setURI: ((x: string) => void),
            }
          }
        }
        metallicRoughnessTexture: null | {
          texture: {
            source: {
              setURI: ((x: string) => void),
            }
          }
        }
        // ... others
      }
    }>
  }
}

I believe these definitions are probably already inside the model-viewer repo, but are not getting exported to npm
Live Demo
N/A
Version

model-viewer: v1.2.1

Browser Affected

[ ] Chrome
[ ] Edge
[ ] Firefox
[ ] IE
[ ] Safari

OS

[ ] Android
[ ] iOS
[ ] Linux
[ ] MacOS
[ ] Windows

Good call; we're TS internally, so I'll see if we can get our bundler to generate a proper .d.ts file.

Progress on this?

@MariusVB A contribution here would be much appreciated if anyone knows a tool that can create a top-level .d.ts file from a bundled library like ours. The alternative is maintaining the file manually, which seems awfully error-prone.

How about this https://github.com/microsoft/dts-gen?

@MariusVB Well, it looks like that probably won't generate complete typings, but you're welcome to give it a try. As I said, I would really like to have something that automatically produces the proper API typings (since all the type info in already contained in our TS source). If that's impossible, the second best would be some kind of test that checks that a manually-created .d.ts file is consistent with our source.

What about the second answer in this thread (the one by magikMaker) https://stackoverflow.com/questions/12687779/how-do-you-produce-a-d-ts-typings-definition-file-from-an-existing-javascript ?

What about the second answer in this thread (the one by magikMaker) https://stackoverflow.com/questions/12687779/how-do-you-produce-a-d-ts-typings-definition-file-from-an-existing-javascript ?

@Sheldonfrith The trouble is we want a .d.ts file for our public API, not for every internal class of the project. What we really want is this: https://github.com/microsoft/TypeScript/issues/4433, but while that's not making much progress I did just notice an interesting comment about this solution: https://github.com/Swatinem/rollup-plugin-dts, which is the most promising thing I've seen yet. May have to give that a try.

@Sheldonfrith The trouble is we want a .d.ts file for our public API, not for every internal class of the project. What we really want is this: https://github.com/microsoft/TypeScript/issues/4433, but while that's not making much progress I did just notice an interesting comment about this solution: https://github.com/Swatinem/rollup-plugin-dts, which is the most promising thing I've seen yet. May have to give that a try.

Bump - March 2021

Also bump..I assume many webdevs use Angular/React with Typescript, so having type definitions would make model-viewer more accessible..

Would this help? Or is this orthogonal? https://dev.to/open-wc/introducing-custom-elements-manifest-gkk

Bump - July 2021

would love to have the typings ..

bump August 2021

Double bump
On Tue, Aug 10, 2021 at 9:36 AM AhrenFullStop @.***>
wrote:

bump August 2021
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/model-viewer/issues/1502#issuecomment-896035228,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJUO7X6ULOPU7PZXAZKRR3T4ETOTANCNFSM4QVDMDWA
.

--
Thanks,
Jeff Ward
Front-end Developer
Tel:<PHONE_NUMBER>
@.*** @.>
@.** https://twitter.com/#!/jeffscottward

One more bump just in case
On Tue, Aug 10, 2021 at 11:09 AM Jeff Ward @.***> wrote:

Double bump
On Tue, Aug 10, 2021 at 9:36 AM AhrenFullStop @.***>
wrote:

bump August 2021
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/model-viewer/issues/1502#issuecomment-896035228,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJUO7X6ULOPU7PZXAZKRR3T4ETOTANCNFSM4QVDMDWA
.

--
Thanks,
Jeff Ward
Front-end Developer
Tel:<PHONE_NUMBER>
@.*** @.>
@.** https://twitter.com/#!/jeffscottward

--
Thanks,
Jeff Ward
Front-end Developer
Tel:<PHONE_NUMBER>
@.*** @.>
@.** https://twitter.com/#!/jeffscottward

Okay, so I need some feedback here because this is a surprisingly complicated topic. First thing: we do and have for quite some time published our .d.ts files: https://www.unpkg.com/browse/<EMAIL_ADDRESS>What we don't have is a unified .d.ts file for our bundle, but if you're writing TS, do you really want to use our bundled version? Our thought was that those who wanted to incorporate our project at a deeper level (i.e. into a larger TS project) would probably rather import the lib, allowing you to do things like e.g. deduplicate three.js if you're also using it elsewhere. Of course if you want to stay in the land of public API, you'll need to only import model-viewer.d.ts (and avoid any symbols), as the rest of those types are private.
Has anyone tried this? I'm not very familiar with modern tools for building React/Angular apps, so I need some feedback from those who are. Also, is it possible we are missing some configuration in our package.json that would make this easier or more automatic?

Typescript cannot be assumed to be only for library level or node apps, it
is used day to day with React almost by default (see Next.js).
I see Model-Viewer as just another installable component just like any
other React components that exist on NPM.
I have no use for deduping if I’m already using model-viewer. I would have
just skipped right to raw three.js otherwise.
The standard practice is to install the library/component and then to also
install its types alongside it. DefinitelyTyped is the defacto registry
example:
@.***/react
On Tue, Aug 10, 2021 at 3:18 PM Emmett Lalish @.***>
wrote:

Okay, so I need some feedback here because this is a surprisingly
complicated topic. First thing: we do and have for quite some time
published our .d.ts files:
<EMAIL_ADDRESS>What we don't have is a unified .d.ts file for our bundle, but if you're
writing TS, do you really want to use our bundled version? Our thought was
that those who wanted to incorporate our project at a deeper level (i.e.
into a larger TS project) would probably rather import the lib, allowing
you to do things like e.g. deduplicate three.js if you're also using it
elsewhere. Of course if you want to stay in the land of public API, you'll
need to only import model-viewer.d.ts (and avoid any symbols), as the rest
of those types are private.
Has anyone tried this? I'm not very familiar with modern tools for
building React/Angular apps, so I need some feedback from those who are.
Also, is it possible we are missing some configuration in our package.json
https://github.com/google/model-viewer/blob/master/packages/model-viewer/package.json#L22-L23
that would make this easier or more automatic?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/google/model-viewer/issues/1502#issuecomment-896250630,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJUO7WCNA2CQ4NFNNT3AW3T4F3OXANCNFSM4QVDMDWA
.

--
Thanks,
Jeff Ward
Front-end Developer
Tel:<PHONE_NUMBER>
@.*** @.>
@.** https://twitter.com/#!/jeffscottward

I found a solution if you are using Angular. Go to the @NgModule that imports the component that you are using model-viewer on. For me this was my component.module.ts but might be your app.module.ts
Then look inside the @NgModule, you will have imports, declarations and exports. simply add
schemas: [CUSTOM_ELEMENTS_SCHEMA]
-- make sure to
import { CUSTOM_ELEMENTS_SCHEMA, NgModule } from '@angular/core';
This stops any errors.

@jeffscottward Yes, I agree and I want to make this as seamless as I can. What does your toolchain look like for installing deps for your React app (you'll have to start at the beginning, since I'm not a React user myself). I'm hoping there's a way to simply depend on our lib directly, which includes the types, rather than on the bundle. It's possible there's something I need to change in our package.json to facilitate this, but I'm not sure what parts your toolchain reads (different tools do it differently). How do you specify your model-viewer dep currently?

@jeffscottward Yes, I agree and I want to make this as seamless as I can. What does your toolchain look like for installing deps for your React app (you'll have to start at the beginning, since I'm not a React user myself). I'm hoping there's a way to simply depend on our lib directly, which includes the types, rather than on the bundle. It's possible there's something I need to change in our package.json to facilitate this, but I'm not sure what parts your toolchain reads (different tools do it differently). How do you specify your model-viewer dep currently?

I use Next.js right out of the box with typescript
https://nextjs.org/docs/basic-features/typescript
I use yarn instead of npm to install deps but same difference.
For model-viewer I include <script> tags in <head>
Here are the tags
<script type="module"<EMAIL_ADDRESS><script<EMAIL_ADDRESS>
I have having weird trouble with the npm module - some issues with a legacy version?
I have this in my code
// import "@google/model-viewer/dist/model-viewer-legacy"
// https://github.com/google/model-viewer/issues/690

An attempt was made at some point to do typescript (honestly Im not very good at TS but I know the value of it)
// TODO: Clean this up once fixed
// https://github.com/google/model-viewer/issues/1502
declare global {
  namespace JSX {
    interface IntrinsicElements {
      'model-viewer': ModelViewerJSX &
        React.DetailedHTMLProps<React.HTMLAttributes<HTMLElement>, HTMLElement>
    }
  }
}

But yea ideally I want to just npm install, and import, and be done with it.

First thing's first, we've removed IE support, so there is no "legacy" anymore. Seems it's also no longer necessary: https://github.com/google/model-viewer/issues/690#issuecomment-884887280
I'm also curious what would happen if you import the library instead of the bundle: @google/model-viewer/lib/model-viewer.js.
Please let me know if any of this bears fruit. I think we're pretty close.

Your docs do not explain how to actually import it via NPM
https://www.npmjs.com/package/@google/model-viewer
Also I get a compile error right away with this bare minimum react code
import ModelViewer from '@google/model-viewer/lib/model-viewer'

const Test = () => {
  console.log(ModelViewer)
  return (
    <div>

    </div>
  )
}

export default Test

wait  - compiling...
error - ./node_modules/@google/model-viewer/lib/features/animation.js:21:0
Module not found: Can't resolve 'lit-element'
null

@jeffscottward actually you should use it this way
import '@google/model-viewer/lib/model-viewer'

const Test = () => {
  return (
    <model-viewer src="..."/>
  )
}

export default Test

@elalish I created a MWE here that can help
Literally 3 lines of code to reproduce from scratch
npx create-react-app create-react-app-model-viewer --template typescript
cd create-react-app-model-viewer
yarn add @google/model-viewer

Then yarn start to test it. Try adding a <model-viewer> element and it won't compile because of the type definitions.

@jeffscottward actually you should use it this way
import '@google/model-viewer/lib/model-viewer'

const Test = () => {
  return (
    <model-viewer src="..."/>
  )
}

export default Test

@elalish I created a MWE here that can help
Literally 3 lines of code to reproduce from scratch
npx create-react-app create-react-app-model-viewer --template typescript
cd create-react-app-model-viewer
yarn add @google/model-viewer

Then yarn start to test it. Try importing and adding a <model-viewer> element to the App.tsx file and it won't compile because of the type definitions. After manually adding the model-viewer declaration to the global namespace, it will work.

Couple of items here

You did import '@google/model-viewer' not  import '@google/model-viewer/lib/model-viewer'

Thats a non-standard way of importing React components - for CSS ok as there is not top level object/function, but for tooling and idiomatic authoring, there should be an export, not an assumed namespace.

After manually adding the model-viewer declaration to the global namespace, it will work. yea this basically what I had to do above, obv shouldn't be required to just plug and play

@jeffscottward I agree, but this lib does not have a default export (I believe), so you can't do import ModelViewer from ...

Yeah, this is interesting; I have the feeling we may just need to patch up our package.json. I'm guessing when you import @google/model-viewer it may just follow the "module" path: "module": "dist/model-viewer.min.js"? In which case you're getting right back to the bundled version. Consider the error about lit-element, I'd guess we need to change our dependencies listing; it seems three.js and lit should probably be under "dependencies" instead of "devDependencies" so that React will know to go get them if you import the lib version. Now I just wish I had a way to test this before publishing to npm...

@jeffscottward I agree, but this lib does not have a default export (I believe), so you can't do import ModelViewer from ...

Would a default export be preferable? I don't have an opinion on this, just trying to figure out best practices. Here is our entry point: https://github.com/google/model-viewer/blob/master/packages/model-viewer/src/model-viewer.ts

@elalish yes so you can name it whatever you feel like as opposed to having to look it up.
Or explicitly named *if you are exporting multiple objects.
Wherever it lands do please make sure to update the README of course :)
https://github.com/google/model-viewer/tree/master/packages/model-viewer#installing
BTW the npm page for the module sends you to the top of monorepo not to the viewer package - was confusing why I was seeing a different readme
https://www.npmjs.com/package/@google/model-viewer
vs
https://github.com/google/model-viewer

Is there any progress or update on this?

Bump Nov

Bump

We could really use a contribution here. The main reason  I haven't done this is because I don't know a good way to test if what I'm doing works (since I have no experience with React/yarn/npx etc). Is anyone  up for making a PR to tweak our package.json  until  the lib version of our library can be  easily found and used? All the TS  declarations are there, we just seem to be missing a little glue (and perhaps instructions).

Exciting stuff, I'll try and look into this. Not immediately, but I'm about to use the npm package in my typescript project, and I very much would love to just import model-viewer and have it over with, and I might be able to accomplish that.
Thanks for the great work so far!

While not a "fix" - I was able to get it working by just using "// @ts-nocheck" at the top of the file that was using

I believe this has been fixed in our v1.11 release. I'm going to close this (a little hopefully) to notify people, but please comment a post a new issue if it's still not working for you.

For the ones, still facing problem, I've used this in my project:
import { Vector3 } from 'three';
import { GLTF } from 'three/examples/jsm/loaders/GLTFLoader';
// Add model-viewer to the IntrinsicElements list
declare global {
    namespace JSX {
        interface IntrinsicElements {
            'model-viewer': ModelViewerElement;
        }
    }
}
export interface ModelViewerElement extends Omit<React.DetailedHTMLProps<React.HTMLAttributes<HTMLElement>, HTMLElement>, 'ref'> {
    /**
     * The URL to the 3D model. Only glTF/GLB models are supported.
     */
    src?: string;

    'ios-src'?: string;
    /**
     * Configures the model with custom text that will be used to describe the model to viewers who use a screen reader or otherwise
     * depend on additional semantic context to understand what they are viewing.
     */
    alt?: string;
    /**
     * Displays an image instead of the model, useful for showing the user something before a model is loaded and ready to render.
     * If you use a poster with transparency, you may also want to set --poster-color to transparent so that the background shows through.
     */
    poster?: string;
    /**
     * If you're using a seamless poster as generated by toBlob({idealAspect: true}) with --poster-color transparent (which is recommended),
     * then enable this attribute to turn off the poster's transition. This keeps the shadow from blinking, and the transition is no longer necessary anyway since the poster matches the rendering.
     */
    'seamless-poster'?: boolean;
    /**
     * An enumerable attribute describing under what conditions the model should be preloaded. The supported values are "auto", "lazy" and "eager". Auto is equivalent to lazy, which loads the model
     * when it is near the viewport for reveal="auto", and when interacted with for reveal="interaction". Eager loads the model immediately.
     */
    loading?: 'eager' | 'lazy' | 'auto';
    /**
     * This attribute controls when the model should be revealed. It currently supports three values: "auto", "interaction", and "manual".
     * If reveal is set to "interaction", <model-viewer> will wait until the user interacts with the poster before loading and revealing the model.
     * If reveal is set to "auto", the model will be revealed as soon as it is done loading and rendering. If reveal is set to "manual",
     * the model will remain hidden until dismissPoster() is called.
     *
     * @example: https://modelviewer.dev/examples/loading#preload
     */
    reveal?: 'auto' | 'interaction' | 'manual';
    /**
     * This attribute makes the browser include credentials (cookies, authorization headers or TLS client certificates) in the request to fetch the 3D model. It's useful if the 3D model file is stored on another server that require authentication. By default the file will be fetch without credentials. Note that this has no effect if you are loading files locally or from the same domain.
     */
    'with-credentials'?: boolean;
    /**
     * Controls the environmental reflection of the model. Normally if skybox-image is set, that image will also be used for the environment-image. Use environment-image to only set the reflection without affecting the background. If neither is specified, default lighting will be applied. If 'neutral' is specified without a skybox, then a more evenly-lit environment is applied instead.
     */
    'environment-image'?: string;
    'camera-controls'?: boolean;
    'disable-zoom'?: boolean;
    'auto-rotate'?: boolean;
    ar?: boolean;
    autoplay?: boolean;
    'shadow-intensity'?: number | string;
    'ar-scale'?: number | string;
    bounds?: string;
    style?: React.CSSProperties;
    ref?: React.MutableRefObject<ModelViewer | undefined>;
}

export interface ModelViewer extends ModelViewerElement {
    /**
     * This property is read-only. It returns true if the load event below has fired since the last src change.
     */
    readonly loaded: boolean;
    /**
     * This property, pronounced model-is-visible, is read-only. It returns true if the element is visible on the page (assuming there is an IntersectionObserver) and the poster has been dismissed. This property is related to the model-visibility event.
     */
    readonly modelIsVisible: boolean;
    /**
     * This object contains all the methods for the materials API. See examples for usage.
     */
    readonly model: Model;
    /**
     * This property reports an array of strings, corresponding to variants in the loaded model that can be selected with variant-name.
     */
    readonly availableVariants: string[];
    /**
     * Returns a readonly copy of the GLTF JSON object as loaded. Changing this object has no affect on the scene and changes made through
     * the materials API are not reflected here. This object is useful for reverting individual changes made through the materials API.
     */
    readonly originalGltfJson: GLTF;
    /**
     * This static, writable property sets <model-viewer>'s DRACO decoder location URL. By default, the DRACO decoder will be loaded from a Google CDN.
     * @example https://modelviewer.dev/examples/loading/#dracoSupport
     */
    dracoDecoderLocation: string;
    /**
     * This static, writable property sets <model-viewer>'s KTX2 transcoder location URL. By default, the KTX2 transcoder will be loaded from a Google CDN.
     * @example https://modelviewer.dev/examples/loading/#ktx2Support
     */
    ktx2TranscoderLocation: string;
    /**
     * Rotates the model to the orientation specified by roll, pitch, yaw Euler angles, where yaw is first applied about the Y-axis, then pitch about the new local X-axis (positive is front-down), then roll about the new local Z-axis. If specified before the model loads, automatic camera framing will take this change into account; otherwise the updateFraming() method must be called manually.
     * Default Value: 0deg 0deg 0deg
     * Options: $roll $pitch $yaw
     */
    orientation: string;
    /**
     * Scales the model as specified in the X, Y, and Z directions. Scale is applied before orientation. If specified before the model loads, automatic camera framing will take this change into account; otherwise the updateFraming() method must be called manually.
     * Default Value: 1 1 1
     * Options: $x $y $z
     */
    scale: string;
    /**
     *
     */
    cameraOrbit: string;
    /**
     * Dismisses the poster, causing the model to load and render if necessary. This is currently effectively the same as interacting with the poster via user input.
     */
    dismissPoster(): void;
    /**
     * Shows the poster, hiding the model. If this is called after the 3D model has been revealed, then it will behave as though reveal='interaction', being dismissed either by a user click or a call to dismissPoster().
     */
    showPoster(): void;
    /**
     * Returns the model's bounding box dimensions in meters, independent of turntable rotation. The returned object has x, y, and z properties along with a toString() method.
     */
    getDimensions(): {
        x: number;
        y: number;
        z: number;
        toString(): string;
    };
    /**
     * Create your own Texture object.
     */
    createTexture(uri: string, type?: 'image/png' | 'image/jpeg' | 'image/webp'): Promise<Texture>;
    /**
     *
     * @param clientX
     * @param clientY
     * @return Material
     * Returns a material whose mesh primitive intersects with a ray created from the input pixel coordinates relative to the screen.
     * Returns the material whose mesh is nearest the camera.
     */
    materialFromPoint(clientX: Vector3, clientY: Vector3): Material;
    /**
     * Exports the glTF scene as a Blob object
     */
    exportScene(): Promise<Blob>;
    /**
     * Returns a screenshot of the current model render in the format specified by type (defaults to image/png). The screenshot is encoded
     * as a data URL string. In formats that support a sliding scale of quality (such as image/jpeg and image/webp) you can also specify a
     * value for encoderOptions between 0 and 1 (encoderOptions defaults to 0.92 otherwise).
     */
    toDataURL(type?: 'image/png' | 'image/jpeg' | 'image/webp', encoderOptions?: number): string;
    /**
     * Returns a promise that resolves into a Blob object in the format specified by the mimeType (defaults to image/png). A Blob object
     * represents a file-like object of immutable, raw data. You can also specify a value between 0 and 1 for qualityArgument (Currently
     * only available on Chrome desktop and Firefox) which defaults to 0.92 and 0.8 for image/png and image/webp respectively. By setting
     * idealAspect to true, the blob will be captured at the ideal poster aspect ratio instead of the canvas aspect ratio. This allows for
     * easy poster creation, where a single poster will match the render seamlessly at any canvas aspect ratio.
     * It is recommended to use a seamless webp poster image and set --poster-color to transparent and enable seamless-poster.
     */
    toBlob(options?: {
        mimeType?: 'image/png' | 'image/jpeg' | 'image/webp';
        qualityArgument?: number;
        idealAspect?: boolean;
    }): Promise<Blob>;
    /**
     * Recalculates the camera defaults in case the model has been changed, for instance by the orientation or scale attributes.
     */
    updateFraming(): void;
    /**
     * Resets the turntable that rotates the model when auto-rotate is enabled. The new value of the turntable rotation will be theta radians after this method is invoked, but the model may not update until the next render frame. If no argument is supplied, theta defaults to zero.
     */
    resetTurntableRotation(theta?: number): void;
    /**
     * Get the current camera phi, theta & radius
     */
    getCameraOrbit(): {
        phi: number;
        radius: number;
        theta: number;
        toString(): string;
    };
}

interface Model {
    /**
     * An ordered set of unique Materials found in this model. The Materials
     * correspond to the listing of materials in the glTF, with the possible
     * addition of a default material at the end.
     */
    readonly materials: Material[];

    // Returns the first material to whose name matches 'name'.
    getMaterialByName(name: string): Material | null;
}

interface Material {
    name: string;

    // Returns the glTF index of this material.
    readonly index: number;
    readonly normalTexture: TextureInfo | null;
    readonly occlusionTexture: TextureInfo | null;
    readonly emissiveTexture: TextureInfo | null;
    readonly emissiveFactor: RGB;
    readonly pbrMetallicRoughness: PBRMetallicRoughness;

    setEmissiveFactor(rgb: RGB): void;
    setAlphaCutoff(cutoff: number): void;
    getAlphaCutoff(): number;
    setDoubleSided(doubleSided: boolean): void;
    getDoubleSided(): boolean;
    setAlphaMode(alphaMode: AlphaMode): void;
    getAlphaMode(): AlphaMode;
}

interface PBRMetallicRoughness {
    readonly baseColorFactor: RGBA;
    readonly metallicFactor: number;
    readonly roughnessFactor: number;
    readonly baseColorTexture: TextureInfo | null;
    readonly metallicRoughnessTexture: TextureInfo | null;

    setBaseColorFactor(rgba: RGBA): void;
    setMetallicFactor(value: number): void;
    setRoughnessFactor(value: number): void;
}

interface TextureInfo {
    readonly texture: Texture | null;

    /**
     * Sets the texture, or removes it if argument is null. Note you cannot build
     * your own Texture object, but must either use one from another TextureInfo,
     * or create one with the createTexture method.
     */
    setTexture(texture: Texture | null): void;
}

interface Texture {
    name: string;
    readonly sampler: Sampler;
    readonly source: Image;
}

interface Sampler {
    readonly name: string;
    readonly minFilter: MinFilter;
    readonly maxFilter: MaxFilter;
    readonly wrapS: WrapMode;
    readonly wrapT: WrapMode;

    setMinFilter(filter: MinFilter): void;
    setMaxFilter(filter: MaxFilter): void;
    setWrapS(mode: WrapMode): void;
    setWrapT(mode: WrapMode): void;
}

interface Image {
    readonly name: string;

    /**
     * The type is 'external' if the image has a configured URI. Otherwise, it is
     * considered to be 'embedded'. Note: this distinction is only implied by the
     * glTF spec, and is made explicit here for convenience.
     */
    readonly type: 'embedded' | 'external';

    // The URI of the image, if it is external.
    readonly uri?: string;

    // The bufferView of the image, if it is embedded.
    readonly bufferView?: number;

    /**
     * A method to create an object URL of this image at the desired
     * resolution. Especially useful for KTX2 textures which are GPU compressed,
     * and so are unreadable on the CPU without a method like this.
     */
    createThumbnail(width: number, height: number): Promise<string>;
}

export type RGBA = [number, number, number, number];
export type RGB = [number, number, number];
type AlphaMode = 'OPAQUE' | 'MASK' | 'BLEND';

enum WrapMode {
    ClampToEdge = 33071,
    MirroredRepeat = 33648,
    Repeat = 10497
}

enum MinFilter {
    Nearest = 9728,
    Linear = 9729,
    NearestMipmapNearest = 9984,
    LinearMipmapNearest = 9985,
    NearestMipmapLinear = 9986,
    LinearMipmapLinear = 9987
}

enum MaxFilter {
    Nearest = 9728,
    Linear = 9729
}

I keep getting an error when using the <model-viewer> tag and I can't wait for this library to fix it or for DefinitelyTyped to do something. So I uploaded a types library on npm, I'm sharing it here in case anyone wants to use it or collaborate:
https://www.npmjs.com/package/model-viewer-types
I'm currently very active using model-viewer so I'll be giving it constant maintenance.

Thank you, though we do publish our own TS types - do you have any idea why they aren't being picked up in your workflow?


[BUG]

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
sign up with google or github  is not working

One more enhancement should that description of various feilds should be shown like how much length of user name should and what are rules for writing the password .
I can fix all these issue please assign me.
Expected Behavior
Behaviour should be that user can signup through their github account or google account directly .
and user should not fill difficulty in sign up
Reproduction steps
1. Go to 'Login'
2. Click on 'continue with Google'
3. Scroll down to 'error page shown'
4. See error 404 error page

Screenshots

while clicking on continue with google or github this page is shown .
Logs
No response
Browsers
Microsoft Edge
OS
Windows

Hi @krishnaacharyaa ,
I am interested to contribute and fix this bug. Please assign this bug to me.
I am GSSOC 2024 contributor.