Problem with non ASCII characters in file names.

If the file is uploaded with a file name that has non ASCII characters,  Papermerge can't process it. It shows a broken Icon. If the same file is renamed before upload with only ASCII characters in its filename, then everything works. I've tried it in the docker version.

Hi @N3tFX,
can you please be more specific?
What non ASCII characters are used in file name ? Was it a pdf file ? Or maybe jpeg, tiff, png ? Was there another OCR background job running (working crunching another file in meantime)?

Basically, ASCII characters https://en.wikipedia.org/wiki/ASCII are the ones used in the English language and numbers. By non ASCII characters I am referring to characters that are not part of the English language. And I have tried it with pdf, jpg and png files. It was the file name that was the problem. When I renamed them with English characters from the ASCII table, everything worked. And no OCR was running in the background as these files where the first I've tried to upload.

@N3tFX,
I tested application with German letters e.g. Änderungen.pdf, with Russian cyrillic e.g. файл.pdf and it worked as expected.
What characters did you use ?

I have tried it in many other languages, even Japanese. Only if the filename is in English it uploads correctly. Remember, I am using the docker version (v1.4.2). Maybe this happens only in the docker container. By the way here is an error message I see in the logs when I upload a file with non English characters in the file name:
`UnicodeEncodeError: 'ascii' codec can't encode characters in position 105-107: ordinal not in range(128)`.

The exact same files with English filenames upload without problems.

What docker image you use ? Is it this one? Or the one provided by linuxserverio?

I am using the linuxserver/papermerge docker. I have tried to run the eugenci/papermerge but I can't make it run. It complains about not finding tesseract and not finding the db. I have even try installing it using the instructions in the Papermerge manual https://papermerge.readthedocs.io/en/latest/setup/docker.html but is fails installing with the error:
ERROR: Cannot locate specified Dockerfile: app.dockerfile
Also another thing I like in the linuxserver/papermerge docker, is that it has enviroment options for bind volumes. This way if something happens to the Papermerge container, at least the documents would be safe outside the container in the host machine.

Ah, and last question. What OS do you use ? Windows/Linux/MacOS ?
I will create an "issue template" to these questions automatically pop up on opening of the new issues.

I am using Debian with the latest docker version from docker repositories.

@N3tFX , thank you! I will investigate the issue.

I had the exact same problem with , and the problem is with the linuxserver.io docker image. Don't use it this docker image. I have spend a lot of time until I realized that the non ascii filenames error is due to this docker image not due to anything related to Papermerge.
Use official documentation provided by Papermerge and install by yourself and you will have it up and running. This is what I did and it fixed it.
This is not a Papermerge bug and @ciur should not waste time on it.

I agree with @stoykovstoyk
Bugs related to external docker images must be handled by respective 3rd parties.
@N3tFX, please open bug at linuxserver.io repo for papermerge docker image.

Hello, @stoykovstoyk ! Can you describe, how you managed to setup the official docker image? I only could install the linuxserver.io edition. When I try to install the original image via portainer.io on my Synology DS218+, I get the error message about not supported version. Is there another way to install it?

I haven't used the docker image. I have installed it with the OS Specific instructions. You just have to follow the instructions and read carefully. I have done it and everything works fine.


Wake Up FIX

This fixes problem with wake up after sleep. You need to stop i2c bus BEFORE you send wake up request via digital pins - Wire.end() added to fix it.

Excellent! Thank you for the PR.

Should now be included in v1.0.1


[NTR] Add plugin version to plugin informations

1. Why is this change necessary?
To check the plugin version inside of kernel.plugin_infos
2. What does this change do, exactly?
Add version to the query
3. Describe each step to reproduce the issue or behaviour.
///
4. Please link to the relevant issues (if any).
///
5. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] I have created a changelog file with all necessary information about my changes
[ ] I have written or adjusted the documentation according to my changes
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/NEXT-11714
Please use this issue to track the state of your pull request.

thanks for your contribution @jinnoflife  :+1: :tada: :blue_heart:


Lower overhead ADO extension wrapping

Removed static initialization of ADO extension so it will NOT wrap the factory if the Glimpse handler is not enabled in the Web.config file. This ensures there is zero overhead on production systems.
Also added support for the GlimpseDbProviderFactory to NOT wrap the connections and commands if the runtime policy is currently set to OFF, for the least amount of overhead for non logged requests if enabled on production systems.

To add to what @CGijbels said, I wondering if we need all the checks in GlimpseDbProviderFactory. In theory GlimpseDbProviderFactory should only be in play if Glimpse is enabled for the given request. That said I would have to test it a little more to make sure.

Not sure how to quote comments here? Anyway, CGijbels said:
"This would break current users and would force every user to add the following code to into their application startup code Glimpse.Settings.Initialize.Ado(); currently this is only required for NET3.5 version of the Glimpse.Ado plugin"
Quite possibly as I am not sure how this works, but the big difference with not having this there is that if you do not have Glimpse enabled at all in your Web.config file, nothing gets initialized and no wrapping of the factory providers happens at all. Which is what you want on a production system so you can turn it on only if you need to track down specific problems. Normally it would be left completely off and have zero overhead.
Now what happens at least on my system is that the AdoInspector() class is called by the normal Glimpse startup code (I believe from within BeginRequest in the HttpHandler) and does all the correct initialization there. But the code that calls AdoInspector() is designed to do nothing when Glimpse is not enabled in the Web.config file. So at least for my case, the static init code is not required at all and I wonder why it was necessary in the first place? Does the normal startup code not run on other platforms? It is only the ADO and EF extensions that somehow required the hack to always init at startup so maybe this is no longer necessary?
For me it is critical that systems like this can be compiled in and be ready to use when we need them, but have zero overhead in production systems. And that is currently not the case with the ADO extension.

"This code is a quick fix that is actually broken in certain circumstances, that is way the GlimpseConfiguration has a private instance field runtimePolicyStrategy which is initialized with a proper strategy that deals with those other situations (see InstantiateRuntimePolicyStrategy() in the Factory class). if you want to check the current runtime policy value, then it would be better to make that runtimePolicyStrategy instance field static and provide it like the GetConfiguredMessageBroker() hack method decorated with the ObsoleteAttribute. Either way, in v2 we have fixed this access issue, so it is possible to get the current runtime policy from a GlimpseRuntime.Instance"
I actually looked at doing it in the GlimpseRuntime class also, and I am glad to know in v2 there is a way for someone to be able to find the single instance of GlimpseRuntime and be able to work out what the current strategy is.

"I see why you would do that, although I'm wondering if checking the current runtime policy isn't adding the same overhead as those pass through calls when being wrapped by Glimpse types and Glimpse is not active? Have you metrics on that?"
I have not measured it directly, but have debugged into the code to see what is happening. IF glimpse is not enabled in the web.config file, the wrapping of the DB classes still happens, so there is an overhead for every single call to DB connections and commands, since they are always wrapped. None of the logging happens though, since the timer stategy and message broker are both null.
However in the case where Glimpse is enabled in the web.config file but not enabled for the request, the wrapped classes will not run any of the timing code but WILL run all of the logging code not related to timing and pass it to the message broker, since the message broker is NOT null in this case. This includes overhead in the the DB reader, DB connection and DB command classes. Look for every piece of code that has an if (MessageBroker != null) in it and every bit of that code executes for EVERY request. Regardless of whether the Glimpse runtime strategy is off or not.
The code change I made takes a quick look at the HttpRequestStore to find the currently configured runtime strategy (which is set up in BeginRequest, so long before it should be needed) and then does not bother wrapping the classes if the strategy is off. This has the benefit of not running any of the message broker stuff when it is not needed, but also completely eliminates any overhead imposed by the class wrappers, since everything is wrapped (every property call etc). So yes, there is a small overhead at the point when you need to wrap the DB classes to determine if it should be wrapped, but it should be significantly less than the total overhead the wrapping imposes.
Also it should be noted that the overhead would be a lot less if the MessageBroker was null when the runtime strategy is OFF, which it currently is not. It would seem the ADO classes were written under the assumption that it would be null in that case, so the overhead would be lower.
But even so I would argue the total overhead of wrapping every single access to the DB classes even if they do basically nothing is a whole lot less if you never wrap them in the first place.

"To add to what @CGijbels said, I wondering if we need all the checks in GlimpseDbProviderFactory. In theory GlimpseDbProviderFactory should only be in play if Glimpse is enabled for the given request. That said I would have to test it a little more to make sure."
I don't think that is possible due to the way that the wrapping is done for the ADO extension. All the code in DbProviderFactoriesExecutionTask only happens once, when the application is first starting up. It finds all the registered DB providers and then wraps them, so we can insert our hooks as necessary. Ideally we would only wrap the DB providers on a per request basis, but that is not possible since those classes are used globally by all requests.
So the wrapping is set up once when the application first starts up, and then it is up to the factory class itself to impose as low overhead as possible on a per request basis.

@kendallb thanks for the comments! I've updated them to show how to add quotes, it is merely preceding them with a >

For me it is critical that systems like this can be compiled in and be ready to use when we need them, but have zero overhead in production systems. And that is currently not the case with the ADO extension.

You are right about the ADOplugins actually running some code, although minor, even when Glimpse is completely disabled. If you want to be 100% sure then you need to remove the Glimpse.Ado and Glimpse.EFx assemblies from your production bin directory (changing web.config to enable Glimpse results in a application restart as well, so adding the additional assemblies then might be a workaround)

Does the normal startup code not run on other platforms? It is only the ADO and EF extensions that somehow required the hack to always init at startup so maybe this is no longer necessary?

If I remember correctly, having the inspector code run on BeginRequest was sometimes too late, especially when dealing with EF, that's why we had to explicitly configure the interceptors at Application_Start in global.asax with code like Glimpse.Settings.Initialize.Ado(); or Glimpse.Settings.Initialize.EF(); (which is still the case for NET35), that's why it has been replaced with the PreApplicationStartMethodAttribute as from NET40 to make sure we don't have a compilation dependency and only a runtime dependency on Glimpse. The exact reason why there were issues with EF is something @avanderhoorn will be able to tell (I think)

I actually looked at doing it in the GlimpseRuntime class also, and I am glad to know in v2 there is a way for someone to be able to find the single instance of GlimpseRuntime and be able to work out what the current strategy is.

Yep, the thing is that the runtimePolicyStrategy is injected in the constructor by the Factory class, that's why you couldn't see it inside the GlimpseRuntime directly. v2 has a proper access to the current Glimpse Request context

