support MODULE.bazel for identifying workspace root

Describe the bug
ibazel does not appear to support finding the workspace root of a project with just a MODULE.bazel file (e.g. no WORKSPACE or WORKSPACE.bazel). As far as I can tell this is a valid repo structure for bazel 7.
Reproduction instructions
klandergren/ibazel-no-workspace-file shows a minimal go project that works using bazel 7 but does not work with ibazel Version 0.24.0.
Steps to reproduce the behavior:

git clone https://github.com/klandergren/ibazel-no-workspace-file
ibazel run //hello:hello
See error

iBazel [6:27PM]: Querying for files to watch...
iBazel [6:27PM]: Error finding workspace: ibazel was not invoked from within a workspace

iBazel [6:27PM]: Error querying for source files: ibazel was not invoked from within a workspace

iBazel [6:27PM]: Error finding workspace: ibazel was not invoked from within a workspace

iBazel [6:27PM]: Error querying for source files: ibazel was not invoked from within a workspace

iBazel [6:27PM]: Running //hello:hello
Computing main repo mapping:
Loading:
Loading: 0 packages loaded
Analyzing: target //hello:hello (0 packages loaded, 0 targets configured)
INFO: Analyzed target //hello:hello (0 packages loaded, 671 targets configured).
 checking cached actions
INFO: Found 1 target...
 checking cached actions
 checking cached actions

INFO: Elapsed time: 0.373s, Critical Path: 0.00s
 checking cached actions
INFO: 0 processes.
 checking cached actions
INFO: Build completed successfully, 0 total actions
INFO: Analyzed target //hello:hello (0 packages loaded, 0 targets configured).
INFO: Found 1 target...
Target //hello:hello up-to-date:
  bazel-bin/hello/hello_/hello
INFO: Elapsed time: 0.532s, Critical Path: 0.29s
INFO: 6 processes: 4 internal, 2 darwin-sandbox.
INFO: Build completed successfully, 6 total actions
iBazel [6:27PM]: Starting...
iBazel [6:27PM]: Error finding workspace: ibazel was not invoked from within a workspace

Kips-MBP:ibazel-no-workspace-file klandergren$ 2024/03/06 18:27:57 hello world

Expected behavior
ibazel to find the workspace root via MODULE.bazel
Actual behavior
ibazel walks the directory tree and does not find the root
Version:

OS: MacOS 13.6.4
Browser: chrome
ibazel Version: iBazel - Version 0.24.0
Bazel version:

Bazelisk version: development
Build label: 7.0.2
Build target: @@//src/main/java/com/google/devtools/build/lib/bazel:BazelServer
Build time: Thu Jan 25 16:22:05 2024<PHONE_NUMBER>)
Build timestamp:<PHONE_NUMBER>
Build timestamp as int:<PHONE_NUMBER>

Additional context
I am new to bazel so if I am mistaken re: WORKSPACE/WORKSPACE.bazel no longer required please close this issue.

