:disabled state for buttons

Currently the buttons don't appear disabled when you add a disabled attribute to them. They appear and interact with the mouse as though they are clickable.

@blackmann aside cursor not allowed, which other styles are we looking at?

The button should appear lighter

Alright, should changes be made in the css.ts file or app/src/components/Button.module.css

css.ts <- That's where the style generation is done from

PR opened, please review


How to fix hardcoded values for NTLM/Kerberos SecPkgContext_Sizes structure ?

In the function :
SECURITY_STATUS SEC_ENTRY ntlm_QueryContextAttributesW(PCtxtHandle phContext, ULONG ulAttribute, void* pBuffer)
we have the following :
`
	SecPkgContext_Sizes* ContextSizes = (SecPkgContext_Sizes*) pBuffer;
	ContextSizes->cbMaxToken = 2010;
	ContextSizes->cbMaxSignature = 16;
	ContextSizes->cbBlockSize = 0;
	ContextSizes->cbSecurityTrailer = 16;

`
Where do the values 2010, 16, 0 and 16 come from ?
Let's take for example cbMaxSignature. The link (https://msdn.microsoft.com/en-us/library/windows/desktop/aa380097) says that cbMaxSignature "specifies the maximum size of the signature created by the MakeSignature function." But in FreeRDP this function is not supported :
SECURITY_STATUS SEC_ENTRY ntlm_MakeSignature(PCtxtHandle phContext, ULONG fQOP, PSecBufferDesc pMessage, ULONG MessageSeqNo) {         return SEC_E_UNSUPPORTED_FUNCTION; }
Then, why do we set cbMaxSignature to 16 ?
Is there a way not to assign hard-coded values but make automatic assignment instead ?
Besides, given the work of tc-anssi (https://github.com/tc-anssi/FreeRDP/tree/kerberos), I want to implement the same QueryContextAttributes function but for Kerberos.
The problem is, I don't know or it's not clear to me, apart from cbMaxToken, which values I have to assign to cbMaxSignature, cbSecurityTrailer and cbBlockSize.
I set cbMaxToken to 48,000 since for Windows Server 2012 the default value of the MaxTokenSize registry entry is 48,000 bytes.
If someone could help me to understand what these parameters are supposed to store.
Finally for both, NTLM and Kerberos, I'm listening if someone is considering some solution or maybe has already come up with a solution to this problem of hardcoded values.

@dodo040 you're right there's good things that we should take from https://github.com/tc-anssi/FreeRDP/tree/kerberos . If you want to submit such improvements as a PR we'll be glad to review it.

@hardening yes sure I'll submit a PR very soon. Before I've a few things to improve or update including this issue.

Kerberos support has been merged, assume this is fixed? Reopen if not.


Choose license, attach it to the repository, add license text into all sources

I think we have to choose WTFPL as reflections did.

I think LICENSE file is enough for this task.


C-API support for .keras models

Issue type
Feature Request
Have you reproduced the bug with TensorFlow Nightly?
Yes
Source
binary
TensorFlow version
2.16
Custom code
No
OS platform and distribution
No response
Mobile device
No response
Python version
No response
Bazel version
No response
GCC/compiler version
No response
CUDA/cuDNN version
No response
GPU model and memory
No response
Current behavior?
TF_LoadSessionFromSavedModel() not able to load .keras files.
Is C-API support for Keras v3 .keras format planned?
Standalone code to reproduce the issue
TF_LoadSessionFromSavedModel(..., "model.keras", ...)

Relevant log output
No response

Sorry, Tensorflow version is 2.11

Hi @Sklaebe ,

In order to expedite the trouble-shooting process, please provide a code snippet to reproduce the issue reported here. And could you please elaborate your issue?
Thank you!

Hi @Venkat6871,
I can't provide a code snippet because there is no function yet and this ticket asks about the plans for an addition.
The C-API contains a function TF_LoadSessionFromSavedModel, which allows loading the saved model format. Keras v3 introduced the new .keras format, for which there is no loading function yet.

Hi @Sklaebe ,

Without code snippet we can't able to trouble- shooting process, please provide a code snippet to reproduce the issue reported here. It helps to debug the issue in an effective way.

Thank you!

This is also an issue for the Rust API, since that depends on the C API.  This is especially a problem now that saving a Keras model from Python can only save in the Keras format and not the SavedModel format (i.e. save_format="tf" support has been removed).

@Venkat6871 this is a feature request, not a bug. So there's no code snippet to reproduce an issue that doesn't exist! Basically, @adamcrume asks for the following to work in C/C++:
TF_LoadSessionFromSavedModel(..., "model.keras", ...);

Adam, I think that unfortunately this won't be possible. The Keras format is at a much higher level than TF. While there's nothing technical that would make support impossible to add, maintaining the C/C++ codebase while the Python version changes will be something of a pain. Plus, Keras aims to be platform agnostic, so model.keras could be actually a PyTorch model!
The fact that saving a model only saves in Keras format is a bug though.


Why this.$CurrencyFilter is removed?

I updated from 5.0.1 => 5.1.0, now this.$CurrencyFilter is undefined. Is there any other way to access it??

After some investigation found by console logging that $CurrencyFilter is replaced with $currency, but it was never mentioned in docs.


Convert memory read to async, fix compatibility with some RF clients

This PR:

Converts the previous memory read approach to async (with a lot of help on proper syntax and C# best practice from ChatGPT)
Shifts to a window title check instead of checking the memory size of loaded modules to identify valid RF processes. This approach is futureproof in that it allows use of any Dash versions going forward without further updates to the component being necessary
Reformats some code to help with readability and adds some additional comments to help anyone interpret the code

Withdrawing PR to revamp, consolidate, and resubmit


slight black and new modes

Here you go @louh. These are for the mode, next to the distance/time
Still working on the transit maneuver icons

huzzah!


Dart analysis server / FATAL error: Failed to handle request

Version information

IDEA AI-191.8<IP_ADDRESS>77832
2.6.0-edge.70a7ef3f589ec525c2a3b14fa7d47f44d09a29f3
AI-191.8<IP_ADDRESS>77832, JRE 1.8.0_202-release-1483-b03x64 JetBrains s.r.o, OS Windows 10(amd64) v10.0 , screens 1920x1080

Exception
Dart analysis server, SDK version 2.6.0-edge.70a7ef3f589ec525c2a3b14fa7d47f44d09a29f3, server version 1.27.3, FATAL error: Failed to handle request: {id: 4, method: analysis.setAnalysisRoots, params: {included: [C:\Users\user1\Development\Android\Projects\pda], excluded: [C:\Users\user1\Development\Android\Projects\pda\.idea, C:\Users\user1\Development\Android\Projects\pda\.dart_tool, C:\Users\user1\Development\Android\Projects\pda\.pub, C:\Users\user1\Development\Android\Projects\pda\build]}, clientRequestTime:<PHONE_NUMBER>530}
FileSystemException: Directory watcher closed unexpectedly, path = 'C:\Users\user1\Development\Android\Projects\pda'
#0      _FileSystemWatcher._listenOnSocket.<anonymous closure> (dart:io-patch/file_patch.dart:307:11)
#1      _ExpandStream._handleData (dart:async/stream_pipe.dart:248:23)
#2      _ForwardingStreamSubscription._handleData (dart:async/stream_pipe.dart:164:13)
#3      _rootRunUnary (dart:async/zone.dart:1136:13)
#4      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#5      _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
#6      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
#7      _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
#8      _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:764:19)
#9      _StreamController._add (dart:async/stream_controller.dart:640:7)
#10     _StreamController.add (dart:async/stream_controller.dart:586:5)
#11     new _RawSocket.<anonymous closure> (dart:io-patch/socket_patch.dart:1384:35)
#12     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:890:18)
#13     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#14     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#15     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#16     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

For additional log information,
Dart analysis server, SDK version 2.6.0-edge.70a7ef3f589ec525c2a3b14fa7d47f44d09a29f3, server version 1.27.3, FATAL error: Failed to handle request: {id: 4, method: analysis.setAnalysisRoots, params: {included: [C:\Users\user1\Development\Android\Projects\pda], excluded: [C:\Users\user1\Development\Android\Projects\pda.idea, C:\Users\user1\Development\Android\Projects\pda.dart_tool, C:\Users\user1\Development\Android\Projects\pda.pub, C:\Users\user1\Development\Android\Projects\pda\build]}, clientRequestTime:<PHONE_NUMBER>530}
FileSystemException: Directory watcher closed unexpectedly, path = 'C:\Users\user1\Development\Android\Projects\pda'
#0      _FileSystemWatcher._listenOnSocket. (dart:io-patch/file_patch.dart:307:11)
#1      _ExpandStream._handleData (dart:async/stream_pipe.dart:248:23)
#2      _ForwardingStreamSubscription._handleData (dart:async/stream_pipe.dart:164:13)
#3      _rootRunUnary (dart:async/zone.dart:1136:13)
#4      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#5      _CustomZone.runUnaryGuarded (dart:async/zone.dart:931:7)
#6      _BufferingStreamSubscription._sendData (dart:async/stream_impl.dart:336:11)
#7      _BufferingStreamSubscription._add (dart:async/stream_impl.dart:263:7)
#8      _SyncStreamControllerDispatch._sendData (dart:async/stream_controller.dart:764:19)
#9      _StreamController._add (dart:async/stream_controller.dart:640:7)
#10     _StreamController.add (dart:async/stream_controller.dart:586:5)
#11     new _RawSocket. (dart:io-patch/socket_patch.dart:1384:35)
#12     _NativeSocket.issueReadEvent.issue (dart:io-patch/socket_patch.dart:890:18)
#13     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#14     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#15     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#16     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)
1573330499718 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[],"removedLibraries":[57]}}
1573330500546 => {"id":"18","method":"analysis.updateContent","params":{"files":{"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\pubspec.yaml":{"type":"add","content":"name: pda\nde
1573330500552 <= {"id":"18","result":{}}
1573330500939 => {"id":"19","method":"analysis.updateContent","params":{"files":{"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\pubspec.yaml":{"type":"remove"}}},"clientRequestTime
1573330500950 <= {"id":"19","result":{}}
1573330543024 => {"id":"20","method":"analysis.updateContent","params":{"files":{"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\pubspec.yaml":{"type":"add","content":"name: pda\nde
1573330543024 <= {"id":"20","result":{}}
1573330545433 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\pubspec.yaml","errors":[]}}
1573330545798 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\pubspec.yaml","errors":[]}}
1573330581836 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":150,"uri":"package:pda/models/_mat_images.dart","items":[{"label":"MaterialImages","declaringLibraryUri"
1573330581858 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\lib\\models\\_mat_images.dart","errors":[]}}
1573330583563 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":116,"uri":"package:pda/screens/home.dart","items":[{"label":"HomeScreen","declaringLibraryUri":"package:
1573330583710 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\lib\\screens\\home.dart","errors":[{"severity":"INFO","type":"HINT","loc
1573330583719 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":13,"uri":"package:pda/screens/listCart.dart","items":[{"label":"ShoppingCartScreen","declaringLibraryUri
1573330583928 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\lib\\screens\\listCart.dart","errors":[{"severity":"INFO","type":"LINT",
1573330583931 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":15,"uri":"package:pda/screens/listCategories.dart","items":[{"label":"CategoriesScreen","declaringLibrar
1573330584207 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\lib\\screens\\listCategories.dart","errors":[{"severity":"INFO","type":"
1573330584214 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":3,"uri":"package:pda/screens/listItems.dart","items":[{"label":"AllProducts","declaringLibraryUri":"pack
1573330584428 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\lib\\screens\\listItems.dart","errors":[{"severity":"INFO","type":"HINT"
1573330584535 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":12,"uri":"package:pda/screens/viewInvoice.dart","items":[{"label":"ViewInvoice","declaringLibraryUri":"p
1573330584541 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":67,"uri":"package:pda/utils/drawer_homescreen.dart","items":[{"label":"HomeDrawer","declaringLibraryUri"
1573330584555 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":151,"uri":"package:pda/SqliteDB/PalmProvider.dart","items":[{"label":"DatabaseHelper","declaringLibraryU
1573330584766 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\lib\\screens\\viewInvoice.dart","errors":[{"severity":"INFO","type":"LIN
1573330584857 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\lib\\SqliteDB\\PalmProvider.dart","errors":[{"severity":"INFO","type":"L
1573330584914 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\lib\\utils\\drawer_homescreen.dart","errors":[{"severity":"INFO","type":
1573330586328 => {"id":"21","method":"analysis.updateContent","params":{"files":{"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\lib\\utils\\drawer_homescreen.dart":{"type":"add","c
1573330586481 <= {"id":"21","result":{}}
1573330586587 <= {"event":"completion.availableSuggestions","params":{"changedLibraries":[{"id":67,"uri":"package:pda/utils/drawer_homescreen.dart","items":[{"label":"HomeDrawer","declaringLibraryUri"
1573330586773 <= {"event":"analysis.errors","params":{"file":"C:\\Users\\user1\\Development\\Android\\Projects\\pda\\lib\\utils\\drawer_homescreen.dart","errors":[{"severity":"INFO","type":
1573330586914 <= {"event":"server.error","params":{"isFatal":true,"message":"Failed to handle request: {id: 4, method: analysis.setAnalysisRoots, params: {included: [C:\\Users\\user1\\Devel

Thanks for reporting the issue. This was previously reported in #38853, please follow along there.

Duplicate of #38853


Adding initial schema for lenkwerk db

This PR is here for a discussion of the initial schema and support structures for the tooling in Perl.
This includes some basic modules for handling Lenkwerk db connection parameters

I am aware that the the test files being .pms break conventions.  This will be fixed in a PR adding the build system.

After discussion will squash merge this.  This is the first code added, which makes review a problem, and it is something where problems will be found and fixed as we go forward.  So this is a one-time initial commit.


support new glslify sync interface

I am working on some upstream changes to glslify to support a synchronous interface. This patch adds support for the new .sync API so we can support both the asynchronous and synchronous code paths in a backwards-compatible way.
https://github.com/substack/glslify-deps/tree/f9806e70c32ffe9257a8a058fed849e7d32cbed3#transform-api
https://github.com/stackgl/glslify-deps/pull/6
https://github.com/stackgl/glslify/issues/80

Nice! Thanks again @substack — will move this over to the stackgl org :)


General Guidance

I have the understanding that to perform 2D localization, the workflow is to first scan the environment while slam toolbox is running and at one point it has to be saved as a map file which can then be loaded later to perform localization.
I am now trying to first generate the map but using 3D lidar from Gazebo velodyne simulator, but I understand that for generating the map I would also need IMU so where would that come from in the Gazebo simulation?
I have built a 3d model of a parking lot as a obj file which I plan to scan through gazebo, and once it is done then save it as a map file and later load it again to perform the localization.
Hence I am looking for some guidance on what would be the workflow and required packages.
what if I already have a pointcloud file e57 (leica blk360) which can also be converted to a laz file and viewed in cloudconvert. Then how can i use it to perform localization only?

for generating the map I would also need IMU

IMUs are not essential for map generation.

where would that come from in the Gazebo simulation?

I don't use Gazebo much, so I don't really remember where the IMU would come from in Gazebo simulations.

Then how can i use it to perform localization only?

If you're using ROS, most ROS localization packages typically utilize the PCL library. You might be able to use your e57 file by converting it into the PCD format, which is the standard point cloud format used by PCL.

Due to inactivity, I'm closing this issue. If there are still concerns, please open a new issue. Thank you.


Add files via upload

Hi, Lukas,
This is a submission of passive Si design. Here, multiple spirals and spiral_paperclips are designd to see how the minimum radius will affect the loss.
Additional GCs are also designed for alignment when testing.
Thanks,
Yiran Guan

can you please fix the errors?


CMake: Replace deprecated FindCUDA with FindCUDAToolkit

Bug summary
CMake has deprecated FindCUDA module in favor of FindCUDAToolkit, with CMake 3.27 adding a noisy warning whenever find_package(CUDA) is used.
To Reproduce
Try building hipSYCL with CUDA backend using CMake 3.27, observe the warning in the terminal:
CMake Warning (dev) at CMakeLists.txt:42 (find_package):
  Policy CMP0146 is not set: The FindCUDA module is removed.  Run "cmake
  --help-policy CMP0146" for policy details.  Use the cmake_policy command to
  set the policy and suppress this warning.

This warning is for project developers.  Use -Wno-dev to suppress it.

Expected behavior
No CMake warnings
Describe your setup

hipSYCL develop
Describe the dependencies that hipSYCL sits on top of in your setup:

Clang 16
CUDA 12.2
ROCm 5.3.3 (unrelated, although it does add its own CMake warning)

Additional context

Despite the message saying "The FindCUDA module is removed" it is not really removed (yet). It works fine except for the warning, and even that can be silenced by setting the corresponding CMake policy. But relying on deprecated functionality does not look right for the project driving the future of heterogeneous/accelerated compute :)

Thank you, @nilsfriess


[profile] page refresh required to update content in menu dropdown

When the profile is updated (attestations or name), a page refresh is required to update the content in the menu dropdown

I am working on this issue.

Hi @ambertch,
The page should be refresh on Publish the profile or when user click on Continue button inside the popup?

@dhruvkumar001 a refresh should not be required at all. The user dropdown should reactively update to show the new attestations or profile attributes.

Okay will make it the way.

Resolved by https://github.com/OriginProtocol/origin-dapp/pull/561 ✅


Applying WaveDiff to Experimental Data with Custom Parameters

Hello,
Thank you for sharing your WaveDiff tool! The performance reported in your papers is very impressive!
I would like to use it for one of my projects on the Keck telescopes, both for PSF reconstruction and phase retrieval. I would have a few questions, please:

Is wf-diff at a stage where it is ready to be applied to any experimental data? I’m happy to test and adapt the code as needed, fine-tuning the hyperparameters to ensure it works effectively with my specific data.

Sorry if I missed it, but do you have a notebook or tutorial that, in addition to the "configuration" section of your documentation, provides a step-by-step example of applying wf-diff to real data?

Unless I'm mistaken, I couldn't find in the config section where I can modify and adapt certain key parameters specific to my system, such as pupil shape/obscuration, focal length/aperture diameter/pixel size (which I think are also used internally to determine the set of wavelengths "allowed" and satisfy the conditions of your zero-padding/resampling strategy, etc.) I believe these parameters are given in the SimPSFToolkit class and are currently set to represent the Euclid optical system.

Is it possible in any version of wf-psf to utilize information obtained via phase diversity (from out-of-focus PSFs)?

Is your new strategy for improved phase retrieval presented in one of your posters (link](https://drive.google.com/file/d/1WJ7qFlLHuAHlyDDU4vFAc-6MYIzsDMGA/view?usp=share_link)) available in any of the published versions of wf-psf?

Thank you for your time and consideration!

Hi @CAClaveau
Thanks for your interest in the method. I have provided some fast answers to your questions in the text below. However, if you're interested in going more into the details of the model and how to use/adapt it, we could program a Zoom call (send me an email to tobias.liaudat@cea.fr). I could assist you in adapting the code for your needs.

We are currently working with real Euclid data, so the answer is yes. However, we are still analysing the data and adding more features to the model to improve its performance. We have not tested the model with ground-based observations, so I'm very interested to see how it performs!

Unfortunately, we do not have one notebook like that. Nevertheless, if there's interest, we could build one!

We have not exposed those parameters to the config files as we were focusing on Euclid (so these parameters were fixed). In any case, there is nothing stopping us from exposing them and adapting them for another telescope.

Yes, this is one of the updates that are not yet published. The idea is to use wavefront information (obtained from simulations or via a phase diversity study) as a prior in the model and take it into account while optimising the model. This information should follow the wavediff format. The model that handles a wavefront prior is the poly_physical  model.

Yes, the strategy for phase retrieval is implemented. A paper describing that method in detail is being prepared. However, those updates have not yet been merged into the main, but are available at the branch case_study_psf_decontamination.

Note that several new features of the model are not described in a paper as we are focused on processing Euclid data, which was the motivation for the development of the WaveDiff model.

Hi @tobias-liaudat,
Thank you for your detailed and prompt response, as well as for offering your help with using the wf-diff tool!
A comprehensive notebook or a fully worked-out script example would indeed be very helpful for getting started with wf-diff.
I plan to begin this project with classical phase diversity in early 2025. In the meantime, I’ll focus on familiarizing myself with the tool and its cfg params. Learning how to incorporate wavefront priors from phase diversity data into the poly_physical model format will be particularly valuable. I’ll also take a look at the case_study_psf_decontamination branch you mentioned.
It’s exciting to hear that you’re applying the model to real Euclid data and actively adding new features to improve it. I look forward to reading the upcoming papers and learning more about these developments!
I’ll reach out closer to the project start if I need assistance adapting the code to my data.
Thank you again for your time and support.


Fast route changes causes component render outside #root

Having an issue, using latest Vite and TSParticles. When I change routes too fast TSParticles renders outside the root. I am using particles inside a component to place it in specific divs, already using the fullscreen option and works fine until fast route changes.
I have tried creating a destroy method but it doesn't seem to be working. Here is a lightweight reproduction. Try change routes fast and you will notice it extends the height of the document.
https://codesandbox.io/p/sandbox/vigorous-austin-f34z57

Closing this since it's a duplicate of the Discord thread


Paging details in listing responses

Resolves Issue #21

I made a minor amendment to what the ticket (#21) said we should do, in that we specified that the parameters would be passed as an array of objects, but when implementing it seemed less verbose to make the parameters object essentially a string -> string map, so it's declared as a object with arbitrary keys and string values.
I've also used "patternProperties", which seems fine in JSON schema, but I've been struggling to get the OpenAPI spec to validate (quite a few tools seem to not like 3.1.0) or to generate the HTML, so I'm not 100% sure that that is as well supported in the API spec.


corerad: 1.2.1 -> 1.2.2

Description of changes
https://github.com/mdlayher/corerad/blob/main/CHANGELOG.md#v122

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[x] 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
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 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

[x] Fits CONTRIBUTING.md.

Thanks for the speedy release and review! 🙂

@GrahamcOfBorg test corerad


support weight parameter for range and geospatial queries in QueryBuilder

Internal bug 55121

Trivial change.  I expect the unit tests may be sufficient coverage.


streamingAssetsUrl Missing in v7

The docs say setting the streamingAssetsUrl is supported since version 6, but I am using version 7 for Unity 2019, and I don't see any way to set streamingAssetsUrl
Defining the Streaming Assets URL https://github.com/elraccoone/react-unity-webgl#defining-the-streaming-assets-url
IUnityConfig doesn't seem to have a streamingAssetsUrl in version 7
export default interface IUnityConfig {
    /**
     * The unique identifier helps you getting the instance
     * of your context from any other class.
     * @type {string}
     */
    id?: string;
    /**
     * Unity Module injection.
     * @type {Object}
     */
    modules?: Object;
    /**
     * You can default your Unity Version. The library may
     * contain future patches for specific Unity versions.
     * It's not needed but is recommended to define a version.
     * @type {UnityVersion}
     */
    unityVersion?: UnityVersion;
    /**
     * Since the Unity canvas itself does not respond to the resizing
     * of it's container we have to manually do this. A width and height
     * of 100% does not seem to work, so we have to fetch it's parent's
     * size to adject the canvas.
     * @type {boolean}
     */
    adjustOnWindowResize?: boolean;
}

Hey @jeffreylanters, We're hitting a similar issue. Looks like it was added in at commit 88621627f21c382da43986a4a933311724a02d53 Do you know you plan to back port it to 7.X?

Hey @jeffreylanters, Yeah. We are making use of addressable to improve performance which is held within streaming assets. Which is currently not possible with 7.x

I've been looking into this, if I remember this correctly the streamingAssetsUrl is provided via the modules parameter, which directly interfaces with Unity's WebGL build Module extension. Could you try to implement this? I think this should work already. Let me know!
let unityContent = new UnityContent(
  "MyGame/Build.json",
  "MyGame/UnityLoader.js", {
    modules: {
      streamingAssetsUrl: "..."
    }
  }
);

I've been looking into this, if I remember this correctly the streamingAssetsUrl is provided via the modules parameter, which directly interfaces with Unity's WebGL build Module extension. Could you try to implement this? I think this should work already. Let me know!
let unityContent = new UnityContent(
  "MyGame/Build.json",
  "MyGame/UnityLoader.js", {
    modules: {
      streamingAssetsUrl: "..."
    }
  }
);

With above code I'm getting the following errors on latest 7.x
exception thrown: TypeError: Module.streamingAssetsUrl is not a function,TypeError: Module.streamingAssetsUrl is not a function

About to publish version 7.1.11 which includes support for Streaming Asset URL's. See LTS-7.X/Feature/Streaming-Assets-URL-Support.

I've released 7.1.11.

i've released version 7.1.12 adding support for Streaming Asset URLs and including updated documentation. If you have any more questions feel free to re-open this issue.
Thanks for opening an issue and best of luck with your project!

That worked first time! Thanks for your help


not compatible with virtual workspaces

The history is not saving any files to a workspace on a virtual workspace.
Refering to : https://code.visualstudio.com/api/extension-guides/virtual-workspaces
Tested it with:
Like with the plugin: liveecommerce.vscode-remote-workspace
With a ftp connection.

I also have this issue with with the SSH FS extension:
Name: SSH FS
Id: Kelvin.vscode-sshfs
Description: File system, terminal and task provider using SSH
Version: 1.24.1
Publisher: Kelvin Schoofs
VS Marketplace Link: https://marketplace.visualstudio.com/items?itemName=Kelvin.vscode-sshfs

When I try to save a remote file using the extension, I get the following error:
Error with copyFile: 'Error: ENOENT: no such file or directory, open '\home\[filename].sh' \home\[filename].sh => C:\[userpath]\home\[filename]_20220507231836.sh


TypeError: l2_normalize() got an unexpected keyword argument 'axis'

from ._conv import register_converters as _register_converters
Using TensorFlow backend.
/home/pcadmin/aakash/ssd_keras-master/data_generator/object_detection_2d_data_generator.py:43: UserWarning: 'BeautifulSoup' module is missing. The XML-parser will be unavailable.
warnings.warn("'BeautifulSoup' module is missing. The XML-parser will be unavailable.")
Traceback (most recent call last):
File "ssd300_training.py", line 63, in
swap_channels=swap_channels)
File "/home/pcadmin/aakash/ssd_keras-master/models/keras_ssd300.py", line 316, in ssd_300
conv4_3_norm = L2Normalization(gamma_init=20, name='conv4_3_norm')(conv4_3)
File "/usr/local/lib/python2.7/dist-packages/keras/engine/topology.py", line 619, in call
output = self.call(inputs, **kwargs)
File "/home/pcadmin/aakash/ssd_keras-master/keras_layers/keras_layer_L2Normalization.py", line 62, in call
output = K.l2_normalize(x, self.axis)
File "/usr/local/lib/python2.7/dist-packages/keras/backend/tensorflow_backend.py", line 3151, in l2_normalize
return tf.nn.l2_normalize(x, axis=axis)
TypeError: l2_normalize() got an unexpected keyword argument 'axis'
versions:
python: 2.7.4
tensorflow : 1.4.0
keras: 2.1.5

You didn't search the closed issues, this exact issue has been solved before.


HDDS-4440- s3 performance

What changes were proposed in this pull request?
Initial commit for s3g gRPC for command OmRequest and OmResponses.  Creates:

a gRPC service for existing Om protocol - protoc 2.5 hadoop-ozone/interface-client/pom.xml, hadoop-ozone/interface-client/target/generated-sources/protobuf/java/org/apache/hadoop/ozone/protocol/proto/OzoneManagerServiceGrpc.java - HDDS-5210
starts OM gRPC server as part of OM bootstrap - hadoop-ozone/ozone-manager/src/main/java/org/apache/hadoop/ozone/om/GrpcOzoneManagerServer.java, OzoneManager.java - HDDS-5211
creates implementation of OmTransport for gRPC -  hadoop-ozone/interface-client/pom.xml - HDDS-5212
Create specific OmTransportFactory for GrpcOmTransport - hadoop-ozone/common/src/main/java/org/apache/hadoop/ozone/om/protocolPB/GrpcOmTransportFactory.java; dynamically selected ServiceProvider loaded class for s3g hadoop-ozone/s3gateway/src/main/resources/META-INF/services/org.apache.hadoop.ozone.om.protocolPB.OmTransportFactory - HDDS-5213

Currently requires ratis disabled for Om : set ozone.om.ratis.enable=false in ozone-site.xml;(fixed/resolved)  use intellij hadoop-ozone/dev-support/intellij/ozone-site.xml and intellij s3g together with invoke s3g for simple bucket commands through s3 cli.
In addition, for s3g gRPC OmRequest/OmResponse a single OmTransport connection is used between s3g and the ozone manager.  A cached OzoneClient is implemented to service every s3g request.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5210 - (see 1. previous section)
https://issues.apache.org/jira/browse/HDDS-5211 - (see 2. previous section)
https://issues.apache.org/jira/browse/HDDS-5212 - (see 3. previous section)
https://issues.apache.org/jira/browse/HDDS-5213 - (see 4. previous section)
How was this patch tested?
Patch is initial POC for s3g gRPC OmRequest/OmResponse.  Currently requires ratis disabled for Om - (when invoking ratis server through OzoneManagerRatisServer submitRequest, createWriteRaftClientRequest(omRequest) fails when checking preconditions due to hadoop class Server.Call is null; requires attention from propagating the om SubmitRequest through the GrpcServer).  (fixed/resolved)
To test - use  intellij ozone development cluster running through runConfigurations for invoking SCM, OM, Recon, Datanodes and S3Gateway.  Commit includes modified ozone-site.xml (hadoop-ozone/dev-support/intellij/ozone-site.xml) to disable ratis for om (<property><name>ozone.om.ratis.enable</name><value>false</value></property>). (fixed/resolved)  Run simple s3 file operations through aws cli:

For s3g gRPC comparison to existing s3g hadoop RPC performance measurements, a freon test is implemented,S3BucketGenerator.java, and used.
Run through intellij, deployment platform a cluster consisting of SCM, OM, Recon,Datanodes, S3Gateway:
$ ozone freon s3bg -t 2 -n 5

Thanks the patch @neils-dev. Looks it has a lot of unrelated change. Is it possible that master is merged to your branch but not to the target branch?

@neils-dev Given that

HDDS-4440 is split into sub-tasks
we had a separate PR for the first sub-task
which had improvement over this one (as CSI test is failing here and was OK there)
the separate PR just got merged
we had a merge conflict even before that

I think we should close this mega PR and open a new one for the second sub-task.


container with privateNetwork fails to start if name is too long

Issue description

make a declarative container, with a long name ("postgres-central" is long enough)
set privateNetwork = true
systemd shortens the ve-interface name and the scripts then fail to find it.

There should probably be an assertion for long container names.

Running into the same issue here. With container name consul-master-1.  Renaming to c1 fixed it.

stepped into that bug too, did cost me a afternoon to understand that I do nothing wrong but that this is a bug over different versions of nixos 17.09 and 18.03.
The config looked very basic so I could not believe that this basic functionality (have a container with private network enabled) could be broken.

I have filed an issue upstream https://github.com/systemd/systemd/issues/10721

IIRC, there's a maximum length of interface names in the kernel, and nixos' generation code tries to create interfaces with names longer than that.
systemd-nspawn generates network interfaces names limited to a maximum of 16 characters (including the null byte), they limit interface size to IFNAMSIZ.
We have a similar assertion in nixos/modules/tasks/network-interfaces.nix - But not in the bash of nixos/modules/virtualisation/containers.nix setting up the containers…
A fix would be to also strip interface names generated to 15 characters, and maybe in the longer run move to generating containers using nspawn ;-)

Just failing when we observe a name that is too long sound reasonable in this case.
If you decide to do some string magic to make them shorter / unique you are asking for more trouble down the road.. (Users will refer to the non-transformed string somewhere and it will fail anyway, …)

nd maybe in the longer run move to generating containers using nspawn ;-)

We already do this, and it's actually systemd-nspawn who is failing to assert this as well. Hence I filed an issue upstream

Ah, I misread the main issue description - sorry.
I'm still not very convinced we should simply fail on privateNetwork = true, because some (mostly internal) network interface names would be too long.
Can't we just adapt the documentation, documenting how interface names of containers with longer names will be shortened, and shorten it like systemd would?
This will only change interface names of containers which are currently broken anyhow, and would stop people from bumping into this.

As for the duplicates problem: How does nspawn handle this, if we let it generate interface names?
Nspawn crashes, see the upstream issue i filed

(triage) @arianvp

What I'm going to do is now change the NixOS module to limit names to 11 characters

Like @andir, I think this is the right way to go. Upstream appears unwilling to change anything here, and we can actually prevent the user from even switching to a failing configuration by adding such an assertion, so the drawbacks are minimal.

Thanks for the bump. Let's implement that then. I'll do that today

Is https://github.com/systemd/systemd/pull/14467 somehow relevant for lifting the 11-character limitation? Feel free to close if it's not possible to incorporate.

I think it is. We can lift the limit now probably.

I've prepared a PR - https://github.com/NixOS/nixpkgs/pull/100433 - that lifts this limit on kernels supporting altnames (which is 5.8+, from what I've managed to test).
Just for context: we need support for altnames, because all our container-setup & -cleanup scripts depend precisely on ve-$containerName to be available (which is not the case for containers with longer names, since the device's name might get mangled by systemd-nspawn).

@Patryk27 @flokli https://github.com/NixOS/nixpkgs/commit/336ef2de99197dd9c07b302685dc9e6282fa5b55#diff-9f35243fa1e67cb77387bca245d3bc5011b08ed64326772fb9190a35df438cabR275 breaks building containers in containers (with extra-container at least) because the kernelPackages attribute doesn't exist:
$extra-container create container.nix --start --build-args --show-trace
Building containers...
error: while evaluating the attribute 'sources' of the derivation 'etc' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixos/modules/system/etc/etc.nix:12:5:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/nixos/modules/system/etc/etc.nix:20:20, called from undefined position:
while evaluating the attribute 'source' at undefined position:
while evaluating 'g' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/attrsets.nix:294:19, called from undefined position:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:139:72, called from /nix/var/nix/profiles/per-user/root/channels/nixos/lib/attrsets.nix:297:20:
while evaluating the attribute 'value' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:523:9:
while evaluating the option `environment.etc.containers/dnsmasq.conf.source':
while evaluating the attribute 'mergedValue' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:555:5:
while evaluating the attribute 'values' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:549:9:
while evaluating the attribute 'values' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:648:7:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:535:28, called from /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:535:17:
while evaluating definitions from `/nix/var/nix/profiles/per-user/root/channels/nixos/nixos/modules/system/etc/etc.nix':
while evaluating 'dischargeProperties' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:607:25, called from /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:536:137:
while evaluating the attribute 'condition' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:691:14:
while evaluating the attribute 'text' at undefined position:
while evaluating 'g' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/attrsets.nix:294:19, called from undefined position:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:139:72, called from /nix/var/nix/profiles/per-user/root/channels/nixos/lib/attrsets.nix:297:20:
while evaluating the attribute 'value' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:523:9:
while evaluating the option `environment.etc.containers/dnsmasq.conf.text':
while evaluating the attribute 'mergedValue' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:555:5:
while evaluating the attribute 'values' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:549:9:
while evaluating the attribute 'values' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:648:7:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:535:28, called from /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:535:17:
while evaluating definitions from `/nix/var/nix/profiles/per-user/root/channels/nixos/nixos/modules/virtualisation/nixos-containers.nix':
while evaluating 'dischargeProperties' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:607:25, called from /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:536:137:
while evaluating the attribute 'value' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:390:44:
while evaluating the attribute 'path' at undefined position:
while evaluating 'g' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/attrsets.nix:294:19, called from undefined position:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:139:72, called from /nix/var/nix/profiles/per-user/root/channels/nixos/lib/attrsets.nix:297:20:
while evaluating the attribute 'value' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:523:9:
while evaluating the option `containers.dnsmasq.path':
while evaluating the attribute 'mergedValue' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:555:5:
while evaluating the attribute 'values' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:549:9:
while evaluating the attribute 'values' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:648:7:
while evaluating anonymous function at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:535:28, called from /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:535:17:
while evaluating definitions from `/nix/var/nix/profiles/per-user/root/channels/nixos/nixos/modules/virtualisation/nixos-containers.nix':
while evaluating 'dischargeProperties' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:607:25, called from /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:536:137:
while evaluating 'dischargeProperties' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:607:25, called from /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:613:11:
while evaluating the attribute 'content' at /nix/var/nix/profiles/per-user/root/channels/nixos/lib/modules.nix:691:14:
while evaluating the attribute 'config.system.build.toplevel' at /nix/store/4nnwdin1z6qai7rshidrk584p476rng3-nixos-21.05pre281538.9e377a6ce42/nixos/nixos/modules/system/activation/top-level.nix:294:5:
while evaluating 'foldr' at /nix/store/4nnwdin1z6qai7rshidrk584p476rng3-nixos-21.05pre281538.9e377a6ce42/nixos/lib/lists.nix:52:20, called from /nix/store/4nnwdin1z6qai7rshidrk584p476rng3-nixos-21.05pre281538.9e377a6ce42/nixos/nixos/modul
es/system/activation/top-level.nix:129:12:
while evaluating 'fold'' at /nix/store/4nnwdin1z6qai7rshidrk584p476rng3-nixos-21.05pre281538.9e377a6ce42/nixos/lib/lists.nix:55:15, called from /nix/store/4nnwdin1z6qai7rshidrk584p476rng3-nixos-21.05pre281538.9e377a6ce42/nixos/lib/lists.n
ix:59:8:
while evaluating anonymous function at /nix/store/4nnwdin1z6qai7rshidrk584p476rng3-nixos-21.05pre281538.9e377a6ce42/nixos/nixos/modules/system/activation/top-level.nix:122:50, called from undefined position:
while evaluating the attribute 'assertion' at /nix/var/nix/profiles/per-user/root/channels/nixos/nixos/modules/virtualisation/nixos-containers.nix:484:31:
while evaluating the attribute 'boot.kernelPackages.kernel.version' at undefined position:
attribute 'kernelPackages' missing, at /nix/var/nix/profiles/per-user/root/channels/nixos/nixos/modules/virtualisation/nixos-containers.nix:275:19

nix repl tab completes the following in a normal environment:
> x = import /nix/var/nix/profiles/per-user/root/channels/nixos/nixos/lib/eval-config.nix {modules = [(import /etc/nixos/configuration.nix)]; }
nix-repl> x.config.boot.kernel
x.config.boot.kernel          x.config.boot.kernelModules   x.config.boot.kernelPackages  x.config.boot.kernelParams    x.config.boot.kernelPatches

and the following in a container:
> x = import /nix/store/8kigqgbq0xfzac8m0lnqjnmf2rnnqmj3-extra-container-0.6/bin/../share/extra-container/eval-config.nix <nixpkgs/nixos> ./container.nix
nix-repl> x.config.boot.kernel
x.config.boot.kernel         x.config.boot.kernelModules  x.config.boot.kernelParams

It looks like https://github.com/erikarvstedt/extra-container/blob/307366f0d4c651b8aa6dd6594b7070404aa8a8a7/eval-config.nix#L31 might be part of the issue.

I'm a bit confused as to how one even would go about solving this, because kernel version is from the perspective of of a container, impure state independent of the container's configs. The impure state would have to be inspected no?

I wonder if better behavior would be to just remove the check altogether...

It seems that upstream actually changed their mind and now truncates to a random hash when the name is too long. So I think we can remove the check altogether properly now? If a longer name is used on an older kernel, systemd will use the hash of the name
https://github.com/systemd/systemd/pull/14467

Well that seems the best but I think the check is also valid and useful thing, so I don't know what would be good...

@arianvp the issue is that our scripts assume that a device named ve-${containerName} exists. On newer kernels (5.8+) it "just works" because systemd assigns altnames (so both ve-${hash} and ve-${containerName} exist and refer to the same interface), but it would fail on older kernels (where there's only ve-${containerHash}).
In order to drop the assertion safely, instead of relying on ve-${containerName}, we could retrieve this shortened, hashed name from systemd - but last time I checked it (when I was implementing https://github.com/NixOS/nixpkgs/pull/100433), I couldn't find an easy, reliable way to ask systemd "what's name of interface for container %s?".

@deliciouslytyped I've just checked and NixOS's containers-in-containers still work, it's only https://github.com/erikarvstedt/extra-container that, unfortunately, got broken in the process :-/

It might not break during eval, but do the kernel version values even make sense?

Can we add an option to disable this until there is a better solution?

@deliciouslytyped I think it should be possible to detect whether kernelModules are empty and, if so, automatically ignore the assertion; I'll try to prepare a patch today 🙂

@deliciouslytyped on a second thought, there's https://github.com/erikarvstedt/extra-container/pull/18, which I'd personally prefer as a less intrusive attempt than a workaround inside Nixpkgs; does that solution work for you, too?

What of the issue that kernelVersion doesn't make sense in containers?

@deliciouslytyped ah, I see your point now (from that linked pull request):

It's a value nixpkgs generates, instead of deriving it from the environment.

Yes, in this sense the best solution would be to check kernel version during nixos-rebuild switch (or a similar command); I started with an assertion, because I wasn't sure how to implement it otherwise 😛
I'll try to come up with some solution, but pull requests changing that build-time assertion into a runtime one are more than welcome 🙂

If you are really against reverting, I think merging a toggle in the interim as a bypass or something of the sort would be OK and give time to deal with a more proper fix.
Not to predicate fixing it on a bigger project - but the proper fix sounds like it might be worth a bigger project and PR.


UI/Devex fixes/improvements

Some modifications after writing up the docs a bit and going through the steps:

Rename NEXT_PUBLIC_ALCHEMY_URI_SEPOLIA to NEXT_PUBLIC_PROVIDER_URI_SEPOLIA (using only Alchemy was only applicable for Autonomous Airdrop example)
Fixes silent failure when on incorrect network (button changes to "Switch to Sepolia")
Copies over some useful components from the new Autonomous Airdrop example

Tests:

Sent query
Received callback
Switched networks

@ytham -- after merging, can you also test that this works with npx create-axiom-client ?

@ytham -- after merging, can you also test that this works with npx create-axiom-client ?

yes sounds good


Fix ambiguous timestep dimension in timeseries data.

What is the issue?
Euro-Calliope code did not fully follow a standard when creating timeseries files, and uses a lot of very different names for the rows: timeseries, timeserie, time, generated-utc...
In combination with this calliope issue (https://github.com/calliope-project/calliope/issues/678), it makes timeseries incompatible with v0.7.
Solution
Always use timeseries for the rows. It's generic enough that anybody outside the Calliope world will understand it, and avoids incompatibility with Calliope.

Partially fixed by #49 (hydropower, heat).
We need to ensure this works before merging the new timeseries modules.


Add json loader

Adding json-loader to default storybook loaders. This is a fix for kadirahq/react-storybook-addon-info#12.

I see a tiny problem here. In my webpack config I already have json loader defined.
{ test: /\.json$/, loader: 'json', include: srcPath },

I have some JSON files in application itself to be loaded.
In storybook/webpack.config.js I have it like this.
var pathUtils = require('path');
var merge = require('webpack-merge');
var validate = require('webpack-validator');
var baseConfig = require('../webpack.config.js');

module.exports = function(storybookConfig) {
	var config = merge.smart(storybookConfig, {
		devtool: 'source-map',
		module: baseConfig.module,
		resolve: baseConfig.resolve,
	});
	return validate(config);
};

That means the json loader will be merged together and include path will be preserved there causing that addon requirement wont be fulfilled anyway.

We fix this with a much better way. See: https://github.com/kadirahq/react-storybook-addon-info/issues/12


Remove orphaned page from French localization

The upstream (English) page is gone and only French still has this page.
Remove it.
/kind cleanup

/lgtm

I'll use this PR to demo for https://github.com/kubernetes/test-infra/pull/22663#issuecomment-871522992

Ping fr team for approval,
/cc @kubernetes/sig-docs-fr-reviews

/approve


RB guess to use decay guess

Summary
Fixes #239.
Currently RB has its own code to generate default guesses, separate from the code of general decay analysis. This PR cleans the code by removing this duplication.
Details and comments

It makes sense that RBAnalysis will inherit from DecayAnalysis. Do you think it makes sense that InterlavedRBAnalysis will continue to inherit from RBAnalysis? Possibly it was not correct from the beginning, because interleaved RB analysis is not a type of RB analsysis; it uses RB analysis. Now it becomes more noticeable, because interleaved RB analysis is certainly not a type of decay analysis.

yes, I was thinking the same thing, but slightly different. I think IRB is kind of RB analysis, but RB analysis implements the post analysis for EPG computation which is not necessary for other RBs We need some kind of base RB analysis, and SRB analysis with EPG computation and IRB analysis both inheriting from the base.

In what sense is IRB a type of RB ?  It could inherit from BaseAnalysis, and maintain two data members of type RBAnalysis.

Stale, closing


[navigation-drawer] Display both unread and flagged message counts

Issue:
In v5.8 the navigation drawer would only display the unread message count in the fragment badges.
Solution:
This PR displays both unread and flagged message counts in the fragment badges (see screen shot below)
Note:
The PR is not yet complete!!
So far it only has the front end UI code, and it is still missing the back end code to fetch the flagged message count from the mail server.

Thanks for taking the time to create a pull request :heart:
Regarding the development process:

While the pull request is not ready yet, please mark it as a draft.
For questions around development, please use the discussions section here on GitHub, not the forum. (I'm also happy to answer questions in our Matrix chat channel. But let's try to keep generic questions to GitHub, so others can benefit from the answers, too.)

Regarding the feature:

I don't want this to be the default. I believe only displaying the unread count makes the user interface far less cluttered and thus more beginner-friendly.
I don't particularly like adding settings either. But this seems like functionality enough people seem to want (back). So making it an optional feature is probably the way to go.

It's fine working on the feature first, then adding a setting later.

While the pull request is not ready yet, please mark it as a draft.

The PR labels box is read only, so I just added the text "DRAFT" to the title.

I don't want this to be the default

Ok.

The link to convert an existing pull request to a draft is not easy to find. It's in the "reviewers" section.

Ok, marked as DRAFT now.
I think that I will need help with fetching the flagged message count from the backend. In prior versions, there was code to fetch it, but it seems that in v5.x that code was deleted. And due to the refactoring of the project structure from v4.x to v5.x I cannot figure out where the respective code got to..

I think that I will need help with fetching the flagged message count from the backend.

You'll have to add another subquery for the number of starred messages. It's basically the same as this, only with checking the messages.flagged column instead of messages.read:
https://github.com/k9mail/k-9/blob/03fb2b953840a667f452c8a8d65ddb15f84b8348/app/storage/src/main/java/com/fsck/k9/storage/messages/RetrieveFolderOperations.kt#L72-L76
Let me know if you're still having trouble making the backend changes. I'm happy to provide a patch.
We sometimes use the term "flagged messages", sometimes "starred messages". I think "starred" is clearer and we should use that in new code.

It's basically the same as this, only with checking the messages.flagged column instead of messages.read

Thanks for the info. I will have another attempt.

I think "starred" is clearer and we should use that in new code.

Understood. Actually I started using "starred" and then refactored all the names to "flagged" in order to be more backwards compatible! But I can easily re-re-factor it again.

Hi @cketti, I just pushed a commit with the following changes..

Refactored flaggedCount back to starredCount again
Added a second SQL sub query to calculate starredCount

I have tested this, and I can confirm that it works perfectly for the Navigation Drawer "Folder View". But unfortunately I was not able to do the coding for the "Account View" and the "Unified Inbox View" as shown "TODO" in the links below. Basically I don't understand enough about the Kotlin Flow concept to be able write this code: => so I would appreciate it if you could give me any tips :)
K9Drawer.kt

AccountsViewModel.kt

The original intent of this PR was to display the following..

Starred and unread message counts in folder view navigation drawer items
Starred and unread message counts in account view navigation drawer items
Starred and unread message counts in unified inbox navigation drawer item

I have coded and tested item 1. above, but I lack the coding skills for items 2. and 3. -- to be specfic..

How to fetch from the back end the starred message counts for account view navigation drawer items
How to fetch from the back end the starred and unread message counts for unified inbox navigation drawer item

So I have decided to split this PR into two parts -- namely item 1. resp. items 2. & 3. With today's commit the functionality of item 1. is assured and tested. And the functionality of item 2. & 2. is suppressed (there are code stubs TODO but nothing will display).
I am therefore converting this part 1. PR from DRAFT to READY FOR REVIEW

@cketti IMHO this PR is now fully ready with all functionality and fully tested .. (at least it is fully ready for review)

PS I also added a new setting for "Show Starred Message Count" with a default value of FALSE

IMHO this should solve https://github.com/k9mail/k-9/issues/5570

@cketti many thanks for the review. I think I have addressed all your issues, so it is ready to review again IMHO.
Also I would like to suggest that if the user has more than one account, then the navigation drawer should open by default in the account view (below), whereas if the user has just one account it should open in folder view. => What do you think?

You can use ./gradlew ktlintFormat to fix Kotlin code style violations.

You can use ./gradlew ktlintFormat to fix Kotlin code style violations.

Thanks for the tip. Generally I use Eclipse IDE which does auto formatting on save. So Android Studio seems rather retrogade in not having that feature.

Phew! All CI tests passed - finally..

@cketti I like the changes you have made. Obviously some reflect your personal coding style preferences, but others are very clever. Please excuse the difficult birth of this PR; although I have decades of coding experience on many platforms, in many languages, and in many IDEs, this was my first on Android / Kotlin / Android Studio. So in fact a quite steep learning process. Thank you for your assistance in this.

Thanks for contributing to K-9 Mail :heart:

Please excuse the difficult birth of this PR

Forget about it. This went a lot smoother than the average pull request of comparable complexity :+1:


[wifi sal]: fix sal issue which sal fw version is not ready

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.jianlong.gaojianlo 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.


Readme says mongodb is optional, but sacred crashes without pymongo

mongodb is described as being optional, but hello world example crashes without pymongo
minimal example is making a virtualenv
virtualenv --python=python3 ./sacred-env
source ./sacred-env/bin/activate
pip install sacred
python dbg.py

#dbg.py
from sacred import Experiment
ex = Experiment()

@ex.main
def my_main():
    pass

resulting in
Traceback (most recent call last):
  File "dbg.py", line 1, in <module>
    from sacred import Experiment
  File "/src/dir/python/sacred-env/lib/python3.5/site-packages/sacred/__init__.py", line 15, in <module>
    from sacred import observers
  File "/src/dir/python/sacred-env/lib/python3.5/site-packages/sacred/observers/__init__.py", line 7, in <module>
    from sacred.observers.mongo import MongoObserver
  File "/src/dir/python/sacred-env/lib/python3.5/site-packages/sacred/observers/mongo.py", line 13, in <module>
    import pymongo
ImportError: No module named 'pymongo'

I believe that this issue can be closed with #519 . @JarnoRFB

True thanks for reporting @sjTaylor


Update CloudEvents

Signed-off-by: Doug Davis<EMAIL_ADDRESS>Pre-submission checklist:
Please check each of these after submitting your pull request:

[x] Are you only including a repo_url if your project is 100% open source? If so, you need to pick the single best GitHub repository for your project, not a GitHub organization.
[x] Is your project closed source or, if it is open source, does your project have at least 300 GitHub stars?
[x] Have you picked the single best (existing) category for your project?
[x] Does it follow the other guidelines from the new entries section?
[x] Have you added your SVG to hosted_logos and referenced it there?
[x] Does your logo clearly state the name of the project/product and follow the other logo guidelines?
[x] Does your project/product name match the text on the logo?
[x] Have you verified that the Crunchbase data for your organization is correct (including headquarters and LinkedIn)?
[ ] ~30 minutes after opening the pull request, the CNCF-Bot will post the URL for your staging server. Have you confirmed that it looks good to you and then added a comment to the PR saying "LGTM"?

I can't view the logs from netlify to see what's wrong

@onlydole made the suggested edits. Any idea why netlify isn't happy?

Looks like Netlify has an error and no logs are showing for me.
@AndreyKozlov1984 - do you see what the error is?

LGTM


Disable RefreshScope in Config Server for AOT and native

See https://github.com/spring-projects-experimental/spring-native/blob/main/spring-native/src/main/java/org/springframework/aot/beans/factory/config/NoOpScope.java

Trying to understand this issue (as I've been asked about it from MSFT): Why is this needed and is it in reference to Config Server itself or the clients of Config Server that might be natively compiled?
I've tested a natively-compiled client app with @RefreshScope and it works fine for the most part, with the only thing odd being the timing of when the refresh-scoped bean is reinstantiated after config changes and a POST to the refresh endpoint is sent. So, I'm just trying to gain better understanding of why disabling refresh scope is important and whether this is intended for the config server itself or its clients (or both).

@OlgaMaciaszek is on vacation but I will try and answer
I believe it is for both.
The main problem (i believe) is that a configuration change could change the logic and which beans are enabled/disabled and that could break a native app.  In general it seem like a bad idea to change the configuration of an application that is compiled natively.

Thanks, @ryanjbaxter - that's right. Any config that can influence context creation should not change from build time to runtime, which is in keeping with the Graal Native images closed world assumption and the Spring AOT processing model  does not support it. A lot of times with refresh scope enabled, natively compiled Spring Cloud applications won't even run. If they do, unexpected behaviour might occur, so we strongly discourage using it this way.

Understood and that's fair. So would this just disable the effects of @RefreshScope rendering the annotation inert? In other words, if the app is using @RefreshScope, it would still compile natively and run fine...it just wouldn't reinstantiate beans if the config changes, right?

That would be my assumption yes.  It would also be nice if we could render a warning somewhere stating that is the case.

Sure, there's info in the docs and this issue is queued precisely to add better handling in apps.

Hey @OlgaMaciaszek , sorry for pinging, but if I got this right this means that if any property changes, bean that already exists won't be reloaded with latest values and refreshed? (both for restart and hot reload?)
I fully understand the point regarding enable/disable bean and this makes total sense, but what if you want to change url of webclient?
I am currently writing native hints for Spring Cloud AWS as we have few integrations with spring.config.import and we support refresh on property change. From my perspective wouldn't it make sense to be able to refresh with restart option since you are only changing a property of bean such as url? Again, I fully see point for enable/disable since it needs to be provided on creation of executable.


V0.19.0

should wait until 0.19.0 is actually released, but the CI tests will still be helpful

Weird error on the Invalid column name 'id'. for the test_dbt_snapshot_strategy_timestamp test.
2021-01-11 17:02:59.100974 (MainThread): Completed with 2 errors and 0 warnings:
2021-01-11 17:02:59.101065 (MainThread):
2021-01-11 17:02:59.101149 (MainThread): Database Error in test failing (test/failing.sql)
2021-01-11 17:02:59.101219 (MainThread):   ('42S22', "[42S22] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid column name 'id'. (207) (SQLExecDirectW)")
2021-01-11 17:02:59.101282 (MainThread):   compiled SQL at target/compiled/dbt_test_project/test/failing.sql
2021-01-11 17:02:59.101349 (MainThread):
2021-01-11 17:02:59.101423 (MainThread): Database Error in test passing (test/passing.sql)
2021-01-11 17:02:59.101518 (MainThread):   ('42S22', "[42S22] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid column name 'id'. (207) (SQLExecDirectW)")
2021-01-11 17:02:59.101581 (MainThread):   compiled SQL at target/compiled/dbt_test_project/test/passing.sql

Weird error on the Invalid column name 'id'. for the test_dbt_snapshot_strategy_timestamp test.
2021-01-11 17:02:59.100974 (MainThread): Completed with 2 errors and 0 warnings:
2021-01-11 17:02:59.101065 (MainThread):
2021-01-11 17:02:59.101149 (MainThread): Database Error in test failing (test/failing.sql)
2021-01-11 17:02:59.101219 (MainThread):   ('42S22', "[42S22] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid column name 'id'. (207) (SQLExecDirectW)")
2021-01-11 17:02:59.101282 (MainThread):   compiled SQL at target/compiled/dbt_test_project/test/failing.sql
2021-01-11 17:02:59.101349 (MainThread):
2021-01-11 17:02:59.101423 (MainThread): Database Error in test passing (test/passing.sql)
2021-01-11 17:02:59.101518 (MainThread):   ('42S22', "[42S22] [Microsoft][ODBC Driver 17 for SQL Server][SQL Server]Invalid column name 'id'. (207) (SQLExecDirectW)")
2021-01-11 17:02:59.101581 (MainThread):   compiled SQL at target/compiled/dbt_test_project/test/passing.sql

There are ci tests on the branch? https://app.circleci.com/pipelines/github/dbt-msft/dbt-sqlserver?branch=v0.19.0&utm_campaign=workflow-failed&utm_medium=email&utm_source=notification

There are ci tests on the branch? https://app.circleci.com/pipelines/github/dbt-msft/dbt-sqlserver?branch=v0.19.0&utm_campaign=workflow-failed&utm_medium=email&utm_source=notification

I don't get that error when testing local?

I don't get that error when testing local?

@mikaelene I made this PR so now every change that is pushed to the v0.19.0 branch will now get tested. Should be helpful to have in addition to your local testing, but I might have goofed something w/ CircleCi...

@mikaelene I made this PR so now every change that is pushed to the v0.19.0 branch will now get tested. Should be helpful to have in addition to your local testing, but I might have goofed something w/ CircleCi...

I noticed some weird behaviour that the latest version, even installed from git does not include the latest commit. Can't get my mind around why it is happening. I'll try to hardcode the latest commit.

I noticed some weird behaviour that the latest version, even installed from git does not include the latest commit. Can't get my mind around why it is happening. I'll try to hardcode the latest commit.

I don't get why it uses the old version. Incorrect syntax near '!'. is what is supposed to be fixed. Maybe we have to wait?!?... Thanks for trying @swanderz !

I don't get why it uses the old version. Incorrect syntax near '!'. is what is supposed to be fixed. Maybe we have to wait?!?... Thanks for trying @swanderz !

@jtcohen6 sorry to pull in into yet another dbt-msft PR, but any idea why CircleCI isn't pulling the latest commit from dev/kiyoshi-kuromiya?

@jtcohen6 sorry to pull in into yet another dbt-msft PR, but any idea why CircleCI isn't pulling the latest commit from dev/kiyoshi-kuromiya?

I think the package are cached by circleCI. Since it is the same version on the new changes it will still take the cached version of the package.

I think the package are cached by circleCI. Since it is the same version on the new changes it will still take the cached version of the package.

I think the package are cached by circleCI. Since it is the same version on the new changes it will still take the cached version of the package.

I think you're onto something. However, I'm trying to read about clearing the cache and my head is spinning...

I think the package are cached by circleCI. Since it is the same version on the new changes it will still take the cached version of the package.

I think you're onto something. However, I'm trying to read about clearing the cache and my head is spinning...

I think I have solved it. Pushing in a minute

I think I have solved it. Pushing in a minute

AAAHHHHHH! I am getting crazy! :-)

AAAHHHHHH! I am getting crazy! :-)

@swanderz @mikaelene I'm not enough of a Circle pro for this one. Does it work when you run these tests locally?
In all likelihood, we'll be coming out with a second RC this week, given the (tiny) changes we've merged since the first one.

@swanderz @mikaelene I'm not enough of a Circle pro for this one. Does it work when you run these tests locally?
In all likelihood, we'll be coming out with a second RC this week, given the (tiny) changes we've merged since the first one.

It works locally and it fails in CircleCI on the thing we fixed in the latest commits.

It works locally and it fails in CircleCI on the thing we fixed in the latest commits.

@swanderz @mikaelene I'm not enough of a Circle pro for this one. Does it work when you run these tests locally?
In all likelihood, we'll be coming out with a second RC this week, given the (tiny) changes we've merged since the first one.

yeah i found an option for circleci python orb's install-packages orb, pypi-cache: false but no luck...
I'm still going to make a release cut of this so I can keep testing w/ Synapse

@swanderz @mikaelene I'm not enough of a Circle pro for this one. Does it work when you run these tests locally?
In all likelihood, we'll be coming out with a second RC this week, given the (tiny) changes we've merged since the first one.

yeah i found an option for circleci python orb's install-packages orb, pypi-cache: false but no luck...
I'm still going to make a release cut of this so I can keep testing w/ Synapse

I'm still going to make a release cut of this so I can keep testing w/ Synapse

update: somehow test_dbt_snapshot_strategy_timestamp is passing over in https://github.com/dbt-msft/dbt-synapse/pull/39
_________________________ usecase: test_dbt_data_test __________________________
usecase execution failed
   spec failed: ("Invalid result, missing required key 'unique_id'",)
   no further details known at this point.

I'm still going to make a release cut of this so I can keep testing w/ Synapse

update: somehow test_dbt_snapshot_strategy_timestamp is passing over in https://github.com/dbt-msft/dbt-synapse/pull/39
_________________________ usecase: test_dbt_data_test __________________________
usecase execution failed
   spec failed: ("Invalid result, missing required key 'unique_id'",)
   no further details known at this point.

It is now on PyPi

It is now on PyPi

I want to merge this to master but can't male the tests pass locally. Actually I don't see how they can work in CircleCI either. Or why they worked before. From my understanding the data test executes
with dbt__CTE__INTERNAL_test as ( select 1 as id where id = 1 )select count(*) from dbt__CTE__INTERNAL_test
and  select 1 as id where id = 1 can't be executed on SQL Server?!
I get Invalid column name 'id' which makes sense as I get that when executing the SQL in my Editor on SQL Server. It works on other DBs.
Anyone have a clue why this works in the CircleCI env?

I want to merge this to master but can't male the tests pass locally. Actually I don't see how they can work in CircleCI either. Or why they worked before. From my understanding the data test executes
with dbt__CTE__INTERNAL_test as ( select 1 as id where id = 1 )select count(*) from dbt__CTE__INTERNAL_test
and  select 1 as id where id = 1 can't be executed on SQL Server?!
I get Invalid column name 'id' which makes sense as I get that when executing the SQL in my Editor on SQL Server. It works on other DBs.
Anyone have a clue why this works in the CircleCI env?

Anyone have a clue why this works in the CircleCI env?
I have no idea! and I've been banging my head on this for a week now....

Anyone have a clue why this works in the CircleCI env?
I have no idea! and I've been banging my head on this for a week now....

It actually passes when run with tox. I don't get this tox thing but I'll do the merge.

It actually passes when run with tox. I don't get this tox thing but I'll do the merge.


Avoid iTunes to auto start

Is there a way to avoid iTunes to autostart every time? If the api is running iTunes is always running. If I close it, iTunes-api opens it again! Can it only open iTunes if you actually want to play something?
Thanks!

The API talks directly to iTunes over AppleScript. It can't function without iTunes open.

to @benquan's request, I would like the following:

If iTunes is open, itunes-api works as expected
If iTunes is closed, itunes-api goes in to 'dormant mode', possibly simply ignoring commands or opening iTunes when a media event is called (play, etc)

I'm cool with iTunes needing to be open for itunes-api, I just don't want iTunes open all the time.


Syncing certs between control-plane instances

After the initial control-plane has started, sync the certs with the "ha" control-planes instances.

will be solved with https://github.com/Smana/terraform-kubernetes/pull/12

will be solved with https://github.com/Smana/terraform-kubernetes/pull/12


Feature request: Store download state in persistent memory

Downloads usually take a long time and data costs are high with low-bandwidth networks, such as NB-IoT. It would be nice to have a possibility to save the current download state to be able to continue later without needing to repeat the already downloaded blocks, e.g. in case of a reset/power loss. Is such a feature planned?

Hello , The library supports resuming a download but it does not store the context in NVM memory . We are reviewing the feature requests but at this time I do not have a release data for this feature. When file blocks are received they are stored in a bitmap, resetting a bit corresponding to the file block. This needs to be stored in the NVM and restored when it boots up.

No further development will be performed on this library. See the readme.


added env and envFrom for initContainers

env and envFrom were missing when running custom initContainers for proxy, broker, brokerSts and function deployments/statefulsets.
This adds those values, also I noticed initContainer.args is definied in the templates but was missing in values.yaml

apologies, not sure what's with all the trailing spaces :sweat_smile:

No worries, I didn't realize trailing spaces in comments would fail the linter.


Support loading options from config/delayed_job.yml

One of the nice things about Sidekiq is being able to save all your commandline options in a config file so you can reuse that everywhere. I just wanted to add the same functionality to delayed_job so that it would be easier to manage and track your options in git as well.

👍 Love it!

This is fantastic, thanks a lot!
I hope the maintainers merge this into DJ soon.
Thanks!

I'm personally against checked-in config files but lots of people seem to like them. I don't have strong feelings about whether this is in scope or not for DJ.

@betamatt are there any updates on the status of this PR?


Shorten refer start path

This has been shortened in the UI, so it needs updating here

 Remove course/:courseid from URL params in Refer


HMR is broken for React

Package version
3.0.0-5
Describe the bug
See the attached video to get the context of the issue
Screencast from 2024-03-04 20-54-30.webm
And here's the repo for the reproduction of this issue
Reproduction repo
https://github.com/muco-rolle/adonis-inertia-demo

Hey
add this to your adonisrc.ts
import { defineConfig } from '@adonisjs/core/app'

export default defineConfig({
  assetsBundler: false,
  unstable_assembler: {
    onBuildStarting: [() => import('@adonisjs/vite/build_hook')],
  },
})

and also this to your root tsconfig :
  "exclude": ["./resources/**/*"]

and you should be good.
This repo can be used as a reference : https://github.com/adonisjs/inertia-starter-kit
Wait a few days for the official release and documentation that will explains that
Feel free to reopen if issue persists

It works. Thanks!


Add Bhutan

Coverage remained the same at 96.522% when pulling d820a850f403b57608cccdf94e71d33c5ac15a4d on addBhutan into 6b1d362c05e0faafeb28e4adfd39799029f5be0a on main.


"Could not resolve the rosdep key 'rosaria" while integrating 2 packages in the build farm

Hi,
Yestreday I integrated two new packages, but it seems that it made a failure during the integration process in the build farm.
I can understand the error for xenial since rosaria doesn't exist in distibution.yaml file of kinetic.
But I don't understand why the same error occurred for trusty (because rosaria package is present distibution.yaml file for both indigo and jade)
Here's the build log (truncated):
Step 23 : CMD rosdep update && PYTHONPATH=/tmp/ros_buildfarm:$PYTHONPATH python3 -u /tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py --rosdistro-name indigo --workspace-root /tmp/catkin_workspace --os-name ubuntu --os-code-name trusty --arch amd64 --distribution-repository-urls http://repositories.ros.org/ubuntu/testing --distribution-repository-key-files /tmp/keys/0.key --dockerfile-dir /tmp/docker_build_and_install && PYTHONPATH=/tmp/ros_buildfarm:$PYTHONPATH python3 -u /tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py --rosdistro-name indigo --workspace-root /tmp/catkin_workspace --os-name ubuntu --os-code-name trusty --arch amd64 --distribution-repository-urls http://repositories.ros.org/ubuntu/testing --distribution-repository-key-files /tmp/keys/0.key --dockerfile-dir /tmp/docker_build_and_test --testing
 ---> Running in 9ba9f849c31f
 ---> f40aee10c2ed
Removing intermediate container 9ba9f849c31f
Successfully built f40aee10c2ed
+ echo # END SECTION
# END SECTION
+ echo # BEGIN SECTION: Run Dockerfile - generating devel tasks
# BEGIN SECTION: Run Dockerfile - generating devel tasks
+ rm -fr <http://build.ros.org/job/Idev__pioneer_bringup__ubuntu_trusty_amd64/ws/docker_build_and_install>
+ rm -fr <http://build.ros.org/job/Idev__pioneer_bringup__ubuntu_trusty_amd64/ws/docker_build_and_test>
+ mkdir -p <http://build.ros.org/job/Idev__pioneer_bringup__ubuntu_trusty_amd64/ws/docker_build_and_install>
+ mkdir -p <http://build.ros.org/job/Idev__pioneer_bringup__ubuntu_trusty_amd64/ws/docker_build_and_test>
+ docker run --rm --cidfile=<http://build.ros.org/job/Idev__pioneer_bringup__ubuntu_trusty_amd64/ws/docker_generating_dockers/docker.cid> -e=HOME=/home/buildfarm -v <http://build.ros.org/job/Idev__pioneer_bringup__ubuntu_trusty_amd64/ws/ros_buildfarm>:/tmp/ros_buildfarm:ro -v <http://build.ros.org/job/Idev__pioneer_bringup__ubuntu_trusty_amd64/ws/catkin_workspace>:/tmp/catkin_workspace:ro -v <http://build.ros.org/job/Idev__pioneer_bringup__ubuntu_trusty_amd64/ws/docker_build_and_install>:/tmp/docker_build_and_install -v <http://build.ros.org/job/Idev__pioneer_bringup__ubuntu_trusty_amd64/ws/docker_build_and_test>:/tmp/docker_build_and_test -v /home/jenkins-slave/.ccache:/home/buildfarm/.ccache devel_task_generation.indigo_pioneer_bringup
reading in sources list data from /etc/ros/rosdep/sources.list.d
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/osx-homebrew.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/base.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/python.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/rosdep/ruby.yaml
Hit https://raw.githubusercontent.com/ros/rosdistro/master/releases/fuerte.yaml
Query rosdistro index https://raw.githubusercontent.com/ros/rosdistro/master/index.yaml
Add distro "groovy"
Add distro "hydro"
Add distro "indigo"
Add distro "jade"
Add distro "kinetic"
updated cache in /home/buildfarm/.ros/rosdep/sources.cache
Crawling for packages in workspace '/tmp/catkin_workspace/src'
Found the following packages:
  - pioneer_bringup
Package maintainer emails<EMAIL_ADDRESS>Always install the following generic dependencies:
  - build-essential
  - python3
  - ros-indigo-catkin
Identified the following build dependencies (ignoring packages available from source):
  - catkin
Resolved the dependencies to the following binary packages:
  - ros-indigo-catkin
Identified the following run and test dependencies (ignoring packages available from source):
  - geometry_msgs
  - lms1xx
  - rosaria
  - rospy
  - usb_cam
Traceback (most recent call last):
  File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 232, in resolve_names
    rosdep_key, view, installer, os_name, os_code_name)
  File "/usr/lib/python3/dist-packages/rosdep2/catkin_support.py", line 81, in resolve_for_os
    d = view.lookup(rosdep_key)
  File "/usr/lib/python3/dist-packages/rosdep2/lookup.py", line 187, in lookup
    return self.rosdep_defs[rosdep_name]
KeyError: 'rosaria'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 248, in <module>
    main()
  File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 122, in main
    run_and_test_depends, **context)
  File "/tmp/ros_buildfarm/scripts/devel/create_devel_task_generator.py", line 235, in resolve_names
    "Could not resolve the rosdep key '%s'" % rosdep_key)
RuntimeError: Could not resolve the rosdep key 'rosaria'
Build step 'Execute shell' marked build as failure
[WARNINGS]Skipping publisher since build result is FAILURE
[xUnit] [INFO] - Starting to record.
[xUnit] [INFO] - Processing GoogleTest-1.6
[xUnit] [INFO] - [GoogleTest-1.6] - No test report file(s) were found with the pattern 'catkin_workspace/test_results/**/*.xml' relative to '<http://build.ros.org/job/Idev__pioneer_bringup__ubuntu_trusty_amd64/ws/'> for the testing framework 'GoogleTest-1.6'.  Did you enter a pattern relative to the correct directory?  Did you generate the result report(s) for 'GoogleTest-1.6'?
[xUnit] [WARNING] - No test reports found for the metric 'GoogleTest' with the resolved pattern 'catkin_workspace/test_results/**/*.xml'.
[xUnit] [INFO] - Skipping the metric tool processing.
[xUnit] [INFO] - There are errors when processing test results.
[xUnit] [INFO] - Skipping tests recording.

The devel job for pioneer_bringup needs to install its dependencies. But rosaria has not been released yet. It only has a doc and source entry but no release entry and therefore no Debian package which can be installed in order to test downstream packages. If you want the devel jobs for pioneer_bringup to pass you need to release all its dependencies.


module not found after change the modules path in configuration

I created some modules by default structure in Modules directory
then i change the config to create the modules in workbench directory
'modules' => base_path('workbench'),
then
php artisan module:list
all modules in Modules directory no found
@nWidart is there any solution for that ??

I just solved a similar problem moving from my development machine (Mac) to an Amazon Ec2 instance (ubuntu). If you have upgraded from the defunct pingpong package, know that for whatever reason this fork is sensitive to directory case.
When running pingpong, my directory worked fine as /modules/SomeModule
But after moving this fork into our test server (ubuntu EC2) I needed to (at least temporarily) create a symbolic link from modules to Modules with:
ln -s modules Modules
Don't forget to do a composer dumpautoload to pick up your modules.
You can test to see exactly what path you're looking for by running php artisan tinker
then
Module::getScanPaths();

You should get back:
=> [
    "/var/www/lms-laravel/Modules/*",
]

See how "Modules" is now capitalized? I don't why that happened, but If you see that, it's a case sensitivity issue. Try the symbolic link. If that corrects the problem, we'll need to understand why a composer.json that autoloads like this:
"psr-4": {
    "App\\": "app/",
    "Modules\\": "modules/"
},

doesn't find the modules path.


Concurrent surveys

Hello. I would like to express a feature I've been trying to pull out and hear your comments.
The idea is to make several users to fill one survey in a concurrent fashion. I know it will cause massive usability problems, collisions and generally corrupted output. I my context I'm trying to avoid this by letting know the users that they should not edit same questions. The idea is that different users edit different pages.
The concept may sound confusing, but it makes sense filling very huge surveys and / or if they need to be filled quickly. Allowing several users to edit the survey certainly helps in this matter.
These are the issues I've found in my initial implementation:
Example concurrent survey
There are 2 users.
The survey contains 2 pages: 1st contains 5 questions and 2nd contains 8 questions.
User Nº1 fills 1st page
User Nº2 fills 2nd page
Results are saved in the DB on pressing button or switching pages.
User 1 enters the survey and fills out 2 out of 5 questions on page 1
User 2 enters afterwards, retrieves 2 already answered questions on the page 1 and fills out 3 questions on page 2
here is where the issue appears -
At this point whatever change will be made by user 1 it will overwrite the whole survey producing an inconsistent result because he is unaware of changes made by user 2.
Also if the user 2 saves his own results, the changes made by user 1 will be overwritten.
I was trying to synchronize the answers to save between users and they keept overlapping. The way I see it there are 2 possible solutions:

Solution 1  -  save only the questions you have answered. Use survey.onMatrixCellValueChanged to generate a JSON of questions you have changed (instead of using model.data). When it comes to saving you've got to use $.extend(savedSurvey, myCurrentSurvey); to merge the JSON obtained from the DB (savedSurvey, - answers from page 1) and your own answers (myCurrentSurvey).

Solution 2 - obtain the actual Diff of saved JSON (retrieved from DB) and your own JSON (your current status) and save it to the DB. The problem of this approach is that deep-diff may cause issues, There are projects such as https://github.com/flitbit/diff and https://github.com/benjamine/jsondiffpatch which allow you to get the descriptor of the difference between JSON objects, but not the diffed JSON itself.

Anyway, the issue seems to be able to distinguish between states of the survey at any given moment. The solution is to keep track of the changes you have made to partially answered survey. For example if you retrieved a survey with few questions already answered, the data you should save is the questions you have answered (or modified) yourself.
What's your thoughts on this ?
Thank you

@Kuhax Yes, it is sounds interesting. However, to be honest, I would like do not to work on it, since there are many other tasks on the list.
If I do it myself, I would it in reactive way. Get the notification on the client about changing happened on the server and show the changes/data immediately.
I would love to work on it, but unfortunately have to work on other, not so cool, but more requested functionality.
Thank you,
Andrew

@andrewtelnov I agree that this feature will not be widespread since it's scope is limited to certain scenarios, but certailnly it will be nice to see it implemented someday. However I just wanted to share my thoughts about this matter (hopefully it may interest other guys out there).
Meanwhile I'm going to try to tinker and make some research on my own. I'll let you know if some meaningful results are reached. And certainly I'll try to put together a demo showing (at least) what I'm aiming to achieve.
Thank you


BUG: pp field parameters conforming to UM convention for unrotated LAMs

UM requires LAM's which are not on a rotated pole to be described with bplat=90 bplon=180.
Iris will currently set bplon to 0.  The recent introduction of UM file metadata checking means that such incorrectly set bplon values will raise an error in the UM.
Our workaround is to override pp fields derived by iris:
https://code.metoffice.gov.uk/trac/ancil/browser/ants/branches/dev/carwynpelley/1169_IRIS_DITCHES_BPLAT_BPLON/lib/ants/fileformats/pp/__init__.py?rev=8607#L207
 207     # Overide bplon as iris doesn not support properly support unrotated pp
 208     # LAMs.  See https://github.com/SciTools/iris/issues/3560
*209     if not ants.utils.cube.is_global(cube):
 210         if x_coord.coord_system == ants.coord_systems.UM_SPHERE.crs:
 211             field.bplon = 180

It would be simple enough to apply a similar change to iris pp generation from cubes by overriding bplon as 180 if the provided field is a LAM with unrotated pole crs.
Background

The convention is that unrotated lams have 180 pole longitude. This way it matches the dumps and matches F03. This is related to the way the UM dump code performs the pole rotation as well as calculating any longitudinal offset of where to place the zero meridian. - Joe Mancell

Internal issue (ANTS workaround): ancil/ticket #1169
Internal issue (F03 update): um/ticket #5305

Happy to look at doing this myself.  However I think this needs some thought as to how exactly this should be handled in iris:
I think the GeogCS should be made to handle and record bplat and bplon of 90 and 180 respectively.  This way iris knows it's unrotated and we can retain UM convention at the same time on save.  I'll have a play with this idea and see what impact it has/how significant a change it is.  I'll then post an update to the ticket with my findings.

Both 'cases' are remedied by altering iris pp save behaviour so that it respects UM convention for unrotated LAMs.  For example we workaround current iris behaviour here.

This should be behind a future flag.