[Bug]: Debugger generates over 5700 logs on editing TableData of Table Widget

Is there an existing issue for this?

[X] I have searched the existing issues

Description
While Modifying Table Data Property, it generates over 5700 logs for just modifying a single character of tableData Property of Table Widget. This was causing performance issues that is being fixed, but we still. need to investigate why a single action generates 5700+ debugger logs.
Steps To Reproduce

Import the below app
Navigate to Regulations page
Of the Regulations table widget, modify tableData code
Check verify that the debugger logs add 5700+ logs to the redux state

https://theappsmith.slack.com/archives/C024GUDM0LT/p1661870471009029
Public Sample App
No response
Version
Cloud/self hosted/Release

@ohansFavour @ApekshaBhosale to give more context on the issue, In the above mentioned App on Regulations Page, while editing tableData, it generates over 5700 logs. Need one of your help in determining why so many logs are needed here.


Fix missing timeline event of flutter engine's startup time

https://github.com/flutter/engine/pull/14319


Add texts extension

Description
Open WhatsApp & other apps via web browsers, sending messages and emails effortlessly.
Screencast

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

Hi @zavbala 👋
I update the code, could you give it a spin and correct if needed 🔥


File already exists but shouldn't

Every time I run the program it will generate a folder called _MEI followed by some numbers in Local/Temp, takes up roundabout 1.6gb each and it will contain some pytorch data by the looks of it.
The odd thing is, that it's the app that generates these folders upon starting, but then immediately throws a warning message that torch/_C.cp36-win_amd64.pyd already exists, but shouldn't.
Even though it generates that file itself every time it runs.
Beyond that no matter what I throw at it I'm never able to generate any audio clips, it will throw an exception at line 84, perhaps it's related, I have only tried the binary release so far

Hi @BartAgterbosch, this unfortunately is an issue with pyinstaller. It creates a folder in temp for the application which does not get cleaned up if you click close on the app window (I think you have to press ctrl+c to get it to exit properly), so I added a workaround which is supposed to delete old temp folders on startup: https://github.com/BenAAndrew/Voice-Cloning-App/blob/main/main.py#L31
However, I have no idea why this warning message is produced on startup. My guess is that it tries to create the temp folder twice for some reason but I'm not sure.
Regardless, ignore this warning as it has no impact on the app. If you are getting an exception, it is most likely a different issue


I have some problems about dataset.py

The part marked in the picture should be repalced by my own path or not ?I want to know what the dataset.py  works.

I download MSRA-B as shown. And i run the code ,but i don't change the path.
Does this have an effect on the results?

The part marked in the picture should be repalced by my own path or not ?I want to know what the dataset.py works.

this is just for own test. (just ignore it)

I download MSRA-B as shown. And i run the code ,but i don't change the path.
Does this have an effect on the results?

The default root is https://github.com/AceCoooool/DSS-pytorch/blob/5aa12cede3659c53634ecd225feaac8ebd505f7b/main.py#L37 (/home/youpcname/data), you can change to your own root.


[RFC] Standardize all stateful components on state_dict/load_state_dict

