TINKERPOP-1120: If there is no view nor messages, don't create empty views/messages in SparkExecutor

https://issues.apache.org/jira/browse/TINKERPOP-1120
The following PR effects TraversalVertexProgram and SparkGraphComputer. Here is what changed in both:
-------SparkGraphComputer
1. If the vertex doesn't pass any messages, don't serialize an empty list, serialize null.
2. If the vertex doesn't have a view, don't serialize an empty list of detached vertex properties, serialize null.
3. If the vertex doesn't have a view nor messages, don't do anything!
-------TraversalVertexProgram
4. Found a memory bug where halted traversers were still distributed amongst the vertices even though they were sent to the master traversal.
5. If a halted traverser TraverserSet is empty, remove the property (remove the vertex view!).

You can read about the performance gains by doing this here:
https://groups.google.com/d/msg/gremlin-users/NKjEXdRNp-M/S48pDXjdAQAJ
CHANGELOG
* `SparkGraphComputer` no longer shuffles empty views or empty outgoing messages in order to save time and space.
* `TraversalVertexProgram` no longer maintains empty halted traverser properties in order to save space.

UPGRADE
TraversalVertexProgram
----------------------

`TraversalVertexProgram` always maintained a `HALTED_TRAVERSERS` `TraverserSet` for each vertex throughout the life of the OLAP computation. However, if there are no halted traversers in the set, then there is no point in keeping the compute property around as without it, time and space are saved. Users that have `VertexPrograms` that are chained off of `TraversalVertexProgram` that have previously assumed that `HALTED_TRAVERSERS` always exists, should now no longer assume that.

---java
// bad code
TraverserSet haltedTraversers = vertex.value(TraversalVertexProgram.HALTED_TRAVERSERS);
// good code
TraverserSet haltedTraversers = vertex.property(TraversalVertexProgram.HALTED_TRAVERSERS).orElse(new TraverserSet());
---

VOTE +1 -- integration tests and Blade cluster benchmarking/testing.

I see test failures.
Results :
Tests in error:
  TinkerGraphStepStrategyTest>AbstractGremlinTest.setup:80 ? NullPointer
  TinkerGraphStepStrategyTest>AbstractGremlinTest.tearDown:135 ? NullPointer
Tests run: 2989, Failures: 0, Errors: 2, Skipped: 392

Tried twice, same result.

