Backtest impossible when trader is enabled (and no paper trader)

Note: this is the technical bug tracker, please use other platforms for getting support and starting a (non technical) discussion. See the getting help page for details.
I'm submitting a ...
[X] bug report
[ ] question about the decisions made in the repository
Action taken (what you did)
Perform a backtest, trader enabled and paper trader disabled in config.
Expected result (what you hoped would happen)
Peform a backtest
Actual result (unexpected outcome)
3x times error in console: Performance Analyzer wanted to listen to the undefined, however the  is disabled.
Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)
The workaround is to enable to paper trader (and trader) while in backtest mode - then it completes fine. But this config with both traders enabled will not work in realtime mode (and should not of course).

Do you encounter this in the UI or using the CLI interface?

Yes, this happens with CLI version (right now I am not using UI anymore).

The CLI interface is a bit lower level: you do need to manually configure all plugins you intend to run. And the trader (live trading plugin) is not supported when doing backtests.
To work around your issue, it's best to use different config files for each gekko instance, you basically have 3 options:

use 1 file and edit it every time just before you run the Gekko (which you call the workaround). Since the config is only imported once and kept in memory for as long as the gekko runs.

copy your main config file into another file and switch the trading plugin here.

create a new js file where you import your main config file and overwrite the plugin settings, example:
const config = require('main-config.js');
config.trader.enabled = fales;
config.paperRrader.enabled = true;
// change whatever else you want different
module.exports = config;

I don't really consider this is a bug, since the CLI interace (and config file) is supposed to be very low level. And I don't want Gekko to go and enable plugins you did not enable yourself. But if you have other ideas I am all open, first thing would be better documentation around this stuff.

I like your third approach with config import.
The problem is, Gekko will run backtest mode without the paper trader enabled, gives lot of debug output, but never returns a backtest result. I think most users do not know what to do.
I have commited two small changes to inform the user and prevent misconfigured runs:
In backtest.js:
if(!config.paperTrader.enabled)
util.die('You need to enable the "Paper Trader" first to run a backtest.')
In trader.js:
if(config.trader.enabled && config.paperTrader.enabled) {
//this can only happen in realtime mode - during backtest the trader is disabled by design
util.die('You can not run Gekko in realtime mode with both "Paper Trader" AND "Trader" enabled.')
}

I think your second case is already catched by gekko (in core/pipeline.js)
a little bit more abstractly: if there are 2 plugins that emit the same
event gekko won't run. I remember testing this in 0.6, but might need to
recheck.
As for your first case: it's not really documented, but a lot of people use
the backtesting mode for a lot more. For example for quickly writing
candles to disk or importing from 1 DB to another. As the backtesting mode
will read candles from the DB as fast as whatever plugins can consume them.
We can definitely put a warning in there, but not stop the process.
On Fri, 13 Jul 2018, 18:21 Mark Sch<EMAIL_ADDRESS>wrote:

I like your third approach with config import.
The problem is, Gekko will run backtest mode without the paper trader
enabled, gives lot of debug output, but never returns a backtest result. I
think most users do not know what to do.
I have commited two small changes to inform the user and prevent
misconfigured runs:
In backtest.js:
if(!config.paperTrader.enabled)
util.die('You need to enable the "Paper Trader" first to run a backtest.')
In trader.js:
if(config.trader.enabled && config.paperTrader.enabled) {
//this can only happen in realtime mode - during backtest the trader is
disabled by design
util.die('You can not run Gekko in realtime mode with both "Paper Trader"
AND "Trader" enabled.')
}
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/askmike/gekko/issues/2303#issuecomment-404792409, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AA7MD1jwUqDbUJ0fl6wS22Mfb6auofhNks5uGHS6gaJpZM4VM84i
.


[Duplicate of #5628] How to make a switch-case statement in Python

Proposed title of the article
How to make a switch-case statement in Python
Proposed article introduction
A switch statement enables a parameter to be compared against a set of attributes for equality. The switch statement is used in many programming languages, including C++, Visual Basic, Java, Ada, and others. It is a powerful programming tool that lets you change the flow of your program based on the value of a variable or expression. In this article, we will look at how to implement switch-case statements in python through various methods and demonstrate with program examples e.g using if-elf-else, dictionaries and classes. We will also look at the advantages of implementing switch cases
Key takeaways
What is a switch case statement
Example of a switch statement
advantages of using a switch case statement.
Methods to implement switch-case in python.
Programs to implement switch-case in python.
Advantages of implementing switch-case in python.
Disadvantages of implementing switch-case in python.
Article quality
This article is unique since it covers a unique topic. Switch case statement does not exist in python but in this article, we will look at ways on how to implement it using various methods.
References
N/A

Unfortunately, this topic appears to be over-saturated on numerous blog sites. A switch-case statement can easily be found in the documentation. Feel free to suggest another topic.


Cannot read property 'onDidOpenNotebookDocument' of undefined

Environment data

Language Server version: 2021.6.0
OS and version: linux x64
Python version (and distribution if applicable, e.g. Anaconda):
python.analysis.indexing: true
python.analysis.typeCheckingMode: off

Expected behaviour
no errors, the language server works
Actual behaviour
it doesn't work
Logs
Error 2021-06-03 10:45:07: Failed to restart language server, Class name = r, completed in 1ms, has a falsy return value, , Return Value: undefined [TypeError: Cannot read property 'onDidOpenNotebookDocument' of undefined
	at l.get onDidOpenNotebookDocument [as onDidOpenNotebookDocument] (/home/adrian/.vscode-server-insiders/extensions/ms-python.python-2021.6.897246044-dev/out/client/extension.js:78:180756)
	at new a (/home/adrian/.vscode-server-insiders/extensions/ms-python.python-2021.6.897246044-dev/out/client/extension.js:59:183978)
	at new t.NotebookMiddlewareAddon (/home/adrian/.vscode-server-insiders/extensions/ms-python.python-2021.6.897246044-dev/out/client/extension.js:59:178815)
	at new y (/home/adrian/.vscode-server-insiders/extensions/ms-python.python-2021.6.897246044-dev/out/client/extension.js:9:446239)
	at r.startLanguageServer (/home/adrian/.vscode-server-insiders/extensions/ms-python.python-2021.6.897246044-dev/out/client/extension.js:59:240168)
	at processTicksAndRejections (internal/process/task_queues.js:93:5)]

This a dupe of https://github.com/microsoft/vscode-jupyter/issues/6108. See comment https://github.com/microsoft/vscode-jupyter/issues/6101#issuecomment-854043224

This has been resolved. https://github.com/microsoft/vscode-python/suites/2904962837/artifacts/65133411 should contain the fix if you'd like to try it out now (you should get the same build if you're opted into daily insiders builds for the Python extension).


Plan pre-event activities to promote Design System Day

What
Plan the topics of the micro blogs we want to publish on Medium in the run up to Design System Day 2022.
Why
To ensure we have momentum in promoting the event.
Who needs to work on this
TBD
Who needs to review this
TBD
Done when

[ ] Topics planned
[ ] Authors identified
[ ] Publication timetable put together

Agreed we will not run these


Support for remote debugging of tests should be added

Description:
At the moment, tests cannot be debugged using remote debugging. This should be supported.

This is fixed in latest master.


Add caching of google maps instance

I currently have the case where I call loadGoogleMapsAPI on a component level. If the component exists multiple times, lgma will try to add multiple script tags to the page, which the google maps api doesn't seem to like.
Thus I've added a very simple layer of caching to prevent that problem from happening.

@nilssolanki Thanks for this.
I’m of the mind that we should only be calling loadGoogleMapsAPI at the top-level, not at the component-level. I don’t think caching should be the purview of this module.
Furthermore, we can support your specific use case by writing a simple wrapper:
// loadGoogleMapsAPIWithCaching.js

import loadGoogleMapsAPI from 'load-google-maps-api'

let cachedGoogleMapsAPI = null

export default () => {
  if (cachedGoogleMapsAPI) {
    return Promise.resolve(cachedGoogleMapsAPI)
  }
  return new Promise((resolve, reject) => {
    return loadGoogleMapsAPI().then((googleMaps) => {
      cachedGoogleMapsAPI = googleMaps
      return resolve(googleMaps)
    }).catch((error) => {
      return reject(error)
    })
  })
}

I wrote a similar workaround as well.

I’m of the mind that we should only be calling loadGoogleMapsAPI at the top-level, not at the component-level. I don’t think caching should be the purview of this module.

This is a good principle, but doesn't always work. In my case, we had different pages, some of which contained a map component, other didn't. This means I didn't want to load it at the top-level, as it might be unnecessary.
But either way, this is your module, so it's your decision.

I think that it is missing wisheable feature since we use it as async loader.


[FEATURE] Provide guidance on how to use ArgoCD with private AKS

Create a new folder in scenarios called DevOps-GitOps-with-ArgoCD-GHActions and provide instructions on how to configure ArgoCD for continuous delivery. Reference this documentation in AAC.

Have user start from using the all-in-one option to deploy the private AKS environment
Have them installed ArgoCD in their cluster
Use ArgoCD to deploy this simple app (they might have to fork the repo)
make changes to the app and show how that changed triggered GitHub Actions to deploy to the ACR and ArgoCO to pull from ACR.

make this use argocid and github actions to deploy this: https://github.com/Azure/AKS-Landing-Zone-Accelerator/blob/main/Scenarios/AKS-Secure-Baseline-PrivateCluster/Bicep/07-workload.md


Set Holocene Mainnet Superchain activation

Setting Holocene Mainnet activationt to

Thu 09 Jan 2025 18:00:01 UTC
unix timestamp<PHONE_NUMBER>

Chains covered by superchain time inheritance are:

Base
OP
Orderly
Lyra
Metal
Mode
Zora

All other mainnet chains will not inherit the activation, unless they join superchain activation times by setting their superchain_time.
In draft until confirmed that all chains that want to join superchain upgrades are covered.

Detected nonzero diff in rollup config. This PR modifies the configuration of at least one chain in the registry, which may or may not have been intended. You can see the detail here.

Detected nonzero diff in genesis. This PR modifies the genesis data of at least one chain in the registry, which may or may not have been intended. You can see the detail here.

@sebastianst double confirming all good on our end. all the superchain registered chain have the superchain_time set and will fork in january

@sebastianst double confirming all good on our end. all the superchain registered chain have the superchain_time set and will fork in january

Thanks @emilianobonassi
The following chains have a granite_time and are therefore candidates for joining Superchain Holocene activations:

Lisk :white_check_mark:
Shape :question:
Worldchain :question:
Ethernity :white_check_mark:
Binary :question:

✅ -> got feedback/PR for inclusion
❓ -> waiting for feedback
cc @ZakAyesh


Cleanup UrlReader related classes

While looking into error handling for FileUrlReader I found some unused and/or empty methods.
Created a separate PR for this so it is easier to review (and cherry-pick if any changes are unwanted).

Coverage increased (+0.02%) to 54.687% when pulling 62f958765de277541306920dff91d717dea99ed1 on dennisschagt:feature/urlreader-cleanup into ddb8d8c192a01be031c16e470b3e332e9a88058a on newsboat:master.


[Card group] Prod QA testing

User Story

As a [user role below]:
developer using the ibm.com Library Card group

I need to:
have a version of the pattern or component that has been tested for accessibility compliance as well as on multiple browsers and platforms

so that I can:
be confident that my ibm.com web site users will have a good experience

Additional information

Browser Stack link
Browser Standard
Browser versions to be tested:  Tier 1 browsers will be tested with defects created as Sev 1 or Sev 2.  Tier 2 browser defects will be created as Sev 3 defects.
Platforms to be tested, by priority:  1)  Desktop  2)  Mobile  3)  Tablet
Mobile & Tablet iOS versions: 13.1, 13.3 and 14
Mobile & Tablet Android versions: 9.0 Pie and 8.1 Oreo
Browsers to be tested:  Desktop: Chrome, Firefox, Safari, Edge, Mobile: Chrome, Safari, Samsung Internet, UC Browser, Tablet: Safari, Chrome, Android
Accessibility Checklist
Creating a QA bug
See the Epic for the Design and Functional specs information
Only test the Web Components version.  The React version will be developed later.
DDS Card Group Box folder link
Web Components Dev issue (#5280 )
Once development is finished the updated code is available in the Web Components Canary Environment for testing.

Acceptance criteria

[ ] Accessibility testing is complete.  Component is compliant.
[ ] All browser versions are tested
[ ] All operating systems are tested
[ ] All devices are tested
[ ] Defects are recorded

@Praveen-sr This component is ready to be tested.  This work should be done before the regression testing.  Thanks.

Prod QA testing started.

Testing finished.  Can be closed.


Remove deprecated samples from the issue template

The issue template still lets you file issues against samples we don't support anymore. Those entries should be removed.

Related: #793
Reach out to me if you need any help figuring out the issue template yaml.


Added 复復複覆 entries from CC-CEDICT & HYDCD-Word

+354 复復複覆 added to TSPhrases. Could be added to STPhrases later.


Increase javascript files limit

I work on a project that at last count uses just a little over 2000 js files - excluding compiled/generated files and third party (vendor) files like jquery, etc.  No matter how I configure jsconfig.json, I always get the too many files error.
"Sorry, but there are too many JavaScript source files for VS Code. Consider using the exclude-property in jsconfig.json".
I use Brackets on a daily basis for my projects and occasionally Sublime text, and neither of those two choke on the number of files in my project, granted neither implement intellisense. Is there anyway this can be adjusted or the limit increased?
On the off chance I'm just not configuring jsconfig.json correctly, I'm open to suggestions

We will move to project Salsa this month so that this request becomes obsolete

Can we suppress that warning for now?

only at the risk of crashing VS Code...

But with that warning popping up every 10 seconds the IDE is simply unusable. Is there no workaround at the moment, other than telling it to ignore parts of the solution?

@ig16022 Your setup will be a great test case for the new Salsa JS infrastructure that will become available as preview early next week. I'll include instructions here once a preview build is available.

I'm looking forward to it.

@ig16022 it is now available, please give it a try.
See https://blogs.msdn.microsoft.com/vscode/2016/02/01/introducing-insiders-builds/ for how to get the insider bits
See https://github.com/Microsoft/vscode-docs/blob/vnext/release-notes/latest.md for how to enable Salsa.


Setup config/app.php file in laravel 5 .1

Hi, how add code in config/app.php file in provide array     'Zizaco\Entrust\EntrustServiceProvider' and in aliases array 'Entrust' => 'Zizaco\Entrust\EntrustFacade'.

Go to the file config/app.php and add Zizaco\Entrust\EntrustServiceProvider::class, to the end of the array, it should be around line 147.
Then lower down add 'Entrust' => 'Zizaco\Entrust\EntrustFacade', at the end at about line 200.
This is not an issue though, if I was you I would do some more reading of the Laravel docs as this will need to be done for almost every package you add.


+1 VAT Provider w/ 40+ countries rules, fix #591

I had to handle backward compatibility on

src/Faker/Provider/at_AT/Payment.php, vatmethod
src/Faker/Provider/bg_BG/Payment.php, vatmethod

I propose to tag them as @deprecated. Existing unit tests are maintained.

May fix #591 too

TODO: "regexify is the slowest of all generators. Can't you achieve the same result with ### and ***?"

This supersedes the taxpayerIdentificationNumber() method from src/Faker/Provider/pl_PL/Payment.php.

This generator looks similar to iban. Maybe a similar countries format can be used instead of regexps?

Could I somehow help @ronanguilloux  with this PR? I'd like to see it merged.

Hi @nineinchnick, sure of course.
I've been too busy lately to continue this PR, but feel free to fork my ronanguilloux:VAT-anyone branch and add your own contrib, and then re-PR to the main Faker repo right from your fork. No need to credit my part of it.

Abandoned, closing.


Not reconnecting when MQTT broker not available

I have MQTT-IO on a different system from where MQTT is installed.
If I have to reboot the raspberry pi where MQTT is running, MQTT-IO is loosing connection but not trying to connect anymore.
When MQTT broker come up, any event MQTT-IO tries to publish is reporting the following error:
2021-03-15 08:07:40 mqtt_io.server [INFO] Digital input 'alarm_out1' value changed to False
2021-03-15 08:07:40 mqtt_io.server [ERROR] Exception while handling MQTT task:
Traceback (most recent call last):
  File "/home/pi/.local/lib/python3.7/site-packages/mqtt_io/server.py", line 996, in _mqtt_task_loop await entry.coro
  File "/home/pi/.local/lib/python3.7/site-packages/mqtt_io/server.py", line 635, in _mqtt_publish await self.mqtt.publish(msg)
  File "/home/pi/.local/lib/python3.7/site-packages/mqtt_io/mqtt/asyncio_mqtt.py", line 76, in publish topic=msg.topic, payload=msg.payload, qos=msg.qos, retain=msg.retain
  File "/usr/local/lib/python3.7/dist-packages/asyncio_mqtt/client.py", line 128, in publish raise MqttCodeError(info.rc, 'Could not publish message')
asyncio_mqtt.error.MqttCodeError: [code:4] Could not publish message
2021-03-15 08:14:04 mqtt_io.server [INFO] Waiting for our tasks to complete...
Traceback (most recent call last):
  File "/usr/lib/python3.7/runpy.py", line 193, in _run_module_as_main "__main__", mod_spec)
  File "/usr/lib/python3.7/runpy.py", line 85, in _run_code  exec(code, run_globals)
  File "/home/pi/.local/lib/python3.7/site-packages/mqtt_io/__main__.py", line 38, in <module> main()
  File "/home/pi/.local/lib/python3.7/site-packages/mqtt_io/__main__.py", line 33, in main mqtt_gpio.run()
  File "/home/pi/.local/lib/python3.7/site-packages/mqtt_io/server.py", line 1174, in run self.loop.run_until_complete(self._main_task)
  File "/usr/lib/python3.7/asyncio/base_events.py", line 584, in run_until_complete return future.result()
  File "/home/pi/.local/lib/python3.7/site-packages/mqtt_io/server.py", line 1168, in run await self.shutdown()
  File "/home/pi/.local/lib/python3.7/site-packages/mqtt_io/server.py", line 1229, in shutdown wait=False,
  File "/home/pi/.local/lib/python3.7/site-packages/mqtt_io/server.py", line 635, in _mqtt_publish await self.mqtt.publish(msg)
  File "/home/pi/.local/lib/python3.7/site-packages/mqtt_io/mqtt/asyncio_mqtt.py", line 76, in publish topic=msg.topic, payload=msg.payload, qos=msg.qos, retain=msg.retain
  File "/usr/local/lib/python3.7/dist-packages/asyncio_mqtt/client.py", line 128, in publish raise MqttCodeError(info.rc, 'Could not publish message')
asyncio_mqtt.error.MqttCodeError: [code:4] Could not publish message

Thanks for the report. I was supposed to link into this at the weekend but I had to work on something else. It's a high priority and I'll try to get it fixed soon.

Very cool that this is already a known issue.
Just wanted to comment that yesterday I noticed the same issue in my setup.
I got this behavior as I updated my mosquitto (via apt) to a new version. The mosquitto is restarted due to the update and therefore not available for a very short time. mqtt-io results in the above behavior.

I’ve upgraded Mqtt-io to 2.1.8 but is neither reconnecting after disconnession nor accepting the new configuration parameter for delay in reconnecting and reconnecting count.
Is the version correct? I’m not too much familiar with python, is there any cache to clean? From pip3 I forced Mqtt-io==2.1.8 and it looks installed (and removed the 2.1.7).
Thanks for your work.
Marco

Il giorno 21 apr 2021, alle ore 23:24, Ellis Percival @.***> ha scritto:

Closed #187 via #207.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Ah, so this is because the documentation follows the develop branch and I haven't released a new version with the reconnect code yet. I'll need to put some versioning on the docs I reckon. I have some more work to do before I can release that, but you're welcome to try the develop branch in the meantime.

This reconnection code is released in version 2.2.6 but it's maybe still a little buggy. Please do try it out and report back if you have any issues.

@flyte This still seems to not work properly.
If I restart my broker (Mosquitto 6.1.1) mqtt_io does not notice this. therefore Events in topics (inserted by other applications) are ignored by mqtt_io until restarted.
My config:
mqtt:
  host: hass.homenet
  user: rpi-electric-box
  password: "*secret*"
  topic_prefix: mqtt-io/rpi-electric-box
  ha_discovery:
    enabled: yes
  keepalive: 3
  reconnect_delay: 1
  reconnect_count: 0

# GPIO
gpio_modules:
  # Use the Raspberry Pi built-in GPIO
  - name: rpi
    module: raspberrypi

digital_inputs:
  # Pin 0 is an input connected to a doorbell button
  - name: doorbell
    pulldown: true
    bouncetime: 2000
    module: rpi
    pin: 4
    ha_discovery:
      component: binary_sensor
      name: Doorbell
      device_class: motion

digital_outputs:
  # Pin 1 is an output connected to a light
  - name: door_buzzer
    module: rpi
    initial: 'high'
    publish_initial: true
    inverted: true
    timed_set_ms: 2500
    pin: 17
    ha_discovery:
      component: switch
      name: Stairwell Buzzer

