local reference table overflow (max=512) error

when I call duktape.set ("someName" , interface.class, interface instance );
local reference table overflow (max=512) error occured
interface method has 40 methods.
and if I set method count 30, the error is not occured.
so I'm call set two interface.class.
the first interface has 20 methods. and second interfacde has 20 method.
Is it a bug?

error position is
DuktapeContext.cpp
void DuktapeContext::set(JNIEnv *env, jstring name, jobject object, jobjectArray methods) {
....
....
for( jsize i=0; i< numMethods; ++i){
...
//here
const JString methodName(env, static_cast(env->CallObjectMethod(method, getName)));
....
}
...

Yes, this is a bug.  Thanks for the report!

Execuse me..
I'm making a apps which using duktape android^^;...
Can I know that your team made a plan to fix this bug?

A fix is in progress: https://github.com/square/duktape-android/pull/97.  I'll try to get a release out in the next week or two.

Fixed.

Thank you for it.
Now it works very well~


Cannot save multiple times w/remote window

Type: Bug
While remote connected into an Ubuntu Server 16.04 VM on VirtualBox, if I save a file multiple times, any attempts past the first one fail to process (no indication of the save, checking the contents of the file show no change). At first, I believed this was due to the save commands not being triggered, but upon trying to terminate the connection, VS Code prompts to wait while text files are saved (which never happens). I am SSH'd in as root, and the directory/file permissions are 777, so it doesn't seem to be a permission issue. If I restart VS Code with a new connection instance, I can then again save once.
Steps I reproduce with:

Connect to my VM
Open a file
Make a change, save it successfully
Make another change, save it unsuccessfully

VS Code version: Code 1.71.2 (74b1f979648cc44d385a2286793c226e611f59e7, 2022-09-14T21:03:37.738Z)
OS version: Windows_NT x64 10.0.22000
Modes:
Sandboxed: No
Remote OS version: Linux x64 4.4.00001 (a slightly modified 4.4 version for class)

System Info

Item
Value

CPUs
Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (8 x 1498)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: enabledvideo_encode: enabledvulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
undefined

Memory (System)
15.60GB (5.51GB free)

Process Argv
-n --crash-reporter-id 240c5682-f852-46af-959d-0bc2e4b98d97

Screen Reader
no

VM
0%

Item
Value

Remote
SSH: <IP_ADDRESS>

OS
Linux x64 4.4.00001

CPUs
Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz (4 x 0)

Memory (System)
3.86GB (3.59GB free)

VM
100%

Extensions (11)

Extension
Author (truncated)
Version

better-cpp-syntax
jef
1.15.19

jupyter-keymap
ms-
1.0.0

remote-containers
ms-
0.251.0

remote-ssh
ms-
0.84.0

remote-ssh-edit
ms-
0.82.0

remote-wsl
ms-
0.66.3

material-theme
zhu
3.15.5

cmake-tools
ms-
1.12.27

cpptools
ms-
1.12.4

cpptools-extension-pack
ms-
1.3.0

cmake
twx
0.0.17

(2 theme extensions excluded)

A/B Experiments
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492cf:30256860
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30557514
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyonecf:30548226
2144e591:30553903
40g7c324:30573242

I believe this is a configuration problem with your setup and not something VSCode can fix or has an issue with, but maybe see if the issue is different when using VSCode insiders?
Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

A configuration issue in the VM, nothing VSCode can do. The dialog you posted indicates that really saving is stuck, so could it be a problem with the underlying file system?

I'm not too knowledgeable about what could be misconfigured, but in the meantime I've transitioned into using WinSCP and its editing capabilities without error. Is it possible that the vscode server itself is misconfigured somehow, instead of the client? There's a massive sense of confusion, because at one point I was using VS Code Remote Development without issue on the same VM.

That is hard to say, how do you configure WinSCP now to make edits, is VSCode still involved?

I use VS Code as the editor for remote files on WinSCP. When I open those files, they are edited locally in a temp file before being synchronized by WinSCP.

Yeah understood, that goes through an entire different way compared to remote development. How are you connected to the remote when using VSCode with remote development, SSH?

I use SFTP with WinSCP and SSH with VS Code Remote.

Maybe @roblourens could follow up.

Follow up on what? Sorry, I have no clue what would be going on, I don't really think it would be an ssh-specific issue.

Are there any steps that are recommended for me to isolate this issue?
As far as I know, at every step I've left things "as is" in regards to configuration. The configuration for my local SSH client, the remote SSH server, the remote file system, VS Code and the VS Code remote server should be as expected.  Even if this issue somehow doesn't root from within VS Code itself, it would be useful to identify the cause so that functionality is guaranteed or a public solution is available for others who find themselves in similar circumstances

@kornelharm Have you got a solution? I meet exactly the same saving problem. I can save a file successfully once, but failed next.

@kornelharm Have you got a solution? I meet exactly the same saving problem. I can save a file successfully once, but failed next.
No I have not. I fully transitioned into using WinSCP to access remote files, and then I edit them remotely with VS Code for WinSCP to synchronize. I would still be interested in trying to isolate the issue, but I definitely still need something or someone to point me in the right direction.

We closed this issue because we don't plan to address it in the foreseeable future. If you disagree and feel that this issue is crucial: we are happy to listen and to reconsider.
If you wonder what we are up to, please see our roadmap and issue reporting guidelines.
Thanks for your understanding, and happy coding!


怎么安装使用？

This code was implemented with Python 3.8 and PyTorch 1.13.0. You can install all the requirements via:
pip install -r requirements.txt
没有看见requirements.txt文件，并且看见model文件夹内有mmseg，是否需要安装mmseg？

Thanks for pointing out! We have added the file!


to support .ts extension

Hi! 👋
Firstly, thanks for your work on this project! 🙂
Today I used patch-package to patch<EMAIL_ADDRESS>for the project I'm working on.

Here is the diff that solved my problem:
diff --git a/node_modules/hardhat-abi-exporter/index.d.ts b/node_modules/hardhat-abi-exporter/index.d.ts
index 7b44cdf..baeb105 100644
--- a/node_modules/hardhat-abi-exporter/index.d.ts
+++ b/node_modules/hardhat-abi-exporter/index.d.ts
@@ -12,6 +12,8 @@ interface AbiExporterUserConfig {
   format?: string,
   filter?: (abiElement: any, index: number, abi: any, fullyQualifiedName: string) => boolean,
   rename?: (sourceName: string, contractName: string) => string,
+  fileExtension?: '.json' | '.ts',
+  renameABI?: (name: string) => string,
 }

 declare module 'hardhat/types/config' {
@@ -32,6 +34,8 @@ declare module 'hardhat/types/config' {
       format?: string,
       filter: (abiElement: any, index: number, abi: any, fullyQualifiedName: string) => boolean,
       rename: (sourceName: string, contractName: string) => string,
+      fileExtension?: '.json' | '.ts',
+      renameABI?: (name: string) => string,
     }[]
   }
 }
diff --git a/node_modules/hardhat-abi-exporter/tasks/export_abi.js b/node_modules/hardhat-abi-exporter/tasks/export_abi.js
index d0c6ccd..9fdaa4c 100644
--- a/node_modules/hardhat-abi-exporter/tasks/export_abi.js
+++ b/node_modules/hardhat-abi-exporter/tasks/export_abi.js
@@ -61,9 +61,9 @@ subtask(
     const destination = path.resolve(
       outputDirectory,
       config.rename(sourceName, contractName)
-    ) + '.json';
+    ) + config.fileExtension || '.json';

