Add basic buzzer system

Main limitation w/ this system is that ties are broken by port priority, though the polling rate might be fast enough that it's not a real issue.
Displayed name is taken from the player list

Can you make the graphic and/or dashboard show the list of connected controllers and which players they're assigned to? That way someone can look at it during setup to make sure the controllers connect as they plug them in.


[Swift 5.0] Extend @available to support PackageDescription

rdar://problem/46572320 [Swift 5.0] Extend @available to support PackageDescription
This introduces a new private availability kind "_PackageDescription" to
allow availability testing by an arbitary version that can be passed
using a new command-line flag "-package-description-version". The semantics
are exactly same as Swift version specific availability. In longer term,
it maybe possible to remove this enhancement once there is
a language-level availability support for 3rd party libraries.
Motivation:
Swift packages are configured using a Package.swift manifest file. The
manifest file uses a library called PackageDescription, which contains
various settings that can be configured for a package. The new additions
in the PackageDescription APIs are gated behind a "tools version" that
every manifest must declare. This means, packages don't automatically
get access to the new APIs. They need to update their declared tools
version in order to use the new API. This is basically similar to the
minimum deployment target version we have for our OSes.
This gating is important for allowing packages to maintain backwards
compatibility. SwiftPM currently checks for API usages at runtime in
order to implement this gating. This works reasonably well but can lead
to a poor experience with features like code-completion and module
interface generation in IDEs and editors (that use sourcekit-lsp) as
SwiftPM has no control over these features.

Trunk PR here: https://github.com/apple/swift/pull/21110
I couldn't find any post that describes the formal process for nominating changes to 5.0 so raising PR directly.

@swift-ci smoke test

@swift-ci test

Build failed
Swift Test OS X Platform
Git Sha - 14679bbeca8b0ad77f5aef488f79002919e535b2

@swift-ci test macOS


Data Preparation Problem for  conll2003

Hi authors,
First of all, I would like to thank for your great works. I've install the packages according to the requirement file, and I run the command for data preparation as:
python -c "import fewshot; fewshot.make_challenge('flex');"
However, an error shows when downloading the conll2003 dataset:

Downloading and preparing dataset conll2003/conll2003 (download: 4.63 MiB, generated: 9.78 MiB, post-processed: Unknown size, total: 14.41 MiB) to /home/yisyuan/.cache/huggingface/datasets/conll2003/conll2003/1.0.0/40e7cb6bcc374f7c349c83acd1e9352a4f09474eb691f64f364ee62eb65d0ca6...
Traceback (most recent call last):
File "", line 1, in                                                                                | 0/3 [00:00<?, ?it/s]
File "/home/yisyuan/Workspace_2_250GB_SSD/researches/flex/fewshot/challenges/registration.py", line 13, in make
return registry.make(id, **evaluator_kwargs)
File "/home/yisyuan/Workspace_2_250GB_SSD/researches/flex/fewshot/challenges/registration.py", line 108, in make
return self.get_spec(id).make(**evaluator_kwargs)
File "/home/yisyuan/Workspace_2_250GB_SSD/researches/flex/fewshot/challenges/registration.py", line 29, in make
return Evaluator(config_name=self.id, hash=self.hash, **evaluator_kwargs)
File "/home/yisyuan/Workspace_2_250GB_SSD/researches/flex/fewshot/challenges/eval.py", line 93, in init
split='test',
File "/home/yisyuan/Venv/flex/lib/python3.7/site-packages/datasets/load.py", line 1707, in load_dataset
use_auth_token=use_auth_token,
File "/home/yisyuan/Venv/flex/lib/python3.7/site-packages/datasets/builder.py", line 595, in download_and_prepare
dl_manager=dl_manager, verify_infos=verify_infos, **download_and_prepare_kwargs
File "/home/yisyuan/Venv/flex/lib/python3.7/site-packages/datasets/builder.py", line 690, in _download_and_prepare
) from None
OSError: Cannot find data file.
Original error:
Error instantiating 'fewshot.datasets.store.Store' : Couldn't find file at https://github.com/davidsbatista/NER-datasets/raw/master/CONLL2003/train.txt