mqtt_io log (with broker restarts inserted)
2022-05-04 11:38:18 mqtt_io.server [INFO] Digital input 'doorbell' value changed to False
2022-05-04 11:38:18 mqtt_io.server [INFO] Connecting to MQTT...
2022-05-04 11:38:18 mqtt_io.server [INFO] Connected to MQTT
2022-05-04 11:38:18 mqtt_io.server [INFO] Subscribed to topic: 'mqtt-io/rpi-electric-box/output/door_buzzer/set'
2022-05-04 11:38:18 mqtt_io.server [INFO] Subscribed to topic: 'mqtt-io/rpi-electric-box/output/door_buzzer/set_on_ms'
2022-05-04 11:38:18 mqtt_io.server [INFO] Subscribed to topic: 'mqtt-io/rpi-electric-box/output/door_buzzer/set_off_ms'

MQTT BROKER STOPPED: Wed  4 May 11:39:45 CEST 2022
...no new log lines in mqtt_io log...
MQTT BROKER STARTED: Wed  4 May 11:40:10 CEST 2022
...no new log lines in mqtt_io log...
at Wed  4 May 11:42:03 CEST 2022 still no reconnect attempt (it somehow must think it still has a connection? So what is the keepalive doing?)

restarting mqtt_io resolves the issue and it connects again.
any ides? I tried clean_session aswell as different values for keepalive, reconnect_delay and reconnect_count


Modification to Backtrace to use output ranges instead of File.

I would like to have considered some changes to the backtrace module.
Generally I have refactored the module to use output ranges instead of File. The changes are as follows:

Refactored private printPrettyTrace to use output ranges instead of File.
Added function printPrettyTrace(OR)(ref OR output ...)
Modified printPrettyTrace to call private printPrettyTrace using File.lockingTextWriter.
BTTraceHandler now implements opApply to use the delegates provided.
BTTraceHandler now implements toString.
runtimeOutputFile has been removed as it is not used.
A new install function that doesn't take a File is provided.

Note that opApply will not notice break statements. To do this would require printPrettyTrace to be refactored again to act as an input range (Although I have since thought of a 'quick and dirty' solution).
Thank you for your consideration
Regards
Jason

LGTM in general. Thanks.

Hi yazd.
Thanks for taking the time to review my changes.
When the exception/error is uncaught and the runtime generates the output, it adds a newline to each iteration. This was the reason why I added insertNewLines and the buffers as I did. (At one point the runtime was printing a single character on each line :)).
I made another modification (please let me know if I ever go too far). printPrettyTrace now puts it all into a string and returns it. Outputting it is now trivial, and has the effect of the opApply now working correctly.
I'm not sure how to reverse or update a pull request. Do I just commit my changes and create a new pull request?
Regards
Jason

You can just commit the new changes. Preferably you can squash the commits as well and force push but don't think of it as a requirement.

Hi. I've uploaded the new changes. As I said, it now just returns a string, which can be sent anywhere. The BTTraceHandler.opApply function is now idiomatically correct.
I also added a sample program to demonstrate Backtrace.
Thank you for this extremely useful tool.
Regards
Jason

Sorry, I accidentally closed the thread.

All looks good, I will merge once I test.
Sorry for the delay.


add hjkl bindings to change slides

Adds vim-ish keybindings for navigating slides. Thanks!

yeah okay

merged into 1.1.0

whoop, thanks! :tada:


change arguments to dynamic (roadmap)

Fixes #441
I understand Object was used, because Flutter's Route arguments uses it. Yet, seems it will not bring any breaking change, beyond removing all type checking to the arguments property. So, it gives full freedom (and responsibility) to the developer to make the proper validations.

Check responses in (we might need to validate the usage of extension methods over dynamic):
https://stackoverflow.com/questions/31257735/what-is-the-difference-between-dynamic-and-object-in-dart#:~:text=Writing dynamic o%3B declares a,except that it's an Object .

if i do remember correctly, i think a long ago it was Objects, but it was giving problems when the argument was a list or a Map
although it was so long ago that i'm not sure if i'm right
@jonataslaw do you remember something like that?

In the past it was dynamic, but for the sake of standardization I switched to Object, because Flutter uses it as Object.
Well, I have nothing against this change at the moment, and it can allow more flexibility, so LGTM.
Thank you Roi!


Add documentation for using default values with triggers

Harness Developer Pull Request
Thanks for helping us make the Developer Hub better. The PR will be looked at
by the CODEOWNERS.
What Type of PR is This?

[ ] Issue
[ ] Feature
[x] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)
https://harness.atlassian.net/browse/CDS-84396

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app


Improve import of films

Support log ID:
NG993Q6V-euc
Full Bib(La)TeX item you are trying to import:
@movie{Marka.S:2011a,
	date-added = {2020-09-16 13:56:16 +0200},
	date-modified = {2020-09-16 13:56:52 +0200},
	director = {Sebastian Marka},
	location = {DE},
	read = {1},
	title = {Interview},
	year = {2011}}

Expected behavior:
At the moment, import of films is severely limited. BBT does not recognise the type @movie. It only handles @film correctly, although biblatex does not know about this type.
In @film entries, the field location (and address) is not handled properly. It is imported as Extra: tex.location instrad of Extra: Publisher place. Interestingly, export does work correctly: When exporting a film from Zotero, Extra: Publisher place ends up as location.
Actual behavior:
Map @movie to film, map location to Extra: Publisher place.

More in general: There are several of biblatex's orig fields for which equivalents exist in the Zotero's extra field, but which are currently not mapped properly on import. Shall I open new bugs for these?

More in general: There are several of biblatex's orig fields for which equivalents exist in the Zotero's extra field, but which are currently not mapped properly on import. Shall I open new bugs for these?

That can be handled under this issue, no problem.

Map @movie to film

A new build will drop here shortly that fixes that

map location to Extra: Publisher place

I'll look into this. Mapping these fields is a little trickier.

Why Publisher place rather than Place?

Why Publisher place rather than Place?
Ah sorry, I didn't realise Place works as well. In the Zotero forums, I only found references to the former.

