Cameras not changing for scenes they're enabled in

At the moment I have two different cameras, a menu cam which is enabled in menu and multiplayerMenu scenes.
I have a second camera play cam which is enabled in all other scenes except for the menu scenes.
The issue is that menu cam is being used in every scene, it doesn't switch when entering a new scene. Is this how it's supposed to behave?

Can you Zip and attach your Camera2 config folder?

Camera2.zip

I experienced this behavior in 0.3.6 and 0.3.10 fwiw

I am unable to replicate this. Once I go into a song the menu cam is gone for me, leaving me with just the smaller play cam. Do you think you could create a video showcasing this?

actually no problem, i have a video already! and will do

This is with the config i sent to you, pardon my frustrated yell haha
https://user-images.githubusercontent.com/39172279/112220599-d49cd700-8bfc-11eb-98c8-e11d149d8fb1.mp4

2<IP_ADDRESS>.53.29.log

Ah yes theres your issue
[CRITICAL @ 17:01:37 | UnityEngine] MissingMethodException: EnvironmentEffectsFilterPreset PlayerSpecificSettings.get_environmentEffectsFilterPreset()
[CRITICAL @ 17:01:37 | UnityEngine] System.Runtime.CompilerServices.AsyncVoidMethodBuilder.Start[TStateMachine] (TStateMachine& stateMachine) (at <9577ac7a62ef43179789031239ba8798>:0)
[CRITICAL @ 17:01:37 | UnityEngine] BeatSaberHTTPStatus.Plugin.HandleSongStart () (at <f1f629093a754a878837db29c15f6c7f>:0)
[CRITICAL @ 17:01:37 | UnityEngine] BeatSaberHTTPStatus.Plugin.OnActiveSceneChanged (UnityEngine.SceneManagement.Scene oldScene, UnityEngine.SceneManagement.Scene newScene) (at <f1f629093a754a878837db29c15f6c7f>:0)
[CRITICAL @ 17:01:37 | UnityEngine] UnityEngine.SceneManagement.SceneManager.Internal_ActiveSceneChanged (UnityEngine.SceneManagement.Scene previousActiveScene, UnityEngine.SceneManagement.Scene newActiveScene) (at <12e76cd50cc64cf19e759e981cb725af>:0)
[CRITICAL @ 17:01:37 | UnityEngine] UnityEngine.SceneManagement.SceneManager:SetActiveScene(Scene)
[CRITICAL @ 17:01:37 | UnityEngine] <ScenesTransitionCoroutine>d__36:MoveNext()
[CRITICAL @ 17:01:37 | UnityEngine] UnityEngine.SetupCoroutine:InvokeMoveNext(IEnumerator, IntPtr)

Uninstall / Update your HTTPStatus, its causing an error that prevents Cam2 from receiving the ccene switch event.

OK!!! Thank you!

Also a little FYI: With how scenes work, you only need to enable your menu cam for "Menu", and your play fp cam for "Playing", Playing360 will look at Playing when it is empty, MultiplayerMenu will look at Menu, etc.

Thank you, yeah I enabled it for all the unnecessary for testing purposes as I was trying to debug, thanks so much for your help!!!


Problem of caculate_base_base_shift

Hello. Here is Jeremy Quo again.
I wanna ask the question of how to calculate the best base shift.
I read carefully the function below,
https://github.com/hiruna72/squigualiser/blob/2389379fa8898bf78fd695b3bddac982213ea951/src/plot_utils.py#L194-L220
And now the function is as below,
https://github.com/hiruna72/squigualiser/blob/2f24ff877f12c70c17cfca476201aa921e150c04/src/calculate_offsets.py#L112-L183
Here are my questions,

Is the number of best base shifts different in each read? Some are -3 and others are 0,-1,-2...
kmer_length is fixed in each sequencing data (such as DNA R941 is 6), so why there's a loop to calculate every kmer_length?
What is the input param y, is it all signals or just signals slice covered base-calling slice (signals[start_index:end_index])

Hello @JeremyQuo,
You are referring to an outdated code. The latest is here on dev branch. https://github.com/hiruna72/squigualiser/blob/2f24ff877f12c70c17cfca476201aa921e150c04/src/calculate_offsets.py#L260
Could you please go throgh it an update the questions. Sorry for any inconvenience.
Generally I can answer,

Depending on the probabilistic behaviour of the basecaller, we can expect different base shifts for different reads. However, the majority of the reads of a given dataset should have the same base shift.
For better accuracy I go though all possible kmers. It is not a requirement. But it serves a purpose. When you increment the kmer length by 1 and do the calculations again to find the base shift; the newly caculated baseshift should be equal to the previous base shift from the previous iteration + 1. I validate this argument at this end https://github.com/hiruna72/squigualiser/blob/2f24ff877f12c70c17cfca476201aa921e150c04/src/calculate_offsets.py#L271

I just updated the function, you know that I am still improving my tool called nanoCEM to adapt f5c. My reviewer recommended finding the most contributing base in this link, and then I found the calculate_base_shift function.
Now I realize that the function is updated. So, forget my previous question.
Is there any function available to help me find the best base shift per read and find the most contributing base?
During the development of nanoCEM, you and your group provided invaluable assistance and answered numerous questions. May I include your group in the acknowledgments section?

Hello @JeremyQuo,
Thank you for acknowledging us!

Any event alignment that used a kmer model will have the same most contributing base as the kmer model.

The move tables will have different most contributing bases that depend on the basecalling model.

We have listed some such most contributing bases here. https://github.com/hiruna72/squigualiser/blob/main/docs/profiles.md

You can get different alignments outputs from different alignment tools and use squigualiser plot tracks tool to see if the bases align to each other across the alignments.
dna_r10.4.1_e8.2_400bps_sup.cfg_evligned_forward_and_realign_forward.zip

To further read and incorporate any code to nanoCEM I suggest you to read our preprint's Supplementary Note 3. https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>1111v2

Also Uncalled4 has a different way to represent the most contributing base using heat maps. https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>3511v1


Create sideeffects.md

Documentation on expected side-effects that SQLx requires for Database version management

This seems like it belongs in the documentation for migrations.

@abonander I have moved to SQLx-CLI section, until Usage


Conda env is not reproducible

I can't create the Conda env:
$ conda env create -f environment.yml
Channels:
 - defaults
Platform: linux-64
Collecting package metadata (repodata.json): done
Solving environment: failed

PackagesNotFoundError: The following packages are not available from current channels:

  - chromadb
  - langchain
  - langchain-chroma
  - langchain-community
  - langchain-core
  - langchain-openai
  - langchain-prompts
  - langchain-text-splitters
  - langchain-vectorstores
  - tiktoken

Current channels:

  - https://repo.anaconda.com/pkgs/main/linux-64
  - https://repo.anaconda.com/pkgs/r/linux-64

To search for alternate channels that may provide the conda package you're
looking for, navigate to

    https://anaconda.org

and use the search bar at the top of the page.

Could you please have a look @Essmaw ?

Is it working now, @pierrepo?
I've added the conda-forge channel and removed the dependencies that don't exist.

Yes. Much better thank you.
A good rule to follow when adding new dependencies is to delete and re-create the env each time:
 5000  conda env create -f environment.yml
 5001  conda activate biopyassistantenv


adding xinyual as maintainer

Description
adding xinyual as maintainer
Issues Resolved
[List any issues this PR will resolve]
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

DCO unsigned.


"Visual was invalidated during a render pass" while opening DevTools without Compositor

Describe the bug
When we create an Avalonia 11.0.0-preview2, and don't use compositor, when DevTools opened at Visuals page InvalidOperationException was thrown.
To Reproduce
Steps to reproduce the behavior:

Create Avalonia app with 11.0.0-preview2 version
Add.With(new Win32PlatformOptions
{
   UseCompositor = false
})

to BuildAvaloniaApp
Attach dev tools
Launch app, invoke dev tools. switch to Visuals page
See exception

Expected behavior
No exception
Desktop (please complete the following information):

OS: Windows (but potentially all others too)
Version: 11.0.0-preview2

