SHIR unable to reconnect to Synapse after forced restart

Problem: when container terminates non-gracefully it is unable to connect to synapse during restart
Background: I have setup the container as suggested, with below alterations

FROM: servercore:ltsc2022
Additionally installed

Denodo ODBC
Oracle Instant Client Basic Lite
VS 2017 redistributable (required for Oracle Instant Client / ODBC)
Oracle ODBC
Oracle Instant Client sqlplus tool
Generated a few DSNs from above
added server certificate

It is running fine on an AKS cluster and the deployment is controlled using ArgoCd.
When I (or AKS backend) terminates/deletes the pod is restarted by ArgoCd. This would end up in an error  "Registration of new node is forbidden when Remote Access is disabled on another node. To enable it, you can login the machine where the other node is installed and run 'dmgcmd.exe -EnableRemoteAccess "" [""]'."
As a work-around I am able to delete the node in synapse and then restart the pod. With these steps it is able to re-connect .
How can I get around this problem

Which environment variable do you set when starting container?

Hi, This is an extract from the deployment yaml ,
`
Container Environment variables:
    env:
    - name: AUTH_KEY
      valueFrom:
        secretKeyRef:
          key: SECRET_AUTH_KEY_1
          name: app-secrets
    - name: NODE_NAME # name as registered in synapse
      value: "t-nx-mirage-synapse-shir"
    - name: ENABLE_HA # The flag to enable high availability and scalability. It supports up to 4 nodes registered to the same IR when HA is enabled, otherwise only 1 is allowed.
      value: "false"  # default is false
    - name: HA_PORT   # The port to set up a high availability cluster.
      value: "8060"   # default is 8060
    - name: ENABLE_AE # The flag to enable offline nodes auto-expiration. If enabled, the expired nodes will be removed automatically from the IR when a new node is attempting to register.
                      # Only works when ENABLE_HA=true.
      value: "false"  # default is false
    - name: AE_TIME   # The expiration timeout duration for offline nodes in seconds. Should be no less than 600 (10 minutes).
      value: "600"    # Least time = 10 minutes = 600 seconds

`

Hi, This is an extract from the deployment yaml ,
`
Container Environment variables:
    env:
    - name: AUTH_KEY
      valueFrom:
        secretKeyRef:
          key: SECRET_AUTH_KEY_1
          name: app-secrets
    - name: NODE_NAME # name as registered in synapse
      value: "t-nx-mirage-synapse-shir"
    - name: ENABLE_HA # The flag to enable high availability and scalability. It supports up to 4 nodes registered to the same IR when HA is enabled, otherwise only 1 is allowed.
      value: "false"  # default is false
    - name: HA_PORT   # The port to set up a high availability cluster.
      value: "8060"   # default is 8060
    - name: ENABLE_AE # The flag to enable offline nodes auto-expiration. If enabled, the expired nodes will be removed automatically from the IR when a new node is attempting to register.
                      # Only works when ENABLE_HA=true.
      value: "false"  # default is false
    - name: AE_TIME   # The expiration timeout duration for offline nodes in seconds. Should be no less than 600 (10 minutes).
      value: "600"    # Least time = 10 minutes = 600 seconds

`

Hi @Mats-Elfving
When the container crashed, the former node was not detached automatically and resulted in the problem.
Please just turn on the flags ENABLE_HA and ENABLE_AE to true. This will let your integration runtime permit registering the restarted container and remove the former node automatically after the time specified by AE_TIME (default is 10 minutes).

Reading the comment on the same, I realize that you are of course right. Would this (HA_PORT) also allow me to deploy two (or more) pods (with different node-names)? How is the HA_PORT used? Is it an inter-pod communication port? Or a port that should be open for communications from out-of-cluster? or only within service?.

Reading the comment on the same, I realize that you are of course right. Would this (HA_PORT) also allow me to deploy two (or more) pods (with different node-names)? How is the HA_PORT used? Is it an inter-pod communication port? Or a port that should be open for communications from out-of-cluster? or only within service?.

sure, HA_PORT is originally designed for deploy multi-nodes.
It is used only among the nodes in the same cluster and in your scenario, it is just an inter-pod port.

Thank you for the help setting this up. I ended up using the below settings. This would ensure a name that is relevant and at the time unique.
`# Container Environment variables:
env:
- name: AUTH_KEY
valueFrom:
secretKeyRef:
key: SECRET_AUTH_KEY_1
name: app-secrets
- name: NODE_NAME # name as registered in synapse
valueFrom:
fieldRef:
fieldPath: metadata.name
value: "t-nx-mirage-synapse-shir"
    - name: ENABLE_HA # The flag to enable high availability and scalability. It supports up to 4 nodes registered to the same IR when HA is enabled, otherwise only 1 is allowed.
      value: "true"  # default is false
    - name: HA_PORT   # The port to set up a high availability cluster.
      value: "8060"   # default is 8060
    - name: ENABLE_AE # The flag to enable offline nodes auto-expiration. If enabled, the expired nodes will be removed automatically from the IR when a new node is attempting to register.
                      # Only works when ENABLE_HA=true.
      value: "true"  # default is false
    - name: AE_TIME   # The expiration timeout duration for offline nodes in seconds. Should be no less than 600 (10 minutes).
      value: "600"    # Least time = 10 minutes = 600 seconds
    - name: ORACLE_HOME
      value: "C:\\Oracle\\instantclient_21_11"
    - name: TNS_ADMIN
      value: "C:\\Oracle\\instantclient_21_11\\network\\admin"

`

closing this ! :)


Runing RedPajama get out of memory error

I run this command:
(mlc-chat) eddie@eddie-XPS-15-9560:~/workspace/mlc$ mlc_chat_cli --local-id RedPajama-INCITE-Chat-3B-v1-q4f16_0
Use MLC config: "dist/prebuilt/mlc-chat-RedPajama-INCITE-Chat-3B-v1-q4f16_0/mlc-chat-config.json"
Use model weights: "dist/prebuilt/mlc-chat-RedPajama-INCITE-Chat-3B-v1-q4f16_0/ndarray-cache.json"
Use model library: "dist/prebuilt/lib/RedPajama-INCITE-Chat-3B-v1-q4f16_0-vulkan.so"
Loading model...
You can use the following special commands:
/help               print the special commands
/exit               quit the cli
/stats              print out the latest stats (token/sec)
/reset              restart a fresh chat
/reload [local_id]  reload model local_id from disk, or reload the current model if local_id is not specified
I get a prompt and enter text:
: Write a poem for San Francisco
Then I get an error:
[10:18:16] /home/runner/work/package/package/tvm/src/runtime/relax_vm/pooled_allocator.h:64: Warning: PooledAllocator got InternalError during allocation:

An error occurred during the execution of TVM.
For more information, please see: https://tvm.apache.org/docs/errors.html

