Docs are outdated

Doing (literally) this code will work but gives a warning:
"'AdaptiveCard.AdaptiveCard()' is obsolete: 'Please use the overload that accepts a version parameter and specify the version your card requires'"
Clicking on "Show Potential Fixes" shows none.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 20a9d59f-d59c-47a4-2b41-389183c551ea
Version Independent ID: b62496c8-3bf5-c148-c0b5-cfe25b520998
Content: Render a card - .NET HTML SDK - Adaptive Cards
Content Source: AdaptiveCards/sdk/rendering-cards/net-html/render-a-card.md
Product: adaptive-cards
GitHub Login: @matthidinger
Microsoft Alias: mahiding

Updated the docs in the latest push to include the new signature

@matthidinger This issue appears to have been closed prematurely. The obsolete warning persists as of Visual Studio 2019 version 16.5.1.
This code snippet is throwing the warning:
   // Build a simple card
   // In the real world this would probably be provided as JSON
   AdaptiveCard card = new AdaptiveCard()
   {
       Body = { new AdaptiveTextBlock() { Text = "Hello World" } }
   };

If you were to modify this documentation to use the following code instead, Visual Studio 2019 will no longer throw this warning:
    var schemaVersion = renderer.SupportedSchemaVersion;
    var newCard = new AdaptiveCard(schemaVersion)
    {
        Body = { new AdaptiveTextBlock() { Text = "Hello World" } }
    };

Thanks!


Does not build

Hey there!
So I have a little issue, when I run "npm run build" it does not create a build folder, is the build folder in the .next folder or is this not possible?
Thanks,
Daniel Lvovsky

Nvm I resolved the issue.


Calling rake geocode:all CLASS=YourClass throws NoMethodError

The rake task fails with the following issue, using Mongoid. Also, confirming that the library works well as part of my app, its just running it in bulk fails. (also confirming that I renamed "YourClass" when calling rake)
rake aborted!
NoMethodError: undefined method `find_each' for #<Mongoid::Criteria:0x007ff02855d370>
Did you mean?  find
               find_all
/Users/user/.rvm/gems/ruby-2.3.1@our-app/gems/mongoid-5.1.5/lib/mongoid/criteria.rb:502:in `method_missing'
/Users/user/.rvm/gems/ruby-2.3.1@our-app/gems/geocoder-1.4.0/lib/tasks/geocoder.rake:19:in `block (2 levels) in <top (required)>'
/Users/user/.rvm/gems/ruby-2.3.1@our-app/gems/rake-11.3.0/exe/rake:27:in `<top (required)>'
/Users/user/.rvm/gems/ruby-2.3.1@our-app/bin/ruby_executable_hooks:15:in `eval'
/Users/user/.rvm/gems/ruby-2.3.1@our-app/bin/ruby_executable_hooks:15:in `<main>'
Tasks: TOP => geocode:all

Beginner Task:
For mongo, do not use find_each here: https://github.com/alexreisner/geocoder/blob/master/lib/tasks/geocoder.rake#L14#L19
Follow the advice in this stack overflow answer: http://stackoverflow.com/questions/7041224/finding-mongodb-records-in-batches-using-mongoid-ruby-adapter


Increment & Decrement COUNTER

Issue Type:

[ ] Bug Report
[x] Feature Request
[ ] Documentaion

will be adding an increment/decrement counter using ReactJS with the help of hooks. And will also be adding comments to help further for easy understanding for beginners.
Please assign me this issue.
I am a GSSOC'22 participant.

The scope of this repo as of now is only projects with Vanilla JS


Version 0.0.1

Landed in https://github.com/metarhia/lowscript/commit/c3bbf3d6126ee647b10d20c8d62a18bf347cd52a, https://github.com/metarhia/lowscript/commit/5e5f0fd5ea7ab3419bac8940c7b27d3c917fc744, https://github.com/metarhia/lowscript/commit/7c60eab68e2955add10db70403ea56598d11cbe2, https://github.com/metarhia/lowscript/commit/75a7b7731d2a3887cd8667203914665c54363569, and https://github.com/metarhia/lowscript/commit/7b9a2c9b16b90a4ed391f6e43eb41154ee412bfe


[Accessibility]A11y_VSCode_Feedback_Keyboard:Controls are not accessible by keyboard.

Environment Details:
VSCode Version : 1.24.1
OS Version : Win10
Additional Details:
Keyboard,MAS2.1.1
Repro Steps:

Launch VS Code.
2.Navigate to Status Bar -->weet Feedback" button.
Check the keyboard navigation.

Actual:
"Tweet Feedback" button is not accessible by keyboard.it is only accessible through mouse.
Expected:
"Tweet Feedback" button should accessible through keyboard.
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/pages/browse-fixes.aspx
User Impact:
The keyboard user will not be able to access the control.
MAS Reference:
https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={8492c4eb-c179-40ae-8777-cd044ed725a2}
Does this issue occur when all extensions are disabled?: Yes/No
Attachment For Reference
[Accessibility]A11y_VSCode_Feedback_Keyboard.pptx

cc @bpasero Is the status bar accessible at all?

@joaomoreno every entry has a related global command, so you do not have to execute something from down there imho via keyboard.

@AccessibilityTestingTeam-TCS Would making a global command for opening the Feedback widget solve this?


Switch to binary rpc at some point

JSON-RPC has been convenient so far but has limitations - we are burying a base64-encoded binary payload at the moment to take advantage of msgpack which supports NaN, inf, etc. as numeric values.
We might want to switch to a binary rpc method (msgpack-rpc or something like that) when a client for javascript becomes stable and if it's not too heavyweight.

As an alternative, since our API is so small (just a handful of methods) we could craft a RESTful service pretty easily using e.g. Falcon and gunicorn instead of the RPC pattern.  Then switching between encodings/JSON/msgpack etc would just involve swapping middleware on the server and client sides.  Might make life easier.

The hug implementation used for python 3 outputs results by default in msgpack directly.  We could eventually use https://github.com/lebedov/msgpack-numpy to skip the conversion to python types.


Output pose length does not match the input audio

Hi,
I am wondering why we have to divide the word and audio into several sequences during inference.
That somehow results in shorter output pose than input audio. Is there a way to fix that?

Hi, we did the subdivision following prior work, to keep our comparisons fair. As a result, if the clip length is not an exact multiple of the subdivision length, the final portion is dropped from the generation pipeline. You can change this behavior by changing the value of unit_time. I have added unit_time as a parameter in the method render_clip inside processor_v2.py to make this easier.

How should I set the unit_time? the same as len(clip_audio) / 16000?

I managed to fix them. Thank you.


// comment inside /* */ comment breaks parsing for javascript

Using v1.12.0
Language javascript:
/*
 * ([{}])
 * //  <= double slash comment
 * ([{}]) <= punctuation
 */

I reverted cebacdfa195b298ee6046e4d6a5c06058cb54090 to fix this issue. Because the use-case for single line comment inside multi-line comment is more common than the opposite.


Today view, what habits to be done today (and order)

1.5)* Today view, what habits to be done today (and order)
[Time: 5; Risk Level: Med]

comeplted 72dfbc1fe0ec2af79909256b8ad4bff8207f77ac


matplotlib rc('text', usetex=True) breaks plotting from .ipynb to .py (jupyter --> spyder)

Description of your problem
I loaded a .py file from jupyter to use it in spyder. But the plotting does not work anymore. I narrowed it down to the rc('text', usetex=True) command. I asked this on stackoverflow:
Original Question:
http://stackoverflow.com/questions/40266888/migrating-jupyter-notebook-to-py-file-spyder-basic-plotting-is-killed-by-late
What steps will reproduce the problem?
create a .py script in spyder:
import numpy as np
import matplotlib as mpl
import matplotlib.pyplot as plt
import matplotlib.gridspec as gs

from matplotlib import rc # this is the matplotlib suggestion
rc('font',**{'family':'sans-serif','sans-serif':['Arial']})
rc('text', usetex=True)

mat = np.random.rand(5,5)

fig = plt.figure()
gsall = gs.GridSpec(6, 1)
ax1 = fig.add_subplot(gsall[:])
source1 = ax1.contourf(mat,extend='both',cmap=mpl.cm.viridis)
plt.title('Random field \n test')
plt.colorbar(source1)
plt.show()

run it.
What is the expected output? What do you see instead?
I expect a figure with the random matrix and the text, but I get many errors.
Please provide any additional information below
In jupyter notebook everything is fine. In ipython shell I get a figure without the text and no errors.
Versions and main components

Spyder Version: 2.3.9
Python Version: 3.5.1
Operating system: macOS sierra v.10.12.1
Matplotlib Version: 1.5.1

Could you update to Spyder 3.0 and try again? Spyder 2.3.9 is no longer maintained :-)

thanks @ccordoba12 the scripts are working now. But Anaconda Navigator does not start anymore. I can start jupyter and spyder from the command line, but the navigator is very useful for me. So I will try to find a solution for that.

Hi @louika
I think you only need:

Latest version of spyder (3.0.1)
sudo apt-get install dvipng (library for manage latex character conversion on matplotlib)

for you can to reproduce this example without problems over Ipython console.

I hope this help you.

Closing, as the last line of the error you posted in StackOverflow
FileNotFoundError: [Errno 2] No such file or directory: 'kpsewhich'

means that you don't have Latex installed, or that is not configured correctly.

And, this has nothing to do with Spyder.
I get the same headache on the command line.
Seems to be a Tkinter / latex issue.
Sacre merde alors!  (=:

Yes, I have latex installed with pip and pip3

What do you mean by this? Latex can't be installed with pip, you need to install with your package manager (i.e. apt-get, emerge, etc, since you're using Linux).

sudo pip3 install latex
installs a Python package called "latex".
However, there must be, as you said, a native-code executable?  Okay.
You use a debian-ish Linux? If so, which package gets the latex executable?
If RPM, then the same question.
Thank you.

Debian/Ubuntu/Mint package texlive-full seems to be an effective solution (yuge!).  Also can be downloaded from http://www.tug.org/texlive/
Anyways, as I said before, this has nothing to do with spyder.

Debian/Ubuntu/Mint package texlive-full seems to be an effective solution (yuge!).  Also can be downloaded from http://www.tug.org/texlive/
Anyways, as I said before, this has nothing to do with spyder.

This comment suggests that it may still be related to spyder after all.

@ImportanceOfBeingErnest, if you define or extend PATH in your .bashrc or and don't start Spyder in a console but using a graphical menu or launcher, then Spyder is unable to detect those modifications to PATH because it doesn't read your environment variables before launching. By the way, Pycharm also has this problem, as reported here:
https://stackoverflow.com/a/9706384/438386
And I think the same happens in the Jupyter notebook. I mean, I haven't seen any code to read env vars in Jupyter or IPython. But the problem could be alleviated there because you usually start the notebook server in a console, and so their environment is picked by the kernels started by it.
To summarize, I don't know if you could say this is a Spyder problem or people not knowing how env vars work.