Proposed refactor
Standardize all stateful components on state_dict/load_state_dict.
Motivation
Improve CheckpointHooks API 1. consistency and 2. specificity. Currently  (see bold text here in components review doc (https://docs.google.com/document/d/1qqkkx5grYYAVT85ZemkZ0l1XrgRT71-AwxiYOF02O1o/edit#heading=h.x846c3xec7la):

Some components contribute saving/loading their own state with on_save/load_checkpoint CheckpointHooks [DataModule, PrecisionPlugin] https://github.com/PyTorchLightning/pytorch-lightning/blob/948cfd24de4f64a2980395581f15544e5e37eab0/pytorch_lightning/core/hooks.py#L765-L807
a. Callbacks contribute saving/loading their own state with different on_save/load_checkpoint hook signatures and functionality https://github.com/PyTorchLightning/pytorch-lightning/blob/948cfd24de4f64a2980395581f15544e5e37eab0/pytorch_lightning/callbacks/base.py#L293-L323
b. Loops have their own on_save/load_checkpoint methods that are inconsistent with both 1. and 1a., do not do anything, and are never called https://github.com/PyTorchLightning/pytorch-lightning/blob/948cfd24de4f64a2980395581f15544e5e37eab0/pytorch_lightning/loops/base.py#L253-L262
Some components contribute saving/loading their own state with state_dict/load_state_dict calls [Optimizers, LR schedulers, Loops]
Some components have both [LightningModule]

These inconsistencies cause confusion and there’s no reason to have these discrepancies between different components. Each component should contribute saving/loading their own state with the same API.
We should:

Ensure consistent API: Each component should contribute saving/loading of the checkpoint dictionary with the same APIs.
Improve specificity: For each component, better distinguish between and provide both of the following APIs:
a. independently contributing/loading one’s own local component state (aligning with PyTorch primitives: state_dict/load_state_dict)
- Following this convention will allow consistency across Lightning components and consistency with PyTorch conventions. Any stateful component can simply implement their own state_dict/load_state_dict methods to contribute their own state.
b. operating and depending on global component state (Lightning CheckpointHooks: on_save/load_checkpoint)

This issue is focused on aligning all components on 2a. 2b is only adjusted as needed (Callbacks).
Pitch
Move this _SupportsStateDict Protocol out to core/hooks.py file:
https://github.com/PyTorchLightning/pytorch-lightning/blob/34c62da37dc1ed9a1de7e023c690c7528ee56c60/pytorch_lightning/utilities/auto_restart.py#L638-L646
@runtime_checkable
class Stateful(Protocol):
    """This class is used to detect if an object is stateful using `isinstance(obj, Stateful)`."""

    def state_dict(self) -> Dict[str, Any]:
        ...

    def load_state_dict(self, state_dict: Dict[str, Any]) -> None:
        ...

Save aligning on state_dict
dump_checkpoint
https://github.com/PyTorchLightning/pytorch-lightning/blob/06b8f82b8a97e7e5653486731751521478f58cce/pytorch_lightning/trainer/connectors/checkpoint_connector.py#L310-L393
becomes:
def dump_checkpoint(self, weights_only: bool = False) -> dict:
   ...
   # dump callbacks
   # checkpoint["callbacks"] = self.trainer._call_callbacks_on_save_checkpoint(checkpoint)
   # becomes
   checkpoint["callbacks"] = self.trainer._call_callbacks_state_dict(checkpoint)

   ...
   # precision plugin
   # self.trainer.precision_plugin.on_save_checkpoint(checkpoint)
   # becomes
   prec_plugin = self.trainer.precision_plugin
   if isinstance(prec_plugin, Stateful):
       checkpoint[prec_plugin.__class__.__name__] = self.trainer.precision_plugin.state_dict()

   ...
   # give the model a chance to dump a few things
   # model.on_save_checkpoint(checkpoint)
   # if self.trainer.datamodule is not None:
   #    self.trainer.datamodule.on_save_checkpoint(checkpoint)
   # becomes

   # datamodule state
   dm = self.trainer.datamodule
   if dm is not None and isinstance(dm, Stateful):
       checkpoint[self.trainer.datamodule.__class__.__name__] = self.trainer.datamodule.state_dict()

   # on_save_checkpoint calls
   model.on_save_checkpoint(checkpoint)
   dm.on_save_checkpoint(checkpoint)
   prec_plugin.on_save_checkpoint(checkpoint)
   for callback in self.trainer.callbacks:
       callback.on_save_checkpoint(self.trainer, model, checkpoint)

Load aligning on load_state_dict
see component Load sections below
Callbacks:
Base Class
https://github.com/PyTorchLightning/pytorch-lightning/blob/59a7ba760548baadf6dbb30864b54cb01c7225a3/pytorch_lightning/callbacks/base.py#L293-L323
becomes
BC: on_save_checkpoint returns None instead of dict
BC: on_load_checkpoint arg takes entire checkpoint dict instead of callback_state
def on_save_checkpoint(
        self, trainer: "pl.Trainer", pl_module: "pl.LightningModule", checkpoint: Dict[str, Any]
    ) -> None:
    """Called by Lightning when saving a checkpoint to give you a chance to store anything
    else you might want to save.
    Args:
        trainer: the current :class:`~pytorch_lightning.trainer.Trainer` instance.
        pl_module: the current :class:`~pytorch_lightning.core.lightning.LightningModule` instance.
        checkpoint: the checkpoint dictionary that will be saved.
    """
    pass

def on_load_checkpoint(
    self, trainer: "pl.Trainer", pl_module: "pl.LightningModule", checkpoint: Dict[str, Any]
) -> None:
    """Called when loading a model checkpoint, use to reload state.
    Args:
        trainer: the current :class:`~pytorch_lightning.trainer.Trainer` instance.
        pl_module: the current :class:`~pytorch_lightning.core.lightning.LightningModule` instance.
        checkpoint: entire loaded checkpoint dictionary
    """
    pass

Save
https://github.com/PyTorchLightning/pytorch-lightning/blob/85304d4672a9ed24a16f7f5b2abaa34148ab86f4/pytorch_lightning/trainer/trainer.py#L1603
becomes
if isinstance(callback, Stateful):
    state = callback.state_dict()

Load
https://github.com/PyTorchLightning/pytorch-lightning/blob/06b8f82b8a97e7e5653486731751521478f58cce/pytorch_lightning/trainer/trainer.py#L1652
becomes
if isinstance(callback, Stateful):
    callback.load_state_dict(state)

restore_callbacks
https://github.com/PyTorchLightning/pytorch-lightning/blob/06b8f82b8a97e7e5653486731751521478f58cce/pytorch_lightning/trainer/connectors/checkpoint_connector.py#L205
becomes
for callback in self.trainer.callbacks:
    callback.on_load_checkpoint(self.trainer, self.trainer.lightning_module, self._loaded_checkpoint)
self.trainer._call_callbacks_load_state_dict(self._loaded_checkpoint)

Callback classes
update timer, pruning, model_checkpoint, finetuning, early_stopping to use state_dict/load_state_dict instead of on_save/load_checkpoint.
Precision Plugin:
Load
restore_training_state
https://github.com/PyTorchLightning/pytorch-lightning/blob/06b8f82b8a97e7e5653486731751521478f58cce/pytorch_lightning/trainer/connectors/checkpoint_connector.py#L189-L190
becomes
# restore precision plugin (scaler etc.)
prec_plugin = self.trainer.precision_plugin
prec_plugin.on_load_checkpoint(self._loaded_checkpoint)
if isinstance(prec_plugin, Stateful) and prec_plugin.__class__.__name__ in self._loaded_checkpoint:
    prec_plugin.load_state_dict(self._loaded_checkpoint[prec_plugin.__class__.__name__])

Precision Plugin classes
Update apex_amp, native_amp to use state_dict/load_state_dict instead of on_save/load_checkpoint
Datamodule:
Load
restore_datamodule
https://github.com/PyTorchLightning/pytorch-lightning/blob/06b8f82b8a97e7e5653486731751521478f58cce/pytorch_lightning/trainer/connectors/checkpoint_connector.py#L151
becomes
datamodule.on_load_checkpoint(self._loaded_checkpoint)
if isinstance(datamodule, Stateful) and datamodule.__class__.__name__ in self._loaded_checkpoint:
    datamodule.load_state_dict(self._loaded_checkpoint[datamodule.__class__.__name__])

Additional context

Part of #7740

If you enjoy Lightning, check out our other projects! ⚡

Metrics: Machine learning metrics for distributed, scalable PyTorch applications.

Lite: enables pure PyTorch users to scale their existing code on any kind of device while retaining full control over their own loops and optimization logic.

Flash: The fastest way to get a Lightning baseline! A collection of tasks for fast prototyping, baselining, fine-tuning, and solving problems with deep learning.

Bolts: Pretrained SOTA Deep Learning models, callbacks, and more for research and production with PyTorch Lightning and PyTorch.

Lightning Transformers: Flexible interface for high-performance research using SOTA Transformers leveraging Pytorch Lightning, Transformers, and Hydra.

cc @justusschock @awaelchli @akihironitta @rohitgr7 @ananthsub @ninginthecloud

I'm strongly in favor of this! This would clarify any confusion around checkpointing (when to use on_save/load_checkpoint vs state_dict) while also following the most familiar PyTorch conventions (state_dict/load_state_dict).
This also allows the framework to be more judicious around which components need access to the global checkpoint dict before saving/loading to minimize concerns like what order they take effect in.

Nit: If we don't want to deal with the isinstance checks everywhere, we could offer dummy implementations of state_dict/load_state_dict on the callback, datamodule, and precision plugin interfaces, given that the Lightning framework dictates these interfaces.

good call, edited!

I see the value, I am slightly in favor of this
Need to be careful with this, checkpointing bugs are the worst because in most cases we can't fix "broken" checkpoints.
To be clear that I don't misunderstand, the proposal is not to remove the on_x_checkpoint hooks, yes? Because these are the ones that users implement and they express in plain simple words what they do. In contrast, state_dict is not very clear for a user what it does.

Old related issue/PR that would probably also benefit from this standardization? #6361

I'm a bit confused about what this is actually proposing, on one hand snippets use

self.trainer._call_callbacks_on_save_checkpoint(checkpoint)

but then you mention that
state = callback.on_save_checkpoint(self, self.lightning_module, checkpoint)
will become
state = callback.state_dict()
So for each of these components, what does this propose to the following use-cases?

User wants to get the state
User wants to set a state
User wants to customize the state generation
User wants to customize the state loading

Will move out the individual component, checkpoint_connector changes to sub-issues to make this more clear/readable. Want to get alignment on the convention for 2a.

To be clear that I don't misunderstand, the proposal is not to remove the on_x_checkpoint hooks, yes?

Correct, this is only for aligning all component APIs for 2a. (at the end of Motivation section) No changes to 2b. on_x_checkpoint yet except for necessary accommodations (Callbacks)

_call_callbacks_on_save_checkpoint

Updated the Callbacks save/load section snippets to include the method name changes from _call_callbacks_on_save_checkpoint --> _call_callbacks_state_dict

So for each of these components, what does this propose to the following use-cases?

These should map to the 2a. v.s. 2b. distinctions (at the end of Motivation section):

User wants to get/set the state (2a.)
User wants to customize the state generation/loading (2b.)

Hey @jjenniferdai. I think this adds value but would need to be properly documented to avoid confusion on which method takes either the full checkpoint or the component associated state.

Thumbs up for this! "checkpoint" is a loaded term that represents various things.
state_dict()/load_state_dict() is standard in Pytorch core, and for someone that usually deals with nn.Module or torch.optimizer, it can be more natural to change state_dict.

Moving this back to 1.6 if that's ok - the 2 remaining linked PRs are already reviewed and just need to be merged
cc @carmocca @ananthsub @awaelchli @tchaton


remove local hc and nodepool creation

Addressing https://coreos.slack.com/archives/C02V40F8BH7/p1648490337830119
Signed-off-by: Ian Zhang<EMAIL_ADDRESS>

This is replaced by the following which is a continuation of this branch: https://github.com/stolostron/hypershift-deployment-controller/pull/64


rubocop: Clean up some Excludes

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Part of #14685.
Clean up some old excludes that are no longer necessary, add in-line disables for some other rules and entirely disable some rules.

Review period will end on 2023-02-21 at 00:00:00 UTC.

Review period skipped due to critical label.


Fix for issue 7233

supply extension parameter

It's preferred to make the title a description of the change (for easy viewing of git history) and then just linking the item in the description

https://help.github.com/en/articles/closing-issues-using-keywords

@alanrenmsft please use more descriptive commit messages and ideally provide a link to the issue in the description.  I have to go to the issues and look up #7233 to determine what this commit is about.  Thanks.

@kburtram, sure. sorry about that.


package building (5)

Tasks
This Repo holds 2 conda packages:

spyder-remote-server
spyder-remote-client

spyder-remote-client is a straight forward package implementing a spyder plugin.
spyder-remote-server is a bit different, in that it provides a script (in /bin or something like that)
so that one installs and enables the package as follows:
(base) me@mybox:~$ conda install spyder-remote-server
(base) me@mybox:~$ sudo spyder-remote-server --install

Prerequisites

Issue#1 : zeroconf needs to be finished
issue#2 : spyder-remote needs to be finshed
Issue#4 : spyder-remote-server daemon needs to be finished
Issue#5 : spyder-remote-server script needs to be finished

Anyway this task is to build the 2 packages.
Versions checklist

Spyder version: >= 5
Python version: 3.7, 3.8
Qt version: all
PyQt version: all
Operating System name/version:

server : Ubuntu 20.04 Linux (aarch64 on RPI)
client : Windows/Linux/macOS

This should be about a day of actual work, including setting up CI to automate the release process and setting the PyPI/conda-forge workflows plus release documentation. But this sometimes takes a bit longer due to time needed on conda-forge for things ti be approved etc.
2 Days.


radio: selecting a radio button temporarily focuses the 0th item

Bug
Expected behavior

Click an item
Focus the clicked item

Actual behavior

Click an item at index 1+
Focus the 0th item temporarily
Focus the clicked item

I see this on the DS site, but sped up.
This is from Nate P


Always getting deprecated warning when not providing  --skip-repo-update

helmfile -l name=blah apply
--skip-repo-update has been deprecated. Provide --skip-deps instead.
Adding repo stable https://kubernetes-charts.storage.googleapis.com
"stable" has been added to your repositories

I get the same, seems like this snippet is the culprit:
if !c.Bool("skip-deps") || !c.Bool("skip-repo-update") {
						if !c.Bool("skip-repo-update") {
							logger.Warn("--skip-repo-update has been deprecated. Provide --skip-deps instead.")
}

Won't both these flags be false by default?

Ah, good catch! Can we just remove them assuming it's not hard to migrate, and adding nil values handling to those flags wouldn't worth the effort?

Going ahead with #493, anyway.


Documentation: Missing Center of Excellence Starter-kit option

Documentation Issue
The Admin Environment and Settings section mentions "Bootstrap the Admin Environments with Center of Excellence Starter-kit" option. However, this option is missing in the deployment UI.
Had a look into the PR history and can see this option has been removed in https://github.com/microsoft/industry/pull/309 - foundations/powerPlatform/referenceImplementation/ppNorthStar-arm.json line 530.
Could you please advise if this has been done intentionally?
Can we expect this feature implemented in the script anytime soon?
Code of Conduct

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

Hi @mehowq - and thanks for reaching out, and I sincerely apologise for the delayed response. We were planning to include it initially, but due to some constraints with the API surface to put it together end-2-end, we removed the option for now.


[5.7]🍒Ensure clocks properly respect leeways and use raw time for calculations for continuous clocks

Original PR: https://github.com/apple/swift/pull/58396
Continuous clocks incorrectly used non raw clock values (which could result in missing time frames in cases where the raw clock did not align with dispatch's expectations).
This aligns those expectations further as well as handling the leeway functions for the clock sources.
Risk: Low

@swift-ci please smoke test

@swift-ci please test


Implement Channel Viewer

Implement a channel viewer similar to the original viewer. We want to have a more basic viewer. (Do we even want to have a channel tree?)

duplicate of #17


[BUG] Smart Doors Integration - Still plays sound and logs the open attempt in chat when too far,

Module Version: v2.1.32
No console log of note happens when doing this.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Smart Doors Integration - Still plays sound and logs the open attempt in chat when too far,
Expected behavior
Nothing should happen, the interaction should be blocked
Browser:

Firefox

Foundry Version: v9.269
Game System: PF2E
Additional context
Not sure if this is on this plugins end or Smart Doors, just the page mentioned compatibility so figured I'd bring this up.

Sorry for the late reply , for limited free time i will ignore any issue related to fvtt9 and fvtt10, sorry for the trouble.


Function Signature formatting makes it more difficult to search for Haskell or PureScript equivalents

It would be nice to be able to copy a function signature from SanctuaryJS docs and paste it into Hoogle or Pursuit to find equivalent or similar functions in Haskell or PureScript.
Unfortunately, the use of WORD JOINER / U+2060 in -> and friends in SanctuaryJS function signatures makes it harder to do this.
Searching for the Haskell and PureScript equivalent of Sanctuary's chain function (fn sig copied directly from the SanctuaryJS docs):
Haskell:

PureScript:

Ramda uses the → character, which works in Pursuit, but not in Hoogle:

Yes, I want to fix this in Ramda too; it's just never made it to the top of the list.  What I really want to do is to use Fira Code, a font with programmers' ligatures, which I first noticed on Tom Harding's site (for example, on his Setoid overview.)
This would allow users to cut and paste -> but still have it appear as a readable arrow.
I think this would improve things quite a bit.

@CrossEye I use Fira in VSCode, where I mostly write PureScript (still learning), but I also take advantage of the fact that PureScript allows unicode characters like ∷, ∀, ⇒ and → :)
Examples:

@kurtmilam, might it be possible to write a few lines of JavaScript to intercept the copy event?
@CrossEye, if you have Fira Code installed you should see it in use on the Sanctuary website.

@davidchambers: Interesting.  When I tried copying the chain signature to Hoogle earlier in the day, I got the same result that Kurt described.  Now it works fine.  Did this change recently, or could it be a difference between Windows and Ubuntu?

@CrossEye, were you copying from the website or from the readme? The script that generates the website removes WORD JOINER characters.

@davidchambers That sounds like an interesting solution. I'll do some research as soon as I get a chance.
I'm on a Mac and copied the sigs from the readme, btw.

That sounds like an interesting solution. I'll do some research as soon as I get a chance.

My suggestion was misleading. I mistakenly assumed the problem applies to the website, but after investigating I convinced myself that it only applies to the readme.
I'm ready to revert plaid/transcribe#14, as it introduced more problems than it solved (in addition to the copy and paste problem, Safari incorrectly renders WORD JOINER characters as spaces).
@kurtmilam, if you have a chance please open an issue and include a link to this one. I think further discussion should take place in Transcribe's issue tracker.

Ah, OK. I had just worked out a solution to remove the WORD JOIN character on the copy event and was going to see how / whether it was possible to run javascript on a GitHub md page 😄

@davidchambers: Perhaps I switched from one to the other when I switched from work (Windows) to home (Mac).  I didn't check.

Also, for posterity, the screenshots I shared above, which I thought were of Fira Code were actually of Hasklig, which also supports ligatures.
I had specified Fira Code as the primary font in my editor, but I'd somehow managed to bungle font's installation.
I've rectified that now 😄

@kurtmilam OT, but I prefer Hasklig to Fira anyway because Fira is too skinny for me anyway. :wink:
I was using a fork of Hasklig called Blackfont for a while that had better support for JS ligatures, but still looks the same.
Now I am using the ligature variant of Fantasque Sans which is more pleasing to my eyes but has less ligatures.


Firebase upload suddenly won't work

I am using
"firebase": "^3.6.0",
"react": "15.3.2",
"react-native": "0.37.0",
"react-native-camera": "git+https://github.com/lwansbrough/react-native-camera.git",
"react-native-fetch-blob": "^0.10.0",
"react-native-vector-icons": "^3.0.0",
"react-native-video": "^0.9.0"

And i'm trying to upload a video recorded with react-native-video to firebase - this worked but suddenly it stopped working and now it doesn't succeed.
I'm using the following code where this.props.file.path looks something like this:
file:///storage/emulated/0/Pictures/vidid.mp4
  accept = () => {
    let rnfbURI = RNFetchBlob.wrap(this.props.file.path)
    Blob
    .build(rnfbURI, { type : 'video/mp4;'})
    .then((blob) => {
      // upload image using Firebase SDK
      firebase.storage()
        .ref()
        .child('testImageName')
        .put(blob, { contentType : 'video/mp4' })
        .then((snapshot) => {
          console.log(snapshot)
          blob.close()
          done()
        })
    })
}

I tried writing Firebase support, but then won't help me since this is a workaround.
My blob object looks like this:
 { listeners: {},
   isRNFetchBlobPolyfill: true,
   multipartBoundary: null,
   _ref: 'file:///storage/emulated/0/Pictures/VID_20161113_142100.mp4',
   _blobCreated: true,
   _closed: false,
   cacheName: 'blob-559cd5c4-e880-4742-a3fe-dfae7e1a0df0',
   type: 'video/mp4;',
   size: '3665375' }

May be related to #180?
Is the Firebase error related to the "wrong offset"?

It doesn't give any error - it just stalls at zero procent uploaded.

We are experiencing the same issue with iOS: The upload might actually succeed (seems to be with small files) but the the Firebase API upload callback is never called. (Even if the upload was successful and the file appears in storage).
We tested with release build iOS and development Android. Development Android works perfectly. Release iOS experiences this issue. Haven't tested with development build iOS.

Well, I'm not be able to reproduce this bug, I think I need more information, the logs from XMLHttpRequest polyfill can be turned on by adding this line :
XMLHttpRequest.setLog(3);

I think it'd helpful !

I have the same thing on Android, the only thing i did was update my android studio then suddenly the callback won't return. I've tried a couple of different approch, using .then or listen to state - or add an await before the "put" command.
The result is always the same - the file does get uploaded to the firebase storage but the client never get the callback.
Here is my XMLHttpRequest log:
11-21 18:59:45.292 10418-25443: 'XMLHttpRequest', 'verbose:', 'get readyState', 2
11-21 18:59:45.292 10418-25443: 'XMLHttpRequest', 'verbose:', 2
11-21 18:59:45.308 10418-25443: 'XMLHttpRequest', 'debug:', 'XMLHttpRequest done', 'https://firebasestorage.googleapis.com/v0/b/planme-1383.appspot.com/o?name=posts%2Ftest123', { data: '{\n  "name": "posts/test123",\n  "bucket": "planme-1383.appspot.com",\n  "generation": "1479747585452000",\n  "metageneration": "1",\n  "contentType": "image/jpg",\n  "timeCreated": "2016-11-21T16:59:45.379Z",\n  "updated": "2016-11-21T16:59:45.379Z",\n  "storageClass": "STANDARD",\n  "size": "490",\n  "md5Hash": "Z+XksMhLu5ErgM6Y9Zv8aw==",\n  "contentEncoding": "identity",\n  "crc32c": "m0iZQg==",\n  "etag": "CODPwKmputACEAE=",\n  "downloadTokens": "8b6a0752-98ef-470c-a9a4-f52453842d8f"\n}',
taskId: '981f0943-19f4-4fb6-afc7-3d9bc80b5b8e',
type: 'utf8',
respInfo:
{ respType: 'json',
headers:
{ 'alt-svc': 'quic=":443"; ma=2592000; v="36,35,34"',
server: 'UploadServer',
date: 'Mon, 21 Nov 2016 16:59:45 GMT',
'content-length': '480',
'access-control-allow-origin': '',
'content-type': 'application/json; charset=UTF-8',
'access-control-expose-headers': 'X-Firebase-Storage-XSRF',
'x-content-type-options': 'nosniff',
'x-guploader-uploadid': 'AEnB2UqL-9999-9NIQe8ypZHJFwf97XXl1CRKTLOVWalspwcI2HHiYqDy5UYAnqE1E9zUoRkYrM5oBUMYxepjsnnXC3g50ofFQ' },
redirects: [ 'https://firebasestorage.googleapis.com/v0/b/planme-1383.appspot.com/o?name=posts%2Ftest123' ],
timeout: false,
taskId: '981f0943-19f4-4fb6-afc7-3d9bc80b5b8e',
state: '2',
status: 200,
rnfbEncode: 'utf8' },
info: [Function],
array: [Function],
blob: [Function],
text: [Function],
json: [Function],
base64: [Function],
flush: [Function],
path: [Function],
session: [Function],
readStream: [Function],
readFile: [Function] }, { listeners:
{ abort: [ [Function] ],
error: [ [Function] ],
load: [ [Function] ] },
_onabort: [Function],
_onerror: [Function],
_onload: [Function],
_onloadstart: [Function],
_onprogress: [Function],
_ontimeout: [Function],
_onloadend: [Function],
upload:
{ listeners: {},
_onabort: [Function],
_onerror: [Function],
_onload: [Function],
_onloadstart: [Function],
_onprogress: [Function],
_ontimeout: [Function],
_onloadend: [Function] },
_readyState: 3,
_uriType: 'net',
_response: '',
_responseText: '',
_responseHeaders:
{ 'alt-svc': 'quic=":443"; ma=2592000; v="36,35,34"',
server: 'UploadServer',
date: 'Mon, 21 Nov 2016 16:59:45 GMT',
'content-length': '480',
'access-control-allow-origin': '',
'content-type': 'application/json; charset=UTF-8',
'access-control-expose-headers': 'X-Firebase-Storage-XSRF',
'x-content-type-options': 'nosniff',
'x-guploader-uploadid': 'AEnB2UqL-9999-9NIQe8ypZHJFwf97XXl1CRKTLOVWalspwcI2HHiYqDy5UYAnqE1E9zUoRkYrM5oBUMYxepjsnnXC3g50ofFQ' },
_responseType: '',
_responseURL: '',
_responseXML: '',
_status: 200,
_statusText: 200,
_timeout: 60000,
_sendFlag: true,
_uploadStarted: true,
_increment: false,
_config: {},
_headers:
{ 'X-Goog-Upload-Protocol': [Getter/Setter],
'Content-Type': [Getter/Setter],
Authorization: [Getter/Setter],
'X-Firebase-Storage-Version': [Getter/Setter] },
withCredentials: false,
_method: 'POST',
_url: 'https://firebasestorage.googleapis.com/v0/b/planme-1383.appspot.com/o?name=posts%2Ftest123',
_body:
{ listeners: {},
isRNFetchBlobPolyfill: true,
multipartBoundary: null,
_ref: '/data/user/0/com.planme/files/RNFetchBlob-blobs/blob-bfd87981-05bd-488a-b6bd-2f9ded892934',
_blobCreated: true,
_closed: false,
cacheName: 'blob-bfd87981-05bd-488a-b6bd-2f9ded892934',
type: 'text/plain',
size: 692 },
_task:
{ _45: 1,
_81: 1,
_65:
{ data: '{\n  "name": "posts/test123",\n  "bucket": "planme-1383.appspot.com",\n  "generation": "1479747585452000",\n  "metageneration": "1",\n  "contentType": "image/jpg",\n  "timeCreated": "2016-11-21T16:59:45.379Z",\n  "updated": "2
11-21 18:59:45.309 10418-25443: 'XMLHttpRequest', 'debug:', 'https://firebasestorage.googleapis.com/v0/b/planme-1383.appspot.com/o?name=posts%2Ftest123', { respType: 'json',
headers:
{ 'alt-svc': 'quic=":443"; ma=2592000; v="36,35,34"',
server: 'UploadServer',
date: 'Mon, 21 Nov 2016 16:59:45 GMT',
'content-length': '480',
'access-control-allow-origin': '*',
'content-type': 'application/json; charset=UTF-8',
'access-control-expose-headers': 'X-Firebase-Storage-XSRF',
'x-content-type-options': 'nosniff',
'x-guploader-uploadid': 'AEnB2UqL-9999-9NIQe8ypZHJFwf97XXl1CRKTLOVWalspwcI2HHiYqDy5UYAnqE1E9zUoRkYrM5oBUMYxepjsnnXC3g50ofFQ' },
redirects: [ 'https://firebasestorage.googleapis.com/v0/b/planme-1383.appspot.com/o?name=posts%2Ftest123' ],
timeout: false,
taskId: '981f0943-19f4-4fb6-afc7-3d9bc80b5b8e',
state: '2',
status: 200,
rnfbEncode: 'utf8' }, 'json'
11-21 18:59:45.309 10418-25443: 'XMLHttpRequest', 'verbose:', 'get responseText', '{\n  "name": "posts/test123",\n  "bucket": "planme-1383.appspot.com",\n  "generation": "1479747585452000",\n  "metageneration": "1",\n  "contentType": "image/jpg",\n  "timeCreated": "2016-11-21T16:59:45.379Z",\n  "updated": "2016-11-21T16:59:45.379Z",\n  "storageClass": "STANDARD",\n  "size": "490",\n  "md5Hash": "Z+XksMhLu5ErgM6Y9Zv8aw==",\n  "contentEncoding": "identity",\n  "crc32c": "m0iZQg==",\n  "etag": "CODPwKmputACEAE=",\n  "downloadTokens": "8b6a0752-98ef-470c-a9a4-f52453842d8f"\n}'
11-21 18:59:45.309 10418-25443: 'XMLHttpRequest', 'debug:', 'request done state = 4'

Okay, I'll setup an 0.37 environment and try reproduce the problem.

The bug reproduce in 0.36, 0.36.1 and 0.35 as well
בתאריך 22 בנוב׳ 2016 4:03, "wkh237"<EMAIL_ADDRESS>כתב:

Okay, I'll setup an 0.37 environment and try reproduce the problem.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/wkh237/react-native-fetch-blob/issues/179#issuecomment-262126400,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAZSEsgQvjwIRWG8KjF8fGmdPvQYZmdyks5rAk1JgaJpZM4KwsO-
.

I see the response data when i put breakpoints in debug mode on the XMLHttpResponse - but it never call any of my events except the error. It is like the firebase javascript sdk won't register well to the events somewhere.

I think I found a related bug when calling getDownloadURL() using "firebase": "^3.6.1". If  window.XMLHttpRequest is overwritten by the polyfill, the returned promise does not resolve. I tried to look at the logs, but like @tomershohet is saying, everything seems fine with the response data. There is probably some event that firebase waits for, but I can't find it. Debugging the minified firebase code is hard.

@sprmn , thanks for the information. Looks like it may related to the firebase's version since I can't get these error with 3.4.1. I'll look into it.

Yes, it was not present in any version before 3.6.1.

Btw, you'll have to fix #187 in order to debug this, otherwise getDownloadURL() will throw an error.

So i can say for sure that the bug is happening due to something that was change on firebase javascript sdk between 3.5.1 and 3.6.0.
The callback works on 3.5.1 and stop working from 3.6.0 and farther versions.

@wkh237, I think I found the problem.
The firebase team probably changed their code in the newer api versions and now uses event listeners for the XMLHttpRequest. The event related code of the XMLHttpRequest polyfill is incorrect. The dispatchEvent over here expects an event object with a type field containing the event type, whereas here a type is provided to the dispatcher as first argument and the second argument contains the event object. Therefore the listeners are never called, since the event.type will always be undefined.
To fix it, either the dispatchEvent calls should provide the event object as first argument, or the dispatchEvent function itself should accept the type as first argument and the event object as second argument.

FYI, I've published a beta release on npm 0.10.1-beta.1 hopefully this can solve the problem. Please try if it works, thanks !

@wkh237  It works well, thanks!

@wkh237 I thought it was working fine, but uploaded image files broken :'-(

I still can't get it to work with:
"firebase": "^3.6.1",
"react-native-fetch-blob": "0.10.1-beta.1",

Using the example from firebase docs it stalls at:
01-05 12:59:55.790 27241  9276 I ReactNativeJS: Upload is 0% done
01-05 12:59:55.790 27241  9276 I ReactNativeJS: Upload is running
`  var path = this.props.file1.path
Blob.build(RNFetchBlob.wrap(path), { type : 'image/jpeg' })
.then((blob) => {
console.log(blob)
var uploadTask = firebase.storage()
.ref('rn-firebase-upload')
.child('testImageName')
.put(blob, { contentType : 'image/png' })
uploadTask.on('state_changed', function(snapshot){
  // Observe state change events such as progress, pause, and resume
  // Get task progress, including the number of bytes uploaded and the total number of bytes to be uploaded
  var progress = (snapshot.bytesTransferred / snapshot.totalBytes) * 100;
  console.log('Upload is ' + progress + '% done');
  switch (snapshot.state) {
    case firebase.storage.TaskState.PAUSED: // or 'paused'
    console.log('Upload is paused');
    break;
    case firebase.storage.TaskState.RUNNING: // or 'running'
    console.log('Upload is running');
    break;
  }
}, function(error) {
  console.log(error)
  // Handle unsuccessful uploads
}, function() {
  // Handle successful uploads on complete
  // For instance, get the download URL: https://firebasestorage.googleapis.com/...
  var downloadURL = uploadTask.snapshot.downloadURL;
  console.log('feeed nok det virker')
});

}
)
`

For me it says
Upload is 0% done
Upload is running
Upload is 100% done
Upload is running
Error: Uncaught (in promise): TypeError: this.uploadTask is undefined
[150]/UploadPage.prototype.phenko/</<@http://localhost:8100/build/main.js:206:21
async/</<@http://localhost:8100/build/vendor.js:125056:13
f</t.prototype.invoke@http://localhost:8100/build/polyfills.js:3:9281
onInvoke@http://localhost:8100/build/vendor.js:4508:28
f</t.prototype.invoke@http://localhost:8100/build/polyfills.js:3:9208
c</r.prototype.run@http://localhost:8100/build/polyfills.js:3:4433
f/<@http://localhost:8100/build/polyfills.js:3:14074
f</t.prototype.invokeTask@http://localhost:8100/build/polyfills.js:3:9956
onInvokeTask@http://localhost:8100/build/vendor.js:4499:28
f</t.prototype.invokeTask@http://localhost:8100/build/polyfills.js:3:9869
c</r.prototype.runTask@http://localhost:8100/build/polyfills.js:3:5124
o@http://localhost:8100/build/polyfills.js:3:2196
t/this.invoke@http://localhost:8100/build/polyfills.js:3:10985

Stack trace:
c@http://localhost:8100/build/polyfills.js:3:13535
f/<@http://localhost:8100/build/polyfills.js:3:14107
f</t.prototype.invokeTask@http://localhost:8100/build/polyfills.js:3:9956
onInvokeTask@http://localhost:8100/build/vendor.js:4499:28
f</t.prototype.invokeTask@http://localhost:8100/build/polyfills.js:3:9869
c</r.prototype.runTask@http://localhost:8100/build/polyfills.js:3:5124
o@http://localhost:8100/build/polyfills.js:3:2196
t/this.invoke@http://localhost:8100/build/polyfills.js:3:10985

@hananurrehman I am seeing this same behavior now that you described above except I don't even get an error returned. I get a successful response but the image never shows up and in the firebase console itself when trying to view the asset it says "Error loading preview". I have noticed that I only see this behavior on images over 350k, my images that fail are all around 650k. This was working fine not too long ago and I haven't changed much around this functionality. Do you recall your fix or workaround by chance?

I'm sorry I do not have access to that code now.

Shoot, ok thanks anyway.

@jSkrills I am facing that same issue now that I upgraded expo to sdk 31.
Did you manage to solve the problem?


Global Attribute Cluster Revision needs to be fixed for Color Control Cluster

Spec snippet :

Value should be 5

Color Control cluster must be spec compliant for v1.
Removing tag v1_triage_split_4

SDK Spec Review: Given no cert tests are failing here (cert blocker), we believe this is likely resolved.


ORCID auth

Added authentication provider for ORCID (see http://orcid.org/)

Hi @tparnell8
Would you be able to merge this provider into master? ORCID is ready to post it on their website! :)

Sure can you update this PR
You need to fix the merge conflicts, and if you notice the project structure has recently changed. You will need to update this implementation to the new model.

Hi @tparnell8,
Got it! Will do and let you know.

Thanks, essentially each provider is its own package now...it shouldn't be too much work to implement the changes.
Let me know if you need any help...
This model is new to this project, and I plan to release the first version(s) within the next 24 hrs or so...
I guess I should also give @Eonasdan a heads up about that :wink:

@RickZee if you have time at some point you should also consider porting this to .net core, the new project model, and aspnet core 1.0 There is a project underway here: https://github.com/aspnet-contrib/AspNet.Security.OAuth.Providers

@tparnell8 - yes, I think I should contribute the to aspnet core as well, thanks for the suggestion!

I will create another PR. I re-forked the repo due to the structure change.

:+1:


Configure caching for static files

I think static fe files should be cached with cache control headers.
Idea: Cache files with hash in filen ame forever. Never cache index.html
Vercel probably does this by default. Let's check if Netlify and Cloudflare does this...
Also configure it for Heroku like and Docker deploys, where fe static files are served from the api server...

done


Selective posfile

This first version allows to select which joint to operate. Using the symbol "-" instead of a number in the pos file if you don't want to send any command to that specific joint.
The parser checks the pos file to avoid discrepancies among the multiple keyframes specifications.

Thanks for opening this PR @antbono, I like the idea of using actions, and it makes it a lot easier to provide feedback with a proof of concept as shown in this PR. So, thank you.
Here is one thought before I go into feedback:

Merging these changes in directly would break other teams' code that relies on the current behavior. I suggest we put your new code in a new repo called "nao_pos" as a version 2 of this project. The two packages could be called "nao_pos_server" and "nao_pos_interfaces", or something. Over time, we encourage people to use nao_pos and try and deprecate this repository.

Here's my feedback on the changes:

In contrast to the file parameter that currently takes the full file path, the filename in the action request, only allows selecting a pos file from inside the naosoccer_pos_action/action directory. This prevents teams from using their own pos files, outside naosoccer_pos_action package. I think using the full file path is necessary to allow that flexibility.
I don't want to include many pos files in this repo. This is because I don't want contributors raising PRs to "tweak" the pos files to make it work on their robot. Also, using rUNSWift's pos files will lower adoption rate (because code usage must be announced if another team's code is used). Rather, I suggest you create a separate package in your own codebase with the pos files you need.
We need clear definitions on how the ignore ("-") operator for a joint position should behave. Can you have some lines in your pos file where the joint position is "-", while some other lines where it is a number? (Looking at the code, it looks like that won't work).
Loading and parsing the pos files when starting the node may be a good way to catch parsing problems in the pos file. Consider a team modifies their pos file right before a game, and they have a missing joint value. Only when the robot falls over, the naosoccer_pos_action node would complain that it can't parse the getup file. If we load all the pos files we need at the start, we can catch such problems earlier.

If you agree with splitting the repo, let's organize a call and do a bit of planning.


DEBUG: Print response on JSON-RPC query errors

Help debug some serde parsing issue with gas estimations.

For the record after adding this PR the problem revealed itself in the following way.
On the client the error was unchanged:
message: 'failed to call estimate gas query: estimate gas query failed: abci query failed: serde parse error\n' +
        '\n' +
        'Caused by:\n' +
        '    expected value at line 1 column 1\n' +
        '\n' +
        'Location:\n' +
        '    /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/flex-error-0.4.4/src/tracer_impl/eyre.rs:10:9: serde parse error: expected value at line 1 column 1'

This came through an ethapi that connected to a load balancer, which routed queries to cometbft nodes.
In the ethapi logs we saw the body that failed to parse:
2024-04-16T14:42:57.466868Z ERROR fendermint/rpc/src/client.rs:335: failed to parse JSON-RPC response error="serde parse error\n\nCaused by:\n    expected value at line 1 column 1\n\nLocation:\n    /root/.cargo/registry/src/index.crates.io-6f17d22bba15001f/flex-error-0.4.4/src/tracer_impl/eyre.rs:10:9" response="upstream connect error or disconnect/reset before headers. reset reason: connection termination"

Trying locally the error was slightly different, pointing exactly at the problem:
message: 'failed to call estimate gas query: estimate gas query failed: abci query failed: HTTP error\n' +
        '\n' +
        'Caused by:\n' +
        '    connection closed before message completed\n' +
        '\n' +
        'Location:\n' +
        '    /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/flex-error-0.4.4/src/tracer_impl/eyre.rs:10:9: HTTP error: connection closed before message completed'

We were given extra context that the call for which they were estimating gas was big, took over 8s to complete, which could have caused a timeout. Trying it locally with an artificial 15s sleep added to any estimation, the same problem occurred in the e2e tests:
Error: failed to call eth_estimateGas w/ height: (code: 0, message: failed to call estimate gas query: estimate gas query failed: abci query failed: HTTP error

Caused by:
    connection closed before message completed

Location:
    /usr/local/cargo/registry/src/index.crates.io-6f17d22bba15001f/flex-error-0.4.4/src/tracer_impl/eyre.rs:10:9: HTTP error: connection closed before message completed, data: None)

After some digging around in CometBFT code I found these timeouts in the HTTP server, and the way we can increase them was found:
# How long to wait for a tx to be committed during /broadcast_tx_commit.
# WARNING: Using a value larger than 10s will result in increasing the
# global HTTP write timeout, which applies to all connections and endpoints.
# See https://github.com/tendermint/tendermint/issues/3435
timeout_broadcast_tx_commit = "10s"

That is, the CMT_RPC_TIMEOUT_BROADCAST_TX_COMMIT env var needs to be adjusted upwards if HTTP requests are expected to take longer than 10s.


Cloudprober on Google Cloud Run

I have been trying to set up Cloudprober to run on Google Cloud's Cloud Run from the image listed on docker. However, I've run into issues with it.
I get a general error:
The user-provided container failed to start and listen on the port defined provided by the PORT=9313 environment variable.
And more specific errors within the logs:
cloudprober.go:134] Error reading config from metadata. Err: metadata: GCE metadata "project/attributes/cloudprober_config" not defined
logger.go:205] [cloudprober.sysvars] Error getting instance name on GCE: metadata: GCE metadata "instance/name" not defined
cloudprober.go:182] Error initializing cloudprober. Err: sysvars_gce: error while getting internal_ip from metadata: metadata: GCE metadata "instance/network-interfaces/0/ip" not defined"
The "How-Tos - Running on Kubernetes" page on Cloudprober's website is helpful for setting up Cloudprober on GKE, but it is a bit overkill for some users (customers of a Google Cloud service). Would it be possible to add similar support for Cloud Run (or point me to some tools to debug this)?

@michaelsatanovsky thanks for reporting this.
There is a workaround for this. You can add the following flag to the command line to disable getting cloud metadata: --cloud_metadata=none.
This error is coming from the fact Cloudprober is discovering it's running on Google cloud, but it's not able to get certain metadata variables. On kubernetes we return early: https://github.com/cloudprober/cloudprober/blob/7d1085c3161c24215864dfee984b424076834bd4/sysvars/sysvars_gce.go#L66.
If we can easily identify that we're running on Cloud Run we can make this more automatic. I'll look into that.

Hi @manugarg,
Thanks for following up on this! I was unable to get Cloudprober to run on Cloud Run as it seemed to require access to other cloud metadata. I ended up using a VM instance. Should Cloudprober work with Cloud Run after this fix?
Thanks again!

Hello, @michaelsatanovsky
This change has not been released yet. If you want to test before the release, you can use the docker image tag - "master". Let me know if that doesn't work as well.

I see. Thanks for retrying it. I'll take another look.

Sorry for the delay. I found the issue and submitted the fix:
https://github.com/cloudprober/cloudprober/pull/228
"master" image should work on Cloud Run now. Would you be able to give it another try? Thanks in advance!

This seems promising after some preliminary testing. I'll continue looking at it in more depth over the next couple days.
Thanks!

Thanks for checking, @michaelsatanovsky! Closing this now; feel free to reopen if you encounter an issue again.


feat: support @vue/compiler-sfc in the vue extension

✅ Closes: #384
@jods4

:tada: This PR is included in version 5.0.0-alpha.8 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 5.0.0-beta.1 :tada:
The release is available on:

npm package (@beta dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


16 Dec 2024: Missing Sentinel-2 data between November 2023 and Februa…

…ry 2024 in AWS database only

[x] Content was spellchecked (e.g. using Microsoft Word or Grammarly).
[x] Updates are posted to the DEA Tech Alerts page.

Claire K has reviewed.


No indication of ghost text and actions via screen reader

As far as I can tell, we blow right by the ghost text if displayed—I only hear the next visible line being read.
I expected to hear the suggestion read out, and then ideally get some sort of access to the hover widget via the keyboard. Do we have any precedent for having the screen reader output something like "Press [cmd K + cmd I] for more suggestions and actions"?
https://user-images.githubusercontent.com/25163139/217100999-da3b2ef9-f8b7-4449-802e-d63311537b5a.mp4
cc @isidorn @hediet @esonnino @meganrogge

Thank you for creating this issue.
I have discussed with @meganrogge and we agreed to re-think the inline suggestion experience and see if we should read out all ghost suggestions, or skew users towards the Ctrl+Enter experience.

It would be great to hear from some screen readers users what they would prefer here. Roberto being one such example.
On one hand, the full editor experience feels much easier to reason about since it acts just like our normal editors. On the other, it feels super heavyweight for what is intended to be a lightweight in-context experience.

We play an audio cue currently when there's a suggestion.
To align the immediacy of the experience with that of sighted users, @jooyoungseo suggested we add a setting to read the suggestion when it appears. I think it makes sense to do that.


"<module_name>" is not accessed Pylance warning

Discussed in https://github.com/microsoft/pylance-release/discussions/5143

Originally posted by Ritesh313 November 24, 2023
I'm getting "<module_name>"is not accessed warnings from Pylance in my python file while importing all the stdlib modules.
The warning description just says:
conda_env_location/lib/python3.9/<module_name>.py" is overriding the stdlib module "<module_name>"
I have my anaconda environment selected as my interpreter in VS code. I know it's just a warning and not interrupting my code, but I would just like to know if I have something setup wrong. Please let me know if I should provide some other information for this.
Modules which have this warning: datetime, random, typing, argparse
Platform: VS code
Environment: Conda
Python version: 3.9.7
Here's a screenshot of the warning:

As a workaround you can disable the warning for now like so:
    "python.analysis.diagnosticSeverityOverrides": {
        "reportShadowedImports": "none"
    }

I can reproduce this in a conda enviroment if I open the 'envs' folder:

We don't detect conda environments as virtual environments because they don't have a bin\activate or Scripts\activate file.
We could probably detect this situation, but I don't think this is very common. Most of the time the env folder is tucked away under the home directory.

We could probably detect this situation, but I don't think this is very common. Most of the time the env folder is tucked away under the home directory.

I do know there are also up-and-coming tools like Pixi that prefer to put Conda envs in a project subfolder, so it may become more common in the future. Pixi stores things in {project_root}/.pixi/ though, so it's ignored by Pylance (which excludes **/.* paths by default) and doesn't cause issues.
For anyone else who likes to put Conda envs in a .gitignored subfolder of their projects (like me!), Pylance will happily ignore it as long as you name your subfolder something like .env/ =)

This issue has been fixed in prerelease version 2024.4.100, which we've just released. You can find the changelog here: CHANGELOG.md


added specificity at 99% sensitivity

@msmolens Can you test / review this? Please change anything you need to, and merge when it looks good.
Once Docker rebuilds, rerun the scoring as we discussed.
Thanks.

LGTM


Improve Performance of Segment Replacement

This patch improves the performance of segment
replacement (by average colors within the segments),
used in Superpixels and segment_voronoi().
The new method is up to around 7x faster, more for
smaller images and more segments. It can be slightly
slower in some cases for large images (512x512 and
larger).
This change seems to improve the overall performance
of Superpixels by a factor of around 1.1x to 1.4x
(more for smaller images).
It improves the overall performance of
segment_voronoi() by about 1.1x to 2.0x and can
reach much higher improvements in the case of very few
segments that have to be replaced.
Note that segment_voronoi() is used in Voronoi.
Added functions:

imgaug.augmenters.segmentation.replace_segments_

Added classes:

imgaug.testutils.temporary_constants (context)

Codecov Report

Merging #640 into master will decrease coverage by 0.02%.
The diff coverage is 93.75%.

@@            Coverage Diff             @@
##           master     #640      +/-   ##
==========================================
- Coverage   96.37%   96.35%   -0.02%
==========================================
  Files          41       41
  Lines       14683    14720      +37
==========================================
+ Hits        14150    14183      +33
- Misses        533      537       +4


fix: Improve wait conditions for Python interpreter activation before running the installer

This pull request introduces an improvement in the wait condition that precedes the running of the Python installer CLI. Previously we waited one second before attempting to run the installer command, however it's possible that the user's terminal was still not ready.
In this fix, we ensure that the CLI command won't be emitted until sendText is called or up to a maximum of five seconds have passed. The sendText function would be called by the required Python extension to activate the user's chosen Python interpreter.
This change aims to minimize potential race conditions and unexpected behaviors that may occur when the Python environment has not been completely activated before the installer runs.
This issue was first noticed on Mac and this change has been confirmed to resolve the issue.

@dustinbyrne what is a good way to test this manually? What project should I use and what kind of python environment should I install? I haven't done very much work with Python.

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

v0.95.1
GitHub release

Your semantic-release bot :package::rocket:


mautrix-signal: init at v0.1.1

The script wrapping python -m mautrix_signal was inspired by
the gunicorn script in powerdns-admin
@ma27 or @nyanloutre (maintaners of the mautrix-telegram package): would you like to be maintainers too?

Motivation for this change
Things done

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

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)

(doesn't crash immediately)

[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I've tested this up to the point of writing a config file. I suspect it won't operate usefully until someone packages signald https://gitlab.com/signald/signald/

Result of nixpkgs-review pr 119285 at ba9fa9a3 run on x86_64-linux 1

1 package built successfully:

mautrix-signal

1 suggestion:

warning: python-include-tests
Consider adding a checkPhase for tests, or if not feasible, pythonImportsCheck.
Near pkgs/servers/mautrix-signal/default.nix:54:0:
   |
54 |     description = "A Matrix-Signal puppeting bridge";
   | ^

First of all, can you please remove at least my name from the commit before merging this? The problem is that as soon as somebody rebases master or cherry-picks the commit to somewhere else or whatever, I get a notification.
While I'm happy to help if there are problems, I guess I have to decline the offer since I'm not using signal (or the bridge) and don't think that this will change soon, but thanks for asking! :)

First of all, can you please remove at least my name from the commit before merging this? The problem is that as soon as somebody rebases master or cherry-picks the commit to somewhere else or whatever, I get a notification.

Oops! done.

While I'm happy to help if there are problems, I guess I have to decline the offer since I'm not using signal (or the bridge) and don't think that this will change soon, but thanks for asking! :)

:+1:

Thanks for the review, I've applied the changes.
I've also added signald which is necessary to use mautrix-signal.
I have a couple of modules set up to use these packages but I think I'll leave them to another PR

Possible to merge this, not sure what to do about the bintray thing.

The build requires the .git directory sadly
On Fri, 23 Apr 2021, 03:37 Sandro, @.***> wrote:

@SuperSandro2000 commented on this pull request.
In pkgs/applications/networking/instant-messengers/signald/default.nix
https://github.com/NixOS/nixpkgs/pull/119285#discussion_r618686396:

@@ -0,0 +1,87 @@
+{ lib, stdenv, fetchurl, fetchgit, jre, coreutils, gradle_6, git, perl
+, makeWrapper }:

+let

pname = "signald";

version = "0.13.1";

This package uses the .git directory

src = fetchgit {

Cna this use fetchFromGitLab?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NixOS/nixpkgs/pull/119285#pullrequestreview-642598412,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGRJXDI4XWBVF3V3F33T5LTKB3IDANCNFSM422PWIYQ
.

The build requires the .git directory sadly

Can we patch this? fetchFromGitLab should also support leaveDotGit.

fetchFromGitLab should also support leaveDotGit

I don't think it does sadly.
It's not impossible to patch, but it's just exchanging cheap computer time for my valuable human time.

it's just exchanging cheap computer time for my valuable human time.

We still don't want to be more wasteful than we need to be.


modified models/scanvi.py for symmetrical KL option

I am unsure whether this is needed anymore. Closed it for now.


[Bridge] Checkpoint

Fix Edge-459
Description
This PR is a base PR for Bridge Checkpoint, checked out from bridge branch.
TODO for Phase 1

[x] Create bridge/checkpoint package bridge
[x] Generate new Checkpoint at the beginning of every epoch
[x] Create Transport for Checkpoint Gossip
[x] Sign generated Checkpoint and gossip it
[x] Show logs once collected 2/3+ signatures

Changes include

[ ] Bugfix (non-breaking change that solves an issue)
[ ] Hotfix (change that solves an urgent issue, and requires immediate attention)
[x] New feature (non-breaking change that adds functionality)
[ ] Breaking change (change that is not backwards-compatible and/or changes current functionality)

Breaking changes
Please complete this section if any breaking changes have been made, otherwise delete it
Checklist

[x] I have assigned this PR to myself
[x] I have added at least 1 reviewer
[x] I have added the relevant labels
[ ] I have updated the official documentation
[ ] I have added sufficient documentation in code

Testing

[ ] I have tested this code with the official test suite
[ ] I have tested this code manually

Manual tests
Please complete this section if you ran manual tests for this functionality, otherwise delete it
Documentation update
Please link the documentation update PR in this section if it's present, otherwise delete it
Additional comments
Please post additional comments in this section if you have them, otherwise delete it

Closing this PR as it's been archived.


HHH-5932 Test and fix on 4.2

See HHH-5932. Fix an issue when enabling a filter on an HQL query that contains a literal string starting with a colon.
The fix is to remove strings open and close quote from the symbols used to split the SQL string into tokens. This doesn’t break any existing test, but worries me in that the open and close quote were clearly voluntarily added.

Closing, since we're not making changes to 4.2.x unless absolutely necessary.  #805 is sufficient.

I have reproduced this error trying to create a query native hat contains a literal string starting with a colon., having HQL filters enable
Query query = entitymanager.createNativeQuery(queryString))
query.list()
But it runs good if I injected the entityManager without the filter enabled.
I used hibernate 3.6.10.Final


aldente: 1.28.2 -> 1.28.4

Description of changes
aldente: 1.28.2 -> 1.28.4
https://github.com/AppHouseKitchen/AlDente-Charge-Limiter/releases/tag/1.28.4

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[x] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 343497 run on aarch64-darwin 1

1 package built:

aldente


Create SECURITY.md

For Issue: #PLACE_ISSUE_NUMBER_HERE
Fixes:

Any repository please fix of any negative effects
Additions:

Checklist

[ ] Ensured there is an open issue for your PR
[ ] Added comments to additions
[ ] Followed common formatting conventions for the contribution language
[ ] Tested code to ensure original features are working

Select one:

[ ] Ensured you are the contributer assigned to the Issue for this PR
[ ] Commented for ownership of an OPEN issue where no one is assigned or has yet asked to be assigned

Screenshots

I don't think a SECURITY.md is required for this project, because we don't provide multiple versions of the website or anything with that require extra security considerations or precautions. However, good luck with the hacks on your phone 😉