UI for resources configurations for pipeline build pods

What kind of request is this (question/bug/enhancement/feature request):
enhancement
Description
Under project-tools-pipeline settings, Be able to configure resouces(CPU/memory request/limit) for dynamically provisioned build pods.
Related issue: https://github.com/rancher/rancher/issues/16538

UI PR is not merged yet. We added it in the Tools => Pipeline

Had to roll back some changes on master this will be on hold until we can merge again.

I do not like that when we authenticate such as with github and pick our repository (ies) we get routed back to listing of repos I think it would make more sense to route back to pipeline settings. It's not as obvious to the user that this is a new feature unless we do that and when they set up their pipeline the first time they would likely want to see any additional settings/options they can pick.
I created #17942 to track this enhancement request.

Version: Master 2.2 (2/8/19)
Validated new feature - Pipeline Settings. Tested with GitHub.
Confirm form works / looks good. Validate the various options (http/api).

Inspect pipeline executors, when you + or - a PUT updates this live without form submission (good).
Inspect resource limit/reservation options. When you click the "Update Limit and Request" button a PUT is submitted for each endpoint (good).
Inspect custom CA cert. When you click "Save cacerts" PUT is submitted and content looks good (fuzz, test newlines, etc).
Confirm "Disable Repository Authentication" works. It will also ask user to confirm with a new button "Are you sure to disable repository authentication?" if you do not click it after about 10 seconds it will revert back to the normal "Disable Repository Authentication" button. If you do click it it will successfully disable repo auth and bring us back to our options for GitHub, GitLab, BitBucket.

During my testing I noticed that we could also use some minor fixes to English translations so I also created #17943


How to bind with sAMAccountName

I want to log in client with sAMAccountName, but I can't find way to finish it.
const client = ldap.createClient({
  url: `ldap://${server}`,
});
const password = '';

// bind to AD by userPrincipalName
const userPrincipalName =<EMAIL_ADDRESS>client.bind(userPrincipalName, password, (err, res) => {
  // ...
});

// bind to AD by CN
const CN = 'CN=Jone,OU=AzureADSyncUsers,DC=github,DC=com';
client.bind(CN, password, (err, res) => {
  // ...
});

// bind to AD by sAMAccountName?

You must bind with a fully qualified DN. To use the Active Directory specific sAMAccountName as a login credential your application must first use it to find the appropriate DN and then use that DN for login. https://www.npmjs.com/package/adldap can make this easier, but I do not promise to keep that library updated.

⚠ This issue has been locked due to age. If you have encountered a recent
problem that seems to be covered by this issue, please open a new issue.
Please include a minimal reproducible example
when opening a new issue.


Scorecard for tech insights

Signed-off-by: irma12<EMAIL_ADDRESS>Hey, I just made a Pull Request!

:heavy_check_mark: Checklist

[x] A changeset describing the change and affected packages. (more info)
[x] Added or updated documentation
[ ] Tests for new functionality and regression tests for bug fixes
[x] Screenshots attached (for UI changes)
[ ] All your commits have a Signed-off-by line in the message. (more info)

This PR contains changes for Scorecards plugin which we proposed and discussed in https://github.com/backstage/backstage/issues/7576.
As a visual representation for tech-insights plugin introduced recently, and as a continuation of https://github.com/backstage/backstage/pull/8057/files we proceeded with creating scorecards and included overview of boolean checks for default checks we would include.

Title, description and overview component, used to render checks, are rendered dynamically and can be defined based on type of checks.

Alright, getting there!

@freben Thank you for revising the code 🙏🏼 . I do see your point with the @backstage/plugin-tech-insights-react but @backstage/plugin-tech-insights-scorecards for me sounds a bit clearer as it makes it obvious what the package actually consists of.
(After we get the agreement on the name, I will apply the change in the plugin name too 😃 )

@Irma12 regarding the naming, what do you think about simply making it @backstage/plugin-tech-insights? It's fine for a plugin to export a couple of different extensions, and an application doesn't necessarily need to import and use all of those extensions. We can keep exporting scorecard extensions, but over time also build out support for other types of components that communicate with the tech-insights backend.

@Rugvip I agree, sounds reasonable naming it @backstage/plugin-tech-insight so I proceeded with it. Thank you 👍🏼

Did a final little run-through, @Rugvip will double check but I had some small comments

Thanks @freben, I have made the final changes based on your comments  :)

@Rugvip Thanks for taking a look into this, you have a point regarding minor bump for -common package, I applied the changes :)


Add doc for equals method in blob

Thank you for opening a Pull Request! Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code!  That way we can discuss the change, evaluate designs, and agree on the general idea
[ ] Ensure the tests and linter pass
[ ] Code coverage does not decrease (if any source code was changed)
[ ] Appropriate docs were updated (if necessary)

Fixes #310 ☕

@frankyn  There is error on Kokoro integration test Caused by: com.google.api.client.googleapis.json.GoogleJsonResponseException: 400 Bad Request
"Bucket is requester pays bucket but no user project provided."


The shared folders are created without errors, but the files and subfolders in the host folder are missing.

Describe the bug
We create shared folders by
Add-EflowVmSharedFolder -sharedFoldersJsonPath "C:\temp\sharedFolders.json"

The shared folders are created without errors, but the files and subfolders in the host folder are missing when we are trying to access them in the EFlowVM.
To Reproduce
Steps to reproduce the behavior:

Add-EflowVmSharedFolder -sharedFoldersJsonPath "C:\temp\sharedFolders.json"
Connect-EFlowVM, navigate to the shared path, the folder is empty.

Expected behavior
All files and subfolders in the host folder should be accessible in EFlowVM
Screenshots
If applicable, add screenshots to help explain your problem.
Windows Host OS (please complete the following information):

Edition: Windows10 Enterprise LTSC 2019
Version:  build 17763
Virtual Machine: None

Additional context
We have tested the folder with:
 Get-EflowVmSharedFolder -sharedfolderRoot "C:\temp" -hostFolderPath @("iotedgegateway")
hostFolderPath readOnly targetFolderOnGuest hostFolderFullPath
-------------- -------- ------------------- ------------------
iotedgegateway    False /srv/IoTEdgeGateway C:\temp\iotedgegateway

The sharedfolder.json content:
[
    {
        "sharedFolderRoot": "C:\\temp",
        "sharedFolders": [
            {
                "hostFolderPath": "iotedgegateway",
                "readOnly": false,
                "targetFolderOnGuest": "/srv/IoTEdgeGateway"
            }
        ]
    }
]

ls output in windows：
PS C:\temp\iotedgegateway> ls

Mode                LastWriteTime         Length Name
----                -------------         ------ ----
d-----       2023/10/14     17:30                Cache
-a----         2021/6/3     21:46         151950 module.json

/srv/IoTEdgeGateway sudo ls output in EFlowVM is empty.

I seem to have the same issue. Shared folders are created without errors (although they have to pre-exist in the VM), but files which are put in the shared folders are not showing up when I connect to VM. If I connect to VM and create some files in the shared folder, they also don't show up in the host.

@aidassimkus Do you use the same Windows10 Enterprise LTSC 2019?
I think I've found the reason; the shared folder feature is not supported in Windows10 Enterprise LTSC 2019. The Prerequisites OS is Windows 10/11 (21H2) or higher.

See this issue.

Yes, SharedFoder is only supported on Client OS (Win11, Win10)...


How to further control the lifetime and speed?

Hi, great lib!
I'd like to have the sparkles appear fast and then stay on screen, or at least for a minute or two.
I've tried tweaking speed, lifetime, messing with modules and creating a custom template, but I could not get the effect I'm after. See CodePen
Is it possible to expose the lifetime and speed within the modules? Or set an easing curve to those values so that they are not constant?
See here what I am trying to achieve:

Thank you

Hi there,
unfortunately, as of yet I haven't come up with a good solution for customizing velocity yet. I'll have to look into this, once uni allows it.
To increase the lifetime, you can increase the initialLifetime property when creating a custom emitter:
party.scene.current.createEmitter({
    // ...
    emissionOptions: {
        initialLifetime: 100
    }
    // ...
});

I'll get back to this, sorry for not being able to fully support what you need currently.


Wrap secret value with multiple words in quotes using view command

Closes #265
I changed the printXXXFormat APIs to accept an io.Writer instead of always using os.Stdout. Makes easier to test and we can combine with another writers if needed.
I also removed the hint from the view command because the text is added to the output file when redirecting.
Eg: torus view > secret.env has at the end:
Protip: Define an organization and project for your current working directory using `torus link`

Probably a better approach would be to disable hints whenever stdout is not printing to the terminal.

This is awesome!
I'm curious as to why the hints were still showing, we had disabled them in https://github.com/manifoldco/torus-cli/pull/254.

I just tested again, you are correct, there is no hint when redirecting stdout. I must have done something wrong previously. I've added the hint back to view.


Support nested host groups

I'm submitting a ...

[ ] Bug report
[ x] Feature requestdd
[ ] Question / Support request

Hi it would be nice to be able to select variuos host groups on the triggers table or select a nested hostgroup weach doesnt show right now for example of nested hostgroup Latvia/Riga
Thanks Great work so far ....

You can select multiple groups by using regex.

Thanks got it working i leave an example here if some one needs it.
Lets say you have two groups Latvia and Riga and want to filter only the hosts of them
you would write on the box /Latvia|Riga/ and it will give you the thes hosts of those groups only.

I would like to know if its possible using "non-consuming regular expressions" to perform an AND to show only hosts that belongs to the same two groups:

One search for Windows servers of customer "A" /(?=customer_a)(?=Windows Servers)/
Another filter to search for Linux servers of customer "A" /(?=customer_a)(?=Linux Servers)/

Problem with nested groups in variables, when i create a using "{*}" to get all groups isn't bring a first nest.
+1

to add my 2 cents here
i have nested host groups, in zabbix if i show all hosts in host group Parent/Child/1
i see all hosts in that and its sub groups .e.g. Parent/Child/1/Access
but in Grafana i see nothing because all of the hosts are in the lowest level hostgroup only, they are not directly in Parent/Child/1
i would at least loosely to expect behaviour similar to zabbix
i tried the workaround of /Latvia|Riga/  however this appears not to work because of the presense of / in the hostgroup name for nested, i also tried escaping and appears not to work - debugging if this is specifically because of that or my query is now large because its a LOT of devices (some 650)

I was creating some scripts at work, and looking at the debug from Zabbix frontend, I found that it makes a query using search in the name with the forward-slash (which I'm using in my script):
Array
(
    [output] => Array
        (
            [0] => groupid
        )
    [search] => Array
        (
            [name] => Array
                (
                    [0] => MyRootGroup/
                )
        )
    [searchByAny] => 1
    [startSearch] => 1
)

Makin a little search at plugin code I found that you always get all groups:
https://github.com/alexanderzobnin/grafana-zabbix/blob/94c5059fb1d21f481678b9dc275a3533c39e7c71/src/datasource-zabbix/zabbix/connectors/zabbix_api/zabbixAPIConnector.js#L106-L114
And then filters them using the defined regex:
https://github.com/alexanderzobnin/grafana-zabbix/blob/94c5059fb1d21f481678b9dc275a3533c39e7c71/src/datasource-zabbix/zabbix/zabbix.js#L166-L184
Maybe an if using a clause where the value is not a regex and contains a forward-slash can solve the issue?
I'm really sorry for not making up the code and sending a PR, but I'm not a JS/TS developer (more like a Python/PHP one), so at the moment I only can share my logic.

Any way I can buy someone some beer/coffee/whatever to implement this change?

@mike-sol just try to put the full group if it's just one. If it's more, I'd just put it in a Regex like this: 'customer_a\/servers\/.*' For me, using this way works just fine.

I was creating some scripts at work, and looking at the debug from Zabbix frontend, I found that it makes a query using search in the name with the forward-slash (which I'm using in my script):
Array
(
    [output] => Array
        (
            [0] => groupid
        )
    [search] => Array
        (
            [name] => Array
                (
                    [0] => MyRootGroup/
                )
        )
    [searchByAny] => 1
    [startSearch] => 1
)

Makin a little search at plugin code I found that you always get all groups:
https://github.com/alexanderzobnin/grafana-zabbix/blob/94c5059fb1d21f481678b9dc275a3533c39e7c71/src/datasource-zabbix/zabbix/connectors/zabbix_api/zabbixAPIConnector.js#L106-L114
And then filters them using the defined regex:
https://github.com/alexanderzobnin/grafana-zabbix/blob/94c5059fb1d21f481678b9dc275a3533c39e7c71/src/datasource-zabbix/zabbix/zabbix.js#L166-L184
Maybe an if using a clause where the value is not a regex and contains a forward-slash can solve the issue?
I'm really sorry for not making up the code and sending a PR, but I'm not a JS/TS developer (more like a Python/PHP one), so at the moment I only can share my logic.

I see. Does @alexanderzobnin allow us to do pull requests and implement this on the plugin or we can't deploy stuff for his plugin zabbix code? I am really needing this - Created the perfect architecture that can adapt to many hosts, clients and scenarios and all this using a single Dashboard - But the ONE thing preventing me to deploying is to filter using Groups. T_T
If only we had a option Comma Delinmted Groups with a AND operator... 😥

I was creating some scripts at work, and looking at the debug from Zabbix frontend, I found that it makes a query using search in the name with the forward-slash (which I'm using in my script):
Array
(
    [output] => Array
        (
            [0] => groupid
        )
    [search] => Array
        (
            [name] => Array
                (
                    [0] => MyRootGroup/
                )
        )
    [searchByAny] => 1
    [startSearch] => 1
)

Makin a little search at plugin code I found that you always get all groups:
https://github.com/alexanderzobnin/grafana-zabbix/blob/94c5059fb1d21f481678b9dc275a3533c39e7c71/src/datasource-zabbix/zabbix/connectors/zabbix_api/zabbixAPIConnector.js#L106-L114
And then filters them using the defined regex:
https://github.com/alexanderzobnin/grafana-zabbix/blob/94c5059fb1d21f481678b9dc275a3533c39e7c71/src/datasource-zabbix/zabbix/zabbix.js#L166-L184
Maybe an if using a clause where the value is not a regex and contains a forward-slash can solve the issue?
I'm really sorry for not making up the code and sending a PR, but I'm not a JS/TS developer (more like a Python/PHP one), so at the moment I only can share my logic.

I see. Does @alexanderzobnin allow us to do pull requests and implement this on the plugin or we can't deploy stuff for his plugin zabbix code? I am really needing this - Created the perfect architecture that can adapt to many hosts, clients and scenarios and all this using a single Dashboard - But the ONE thing preventing me to deploying is to filter using Groups. T_T
If only we had a option Comma Delinmted Groups with a AND operator... 😥

You can do nested groups using regex on group names. Like:
CUSTOMER-A/NETWORK/ROUTER
CUSTOMER-A/NETWORK/SWITCH
CUSTOMER-A/SERVERS/WINDOWS
CUSTOMER-A/SERVERS/LINUX
CUSTOMER-B/NETWORK/ROUTER
CUSTOMER-B/NETWORK/SWITCH
CUSTOMER-B/SERVERS/WINDOWS
CUSTOMER-B/SERVERS/LINUX
And some examples:
All CUSTOMER-A hosts: /CUSTOMER-A./
All CUSTOMER-A network devices: /CUSTOMER-A/NETWORK/./
All customers SERVERS: /.SERVERS./
This issue should be closed. There's no need for more than the already existent regex support.

@alexanderzobnin just close the issue with the reference to regex support


CodeFactor fixes for configure script

https://www.codefactor.io/repository/github/zlib-ng/zlib-ng/file/develop/configure

LGTM
But will postpone this to after stable release, just in case it breaks anything.

Sounds good to me.


Suggestion: Use reactphp/http for http server

Using reactphp/http can significantly reduce the amount of code that needs to be written.

Thank you for your suggestion!
The main idea of this tool is to be lightweight and fast. The HTTP server implementation itself is actually not that big compared to all the code included in the suggested library and its dependencies.
Unfortunately, I can't use it here because reactphp/http runs on top of the reactphp event loop implementation and is coupled with other reactphp components. I'm using the revolt event loop here.


Fix logic of adding remoting headers

Due to inversed condition, headers were not added during remoting transfer for a week now.
UT were ignoring this failure because they have not had await for a Task, also fixed in this PR

Would be fixed, here https://github.com/microsoft/Omex/pull/262

Would be fixed, here https://github.com/microsoft/Omex/pull/262


fix #2086

A few changes from the original issue:

The timestamp and md5 are stored in redis so we can quickly display
I moved the test_generate_biom_and_metadata_release method to meta_util.py as it requires redis and we already are importing it there and the other "qiita-cron-jobs" are there ...

Note that I'm gonna deploy in qiita-test to check that everything works as expected.

Forgot to add that the new link looks like:

Coverage decreased (-0.008%) to 91.954% when pulling 2b8d608bf5a754fca8a4bd7c72eee2ebb10e8696 on antgonza:fix-2086 into a60cec21a808cf79b59636a93b56bb8e51d75d3e on biocore:master.

@ElDeveloper, @wasade, @josenavas, this is ready for final review. I would like to have this reviewed/merged soon so I can add the bulk raw data download in a following PR (will issue soon!). Thanks.


256k dash audio no longer available

Possibly not a bug with youtube-dl, but previously all videos had a 256k audio stream available - admittedly the vast majority were upscaled. Today the maximum is 128k, anyone know what's going on?

It seems that Youtube stopped using the 141 itag and 256 kbps AAC for new videos. :-(


tob-agent-http

because some things can only be accessed from the OS level directly, the objective is to create a special agent to serve tob,

improve error messages: error messages such as threshold notifications cannot be as simple as service UP or service DOWN
create a similar script https://github.com/telkomdev/tob/blob/master/scripts/package.sh for each binary agent
create a new build command in a Makefile for Linux and MacOS binary agent with an additional suffix: build-osx-agent-xxx:, build-linux-agent-xxx:,

example parsing df command to json
https://gist.github.com/wuriyanto48/67ce6439ce168ef70a22aa71cf0d1440

https://github.com/telkomdev/tob/releases/tag/1.2.0


Dutch Railways disruptions API

This script implements (part of) the NS (Dutch Railways) API and allows you to check railway disruptions around a certain train station from Campfire. Super handy to see if your train is going to make it on time.
Dependencies: xml2js
Requires NS_API_EMAIL and NS_API_PASSWORD to be set through "heroku config:add"

Can you prefix the environmental variables with HUBOT please?

Done :-)


Order components

[ ] Geiger Counter
[ ] Air Quality Sensor
[x] Sense HAT
[x] LoRa Capabilities
[ ] NOAA Radio
[ ] GPS
[ ] AM/FM Radio

Blocked by #5

Using Sense HAT from older project. LoRa HAT arrive 2023-11-03.

Updating Due Date


fix(#720): do not require questionary for tasks.py

Current dependencies on/for this PR:

main

PR #724   👈

This stack of pull requests is managed by Graphite.

Merge activity

Jan 18, 10:31 AM: @MartinBernstorff merged this pull request with Graphite.


Documentation updates to some portal and entity functions.

Documentation comments in JSDoc syntax.

This has been sitting a while without any comments. Can I get some feedback on what the concerns are?


Some docs/comment updates for the new cast_ref() functions

@sdroege Thanks
👍

Awesome! Such comments are very welcome and help a lot to understand the code. Thanks a lot!


No longer works as expected

This example fails to work for me.
I tried downgrading to the Node version used to create this, but no success :(
Observed error:
Pact Binary Error: C:/.../node_modules/@pact-foundation/pact-node/standalone/win32-1.88.83/pact/lib/vendor/ruby/2.2.0/gems/pact-mock_service-3.9.0/lib/pact/mock_service/request_handlers/interaction_post.rb:1:in `require': cannot load such file -- pact/mock_service/request_handlers/base_administration_request_handler (LoadError)

I would recommend using the adapter that has been built, that came out of this initial proposal
https://github.com/pactflow/pact-cypress-adapter
Ideally we should update this example to use it.

all the example projects conform to the same api for interop so that isn’t preferred


kube-proxy + iptables

What exactly is the problem with --proxy-mode=iptables right now?

In v1.1* (v0.6.x of Kubernetes on ARM), it didn't work. I don't know why.
I actually tested it yesterday, and now with v1.2, it works! So I have enabled it in v0.7.0.
Please test it if you can

I was wondering because of a change I made for getting glusterfs working. I have it working with 1.1 on my local. It works if you move ip-masq config to flannel and explicitly disable it in docker.
It needs to be configured that way for 1.2 as well, so I'll put it in a PR. Applications like gluster discover their IP as the host's IP instead of the container IP if docker is configured to do the masqing.

https://github.com/luxas/kubernetes-on-arm/pull/82

Thanks, I think it's fixed with #82


voicing: sometimes notes will never turn off after being disabled in reaper

a specific / odd one, but there are times a rather innocent patch becomes unruly and impossible to turn off. have to restart Reaper.
steps:

create some patch in reaper with midi events
play it on repeat, disable the track
...
at some point, turn the track back on, and it will have a stuck note on

doing a "panic" in WS menus will stop the note, but any time it plays that stuck note will return. only option is to restart Reaper.
experienced while making the cinematic tag port

problem was the event buffer was overflowing. we supported a max of 64 events per buffer process, which is reasonable during normal operation. but there are certain activities in Reaper that can overflow this easily. Especially when audio processing stalls at any point, midi events can traffic jam and the buffer fills.
we had no buffer overflow checking, and the buffer was unnecessarily small (64 events). when it overflowed, heap corruption clobbered over mIsPedalDown and was keeping notes on at all times because currently i have no pedal connected.
fixes:

increased buffer to 128. for most purposes even 64 is fine but there's no cost to increasing.
when buffer is full, we AllNotesOff and avoid an overflow condition exceptionally.


[CORE] ParquetFileForamt/OrcFileFormat has code like if (xxx && false)

Description
Not sure why we make this if branch always skipped.
See https://github.com/apache/incubator-gluten/blob/main/shims/spark32/src/main/scala/org/apache/spark/sql/execution/datasources/parquet/ParquetFileFormat.scala#L204

Hi @binmahone, do you remember the reason?

@PHILO-HE does you try if CI pass if remove the false check ?

@PHILO-HE does you try if CI pass if remove the false check ?

@gaoyangxiaozhu, thanks for your comment! I will try to do that.

Hi @binmahone, do you remember the reason?

Sorry I can't really recall. When the intial PR was checked in, velox backend did not actually supported native writer.

Hi @binmahone, do you remember the reason?

Sorry I can't really recall. When the intial PR was checked in, velox backend did not actually supported native writer.

@binmahone, I see. Anyway, thanks for your reply!

As confirmed with @JkSelf, we can remove this code to always use vanilla Spark's API for Velox backend. #6663 is removing the useless code.


Skip perfect scores in stdout summary

Currently, the collect/autorun command lists every audit. When there are a lot of audits, this produces a very long output in CI (full example here).
ESLint audits

● Enforce a maximum number of lines per file                          6 warnings
● Enforce naming conventions for everything across a codebase         1 warning
● Require Promise-like statements to be handled appropriately         1 error
● "catch" clauses should do more than rethrow                         passed
● "switch" statements should not be nested                            passed
● "switch" statements should not have too many "case" clauses         passed
● A "while" loop should be used instead of a "for" loop               passed
● All branches in a conditional structure should not have exactly     passed
  the same implementation
● Boolean expressions should not be gratuitous                        passed
● Boolean literals should not be redundant                            passed
● Cognitive Complexity of functions should not be too high            passed
● Collapsible "if" statements should be merged                        passed
● Collection and array contents should be used                        passed
● Collection elements should not be replaced unconditionally          passed
● Collection sizes and array length comparisons should make sense     passed

We could truncate the output by compressing audits with perfect scores into a one line, which simply summariez how many there are:
ESLint audits

● Enforce a maximum number of lines per file                          6 warnings
● Enforce naming conventions for everything across a codebase         1 warning
● Require Promise-like statements to be handled appropriately         1 error
● ... 12 audits with perfect scores omitted for brevity ...

Optionally, we could show the full list when --verbose flag has been specified.

Could we move the flag into persist options?
Verbose logging will print a lot of other infos too plus plugin internal things. This information is helpful for debugging but if you just want to see more audits maybe unexpected.
wdyt?

Could we move the flag into persist options?

I don't think this change should be tied to persistence. Whether or not audits with perfect scores are printed in the CLI output should not affect the content of generated reports. I see it as a CLI output readability enhancement.
Will it be overkill to introduce a new global option, like --showAllAudits, defaulting to false?

I wouldn't add any extra options for this, it would be needlessly complicated and likely noone would use it. The vast majority of users will configure little to nothing. I suggested the --verbose flag because we already have it anyway and its a strong convention (unlike any custom flag we could add). And there is a general expectation that --verbose will result in many more logs than by default, so listing all audits seems like a reasonable side-effect to me.
I agree that persist options is the wrong place for such a flag anyway, I wouldn't consider stdout to be persistent. But I wouldn't add a new flag regardless.
At the end of the day, if the user wants to see all audits, the stdout summary isn't the best place to look for it. They have the full list of audits in report.md and report.json already, which is much more accessible than re-running everything with a different flag.
I would add that listing all audits in stdout when --verbose is optional as far as I'm concerned. If perfect audits are always omitted regardless, then that's fine too. Basically, let's keep it simple (for us and for users).


[DBUS] Don't break when reading settings from org.freedesktop.portalSettings v1

https://github.com/AvaloniaUI/Avalonia/pull/15568 made an attempt to correctly handle int32-in-variant-in-another-variant value ([Variant: [Variant(uint): 2]] in qdbus notation), however the current version of Tmds.DBus.Protocol simply reads it as a single VariantValue with int32 type (https://github.com/tmds/Tmds.DBus/issues/282).
The PR removes GetItem call that wasn't intended to be used for unwrapping variants and adds a type check later just in case.
Verified with Plasma 5.27.
@affederaffe

Shouldn't this be fixed in Tmds.DBus.Protocol then?
Per spec we expect the Variant to not be collapsed, so in my opinion this is the wrong layer to fix it.
In the meantime, we can easily revert the initial PR, the old Tmds.DBus.SourceGenerator Variant system has proven to work as expected.

Closing this PR, as dbus upgrade was reverted.


Adding only the dist folder to the paths

I think the problem was there were a bunch of files making into the asset path from other node_modules. Adding only what's needed seems to help.

:+1:


Notebook doesn't output as expected

Did I miss a config step or stumble across an incompatibility of some sort?

REPL and example notebooks behave the same.
I installed the extension and the MS Jupyter extension and followed the Getting Started.

Please could you provide the following info:

Version of VS Code
Version of the extension
Output from the output panel named TypeScript kernel
Output from your developer tools (go into the command Toggle Developer Tools and open the console window)

Same issue, details:
VSCode version: 1.63.2
Extension version: v2.0.6
Output from TypeScript Kernel panel:
Starting node c:\Users\siddh\.vscode\extensions\donjayamanne.typescript-notebook-2.0.6\out\extension\server\index.js & listening on 56412 & websock on 56411
Server Exited, error: [Error: spawn node ENOENT
	at Process.ChildProcess._handle.onexit (internal/child_process.js:269:19)
	at onErrorNT (internal/child_process.js:465:16)
	at processTicksAndRejections (internal/process/task_queues.js:80:21)] {
  errno: -4058,
  code: 'ENOENT',
  syscall: 'spawn node',
  path: 'node',
  spawnargs: [
    '--inspect=56412',
    'c:\\Users\\siddh\\.vscode\\extensions\\donjayamanne.typescript-notebook-2.0.6\\out\\extension\\server\\index.js',
    '--port=56411',
    '--config=C:\\\\Users\\\\siddh\\\\AppData\\\\Local\\\\Temp\\\\tmp-36152-PFHlLJIFP3I7-.json'
  ]
}
Server Exited, code = -4058

No output in Developer Tools Console

I think the issue is not with the extension, I had accidentally corrupted my NodeJS installation on my machine; reinstalling NodeJS fixed the issue for me


Debug code for file writing breaks in MS-DOS

The debug file writing thing that puts all the arguments from -i in the file specified in -o breaks when -i has more than 2 arguments!

fixed


QuizSet should be related with TopicSet

QuizSet should be related with TopicSet.
bug in #35 .

Fixed.


Add Mixin that allows refresh_from_db

This PR aims to allow model.refresh_from_db() for a model that contains protected fields. fixes #174
Inspired by django internal refresh_from_db

request review @kmmbvnr

Let's try to merge and hope )

merged


Patch Failure (realease 2.10.1, kernel 4.4.0-116)

Required Info

Camera Model
SR300

Firmware Version

Operating System & Version
Linux Ubuntu 16

Kernel Version (Linux Only)
4.4.0-116

Platform
PC

SDK Version
2.10.1

Issue Description
encountered error while patching (from dmesg):
videodev: version magic '4.4.0-116-generic SMP mod_unload modversions ' should be '4.4.0-116-generic SMP mod_unload modversions retpoline '
The error displayed in the patching session was:
Handle videodev :
Applying the patched module ... modprobe: ERROR: could not insert 'videodev': Exec format error
Failed to insert the patched module. Operation is aborted, the original module is restored
Verify that the current kernel version is aligned to the patched module version
The original  videodev  module was reloaded
It was working with 4.4.0-112 kernel

patch worked when I boot with 4.4.0-112 kernel

This issued might be caused by inconsistency between 116 kernel distribution and src code.

[Realsense Customer Engineering Team Comment]
Hi @marvin-hao,
still need any further help?


Add 'tab' option

Hi there!
One of the maintainers on tslide/tslide is trying to add this renderer to the project, but ran into an issue with the size of tabs changing expecting behaviour. So, thought I'd throw this PR out to add an option to change the default tab fixture (which I thought was 4, but was actually 3!).
I was going to add the option to require numbers to specify the number of spaces, but then you can't use a \t char in place of spaces (possible case), so instead it can currently take any arbitrary string.
Let me know what you think of the PR, cheers!

Hi. Thanks for this! I don't remember if the tab was set to 3 because it looked better or just laziness, but this customise step makes sense.
Are we sure the tab property is the most intuitive API? Should it be useTabs and tabSize instead, or do you think this is fine? Another option could be to have tab: 4 or tab: '\t' but as with specifying tabs: '   ' you can have issues where people put in what ever (unsanitized etc), but maybe this isn't a problem.

Sounds good.
At the moment there is no error management in the codebase - would you want the sanitization to fall back on on the default tab option if it the user provided tab failed the check?

I think that is just fine 👍 I can add you as a collaborator to the project if you want?

Sounds great 👍 Nice one. I'll add this and merge it in.
Would you mind publishing the new version yourself, or give collab on the npm package as well?

I can add it to NPM so you don't have to do all the tagging and changelog-writing stuff. But if you want I can add you on NPM as well.

I am happy with you doing that stuff :wink:.

Hehe, not surprised 🍰

I'll do a minor release later today!

Awesome, looking forward to it.
Thanks for being super responsive!

All credit to you for giving proper insights into what the problem is, why it's a problem and to provide a solution. Without that I probably wouldn't have found the time to do this right now.

~/Documents/Sites/repos/marked-terminal master 6s
❯ npm publish
+<EMAIL_ADDRESS>
https://github.com/mikaelbr/marked-terminal/releases/tag/v1.7.0


add minimum size options to the resizeable directive

I've added some options for minimum height and minimum width.
I tried to copy existing style and format as much as possible, but I'm not very accustomed to Angular/Typescript yet, so it might need some tweaks still.

@kukelekuuk00
I've merged your codes and done some changes. So I will close this PR and thank you again.


@alloy => [Bidding] Show spinner to remove flash of old amount, "not for sale"

Show a spinner when transitioning back to the auction artwork until the new top bid information comes in. This prevents the user from seeing the old bid amount and a "Not for sale" message for a brief moment until the new data loads.

So green, merging! :clap:


vim-cpywrite cost longer time than other plugins.

using vim --startuptime file
it take 230ms to load this plugin, much longer than other plugins.

Yikes!
I repeated your steps and got similar or worse results with vim and neovim on a virtualized Ubuntu image.
The output is attached for anybody who wants to tackle this issue.
srvadmin@ubuntu:~$ uname -a
Linux ubuntu 4.4.0-184-generic #214-Ubuntu SMP Thu Jun 4 10:14:11 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

vim-bench.log
nvim-bench.log

I traced the problem to the Python feature tests. According to the help topic at :help has-python:

when Python 2 and 3 are both available and loaded
dynamically, these has() calls will try to load them

The newest build holds off on calling has(python) until the first command call, and the error reporting function won't get loaded unless it's actually needed.
You may notice it takes longer to update the buffer on the first go, but your editor will start up a lot quicker:
awk '/.*plugin\/cpywrite\.vim.*$/' nvim_bench.log vim_bench.log
014.314  000.089  000.089: sourcing ./plugin/cpywrite.vim
052.832  000.082  000.082: sourcing ./plugin/cpywrite.vim

I'll be merging the  autoloaded version soon.
Thanks for your help!


Add owl4ce's dotfiles

Aesthetic OpenboxWM Environment. The complete setup, including configuration of several apps and bash scripting allows things to change with just one click and from the variables.
Thanks!

You do not need to manually push a new commit every time someone stars your repo: all the star counts are automatically updated once a week.

Thanks for the contribution. Sorry it took so long to get merged.


camel-salesforce: Change default API version to 50.

Current default is 34, which is ancient and causes issues that either don't have a good error message, or the underlying error message from salesforce never makes it to the user.

I like the idea of adding the change to the upgrade guide. Would that be camel-3x-upgrade-guide-3_7.adoc? Also, since api version is a component option, the new default value will show up in the doc for the salesforce component. Not sure anything additional would be needed here.

Yes, in the migration guide. In the doc i meant if there are reference in examples about api version :-)

Gotcha. I just looked through it and don't see anything that needs to be updated.


Fixed miscapitalisation in test/Narrowphase.js

Love the project, just fixed a minor typo :)

Fixes:
Fatal error: Cannot find module '../src/shapes/heightfield'
when building via grunt.

Duplicate of #241


fix: show category picker when creating invoices

Details

This PR shows category picker when creating invoices.
Fixed Issues

$ https://github.com/Expensify/App/issues/41281
PROPOSAL: https://github.com/Expensify/App/issues/41281#issuecomment-2087750193
Tests

Press FAB >> Send invoice >> Select any participant and a Collect workspace with categories enabled
Verify in confirmation screen, the Category menu shows and you can select a category
Press Send invoice
Open transaction report
Verify you can change the category

[x] Verify that no errors appear in the JS console

Offline tests

NA
QA Steps

Press FAB >> Send invoice >> Select any participant and a Collect workspace with categories enabled
Verify in confirmation screen, the Category menu shows and you can select a category
Press Send invoice
Open transaction report
Verify you can change the category

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/153004152/718f9f08-fea9-4e3a-b178-abc45451ecdc

Android: mWeb Chrome

iOS: Native

https://github.com/Expensify/App/assets/153004152/95657b46-aeea-41eb-989c-e01d3843b277

iOS: mWeb Safari

https://github.com/Expensify/App/assets/153004152/fd1d021c-08f4-4854-96b3-5903ce9fdbc0

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/153004152/ec6a3a49-44ac-484f-82f9-db91a362191a

MacOS: Desktop

https://github.com/Expensify/App/assets/153004152/86213ec5-3794-4346-9299-7fef1eda3139

Hide those fields in IOU confirmation screen but show them in transaction report to allow user to manually add tags/tax

@gijoe0295 I think this option seems good but are they able to edit these values with the updateInvoice API?
@davidcardoza A Better and more consistent solution is to fix the BE first and then apply the changes here.

@Pujan92 But does it go against with what we're fixing now (category is not in confirmation screen but is in money request view)? I know this is quite tricky because BE is at limited support.

It does but if we can't hold for the backend change then this is the most convenient change looks to me.

Thanks @Pujan92. Agree. I'll push the changes and note this so we could handle it later in follow-up PRs and QA team be aware of.

Exactly, Thanks!

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[ ] MacOS: Chrome / Safari
[ ] MacOS: Desktop

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

I'm reverting because it causes a crash in the App.

@gijoe0295 plz raise a new PR again with the original changes with the crash fix.

@cristipaval the problem is found by the @gijoe0295 and looks simpler to fix. How about we fix that in the quick PR instead of revert?

Sorry, I missed this. I've been ooo today and I jumped off after the revert.

This PR is failing because of issue https://github.com/Expensify/App/issues/41281
The issue is reproducible in: All Platforms
https://github.com/Expensify/App/assets/93399543/eb5d504d-4e2c-40a5-923a-84cc261f4c92
https://github.com/Expensify/App/assets/93399543/b07f7132-243f-467b-8801-d89222a8e753
https://github.com/Expensify/App/assets/93399543/e9cdf932-c797-4a84-8cc3-8ce8fb7c6d04
https://github.com/Expensify/App/assets/93399543/33a09e46-3cc5-49c7-b665-a9aafa533d28

🚀 Deployed to production by https://github.com/marcaaron in version: 1.4.71-6 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


Is there anyway to cut space between label and image in each item?

@elvinkim03 can you provide a screenshot and example of what you are trying to do?

@CrazyTim Sorry I was really busy. I've designed and changed to use image property now. But there's a problem sometime the image flick white when I try to change the image (I change to selected image that has highlighted) and I'm not sure what caused it

Hi @elvinkim03, it sounds like the image has not been loaded by the browser yet. Try pre-loading all images before you add them to the wheel. Have a look at how its done in this example page https://crazytim.github.io/spin-wheel/examples/themes.


Update react, react-dom to v17.0.1

Description

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as before)

Checklist

[ ] Read the Contributing Guide
[ ] Perform a code self-review
[ ] Comment the code, particularly in hard-to-understand areas
[ ] Add documentation
[ ] Add hook's story at Storybook
[ ] Cover changes with tests
[ ] Ensure the test suite passes (yarn test)
[ ] Provide 100% tests coverage
[ ] Make sure code lints (yarn lint). Fix it with yarn lint:fix in case of failure.
[ ] Make sure types are fine (yarn lint:types).

:tada: This PR is included in version 15.3.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 15.3.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Snapshot Mode for Arducam IMX296 on OAK-FFC-4P

Hi,
I'm trying to get snapshot triggered acquisition working for an IMX296 camera connected to an OAK-FFC-4P baseboard. My goal is to be able to send pulses at arbitrary times (and exposures) to control image acquisition. My approach was to use the example script below (modified from the example here) while supplying an external 5us 1.8v pulse to the headers directly on the camera boards. This seems to work fine when testing on OV9782 and AR0234 cameras, i.e. the cameras wait indefinitely for the pulse before capturing. With the IMX296 however, I get essentially continuous free-run despite applying a similar configuration. I'm using the XVS and GND headers on the IMX296 camera board as recommended by the Arducam documentation.
I see that IMX296 is listed as "fully integrated" on the list of supported sensors. Is it possible that snapshot feature is not yet supported?
Example Script:
import cv2
import depthai as dai
import numpy as np
import time

# Create pipeline
pipeline = dai.Pipeline()

# Define sources and outputs
camRgb = pipeline.create(dai.node.ColorCamera)
camRgb.setBoardSocket(dai.CameraBoardSocket.CAM_A)
xoutRgb = pipeline.create(dai.node.XLinkOut)
xoutRgb.setStreamName("rgb")

# Properties
camRgb.setResolution(dai.ColorCameraProperties.SensorResolution.THE_1440X1080)
camRgb.setPreviewSize(1440, 1080)
camRgb.setInterleaved(False)
camRgb.setFps(40)
camRgb.initialControl.setFrameSyncMode(dai.CameraControl.FrameSyncMode.INPUT)
camRgb.initialControl.setExternalTrigger(2,1)
camRgb.preview.link(xoutRgb.input)

# Connect to device and start pipeline
with dai.Device(pipeline) as device:

    qRgb = device.getOutputQueue(name="rgb", maxSize=4, blocking=False)
    frame = None
    counter = 0

    while True:

        if qRgb.has():
            counter+=1
            inRgb = qRgb.get()
            print(f'{counter} frame(s) detected.')
            if inRgb is not None:
                frame = inRgb.getCvFrame()

        if frame is not None:
            cv2.imshow(name, frame)

        if cv2.waitKey(1) == ord('q'):
            break

Hi @rajsinghmn,
For snapshot mode, you will need to put the IMX296 to slave mode explicitly by hardware configuring the relevant pin.
Also, I think that IMX296 could work similarly to OV9782 in continuous mode for the stereo pair : one as master, other as slave and XVS is driven by the master. Once again, you will need to configure the relevant hardware pin to put the sensor into the slave mode explicitly.
Best Regards,
Khang

Support (with a note) ready in 47055d5270b13adbb740cb1a897b7f9fe7a98aa5


Calculate length

Description
It would be nice to be able to calculate a length, for example a font size or line length, i.e. convert an integer to pt or em.
Use Case
This can be used in templates, for example to dynamically size lines based on the input.

You can already do this
#let f(x) = {text(size:x*1pt)[hello]}

Agree, this would be nice.  The following errors:
  for i in range(-3, 4) {
    move(
      dx: (i - 3cm), dy: (i + 3cm),
    )
  }


Update with new functions in OpenCL-Headers repo

The opencl-sys repo has been updated to reflect changes to the OpenCL-Headers repo.
The new functions should be added to this repo.

Incorporated in version 0.9.4.


Set up testing against the ndcube 1.3 branch as well as ndcube master

Hi @nabobalis, the recent API breaking changes to the ndcube master branch mean that testing sunraster against does not reflect whether sunraster will work with the stable release of ndcube.  Is it possible to set up additional CI tests that use the ndcube 1.3 branch, so we can confirm that sunraster v0.1 will work with ndcube v1.3.x?  Is that a difficult job?

It should be done already. Let me check.

The dev build checks with master for astropy, ndcube and sunpy. I can remove them and leave ndcube?

Actually if it's an easy thing, I actually need the tests to be against the 1.3 branch.  I want to make sure it's working with the planned but not yet released 1.3.1 version.  Is that difficult/possible?

But keeping the tests against master as well is important to know for keeping up with ndcube 2.0 development.

It tests with the latest released version of ndcube normally and the master version too.

OK.  So in order to be 100% sunraster works with ndcube 1.3.1 is to release it and then run the sunraster CI?
I guess that'll have to do.

Thanks!

Well if the 1.3.1 changes are on master, they will be tested.
It should be possible to setup the branch test.

OK, that'd be great.  Perhaps you could show me how to do that on Monday?

I opened a PR for this.


Test cornercases of current Mixins in Tamás' addons POC

As a developer of OpenSCD I would like to count on assurance that the big refactor of turning mixins into addons before we move into the development, hence we should test in a POC that all the edge cases of the current mixins' functionality works properly with addons

Won't do


Problem with ZEIT deploy

Please fix now.json file, does not work project at ZEIT deployment. Thanks for help.

can you provide the logs @daimonkor? cheers!

http://prntscr.com/mkpvlf

thanks @daimonkor, managed to deploy now using "version": 2 on now.json file: https://colyseus-examples-dhbbjzitqb.now.sh/
I've dragged the folder of the project to zeit-now's icon on my desktop, and the deployment was successful.
Cheers!

What is my problem? http://prntscr.com/mkqf2c

@daimonkor that's odd. It seems it didn't recognize it as a node application, and it's trying to download the index.ts file.
I've deployed just like this: https://drive.google.com/open?id=15TsVI52yUxfjrbDbz-V4gvSe3WiJ3dNd
Don't really know what's going wrong there :(

Magic, the same state http://prntscr.com/mkqjgk http://prntscr.com/mkqjr7 . Official application, downloaded today

With the current now.json, without "builds", it is deploying as static.
Do notice that our current Now 2.0 still doesn't support WSS, which is needed for this repository, if I understand it correctly.
Please @daimonkor, take a look at our examples before deploying.

But I saw worked sample https://drive.google.com/open?id=15TsVI52yUxfjrbDbz-V4gvSe3WiJ3dNd ). What is the magic. Client used ws

@daimonkor I can reproduce your issue using now from the command-line. I'll follow @paulogdm's suggestion and will update the repository as soon as I get it working

@endel Thank you very much

@daimonkor apparently now v2 still doesn't support WebSockets (as @paulogdm mentioned, and I thought it was only for Secure WebSockets 😅)
I've changed the now.json file to use v1 instead, which I've managed to deploy successfully from the command-line!
Let me know if it works for you @daimonkor

@endel I tested http://prntscr.com/mkslb9. Used node module now  Now CLI 13.1.3.

@daimonkor that's odd, here the command-line asks me if you'd like to proceed, and then it deploys sucessfully

@endel Version number are common, but they are different releases.

thanks @daimonkor, I guess I can deploy because my account may be older than yours, it's a shame they're disabling V1 for new users, given that V2 doesn't even support WebSockets yet. 😢

Still waiting support)

I'm afraid it will take long for them to support environments with WebSockets, you'd be better off using Heroku or a VPS, they support tickets about this are months old

@endel I will try use Heroku, thanks

Zeit is not listed anymore as a deployment target due to how their new system works


Debug.WriteLine messages now start with "[OSVR] ".

Applying feedback from line notes here:
https://github.com/OSVR/Managed-OSVR/pull/10

Great, thanks. Sorry I missed this one. GitHub notifications are a mess, grumble.


31may2016 docs updates

@RichardScothern can you please confirm that #1741 and #1748 are fixes that apply to the current release?

I have one more PR that i want to make and cherry-pick

[Current coverage][cc-pull] is 53.50%

Merging [#1758][cc-pull] into [docs][cc-base-branch] will decrease coverage by 6.71%

3 files (not in diff) in ...istry/storage/driver were modified. more

Misses +803
Partials -92
Hits -711

1 files (not in diff) in registry were modified. more

Misses +6
Hits -6

@@               docs      #1758   diff @@
==========================================
  Files           122        122
  Lines         10683      10683
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6432       5715   -717
- Misses         3658       4467   +809
+ Partials        593        501    -92

[][cc-pull]

Powered by Codecov. Last updated by [4f20717...408c468][cc-compare]
[cc-base-branch]: https://codecov.io/gh/docker/distribution/branch/docs?src=pr
[cc-compare]: https://codecov.io/gh/docker/distribution/compare/4f20717da9e143ebf99593efa41d1e741b56e87b...408c4684fafce7567398efb540ead9c250968698
[cc-pull]: https://codecov.io/gh/docker/distribution/pull/1758?src=pr

I confirm that they are.

sweet - I'm hoping to add #1759 to this in the next day or so.

will add #1762 when that's merged.

OK, done. that's alot of docs debt paid :(

Tested and LGTM, but the build is failing with
link error: (in page registry/index.md) /docker-trusted-registry/overview.md

I don't know what's causing the failure, since that overview.md file exists in the DTR repo.

yeah, that's due to the tests here being built with only the oss docs - I've an action item for out meeting that's related.


Desktop menu with first-class nesting

Feature request type
Enhance component
Component name
MudMenu
Is your feature request related to a problem?
Current menu is has a lot of gutter space (#9143)

is excessively large on desktop

has poor support for nesting (which has been the cause of a lot of issues)

Describe the solution you'd like
Add a dense option that resembles Material Design:

https://m2.material.io/components/menus
https://mui.com/material-ui/react-menu/
and rework the nesting so you can directly nest MudMenuItems instead of requiring sub MudMenus:
<MudMenu Label="Open Menu" Variant="Variant.Filled" Color="Color.Primary" AnchorOrigin="Origin.CenterCenter" TransformOrigin="Origin.TopLeft" Dense>
    <MudMenuItem>
        <MudMenu ActivationEvent="MouseEvent.MouseOver" AnchorOrigin="Origin.TopRight" TransformOrigin="Origin.TopLeft" Dense>
            <ActivatorContent>
                <MudMenuItem> Item 1 </MudMenuItem>
            </ActivatorContent>

            <ChildContent>
                <MudMenuItem Href="https://mudblazor.com" Target="_blank"> Open https://mudblazor.com in new tab </MudMenuItem>
                <MudMenuItem Href="/" Disabled="true"> Disabled Item 1.2 with navigation </MudMenuItem>
            </ChildContent>
        </MudMenu>
    </MudMenuItem>

    <MudMenuItem>
        <MudMenu ActivationEvent="MouseEvent.MouseOver" AnchorOrigin="Origin.TopRight" TransformOrigin="Origin.TopLeft" Dense>
            <ActivatorContent>
                <MudMenuItem Href="/">Item 2</MudMenuItem>
            </ActivatorContent>

            <ChildContent>
                <MudMenuItem Href="/docs/overview"> Item 2.1 Docs Overview</MudMenuItem>
                <MudMenuItem > Item 2.2 </MudMenuItem>
            </ChildContent>
        </MudMenu>
    </MudMenuItem>
</MudMenu>

<MudMenu Label="Open Menu" Variant="Variant.Filled" Color="Color.Primary" AnchorOrigin="Origin.CenterCenter" TransformOrigin="Origin.TopLeft" Dense>
    <MudMenuItem Text="Item 1">
        <MudMenuItem Href="https://mudblazor.com" Target="_blank"> Open https://mudblazor.com in new tab </MudMenuItem>
        <MudMenuItem Href="/" Disabled="true"> Disabled Item 1.2 with navigation </MudMenuItem>
    </MudMenuItem>

    <MudMenuItem Text="Item 2">
        <MudMenuItem Href="/docs/overview"> Item 2.1 Docs Overview</MudMenuItem>
        <MudMenuItem > Item 2.2 </MudMenuItem>
    </MudMenuItem>
</MudMenu>

Have you seen this feature anywhere else?
No response
Describe alternatives you've considered
No response
Pull Request

[ ] I would like to do a Pull Request

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Not to forget that there are multiple types of icons that have a different default size, which already cause problems with the MudNavMenu as @henon pointed out here: https://github.com/MudBlazor/MudBlazor/pull/9143#issuecomment-2429017572

Cascading moved to #10255


[TEVA-4349] Update Job Location Step

Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-4349
Job location step
Before

After

@josephhull676 The trust name needs to be updated on the Review page to match "Trust head office" like on the selection page.
This might need a discussion with a designer actually, because looking at the bottom screenshot from QA we have a different heading for location when head office has been selected

@josephhull676 The trust name needs to be updated on the Review page to match "Trust head office" like on the selection page. This might need a discussion with a designer actually, because looking at the bottom screenshot from QA we have a different heading for location when head office has been selected

Have updated this so it reads "Trust central office"


Writing to launch.json via WorkspaceConfiguration.update doesn't format nicely

VSCode Version: 1.7.1
OS Version: Windows 10

I'm using WorkspaceConfiguration.update to try and update existing launch.json files due to a change in data passed to our debug adapter. Code looks like this (I don't know if there's a better way; although update supports dotted names, this is inside an array?):
function update_launch_json_change_sdk_to_settings() {
	// Read launch.json config.
	let launchFile = vs.workspace.getConfiguration("launch");

	let configs = launchFile.get<any[]>("configurations");
	if (!configs)
		return;

	let hasChanged = false;

	// Find Dart CLI items that might need upgrading.
	configs.filter(c => c.type == "dart-cli").map(d => {
		// Remove the old sdkPath.
		if (d.sdkPath) {
			console.log("Found old sdkPath, removing...");
			d.sdkPath = undefined;
			hasChanged = true;
		}

		// Add the new debugSettings.
		if (!d.debugSettings) {
			console.log("Didn't find debugSettings, adding...");
			d.debugSettings = "${command.debugSettings}";
			hasChanged = true;
		}
	});

	if (hasChanged)
		launchFile.update("configurations", configs);
}

When I look at the changes that were made, the formatting has been lost so it's not obvious what the change was. Since this change is somewhat destructive to the end user, it would be nice if the diff was clean and they could see exactly what was modified.

Note: The original data was inserted from initialConfigurations in our package.json, we didn't manually format it.

@bpasero @DanTup It's important to give the minimal change to the JSON edit rewriter. So for Dan, instead of replacing the full configuration object, make multiple changes on the particular property.
Otherwise @bpasero we should do a diff in our code to get smaller changes.
I see an bug in my code that cases the new object to be flattened, I'll fix that.

@aeschli I'm not sure how to make a minimal change here - update accepts dotted names, but configrations is an array. Could you give an example of how I can modify a single value from the dart-cli launch configurations?

@aeschli thanks for fixing. I often also notice some whitespace issues where the new key ends up in the beginning of the line and not indented to the previous values. Maybe it is also something to look into so that the contents of the file look "user edited" still.

@aeschli

So for Dan, instead of replacing the full configuration object, make multiple changes on the particular property.

Could you give an example of how to do this? I only want to update dart-cli things inside the array but I'm not sure how to do this. The docs say dotted identifiers are supported, but I just tested using array indexes and it didn't work (it added a new item with the full string I provided as the name):
launchFile.update("configurations.0.debugSettings", "${command.debugSettings}");
launchFile.update("configurations[0].debugSettings", "${command.debugSettings}");

Resulted in:
{
  // original stuff
  ,
  "configurations.0.debugSettings": "${command.debugSettings}"
  ,
  "configurations[0].debugSettings": "${command.debugSettings}"
}

If you're fixing this by doing a diff in Code then this might be irrelevant, though if there is an easy way for me to do it now (in 1.6) that would be better.

I have to take back what I wrote. As this is an array its not possible. We would have to extend our API.

Gotcha, thanks for confirming!

I'm also using WorkspaceConfiguration.update in Toggle Excluded Files and am having the same issue. I am updating the files.excludes setting.
Before calling update:
    "files.exclude": {
        "**/node_modules/": true,
        "**/jspm_packages/": true,
        "**/bin/": true,
        "**/obj/": true,
        "**/wwwroot/dist/": false
    },

After calling update:
    "files.exclude": {"**/node_modules/":false,"**/jspm_packages/":false,"**/bin/":false,"**/obj/":false,"**/wwwroot/dist/":true},

It would be great if the setting was formatted before being replaced. That way there won't be contention between a user editing the file (and it being formatted) and the api.

#13436 fixes the issue of the newly inserted code not being formatted.


Refactor typeahead

This PR is to refactor the typeahead component so that its functionality is added to the input component rather than being a separate component.

 Lookup pattern component

Aria message aria_min_chars is being repeated twice in VoiceOver for Mac


Adds kwargable decorator

Kwargable decorator can be applied to any transformed fun (grad/vmap/etc.) to support calling with args/kwargs/defaults.
Can update/test all fun transforms to apply this by default in a follow-up PR.

It might be helpful to look at the argnums_partial helper function from api_util.py that is currently used to implement partial application of positional arguments, e.g., inside value_and_grad:
https://github.com/google/jax/blob/140c9ea937a4ed436d9039bf7d73d7dcb3869373/jax/api.py#L466-L467
I suspect integrating this at lower level could facilitate doing this wrapping in a most efficient way.

(I'm assuming that you are iterating on this PR and there is no immediate action required from us.)

I tried prototyping my suggested approach in https://github.com/google/jax/pull/3532

Any news on this?
In general I find that adding kwargs support to transformed functions would be quite important


Let CMake handle prefix of include path

Original pull request by Florian Franzen (Bitbucket: [Florian Franzen](https://bitbucket.org/Florian Franzen), ).

There is no need to add the prefix here as relative path are always assumed relative to the prefix by CMake.
Adding the prefix here however leads to an incorrect include path if absolute paths are being used.

Original comment by Volker Enderlein (Bitbucket: VolkerEnderlein, GitHub: VolkerEnderlein).

Thank you very much for the patch, it is highly appreciated.


Moc labs review patch 8

Module: 00
Lab/Demo: 00
Fixes # .
Changes proposed in this pull request:

Submitted by ParamRamki on behalf of MOC Labs Review

I applied this change to the Jan_2022_scrub branch and will merge this evening. Thanks!


[css mode] Case-insensitive parsing of grammar tokens

Grammar tokens in CSS is case-insensitive as per https://www.w3.org/TR/css-syntax-3/#rule-defs
This PR makes css mode addon respect that.
A quick test in devtools timeline profiler doesn't show any perceivable difference on a relatively complex and big CSS.
Not sure how to add tests (the contributing guide suggests that)... Probably in mode_test.js but it's not obvious. It might make sense to add some uppercase tokens in mode_test.css like @MEDIA and a couple of random properties.

Thank you! Merged as b1bf7b3ad5394. Tests for the CSS mode live in mode/css/test.js. I've added one in 74e7447cf7.


Handle cases where ServiceBus message has no payload

Apparently, a Service Bus message may have no payload at the protocol
level, so the worker must account for that.
Fixes: #330

@elprans, I believe this should be ready to merge?

Ping. I believe this should be good to check in?


Cifar10 - fp16 + convergence tests

Attempt to speed up cifar10 training: cifar10/cifar10-convergence-playground.ipynb

Basically try to use high learning rates + CLR and beat our original cifar10 benchmark
The paper (listed in the notebook) has some great resources on hyperparameter tuning for cifar10
One improvement is to use cyclical momentum - inverse proportional to learning rate increase

Time profiling fp16 model conversion: fp16/cifar10-fp16-speed-test.ipynb

Doesn't seem to speed up anything so far. Added comments at the bottom of the notebook
It's also weird that training on 32x32 size images isn't any slower than 8x8. Will need to profile the dataloader

@brettkoonce


corrected navbar-brand text

Fix #51
I have corrected the navbar-brand in all html pages to use TimeConv instead of Navbar.

Thanks for your PR!


JavaScript

JavaScript
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
So that I can easily find and read the information
Acceptance Criteria
GIVEN a Prework Study Guide website
WHEN I view the Study Guide
THEN I can see the four topics I learned listed along with a suggestion on what I should study first

JavaScript section completed


Strapi v4 blogpost and demo

[x] How to Add Relevant Search to Your Strapi App Using MeiliSearch => v4
[ ]  Reuse existing draft blog post (private link) that explains how to create the front for the above tutorial
[ ]  Publish demo

Given the fact that the second tutorial is not closely related to Strapi (it is still going to be published but no mention to Strapi) and that a demo would not make sense with just the first tutorial, I am closing this.


[PhantomJS 2.1.1] matchMedia queries not honoring viewPort width and height

Which version of PhantomJS are you using? Tip: run phantomjs --version.
2.1.1

What steps will reproduce the problem?
2.1. Set a mobile view port and user agent.
2.2. Open a mobile user agent.
2.3. phantomJS MatchMedia says that he is a tablet instead of a phone.

Which operating system are you using?
macOS Sierra

Did you use binary PhantomJS or did you compile it from source?
Installed with npm install -g phantomjs

Please provide any additional information below.

I'm setting a mobile viewPort and userAgent:
var casper= require('casper').create({
    viewportSize: {
            width: 414,
            height: 736
    }
});

casper.userAgent = 'Mozilla/5.0 (iPhone; CPU iPhone OS 9_1 like Mac OS X) AppleWebKit/601.1.46 (KHTML, like Gecko) Version/9.0 Mobile/13B137 Safari/601.1';

After opening a given web page, always opens in tablet version instead of phone. The reason was this:
matchMedia('only screen and (max-device-width: 767px), only screen and (max-device-height: 767px)').matches;
This query should return true and returns false, since my view port is 414x736. Other browsers like chrome and firefox return true on this.
An additional information is that, the 'tablet' query returns true on phantom:
matchMedia('only screen and (min-device-width: 768px) and (min-device-height: 768px)').matches;
I have watched the web page dimensions in run time and they match what I have set on the viewPort but for some reason matchMedia doesn't agree.
Is there any known problem with PhanomJS  matchMedia ? I have been searching for a while and didn't find any precise information about this, only a few posts refering match media problems.
Thanks in advance.

PhantomJS is abandoned. The maintainer recommends you use Chrome Headless instead.
https://groups.google.com/forum/#!topic/phantomjs/9aI5d-LDuNE

Since PhantomJS is abandoned I let here an example on how to completely emulate a mobile device with Headless Chrome.
https://github.com/josebrandao13/headlessChromeMatchMedia


docker+machine Executor Is Not Working In eu-central-2 AWS Region

Describe the bug
GitLab CI pipeline fails when the solution is deployed in eu-central-2 AWS region because docker+machine executor is not supported in eu-central-2 region.
To Reproduce

Having the terraform module:npalm/gitlab-runner/aws - version = 5.9.0

AWS region: eu-central-2

Provision infrastructure by running: terraform plan && terraform apply

Infrastructure in AWS is successfully provisioned.

Gitlab Runner Manager is registered with the GitLab repository:

Trigger CI pipeline in the GitLab repo.

Pipeline fails:

Expected behavior

Scaling out works - Gitlab Runner Manager provisions new EC2 spot instances that run a CI job.
GitLab CI pipeline pass.
Scaling in works.

Additional context
AWS Environment - Logs From CloudWatch
Jan 13 13:04:57 ip-10-0-1-235 gitlab-runner:
{
    "driver": "amazonec2",
    "level": "error",
    "msg": "Error setting machine configuration from flags provided: Invalid region specified",
    "name": "runner-6kjscxd-runners-dev-1673615097-6f5cf581",
    "operation": "create",
    "time": "2023-01-13T13:04:57Z"
}

Jan 13 13:04:57 ip-10-0-1-235 gitlab-runner:
{
    "error": "read |0: file already closed",
    "level": "warning",
    "msg": "Problem while reading command output",
    "time": "2023-01-13T13:04:57Z"
}

Jan 13 13:04:57 ip-10-0-1-235 gitlab-runner:
{
    "error": "exit status 1",
    "fields.time": 43137570,
    "level": "error",
    "msg": "Machine creation failed",
    "name": "runner-6kjscxd-runners-dev-1673615097-6f5cf581",
    "time": "2023-01-13T13:04:57Z"
}

Jan 13 13:05:01 ip-10-0-1-235 gitlab-runner:
{
    "duration_s": 18.42350433,
    "job": 2455638,
    "level": "error",
    "msg": "Job failed (system failure): exit status 1",
    "project": 4140,
    "runner": "6kjs_cxd",
    "time": "2023-01-13T13:05:01Z"
}

Jan 13 13:05:01 ip-10-0-1-235 gitlab-runner:
{
    "builds": 0,
    "error": "exit status 1",
    "executor": "docker+machine",
    "level": "warning",
    "msg": "Failed to process runner",
    "runner": "6kjs_cxd",
    "time": "2023-01-13T13:05:01Z"
}

Local Test
.aws/config setup with eu-central-2 region
$ docker-machine create --driver amazonec2 --amazonec2-region eu-central-2 aws01
Error setting machine configuration from flags provided: Invalid region specified

docker executor
Autoscaling is not supported when the docker executor is used (if I am not mistaken - see A Brief Guide to GitLab CI Runners and Executors).

GitLab CI pipeline runs but scaling out is not working when changing the executor for docker

Terraform snippet (variables.tf)

variable "runners_executor" {
  description = "The executor to use. Currently supports `docker+machine` or `docker`."
  type        = string
  default     = "docker"
}

Error:
{"builds":0,"error":"exit code 1","executor":"docker","level":"warning","msg":"Failed to process runner","runner":"6kjs_cxd","time":"2023-01-13T12:32:12Z"}

Sounds interesting. Have to investigate this and will try to install the runner in eu-central-2 too.

Problem found. The regions are checked in the docker-machine driver. I created a merge request in the project. We have to wait for it and upgrade to the new version.
GitLab/docker-machine merge request

GitLab docker-machine reviewers not available in January.

Hi @kayman-mk, do you have already a plan when the eu-central-2 and other regions will be available for docker+machine executor (GitLab merge request was already reviewed and merged)?

Due to all the problems within the docker+machine and the Docker v23 update: It could be the case that it is already working with version 5.9.1 of this module. Do you have the chance to test it?

Yes, I will try it to provision resources into eu-central-2 region.

I am getting still the same error into deploying the solution in to eu-central-2 region:
GitLab CI/CD pipeline:

AWS Cloudwatch Logs:
Feb 15 10:13:16 ip-10-0-1-23 gitlab-runner:
{
    "driver": "amazonec2",
    "level": "error",
    "msg": "Error setting machine configuration from flags provided: Invalid region specified",
    "name": "runner-yyehpyy-runners-dev-1676455996-da045408",
    "operation": "create",
    "time": "2023-02-15T10:13:16Z"
}

Feb 15 10:13:16 ip-10-0-1-23 gitlab-runner:
{
    "error": "read |0: file already closed",
    "level": "warning",
    "msg": "Problem while reading command output",
    "time": "2023-02-15T10:13:16Z"
}

Feb 15 10:13:16 ip-10-0-1-23 gitlab-runner:
{
    "error": "read |0: file already closed",
    "level": "warning",
    "msg": "Problem while reading command output",
    "time": "2023-02-15T10:13:16Z"
}

Feb 15 10:13:16 ip-10-0-1-23 gitlab-runner: {
    "error": "exit status 1",
    "fields.time": 41118903,
    "level": "error",
    "msg": "Machine creation failed",
    "name": "runner-yyehpyy-runners-dev-1676455996-da045408",
    "time": "2023-02-15T10:13:16Z"
}

Feb 15 10:13:16 ip-10-0-1-23 gitlab-runner:
{
    "error": "exit status 1",
    "fields.time": 41118903,
    "level": "error",
    "msg": "Machine creation failed",
    "name": "runner-yyehpyy-runners-dev-1676455996-da045408",
    "time": "2023-02-15T10:13:16Z"
}

Sometimes, I am getting also this error related to Spot runner fails to deploy new runner #675
Feb 15 10:24:49 ip-10-0-1-238 gitlab-runner:
{
    "driver": "amazonec2",
    "level": "info",
    "msg": "(runner-yyehpyy-runners-dev-1676456689-aefcc7c5) Missing instance ID, this is likely due to a failure during machine creation",
    "name": "runner-yyehpyy-runners-dev-1676456689-aefcc7c5",
    "operation": "create",
    "time": "2023-02-15T10:24:49Z"
}

runner module version 5.9.1

Hm, may be something with the merge train But I have no idea a) how it works and b) where I can see the results. I ask the maintainer to clarify.

Shall be included in the latest version of GitLab docker+machine. But I think you won't get it running.
Please check #696 which posts a working configuration which fixes your problems.


Usage of Advanced Actions breaks mock server

Steps to reproduce:

Setup API using https://github.com/apiaryio/api-blueprint/blob/master/examples/12. Advanced Action.md example
Try to call Retrieve task method against Mock server in Console

Expected result:

Successful execution of request

Actual result:

Request fails with error "We are sorry, but the API call failed. Please, give it another try." with additional information in Inspector "This API request did not match any documented resource. Your URL or method are probably wrong."

I guess syntax of the example is correct. It looks like usage of Advanced Actions breaks mock server, because it supports only matching for Standard Actions.
We need to have mock server working with Advanced Actions usage. So what's a fix for that?

Hey @AlexKorovyansky. Thanks for the bug report. We are going to look into it and see why it's happening.

Hey,
I am happy to announce that we have just deployed a fix for our mockserver, and now your case use should work as expected.
Could you please give it a try and let me know if everything is working properly?
Feel free to reopen the issue if the problem persists.

Thanks @XVincentX for the updates!

Thanks @XVincentX
Sample is working now!
But in our real app it's still broken, after short investigation I can say that reason of the problem is usage of HOST with path.

HOST: http://api.site.com/general/path

(if I change HOST to http://api.site.com, it fixes the problem)
Can you support HOST variable with path?
Or how can I add general path to all API methods in other way?

@AlexKorovyansky We do not support paths in HOST. You would have to add the path to every URL in the API Blueprint.

Okay. In such case it's just idea for improvement. Thanks!

@AlexKorovyansky, I am afraid we did a mistake here. The behavior should be as follows:

Path SHOULD be supported in HOST
Advanced action SHOULD work in Apiary.io' mock server

However, while implementing the later, we have introduced a regression issue that broke the former. When we have realized we have rollbacked the "advanced actions".
The current situation is: Paths should work in HOST, the advanced actions in mock are not working but should (to be fixed soon)
Sorry for the confusion!

Oh, ETA for the fix? Can you do it till Jul 28? Otherwise I will need to
rewrite our API without usage of Advanced actions, because we need to have
working mock server.
On Thu, Jul 23, 2015 at 12:29 PM Z<EMAIL_ADDRESS>wrote:

@AlexKorovyansky https://github.com/AlexKorovyansky, I am afraid we did
a mistake here. The behavior should be as follows:

Path SHOULD be supported in HOST
Advanced action SHOULD work in Apiary.io' mock server

However, while implementing the later, we have introduced a regression
issue that broke the former. When we have realized we have rollbacked the
"advanced actions".
The current situation is: Paths should work in HOST, the advanced actions
in mock are not working but should (to be fixed soon)
Sorry for the confusion!
—
Reply to this email directly or view it on GitHub
https://github.com/apiaryio/api-blueprint/issues/229#issuecomment-123993800
.

@zdne ?

Can you please reopen this issue if it's not fixed?

@AlexKorovyansky The issue has been reopened, and we're working hard to make it done as soon as possible

Thanks for the update @XVincentX!

Is there any news on this ticket. My company has recently adopted apiary.co and are now experiencing the same bug.

Hey,
I am afraid I do not have any update for now, but I can surely tell you that we're hardly working on it and a solution should come up in the following days.
Please bear with us,
V.

@AlexKorovyansky
@chance-schultz
Hello,
I am happy to announce you that we have finally deployed Advanced Actions support for Apiary, and they should now work correctly.
Could you please give a new try to that and let me know if everything is working correctly?

I can confirm now it's working right. Thanks!

@XVincentX  Getting the error: "This API request did not match any documented resource. Your URL or method are probably wrong."
Is the mock server breaking again when using advanced actions?

Hey
you should probably provide an example APIB to reproduce the error.
@ayushav12 could you?

Here's the APIB in which I got the error:
CourtAvailability API
This API shows the sessions that can be booked in a facility.
Data Structures
Time (object)

hour (number)
minute (number)

Date (object)

day (number)
month (number)
year (number)

DateTime (object)

day (number)
month (number)
year (number)
hour (number)
minute (number)

Court Availability [/courts]
getAllCourtsAvailability [GET /courts/{date}]
This action retrieves all the sessions (color coded) for all the courts at a specific
date(date specified as URI parameter).

Parameters

date (Date) - Date to book the seesion

Request (application/json)

Attributes

Softbooked_Sessions (DateTime)
Booked_Sessions (DateTime)
Available_Sessions (DateTime)

Response 200 (application/json)

Attributes

User_id (number) - Id of the user
session_from (Time) - Start time for each available session
session_for (Time) - duration of each available session
retrieve_upto (Date) - retireves availability of courts
upto the date specified

getCourtAvailability  [GET /courts/{id}/{date}]
This action retrieves all the sessions (color coded) for a specified court at a specified
date(court_id and date specified as URI parameters).

Parameters

id (number) - Id of the court.
date (Date) - Date to book the session.

Request (application/json)

Attributes

Softbooked_Sessions (DateTime)
Booked_Sessions (DateTime)
Available_Sessions (DateTime)

Response 201 (application/json)

Attributes

User_id (number) - Id of the user.
session_to (Time) - Start time for available sessions
session_from (Time) - End time for available sessions
retrieve_upto (Date) - retireves availability of courts
upto the date specified

Can you try changing GET to POST in the both the actions?

I have to define the actions using GET method as per the design of the API. Can you suggest an alternative please??

GET actions shouldn't have request bodies.


Add Slice#unsafe_slice_of, #to_unsafe_bytes, #to_bytes

Resolves #11010, including making #hexdump and #hexstring work for arbitrary Slices.

Hm sorry, of all these things I like only the addition of unsafe_slice_of. It is a frequent operation and is marked as unsafe so that's fine.

to_unsafe_bytes is just an alias of unsafe_slice_of(UInt8), not worth the mental overhead.

I would actually put messing with endianness into unsafe territory as well, so my following reasonings are with that in mind:

to_bytes returns a system-dependent value without directly acknowledging it in its name. Instead I would suggest an equivalent to it in the docs of to_unsafe_bytes. Which, by the way, you do as Slice.new(to_unsafe.as(UInt8*), bytesize, read_only: true) but couldn't it instead be to_unsafe_bytes.dup?

Changing hexstring to become an alias of to_unsafe_bytes.hexstring and returning a system-dependent value is definitely not good. Just suggest the latter piece of code in the docs of hexstring.

And, well, seeing as my latter two items hinge on the existence of to_unsafe_bytes, maybe that one is actually fine.


Revert DG deletions

Codecov Report
Patch and project coverage have no change.

Comparison is base (72d1af5) 39.37% compared to head (91375ba) 39.37%.

Additional details and impacted files
@@            Coverage Diff            @@
##             master     #162   +/-   ##
=========================================
  Coverage     39.37%   39.37%
  Complexity      722      722
=========================================
  Files           225      225
  Lines          4973     4973
  Branches        497      497
=========================================
  Hits           1958     1958
  Misses         2908     2908
  Partials        107      107

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add Karius to users in README.md

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

@jessesuen @alexmt    Thanks for Argo and your support.
We are now using Argo in Karius, Inc.   Please accept this PR for adding Karius in Argo users.


updated composer.json for SensioGeneratorBundle

this is more readable, as the 2.5.2 was anyway locked

What is wrong with the 2.3 version? If it works, the requirement should not be increased.

there is nothing wrong, but the composer.lock file now pins 2.5.2 anyway...
https://github.com/symfony/symfony-standard/blob/2.8/composer.lock#L1568

@OskarStark and what is the issue ? The composer.lock contains the version selected by composer. This does not mean we have to bump the min requirement

there is no issue.
IMO it is not very transparent that ~2.3 uses 2.5.2 (just by reading the composer.json)
i know this is locked in the composer.lock, but didn't you think if we write ~2.5 is the same result with a much more clearer info to a developer?
this is just a proposal, feel free to close this PR ;-)

I think @fabpot often updates dependencies on the standard edition so the
next release has an updated composer.lock
Anyway we should still keep "lowest" dependencies in composer.json to avoid
conflicts with third-party bundles that may require an older version
2015-08-14 10:21 GMT+02:00 Oskar Stark<EMAIL_ADDRESS>
there is no issue.
IMO it is not very transparent that ~2.3 uses 2.5.2 (just by reading the
composer.json)
i know this is locked in the composer.lock, but didn't you think if we
write ~2.5 is the same result with a much more clearer info to a
developer?
this is just a proposal, feel free to close this PR ;-)
—
Reply to this email directly or view it on GitHub
https://github.com/symfony/symfony-standard/pull/844#issuecomment-131016702
.

to be more clear: in this case we could also use ~2.0, right?
my recommendation is, if we have patch versions, i would use them in the json file

@Pierstoval in this case, this would not change anything at all for conflicts, as the 2.5.2 is already locked....

Yep it is locked, but when you run a composer update for all deps and a package requires an older version, then the good one can be installed. But it's quite rare...

@Pierstoval , ok you are right, but is this really needed for this bundle?
as you said, @fabpot often updated some patch versions for different releases, but never the 2.3 of GeneratorBundle ;-)

I think that patch versions should be changed whenever changes in the main project (we're on the standard edition here, fully customizable, it's not like it was the framework repo) include modifications that are incompatible with older versions of the projects, it's more a matter of BC breaks policy explanation, saying something like "SensioGeneratorBundle 2.3+ is compatible", even if the lock file is on 2.5

In the composer.json file you should put the MINIMUM viable version. What version is then locked or chosen by the user, is a different thing.