This issue should be reopened based on interest from the community. Presumably the maintainers would be willing to merge the PR that fixes this (#647) once it's passing CI.

@achew22 could we re-open this? Bazel 8 was released today, and this issue is the last reason many projects will have a non-functional WORKSPACE file


operators azure-service-operator (1.0.27207)

Signed-off-by: Christian Muirhead<EMAIL_ADDRESS>Thanks submitting your Operator. Please check below list before you create your Pull Request.
Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[x] Modify more than one operator
[x] Modify an Operator you don't own
[x] Rename an operator - please remove and add with a different name instead
[x] Modify any files outside the above mentioned folders
[x] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

/merge possible

@babbageclunk, please follow the test output https://github.com/k8s-operatorhub/community-operators/pull/73/checks?check_run_id=3216995333

/merge possible

I'm not sure that my change to ci.yaml will help with getting this merged automatically - presumably it's looking at the previous version to determine whether these changes should be considered authorized. But I guess it'll help for next time.

/merge possible

I've made the reviewers change but it looks like that will only help with auto-merging once this has landed. Can someone merge this for me? Possibly @madorn?

@babbageclunk automerge will work next time as it checks main for security reasons.

@J0zi thanks, that makes sense.


fix division by zero

Hi,
unit_vector(a,b) sometimes divides by zero (a==b).
With the consequence of creating a blank output with fdg-img.
Have a good day

Thanks!


build(github CI): replace actions/cache@v2 with `Swatinem/rust-cach…

…e@v2`

actions/cache@v2 seems no longer working for cargo

before vs after:

Can you resolve the merge conflicts created by your last PR?


Ghost considers my 4-character Facebook username to be invalid.

Steps to Reproduce

Navigate to /ghost/settings/general/ and scroll down to the Facebook Page setting
Enter my Facebook URL, https://www.facebook.com/folz

What I expected to happen:
I would be able to configure my Facebook URL in the settings.
What actually happened:
I received the error message "Your Page name is not a valid Facebook Page name"

Looking at the relevant validation in app/controllers/settings/general.js, this appears to be intentional. However, this means you're excluding anyone who worked at Facebook from linking their profile, as current/former FB employees are allowed to have usernames under 5 characters. Also, some brands have Page usernames under 5 characters (ex: https://www.facebook.com/nike).
Technical details:

Ghost Version: Pro
Node Version: Unsure, using Pro
Browser/OS: Firefox on Linux
Database: Unsure, using Pro

Was trying to make a PR for this, but it's taking me a while to figure out how to set testem up with Chromium and not Chrome. The related test is at tests/acceptance/settings/general-test.js:272 and potentially :280.


fix timer leak

The following code leads to timer leak. defer ticker.Stop() cannot stop the new ticker because of different addresses. The patch fixes this bug.
case timeout := <-t.timeout:
 			ticker.Stop()
 			ticker = time.NewTicker(timeout)

Thanks


⚠ GitHub has degraded performance

In 34c07fb, GitHub (https://www.githubstatus.com/api/v2/status.json) experienced degraded performance:

HTTP code: 200
Response time: 344 ms

Resolved: GitHub performance has improved in ca1c3fe.


Windows update is not working properly after creating a MicroWin image

Describe the bug
Windows update is not working properly after creating a MicroWin image - it does not install cumulative updates with the error 800f0983. Tested on latest builds of Windows 11 ARM and Windows 10, the issue is identical.
Repair (sfc, dism restore health) does not help. Sfc finds a lot of damaged components though. Happens on both VM and real hardware.
To Reproduce
Steps to reproduce the behavior:
Create an image de-selecting options "Keep Defender" and "Keep Edge" (essentially removing everything). It also breaks WinUpdate if you de-select only "Keep Edge".
So resulting image will be broken and will not install cumulative updates once installed. Other updates install fine though.
Screenshots

Additional context
Happy to assist in testing.

Probably because of setting security update by default? I have no idea how does MicroWin works but I guess that's the issue

Amazing, you are correct!. Indeed if I switch the update options in the script, they install fine.
I believe this must be documented properly as it is very unclear - also why run the tool after installation if the image was supposed to be pre-configured.

Alright. I think someone should make a switch to switch between update mode before getting configured.
But I am too out of touch with Microwin having no idea how to add it. But I can try my best adding it.

@CodingWonders

Sadly, I don't have a powerful ARM-based device (the only thing I have with such a chip is a Raspberry PI 3B)

This is also applicable to a regular x86-64 image. I can assist in testing on ARM if required
Get BlueMail for Android
On 11 Jul 2024, 15:19, at 15:19, CodingWonders @.***> wrote:

Sadly, I don't have a powerful ARM-based device (the only thing I have
with such a chip is a Raspberry PI 3B)
--
Reply to this email directly or view it on GitHub:
https://github.com/ChrisTitusTech/winutil/issues/2118#issuecomment-2223064127
You are receiving this because you authored the thread.
Message ID: @.***>

Hi,
Sorry for the lack of response. It looks like that current versions of the script do not have this problem anymore: I've checked ARM version 2 weeks ago and a regular x64 one now, and haven't encountered any problems with windows update.


Polymer Gestures creates a new bound handler for every listen call

As discussed in person, this could be made slightly more optimal by looking to see if a listener has been created already.
Fixing this would allow listen to be called n times with the same arguments, while ensuring that only one listener is ever actually added.

This bugfix blocks https://github.com/PolymerElements/iron-selector/pull/64

This is a bug in events module, not in gestures.

Amended the title.

We merged a temporary patch to IronSelectable where we do our own book-keeping. When this is closed, we should go back and clean up the extra book keeping in https://github.com/PolymerElements/iron-selector/pull/70


Bump black version and relax constraint

Summary
See Qiskit/qiskit-terra#7615
Details and comments

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

4 of 5 (80.0%)  changed or added relevant lines in 5 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 82.735%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit_finance/circuit/library/probability_distributions/gaussian_conditional_independence_model.py
0
1
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
714

Relevant Lines:
863

💛  - Coveralls


fix: correct squoosh leveled dependencies

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[x] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description
This PR removes pre-node 18 dependencies and makes development work again with image scripts
Related Tickets & Documents

closes #350
Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

❌ Deploy Preview for hot-sauced-ui failed.
Name	Link
🔨 Latest commit	30ceb10
🔍 Latest deploy log	https://app.netlify.com/sites/hot-sauced-ui/deploys/64639d5fa5e7f10008285012

@bdougie needs NODE_VERSION=18 in netlify project to finish the upgrade 🚀

NODE_VERSION=18

done

NODE_VERSION=18

done

added the .node-version file as well, think it's better than setting the env variable remotely, even if this is my least favorite method :< (extra tooling files)


Delete Review doesn't delete the review from the left side Average Rating Section

STR-
Add a review to an app.
Delete the review.
Click through the "are you sure?" prompt.
RESULTS - Review is removed from User Review and Review this Listing Section but stays in Average Rating Section
EXPECTED RESULTS - Should be removed from all sections and not require a refresh in order to clear out the review.

Can't recreate bug with latest version of "git pull" for master. I believe this issue was resolved thanks to:
491: fixed IconRating issue
@tonyalletag
@tdressel

@clarkjefcoat

Looks resolved to me too (Tested in Chrome, IE11)

Passed

Passed on Staging.


Do not check the expiration time at during a revoke

https://github.com/oauthjs/node-oauth2-server/blob/master/lib/grant-types/refresh-token-grant-type.js#L135
At revocation of the refresh token, only a state i.e. isRevoked=true should be changed. I think, revokeToken should not change the token expiration time. So there is no need to check refreshTokenExpiresAt value.
EDIT
Docs says:
revokeToken	Must revoke the accessToken and return the revoked object	{ expiresAt: '2015-11-16T23:58:59.888Z' }

Is there a typo? It should be
Must revoke the refreshToken ...

#250


Crashes on 1.16.5 after clicking start game

It seems like this mod is trying to send a request to some kind of server before a world has been loaded which minecraft doesn't like and crashes because of

Update: This actually seems to only happen if u click ctrl or shift which is.... strange as when you're in the world it works fine

Duplicate of #2


Update 07-advanced.md, document isAbsolute for $get

Added missing documentation of $get function. Found the solution in https://github.com/filamentphp/filament/discussions/4843 by @danharrin

Description
I was having difficulty accessing property values which I was unable to resolve until I stumbled across @danharrin's solution. I had come across the isAbsolute property, but i did not realise it was the absolute path of the Livewire component.
I have added the information @danharrin provided with a code example in the appropriate section of the Advanced Forms page.

Visual changes

Functional changes

[x] Code style has been fixed by running the composer cs command.
[x] Changes have been tested to not break existing functionality.
[x] Documentation is up-to-date.

Thanks! Going to keep this out of the documentation still though, as it's tricky to explain how to find the correct absolute path (do you choose data or mountedActionData or something else)? I think it might cause more confusion than it's worth, and I want to encourage users to use ../../ to traverse the state paths instead. Maybe it will get simpler in the future.

👍 ok no worries, I figured that might be the case.
I hoped it would just help the next person find the solution and figure it out with some troubleshooting.
I only found the ../../ traversal pattern after this pr.
Its documented in the Repeater documentation, not with the rest of the $get documentation.
I'm not sure it would have solved my problem anyway.


Use a top default registry when pushing unqualified repository

This is based on issues #11815 and #11816.
Use case
As an enterprise user interacting with multiple private registries with little or no need for a public registry, I'd like to be able to push unqualified repository to one of my private registries.
So when I execute:
$ docker push precious/app

it will be pushed to my default registry specified in configuration.
Requirements

Allow to specify a default registry used for push of any unqualified repository.

Proposal
Use the first item in the list of default registries as a receiver of unqualified repositories during push command.

Closing for the same reason as #11816
Having that ability will definitely happen, but we need image signing first to guarantee this will not let ISV fragment the image namespace.


[Ameba] Read General Diagnostic attributes from platform at runtime

Problem

To be consistent with PR #9930, populate General Diagnostic attributes with the actual value from Ameba platform in run-time

Change overview

Read General Diagnostics attributes from Ameba platform
Add framework of WiFi Network Diagnostics attributes

Testing

Tested all-clusters-app control via python controller.

Fast tracking, given this is a platform maintainer making platform changes.

Comments appear resolved.


Adding kneaddata pipeline

cc: @tanaes and @josenavas

retest this please

@jdereus, can you take a look at this one?

Looks good.  Build failure point is gone.
JD
From: Antonio Gonzalez <notifications<EMAIL_ADDRESS>Reply-To: qiita-spots/qp-shotgun <reply<EMAIL_ADDRESS>Date: Thursday, November 10, 2016 at 9:54 PM
To: qiita-spots/qp-shotgun <qp-shotgun<EMAIL_ADDRESS>Cc: Jeff DeReus <jdereus<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [qiita-spots/qp-shotgun] Adding kneaddata pipeline (#19)
@jdereushttps://github.com/jdereus, can you take a look at this one?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/qiita-spots/qp-shotgun/pull/19#issuecomment-259886891, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANq27QUDhL4ool_uuTL0PkrBEyiV43uCks5q9AL9gaJpZM4Kn1DQ.

Yes, note that the other one has changes on top of this one so @josenavas could debug. Perhaps this will pass???

@jdereus note that the current error is: AssertionError: '' != u'Error running KneadData:\nStd out: \nStd err: ERROR: Unable to find trimmomatic. Please provide the full path to trimmomatic with --trimmomatic., and the reason @josenavas was trying to debug with the other PR. However, I think the easiest will be to run the commands on the machine and figure out what's wrong or what needs to change. Thank you for taking a look.

Saw that late last night.  Trimmomatic is present in environment location.  Some sort of $PATH issue?  Not sure how kneaddata looks for binaries.
From: Antonio Gonzalez <notifications<EMAIL_ADDRESS>Reply-To: qiita-spots/qp-shotgun <reply<EMAIL_ADDRESS>Date: Friday, November 11, 2016 at 5:28 AM
To: qiita-spots/qp-shotgun <qp-shotgun<EMAIL_ADDRESS>Cc: Jeff DeReus <jdereus<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [qiita-spots/qp-shotgun] Adding kneaddata pipeline (#19)
@jdereushttps://github.com/jdereus note that the current error is: AssertionError: '' != u'Error running KneadData:\nStd out: \nStd err: ERROR: Unable to find trimmomatic. Please provide the full path to trimmomatic with --trimmomatic., and the reason @josenavashttps://github.com/josenavas was trying to debug with the other PR. However, I think the easiest will be to run the commands on the machine and figure out what's wrong or what needs to change. Thank you for taking a look.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/qiita-spots/qp-shotgun/pull/19#issuecomment-259957093, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANq27acIcHqmDAWlU-XyCjARnP5U27oMks5q9G1lgaJpZM4Kn1DQ.

Thanks. Just out of curiosity, which is the version/path of the installed version of trimmomatic?

Proper trimmomatic installed for 0.36-3.
/var/lib/jenkins/workspace/qp-shotgun-job/miniconda3/envs/qiita_env/bin -> ../share/trimmomatic-0.36-3/trimmomatic
From: Antonio Gonzalez <notifications<EMAIL_ADDRESS>Reply-To: qiita-spots/qp-shotgun <reply<EMAIL_ADDRESS>Date: Friday, November 11, 2016 at 6:48 AM
To: qiita-spots/qp-shotgun <qp-shotgun<EMAIL_ADDRESS>Cc: Jeff DeReus <jdereus<EMAIL_ADDRESS>Mention <mention<EMAIL_ADDRESS>Subject: Re: [qiita-spots/qp-shotgun] Adding kneaddata pipeline (#19)
Thanks. Just out of curiosity, which is the version/path of the installed version of trimmomatic?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/qiita-spots/qp-shotgun/pull/19#issuecomment-259972543, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANq27RJyWnF8OWZcjmPVRMvLOtjlZ2ySks5q9IBIgaJpZM4Kn1DQ.

retest this please

@jdereus could you take a look? I think now it's a JAVA error ...

ping @jdereus!

I don't believe you are trying to call the jar file.  Looks like you need to give path to trimmomatic.jar.  will check more when not in middle of conference
Sent from my mobile device. Please forgive typos and brevity.
On Tue, Nov 15, 2016 at 10:52 AM -0700, "Antonio Gonzalez" <notifications<EMAIL_ADDRESS>wrote:
ping @jdereushttps://github.com/jdereus!

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/qiita-spots/qp-shotgun/pull/19#issuecomment-260714943, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANq27fxzfo8sOxKqr65Z23xYzUBSGjgMks5q-fFegaJpZM4Kn1DQ.

I think that it wants the directory in which trimmomatic.jar is located, rather than the jar itself (at least passed to kneaddata via --trimmomatic_path). I have done this in other contexts by either readlink -f which trimmomatic or hardcoding.
Kneaddata has a little 'find_dependency' util that grabs the value in trimmomatic_path and looks for 'trimmomatic*.jar' in it.
-j

@jdereus, can you check the latests tests? I think the issue is that the encapsulation of the environments are not happening the way it should be ...

This is different.
http://kl-ci.ucsd.edu:8080/job/qp-shotgun-job/85/console
Something is not installing correctly.
 I think the issue is that the encapsulation of the environments are not happening the way it should be ...

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/qiita-spots/qp-shotgun/pull/19#issuecomment-260832504, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ANq27dAPVte3NctNcbPt5MjlLlvIABmDks5q-mWIgaJpZM4Kn1DQ.

@jdereus, that's correct. The issue is that I'm using -U (pip install -U sphinx sphinx-bootstrap-theme coveralls ipython[all]==2.4.1) to force the install and confirm that the encapsulation is not fine as the files can't be updated because they can't be rewritten (outside of the vm). I thought this could be the problem after this run: http://kl-ci.ucsd.edu:8080/job/qp-shotgun-job/83/console, because it says that some of the packages were already installed, which is not possible.

retest this please

@tanaes and @josenavas, this is ready for review.

This looks good to me if passing... @antgonza let me know if ready to merge.

@tanaes I think is fine to merge but @josenavas requested changes so I would suggest waiting for him to merge, thanks!


clarify that the Containers property is able to patch existing containers.

I noticed this useful feature (or behavior) when I was reading the source code for another reason. It would be nice to clarify the feature.
Signed-off-by: UMEZAWA Takeshi<EMAIL_ADDRESS>

Thanks for contribution! Documentation is far from perfect and every improvement is great.


Inserting/updating/erasing lines still fails sometimes

I believe this is an issue with either the scrollable region or with the commands for moving lines.
This can be reproduced easily by running vim and adding more lines than fit on the screen. In this case it looks like only the last three lines update while the rest of the screen is still showing old lines (enabling line numbers in vim helps). It gets even worse when using ctrl-u and ctrl-d to scroll back up again.
I've seen similar issues with less.

All repositories in the atom-archive organization are unmaintained and deprecated. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!


git config doesn't recognize U:\ as the user directory in PowerShell

System Details

posh-git version/path: 0.7.3  C:\Program Files\WindowsPowerShell\Modules\posh-git\0.7.3
PowerShell version: 5.1.17134.112
git version 2.17.1.windows.2
OS: Microsoft Windows NT 10.0.17134.0

Issue Description
I am experiencing a problem with git config in PowerShell, which I'm assuming is the case since it doesn't recognize U:\ as the user directory. Whenever I query my identity with something like git config user.email it returns nothing, while doing the same in git-bash.exe shell works as intended. This problem happens whether I use --global or omit it for local config.
Even my config within my local .git folder has the proper email listed under [user] but it still generates some fake email using my domain login. Again, I have no problems when I use git-bash.exe

My first guess is that your HOME environment variable isn't set. What do you get for $HOME or $Env:HOME?
What do you get from git config --show-origin --name-only --list? (No values will be included, so safe to share.)

I tested all this on my home computers and they all worked fine. The problem seems to only occur on my work computer so it may be an issue with how my work computer's credentials/domain are setup (outsourced IT dept, not sure what was all done).
$HOME returns my user directory (C:\Users<username>)
$Env:HOME returns U:\
and git config --show-origin --name-only --list returns
file:"C:\\ProgramData/Git/config"       core.symlinks
file:"C:\\ProgramData/Git/config"       core.autocrlf
file:"C:\\ProgramData/Git/config"       core.fscache
file:"C:\\ProgramData/Git/config"       color.diff
file:"C:\\ProgramData/Git/config"       color.status
file:"C:\\ProgramData/Git/config"       color.branch
file:"C:\\ProgramData/Git/config"       color.interactive
file:"C:\\ProgramData/Git/config"       help.format
file:"C:\\ProgramData/Git/config"       rebase.autosquash
file:C:/Program Files/Git/mingw64/etc/gitconfig http.sslcainfo
file:C:/Program Files/Git/mingw64/etc/gitconfig http.sslbackend
file:C:/Program Files/Git/mingw64/etc/gitconfig diff.astextplain.textconv
file:C:/Program Files/Git/mingw64/etc/gitconfig filter.lfs.clean
file:C:/Program Files/Git/mingw64/etc/gitconfig filter.lfs.smudge
file:C:/Program Files/Git/mingw64/etc/gitconfig filter.lfs.process
file:C:/Program Files/Git/mingw64/etc/gitconfig filter.lfs.required
file:C:/Program Files/Git/mingw64/etc/gitconfig credential.helper
file:C:/Program Files/Git/mingw64/etc/gitconfig core.editor
file:.git/config        core.repositoryformatversion
file:.git/config        core.filemode
file:.git/config        core.bare
file:.git/config        core.logallrefupdates
file:.git/config        core.symlinks
file:.git/config        core.ignorecase
file:.git/config        remote.origin.url
file:.git/config        remote.origin.fetch
file:.git/config        branch.master.remote
file:.git/config        branch.master.merge
file:.git/config        gui.wmstate
file:.git/config        gui.geometry
file:.git/config        submodule.SlotFramework/Engines/HarmonyEngine.url
file:.git/config        submodule.SlotFramework/Engines/HarmonyEngine.active
file:.git/config        status.submodulesummary
file:.git/config        user.email
file:.git/config        user.name

While I'm still unable to reach the global config:
D:\Soft\lgdev\SlotFramework\Engines [master ↑2]> git config --global user.name "Jason Knobler"
error: could not lock config file U://.gitconfig: No such file or directory

I seem to have been able to finally have my local repo's config take effect once I did a git commit --amend --reset-author. This is workable for me, assuming it keeps working. I don't want to waste anymore of your time since the problem is likely with my work computer, so feel free to close the issue unless you want to respond with more info.

I'm going to go ahead and close this, since it doesn't seem to be specific any posh-git functionality...
That being said, this code is probably relevant. Since it's working in Git Bash, what does echo $HOME show there? Does the problem go away if you set $Env:HOME = "$Env:USERPROFILE" (or otherwise set $Env:HOME to C:\Users\jknobler)?

Because of roaming profiles and VPN connections I had a similar situation, that the U: drive as my home folder was not available when I had to connect via VPN (U-Drive was not connected).
In these cases, the .gitconfig from the local home was chosen (c:\users\<account>) from Git-Bash. But posh-git was not able to do the same. ($Home pointed to  c:\users\<account> but $Env-Home pointed to U:\, which was not connected and therefore not available). Without having the .gitconfig none of my aliases were available.
To work-around this, I did a $Env:Home = $Home. After this all my aliases were back.


Creating container failed component=arangodb error="container already exists"

root@arango2:~# docker run -it --name=adb939029 --rm -p 8528:8528     -v arangodb:/data     -v /var/run/docker.sock:/var/run/docker.sock     arangodb/arangodb-starter     --starter.address=<IP_ADDRESS>     --starter.mode=single
2020-07-09T12:34:34Z |INFO| Starting arangodb version 0.14.15, build e32307e component=arangodb
2020-07-09T12:34:52Z |INFO| Relaunching service with id '19b86afd' on <IP_ADDRESS>:8528... component=arangodb
2020-07-09T12:34:52Z |INFO| Using storage engine 'rocksdb' component=arangodb
2020-07-09T12:34:52Z |INFO| ArangoDB Starter listening on <IP_ADDRESS>:8528 (<IP_ADDRESS>:8528) component=arangodb
2020-07-09T12:34:52Z |INFO| agent starting routine component=arangodb
2020-07-09T12:34:52Z |INFO| agent started routine component=arangodb
2020-07-09T12:34:52Z |INFO| Looking for a running instance of agent on port 8531 component=arangodb
2020-07-09T12:34:52Z |INFO| Starting agent on port 8531 component=arangodb
2020-07-09T12:34:53Z |INFO| dbserver starting routine component=arangodb
2020-07-09T12:34:53Z |INFO| dbserver started routine component=arangodb
2020-07-09T12:34:53Z |INFO| Looking for a running instance of dbserver on port 8530 component=arangodb
2020-07-09T12:34:53Z |INFO| Starting dbserver on port 8530 component=arangodb
2020-07-09T12:34:54Z |INFO| coordinator starting routine component=arangodb
2020-07-09T12:34:54Z |INFO| coordinator started routine component=arangodb
2020-07-09T12:34:54Z |INFO| Looking for a running instance of coordinator on port 8529 component=arangodb
2020-07-09T12:34:54Z |INFO| Starting coordinator on port 8529 component=arangodb
2020-07-09T12:35:02Z |INFO| Failed to register upgrade plan changed callback component=arangodb error="context deadline exceeded"
2020-07-09T12:35:09Z |INFO| agent up and running (version 3.6.4). component=arangodb
2020-07-09T12:35:11Z |ERRO| Creating container failed component=arangodb error="container already exists" options={"Config":{"Cmd":["-c","/data/coordinator8529/arangod.conf","--database.directory","/data/coordinator8529/data","--javascript.startup-directory","/usr/share/arangodb3/js","--javascript.app-path","/data/coordinator8529/apps","--log.file","/data/coordinator8529/arangod.log","--log.force-direct","false","--cluster.my-address","tcp://<IP_ADDRESS>:8529","--cluster.my-role","COORDINATOR","--foxx.queues","true","--server.statistics","true","--cluster.agency-endpoint","tcp://<IP_ADDRESS>:8531","--cluster.agency-endpoint","tcp://<IP_ADDRESS>:8531","--cluster.agency-endpoint","tcp://<IP_ADDRESS>:8531"],"Entrypoint":["/usr/sbin/arangod"],"ExposedPorts":{"8529/tcp":{}},"Image":"arangodb/arangodb:latest","Labels":{"created-by":"arangodb-starter"},"Tty":true},"Context":null,"HostConfig":{"LogConfig":{},"PortBindings":{"8529/tcp":[{"HostIP":"<IP_ADDRESS>","HostPort":"8529"}]},"RestartPolicy":{},"VolumesFrom":["/adb939029"]},"Name":"/adb939029-coordinator-19b86afd-0-<IP_ADDRESS>-8529","NetworkingConfig":null}

@max-yue Can you check whether other containers are already running and happen to have the same name, which causes a conflict?


SVProgressHUD  setSuccessImage  显示出来是一块黑色的

[SVProgressHUD]  setSuccessImage 显示出来是一块黑色的，并不是我设置的图

The repository language is english. Please reopen with an english description if necessary, otherwise the issue remains closed for now.
FYI: Questions like this, are the reason people burn out on open source. Don't let others do your work, give good questions (in a language everybody understands, especially the maintainer), follow issue guidelines, provide a demo project or tell what you have already done to solve the problem.


List item with multiple blocks, last empty block outdents

Place the cursor in the last block of a multi list item. When the last block in the list item is an empty paragraph, hit the enter key. The expected behavior is to create a new list item below the current one. Instead, the current multi block list item is outdented.
If the last block in the list item has content, a new list item is created below the initial multi block list item. This is an edge case that is totally worth eliminating.
Initial State:
* list item
  > with multiple blocks (can just be paragraphs)
  <cursor at empty paragraph>
* list item

Result:
list item

> with multiple block types

<cursor at empty paragraph>

* list item

Example Gif:

Thank you for reporting. Fixed in 0.5.7 by https://github.com/GitbookIO/slate-edit-list/pull/39


creduce: 2.6.0 -> 2.7.0, now uses LLVM 4

Motivation for this change
Update.
Things done

[x] Tested using sandboxing
(nix.useSandbox on NixOS,
or option build-use-sandbox in nix.conf
on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] Linux

[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Fits CONTRIBUTING.md.

Tested using creduce in derivations to conduct the reductions described on their website, LGTM.

(CI error seems to be unrelated, something about nox...)


object reference in three.js

Hi!
I just came across this project today and found it pretty amazeing!
I played with the three.js stl exporter and 3d-printing lately, and wanted to do something with your library. So I setup a basic three.js page (http://mitschelen.de/share/test/) but I had some problems referencing the whole generated object, which geometry I need to pass to the exporter. I wonder if I need to do some more recrusive backwards engineering, like pushing all geometrys into a  group by myself, or is there already a way to reference the whole generated objects geometry?

Thanks a lot for the kind words!
The problem seems to be that the stel exporter (https://github.com/envisprecisely/THREE2STL) takes a single geometry and exports it to stl. However, the structure created by grow3 consists of a tree of Object3D-instances. Each object in turn has a geometry attached (f.e. a cube or sphere).
What would be needed would be either an exporter to stl that can handle object trees OR a way to flatten a complete three.js-scene into a single geometry (losing individual material-properties). A starting point for the latter could be THREE.GeometryUtils.merge() that can merge two meshes into one.
For now I'll leave this issue open...

Thanks foor the answer!
I see.., i had some success useing https://gist.github.com/kjlubick/fb6ba9c51df63ba0951f, which can handle the whole scene:

unfortunately the created STL isn't really suitable for 3D Printing, the mesh holds way too many informations, so i guess i have to use something like THREE.GeometryUtils.merge()
or ThreeCSG anyway.
I will give you an update if i find the time to do this:)


[Idea] Supporting WebP via CocoaPod's subspec

Hey! First off, I only recently discovered this library and wow it's impressive! As our project has evolved we've outgrown our existing tool used for managing remotely served images and when I came across TIP it seemed to check all of the boxes for what I was looking for!
We currently also depend on WebP support and I understand why you didn't include it built into TIP however I was wondering if there is any reason not to provide the Codec via an opt-in subspec using CocaPods?
I see that there is a bit of trickery around getting libwebp building for Mac Catalyst however I stubbed across SDWebImage/libwebp-Xcode and it appears to handle all platforms correctly (although I need to double check that). In the sample PR here, I've added a simple subspec that includes the TIPXWebPCodec as well as a dependency on the libwebp pod provided by the linked repo and can confirm that this works for my iOS project... Is this approach something that interests you?
I guess that there are still a few unresolved questions though but I wanted to get opinions before I dig deeper:

Does this work for everything (macCatalyst and so on)?
How much work does it take to get TIPXWebPCodec up to scratch to release alongside (I noticed a couple of TODO's)
Should we somehow auto-register the codec with TIPImageCodecCatalogue or leave that up to the user?

No worries if this isn't something that you want to support in TIP, I just thought that it's better to check here as I'd much rather help give back a little than just integrate something directly into our project 🙏

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

Thank you for taking active interest!   We are committed to having Twitter Image Pipeline be a zero dependency project but have taken great pains to provide abstractions so that consumers can plug in their own customizations.  It is important that the WebP extended code be committed to the repo but also unnecessary for using TIP, only Apple provided decoders/encoders will be automatically supported.  This will avoid any binary bloating for consumers that do not need codecs that are not included by Apple.  iOS 14 adds WebP support and we have a large set of revisions coming down the pipeline that would include that WebP decoder for iOS 14+, among other things.
I think the libwebp CocoaPod dependency is great and, as an alternative, would encourage yourself and others to create a WebP codec for you application layer to plug into Twitter Image Pipeline.  You can simply copy the the TIPXWebPCodec code and replace any implementation parts you want to customize to fit your needs (being that you want to use a different dependency for webp but still want webp, the delta ought to be quite trivial - but you could add other codecs too).  Then you merely need to register your own codec with the TIPImageCodecCatalogue.
I can empathize with the in-between-ness of where does such a "glue" layer live in open source.  We have a similar problem between Twitter Image Pipeline and Twitter Network Layer.  Using TIP & TNL together requires a small amount of "glue" and we provide that as a gist: https://gist.github.com/NSProgrammer/6e4c93ca9b9518178c9cbc7d950efd9c  --- perhaps we need to think more about "glue" being open sourced but that is what we have for now.  Were you to construct your own "glue" gist, we would happily link to it.
Again, thank you for your PR and great thoughts on advancing Twitter Image Pipeline.  Although this PR doesn't align with the philosophy of this project, we hope that you would continue to maximize TIP for your use cases and provide PRs of improvement in the future too!  Feel free to reach out for questions or comments on this or any other Twitter iOS open source projects on Twitter: @NolanOBrien

Also, I should note, that in the upcoming release of TIP, the codec protocol interface will be revised slightly.  Adapting to the changes will be very straightforward, but I feel it only fair to prepare you so that you won't be caught off guard that any custom codecs will stop compiling after updating to the latest TIP in the future.

Thanks @NSProgrammer for such a detailed explanation, I imagined that something like this might be the case so no worries at all! We're more than happy to bring the custom codec under our control so will do just that given your reasoning here
I agree with you regarding the glue logic and that was my main reasoning for thinking about how it could be included since the codec itself was already checked into this repo, but it makes sense not to do that because of the libwebp dependency like you mentioned.
The idea of using a subspec though was inspired by libraries such as Firebase where their frameworks integrate with one another using subspecs so in theory something similar might be possible here where there is a 'TNL' subspec in this repo that contains the glue code you linked in the gist ... That kind of approach might help consumers who look to use both dependencies 🙂
Thanks again for all the work that went into this, I'll close this PR off now 👍


Protect ceph_pools with default value

with_* always executed before when, conditions in when can't protect the variable in with_*.
This patch is to protect ceph_pools with default empty dict.

Can one of the admins verify this patch?

"ok to test" to accept this pull request for testing
"test this please" for a one time test run
"add to whitelist" to add the author to the whitelist

ok to test


Allow me to define the query URI myself

This is a crazy use case, but it would be extremely helpfull for extending missing functionality on the server side, where I need to make a request with a URI that is provided by WebApi OData.
I would like to be able to define the whole query URL (get only) myself.
Something along the line:
await odc.For<Account>()
    .WithUri(stringoruri)
    .FindEntryAsync();

Here is the concrete use case. There is extremely no limited support for odata.bind in Webapi Odata. Witha  custom deserializer I am able to get the URL's of all the objects bound to my main object. Sadly I need to still make the requests for those objects, and crazy as I am - l really want to use simple odata client.
Deserializing etc. can be not totally trivial, so I would love to be able to use the existing preferred client library ;) Because that hanels all special cases quite easily ;)

But can you use custom query options? It's defined in OData protocol and supported by the library.

Not really. This is a pure "get the object for the bind".
This is a "post/Put" scenario (and patch) where someone defines another object (like you do).
Example:
if you post an object (Account) and it has a Property with the Entity User, you send odata.bind
now I either parse the URL you generate, or (easier) i just make a get request for this url (which then also handles security and checks whether you can read it on the side).
This is pure easy "execute get on url and return object(s). to allow retrieval of AN object (mostly I htink) that i take fom the URL in an odata.bind

I see. I need to think if this is not going too far. After all, the library's primary goal is to wrap OData functionality. The extension you propose has nothing to do with OData protocol so I am not sure it belongs to the library.

There is still a lot  - possibly return structures, error handling etc. Also do not forget that parsing the return is not trivial - there may be inheritance involved. This can be quite complex.
Being able to "just use simple.odata.client" with a custom defined URL would solve all these scenarios. Otherwise I likely have to regbuild asignificant part of the logic myself, at least the whole return type parsing.
So, I am not sure it has nothing to do with Odata prodocol- there is a lot of possible logic involved to make sure you get the proper type from edm etc.  - all that is bypassed is the "generate the query url" part.

I see your point but also have reasons to be concerned about extending the API with unrelated functionality. Many developers use Intellisense to explore the API. Currently fluent API is an entry to OData URI building blocks, like "filter", "expand" and "select". I am not keen about mixing it with something that don't belong to OData. I'd rather think about extension points, to you could write your own extension methods on the top of the library without making the rest of library users aware of them.

Let's talk then about opening up a little ;)
Given a HttpResponseMessage, how can i get it parsed into one or more (Entry, Entries) of a specific type?
This as entry point should also fit with unit testing this particular functionality ;) May even exist already ;)

The library already exposes method GetResponseStreamAsync.


TypeError: destination.substring is not a function

When I down migration:
exports.up = function (db, callback) {
  db.runSql('ALTER TABLE tableName ADD CONSTRAINT keyName UNIQUE (key1, key2)', function (err) {
    if (err) return callback(err);
    callback();
  });
};

exports.down = function (db, callback) {
  db.runSql('ALTER TABLE tableName DROP CONSTRAINT keyName', function (err) {
    if (err) return callback(err);
    callback();
  });
};

Error:
[INFO] Defaulting to running 1 down migration.
[ERROR] TypeError: destination.substring is not a function

Hey @WebStyle,
unfortunately we can't help you if you don't provide us all informations necessary to reproduce your case.
This means, always post:

used node version
used npm version
used db-migrate version
used driver and its version
used plugins
full output of the verbose run
in complex cases a full gist, as an executable proof
if necessary used migrations and configuration details (replace sensible informations before posting configs!)
if necessary code samples

As soon as you provide us all information needed, we have an easy way to reproduce your problem and provide you with the help or bugfix you need.
Thank you.

Thank you, i'm upgraded db-migrate. Its works!!!


Add add_item wrapper around SecItemAdd

Move Location struct from key.rs to item.rs and re-use it for this SecItemAdd abstraction.
Create an ItemAddOptions builder struct.

Thanks!


compute credible sets from CAFEH output outside of python

Hi CAFEH-team,
Congratulations on publishing such a decent tool. I am currently working to implement CAFEH to be used with pQTL data and must admit that I struggle a bit in understanding the output in the results file.
For example, my naive assumption was that one can use the alpha column to obtain 95%-credible sets by simply subsetting alpha > 0.95. However, the top ranked SNP does usually have a zero as entry, which means it is dropped. Further, the sum of the pi column of the SNPs included does not sum up to 95%, which is my naive understanding how credible sets are computed. In addition all SNPs are assigned to a top component in the example I am working on, and I was wondering, on how to decide which components to drop.
I appreciate that the tool is written in python with additional functionality to obtain credible sets and so, but as CAFEH would be part of a more complex workflow mostly embedded within R, I would love to be able to obtain such information form the results output only.
Just to clarify, I am using the z-score-based version of CAFEH with summary statistics.
Thanks,
Maik

Hi Maik,
You should filter for alpha <= 0.95. alpha in the summary table is actually the minimum coverage level required for a SNP to be included in the credible set. That is if alpha=0.5  the SNP would be included in any credible set with target coverage >50%, and if alpha = 0 that means it's the top SNP in the component, and thus the first SNP to be included in any credible set.
If you filter alpha <= 0.95 and then sum over pi within each top_component, it should be close to 0.95.  It could be a bit more (e.g a credible set with two SNPs with pi=0.5 will have pi sum to 1).
It could also be a bit less. This is because the variant report file only reports information on the top component for each SNP (largest pi). If a SNP is included in the 95% credible set of two components, it will only show up for the component with larger pi. This situation should only happen for SNPs on the fringe of being included in a CS, and if it's happening to an appreciable proportion of SNPs in a given component, that's a good indication that it is a low quality component that is not capturing appreciable signal.
The variant report file maps each variant to its top component (the component which has the highest pi). All SNPs get mapped to exactly one component. So getting assigned to a component doesn't mean much, but having a large pi/ small alpha does.
Hope that helps! Let me know if there is anything else I can help with.
Best,
Karl

Hi Karl,
Thanks for your quick answer. It was entirely my fault missing the explanation! Just to be completely clear, this would then also imply to drop each component that does not sum up to 95% in the pi column?
Thanks,
Maik

Thanks, Karl. I will follow your advice. Thanks so much for your guidance on my somewhat ignorant questions.
Cheers,
Maik


[Debugger] Add variable visibility test for function returned values and their assigned variables

Description:
We need to add variable visibility test for function returned values and their assigned variables
Related issue https://github.com/ballerina-platform/ballerina-lang/issues/31385
Consider the below code segment:
public function main() {
    int a = getNumber(); // Add a debug point here
}

function getNumber() returns int {
    return 123;
}

Closing with https://github.com/ballerina-platform/ballerina-lang/pull/32035


Show a warning when building APK/AAB with unsupported architecture

See https://github.com/flutter/flutter/issues/37566 and https://github.com/flutter/flutter/issues/59501.
It's possible for users to end up adding their own native libraries in their Flutter Android project's gradle. If the user ends up adding an x86 .so to their project, the APK will be installable on x86 physical devices, cause it to skip the ARM emulation and crash when trying to load Flutter since there are no flutter .so.
In flutter.gradle, we should look for the presence of native libraries in the APK with unsupported architectures and show a warning to prevent this subtle crasher.
cc @jmagman @blasten @chinmaygarde

Agreed that this can cause subtle issues and a warning is necessary. Some other thoughts/ideas:

Explicitly specify the architectures in Gradle files generated from the templates (Not sure how this will play with the architectures specified on the command line).
Cause builds the fails by inspecting the APK post packaging to see if there are dylibs for architectures other than those supported by Flutter and/or specified on the command line.

I wonder if AGP has a hook to verify that. You might want to get input from the AGP team. I can see this causing race conditions, but there might be a way to work around those.


Some files in tests/target/ don't exist in tests/source/

Easy way to improve test coverage: add a bunch of corresponding files to source/ .
@@ -1,10 +1,14 @@
 assignment.rs
+attrib-extern-crate.rs
 attrib.rs
 chains-no-overflow.rs
+chains-no-overlow-2.rs
 chains.rs
 closure.rs
+comments-fn.rs
 doc.rs
 empty_file.rs
+enum.rs
 expr-no-hints.rs
 expr.rs
 extern.rs
@@ -14,14 +18,17 @@
 fn-custom-5.rs
 fn-custom-6.rs
 fn-custom.rs
+fn.rs
 fn-simple.rs
 hard-tabs.rs
-hello2.rs
 hello.rs
 imports-reorder.rs
 imports.rs
+issue-64.rs
+long-fn-1.rs
 loop.rs
 macros.rs
+match.rs
 mod-1.rs
 mod-2.rs
 multiple.rs
@@ -30,9 +37,13 @@
 other.rs
 paths.rs
 single-line-if-else.rs
+skip.rs
+string-lit-custom.rs
 string-lit.rs
 struct_lits_multiline.rs
 struct_lits.rs
 struct_lits_visual_multiline.rs
 struct_lits_visual.rs
 structs.rs
+trait.rs
+tuple.rs

This is somewhat by design - they are designed to be used for idempotent tests.
It would be pretty easy to make source->target tests by taking the target files and removing (nearly) all whitespace. The hard bit is then undoing this where we aren't perfect yet.

I'll close this since this was intentional as @nrc mentioned.


Linting

This should:

setup linting to match the isomorphic-lib-template
get all code into compliance
make a pre-commit hook to:

check any staged files for lint errors
run all unit tests

@dmitrizagidulin how would you like us to continue with this? Would you like us to rebase and commit, or is that something the DCC would like to lead on?

@stuartf Hey Stuart, did you want to merge it in to main?

@jchartrand sure, I can merge this myself, I just didn't want to step on any toes if that wasn't the way you expected it to happen.

@stuartf Is it okay with you if I squash the 5 commits and then merge?

@jchartrand yes, I'm fine with you squashing the commits and merging, go for it


Implement the new API

This API aims to simplify usage and fix bugs (such as random_init being
set wrong) by removing as many arguments as possible from the API.
In the process, it makes using metaworld potentially much more
efficient.
However, this changes breaks the old API.
It also does not fix the goal being re-sampled on reset when
random_init=True.

I'm confident this change isn't complete, but I think this is in fairly good shape for our own use.
I broke the old API by implementing this. They could be made compatible again, but I'm not sure how important that is.
The "random_init resamples goal on reset" bug should definitely also be fixed, although I think that's in another PR @avnishn is working on, that should be compatible with this one.
The tests need to be fixed, but the new one which tests the entire new api passes.

There also isn't yet proper checking that set_task has been called on an environment, but that's fairly easy to fix.

There are potentially users who are using the old API for their June deadlines. Perhaps we should push this on to a new branch for our own use, then phase it in after the june deadline has passed.
We can also ping the mailing list to let them know of the new API that is on another branch, so that they can make the decision for themselves.

Does this preserve the current random_init behavior for all benchmarks? As it stands today, some environments are initialized with random_init=True or random_init=False for some benchmarks. Most default to True almost all the time.

No, it sets them all to False, currently.

This change is no longer relevant, since it was superseded by #143


Cannot add select options (1.0 release branch)

For select fields it comes with three options by default. I can rename these options and delete these options but the adding option button doesn't do anything. It is not possible to get 4 or more options.

@dtorres-sf This is an issue with the current release. Fixes will be included in the next release.

@kevinchappell The latest 1.0 allows more options to be added, but it still always only has at most 3 options in the schema output. It seems like it always has the first two options and the last option:

And the schema for the field shows:
    "270384b7-82a7-4786-aefa-5609dc4027fc": {
      "conditions": [
        {
          "if": [
            {
              "source": "",
              "sourceProperty": "value",
              "comparison": "==",
              "target": "",
              "targetProperty": "value"
            }
          ],
          "then": [
            {
              "target": "",
              "targetProperty": "value",
              "assignment": "=",
              "value": ""
            }
          ]
        }
      ],
      "tag": "select",
      "config": {
        "label": "Select"
      },
      "attrs": {
        "required": false,
        "className": ""
      },
      "meta": {
        "group": "common",
        "icon": "select",
        "id": "select"
      },
      "options": [
        {
          "label": "Option 1",
          "value": "option-1",
          "selected": false
        },
        {
          "label": "Option 2",
          "value": "option-2",
          "selected": false
        },
        {
          "label": "option 45",
          "value": "option-5",
          "selected": false
        }
      ],
      "id": "270384b7-82a7-4786-aefa-5609dc4027fc"
    },

OK I'll focus on that now. Thanks

@kevinchappell still seeing this on latest beta.

:tada: This issue has been resolved in version 0.7.18 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


please make a new release

Please make a new (pypi) release so swagger_test(extra_headers={}) option becomes available when installing the package via Pypi.
Thank you.

Done 😃


Bump sidekiq to 6.5.12

This resolves the security alert in https://github.com/alphagov/transition/security/dependabot/37.
Dependabot was unable to raise a PR to bump this gem, so I've done it manually.

We cannot upgrade beyond sidekiq version 6.5.5 as 6.5.6 requires redis <5 and we are already using version 5.
This will be resolved when we upgrade to Sidekiq 7.


Enable user tracking even if RUM is disabled in magento admin

I don't know if I'm missing something here but my understanding of this user tracking method is that it shouldn't depend on the RUM feature being enabled or not.

Ehm, you are completely correct. The last call though in that method is all about RUM, so that's why the check was there in the first place. In the mean time, all kinds of new stuff was added in the past (either by me or via other PRs) so this thing got mixed up. I will first merge your PR and then re-add the check but only for the last bit in the method. Many thanks!


[Adoption] Create a feature parameter

Critical Changes
Changes
According a conversation held  with @force2b, we need to merge this feature parameter used in Adoption in this sprint before we merge all the feature branch.
Issues Closed
Community Ideas Delivered
New Metadata
- Feature Parameter
    P10_Application_Date.featureParameterDate

Deleted Metadata

@dcaballeroSf The FP needs to be listed in the package.xml file

Yeap michael, my bad.


No results in positional filtering causes an error

IndexError: arrays used as indices must be of integer (or boolean) type
IndexError                                Traceback (most recent call last)
Cell In [15], line 1
----> 1 nus.filter_on_positions(SkyCoord(149.592500, -11.059722, unit='deg'), Quantity(10, 'arcmin'))
2 # nus.filter_on_positions(SkyCoord(74.775833, 8.780278, unit='deg'), Quantity(10, 'arcmin'))
File ~/code/DAXA/daxa/mission/base.py:39, in _lock_check..wrapper(*args, **kwargs)
34 @wraps(change_func)
35 def wrapper(*args, **kwargs):
36     # The first argument will be 'self' for any class method, so we check its 'locked' property
37     if not args[0].locked:
38         # If not locked then we can execute that method without any worries
---> 39         change_func(*args, **kwargs)
40     else:
41         # If the mission is locked then we have to throw an error
42         raise MissionLockedError("This mission instance has been locked, and is now immutable.")
File ~/code/DAXA/daxa/mission/base.py:674, in BaseMission.filter_on_positions(self, positions, search_distance)
670 pos_filter = np.zeros(self.filter_array.shape)
671 # The which_obs array indicates which of the entries in the table of observation info for this mission are
672 #  matching to one or more of the positions passed. The list(set()) setup is used to ensure that there are
673 #  no duplicates. These entries in the pos_filter are set to one, which will allow those observations through
--> 674 pos_filter[np.array(list(set(which_obs)))] = 1
675 # Convert the array of ones and zeros to boolean, which is what the filter_array property setter wants
676 pos_filter = pos_filter.astype(bool)
IndexError: arrays used as indices must be of integer (or boolean) type
Don't know yet if that's true of all the filtering methods, but I will check

This bug-fix should include an actually useful error where filtering has resulted in no observations being let through


Add a demo link to the readme

Ask user for a demo URL and display it in the readme (just below Homepage link)

I would really appreciate to do this as a good first issue, I will try and let you know the results thanks  :)

I have made a PR and all test cases have passed but one

greenkeeper/verify Expected — Waiting for status to be reported

What should I do about this one ? 😃
thanks in advance :)  I am enjoying contributing.


Image Upload

It would be really nice when we can upload images via url :D Thank you for sharing! Enjoy the coffee ;)