@dkuppitz --- I can't seem to reproduce this. Note that there is nothing in this PR that has to do with the testing infrastructure (AbstractGremlinTest) or TinkerGraph (save indirectly via TraversalVertexProgram, but that wouldn't effect test setup and teardown infrastructure). Can you give line numbers to where the failure is occurring?
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
[INFO] Apache TinkerPop .................................. SUCCESS [5.301s]
[INFO] Apache TinkerPop :: Gremlin Shaded ................ SUCCESS [3.117s]
[INFO] Apache TinkerPop :: Gremlin Core .................. SUCCESS [42.045s]
[INFO] Apache TinkerPop :: Gremlin Test .................. SUCCESS [13.780s]
[INFO] Apache TinkerPop :: Gremlin Groovy ................ SUCCESS [43.143s]
[INFO] Apache TinkerPop :: Gremlin Groovy Test ........... SUCCESS [7.014s]
[INFO] Apache TinkerPop :: TinkerGraph Gremlin ........... SUCCESS [1:46.117s]
[INFO] Apache TinkerPop :: Gremlin Benchmark ............. SUCCESS [4.385s]
[INFO] Apache TinkerPop :: Hadoop Gremlin ................ SUCCESS [6:38.470s]
[INFO] Apache TinkerPop :: Spark Gremlin ................. SUCCESS [4:55.645s]
[INFO] Apache TinkerPop :: Giraph Gremlin ................ SUCCESS [6.477s]
[INFO] Apache TinkerPop :: Neo4j Gremlin ................. SUCCESS [3.377s]
[INFO] Apache TinkerPop :: Gremlin Driver ................ SUCCESS [8.600s]
[INFO] Apache TinkerPop :: Gremlin Server ................ SUCCESS [39.823s]
[INFO] Apache TinkerPop :: Gremlin Console ............... SUCCESS [17.190s]
[INFO] Apache TinkerPop :: Gremlin Archetype ............. SUCCESS [0.149s]
[INFO] Apache TinkerPop :: Archetype - TinkerGraph ....... SUCCESS [5.030s]
[INFO] Apache TinkerPop :: Archetype - Server ............ SUCCESS [10.586s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 16:50.865s
[INFO] Finished at: Wed May 04 07:08:15 MDT 2016
[INFO] Final Memory: 133M/739M
[INFO] ------------------------------------------------------------------------

Another thing that is weird. TinkerGraphStepStrategyTest doesn't even use TraversalVertexProgram and thus, this failure is in no way related to the changed in this PR.
 @IgnoreEngine(COMPUTER)
    public void shouldFoldInHasContainers() {

That's the full log of the 2nd time it failed: https://gist.github.com/dkuppitz/406e2e89dc10b74aeaef9a11c4bb7718

Build worked properly on the other machine.
VOTE: +1

That is a wierd NullPointerException in that the graphProvider of the test is null.
        graphProvider = GraphManager.getGraphProvider(); // THIS BECOMES NULL ?
        graphProvider.getTestListener().ifPresent(l -> l.onTestStart(this.getClass(), name.getMethodName()));

What is different about your other machine?

My other machine is my my usual dev machine. I was trying to optimize things by running full test suites on OpenStack CoreOS instances, that failed. I will try that again using a different OS.

VOTE +1 - tested with mvn clean install


Migrate PDAL and GDAL together (LTR)

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Closes https://github.com/conda-forge/qgis-feedstock/pull/482 and https://github.com/conda-forge/qgis-feedstock/pull/480.
Same as https://github.com/conda-forge/qgis-feedstock/pull/484 but for the LTR branch

@conda-forge-admin, please rerender

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

If it builds, fine by me!

Thanks for working on this.


X and Y offset of bitmapfonts does not work for single-character strings.

Issue details
In bitmapFont.java, lines 850-853 (https://github.com/libgdx/libgdx/blob/e60a3937d31670602d5cdf3aca1ccffc7b7b08f9/gdx/src/com/badlogic/gdx/graphics/g2d/BitmapFont.java#L850-L853), the xAdvances of a string are set.  If the string only consists of one character, however, the offset isn't applied properly. This is improper for the kerning of characters, and how they should appear relative to input coordinates will be wrong..
In my case, this was found when trying to draw a box with box-drawing characters from a monospaced font using the unicode character set.
For example, here is a box printed using the box-drawing characters in single-character strings:

Reproduction steps/code
BitmapFont font;
font.draw(batch, "|", 100, 100);
Version of LibGDX and/or relevant dependencies
Master as of 5/4/21
Stacktrace
N/A
Please select the affected platforms
All / platform agnostic.

[x] Android
[x] iOS
[x] HTML/GWT
[x] Windows
[x] Linux
[x] MacOS

The workaround for this bug is to print a no-break space (a special space character that is in the quotes: " "), which will bypass the check and allow the text to be printed properly.

Are you setting the chars you use in the font to be fixed-width? That is, with bmpFont.setFixedWidthGlyphs(String); . This is mentioned in the linked code, as isFixed, and generally fixed-width implies there is no kerning in the font. There is a complex bug in Hiero that affects the creation of fixed-width fonts with the Java renderer, but Hiero's FreeType renderer should make fixed-width fonts correctly. There's also alternatives like the original AngelCode BMFont tool.

I'm using the angelcode exporter.
You're right in that I think setting the characters to fixed width may fix the issue, but when I have 3400 code points, it becomes impractical. That said, I've tried it with the box-drawing chars only, and I didn't notice a difference.

I use cmapToFile when I need to generate all the code points in a font, though it will be a pain to track down the actual site again. It probably isn't too hard to write this type of application for someone already familiar with the internals of the TTF format.. but I don't know any of those people... So here's the zipped .exe : cmaptofile.zip On windows, you can drag and drop a .ttf font onto this and it will place a .txt file next to it with all glyphs. You can possibly just read that file in as a String with FileHandle, and pass that to setFixedWidthGlyphs(). I have no real idea on the licensing of cmaptofile other than it isn't linked with or distributed with your game, and it was on a personal site that basically dumped utilities that person had made.

You can possibly just read that file in as a String with FileHandle, and pass that to setFixedWidthGlyphs()

Oh boy! This one's gonna be a funny-looking PR. 😆
Also: Updated original post with some code to help reproduce the bug. You'll need a bitmap font to plug into it, but it creates a beautiful color spread.

I ran your code, only changing the font for a monospaced one I had available:

Doesn't seem to be a problem here, with a different font. This appears to be a font configuration issue. My code changes to make your repro code runnable are here: https://github.com/yellowstonegames/SquidLib/blob/master/squidlib/src/test/java/squidpony/gdx/tests/issues/Issue6519.java (I don't actually use SquidLib there, just the assets for the font and the LWJGL3 test dependency.)

So, I was able to get the full font fixed-width using no external dependencies. It looks like
 now. The code I used is:
        public static void setAllFixedWidth(BitmapFont font) {
            BitmapFont.BitmapFontData data = font.getData();
            int maxAdvance = 0;
            for (int index = 0, end = 65536; index < end; index++) {
                BitmapFont.Glyph g = data.getGlyph((char) index);
                if (g != null && g.xadvance > maxAdvance) maxAdvance = g.xadvance;
            }
            for (int index = 0, end = 65536; index < end; index++) {
                BitmapFont.Glyph g = data.getGlyph((char) index);
                if (g == null) continue;
                g.xoffset += (maxAdvance - g.xadvance) / 2;
                g.xadvance = maxAdvance;
                g.kerning = null;
                g.fixedWidth = true;
            }
        }

It simply does what setFixedWidthGlyphs(CharSequence) does, but for all of the Unicode BMP (every Java char, ignoring any that aren't in the font).


Managed Installers across Applocker and WDAC

[Enter feedback here]
There are two ways to control apps. 1) AppLocker and 2) WDAC
On this page , when trying to learn about Managed installers, the text starts talking about WDAC, and then flips to AppLocker, without mentioning if manager installer works on both WDAC and AppLocker, or
Please can you help clear up the confusion, but explicitly saying where Managed Installer can work.
_Windows Defender Application Control (WDAC) includes an option called managed installer that helps balance security and manageability when enforcing application control policies. This option lets you automatically allow applications installed by a designated software distribution solution, such as Microsoft Configuration Manager (MEMCM) or Microsoft Intune.
How does a managed installer work?
Managed installer uses a special rule collection in AppLocker to designate binaries that are trusted by your organization as an authorized source for application installation. When one of these trusted binaries runs, Windows monitors the binary's process (and any child processes it launches) and watches for files being written to disk. As files are written, they're tagged as originating from a managed installer._

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

ID: 7d9a0607-b206-fab3-ef68-9de7c7e6a072
Version Independent ID: 9ca53978-51c8-d2e1-c6a4-4b0a19bac244
Content: Allow apps deployed with a WDAC managed installer (Windows)
Content Source: windows/security/threat-protection/windows-defender-application-control/configure-authorized-apps-deployed-with-a-managed-installer.md
Product: windows-client
Technology: itpro-security
GitHub Login: @jsuther1974
Microsoft Alias: vinpa

To make it easier for you to submit feedback on articles on learn.microsoft.com, we're transitioning our feedback system from GitHub Issues to a new experience.
As part of the transition, this GitHub Issue will be moved to a private repository. We're moving Issues to another repository so we can continue working on Issues that were open at the time of the transition. When this Issue is moved, you'll no longer be able to access it.
If you want to provide additional information before this Issue is moved, please update this Issue before December 15th, 2023.
With the new experience, you no longer need to sign in to GitHub to enter and submit your feedback. Instead, you can choose directly on each article's page whether the article was helpful. Then you can then choose one or more reasons for your feedback and optionally provide additional context before you select Submit.
Here's what the new experience looks like.
Note: The new experience is being rolled out across learn.microsoft.com in phases. If you don't see the new experience on an article, please check back later.
First, select whether the article was helpful:

Then, choose at least one reason for your feedback and optionally provide additional details about your feedback:

Article was helpful
Article was unhelpful

Finally, select Submit and you're done!


Remove the stackframes with unnecessary method calls

Purpose

$title

Fixes #27867
Approach
Samples
Remarks
Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[x] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

The patch coverage is still low after added relevant test cases because no test cases has been added for the fileName != null check and we can't remove this check since there is a possibility to have the value null as per Java Api doc.


CRA with docz: components relative (base) url not working properly

Bug Report
Describe the bug
Docz required files to be absolutely imported, relative imports does not works
To Reproduce

Go to Install docz and configure on any CRA app
Run docz dev server.
See error (when relative file-paths)

 ERROR  Failed to compile with 1 errors                                                                                16:08:59

This dependency was not found:

* redux/rest in ./src/pages/Counter/reducers.js

To install it, you can run: npm install --save redux/rest

In order to allow us to quickly reproduce you issue please include a link to a reproduction repository.
Expected behavior
A clear and concise description of what you expected to happen..
Environment

OS: [e.g. OSX 10.13.4, Windows 10]
Node/npm version: [e.g. Node 8/npm 5]

Additional context/Screenshots
Add any other context about the problem here. If applicable, add screenshots to help explain.

You need to configure your alias using custom webpack configuration to has the same shape of u're using inside CRA.


[BUG - Release] minor issue since we got logtext but the othe opengl window dont work

Branch or Release
The Tag for the Release you are using, or the commit you used if you built from source yourself.
main branch newest ,3
Game and Engine Version
Game where the bug occurred, and the UE engine version of the game.
4.27.2
Describe the bug
A clear and concise description of what the bug is.
well, the debug windows is not working, its all white, and i had to make my own debug report to get it printet, theres an issue with  vertex shader 150 of imgue.
Mods directory
A zip of your Mods folder if you've installed any mods that don't come with UE4SS by default
also the guide making c++ mods is not accurate, u dont get the correct actor. so i did hook on instead wich works. i am attaching my code instead its just one file , feeling out the c++ what it can do, but bug live or bug at any way window is not happening with latest release. https://paste.ofcode.org/KEcB84dujpRrLCGgs2xT5S
https://github.com/nexustheru/myawsomemod/tree/main
To Reproduce
Steps to reproduce the behavior:

Launch game
Attempt UHT Dump
impossible bc windows its all white, and clicking ctrl-0 o or whatever new hotkey, it crashes the game
See error in log

Expected behavior
A clear and concise description of what you expected to happen.
to find the source of why text is not appearing on the debug window
Screenshots and UE4SS Log
If applicable, add screenshots to help explain your problem, and upload the log.
https://paste.pics/4893701f95dc6b5cd4dfc75bdccfe0f7
Desktop (please complete the following information):

OS: [e.g. Win10, Win11] win 10

Additional context
i tried this code on a slate console window, its fine and works, but as soon as i moved this code into ue4ss main repo as cpp++ mod with source  from deps, we have this issue.

Is this a new problem in 3.0 ?

version before i could see the gui error message, now its all blank, as i sayed i had to attach my own stuff to get the error out since it was all blank could not even get headers out, no button nothing., theres an issue with imgue how it renders on the gui part on developer window. prolly minor .  imma tinker around abit more with ue4ss ,theres prolly just a typo

I have no idea how rendering your own ImGui window will work or how it may or may not interfere with the UE4SS window so unfortunately I can't really help with this problem.
The best I can offer is a quick search: https://stackoverflow.com/a/72901890
Hopefully someone else can help.
What are you planning on using your window for ? If it's for debugging purposes, you can create a tab in our own ImGui window instead of making your own window.

orginally i wanted to make a cpp mod, but i had to find my own ways to get the actors for hogwarts legacy since ,wiki is not correct here , static object dont work, and imgui creating tab dont work either. so i went on to do seperate process, and this how i found whats the issue was atleast on the gui tab stuff. and this explains why gui dev is not working, register tab is not simply getting thought. i spammed that funktion, not a single log.

orginally i wanted to make a cpp mod, but i had to find my own ways to get the actors for hogwarts legacy since ,wiki is not correct here , static object dont work, and imgui creating tab dont work either. so i went on to do seperate process, and this how i found whats the issue was atleast on the gui tab stuff. and this explains why gui dev is not working, register tab is not simply getting thought. i spammed that funktion, not a single log.

Maybe you made a mistake in your code and that's why the tab system isn't working.
Show your code for it.
I currently have a C++ mod running on 3.0 with working tabs.

i followed the wiki to letter, i put a log up right after this function. it never fire, inside registertab at bottom

i had to find my own ways to get the actors for hogwarts legacy since ,wiki is not correct here , static object dont work

The wiki just shows an example of how to get an object, it's not incorrect, it's just that StaticFindObject is not applicable for everything.

i know that, why i used hook. but problem is the error is not getting thought. before version 3  that was rel few days ago, theres was no issue with live debugger or dumping headers or buttons.

I'm having problems understanding your broken English unfortunately.
Had you perhaps changed anything in UE4SS-settings.ini before you updated to 3.0 and forget to change it again after the update ?

never mind. i fix it myself, thank you for your help.

Just FYI, @UE4SS, the issue about the gui window being "all blank" (as this user described) happens for many games, and the fix for it is to change the renderer from opengl to dx11

Just FYI, @UE4SS, the issue about the gui window being "all blank" (as this user described) happens for many games, and the fix for it is to change the renderer from opengl to dx11 in settings

That's kind of what I thought, which is why I was asking them if they'd changed anything in the settings file.
The idea was, they changed it and that's why it worked fine before, and then they updated and overrode the settings file and didn't make the change again.

Just FYI, @UE4SS, the issue about the gui window being "all blank" (as this user described) happens for many games, and the fix for it is to change the renderer from opengl to dx11 in settings
nope, [Overrides]
; Path to the 'Mods' folder
; Default: <dll_directory>/Mods
ModsFolderPath =

[General]
EnableHotReloadSystem = 0
; Whether the cache system for AOBs will be used.
; Default: 1
UseCache = 1
; Whether caches will be invalidated if ue4ss.dll has changed
; Default: 1
InvalidateCacheIfDLLDiffers = 1
; The number of seconds the scanner will scan for before giving up
; Default: 30
SecondsToScanBeforeGivingUp = 30
; Whether to create UObject listeners in GUObjectArray to create a fast cache for use instead of iterating GUObjectArray.
; Setting this to false can help if you're experiencing a crash on startup.
; Default: true
bUseUObjectArrayCache = true
[EngineVersionOverride]
MajorVersion =
MinorVersion =
[ObjectDumper]
; Whether to force all assets to be loaded before dumping objects
; WARNING: Can require multiple gigabytes of extra memory
; WARNING: Is not stable & will crash the game if you load past the main menu after dumping
; Default: 0
LoadAllAssetsBeforeDumpingObjects = 0
[CXXHeaderGenerator]
; Whether to property offsets and sizes
; Default: 1
DumpOffsetsAndSizes = 1
; Whether memory layouts of classes and structs should be accurate
; This must be set to 1, if you want to use the generated headers in an actual C++ project
; When set to 0, padding member variables will not be generated
; NOTE: A VALUE OF 1 HAS NO PURPOSE YET! MEMORY LAYOUT IS NOT ACCURATE EITHER WAY!
; Default: 0
KeepMemoryLayout = 0
; Whether to force all assets to be loaded before generating headers
; WARNING: Can require multiple gigabytes of extra memory
; WARNING: Is not stable & will crash the game if you load past the main menu after dumping
; Default: 0
LoadAllAssetsBeforeGeneratingCXXHeaders = 0
[UHTHeaderGenerator]
; Whether to skip generating packages that belong to the engine
; Some games make alterations to the engine and for those games you might want to set this to 0
; Default: 0
IgnoreAllCoreEngineModules = 0
; Whether to skip generating the "Engine" and "CoreUObject" packages
; Default: 1
IgnoreEngineAndCoreUObject = 1
; Whether to force all UFUNCTION macros to have "BlueprintCallable"
; Note: This will cause some errors in the generated headers that you will need to manually fix
; Default: 1
MakeAllFunctionsBlueprintCallable = 1
; Whether to force all UPROPERTY macros to have "BlueprintReadWrite"
; Also forces all UPROPERTY macros to have "meta=(AllowPrivateAccess=true)"
; Default: 1
MakeAllPropertyBlueprintsReadWrite = 1
; Whether to force UENUM macros on enums to have 'BlueprintType' if the underlying type was implicit or uint8
; Note: This also forces the underlying type to be uint8 where the type would otherwise be implicit
; Default: 1
MakeEnumClassesBlueprintType = 1
; Whether to force "Config = Engine" on all UCLASS macros that use either one of:
; "DefaultConfig", "GlobalUserConfig" or "ProjectUserConfig"
; Default: 1
MakeAllConfigsEngineConfig = 1
[Debug]
; Whether to enable the external UE4SS debug console.
ConsoleEnabled = 1
GuiConsoleEnabled =0
GuiConsoleVisible = 0
; Multiplier for Font Size within the Debug Gui
; Default: 1
GuiConsoleFontScaling = 1
; The API that will be used to render the GUI debug window.
; Valid values (case-insensitive): dx11, d3d11, opengl
; Default: opengl
GraphicsAPI = opengl
; How many objects to put in each group in the live view.
; A lower number means more groups but less lag when a group is open.
; A higher number means less groups but more lag when a group is open.
; Default: 32768
LiveViewObjectsPerGroup = 32768
[Threads]
; The number of threads that the sig scanner will use (not real cpu threads, can be over your physical & hyperthreading max)
; If the game is modular then multi-threading will always be off regardless of the settings in this file
; Min: 1
; Max:<PHONE_NUMBER>
; Default: 8
SigScannerNumThreads = 8
; The minimum size that a module has to be in order for multi-threading to be enabled
; This should be large enough so that the cost of creating threads won't out-weigh the speed gained from scanning in multiple threads
; Min: 0
; Max:<PHONE_NUMBER>
; Default: 16777216
SigScannerMultithreadingModuleSizeThreshold = 16777216
[Memory]
; The maximum memory usage (in percentage, see Task Manager %) allowed before asset loading (when LoadAllAssetsBefore* is 1) cannot happen.
; Once this percentage is reached, the asset loader will stop loading and whatever operation was in progress (object dump, or cxx generator) will continue.
; Default: 85
MaxMemoryUsageDuringAssetLoading = 80
[Hooks]
HookProcessInternal = 1
HookProcessLocalScriptFunction = 1
HookInitGameState = 1
HookCallFunctionByNameWithArguments = 1
HookBeginPlay  = 1
HookLocalPlayerExec = 1
FExecVTableOffsetInLocalPlayer = 0x28
[CrashDump]
EnableDumping = 1
FullMemoryDump = 0
[ExperimentalFeatures]
; Only enable these features if you know what you are doing.
GUIUFunctionCaller = 0
only thing i changed was the debugger gui 1 or 0 then it got all weird. dosnt matter what i change im just gonna rebuild it tomrrow with pull and do proper test.

but im pore in english so i dont expect you to understand me. but im trying .

found the issue   ; The API that will be used to render the GUI debug window.
; Valid values (case-insensitive): dx11, d3d11, opengl
; Default: opengl
GraphicsAPI = dx11  <---- changed default to this, now its working

That is what I said, but well done for figuring it out yourself too


Lock down to Rails ~>4.0

As this isn't needed with Rails 5+, and likely won't work will older (and no longer supported) Rails versions < 4.

Thank you!


core bundle for archetype25 does not start when installed on v6.5.0[bug]

###Issue
When package for Archetype 25 is installed on a clean version of 6.5.0 the core bundle does not start.
###Error Message
Core bundle not starting
org.apache.sling.api.resource,version=[2.12,3) -- Cannot be resolvedorg.apache.sling.api.servlets,version=[2.3,3) -- Cannot be resolved
com.day.cq.wcm.api,version=[1.29,2) -- Cannot be resolved
Expected Behaviour

Documentation would call out minimum version dependencies OR....Bundles would start when installed OOTB

Actual Behaviour

Bundles do not start

Reproduce Scenario (including but not limited to)
Steps to Reproduce

Create a project using the properties referenced in the attachment
Run the command mvn install -DskipTests -PautoInstallSinglePackage
Observe bundle in the Felix Console, as it will be in the "installed" status vs "started"
archetype.properties.txt

Platform and Version
6.5.0

Look at https://github.com/adobe/aem-project-archetype#system-requirements.
You need 6.5.5 or newer with archetype 25.

@kwin ah...major face-palm on that one!  That is 100% a miss on my end. Apologies for the trouble. Closing ticket


[LLM Runtime] Optmized dropout operator

Type of Change
feature or bug fix or documentation or others: feature
API changed or not: Yes
user can call optimized fwd/bwd dropout operator in QBits, 3X+ perf improvement compared to pytorch.
e.g.
torch.ops.qbits_customop.qbits_dropout_fwd(weight, p)
torch.ops.qbits_customop.qbits_dropout_bwd(grad, mask)

Description
detail description
JIRA ticket: https://jira.devtools.intel.com/browse/NLPTOOLKIU-958
optmized fwd/bwd dropout operator under AVX512/AVX2 ISA, including a high-performance rand-generator.
change QBits log from cout to torch::LOG.
Expected Behavior & Potential Risk
the expected behavior that triggered by this PR
How has this PR been tested?
how to reproduce the test (including hardware information)
tested on 335T(spr) & desktop(Core i9-10900)
Dependency Change?
any library dependency introduced or removed
No.

there is something wrong when build binary, please check @zhewang1-intc
https://inteltf-jenk.sh.intel.com/job/nlp-toolkit-release-wheel-build/6928/consoleFull


ImportError: cannot import name 'frange' from 'matplotlib.mlab'

Hi,
I'm trying to get started with the library and I always get this error.
from control import *
import matplotlib.pyplot as plt
g=tf(1,[1,1,1])
t,y= step.response(g)
plt.plot(t,y)
plt.grid()
plt.xlab('t')
plt.ylab('t')
Thanks for your help.
ImportError                               Traceback (most recent call last)
 in
----> 1 from control import *
2 import matplotlib.pyplot as plt
3 g=tf(1,[1,1,1])
4 t,y= step.response(g)
5 plt.plot(t,y)
C:\Anaconda3\lib\site-packages\control_init_.py in
56 from .modelsimp import *
57 from .nichols import *
---> 58 from .phaseplot import *
59 from .pzmap import *
60 from .rlocus import *
C:\Anaconda3\lib\site-packages\control\phaseplot.py in
40 import numpy as np
41 import matplotlib.pyplot as mpl
---> 42 from matplotlib.mlab import frange, find
43 from scipy.integrate import odeint
44 from .exception import ControlNotImplemented
ImportError: cannot import name 'frange' from 'matplotlib.mlab' (C:\Anaconda3\lib\site-packages\matplotlib\mlab.py)

You are using an outdated control with a recent matplotlib. mlab.frange was removed in matplotlib-3.1.0, and control removed the call in control-0.8.2.
Update your control package from conda-forge as described in the README and you should be fine.

Thanks for your help.


docs: Add alias info to Admin API

Signed-off-by: Dan Sover<EMAIL_ADDRESS>Docs PR Template
Why this should be merged
Additional information on the Admin API
How this works
Adds an info box with new information
How these changes were tested
Workflow checks

[] ran vale /docs/file/path on all changed .md files to ensure all grammar rules pass
[] ran markdownlint /docs/file/path on all changed .md files to ensure all linting rules pass
[] completed the above two checks and all additional rules outlined in style-checker-notes.md to
ensure all checks pass
[] if a doc was removed/deleted, the path to that doc must be redirected to a valid URL via the
_redirects file
[] all files that were moved from their current directory to a new path have had their paths
redirected via the _redirects file
[] _redirects were manually verified with the cloudflare preview link
[] sidebars.json reflects all changes made to file path

Ok updated -- this is how it looks now


Doesn't work, even the example page

I was curious when it didn't work in my app. Not sure if it matters, but I installed default-passive-events via NPM. I'm building a React application in Windows 10 using Chrome Version 70.0.3538.110 (Official Build) (64-bit). Maybe it's because it's React, but that's why I wanted to try your package, anyway I went to your example and ran an audit and either you're not using it on your own example or it just doesn't work. Thought I'd share with you.

Just confirmed - library is working under Win 10 Chrome 70.0.3538.110 (see screenshot below).
Is it possible that you're using any of Chrome's extenstions/plugins that break our functonality?

Hmm... I'll try another browser and let you know how it goes. Hopefully I
can find out why and let you know.
On Wed, Dec 5, 2018, 4:12 AM Jakub Freisler<EMAIL_ADDRESS>wrote:

Just confirmed - library is working under Win 10 Chrome 70.0.3538.110 (see
screenshot below).
Is it possible that you're using any of Chrome's extenstions/plugins that
break our functonality?
[image: image]
https://user-images.githubusercontent.com/10456649/49509878-ea006280-f886-11e8-96cd-6a6116f3f395.png
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zzarcon/default-passive-events/issues/26#issuecomment-444449201,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATGDQSA0qwBqbs18OaRH_IxmCvLTT9vyks5u16oNgaJpZM4ZCENK
.

Because of inactivity I'm closing this issue as invalid, if it's reproducible somehow, please submit new issue with reproduce steps


move gsm transport out of core vumi

Gammu works great but it is packaged terribly. It needs to be installed system wide via Apt and tests break unless it's been installed.  We'll be moving it out into a separate repository.

Code is going to be moved to http://github.com/praekelt/vxgsm


Address mixup between bzr revisions and semver suffixes

What does this do / why do we need it?
This PR handles the case in the godep_importer where the imported dependency is referencing a semantic version with a suffix. E.g.
{
	"ImportPath": "github.com/Shopify/sarama",
	"Comment": "v1.12.0-12-g2fd980e",
	"Rev": "2fd980e23bdcbb8edeb78fc704de0c39a6567ffc"
},

Will now become:
[[constraint]]
  name = "github.com/Shopify/sarama"
  version = ">=1.12.0, <=12.0.0-g2fd980e"

What should your reviewer look out for in this PR?
As per my understanding it is fine to assume that bzr revisions contain @ symbols. But I'm not a bzr user so I'm half guessing (with some reading on the Internet) that it's valid.
Do you need help or clarification on anything?
I think I've gotten what I needed in #827.
There was a comment in the code that I modified that was a bit too long. I have wrapped it. Don't know if you'd like to keep such things out of the PR. Let me know and I can drop that commit, no biggie 😄 .
Which issue(s) does this PR fix?
fixes #827

I signed it!

Thanks for the review, @carolynvs. I'll address your comments.

@carolynvs I have addressed your comment in commit a2c11c7 🙇

@sebdah Thank you for the fix! 🎉 💖


python310Packages.bcrypt: 3.2.2 -> 4.0.0

Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[ ] Fits CONTRIBUTING.md.

@ofborg build python3.pkgs.django_4 python3.pkgs.paramiko python3.pkgs.twisted python3.pkgs.fastapi python3.pkgs.asyncssh

:point_up: some good candidates for passthru.tests perhaps?

Cherry-picked to master for testing, on macos 10.15 passlib fails with:
______________________ CryptContextTest.test_dummy_verify ______________________

self = <passlib.tests.test_context.CryptContextTest testMethod=test_dummy_verify>

    def test_dummy_verify(self):
        """
        dummy_verify() method
        """
        # check dummy_verify() takes expected time
        expected = 0.05
        accuracy = 0.2
        handler = DelayHash.using()
        handler.delay = expected
        ctx = CryptContext(schemes=[handler])
        ctx.dummy_verify()  # prime the memoized helpers
        elapsed, _ = time_call(ctx.dummy_verify)
>       self.assertAlmostEqual(elapsed, expected, delta=expected * accuracy)
E       AssertionError: 0.06496206690000009 != 0.05 within 0.010000000000000002 delta (0.014962066900000084 difference)

passlib/tests/test_context.py:1605: AssertionError

Looks like a timing-based test to me.


Add faster scaling composite hash value encoding for remote path

Description
This is one of the tasks to achieve https://github.com/opensearch-project/OpenSearch/issues/12589 as part of the feature request https://github.com/opensearch-project/OpenSearch/issues/12567. This is only an increment step to conclude the optimised prefix path work proposed in the feature request.
In this PR, we have introduced a composite encoding for the 64 bits hash value. We use multiple attributes like index uuid, shard id, data category (segment/translog) and data type (data/metadata/lock_files) for generating a 64 bit hash value. Now, based on tests performed during the development, we have found a encoding that works best when the index shard counts or indexing rate increases on a cluster. The encoding uses 1st 6 bits to generate URL safe base 64 character and uses rest of the 14 bits as binary string equivalent. This encoded value as the prefix or infix depending of the path type selected at the cluster level. Currently, we are making this encoding value as default. We have levers in code to set the hash algorithm in index metadata to allow us in future to give a dynamic cluster setting that can be used to set the hash algorithm or the hash value encoding from multiple options.
Simulation steps done using AWS S3 -

Create S3 bucket and upload at very high rate at all possible characters from URL safe base64 charset. This will warm up and increase the overall maximum request rate capacity for the prefix. We see throttling for couple of hours until the throttling stops. Please note at this point we have not started our opensearch cluster.
Now we start our opensearch cluster with the same bucket we use above. We see we are able to support multiple active shards. Now, if we get more indexes (or more shards) created gradually, we are able to scale up S3 request rate capacity faster with binary encoding than the base64 encoding. The time is considerably lower in comparison to base64.

Check List

[x] New functionality includes testing.

[x] All tests pass

[x] New functionality has been documented.

[x] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s) (See: Troubleshooting Failing Builds)
[x] Commits are signed per the DCO using --signoff
~[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)~
~[ ] Public documentation issue/PR created~

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.

