ParameterVector support for Schedules

What is the expected enhancement?
Currently, QuantumCircuits support assign_parameters with ParameterVector input. The task is to add support similarly for Schedules, which now support parameter assignment as well.

can I try this one?

Yes, please! Let me know if you need help. I would start by looking in circuit/quantumcircuit.py and expect to make changes in pulse/schedule.py. (Plus a reno note and tests)

Hello, @lcapelluto I am a first-time Open Source contributor, do you mind if I take a look at the issue?

Hello, @lcapelluto I am a first-time Open Source contributor, do you mind if I take a look at the issue?

Hi @alejomonbar ! any progress?

Hi @1ucian0. Yes, I just got some feedback from @lcapelluto but I have this question https://github.com/Qiskit/qiskit-terra/pull/5240#issuecomment-793194776 for concluding with this issue.

This issue can be closed as this functionality is available in the current version of qiskit.

from qiskit import pulse
from qiskit.pulse import Schedule
from qiskit.circuit import ParameterVector

schedule = pulse.Schedule()
parameters = ParameterVector("θ", 2)
gate = pulse.Gaussian(640, parameters[0], parameters[1])
schedule += pulse.Play(gate, pulse.DriveChannel(0))
schedule.assign_parameters({parameters:[0.75, 160]})

# Schedule((0, Play(Gaussian(duration=640, sigma=θ[1], amp=θ[0], angle=0), DriveChannel(0))), name="sched2")

@rupeshknn This issue should actually remain open, as the output schedule does not carry the assigned parameter values but maintain the ParameterVectorElements themselves.


appservice plan modified by az webapp up

Describe the bug
az webapp up modifies the plan given via -p option. Tested for Linux apps plan.
Expected Behavior
The appservice plan settings are respected by the command
To Reproduce:
Create a plan and then a webapp (in my case a Python Flask app)

az appservice plan create -n my-plan -g my-group --sku B1 -l "West Europe" --is-linux
az webapp up -n my-app -g my-group -p my-plan

Now the plan is P1v2 instead of B1 as originally created.
Environment Summary
Linux-4.15.0-65-generic-x86_64-with-debian-buster-sid
Python 3.6.5
Shell: bash

azure-cli 2.0.75 *

Additional Context

Thanks for reporting this,  for a current work around please run the up command with --sku parameter  as az webapp up -n my-app -g my-group -p my-plan --sku B1
This is because the up command uses some defaults & SKU might be using the defaults, i will take a look but could you also try to upgrade to 2.077 https://pypi.org/project/azure-cli/ if possible if you still see this?

Can we close this issue?

I haven't been able to test. I will do so this week and comment on the results here.

@ammanifold can you check if this repros for you locally. I am expecting this shouldn't be an issue since if the app exists we try to use the SKU from the ASP of the APP. https://github.com/Azure/azure-cli/blob/dev/src/azure-cli/azure/cli/command_modules/appservice/custom.py#L3012
Please close this if this doesn't repro for you. thanks!

Thanks @panchagnula
I also cannot reproduce this issue, closing!


Atata Screenshot Comparison

Hi,
I am working on a test to match two screenshots. I have added some custom functionality to compare the screenshot taken by a user with a screenshot taken using Atata framework.
For some reason, the images comparison don't pass. However, if I generate both images via Atata, the comparison passes.
In all cases, I make sure in my algorithm that images are of the same size. Also, the image Bit Depth is same.
Do you have any idea, what could be cause here.
Apologies for not passing any sample data. It is just because of the privacy.
However, should you require, I will prepare some.
Thanks in advance.
Regards,
Muhammad

Hey,
It's hard to say at this point. First, I assume that you save screenshots in PNG format, not JPEG. I think you should check with your comparison algorithm the difference between images, how much are they different. Generate a delta image with highlighted pixels (red or pink color) that differ. That should make it more clear to understand the difference.
Also, it is absolutely OK, from my point of view, to get the expected screenshot in an automatic way from Atata/WebDriver. Run the test once to get the expected screenshot and then store it somewhere for the future comparison as expected image.
Also, I can advise taking a look at Applitools, which does the screenshot comparison in a good way. But it is not free.

Thanks for your feedback. I'll look to see if I can stick with Atata generating testing samples for me.

We implemented this in the Lombiq UI Testing Toolbox that uses Atata. Check it out here: https://github.com/Lombiq/UI-Testing-Toolbox/issues/85


Handling telemetry client errors

Handling telemetry errors and tests

Moving https://github.com/confluentinc/kafka/pull/682 to this PR.

Yeah, there's at least one thing visible in the build:
11:38:09  [ant:checkstyle] [ERROR] /home/jenkins/workspace/confluentinc-pr_kafka_PR-685/clients/src/test/java/org/apache/kafka/clients/telemetry/DefaultClientTelemetryTest.java:152:9: 'while' is not followed by whitespace. [WhitespaceAfter]

This is fixed, thanks @kirktrue


pkg/dartdev/test/commands/test_test failed on "[vm] Enable non-nullable experiment in the VM by default"

After https://dart-review.googlesource.com/c/sdk/+/170201 VM started correctly auto-detecting sound null safety mode (based on the opt-in status of entry point), and the test pkg/dartdev/test/commands/test_test started failing. It attempts to run an opted-in script which depends on opted-out packages.
stdout: 00:00 +0 -1: loading test/foo_test.dart [E]
  Failed to load "test/foo_test.dart":
  Unable to spawn isolate: Error: This project cannot run with sound null safety, because one or more project dependencies do not
  support null safety:

   - package:stream_channel
   - package:test_core
   - package:test_api
   - package:test
   - package:async
   - package:stack_trace
   - package:term_glyph
   - package:collection
   - package:boolean_selector
   - package:meta
   - package:path
   - package:matcher
   - package:string_scanner
   - package:source_span
   - package:pedantic
   - package:pool
   - package:charcode
   - package:package_config

  Run 'pub outdated --mode=null-safety' to determine if versions of your
  dependencies supporting null safety are available.
  ===== asynchronous gap ===========================
  dart:async/future.dart 280:46                                  new Future.error
  package:test_core/src/runner/loader.dart 246:26                Loader.loadFile.<fn>
  ===== asynchronous gap ===========================
  dart:async/zone.dart 1129:19                                   _CustomZone.registerBinaryCallback
  dart:async-patch/async_patch.dart 94:8                         _asyncErrorWrapperHelper
  package:test_core/src/runner/loader.dart                       Loader.loadFile.<fn>
  package:test_core/src/runner/load_suite.dart 98:31             new LoadSuite.<fn>.<fn>
  package:test_core/src/runner/load_suite.dart 108:8             new LoadSuite.<fn>
  package:test_api/src/backend/invoker.dart 229:15               Invoker.waitForOutstandingCallbacks.<fn>
  dart:async/zone.dart 1190:13                                   _rootRun
  dart:async/zone.dart 1093:19                                   _CustomZone.run
  dart:async/zone.dart 1630:10                                   _runZoned
  dart:async/zone.dart 1550:10                                   runZoned
  package:test_api/src/backend/invoker.dart 226:5                Invoker.waitForOutstandingCallbacks
  package:test_api/src/backend/invoker.dart 381:17               Invoker._onRun.<fn>.<fn>.<fn>
  ===== asynchronous gap ===========================
  dart:async/zone.dart 1121:19                                   _CustomZone.registerUnaryCallback
  dart:async-patch/async_patch.dart 83:23                        _asyncThenWrapperHelper
  package:test_api/src/backend/invoker.dart                      Invoker._onRun.<fn>.<fn>.<fn>
  dart:async/zone.dart 1190:13                                   _rootRun
  dart:async/zone.dart 1093:19                                   _CustomZone.run
  dart:async/zone.dart 1630:10                                   _runZoned
  dart:async/zone.dart 1550:10                                   runZoned
  package:test_api/src/backend/invoker.dart 368:9                Invoker._onRun.<fn>.<fn>
  dart:async/zone.dart 1190:13                                   _rootRun
  dart:async/zone.dart 1093:19                                   _CustomZone.run
  dart:async/zone.dart 1630:10                                   _runZoned
  dart:async/zone.dart 1550:10                                   runZoned
  package:test_api/src/backend/invoker.dart 148:7                Invoker.guard
  package:test_api/src/backend/invoker.dart 411:15               Invoker._guardIfGuarded
  package:test_api/src/backend/invoker.dart 367:7                Invoker._onRun.<fn>
  package:stack_trace/src/chain.dart 102:24                      Chain.capture.<fn>
  dart:async/zone.dart 1190:13                                   _rootRun
  dart:async/zone.dart 1093:19                                   _CustomZone.run
  dart:async/zone.dart 1630:10                                   _runZoned
  dart:async/zone.dart 1550:10                                   runZoned
  package:stack_trace/src/chain.dart 100:12                      Chain.capture
  package:test_api/src/backend/invoker.dart 366:11               Invoker._onRun
  package:test_api/src/backend/live_test_controller.dart 152:11  LiveTestController.run
  dart:async/future.dart 201:37                                  new Future.microtask.<fn>
  dart:async/zone.dart 1190:13                                   _rootRun
  dart:async/zone.dart 1093:19                                   _CustomZone.run
  dart:async/zone.dart 1021:23                                   _CustomZone.bindCallback.<fn>
  dart:async/schedule_microtask.dart 41:21                       _microtaskLoop
  dart:async/schedule_microtask.dart 50:5                        _startMicrotaskLoop
  dart:isolate-patch/isolate_patch.dart 120:13                   _runPendingImmediateCallback
  dart:isolate-patch/isolate_patch.dart 185:5                    _RawReceivePortImpl._handleMessage

00:00 +0 -1: Some tests failed.

/cc @a-siva @bkonyi @devoncarew

CI output for the failure here: https://dart-ci.firebaseapp.com/cl/170201/3.

https://dart-review.googlesource.com/c/sdk/+/170241

This CL also caused standalone_2/io/regress_7679_test to start failing:
https://dart-ci.appspot.com/log/vm-kernel-reload-linux-debug-x64/dartk-reload-linux-debug-x64/8924/standalone_2/io/regress_7679_test
This test starts a new process to run another script, so the logs don't show the actual failure. If you print result.stdout and result.stderr you can see the problem. It's hitting ASSERT(!FLAG_identity_reload) on line 2296 of runtime/vm/isolate_reload.cc.

@liamappelbe - just so there's no confusion - can you attach the commit that you bisected to? I'm not sure if you mean the CL that fixed the null safety detection, or the CL that fixed one of the follow-on failing tests.

https://dart-review.googlesource.com/c/sdk/+/170201

Thanks! Note that this specific issue is related to the pkg/dartdev/test/commands/test_test test failure.

Ok. Filed https://github.com/dart-lang/sdk/issues/44065 instead.

Thanks! I'll close this issue as the fix for it landed.


Pipeline for building tidy df for indicators

The Rmd takes care of:

retrieving taxa from checklists
retrieving taxonomic information for taxa in 1. which match GBIF backbone
retrieving distribution information for each taxa
retrieving description information for each taxa
merge all retrieved information
tidying
filtering alien species based on establishmentMeans (see #28), occurrenceStatus (see #26) and country  equal to BE (at the moment the problem with synonyms is not tackled, see https://github.com/trias-project/pipeline/issues/21#issuecomment-382038846)
saving final df as .tsv file

The data.frame output is now 100% tidy (see https://github.com/trias-project/pipeline/issues/30), in particular the columns type and description don't exist anymore, the 5 different types are spread in 5 columns:

pathway
native range
origin
invasion stage
habitat

At some point, a large part of this functionality will have to be ported to https://github.com/trias-project/unified-checklist, but it doesn't have to be now.


Labels still displayed for annotations outside axis limits

My specific case is a series of four charts, one of which has a shorter horizontal (x-) axis than the others. On the chart with the shortened x-axis, there are two line annotations which are less than the minimum value for the axis. The lines aren’t displayed, but the labels are displayed atop each other near the minimum x-axis value. For an example, check this page and click “Testing” above the chart.
One can, of course, work around this by manually setting enabled: false for labels for which the corresponding annotations are located outside the range of values for the axis, but this seems like fairly boilerplate code that might be better handled at the plugin level.
I’m not sure if there is a particular interest in maintaining the current behavior of enabled: true, where a label is forced to be shown even if its corresponding annotation isn’t visible. If there is such an interest, I would suggest adding a new option such as enabled: 'auto', which would display a label only if the corresponding annotation is visible. (Maybe make it the default, also? To me, at least, this seems like the more intuitive behavior.)

I'd consider this a bug


docs: adds detailed docs for configuring the service

Summary by CodeRabbit

Documentation

Added a new section in the README for configuration variables.
Detailed required and optional environment variables for database connections, monitoring, Ethereum RPC, debugging, performance, heartbeats, and various transport configurations (Slack, Telegram, Email).

@coderabbitai review


Mac: allow for more custom title bar styles

On Mac OS, modern applications typically take over control of the title bar. Some examples:
Skype for Business:

Outlook:

VS Code so far is not leveraging this and thus the title appears like this:

Proposed solution introduces a new setting window.titleBarStyle that allows to switch to a custom title bar (and potentially also to a inline style as discussed in https://github.com/Microsoft/vscode/pull/12628).

Will this setting be in Insiders build soon?

@smlombardi tomorrow 👍

@bpasero this is great.  It's exactly what I was going to propose for a conservative first step.  Thanks!

@bgashler1 great. I was about to ask if you have ideas for which coloring to use. I just picked the ones for dark, light and high contrast theme.
They live in https://github.com/Microsoft/vscode/blob/master/src/vs/workbench/browser/parts/titlebar/media/titlebarpart.css#L55

Could this feature be wrapped up in an extension instead? This could give more flexibility to customize the color of the titlebar.

OK. Then how about a more specific name for the settings property, so it is easily recognized as applying to mac only?

@jtlowe the setting will not show up on Windows and Linux. And it will eventually be supported across all OS.

The app looks much nicer with this enabled, thanks for adding this.

Note that on macOS when "window.titleBarStyle": "custom" is set, the usual behavior allowing one to see the path tree (while holding down the command key and clicking) of the file in the titlebar is not preserved. I realize this is a "custom" titlebar, but it would still be nice to keep this behavior.

@wprater Perhaps an option to display the entire path in the title bar?  I've seen that option in other editors.

@wprater good point, I guess one thing I could do is open a context menu upon Cmd+click that contains entries for the path segments to open in the finder. What I will not be able to do is to show icons though...

Btw we do also have a new option to show the full path in the title bar:
"window.showFullPath": true

I think users will appreciate that.  I've used it many times over the years to open a directory from the title bar.

It should be in insiders now.

Closing, this is done minus bugs.

Great job!! I am loving it

Closing, this is done minus bugs.

where is the bug list?  thought I recalled you spelling them out?  just wanted to track https://github.com/Microsoft/vscode/issues/15098#issuecomment-259274919

@wprater but that one is fixed in current insider builds.
Outstanding bugs are two I can think of right now:

on sierra it can lead to a native crash (https://github.com/Microsoft/vscode/issues/15154)
when dev tools are opened and docked into the window you cannot move the window (https://github.com/electron/electron/issues/3647)


Gopass colors not shown > 45-ish entries

Summary
Gopass doesn't display the tree overview with colors after a certain number of entries
Steps To Reproduce
I have created a new store with 1 entry (test) with 2 passwords
I have added 46 additional passwords (all copies of the same one)
When I add entry 47 the colors of the gopass-->test tree entry are no longer shown.
When I remove the last entry the gopass-->test tree entry are shown in color again.
Note: I also tried this with additional stores, same thing. At some points the colors disappear.
Expected behavior
I expect the color to be shown of the tree entries regardless of the number of passwords stored.
Environment
Mac OS X Catalina. Darwin Kernel Version 19.2.0: Sat Nov  9 03:47:04 PST 2019; root:xnu-6153.61.1~20/RELEASE_X86_64 x86_64
Gopass version info: gopass 1.8.6 (d5b0d3b906cdd9f16ad3f21e366845af7f2c22f3 2019-10-11 18:54:23) go1.13.1 darwin amd64
Installed with Brew 2.2.4
Additional context
Pass shows the colors

I'm afraid, this is not a bug but a feature.
By default gopass will redirect the output to a pager if it's longer than the current terminal.
Some pagers don't handle ANSI color codes, so the output would be broken if colored.
This is why we turn colors off in such cases.
However we can do better and not disable colors if $PAGER is not defined.


METRON-2135: Add NgRx actions to trigger state changes

Contributor Comments
Link to the original JIRA: https://issues.apache.org/jira/browse/METRON-2135
Link to Parent Feature ticket: https://issues.apache.org/jira/browse/METRON-1856
In NgRx, actions are responsible for letting it know about that the application is about to change the global state due to a user interaction or a particular life cycle like "initial load".
https://ngrx.io/guide/store/actions
Related commits
This PR is part of a larger sequence of PRs we are opening to make the reviewing process of the relatively large Parser Aggregation UI feature easier.
To see only the changes that apply to this PR, please review the last commit in the list of commits (the commit to review contains the title of the PR)
If you want to learn more about why we picked this method, please refer to the discussion thread here
Please find the full list of relating PRs below.
PR#1 METRON-2114: [UI] Moving components to sensor parser module
PR#2 METRON-2116: [UI] Removing redundant AppConfigService
PR#3 METRON-2117: [UI] Aligning models to grouping feature
PR#4 METRON-2115: [UI] Aligning UI to the parser aggregation AP
PR#5 METRON-2122: [UI] Fixing early app config access issue
PR#6 METRON-2124: [UI] Move status information and start/stop to the Aggregate level
PR#7 METRON-2125: [UI] Making changes visible in the parser list by marking changed items
PR#8 METRON-2131: Add NgRx and related dependencies
PR#9 METRON-2133: Add NgRx effects to communicate with the server
PR#10 METRON-2134: Add NgRx reducers to perform parser and group changes in the store
CURRENT PR#11 METRON-2135: Add NgRx actions to trigger state changes
PR#12 METRON-2136: Add parser aggregation sidebar
PR#13 METRON-2137: Implement drag and drop mechanism and wire NgRx
PR#14 METRON-2138: Code clean up
PR#15 METRON-2139: Refactoring sensor-parser-config.component and wire NgRx
Pull Request Checklist
Thank you for submitting a contribution to Apache Metron.
Please refer to our Development Guidelines for the complete guide to follow for contributions.
Please refer also to our Build Verification Guidelines for complete smoke testing guides.
In order to streamline the review of the contribution we ask you follow these guidelines and ask you to double check the following:
For all changes:

[X] Is there a JIRA ticket associated with this PR? If not one needs to be created at Metron Jira.
[X] Does your PR title start with METRON-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.
[X] Has your PR been rebased against the latest commit within the target branch (typically master)?

For code changes:

[ ] Have you included steps to reproduce the behavior or problem that is being changed or addressed?

[ ] Have you included steps or a guide to how the change may be verified and tested manually?

[ ] Have you ensured that the full suite of tests and checks have been executed in the root metron folder via:
mvn -q clean integration-test install && dev-utilities/build-utils/verify_licenses.sh

[ ] Have you written or updated unit tests and or integration tests to verify your changes?

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

[ ] Have you verified the basic functionality of the build by building and running locally with Vagrant full-dev environment or the equivalent?

For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered by building and verifying the site-book? If not then run the following commands and the verify changes via site-book/target/site/index.html:
cd site-book
mvn site

[ ] Have you ensured that any documentation diagrams have been updated, along with their source files, using draw.io? See Metron Development Guidelines for instructions.

Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.
It is also recommended that travis-ci is set up for your personal repository such that your branches are built there before submitting a pull request.

+1


Dropdown disabled and loading options

Is your feature request related to a problem? Please describe.
The dropdown feature on the https://flowbite-react.com/dropdown does not provide the loading and disabled options.
Describe the solution you'd like
There are already implemented on Buttons category. Thus, it is possible to integrate the option loading={true} (or the div with the spinner) and disabled={true} on the dropdown feature.

@zoltanszogyenyi I'm trying to find these on flowbite. Do we have disabled options or a loading state? Maybe we need to have it there first so we can implement it here. WDYT?


Change default page size to 1000

Current Behavior

env/netbox.env defines MAX_PAGE_SIZE=0, effectively disabling API pagination.
Expected Behavior

The documented default pagesize of Netbox is 1000. I'd recommend setting the same number out of the box, or just not set the variable at all. This is a common pattern for performance reasons and may (like it did for me initially) lead to some confusion on why the pagination didn't seem be limiting results by default.
I realize that those environment settings are really just there for quick testing and any 'real' deployment should override pretty much every setting in that file. It's a minor change, but thought it could be helpful as it was confusing some of my peers who are testing Netbox now.

I've got no issues with this change, makes sense to me.


feature: Add missing Home props

The type of this PR is: feature
Follow-up to https://github.com/artsy/cohesion/pull/231, adding some missing props.

📦 Published PR as canary version: 4.4.1-canary.242.3515.0

:sparkles: Test out this PR locally via:
npm install<EMAIL_ADDRESS># or
yarn add<EMAIL_ADDRESS>

Thank you chris!

:rocket: PR was released in v4.4.1 :rocket:


FIX: download artifacts from desired workflow

Fixes the recent issues in:

Pyfluent visualization: https://github.com/pyansys/pyfluent-visualization/actions/runs/3992912227/jobs/6849174814
PyAEDT: https://github.com/pyansys/pyaedt/actions/runs/3992907653
Other internal repositories that just upgraded to pyansys/actions@v3.

I feel the conflict is being caused because the value for the workflow is not behaving as expected. Hence, I went with this "duplicated" logic. This is the original logic from<EMAIL_ADDRESS>which has been proven to work.
I do not like to keep patching stuff in here but I did not see other option for the moment. Once we agree on https://github.com/pyansys/actions/discussions/141, everything will be unified for @v4.

I feel the conflict is being caused because the value for the workflow is not behaving as expected. Hence, I went with this "duplicated" logic. This is the original logic from<EMAIL_ADDRESS>which has been proven to work.

I think PyGeometry uses this actions version and we weren't really seeing any issues... let me double check it.

I do not like to keep patching stuff in here but I did not see other option for the moment. Once we agree on #141, everything will be unified for @v4.

I feel you... I don't like patching stuff either. Let's try to get some consensus on #141

Yes... see https://github.com/pyansys/pygeometry/actions/runs/3993924998/jobs/6851241074
PyGeometry isn't affected by this issue. We might want to look into whether this is really what's causing it or not.

@jorgepiloto @RobPasMue @MaxJPRey
What is happening?
The reason why the artifact is not being found is because the workflow conclusion.
If we examine the workflow log:
https://github.com/pyansys/pyfluent-visualization/actions/runs/3992912227/jobs/6849174814#step:11:480
Run dawidd6/action-download-artifact@v2
==> Repository: pyansys/pyfluent-visualization
==> Artifact name: HTML-Documentation-tag-v23.1.0
==> Local path: dev
==> Workflow name: 27198130
==> Workflow conclusion: success
==> (found) Run ID:<PHONE_NUMBER>
==> (found) Run date: 2023-01-20T04:05:04Z
==> (not found) Artifact: HTML-Documentation-tag-v23.1.0
==> Found the following artifacts instead:
Error: no artifacts found

It says the Workflow conclusion: success, and then it picks the run<PHONE_NUMBER>, which is Nightly Documentation Build #239:
https://github.com/pyansys/pyfluent-visualization/actions/runs/3964634582
And it is the last successful run:

See: https://github.com/pyansys/pyfluent-visualization/actions/workflows/nightly-doc-build.yml
Picking a successful workflow run is based on the default behavior of the dawidd6 download action and it was already noted as an issue in here:
https://github.com/dawidd6/action-download-artifact/issues/176
In Pyfluent repo, it was actually picking the wrong workflow.... it was picking the latest successful workflow, until the artifacts expired, hence the error message.
I face that myself in PyMAPDL. See: https://github.com/pyansys/pymapdl/issues/1792
Solution:
You can change the workflow_conclusion option to be in_progress, so it picks the current run. However, that will probably break other workflows which use artifacts from other workflows (they are not in progress anymore).
We could go for the "skip-all-together-this-option", detailed in the following PR:
https://github.com/dawidd6/action-download-artifact/pull/185
I will outline the PR in a few minutes.
TLDR
The default workflow_conclusion argument is successful so it does not work for downloading the artifacts from an artifact which is running already.

I must say I really "hate" this action we are using behind the scenes... I understand the need of using but it is overcomplicating things a lot... I would be in favor of just removing its use and if somebody needs an artifact from another workflow then you just generate that artifact in your new workflow - especially since public repos are not charged by minutes consumed on GH Actions... and they are the ones using it the most.

Thanks for the deep explanation, @germa89.
I saw the changes you made in #156 and decided to add those in here. Even if this pull-request introduces some duplicated logic, it isolates the one from version<EMAIL_ADDRESS>which is the one before introducing the workflow input.
Isolation ensures that users are able to upgrade to the latest "v3" and that we do not run into additional issues. The PR also provides the logic for those who want to use the workflow and workflow_conclussion option.

Fair enough! Thank you for the fix!


Missing constants

The file value/vdouble/scalar/base/Constants.java defines a number of physical and mathematical constants.
Sorely missing are:
pi (but we do have tau)
e (Euler's constant)
Slighly less important (because it is quite easy to "construct"):
phi (The golden ratio; (1+sqrt(5)/2)

The constants E, PHI and PI have been added as Dimensionless constants to the Constants class, and as FloatDimensionless constants to the FloatConstants class. Additionally, the FloatConstants class now contains FloatSIScalar, FloatDimensionless, FloatMass, etc, where the previous version defined double constants (which was clearly wrong).

The unit tests have also been adapted to test the float values in FloatConstants up to 1 ulp precision for the expected value.

All unit tests for Constants and FloatConstants pass, so this issue can be closed.


DecorationManager doesn't understand OpDecorateStringGOOGLE

E.g. need to fill out places where things like SpvOpDecorateId are used.
see HaveTheSameDecoration, AreDecorationsTheSame, etc.

Hey @antiagainst do you want to take a look?

I see there is an rewriting coming for DecorationManager: #1373. I think maybe I should wait until that is landed?

Now that #1373 has landed I've started this.

Fixed by #1410


Persist own keys

Persist own keys, including secret key. Do it in a secure way: only if user accepts it, and do it encoded.

Not yet encrypted


Understand how sqlite works and turn inmate profile into db

This should be helpful https://www.sqlitetutorial.net/sqlite-python/

Created branch to work on this issue: create_ncdoc_db

I took a crack at getting us started. Basically watched the sqlite tutorial and created some files (create_db, config, and main) to create a new ncdoc database and initialize an empty Inmates file.
Definitely not tied to this workflow, so let me know what you think!
Next steps on this issue ticket I believe:

inserting data into the inmates table
dealing with data types (i think all will be added as text - see my note in main.py)

I updated the main.py file to default all columns to string (without it, I ran into this error: "DtypeWarning: Columns (0) have mixed types. Specify dtype option on import or set low_memory=False"). This message didn't come up when I added the parameter (dtype=str) to the pd.read_csv() function.

Good call! Gonna go ahead and close this ticket


Adding a tour guide to make the app beginner friendly

Refers to #136
When the user uses the app for the first time, there should be a quick tour of how to use the feature of the app. I have added a quick tour when a user creates a wallet for the first time.

[x] bdb0007 adds all the necessary dependency to support the tour guide.
[x] 29b67b8 adds a quick tour guide in WalletHome
-Sync Button : User is prompted to use the sync button to sync balance and transaction history.
-Unit Button : User is made aware that they can see the balance in Santoshi unit as well as in bitcoin unit.
-Send Button : User is encouraged to send some of their coins to family and friends or back to the faucet.
[x] 6ffa8cd adds the function homeTutorialDone() so that whenever the tour is finished we can set it to true and can use it to reset it.
[x] a7a02dc Adds a quick tour for the navigation setting as well as for the tutorial.

Dope work. Super super cool.
I tested on my phone and everything worked well. I'll need to dig into the code a bit before I can give bigger comments. A few thoughts to start:

Can we put a button in the settings to allow people to reset the tutorials? As in, if they want to see it again?
So the "tutorials" and the "drawer" buttons, I see you were able to just add a glowing circle, which indicates that they should check those out. The fact that they don't have text associated with them is because we didn't have resource IDs for those items right?

Dope work. Super super cool.
I tested on my phone and everything worked well. I'll need to dig into the code a bit before I can give bigger comments. A few thoughts to start:

Can we put a button in the settings to allow people to reset the tutorials? As in, if they want to see it again?
So the "tutorials" and the "drawer" buttons, I see you were able to just add a glowing circle, which indicates that they should check those out. The fact that they don't have text associated with them is because we didn't have resource IDs for those items right?

Yes we can put a button in settings to reset the tour.
Yes because when I try to add a text to it, it appears in the middle which does not look like it is giving description about the tutorials and drawer. I also tried to align the gravity so that the test appears next to them, but that text was going outside the screen.


Feedback on Tutorial: SAP HANA, express edition Troubleshooting

I guess the only issue with this is that in 60 days you owe Suse $2000-$4000 in subscription fees or .. start over to get a new freekey.
I've tried updating from OpenSuse 12.1 repositories but Suse for SAP seems to be several generations ahead of Open and so nearly every update wants to downport critical versions of libs (like ssl you indicated here).
Suggestions welcome...

Hello SAPSuper
Thank you for bringing this to our attention.    We're assuming that you already have a subscription for SLES, which we should probably document.
If you don't want to go down that route - why not install OpenSuse?    SAP HANA, express edition is community supported, so there's no "formal" certification required.
R


Create a ChatGPT based voice assistant

Added a ChatGPT based voice assistant to help with your queries.

@Techiral   I want to know  if the maintainer didn't add the accepted label the PR won't be considered for the Hacktoberfest ?


[many ports]Update ports.

librsync, tinyutf8, yaml-cpp, rocksdb, xxhash, libwebp

Some file is Binary file not shown, so close this pull request and pull another request.


Slightly more consistent test framework

depends on #133

Codecov Report

Merging #134 into xbrianh-blob-listing will not change coverage.
The diff coverage is n/a.

@@                  Coverage Diff                  @@
##           xbrianh-blob-listing     #134   +/-   ##
=====================================================
  Coverage                 88.52%   88.52%
=====================================================
  Files                        11       11
  Lines                       767      767
=====================================================
  Hits                        679      679
  Misses                       88       88

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 9813f88...88c258a. Read the comment docs.

@DailyDreaming post hoc review please


[BUG] Kubernetes 1.22 is not supported by 1.1.x

https://github.com/longhorn/longhorn/issues/2757 for v1.1.3. Only focus on supporting 1.22.
cc @longhorn/qa

Update: some of the CSI sidecar components doesn't work with Kubernetes v1.22 (e.g., the csi-attacher).
So, we also need to update the csi sidecar components not just the k8s dependency

Note: We need to add to v1.1.3 release note that this version only runs on Kubernetes >= v1.18

Test steps:

Follow the manual test steps at https://github.com/longhorn/longhorn-tests/pull/676/files but for Longhorn v1.1.3 version
Check the following items:

Raise K8s version in Helm chart
Raise K8s version in Doc, Release note
Check the fsGroup permission issue https://github.com/longhorn/longhorn/issues/2964#issuecomment-911993644
Check the RWX feature feature
Check uninstallation using Helm/Kubectl

@kaxing
Please pause on testing this issue. We are planing to revert the commits of this issue because we don't want to drop support for Kubernetes v1.16 and v1.17 in Longhorn v1.1.3
cc @innobead

As per @PhanLe1010 investigation, it's unable to support K8s 1.22 in the coming 1.1.3 w/o updating CSI sidecars because the current sidecars use the deprecated storage storage.k8s.io/v1beta1) APIs which was deprecated and removed from 1.22 already. Also updating sidecars will also require users to have 1.18 minimum version cluster first before upgrading to 1.1.3.
For a patch release, we should focus on bug fixes instead of having another assumption (ex: need to upgrade to K8s 1.18+ first) to avoid users upgrading to it.
So, 1.1.3 will not support 1.22, but if users would like to use longhorn on 1.22, we will suggest using 1.2 instead. (1.2.3 will be a stable release)

As per @PhanLe1010 investigation, it's unable to support K8s 1.22 in the coming 1.1.3 w/o updating CSI sidecars because the current sidecars use the deprecated storage storage.k8s.io/v1beta1) APIs which was deprecated and removed from 1.22 already. Also updating sidecars will also require users to have a 1.18 minimum version cluster first before upgrading to 1.1.3.
For a patch release, we should focus on bug fixes instead of having another assumption (ex: need to upgrade to K8s 1.18+ first) to avoid users upgrading to it.
So, 1.1.3 will not support 1.22, but if users would like to use longhorn on 1.22, we will suggest using 1.2 instead. (1.2.3 will be a stable release)
cc @jenting @khushboo-rancher @kaxing

@innobead, apart from the Longhorn UI, where can I find information about which Longhorn versions are (or will be) stable releases?


Incorrect port redirection when login (with nginx unix socket setup)

Hi devs,
I'm using openresty (nginx fork) but not using a typical setup for it.
I use server in stream to listen port 443 and use upstream and server which listens on unix sockets.
The model can be simplified as below:
stream {
    upstream web-example {
        server unix:/dev/shm/nginx.web.sock;
    }

    server {
        listen 443;
        listen [::]:443;
        proxy_pass web-example;
    }
}

http {
    server {
        listen unix:/dev/shm/nginx.web.sock ssl;
        server_name example.domain;

        ssl_certificate      ...;
        ssl_certificate_key  ...;

        ...
    }
}

When I login with admin panel, grav server redirects me to https://example.domain:0/admin like below:

(actual practice)
I tried to enable Reverse Proxy option in the Configuration tab but it seems not work for my case.
Can you investigate the problem? thank you in advance!

@CaiMiao I have likely found and fixed the bug, but I'm unable to test it. Can you please try the changes in your setup?

@mahagr have been busy and i will check when production ships

seems not working with latest 1.7.21

I don't have a proxy setup, so I cannot really help here. @rhukster you had more experience on proxies?

any news on this?


CAN it replace or just input one column date？

Dear developer,
     I want to write some date into one matrix in different timestep, it means that for one step, i just only input one column in the matrix, but i found that, it is can not work, once whole matrix entry the mat file, the date can not replace if rewrite it, it can not wirte just one by one line.

    Hope to get help!

best
Xinmeng

MatIO is not designed for your use case. You rather would need to read the variable, delete the variable from file (Mat_VarDelete), update the read vaiable and write back.

I consider this answered.


number value error

SQL> create table n(id number primary key,n number(10,2));

Table created.

SQL> insert into n values(1,11.12);

1 row created.

SQL> commit;

Commit complete.

SQL> select * from n;

	ID	    N
---------- ----------
	 1	11.12

ID                       : 1
N                        : 11.120000000000001

package main

import (
	"database/sql/driver"
	"fmt"
	goora "github.com/sijms/go-ora/v2"
	"io"
	"log"
)

func main() {
	DB, err := goora.NewConnection("oracle://hcl:hcl@<IP_ADDRESS>:1521/orcl")
	if err != nil {
		log.Println(err)
		return
	}
	err = DB.Open()
	if err != nil {
		log.Println(err)
		return
	}

	defer DB.Close()

	stmt := goora.NewStmt("select * from n", DB)

	defer stmt.Close()

	rows, err := stmt.Query(nil)
	defer rows.Close()
	columns := rows.Columns()
	values := make([]driver.Value, len(columns))
	for {
		err = rows.Next(values)
		if err != nil {
			break
		}

		Record(columns, values)
	}
	if err != io.EOF {
		log.Println("Can't Next", err)
	}
}

func Record(columns []string, values []driver.Value) {
	for i, c := range values {
		fmt.Printf("%-25s: %v\n", columns[i], c)
	}
	fmt.Println()
}

the problem of float point precision is not related to driver and also not restricted to go
this is a Microsoft link that describe this problem in c++
also I will try to find solution depends on columns pre-defined precision value

I find a solution for this problem I will include it in my next release

you can test it in latest version

yes you are correct I fix it in DecodeDouble but not in DecodeNumber

Thanks, the test is ok
>go get -u github.com/sijms/go-ora/v2
go: downloading github.com/sijms/go-ora/v2 v2.4.14
go get: upgraded github.com/sijms/go-ora/v2 v2.4.13 => v2.4.14

>go run goora.go
ID                       : 1
N                        : 11.12

I will close the issue


Disable unit tests that use private resources

This is an attempt to enable automatic unit tests on external pull requests via CircleCI.
This PR:

disable unit tests using our private resources via @Ignore annotation
comment out git pull on our private resources in the CircleCI configuration

Please note that:

Currently our Redshift test instance is down, so CircleCI tests will fail
There has been issue with CircleCI image that we use for our jdk7 tests: https://discuss.circleci.com/t/apt-get-update-return-404/29237/8
I have included a temporary fix to it, but we may need to use a different image for a proper fix.

I think it looks good. Let me disable the private repo itself and let you know. In this way, we can fundamentally guarantee no access to the repo.

@dongyoungy Currently, the errors are due to our stopped Redshift cluster.  Can you also simply deactivate those unit tests?

@dongyoungy Can you fix the error and merge this to the master?  Not urgent, but I would like to base my branch on this.

Codecov Report

Merging #366 into master will decrease coverage by 2.26%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #366      +/-   ##
==========================================
- Coverage    70.9%   68.64%   -2.25%
==========================================
  Files         168      168
  Lines       11517    11517
  Branches     1879     1879
==========================================
- Hits         8165     7905     -260
- Misses       2868     3106     +238
- Partials      484      506      +22

Impacted Files
Coverage Δ

...n/java/org/verdictdb/sqlsyntax/RedshiftSyntax.java
5.56% <0%> (-72.22%)
:arrow_down:

...erdictdb/core/scrambling/ScramblingMethodBase.java
57.9% <0%> (-31.57%)
:arrow_down:

...rdictdb/core/querying/CreateTableAsSelectNode.java
65.52% <0%> (-24.13%)
:arrow_down:

...ava/org/verdictdb/metastore/ScrambleMetaStore.java
67.23% <0%> (-23.88%)
:arrow_down:

...ictdb/core/scrambling/UniformScramblingMethod.java
70.32% <0%> (-21.87%)
:arrow_down:

...org/verdictdb/sqlreader/ScrambleTableReplacer.java
65.56% <0%> (-16.66%)
:arrow_down:

...ain/java/org/verdictdb/commons/StringSplitter.java
82.76% <0%> (-13.79%)
:arrow_down:

...va/org/verdictdb/coordinator/ExecutionContext.java
71.67% <0%> (-13.35%)
:arrow_down:

src/main/java/org/verdictdb/sqlreader/CondGen.java
66.67% <0%> (-8.77%)
:arrow_down:

...in/java/org/verdictdb/sqlreader/ExpressionGen.java
75.31% <0%> (-7.22%)
:arrow_down:

... and 17 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a29dc0b...b044e37. Read the comment docs.

I have further disabled unit tests with redshift since all unit tests get passed, I am merging this PR.


Double click to finish a freehand polygon

Robin noticed this bug yesterday. Thanks to OSMUS for advice: https://osmus.slack.com/archives/C01G3D28DAB/p1685016451984109
We have a remaining bug double clicking in the snap polygon tool, but the fix for that needs to happen in the route-snapper repo; I'll do it separately.

Aha, apparently the order double click events are fired is not guaranteed by the browser. I suggest we continue with this approach for the moment until we think of something better, or at least make sure this works in the common browser people're using (Edge?)
https://github.com/maplibre/maplibre-gl-js/pull/2593


Discord Server is expired or I cannot join

Describe the bug
expired link in the themes information
To Reproduce
go to your themes -> discord server
Infomation (please complete the following information)
https://i.imgur.com/3THb3fP.png

https://i.imgur.com/qBQPEds.png

It's not expired just locked.


select component should set class from className

This appears to be a regression somewhere between 36.6.1 and 40.0.0.

I might be misunderstanding this bug report, but I am seeing a className prop supplied to a desktop select component getting passed through as intended to the rendered div. Here I have added a tb-select1 class to the Toolbox inputs example in my local sandbox, running with the latest Hoist snapshot:

and I can see it OK in the rendered markup:

Looking at the diff from v40.0.0 to now, I don't see any indication this has changed since release. Let me know if I'm missing it? Thanks.

Yes, in 36.6.1, the class is place on the div in the same way.
It is true that we aren't 100% consistent with where we place the class in our HoistInput implementations.  Sometimes we pass it through to the underlying Blueprint (and presumably HTML element), and sometimes we put it on a div.   For example, in NumberInput we do the former and TextInput we do the latter.

Yes, select does pass through className properly. This can be closed.
I was mistakenly overriding the className when creating my select().
Thanks for following up promptly!


Trivia question error

🐛 Bug Report
Write a description of the bug here, give all the information you can about what it is, how it happened.

correct answer should be 25%

it is


Add Freestyle Jobs support

What's changed?
Adding the capability of creating freestyle jobs instead of pipelines.
What's your motivation?
Some Jenkins installations does not allow the usage of pipelines.
Checklist

[x] I've added unit tests to cover both positive and negative cases
[x] I've added the license header to any new files through ./gradlew licenseFormat
[x] I've used the IntelliJ auto-formatter on affected files
[x] I've updated the documentation (if applicable)

Tested it locally with .war jenkins & mac native cli. It seems to work fine for the happy path. Maybe some corner cases that will need to address in the future.


Hexagonal Architecture (“Ports & Adapters”) – A Quick And Practical Example In Java<EMAIL_ADDRESS>ralfueberfuhr)

Spring Boot + Lombok + MapStruct Code that demonstrates the dependencies within the Hexagonal Architecture. It's focused on the domain, so there is only a single test as PoC for testability.

Closing as instructed by the team.


⚠ Fortnite has degraded performance

In d3fb519, Fortnite (https://fortnite.com) experienced degraded performance:

HTTP code: 503
Response time: 1452 ms

Resolved: Fortnite performance has improved in 9f37337.


Expose isort preferences for tools.

Description: If you're like me you automate everything, including your coding. So I run isort and autopep8 whenever I save a file to get rid of those pesky linting errors.
The changes basically make sure the standards set for this project (by: #1330 and Pylint) are available for other tools like IDE's or texteditors.
I created an additional branch (which I don't suggest merging as it will upset a lot of people) where isort with these settings is applied to the entire codebase in order to proof linting works. https://github.com/aequitas/home-assistant/pull/1
The forced_separate is to satisfy pylint who otherwise throws errors like
************* Module homeassistant.components.google
C: 17, 0: Imports from package voluptuous are not grouped (ungrouped-imports)

A consideration might be to disable that check in pylint.
Please let me know if you think this is worth accepting in the codebase. I can also spend some time on getting autopep8 work.

I'm down to add this config. I did the sorting once before in #1330. However we should make it clear that people should not run this as part of PRs that submit new features. Because all of a sudden it is not clear to me what has changed, making the effort of reviewing a pr way worse. Why change something if it a) already works and b) already passes the linter. (same with autopep)
Because typing is standard lib on Python 3.5 but on Python 3.4, we have been having that one sit in between the standard lib and 3rd party dependencies which satisfies linters run under both versions of Python. How is isort going to handle that ?
Grouped imports makes it very clear what the dependencies are. That's something we should keep. So if isort has an option for that, we should use that.

@balloob I agree with you on that. I don't intent to enforce this on every change, but more like if people choose to use isort/autopep8 on save (like me), the preferences of the project should be reflected in the codebase.
The isort config as I have created it now will put typing in the standard lib section no matter which python version you run isort on.
I updated the config to make group sorting work in all future cases, not just the ones where it conflicts now.

However we should make it clear that people should not run this as part of PRs that submit new features. Because all of a sudden it is not clear to me what has changed, making the effort of reviewing a pr way worse. Why change something if it a) already works and b) already passes the linter. (same with autopep)

If we would run isort globally for the project once again, and then enforce it during CI, we wouldn't have to worry about people changing it in PRs. It would be correct. New PRs that don't follow import order would fail CI. The problem right now is that we have merged code that doesn't follow import order. I don't know why CI doesn't pick this up. More than one time in the last couple of months I've come across modules that have the wrong import order, and not only cases of python3.4 vs python3.5.

I would still be interested to see if isort can run under both Python 3.4 and 3.5 and not freak out Pylint. To satisfy both typing should be between the built-ins and the 3rd party. Just treating it as built-in is not going to satisfy pylint running under Python 3.4

@balloob I get what you mean, I will start investigating if it is possible with isort.

@balloob typing is now sorted in between: https://github.com/aequitas/home-assistant/pull/1/files?diff=unified#diff-1144936535fa48add3eee12ebaee65f1R11

My experience with these automated tools is they really break down the moment you are using 2 or more versions of python. Basically, they are fine for individuals, but on large group projects, with people having a diversity of tools / runtimes, they just generate noise and cruft. Especially given that the stdlib in python grows over time, so what is in which group is python version dependent.
In OpenStack we used to enforce these kinds of rules when it was python 2.7 only. But going across 2.7, 3.4, 3.5 we gave up on machine enforcement, it was just causing more challenges than it was worth.

@sdague I think you have some valid points there. There is always a balance where automation tools outweigh there usefulness (https://xkcd.com/1579/).
Currently this project seems to be aimed at only supporting Python3.x. And there seems to be only a few conflicts in 3.4 and 3.5, which can easily be overseen. In my opinion this argument can be raised again when this direction is shifted, but for now it should not cause big problems.
I am a huge fan of automating as much as possible including my development. I have no strong desire to force this onto everyone, rather convert by example. But making these preferences available in the project allows people to choose for themselves. It also allows to lower the review/contribution burden by giving the developers a quick and easy way to adhere the the project's community preference.
I am willing to invest time in supporting my changes (and other automation topics) for this project over a longer period of time if needed since I work with these topics on a daily basis at work and I really like this project.

We should not automate and enforce the sorting. Reason for this is that although I think readability is important (hence the automated linting), readability of sorting is not as important versus the hurdle that it will add for new contributors.
Instead we could run isort on the code base from time to time, like I did before.

I have no strong desire to force this onto everyone, rather convert by example. But making these preferences available in the project allows people to choose for themselves.

I will not accept PRs that change imports/reformat code unrelated to the code change being made.

I will not accept PRs that change imports/reformat code unrelated to the code change being made.

Agree with you on that, it should never be made hard for a reviewer to oversee what changes a PR intents to bring.
Resorting from time to time will also reduce the amount of difference when people do use these tools on existing files, which I think is a nice compromise.
Sorry for (still) committing isort results on existing code in my PR's. I sometimes forget to manually exclude them from the commits.

readability of sorting is not as important versus the hurdle that it will add for new contributors

I don't think the hurdle of sorting imports is any bigger than sorting modules alphabetically in .coveragerc, or adhering to the other rules of PEP8. Also, there's a tool for sorting the imports.


feat: Add Turkey map to Country Map

SUMMARY
Add Turkey map to Country Map.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS
Clone the repo and go to its root directory. Run the following shell commands:
cd superset-frontend && npm install
npm run plugins:storybook
ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

Hi @rizacavus Thanks for the contribution! code looks great, do you mind fixing the code style to unlock the CI?

Closing since this already exists :)
https://github.com/apache/superset/pull/20698


--conn-limit is not documented

It's not in the site directory or in the Usage text in the weave script.
I'm rather puzzled since the topic comes up fairly often in questions.
The kube-addon page does mention CONN_LIMIT.

there is one-liner in configuration options in kube-addon.md but needs to be updated with current default of 100
CONN_LIMIT - soft limit on the number of connections between   peers. Defaults to 30.
Will update the docs


Replace docs.meilisearch.com with meilisearch.com/docs in every repository.

Since the docs have a new domain, we must update the current occurrences from our repositories.
Search by occurrences in

CONTRIBUTING.md
README.md
code-samples.meilisearch.yml

[ ] automate the work

Notification rain incoming ☔ 🌈

All PR's have been opened in all integrations repositories. I should have mentioned this issue in their PR body. My bad :/

this link appears to be broken https://www.meilisearch.com/docs/learn/what_is_meilisearch/contact, is there a replacement for it ?

Yes! @alallema found it: https://discord.com/invite/meilisearch

Time to a new automation!

Done! 🏁


Make mktemp work on OSX

The mktemp command in OSX needs a template. Here is an example
mktemp /tmp/foo-XXXXX
I have been testing the fix on OSX and Ubuntu.

Thanks!


HEDA Idea: Emergency Contacts

HEDA Idea: Emergency Contacts
Created by: Stewart Anderson (EMEA SE - Salesforce.org)
Idea:
It would be great if we could be able to see "at a glance" who needs to be contacted in an emergency should something happen to a student. It would also be great to not have to figure out who should be contacted in some of our more complex family relationships where one parent or guardian should be contacted before another. So potentially utilize the Relationships within HEDA and add the option to have primary and secondary points of contact and then an Emergency button which shows a model window with the contact details of the primary and secondary contacts with their phone number and email.

**lurch: add

We could leverage the existing "Emergency Contact" checkbox field on Relationship: https://github.com/SalesforceFoundation/HEDAP/blob/a94786e57fd710866ff9d877b70cfde9a574227e/src/objects/Relationship__c.object#L96

Definitely. The only thing that is lacking on the Relationship object is the ability to identify which Emergency Contact is the actual Primary and Secondary Contacts. For example: you could have 4 Relationships tied to a Contact and all 4 be marked as an Emergency Contact. Considering you can set a Type when creating the Relationships maybe we can, as part of the investigation, look at adding a Primary Emergency Contact and Secondary Emergency Contact checkbox to the Relationship Reciprocal Settings in order to identify which contact should be contacted first in an emergency situation.

Could you add an emergency contact numeric sort field and have said modal sort by that.

It is possible to do this as an admin w/out the need for further development in HEDA.
Here is what I did:

Create the following custom fields on the Contact Object:

Here are the formulas used for 4 of the custom fields:
Primary Emergency Contact Email: Primary_Emergency_Contact__r.Email
Primary Emergency Contact Phone Number: Primary_Emergency_Contact__r.Phone
Secondary Emergency Contact Email: Secondary_Emergency_Contact__r.Email
Secondary Emergency Contact Phone Number: Secondary_Emergency_Contact__r.Phone

Add new custom fields to the HEDA Compact Layout on Contact

Create a Process Builder that includes the following steps. Then Activate:

Create 2 Relationships on a single Contact where 1 is marked as Primary and the other is marked as Secondary
Make sure the Emergency Contact Field is checked on both.

Results:

The Issue with going down this route
Obviously most people may not want to use the Compact Layout in this fashion especially since there is a limit to how many fields can be made visible in Lightning: https://success.salesforce.com/ideaView?id=08730000000cETvAAM
Alternative Route
Customers create a lightning component to capture this information and add it to the Contact Record page.

This issue was reviewed by the HEDA team and marked as a solid candidate for a Community Contribution. Please comment with any questions or concerns you may have. Thank you!

Since you asked, @akouayri this looks like a good issue to work on for EDA :-)
CC @jacebryan & @lifewithryan in case things have changed in the last couple of years.

Thanks @Julian88Tex for tagging me on this, But I think things have changed I don't see those emergence fields on contact so I am not sure if this issue still considered

This GitHub Issue will be closed; please follow this Idea in the Trailblazer Community for updates.


[CT-3108] [Bug] Change in state:modified+ behaviour on dbt 1.6 when modifying tests on a model

Is this a new bug in dbt-core?

[X] I believe this is a new bug in dbt-core
[X] I have searched the existing issues, and I could not find an existing issue for this bug

Current Behavior
Just trying to confirm if this is an intended change in dbt 1.6 to the behaviour of state:modified+ wrt modifying a models test.
Expected Behavior
Possibly the same behaviour as it always has been with dbt <= 1.5.
Steps To Reproduce
Using dbt 1.6

Project setup:

# dbt_project.yml
name: my_dbt_project
profile: all
config-version: 2
version: 1.0

models:
  my_dbt_project:
    +materialized: table

# models/schema.yml
version: 2
models:
  - name: foo
    columns:
      - name: id
        tests:
          - not_null

-- models/foo.sql
select 1 id

-- models/bar.sql
select * from {{ ref('foo') }}

Make sure there are no target files present before building for the first time:

$ rm -rf target && dbt build
04:11:16  Running with dbt=1.6.2
04:11:18  Registered adapter: snowflake=1.6.2
04:11:19  Found 2 models, 1 test, 0 sources, 0 exposures, 0 metrics, 372 macros, 0 groups, 0 semantic models
04:11:19
04:11:25  Concurrency: 1 threads (target='sf')
04:11:25
04:11:25  1 of 3 START sql table model dbt_jyeo.foo ...................................... [RUN]
04:11:28  1 of 3 OK created sql table model dbt_jyeo.foo ................................. [SUCCESS 1 in 2.95s]
04:11:28  2 of 3 START test not_null_foo_id .............................................. [RUN]
04:11:30  2 of 3 PASS not_null_foo_id .................................................... [PASS in 2.37s]
04:11:30  3 of 3 START sql table model dbt_jyeo.bar ...................................... [RUN]
04:11:33  3 of 3 OK created sql table model dbt_jyeo.bar ................................. [SUCCESS 1 in 2.81s]
04:11:33
04:11:33  Finished running 2 table models, 1 test in 0 hours 0 minutes and 13.82 seconds (13.82s).
04:11:33
04:11:33  Completed successfully
04:11:33
04:11:33  Done. PASS=3 WARN=0 ERROR=0 SKIP=0 TOTAL=3

^ At this stage, we now have a target/ folder with the state representation (i.e. target/manifest.json) - we will be mv-ing that folder so we can defer to its state.

Modify the test on foo:

# models/schema.yml
version: 2
models:
  - name: foo
    columns:
      - name: id
        tests:
          - unique

Run with state deferral:

$ mv target target_old
$ dbt build --select state:modified+ --defer --state target_old
04:14:09  Running with dbt=1.6.2
04:14:10  Registered adapter: snowflake=1.6.2
04:14:11  Found 2 models, 1 test, 0 sources, 0 exposures, 0 metrics, 372 macros, 0 groups, 0 semantic models
04:14:11
04:14:14  Concurrency: 1 threads (target='sf')
04:14:14
04:14:14  1 of 1 START test unique_foo_id ................................................ [RUN]
04:14:17  1 of 1 PASS unique_foo_id ...................................................... [PASS in 2.94s]
04:14:17
04:14:17  Finished running 1 test in 0 hours 0 minutes and 6.14 seconds (6.14s).
04:14:17
04:14:17  Completed successfully
04:14:17
04:14:17  Done. PASS=1 WARN=0 ERROR=0 SKIP=0 TOTAL=1

^ Only test on foo is executed.
Using dbt 1.5

Following on from the above steps, change the test back to what it was:

# models/schema.yml
version: 2
models:
  - name: foo
    columns:
      - name: id
        tests:
          - not_null

Remove all remnants of state (and previous state) and rebuild for the first time with 1.5:

$ rm -rf target && rm -rf target_old && dbt build
04:17:16  Running with dbt=1.5.6
04:17:18  Registered adapter: snowflake=1.5.3
04:17:19  Found 2 models, 1 test, 0 snapshots, 0 analyses, 322 macros, 0 operations, 0 seed files, 0 sources, 0 exposures, 0 metrics, 0 groups
04:17:19
04:17:25  Concurrency: 1 threads (target='sf')
04:17:25
04:17:25  1 of 3 START sql table model dbt_jyeo.foo ...................................... [RUN]
04:17:29  1 of 3 OK created sql table model dbt_jyeo.foo ................................. [SUCCESS 1 in 4.27s]
04:17:29  2 of 3 START test not_null_foo_id .............................................. [RUN]
04:17:32  2 of 3 PASS not_null_foo_id .................................................... [PASS in 2.98s]
04:17:32  3 of 3 START sql table model dbt_jyeo.bar ...................................... [RUN]
04:17:35  3 of 3 OK created sql table model dbt_jyeo.bar ................................. [SUCCESS 1 in 3.00s]
04:17:35
04:17:35  Finished running 2 table models, 1 test in 0 hours 0 minutes and 16.10 seconds (16.10s).
04:17:35
04:17:35  Completed successfully
04:17:35
04:17:35  Done. PASS=3 WARN=0 ERROR=0 SKIP=0 TOTAL=3

Do as we do above - modify the test:

# models/schema.yml
version: 2
models:
  - name: foo
    columns:
      - name: id
        tests:
          - unique

Move the state and build with deferral as we did previously:

$ mv target target_old
$ dbt build --select state:modified+ --defer --state target_old
04:19:11  Running with dbt=1.5.6
04:19:12  Registered adapter: snowflake=1.5.3
04:19:13  Found 2 models, 1 test, 0 snapshots, 0 analyses, 322 macros, 0 operations, 0 seed files, 0 sources, 0 exposures, 0 metrics, 0 groups
04:19:13
04:19:19  Concurrency: 1 threads (target='sf')
04:19:19
04:19:19  1 of 2 START test unique_foo_id ................................................ [RUN]
04:19:22  1 of 2 PASS unique_foo_id ...................................................... [PASS in 3.34s]
04:19:22  2 of 2 START sql table model dbt_jyeo.bar ...................................... [RUN]
04:19:25  2 of 2 OK created sql table model dbt_jyeo.bar ................................. [SUCCESS 1 in 3.45s]
04:19:25
04:19:25  Finished running 1 test, 1 table model in 0 hours 0 minutes and 12.19 seconds (12.19s).
04:19:25
04:19:25  Completed successfully
04:19:25
04:19:25  Done. PASS=2 WARN=0 ERROR=0 SKIP=0 TOTAL=2

^ Test on foo is executed but so is bar rebuilt - which is a different behaviour than dbt 1.6.
Relevant log output
No response
Environment
- OS: macOS
- Python: Python 3.9.13
- dbt: dbt-core==1.6.2 dbt-snowflake==1.6.2 / dbt-core==1.5.6 dbt-snowflake==1.5.3

Which database adapter are you using with dbt?
snowflake
Additional Context
There appear to be some changes to state selection (?) in 1.6 https://github.com/dbt-labs/dbt-core/releases/tag/v1.6.0 - not too sure if this is expected or not.

Hello! Thanks for opening this up.
I find the pre-1.5 behavior unexpected. I'm curious if you have a use case for when this would be useful?
If we imagine our dag:
foo -> bar
and we modify or add a new test to foo. Is there any reason we'd want to run bar when we execute dbt build --select state:modified+. Either a) the test on foo fails or b) the test on foo succeeds - but either way, do we actually need to build bar to validate our change? I can't think of a use case where changing/adding a test to foo would change anything about bar.
That being said, I don't know if this change was intended @jtcohen6 do you know? And if it wasn't, we should add a test to ensure we don't break this in the future.


JWT Token Should Contain More Information from Client

JWT token should contain more information from client:
Fields to include

aud - Audience (https://tools.ietf.org/html/rfc7519#section-4.1.3)
jti - JWT ID (https://tools.ietf.org/html/rfc7519#section-4.1.7)
consumerid - Consumer ID (Custom)
consumername - Consumer Username(Custom)

Other fields to also consider

iss - Issuer (https://tools.ietf.org/html/rfc7519#section-4.1.1)
iat - Issued at (https://tools.ietf.org/html/rfc7519#section-4.1.6)

Codebase merged, addresses the issue here.


Cascading Deployment Removal

When calling delete_namespaced_deployment, even with orphaned_dependents (which doesn't mean I think it means), only the deployment object itself gets removed. This means you've got the ReplicaSet and 1 or more Pods still running.
Between garbage collection and ReplicaSet references to the Deployment that created it, there still doesn't seem to be a way to have a delete cascade properly.
Kinda wondering how others are solving the problem and if maybe there needs to be more development in this area either here or upstream. Merely trying to provide a reliable removal function in my application...

you can call delete replicaset and pod alone against label selector

sorry,I can't reproduce the problem. when orphaned_dependents=True, replicaset and pods all gets removed

sorry for wrong reply. you are right.orphaned_dependents takes no effect

doesn't look like a python client issue.  If yes, you can use -v9 with kubectl to see what APIs are called.

On my phone so don't have the link handy but kubectl apparently handles
this itself. I do think you're right in that this is an actual API feature
request more so than a client-python problem.
On Mar 31, 2017 3:14 AM, "Mehdy Bohlool"<EMAIL_ADDRESS>wrote:

doesn't look like a python client issue.  If yes, you can use -v9
with kubectl to see what APIs are called.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/client-python/issues/162#issuecomment-290635693,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABIzFmxgcdpkEvrl00KyuN9KaoQbkcMrks5rrKfngaJpZM4MsaC8
.

I'm having this same issue, and after further investigation have found out that the current (1.6.1) way of doing this is with the parameter propagationPolicy on the DeleteOptions:
k8s documentation
It seems the python client doesn't support this ATM:
v1_delete_options.py
When can we expect this feature to be implemented?

Can you guys give 2.0.0a a try. I've updated python client.

I've tried it, working fine for my application, at least the new options I needed in v1_delete_options.py are working fine.

@vascofg ,Please I tried the function call below, but I was still unable to archive cascading deletion. Can you help me understand what I am not doing right?
extensions.delete_namespaced_deployment(name='nginx-deployment', namespace='default', body=client.V1DeleteOptions(),grace_period_seconds = 56, propagation_policy = \"Background\")

Check this, there's a bug with background deletion of deployments:
https://github.com/kubernetes/kubernetes/issues/44046
Use foreground for now.
On Jun 12, 2017 14:44, "Konrad Djimeli"<EMAIL_ADDRESS>wrote:

@vascofg https://github.com/vascofg ,Please I tried the function call
below, but I was still unable to archive cascading deletion. Can you help
me understand what I am not doing right?
extensions.delete_namespaced_deployment(name='nginx-deployment',
namespace='default', body=client.V1DeleteOptions(),grace_period_seconds =
56, propagation_policy = "Background")
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/client-python/issues/162#issuecomment-307793677,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmuScDkn6BsbX7l7J4oqTq6JS6i9mYUks5sDUDXgaJpZM4MsaC8
.

@vascofg, I have also tried Foreground but it still deletes only the deployment and not it dependents.

I think your error is when creating DeleteOptions, try passing parameters to the object constructor, mine looks like this:
client.V1DeleteOptions(propagation_policy="Foreground", grace_period_seconds=5)

Hope it helps

I have tried extensions.delete_namespaced_deployment(name='nginx-deployment', namespace='default', body=client.V1DeleteOptions(propagation_policy="Foreground", grace_period_seconds=5)), but I am still getting the same result (pods are not deleted). Thanks alot for the help.

Is the replicaset being deleted?
On Jun 13, 2017 15:03, "Konrad Djimeli"<EMAIL_ADDRESS>wrote:

I have tried extensions.delete_namespaced_deployment(name='nginx-deployment',
namespace='default', body=client.V1DeleteOptions(propagation_policy="Foreground",
grace_period_seconds=5)), but I am still getting the same result (pods
are not deleted). Thanks alot for the help.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/client-python/issues/162#issuecomment-308126228,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmuSXbhucUaGy9lM49AkgdgPtXwFVboks5sDpa0gaJpZM4MsaC8
.

No, the replicaset not deleted.

What version of Kubernetes are you running? This feature is only supported
since 1.6.0
On Jun 13, 2017 17:38, "Konrad Djimeli"<EMAIL_ADDRESS>wrote:
No, the replicaset not deleted.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes-incubator/client-python/issues/162#issuecomment-308175921,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAmuSQCCC11xFAW8cPxCf-2b-lYuYSELks5sDrsPgaJpZM4MsaC8
.

@vascofg, Thanks very much, I just updated my version for Kubernetes and it now works fine.


Mr.Chang vending machine wrong texture

its showing up as a shady cig machine instead of mr.chang texture

this needs attention

i have not a goddamn clue how this happened.

The reason for this actually pretty simple. If you look in chang.yml, the inventory prototype for the vending machine, it's currently set to spriteName: cigs. The vending machine inventory prototypes override the sprite of the vending machine that way. To fix this immediately you'd just change that to spriteName: changs, but it's fixed in my vending machine cleanup PR as well because I removed that override mechanism from the inventory prototypes entirely. It's never actually used in any meaningful way and only leads to weird inconsistent behavior like this.

i have not a goddamn clue how this happened.

Yeah it seems to be a new issue because it used to work. I noticed it yesterday.

Yeah it seems to be a new issue because it used to work. I noticed it yesterday.

From the looks of it chang.yml had the wrong spriteName configured ever since it was added but the vending machine visualizer was updated to actually do the sprite replacing a little under a month ago. That'll be when this started happening.


[CI/Build] drop support for  Python 3.8 EOL

As Python 3.8 reaches EOL, this PR would be a starting point to remove potential code branch on 3.8 only.
I'm still working through all of the code, but this would be a starting point for CI.

 PR Checklist (Click to Expand)
Thank you for your contribution to vLLM! Before submitting the pull request, please ensure the PR meets the following criteria. This helps vLLM maintain the code quality and improve the efficiency of the review process.
PR Title and Classification
Only specific types of PRs will be reviewed. The PR title is prefixed appropriately to indicate the type of change. Please use one of the following:

[Bugfix] for bug fixes.
[CI/Build] for build or continuous integration improvements.
[Doc] for documentation fixes and improvements.
[Model] for adding a new model or improving an existing model. Model name should appear in the title.
[Frontend] For changes on the vLLM frontend (e.g., OpenAI API server, LLM class, etc.)
[Kernel] for changes affecting CUDA kernels or other compute kernels.
[Core] for changes in the core vLLM logic (e.g., LLMEngine, AsyncLLMEngine, Scheduler, etc.)
[Hardware][Vendor] for hardware-specific changes. Vendor name should appear in the prefix (e.g., [Hardware][AMD]).
[Misc] for PRs that do not fit the above categories. Please use this sparingly.

Note: If the PR spans more than one category, please include all relevant prefixes.
Code Quality
The PR need to meet the following code quality standards:

We adhere to Google Python style guide and Google C++ style guide.
Pass all linter checks. Please use format.sh to format your code.
The code need to be well-documented to ensure future contributors can easily understand the code.
Include sufficient tests to ensure the project to stay correct and robust. This includes both unit tests and integration tests.
Please add documentation to docs/source/ if the PR modifies the user-facing behaviors of vLLM. It helps vLLM user understand and utilize the new features or changes.

Adding or changing kernels
Each custom kernel needs a schema and one or more implementations to be registered with PyTorch.

Make sure custom ops are registered following PyTorch guidelines: Custom C++ and CUDA Operators and The Custom Operators Manual
Custom operations that return Tensors require meta-functions. Meta-functions should be implemented and registered in python so that dynamic dims can be handled automatically. See above documents for a description of meta-functions.
Use torch.libary.opcheck() to test the function registration and meta-function for any registered ops.  See tests/kernels for examples.
When changing the C++ signature of an existing op, the schema must be updated to reflect the changes.
If a new custom type is needed, see the following document: Custom Class Support in PT2.

Notes for Large Changes
Please keep the changes as concise as possible. For major architectural changes (>500 LOC excluding kernel/data/config/test), we would expect a GitHub issue (RFC) discussing the technical design and justification. Otherwise, we will tag it with rfc-required and might not go through the PR.
What to Expect for the Reviews
The goal of the vLLM team is to be a transparent reviewing machine. We would like to make the review process transparent and efficient and make sure no contributor feel confused or frustrated. However, the vLLM team is small, so we need to prioritize some PRs over others. Here is what you can expect from the review process:

 After the PR is submitted, the PR will be assigned to a reviewer. Every reviewer will pick up the PRs based on their expertise and availability.
 After the PR is assigned, the reviewer will provide status update every 2-3 days. If the PR is not reviewed within 7 days, please feel free to ping the reviewer or the vLLM team.
 After the review, the reviewer will put an  action-required label on the PR if there are changes required. The contributor should address the comments and ping the reviewer to re-review the PR.
 Please respond to all comments within a reasonable time frame. If a comment isn't clear or you disagree with a suggestion, feel free to ask for clarification or discuss the suggestion.

Thank You
 Finally, thank you for taking the time to read these guidelines and for your interest in contributing to vLLM. Your contributions make vLLM a great tool for everyone!

Do we have pyupgrade enabled in the settings for ruff? Would be great if we could use it to get rid of legacy code.

Do we have pyupgrade enabled in the settings for ruff? Would be great if we could use it to get rid of legacy code.

I think we can update to latest ruff and use pyupgrade. But I feel like that introduce a lot of merge conflict for other higher priority PR.
For these CI PR would probably be best to run before releasing a new version. What do you think?
ps: I can add ruff tool, but won't run it if that works better.

Currently we use yapf for formatting, and ruff only for linting. I think adding pyupgrade lint rules should not cause many changes to the code.

I think adding pyupgrade lint rules should not cause many changes to the code.

OK, I stand corrected... maybe we can turn on just a subset of the rules ?

In particular, f-string formatting seems to be responsible for most of the diffs.

yes, will revert 182d0d7

fwiw https://docs.astral.sh/ruff/rules/#pyupgrade-up we can exclude f-string format?

Also are there any specific reason that we locked ruff to 0.1? it is pretty old?

Upgrading ruff may add new rules from the categories that we've currently enabled. Let's do that in a separate PR to avoid introducing a huge amount of diffs.

fwiw https://docs.astral.sh/ruff/rules/#pyupgrade-up we can exclude f-string format?

I think we can add the rules to ignore inside the list in tool.ruff.lint.ignore.

Since we might not want to drop Python 3.8 immediately, it's probably better to work on upgrading ruff first.

#8469 cc @DarkLight1337

Now that Python 3.8 has reached EOL, let's resume work on this.

Heads up that PyTorch 2.5.0 has officially dropped Python 3.8 as well

yep I will revisit this this weekend, sorry work and other stuff got caught up

@aarnphm any update? Otherwise, we'll work on this issue in #10038 instead.

Oh I think I already push on my end

Please fix the linter errors. There are also a couple places where we use sys.version_info, so it would be great if you could prune the 3.8-only branches!

cc @DarkLight1337 PTAL

Please take a look at the doc failure.

There are also a couple places where we use sys.version_info, so it would be great if you could prune the 3.8-only code!

And also this.

Hmm I already remove all sys.version_info compat for 3.8

Hmm I already remove all sys.version_info compat for 3.8

How about sys.version_info < 3.9?

hmm thats weird I thought I already fixed it, anw


Add --logging option

Close #48

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 94.04%. Comparing base (79a7aaa) to head (9d39a79).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #54   +/-   ##
=======================================
  Coverage   94.04%   94.04%
=======================================
  Files          34       34
  Lines        1629     1629
=======================================
  Hits         1532     1532
  Misses         97       97

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Implement Mattermost Webhook in Notifications

At present we have Discord, Slack & Team integration with webhooks. Please implement Mattermost Webhooks next to the existing ones.
You have to work around the web/crux/src/app/notification for the backend and web/crux-ui/src/components/notification for the user interface. Furthermore, you have to extend the protobuff file with the new NotificationType.
Add regexp to check the validation of the webhook URL.
Mattermost Webhook Documentation: https://developers.mattermost.com/integrate/webhooks/incoming/

Hello :)
Can I work on this issue?
I never implemented this and looks like a good challenge. :)
But i probably need more information on your side:

What is you mattermost server?
Do you have incoming webhooks enabled?
Do you have secrets to store sensitive information?

Thanks :)

Hi @bpvcode go ahead, feel free to work on it, don't hesitate to ask if you have any questions, you can find us on Discord.
Here is our demo server, with enabled webhooks. Link: https://dyrectorio.cloud.mattermost.com/

Hi,
Is this issue still open? If so please assign it to me


zebrad terminal user interface improvements

Is your feature request related to a problem? Please describe.
During our first alpha user studies (#1501) users mentioned that the large amount of scrolling logs could be intimidating and a cause for concern with less experienced users.
Describe the solution you'd like
We should review other node software such as zcashd and bitcoind to see if there are any user interface improvements we can apply to zebrad.
We should also investigate using Tui + Termion backend.
Describe alternatives you've considered
Expose less verbose logs by default (#1381)
Additional context
Some users found the amount of logs reassuring as they could understand what was going on and that the node was working correctly

We've already simplified the Zebra logs. We can re-open this ticket if we decide on a terminal for Zebra's user interface.
(We could use a web page or Grafana dashboard instead.)


Add rule to remove leading shell prompt literal $

Rule added to remove leading shell prompt literals found in the command.

I have made the modifications as suggested. However, the non matches were not changed as I realised that the outputs were not the same for every test case.

Looks good, thanks!


Capability System: Set all extension capabilities to include version relationship for culling capabilities accordingly

_GL_EXT_foo = version | GL_EXT_foo is how the capabilities should look.
This will allow us to remove all GL_EXT capabilities implied by a profile target in a entryPoint post processing step.
This means that when we are to convert capabilities to automatic extension setting from capabilities, we won't need redundant extensions.

Currently we use _GL_EXT_FOO to represent the real glsl extension EXT_FOO,
L then we also define a user facing alias GL_EXT_FOO = _GL_EXT_FOO|_SPV_EXT_FOO to mean either the glsl extension or the equivalent spv extension depending on whether the user is targeting glsl or spirv. This setup makes it possible for our users to specify:
-profile spirv+GL_EXT_FOO and we will be able to resolve it to spirv+SPV_EXT_FOO.
We should maintain this setup. I was simply asking us to define GLSL_450 profile such that it implies all extensions for 450:
def glsl450:glsl440, _GL_EXT_FOO, _GL_EXT_BAR, ...
This means that when the user has specified -profile glsl450 they will be able to use ext_foo without having to explicitly specify it again even in restrictive mode. But if they are targeting 430 they will need to do -profile glsl430+_Gl_EXT_FOO.
What is important here is that the canonical representation of glsl450 will contain the _GL_EXT_FOO atom. But we can also know that the atom is implicitly inferred by seeing that the ext atom does not exist in the compacted set.


Supporting using on YAML file that contains secrets for multiple environments

It would be nice if plugins worked with one YAML file, rather than one per stage.
It would work like this:
serverless.yml
custom:
  serverless-kms-secrets:
    secretsFile: kms-secrets.${opt:stage, self:provider.stage}.${opt:region, self:provider.region}.yml (optional)
    perStage: false # defaults to true
  kmsSecrets: ${file(kms-secrets.${opt:stage, self:provider.stage}.${opt:region, self:provider.region}.yml)}

kms-secrets.yml
dev:
  secrets:
      VARIABLE_NAME: encrypted_value
  keyArn: 'arn:aws:kms:us-east-1:514209761729:key/147fa7d3-e22f-486e-b4d0-27d40aa7ae7d'
prd:
  secrets:
      VARIABLE_NAME: encrypted_value
  keyArn: 'arn:aws:kms:us-east-1:514209761729:key/147fa7d3-e22f-486e-b4d0-27d40aa7ae7d'

Thoughts?

You can achieve exactly that by just modifying the config. i.e. by dropping the stage option from the file paths. You can actually define name your file however you want. That’s basis Serverless framework config stuff, nothing specific to the plugin. For example:
custom:
serverless-kms-secrets:
secretsFile: kms-secrets.${opt:region, self:provider.region}.yml
kmsSecrets: ${file(kms-secrets.${opt:region, self:provider.region}.yml)}
would drop the stage from the filename.

On 4 Sep 2019, at 21.43, Miguel Calles<EMAIL_ADDRESS>wrote:
It would be nice if plugins worked with one YAML file, rather than one per stage.
It would work like this:
serverless.yml
custom:
serverless-kms-secrets:
secretsFile: kms-secrets.${opt:stage, self:provider.stage}.${opt:region, self:provider.region}.yml (optional)
perStage: false # defaults to true
kmsSecrets: ${file(kms-secrets.${opt:stage, self:provider.stage}.${opt:region, self:provider.region}.yml)}
kms-secrets.yml
dev:
secrets:
VARIABLE_NAME: encrypted_value
keyArn: 'arn:aws:kms:us-east-1:514209761729:key/147fa7d3-e22f-486e-b4d0-27d40aa7ae7d'
prd:
secrets:
VARIABLE_NAME: encrypted_value
keyArn: 'arn:aws:kms:us-east-1:514209761729:key/147fa7d3-e22f-486e-b4d0-27d40aa7ae7d'
Thoughts?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub https://github.com/nordcloud/serverless-kms-secrets/issues/24?email_source=notifications&email_token=ACABC3DNAAJXUSMU7LSRY6TQH76VXA5CNFSM4ITVHVNKYY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HJKSRFA, or mute the thread https://github.com/notifications/unsubscribe-auth/ACABC3C6MJ4JDZ4N7BJVZI3QH76VXANCNFSM4ITVHVNA.

@mpuittinen, I think a solution like this would benefit users with several environments. https://github.com/nordcloud/serverless-kms-secrets/pull/25


StorageBucket attribute is always empty when adding firebase to webApp

Hello, I am following the steps given on page (using google chrome)
https://codelabs.developers.google.com/codelabs/firebase-web/#3
It says: You've hit a bug. Sorry about that! Close and re-open this dialog and your storageBucket should now be populated.
I have tried this many a times, but doesn't populate the atrribute. The result is I am not able to work with images.
When I browse the project in Firebase console and go to Storage, it gives error: Can't connect to server. Try again in a few minutes. RETRY
What is the solution?

Would you mind filing an issue on our support queue? This sounds like you're falling into an edge case of Storage and we'd like to offer some more personal support.


[MIXCLOUD] youtube-dl hangs on invoking downloader

[x] I've verified and I assure that I'm running youtube-dl 2017.01.16

Before submitting an issue make sure you have:

[x] At least skimmed through README and most notably FAQ and BUGS sections
[x] Searched the bugtracker for similar issues including closed ones

What is the purpose of your issue?

[x] Bug report (encountered problems with youtube-dl)
[ ] Site support request (request for adding support for a new site)
[ ] Feature request (request for a new functionality)
[ ] Question
[ ] Other

$ youtube-dl --print-json --verbose https://www.mixcloud.com/johndigweed/transitions-with-john-digweed-live-from-ministry-of-sound-london-and-raxon/
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: [u'--print-json', u'--verbose', u'https://www.mixcloud.com/johndigweed/transitions-with-john-digweed-live-from-ministry-of-sound-london-and-raxon/']
[debug] Encodings: locale UTF-8, fs utf-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2017.01.16
[debug] Python version 2.7.11 - Darwin-15.6.0-x86_64-i386-64bit
[debug] exe versions: ffmpeg 3.0.2, ffprobe 3.0.2
[debug] Proxy map: {}
{"extractor": "mixcloud", "protocol": "https", "fulltitle": "Transitions with John Digweed live from Ministry of Sound London and Raxon", "id": "johndigweed-transitions-with-john-digweed-live-from-ministry-of-sound-london-and-raxon", "view_count": 538, "playlist": null, "title": "Transitions with John Digweed live from Ministry of Sound London and Raxon", "_filename": "Transitions with John Digweed live from Ministry of Sound London and Raxon-johndigweed-transitions-with-john-digweed-live-from-ministry-of-sound-london-and-raxon.m4a", "playlist_index": null, "thumbnail": "https://thumbnailer.mixcloud.com/unsafe/60x60/extaudio/a/f/0/9/ad67-0166-4e53-8b3c-9304cd609fb9", "webpage_url_basename": "transitions-with-john-digweed-live-from-ministry-of-sound-london-and-raxon", "display_id": "johndigweed-transitions-with-john-digweed-live-from-ministry-of-sound-london-and-raxon", "description": "This week a new hour recorded at the Bedrock 18 party in London plus Raxon returns for a new guest mix.\r\n\r\nProduced and syndicated by theradiodepartment.com", "format": "0 - unknown", "requested_subtitles": null, "uploader": "John Digweed", "format_id": "0", "uploader_id": "johndigweed", "thumbnails": [{"url": "https://thumbnailer.mixcloud.com/unsafe/60x60/extaudio/a/f/0/9/ad67-0166-4e53-8b3c-9304cd609fb9", "id": "0"}], "url": "https://stream9.mixcloud.com/c/m4a/64/3/e/1/d/75d3-812c-42f8-b958-966994dfd604.m4a", "extractor_key": "Mixcloud", "http_headers": {"Accept-Language": "en-us,en;q=0.5", "Accept-Encoding": "gzip, deflate", "Accept": "text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8", "User-Agent": "Mozilla/5.0 (X11; Linux x86_64; rv:10.0) Gecko/20150101 Firefox/47.0 (Chrome)", "Accept-Charset": "ISO-8859-1,utf-8;q=0.7,*;q=0.7", "Cookie": "csrftoken=XxJPuuy5cGtPZzL8L5VMqjI86EW8TMVP; __cfduid=d473cc3af5fb36c49ef560d10b5c350601484749284"}, "ext": "m4a", "webpage_url": "https://www.mixcloud.com/johndigweed/transitions-with-john-digweed-live-from-ministry-of-sound-london-and-raxon/"}
[debug] Invoking downloader on u'https://stream9.mixcloud.com/c/m4a/64/3/e/1/d/75d3-812c-42f8-b958-966994dfd604.m4a'
<end of log>

Description of your issue, suggested solution and other information
When envoking the above command, youtube-dl hangs.

--print-json suppresses progress info.


Return AMC v1 compatible sass as list

Returning the dict as-is means that Open edX needs to worry about converting back into list, which is a concern of the adapter and not Open edX.

Enables: https://github.com/appsembler/edx-platform/pull/1062

@OmarIthawi if we want the values represented as a list, we should be removing these lines here?


Bulk junks from cards like Fission should be able to trigger Glory and Victory special achievements

Only if the player doing the junking has such a card in their hand.

This has since been fixed.


Wager should show decimal places in my bets like it does in active bets and Include $ sign

ok


Feature/lol/fix retry on complete

Connects #306
Solves issues in which jobs were being marked as failed after they were marked as complete.
This partially stemmed from the fact that our heartbeat could in some cases check to see if the EMR cluster was terminated after the cluster returned a success message to the queues but before that message was processed.
To test

Create a job
Wait for job to complete.
Ensure that the "retry" option is not available.
Use admin interface to ensure the failed status is not set and there are no error messages.

@azavea-bot rebuild

+1


ResourceWarning: Unclosed file <tempfile.SpooledTemporaryFile object at 0...> in form handling

reproducer:
import io

import asyncio
import httpx
import anyio
from hypercorn.config import Config
from hypercorn.asyncio import serve
from quart import make_response, request, Quart

app = Quart(__name__)

@app.route("/upload", methods=["POST", "OPTIONS"])
async def pyodide_upload():
    if request.method == "OPTIONS":
        return await make_response("", 200)
    spare_data = await request.get_data(parse_form_data=True)
    if len(spare_data) != 0:
        return await make_response("Bad upload data", 404)
    files = await request.files
    form = await request.form
    if form["upload_param"] != "filefield" or form["upload_filename"] != "lolcat.txt":
        return await make_response("Bad upload form values", 404)
    if len(files) != 1 or files.get("filefield") is None:
        return await make_response("Missing file in form", 404)
    file = files["filefield"]
    if file.filename != "lolcat.txt":
        return await make_response(f"File name incorrect {file.name}", 404)
    data = file.read().decode("utf-8")
    if data != "I'm in ur multipart form-data, hazing a cheezburgr":
        return await make_response(f"File data incorrect {data}", 200)
    return await make_response("Uploaded file correct", 200)

config = Config()
config.bind = ["localhost:8080"]  # As an example configuration setting

async def main():
    async with anyio.create_task_group() as tg:
        tg.start_soon(serve, app, config)

        async with httpx.AsyncClient() as client:
            data = b"I'm in ur multipart form-data, hazing a cheezburgr"
            with io.BytesIO(data) as bio:
                files = {"filefield": ("lolcat.txt", bio)}
                await client.post(
                    "http://localhost:8080/upload",
                    files=files,
                    data={"upload_param": "filefield", "upload_filename": "lolcat.txt"},
                )

        tg.cancel_scope.cancel()

asyncio.run(main())

with the requirements:
#
# This file is autogenerated by pip-compile with Python 3.12
# by the following command:
#
#    pip-compile
#
aiofiles==23.2.1
    # via quart
anyio==4.2.0
    # via httpx
attrs==23.1.0
    # via
    #   outcome
    #   trio
blinker==1.7.0
    # via
    #   flask
    #   quart
certifi==2023.11.17
    # via
    #   httpcore
    #   httpx
click==8.1.7
    # via
    #   flask
    #   quart
exceptiongroup==1.2.0
    # via
    #   hypercorn
    #   quart-trio
flask==3.0.0
    # via quart
h11==0.14.0
    # via
    #   httpcore
    #   hypercorn
    #   wsproto
h2==4.1.0
    # via hypercorn
hpack==4.0.0
    # via h2
httpcore==1.0.2
    # via httpx
httpx==0.26.0
    # via -r requirements.in
hypercorn[trio]==0.15.0
    # via
    #   -r requirements.in
    #   quart
    #   quart-trio
hyperframe==6.0.1
    # via h2
idna==3.6
    # via
    #   anyio
    #   httpx
    #   trio
itsdangerous==2.1.2
    # via
    #   flask
    #   quart
jinja2==3.1.2
    # via
    #   flask
    #   quart
markupsafe==2.1.3
    # via
    #   jinja2
    #   quart
    #   werkzeug
outcome==1.3.0.post0
    # via trio
priority==2.0.0
    # via hypercorn
quart==0.19.4
    # via quart-trio
quart-trio==0.11.1
    # via -r requirements.in
sniffio==1.3.0
    # via
    #   anyio
    #   httpx
    #   trio
sortedcontainers==2.4.0
    # via trio
trio==0.23.2
    # via
    #   -r requirements.in
    #   hypercorn
    #   quart-trio
werkzeug==3.0.1
    # via
    #   flask
    #   quart
wsproto==1.2.0
    # via hypercorn

running with -W error results in:
python -W error demo_resource_warning.py
[2023-12-21 10:17:53 +0000] [547211] [INFO] Running on http://<IP_ADDRESS>:8080 (CTRL + C to quit)
Exception ignored in: <function SpooledTemporaryFile.__del__ at 0x7f2f726fe980>
Traceback (most recent call last):
  File "/usr/lib/python3.12/tempfile.py", line 876, in __del__
    _warnings.warn(
ResourceWarning: Unclosed file <tempfile.SpooledTemporaryFile object at 0x7f2f718cc850>

Environment:

Python version: 3.11
Quart version: 0.19.4

Fixed in 1fb23b7e156e5cd1d37f87abe794f51694d08952


image in week editor

Describe your bug here.
when i put my image in the \assets\images\storymenu folder and type it in the week editor it still says not found

Command Prompt/Terminal logs (if existing)
No response
Are you modding a build from source or with Lua?

[X] Lua
[ ] Source

What is your build target?

[X] Windows
[ ] Linux
[ ] Mac
[X] HTML5
[ ] Flash/Air-based target
[ ] Neko, HashLink, or other build system

Did you edit anything in this build? If so, mention or summarize your changes.
nothing other than png images and a few songs

I think it needs to be in the Mods Folder.

you have to put the week image in the mods/images/storymenu folder
it's not a bug.