Thank you for the coffee. I will be adding extra functionality to this package soon and converting it to .NET Standard 2.0

@kshopper93 I have rewritten the whole thing and released version 2.0
Take a look at the readme now and please try it out and let me know what you think.
Paul

Perfekt! Thank you

Awesome to see. Thanks.


optional: add helpers for map index, channel receive, type assertion

Map index, channel receive, and type assertion expressions only return the extra boolean if dictated by the assignment. To use with optional.Value you must first assign to two variables, e.g.:
var m map[string]string
v, ok := m["foo"]
val := optional.Of(v, ok)

Instead, a helper could do the assignment internally and return the populated optional.Value, e.g.:
val := optional.OfIndex(m, "foo")

Also added OfPointer.


Nothing works

Describe the bug
So I download the plugin using: Plug 'michaelb/sniprun', {'do': 'bash install.sh'}. Then restart nvim then execute :Sniprun  --> nothing... no errors just nothing. OKAY. So now I execute :Snipinfo --> nothing... no errors just nothing.
Expected behavior
I just want my code to run
Environment:

Latest Neovim Nightly with linux Ubuntu machine and cargo installed.

yep, that's a known issue but I guess I should make it more obvious.
Silent fail is a consequence of the precompiled binary being incompatible with your system (sometimes uncommon distros or Mac) (are you on Mac?)
The new :checkhealth sniprun feature should provide solid clues about what went wrong. You arleady have the rust toolchain installed, so I recommend you compile the core sniprun binary locally: in order to do that, run either bash ./install.sh 1 or cargo build --release as install script, instead of bash ./install.sh

(also but I think you got this right or you'd have had a 'undefined command' error, but the shorthands are :SnipRun and :SnipInfo with capitals )

Silent fail is a consequence of the precompiled binary being incompatible with your system, for some reason I can't fully understand, but happens with Mac, or ARM machines, or i don't know.

I am actually on Linux(Ubuntu) so my guess is that you compiled it on arch for example and that made it incompatible on my distro, so maybe you can package it as an AppImage or build it for every distro using specialized tools (LXC-Containers ?).

yep, that's a known issue but I guess I should make it more obvious.

The new :checkhealth sniprun feature should provide solid clues about what went wrong. You arleady have the rust toolchain installed, so I recommend you compile the core sniprun binary locally: in order to do that, run either bash ./install.sh 1 or cargo build --release as install script, instead of bash ./install.sh

With all my respect, I don't think making it obvious is the correct solution here (although could be part of the solution). Instead of telling the user to compile the program on his machine, it should check if cargo is installed and then build the program directly within vim. I suggest you have a look at what vim clap does because I believe it is the correct way of handling such issue.

Your guess is right, though binary compatibility between contemporate distros is usually not an issue.
I got a look at vim-clap, but the build system is so incredibly complicated I don't know where to begin to replicate such a thing.
I don't think (unless some assumptions are challenged) I will provide such auto-compilation feature, because:

I can't test anything, because there are many various laptops/architectures/distros which will probably behave differently
The logic detecting whether the binary crashes at start is very, very far from perfect. Automating sniprun's compilation could have disastrous consequences (like recompiling everytime sniprun is launched even though the binary runs fine, but wasn't detected as such)

Oh god, I get it.
A very embarrasing typo indeed is the root cause of this issue, because otherwise binary compatibility between recent distros is a given ,right? Now fixed in v0.5.4, and regarding the anwser I provided earlier, I think this issue can be closed


[whatwg-node/server] Support for Next 13 API routes

Is your feature request related to a problem? Please describe.
I'm using Next 13 API routes.
Describe the solution you'd like
Mount a server in an API route.
Describe alternatives you've considered
I haven't.
Additional context
This is more of a question, I'm not using whatwg-node at this moment.

Closing the issue for now due to the lack of information.
What doesn't work currently?
Could you create a failing reproduction so we can see what is missing?
We can reopen after we have a reproduction.
Thanks!


Validation of LOINC display names

We have noticed today that the visualization tool is rejecting our messages when we send a LOINC code with a display name and the display name doesn't match one of the names expected by the server. If we leave the display name empty and send just the code, the message is successfully validated.

I have following questions related to this:

We believe that this kind of validation has been added very recently because we never noticed such kind of errors in the past. Can you confirm?
Are the laboratories expected to send the LOINC display names as part of the FHIR bundle or is allowed or advised to leave it empty and include only the code?
In case the display names are included in the messages, what is the reference database against which the tool is validating the names? The names published on loinc.org.
It seems that the tool always expects the LOINC display names to be in English even if the main language of the report is indicated to be Dutch or French. Can you confirm?

@frederic-istace ,
the conditions of the tests have not changed. At the moment we are facing a technical problem due to changes on the international terminology server.
The validation errors are invalid with respect to the agreements made in the HL7 Belgium Workgroup.
We are trying to find a solution.

Hello @bdc-ehealth , do you have an update about this international terminology server issue? We cannot validate our remaining test cases because of this.

@sebwautelet ,
On 11/11/2023, there was an upgrade on the international validator and in combination with an upgrade on the international terminology server on 16/02/2024, this causes the problems we are experiencing now. As there is no option to return to a stable situation (there are external components involved beyond our reach), we are working on a work-around. We hope to install it during next week, but as we are on unknown ground, we cannot guarantee a release moment.

For this issue please use the parameter display-warnings in the validator.
On Fri, Jan 26, 2024 at 1:30 PM Bart Decuypere (eHealth) <
@.***> wrote:

@sebwautelet https://github.com/sebwautelet ,
On 11/11/2023, there was an upgrade on the international validator and in
combination with an upgrade on the international terminology server on
16/02/2024, this causes the problems we are experiencing now. As there is
no option to return to a stable situation (there are external components
involved beyond our reach), we are working on a work-around. We hope to
install it during next week, but as we are on unknown ground, we cannot
guarantee a release moment.
—
Reply to this email directly, view it on GitHub
https://github.com/hl7-be/lab/issues/278#issuecomment-1911997913, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3HUUF6FAMIDXS7NHUH6Z3YQOOW5AVCNFSM6AAAAABB6U44NSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMJRHE4TOOJRGM
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

@sebwautelet @frederic-istace
There is a workaround for the "Wrong Display Name" problem. As you can see, the validation rules have become more strict since 11/11/2023. Due to a combination of factors, we could not stick to the older version of the validator, and we have had to upgrade. However, to keep the situation for this project stable, we will still accept files complying with the older rules, but we will display an additional warning sign. Further communication will indicate when the new international rules will be enforced for the lab project.

@bdc-ehealth
Do you know where we can find more information about these new international validation rules?
I just tried to upload an older test message to the visualizer and get a lot of error messages like this one that I never saw before:
Can't find 'Patient/1d23f18f-21d4-4615-b06c-fdad31767fd8' in the bundle (Composition.subject). Note that there are 1 resources in the bundle with the same type and id, but they do not match because of the fullUrl based rules around matching relative references (one of urn:uuid:1d23f18f-21d4-4615-b06c-fdad31767fd8)
It's not very clear to me what they mean by "the fullUrl based rules around matching relative references". So, any help would be welcome.

To clarify, these are not new international rules, they were there from the
beginning, we just didn't follow them, and more recently this became
visible on the validator.
There hasn't been any change to the rules.
On Fri, Feb 2, 2024 at 5:07 PM Bart Decuypere (eHealth) <
@.***> wrote:

@frederic-istace https://github.com/frederic-istace ,
It basically amounts to the fact that you cannot longer use a relative URL
of type 'Patient/1d23f18f-21d4-4615-b06c-fdad31767fd8' in the fullUrl
field, but that you must use the urn (which is a full URL)
urn:uuid:1d23f18f-21d4-4615-b06c-fdad31767fd8 in the fullUrl field. But as
you can see, we will not fail messages that do not do so until further
notice.
—
Reply to this email directly, view it on GitHub
https://github.com/hl7-be/lab/issues/278#issuecomment-1924176046, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3HUUGUJ5QWS2KLKBQAZ73YRUFLDAVCNFSM6AAAAABB6U44NSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUGE3TMMBUGY
.
You are receiving this because you commented.Message ID:
@.***>

thanks.
Please consult with Bart for the next actions;
I am just clarifying that the validator has been imposing stricter
terminology constraints for a while now, but it was never OK to use a
relative URL in the fullURL element.
On Fri, Feb 2, 2024 at 5:51 PM frederic-istace @.***>
wrote:

@bdc-ehealth https://github.com/bdc-ehealth @costateixeira
https://github.com/costateixeira
Thank you for the clarifications. We will fix this in the next patch of
our interface to be ready for later.
—
Reply to this email directly, view it on GitHub
https://github.com/hl7-be/lab/issues/278#issuecomment-1924261725, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AD3HUUC6GDIAKPSQCDJFIZLYRUKSFAVCNFSM6AAAAABB6U44NSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTSMRUGI3DCNZSGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

@bdc-ehealth
I have been able to get rid of all the error messages containing the text "fullUrl based rules around matching relative references" by replacing all the references into our bundle as follow:
"reference": "Organization/64b9f4ab-8cef-44cf-acfb-10fa6075992c"
-->
"reference": "urn:uid:64b9f4ab-8cef-44cf-acfb-10fa6075992c"
However, I now get following error for every message I try to upload to the visualizer https://fhir-testserver.be/index.php/visualization_webapp:

I don't really what's wrong with the patient identifier included in the bundle. So, I'm wondering if this is really a problem with my test message or a bug in the new version of the validator?
Example of a file related to test case 2F2 which is producing this error:
82470091998_013G050038_l_2_MOLIS_4.json
This same file is still passing validation on the test server fhir-testserver.be

@frederic-istace ,
we will track this one here: https://github.com/ehealthplatformstandards/laboResultVisualization/issues/39


update for Azure CLI output message

Response now includes "zones".  It looks like:
"resourceGroup": "myResourceGroup",
"zones": ""
}

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

ID: 0e84d074-09a8-4b15-243a-de80ebe797d8
Version Independent ID: 99f1dea0-4c3f-e25b-e778-24ca2a2bc5d2
Content: Create a virtual network - quickstart - Azure CLI
Content Source: articles/virtual-network/quick-create-cli.md
Service: virtual-network
GitHub Login: @jimdial
Microsoft Alias: jdial

@PHBeagle Thanks. I added zones to the output. It will publish later today. #please-close

@PHBeagle We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Deployment target changed to iOS 10.0

Hi,
I noticed the deployment target was changed to iOS 10.0. Is there a reason for this? I'm still targeting iOS 9.0 so now I can't use your lib anymore.
Thx!

Please consider this as bug! I'll try to push a quick fix next week.

any update on this?

Thanks so much!


Disabling in config does not disable

Weapons still show up in NEI/JEI and are completely craftable even when disabled in the config

Config properties for weapons aren't being loaded early enough. I've fixed that locally, but I'll need to do some more work tomorrow to remove disabled weapons from JEI and the creative inventory.


Jest Testing Tools

ToDo

[x] add general jest bindings
[x] export react/preact/inferno tools

Description
Introducing a general tool to create snapshots that include both rendered CSS and HTML markup in a minimal, formatted output.
Example
import { createSnapshot } from 'jest-react-fela'

describe('Rendering Fela components', () => {
  it('should render correctly', () => {
    const snapshot = createSnapshot(
      <FelaComponent style={{ color: 'blue' }} />
    )

    expect(snapshot).toMatchSnapshot()
  })
})

.a {
  color: blue
}

<div className=a />

Versioning

Major

jest-react-fela
jest-preact-fela
jest-inferno-fela
jest-fela-bindings

Minor
Patch
Checklist
Quality Assurance

You can also run yarn run check to run all 4 commands at once.

[x] The code was formatted using Prettier (yarn run format)
[x] The code has no linting errors (yarn run lint)
[x] All tests are passing (yarn run test)
[x] There are no flow-type errors (yarn run flow)

Changes
If one of the following checks doesn't make sense due to the type of PR, just check them.

[x] Tests have been added/updated
[x] Documentation has been added/updated
[x] My changes have proper flow-types

SWEET! I of course built something exactly for this for internal use at the end of June only to see your PR go up in early July. ;)

Haha. Same here! We built it at work and now I wanted to share it as I was also using something like that to improve the snapshot tests we use to test felas' APIs itself =)


Add perimeter functions

Thanks for the additions! I added a few notes inline.

Looks good! Could you also extend the read me with your additions?

Changes have been made based upon the suggestions. :+1:

Awesome :tada:


KOGITO-9455: Create the getting started guide to describe how to run …

…workflow projects
@ricardozanini could you please suggest if all-together in one file is OK, or if we should split some parts to different sections. Imho keeping it in one file like this makes it easier for users not familiar with our docs.
Just the getting started guide a follow-up guide where we expand the hello-world workflow with supporting files is required imho. Will be done as part of  - https://issues.redhat.com/browse/KOGITO-9457
Adds new file with guide containing create, run and deploy showcases to begin development of SonataFlow project using operator first approach.

JIRA:KOGITO-9455

Description:
Adds new file with guide containing create, run and deploy showcases to begin development of SonataFlow project using operator first approach.

Please make sure that your PR meets the following requirements:

[x] You have read the contributions doc
[x] Pull Request title is properly formatted: KOGITO-XYZ Subject
[x] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[x] The nav.adoc file has a link to this guide in the proper category
[x] The index.adoc file has a card to this guide in the proper category, with a meaningful description

How to backport a pull request to a different branch?

In order to automatically create a backporting pull request please add one or more labels having the following format backport-<branch-name>, where <branch-name> is the name of the branch where the pull request must be backported to (e.g., backport-7.67.x to backport the original PR to the 7.67.x branch).

NOTE: backporting is an action aiming to move a change (usually a commit) from a branch (usually the main one) to another one, which is generally referring to a still maintained release branch. Keeping it simple: it is about to move a specific change or a set of them from one branch to another.

Once the original pull request is successfully merged, the automated action will create one backporting pull request per each label (with the previous format) that has been added.
If something goes wrong, the author will be notified and at this point a manual backporting is needed.

NOTE: this automated backporting is triggered whenever a pull request on main branch is labeled or closed, but both conditions must be satisfied to get the new PR created.

@ricardozanini thanks, fixing!

@ederign can you or someone from tooling please review?


Create benchmark for extension field

Field
Square(ns)
Inv(ns)
Mul(ns)

BinomialExtensionField<BabyBear, 4>
15.879
152.17
15.660

BinomialExtensionField<BabyBear, 5>
24.375
204.92
24.498

BinomialExtensionField<Goldilocks, 2>
9.3334
177.79
9.5519

QuadraticBef<Goldilocks>
6.1542
147.14
7.4340

BinomialExtensionField<Mersenne31Complex<Mersenne31>, 2>
29.572
122.02
30.772

QuadraticBef<Mersenne31Complex<Mersenne31>>
22.785
72.547
26.657

BinomialExtensionField<Mersenne31Complex<Mersenne31>, 3>
70.264
295.85
73.039

CubicBef<Mersenne31Complex<Mersenne31>>
42.416
134.82
62.071

As https://github.com/Plonky3/Plonky3/pull/151#issuecomment-1752197239 suggested, we can optimize the result by adding to cargo.toml
[profile.release]
lto = "fat"
codegen-units = 1

Field
Square(ns)
Inv(ns)
Mul(ns)

BinomialExtensionField<BabyBear, 4>
14.094
158.38
13.978

BinomialExtensionField<BabyBear, 5>
21.609
215.81
22.232

BinomialExtensionField<Goldilocks, 2>
1.5406
140.62
1.6737

QuadraticBef<Goldilocks>
1.3471
136.75
1.546

BinomialExtensionField<Mersenne31Complex<Mersenne31>, 2>
8.2529
75.858
8.1932

QuadraticBef<Mersenne31Complex<Mersenne31>>
0.25872
51.492
0.257

BinomialExtensionField<Mersenne31Complex<Mersenne31>, 3>
20.895
119.47
20.883

CubicBef<Mersenne31Complex<Mersenne31>>
0.38587
58.28
0.38696

Thanks for updating, I think something seems funny with Mersenne31Complex<Mersenne31>. The times you got for its QuadraticBef and CubicBef would be roughly a single cycle on most CPUs; seems too good to be true.
On my M1 I'm getting more expected times, like
(default config)
BinomialExtensionField<Mersenne31Complex<Mersenne31>, 3> mul
                        time:   [59.334 ns 59.379 ns 59.433 ns]
CubicBef<Mersenne31Complex<Mersenne31>> mul
                        time:   [50.086 ns 50.157 ns 50.246 ns]

(lto = "fat", codegen-units = 1)
BinomialExtensionField<Mersenne31Complex<Mersenne31>, 3> mul
                        time:   [60.561 ns 60.832 ns 61.162 ns]
CubicBef<Mersenne31Complex<Mersenne31>> mul
                        time:   [50.965 ns 51.154 ns 51.382 ns]

Oh my mistake, I hadn't actually changed the config, after doing so I also see those extremely fast times. Will look into it.

Looks like we need to black_box the inputs, or use bench_with_input which does that for us; then the times with lto = fat look realistic.

After further adding black_box func the final benchmark are as following:

Field
Square(ns)
Inv(ns)
Mul(ns)

BinomialExtensionField<BabyBear, 4>
15.014
160.74
15.980

BinomialExtensionField<BabyBear, 5>
22.061
215.68
22.121

BinomialExtensionField<Goldilocks, 2>
2.6672
142.72
2.8484

QuadraticBef<Goldilocks>
2.2181
139.48
2.7713

BinomialExtensionField<Mersenne31Complex<Mersenne31>, 2>
9.1203
78.040
9.96

QuadraticBef<Mersenne31Complex<Mersenne31>>
6.3807
60.707
9.6052

BinomialExtensionField<Mersenne31Complex<Mersenne31>, 3>
29.893
129.17
30.799

CubicBef<Mersenne31Complex<Mersenne31>>
11.749
75.907
17.760

quadratic provide a 20~30% gain for Mersenne complex and cubic provide a 40~50% gain

@dlubarov @unzvfu, there is one last thing we need to decide. Should we keep the qudraticBef and cubicBef for mersenne31Complex?

@dlubarov @unzvfu, there is one last thing we need to decide. Should we keep the qudraticBef and cubicBef for mersenne31Complex?

Personally I vote to remove them. I think if we ever need a faster implementation of an extension of Mersenne31Complex, then it would make more sense to implement that special case directly, rather than using QuadraticBef or CubicBef.

I'd vote to remove also. I think if we experiment with tweaks to BinomialExtensionField we can probably get the compiler to generate the same code for both; e.g. we could rewrite it to avoid 0 + something, or worst case we could write match D { ... } in a few places.


Fix for CharacterAI api

This will fix all errors for now.

Requests don't need any additional headers other than authorization. The 403 error occurred because some tls_client identifiers were blocked


feat: Added stale-issue handling

Description
Runs a stale-issue check every night. Only cares about issue that has label Besvart, every other issue is ignored. This lets us incrementally add the label when we discuss them at issue meetings, and/or write a response asking for further follow-up.

Gets "stale" after 120 days
Closed 30 days after stale (so 120 + 30 days)

What happens if someone e.g. writes a comment after it's marked as stale? Will the label be removed, or will it be closed after 30 days of last activity?


Reduce npm package size.

Hi, @samme, @photonstorm.
I'm sending this PR as a proposal to make some adjustements to the Phaser CE package. It is not a big change (just only an additional file), but it changes the contents distributed through npm. I'd like to ask you to review this change carefully. I am able to update this PR, if requested.
The problem is that phaser-ce package is too big, much because it includes contents not relevant for a npm package. Right now, running npm pack . against the master branch will create a TAR+GZIP archive which sits at around 36MB of size, ~96MB uncompressed ─ Think of npm pack as a "dry-run mode" of npm publish.
My proposal is to remove, among other things:

The resources folder, which contains miscellaneous files;

The Grunt tasks, because it is unusual (and unpractical) to keep those files in a distribution package;

The documentation folder, because it is more convenient to read it either using a repository clone or the GitHub page.

With these changes applied, the package size should be reduced to around ~9.6MB, and ~33MB uncompressed, around 1/3 of the original size but still a little big because of all source maps and a few duplicate files under build/custom, which you should check later.
One question I have is about the filters/ folder, which contains some useful content. I opted to keep those files in the package, but I wonder how users are consuming those files. Perhaps those files should be published as a separate package.

References:

npm-pack
npm-developers § Keeping files out of your package

/resources and /docs can be definitely be excluded.
/src and /tasks are needed (together) only for custom builds.
I used to include filter files as needed from bower-installed phaser, which was convenient.

Ok, updated to keep Grunt tasks in the package.


New patch release of Golang: v1.21.5

Update EKS Go Patch Version: v1.21.5-6
SPEC FILE STILL NEEDS THE '%changelog' UPDATED
PLEASE UPDATE WITH THE FOLLOWING FORMAT
* Wed Sep 06 2023 Cameron Rozean<EMAIL_ADDRESS>- 1.20.8-1
- Bump tracking patch version to 1.20.8 from 1.20.7

/approve


Added RawBodyParser for BodyParser default parsing method (#908).

BodyParser should default a ParsedBody.raw(Data) when the Content-Type isn't known.
Description
BodyParser has a parserMap which designates that text-based Content-Types correspond to a specialized parser (e.g., application/json -> JSONBodyParser).
If the Content-Type was not any of those types, it would fall-through and nil out the data from the RouterRequest instead of storing the raw data in .raw(Data) on ParsedBody.
I fixed this by following pattern and creating RawBodyParser which just slots the data into .raw(Data). BodyParser now defaults to passing the RouterRequest body into RawBodyParser.
Motivation and Context
This is in response to Issue 908. While exploring @rfdickerson's Kitura Protobuf Sample, I notice that POSTing did not work when sending a protobuf file. The RouterRequest's body was nil not application/json. @rfdickerson assumed, as I would have, that the body could have been accessed using .raw(Data) on the ParsedBody. This was not the case.
How Has This Been Tested?
I wrote a unit test that tests whether raw data being sent passes through the router properly and can be accessed using .raw(Data).
I only ran tests locally on Mac OS X since I do not have access to a Linux environment immediately.
This would only have impact on existing code if the end user knew that BodyParser would nil out the body and wrote against that scenario.
Checklist:

[x] I have submitted a CLA form
[x] If applicable, I have updated the documentation accordingly.
[x] If applicable, I have added tests to cover my changes.

Realized the arc4Random isn't available on Linux. I'll update shortly.

Thanks for your PR! Please don't use random data in the test. It makes recreating any future failures theoretically impossible.

@ianpartridge would a Data object filled with zeros be better? The point is that raw data is coming through. Don't care what but just that the length is the same. Should I be testing for something else?

If you can test the same thing using just zeroes then please do that :)

@ianpartridge Will do! Thanks!

All zeros sounds to me like an edge case.... maybe have another test with statically generated random data?

@ianpartridge Updated!

Thanks for your work on this, @jacobvanorder!

@ianpartridge I'd love to chip in more. Is there a standard for picking off issues or is it anything that isn't assigned is fair game?

Hi @jacobvanorder.  Any issue that isn't assigned is available - let us know if a particular one looks interesting.  Is there a particular area of Kitura that you've been investigating or using?  If you are looking for a standalone feature to work on, we'd love Kitura-Credentials to support more providers (currently we have Facebook, Google and GitHub).  How about creating Kitura-Credentials-Twitter so Kitura apps can provide login through the Twitter OAuth API?

@ianpartridge Thanks for the direction!
I came to this issue after investigating Protocol Buffers and @rfdickerson's example for a talk I'll be doing in the spring. I've been trying to frame the depth of what I get into concerning Kitura balanced with my time limit for the talk.
I'll take a look at Twitter OAuth and contribute how I can. This has been really fun to delve into and I'm happy to work on something new.

Sounds good - let us know how you get on!

The information to set a custom Content-Type could be helpful.
I didn't set it and it the parser will return here ;)
I use now: "custom/row" and it works well :)
if let parser = parserMap[contentTypeWithoutParameters] {
return parser


ARROW-9183: [C++] Fix build with clang & old libstdc++.

See https://issues.apache.org/jira/browse/ARROW-9183# for further details & discussion.

Hmm, there's a failure building with GCC 4.8 https://github.com/apache/arrow/pull/7493/checks?check_run_id=791725319#step:9:534
The #ifdef condition seems to be failing to detect too-old libstdc++

Got it. It seems that the gcc 4.8.5 is released later than gcc 4.9.2 & gcc 5.1. I'll take a future investigation on how to detect the missing of std::atomic_load overloads.


Update README-id.md

Update readme translation to reflect  fb99efb3

Continued in #10 . Reason: was using default github editing feature.

That is not a reason to abandon a PR.

@jayvdb The email address used in the pr was not mine. It was github emails. I though by fetching and ammending the changes i will be able to retain my email address, but it wasn't. On #10, apparently, it is still using<EMAIL_ADDRESS>Which is far from what i itended.

That is because you dont have a public email address in your GitHub profile.
But it isnt necessary.  You can use git commit --amend --author="...."

It will fix https://tree.taiga.io/project/jayvdb-wikimedia-idanak-pulau/task/17 when merged


Session  View

WIP - placeholder for a system level viewer of all interop session state.

@sebbenmbarek  the 'UI' is just a WIP.  I have some ideas on how to visualize that I'm going to take a pass at.  Would rather get a placeholder in now and try to keep the PRs as small as possible.  Not sure why reload is breaking things for you (it generally doesn't for me).  Though, in general, HMR does not work right on changes to renderer and preload - this has been an ongoing problem with HMR in the setup (not sure if this is a Vite, React, Electron, or Sail thing).  Definitely something well worth figuring out.


TTVLOL v2 Proxy Support

https://github.com/younesaassila/ttv-lol-pro
It looks like the original ttvlol api has been taken down. I've been getting 500 internal server error for the past week or so. I tried the alternate proxies mentioned here and here using the --twitch-proxy-playlist flag but none of them work

Try luminous-ttv. Either host it yourself or try the eu public url. https://eu.luminous.dev
It was linked in the readme.md but likely removed to make things less confusing.

Try luminous-ttv. Either host it yourself or try the eu public url. https://eu.luminous.dev
It was linked in the readme.md but likely removed to make things less confusing.

--twitch-proxy-playlist=https://eu.luminous.dev
That works for me, thanks


added introductory notebook (first draft) with cosyne tutorial included

Fixes #4

@synek can you quickly check this merge won't mess with yours and then go ahead and merge it in?

Even though it's the same directory structure, the two PRs would conflict because they each have a different lineage of commits! But if you change this PR to point to my branch (instead of main), then it should work and we can merge it into my branch.
Do instead of main <- thesamovar, it'll be rory/structure <- thesamovar.

(you do it by clicking the edit button up at the title of the PR)

OK I'm going to make a few other changes quickly separately and let's deal with that tomorrow.


site crashes when midway through adding a sponsor

duplicate of #1, I think -- both a side effect of a sponsor not having images attached? although it makes the non-dashboard pages crash, the dashboard and admin seems to continue working


balena-linux-firmware: Do not compress non-binary txt files

Some device types like the RaspberryPi place non-firmware files under
/lib/firmware. This commit skips compression for them.
Change-type: patch
Signed-off-by: Alex Gonzalez<EMAIL_ADDRESS>

@balena-ci rebase

@balena-ci rebase

@balena-ci I self-certify!


Can't configure network interface to listen on

I followed the instructions to set up mailin, and I can get it to listen on localhost:
$ telnet localhost 25
Trying ::1...
Trying <IP_ADDRESS>...
Connected to localhost.
Escape character is '^]'.
220 localhost ESMTP Mailin Smtp Server

But it isn't listening on my actual public IP:
$ telnet <IP_ADDRESS> 25
Trying <IP_ADDRESS>...
telnet: Unable to connect to remote host: Connection refused

Perhaps I configured it wrong. But I've also noticed that my server is perhaps configured to think that is name is localhost:
$ echo $HOSTNAME
localhost

Is there something to do to fix my server config? Can't I just tell mailin "Hey, listen on interface eth0!"?

I suspect it to be due to some network configuration issue rather than to mailin. Is your machine behind any router? To be sure it holds this public IP, can you post the output of ifconfig?
Le 28 décembre 2015 10:15:04 UTC+01:00, Michael Toomim<EMAIL_ADDRESS>a écrit :

I followed the instructions to set up mailin, and I can get it to
listen on localhost:
$ telnet localhost 25
Trying ::1...
Trying <IP_ADDRESS>...
Connected to localhost.
Escape character is '^]'.
220 localhost ESMTP Mailin Smtp Server

But it isn't listening on my actual public IP:
$ telnet <IP_ADDRESS> 25
Trying <IP_ADDRESS>...
telnet: Unable to connect to remote host: Connection refused

Perhaps I configured it wrong. But I've also noticed that my server is
perhaps configured to think that is name is localhost:
$ echo $HOSTNAME
localhost

Is there something to do to fix my server config? Can't I just tell
mailin "Hey, listen on interface eth0!"?

Reply to this email directly or view it on GitHub:
https://github.com/Flolagale/mailin/issues/75

Thanks, but there was no problem in the network. The problem was, in fact, that mailin was listening on the wrong interface.
I fixed this by looking at the source code, finding where mailin tells smtp-server which network interface to listen on, and seeing that you can configure this with the host parameter in:
mailin.start({
   host: "<IP_ADDRESS>",
   port: 25,
   // etc...
})

This should go in the documentation.

The same problem. Mailin starts on the local interface, instead external.

@pomeo, did you read the fix?

On Dec 29, 2015, at 7:07 AM, Sergey Ovechkin<EMAIL_ADDRESS>wrote:
The same problem. Mailin starts on the local interface, instead external.
—
Reply to this email directly or view it on GitHub.

@toomim Yes. Only from the command line it doesn't work. Because there is no --host.
Not from the command line of course works with "host:"

+1 Had trouble with this after updating to the latest release also, as it is an undocumented change and also breaks the example in the readme. Used to work without any configuration.

+1 same here, I'm using it from the command line and it's binding the <IP_ADDRESS> ip I can't get it to bind the <IP_ADDRESS> from the command line so until a fix is release to add a --host The only solution I see is to embed mailin into an small app to be able to configure the host like @toomim did...

Created a pull request which should restore the functionality of the previous version, while allowing the host configuration to be set if required. This also adds the functionality to the cli.

@janbialostok, it looks like it was a host issue (in relation to #77 )

@tomforster provided a fix by allowing the host configuration to be set from the command line. It is published as<EMAIL_ADDRESS>


revert regex related linting

My apologies that Varnish regular expression is not compatible for Golang's regexp package.
It causes:
if (req.url ~ "^/([^\?]*)?(\?.*)?$") {
...
}

Then raises [ERROR] regex string is invalid, error parsing regexp: invalid or unsupported Perl syntax: (?.
I assume that VCL regular expression is using Perl syntax but Golang does not have it... so I revert these changes 😢

Temporary revert this change. I guess it may fix by escaping back-slash.
"^/([^\?]*)?(\?.*)?$" does not seem Perl syntax, just matches ? character 🤔

I think you're right. Can regexp.QuoteMeta help here?
https://pkg.go.dev/regexp#QuoteMeta

Thanks, I think that function also escapes other meta characters like [.
Simply we can replace escape back-slack like strings.ReplaceAll(regexString, "\\", "\\\\").

Ah, I misunderstood the point. Sounds good.


Is there a way to catch 404 error ?

FYI for anyone else looking I got this working with this:
  const fetchFont = async (fontName: string) => {
    try {
      const promise = new Promise((resolve, reject) => {
        WebFont.load({
          google: { families: [fontName] },
          active: () => resolve("true"),
          inactive: () => reject("404"),
        })
      })
      await promise
      .....
    } catch (err) {
      console.log("HAS ERR", err)
      .....
    }
  }


chore: created a modal for 'update version' popup, if clicked skip, doesn't appear again until next version

[Inspired from PR #269 discussion]
features:

SweetAlert2 modal (instead of an 'alert dialog which is a blocking action')
If clicked 'skip' on the modal, the skipped version is stored locally, the modal doesn't appear until there is a newer version released other than the skipped version.
there is a default 5-second timer, it dismisses if there is no interaction, and can be changed/disabled from the config mentioned below.
can be disabled at the start of the script:

// Enable custom modal
    const updateModal = {
        enable: true, // if true, replaces default window popup with a custom modal
        timer: 5000, // timer: number | false
    };

https://github.com/TheRealJoelmatic/RemoveAdblockThing/assets/74111241/95c1fd7a-7a9e-4925-90d4-aea053f8ce0c
ps: first time using tampermonkey, open for suggestions about the implementation

Great one !
But not a big fan of injecting scripts like that with a user script.
If you really want to do so, make it clear for the users and not "hidden" in the code: use @require (check https://www.tampermonkey.net/documentation.php?locale=en#meta:require)
Or maybe consider creating a modal with no dependency ? For one small modal should be fine.
Your script is 25kb, IMO it's not worth it for one modal.

Great work this looks amazing.

But not a big fan of injecting scripts like that with a user script. If you really want to do so, make it clear for the users and not "hidden" in the code: use @require
last point: if the CDN is down, maybe you should consider a fallback. It could be possible that your script is no longer available, since it's not bundled in the repo. You can use the callback script.onerror.

Hey, thanks for the comment. Although also not a fan of injecting the script, I think I had a problem calling the modal function when I used @require, so did that instead.. And in that way if the modal is disabled by the user, they don't need to fetch for the script, only fetch when enabled. I agree on making it more clear, so I added a comment to the config part instead.