Check failed: (__e == VK_SUCCESS) is false: Vulkan Error, code=-2: VK_ERROR_OUT_OF_DEVICE_MEMORY
[10:18:16] /home/runner/work/package/package/tvm/src/runtime/relax_vm/pooled_allocator.h:65: Warning: Trying to release all unused memory and reallocate...
terminate called after throwing an instance of 'tvm::runtime::InternalError'
what():  [10:18:16] /home/runner/work/package/package/tvm/include/tvm/runtime/device_api.h:291: unknown type =0
Stack trace:
[bt] (0) /home/eddie/miniconda3/envs/mlc-chat/bin/../lib/libtvm_runtime.so(tvm::runtime::Backtraceabi:cxx11+0x27) [0x7f19af02e0c7]
[bt] (1) /home/eddie/miniconda3/envs/mlc-chat/bin/../lib/libtvm_runtime.so(+0x65a7a) [0x7f19aeff1a7a]
[bt] (2) /home/eddie/miniconda3/envs/mlc-chat/bin/../lib/libtvm_runtime.so(+0x4e809) [0x7f19aefda809]
[bt] (3) /home/eddie/miniconda3/envs/mlc-chat/bin/../lib/libtvm_runtime.so(+0xee9d4) [0x7f19af07a9d4]
[bt] (4) /home/eddie/miniconda3/envs/mlc-chat/bin/../lib/libtvm_runtime.so(+0x4c4de) [0x7f19aefd84de]
[bt] (5) /home/eddie/miniconda3/envs/mlc-chat/bin/../lib/libtvm_runtime.so(tvm::runtime::PackedFuncObj::Extractor<tvm::runtime::PackedFuncSubObj<tvm::runtime::TypedPackedFunc<tvm::runtime::relax_vm::Storage (void*, tvm::runtime::ShapeTuple, long, DLDataType)>::AssignTypedLambda<tvm::runtime::relax_vm::Storage ()(void, tvm::runtime::ShapeTuple, long, DLDataType)>(tvm::runtime::relax_vm::Storage ()(void, tvm::runtime::ShapeTuple, long, DLDataType), std::__cxx11::basic_string<char, std::char_traits, std::allocator >)::{lambda(tvm::runtime::TVMArgs const&, tvm::runtime::TVMRetValue*)#1}> >::Call(tvm::runtime::PackedFuncObj const*, tvm::runtime::TVMArgs, tvm::runtime::TVMRetValue*)+0x25e) [0x7f19af08c58e]
[bt] (6) /home/eddie/miniconda3/envs/mlc-chat/bin/../lib/libtvm_runtime.so(tvm::runtime::relax_vm::VirtualMachineImpl::RunInstrCall(tvm::runtime::relax_vm::VMFrame*, tvm::runtime::relax_vm::Instruction)+0xa11) [0x7f19af0c06d1]
[bt] (7) /home/eddie/miniconda3/envs/mlc-chat/bin/../lib/libtvm_runtime.so(tvm::runtime::relax_vm::VirtualMachineImpl::RunLoop()+0x2e7) [0x7f19af0bda87]
[bt] (8) /home/eddie/miniconda3/envs/mlc-chat/bin/../lib/libtvm_runtime.so(tvm::runtime::relax_vm::VirtualMachineImpl::InvokeBytecode(long, std::vector<tvm::runtime::TVMRetValue, std::allocatortvm::runtime::TVMRetValue > const&)+0x246) [0x7f19af0be096]
Aborted (core dumped)
I'm running Linux Mint 21.2 with this GPU:
(from Vulkaninfo):
GPU1:
VkPhysicalDeviceProperties:
apiVersion        = 4206816 (1.3.224)
driverVersion     =<PHONE_NUMBER> (0x835a4440)
vendorID          = 0x10de
deviceID          = 0x1c8d
deviceType        = PHYSICAL_DEVICE_TYPE_DISCRETE_GPU
deviceName        = NVIDIA GeForce GTX 1050
pipelineCacheUUID = dcbcd2de-e45b-e401-58e7-40a8bbb24597

VkPhysicalDeviceLimits:
maxImageDimension1D                             = 32768
maxImageDimension2D                             = 32768
maxImageDimension3D                             = 16384
maxImageDimensionCube                           = 32768
maxImageArrayLayers                             = 2048
maxTexelBufferElements                          = 134217728
maxUniformBufferRange                           = 65536
maxStorageBufferRange                           = 429nvii4967295
maxPushConstantsSize                            = 256
maxMemoryAllocationCount                        =<PHONE_NUMBER>

nvidia-smi yields this output:
mlc-chat) eddie@eddie-XPS-15-9560:~/workspace/mlc$ nvidia-smi
Mon May 29 10:46:30 2023
+-----------------------------------------------------------------------------+
| NVIDIA-SMI 525.105.17   Driver Version: 525.105.17   CUDA Version: 12.0     |
|-------------------------------+----------------------+----------------------+
| GPU  Name        Persistence-M| Bus-Id        Disp.A | Volatile Uncorr. ECC |
| Fan  Temp  Perf  Pwr:Usage/Cap|         Memory-Usage | GPU-Util  Compute M. |
|                               |                      |               MIG M. |
|===============================+======================+======================|
|   0  NVIDIA GeForce ...  Off  | 00000000:01:00.0 Off |                  N/A |
| N/A   45C    P3    N/A /  N/A |   1113MiB /  4096MiB |      0%      Default |
|                               |                      |                  N/A |
+-------------------------------+----------------------+----------------------+
+-----------------------------------------------------------------------------+
| Processes:                                                                  |
|  GPU   GI   CI        PID   Type   Process name                  GPU Memory |
|        ID   ID                                                   Usage      |
|=============================================================================|
|    0   N/A  N/A       987      G   /usr/lib/xorg/Xorg                842MiB |
|    0   N/A  N/A      1674      G   cinnamon                           33MiB |
|    0   N/A  N/A      2112      G   /usr/lib/firefox/firefox          235MiB |
+-----------------------------------------------------------------------------+
Maybe the CUDA version reference means that the Vulkan drivers are not being used?
Any help appreciated.
Thanks,
Eddie

The GPU memory of GTX 1050 (4GB) might be too small to run RedPajama inference, especially when your graphics environment takes 1GB of GPU memory.
One suggestion is to disable x-server when you run mlc_chat_cli, by running the following command (I assume you are using GDM, another display manager such as LightDM should work similarly):
sudo systemctl stop gdm

After that, you can ctrl + alt + f2 to enter another tty, and if you run nvidia-smi in this case, the GPU Memory Usage should be 1MiB/4096MiB, and you can try running mlc_chat_cli again and see if you will still encounter the OOM issue.
After you have fun with MLC-LLM, you can restart your x-server by:
sudo systemctl start gdm

Thank you @yzh119, that worked great!
I did:
sudo systemctl stop lightdm then ctrl + alt + f4 ran mlc_chat_cli and the MLC-LLM wrote me a nice poem about San Frnacisco.
I typed 'ctrl + alt + ff7` to exit text mode. Thank you for all this work!


Incognito mode doesn't use the incognito keyboard

Steps to reproduce

Turn on incognito mode
Click on any text field

Expected behavior
Keyboard should be in incognito mode
Actual behavior
Keyboard is in general mode and saves typing history
Crash logs
No response
Mihon version
App version: 0.16.3-6499 (standard, 139663acf, 4, 2024-01-29T20:34Z) Android version: 14 (SDK 34; build UQ1A.240105.004) Device brand: google Device manufacturer: Google Device name: panther (panther) Device model: Pixel 7 WebView: Android System WebView 122.0.6261.5
Android version
Android 14
Device
Pixel 7
Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] I have gone through the FAQ and troubleshooting guide.
[X] I have updated the app to version 0.16.3.
[X] I have updated all installed extensions.
[X] I will fill out all of the requested information in this form.

These too maybe but apparently its might be a compose issue
Discord
https://github.com/mihonapp/mihon/blob/a3dfd2efe6ace7a2a4d79bd09fb1a729989f1094/app/src/main/java/eu/kanade/tachiyomi/widget/TachiyomiTextInputEditText.kt#L21

There's also this possible solution
https://issuetracker.google.com/issues/359257538


Please review annotation of 'll' as 'ʒ' in Imbabura Quechua.

My Quechua dictionary (not necessarily correct for Imbabura Quechua),  indicates that 'll' is a voiced lateral palatal fricative.  Which doesn't have a symbol on my IPA chart, but next  to 'j'. This would make it similar to the Spanish pronunciation of 'll'.

We have lateral release and friction as modifying features in clts.
>>> from pyclts import CLTS
>>> bipa = CLTS().bipa
>>> bipa["with-friction voiced palatal lateral approximant consonant"].s
'ʎ͓'
>>> bipa["with-lateral-release voiced palatal fricative consonant"].s
'ʝˡ'

Either variant would be fine with me. If you want to modify this in Quechua, this would be fine with me!

On the other hand: 'ʒ' is very typical for the Spanish of Mendoza and the region. So it is not unnormal for variants of Spanish or other regions to acquire this sound for ll from Spanish, which is an intermediate stage of the extreme variant of unvoiced 'ʒ' in Buenos Aires.

Ok. Best action seems to leave it as us. It just surprised me. And matching ‘l’ in the Aymara was more costly, but such is life! Thanks.
J.E.M.

On Apr 17, 2023, at 11:44 PM, Johann-Mattis List @.***> wrote:

On the other hand: 'ʒ' is very typical for the Spanish of Mendoza and the region. So it is not unnormal for variants of Spanish or other regions to acquire this sound for ll from Spanish, which is an intermediate stage of the extreme variant of unvoiced 'ʒ' in Buenos Aires.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.


Organize crates into folders

What

Closes https://github.com/rerun-io/rerun/issues/5888

This organizes the crates into five folders:

crates/build: build tools
crates/top: top-level crates (re_sdk, rerun, rerun_c, rerun-cli)
crates/viewer: everything visual and UI
crates/store: how data is stored, transmitted, indexed, plus type definitions
crates/utils: bottom-level crates, perhaps useful to others

This is a very rough split, and better ones are certainly possible, but I think this is at least a good start.
Future work: lint on wether or not crates in one folder may depend on crates in another.
 crates
 ├─ build
 │  ├─ re_build_info
 │  ├─ re_build_tools
 │  ├─ re_dev_tools
 │  └─ re_types_builder
 ├─ store
 │  ├─ re_chunk
 │  ├─ re_chunk_store
 │  ├─ re_data_loader
 │  ├─ re_data_source
 │  ├─ re_entity_db
 │  ├─ re_format_arrow
 │  ├─ re_log_encoding
 │  ├─ re_log_types
 │  ├─ re_query
 │  ├─ re_sdk_comms
 │  ├─ re_types
 │  ├─ re_types_blueprint
 │  ├─ re_types_core
 │  └─ re_ws_comms
 ├─ top
 │  ├─ re_sdk
 │  ├─ rerun
 │  ├─ rerun-cli
 │  └─ rerun_c
 ├─ utils
 │  ├─ re_analytics
 │  ├─ re_case
 │  ├─ re_crash_handler
 │  ├─ re_error
 │  ├─ re_format
 │  ├─ re_int_histogram
 │  ├─ re_log
 │  ├─ re_memory
 │  ├─ re_smart_channel
 │  ├─ re_string_interner
 │  ├─ re_tracing
 │  └─ re_tuid
 └─ viewer
    ├─ re_blueprint_tree
    ├─ re_context_menu
    ├─ re_data_ui
    ├─ re_edit_ui
    ├─ re_renderer
    ├─ re_renderer_examples
    ├─ re_selection_panel
    ├─ re_space_view
    ├─ re_space_view_bar_chart
    ├─ re_space_view_dataframe
    ├─ re_space_view_spatial
    ├─ re_space_view_tensor
    ├─ re_space_view_text_document
    ├─ re_space_view_text_log
    ├─ re_space_view_time_series
    ├─ re_time_panel
    ├─ re_ui
    ├─ re_viewer
    ├─ re_viewer_context
    ├─ re_viewport
    ├─ re_viewport_blueprint
    └─ re_web_viewer_server

Checklist

[x] I have read and agree to Contributor Guide and the Code of Conduct
[x] I've included a screenshot or gif (if applicable)
[ ] I have tested the web demo (if applicable):

Using examples from latest main build: rerun.io/viewer
Using full set of examples from nightly build: rerun.io/viewer

[x] The PR title and labels are set such as to maximize their usefulness for the next release's CHANGELOG
[x] If applicable, add a new check to the release checklist!

PR Build Summary
Recent benchmark results
Wasm size tracking

To run all checks from main, comment on the PR with @rerun-bot full-check.

@rerun-bot full-check

@rerun-bot full-check

@rerun-bot full-check

check if someone has something big in flight that will be harder to merge/rebase than this

Rebasing on moved files is quite painless - I know, I did it three times while working on this PR :)


editor not updated when resource in multi-resource file is updated externally

Steps to reproduce

open a folder containing a multi-resource file
select a resource in the multi-resource file in the resource navigator so that file is shown in the source editor
make a change to the resource in the multi-resource file using an external tool (for example change its name)
monokle will detect the change and update the navigator with the new object (if you changed the name that will show), but the editor will continue to show the old resource

Monokle should either update the editor to show the new resource - or deselect the resource and clear the editor

note: it works fine for single-resource files


Just raise event with the table PK - with no other data.

Hi There,
I'm following your examples and have tried looking though the source code for some answers, but I don't seem to be able to receive an event with just the ID of the target Table.
If I comment out the EXCEPT statement in the trigger created I can get my desired results.

Is there a way to do this programmatically?
My on create settings are borrowed from the console example