❕ Gradle check result for 9e86fad: UNSTABLE

TEST FAILURES:

      2 org.opensearch.common.util.concurrent.QueueResizableOpenSearchThreadPoolExecutorTests.classMethod
      1 org.opensearch.common.util.concurrent.QueueResizableOpenSearchThreadPoolExecutorTests.testResizeQueueDown

Please review all flaky tests that succeeded after retry and create an issue if one does not already exist to track the flaky failure.

Flaky test - https://github.com/opensearch-project/OpenSearch/issues/11979


Tests\Unit\MSFT_xMsiPackage.Tests.ps1: Fixes issue where tests fail if executed from a drive other than C:

Pull Request (PR) description
Tests\Unit\MSFT_xMsiPackage.Tests.ps1: Fixes issue where tests fail if executed from a drive other than C:
This Pull Request (PR) fixes the following issues
-Fixes #573
Task list

[x] Added an entry under the Unreleased section of the change log in
CHANGELOG.md. Entry should say what was changed, and how that affects
users (if applicable).
[ ] Resource documentation added/updated in README.md.
[ ] Resource parameter descriptions added/updated in README.md, schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as
appropriate.
[ ] Examples appropriately added/updated.
[x] Unit tests added/updated. See
DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See
DSC Resource Testing Guidelines.
[x] New/changed code adheres to
DSC Resource Style Guidelines and Best Practices

