"End of Central Directory record could not be found." when adding existing app

Set up new repository with AL-Go for AppSource template
Attempting to import .app file to populate the repository
New error; could this be something wrong with the app file itself?
(Let us know if you need any log sections expanded)
Current runner version: '2.308.0'
Operating System
Runner Image
Runner Image Provisioner
GITHUB_TOKEN Permissions
Secret source: Actions
Prepare workflow directory
Prepare all required actions
Getting action download info
Download action repository 'actions/checkout@v3' (SHA:f43a0e5ff2bd294095638e18286ca9a3d1956744)
Download action repository<EMAIL_ADDRESS>(SHA:73be67b4c349ca02aeaf5f52523d381824970b6e)
Complete job name: AddExistingAppOrTestApp
7s
Run actions/checkout@v3
Syncing repository: CAI-Software-Inc/Precious-Metals-Solution
Getting Git version info
Temporarily overriding HOME='D:\a_temp\c705b978-b7ef-481a-8242-51d1ca8aafac' before making global git config changes
Adding repository directory to the temporary git global config as a safe directory
"C:\Program Files\Git\bin\git.exe" config --global --add safe.directory D:\a\Precious-Metals-Solution\Precious-Metals-Solution
Deleting the contents of 'D:\a\Precious-Metals-Solution\Precious-Metals-Solution'
Initializing the repository
Disabling automatic garbage collection
Setting up auth
Fetching the repository
Determining the checkout info
Checking out the ref
"C:\Program Files\Git\bin\git.exe" log -1 --format='%H'
'296f48464393f04d75253f4af3821de65fbaa1c4'
19s
Run<EMAIL_ADDRESS>Run try { D:\a_actions\microsoft\AL-Go-Actions\v3.1\WorkflowInitialize/WorkflowInitialize.ps1 -eventId $ENV:eventId } catch { Write-Host "::Error::Unexpected error when running action ($($.Exception.Message.Replace("r",'').Replace("n",' ')))"; exit 1 }
_           _____          __              _____ _ _   _    _       _                 ____        __
/\   | |         / |        / |            / () | | |  | |     | |               | \      / |
/  \  | |  | |  __  ___   | | ___  _ __  | |  __ | || || | | |     __   __   ) |      | |
/ /\ \ | | || | | |/ _ \  |  / _ | '__| | | | | | |  __  | | | | ' \    \ \ / /  |_ <       | |
/ ____ | |____    | || | () | | || () | |    | || | | || |  | | || | |) |    \ V /   ) |  _   | |
//    _____|    _|___/  || ___/||     _||_||  ||_,|.__/      _() |_/  ()  ||
Checking AL-Go Org Settings variable (ALGoOrgSettings)
BaseFolder: D:\a\Precious-Metals-Solution\Precious-Metals-Solution
Checking AL-Go Project settings file in .AL-Go\settings.json (type = Project)
Checking AL-Go Repo settings file in .github\AL-Go-Settings.json (type = Repo)
Checking AL-Go Workflow settings file in .github\Test Current.settings.json (type = Workflow)
Checking AL-Go Workflow settings file in .github\Test Next Major.settings.json (type = Workflow)
Checking AL-Go Workflow settings file in .github\Test Next Minor.settings.json (type = Workflow)
Downloading BcContainerHelper latest version from CDN
BcContainerHelper version 5.0.5
BC.HelperFunctions emits usage statistics telemetry to Microsoft
telemetryScopeJson=7b22506172616d6574657273223a7b7d2c22456d6974746564223a66616c73652c22436f7272656c6174696f6e4964223a2262616663623763642d316534352d346361332d383261612d306664353234333663623234222c22506172656e744964223a22222c22416c6c506172616d6574657273223a7b7d2c22546f704964223a2262616663623763642d316534352d346361332d383261612d306664353234333663623234222c224e616d65223a22414c2d476f20776f726b666c6f772072616e3a204164644578697374696e674170704f7254657374417070222c22537461727454696d65223a225c2f446174652831363932393739373732373234295c2f222c2250726f70657274696573223a7b226576656e744964223a22444f30303930222c226263436f6e7461696e657248656c70657256657273696f6e223a22352e302e35222c22697341646d696e6973747261746f72223a2254727565222c22737461636b5472616365223a225b5c6e2020496e697454656c656d6574727953636f70652061742054656c656d6574727948656c7065722e7073313a206c696e65203231345c6e202043726561746553636f70652061742054656c656d6574727948656c7065722e70736d313a206c696e652037355c6e2020576f726b666c6f77496e697469616c697a652e70733120617420576f726b666c6f77496e697469616c697a652e7073313a206c696e652033375c6e202030323036323965642d623037352d343035382d623766362d6162393061376463643963332e7073312061742030323036323965642d623037352d343035382d623766362d6162393061376463643963332e7073313a206c696e6520325c6e20205c7530303363536372697074426c6f636b5c7530303365206174205c75303033634e6f2066696c655c75303033655c6e5d222c22414c476f56657273696f6e223a2276332e31222c2274797065223a22417070536f7572636520417070222c2274656d706c61746555726c223a2268747470733a2f2f6769746875622e636f6d2f6d6963726f736f66742f414c2d476f2d417070536f75726365406d61696e222c227265706f7369746f7279223a224341492d536f6674776172652d496e632f50726563696f75732d4d6574616c732d536f6c7574696f6e222c2272756e417474656d7074223a2231222c2272756e4e756d626572223a2232222c2272756e4964223a2235393738303338363232227d2c224576656e744964223a22444f30303930227d
correlationId=bafcb7cd-1e45-4ca3-82aa-0fd52436cb24
Removing BcContainerHelper
24s
Run<EMAIL_ADDRESS>Run try { D:\a_actions\microsoft\AL-Go-Actions\v3.1\AddExistingApp/AddExistingApp.ps1 -actor $ENV:_actor -token $ENV:_token -parentTelemetryScopeJson $ENV:_parentTelemetryScopeJson -project $ENV:_project -url $ENV:_url -directCommit ($ENV:directCommit -eq 'Y') } catch { Write-Host "::Error::Unexpected error when running action ($($.Exception.Message.Replace("r",'').Replace("n",' ')))"; exit 1 }
Cloning into 'Precious-Metals-Solution'...
Your branch is up to date with 'origin/main'.
Already on 'main'
Switched to a new branch 'paw3cohw.sk1'
Downloading BcContainerHelper latest version from CDN
BcContainerHelper version 5.0.5
BC.HelperFunctions emits usage statistics telemetry to Microsoft
Reading .github\AL-Go-Settings.json
Downloading C:\Users\runneradmin\AppData\Local\Temp\41b3822f-64da-46bf-90f6-0be7897485db.app
Downloading using WebClient
Extracting C:\Users\runneradmin\AppData\Local\Temp\41b3822f-64da-46bf-90f6-0be7897485db.app
Error: AddExistingApp acion failed. Error: Exception calling ".ctor" with "2" argument(s): "End of Central Directory record could not be found." Stacktrace: at Extract-AppFileToFolder, C:\Users\runneradmin\AppData\Local\Temp\800db90d-bfd6-4d0d-aff2-5d91cf2f7d5f\BcContainerHelper\AppHandling\Extract-AppFileToFolder.ps1: line 85 at expandfile, D:\a_actions\microsoft\AL-Go-Actions\v3.1\AddExistingApp\AddExistingApp.ps1: line 71 at getfiles, D:\a_actions\microsoft\AL-Go-Actions\v3.1\AddExistingApp\AddExistingApp.ps1: line 27 at , D:\a_actions\microsoft\AL-Go-Actions\v3.1\AddExistingApp\AddExistingApp.ps1: line 107 at , D:\a_temp\d1e2ae0e-b22c-430e-badf-f4f3831f80f0.ps1: line 2 at , : line 1
AL-Go action ran: AddExistingApp Telemetry Correlation Id: 06b5a9b1-5895-4143-a43e-61b6bc5994ba
Removing BcContainerHelper
Error: Process completed with exit code 1.

Apparently it was an issue with the app archive (zip file). I had exported the app.json, edited the version number, and re-added it to the archive. Tried again with an app that had been compiled natively with the correct app.json contents, and it went in just fine.


Please Review

This documentation is outdated and it's last update is 07/24/2017, apparently the only way the documentation team does a review is when someone attempts to find a pertinent piece of information.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: c377fa1e-2274-704a-dcfa-4ac02659bf87
Version Independent ID: 1ba8a48b-a99e-096b-4822-63d62379e605
Content: Create, change, or delete an Azure network interface
Content Source: articles/virtual-network/virtual-network-network-interface.md
Service: virtual-network
GitHub Login: @jimdial
Microsoft Alias: jdial

@jeffpatton1971 thanks for the feedback. Can you point out a few specific thins that need updating?
I have assigned the issue to the content author to evaluate and update as appropriate.

@jeffpatton1971 The date you see on the page is the last date the entire article was reviewed. It has been updated several times since that date however. Is there a specific inaccuracy that should be fixed? What are you trying to find that you're unable to find?

@jeffpatton1971 Since we haven't heard back, we'll close this issue. If you saw any incorrect information though, please let us know. Thanks. #please-close

@jeffpatton1971 We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Improving locale test

Fixes #18205
Checklist

[ ] documentation is added or updated
[x] tests are added or updated

Done

Dmitry Belyavskiy wrote:

Improving locale test

Is locale test skipped if system does not support "locale" used in test?
I could found "skip" message.
Roumen

For Github CI purposes I added explicit installation of the Turkish langpack. I have no idea how to check if the particular locale is present

This pull request is ready to merge

Merged both to 3.0 and master. Thanks!


Add support for Artifact Registry in yarn

I have a web project that uses yarn v1 for package management hosted on Google App Engine.
Newly, I am trying to use private npm packages managed by Artifact Registry in my project.
I believe that buildpacks recognizes the .npmrc when building App Engine and automatically generates an access token if the package manager is npm, but yarn does not support automatic generation of this access token, so I would like you to consider supporting this.

I managed to hack it by adding a yarn preinstall hook to package.json
    "preinstall": "printf \"@SCOPE:registry=https://private.repository/\n//private.repository/:always-auth=true\n\n//private.repository/:_authToken=$(gcloud auth print-access-token)\" > .npmrc; yarn install --ignore-scripts; kill -9 $(ps | grep 'yarn.js install' | awk 'NR==1' | awk '{print $1}')"

Makes sense. For additional context, it sounds like a request to extend the capabilities of this feature we introduced in App Engine / Cloud Functions (https://cloud.google.com/appengine/docs/standard/nodejs/specifying-dependencies#private_dependencies_with_artifact_registry) that allows users to access their packages hosted in Artifact Registry without performing additional configuration.
I think yarn would be a good next package to pick up to support Node.js workloads

+1 for this. Ran into the same problem. heart

Enabled AR support for yarn1 -> https://github.com/GoogleCloudPlatform/buildpacks/commit/92cbbdebc4f810d757e2dc44fa9599fca9a7936c

Enabled AR support for yarn2 -> https://github.com/GoogleCloudPlatform/buildpacks/commit/e924f3bfa5ed17e0d755b6df24568e5f6f57eb34

For future reference, docs have also been updated on GCP Buildpacks Node.js page


Configure tsup as library builder

Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time.
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[ ] Run the tests with npm run test and lint the project with npm run lint and npm run prettier

Based on the recommendations from #376, tsup seems to be a cleaner solution for building ESM and CJS libraries, and so far I kinda like it. Typing will still be handled by tsc, as I don't like having duplicated declaration files for each format (package.json already handles that).

Ok, unfortunately I found a major issue with the setup. bundle is configured to true, which no only increases the library size exponentially, but also makes instanceof useless, as the classes are repeated rather than being the same.
I will think around this issue, but we are back to the begining: ts and node disagree on imports path resolutions.
I think it's about time to drop cjs for good...

Dropping CJS seems like a good alternative since now sync require(esm) is supported in node LTS

Closing in favor of #392


Reservation Rate excel export

Changes are well documented in commit messages and code!
Not to be merged quite yet!
To be done:

[x] Tests

Tests are done, but tests unrelated to these changes are failing.

[ ] Make up our mind on method of time filtering

See frontend PR: https://github.com/City-of-Helsinki/huvaja/pull/338

Example of generated excel file.

Most of the tests that were failing were due to a translation mismatch. So nothing critical and doesn't have to be bothered with in this PR. I did however remove another test that was failing due to code changes from a ~year ago that made the test void.

Added translations to API error messages for fields that the user selects on the frontend.


Uploading Multidimensional Tiffs for Segmentation

Hello, I'm going through the pre-processing procedures and am uploading a MassCorrected-Filtered.tiff as a multidimensional tiff.  I set the MIBItiff parameter to True.  My nuc marker is "dsDNA" and my membrane is 'CD45'.  Such as below.  When I try to load channels load channels to be included in deepcell data I get an error regarding indexing.  Is it not recognizing the channels?*
MIBItiff = True
MIBItiff_suffix = "-MassCorrected-Filtered.tiff"
nucs = ['dsDNA']
mems = ['CD45']
data_utils.validate_paths([data_dir,tiff_dir,deepcell_dir, ])
points = os.listdir(tiff_dir)
points = [point for point in points if os.path.isdir(tiff_dir + point) and point.startswith("Point")]
if MIBItiff:
points = [point for point in points if point.endswith(MIBItiff_suffix)]

channels = (nucs if nucs else []) + (mems if mems else [])
if MIBItiff:
data_xr = data_utils.load_imgs_from_mibitiff(tiff_dir, mibitiff_files=points, channels=channels)
else:
data_xr = data_utils.load_imgs_from_tree(tiff_dir, img_sub_folder="TIFs", fovs=points, imgs=channels)
data_utils.generate_deepcell_input(data_xr, deepcell_dir, nucs, mems)

IndexError                                Traceback (most recent call last)
 in
2 channels = (nucs if nucs else []) + (mems if mems else [])
3 if MIBItiff:
----> 4     data_xr = data_utils.load_imgs_from_mibitiff(tiff_dir, mibitiff_files=points, channels=channels)
5 else:
6     data_xr = data_utils.load_imgs_from_tree(tiff_dir, img_sub_folder="TIFs", fovs=points, imgs=channels)
/usr/local/lib/python3.6/site-packages/segmentation/utils/data_utils.py in load_imgs_from_mibitiff(data_dir, mibitiff_files, channels, delimiter, dtype)
73                       for mt_file in mibitiff_files]
74
---> 75     test_img = io.imread(mibitiff_files[0], plugin='tifffile')
76
77     # check to make sure that float dtype was supplied if image data is float
IndexError: list index out of range

what is the full name of one of the MIBItiff files you're uploading?

The full name is "20200522_MIBI_Titration_Tonsil_A-MassCorrected-Filtered.tiff"

Great!  So in the third code cell of the notebook, you should see the line:
points = [point for point in points if os.path.isdir(tiff_dir + point) and point.startswith("Point")]
If you remove this line, it should work correctly.  Sorry about that!  Please let us know if another problem occurs.

Got it thanks!  I was able to get the segmentation to work after this.


Stop then start laradock the global composer package is missing

Description:

Hi ! I have a problem when using laradock.
I installed a package in workspace with the commond composer global require deployer/deployer,
but when I stop the laradock with docker-compose down,
then start the laradock with docker-compose up -d nginx mysql redis workspace elasticsearch, the global compser package in workspace is missing.
The same problem occurs in elasticsearch, when I install a plugin, the plugin is missing when I stop the laradock then start laradock.
Expected Behavior:

Context information:
Output of git rev-parse HEAD
0d086024a8b7cff30f45860fe28c9ae896281bc8

Output of docker version
Client: Docker Engine - Community
 Version:           19.03.6
 API version:       1.40
 Go version:        go1.12.16
 Git commit:        369ce74a3c
 Built:             Thu Feb 13 01:27:49 2020
 OS/Arch:           linux/amd64
 Experimental:      false

Server: Docker Engine - Community
 Engine:
  Version:          19.03.6
  API version:      1.40 (minimum version 1.12)
  Go version:       go1.12.16
  Git commit:       369ce74a3c
  Built:            Thu Feb 13 01:26:21 2020
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.2.12
  GitCommit:        35bd7a5f69c13e1563af8a93431411cd9ecf5021
 runc:
  Version:          1.0.0-rc10
  GitCommit:        dc9208a3303feef5b3839f4323d9beb36df0a9dd
 docker-init:
  Version:          0.18.0
  GitCommit:        fec3683

Output of docker-compose version
docker-compose version 1.24.0, build 0aa59064
docker-py version: 3.7.2
CPython version: 3.6.8
OpenSSL version: OpenSSL 1.1.0j  20 Nov 2018

System info: Mac, Windows or Linux. Include which disto/version
OS: Ubuntu 18.04.4 LTS x86_64
Kernel: 5.3.0-40-generic

Steps to reproduce the issue:

Install package in workspace with composer global require deployer/deployer.
Stop  laradock with docker-compose down.
Start laradock with docker-compose up -d nginx mysql redis workspace elasticsearch
Enter workspace, view the /home/laradock/.composer/composer.json file, the package is missing.

Stacktrace & Additional info:
{paste here}

I'm so sorry ! It's my fault, didn't read the document carefully.


micro optimizations to speed up small networks

mostly replace CFloatHandle to float* inside CpuMathEngine implementation
leave some CFloatHandles unchanged forawhile in *Backwards and Algo1 related methods
Signed-off-by: Aleksandr Pakhomov<EMAIL_ADDRESS>

Let's write all public methods (affected by this PR) in the next way
CCpuMathEngine::PublicSuperMethod( firstHandle, secondHandle, resultHandle )
{
    /* ASSERT_EXPR's */

    /* additional allocations if needed */

    /*const*/ float* first/second/result = GetRaw(first/second/resultHandle);

    /*
    method implementation which doesn't use CMemoryHandle's at all
    */
}


added withMsg to History and created exec/hlearn-allknn-bench.hs

#56
I created a new executable (hlearn-allknn-bench.hs) rather than edit the original.
There's a few gotchas/fails with what I have so far:

I couldnt work out what to do with the disableMultithreading so I deleted it.
The new timings look like they're being reported 1 behind.  Don't know why but a simpler example would tease that bug out.
I tried to withMsg'ify the loadfile section, and change the allknn type sig to take a History, but I ran into an escaped scope.  Maybe the context stuff only works if you have exactly 1 use floating around.

Thanks for doing this!  I've just glanced through, and the big picture ideas look good.
It'll probably be a few days before I can look at this in more detail though.  If I haven't gotten back to you by next week, ping me again.


wdqs-frontend: build the UI

should fix the following tickets:

https://phabricator.wikimedia.org/T234041
https://phabricator.wikimedia.org/T191953
https://phabricator.wikimedia.org/T223068

This is a fairly big brekaing change for the way to image worked.
Would have been nice to have the tagged versions done before doing this, as if any users have any customizations to the image other than the basic things they will now be broken, and there is no tag to go back to.

For anyone that needs the prior version I looked it up and the following digest could be used:
latest: digest: sha256:9bc95c4678e1110a28ee9556598ccabcf0dbaa2be58dee2c59e8a2f71fae4b66 size: 1780
From https://travis-ci.org/wmde/wikibase-docker/jobs/590363979
Which is built from https://github.com/wmde/wikibase-docker/commit/e822265186acf18155bc1f42f7d73da15cc87536


Create video tutorial on how to use ZenHub

This can be closed once the video is in our Dropbox.

Please ignore this issue, I made a mistake while opening it.

(duplicate of #577)


checked whether the project name is valid.

Basically, added a check on whether the project name consists of only lowercase letters and underscores.
List which issues are fixed by this PR. You must list at least one issue.
Pre-launch Checklist

[x] I read the Contribute page and followed the process outlined there for submitting PRs.
[x] This update cointains only one single feature or bug fix and nothing else. (If you are submitting multiple fixes, please make multiple PRs.)
[x] I read and followed the Dart Style Guide and formatted the code with dart format.
[x] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///), and made sure that the documentation follows the same style as other Serverpod documentation. I checked spelling and grammar.
[ ] I added new tests to check the change I am making.
[ ] All existing and new tests are passing.
[ ] Any breaking changes are documented below.

If you need help, consider asking for advice on the discussion board.
Breaking changes
If you have done any breaking changes, make sure to outline them here, so that they can be included in the notes for the next release.

Have made a New PR regarding the REGEX.

@vlidholt Should I make a PR or should we wait?

@vlidholt Should I make a PR or should we wait?

Very Sorry for the delay.. Have been going through a lot.. Thanks to endSems.. Hope you understand.. will do it ASAP..

@Crazycoder122 Please close this in the favour of #499


[Feat]: There should be a form to fill out when clicked on "Add Profile"

What feature?
Overview:
Introducing an "Add Profile" form will allow users to easily create their developer profiles on the platform. This feature aims to streamline the profile creation process and encourage more users to showcase their skills and projects.
Features:

Add Profile Form:

Clicking on the "Add Profile" button will open a form where users can fill out their profile information.
The form will include fields for name, avatar, bio, skills, projects, and social links.
Users can upload an avatar image and provide a brief bio to introduce themselves.
Skills and projects fields will allow users to highlight their expertise and showcase their work.
Social links fields will enable users to connect their profiles with their external social media accounts.

Implementation Plan:

Frontend Development:

Design and create the "Add Profile" form using HTML, CSS, and JavaScript.
Ensure the form is user-friendly, visually appealing, and responsive across different devices.
Implement form validation to ensure that required fields are filled out correctly.

Backend Integration:

Create backend routes and controllers to handle form submission and profile creation.
Define database schema for storing profile information and integrate it with the backend.
Implement logic to process form data, validate inputs, and save profiles to the database.

User Experience Enhancements:

Add feedback messages to inform users about the status of their profile creation (success, error, etc.).
Provide clear instructions and tooltips to guide users through the form-filling process.
Optimize the form submission flow to minimize friction and maximize user engagement.

Benefits:

Simplified Profile Creation: The "Add Profile" form will streamline the process of creating developer profiles, making it easier and more accessible for users.
Increased User Participation: By lowering the barrier to entry for profile creation, more users are likely to contribute their profiles, enriching the platform's developer ecosystem.
Improved Platform Value: A diverse range of developer profiles will enhance the platform's value as a hub for talent discovery, collaboration, and networking.

Add screenshots
Add screenshots
Code of Conduct

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

I would Like to work on this under GSSOC'24

@haard18 I am have already closed the same issue previously, We don't want backend integration now. Maybe in future we will think of it.


Application is crashed when press toggleDevTools shortcut ['ctrl + f12']

VSCode Version: Code 1.11.2 (6eaebe3b9c70406d67c97779468c324a7a95db0e, 2017-04-13T08:03:11.395Z)
OS Version: Windows_NT ia32 6.1.7601
Extensions:

Extension
Author
Version

vscode-css-formatter
aeschli
0.0.2

mssql
ms-mssql
0.3.0

csharp
ms-vscode
1.8.1

debugger-for-chrome
msjsdiag
3.0.1

Steps to Reproduce:

Defined a shortcut for toggleDevTools, for example 'ctrl + f12'
{
    "key": "ctrl+f12",
    "command": "workbench.action.toggleDevTools"
}

Press the shortcut serveral times, the application is crashed.
Addtional
I haved defined other shortcuts('s', 'ctrl + b'), and the issue appears again.
Expected Result
The application can toggle dev tools correctly.
Actual Result
The application is crashed.

https://github.com/Microsoft/vscode/issues/4430


Expand environment variables in argumentfile

My request is to enable the expansion of environment variables inside of the argumentfile.
Background: when RF reads additional path-like arguments from an argumentfile, arguments like --pythonpath  or --output are hardcoded. There is currently no way to make them dynamic.
Writing this
--output $TESTBASEDIR/somefolder/output.xml

inside of an argumentfile would be awesome.
Thanks!

This would probably be pretty easy to implement using os.path.expandvars. As explained in its documentation, it works like this:

$name and ${name} formats are supported universally and on Windows also %name% works. This is convenient, because it's possible to use $ variants to create OS-agnostic argument files, but on Windows the native format works too.
Non-existing or malformed variables are left unchanged. This is good for backwards compatibility. Otherwise all current argument files containing $ characters would be broken, but with these semantics there are problems only if there are accidental matches to existing environment variables.

Some examples assuming that $HOME contains /usr/robot:
>>> os.path.expandvars('$HOME/path')
'/usr/robot/path'
>>> os.path.expandvars('$HOMER/path')
'$HOMER/path'
>>> os.path.expandvars('${HOME}R/path')
'/usr/robotR/path'

There are some design decisions to be solved still:

Do we need to care that they apparently is no way to escape variables so that they wouldn't be expanded? At least the docs didn't mention about that and with both r'\$HOME/path' and $$HOME/path the $HOME variable is replaced. If we needed to care about this, and there's no undocumented escaping functionality, we needed to implement something ourselves. That's likely a lot bigger task than this whole issue is otherwise.
Do we want to replace variables only in option values or should we do it everywhere? I was thinking the former would be better, but to my small surprise the shell replaces variables everywhere and, for example, if I set $x to version then robot --$x works fine. Based on that replacing variables everywhere would be fine and it certainly would simplify implementation even further.

One concern is that escaping seems not to be possible.

I also mentioned the lack of escaping in os.path.expandvars above. It's unlikely to cause issues often, but the problem is that there's no workaround if it causes them. For example, Bash supports escaping with \ and by using single quotes:
$ echo \$HOME
$HOME
$ echo '$HOME'
$HOME

We could pretty easily create our own expandvars variant that supports escaping (see e.g. answers to this StackOverflow question), but I don't think neither of the escape approach supported by Bash actually work for us for these reasons:

Supporting \ would require us to consider it an escape character also elsewhere. That would cause problems with existing backslashes, for example, in Windows paths.
Values in argument files shouldn't be quoted. For example, if you try to use --variable VAR:"Hello, world!" the value ends up being literally "Hello, world!", and if you use --variable "VAR:Hello, world!", you actually get variable ${"VAR} with value Hello, world!". Requiring quoting for escaping purposes would thus be inconsistent.

If we want to allow escaping, I believe we should support doubling $ so that $$HOME becomes $HOME. Also that would cause problems if someone currently has two or more subsequent dollar signs in their argument files, but that ought to be pretty rare. The logic would be somewhat strange because also a single $ would be preserved, unless it's followed by a name of an existing environment variable, but requiring all existing $s to be escaped would be quite badly backwards incompatible.

Hi @pekkaklarck , I'm interested in contributing to this issue, can you please assign me this task.

Thanks @kachida. Before implementing this, we need to agree on the design. Everything else ought to be pretty clear, but we need do decide what to do with escaping. This is very easy to implement using os.path.expandvars if the decision is that no escaping is needed. On the other hand, if we want to support escaping, there's much more work and the work starts by agreeing on the escaping syntax.
I doubt there are enough people following this issue tracker that would comment about escaping so we should probably ask also elsewhere. Are you @kachida interested to start with that? Our biggest user forum is Slack and there the #robotframework channel is probably the best place to ask about this.

Agreed @pekkaklarck 👍, I'm interested on this

Is anyone working on this. I would like to try  this. Can post on the #robotframework channel and see what the responses suggest?

Hey folks, I am looking forward to contribute , i have been using robot framework for the last couple of months and already forked the project . I think this issue is a good starting point for me before going further with other issues. i read the discussion and here’s my take on the environment variable expansion idea:

backward compatibility : I think that people who literally wrote $HOME in their argument files are probably pretty rare.. Still, to be safe, I'd say we can make expansion opt-in with something like a --expand-env-vars flag for example ? this way we dont break anyone’s existing setup ,, just in case if someone upgrade accidentally without being aware of this ...

escaping mechanism : using $$ to escape a literal dollar sign makes sense ... straightforward + well-known in other contexts ( shell etc .. )

tilde expansion : I also think expanding ~ to the user’s home directory would be super handy—just be sure to mention it clearly in the docs so nobody’s confused.

scope of expansion: that would be consistent to do it for all arguments ,also once and for all effort ?

questions for everyone:
are we okay with making this feature explicitly controlled by --expand-env-vars ? any other naming suggestions ?
any concerns about using $$ for escaping?
if this sounds good, can i start working on it since i have time this week , i will be able to deliver it in few days ?

Design decision from the following slack thread :

Expand variables for all flags.
Expand variables by default (no specific flag to activate this feature).
Use os.path.expandvars for expanding environment variables.
Handle escaping with Template.safe_substitute (fail gracefully without raising errors for missing variables).
No tilde expansion for now, at least.
Use robot.utils.NormalizedDict to normalize case on Windows while maintaining case sensitivity on Linux/macOS.


twttr.ready isn't always firing

Hey @arusahni
Its great work.
Somehow I experienced that twttr.ready is not firing when twitter widget js is already loaded before.
Because your code depends on twttr.ready, so if it isn't firing, whole this plugin stops working.
https://github.com/arusahni/ngtweet/blob/develop/src/twitterWidget.service.js#L37
So i think you need to check if its loaded already by $window.twttr.init == true first and if it isn't, add listener to twttr.ready.
i can submit PR if wanted

Hi @sujameslin - thanks for the bug report! That's the downside of being a third-party library - Twitter doesn't communicate these changes.  If you could file a PR, that'd be much appreciated.  Thanks again!

@arusahni
I think I might be hitting this bug as well, I am seeing a
TypeError: Cannot read property 'ready' of undefined     at Object.loadScript [as initialize] (http://localhost:8080/bower_components/ngtweet/dist/ngtweet.js:273:22)
When I try and add ngtweet to my project.
@sujameslin would your pull be the fix to this ?

Thanks for the submission, @sujameslin! I merged it in and cut a release. v0.6.2 should do the trick.
@GwilymNewton if v0.6.2 doesn't work for you, can you open a separate issue?


🐛 [BUG] - Windows Do not want to Download the App

Description
Sprint_0.9.19_x64_win.exe
Windows found this file suspicious. You need to add certification.
Reproduction URL
https://github.com/sprintrest/support/releases/tag/v0.9.19
Reproduction steps
1. Click on 'https://github.com/sprintrest/support/releases/download/v0.9.19/Sprint_0.9.19_x64_win.exe'
2. See "Windows do not want to download"

Expected not to see this pop-up

Screenshots
![DESCRIPTION](LINK.png)

Logs
No response
Browsers
Chrome
OS
Windows

@ilkan windows app is already signed with EV certificate


check for uploaded file before validation job is created

Overview
Please replace this line with full information about your pull request. Make sure that tests pass before publishing it

Please preserve this line to notify @amercader (lead of this repository)

Maybe we should remove the Adrià notification in the PR templates on our fork


[Feature] Unicode object support for Python code generator [sf#18]

Reported by zgoda on 2005-01-03 13:45 UTC
Would it be possible to add unicode object support to
Python code generators? Now wxGlade produces only
ordinal (encoded) strings, which are of no value if one
wants to put any national characters on labels,
captions et caetera. These strings choke interpreter
and cause encoding errors. Also, putting "coding
cookie" in this situation only helps to avoid
DeprecationError, but could be used to generate unicode
objects for output Python code.
Now, if one wants to use national characters, there's
few possibilies: one may use gettext or modify local
sitecustomize.py. One is easy (trick with
sitecustomize.py), one is elegant (gettext), but all
two have shortcomings. I think that allowing wxGlade to
generate unicode objects instead of encoded strings
would be welcome.

Commented by agriggio on 2005-01-14 14:28 UTC
Logged In: YES
user_id=375945
sounds like a sensible request...I'll add it to my todo, thanks.


Unable to attach a persistent volume in vsphere in-tree cluster's workload

on 2.5-head, commit eb160e0 and master-head commit fbe2c30
Rancher server docker version:  20.10.1

Created a in-tree cluster using rancher's node driver ( providing vsphere datacenter info as cloud provider)

cloud_provider:
  name: vsphere
  vsphereCloudProvider:
    global:
      insecure-flag: true
      soap-roundtrip-count: 0
    virtual_center:
      x.x.x.com:
        user: VCENTER_USER_NAME
        password: VCENTER_PASSWORD
        port: 443
        datacenters: vCenter Name
    workspace:
      server: x.x.x.com
      folder: /XXX/vm/
      default-datastore: /XX/datastorename
      datacenter: xxx
      resourcepool-path: /x/x/x1/Resources/RESOURCE_POOL

Created a storage class type "VMware vSphere"

During creating a workload of type deployment, choose "add volume" --> "Add a new persistent volume(claim) and chose the storage class created on step 2

The container creation is in a hang state since it couldn't attach the pv with the workload

Rancher UI is showing a pv is been created with the following vmkd id

Checked on the vCenter for the pv's  vmdk in kubevol and seeing the vmkd is there but the size is zero

Repeated the tests on 2.5.6-rc4 and master-head the same issue, pv attachment is failing.
Additional info that can be helpful, when tried the same test on v2.5.5, the workload deployment attaching a pv with it was successful.
I have the setup can complete logs available for debugging.

The error is due to invalid datastore path. Nothing changed between these two versions with respect to the in-tree provider. And the changes for out-of-tree only apply if the chart is launched. So I think the input needs to be checked again

@sadiapoddar Yes, can you please re-try and let me know what happens. I'm surprised this is blocking out of tree cloud provider testing as this has nothing to do with in-tree.

Check the datastore path,  there was no error in input for the datastore path, the same datastore was used on v2.5.5 and it worked.
On v2.5.5 the k8s version is v1.19.7 and retried the same test on 2.5-head, commit  eb160e06
The same test with k8s 1.19.7, workload creation with a persistent volume attached worked without any issue.
Looks like the issue with k8s version, on 2.5-head, commit eb160e06 the default version is v1.20.2
Hi Denise, why I marked it blocker since all our in-tree to out-tree migration tests require that cluster needs to have at least a workload with a persistent volume attached to the workload. From in-tree to out-tree migration we are testing CPI and CSI drivers migration, we can't test CSI  migration if there is no PV attached workload in the migration process.

This could be related to this change which was introduced in 1.20 line

@dramich Can you file an issue with k8s as it looks like it's a k8s 1.20 issu with the vsphere in tree cloud provider.
We will release note this: @Jono-SUSE-Rancher and this isn't a blocker for the release.
Note: for anyone who finds this, Rancher supports the out of tree vsphere cloud provider starting as of v2.5.6 which is when k8s 1.20 support was introduced.

Since we now support out-of-tree provider, do we still need this ticket/fix @deniseschannon ?

Yes, even though vSphere doesn't recommend the in-tree, we should still note when this gets fixed. Did @dramich open an upstream issue?

This is actually a docs/configuration bug and no upstream issue is needed.

rancher/rancher:v2.5-head 67228a3
The problem here was not following the cloud provider format specified by the in-tree cloud provider docs. Using the format from the cloud provider docs (https://vmware.github.io/vsphere-storage-for-kubernetes/documentation/existing.html#template-config-file) which does not include the full path to the datastore allows the user to provision the volume successfully:
cloud_provider:
    name: vsphere
    vsphereCloudProvider:
      global:
        insecure-flag: true
      virtual_center:
        my.virtualcenter.com:
          user: user
          password: supersecret
          port: 443
          datacenters: datacenter
      workspace:
        server: my.virtualcenter.com
        folder: /
        default-datastore: datastore
        datacenter: datacenter
        resourcepool-path: resourcepool

I also tested a scenario where I created a cluster using the previously used format and saw it fail to provision the volume, then updated the cluster's cloud provider to the format specified above and was then able to see the volume provision successfully.
Our docs however, specify using the full path to the datastore: https://rancher.com/docs/rke/latest/en/config-options/cloud-providers/vsphere/config-reference/
I've logged an issue to update the docs here: https://github.com/rancher/docs/issues/3071

rancher/rancher:v2.5-head 51253e5
Confirmed again that for k8s 1.20, the format specified in my previous comment is required for the volume to provision successfully.
We will check that this also works on master-head, and then close this issue after the docs have been updated.

Verified the issue on master-933b15908af72f751ffe9ab722da7e23c629fb4d-head
k8s: v1.20.4-rancher1-2

Created a vsphere cluster with in-tree enabled and only datastore name provided without giving the full path
Created a storage class on vsphere cloud
Deploy a workload by selecting the storage class created in the above step
Deployment goes through without any error

^^^ Closing this issue as the document updating is being tracked separately


Support Python 3

It is now safe and preferred to write code for Python 3 as Python 2 is reaching the end of its extended life. There is no need to support Python 2 anymore in libraries like these.

Done! Thanks!


Can't get it running on Fedora 25

I'm trying to run it on Fedora 25 and getting the following error:
 ~/code/vagrant-swift-all-in-one [17-04-21 11:32:10] [master]
 % vagrant up
Bringing machine 'default' up with 'libvirt' provider...
==> default: Box 'xenial' could not be found. Attempting to find and install...
    default: Box Provider: libvirt
    default: Box Version: >= 0
==> default: Box file was not detected as metadata. Adding it directly...
==> default: Adding box 'xenial' (v0) for provider: libvirt
    default: Downloading: http://cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-vagrant.box
The box you attempted to add doesn't match the provider you specified.

Provider expected: libvirt
Provider of box: virtualbox

I tried to install vagrant-libvirt package, but it didn't help. What's wrong there?

Fixed it with:
dnf install akmod-VirtualBox kernel-devel-4.10.10-200.fc25.x86_64
akmods --kernels 4.10.10-200.fc25.x86_64 && systemctl restart systemd-modules-load.service

I got these commands by running VBoxManage --version.
Then you have to start vagrant this way:
% VAGRANT_DEFAULT_PROVIDER=virtualbox vg up


Add unread messages count in chat list

Adding the number of unread messages per chat list will help the user to quickly identify the unread chats rather than clicking on each of the chats and checking for those messages

assign this to me!

assign this to me!


JS console error:  Uncaught TypeError: Cannot read property 'tooltip' of undefined

Open the browser
Open the developer console
Open appliance's ip
Log in
A couple of errors in the console appear:

Haven't seen that recently


Update Kubernetes version to 1.19.9

Update default Kubernetes version to 1.19.9 to align with the default
in the IBM Cloud which was changed to 1.19.9
Signed-off-by: Chin Huang<EMAIL_ADDRESS>

can you also update the README? currently, I put two README with the same content, one is under repo root and the other is under terraform directory. I think you only need to update the one under terraform directory. Thinking about change the one in repo root to some general information later.

Sure, forgot README earlier.


which version of tf in your env?

my env is tf 1.0.0, and with so much variable sharing problems,
i change the code with variable scope, but it still can't work...
Error Info looks like:
ValueError: Variable lstm/basic_lstm_cell/weights already exists? ....
Otherwise,
tf.get_variable_scope().reuse_variables() lies in Line 78 of solver.py, it change the whole variable scope to reuse status, is that what you desire?
Thks!

I recommend using TensorFlow 0.11 version to run this project's code. I will upgrade the version of the code layer, but not sooner.


chore: drop python 3.6 supports

chore: update README
Signed-off-by: Aaron Pham<EMAIL_ADDRESS>

#19 We can keep the py36 support because of this


Add missing share messages

Whoops 🤦♂

Codecov Report

Merging #12 into master will not change coverage.
The diff coverage is n/a.

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

I am so sorry I missed this ! I only saw your message now

No problem @SaraVieira, just hope the issue didn't affect any users 😅


Possible bug due to order of width and id

Given this minimal example:
extern crate cursive;

use cursive::Cursive;
use cursive::views::*;
use cursive::traits::{Boxable,Identifiable};

fn main() {
    let mut cur = Cursive::new();

    cur.add_layer(LinearLayout::horizontal()
        .child(Dialog::around(LinearLayout::vertical()
            .child(Checkbox::new().on_change(|cur, val| {
                cur.call_on_id("v1", |cb: &mut EditView| cb.set_enabled(!val));
            }))
            .child(EditView::new().content("0").with_id("v1").fixed_width(5))))
        .child(Dialog::around(LinearLayout::vertical()
            .child(Checkbox::new().on_change(|cur, val| {
                cur.call_on_id("v2", |cb: &mut EditView| cb.set_enabled(!val));
            }))
            .child(EditView::new().content("0").fixed_width(5).with_id("v2"))))
    );
    cur.run();
}

V1 works, v2 not and the only difference here is the order on which fixed_width and with_id are provided. I'm not sure what leads to this bug, but I think it should be fixed :)

Ah yes, I think this point needs more documentation.
The problem is caused by the way these methods work: with_id and fixed_width actually wrap the view (respectively in an IdView and a BoxView).
This means the type of EditView::new().fixed_width(5) is not EditView, but BoxView<EditView>. So when you write EditView::new().fixed_width(5).with_id("v2"), the view you can access through the "v2" ID is this BoxView<EditView>, not the inner EditView.
The 3rd tutorial tries to address this:
let select = SelectView::<String>::new()
    .on_submit(on_submit)
    .with_id("select")
    .fixed_size((10, 5));

(Here again, the order is important: we want to wrap the SelectView, not the BoxView. But we still need to call on_submit before that.)

The general idea to order these methods is:

First, use all methods native to the given view; they usually return the view itself, so within this group, the order doesn't matter.
Then, with_id: when looking up an ID, you want the inner view, not any other wrapper.
Then, other wrappers, like fixed_width.


Launch button in status bar not launching the selected target

Type: Bug
Hello,
since a month, we are neither able to launch the "Selected target" from the launch button (CMake) in the status bar of VS Code, nor from the CMake project outline sidebar, when we click "Run in terminal" from the context menu of the designated executable target. VS Code just triggers the build but no execution is followed.
Our codebase is stored on a high performance cluster (Linux) to which we connect using the standard Remote-SSH connection. We are still able to execute the binary by using the terminal and going to CMakes build directory.
If you need any more information (regarding our configuration, especially our CMakeLists.txt) please contact me.  Is there a sample project you could share with us that encounters this issue?

Hi @ruben-fuerst, I'm going to go ahead and close this issue since I cannot reproduce it. Please try the latest pre-release and see if it is fixed. If you encounter this issue again, please open a new issue, thanks!


DOC: cell blocks for installs

Can't say i've built the docs but the current page is missing some cell blocks
https://filesystem-spec.readthedocs.io/en/latest/index.html

(failures I hope will be fixed in #534 )


the normalization of OOD test datasets

Hello, I have encountered an issue regarding the normalization of OOD test datasets. As per my understanding, during the evaluation of OOD datasets, it is necessary to perform normalization specific to each OOD test dataset. Taking CIFAR-100 as an example, where can I find the mean and standard deviation for the normalization of various OOD datasets? Thank you

for example， the mean and std for svhn\tin\texture\places365....

Actually one should NOT "perform normalization specific to each OOD test dataset". By doing so you are assuming that you know which dataset the input is from in the first place, which makes OOD detection meaningless (you already know whether the input is OOD or ID).
Therefore we just use the normalization parameters corresponding to each ID dataset, which we believe is reasonable and also practical. You can find the parameters here:
https://github.com/Jingkang50/OpenOOD/blob/555d879be07d977f6ccf091b559afd64b37fc6f2/openood/preprocessors/transform.py#L3-L12

Thank you for your prompt reply！
Can I understand it this way: if I use CIFAR-100 as the ID dataset, then when conducting out-of-distribution detection on various OOD datasets, all OOD datasets should be normalized using the same normalization parameters as CIFAR-100?

Or OOD test datasets do not need to be normalized to maintain the differences in their distributions?

if I use CIFAR-100 as the ID dataset, then when conducting out-of-distribution detection on various OOD datasets, all OOD datasets should be normalized using the same normalization parameters as CIFAR-100

Correct. You can also imagine that in practice, a deployed image classifier typically uses a fixed set of preprocessing operations.

thanks sooo much！


.orElse() #909 part 1

Future
Lazy
Option
Validation

@danieldietrich please review Future

Current coverage is 95.09%

Merging #1049 into master will increase coverage by +0.01% as of c312c6d

@@            master   #1049   diff @@
======================================
  Files           75      75
  Stmts         9418    9446    +28
  Branches      1729    1737     +8
  Methods          0       0
======================================
+ Hit           8955    8983    +28
  Partial        112     112
  Missed         351     351

Review entire Coverage Diff as of c312c6d

Powered by Codecov. Updated on successful CI builds.

Well done, thank you Ruslan!


ARM binaries?

Would be nice to provide ARM binaries for devices like the Raspberry Pi 2 & Raspberry Pi Model B+. I had to install Golang on B+ just to go get the binary. (Great job btw @moncho with dry)

Thanks :) feel like trying? It would be the first PR ever on this repo ;)
Changes should be done in the Makefile.
To test: make release, then check that binaries for ARM are also built.

@moncho Made a PR #7

Thanks a lot, next release will include an ARM binary


[ISSUE]active healthcheck with type:https got the issue: unable to get local issuer certificate, context: ngx.timer

Summary
kong version 1.4.0
By some reason, we need to support ssl endpoint as targets, for the active healthcheck, we configured available items:
proper path\sni
type as https,
verify https certificate as true
while its all set, we got the below issue:
2020/02/21 09:47:50 [error] 9027#0: *46232650 [lua] healthcheck.lua:1025: log(): [healthcheck] (healthcheck-mine) failed SSL handshake with ' (:443)': 20: unable to get local issuer certificate, context: ngx.timer
Steps To Reproduce
base above configuration, interval checked by kong admin, we can get the issue.
Additional Details & Logs
kong error log:
2020/02/21 09:47:50 [error] 9027#0: *46232650 [lua] healthcheck.lua:1025: log(): [healthcheck] (healthcheck-mine) failed SSL handshake with ' (:443)': 20: unable to get local issuer certificate, context: ngx.timer

not sure if I got the reason, I checked the code
/kong/runloop/balancer.lua
and the module resty.healthcheck, with debugging, I found that:
if we set the active healthcheck as https, setting the sni, but when do the real healthchecking, the specified sni does not pass correctly, still use the ip, consider the situation that:
when the targets for service request forwarding, the sni would be specified by route/service, but the healthcheck is not, so we have no simple way to bind a host.hostname for each target address,
currently I tried a workaround(changed the file balancer.lua): while process the healthcheck with https and sni specified, pass the sni correctly to resty.healthcheck module by method add_target(refer line 199 and line 268, line number more or less) and while alter the status, remove the real healthcheck sni to avoid the not match issue
ok, err = balancer:setAddressStatus(status, tgt.ip, tgt.port, hostname)  change to
ok, err = balancer:setAddressStatus(status, tgt.ip, tgt.port, tgt.ip)

balancer.lua.zip
the related file be chagned.
our kong version is the kong 1.4.0.

Hi @mnteam, could you confirm if the issue still exists on the latest version? we will close this issue if there is a lack of activity.

Hi, you can close the issue, we fixed it, it should be the configuration issue in our env. Thanks.
发自我的iPhone

在 2022年11月30日，12:16，Mayo @.***> 写道：

Hi @mnteam, could you confirm if the issue still exists on the latest version? we will close this issue if there is a lack of activity.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were mentioned.

@mnteam Thank you!


First PR to trigger sonar

Creating this PR to check the sonarqube analysis using github workflows.

Metric
Value

alert_status
OK

bugs
0

code_smells
1

reliability_rating
1.0

security_rating
1.0

vulnerabilities
0

Metric
Value

alert_status
OK

bugs
0

code_smells
1

reliability_rating
1.0

security_rating
1.0

vulnerabilities
0


Multiple Charts Will Grow but Not Shrink In A Grid

Version
4.8.0
Reproduction link
https://jsfiddle.net/8hngc24b/49/
Steps to reproduce
-Create a grid layout consuming 100% width and height with two columns.
-Please a chart (ex. Pie) in both columns.
-Tie windows.resize event to a function that resizes the charts.
-Make browser window larger in height.
-Note that charts grow.
-Make browser window smaller in height.
-Note that charts do not shring.
-Make browser window smaller in width.
-Note that charts shrink.
What is expected?
Charts shrink when resized as part of the browser window being reduced.
What is actually happening?
The charts are not shrinking creating overflow.

This only occurs when multiple charts are on the same grid row.  Here's the same example with a single chart and it works fine: https://jsfiddle.net/8hngc24b/46/.
My guess is that there's some kind of race condition here because the resizing is happening serially: the grid's row can't shrink because the second graph hasn't resized yet and so it redraws with the same height.
There's a few other issues that sound similar.  Here's one talking about using Flex (which I'm not doing) and where one of the comments suggest calling resize on each chart (which I am doing).

It seems to do with the grid layout. When the height of the chart grows and calls resize function, ECharts cannot calculate a new correct height. But I think there may be no need to use a single chart because it works well if not using display: grid.
For example, use the common default layout display: block.
.container {
  height: 100%;
  margin-left: 1rem;
  margin-right: 1rem;
  font-size: 0;
}

.chart {
  width: 50%;
  height: 100%;
  float: left;
  /* left: 0;
    top: 0; */
  position: relative;
}

Thanks for the reply @plainheart.  What's weird is that they work for a single chart, they work when charts grows, just not when there's multiple and it shrinks.
A non-grid layout does work but then you loose the power that Grid provides.  In our case we are replicating some WPF charting and in a couple of cases the user can dynamically select what charts to display.  So Grid's ability to handle dynamic content in a dynamic view port is super awesome.
My guess is that this is related to #11791 which is a similar problem with Flex layouts.

I also had the same problem, and finally I solved it by manually specifying the width and height with calc, It works.
But I think this loses a big advantage of grid layout.

@anguiao Yea that works but at that point you're not really using grid.  I've had some small amount of success by putting each chart in it's own grid by itself but that only seems to work horizontally.  If I stack charts in two dimensions (ex. a 2x2 grid) then I'm right back at the same problem.

@bryandam @anguiao
Hi, I now think the reason why ECharts cannot calculate a correct height after the height of the window decreases is that the previous height value has been set on the root DOM of ECharts instance but not the default 'auto'(the specified value will affect the height of its parent DOM).
So I suppose we should hide the DOM first before resizing and then restore the visibility after the chart resizes.
This way can probably resolve this issue.
Take a try with this demo: https://codepen.io/plainheart/pen/VwKPzpj

@plainheart Thanks, I just tested it and it works.
But getZr() does not seem to be a public API, it is not mentioned in the ECharts documentation.

@anguiao Yes, getZr is never documented in ECharts documentation but this API is often used. It's from zrender, which is the core base library of ECharts. But note that the documentation of zrender is written in Chinese now.

Try this demo https://codepen.io/librajt/pen/XWEJeVj ( forked from @plainheart )
In the demo, I wrap the chart el with the grid items, and set them position: absolute,
then call resize() directly :)

Thanks @librajt that was a lifesaver.

I think this is related to this:
https://stackoverflow.com/questions/77661631/having-an-echart-on-the-front-and-back-of-a-flip-card-breaks-resizing

Try this demo https://codepen.io/librajt/pen/XWEJeVj ( forked from @plainheart ) In the demo, I wrap the chart el with the grid items, and set them position: absolute, then call resize() directly, charts resize well :)

완벽히 작동합니다. 감사합니다.

Try this demo https://codepen.io/librajt/pen/XWEJeVj ( forked from @plainheart ) In the demo, I wrap the chart el with the grid items, and set them position: absolute, then call resize() directly, charts resize well :)

Thank you!
For my situtation it was much simpler. All I have to fo was wrap the chart in a div with grid display. Then put autoresize on the chart itself. Finally worked!


Confusion of documentation

In the first example, for Configure pipeline resource triggers, the pipeline name and reference has me confused.
The lines above the yaml code reference the pipeline for the snippet as app-ci, and the pipeline it triggers off of as security-lib-ci. The code snipped seems to say that securitylib is the name of the pipeline that yaml is defining. So is app-ci = securitylib? Can the description be adjusted to clarify, or the example be adjusted to better define the names to understand the example better?
Thanks

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 86285f72-9e28-da97-59bb-c29eb60f627d
Version Independent ID: 18d5a591-a7d3-c261-6bff-8808ae433f54
Content: Configure pipeline triggers - Azure Pipelines
Content Source: docs/pipelines/process/pipeline-triggers.md
Product: devops
Technology: devops-cicd-process
GitHub Login: @steved0x
Microsoft Alias: sdanie

investigating


Elasticache Cluster URLs Don't Appear to Be Correct

Version
7.10.1
Steps and/or minimal code example to reproduce
Create some elasticache monitoring instances or just do the following:
import { Stack } from "aws-cdk-lib";
import {
  AwsConsoleUrlFactory,
  ElastiCacheClusterType,
} from "cdk-monitoring-constructs";

const stack = new Stack();

const f = new AwsConsoleUrlFactory({
  awsAccountId: "123",
  awsAccountRegion: "us-east-1",
});

let r = f.getElastiCacheClusterUrl("c1", ElastiCacheClusterType.REDIS);
let m = f.getElastiCacheClusterUrl("c2", ElastiCacheClusterType.MEMCACHED);

console.log({ redis: stack.resolve(r), memcached: stack.resolve(m) });

Expected behavior
The urls should look like:
https://us-east-1.console.aws.amazon.com/elasticache/home?region=us-east-1#/redis/c1
https://us-east-1.console.aws.amazon.com/elasticache/home?region=us-east-1#/memcached/c2
Even if the clusters don't exist you can tell that the form of the URL is correct - the fields on the page will just be missing.
Actual behavior
You'll get URLs of the form:
https://us-east-1.console.aws.amazon.com/elasticache/home?region=us-east-1#redis-shards:redis-id=c1
https://us-east-1.console.aws.amazon.com/elasticache/home?region=us-east-1#memcached-nodes:id=c2;nodes
Which don't work - they'll bounce you to the elasticache landing page.
Other details
I'm not sure the console URLs are documented anywhere, so it's possible that this is different for different accounts or elasticache setups.

As a side-note, making clusterUrl read-only exacerbates this, as the user has to create a subclass and override createTitleWidget in order to fix, rather than just setting the correct url on the instance.
https://github.com/cdklabs/cdk-monitoring-constructs/blob/d1fda6fd7ea7ae2e07d9ae847273794474f9b36f/lib/monitoring/aws-elasticache/ElastiCacheClusterMonitoring.ts#L93
Any reason it's read-only?


Fix newline parsing in MD to HTML parser

@Jag96  will you please review this?
[Explanation of the change or anything fishy that is going on]
If a br tag is followed by a newline then we should parse both as single newline. e.g.
 <b>Joe likes to eat <b><br>\n Apple & Doughnut.
Fixed Issues
$ https://github.com/Expensify/Expensify.cash/pull/4009#issuecomment-879534328
Tests

What unit/integration tests cover your change? What autoQA tests cover your change?
UNit
What tests did you perform that validates your changed worked?
Unit

QA

What does QA need to do to validate your changes?
NA
What areas to they need to test for regressions?
NA

Done


[BUG] Width gets messed up with Minimal UI module

tested it, works fine with minimal UI turned off, but it'd be nice if I could have Minimal UI on without the bar going under the collapsed right sidebar

i'm afraid i cannot account for every module that changes core CSS, that said it's possible that with the changes that will be required with v9 this issue will be fixed then (since in core v9 this same issue happens)


Front USB port is USB 2.0 only

The front USB port is only mapped for USB 2.0, the one nearest the rj45 port works with 2 and 3 devices.
This is in the latest version/1.2.2
Disabling the usbmap kext resolves the issue.

Use hackintool for USB customization, replace USBMap.kext with USBPort.kext, all USB ports are normal


Pathfinding Improvements

Fixed issues with pathfinding which causes mobs to walk into walls and get stuck. Seems to be working a lot better now with the A* and theta pathfinding at least (I've not touched the neighbors or obstacle_avoidance methods).
Pathfinding Improvements
mob_meta.get_node_height:
Moved to pathfinding, and made public (creatura.get_node_height).
Now uses collision box rather than node box, if available, unless flag specifies not to.
Fix for getting node height for nodes with connected node boxes
pathfinding.get_ground_level:
We now have one copy between pathfinding and mob_meta.
Can check a larger range of nodes at different heights.
Takes into account node height of both target node, and the height of the node we're coming from.
pathfinding.get_neighbors:
Get maximum distance mob can travel up/down from mob stepheight.
Improved checking diagonals are clear.
Improved checking vertical clearance, takes into account height of current and target node.
Vertical clearance can cope with nodes that have a different collision and node boxes, like snow.
Vertical clearance has a tiny height adjustment so a 2 node heigh entity can fit through a 2 node gap.
Fixed bug where it was assumed a node was reachable if it's the end goal.
methods.movement_theta_pathfind and movement_pathfind:
Fixed bug that raised goal pos by 0.5 nodes.
Movement Improvements
Pathfinding movement functions for A* and theta have been combined into one generic function.
Ensure next goal is always set if there is a valid path.
Checking if mob has reached the next goal improved - now works no matter the mob height, and the height of the node below the goal.
Mobs now won't overshoot their goal, if they're very close to it (less than mob width) their speed reduces.
The more a mob is turning, the less forward velocity it has. This should fix spinning a lot.
mob:pos_in_box now can take a size param that is a table, containing the separate width and height.
pathfinding.moveable no longer pads an extra 0.2 around the width of mob when checking if there is sufficient space for the mob.
pathfinding.get_neighbors now uses max_fall for the maximum distance we can go down, instead of stepheight.

Did some testing and found that it breaks mob following behavior in Animalia. Spawn in some cows and hold wheat, they just walk in somewhat of a circle. Pretty sure this has to do with the changes to pathfinding movement methods.

Fixed, the vertical check on the pos_in_box should be correct now, no matter the node its standing on too.
Also the movement should be better in general, at least less susceptible to spinning. The more the mob has to turn, the less forward velocity it has. If it has to turn at full turning speed, the forward velocity drops to zero. This means it won't circle the position it's aiming for.

First issue I've found is that pathfinding.moveable padding by 0.2 isn't a bug. It does so because of an issue with indexing positions without the padding. Sorry for not getting to this sooner btw, been busy with some visual assets.

I can add it back in, but would you mind explaining what you mean by indexing positions and the issue without the padding?

Best explained through screenshots.
The particle represent the indexed positions of a Dragons hitbox with the + 0.2 padding

and this is without the padding.

I have no idea why this happens, but not having the padding is definitely a potential issue for bigger mobs.

Is this to do with index_box_border in mob_meta.lua?

Nope, index_box_border just grabs each node around the based of a mobs collisionbox but doesn't modify anything. I encountered this same issue with mobkit as well, so I don't think any lua-side tampering is to blame.

Odd, as far as I can see, pathfinder.moveable is only used in pathfinder.get_neighbors.

It is, but it's very important because it checks if the mobs entire collisionbox can fit at each neighboring position.

I'll add it back, also found an issue with dragons pathfinding around snow, will fix that too.

I've increased the mob's collision box vertically when we're checking if the next pathfinding goal is inside the box, this helps dragons. The fire dragon seems to have trouble pathfinding around its own fire, although that seems to be an existing issue (shouldn't fire be seen as non-walkable?).


No module named 'g4f'

Tried doing pip install g4f although no difference upon startup

Then you're probably using the wrong interpreter to execute the script, try using python instead of python3 when installing, so:
python -m pip install -U g4f

Thanks fixed that ,although upon fixing it it now returns this error when creating a video

This is probably because you supplied the wrong ImageMagick Path, it should point to the .exe file called magick.exe, also make sure to use double back slash on windows.
See one of the closed issues talking about this error

Sorry but where do i insert the path?

Bro did you read the instructions 💀
Copy contents from .env.example to .env, and fill out the values.

Did that solve your problem?


Sometimes the wrong IP address shows up in the terminal output

In the module aaNetwork.cpp in the routine cfgToConsole() the display of the robot IP address is sometime incorrect. Specific use case was the address being assigned to Doug's robot on Andrew's network, <IP_ADDRESS> was displayed as <IP_ADDRESS>. We put in a debug line that help ed uncover this issue an the code that actually worked was WiFi.localIP().toString(); This can be displayed with far less work and is correct. The code _convert.ipToString(WiFi.localIP().cStr());

The issue just popped up on the Andrew robot. Here is what led to this:

I closed the current terminal connected to a working ESP32
started a new terminal session
I rebooted the ESP32
The trace output from the ESP32 showed up without needing to rebuild/upload the code
I then saw not only the wrong IP address, but the same incorrect IP address as we saw on Doug's robot.
I then rebuilt/posted to the ESP32
The output returned to normal

From this experience we can conclude that the value of the IP address is not relevant to the bug. It must be some other subtle thing. We seem to have a good workaround (see last note on this issue) and may never know the root cause of the bug.

It seems that WiFi.localIP() is provided as a string, and no conversion is needed.

Would be  great to reduce the complexity of the code as you have discovered is possible. The MAC address of the ESP32 that you loaned e is 94B97E5F52DC.  Also,  while you are in  there messing around you should change the prefix of the robot name from Hexbot to HexaFloorRide.  For example, in MQTT my robot current registers as Hexbot94B97E5F52DC but he really should call himself HexaFloorRide94B97E5F52DC.

I'm about to wrap up this issue, following your suggestions. A few philosophical thoughts first:

we're using the ESP32 MAC address to identify the robot chassis, for example to identify soft servo offsets.
if we swap ESP32's that falls apart
it would be nice to have a real chassis ID, which could be:
- some DIP switches
- a 4 bit rotary switch
- an I2C readable value, maybe something in PCA9685?
as we already discussed, using NV RAM in ESP32 for MQTT Broker IP address has similar problems

could scan through a list of possible broker IPs, but that doesn't work in new demo environment
could use a symbolic name, and look it up in DNS, if DHCP can supply a DNS service pointer
might be able to do a MAC level broadcast, that invites Broker to connect and identify itself
might also be able to do that at IP layer, maybe more easily

OK, into the code.

We could adopt an idea that will take work and time but is possible. We can put unique serial numbers on each chassis. When the robot looks at this memory and it is not set it could use the current MAC address scheme. And issue a please set my serial number value message to the MQTT broker. If the serial dumber is set then use that instead of the old scheme. To be really ambitious, down the road if we add vision the robot could scan its own serial number and set its name for itself. Well worth discussing further I think.
On Tue, Dec 20, 2022 at 6:56 PM, Doug Elliott VA3DAE @.***> wrote:

I'm about to wrap up this issue, following your suggestions. A few philosophical thoughts first:

we're using the ESP32 MAC address to identify the robot chassis, for example to identify soft servo offsets.

if we swap ESP32's that falls apart

it would be nice to have a real chassis ID, which could be:

some DIP switches

a 4 bit rotary switch

an I2C readable value, maybe something in PCA9685?

as we already discussed, using NV RAM in ESP32 for MQTT Broker IP address has similar problems

could scan through a list of possible broker IPs, but that doesn't work in new demo environment

could use a symbolic name, and look it up in DNS, if DHCP can supply a DNS service pointer

might be able to do a MAC level broadcast, that invites Broker to connect and identify itself

might also be able to do that at IP layer, maybe more easily

OK, into the code.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

After re-reading your comment and mine here is a basic question to resolve. What is the essence of the robot identity?

Your suggestion implies that the PCB (circuit or brain) is the answer.
My suggestion implies that the chassis (the body) is the answer.

Either way can work. I guess we have to do some robot philosophy to decide which way we want to go. Truly this hobby copies every area of the sciences!

I think this naming scheme is really a new topic. I have created issue #53 to track the idea of a new naming scheme for the robot. Let’s keep this ticket focused on fixing the software bug that causes the wrong IP address to be displayed. This will ensure that each issue only tracks one item and can be closed. Nothing worse then an issue that needs to stick around forever and has to be renamed as the topic shifts. Over time this approach tens to make it hard to find old tickets I think.


Stage variable

Is there a way to set stage variable during an create or deploy?

Unfortunately, the API importer doesn't have ability to create/set stage variable.

So the best solution here is to do a create or update without a deploy and creating the stage via the CLI tools?
BTW, would be a nice +1 to include it as a feature

To clarify create or update the stage variables, it means assigning the values to stage variables. The stage variables placeholder can be set in a part of swagger document. Changing the stage variables placeholder is required an API deployment.
In order to assign the values to stage variables, you have to create a stage or point the deployment to an existing stage.
There are multiple ways you can assign the values to the stage variables.
For the easiest way to assign the values to a stage, you can do it from API Gateway console.
If you want to automate the process, you can use API Gateway SDK to do so.

Swagger/OpenAPI import is now generally available in the API Gateway REST API, the AWS CLI and all AWS SDKs. You can also import and export Swagger definitions using the API Gateway console. This release addresses many of the open issues and feedback in this repository.
I would encourage you to migrate your workflow to the standard AWS tools. aws-apigateway-importer will receive minimal support from the API Gateway team going forward.
Any feedback or issues with the new importer should be directed to the official API Gateway forums.
Thanks,
Ryan


[HW]

Name: Jeemish Modi
Email<EMAIL_ADDRESS>Linkedin Profile: <https://www.linkedin.com/in/jeemishmodi/

Attach the homework screenshots below for both step II and step III:

https://api.badgr.io/public/assertions/XZIV2iC2S6yjXLlzmH91XQ?identity__email=jeemishmodi%40gmail.com Well done!


Split WND into onshore and offshore

This issue can be closed when the JPN model has separate processes for onshore and offshore solar power, with distinct LCoE, CO2 emission coefficients and available capacity projections.

Can you add more details in the issue definition? (e.g. How will one know when this issue can be closed?)

Feature added to 201808 input files.


Unable to build Rider Plugin with 1.0

I'm currently trying to migrate a Rider Plugin of mine from 0.7.3 to 1.0. There is an issue that started to appear when I tried to build the plugin. Some variant of
2021-06-05 12:52:11,152 [   2644]  ERROR - ntellij.idea.ApplicationLoader - Cannot run program "/home/runner/.gradle/caches/modules-2/files-2.1/com.jetbrains.intellij.rider/riderRD/2021.1.3/9afc70d25c6c7730b23aa954766cdaf1460bf480/riderRD-2021.1.3/lib/ReSharperHost/linux-x64/dotnet/dotnet": error=13, Permission denied
java.io.IOException: Cannot run program "/home/runner/.gradle/caches/modules-2/files-2.1/com.jetbrains.intellij.rider/riderRD/2021.1.3/9afc70d25c6c7730b23aa954766cdaf1460bf480/riderRD-2021.1.3/lib/ReSharperHost/linux-x64/dotnet/dotnet": error=13, Permission denied

Shows up in the log, and it fails during buildSearchableOptions. When I run chmod +x /home/runner/.gradle/caches/modules-2/files-2.1/com.jetbrains.intellij.rider/riderRD/2021.1.3/9afc70d25c6c7730b23aa954766cdaf1460bf480/riderRD-2021.1.3/lib/ReSharperHost/linux-x64/dotnet/dotnet": error=13, Permission denied  java.io.IOException: Cannot run program "/home/runner/.gradle/caches/modules-2/files-2.1/com.jetbrains.intellij.rider/riderRD/2021.1.3/9afc70d25c6c7730b23aa954766cdaf1460bf480/riderRD-2021.1.3/lib/ReSharperHost/linux-x64/dotnet/dotnet the next time I run the build, it passes. Here is the suspect build and pr
I didn't know where to put this. This didn't happen in a previous pr, however I don't know if I should have put this in youtrack under issues with rider, or if it belongs here. Any clarity/insights are welcome!

Thanks for reporting, Alex!
That's a known issue with extracting mechanism of the SDK artifact – no permissions are preserved, so if you try to run any binaries provided with the SDK, it'll fail.
The issue is already fixed – check #681 for more details.


Update dependencies and refactor gradle

All modules (excepting examples modules, if this PR is merged, I will create another PR to update examples modules 😁):

applyDefaultHierarchyTemplate.
remove deprecated targets.
use JDK 17 as jvmToolchain, but 11 as JVM target and sourceCompatibility (for Android)
simplify ksp config.
add -Xexpect-actual-classes flag

Android modules: change Compile SDK and Target SDK to 34.

Update dependencies:

gradle wrapper 8.6.
AndroidX deps to latest stable version.
Kotlin 1.9.22 along with ksp, compose multiplatform, and android compose compiler.
Kotlin Coroutines 1.8.0.

Upgrade yarn.lock file

I have run CI on my forked repository, it passed 👉 https://github.com/hoc081098/koject/actions/runs/8030334668


Dockstore Integration 1.2.7 Artifact Missing

Bug Report
Expected behaviour
Dockstore Integration 1.2.7 artifact should be on Artifactory
Actual behaviour
It is not on Artifactory

This should not be a proplem, will sit down together to do a 1.2.8 release which should make this redundant. Also, nothing probably relies on the integration test jar anyway


UE 5.3 Compatibility

I've stripped out incompatible interface to allow UE 5.3.X to compile. I'm unclear on the purpose of FGCObject seeing as FArticyGVEditor::AddReferencedObjects() implementation was empty.
I doubt overall that this is a good fix, but figured I'd get the ball rolling on UE 5.3 compatibility.

Closing pull request - official support has been provided already.


[mxnetR] Option to handle missing values

Not able to handle even any single NA.
Reproducible example:
require(mlbench)
require(mxnet)

data(Sonar, package="mlbench")

Sonar[,61] = as.numeric(Sonar[,61])-1
train.ind = c(1:50, 100:150)
train.x = data.matrix(Sonar[train.ind, 1:60])
train.y = Sonar[train.ind, 61]
test.x = data.matrix(Sonar[-train.ind, 1:60])
test.y = Sonar[-train.ind, 61]

train.x[1, 1] <- NA

mx.set.seed(0)
model <- mx.mlp(train.x, train.y, hidden_node=10, out_node=2, out_activation="softmax",
                num.round=50, array.batch.size=15, learning.rate=0.07, momentum=0.9,
                eval.metric=mx.metric.accuracy)

gives
Auto detect layout of input matrix, use rowmajor..
Start training with 1 devices
[1] Train-accuracy=NA
[2] Train-accuracy=NA
[3] Train-accuracy=NA
[4] Train-accuracy=NA
[5] Train-accuracy=NA
[6] Train-accuracy=NA
[7] Train-accuracy=NA
[8] Train-accuracy=NA
[9] Train-accuracy=NA
[10] Train-accuracy=NA
[11] Train-accuracy=NA
[12] Train-accuracy=NA
[13] Train-accuracy=NA
[14] Train-accuracy=NA
[15] Train-accuracy=NA
[16] Train-accuracy=NA
[17] Train-accuracy=NA
[18] Train-accuracy=NA
[19] Train-accuracy=NA
[20] Train-accuracy=NA
[21] Train-accuracy=NA

My thought is maybe provide some helper functions to let users easily handle this.

I am new to mxnet. I am thinking to work on this problem. I have thought of three ways to deal with problem 1. one is omitting the rows with missing data 2. using mean for prediction 3. using EM algorithm before processing . I want to know how missing data is handled in other packages. Any guidance on how to proceed further?

Personally it is users' responsibility to decide how to handle missing data.
I think we can provide some functions, but we can't do that automatically.

so what kind of functions might be helpful ?

Usually in these situations, you are not supposed to use something like matrix completion  algo? What else can be done?
It can't be fixed as easily that in XGboost as we can't easily tell the #nnet NA is a special value. How to compute a partial derivative on it?

@pommedeterresautee I agree with you. We can give a warning, even an error, when the data set has NA. It is users who need to decide how to handle missing values.

Yeah probably just some warnings since new users might not be sure how to deal with NAs in the evaluation metrics. @thirdwing
I was mistakenly thinking this can be handled like in xgboost. @pommedeterresautee thanks for correcting me.


Adding power (ppc64le) architecture image mappings

Changes

Adds ppc64le architecture image mappings
Excludes some of the test cases for ppc64le

/kind misc
Submitter Checklist
These are the criteria that every PR should meet, please check them off as you
review them:

[ ] Includes tests (if functionality changed/added)
[ ] Includes docs (if user facing)
[x] Commit messages follow commit message best practices
[x] Release notes block has been filled in or deleted (only if no user facing changes)

See the contribution guide for more details.
Double check this list of stuff that's easy to miss:

If you are adding a new binary/image to the cmd dir, please update
the release Task to build and release this image.

Reviewer Notes
If API changes are included, additive changes must be approved by at least two OWNERS and backwards incompatible changes must be approved by more than 50% of the OWNERS, and they must first be added in a backwards compatible way.
Release Notes
NONE

/ok-to-test

@sbwsg anyway to look at https://github.com/tektoncd/pipeline/pull/3550 too 🐼 (might affect this)

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

Is there any issue with build infra? pull-tekton-pipeline-integration-tests seems to be failing.

Is there any issue with build infra? pull-tekton-pipeline-integration-tests seems to be failing.

@bahetiamit hum, this is happening on all PRs it seems, something changed somewhere 😓

@bahetiamit hum, this is happening on all PRs it seems, something changed somewhere 😓

/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-integration-tests

@afrittoli Please see if you can find time to review this

@afrittoli Please see if you can find time to review this

/test pull-tekton-pipeline-build-tests

/test pull-tekton-pipeline-build-tests

/test pull-tekton-pipeline-build-tests
/test pull-tekton-pipeline-integration-tests

/test pull-tekton-pipeline-build-tests
/test pull-tekton-pipeline-integration-tests

@vdemeester I am not sure why pull-tekton-pipeline-build-tests is failing. Are you aware of any issue with build infra?

@bahetiamit looking at the log
-------------------------------------------
---- Checking go code style with gofmt ----
-------------------------------------------
diff -u test/multiarch_utils.go.orig test/multiarch_utils.go
--- test/multiarch_utils.go.orig	2021-01-29 09:45:57.785742280 +0000
+++ test/multiarch_utils.go	2021-01-29 09:45:57.785742280 +0000
@@ -74,20 +74,20 @@
 		}
 	case "ppc64le":
 		return map[int]string{
-			busyboxImage:  "busybox@sha256:4f47c01fa91355af2865ac10fef5bf6ec9c7f42ad2321377c21e844427972977",
-			registryImage: "ppc64le/registry:2",
-			kubectlImage:  "ibmcom/kubectl:v1.13.9",
-			helmImage:     "ibmcom/helm-ppc64le:latest",
-			kanikoImage:   "ibmcom/kaniko-project-executor-ppc64le:v0.17.1",
+			busyboxImage:   "busybox@sha256:4f47c01fa91355af2865ac10fef5bf6ec9c7f42ad2321377c21e844427972977",
+			registryImage:  "ppc64le/registry:2",
+			kubectlImage:   "ibmcom/kubectl:v1.13.9",
+			helmImage:      "ibmcom/helm-ppc64le:latest",
+			kanikoImage:    "ibmcom/kaniko-project-executor-ppc64le:v0.17.1",
 			dockerizeImage: "ibmcom/dockerize-ppc64le",
 		}
 	default:
 		return map[int]string{
-			busyboxImage:  "busybox@sha256:895ab622e92e18d6b461d671081757af7dbaa3b00e3e28e12505af7817f73649",
-			registryImage: "registry",
-			kubectlImage:  "lachlanevenson/k8s-kubectl",
-			helmImage:     "alpine/helm:3.1.2",
-			kanikoImage:   "gcr.io/kaniko-project/executor:v1.3.0",
+			busyboxImage:   "busybox@sha256:895ab622e92e18d6b461d671081757af7dbaa3b00e3e28e12505af7817f73649",
+			registryImage:  "registry",
+			kubectlImage:   "lachlanevenson/k8s-kubectl",
+			helmImage:      "alpine/helm:3.1.2",
+			kanikoImage:    "gcr.io/kaniko-project/executor:v1.3.0",
 			dockerizeImage: "jwilder/dockerize",
 		}
 	}

I think you need to do a gofmt -s -w on that file.

Thanks @vdemeester. All checks are green now.


I can't access web app inside docker

$ sudo docker run -d -P training/webapp python app.py

root@vpn:~# docker ps
CONTAINER ID        IMAGE                    COMMAND             CREATED             STATUS              PORTS                     NAMES
e3efda65c3e8        training/webapp:latest   "python app.py"     39 minutes ago      Up 39 minutes       <IP_ADDRESS>:49153->5000/tcp   stoic_pasteur

When I enter <IP_ADDRESS>:49153(my VPS's Ip), but It doesn't response.

what does curl localhost:49153 from the VPS shell do?

@wyaeld
root@vpn:~# curl localhost:49155
Hello world!root@vpn:~#

check your firewall

@duglin I use ufw
root@vpn:~# ufw allow 49155/tcp
Rule added
Rule added (v6)
root@vpn:~# ufw status
Status: active

To                         Action      From
--                         ------      ----
49155                      ALLOW       Anywhere
49155/tcp                  ALLOW       Anywhere
49155 (v6)                 ALLOW       Anywhere (v6)
49155/tcp (v6)             ALLOW       Anywhere (v6)

I can see that 49155 is open, and telnet shows I can connect, but your
initial issue shows the app running on 49153
On Tue, Apr 7, 2015 at 5:37 PM, arcticlion<EMAIL_ADDRESS>wrote:

@duglin https://github.com/duglin I use ufw
root@vpn:~# ufw allow 49155/tcp
Rule added
Rule added (v6)
root@vpn:~# ufw status
Status: active
To                         Action      From

49155                      ALLOW       Anywhere
49155/tcp                  ALLOW       Anywhere
49155 (v6)                 ALLOW       Anywhere (v6)
49155/tcp (v6)             ALLOW       Anywhere (v6)
—
Reply to this email directly or view it on GitHub
https://github.com/docker/docker/issues/12131#issuecomment-90369925.

@wyaeld Oh, It works! It's very strange. It doesn't response at all before.
To save this problem, I stop container before, then I run again and the port changed.

Ohh... the problem you are having is because of the -P flag.
If you use it by itself, it publishes any exposed ports onto something within the available range on the host.  It doesn't automatically publish them onto the same port.  However the range around 49150 seems to be a default somewhere.
If you are just getting started, you'll probably find it easier to explicitly publish the port onto the one you want to open with ufw.  Try using -p 49155:whatever_your_image_exposes

@wyaeld Thanks for help.


Member management and security

Currently everyone bootstrapped into the workspace is equal in role.
However, we do think that privilege / permission management will be important when people start using it in real life.
We need a design for this.
Also, if possible, we may allow workspace owners to create workspaces and manage members within the app,
and get rid of the dependency on the external ndncert server.
We may use Yjs docs to do user management, but the entanglement of sync and security will make things extremely complicated.

We decided to go with two modes: Initiator-only and Peer-to-peer. Detailed design is under discussion
How to support multiple devices of one user is under discussion. We may change the namespace to adapt this.


FormatException: Invalid group(?<=\d)(?=(\d{3})+(?!\d))

On Dart VM have FormatException: Invalid group(?<=\d)(?=(\d{3})+(?!\d))
on code: final _triadesRegExp = RegExp(r'(?<=\d)(?=(\d{3})+(?!\d))');

Teagan, do you know if this is expected behavor?

It's not expected behavior, and it works when I try it out. Here's my quick test file:
void main() {
  final _triadesRegExp = RegExp(r'(?<=\d)(?=(\d{3})+(?!\d))');
  var matches = _triadesRegExp.allMatches("1234i2345");
  for (var match in matches) {
    print("${match.start},${match.end}: \"${match.group(1)}\"");
  }
}

and when running that file, I get the following output:
1,1: "234"
6,6: "345"

which matches my expectations.
Is it possible this is an older version of Dart that doesn't include lookbehind support? IIRC, that was first included in the 2.3.0 release. In any case, more context of the Dart environment being used would be useful if it is post-2.3.0 so I could check on that version.

For now, closing since this doesn't seem to be an issue in versions of Dart that support lookbehind.


chore: setup release-please

This sets up Release Please for the repo. Basically it takes Conventional Commits and generates a changelog, updates documentation versions, and updates the package version. It's very helpful for OSS repos to cut down on maintenance work, and ensure people not 100% familiar with the repo can still release it correctly.
There are a couple of settings that will need to be set on the repo:

We need to set the default PR merge method to squash with default to pull request title and description

We need a personal access token set as GH_PERSONAL_ACCESS_TOKEN secret in the repo. This is used for creating the release in GitHub. Sadly we can't use the normal GITHUB_TOKEN because it won't trigger subsequent actions. You can see a little blurb about this on the release please action README. All it should need is the repo scope. If you want more security, GitHub does have a beta for Fine grained tokens (restricted to only this repo).

@scopsy can we get some assistance on updating the repo settings here please?

@btkostner Done!

Error: release-please failed: Personal access tokens with fine grained access do not support the GraphQL API

:facepalm: Apparently GitHub hasn't setup fine grained tokens to work with GraphQL yet. That's uhhh, annoying. @scopsy Any chance you could use a regular personal access token? Sorry about that. I figured it would work because, well, it's still a personal access token. Apparently not.


git_setup not working anymore?

I just tried to use this action again after not using it for a while and I'm getting an odd failure:
/usr/bin/docker run --name cd98f3c84ac33cc6c4f72b92a734c7dfb[0](https://github.com/ProteoWizard/pwiz/runs/7118491438?check_suite_focus=true#step:4:1)08e_2ac793 --label 4cd98f --workdir /github/workspace --rm -e INPUT_PR_BRANCH -e INPUT_PR_TITLE -e INPUT_GITHUB_TOKEN -e INPUT_PR_BODY -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_RUN_ATTEMPT -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_REF_NAME -e GITHUB_REF_PROTECTED -e GITHUB_REF_TYPE -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e GITHUB_STEP_SUMMARY -e RUNNER_OS -e RUNNER_ARCH -e RUNNER_NAME -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/pwiz/pwiz":"/github/workspace" 4cd98f:3c84ac33cc6c4f72b92a734c7dfb008e  "Skyline/skyline_21_2" "Automatic cherry pick of #{pr_number} from {base_branch} to {pr_branch}" "An automated backport for #{pr_number}." "***"

Traceback (most recent call last):
  File "/action/helpers.py", line 17, in git
    command_run = subprocess.run(["git", *args], stdout=subprocess.PIPE, stderr=subprocess.PIPE, check=True)
  File "/usr/local/lib/python[3](https://github.com/ProteoWizard/pwiz/runs/7118491438?check_suite_focus=true#step:4:4).8/subprocess.py", line 516, in run
    raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command '['git', 'remote', 'set-url', '--push', 'origin', '***github.com/ProteoWizard/pwiz.git']' returned non-zero exit status 128.
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
  File "/action/main.py", line 70, in <module>
    git_setup(args.github_token)
  File "/action/helpers.py", line 5, in git_setup
    git(
  File "/action/helpers.py", line 2, in git
    raise GitException(output)
helpers.GitException: fatal: unsafe repository ('/github/workspace' is owned by someone else)

Any idea what's going wrong here?

Hey !
I've had a similar issue on another action, I think it's a change since a vulnerability was discovered in git.
A similar issue happened there, if that may help https://github.com/repo-sync/pull-request/issues/84

Great, adding that before the repo clone in git_setup fixed the error. Thanks!


Cannot run sbt test twice

On current master, and at least the commit before it I cannot run the following shell command sbt clean test && sbt test without getting a linking error:
[info] Compiling to native code (1020 ms)
[info] Linking native code (immix gc) (184 ms)
[error] java.nio.file.ClosedFileSystemException
[error]         at com.sun.nio.zipfs.ZipFileSystem.ensureOpen(ZipFileSystem.java:1084)
[error]         at com.sun.nio.zipfs.ZipFileSystem.newByteChannel(ZipFileSystem.java:633)
[error]         at com.sun.nio.zipfs.ZipPath.newByteChannel(ZipPath.java:739)
[error]         at com.sun.nio.zipfs.ZipFileSystemProvider.newByteChannel(ZipFileSystemProvider.java:255)
[error]         at java.nio.file.Files.newByteChannel(Files.java:361)
[error]         at java.nio.file.Files.newByteChannel(Files.java:407)
[error]         at java.nio.file.Files.readAllBytes(Files.java:3152)
[error]         at scala.scalanative.io.VirtualDirectory$NioDirectory.read(VirtualDirectory.scala:72)

In other words, running test appears to produce target files that make the next run of test fail.
Running sbt clean or manually removing core/native/target/scala-2.11/classes will make the next run of test complete successfully.
I believe this is the issue I'm encountering in https://github.com/shadaj/scalapy/pull/35 and encountered in https://github.com/shadaj/scalapy/pull/36. As I think TravisCi caches per branch:

There is one cache per branch and language version/ compiler version/ JDK version/ Gemfile location/ etc.
(from https://docs.travis-ci.com/user/caching/)

/cc @densh, this may be a Scala Native bug. Don't think this is a ScalaPy bug since we're not doing anything special with how linking runs.
@valencik have you seen this with Scala Native 0.4.0-M2? Maybe this is just a bug with the 0.3.x series, which is what's used on master right now.

I find that re-runs work when I remove the test "Can use with statement with file object" in MethodCallingTest, if that helps narrowing down the cause.

@valencik @bfdes what happens if you run coreNative/test twice? I haven't seen this during development, but I also don't use the aggregate test command so I have a hunch that that might be the source of the problem.

Running coreNative/test on its own is fine no matter how many times I do it.
I only noticed this error because I hadn't installed the ScalaNative dependencies until very recently. (Before that I was getting an error associated with missing dependencies.)

This seems to be fixed now, I am able to repeatedly run native tests without any failures. Closing for now, but please let me know if this is still an issue!


Infinite scrolling renderer

Since I managed to do the CheckeredBackground for diagnostics, I was wondering if it would be helpful to implement a generic infinite scrolling SpriteRenderer, that could be used as background for a game.
Properties that it should expose:

a Material
a Scale factor
if the scrolling should be made on the X, Y, or both
scrolling speed multiplier?

Should I go for it?

Yes, please!
The default SpriteRenderer of Duality supports already this feature in some ways, but some properties and stuff are not designed for this purposes, so you have to implement your own renderer with some tweaks...
I used this infinite scrolling renderer for my space game to display an infinite star background.
Maybe we could name this renderer like "PlaneRenderer" or something like that...?
Original Issue
https://github.com/AdamsLair/duality/issues/325

Ooh, didn't know there was an issue about this..
alright, will do

Just tried it, very smooth so far!

Fixed one final issue. Still to document the properties. Closing anyway.

Reopening to implement some of the missing requirements described in https://github.com/AdamsLair/duality/issues/161

AlignToPixelGrid
VisibilityGroup

Forgot to close..


Domains

@tiagofneto
For desnap operations we need Copy trait (it is actually free in Cairo because it can be optimized because memory is immutable).
If that's okay I will change Clone to Copy and try to leverage snapshots


sqlx-cli fails to build on 0.7-dev branch

Bug Description
The build fails forsqlx-cli on the 0.7-dev branch. It looks like GItHub Actions is not configured to run on this branch, so that's probably why this was missed.
   Compiling sqlx-core v0.6.2 (/home/joe/src/sqlx/sqlx-core)
warning: unused import: `std::ops::DerefMut`
  --> sqlx-core/src/pool/mod.rs:77:5
   |
77 | use std::ops::DerefMut;
   |     ^^^^^^^^^^^^^^^^^^
   |
   = note: `#[warn(unused_imports)]` on by default

error: non-binding let on a synchronization lock
  --> sqlx-core/src/sqlite/statement/unlock_notify.rs:51:13
   |
51 |           let _ = self
   |  _____________^___^
   | |             |
   | |             this lock is not assigned to a binding and is immediately dropped
52 | |             .condvar
53 | |             .wait_while(self.mutex.lock().unwrap(), |fired| !*fired)
54 | |             .unwrap();
   | |_____________________^ this binding will immediately drop the value assigned to it
   |
   = note: `#[deny(let_underscore_lock)]` on by default
help: consider binding to an unused variable to avoid immediately dropping the value
   |
51 |         let _unused = self
   |             ~~~~~~~
help: consider immediately dropping the value
   |
51 ~         drop(self
52 |             .condvar
53 |             .wait_while(self.mutex.lock().unwrap(), |fired| !*fired)
54 ~             .unwrap());
   |

warning: `sqlx-core` (lib) generated 1 warning
error: could not compile `sqlx-core` due to previous error; 1 warning emitted
warning: build failed, waiting for other jobs to finish...
warning: `sqlx-core` (lib) generated 1 warning (1 duplicate)
error: could not compile `sqlx-core` due to previous error; 1 warning emitted

Interestingly cargo build -F runtime-* works fine on this branch. It's just the CLI that fails.
Minimal Reproduction

Fresh clone
git checkout 0.7-dev
cargo build --manifest-path sqlx-cli/Cargo.toml --bin cargo-sqlx

Info

SQLx version: https://github.com/launchbadge/sqlx/commit/4b7053807c705df312bcb9b6281e184bf7534eb3
SQLx features enabled: defaults, but I tried several and they made no difference
Database server and version: SQLite 3.39.4
Operating system: Archlinux
rustc --version: rustc 1.65.0 (897e37553 2022-11-02)

I believe has been fixed.