Hi @Phiph,
it is not possible to achieve this programmatically. You can try to customize the trigger generation by overriding the corresponding SqlTableDependencyProvider.CreateSqlTableDependency function in the following way:
  abstract class CustomSqlTableDependencyProvider<TEntity> : SqlTableDependencyProvider<TEntity>
    where TEntity : DomainEntity, new()
  {
    private readonly string connectionString;
    private readonly LifetimeScope lifetimeScope;

    internal CustomSqlTableDependencyProvider(string connectionString, IScheduler scheduler, LifetimeScope lifetimeScope = LifetimeScope.UniqueScope)
      : base(connectionString, scheduler, lifetimeScope)
    {
      this.connectionString = connectionString;
      this.lifetimeScope = lifetimeScope;
    }

    SqlTableDependencySettings<TEntity> sqlTableDependencySettings;

    protected override SqlTableDependencySettings<TEntity> OnCreateSettings()
    {
      sqlTableDependencySettings ??= new SqlTableDependencySettings<TEntity>();

      return sqlTableDependencySettings;
    }

    protected override ITableDependency<TEntity> CreateSqlTableDependency(IModelToTableMapper<TEntity> modelToTableMapper)
    {
      if (lifetimeScope != LifetimeScope.UniqueScope)
        return base.CreateSqlTableDependency(modelToTableMapper);

      OnCreateSettings();

      return new CustomSqlTableDependencyWithUniqueScope<TEntity>(connectionString, TableName,
        schemaName: sqlTableDependencySettings.SchemaName, mapper: modelToTableMapper, updateOf: sqlTableDependencySettings.UpdateOf,
        filter: sqlTableDependencySettings.Filter, notifyOn: sqlTableDependencySettings.NotifyOn,
        executeUserPermissionCheck: sqlTableDependencySettings.ExecuteUserPermissionCheck,
        includeOldValues: sqlTableDependencySettings.IncludeOldValues);
    }
  }

and then override PrepareInsertIntoModifiedRecordsTableStatement:
  public class CustomSqlTableDependencyWithUniqueScope<TEntity> : SqlTableDependencyWithReconnection<TEntity>
    where TEntity : class, new()
  {
    #region Constructors

    public CustomSqlTableDependencyWithUniqueScope(string connectionString, string tableName = null, string schemaName = null, IModelToTableMapper<TEntity> mapper = null, IUpdateOfModel<TEntity> updateOf = null, ITableDependencyFilter filter = null, DmlTriggerType notifyOn = DmlTriggerType.All, bool executeUserPermissionCheck = true, bool includeOldValues = false)
      : base(connectionString, tableName, schemaName, mapper, updateOf, filter, notifyOn, executeUserPermissionCheck,
        includeOldValues)
    {
    }

    #endregion

    #region LifetimeScope

    public override LifetimeScope LifetimeScope { get; } = LifetimeScope.UniqueScope;

    #endregion

    protected override string PrepareInsertIntoModifiedRecordsTableStatement(
      IReadOnlyCollection<TableColumnInfo> interestedColumns)
    {
      return base.PrepareInsertIntoModifiedRecordsTableStatement(interestedColumns); //override this
    }
  }

Regards Tomas

Hi Tomas,
Thank you very much for taking the time on producing an example. Really helpful!

Hi, I'm glad that it helped you).


Multiple definition of raygui functions

Related to #49 I think, it's basically the same problem but with raygui.
Issue
Using raygui causes multiple definition errors for symbols defined in raygui headers.
Steps to reproduce
Clone https://github.com/the-argus/hampster-game at commit af08b1f61a02b89bf12d19aca6e2dca52bf0c9e7 and run nimble build -d:nimraylib_now_shared --threads=on (I used the shared lib since I'm on nixOS).
Alternatively, if you have nix installed, just enter the directory and run nix run.
Error log
I'm not going to paste the whole thing, but its just this over and over for all the raygui functions:
Output: /nix/store/lz1bwpdvlywij5ir0fmncgqa83dlpwhn-binutils-2.39/bin/ld<EMAIL_ADDRESS>in function `GuiEnable':
        ... @mhampster_game.nim.c:(.text+0x0): multiple definition of `GuiEnable'; /home/argus/.cache/nim/hampster_game_d/@mui.nim.c.o:@mui.nim.c:(.text+0x0): first defined here
        ... /nix/store/lz1bwpdvlywij5ir0fmncgqa83dlpwhn-binutils-2.39/bin/ld<EMAIL_ADDRESS>in function `GuiDisable':
        ... @mhampster_game.nim.c:(.text+0x11): multiple definition of `GuiDisable'; /home/argus/.cache/nim/hampster_game_d/@mui.nim.c.o:@mui.nim.c:(.text+0x11): first defined here
        ... /nix/store/lz1bwpdvlywij5ir0fmncgqa83dlpwhn-binutils-2.39/bin/ld<EMAIL_ADDRESS>in function `GuiLock':
        ... @mhampster_game.nim.c:(.text+0x22): multiple definition of `GuiLock'; /home/argus/.cache/nim/hampster_game_d/@mui.nim.c.o:@mui.nim.c:(.text+0x22): first defined here

I guess I will have to prioritize the re-write to a single C file. This issue seems to be too ubiquitous. Thank you for this bug report!


cannot install azure functions

Does this occur consistently?
Repro steps:

Action: azureFunctions.installOrUpdateFuncCoreTools
Error type: Error
Error Message: Failed to run "npm" command. Check output window for more details.
Version: 0.24.0
OS: win32
OS Release: 10.0.18362
Product: Visual Studio Code
Product Version: 1.48.2
Language: en

Call Stack
Object.<anonymous> extension.bundle.js:33:51462
fulfilled extension.bundle.js:33:50345
processTicksAndRejections task_queues.js:85:5

@majo1313 there should be more logs in the output window (which should automatically become visible when this error occurs). If you still need help after looking at those, please copy the logs here and add repro steps


roon-server: revamp

Motivation for this change
This builds on https://github.com/NixOS/nixpkgs/pull/92945 by completely revamping the roon-server derivation, and in the process fixing numerous issues with it.
With these changes I now have a fully functioning Roon on NixOS setup for the first time!
cc. @eljojo
cc. @flokli @andir
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

The zlib hack from #92945 isn't required anymore, right?

As far as I understand this is taken care of by the patchelf hook — that said I must say I am not a user of roon myself, so couldn't confirm with 100% certainty.

Hi everyone, I'm glad that the roon-server package is getting more attention.
I have to admit it makes me feel a bit sad that this PR was merged before mine, I worked really hard on it and was hoping it'd get merged.
With that being said, would someone be able to explain to me:

how this goes about solving the zlib issue?

I went through the diff but still can't understand how this fixes the issue
I am not doubting that this does indeed fix it, I just want to improve my understanding of nix

any guidance on how to run this on my local NixOS?

it seems superior than what I already have running, but I am not sure how to point my local NixOS to the "master branch" version of this roon-server package.

Thanks for your help and doing this work

any guidance on how to run this on my local NixOS?

There are various ways, e.g. use parameter -I nixpkgs=/path (accepted by nixos-rebuild, nix-* and even new nix), where /path can even be like https://github.com/nixos/nixpkgs/archive/master.tar.gz

@vcunat It's being handled by the autoPatchelfHook.
@eljojo

how this goes about solving the zlib issue?

The original Nix code was a bit "traditional" in that it manually tried to patchelf binaries, and so missed patchelf-ing zlib into the mono runtime. My changes uses the autoPatchelfHook as opposed to manually calling patchelf. What this effectively does is scan all ELF binaries for libraries and automatically patchelf the correct rpaths in. Thus not only the zlib issue you had is fixed, but also the alsalib issue I had, and any other new dynlinked dependencies Roon might add in the future.

any guidance on how to run this on my local NixOS?

You can add it in an overlay, but i think you'd benefit from going to #nixos on freenode for more interactive help on how to set those things up

👍 thanks for the context this is super useful!


Print stylesheet

Printing things like index tables and show views is a pretty common use case. I created a fairly basic print stylesheet that handles basic ActiveAdmin UI concepts and creates pretty printed output for them.
It's really lightweight at the moment and doesn't handle everything gracefully, but I think it's a good starting point for later development, and handles common uses and data.

To clarify, I know it's possible to add custom stylesheets (including print, if you set the media type).
But I think it's useful to provide useful defaults on the print side, just like on the screen side.
Would love any/all feedback on both usefulness and implementation.

Well done, looks great man! I've thought this was necessary for quite some time just never got around to it.
Two things before I merge this:

Right now our main stylesheet's media type is "all" and this clobbers any other stylesheet types such as this one (at least it did for me) so let's change that to "screen"
Could you maybe add some CSS to hide the .table_tools div, it shows up for me as a UL when I try printing

Other than that great job, can't wait to get this merged!

Awesome! :)

Good catch on the media type; had that working before a recent rebase, but should have done more testing there.
Instead of totally hiding .table_tools, I set it so it shows you your current scope if you have one, which is nice info to have:


Broken image

I set my pet to a grey cat and it showed up as a broken image, and now even though I added a brown cat the broken image cat wont go away.

I just had the same issue. In the logs it was referring to the previous version of the extension.
Try reloading the window and seeing if that fixes the bug, otherwise I'll have to raise it with the vscode team

Same issue. I went to spawn a dog but before I could choose the color the command line closed and the broken image spawned.

Wouldn't be such an issue if I could de-spawn pets. That might be the simple "band-aid" solution.

Same issue. It's kind of annoying

Same issue here. I think I also set it to grey cat before it bugged out.
Reload & reinstalling doesn't work for me.

Fixed in 1.9.2. Cats and dogs can only be brown or black. The settings would let you type anything. Now it will default to brown.


Delete CustomDomain

Hello
I am playing around with running two Auth0 CustomDomains. After having created two, I don't seem to be able to unprotect, then delete both of them.
I need some help deleting them from our develop tenant.
Thanks

The error message you're getting indicates Pulumi is trying to create a CustomDomain that already exists in your account when you run pulumui up. If your stack doesn't contain important resources, simply try running pulumi destroy.
Also, could you please ping me on our community Slack? I may be easier to look into your issue rather that using a github issue.
Thanks.

Oh sure. Thanks for your help

Have moved away from this issue format as this isn't the best way to communicate about our problem


Disabled Date/Time Ranges ?

Hi I would like to ask can we have some disabled Date/Time Ranges feature ?

Do you mean in the calendar grid? or the date navigator?
if you could elaborate more plz

Assume you found solution.

Yes, sorry for late reply.
disabled in the calendar grid that user cannot click those specific date and time ranges

I havent found the solution yet.

Have you checked out this example sandbox in the Readme?
does it solve your issue?

@aldabil21 thanks
I am really appreciated for your help.
This is really what I want.


VinObdCommand get vin only once per session

Since the vin will never change on a vehicle, I think a improvement will be to only get the vin once at the start of a logging session. If this is currently the case I apologize for creating this.
This will bring down the overhead on polling.

i think this applies in general , for example a unsupported command in unlikely to suddenly become supported. so maybe if a command return same value x number of times don't request it again in that session ?  but that might not be a good idea for all commands

Yes that would be the ideal solution. There is a class that checks the supported PIDs, when a session is started it would be good to run this first and store the PID's with the vin, so next time it knows what can be polled and what can't.