It seems like the error comes from the Huggingface datasets since there is a related issue which has been solved. (https://github.com/huggingface/datasets/issues/3582) However, I've changed the version of datasets from 1.8.0 (as requirements) to 1.18.3 (current version) but the error still happens. Also, I've tried to download the conll2003 dataset directly with 1.18.3 version and it just goes well:
datasets.load_dataset("conll2003")
So, I'm not quite sure what goes wrong. It would be really appreciated if you could provide any suggestion. Thank you!

Thank you for reporting!
Should be fixed now. Please reopen if you still have issues.
To be safe, I have updated the HF_SCRIPTS_VERSION only for that dataset.

Sorry, Im a newbie and my task is to learn with flair how to train models. And I just copied the code `import torch
1. get the corpus
from flair.datasets import CONLL_03_GERMAN
corpus = CONLL_03_GERMAN()and this doesnt work at all becauzse I have to mount somtehing from somehwere (ECI Multilingual...) but I cant really find and and understand what to do. I tried it also with from datasets import load_dataset
dataset = load_dataset("conll2003")and it downloaded it but latest step 3 . make the tag dictionary from the corpustag_dictionary = corpus.make_tag_dictionary(tag_type=tag_type)` it failes beacuse "corpus" is not defined. Could please someone help! Thank you so much!


JasperFx Ecosystem Dependency Reorganization

This is in Wolverine just because it needs to go somewhere, and because Wolverine is kind of at the top.
"Problems"

There are some shared framework-y elements like the application assembly determination that are duplicated between Marten & Wolverine today, with Ermine coming soon-ish
I think it would be hugely advantageous to have some sharing of the OptimizeArtifictWorkflow between Marten & Wolverine, just so there's less repetitive junk going on in bootstrapping -- especially when there are becoming some many different things that should or could be different in Development vs Production mode
Wolverine 3.0 is coming soon, so Wolverine can accommodate breaking changes, but there's no other justification for a Marten 8 in the immediate future. At least until Ermine later this year
Lamar is already on the chopping block. Questioning whether Oakton should be as well

Today
Some of the current dependencies between the greater JasperFx / Critter Stack world:

I've omitted Weasel, but it's of course there and would be impacted by this too.
Proposed Future

Okay, so this is going to require a full point Marten 8 and a new Wolverine as well. Maybe this doesn't exactly happen until Wolverine 4. Might help to start with some temporary [Obsolete] tags in especially Marten
Here's the big points, I think:

The basic goal is to simplify the dependency structure and just make it look like things are more cohesive. Should also move in the direction of having fewer knobs and dials for users to have to do to go with the Critter Stack in terms of how many Nugets have to be added or how many different settings need to be used
Lamar just disappears, but will still be supported for usage within Wolverine. That work is close to done already
We introduce a brand new, shared library called JasperFx.Framework that will hold some newer stuff related to shared configuration helpers and logic that is very specific to Marten/Wolverine/future critter stack tools, but not generic enough to live in JasperFx.Core that's just utilities and more or less the "junk drawer"
Combine JasperFx.CodeGeneration into JasperFx.Framework
LEAVE JasperFx.Compiler alone, other than to change its dependency to JasperFx.Framework
Oakton goes away, with basically everything it does moving to the new shared JasperFx.Framework, including both the command line parsing and execution, as well as the IEnvironmentCheck and IStatefulResource models
Fold the commands in Marten.CommandLine and really Weasel.CommandLine into Weasel.Core and/or Marten. Trying to get to fewer assemblies and less stuff to add
Here's a hurtful one, move as much of the projection support in Marten including the async daemon code to a more generic JasperFx.Projections library. This is 100% in preparation for tackling "Ermine", the intended Sql Server backed event store lib

Finer Grained Thoughts

Centralize the configuration of the code generation GenerationRules
Centralize the application assembly determination that both Wolverine & Marten & Ermine in the future need
Centralize the "optimize artifact workflow" logic that all the tools use
Set us up for some streamlined bootstrapping alternatives. Anything that reduces the friction of starting a new project can only help

Wolverine & Marten Compliance Tests
To help build more Event Sourcing + CQRS products with Wolverine as a baseline, let's start to pull a standard set of compliance tests for Wolverine extensions and possible future Marten alternatives. Some of this already exists, or "almost" exists, but put it in a publicly published Nuget so it's usable outside of the main Wolverine or Marten repositories:

The existing TransportCompliance work
The smoke tests on stateful resource compliance that today is copy/pasted
Scheduled test integration
Envelope persistence -- this is a bit bigger because of the API surface, but it would be super helpful for the upcoming RavenDb integration
Inbox/outbox integration tests ?
Persisted saga tests -- already kind of exists, but it's mostly copy/pasted. See if that can be generalized
Leadership assignment and node failover -- ugh, this will stink
Scheduled job execution
Event sourcing conformance testing -- much bigger. Might require some changes to Marten first, but do in preparation for Ermine. Kind of assumes that there will be an interface for event capture that is more or less standardized between different critter stack versions of event sourcing

Maybe a different take on this. What if Oakton 7.0 becomes what I wanted JasperFx.Framework to be? It's goofy naming, but in this case Oakton essentially becomes the foundational piece for JasperFx tools. It already has some things like the IStatefulResource model that shouldn't technically be in Oakton anyway

Latest Thinking (September 21st)
JasperFx Repository

Build a new library named JasperFx that will subsume what is now JasperFx.Core, JasperFx.CodeGeneration, and Oakton. Keep the same namespace for the core and code generation elements
Kind of orphan Oakton as is where its types mostly inherit from the same types in the new JasperFx lib? Or don't worry about it
Retain the dependency on Spectre.Console because it's really light in terms of its dependency tree
Subsume JasperFx.CodeGeneration.Commands into the new JasperFx library
JasperFx.RuntimeCompiler just moves to the new JasperFx repository
Actually write documentation for all of JasperFx including the code generation stuff

Streamlined "Stateful Resource" Model
Have a single place where you can set all the "should I build this on demand at runtime, or not" settings across
both Marten & Wolverine & whatever other critters exist.
By standardizing on this model across the board, some one off things in Marten & Wolverine should go away:

Deprecate Marten specific options to do database set up on app start that was introduced in Marten 5 (I think)
Delete one off AutoProvision() / AutoPurgeOnStartup() options on Wolverine transports
Eliminate the one off boolean flag in Wolverine for disabling automatic envelope storage setup

In all cases, use the AutoCreate enum -- currently in Weasel, but moving to JasperFx -- to specify the setup rules

// Helper for overriding in tests. If `generatedCodePath` isn't specified, but it under `Internal/Generated` of the designated
// assembly, assuming it's in a project named the same as the assembly
builder.Services.OverrideApplicationAssembly(assembly, string? generatedCodePath = null);

// Syntax for configuring the stateful resource model
builder.Services.ConfigureJasperFx(opts => {
    // Shouldn't be needed very often, but *sometimes* people just want to do things differently
    // instead of using idiomatic "Development" / "Testing" / "Production"
    opts.DevelopmentEnvironmentNames = ["Development", "Testing"];

    // This would be the default of either
    opts.Development.AutoCreate = AutoCreate.CreateOrUpdate;

    // Do *once* for all of the critters
    opts.Development.TypeLoadMode = TypeLoadMode.Dynamic;

    // Maybe make this auto. Probably make this a prop instead
    opts.Development.ResourceSetupOnStartup();

    // Default is false. Would apply to both AutoPurgeOnStartup() in Wolverine and Marten.ResetState()
    // Development time helper!!!
    // Could do stuff like delete all outstanding inbox/outbox messages, reset Marten state, purge queues
    opts.Development.ResetAllStateOnStartup = true;

    opts.Production.AutoCreate = AutoCreate.CreateOrUpdate;

    // Maybe make this auto. Probably make this a prop instead
    opts.Production.ResourceSetupOnStartup();

    // Do *once* for all of the critters
    opts.Production.TypeLoadMode = TypeLoadMode.Static;
});

Also, keep the current extension methods on IServiceCollection that refer to the stateful resource model

Update
What's shown as "JasperFx.Framework" and "JasperFx.Core" are being subsumed into a new library called just "JasperFx" as well as "Oakton". To avoid disturbing existing Oakton users too much, Oakton will be somewhat rebuilt as a shim over the newer "JasperFx". All this shuffling around hopefully helps us reduce the total number of Nugets floating around in our ecosystem and also make there be less wiring, configuration, and general overhead to set up projects.

This was just a discussion. The ongoing work in the jasperfx repo already does some of this that will be incorporated into Wolverine 4.0


Add support for building bazel from source

This patch adds a new notation to .bazelversion:
<FORK>/commit/<GIT-REV>
Bazelisk will fetch, build and use this distribution. This enables
more robust usage of bazel forks without needing to deploy binary
distributions to github.
See https://github.com/bazelbuild/bazelisk/issues/110

Hi @chancila,
sorry, I was busy with some work on Bazel's CI in the last days and need a bit more time for the review here. I'll get back to you very soon!
Philipp

@philwo Do you have time to look at it this week?

Any updates on this?


Support for single multi-node task

Related to #476 and #1277
Currently nodes is one of the task options that has not been implemented. This option is supposed to specify the number of nodes a single task runs, and a template is supposed to do something like
%PBS -l {nodes}:{cores}

sos execute task_id

to execute a multi-node task with id task_id.
However, because multi-node jobs require special way to start (e.g. mpiexec or mpirun) and sos execute cannot mimic this behavior, tasks are currently limited to single node only.
With the new -e option
sos execute -e pbs {task}

we are supposed to implement a PBS version of the task executor. Although this feature is designed to distribute multiple subtasks to multiple nodes, it would be nice to support single multi-node as well. This would involve the submission of a MPI job as follows:
task: nodes=5, cores=4
mpiexec ...

Just for records of tests:

installed mpi4py on cluster (PBS)
Created test_mpi.py with content

import os
from mpi4py import MPI

comm = MPI.COMM_WORLD
rank = comm.Get_rank()

with open(os.path.join(os.environ['HOME'], f'mpi_result_{rank}.txt'), 'w') as out:
    out.write(f'My rank is {rank}\n')

On head node, mpiexec creates four files

(sos) bpeng1@q1prphtch00:~/sos/sos$ mpiexec -n 4 python test_mpi.py

Create a bash script test_mpi.sh with content

#!/bin/bash
#PBS -N test_mpi
#PBS -l nodes=2:ppn=4
#PBS -l walltime=1:0:0
#PBS -l mem=1GB
#PBS -o /home/bpeng1/.sos/tasks/test_mpi.out
#PBS -e /home/bpeng1/.sos/tasks/test_mpi.err
#PBS -m ae
#PBS -M<EMAIL_ADDRESS>#PBS -v /home/bpeng1/sos/sos

module load openmpi

mpiexec python /home/bpeng1/sos/sos/test_mpi.py

Submit job in a regular way

qsub test_mpi.sh

and everything works as expected.

Then, if not using MPI, we can do

test_regular.py

import socket
import os
with open(os.path.join(os.environ['HOME'], f'regular_{socket.gethostname()}_{os.getpid()}.txt'), 'w') as out:
    out.write(f'I am process {os.getpid()} on host {socket.gethostname()}\n')

test_regular.sh

#!/bin/bash
#PBS -N test_mpi
#PBS -l nodes=2:ppn=4
#PBS -l walltime=1:0:0
#PBS -l mem=1GB
#PBS -o /home/bpeng1/.sos/tasks/test_mpi.out
#PBS -e /home/bpeng1/.sos/tasks/test_mpi.err
#PBS -m ae
#PBS -M<EMAIL_ADDRESS>#PBS -v /home/bpeng1/sos/sos

python /home/bpeng1/sos/sos/test_regular.py

Running this on the cluster only creates one file, so the script is not executed properly on multiple nodes.


Fixed decorators formatting bug #74

Issue: https://github.com/royriojas/esformatter-jsx/issues/74

hi @theadriann
Thank you very much for your contribution, will it be too much to ask to add unit tests for this one? please check the other unit tests that are there.
I plan to move to use snapshots instead of what currently is there, sadly I haven't find time yet to fix this.

Sure 📦 🚢

@royriojas  is everything ok?

it is sorry for the long delay to reply. It is merged now. Will publish a new version soon

@theadriann published as<EMAIL_ADDRESS>Thank you very much on helping with the bug


fix(modal): add primary focus on open

Related Ticket(s)
#2723
Description
This focuses the close button in LightboxMediaViewer when the modal first opens.
Changelog
New

add selectorPrimaryFocus to ExpressiveModal

Thanks @kennylam for getting into this! I'm not familiar enough on how <ExpressiveModal> should work, but just thought it'd be nice if we can limit the change in behavior to light box only; Given for many kind of modals the primary focus tends to be on the primary button.

@asudoh Yes, you're correct. Currently ExpressiveModal simply imports Carbon's ComposedModal and the only component of ours that uses it is LightboxMediaViewer. If it becomes problematic we can make close the default prop but open it up to be user-defined.
The larger issue I'm wondering about is whether we should be using Carbon's ComposedModal vs ModalWrapper? It seems ModalWrapper also includes passing focus back to the triggering element onClose, which ComposedModal does not have.

@asudoh Yes, you're correct. Currently ExpressiveModal simply imports Carbon's ComposedModal and the only component of ours that uses it is LightboxMediaViewer. If it becomes problematic we can make close the default prop but open it up to be user-defined.

Thank you for clarifying @kennylam! And we don't expect our users to use <ExpressiveModal> directly?

The larger issue I'm wondering about is whether we should be using Carbon's ComposedModal vs ModalWrapper? It seems ModalWrapper also includes passing focus back to the triggering element onClose, which ComposedModal does not have.

<ModalWrapper> is a demonstration-only component that was shipped by mistake. So our choice is between <Modal> and <ComposedModal>. <Modal> is a simple choice, <ComposedModal> provides more flexibility in content.
The reason <ModalWrapper> being demonstration-only component is that interaction with launcher button has many application-only use cases which does not make the problem area abstracted. That said, it's a purview of application code to handle "focusing back to the launcher button on close".

Ah, I see, thanks for the explanation. It can get a little confusing with all the different Carbon modal versions.

Thank you for clarifying @kennylam! And we don't expect our users to use <ExpressiveModal> directly?
I don't think so, no. I'm not very familiar with ExpressiveModal and how it even came about. But from what I see so far, it seems more like it should be an internal wrapper for Carbon modals and not exposed for direct use (but currently it is).


fix: update the sample output for 'get pods' command

This PR adds instances of "HA pods" to the sample output for 'kubectl get pods -n mayastor'.
Signed-off-by: anupriya0703<EMAIL_ADDRESS>

I think we should qualify the Sample Output shown, as being taken from a cluster with three mayastor nodes, to remove any ambiguity on the part of the user on exactly how many instances of a particular pod type are expected in a given cluster size.
Just taking this example on face value, for example, should I always expect to have 3 HA node pods? What if I deployed on a single node?

That makes sense. I have added that the output is for a 3-node mayastor cluster in the tab heading. Will check if the orientation looks alright. If not, I will be adding it as a note.


Stokes-V leakage validation checks

Now that a stokes-v imager has been added to flint it is possible to look at #53 and the associated pull request.
A few points to note:

The stokes-v imager is only run once on the very last set of measurement sets, whether they have gone through self-calibration or not
Not creating stokes-v linmos images of the cleaning residuals
No plans to make optimal and fixed beam resolutions
Need to consider which / how to convol. At the moment the final resolution is derived from the synthesised beam of the stokes-v images through radio_beam. The be strictly correct it should probably be the same final resolution as the stokes-I linmos image if V/I are to make sense

Being addressed in #157

Closed in #157
That was a silly bunch of commits around my bad spelling


Set custom/optional parameters in MultiSend transaction

Description
When creating a multisend transaction the user is not allowed to set the optional params included in SafeTransactionDataPartial (safeTxGas, baseGas, gasPrice, gasToken, refundReceiver and nonce).
Environment

Safe Core SDK last version

Expected result
The user is allowed to set the optional params included in SafeTransactionDataPartial (safeTxGas, baseGas, gasPrice, gasToken, refundReceiver and nonce) when creating a multisend transaction.

Do you envisage it just be an additional argument to Safe.createTransaction() ?

Hi @justinjmoses
Just adding the options parameter for the multisend transaction:
function createTransaction(tx: SafeTransactionDataPartial, options: undefined)
function createTransaction(tx: MetaTransactionData[], options?: SafeTransactionDataPartial)

Awesome. Looking forward to the next release.


InlineQueryResultArticle doesn't send type?

Hello,
I'm having a problem with answering inline queries.
Library version is 4.0.0-RC1.
System information:
 ~/testproject $ uname -a
 FreeBSD scaladev 11.1-RELEASE-p10 FreeBSD 11.1-RELEASE-p10 #0: Tue May  8 05:21:56 UTC 2018     root@amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC  amd64
 ~/testproject $ scala -version
 Scala code runner version 2.12.6 -- Copyright 2002-2018, LAMP/EPFL and Lightbend, Inc.
 ~/testproject $ java -version
 openjdk version "1.8.0_172"
 OpenJDK Runtime Environment (build 1.8.0_172-b11)
 OpenJDK 64-Bit Server VM (build 25.172-b11, mixed mode)

sbt version is 1.0.
This is the whole code (things are named like that because I'm just starting to try out things):
 import com.bot4s.telegram.api.declarative.InlineQueries
 import com.softwaremill.sttp.okhttp.OkHttpFutureBackend
 import com.bot4s.telegram.clients.SttpClient
 import com.bot4s.telegram.methods._
 import com.bot4s.telegram.models._
 import slogging.{LogLevel, LoggerConfig, PrintLoggerFactory}

 class EchoBot(val token: String) extends TelegramBot with Polling with InlineQueries {
   LoggerConfig.factory = PrintLoggerFactory()
   LoggerConfig.level = LogLevel.TRACE

   onInlineQuery { implicit q =>
     val results = Seq(
       InlineQueryResultArticle("1", "Klingt lustig",
         inputMessageContent = InputTextMessageContent("Klingt lustig")))
     answerInlineQuery(results, Some(60))
   }

   implicit val backend = OkHttpFutureBackend()
   override val client: RequestHandler = new SttpClient(token)
 }

 object Hello extends App {
   new EchoBot("<bot token>").run()
 }

When the bot receives an inline query, the output looks like this:
 [trace, com.bot4s.telegram.clients.SttpClient] REQUEST c529aba4-79d6-4cca-87eb-cb8c9d9f8a77 AnswerInlineQuery(1302304079610336554,List(InlineQueryResultArticle(1,Klingt lustig,InputTextMessageContent(Klingt lustig,None,None),None,None,None,None,None,None,None,article)),Some(60),None,None,None,None)
 [error, com.bot4s.telegram.clients.SttpClient] RESPONSE c529aba4-79d6-4cca-87eb-cb8c9d9f8a77 java.util.NoSuchElementException: Status code 400: {"ok":false,"error_code":400,"description":"Bad Request: can't find field \"type\""}

I don't actually know if this is a problem with the library, but I think it might be. If it's a user error, then I'm sorry and would like to know how to do it properly.
Thanks!

Thanks for the excellent bug report!
Indeed circe encoding for sealed traits hierarchies breaks the expected JSON structure, note that this is a just a residual bug due to the migration from json4s to circe.
A fix already landed in 491d5cdfe90bb9603154f8a8f5040944a347d5d8 please do report any further bugs.


Expose cached path

This is an attempt to expose the cached file such that it can be saved by the application.
It only works on iOS (for now).
What do you think?

Oh, now I see that you're working on the media-cache branch.
Any idea when that will be merged?


KeyValueStoreBackend.get_many ignores timeout

celery.backends.base.KeyValueStoreBackend seems to ignore its timeout parameter, though it does perform a pooling loop using the interval param.

Where does it ignore the timeout?

doh, sorry : the get_many method.  I edited the issue title to reflect.

Thanks!  I fixed the issue with the above patch, does that work for you?


Change License for OpenSource

Currently the license file in repo and packages lists Extreme Workflow Composer EULA, including Homepage: https://www.extremenetworks.com/product/workflow-composer/ and other Extreme Networks references. This applies to repository descriptions and READMEs.
This should be changed to Apache 2 OSS license by someone from Extreme that open-sourced it.
Same for the Copyright record in every file which doesn't list Apache 2 license, example: https://github.com/StackStorm/st2flow/blob/master/modules/st2-login/login.component.js

I recommend we archive this repo and make these license changes in this PR:
https://github.com/StackStorm/st2web/pull/759#discussion_r435280741

Yeah, I agree with you that st2flow archival and moving the code into st2web is the best option that may simplify operations, management and even migration :+1:
However before re-using st2flow code, original (this) repo should have the OSS license first. Same as https://github.com/StackStorm/st2-enterprise-rbac-backend/issues/32#issuecomment-635574887

gotcha, so:

Resolve this issue
do the same for https://github.com/StackStorm/st2web/pull/759
merge https://github.com/StackStorm/st2web/pull/759
deprecate st2flow
explore the future (like st2flow-components for example)

..something like that?

@armab @m4dcoder
What do we want the licenses to be?
The easiest path is to replicate what st2web is doing:
license
https://github.com/StackStorm/st2web/blob/master/LICENSE
Readme
https://github.com/StackStorm/st2web/blob/master/README.md#copyright-license-and-contributors-agreement
js files
https://github.com/StackStorm/st2web/blob/master/modules/st2-action-reporter/action-reporter.component.js#L1
still has

Copyright 2019 Extreme Networks, Inc.

but also has apache license, version 2.0 stuff
css files
no analogy in st2web that I could see.  would do:
/*
Copyright 2019 Extreme Networks, Inc.

Licensed under the Apache License, Version 2.0 (the "License");
you may not use this file except in compliance with the License.
You may obtain a copy of the License at

    http://www.apache.org/licenses/LICENSE-2.0

Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an "AS IS" BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
*/

For st2flow license transition from closed-source proprietary to open-source Apache 2.0.
Existing st2web https://github.com/StackStorm/st2web/blob/master/modules/st2-action-reporter/action-reporter.component.js#L1
+
Existing st2flow https://github.com/StackStorm/st2flow/blob/master/modules/st2-style/colors.css#L2
The resulting Apache 2.0 header will look the following:
// Copyright 2020 Extreme Networks, Inc.
//
// Licensed under the Apache License, Version 2.0 (the "License");
// you may not use this file except in compliance with the License.
// You may obtain a copy of the License at
//
//     http://www.apache.org/licenses/LICENSE-2.0
//
// Unless required by applicable law or agreed to in writing, software
// distributed under the License is distributed on an "AS IS" BASIS,
// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
// See the License for the specific language governing permissions and
// limitations under the License.

And yes, Apache 2.0 LICENSE file is the same across the repositories.


irregular external granule cell layer [MP:0000874]

The name of this term (irregular external granule cell layer [MP:0000874]) is easily confused with the parent term abnormal cerebellum external granule cell layer morphology [MP:0000872]. The definition specifies that it's the thickness that's irregular.
Consider renaming the term to irregular external granule cell layer thickness.
Reported by: michknow
Original Ticket: obo/mammalian-phenotype-requests/1838

modified term name to include thickness


Add View Count + Read Time Feature

Add a View Count feature that will display the number of times any Blog Post has been viewed.
On the index.html page, each post should have an eye icon along with an integer that displays the number of views on that post.
Add a Read Time feature that calculates the read time of any post and displays it on the UI, similar to that on medium.com

@diyajaiswal11 for the no of views on a post, i was thinking of adding an additional attribute for blog model which will store the no. of views and increment it by 1 every time, post_detail request is made.
what do you think is it a good idea to work for this issue?

@diyajaiswal11 i would like to work for this issue

@diyajaiswal11 Can u assign me this issue?

@diyajaiswal11 For the read time feature, will the author of the blog set the read time, or will it be automatically generated(using some other package)?

@diyajaiswal11 For the read time feature, will the author of the blog set the read time, or will it be automatically generated(using some other package)?

Sure @SubhradeepSS , Go ahead.

@diyajaiswal11 For the read time feature, will the author of the blog set the read time, or will it be automatically generated(using some other package)?

@SubhradeepSS , You can use this -  from .utils import get_read_time . Please study about this, and let me know if you've a doubt.


fob, drudgers

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.4
logical conflict every: 100
sleep for: 300s
[pullrequest]
requests per hour: 30
deps=[d,f]

/trunk merge


Use GNUInstallDirs; put uhdm and capnp into same lib dir.

@timkpaine this unifies the way we do lib directories in Surelog and UHDM.


Add touch support

I took the liberty of making a PR of this, @arist0tl3!

Just realised pointer event handlers are not supported by Safari, so will try to get https://github.com/alexanderwallin/react-player-controls/tree/touch-slider working instead.


issue: Timeout failure on restart

Thanks for making the addon.
I've started learning elasticsearch for Drupal and thought I would try this addon too.
I have ElasticSearch in Drupal via the official addon for DDEV.
I tried to add this addon too with the following command: ddev get janopl/ddev-kibana
However, when I restart DDEV, I get the following error:
Failed to start elasticsearch-d94-demo: container(s) failed to become healthy before their configured timeout or in 120 seconds. This may be just a problem with the healthcheck and not a functional problem. (container /ddev-elasticsearch-d94-demo-kibana is unhealthy: )

When I run ddev logs -s kibana, I
...
{"type":"log","@timestamp":"2022-09-28T03:27:26+00:00","tags":["info","status"],"pid":7,"message":"Kibana is now available (was degraded)"}
{"type":"log","@timestamp":"2022-09-28T03:27:29+00:00","tags":["info","plugins","reporting","chromium"],"pid":7,"message":"Browser executable: /usr/share/kibana/x-pack/plugins/reporting/chromium/headless_shell-linux_x64/headless_shell"}agent":"curl/7.68.0","accept":"*/*"},"remoteAddress":"<IP_ADDRESS>","userAgent":"curl/7.68.0"},"res":{"statusCode":302,"responseTime":6},"message":"GET / 302 6ms"}
...

The last message appears about 20-30 times or so. I'm not familiar with kibana so I'm not sure if this is expected behavior or not.

Hi
Sometimes kibana container has some issue with healthcheck parameter in docker compose file
you can also check if kibana is boot up correctly to check kibana api status.
first you need comment or remove healthcheck section in docker-compose.kibana.yaml and boot up your project
there is an address to check the kibana status http://<your-project-name>.ddev.site:5601/api/status
it should return status for all plugins and kibana herself and should be something like "state": "green" especially in "overall" section in response body
you can increase healthcheck values for interval and timeout in file "docker-compose.kibana.yaml" and check if this resolve your issue
from:
    healthcheck:
      test: [ "CMD-SHELL", "curl --fail -s localhost:5601" ]
      interval: 30s
      timeout: 10s
      retries: 3

to:
 healthcheck:
      test: [ "CMD-SHELL", "curl --fail -s localhost:5601" ]
      interval: 60s
      timeout: 30s
      retries: 3

if this doesn't help, you can modify healthcheck test to
    healthcheck:
      test: [ "CMD-SHELL", "curl  --fail -s \"http://localhost:5601/api/status\" | grep 'Looking good'" ]
      interval: 60s
      timeout: 30s
      retries: 3

after start project you should have in kibana container logs something similar to this
{"type":"response","@timestamp":"2022-09-28T14:27:27+00:00","tags":["api"],"pid":7,"method":"get","statusCode":200,"req":{"url":"/api/status","method":"get","headers":{"host":"localhost:5601","user-agent":"curl/7.68.0","accept":"*/*"},"remoteAddress":"<IP_ADDRESS>","userAgent":"curl/7.68.0"},"res":{"statusCode":200,"responseTime":4,"contentLength":24697},"message":"GET /api/status 200 4ms - 24.1KB"}

Let me know if the above suggestions help you then I will make changes to the repo.


player cannot ride entity (boat, minecraft, etc) on skyblock world

player cannot ride entity (boat, minecraft, etc) on skyblock world

I need more reproduction steps

https://youtu.be/WnE6hF1t-nY
except the default world is allowed to ride the entity.
The rest of the world can't be ridden, it automatically pushes me down on right click

That sounds like the empty chunks were trimmed and aren't regenerating, or were generated as entirely empty?


Difference between docs and  and help pages and expected behavior

TL;DR
Running command with -dry_run=true command results in failure. Docs show that command is -dry_run=true command that works is -dry-run=true
Help page also shows that the proper command is -dry-run
Expected behavior
-dry-run=true should be changed in docs
Observed behavior
-dry_run=true does not work
Debug log output
docker run -it us-docker.pkg.dev/gcr-cleaner/gcr-cleaner/gcr-cleaner-cli -repo=gcr.io -dry_run=true
flag provided but not defined: -dry_run
Usage of /bin/gcr-cleaner-cli:

  Deletes untagged or stale images from a Docker registry.

Additional information
No response

Hi @grabango-ttharp
None of the documentation in this repo suggests using "dry_run=true" on the CLI. I believe you're referring to the Server Payload & Parameters, which has the following warning at the top:

⚠ This section is for the server payload. If you are using the CLI tool, run gcr-cleaner -h to see the list of flags and their descriptions.

As the warning implies, please run gcr-cleaner -h to see the full list of CLI flags and that pertain to the version of gcr-cleaner that you have downloaded.


cannot build with ghc 8.2-rc (GHC.TcRnExprMode)

PATH=/opt/ghc/ghc-<IP_ADDRESS>70507/bin:$PATH cabal install hint --allow-newer
...
Configuring hint-0.6.0...
Building hint-0.6.0...
Preprocessing library hint-0.6.0...
...
[11 of 19] Compiling Hint.Typecheck   ( src/Hint/Typecheck.hs, dist/build/Hint/Typecheck.o )

src/Hint/Typecheck.hs:46:12: error:
    • Couldn't match type ‘[Char]’ with ‘GHC.TcRnExprMode’
      Expected type: String -> m (Maybe GHC.Type)
        Actual type: GHC.TcRnExprMode -> m (Maybe GHC.Type)
    • In the expression: fmap Just . GHC.exprType
      In an equation for ‘exprType’: exprType = fmap Just . GHC.exprType
   |
46 | exprType = fmap Just . GHC.exprType
   |            ^^^^^^^^^^^^^^^^^^^^^^^^

src/Hint/Typecheck.hs:46:24: error:
    • Couldn't match type ‘m0 GHC.Type’ with ‘GHC.Type’
      Expected type: GHC.TcRnExprMode -> m GHC.Type
        Actual type: GHC.TcRnExprMode -> String -> m0 GHC.Type
    • In the second argument of ‘(.)’, namely ‘GHC.exprType’
      In the expression: fmap Just . GHC.exprType
      In an equation for ‘exprType’: exprType = fmap Just . GHC.exprType
   |
46 | exprType = fmap Just . GHC.exprType
   |                        ^^^^^^^^^^^^

This is fairly standard - each new major GHC release tends to break hint in some way. That's why the codebase adapts to different GHC versions.
If you look at the commits made around when 8.0 came out, you'll see examples. If you look into it and come up with a patch, I'll be happy to review. I don't think I'll look into it until 8.2 is released.

Please test master with 8.2. I'll wait a few days before doing a release.

This is hardly a comprehensive test, but mueval seems to work fine with ghc-8.2-rc2.

@int-e thank you - it's been more than two weeks, so I'll just do a release now.


Add SNI with DTLS tests to ssl-opt.sh script

This PR adds 3 tests for SNI with DTLS to the script ssl-opt.sh.
The change is related to IOTSSL-1114.

@sbutcher-arm

@gilles-peskine-arm: The initial 3 tests in SNI/DTLS are copies of the original SNI/TLS tests. There were only 3 because the idea was to do a quick check rather than duplicate the whole tests as the SNI functionality is mostly shared. I have now copied the missing SNI/DTLS into SNI/TLS.

I have created backports for this PR:

Mbed TLS 2.7: https://github.com/ARMmbed/mbedtls/pull/1664
Mbed TLS 2.1: https://github.com/ARMmbed/mbedtls/pull/1665

retest

Marked “ready for merge”. We need new Jenkins results because the logs of the old run have been deleted but the backports pass and it's been tested manually so it's good enough to merge to -proposed at this point.


Bug: My Cart

I add a product in my cart with user x
when I log out from user x
A product is still displayed in the cart

This is the same issue as the cart not clearing in the cache after a successful order @RamRamez

@ahmadabugosh we have two sign in and sign out method in the app. Sign in with wallet and sign in with username and password. What is the desired behavior when user signs out of each one?

@RamRamez I think those are two separate issues. The main thing for this issue is to clear the cart once an order goes through.
The two sign in options are separate for now, the shopify one lets you view the orders and the wallet one lets you connect your wallet to customize your ENS name.

@maryjaf since people could check out as a guest, we don't need to delete cart items on log out


Add VexFlow definitions

These are the definitions for [VexFlow 1.2.27] (http://vexflow.com).
I added comments at points where the API is inconsistent to facilitate refactoring if the API changes.

Thank you for proof-reading! I just implemented the changes you suggested.

Thanks! :+1:

vexflow/vexflow.d.ts
check list

[ ] is collect naming convention?

https://www.npmjs.com/package/vexflow
http://bower.io/search/?q=vexflow
others?

[ ] has a test file? (vexflow/vexflow-tests.ts or others)
[ ] pass the Travic-CI test?

I went over the definitions again and added the test file (don't know how I could miss that). Everything should be good now!


Cleaner use of regexes for things that don't allow whitespace

The tree-sitter DSL function seq(...) allows arbitrary whitespace between terms. One upshot of this is that : test would have potentially parsed as a valid symbol, since we used seq(':', choice(...))
This is not only not valid, but it creates unnecessary ambiguity for things like type annotations.
Relatedly, anything that was using identifierRegex as part of a seq(...) had the problem (this was pretty common, because generally we needed to express things like "an identifier that begins with an uppercase letter or an underscore").

Oh this is really cool


Shorten location names for Alexa to say

As of right now, there are long location names being stored in the database and different versions of the same name. For example, here are ways that the Green Music Center is listed in the database:

Green Music Center | 1141 (Musician's Lounge), Green Music Center | Joan and Sanford I. Weill Hall, Green Music Center - Weill Hall Lobby
Green Music Center | Joan and Sanford I. Weill Hall, Green Music Center - Weill Hall Lobby
Green Music Center | Schroeder Recital Hall Lobby, Green Music Center | Schroeder Hall

They are slightly different, but the user is probably only going to care about the event being at the Green Music Center and would not want to hear the entire location being read (especially since some are repetitive). On the other hand, for some buildings, the user would probably want to know the specific location listed, such as whether something is in Ives 76 or Ives 101.
The goal is to come up with a way to shorten long names to what the user would likely want to hear. Not all location names should be shortened, but some (like the green music center example) should be. See the suggestions listed below for doing this.

Possible solutions:

Add a new column or lookup table to the database to store the way Alexa should say things. We would manually have to enter the way we want her to say location names, but since there are a limited number of locations around the campus, it would probably be low maintenance in the future once most of them are stored.
Create a method to look at the location name, and if it contains a certain string, then replace the entire name with the simplified name before Alexa says it. For example, it could look through the location to see if it contains "Green Music Center", and if it does, just replace the entire string that will be used as part of our response with "Green Music Center".

This functionality would ideally be implemented in the database in order to minimize the latency of our responses. The additional table or column approach would be fairly straightforward, but the search and replace method might be more appropriate or scalable.
I'm in the process of checking what language extensions I can install on Amazon RDS to make the task more approachable.

Another thing that comes to mind on this is that I noticed some of these locations are actually a comma-separated list of different rooms at the same location. We could potentially break the locations down into buildings and rooms, by altering the schema as such and tweaking the scraper to break the field apart for us.

I think creating columns for SSML marked-up versions of the locations (as well as event types and categories eventually) would be easiest, at the possible expense of some duplication of information.
On the other hand, a series of transformations approach could transform a location into something sensible and the result of that could pass through a function that transforms words Alexa has trouble with into SSML marked-up versions. The "pronunciation function" would be reusable for any field, and different versions of the first function could be made for any field.
For example, to apply the same process to the event descriptions, we would make a function that strips the HTML tags (and any other transformations we need to get a presentable string), then that string would pass through the pronunciation function.
The decision can be up to whoever wants to tackle the problem, but I suspect the latter is more challenging and more interesting. The first solution would be tedious but simple enough.
We should get the rest of the calendars in the database before deciding either way, so this issue is blocked by #5

Shortened responses where necessary.

This was merged as #74


Analysis of newsletter promo (deployed 22/1/20)

We think that
Users are not signing up to the newsletter because:-

it's confusing
it blends into the footer

Therefore we hypothesise that
If we change the background and simplifying the sign up process, users will find the newsletter promo more attractive and easier to understand.
As measured by
Visit numbers on GA
We are right if
Visits have increased following deployment compared to baseline levels during 2019 up to the day before deployment

https://github.com/wellcomecollection/wellcomecollection.org/issues/2703#issuecomment-580128068

Unique page views of /newsletter have neither increased in terms of numbers nor in terms of percentage of unique views.  For discussion at User and Data meeting on 24/2.

Sharepoint documents:
https://wellcomecloud.sharepoint.com/:w:/r/sites/wcdigitalexperience/Shared Documents/Analytics/5108 Analysis of newsletter promo deployed 22Jan 2020.docx?d=wbbd46c13d3a24bf0af15da5cc19a16eb&csf=1&e=aGVSXA
https://wellcomecloud.sharepoint.com/:x:/r/sites/wcdigitalexperience/Shared Documents/Analytics/5108 newsletter analysis.xlsx?d=waa7a48328983494e8c145591c9467f32&csf=1&e=gPNVBm

We'll go with option B as that allows for signing up for particular newsletters from particular pages i.e. teachers and schools newsletter on schools page https://wellcomecollection.org/pages/Wuw2MSIAACtd3StS

Conclusions:

Numbers of signups have increased due to implementation of suggested single stage signup

While A/B testing did not find one version to be more effective than the other in driving signups, Version B was agreed to be deployed as this provides more flexibility for audience-specific signups by page (eg Youth signup on Youth pages) Link to A/B testing here:
https://datastudio.google.com/open/1aDfsiJqf71YKZZMwFTOB6LoW01bRqCjn

Analysis of Dotdigital data shows numbers of signups increasing steadily regardless of the newsletter promo redesigns

Dotdigital data also shows a slowly increasing number of unsubscribes.

These conclusions have been shared with Lynn Huynh, Marketing.


CNI 0.2.x / Mesos :   Mesos GSG documentation

For Cilium v0.10 release announcement.
CNI 0.2.x / Mesos :   Mesos GSG (cynthia in progress)

@tgraf Is there something specific with "CNI 0.2.x" that enables Cilium with Mesos? With the Mesos GSG done, do we want to do a blog post and perhaps get into the details of why CNI 0.2.x enables Cilium with Mesos? I think this was initially targeted as a Release Announcement.

Mesos GSG live as of 8/30/2017:
http://docs.cilium.io/en/latest/gettingstarted/#getting-started-using-mesos


[Enhancement] Ability to change layer/export order.

So I like if I could flip the order of layers when exporting, as I used the 'Renamed' procedure but my layers are in descending order, so my exported layers are numbered in reversed...
I have a batch naming tool so it isn't a big problem, but it would be nice to be able to flip the order.

If you use the image[001] pattern, you can instead type image[000, %d], which will number the layers in reversed order.

Noted I try it next time I need to export.
I'll leave this issue open for others that might need it.

It's custom syntax I made for the plug-in, documented here. The % arguments are hard-coded and specific to each field.
If you need more customization, the [replace] field might be of use, which uses the Python regular expression syntax. It's also possible to chain multiple Rename procedures if case you need to use regular expression substitution multiple times.


chore(main): release 1.9.0

:robot: I have created a release beep boop
1.9.0 (2023-04-15)
Features

Implement subset of crypto.subtle.importKey which can import a JSONWebKey using RSASSA-PKCS1-v1_5 (b66bf50)
Implement subset of crypto.subtle.sign which can sign data with a JSONWebKey using RSASSA-PKCS1-v1_5 (800fb66)
Implement subset of crypto.subtle.verify which can verify a signature with a JSONWebKey using RSASSA-PKCS1-v1_5 (077adfd)

Bug Fixes

free buf if an error has occured (bfa84cc)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/fastly/js-compute-runtime/releases/tag/v1.9.0 :sunflower:


Fix: New log formats not being displayed

As I was testing the image on my local cluster, i noticed that the formatting I've setup in my previous PR hasn't taken effect.
This is because when we ask for a new logger, it doesn't come with any handlers.
The solution to this is to use logging.basicConfig upon package instantiation.
I know that we previously discussed this, but I said it was a problem if we put it in __main__.py as it'll only be available when the server is launched, and not if it's used as a package. And I don't know why I didn't think about putting it in the package's __init__.py .
@supakeen I know i've kep the get_logger method even though it does practically nothing.
I just wanted to reduce the changes and also let room for extra setup if we're ever going to do that.
Also, what do you think about making the log level configurable ?

@shtlrs It should already be configurable, you can call setup_logging from here: https://github.com/supakeen/pinnwand/blob/master/src/pinnwand/command.py#L30

@shtlrs It should already be configurable, you can call setup_logging from here: https://github.com/supakeen/pinnwand/blob/master/src/pinnwand/command.py#L30

@supakeen it's only configurable via the CLI there. Not when used as a package.
What i meant to say is, we can make it configurable via a debug that'll log at debug level when developing and at INFO level (min) in production.
Then if someone wants to suppress that, they could using that option.


Bug in last version (str / list in interface keyword)

Hi,
I decided to upgrade my dask-jobqueue module. Now, I get some strange bug with this simple code:
from dask_jobqueue import PBSCluster
c=PBSCluster()

Here is the error:

TypeError                                 Traceback (most recent call last)
 in
1 from dask_jobqueue import PBSCluster
----> 2 c=PBSCluster()
~/conda-env/RSSS/lib/python3.6/site-packages/dask_jobqueue/pbs.py in init(self, queue, project, resource_spec, walltime, job_extra, **kwargs)
69
70         # Instantiate args and parameters from parent abstract class
---> 71         super(PBSCluster, self).init(**kwargs)
72
73         # Try to find a project name from environment variable
~/conda-env/RSSS/lib/python3.6/site-packages/dask_jobqueue/core.py in init(self, name, cores, memory, processes, interface, death_timeout, local_directory, extra, env_extra, log_directory, walltime, threads, python, **kwargs)
220
221         if interface:
--> 222             extra += ['--interface', interface]
223             kwargs.setdefault('ip', get_ip_interface(interface))
224         else:
TypeError: must be str, not list
I did not change anything in my config yaml file :

jobqueue:
pbs:
name: dask-worker
# Dask worker options
cores: 56
processes: 28
memory: 120GB
interface: ib0
death-timeout: 900 # should be large if many workers are launched
local-directory: null

# PBS resource manager options
queue: mpi_1
project: SKIM
walltime: '24:00:00'
extra: ""
env-extra: []
resource-spec: select=1:ncpus=28:mem=120GB
job-extra: ['-m n']

Hi,
Sorry for the trouble, there has been a small breaking change in #160. You should replace
extra: ""

By
extra: []

Hi Guillaume,
Thanks. Now it works. What was strange is that the error was about the "interface" keyword and not the "extra" one even if the interface was a str.


LOGIN ERROR but no keychain entry found

One of my users is having trouble logging in. She is getting the following error:
%gimme-aws-creds
Stored password is invalid, clearing.  Please try again
LOGIN ERROR: Authentication failed | Error Code: E0000004
I understand this is to be expected if the password stored in keychain is wrong. However:
1)She was unable to find a keychain entry when searching for gimme-aws-creds
2)The error persisted even after multiple attempts until, the error changed to a lockout message
I looked at the okta logs and the attempts also show an incorrect password, so I don't think this is a connection failure.
I think this may be the same problem this comment (https://github.com/Nike-Inc/gimme-aws-creds/issues/160#issuecomment-1031087069) refers to, but it's unclear since the commenter doesn't follow up at all
Expected Behavior:
Either 1)The user is prompted to enter a new password after a 2nd run of the command, or
2)A keychain entry is found when searching for "gimme"
App Version used: 2.4.4 installed via homebrew
Environment name and version: terminal
Operating System and version: MacOS 11.7

I found the solution: run unset OKTA_PASSWORD and the rerun gimme-aws-creds


Json Schema doesn't autocomplete when setting the color scheme in VS Code

Environment
Windows build number: Microsoft Windows [Version 10.0.18363.778]
Windows Terminal version (if applicable): 0.11.1191.0

Any other software?
VS Code

Steps to reproduce

Open Settings from the About Page and see it launch in VS Code.
Define "colorScheme" to use a color scheme listed in defaults.json. Watch as Code refuses to do autocomplete for it.
Expected behavior

I expect the auto-complete to supply a list of color schemes listed in defaults.json that narrows as you start typing. For example, if the first letter I choose is "T", I'd expect all options that start with the letter T to appear in the helpful drop-down list (the newly added Tango schemes in this case.)
Actual behavior

You need to manually type it or copy/paste the name from defaults.json.

This might be possible for the built-in themes, but I can't imagine that it would be possible to get this auto-complete behavior for schemes that the user has added

Yes, I'm thinking anything in defaults.json ought to be able to get IntelliSense. The user is on their own for any custom schemes.

but I can't imagine that it would be possible to get this auto-complete behavior for schemes that the user has added

// Add custom color schemes to this array.
    // To learn more about color schemes, visit https://aka.ms/terminal-color-schemes
    "schemes": [],

Actually now that I think about it, before "colorScheme" is set, if "schemes": [] is configured, then we ought to be able to use what's defined there to allow "colorScheme" to get IntelliSense. VSCode does this when you write code that is intended to be re-used later on such as a variable. We should be able to take advantage of that.

We would need an entire LanguageServer to get VSCode to suggest existing schemes. That’s just not something the schema can do, and it’s not something we’re likely to do. Great VSC extension idea!

Probably there should be a way to get the TS/JS language server to help with json. Red Hat puts out a YAML extension though so it could go either way. I'll file a feature request on their side for it.

I mean, I think the JS/TS language servers do help with JSON, by way of the schema. Since there’s no schema-approved way to set dependent values and implement dynamic sets or say that you need to parse TWO json files instead of just the one, it’s just not something a generic language server or schema can do. It needs to be specific to the terminal settings format just so that it can actually give you contextual feedback.

I think it's reasonable to only be able to parse through settings.json. If users create a separate json for settings, probably via extension, it would be on the extension to ensure the schema registers that json instead of the regular settings.json (It really ought to just overwrite the original and ensure it stays synced to any changes made to settings.json.

You can always add jq as a dep for json parsing. That is exactly what it's intended to do and it does it well (and it available for Windows, not just Linux unlike sed, awk, gawk, etc.)

Sorry, it’s just not terminal’s job. This is really good stuff to capture for VSC though

The action still here is reading the schemes from default.json. The schema can do that.

The schema causes warning (Incorrect type String expected) when using (valid):
              "colorScheme": { "light": "Solarized Light", "dark": "Solarized Dark" },

Not sure if it's already fixed.


Unable to manually build projects if pull request plugin is filled out.

If I attempt to build a project manually and have the pull request plugin enabled I get the following error:
Last Built Revision: Revision 6daa227a0bb360c2e330d20d1bd10c3babed2fa8 (detached)
Fetching changes from 1 remote Git repository
Fetching upstream changes from git@github.com:JenRed12/utui.git
No candidate revisions
ERROR: Couldn't find any revision to build. Verify the repository and branch configuration for this job.
Finished: FAILURE
This was working correctly with public repos last week but seems to no longer work since I updated to new version this morning. It does not work for public or private repos.

Was there a solution found for this one? I'm getting the same issue.


Nameraka society

This summer I became aware of the work of Suzuki Ken on Nameraka Society and its Enemies, which is only in Japanese, but which is closely related to our work.  It deserves mention in Part 3 of the book, especially 3-2 and 3-3 as it is a clear precedent and cultural resonance for our book in the Japanese context.  It also serves as a way to connect the work to Deming.

 Gov4Git notices
On Thursday, 29-Aug-24 16:38:13 UTC by Gov4Git dev
Notice yk5nlt
Started managing this issue, using the Plural Management Protocol v1,  as Gov4Git concern 1001 with initial priority score of 0.000000.
This project is managed by Gov4Git, a decentralized governance system for collaborative git projects.
To participate in governance, install the Gov4Git desktop app.
Notice xnhseu
This issue's priority score is now 0.000000.
The cost of priority is 0.000000.
The projected bounty is now 0.000000.
Notice gsmga5
The set of eligible proposals claiming this issue is empty.

@Taiyou will request to join community and PR.


fsttest: discard header changes after send

This should correctly ignore headers set too late to make it into the response.

Updated to address feedback. PTAL


[Android] Support React Native v0.60

Remove LocationModule on Android, it's no longer live on RN >= 0.60
Override versions with root project for support AndroidX
Support use Hermes JS engine on react-native-threads (If not, it will get error of jscexecutor.so not found with enableHermes: true)

/cc @Traviskn

Thanks for the PR, we'll test this out soon 👍

An issue is the host sometimes doesn't not received ThreadSelfManager.postMessage with hermes -emit-binary for worker bundle, I've to use setTimeout(() => ThreadSelfManager.postMessage('init'), 100) to solve issue.
I think the reason is the Hermes compiler speeds up the startup time of worker, it may faster than the preparation of thread bridge.

any news on this?

@jhen0409  I use react-native0.60.3, the PackageList is auto generate by react-native. The RNThreadPackage.java constructor need incoming parameter ReactNativeHost, but in PackageList no put  the parameter into.

@ jhen0409 я использую среагировать-native0.60.3, то PackageList является автоматической генерации по реакции родной. RNThreadPackage.java конструктор не нужен входящий параметр ReactNativeHost , но в PackageList не поставить параметр в.

@jhen0409 I use react-native0.60.3, the PackageList is auto generate by react-native. The RNThreadPackage.java constructor need incoming parameter ReactNativeHost, but in PackageList no put the parameter into.

The same issue

@biduone @neller1, if you're used autolinking, you should disable it for react-native-threads and link it manually. You can read the doc: How can I disable autolinking for unsupported library?

Thank you for your answer, but after switching to manual link I have the same error ( Can you write me in skype (alex.stacheev)? Thank you!!!
Frady


"Teleac" is listed in the drop-down menu

Description:
"Teleac" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Teleac" in the search bar.

Expected results
The location is listed in the drop-down menu as "Teleac, Alba (Ciugud)".


bump aiobotocore to 1.4.2

bumped aiobotocore to 1.4.2 and updated the ci to point to a yml file (with aiobotocore==1.4.2).
In discovery of https://github.com/fsspec/s3fs/pull/553 when working on a VM I got a botocore.exceptions.NoCredentialsError: Unable to locate credentials when I installed s3fs using conda. The tail of the Trackback looks like:
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/fsspec/asyn.py", line 91, in wrapper
    return sync(self.loop, func, *args, **kwargs)
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/fsspec/asyn.py", line 71, in sync
    raise return_result
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/fsspec/asyn.py", line 25, in _runner
    result[0] = await coro
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/s3fs/core.py", line 1128, in _isdir
    return bool(await self._lsdir(path))
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/s3fs/core.py", line 580, in _lsdir
    async for i in it:
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/aiobotocore/paginate.py", line 32, in __anext__
    response = await self._make_request(current_kwargs)
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/aiobotocore/client.py", line 141, in _make_api_call
    http, parsed_response = await self._make_request(
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/aiobotocore/client.py", line 161, in _make_request
    return await self._endpoint.make_request(operation_model, request_dict)
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/aiobotocore/endpoint.py", line 77, in _send_request
    request = await self.create_request(request_dict, operation_model)
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/aiobotocore/endpoint.py", line 70, in create_request
    await self._event_emitter.emit(event_name, request=request,
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/aiobotocore/hooks.py", line 27, in _emit
    response = await handler(**kwargs)
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/aiobotocore/signers.py", line 16, in handler
    return await self.sign(operation_name, request)
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/aiobotocore/signers.py", line 63, in sign
    auth.add_auth(request)
  File "/opt/userenvs/ray.bell/test_env2/lib/python3.9/site-packages/botocore/auth.py", line 373, in add_auth
    raise NoCredentialsError()

However, when installing from pip which grabbed aiobotocore 1.4.2 I was able to do pd.read_parquet("s3://bucket/file.parquet"). This solves my use case and I hope doesn't break anything for others.

Sorry if I'm being dense, but does this now actually install the local version of s3fs? Also, I notice lines like this apparently changing the base python version in the environment, which doesn't seem like a great idea. That particular line installs py39, even though it's the py38 run.

Sorry if I'm being dense, but does this now actually install the local version of s3fs? Also, I notice lines like this apparently changing the base python version in the environment, which doesn't seem like a great idea. That particular line installs py39, even though it's the py38 run.

Thanks for the comments. I agree more thought is needed for the best way to do this. I added a comment on an issue to move the convo there (https://github.com/fsspec/s3fs/issues/528).
Opened up https://github.com/fsspec/s3fs/pull/555 as a minimal example example of what i'm trying to achieve here.
Thanks for the discussion here. I'm going to close this one as I feel it the changes to ci.yml file too much.

Pinning aiobotocore to 1.4.2 depends on botocore 1.20, but up to date versions of boto3 need botocore >= 1.23. Hopefully there's a plan here to get s3fs working with up to date versions of botocore?

We tend to consider the current version of aiobotocore at release time; however, a PR bumping the requirement will be gratefully received any time, and hopefully nothing breaks.


[FEATURE] - Document how to deploy MinIO via ArgoCD/GitOps with Helm

Is your feature request related to a problem? Please describe.
This is not related to a problem but to a necesity of helping users in a better way, lately I have seen more and more users using ArgoCD and they all have similar questions when performing the deploy. And all of them want to use helm on top of ArgoCD, during those meetings, I have seen how this is possible and it can work, but I never had a chance to do it my-self, so I just have part of the procedure. At the end, what I am requesting is to start formal documentation on how this can be achieved, so that when next customer comes with same questions, we can simple redirect the customer to read our Documentation on ArgoCD integration with Helm.
Describe the solution you'd like
A clear and concise description of what you want to happen: To have formal documentation on how to deploy MinIO via ArgoCD/Helm.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered: I have heard from some customers, that Kustomize could be an option and even OperatorHub, but at the end all of the customers I have been in touch with, are using just Helm, so if someone knows more from Kustomize and ArgoCD or OperatorHub and ArgoCD, that would be the alternatives.
Additional context
Add any other context or screenshots about the feature request here: I just have a small wiki to show how to use Helm and that has been working for old versions of Operator and MinIO and for new versions as well, this wiki can help get ArgoCD working but it is just half of the equation, as I would like to see ArgoCD part also documented and some screenshots on how this can be used, maybe we can start with some initial tags or places to expose this and then we can share and get feedback from the users: https://github.com/cniackz/public/wiki/How-to-install-MinIO-Using-Helm-in-Kubernetes
Tested locally, you can get steps from:
https://github.com/minio/wiki/wiki/How-to-deploy-MinIO-with-ArgoCD-in-k8s

@kannappanr one thing to follow-up here is on the helm side for tenant deployment. we can in detail talk about values.yaml and document the mapping, but ideally we would find a way to do this via annotations and auto-generating some level of reference. Otherwise it is far too easy for the docs to fall out of sync w/ the core product.


crispy-doom: upgrade 5.8.0 -> 5.9.2 + add manpages

Motivation for this change
Version bump. While doing the version bump I realized manpages were failing to build because python was a missing build dependency, so I added that too.
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)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Upstream upgraded to 5.9.2, so I pushed another update

Result of nixpkgs-review pr 95996 1

1 package built:

crispyDoom

Can you rebase this? I'm getting an odd error during nixpkgs-review.
builder for '/nix/store/61f1rkkvw1bnkx30nd4wilqyw9v3awkk-crispy-doom-5.9.2.drv' failed with exit code 1; last 6 log lines:
  unpacking sources
  unpacking source archive /nix/store/rpwp850rqim6c9b3wr4v5qrvjmlc6ca8-source
  source root is source
  patching sources
  /nix/store/333six1faw9bhccsx9qw5718k6b1wiq2-stdenv-linux/setup: eval: line 83: syntax error: unexpected end of file
  builder for '/nix/store/61f1rkkvw1bnkx30nd4wilqyw9v3awkk-crispy-doom-5.9.2.drv' failed with exit code 2
cannot build derivation '/nix/store/6m02m5g1fa99a6rf8j9lj60416y7rv89-env.drv': 1 dependencies couldn't be built

Okay odd, I rebased it onto master and I'm getting the same error. Some dependency must have changed and broke the build. I'll look into it...

Okay it was my mistake, I missed a semicolon when squashing the lines down in my script. Fixed and pushed.


Add support for Laravel 5.3

Laravel 5.3 is officially out. Would be great to have this PR merged as we want to craft a 5.3 app with Dingo.

Definitely something I'm interested in, but currently want to nail down the issue people are having in regards to 5.1, before adding another version to support.

@hskrasek my company would need to upgrade to Laravel 5.3 within this 1 to 2 week because we need to start supporting laravel/passport (which only support 5.3). I would very much like to NOT have to maintain a fork to handle this.

I have upgraded to Laravel 5.3
Everything looks fine so far, except this PR need to include https://github.com/laravie/api/commit/51f9c8553efc00b96e552d3c5f281d97272f3e54 due to changes with Laravel Router.

@Kaukov If you could make the change suggested by @crynobone, I'll give this a test soon and merge if we are all good.
If you're busy though, I can make the change myself and merge in the PR from there.

@hskrasek is it ok now?

Hello guys, what should I do to get to work laravel 5.3 with Dingo? I'm getting this error message (gatherRouteMiddlewares..). Thank you.

yebah!

@hskrasek still require https://github.com/dingo/blueprint/pull/43 to be merged in order to allow developer to install on L5.3

still not work
I used php composer.phar require dingo/api:v1.0.*@dev
Problem 1
- dingo/api v1.0.0-beta5 requires dingo/blueprint 0.2.* -> satisfiable by dingo/blueprint[0.2.x-dev] but these conflict with your requirements or minimum-stability.
- dingo/api v1.0.0-beta4 requires dingo/blueprint 0.2.* -> satisfiable by dingo/blueprint[0.2.x-dev] but these conflict with your requirements or minimum-stability.
- dingo/api 1.0.x-dev requires dingo/blueprint 0.2.* -> satisfiable by dingo/blueprint[0.2.x-dev] but these conflict with your requirements or minimum-stability.
- Conclusion: don't install dingo/api v1.0.0-beta3
- Installation request for phpdocumentor/reflection-docblock (locked at 3.1.0) -> satisfiable by phpdocumentor/reflection-docblock[3.1.0].
- Conclusion: remove laravel/framework v5.3.4
- Conclusion: don't install laravel/framework v5.3.4
- dingo/api v1.0.0-beta1 requires illuminate/routing 5.1.* -> satisfiable by illuminate/routing[v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8].
- dingo/api v1.0.0-beta2 requires illuminate/routing 5.1.* -> satisfiable by illuminate/routing[v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.28, v5.1.30, v5.1.31, v5.1.41, v5.1.6, v5.1.8].
- don't install illuminate/routing v5.1.1|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.13|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.16|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.2|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.20|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.22|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.25|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.28|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.30|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.31|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.41|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.6|don't install laravel/framework v5.3.4
- don't install illuminate/routing v5.1.8|don't install laravel/framework v5.3.4
- Installation request for laravel/framework (locked at v5.3.4, required as 5.3.) -> satisfiable by laravel/framework[v5.3.4].
- Installation request for dingo/api v1.0.@dev -> satisfiable by dingo/api[1.0.x-dev, v1.0.0-beta1, v1.0.0-beta2, v1.0.0-beta3, v1.0.0-beta4, v1.0.0-beta5].

@DesmondPang That is because I have not tagged a new beta yet. I'm probably going to soon, but if you want to try it out before than, switch to installing dev-master

"require": {
    "dingo/api": "dev-master"

},
"prefer-stable": true,
"minimum-stability": "dev"

Thank you for your Beta 6 release. but I still got problem with dingo/blueprint. Need to release blueprint 0.2???
Problem 1
- Installation request for dingo/api v1.0.0-beta6 -> satisfiable by dingo/api[v1.0.0-beta6].
- dingo/api v1.0.0-beta6 requires dingo/blueprint 0.2.* -> satisfiable by dingo/blueprint[0.2.x-dev] but these conflict with your requirements or minimum-stability.

@DesmondPang Try it once more, looks like the composer file has been pointed to a tag pattern thats never existed.

@hskrasek successful. Thank you so much.

@hskrasek are you going to tag a new beta soon (in matter of days)? I have big refactoring on the table but I want to create tests first, but can't due to error :) Thank you. Btw. can I help you somehow?

@jakubkratina v1.0.0-beta6 has been tagged an hour or so ago.

@bkintanar: I can see that now, just updated the composer. Great work, thank you. Can I contribute to dingo development?

@jakubkratina opensource is always open for contribution. 👍

I would like to, is here a contribution document? I have found only slack channel. Thank you.

here: https://github.com/dingo/api/blob/master/CONTRIBUTING.md

Plans for passport? #1159


Fix import paths

Hi!  👋 I am very exited about this new library so I gave it a shot! I saw some minor path import issues which I believe are part of the first iterations. Still, I wanted to contribute a bit (maybe related to https://github.com/probml/dynamax/commit/6f26b88af6ba3944d0af7894457c9d5435969b04 ?).
I'll be exploring some application examples which hopefully serve as documentation :)

Hi @juanitorduz . Thanks for your comments. The library is still in a state of rapid change, so we are not yet accepting external PRs. @xinglong-li is working on a major refactor. The plan is to first launch https://github.com/probml/dynamax on ~11/14, and then to release a v1 of sts-jax (which depends on dynamax).

Great! Sure, I understand. I was excited about trying sts-jax out 😅 . Looking forward to the release. ( I will close this PR and https://github.com/probml/sts-jax/pull/2 for now)


Node labels can be defined at two locations in UI

Version: master 9/4
If you hit Advanced Options, you get the option to set Node Labels. In the bottom you have a static part where you can set Labels. This should be one place, or the bottom one needs to be hidden when advanced is clicked as they do not merge.

Version - 2.1 master 9/10
Verified fixed


how to run SQL but not need builder

I have a sql "Select * from user"
How to run this sql and return result same as knex.select().from('user')
Thanks

Duplicate issue (I don't have time to dig up the last issue when this was asked). Check the result that knex.raw() is returning with console.dir(res, { depth: null });.
If I remember correctly that depends on which DB dialect you are using so you might need to have different implementation how to fetch actual rows for each dialect.
Anyways IIRC the attribute  was res.rows where you can find resulted rows with postgresql.


Impose limits on all VM creation

This prevents people from trying to allocate more resources than they have available in total. This isn't the best solution, since it may prevent people from having many VMs with only a few started up, but that's a problem for when users start complaining.

Have you tested this against the method I described in the document

I have not. I was lowkey hoping you could do that for me? 😅 Maybe you could show me how?

Thanks joe.
The frontend still reports success to the user, so we gotta transport that 403 up to it somehow so that it displays an error message.


Car controller

In this milestone, implemented the following:

[ ] Generated the car controller with required actions.
[ ] Generated the requests spec and ensured all the tests are passing.

Hello @MohamedHNoor 👋🏼 ,
Thank you for taking time out to review and approve this PR. You are amazing 💯


Improve iRODS data request path display in UI

The current way we render the path is not optimal, as it only shows the immediate collection above the collection/object to be deleted.
Depends on #1748.
Spec

Add assay link similar to current landing zone list

Do #1748 first

Display entire path below assay root

Do not use overflow container
Allow line breaks

Update tests

Done.


MorphNet TF Slim Examples for ResNet with ImageNet

Instructions to train with Morph-Net
Morph-Net parameters are in train_image_classifier.py from lines 546-552.
Change models as described in nets/net_factory.py lines 30-37.
Structure should be exported to TRAIN_DIR/ee.
num_clones specifies number of GPUs for multi-GPU training.
DATASET_DIR=/path/to/imagenet/tf-records
TRAIN_DIR=/path/to/morph-net_logs
python train_image_classifier.py \
    --train_dir=${TRAIN_DIR} \
    --dataset_name=imagenet \
    --dataset_split_name=train \
    --dataset_dir=${DATASET_DIR} \
    --model_name=resnet_v2_50 \
    --num_clones 8

@googlebot I signed it!

@pkch can you please take a look.


YouTube feed page no longer working - showing single device support info

Have updated to latest to revision but this may have stopped working before today. For me this now only shows a single video about YouTube device support regardless of the device I'm using. e.g. happens on my Win7 laptop and my iPad.
Is this the same for everyone? Is it due to yet another change at YouTube end?
The single clip that now shows links to https://support.google.com/youtube/answer/6098135?p=yt_devicesupport&hl=en&rd=1

Same for me. Upon investigation it seems that they have changed their API and now place a restriction on the number of unauthorised accesses anyone can make - I did about 5 before receiving this message

We might not be able to get around this...

Although not our fault this is a biggie in terms of breaking existing projects. e.g. I'm certain that Alistair will now have plenty of LO's with this page type added and now broken.
Is there a solution where whoever is responsible for an installation registers for the api to work?

The problem is that the api key would be exposed in the javascript so anyone could use it. The only way would be to have a youtube_proxy.php file on the server and use that as a go between... we would however have the same problem for exported standalone LOs; they would always be tethered to the server..

I suspect we use the key I set up, and everyone is using that. Institutions ought to really set up their own, same goes for flickr.

We dont use a key, v2 of the youtube feed gave us the required feed without authentication... Google have now moved on to v3 since March and require auth using a key. with an api key though we could solve this and the qrcode short url issue...

So the answer is to provide space in management.php for the various keys?

I've got a basic search working and will finish this off next week. At the very least we can leave a placeholder INSERT YOUR KEY HERE, but so much the better if management.php can hold a slot for it, and we can get it from there (and error if it isn't present)

All done. api_key_dist.php is the placeholder, code checks for existence of api_keys.php and then includes it if it exists.


Add server version to about page template.

zserver/context_processors.py: Pull in ZULIP_VERSION variable from version.py
about.html: Put server version into template.
Fixes: #3907

Automated message from Dropbox CLA bot
@wangjames, it looks like you've already signed the Dropbox CLA. Thanks!

Looks great; I posted one small comment; if you fix that and the tests pass, we can merge this :).
I guess we should also add a link to "About Zulip"?

Hmmm now all of a sudden I'm getting this error when I run the tests?
ImproperlyConfigured: Requested setting DATABASES, but settings are not configured. You must either define the environment variable DJANGO_SETTINGS_MODULE or call settings.configure() before accessing settings.
This is happening with the up to date master branch without my changes. I did another provision just in case, but it didn't change anything.

ok made changes

Nice, merged, thanks @wangjames!


Dependencies update ...

Silly dep updates, that's it.

Ciao Luca,
thanks for the contribution, looks good, merging it.


Undecipherable error when specifying admin.useAsTitle on an nonexistent field

Link to reproduction
No response
Environment Info
Node.js v20.12.2

Binaries:
  Node: 20.12.2
  npm: 10.5.0
  Yarn: 4.4.1
  pnpm: N/A
Relevant Packages:
  payload: 3.0.0-beta.100
  next: 15.0.0-canary.104
  @payloadcms/db-postgres: 3.0.0-beta.100
  @payloadcms/graphql: 3.0.0-beta.100
  @payloadcms/next/utilities: 3.0.0-beta.100
  @payloadcms/richtext-lexical: 3.0.0-beta.100
  @payloadcms/translations: 3.0.0-beta.100
  @payloadcms/ui/shared: 3.0.0-beta.100
  react: 19.0.0-rc-06d0b89e-20240801
  react-dom: 19.0.0-rc-06d0b89e-20240801
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10

Describe the Bug
Specifying a useAsTitle on a field that doesn't exist triggers an undecipherable error: TypeError: right-hand side of 'in' should be an object, got undefined when visiting the List page of the Collection.
Reproduction Steps

Add the following Collection:

import type { CollectionConfig } from "payload";

export const Example: CollectionConfig = {
    slug: "example",
    admin: {
        useAsTitle: "email", // this field does not exist
    },
    fields: [],
};

export default Example;

Adapters and Plugins
No response

Fixed in https://github.com/payloadcms/payload/pull/8122
We'll throw a clear error if the useAsTitle is invalid


Feature request: imagelightbox selector in overlay

For scenarios where there are >1 ILB galleries, it would neat if the user could "jump" from gallery to gallery by clicking associated tabs when any given lightbox set is activated. Seamlessly and stuff.

Hi, I'm cleaning up old issues. This seems to me to be way too complicated and confusing for users. I'm closing this until there is a reasonable proposal with some mockups on how to do this with good UX.


Remove CockroachDB poststart commands

High-level description
If an ExecStartPost command times-out, then the unit is killed,
even when the command starts with -.  As the post-start steps
here are also executed by a periodic timer, we remove them here
to prevent the post-start timing out while waiting for Cockroach
to start, and then preventing Cockroach from starting.
Corresponding DC/OS tickets (required)

DCOS-62292 Remove possibility of timeouts in systemd ExecStartPost

Related tickets (optional)

DCOS-ID JIRA title / short description.

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[ ] Change log from the last version integrated (this should be a link to commits for easy verification and review): example
[ ] Included a test which will fail if code is reverted but test is not. If there is no test please explain.
[ ] Test Results: [link to CI job test results for component]
[ ] Code Coverage (if available): [link to code coverage report]

@mesosphere-mergebot changelog-not-required change will be back-ported


noop commit to test travis

Coverage remained the same at 88.21% when pulling 2bcaeca246ea3703325b38e61d2ff495d0afd329 on travis-test into ae9b8bce7a804ff66712c7bf5caf084e321601ce on master.

Status checks look good again:


Fix for .babelrc handling

I believe I've found a fix for .babelrc loading. We need to pass the filename and sourceRoot options to babel.transform. I had to modify a couple of function signatures and their uses to do this.
Solves #40
Hope you like it!

Thanks @davidhewitt, I have already published it in a beta version, because I will try it with vue-styleguidist
npm install<EMAIL_ADDRESS>

This seems to work when I tested by changing the vue-styleguidist dependency on vue-docgen-api from its current ^2.3.11 to 2.3.12-beta. Any chance this can get rolled out officially, or are you still testing/investigating?

@mclassic Thank for validating it. This week I will release it.

Ready on version 2.3.13

Many thanks - 2.3.13 is working nicely for me too.


Sidebar navigation not working

Describe the bug
After upgrading to v1.8.1 on MacOS 15.1, the sidebar navigation stopped working.
As a workaround, you can navigate by using the "Tab" system menu (or the related keyboard shortcuts).
To Reproduce

Open OrbStack window
See the Docker Containers screen
Click on any other item on the left

Expected behavior
The screen changes to show the selected tab.
Diagnostic report (REQUIRED)
OrbStack info:
Version: 1.8.1
Commit: 442ca0f634f1e62aa1f00c2c54353e69830cc4d5 (v1.8.1)
System info:
macOS: 15.1 (24B83)
CPU: arm64, 8 cores
CPU model: Apple M1 Pro
Model: MacBookPro18,3
Memory: 16 GiB
Full report: https://orbstack.dev/_admin/diag/orbstack-diagreport_2024-11-13T16-04-06.428430Z.zip

Screenshots and additional context (optional)
See example below: I navigated to the Kubernetes Pods screen using keyboard shortcuts, then clicked on the Linux Machines menu item, but the screen didn't change.

I see the exact behavior on Orbstack 1.8.1 on Mac OS 15.1.

For me this only happens when closing (CMD+w or by pressing the X) and re-opening the OrbStack window . Afterwards, the navigation is broken.
(1.8.1 on macOS 15.1 as well)

As a workaround, you can close the window and re-open it by clicking OrbStack's Dock icon.

As a workaround, you can close the window and re-open it by clicking OrbStack's Dock icon.

Thanks for the workaround.  Also of note, I've noteced the OrbStack menu items for the application disappear at random times when the window is active.

Yes, the issue comes up when I close the orbstack window and open it again, even by using dock icon.
I think it got introduced after recent release.
https://github.com/user-attachments/assets/5e2c73e9-6cf0-4c17-a6a3-739d6b0ef588

Just an update: This is a compatibility issue with macOS 15.1, introduced in OrbStack 1.8.1. We're still working on fixing this without causing regressions in other cases and OS versions — sorry for the delay.
There are several workarounds:

Close the window, then click OrbStack's Dock icon to re-open it. (Do not use the menu bar or any other way of opening the window.)
Restart the OrbStack app
Always keep the main window open (background/minimized is fine); avoid closing it until this bug is fixed
Downgrade to OrbStack 1.8.0: https://docs.orbstack.dev/downgrade#v1-8-0

Fixed in v1.8.2.


[SPARK-18061][SQL][Security] Spark Thriftserver needs to create SPNego principal

What changes were proposed in this pull request?
Spark Thriftserver when running in HTTP mode with Kerberos enabled gives a 401 authentication error when receiving beeline HTTP request (with end user as kerberos principal). The similar command works with Hive Thriftserver.
What we find is Hive thriftserver CLI service creates both hive service and SPNego principal when kerberos is enabled whereas Spark Thriftserver only creates hive service principal.
CLIService.java
if (UserGroupInformation.isSecurityEnabled()) {
      try {
        HiveAuthFactory.loginFromKeytab(hiveConf);
        this.serviceUGI = Utils.getUGI();
      } catch (IOException e) {
        throw new ServiceException("Unable to login to kerberos with given principal/keytab", e);
      } catch (LoginException e) {
        throw new ServiceException("Unable to login to kerberos with given principal/keytab", e);
      }

  // Also try creating a UGI object for the SPNego principal
  String principal = hiveConf.getVar(ConfVars.HIVE_SERVER2_SPNEGO_PRINCIPAL);
  String keyTabFile = hiveConf.getVar(ConfVars.HIVE_SERVER2_SPNEGO_KEYTAB);
  if (principal.isEmpty() || keyTabFile.isEmpty()) {
    LOG.info("SPNego httpUGI not created, spNegoPrincipal: " + principal +
        ", ketabFile: " + keyTabFile);
  } else {
    try {
      this.httpUGI = HiveAuthFactory.loginFromSpnegoKeytabAndReturnUGI(hiveConf);
      LOG.info("SPNego httpUGI successfully created.");
    } catch (IOException e) {
      LOG.warn("SPNego httpUGI creation failed: ", e);
    }
  }
}

SparkSQLCLIService.scala
 if (UserGroupInformation.isSecurityEnabled) {
      try {
        HiveAuthFactory.loginFromKeytab(hiveConf)
        sparkServiceUGI = Utils.getUGI()
        setSuperField(this, "serviceUGI", sparkServiceUGI)
      } catch {
        case e @ (_: IOException | _: LoginException) =>
          throw new ServiceException("Unable to login to kerberos with given principal/keytab", e)
      }

The patch will add missing SPNego principal to Spark Thriftserver.
How was this patch tested?
Ran manual testing with beeline command through spark against kerberized cluster.
Ran Spark unit tests for hive, sql and catalyst.

Can one of the admins verify this patch?

@steveloughran @yhuai Will you be able to help review this PR?

I'm not spark committer so can't review it well enough to get in; I was just watching it out of concern for the word "kerberos". How about you ask on the spark developer list for any volunteers to review.
Looking at the code, I'd drop using reflection for logging. You can just create an SLF4J log with the name "org.apache.hive.hiveserver2" (or whatever the full path is) and end up with the same log name as the parent class. As for the setting of the hive option, I do think it's an ugly pain which should really be addressed by making hive extensible —until then, what choice to do you have.

Thanks @steveloughran. I will check on the developer list.

@vanzin I believe this might be your realm :) Could you please help review this.

Thanks Luciano. I am looking at the changes and will add them soon.

ok to test

Test build #69034 has started for PR 15594 at commit 448f91f.

Test build #69034 has finished for PR 15594 at commit 448f91f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/69034/
Test PASSed.

Merged build finished. Test PASSed.

Hi @cmirash, is it still active?


Autopilot rebalance automation

This is combined PR of:
https://github.com/portworx/torpedo/pull/547
https://github.com/portworx/torpedo/pull/543
https://github.com/portworx/torpedo/pull/537
It covers:
https://portworx.atlassian.net/browse/AUT-217
https://portworx.atlassian.net/browse/PTX-2732
https://portworx.atlassian.net/browse/PTX-2733
https://portworx.atlassian.net/browse/PTX-2734
https://portworx.atlassian.net/browse/PTX-2736
https://portworx.atlassian.net/browse/PTX-2737
https://portworx.atlassian.net/browse/PTX-2741
https://portworx.atlassian.net/browse/PTX-2743

LGTM

LGTM


Step option to set Message Format and use that in notification API call

Currently the message is sent with default message format - HTML if no option is provided while calling the API.
The HTML message format does not support @ mentions and (emojis). So enhanced to provide option for selecting message format type!!
This for my first experience with GO lang so pardon me and laugh aloud if I made a mistake. Please suggest and I will fix it.
Also was not sure how to test it.
Thanks!

Thanks so much! Couple of notes:

Did you try to run this step locally, with bitrise CLI? This step still has the old, V1 README; please check this readme for up to date info https://github.com/bitrise-steplib/step-template

You made a couple of syntax errors, running the step with bitrise run test will show those

I'm not sure, but we should probably have only a single message format - I think if someone sets the format for the success message s/he will want to use the same format for error too; but if you think it would be useful to have separate format params for success & error we can keep it the way it is in the PR.

We'll schedule a full step revision for this step, as it has quite outdated README, testing setup, etc. We'll do this on Monday, after that it should be easier to just check the README and run the tests on your Mac before submitting a PR.

@jsinh I will do a step revision and wire in a new input message_format based on your PR.
I close this PR, becouse of the revision will change a couple of things in the code.
A new version will come soon.
Thanks for your contribution @jsinh :)

I was going to work on it tonight. Sorry for the timezone diff.
But thanks to picking it up, appreciate it! :)


Add: rio-wayland-deb and rio-x11-deb

rust based terminal emulators. sorry for the hiatus

Please make these 2 seperate PRs.


Ubuntu 14.04 + GCC4.9 link error

About latest master branch, the following link error occurred.

vagrant@processor:/srv/tools/PotreeConverter/build$ make
Scanning dependencies of target PotreeConverter
make[2]: Warning: File `PotreeConverter/CMakeFiles/PotreeConverter.dir/depend.make' has modification time 1.                           4 s in the future
[  7%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/BINPointReader.cpp.o
[ 15%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/GridCell.cpp.o
[ 23%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/LASPointReader.cpp.o
[ 30%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/LASPointWriter.cpp.o
[ 38%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/main.cpp.o
[ 46%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/Point.cpp.o
[ 53%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/PointAttributes.cpp.o
[ 61%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/PotreeConverter.cpp.o
[ 69%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/PotreeWriter.cpp.o
[ 76%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/PTXPointReader.cpp.o
[ 84%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/SparseGrid.cpp.o
[ 92%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/stuff.cpp.o
[100%] Building CXX object PotreeConverter/CMakeFiles/PotreeConverter.dir/src/Vector3.cpp.o
Linking CXX executable PotreeConverter
/usr/bin/ld: CMakeFiles/PotreeConverter.dir/src/PotreeConverter.cpp.o: undefined reference to symbol 'pthrea                           d_create@@GLIBC_2.2.5'
//lib/x86_64-linux-gnu/libpthread.so.0: error adding symbols: DSO missing from command line
collect2: error: ld returned 1 exit status
make[2]: *** [PotreeConverter/PotreeConverter] Error 1
make[1]: *** [PotreeConverter/CMakeFiles/PotreeConverter.dir/all] Error 2
make: *** [all] Error 2

Sorry, this issue's cause was my fault (pulling master branch was failed).
So, I close this issue.


[PDI-16178] arrayIndexOutOfBoundsException when collapsing a folder in "Open File" dialog

check was added

Build Completed
:white_check_mark: This pull request has passed all validations.
Build Commands
ant -Dtestreports.dir=bin/reports/unit-test -f ui/build.xml clean-all resolve jacoco && ant -f ui/build.xml checkstyle publish-local

Cleanup Commands
rm -r ~/.ivy2/local || echo no publish local to remove

Changed files
  ui/src/org/pentaho/di/ui/repository/dialog/SelectObjectDialog.java

@mbatchelor @mchen-len-son @pamval please review


arm64: fix qemu SEGV during build process

Followup #1336
Docker hub automated build fails with qemu
It is caused by problematic qemu-user-static which contains a bug that crashes
arm64 Debian derivatives.
#16 104.7 update-alternatives: using /usr/bin/g++ to provide /usr/bin/c++ (c++) in auto mode
#16 104.7 Processing triggers for libc-bin (2.31-13+deb11u2) ...
#16 104.8 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#16 105.0 Segmentation fault (core dumped)
#16 105.0 qemu: uncaught target signal 11 (Segmentation fault) - core dumped
#16 105.3 Segmentation fault (core dumped)
#16 105.3 dpkg: error processing package libc-bin (--configure):
#16 105.3 installed libc-bin package post-installation script subprocess returned error exit status 139
#16 105.3 Errors were encountered while processing:
#16 105.3 libc-bin
#16 105.4 E: Sub-process /usr/bin/dpkg returned an error code (1)
See https://github.com/fluent/fluentd-docker-image/pull/315

#1338 is not published yet, so it is not bumped up revision.

Thanks!