This change is

Codecov Report

Merging #578 into dev will not change coverage.
The diff coverage is n/a.

@@         Coverage Diff         @@
##            dev   #578   +/-   ##
===================================
  Coverage    74%    74%
===================================
  Files        27     27
  Lines      4074   4074
  Branches      4      4
===================================
  Hits       3032   3032
  Misses     1038   1038
  Partials      4      4

@PlagueHO , I'll leave this one for you to merge since it's my PR and someone else did the code review. Thanks.

Hi @ykuijs - could you resolve conflicts?

@PlagueHO , I'll resolve the conflicts since it's my PR (@ykuijs just did the review). Thanks.

@mhendric - doh! It was a long week at work :cry:


Set parallel_tests to output progress in the same format as regular RSpec

What was the end-user problem that led to this PR?
When running tests using the parallel_test tool, there will be no output on the terminal to show the progress or result of the test suit.
$ ./bin/parallel_rspec spec
8 processes for 162 specs, ~ 20 specs per process

Took 576 seconds (9:36)

You have to go diving into a file that's located in tmp/parallel_runtime_rspec.log.
It would be better to have the output set to the same as normal ./bin/rspec and show the progress/result of the test suit.
What was your diagnosis of the problem?
Run the parallel test suit using ./bin/parallel_rspec spec
What is your fix for the problem, implemented in this PR?
Remove the set format and out options for parallel_tests and let it output the progress of the test suit.

The current formatter is used to balance test times across thread/processes.
I think parallel_tests support multiple formatters, so if we want another formmatter, I think we can add it as a separate configuration?
Also, are failures not printed with the current format?

Oh, It's configured at the moment to record the test time and to balance out the different processors. There's a doc that uses both the RuntimeLogger and the progress formatter.
https://github.com/grosser/parallel_tests#rspec

@bundlerbot merge


With rye {root:uri}/../../packages/ seems to traverse more than 2 folders up

i'm trying to use rye sync with a python monorepo and root:uri
the resolution of folders doesn't seem to work.  for example
    "askluna-dotenv @ {root:uri}/../../packages/dotenv" => error: Distribution not found at: file:///Users/shravansunder/Documents/dev/project-dev/askluna-project/packages/dotenv
error: could not write production lockfile for workspace

    "askluna-dotenv @ {root:uri}/../packages/dotenv" =>error: Distribution not found at: file:///Users/shravansunder/Documents/dev/project-dev/askluna-project/askluna/apps/packages/dotenv

So for some reason, ../../ seems to traverse by more than 2 folders up instead of exactly 2 folders.   And ../ only traverses 1 folder up

Isn't {root:uri} a Hatch thing? What does it resolve to?

I don't know that uv has any control over how that URL gets resolved. I believe we just ask Hatch for the metadata, and it returns the resolved file path.

i'll create a issue in their repo as well.  https://github.com/pypa/hatch/issues/1570
Related question @charliermarsh so with uv (and ruff) whats the recommended mechanism to point to a local package in a monorepo.  I've searched all the issues and unable to find a solution that doesn't use absolute paths from user folder.
I can make a related discussion if that's better for this


Separate thirdparty dirs

@undera , are those merge commits required in this PR?
Can you rebase "Separate thirdparty dirs" commit on top of trunk?

The git commits won't go into SVN anyway, but I'll try to rebase.


Added visibility settings

Subclasses ExportTask to FormatTask, and assigns some tasks like GeoPackage, Styles, and Shapefiles the new class.
Adds display setting to ExportProviderTask, ExportProvider, and ExportTask models.
ExportProvider can be toggled in the admin console.
To test create an OSM Themes export and view the Run in the API.  Themes Provider should have display: true, and the generic provider should have display: false.  Additionally most formats should have display: false with the exception of the Geopackage export, the QGIS export and the Zip File export (if enabled).

Coverage increased (+0.06%) to 83.236% when pulling b67cddad943890d64d2498a6f6b89675dfb21ca0 on 23387-AddVisibilitySetting into 5730553a7ac0cbccfd650833d752e7d1dc4fcee3 on master.

Coverage increased (+0.06%) to 83.236% when pulling b67cddad943890d64d2498a6f6b89675dfb21ca0 on 23387-AddVisibilitySetting into 5730553a7ac0cbccfd650833d752e7d1dc4fcee3 on master.

Coverage increased (+0.06%) to 83.277% when pulling f8a9368f905c0a8d945785920f0947a15f9fd6f6 on 23387-AddVisibilitySetting into 32fa16ef2adb620d284404f9a68cc38f44c2afd8 on master.

Coverage increased (+0.09%) to 83.311% when pulling 48dd98779e3fe3452a1975a89b59271de441a7fa on 23387-AddVisibilitySetting into 32fa16ef2adb620d284404f9a68cc38f44c2afd8 on master.


up go 1.22.3

The following changes have been made:

added new possible error based on platform and Go release
changed the work with encoding/json - https://go.dev/doc/go1.22#minor_library_changes.
Marshaling and encoding functionality now escapes '\b' and '\f' characters as \b and \f instead of \u0008 and \u000c.
The creators of go overmuch with the change of cover work. So far I have turned on the old flag of cover operation - GOEXPERIMENT=nocoverageredesign. I will open a question in the go community. Most likely in the next release of go it will be necessary to remove this flag.

The creators of go overmuch with the change of cover work. So far I have turned on the old flag of cover operation - GOEXPERIMENT=nocoverageredesign. I will open a question in the go community. Most likely in the next release of go it will be necessary to remove this flag.

I do not think this is should be a fix and need to have better understanding of the root cause for the unit tests in failure.

The creators of go overmuch with the change of cover work. So far I have turned on the old flag of cover operation - GOEXPERIMENT=nocoverageredesign. I will open a question in the go community. Most likely in the next release of go it will be necessary to remove this flag.

I do not think this is should be a fix and need to have better understanding of the root cause for the unit tests in failure.

All right. I got it. I'll find a better explanation for why they're like this.

@C0rWin @denyeart
I was able to simulate the error.
The error is definitely not in fabric, it's in go. At a certain stage the test has an extra file covervars.go. Because of this, the test and plugin have different versions of the same package.
I'll pass it all on to the go developers from here on out.
Here's my example of the error appearing.
https://github.com/pfi79/go-test-cover-error

@C0rWin @denyeart
I was able to simulate the error. The error is definitely not in fabric, it's in go. At a certain stage the test has an extra file covervars.go. Because of this, the test and plugin have different versions of the same package.
I'll pass it all on to the go developers from here on out.
Here's my example of the error appearing. https://github.com/pfi79/go-test-cover-error

Ok, thanks for investigating and opening the dialog with the Go team. Please add a link to that conversation here. Let's keep this PR on hold for now, perhaps Go team will offer another solution. Alternatively, if they agree to work on a fix we could potentially use the GOEXPERIMENT=nocoverageredesign workaround until the fix is available.

@denyeart @C0rWin I got an answer.
The error is no longer reproduced in version 1.23.
There are 2 variants of action:

Wait for go version 1.23 and try it already.
Now accept pr with GOEXPERIMENT=nocoverageredesign. When go 1.23 appears, check and if successful, remove GOEXPERIMENT=nocoverageredesign.

I'll add more details

go developers started to change cover to allow to take into account those packages that do not have test files, but functions are called from them when running tests.

Further implementation problems:

when forming a test plan, when several packages are passed there, their compilation cache is common for all tests.
core/handlers/endorsement/api package as a separate package for testing is processed in a special way and some covervars.go file is added to its cache.
our test from core/handlers/library depends on the core/handlers/endorsement/api package and with the cover.go file compiles it into the body of the executable.
Next, the test sends a command to build a plugin. The plugin also depends on core/handlers/endorsement/api, but it is built independently of the test. Therefore, it does not know anything about the covervars.go file.
And we try to open the plugin, but the core/handlers/endorsement/api package is really different in the test and in the plugin

Since it appears to be resolved in upcoming Go 1.23, I'd be willing to live with the workaround GOEXPERIMENT=nocoverageredesign for the duration of Go 1.22. Let's see if others agree...

Since it appears to be resolved in upcoming Go 1.23, I'd be willing to live with the workaround GOEXPERIMENT=nocoverageredesign for the duration of Go 1.22. Let's see if others agree...

Well, this is not really a production code matter, so I think it's fine. However, IMO, we can just skip 1.22 and wait for 1.23 since I do not think there is something urgent that might require an immediate update to 1.22.

Since it appears to be resolved in upcoming Go 1.23, I'd be willing to live with the workaround GOEXPERIMENT=nocoverageredesign for the duration of Go 1.22. Let's see if others agree...

Well, this is not really a production code matter, so I think it's fine. However, IMO, we can just skip 1.22 and wait for 1.23 since I do not think there is something urgent that might require an immediate update to 1.22.

I do like to step through every Go release... if some problem shows up it is easier to pinpoint the issue by looking at that version's Go release notes. There will also be a growing list of CVEs on Go 1.21 so I'm motivated to get to 1.22 soon and backport for a v2.5.8 release.
Let's see if there are any other comments in the next day, otherwise I'll plan to approve and merge.


Pick some pr to 30 #44779 #44786 #44857

What problem does this PR solve?
5ce76049
https://github.com/apache/doris/pull/44779
d350e3c5
https://github.com/apache/doris/pull/44786
8ea48afc
https://github.com/apache/doris/pull/44857
Issue Number: close #xxx
Related PR: #xxx
Problem Summary:
Release note
None
Check List (For Author)

Test

[ ] Regression test
[ ] Unit Test
[ ] Manual test (add detailed scripts or steps below)
[ ] No need to test or manual test. Explain why:

[ ] This is a refactor/code format and no logic has been changed.
[ ] Previous test can cover this change.
[ ] No code files have been changed.
[ ] Other reason

Behavior changed:

[ ] No.
[ ] Yes.

Does this need documentation?

[ ] No.
[ ] Yes.

Check List (For Reviewer who merge this PR)

[ ] Confirm the release note
[ ] Confirm test cases
[ ] Confirm document
[ ] Add branch pick label

run buildall

run buildall


Publish multi-arch docker images and binaries for arm64, amd64

Signed-off-by: Josh Kneubuhl<EMAIL_ADDRESS>Type of change

New feature

Description
Builds multi-arch Docker images and native binaries for arm64 and amd64.
Additional details
This PR is a "cherry-pick" (back/forward) port of the following PRs from the release-2.5 branch "up" into the mainline:

PR #3843
PR #3839
PR #3837
PR #3836