or maybe move both the preference dialogue, i.e. before (only show available) or after(check selected) selecting the commands.  and for vin, since we already have a setting for vin there we could add option to get it from the car.

I will try to add the feature, I am craving for faster data

@Pho3niX90 you're rocking the place! Keep it up.


[hooks] Support during-install/upgrade hooks

Description
I'm wondering if there is a desire for during-install and during-upgrade hooks. The use case is for sure an interesting one, and if people have solved this another way, I'd be happy to hear how this was done.
Desired Outcome
As a result of what I mentioned above, I should be able to create a Job template like so:
apiVersion: batch/v1
kind: Job
metadata:
  name: "{{ .Release.Name }}"
  labels:
    app.kubernetes.io/managed-by: {{ .Release.Service | quote }}
    app.kubernetes.io/instance: {{ .Release.Name | quote }}
    app.kubernetes.io/version: {{ .Chart.AppVersion }}
    helm.sh/chart: "{{ .Chart.Name }}-{{ .Chart.Version }}"
  annotations:
    helm.sh/hook: during-install,during-upgrade
    helm.sh/hook-delete-policy: "before-hook-creation,hook-succeeded"

Motivation / Use Case
My company has a Helm chart which installs our product; essentially it's a parent chart, which is made up of many dependencies and child charts, which contain the actual logic.
One of those dependencies is Kafka, which many other components depend on. The components that depend on Kafka have an initContainer which essentially does a sleep command until all Kafka brokers are ready.
We then have a Job template in the parent chart that currently only runs during the initial installation. It's essentially a script that runs the equivalent kafka-topics.sh command to create topics; the script has some internal logic to determine things like replication factor, number of partitions, etc.
We now have a use case to not only run the script during installations, but now also during upgrades in case new Kafka topics should be created. The problem is that the current pre-install and post-install hooks will not work. This is why:

❌ For an installation, a pre-install hook will fail because the Kafka topic creation job depends on Kafka being already spun up.
❌ For an installation, a post-install hook will fail because the processes that need the Kafka topics to be present will never make it to a full Running state, and this hook will never be called.
✅ For an upgrade, a pre-upgrade hook would create the topic successfully. This is the only case that would work.
❌ For an upgrade, a post-upgrade hook will fail for the same reasons as a post-install hook: namely, the processes that depend on the new topic would never reach a Running state.

Potential Workarounds
There are several that I have found:

Use a Kafka Operator. This way, KafkaTopic CRDs can be configured as part of the deployment itself as a template. However, this is a bit heavier than simply including a Kafka chart like Bitnami's.
Use a Job template that always runs, without any Helm hooks. We tried this, but unless you're using the ttlSecondsAfterFinished feature (and thus, have enabled the feature gate), this doesn't work. During an upgrade, we find that if the job is in a Completed state, and hasn't expired, Kubernetes will not create a new Job to re-run.
Use initContainers to create the topics. While this could work, the problem is they will always re-run when the pod itself gets moved. While technically this works, it slows down a new deployment.

Output of helm version:
Helm v3:
version.BuildInfo{Version:"v3.1.1", GitCommit:"afe70585407b420d0097d07b21c47dc511525ac8", GitTreeState:"clean", GoVersion:"go1.13.8"}