It would also probably be good to map biblatex's @video to film.
As for the additional mapping. I am not sure, what is already handled by BBT, but the following mappings would make sense
original-date ⇿ origdate
original-publisher ⇿ origpublisher
original-publisher-place ⇿ origlocation
original-title ⇿ `origtitle

Something else I've noticed: At the moment, BBT collapses title and subtitle into Zotero's title field on import and joins them with a hyphen.
Is this documented somewhere? And would it be possible to add the possibility to configure how these fields are joined?

Why Publisher place rather than Place?

Ah sorry, I didn't realise Place works as well. In the Zotero forums, I only found references to the former.
It would also probably be good to map biblatex's @video to film.
As for the additional mapping. I am not sure, what is already handled by BBT, but the following mappings would make sense
original-date ⇿ origdate
original-publisher ⇿ origpublisher
original-publisher-place ⇿ origlocation
original-title ⇿ origtitle

Can you construct a testcase for these? Field mappings are not uniform  across types, so I always prefer to have concrete test cases.

I just realised that the mapping does work one way: original entries Zoteros Extra field are correctly mapped when exported to BibLaTeX, but not the other way round. orig fields in .bib files end up as tex… in Zoteros Extra field.
Here's an example:

@book{Roy.O:2017a,
location = {New York},
author = {Roy, Olivier},
origdate = {2016},
origlanguage = {french},
origlocation = {Paris},
origtitle = {Le djihad et la mort Le djihad et la mort},
publisher = {Oxford University Press},
subtitle = {The Global Appeal of Islamic State},
title = {Jihad and Death},
translator = {Schoch, Cynthia},
year = {2017}}

I normally don't use origpublisher.

I only have the following Zotero-supported orig fields:

Original date
Original publisher
Original publisher place
Original title

So I don't have a place for origlanguage

So I don't have a place for origlanguage

That is correct, AFAIK.
Thanks for taking care of this so quickly, this is simply amazing.
Something I noticed which I did not realise before: With @movie, the author field is now mapped to Contributor.
I understand that, by default, @movie is basically undefined in biblatex. My own style biblatex-fiwi is, to my knowledge, the only one with extensive support for films. While I have added the field director which does not exist in standard biblatex , the default for director is author. I have also added scriptwriter which is mapped to editor. So maybe it would make sense to add the following:
author/director ⇿  director
editor/scriptwriter ⇿  scriptwriter
Here's an example:
@movie{Ball.W:2014a,
	address = {US},
	author = {Ball, Wes},
	editor = {Noah Oppenheim and Grant Pierce Myers and T.S. Nowlin},
	title = {The Maze Runner},
	year = {2014}}

Hi,
It's not clear to me whether we're addressing import or export currently. The bidi arrows aren't always helpful, as the transformation between bib(la)tex can't be entirely without loss of information about the context in which a field was used. I try to get roundtrippable import/export, but it's not a hard target.
Easiest for me actually is:
import:

paste the bib(la)tex to import here
import and edit it in zotero to have it look like you want
right-click the item and send a debug log from the popup menu, and paste the log id next to the input sample

this will give me exactly what you have so we can forego guessing and descriptions.
export

export the entry from Zotero to bib(la)tex and edit the things you'd like to see differently
paste the result here
right-click the entry you exported and send a log from the popup menu
paste the log ID next to the sample entry

import:
@movie{Ball.W:2014a,
	address = {US},
	author = {Ball, Wes},
	editor = {Noah Oppenheim and Grant Pierce Myers and T.S. Nowlin},
	title = {The Maze Runner},
	year = {2014}}

Support log ID: LBJE5FK6-refs-euc
export:
@movie{spielbergJaws1975,
 title = {Jaws},
  author = {Spielberg, Steven},
  date = {1975},
  location = {US},
  editor = {Benchley, Peter and Gottlieb, Carl}}

Support log ID: VHX8F3TY-refs-euc

the default for director is author

I don't know what is meant by this.
I have no expertise in film -- it's not entirely clear to me what "author" means for a film. It seems more fuzzy than for a book or article. Not that I have reason to doubt that the closest analogue for a movie editor is author though. @njbart, what do you make of this? Is there any precedent that you know of?

Is that surprising? How often do you read about a film's scriptwriter oder editor?
Anyway, while there are huge differences in how films are cited in different styles – some even demand that actors are given which makes no sense at all –, the director is essential in all of them. And if you look at what is common in film and media studies, in most cases, only the director is given (tv shows are a bit different; here you often cite the show runner and sometimes the channel on which the show premiered).
I introduced the production in biblatex-fiwi for films which don't have an identifiable director (quite common if you deal with early films; in my case, I needed this for ISIS online videos which don't have proper credits). Having read the discussion in #365, I have now decided to map this field to publisher. So in a future release, they will be equivalent.
Oh, and did you see my question regarding the handling of subtitle?

Is that surprising? How often do you read about a film's scriptwriter oder editor?

Me, literally? Never on both.

Oh, and did you see my question regarding the handling of subtitle?

I did but then forgot -- it's currently neither configurable nor documented. Do you have a different rule for importing them in mind?

In general, the director is considered the central creative instance of a film, so it makes sense the use the author field for this.

True, broadly speaking. But details vary wildy when it comes to how this is handled by the various biblatex packages, and, accordingly, what might be encountered when importing from biblatex data in the wild.
biblatex itself makes no provisions for films/movies/videos at all, except for @movie and @video being aliases for @misc.
As of lately, it does support “data annotations“ via additional field such as, e.g., AUTHOR+an:role (see section “3.7 Data Annotations” in the v3.16 manual, and the biblatex-apa example below).
biblatex-apa used to support director and producer fields, but currently seems to make extensive use of “data annotations“ only. The manual does not discuss any of this, but see this example from the package’s biblatex-apa-test-references.bib:
% ENTRYSUBTYPE is a localisation string
% Three data annotations, one for each name in the AUTHOR list
@VIDEO{10.12:87b,
  ENTRYSUBTYPE    = {tvepisode},
  AUTHOR          = {B. Oakley and J. Weinstein and J. Lynch},
  AUTHOR+an:role  = {1=writer;2=writer;3=director},
  TITLE           = {Who Shot {Mr.} {Burns}? ({Part} {One}) ({Season}~6,
                     {Episode}~25)},
  MAINTITLE       = {The Simpsons},
  EXECPRODUCER    = {D. Mirkin and J. L. Brooks and M. Groening and S. Simon},
  PUBLISHER       = {Gracie Films and Twentieth Century Fox Film Corporation},
  DATE            = {1995-05-21}
}

biblatex-chicago on the other hand, does not use author but editor in combination with an editortype of director. Other editortypes include producer and none (“particularly useful if you want to identify performers”; for details, see the manual, currently v2.1).

Interesting to see the example from biblatex-apa. Basically, they do everything different than biblatex-fiwi. Here's an example of tv episode in biblatex-fiwi:
@movie{Reardon.J:1994a,
	location = {USA},
	author = {Reardon, Jim},
	maintitle = {The Simpsons},
	number = {6},
	title = {Treehouse of Horror V},
	volume = {6},
	year = {1994}}

As I said, I am well aware that various citation styles handle films vastly differently. But AFAICS, APA actually does not mention the screenwriter in its citation style. So I am not sure why this is implemented in biblatex-apa (in biblatex-fiwi, the field scriptwriter only exists because a user specifically asked for it. I never use it and it is disabled by default).
That said, I am open to changes in biblatex-fiwi, for example adopting the annotation approach. It probably would be best to try to coordinate the various the styles in this regard, but this is definitely beyond the scope of this bug.

I did but then forgot -- it's currently neither configurable nor documented. Do you have a different rule for importing them in mind?

My preference would be a period followed by an empty space. But that's just me. The hyphen approach seems unusual though. I would say that in general, either periods or colons are most common.

but this is definitely beyond the scope of this bug

For import this is true, for export not.

FWIW, the APA Manual, 7e, has:

87. TV series episode or webisode
Barris, K. (Writer & Director). (2017, January 11). Lemons (Season 3, Episode 12) [TV series episode]. In K. Barris, J. Groff, A. Anderson, E. B. Dobbins, L. Fishburne, & H. Sugland (Executive Producers), Black-ish. Wilmore Films; Artists First; Cinema Gypsy Productions; ABC Studios.
Oakley, B. (Writer), Weinstein, J. (Writer), & Lynch, J. (Director). (1995, May 21). Who shot Mr. Burns? (Part one) (Season 6, Episode 25) [TV series episode]. In D. Mirkin, J. L. Brooks, M. Groening, & S. Simon (Executive Producers), The Simpsons. Gracie Films; Twentieth Century Fox Film Corporation.
Parenthetical citations: (Barris, 2017; Oakley et al., 1995)
Narrative citations: Barris (2017) and Oakley et al. (1995)

Include writer(s) and the director for the episode. Include the contributor roles in parentheses after each contributor’s name. “Writer” and “Director” are shown here, but “Executive Director” or other role descriptions might also be used.

Provide the season number and episode number after the title in parentheses.

This looks a bit excessive to me as well, but, be that as it may, the most interesting question for BBT here is about useful heuristics for importing stuff into Zotero.
At a minimum, an author field in a @movie or @video item in the absence of any fields like director, or author+an:role or editortype (including editor[abc]type) containing director would most likely indicate a director.
In addition, an author field in any item type if accompanied by authortype={director} or by author+an:role={director}, or an editor field in any item type accompanied by editortype={director} or by editor+an:role={director} is definitely intended to represent a director as well (note again that instead of editor, editor[abc] could be used in any of these field names). There are probably other variations out there, but these are the ones that come to mind ATM …

It probably would be best to try to coordinate the various the styles in this regard, but this is definitely beyond the scope of this bug.

Agreed on both counts.
FWIW, again, I’m not sure why biblatex-apa uses EXECPRODUCER rather than something like editor plus editor+an:role={execproducer}, and I’ve been puzzled for a long time why biblatex-apa never went for using something like volume=6, number=25 for TV seasons and episodes. If you, @simifilm, would like to try coordinating with biblatex-apa, this, I think, would be worth bringing up.

@njbart This section from the APA manual is completely braindead IMO and obviously written by people who never actually work with films. The point of any citation is to clearly identify a certain work; why you would need stuff like executive producer is completely beyond me. But this is not really surprising, since I rarely ever encounter APA in film or media studies. In my experience, in English speaking humanities, in other words, the fields which do work with film, MLA is much more common.
That said, I doubt that many people ever use biblatex-apa in the way the example posted by @njbart implies since neither the annotation part nor fields like execproducer are mentioned in the manual.
I think I also looked at this once, but since I originally did only have the role of director did not see the point in using anything but author. I think I even looked at the annotation mechanism once for biblatex-fiwi. If I remember correctly, main reason I did not follow this route, was that it really does not work well with BibTeX GUIs (BibDesk in my case).
I don't want to promise too much, but I think I might try to get in touch with Phil and David Fussner, the author of biblatex-chicago. Maybe we can clean this up a bit.

This section from the APA manual is completely braindead IMO […]

I won’t argue with that – but don’t forget there are people out there compelled by supervisors or publishers to follow this format to the letter.

[…] I doubt that many people ever use biblatex-apa in the way the example […] implies since neither the annotation part nor fields like execproducer are mentioned in the manual.

This does not necessarily follow. The biblatex-apa manual itself is extremely terse compared to its biblatex and biblatex-chicago counterparts, and actually says “biblatex-apa-test-references.bib […] is the main documentation […]”.
And, more importantly, I don’t see any other way to use biblatex-apa. director not longer works (I just checked), so author plus author+an:role={director} seems to be the only option there is.

@retorquere Thank you very much for the new build. Your response time is simply amazing.

I must admit I've lost track of the discussion above -- would it be possible to construct import/export samples that you agree on?

I am good for the moment. Import from biblatex-fiwi seems to work fine now. And for everything else I think we first have to agree on among style authors.

And wrt the import of the annotated styles? I don't think I'm handling that correctly right now. A sample with match would help a lot.

closing this as (partially) resolved as I want to cut a new release. If the dialogue progresses on the annotated fields etc, please open a new issue.


fix various small annoyances

Scope & Purpose
Fix very minor annoyances.

[x] Bug-Fix for devel-branch

Testing & Verification
This change is a trivial rework / code cleanup without any test coverage.

https://jenkins01.arangodb.biz/view/PR/job/arangodb-matrix-pr/4589/


[arch] testshfl.cu:50 Assertion `hostFloats1[0] == 1001' failed

make run-testshfl
OpenCL platform: AMD Accelerated Parallel Processing
OpenCL device: Ellesmere
1002
1003
1004
1006
1007
testshfl: /coriander/test/endtoend/testshfl.cu:50: int main(int, char **): Assertion `hostFloats1[0] == 1001' failed.
make[3]: *** [test/endtoend/CMakeFiles/run-testshfl.dir/build.make:61: test/endtoend/CMakeFiles/run-testshfl] Aborted (core dumped)
make[2]: *** [CMakeFiles/Makefile2:2785: test/endtoend/CMakeFiles/run-testshfl.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:627: test/endtoend/CMakeFiles/run-endtoend-tests.dir/rule] Error 2
make: *** [Makefile:307: run-endtoend-tests] Error 2
Just a note for myself

OK, I'm confused, now it works again??
[  2%] Built target clew
[ 12%] Built target easycl
[ 86%] Built target cocl
[ 88%] Built target testshfl
[100%] Built target patch_hostside

make run-testshfl
OpenCL platform: AMD Accelerated Parallel Processing
OpenCL device: Ellesmere
1001
1002
1003
1005
1006
[100%] Built target run-testshfl


Adding more theme color options

I think it would be great if we had more theme color options or kinda like two group of options.
Let me explain
When I work, I usually like having two groups of color themes :

The app level themes (danger, success, warning). Those colors will pretty much be always the same no matter the project.
The brand themes which will be customized to suit every project branding

I would suggest the following

App level :

Success (green)
Info (blue or maybe purple)
Warning (orange)
Danger (red)

Brand colors :

Primary
Secondary

Aside
Since we have a Dark color, shouldn't we also have a light one ?

Yes pretty much. And also an info color which would be blue.
The primary color for Vuesax will therefore be purple since that's the colors that's primarily used on the docs site and logo.
The primary and secondary colors should be the ones that should be highly customizable in order to apply the project's branding colors. The other ones can be customizable as well but they won't change much from projects to projects (Meaning the danger color will always be a shade of red)

You have all the right friend but you have to define the color primary as blue initially in vuesax the user would change the color for each use case to his preference and an example in the vuesax documents would be purple me love the idea of adding them you can do a PR of this without any question question me, thank you very much for the contribution

If you like I can help you with that!

@ziadzadeh clear you can always help the only thing is that now I'm migrating all the components to stylus for support issues in SSR and better functioning
If you want to more or less understand the change, the buttons were made completely from 0 in the migration that is the approach that is going to be done in all the components
https://github.com/lusaxweb/vuesax/blob/master/src/components/vsButton/vsButton.vue
thank you very much for wanting to help and the contribution

All the components have the same language and it is much better understood thanks to the contribution


Formatting

PEP8 Format
Organized imports
Added link to README.md
Formatted html and css

This is just PEP8 formatting.


 We have manually pushed manifests to the registry that include all upstream arches:
rocks.canonical.com:443/cdk/calico/node:v3.6.1
rocks.canonical.com:443/cdk/calico/kube-controllers:v3.6.1
They were made like this:
docker pull --platform $arch calico/[node|kube-controllers]:v3.6.1

docker tag calico/[node|kube-controllers]:v3.6.1 $reg/cdk/calico/[node|kube-controllers]-$arch:v3.6.1

docker push $reg/cdk/calico/[node|kube-controllers]-$arch:v3.6.1

docker manifest create $reg/cdk/calico/[node|kube-controllers]:v3.6.1 $reg/cdk/calico/[node|kube-controllers]-$arch:v3.6.1

docker manifest push $reg/cdk/calico/[node|kube-controllers]:v3.6.1

docker manifest inspect $reg/cdk/calico/[node|kube-controllers]:v3.6.1

These manifests allow the right arch image to be used when deploying calico. However, s390x doesn't exist upstream:
https://hub.docker.com/r/calico/node/tags?page=2&name=v3.6.1
Until we figure out how to deal with this missing arch, remove these images from container-images.txt so our jenkins jobs don't clobber our shiny new manifests with bad arch images.

However, s390x doesn't exist upstream

We have never supported calico on s390x anyway. See the Calico charm resources here - amd64 and arm64 only.


Refactor for deploying a Xenial buildfarm.

This is a heavy refactor of the buildfarm deployment puppet.
The purpose of the refactor is to

Use the Roles & Profiles pattern endorsed by Puppet Labs for keeping insanity low
Allow the configuration for different roles to coexist on a single machine.
Initiate the move to Puppet 4

Outstanding work

[x] Reprepro 5.x on the repo node. https://github.com/ros-infrastructure/buildfarm_deployment/issues/145
[ ] Allow a single node to have multiple roles https://github.com/ros-infrastructure/buildfarm_deployment/issues/42 (deferred)
[x] Refactor to hiera hierarchy (necessary for role coexistence)
[ ] refactor *_files modules into respective profile modules

Issues resolved by this PR

[x] Java 8 on master (and everywhere else to boot) https://github.com/ros-infrastructure/buildfarm_deployment/issues/144
[x] Ubuntu Xenial Support https://github.com/ros-infrastructure/buildfarm_deployment/issues/137 (it was kinda the whole point)
[x] Switch to python puppet module with better support https://github.com/ros-infrastructure/buildfarm_deployment/issues/135
[x] Remove vendored upstart module (superseded by systemd) https://github.com/ros-infrastructure/buildfarm_deployment/issues/63

Outside the scope of this PR is completing the move to Puppet 4. Some of the modules we're using don't yet explicitly support Puppet 4 and Xenial ships with the recently EOL'd 3.8.5 which is what this targets currently. We are using the "future" parser which is shared by puppet 3 and 4. I've also incorporated a puppet lint config and I think it'd be a nice idea to get puppet-lint and puppet parser validate running through travisci or something.
This PR is quite large and moves a lot of stuff around. When it comes time to review I'll point out a few highlights and areas I think need the most attention.

In an offline discussion earlier this week I decided that testing with and supporting a single node buildfarm was not going to be a goal for this PR. The refactoring I've done so far should make it much more doable but right now I want to focus on getting the official buildfarm tested and then migrated to Xenial. Once that's complete circling back to support a single node configuration can be done with time pressure.
It's still something we want to do as it greatly eases running local or alternate buildfarms on smaller setups.

I also found and fixed some bugs related to the systemd <-> initscript interaction for the agent profile which was blocking further work on the repo profile.

This PR is completely untested on Trusty and I don't currently see a reason to try and achieve trusty compatibility.
Plugin dependency management and versioning is still a royal pain so there will be some post setup manual work to do. As this is my first time migrating a ROS buildfarm I'll be looking for help preparing a test and migration checklist.

This PR is completely untested on Trusty and I don't currently see a reason to try and achieve trusty compatibility.

:+1: Supporting only Xenial is absolutely fine.

Plugin dependency management and versioning is still a royal pain so there will be some post setup manual work to do.

For a first steps that might be fine. But in order to use this for CI testing it needs to be fully automated at some point.

As this is my first time migrating a ROS buildfarm I'll be looking for help preparing a test and migration checklist.

I guess the "best" test is setting up a test farm and let it build e.g. all of Lunar and compare that the jobs which pass on the live farm also pass on the test farm.

For a first steps that might be fine. But in order to use this for CI testing it needs to be fully automated at some point.

Do you know how this was dealt with previously? The puppet module for Jenkins doesn't resolve plugin dependencies because only the latest (non-LTS even) plugin versions have dependency metadata provided via the Jenkins wiki. There is an effort underway at rtyler/jpm to get a sophisticated package manager for Jenkins plugins off the ground but it's also in very early stages and doesn't yet support LTS.

Do you know how this was dealt with previously? The puppet module for Jenkins doesn't resolve plugin dependencies because only the latest (non-LTS even) plugin versions have dependency metadata provided via the Jenkins wiki. There is an effort underway at rtyler/jpm to get a sophisticated package manager for Jenkins plugins off the ground but it's also in very early stages and doesn't yet support LTS.

The puppet files explicitly installed the dependencies. Those lines usually had a comment to mention which other plugin they are required for.
While that is certainly more effort it avoids any manual work for deploying the machines. Once a better solution is available we should certainly change to that to avoid having to list the dependencies explicitly.

cc50aca spikes out a script that reads a current Jenkins instance and dumps the currently installed plugins as an include-able puppet module. Each plugin has a require block for it's dependencies rather than a comment with its dependents since that's the format of the data from Jenkins but we could easily invert that if we think it's preferable.

Thanks for all this good work. I'm looking to set up a small (4-5 machines) build farm, do you suggest trying to use this branch or sticking to trusty for now?

Thanks for all this good work. I'm looking to set up a small (4-5 machines) build farm, do you suggest trying to use this branch or sticking to trusty for now?

If you're familiar with the ROS buildfarm's design (I wasn't when I started this project :grin:), plan to keep your farm around for a while, and don't mind a few speedbumps early in the setup process, then the Xenial branch is probably suitable. I think the prime advantage of using Xenial is Java 8 for the Jenkins master. Since the packages themselves are built in containers, the host OS has less impact on available dependencies. If you're going to be making modifications to the puppet code, the refactor here is intended to make it much more grok-able and customizable but there's still work to be done documenting recommended ways to hook in and layer this code into your own puppet scripts. I particularly need to document the hiera keys.
The trusty code has been configuring agent machines consistently for the current farm though the plugin versions and dependencies are out of sync with what's currently deployed on the farm (which can be resolved by updating plugins in the Jenkins UI). If you want to take advantage of that proofing or your farm needs to match as faithfully as possible to the currently deployed ROS buildfarm then the code in master is the place to start, with the caveat that we are in early testing for a xenial based buildfarm and want to migrate the current farm in the coming months.
Be sure to browse some of the recent issues on this repository, particularly #149 as there are some problems with both the current master and the current xenial branch.

https://github.com/ros-infrastructure/buildfarm_deployment/pull/153/commits/c14135d0644c73dfaf5f98f15661907b54a116e2 will need to be incorporated here.

I didn't see any Java arguments in the patch but I might have just missed them. What JAVA_ARGS are you using for Java 8? The existing Jenkins machine has some commented options in the /etc/default/jenkins file which should be considered (which are based on the guide referenced in #144).

I didn't see any Java arguments in the patch but I might have just missed them. What JAVA_ARGS are you using for Java 8? The existing Jenkins machine has some commented options in the /etc/default/jenkins file which should be considered (which are based on the guide referenced in #144).

For now, the Jenkins Java arguments are still part of the [hiera config](
https://github.com/osrf/buildfarm_deployment_config/pull/14/files#diff-b8e0ea5a576fa05bfc7b51c9a683b3b3R13) rather than the Puppet. This is how they were maintained previously and I was changing so much else that I wanted to leave anything I didn't have an explicit reason to change the way it was.
I need to take time to read through the entire referenced blog post still. It looks like a lot of the flags they're using are tailored toward logging and diagnostics. Is there going to be a disk utilization (storage and throuput) consideration if we just enable all of those? Are there tuning flags we should adopt directly without the logging for now?

For now, the Jenkins Java arguments are still part of the hiera config...

That's why I didn't see them in the diff :wink: Thanks for the pointer.

Is there going to be a disk utilization (storage and throuput) consideration if we just enable all of those? Are there tuning flags we should adopt directly without the logging for now?

I wouldn't blindly enable all the arguments mentioned in the blog post. Since we didn't have Java 8 I wasn't able to try those but the config file on the existing Jenkins machine has the options I thought would be most valuable in a commented line:

Tweaking of the garbage collector will hopefully prevent us to have phases where the master is unresponsive for longer periods of time while doing gc.
Reduce memory usage by applying deduplication (payed for by additional CPU resources)

Let's move the JVM tuning discussion to the config repo in order to keep the discussion closer to the code.

I have changed the target branch of this pull request to point to a new xenial branch in order to stagger the rollout of xenial changes to default branches. As a note to (mostly) myself: Do not delete the origin branch until the corresponding configuration repositories are updated to target ros-infrastructure/xenial branch instead of my fork.


Export cmake package

http://www.cmake.org/Wiki/CMake/Tutorials/How_to_create_a_ProjectConfig.cmake_file

libraries, but also tools that could be useful as a build-utility, such as documentation generators, wrapper generators, etc.) should provide at a minimum a Config.cmake or a -config.cmake file. This file can then be used by the find_package() command in config-mode to provide information about include-directories, libraries and their dependencies, required compile-flags or locations of executables.

PR please?


Add margins around list-items in markdown

They're pretty tightly squeezed in there right now.

@bioball could you plz add print-screens "before" and "after"

Hey @RomanGotsiy, sorry, not sure what you mean by print-screens

Ooooops. I meant screenshots 🤣

Ah!
Before:

After:

@bioball awesome! Thanks


Fix LVM resize error due to fs utilities do not support renamed devices

As part of disk resize for microshift looks like there is bug in the lvextend tool and it is not work when extending a lvm with resize.

https://access.redhat.com/solutions/7016718
https://bugzilla.redhat.com/show_bug.cgi?id=2211856

This PR is a workaround which is provided as part of BZ where lvextend shouldn't run with -r (resize) option. So now we are using lvextend only for extending the respective logical volume and then using xfs_growfs to grow that volume.
Fixes: Issue #3705

Tested and the error reported in #3705 doesn't occur with this PR, inside the VM /sysroot size is also increased:
Filesystem             Size  Used Avail Use% Mounted on

/dev/mapper/rhel-root   24G  4.6G   20G  19% /sysroot


Path of over 260 characters is not supported

I have an Oracle package that I am trying to extract and it fails on one file, which has over 255 chars in length for the full path. Yes I could probably trim down the path to extract to, but that will not be future proof.
Error I get:
[[x7ZipArchive]x7ZipArchive_b9c366ec-18c4-4d1e-86ed-feca54f0e966_202202251202489510975] The file
"client\stage\Components\oracle.jdk\<IP_ADDRESS>.0\1\DataFiles\Expanded\filegroup3\lib\missioncontrol\plugins\com.jrockit.
mc.console.ui.notification_<IP_ADDRESS>165\com.jrockit.mc.console.ui.notification_contexts.xml" in the archive is not
exist in the destination folder

Also change the error message into better English (in the archive is not exist in the destination folder) to does

Thank you.
I will investigate the issue as soon as possible and try to fix it.
Thanks also for pointing out the English message. I'm not very good at English and use machine translation, so I'm very glad for your suggestion to fix it.

No problem happy to help. Maybe something like this?
$tParam = @{
#Added support for long pathnames via unicode \?
LiteralPath = "\?$AbsolutePath"
PathType    = $(if ($Item.ItemType -eq 'File') { 'Leaf' }else { 'Container' })
}

I have released v1.6.0, which fixes the issue, to PowerShell Gallary, please try it.
If the issue is still unresolved, please let me know.
This issue was actually occurring when the full path after expansion exceeded 260 characters. (not 255 characters)
I used your suggested approach of using \\?\ prefix to fix it, but I needed to make a few more corrections in various codes.
I deeply appreciate that you reported this issue.
Thank you so much.

Thanks for the update, still getting this when I *rerun *the DSC module.
When I run it the first time with no extracted data at the destination, it
works ok.
   x7ZipArchive Unzip
    {
        Destination =

'C:\Utilities\DSC\Source\b9c366ec-18c4-4d1e-86ed-feca54f0e966'
Path        =
'C:\Utilities\DSC\Cache\b9c366ec-18c4-4d1e-86ed-feca54f0e966\DSC_Oracle_Client_19c_19.3.zip'
Checksum    = "CRC32"
Clean       = $true
Validate    = $true
}
PowerShell DSC resource x7ZipArchive  failed to execute Test-TargetResource
functionality with error message: The
running command stopped because the preference variable
"ErrorActionPreference" or common parameter is set to Stop:
The specified path, file name, or both are too long. The fully qualified
file name must be less than 260 characters,
and the directory name must be less than 248 characters.
+ CategoryInfo          : InvalidOperation: (:) [], CimException
+ FullyQualifiedErrorId : ProviderOperationExecutionFailure
+ PSComputerName        : localhost
On Sat, 26 Feb 2022 at 04:02, mkht @.***> wrote:

I have released v1.6.0, which fixes the issue, to PowerShell Gallary,
please try it.
If the issue is still unresolved, please let me know.
This issue was actually occurring when the full path after expansion
exceeded 260 characters. (not 255 characters)
I used your suggested approach of using \?\ prefix to fix it, but I
needed to make a few more corrections in various codes.
I deeply appreciate that you reported this issue.
Thank you so much.
—
Reply to this email directly, view it on GitHub
https://github.com/mkht/7ZipArchiveDsc/issues/6#issuecomment-1051029203,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAZPR2T4OXOGWD7IFVXFRLU46Y33ANCNFSM5PI6R5SA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you authored the thread.Message ID:
@.***>

Hi @pubsquash
I am not able to reproduce the same error as you. Can you provide a reproducible zip archive if possible?
Apart from that, in my testing, I noticed that there are many inadequacies regarding long path support.
I don't know why, but it seems that in some cases, code that works fine in the local PowerShell console does not work when run via DSC.
I will work on resolving this issue, but it may take some time as it may require more changes than expected.

After some investigation, I found that \\?\ pre-fixed paths (extended-length paths) are enabled in the PowerShell console, but not in the DSC engine.
For example, the following code executes a nearly equivalent process, but only in DSC it throws an exception.
Code for PowerShell console
$ExtendedPath = '\\?\C:\Test.txt'
New-Item -Path $ExtendedPath

Code for DSC
Configuration test
{
    Script test1 {
        GetScript  = { @{} }
        SetScript  = { retrun $true }
        TestScript = {
            $ExtendedPath = '\\?\C:\Test.txt'
            New-Item -Path $ExtendedPath -ItemType Directory
        }
    }
}

test -outputpath C:\dsc
Start-DscConfiguration -Path C:\dsc -Force -Wait -Verbose

I am currently working on the implementation of the code to enable the extended path in DSC as well, and I hope to release it within the next few days.

Awesome, thanks!
On Tue, 1 Mar 2022, 03:51 mkht, @.***> wrote:

After some investigation, I found that \?\ pre-fixed paths
(extended-length paths) are enabled in the PowerShell console, but not in
the DSC engine.
For example, the following code executes a nearly equivalent process, but
only in DSC it throws an exception.
Code for PowerShell console
$ExtendedPath = '\?\C:\Test.txt'New-Item -Path $ExtendedPath
Code for DSC
Configuration test
{
Script test1 {
GetScript  = { @{} }
SetScript  = { retrun $true }
TestScript = {
$ExtendedPath = '\?\C:\Test.txt'
New-Item -Path $ExtendedPath -ItemType Directory
}
}
}
test -outputpath C:\dscStart-DscConfiguration -Path C:\dsc -Force -Wait -Verbose
I am currently working on the implementation of the code to enable the
extended path in DSC as well, and I hope to release it within the next few
days.
—
Reply to this email directly, view it on GitHub
https://github.com/mkht/7ZipArchiveDsc/issues/6#issuecomment-1054455970,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAZPRYYGKRZBPI3BIJYLFTU5T2QZANCNFSM5PI6R5SA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Found a solution, but not sure if it will work, hope it helps you:
Configuration test
{
Script test1 {
    GetScript  = { @{} }
    SetScript  = { return $true }
    TestScript = {

        Invoke-Command -ComputerName . -ScriptBlock {

            $ExtendedPath = '\\?\C:\Utilities\Test.txt'
            New-Item -Path $ExtendedPath

        }

    return $true

    }
}

}
test -outputpath C:\dsc
Start-DscConfiguration -Path C:\dsc -Force -Wait -Verbose
On Tue, 1 Mar 2022 at 03:51, mkht @.***> wrote:

After some investigation, I found that \?\ pre-fixed paths
(extended-length paths) are enabled in the PowerShell console, but not in
the DSC engine.
For example, the following code executes a nearly equivalent process, but
only in DSC it throws an exception.
Code for PowerShell console
$ExtendedPath = '\?\C:\Test.txt'New-Item -Path $ExtendedPath
Code for DSC
Configuration test
{
Script test1 {
GetScript  = { @{} }
SetScript  = { retrun $true }
TestScript = {
$ExtendedPath = '\?\C:\Test.txt'
New-Item -Path $ExtendedPath -ItemType Directory
}
}
}
test -outputpath C:\dscStart-DscConfiguration -Path C:\dsc -Force -Wait -Verbose
I am currently working on the implementation of the code to enable the
extended path in DSC as well, and I hope to release it within the next few
days.
—
Reply to this email directly, view it on GitHub
https://github.com/mkht/7ZipArchiveDsc/issues/6#issuecomment-1054455970,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAZPRYYGKRZBPI3BIJYLFTU5T2QZANCNFSM5PI6R5SA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>

Thanks for your help. Worked
On Wed, 9 Mar 2022, 22:50 mkht, @.***> wrote:

Closed #6 https://github.com/mkht/7ZipArchiveDsc/issues/6.
—
Reply to this email directly, view it on GitHub
https://github.com/mkht/7ZipArchiveDsc/issues/6#event-6209375683, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AJAZPR7WFEB5DZPD45UH2ITU7CF7VANCNFSM5PI6R5SA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
@.***>


Add option to terminate on specific character in search

Assuming the following directory structure:
% tree .
.
├── b
│   ├── c
│   │   └── g
│   │       └── h
│   │           ├── j
│   │           └── k
│   └── d
└── e
    └── f

9 directories, 0 files

When in dir b/c/g/h/j with FZF_COMPLETION_TRIGGER='':
/tmp/b/c/g/h/j % cd ../<PRESSED_TAB>
>
  2/2
> ../j
  ../k

Above I am using tab completion to get a listing of available directories to cd into.  I quickly realise that I wanted to go a directory (or maybe more) further up the stack.  My instinct is to type ../<TAB> as I would with standard bash/zsh tab completion.  However, with FZF these keystrokes get passed into the search filter and I must instead press ^C and the  ../<TAB>.  Having to press ^C repeatedly gets old quickly.
My feature request is the ability to specify a character via the commandline that would immediately terminate fzf with a zero exit code.  For this example let's name the argument --exit0-char.
In my .zshrc I would set export FZF_COMPLETION_OPTS='--select-1 --exit-0 --exit0-char=." which would be automatically picked up by __fzf_generic_path_completion in completion.zsh and offer (IMO) greatly enhanced path completion.

I think the closest you can do is
export FZF_COMPLETION_OPTS='--bind ".:become:echo {}/."'


How to get started

Hi! I have this laptop model and would like to hackintosh it! I never did this before and would  like to at least now how to get started. I don`t know how to apply a patch nor ever installed hackintosh on any physical hardware (only vbox).
Could you please provide us a brief guide?

I advise against it.  If you can't disassemble it (lack of knowledge / scared to do so) you'll need to send it to repair and that will cost you. If you do disassemble, you might break it (it did, not only once, but twice, and I'm used to doing that on a daily basis).
Stick to VMs (I know the experience sucks, and you won't be able to passthrough the GPU, so it will lag for sure), but at least you won't break the damn machine.
Save a few bucks and buy yourself some cheap desktop parts and build a PC. There it will be much easier to setup a working hackintosh with no issues. Even a Core 2 Duo (needs to support SSE 4.1 for High Sierra and Sierra, and SSE 4.2 for Mojave and up) will do it (altought I recommend a Core i3 or better, because Core 2 Duo means DDR2 and 4GB max of RAM, which will make it run a little bit slower that what it's supposed to). Another important thing to pay attention is GPU.
DO NOT BUY NVIDIA CARDS. Sorry for the all caps, but it is really important. They won't work on macOS 10.13+ (Mojave and up). Even on High Sierra they don't work as expected on certain scenarios.
Take a look here for more information on which GPUs and other parts to buy.
If you're not convinced yet, you might want to take a look at my comment on the other issue #1 .
Sorry for the delayed response. Hope it helps!

I found a way to reset without opening. please check https://www.tonymacx86.com/threads/vostro-5470.273654/post-2127079


Use triggers for tests

Use triggers to run or skip tests.

Too stale, too many new ideas.  Closing.


guardduty:DescribePublishingDestination does not work with documented resources

The GuardDuty IAM docs list detector* and publishingdestination* as resources that can be used for guardduty:DescribePublishingDestination.
Error: (Notice the :/detector/ in the expected resource ARN)
DescribePublishingDestination: User: arn:aws:sts::ACCOUNTID:assumed-role/ROLE/USER is not authorized to perform: guardduty:DescribePublishingDestination on resource: arn:aws:guardduty:us-east-1:ACCOUNTID:/detector/DETECTORID/publishingDestination/PUBLISHINGDESTINATION
This works but is not aligned with the docs:
"Resource": [
"arn:aws:guardduty::ACCOUNTID:/detector/",
"arn:aws:guardduty::ACCOUNTID:detector//threatintelset/*"
]

Thanks for reporting this issue. The information on these pages in the IAM docs is generated automatically from code that the Guard Duty team owns. I sent a ticket to them for this issue and the other that you opened https://github.com/awsdocs/iam-user-guide/issues/217.


Introduce constants for commonly used MIME types

Is your feature request related to a problem? Please describe.
Not a problem, but an inconvenient. I see there are constants available for HTTP methods, HTTP status codes, and so on. I think it would be great if Hertz can expand on that and introduce constants for commonly used MIME types as well — probably within consts.
Describe the solution you'd like
To be able to refer to commonly used MIME types using predefined values, such as MIMETextPlain, MIMETextPlainCharsetUTF8, etc.
Describe alternatives you've considered
Importing the relevant packages from Fiber or any other library that include these.
Additional context
I usually have something like this in almost all handlers:
func RootHandler(ctx context.Context, req *app.RequestContext) {
  switch header := http.DetectContentType(req.GetHeader(consts.HeaderAccept)); header {
  case "text/plain", "text/plain; charset=utf-8": // Errrr...not great
    {
      req.Header(consts.HeaderContentType, header)
      req.String(consts.StatusOK, "Go Hertz!")
    }
  ...
  default:
    {
      req.Header(consts.HeaderContentType, "text/plain")
      req.String(consts.StatusNotAcceptable, "Not Acceptable")
    }
  }
}

Good idea! May just add a file for this sort of consts under pkg/protocol/consts.

let me try

let me try

thanks @cqqqq777


Select2 looses focus when enclosed in a label tag

Steps to reproduce the issue

Create a select2 inside a label tag (see fiddle: https://jsfiddle.net/2kt7z8wu/)
When you click on the select2 dropdown, the search gets focus before loosing it as the hidden select gets the focus.

Expected behavior and actual behavior
When I click on a select I expect it to retain focus.
We found this because we have replaced standard selects in our django admin screens which are wrapped in labels and they don't retain focus correctly. Without a lot of extra work we can't change the html so would prefer to fix select2.
Environment
Browsers

[x] Google Chrome
[x] Mozilla Firefox
[x] Internet Explorer

Operating System

[x] Windows
[ ] Mac OS X
[ ] Linux
[ ] Mobile

Libraries

jQuery version: 4.0.1
Select2 version: 2.2.0

Isolating the problem

[ ] This bug happens on the examples page
[x] The bug happens consistently across all tested browsers
[x] This bug happens when using Select2 without other pluigns
[x] I can reproduce this bug in a jsfiddle

refer to: #4187

That is a solution to the problem, but I think it does need to be integrated into select2. Because you don't have to do that on a normal select to make it work correctly.
Now that I have an idea on how it could be solved I can take a look at where in select2 this might be fixable and see if I can come up with a pull request..


test: use grep -E instead of egrep

egrep has been deprecated in GNU grep since 2007, and since 3.8 it emits obsolescence warnings:
https://git.savannah.gnu.org/cgit/grep.git/commit/?id=a9515624709865d480e3142fd959bccd1c9372d1

Thanks for your fix, do you mind adding a Signed-off-by ?

Done.

Thank you.


perf: cache selector query

This operation is quite repetitive and intensive. However, it can be optimized through caching, as stylesheets rarely change between executions, and selectors are consistently evaluated in the same way.

:sparkles: Description by Callstackai
This PR introduces a caching mechanism for selector tokens to optimize the performance of querying nodes, along with a bug fix for a typo in the attribute setting functionality.

Diagrams of code changes
sequenceDiagram
    participant Client
    participant DOM
    participant SelectorCache
    participant Parser

    Client->>DOM: setAttribute('id', value)
    DOM-->>Client: ID Updated

    Client->>DOM: cachedQuerySelector(selector, node)
    alt Selector not in cache
        DOM->>SelectorCache: Check cache
        SelectorCache-->>DOM: Cache miss
        DOM->>Parser: Parse selector
        Parser-->>DOM: Return tokens
        DOM->>SelectorCache: Store parsed tokens
    else Selector in cache
        DOM->>SelectorCache: Check cache
        SelectorCache-->>DOM: Return cached tokens
    end

    alt Has class/id tokens
        DOM->>DOM: Check class/id cache
    else No special tokens
        DOM->>DOM: Fallback to selectOne
    end
    DOM-->>Client: Return match result

Files Changed

FileSummary
packages/beasties/src/dom.tsAdded caching for selector tokens and fixed a typo in the attribute setting.

This PR includes files in programming languages that we currently do not support. We have not reviewed files with the extensions .ts. See list of supported languages.

Summary by CodeRabbit

New Features

Introduced a caching mechanism for selector tokens, improving the efficiency of querying nodes.

Bug Fixes

Corrected a typo in the attribute setting functionality to ensure proper operation.

These updates enhance the performance of attribute selector handling within the application.

Codecov Report
Attention: Patch coverage is 18.18182% with 18 lines in your changes missing coverage. Please review.

Project coverage is 83.14%. Comparing base (8cbd46b) to head (bd7196f).

Files with missing lines
Patch %
Lines

packages/beasties/src/dom.ts
18.18%
18 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #49      +/-   ##
==========================================
- Coverage   84.73%   83.14%   -1.59%
==========================================
  Files           7        7
  Lines        1166     1181      +15
  Branches      271      268       -3
==========================================
- Hits          988      982       -6
- Misses        178      199      +21

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

🚨 Try these New Features:

Flaky Tests Detection - Detect and resolve failed and flaky tests
JS Bundle Analysis - Avoid shipping oversized bundles


Side menu highlighting

Previously, the side menu icon highlighting responded only to dom input. This meant that a redirect to /#discover, or a change to the /#settings page would leave the menu icon highlighting out of sync.
Now the side menu nav listens to a change event from the router, and matches the appropriate icon to the current router state.
PR includes tests.

Current coverage is 69.15%

Merging #398 into master will not affect coverage as of 8617597

@@            master    #398   diff @@
======================================
  Files           64      64
  Stmts         2597    2597
  Branches         0       0
  Methods          0       0
======================================
  Hit           1796    1796
  Partial          0       0
  Missed         801     801

Review entire Coverage Diff as of 8617597

Uncovered Suggestions

+0.66% via goldstone/views.py#30...46
+0.62% via ...stone/drfes/views.py#134...149
+0.43% via ...tone/drfes/models.py#165...175
See 7 more...

Powered by Codecov. Updated on successful CI builds.

:+1:


feat: azapi2dotOh

Description
Adds support for AzAPI 2.0 in preparation for AVM v1.0 specs.
Also pulls in latest repo governance stuff and updates unit tests to work with new auth.
Code owner review because changes to .github/policy
Type of Change

[ ] Non-module change (e.g. CI/CD, documentation, etc.)
[ ] Azure Verified Module updates:

[ ] Bugfix containing backwards compatible bug fixes

[ ] Someone has opened a bug report issue, and I have included "Closes #{bug_report_issue_number}" in the PR description.
[ ] The bug was found by the module author, and no one has opened an issue to report it yet.

[ ] Feature update backwards compatible feature updates.
[x] Breaking changes.
[ ] Update to documentation

Checklist

[ ] I'm sure there are no other open Pull Requests for the same update/change
[ ] My corresponding pipelines / checks run clean and green without any errors or warnings
[ ] I did run all  pre-commit checks

Cheers @luke-taylor
Need an AVM code owner to approve changes to GH policy files


docker pull: "invalid reference format"

Hi;
Small bug to report:
$ docker pull owasp/dependency–track
invalid reference format

Some blinkety-blankety web site authoring tool replaced the hyphen ('-') with a long hyphen ('–'), so when I copy-and-pasted the command it always failed with the error 'invalid reference format'.
Could you please give an error message that doesn't require users to Google their brains out for half an hour to figure out the problem?
Thanks!

Changing that error message would likely result in broken scripts looking for that message. And anyone googling for the new message wouldn't find all the answers for the old message (like this SO answer).

Instead of changing it, maybe add an second line of text, possibly on stderr, possibly selectable with a --verbose-error-messages option or environment variable, just something.
Then scripts looking for the existing message will find it, the error string is still Google-able, and yet the second line can still give useful information to a human so they can solve it without resorting to Google.  Some programs (i.e. ShellCheck) even put a url into the error message that links to a full explanation of what could cause that error message and how to fix it, which is way more focused than a Google search.
In this particular case, reading through all the documentation didn't help, the reference looked correct.  The true cause of the error was only found by accident when the reference was typed over again by hand and suddenly it worked.  Normally, one expects copy-and-paste to be more reliable than typing.
I feel (rightly or wrongly) that an error message should be more informative than the "check engine" light on a car's dashboard.

For what it's worth, after answering quite a few stackoverflow questions, copy and paste, especially from websites, causes a lot of issues. Different dashes, smart quotes, weird space characters, etc.
Links to a website can be problematic when the website changes. There are a lot of Docker EE links that went stale after the Mirantis split, and I'm sure things have broken with distribution moving out of the docker repo. With the distribution no longer a docker project, now moved out to CNCF, it would be another external source to keep in sync for docker.
As user unfriendly as the error message is, it also makes sense technically. The problem is more that error message is directly exposed in user tools, where users may not know what a reference is. The fix could be to update the docker cli to enhance the error messages, rather than the distribution project.
But my preferred option is to have a documentation page to explain various error messages from docker, could be just as useful as the Dockerfile and compose documentation pages. That also wouldn't be a CNCF change.

Please consider opening an issue in https://github.com/moby/moby if looking for a more user friendly message. Closing this issue as it's not a registry bug.


Canceled builds do not show as canceled in the pull request

Integrations canceled because of a new commit continue to show as "building..." in the pull request. See #112 for additional information.

This will require a bit more logic to be added: namely, resolveActionsForCommitAndIssueWithBotIntegrations in SyncPairResolver will need to keep a map from commits to an array of integrations performed for that commit. Then, we would resolve not just the last commit, but all commits to their corresponding status and update all of the affected commits.
This could work. Sorry, @ioveracker if this doesn't make much sense, I'm just thinking out loud :blush:

+1 on this, I like to have clean PRs 😊


[constant-folding] Remove unneeded code.

recursivelyDeleteTriviallyDeadInstructions will handle this for us when it
deletes the instruction. So in fact, this was actually a use of an invalid
pointer. Good thing we never dereferenced it.

Obvious fix since the callback above just does this.

@swift-ci smoke test and merge


[FEATURE] Adding Docker to the project

Description
Long story short: Dockerize Project :)
Screenshots
No response
Additional information
I can create proper Docker images and Docker compose config.

Thank you @the-mzakrzewski , I have assigned it to you

Merged https://github.com/EddieHubCommunity/HealthCheck/pull/30


(python3) choco install python3 didn't install pip

Expected Behavior
pip -V displays pip's version
Current Behavior
$ python -V
Python 3.9.7
$ pip -V
bash: pip: command not found

Steps to Reproduce (for bugs)

choco install -y python3
Re-open terminal
Type pip -V

Context

I'm trying to install packages using pip.
Your Environment

Package Version used: python3 3.9.7
Operating System and version: Windows v 10.0.19043.0
Chocolatey version: 0.11.2
Install/uninstall gist: https://gist.github.com/weeix/ab7be2c0e445fe86290b6fe2f5a4b35a

Solved by these steps:

choco uninstall -y python3
Download installer from https://www.python.org/downloads
Double-click the installer, choose "Repair"
Double-click the installer again, choose "Uninstall"
choco install -y python3


Content Suggestion: IBEXPay added to Store Tools

Link to Content: https://www.ibexmercado.com/ibex-pay
Briefly Describe Content: The easiest and fastest way for any business to receive instant Bitcoin payments via the Lightning Network.
Suggested Section: Store Tools

Is it no KYC?


pot may fail with complain about Error: missing field `PAW_PBE``

Duplicated with #11  (maybe a bug from GitHub)


PATCH request

I have some problem with PATCH request from Fuel 2.2.0
Code:
"$HOST/status".httpPatch()
            .header("Authorization" to BEARER)
            .response { request, response, result ->
            }

The problem is that server at the same time receive POST request, but not PATCH.
Apache log:
- - [13/Oct/2020:14:37:59 +0000] "POST /status HTTP/1.1" 404 3771 "-" "Dalvik/2.1.0 (Linux; U; Android 11; sdk_gphone_x86 Build/RSR1.200819.001.A1)"

This is currently a feature I believe :) We are using FuelManager.instance.forceMethods = true. This will enable true PATCH. Btw. you'll end up with a reflective warning, i.e. WARNING: Illegal reflective access by com.github.kittinunf.fuel.toolbox.extensions.ForceMethodK, so I guess it will stop working some day!

Yes, @hestad is correct here! Please try and let us know whether that answers your question?

I guess this should be closed then. Thanks for asking btw! :)


[Candidate 1v1 Dammed Scorpion ZH v2] Map uses houses with missing fire ports

Observed behavior
Map uses houses with missing fire ports. Soldiers shoot from 0,0,0.
Expected behavior
Map uses houses with good fire port setups.
Screenshots

Not a blocker bug, because terrain around houses appears to be located on favorable terrain, causing no damage to buildings.

map is a one-for-one copy of sand scorpion to make sure player still like it. Sand Scorpion is ranked and is crazy popular, maybe top 5 map. Suggest to keep it exactly the same, players been using it many years and never said anything.
fix in patch

yeah, as long as it doesn't damage itself, like on double damination (which I now fixed) it's fine

As designed.


Need help in Multiple Camera Realsense D435 calibration

Before opening a new issue, we wanted to provide you with some useful suggestions (Click "Preview" above for a better view):

Consider checking out SDK examples.
Have you looked in our documentations?
Is you question a frequently asked one?
Try searching our GitHub Issues (open and closed) for a similar issue.

All users are welcomed to report bugs, ask questions, suggest or request enhancements and generally feel free to open new issue, even if they haven't followed any of the suggestions above :)

Required Info

Camera Model
D435

Firmware Version
(Open RealSense Viewer --> Click info)

Operating System & Version
Ubuntu 18.04

Kernel Version (Linux Only)
(e.g. 4.14.13)

Platform
PC

SDK Version
2.27

Language
Python

Segment
{Robot/Smartphone/VR/AR/others }

Issue Description
<Describe your issue / question / feature request / etc..>
Currently we tried box dimensioner example, it's not giving ver accurate result when the transformation happens using the calibration from local camera coordinate to the global coordinate. The setup has three camera. I have following questions, please help me :

Does the each camera has to be in same orientation, currently we have the positioned horizontally, flipped horizontally, vertically placed.
Commom field of view is below 40 cm for all the three cameras.
I am looking for a method which can provide robust calibration.

Is this a follow-up to your previous case about box-dimensioner, please?  Did the advice given in that case help?
https://github.com/IntelRealSense/librealsense/issues/4715

This is not follow-up on Issue #4715, We are able to calibrate with success and but when using TranformationPose(R|t) matrix the camera which is positioned vertically has a very inaccurate result. Please suggest some robust in calibrating multiple realsense camera. Please let me know if you need more input from my side.

A tool that Intel themselves have used for multi camera calibration of 400 Series cameras is Vicalib.
It uses a board that you show to each of the cameras in turn., and it establishes overlapping regions to then minimize the pose of each of those together.
https://github.com/arpg/vicalib

Thanks @MartyG-RealSense  I can try this tool, is tool only availaible to install through source code?

As far as I know you have to compile Vicaib yourself. Intel also sell a professional calibration system that can calibrate multiple cameras and do so through a remote server, though it costs 1500 dollars due to the cost of manufacturing the large calibration chessboard.
https://store.intelrealsense.com/buy-intel-realsense-d400-cameras-calibration-target.html

@MartyG-RealSense Is the calibration system can offer calibration for multiple cameras looking to a common scene. The whole arrangement is static? If yes would like to get in touch with the Intel Support team to understand and order it.

I do not know enough about that aspect of the tool to comment on it.  I will link this discussion to Intel's @agrunnet  who may be well equipped to answer.

That would great! Thanks looking forward to connecting.

@MartyG-RealSense Would be great if you share vicalib command line usage when 3 cameras are connected. Thanks again for all the support!

@agrunnet I'm looking forward to talking with you.

@dk67604  You're very welcome.  I've never used Vicalib myself though, so have no insight about its detailed operation.

@MartyG-RealSense Is there anyway I can connect with some one. Please help me with this, we are trying to solve this problem from last 1 month.

I have no influence over when Intel RealSense team members respond, unfortunately.  They are required to visit each case at least once to ask if help is still required, and close the case if the problem is resolved or nobody responds that they want to keep it open.  I do not know exactly when they will comment though.
I re-read your case from the start to try to get new insight.  I am not sure that special calibration is required.  As the D435 that you are using does not have an IMU (and so does not have a gyro component that responds to tilt), the direction that the camera is pointed in should not make a difference.
Looking over the instructions in the box-dimensioner example, I don't believe that a calibration solution like Vicalib is going to help.  Box-dimensioner seems to use its own in-built calibration system to analyze the chessboard that the object being measured is placed on.
So there is an important distinction to make:

You could use the Ubuntu version of the Dynamic Calibrator tool to calibrate each camera individually to help ensure that you are going to get a good-quality image.

But then the code in the box-dimensioner example carries out its own kind of calibration of the multiple cameras by observing the chessboard, and this enables it to get good measurements of the object on the chessboard.

Looking at the main instructions page for box-dimensioner, it seems to say that no object should be on the chessboard when you start the program.  When the program starts, it should automatically carry out its multiple-camera calibration.   An object should not be placed onto the chessboard until the program asks you to.
If you are using your own custom size of chessboard then the program's chessboard parameters need to be edited so that you get correct results.  Also, make sure that the chessboard is in the view of all the cameras.
https://github.com/IntelRealSense/librealsense/tree/master/wrappers/python/examples/box_dimensioner_multicam#workflow

Thanks @MartyG-RealSense I appreciate your efforts for instructions. I'll definitely be going to try Dynamic Callibrator tool, and then the box-dimensioner example.

@MartyG-RealSense I tried to Ubuntu version of the official Intel 'Dynamic Calibrator' tool, tried a couple of times and followed the steps shown in demo. Everytime I'm getting this error.

Are you using a USB 3 port with the tool, please?

@MartyG-RealSense Yes I make sure that I'm using USB 3.0 port. I can try different machine

Hi dk67604
Can you try the Dynamic Calibrator tool under Windows 10 instead of Ubuntu? I just want to make sure your operation of the calibration is correct. This is to help you build the experience about how to use the tool.
Thanks
**Please be informed that we will close this ticket in seven (7) days if we have not heard back from you.

I'll try on Windows 10


Add defensive checks to safely handle browser disconnects.

This is a common occurrence when integrating with SauceLabs or BrowserStack.

Add safety check to handle the case where a browser disconnects and specSuccess/specSkipped/specFailure will throw an Error due to suites[browser.id] returning undefined.
Add safety check to handle the case where a browser disconnects and onBrowserComplete receives a result object without total or failed values. Causes XMLAttribute in xmlbuilder to throw an error.
Add tests to validate new behavior works correctly and that no errors are thrown.

Thanks, can you change your commit message to follow our convention please

Amended commit message to follow the referenced guidelines.

@dignifiedquire Is there anything blocking this PR from getting merged?

Thanks :octocat:


[MP+] Setup namespaces

Once we have a our tenant created (#438) in the cluster(s):

[x] Create packit-service-validation namespace(s) - see Tenant management in this doc
[ ] Figure out the next step(s) and create follow-up card(s)

[ ] Do we have to build the packit-service-validation images on the cluster or can we use the already existing ones in Quay.io?
Consult Building and Deploying in MP+ and Enterprise Application Lifecycle Standards
[ ] When/where/how begins the ESS assessment?

packit--stg namespace/project has been created and the next step is packit/deployment#470