Related issues

#2994

I think this looks good and is an accurate forward port of the release-2.5 changes that have been validated in that branch.
The changes to the Dockerfiles are slightly different than what was done in release-2.5, because Artem @C0rWin has previously updated the Dockerfiles for ARM in https://github.com/hyperledger/fabric/commit/ac31c577a2f5804906b6d0d263a5efc5f674eed8. So let's ask @C0rWin to review also and make sure he is good with this approach.

The etcdraft unit test failure is a known flake and can be ignored, it is being looked at by @Param-S

I'll go ahead and merge to keep the branches consistent, but @C0rWin and others please do holler if you see anything not correct.

Note that subsequent PR https://github.com/hyperledger/fabric/pull/3857 reversed some of this.
As of https://github.com/hyperledger/fabric/pull/3857, the locally built peer images will continue to be created as dynamically linked binaries, with the static linking enabled only for the release target and for binaries deployed to alpine in Docker.


.vfe implementation

Solves #142

Add a test file, just checking that a full exported text file matches is enough.

If it did, those files would also have to swap streams I guess.

We need to implement some shared/common way to export these.

VRF GUI can decompile vfe to txt
VRF Decompiler (with -d) return compiled vfe file


Integrate fast entrypoint selection into new deployment multi-stepper

Intent

This PR updates the new deployment multi-stepper and breaks up the previous page which showed both entrypoint files as well as content types, into two pages. Switching to the two pages allows us to remove the expensive deep recursion required to inspect all possible entry points. With the change, we perform a quick directory walk looking only at the file extensions, and then once one of these is selected, we inspect the file to determine its content type / initial configuration file.
To support the selection of an entrypoint file, I have separated the list items for the potential entrypoint files that are opened within VSCode vs. the ones which are present within the VSCode workspace.

When the entrypoint selected could be deployed in multiple ways, we present an additional step to handle the selection.

When the entrypoint can be only one content type, we suppress this page.
Resolves #2045
Resolves #2046
Type of Change

[ ] Bug Fix

[x] New Feature

[ ] Breaking Change

[ ] Documentation

[x] Refactor

[ ] Tooling

Approach

Changes included here:

The new /entrypoints API was integrated into the UX codebase
The agent code was updated to perform case-insensitive comparisons when identifying possible entrypoint files.
The flow associated with the new deployment multi-stepper was updated.

Automated Tests

Directions for Reviewers

Note that I have separated functionality into individual commits to help with a more understandable review.
These changes are only in effect for the newDeployment flow. To verify:

Invoke the new Deployment flow
Select an entrypoint which can have multiple content types (like an RMD file), and verify that content-type selection page follows the entrypoint selection page
Verify that selection of an entrypoint file that can be only one type does not show the content-type selection page.
Verify that moving forward and back, update the current page numbers and total page numbers correctly.
Verify an error is displayed when there are no files that qualify as entry points available to be found.
Verify this functionality on large project hierarchies and small ones.

Checklist

[ ] I have updated CHANGELOG.md to cover notable changes.

I noticed that if I select the empty.ipynb notebook we have in the sample-content repo that I was not given an error - things just went forward. I think this is because the inspect API will return an unknown configuration when an entrypoint is specified.
But that leads me to a state where I have an error in my config (since type = 'unknown' is invalid). This also immediately causes an error in our refresh file lists API.

I recreated the invalid configuration file (due to unknown), but I'm not seeing any refresh error.

This feels like an unrelated bug to this PR. Can we separate it?

I noticed that if I select the empty.ipynb notebook we have in the sample-content repo that I was not given an error - things just went forward. I think this is because the inspect API will return an unknown configuration when an entrypoint is specified.

empty.ipynb isn't a valid notebook - it is an empty file instead of valid JSON, so it can't be deployed. #2038 made this return an unknown configuration instead of erroring out during inspection.


Add expected behavior for null values to decode functions

What does this pull request do?
Renames decode combinators and introduces a new one that treats null values as missing values. See discussion here: #32
The reason for this boils down to the current combinators not behaving as most users would expect, but updating their behavior would break existing codebases without them knowing. So the solution was to rename the functions altogether, now matching their analogues in Haskell's Aeson library.
Also added some tests. I couldn't figure out how to test the decode combinators with QuickCheck. Even for the existing tests, the one that claimed to be testing .? (now .:) wasn't. So instead I added a suite of manual tests.
Where should the reviewer start?
src/Data/Argonaut/Decode/Combinators.purs contains the meat of the updates. Then the tests also illustrate the intended behavior.
How should this be manually tested?
Beyond running the tests, if you have any projects that use this library you could test those.
Other Notes:
This is a breaking change and will require a major version bump.

I'm in favor of this change. The combinators have the same functionality, but now match the highly-similar Aeson library more closely. There's now a more intuitive alternative to getFieldOptional, which has been a problem for me in the past and caused the issue you linked, https://github.com/purescript-contrib/purescript-argonaut-codecs/issues/32. And I appreciate the tests and added documentation.
I'd like to leave this open for some time to let others affected by the change weigh in. I've cross-posted to Discourse to get a little more visibility as well.

Is there a reason to not also keep the old combinators, possibly marking them as deprecated with a warning?

Yes, if the only reason it is breaking is because we are removing a few functions, then I'd recommend just leaving them where they are and discouraging their use, possibly removing them with the next breaking compiler release.

possibly marking them as deprecated with a warning?

@natefaubion are you suggesting something like the Warn typeclass (https://liamgoodacre.github.io/purescript/warnings/2017/01/17/purescript-warn-type-class.html) or is that a little much?

It's aggressive, but I don't mind adding the type class warning if we're planning to remove them altogether in a future version of the library. Better to see the warnings in your build output than to never see them at all until it actually switches IMO. If you've been using the library for a while, then you may not be looking at the docs very often anymore.

Okay, I've added them back. Had to alias the original functions so that I could add the Warn constraint to the old operators without affecting the new ones, so now the file's really cluttered. I don't think it's a big deal though

Something to consider here - renaming the functions, even if the operator names are preserved, is still a breaking change, since people could have been using the named variants.

@garyb I believe @davezuch did preserve the original names with their original implementations (but new operators) when reverting, and the old operators have the old implementations but under new names. In a way, folks will now be using 'new' functions when they use the old operators, but the implementations are exactly the same except with the new Warn constraint. Then, he added another function / operator on top to handle this null issue.
IMO that shouldn't constitute a breaking change even if technically it is true that the functions have been renamed, because existing code shouldn't break. I've pulled this down on a personal project and things seem OK; I know CitizenNet has a lot of code exercising all these operators and occasionally named variants; might be a useful mini-test to make sure that stuff doesn't break @davezuch

For anyone using the named functions, nothing will change. For those using the existing operators, now they'll get compiler warnings telling them to use the new operators. Does that constitute a breaking change? I don't think it should, though I can see the argument for it

I'd like to leave this open for another day or two, and then I think it's ready to merge as a minor release (non-breaking). However, if folks disagree, then I can hold off.

Might be a good idea to note in the project readme that this is now meant to be closer to Aeson than Argonaut. I haven't used either of those other libraries but it's what I gather from reading the discussion so far. That note can be added as part of a different PR, though. I can add it to https://github.com/purescript-contrib/purescript-argonaut-codecs/issues/48 if you'd rather not add more commits, no problem.

Looks like this project moved towards Aeson a long time ago, actually: https://github.com/purescript-contrib/purescript-argonaut-codecs/pull/12
I'll just add a note to the other issue about updating the readme. 👍

I'm merging now. Thanks for your work on this, @davezuch.

A bit late, but this looks very welcome :)
Makes the switch from/to Haskell easier too.


Failed to run 7nodes at geth execution

I am running the 7nodes examples with the vagrant setup and the run is stopping with the ./raft-init.sh execution itself. The run terminates with the following message
$ ./raft-init.sh
[] Cleaning up temporary data directories
[] Configuring node 1 (permissioned)
INFO [06-15|07:14:43] Allocated cache and file handles database=/vagrant/examples/7nodes/qdata/dd1/geth/chaindata cache=16 handles=16
Fatal: Failed to open database: sync /vagrant/examples/7nodes/qdata/dd1/geth/chaindata: invalid argument
I also found a lock in the data directory
$ ls qdata/dd1/geth/chaindata/
CURRENT LOCK LOG
I had made some progress by moving the qdata ( data directory ) from the vagrant shared directory to the VM home directory (/home/vagrant/qdata) but even with that I eventually ran into an IPC socket file issue. So I stopped with that direction as well.

Expected behaviour
The initialization proceeds smoothly
Actual behaviour
$ ./raft-init.sh
[] Cleaning up temporary data directories
[] Configuring node 1 (permissioned)
INFO [06-15|07:14:43] Allocated cache and file handles database=/vagrant/examples/7nodes/qdata/dd1/geth/chaindata cache=16 handles=16
Fatal: Failed to open database: sync /vagrant/examples/7nodes/qdata/dd1/geth/chaindata: invalid argument
Steps to reproduce the behaviour
% git clone https://github.com/jpmorganchase/quorum-examples
% cd quorum-examples
% vagrant up
% vagrant ssh
% cd /vagrant/examples/7nodes/
% raft-init.sh
Backtrace
[] Cleaning up temporary data directories
[] Configuring node 1 (permissioned)
INFO [06-15|07:14:43] Allocated cache and file handles database=/vagrant/examples/7nodes/qdata/dd1/geth/chaindata cache=16 handles=16
Fatal: Failed to open database: sync /vagrant/examples/7nodes/qdata/dd1/geth/chaindata: invalid argument

Hi @aroommen please make sure you are executing it in the vagrant environment. From your exmaple above, it looks like you are running it in your host os.

@fixanoid Thanks for the response. I was actually running this on vagrant environment although I have not included that as part of the run steps. Since then I have been able to get this to run by doing manual installation of each of the pieces as listed in the vagrant/bootstrap.sh file and increasing the memory limit to about 4gb ( actual consumption is less than 3gb) in the VM.
I think something might be off with this part of the bootstrap.sh
Line 41
chown -R vagrant:vagrant /home/vagrant/quorum /home/vagrant/quorum-examples
or could it be just a memory limit issue.

even i'm getting this same issue..
vagrant@ubuntu-xenial:~/quorum-examples/examples/7nodes$ sudo ./raft-init.sh
[] Cleaning up temporary data directories
[] Configuring node 1 (permissioned)
./raft-init.sh: line 15: geth: command not found
need help..

@sherrygarg can you please open a new issue for this?


Support verilator for verilog

I've added verilator for verilog.

I see no problems with this. Cheers! :beers:


Add Python 3 Trove classifier ("Programming Language :: Python :: 3") to setup.py