-    outputData.push({ abi, destination });
+    outputData.push({ abi, destination, contractName });
   }));

   outputData.reduce(function (acc, { destination }) {
@@ -79,8 +79,15 @@ subtask(
     await hre.run('clear-abi-group', { path: config.path });
   }

-  await Promise.all(outputData.map(async function ({ abi, destination }) {
+  await Promise.all(outputData.map(async function ({ abi, destination, contractName }) {
     await fs.promises.mkdir(path.dirname(destination), { recursive: true });
-    await fs.promises.writeFile(destination, `${JSON.stringify(abi, null, config.spacing)}\n`, { flag: 'w' });
+    let fileContent = '';
+    if (config.fileExtension === '.ts') {
+      const name = config.renameABI ? config.renameABI(contractName) : `ABI_${contractName}`;
+      fileContent = `const ${name} = ${JSON.stringify(abi, null, config.spacing)} as const;\nexport default ${name};\n`;
+    } else {
+      fileContent = `${JSON.stringify(abi, null, config.spacing)}\n`;
+    }
+    await fs.promises.writeFile(destination, fileContent, { flag: 'w' });
   }));
 });

This issue body was partially generated by patch-package.

Why do you need to store ABI files with a .ts extension?

Why do you need to store ABI files with a .ts extension?

https://wagmi.sh/docs/typescript
Unfortunately [TypeScript doesn't support importing JSON as const](https://github.com/microsoft/TypeScript/issues/32063). If you have ABIs in .json files, you should convert the files to .ts, export the ABIs, and add const assertions to them. (We have future integrations planned for Foundry/Hardhat users to make this easier.)

@ItsNickBarry  Or set
beforeAbiSaveFunction: (abiContent, fileName)=>/ do something / return { abiContent, fileName}
so that users can freely modify the content, file name and suffix of the last output abi file. Thank you for your attention~~

Is Typechain not suitable for this?
I might be willing to add the fileExtension option, but only if it's really necessary.

I didn't find the right types to use Typechain on wagmi

Thank you for the suggestion @biluochun, but I think this feature falls outside of the scope of the plugin.  My suggestion for anyone who needs it would be to implement a task like the following:
// override the ABI export task defined by the plugin
task('export-abi').setAction(async (args, hre, runSuper) => {
  // call super to avoid overwriting funtionality
  await runSuper();

  // TODO: delete "abi_ts" directory if it exists

  // TODO: create empty "abi_ts" directory

  // TODO: read all files in "abi" directory (or whatever directory is determined by hre.config.abiExporter.path)

  // TODO: apply transformations to files and write to "abi_ts" directory
});

this would be great to work with wagmi (used by almost all top dapps)


variance of subtyping

TypeScript Version:  3.6

Search Terms:
subtyping invariant covariant

Read and write
variance

read and write
invariance

readonly
covariance

writeonly
contravariance

Code

interface a {
  foo?: string
}

interface b extends a {
  foo: string // subtype of string | undefined
}

declare const b: b;

const a: a = b;

a.foo = undefined; // now b has property `foo:undefined`
console.log(b.foo);

Expected behavior:
Can't extends when  property foo of b isn't readonly
Actual behavior:
It has no warning and no error
Playground Link:
Related Issues:

https://github.com/microsoft/TypeScript/issues/18770

A not-so-great workaround at the moment is to just make all your properties readonly always, and treat everything as immutable.
I personally do that but it's unnerving that I can slip up and make a mistake, and not have the compiler tell me about it

I don't think we're likely to make extends sound with respect to variance. Many crusty old OO codebases violate it.
Intersection behaves better, so I'd recommend that over extends if you care about variance.

Doesn't TS add new breaking behavior behind a flag?
Anything that relies on unsound extends can turn it off, and everyone else that wants more safety, and are masochistic can use the new flag

I'm curious if anyone's run into issues in real code arising from this issue.


Failed promise result not visible in callback

When dealing with callbacks, it is possible to access the env::promise_result context.
This call returns an enum:
pub enum PromiseResult {
    NotReady,
    Successful(Vec<[u8]>),
    Failed,
}

Per the documentation, NotReady is never returned in the current version.
Successful is returned when the cross contract call is executed without panicking and the return value of the call is present in the enum variant as a vector of bytes.
However, when a transaction fails (Failed variant) there is no information regarding the error type returned, all that is accessible through the smart contract is the information that the call has failed.
I know that it is perfectly possible to fetch the panic message by checking the transaction from outside of the blockchain. Is there a way to also check the panic message during the execution of the callback? So that the contract can have different reactions based on the error message?

Unfortunately, this data is not accessible by the protocol/runtime. I'm not sure the context of why it isn't, I assume it's to keep a small data footprint not to have to transfer the failure message data across shards by default, but that's just a guess.
@bowenwang1996 do you have context on this, or would know who does?

Any news on this? Our protocol interacts a lot with other contracts and not having access to what kind of error we are at leads to more complexity in the contract

Protocol community chat is the best place to discuss it. This issue is not actionable without a protocol change, so I am closing this issue. Feel free to discuss and open a tracking issue on nearcore repo.


OB server behind a hostname

I switched from amazon AWS to rpi3 which sits behind a dynamic address. I'm using dynamic DNS so a hostname points to this dynamic IP(s) and the DNS updates every time my IP changes. This works without any issues.
The problem is (I think) that instead of my hostname, my IP address is stored in DHT which causes issues the moment my rpi3 gets a new IP address (and user's DHT still points to the old one). This causes me to appear offline for duosear.ch and some others.
I'd suggest a hostname is stored in DHT instead of IP when the server runs on one. This information is available in server settings.

I'm marking this as Won't Fix because we won't be addressing this in the 1.x code.


Correction for raw affiliation CEREA, Ãcole des Ponts , EDF R&D, Marne-la-VallÃ©e, France

Correction needed for raw affiliation CEREA, Ãcole des Ponts , EDF R&D, Marne-la-VallÃ©e, France
raw_affiliation_name: CEREA, Ãcole des Ponts , EDF R&D, Marne-la-VallÃ©e, France
new_rors: 03a84yw54;03wb8xz10
previous_rors: 03a84yw54
works_examples: W4360866234;W4388568819
contact: e66cfefb3311ec3144fe9eebba0ce46c:2dc623a0dae4ac393c5f2eae6b1c6e @ recherche.gouv.fr

This issue was accepted and ingested by the OpenAlex team on 2024-10-09. The new affiliations should be visible within the next 7 days.


Expose docker identifier/name

After marathon starts a docker task, there is no information from marathon that can be used to identify the corresponding docker container started by the task. It'd be useful if marathon can expose that information.

Why can't you use taskID as container name? Why do you need to create some other ID for docker container? hostname will not help at all, because if you have 250 containers on the host, and you need to go through all of them just to get a match with one, I doubt it's a proper way to do this. The best option would be to have direct match between TaskID from marathon and container name. No over engineering with some extra IDs, no headache of matching containers to tasks, plain and simple.

Unfortunately Mesos uses the docker name for its own accounting purpose as there is no way to tag or add metadata to a particular container in Docker. Which means Mesos needs to control the docker container name, and it's not the task id. We're thinking about providing these information back as TaskStatus in the future.

Out of curiosity, what is the use case to control the container name by Mesos? what is the difference between task id and mesos container name if both values are unique?

+1; some way to correlate container name and mesos task ID would help correlate log sources e.g. using docker with syslog log-driver, the docker id is emitted along with each log statement.  A way to correlate that with the mesos task would be helpful.

+1 would be useful

@onorua I think one challenge is that in mesos it's possible to run many task in a container (mesos native or docker) which means that a single taskid can't be used for the docker name.
I can't remember off the top of my head whether mesos sets the docker name to the executor id or whether it sets it to some other container id.  If it's set to the executor id, that information can be used to correlate the container with the task.

For cluster type deployments, when multiple containers need to talk to each other, each container should have easy name tag and other containers should be able to identify and connect using the name of the container.

@ajaybhatnagar That's probably a larger story that exceeds the scope of this issue ;) If you do make feature suggestions, it would also help if you were more specific, elaborated on use cases, possible syntax etc. But please in a separate issue.

+1

+1
Such feature is very important for container monitoring

+1

+1

Could also add mesos/marathon labels to docker labels.

+1

+1

Note: This issue has been migrated to https://jira.mesosphere.com/browse/MARATHON-4031. For more information see https://groups.google.com/forum/#!topic/marathon-framework/khtvf-ifnp8.


No audio from Raspberry Pi 4 on 3.5mm jack

Raspberry Pi 4 with 8Gb RAM
balenaOS 4.0.26+rev1
No DAC
I installed balenasound and didn't change any settings.
I can connect to the device with any of Bluetooth / Airplay / Spotify Connect.
With AUDIO_OUTPUT set to the default of AUTO
Sound is only available over HDMI, can't get anything to play from 3.5mm jack
After changing AUDIO_OUPUT to RPI_HEADPHONES
No sound plays from the 3.5mm jack
I have done a hardware check that the 3.5mm jack is working correctly under Raspbian
Suggestions please?

https://forums.balena.io/t/raspberry-pi-4-no-3-5mm-sound-using-balenasound/356827

Thanks for the links @dotzeno
Removing the overlay fixed the issue for me
I had already searched but not found the right pages
What I did find was the balenasound support page which says for troubleshooting support to create an issue on Github
https://balena-labs-projects.github.io/balena-sound/support#contact-us


configurability of SpannerOptions and SessionPoolOptions as properties

Expose the options as properties available on SpannerOptions, it is very important to have a look at SessionPoolOptions in particular as large use cases will want fine tuneability on these knobs.
Please discuss here first the details before jumping into implementation.

should this be M4?


the get_configuration() method throws an error

Because
Maybe this should be an issue on clams-python, but the app crashes with the following error:
<class 'TypeError'>: ClamsApp.get_configuration() takes 1 positional argument but 2 were given

  File "/Applications/ADDED/venv/clams/app-swt/lib/python3.11/site-packages/clams/restify/__init__.py", line 146, in post
    return self.json_to_response(self.cla.annotate(raw_data, **self.annotate_param_caster.cast(raw_params)))
                                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/Applications/ADDED/venv/clams/app-swt/lib/python3.11/site-packages/clams/app/__init__.py", line 116, in annotate
    annotated = self._annotate(mmif, **runtime_params)
                ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

  File "/Users/marc/Desktop/projects/clams/code/clamsproject/apps/app-swt-detection/app.py", line 46, in _annotate
    parameters = self.get_configuration(parameters)
                 ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^

This was with code at the top of the develop branch. For now I have restored and adapted the previous way of reading configuration settings and updating them with app parameters.
Done when
No response
Additional context
No response

this was my bad, but it should be a trivial fix. https://sdk.clams.ai/autodoc/clams.app.html#clams.app.ClamsApp.get_configuration just make parameters into a kwarg.

Ah, good. One potential source of trouble there is that we have competing settings in the config file and the parameters, must think that through a little bit.

Largely there are model_configs and stitcher_configs. Once classifier and stitcher are separated into their own modules/classes, there won't be competing conditions (or at least much less of them).
Eventually I'd like to have is just to get rid of classifier.yml at all, and to directly re-use trainer.yml for Classifier class and to configure stitcher from the runtime params (passed via CLI or POST call).

Maybe three kinds: model, classifier and stitching.
Model:

img_enc_name, num_epochs, num_splits, num_layers, dropouts
block_guids_train, block_guids_valid
max_input_length
pos_enc_name, pos_unit, pos_enc_dim

Classifier:

model_file, model_config_file
sample_rate

Stitching

minimum_frame_score, minimum_timeframe_score, minimum_frame_count

There indeed is redundancy between trainer.yml and the model config file. But we may need to live with that. If we do not save the the trainer.yml information with the model config then we cannot change trainer.yml unless we associated the model with a version of trainer.yml. Maybe simply copying the trainer config when creating the classifier model would be the easiest.
I do like the idea of choosing for parameters via CLI and POST request wherever we can, probably removing the need for classifier.yml.

I misread your message a bit I think.
Anyway, what I am suggesting is:

Directly copy the trainer configuration with the model
Use POST/CLI parameters where we can, hopefully getting rid of classifier.yml
Figure out something for the model file and model config file.

Fixed in https://github.com/clamsproject/app-swt-detection/commit/0ab78e0c3eda4a601aee021cbf9b05eb77249a5b.
Keeping this open because we the question on how best to do the configuration is still open..

Nah, closing it anyway, configuration seems stable.


LuaTable to XML

Is there any built-in function in this module that converts a Lua table to an XML string?
(sorry if I missed that in the documentation)

There is no such function, but I may add it in the next few days.

Thanks, yeah, that would be helpful.

Thanks @jonathanpoelen , this is very helpful.


It should not be possible to project away columns of a key in a map in parquet-thrift

That wouldn't make much sense when re-assembling the map, there could be unexpected key collisions
Reporter: Alex Levenson / @isnotinvain
Assignee: Alex Levenson / @isnotinvain
Note: This issue was originally created as PARQUET-275. Please see the migration documentation for further details.

Alex Levenson / @isnotinvain:
For that matter, projecting in sets shouldn't be allowed either...

Alex Levenson / @isnotinvain:
@julienledem @tsdeng what do you think?

Alex Levenson / @isnotinvain:
It could work for a set, if the user understands what they're doing, eg:
projecting a Set[User] down to say, Set[User.country], would yield a (smaller) set of the unique countries in the original Set.

Alex Levenson / @isnotinvain:
thought the types would still be weird, eg Set[User], one per unique country.

Tim / @tsdeng:
agree that the user should not be able to project out part of the key

Alex Levenson / @isnotinvain:
Looks like I even documented that the key can't be partially projected here: https://github.com/apache/parquet-mr/blame/b8aae90d333094da4afd65ad5f5eb13854811f28/parquet_cascading.md#L115
but it's not enforced. I'm going to include this fix in https://github.com/apache/parquet-mr/pull/189

Julien Le Dem / @julienledem:
Projecting inside a set should not change the number of elements in the set.
When projecting, we just mean that we are not going to access the other fields, but that does not change the data content.
It is an optimization for not loading the data that we are not going to access.
In the case of the Map api, you would be able to list entries when part of the key is projected but you would not be able to get something by key obviously as that requires having the entire key.
same thing for a set, you would not be able to use add or contains but you would be able to iterate and access the fields that are not projected out.
But to support this in parquet-thrift we need to be able to use our own implementation of Set or Map so the current implementation would have to change.
class ProjectedSet extends Set {
  add() { throw ...}
  contains() { throw ...}
  iterator() { return iterator }
}
class ProjectedMap extends Map {
   put() { throw ...}
  contains() { throw ...}
  get() { throw ...} // if keys are partially projected, otherwise its ok
  entries() { return entries }
}

as a short term solution, restricting projection or just adding back columns in those cases seems reasonable.

Alex Levenson / @isnotinvain:
Yeah so, the way I'd rather deal with that is for us to stop returning thrift objects, and instead return something with a schema that matches the projection. In the case of maps + sets, we would instead return lists.
Returning sets that can blow up when used as a set doesn't seem great, but yes it could work. The more we do things like this though the more I feel that it'd be better to return a different kind of object other than thrift.


fix: check if middlewareMode enabled before start dev server (close #2094)

fixed by https://github.com/vitejs/vite/pull/2101, closing this


fixed the problem with refreshing both the user feeds

the refresh functionality was not working before, now its reseting the feed store and refetches the posts on the specific feed accordingly
problems are:

upon refreshing, the feed goes to the initial state then after the posts are loaded it reflects
if there is no posts on a feed, the user does have to ability to refresh that feed and is stuck on the initial state until restarted

related 8703dddb0a627db7c871f297e839fdb20bdd63e6

yep I have that

fixed with the new version


Update README.md

Minor typo.

Hey Kaan
It should be 0 to 1, as I normalize (and unnormalize during sampling) it to -1 to 1 here

hey luciddrains,
I believe 'torch.randn' generates zero mean random numbers, no?

@kaanaksit haha yea, but it is just for testing, not real image data
i see why you are confused though

https://github.com/lucidrains/denoising-diffusion-pytorch/commit/e872ec361881dc74cfda48e3d76ff0148b63e1f4

Perhaps removing the comment may help your readers . Btw, thank you for making this code base available, huge help to folks out there!

Closing the pull request


pep.py mysql error :(

I'm run the pep.py and write config.ini.
but pep.py say's
raise errorclass(errno, errorvalue)

pymysql.err.ProgrammingError: (1146, "Table 'osu.bancho_settings' doesn't exist")
Please help me

You may not have created the database running migrations.php
You may have misconfigured pep.py

I'll close this issue because, as stated in the README, NO SUPPORT IS PROVIDED FOR ANYTHING THAT HAS TO DEAL WITH THIS CODE. USE AT YOUR OWN AND SOLE RISK.


Support any zero-sized type in trivial

Currently, even setting explicit #[trivial] doesn't allow anything except PhantomData / PhantomPinned / ().
However, #[repr(transparent)] allows custom arbitrary zero-sized fields alongside the primary non-zero-sized one, and I believe explicit annotation should be enough to tell ref-cast to check size_of instead of limiting to a specific set of types.

This would not be sound for zero sized types that are not constructible at an arbitrary location, such as https://docs.rs/ffi-opaque/2.0.1/ffi_opaque/macro.opaque.html or the Ref types from https://docs.rs/foreign-types/0.5.0/foreign_types/index.html.

Hmm not sure I understand the problematic case from the first glance, will need to look at your links deeper. Are you saying it's possible to use #[repr(transparent)] in Rust on structs that are not, in fact, safely transparent?
If that's the case, this feels like something that should be expanded upon in nomicon and possibly produce an error (a warning?) in Rust itself.

I don't know what you mean by "safely transparent".
If you have been treating anything with size 0 (and presumably alignment 1) as being trivially constructible at any memory address, that is definitely not sound.
An FFI example:
// opaque type (size=0, align=1, ffi-safe, !Send, !Sync, !Unpin)
#[repr(C)]
pub struct Thing {
    _opaque: [u8; 0],
    _marker: PhantomData<(*mut u8, PhantomPinned)>,
}

impl Thing {
    fn new() -> Malloc<Self> {
        extern "C" {
            fn thing_create() -> *mut Thing;
        }
        unsafe { Malloc(thing_create()) }
    }

    fn frob(&self) {
        extern "C" {
            fn thing_frob(this: *const Thing);
        }
        unsafe { thing_frob(self) }
    }
}

struct Malloc<T>(*mut T);

impl<T> Deref for Malloc<T> {
    type Target = T;
    fn deref(&self) -> &Self::Target {
        unsafe { &*self.0 }
    }
}

impl<T> Drop for Malloc<T> {
    fn drop(&mut self) {
        extern "C" {
            fn free(ptr: *mut c_void);
        }
        unsafe { free(self.0.cast()) }
    }
}

// some other crate

#[repr(transparent)]
struct Struct {
    asdf: String,
    thing: lib::Thing,
}

let asdf = String::new();
let ref_cast = unsafe { &*(&asdf as *const String as *const Struct) };
ref_cast.frob(); // RIP

Even easier UB example:
enum Void {}

#[repr(transparent)]
struct Struct {
    asdf: String,
    thing: Void,
}

let asdf = String::new();
let ref_cast = unsafe { &*(&asdf as *const String as *const Struct) };
match ref_cast.thing {}

Right, I see what you mean.
In my case I don't care about either uninhabited types or FFI, I just want to implement ref-cast for own zero-sized structs without having to additionally wrap them into PhantomData.
What I meant in the issue description is that in this crate we need to mark those fields with explicit attribute (#[trivial]) anyway, seems like enough of an opt-in to avoid accidentally passing one of the wrong types. If you think it's not obvious enough for something this risky, maybe trivial(unsafe) would do?

Besides the feature request, but I'd probably also argue that in the FFI example the unsafety is in the "safe" wrappers of the unsafe methods rather than in the ref-cast - personally I prefer exposing smart pointers in such scenarios, as in, I'd implement methods directly on ThingPtr rather than an arbitrary &Thing. I know it's a common representation of dynamically-sized FFI structs though, so that ship has sailed.

What I meant in the issue description is that in this crate we need to mark those fields with explicit attribute (#[trivial]) anyway, seems like enough of an opt-in to avoid accidentally passing one of the wrong types. If you think it's not obvious enough for something this risky, maybe #[trivial(unsafe)] would do?

Actually... how about T: Default && size_of() == 0 && align_of() == 1?
That would safely cover any constructible types - including PhantomData, PhantomPinned and most of 3rd-party zero-sized structs which usually do derive Default - while still safely excluding any "zero sized types that are not constructible at an arbitrary location"?
Am I missing an edge case where that wouldn't be enough?

A T: Default bound is not sufficient to soundly instantiate a &T without having called T::default(). For example stuff like safe bindings to C++ singletons (https://github.com/facebook/folly/blob/v2<IP_ADDRESS>/folly/init/Init.h).
// must be called at most once
void init();

// requires init to have been called
void frob();

use std::sync::Once;

#[derive(Copy, Clone)]
#[non_exhaustive]
pub struct ProofOfStaticInit;

// called once from main, then all subsequent library calls are zero overhead.
//
//     fn main() {
//         let init = ProofOfStaticInit::default();
//         for _i in 0..=u64::MAX {
//             lib::frob(init);
//         }
//     }
impl Default for ProofOfStaticInit {
    fn default() -> Self {
        extern "C" {
            fn init();
        }
        static ONCE: Once = Once::new();
        ONCE.call_once(|| unsafe { init() });
        ProofOfStaticInit
    }
}

pub fn frob(_init: ProofOfStaticInit) {
    extern "C" {
        fn frob();
    }
    unsafe { frob() };
}

#[repr(transparent)]
struct Struct {
    asdf: String,
    init: ProofOfStaticInit,
}

let asdf = String::new();
let ref_cast = unsafe { &*(&asdf as *const String as *const Struct) };
lib::frob(*ref_cast.init); // RIP

...wow. Okay, I give up 😅


How do I change the default color of the selected row of a datagrid?

Hi, can you tell me how do I change the default purple color of a selected row of a datagrid?

I think you need to replace the resource for the AccentBrush

Hi rsuter,
can u please tell me where i need to change the accentbrush resource
thanks,
nitesh

Did anyone have any luck in archieving this?


organize protobuf files

Issue #297
To make the protobufs use relative imports, I did the following.  If you
regenerate the protobuf files then you will have to run the last command
to get the relative imports to work correctly.
cd presidio-analyzer/presidio_analyzer
mkdir -p protobuf_models
mv *_pb2*.py protobuf_models/
cd protobuf_models
sed -i -E 's/^import.*_pb2/from . \0/' *.py

Signed-off-by: David Pollack<EMAIL_ADDRESS>

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

thanks @dhpollack we will review this PR soon.
Thanks for your contribution!

The manual step is not ideal but it's a long standing issue with Google and how they generate the files. You can see the link in the issue that's attached to this PR. Instead of adding this functionality they insist that it's not need despite the hundreds of messages in the issue.

/azp run

@dhpollack If this fix: https://github.com/protocolbuffers/protobuf/issues/1491#issuecomment-542398041 would work, it's easier to maintain and doesn't require some post processing. WDYT?

@dhpollack If this fix: protocolbuffers/protobuf#1491 (comment) would work, it's easier to maintain and doesn't require some post processing. WDYT?

The comment after that one looks more fool-proof.  I'll give that a try.

/azp run

It looks like the build is failing due to failure downloading the spacy models, even though all the tests are passing.  It would be nice if you used the small spacy model as a default, so one can test presidio without having to download and build 800MB large model.  Also, the English spacy models aren't actually "requirements" if someone were to use this library on non-English data.

We have an issue with the build agent which is currently being fixed (see https://github.com/microsoft/presidio/pull/300)
The reason we're using the big spaCy model is because it has NER capabilities which the small one doesn't, and some of our tests validate the output of the spaCy model.  The current deployment is coupled with the English version and supporting deployments of other models requires some changes to the deployment pipeline.

/azp run

Hi @dhpollack,
We have fixed the build issue. can you fix the merge conflicts and we will merge this

@eladiw I rebased on master and then fixed the imports in the test.  I think it should work now.

/azp run


cursor will jump to the bottom after format on save/paste

Vscode editing json has wrong behavior
Hello! Editing json in vscode will cause wrong behavior
Error 1:
After enabling  "editor.formatOnSave": true,
Trigger Ctrl+S and the cursor will jump to the bottom
https://github.com/microsoft/vscode/assets/54253524/288ba573-0a0e-4412-83dd-4b0f8cde2099
Error 2:
After enabling  "editor.formatOnPaste": true,
After using the mouse to paste the code, the cursor will randomly jump to the bottom
https://github.com/microsoft/vscode/assets/54253524/61f65670-b7af-4701-8ab2-3c0e0537fc72
The above error has existed for a very long time. It was originally thought that it would be fixed, but it has not been fixed until now. . .
Windows 10
VSCode 1.81
Associated extensions:
Prettier

The same issue applies only to a JSON file.
Works fine when the editor.formatOnSave is set to false on settings.json

This happens because formatting emits a single edit that replaces the entire text with the formatted text.
Because in your case the file is very big, VS Code does not try minimize the edit by diffing it against the replaced text.
I think for formatting where just whitespace changes, we could implement a more efficient algorithm to minimze the edit.
Alternatively, the formatting provider should not provide a single edit, but smaller edits.


Use of new 'PauseActivity' and 'WaitPause' in a UWP suspend step of app lifecycle?

I see that the newest release includes a doc cpp_client_telemetry/docs/use-after-free.md that mentions new methods for eliminating race conditions during app shutdown.  I'm wondering if you have also seen the same race condition during the suspend process of a UWP app (https://docs.microsoft.com/en-us/windows/uwp/launch-resume/app-lifecycle)
The app I work on sometimes sees crashes due to the suspend process taking too long so the OS kills the app.  The doc added states the most common crash is a read-dereference, but if you have seen issues with this SDK due to perhaps unsent telemetry messages during an app suspend, maybe these new methods could help us avoid some of these crashes.

The app I work on sometimes sees crashes due to the suspend process taking too long so the OS kills the app.

The app I work on sometimes sees crashes due to the suspend process taking too long so the OS kills the app.

Do you mean the app is taking a long time to suspend, possibly because it is still transmission the telemetry events, and so the OS kills the app?

Make sure when you suspend, you do not perform FlushAndTeardown. You must also request deferral from UWP while you run PauseTransmission+Flush and ResumeTransmission after. This historically worked well. This is for C#, but C++ should have the same APIs available:
https://github.com/microsoft/cpp_client_telemetry/blob/fcd3b5219abf25c958c9621f64105a9f6a5122f4/examples/cs/SampleCsUWP/App.xaml.cs#L239
Adjust the code though to avoid upload, because it'd be best to PauseTransmission rather than resume when you are being suspended. Resuming and trying to upload - results in non-deterministic network I/O delay, whereas flushing on disk with paused transmission should generally be fast.

@Jamatth - do you have any further questions, or this can be closed?


community: minor changes sambanova integration

- **Description:** fix: variable names in root validator not allowing pass credentials as named parameters in llm instancing,  also added sambanova's sambaverse and sambastudio llms to __init__.py for module import

Hi @baskaryan ,  could you please take a look to this PR


Use case: sending token as HTTP header?

When updating parts of the page using JavaScript, rather than having to parse the response for form tags and extract the input elements, it would be really useful to have the tokens provided by HTTP tokens.

Are there any security implications of doing this?
How would responses containing multiple forms be handled?

HTTP headers can already pass multiple data. See HTTP Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/webp,*/*;q=0.8.

Do you mean the server providing a token using a custom header, or the client submitting the token in a custom header?  OWASP discuss (and endorse, albeit they list it as lowest in order of strength of defense) on their CSRF page.  a X-CSRF-TOKEN header would seem to be an obvious choice.
If you meant a way for javascript to get the token in the first place without parsing one or more forms: Either a custom cookie set by the server, or (rather more simply - and as adopted by laravel): the library could set a <meta name="csrf-token" content="xyz123"/> tag in the page head.

Was mainly asking if there was any implications in using a header for this rather than putting it in the body - some use cases I can think of would be really useful using headers, such as when doing ajax requests.

Sorry, I wasn't clear.  When you say "using headers for this", do you mean for receiving a token from the server or submitting a token with a request?

Yeah there are cases where a developer may want to submit form data without using an actual form in the HTML... to retrieve and send the correct tokens we could parse the page for the form's csrf, use the meta tag as in #33, or read response headers.

Carry on the implementation from #44 - response header should be comma separated.

Tracked in phpgt/webengine#572


Hi Bored APE Club

Title of your project
Hi Bored APE Club
Short (1-2 sentence) description of your project
Hi Bored APE Club
Link to your project
https://www.hbape.club
Live on Testnet
No
If your project is live on one of Taiko's testnets, please provide evidence of that here (eg. links, screenshots). If your project is NOT live, please provide your plan for integration here.
https://www.hbape.club
Upload a quality logo to your project


Freeze Computer

a keep having a problem where the victims moves there mouse. I have a few trojans that freeze there computer but still could u make it like freeze there computer on there side so u can snoop around?

YES im t-450 btw


SDK Review Meeting - Tracking Azure Communication Services

This meeting was created by LaDonna Quinn.

It will be used to Track the conversation in the informational Session for the Azure Communication Services Service.

Detailed meeting information and documents provided can be accessed here

Cancelled by: LaDonna Quinn


Minor mistake in section 3.5.2

In section 3.5.2 (Formal specification of equal and mismatch), the first sentence reads: "Using predicate equal_range we can formulate the specification of equal..." . Given that EqualRanges (and not equal_range) was the predicate defined just above this section, I believe you meant: "Using predicate EqualRanges ...".
BTW: I was going to submit a patch but I did not find the files that are used to generate the pdf. This is the reason why I did not submit a patch.

Yes, you are right. We will fix this. Thanks a lot!

You are welcome. Another very minor thing: Under Listing 3.23, it reads: "The loop invariant not_foundis ... ". It needs a space between 'not_found' and 'is'.
I plan on going through the whole book but it will take me a while because I can only do it in my spare time. If the source code of the pdf is in latex and you make it available, I could submit patches if I run into anything else.

Again thanks a lot. I fixed it in our development version. We will provide a new release soon.
So you shouldn't be surprised when your gtihub handle appears in he changes section!-)
I hope it doesn't bother your that we do not put the latex source on GitHub...

Regarding "EqualRanges": This problem occurred because we had a command "\equalrange" that expands to something like "equal_range" and a command "\equalranges" that expanded to "EqualRanges".
We have change the latter command (and similar commands) to "\EqualRanges" to avoid this confusion in future.

No worries. If you guys don't want to publish the latex source, that's fine. This is a great book and a great introduction to ACSL. The first time I tried Frama-C/ACSL was many years ago and I did not get very far. I think it will be a lot easier this time around because I can use your book as a reference. Thank you guys at Fraunhofer for putting it together.

Thank you for your nice comments. If you have time I would like to know more about your interest in Frama-C/ACSL. Perhaps, it's better when you write me an email<EMAIL_ADDRESS>

I see that the problem was fixed in 15.1.2. Therefore, I am closing this issue. Cheers


RestSharp Upgrade to 105.2

RestSharp unfortunately made a breaking change in their minor release. This PR addresses #46 and upgrades the dependency to 105.2.3 or greater.

@Giovani-Brady Please review. Thanks!

@paulirwin
approved. please merge when able.


[BUG]where is the default place to save the model?

where is the default place to download the model when use model on GUI?

Looking at this code:
_MODEL_DIR_DEFAULT = pathlib.Path.home().joinpath('.cellpose', 'models')
So I think on windows this points to c:\Users and on Linux its /home/<username/

tks，i found it


adds support for function-serializers

Support for conditional fields by accessing the Hapi request object.

Closing in favor of #3


A question about memory initialization.

Hi,
I am a bit confused about how we save memory states in DNC. To be more specific, at the starting point of training, we have to initialize the memory with no doubt (fill all 0s in code). Having finished the training process, I think the memory values should be saved for testing usages. But it turns out that you reset the memory hidden states to be 0s AGAIN! (just as the erase part of dnc/memory.py,Line 69-75).
Could you please give me some explanations about this? Thank you in advance! Really need your help.

Hey there. I think the reason behind erasing the memory after each training is that the point is for the network to use the memory. If you let memory uninitialised, the consequences are not explored in the paper. I think I remember commenting the line out and trying DNCs for translation. I thought maybe if after training if I were to take the memory cells and see if they have developed any sort of a map (like a dictionary?) by looking at their matrix of dot products but got nothing.
But you're right, not re-initialising memory has not been tried in the paper and hence this implementation, but it can most certainly be tried.


Update Doc Release to Per-Build Branches

So essentially, the issue this PR resolves can be seen in a release like this one
git can't figure out how to apply the patch update of this
---
title: Azure Core HTTP client library for JavaScript
keywords: Azure, javascript, SDK, API, @azure/core-http,
author: maggiepint
ms.author: magpint
ms.date: 06/05/2020
ms.topic: article
ms.prod: azure
ms.technology: azure
ms.devlang: javascript
ms.service:
---

to this
---
title: Azure Core HTTP client library for JavaScript
keywords: Azure, JavaScript, SDK, API, core, @azure/core-http
author: maggiepint
ms.author: magpint
ms.date: 05/10/2020
ms.topic: article
ms.prod: azure
ms.technology: azure
ms.devlang: JavaScript
ms.service: core
---

When it tries, we see
error: patch failed: docs-ref-services/core-http-readme.md:1
error: docs-ref-services/core-http-readme.md: patch does not apply

Sure I can manually correct this, but right now those readme changes from the patch not applying disappear! Given that the PR submissions will be on the fork, the docs validation builds won't be triggered for each new PR branch.
We're talking about 40 validation builds over a longer period of a release week. Should be fine. I'll take the additional docs builds if it keeps my manual effort lower. I don't want to manually release readmes this release.
Edit: the reason I chose just buildId to extend the branch name and did not include packagename  is because we won't update the same readme twice in the same release. We're safe.
@Azure/azure-sdk-eng

Is it safe to assume the line that won't apply is the keyword line? Is there a way to make those keywords span lines? If so we might be able to get this merging to work automatically.
Even though this might allow for all the PR's to get created we will still have an issue with dealing with the merge conflicts across PR's which will still cause manual intervention.
If all else fails there is another possibility which is to not apply a patch on failure but instead rerun the script on failure after the branch has been updated. That would require some refactoring to accomplish but it isn't out of question.


Bug Report: Deny-Private-DNS-Zones.json

Describe the bug
The https://github.com/Azure/Enterprise-Scale/blob/main/src/resources/Microsoft.Authorization/policyDefinitions/Deny-Private-DNS-Zones.json policy definition contains 2 square brackets causing the policy deployment to fail:

Steps to reproduce

Navigate https://github.com/Azure/Enterprise-Scale/blob/main/src/resources/Microsoft.Authorization/policyDefinitions/Deny-Private-DNS-Zones.json
Deploy using using the preferred technology (Azure Portal, Terraform ….)

PS. How are the json definitions validated on your end, before being pushed to the repo ?

Hey @mezzofix, Thanks for the issue.
This is actually correct as we have documented here: https://github.com/Azure/Enterprise-Scale/wiki/ALZ-Contribution-Guide#:~:text=When working within,normal %2C['
This is because of the way the ALZ portal experience works and the various loops and nested deployments we have to do some ARM escaping.
You will need to remove one of the ['s when deploying manually outside of any of the ALZ implementation options
Thanks
Jack

@jtracey93 Thank you for such quick response! However, I'm a bit confused. I'm also using Terraform modules, and never had to do any ARM escaping. What am I missing ?

We handle this as part of the Terraform & Bicep modules but at the source (here) we need the escaping to support the portal deployment option


Statistics announcement unpublisher

Add a rake task to unpublish statistics announcements. They don't have any workflow, so after discussion with @marksheldonGDS we agreed the best way to handle it would be to delete the records and register a GONE route for them.
Here are a couple of tickets with details of announcements that need unpublishing:

https://www.pivotaltracker.com/story/show/89716404
https://www.pivotaltracker.com/story/show/89094234

Very minor points in the tests, but otherwise looks good! :+1:

Tests updated. If someone wants to give this a "good to merge" I'll hit the button once it goes green.

:shipit:


Build(deps-dev): Bump @types/node from 18.7.17 to 18.7.18 (#4044)

Pull request opened by the merge tool on behalf of #4044

Merged in 46143301bd6e4d520f2d106a2454b070cc61b7c0


[Feature] Sorting progress indicator

Sorting of large data freezes the app, maybe add a popup displaying 'Sorting...' or something?

I've been thinking about this.
Currently, the way I sort a large list without UI freezing is
Each step of merge sort is properly divided and processed asynchronously.
If anyone knows a better way, I'd appreciate it if you could leave it here.

I think we should left backend server doing this sort. Because database have many functions deal with it better and dont block main thread of UI.
... Maybe we need a parameter which called onlineFilter:  to call a API to backend and return the list.

@thegioiso
Server-side sorting and filtering is possible using pagination.
https://pluto.weblaze.dev/rows-from-server-side
The problem is sorting and filtering large amounts of data on the client-side.
in the first way,
To use Isolate, code such as worker.js must be added in the web.
in the second way,
When processing sort, giving a delay of 1 microsecond for every N rows minimizes freezing of the UI.
I've tested both methods.
The first method is inconvenient for web because the user needs to add code such as worker.js.
The second method is simpler from the user's point of view, but it doesn't completely eliminate UI freezing, as it takes a little longer to sort and doesn't run in isolation.

... I mostly create UI on Flutter web so the first method maybe be a bad Breaking changes. But its will be fine if the package can create everything automatic when run flutter pub get.

@thegioiso
There is an onSorted callback.
PlutoGrid(
  onSorted: (event) => print(event),
)

@MRKDaGods onSorted can callback when sort button is clicked, and you can call gridStateManager?.setShowLoading(true); for loading widget in grid. I dont have big data to test this callback, maybe you can call a timer function to set the loading off after your sorting processed.

@MRKDaGods   you can set a loading widget when sorting button is clicked with this callback. I dont have a big data to test so maybe you will need timer or other sync function to turn off loading after sorting is processed.

@thegioiso There is an onSorted callback.
PlutoGrid(
  onSorted: (event) => print(event),
  // Execute the following, the internal sort is ignored
  // when the sort button is clicked, and sorting can be done manually through the onSorted callback.
  // However, it is convenient to use the server-side pagination mentioned in the link above.
  // Otherwise, you'll have to manually handle post-sorting.
  onLoaded: (event) => event.stateManager.setSortOnlyEvent(true),
)

This is exactly what I needed.
Now I can easily display a popup notifying the user that sorting is in progress for big datasets and meanwhile handle the sorting myself.
Thank you both!


Movie Search App

Please Assign me under GSSOC'22
@swapnilsparsh

I want to work on this under GSSOC2022. Here is my discord profile DHANANJOY DEY | Contributor#7903 can you assign me?


Update direct-routing-plan-media-bypass.md

Line 152 Typo fixes https://github.com/MicrosoftDocs/OfficeDocs-SkypeForBusiness/issues/1967

@CarolynRowe Hi Carolyn,  changes look correct. Could you please check and merge? Thanks!


Use deterministic ECDSA with PSA interface

Partially solves #157 , only for Mbed TLS with PSA interface.
This PR make t_cose to use deterministic version of ECDSA.
PSA_ALG_DETERMINISTIC_ECDSA macro is used instead of PSA_ALG_ECDSA if the option PSA_WANT_ALG_DETERMINISTIC_ECDSA is enabled.
By default MBEDTLS_ECDSA_DETERMINISTIC is defined, so that it is also enabled here.
The example codes one_step_sign_example() and two_step_sign_example() in examples/t_cose_basic_example_psa.c will produce the same COSE_Sign1 message below, maybe also in your environment.
$ ./t_cose_basic_example_psa
Encoded payload (size = 97): 0 (success)
Made EC key with curve prime256v1: 0 (success)
Initialized t_cose and configured signing key
Finished signing: 0 (success)
Completed COSE_Sign1 message:
    172 bytes
    d2 84 43 a1 01 26 a0 58
    61 a6 69 42 65 69 6e 67
    54 79 70 65 68 48 75 6d
    61 6e 6f 69 64 68 47 72
    65 65 74 69 6e 67 70 57
    65 20 63 6f 6d 65 20 69
    6e 20 70 65 61 63 65 68
    41 72 6d 43 6f 75 6e 74
    02 69 48 65 61 64 43 6f
    75 6e 74 01 69 42 72 61
    69 6e 53 69 7a 65 66 6d
    65 64 69 75 6d 6b 44 72
    69 6e 6b 73 57 61 74 65
    72 f5 58 40 8a 8c 4a 42
    91 e2 6e 7f bd 25 41 69
    f5 5f a4 07 1a 3c 7e 70
    8e 45 66 04 5d 2b 07 b9
    b1 4c 18 2d 35 bd 26 37
    3b 27 79 23 cf 10 60 b9
    9b f2 53 83 25 ae 18 70
    bc 96 92 9a 3b b4 ba fb
    79 a0 b3 de

Hi Ken,
This one is not very straightforward for me and will take a lot of analysis, probably some changes and some documentation before merging.
My understanding is that non-deterministic is bigger and more complex in the crypto library, but is secure even if you have a bad random number generator.  If you have a good random number generator you don't need this and it is a waste of code in the crypto library.
These days random number generators are very good, so it is not often needed.
I am also very cautious about #ifdefs like this because they can make the code a mess and add to test fan out. If this is merged it should be put in the the test fan out in tdv.
Basically, I don't want to work on this unless it is really really important because there is a huge amount of other work to do. Is it really really important?

Users who want to use deterministic version of ECDSA can replace PSA_ALG_ECDSA to PSA_ALG_DETERMINISTIC_ECDSA .


Allow options to be updated

Is your feature request related to a problem? Please describe.
Currently, you can only to pass options.headers on first render.
This makes it impossible to 'update' things such as the token, if required.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
setOptions() to update the stored options:
eg:
setOptions({
...options,
headers: {
  Authorization: 'Bearer anUpdatedToken`
}

Describe alternatives you've considered
Right now, I have to wrap my component in another component that async gets the bearer token.

Additional context
Add any other context or screenshots about the feature request here.

@davecarlson thank you for opening this issue. Will look into it as soon as possible.

Thanks ! In our use case, the tokens are only valid 30 seconds, and thus need to be fetched onClick ideally ( a new token each time )

@davecarlson would the proposed PR work for you?

@all-contributors please add @davecarlson for ideas!


fan-only mode changes the target temperature to 0°C

When I set climate:fan-only mode in homeassistant it changes the target temperature to 0°C
(even if target min=16°C and max=30°C).
Later when I set climate:cool mode, the target temperature is set to 0°C, then in a second it raises to 18°C, but the last used cooling target temp is lost (eg. 24°C).
When using remote control this doesn’t happen.
Wired remote doesn’t make any changes in the target temperature when using fan mode (it just doesn’t display the target temp).
Later when I set climate:cool mode, the last used cooling target temperature remains (eg. 24°C).

I found that this is probably due to the wired controller.
When set to fan_only mode (no matter if by HA or wired ctrl) then the controller set the target temp to 0.
Later if set to cool mode things are different:

if set to cool by HA - cooling start with target temp=0°C immediately changed to 18°C
if set to cool by wired ctrl - cooling start with the last known target temperature used for cooling which is probably memorised in the controller

Log fron esphome with my comments:
`[17:51:51][I][app:100]: ESPHome version 2024.5.5 compiled on Jun 11 2024, 16:33:12
[17:51:51][C][wifi:580]: WiFi:
[17:51:52][C][wifi:408]:   Local MAC: xxxxx
[17:51:52][C][wifi:413]:   SSID: [redacted]
[17:51:52][C][wifi:416]:   IP Address: <IP_ADDRESS>
[17:51:52][C][wifi:420]:   BSSID: [redacted]
[17:51:52][C][wifi:421]:   Hostname: 'fujitsu'
[17:51:52][C][wifi:423]:   Signal strength: -63 dB ▂▄▆█
[17:51:52][C][wifi:427]:   Channel: 10
[17:51:52][C][wifi:428]:   Subnet: <IP_ADDRESS>
[17:51:52][C][wifi:429]:   Gateway: <IP_ADDRESS>
[17:51:52][C][wifi:430]:   DNS1: <IP_ADDRESS>
[17:51:52][C][wifi:431]:   DNS2: <IP_ADDRESS>
[17:51:52][C][logger:185]: Logger:
[17:51:52][C][logger:186]:   Level: DEBUG
[17:51:52][C][logger:188]:   Log Baud Rate: 115200
[17:51:52][C][logger:189]:   Hardware UART: UART0
[17:51:52][C][captive_portal:088]: Captive Portal:
[17:51:52][C][web_server:173]: Web Server:
[17:51:52][C][web_server:174]:   Address: fujitsu.local:80
[17:51:52][C][mdns:115]: mDNS:
[17:51:52][C][mdns:116]:   Hostname: fujitsu
[17:51:52][C][ota:096]: Over-The-Air Updates:
[17:51:52][C][ota:097]:   Address: fujitsu.local:3232
[17:51:53][C][ota:103]:   OTA version: 2.
[17:51:53][C][api:144]:   Using noise encryption: NO
[17:51:54][D][api:102]: Accepted <IP_ADDRESS>
[17:51:54][D][api.connection:1321]: Home Assistant 2024.6.1 (<IP_ADDRESS>): Connected successfully
[17:52:14][D][climate:011]: 'Fujitsu' - Setting
[17:52:14][D][climate:040]:   Target Temperature: 24.00
[17:52:14][D][fuji:234]: Fuji setting temperature 24.000000
[17:52:15][D][fuji:145]: ctrl temp 24 vs my temp 4194303
[17:52:15][D][fuji:201]: publishing state
---start---
[17:52:15][D][climate:396]: 'Fujitsu' - Sending state:
[17:52:15][D][climate:399]:   Mode: FAN_ONLY
[17:52:15][D][climate:404]:   Fan Mode: AUTO
[17:52:15][D][climate:419]:   Current Temperature: 27.00°C
[17:52:15][D][climate:425]:   Target Temperature: 24.00°C
[17:52:16][D][fuji:145]: ctrl temp 0 vs my temp 4194303
[17:52:16][D][fuji:201]: publishing state
[17:52:16][D][climate:396]: 'Fujitsu' - Sending state:
[17:52:16][D][climate:399]:   Mode: FAN_ONLY
[17:52:16][D][climate:404]:   Fan Mode: AUTO
[17:52:16][D][climate:419]:   Current Temperature: 27.00°C
[17:52:16][D][climate:425]:   Target Temperature: 0.00°C
---HA set to cool---
[17:55:27][D][climate:011]: 'Fujitsu' - Setting
[17:55:27][D][climate:015]:   Mode: COOL
[17:55:27][D][fuji:213]: Fuji setting mode 2
[17:55:28][D][fuji:155]: ctrl mode 2 vs my mode 4
[17:55:28][D][fuji:201]: publishing state
[17:55:28][D][climate:396]: 'Fujitsu' - Sending state:
[17:55:28][D][climate:399]:   Mode: COOL
[17:55:28][D][climate:404]:   Fan Mode: AUTO
[17:55:28][D][climate:419]:   Current Temperature: 27.00°C
[17:55:28][D][climate:425]:   Target Temperature: 0.00°C
[17:55:29][D][fuji:145]: ctrl temp 18 vs my temp 4194303
[17:55:29][D][fuji:201]: publishing state
[17:55:29][D][climate:396]: 'Fujitsu' - Sending state:
[17:55:29][D][climate:399]:   Mode: COOL
[17:55:29][D][climate:404]:   Fan Mode: AUTO
[17:55:29][D][climate:419]:   Current Temperature: 27.00°C
[17:55:29][D][climate:425]:   Target Temperature: 18.00°C
--HA set target temp to 22---
[17:55:31][D][climate:011]: 'Fujitsu' - Setting
[17:55:31][D][climate:040]:   Target Temperature: 22.00
[17:55:31][D][fuji:234]: Fuji setting temperature 22.000000
[17:55:32][D][fuji:145]: ctrl temp 22 vs my temp 4194303
[17:55:32][D][fuji:201]: publishing state
[17:55:32][D][climate:396]: 'Fujitsu' - Sending state:
[17:55:32][D][climate:399]:   Mode: COOL
[17:55:32][D][climate:404]:   Fan Mode: AUTO
[17:55:32][D][climate:419]:   Current Temperature: 27.00°C
[17:55:32][D][climate:425]:   Target Temperature: 22.00°C
---HA set to fan only mode---
[17:56:40][D][climate:011]: 'Fujitsu' - Setting
[17:56:40][D][climate:015]:   Mode: FAN_ONLY
[17:56:40][D][fuji:213]: Fuji setting mode 4
[17:56:41][D][fuji:155]: ctrl mode 4 vs my mode 2
[17:56:41][D][fuji:201]: publishing state
[17:56:41][D][climate:396]: 'Fujitsu' - Sending state:
[17:56:41][D][climate:399]:   Mode: FAN_ONLY
[17:56:41][D][climate:404]:   Fan Mode: AUTO
[17:56:41][D][climate:419]:   Current Temperature: 27.00°C
[17:56:41][D][climate:425]:   Target Temperature: 22.00°C
[17:56:42][D][fuji:145]: ctrl temp 0 vs my temp 4194303
--my temp changed to 0 by the code to match ctrl temp--
[17:56:42][D][fuji:201]: publishing state
[17:56:42][D][climate:396]: 'Fujitsu' - Sending state:
[17:56:42][D][climate:399]:   Mode: FAN_ONLY
[17:56:42][D][climate:404]:   Fan Mode: AUTO
[17:56:42][D][climate:419]:   Current Temperature: 27.00°C
[17:56:42][D][climate:425]:   Target Temperature: 0.00°C
--HA set hvacmode to off--
[18:04:48][D][fuji:193]: Controller turned off AC, adding mode change to call
[18:04:48][D][fuji:201]: publishing state
[18:04:48][D][climate:396]: 'Fujitsu' - Sending state:
[18:04:48][D][climate:399]:   Mode: OFF
[18:04:48][D][climate:404]:   Fan Mode: AUTO
[18:04:48][D][climate:419]:   Current Temperature: 27.00°C
[18:04:48][D][climate:425]:   Target Temperature: 0.00°C
--wired controller set to on and to cool--
[18:06:28][D][fuji:145]: ctrl temp 22 vs my temp 4194303
[18:06:28][D][fuji:155]: ctrl mode 2 vs my mode 0
[18:06:28][D][fuji:201]: publishing state
[18:06:28][D][climate:396]: 'Fujitsu' - Sending state:
[18:06:28][D][climate:399]:   Mode: COOL
[18:06:28][D][climate:404]:   Fan Mode: AUTO
[18:06:28][D][climate:419]:   Current Temperature: 27.00°C
[18:06:28][D][climate:425]:   Target Temperature: 22.00°C
--wired controller set to fan only--
[18:08:57][D][fuji:145]: ctrl temp 0 vs my temp 4194303
[18:08:57][D][fuji:155]: ctrl mode 4 vs my mode 2
[18:08:57][D][fuji:201]: publishing state
[18:08:57][D][climate:396]: 'Fujitsu' - Sending state:
[18:08:57][D][climate:399]:   Mode: FAN_ONLY
[18:08:57][D][climate:404]:   Fan Mode: AUTO
[18:08:57][D][climate:419]:   Current Temperature: 27.00°C
[18:08:57][D][climate:425]:   Target Temperature: 0.00°C
--wired controller set to cool--
[18:10:30][D][fuji:145]: ctrl temp 22 vs my temp 4194303
[18:10:30][D][fuji:155]: ctrl mode 2 vs my mode 4
[18:10:30][D][fuji:201]: publishing state
[18:10:30][D][climate:396]: 'Fujitsu' - Sending state:
[18:10:30][D][climate:399]:   Mode: COOL
[18:10:30][D][climate:404]:   Fan Mode: AUTO
[18:10:30][D][climate:419]:   Current Temperature: 27.00°C
[18:10:30][D][climate:425]:   Target Temperature: 22.00°C`

Log from esphome:
[17:51:51][I][app:100]: ESPHome version 2024.5.5 compiled on Jun 11 2024, 16:33:12 [17:51:51][C][wifi:580]: WiFi: [17:51:52][C][wifi:408]:   Local MAC: xxxxx [17:51:52][C][wifi:413]:   SSID: [redacted] [17:51:52][C][wifi:416]:   IP Address: <IP_ADDRESS> [17:51:52][C][wifi:420]:   BSSID: [redacted] [17:51:52][C][wifi:421]:   Hostname: 'fujitsu' [17:51:52][C][wifi:423]:   Signal strength: -63 dB ▂▄▆█ [17:51:52][C][wifi:427]:   Channel: 10 [17:51:52][C][wifi:428]:   Subnet: <IP_ADDRESS> [17:51:52][C][wifi:429]:   Gateway: <IP_ADDRESS> [17:51:52][C][wifi:430]:   DNS1: <IP_ADDRESS> [17:51:52][C][wifi:431]:   DNS2: <IP_ADDRESS> [17:51:52][C][logger:185]: Logger: [17:51:52][C][logger:186]:   Level: DEBUG [17:51:52][C][logger:188]:   Log Baud Rate: 115200 [17:51:52][C][logger:189]:   Hardware UART: UART0 [17:51:52][C][captive_portal:088]: Captive Portal: [17:51:52][C][web_server:173]: Web Server: [17:51:52][C][web_server:174]:   Address: fujitsu.local:80 [17:51:52][C][mdns:115]: mDNS: [17:51:52][C][mdns:116]:   Hostname: fujitsu [17:51:52][C][ota:096]: Over-The-Air Updates: [17:51:52][C][ota:097]:   Address: fujitsu.local:3232 [17:51:53][C][ota:103]:   OTA version: 2. [17:51:53][C][api:144]:   Using noise encryption: NO [17:51:54][D][api:102]: Accepted <IP_ADDRESS> [17:51:54][D][api.connection:1321]: Home Assistant 2024.6.1 (<IP_ADDRESS>): Connected successfully [17:52:14][D][climate:011]: 'Fujitsu' - Setting [17:52:14][D][climate:040]:   Target Temperature: 24.00 [17:52:14][D][fuji:234]: Fuji setting temperature 24.000000 [17:52:15][D][fuji:145]: ctrl temp 24 vs my temp 4194303 [17:52:15][D][fuji:201]: publishing state ---start--- [17:52:15][D][climate:396]: 'Fujitsu' - Sending state: [17:52:15][D][climate:399]:   Mode: FAN_ONLY [17:52:15][D][climate:404]:   Fan Mode: AUTO [17:52:15][D][climate:419]:   Current Temperature: 27.00°C [17:52:15][D][climate:425]:   Target Temperature: 24.00°C [17:52:16][D][fuji:145]: ctrl temp 0 vs my temp 4194303 [17:52:16][D][fuji:201]: publishing state [17:52:16][D][climate:396]: 'Fujitsu' - Sending state: [17:52:16][D][climate:399]:   Mode: FAN_ONLY [17:52:16][D][climate:404]:   Fan Mode: AUTO [17:52:16][D][climate:419]:   Current Temperature: 27.00°C [17:52:16][D][climate:425]:   Target Temperature: 0.00°C ---HA set to cool--- [17:55:27][D][climate:011]: 'Fujitsu' - Setting [17:55:27][D][climate:015]:   Mode: COOL [17:55:27][D][fuji:213]: Fuji setting mode 2 [17:55:28][D][fuji:155]: ctrl mode 2 vs my mode 4 [17:55:28][D][fuji:201]: publishing state [17:55:28][D][climate:396]: 'Fujitsu' - Sending state: [17:55:28][D][climate:399]:   Mode: COOL [17:55:28][D][climate:404]:   Fan Mode: AUTO [17:55:28][D][climate:419]:   Current Temperature: 27.00°C [17:55:28][D][climate:425]:   Target Temperature: 0.00°C [17:55:29][D][fuji:145]: ctrl temp 18 vs my temp 4194303 [17:55:29][D][fuji:201]: publishing state [17:55:29][D][climate:396]: 'Fujitsu' - Sending state: [17:55:29][D][climate:399]:   Mode: COOL [17:55:29][D][climate:404]:   Fan Mode: AUTO [17:55:29][D][climate:419]:   Current Temperature: 27.00°C [17:55:29][D][climate:425]:   Target Temperature: 18.00°C --HA set target t to 22--- [17:55:31][D][climate:011]: 'Fujitsu' - Setting [17:55:31][D][climate:040]:   Target Temperature: 22.00 [17:55:31][D][fuji:234]: Fuji setting temperature 22.000000 [17:55:32][D][fuji:145]: ctrl temp 22 vs my temp 4194303 [17:55:32][D][fuji:201]: publishing state [17:55:32][D][climate:396]: 'Fujitsu' - Sending state: [17:55:32][D][climate:399]:   Mode: COOL [17:55:32][D][climate:404]:   Fan Mode: AUTO [17:55:32][D][climate:419]:   Current Temperature: 27.00°C [17:55:32][D][climate:425]:   Target Temperature: 22.00°C ---HA set to fan only mode--- [17:56:40][D][climate:011]: 'Fujitsu' - Setting [17:56:40][D][climate:015]:   Mode: FAN_ONLY [17:56:40][D][fuji:213]: Fuji setting mode 4 [17:56:41][D][fuji:155]: ctrl mode 4 vs my mode 2 [17:56:41][D][fuji:201]: publishing state [17:56:41][D][climate:396]: 'Fujitsu' - Sending state: [17:56:41][D][climate:399]:   Mode: FAN_ONLY [17:56:41][D][climate:404]:   Fan Mode: AUTO [17:56:41][D][climate:419]:   Current Temperature: 27.00°C [17:56:41][D][climate:425]:   Target Temperature: 22.00°C [17:56:42][D][fuji:145]: ctrl temp 0 vs my temp 4194303 [17:56:42][D][fuji:201]: publishing state [17:56:42][D][climate:396]: 'Fujitsu' - Sending state: [17:56:42][D][climate:399]:   Mode: FAN_ONLY [17:56:42][D][climate:404]:   Fan Mode: AUTO [17:56:42][D][climate:419]:   Current Temperature: 27.00°C [17:56:42][D][climate:425]:   Target Temperature: 0.00°C --HA set hvacmode to off-- [18:04:48][D][fuji:193]: Controller turned off AC, adding mode change to call [18:04:48][D][fuji:201]: publishing state [18:04:48][D][climate:396]: 'Fujitsu' - Sending state: [18:04:48][D][climate:399]:   Mode: OFF [18:04:48][D][climate:404]:   Fan Mode: AUTO [18:04:48][D][climate:419]:   Current Temperature: 27.00°C [18:04:48][D][climate:425]:   Target Temperature: 0.00°C --wired controller set to on and to cool-- [18:06:28][D][fuji:145]: ctrl temp 22 vs my temp 4194303 [18:06:28][D][fuji:155]: ctrl mode 2 vs my mode 0 [18:06:28][D][fuji:201]: publishing state [18:06:28][D][climate:396]: 'Fujitsu' - Sending state: [18:06:28][D][climate:399]:   Mode: COOL [18:06:28][D][climate:404]:   Fan Mode: AUTO [18:06:28][D][climate:419]:   Current Temperature: 27.00°C [18:06:28][D][climate:425]:   Target Temperature: 22.00°C --wired controller set to fan only-- [18:08:57][D][fuji:145]: ctrl temp 0 vs my temp 4194303 [18:08:57][D][fuji:155]: ctrl mode 4 vs my mode 2 [18:08:57][D][fuji:201]: publishing state [18:08:57][D][climate:396]: 'Fujitsu' - Sending state: [18:08:57][D][climate:399]:   Mode: FAN_ONLY [18:08:57][D][climate:404]:   Fan Mode: AUTO [18:08:57][D][climate:419]:   Current Temperature: 27.00°C [18:08:57][D][climate:425]:   Target Temperature: 0.00°C --**wired controller** set to cool-- [18:10:30][D][fuji:145]: ctrl temp 22 vs my temp 4194303 [18:10:30][D][fuji:155]: ctrl mode 2 vs my mode 4 [18:10:30][D][fuji:201]: publishing state [18:10:30][D][climate:396]: 'Fujitsu' - Sending state: [18:10:30][D][climate:399]:   Mode: COOL [18:10:30][D][climate:404]:   Fan Mode: AUTO [18:10:30][D][climate:419]:   Current Temperature: 27.00°C [18:10:30][D][climate:425]:   Target Temperature: 22.00°C

Log from esphome:
`[17:51:51][I][app:100]: ESPHome version 2024.5.5 compiled on Jun 11 2024, 16:33:12
[17:51:51][C][wifi:580]: WiFi:
[17:51:52][C][wifi:408]:   Local MAC: xxxxx
[17:51:52][C][wifi:413]:   SSID: [redacted]
[17:51:52][C][wifi:416]:   IP Address: <IP_ADDRESS>
[17:51:52][C][wifi:420]:   BSSID: [redacted]
[17:51:52][C][wifi:421]:   Hostname: 'fujitsu'
[17:51:52][C][wifi:423]:   Signal strength: -63 dB ▂▄▆█
[17:51:52][C][wifi:427]:   Channel: 10
[17:51:52][C][wifi:428]:   Subnet: <IP_ADDRESS>
[17:51:52][C][wifi:429]:   Gateway: <IP_ADDRESS>
[17:51:52][C][wifi:430]:   DNS1: <IP_ADDRESS>
[17:51:52][C][wifi:431]:   DNS2: <IP_ADDRESS>
[17:51:52][C][logger:185]: Logger:
[17:51:52][C][logger:186]:   Level: DEBUG
[17:51:52][C][logger:188]:   Log Baud Rate: 115200
[17:51:52][C][logger:189]:   Hardware UART: UART0
[17:51:52][C][captive_portal:088]: Captive Portal:
[17:51:52][C][web_server:173]: Web Server:
[17:51:52][C][web_server:174]:   Address: fujitsu.local:80
[17:51:52][C][mdns:115]: mDNS:
[17:51:52][C][mdns:116]:   Hostname: fujitsu
[17:51:52][C][ota:096]: Over-The-Air Updates:
[17:51:52][C][ota:097]:   Address: fujitsu.local:3232
[17:51:53][C][ota:103]:   OTA version: 2.
[17:51:53][C][api:144]:   Using noise encryption: NO
[17:51:54][D][api:102]: Accepted <IP_ADDRESS>
[17:51:54][D][api.connection:1321]: Home Assistant 2024.6.1 (<IP_ADDRESS>): Connected successfully
[17:52:14][D][climate:011]: 'Fujitsu' - Setting
[17:52:14][D][climate:040]:   Target Temperature: 24.00
[17:52:14][D][fuji:234]: Fuji setting temperature 24.000000
[17:52:15][D][fuji:145]: ctrl temp 24 vs my temp 4194303
[17:52:15][D][fuji:201]: publishing state
---start---
[17:52:15][D][climate:396]: 'Fujitsu' - Sending state:
[17:52:15][D][climate:399]:   Mode: FAN_ONLY
[17:52:15][D][climate:404]:   Fan Mode: AUTO
[17:52:15][D][climate:419]:   Current Temperature: 27.00°C
[17:52:15][D][climate:425]:   Target Temperature: 24.00°C
[17:52:16][D][fuji:145]: ctrl temp 0 vs my temp 4194303
[17:52:16][D][fuji:201]: publishing state
[17:52:16][D][climate:396]: 'Fujitsu' - Sending state:
[17:52:16][D][climate:399]:   Mode: FAN_ONLY
[17:52:16][D][climate:404]:   Fan Mode: AUTO
[17:52:16][D][climate:419]:   Current Temperature: 27.00°C
[17:52:16][D][climate:425]:   Target Temperature: 0.00°C
---HA set to cool---
[17:55:27][D][climate:011]: 'Fujitsu' - Setting
[17:55:27][D][climate:015]:   Mode: COOL
[17:55:27][D][fuji:213]: Fuji setting mode 2
[17:55:28][D][fuji:155]: ctrl mode 2 vs my mode 4
[17:55:28][D][fuji:201]: publishing state
[17:55:28][D][climate:396]: 'Fujitsu' - Sending state:
[17:55:28][D][climate:399]:   Mode: COOL
[17:55:28][D][climate:404]:   Fan Mode: AUTO
[17:55:28][D][climate:419]:   Current Temperature: 27.00°C
[17:55:28][D][climate:425]:   Target Temperature: 0.00°C
[17:55:29][D][fuji:145]: ctrl temp 18 vs my temp 4194303
[17:55:29][D][fuji:201]: publishing state
[17:55:29][D][climate:396]: 'Fujitsu' - Sending state:
[17:55:29][D][climate:399]:   Mode: COOL
[17:55:29][D][climate:404]:   Fan Mode: AUTO
[17:55:29][D][climate:419]:   Current Temperature: 27.00°C
[17:55:29][D][climate:425]:   Target Temperature: 18.00°C
--HA set target t to 22---
[17:55:31][D][climate:011]: 'Fujitsu' - Setting
[17:55:31][D][climate:040]:   Target Temperature: 22.00
[17:55:31][D][fuji:234]: Fuji setting temperature 22.000000
[17:55:32][D][fuji:145]: ctrl temp 22 vs my temp 4194303
[17:55:32][D][fuji:201]: publishing state
[17:55:32][D][climate:396]: 'Fujitsu' - Sending state:
[17:55:32][D][climate:399]:   Mode: COOL
[17:55:32][D][climate:404]:   Fan Mode: AUTO
[17:55:32][D][climate:419]:   Current Temperature: 27.00°C
[17:55:32][D][climate:425]:   Target Temperature: 22.00°C
---HA set to fan only mode---
[17:56:40][D][climate:011]: 'Fujitsu' - Setting
[17:56:40][D][climate:015]:   Mode: FAN_ONLY
[17:56:40][D][fuji:213]: Fuji setting mode 4
[17:56:41][D][fuji:155]: ctrl mode 4 vs my mode 2
[17:56:41][D][fuji:201]: publishing state
[17:56:41][D][climate:396]: 'Fujitsu' - Sending state:
[17:56:41][D][climate:399]:   Mode: FAN_ONLY
[17:56:41][D][climate:404]:   Fan Mode: AUTO
[17:56:41][D][climate:419]:   Current Temperature: 27.00°C
[17:56:41][D][climate:425]:   Target Temperature: 22.00°C
[17:56:42][D][fuji:145]: ctrl temp 0 vs my temp 4194303
[17:56:42][D][fuji:201]: publishing state
[17:56:42][D][climate:396]: 'Fujitsu' - Sending state:
[17:56:42][D][climate:399]:   Mode: FAN_ONLY
[17:56:42][D][climate:404]:   Fan Mode: AUTO
[17:56:42][D][climate:419]:   Current Temperature: 27.00°C
[17:56:42][D][climate:425]:   Target Temperature: 0.00°C
--HA set hvacmode to off--
[18:04:48][D][fuji:193]: Controller turned off AC, adding mode change to call
[18:04:48][D][fuji:201]: publishing state
[18:04:48][D][climate:396]: 'Fujitsu' - Sending state:
[18:04:48][D][climate:399]:   Mode: OFF
[18:04:48][D][climate:404]:   Fan Mode: AUTO
[18:04:48][D][climate:419]:   Current Temperature: 27.00°C
[18:04:48][D][climate:425]:   Target Temperature: 0.00°C
--wired controller set to on and to cool--
[18:06:28][D][fuji:145]: ctrl temp 22 vs my temp 4194303
[18:06:28][D][fuji:155]: ctrl mode 2 vs my mode 0
[18:06:28][D][fuji:201]: publishing state
[18:06:28][D][climate:396]: 'Fujitsu' - Sending state:
[18:06:28][D][climate:399]:   Mode: COOL
[18:06:28][D][climate:404]:   Fan Mode: AUTO
[18:06:28][D][climate:419]:   Current Temperature: 27.00°C
[18:06:28][D][climate:425]:   Target Temperature: 22.00°C
--wired controller set to fan only--
[18:08:57][D][fuji:145]: ctrl temp 0 vs my temp 4194303
[18:08:57][D][fuji:155]: ctrl mode 4 vs my mode 2
[18:08:57][D][fuji:201]: publishing state
[18:08:57][D][climate:396]: 'Fujitsu' - Sending state:
[18:08:57][D][climate:399]:   Mode: FAN_ONLY
[18:08:57][D][climate:404]:   Fan Mode: AUTO
[18:08:57][D][climate:419]:   Current Temperature: 27.00°C
[18:08:57][D][climate:425]:   Target Temperature: 0.00°C
--wired controller set to cool--
[18:10:30][D][fuji:145]: ctrl temp 22 vs my temp 4194303
[18:10:30][D][fuji:155]: ctrl mode 2 vs my mode 4
[18:10:30][D][fuji:201]: publishing state
[18:10:30][D][climate:396]: 'Fujitsu' - Sending state:
[18:10:30][D][climate:399]:   Mode: COOL
[18:10:30][D][climate:404]:   Fan Mode: AUTO
[18:10:30][D][climate:419]:   Current Temperature: 27.00°C
[18:10:30][D][climate:425]:   Target Temperature: 22.00°C`

i cannot replicate this issue so can't help you out here.


Crownium theme

Since the new official theme seems to need some more time I thought I'd offer my own one for merging and keep the people busy bitching about it.
Keep in mind that the main emphasize of this theme wasn't usability (we have already covered that with other themes), I just wanted to do something COMPLETELY different instead of just another blue-ish theme. And a PoC for others to learn how new themes are integrated into Dash.
Looks like this:

....and this:

...and that:

Now kill me :stuck_out_tongue_winking_eye:

Very cool!


Git Stash crash with the 1.33 VS Code update

After the VS Code 1.33.1 update. The extension chrash with the following error:
Cannot read property 'name' of undefined.
You will not see the stash list anymore.
You get the error when open VS Code
You get the error when push the stash refresh button

:scream:
Thanks for reporting @AdrianGarciaSimplr! Will check it as ASAP.

I just updated to 1.33.1 and I haven't had any problem so far. I wonder if has to do with data on any of your open repos.
Does it fail with every git project?
OS?

Yes. In my teams there some developers that use the extension and have the same problem. I will check with an empty repo to see what's happens.

Facing the same issue with the latest version of the extension. Have two stashes in my repository.

Hi @AdrianGarciaSimplr @MoonStruckHorrors. Got some time to review the way stashed files were identified and fixed a couple of related bugs around it that may fix the issues you were having. Would you let me know if the new version behaves correctly on your cases?

Closing due inactivity. Happy to reopen if issue persists.


callback url doesn't keep custom port

I'm trying to configure the nginx with a custom port.
For example:
https://server.com:8443/
But the callback, is always set to https://server.com/_oauth, instead of https://server.com:8443/_oauth.
I was able to do this by adding ngo_callback_host to server.com:8443, but with this I cannot use the localhost approach (using ngo.lol).

Hi @bobrik,
I even if I add http://ngo.lol/_oauth as an "Authorized redirect URIs" in Google console, but I have ngo_callback_host configured as server.com:8443, the callback url is https://server.com:8443/_oauth and not https://ngo.lol/_oauth.
So, If I want to be able to use my custom server name and ngo.lol at the same nginx server with a custom port I cannot use ngo_callback_host, right?
I've made a pull request  #42, so a custom port could be used. Can you have a look?
Thanks

Any update?


Set logging level of basicConfig + catch error of git repo not having…

The script fails when a new conan package has no origin remote.

@uilianries do you think if we should merge this or close?

Sorry, I forgot about this PR. It looks great.
However, Travis is failing. I'm going to restart all jobs now.

ERROR: Failure: ImportError (cannot import name 'ReadmeTemplater')
Seems outdated, it needs to be rebased.


totems

Do you also have the problem that totems are not displayed? which ones you choose

1de72084f64e2c39a63a71e5abd7f3103f9421e3 now the totems should work


simple fix for spike2io

#948
@eduardacenteno : could you test this ?

Hello @samuelgarcia! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file neo/rawio/spike2rawio.py:

Line 552:1: W293 blank line contains whitespace

#948
@eduardacenteno : could you test this ?

hey @samuelgarcia , I tested it in my computer, adding these lines to my spike2rawio.py file indeed solved the issue :)

Ready to reveiw and merge if OK

Ready to review (and merge maybe)

@apdavison @JuliaSprenger : can we merge this ?

@eduardacenteno I assume this fixes your issue. Please comment if this is not the case.


ros_gz: 1.0.3-1 in 'jazzy/distribution.yaml' [bloom]

Increasing version of package(s) in repository ros_gz to 1.0.3-1:

upstream repository: https://github.com/gazebosim/ros_gz
release repository: https://github.com/ros2-gbp/ros_ign-release.git
distro file: jazzy/distribution.yaml
bloom version: 0.12.0
previous version for package: 1.0.2-1

ros_gz

No changes

ros_gz_bridge
* Add support for gz.msgs.EntityWrench (base branch: ros2) (#573 <https://github.com/gazebosim/ros_gz/issues/573>) (#574 <https://github.com/gazebosim/ros_gz/issues/574>)
  (cherry picked from commit f9afb69d1163633dd978024bb7271a28cf7b551a)
  Co-authored-by: Victor T. Noppeney<EMAIL_ADDRESS>* Contributors: mergify[bot]

ros_gz_image

No changes

ros_gz_interfaces
* Add support for gz.msgs.EntityWrench (base branch: ros2) (#573 <https://github.com/gazebosim/ros_gz/issues/573>) (#574 <https://github.com/gazebosim/ros_gz/issues/574>)
  (cherry picked from commit f9afb69d1163633dd978024bb7271a28cf7b551a)
  Co-authored-by: Victor T. Noppeney<EMAIL_ADDRESS>* Contributors: mergify[bot]

ros_gz_sim

No changes

ros_gz_sim_demos

No changes

test_ros_gz_bridge

No changes

Holding for Jazzy sync


Routing Error - No route matches [GET] "/api/v2/blacklist_emails"

I'm getting a Routing Error when using the jsonapi_resources route helper.
  namespace :api do
    namespace :v1, :defaults => { :format => :json } do
      # ... omitted
    end
    namespace :v2, :defaults => { :format => :json } do
      # get :blacklist_emails, to: "blacklist_emails#index" # enabling this works
      jsonapi_resources :blacklist_emails
      jsonapi_resources :activities
    end
  end

Enabling the specific get request works fine. What could I be doing wrong?

Doh...I ran rake routes like Rails said to and realized the URL is dasherized. Never mind!

The default is dasherized, but you can change that in the configuration section.
JSONAPI.configure do |config|
      #:underscored_route, :camelized_route, :dasherized_route, or custom
      config.route_format = : underscored_route
end

See https://github.com/cerebris/jsonapi-resources#key-format for more details on the configure method. It looks like the documentation for this didn't make it into the readme. Sorry for that.

No worries, I should have guessed it would be dasherized. :-)


Primitive integration

Begin work on integrating Primitives into Radix ✨

Alright, updated to a pre-release version of Primitives, gonna merge this, release a new beta version, and test it in Modulz
@benoitgrelard @vladmoroz @colmtuite @StephenHaney


Store the data in a date-based file.

This will allow us to do analysis of how things changed over time.

Thanks! Merge after addressing.


Search is Broken

As reported by @dvdplm :pray: the search box for substrate.dev is not working.

Search is working :tada: I don't know what happened...something must have fixed it on Algolia's end.


using with php+codeception not using relative path from project root

When I run a TestFile, it figures out codeception correctly (wow), but calls my test file with full path rather than relative to project root.
Suite '/Volumes/Untitled/projects/xyz/tests/unit/models/OrderTest.php:testName' could not be found
Had it called codeception with relative path like
codecept tests/unit/models/OrderTest.php:testName the test would have worked.
I tried using let test#filename_modifier = ':.' but did not help.
Can I configure some exception?

For me it does run relative to the project root.  What do you get you open your test file and run :echo expand('%') and :echo expand('%:.')?

I've been using Codeception lately, too, and it seems to figure out the relative path for me as well: clear;codecept run ./api/push/TagsCest.php:fooCan

Is this still an issue?

I'll check and respond.
On Sat, 23 May 2020, 13:45 Mathew Attlee<EMAIL_ADDRESS>wrote:

Is this still an issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/vim-test/vim-test/issues/374#issuecomment-633005502,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAXFSTD5P3OJYF3BEG2HNTRS6AZ3ANCNFSM4HZPJEOA
.


Check that things work with android

The goal of this is to make sure the Android version of the app starts after using this template.

Verified that it still works!


some dashboards are showing no datapoints

some dashboards showing no datapoints at all

System overview not showing all VMS

am I serioulsly missing anything thats why dashboards are not showing any datapoints?
some dashboards are just fine

do i need to configure datasource like influxDB? why?

Hi. There are three data sources that are used to monitor PCF - bosh_exporter, firehose_exporter and cf_exporter. Different graphs use values emitted by different exporters so a situation where you see data in some dashboards but not others typically means that some exporters are running fine while other don't. I'd start by going to each exporters logs: on the Prometheus VM go to /var/vcap/sys/log and check bosh_exporter/* cf_exporter/*  and firehose_exporter/*.

Oh, and regarding InfluxDB - it's not needed at all. What made you think it could be required?

@mkuratczyk Thanks again. your quick response much appreciated. I did check logs for cf_exporter and found
time="2017-08-16T20:35:51Z" level=error msg="Error while listing audit.app.update application events: Error requesting appevents Get https://api.system.cf-ssb-z3-dev.discoverfinancial.com/v2/events?q=type:audit.app.update: oauth2: cannot fetch token: 401 Unauthorized\nResponse: {"error":"unauthorized","error_description":"Bad credentials"}" source="application_events_collector.go:188"
I thought I was using the correct credentials , but anyways I reset uaac client prometheus secret using following
uaac secret set prometheus-cf
That error stopped throwing in the logs and cf-summary dashboard started ...

Influxdb_exporter (which is a fake API-compatible server that pretends to be InfluxDB but exposes data for Prometheus instead of actually storying it) or an actual InfluxDB (a different BOSH release) can be used to monitor Concourse. There is one dashboard for Concourse monitoring in prometheus-boshrelease but if you want a more detailed view of your Concourse I'd currently recommend deploying an actual InfluxDB (problem is Concourse emits events which are not handled well by Prometheus). You can see an example of Concourse dashboards with real InfluxDB on https://metrics.concourse.ci/


HTML

HTML
User Story
As a bootcamp student
I want the prework notes to be structured an a webpage
so i can easily find and read information
Acceptance Criteria
GIVEN a Prework Study Guide Website
WHEN i visit the website in my browser
THEN I see four boxes titled HTML, CSS, GIT, and JavaScript with association notes listed

CSS
User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I see a dark blue header and footer, and four boxes with a shadow

JavaScript
User Story
As a boot camp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the study guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first

#README
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN the prework project repository,
WHEN I view the README for the repository,
THEN I can see a professional README that provides information on the project and how to use it

Deployment
User Story
As a boot camp student,
I want the prework notes to be structured on a webpage,
So that I can easily find and read the information.
Acceptance Criteria
GIVEN a Prework Study Guide website,
WHEN I visit the website using the URL,
THEN I can access my website from any browser


python3Packages.heatzypy: init at 1.4.2

Motivation for this change
Python module to interact with Heatzy devices
https://github.com/Cyr-ius/heatzypy
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.11 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 148513 run on x86_64-linux 1

2 packages built:

python38Packages.heatzypy
python39Packages.heatzypy


modern-cv:0.2.0

I am submitting

[ ] a new package
[x] an update for a package

Improved the readability of the template and cleaned up the design to make it more readable and flexible.

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

Thanks for the review @laurmaedje, I think I addressed all your points.


chore: use issue forms

Please describe what the pull request is about, and what this aims to do:
This makes use of GitHub's new feature - issue forms to easily organize things.
Details on why this pull request should be merged:
User friendly and it has good validation and design.
Any alternative pull requests or issues that work on this:
None.
Additional details:
https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-issue-forms

/approve


Menus not working

The menu dropdowns are not working with a fresh install of this theme. You click, nothing drops down.

By default, Bootstrap menus only support dropdowns under top level items that don't have a real link (e.g. href="#"). For more elaborate navs adjustments need to be made or a third party plugin like Ubermenu.
Is this the problem you are seeing?

I don't think so.
http://kimberlygettle.agentmultisite.com/
I have # as the link for the parent link.

Strange, the <li> should automatically (via JavaScript) get the class .open added when clicked.
You can see in the screenshot where I added it manually via Google Inspector.
However, it is not being added when clicked on your site.

Okay, it looks like somewhere bootstrap.min.js is being included in your theme, which should be removed.
Bootstrap Genesis includes Bootstrap's JavaScript in javascript.min.js.
Enqueuing that file would be the next thing I'd try.
If it still doesn't work, I'd disable all the plugins and try it again.

Thank you. I am sorry you had to do that. I should have known. I have a plugin that has bootstrap on it.  Thank you for your time.

Nothing to apologize for @AgentFrameworks
If we were enqueuing using a standard handle like "bootstrap" this problem might have been avoided but making that change leads to other problems (see #88)
I'm glad things are sorted.  I'm going to close this issue.

I had a similar issue, it was caused by the plugin > "Bootstrap Shortcodes", which added "bootstrap.js". I removed the plugin for now. Thanks


Install instructions for vim-plug

Adds install instructions for vim-plug in the README.md (as promised in issue https://github.com/elixir-tools/elixir-tools.nvim/issues/230).

:) thank you Sir, happy holidays.


Paginated QueryStream

I've noticed that watch() is not very well optimized for larger fetches because on every update it fetches all data and maps it into objects.
A typical case for larger fetch is displaying items in a very long list: chat messages, mails, history, etc.
So perhaps moor should provide something like NSFetchedResultsController from CoreData - as users scrolls list / grid, it would query further pages, and probably discard previous ones.
I'm not sure what would be the best way to do this, maybe have something that maintains QueryStream for current page, and then recreates it when user scrolls further.

i have the same use case
i want to observe data from table that have a lot of data  so i load the first 20 and append them to list and so on, but when first values changed in database my values in list not updated and that normal because it's not a stream .
any helpful idea to apply pagination with moor and stream without loading all data please @simolus3  @szotp ?

I have a solution for this, I'll post it during the weekend. Basically you have to watch first page of data and adjust your big array if something gets inserted or deleted.

i'll be waiting for you, please do not forget and thank you .

Here it is: https://github.com/szotp/moor_fetcher/blob/master/lib/moor_fetcher.dart
You can copy the code or import is as package.

@szotp is there any updated code for this issue? thankyou

To give an update for it and how I managed to solve it - assume you've  list of items which you'd like to paginate over and listen for its changes:
Assuming you locally have List<T>.

Get length of List<T> and based on it, get the offset for pagination
Check if there are any more T in the DB based on the offset.
2a. If there are not - terminate querying
2b. If there are, get more T based on the offset and page size
Iterate through new List<T> and attach watch query to each item to observe the changes
3.1. If item is null - remove from the local list otherwise replace in the local list
Add all List<T> from DB to local list

This way we do not need to keep track of pagination as it will be dependant on the length of the items in the local list. Further, only these item changes are being listened to.
Let me know if anyone finds it beneficial - can put up a full implementation of it.

@deimantasa Hi please post cose sample example for how you solved thesw