feat: unpack bootstrap using TypeScript for cross-platform compatibility

Hi @HRAshton, thanks! I was not aware of this platform issue. I assumed these commands are executed inside the docker container, but yeah, the underlying NodejsFunction does local bundling if esbuild is available locally, and it may not work on different shell or Windows environment.
So, another solution is to use forceDockerBundling flag, which forces bundling commands run in a container and become free from cross-platform issues. What do you think?
I'm afraid your solution may not work after npm publish because ts-node or unzipper are in dev dependencies. Also I'd like to keep dependencies as small as possible for maintenability.

Hmm.. Make sense, I'll try it, thank you

I guess something like this should work on Windows.
    new LlrtFunction(this, 'Handler', {
      entry: 'handler.ts',
      bundling: {
        forceDockerBundling: true,
      },
    });

Please let me know if it doesn't work. I don't have Windows environment in hand 🙏  Then we can update README to describe the workaround.

@HRAshton I updated the code to automatically set forceDockerBundling: true on Windows platform. b9e41f7 along with updating README. Let me know if you have further problem. Thanks again!

Yes, I just checked it out, works great) Thanks!


isobib can't find the ISO/IEC Directives

... Because they do not show up in a search on the ISO website. (The Rice model does :-(
This is bad; bad enough, @ronaldtse, that it should be escalated to ISO. The gem is predicated on the assumption that all ISO publications are discoverable through the web search. In the interim, I will need to code an exception in the gem for the contents of http://www.iso.org/directives.

I am restricting the manual exceptions in isobib to:

ISO/IEC Directives, Part 1
ISO/IEC Directives, Part 1 Consolidated ISO Supplement
ISO/IEC Directives, Part 2

And the citations will need to appear exactly like that. I have no idea if there even is a document identifier for the other documents appearing in http://www.iso.org/directives, such as the Vienna agreement; and if ISO have not (the VA in the footer does not count), then I can't.

And these? 😉
http://www.iec.ch/members_experts/refdocs/
e.g. "ISO/IEC Directives, IEC Supplement:2018"

Unfortunately while the PDFs of ISO/IEC DIR are discoverable at IEC, which they are not at ISO, that's useless, because there is no associated landing page in the webstore, so there is no discoverable metadata about the PDFs. Nor will either ISO or IEC be motivated to create landing pages for them. The only way unfortunately is to create custom XML :(

Right, perhaps we can make a general mechanism that overrides Relaton Bib items.
For example, we could have a new repo called "relaton-iso-overrides" that details these “special cases” in some YAML file, and Relaton will use these to override.
I’m pretty sure we will run into these soon, not only for ISO, but also other orgs like IEC etc.

This issue is moved to https://github.com/relaton/relaton/issues/57

@andrew2net can we keep this open? This specifically relates to relaton-iso, while the referred task is a generic task across Relaton. Thanks.

@andrew2net is this done? Can you update metanorma.com on how to refer to these documents and close this? Thanks.

@ronaldtse the static cache is created. While we were discussing references format I switched to another task. So now we just need to make YAML files and put them to the static cache directory.
The filenames should be lowercased references with symbols and break spaces replaced by underscores. There is one example https://github.com/relaton/relaton/blob/feature/support-un-fetchable-data/lib/relaton/static_cache/iso/iso_iec_directives_part_1.yml

Solved in https://github.com/relaton/relaton/issues/57


[BUG] Upgrade failed through Rancher (2.5.5) UI from 1.2.0 -> 1.2.2

Describe the bug
The upgrade of Longhorn from version 1.2.0 to 1.2.2 failed with the following error message
Failed to install app longhorn-system. Error: UPGRADE FAILED: kind CustomResourceDefinition with the name "backups.longhorn.io" already exists in the cluster and wasn't defined in the previous release. Before upgrading, please either delete the resource from the cluster or remove it from the chart

To Reproduce
Steps to reproduce the behavior:

Go to Apps
Click on Longhorn Upgrade
Review settings and start
See error message above in the longhorn chart overview

Expected behavior
Expected that all workloads from longhorn will be updated to version 1.2.2
Log or Support bundle
If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment

Longhorn version: 1.2.0
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): Rancher Catalog App
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: RKE

Number of management node in the cluster: 7
Number of worker node in the cluster: 2

Node config

OS type and version: Ubuntu Server 20.04
CPU per node: 4
Memory per node: 64
Disk type(e.g. SSD/NVMe): SSD/HDD/NVMe
Network bandwidth between the nodes: 10G

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): Baremetal/VM
Number of Longhorn volumes in the cluster: 26

Additional context
Add any other context about the problem here.

Seems to be related to the issue https://github.com/longhorn/longhorn/issues/3166
There are 2 rancher UIs:

the old one

and the new one

Please use the same UI that you installed Longhorn to upgrade Longhorn

Hi @PhanLe1010, thank you for your fast reply.
I am aware of this issue. I created the longhorn with the old catalog ui and also updated all versions with it, the last update was to version 1.2.0.
I do not use the new UI because there is no chart for the newer Longhorn Verions.

Is it safe to just delete the CRD? And try to rerun the update process?

If you delete the CRDs, doesn't that mean you have to delete the K8s resources matching the CRDs too which would mean you lose PVCs?
I wrote a blog post on how I upgraded it here without deleting any data. Ultimately, I used kubectl change the labels and annotations. Then used Helm to deploy over top of the existing resources and it worked. I think this should be the same fix for your case.
KUBE_CONTEXT=prod

kubectl --context=$KUBE_CONTEXT get crds -o name | grep longhorn | xargs -I % kubectl --context=$KUBE_CONTEXT label --overwrite -n longhorn-system % app.kubernetes.io/managed-by=Helm

kubectl --context=$KUBE_CONTEXT get crds -o name | grep longhorn | xargs -I % kubectl --context=$KUBE_CONTEXT annotate -n longhorn-system % meta.helm.sh/release-name=longhorn-crd

kubectl --context=$KUBE_CONTEXT get crds -o name | grep longhorn | xargs -I % kubectl --context=$KUBE_CONTEXT annotate -n longhorn-system % meta.helm.sh/release-namespace=longhorn-system

kubectl --context=$KUBE_CONTEXT get psp longhorn-psp -o name | xargs -I % kubectl --context=$KUBE_CONTEXT annotate % meta.helm.sh/release-name=longhorn

kubectl --context=$KUBE_CONTEXT get psp longhorn-psp -o name | xargs -I % kubectl --context=$KUBE_CONTEXT annotate % meta.helm.sh/release-namespace=longhorn-system

kubectl --context=$KUBE_CONTEXT -n longhorn-system get configMap,service,ds,deploy,serviceaccount,role,rolebinding -o name  | xargs -I % kubectl --context=$KUBE_CONTEXT label --overwrite -n longhorn-system % app.kubernetes.io/managed-by=Helm

kubectl --context=$KUBE_CONTEXT -n longhorn-system get configMap,service,ds,deploy,serviceaccount,role,rolebinding -o name  | xargs -I % kubectl --context=$KUBE_CONTEXT -n longhorn-system annotate % meta.helm.sh/release-name=longhorn

kubectl --context=$KUBE_CONTEXT -n longhorn-system get configMap,service,ds,deploy,serviceaccount,role,rolebinding -o name  | xargs -I % kubectl --context=$KUBE_CONTEXT -n longhorn-system annotate % meta.helm.sh/release-namespace=longhorn-system

kubectl --context=$KUBE_CONTEXT get clusterrole,clusterrolebinding -o name | grep longhorn   | xargs -I % kubectl --context=$KUBE_CONTEXT label --overwrite -n longhorn-system % app.kubernetes.io/managed-by=Helm

kubectl --context=$KUBE_CONTEXT get clusterrole,clusterrolebinding -o name | grep longhorn   | xargs -I % kubectl --context=$KUBE_CONTEXT annotate % meta.helm.sh/release-namespace=longhorn-system

kubectl --context=$KUBE_CONTEXT get clusterrole,clusterrolebinding -o name | grep longhorn   | xargs -I % kubectl --context=$KUBE_CONTEXT annotate % meta.helm.sh/release-name=longhorn

If you're using the old UI to manage, please keep using the old UI to manage it.
Also, please do not delete the CRDs otherwise all the Longhorn CRs would lost.

@ajacques Thank you, your post relates to Rancher 2.6, I still use the old version 2.5.5. Will your description also match for the old Rancher version 2.5.5?
@jenting As I wrote, I have created Longhorn with old UI and updated each time with old UI. I thought when I delete the CRD, the Helm Chart would recreate it during the update process??

Right, but it also means that the Longhorn CRs would be deleted as well. Then, the Longhorn cluster will broken.

ahh I see, thank you! Then this is not the way.

@ajacques Thank you, your post relates to Rancher 2.6, I still use the old version 2.5.5. Will your description also match for the old Rancher version 2.5.5?

It'll let you migrate to Helm 3 even if you're still using Rancher 2.5.x. I assumed this is the problem because this is the same error I got when I tried to switch my Helm 2 version of Longhorn to Helm 3.

Right, but it also means that the Longhorn CRs would be deleted as well. Then, the Longhorn cluster will broken.

My proposed fix does not delete the CRDs. It modifies the CRDs so you can upgrade in place.

@ajacques Thank you, your post relates to Rancher 2.6, I still use the old version 2.5.5. Will your description also match for the old Rancher version 2.5.5?

This allows you to upgrade to Helm 3 (it's actually not related to Rancher 2.6 or Rancher 2.5, but I ended up doing this because Rancher 2.6 removed Helm 2, but ultimately it's a similar problem). I assumed this is your problem because this is the same error I got when I tried to switch my Helm 2 version of Longhorn to Helm 3.

Right, but it also means that the Longhorn CRs would be deleted as well. Then, the Longhorn cluster will broken.

My proposed fix does not delete the CRDs. Note the commands do not delete any resources. It modifies the CRDs so you can upgrade in place. Following this, I was able to continue using Longhorn without deleting any volumes and after upgrading PVCs and restarting pods, it worked perfectly.

cc @shuo-wu

@ajacques
Thank you for this explanation. I will try to update between the years and will report back in this issue.

If you delete the CRDs, doesn't that mean you have to delete the K8s resources matching the CRDs too which would mean you lose PVCs?
Instead of deleting CRDs, I figured out a way to upgrade to Helm 3 in place and wrote a blog post on how I upgraded it here without deleting any data or CRDs. Ultimately, I used kubectl change the labels and annotations. Then used Helm to deploy over top of the existing resources and it worked. I think this should be the same fix for your case.
KUBE_CONTEXT=prod

