Move hipster shop to 80/443

Is your feature request related to a problem? Please describe.
In the Splunk Show environment, the hipster online boutique is exposed on port 81. For example, http://splunkawssacramento-i-0b719386050b2ff12.splunk.show:81/
While exposing the service on port 81 will work fine in many cases, there are customer networks where this is considered a non-standard, non-permitted egress port. We hit this issue in a workshop yesterday.
Describe the solution you'd like
Expose the boutique with a friendly DNS name on 80 + 443.
Describe alternatives you've considered
To address the issue during the workshop, I had to build an nginx reverse proxy using standard 80/443 ports in my own cloud provider account. I had students use my personal reverse proxy instead.
Later, I stood up a CDN endpoint on Fastly to do the same thing. This had the benefit of being available with a DNS name I could give out to epople.
Additional context
Having to scramble and troubleshoot this was unfortunately a setback for us during the workshop. While I understand this issue may not arise everywhere, it is better for us to assume customer networks will be restrictive. Let's design the workshop infrastructure to be as standard as possible when it comes to network access.
Thanks.

The following ingress has been added to the deployment.yaml
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: frontend
  annotations:
spec:
  ingressClassName: traefik
  rules:
  - http:
      paths:
      - path: /
        pathType: Prefix
        backend:
          service:
            name: frontend
            port:
              number: 80

This will expose the Boutique on ports 80 and 443 (untrusted cert. over 443).
Will look into replicating this across the Ninja workshop series in the near future.
Good news, no changes to the Splunk Show environment are required as port 80 and 443 are already open.

Also, updated PetClinic K8s workshop to expose on 80/433. Added notes into workshop text highlighting these ports are available to access the URLs.


[WIP] Install after eject

Related Issue:
#68
Summary:
Addressing the issue where ejecting causes babel-loader to not be found. Didn't see anyone working on it so thought I'd take a stab at it!
Tests are failing but thought I'd get some feedback first before attempting to fix them, in case this approach isn't quite right...
Test Plan:

Create a test CRA project
Click eject
Task will run (with pending spinner) while promise is resolving. Once it's resolved, then the rest of the tasks will run (task pane will get deleted, dependency list will be updated which exposes babel-loader to the list because it's now installed)

Not sure if we want to modify things because right now there's a 'View Details' button in the UI for the eject task, but nothing gets piped to it. We may want to pipe all the yarn install stuff to it now that it runs because it's a longer process than the simple eject.

Feedback addressed! Left the function where it is for now but let me know if you think it should be moved. I also chose to remove the 'View Details' button for this task. I feel as though the Details modal is pretty unnecessary if all we're showing is 'Ejecting project...' in the output. At that point it's not really a log output, more of a status message. If anything, we could modify 'Pending' spinner to be 'Ejecting Project' but I don't think it's super critical... what do you think?
Also hacked away at the tests for an hour to try get them to pass but ultimately unsuccessful. Think I need some help with how to test this...


Improve Documentation

Improve documentation to include usage details for package

The documentation has been updated with usage details in the following in the following commit.


Split prune into slightly small functions

What does this PR change? What problem does it solve?
prune is currently a function with over 400 lines of code. This PR splits it into three pieces with only a bit more than 100 lines of code. There is definitely room for further refactoring, but I wanted to keep this PR simple.
In addition, the PR contains two small commits which add a sanity check that all expected blob were repacked and a fallback in case a blob cannot be read while reading a pack. The latter might help with situations where multiple copies of a blob exist.
Was the change previously discussed in an issue or on the forum?
No.
Checklist

[x] I have read the contribution guidelines.
[x] I have enabled maintainer edits.
[ ] I have added tests for all code changes.
[ ] I have added documentation for relevant changes (in the manual).
[ ] There's a new file in changelog/unreleased/ that describes the changes for our users (see template).
[x] I have run gofmt on the code in all commits.
[x] All commit messages are formatted in the same style as the other commits in the repo.
[x] I'm done! This pull request is ready for review.

What's the issue with #3140 which does a similar thing (at least in the first two commits)?

I totally forgot about the refactoring in #3140. I've cherry-picked the commit with the prunePlan struct.

Let's merge this as it seems to be working fine and nobody complained about the code ;-) .


Service manager captures exceptions thrown by Factories

This is not necessarily an problem, but the fact that service manager captures exceptions thrown by Factories makes it harder to debug, and hard to treat them as well. I would suggest that, as an improvement, we remove the mechanism of catching these exceptions letting the programmer free to treat them as it pleases him.
If there is some constraint or business rule I'm missing, please let me know.

This is addressed in the refactor currently in the develop branch.
On Oct 4, 2015 2:46 PM, "Jean Carlo Machado"<EMAIL_ADDRESS>wrote:

This is not necessarily an problem, but the fact that service manager
captures exceptions thrown by Factories makes it harder to debug, and hard
to treat them as well. I would suggest that, as an improvement, we remove
the mechanism of catching these exceptions letting the programmer free to
treat them as it pleases him.
If there is some constraint or business rule I'm missing, please let me
know.
—
Reply to this email directly or view it on GitHub
https://github.com/zendframework/zend-servicemanager/issues/32.

Thanks for the quick answer. :)


⚠ 한경주요지수-코스피200 has degraded performance

In 7751b64, 한경주요지수-코스피200 (https://markets.hankyung.com/indices/kospi200) experienced degraded performance:

HTTP code: 200
Response time: 20510 ms

Resolved: 한경주요지수-코스피200 performance has improved in 4725bb0.


I should see size in characterization metadata

When I view characterization metadata I should see the FileSet size in the characterization metdata.

Looks like it is not being index for display.  The display items are here: https://github.com/projecthydra/curation_concerns/blob/master/app/presenters/curation_concerns/characterization_behavior.rb

PSUSprint3


no  kernel headers

I update to 4.14.48
but no kernel head in my system when i install  seeed-voicecard -v 0.3
dkms add -m seeed-voicecard -v 0.3
DKMS: add completed.
Error! echo
Your kernel headers for kernel 4.14.48+ cannot be found at
/lib/modules/4.14.48+/build or /lib/modules/4.14.48+/source.

You Have to install kernel-header
sudo apt-get install kernel-header
Le mar. 12 juin 2018 à 11:42, dissipator<EMAIL_ADDRESS>a
écrit :

I update to 4.14.48
but no kernel head in my system when i install seeed-voicecard -v 0.3
dkms add -m seeed-voicecard -v 0.3
DKMS: add completed.
Error! echo
Your kernel headers for kernel 4.14.48+ cannot be found at
/lib/modules/4.14.48+/build or /lib/modules/4.14.48+/source.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Hexxeh/rpi-update/issues/262, or mute the thread
https://github.com/notifications/unsubscribe-auth/AKoMY1Y0_hHm8WgrkS7aX893dk5qSrhIks5t740ggaJpZM4UkG4T
.

yes only 4.9.+ header

Are you using an updated raspbian stretch distribution? That should be on 4.14.
You may also want to consider this: https://github.com/notro/rpi-source/wiki

OK ,I will try.thanks.......

*** Create /lib/modules//{build,source} symlinks
*** .config
*** Module.symvers
*** make modules_prepare
HOSTCC  scripts/basic/fixdep
/bin/sh: 1: scripts/basic/fixdep: Permission denied
scripts/Makefile.host:102: recipe for target 'scripts/basic/fixdep' failed
make[2]: *** [scripts/basic/fixdep] Error 126
Makefile:463: recipe for target 'scripts_basic' failed
make[1]: *** [scripts_basic] Error 2
make: *** No rule to make target 'modules_prepare'。 停止。
Traceback (most recent call last):
File "/usr/bin/rpi-source", line 379, in
sh("cd %s && make modules_prepare %s" % (linux_symlink, (" > /dev/null" if args.quiet else "")))
File "/usr/bin/rpi-source", line 85, in sh
subprocess.check_call(cmd, shell=True)
File "/usr/lib/python2.7/subprocess.py", line 186, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command 'cd /app/root/linux && make modules_prepare ' returned non-zero exit status 2
use the root user.

the same as:
https://github.com/raspberrypi/linux/issues/2579

@dissipator is this issue still relevant?

@dissipator is this issue still relevant?

This issue is stall. Please consider to close.


[Feature] Animations on home page.

Description
I want to add subtle floating effects for the website's home page when the page gets loaded,
this would make the website more interesting.
Please assign this issue to me under SWOC.
Screenshots
No response
Checklist

[X] I have checked the existing issues.
[X] I follow Contributing Guidelines of this project.
[X] I am a IWOC'24 contributor.
[ ] I am a JWOC'24 contributor.
[X] I am a SWOC'24 contributor.

Code of Conduct

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

Do you want to add preloader to the website @yashi-15


[feedback] operator alerting system installation

Background:

AWS EKS cluster v1.16.15-eks-ad4801
default pod security policy is disabled (https://docs.aws.amazon.com/eks/latest/userguide/pod-security-policy.html)

Installation was done from master using following commands:
export VM_VERSION=`basename $(curl -fs -o/dev/null -w %{redirect_url} https://github.com/VictoriaMetrics/operator/releases/latest)`
wget https://github.com/VictoriaMetrics/operator/releases/download/$VM_VERSION/bundle_crd.zip
unzip  bundle_crd.zip
rm bundle_crd.zip

kubectl apply -f release/crds
kubectl apply -f release/operator

Current issues I've experienced:
1. No PSP goes with the operator
As we have default pod security policy disabled - k8s requires to have it explicitly specified. Had to apply custom one in order to launch operator.
2. Operator constantly spams errors when tries to reach non-existing CRD:
{"level":"error","ts":1606915730.012771,"logger":"controller_vmcluster","msg":"cannot get  server resource","group":"monitoring.coreos.com/v1","kind":"probe","error":"unable to retrieve the complete list of server APIs: custom.metrics.k8s.io/v1beta1: the server is currently unable to handle the request","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\tgithub.com/go-logr/zapr@v0.1.0/zapr.go:128\ngithub.com/VictoriaMetrics/operator/controllers.waitForAPIResource\n\tgithub.com/VictoriaMetrics/operator/controllers/vmprometheusconverter_controller.go:149\ngithub.com/VictoriaMetrics/operator/controllers.(*ConverterController).runInformerWithDiscovery\n\tgithub.com/VictoriaMetrics/operator/controllers/vmprometheusconverter_controller.go:173\ngithub.com/VictoriaMetrics/operator/controllers.(*ConverterController).Run.func4\n\tgithub.com/VictoriaMetrics/operator/controllers/vmprometheusconverter_controller.go:204\ngolang.org/x/sync/errgroup.(*Group).Go.func1\n\tgolang.org/x/sync@v0.0.0-20200317015054-43a5402ce75a/errgroup/errgroup.go:57"}

We do not have prometheus operator CRDs installed and none was shipped with VM operator
3. .serviceAccountName in vmalert manifest is ignored:
After applying this manifests I see errors:
Error creating: pods "vmalert-test-794d4868cc-" is forbidden: unable to validate against any pod security policy: []

Deployment starts successfully when I specify service account name manually in it.
4. Error while adding metadata
After applying the same manifests I see errors:
{"level":"error","ts":1606916310.0136878,"logger":"controllers.VMAlert","msg":"cannot create or update vmalert deploy","vmalert":"monitoring-system/test","error":"cannot update vmalert deploy: Deployment.apps \"vmalert-test\" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{\"app\":\"server\", \"app.kubernetes.io/component\":\"monitoring\", \"app.kubernetes.io/instance\":\"alert\", \"app.kubernetes.io/name\":\"victoria-metrics-alert\", \"managed-by\":\"vm-operator\"}: `selector` does not match template `labels`","stacktrace":"github.com/go-logr/zapr.(*zapLogger).Error\n\tgithub.com/go-logr/zapr@v0.1.0/zapr.go:128\ngithub.com/VictoriaMetrics/operator/controllers.(*VMAlertReconciler).Reconcile\n\tgithub.com/VictoriaMetrics/operator/controllers/vmalert_controller.go:68\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:235\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:209\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker\n\tsigs.k8s.io/controller-runtime@v0.6.2/pkg/internal/controller/controller.go:188\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil.func1\n\tk8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:155\nk8s.io/apimachinery/pkg/util/wait.BackoffUntil\n\tk8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:156\nk8s.io/apimachinery/pkg/util/wait.JitterUntil\n\tk8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:133\nk8s.io/apimachinery/pkg/util/wait.Until\n\tk8s.io/apimachinery@v0.18.6/pkg/util/wait/wait.go:90"}

https://github.com/VictoriaMetrics/operator/blob/master/docs/api.MD#embeddedobjectmetadata
That's all. I've reached this point and stopped so far, will inform when I go further :)
Best.

Thanks for reporting!

this one can be simply disabled with env variables passed to operator deployment:

- name: VM_ENABLEDPROMETHEUSCONVERTER_PODMONITOR
  value: "false"
- name: VM_ENABLEDPROMETHEUSCONVERTER_SERVICESCRAPE
  value: "false"
- name: VM_ENABLEDPROMETHEUSCONVERTER_PROMETHEUSRULE
  value: "false"
- name: VM_ENABLEDPROMETHEUSCONVERTER_PROBE
  value: "false"

i'll create kustomize patch for it.
Others must be fixed.

@afoninsky  release 0.5.0 must fix all exists issues and brings support for PSP. For operator it was included at helm-chart and kustomize install, for CRD objects it will be generated automatically, check related doc https://github.com/VictoriaMetrics/operator/blob/master/docs/security.MD#podsecuritypolicy
There is also issue with proposal for auto-discovery for CRD components: https://github.com/VictoriaMetrics/operator/issues/114
If you have some thoughts suggestions, can you share it there?

feel free to reopen if spot something else.


npm 8.6, authorization header missing & symlink problem

Hello,
I can't install npm 8.6.0, which is the recommanded version by node doctor.
When using nodist global npm 8.6 :
npm 8.6
{"message":"Must specify access token via Authorization header.
https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param","documentation_url":"https://docs.github.com/v3/#oauth2-token-sent-in-a-header"}.
Sorry.

I've got no problem with previous versions.
The latest installable version is 8.5.5 (match with node 17.8.0).
If I use the official command npm install -g<EMAIL_ADDRESS>it installs but can't be used (npm -v still return 8.5.5).
Another bug : the symlinks created automatically in npmv/8.5.5/nodes-modules were not working on my Windows 10 system, I don't know why. I had to recreate them to have npm working as expected. Same for the ``` arborist ```` symlink in @npmcli.
If you need more infos on the specs of my computer, please ask.
Cheers !

I've returned on my project and I've tried to update npm and I'm receiving something similar:
$>nodist npm latest
Unhandled rejection {"message":"Must specify access token via Authorization header. https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param","documentation_url":"https://docs.github.com/v3/#oauth2-token-sent-in-a-header"}

I had a similar error message starting from scratch with nodist - I typed
"nodist add 16" and it installed 11.13.0 and 16.14.2
"nodist npm" and it reported npm 6.9.0 (which doesn't work with node 16)
"nodist 16" and it switched to 16
"nodist npm 8.5.5" and it reported {"message":"Must specify access token via Authorization header.
https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param","documentation_url":"https://docs.github.com/v3/#oauth2-token-sent-in-a-header"}.
Sorry.
(I really like the "Sorry" part ;-)
the workaround I finally learned about was " nodist npm global match " which eventually finished successfully.  Now typing
"nodist npm" reports 6.9.0 and 8.5.0 with 8.5.0 active.
Now I'm getting what seems to be an unrelated error: "Error: Cannot find module 'libnpmfund'"

I´m having same issue as @joelparks

any news about this ?

bonjour svp aider mois je n'arrive pas à installer les asset css de breese de laravel9 ,je un systeme ubuntu 20.04 ,xampp,apache server http

A quick fix after doing nodist npm match|<version>, it's to manually fix the symlinks.
Windows could be configured in developer mode to avoid administration rights.
nodist npm match
cd C:\Program Files (x86)\Nodist\npmv\8.11.0\node_modules
rm @npmcli\arborist && mklink /D @npmcli\arborist ..\..\workspaces\arborist
rm libnpmaccess  && mklink /D libnpmaccess ..\workspaces\libnpmaccess
rm libnpmdiff    && mklink /D libnpmdiff ..\workspaces\libnpmdiff
rm libnpmexec    && mklink /D libnpmexec ..\workspaces\libnpmexec
rm libnpmfund    && mklink /D libnpmfund ..\workspaces\libnpmfund
rm libnpmhook    && mklink /D libnpmhook ..\workspaces\libnpmhook
rm libnpmorg     && mklink /D libnpmorg ..\workspaces\libnpmorg
rm libnpmpack    && mklink /D libnpmpack ..\workspaces\libnpmpack
rm libnpmpublish && mklink /D libnpmpublish ..\workspaces\libnpmpublish
rm libnpmsearch  && mklink /D libnpmsearch ..\workspaces\libnpmsearch
rm libnpmteam    && mklink /D libnpmteam ..\workspaces\libnpmteam
rm libnpmversion && mklink /D libnpmversion ..\workspaces\libnpmversion

That is because the tar lib used by nodist seems to not create correctly symlink about directories on Windows when extracting https://codeload.github.com/npm/cli/tar.gz/v8.11.0

Workaround:
Download NPM CLI version from official repo: https://github.com/npm/cli/tree/v8.6.0
and unpack locally to your C:\Program Files (x86)\Nodist\npmv\8.6.0 folder

Yes that will work. Thank you for posting.
I will have a new package out either end of July or beginning of August. Finally, got our new office and need something to break the ice with.

I have created an installer. I hope it will be useful for you.
[wafflook/A node.js and npm version manager(nodist will not die. It will revive)

The workaround doesn't seem to work, and wafflook's installer is no longer available. Any word on this?
I populated C:\Program Files (x86)\Nodist\npmv\9.5.1 with the contents of https://github.com/npm/cli/tree/v9.5.1 and then ran:

nodist npm 9.5.1
npm 9.5.1
{"message":"Must specify access token via Authorization header.
https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param","documentation_url":"https://docs.github.com/v3/#oauth2-token-sent-in-a-header"}.
Sorry.

The workaround doesn't seem to work, and wafflook's installer is no longer available. Any word on this?
I populated C:\Program Files (x86)\Nodist\npmv\9.5.1 with the contents of https://github.com/npm/cli/tree/v9.5.1 and then ran:

nodist npm 9.5.1
npm 9.5.1
{"message":"Must specify access token via Authorization header.
https://developer.github.com/changes/2020-02-10-deprecating-auth-through-query-param","documentation_url":"https://docs.github.com/v3/#oauth2-token-sent-in-a-header"}.
Sorry.

You have to do essentially what @nicomeunier posted, but with some minor modifications:

run nodist npm match global
open a command prompt (cmd, not powershell) in admin mode and input:

cd C:\Program Files (x86)\Nodist\npmv\9.5.1\node_modules
del @npmcli\arborist && mklink /D @npmcli\arborist ..\..\workspaces\arborist
del @npmcli\config && mklink /D @npmcli\config ..\..\workspaces\config
del libnpmaccess  && mklink /D libnpmaccess ..\workspaces\libnpmaccess
del libnpmdiff    && mklink /D libnpmdiff ..\workspaces\libnpmdiff
del libnpmexec    && mklink /D libnpmexec ..\workspaces\libnpmexec
del libnpmfund    && mklink /D libnpmfund ..\workspaces\libnpmfund
del libnpmhook    && mklink /D libnpmhook ..\workspaces\libnpmhook
del libnpmorg     && mklink /D libnpmorg ..\workspaces\libnpmorg
del libnpmpack    && mklink /D libnpmpack ..\workspaces\libnpmpack
del libnpmpublish && mklink /D libnpmpublish ..\workspaces\libnpmpublish
del libnpmsearch  && mklink /D libnpmsearch ..\workspaces\libnpmsearch
del libnpmteam    && mklink /D libnpmteam ..\workspaces\libnpmteam
del libnpmversion && mklink /D libnpmversion ..\workspaces\libnpmversion

Note using del instead of rm and the new link to config that I guess was added sometime after 8.11.

This worked for me, thanks to everyone that contributed. It's so annoying that we have to do stuff like this just to get npm working!

Has been fixed in v.10.2


Button style conflict when using Suki and Cheryl

Hi, I'm writing an Avalonia demo project, and I want to mainly use Suki controls, when it comes to Android and IOS, I want to use Bottom Tabs in Cheryl. So I install both, and my app window(running on Windows10) become like this👇

Hi,
I would advise you to not use both in the same project, there are probably some named use that are the same. If you really want to do so, maybe check that Cheryl is included before Suki, so Suki values overrides it if necessary.
For cross-platform development, I would advice you to make three seperate project.

A Class Library project for all your backend
A desktop avalonia app for your desktop development, using SukiUI and your backend
A xplat Avalonia app for Android/IOS, using CherylUI and your backend

To me, the benefit of cross-platform is not to be able to make one view for all the platforms, it's almost impossible to do it correctly, but to be able to use the same stack for everything. If you want to do a nice desktop UI and a nice Mobile UI, sharing the same view is impossible to me, no matter the framework btw.
Hope it helps you 👍

Thanks for your advice, that's helpful！
Now I'm working on seperating core library from my original project.


accuracy

For seq2seq, I got following accuracies (based on Atis dataset):
seq2seq (with attention) | Accuracy | 86.3839 | 84.2000
seq2seq (lstm) | Accuracy | 77.4554 | 75.7000
86.3839 is from py code whereas 84.2 is mentioned in the paper (lua code). Similarly, 77.4554 based on py code and 75.7 mentioned in the paper.
On Geoqueries, I have following:
seq2seq (with attention) | Accuracy | 83.5714 | 84.6000
seq2seq (lstm) | Accuracy | 73.9285 | 72.9000
I am trying to understand the reason for having better accuracy in py code.

I think the discrepancies in accuracy result from differences in seed/random number initialization or CUDA version/hardware rather than any fundamental differences in the implementation.

I am running the code on CPU i.e. -1.
So, yeah. I agree it can be from seed/random initialisation.

Hi, a question: with random seed initialisation, evaluation is normally taken as average results for n rounds. With the accuracy calculations in util.py, I believe this is not the case.
Please confirm.

Seeds are set according to the seed parameter in main.py, although even with that variations in version and hardware can cause differences. You are right that evaluation of results is taken over a single round. For an overview of some of the problems with reproducibility I definitely recommend this paper..

Thank you.


Styling issue on nav bar

The "documentation" link is shifted to the left and half hidden.

odd - I can replicate if I really zoom out in the browser. does problem fix if you zoom in a bit?

To 125%, yes.

odd - thanks! we have a big release going out this week which hopefully fixes this - should be deployed by end of week and would love to know if the problem still exists.

This should be fixed now (I hope!) have a new problem that the apidoc logo itself is now hidden,but will fix in another patch


gulp nuke deletes Gulpfile

Thank you for reporting an issue or suggesting an enhancement. We appreciate your feedback - to help the team to understand your needs, please complete the below template to ensure we have the necessary details to assist you.
Category
[ ] Question
[ ] Typo
[X ] Mistake
[ ] Additional article idea
Expected or Desired Behavior
When I type in gulp nuke it should clean up my web part directory.
Observed Behavior
When I type gulp nuke  I get cannot find module gulp-core-build.
C:\XXX\YYY\ZZZ\Documents\SPFx\Projects\SiteInfo-webpart>gulp nuke
module.js:327
throw err;
^
Error: Cannot find module 'gulp-core-build'
at Function.Module._resolveFilename (module.js:325:15)
at Function.Module._load (module.js:276:25)
at Module.require (module.js:353:17)
at require (internal/module.js:12:17)
at Object. (C:\XXX\YYY\ZZZ\Documents\SPFx\Projects\SiteInfo-webpart\node_modules@microsoft\sp-build-web\lib\index.js:13:25)
at Module._compile (module.js:409:26)
at Object.Module._extensions..js (module.js:416:10)
at Module.load (module.js:343:32)
at Function.Module._load (module.js:300:12)
at Module.require (module.js:353:17)
Steps to Reproduce
follow instructions which end with gulp build

Hi Nigel, it seems like you're missing one of the dependencies. Could you try running in command line npm install to restore dependencies and try running gulp nuke after that?

Hi Waldek
I have run npm install and other than the usual suspect :-
(node) warning: possible EventEmitter memory leak detected. 11 error listeners added. Use emitter.setMaxListeners() to increase limit..42.1\package\package.json written
Worked OK.
Then ran gulp nuke and got this error :-
[14:12:05] No gulpfile found
This has only started happening after implementing  SharePoint Framework SPFX drop 2 https://github.com/SharePoint/sp-dev-docs/wiki/Release-Notes-Drop-2
Regards
Nigel
From: Waldek Mastykarz<EMAIL_ADDRESS>Sent: 05 September 2016 13:48
To: SharePoint/sp-dev-docs<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-dev-docs] Cannot find module gulp-core-build after gulp nuke (#151)
Hi Nigel, it seems like you're missing one of the dependencies. Could you try running in command line npm install to restore dependencies and try running gulp nuke after that?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/SharePoint/sp-dev-docs/issues/151#issuecomment-244739125, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIF00Nv-tTuQB8TIY30UpOaQAny4Moz2ks5qnA-KgaJpZM4J02jC.

No virus found in this message.
Checked by AVG - www.avg.comhttp://www.avg.com
Version: 2016.0.7688 / Virus Database: 4649/12947 - Release Date: 09/05/16

Hi Waldek
I ran npm install again after my previous email and got a different error :-
C:\ XXX\YYYY\ZZZZ \Documents\SPFx\Projects\SiteInfo-webpart>npm install
npm WARN optional Skipping failed optional dependency /chokidar/fsevents:
npm WARN notsup Not compatible with your operating system or architecture<EMAIL_ADDRESS>npm WARN enoent ENOENT: no such file or directory, open 'C:\XXX\YYYY\ZZZZ\Documents\SPFx\Projects\SiteInfo-webpart\package.json'
npm WARN enoent ENOENT: no such file or directory, open 'C:\ XXX\YYYY\ZZZZ<EMAIL_ADDRESS>npm WARN enoent ENOENT: no such file or directory, open 'C:\ XXX\YYYY\ZZZZ<EMAIL_ADDRESS>npm WARN enoent ENOENT: no such file or directory, open 'C:\ XXX\YYYY\ZZZZ \Documents\SPFx\Projects\SiteInfo-webpart\node_modules\es6-templates\package.json'
npm WARN enoent ENOENT: no such file or directory, open 'C:\ XXX\YYYY\ZZZZ \Documents\SPFx\Projects\SiteInfo-webpart\node_modules\html-minifier\package.json'
npm WARN<EMAIL_ADDRESS>requires a peer of cldr-data@>=25 but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of cldr-data@>=25 but none was installed.
npm WARN<EMAIL_ADDRESS>requires a peer of cldr-data@>=25 but none was installed.
npm WARN SiteInfo-webpart No description
npm WARN SiteInfo-webpart No repository field.
npm WARN SiteInfo-webpart No README data
npm WARN SiteInfo-webpart No license field.
C:\ XXX\YYYY\ZZZZ \Documents\SPFx\Projects\SiteInfo-webpart>dir
Volume in drive C has no label.
Volume Serial Number is 749F-CEC2
Directory of C:\ XXX\YYYY\ZZZZ \Documents\SPFx\Projects\SiteInfo-webpart
05/09/2016  00:42              .
05/09/2016  00:42              ..
05/09/2016  14:22              node_modules
04/09/2016  22:03              src
04/09/2016  22:03              typings
0 File(s)              0 bytes
5 Dir(s)  14,684,434,432 bytes free
I would seem that npm nuke has nuked a bit too much !
Regards
Nigel
From: Waldek Mastykarz<EMAIL_ADDRESS>Sent: 05 September 2016 13:48
To: SharePoint/sp-dev-docs<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-dev-docs] Cannot find module gulp-core-build after gulp nuke (#151)
Hi Nigel, it seems like you're missing one of the dependencies. Could you try running in command line npm install to restore dependencies and try running gulp nuke after that?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/SharePoint/sp-dev-docs/issues/151#issuecomment-244739125, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIF00Nv-tTuQB8TIY30UpOaQAny4Moz2ks5qnA-KgaJpZM4J02jC.

No virus found in this message.
Checked by AVG - www.avg.comhttp://www.avg.com
Version: 2016.0.7688 / Virus Database: 4649/12947 - Release Date: 09/05/16

Paging @nickpape-msft @iclanton

Chatted with Nick, and looking at the your output, it was that gulp nuke couldn't find gulp-core-build.
Can you double check what version of npm you are running?

Hi Pat
npm version = 3.10.7
Regards
Nigel
From: Pat Miller<EMAIL_ADDRESS>Sent: 07 September 2016 18:57
To: SharePoint/sp-dev-docs<EMAIL_ADDRESS>Cc: Nigel Price<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [SharePoint/sp-dev-docs] Cannot find module gulp-core-build after gulp nuke (#151)
Chatted with Nick, and looking at the your output, it was that gulp nuke couldn't find gulp-core-build.
Can you double check what version of npm you are running?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/SharePoint/sp-dev-docs/issues/151#issuecomment-245364843, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIF00Oz1eVnZSkRw17D-meLJh5Lh0z4Nks5qnvsJgaJpZM4J02jC.

No virus found in this message.
Checked by AVG - www.avg.comhttp://www.avg.com
Version: 2016.0.7688 / Virus Database: 4649/12958 - Release Date: 09/06/16

Is this still an issue for you? Has this happened again?

I have not seen it since I installed drop 3.  That might just be co-incidence

Okay I'm going to close this. Let us know if you see this again.

OK- will do


[Spark] Write INT64 by default for Timestamps

Which Delta project/connector is this regarding?

[x] Spark
[ ] Standalone
[ ] Flink
[ ] Kernel
[ ] Other (fill in here)

Description

Iceberg states in the spec that Timestamps should be written with INT64 physical types. There were already flags to enable this, but this PR makes this behavior the default.
INT96 is discouraged: https://github.com/apache/parquet-format/blob/master/src/main/thrift/parquet.thrift#L981

How was this patch tested?

Added new unit-tests to validate the correct behavior

Does this PR introduce any user-facing changes?

Yes, it will default to INT64 if nothing has been set.

@Fokko @lzlfred should we update the protocol to recommend INT64?
Context: https://github.com/delta-io/delta/pull/2048/files#r1476851129


drop requirement that custom elements must have a '-' in their name

From @rafaelw on October 30, 2014 22:0
Copied from original issue: domokit/mojo#17

obsolete


handle UUID type field (some database like postgres support UUID type field)

This fix can correctly show the UUID field in table widget.

Coverage decreased (-0.1%) to 81.355% when pulling 73a3d06a7c955ee13cdec19571df4967634c58e5 on tninja:master into 7c810dbd20ef394c073ec78c0c46380f471fff4d on airbnb:master.

@tninja so currently json is raising an exception because it can't serialize uuid right?

minimal change that can't hurt, LGTM


TS doesn't work well with generics and classes as props

TypeScript Version:  2.3.4 , 252
Code
class Container<TT> {
    attr: TT
  }

class AttrX {
    hello: string = 'max'
}

const createClass = <T>(x: T): typeof Container => {
    return class ExtendedContainer extends Container<T> {}
}

const X = createClass(AttrX)
const x = new X()
console.log(x.attr.hello)

Expected behavior:
It's compiled
Actual behavior:
I see error
Type 'typeof ExtendedContainer' is not assignable to type 'typeof Container'.
  Type 'ExtendedContainer' is not assignable to type 'Container<TT>'.
    Types of property 'attr' are incompatible.
      Type 'T' is not assignable to type 'TT'.

Looks like you're dealing with the static side of the class in a couple places where you really want the instance side. This seems to work
const createClass = <T>(x: new() => T) => {
    return class ExtendedContainer extends Container<T> {}
}

@jwbay awesome, thank you


Enhancement: New Props for Calendar Component - Disabled Dates, Multiple Day Selection, and Custom Date Styles

Enhancement Request for Calendar Component 📆🛠
Hello there! I'm excited to suggest some enhancements for the Calendar component. These features would significantly boost its functionality and user experience.
1. Disabled Dates Prop 🚫📅
Description: This prop would allow us to specify dates in the calendar that should be disabled. These dates would be non-selectable and visually distinct, ideal for indicating unavailable dates like holidays or past days.
2. Multiple Day Pick Prop 🗓✅
Description: This feature would enable users to select multiple dates within the calendar. It's a key functionality for scenarios like booking systems or event scheduling, where multiple distinctive dates needs to be chosen.
3. Dates with Different Style Prop 🎨📆
Description: This enhancement allows for the custom styling of certain dates. It's perfect for highlighting specific dates (such as birthdays or holidays) with different colors, fonts, or borders for easy identification.
Integrating these features would make the Calendar component more versatile and adaptable for various use cases. I believe they would be valuable additions to your library. Looking forward to your thoughts on this!
Thank you for your continuous efforts in improving this library! 🌟

Disabled Dates already exist, use the isDateDisabled prop, or if you want the data to be unavailable, is the isDateUnavailable prop.
Multiple dates already exist (https://bits-ui.com/docs/components/calendar) use the multiple prop.
This is something that shouldn't be handled at a library level and should be handled individually. You have access to the date before rendering it in the <Calendar /> component so you can apply your checks and update the styles there!

Oh thanks a lot! Sorry to bother you with the useless issue open. Have a great day :D


(ISO 19144-2) Word: List of figures cannot be regenerated

After clicking on Update field, this happens:

Style name for FigureTitle is Figuretitle in DIS: ToC directive needed to be updated.

Confirm fixed, can regenerate properly.


Arctis Nova 7x compatibility

Hello, I have tried your app with Arctis Nova 7x and they do not appear. Is it possible to add them? Thank you very much for your time.

Here are the Arctis Nova 7 details while you are at it

Ive added these devices into the latest release :) https://github.com/craigster1991/arctis-battery-win-app/releases/tag/v0.2.1

Hello!
Unfortunately, it doesn't work, I've been debugging and I've seen that there is a condition that expects attDevice?.usage !== 1 in device.js, the problem is that my Artix 7X devices reach usage 1 (I don't know why it appears three times either).
{
vendorId: 4152,
productId: 8710,
path: '\\?\hid#vid_1038&pid_2206&mi_03#8&11defc96&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}',
manufacturer: 'SteelSeries',
product: 'Arctis Nova 7X',
release: 273,
interface: 3,
usagePage: 65472,
usage: 1
},
{
vendorId: 4152,
productId: 8710,
path: '\\?\hid#vid_1038&pid_2206&mi_04#8&3a49aa5f&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}',
manufacturer: 'SteelSeries',
product: 'Arctis Nova 7X',
release: 273,
interface: 4,
usagePage: 12,
usage: 1
},
{
vendorId: 4152,
productId: 8710,
path: '\\?\hid#vid_1038&pid_2206&mi_05#8&27198e21&0&0000#{4d1e55b2-f16f-11cf-88cb-001111000030}',
manufacturer: 'SteelSeries',
product: 'Arctis Nova 7X',
release: 273,
interface: 5,
usagePage: 65280,
usage: 1
}


Make a suggestion about 'Unknown mana'

first of all thanks for the bot.
please add a logic in the 'download_card_sets.py' file.
add '(http://dd.b.pvp.net/latest/set6cde/en_us/data/set6cde-en_us.json)'  to 'card_sets'.
'cde'

Done
https://github.com/MOj0/LoR-Bot/commit/eacd3f07a69e511f02c4b1e5e4442293e91597d1


feat: compound rows in paradigms

What's in this PR?
Adds compound rows! Do you have inflections that have multiple valid realizations? What's the plural of cactus? This PR will place each wordform on its own row instead of concactenating all the results together on the same line!
Before:

After:

added: CompoundRow class — contains multiple ContentRow
added: RowLabel has a row_span attribute, which allows it to label multiple rows!
added: Pane.tr_rows — iterates rows that should create <tr> in the HTML output
added: SuppressOutputCell — indicates that a <td> should NOT be created in the HTML output
added:  a bevy of unit tests, integration tests, and end-to-end tests

Fixes #507

Codecov Report

Merging #858 (254be70) into main (0ed6a09) will increase coverage by 1.81%.
The diff coverage is 89.78%.

@@            Coverage Diff             @@
##             main     #858      +/-   ##
==========================================
+ Coverage   79.85%   81.67%   +1.81%
==========================================
  Files         104      106       +2
  Lines        4279     4414     +135
  Branches      636      650      +14
==========================================
+ Hits         3417     3605     +188
+ Misses        743      683      -60
- Partials      119      126       +7

Impacted Files
Coverage Δ

src/CreeDictionary/CreeDictionary/urls.py
100.00% <ø> (ø)

src/CreeDictionary/morphodict/urls.py
100.00% <ø> (ø)

.../CreeDictionary/DatabaseManager/test_db_builder.py
36.20% <50.00%> (ø)

src/CreeDictionary/API/search/cvd_search.py
83.33% <66.66%> (-5.56%)
:arrow_down:

src/CreeDictionary/CreeDictionary/views.py
78.26% <68.00%> (-2.33%)
:arrow_down:

.../CreeDictionary/CreeDictionary/paradigm/manager.py
80.26% <76.19%> (-14.61%)
:arrow_down:

...CreeDictionary/paradigm/crkeng_corpus_frequency.py
80.76% <80.76%> (ø)

...nary/management/commands/ensurecypressadminuser.py
71.87% <83.33%> (+4.01%)
:arrow_up:

...rc/CreeDictionary/CreeDictionary/paradigm/panes.py
87.94% <97.40%> (+2.27%)
:arrow_up:

src/CreeDictionary/CreeDictionary/hfstol.py
86.95% <100.00%> (-0.55%)
:arrow_down:

... and 16 more

Continue to review full report at Codecov.

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

The code looks ok, but honestly I like the version in the first screenshot better, the part with the slash instead of multiple rows.
I don’t see that on the production itwêwina site, so is that something you were experimenting with?
With the two images side by side, seeing kinipânaw / kinipânânaw looks like two options for the same thing, where the stacked cells make it look to me like there’s a missing label.
That’s just my opinion though, I’m happy with whatever others decide to do here.

The code looks ok, but honestly I like the version in the first screenshot better, the part with the slash instead of multiple rows.

Yeah, I think styling needs to make it obvious that these forms are related.

I don’t see that on the production itwêwina site, so is that something you were experimenting with?

Yeah, production itwêwina doesn't even render multiple forms 💀

With the two images side by side, seeing kinipânaw / kinipânânaw looks like two options for the same thing, where the stacked cells make it look to me like there’s a missing label.
That’s just my opinion though, I’m happy with whatever others decide to do here.

I think the paradigm presentation needs to be worked on soon (styling, bolding, grouping, etc.). @aarppe, @dwhieb, what do other sources use for when there are multiple realizations of the same inflection?

What is the plural of cactus? 🤔

cactus+N+Pl	cactuses
cacus+N+Pl	cacti

It can be either cactuses or cacti. Both are acceptable and understandable inflections. Now how do you cram that into a single paradigm?

Looking at various on-line resources on paradigms, some by more established entities and others by more random matches when searching for 'paradigm(s)', Wiktionary appears to put alternative forms on their own lines (separated by a semicolon, that I'd ignore), e.g. for the Finnish hevonen 'horse'. Whether the alternative words end up on their own lines due to cell size or not is not clear.

Another approach is taken by this older resource for Latin, separating alternative forms with commas (link):

This same approach is used in the (Finnish) Language Bureau's on-line dictionary for Finnish:

Another alternative approach for Latin uses slashes to separate alternative forms (link):

I'd think that we can use any approach that is clear and makes sense to users. A slash is quite broadly understood to separate alternatives.

I merged this, but @andrewdotn, I think you're right. Slashes would probably work better, given the examples @aarppe posted. I'll punt that change until #862. In the meantime, @aarppe, this PR fixes the issue that highlighting should apply for each observed wordform rather than analysis.


Create A Welcome Message for PNG

Kindly proposed to added a welcome message for PNG new mapper

🚀 Deployed!


Order of execution for different extensions (extending the same standard object)

Hi team,
Is there a plan that we have a priority property when we publish extensions to control which extension executes first if two different extensions extend the same object?
Kind Regards,
Robert

If extension one has an object id 50000 and is published.
Than, while publishing the second extension with same object id 50000, will give an error.

What if Object IDs are different but extending the same object ?
For example, if I have code in OnDelete trigger in each Customer's tableextension I published. Which one is triggered first ? And how to give priority to one or the other ?

I'd guess it's the same as subscribing to events - there is no possibility to give priority. Write your code to be safe everything is always working..

We are thinking about this scenario. Let's combine the discussion under suggestion #154


release v0.24.0

Breaking Changes

Renames original Card components to be CardEdition.

Adds

Adds the DatePicker component.
Adds new Card component.
Adds spacing prop to Form component to allow for spacing variations.
Adds Style Guide Forms

Changes

Exports VideoPlayerAspectRatios.
Adds additional props for the DatePicker component based on its TAD Addendum section.
Adds Tugboat QA configuration for PR preview deployments to replace Netlify.
Updates the DatePicker, TextInput, Select, and Label components to pass an optional showOptReqLabel prop to conditionally render "Required"/"Optional" in the label text.

Fixes

Fixes Accordion FAQ Storybook example rendering bug.

Tugboat has finished building the preview for this pull request!
Link:

https://pr667-cz6ktvbnlnxii1v4nxdqakcdqwnbyyke.tugboat.qa

Dashboard:

https://dashboard.tugboat.qa/613236aebaa70d706897a56a


SSD tensorflow checkpoint inconsistent with the reference model

SSD 1200 tensorflow checkpoint: https://zenodo.org/record/3247091#.XQ0S4pJKhGE is inconsistent with the reference model: https://github.com/mlperf/inference/blob/master/v0.5/classification_and_detection/python/models/ssd_r34.py#L295
Batchnorm is added after each convolution in additional layers in the checkpoint, for example, ssd1200/additional_layers/conv8/conv8_bn1/beta is found in the checkpoint.
But in the reference model, there is no batchnorm added after convolution: https://github.com/mlperf/inference/blob/master/v0.5/classification_and_detection/python/models/ssd_r34.py#L295

In the checkpoint's additional_layers, there is no bias for convolutions, but bias=True in the reference code: https://github.com/mlperf/inference/blob/master/v0.5/classification_and_detection/python/models/ssd_r34.py#L295

There is bias in the checkpoint's convolution layers of Resnet-34, but there is no bias in the reference code: https://github.com/pytorch/vision/blob/ec203153095ad3d2e79fbf2865d80fe6076618fa/torchvision/models/resnet.py#L23

@jveejay to ask tao and xilinx folks to align on the model in the next week.

@christ1ne I think this is the latest resolution for this issue: https://zenodo.org/record/3262269 -- as in they updated the model and the checkpoint together so they should be aligned.
Can you verify and close?

I think the issue can be closed as the latest model is running fine. Please re-open the issue if needed.

I checked the new checkpoint https://zenodo.org/record/3262269, model architecture is still inconsistent with Pytorch reference.
Could SSD tensorflow owner share the SSD-large tensorflow training code with us? Thanks!

Adding ashish to make sure he can help us get in touch with the right folks at Xilinx.
Typed on a small screen, excuse brevity and typos.
vj.

From: wang12tao<EMAIL_ADDRESS>Sent: Tuesday, July 9, 2019 12:49 PM
To: mlperf/inference_policies
Cc: jveejay; Mention
Subject: Re: [mlperf/inference_policies] SSD tensorflow checkpoint inconsistent with the reference model (#7)
I checked the new checkpoint https://zenodo.org/record/3262269, model architecture is still inconsistent with Pytorch reference.
Could SSD tensorflow owner share the SSD-large tensorflow training code with us? Thanks!
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/mlperf/inference_policies/issues/7?email_source=notifications&email_token=ABT6DFFYP4I3LXYT2TIFDETP6S6Q5A5CNFSM4H2T52MKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZQ3OLI#issuecomment-509720365, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ABT6DFGPVHNATVJB6DXDZ3LP6S6Q5ANCNFSM4H2T52MA.


Is managing AppFabric service via services console is safe ?

There is a number of articles from knows MVPs and some TechNet articles suggest not to manage AppFabric service via services.msc console, this can leave your farm in unmanageable state and might have to rebuild the farm. This is the only article I find that is suggesting to do that. Please review.

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

ID: 59fa2ba1-01a4-d787-e7d8-7734686c55c8
Version Independent ID: dc2de12e-3433-0f4f-dee3-e42d092d6d66
Content: One of the cache hosts in the cluster is down (SharePoint Server)
Content Source: SharePoint/SharePointServer/technical-reference/one-of-the-cache-hosts-in-the-cluster-is-down.md
Product: sharepoint-server-itpro
GitHub Login: @bentoncity
Microsoft Alias: stevhord

https://docs.microsoft.com/en-us/sharepoint/administration/manage-the-distributed-cache-service
"Do not administer the AppFabric Caching Service from the Services window in Administrative Tools in Control Panel."

This is a health analyzer rule and would require a product change to be fixed.

@UmrG Did Trevor's information resolve this issue?

@scanum please close this one.
@UmrG if you'd like to see a product change, I'd recommend posting at https://sharepoint.uservoice.com/forums/330318-sharepoint-administration where it will get the attention of the engineers.


Fix typo in architecture-glossary.md

Thanks for the fix @stanleyugwu. Could you accept the CLA as the bot suggests?

Thanks for the fix @stanleyugwu. Could you accept the CLA as the bot suggests?

Yeah, I've accepted the CLA


FIX #240 - Allows Search functionality to work again after website changes

Some recent website changes seem to have affected the Search functionality.
A couple of changes are included in the fix:

UrlSearchWeb request was hitting a redirect where the js string could not be found anymore. UrlBase was however containing the string we were after, so the latter was used instead.
The js string then contained two concats instead of one, so the regexp was updated accordingly.

This change has been tested successfully by a few users from the hotfix release made from this branch.

This issue solved the search problem with this plugin for me. Please @Lacro59 make the merge and create the official 3.5.1 fix.


be louder about namespace conflicts

Seems like the right thing to do is to kill all apps involved in a namespace conflict.

Deterministic thing to do is kill both apps
Easier to notice conflicts if log files aren't being watched closely

Fixed in 284bec2


Json Log File Appender

We have a requirement of including json logs creation in production.  I realize this has been brought up before, but I felt like this was a little bit of a different take on the issue.
I was looking for a simple way of implementing this in dropwizard, which was straight forward in prior versions, it seemed like less of a hack.
Unfortunately, it feels like the shared interface added in 1415 between access and event logging made adding your own appenders feel much more like a hack.
It is still manageable, but If I want to add a new file appender that does not implement PatternLayout (e.g.,a JsonLayout) the previous changes force new implementations to ignore the LoggingFactory altogether, because we still need to meet the build() contract of the AppenderFactory because of the way DefaultLoggingFactory() is implemented.
The 2nd option is modifying LayoutFactory to implement a secondary build method, and changing some of the deeper return types from PatternLayout to Layout as downstream consumers don't actually need anything the higher level layouts offer.  See the branch where I did this here.
Unfortunately, this brings up a secondary issue...where implementers of LayoutFactory must provide implementations for AccessEvent's even if there's no desire for that functionality. I believe this is 'solved' here, and will fail fast...but it's still a hack.
In short, I'm not certain tying all future appenders hooked in through the build() of DefaultLoggingFactory to a PatternLayout for both AccessEvents and LoggingEvents leaves much wiggle room for people to cleanly extend their logging solutions.
This is all assuming I didn't miss something glaring for easily implementing the JsonLayout without ignoring the factory.

I think we should ship with a JSON logger out of the box as this is definitely becoming more common with tools like the ELK stack.  Any thoughts @ghenkes on how best to implement one and address @jamisonhyatt's concerns? /cc @dropwizard/committers

Preferably, I would like to see if it could be done as a Dropwizard module (ie, not in core, (but core work may have to be done to make it extensible?)).

@jplock the easiest way is probably to change LayoutFactory to return a Layout, rather than a PatternLayoutBase. I would have done that originally, however all use cases within dropwizard used a PatternLayout and this will require casting to a PatternLayout in buildLayout in order to set the pattern like this:
if (!Strings.isNullOrEmpty(logFormat) && formatter instanceof PatternLayout) {
    ((PatternLayout) formatter).setPattern(logFormat);
}

@jamisonhyatt out of curiosity have you got a newer solution, or which solution have you settled on for JSON logging?

I haven't done any more work on the implementation; what's in my fork is
the current state.  I was waiting for the 1.0 release, but since then I've
had other work that's a higher priority.  I think it's at least a 4-5 hours
of design and refactor away from being ready for a review.
Feel free to take it and run with it.
On Wednesday, October 5, 2016, Saem Ghani<EMAIL_ADDRESS>wrote:

@jamisonhyatt https://github.com/jamisonhyatt out of curiosity have you
got a newer solution, or which solution have you settled on for JSON
logging?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dropwizard/dropwizard/issues/1451#issuecomment-251817361,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFJZITtmPxotNZsdcbfRPUeSTg0uTAGqks5qxCO5gaJpZM4HVAMT
.

--
-Jamison-

I have taken JamisonHyatt's branch as a starting point and added support for ILoggingEvent and IAccessLog: https://github.com/dropwizard/dropwizard/compare/master...jamisonhyatt:AddJsonFileAppender?expand=1
I have created the following PR: https://github.com/dropwizard/dropwizard/pull/2180
Please take a look

would anyone object to a configuration option that would flatten the mdc into the root object?

would anyone object to a config option that flattens the MDC into the root object? i opened a PR (#2293) that would enable this. it's not a big change.

Closed via #2232.


URL error!

Not valid url in main.py: https://github.com/Arthur151/ROMP/releases/download/V2.0/smpl_packed_info.pth

Hi, @xangs ,
Thanks for your bug report!!
Due to the license problem, we no longer provide SMPL file.
Instead, please follow the instrcution
https://github.com/Arthur151/ROMP/tree/master/simple_romp#installation
to prepare the SMPL model file, including smpl_packed_info.pth
For now, you will have to run
cd simple_romp
sh reinstall.sh

to get the latest simple-romp. I will update the pip resource later.

Thanks

Please refer to https://github.com/Arthur151/ROMP/blob/master/simple_romp/README.md
Now we have:
pip install simple-romp==1.1.1


Add flag to load env vars from file when building a deployment

We usually need to export env vars befores building an agent deployment. For the last months 90% of the problems I've faced while running agents had to do with problems in those vars: remember which ones to export, double checking their values are correct... Furthermore, when switching between services of different deployment types this can lead to frction in the development. Having a flag (domething like --env-file) that lets us specify a file where we store some vars would be easier.

I 100% agree with this.
Apply environment variables should be default.
this would save a load of time from my side as well, and you could create different env var files for different deployments.


Add ClickableWorkspaces to exposed modules

Description
XMonad.Util.ClickableWorkspaces was added in #364 but never listed as an exposed module in xmonad-contrib.cabal, so any attempt to use it resulted in a compilation error.
Fix this by adding it to the list of exposed modules .
Checklist

[x] I've read CONTRIBUTING.md

[x] I tested my changes with xmonad-testing (see commits)

[ ] I updated the CHANGES.md file

[ ] I updated the XMonad.Doc.Extending file (if appropriate)

Thanks for catching this!


Issue with the structure of document CVE-2023-37276

Hello,
While using the Skjold tool for security auditing in a Python project, I encountered an issue with the CVE-2023-37276 document. It seems that the structure of the document is not in accordance with the expected schema.
According to what the Skjold tool expects and, as far as I understand, by the OSV schema, the "affected" key should be a list. However, in the CVE-2023-37276 document, this key is appearing as an object.
Here is an example of the document in question:
id: PYSEC-0000-CVE-2023-37276
summary: "aiohttp.web.Application vulnerable to HTTP request smuggling via llhttp HTTP request parser"
# ...
affected:
  package:
    name: aiohttp
    ecosystem: PyPI
    purl: pkg:pypi/aiohttp
  ranges:
  - type: ECOSYSTEM
    events:
    - introduced: '0'
    - last_affected: '3.8.4'
# ...

The "affected" key should be a list, as follows:
affected:
- package:
    name: aiohttp
    ecosystem: PyPI
    purl: pkg:pypi/aiohttp
  ranges:
  - type: ECOSYSTEM
    events:
    - introduced: '0'
    - last_affected: '3.8.4'

This error is causing Skjold tool execution to fail. I would appreciate if you could verify whether this is an issue with the OSV database or if the Skjold tool is misinterpreting the schema.
Thank you for your attention.
@sethmlarson @oliverchang

Yeah sorry about that, it got introduced during a manual triage of a vuln and fixed here: https://github.com/pypa/advisory-database/commit/87b08dcf17a46beaae1b67c99548f987218a0cef I was seeing if there's an easy way we can detect poorly formatted submissions so this doesn't happen in the future.

Fixed by https://github.com/pypa/advisory-database/pull/135.

Awesome! Thanks!!


Add customisable gender

Context:
https://github.com/OpenSlides/openslides-client/issues/3098
https://github.com/OpenSlides/openslides-client/pull/3101
https://github.com/OpenSlides/openslides-backend/issues/2170
Desired behaviour:
We want to make it possible to add/update/delete new genders while the old ones cannot be changed or deleted
This feature should get a new view
Navigating to the view > account-list > top right three dot menu > "Edit gender" please use a provisional icon around gender for now
Every account admin and above should be allowed to edit gender, navigate to the view, and see the option in the three dot menu

The wanted icon is "face"


fix: terminal env not inject

Types

[x] 🐛 Bug Fixes

Background or solution
Changelog
fix inject env to terminal

Codecov Report

Merging #449 (2011aaa) into main (889f1dd) will decrease coverage by 0.00%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #449      +/-   ##
==========================================
- Coverage   59.20%   59.20%   -0.01%
==========================================
  Files        1196     1196
  Lines       73568    73567       -1
  Branches    15219    15218       -1
==========================================
- Hits        43554    43553       -1
+ Misses      27351    27350       -1
- Partials     2663     2664       +1

Impacted Files
Coverage Δ

...kages/terminal-next/src/browser/terminal.client.ts
74.49% <100.00%> (+0.49%)
:arrow_up:

packages/monaco/src/browser/schema-registry.ts
68.88% <0.00%> (-2.23%)
:arrow_down:

...kages/theme/src/browser/workbench.theme.service.ts
70.32% <0.00%> (-0.90%)
:arrow_down:

...erences/src/browser/preference-settings.service.ts
79.16% <0.00%> (-0.70%)
:arrow_down:

...ages/file-service/src/node/file-service-watcher.ts
72.88% <0.00%> (+1.69%)
:arrow_up:

Continue to review full report at Codecov.

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

@bytemain 冲突了

@bytemain 冲突了

解决了


denormalize should be memoized, changing only when object has actually changed

In my mind, denormalizr is most useful when passing large nested objects to a component using connect. But currently it always returns a new object, so the component re-renders on every action.
denormalize should always return the same (strictly equal) result unless:

The root object is different
Any of the associations in the schema are different

I believe this could be accomplished fairly simply using a cache of denormalized resources.

Yes, this is needed 👍 I'm not a champion in caching techniques, do you have a suggestion about how to implement it?

I can maybe take a look this weekend.

Currently I'm combining denormalizr with reselect

Hello,
I've currently forked and achieved memoization with denormalizr. I will push it soon on my repo, but I was unable to make it work with circular dependency ; I don't think it is possible for technical reasons on how the cache diff is calculated.
Is it a concern for you ? Dropping circular dependencies would introduce a breaking change.
But memoization is a great plus.

Can't you use reselect? I didn't test it specifically, but I'm pretty sure that it handles circular dependencies:
import { createSelector } from 'reselect'
import { denormalize } from 'denormalizr'

const getChallenge = createSelector(
  getEntitiesState,
  getChallengeState,
  (entities, challenge) => denormalize(challenge, entities, challengeSchema)
)

@diegohaz With cache, you can achieve 2 things : recompute only when the concerned dependencies have been changed, and recompute only the part of the denormalized entity which has changed.
reselect will achieve first poorly in this use-case : it will actually recompute when any of the entities in your app changed, which essentially means every other action, and can't achieve second (as this is the job of the denormalize function).
For why it is important for performance to only recompute the part that has changed, let's imagine a Schema :
const Book = new Schema('books')
const Author = new Schema('authors')
const Review = new Schema('reviews')

Book.define({
  author: Author,
  reviews: arrayOf(Review),
})

With the cache, this will work:
let response = {
  id: 1,
  title: 'Game of Thrones',
  author: {
    id: 1,
    name: 'Georges RR Martin'
  },
  reviews: [{
    id: 1,
    content: 'Great book',
  }]
}

let normalized = normalize(response, Book)

let denormalized1 = denormalize(normalized.result, normalized.entities, Book)
let denormalized2 = denormalize(normalized.result, normalized.entities, Book)

assert(denormalized1 === denormalized2
  && denormalized1.author === denormalized2.author
  && denormalized1.reviews === denormalized2.reviews
 && denormalized1.reviews[0] === denormalized2.reviews[0])

// We change only the review entity with id 1
normalized.entities.reviews[1] = {
   ...normalized.entities.reviews[1],
  content: 'I changed my mind, this sucks !',
}

let denormalized3 = denormalize(normalized.result, normalized.entities, Book)

assert(denormalized2 !== denormalized3
  && denormalized2.reviews !== denormalized3.reviews)
// ... and author object gets unchanged in the denormalized response
assert(denormalized2.author === denormalized3.author)

This essentially means that we will only trigger re-render on our React component and all his children that might exploit some part of the nested response only if the denormalized response, or the part, truly changed.

@yachaka thanks for caring about this!
I'm ok for disabling circular dependencies if case memoization is enabled. I'm thinking to export another function enabling memoization, which turns circular dependencies off. Something like:
import { memoizedDenormalize } from 'denormalizr';
const denormalized = memoizedDenormalize(normalized.result, normalized.entities, Book);

memoizedDenormalize would be a shortcut for a fourth options argument for denormalize, so the code above would be the same as:
import denormalize from 'denormalizr';
const denormalized = denormalize(normalized.result, normalized.entities, Book, { memoize: true });

+1 the fourth argument is very elegant
On Sun, Sep 25, 2016 at 02:52 Giampaolo Bellavite<EMAIL_ADDRESS>wrote:

@yachaka https://github.com/yachaka thanks for caring about this!
I'm ok for disabling circular dependencies if case memoization is enabled.
I'm thinking to export another function enabling memoization, which turns
circular dependencies off. Something like:
import { memoizedDenormalize } from 'denormalizr';const denormalized = memoizedDenormalize(normalized.result, normalized.entities, Book);
memoizedDenormalize would be a shortcut for a fourth options argument for
denormalize, so the code above would be the same as:
import denormalize from 'denormalizr';const denormalized = denormalize(normalized.result, normalized.entities, Book, { memoize: true });
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gpbl/denormalizr/issues/10#issuecomment-249404436,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC7Sk3yKLHpJDQK-ammaZybu2elOS7pCks5qtgwugaJpZM4IxIW1
.

--
Haz

The solution by @yachaka in #20 works, but it needs some refactoring to keep the code more maintainable.
I wonder if it makes sense supporting external cache libraries such as https://github.com/isaacs/node-lru-cache, thus implementing a similar API for an internal cache utility.
I'm marking this issue as "breaking change" because the export would work differently – maybe once memoization is ready we can release a v1.0 🎉

@gpbl Shouldn't it be considered a new feature rather than a breaking change ? The old API is fully supported and existing code will not break.

Shouldn't it be considered a new feature rather than a breaking change

@yachaka sure! I was thinking to add a new options argument:
denormalize(entity, entities, schema, { memoize = false })

yet now the fourth argument is a bag (which shouldn't be there, actually). Anyway, we are still in the v0. realms so I wouldn't care so much about this :)


RDeque needs popRange()

RList already got its subList() method, but RDeque still could not pop multiple elements at one time.
This limits a lot RDeque's usage, and I have to use RList instead.
Redis realization[python]:
import redis
client = redis.Redis()

def batch_lpop(key, n):
    p = client.pipeline()
    p.lrange(key, 0, n - 1)
    p.ltrim(key, n, -1)
    data = p.execute()
    return data

batch_lpop('test_pipeline', 20)

You can use RDeque.poll(int limit) method instead.

Many thanks. It seems that I use a too much outdated version of Redisson.


Code clean-up

A few code improvements made while I was reading code to understand why some of my API were not found (more on that in a later issue/PR)
Code style is always subjective and personal, feel free to ignore and close the PR if it doesn't feel right :)

Looks good to me. And I learned a couple of syntax. :)
Thank you.
And I'm really curious about your problem on API discovery.
On a side note, please be advice that I'll be on holidays for the whole September month. I might be curious enough to check any message on my phone. But no possibility to release anything during this time. Do you need a release of the current state @murdos ? Tomorrow is my last window for it before October.

@kbuntrock : Thanks for the notice and your offer :)
I've found multiple potential issues that prevent me from using this plugin right now (notably https://github.com/kbuntrock/openapi-maven-plugin/pull/165), so a new release is not needed for the moment. but I'll continue working on it during your holidays.
At least I know there's no hurry, I've the whole month to do that.
Enjoy your holidays! :smile:


Windows: Using a Symbolic Link to download clips into a Vault that is not under Downloads/

In Options under "Downloads/" I entered
_MarkDownload
representing ...
C:\Users\ichmo\Downloads\_MarkDownload
I want to get my clips automatically into my Vault:
C:\Users\ichmo\OneDrive\Documents\Obsidian\O_ichmoimeyo\z_capture\markdownload
\\\\\\\\\\\\\\\\
Symbolic Link in a nutshell ...
mklink /J Link Target
mklink /J C:\LinkToFolder C:\Users\Name\OriginalFolder
\\\\\\\\\\\\\\\\
I opened a Command Prompt window as Administrator & entered:
mklink /J C:\Users\ichmo\OneDrive\Documents\Obsidian\O_ichmoimeyo\z_capture\markdownload C:\Users\ichmo\Downloads\_MarkDownload
Command Prompt window output:
C:\Users\ichmo>mklink /J C:\Users\ichmo\OneDrive\Documents\Obsidian\O_ichmoimeyo\z_capture\markdownload C:\Users\ichmo\Downloads\_MarkDownload
Junction created for C:\Users\ichmo\OneDrive\Documents\Obsidian\O_ichmoimeyo\z_capture\markdownload <<===>> C:\Users\ichmo\Downloads\_MarkDownload

It is working very nicely thanks to How-To Geek:
The Complete Guide to Creating Symbolic Links (aka Symlinks) on Windows
PS: CAUTION - deleting files in either folder deletes it in the other.
I especially will try to remember to not delete files inadvertently in C:\Users\ichmo\Downloads\_MarkDownload

Nice. You could also just run a script to move the files to the Obsidian folder, and schedule it with Task Scheduler.

@fmeres - thanks, good idea for doing things in bulk.
The main point for me is that once set up, I don't have to deal with the file explorer.
When using Obsidian, anything I clip with MarkDownload appears in my capture folder(z_capture / markdownload) where I can immediately process it further.

In Options under "Downloads/" I entered _MarkDownload
representing ... C:\Users\ichmo\Downloads_MarkDownload
I want to get my clips automatically into my Vault: C:\Users\ichmo\OneDrive\Documents\Obsidian\O_ichmoimeyo\z_capture\markdownload
\\\\\\\\
Symbolic Link in a nutshell ... mklink /J Link Target mklink /J C:\LinkToFolder C:\Users\Name\OriginalFolder
\\\\\\\\
I opened a Command Prompt window as Administrator & entered:
mklink /J C:\Users\ichmo\OneDrive\Documents\Obsidian\O_ichmoimeyo\z_capture\markdownload C:\Users\ichmo\Downloads\_MarkDownload
Command Prompt window output:
C:\Users\ichmo>mklink /J C:\Users\ichmo\OneDrive\Documents\Obsidian\O_ichmoimeyo\z_capture\markdownload C:\Users\ichmo\Downloads\_MarkDownload
Junction created for C:\Users\ichmo\OneDrive\Documents\Obsidian\O_ichmoimeyo\z_capture\markdownload <<===>> C:\Users\ichmo\Downloads\_MarkDownload

It is working very nicely thanks to How-To Geek: The Complete Guide to Creating Symbolic Links (aka Symlinks) on Windows
PS: CAUTION - deleting files in either folder deletes it in the other. I especially will try to remember to not delete files inadvertently in C:\Users\ichmo\Downloads_MarkDownload

closed in error
The symbolic link topic was previously well answered ...
https://forum.obsidian.md/t/markdownload-markdown-web-clipper/173/136

thanks to CharisLee ->  https://github.com/deathau/markdownload/issues/208#issuecomment-1435833395 got it working now without a symbolic link.


Remove #[inline] from function prototypes

This re-adopts the way used before https://github.com/taiki-e/easy-ext/commit/3234d3db4d62b958ab45e1f9005c2b7fb27c37b1.
Previously only clippy::inline_fn_without_body warned about this, now unused_attributes also warns about this.
Fixes #21

bors r+


[Container] Allow disableGutters to support breakpoints

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
The ability to add breakpoints when the show/hide the gutters.
Examples 🌈
<Container maxWidth={"xl"} disableGutters={{ xs: true, xl: false }}>

Motivation 🔦
No response

Hi, thanks for your suggestion. Do you want to give it a try? I can help :)
There are utils you can use in packages/mui-system/src/breakpoints.js. For example, in order to handle columns prop in Grid, computeBreakpointsBase, resolveBreakpointValues and handleBreakpoints are used. handleBreakpoints outputs css object including media query.

Hi @hbjORbj , Are you aware if any action was ever taken relating to this issue? If not, I'd love to tackle it with your help.

Adding to see if this was ever implemented. I think it would be useful on all MUI props, especially the ones inaccessible in the SX prop


Add qy-h00.md

Codecov Report

Merging #232 (6425a9d) into master (4ee2480) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #232   +/-   ##
=========================================
  Coverage     69.05%   69.05%
  Complexity      645      645
=========================================
  Files            96       96
  Lines          2133     2133
  Branches        270      270
=========================================
  Hits           1473     1473
  Misses          561      561
  Partials         99       99

Continue to review full report at Codecov.

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


chore: Update controller-tools

Description
Previously used controller-tools 0.11.3 might have issues with latest Golang release.
Changes proposed in this pull request (what was done and why):

Update controller-tools to 0.14.0
Updated table-gen
Improve wording in CRD description

Changes refer to particular issues, PRs or documents:

https://github.com/kubernetes-sigs/controller-tools/issues/888

Traceability

[ ] The PR is linked to a GitHub issue.
[ ] New features have a milestone set.
[ ] New features have defined acceptance criteria in a corresponding GitHub Issue, and all criteria are satisfied with this PR.
[ ] The corresponding GitHub issue has a respective area and kind label.
[ ] The follow-up issues (if any) are linked in the Related Issues section.
[ ] Adjusted the documentation if the change is user-facing.
[ ] The feature is unit-tested
[ ] The feature is e2e-tested

/hold

New controller-gen introduces new-lines in CRD docs, which breaks our generated Markdown tables. Fix in table-gen is required first.

/test pull-telemetry-manager-build

/unhold


Purifying Factory Not Accepting Automated Inputs

I am having an issue with the Purifying Factory not accepting items from any form of automation. I've tested it with a Logistical Sorter/Transporters, as well as as a hopper. I am currently using version <IP_ADDRESS>4 for Minecraft 1.10.2

did you configure the sided configuration for input? And if so, can you take a couple screenshots showing your setup?

I managed to figure out what the issue was. The purifying factory requires the gas to be input before it will allow any ores to be added in automatically. I didn't realize this, and tried to put the ores in first


[CSSimplify] Account for tuple splat when resolving closure parameters

SE-0110 allows tuple slat between function types. The solver needs to
account for that when trying to infer parameter types from context
while resolving a closure in order to propagate types and speed up
type-checking.
Resolves: https://github.com/apple/swift/issues/62390

@swift-ci please test source compatibility


updating outdated plugin

Proposed changes

As people are trying to search flocker but flocker has shutdown . So you need to update that
Related issues (optional)

#2897

Thanks, @frankgreco :)


Remove Unnecessary Bullet Point Marker

What does this PR do?
Removes bullet point markers on migrations page.
Test Plan
Manual.
Before -

After -

Related PRs and Issues
N/A.
Have you read the Contributing Guidelines on issues?
Yes.

@ItzNotABug instead of changing the component wrapper to a div, we can change line 47 <div class="u-flex u-flex-vertical u-gap-24"> to the FormList component, and remove other div wrappers on inputs

Done!


2.9.0 includes a huge libvk_swiftshader.so

Hello!
Actual behavior:
libvk_swiftshader.so in 2.9.0 is 120Mb.
Expected behavior:
libvk_swiftshader.so in 2.8.4 is 4Mb.
How to reproduce it (as minimally and precisely as possible):
Look at the files.
I have not yet figured out why the difference, but I thought @thedoublejay you might know quickly. :)
Anything else we need to know?
Unrelated but is it acceptable to strip the binaries? I took over maintenance of this for my distro it and the previous maintainer prevented stripping, so I'm wondering if there's a reason.
Thanks!

Ok you fixed it in 2.9.1, thanks!

Hey @John-Gee I'm not familiar with libvk_swiftshader.so but it might be from Electron library.

@thedoublejay
Yeah it's from Chromium, but you fixed it with .1 anyway.
How about the stripping part for the whole build though?


Future compatibility with Angular v8?

Describe the bug
Package "codelyzer" has an incompatible peer dependency to "@angular/common" (requires ">=2.3.1 <7.0.0 || >6.0.0-beta <7.0.0" (extended), would install "8.2.12")
...

[ ] MaterialDesignFrameworkModule — Material Design
[ ] Bootstrap3FrameworkModule — Bootstrap 3
[x] Bootstrap4FrameworkModule — Bootstrap 4
[ ] NoFrameworkModule — plain HTML
[ ] Other (please specify below)

I am struggling with incompatibilities  on updating this demo https://stackblitz.com/edit/angular6-json-schema-form to Angular v8.
To Reproduce

Clone and run this demo https://stackblitz.com/edit/angular6-json-schema-form on Angular v7
Update Angular (@angular/core, @angular/cli, @angular/compiler-cli, etc.) to last version (v8)
ng serve

Expected behavior
Compiled succesfully.

The demo in Stackblitz is working fine. If you're using Angularv8 you need to use the version ^8.0.0 of this library.


Make blobLines count from end of BODY

Is your feature request related to a problem? Please describe.
Often when I use the BODY syntax I find myself writing a full paragraph to properly describe the reasoning behind the TODO, so when the app creates an issue from it the blob is just the TODO and the BODY and all the relevant code has been pushed out of the 6 lines.
Describe the solution you'd like
I'd like blobLines to take the number of BODY lines into account.
Describe alternatives you've considered
I could just increase blobLines, but most of the time TODO+5 lines is perfectly fine, and adding more lines than that would be distracting at best.
Additional context
Here's an example of a blob entirely taken up by a long BODY

This is still relevant.

Still relevant afaik

Hi 👋  I've decided to shut down this project - please see https://github.com/JasonEtco/todo/discussions/293 for more information 🙏


Uncaught SyntaxError: Missing initializer in const declaration

Expected Behavior
Working
Current Behavior
After clinic as run the html report is broken with error.
14030.clinic-doctor.html:7476 Uncaught SyntaxError: Missing initializer in const declaration
This error happen with doctor and with bubbleproof.

Steps to Reproduce (for bugs)

clinic doctor -- node yourscript
ctrl + c
open the report in chrome
error in console

N.B: also broken on your website :/
Sample upload
This has nothing to do with report, it's working once all js errors are fixed
Environment

Clinic.js version: 6.0.0

Node.js version:12.16.1

Browser name and version: Chrome Version 83.0.4103.61 (Official Build) (64-bit)

Operating system and version: osx catalina 10.15.5

@bodinsamuel Came across the same issue.
I copied all scripts inside the last script tag in the html, found const EventEmitter,， and replaced them all with const EventEmitter=require('events'),. After that everything was fine.
I guess this is a babel issue but I cannot pinpoint where the problem is. Anyways, hope this helps.

Will investigate, thank you! :-)

yep I can confirm, this is the same issue happening, I saw one with let HtmlContent;require('./content-html.js);.
The actual code seems fine so I wonder what happened in the compilation

I got the same issue but no solution. Any updates ?

Should have a fix in by Monday end of day.

Hey 👋
Is this issue still being looked into? Happy to help where I can but not to familiar with the setup here. I can work around the doctor report with the suggestions above however, unable to resolve the same issues with my bubbleprof out put.
Any suggestions would be much appreciated :)
Tom

What version are you using? I believe it should have been fixed in the latest version.

hey @TomVance  - can you confirm which versions are installed on your local environment? - specifically the @nearform/clinic-common dependency.
If you run the command npm list @nearform/clinic-common -g you should get something like the output below.

If you somehow have a previous version installed, can you try npm install clinic -g again to update to the latest?

Apologies for my delay in getting back to you:
/Users/thomasvance/.nodenv/versions/14.3.0/lib
└─┬<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ └──<EMAIL_ADDRESS>  ├─┬<EMAIL_ADDRESS>  │ └──<EMAIL_ADDRESS>deduped
  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>deduped

Thank you @TomVance  - that looks as it should be
Can you confirm the error you are getting in the console after running a fresh clinic bubbleprof -- node yourscript?

According to all reports and testing this is now working as expected. 🎉  The minor version bump fixed the dependencies.


[Bug] Deleted shelf reappears in the library

The deleted shelf won't be removed from the database, even though the api request is processed.

Solved with the last commit. Issue was caused by the shelfList field in the library entity and the fix was removing the shelf from the library manually in the delete controller.


Feature Request: Save filter selection on scrum backlog screen

reproduction steps

select a filter on the scrum backlog screen
switch over to board/epics/issues etc.
switch back to the scrum backlog screen

expected behavior
the selected filters from before are still selected
observed behavior
no filters are selected

For now "primary screens" - those which you navigate using bottom and "More" menu - don't preserve their state when you're navigating between them. So if you navigate, for example, from "Scrum" screen to task screen, edit this task and then return - the state will be preserved (only specific task item would be updated). But, as you've noticed, that's not the case when you're navigating, for example, from "Scrum" screen to "Issues" screen. This means that we would need to support state preservation between those "primary screens" in general. But then the information can become outdated on these screens. It's possible to implement manual refreshing (like swipe-to-refresh), but I don't think that's a good idea since users would forget about this and inevitably face with some strange errors due to desynchronisation. Silent refreshing is much more tricky and at this moment I don't have any clear ideas how to implement this to both refresh all the information and preserve the state. If you have any suggestions regarding implementation - either from the user side (UI/UX part) or from the technical side (how this might work under the hood) - let's discuss it

introduction/reply

then the information on these screens can become outdated

this is an edge case scenario, like if a user has a filter selected and the project gets updated and that filter is deleted. this should be considered as a requirement for implementation, but it by no means prevents implementing the functionality.
the overall idea idea would be to keep the selected filters saved in persistent data somewhere, and when refreshing a project re-applying the saved filters, so
where would it make sense to store this data?
i think settings
https://github.com/EugeneTheDev/TaigaMobile/blob/0f5dbaf7ef3cbb3ce9bda1e3cd7688692127b536/app/src/main/kotlin/io/eugenethedev/taigamobile/state/Settings.kt#L8
is the best option, then it can be pulled it in like
https://github.com/EugeneTheDev/TaigaMobile/blob/cd6f44493065d8a8df03f6f4ef32790d825ce7e6/app/src/main/kotlin/io/eugenethedev/taigamobile/ui/screens/main/MainViewModel.kt#L12
and read from in all the places activeFilters gets reset
where are all the places activeFilters gets reset?
https://github.com/EugeneTheDev/TaigaMobile/blob/2ea06035c92a0bc72723cf2e01a805be208606af/app/src/main/kotlin/io/eugenethedev/taigamobile/ui/screens/scrum/ScrumScreen.kt#L79
https://github.com/EugeneTheDev/TaigaMobile/blob/2ea06035c92a0bc72723cf2e01a805be208606af/app/src/main/kotlin/io/eugenethedev/taigamobile/ui/screens/scrum/ScrumScreen.kt#L55
https://github.com/EugeneTheDev/TaigaMobile/blob/0f5dbaf7ef3cbb3ce9bda1e3cd7688692127b536/app/src/main/kotlin/io/eugenethedev/taigamobile/ui/screens/scrum/ScrumViewModel.kt#L50
https://github.com/EugeneTheDev/TaigaMobile/blob/0f5dbaf7ef3cbb3ce9bda1e3cd7688692127b536/app/src/main/kotlin/io/eugenethedev/taigamobile/ui/screens/scrum/ScrumViewModel.kt#L86
i didn't look much outside of ScrumViewModel, but it seems like this is where all the resetting happens.
how can we ensure the data is available to us at those times?
https://github.com/EugeneTheDev/TaigaMobile/blob/0f5dbaf7ef3cbb3ce9bda1e3cd7688692127b536/app/src/main/kotlin/io/eugenethedev/taigamobile/ui/screens/scrum/ScrumViewModel.kt#L29
is already there, if Settings gets pulled in the same way it seems like it should work
what happens when activeFilters are set?
https://github.com/EugeneTheDev/TaigaMobile/blob/0f5dbaf7ef3cbb3ce9bda1e3cd7688692127b536/app/src/main/kotlin/io/eugenethedev/taigamobile/ui/screens/scrum/ScrumViewModel.kt#L60-L62
where is that data living currently?
looks like right on the model and that's it?
so how do we save it to settings instead?
https://github.com/EugeneTheDev/TaigaMobile/blob/0f5dbaf7ef3cbb3ce9bda1e3cd7688692127b536/app/src/main/kotlin/io/eugenethedev/taigamobile/ui/screens/settings/SettingsViewModel.kt#L37-L39
https://github.com/EugeneTheDev/TaigaMobile/blob/0f5dbaf7ef3cbb3ce9bda1e3cd7688692127b536/app/src/main/kotlin/io/eugenethedev/taigamobile/state/Settings.kt#L13-L16
following that pattern seems like a good plan
so so far we have

[x] where to store the data
[x] a pattern to follow for storing data there
[ ] a way to ensure active filters are stored per-project

how do we store the activeFilters per project?
depeding on how unique the ids are on the filter interface, it may not matter what project is loaded, and it could just be a matter of saving each active filter id to settings
https://github.com/EugeneTheDev/TaigaMobile/blob/ab6f371ab7ea189d671574b8306f2c45ad76b8ea/app/src/main/kotlin/io/eugenethedev/taigamobile/domain/entities/Filters.kt#L36-L37
if that's not the case, then probably using a combo of filter id and project id
conclusion
this definitely isn't everything, but it seems like a decent place to start for trying to make this work.

made a wip pr, next thing to figure out is how to use the saved ids in settings to set activeFilters when filters are loaded


[Windows] Add quotes only to the command line arguments with special characters.

Fixes #38803

For the reference, we do a similar quoting of all arguments in OS_Unix that also creates some restrictions: #37440 #37291.

Might use a similar fix, but it doesn't necessarily have to be in this PR as the issues are different on each OS.

It's highly unlikely that list of the special character and quoting rules are the same on Linux (it might be different for each shell). This fix definitely should not be reused as is, without prior investigation.

Thanks!

Cherry-picked for 3.2.2.


Add new scheduler

A scheduler that creates 30 or 30+ events based on the number of members in any teams roster. Here each event is 24hr long and has different user assigned to every event.

**Use python3 for setup


Is C++ required?

Since Luna can do pointer arithmetic and should be pretty fast on its own, why not implement the library in pure Luna, without using C?

TLDR: in the longer-term we are going to migrate C++ parts to Luna.
Long answer:
I think that C++ parts could be expressed in Luna right now but it wouldn't work very well.
Luna is still a work-in-progress in some areas. In particular performance and optimization capabilities are still being actively developed — Luna is not "that fast" yet. When it comes to DataFrames, being able to quickly process huge amounts of data is crucial. As things stand right now, it makes sense to implement low-level primitives and operations on them in C++ and to consume them from Luna.
Such approach will allow Luna users to use Dataframes to quickly process and visualize their data. For many users this will be enough — being able to use in Luna libraries like Dataframes and being able to implement them in pure Luna are separate use-cases, and since we can deliver the first one, we don't want to wait for the second one. At this point we prioritize data-processing and visualization capabilities of Luna over being able to implement low-level code (i.e. rivalling C and C++).
Implementing Dataframes needs much more than just having support for pointer arithmetics. Providing highly performant primitives also requires control over data layout in memory. Many defaults that Luna currently assumes (like lazy evaluation, boxed values, garbage collecting, being interpreted rather than compiled, etc.) are often not best suited for implementing low-level code. That's common case for many high-level languages and is also the reason why C and C++ remain still so prevalent. They are just tools perfectly suited for the low-level domain. I don't think that taking advantage of them is wrong — that's what's Luna's FFI support is for.
This library is still pretty much at the design space exploration stage. The goal is to deliver well-performing low-level pieces and see how they perform, and work on integration with Luna Studio (e.g. data visualizations).  Having the initial implementation in C++ will provide a good benchmark for us. In the long term we want to move away from C++ and use Luna as much as reasonably possible. My belief is that it is best to first write the performant code (be it C++ or anything) and then gradually move it to Luna while preserving the speed. That will also allow us to catch design and architectural issues early.