However in the case where Glimpse is enabled in the web.config file but not enabled for the request, the wrapped classes will not run any of the timing code but WILL run all of the logging code not related to timing and pass it to the message broker, since the message broker is NOT null in this case. This includes overhead in the the DB reader, DB connection and DB command classes. Look for every piece of code that has an if (MessageBroker != null) in it and every bit of that code executes for EVERY request. Regardless of whether the Glimpse runtime strategy is off or not.

true, the problem or thing to keep in mind here is that there is only a current runtime policy that you can ask for, but during the same request the returned value may change, but even after said that, I do agree that there is a performance impact, even when it is small, it is still there.

So yes, there is a small overhead at the point when you need to wrap the DB classes to determine if it should be wrapped, but it should be significantly less than the total overhead the wrapping imposes.

It will be less in the cases where actual logging would take place, but checking the current value will execute a delegate, check a dictionary, ... but it should be less impacting, normally

Also it should be noted that the overhead would be a lot less if the MessageBroker was null when the runtime strategy is OFF, which it currently is not. It would seem the ADO classes were written under the assumption that it would be null in that case, so the overhead would be lower.

Nope, the broker is set at initialization time and is independent of Glimpse monitoring a request or not, it is static :wink: so it will only be null when Glimpse is configured Off

But even so I would argue the total overhead of wrapping every single access to the DB classes even if they do basically nothing is a whole lot less if you never wrap them in the first place.

I agree, we just need to find the best way with the least impact on existing userbases

So the wrapping is set up once when the application first starts up, and then it is up to the factory class itself to impose as low overhead as possible on a per request basis.

I think your final comment is what we should try to achieve, which means we need to keep the PreApplicationStartMethodAttribute in the AssemblyInfo.cs files, otherwise we are going to have a breaking change. But checking if we need to wrap is something that can be done while being backward compatible (at least nobody should be checking a Glimpse specific wrapper in its code as it could absent as well if Glimpse is configured Off in the web.config)
So to wrap up, if you could undo some of the removals, and adjust the code inside the GlimpseConfiguration to use the private runtimePolicyStrategy (initialized by this code) in an extra Obsolete marked static method, then that might work and still be backward compatible.
I hope all of the above makes sense? If not then let us know and we'll see where we can help you further or clarify things further

I think your final comment is what we should try to achieve, which means we need to keep the PreApplicationStartMethodAttribute in the AssemblyInfo.cs files, otherwise we are going to have a breaking change. But checking if we need to wrap is something that can be done while being backward compatible (at least nobody should be checking a Glimpse specific wrapper in its code as it could absent as well if Glimpse is configured Off in the web.config)

Right, a small overhead in the wrappers at wrap time is probably decent. The most critical part is making sure there is zero impact (or close to zero) for production. If we check for the MessageBroker = null we can easily detect the case when Glimpse is entirely off in the Web.config file and avoid doing anything in that case. A small overhead for that check in the factory to create commands and connections will be nothing. Then we can leave the static init startup code in place.

true, the problem or thing to keep in mind here is that there is only a current runtime policy that you can ask for, but during the same request the returned value may change, but even after said that, I do agree that there is a performance impact, even when it is small, it is still there.

So the runtime policy may change AFTER the request has started? What would the use cases for that be, and is it expected that a DB connection created at request start time can turn on/off the logging during the handling of the request? If that is the case then checking in the wrapper if you should wrap the connection is probably not going to work, as if it starts in the OFF state but then gets turned on for a single controller or something it would never be wrapped and the logging would be lost.
If we want that to work with minimal overhead when Glimpse enabled but is currently set to a runtime policy of OFF (something I think is critical to ensure impact on requests you are not logging is low), then we would need a really fast way to know if the runtime policy is off so you can call that instead everywhere that the current code is checking for a null message broker?

So to wrap up, if you could undo some of the removals, and adjust the code inside the GlimpseConfiguration to use the private runtimePolicyStrategy (initialized by this code) in an extra Obsolete marked static method, then that might work and still be backward compatible.

I looked at doing that initially but I was concerned about the overhead of calling that callback, since won't it end up running all the runtime policy determination code? It seemed faster to me to check what is stored in the request context, since that is the cached result of having already executed that code, but I can see if the policy can change dynamically that might cause a problem.
I think it would be too much overhead to call this every time you need to log something to see if the policy is turned on, but it could be used before you wrap something the connections and command I suppose. Just not sure what would happen if the policy is OFF when the connection is created and then turns to ON when commands are executed?

Ok, changes are made. Let me know if this is more like what you expected.

So the runtime policy may change AFTER the request has started? What would the use cases for that be, and is it expected that a DB connection created at request start time can turn on/off the logging during the handling of the request? If that is the case then checking in the wrapper if you should wrap the connection is probably not going to work, as if it starts in the OFF state but then gets turned on for a single controller or something it would never be wrapped and the logging would be lost.

Yep, it will change, but it can only become more restrictive, which means once it is Off it remains Off, but it is possible that it is On and becomes Off as a result of executing one or more IRuntimePolicy implementations. So what could happen is that a connection is being wrapped at the beginning of the request and maybe some commands as well, but that at the end for instance, some final commands (although less likely there would be some after Glimpse processed the request) might be unwrapped, but then again, that is not an issue as it first was enabled for the request. In case of a configured Off state in the web.config no wrapping will be done because Glimpse won't allow you to.

If we want that to work with minimal overhead when Glimpse enabled but is currently set to a runtime policy of OFF (something I think is critical to ensure impact on requests you are not logging is low), then we would need a really fast way to know if the runtime policy is off so you can call that instead everywhere that the current code is checking for a null message broker?

I was thinking in the lines of exposing the default runtime policy, aka the one read from the web.config and passed in into the GlimpseConfiguration. So the logic could be

check the default, configured, runtime policy, if it is Off then no wrapping should be done
check the MessageBroker for null , if it is null, then no wrapping should be done either as messages can't be sent anyway
check the current runtime policy for an up-to-date value of the current request, if Off then no wrapping should be done
all other cases => wrap

I looked at doing that initially but I was concerned about the overhead of calling that callback, since won't it end up running all the runtime policy determination code? It seemed faster to me to check what is stored in the request context, since that is the cached result of having already executed that code, but I can see if the policy can change dynamically that might cause a problem.

as you can see at the code I mentioned then you'll notice it will not evaluate the configured IRuntimePolicy instances, it will merely look up the current value inside the dictionary, just like you proposed, but with the additional check if the key exists, either way, by reusing that delegate, we can be sure the same check is only implemented once.
So the above will make sure it will become faster when no wrapping needs to be done, but it will become slightly slower when it does, on the other hand the impact should be negligible as a monitored request has more overhead than such a check, and once you are creating many connections or commands that need to be wrapped, then you have another problem :wink:

@kendallb it is looking good, some minor remarks and we should be good to go
Once we have a final version, we need to have @avanderhoorn or @nikmd23 have a final look, as we need somebody less involved in the PR to get a clear view and merge it in the end...
Oh, and you'll have to sign the CLA and mail it to anthony dot vanderhoorn at the google place so that we can pull in the code

I was thinking in the lines of exposing the default runtime policy, aka the one read from the web.config and passed in into the GlimpseConfiguration. So the logic could be

That makes sense. Is that something we can do now or in v2? Also we should make sure that when this PR is pulled over that the equivalent is done in the v2 tree. Is that something you want me to look at? I have not looked at the v2 code at all yet.

as you can see at the code I mentioned then you'll notice it will not evaluate the configured IRuntimePolicy instances, it will merely look up the current value inside the dictionary, just like you proposed, but with the additional check if the key exists, either way, by reusing that delegate, we can be sure the same check is only implemented once.

Yes, I figured that out when I debugged into the code to see what it did :)

Oh, and you'll have to sign the CLA and mail it to anthony dot vanderhoorn at the google place so that we can pull in the code

I will get that done ASAP.

Changes made, let me know if it is good. I will get the CLA signed and sent off.

Currently on my mobile at the moment, so haven't been been able to catch up on all of the latest, but one thing that concerns me about this, is the overhead of conducting the check in the first place. I'm wondering if there is a better way of doing this which would mean that te factory would effectively be a null version in cases were Glimpse is disabled. Not sure exactly how this could be down but just thinking.
And yes, the init code was implemented they way it was because of how early EF starts initializing and what problems we have with trying to wire up our observers post EF getting started.

@kendallb for me this is looking good
@avanderhoorn the way it is changed now means that:

when the Gimpse HttpModule is not available in config but the Glimpse.Ado assembly is, then the GlimpseConfiguration.GetConfiguredMessageBroker() will return null as no initialization has been done and the static messageBroker field inside the GlimpseConfiguration will remain null : this means performance win in that situation and no side effects at all
when the GlimpseConfiguration.GetConfiguredMessageBroker() returns non null value, then this means the Glimpse HttpModule is registered, but then we have the second fallback scenario, where we check for the default runtime policy as it is configured in the web.config. If it is configured as Off then no wrapping will be done either, the call to GlimpseConfiguration.GetDefaultRuntimePolicy() returns the static field defaultRuntimePolicy from the GlimpseConfiguration, set only once : this means in case Glimpse is configured to be Off, no wrapping will be done and no side effects
in case Glimpse HttpModule is active and the default runtime policy is not null then we need to check the current value, which will be done each time a connection, command, adapter is created. This check will add an extra overhead in those cases where Glimpse is active for the request which is different for the current situation, but if Glimpse is active then this additional check can be neglected when looking at the bigger impact the whole request monitoring has, but if Glimpse is inactive for the request because cookie is not set for instance, then you have a performance gain again.

So I wouldn't worry to much about it, and if a user is creating a lot of connections, commands or adapters, then they have another issue and will loose the most time waiting for the DB to return a response :wink:

@kendallb

That makes sense. Is that something we can do now or in v2? Also we should make sure that when this PR is pulled over that the equivalent is done in the v2 tree. Is that something you want me to look at? I have not looked at the v2 code at all yet.

That shouldn't be an issue, normally we can just merge the change in, as we merge the master branch into the v2 branch at regular intervals

How long does it take for the merges to get pushed into an official release on NuGet?

Sorry been focused on my new baby. Is this all ready to go @CGijbels @kendallb @nikmd23

I think so. It was waiting on someone else to approve and pull in to the main branch I believe.
Regards,
Kendall Bennett
CEO & Co-Founder
www.AMain.com |<PHONE_NUMBER> |<PHONE_NUMBER>
424 Otterson Drive, Chico, California 95928

On Apr 23, 2015, at 4:19 PM, Anthony van der Hoorn<EMAIL_ADDRESS>wrote:
Sorry been focused on my new baby. Is this all ready to go @CGijbels https://github.com/CGijbels @kendallb https://github.com/kendallb @nikmd23 https://github.com/nikmd23
—
Reply to this email directly or view it on GitHub https://github.com/Glimpse/Glimpse/pull/894#issuecomment-95745553.

@kendallb Just wondering if you had a chance to sign the CLA. I was hoping to get this into the next release.

I did and I asked to have it sent off. Did you not get it? I can check how it was sent.
Sent from my iPhone
Kendall Bennett
CEO & Founder
www.AMain.comhttp://www.amain.com/ |<PHONE_NUMBER>tel:530-894-0797 |<PHONE_NUMBER>tel:800-705-2215
424 Otterson Drive, Chico, California 95928x-apple-data-detectors://2/1
On Jun 12, 2015, at 11:33 AM, Anthony van der Hoorn <notifications<EMAIL_ADDRESS>wrote:
@kendallbhttps://github.com/kendallb Just wondering if you had a chance to sign the CLA. I was hoping to get this into the next release.
—
Reply to this email directly or view it on GitHubhttps://github.com/Glimpse/Glimpse/pull/894#issuecomment-111582871.

No, not that I have seen.

I checked and I emailed it to glimpseproject<EMAIL_ADDRESS>If there is another email address I should send it to, which one should I use?
Regards,
Kendall Bennett
CEO & Co-Founder
www.AMain.comhttp://www.AMain.com |<PHONE_NUMBER> |<PHONE_NUMBER>
424 Otterson Drive, Chico, California 95928
On Jun 12, 2015, at 12:46 PM, Anthony van der Hoorn <notifications<EMAIL_ADDRESS>wrote:
No, not that I have seen.
—
Reply to this email directly or view it on GitHubhttps://github.com/Glimpse/Glimpse/pull/894#issuecomment-111597661.

Sorry that it got missed that that address. Have recieved it now and we are good to go.

Cool
Sent from my iPhone
Kendall Bennett
CEO & Founder
www.AMain.comhttp://www.amain.com/ |<PHONE_NUMBER>tel:530-894-0797 |<PHONE_NUMBER>tel:800-705-2215
424 Otterson Drive, Chico, California 95928x-apple-data-detectors://2/1
On Jun 16, 2015, at 9:36 AM, Anthony van der Hoorn <notifications<EMAIL_ADDRESS>wrote:
Sorry that it got missed that that address. Have recieved it now and we are good to go.
—
Reply to this email directly or view it on GitHubhttps://github.com/Glimpse/Glimpse/pull/894#issuecomment-112490932.

Hi Guys,
Just checked to see if there are new NuGet builds for MVC4 and ADO that have this, but they are still all from 2014? Is this something that will get rebuilt at some point?


[turborepo] turbo-ignore seems to conflict with Vercel's "Promote to production"

What version of Turborepo are you using?
1.7.4
What package manager are you using / does the bug impact?
pnpm
What operating system are you using?
Mac
Describe the Bug
"Promote to production" feature in Vercel is being cancelled by turbo-ignore, when promoting deployment
Expected Behavior
"Promote to production" in Vercel should work, because NEXT_PUBLIC_VERCEL_ENV, so turbo cache should be different
To Reproduce

Deploy one of packages in https://github.com/saleor/apps. Set "production" branch to some new branch that is not important
Add env variable "preview" specific to "main" branch and another for "production".
Add npx turbo-ignore to ignore build step
Push something to main
Try to "promote to production"

Build gets cancelled
Reproduction Repo
https://github.com/saleor/apps

We now encourage the use of our new feature to automatically ignore unchanged deployments. While this bug may or may not be resolved since the original report, it should address the same use case in a much better way.


fix: HMR error in vue

this fixes TypeError: originalSlots[slotName] is not a function error during HMR in vue by ensuring the function exists.
I havn't opend a issue because it is quite some work to provide a repo and the change is just an assertment.
But I'm not the only one getting this error https://github.com/ionic-team/ionic-framework/issues/24134

@indus see build errors

Merged, thanks!


Transformations

Hi,
it would be great to add the possibility to apply CSS transformations to the STL.
From my trials, it should not work at the moment.
If there's a way to apply them now (v5.0.1) please let me know!
Christian

Hi,
the <mesh> element that references the STL file, or any parent group element is transformable, for instance using CSS. In the example, open a console and try:
document.querySelector("mesh").style.transform = "translate3d(2px, 1px, -3px)"

Works for me.

perfect it works


1.2.0 RC1 - who is wining a replay is not displayed, no button

Describe the bug
I cant make the client display who won a replay. There is no button anymore for that.
Screenshots
https://i.imgur.com/qMmxGBm.png
OS
Linux, Ubuntu 20.04 LTS, openjdk-14-jre, Gnome 3

@Sheikah45 u fixed that as well right?

he fixed it


Add support for max_line_length and max_line_count

As requested here: https://github.com/guillaumekln/faster-whisper/issues/156
Would be nice if we could get this implemented in whisper-ctranslate2
Relevant Whisper code:
https://github.com/openai/whisper/commit/43940fc9780cb91c4f94899755b4648e19d7b977

I have implemented the same that OpenAI. It's not perfect but it's definitely useful for our use cases. Thanks


Instructions sentence/grammar issue

Challenge Use HTML5 to Require a Field has an issue.
User Agent is: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:50.0) Gecko/20100101 Firefox/50.0.
Please describe how to reproduce this issue, and include links to screenshots if possible.
The following paragraph from the instructions is ungrammatical:
"For example, if you wanted to make a text input field required, you can just add the word required within your input element, you would use: "
I suggest changing to the following:
"For example, if you wanted to make a text input field required, you can just add the word required within your input element, like this: "

Confirmed. First-timers only:
Change this line:
https://github.com/FreeCodeCamp/FreeCodeCamp/blob/1a7db665b9f76e70065c1507d584681ecad20b81/seed/challenges/01-front-end-development-certification/html5-and-css.json#L2568
per @discotechne's recommendation above.

I'll take care of this, if I may?

woop woop :100:

is this issue fixed ?

@Kartikkh yes, when a pull request is opened referencing an issue it's shown in the thread, as you can see #12123 is opened as a fix.
Please feel free to browse through the lots of help wanted issues that we have open for contribution on the issues tab.
Thanks and happy fixing!


[bug]:

Is there an existing issue for this?

[X] I have searched the existing issues

OS
Windows
GPU
amd
VRAM
8GB
What version did you experience this issue on?
2.3.2
What happened?
every time I open app to the website it says connected but after a while it will say disconnected for some reason and I have the terminal open
Screenshots
No response
Additional context
No response
Contact Details
No response

Can you give more details? What errors are displayed in the terminal when this happens?


something odd with WPA

I compared the diff of two plays' home_wp_post and WPA in the database.
Is WPA suppose to be the diff of two plays' home_wp_post?
Most numbers check out, but some numbers dont make sense.
Why timeOUT has a different home_wp_post?
Here is what i do:
tic()
test<-pbp %>%
         filter(game_id == "2009_18_GB_ARI",!is.na(home_wp_post)) %>%
         select(game_id,play_id, qtr, desc, total, spread_line, home_wp_post, wpa) %>%
         collect()
toc()

tic()
test <- test %>%
     mutate(wp_diff1 = abs(wpa))
toc()

tic()
test[1,'wp_diff2'] = 0

rownum <- nrow(test)

for (i in 2:rownum){
test[i,'wp_diff2']=abs(test[i,'home_wp_post']-test[i-1,'home_wp_post'])
}
toc()

temp<-test%>%filter(wp_diff2!=wp_diff1)

Here is some more efficient code to reproduce this
pbp %>%
  filter(game_id == "2009_18_GB_ARI", !is.na(home_wp_post)) %>%
  select(game_id, play_id, play_type, desc, home_team, posteam, wp, home_wp, wpa, home_wp_post) %>%
  mutate(
    wp_diff1 = abs(wpa),
    wp_diff2 = abs(home_wp_post - lag(home_wp_post))
  ) %>%
  filter(wp_diff2 != wp_diff1)

output
# A tibble: 4 x 12
  game_id   play_id play_type desc                                home_team posteam    wp home_wp      wpa home_wp_post wp_diff1 wp_diff2
  <chr>       <dbl> <chr>     <chr>                               <chr>     <chr>   <dbl>   <dbl>    <dbl>        <dbl>    <dbl>    <dbl>
1 2009_18_~    1416 no_play   (7:42) J.Kuhn right tackle to ARI ~ ARI       GB      0.153   0.847  0.00151        0.847  0.00151  0
2 2009_18_~    1437 run       (7:02) A.Rodgers up the middle for~ ARI       GB      0.155   0.845 -0.00730        0.852  0.00730  0.00580
3 2009_18_~    4108 no_play   Timeout #1 by ARI at 01:46.         ARI       GB      0.639   0.361  0              0.361  0        0.278
4 2009_18_~    4125 pass      (1:46) (Shotgun) K.Warner pass sho~ ARI       ARI     0.639   0.639  0.0216         0.661  0.0216   0.300

home_wp_post of the play 1416 is modified in this line
https://github.com/mrcaseb/nflfastR/blob/9ae4bb1951a5b4302bc0e3e83261f5bb4406af32/R/helper_add_ep_wp.R#L1011
where home_wp_post is set to the previous value if the current play and the previous play are "no_play"s
The 4108 play appears to have switched home_wp and away_wp.
Any insights @guga31bb ?

This is the equivalent part in nflscrapR and I guess we must have modified it at some point, though I can't remember why. I personally have never used home_wp_post or WPA so I'm surprised we bothered to modify nflscrapR here- there must have been some bug addressed at some point?

finally found the commit but it's not really informative lol
https://github.com/mrcaseb/fastscraper/commit/12a03f956b313bcf6b247159474100aa93ae7403#diff-0a766e08dadf2046e3cf5c64e0d680e7315073ec7f764627a0d55f68e13136c0

That commit was mostly me just copy and pasting nflscrapR's part. But it's weird because it doesn't look identical to nflscrapR in that section


Fix to status logic and tests (for the 2.6.z release branch)

Signed-off-by: randybrunopiverger<EMAIL_ADDRESS>regarding: https://github.com/stolostron/backlog/issues/22692

/lgtm


Implementation: Reddit-Specific HTML tags and other features

This Issue proposes to detect common types of online speech and turn these into features in our engine.
For example, in Reddit (the r/CMV datasets), the ">" character is often used to indicate that someone is responding to another user. The format looks something like this:
> original statement
no, here is my rebuttal!

Due to HTML translation, the ">" character appears as &gt ; in our data.
Other common online-specific text include:

Use of all caps
Adding a link (to an external source)
referencing a user (in Reddit, it has the format u/username, so it can be detected by regex
... (probably many others!)

One key implementation note is that we'll have to preprocess the text differently for these features --- we want to KEEP the special characters and the capitalization!

We might also want to consider versions of preprocessing that eliminate the statements that are inside the quotes, since they are not part of the speaker's "argument" per se, and it's being incorrectly attributed to that person.
Currently, the preprocessing is being handled by code in the utils folder: https://github.com/Watts-Lab/team-process-map/blob/main/feature_engine/utils/preprocess.py. This preprocessing strips away things like special characters.
However, you'll notice that there are different versions of preprocessing that we've already tried to experiment with. One version makes text lowercase but retains punctuation: preprocess_text_lowercase_but_retain_punctuation. This is already used in our code when we detect the number of questions in a native way (by counting the number of question marks). There might be a version where we actually even want to retain capitalization (since that's a huge indicator of emotion / oppositional intensity!).
Thus, this could be a starting point for designing a way to detect Reddit-specific features.

Tips for getting started:

Write down the kinds of special characters and writing styles that are common in the Reddit data. What should we be paying attention to, other than the ">" character and hyperlinks? What about bullet points, numbering, attempts to express text in bold (using * asterisks * on either side, for example), use of ALL CAPS....
Write down ways that we can detect these different characters / styles. Many of them might just involve using a regular expression to detect the relevant patterns or special character. But we'll have to test those regular expressions rigorous to make sure they capture what we hope that they capture! One of my favorite testers is: https://regex101.com/
Figure out how to integrate these different features into our framework. What files need to be modified? Which types of preprocessing do we need to add or change?

[ ] Copy the Template. Go to the Feature Wiki and Copy/Paste the Feature Template into a new page.

[ ] Fill out the Template. Fill out the basic information for the feature in the template. Use the template to document your plan for implementation and major design decisions; if anything changes along the way, update the documentation as you go.

[ ] Create a new Feature file. Create a new file in the folder feature_engine/features. The name of the file should be NAME_features.py, where NAME is the name of your feature.

[ ] Code your feature. Write the code for the feature.

[ ] Evaluate/Unit Test. Come up with a method of evaluating your feature. How do you know that the feature is 'correct?' For simple features, this may be trivial; for more complex ones, you may need to break down each sub-function and unit test them separately, or validate on external data. Add your unit tests to feature_engine/test_featurize.py.

Updating with notes from 2/16/24 meeting:

The goal of this feature is to incorporate attributes that we (as human raters) notice when we read reddit content: we see that someone is using a quote to respond to someone else, so we ignore the quoted content and focus on the response. We see that someone is linking to external materials, so we take that under consideration. We see all caps, and we realize that someone is yelling. Currently, the featurizer doesn't incorporate these insights into the way that features are calculated in our system.
This goal means that it's not so much about displaying these features to us as raters, but about accounting for and quantifying them in our system --- for example, generating features that capture how many quotes are used; whether there are any instances of all caps; how many external links, etc. All these will end up as columns in the feature output.

As a first step, let's do something like the following:

Come up with a list of the common types of special characters and events on Reddit. Draw on your personal experience with rating so many of these chats!
Build a few feature extractors that simply detect their existence or count the number of them (if relevant): for example, number of links, number of quotes, number of bullet points...
Come back and discuss whether we want to add anything else interesting to analyze.

Emily Testing Progress -- as of 03/04/2024
Modifications Made to Branch

Updated responding to someone to return a number and not a boolean
Created a new column that retains capitalization and punctuation (no preprocessing)
Called the function within calculate_chat_level_features()
Added a test dataset (test_reddit_features.csv) and called with FeatureBuilder --
test_reddit_features.csv

Testing Progress
Evaluating tests here: https://github.com/Watts-Lab/team-process-map/blob/902196df81f598aa16d1c3b1021d0e0f20d9d987/feature_engine/testing/ipython_notebooks/test_reddit.ipynb


"Duplicate" duplicating blocks below selected block

Describe the bug
"Duplicate" duplicates all blocks attached below the selected block now
Steps to reproduce the behavior:

Go to https://arcade.makecode.com/beta#editor
Create a series of blocks
Right click on the top most block and select 'duplicate'

Expected behavior
Duplicate should create a copy only of the blocks 'inside' the current block
Actual behavior
"Duplicate" duplicating blocks below selected block

Additional context

OS: Windows(this bug repro on each browser)
Machine build: 17763.1.amd64fre.rs5_release.180914-1434
arcade version: 0.10.1
Microsoft MakeCode version: 5.9.15

This is the new design. Duplicate duplicates the stack, same behavior as drag.

I really do not like the new behavior because delete does not behave the same way... so you duplicate 10 blocks and have to delete them 1by1.

I agree with Peli. Lets keep this bug open.

Fixed


Pokemon vulnerability Tridents

Pokemon can take damage from thrown tridents and upon killing the Pokemon yield vanilla Minecraft experience.

Testing old tickets; this seems out of date as I can no longer impale pokemon with a trident! Closing!


charmc Chokes on @explicit@ constructors

Original author: Nils Deppe (@nilsdeppe)
Original issue: https://charm.cs.illinois.edu/redmine/issues/1685

If I mark a constructor explicit using the explicit keyword as follows:

entry explicit Klass(int);

I get the error:

STDIN:8:error: constructors cannot return a value
  entry explicit Klass(int);

STDIN:8:error: non-void return type in a non-sync/non-local entry method
To return non-void, you need to declare the method as [sync], which means it has blocking semantics, or [local].
  entry explicit Klass(int);

Fatal Error by charmc in directory /home/nils/SpECTRE/spectre/build_clang/src/Parallel
   Command /home/nils/SpECTRE/charm/multicore-linux64-gcc/bin/charmxi -orig-file Algorithm.ci returned error code 1
charmc exiting...

Original date: 2017-09-28 17:11:04

I'm not sure what it would mean to mark a chare class constructor explicit at all, let alone declaring it in the .ci file. The only way a chare constructor can get called is through code that's made a CProxy_Foo::ckNew or array_proxy[k].insert call, leading the RTS code to deliver a message that calls the constructor.
Do you have functions that are taking chare types as arguments, for which you're trying to prevent accidental conversion from some other type that could be used to construct the chare?

Original author: Nils Deppe (@nilsdeppe)
Original date: 2017-09-28 17:37:21

I'm trying to maintain consistency between my C++ code and the CI file, that is all. I would not expect marking the constructors explicit to cause problems (aside from parsing), and we've found that marking constructors explicit unless they should be converting constructors helps catch bugs at compilation time with zero runtime and compile time cost.

Original date: 2017-10-06 15:05:44

So, it wasn't stated earlier, but it looks like having explicit in the class declarations in the C++ code does work fine (just tested on tests/charm++/simplearrayhello), it just doesn't match what's allowed in the .ci file.
I'm inclined toward closing this. We're hoping to phase out .ci files, and hence obviate deficiencies in their parsing, rather than working more and more on the parser. Is that OK by you?

Original author: Nils Deppe (@nilsdeppe)
Original date: 2017-10-06 15:31:33

Ah good. Yes, with moving away from ci files I don't think this is worth anyone's time to fix.


Fix i18n

There were several places in the solidus_digital sources where i18n wasn't working correctly. This should tidy them up!

@pedantic-git thanks man!


etcd: try put again when the ch closed

put(key, value, opt.keepalive=true) to etcd
kill etcd server
wait for 30s
start etcd server

problem:
5. the key will not exist in the etcd server
expect:
5. the (key, value) will put again in etcd server

@ldez
When I was testing the keepalive option of the Put command, I found that once I restarted the etcd server, the keepalive behavior would be invalid. The most terrible thing is that I don't know when the keepalive will be invalid, so once I use the keepalive I have to start another coroutine to determine whether the Put information is still valid. Because of the lease.KeepAlive itself will return a channel, when the channel is closed, the keepalive fails. At this time, we can put it again to make the keepalive take effect.  The following is the test flow

call the put command (set keepalive=true)
stop etcd server
wait 30 seconds
start etcd server

problem:
The set value does not exist on etcd
expect:
The set value still exists in etcd


automation test

Describe the bug
automation test
Expected Behavior
automation test
Current Behavior
automation test
Reproduction Steps
automation test
Regression Issue

[ ] Select this option if this issue appears to be a regression.

Possible Solution
No response
Additional Information/Context
No response
neuronx-cc version used
automation test
Framework(s) and their versions used (JAX, PyTorch, etc..)
No response

closing with comment


Use Travis + the Meetup API to populate upcomming events

From the comment https://github.com/osmlab/osm-community-index/pull/63#issuecomment-379814213 it sounds like having the extra metadata will show the actual meetup events.
Looking at the Meetup API https://www.meetup.com/meetup_api/docs/find/upcoming_events/ it seems like that meeting info could be periodically scraped. EX: https://api.meetup.com/open-cleveland/events?&sign=true&photo-host=public&page=5&status=upcoming
You might be able to use the Travis CI cron jobs to do this periodically https://docs.travis-ci.com/user/cron-jobs/

stale


ps_metrics issue

An annoying warning within Prestashop 8.1.7 that has been around for more than two years:

Warning on line 2292 in file /home7/bocxas/trendyshop/classes/module/Module.php
[2] file_exists(): open_basedir restriction in effect. File(/views/templates/hook/HookDashboardZoneTwo.tpl) is not within the allowed path(s): (/home7/bocxas/:/opt/cpanel/eaxphp81/root/usr:/usr/local/lib/php:/tmp:/etc/pki/tls/certs/ca-bundle.crt:/var/cpanel/php/sessions:/usr/local/bin/wp)

According to the Prestashop Github (https://github.com/PrestaShop/PrestaShop/issues/30531) this is an issue that is caused by the ps_metrix module.
The suspect is the ps_metrix.php file. It contains twice the code
return $this->display(__FILE__, '/views/templates/hook/HookDashboardZoneTwo.tpl');
I suspect this is one '/' too much and that it should be:
return $this->display(__FILE__, 'views/templates/hook/HookDashboardZoneTwo.tpl');

NB: you see this error immediately after you log in. Debug mode should be enabled and the server should have open_basedir set.

Hello @musicpanda !
Thx for this report. We have publish a new release of Metrics (4.0.6) on Addons Store. Can you try to install this version, and say me if your problem persist or not ?

Hello @fox-john !
No, that does not solve the problem.

@musicpanda ok thank you.
We will investigate the issue further, and attempt to apply a fix later.

Hil, @fox-john
As @oclavero menioned here on Mar 23, 2023:
https://github.com/PrestaShop/PrestaShop/issues/26783#issuecomment-1480920541
Just have to remove the starting slash...

Hello @carlos-blazquez-global
Sorry, the fix was applied, but the release was not effective due to a pipeline issue.
A new version has just been deployed. Could you check if the problem persists?
Thanks, and sorry for the delay.


Creating a PR when working on issue does not link

Extension version: v0.29.0
VSCode Version: 1.59.0
OS: Linux x64 5.11.0-25-generic snap

Steps to Reproduce:

create an Issue, and starting work on it
create a PR from working issue

duplicate of https://github.com/microsoft/vscode-pull-request-github/issues/2676


fixed formatting errors for Manifest tutorial and SSH deployments topic

fixed formatting errors for Manifest tutorial and SSH deployments topic
Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the maintainers.
What Type of PR is This?

[ ] Issue
[ ] Feature
[ x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Can slua support Nintendo Switch?

Can slua support Nintendo Switch?

I don't have enviroment of switch , so I can't compile so of slua for switch, if you can compile it by yourself, slua would support switch.

OK, I will try if needed.


Asynchronous processor and exporter for query insight data

Is your feature request related to a problem? Please describe.
we haven't provide a efficient way to export the “top queries with latency” data collected in #11295 , a generic, asynchronous processor and exporter should be created to handle those data for query insight.
(Parent RFC: #11186 )
Describe the solution you'd like
As part of #11186 , we need to implement an asynchronous processor and exporter to handle the data for query insight features. At the first iteration, the processor should be able to handle query latency data asynchronously and enqueue to the aggregator implemented in #11295 , and also export the aggregated data to an OpenSearch index. This framework can potentially be used by other query insight features in the future to avoid adding blocking logic in core search path.
Describe alternatives you've considered
In the future, we can potentially leverage the OPTL collector when it becomes available. With that we can send traces/spans to OPTL collectors, where the collector takes responsibility for necessary calculations, aggregations and export. This strategy could further reduce the impact on the OpenSearch process.
Additional context
Please refer to RFC: #11186

The processor is done as part of the plugin implementation: https://github.com/opensearch-project/OpenSearch/pull/11903
We need to follow up on the exporter:

what are the exporters we want to to expose to the users
configuration endpoints etc.

I want to further elaborate on the exporter component in the query insights framework. As mentioned in the architecture diagram (see https://github.com/opensearch-project/OpenSearch/issues/11429), we want to have generic and asynchronous exporters to export the queries insights data. In the first phase, we should focus on the use case to export top n queries data (since that’s the only insights data we have in memory now - https://github.com/opensearch-project/OpenSearch/pull/11904), while keeping in mind the exporter should be generic enough to handle different use cases to export to other sinks.
Exporter types and configurations
Configuration endpoints shuold be provided for exporters for any types of top n queries (by latency, by resource usages etc), For development and debugging purposes, a debug exporter that exports to stdout will be provided.
search.insights.top_queries.latency.exporter.type: debug

Additionally, the initial exporter release will include a local index exporter with minimal configurations required, such as the rolling index pattern to export to. By default, we can store the top n queries data in a daily rolling index named topQueries-YYYY.MM.dd.  The user can define their own prefix and date pattern to configure daily, weekly, or monthly rolling indexes:
search.insights.top_queries.latency.exporter.type: internal_opensearch
search.insights.top_queries.latency.exporter.config.index: "'my_top_queries-'YYYY.MM.dd"

Future implementations may include exporters for other sinks such as log4j, webhook, external_opensearch, etc., each with their specific configuration details.
Proposed Implementation
In the top n queries implementation, search requests data will be accumulated and finally drained to and stored in an in-memory priority queue in a fixed interval. The priority queue will be rotated to the "last window snapshot" once the data reaches the end of the window. The asynchronous exporter logic can be triggered during this window rotation process.
Further consideration:

Access Control: We need to implement access control for the top queries indices to restrict access to authorized personnel only. This ensures data security and compliance with privacy regulations.
Retention Policy: We should set up index lifecycle policies to manage the retention and deletion of old top queries indicies. This helps optimize storage usage and ensures data is retained for the required duration based on business and regulatory requirements.

@ansjcy Thanks for the proposed solution for exporter and the PR that followed. The proposal looks good to me overall. For the following : search.insights.top_queries.latency.exporter.type: internal_opensearch do we want to be more specific and mention internal_opensearch_index or local_opensearch_index or something on these lines?
Furthermore, are we planning on having a different index for top queries by cpu and memory in the future or use the same index? If its the former, we may want to make this clear in the naming here: search.insights.top_queries.latency.exporter.config.index: "'my_top_queries-'YYYY.MM.dd"


QGIS 3.0 Doesn´t print in A3 format

I have gone from version 2.18 to version 3.0. In the Las Palmas version I had no problem with printing.
I usually work in A3 format and as I said in version 2.18 I did not have any problems with printing from the "designer manager", but in version 3.0, from the "Show Layout" I printed the rotated drawing occupying only a part of A3 paper. Paper comes out horizontally and printing makes it vertical. It is not a problem to configure the printer or the preferences because with version 2.18 I do exactly the same and print well.
Thanks

Dear @fciges,
This repository is to manage the QGIS website and related issues. Your report does not concern the website and should be reported in the application issue tracker. Please check the repo before any report as I think there are already reports about printing failures.
Closing...


mdserver_remote: use short timeout to check server for latest TLF

This waits 500ms for a server response before giving up and using the cached MD if there is one.
In most cases folderBranchOps will roll forward to the latest revision without this fix, but in the meantime bad stuff can happen: if it's an unsynced TLF, the user can get "block not found" errors, or rekeys/upgrades can fail because of conflicts.
Issue: KBFS-3665
Issue: KBFS-3676

Two questions:

It seems this (GetForTLF) is only called when user first time access a TLF, and when suer tries to write into it. So the 500ms delay won't affect reads. Is this correct?

In slow network where it times out after 500ms, we'd still have that "block not found" issue right? Is there a way to detect that error and do the get after that?

It seems this (GetForTLF) is only called when user first time access a TLF, and when suer tries to write into it. So the 500ms delay won't affect reads. Is this correct?

Not sure where you got that impression, but no, this is used before the first read of a TLF during an kbfs instance's lifetime too: https://github.com/keybase/kbfs/blob/f7c9b5de11e410df6d1f4963d1c74177840b15d8/libkbfs/kbfs_ops.go#L546
But it's not really right to say that it "slows down" reads, because getting the MD on the first TLF access is how KBFS has worked for years.  So it just brings performance back to closer to what it was before I introduced the cache (and broke a bunch of stuff).

In slow network where it times out after 500ms, we'd still have that "block not found" issue right? Is there a way to detect that error and do the get after that?

We will immediately register with the mdserver to be notified about new MDs, and start applying them as quickly as we can.  But yes whatever we return from here controls the view of the folder until that catch-up can happen.  We can try to figure out something crazy to do in folderBranchOps to add another blocking step to wait on a fast-forward if there's a "block not found" error, but it would be pretty nasty to implement and I personally don't think it's worth spending much time on.  I'd rather increase the timeout here to a point you're more comfortable with, at the cost of slowing down offline access, than re-architecting the folderBranchOps behavior.

Thanks for the detailed explaination!

We will immediately register with the mdserver to be notified about new MDs, and start applying them as quickly as we can. But yes whatever we return from here controls the view of the folder until that catch-up can happen.

Does this mean the "block not found" error we've been seeing were all transient and would have been resolved as soon as that notification came in? I guess that's why it was flaky.

Not sure where you got that impression,

Ah I only grepped folder_branch_ops.go for it. Now I remember. Thanks.


chore: Updated Babel Dependencies

Hello @anthony-redFox. Why did you drop the loose transpilation? It was there for bundle size & performance.

@Yomguithereal  you right, I missed "loose" option. fixed

And I don't remember correctly but won't the env preset compile for node's version hence making the build unusable on currently supported browsers?

By default uses babel-preset-es2015, babel-preset-es2016, and babel-preset-es2017 together
https://babeljs.io/docs/plugins/preset-env/
It is support node and browsers and currently we also transpile code to ES5 version.

@Yomguithereal  Env  just encapsulate babel-preset-es2015, babel-preset-es2016, and babel-preset-es2017 depend of version node or browsers. Which browser version are you care we will not support?

ES2015 should be the only thing to transpile because I don't use later features. Built version should support at least IE9 if I remember correctly.

@Yomguithereal  done. Replaced on babel-preset-es2015 package.

Thanks @anthony-redFox. Merging now.


samples/../smp_svr: show flashing using intel-hex

Added console snippets which shows possibility
of flashing the signed image using the intel-hex file
opposite the *.bin file.
fixes #29782
Signed-off-by: Andrzej Puzdrowski<EMAIL_ADDRESS>

We know what tools support what input format; I think it would make a lot more sense to just tell the user by throwing an error when an invalid format was used. Or even better would be to add an option like --file which already auto-selects the correct input file extension based on the requirements of the tool used for flashing.

^^ @mbolivar-nordic


Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS)
Built on platform(s)

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

[x] Tested via nixos/tests/magnetico.nix
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

ping

@GrahamcOfBorg test magnetico

It's not referenced in all-tests.nix ?

It's not referenced in all-tests.nix ?

Found another mistake.

I added the test to all-tests.nix, ported it to the python driver and fixed a race condition in.

@GrahamcOfBorg test magnetico

Thank you


Allow annotated FlyteFile as task input argument

TL;DR
This PR allows annotated FlyteFiles to be used as input arguments of a task, e.g., when calculating a custom hash using Annotated[FlyteFile, HashMethod(...)].
See the discussion on Slack for additional details.
Type

[x] Bug Fix
[ ] Feature
[ ] Plugin

Are all requirements met?

[x] Code completed
[x] Smoke tested
[x] Unit tests added
[ ] Code documentation added
[ ] Any pending items have an associated Issue

Complete description
Using an annotated FlyteFile type as an input to a task was previously impossible due to an exception being raised in FlyteFilePathTransformer.to_python_value.
This MR applies the fix previously used in FlyteFilePathTransformer.to_literal to permit using annotated FlyteFiles as either inputs or outputs of a task (see MR #1544), by unwrapping the origin type of the annotated type.
Tracking Issue
https://github.com/flyteorg/flyte/issues/3424
Follow-up issue
NA

Thanks, LGTM. would you resolve branch conflict?

Sorry, was sick for the past days, just merged upstream master and resolved the conflicts.

Merged master again and fixed the test failures on Python 3.8 in 34600b081.
The remaining failing test on 3.11/Windows seems to be unrelated to my changes and I'm not familiar enough with that part of the code base to suggest a fix - anything I should do about that, @pingsutw?

@AdrianoKF never mind. That's flaky test.


Removed unneccesary mpi4py import

Purpose
Removed the implicit import of mpi4py when importing geo_utils etc. Closes #85.
Now the example provided by @akleb returns:
>>> from pygeo.geo_utils import *
>>> import subprocess
>>> print(subprocess.run("mpirun hostname", shell=True))
bdeb688de7b2
bdeb688de7b2
bdeb688de7b2
bdeb688de7b2
CompletedProcess(args='mpirun hostname', returncode=0)

Backwards imcompatibility
DVGeometryVSP import.
previous: from pygeo import DVGeometryVSP, which no longer works.
new: from pygeo.DVGeometryVSP import DVGeometryVSP
This will affect a few files in ADflow and personal runscripts. I'll submit a PR to ADflow.
Type of change
What types of change is it?
Select the appropriate type(s) that describe this PR

[ ] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (non-backwards-compatible fix or feature)
[ ] Code style update (formatting, renaming)
[x] Refactoring (no functional changes, no API changes)
[ ] Documentation update
[x] Maintenance update
[ ] Other (please describe)

Checklist
Put an x in the boxes that apply.

[x] I have run flake8 and black to make sure the code adheres to PEP-8 and is consistently formatted
[x] I have run unit and regression tests which pass locally with my changes
[ ] I have added new tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation

The more I'm thinking about this, I think there are valid scenarios where we want to load MPI, for printing or whatever when we're running this code in parallel. What we essentially want to do is control whether or not to load MPI at run time, and the decision is not simply checking whether mpi4py is installed because you may want to not load MPI even if it's available.
If we want to do this, then what we can do is introduce an environment variable which will control the MPI behaviour of the code, similar to what is done in pyOptSparse or OpenMDAO currently (via PYOPTSPARSE_REQUIRE_MPI and OPENMDAO_USE_MPI, respectively). If we uniformly adopt this across MACH this might help ensure consistency in detecting/loading MPI. Thoughts?

I dont think removing mpi4py is necessary like Neil said. We can use a dummy mpi4py like openmdao if its not available. I dont like the separate import of DVGeoVSP. I also dont like that we import MPI during that eval functions sense call.
This code is designed to work in a parallel environment. I think we need to treat that as default, and add ad-hoc fixes to have it run in serial, instead of the other way around. Whenever any pygeo parameterization is used in parallel, we will need that allreduce at least for the total derivatives.

I dont think removing mpi4py is necessary like Neil said. We can use a dummy mpi4py like openmdao if its not available. I dont like the separate import of DVGeoVSP. I also dont like that we import MPI during that eval functions sense call.
This code is designed to work in a parallel environment. I think we need to treat that as default, and add ad-hoc fixes to have it run in serial, instead of the other way around. Whenever any pygeo parameterization is used in parallel, we will need that allreduce at least for the total derivatives.

It's not about MPI being unavailable, but that parts of pyGeo doesn't need MPI and you should not import MPI just because it's there -- see #85 for an example where you'd want to import something from geo_utils but because something included in the __init__ imports MPI, suddenly your script is importing MPI which fundamentally changes certain behaviour.
I take back what I said about the environment variable, that doesn't really make sense IMO. I think the user should be able to import geo_utils without having something within pygeo automatically importing MPI, but I'm not sure what's the cleanest way to do that.

I'm going to close this PR -- we decided that this is probably not the best approach. Further discussions are encouraged in #85.


InjectorServer module not found

Hey,
About a week ago, I've started getting this error when i try to debug in chrome -
"Error: Cannot find module '/usr/lib/node_modules/node-inspector/lib/InjectorServer.js'"
The nodejs version is 0.10.33 and the node-inspector was 0.9.2. After reading issue #535 , i've tried to upgrade the node-inspector module to latest 0.10.2, but the error persist. The InjectorServer.js file is there in the mentioned directory, so any ideas are welcome

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Bump

Running into this same issue with node-inspector 0.12.8 on node 4.4.2. I've tried uninstalling and cleaning the cache to no avail. Would love to know if anyone has found a solution for this.

have some error, can not find InjectorServer.js.
Any idea will be welcome.


Duplicate attributes in default schemas

I have a simple ASP.Net Core project with a simple controller. Nothing special. But when I load it up with swagger ui in the json file in the generated attributes I have a lot of duplicated value, for example:
TypeAttributesinteger($int32)Enum:
[ 0, 0, 0, 0, 1, 2, 3, 4, 5, 6, 7, 7, 8, 16, 24, 32, 32, 128, 256, 1024, 2048, 4096, 8192, 16384, 65536, 131072, 196608, 196608, 262144, 264192, 1048576, 12582912 ]
If I generate a C# code from this with NSwagStudio I will get a lot of duplicated values, and the code will not compile.
I wrote a ticket on swaggerUI, and they pointed me this way, saying that this is a library issue.
Is this a bug, or some ASP.Net Core issue?

Please create a minimal app that repro's the issue and post to github where I can pull down and take a look.

Thanks for responding, I've created a minimal web-service, and invited you on the github repo.
Just as an extra info: I have the ErrorResponseModel class that it seems to generate the errors in the swagger.json file, values such as (0 and 256 are duplicated):
"MethodAttributes": {
"enum": [
0,
0,
1,
2,
3,
4,
5,
6,
7,
8,
16,
32,
64,
128,
256,
256, ....

You're ErrorModel includes a property of type Exception which has an extremely low-level C#-specific structure and is therefore not ideal for serializing to JSON. Swashbuckle is trying to describe what this might look like in a serialized-to-json form and as you can see it's extremely complicated.
Do you really want to expose the full internals of your Excpeptions instances to your API consumers? Aside from the fact that it's not a particularly usable structure for API consumers, I would think it could also be a security concern. If you want to maintain the structure internally (possibly for internal logging etc.) you can keep the property but tell the serializer to ignore it as follows:
[JsonIgnore]
public Exception FullException { get; }

This will provide a much API contract and corresponding Swagger/OpenAPI description

I've also noticed that you're using some Newtonsoft specific annotations. I'm not sure if you're aware of this but as of ASP.NET Core 3.0, 'Newtonsoftis no longer the default serializer and as far as I can tell you're not explicitly reverting back toNewtonsoftin yourStatup.cs`. This means your annotations will essentially have zero effect.

Thank you, you are totally right. By removing the Exception type from the serialization the issue is gone.
Also thanks for the headsup on the annotations. We wrote this code last year, using ASP.Net Core 2,  its time to update it.


HBASE-23756. [OpenTracing] Add OpenTracing dependency and helper methods.

(1) Add OpenTracing dependencies, shade them appropriately.
(2) Add a few helper methods in TraceUtil, and added test for the helper methods.

This PR is not going to compile properly because of HBASE-23811. However I do want to kick this off early. Preferably this should be in a feature branch.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 29s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s
The patch appears to include 2 new or modified test files.

_ master Compile Tests _

+0 :ok:
mvndep
0m 47s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
5m 14s
master passed

+1 :green_heart:
compile
3m  0s
master passed

+1 :green_heart:
checkstyle
2m 20s
master passed

+1 :green_heart:
shadedjars
4m 37s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
4m 52s
master passed

+0 :ok:
spotbugs
0m 25s
Used deprecated FindBugs config; considering switching to SpotBugs.

+0 :ok:
findbugs
0m 40s
branch/hbase-shaded no findbugs output file (findbugsXml.xml)

+0 :ok:
findbugs
0m 17s
branch/hbase-shaded/hbase-shaded-client no findbugs output file (findbugsXml.xml)

+0 :ok:
findbugs
0m 14s
branch/hbase-shaded/hbase-shaded-with-hadoop-check-invariants no findbugs output file (findbugsXml.xml)

+0 :ok:
findbugs
0m 16s
branch/hbase-shaded/hbase-shaded-check-invariants no findbugs output file (findbugsXml.xml)

+0 :ok:
findbugs
0m 25s
branch/hbase-shaded/hbase-shaded-testing-util no findbugs output file (findbugsXml.xml)

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 18s
Maven dependency ordering for patch

-1 :x:
mvninstall
0m 27s
root in the patch failed.

-1 :x:
compile
0m 12s
root in the patch failed.

-1 :x:
javac
0m 12s
root in the patch failed.

-1 :x:
checkstyle
0m  9s
The patch fails to run checkstyle in root

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
xml
0m  9s
The patch has no ill-formed XML file.

-1 :x:
shadedjars
0m 26s
patch has 11 errors when building our shaded downstream artifacts.

-1 :x:
hadoopcheck
0m 12s
The patch causes 10 errors with Hadoop v2.8.5.

-1 :x:
hadoopcheck
0m 24s
The patch causes 10 errors with Hadoop v2.9.2.

-1 :x:
hadoopcheck
0m 36s
The patch causes 10 errors with Hadoop v3.1.2.

-1 :x:
javadoc
0m 10s
hbase-shaded in the patch failed.

-1 :x:
javadoc
0m 12s
root in the patch failed.

-1 :x:
javadoc
0m  8s
hbase-common in the patch failed.

-1 :x:
javadoc
0m 10s
hbase-server in the patch failed.

-1 :x:
javadoc
0m  9s
hbase-shaded-client in the patch failed.

-1 :x:
javadoc
0m  9s
hbase-shaded-testing-util in the patch failed.

-1 :x:
findbugs
0m 12s
hbase-shaded in the patch failed.

-1 :x:
findbugs
0m 13s
root in the patch failed.

-1 :x:
findbugs
0m  8s
hbase-common in the patch failed.

-1 :x:
findbugs
0m 10s
hbase-server in the patch failed.

+0 :ok:
findbugs
0m 11s
hbase-shaded/hbase-shaded-check-invariants has no data from findbugs

-1 :x:
findbugs
0m  8s
hbase-shaded-client in the patch failed.

-1 :x:
findbugs
0m  9s
hbase-shaded-testing-util in the patch failed.

+0 :ok:
findbugs
0m 12s
hbase-shaded/hbase-shaded-with-hadoop-check-invariants has no data from findbugs

_ Other Tests _

-1 :x:
unit
0m 28s
root in the patch failed.

+1 :green_heart:
asflicense
1m 20s
The patch does not generate ASF License warnings.

51m  9s

Subsystem
Report/Notes

Docker
Client=19.03.6 Server=19.03.6 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/1202

Optional Tests
dupname asflicense checkstyle xml javac javadoc unit shadedjars hadoopcheck compile spotbugs findbugs hbaseanti

uname
Linux 5a11615a8340 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1202/out/precommit/personality/provided.sh

git revision
master / 3e21dc73de

Default Java
1.8.0_181

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-mvninstall-root.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-compile-root.txt

javac
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-compile-root.txt

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out//home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-1202/out/maven-patch-checkstyle-root.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-shadedjars.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-javac-2.8.5.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-javac-2.9.2.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-javac-3.1.2.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-javadoc-hbase-shaded.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-javadoc-root.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-javadoc-hbase-common.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-javadoc-hbase-server.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-javadoc-hbase-shaded_hbase-shaded-client.txt

javadoc
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-javadoc-hbase-shaded_hbase-shaded-testing-util.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-findbugs-hbase-shaded.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-findbugs-root.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-findbugs-hbase-common.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-findbugs-hbase-server.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-findbugs-hbase-shaded_hbase-shaded-client.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-findbugs-hbase-shaded_hbase-shaded-testing-util.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/artifact/out/patch-unit-root.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/testReport/

Max. process+thread count
96 (vs. ulimit of 10000)

modules
C: hbase-shaded . hbase-common hbase-server hbase-shaded/hbase-shaded-check-invariants hbase-shaded/hbase-shaded-client hbase-shaded/hbase-shaded-testing-util hbase-shaded/hbase-shaded-with-hadoop-check-invariants U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-1202/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

We plan to go with open telemetry for now.


Can't access to $wamp.session

Hi,
I'm having problem to access to $wamp.session after $wamp.open()
I know I'm connected with the WAMP router, I can check it from the router's log. But a
console.log($wamp.session)

keeps returning null.
I also tried to inspect $wamp object, and I can't find any properties called session... Any suggestion?

Try $wamp.connection.session.   You can also listen to the $wamp.open event, which returns the session
    $scope.$on("$wamp.open", function (event, session) {
        console.log("the session", session);
    });

Just found the and trying the second solution. It looks to work :D
Thanks!
On Wed, Mar 4, 2015 at 3:18 PM, David Dan<EMAIL_ADDRESS>wrote:

Try $wamp.connection.session. You can also listen to the $wamp.open
event, which returns the session
$scope.$on("$wamp.open", function (event, session) {
    console.log("the session", session);
});

—
Reply to this email directly or view it on GitHub
https://github.com/voryx/angular-wamp/issues/14#issuecomment-77164964.

--
Francesco Cozzolino
Settore Information Technology
Europe Consulting Coop. Soc.
Viale dell’Università, 11
Roma IT - 00185
Tel.<PHONE_NUMBER>
Fax.<PHONE_NUMBER>
<EMAIL_ADDRESS>www.europeconsulting.it


test(e2e): ensure no console logs are emitted

When proper used, that shouldn't happen

Current dependencies on/for this PR:

main

PR #100   👈

This stack of pull requests is managed by Graphite.


Cite keys synchronization

[x] I have verified in the Zotero addons screen that I have the latest release of BBT (https://github.com/retorquere/zotero-better-bibtex/releases/latest) and Zotero installed
[x] I am posting a single question, bug or feature request
[x] I have included a descriptive subject of the problem
[x] I am available for follow-up questions and testing

Your question/suggestion:
Hi,
I use Zotero and BBT on two different computers. I installed BBT on my two computers and it seems BBT recreates all cite keys on the second computer. And I'm not sure they are the same on the two Zotero installation.
So, is there a way to synchronize cite keys between computers ? Maybe, is it possible to use the Zotero sync system ? Or perhaps, is there an other way ?
Thanks in advance and thank you for your hard work.

The only way that currently works is to pin your citekeys. When Zotero gains a citekey field (which has been planned for a long time), they will sync as any other data. When pinned, they'll be put in the extra field, and that will sync; there are also a number of existing Zotero translators (currently BibLaTeX,  BibTeX, CSL JSON and TEI) which will recognize that format, and when Zotero gains the citekey field, Zotero will migrate it there.


ALVR dont see SteamVR

Simmular issue. SteamVR states its missing some files. But everytime i close steam steamVR loads properly but still not detected. Its an openvr issue which i dont have the nerves to fix. Using arch linux with KDE plasma X11 with nvidia 565 drivers on RTX 4060ti.

Same problem


⚠ Jenkins Plugins Artifactory has degraded performance

In fafcfea, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1233 ms

Resolved: Jenkins Plugins Artifactory performance has improved in b2db6f9 after 36 minutes.


Add EntryBehaviours to TextField

Closes https://github.com/enisn/UraniumUI/issues/439
<material:TextField Title="Masked Input">
    <material:TextField.EntryBehaviors>
        <toolkit:MaskedBehavior Mask="XXXX XXXX XXXX XXXX"/>
    </material:TextField.EntryBehaviors>
</material:TextField>

No property, BindableProperty, or event found for "EntryBehaviors", or mismatching type between value and property.

It's not released yet, I'll release 2.6.0-pre.2 after tests are finished, sooner today

nice, tks...

Hello if i use EmailValidationBehavior i got NullReference on TextColorProperty, the EntryView is not defined
    <ContentPage.Resources>
        <Style x:Key="InvalidTextField" TargetType="material:TextField">
            <Setter Property="TextColor" Value="{StaticResource Error}" />
        </Style>
    </ContentPage.Resources>

                        <material:TextField Style="{StaticResource InvalidTextField}" Title="Email Validation" Icon="{FontImageSource FontFamily=MaterialRegular, Glyph={x:Static m:MaterialRegular.Email}}">
                            <material:TextField.Behaviors>
                                <toolkit:EmailValidationBehavior InvalidStyle="{StaticResource InvalidTextField}" />
                            </material:TextField.Behaviors>
                        </material:TextField>

I noticed after adding this behavior, the entry does not put the values in the order I type them.  In the following example, I types<PHONE_NUMBER> with this mask:
<material:TextField.EntryBehaviors>
    <toolkit:MaskedBehavior Mask="(XXX) XXX-XXXX" />
</material:TextField.EntryBehaviors>

This is what I end up with when typing those numbers in the order above:

Thank you,
Sean

Hello if i use EmailValidationBehavior or other validation behavior i got NullReference on TextColorProperty, the EntryView is not defined
    <ContentPage.Resources>
        <Style x:Key="InvalidTextField" TargetType="material:TextField">
            <Setter Property="TextColor" Value="{StaticResource Error}" />
        </Style>
    </ContentPage.Resources>

    <material:TextField Style="{StaticResource InvalidTextField}" Title="Email Validation" Icon="{FontImageSource FontFamily=MaterialRegular, Glyph={x:Static m:MaterialRegular.Email}}">
        <material:TextField.Behaviors>
            <toolkit:EmailValidationBehavior InvalidStyle="{StaticResource InvalidTextField}" />
        </material:TextField.Behaviors>
    </material:TextField>

thanks

Community Toolkit validation behaviours are designed for MAUI Entry object. They can't work with TextField. You can try using EntryBehaviors of TextField instead `Behaviors``.

** UPDATE ** - this only seems to be an issue with Android
I noticed after adding this behavior, the entry does not put the values in the order I type them. In the following example, I type<PHONE_NUMBER> with this mask:
<material:TextField.EntryBehaviors>
    <toolkit:MaskedBehavior Mask="(XXX) XXX-XXXX" />
</material:TextField.EntryBehaviors>

This is what I end up with when typing those numbers in the order above:

Thank you, Sean

Since those mask implemented in Community Toolkit, I can't know how it works. The behaviour itself comes from community toolkit library. I just added an adapter to run those behaviours in the TextField

Thank you @enisn ...
I have found a workaround for now by leaving the XAML portion in there for iOS:
<material:TextField     x:Name="PhoneNumberText"     Title="{x:Static strings:AppResources.Label_PhoneNumber}"     Grid.Row="0"     BorderColor="{Binding PhoneTextFieldColor}"     Focused="HiddenTextField_Focused"     Keyboard="Numeric"     MaxLength="16"     ReturnType="Next"     Text="{Binding Phone}"     TitleColor="{Binding PhoneTextFieldColor}"     Unfocused="HiddenTextField_Unfocused">     <material:TextField.Behaviors>         <toolkit:EventToCommandBehavior Command="{Binding AccountOrPhoneTextChangedCommand}" EventName="TextChanged" />     </material:TextField.Behaviors>     <material:TextField.EntryBehaviors>         <toolkit:MaskedBehavior Mask="(XXX) XXX-XXXX" />     </material:TextField.EntryBehaviors> </material:TextField>
Then in the CS doing this before InitializeComponent:
if (DeviceInfo.Platform == DevicePlatform.Android) {     PhoneNumberText.EntryBehaviors.Clear();     PhoneNumberText.Behaviors.Add(new MaskedTextFieldBehavior() { Mask = "(XXX) XXX-XXXX" }); }
This will work for now... not pretty, but it works!
Thank you,
Sean

I think this issue may be related to CursorPosition.
I add a event to TextChanged in my entry (Inherit TextField) to force the cursor at the end of the text.
And the I test the case of @seanjaeger73 and it's working.
public class MyTextField : TextField
{
    public AscendTextField()
    {
        Loaded += OnLoaded;
    }
    private void OnLoaded(object? o, EventArgs e)
    {
        TextChanged += SetCursorPosition;
        CheckAndShowValidations();
    }
    private void SetCursorPosition(object? o, TextChangedEventArgs e) => CursorPosition = (o as MyTextField )!.Text.Length;
}


MudMenu overlay issue in sticky element

Bug type
Component
Component name
MudMenu
What happened?
When a MudMenu is defined on a sticky cell (position: sticky) in a table row, opening the menu create an overlay that cover everything but the sticky cell after the menu.
Expected behavior
The overlay div covers everything but the menu,
Reproduction link
https://try.mudblazor.com/snippet/wEcHkyuVnVykRptC
Reproduction steps
Just click on a three-dot button, the overlay will appear (made red to make evident the behaviuor), and see the some cell are not below the overlay
Relevant log output
No response
Version (bug)
6.2.0
Version (working)
No response
What browsers are you seeing the problem on?
Firefox, Chrome
On what operating system are you experiencing the issue?
Windows
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

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

I think I found a solution in a StackOverflow.
So to apply this you first need to find out which parent of your overlay element has position: sticky and then just apply a high enough z-index to this element.
In your case, it's a bit harder, as the respective parent element is the th element, but you have to set the higher z-index to only the one th that is parent of the currently open menu, and not to all of them.

Hi @ar-schraml , I'd like to try your suggestion but as you wrote it's harder to do it programmatically.
Instead with last version of MudBlazor (6.17.0 as I write) I can use the new event IsOpenChanged to know if the menu is open or not and then apply a class to a container (eg. body) and with some simple css disable pointer events on elements under the overlay.
I wrote a new example here
https://try.mudblazor.com/snippet/mYwekRYhxxItTmWJ
the sticky elements are still over the overlay, but now you cannot click them, and only overlay and popover are clickable.
In my project I defined all the event callback and handler manually just to intercept the event and add or remove the class.
It would be nice if MudMenu would add/remove the class automatically (I dont know if it's an hard change).


[release/v1.59] Update AMI filter for rocky linux (#1803)

What this PR does / why we need it:
This is a manual backport of #1803.
What type of PR is this?
/kind chore
Does this PR introduce a user-facing change? Then add your Release Note here:
Update AWS AMI filter for rocky linux 8

Documentation:
NONE

/lgtm


pydobot on win7 jupyter - connection problem.

Hi, luismesas!
I work under Win7 OS, in Jupyter notebook.
I have a problem - how should i configure the appropriate port for my Dobot?
Thanx a lot for your work.

Hi @ivldmitriy not sure if a jupyter notebook manages connections, but I updated the basic example using the first available port in the computer, please let me know if that helps.


FileNotFoundError: [Errno 2] No such file or directory: ''

I have added the trained model "bertext_cnndm_transformer.pt" in models folder and two text files in data - one is source in their is one para and another dest which is empty and then I am running this code.
"python ./src/train.py -task abs -mode test_text -model_path ./models/bertext_c
nndm_transformer.pt -text_src ./data/src -text_tgt ./data/tgt"
I am getting this error
[2020-04-12 09:31:07,554 INFO] Loading checkpoint from
Traceback (most recent call last):
File "./src/train.py", line 140, in
test_text_abs(args)
File "/home/yash_watwani/PreSumm-dev/src/train_abstractive.py", line 317, in test_text_abs
checkpoint = torch.load(args.test_from, map_location=lambda storage, loc: storage)
File "/usr/local/lib/python3.5/dist-packages/torch/serialization.py", line 525, in load
with _open_file_like(f, 'rb') as opened_file:
File "/usr/local/lib/python3.5/dist-packages/torch/serialization.py", line 212, in _open_file_like
return _open_file(name_or_buffer, mode)
File "/usr/local/lib/python3.5/dist-packages/torch/serialization.py", line 193, in init
super(_open_file, self).init(open(name, mode))
FileNotFoundError: [Errno 2] No such file or directory: ''

"use -test_from $PT_FILE$ to use your model checkpoint file."
Please specify the path to bertext_cnndm_transformer.pt as -test_from.


Issue 844 fix

Issue 844 will be fixed with this. fixes #844

closing as some tests are failing...☹☹


NFC: Make SILType.h and SILDeclRef.h not depend on SIL/*.h

SILType and SILDeclRef do not actually need anything from SIL/*.h. Also, a few dependencies can be pushed out of the headers into cpp files to speed up incremental rebuilds.

@swift-ci please test

@jckarter – After this clean up, I'd like propose moving SILType.h from include/swift/SIL to include/swift/AST. This would simplify a bunch of things and allow for better self-consistency checks in the SIL specific types of the AST type system.

In principle, I feel like SILType-specific consistency checks could go in the SIL library too. It would be nice if we could drive a stronger wedge between SIL types and AST types, to help make it harder to confuse lowered types and formal types when working in SILGen, optimization passes, and IRGen, instead of making them more similar.

Okay. Let me think about that. In any case, this pull request is still worthwhile, right?

Sure, this patch looks good.


Refactoring the build process

(see for details https://medium.com/@diogok/on-golang-static-binaries-cross-compiling-and-plugins-1aed33499671)

Pull Request Test Coverage Report for Build 557

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 52.424%

Totals

Change from base Build 556:
0.0%

Covered Lines:
638

Relevant Lines:
1217

💛  - Coveralls


⚠ Processors has degraded performance

In 930a424, Processors ($STATUS_URL) experienced degraded performance:

HTTP code: 200
Response time: 72 ms

Resolved: Processors performance has improved in badfdea.


Automation for documenting Agda code

In recent work I spent more time trying to properly typeset Agda tokens that appear in documentation than on making sure the prose is correct and well-written.
To address this, I suggest we develop a script that reads in the tex produced by agda (from our .lagda files) and extracts all tokens along with the appropriate tex macros for formatting them and places these in a macro file.  With such a utility, we can simply use, e.g., \GovAction instead of \AgdaRecord{GovAction} in the documentation.
It might seem this merely saves a few key strokes but the problem when documenting a large Agda module (especially when you're not the original author of the module) is that it can be tedious and distracting to try to remember or look up whether we want, e.g., \AgdaRecord{GovAction} instead of \AgdaDatatype{GovAction}.

I wrote such a script (in Scala) and it does okay, but the output needs quite a bit of hand-tweaking.  For example, the script cannot choose a good name for the macro when the token involves unicode symbols.
Here's a more complicated example than those mentioned above in the issue description:
If we want _⊢_⇀⦇_,RATIFY⦈_ to appear in the documentation, we could use the following latex macro to typeset it:
\newcommand{\RATIFYtransition}{\AgdaOperator{\AgdaFunction{\AgdaUnderscore{}⊢\AgdaUnderscore{}⇀⦇\AgdaUnderscore{},RATIFY⦈\AgdaUnderscore{}}}\xspace}
The script I wrote can construct almost all of this macro by extracting the Agda formatting from the Ratify.tex file that Agda generates from the Ratify.lagda file.  The only part it can't create is the name \RATIFYtransition that I chose... and since I can't even decide if that's a reasonable name, I certainly can't expect the script to do so 😆)
But if all we have to do is select names for the macros produced by the script, that should relieve us of a non-trivial amount of tedious typesetting.

I think this is a great idea! I have two points to make:

We could have a simple config file, that just contains lines looking like _⊢_⇀⦇_,RATIFY⦈_ RATIFYtransition. Then, the tool can read in this file & can do all the replacements described in it.
The tool should run as part of our build system. In particular, this means that our build system needs to be able to build that tool. Since we currently only support nix anyway it's good enough to have a nix derivation building the tool, but I don't know how easy that is to do for Scala. If the tool was written in Haskell or Agda it would probably be easier to maintain since I don't know who else even knows Scala and we don't have to figure out how to get nix to build it. Also, the Agda community might be much more interested in a tool they can compile without having to install something new.


How can we perform responsible disclosure about security problems with Apollo

Hi Apollo developers, is there any channel (e.g., email, website) for us to report security problems or attacks on Apollo? Could you let us know how to perform such responsible disclosure in Apollo? Thanks.

Hi @analyzerav
if you have some security problems you can send mail to our security team by email or website.
Email
You can report security problems to our security team<EMAIL_ADDRESS>they will make a professional response.
Security Website
http://apollo.auto/platform/security_cn.html

@mickeyouyou Thanks for your information!


Implement ArrayBase::fill

Also changed the tests and depracated ArrayBase::assign_scalar.
Fixes #235

Thanks, looks good! I'll just wait for travis to finish.


doc requirements are py3 only

... let's not install them by default

this should help with #100 - but it probably breaks doc building which should now be expected to require a py3 environment


Encode Reverse PInvoke frame stack slot in GCInfo

The GCInfo has space and encoding for reverse PInvoke frame slot. The JIT needs to set it, so that RyuJITT CodeManager can use it.
(Look for TODO link to this issue on where this needs to be fixed.)

Where is this TODO?

https://github.com/dotnet/corert/blob/cac5d0efe2783ebf81b17143d797ea1540dd9bbb/src/Native/Runtime/windows/CoffNativeCodeManager.cpp#L325
https://github.com/dotnet/corert/blob/cac5d0efe2783ebf81b17143d797ea1540dd9bbb/src/Native/Runtime/unix/UnixNativeCodeManager.cpp#L148

To repro:

Uncomment the two lines after the TODO
Compile and run program that just throws unhandled exception: static int Main() { throw new Exception(); }

You should see the uncommented assert to be hit.

Need to get the JIT package updated in CoreRT


Improve POD paragraph highlighting (WIP)

Verbatim paragraphs start with a leading whitespace line and continue
until a blank line.
This also prevents indented lines of ordinary paragraphs from being
incorrectly highlighted as verbatim paragraphs.
Fixes #14.
This will require a corpus rebuild.  Highlighting is now correct for:

corpus/Regexp-Debugger-0.001016/lib/Regexp/Debugger.pm at lines 3154-5
corpus/Moose-2.1005/lib/Moose/Meta/TypeCoercion/Union.pm at line 68
corpus/Moose-2.1005/lib/Moose.pm at lines 1002-8
corpus/Data-Printer-0.35/lib/Data/Printer.pm at lines 1496-1514

Does this handle both =over and =over 4 ?

Does this handle both =over and =over 4 ?

Yes.  The implicit case is already matched before the optionally specified indent level is even considered.

@petdance,  if you're happy with this could you please merge it.

Done. Thanks.


cluster definition: rename environment --> purpose

We're currently using the term "environment" for both hosting environment (AWS, Azure, Xen,...) and for cluster purpose (production, test, staging,...).  This is confusing and looks kind of bad in the dashboard:

Let's rename environment --> purpose in the cluster definition and dashboard and rename hosting environment --> environment on the dashboard.

DONE