kubectl --context=$KUBE_CONTEXT get crds -o name | grep longhorn | xargs -I % kubectl --context=$KUBE_CONTEXT label --overwrite -n longhorn-system % app.kubernetes.io/managed-by=Helm

kubectl --context=$KUBE_CONTEXT get crds -o name | grep longhorn | xargs -I % kubectl --context=$KUBE_CONTEXT annotate -n longhorn-system % meta.helm.sh/release-name=longhorn-crd

kubectl --context=$KUBE_CONTEXT get crds -o name | grep longhorn | xargs -I % kubectl --context=$KUBE_CONTEXT annotate -n longhorn-system % meta.helm.sh/release-namespace=longhorn-system

kubectl --context=$KUBE_CONTEXT get psp longhorn-psp -o name | xargs -I % kubectl --context=$KUBE_CONTEXT annotate % meta.helm.sh/release-name=longhorn

kubectl --context=$KUBE_CONTEXT get psp longhorn-psp -o name | xargs -I % kubectl --context=$KUBE_CONTEXT annotate % meta.helm.sh/release-namespace=longhorn-system

kubectl --context=$KUBE_CONTEXT -n longhorn-system get configMap,service,ds,deploy,serviceaccount,role,rolebinding -o name  | xargs -I % kubectl --context=$KUBE_CONTEXT label --overwrite -n longhorn-system % app.kubernetes.io/managed-by=Helm

kubectl --context=$KUBE_CONTEXT -n longhorn-system get configMap,service,ds,deploy,serviceaccount,role,rolebinding -o name  | xargs -I % kubectl --context=$KUBE_CONTEXT -n longhorn-system annotate % meta.helm.sh/release-name=longhorn

kubectl --context=$KUBE_CONTEXT -n longhorn-system get configMap,service,ds,deploy,serviceaccount,role,rolebinding -o name  | xargs -I % kubectl --context=$KUBE_CONTEXT -n longhorn-system annotate % meta.helm.sh/release-namespace=longhorn-system

kubectl --context=$KUBE_CONTEXT get clusterrole,clusterrolebinding -o name | grep longhorn   | xargs -I % kubectl --context=$KUBE_CONTEXT label --overwrite -n longhorn-system % app.kubernetes.io/managed-by=Helm

kubectl --context=$KUBE_CONTEXT get clusterrole,clusterrolebinding -o name | grep longhorn   | xargs -I % kubectl --context=$KUBE_CONTEXT annotate % meta.helm.sh/release-namespace=longhorn-system

kubectl --context=$KUBE_CONTEXT get clusterrole,clusterrolebinding -o name | grep longhorn   | xargs -I % kubectl --context=$KUBE_CONTEXT annotate % meta.helm.sh/release-name=longhorn

It looks fantastic and glad to see it's workable without having to reinstall the longhorn cluster so the Longhorn app is able to be managed by the new Rancher UI after migration. Thanks for the sharing.

@ajacques
Would you mind contributing to the Longhorn knowledge base according to your blog post?
If yes, please file the PR to the https://github.com/longhorn/website and we'll review it, thank you :pray:

Sorry for my late reply 😶
@ajacques
I performed all the commands, after that I used the new Rancher UI to upgrade Longhorn to the newest version.
This failed with the following error message:
helm  upgrade --history-max=5 --install=true --namespace=longhorn-system  --timeout=10m0s  --values=/home/shell helm/values-longhorn-1.2.300-up1.2.3.yaml  --version=1.2.300+up1.2.3 --wait=true longhorn-system  /home/shell/helm/longhorn-1.2.300-up1.2.3.tgz
Release "longhorn-system" does not exist. Installing it now.
Error: rendered manifests contain a resource that already exists. Unable to continue with install: PodSecurityPolicy "longhorn-psp" in namespace "" exists and cannot be imported into the current release: invalid ownership metadata; label validation error: key "app.kubernetes.io/managed-by" must equal "Helm": current value is "Tiller"; annotation validation error:
key "meta.helm.sh/release-name" must equal "longhorn-system": current value is "longhorn"

In your blog post, you say "deploy the Longhorn application". Do you mean, that I need to redeploy the Chart from the marketplace instead of updating the old Longhorn App?

In your blog post, you say "deploy the Longhorn application". Do you mean, that I need to redeploy the Chart from the marketplace instead of updating the old Longhorn App?

Yes, you're going to deploy it from the Marketplace since that'll ensure it gets installed with Helm v3.

label validation error: key "app.kubernetes.io/managed-by" must equal "Helm": current value is "Tiller"

This can be fixed by running (and I've updated the doc):
kubectl --context=$KUBE_CONTEXT get psp longhorn-psp -o name | xargs -I % kubectl --context=$KUBE_CONTEXT label --overwrite -n longhorn-system % app.kubernetes.io/managed-by=Helm

key "meta.helm.sh/release-name" must equal "longhorn-system": current value is "longhorn"

However, this error is interesting. AFAIK, the release-name was supposed to be 'longhorn', not 'longhorn-system', as per 1, 2, and 3 Maybe somebody else knows why. It's easy to fix, but maybe somebody else knows if this is correct or not?

However, this error is interesting. AFAIK, the release-name was supposed to be 'longhorn', not 'longhorn-system', as per 1, 2, and 3 It's easy to fix, but maybe somebody else knows if this is correct or not?

The app name comes from the old marketplace where I firstly install longhorn, is there a way that I can just rename the current App from longhorn-system to longhorn? I am not brave enough to just reinstall the newer version with a different name 😅

I am not sure if it's possible and what the potential impact is. If you want to retain the Longhorn volumes in the old Longhorn, I would not recommend doing so. Does this naming matter?

Does this naming matter?
I am not sure about that. As @ajacques mentioned in his post, I changed the labels and annotations. In his post, the name of the app is longhorn. Now, when I reinstall the App over the marketplace, but the old app has the name longhorn-system, I think this could lead to a double deployed application with different names. But I did not try this yet because the cluster is productive.

I am not sure about that. As @ajacques mentioned in his post, I changed the labels and annotations. In his post, the name of the app is longhorn. Now, when I reinstall the App over the marketplace, but the old app has the name longhorn-system, I think this could lead to a double deployed application with different names. But I did not try this yet because the cluster is productive.

If you run

helm  list --namespace=longhorn-system

Does it show a release named longhorn-system and longhorn-crds?
There's three options:

The safe option - Do nothing
Rename the Helm release from longhorn-system to longhorn using something like this
Continue using the longhorn-system release by changing the annotate -n longhorn-system % meta.helm.sh/release-name=longhorn parts in my script to annotate -n longhorn-system % meta.helm.sh/release-name=longhorn-system

On further reading of your GitHub issue it seems like your issue was that the CRDs were not created using Helm, but the Longhorn application itself was? If so, then option 3 can be used to undo the part that is currently broken and should permit upgrades to continue:
kubectl --context=$KUBE_CONTEXT get psp longhorn-psp -o name | xargs -I % kubectl --context=$KUBE_CONTEXT annotate % meta.helm.sh/release-name=longhorn-system
kubectl --context=$KUBE_CONTEXT -n longhorn-system get configMap,service,ds,deploy,serviceaccount,role,rolebinding -o name  | xargs -I % kubectl --context=$KUBE_CONTEXT -n longhorn-system annotate % meta.helm.sh/release-name=longhorn-system
kubectl --context=$KUBE_CONTEXT get clusterrole,clusterrolebinding -o name | grep longhorn   | xargs -I % kubectl --context=$KUBE_CONTEXT annotate % meta.helm.sh/release-name=longhorn-system

Changing the annotation doesn't do much other than tell Helm that yes it's okay to touch those resources.

@ajacques Thank you so much!!
With option 3 I was able to upgrade longhorn and after that successfully update rancher to the latest version and I can still manage everything correctly 🥳


fixed IngameTick value

The IngameTick field didn't reflect to the tick reported by the demo file, now it is.

This would most likely break

ParsingProgress and
CurrentTime

Have you tested this?

I just tested it, these 2 values was wrong.
I pushed a fix but the tick value from NETTick is not used now (it returns strange value).

This reversed the last commit, so I don't think it's useful. Ingame-Tick is the way to go then. I think renaming CurrentTick would do the trick. I'll look into a better solution, but I can't promise anything.

mmmm the last commit revert partially the 1st commit.
The important thing in the last commit is that IngameTick (https://github.com/akiver/demoinfo/blob/e08732e2bc8af03c95a060677902cd613dad086a/DemoInfo/DemoParser.cs#L579) correspond to the tick displayed by the demo (it is not the case ATM).
ParsingProgress and CurrentTime are working as before.
Thanks

I can't reopen the pull-request - that would be something you need to do.

I made clean PR.
Thanks


ColorPickerDemo Sample

There is already a simple sample for this. Please check that first to see if anything is needed.


Can you add support for trigonometric functions sin(x), cos(x), etc in BARON.jl?

Thank you very much for all your hard work.
I have another need that I don't know if I can fulfill. In BARON's documentation, there is no support for trigonometric functions, could you please help to add support for trigonometric functions in BARON.jl? For example. sin， cos, or provide an idea for BARON to support these trigonometric functions?
Thank you very much.

Hi @askuyue,
Unfortunately, no.
See the BARON manual: https://minlp.com/downloads/docs/baron manual.pdf

p.s., Please note that BARON.jl is not an official product of the Optimization Firm: https://github.com/jump-dev/BARON.jl?tab=readme-ov-file#affiliation. If you are a commercial customer and you have feature requests for BARON, you should reach out to their support team.

Thanks.

Don't be sorry. No question is a bad question :smile:


Feature 'file-scoped namespaces' is not available. Please use language version 10.0 or greater.

We'd like to use AutoInterface in an API client SDK which we're targeting to netstandard2.1
Unfortunately, it seems that AutoInterface generates types with file-scoped namespaces. This is unsupported in C# 8.0, which is the highest language version that is supported by .NET Standard 2.1.
Can we generate the interfaces in a namespace block to mitigate this issue?

It seems that init properties are unsupported in this use case too.
I would be happy to submit a PR to change these if it would be accepted. Let me know. :)

If your condition is just the use of some older framework, I recommend to set the language version to 12 and also include PolySharp:
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <TargetFramework>netstandard2.1</TargetFramework>
    <LangVersion>12</LangVersion>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="AutoInterface" Version="2.1.0" PrivateAssets="all" />
    <PackageReference Include="PolySharp" Version="1.14.1" PrivateAssets="all" />
  </ItemGroup>

</Project>

This is something I considered, but the SDK we're writing is for our Unity frontend and we're reluctant to put things into what is an officially unsupported configuration.

yeah, Unity is known for being stone age, the target group for Unity are mostly beginner programmers. As experienced programmer it can be pretty rough to work with Unity, especially when it comes to language features and software architecture.
Give it a try. Set the language version to “latest” and see what you get. If you get C#12, Unity uses an up-to-date Roslyn compiler. Then try to compile and try to build a release version, if both works, you are good to go. The possibility of side effects is neglectable. I won’t they, they are impossible, but changing the language version is actually a pretty small and local change. The configuration affects only the compile process from your code to the IL assembly and everything beside that (other assemblies, linking of these assemblies, runtime) will be untouched.
PolySharp is even more harmless. It is just a source generator that creates some polyfill classes.
Regardless of the outcome, I already thought about the problem of language version compatibility. There was the decision between breaking everything down to version C#7.3 or just using the new features. I decided to just use the new features, because changing the language version is not a big deal.


Needs update!!!

Had to fix a whole bunch of warnings to get this to work.  Despite being only a year old, it's way out of date.
Authors need to bring this up to date.
Here is a working version (no starter/complete folders, just the project with tags - name is changed): https://github.com/rickbsgu/my_admob_tutorial
There is a 'starter' tag you can use to follow the tutorial, if you want.
Note there is an issue with android on an m1 mac.  I've reported that in #22, with a Stackoverflow link: https://stackoverflow.com/questions/72116841/admob-issues-on-m1-mac-for-android

one specific issue is that on step 9 the guide uses _rewardedAd!.show() when RewardedAd's .show() method requires a Function as an argument these days.

Thanks for the input.
Can you point me to a reference that spells that out?

Hello all - the sample code has been updated! It should include the fix for the issues reported so far :)