This will let people and tools (e.g.: https://python3wos.appspot.com/) know that yolk is compatible with Python 3.
Should do a release to PyPI; it seems that the latest code in GitHub works with Python 3, but the last released version on PyPI (0.4.3; released 2012-02-06) doesn't work with Python 3.

Bump.


Error while running the code.Please resolve asap.

I am getting an error when compiling the code SpeechRecogonizerMain.java
Can you please resolve this for me
Sep 17, 2017 10:25:58 AM model.SpeechRecognizerMain
INFO: Loading Speech Recognizer...
10:26:02.393 INFO unitManager          CI Unit: *+NSN+
10:26:02.414 INFO unitManager          CI Unit: *+SPN+
10:26:02.414 INFO unitManager          CI Unit: AA
10:26:02.414 INFO unitManager          CI Unit: AE
10:26:02.414 INFO unitManager          CI Unit: AH
10:26:02.414 INFO unitManager          CI Unit: AO
10:26:02.414 INFO unitManager          CI Unit: AW
10:26:02.414 INFO unitManager          CI Unit: AY
10:26:02.414 INFO unitManager          CI Unit: B
10:26:02.414 INFO unitManager          CI Unit: CH
10:26:02.414 INFO unitManager          CI Unit: D
10:26:02.414 INFO unitManager          CI Unit: DH
10:26:02.418 INFO unitManager          CI Unit: EH
10:26:02.418 INFO unitManager          CI Unit: ER
10:26:02.418 INFO unitManager          CI Unit: EY
10:26:02.418 INFO unitManager          CI Unit: F
10:26:02.418 INFO unitManager          CI Unit: G
10:26:02.418 INFO unitManager          CI Unit: HH
10:26:02.418 INFO unitManager          CI Unit: IH
10:26:02.418 INFO unitManager          CI Unit: IY
10:26:02.418 INFO unitManager          CI Unit: JH
10:26:02.418 INFO unitManager          CI Unit: K
10:26:02.418 INFO unitManager          CI Unit: L
10:26:02.418 INFO unitManager          CI Unit: M
10:26:02.422 INFO unitManager          CI Unit: N
10:26:02.422 INFO unitManager          CI Unit: NG
10:26:02.422 INFO unitManager          CI Unit: OW
10:26:02.422 INFO unitManager          CI Unit: OY
10:26:02.422 INFO unitManager          CI Unit: P
10:26:02.422 INFO unitManager          CI Unit: R
10:26:02.422 INFO unitManager          CI Unit: S
10:26:02.422 INFO unitManager          CI Unit: SH
10:26:02.422 INFO unitManager          CI Unit: T
10:26:02.422 INFO unitManager          CI Unit: TH
10:26:02.422 INFO unitManager          CI Unit: UH
10:26:02.422 INFO unitManager          CI Unit: UW
10:26:02.422 INFO unitManager          CI Unit: V
10:26:02.422 INFO unitManager          CI Unit: W
10:26:02.426 INFO unitManager          CI Unit: Y
10:26:02.426 INFO unitManager          CI Unit: Z
10:26:02.426 INFO unitManager          CI Unit: ZH
10:26:04.391 INFO autoCepstrum         Cepstrum component auto-configured as follows: autoCepstrum {MelFrequencyFilterBank, Denoise, DiscreteCosineTransform2, Lifter}
Exception in thread "main" java.lang.Error: Unresolved compilation problems:
Syntax error on tokens, delete these tokens
Syntax error on token(s), misplaced construct(s)
Syntax error on token ")", delete this token
at model.SpeechRecognizerMain.startResourcesThread(SpeechRecognizerMain.java:202)
at model.SpeechRecognizerMain.<init>(SpeechRecognizerMain.java:103)
at model.SpeechRecognizerMain.main(SpeechRecognizerMain.java:251)

Hello my friend :)
I want you to report this on Java Speech Recognize Github issues so I can
give you detailed answer.
Which tutorials is this 1,2,3,4?
Did you modified the code?
Did you followed the latest tutorial I released this September?
Cheers Alex K.
Στις 17 Σεπ 2017 07:58, ο χρήστης "san1197"<EMAIL_ADDRESS>έγραψε:
I am getting an error when compiling the code SpeechRecogonizerMain.java
Can you please resolve this for me
Sep 17, 2017 10:25:58 AM model.SpeechRecognizerMain
INFO: Loading Speech Recognizer...
10:26:02.393 INFO unitManager CI Unit: *+NSN+
10:26:02.414 INFO unitManager CI Unit: *+SPN+
10:26:02.414 INFO unitManager CI Unit: AA
10:26:02.414 INFO unitManager CI Unit: AE
10:26:02.414 INFO unitManager CI Unit: AH
10:26:02.414 INFO unitManager CI Unit: AO
10:26:02.414 INFO unitManager CI Unit: AW
10:26:02.414 INFO unitManager CI Unit: AY
10:26:02.414 INFO unitManager CI Unit: B
10:26:02.414 INFO unitManager CI Unit: CH
10:26:02.414 INFO unitManager CI Unit: D
10:26:02.414 INFO unitManager CI Unit: DH
10:26:02.418 INFO unitManager CI Unit: EH
10:26:02.418 INFO unitManager CI Unit: ER
10:26:02.418 INFO unitManager CI Unit: EY
10:26:02.418 INFO unitManager CI Unit: F
10:26:02.418 INFO unitManager CI Unit: G
10:26:02.418 INFO unitManager CI Unit: HH
10:26:02.418 INFO unitManager CI Unit: IH
10:26:02.418 INFO unitManager CI Unit: IY
10:26:02.418 INFO unitManager CI Unit: JH
10:26:02.418 INFO unitManager CI Unit: K
10:26:02.418 INFO unitManager CI Unit: L
10:26:02.418 INFO unitManager CI Unit: M
10:26:02.422 INFO unitManager CI Unit: N
10:26:02.422 INFO unitManager CI Unit: NG
10:26:02.422 INFO unitManager CI Unit: OW
10:26:02.422 INFO unitManager CI Unit: OY
10:26:02.422 INFO unitManager CI Unit: P
10:26:02.422 INFO unitManager CI Unit: R
10:26:02.422 INFO unitManager CI Unit: S
10:26:02.422 INFO unitManager CI Unit: SH
10:26:02.422 INFO unitManager CI Unit: T
10:26:02.422 INFO unitManager CI Unit: TH
10:26:02.422 INFO unitManager CI Unit: UH
10:26:02.422 INFO unitManager CI Unit: UW
10:26:02.422 INFO unitManager CI Unit: V
10:26:02.422 INFO unitManager CI Unit: W
10:26:02.426 INFO unitManager CI Unit: Y
10:26:02.426 INFO unitManager CI Unit: Z
10:26:02.426 INFO unitManager CI Unit: ZH
10:26:04.391 INFO autoCepstrum Cepstrum component auto-configured as
follows: autoCepstrum {MelFrequencyFilterBank, Denoise,
DiscreteCosineTransform2, Lifter}
Exception in thread "main" java.lang.Error: Unresolved compilation problems:
Syntax error on tokens, delete these tokens
Syntax error on token(s), misplaced construct(s)
Syntax error on token ")", delete this token
at model.SpeechRecognizerMain.startResourcesThread(SpeechRecognizerMain.java:202)
at model.SpeechRecognizerMain.(SpeechRecognizerMain.java:103)
at model.SpeechRecognizerMain.main(SpeechRecognizerMain.java:251)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/goxr3plus/Java-Speech-Recognizer-Tutorial--Calculator/issues/6,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATbiwDuG-1bWBFwlFAYFHfk7CmEP7Ntuks5sjKbZgaJpZM4PaCoy
.

Hi sir.
Thanks for responding.
This is the first tutorial.I am getting syntax errors in four lines during
Executor service.Can u send me the link for the latest video?
Thank you.
On Sun, Sep 17, 2017 at 7:12 PM, GOXR3PLUS STUDIO<EMAIL_ADDRESS>wrote:

Hello my friend :)
I want you to report this on Java Speech Recognize Github issues so I can
give you detailed answer.
Which tutorials is this 1,2,3,4?
Did you modified the code?
Did you followed the latest tutorial I released this September?
Cheers Alex K.
Στις 17 Σεπ 2017 07:58, ο χρήστης "san1197"<EMAIL_ADDRESS>έγραψε:
I am getting an error when compiling the code SpeechRecogonizerMain.java
Can you please resolve this for me
Sep 17, 2017 10:25:58 AM model.SpeechRecognizerMain
INFO: Loading Speech Recognizer...
10:26:02.393 INFO unitManager CI Unit: *+NSN+
10:26:02.414 INFO unitManager CI Unit: *+SPN+
10:26:02.414 INFO unitManager CI Unit: AA
10:26:02.414 INFO unitManager CI Unit: AE
10:26:02.414 INFO unitManager CI Unit: AH
10:26:02.414 INFO unitManager CI Unit: AO
10:26:02.414 INFO unitManager CI Unit: AW
10:26:02.414 INFO unitManager CI Unit: AY
10:26:02.414 INFO unitManager CI Unit: B
10:26:02.414 INFO unitManager CI Unit: CH
10:26:02.414 INFO unitManager CI Unit: D
10:26:02.414 INFO unitManager CI Unit: DH
10:26:02.418 INFO unitManager CI Unit: EH
10:26:02.418 INFO unitManager CI Unit: ER
10:26:02.418 INFO unitManager CI Unit: EY
10:26:02.418 INFO unitManager CI Unit: F
10:26:02.418 INFO unitManager CI Unit: G
10:26:02.418 INFO unitManager CI Unit: HH
10:26:02.418 INFO unitManager CI Unit: IH
10:26:02.418 INFO unitManager CI Unit: IY
10:26:02.418 INFO unitManager CI Unit: JH
10:26:02.418 INFO unitManager CI Unit: K
10:26:02.418 INFO unitManager CI Unit: L
10:26:02.418 INFO unitManager CI Unit: M
10:26:02.422 INFO unitManager CI Unit: N
10:26:02.422 INFO unitManager CI Unit: NG
10:26:02.422 INFO unitManager CI Unit: OW
10:26:02.422 INFO unitManager CI Unit: OY
10:26:02.422 INFO unitManager CI Unit: P
10:26:02.422 INFO unitManager CI Unit: R
10:26:02.422 INFO unitManager CI Unit: S
10:26:02.422 INFO unitManager CI Unit: SH
10:26:02.422 INFO unitManager CI Unit: T
10:26:02.422 INFO unitManager CI Unit: TH
10:26:02.422 INFO unitManager CI Unit: UH
10:26:02.422 INFO unitManager CI Unit: UW
10:26:02.422 INFO unitManager CI Unit: V
10:26:02.422 INFO unitManager CI Unit: W
10:26:02.426 INFO unitManager CI Unit: Y
10:26:02.426 INFO unitManager CI Unit: Z
10:26:02.426 INFO unitManager CI Unit: ZH
10:26:04.391 INFO autoCepstrum Cepstrum component auto-configured as
follows: autoCepstrum {MelFrequencyFilterBank, Denoise,
DiscreteCosineTransform2, Lifter}
Exception in thread "main" java.lang.Error: Unresolved compilation
problems:
Syntax error on tokens, delete these tokens
Syntax error on token(s), misplaced construct(s)
Syntax error on token ")", delete this token
at model.SpeechRecognizerMain.startResourcesThread(
SpeechRecognizerMain.java:202)
at model.SpeechRecognizerMain.(SpeechRecognizerMain.java:103)
at model.SpeechRecognizerMain.main(SpeechRecognizerMain.java:251)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/goxr3plus/Java-Speech-Recognizer-
Tutorial--Calculator/issues/6>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATbiwDuG-
1bWBFwlFAYFHfk7CmEP7Ntuks5sjKbZgaJpZM4PaCoy>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/goxr3plus/Java-Speech-Recognizer-Tutorial--Calculator/issues/6#issuecomment-330045623,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeeQSqsGbOfi9zQwKm793xjn4DEVJYqnks5sjSHZgaJpZM4PaCoy
.

--

Sandya*

I have to complete the speech calculator mini project by two weeks.Kindly
help :)
On Sun, Sep 17, 2017 at 8:04 PM, Sandya Manoharan<EMAIL_ADDRESS>wrote:

Hi sir.
Thanks for responding.
This is the first tutorial.I am getting syntax errors in four lines during
Executor service.Can u send me the link for the latest video?
Thank you.
On Sun, Sep 17, 2017 at 7:12 PM, GOXR3PLUS STUDIO <
<EMAIL_ADDRESS>wrote:

Hello my friend :)
I want you to report this on Java Speech Recognize Github issues so I can
give you detailed answer.
Which tutorials is this 1,2,3,4?
Did you modified the code?
Did you followed the latest tutorial I released this September?
Cheers Alex K.
Στις 17 Σεπ 2017 07:58, ο χρήστης "san1197"<EMAIL_ADDRESS>έγραψε:
I am getting an error when compiling the code SpeechRecogonizerMain.java
Can you please resolve this for me
Sep 17, 2017 10:25:58 AM model.SpeechRecognizerMain
INFO: Loading Speech Recognizer...
10:26:02.393 INFO unitManager CI Unit: *+NSN+
10:26:02.414 INFO unitManager CI Unit: *+SPN+
10:26:02.414 INFO unitManager CI Unit: AA
10:26:02.414 INFO unitManager CI Unit: AE
10:26:02.414 INFO unitManager CI Unit: AH
10:26:02.414 INFO unitManager CI Unit: AO
10:26:02.414 INFO unitManager CI Unit: AW
10:26:02.414 INFO unitManager CI Unit: AY
10:26:02.414 INFO unitManager CI Unit: B
10:26:02.414 INFO unitManager CI Unit: CH
10:26:02.414 INFO unitManager CI Unit: D
10:26:02.414 INFO unitManager CI Unit: DH
10:26:02.418 INFO unitManager CI Unit: EH
10:26:02.418 INFO unitManager CI Unit: ER
10:26:02.418 INFO unitManager CI Unit: EY
10:26:02.418 INFO unitManager CI Unit: F
10:26:02.418 INFO unitManager CI Unit: G
10:26:02.418 INFO unitManager CI Unit: HH
10:26:02.418 INFO unitManager CI Unit: IH
10:26:02.418 INFO unitManager CI Unit: IY
10:26:02.418 INFO unitManager CI Unit: JH
10:26:02.418 INFO unitManager CI Unit: K
10:26:02.418 INFO unitManager CI Unit: L
10:26:02.418 INFO unitManager CI Unit: M
10:26:02.422 INFO unitManager CI Unit: N
10:26:02.422 INFO unitManager CI Unit: NG
10:26:02.422 INFO unitManager CI Unit: OW
10:26:02.422 INFO unitManager CI Unit: OY
10:26:02.422 INFO unitManager CI Unit: P
10:26:02.422 INFO unitManager CI Unit: R
10:26:02.422 INFO unitManager CI Unit: S
10:26:02.422 INFO unitManager CI Unit: SH
10:26:02.422 INFO unitManager CI Unit: T
10:26:02.422 INFO unitManager CI Unit: TH
10:26:02.422 INFO unitManager CI Unit: UH
10:26:02.422 INFO unitManager CI Unit: UW
10:26:02.422 INFO unitManager CI Unit: V
10:26:02.422 INFO unitManager CI Unit: W
10:26:02.426 INFO unitManager CI Unit: Y
10:26:02.426 INFO unitManager CI Unit: Z
10:26:02.426 INFO unitManager CI Unit: ZH
10:26:04.391 INFO autoCepstrum Cepstrum component auto-configured as
follows: autoCepstrum {MelFrequencyFilterBank, Denoise,
DiscreteCosineTransform2, Lifter}
Exception in thread "main" java.lang.Error: Unresolved compilation
problems:
Syntax error on tokens, delete these tokens
Syntax error on token(s), misplaced construct(s)
Syntax error on token ")", delete this token
at model.SpeechRecognizerMain.startResourcesThread(SpeechRecogn
izerMain.java:202)
at model.SpeechRecognizerMain.(SpeechRecognizerMain.java:103)
at model.SpeechRecognizerMain.main(SpeechRecognizerMain.java:251)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/goxr3plus/Java-Speech-Recognizer-Tutoria
l--Calculator/issues/6>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATbiwDuG-
1bWBFwlFAYFHfk7CmEP7Ntuks5sjKbZgaJpZM4PaCoy>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/goxr3plus/Java-Speech-Recognizer-Tutorial--Calculator/issues/6#issuecomment-330045623,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AeeQSqsGbOfi9zQwKm793xjn4DEVJYqnks5sjSHZgaJpZM4PaCoy
.

--

Sandya*

--

Sandya*

It's called JAVA SPHINX4-5 FULL EXPLANATION OF EVERYTHING 07/09/2017
It's easy to find it on my channel videos section :)
Στις 17 Σεπ 2017 17:41, ο χρήστης "san1197"<EMAIL_ADDRESS>έγραψε:

I have to complete the speech calculator mini project by two weeks.Kindly
help :)
On Sun, Sep 17, 2017 at 8:04 PM, Sandya Manoharan<EMAIL_ADDRESS>wrote:

Hi sir.
Thanks for responding.
This is the first tutorial.I am getting syntax errors in four lines
during
Executor service.Can u send me the link for the latest video?
Thank you.
On Sun, Sep 17, 2017 at 7:12 PM, GOXR3PLUS STUDIO <
<EMAIL_ADDRESS>wrote:

Hello my friend :)
I want you to report this on Java Speech Recognize Github issues so I
can
give you detailed answer.
Which tutorials is this 1,2,3,4?
Did you modified the code?
Did you followed the latest tutorial I released this September?
Cheers Alex K.
Στις 17 Σεπ 2017 07:58, ο χρήστης "san1197"<EMAIL_ADDRESS>έγραψε:
I am getting an error when compiling the code SpeechRecogonizerMain.java
Can you please resolve this for me
Sep 17, 2017 10:25:58 AM model.SpeechRecognizerMain
INFO: Loading Speech Recognizer...
10:26:02.393 INFO unitManager CI Unit: *+NSN+
10:26:02.414 INFO unitManager CI Unit: *+SPN+
10:26:02.414 INFO unitManager CI Unit: AA
10:26:02.414 INFO unitManager CI Unit: AE
10:26:02.414 INFO unitManager CI Unit: AH
10:26:02.414 INFO unitManager CI Unit: AO
10:26:02.414 INFO unitManager CI Unit: AW
10:26:02.414 INFO unitManager CI Unit: AY
10:26:02.414 INFO unitManager CI Unit: B
10:26:02.414 INFO unitManager CI Unit: CH
10:26:02.414 INFO unitManager CI Unit: D
10:26:02.414 INFO unitManager CI Unit: DH
10:26:02.418 INFO unitManager CI Unit: EH
10:26:02.418 INFO unitManager CI Unit: ER
10:26:02.418 INFO unitManager CI Unit: EY
10:26:02.418 INFO unitManager CI Unit: F
10:26:02.418 INFO unitManager CI Unit: G
10:26:02.418 INFO unitManager CI Unit: HH
10:26:02.418 INFO unitManager CI Unit: IH
10:26:02.418 INFO unitManager CI Unit: IY
10:26:02.418 INFO unitManager CI Unit: JH
10:26:02.418 INFO unitManager CI Unit: K
10:26:02.418 INFO unitManager CI Unit: L
10:26:02.418 INFO unitManager CI Unit: M
10:26:02.422 INFO unitManager CI Unit: N
10:26:02.422 INFO unitManager CI Unit: NG
10:26:02.422 INFO unitManager CI Unit: OW
10:26:02.422 INFO unitManager CI Unit: OY
10:26:02.422 INFO unitManager CI Unit: P
10:26:02.422 INFO unitManager CI Unit: R
10:26:02.422 INFO unitManager CI Unit: S
10:26:02.422 INFO unitManager CI Unit: SH
10:26:02.422 INFO unitManager CI Unit: T
10:26:02.422 INFO unitManager CI Unit: TH
10:26:02.422 INFO unitManager CI Unit: UH
10:26:02.422 INFO unitManager CI Unit: UW
10:26:02.422 INFO unitManager CI Unit: V
10:26:02.422 INFO unitManager CI Unit: W
10:26:02.426 INFO unitManager CI Unit: Y
10:26:02.426 INFO unitManager CI Unit: Z
10:26:02.426 INFO unitManager CI Unit: ZH
10:26:04.391 INFO autoCepstrum Cepstrum component auto-configured as
follows: autoCepstrum {MelFrequencyFilterBank, Denoise,
DiscreteCosineTransform2, Lifter}
Exception in thread "main" java.lang.Error: Unresolved compilation
problems:
Syntax error on tokens, delete these tokens
Syntax error on token(s), misplaced construct(s)
Syntax error on token ")", delete this token
at model.SpeechRecognizerMain.startResourcesThread(SpeechRecogn
izerMain.java:202)
at model.SpeechRecognizerMain.(SpeechRecognizerMain.java:103)
at model.SpeechRecognizerMain.main(SpeechRecognizerMain.java:251)
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
<https://github.com/goxr3plus/Java-Speech-Recognizer-Tutoria
l--Calculator/issues/6>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/ATbiwDuG-
1bWBFwlFAYFHfk7CmEP7Ntuks5sjKbZgaJpZM4PaCoy>
.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<https://github.com/goxr3plus/Java-Speech-Recognizer-
Tutorial--Calculator/issues/6#issuecomment-330045623>,
or mute the thread
<https://github.com/notifications/unsubscribe-auth/
AeeQSqsGbOfi9zQwKm793xjn4DEVJYqnks5sjSHZgaJpZM4PaCoy>
.

--

Sandya*

--

Sandya*

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/goxr3plus/Java-Speech-Recognizer-Tutorial--Calculator/issues/6#issuecomment-330053714,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATbiwPOLm3huao4GMW7SqGcsc6FUInLXks5sjS-QgaJpZM4PaCoy
.

It's called JAVA SPHINX4-5 FULL EXPLANATION OF EVERYTHING 07/09/2017
Here you go -> https://www.youtube.com/watch?v=NwnGJD6OWWQ&list=PL-xqaiRUr_iRxKrQvFMmOsvWkhxea9EpX
I recommend you to check Java Google Speech Recognition Tutorials -> https://www.youtube.com/watch?v=R8QkzTIm-Xk&list=PL-xqaiRUr_iStfTjfZAuCiCA-JVC9qJHQ

@san1197  You got any solutions ?


[stable/tensorflow-serving] add apiVersion

Adding the apiVersion for chart.yaml
to fix the issue: https://github.com/helm/charts/issues/13763
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] title of the PR contains starts with chart name e.g. [stable/chart]

/assign @mattfarina

/lgtm
/approve


[Bug] HoK menu being strange

After attacking somone the hok part of menu is being flattens
Before :

After :

OS: Windows 10
Version Latest

(sorry for bad english)

Thanks for the report. This is mainly an issue of the GUI library I used. They seem to handle vertical space in combination with a scrollable area very weirdly. There is even a bug, where the entire tool crashes, if you make it small enough.
For the next release, I have therefore increased the minimum size of the tool, to make sure there is enough space for everything to render. That should "fix" this issue for the time being.
Feel free to tell me, if the issue still happens in the next release, which should come in the next few days 😄


AMDGPU: gfx803: comd-mp4 fails execution