Additional context
Exception details:
System.InvalidOperationException: Visual was invalidated during a render pass
   at Avalonia.Rendering.DirtyVisuals.Add(IVisual visual) in /_/src/Avalonia.Base/Rendering/DirtyVisuals.cs:line 35
   at Avalonia.Rendering.DeferredRenderer.AddDirty(IVisual visual) in /_/src/Avalonia.Base/Rendering/DeferredRenderer.cs:line 122
   at Avalonia.Visual.InvalidateVisual() in /_/src/Avalonia.Base/Visual.cs:line 330
   at Avalonia.Layout.Layoutable.InvalidateArrange() in /_/src/Avalonia.Base/Layout/Layoutable.cs:line 445
   at Avalonia.Controls.Panel.AffectsParentArrangeInvalidate[TPanel](AvaloniaPropertyChangedEventArgs e) in /_/src/Avalonia.Controls/Panel.cs:line 165
   at System.Reactive.AnonymousObserver`1.OnNextCore(T value) in /_/Rx.NET/Source/src/System.Reactive/AnonymousObserver.cs:line 67
   at System.Reactive.ObserverBase`1.OnNext(T value) in /_/Rx.NET/Source/src/System.Reactive/ObserverBase.cs:line 34
   at System.Reactive.Subjects.Subject`1.OnNext(T value) in /_/Rx.NET/Source/src/System.Reactive/Subjects/Subject.cs:line 147
   at Avalonia.AvaloniaProperty`1.NotifyChanged(AvaloniaPropertyChangedEventArgs`1 e) in /_/src/Avalonia.Base/AvaloniaProperty`1.cs:line 65
   at Avalonia.AvaloniaObject.RaisePropertyChanged[T](AvaloniaPropertyChangedEventArgs`1 change) in /_/src/Avalonia.Base/AvaloniaObject.cs:line 779
   at Avalonia.AvaloniaObject.ValueChanged[T](AvaloniaPropertyChangedEventArgs`1 change) in /_/src/Avalonia.Base/AvaloniaObject.cs:line 551
   at Avalonia.ValueStore.NotifyValueChanged[T](AvaloniaProperty`1 property, Optional`1 oldValue, BindingValue`1 newValue, BindingPriority priority) in /_/src/Avalonia.Base/ValueStore.cs:line 354
   at Avalonia.ValueStore.SetValue[T](StyledPropertyBase`1 property, T value, BindingPriority priority) in /_/src/Avalonia.Base/ValueStore.cs:line 120
   at Avalonia.AvaloniaObject.SetValue[T](StyledPropertyBase`1 property, T value, BindingPriority priority) in /_/src/Avalonia.Base/AvaloniaObject.cs:line 368
   at Avalonia.Controls.Canvas.SetLeft(AvaloniaObject element, Double value) in /_/src/Avalonia.Controls/Canvas.cs:line 69
   at Avalonia.Diagnostics.Views.LayoutExplorerView.<UpdateSizeGuidelines>g__SetPosition|12_2(Rectangle rect, Point start) in /_/src/Avalonia.Diagnostics/Diagnostics/Views/LayoutExplorerView.axaml.cs:line 110
   at Avalonia.Diagnostics.Views.LayoutExplorerView.<UpdateSizeGuidelines>g__UpdateGuidelines|12_0(Visual area) in /_/src/Avalonia.Diagnostics/Diagnostics/Views/LayoutExplorerView.axaml.cs:line 71
   at Avalonia.Diagnostics.Views.LayoutExplorerView.UpdateSizeGuidelines(AvaloniaPropertyChangedEventArgs e) in /_/src/Avalonia.Diagnostics/Diagnostics/Views/LayoutExplorerView.axaml.cs:line 116
   at System.Reactive.AnonymousObserver`1.OnNextCore(T value) in /_/Rx.NET/Source/src/System.Reactive/AnonymousObserver.cs:line 67
   at System.Reactive.ObserverBase`1.OnNext(T value) in /_/Rx.NET/Source/src/System.Reactive/ObserverBase.cs:line 34
   at Avalonia.Reactive.LightweightObservableBase`1.PublishNext(T value) in /_/src/Avalonia.Base/Reactive/LightweightObservableBase.cs:line 118
   at Avalonia.Reactive.AvaloniaPropertyChangedObservable.PropertyChanged(Object sender, AvaloniaPropertyChangedEventArgs e) in /_/src/Avalonia.Base/Reactive/AvaloniaPropertyChangedObservable.cs:line 42
   at Avalonia.AvaloniaObject.RaisePropertyChanged[T](AvaloniaPropertyChangedEventArgs`1 change) in /_/src/Avalonia.Base/AvaloniaObject.cs:line 780
   at Avalonia.AvaloniaObject.RaisePropertyChanged[T](AvaloniaProperty`1 property, Optional`1 oldValue, BindingValue`1 newValue, BindingPriority priority) in /_/src/Avalonia.Base/AvaloniaObject.cs:line 691
   at Avalonia.AvaloniaObject.SetAndRaise[T](AvaloniaProperty`1 property, T& field, T value) in /_/src/Avalonia.Base/AvaloniaObject.cs:line 721
   at Avalonia.Visual.Avalonia.VisualTree.IVisual.set_TransformedBounds(Nullable`1 value) in /_/src/Avalonia.Base/Visual.cs:line 321
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 262
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 273
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 306
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 273
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 306
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 273
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 306
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 273
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 273
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 306
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 273
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 273
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 306
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 306
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 306
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 273
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 273
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(DrawingContext context, Scene scene, VisualNode node, Rect clip, Boolean forceRecurse) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 273
   at Avalonia.Rendering.SceneGraph.SceneBuilder.Update(Scene scene, IVisual visual) in /_/src/Avalonia.Base/Rendering/SceneGraph/SceneBuilder.cs:line 91
   at Avalonia.Rendering.DeferredRenderer.UpdateScene() in /_/src/Avalonia.Base/Rendering/DeferredRenderer.cs:line 661
   at Avalonia.Rendering.DeferredRenderer.UpdateSceneIfNeeded() in /_/src/Avalonia.Base/Rendering/DeferredRenderer.cs:line 624
   at Avalonia.Threading.JobRunner.Job.Avalonia.Threading.JobRunner.IJob.Run() in /_/src/Avalonia.Base/Threading/JobRunner.cs:line 193
   at Avalonia.Threading.JobRunner.RunJobs(Nullable`1 priority) in /_/src/Avalonia.Base/Threading/JobRunner.cs:line 38
   at Avalonia.Win32.Win32Platform.WndProc(IntPtr hWnd, UInt32 msg, IntPtr wParam, IntPtr lParam) in /_/src/Windows/Avalonia.Win32/Win32Platform.cs:line 267
   at Avalonia.Win32.Interop.UnmanagedMethods.DispatchMessage(MSG& lpmsg)
   at Avalonia.Win32.Win32Platform.RunLoop(CancellationToken cancellationToken) in /_/src/Windows/Avalonia.Win32/Win32Platform.cs:line 214
   at Avalonia.Threading.Dispatcher.MainLoop(CancellationToken cancellationToken) in /_/src/Avalonia.Base/Threading/Dispatcher.cs:line 61
   at Avalonia.Controls.ApplicationLifetimes.ClassicDesktopStyleApplicationLifetime.Start(String[] args) in /_/src/Avalonia.Controls/ApplicationLifetimes/ClassicDesktopStyleApplicationLifetime.cs:line 120
   at Avalonia.ClassicDesktopStyleApplicationLifetimeExtensions.StartWithClassicDesktopLifetime[T](T builder, String[] args, ShutdownMode shutdownMode) in /_/src/Avalonia.Controls/ApplicationLifetimes/ClassicDesktopStyleApplicationLifetime.cs:line 209
   at AvaloniaCrossPlatformApplication1.Desktop.Program.Main(String[] args) in C:\Users\SKProCH\RiderProjects\AvaloniaCrossPlatformApplication1\AvaloniaCrossPlatformApplication1\AvaloniaCrossPlatformApplication1.Desktop\Program.cs:line 10

When diagnosing renderer-related bugs, a check was added to prevent visuals from being invalidated while renderer is actively building a scene (since it's something that shouldn't happen): https://github.com/AvaloniaUI/Avalonia/blob/ce98bffe66e92b3b68205036f0fe4dfeb2b138e8/src/Avalonia.Base/Rendering/DirtyVisuals.cs#L33-L36
It seems that devtools are doing exactly that
@grokys @Gillibald

Hello, thank you for the feedback. The OS is Windows 10 x64. The bug itself I can also only reproduce in my application. In the demo it works flawlessly. However, I use massive async operations - I wonder if it's because of that? Whereas the binding thread is save and still NotifiyPropertChanged is thrown in the main thread.
A similar bug also exists in relation to DevTools directly in Avalonia:
https://github.com/AvaloniaUI/Avalonia/issues/9275


Hide default spring JDBC properties behind PowerAuth properties

In order to be able to configure PowerAuth 2.0 Server JDBC properties globally (not for a given context), it would be nice to allow configuration using other than Spring default properties.
Following new properties should be introduced:
spring.datasource.url=${powerauth.datasource.url}
spring.datasource.username=${powerauth.datasource.username}
spring.datasource.password=${powerauth.datasource.password}
spring.datasource.driver-class-name=${powerauth.datasource.driver-class-name}
spring.jpa.properties.hibernate.default_schema=${powerauth.jpa.properties.hibernate.default_schema}

Moved to the correct repository. lime-company/powerauth-server#3


New draw.io file not saved through Onedrive

Preflight Checklist

[ x] I agree to follow the Code of Conduct that this project adheres to.
[ x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

You must agree to search and the code of conduct. You must fill in this entire template. If you delete part/all or miss parts out your issue will be closed.
If you are technical, you should reporting bugs along the lines of https://marker.io/blog/how-to-write-bug-report. If you are not technical, we will make allowances, please try to make an effort to understand the process.
Describe the bug
New draw.io file when saving to Onedrive is not saved, but the web interface says it is saved. Also changes after first save and when hit 'Save'  are not saved and not mentioning of unsaved changes
To Reproduce
Steps to reproduce the behavior:
Open app.diagram.net
Select Onedrive
Click Create New Diagram
Set a name and pick template or blank
Click Create
Pick a subfolder or click Yes
Check if the file is created in the location you selected and see that there is nog file with the name given.
Expected behavior
New file is created in specified location and changes are save as well.
Screenshots
draw.io version (In the Help->About menu of the draw.io editor):
Web version: v22.0.2
Desktop (please complete the following information):

OS:  Windows 10
Browser Edge and Chrome
Browser Edge Version 117.0.2045.47 (Official build) (64-bit)
Browser Chrome Version Version 117.0.5938.134 (Official Build) (64-bit)

I tested the problem in incognito/private mode with all browser extensions switched off, write "yes" below:

yes

Additional context

I have to rectify/close/delete my issue. How?
Although I could not see the saved files on the expected locations and I could not find the files by searching for the name in Onedrive and/or SharePoint/Teams, the files were saved in the end.
Today, a day later, I could search and find all the new files created in either Onedrive Business Personal folder and SharePoint Teams Site Files folders.
It turns out that the folder selected in blue(highlighted) is the folder where the file is saved. (and not the folder in the crumpath showing in top line.
See screenshot below for a new file that will be saved in the 'Microsoft Edge' folder and not in the 'App'(parent) folder!

Not a bug, but a little confusing way of user interface. Luckily😄

Not a bug, but a little confusing user interface only. Luckily 🙂


Update configure-spring-boot-starter-java-app-with-azure-key-vault.md

Little adjustment to avoid misconceptions.

Thanks, @iamNoah1 !


Follow Apple advice for deprecated CFURL method.

Xcode v7+ complains about CFURLCreateStringByAddingPercentEscapes being deprecated. Perusing the code indicates that this method is only used to encode query components. Hence, I used Apple's recommended NSCharacterSet.URLQueryAllowedCharacterSet instead of the preexisting definition.

I signed it. The email you required is not the same as my github email.

👍


Issue about push new controller using tableview in CapsPageMenu Child Controller.

Hello sir i am using CapsPageMenu library,
its very easy to use, but i am getting stuck at pushing view controller from child controller of pageMenu (UITableview did select). using UIButton also its not working. please give me the solution for this.
Thanks in Advance..

Resolved with issue#200


adam-submit aborts if ADAM_HOME is set

If ADAM_HOME is set, adam-submit aborts with the message:
java.lang.ClassNotFoundException: org.bdgenomics.adam.cli.ADAMMain
	at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
	at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
	at java.lang.Class.forName0(Native Method)
	at java.lang.Class.forName(Class.java:348)

The bin/find-adam-assembly.sh used by adam-submit sourcesbin/find-adam-home.  find-adam-home script exits when ADAM_HOME is found. Since it is sourced, the adam-submit also exits.
To reproduce this, set ADAM_HOME and try running adam-submit .
Here's my patch to get it working:
diff --git a/bin/find-adam-home b/bin/find-adam-home
index 10269078..967f62a1 100755
--- a/bin/find-adam-home
+++ b/bin/find-adam-home
@@ -25,7 +25,7 @@ FIND_ADAM_HOME_PYTHON_SCRIPT="$(cd "$(dirname "$0")"; pwd)/find_adam_home.py"

 # Short cirtuit if the user already has this set.
 if [ ! -z "${ADAM_HOME}" ]; then
-   exit 0
+   true
 elif [ ! -f "$FIND_ADAM_HOME_PYTHON_SCRIPT" ]; then
   # If we are not in the same directory as find_adam_home.py we are not pip installed so we don't
   # need to search the different Python directories for a ADAM installation.

@fnothaft I'm still a bit shaky on changes to the bin scripts to support Python, is there a reason why find-adam-home short circuits out if ADAM_HOME is set?

It shouldn't. I'd tested the exact use case that @pbashyal-nmdp is running locally (before we merged the PR) and it had worked for me; I'm guessing that I then made a change after testing that locally and broke things. @pbashyal-nmdp do you mind if I commit the patch you provided (after testing it on my end)?

Yes, please use the patch. Thanks!


Stacked suggestions

I think this can be closed for now as all changes are in the stacked-slices-backend branch


fix bug breaking PausableTypewriter when pause occurs at beginning of…

Fixes https://github.com/YarnSpinnerTool/YarnSpinner-Unity/issues/290

Merged. Thank you very much!


blog: using webhook with node-red

Description

Related Issue(s)

Checklist

[ ] I have read the contribution guidelines
[ ] I have considered the performance impact of these changes
[ ] Suitable unit/system level tests have been added and they pass
[ ] Documentation has been updated

@sumitshinde-84 Is there an issue in the customer tracker? If so, can you link it in the description?

@sumitshinde-84 Is there an issue in the customer tracker? If so, can you link it in the description?

No, there are no issues related to this PR. Actually, this topic was provided in the Slack channel.

@ZJvandeWeg, the post is ready for your review. I have provided instructions to read DHT11 sensor data connected to Raspberry Pi 4. However, I haven't tested it on RPi 4. The post doesn't involve much about connecting RPi with the sensor; it focuses on how users can read the sensor data and about the webhook.

Hii @ZJvandeWeg , could you please check the diagram and let me know if it is correct?


move filter click-away detection behind filters

we'll likely want to close the current filter and open the other if a different filter is selected when a single filter is opened.
I believe we'll also want to remove the Apply button at some point and do real-time filtering on select.

To clarify, is

we'll likely want to close the current filter and open the other if a different filter is selected when a single filter is opened

the desired future behavior or what this PR is addressing? If the latter, that's not how I see it behaving locally, but just want to confirm.

We'll need to fix this behavior, shown below
stays-open.webm


Email key is null even after adding it in the scope while using Profile.getCurrentProfile method

🐛 Bug Report
Email field is null in iOS even after adding the scope of email in Login Manager after using the Profile.getCurrentProfile method .
//Object Received
[
"The current logged user is: ",
{
"firstName": null,
"lastName": null,
"middleName": null,
"linkURL": null,
"imageURL": XXX,
"userID": XXX,
"email": null,
"name": "Loreum Ipsum"
}
]
To Reproduce
Use Profile.getCurrentProfile method to retrieve user profile details from Facebook.
Expected Behavior
Receive Email in profile object after adding email scope inside the Login Manager.
Code Example
// Login Manager Function
const facebookSignIn = () => {
    LoginManager.logInWithPermissions(["public_profile", "email"]).then(
        function (result) {
            if (result.isCancelled) {
                console.log("Login cancelled");
            } else {
                console.log(
                    "Login success with permissions: ",
                    result
                );
                FacebookProfile()
            }
        },
        function (error) {
            console.log("Login fail with error: " + error);
        }
    );
}

// Function used for getting profile
const FacebookProfile = () =>{
    const currentProfile = Profile.getCurrentProfile().then(
        function(currentProfile) {
          if (currentProfile) {
            console.log("The current logged user is: " , currentProfile);
          }
        }
      );
    if (Platform.OS === 'ios') {
        AuthenticationToken.getAuthenticationTokenIOS().then((data) => {
          console.log(data);
        });
      } else {
        AccessToken.getCurrentAccessToken().then((data) => {
          console.log(data?.accessToken.toString());
        });
    }
}

Environment
System:
OS: macOS 11.4
CPU: (8) arm64 Apple M1
Memory: 98.63 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.5.0 - /opt/homebrew/bin/node
Yarn: 1.22.10 - /opt/homebrew/bin/yarn
npm: 7.19.1 - /opt/homebrew/bin/npm
Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
Managers:
CocoaPods: 1.10.1 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 14.5, DriverKit 20.4, macOS 11.3, tvOS 14.5, watchOS 7.4
Android SDK:
API Levels: 29, 31
Build Tools: 28.0.3, 29.0.2, 30.0.2, 31.0.0
System Images: android-29 | Intel x86 Atom_64, android-31 | Google APIs Intel x86 Atom_64
Android NDK: Not Found
IDEs:
Android Studio: 4.2 AI-202.76<IP_ADDRESS>86908
Xcode: 12.5.1/12E507 - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_292 - /usr/bin/javac

npmPackages:
@react-native-community/cli: Not Found
react: 17.0.1 => 17.0.1
react-native: 0.64.2 => 0.64.2
react-native-macos: Not Found

Isn't it suspicious that every data element is unpopulated :thinking: ?

It is @mikehardy , is there something missing from my end or do I have to provide any additional scope for the same.

const facebookSignIn = () => {
    if (Platform.OS === "android") {
    LoginManager.setLoginBehavior("web_only")

    }
    LoginManager.logInWithPermissions(['public_profile', 'email']).then(
    result => {
    if (result.isCancelled) {
    } else {

    AccessToken.getCurrentAccessToken().then(data => {
    const { accessToken } = data;
    let token = accessToken.toString();
    return fetch(
    'https://graph.facebook.com/v2.5/me?fields=email,name,first_name,last_name,picture.type(large),friends&access_token=' +
    token,
    {
    method: 'GET',
    headers: {
    'Content-Type': 'application/json',
    },
    },
    )
    .then(response =>
    response.json().then(facebookData => {
    const fbData = JSON.stringify(facebookData);
    console.log("My fbData", fbData)
    }),
    )
    .catch(err => {
    console.log('FBERROR', err.message);
    });
    });
    }i
    },
    function (error) {
    console.log('Login fail with error: ' + error);
    },
    );
    };

Ok I did got my desired fb data by using GraphQL api inside after getting the access token which provides me desired output for both the Platform.

i also face the same error only on android

@NguyenLuongVinh  you can use the code above this will work for both the platforms
.

@NguyenLuongVinh you can use the code above this will work for both the platforms
.

I hope somehow, the data returned when calling Profile.getCurrentProfile() will contain email because it still works fine on ios :((((((

@NguyenLuongVinh you can use the code above this will work for both the platforms
.

I hope somehow, the data returned when calling Profile.getCurrentProfile() will contain email because it still works fine on ios :((((((

@NguyenLuongLinh It is present in the documentation that email field doesn't get retrieved on Android.

@NguyenLuongVinh you can use the code above this will work for both the platforms
.

I hope somehow, the data returned when calling Profile.getCurrentProfile() will contain email because it still works fine on ios :((((((

@NguyenLuongLinh It is present in the documentation that email field doesn't get retrieved on Android.

Tks so much, I want to cry :(


#unpublishgate

http://www.haneycodes.net/npm-left-pad-have-we-forgotten-how-to-program/
Thoughts?

Can't really find anything to agree with there. Writing for loops is a skill, just not one I care about having.
Couple comments put it well:
First:

Yeah, I think you’re just fundamentally misunderstanding the npm ecosystem and small module philosophy. +1 on the above link from Luis. The real problem yesterday’s events exposed is a design flaw in npm. Immutability at the centralized authority level and more decentralization of package distribution is the solution, not “write more functions yourself.”

Second:

These packages proliferate because JavaScript’s standard library is so woefully inadequate. It’s ridiculous that anyone has to write their own left-pad function in the first place. The problem isn’t that people “don’t know how to code”, it’s that they’re operating in an environment where basic functionality has to be implemented by end-users (i.e. developers), and where it’s — perhaps reasonably — standard operating procedure to import someone else’s solution rather than write your own.

Author seems like he's written some good C#. That's a very different world. He hasn't written any open source JS.

Like Ben said, when reading this it didn't feel like he'd written much OS JS.
This inspires me to use more things outside of my normal toolkit.
Maybe I should spend an evening here and there writing some C#, etc.
How about your thoughts @bsiddiqui ?

I don't agree with the article's suggestions: write all inline functions, don't rely on small modules that are less than "x" LOC, etc. I do think, however, that having an ecosystem where lots of packages are reliant on obscure, likely untested code, with no guarantee the dependencies won't change is a bit frightening.
Issues with packages being taken down, versioned incorrectly, etc creates points of failure that anyone doing professional software dev should be weary of. Recently I had an issue where Lob made a breaking change to their package and did a minor release, leading to some unexpected behavior.
I agree with the perspective that it's especially concerning if you expose these failure points for 1 LOC.
I'll likely just be much more careful about what software I depend on - something that everyone should be doing regardless. The npm ecosystem makes it simple to just find a package that does "x", require it, and ask questions later.
So basically totally fine to not want to write for utility functions and depend on abstractions as long as you know exactly what it's doing, it's well tested, and you have some degree of confidence that the maintainer won't take it down on a whim.
--
What would you guys think about NPM requiring some amount of notice be given before taking down a package? Perhaps if a package has dependencies you a notification could go out to maintainers on dependent projects that the package will be taken down in "x" days.
It'd leave devs with the autonomy to do whatever with their software and would give others some assurance that a package won't randomly disappear. Can't imagine anyone writing OSS having an issue with that.

What would you guys think about NPM requiring some amount of notice be given before taking down a package?

Nice in theory, doubt it could be executed well. I think the move here is full immutability. Just don't let people unpublish public packages without contacting support.


Compiling for Android failing with CMake 3.10.2

What platform/OS are you using?
Ubuntu 18.04.2
What compiler are you using? what version?
CMake 3.10.2
What's your CMake arguments?
cmake  -DBUILD_ONLY="s3;iot" -DENABLE_TESTING=OFF -DTARGET_ARCH=ANDROID -DNDK_DIR=/path/to/android-ndk-r12b ..
Can you provide a TRACE level log? (sanitize any sensitive information)
-- Found Git: /usr/bin/git (found version "2.21.0")
-- Building AWS libraries as shared objects
-- Android ABI: none specified, defaulting to armeabi-v7a
-- Android toolchain unspecified, defaulting to standalone-clang
-- Android std lib: libc++_shared
-- Android API level: android-21
-- Detected NDK version r12b
-- Could not find an appropriate standalone toolchain.  Generating one into /my/path/aws-sdk-cpp/build_android/toolchains/android/armeabi-v7a-standalone-clang-android-21-libc++_shared-12002
-- Building project version: 1.7.78
CMake Error: CMake was unable to find a build program corresponding to "Unix Makefiles".  CMAKE_MAKE_PROGRAM is not set.  You probably need to select a different build tool.
-- Configuring incomplete, errors occurred!
See also "/my/path/aws-sdk-cpp/build_android/.deps/CMakeFiles/CMakeOutput.log".
CMake Error at CMakeLists.txt:183 (message):
  Failed to configure third-party libraries.

-- Configuring incomplete, errors occurred!

Interestingly, with CMake version 3.6 it is working (I used the one provided by Android Studio).

Thank you for reporting this issue.
We are using a quite old NDK, which is not compatible with the new cmake.
And we are trying to make SDK build with latest Android NDK right now.

Now we support latest NDK r19c (back to 13b) with their own toolchain files, 12b is not supported anymore. Please reopen if you still have problem.


Autoreload issues not shown in ipython console

From<EMAIL_ADDRESS>on 2014-06-17T02:42:59Z
Hi, when setting IPython to autoreload modules like
%load_ext autoreload
%autoreload 2
and there is an issue in one of the modules, the ipython console in Spyder does not report it, while normal ipython consoles do. Example:
[autoreload of basicmodels failed: Traceback (most recent call last):
File "//anaconda/lib/python2.7/site-packages/IPython/extensions/autoreload.py", line 229, in check
superreload(m, reload, self.old_objects)
File "basicmodels.py", line 127
self.matr = self.get(exclude_idx = idx, axis)
SyntaxError: non-keyword arg after keyword arg
]
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=1853

From ccordoba12 on 2014-08-26T09:44:41Z
Labels: Cat-IPythonConsole MS-v2.4


Webcontainer => Jasonette IPC

Should work the same way it works for the iOS branch
https://github.com/Jasonette/JASONETTE-iOS/pull/253

@gliechtenstein I'm happy to work on this as I've just done the work on #162 so am in the webview head space atm.

@maks sounds great! 👍👍

This will be implemented per the doc issue: https://github.com/Jasonette/documentation/issues/66

@gliechtenstein I've got an initial working implementation: https://github.com/maks/JASONETTE-Android/commit/5ed6938c822507d8c391faecf1e6806a9f1563f5
BUT I haven't done the PR yet due to the interface for objects added to a Webview in Android  via addJavaInterface() only allowing simple types we need to pass the Jason from Webview JS to Java via JSON string (JSON.stringify()) not an actual JS object. Would you be able to do it this way on iOS to be consistent?

@maks I was thinking about that issue too. I guess we could do that in the worst case, but it feels a bit too inconvenient because then the user would have to write the code in escaped JSON string everytime and it's really cumbersome and not intuitive.
Would it be possible to inject an additional javascript on the Android side so that it automatically interprets a JS object into a JSON string before evaluating?

@gliechtenstein I guess we can load a bit of JS shim code to do this as long as we DONT target N where this will no longer work,  [per this compatibility note](https://developer.android.com/reference/android/webkit/WebView.html#evaluateJavascript(java.lang.String, android.webkit.ValueCallback<java.lang.String>))
The problem with doing the above is we permentantly stop Jasonette from ever targeting Android N or higher.
An alternative to that is to require webcontainer content that wants to use JASON to do so via loading a JS library (eg. via  CDN or locally) which could then hide this and any other future compatibility issues.

@gliechtenstein I saw you merged the iOS implementation for this. Are you ok then for me todo PR with implementation I have for Andriod with the caveat of needing to stringify() the return value?

Oops sorry i totally dropped the ball on this one, shouldn't have merged that iOS one before this issue was resolved in this world. Thankfully an API doesn't exist until it's documented so I think we have some room for now.

An alternative to that is to require webcontainer content that wants to use JASON to do so via loading a JS library (eg. via CDN or locally) which could then hide this and any other future compatibility issues.

Could you elaborate a bit on this? Do you mean like injecting some JavaScript into the webview? And how is this different from the JS shim approach? I guess I didn't fully understand the JS shim approach to begin with...

@gliechtenstein no worries.
What I meant would be to have content in a webview include a js file:
<script src="https://jasonette.org/webview-shim.js"></script>
and then webview-shim.js would expose whatever API we are going to document and the JS code in that would take care of doing anything needed to make it compatible across iOS and ANdroid, eg. needing to stringify() on Android.
Hope that makes sense?

@maks I think this is kind of related to https://github.com/Jasonette/Jasonette/issues/4 we're discussing. I guess now that we're going to be injecting JS files into JS execution context I guess there's not much holding us back from doing it this way?

@gliechtenstein no sorry its different, there we are talking about a webview whos content jasonette "controls" whereas here its any html content supplied be the user.

@maks OK I've just realized my confusion stems from the fact that the anchor tag part of the link you pasted is broken and simply opens up at the top of the https://developer.android.com/reference/android/webkit/WebView.html page. I didn't understand because I didn't realize you were talking about the valueCallback part specifically.
Anyway, now that I understand I can make a more constructive comment hopefully.
Basically the way I've implemented this logic on iOS side is

Create a javascript function called JASON.call and inject it to the webview context

Instead of having JASON.call run some JS-to-native binding logic, the JASON.call simply creates an <iframe> element with its src attribute set to the JSON object parameter we pass in to JASON.call https://github.com/Jasonette/JASONETTE-iOS/pull/253/files#diff-f22c800ecb5b9ecf974c06bdcb66ad7cR1881
NSString *summon = @"var JASON={call: function(e){var n=document.createElement(\"IFRAME\");n.setAttribute(\"src\",\"jason:\"+JSON.stringify(e)),document.documentElement.appendChild(n),n.parentNode.removeChild(n),n=null}};";
[webView stringByEvaluatingJavaScriptFromString:summon];

This JS creates an iframe that looks like this:
<iframe src="jason://{\"trigger\": \"some_action\"}">

(Note that we also make sure the iframe is cleaned up after this function is triggered. If you look at the script it calls removeChild to get rid of the created iframe right after execution)

Then we make sure the webview monitors a URL navigation event. When we encounter a url request attempt that starts with jason://, we extract out the JSON and parse it into dictionary and use it: https://github.com/Jasonette/JASONETTE-iOS/pull/253/files#diff-f22c800ecb5b9ecf974c06bdcb66ad7cR1886

Basically iOS has the same challenge as the challenge you brought up for higher version Androids. There is no way to directly make native calls from webview, and this is how we achieve it.
And since this problem is not unique to Android, I was thinking maybe we could do the same thing for Android.

Create a similar JS logic and inject it into webview, like we do for iOS
Implement shouldOverrideUrlLoading and watch out for the jason:// url, and when we come across one, parse it into JSONObject and use it.

How does that sound?

@gliechtenstein sorry about the broken link. I think we may have our wires crossed here...
On Android you can just "native calls" into Java directly. You use addJavascriptInterace() to inject a Java object into the global JS scope of the webview, then html content can call public methods of that object, there is no need at all for the iframe dance you need to use on iOS.
BUT there are constraints on the above, one of them is that the public Java methods you expose can only have "primitives" as parameter types, so you can pass in only numbers, strings, booleans but not JS objects. Hence the need to JSON.stringify().
So on Android its very straightforward to inject a Java object named JASON into the webviews global JS scope, its just not possible to pass it a object as a parameter, but a json string is fine.
To be honest to my mind this seems like a very small requirement to place on anyone making use of this interface, its just it would be nice for it to be consistent across iOS and Android.

Will there are any solution to do calls from JS to JASON?


Do not add the JavaEE dependency

The library is adding the JavaEE API. This should not be done so, and the Tomcat server will send a warning for this. The scope has to be reduced to runtime.

Removed


Use 'elemental install' instead of the former bash script

Signed-off-by: David Cassany<EMAIL_ADDRESS>

Marked as ready to review since CI tests are expected to be green and I believe there won't be further significant changes from now on. However before merging I'd like to verify some manual tests and double check some little behavior changes (environmental variables, defaults, etc.)

There are a couple of behavior changes to discuss:

--config flag has been renames to --cloud-init. I do believe this actually makes sense, but note this is a breaking change. Shall we add some --config deprecated flag that behaves as --cloud-init? I don't think so, as I'd like to start using elemental install --config <install-yaml> at some point not that far away. For that to happen I believe it is better to actually force a flag rename now.
cosign plugin is non functional with the current implementation as it used to be. Cosign plugin requires few environmental variables to run. Former installer code used to silently inject them. I don't want to do such thing in elemental install code. This is way too far from obvious. In addition, cosign plugin in luet is likely to be enabled by default. Would it actually make sense to invert the logic of --no-cosign flag and use a --cosign flat to explicitly enable it? This way we, if we run sanity checks on --cosign presence to verify env vars, I believe it would be way easier for the user to understand some extra configs or steps might be required. Also, in parallel, I believe having a proper channel of communication between elemental and luet plugins is something to consider, however I am not aware of the challenges of such a thing.

RE: config vs cloud-init
cloud-init all way. Like we have to maintain the functionality the same as before, but that doesnt mean we need to keep the flags and everything the same, for example, we are changing the config files location and format.
IMHO having an alias would be shooting in our own feet. Lets transition to nicer things now that we can :D

Like I get that on luet we needed to do it as a plugin, but on elemental we dont need to, we can have it directly and take advantage of us controlling all the flags passed and so on, so its much easier to avoid the env vars. Plus with our config stuff it should still be possible to use env vars (with ELEMENTAL on front) so win win. I would not support luet plugins on elemental as they have to be tied to whatever luet does, while on elemental we can do whatever we want.

I like this idea, then I just need to understand when and how to call the required plugins. Do you have any simple hints regarding that? Mostly about when to call it, I guess right after the luet call, but I am not 100% sure. I guess I will simply discover how to call the plugins.
Gonna have a look to this idea, if this is straight forward I'll try to implement it in the scope of this PR, otherwise I'd suggest to leave it for a follow up PR with a dedicated card.

yes, leaving for a different PR seems like a good idea.
The plugins stuff should be simple (HA!) as we only need to listen for the events and react to them, so it should be the cosign object or whatever, subscribing to the bus.Manager events and reacting to them.
@mudler probably knows if this is correct or more complicated than that?

The plugins stuff should be simple (HA!) as we only need to listen for the events and react to them, so it should be the cosign object or whatever, subscribing to the bus.Manager events and reacting to them.

mmm not so sure, I guess this requires to run luet and listen to events at the same time... plus having some coordination between both. Unless I am not understanding it to me it feels like this approach of relaying on luet events on elemental code requires setting a plugin to communicate luet and elemental (a mutex to to wait and raise trigger on events) and then run an event listener in elemental in a separate thread... Isn't it too complicated? Most events I see in Luet looks like they are before or after the main blocks (upgrade, unpack, install, etc), so I'd say simply running the plugin before or after is enough and do not mess with luet's events bus.

sure we can, but AFAIK is just a simple use of the manager from go-plugabble to subscribe and receive events no? Maybe not, I dont know, I just expected it to work like that, probably Im wrong :D

bah, go pluggable only works with external plugins, not with internal objects :/

In any case, as we control the workflow, its even simpler to just call the cosign/mtree objects on the created artifacts at build time, or after download(even before download with cosign!) the install/upgrade artifacts :D

In any case, as we control the workflow, its even simpler to just call the cosign/mtree objects on the created artifacts at build time, or after download(even before download with cosign!) the install/upgrade artifacts :D

Yes this is what I thought it would be simpler. Just create an mtree and cosign interfaces in elemental and call what we need when we need it.


Laravel Mix Browser Sync stopped working on Linux Mint

This problem is occurring on a fresh install. However, I have run the suggested commands (reinstall node/check for elixir etc.) anyway.

Laravel Mix Version: 1.4.5
Node Version: 8.6.0
NPM Version: 5.4.2
OS: Linux Mint 18 Cinnamon 64-bit

<EMAIL_ADDRESS><EMAIL_ADDRESS>
Description:
When running 'npm run watch' the following error is returned:
events.js:182
throw er; // Unhandled 'error' event
^
Error: watch app ENOSPC
at _errnoException (util.js:1019:11)
at FSWatcher.start (fs.js:1383:19)
at Object.fs.watch (fs.js:1409:11)
at createFsWatchInstance (/home/simon/Code/exp/testWatch/node_modules/chokidar/lib/nodefs-handler.js:37:15)
at setFsWatchListener (/home/simon/Code/exp/testWatch/node_modules/chokidar/lib/nodefs-handler.js:80:15)
at FSWatcher.NodeFsHandler._watchWithNodeFs (/home/simon/Code/exp/testWatch/node_modules/chokidar/lib/nodefs-handler.js:228:14)
at FSWatcher.NodeFsHandler._handleDir (/home/simon/Code/exp/testWatch/node_modules/chokidar/lib/nodefs-handler.js:407:19)
at FSWatcher. (/home/simon/Code/exp/testWatch/node_modules/chokidar/lib/nodefs-handler.js:455:19)
at FSWatcher. (/home/simon/Code/exp/testWatch/node_modules/chokidar/lib/nodefs-handler.js:460:16)
at FSReqWrap.oncomplete (fs.js:154:5)
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR! @ watch: cross-env NODE_ENV=development node_modules/webpack/bin/webpack.js --watch --progress --hide-modules --config=node_modules/laravel-mix/setup/webpack.config.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the @ watch script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR! A complete log of this run can be found in:
npm ERR!     /home/simon/.npm/_logs/2017-09-30T22_19_30_813Z-debug.log
Steps To Reproduce:
Install a new Laravel app using 'laravel new '
Run 'npm install'
Add:
mix.js('resources/assets/js/app.js', 'public/js')
   .sass('resources/assets/sass/app.scss', 'public/css')
   .browserSync('thephysics.dev');

to webpack.mix.js.
Run 'npm run watch' (install extra dependencies the first time)
Run 'npm run watch' again - see the error described above.

This was working fine last week.
It didn't work on a new project tonight.
Having upgraded npm and node it now doesn't work on any projects (even after reinstalling all node dependencies).
Help!

ENOSPC = No space left on drive.

That's not it, as I have 4.6 Gb of free space on the drive concerned.
That may be what the error means - but it doesn't make any sense.

What is the capacity of your swapfile?

Thanks @ruchern
/tmp is 66.7 kb - is that what you meant?
I've tried using:
npm config set tmp /path/to/some/other/dir

And no joy with that either.
What I have noticed, is that it only seems to happen when I have VS Code open before running npm run watch. And the thing that changed at the weekend is that I was trying VS Code out for the first time on this machine.
Two possible solutions:

VS Code is hogging more memory than either atom or PHP Storm (I don't know enough about VS Code to know if this is the case).
VS Code is doing something odd.

It tends to suggest that it isn't anything to do with Mix though (as I've recreated the same problem when using BrowserSync directly also).

The solution to this seems to be to increase the number of 'watches' the linux system can handle by running this command:
echo fs.inotify.max_user_watches=524288 | sudo tee -a /etc/sysctl.conf && sudo sysctl -p

This comes from the following Stack Overflow thread:
https://stackoverflow.com/questions/16748737/grunt-watch-error-waiting-fatal-error-watch-enospc

@simonhunt Sorry that I have missed your reply. No, not that. I am referring to this file /swapfile.
I had that issue just the other day after I have migrated my production server. Adding a 4G swapfile fixed the issue for me.
I am not sure if this applies to Linux Mint: https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-16-04

Thanks again @Ruchern - really grateful for your time.
I've actually reinstalled Linux Mint in an attempt to solve this thread since and set the swapfile to nearly 15 Gb (twice my RAM). This didn't work, but I have literally just posted something which did fix it.
It appears to be something to do with the default number of files which can be watched. By increasing that number the process works now.

Cool that at least you found a fix to it.

@simonhunt your solution fix the problem .. thanks.

This is not laravel-mix related but due to "files.useExperimentalFileWatcher": true, which is the default in vscode, does not work on linux.
Here is the main issue: https://github.com/Microsoft/vscode/issues/45295
And here, I've written a resume and workaround: https://github.com/Microsoft/vscode/issues/62314#issuecomment-434990537
TL;DR set  "files.useExperimentalFileWatcher": false in vscode.


go.{mod,sum}: update

Commit ba3a445dda6941ba82 added use of github.com/thoas/go-funk but it
was not reflected in go.mod.
This commit is brought to you by
go mod tidy

@kolyshkin Thanks. I did not update go.mod because I thought that go-funk is only used in magic-gen which is not really used, yet. But I guess I misunderstood Go modules once again.

I thought that go-funk is only used in magic-gen which is not really used, yet. But I guess I misunderstood Go modules once again.

No one understands Go modules in their entirety :trollface:
Closing this one in favor of https://github.com/checkpoint-restore/go-criu/pull/37


Add resize method

This adds optimized rust implementations for many resize filters. All except Nearest defer down to the resize crate.
Other changes:

I also had to add a few more traits for pixels to make this work.

Floating point strikes again.


Fix Algolia Search

We were using the wrong API key for search.  So no results. This fixes the API key.

/land

/land


Pre-generating output

More notes from previous F2Fs.
We want to figure out how we can align the new tools (enrichment, collapse, speech/walker) with MathJax-node.

pre-generate enriched MathML
pre-generate maction-ified MathML  (+ minimal extension for collapsing)
pre-generate full MathJax-node output (+ minimal extensions for collapsing)

enable the walker to use the data attributes in the output.

One advantage of pre-generating the maction-ified MathML would be that we could more easily compute summaries as currently the workflow does not easily lent itself to it:
MathML -> enriched MathML -> mactions added -> summaries for mactions
MathJax ->         SRE             ->       MathJax      ->     SRE


Feature request: Parsec app

Is it possible to run the Raspberry pi build of Parsec game streaming app (https://parsec.app/) on ArkOS? I was attempting to run it on ArkOS 1.7 installed on an odroid go advance 1.1 but it seems to have issues with libopenmaxil.so.
Thanks.

I looked into this before and unfortunately it wouldn't launch.  With it being closed source, I couldn't troubleshoot it.


Identifiers validation failed for dataset Texas A&M University Insect Collection

Identifier validation failed for the dataset Texas A&M University Insect Collection:

Crawler attempt: 218
Publishing organization: Texas A&M University Insect Collection
Publishing country: UNITED_STATES
Installation: Symbiota Collections of Arthropods Network (SCAN)
Number of occurrences indexed for this dataset at the time of the issue: 999991
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 999993, absent records count 999808
Step metrics:

Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3029849/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Texas A&M University Insect Collection : https://doi.org/10.15468/caprqh.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Cecilie contacted the Symbiotic SCAN portal manager about this dataset on March, 29th.
The answer at the time was that the file was corrupt but they weren't available to fix things at the moment. They wrote to bring it back up later if needed.

Identifier validation still  failing for the dataset Texas A&M University Insect Collection:

Crawler attempt: 221
Publishing organization: Texas A&M University Insect Collection
Publishing country: UNITED_STATES
Installation: Symbiota Collections of Arthropods Network (SCAN)
Number of occurrences indexed for this dataset at the time of the issue: 999991
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 999993, absent records count 999808
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3062709/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Texas A&M University Insect Collection : https://doi.org/10.15468/caprqh.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Texas A&M University Insect Collection:

Crawler attempt: 223
Publishing organization: Texas A&M University Insect Collection
Publishing country: UNITED_STATES
Installation: Symbiota Collections of Arthropods Network (SCAN)
Number of occurrences indexed for this dataset at the time of the issue: 999991
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 999993, absent records count 999808
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3083819/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Texas A&M University Insect Collection : https://doi.org/10.15468/caprqh.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Texas A&M University Insect Collection:

Crawler attempt: 224
Publishing organization: Texas A&M University Insect Collection
Publishing country: UNITED_STATES
Installation: Symbiota Collections of Arthropods Network (SCAN)
Number of occurrences indexed for this dataset at the time of the issue: 999991
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 999993, absent records count 999808
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3096187/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Texas A&M University Insect Collection : https://doi.org/10.15468/caprqh.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Texas A&M University Insect Collection:

Crawler attempt: 226
Publishing organization: Texas A&M University Insect Collection
Publishing country: UNITED_STATES
Installation: Symbiota Collections of Arthropods Network (SCAN)
Number of occurrences indexed for this dataset at the time of the issue: 999991
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 999993 total records; 999808 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3188425/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Texas A&M University Insect Collection : https://doi.org/10.15468/caprqh.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Texas A&M University Insect Collection:

Crawler attempt: 228
Publishing organization: Texas A&M University Insect Collection
Publishing country: UNITED_STATES
Installation: Symbiota Collections of Arthropods Network (SCAN)
Number of occurrences indexed for this dataset at the time of the issue: 999991
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 999993 total records; 999808 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3304497/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Texas A&M University Insect Collection : https://doi.org/10.15468/caprqh.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Texas A&M University Insect Collection:

Crawler attempt: 230
Publishing organization: Texas A&M University Insect Collection
Publishing country: UNITED_STATES
Installation: Symbiota Collections of Arthropods Network (SCAN)
Number of occurrences indexed for this dataset at the time of the issue: 999991
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 999993 total records; 999808 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3326759/step

New IDs sample:

21419238
15247807
15247682
15240327
15247797
15237253
15247801
15247808
15247792
21420106

Old IDs sample:

7879b90b-58ed-4e0a-b6c9-498f4f28b7fb
94ab3c4c-108c-4df7-99e8-99cda2b6d6cd
3d44fecb-b514-4b9e-9738-a64b0e6251de
f93bb67f-39a9-40e0-a7a7-da7f9691b702
c70a99c5-650d-49e8-8403-4724f1565495
34f8c9c7-6edc-42aa-aded-fc8846c14322
5c0dcad1-d57e-4186-a235-d4721d8ebbeb
f7367624-e12a-4d56-9b56-30b3a710355a
5410651e-7d2b-4624-b6a2-37a4b270631b
04ff8ff2-2c67-4504-8442-296793b4b92d

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Texas A&M University Insect Collection : https://doi.org/10.15468/caprqh.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Texas A&M University Insect Collection:

Crawler attempt: 231
Publishing organization: Texas A&M University Insect Collection
Publishing country: UNITED_STATES
Installation: Symbiota Collections of Arthropods Network (SCAN)
Number of occurrences indexed for this dataset at the time of the issue: 999991
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 999993 total records; 999808 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3337873/step

New IDs sample:

21422310
15247810
15240422
15247672
15237254
15247790
15247789
15237257
15247674
15247798

Old IDs sample:

7879b90b-58ed-4e0a-b6c9-498f4f28b7fb
94ab3c4c-108c-4df7-99e8-99cda2b6d6cd
3d44fecb-b514-4b9e-9738-a64b0e6251de
f93bb67f-39a9-40e0-a7a7-da7f9691b702
c70a99c5-650d-49e8-8403-4724f1565495
34f8c9c7-6edc-42aa-aded-fc8846c14322
5c0dcad1-d57e-4186-a235-d4721d8ebbeb
f7367624-e12a-4d56-9b56-30b3a710355a
5410651e-7d2b-4624-b6a2-37a4b270631b
04ff8ff2-2c67-4504-8442-296793b4b92d

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Texas A&M University Insect Collection : https://doi.org/10.15468/caprqh.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

It has been more than 3 months and although the publisher mentioned trying to fix the issue, the dataset is still paused. I am letting it go through.


Bootstrap dowload run npm install ater this run npm start get that error og hugo-binProvide a general summary of the issue

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
Error: spawn C:_mywork\bootstrap-5.0.2\node_modules\hugo-bin\vendor\hugo.exe ENOENT
at Process.ChildProcess._handle.onexit (node:internal/child_process:282:19)
at onErrorNT (node:internal/child_process:477:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
Emitted 'error' event on ChildProcess instance at:
at Process.ChildProcess._handle.onexit (node:internal/child_process:288:12)
at onErrorNT (node:internal/child_process:477:16)
at processTicksAndRejections (node:internal/process/task_queues:83:21) {
errno: -4058,
code: 'ENOENT',
syscall: 'spawn C:\_mywork\bootstrap-5.0.2\node_modules\hugo-bin\vendor\hugo.exe',
path: 'C:\_mywork\bootstrap-5.0.2\node_modules\hugo-bin\vendor\hugo.exe',
spawnargs: [ 'server', '--port', '9001', '--disableFastRender' ]
Reduced test cases
"name": "bootstrap",
"version": "5.0.2",

Clone the repo: git clone https://github.com/twbs/bootstrap.git
Install with npm: npm install bootstrap
Install with yarn: yarn add bootstrap
after npm start get error

What operating system(s) are you seeing the problem on?
Windows
What browser(s) are you seeing the problem on?


Standardize the error objects

Currently there seems to be two different error objects returned as part of a 4xx error response:
1:
{
  "code": "NINO_INVALID",
  "message": "The provided Nino is invalid"
}

2:
{
  "code": "INVALID_REQUEST",
  "message": "Invalid request",
    "errors": [
    {
      "code": "INVALID_MONETARY_AMOUNT",
      "message": "annualInvestmentAllowance should be non-negative number up to 2 decimal values",
      "path": "/allowances/annualInvestmentAllowance"
    },
    {
      "code": "INVALID_MONETARY_AMOUNT",
      "message": "averagingAdjustment should be non-negative number up to 2 decimal values",
      "path": "/adjustments/averagingAdjustment"
    }
  ]
}

Are there any plans to standardize it, so that the error objects returned are the same model regardless of the error. i.e something like:
[
   {
      "code": "INVALID_MONETARY_AMOUNT",
      "message": "annualInvestmentAllowance should be non-negative number up to 2 decimal values",
      "path": "/allowances/annualInvestmentAllowance"
    },
    {
      "code": "NINO_INVALID",
      "message": "The provided Nino is invalid",
      "path": "" (optional)
    },
]

Well,
This is our standard error message;
{   "code": "INVALID_REQUEST",   "message": "Invalid request",     "errors": [     {       "code": "INVALID_MONETARY_AMOUNT",       "message": "annualInvestmentAllowance should be non-negative number up to 2 decimal values",       "path": "/allowances/annualInvestmentAllowance"     },     {       "code": "INVALID_MONETARY_AMOUNT",       "message": "averagingAdjustment should be non-negative number up to 2 decimal values",       "path": "/adjustments/averagingAdjustment"     }   ] }
You should create a single Error object on your side with fields such as 'code': String, 'message': String and 'errors': List[Error] where the errors list may be empty. Please refer to the JSON error schema on the hub for detail.
I would much prefer the structure suggested by you, but we hamstrung the other APIs on the platform.

@osblue13
Looking at the raml spec I would observe that there is just one definition of the error object and the two examples are both valid by that definition.
Generating the following C# (Typescript/JS also available) from the Json Schema shows this clearly:
namespace MyNamespace
{
    #pragma warning disable // Disable all warnings

    [System.CodeDom.Compiler.GeneratedCode("NJsonSchema", "8.1.6249.15627")]
    public partial class Part
    {
        [Newtonsoft.Json.JsonProperty("code", Required = Newtonsoft.Json.Required.Default, NullValueHandling = Newtonsoft.Json.NullValueHandling.Ignore)]
        public string Code { get; set; }

        [Newtonsoft.Json.JsonProperty("message", Required = Newtonsoft.Json.Required.Default, NullValueHandling = Newtonsoft.Json.NullValueHandling.Ignore)]
        public string Message { get; set; }

        [Newtonsoft.Json.JsonProperty("path", Required = Newtonsoft.Json.Required.Default, NullValueHandling = Newtonsoft.Json.NullValueHandling.Ignore)]
        public string Path { get; set; }

        public string ToJson()
        {
            return Newtonsoft.Json.JsonConvert.SerializeObject(this);
        }

        public static Part FromJson(string data)
        {
            return Newtonsoft.Json.JsonConvert.DeserializeObject<Part>(data);
        }
    }

    [System.CodeDom.Compiler.GeneratedCode("NJsonSchema", "8.1.6249.15627")]
    public partial class Error
    {
        [Newtonsoft.Json.JsonProperty("code", Required = Newtonsoft.Json.Required.Always)]
        [System.ComponentModel.DataAnnotations.Required]
        public string Code { get; set; }

        [Newtonsoft.Json.JsonProperty("message", Required = Newtonsoft.Json.Required.Always)]
        [System.ComponentModel.DataAnnotations.Required]
        public string Message { get; set; }

        [Newtonsoft.Json.JsonProperty("path", Required = Newtonsoft.Json.Required.Default, NullValueHandling = Newtonsoft.Json.NullValueHandling.Ignore)]
        public string Path { get; set; }

        [Newtonsoft.Json.JsonProperty("errors", Required = Newtonsoft.Json.Required.Default, NullValueHandling = Newtonsoft.Json.NullValueHandling.Ignore)]
        public System.Collections.ObjectModel.ObservableCollection<Part> Errors { get; set; }

        public string ToJson()
        {
            return Newtonsoft.Json.JsonConvert.SerializeObject(this);
        }

        public static Error FromJson(string data)
        {
            return Newtonsoft.Json.JsonConvert.DeserializeObject<Error>(data);
        }
    }

For my own sanity I have given up trying to reverse out the data model from the documented and operational examples.  Better to rely upon the RAML, imperfect though it is.

The generated code will be able to parse the first 2 error structures as both are correct.

Are you happy for me to close this issue?

@saurabharora80
It's a pity that the wiki isn't open to contributors so this stuff doesn't sink below the waves or get lost in one-to-one emails with SDS

But there again perhaps I spoke too soon...
In the application.raml file many of the errors are typed as:
                400:
                  body:
                    application/json:
                      type: types.errorResponse
                      examples:
                        invalidNino:
                          description: Invalid NINO
                          value:
                            code: NINO_INVALID

But types.errorResponse is defined in types.raml as:
  errorResponse:
    properties:
      code: string

But some are typed as:
              403:
                body:
                  application/json:
                    type: !include schemas/Error.json
              409:
                body:
                  application/json:
                    type: !include schemas/Error.json

So in my opinion a version of this questions remains open.  Why do we need two distinct error constructs?

400:                   body:                     application/json:                       type: types.errorResponse                       examples:                         invalidNino:                           description: Invalid NINO                           value:                             code: NINO_INVALID
This is API hub custom/non-standard RAML for generating error tables. Please don't refer to it.

Yes, happy to close.
Thanks @saurabharora80 @andyws


Update .env.example

there was a typo here price_ instead of prod_ as they all say first thing first as env files important thing in any project without nothing can work so it's need 100% clearify of everything and i feel that work maybe confuse someone so i edit it

@sadmann7

You are supposed to copy the price api id within the product


Choreremove javax.el and upgrade jackson to 2.16.0 (#38843)

…
Proposed changes
javax.el is the API for Java Expression Language, which provides a simple and flexible way for Java Web applications to access and manipulate data. EL expressions are commonly used in JSP pages, but we are not involved in their use here, so I removed it.

upgrade jackson to 2.16.0

(cherry picked from commit 33a0ea5565c2e0d7e5909ca3b512fb0b539f05f4)
#38843
Issue Number: close #xxx

run buildall

run buildall


Remove Sidekiq::Util

Fixes #381

I tested the changes locally and it seems that this does the trick! Thank you!

sidekiq/util has been replace with sidekiq/component in sidekiq 6.5.0.
Why not make the replacement in this gem instead of removing it? Is sidekiq/util not needed by this gem at all?

@ltello The problem with that is that Sidekiq::Component does only exist in Sidekiq 6.5 which would force us to bump a major release of sidekiq-scheduler and this major release would require Sidekiq >= 6.5

Also, I believe that sidekiq/util is not needed at all by this gem, the only method we were using was the logger which we can access without requiring this internal API (maybe in older versions of sidekiq it was required, but doesn't seem to be anymore)

Another important thing to note is that we have been accessing the logger through Sidekiq.logger, including sidekiq/util would have allowed us to access it directly  logger which we don't do, so I don't see reasons for requiring that file.
Looking at the history, it seems that since https://github.com/moove-it/sidekiq-scheduler/pull/238 we didn't depend anymore on any method of sidekiq/util, before we did access logger directly https://github.com/moove-it/sidekiq-scheduler/pull/238/files#diff-0ddd2bcc9bd29aac261acdd76530920c85887c269cc29e3f054e465b4ac8699eL76 but with that refactor we don't do anymore


Delete Repository?

This is behind the solnic version. Do we even use this?

I think it was just used to make a PR.
https://github.com/solnic/virtus/commit/c2dc794e22d1da559e42462d6220595e115b9985

Lovely. Thanks @lpil :)

Used by Reports, Insight + Data Service. Not sure we want to touch them. We should reconsider removing this when they go out of service.


gem built in ubuntu 18.04 cannot be installed for td-agent 0.12.43

$ td-agent --version
td-agent 0.12.43

hearen@hearen-pc:/opt/fluent-plugin-prometheus$ uname -r
4.15.0-46-generic

hearen@hearen-pc:/opt/fluent-plugin-prometheus$ cat /etc/os-release
NAME="Ubuntu"
VERSION="18.04.2 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.2 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

I created my own plugin for prometheus collection and tried to install the td-agent following these two options in 18.04:
option - 1:
curl -L https://toolbelt.treasuredata.com/sh/install-ubuntu-bionic-td-agent3.sh | sh

option - 2:
download its deb: https://td-agent-package-browser.herokuapp.com/2.5/ubuntu/bionic/pool/contrib/t/td-agent
My configuration looks
<source>
  @type prometheus
  port 7081
</source>

<source>
  @type prometheus_monitor
</source>

<source>
  @type prometheus_output_monitor
</source>

<source>
  @type prometheus_tail_monitor
</source>

My Error is that I cannot build a valid gem in 18.04 which means I can build a valid gem in 16.04
td-agent-gem build ./fluent-plugin-prometheus.gemspec -q

If I built the gem in 18.04, td-agent then cannot be restarted and print error log as
2019-04-01 18:16:52 +0800 [info]: adding match pattern="debug.**" type="stdout"
2019-04-01 18:16:52 +0800 [info]: adding source type="prometheus"
2019-04-01 18:16:52 +0800 [error]: config error file="/etc/td-agent/td-agent.conf" error="Unknown input plugin 'prometheus'. Run 'gem search -rd fluent-plugin' to find plugins"
2019-04-01 18:16:52 +0800 [info]: process finished code=256
2019-04-01 18:16:52 +0800 [warn]: process died within 1 second. exit.

I'm quite new in fluentd/td-agent, perhaps it's silly question. Please provide any clue you have to help.
Any help will be appreciated ;)

Please paste gem build and install log.

@repeatedly
The build log
$ td-agent-gem build ./fluent-plugin-prometheus.gemspec -q
fatal: not a git repository (or any of the parent directories): .git
WARNING:  description and summary are identical
WARNING:  open-ended dependency on prometheus-client (>= 0) is not recommended
  if prometheus-client is semantically versioned, use:
    add_runtime_dependency 'prometheus-client', '~> 0'
WARNING:  open-ended dependency on bundler (>= 0, development) is not recommended
  if bundler is semantically versioned, use:
    add_development_dependency 'bundler', '~> 0'
WARNING:  open-ended dependency on rake (>= 0, development) is not recommended
  if rake is semantically versioned, use:
    add_development_dependency 'rake', '~> 0'
WARNING:  open-ended dependency on rspec (>= 0, development) is not recommended
  if rspec is semantically versioned, use:
    add_development_dependency 'rspec', '~> 0'
WARNING:  open-ended dependency on test-unit (>= 0, development) is not recommended
  if test-unit is semantically versioned, use:
    add_development_dependency 'test-unit', '~> 0'
WARNING:  See http://guides.rubygems.org/specification-reference/ for help
  Successfully built RubyGem
  Name: fluent-plugin-prometheus
  Version: <IP_ADDRESS>
  File: fluent-plugin-prometheus-<IP_ADDRESS>.gem

The install log
$ sudo td-agent-gem install fluent-plugin-prometheus-<IP_ADDRESS>.gem
Successfully installed fluent-plugin-prometheus-<IP_ADDRESS>
1 gem installed

I see. Could you also paste the result of td-agent-gem list | grep prometheus and
ls /opt/td-agent/embedded/lib/ruby/gems/RUBY-VERSION/gems/fluent-plugin-prometheus-<IP_ADDRESS>/lib/fluent/plugin ?

$ td-agent-gem list | grep prometheus
fluent-plugin-prometheus (<IP_ADDRESS>)
prometheus-client (0.9.0)

$ sudo ls /opt/td-agent/embedded/lib/ruby/gems/RUBY-VERSION/gems/fluent-plugin-prometheus-<IP_ADDRESS>/lib/fluent/plugin
ls: cannot access '/opt/td-agent/embedded/lib/ruby/gems/RUBY-VERSION/gems/fluent-plugin-prometheus-<IP_ADDRESS>/lib/fluent/plugin': No such file or directory

RUBY-VERSION is td-agent's ruby version. Please replace it.

$ /opt/td-agent/embbeded/bin/ruby -v
bash: /opt/td-agent/embbeded/bin/ruby: No such file or directory

Sorry. My typo. embedded is correct.

$ /opt/td-agent/embedded/bin/ruby -v
ruby 2.5.1p57 (2018-03-29 revision 63029) [x86_64-linux]
hearen@hearen-pc:/opt/fluent-plugin-prometheus$ sudo ls /opt/td-agent/embedded/lib/ruby/gems/2.5.1/gems/fluent-plugin-prometheus-<IP_ADDRESS>/lib/fluent/plugin
ls: cannot access '/opt/td-agent/embedded/lib/ruby/gems/2.5.1/gems/fluent-plugin-prometheus-<IP_ADDRESS>/lib/fluent/plugin': No such file or directory

2.5.1 -> 2.5.0

$ sudo ls /opt/td-agent/embedded/lib/ruby/gems/2.5.0/gems/fluent-plugin-prometheus-<IP_ADDRESS>/

I see. Maybe, your rubygems spec is wrong.

but it works in 16.04 as I mentioned in the question....

Could you upload your gem to github or something?

I am uploading it to github: https://github.com/Hearen/smallest-demos/blob/master/fluent-plugin-prometheus-<IP_ADDRESS>.gem

Please check it here, I am uploading it to github: https://github.com/Hearen/smallest-demos/blob/master/fluent-plugin-prometheus-<IP_ADDRESS>.gem

I mean your actual repository because need to simulate build / install.
BTW, your uploaded gem is empy. You can confirm it via gem unpack command.
With above gem, ubuntu 16.04 also failed. I confirmed directory is empty on ubuntu 16.04.

@repeatedly Wow, I just know gem unpack...just start to work on ruby. I uploaded the files to, you can check it here: https://github.com/Hearen/smallest-demos/blob/master/fluentd-prometheus/README.md

@repeatedly Thanks for the help, I think I located the issue now. I am adding the details here. Please continue your work. Really thanks for all the help to this newbie ;) (me). Have a nice day!

The whole issue come to the failed gem generation and the solution is
# remove the generated to avoid
# While executing gem ... (Gem::InvalidSpecificationException) ... contains itself
$ rm fluent-plugin-prometheus-<IP_ADDRESS>.gem

# to make this change visible to git
# since I am using `git ls-files -z` for my spec.files in fluent-plugin-prometheus.gemspec
$ add .

# ready to generate now
$ td-agent-gem build fluent-plugin-prometheus.gemspec

Now, you can install it as expected.
Very sorry to mention that 16.04 is working, it's just old story and I have no 16.04 to test on my own.

More details about why this occurred to me.
I am taking over the old task and just follow its doc using
td-agent-gem build ./fluent-plugin-prometheus.gemspec -q
# with -q, I unknowingly silenced all the generation details
# whose generation is actually failed but it presents **Successfully built RubyGem**


Allow to build for non-systemd systems

This will disable systemd integration for all cabal users,
but fixes #1200.
There are two other ways to fix this:

provide a hackage overlay, which contains lobemo-scribe-systemd
only or all 3rdparty packages and then add that overlay to
cabal.project (downside: stack doesn't seem to be able to use
hackage overlays)
provide 2 cabal.project files and let user choose via e.g.:
--project-file=cabal.project.nosystemd
(downside: maintaining yet another file)

Edit: third option could be to document for non-systemd users how to edit cabal.project, but I guess that's a bit awkward?

That's certainly an option. What about providing a hackage overlay? I find that an interesting idea in general and would be eager to look into it. But it will add more steps to release cycle.

@hasufell Why do you need to disable systemd anyway?
You can just install the systemd development package for your Linux distribution and then the cabal build will succeed.
If you have religious objections to systemd, there is always cabal.project.local.

You can just install the systemd development package for your Linux distribution and then the cabal build will succeed.

not all distros have systemd: https://pkgs.alpinelinux.org/packages?name=systemd&branch=edge
on some distros you cannot have eudev and systemd installed at the same time, because they are both udev providers: https://gitlab.exherbo.org/exherbo/arbor/-/blob/aec8e96ed61483f92995680ad0e3b414934fee0a/packages/sys-apps/eudev/eudev.exlib#L34

So installing systemd is not an option for me.

That doesn't work, as discussed in this PR, because of #1200 and haskell/cabal#5444

This seems to me like an issue that should be fixed upstream.

This seems to me like an issue that should be fixed upstream.

Yes, there already is an issue open, but there is no clear timeline, so it needs a workaround.

I don't see a reason to address this. The work-around is you modify the cabal.proejct file (as this patch does, and ideally when cabal is fixed, just add to cabal.project.local), but this patch would break our nix builds and cabal builds for anyone that wants systemd (which there are a number of pool operators I've been helping this weekend trying to get systemd services setup on non-nixos).

@disassembler as @erikd pointed out, this could be done by a shell script. I don't believe users will figure this out on their own. Is there any reason to not accept a patch for that?


Dependencies version bump

Updated some outdated packages, fixed import for newer version.

I'm archiving this repository in favor of https://github.com/jxnblk/mdx-deck/tree/master/packages/gatsby-theme ✌


Add support for Wagtail integration

I think we can leverage all the work done in this app and allow for creating blog posts within Wagtail by supplying just a couple classes.
I'm relatively green to Wagtail though so I might be underestimating the effort or misunderstanding the viability of such an idea.

Not sure if it's a good idea, but happy to help evaluate!

If you want a blog already for wagtail there is coderedcms

@bastianhilton Thank you for pointing that out. We will take a look!


Update appveyor, fix traj slicing test

Bugfixes for 0.2.2 release

Codecov Report

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

@@           Coverage Diff           @@
##           master      #16   +/-   ##
=======================================
  Coverage   93.98%   93.98%
=======================================
  Files          18       18
  Lines         565      565
=======================================
  Hits          531      531
  Misses         34       34

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 480e27f...aa53e58. Read the comment docs.