Clicking a menuitem

I have a toolbar in my app with toolbaritems defined.  I use the following to get a particular menu item:
    MetaX = Application.Launch(psi)
    mainWindow = MetaX.GetMainWindow(FlaAutomation)
    mm = mainWindow.FindFirstChild(Function(cf) cf.ByName("MainToolStrip")).AsMenu
    mnuOpenFile = mm.FindFirstChild(Function(cf) cf.ByName("Open File")).AsButton

Which works fine, but when I try to use mnuOpenFile.Click, it tells me no clickable point.  I've also tried defining mnuOpenFile as menuItem, but that has the same problem.
I'm sure I'm missing something basic here, can you tell me what I'm doing wrong?

I'm really missing something.  Now I tried setting the text of a textbox, and I get an error target element cannot receive focus.  I tried looking in the uitests, but couldn't find anything.
Also, how do you send a ctl+ sequence using keyboard?
Is there any test app that uses a wider range of flaui that I could look at?  I'm pretty good at working from examples, and there's clearly some basic thing that I'm not understanding.
Any help would be greatly appreciated.
Dan

Regarding keyboard, look at: https://github.com/Roemer/FlaUI/wiki/Keyboard
Also how do you set the text? With the Text property?
Can you try using mnuOpenFile.Invoke()?

So looking at gitter, I saw the invoke, so I tried that and it worked.  Buy any idea why click (which seems the obvious choice) doesn't work?
Got it on the keyboard.  I need to go through the wiki, maybe it will enlighten me.
And yes, I'm using the text property:
    modals = mainWindow.ModalWindows()
    fileOpenWindow = modals(0)
    tbFilename = fileOpenWindow.FindFirstChild(Function(cf) cf.ByName("File name:")).AsTextBox
    tbFilename.Text = "test"

Are you running on a build system where you don't have a desktop session?

No, just running a plain vanilla Win 10.

Is it a free application you're trying to automate?

It’s my own app, so I have access to the automation id’s as well as the names.
From: Roman<EMAIL_ADDRESS>Sent: Thursday, August 24, 2017 1:08 PM
To: Roemer/FlaUI<EMAIL_ADDRESS>Cc: Dan Hinsley<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [Roemer/FlaUI] Clicking a menuitem (#82)
Is it a free application you're trying to automate?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/Roemer/FlaUI/issues/82#issuecomment-324742816 , or mute the thread https://github.com/notifications/unsubscribe-auth/ADM-tU4XGoTZT3Tg1cLOXUURbPQgo-Yyks5sbdgEgaJpZM4PBmht .  https://github.com/notifications/beacon/ADM-tc-ukwTLIxavboebqYXtioFNUMBuks5sbdgEgaJpZM4PBmht.gif

It's more if it's possible to share the app with me or not :)

I can, or I could create a small test app that shows the problem as well.  The entire app is kind of large.  let me see if I can create a small app that shows the problem.

Would be awesome and much easier for me to find issues then.

Actually, it's the standard file open box, which is actually a combobox.  So setting it to that, the only thing I can see to use if value or editabletext.  Value give me value not supported, editabletext tells me not editable.  So I created an app with my own combobox and it works fine, but then in the test app if I use the openfiledialog, I can find the combobox, but get the pattern value not supported.
I can send you the code for both the app that has the openfiledialog and the app that has the flaui calls.  But I think if you just create an app that calls openfiledialog, then try to set the value from another test app, you'd get the issue.
But whichever is easiest for you.

Thought I'd just send these along.  FlaTest has the openfiledialog,
FlaTest.zip, testharness has the FlaUI calls
Testharness.zip

Found this in the microsoft automation docs:

IValueProvider
Depends
If the combo box has the ability to take arbitrary text values, the Value pattern must be supported. This pattern provides the ability to programmatically set the string contents of the combo box. If the Value pattern is not supported, this indicates that the user must make a selection from the list items within the subtree of the combo box.

Yeah, docs and reality are mostly not the same :)

Use the EditableText property on the ComboBox element.

I also am trying to use a radiobutton (this time in my own code) and the click event raises the noclickable exception.

Never mind about the radiobutton, realized I just need to select it and then click the ok button.  Still seems like the semantics should work for click, but at least now I know what to do.

Regarding your combobox:
You are using: cmb = mw.FindFirstChild(Function(cf) cf.ByName("File name:")).AsComboBox
Which returns the Label (as this comes before the combobox). And a label cannot change the text. So it is absolutely correct.
You need to find the combobox:
cmb = mw.FindFirstChild(Function(cf) cf.ByName("File name:").And(cf.ByControlType(ControlType.ComboBox))).AsComboBox
Then everything works as expected.

I had to change controltype.combobox to definitions.controltype.combobox and then everything works.
You might consider adding something to the wrapper that makes this a little more intuitive, seems like the main thing someone is going to want to do with a combobox is either select one of the pre-filled entries or enter in an entry.
The same is true for a toolbar item and click versus invoke, and click on a radiobutton.  Having the semantics be more intuitive would mean less work for you in the long term.
But thanks for doing this.  I tried White and it was really slow, had bugs, and no support.  So just the great support you provide makes this much, much better.
Dan

UIA is very fragile. UIA2 and UIA3 behaves differently. Then there's also WPF, WinForms, UWP, Win32 and custom UI control libraries which all behave differently. I don't get what doesn't work on the combobox in the example above. The problem was you just took the label (the control before the combobox). There is no way FlaUI can automatically assume that you wanted the combobox and not the label, so you had to fix the searching.
Fragility is also about clicks / invokes. Sometimes one works and the other not. I know that like toggle buttons in WPF do NOT fire any commands bound to the control when using invoke, you need to use click there. The whole UIA is full of bugs and FlaUI tries to fix those which are clear. It will always be a bit trial and error.
But if you do see improvement possibilities, I'm happy to take PRs or feature requests.

Also the togglebutton has a select method. When using controls always first try what's on the control itself. I know, the wiki could have more information. Happy to take contributions there as well, it's open for anyone :)

