Nuxt 3 useFetch - nuxt instance unavailable when using useFetch at least twice in one function

Environment
Nuxt 3.0 / Nuxt 3.1
Linux
Node 16
Reproduction
https://stackblitz.com/edit/github-qe9ulj?file=app.vue
Describe the bug
When we try to use useFetch at least twice in a function, we often get server error in console saying:
[nitro] [dev] [unhandledRejection] Error: nuxt instance unavailable

Additional context
No response
Logs
No response

Don't mix async and await.
Simply use ```vue

After calling useFetch within a function the context is lost - it should be called either directly within your setup block (in which case the context will be preserved - or you can use callWithNuxt. More info here: https://github.com/nuxt/nuxt/issues/14269#issuecomment-1397352832.

Don't mix async and await.
Simply use
``

kuohuanhuan it doesn't change anything, the app will start but you will still get error in console as I said in the reproduction..

After calling useFetch within a function the context is lost - it should be called either directly within your setup block (in which case the context will be preserved - or you can use callWithNuxt. More info here: #14269 (comment).

@danielroe so why it's working with one useFetch call? Shouldn't we use useFetch inside functions?

No. You can use $fetch instead - useFetch is a composable that is meant to be used within a setup function. Do read the comment I linked - it explains this in more detail.

Don't mix async and await.
Simply use
``

kuohuanhuan it doesn't change anything, the app will start but you will still get error in console as I said in the reproduction..

It works, actually. Put the useFetch() method outside of a function.

@danielroe Ok let's assume we switch to $fetch inside function.
What happens right now is that first when server renders page, the request is made server side. Server returns document with fetched data. However when application mounts, the request is also made client-side.
When we used useFetch, the request on initial load was made only on server side and it wasn't visible in network tab. Is this correct behavior?

Yes, that is the expected behaviour.
If you are trying to show a composable in your repro, then something like this would likely be better:
function myFunc() {
  const [res1, res2] = await Promise.all([
    useFetch(/* */),
    useFetch(/* */)
  ])
}

If you really need the result of first before calling second one (bear in mind this will cause a waterfall and performance cost) then you can use callWithNuxt as spelled out in the issue I linked.

Yes, I am aware of Promise.all, repro was made, well, just for repro ;)
Would approach below (and callWithNuxt in general) incur unwanted performance costs?
function myFunc() {
  const [res1, res2] = await Promise.all([
    useApi(endpoint),
    useApi(another_endpoint)
  ])
}

// useApi function
const nuxtApp = useNuxtApp();
const { data } = await callWithNuxt(nuxtApp, useFetch, [`/api/${endpoint}`]);
return data

No, that would be fine 👌

@danielroe it seems that callWithNuxt is still not resolving issue with nuxt instance unavailable.. (initial page load)
// useApi composable
const nuxtApp = useNuxtApp();
const { data } = await callWithNuxt(nuxtApp, useFetch, [`/api/${endpoint}`]);
return data.value

// function inside pinia setup store
const fetchListing = async () => {
  const res1 = await useApi('...')
  // now some logic that has to be performed before res2 call
  const res2 = await useApi('...')
}

// listing.vue (script setup) in pages folder
await fetchListing()

[nitro] [dev] [unhandledRejection] Error: nuxt instance unavailable

No, more like this:
// useApi composable
const { data } = await useFetch(`/api/${endpoint}`);
return data.value

// function inside pinia setup store
const fetchListing = async () => {
  const nuxtApp = useNuxtApp();
  const res1 = await useApi('...')
  // now some logic that has to be performed before res2 call
  const res2 = await callWithNuxt(useApi, '...')
}

// listing.vue (script setup) in pages folder
await fetchListing()

@danielroe Page is getting loaded, however we now can observe this type of warn in console:
[Vue warn]: onServerPrefetch is called when there is no active component instance to be associated with. Lifecycle injection APIs can only be used during execution of setup(). If you are using async setup(), make sure to register lifecycle hooks before the first await statement.


Enhance message for users running a project on a used port

Running a dev server of a muban project installed through pota on a port that is already in use confronts the user with a wall of feedback. It feels this could be handled more gracefully or even better: a suggestion to run the project on a different port.

This seems to be an old issue, as I would not consider as a single line in the terminal mentioning that the development server is picking a different, unused port, as a "wall of feedback".


Explain why NetID is needed and prepare user to recieve email

Asking for a NetID with no context perhaps might slightly dissuade someone from moving to the next step of an order. Explaining why it's needed might be of some use. Here's a draft template message:

Please provide your UT Dallas NetID. We use it to send you a verification email, helping us fight spam.

This also lets the user know what the next step of the process is before it actually taken place.

Fixed with 40b63ed


Proper binding to allow inline html

Subject of the issue
I am trying to use translation bindings that contain inline HTML elements using $translateProvider.useSanitizeValueStrategy('sanitizeParameters');

{{'value' | translate}}

Steps to reproduce
https://plnkr.co/edit/vDsqsFyvT3ntysO8DmpN?p=preview
Expected behaviour
Item should print as
value
Actual behaviour
HTML is actually printing to the screen.
value
the below ways render as I would expect as value

value

Hi @just-trey
That result is correct so far: AngularJS filters' output is escaped always (by AngularJS).
I also recommend and linking to #1588 as we discussing how we can improve the situation with filters and services also.
I'll close this as it duplicates #1588 actually. Feedback is still welcome.


fix(aws-stepfunctions): refactor sagemaker tasks and fix default role issue

Refactor the train job to create default security group and add new method to add new security groups
Ensure the environment variables and tags values are always string values
Change IAM role id to be different for SagemakerTrainJob and SagemakerTransformJob. Fixes #3013
Added new check to ensure there is an Image Name or Algorithm Name defined for the train job

Please read the contribution guidelines and follow the pull-request checklist.
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license

The error is due to a break in the compatibility as I removed the Construct param from the constructor of the SFN Task objects. This package should be flagged as experimental so that breaks in compatibility are allowed. Waiting for this change to be reflected in the CI process

Triggering build


Do i need to link this project?

I m in RN 0.62.
did I need to link  this project?
like
react native link react-native-alarm-manager

Hello @Foveluy.
As far as I know is you don't need to use link command. Because auto linking is supported in react native 0.60 greater version.
Thank you.


Remove stream included list check in destroy_stream [BUG]

In destroy_stream_locked
if (s->included[i]) {       gpr_log(GPR_ERROR, "%s stream %d still included in list %d",               t->is_client ? "client" : "server", s->id, i);       abort();     }
The abort() can really happen although I didn't find more detail info on it now.
Also I think this abort is meaningless. It doesn't imply other stream or transport is damaged.
So why can we do something like the grpc_chttp2_list_remove_stalled_by_stream(t, s); grpc_chttp2_list_remove_stalled_by_transport(t, s); above to remove other stream list id ??

I can find a code path to reproduce this abort now.
Suppose the following scenario.
In server side, after prepare the response , start to send initialmetadata/message.
It will schedule write_action_begin_locked and grpc_chttp2_begin_write to change stream from writable to writing state.
At the time, the client send the rst stream to cancel the call then server  will read_action_locked to parse  the new coming data and handle it by grpc_chttp2_mark_stream_closed terminally.
If  grpc_chttp2_mark_stream_closed happens before  write_action_end_locked, the stream state won't change back to writing  again.  So you will meet the abort in the destroy_stream_locked.
In summary, I think it is  a bug   and we need pop/remove the stream from the transport list in grpc_chttp2_mark_stream_closed  or  destroy_stream_locked or somewhere else.
Please correct me if something incorrect.

Could you provide a code snippet or a test that demonstrated this behavior? We have hit this abort before, and all times it has caught real bugs that needed to be fixed, so I am hesitant to remove this without a test that uses gRPC correctly and also triggers this abort

Closing for now. Please reopen if you have a reproduction in which valid gRPC code triggers this abort


SSH

I updated to version: 1.86.0 (Universal) MAC and now I can't connect to ssh

I have the same issue. Downgraded to previous version and its working now

Same issue here.  Normally use ssh to Synology NAS. This was working fine in version 1.85.2. I can no longer connect with version1.86.0

@Matilio @sagarbhatt0904 @git-nico Looks like this is same as https://github.com/microsoft/vscode/issues/203967?

@Matilio @sagarbhatt0904 @lszomoru @WinCPP
touch /tmp/vscode-skip-server-requirements-check on the remote server did the trick. I could use version 1.86 to ssh into remote machine.

closing as duplicate of https://github.com/microsoft/vscode/issues/203967#issuecomment-1923440629


Doesn't save tags passed as associations after upgrading to 6.0.0

Hello,
in our project we assign tags the following way:
tag = ActsAsTaggableOn::Tag.create! name: 'people'

Article.create! title: 'Title', content: 'Text', tags: [tag]
#or
Article.create! title: 'Title', content: 'Text', tags_ids: [tag.id]

Especially we have many pieces like this in our tests.
After upgrade  from AATO 5.0.0 to 6.0.0 it started to fail with
ActiveRecord::RecordInvalid:
  Validation failed: Tag taggings is invalid

Seems like that tagging cannot be saved because context is blank.
Should it save tags passed to tags association with DEFAULT_CONTEXT = 'tags' by default?
If it should could you please confirm and fix it,
otherwise I need to change the way we assign tags in our code
Thank you!

I am upgrading from 5.00 to 6.00 version and I have the same issue.
How did you solve it @Hirurg103  ?

Hi @piotr-galas I could not solve this issue for now and use the 5 version

@Hirurg103 override tagging model in you app with  this file

@Hirurg103
You have added the optional: true to this file.  I will prepare PR with this fix, in the next week maybe

Hi @piotr-galas I suppose you wanted to mention @uzaif313 in your last comment

thanks, @Hirurg103 for fix @piotr-galas  comment

Any update on this? just started running into this issue.

some question

i use the patch but not work, error is there

Don't specify
config.load_defaults <rails_v>
in application.rb

Don't specify
config.load_defaults <rails_v>
in application.rb

You can also remove the validator for the taggable association:
# config/initializers/aato.rb

chain = ActsAsTaggableOn::Tagging.send(:get_callbacks, :validate)
callback = chain.find{|cb| cb.filter.attributes == [:taggable]}
chain.delete(callback)

Works on rails 5.1 with aato 7.0.0


Automated Package Upgrade

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat(Table): add vertical alignment

This PR adds vertical alignment for table body rows just like in the uikit's table: https://preview.gravity-ui.com/uikit/?path=/story/components-data-display-table--default.
As for my investigation, horizontal alignment requires many wrappers for tanstack's types, so I suggest to implement it in another PR

Also it might be a good idea to make verticalAlign: 'top' default?


Add module for PCA

Add a module that generates a 2-dimensional PCA plot of the samples.
Input:

gene expression matrix
sample sheet

Ouput:

plot

Section in old code:
https://github.com/icbi-lab/deseq2icbi/blob/28e54a75598d39b70090376daa0e9ddefee25363/runDESeq2_ICBI.R#L481-L491

Closed via #25


Use Color.Resolved to serialize Color on macOS 14+

https://developer.apple.com/documentation/swiftui/color/resolve(in:)
https://developer.apple.com/documentation/swiftui/color/resolved
It should be able to store the color better than what we currently do. We still need to preserve backwards compatibility, so we can first try loading it as Color.Resolved and if it fails, we can use the old way.

Hmm, actually, this means it would not be able to preserve colors that contain both light and dark variants. I wonder if that is currently supported with our current method.


Enable/disable maps based on environment

I'd like the source maps to be disabled based on environment. However, when I do this:
var devLikeEnvs = ['development'];
And then in my bundle options:
maps: devLikeEnvs
It doesn't work. I looked closer at the code and it appears that you can't set it by environment like you can other bundle options.

This is true. I take PRs!


FixedBucketSampler may return batch with varied length (setting ratio=0)

When using FixedBucketSampler, it seems if a bucket includes fewer than batch_size data points, the sampler may return a batch with less data (than the configured batch_size).  This might be an unexpected behavior for the users since the ratio=0 and batch_size=N are configured to get exactly N data points per batch.
I observed this when using the FixedBucketSampler together with the DataLoader as in the following, therein making a guess about the reason at this line. Please correct me if there exist configuration to get batches including the same amount of data.
To repeat the errors, one may simply configure a large enough num_buckets (e.g., 20).
batchify_fn = mxex.gluonnlp.data.batchify.Dictionary({constants.QUESTION:
                                Pad(axis=0,
                                    pad_val=vocab[constants.PADDING_TOKEN],
                                    ret_length=False,
                                    dtype='int32'),
                            constants.ANSWERS:
                                Pad(axis=0,
                                    pad_val=vocab[constants.PADDING_TOKEN],
                                    ret_length=False,
                                    dtype='int32'),
                            constants.CONTEXTS:
                                Pad(axis=0,
                                    pad_val=vocab[constants.PADDING_TOKEN],
                                    ret_length=False,
                                    dtype='int32')})

batch_sampler = gluonnlp.data.FixedBucketSampler(lengths=txt_lengths,
                                                         batch_size=batch_size,
                                                         num_buckets=num_buckets_in_sampler,
                                                         shuffle=True)
data_loader = gluon.data.DataLoader(encoded_seqs,
                                        batch_sampler=batch_sampler,
                                        batchify_fn=batchify_fn,
                                        num_workers=num_workers)

When ratio is 0, there's still the case where num_samples % batch_size != 0. In this case, we'd have the choice of 1) drop the batch, 2) pad samples 3) leave as is. There likely are scenarios that each of these options are good for. @sxjscience @szhengac how do you recommend we handle these cases?

@szha Thanks for the comments.
I may not find the last_batch parameter for the sampler since the last_batch is disabled in data_loader if a batch_sampler is used.

The current design is that the data are loaded without any padding. The user may pad the data/drop the batch after it’s loaded. I agree it should be added to the document.

@sxjscience
As far as I understand, the padding is orthogonal right? This is the sampler, meanwhile the padding is done with the function in batchify batchify_fn .

@khui Thanks for the question.

Yes, I mean the current implementation will not pad the incomplete batches. There are multiple ways to handle those incomplete batches, e.g., padding with zeros, padding by repeating the last few samples, padding by feeding in samples in a round-robin order, or just drop the batch.

We chose not to handle these cases and just implemented the very basic strategy (no padding) because it simplifies the API and can satisfy the requirement of most users. Now we can think if we could add an additional API that deals with these scenarios.

I haven't fully understood the second question. Would you provide an example about how TF handles that?

@sxjscience
Thanks for the answers.
As for 1, I am not sure why people will pad zeros to complete the batch. Could you provide examples? The sampler basically randomlly sample (random sample with replacement) the data points to generate batch, thereby, one might assume there wont be not enough data. Namely, even when I only have 10 data point, I should still generate batch with 32 data points, by simply repeating some of the data points.
For 2), please refer to the repeat() in the dataset api.
https://www.tensorflow.org/api_docs/python/tf/data/Dataset#repeat.
The use of repeat is something like that:
dataset = tf.data.Dataset.from_generator(...)
dataset=dataset.apply(lambda X, _:(transformation_func(X), y))
dataset=dataset.shuffle(buffer_size=10000)
dataset=dataset.repeat()
iterator = dataset.make_one_shot_iterator()
nxt_X, nxt_y = iterator.get_next()

....
for batch_id in range(num_batch_to_run):
    loss_np = sess.run(loss, feed_dict={X: nxt_X, y: nxt_y})

Sometimes the data/label are all padded to zero to mimic a masking behavior, although that’s not necessary in our case. I think adding a padding by samples/drop/no_padding option would be feasible in our case.
BTW,  would the performance be downgraded if the batchsize are not always the same? Since Gluon support dynamic shapes, I assumed that we would no longer require to pad the data.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Kai Hui<EMAIL_ADDRESS>Sent: Friday, May 3, 2019 9:03 PM
To: dmlc/gluon-nlp
Cc: Xingjian SHI; Mention
Subject: Re: [dmlc/gluon-nlp] FixedBucketSampler may return batch with varied length (setting ratio=0) (#683)
@sxjsciencehttps://github.com/sxjscience
Thanks for the answers.
As for 1, I am not sure why people will pad zeros to complete the batch. Could you provide examples? The sampler basically randomlly sample (random sample with replacement) the data points to generate batch, thereby, one might assume there wont be not enough data. Namely, even when I only have 10 data point, I should still generate batch with 32 data points, by simply repeating some of the data points.
For 2), please refer to the repeat() in the dataset api.
https://www.tensorflow.org/api_docs/python/tf/data/Dataset#repeat.
The use of repeat is something like that:
dataset = tf.data.Dataset.from_generator(...)
dataset=dataset.apply(lambda X, _:(transformation_func(X), y))
dataset=dataset.shuffle(buffer_size=10000)
dataset=dataset.repeat()
iterator = dataset.make_one_shot_iterator()
nxt_X, nxt_y = iterator.get_next()
....
for batch_id in range(num_batch_to_run):
loss_np = sess.run(loss, feed_dict={X: nxt_X, y: nxt_y})
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dmlc/gluon-nlp/issues/683#issuecomment-489087836, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABHQH3VUFCVBY4QG6HSLQS3PTQZ3BANCNFSM4HJDVIFA.

I am not sure about the influcences of the variant batch size on the performance. My point is that the behavior should align with the expectation and the convention as well. Especially notice that, the batch_size (together with the learning rate) is among the important hyperparameters to govern the learning process.  Up to the distribution of the data, however, it is possible that significant amount of batches are with different size then the configured one (use big bucket number and big batch size).
More importantly, for those bucket that includes not enough samples for a batch, there exist no sampling mechanism when the bucket is chosen, this could be harmful to the performance. Thereby, some measurements beyond documentation, e.g., merging those incompleted buckets make more sense, to 1) get enough sampling per batch; 2) actually do the sampling and introduce randomness.
You are right that the FixedBucketSampler actually supports the varied batch sizes. And better documentation could at lesat remind the users to pay attention to the behaviors of the samplers.

I am facing a similar issue:
SET UP:
train_batch_sampler = nlp.data.FixedBucketSampler(lengths=data_train_lengths,
batch_size=500,
num_buckets=1,
ratio=0.0,
shuffle=True,
use_average_length=True,
num_shards=1,
bucket_scheme=bucket_scheme)
Where,
len(data_train_lengths) is 3560
bucket_scheme is obtained using "nlp.data.ConstWidthBucket()"
ISSUE:
With the above settings, the number of batches should be 3530/500 = 7.
I, however, see the total number of batches (as returned by the data loader) to be 118!
Additionally, train_batch_sampler.stats() gives a batch size of 30! Not sure why.

train_batch_sampler.stats():
sample_num=3530, batch_num=118
key=[(31, 32)]
cnt=[3530]
batch_size=[30]

train_batch_sampler._batch_size
500

@Arhamna. When use_average_length=True, batch_size means the approximate number of tokens in a mini-batch.

I see. Yes setting use_average_length=False gives the desired batch size. Thank you so much!


Update mainline and stable patches (November 2, 2023)

Just two patches for recent build failures from changes on both the Linux and LLVM side.
I have opted not to patch next to avoid losing coverage if patches no longer apply (as they will end up there first).

Added two more patches that are needed after last night's run: https://github.com/ClangBuiltLinux/continuous-integration2/actions/runs/6745136000


How well does pixi.js scale?

Hi all,
I'm a long time gamedev enthusiast - currently working as a software engineer specializing in JS.  I have a ton of experience with JS and reading the tutorials made sense and it seems easy to pickup.
While I've made a few games (and a little cash) off of the flash market several years ago, I've been thinking about diving into HTML 5.  pixi's cross-browser support seems very promising.  I'm just thinking of getting into it as sort of a hobby, and maybe meeting some cool folks and collaborate down the road.
However, I'm still not 100%, there's a lot of html 5 engines out there, and I'm sure each one is unique.  So please humor me as I describe my ideal game engine, and tell me if pixi is right (or not for me)
TLDR?
Currently I'm looking for an html 5 engine that is:

Lightweight

Plays well with others (other JS frameworks such as underscore, and requireJS)

Can scale. (extremely important)

Works well with CommonJS / AMD (requireJS, nodeJS, browserify; requireJS preferred)

Given the points above, how well does pixi.js fit?  Are there any demos out there that show the directory scaffold of a well engineered pixi.js?

Lightweight

Wait until v3.

Plays well with others (other JS frameworks such as underscore, and requireJS)

We export UMD so it should work with all module systems.

Can scale. (extremely important)

Not sure what this even means. Do you mean screen size, project size, texture size, GPU ops, backwards compat...

Works well with CommonJS / AMD (requireJS, nodeJS, browserify; requireJS preferred)

We export with a UMD wrapper. It does not run on nodejs yet, wait for v3.
A "well engineered pixi.js" project looks like what works best for your use case. Pixi is meant to be a general rendering engine for games, sites, charts, anything. Each project looks different, pixi is just one of many libraries your project will depend on.

Thanks for the reply.
As for "can scale" - sorry to be vague - I mean in strictly in maintainability.  as in scale well in volume of assets (separate script files, maintainable architecture, etc) I'll wait for v3, might play around with the code a bit to get my feet wet.

@MattMcFarland The architecture's maintainability is the primary goal of the v3 rewrite due to challenges we are facing in the maintainability of the core lib now. So hopefully that makes my answer "yes" when that work is done :)

:+1: Awesome! Thank you, and cant wait to see what happens.   I'd love to watch and provide input if possible, even help if I can.  I'm an avid JS engineer with passion for good architecture :)  Or I can silently read at least...

Most conversation is happening on that thread. I'm doing most of the work for now and that is happening on my dev-rewrite branch.
If you want to help out just hit send PRs to that branch. If you see something in the code that doesn't make sense, let me know. Feel free to run with any of the Phase4+ phases that seem interesting to you!

Obviously we also need examples and tests for the new code, so that is always a huge help as well!

Reading the proposal, and looks good so far. glad to see a lot of progress
already made.  I am especially pleased to see the decoupling a priority.
I'll look through more.  thanks again.
On Fri, Jan 9, 2015 at 10:46 PM, Chad Engler<EMAIL_ADDRESS>wrote:

Obviously we also need examples and tests for the new code, so that is
always a huge help as well!
—
Reply to this email directly or view it on GitHub
https://github.com/GoodBoyDigital/pixi.js/issues/1341#issuecomment-69438299
.

Anytime!

Just posted my thoughts here:
https://github.com/GoodBoyDigital/pixi.js/issues/1296#issuecomment-69439842

please have a read I hope they help with phase 3.

On Fri, Jan 9, 2015 at 11:02 PM, Chad Engler<EMAIL_ADDRESS>wrote:

Anytime!
—
Reply to this email directly or view it on GitHub
https://github.com/GoodBoyDigital/pixi.js/issues/1341#issuecomment-69439053
.


Switch "HP A5500-24G-SFP EI" not receiving logs

Hi Team,
We are not receiving logs from Core Switch "HP A5500-24G-SFP EI"  tried with below link but it is not working
https://splunk.github.io/splunk-connect-for-syslog/main/sources/vendor/HPe/procurve/
We want this device to be added in our syslog server
Requesting this source to be added.
Regards
Juhi Sharma

Hi @Juhi220915 , please provide .pcap file or anonymised raw log.

Hi Team
.pcap from Switch is not possible...
We can do telnet (on TCP port; since we can not do telnet on UDP port) from switch towards France splunk server..and itis connecting.
this means connectivity is through from Switch to Splunk.
Regards,
Juhi Sharma

Hi, I am a bit confused. Normally there would be a kind of architecture where switch is sending the logs to the host where SC4S is installed and further SC4S forwards processed messages to a Splunk server. If you are checking connectivity between switch and Splunk it either has no sense or you are hosting SC4S on the same server as Splunk which is not recommended (usually you want syslog server as close to a source as possible). If the switch is configured properly you should be able to do tcp dump on SC4S server to see what's incomig. This should also resolve the doubts about the connectivity- if you can see data form switch on SC4S instance and not in Splunk it is issue with missing parser/filter and we can help. If no data incoming from that switch will be visible on SC4S host it's most probably connectivity issue and we can't help with that.

Hi Team,
We are able to see logs for this particular device under sourcetype (fallback).
Attached is the screenshot for your reference

Thanks,
Juhi Sharma

Hi, it is not a valid syslog message and this we will not add it to the standard package (simply we don't support this kind message). However if you wish to put it under specific sourcetype or index you can use custom filter.  In this case I think the only valid option would be using host as data that will somehow 'identify' the source of message.
Just place it under (example) /opt/sc4s/local/config/filters/app-postfilter-hp-a5500.conf
`block parser app-hp-a5500-postfilter() {
channel {
rewrite {
r_set_splunk_dest_default(
index('netops') #this is just an exapmle
source('hp:A5500')
sourcetype('hp:A5500:something')
vendor("hp")
product('A5500')
        );
    };

};
};
application app-hp-A5500-postfilter[sc4s-postfilter] {
filter {
host("es-mjv-mjv-dc-hpcs-std-01" type(glob))
};
parser { app-hp-a5500-postfilter() };
};Take a note that you can use wildcards in the host name or useor` condition if you want to specify a list of hosts. The indexes etc are up to your choice- just keep in mind that you need to create index in Splunk first if you use something custom- otherwise message will be dropped.
After placing the file you need to restart sc4s service to reload the configuration.

Hi, I'm closing this issue due to inactivity. Please re-open it in case of problems.


Model seems to be valid but renders empty with error logged

Description
A specific model renders empty in model-viewer but displays correctly in other viewers (e.g. three.js editor, Don's old and new viewers, ...).
Live Demo
Drop this model into modelviewer.dev/editor:
plant_3.o.zip
There's an error logged:
space-opera.js:80510 Mesh is missing primitive index association

Browser Affected

[X] All as far as I can tell

This has come up before, see https://github.com/mrdoob/three.js/issues/25252, which I suppose I should actually contribute. If you happen to figure out what part of the glTF is triggering this bug, please post it here - it may help with that refactor.


[5.5] UPDATED_AT constant behavior breaking change

Laravel Version: 5.5.0
PHP Version: 7.1
Database Driver & Version: MySQL 5.7

Description:
I've used null UPDATED_AT contant in models where there were no updated_at column but something was changed in 5.5 and I couldn't find this change in changelog. In 5.4 updated_at column was completely ignored on null value of constant. And now we have an exception:

Too few arguments to function Illuminate\Database\Eloquent\Model::setAttribute(), 1 passed

That happens because setAttribute method instead of updated_at column key receives empty string.
Found by @xdisplayx in one of my packages: https://github.com/cybercog/laravel-likeable/issues/24
Steps To Reproduce:
1. Create migration without updated_at column
<?php

use Illuminate\Database\Migrations\Migration;
use Illuminate\Database\Schema\Blueprint;
use Illuminate\Support\Facades\Schema;

class CreateEntitiesTable extends Migration
{
    public function up()
    {
        Schema::create('entities', function (Blueprint $table) {
            $table->increments('id');
            $table->string('name');
            $table->timestamp('created_at')->nullable();
        });
    }
}

2. Create Eloquent Model class
<?php

namespace App;

class Entity extends \Illuminate\Database\Eloquent\Model
{
    const UPDATED_AT = null;

    protected $fillable = [
        'name',
    ];
}

3. Try to create an Entity
$entity = Entity::create([
    'name' => 'Test',
]);

Result

Too few arguments to function Illuminate\Database\Eloquent\Model::setAttribute(), 1 passed

Temporal fix
change  const UPDATED_AT = null; to public $timestamps = false;
and set manually data to created_at or in BD set defalt current_timestamp()  to created_at column.
It works for me.

I am not sure from where you got that idea to define const UPDATED_AT = null.

It was worked fine since 5.0 =) Just experimented myself.

@Manfred047 Thanks for the possible solution, but I'll prefer to add updated_at column for my case. There is no possibility to update records, but I don't want to add one more hacky fix for it. It seems Laravel not designed to work with single created_at timestamp.

Actually the suggestion is the least hacky thing here. Laravel provides a simple way to add created_at and updated_at fields to your models. If you need something different, then the solution is to implement it yourself. In Laravel, you do this by setting $timestamps to false on your model then implement your own fields.

try with setAttribute, example
in your model
public function setCreatedAtAttribute($value) {     $this->attributes('created_at') = \Carbon\Carbon::now(); }
remember set $timestamps = false;

@Manfred047 if you are setting $timestamps = false then setCreatedAtAttribute method wouldn't be called automatically. And you've got a small issue with attributes assigning in code block, here is how it should looks like:
public function setCreatedAtAttribute($value)
{
    $this->attributes['created_at'] = \Carbon\Carbon::now();
}

As @devcircus said there is a possiblity to create special trait which will fill created_at attribute on model saving event. That seems to be clean and transparent solution.

Hah... one more hack found. Just add to your model this method and keep $timestamps = true:
public function setUpdatedAt($value)
{
    return $this;
}

Thanks to all of you guys for helping to find all possible ways to solve an issue. As for me this issue could be closed because null UPDATED_AT constant was worked for a long time but wasn't documented ever.
It wouldn't be hard to extend current HasTimestamps trait to omit updated_at Model's attribute but that's another story.

I pointed out the breaking change on the following PR but never got any reply xD
https://github.com/laravel/framework/pull/19627

@kamui545 I've proposed a solution to stop people using such hacks and standartize models without updated_at column: https://github.com/laravel/framework/pull/20930 but there is no plans to add this functionality.

Yup I thought so, this is why I ended up adding those fields even if I don't use it.
Thanks for letting me know.

It's very odd const UPDATED_AT = null is no more a thing, I was using like so a lot in my models, where I do not need updated_at column...

@linaspasv you can find solution above: https://github.com/laravel/framework/issues/20901#issuecomment-326713868
This should work in all 5.x versions.

@a-komarev yes, I have tried it, but it does not seem to work for update actions, still getting - "message": "SQLSTATE[42S22]: Column not found: 1054 Unknown column 'updated_at' in 'field list' .
const UPDATED_AT = null; was so elegant workaround...

oh it seems, I need to write like this now (const UPDATED_AT = null was missing)
    public $timestamps = true;

    const UPDATED_AT = null;

    public function setUpdatedAt($value)
    {
        return $this;
    }

You don't need $timestamps property because it's true by default. And remove UPDATED_AT constant declaration.
Result should be:
public function setUpdatedAt($value)
{
    return $this;
}

@a-komarev without UPDATED_AT constant it doesn't work. :-)

Seems strange. It works for me and @rodrigopedra confirmed this solution too: https://github.com/laravel/framework/issues/21045#issuecomment-327593582

Here is live example: https://github.com/cybercog/laravel-likeable/blob/master/src/Models/Like.php#L52

Hi, @a-komarev  in your package works but I also try with that solution in a model of its own and it does not work. I have the same problems as @linaspasv

I am running a simple model without update_at field. Without const UPDATED_AT = null it still tries to update the missing field.
namespace App\Models;

use Illuminate\Database\Eloquent\Model;

class Fingerprint extends Model
{
    protected $table = 'fingerprints';
    protected $casts = [
        'snapshot' => 'array'
    ];

    const UPDATED_AT = null;

    public function setUpdatedAt($value)
    {
        return $this;
    }
}

It seems that there is something that influences. In a new installation if the solution works, but in my project already advanced does not work.
    public function up()
    {
        Schema::create('tests', function (Blueprint $table) {
            $table->increments('id');
            $table->string('name');
            $table->timestamp('created_at')->nullable();
        });
    }

namespace App;

use Illuminate\Database\Eloquent\Model;

class Test extends Model
{
    protected $fillable = [
        'name',
    ];

    public function setUpdatedAt($value)
    {
        return $this;
    }
}

Route::get('test', function () {
    $test = new \App\Test();
    $test->name = 'tutututu';
    $test->save();

    dd($test);
});

The above example works on a new installation.

Sad this breaking change wasn't mentioned :/

@mr-feek it should work again in the next minor release as of #21178 PR

When a hack quits working it doesn't qualify as a breaking change.

Yep. This feature wasn't documented somewhere. So it could be classified as bug.

There are many undocumented features that are only found when reviewing the source code of the framework. Github is a good source to learn new things.


Adding more than one platform

I’m trying to add cmd2 platform, however only the tp-link platform and my roku tv accessory are being detected

If the other platforms are being detected, it's not a problem of the container, but might be the config and/or Homebridge itself.


Getting Compiler error

ai.api.util.BluetoothController file is missing

Hi, @sudheepsnair !
This problem is due to the new version of the library that has not yet been published.
Today library will be published
also you can change settings in the apiAISampleApp/build.gradle
//compile 'ai.api:sdk:1.6.1@aar'
compile project(':ailib')


Star Catching game

Description
Hi, I am Shreya. I'm GSSoC22 participant.
I want to add Star Catching Game  with proper documentation  .
Code of Conduct

[X] I follow Contributing Guidelines of this project.

/assign


On Switching Files file is not selected in left pane

Issue Type: Bug
Hello
When i switch between files files are no longer selected in left tree.,
Thank you.
VS Code version: Code - Insiders 1.27.0-insider (b00ab5288f314f6ef8d82923d89a0555ad15eb06, 2018-08-16T09:38:37.976Z)
OS version: Windows_NT x64 10.0.17134

System Info

Item
Value

CPUs
Intel(R) Core(TM) i5-6260U CPU @ 1.80GHz (4 x 1800)

GPU Status
2d_canvas: enabledchecker_imaging: disabled_offflash_3d: enabledflash_stage3d: enabledflash_stage3d_baseline: enabledgpu_compositing: enabledmultiple_raster_threads: enabled_onnative_gpu_memory_buffers: disabled_softwarerasterization: enabledvideo_decode: enabledvideo_encode: enabledwebgl: enabledwebgl2: enabled

Memory (System)
15.89GB (3.76GB free)

Process Argv
C:\Users\Sergey Kuchuk\AppData\Local\Programs\Microsoft VS Code Insiders\Code - Insiders.exe

Screen Reader
no

VM
0%

Extensions (10)

Extension
Author (truncated)
Version

ng-template
Ang
0.1.9

npm-intellisense
chr
1.3.0

path-intellisense
chr
1.4.2

vscode-eslint
dba
1.4.12

tslint
eg2
1.0.34

vscode-scss
mrm
0.6.2

tsimporter
pmn
1.2.14

typescript-hero
rbb
2.3.2

vscode-icons
rob
7.25.0

stylelint
shi
0.39.0

Did you set the explorer.autoReveal setting?

Hello
This setting is enabled

Navigation is not working anymore since this build.

I have a workspace with project and additional folder. When i press Ctrl+T and navigate through it to file editor tree is still folded and i dont see files near

Rigit click on file and press 'Reveal on Side Bar' does not do anything as well

I can reproduce:

be on Windows
have an empty window
File > Open > pick 2 folders
You are now in an untitled workspace with 2 folders
quick open a file from one folder
🐛 the file is not revealed in the explorer

Seems like a bad check around here where we have an uppercase drive letter in the explorer root but a resource with a lowercase drive letter:

My understanding is that for resources the drive letter should always be lowercase.
/cc @isidorn

It would be cool if you can publish fix, because its not comfortable to work now.

!


Set-MailboxMessageConfiguration has no effect

We have been successfully updating OWA signatures using Set-MailboxMessageConfiguration for the past 6+ months. Suddenly, and with no change on our part, Set-MailboxMessageConfiguration has started to have no effect. Our business heavily depends on this cmdlet and we would really appreciate your feedback/guidance. Someone else posted the same issue on SO here: https://stackoverflow.com/q/69764573/152630.
Example (that previously worked):
Set-MailboxMessageConfiguration -Identity<EMAIL_ADDRESS>-SignatureHTML "My new sig" -AutoAddSignature $True -AutoAddSignatureOnReply $True

Interestingly, after manually running Set-MailboxMessageConfiguration in a local PowerShell, we see the correct result in Get-MailboxMessageConfiguration (https://www.screencast.com/t/X9i4BY1jSb) but NOT in the OWA UI. Please advise.

Any guidance on the matter would be greatly appreciated

@leewisestamp, the best way for you to get an answer is to open a support ticket. The fact that this feature worked fine and then suddenly stopped working indicates some kind of problem that's beyond documentation.
Report back here with your findings.

@chrisda Obviously, we did that in parallel to opening this documentation ticket. So far Support has no answers other than a shaky workaround that will effectively ruin our product.
And I disagree that this is beyond documentation because if the cmdlet behavior has changed (e.g. to support multiple signatures in OWA) without that being documented (e.g. by adding a new parameter to the cmdlet to specify which signature should be updated), then that is a gap in documentation.

@leewisestamp, the issue is determining whether this is a deliberate feature change or some transitory problem that's going to get fixed. The answer to those questions determines whether we update documentation or not.
So is your ticket still open? Are they looking into it and gave you the lame workaround as a stop-gap until they can find out what's going on? Or did they say "that's the way it is" and close your ticket? And are you saying that there are new undocumented parameters/behavior that need to be documented?

@chrisda I don't work for MSFT so your team is far better qualified to determine if this deliberate or a bug.
Our ticket is still open with effectively no progress for 2 days other than the lame workaround and "we're looking into it".
As regards undocumented OWA behavior, multiple test accounts of ours inexplicably received the following "multiple signatures" functionality which we can't find documented anywhere.

My comment about a potentialy discrepancy between Set-MailboxMessageConfiguration and OWA is pure speculation. Again, I don't work for MSFT and I have no official or unofficial documentation supporting my speculation other than the problem we're seeing (and which a couple of others have now reported on StackOverflow).

Also, where should a bug in the cmdlet be reported if not here?

In my organization we also depend heavily Set-MailboxMessageConfiguration cmdlet.  @leewisestamp probably found something here. In my organization there are users that have the functionality with multiple signature and these are the ones where cmdlet doesn't work anymore. Mailboxes of users that have 'old' functionality with only one single signature, are working properly (signatures and settings are updating with cmdlet).

@wojcib, understood. Attempting to find answers. If you haven't already, I would also suggest opening a support ticket.

It's not limited to this project : we're also impacted when using the Dictionary of UserConfiguration in C# .NET (following instructions from https://social.msdn.microsoft.com/Forums/en-US/0b654e7f-2206-44bb-a595-7eed4c299c5b/how-to-create-an-owa-email-signature-by-using-ews?forum=exchangesvrdevelopment).
We're in the same position as you : the code does update the configuration for the user on OWA, but this isn't reflected in the new UI.
Maybe Microsoft decided to store its signatures elsewhere ?
@leewisestamp,  I'm interessed if you found anything to address this issue.

Any insights? Thanks in advance. To be clear, this is very urgent for us.

Any update of this? my project in C# was also affected in the same way as @David-Forlen-Themis

No updates. I strongly encourage any of you who haven't already to open a support ticket about this.

I noticed the same problem today; opened a new ticket

I noticed the same problem today; opened a new ticket

Any progress with your ticket? Our Premium support ticket has been opened for nearly two weeks with the only reply being "we're still looking into it".

I noticed the same problem today; opened a new ticket

Any progress with your ticket? Our Premium support ticket has been opened for nearly two weeks with the only reply being "we're still looking into it".

it's the first ticket in history where I've not been called back in a few minutes.
Stilll no answers

Same issue here. First support ticket opened 1 month ago. Support had not workaround neither resolution. Some users have multiple signature feature enabled and for these users cmdlet set-mailboxmessageconfiguration does not work. Other ticket opened last week. No reply from Microsoft.

I noticed the same problem today; opened a new ticket

Any progress with your ticket? Our Premium support ticket has been opened for nearly two weeks with the only reply being "we're still looking into it".

No words!

No updates. I strongly encourage any of you who haven't already to open a support ticket about this.

thank you for suggestion but the opened tickets have no reply from Microsoft.

Please don't let the lack of response scare you from opening a support ticket. Volume is important here. The more people that open tickets about the issue, the higher the escalation likely will be.

Please don't let the lack of response scare you from opening a support ticket. Volume is important here. The more people that open tickets about the issue, the higher the escalation likely will be.

I have opened the ticket but Microsoft does not reply. (for the same issue I have opened 3 tickets).
thank you!

Microsoft is closing the tickets saying they don't support scripts

I would rephrase the issue:

Any mailbox that allows the configuration of multiple signatures in Outlook on the Web no longer recognizes or uses the SignatureHTML value that's configured on the mailbox using the Set-MailboxMessageConfiguration cmdlet like it used to (for years). So where are the multiple Outlook on the Web signatures now stored, and how can we manage them using PowerShell cmdlets?

That's the fundamental issue.

If the user Deletes there current signature from Outlook Online and ensures both For New Messages, For Replies/Forwards = (No signature) this then oddly falls back to whatever is defined in the SignatureHTML property

If the user Deletes there current signature from Outlook Online and ensures both For New Messages, For Replies/Forwards = (No signature) this then oddly falls back to whatever is defined in the SignatureHTML property

I checked and your observations are correct. But it only works when user clicks 'Delete' (right above signature) from user's OWA interface.
I tried to script that somehow but had no luck.

If the user Deletes there current signature from Outlook Online and ensures both For New Messages, For Replies/Forwards = (No signature) this then oddly falls back to whatever is defined in the SignatureHTML property

I checked and your observations are correct. But it only works when user clicks 'Delete' (right above signature) from user's OWA interface. I tried to script that somehow but had no luck.

There's a user element at play here; we maybe able to determine the graph call used via that 'Delete' action using the Edge development tools but I'm not sure it'll be something we could interface with without a user token (auth) but this is speculative as I've not had an opportunity to investigate this potential approach yet - maybe worth a look if someone has the time

If the user Deletes there current signature from Outlook Online and ensures both For New Messages, For Replies/Forwards = (No signature) this then oddly falls back to whatever is defined in the SignatureHTML property

This works but you have to delete all signatures then set For New Messages, For Replies/Forwards = (No signature), like he said and Save. This creates a new signature called "Signature Outlook Web" with the content of the SignatureHTML property.
You can update/edit this signature in OWA but that doesn't update/edit the SignatureHTML property.
You can update/edit this signature with Powershell (cmdlet) but this takes a few minutes and doesn't work all the times ( I don't know why)

If the user Deletes there current signature from Outlook Online and ensures both For New Messages, For Replies/Forwards = (No signature) this then oddly falls back to whatever is defined in the SignatureHTML property

This works but you have to delete all signatures then set For New Messages, For Replies/Forwards = (No signature), like he said and Save. This creates a new signature called "Signature Outlook Web" with the content of the SignatureHTML property.
You can update/edit this signature in OWA but that doesn't update/edit the SignatureHTML property. You can update/edit this signature with Powershell (cmdlet) but this takes a few minutes and doesn't work all the times ( I don't know why)

tried it and it doesn't work.
actually it worked on one account and not on all the others.

OFFICIAL STATEMENT FROM MICROSOFT:
the problem was introduced in July, with this feature (Outlook for windows roaming signatures):
https://www.microsoft.com/en-ie/microsoft-365/roadmap?filters=&searchterms=60371
the problem has been escalated and any news will be published here:
https://techcommunity.microsoft.com/t5/exchange/roaming-signatures-for-outlook-for-windows/m-p/1398915
unfortunately, no ETA

If the user Deletes there current signature from Outlook Online and ensures both For New Messages, For Replies/Forwards = (No signature) this then oddly falls back to whatever is defined in the SignatureHTML property

This works but you have to delete all signatures then set For New Messages, For Replies/Forwards = (No signature), like he said and Save. This creates a new signature called "Signature Outlook Web" with the content of the SignatureHTML property.
You can update/edit this signature in OWA but that doesn't update/edit the SignatureHTML property. You can update/edit this signature with Powershell (cmdlet) but this takes a few minutes and doesn't work all the times ( I don't know why)

tried it and it doesn't work. actually it worked on one account and not on all the others.

I found that this also seems to be impacted by the browser cache, maybe worth a clearing it

OFFICIAL STATEMENT FROM MICROSOFT:
the problem was introduced in July, with this feature (Outlook for windows roaming signatures): https://www.microsoft.com/en-ie/microsoft-365/roadmap?filters=&searchterms=60371
the problem has been escalated and any news will be published here:
https://techcommunity.microsoft.com/t5/exchange/roaming-signatures-for-outlook-for-windows/m-p/1398915
unfortunately, no ETA

No, I don't think this is related since this feature is explicitly for Outlook for Windows and not (explicitly) related to OWA.

OFFICIAL STATEMENT FROM MICROSOFT:
the problem was introduced in July, with this feature (Outlook for windows roaming signatures): https://www.microsoft.com/en-ie/microsoft-365/roadmap?filters=&searchterms=60371
the problem has been escalated and any news will be published here:
https://techcommunity.microsoft.com/t5/exchange/roaming-signatures-for-outlook-for-windows/m-p/1398915
unfortunately, no ETA

No, I don't think this is related since the feature you referenced is explicitly for Outlook for Windows and not (explicitly) related to OWA.

outlook for win SHOULD sync signatures with OWA since july.

OFFICIAL STATEMENT FROM MICROSOFT:
the problem was introduced in July, with this feature (Outlook for windows roaming signatures): https://www.microsoft.com/en-ie/microsoft-365/roadmap?filters=&searchterms=60371
the problem has been escalated and any news will be published here:
https://techcommunity.microsoft.com/t5/exchange/roaming-signatures-for-outlook-for-windows/m-p/1398915
unfortunately, no ETA

No, I don't think this is related since the feature you referenced is explicitly for Outlook for Windows and not (explicitly) related to OWA.

outlook for win SHOULD sync signatures with OWA since july.

There is no mention in the roadmap item (or the techcommunity post) of OWA. Anyway, I don't think this is related to the issue we're all facing.

@leewisestamp as advised by Chris multiple times, reporting support is the only way. We are here to improve  the documentation only. Proceed to close it. Thanks for your contribution.

@yogkumgit And as I previously replied, I disagree that this is unrelated documentation. Until someone from Microsoft confirms one way or the other (i.e. if the product changed and therefore docs need updating, or if the product broke and therefore docs are good), this ticket should remain open!
https://github.com/MicrosoftDocs/office-docs-powershell/issues/8537#issuecomment-960574889

Already have the problem in july and it disapeared like it appears.
No problem since july...
My july ticket give me a poor explication and workaround (in french) :
Voici le plan d’action/Plan d’analyse/Troubleshooting de MS :
○ 1. Naviguez dans Outlook en ligne -> icône de l'engrenage -> Afficher tous les paramètres d'Outlook.
○ 2. Naviguer dans Courrier -> Composer et répondre
○ 3. Définissez "Annuler l'envoi" à 0 et enregistrez.
(S'il est déjà à 0, donnez-lui une autre valeur et enregistrez, puis remettez-le à 0).
We have a formate signature design by our administration (gouvernment ministry).
The goal off a feature for outlook store in the cloud is cool, so we could have one script to configure OWA, Outlook desktop and outlook mobile.
But it must be document.
And why is the multiple signature come before cloud storage off signature.
:-(

Hello,
is there a solution? I have the same problem

Hello,
same here.
It works individually "If the user Deletes there current signature from Outlook Online and ensures both For New Messages, For Replies/Forwards = (No signature) this then oddly falls back to whatever is defined in the SignatureHTML property."
But isn't a solution if you have hundreds of accounts to manage or updates.
I can't believe there is no documentation or solution about that :-(

@alesysadmin75, @TOH2F and anyone else: if this change in functionality affects you, I highly recommend that you open a support case about it if you haven't already.

Here is my advice for everyone that would like the cmdlet to work again. What I did:
In portal.office.com -> Administration -> Help -> Create new ticket.
In my particular case it took Microsoft 3 weeks, to disable 'multiple signatures' functionality. The powershell cmdlet works now.
There is no workaround. Only disabling mutliple signatures functionality by MS support.

So documentation is wrong for many people and we can't mention it in
documentation?
On Sat, Jan 8, 2022, 18:15 wojcib @.***> wrote:

Here is my advice for everyone that would like the cmdlet to work again.
What I did:
In portal.office.com -> Administration -> Help -> Create new ticket.
In my particular case it took Microsoft 3 weeks, to disable 'multiple
signatures' functionality. The powershell cmdlet works now.
There is no workaround. Only disabling mutliple signatures functionality
by MS support.
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/office-docs-powershell/issues/8537#issuecomment-1008068493,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJWWF7B2JUU6PPMYSARSKH3UVBWL3ANCNFSM5HCLJBHQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

I have created ticket with MS support on 11th of January, but they still playing with me.
@wojcib what would you advise to ask Microsoft exaclty to do?
Description: issue described here: https://github.com/MicrosoftDocs/office-docs-powershell/issues/8537 [github.com] As a solution please disable multi signatures for our tenant.

I opened the ticket just 1 week ago.
Microsoft just called me. They disabled 'Roaming signature' on our tenant and they confirmed it as only workaround by now.

@yogkumgit why is this issue closed when there has been no update to the documentation?
Also no explanation on why it is closed without being addressed. 🤬
@chrisda Feel free to reopen again. ;)

@yogkumgit why is this issue closed when there has been no update to the documentation? Also no explanation on why it is closed without being addressed. 🤬
@chrisda Feel free to reopen again. ;)

Agree 100%

Are there any updates on this or progress towards a Graph API alternative? We have been needing to use this cmdlet for months and there's seemingly no movement from Microsoft's end! When I contacted support I was told there would be a solution soon, so it wouldn't be necessary to disable roaming signatures (this was a couple of months ago).

Support just disabled roaming signatures for our tenant some time ago. It
works since.
On Sun, Apr 17, 2022, 21:20 Tom Herring @.***> wrote:

Are there any updates on this or progress towards a Graph API alternative?
We have been needing to use this cmdlet for months and there's seemingly no
movement from Microsoft's end! When I contacted support I was told there
would be a solution soon, so it wouldn't be necessary to disable roaming
signatures (this was a couple of months ago).
—
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/office-docs-powershell/issues/8537#issuecomment-1100935470,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJWWF7DMYVA3X4TLGCRT6FDVFRQAFANCNFSM5HCLJBHQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***
com>

Support can disable the roaming signatures function.
They told me last week that it will be completed (and hopefully working) in July 2022.
They have no info on PowerShell api

The main issue here is still that there is no documentation about this cmdlet not working (in some cases?), and explanation as to why. MS claims this is not in a public release, and that disabling roaming signatures "resolves" the issue, totally ignoring the fact that any existing signatures seems to be lost in the process.
Real fix should be out when roaming signatures is GA, which I think it already is, so confusing! https://www.microsoft.com/en-in/microsoft-365/roadmap?filters=&searchterms=60371

I added the following note to the top of the SignatureHtml parameter description:

Note: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your organization. Currently, the only way to make this parameter work again is to open a support ticket and ask to have Outlook roaming signatures disabled in your organization.

If/when there's ever a way to disable Outlook roaming signatures yourself (or any other fix), I'll updated the note.
OK to close this issue now?

Thank you @chrisda for the update, good to finally have this documented, but what took so long? ;)
Still tho, why is roaming profiles even deployed when there is no cmdlets to manage them? When contacting support they just refer to the roadmap that roaming profiles will be deployed later in 2022 and that it at that time will be cmdlets available to manager signatures. but as we can see here, roaming profiles are already deployed. I think that roaming profiles should not be enabled as it has been. Disable roaming profiles for everyone, or have working cmdlets, do not enable roaming profiles again until cmdlets is available.

I added the following note to the top of the SignatureHtml parameter description:

Note: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your organization. Currently, the only way to make this parameter work again is to open a support ticket and ask to have Outlook roaming signatures disabled in your organization.

If/when there's ever a way to disable Outlook roaming signatures yourself (or any other fix), I'll updated the note.
OK to close this issue now?

Thanks, @chrisda. I think your comment suffices for this issue. Frustrating that it took over six months to get resolved and that we were left without a real fix to the original functionality. But, at least the documentation now accurately reflects what to expect. Cheers.

Ok, any progress on ability to set signatures for mailbox using powershell or graph api when using roaming signatures? It is July 2022. If this is a new feature, what is number # in Microsoft 365 roadmap?

Outlook for Windows: Signature cloud settings
Your Signature settings are stored in the cloud, so your experience is consistent when you access Outlook for Windows on any computer. This feature has been delayed and will only be available in Beta Channel.
Feature ID: 60371
Preview: September 2022
GA: October 2022
https://www.microsoft.com/en-us/microsoft-365/roadmap?searchterms=60371

Hello again, just an update
We have had the roaming feature disabled and can confirm this cmdlet now works, also confirmed Outlook roaming signatures feature is now disabled on the tenant and advised it will impact the release of the feature.
Findings however are contrary, when using the 'New' Outlook the cmdlet set signatures are present on the client (implying a roaming capability?) can the documentation at either clarify what the Outlook roaming signatures feature is and what disbaling it impacts or that stipulate that this cmdlet works when using the 'New' Outlook client?

@beail, this feature is now GA, so it is not anymore preview. It can be manually enabled on the tenant level still. Once enabled, Outlook Web App and Outlook desktop client uses the same signatures from cloud. I confirm that have several customers/tenants with this feature enabled and fully working.
What needs to be updated is the powershell and documentation for SignautreHtml parameter.

OK. Per #10111 I removed the note.

Hi,
Just to leave a quick feedback about this issue.
I was trying to use this command last week, October 28 to November 2, and it wasn't working.
Opened a ticket with support and in 1 week they disable Roaming for me, and works now.

I am not sure is it resolved or not.
Outlook Roaming is not anymore in beta, that is for sure.
But what is not sure, how to use PowerShell to set signature, when using Roaming on tenant features.
I believe this needs inspection from product group and update in docs still. For example in docs is not clear how to create multiple signatures for particular user and managed them. (again, this is not in beta anymore and is GA)

I'm confused. I had support disable roaming signatures in my organization a few months ago. Can I now have them re-enabled, but now be able to set SignatureHtml content via PowerShell? This is a pretty messy rollout.

Any updates on this issue? I am still unable to set an email signature using the Set-MailboxMessageConfiguration command.

I added the following note to the top of the SignatureHtml parameter description:

Note: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your organization. Currently, the only way to make this parameter work again is to open a support ticket and ask to have Outlook roaming signatures disabled in your organization.

If/when there's ever a way to disable Outlook roaming signatures yourself (or any other fix), I'll updated the note.
OK to close this issue now?

The documentation page for Set-MailboxMessageConfig does not have the warning message: https://learn.microsoft.com/en-us/powershell/module/exchange/set-mailboxmessageconfiguration?view=exchange-ps

@tdannecy, I was told to remove that note per this issue #10111. Was that guy wrong?

It seems that the only way to set signatures via PowerShell is still to disable roaming profiles, and it would seem that the only way to do that is to contact support and wait for them to figure out what you're talking about. (Especially now that it's not in the documentation.)
But ultimately the hope is that the PowerShell command or its underlying API are fixed such that they start to work with roaming profiles.
There are several problems:

Can't set signatures when roaming profiles are enabled.
The tenant admin can't readily see whether roaming profiles are enabled, and certainly can't control that setting.
If or when these issues are fixed, I'm not sure how we tenant admins would know about the fix, nor how to test it without a weeks-long dance with support.

From: Chris Davis @.>
Sent: Wednesday, December 14, 2022 6:09:12 PM
To: MicrosoftDocs/office-docs-powershell @.>
Cc: James K. @.>; Manual @.>
Subject: Re: [MicrosoftDocs/office-docs-powershell] Set-MailboxMessageConfiguration has no effect (Issue #8537)
@tdannecyhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftdannecy&data=05|01||f38ecacb3c644df99f8708dade283780|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638066561559094976|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=X5k7HEcq8DIGNZ2DDG8LAwu%2BOAHt2nns1S0NFFSZSCk%3D&reserved=0, I was told to remove that note per this issue #10111https://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Foffice-docs-powershell%2Fissues%2F10111&data=05|01||f38ecacb3c644df99f8708dade283780|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638066561559094976|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=HFBa4r3jCdXOnKqNAzlso2KhJ5dHErshpkBh1p2Bzjo%3D&reserved=0. Was that guy wrong?
—
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Foffice-docs-powershell%2Fissues%2F8537%23issuecomment-1352342306&data=05|01||f38ecacb3c644df99f8708dade283780|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638066561559094976|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=kZe0YzucQ1Su8xFtLkdvcynclPXzcBJLAI5OgFKsc%2B4%3D&reserved=0, or unsubscribehttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAAJOK5ZA6WZFJBREVZSQCXTWNJHRRANCNFSM5HCLJBHQ&data=05|01||f38ecacb3c644df99f8708dade283780|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|638066561559094976|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|3000|||&sdata=HRCauBgknRDad4t%2BvlacJh%2FVoNHHSzsAanemcQWvimY%3D&reserved=0.
You are receiving this because you are subscribed to this thread.Message ID: @.***>

If this for whatever reason this doesn't currently work (as Microsoft promised it would over a year ago) then Microsoft really really needs to get their act together and get this fixed. [Case #:30105210]
Not to mention that removing these details if it doesn't work, If Microsoft can't confirm this working @chrisda ?? then we need a revert of the documentation quickly, and then we need to have this fixed (again this was guaranteed to be working by Microsoft when it was GA, even tho MS already have made this feature GA and then taken that back)
Support ticket is the only way to switch back from roaming signatures.

OK. I'll put the note back in.

Note: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your organization. Currently, the only way to make this parameter work again is to open a support ticket and ask to have Outlook roaming signatures disabled in your organization.

Does the registry setting discussed in this topic offer any relief from having to open a support ticket?

Does the registry setting discussed in this topic offer any relief from having to open a support ticket?

No, setting DisableRoamingSignaturesTemporaryToggle in the registry only changes the behavior of Outlook on Windows, but has no influence on Outlook Web and if roaming signatures are enabled in Exchange Online at tenant or mailbox level.

@chrisda please reopen this GitHub issue since it is not resolved. What did product group say about this PowerShell cmdlet now when the roaming signatures are GA ?

OK Original statement added back. @hkusulja, I have nothing to report.

@chrisda previously it was stated that this limitation is temporary until outlook roaming signatures are not GA, now they are GA for months but still limitation via PowerShell persists. I believe that then Exchange Online - API and PowerShell module needs to be updated (as product group feedback). Just to be on safe side, sharing now also this here - https://feedbackportal.microsoft.com/feedback/idea/46c270e4-7981-ed11-a81b-000d3ae32cd0

@hkusulja, all of what you're saying sounds good, but all I can do here is fix documentation for the Set-MailboxMessageConfiguration cmdlet reference topic, which should now (again) be accurate.
If you haven't already, I highly encourage you and anyone else affected to open a support ticket about this. The product teams see this information.

Case #34380403

@chrisda Microsoft support ticket does not help. They just point to this documentation and statement that is there, and do not go further, nor the product group, or without any progress or answer.

I realize there probably won't be immediate gratification, but the volume of support tickets about an issue is noticed by the people who need to see it.

Our signature scripts are broken as well.

The doc still states to contact support for the workaround
https://learn.microsoft.com/en-us/powershell/module/exchange/set-mailboxmessageconfiguration?view=exchange-ps#examples
The post on feedbackportal only contains outdated information about the roadmap
https://feedbackportal.microsoft.com/feedback/idea/46c270e4-7981-ed11-a81b-000d3ae32cd0
On the roadmap the entry is in preview again with GA: April 2023
https://www.microsoft.com/en-us/microsoft-365/roadmap?searchterms=60371&filters=&searchterms=60371

And can we re-open this github bug so people coming here have the correct information without reading the whole thread?
I opened a support ticket with all the above information and was immediatly told this is a known issue and that they will notify me as soon as it is resolved.

Wanted to add in here and say this has been broken for our thousands of users for a few months now, at least.
We would push out the HTML signatures via PowerShell script, which would update the OWA signatures for our users. However, we estimated ever since this has switched to the multiple signature option/dropdown, the signatures do not show or apply correctly.
If we open another user's mailbox via the OWA option, the other user's signature shows correctly (no multiple signature dropdown is shown). However, if that user, or even myself, try to view our own signature, it does not show the recently applied signature, or any at all in most cases (and it shows the single signature option). This leads me to believe the multiple signature feature clearly is broken.
Support ticket has been open for well over a month with constant back and forth, logs, screen captures, calls, etc. but with no resolution or any ideas.  No resolution yet...

I opened a ticket asking the feature to be disabled on our org on march 8th, even linked the documentation note and this thread. Had to give them lots of info and still no one even tried to disable the feature.

Just to add to the fun, we're having the same issues.
On one of our tenants Microsoft disabled roaming signatures and we're able to sucessfuly deploy the signatures, however we're still having issues on another tenant, although it briefly worked after MS disabled the roaming, it appears to have stopped for some reason. MS Support on this most recent problem seems not able to resolve the issue, instead wanting a remote session which won't help...

Wanted to add for the thread that today Support is telling me that disabling Outlook Roaming Signatures for OWA is no longer possible. It's "enabled globally" and for some sort of security reasons it cannot be disabled. No guidance was provided on how we are to administer signatures at this time.

@chrisda It's kind of weird that we cant have this working, it is way past the date of promise from support that this should have been fixed, especially if we now even cant disable roaming profiles!

Wanted to add for the thread that today Support is telling me that disabling Outlook Roaming Signatures for OWA is no longer possible. It's "enabled globally" and for some sort of security reasons it cannot be disabled. No guidance was provided on how we are to administer signatures at this time.

This is frustrating :/ We've still got a call open with MS about this so wonder if we'll eventually get the same response

@chrisda why is this not reopened , again, workaround / reverting back does not help anymore. Please ask product group about this documentation.

With the new outlook version fixing this is imperative, I cant ask the entire company to copy paste their signatures from before!

Thank you for reopening this. Hopefully this actually will make some progress!

Keep in mind, this isn't a support ticket. You, me, or anyone else can close and open GitHub issues. The product team does not watch these issues; only guys like me who are interested in documentation updates do.

Keep in mind, this isn't a support ticket. You, me, or anyone else can close and open GitHub issues. The product team does not watch these issues; only guys like me who are interested in documentation updates do.

Got it. We have had a support ticket opened for months with no progress. Good to know about this thread and keeping an eye on it for any progress that might be made.

Many are stating that they have had tickets open with no progress, or have had trouble communicating what needs to be done. I was able to have this change made for my org with the following request:

We can no longer use the Set-MailboxMessageConfiguration cmdlet to apply HTML signatures to mailboxes. This issue is well known and further explained here. https://github.com/MicrosoftDocs/office-docs-powershell/issues/8537. I am kindly requesting "Roaming Signatures" be disabled for our organisation as per advice.

Though I fully understand that there exists different levels of understanding between support units.

Many are stating that they have had tickets open with no progress, or have had trouble communicating what needs to be done. I was able to have this change made for my org with the following request:

We can no longer use the Set-MailboxMessageConfiguration cmdlet to apply HTML signatures to mailboxes. This issue is well known and further explained here. https://github.com/MicrosoftDocs/office-docs-powershell/issues/8537. I am kindly requesting "Roaming Signatures" be disabled for our organisation as per advice.

Though I fully understand that perhaps there is a different level of understanding between support units.

Many are stating that they have had tickets open with no progress, or have had trouble communicating what needs to be done. [...]
Though I fully understand that there exists different levels of understanding between support units.

Same here, we dropped our support request, because the support won't read this issue thread. They were only helping with looking at our powershell script and that's it... over 5 calls... No result at the end.

With the future version of Outlook, Set-MailboxMessageConfiguration is mandatory: we can't tell our users to change by the hand their own signature.
And knowing my users, our support team will have to do that for them, I can't ask that to my team.

Just wanted to chime back in here. I had two tickets opened (one for each of our tenants), and support FINALLY was able to opt us out of roaming signatures and now PowerShell command works perfectly! The roaming signature option is removed from our option for all users and the command pushed out successfully.
I really hope the documentation for this gets better, and for those of you looking to get this fixed, be persistent! It amazing how the new tenant we spun up got resolved within a week, but the other older tenant it is going on 2+ months and they're going in circles with "checking the logs" - yikes!
Before support opted us out:

After support opted us out:

Case 36208070

Can we point out that this is no real resolution to the issue? It is obvious that there should be an API update to be able to change roaming signatures. If this was an open source project it would have been done ages ago.

@yogkumgit Can you please explain in what way this issue has been resolved? If not why was it closed?

I reopend the issue, for what that's worth.
Fundamentally, this forum is for fixing documentation issues in Exchange-related PowerShell cmdlet reference topics (which includes Security & Compliance PowerShell). I realize the nature and duration of the problem has morphed this GitHub issue into something else, which I'm not insensitive to.
The documentation end of this problem has been fixed (then modified, then fixed again) a long time ago by stating the current reality in the SignatureHtml parameter description:

Note: This parameter doesn't work if the Outlook roaming signatures feature is enabled in your organization. Currently, the only way to make this parameter work again is to open a support ticket and ask to have Outlook roaming signatures disabled in your organization.

So, from the documentation end, this issue has been 'fixed', which is why this issue keeps getting closed.
My last big sweep in April of comparing what cmdlets/parameters are available to me in a plain Microsoft 365 E5 tenant vs. what's documented revealed no new cmdlets that looked like they would help with this issue. I'll probably due another sweep in July.
But, the fix for this issue is likely to come from outside of Exchange-related PowerShell, because the Outlook roaming signatures feature itself appears to operate outside of Exchange-related PowerShell (which explains why turning the feature off makes the world right again).

My little experience with that: I had to spend 3 weeks with the MS support (first mail explaining why I need to have this option activated on my domains, with links to issue, KB and other docs).
The support explained me how to add signature in my own box, .... Finally, when I answer that I knew that disabling this option will also disable the hability to have several signatures (I don't care about it, I don't want it, it's company preformated signature and I'll kill the first one which think to modify it :D), they uncheck the f*cking checkbox and my system works.
imho, the issue is that domain admin can't disable this feature, using powershell or web interface.

@leewisestamp Hope the comment by Chris is helpful for you. If you see a documentation update is required, please feel free to open an issue for the same. We proceed here to close it. Thanks for taking out some time to open the issue. Appreciate and encourage you to do the same in future also.

Today on navigating Microsoft's maze of annoyances

Set-MailboxMessageConfiguration still does not work and not all tenants or users see the new feature in Outlook Web.
I opened a support call last week, because my different Outlook clients already sync signatures but they do not show up in Outlook Web. Result: "This is expected behavior at the moment. They estimate the rollout to Outlook Web will finish by the end of July. We can't opt-in your tenant to bring the feature sooner."
As maintainer of the free and open-source core of Set-OutlookSignatures (https://github.com/GruberMarkus/Set-OutlookSignatures), I want to additionally share something that is good news for at least some of us in this thread: The first signature management solution for Outlook with support for roaming signatures has been released. The feature is only available in the commerical Benefactor Circle add-on and is marked experimental as there is no API officially released by Microsoft, but it works stable in the trial version: https://explicitconsulting.at/open-source/set-outlooksignatures/
The interesting thing is that the solution is independent of the Outlook version used. It downloads roaming signatures, treats them just like local ones during the signature update process, and then uploads all locally available signatures. The old Outlook Web single signature feature and the new multiple roaming signatures feature are supported at the same time, and it even does not matter if Outlook is configured to use roaming signatures or not.

@GruberMarkus but how can this feature work if there is no API ?

@GruberMarkus but how can this feature work if there is no API ?

By watching what the client really does in detail. I am sorry, I can't go into more details.

therfore, asking microsoft / product group to document this here

I intercepted the HTTP PATCH and inserted the HTML signature as needed, which works as expected.  Obviously though this is individual solution, not great for mass management.

Greetings. A new parameter named PostponeRoamingSignaturesUntilLater has been added to the Set-OrganizationConfig cmdlet that allows admins to turn off Outlook roaming signatures themselves without the need to open a support ticket. Setting this parameter to $true allows the signature-related parameters on the Set-MailboxMessageConfiguration cmdlet to work as expected.
It's being called a 'temporary' parameter because there will eventually be API access for admins to manage/configure Outlook roaming signatures directly, so there will be no need to turn off Outlook roaming signatures and/or use the signature-related parameters in Set-MailboxMessageConfiguration. After API access to roaming signatures is available, the PostponeRoamingSignaturesUntilLater parameter on Set-OrganizationConfig will be deprecated.
I've updated the signature-related parameter descriptions in Set-MailboxMessageConfiguration to mention this new parameter.
I'm happy to leave this issue open until the new API is available.

Hi chrisda
Thank you for the update! This sounds promising.
I've just set the PostponeRoamingSignaturesUntilLater function in our organization, but the signatures that are set with "Set-MailboxMessageConfiguration" are still not added to Outlook.com.
Is it because the function is not fully working yet?
I saw this comment from Microsoft:
Note: This parameter is in the process of being rolled out. The rollout is expected to be completed by mid-November 2023.

@yogkumgit  why is this added as complete? is documentation updated on how can you update signature settings using graph api or exchange powershell module for roaming signatures?

Dont think they did @hkusulja  this is the only documentation I could find
Graph api acces and set- command info should definetly be added imo.

question is how to set signatures when using roaming signatures, not without them or by disabling them :)

Reopening.

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!

This issue is still broken, and PS does not update Office 365 Signatures at all.  Any update on this?  Is there a spot where we can see the status on this bug / feature / issue?


Uberon and GO imports should bring in taxon axioms

We have virtually no taxon checking in CL because we don't bring in any TCs from external ontologies!!
At least we need uberon which is richest
Fixed by using uberon-base for imports

Hmm, looks like uberon base is lacking the never-ins, see for example http://purl.obolibrary.org/obo/UBERON_0000023

What are the concrete remaining action items here?


General Fixes

Explain the changes

Fix toggle link for maintenance section
Hide download and preview if the user cannot use them
Remove links to object if the object is uploading or delete marker in host parts table
Add a workaround for SVG k8s icon (use png inside an SVG)

Issues: Fixed #xxx / Gap #xxx

Testing Instructions:

Fixes #5660


ZEPPELIN-3236. Make grpc framesize configurable

What is this PR for?
Add one new property zeppelin.ipython.grpc.framesize which is an advanced configuration. By default it is 32M which should be sufficient for most of scenarios.
What type of PR is it?
[ Improvement ]
Todos

[ ] - Task

What is the Jira issue?

https://issues.apache.org/jira/browse/ZEPPELIN-3236

How should this be tested?

Unit test is added.

Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Thanks for the heads up, yep I figured out that I have to tune up zeppelin.ipython.grpc.framesize to a large number.
I looked over the PR. Two quick suggestions

Would it be possible to make spark interpreter keep and not close the stream if such an exception happens? We can see a higher limit, but I am sure users will have cases when they will try to go higher. The Spark interpreter is then in a bad state and only way to fix this is to try increase a limit again.. Not sure if this problem belongs to Zeppelin or to grpc, so provisionally opened an issue in grpc too - https://github.com/grpc/grpc-java/issues/4086
Should we increase the default? .. 4Mb isn't that hard to hit when ipython returns a mid-size dataset / table.

@Tagar , 4 Mb is the default value of gprc, I am fine to use another large. But from your error logs, your code will produce 200M data, I am curious to know how do you produce that, do you mind to paste your code to reproduce it ?
io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: io.grpc.netty.NettyClientTransport$3: Frame size 216695976 exceeds maximum: 4194304.

My main point was that this exception should be thrown to the user, so he or she has a chance to increase this limit. Currently if it breaks, only way to find out about this limitation is to enable debugging and not a lot of users can do that.

You're right .. it's 200M not sure how that user got that much data. That wasn't from my code, but from a colleague of mine. I guess it was a larger table of data. Would you mine making default somewhere in the range 16-32M? I think a lot of folks would run into the 4M limit.

Also, it would be great if IPythonInterpreter would catch exceptions better. Found another problem - https://issues.apache.org/jira/browse/ZEPPELIN-3239 - unrelated to this one, but it also shows the same symptoms to the user - Spark interpreter just becomes irresponsive.

@Tagar Do you have any sample code to reproduce this issue ? So that I can verify it and also may include it in unit test.

@zjffdu I don't have a reproducible case yet. This error hasn't been very consistent for me so it might be also a side effect of another problem. That's why I asked above if we could capture exceptions in grpc better. Also check what you think of the suggestion made in grpc/grpc-java#4086 to make a new grpc stream for each call?

@Tagar Can you paste the full log ? I'd like to see the full stacktrace.

ERROR [2018-02-14 10:39:10,922] ({grpc-default-executor-3} IPythonClient.java[onError]:138) - Fail to call IPython grpc
io.grpc.StatusRuntimeException: RESOURCE_EXHAUSTED: io.grpc.netty.NettyClientTransport$3: Frame size 216695976 exceeds maximum: 4194304.
at io.grpc.Status.asRuntimeException(Status.java:543)
at io.grpc.stub.ClientCalls$StreamObserverToCallListenerAdapter.onClose(ClientCalls.java:395)
at io.grpc.internal.ClientCallImpl.closeObserver(ClientCallImpl.java:426)
at io.grpc.internal.ClientCallImpl.access$100(ClientCallImpl.java:76)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.close(ClientCallImpl.java:512)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl.access$700(ClientCallImpl.java:429)
at io.grpc.internal.ClientCallImpl$ClientStreamListenerImpl$1StreamClosed.runInContext(ClientCallImpl.java:544)
at io.grpc.internal.ContextRunnable.run(ContextRunnable.java:52)
at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:117)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
INFO [2018-02-14 10:39:10,923] ({grpc-default-worker-ELG-1-2} AbstractClientStream2.java[inboundDataReceived]:249) - Received data on closed stream
INFO [2018-02-14 10:39:10,924] ({grpc-default-worker-ELG-1-2} AbstractClientStream2.java[inboundDataReceived]:249) - Received data on closed stream
INFO [2018-02-14 10:39:10,925] ({grpc-default-worker-ELG-1-2} AbstractClientStream2.java[inboundDataReceived]:249) - Received data on closed stream

@zjffdu that's what I have.. is this helpful? It seems contain full exception stack.

@Tagar Have you tried this PR ? Does this PR solve your issue ?

thank you @zjffdu - I will check this today.

@zjffdu I just verified this new commit and it works great.
Glad to see exceptions in ipython backend are now being captured correctly.
I wasn't able to actually test frame size problem, as it's hard to reproduce.
As @ejona86 said today in https://github.com/grpc/grpc-java/issues/4086#issuecomment-367053465

Note that something else is broken if you're seeing that error. You should not be receiving a frame that large. (Chances are it's not actually a frame length and we're seeing garbage.)

So I think that frame size error might be caused by some other problem.
But it's great we can make frame size configurable now.

LGTM
thanks a lot @zjffdu

@Tagar, I mis-read the error earlier. That message is just "gRPC message too large." It'd probably be good to talk about "messages" instead of "frames" here.

@ejona86 The error from grpc is about Frame size exceed

I just changed them to be more clear in grpc/grpc-java#4106. Each message gets its own gRPC frame, but the very fact there are gRPC frames is more of an internal detail; users shouldn't need to know about such things.

Thanks @ejona86

rename the property in #2813


Flyway 4.2.0 to 5.0.0

Which version and edition of Flyway are you using?
4.2.0
If this is not the latest version, can you reproduce the issue with the latest one as well? (Many bugs are fixed in newer releases and upgrading will often resolve the issue)
NA
Which client are you using? (Command-line, Java API, Maven plugin, Gradle plugin)
Java API
Which database are you using? (Type & version)
MySQL
Which operating system are you using?
Windows
What did you do? (Please include the content causing the issue, any relevant configuration settings, the SQL statement(s) that failed (if any), and the command you ran)
We are upgrading from 4.2.0 to 5.0.0 and we have provided property spring.flyway.table=schema_version.
We also have a multi tenant DB schema
What did you expect to see?
Newly created schemas after 5.0.0 upgrade should use old table name i.e. schema_version since we have provided that property
What did you see instead?
For newly created schema the metadata table name is flyway_schema_history

As you're relying on Spring's integration you may need to ask the people over at Spring if their integration supports flyway.table for your version
Another thing to try for now is setting flyway.table instead of spring.flyway.table
Closing for now

We tried with flyway.table as well but its same.
So lets assume we are not using spring integratoin. Now  if I am migrating to flyway 5.0.0 and have set flyway.table=schema_version.
Now if I create any new schema via flyway, the metadata table will be created as schema_version or flyway_schema_history?

Now if I create any new schema via flyway, the metadata table will be created as schema_version or flyway_schema_history?

schema_version

@DoodleBobBuffPants
Ok thanks for the reply. So for us for new schemas its creating the metadata table as flyway_schema_history even though we have provided the property in our config file(tried both flyway.table and spring.flyway.table).
So say if we have few old schemas with metadata table as schema_version and the newly created schemas after flyway 5.0.0 upgrade have metadata table as flyway_schema_history and we have also set the flyway.table property to schema_version. Will it now create any issue when we move to Flyway version 6.0.0?

Yes, the fallback mechanism is only available in version 5
To complete the upgrade you need to set table=schema_version then run repair to update the schema of the history table, and then you would need to keep table=schema_version going forwards
It's worth noting that this is only for existing schemas, new schemas will work fine without this


⚠ Bofrost.lu has degraded performance

In 551bb65, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 940 ms

Resolved: Bofrost.lu performance has improved in 62e8b39 after 6 minutes.


fixed the catalogues-db version for k8s deployment

fixed the catalogues-db version for k8s deployment in both the split and complete manifests

related to https://github.com/microservices-demo/microservices-demo/issues/533


Can not run the wasm example

After compiling &. building the tvm-wasm runtime followed by this doc, I am able to get the wasm package. However, when I try to run the demo example:
const path = require("path");
const fs = require("fs");
const tvmjs = require("../../dist");

const wasmPath = tvmjs.wasmPath();
const EmccWASI = require(path.join(wasmPath, "tvmjs_runtime.wasi.js"));
const wasmSource = fs.readFileSync(path.join(wasmPath, "tvmjs_runtime.wasm"));
// Here we pass the javascript module generated by emscripten as the
// LibraryProvider to provide WASI related libraries.
// the async version of the API.
tvmjs.instantiate(wasmSource, new EmccWASI())
.then((tvm) => {
    // List all the global functions from the runtime.
    console.log("Runtime functions using EmccWASI\n", tvm.listGlobalFuncNames());
});

I got the following errors:
missing function: main
-1
exception thrown: RuntimeError: abort(-1). Build with -s ASSERTIONS=1 for more info.,RuntimeError: abort(-1). Build with -s ASSERTIONS=1 for more info.
    at abort (/Users/ericli/Desktop/dev/tvm/web/dist/wasm/tvmjs_runtime.wasi.js:3:9655)
    at _main (/Users/ericli/Desktop/dev/tvm/web/dist/wasm/tvmjs_runtime.wasi.js:3:68366)
    at <anonymous>:wasm-function[1265]:0x48018
    at _start (<anonymous>:wasm-function[571]:0x28a83)
    at EmccWASI.Module.__start (/Users/ericli/Desktop/dev/tvm/web/dist/wasm/tvmjs_runtime.wasi.js:3:88834)
    at callMain (/Users/ericli/Desktop/dev/tvm/web/dist/wasm/tvmjs_runtime.wasi.js:3:89545)
    at doRun (/Users/ericli/Desktop/dev/tvm/web/dist/wasm/tvmjs_runtime.wasi.js:3:90124)
    at run (/Users/ericli/Desktop/dev/tvm/web/dist/wasm/tvmjs_runtime.wasi.js:3:90296)
    at runCaller (/Users/ericli/Desktop/dev/tvm/web/dist/wasm/tvmjs_runtime.wasi.js:3:89392)
    at removeRunDependency (/Users/ericli/Desktop/dev/tvm/web/dist/wasm/tvmjs_runtime.wasi.js:3:9402)

Any insight on how to fix it?
Thanks in advance!

Should be fixed by the lastest main. Thanks @WenheLI  for reporting the issue


Current temperature  HEAT PUMP C3

HA core version
2023.11.3
Intergration version
0.3.22
Device type and model
Heat Pump Wi-Fi Controller 171H120F (0) da Midea
Used App
MSmartHome
The description of problem
current_temperature is null
This is state of climate:
hvac_modes: off, auto, cool, heat
min_temp: 17
max_temp: 30
target_temp_step: 0.5
current_temperature: null
temperature: 21
zone1_power: true
zone2_power: false
dhw_power: false
zone1_curve: true
zone2_curve: false
disinfect: false
fast_dhw: false
zone_temp_type: false, false
zone1_room_temp_mode: true
zone2_room_temp_mode: false
zone1_water_temp_mode: false
zone2_water_temp_mode: false
silent_mode: true
eco_mode: false
tbh: false
mode: 3
mode_auto: 3
zone_target_temp: 40, 40
dhw_target_temp: 39
room_target_temp: 21
zone_heating_temp_max: 65, 65
zone_heating_temp_min: 35, 35
zone_cooling_temp_max: 25, 25
zone_cooling_temp_min: 5, 5
room_temp_max: 30
room_temp_min: 17
dhw_temp_max: 60
dhw_temp_min: 20
tank_actual_temperature: 25
target_temperature: 21, 21
temperature_max: 30, 30
temperature_min: 17, 17
total_energy_consumption: 113
status_heating: false
status_ibh: false
total_produced_energy: 400
outdoor_temperature: 14
error_code: 0
icon: mdi:air-conditioner
friendly_name: Pompa di calore
supported_features: 1
The logs
No response

current temperature must is the indoor temperature detected from HMI.
In the climate.py at class MideaC3Climate(MideaClimate)::
@property
    def current_temperature(self):
        return None

Why return none? and not :
return self._device.get_attribute(C3Attributes.current_temperature)