Helm v2:
Client: &version.Version{SemVer:"v2.16.3", GitCommit:"1ee0254c86d4ed6887327dabed7aa7da29d7eb0d", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.16.3", GitCommit:"1ee0254c86d4ed6887327dabed7aa7da29d7eb0d", GitTreeState:"clean"}

Output of kubectl version:
Client Version: version.Info{Major:"1", Minor:"17", GitVersion:"v1.17.3", GitCommit:"06ad960bfd03b39c8310aaf92d1e7c12ce618213", GitTreeState:"clean", BuildDate:"2020-02-13T18:08:14Z", GoVersion:"go1.13.8", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"14+", GitVersion:"v1.14.9-eks-c0eccc", GitCommit:"c0eccca51d7500bb03b2f163dd8d534ffeb2f7a2", GitTreeState:"clean", BuildDate:"2019-12-22T23:14:11Z", GoVersion:"go1.12.12", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):  AWS EKS

@sc250024 interesting proposal. When during the install and upgrade process would you be wanting these hooks to fire? "during" isn't very specific. Is this after subcharts but before the manifests for your chart? Or, somewhere else?
I understand this is a difficult problem for deploying apps. This problem has come up in Kubernetes SIG Apps in the past and we didn't have a good answer back then.

@mattfarina Great question. If I look the Hook docs at section Hooks and the Release Lifecycle, I would modify it like so:
diff --git i/content/en/docs/topics/charts_hooks.md w/content/en/docs/topics/charts_hooks.md
index 6f41f69..b8ac6d9 100644
--- i/content/en/docs/topics/charts_hooks.md
+++ w/content/en/docs/topics/charts_hooks.md
@@ -24,10 +24,12 @@ The following hooks are defined:
 | Annotation Value | Description                                                                                |
 | ---------------- | ----------------------------------------------------------------------------------------------------- |
 | `pre-install`    | Executes after templates are rendered, but before any resources are created in Kubernetes             |
+| `during-install` | Executes while all resources are loaded into Kubernetes                                               |
 | `post-install`   | Executes after all resources are loaded into Kubernetes                                               |
 | `pre-delete`     | Executes on a deletion request before any resources are deleted from Kubernetes                       |
 | `post-delete`    | Executes on a deletion request after all of the release's resources have been deleted                 |
 | `pre-upgrade`    | Executes on an upgrade request after templates are rendered, but before any resources are updated     |
+| `during-upgrade` | Executes on an upgrade while all resources are being upgraded                                         |
 | `post-upgrade`   | Executes on an upgrade after all resources have been upgraded                                         |
 | `pre-rollback`   | Executes on a rollback request after templates are rendered, but before any resources are rolled back |
 | `post-rollback`  | Executes on a rollback request after all resources have been modified                                 |
@@ -63,9 +65,10 @@ lifecycle is altered like this:
 7. The library then loads the hook with the lowest weight first (negative to
    positive)
 8. The library waits until the hook is "Ready" (except for CRDs)
-9. The library loads the resulting resources into Kubernetes. Note that if the
-   `--wait` flag is set, the library will wait until all resources are in a
-   ready state and will not run the `post-install` hook until they are ready.
+9. The library loads the resulting resources into Kubernetes, and calls the
+   `during-install` hook. Note that if the `--wait` flag is set, the library
+   will wait until all resources are in a ready state and will not run the
+   `post-install` hook until they are ready.
 10. The library executes the `post-install` hook (loading hook resources)
 11. The library waits until the hook is "Ready"
 12. The library returns the release object (and other data) to the client

Essentially what I'm looking for is a way to manage the one-off Job templates that need to run during an installation, and all upgrades. The frustration with ttlSecondsAfterFinished is that it's a feature gate that has to be explicitly enabled for that cluster.

@sc250024 I'm still not exactly sure when you are asking for the hooks to run.

Executes while all resources are loaded into Kubernetes

Can you expand on this buy telling me what this happens after and before?

Hi, @sc250024 - thank you for your clearly-laid-out ideas. I'm closing this issue because we now have a recommended path forward for proposals: if you'd like to formally propose this idea, please file a Helm Improvement Proposal to discuss it with the community. Thanks!


New BlueZ version in latest OS causes features to break.

In Balena OS 2.71.3 (and possibly slightly earlier) Blue Z has been upgraded to 5.55 which introduces some breaking changes to how we were planning to use it.
It was updated here (https://github.com/balena-os/poky/commit/6fa6afd5329e9c4f80d1fc8a9365a6faacec0ed0).
Would it be possilbe to have it downgraded back to 5.53 for the NEBRA-HNT device?

I can't quite tell if it's correct, but it might be as simple as adding
SRC_URI_nebra-hnt[md5sum] = "e637feb2dbb7582bbbff1708367a847c"
SRC_URI_nebra-hnt[sha256sum] = "68cdab9e63e8832b130d5979dc8c96fdb087b31278f342874d992af3e56656dc"

to layers/meta-balena-raspberrypi/recipes-connectivity/bluez5/bluez5_%.bbappend?

Hi @ryanteck can you point to those breaking changes?

Hia @floion ,
It's in relation to when using BlueZ to provide a GATT BTLE Server, in 5.55 they introduced it where it provided some data which conflicted to when user's applications provide the data.
This has now been patched at https://github.com/bluez/bluez/issues/101 which shows it is an issue. However I'm not sure in which release this patch will be deployed.

Addressed by https://github.com/balena-os/balena-raspberrypi/pull/627
Feel free to re-open if necessary


New Devices

Per our discussion today, I think we should look in to getting new devices. Preferably a phone (cheaper) and one that has a good GPS and Verizon LTE compatibility.
The Moto E immediately comes to mind, and can be had brand new for $47.99 here: http://www.walmart.com/ip/Verizon-Moto-E-Prepaid-Smartphone/44052006
The Moto E is more than capable for our purposes and the price point is really attractive. The only issue is that Verizon has a policy that says you can't use prepaid devices on postpaid plans unless the phone has been active on a prepaid plan for longer than 6 months.
The loophole to this is that if you just ask Verizon for an activated sim card, they don't know what device you're going to use it in so they can't really enforce this.
I'm ready to pull the trigger and buy one of these puppies and rig it up so it powers on/off when it is unplugged, I just need @greenlinktransit to verify that they can get an activated LTE micro-sim card from Verizon for each of the trolleys.
Source: https://www.reddit.com/r/verizon/comments/36pprc/which_prepaid_phones_able_to_be_put_on_postpaid/
Our other option is to buy a cheap used Verizon post-paid phone. But I would really prefer the Moto E.

If we can install the devices as hidden and auto-on, it shouldn't need security updates since people won't be browsing the web on it.
One other thing if it's hidden - the GPS signal is much weaker than cellular signals, so it might not work acceptably if mounted under the foil of the roof panel or under a metal dash.
I'm good with either this or a tablet - this phone will certainly be easier to finance.

I'm gonna backtrack a bit - apparently that model of the Moto E is not rootable, Verizon has locked down the bootloader. I will need root to modify the phone to turn on when it is plugged in.
I will do more research on devices. In the meantime I would still like to know what the device activation process is like with your contract with Verizon. If the modems on the trolley already have micro sim cards, it could be as simple as swapping it over to our new device. Otherwise, we will need to get sim cards from them. They might want to have the device physically there to issue a new sim card too, due to their policy with using prepaid phones.
@bikeoid those are all good points, though we will want to keep auto updates on (for apps at least) for pushing new versions of our beacon app. Hopefully that layer of metallic foamy stuff lining the roof won't affect GPS too much but we'll have to do some testing with it.

It would be helpful if you guys gave me a specific list of questions for Verizon.  I could send them around internally, but I'm guessing that no one would have a clue.

For you guys:

How married are you to Verizon? Contract-wise and otherwise. They are pretty expensive, as yall have seen, and are very restrictive as to what devices they allow on their networks (and even what you can do with those devices).
Does the modem you have use a SIM card? Probably not because it seems to be a 3G device.

For verizon:

Is 4G LTE service included in your current contract?
If we have existing Verizon LTE devices (say we have them already but we would probably buy them off ebay), what is the process for activating them under your account? Can we just get some activated SIM cards?
What Android devices are available to purchase via Verizon and at what cost?

Do you get a subsidized contract price?
Up to how many devices?
If you have to buy them outright, what is the cheapest device?
Any refurbished options?

I'll forward these questions on the appropriate people and will let you know when I hear back.

Guys....I forwarded Adam's questions to our IT department (they control our Verizon contract) and here's their response...

Grant,
I was talking with Tristan yesterday and he will be working closely with you guys.  In answering some of the questions below, perhaps it will give us some options.  First, before I answer those, here was Tristan’s idea to diagnosis this issue.    He was going to take an existing Android phone that we have which has Verizon service.  He would like to install the tracker app on the phone and run the phone at the same time as running the tablet.  We are trying to pinpoint if the issue is with the modem versus the Verizon service.  You should be hearing from him today about this.
Our contract is the same with Verizon as it is with AT&T and Sprint.  All three are driven by the state contract.  I was not involved in the original setup so I am not sure why we are using machine to machine service for these tablets, however, I do know that we could get data enabled tablet from Verizon fairly inexpensive which is mandated by the state contract to have an unlimited data plan.
If Tristan’s test works and his phone proves to be more stable than the tablet going through a machine to machine modem I propose that we turn off all the services associated with these modems and order two data enabled tablets.  That would eliminate all the overhead associated with the connection now.

I think it would be easiest if someone sends Tristan a GitHub invitation so he can chime in on this thread.  His email address is<EMAIL_ADDRESS> He also just requested to be a Beta tester in the yeahthattrolley.com site.

Also, I have no idea if this is relevant at all but in working with some colleagues from other transit systems someone suggested that we look into Transitime (http://www.transitime.org/home.html) and see if we can use some of their concepts for our own system.  Apparently they won some hackathon award -- http://devpost.com/software/transitime-open-source-real-time-transit-information.

I'm happy to volunteer my old Nexus 5 again (we used it in the beginning for testing purposes, but it was decided that we'd use the tablets instead). It won't work on Verizon, however.
@greenlinktransit: It should be no problem adding Tristan to the organization; however, he must first sign up. Once he's signed up, let us know, and one of us can add him.

I sent him the yeahthattrolley.com link, so he should have already signed up (or will be very soon).

:+1: good addition to the conversation. I just would like to let the IT guys (Tristan?) know that we would like to move away from having a tablet on the dash at all and instead mount the phone in the overhead compartment where the router currently resides. To do this, we need a phone that I can root and dig in to the system partition so I can boot the phone up whenever it is "plugged in" (key in the ignition). Then we don't have to worry about drivers forgetting to turn the device on/off.
But other than that it sounds like we are on the same page here. Nexus 5 would be great, Moto E would also be great because of how cheap it is. If GreenLink already has access to AT&T and there is no legal/financial downside to switching service for the trolleys over to AT&T and purchasing a couple Moto E's, it would make my life a lot easier!
Please keep me posted on how the phone test goes. We were measuring ~500kbps up/down on the trolley so I have a feeling that a phone with a 4G connection is going to be a lot more consistent.
I will have to whitelist Tristan's email before he can download the beacon app (which is separate from the client), and we will have to work something out so we don't have his phone showing up as a "live trolley" on the map. @bikeoid what do you think? Should we have him point his phone at the old API?

@greenlinktransit Tristan should have just received a Beta invite for the public Android app. Like @dacohenii mentioned, if Tristan wants to be part of the GitHub org just have him create a GitHub account and let me know what that email is and I'll add him to the Code for Greenville org.

Re: testing - I'd agree that it is better for him to use the dev server at http://yeahthattrolley.azurewebsites.net for the Server IP on the beacon.   He can leave it on and use the DB Visualizer to confirm complete system operation.

@agautsc @dacohenii Tristan's GitHub username is tkenney-gvl and his email address is<EMAIL_ADDRESS>

He's been added :wave: @tkenney-gvl

I have another request -- could you please add Mike Blizzard from IT, as well?  His username is mblizzard-gvl

@mblizzard-gvl has been added. :wave:

Hey guys,
sorry it took me a while to get on, we were pretty busy here today. My initial thought when Grant approached us was that we could just keep the existing system and run a phone (since he had one that was just reclaimed - a Galaxy S4, Verizon) that we could use to test along side the existing setup to verify that it was a connection issue. I can definitely root it to make it usable for the auto-launch if that is the route the OP wants to take.
Thanks to everyone willing to donate hardware, however, the City will provide its own hardware and choose its own carrier primarily since we will be supporting this in the future.
For now, though, I'll get the S4 rooted per @ajhodges suggestion and get the admin tracker app installed, so we can test the connectivity issue.
Long term solution if the connectivity issue is resolved with the S4 would be to have two new dedicated mobile devices provided by the City.

Hey Tristan! Sorry for the confusion, I think you should go ahead and do your parallel test! Should be helpful in diagnosing the issue.
As for the S4, we could use a S4 no problem. The reason I wanted to nail down a long-term device ahead of time is that it will take some hackery to make the device boot up when it is plugged in, and because the technique I am going to use is device-specific, I'd rather not have to figure it out twice. So maybe we can just use the S4 to test the connectivity (so there's no need to root) and then you guys can choose whatever device you'd like - provided that the bootloader is unlockable.
Also I need your gmail (@tkenney-gvl) so I can whitelist it for the app.
Thanks!

Sounds great. I totally agree that we'd only need to do that custom hackery once (or a few times as device lifecycles happen). :) I'll email you from my my test gmail account so you can add it to the whitelist. Thanks!

I added you. Please make sure you go in the settings of the app and change the server URL from api.yeahthattrolley.com to yeahthattrolley.azurewebsites.net before enabling background collection! I think we need to send you the credentials to use too (username is hard coded). @bikeoid can you send those in an email to @tkenney-gvl? I can't remember them...

Cool, thanks!

Everyone,
Thanks for all the info and help. I just wanted to update everyone that I was able to get the agent loaded on the S4 this morning and I checked on the test tracking page and it shows up. Our next step will be to get it in the Trolley (probably Trolley1) and have it ride along, so we can do some testing and watch them side by side and see if the tablet drops and the S4 doesn't or if they both drop at the same time.
Also I wanted to let you know of a possible issue, where when I was transitioning between mobile data and Wifi and I happened to launch the consumer app on my LG G3 it kept crashing the app. I'm not sure if that's default behavior or because of the underlying android system calls that happen when the app is launched. Also when I turned off any mobile or wifi it kept crashing the app too. I'm wondering if we could maybe add a function to allow the app to still launch, and just do a quick check for connectivity and if not, pop up a redirect to the settings to enable data/location/wifi or something. Might be more headache with coding than what it's worth, but I  just thought I'd make a note here to let you all know. :)

It looks like the test beacon (Trolley 3 on the dev server) stayed running all weekend.   Let me know before you run the test on a real trolley;  especially if it's tested in the same location where it will be finally installed.   I'd like to record the path to confirm that the GPS isn't lost, causing it to fall back on wifi + cellular accuracy only.

@bikeoid I also saw that it was up pretty much all weekend. At this point I've heard back from the Fleet Services from the Trolley and we'll be getting them the device tomorrow for them to install in the Trolley (I'll find out which one tomorrow). Hopefully they'll get it installed before this weekend's Trolley use so we can watch them this weekend. Once I know which Trolley they'll be installing it on, we should be able to compare the route from the active trolley with the route on the test server and make sure that they're coinciding and then can also check for stability.

Hey Guys (and Gals),
The S4 is live and mounted in one of the trolleys. Since the fleet management doesn't use "Trolley 1" and "Trolley2", as they have other designations for them, I'll be looking at it over the lunch period when the trolleys are running today. I'll be able to tell probably pretty quickly which trolley it's on and I'll post it here as well. Thanks again.

:clap:

At this point I'm not seeing any trolleys running in the Android client Trolley Tracker app, but I'm seeing the positions of the one Trolley that has the S4 (from the test DB URL). It was pretty accurate as I watched it pass by City Hall and I was looking at it from the office, so I know at least that the tracking is working for the S4 - we'll just need to see how consistent it is.

This looks great!    When the S4 is on the trolley, it's fine to point the beacon to the real server.   Everything remains the same in the settings except for the "Server IP", which is set to api.yeahthattrolley.com .
I noticed that the S4 on the development server was moving so I watched it for part of lunch.    There were some GPS wobbles around the downtown buildings, but it is more than adequate for what we need to go live, as long as it runs consistently.

How is the S4 mounted right now, out of curiosity? Does the driver turn it on/off?
We've been using the last digit of the license plate to identify the trolleys right now, so we have 5 and 6. So you'll also need to take a look at that and change the ID in the app accordingly, and then delete the agent from the tablet. Then we should be good to go! We could use a different method of identifying the trolleys, that's just the only visual difference between the trolleys we could really find at the time.
Hopefully we see continue to see a higher level of consistency on the S4. I've been meaning to do some work on the agent app to try to improve reliability, I just haven't gotten around to it :(

FYI - I'm also mirroring Trolley 3 from the Dev server to the production server so that those who have signed up for the Trolley Tracker beta will have something to see and test with.

@ajhodges As far as I know it's mounted right beside the tablet on the dash. The drivers are doing the exact same thing with it as with the tablet (turning it on/off with the trolley power).
@bikeoid I'll be heading over there sometime today and will be updating the S4's tracker settings to go directly to the production server's address. I'll be leaving it as Trolley3, though, since we want to run it side-by-side with the real Trolley (5 or 6) to test for stability.
Thanks again for all your work and help! :)

I collected some good data from this weekend's run.  The first shows all tracks - the track accuracy was very good for our purposes.  This is all paths run over the entire route:

The single detour on Academy Street was a real path.  There was only a single 'shortcut' trace from Park to N Main, but that isn't a big problem.  Here is a closer view against city building satellite views:

Unless the new device will be mounted in a location with more metal shielding, we should not need any more testing.  Device 3 did not show up on Friday night, so the biggest problem may still be getting it started consistently.
If the mounting has been finalized, I'd recommend that we proceed with the device adaptation to automatically turn on when power is applied, and assuming that it can be attached to 'ignition power'.   We can run testing while modifying to confirm that it can start by itself many times in a row without failing.
The tablet was only online for a few minutes on Friday.

Super helpful data @bikeoid :clap: I might get that top image as a tattoo. (I'm not really getting that as a tattoo, but it would be some cool piece of art.)
I agree with switching over to phones. It seems like the tablet use is getting worse. If there are two phones that the city or Greenlink has and can use let's do it. If we need to have some type of fundraiser to buy root-able phones I bet we could get that done fairly quickly. Just let us know what we need to do.

That looks pretty accurate to me! Thanks for doing that visualization.
I think the 'ignition power' issue was mostly just that when we first
tested it, we left the key in the ignition and the power isn't cut to
accessories until the key is removed from the ignition. Assuming the keys
aren't left in the ignition, that should be more than suitable.
Unfortunately I've been doing more research in to Verizon devices and it
seems like Verizon is very particular about having devices with unlocked
bootloaders on their network, and so there are very few devices (if any?)
that have unlockable bootloaders. A cursory search reveals that the Nexus 6
and Moto X (2015) version are some of the only phones that are currently
able to have their bootloader unlocked (along with other 'developer
edition' phones).
If we are stuck with Verizon S4s, then the 'auto-on' feature might not be
possible as I'm going to need an unlocked bootloader to modify the charging
animation to trigger a boot. Some of the older Verizon S4 OS versions were
unlockable, but chances are these S4s have been updated and the exploits
have been patched.
On Mon, Nov 16, 2015 at 2:30 PM, bikeoid<EMAIL_ADDRESS>wrote:

I collected some good data from this weekend's run. The first shows all
tracks - the track accuracy was very good for our purposes. This is all
paths run over the entire route:
[image: t3path]
https://cloud.githubusercontent.com/assets/75929/11192113/2ba47cdc-8c6d-11e5-8d36-33f0c8a8ae05.jpg
The single detour on Academy Street was a real path. There was only a
single 'shortcut' trace from Park to N Main, but that isn't a big problem.
Here is a closer view against city building satellite views:
[image: t3pathwithsatellite]
https://cloud.githubusercontent.com/assets/75929/11192144/54ee433e-8c6d-11e5-8926-fd376feaa58b.jpg
Unless the new device will be mounted in a location with more metal
shielding, we should not need any more testing. Device 3 did not show up on
Friday night, so the biggest problem may still be getting it started
consistently.
If the mounting has been finalized, I'd recommend that we proceed with the
device adaptation to automatically turn on when power is applied, and
assuming that it can be attached to 'ignition power'. We can run testing
while modifying to confirm that it can start by itself many times in a row
without failing.
The tablet was only online for a few minutes on Friday.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/105#issuecomment-157144492
.

@tkenney-gvl: what are the plans for the weekend?    I think we could have good results if we replaced the tablets with a mobile device, unless final mounting needs to be tested.
Also, will both trolleys be running this weekend?

@bikeoid I'll check with Maintenance and OPS on the trolley schedule for this weekend.

@bikeoid Per OPS....we're still waiting for one of the trolleys to get back from the body shop.  Apparently it's supposed to be back today, but I heard the same story a couple weeks ago. I'll give you an update tomorrow.

Nice visualization @bikeoid! As far as I know, the City will plan on providing the final equipment (the S4 was just for testing), so we'll do some research and make sure we get some devices with unlockable bootloaders for the final mounting.
I tried getting the S4 on the production server the other day, but the data Mike Nice gave me to plug in showed "Unauthorized" in the main window on the tracker agent. I'll email him to get the complete info for when we get the new phones. Thanks!

FYI -- we got the 2nd trolley back last night from the body shop and it broke down on its first loop.  Back to the shop it goes....

They are being bought up fairly quickly, but there are still some Nexus 5's (last years model not the 5X) that are being sold online for around $200 each. I'll get @ajhodges to confirm, but I think those would work for all our needs.

Unfortunately I just looked it up and the Nexus 5 won't work on Verizon,
but the 5X will.
On Fri, Nov 20, 2015 at 10:03 AM, Adam Gautsch<EMAIL_ADDRESS>wrote:

They are being bought up fairly quickly, but there are still some Nexus
5's (last years model not the 5X) that are being sold online for around
$200 each. I'll get @ajhodges https://github.com/ajhodges to confirm,
but I think those would work for all our needs.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/105#issuecomment-158424954
.

Hi All,
I've been sitting tight and keeping an eye on the conversation but haven't contributed.  Thank you all for you for the hard work you have put into this.  We are ordering two Nexus 6's from Verizon today.  They should arrive early next week which will allow us to configure the device and install the app before we head out for Thanksgiving.  Either myself or Tristan will update everyone once we have them in hand.
Thanks again for all the input.
Mike
City IT Department

Woot!

This is great news!   I'll disable the monitoring system for now until the new devices are installed.

Also a heads up that we will be returning all of the RouteMatch equipment on the Trolleys once the new phones come in.  This includes the Samsung tablets, mounts, cases, and chargers.

Thanks Mike! Awesome!
On Fri, Nov 20, 2015 at 11:27 AM, greenlinktransit<EMAIL_ADDRESS>
wrote:

Also a heads up that we will be returning all of the RouteMatch equipment
on the Trolleys once the new phones come in. This includes the Samsung
tablets, mounts, cases, and chargers.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/105#issuecomment-158483126
.

FYI -- one of our supervisors said that the trolleys were appearing and disappearing on the Trolley Tracker all weekend despite the tablets being powered on.  Hoping these snazzy new phones will be more reliable.

How do the new phones look?   Let us know if you want any help on the special bootloader for auto power on/off (I haven't done one of these myself before)

I second @bikeoid Let us know if we can help get the phones installed this week. I'm around and available if needed.

We have the phones in hand now.  Tristan will be working with everyone to get the app installed and configured hew will also work with the fleet shop to get the units mounted.  If everything goes as planned, they should be live this week.

I won't be able to tinker with the auto power on/off stuff (off will just need an app/I can add it to the agent, on will need some digging) without access to a device. I can probably get started by poking around a rom I downloaded off xda-developers but I'll definitely need to use one of the devices to test, unless @tkenney-gvl was going to take a stab at it.
FWIW I was going to follow the general approach here: http://stackoverflow.com/questions/4169387/how-to-make-android-device-boot-when-power-is-plugged-in

Hey guys, sorry for the delay. I wasn't able to get it taken care of before Thursday. Right now I'm working on getting the bootloaders unlocked and the devices rooted. Once that's done I'll go ahead and set the tracker agent to autostart when the device is powered on. Since the devices have battery, I'm honestly not sure how we'll be able to use the ignition-on feature. But if we can train the attendants to turn the devices off when the Trolley is done running and turn them on when they turn the Trolleys, then having the app autostart would make things a lot easier. :) Anyway, I'll let everyone know when the devices are installed in the Trolleys. Thanks again for all the help!

The app is already set to autostart when the device is powered on so we
should be good there. The premise of the ignition-on feature is that we
hook in to the charging screen (that pops up with a battery indicator when
you plug in a powered-down device) script and make it reboot the device, so
it is effectively powering on the device whenever it is plugged in. More
details in the stackoverflow link in my last comment.
We aren't sure how much of our issues have been due to drivers forgetting
to turn the tablets on/off but Grant has already had a few training
sessions with them. Not sure how effective that is. The idea behind the
auto-on/off feature was that we could mount the devices in a hidden spot
(the overhead compartment is a good candidate) and have them
out-of-sight/out-of-mind. Less likely to be stolen too.
On Mon, Nov 30, 2015 at 11:41 AM, tkenney-gvl<EMAIL_ADDRESS>wrote:

Hey guys, sorry for the delay. I wasn't able to get it taken care of
before Thursday. Right now I'm working on getting the bootloaders unlocked
and the devices rooted. Once that's done I'll go ahead and set the tracker
agent to autostart when the device is powered on. Since the devices have
battery, I'm honestly not sure how we'll be able to use the ignition-on
feature. But if we can train the attendants to turn the devices off when
the Trolley is done running and turn them on when they turn the Trolleys,
then having the app autostart would make things a lot easier. :) Anyway,
I'll let everyone know when the devices are installed in the Trolleys.
Thanks again for all the help!
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/105#issuecomment-160683451
.

Thanks to my supervisor, we found a fastboot command that allows the system to turn on automatically when power is applied (just tested and it works!). We still haven't solved for shutdown, but we're testing what will happen with a fully drained battery and the autostart. If that works, then I think we have all the pieces down so that when they turn on the Trolley and the power is sent to the device it should turn on automatically and then load the Trolley Tracker Agent app (just in case the event hook doesn't do the full trick). Hopefully that will solve all the hiccoughs. :)

That's awesome! Even easier than I expected. Give your supervisor a high
five for me. I believe there are apps that will do the shutdown or I am
pretty certain that I could package that functionality in with the agent in
just a few lines of code. Fingers crossed that it all works smoothly. It's
always a win when you can eliminate human error from the equation.
On Mon, Nov 30, 2015 at 2:10 PM, tkenney-gvl<EMAIL_ADDRESS>wrote:

Thanks to my supervisor, we found a fastboot command that allows the
system to turn on automatically when power is applied (just tested and it
works!). We still haven't solved for shutdown, but we're testing what will
happen with a fully drained battery and the autostart. If that works, then
I think we have all the pieces down so that when they turn on the Trolley
and the power is sent to the device it should turn on automatically and
then load the Trolley Tracker Agent app (just in case the event hook
doesn't do the full trick). Hopefully that will solve all the hiccoughs. :)
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/105#issuecomment-160728373
.

It sounds like you guys are on the right track.  For what it's worth, it would save us many headaches if we can completely remove the human component of turning the phones on/off during each run.  But you know that already.

Definitely agreed. +100 on no human interaction needed :)
On Mon, Nov 30, 2015 at 3:40 PM, greenlinktransit<EMAIL_ADDRESS>wrote:

It sounds like you guys are on the right track. For what it's worth, it
would save us many headaches if we can completely remove the human
component of turning the phones on/off during each run. But you know that
already.
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/105#issuecomment-160755342
.

Good news, I just implemented a feature in the agent that will shut down the device when it is unplugged. The two caveats are that it is opt-in (you will need to enable it in the settings for each device) and that it requires root. If you have a root management app on the device like SuperSU, you will need to grant the agent root access. It will request root access the first time you enable the shutdown feature and then unplug the device. Hope this is the last piece to our puzzle!
The update should be available via the play store in an hour or so. Which reminds me, are the devices configured to download new updates automatically? That would make updating the app pretty painless in the future.

One more point, this new feature is going to make it so if the drivers
unplug the USB cord to charge their own phone (as they've done in the
past), our device will be powered down. Just something to think
about/another reason to hide the device
On Nov 30, 2015 6:20 PM, "Jeremy Wight"<EMAIL_ADDRESS>wrote:

Definitely agreed. +100 on no human interaction needed :)
On Mon, Nov 30, 2015 at 3:40 PM, greenlinktransit <
<EMAIL_ADDRESS>wrote:

It sounds like you guys are on the right track. For what it's worth, it
would save us many headaches if we can completely remove the human
component of turning the phones on/off during each run. But you know that
already.
—
Reply to this email directly or view it on GitHub
<
https://github.com/codeforgreenville/trolley-tracker/issues/105#issuecomment-160755342
.

—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/105#issuecomment-160794367
.

SuperSU is on both Nexi (?), so I'll add the tracker to the root list. As far as I know they are set to do the automatic updates, but I'm not sure how the newer Android "oh, you're not on wireless, so maybe we won't download the updates" feature will affect it. I know that it's a small app, so it may do the auto update. I'll check into it a bit more and hopefully there's an option in the app to specifically get the updates automatically instead of requiring manual intervention. Worst case, we can set up something on our end to go to the shop and do maintenance once a month or so and get all the system and app updates. :)

Sounds good! Another thought, I think there is WiFi around the maintenence
bay. So if we are 100% sure that it's a unique SSID and not used anywhere
else downtown (don't want to go down that road again), then maybe that
could trigger the updates?
On Dec 1, 2015 9:41 AM, "tkenney-gvl"<EMAIL_ADDRESS>wrote:

SuperSU is on both Nexi (?), so I'll add the tracker to the root list. As
far as I know they are set to do the automatic updates, but I'm not sure
how the newer Android "oh, you're not on wireless, so maybe we won't
download the updates" feature will affect it. I know that it's a small app,
so it may do the auto update. I'll check into it a bit more and hopefully
there's an option in the app to specifically get the updates automatically
instead of requiring manual intervention. Worst case, we can set up
something on our end to go to the shop and do maintenance once a month or
so and get all the system and app updates. :)
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/105#issuecomment-160986584
.

We got the Nexus 6 phones over to the trolleys and they are being installed. As of right now, when the drivers turn the trolleys on, the auto-on feature kicks in and the Nexus 6 will boot (tested), then automatically launch the app as soon as the OS boots (just a precaution, since @bikeoid mentioned that he had to do that before on the tablets on occasion). The wifi is also on and automatically set up to connect to our Internal City Wifi network, which is over at the Shop. I tested and as soon as I had it back on wifi the tracker agent updated on both phones, so we will have to leave the wifi on. With the new version of the tracker, I was able to set the auto-off feature and also grant root permissions and have tested both phones when the power was unplugged. That worked, too, so hopefully at this point everything should be as automated as possible and working for tomorrow's route as soon as they're installed.
Initially we're having one mounted on the dash and the other one in the other trolley mounted in the overhead bin, and we'll see if there is a difference in signal quality between the two trolleys. If they both function great this weekend, then we'll be able to put the dash mounted on also in the overhead bin and make it super clean. :) Thanks again for everyone's help with this! :+1:

:trolleybus: :dancer: :fireworks: :tada:  Super exciting
Worth a mention, our belief is part of the problem with the tablets was they were jumping off the internal trolley wi-fi and connecting to other free downtown hotspots and even the other trolley wi-fi. I doubt this will be a problem with the phone, but it we do have connection problems it might be worth turning off wi-fi as a troubleshooting step.
:fireworks: :trolleybus: :tada: :trophy:

Very exciting, it all sounds promising! Thanks for all your help @tkenney-gvl, I think we're close! :tada:

@tkenney-gvl Thanks for your hard work on this, Tristan!

That's great news!    I'll keep an eye on the accuracy over the weekend and should be able to generate the same type of report as last time for each vehicle.

This is great news. Look forward to checking it this weekend!

@tkenney-gvl so we should be seeing two trolleys right now? Looks like trolley 6 is up but trolley 5 is MIA. Which one was the dash-mount? Excited to see these new nexuses cranking out some lat/lngs!

So the tracker is still running on the trolley even though it's been parked
for a while now. It just occurred to me that we need to make sure the keys
are removed from the ignition after the drivers turn the trolleys off.
Otherwise the accessories (including our phone) are left powered on and
will drain the trolleys battery. Not to mention our app will run overnight.
Doesnt really affect the reliability of our app (I'm pretty sure Mike can
code something to mark a trolley as offline if it hasn't moved a
significant amount in >30min) but it sure will suck to have to jump the
trolleys every morning.
On Dec 2, 2015 7:44 PM, "Jeremy Wight"<EMAIL_ADDRESS>wrote:

This is great news. Look forward to checking it this weekend!
—
Reply to this email directly or view it on GitHub
https://github.com/codeforgreenville/trolley-tracker/issues/105#issuecomment-161479427
.

Trolley 5 was last seen at city hall, so it's never obtained a GPS fix from the trolley.

I've alerted OPS about the new devices and have asked them to keep an eye on the tracker over the next couple weeks to see if there's a certain trolley that's working better than the other.  I've also asked them to give me a heads up if a trolley ever goes out of service, is late, etc.  I know that the trolley schedule is going to be weird tomorrow with the parade -- I believe we're decorating both trolleys in the morning, so we probably won't have anything to look at until after the parade is over.
Lastly, we have a new General Manager of OPS starting with us on Monday.  He's young and understands technology very well.  Once he gets settled in, I'd like to set up a short meeting so we can brief him on the Trolley Tracker and how he can assist.
Thanks again for everyone's hard work on this.

I separated out the two "bugs" we tracked last night (Thursday 12/3) into unique issues.


[Feature] Access to webhook id in handlers

Overview
I want to process webhooks in an idempotent way. Shopify provides us with X-Shopify-Webhook-Id headers. But these get lost in the webhook process function.
It would be great to have access to the webhook ID in my handlers.
Type

[ ] New feature
[x] Changes to existing features

Motivation

What inspired this feature request? What problems were you facing?

I want to process webhooks in an asynchronous way, using background workers. For this, I want to use the webhook ID as the background Job ID.
Checklist

[x] I have described this feature request in a way that is actionable (if possible)

not stale

any updates here?


chore: revisit LightGBMRanker manifest.yml

Fixed isort/flake8/test issues. Please take a look if you have time. Thanks! @tadejsv


Drag a Font file in a 'Font' field to automatically generate a Dynamic/BitmapFont with Font Data

Describe the project you are working on
i dont think it matters
Describe the problem or limitation you are having in your project
Every time I am adding a new Label/TextEdit or anything related, and have to put in a font, I always think having to create a DynamicFont BitmapFont and then assigning the data for it is very cumbersome
Describe the feature / enhancement and how it helps to overcome the problem or limitation
Just drag a font file over a "Font Data" or similiar property field and have it generate a Dynamic/BitmapFont with the data from the dragged file
Describe how your proposal will work, with code, pseudo-code, mock-ups, and/or diagrams

not sure how to explain this
If this enhancement will not be used often, can it be worked around with a few lines of script?
Not to my knowledge
Is there a reason why this should be core and not an add-on in the asset library?
I think this is a very basic feature and having to install a separate plugin for it to happen could lead people off

I've moved this to the main repository, as it's really just a bug, and a regression to boot. Can you please update the OP to add information about which version of Godot you are using, what system you have, etc?

I noticed that the code that should handle Fonts wasn't backported for some reason (or it was removed?).

Aye, I never backported it when porting the resource picker (https://github.com/godotengine/godot/pull/49491). I think I wasn't sure how it's supposed to work in 3.x with Dynamic/BitMap fonts.
Ok, then it's not a regression.

I've moved this to the main repository, as it's really just a bug, and a regression to boot. Can you please update the OP to add information about which version of Godot you are using, what system you have, etc?

I use Godot 3.4.4, I've updated the post to reflect that


launcher.spot.im

Energized Protection - block ⚡

Let's make an annoyance free, better open internet, altogether!

Issue Submit Form

  Provide the following infos properly, which will help us to resolve your issue quickly.

Issue(s):
Type x in between [ ] and make sure there isn't any space between brackets. Example; for Your Selected Issue(s), type like this - [x]
You can select more than one category of issues if you need to!

[x] Whitelist
[ ] Blacklist
[ ] App Broken
[ ] Website Broken
[ ] Request
[ ] Other Issue

Pack(s):
Write the name of the pack(s) you are using.

Pack(s) Name: blu

Extension(s):
Also name the extension(s) if you are using any. If you don't then leave it blank.

Extension(s) Name:

Domain(s):
If you are submitting this issue for whitelist/blacklist issue, send us the domain(s) for whitelisting/blacklisting here. Kindly use the Code Tag to prevent tracking.

Domain(s):

launcher.spot.im

Your Config:
Just to ensure there is no issues or conflicts with other app/software/magisk module/extension/source list.
Make sure you are running Energized Protection Service only.

Client: blokada

Version: 19.02.032

Details:
Write us a lil bit more about your issue or query. You can attach any screen shot or log of the issue or advert, this will help to highlight it.

Your Issue Detail:
Blocks comments
https://m.washingtontimes.com/news/2019/feb/11/appeals-court-rules-trump-can-build-border-wall/
Please also consider if the other spot.im domains need to be blocked:

mc-siderail.spot.im
recirculation.spot.im
spotops.spot.im
traffic.spot.im

Thank you for making Energized Protection great with your kind help!

A project by Ador with ❤

@AdroitAdorKhan Thanks, but now there are 62 spot.im items in the list... so the comments is still broken.

My bad! I will fix them on next release. Probably, tomorrow!

@AdroitAdorKhan still broken. 19 entries in the list.

https://www.foxnews.com/politics/new-york-times-backs-up-trump-claim-yes-there-was-duct-tape


maven-compiler-plugin: disable forking + remove duplicated config

jboss-parent already defines source, target, warnings and deprecation
fork config removed == forking disabled (default is false)
meminitial and memmax are only needed when forking

thanks @psiroky


Add MI - Fuel Tank Expansion from Kerbal Stuff

This pull request was automatically generated by Kerbal Stuff on behalf of MunarIndustries, to add MI - Fuel Tank Expansion to CKAN.
Please direct questions about this pull request to MunarIndustries.

Closing in favour of https://github.com/KSP-CKAN/NetKAN/pull/708


[FEAT]: Update pledge certificates with the given design v3

What is the feature request for?
Registry Core
What problem/inconvenience (if any) will this feature solve?
Update pledge certificates with the given design

[x] Compress and Add provided certificates
[x] Fix positions of values accordingly

Describe the feature clearly.
Add a new feature that does ....

https://github.com/Sunbird-RC/demo-donor-registry/pull/398
https://github.com/Sunbird-RC/demo-donor-registry/pull/399


Adding ms.prod

Docs Build status updates of commit 09d60bd:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

trace-processor-reference-docs/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Copy of theta23 param causes issue

In analysis.py the function  get_separate_octant_params (used by _fit_octant) makes a copy of the theta23 Param instance (see here), and this copy is later written back to hypo_maker.params (see here).
theta23 lives in a ParamSelector object, which stores the original theta23 param value in its dict of selections. And so there is now basically a new duplicate parameter in the current params, but this will be overwritten by the original stored param in the selections dict next time ParamSelector.select_params is called (see here).
This is a problem is the user then modifies the theta23 param, since at the start of the next fit ParamSelector.select_params is called and the theta23 param is overwritten by the stored value, and thus the user's changes are lost. This breaks oscNext sensitivity scans for numu disappearance, since the user does a free fit first (resulting in the duplicate theta23 param), then fixes theta23 for the scan but at the first scan point the param is overwritten and hence it is no longer fixed, breaking the scan.
The solution to this issue is simple, simply remove the deepcopy of the original param in this line.

I am fixing this in my own fork now, and will make a PR ASAP

Hey, cool! We then just need to make sure that https://github.com/icecube/pisa/blob/master/pisa/analysis/analysis.py#L327 does not change the original value

This issue is now resolved and we have unit tests to assert this. :)


Hashing public data

Added a section to describe the GGPR trick of hashing public inputs to a single primary input.

@mpzajac  would you mind sanity checking this new section in the zeth specs?

@mpzajac  would you mind sanity checking this new section in the zeth specs?

I made some minor changes to 4.3.4 -- the relation definition needed a bit of polish. Please check. Otherwise LGTM

I made some minor changes to 4.3.4 -- the relation definition needed a bit of polish. Please check. Otherwise LGTM

Great.  Thanks for fixing that definition @mpzajac .  That was a pretty big mistake :)
I've rebased  onto the latest to clean the history.


please add the projected volume type in the volumes list

Is your feature request related to a problem? Please describe.
When running kubectl advise-psp inspect -n test_namespace and that pod requires a projected volumeType of some kind, the psp generated is not included in the list of volumes: in the generated yaml.
Describe the solution you'd like
If a volumeType of projected is detected in the spec its read write property and type should be listed in the psp generated i
Describe alternatives you've considered
No other alternatives were considered other than having to debug the missing pieces while getting the amazon-cloudwatch-agent and fluentbitd daemonsets running in their namespace.

I also found the same to be true for pods that might need to allow for allowPrivilegeEscalation and various allowedCapabilities generally are listed in the pod spec, but also not included in the generated output. If I should create a new issue for each of these I can

@caleyg do you have a sample yaml that I can test with?

thanks for the response! these might be able to help some!
kind: Pod
metadata:
  name: test-projected-volume
spec:
  containers:
  - name: test-projected-volume
    image: busybox
    args:
    - sleep
    - "86400"
    volumeMounts:
    - name: all-in-one
      mountPath: "/projected-volume"
      readOnly: true
  volumes:
  - name: all-in-one
    projected:
      sources:
      - secret:
          name: user
      - secret:
          name: pass

# Create files containing the username and password:
echo -n "admin" > ./username.txt
echo -n "1f2d1e2e67df" > ./password.txt

# Package these files into secrets:
kubectl create secret generic user --from-file=./username.txt
kubectl create secret generic pass --from-file=./password.txt

# create the projected test pod (the above yaml)
kubectl apply -f https://k8s.io/examples/pods/storage/projected.yaml

POD with NET_ADMIN capabilities I haven't tried to add others that might be needed
kind: Pod
metadata:
 name: capabilities
spec:
 containers:
   - name: capabilities
     image: "ubuntu:14.04"
     command:
       - /bin/sleep
       - "300"
     securityContext:
       capabilities:
         add:
           - NET_ADMIN

a privileged pod that would need a generated psp unique to that pod to include allowPrivilegeEscalation: true
apiVersion: v1
kind: Pod
metadata:
  name:      privileged
spec:
  containers:
    - name:  privileged
      image:"ubuntu:14.04"
      securityContext:
        privileged: true


(-215:Assertion failed) number < max_number in function 'icvExtractPattern'

Just tried this extension, after generating images then I got this errors when it generate .mp4 file:
Start generating .mp4 file
<EMAIL_ADDRESS>global cap_ffmpeg_impl.hpp:2991 open Could not find encoder for codec_id=27, error: Encoder not found
<EMAIL_ADDRESS>global cap_ffmpeg_impl.hpp:3066 open VIDEOIO/FFMPEG: Failed to initialize VideoWriter
<EMAIL_ADDRESS>global cap.cpp:595 open VIDEOIO(CV_IMAGES): raised OpenCV exception:

OpenCV(4.7.0) /io/opencv/modules/videoio/src/cap_images.cpp:267: error: (-215:Assertion failed) number < max_number in function 'icvExtractPattern'

The generation is complete, the directory::outputs/mov2mov-videos/1684820171.mp4

Total progress: 100% 1200/1200 [27:23<00:00,  1.37s/it]
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/dist-packages/gradio/routes.py", line 337, in run_predict
    output = await app.get_blocks().process_api(
  File "/usr/local/lib/python3.10/dist-packages/gradio/blocks.py", line 1018, in process_api
    data = self.postprocess_data(fn_index, result["prediction"], state)
  File "/usr/local/lib/python3.10/dist-packages/gradio/blocks.py", line 956, in postprocess_data
    prediction_value = block.postprocess(prediction_value)
  File "/usr/local/lib/python3.10/dist-packages/gradio/components.py", line 1888, in postprocess
    y = self.make_temp_copy_if_needed(y)
  File "/usr/local/lib/python3.10/dist-packages/gradio/processing_utils.py", line 379, in make_temp_copy_if_needed
    temp_file_path = self.get_temp_file_path(file_path)
  File "/usr/local/lib/python3.10/dist-packages/gradio/processing_utils.py", line 365, in get_temp_file_path
    file_hash = self.hash_file(file_path)
  File "/usr/local/lib/python3.10/dist-packages/gradio/processing_utils.py", line 334, in hash_file
    with open(file_path, "rb") as f:
FileNotFoundError: [Errno 2] No such file or directory: 'outputs/mov2mov-videos/1684820171.mp4'

Do I installed wrong OpenCV ?
!pip -q install opencv-python
Sorry to open this new Issue if exists, Not be a racist but I'm having trouble to find the same issues as mine here because mostly are in Chinese 😂😅

try xvid or mp4v. similar errors occur when I use H264 encoding.


Missing prompts “single-v1-multi-turn” and “single-math-v1-multi-turn” in Japanese MT-Bench

Thank you for maintaining the benchmarks. Currently, I am evaluating models with Japanese MT-Bench, and I need the prompts “single-v1-multi-turn” and “single-math-v1-multi-turn” to execute the function 'make_judge_simgle' in gen_judgement.py, but I can't find them. There seems to be only the prompts “single-v1” and “single-math-v1” in fastchat/llm_judge/data/judge_ja_prompts.jsonl. I would appreciate it if you could tell me where to find them or how to evaluate them.

There is no evaluation result for the second turn in model_judge file as well.
Where are the evaluation results for the second turn?


fix: improve date and date-time serialization/deserialization

Fixes arf/planning-sdk-squad#2291
This commit contains a re-alignment of our support for
serialization and de-serialization of java.util.Date values
within the Java core:

The basic function of formatting and parsing java.util.Date
values as an OpenAPI "date" or "date-time" value is now isolated
in the DateUtils class.
The Gson serialization/deserialization of "date-time" values is now
implemented in the DateTimeTypeAdapter class. This class is also the
default type adapter registered with Gson for java.util.Date instances.
The Gson serialization/deserialization of "date" values is
implemented in the DateTypeAdapter class.  This class can be used
with the @JsonAdapter annotation to override the ser/deser handling
of a java.util.Date field that should be interpretted as a "date" value.
This will be done by the Java generator.

@mkistler @jorge-ibm hold on before reviewing this... I found a little gotcha.

@mkistler @jorge-ibm hold on before reviewing this... I found a little gotcha.

Ok, this is ready to review now... and that's my final answer :)

:tada: This PR is included in version 9.5.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Font color not reverting after hover over button from 2.6.0 onwards (UWP)

When using a button with a dark background and a white font colour, hovering inverts the font colour to black (and the background to grey). From 2.6.0 onwards, the background colour reverts when hover ceases, but the font colour does not (it stays black).
Button:
x:Name="Administration"
HeightRequest="60"
WidthRequest="300"
CornerRadius="30"
Grid.Row="7"
Text="Administration"
VerticalOptions="Center"
HorizontalOptions="Center"
FontSize="Medium"
TextColor="White"
Clicked="AdministrationClicked">
Button.Background
LinearGradientBrush EndPoint="0,1">
GradientStop Color="#90278E" Offset="0.1" />
GradientStop Color="#353254" Offset="1.0" />
LinearGradientBrush>
Button.Background>
Button>
Before hover:

During hover:

After hover:

Likely dupe of #5717

Hi - is there a timeline on when a fix for this is likely to be available please?


Communicate node ID in metadata of subscription requests

As the gRPC protocol is stateless, and transport connection information cannot reliably be used to establish the peer identity, we need to exchange node IDs along with subscription requests. Request metadata is the place to do it.
The sender ID field from Gossip therefore becomes redundant and is removed.

Ugh, I meant to publish this as a draft. The IDs are not yet sent on the client side. Stay tuned for more commits.

If you want, there is a label X-WIP you can use to warn others it is not meant to merge already

Rebased and ready now.


gcode module has no way to pass information to octoprint

Is your feature request related to a problem? Please describe.
When using robotic_chess.octoprint.Printer.run_gcode() there is no way to input gcode from robotic_chess.gcode.Parser.parse().
Describe the solution you'd like
A mode to immediately output gcode after running a command.
Describe alternatives you've considered
Rewriting the entire gcode library with functions instead of a class.

In development.

Fixed.