Nothing in my browser nor in terminal

As in readme file I made changes to code.When I run the code with yarn run notifiction catcher as mentioned in readme file I am getting errors regarding yarn.So that I run the code with yarn run run-catcher then in terminal I am getting this
**

yarn run v0.27.5
$ notification-catcher
NotificationCatcher webapp running at http://<IP_ADDRESS>:1080
NotificationCatcher SMTP Server running at <IP_ADDRESS>:1025

**
When I run the following url in my browser http://localhost:1080 I am getting notifme page but I am not getting a message(as shown in readme file) which I am sending in code.

Hi @Syedayesha, the log for the notification-catcher is ok.

Sorry for that.And Thanks for your quick reply I clone th code from this github.I placed my nexmo number in notifme-sdk-master/examples/ simple.js  file and I did the same thing in notifme-sdk-master/examples/ with-notification-catcher.js file.And I used my nexmo api_key and secret_key in
notifme-sdk-master/src/models/provider-sms.js.So please help me to overcome this issue

Have you run the example? (yarn run babel-node examples/with-notification-catcher.js)
If yes, what is the log of the command?

Note: if you're trying to see the sms in the notification catcher, no need to add your Nexmo credentials.

I am getting this error.
yarn run v0.27.5
warning package.json: No license field
error Command "with-notification-catcher.js" not found.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this com
and.

Are you running the command in notifme-sdk folder?

Yes..How can I run this command outside of the notifme-sdk?Help me to get out of this..

Given the error, the only thing I can tell you is to double-check your current folder. You should be in the root folder of the project. (pwd displays where you are).


"handles_uncertainty" needs domains deterministic and stochastic

Description of the issue
The "approach to uncertainty" is part of the model factsheets (#15) and should be included in the ontology.
We have an object property "handles_uncertainty" but we dont have instances "deterministic" and "stochastic" to choose as domain, eg. model_x handles_uncertainty value stochastic.
Those two then also need a type. We have the class "Uncertainty" (subclass of validation) but I'm not sure if that fits.
Ideas of solution
Add instances "stochastic" and "deterministic" and give them a type.
Workflow checklist

[ ] I discussed the issue with someone else than me before working on a solution
[ ] I already read the latest version of the workflow for this repository
[ ] The goal of this ontology is clear to me

I am aware that

[ ] every new entry in the ontology should have an annotation
[ ] classes should arise from concepts rather than from words
[ ] class or property names should follow the UpperCamelCase

The class uncertainty was removed in #347, the object property handles uncertainty has also been deleted at some point.
This means we have to introduce a new class uncertainty handling (maybe with a better label). As this is about describing models, I would suggest to make uncertainty handling a subclass of model descriptor (analogous to analytical approach and methodical focus which also have assigned instances). Definition: Uncertainty handling is a model descriptor that specifies how a model deals with uncertainty.
Then we can add stochastic and deterministic as instances. I don't think we need a relation handles uncertainty because other model descriptors just use is  about.

Does everyone agree with my proposal (especially @p-kuckertz and @carstenhoyerklick, since you have been assigned to this issue)?

Hi Simon,
for me your proposal makes good sense:

We need this concept to describe models
Therefore it should belong to “model descriptor” (esp. when other model describing concepts have been put here)
I also agree with “is about”, since this descriptor is about a specific concept - instead of basically always asking how the model handles a, b, c, etc.

Concerning the name giving, I would prefer “uncertainty approach” (in accordance with “analytical approach” and the OEP Model Factsheet field “approach to uncertainty”), then with stochastic and deterministic as possible options.
Best regards,
Patrick

Dr. Patrick Kuckertz
Institut für Energie- und Klimaforschung –
Technoökonomische Systemanalyse (IEK-3) https://www.fz-juelich.de/iek/iek-3/DE/Home/home_node.html
Forschungszentrum Jülich GmbH
D-52425 Jülich
Telefon: +49 2461 61-1822
Mobil: +49<PHONE_NUMBER>
E-Mail: @.*** @.***>
Von: Simon Flügel @.>
Gesendet: Donnerstag, 5. August 2021 13:40
An: OpenEnergyPlatform/ontology @.>
Cc: Kuckertz, Patrick @.>; Mention @.>
Betreff: Re: [OpenEnergyPlatform/ontology] "handles_uncertainty" needs domains deterministic and stochastic (#183)
Does everyone agree with my proposal (especially @p-kuckertz https://github.com/p-kuckertz  and @carstenhoyerklick https://github.com/carstenhoyerklick , since you have been assigned to this issue)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/OpenEnergyPlatform/ontology/issues/183#issuecomment-893389946 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AICVBRUV44CUBASMKCBYRNDT3J2AZANCNFSM4J3YRP2Q .
Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675  or Android https://play.google.com/store/apps/details?id=com.github.android&utm_campaign=notification-email .


meaningful messages on files not existing

Right now, if the user provides a file that doesn't exist, they get an error message that one of the variables in the model can't be found (init or data, depending on usage).
What should happen is that we should test that the file exists and return a meaningful message if it doesn't.
I don't know whether this is something that's going to get sorted out automatically in the new command config infrastructure or not.
(I also filed the same issue on RStan.)

I'll fix this on the current branch, but it'll need to be reimplemented as part of the refactor.
The fundamental problem here is that the validation done by the arguments isn't actually validating this argument. I think we need to rethink the args. After the refactor, it'll be part of the CmdStan repo.


default export orElse for Nullable/Undefinable

This change is

:pushpin: Commit b12d63c has been approved by saneyuki

@homu r+

:hourglass: Testing commit b12d63c with merge d52d269...

:sunny: Test successful - status


More Feats

This request touches translations which is holding other activities I was willing to do. Appreciated if we get into a consensus here.


Updated Jump Statements Lesson in Java

Fixes #5
Added Jumps statement Lesson.
Issue name - new lesson: jumps statements
What changes made

added different jumps statement with code examples and explanation.
added syntax with examples.
added comments to make the lesson more understandable.

Checklist

[x] Added description of change
[x] Added code examples, test must pass
[x] Added documentation so that the program is self-explanatory and educational.
[x] Relevant documentation/comments is changed or added
[x] I acknowledge that all my contributions will be made under the project's license.

Notes:

@Ayushi7456 I think you should remove the whole Conditional Jumps section from the lesson as it is already covered in this lesson https://utkarsh1504.github.io/DSA-Java/io-conditionals
Just covered the below topics in your Pull request:

break + code examples + explanation
continue + code examples + explanation
break vs continue (comparison)
break vs continue vs return

you if face any issue during the contribuion you ask in the discussion forum.
Thank you for your hard work.🎈

I have made the changes. Please review and let me know if it's fine now.

@Ayushi7456 Thanks a lot, really appreciate your work.🎈🎉


fix console buttons hitbox on macOS

On master, for macOS, the console buttons' hitboxes are quite small. This makes clicking on the button with your mouse a little more tedious than it should be. The Issue is related to recent versions of Qt (>5.9.8) not playing so nice on macOS when there are "incorrect" width and height values set for a QPushButton (here is another example: https://github.com/bitcoin-core/gui/pull/319#pullrequestreview-652907740).
This fixes this small hitbox issue by converting the buttons from QPushButton to QToolButton. This approach was chosen as it helps us avoid having to play around with width and height values until we find values that play nice with macOS and look good on Linux & Windows. Also, QToolButton is an appropriate class for these buttons.
Per Qt Docs:

A tool button is a special button that provides quick-access to specific commands or options. As opposed to a normal command button, a tool button usually doesn't show a text label, but shows an icon instead.

Since we are changing the type of the buttons, we need to change the respective actions connection logic in rpcconsole. Instead of plugging in QToolButton, we abstract it to the base class: QAbstractButton.
per Qt Dev Notes

Use base class functions as this makes the code more general, e.g., use QAbstractButton::clicked instead of QPushButton::clicked.

While here, we also update the size of the icons to 22x22 to be consistent with other tool buttons.
macOS: Master vs PR:

Master
PR

Linux: Master vs PR:

Master
PR

Concept ACK on making clickable elements explicit (see #217).

On master, for macOS, the console buttons' hitboxes are quite small

How do your changes increase their sizes?

@hebasto

How do your changes increase their sizes?

It seems a better name for this PR would be "Make Console Buttons Look Clickable" as that is what it really does for all systems. The PR was motivated by the small hitbox bug on macOS, this is fixed by making the buttons a QToolButton instead of finding appropriate width and height values for aQPushButton.

updated from 05808da -> 8b419b5:
Changes:

Change naming of commit and pr to better represent what the PR is doing

Not a NACK, personally I think they are fine as is.

Played around and with
          </item>
          <item>
           <widget class="QPushButton" name="fontSmallerButton">
-           <property name="maximumSize">
-            <size>
-             <width>24</width>
-             <height>24</height>
-            </size>
-           </property>
            <property name="toolTip">
             <string>Decrease font size</string>
            </property>
@@ -490,7 +484,7 @@
            <property name="iconSize">
             <size>
              <width>24</width>
-             <height>16</height>
+             <height>24</height>
             </size>
            </property>
            <property name="autoDefault">

I get this

and when clicking

So it seems that maximumSize is screwing the button layout.


[WIP] RecordsGet to RecordsRead

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 98.69%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #774      +/-   ##
==========================================
- Coverage   98.69%   98.69%   -0.01%
==========================================
  Files          73       73
  Lines       11258    11257       -1
  Branches     1609     1609
==========================================
- Hits        11111    11110       -1
  Misses        141      141
  Partials        6        6

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Add BaseControllerV2 schema

A schema has been added to the new BaseController class as a required constructor parameter. The schema describes which pieces of state should be persisted, and how to get an 'anonymized' snapshot of the controller state.
This is part of the controller redesign (#337).

This depends upon #358

Replaced by #362


feat(protocol-designer): disallow saving ingred form w/o name & volume

overview
Disallow saving Ingredient Properties Form w/o name & valid volume. Also show field-level errors
Closes #1609
changelog

disable saving ingred props form w/o name & volume > 0
show field-level errors
COMPONENT LIBRARY: add some padding-top to the InputField captions, the new drop shadow overlaps them without it

review requests
IngredientPropertiesForm overall needs a big refactor, but hopefully the new structures in StepEditForm can be applied here & we can trash all the this.Field junk down the road!
So this is a somewhat ugly, non-scalable fix to make UX for ingred properties form work as desired, for now.
@mcous @Kadee80 do you use the caption of InputField? Is this padding-top addition OK?

@IanLondon When you click on wells the form starts with volume and name errors


Postal code field doesnt accept US ZIP codes

Postal Code field doesn't return true for valid US ZIP codes. It expects 6 digits to return true.
connectToState.js line 38
validatePostalCode: (postalCode = "") => {
return postalCode.match(/^\d{6}$/) ? "valid" :        <--- this has to check for both 5 and 6 digits
postalCode.length > 6 ? "invalid" :
"incomplete";
},

Yep, that's an example implementation for validating SG postal code which you could replace with your country's own ZIP code validation

Sam

Thank You Sam for the response. But the validation is in your source code, so if I make local changes to it wont it get overwritten in my next npm install ? Do you suggest creating a fork for this change ?
Thanks
Sajith

Hey Sajith, You could pass in the postal code validation function into the component.
e.g.

function myValidatePostalCode(postalCode) {
    return postalCode.match(/^\d{8}$/) ? "valid" :
               postalCode.length > 8 ? "invalid" :
               "incomplete";
}

export default class Form extends Component {
  render() {
    return (
      <CreditCardInput requirePostalCode
            validatePostalCode={myValidatePostalCode} />
    );
  }
}

Thank you for the prompt response !!
Thanks
Sajith
On Sun, Mar 5, 2017 at 6:58 PM, Sam Aryasa<EMAIL_ADDRESS>wrote:

Closed #37
https://github.com/sbycrosz/react-native-credit-card-input/issues/37.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/sbycrosz/react-native-credit-card-input/issues/37#event-987064174,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AXO_c89853Wwu4ReOLHXFTZTduWYwuo9ks5ri3ZsgaJpZM4MMt-U
.

--
Sajith Sadanandan
Evolvier Technologies


DynamicScraper from the example not doing anything

I'm trying out the examples exactly as written. The HackerNews example with scraperjs.StaticScraper works perfectly fine and I get a big array of strings.
However, replacing Static with Dynamic doesn't do anything. At all. The execution just ends with no error. I tried debugging it, adding try/catch statements, but I still get no error.
I tried "npm install phantom" too, but it doesn't change anything for scraperjs.
I have no idea what's wrong here.

+1

@jeremythille @abinashmeher999  It will work, if you downgrade phatomjs to 1.9.8 version as mentioned in #53

I downgraded to phantomjs 1.9.8 but it still does not work on Mac OS 10.11.5.

Removing the folder node_modules and install again did the trick for me.

Downgraded to 1.9.8 and no luck

Check your version of node.  It looks like DynamicScraper doesn't work with newer node versions.  node 7.9 didn't work for me, but 4.8.2 worked fine.
I'm building a docker image to encapsulate the correct version of node/phantom/scraperjs, as it appears there's a pretty specific set of versions that are required to make this all work.
This Dockerfile worked for me:
FROM node:4.8

WORKDIR /scraperjs
RUN npm install scraperjs
RUN npm install -g<EMAIL_ADDRESS>ENV NODE_PATH=/scraperjs/node_modules

then:
# assumes dynamic HN example is in 'hn.js'
$ sudo docker build -t coopernurse/scraperjs .
$ sudo docker run -it -v `pwd`:/code coopernurse/scraperjs node /code/hn.js


Changes cursor animations to start in default state to fix #10922.

Fixes #10922

Hi @sprinkle131313, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
We will now validate the agreement and then real humans will evaluate your PR.
TTYL, MSBOT;

@sprinkle131313 can you please make two PRs out of this since the touch two completely different areas of the code.


add image field to cloudshell crd

Signed-off-by: calvin0327<EMAIL_ADDRESS>/kind feature
fixed: https://github.com/cloudtty/cloudtty/issues/124

add image field to cloudshell crd
Optimized cloudshell ready time

can you please update doc as well ? @calvin0327

can you please update doc as well ? @calvin0327

ok, we can release a v0.3.1 version after updating doc.


Not accommodating for two/three double finishes

Currently I check for a double finish, then up to two trebles, completely overlooked an all double throw finish.

Completely re-written the logic behind checkout, needs massive optimisation now :)


[PE-D][Tester D] Undo feature does not support addition and deletion of tags

The limitation in the user guide that the undo and redo functionalities only support commands such as add, delete, edit, and clear appears counterintuitive, especially when considering the impact of adding and deleting tags on user inputs and the ability to add a person.
As users are required to have tags available in the tags list before creating a person entry, accidental tag additions or deletions can disrupt the seamless input flow for creating new entries.
Moreover, offering undo and redo for tag operations not only streamlines tag management, ensuring efficiency, but also prevents user frustration by allowing for quick correction of errors, ultimately creating a more user-friendly and consistent experience overall.

Labels: type.FeatureFlaw severity.High
original: NeoHW/ped#23

I would highly suggest the tag list be removed.

It makes other operations unnecessarily complex. I don't know why the input tag must be in the tag list to be valid when you can add whatever tag you like into the tag list without any constraints. For example, in many bug reports, when testers want to add a person, they try the + first, then see the tag not in the list error, and then they need to add the tag, finally they can add the person, which is quite annoying and not user-friendly.
There isn't any command to display the whole list of the tagList. users cannot see what tags are now available in the list. This is really confusing, and users cannot manage the tag list effectively.
Most importantly, the presence of tagList also triggers the bugs of other operations. For example, when many testers delete a person from the sample data and want to redo that, it doesn't work because the sample person has a tag that is not in the tag list, so this person cannot be added back to the list.
tag+ and tag- cannot be redone just like add and delete, which is quite counterintuitive. And this feature flaw cannot be fixed in v1.4.

Overall, currently, the tag list and related tag+ tag- operations don't bring any benefits, but introduce a lot of drawbacks. Whether it is for the benefit of the whole group or for individual interests, I believe the tag list should be deleted.


Embedded Files in PDF not working - kind of !?

Hello Guys!
Thank you for this great project and Community, as already discussed today in the IRC-Chat we are having a hard time reading Embedded Files from a PDF [6].
The topic is not an easy one but some guys [1] have already explained and done the ground work for a discussion about this.
Here is how it it can be reproduced:
Working Case:
Open up the PDF-JS Viewer [3] with the file [2] mentioned in the article [1], click the attachments tab and download the embedded file. Great it works!
No so working case:
Create an empty PDF and add an attachment to it [4] or use this test file [5], open up the PDF-JS Viewer [3] with one of the mentioned files and click on the attachments tab, it does not work.
Why?
We think that there are more ways how to embed files into a pdf since newer versions of pdf acrobat readers appeared and the other ways have most probably not been implemented yet. Therefore a file embedded with Acrobat Reader higher version - like 11, will be not found and not displayed by pdf.js at all.
1: http://openpreservation.org/blog/2013/01/09/what-do-we-mean-embedded-files-pdf/
2: http://opf-labs.org/format-corpus/pdfCabinetOfHorrors/fileAttachment.pdf
3: http://mozilla.github.io/pdf.js/web/viewer.html
4: http://help.adobe.com/en_US/acrobat/X/standard/using/WS58a04a822e3e50102bd615109794195ff-7e4e.w.html
5: https://onedrive.live.com/view.aspx?resid=A2E6EDB5D81A9B36!7890&ithint=file%2Cpdf&app=WordPdf&authkey=!AKx_9e-1AJjlAEE
6: http://blogs.adobe.com/insidepdf/2010/11/pdf-file-attachments.html

We have uploaded the not working attachments here:
https://onedrive.live.com/view.aspx?resid=A2E6EDB5D81A9B36!7890&ithint=file%2Cpdf&app=WordPdf&authkey=!AKx_9e-1AJjlAEE
Please let us know your thoughts!

Maybe the PDF must be linearized before trying to read it: https://gist.github.com/hubgit/6078384#qpdf

The reason for this issue is that the attachments are added as FileAttachment annotations, which are not supported by PDF.js yet. Previously this was not clear, but with the refactored annotation code this is now visible in the console:
Warning: Unimplemented annotation type "FileAttachment", falling back to base annotation


Mod Manager doesn't remember it's own window position

BG3MM always opens on the 'main' monitor, rather than the second monitor where I've dragged the window in order to use it. I'd like to be able to keep it on the screen I've moved it to, rather than have to alt-tab out of the game to snatch the window and drag it back to where it belongs.
Honestly not sure if being able to stay where I put it is intended, and thus this is a bug, or simply a feature that isn't available currently. Thought I'd mention it either way.

Yes, this is annoying. It also always opened too small and I have to resize it everytime.


MNT: Update to pylint 1.8.1 and re-rendered with conda-smithy 2.4.4

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

Thanks @timleslie. Any interest in helping maintain?

@jakirkham Happy to help out where possible, sure!

In that case, please feel free to add your GitHub handle to the recipe-maintainers list in meta.yaml.

Also we may want to switch this over to a noarch: python package.

Have added myself to the maintainers. I don't think we can go to noarch yet, as we have some python 2.7 specific dependancies (backports.functools_lru_cache, configparser, singledispatch).

Thanks. Good point.

Thanks @timleslie. Should get an invite to join conda-forge momentarily, which will provide merge permissions on this feedstock.


ViewHelper test class should be better tested

hex.view.viewhelper.ViewHelper unit tests are very basic. They should be extended to cover the whole internal event flow.
This class should be updated.

This issue was moved to DoclerLabs/hexMachina#56


Merge Stereotactic Modules into Stereotaxia

The initial attempt to combine the projects, see link . As suggested by @lassoan, we now merge our modules into this repository.
After additional iterations, certain modules will vanish or become submodules of others. The desired outcome is to have three modules: Sterotaxia_old, Stereotaxia (the merge), and Stereotactic.
We still hope that in the future we can move this repository to a group where everyone has access to it, and all contributors have the same rights.

@JBeninca @pieper @lassoan @jcfr could somebody please accept this merge?


Add French Language

Hello,
Add French README,
Thank you,

@esau-morais please review it

If the French language not be changed until 1 week, @sabesansathananthan, you can close this PR.
Note: One choice is review and make the changes, if @Sheitak not

@Sheitak Could you please consider the suggestions?

@Sheitak Could you please consider the suggestions?

Probably he didn't see the review and is not so connected. I think it's necessary to close or solve by our own

@Sheitak Could you please consider the suggestions?

Probably he didn't see the review and is not so connected to GitHub. I think it's good to close or solve by our own

Maybe he has some work so he couldn't open GitHub as well. shall we wait for a week? shall we close this on 14th Oct if @Sheitak didn't make changes?

@Sheitak Could you please consider the suggestions?

Probably he didn't see the review and is not so connected to GitHub. I think it's good to close or solve by our own

Maybe he has some work so he couldn't open GitHub as well. shall we wait for a week? shall we close this on 14th Oct if @Sheitak didn't make changes?

Yes, sure

Hello gentlemen, excuse me I had an exam recently! I'm sorry for the delay, I'll take care of this right away @esau-morais @sabesansathananthan

Please fill the PR form and Edit Main README and remove the word upcoming in French

Hello gentlemen, excuse me I had an exam recently! I'm sorry for the delay, I'll take care of this right away @esau-morais @sabesansathananthan

Good luck with your exams. <3

Thank you for your PR... <3


lb: add probe for helper that invalidates hash

This pull request is now managed with CodeReviewHub. Refresh.


see animation when page on scroll

Hello to all
I wanna be when the animated scroll page is displayed.
How do I do this?

explain in more detail what you want please

Hi @abas619, you can reveal animation when you scroll with the help of wow.js. A friend of animate.css!
For video tutorial please watch this video...
https://www.youtube.com/watch?v=bd_jHBk8Kzw
You can also visit the repo for more info...
https://github.com/matthieua/WOW
Please let me know if you have any questions about animate.css :) cheers!

Hi @abas619,
You have many options that you can opt to choose, @WarenGonzaga mentioned wow.js which is pretty good. You can choose scrollreveal.js which is quite good for revealing animations but doesn't work quite well with animte.css. In my opinion your best bet is to use scrollmagic, in combination with GSAP and animate.css and you'll end up with something pretty amazing.
GSAP course on Youtube,
[GSAP Youtube]https://www.youtube.com/watch?v=_42HpXlGpfk&list=PLkEZWD8wbltlSS_d_7tx_H_FBNVro8918)
Scrollmagic course on Youtube,
ScrollMagic Youtbe
Here is Pen for reference,
CodePen proof of concept

@SakhirAtwi agree with you... since this is animate.css repository lets keep the topic to animate.css solutions only. GSAP is js based animations (I am also a contributor on GSAP and enthusiast.) it has some advantage and disadvantage. For @abas619 you have to choose one between animate.css or gsap because they can't be used in one project because of some css rendering issues which we have discussed over gsap forum. That's why I create a plugin for GSAP to mimic our favorite animation from animate.css please check the link below.
greensock.com/forums/topic/15115-animatecssplugin-is-now-open
For everyone, even @daneden we should recommend solutions for animate.css only since we are on the official repo of animate.css if animate.css cant achieve what you want to achieve then make a suggestion instead. Alright.

@WarenGonzaga agree with you totally, I have experimented with the combo of animate.css + GSAP + scrollmagic as in the pen I linked in the comment above, and honestly it was the complete disaster coz it creates some sort of glitch in your animation (Don't know why). If you are using scrollmagic then you should always always use javascript animations, i.e GSAP or velocity.js, using animate.css is absolute nightmare.
But!
the problem is some sort of flexibility should in fact be created in animate.css that so it can be used with scrollmagic or scrollreveal, right now you can use it purely with HTML5, but this practice hinders control from the developer for JS side.
Cheers, Happy coding :)

Thanks My Friend @SakhirAtwi
Sent from Mail for Windows 10
From: SakhirAtwi
Sent: جمعه, 12 مرداد 1397 08:13 ب.ظ
To: daneden/animate.css
Cc: abas dolati; Mention
Subject: Re: [daneden/animate.css] see animation when page on scroll (#848)
Hi @abas619,
You have many options that you can opt to choose, @WarenGonzaga mentioned wow.js which is pretty good. You can choose scrollreveal.js which is quite good for revealing animations but doesn't work quite well with animte.css. In my opinion your best bet is to use scrollmagic, in combination with GSAP and animate.css and you'll end up with something pretty amazing.
GSAP course on Youtube,
[GSAP Youtube]https://www.youtube.com/watch?v=_42HpXlGpfk&list=PLkEZWD8wbltlSS_d_7tx_H_FBNVro8918)
Scrollmagic course on Youtube,
ScrollMagic Youtbe
Here is Pen for reference,
CodePen proof of concept
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

So this issue should solve now :) @daneden or @eltonmesquita please close this :) thanks!


Added AWS SNS Notification API

Description of your changes

Fixes #175
- Added SNS Topic CRUD methods + tests
- Added SNS Subscription CRUD methods + tests

Checklist

I have:

[x] Run make reviewable to ensure this PR is ready for review.
[x] Ensured this PR contains a neat, self documenting set of commits.
[ ] Updated any relevant documentation, examples, or release notes.
[ ] Updated the dependencies in app.yaml to include any new role permissions.

TODO:
- fix CI Build Issue
- fix Cyclometric Complexity a Observe func SNSSubscription (make reviewable)
- Add resource in app.yaml

FORCED PUSHED ON THIS BRANCH WITHOUT ANY CHANGES
Had some issues with rebasing.

@negz I have made all the appropriate changes.

@rahulchheda It looks like there's an in-progress conflict resolution checked into this PR. Please work with @sahil-lakhwani to get this PR to a point where he's satisfied with it, then let me know when it is ready for me to review again.

@rahulchheda It looks like there's an in-progress conflict resolution checked into this PR. Please work with @sahil-lakhwani to get this PR to a point where he's satisfied with it, then let me know when it is ready for me to review again.

@negz  -  @rahulchheda has addressed all the changes that I could request.

Thanks @rahulchheda and @sahil-lakhwani!

Hi @rahulchheda,
Apologies if I wasn't explicit with my last review pass, but I'm waiting on you to address my last round of review feedback. Please comment on this PR once you've addressed the feedback and are waiting on another review.

Got it, will make it reviewable ASAP, I think I missed those comments

Apologies @negz for delaying this PR Review. I have tried to resolve most of your comments, added comments on a few. Let me if some improvement needed.


[Proposal] UI implementation guideline for a11y

Idea Description
Currently bunch of UI missing a11y supporting, It's not suitable situation for the handicapped attendees as you know.
From this situation, kind of guideline for a11y implementation to keep a11y supporting quality over the contributors.
For expand the knowledge of a11y (for Android developers industry as well 😃 ), it's nice to have kind of those document.
Proposal solution

Make guideline at Readme.md or reuse the Google's document
Add section at CONTRIBUTING.md
(nice to have) Enable automation tests to checking on each PR

For Item1, This page(https://developer.android.com/guide/topics/ui/accessibility) will be basis of discussion for document.
For Item3, We can refer the document
Discussion points

Contributor's cost/ too much requirements
Reuse Google's material or in-house documentation for the issue.

Reference images and links

Thanks for your proposal!

Make guidelines in Readme.md or reuse Google's document

Add a section to CONTRIBUTING.md

(nice to have) Enable automation tests to check on each PR

Linking to Google's document instead of copying it might be a good idea, as it will always be up-to-date. However, in that case, it might not be viewed as often. Probably, dealing with the document might be challenging, so I'd like to consider option 3.

For the code, I'd prefer to gather it in a place other than CONTRIBUTING.md.

Regarding 3, Roborazzi's functionality to visualize accessibility status and take screenshots of it might be helpful. It allows us to develop with constant awareness of accessibility. https://github.com/DroidKaigi/conference-app-2023/issues/444

I feel like there's nothing we can do, so let me close this. If there's anything you want to do, please feel free to reach out to me!


packup.json or packup.ts for config

I suugesse to add possiblity to read config from packup.json or something similar as option

what do you want to configure?

staiticFilesPath indicate where assests will be loaded from ( you can give it assests as default value )
staticFilesHost indicate the host for serving static file in production
mediaFilesPath indicate where images and audio will be content the users can add dynamicly
mediaFilesHost indicate the host for media in production it can be aws or something else
I insipirate this suggestion fron Django settings


[BUG] Unexpected "Failed" volume workload pod status on k8s v1.27

Describe the bug (🐛 if you encounter this issue)
In a v1.27.1+k3s1 cluster, create a volume with pv/pvc, and create a pod to use this volume, then delete the pod, the volume workload pod status becomes "Failed"
To Reproduce
Steps to reproduce the behavior:

Create a v1.27.1+k3s1 cluster, and install Longhorn v1.5.x-head or master-head
Create volume test-1 from Longhorn UI
Create PV/PVC for this volume from Longhorn UI
Create a pod to use this volume:

# pod.yaml
apiVersion: v1
kind: Pod
metadata:
  name: test-pod-1
spec:
  containers:
    - name: sleep
      image: busybox
      imagePullPolicy: IfNotPresent
      args: ["/bin/sh", "-c", "while true;do date;sleep 5; done"]
      volumeMounts:
        - name: pod-data
          mountPath: /data
  volumes:
    - name: pod-data
      persistentVolumeClaim:
        claimName: test-1

$ kubectl apply -f pod.yaml

Wait the pod running, and check volume status:

$ kubectl get volume test-1 -n longhorn-system -o yaml
  kubernetesStatus:
    workloadsStatus:
    - podName: test-pod-1
      podStatus: Running
      workloadName: ""
      workloadType: ""

delete the pod:

$ kubectl delete -f pod.yaml

The volume workload pod status becomes Failed

$ kubectl get volume test-1 -n longhorn-system -o yaml
  kubernetesStatus:
    workloadsStatus:
    - podName: test-pod-1
      podStatus: Failed
      workloadName: ""
      workloadType: ""

Expected behavior
A clear and concise description of what you expected to happen.
Log or Support bundle
If applicable, add the Longhorn managers' log or support bundle when the issue happens.
You can generate a Support Bundle using the link at the footer of the Longhorn UI.
Environment

Longhorn version: v1.5.x-head, master-head
Installation method (e.g. Rancher Catalog App/Helm/Kubectl):
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: v1.27.1+k3s1

Number of management node in the cluster:
Number of worker node in the cluster:

Node config

OS type and version:
CPU per node:
Memory per node:
Disk type(e.g. SSD/NVMe):
Network bandwidth between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:

Additional context
v1.25.3+k3s1 doesn't have this issue.

Probably related to https://github.com/kubernetes/kubernetes/issues/118472

Since 1.27 (https://github.com/kubernetes/kubernetes/pull/115331) a deleted pod is transitioned to terminal phase (either Succeeded or Failed).

Yeah, the pod terminates with phase equal Failed:
   containerStatuses:
   ...
     state:
       terminated:
         exitCode: 137
         reason: Error
         ...
   phase: Failed

I assume the podStatus: Failed just reflects that. This is WAI since 1.27: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase:
Since Kubernetes 1.27, the kubelet transitions deleted pods, except for [static pods](https://kubernetes.io/docs/tasks/configure-pod-container/static-pod/) and [force-deleted pods](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced) without a finalizer, to a terminal phase (Failed or Succeeded depending on the exit statuses of the pod containers) before their deletion from the API server.

@mimowo
Thanks for the information.
But, why does the simple kubectl delete -f pod.yaml operation bring the phase to a Failed state? Is there possible cause?

Yeah, the pod terminates with phase equal Failed:
   containerStatuses:
   ...
     state:
       terminated:
         exitCode: 137
         reason: Error
         ...
   phase: Failed

I assume the podStatus: Failed just reflects that. This is WAI since 1.27: https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-phase:
Since Kubernetes 1.27, the kubelet transitions deleted pods, except for [static pods](https://kubernetes.io/docs/tasks/configure-pod-container/static-pod/) and [force-deleted pods](https://kubernetes.io/docs/concepts/workloads/pods/pod-lifecycle/#pod-termination-forced) without a finalizer, to a terminal phase (Failed or Succeeded depending on the exit statuses of the pod containers) before their deletion from the API server.

@mimowo Thanks for the information. But, why does the simple kubectl delete -f pod.yaml operation bring the phase to a Failed state? Is there possible cause?

Answer to my question: https://stackoverflow.com/questions/59729917/kubernetes-pods-terminated-exit-code-137

Graceful pod deletion issues SIGTERM, followed by SIGKILL after ~30s. This pod gets terminated by SIGKILL, thus the exit code 137. If you want the container to complete with success you need to intercept the SIGTERM and exit with 0.

Graceful pod deletion issues SIGTERM, followed by SIGKILL after 30s (by default). This pod gets terminated by SIGKILL, thus the exit code 137. If you want the container to complete with success you need to intercept the SIGTERM and exit with 0.

Got it. Thank you.

@derekbit It would be appreciated that you can help to refine test_kubernetes_status and test_backup_kubernetes_status regarding the change described in this ticket to let them pass?
Of course I can remove all the 'podStatus': 'Running' checking in these test cases, but I'm not sure if we really expect podStatus to be Running in some scenarios. Many Thanks!

@derekbit It would be appreciated that you can help to refine test_kubernetes_status and test_backup_kubernetes_status regarding the change described in this ticket to let them pass?
Of course I can remove all the 'podStatus': 'Running' checking in these test cases, but I'm not sure if we really expect podStatus to be Running in some scenarios. Many Thanks!

Sure. Can you remove the check temporarily? I will revise the test cases later.


How to compute LRF?

Hi,
can you provide detailed instructions for computing LRFs by FLARE in PCL?
Thanks.

Hi @yokinglou,
You can fetch https://github.com/tolgabirdal/qecnetworks/pull/7 for computing LRFs.

merged :)

I see. Thanks :)


ENV variables are not loaded at runtime

Describe the bug
ENV variables are not loaded at runtime. Old env variables are getting assigned in components and works if console logs are added.
To Reproduce
Steps to reproduce the behavior:

Added module in babel.config.js

module.exports = {
  presets: ['module:metro-react-native-babel-preset'],
  plugins: [
    ["module:react-native-dotenv"]
  ]
};

Added .env file in root directory with following values, Allowed THEME values -->theme1/theme2 DEFAULT_MODE=yes/no

THEME="theme1"
DEFAULT_MODE="yes"

Importing and using the env variables

import {THEME, DEFAULT_MODE} from "@env";
const AuthStack = createStackNavigator({
  Welcome: {
    screen: Welcome,
    navigationOptions: {
      title: 'APP NAME',
      headerShown: DEFAULT_MODE == "yes" ? true : false,
    }
  }})

Scripts updated in package.json
"cc": "rimraf node_modules/.cache/babel-loader/*,", "android": "npm run cc && react-native run-android",

Expected behavior
Above code should work after changing THEME="theme2" & DEFAULT_MODE="no" and rebuilding app using npm run android and headerShown value should be false
** Error**
Above code still points to DEFAULT_MODE="yes" and works i.e. headerShown value updates to false only if there is console statement after import in every file. i.e
import {THEME, DEFAULT_MODE} from "@env"; console.log("THEME CHECK",THEME, DEFAULT_MODE);
React native version used:
"react": "16.13.1",
"react-native": "0.63.3",

My guess is that babel recompiles the file when you make the change of adding the console.log . I don't know why but I advise you try to invalidate the cache in your babel config https://github.com/goatandsheep/react-native-dotenv-metro-demo/blob/c0daeebe35a87c524eb88803e19f445d6d6956d4/babel.config.js#L2

has anyone figured out a more elegant solution to this?

I'm working on using a new Babel feature that came out this year but it has not been widely used so documentation has been challenging to follow. Fix should be in next release, tracked in #75

I just solved the issue, need to run yarn start --reset-cache, then it runs like a dream

Hi @Ryanjso this ticket is closed because I haven't been able to reproduce it since recent changes. Make sure your Babel version is up to date or if you're using Expo that you're using the latest version of that or if you're using something else that is forcing the version of Babel down that you use package resolutions


[regression]Remove of mapping is not refreshing UI immediately for the blue link

versions standalone 1.40.0 on Chrome and Firefox

create two mapping

click on the top right icon of the third column to delete the mapping
Click remove in the popup

--> there is still a blue link connection

when clicking in another place the blue link is removed

This is fixed by https://github.com/atlasmap/atlasmap/commit/5c1da4539a258c712afd4c86671df8f6db4465e5


backtrace name collision

https://travis-ci.com/rust-lang-nursery/error-chain/jobs/240939141#L293
error: a method with this name may be added to the standard library in the future
--> src/lib.rs:657:41
|

657 |         if let Some(backtrace) = self.0.backtrace() {
|                                         ^^^^^^^^^

|

= note: `-D unstable-name-collisions` implied by `-D warnings`

= warning: once this method is added to the standard library, the ambiguity may cause an error or change in behavior!

= note: for more information, see issue #48919 <https://github.com/rust-lang/rust/issues/48919>

= help: call with fully qualified syntax `ChainedError::backtrace(...)` to keep using the current method

= help: add `#![feature(backtrace)]` to the crate attributes to enable `std::error::Error::backtrace`

This should be fixed by https://github.com/rust-lang-nursery/error-chain/pull/279


Deployment

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

Pre-work Study Guide has been completed and deployed at [https://chasejlaw.github.io/prework-study-guide/]


[wip] Change CommandExecutor SPI

This PR changes CommandExecutor SPI that are used by command based operators like py, rb and sh. The goal of this PR is that those operators could be executed on different instances from those tasks are executed by OperatorManager. The current SPI was designed supposing that a command task and the operator are executed on same instance. But, basically we don't need to suppose that.

I closed this PR to make cleanup. Will open another for this.


Out of tree BSP

Zephyr shall support out-of-tree BSPs (Board definition packages) with BSPs including board, soc, driver definitions and code. A BSP shall be able to have its own configuration system that integrates with the overall Zephyr configuration system.
The following shall be supported with out-of-tree feature:

Independent applications and BSP repositories
Ability to build applications by referencing both Zephyr and BSP
Sanitycheck can run Zephyr tests on BSP
Sanitycheck can test out-of-tree applications.

We already have out of tree board support, but that is done right now within an application and only supports boards. We should have the same thing for SoCs and drivers and should be able to build multiple application using this out-of-tree BSP.

Perquisite of this is 34438

Having also support for out of tree archs would be very welcome for us.

Having also support for out of tree archs would be very welcome for us.
(even if it would be limited to build, without sanitycheck support)

you need to open a new feature item for that. This is only for BSP

you need to open a new feature item for that. This is only for BSP

It is already done :)


State operator[] can be a const method

Closes #163

Resolves history issues with #163

@jeremyong any chance of getting this merged?

Thanks!


Auto copy member to developer library

Since we now have the comparison features in the extension, I am wondering if we should add some new functionality that

When they click on a member, it checks to see if they have a 'developer library' defined
It prompts the user if they'd first like to copy the member to their develop library and edit from there instead
If they say no, they will edit the source as normal. If they say yes, it will copy the source into their developer library (into the same source file name, member, and extension) and they would work on their changes there.
When they are done, there will be a new mention option that allows them to compare their changes with what's in the library the source came from. If they are happy with their changes, they can run another command to copy their changes back to the original member.

It would be configurable. You would have to enable this feature and define a developer library

Mostly looking for ideas on this. I think it sounds like a good idea, but is it really?

Technically, they can do this already manually.

Copy the member to another library
Make changes in the other library
Compare the two files
Copy the file back to the original library.


#709 fixes some problems in ItemVirtualizerSimple for generating item…

fixes some problems in ItemVirtualizerSimple for generating items when not in visual tree
fixes #709 like issues in my app

Progress report: still trying to find a repro as described in #725. Don't want to commit a fix until we have unit tests that demonstrate the problem.

I'm going to close this. If someone finds a repro, we can re-open this and update it.


fix: specify x|std

I think the probrem caused by ambigous regex.
So specify x|std.
fix #22

I checed renvoate's logs.
It failed to update bacause of v is not included.
So, I fix capture to include it.


release 0.13.4

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 95.61%. Comparing base (45d8db0) to head (73a815f).

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #133   +/-   ##
=======================================
  Coverage   95.61%   95.61%
=======================================
  Files          61       61
  Lines        5107     5107
=======================================
  Hits         4883     4883
  Misses        224      224

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Docker and domains

Using morbier and previously camembert with docker (just starting to using, not on production yet), I found working with domains to be complex and difficult.
First traefik.domain label seems not to work, and even if it work in future, I can't set it on the fly because labels on dockers are immutable.
Then I decided to use container names as domains, seems to works for subdomains, but if I set docker.domain to empty string in the traefik.toml it append dot at the end so this is not an option too.
For docker containers, you could set domain and hostname as network options but this is not respected from traefik (sadly but true)
Then I'v tried to  setup manual rules from file and point frontend to already done backend from dockers (I mean backend-CONTAINER_NAME) which seems to not working too.
So what I found is the only working for me way.
Creating backend that point url to automatic docker generated (CONTAINER_NAME.DOCKER_DOMAIN) and create and associate frontend with this backend, and the only plus of having docker configured is that have automatic urls, nothing more.
May be the problem is on me as not understanding the tool very well, documentation didn't help a lot (may be I am missing something).
So could you point me where I am wrong? And may be implement in next versions mechanism of easy domain mapping and multiple domain (aliasing) assignment.
Don't let me wrong, this peace of software seems to be really helpful.

It would help you could share your traefik container commands arguments plus your container argument.
Cheers!

These are my toml files
rules.toml.txt
traefik.toml.txt
But reading what I already write, may be I should open new issues about the ideas that have.

I'll close the issue due to inactivity but feel free to re-open if needed.


Mention the Slack usergroup "cert-manager-maintainers"

ref: https://github.com/kubernetes/community/issues/7360, https://github.com/kubernetes/community/pull/7368

@maelvls this looks good to merge to me - is further work needed?

Thanks for reminding me of this PR. I think I was waiting for https://github.com/kubernetes/community/issues/7360 and https://github.com/kubernetes/community/pull/7368 to be done before labelling this PR as ready. Now that they are merged, let's merge this PR!


Fix file open with append_existing flag on posix

fixes #2011

@vinniefalco pls check that this was the intent.

Dammit, how did that get in there?
On Tue, 21 Jul 2020 at 17:54, Vinnie Falco<EMAIL_ADDRESS>wrote:

@vinniefalco commented on this pull request.
In test/beast/core/CMakeLists.txt
https://github.com/boostorg/beast/pull/2027#discussion_r458206565:

@@ -72,3 +72,11 @@ target_link_libraries(tests-beast-core
)

set_property(TARGET tests-beast-core PROPERTY FOLDER "tests")
+
+add_executable(_2011 2011.cpp)
umm... we're adding a whole executable just to test this issue?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/boostorg/beast/pull/2027#pullrequestreview-452600295,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABHOZSLGSWXCL27XQFCEVH3R4W24TANCNFSM4PDXKTRQ
.

--
Richard Hodges
<EMAIL_ADDRESS>office: +442032898513
home: +376841522
mobile: +376380212


[create] CLI scaffolding step

In the open-wc-cli when you want to create a new application with rollup there is an additional step that ask you for scaffolding files:

If I remembered correctly this had some sense because you could select between rollup or webpack but now maybe can be deleted directly cause we only have the rollup option.

For storybook and testing they make sense because they add example tests and stories. I'm not sure what this does for building.
We used to generate a lot more files in the init, but now it's pretty minimal. Maybe we can skip this now? And if you're upgrading a project, we just don't generate example files?

This looks like it would scaffold the Rollup config: https://github.com/open-wc/open-wc/blob/master/packages/create/src/generators/building-rollup/templates/static/rollup.config.js which I think is a requirement to actually build with Rollup. It seems like we could force the creation of this file, but beyond that, I'm not sure how we'd be able to remove this step in the CLI. Thoughts?

From what I could check there is no difference between selecting or not that option:

This is the output that I got not selecting and selecting the option Building (rollup) in that step respectively and it's the same. Furthermore the rollup.config.js is always generated too maybe because is being added in previous steps like?:


Support mpv by allowing it to remove --x11-netwm=yes option.

Problem Description
Cuirrently, to get proper fullscreen support for mpv in XMonad, I have to pass --x11-netwm=yes to mpv.
Otherwise, mpv window becomes larger than the screen by border widths in fullscreen mode.
man mpv complains about XMonad for breaking X.
Perhaps, xmonad should fix this?

#109

Oh, I'm closing it. It seems it is a duplicate of that issue.


[PE-D][Tester E] addp command does not work for contacts with the same name but different details

From the default contacts, the first contact has the name Alex Yeoh, when trying to addp a new contact with the exact same name but different details, it is not allowed even thought they are technically different people.

Labels: type.FunctionalityBug severity.Medium
original: turretDive/ped#5

Closed this issue as it is duplicated with issue #218.


simplified 'with-docker' installation process

fairly self-explanatory, but the signalserver installation process can be tricky for the inexperienced. If there was any way to package the processes (frontend.sh and quickstart.sh), or resolve the cleanup issues internally, I think it would be a great for a lot of us loser users.

I got this - I actually spent quite a bit of time already on it a few months ago - table of contents and everything -  but then had some drama with a pull request and ended up deleting it.

Can this be scoped into #250? Closing this more granular issue since we are doing a larger refactoring of docs generally.


fs_1.default.readFileSync is not a function

I installed the package in my codebase. I am using React Gatsby. I get error "fs_1.default.readFileSync is not a function"
"global-tld-list": "^1.16.74"

Hi @shareef-dweikat, do you still get the error?

I am getting this very similar error in the latest version:


CMakeLists.txt should use ${Boost_SYSTEM_LIBRARY}

cpp-netlib / libs / network / src / CMakeLists.txt
uses
target_link_libraries(cppnetlib-client-connections ${Boost_System_LIBRARY})
which fails at least on OSX, maybe other case-sensitive OSs?  Should be
target_link_libraries(cppnetlib-client-connections ${Boost_SYSTEM_LIBRARY})

I've encountered the same problem: https://github.com/cpp-netlib/cpp-netlib/blob/0.11-devel/libs/network/src/CMakeLists.txt#L48.
I'm using Debian 7 amd64 system, cmake 3.0, boost 1.57.0.
And at least in cmake 3.x the found library names are uppercased, e.g. ${Boost_SYSTEM_LIBRARY}. https://github.com/Kitware/CMake/blob/master/Modules/FindBoost.cmake#L988-989
I will make pull request later on today :)

I see you've fixed this now, thanks @povilasb!


tests: stabilize integration cases about prevote

Signed-off-by: qupeng<EMAIL_ADDRESS>What have you changed?
Stabilize integration cases about prevote.
In best situation, the case needs 2s to receive an expected pre-vote message:

500ms to trigger the first check quorum;
500ms to trigger the second check quorum, and the leader steps down;
[500ms, 1000ms) to start a new election.

On CI it could be much more slow, so 5s could be not enough.
This PR changes base tick interval to 20ms, and election timeout to 200ms.
What is the type of the changes?
Engineering
How is the PR tested?
Unit test
Does this PR affect documentation (docs) or should it be mentioned in the release notes?
No
Does this PR affect tidb-ansible?
No
Refer to a related PR or issue link (optional)
Benchmark result if necessary (optional)
Any examples? (optional)

/run-all-tests

/run-all-tests

@hicqu
CI still failed...

/run-all-tests

/run-all-tests

/run-all-tests


added 3d rotating card project

This pull request implements a 3D rotating card animation feature showcasing cityscape images. The cards smoothly rotate along the diagonal axis, providing an interactive and engaging visual experience for users. Each card rotates in a dynamic way, offering a modern, visually appealing effect.
Changes include:
Added 3D rotation animation using CSS transforms.
Incorporated three cityscape images displayed on rotating cards.
Fine-tuned rotation speed and perspective for a smooth user experience.
This update adds an interactive design element that enhances user engagement with a striking 3D effect, improving the overall look and feel of the project. It’s a visually stimulating feature that will capture the attention of users and make the interface more dynamic and immersive.
Looking forward to your feedback and further improvements!

Remember to add hactoberfest guideline tags and labels only then i am able to contribute and this contribution shown in my hactoberfest 2024. thankyou

@abhishekrajput-web Please move this folder into frontend module.

@indrakishore , i have move this folder to frontend module. thankyou


Overriding feature detection

We're currently building a page for deployment to a browser version that has a quirk in its FileReader API that results in errors when using the fetch polyfill, but in a way that means it passes the feature detection for blob support. Obviously this is such a specific problem that it wouldn't be sensible to change the feature detection in the upstream polyfill to take it into account, but ideally we'd like to avoid maintaining a fork just to tweak the feature detection.
Would it be reasonable to add some kind of mechanism for overriding the feature support for this use case? Happy to put in a PR with a candidate implementation if so.

yes, happy to accept a pr for this

hi


Add directory support for FileTrigger

Provide a general summary of the feature here
Upload selecting directories when using FileTrigger.
🤔 Expected Behavior?
Add support for <FileTrigger directory> to allow selecting directories.
😯 Current Behavior
Not supported
💁 Possible Solution
Although the property is called webkitdirectory and not directory, it is supported by Chrome, Firefox, Edge 14+, and Safari 11.1+.
https://caniuse.com/?search=webkitdirectory
Could prefix with UNSAFE_.
<FileTrigger UNSAFE_directory>

🔦 Context
This allows nested folders to be supported.
💻 Examples
No response
🧢 Your Company/Team
No response
🕷 Tracking Issue
No response

Seems like a reasonable request, although I noticed webkitdirectory isn't even in the React types for input, so I think we would need to ts-ignore it. I tried locally and it passed the directory contents as the FileList in onChange, as expected.


 at  level not applied to

I want to be able to apply group filtering to multiple suite files.
Use Case - Let's say, I have multiple test suites defining all the tests.  (I may want to do this for more environments in future). I am trying to achieve this by creating a suite file for every environment and invoking the one depending on the execution environment.
E.g. file dev-env-suite.xml -
<suite name="Dev environment">
    <groups>
        <run>
            <include name="dev" />
        </run>
    </groups>
    <suite-files>
        <suite-file path="suiteA.xml"></suite-file>
        <suite-file path="suiteB.xml"></suite-file>
    </suite-files>
</suite>

But the  filtering does not seem to get applied to tests within the . Is this by design and intentional?

Dupliate of #589

Is there an update for this issue. We do also have the problem with this, and would be very happy it worked.

@juherr Any thoughts on this?

@cbeust No, I didn't have a look yet.

Oh, thank you for your reply! Hope you'll implement this feature soon!
On Mon, Dec 28, 2015 at 6:40 PM, Julien Herr<EMAIL_ADDRESS>wrote:

@cbeust https://github.com/cbeust No, I didn't have a look yet.
—
Reply to this email directly or view it on GitHub
https://github.com/cbeust/testng/issues/689#issuecomment-167600852.