Understood.  Now that I understand it, it won’t be a problem for me.
If I get some time I’ll create a test app with a lot of controls and a FlaUI that works with them.
Dan
From: Roman<EMAIL_ADDRESS>Sent: Friday, August 25, 2017 8:39 AM
To: Roemer/FlaUI<EMAIL_ADDRESS>Cc: Dan Hinsley<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [Roemer/FlaUI] Clicking a menuitem (#82)
UIA is very fragile. UIA2 and UIA3 behaves differently. Then there's also WPF, WinForms, UWP, Win32 and custom UI control libraries which all behave differently. I don't get what doesn't work on the combobox in the example above. The problem was you just took the label (the control before the combobox). There is no way FlaUI can automatically assume that you wanted the combobox and not the label, so you had to fix the searching.
Fragility is also about clicks / invokes. Sometimes one works and the other not. I know that like toggle buttons in WPF do NOT fire any commands bound to the control when using invoke, you need to use click there. The whole UIA is full of bugs and FlaUI tries to fix those which are clear. It will always be a bit trial and error.
But if you do see improvement possibilities, I'm happy to take PRs or feature requests.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/Roemer/FlaUI/issues/82#issuecomment-324957335 , or mute the thread https://github.com/notifications/unsubscribe-auth/ADM-taPm2UrVJOWSBNIHGHhcItsox1-Aks5sbuqngaJpZM4PBmht .  https://github.com/notifications/beacon/ADM-tbEXVoAf4Gyc6SsYIfLRHSBCyc_vks5sbuqngaJpZM4PBmht.gif

And in case some other user runs into it, toolboxitems don’t have an automation id, you have to use the name.
From: Roman<EMAIL_ADDRESS>Sent: Friday, August 25, 2017 8:46 AM
To: Roemer/FlaUI<EMAIL_ADDRESS>Cc: Dan Hinsley<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [Roemer/FlaUI] Clicking a menuitem (#82)
Also the togglebutton has a select method. When using controls always first try what's on the control itself. I know, the wiki could have more information. Happy to take contributions there as well, it's open for anyone :)
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub https://github.com/Roemer/FlaUI/issues/82#issuecomment-324959285 , or mute the thread https://github.com/notifications/unsubscribe-auth/ADM-tc8L5PVN3KU5vuD2xTZ6-j7xJHPLks5sbuw_gaJpZM4PBmht .  https://github.com/notifications/beacon/ADM-tSGFBpEkjQb2xAXYrFxThOtUXDcAks5sbuw_gaJpZM4PBmht.gif

There is a FlaUI WPF and a WinForms Test App and some UI-Tests that test them, maybe you can extend them?
Regarding how to find items: You should always use an inspect tool like FlaUInspect.


plugins/lsp/jdtls: add Eclipse JDT language server for Java

This adds the Eclipse JDT language server for Java. The existing Java LSP, "Java Language Server" was not suiting my use case. JDT seems to work better for me, so this adds that functionality to the list of LSPs.

I believe it should all be rebased properly now, and includes the lib.getExe function to get the command properly. Let me know if there is anything else needed.

@mergifyio queue


Feat: Improve UX of pytorch-elastic plugin by configuring reasonable defaults

Tracking issue
Closes https://github.com/flyteorg/flyte/issues/5339
Why are the changes needed?
As outlined in the tracking issue, when using the pytorch elastic plugin, users almost always have to configure the following on their own:

A pod template with a volume/volume mount which increases the shared memory as the default shared memory segment size of the container is very often too small when torch multiprocessing is used (e.g. for multithreaded data loaders).
A higher join timeout because it easily happens that some worker pods start quicker than others, causing the rendezvous of the workers to fail due to timeouts.

What changes were proposed in this pull request?
Configure reasonable defaults to improve the UX for users:

Add a flag to task_config=Elastic() and PyTorch() which allows adding such a shared memory volume to the pod template. The flag defaults to true.

Configure reasonable join timeouts of 15 minutes.
15 minutes was chosen as an estimate for the time difference between the startup of a pod which is immediately assigned to a running node which has the image pulled (a few seconds) and a pod which requires a node to be scaled up and the image to be pulled.
If users require a larger timeout, they can of course increase the values but should likely rather use a gang scheduler as described here.

How was this patch tested?

Added unit tests
Ran pytorch and elastic pytorch tasks in a cluster and ensured that the volume/volume mount is added

Sentence for the release notes:
@wild-endeavor

The distributed pytorch and distributed elastic-pytorch tasks in flytekitplugins-kfpytorch by default increase the shared memory limit by mounting an emptyDir volume with medium Memory to to /dev/shm as this is almost always required when working with torch multiprocessing (e.g. multi-processed data loader workers or local worker group in distributed training). To disable this, pass increase_shared_mem=False to task_config=PyTorch/Elastic. Elastic tasks now also set a default join timeout of 15 minutes to prevent timeouts when some worker pods require a node scale-up. This setting can be modified via task_config=Elastic(rdzv_configs{...}).

Check all the applicable boxes

[ ] I updated the documentation accordingly.
[ ] All new and existing tests passed.
[x] All commits are signed-off.

+1 from me, but will let thomas give the final go.

and thanks for the blurb!

This is awesome - cc @thomasjpfan @samhita-alla can we improve all our examples to drop the volume config etc


WISH: --version to display version of vcf_* tools

First timer here (thxs!). Please consider adding command-line option --version, e.g.
$ vcf_validator --version
0.6

or possible have --help output the version.

This seems reasonable. We haven't done it yet because no big compatibility-breaking changes have been done since the experimental versions.


Change ciphers and key-exchange-algorithms settings for bottlerocket-admin-container

Hello,
is there some way how to change ciphers and key-exchange-algorithms settings for bottlerocket-admin-container in EKS-Anywhere ?
I see that they are configurable , mentioned here
Which leads me to Bottlerocket docs about settings, here
But can I change them from EKS-Anywhere configuration somewhere, so they will be applied to all nodes during cluster build and also newly added nodes later? Or, the only possible way here, is to build custom bottlerocket-admin-container image ?
Thank you very much for your reply

Unfortunately we don't make all the settings that are available through Bottlerocket available through EKS Anywhere. However we can take requests for these features through these GitHub issues and use it to track support in the future.


🐛 Bug ➾ taqueria does not work with ligo packages

🚥 Status (Internal Taqueria Team Use Only)

[x] 🔬 Investigated and Verified
[x] ⚗ Solution Identified and Designed
[ ] 🧫 Dev Implementation of Fix
[ ] 🧪 Fix Tested and Validated
[ ] 🏆 PR Merged

🆘 What happened?
If I try to use a ligo package like fa
then taq compilation fails , not finding the source files.
Let's do this in ligo first (version > 0.54) :

create a esy.json file with {} content
ligo install @ligo/fa
taq create contract nft.jsligo
write whatever code on this file, and add this first line of import :  #import<EMAIL_ADDRESS>"NFT"
ligo compile contract ./contracts/nft.jsligo
it works !

then try with taq (even if it is ligo hardcoded 0.51 ...)

taq c nft.jsligo

=== For nft.jsligo ===
File "contracts/nft.jsligo", line 1, characters 8-47:
File "contracts/nft.jsligo", line 1, characters 8-47:
File<EMAIL_ADDRESS>to include not found.

┌────────────┬──────────────┐
│ Contract   │ Artifact     │
├────────────┼──────────────┤
│ nft.jsligo │ Not compiled │
└────────────┴──────────────┘

it cannot find the file<EMAIL_ADDRESS>...
let's trick it a bit to point directly to the real path ...
change the first line of imports to
#import "../.ligo/source/i/ligo__s__fa__1.0.4__11004e5b/lib/fa2/nft/NFT.jsligo" "NFT"
try again to compile
taq c nft.jsligo
=== For nft.jsligo ===
File "contracts/nft.jsligo", line 3, characters 0-6:
Ill-defined value declaration.
At this point, one of the following is expected:
  * the keyword 'const';
  * the keyword 'let'.

┌────────────┬──────────────┐
│ Contract   │ Artifact     │
├────────────┼──────────────┤
│ nft.jsligo │ Not compiled │
└────────────┴──────────────┘

This time , it is found
Note : Ignore the warning, it is because on newest version ligo we have to replace let by const when necessary ...
🆘 Steps to Reproduce?
see above
🪵 Relevant log output
see above

🐘 How impactful is this bug?
🚒 Showstopper
⏱ Prevalance
No response
💻 Operating System
Windows -> WSL
🕸 System Architecture
No response
🌮 Taqueria Version
0.22
🌿 Node.js Version
No response
☎ Contact Details
No response
Code of Conduct

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

Beware of using maybe this option
https://ligolang.org/docs/advanced/package-management/#--project-root
to point to root folder where the imported library ./ligo folder should be present

@jchenche, can you look into this?

@zamrokk the problem you'd like us to address is that you cannot point to this package by using #import<EMAIL_ADDRESS>"NFT" right?

ligo CLI exe is able to find the files from this declaration line #import<EMAIL_ADDRESS>"NFT" and compile to Michelson
taq, using ligo plugin, is not able to compile the same file using ligo exe via docker image
hint : look at the ligo expected path ? on taq, contracts are on ./contracts folder, when ligo CLI exe compile it expects ligo packages to be at same folder root as the current execution folder, but with taq , the execution is run at project root level. Maybe that's why with taq it does not find the ligo package file

we should let ligo exe find the path , just indicating where is the project root to find the .ligo folder
I do not recomment a hack on taq to do this, not its responsibility. Try to play with ligo compile options to point to project root maybe. Better to talk with ligo team directly to solve this issue/help
ligo new manager =><EMAIL_ADDRESS>

@zamrokk @avysel I'll try a small POC to fix this issue in the LIGO plugin, I'm thinking of 2 solutions

Add a way to pass --project-root to LIGO from taq
I'll if it is possible to detect --project-root within the LIGO plugin

@hu3man less than 1 day probably

@melwyn95 thanks! Feel free to make a PR! And ping us if you need any support. 🎉

@jchenche How do I get started building taqueria locally? I tried the script ./bin/build-all.sh but I get a typescript error. can you help?

@melwyn95, @mweichert had replied to you on Slack. Btw, you may also use npm run build-all instead of ./bin/build-all.sh

A couple things to note @melwyn95:

You will need a specific version of Deno installed: v1.23.4
The npm run build-all script has a dependency on the taq binary. The first time you build Taqueria, you should run npm run build first to build the binary, then npm run build-all to build the docker images and plugins

This issue was on LIGO side and has been fixed in this MR and this fix will be available in the next LIGO release 0.56.0 which will be release on 23rd November
cc: @avysel

👍

Closing due to pending fix


Release 2.0.0

Pull Request (PR) description
Prepare 2.0.0 release

i would give it a go now.... you ok @bastelfreak ?


paramater onError at props

Hello,
Can I get error value at props parameter like onError than at exported options? Because sometimes we need to get have custom error like with popup or modal or alert than just free text.
Thank you,
Regards

Hi Kuzato,
Sorry for too late reply to you. I have considered about your suggestion and workaround in my working. So I think it is necessary to have an onError function to trigger each validation has errors.
Thank you for your suggest. Have a nice day.


support init containers

Supporting init containers would be great for troubleshooting.
I have some troubleshooting to do on mongodb-replicaset, getting locked with init containers. So tried this beautiful tool but :
[test@test ~]$ kubectl debug --namespace test test-mongodb-replicaset-1
container mongodb-replicaset id not ready
[test@test ~]$ kubectl debug --namespace test test-mongodb-replicaset-1 -c bootstrap
cannot find specified container bootstrap

kubectl can see this bootsrap (still running, that is the problem) running :
[test@test ~]$ kubectl logs test-mongodb-replicaset-1 -n test -c bootstrap -f
2019/02/21 11:05:13 Peer list updated
... waiting for new logs that will never come...

Extract from describe :
kubectl -n test describe pod test-mongodb-replicaset-1
Name:               test-mongodb-replicaset-1
Namespace:          test
Priority:           0
PriorityClassName:  <none>
Node:               xxx
Start Time:         Thu, 21 Feb 2019 11:05:09 +0000
Labels:             app=mongodb-replicaset
                    controller-revision-hash=test-mongodb-replicaset-647db4c6c4
                    release=test
                    statefulset.kubernetes.io/pod-name=test-mongodb-replicaset-1
Annotations:        <none>
Status:             Pending
IP:                 <IP_ADDRESS>
Controlled By:      StatefulSet/test-mongodb-replicaset
Init Containers:
  copy-config:
    Container ID:  docker://f6685231928ba6a843dd348f6cdd602f178aa5e132194dc8aaa44b8058d02c21
   ...
    State:          Terminated
  install:
    Container ID:  docker://618fcfe64504376ece61dfc481641921f0bf1226a6b1394503f8622e0fed0cd9
    State:          Terminated
   ...
  bootstrap:
    Container ID:  docker://34e529ecd86058e1c9e45a1a50f51d610ec65181c0bdfab17b46010c47083142
    Image:         mongo:3.6
    Image ID:      docker-pullable://mongo@sha256:89822fa6161c2ed77e73fb717f189e6ce5a95cb752fe2021508daeee366f9b69
    Port:          <none>
    Host Port:     <none>
    Command:
      /work-dir/peer-finder
    Args:
      -on-start=/init/on-start.sh
      -service=test-mongodb-replicaset
    State:          Running
      Started:      Thu, 21 Feb 2019 11:05:13 +0000
    Ready:          False
    Restart Count:  0
    Environment:
      POD_NAMESPACE:  test (v1:metadata.namespace)
      REPLICA_SET:    rs0
    Mounts:
      /data/configdb from configdir (rw)
      /data/db from datadir (rw)
      /init from init (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-f6p6g (ro)
      /work-dir from workdir (rw)
Containers:
  mongodb-replicaset:
    Container ID:
    Image:         mongo:3.6
    Image ID:
...
Conditions:
  Type              Status
  Initialized       False
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
...
Events:          <none>

Thanks! I will take a look this weekend.

Addressed in 0.0.2 release


Incorrect Content Type for Certain Extensions

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.22.1
Regression From
No response
Architecture
x64
Storage Explorer Build Number
20220122.3
Platform
Windows
OS Version
Windows 10
Bug Description
When uploading certain, known, extensions, the content type is changed to application/octet-stream
This is expected for generic content types but for known ones this should not happen
Examples this happens which then causes issues and needs to be manually changed
.svg -> should be image/svg+xml
.json -> should be application/json
Here is a cheat sheet of content types for reference -- many of them are auto-detected today
https://ppolyzos.com/2015/10/27/apply-proper-content-type-to-files-in-azure-storage-containers-based-on-file-extensions/
Steps to Reproduce

Launch Storage Explorer
Connect to Storage Account (make sure storage account is setup as static website host)
Upload an svg and/or json
It should present the SVG / JSON in a website, but instead asks to download

Actual Experience
Asks to download the SVG or JSON instead of presenting it in the website as hosted content
Expected Experience
Present in the site rather than download as a normal image/data content
Additional Context
As a workaround a script must be run manually each time content is uploaded to change the content type to the proper content type to correct this

We use AzCopy to handle the upload. On Windows, AzCopy will lookup your local registry to determine which contentType to use for the uploaded blobs. Once it's configured, your future uploads will have the correct content types set. See https://github.com/microsoft/AzureStorageExplorer/issues/2267 for more details.

Thank you! This works! closing out


Return whatever data is available when there is a failed remote read

The goal is to return all the data that can be retrieved from storage, even if there is an error doing a remote read. Normally, the error would have caused there to be no data sent from an api call. Now, a "RemoteReadError" is propagated back to the api call. In addition, as per the discussions https://github.com/prometheus/prometheus/issues/2573 and https://github.com/prometheus/prometheus/pull/3421, if there is a remote read error, a new field is added (called extraMessage) that indicates that there was an issue doing the remote read. This way the failure doesn't get silenced.
I'm not exactly sure if the "extra message" is being placed in the best spot/has the best name, so any suggestions would be great. Thanks guys!

Thanks for looking into this. This seems like a layering violation, the query engine shouldn't have to care about how the storage is implemented.
What you want to do is in the fanout if one request for a storage fails, make it as though all requests to that storage return nothing. Returning partial data is to be avoided, it's either all or nothing.

I'm not sure I really follow, are you suggesting keeping the behavior as is then? Because that's what currently happens, if any storage fails, then it returns nothing.

Ok, I get it now. I don't see any way though to stop the the query engine from having to know about the storage in some way. For the API to to know about a remote storage error, that information would have to pass through the query engine, would it not? I agree that it does feel like a layering violation, but I don't really see how to avoid it.

You could remember that the error happened in the fanout storage, and the api check for it afterwards.

It would have to be stored in the querier though, wouldn't it? Because a new querier is generated for each query. Otherwise if it was remembered in the fanout storage, a different simultaneous query might see that it was "remembered" and report it, even if it didn't fail for that query.

No, you could provide a new fanout storage. We'll want the ability to turn on/off remote storage on a per query basis at some point.

If a remote storage fails one any single selector, then we should act as though that remote storage returned nothing for all selectors. If local storage fails for any selector, we fail the entire query.

It feels a bit weird to me for a system to fail silently this way. With little local history relevant for a query, that could make results become completely unpredictable in the face of remote errors, without any errors being surfaced at all. Shouldn't this at least be opt-in via a setting? Or at least somewhere have an indicator in the result metadata that the result is partial?

Shouldn't this at least be opt-in via a setting?

This shouldn't be optional. A Prometheus should still be able to work based on local data alone.

Or at least somewhere have an indicator in the result metadata that the result is partial?

That's the idea.

This shouldn't be optional. A Prometheus should still be able to work based on local data alone.

For rules, yes. For interactive queries though, should it just drop data by default when there are remote errors? I would imagine a query option to explicitly allow not failing on partial errors.

Or at least somewhere have an indicator in the result metadata that the result is partial?

That's the idea.

Ok, still not ideal because we can probably wait a long time until existing API consumers get that particular memo. On the other hand they would also have to implement features needed for explicitly enabling partial results, so either case is not great.

For interactive queries though, should it just drop data by default when there are remote errors?

Yes, it's the only sane thing to do semantically. Consider a unless b where b failed.

For interactive queries though, should it just drop data by default when there are remote errors?

Yes, it's the only sane thing to do semantically. Consider a unless b where b failed.

With "drop data by default" I meant acting and succeeding on partial data. Your example sounds like you interpreted it the other way around, or am I mistaken? You don't meant to say that you want to continue evaluating a unless b when b fails, or? Otherwise I might need more elaboration on the reasoning of that particular query. I mean it's always semantically safer to just return an error by default.

With "drop data by default" I meant acting and succeeding on partial data.

My intention is that a query will always succeed as long as local storage succeeds. If a remote storage fails, we need to discard any successful data we got back from it before the failure though.

Ah ok, you were talking about some remote results succeeding, others failing. I was talking about the case where all remote queries fail intermittently (or one fails, and the data for other remote ones is dropped), leaving the caller with weird and unpredictably flip-flopping results for the older time ranges and without any of the current API users knowing that they have to look somewhere deep into result error metadata to detect that a partial error happened. That's why I considered whether it'd be better to fail the entire query by the default on any partial error anywhere, and only enabling partial evaluation when explicitly enabled.

(or one fails, and the data for other remote ones is dropped),

I'd expect each remote storage to be considered independently.

That's why I considered whether it'd be better to fail the entire query by default on any partial error anywhere, and only enabling partial evaluation when explicitly enabled.

That's kinda what we currently do, and it leads to broken graphs when remote storage is broken - which is not what we should be doing reliability wise.

That's kinda what we currently do, and it leads to broken graphs when remote storage is broken - which is not what we should be doing reliability wise.

Yes, I was suggesting to keep the current behavior as the default, but allowing partial failures when explicitly enabled. The question is what's worse: completely but obviously broken graphs or graphs that look like they loaded correctly, but that are actually partially wrong (and might look completely different on the next refresh). Not that I'm sure of it myself, but it seems worthy of some thought it seems?

I think it's pretty clear that we should be changing how this works by default, and I'm not sure we should even consider giving users an option to make it hard fail in this case. If they care they can look at the warnings field in the response.

The question is what's worse: completely but obviously broken graphs or graphs that look like they loaded correctly,

Consider the case where remote storage is hard down. Completely broken alerting and a no dashboards to debug it are worse. In a standard setup older data will be missing, recent data is fine.

I think it's pretty clear that we should be changing how this works by default

I don't think it's that clear, given that both options are suboptimal and we aim to fail hard and fast in almost all other circumstances.

Consider the case where remote storage is hard down. Completely broken alerting and a no dashboards to debug it are worse. In a standard setup older data will be missing, recent data is fine.

Alerting rules would be exempt as they should be changed to only query local data by default anyway. Completely broken dashboards in a failure case are a better argument for allowing partial evals by default.
I would be ok to go this way, but we do have to at least recognize that it's going to be problematic, non-obvious, and can hurt people's trust in Prometheus (data in graphs flapping in and out of existence). If we do allow this partial failure eval, then we need to push really hard on Grafana folks to implement some kind of obvious indicator for the new partial failure metadata field.

I don't think it's that clear, given that both options are suboptimal and we aim to fail hard and fast in almost all other circumstances.

I'm not sure that's true. We work off stale data rather than hard failing for SD for example.

Completely broken dashboards in a failure case are a better argument for allowing partial evals by default.

I disagree. One of our core principles is reliability. I would not class hard failing because a non-critical component failed as being reliable. Prometheus is not meant to have a hard dependency on any external resources. The whole point of the remote APIs is to isolate us from such failures.

I'm not sure that's true. We work off stale data rather than hard failing for SD for example.

I was careful to say "almost all" :)

Completely broken dashboards in a failure case are a better argument for allowing partial evals by default.

I disagree.

I was trying to make a case for your proposal with that sentence :) I agree that in such a case it would suck to have completely broken dashboards and not be able to debug anything. Thus the "I would be ok to go this way, but...".

@brian-brazil The error happens at the querier level, AFAIK there's no reference to the storage from the querier. I don't see a way of remembering an error in the storage if it's happening in the querier. It could certainly be cleaned up a bit but I feel the query engine has to be involved in some way.
And as far as failing all selectors if 1 fails, how should it handle an error in the middle of getting all the selectors? If it fails in the middle then some selectors have already been added appended. Should the API go back through and remove all series that have the same instance as the failed remote storage or something? That feels like way too hacky of an approach, but I don't see another way of getting rid of those series.

populateSeries is already called just before the evaluation occurs, so I'm not sure where you'd want to move expandSeriesSet to. Also, i'm sure it's just me misunderstanding, but

and return empty results for previous queries from that storage

Makes it sound like you want to return empty for a query that already happened, i'm not sure what you mean here.

populateSeries is already called just before the evaluation occurs, so I'm not sure where you'd want to move expandSeriesSet to. Also, i'm sure it's just me misunderstanding, but

and return empty results for previous queries from that storage

Makes it sound like you want to return empty for a query that already happened, i'm not sure what you mean here.

so I'm not sure where you'd want to move expandSeriesSet to

Move it into the evaluation proper, or more exactly move the logic into the places it's used.

Makes it sound like you want to return empty for a query that already happened, i'm not sure what you mean here.

The result only becomes "real" once we call expandSeriesSet, so if we delay that then we can not mention "missing" data as needed when the expansion starts.

The problem I'm having right now is being able to trace a SeriesSet back to the source it came from and knowing it was the same source that errored before. The remote storage(s) and local storage get merged together for each series, and the source is lost.
One idea I had that would be easier to implement would be to return an error for the whole query if a remote storage errors in the middle of the query, and if it was down the entire time then it would exclude data only from that remote storage. A remote storage failing in the middle of a query should only be a rare event. I know it would be more ideal to be able to handle this event, I just wanted to get your opinion, because i'm finding it's going to take a good amount of reworking to be able to handle it.

A remote storage failing in the middle of a query should only be a rare event.

All data from a remote storage is requested (in populateIterators) before the query is evaluated, so this is impossible.

Yes, and we can handle that entirely in the fanout storage.

Should the behavior be the same for the /series endpoint that doesn't use expandSeriesSet?

Yes, that should be an easier one to handle anyway as it's only a single select.

Well, I managed to really screw up rebasing, but the changes I've made are here. I think the code is kind of messy and hard to follow, so any suggestion would really be appreciated. I still wasn't exactly sure where you wanted expandSeriesSet, I moved it to a later point in populateSeries so that failed remote sources would be identified before expanding everything.

Can you rebase this properly? It's a bit difficult to review currently with all the unrelated changes.

Besides the error coming from TestRecoverParserRuntime(), this should reflect all the changes now. I'm not really sure what's causing that error.

I just pushed some of the changes, but for some reason they aren't showing up here on the PR (Any ideas? https://github.com/mknapphrt/prometheus/commits/failed_remote_read). I was still waiting on a few answers, but I pushed the updates to the apiFunc interface/added a new return type struct, and removed special casing checks for apiFunc responses.

@brian-brazil I pushed some changes that remove all the type checks, It adds a lot of code extra code to accomplish it, I don't know if this is what you're looking for.

I don't think I follow, which merge-related state stuff are you talking about? The list of failed queriers/errors that's in fanout? And I don't understand what this new class is supposed to do or what you mean by reusing mergeQuerier?

The list of failed queriers/errors that's in fanout?

Yes

And I don't understand what this new class is supposed to do

Contain that state, rather than mixing it it in with Storage.

what you mean by reusing mergeQuerier?

Instead of creating a whole new class for this, mergeQuerier might suffice.

I need some way of accessing that 'Container', whether it be in the mergerQuerier or somewhere else. The api doesn't have access to the querier that the fanout storage creates. How would it get the state if it were contained in the mergeQuerier (or a new object either)?

The API has access to the Queryable, which you've currently got a "GetRemoteErrors" method on - which does that. Though GetWarnings would be more generic.

Right, GetRemoteErrors is a function on the fanout storage, not the mergeQuerier though. I agree that GetWarnings would be more appropriate.

@brian-brazil I'm still now sure how you want to access the warnings, do you think you could explain your idea more or give some suggestions? I don't see how the mergeQuerier would be able to store it and still be accessible from the api.

mergeQuerier is a Querier, so will have a GetWarnings method. It you pass the mergeQuerier down to NewMergeSeriesSet, you can then keep the state in there.

Can you explain again why it's unreasonable to pass these warnings through the engine and return them as a result of the query? It seems like this would be a much easier solution if Select returned a set, an error, and warnings and the warnings got passed up exactly the same way the errors did. I don't see how this is would be a layering violation.


fix: added package name prefix to all console. methods in src/

What kind of change does this PR introduce?
After upgrading @supabase/supabase-js, I stumbled on an error message (No storage option exists to persist the session, which may result in unexpected behavior when using auth.         If you want to set persistSession to true, please provide a storage option or you may set persistSession to false to disable this warning.).
It took me a while to figure out from which package this comes and why. Found it only because it was reported in the nuxt/supabase repo https://github.com/nuxt-modules/supabase/issues/188.
I therefore suggest to prefix console.error / console.warning with this package's name, so you can easily check where this random error in your console comes from.
What is the current behavior?
Errors are logged into the server console without me having an idea from which package they come from.
What is the new behavior?
Now every error/warning has the package name [@supabase/gotrue-js] prefixed.

Can you point me in the direction of a fix for this (or at least some docs for the persistSession option mentioned). I seem to have this "unexpected behavior" :)

Would love some info on why this warning is happening and how to get rid of it. It is clogging up our supabase logs rendering them useless.

Would love some info on why this warning is happening and how to get rid of it, it is clogging up our supabase logs rendering them useless.

@AdamEisfeld @notjustinshaw The error appears because some config is not set. Ideally, this would not throw an error, but here we are. The solution in nuxt seems to just set this config value to true/false. But I haven't done any deepdive so it could be something else. https://github.com/nuxt-modules/supabase/issues/188 have you tried that?

We are also having this issue.
I guess there is no solution yet, right?

@nfts2me @notjustinshaw @AdamEisfeld this behavior is designed to help devs be aware that they've got a configuration which could cause them issues. There are plenty of documented cases here
Most of the time, you pass the following option to your supabase client - usually just the server-side ones - the error will go away.
const supabase = await createClient(url, key, {
  auth: {
    persistSession: false
  }
}

Let’s fix this. Seems easy enough to make persist-state:false the default?
On Jun 27, 2023 at 7:37 AM -0700, Jason Creviston @.***>, wrote:

I'm not even using auth. Setting an optional param to mute a warning about something we're not using seems not reasonable.
Good point there!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.Message ID: @.***>

Hi there, is there still interest in improving the log messages (which this PR was originally intended to be)? Or can I close this and it's fine due to the core issue being fixed.

Hi there, is there still interest in improving the log messages (which this PR was originally intended to be)? Or can I close this and it's fine due to the core issue being fixed.

IMO this change is still worthwhile, it will make it easier to spot the source of the error before making the changes which are mentioned in the thread to avoid it.


Impossible to validate host (domain name or IP)

Hi guys,
Just came across your library this morning and was quite surprised with the richness of it. Super nice!
Here's one one observation from a newbie: I've been trying to validate a host and have noticed that the combination of isFQDN and isIP does match my expectations in a couple of edge cases.
Check this out:
const validateHost = (input) => {
  if (!isFQDN(input, { require_tld: false }) && !isIP(input)) {
    throw new EnvError(`Invalid host (domain or ip): "${input}"`)
  }
}
validateHost('example.com')     // no exception, as expected
validateHost('localhost')       // no exception, as expected
validateHost('localhost.')      // exception, as expected

validateHost('<IP_ADDRESS>')     // no exception, as expected
validateHost('192.168.0')       // no exception, despite expected (isFQDN returned true!)
validateHost('<IP_ADDRESS>99')  // no exception, despite expected (isFQDN returned true!)

The function I've written is supposed to check environment variables in a microservice, so it's important to accept both domain names and IP addresses. It is also necessary to make sure there are no typos in the IP address (ideally both for ipv4 and ipv6).
How about making isFQDN a bit more strict? Or what about isHost() that would work slightly better than a combination of two validators?

I'd be ok with making isFQDN more strict and would be happy to accept a PR. Ideally the validator would check TLDs against a list of known values, however the addition of gTLDs mean that the list would be long and ever-growing. I'm not interested in bloating the library or keeping the list up to date.
An alternative might be to disallow numeric TLDs? I'm not aware of any numeric gTLDs, and in fact this may not be allowed by ICANN. It'd be safest to control the behavior with a new option: allow_numeric_tld
Something like this @ isFQDN.js:31 would work:
if (!options.allow_numeric_tld && i == parts.length - 1 && /^\d+$/.test(part)) {
   return false; // reject numeric TLDs
}

I guess you could do a check for IP address in isFQDN and return false if it is one. Not as an option but more as a guard clause.
The proposed isHost is pretty much the same as isURL I think, when you set require_valid_protocol = false and require_tld = false.

this also fails. is this expected?
validator.isURL('http://docker-continer-web')

@maikelmclauflin try require_tld:
> validator.isURL('http://docker-continer-web')
false
> validator.isURL('http://docker-continer-web', { require_tld: false })
true


footer jumps when the size of sidebar is lower than the top of the website.

Hi, Excellent theme'm adapting the template to yii2, and had made in the previous version I changed all new classes and works well only the footer jump to reload the website, because the sidebar is smaller than the top of the screen.
Annex pictures:
Footer Jump in reload website:

Footer after reload website is ok:

Please which version of AdminLte are u using ? The footer has been fixed in the latest release
You can download it from
http://almsaeedstudio.com/themes/AdminLTE/AdminLTE2-dist.zip

I install via composer "bower-asset/admin-lte": "dev-master".

If you upgraded to the latest version then you should read the upgrade guide

thanks for your reply,
My Code Main-Dashboard.php
<?php
    use yii\helpers\Html;
    use yii\widgets\Breadcrumbs;
    use backend\widgets\Alert;

    /* @var $this \yii\web\View */

?>

<?php $this->beginPage() ?>
    <!DOCTYPE html>
    <html lang="<?= Yii::$app->language ?>">

        <meta charset="<?= Yii::$app->charset ?>"/>
        <meta content='width=device-width, initial-scale=1, maximum-scale=1, user-scalable=no' name='viewport'>
        <?= Html::csrfMetaTags() ?>
        <title><?= Html::encode($this->title) ?></title>

        <?php $this->head() ?>

    <?php $this->beginBody() ?>
        <?php if (!\Yii::$app->user->isGuest): ?>
            <?php if (Yii::$app->user->can('Administrador')): ?>

                        <?= Html::a('ChecktimeWeb v. 1.0.', \Yii::$app->homeUrl, ['class' => 'logo']) ?>

                            <?= Html::a('Toggle navigation','#', ['class' => 'sidebar-toggle', 'data-toggle'=>'offcanvas','role'=>'button']) ?>

                           <?= $this->render('_menuser') ?>

                                    <?= html::img(\Yii::$app->session->get('user.avatar30'), $options = ['class' => 'img-rounded'], ['aria-expanded' => 'false']) ?>

<?= \Yii::$app->session->get('user.username') ?>

                                    <?= Html::a(' Online','#') ?>

                            <?= $this->render('_sidebar') ?>

                                <?= Breadcrumbs::widget([
                                    'links' => isset($this->params['breadcrumbs']) ? $this->params['breadcrumbs'] : [],
                                ]) ?>

                            <?= $content ?>
                            <?= Alert::widget() ?>

                   <?= $this->render('_footer') ?>

            <?php endif; ?>
        <?php endif; ?>
    <?php $this->endBody() ?>

endPage() ?>

You cannot use a container in the main content because the .content-wrapper creates that by default. Remove the container div and try again.
When in doubt, consult the blank example page.

I removed the , but just keep doing jumping footer, now does it faster I reviewed the example of the blank page and have all parts of the layout correctly, not if be any dependence on jquery or some .js file, jquery'm running v2.1.3, who else could verify and thank you very much, will wait to leave the paid version because it really worth it, and thus also help so that they can produce new themes.

If you check the example of blank page on your website http://almsaeedstudio.com/themes/AdminLTE/pages/examples/blank.html really jumping footer, makes fast but Salta-

I get what you mean now. Unfortunately there isn't a cross browser way to fix that except by adding a min height to the content which can be inconvenient since you will have to add that to every page that doesn't contain much content. Otherwise, you'll have to tolerate the jumping footer for now.

no problem it just wanted you to have it present excellent upgrade to separate the skins, congratulations this being fine, thks.

You can use a sticky footer instead.

Hello, guys!
I don't know if you guys are still facing this issue, but this CSS workaround seems to have worked for me:

add  at the end of index.php code.


od_blank is not temperature-compensated when it's used in growth rate calculating

users can blank when the vial is at the temperature set point


Don't stop investigation if last lines of shutdown are unknown

please avoid contractions in git commit messages
I don't understand why you would want that. Do we still ensure to exit with a non-zero exit code?

please avoid contractions in git commit messages

I don't see any contradictions.

I don't understand why you would want that.

I want the script to consider all incomplete jobs and not stop on a job where we can not print the addtional shutdown output. I also want to see the summary in that case. As far as I understand, printing the log lines near the shutdown is a purely optional feature of the review script to help the user but shouldn't change the overall behavior.

Do we still ensure to exit with a non-zero exit code?

So far the script exits with a zero exit code if there are no jobs to review but also if there are unreviewed jobs. So unless an unexpected error occurs it basically always returns zero. I even tested this yesterday before and after my summary change and it didn't make a difference. Only if the script is interrupted in the middle due to an error it would return a non-zero exit code.

please avoid contractions in git commit messages

I don't see any contradictions.

"contradictions" != "contractions" :)


01-prepare-data-with-power-query-in-power-bi-desktop.md

English:
For the Position column (sixth last column), notice that 94% of rows are empty (null).
Current Translation:
針對 [職位] 資料行 (第六個資料行)，
Suggested Translation:
針對 Position 資料行 (第六個資料行)，
Description:
The name of column should be English. Global check

Hello contributor,
Thank you for your contribution! We are processing your suggestions and we will update you shortly.
Kind regards,
Microsoft Worldwide Learning Team

Run bugfix tool and waiting for result.


fix: fix deep-learning test flakiness

Related Issues/PRs
None
What changes are proposed in this pull request?
fix deep-learning test flakiness
How is this patch tested?

[x] I have written tests (not required for typo or doc fix) and confirmed the proposed feature/bug-fix/change works.

Does this PR change any dependencies?

[x] No. You can skip this section.
[ ] Yes. Make sure the dependencies are resolved correctly, and list changes here.

Does this PR add a new feature? If so, have you added samples on website?

[x] No. You can skip this section.
[ ] Yes. Make sure you have added samples following below steps.

Find the corresponding markdown file for your new feature in website/docs/documentation folder.
Make sure you choose the correct class estimators/transformers and namespace.
Follow the pattern in markdown file and add another section for your new API, including pyspark, scala (and .NET potentially) samples.
Make sure the DocTable points to correct API link.
Navigate to website folder, and run yarn run start to make sure the website renders correctly.
Don't forget to add <!--pytest-codeblocks:cont--> before each python code blocks to enable auto-tests for python samples.
Make sure the WebsiteSamplesTests job pass in the pipeline.

AB#1914960

/azp run

Codecov Report

Merging #1600 (e95a503) into master (05a4202) will decrease coverage by 79.78%.
The diff coverage is n/a.

:exclamation: Current head e95a503 differs from pull request most recent head 455d1df.


PalEdit does not work on most recent update (v<IP_ADDRESS>731)

I tried doing what I usually do, I put in the level.sav file onto paledit and it does not work since the newest update dropped. Also, cloning pals seems to not work.

Same issues here, won't work since recent update and clone doesn't seem to work

Is anyone else getting "Loading GVAS File, please be patient" and then nothing happens, ever?
Follow up, does this application update automatically? Idk when it would, but I have since been unable to load my save file as of today. Was working fine yesterday.

we need update,please!

You can simply replace the "palworld_save_tools" folder inside the PalEdit folder with the updated https://github.com/cheahjs/palworld-save-tools. Seems to work just fine although i only tested it on one pal. So make sure to backup your savegame before doing any changes to it!

You can simply replace the "palworld_save_tools" folder inside the PalEdit folder with the updated https://github.com/cheahjs/palworld-save-tools. Seems to work just fine although i only tested it on one pal. So make sure to backup your savegame before doing any changes to it!

location of the folder: 0.9.1 Release-104-v0-9-1-1720132586.zip\lib\palworld_save_tools

You can simply replace the "palworld_save_tools" folder inside the PalEdit folder with the updated https://github.com/cheahjs/palworld-save-tools. Seems to work just fine although i only tested it on one pal. So make sure to backup your savegame before doing any changes to it!

seems like this method will load and view the save file, however as soon as you make any changes it freezes the entire program and I have to kill it with task manager, at least for me anyway

Since yesterday, I have had the same problem with the current and previous versions.
I wish someone could find the solution to solve the problem.


table: make copy-paste experience better for excel users

Source: Ben in plan analytics
https://pluralsight.slack.com/archives/C70HPSJPP/p1603836664143200
Before using the DS table, users could copy the on-screen table's content by selection and paste nicely into Excel.  Now, they cannot after switching to the DS table.  This is presumably because the DS table uses divs instead of table tags.
Explore the options for making copy-paste better.
Consider whether the original reasons for not using table on the DS table are valid or attainable in other ways.
, the reasons being:

CSS styling freedom
mobile reflow flexibility

Ben reports continuing customer pushback on their experience now missing this copy-paste experience ability.
I'm leaning toward redoing the markup of tables as with  tags.
Team, why shouldn't we do this?
@sweeting , perhaps you could help on the mobile table front and refresh our knowledge of the design constraints.  What are our current design requirements for tables on mobile screens?  Eg, how do we recommend handling many columns on mobile?

It seems the only reason not to use <table /> tags would be if you want to get really clever with responsive tables.
When we last talked about how to do responsive tables, there seemed to be a consensus for simply allowing table contents to overflow on smaller screens to allow vertical and horizontal scrolling of the table contents and add the ability to have a sticky header. Given that, I would think it makes sense to use table markup to build the DS table.

i'm down for just using native table tags. responsive tables seem like a pipe dream and horz scroll can still happen

Responsive tables are a no no no if using the table tag. I'd recommend keeping current table and just renaming it DataGrid.

^ Very interesting option.
Another issue is whether or not we would integrate Drawer with a new <table /> table.

Other issues: sticky header, nested tables.

via sweets: materialui is div-based.  ant.design is table-based.

Mtg with product team and customer success notes:

copy-paste is still common for customers because csv download and dash date didn't line up, coached by csms
filtering happens in ui table, copy from there (csv doesn't apparently match)
html includes anchors for user urls, they like to send those to other team managers

Team triage:

Split Table and Data Grid
Table is simple, table-markup-based
Data Grid does other interesting use cases like drawer and nesting
Play with this and see what's possible

Designs from Ben:
Link to old table with drawer: https://app.pluralsight.com/plan-analytics/pluralsight-engineering-1d36a/subjects/Microsoft Azure/users?dateFilter=30d&userHandle=861959ec-4331-4382-b732-ea10349865d0
Link to new table; no drawers yet, but plan to add: https://app.pluralsight.com/plan-analytics/pluralsight-engineering-1d36a/inventory?dateFilter=30d
Figma of the design for the second link above, that includes a drawer. https://www.figma.com/proto/X3pUg2mcKjBYTgCiHk6SGT/Inventory-17?node-id=2660%3A6750&viewport=910%2C-1955%2C0.05446632206439972&scaling=min-zoom (edited)


Fix heatmap rendering in Chrome and Safari

Apparently SVG inside flexbox renders slightly different across browsers where Firefox would stretch to fit the parent while Chrome and Safari wouldn't. Stretch the SVG to the width of the parent for consistent rendering.
Also did a few minor tweaks on the min-height of the box so it takes up less space on smaller responsive breakpoints.
Fixes: https://github.com/go-gitea/gitea/issues/13634
Fixes: https://github.com/go-gitea/gitea/pull/13637

still getting small heatmaps in chromium and no heatmaps below 1200w with this.

Must be cached. Try clearing browser cache or start with RUN_MODE=dev.

Must be cached. Try clearing browser cache or start with RUN_MODE=dev.

cleared cache multiple times, cleared site data in browser, reloaded gitea in dev mode.
still small and hidden below 1200w.

alright now this works for me fine and also scales well just as presented.

what is the advantage of hardocoding more values, though, e.g. compared to #13637 ?

The hardcoded min-height values are necessary if we want to prevent the page from jumping after load, I see no way around it because CSS can't know beforehand how big the SVG will render.

The static min-height values are necessary if we want to prevent the page from jumping after load, I see no way around it because CSS can't know beforehand how big the SVG will render.

alright..
I still think the display: inline does the same thing and with style.
the only thing missing is the here-added min-heights so that it doesn't jump either.

noticed sth else though.
see what the titlebar does now along with the feed (where also heatmap is placed).

looks like it's shrinking preliminarily where it could still fit content, doesn't it?

I still think the display: inline does the same thing and with style.

Not sure why you persist on inline, it's just not meant for non-text content and thing like min-height would not work on it because that works only on block-level (you need line-height for inline elements at which point you're just enlarging one "text line" with no text on it).

see what the titlebar does now along with the feed (where also heatmap is placed).

I can't reproduce that one and it's certainly not related here.

I still think the display: inline does the same thing and with style.

Not sure why you persist on inline, it's just not meant for non-text content and thing like min-height would not work on it because that works only on block-level (you need line-height for inline elements at which point you're just enlarging one "text line" with no text on it).

see my comment above.
basically boils down to - do what you think is best.

see what the titlebar does now along with the feed (where also heatmap is placed).

I can't reproduce that one and it's certainly not related here.

no, it's a separate issue but I think may also be affecting the feed column, of which heatmap is a part.
as a whole it might look even better once that is fixed.
just noticed it now, would need investigation.

This should be good to go.

🚀


[search] Feature Request: Counter custom query

Hi,
I noticed that its not possible to specify custom query for counter in the dashboard.
Motivation:

Currently Counter widget can be used only for retrieval for rather simple statistics (count, unique, median...)
But sometimes we need to show more advanced aggregates on the dashboard (with respect to filtering and time selection)

Example: Our customers are often using a business metrics called Net Promoter Score, which is based on customer rating.
The formula for calculation of NPS is really simple (and this calculation can be done is Solr):

(nr_of_high_scores/nr_all_scores - nr_of_low_scores/nr_all_scores)*100

Having this on "customer reviews" dashboard would greatly improve its value, as it would be easy to explore, what was "NPS in our German Branch, in november, by customers from retail segment".

Is there any plan to introduce such feature in Hue?
Thanks!

The counter widget is going to support any formula (https://issues.cloudera.org/browse/HUE-3664)
And the pivot graph could even compute the NPS by categories (by customer by segment by ...)
That way we can have the NPS for the overall dashboard and its filter, and can visualize multiple NPS at the same times by categories.
I could see the need of adding a query facet on the counter widget for static report (KPI style) though. Those static report will come just after the analytics dynamic dashboards.
Does it make sense or I missed something? :)

Sounds good :-). Thanks for a quick answer.


Deprecation warnings with Sass 1.77.8

Describe the issue
Ran into deprecation warnings after upgrading sass to 1.77.8 which means some day, this version of Pico might not work :)
31  │ ┌           @media (min-width: map.get($values, "breakpoint")) {
32  │ │             #{$css-var-prefix}font-size: map.get($values, "root-font-size");
33  │ │           }
    │ └─── nested rule
... │
41  │       #{$css-var-prefix}outline-width: 0.125rem;
    │       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ declaration
    ╵
<EMAIL_ADDRESS>41:5               @use
<EMAIL_ADDRESS>2:1                       @use
<EMAIL_ADDRESS>7:1                                @use
<EMAIL_ADDRESS>2:1                                  @use
    frontend/stylesheets/layout.scss 2:1                                           @use
    frontend/javascript/react/components/artwork_browser/artwork_browser.scss 1:1  root stylesheet

Deprecation Warning: Sass's behavior for declarations that appear after nested
rules will be changing to match the behavior specified by CSS in an upcoming
version. To keep the existing behavior, move the declaration above the nested
rule. To opt into the new behavior, wrap the declaration in `& {}`.

More info: https://sass-lang.com/d/mixed-decls

Current Behavior
Running a build with yarn vite build this kind of error came up a lot.
Expected Behavior
No warnings.
Reproduction URL
I'm working on getting a repro that I can share together.
It came up with a bump from Sass: 1.77.4 to 1.77.8 when these warnings started showing up.
Environment
What feels like related tools and versions
yarn 1.22.22
<EMAIL_ADDRESS>with dependencies
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>

I also get these warnings, just installed Pico to my Vite project.
sass: 1.77.8
vite: 5.3.1
@picocss/pico: 2.0.6

Same issue for me. I'm using Pico v2.0.6 with Astrojs and Vite and rolled back Sass from 1.77.8 to 1.77.6 to avoid this message.
I'm loving Pico, so hopefully the issue can be resolved without a major re-write.


⚠ Bofrost.at has degraded performance

In bd89d19, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1436 ms

Resolved: Bofrost.at performance has improved in 62a52ac.


Change the host / ip of my inverter in Home Assistant

Hey,
Iam not sure, if Iam right here...^^ Your profile was linked as integration owner (https://www.home-assistant.io/integrations/kostal_plenticore) and thats your repo regarding Kostal Inverter readings.
I changed my router and after that the integration wasnt working, since the inverter got a new ip adress. I dont want to lose the data of my entities, but I also dont know my old ip adress and I cant change the ip adress for the integration somewhere?!
What can I do? :)

Hey Acanis87,
I had to change the IP of my inverter in the past too. I worked without a problem, just delete the inverter and create it again. as long as the inverter have the same name (default: scb) everythings works as before.
There might be an alternative: The ip is saved in the config/.storage/core.device_registry file, where you can edit it directly. Just make sure, homeassistant is stopped.


Getting "Download is Disallowed" in iframe.

Describe the bug
I have attached a file to a particular page. When I attempt to download the file while using Bookstack in an iframe I get this error in my console and the file does not download:
Download is disallowed. The frame initiating or instantiating the download is sandboxed, but the flag ‘allow-downloads’ is not set. See https://www.chromestatus.com/feature/5706745674465280 for more details.

Steps To Reproduce

Browse to Bookstack in an iframe.
Upload a file to a page.
Attempt to download the file. It will not work and you will get the above error.
Attempt to download the file again while browsing not in an iframe. It works just fine.

Expected behavior
I should be able to download files while browsing Bookstack in an iframe.
Your Configuration (please complete the following information):

Exact BookStack Version (Found in settings): BookStack v21.05.4.
PHP Version:
Hosting Method (Nginx/Apache/Docker): Docker on Ubuntu.

Additional context
I'm not quite sure if this is a bug or some other configuration change I need to make. I have also already set the - ALLOWED_IFRAME_HOSTS="my_domain" environment variable in my docker compose. Testing the downloading in Chrome on Windows.
Any help on this would be greatly appreciated. Thanks!

Hi @joe-eklund,
Getting downloads to work here requires a change in the way the iframe is defined on the site that's embedding BookStack. The sandbox attribute of the iframe needs to be updated with allow-downloads. I don't think this is something that can be solved from the BookStack side of things.

Hmm ok. I am iFraming it inside Organizr with both being Traefik 1.7 as a reverse proxy. I am planning on upgrading to Traefik 2 soon.
I attempted to set the contentSecurityPolicy with sandbox allow-downloads for Bookstack using Traefik labels but that didn't seem to affect it. I will continue to investigate how this is possible, but if anyone has this working I would very much like to know.


Atom disappears from quick launch bar

When i open Atom, and i finish and click close button, atom disappears from quick launch bar.
I use windows 7 Home Premium (SP1) and latest version of Atom.

I don't know why, but now i installed again and everything is fine. Sorry for incomplete issue.


Fix PHP Fatal error when installed with --prefer-lowest

Hi!
I publish this PR to fix a PHP Fatal error I faced when I installed the bundle with php7.4 with --prefer-lowest flag
The error is the following:
PHP Fatal error:  Declaration of Matthias\SymfonyConfigTest\PhpUnit\ProcessedConfigurationEqualsConstraint::evaluate($other, $description = '', $returnResult = false) must be compatible with PHPUnit\Framework\Constraint\Constraint::evaluate($other, string $description = '', bool $returnResult = false): ?bool .../vendor/matthiasnoback/symfony-config-test/PhpUnit/ProcessedConfigurationEqualsConstraint.php on line 23

as you can see, the strong typed return : ?bool is not present in https://github.com/SymfonyTest/SymfonyConfigTest/blob/4.0.1/PhpUnit/ProcessedConfigurationEqualsConstraint.php#L23
as in  https://github.com/sebastianbergmann/phpunit/blob/9.5.0/src/Framework/Constraint/Constraint.php#L42
Thanks for maintaining this repo!

Hi there, any news about this PR ?

Hello, is this repo still maintained ?

We are preparing for a v5 release. We have dropped PHP 7.
This issue is fixed there.
To fix this issue in your own project. Just add "matthiasnoback/symfony-config-test": "^4.2.0", in your composer.json.


Avoid disposing Path texture

Potentially still being used by drawnode. Also stops needlessly disposing Texture.WhitePixel on Texture_Set.

As discussed, I've added back the disposal since it is safe and definitely what we want. I've also added a texture disposal inside Dispose() to complement it.


Add method disableHistory to disable history on the given transaction

Hi marijnh,
I am building a codeblock node based on CodeMirror and ProseMirror.
Similar to the official codemirror example, a code editor in prosemirror. The difference is that I am using the codemirror6 and the code editor have tabs.
When change the tab, I need to change the content of codeblock node dynamicly by dispatching tr.replaceWith. Then the change will be stored in history which is unwanted.
So I make this PR.

This looks like it will just corrupt the history (by making the changes in it no longer align with the current document).

You are right. I think I should try another interaction.


Validate url format after adding BASE_URL

This makes it possible to use BASE_URL=http://host/path_part_ and image url _second_part/file.ext.

Oh, thanks for catching this. We don't actually need to check url on the download stage since it will be checked by downloadClient.Get. Please, remove the redundant check, and I'll merge this.

Nevermind, I'll do it myself. Thanks for your contribution!

Released in darthsim/imgproxy:v2.0.3


[LLC] RequestOptions into Azure.Core

At some point RequestOptions will move from Experimental to Core, and we need to update for that.

[ ] Finalize ResponseClassifier API
[ ] Review RequestOptions at arch board
[ ] Consider renamings to make ResponseStatusOption enum and value a little easier to understand

We won't move to Core for RC1.0, because it's a proper GA.  We will do an arch board review and agree on what's Experimental/RC1.0.

ResponseClassifier APIs have been removed to allow more bake time.


Reconnecting host appears as two in GUI

I am using boot2docker (docker-machine) on a Mac to host some Selenium Grid agents, and as soon as the computer gets restarted or the VM gets restarted it auto connects to Rancher, this causes a confusion in Rancher, as it believes it's two instances.
One of the instances will show all the agents running, and the other will just be empty, without a network agent. If I close the empty one down, it will close the working one down as well.

will investigate.

This is because boot2docker uses a read only file system and anything outside of /var/lib/docker is lost upon restart.
Definitely not a GA bug, maybe we don't fix at all since it might be worth the effort to make the special dispensation for b2d.


Added DRC Digital Reserve Currency Alias to ENS

Hi! What is your PR about?

[ ] Add or edit a skin
[x] Add custom domain for your space
[X] Add alias for migrate your space
~Add images for your space~ (deprecated) Add the image URL on the space settings directly
~Edit your space with GitHub?~ (deprecated) Please migrate your space to ENS https://docs.snapshot.page/spaces/migrate
~Create your space with GitHub~ (deprecated) Create your space with ENS instead https://docs.snapshot.page/spaces/create

I can't find your new space. Please make sure that you have filled in all required fields and added a strategy.
https://snapshot.org/#/drctoken.eth

We are trying to migrate from legacy to the new Snapshot setup that needs an ENS.
Can you please commit this to the alias.json:  "digital-reserve-currency": "drctoken.eth"
Then I should be able to access areas to add new strategies?

Reason for this PR is to: Add alias for migrate your space

I can't find your new space. Please make sure that you have filled in all required fields and added a strategy.
https://snapshot.org/#/drctoken.eth

You should be able to see it now. Are you able to help with the Migration from the old to new?


pubsub: make Polling work with Long element count

Bump gax version to 1.0.1 and gax-grpc to 0.16.1.

LGTM after tests pass

Changes Unknown when pulling fd0984b1716b5d2dc24b0a569d70277773e14175 on pongad:long-semaphore into ** on GoogleCloudPlatform:master**.

Changes Unknown when pulling fd0984b1716b5d2dc24b0a569d70277773e14175 on pongad:long-semaphore into ** on GoogleCloudPlatform:master**.


[CSBindings] A couple of minor adjustments to inferring default bindings from literal protocols

Don't track ExpressibleByNilLiteral as a coverable protocol because it can't produce a binding
Coalesce ExpressibleBy{Integer, Float}Literal early
Avoid double-checking whether protocol requirement is direct

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test source compatibility

@swift-ci please test


Updates to support Nativescript 7

I think that this is all that is needed to support nativescript 7.

@cla-bot check

The cicd failure looks like it just failed to reach npm at one particular point, triggering a rerun should clear it up


Using RKE2 with registry mirror

Should include instructions how to install and configure a registry mirror for docker hub

RKE2 mirroring docs are HERE.  This issue was opened before that page was published, so I'm going to close.  If we need to go deeper with mirroring at some point in the future, we can re-open.


Publishing changes to live

Docs Build status updates of commit 334ef64:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/New-TransportRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

sharepoint/sharepoint-ps/sharepoint-online/Submit-SPOMigrationJob.md
:white_check_mark:Succeeded
View (sharepoint-ps)

skype/skype-ps/skype/Set-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 3d662d8:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

exchange/docs-conceptual/app-only-auth-powershell-v2.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/New-TransportRule.md
:white_check_mark:Succeeded
View (exchange-ps)

exchange/exchange-ps/exchange/Set-DlpComplianceRule.md
:white_check_mark:Succeeded
View (exchange-ps)

sharepoint/sharepoint-ps/sharepoint-online/Submit-SPOMigrationJob.md
:white_check_mark:Succeeded
View (sharepoint-ps)

skype/skype-ps/skype/Set-CsTenantNetworkSite.md
:white_check_mark:Succeeded
View (skype-ps)

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


fix mt4/mt5 installation

This should fix #122, as I was able to get them to work correctly in a local image build in docker. However, the Travis CI tests will fail due to using an outdated copy of the scripts. Let me know if there's anything else.

Thanks, will test in 1h and merge.


Add database block

Summary

Relevant Issue(s)

Checklist

[ ] Summarized PR's changes in CHANGELOG.md

Superseded by https://github.com/PrefectHQ/prefect-snowflake/pull/53


+8 icons, +1 link, +1 update

Description

Added few new icons and updated Athena icon to better reflect the original one.
Icons addition information

Added
ColorBlendr (com.drdisagree.colorblendr)
DevInfoOverlay (ru.andr7e.devinfooverlay)
File Navigator (com.w2sv.filenavigator)
HeliBoard (helium314.keyboard)
Kraken (com.kraken.invest.app)
Kraken Pro (com.kraken.trade)
Rozkład PKP (de.hafas.android.pkp)
Sim Cell Info (ru.andr7e.simcellinfo)
Linked
Wi-Fi Monitor (ru.andr7e.wifimonitor → wifianalyzer.svg)
Updated
Athena (dev.sebaubuntu.athena)
Contributor's checklist

[x] I made the icons following the Lawnicons Guidelines (upd. Jan 2024) and will make changes if someone suggests. I will also make sure that Lawnicons builds correctly.

but if you have a better idea how to achieve that I would be grateful for the hint.

I can't help you with that.

Cool, thanks!


Hybrid Cost function error

Currently HybridSystems formulations call to add PowerIn, PowerOut variables in the objective function.
The method is missing to add them to the cost function for TwoPart costs, Ideal we only add cost related to PowerOut

I will move this issue for the next period since the HybridSystems code should be placed in the new repo. The overhead cost to maintain the HybridGeneration models is too large and it shouldn't be part of 1.0
cc. @daniel-thom


StatsController for time-to-data-arrival and other things

Initial metric is time-to-data-arrival on the catalog page. For now, the controller uses window.location.hash when it's instantiated to determine whether or not the statistic should apply. This is important because there is no navigation+reload when moving between front page, catalog page, and metrics page. The metric is only reported when the user first loads the page looking at a catalog (and non-empty catalog data eventually arrive).

Codecov Report

Merging #246 into master will increase coverage by 0.17%.
The diff coverage is 71.42%.

@@            Coverage Diff            @@
##           master    #246      +/-   ##
=========================================
+ Coverage   61.33%   61.5%   +0.17%
=========================================
  Files          38      39       +1
  Lines        2387    2429      +42
  Branches      159     164       +5
=========================================
+ Hits         1464    1494      +30
- Misses        923     935      +12

Impacted Files
Coverage Δ

lib/component/catalog_table.es6.js
6.14% <0%> (-0.06%)
:arrow_down:

lib/client/api_service.es6.js
34.28% <50%> (+0.95%)
:arrow_up:

lib/client/stats_controller.es6.js
74.35% <74.35%> (ø)

Continue to review full report at Codecov.

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


Decompose constructor to improve readability

[x] tests and linter show no problems (npm t)
[x] tests are added/updated for bug fixes and new features
[x] code is properly formatted (npm run fmt)

Landed in https://github.com/metarhia/metacalc/commit/3f03b71c97c26cd68ce209df893eb165e7cef1c9


File selector for loading a har file

Improve the docs on the Load tab and include a way to open a file selector.

Need to provide the file selector as there is a performance bug when trying to load in very large HAR files.


Make keys DDL use LeveledCompactionStrategy by default [CE2]

This is a backport of https://github.com/evolution-gaming/kafka-flow/pull/636

lgtm


Test viewer

@aruniverse I've been working on a way to link a Viewer, from another repo, with this Rush repo to do what you're trying to solve here. I'll hopefully have a sample a bit later today that I can show.

@aruniverse I've been working on a way to link a Viewer, from another repo, with this Rush repo to do what you're trying to solve here. I'll hopefully have a sample a bit later today that I can show.

ok sounds good, so we wont have a test viewer in the repo, but link multiple repos together where there is atleast one viewer in one of em

Abandoning this PR. Should be able to test pkgs in a viewer using co-spaces


Update Dockerfile to use latest WebRTC Streamer

I could not get the code to work without making an update to use the latest WebRTC Streamer for the Raspberry Pi 3 architecture. I do not know if this is worth merging into the main repository however might be useful for other people to make reference to.

Looks good to me but

I am no longer interning at Resin
There is always a newer build

I cannot merge this PR and it does not look like the Balena team care


Setting distinct for an index by default using $algoliaSettings

Greetings,
I have a model set up to automatically sync to Algolia and for this index I would like to have the field called category to be distinct by default for all queries. In my Eloquent model, part of my $algoliaSettings look like this:
public $algoliaSettings = [
    'attributeForDistinct' => 'category'
];

When I call Model::setSettings() and then take a look at the index display settings in the web app, I see this:

The distinct true/false option is not set. I have looked through the documentation here and on Algolia and cannot find anything that will allow me to programmatically set distinct to true for all queries. Does this feature exist? And do you know of any way I can mark distinct as true without logging in and manually setting it each time I need to update the index settings?
Thanks for the help!

Did you try:
public $algoliaSettings = [
    'attributeForDistinct' => 'category',
    'distinct' => true
];

?

Excellent! Thank you very much. I'm not sure how I managed to try every variation except for this one, but I do appreciate the help.
I suppose when I was looking through the documentation, I was expecting $algoliaSettings to only include indexing parameters and the only examples I could find using the distinct option were at the query level.


Build process fails on aarch64

The build process (cargo +nightly build) fails with this message
   Compiling librocksdb-sys v6.11.4
error: failed to run custom build command for `librocksdb-sys v6.11.4`

Caused by:
  process didn't exit successfully: `/home/ferry/apps/pastebin/target/debug/build/librocksdb-sys-a85dc79a0dccba47/build-script-build` (exit code: 101)
  --- stderr
  rocksdb/include/rocksdb/c.h:65:10: fatal error: 'stdarg.h' file not found
  rocksdb/include/rocksdb/c.h:65:10: fatal error: 'stdarg.h' file not found, err: true
  thread 'main' panicked at 'unable to generate rocksdb bindings: ()', /home/ferry/.cargo/registry/src/github.com-1ecc6299db9ec823/librocksdb-sys-6.11.4/build.rs:44:10
  stack backtrace:
     0: rust_begin_unwind
               at /rustc/b2025326088b54fb3f083bebeba14e0a15bf00d3/library/std/src/panicking.rs:495:5
     1: core::panicking::panic_fmt
               at /rustc/b2025326088b54fb3f083bebeba14e0a15bf00d3/library/core/src/panicking.rs:92:14
     2: core::option::expect_none_failed
               at /rustc/b2025326088b54fb3f083bebeba14e0a15bf00d3/library/core/src/option.rs:1268:5
     3: core::result::Result<T,E>::expect
               at /rustc/b2025326088b54fb3f083bebeba14e0a15bf00d3/library/core/src/result.rs:933:23
     4: build_script_build::bindgen_rocksdb
               at ./build.rs:37:20
     5: build_script_build::main
               at ./build.rs:328:5
     6: core::ops::function::FnOnce::call_once
               at /rustc/b2025326088b54fb3f083bebeba14e0a15bf00d3/library/core/src/ops/function.rs:227:5
  note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

This is on an nvidia jetson nano (quad core ARM57)

Likely you're missing some C lib... Since I don't want to troubleshoot platform (nvidia jetson nano) specific issues I've set up CI/CD image for armv7 & armv8/aarch64:
docker run --network host mkaczanowski/pastebin:armv8 --address localhost --port 8000
docker run --network host mkaczanowski/pastebin:armv7 --address localhost --port 8000

The above will also run on your x86 machine assuming you have qemu-static installed & binfmt_misc

Thanks this works perfectly!


handleErrorBinding (can't run min.js)

Hi all,
I'm by no means an expert and have followed the tutorial without fault till this point, but every time i run "node utils/nftport/mint.js" i get the same error.
I've searched the forums and can't find a solution.
Any help would be greatly appreciated.

The solution is in the error. It cannot find the file _ipfsMetas.json. Check your previous steps to track the problem.


Rename Token to OAuthToken

There were references to OAuthToken in linode_client.py, which for one is undefined so this cannot work, and other classes followed the pattern of camel_case_obj.py contains class CamelCaseObj.

test seems stuck

kicked it

Either Token or PersonalAccessToken seems fine. I saw
https://github.com/linode/python-linode-api/blob/master/linode/linode_client.py#L192
and assumed that OAuthToken would be the desired name. Will update

Bleh, that was probably missed in a prior rename. Thanks


Add missing ```math line in optimization docs

Fixes #171.

Coverage increased (+0.02%) to 89.91% when pulling 83c9219322122cffe8b27510d72498223e6644a7 on nl/math into 95baee7a01fad1ab53b3d3b043c9ac44e2844e10 on master.

Codecov Report

Merging #173 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #173   +/-   ##
=======================================
  Coverage   89.91%   89.91%
=======================================
  Files          13       13
  Lines        1338     1338
=======================================
  Hits         1203     1203
  Misses        135      135

Continue to review full report at Codecov.

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


HTML Theme is not working properly

HTML formatting is not working.

Expected Behavior
Just wanted to add an HTML and CSS element together in a screenshot.
PS: It would be awesome if I could show the result of my HTML and CSS combination somewhere in the screenshot.
Info
OS: Windows 10
Browser: Google chrome v 83.0.4103.116

@amirmeimari please post a link to a Carbon snippet, or at least the code of your example so I can recreate the issue.

@mfix22 sure
https://carbon.now.sh/?bg=rgba(55%2C140%2C206%2C1)&t=night-owl&wt=none&l=htmlmixed&ds=true&dsyoff=38px&dsblur=82px&wc=true&wa=true&pv=56px&ph=74px&ln=false&fl=1&fm=dm&fs=18px&lh=150%25&si=false&es=2x&wm=false&code=%253C!--%2520Adjacent%2520sibling%2520combinator%2520--%253E%250A%250A%253Cstyle%253E%250A%2520%2520li%253Afirst-of-type%2520%252B%2520li%2520%257B%250A%2520%2520%2520%2520color%253A%2520red%253B%250A%2520%2520%257D%250A%253C%252Fstyle%253E%250A%250A%253Cul%253E%250A%2520%2520%253Cli%253EOne%253C%252Fli%253E%2520%253C!--%2520This%2520line%2520is%2520selected%2520in%2520style%2520--%253E%250A%2520%2520%253Cli%253ETwo!%253C%252Fli%253E%2520%253C!--%2520Color%2520of%2520this%2520line%2520will%2520get%2520chnaged%2520---%253E%250A%2520%2520%253Cli%253EThree%253C%252Fli%253E%250A%253C%252Ful%253E


Upgrade to TinyMCE 7 due to XSS Vulnerability in TinyMCE 6.8.1

Hi,
got a composer vulnerability in TinyMCE ..
[https://github.com/advisories/GHSA-5359-pvf2-pw78]
is it possible to either update dependencies to 7 or to
use convert_unsafe_embeds option to automatically convert object and embed elements respective of their type attribute to bypass this security issue?
thanks
Gary

Hi Gary please use the latest version.
"tinymce/tinymce": "^7.0"

Thanks Amid, my composer wasn't noticing the bump to ^2.0 last week with the upgrade to tinymce 7.0


About interface synchronization request method

Hello, all ccapi interface requests are asynchronous requests. Is there any configuration or method to turn the interface requests into synchronous requests? thanks。

https://github.com/crypto-chassis/ccapi#make-sessionsendrequest-blocking


docs: DOC-132: Include analytics collection setting in Enterprise docs

The line about the COLLECT_ANALYTICS environment variable was hidden from the Enterprise docs. This PR exposes.
Affects:

[ ] Community docs
[X] Enterprise docs

Closing because this isn't relevant for LSE


How to shift nested set to Closure Table

Hi i am intended to shift nested set pattern to closure table pattern but there are around 1 lakh records in the table. Please recommend a appropriate way to shift Nested set data to closure table.

@ajay-logiciel Nested Sets and Closure Table are very different approaches. So you need to write a converter, I think.


Model config and training

I am interested in your work. And I want to implement your model training. But I don't find the related files. So can you upload files in detail? Thank you.

@chaowentao: First of all, great to get to know your interest in this project! Unfortunately, we are not at the moment planning to launch training code for EfficientPose. However, all necessary details are available in our paper (https://link.springer.com/article/10.1007/s10489-020-01918-7), which enables reimplementation.

@chaowentao: First of all, great to get to know your interest in this project! Unfortunately, we are not at the moment planning to launch training code for EfficientPose. However, all necessary details are available in our paper (https://link.springer.com/article/10.1007/s10489-020-01918-7), which enables reimplementation.

@daniegr What is the loss of the article? paf and three-stage heatmap loss?

@daniegr What is the loss of the article? paf and three-stage heatmap loss?

@chaowentao: For all three detection passes (pass 1 with Part Affinity Fields and pass 2-3 with confidence maps) Euclidean loss is used, with appropriate sigma values to define the ground truth maps. As mentioned in Appendix B of the paper, a stepwise sigma scheme is utilized.

@chaowentao: For all three detection passes (pass 1 with Part Affinity Fields and pass 2-3 with confidence maps) Euclidean loss is used, with appropriate sigma values to define the ground truth maps. As mentioned in Appendix B of the paper, a stepwise sigma scheme is utilized.

Great work, I also had a few questions regarding reimplementation.
(1) In the paper you mention that you evaluate EfficientPose by using "MSE of the model predictions relative to the target coordinates". However you mention here that Euclidean loss was used, was MSE then used only for the comparison of EfficientPose and OpenPose?
(2) Im guessing that the learningrates employed in the trainingscheme mentioned in Appendix B are specifically designed for an MSE loss function. Is there a formula that would allow for the recalculation of the scheme based on the highest learning rate for which a Euclidean loss function did not diverge?
(3) Were the EfficientNet feature extractors frozen during the training?
Thanks in advance.

@chaowentao: Thank you for your interest in the EfficientPose framework. To clarify and to avoid possible confusion with the previous comment, the description in Appendix B of the paper is correct. The training loss is implemented as the mean squared error (MSE) of the predicted maps Y (i.e., Part Affinity Fields or confidence maps) relative to the ground truth maps Y* (as determined by the ground truth locations and the sigma value) across the output responses N:

Regarding your final question, the feature extractors were also fine-tuned during training.


Font Awesome issues (delete button not shown)

Actually I found out the delete button needs font awesome (which is not needed by Etherpad in general as it seems). Font awesome is saved under etherpad/static/font/fontawesome-etherpad.woff.
However the delete button was not shown.
But from having q quick look on your code you seem to use etherpad-lite to load font awesome, so I reported the issue there: https://github.com/ether/etherpad-lite/issues/2963
So go on reading there if you're interested in this issue. (And please confirm that it must be fixed in etherpad-lite. If you can fix it, you're of course free to do it.)

The icon is part of Etherpad code. This PR added icons to it, for example: https://github.com/ether/etherpad-lite/pull/2690. On its discussion you might find a way to fix your issue too.

Please reopen this issue, because ep_comments seem to have an issue with that files:
Reproduce:
0.
Filter it, so only fonts are shown.
Now hover over a comment.

What you'll see:
In step 2 you'll see the font being loaded:
200 /CustomSubDir/static/font/fontawesome-etherpad.woff

However when hovering over the comment another font is loaded:
404 /static/font/fontawesome-etherpad.woff

And this one can't be found in my setup.
So what happens is the following:

All "usual" Etherpad icons are correctly shown as they use the font, which was loaded the first time.
The small "delete" icon is broken as it tries to use the same font loaded in another (incorrect) way

This makes up two issues:

Why does this plugin tries to load the same font again? (And refuses to use the one, which was already loaded)
It loads the font incorrectly.

This was resolved already, sorry for not closing.


add python3-h5py

https://packages.ubuntu.com/focal/python3-h5py
https://packages.debian.org/buster/python3-h5py
https://packages.gentoo.org/packages/dev-python/h5py
https://fedora.pkgs.org/30/fedora-x86_64/python3-h5py-2.9.0-3.fc30.x86_64.rpm.html

@ahcorde sorry, fixed

Thank you for iterating


Show notification when default formatter is gone

This PR is for https://github.com/Microsoft/vscode/issues/71400

@jrieken please merge into release/1.33 branch


Prefer refutable slice patterns over len check + index op

Just something I noticed while reviewing other PRs
We do it for shim arguments almost everywhere, but when the size is not statically known, we didn't use the helpers as they rely on array ops. But we can avoid a len check followed by several index ops by just using a refutable slice pattern with let else.
The pattern is so common, it seems almost worth a dedicated macro

Nice. :)
@bors r+

:pushpin: Commit b02f3493aa18ddabd709c8a7b64c31cbf2bbb971 has been approved by RalfJung
It is now in the queue for this repository.

:hourglass: Testing commit b02f3493aa18ddabd709c8a7b64c31cbf2bbb971 with merge 52360b0a795c19d846bffc041e21104d00cf1eb2...

:sunny: Test successful - checks-actions
Approved by: RalfJung
Pushing 52360b0a795c19d846bffc041e21104d00cf1eb2 to master...

Wow. This is a very nice pattern.


Add receive intent feature

Ticket: Ability to use intent - sharing#184
Few config need to be done in the host platform (Android and iOS)
Ensemble Live PR - https://github.com/EnsembleUI/ensemble_live/pull/34
iOS - WIP
User can able to send text, images, videos and any files to the Ensemble Apps. You can get the files or text like below
View:
  header:
    title: Receive Intent
  styles:
    scrollableView: true
  onLoad:
    receiveIntent:
      onReceive: |
        //@code
        textId.text = event.data.text;
        imageId.source = event.data.file;
      onError: |
        //@code
        console.log("Failed to get the data");

See the following video. Here, I passed image (from gallery app) and text (from notes app) to the Ensemble App
Text: https://drive.google.com/file/d/1JhCTcxxN-EenleNl6uzKm1tMQeUSk6Tq/view?usp=share_link
Image: https://drive.google.com/file/d/1JjvBx1Pun7AVBZky9h4nmudIuiOZAbsV/view?usp=share_link

This only works if our App is on the page that has an intent listener. We need a concept of global listeners (incoming intents, notifications, deep links) that will trigger an Action regardless of what page we are on.

@vinothvino42 this has been waiting for your response for two weeks! Please see Vu's comment and make changes or respond

@vinothvino42 this has been waiting for your response for two weeks! Please see Vu's comment and make changes or respond

@vusters @kmahmood74 Today I also I worked on this issue. In iOS, it's not working as expected but android it's working. Can I simply update and merge these changes.

@vinothvino42 please merge this and close the ticket. Create another ticket for Android.

@vinothvino42 please merge


Added rate limiter

I'm not quite certain about adding it to another file as an example. Hope this is right.

Looks good to me. Nice work and thank you for your contribution.


terminationGracePeriodSeconds: field not declared in schema

Hi Kong team,
I'm unable to deploy a Kong chart successfully after Helm Chart version 2.8.2 due to the following error:

error validating data: ValidationError(Deployment.spec.template.spec.containers[0]): unknown field "terminationGracePeriodSeconds" in io.k8s.api.core.v1.Container

The above error is from Kong Helm chart v2.10.2
I've tried deploying on both kubernetes 1.21 and 1.22 both running in EKS
I'm using ArgoCD 2.4.4
I think the suspecting code is https://github.com/Kong/charts/blob/ab5d60f8342d91d2b9883d152c64be9cd7d3c174/charts/kong/templates/_helpers.tpl#L626
besides the fact the it says .Values.ingressController.terminationGracePeriodSecond and your values.yaml file has ingressController.terminationGracePeriodSeconds (Seconds plural)
I've tried both terminationGracePeriodSeconds and terminationGracePeriodSecond in my values file but that doesn't change the error.
But after a lot of reading I think the reason is that terminationGracePeriodSeconds is not apart of the Kubernetes schema in spec.template.spec.containers. See https://kubernetes.io/docs/reference/generated/kubernetes-api/v1.22/#pod-v1-core

Hi @flickers 👋
Thanks for your report! I believe #640 should fix your problem. We should have a release sometime this week which will have this fix.


run() has inconsistent signatures for the local and remote engines

While working on #334, I noticed that the LocalEngine and RemoteEngine have inconsistent signatures. In particular:

LocalEngine.run():
run(self, program, *, args=None, compile_options=None, run_options=None):

RemoteEngine.run():
run(self, program: Program, shots: Optional[int] = None):

This leads to the odd case where running a program for 50 shots looks like
eng.run(prog, run_options={"shots": 50})

on the local engine (here, run_options passes runtime specific options directly to the backend Operation.apply() methods), but looks like
eng.run(prog, shots=50)

on the remote engine.

#327 might be relevant as a whole and had a review comment there which might also be connected