The comd-mp4 app (https://github.com/AMDComputeLibraries/OpenMPApps/tree/AOMP-0.5/comd-mp4) soft hangs while executed on gfx803 (gfx900 and gfx906 are fine).

Fixed by commit in clang
commit a46001d2f0c94292cd80a7d4caf81b56ee85d03f
Author: Ron Lieberman<EMAIL_ADDRESS>Date:   Mon Apr 29 11:34:41 2019 -0500
Disable META data opt, and provide evar AMDGPU_ENABLE_META_OPT_BUG to enable


Fix NLL warnings

cc rust-lang/rust#58781
Ideally this would be released as 0.2.2 (note: this PR targets master, but is based atop the 0.2.1 tag).

Thanks for the pull request!
The issue was fixed for the 0.3 series, but, indeed, there should also be a release in the 0.2 series. I have merged the PR into the release-0.2.2 branch which will result in 0.2.2.

Version 0.2.0 has been released – closing this PR.
Once again, thanks!


First pass at IFormFile support

This is a first pass at adding IFormFile support.  There's a couple of bits I might need help with:

Should the API accept streams
Support for a collection of files
Should we split the form from the file method
Wasn't too sure about the mime type and header as there are a couple of ways to do that, guidance on the correct namespace would be appreciated

I'll also probably double back on adding stream tests to ensure the file can be read.
This might also solve https://github.com/JasperFx/alba/issues/70.

@dionfoster Sorry for the delay. I wouldn't worry about dealing with StubHttpContext unless you just want that functionality. Alba as of 3.0 no longer uses that class in the Scenario() tests.
For pure form submissions, I think the extension method to take in a Dictionary, then have that written to the HttpRequest.Stream is fine. You could add an optional argument for the actual mimetype, but use a default otherwise.
I don't have an informed opinion on uploading files, sorry.

I adapted @dionfoster's code to the following HttpContext extension method:
public static class HttpContextExtensions
    {
        /// <summary>
        /// Write multi-part form data to the Request Body of the supplied HttpContext.
        /// </summary>
        /// <param name="context">The HttpContext.</param>
        /// <param name="values">Dictionary containing name-value pairs.</param>
        /// <param name="name">Name of the file to attach.</param>
        /// <param name="filePath">Path of the file to attach.</param>
        public static void WriteMultipartFormData(this HttpContext context, Dictionary<string, string> values,
            string name, string filePath)
        {
            WriteMultipartFormData(context, values, new Dictionary<string, string> { { name, filePath } });
        }

        /// <summary>
        /// Write multi-part form data to the Request Body of the supplied HttpContext.
        /// </summary>
        /// <param name="context">The HttpContext.</param>
        /// <param name="values">Dictionary containing name-value pairs.</param>
        /// <param name="files">Dictionary containing name-filepath pairs.</param>
        public static void WriteMultipartFormData(this HttpContext context, Dictionary<string, string> values,
            Dictionary<string, string> files)
        {
            var formDataBoundary = $"----------{Guid.NewGuid():N}";
            var contentType = "multipart/form-data; boundary=" + formDataBoundary;
            context.Request.ContentType = contentType;

            using var multipartContent = new MultipartFormDataContent(formDataBoundary);

            // Add values
            if (values != null)
            {
                foreach (var (key, value) in values)
                {
                    multipartContent.Add(new StringContent(value), key);
                }
            }

            // Add files
            foreach (var (name, filePath) in files)
            {
                new FileExtensionContentTypeProvider().TryGetContentType(filePath, out var fileContentType);
                var fileInfo = new FileInfo(filePath);
                using var fileStream = File.OpenRead(filePath);
                var fileContent = new ByteArrayContent(File.ReadAllBytes(filePath));
                fileContent.Headers.ContentType = new MediaTypeHeaderValue(fileContentType);
                fileContent.Headers.ContentDisposition = new ContentDispositionHeaderValue("form-data")
                {
                    FileName = fileInfo.Name,
                    Name = name
                };

                multipartContent.Add(fileContent, fileInfo.Name, name);
            }

            // Fill request body and set content length
            multipartContent.CopyToAsync(context.Request.Body).Wait();
            context.Request.ContentLength = context.Request.Body.Length;
        }
    }

I've used this successfully  in the following example:
 await Application.AlbaHost.Scenario(s =>
    {
        s.ConfigureHttpContext(context =>
        {
            context.HttpMethod("POST");
            context.RelativeUrl("/ilovefiles");
            context.WriteMultipartFormData(null, "formFile", "excellentfiles/file1.zip");
        });

        s.StatusCodeShouldBeOk();
        s.ContentShouldBe("Excellent file, thank you!");
    });

I'm going to close this, as it would make sense to apply this to the new alba internals.  If I get time I might open a new PR.

@dionfoster was this ever implemented in master branch? The file upload with existing context.WriteFormData does not work.


Wrong buffer allocation and encoding compare

The call to  var buffer=Buffer.alloc(8*10*8, "binary"); is wrong because the second argument is the fill value not the encoding. So the encoding is never set in the buffer.
In the function make_dataset_from_buffer
if (!std::strcmp("binary", (*encoding))) {
  herr_t err = H5LTmake_dataset_string(group_id, dset_name, const_cast<char*>(node::Buffer::Data(buffer)));
  if (err < 0) {
    v8::Isolate::GetCurrent()->ThrowException(
      v8::Exception::SyntaxError(String::NewFromUtf8(v8::Isolate::GetCurrent(), "failed to make char dataset")));
      return;
  }
return;
}

This makes a string dataset when the encoding is set to binary, not the other way around.

hmmm, his was changed from the deprecated new Buffer constructors but not correctly.
Wonder if the fill can be a 0:
var buffer=Buffer.alloc(8*10*8, "\0", "binary");

will change and test

var buffer=Buffer.alloc(8*10*8) worked for me.
Also if (!std::strcmp("binary", (*encoding))) { means when encoding is equals binary. But the expression should be inverted.

binary is supposed to equal "encoding"?
I'l test
Commit another bug fix and the "\0" in tests

But when encoding is binary then H5LTmake_dataset_string will be called.
Example:
When encoding is binary then
std::strcmp("binary", (*encoding) -> 0
!0 -> 1
H5LTmake_dataset_string called

https://github.com/HDF-NI/hdf5.node/issues/20
in older version the native Buffer was it's own custom thing till v8 changed something.  Then nodejs people went to using Int8Array as their Buffer.  The H5LTmake_dataset_string doesn't make an actual string but handles chars which int8 is;  this use was from way back when I used all hdf5 HL commands but then realized they were more limited and started adding in all the low level calls.
I'm wondering if this can be removed and let it just go to the remain code. I'll experiment.  Not sure if there is any user using nodejs before v4.2.x.  With any change on this I'll tag the repository so I can attempt to help such a user if they exist

Also the code should not have new and delete in it ; rather use the c++ memory management

Ah which version of nodejs are you using?
They changed the meaning of
node::Buffer::HasInstance

again!
This is why std::strcmp("binary", (*encoding) is acting strange for you and now me.  Only supposed to be in make_dataset_from_buffer if it's an wrapper of Int8Array
Going to have to reorder things and find how old a version of nodejs we can support on new release

I'm using v8.11.2.

I have more unit tests back to working with nodejs v9.9.0.  I'll be testing back thru versions including yours.  Some of the unit tests I have running with
{rank: 2, rows: numberOfDataLines, columns: 3} option style. We'll see what the day brings

Ok, great.

tests:
66 passing (434ms)
8 pending
The pending ones are ones skipped because they depend on h5's people gave me locally to tests.  I want to replace with ones the tests create on the fly; don't want to clutter repository or use something someone never gave permission for such use.
testing with different versions of nodejs...

After a release and tagging with the deprecation, the reserved properties will go away for v4.x.x


Prompt file doesn't support multi-shot, multi-line prompts

I would like to give a multi-shot prompt with multiple user/assistant messages.
For that, as the examples state, I use a JSON list of objects.
However, in this format, if I have newlines inside a prompt, the JSON isn't properly decoded (as officially, newlines should be encoded as \n in JSONs).
This makes it extremely uncomfortable to use, as copying prompts in/out of promptfoo requires a lot of manual work of transforming newlines to \n s.
I think there should be a way to write multi-line, multi-shot prompts in some non-JSON way.

Sure! I would like something like this:
[{"role": "system", "content": "This is a multiline prompt.
It has multiple lines in it.
Today, it doesn't work."},
{"role": "user", "content": "Another prompt,
which has several lines in it."}]```

Ah I see.  As you pointed out in your original post, that is not valid JSON.  I imagine most users won't want a tool that coerces malformed JSON to correct JSON, because then it won't work properly in their production application.
One potential solution is to add YAML support.  YAML has built-in support for multiline strings, and it maps directly to JSON.  For example:
- role: system
  content: |
    This is a multiline prompt.
    It has multiple lines in it.
    Today, it doesn't work.
- role: user
  content: |
    Another prompt,
    which has several lines in it.

What do you think?

That would make a lot of sense.

This will be in the next release.  Example usage here: https://github.com/promptfoo/promptfoo/tree/main/examples/openai-multiline-yaml

Thanks for the prompt fix (pun intended)!


Add Aaron Griswold @grizzwolf as a new ODP project team member

Add the following FINOS team member to the ODP project in GitHub.

[x] https://github.com/grizzwolf - @grizzwolf

@grizzwolf - Welcome to the ODP team. I have allocated you stories #55 and #56 😄


Make installing PDBs optional.

PDBs are not necessarily generated, even in Debug configuration. For example, if the CXX_FLAGS are set to /Z7, debug symbols are embedded, and so the PDBs are not generated. This prevents installing from failing by marking these PDBs as optional.
Fix #610

Much appreciated, thanks!


implement rules and recommendations of SITRE on Windows process API related tasks

https://wiki.sei.cmu.edu/confluence/pages/viewpage.action?pageId=87151933
Recommendations

[x] WIN00-C. Be specific when dynamically loading libraries LoadLibraryEx (without PATH and include paths)
[x] WIN01-C. Do not forcibly terminate execution
[x] WIN02-C. Restrict privileges when spawning child processes

[x] unfeasible in libstd => heavily platform based
CreateProcessAsUserW (Unix equivalent), CreateProcessWithTokenW (no unix equivalent) + API to drop permissions
setuid + capsdrop
[x] win32k mitigation (nonsensical ERROR_OUTOFMEMORY on 2nd faiure of LoadLibrary)
seccomp filter

[x] WIN03-C. Understand HANDLE inheritance

can be disabled in CreateProcess (not generally useful for libstd)
[x] can be disabled on each handle (implemented here; sounds like a good addition to libst)
can be attached to security handle at HANDLE creation for CreateProcess (not generally useful for libstd)
[x] can be explicitly set in list (requires to be enabled on each HANDLE and erach HANDLE in list must be valid and non-null) for CreateProcess

[x] is automatically inherited if enabled in CreateProcess and at HANDLE (without security handle and list approach)

[x] WIN04-C. Consider encrypting function pointers

[x] encrypting longterm global pointers without shadow stack sounds useless
[x] not generealizable and only increases amount of followup bytes attacker must control

Rule

[x] WIN30-C. Properly pair allocation and deallocation functions

Tasks for libstd done, upstreaming is pending a fix to #1.

Use upstreaming issue #8 instead to reduce noise.


Unreasonable error reported in Nuxt3 At least one <template> or


feat: add first day of week user setting

Homarr

Thank you for your contribution. Please ensure that your pull request meets the following pull request:

[x] Builds without warnings or errors (pnpm buid, autofix with pnpm format:fix)
[x] Pull request targets dev branch
[x] Commits follow the conventional commits guideline
[x] No shorthand variable names are used (eg. x, y, i or any abbrevation)

Check with #1248 which one we take :joy: