teamspeak_server: 3.9.1 -> 3.10.1

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/teamspeak-server/versions.
meta.description for teamspeak_server is: '"TeamSpeak voice communication server"'.
meta.homepage for teamspeak_server is: '"https://teamspeak.com/"

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 3.10.1 with grep in /nix/store/i66v60ahy396bh19926h8272lyplb3xr-teamspeak-server-3.10.1

directory tree listing: https://gist.github.com/6c8629eb45ae18df494597167a545fd4

du listing: https://gist.github.com/f1a1f4cae4263e48251a65a85e54a393

Rebuild report (if merged into master) (click to expand)

3 total rebuild path(s)
1 package rebuild(s)
1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
teamspeak_server

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/i66v60ahy396bh19926h8272lyplb3xr-teamspeak-server-3.10.1 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A teamspeak_server https://github.com/r-ryantm/nixpkgs/archive/15f9494b4a51af9ba7840db11a3cad13a009e070.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/i66v60ahy396bh19926h8272lyplb3xr-teamspeak-server-3.10.1
ls -la /nix/store/i66v60ahy396bh19926h8272lyplb3xr-teamspeak-server-3.10.1/bin

cc @shados for testing.

New sha256 for 32-bit missing, see https://github.com/NixOS/nixpkgs/pull/75109

closed because of https://github.com/NixOS/nixpkgs/pull/75109


Restructure CLI README Page

Restructuring CLI README for general and dev information.

i'd personally like to stick with brew as mac primary as long as we get #549 finished in a reasonable amount of time.
rest of the changes are easy.

Bump. I need a review to merge. thanks.

Can we revert the brew install back to primary?

I'll swap em.

Updated.

Updated.


[SPARK-42143][UI] Handle null string values in RDDStorageInfo/RDDDataDistribution/RDDPartitionInfo

What changes were proposed in this pull request?

Similar to https://github.com/apache/spark/pull/39666, this PR handles null string values in RDDStorageInfo/RDDDataDistribution/RDDPartitionInfo
Why are the changes needed?

Properly handles null string values in the protobuf serializer.
Does this PR introduce any user-facing change?

No
How was this patch tested?

New UTs

cc @LuciferYang

Merged to master, @gengliangwang .

@dongjoon-hyun @LuciferYang Thanks for the review!


Quantum signal processing sample for Azure Quantum notebook gallery

This contributes a quantum signal processing sample based on Qiskit and IonQ to the Azure Quantum hosted notebook gallery.
Title: Quantum Signal Processing
Brief description: Evaluate polynomials using a single qubit and quantum signal processing.

I changed the target branch to main


update kubectl create commend in kubectl Usage Conventions page

Hi,
As I currently learn about k8s via k8s.io, I find that this page does not mention the current way to get the resource template and it only mentions some of the resources is deprecated in kubectl run
So, I think we should also update this page as well.
Best,
Alpha

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.
It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address.  Check your existing CLA data and verify that your email is set on your git commits.
If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at<EMAIL_ADDRESS>

signed

Thanks for your pull request. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please follow instructions at https://git.k8s.io/community/CLA.md#the-contributor-license-agreement to sign the CLA.
It may take a couple minutes for the CLA signature to be fully registered; after that, please reply here with a new comment and we'll verify. Thanks.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address.  Check your existing CLA data and verify that your email is set on your git commits.
If you signed the CLA as a corporation, please sign in with your organization's credentials at https://identity.linuxfoundation.org/projects/cncf to be authorized.
If you have done the above and are still having issues with the CLA being reported as unsigned, please log a ticket with the Linux Foundation Helpdesk: https://support.linuxfoundation.org/
Should you encounter any issues with the Linux Foundation Helpdesk, send a message to the backup e-mail support address at<EMAIL_ADDRESS>

plz check it again

/lgtm

@AlphaWong Thanks for the improvements! Some grammar nits, then LGTM.

thx for review. I updated it

@AlphaWong Thanks for the update. Please squash your commits so we can merge.

sure

@AlphaWong Thanks for the update. Please squash your commits so we can merge.

done

/lgtm
/approve


feat: expose Application attrs for App Discovery

What type of pull request is this?

[x] Non-breaking code change
[ ] Breaking code change
[x] Documentation change/addition
[ ] Tests change

Description
This simply exposes the tags and custom_install_url fields which were recently amended to the Application object when application discovery was announced. These also may have just been simply overlooked as well.
Side note: I've commented out another attribute missing, install_params which needs an object suited for it. I'm willing to implement said object for this PR if one desires
Changes

Added tags optional attribute for a list of string values
Added custom_install_url optional attribute for a string value

Checklist

[x] I've formatted my code with Black
[x] I've ensured my code works on Python 3.10.x
[x] I've tested my code

It also seems that there's a merge conflict for this file only when switching to naff branch too, FYI. No issues on dev branch if targeted.

Set install_params as a dict for now. The to-do to create the object stands. Better to at least leave the data accessible than discard it


docs: update the documented base image

:tada: This PR is included in version 0.16.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Add Horizon to DeltaV replays

New server that has been recording for a few days, but a misconfiguration meant they couldn't be reached publicly. There's a backlog of a few days

Thank you for your contribution.


Task.onlyIf should provide transitive avoidance

Gradle <= 6.8.2
Let's say we have tasks with the following dependencies
// the arrows mean A --depends on--> B
A --> B
       \
         -> E
       /
C --> D

If we add an onlyIf clause to B and this condition is false, Gradle should be able to skip both A & B when invoking task E. The current behavior is to only skip B, but still execute A.
Of course, there are some rare cases where the execution of A would influence the onlyIf condition on B, but they are rare. It would be nice to have an API to allow Gradle to make such a decision.
e.g.: B.onlyIfTransitive { <condition> } <<-- naming is a hard problem :D

@stephanenicolas , would you please use real-looking names instead of A B C D? Names like A B make it really hard to understand the intention
What do the tasks do, what command user issues, and what is the expected result?

@stephanenicolas , would you please use real-looking names instead of A B C D? Names like A B make it really hard to understand the intention
What do the tasks do, what command user issues, and what is the expected result?

We're also running into this over at Google.
For example;
We have a generateReleaseConfig task which figures out which projects in a multi-module project are opted into a release given some conditions and state.
We additionally have a publishRelease task which publishes the release artifacts for a given module. Although, this should only occur if the module is opted into a release (as discovered via generateReleaseConfig). Our ideal solution is something like this:
val releasingLibraries = generateReleaseConfig.map { it.releasingLibraries }
val imReleasing = releasingLibraries.map { it.contains(name) }

tasks.register("publishRelease") {
  dependsOn(imReleasing)
  onlyIf { imReleasing.get() }

  finalizedBy("publishReleasePublicationToRepo") // provided by AGP
  finalizedBy(...) // other release tasks
}

Although, this doesn't work- as the dependent tasks of publishRelease are still ran, even if the onlyIf causes the task to skip.
tl;dr -  wrapper tasks that are conditional given some Provider are perfect examples of where this becomes an issue.

Sorry for the late reply.
Thank you for your interest in Gradle!
This issue needs a decision from the team responsible for that area. They have been informed. Response time may vary.

The way Task.onlyIf() works now is unfortunately broken. As you demonstrated, a downstream task can still consume the excluded task's stale output. The plan is to disallow depending on excluded tasks, though this is not something that we will work on in the near future: https://github.com/gradle/gradle/issues/11100


Don't get into infinite loops with other bots

AgainstHumanity got into an infinite loop with another bot because:

AgainstHumanity sent an introductory message to the other bot when it joined a channel that AgainstHumanity was in.

That bot takes all private messages as requests to do a Google search, so it attempted to do a Google search for AgainstHumanity's whole introductory speech. It reported its results back.

AgainstHumanity then complained that this wasn't a valid command.

The bot then searched for AgainstHumanity's complaint and replied with the results of that.

Back to 3.

Pre-existing rate limiting in both bots at least reduced the exchange to one response per 5 seconds.
PAH should probably check the rate it is sending "invalid command" messages and ignore the sender for increasingly-large periods of time once some threshold is reached, in order to break such loops.
Traditionally bots are supposed to avoid loops by:

Only sending messages as NOTICEs.

Not responding to NOTICEs.

I reluctantly did not do this in PAH because PAH relies on causing hilights in users' IRC clients, and NOTICEs typically do not trigger a hilight. Depending on how issue #50 goes there could be increased use of NOTICE but even so, this work is probably necessary since lots of other bots don’t comply with the above either.

I think I'm going to:

Keep a record of how many "invalid command" messages have been sent to a given nickname both in public and in private.

If the public count exceeds X or the private count exceeds Y where X < Y (assuming that public invalid commands will be much more irritating for everyone) then that nickname will get put on ignore for T seconds.

Invalid command count will be reset to 0 when a valid command is encountered. So a few mistakes won't cause any difficulty.

If a nickname has to be put on ignore then the ignore count will be incremented. Depending on ignore count, the next ignore will be for a longer time. Maybe the sequence goes:

A minute
10 minutes
An hour
6 hours
A day
A week
A month.
Until administratively unignored.

This all assumes that the flooder is a misconfigured client that is not actively trying to destroy the game. It will be very hard for this bot to prevent a malicious client from disrupting the game.


npm run build fails on compiling to npm package for vue 2.7.14

Version
2.7.14
Reproduction link
github.com
Steps to reproduce
first time doing open source contributions and wanted to solve https://github.com/vuejs/vue/issues/12998
but was unable to compile vue into node package
Steps:
git clone https://github.com/vuejs/vue/tree/v2.7.14
yarn at root of project
npm run build at root of project
following these steps outlined here
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md
What is expected?
the entire Vue NPM package should exist and be built into [root]/dist
What is actually happening?
npm run build

<EMAIL_ADDRESS>build
node scripts/build.js

node:internal/modules/cjs/loader:944
throw err;
^
Error: Cannot find module<EMAIL_ADDRESS>Require stack:

You are following the instructions from an outdated branch (dev). The current default branch is main.


InvalidParameter

getting error after execute php ./index.php.
{
"code": "InvalidParameter",
"message": "Unable to parse message body"
}
im trying creating VM.Standard.E2.1.Micro

nvm, worked by deleted new line in .env


Add support for using ZULIP_FEATURE_LEVEL to determine how to encode parameters

As part of https://github.com/zulip/zulip/issues/18035
We should implement this as follows:

A commit should make a Client object do a GET /server_settings and store the feature_level and server version as properties.
We can then write functions to encode parameters differently depending on the feature level. for update_user as a sample case, in preparation for the API migration there.
We can figure out a test suite strategy to ensure that these actually work across versions.  E.g. maybe we have CI to run the zulip/zulip tools/test-api tests for 2.1, 3.0, 4.0, and master against the Python bindings.
Once we've figured out the infrastructure for this, we can make a master issue to make everything in our API changelog be supported across versions by this project.

@ligmitz FYI.

Also @msurfer @orientor @LoopThrough-i-j FYI, since if we implement this correctly, it would adjust and hopefully improve the workflow for making API changes.

Exactly something I was looking for and couldn't find. This could create a door for writing integration tests for the API clients and much more.

@PIG208 FYI as well; this is probably one of the more important features for us to add to the Python API bindings.
@neiljp also FYI, since this may have some utility for ZulipTerminal as well (if you can transparently handle some API upgrades).

We already fetch the feature-level and adjust some behavior based on it. It's not clear to me precisely what's involved here, but we can likely handle this via a zulip dependency upgrade or via feature-level conditionals?
Is this required (ie a ZT bug as of now) or optional (ie. ZT api migration, or subject->topic)?

The goal as stated here is just to have things written with the python-zulip-api transparently handle how to call endpoints (E.g. if we rename an endpoint or we change how a parameter to send is encoded).  I think ZT will still need to have all the logic for parsing event formats, etc., though it would certainly be reasonable to consider as a follow-up having a shared function here that converts any old-format events into newer-format events.
Relatedly, we probably want python-zulip-api to pass various client_capabilities by default?  Not sure.

@PIG208 I think this is probably the most important issue for the Python bindings. I think in particular we want to pass all the client_capabilities currently documented by default, to encourage coding against the latest API when writing new clients.


Add c bindings

adding c binding seems hacky. I think it's worth implementing the util functions in every language bc it's simple hex encoding/decoding

Yeah, that's a good thought. My main reasoning was two-fold:

We would eventually add c bindings for almost every piece of code, making it easier to support other languages, at least initially
Any changes would only need to be made in one repo, reducing bugs

the util functions are trivial enough that it may take less time to implement than figuring out c binding integration for the language

this is true, though there's the possibility that edge cases could exist which would be harder to debug

it makes the application bundle bigger and native implementation will have a faster start time

All good points. I'll add another con to your list:

it requires go to be installed and $ make deps for any sdk that uses it.


⚠ Bofrost.es has degraded performance

In 2569c8c, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1657 ms

Resolved: Bofrost.es performance has improved in a297595 after 14 minutes.


Fix a bug when using a custom exception with a custom exception message. Also remove tests for Python 3.2 and 3.3.

Fixes #54
Test included. I didn't see how to run the test so hopefully it just passes. :)

Hmmm. I fixed the linter error And most of the tests pass now. The tests that fail seem to be failing due to the python version used for those tests, which doesn't seem to be caused by my code. So I think it's good now? I'm new to this system.

It looks like tox no longer supports python 3.2 and 3.3, so I've removed those from the tests.
I base my understanding on the comment "tox fails (because setuptools has dropped support for Python 3.3 since v40.0.0)." From this page:
https://github.com/noahmorrison/chevron/issues/42
Well... The test just completed as I was writing this comment, and it seems I failed to disable the tests in the way I had intended. I will try to see what I can do here, but perhaps this needs to be fixed by the project owner...

Okay! Sorry I missed the .travis.yml as I was only looking in the command line with "ls" and the yml was hidden. Got it sorted! It does look like the tests for python 3.2 and 3.3 should be removed. Hopefully my changes look good.
Thanks!

lgtm. Can you please bump the version to 0.4.1? See https://github.com/pnpnpn/timeout-decorator/commit/2bc336d6ed08eb380f51d249ac33a3d284ae10f4

Done. Thanks for the quick response!


adding purple theme

Changed the complexities graphic to a purple theme.

@rbitia can you clarify which graphics you're referring to? Screenshot would be helpful

Nevermind, I see the image now


Fix typo

@stuartleeks : Thanks for your contribution! The author(s) have been notified to review your proposed change.

The typo fix looks good; thanks.


Add mam3 nucleation parameters

Purpose

Add ClimaParameters support for the aerosol nucleation code in the CloudMicrophysics repo.
Content

Add parameters used to calculate nucleation rates in the modal aerosol model.

[x] I have read and checked the items on the review checklist.

LGTM! Thank you.

bors r+


Typo in the article

Step 7 in the Add some code section, there is small mistake. The page should be Index.cshtml instead of index.html
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 68483bc8-45dc-fc2e-b289-2901a70461ff
Version Independent ID: 5167502a-bd55-8927-5656-1c4f107884d7
Content: Create an ASP.NET Core app with TypeScript - Visual Studio
Content Source: docs/javascript/tutorial-aspnet-with-typescript.md
Product: visual-studio-windows
Technology: vs-javascript
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

@Mikejo5000 -- Mike, please review private PR 6641.


hard coded saucelab chrome version

Jun,
can u please approve the pull request as well?
Peidong
On Mon, Sep 18, 2017 at 8:40 PM, Jun Yang<EMAIL_ADDRESS>wrote:

@Jun-Yang commented on this pull request.
Reviewed.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bigtester/automation-test-engine/pull/225#pullrequestreview-63526040,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AL_i0kJpIWUTxr4pluyzspPP21cSVCjQks5sjw14gaJpZM4PbohE
.


Canvas: fix disabling nav buttons if there's no page

Context

The next/previous navigation buttons next to the canvas ought to be disabled if there's no page to navigate to.
However, this was somehow forgotten during some refactoring, passing some non-existent isDisabled and isHidden props.
Summary

This PR addresses this by disabling the buttons using aria-disabled, which means they can still receive focus and can get tabbed to, to ensure accessibility.
We probably need to do this in many other places too, but this is a start.
Relevant Technical Choices

Updates the button component from the design system so it can
To-do

User-facing changes

Before:

After:

Testing Instructions

[ ] This is a non-user-facing change and requires no QA

This PR can be tested by following these steps:

See that next/prev buttons are disabled on the canvas when there's no page to navigate to

Reviews
Does this PR have a security-related impact?

No
Does this PR change what data or activity we track or use?

No
Does this PR have a legal-related impact?

No
Checklist

[ ] This PR addresses an existing issue and I have linked this PR to it in ZenHub
[x] I have tested this code to the best of my abilities
[x] I have verified accessibility to the best of my abilities (docs)
[x] I have verified i18n and l10n (translation, right-to-left layout) to the best of my abilities
[ ] This code is covered by automated tests (unit, integration, and/or e2e) to verify it works as intended (docs)
[x] I have added documentation where necessary
[x] I have added a matching Type: XYZ label to the PR

Fixes #

Verified in QA


Plugin polishing

Fix issues with plugin build system, and add some new plugin developer features

update plugin docs to new import style
add npm run lint/format/tsc/lint-fix plugin developer tools
type check base template code
make the tests are testing the repo version of headlamp-plugin, not headlamp-plugin installed from npm
make sure npm run build and npm pack are used in the headlamp-plugin test script

How to use
Look at plugin docs.

Testing done
Added a few tests for the new lint/format/lint-fix/tsc commands.
Note, I set the version as 0.4.1-rc1 so we could do a release candidate release for testing it works ok.

I realized the API docs related to plugins need attention as well, I'll do them in here.

Made those changes, except for leaving the commented out imports inside the examples.


 Happy to maintain as a separate fork if that's better, just figured I'd send the PR in case it's useful.
The only downside is that we have to duplicate parser.c and parser.h, because they need to be in the same directory for Go compiler to find them.
Signed-off-by: Stephen Gutekanst<EMAIL_ADDRESS>

Sorry for late reply. I have been changing country for the last few months. The main purpose for this repo is I need some eyes candy syntax highlighting for my neovim,  and the old zig treesitter is bigger than this. The problem is the generated c file is fairly big in size. I think adding the same c file, is really waste of space and bandwidth. And I really don't want to do that. It better of with separate fork. Sorry for the inconvenience

No worries at all, that makes sense. I just sent as a courtesy anyway :)
let’s close; cheers!
On Sun, Jul 10, 2022 at 4:26 PM maxxnino @.***> wrote:

Sorry for late reply. I have been changing country for the last few
months. The main purpose for this repo is I need some eyes candy syntax
highlighting for my neovim, and the old zig treesitter is bigger than this.
The problem is the generated c file is fairly big in size. I think adding
the same c file, is really waste of space and bandwidth. And I really don't
want to do that. It better of with separate fork. Sorry for the
inconvenience
—
Reply to this email directly, view it on GitHub
https://github.com/maxxnino/tree-sitter-zig/pull/14#issuecomment-1179822654,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAYGWOAV6YBQSXM5DSSZQUDVTNLZVANCNFSM5V2XXZRA
.
You are receiving this because you authored the thread.Message ID:
@.***>

--
Follow me on twitter @slimsag https://twitter.com/slimsag.


Add [My github profile link]

What changes does this PR do?
Add My profile link into  the mentionned list
Screenshots (If any)
Questions

closing due to inactivity. feel free to reopen


ELevate repository recipe

https://wiki.almalinux.org/elevate/
Signed-off-by: Lance Albertson<EMAIL_ADDRESS>

!bump minor ~

Jenkins has merged this PR into master and has automatically performed a minor-level version bump to v4.2.0.  Have a nice day!


Added grab vars in RouterMux

Codecov Report

Merging #17 into master will increase coverage by 2.03%.
The diff coverage is 94.11%.

@@            Coverage Diff             @@
##           master      #17      +/-   ##
==========================================
+ Coverage   78.31%   80.34%   +2.03%
==========================================
  Files           9        9
  Lines         332      346      +14
==========================================
+ Hits          260      278      +18
+ Misses         56       53       -3
+ Partials       16       15       -1

Impacted Files
Coverage Δ

router_mux.go
84.53% <94.11%> (+7.42%)
:arrow_up:

Continue to review full report at Codecov.

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


Long calendar item popup is cutted

When block has a lot of State records there is no possibility to see link "Navigate to block"
Scrollbar request! ))

Version 1.8.1 added a height limit.

The original journalDateFormatter configuration required the user to read the dayjs document to fill in correctly, Version 1.8.1 removes the journalDateFormatter setting. Instead, I got it from logseq on my own, which unfortunately affected the original date parsing. If you get the error 'Use 'yyyyy' instead of 'YYYY' (in 'YYYYMMDD') for formatting', please click the fx button in the settings to change all YYYYMMDD to yyyyMMdd

confirmed, works well! tnx


Preserve AFK check embed message upon end of raid

Right now, when a raid is ended, the associated AFK check message is deleted. Like headcount, we also want to preserve the AFK check message

We do? sounds like more clutter.  Can just look for headcounts that have been converted

Yes, I've gotten that request multiple times

Bozos don't know what they want.  I'll make the change in 1.1.2


[DO NOT MERGE] Remove snowflake patch

What does this PR do?
Attempt to remove the Snowflake patch. This is likely going to fail but we should record the error and fix it.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

Reviewer's Checklist

[ ] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[ ] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[ ] A release note has been added or the changelog/no-changelog label has been applied.
[ ] Changed code has automated tests for its functionality.
[ ] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[ ] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[ ] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[ ] If applicable, the need-change/operator and need-change/helm labels have been applied.
[ ] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[ ] If applicable, the config template has been updated.

Should we mark this as draft if it's only testing?

Marking as draft. @yzhan289 feel free to unmark it if needed :)

Closing PR in favor of https://github.com/DataDog/datadog-agent/compare/kserrania/remove-custom-snowflake-build


drericeto ban appeal

reason: alting
I like playing on this server very much and thats why I played on an alt account. I did not cause any trouble and will not cause any trouble in the future because I learned from my previous ban.

ples unban im so sorry im crying

Hm, okay. Well, I believe that you are sorry. Unfortunately, it appears you are sorry for all the wrong reasons. Not an hour after you put in an appeal, (which by the way was at around 4AM for me, I could not possibly have answered within the timeframe you wanted) you attempted to spam ping all the moderators on the server as well as all STAFF on the server, because you wanted us to read your appeal faster, I guess?
After being told to wait, you decided

was the best course of action. Normally this is a discord ban. However, staff were lenient, and instead gave you another chance, which you used to ping me personally so I could wake up and read your appeal.
Ban appeals are for those that believe they have been banned unfairly so they can share their story and gain a second chance should they deserve it.
Right now, I am looking at discord, which you are now banned from, FYI and I see you asking users if they want to see your "huge penis". Given all this, it's rather clear to me that you are indeed sorry. Sorry you got caught, sorry you didn't get your appeal read sooner, and sorry you didn't get unbanned.
Have a good day 👍

nigger

lol, is that the best you can do? You really are 7 years old. Consider yourself banned from this tracker as well.

im serious about the infinite master balls

you should check out the exploit

people on the server already know about the exploit dont need to delete my comment
s


Modal Consistency

There's some inconsistencies across modals I wanted to attempt to fix.
Here's the specs for a perfect modal:

Offending Modals
Heads Up

Needs header space, alignment fixing
Heading needs to be the right weight
Needs the right X

Flag an item

Needs header space, alignment fixing
Heading needs to be the right weight
Needs the right X
Isn't tall enough or doesn't have the proper padding.
Buttons need to be 20px apart
The content in the content area should line up with the heading.
Can we change "OK" to "OK, got it!" so the button is more visible.

Edit License

Needs header with close button and "Edit License" becomes the heading.
Buttons in footer are too close together

About Community Taxa

Heading needs to be in header with close button
Can we make the button say "OK, got it!"

Projects
Might as well make this one consistent so everything is controlled by the same styles.

Needs the header specced out above
Needs the right button styles in the footer

@pleary or @kueda Are these modals on a different stylesheet since they don't use Whitney

Please don't start this just yes. Need to fix something! Tnx.

@kueda this is ready to go. Have always dreamed of having consistent modals. Up to you, of course!


Support custom attributes on node

I'm assuming that at this moment there can only be 2 attributes for each node:

title
description

In our application, which you will be able to see its UI pretty soon, we have lots of data on every single node. For example, one of the node in our database has more than 30 properties.
We should allow user to freely specify the node properties. We can assume they are all key-value pairs, such as
"name": "..."
"color": "red"
"size": "big"
"location": "(234, 566)"
...

I deside removing the Title and Description and giving a Map to store multiple data values.

I deside removing the Title and Description and giving a Map to store multiple data values.

That shall work. One question though: do we assume the map value to be primitive or object?

I deside removing the Title and Description and giving a Map to store multiple data values.

That shall work. One question though: do we assume the map value to be primitive or object?

I'm going to use the String directly, and some potentially complex data will be serialized back to String

I deside removing the Title and Description and giving a Map to store multiple data values.

That shall work. One question though: do we assume the map value to be primitive or object?

I'm going to use the String directly, and some potentially complex data will be serialized back to String.

String would be OK at this moment. In fact, do do with String in this PR, because this will be the first step for later improvement


Rename BUILD_TRANTOR_SHARED to BUILD_SHARED_LIBS

Use official variable name to build shared library.
You don't need to add static/shared when calling add_library and CMAKE_POSITION_INDEPENDENT_CODE is automatically set to the good value.
Don't forget to update Trantor submodule that chekout actually to the merge request

@an-tao trantor has been updated
At first commit, I get a failure (https://github.com/drogonframework/drogon/runs/7107627659). I enabled output on failure but at second try, I get no failure. Strange...
I think that output on failure should be enabled by default.


Merge main into qa-beta

Description

Checklist (Definition of Done)

[ ] Unit and integration tests added
[ ] Added test description under Test manual
[ ] Documentation added if necessary
[ ] CI and all relevant tests are passing
[ ] Add the ticket number to the PR title if available, i.e. ROX-12345: ...
[ ] Discussed security and business related topics privately. Will move any security and business related topics that arise to private communication channel.

Test manual
TODO: Add manual testing efforts
# To run tests locally run:
npm run test

Codecov Report
Patch coverage has no change and project coverage change: -0.17 :warning:

Comparison is base (71a7568) 9.07% compared to head (bf05b01) 8.90%.

:exclamation: Current head bf05b01 differs from pull request most recent head 9753129. Consider uploading reports for the commit 9753129 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##           qa-beta    #108      +/-   ##
==========================================
- Coverage     9.07%   8.90%   -0.17%
==========================================
  Files           37      37
  Lines          540     550      +10
  Branches       109     112       +3
==========================================
  Hits            49      49
- Misses         458     465       +7
- Partials        33      36       +3

Impacted Files
Coverage Δ

src/routes/InstancesPage/CreateInstanceModal.js
0.00% <0.00%> (ø)

src/routes/OverviewPage/OverviewPage.js
0.00% <ø> (ø)

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


The ally.js integration is broken

Expected behavior:
When running npm run production, everything should compile nicely.
Actual behavior:
When running npm run production, node is complaining about ally.js (see error in terminal window).
Steps to reproduce that behavior:
Run npm run production.

This was recently brought up in the Mix repo:

https://github.com/JeffreyWay/laravel-mix/pull/1669#issuecomment-416833673
https://github.com/JeffreyWay/laravel-mix/issues/1774


Feedback for: Running a Local Web Server [en]

https://github.com/google/WebFundamentals/blob/master/src/content/en/ilt/pwa/running-a-local-web-server.md
This doc is outdated. It was from before we started using Node in the labs. It's a nice resource but it doesn't align with the labs anymore. We should probably remove it. If we really want to keep it then it will need to be edited to match the new course design or to exist as a stand alone document. (Also there are grammar issues.)

Will yank.


#161420737 Create a db powered endpoint to login users

What does this PR do?
This PR creates the endpoint for store attendants and owners to login
Description of Task to be completed
The main tasks to be completed are:
Creation of an endpoint to login a user
Connect it to a database
How should this be manually tested?

Create  a virual enviroment with the command
$ virtualenv -p python3 env

Activate the venv with the command
$ source env/bin/activate

Install git
sudo apt install git

clone this repo
$ git clone https://github.com/codeMarble254/Store-Manager-v1.git"

cd into the folder Store-Manager-V1

export required enviroment variables
$ export FLASK_APP=run.py
$ export DB_NAME="storemanager"
$ export DB_HOST="fill in your localhost"
$ export DB_USER="fill in the db user"
$ export DB_PASSWORD="fill in your db user password"
$ export SECRET_KEY="<your key>"

create the dev database
createdb storemanager

create the testing database
$ createdb test_db

Switch to the current branch
$ git checkout ft-login-user-v2-161420737

install requirements
$ pip install -r requirements.txt

now we are ready to run.
8.now we are ready to run.
for tests
export APP_SETTINGS="testing"
pytest app/test/v2 -v --cov=app/test/v2

for the application run
export APP_SETTINGS="development"
$ flask run
If you ran the application you can test the  api end points using postman as follows

Endpoint
functionality
contraints(requirements)

post /api/v2/auth/login
Login
User information

What are the relevant pivotal tracker stories?
#161420737

Pull Request Test Coverage Report for Build 127

110 of 112 (98.21%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.0%) to 98.214%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/test/v2/test_users.py
83
85
97.65%

Totals

Change from base Build 67:
1.0%

Covered Lines:
110

Relevant Lines:
112

💛  - Coveralls

Pull Request Test Coverage Report for Build 127

110 of 112 (98.21%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.0%) to 98.214%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

app/test/v2/test_users.py
83
85
97.65%

Totals

Change from base Build 67:
1.0%

Covered Lines:
110

Relevant Lines:
112

💛  - Coveralls


fix(*): rm filterTrafficSplit logic as it is no longer needed

Keeping this prevents us from referencing just a service name
without the namespace suffic as the traffic split root service
Signed-off-by: Michelle Noorali<EMAIL_ADDRESS>
Description:

Affected area:

New Functionality      [ ]
Documentation          [ ]
Install                [ ]
Control Plane          [X ]
CLI Tool               [ ]
Certificate Management [ ]
Networking             [ ]
Metrics                [ ]
SMI Policy             [ ]
Security               [ ]
Tests                  [ ]
CI System              [ ]
Performance            [ ]
Other                  [ ]

Please answer the following questions with yes/no.

Does this change contain code from or inspired by another project? If so, did you notify the maintainers and provide attribution? No

I added an e2e. Would ya'll mind re-reviewing @snehachhabria @shashankram


Corrected the log placeholder.

I corrected the SLF4J log placeholder: http://www.slf4j.org/manual.html

Thanks.


Use upstream definitions, fix gopackagesdriver

What type of PR is this?
Bug fix
Feature
What does this PR do? Why is it needed?
With some recent changes made, the gopackagesdriver seems to fail to resolve all standard library imports. This fixes that, as well as migrating the driver to use the upstream definitions as defined here: https://pkg.go.dev/golang.org/x/tools/go/packages#hdr-The_driver_protocol.
Which issues(s) does this PR fix?
Fixes #4184
Fixes #3962
Other notes for review
This is absolutely not fully ready to be merged in. I'm willing to take some time to clean this diff up, but would like some guidance on what specifically should be changed / what should be kept. Please let me know, and be patient with me here - it's my first time contributing code to this repo. Thanks <3!

It looks like this CI failure: https://buildkite.com/bazel/rules-go-golang/builds/7281#019373f5-722b-4160-8e7b-4cdc32943756 is unrelated to this PR. Going to ignore it for now.

What else would be needed here to get this landed?

@aran

What else would be needed here to get this landed?
I'm not sure. At @devzero-inc, we use this patch-set daily, and I know that it definitively works for us, but we also have an entirely cgo-free code base. Earlier, at @fmeum's request, I tried to dig into /why/ specifically CompiledGoFiles isn't getting populated, and experimented with passing -compiled=true to go list... and, well, that compiles basically cgo file in the standard library from scratch and invokes the C compiler a bunch of times, pinning CPU at 100% for 10+ minutes.


Make TopAppBar transparent over full page background image

Hi team,
what is the way to show a full page background image over TopAppBar?
I can not get it transparent showing to wrapping div background image...
.bg{
background: url(/assets/images/pre.jpeg) no-repeat 0 0;
background-size: cover;
}
return (
<TopAppBar onNav={(e) => alert(e)} className="topappbar">
<TopAppBar.Row>
<TopAppBar.Section align-start>
...
any clue?
best
Timo

Sorry guys, it was just the missing 100vh on the bg class.


Updated balanceparenthesis.java

Replaced For Loop to If-Else Loop for better Readability of code
Replaced List Methods with Stack Methods For Homogeneity of the Program
Looking Forward For Merge

Hey,
Thanks for the Merge


Autorest Regen Preview to 3.0.0-alpha.20230918.7 by Dapeng Zhang from refs/pull/3747/merge

Triggered from https://github.com/Azure/autorest.csharp/pull/3747

API change check
API changes are not detected in this pull request.


SEO updates for Version

Contributes to #9440
ALERT
I deleted docs/core/versions/install-management.md and redirected to the how to remove sdk/runtime article. This article seemed pointless and just reiterated information in the how to remove article. It also had < 500 page views.

Wondering if parts of that topics then should move into the article you're redirecting it to.

@mairaw I think maybe porting

In general, you only need the latest SDK and latest patch version of the runtimes required for your application. Instances where retaining older SDK or Runtime versions include maintaining project.json-based applications. Unless your application has specific reasons for earlier SDKs or runtimes, you may safely remove older versions.

would be handy


Upgrade

@amira133 Please fork from here https://github.com/komsa-ag/Camunda.Api.Client and create a new PR.
This repo is no longer maintained.

Please also create a issue for your changes in https://github.com/komsa-ag/Camunda.Api.Client


Road to v2.0.0

The following is a list of changes I intended for v1.0.0. However, since that version has already been released, these changes will be targeted for v2.0.0:

[ ] Remove gausschebyshev
[ ] Remove besselroots
[ ] Organize function names etc.

For example, FastGaussQuadrature.asy should be renamed to FastGaussQuadrature.gausslegenedre_asy.
They (gausslegendre_asy, gausslaguerre_asy, etc.) will be treated as 'non-exported stable API', meaning they won't be exported but are stable for use.
Consider adding an _ prefix for purely internal functions, such as underflow_threshold.

Removing deprecated functions and changing internal function names can all happen on 1.1

Please don't remove deprecated functions such as gausschebyshev without a breaking change, as these used to be a part of the official API. By default, Julia doesn't warn about the deprecation unless one starts it with --depwarn=yes, so this may confuse users. Is there a pressing need to remove these functions right away anyway?

changing internal function names can all happen on 1.1

That's right. But I was just planning to make this package more stable before releasing v1.0.0.

Is there a pressing need to remove these functions right away anyway?

No. I believe we should not remove the exported functions before we get an agreement.


Add Strapi cms

Noticed Strapi is not included in the cms list. Would be great to have it there since I have a theme using it that I'd like to submit.

Hi @collinsmuriuki - Strapi should be on the list for sure! We just havent had any themes submitted that use it yet.
You can add Strapi as a CMS as part of your PR - instructions are in the README.

Cool, will do that


clear_colors in TextEdit does not work

Godot version:
3.2 Master
OS/device including version:
Ubuntu 18.04 bionic
x86_64 Linux 5.0.0-31-generic
Issue description:
TextEdit.clear_colors() should remove all syntax highlighting colors, although it does not
Steps to reproduce:

clear_colors()

Minimal reproduction project:
GodotTestProject.zip

Are you trying to disable all syntax highlighting? In this case you can simply use syntax_highlighting = false instead of clear_colors().
It seems clear_colors() is not doing exactly what the documentation says, though. I'm going to propose a PR with two things:

Clarification in TextEdit doc about clear_color()
Fix its implementation, because it's not working in all cases at the moment

Thank you for the PR :)
Of course disabling syntax highlighting would work, I would plan to add my own custom options after the clear call

After my change, clear_colors() is still going to only reset the custom options you've previously added using add_keyword_color() and add_color_region().
If you need to disable all the default highlighting and replace it with your own, you can try to change the default colors in the Custom Colors section to make all the text white, and then add your own custom keywords by script like you intended to. Would that work for you?

So can this be considered solved by #32940?

Yes, thank you all!

Archive This?

Well no, why? It's a bug which has been fixed.


CLI ignores nonexistent path

Running typeshare ./path/that/does/not/exist --lang=typescript --output-file=my_typescript_definitions.ts does not seem to throw an error

Hello, and thank you for reporting this! I'll be looking into this!

At the moment, we are discarding errors that result from converting the CLI-provided paths to walkable iterators. I'll bring this up with the team to discuss if there's a better way to handle these errors.


Update ns-wincred-credentiala.md

Escaping a backslash

@TimMisiak : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Thanks for your contribution, I've merged your changes and they should be live soon.


∵(;,) is not equal ∵(.) I think it should equal.

I run this code:
□4_5_6
∵(;,) ⇡4

I think this stdout
⟦1 2 3⟧
[0 1 2 3]

but real stdout:
[0 1 2 3]
[⟦4 5 6⟧ ⟦4 5 6⟧ ⟦4 5 6⟧ ⟦4 5 6⟧]

if this code:
□4_5_6
∵(.) ⇡4

⟦1 2 3⟧
[0 1 2 3]

is this specification?
version is 962e64c90a8a568397f1a78c32acbaf04f551d5f and 0.3.1 prerelease

The signature of . is |1.2.
The signature of ;, is |2.2.
This makes ∵ each behave differently.
This behavior is intended.

The signature of . is |1.2.
The signature of ;, is |2.2.
This makes ∵ each behave differently.
This behavior is intended.

I understood design. Thank you.


feat: add JGLUE tasks

JGLUE is a widely used test set in the Japanese LLM research community, consisting of five sub-tests (with MARC-ja removed due to a request from Amazon):
JSTS
JNLI
JSQuAD
JCommonsenseQA
Finished Issue #455

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint. The docs are available until 30 days after the last update.


Crashes on close with Win 7 x64

Operation System: Win 7 x64 Ultimate
Beaker version: v0.8.0-prerelease.9
This is the first version of Beaker that I've used that has crashed like this. Very simple:

Beaker works fine while running (no crashes at all), BUT ...
Close Beaker
"Beaker Browser has stopped working"

I've tried a new fresh install and the same thing happens - so at least it's consistent and repeatable.
Let me know if you need more system info etc ..
P.

Thanks for reporting. I've seen this on MacOS too. I'll investigate.

Filed an issue with Electron. Not sure yet what could be causing this.

Just wanted to add to this that I couldn't launch the browser a few days ago so I reinstalled it (.8) and while I had this same problem before it no longer happens. The only other thing of note is then when I updated windows this month (which was before the reinstall)  I updated .Net and all the patches that weren't previously installed.


Add tests for Django 3.2

Before contributing, please read our contributing guidelines and code of conduct.
Overview
This PR adds new tox environments to run the tests against latest Django 3.2 and Python from 3.6 to 3.9 (supported Python version for Django 3.2)
Related Github Issue
https://github.com/newrelic/newrelic-python-agent/issues/343
Testing
There's no special setup for testing, the CI will run the tests in the new environments with tox.

 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 the contribution!


After upgrading from 1.5.10 index isn't working anymore in combination with loop=false

Which OS ?
IOS
Version
Which versions are you using:

react-native-swiper v1.5.10
react-native v0.48

Expected behaviour
Page starts on provided index.
Actual behaviour
Page just starts at index 0.
How to reproduce it>
To help us, please fork this component, modify one example in examples folder to reproduce your issue and include link here.
Steps to reproduce

Add a loop={false} and index={1} to any swiper.
Try it out.
It will start swiping from index 0.

yup same problem here.. also won't recalculate dimensions if the swiper changes width.
also loop will only let me go forward the first time.

I'm also hitting this problem. According the  dot indicator  i'm on view 3 but it renders the first view.

same here. even setting index to 0 and using scrollBy() in componentDidMount() results in the same issue

Actually, which version were you on prior that it was working?

I guess is the react-native update caused it.
Having these 0.45 fully working, switching to 0.48 caused problems.

This was just released, is it working for any of you?
https://github.com/leecade/react-native-swiper/releases/tag/1.5.13

@IjzerenHein v1.5.13 has resolved my problem


Feature request: pipenv install --index myindex mypackage

I would like to request a command line option for specifying the source during pip install. For example, given this Pipfile (from the docs):
[[source]]
url = "https://pypi.python.org/simple"
verify_ssl = true
name = "pypi"

[[source]]
url = "http://pypi.home.kennethreitz.org/simple"
verify_ssl = false
name = "home"

I would like to be able to invoke something like:
pipenv install --index home mypackage
Which would install from my "home" index and add this into my Pipfile:
[packages]
mypackage = {version="*", index="home"}

Makes sense, although if it's a package that isn't on pypi and your index is in your pipfile already it may work just fine to leave the index off

Is this technically possible though? While there is --extra-index-url in pip, I don’t think you can specify which index to use for each dependency, only the installation as a whole.

The example at https://docs.pipenv.org/advanced/#specifying-package-indexes specifies a different index for each requirement, so Pipenv must already support it.

Yeah good point, doesn’t this already work?

Try pip install -e git+https://github.com/pypa/pipenv.git@1973-extra-index-urls#egg=pipenv and let me know if it works


exclude Node 17.x as supported version

Closes #8173. The >=16.14 range also includes Node 17, which (apparently at least in some versions) doesn't support the three-argument version of util.inspect.custom. People shouldn't be using Node 17 anyway. I think we can make this change as a fix rather than as a breaking change.
Please don't delete this checklist! Before submitting the PR, please make sure you do the following:

[x] It's really useful if your PR references an issue where it is discussed ahead of time. In many cases, features are absent for a reason. For large changes, please create an RFC: https://github.com/sveltejs/rfcs
[x] This message body should clearly illustrate what problems it solves.
[ ] Ideally, include a test that fails without this PR but passes with it.

Tests

[x] Run the tests with pnpm test and lint the project with pnpm lint and pnpm check

Changesets

[x] If your PR makes a change that should be noted in one or more packages' changelogs, generate a changeset by running pnpm changeset and following the prompts. All changesets should be patch until SvelteKit 1.0

I really can't tell what all these test and deployment failures are about. I don't see how they could be related to this change.

(I approved because I think Node 17 being a non-LTS line and unsupported at this point is a good-enough reason to make this change right now when 1.0 is so fresh still; it will probably break right away for anyone using it anyway, as the issue shows)

Question about Cloudflare – right now they ask for 17 for Pages projects, wondering what the impact there might be

That's annoying. Thanks. I've opened a PR https://github.com/cloudflare/cloudflare-docs/pull/7043

I'm also not sure if anything above 17 is available, last time I tried 18 it wasn't. Let me try a build now ...
Nope: Failed to install node version '18'

Do you know what version of Node 16 you get if you specify NODE_VERSION=16? Is it at least 16.14, the minimum version needed by SvelteKit?

Let's see ... 16.19.0.
I can go around to my existing Pages projects and switch everything to 16, just in case it takes a while for Flare to get on it.
When you ask for 17 you get 17.9.1, fyi


Schema n seeds

Hi!
At Metric Insights, we've been using Phinx to handle migrations of our rather complicated database (360 tables, 60 seed tables, some foreign keys, procedures, views, etc.) However, we needed a clean and easy way to create a base schema including seed data to allow us to install a fresh version of our product on customer machines. (Instead of running through all the migrations, it is easier to create the schema once, and then add any seed data.)
I know some work on adding a seed() function to migrations, but I was looking for something a little more akin to the Ruby On Rails method of automatically dumping a schema structure on each migration. As a result, I spent the past week working on implementing this in a pull request. The main features and design goals that I wanted were as follows:

feature1 - automatically dump modified schema structure when a developer creates a new migration
feature2 - be able to create seed data from an existing database (that may not already have a phinx migration for)
feature3 - be able to reset the database to a 'known' clean version during development, similar to rail's db:reset functionality
keep it as simple as possible for the user.  don't add a bunch of unnecessary phinx commands or collections of commands
intentionally do NOT support views, stored procedures, and functions. This is more like code and should be loaded in after the basic schema structure has been loaded.
use sql-based (database specific) schema dumps (no ORM)
support as many database adapters as possible
make phinx migrate continue to work with existing phinx.yml configurations

The result is this pull request. (Sorry it's kinda big! Most of the code is tests) It includes two new user-facing methods:
phinx reset - reset the database to the state known in schema.sql
phinx dump - dump the current version of the target environment into a schema.sql (this will automatically be called by phinx migrate and phinx rollback, similar to rails, but can be turned off with the --no-schema-dump option)
I have tested this branch with MySQL, Postgres, and SQLite adapters and all tests pass, including with potentially complicated foreign key dependency schemas. However, I was unable to test SQLServer so I would love for someone to help with that.
I'm also open to feedback, both positive and negative, and would be willing to work with the community more to get this functionality upstream.  There are still some things that could use doing, like:

integrating with proposed Migration::seed() if necessary
testing SQLServer
updated user documentation about working with seeds, handling code like views, procedures, etc.
a database setup/create method similar to rails?

Thanks for all the good work you guys have done on this project, it was relatively easy to modify!
-Steve
p.s. - if you are running MySQL 5.5 or earlier, and you point the phinx test suite against said database with a lot of innodb tables, you might need to set global innodb_stats_on_metadata=0;, otherwise the code dump the schema is pretty horribly slow. See https://www.percona.com/blog/2013/12/03/innodb_stats_on_metadata-slow-queries-information_schema/ for more info. Luckily, innodb_stats_on_metadata defaults to OFF for mysql 5.6 and later.

Hm... so i had a bout of php 5.3 incompatibilities, which I have verified fixed on a php 5.3 debian squeeze docker image. The latest build, however, seems to die due to a travis configuration error. Php 5.4 build is trying to create postgres user and blocking on user input:
Shall the new user be a super user? (y/n)
I'll commit a dummy commit later to see if the build machine magically fixed itself (because before the 5.4 build built just fine?)

hey @robmorgan! i've been perusing through the open tickets and i gather that you're working on a seed functionality for 0.5.0. From what little I could piece together, I think you're leaning more to a separate command like phinx seed which will seed the database with a local seeder, as well as separate migrations out to include up/down and a separate seed method.
While that functionality may prove useful for many folks, it's not really what we needed at MI. Hence this PR.
I very much hope that what I've done here is compatible with your anticipated changes as I'd love to see it merged. Would you mind giving it a review when you get the chance? Please let me know if there's anything I need to change to make it work with what you're planning. I'm happy to work with you in whatever way you need to get this functionality upstream! Thank you!

hi @rockpunk thanks for such a big PR. I've just started skimming over it. First thing I can spot is some of the code is not properly PSR formatted. The other thing - I like the reset + dump commands <--- they have been commonly requested in the past. The seed logic though will need to be expanded on in order to meet everyone's needs. I can probably integrate some of my work in here, I'll keep going over it. Cheers, Rob

Thanks Rob, yes, you are correct re: psr formatting. I ran everything I wrote through php-cs-fixer so it should be kosher now. (i don't normally write php and only touch it if i have to ;) ) I'm happy to hear that this functionality can likely be expanded on. Please don't hesitate to let me know if you have any questions if/where the code doesn't speak for itself.
I'm looking forward to seeing how the seed logic will be expanded!
-Steve

+1 on being able to dump schema. Looks like I searched for this feature at the perfect time as I'm seeing a lot of active development on it. Great work guys

Thank you for contributing! The branch you made this PR against is no longer accepting patches. This probably happened because we didn't merge your changes fast enough. :sob:
Please create a new PR against the current default branch if you want to see these changes merged.


Fetch user data to continue the wallet dashboard flow

We need to figure out how to fetch the user data to continue the dashboard flow

Auth server sends user sub id along with the continue response
Call the another endpoint in auth server to fetch the user data ??
add additional data to auth server session : vault id (arbiratory id)  creating keystore and vaultID and persistance

It is part of integration pr. Changes are cherry picked


Document the cluster capacity framework

@kubernetes/rh-cluster-infra

I would add a section that explains what level of access the supplied kube config must have on the cluster for specific resources in order to run.   Assume you need LIST pods, etc.

Cluster capacity build/test passed for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

Cluster capacity build/test errored for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

The magic incantation to run this job again is be nice and run.

Cluster capacity build/test errored for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

The magic incantation to run this job again is be nice and run.

Cluster capacity build/test errored for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

The magic incantation to run this job again is be nice and run.

Cluster capacity build/test errored for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

The magic incantation to run this job again is be nice and run.

Cluster capacity build/test errored for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

The magic incantation to run this job again is be nice and run.

Cluster capacity build/test errored for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

The magic incantation to run this job again is be nice and run.

Cluster capacity build/test errored for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

The magic incantation to run this job again is be nice and run.

Cluster capacity build/test errored for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

The magic incantation to run this job again is be nice and run.

Cluster capacity build/test errored for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

The magic incantation to run this job again is be nice and run.

Cluster capacity build/test errored for commit 6567cba828630eec48e646fecf9f09e629d42b9f

logs

The magic incantation to run this job again is be nice and run.

@redhat-k8s-bot test please


Envelope Decay Bug

When decay value is set to 0 and the sustain is set to 0. The attack portion of the envelope cannot be heard.

Update. This isn't a bug. The input must have a positive integer. 0 throws and error and doesn't allow any triggering at all.


Fix crash when changing flash mode on front camera

getSupportedFlashModes returns null for front camera on most devices.

Available in v5.3.3.
Thanks again!


Starting PR to push DBN to Pylearn2.

Added RBM subclass of DBM for convenience.
Add docs to DBM.
Added chain initialization to DBM for some future changes to gradient estimation.

@goodfeli You were reviewing this originally, any update?

Got side-tracked. Hoping to pick this back up eventually but don't have time ATM.


When it is expected to have more sophisticated LiDAR?

Dears
the current LiDAR is a very simple ray casting one. When it is expected to have a more sophisticated, more realistic LiDAR sensor based on ray-tracing?
Best Regards

Hello Ibrahim,
We are currently developing a new module for electromagnetic sensors based in physical interactions for both LiDAR and RADAR. We expect to have news about it in the following months.
Regards,
Daniel.

Dears
I am asking if there is any update?
Thank you very much


GitHub page deployment not up to date

The deployed GitHub page contains outdated slides (https://esciencecenter-digital-skills.github.io/scikit-learn-mooc/). For example, the sides on decision trees should not contain material about over- and underfitting.

This is fixed now!


add .ConfigureAwait(false) to all async calls

Added ConfigureAwait to all async calls in the library.
Closes: https://github.com/DuendeSoftware/Duende.AccessTokenManagement/issues/15

@leastprivilege -- is this all that was needed?

@ArnautS -- can you have a look at this PR, please?

The OP doesn't seem to pay attention anymore.
Can we try to only wrap the HTTP calls in CA(false) for a start?


PIP-117: Change Pulsar standalone defaults

Master Issue: #13302
Motivation

Change standalone metadata impl from ZooKeeper to RocksDB

Pulsar functions package backend -->  Change from using DistributedLog to using local filesystem, storing the
jars directly in the data folder instead of uploading them into BK.

Pulsar functions state store implementation --> Change the state store to be backed by a MetadataStore based backed,
with the RocksDB implementation.

Table Service --> Do not start BK table service by default

/pulsarbot run-failure-checks

Some thought (I voted the PIP but now that we are close to committing the patch some doibts camento my mind) Disabling zookeeper by default may have some nasty impact of integration tests of many applications and that run the same test against many versions of Pulsar.
I wonder if there is some easy way, especially for docker users, like passing a single ENV entry of telling Pulsar standalone to run with zookeeper. It will be quite difficult to support probably but I am now imagining the pain for making integration tests of many applications work with different versions of Pulsar

I'm not sure I'm following here. The external interface of Pulsar does not change whether its metadata is stored in ZK or RocksDb.
I agree though that it's probably a good idea to leave a CLI flag to force the ZK mode, to leave the option open, but that wouldn't be the default.


Local-model not working, as it expects openai api key.

Hello!
Regarding this issue, I am currently using LM Studio. When using local-model, it does not work. As I can see in code, in interpreter_lib.py, line 324, variable custom_llm_provider is set to 'openai', so it expects de openai api key. Which has to be the value of this variable when using open-source LLMs as Mistral?

Okay i will take a look at this issue today.

Thanks! In my case, the issue has been solved by setting:
model = "ollama/llama2"
And removing the variable custom_llm_provider.
Just in case it helps! 😄

Fix this bug in this PR : https://github.com/haseeb-heaven/code-interpreter/pull/14


MINOR: Do not end Javadoc comments with **/

From https://blog.joda.org/2012/11/javadoc-coding-standards.html :

Use the standard style for Javadoc comments
Javadoc only requires a /** at the start and a */ at the end.
[...]
Do not use **/ at the end of the Javadoc.

Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Note: I have more meaningful improvements coming for the Javadocs, but I'm starting with small stylistic changes to get those out of the way first as a baseline.

retest this please

@eneveu -- Thanks for the PR. Seems it's outdated. Would you like to update it so we can merge it?

Closing this stale PR in favor of https://github.com/apache/kafka/pull/14540


Add the Arabic Smith and Van Dyke version to BibleVersionCollections.ts

Added the SVD Arabic version from bolls.life https://bolls.life/static/bolls/app/views/languages.json

It's great to see others contributing! I know this has been a life changer when taking sermon notes for me and to be able to have more people be able to use it in their own language is amazing! Thank you for your contribution! Hopefully Tim will be able to get this approved soon.
As one who is particular to formatting of verses, how does this work with verse numbers and what not? I'm not familiar with how verses are numbered in the Arabic language. Just as an example in English we tend to have verses either in paragraph form or verse by verse form. Pictures below for reference.
Also as a side note how are verse references formatted? This should probably be in the discussions but I'll go ahead and hijack this anyway lol

Thanks, will try to review it today

Hi @kajogo777
Thanks for the contribution, the change is clear, and I would like to approve it,
BTW, do you mind sharing more about the number formatting in Arabic, like @JPT62089 mentioned in this comment,
https://github.com/tim-hub/obsidian-bible-reference/pull/70#issuecomment-1364732566

Thank you @JPT62089 @tim-hub
Arabic is an RTL language, so unfortunately both the number formatting and text alignment are broken.
It's fine to have the numbers in English, but the formatting makes it a little confusing :D, maybe I'll submit another PR later to support RTL languages.

Thank you @JPT62089 @tim-hub
Arabic is an RTL language, so unfortunately both the number formatting and text alignment are broken.
It's fine to have the numbers in English, but the formatting makes it a little confusing :D, maybe I'll submit another PR later to support RTL languages.

Thanks that will be great!

Thanks, will try to review it today

Sorry all, I didn't manage to get it reviewed and tested it on time, will try find some time this week

Hi @kajogo777
@JPT62089 started a discussion here, it could help for supporting RTL languages.
https://github.com/tim-hub/obsidian-bible-reference/discussions/77

this is in after resolving conflicts.
https://github.com/tim-hub/obsidian-bible-reference/pull/90


Hello, in ontology propagation annotation, what relationships between ontologies do you consider?

Hi, we follow CAFA rules and consider all relations such as part_of, regulates, occurs_in, and etc.
Have a look here https://github.com/bio-ontology-research-group/deepgo2/blob/fe6f9b05790d8e3d2da491083f04fded4840539e/deepgo/utils.py#L142

But I found that in the get_ancestors function of utils.py, in this code, only the is_a relationship is used to find the ancestor node:
for parent_id in self.ont[t_id]['is_a']:
if parent_id in self.ont:
q.append(parent_id)
Is my understanding wrong?

Hi, all relations are considered as 'is_a', if with_rels parameter of ontology class is set to True


Instantiate without string for Laravel IoC

Is there any way to get an instance of Stringy without passing a string to the constructor since StaticStringy has been removed?
I need to have Stringy in the app container which would usually be just this short piece.
$this->app->singleton('stringy', function ($app) {
    return new Stringy();
});

The issue is that Stringy expects the first parameter to be a string and since calling the facade would be something like Stringy::slugify('fòô     bàř') there is nothing I can pass to the new Stringy() which is why I would need new StaticStringy() which works.
So how would I put Stringy behind a Facade now that StaticStringy is gone?

Just wondering, what did things look like when using StaticStringy?

@GrahamCampbell any suggestions here?

I could make the string an optional arg for the constructor and create method, resulting simply in an empty string. That is, same behavior as return new Stringy('');

With StaticStringy it was just the following and that is what I am currently using with ~1.9.
$this->app->singleton('stringy', function ($app) {
    return new StaticStringy();
});

Fixed via https://github.com/danielstjules/Stringy/commit/e237f30d94cadefdbea6a9ca3f9406b3167fffe6


Fixing collisions

Description
Task: Fixing collisions
Feature: #459
This task is related to fixing the collisions modified when creating MapLayout. This is to make sure that a player cannot walk over a bench or a station to ensure adequate gameplay when cooking and making different meals that need to be delivered to customers.
Dependencies
Would be good to finish finalising MapLayout and testing #480
Milestones
List of steps that need to be completed for this task.

[x] Bench Collisions (Oct 11)
[x] Stations Collisions (Oct 11)
[x] Fix any other issues that are faced when player moves (Oct 12)

Completion Deadline: Oct 12
Member

@danhdinh98
@Rakshit31773

Closed by #533 (with team 5)


Fixes #3847 - clarifies configuration of language fallbacks

Makes clearer that language fallback configurations for pages are not automatically applied to placeholders too.

Coverage remained the same at 87.67% when pulling b966064ada43457e475f76def6f77cd672769f42 on evildmp:fix-3847 into e1fa7e49bfa6f2dbda0ce7c8a4af2423133819db on divio:support/3.0.x.

Coverage remained the same at 87.67% when pulling b966064ada43457e475f76def6f77cd672769f42 on evildmp:fix-3847 into e1fa7e49bfa6f2dbda0ce7c8a4af2423133819db on divio:support/3.0.x.

Coverage remained the same at 87.67% when pulling b966064ada43457e475f76def6f77cd672769f42 on evildmp:fix-3847 into e1fa7e49bfa6f2dbda0ce7c8a4af2423133819db on divio:support/3.0.x.


Swift tests: RSC7, RSC18

Looks good, but the commits for RSC9 and RSC10 are already merged so this PR has included additional commits I think?

@mattheworiordan The RSC9 and RSC10 commits come from the PR that you merged: #70 - Swift tests: RSC9. I joined RSC9 and RSC10 to the same branch.

@ricardopereira the thing is that your branch swift-tests-RSC7 should only contain the commits for this PR.  If commits from another PR are included in this branch, then the scope of this PR becomes greater than what you intended.  Why don't you rebase this on master and force push this branch, and only the relevant commits will be included, and I can then merge.

@mattheworiordan Then I misunderstood, sorry. In some PRs I needed the changes of the last PR so I created each PR to merge with the last one.
So, what am I missing?
Before each push spec-branch I need to rebase it with master and create the PR to merge with the master branch?

Then I misunderstood, sorry. In some PRs I needed the changes of the last PR so I created each PR to merge with the last one.

It's not really that important to be honest, and I could just merge it so sorry if I am being pedantic.  But the idea generally is as follows:
master
  |-> feature A (2 commits)
       -> feature B (2 commits)

So when you do a PR for feature A it will contain only 2 commits, and be based from master i.e. the from bit of the PR in Github.  You do not push the 2 commits from feature B into the feature A branch, so that feature A will only have the 2 commits relating to feature A.
When you then do a PR for feature B because A is not yet merged, you do the pull request from A to B and once again this only has 2 commits, and the PR only has the 2 commits relevant to the feature.
Does that make sense?

@mattheworiordan

When you then do a PR for feature B because A is not yet merged, you do the pull request from A to B and once again this only has 2 commits, and the PR only has the 2 commits relevant to the feature.

But that is what I do. E.g. The last one I created:

Mm, I now see the issue.  Apologies for the confusion, but glad I understand why this happened.
Looking at the branch swift-tests-RSC7 at https://github.com/ably/ably-ios/commits/swift-tests-RSC7, I can see commit 82db599afd3febeff9cdc6e0f00e14d8540e4ea7 which is what I expect to see in this branch (and I expect what you have in your local branch).  However I also see dc48ada0f930f8cc2dee260d5182076238797421 and f71fb9ae1caf80748cf39687f4ba7fd4592616ef.  These two commits shouldn't be in this branch.  Looking then at the merge commit f4f606a155158c22f4a2acfab6f3b690a0a162fc for PR https://github.com/ably/ably-ios/pull/70, I can see that #70 was merged before this branch was merged, and as such the commits from that branch are added to this branch.
So I am not really sure how to get around this problem other than to ensure I merge in PRs in the order they were issued so that we don't end up adding commits from a later PR into an earlier PR that it is based on.
Sorry once again for the confusion, let's try and stick to a rule that PRs based on others should be merged after the parent PR is merged.

@mattheworiordan I agree. I thought about it and I don't see other way than to ensure the merging order.


General Permanent Error on startup

I've installed 1.4.3 on OTA-13 on Ubuntu Touch. It worked great at first and even downloaded my playlist for offline playback. That was last night.
This morning, I'm asked to log in and get the above error message "general permanent error". Each time. I've also logged in via the website to be sure I'm using the correct password.
Searching online for the error surfaces one stackoverflow result, where a coding issue with a similar app was causing login problems.

Hi,
Could you please try the latest version from the Open Store (1.6.1), and let me know if you're still having any problems? https://open.uappexplorer.com/app/com.mikeasoft.cutespotify
Thanks!

Thanks Mike, 1.6.1 isn't any better. But, I tried my username instead of
email (the prompt requests email) and I got in.
I am travelling cross country at the moment so there is a slight chance its
connectivity related. But it seems the login method matters.
--
Sent using Dekko from my Ubuntu device

The prompt requests username, not email. I don't know what I was thinking.


Feature: Added Methods

OVERVIEW
This PR aims to bring a receiver-alike functionality to Tengo, allowing for getters, setters, mutators, and more. Overall, the change makes it much easier to use some OOP principles in Tengo, much as the 'this' keyword does in certain JS applications.
A method declaration is syntactically defined as follows:
//derived from func (r *receiver) method (argument interface{}) {...}
method := func(receiver)(argument) { ... }

This is done to alleviate two major concerns I had with this feature:

The strange 'this' keyword functionality in JS would not be very idiomatic.
Golang methods require a declaration, but Tengo specifically avoids declarations.

Specifics
These proposed Tengo receivers do not carry a guarantee about their underlying type: It could be any index-able Tengo type, or undefined, should the method be called in a non-parent context. For example:
f1 := func(r)() { return r }

a := f1() // a = undefined

m := { f2: f1 }

b := m.f2() // b = m

You may notice that unlike JS, where 'this' contains some scope information no matter the context, Tengo's receivers very often carry undefined as their value.
Another important question is how this is different from a self-capturing closure. e.g:
m := { get: func() { return m }}

a := m.get() // a = m

at first glance, this serves a similar purpose, however the given relationship breaks down if you attempt to copy m.
m := { get: func() { return m }}
o := copy(m)
a := o.get() // a = m, even though we copied it.

This is because closures capture at definition time, whereas receivers capture at call-time. The same operation, when done with a receiver, acts as a method call:
m := { get: func(r)() { return r }}
o := copy(m)
a := o.get() // a = o

Implementation
The implementation of receivers is handled by altering the way free-vars are stored when a method is indexed out of a map or array. At parsing, a look-ahead is performed on any selector or index expressions, in order to see if they directly feed into a call operation. If they do, they mark themselves as being a method call.
At compile time, a select or index expression is then compiled to the OpIndex opcode, with a new flag set afterwards, akin to the spread flag, that indicates whether the given indexing operation should include its context info in the indexed object.
Then finally, at run time, when OpIndex is called with a method flag, it behaves as per usual, except that it attempts to cast the retrieved object as a compiled function, and then if it is successful, copies the function, sets freevar[0] inside of the function as itself (the indexed map/array), and then continues normally.
This copy prevents the given map context from escaping this particular function call.

It is also useful to note that the freevars in compiled functions are now always +1 in length, as the 0th item is reserved for the receiver implementation. If no receiver exists, a placeholder "" freevar is created in order to reserve the space. This is done to streamline the function calls at runtime.
Caveats
This feature does not extend to non-compiled methods, mainly because that would require a huge API change that I do not feel comfortable suggesting. Additionally, I questioned the usefulness of being able to move context out into Go-space.
Accessing methods in any way that is not an "index" or "select" operation results in an undefined receiver. To my mind, this is fine, mainly because those are the places where parent-access is most frequently required.
Continued extensions of this feature
I considered adding a bind keyword to the specification, which would allow a receiver to be permanently bound to a specific map/array.
m := { f: func(r)() { return r }}
fn := bind(m.f)
a := fn() // a = m, even though it was called without context

And while I believe this may be a useful feature, I do think its use is extremely niche.
Benchmarks:
Master:
-------------------------------------
fibonacci(35)
-------------------------------------
Result:  9227465
Go:      60.857359ms
Parser:  46.585µs
Compile: 131.165µs
VM:      3.346390935s
-------------------------------------
fibonacci(35) (tail-call #1)
-------------------------------------
Result:  9227465
Go:      82.520452ms
Parser:  21.779µs
Compile: 87.366µs
VM:      3.444464444s
-------------------------------------
fibonacci(35) (tail-call #2)
-------------------------------------
Result:  9227465
Go:      335ns
Parser:  20.929µs
Compile: 77.084µs
VM:      16.204µs

This Branch:
-------------------------------------
fibonacci(35)
-------------------------------------
Result:  9227465
Go:      63.743294ms
Parser:  44.97µs
Compile: 137.976µs
VM:      3.265088942s
-------------------------------------
fibonacci(35) (tail-call #1)
-------------------------------------
Result:  9227465
Go:      82.495663ms
Parser:  20.835µs
Compile: 128.924µs
VM:      3.373017762s
-------------------------------------
fibonacci(35) (tail-call #2)
-------------------------------------
Result:  9227465
Go:      305ns
Parser:  19.629µs
Compile: 79.299µs
VM:      15.721µs

Thanks for the PR. I'm gonna give this some thought.
At first glance I am comfortable with a feature like this, but I'm not entirely sure about the syntax for declaring the methods.
@d5 thoughts?

Thanks for the PR. I really like the documentation on this change. I thought a lot about adding "methods" in the past, and, I've explored Python-like syntax as well. I will definitely think more about this suggested syntax. What bothers me right now is that the first argument can be either a receiver or just a regular argument at the same time.
I'm curious, what would be the problems if we introduce a new language construct such as "this" or even "context" (maybe we can find an interesting approach that is similar to Go's context)? Just a quick thought.

Thanks for getting to this so quickly, both of you.
I hemmed and hawed over what to do in regard to the a keyword (Obviously it would be "this" I think, just due to convention). Several of my prototype versions used a keyword like that, but it just never felt go-like. The context idea is neat - it could perhaps even be an array of context, with each context on top of the other?
(That would be more difficult to implement, but I did consider it. There was always the question in my mind about how useful that would end up being.)
A ctx object would be interesting though... especially if the most "root" object contained the context from golang.
I'm not certain either way. I landed on this syntax as a kind of call-back to how golang tends to do things.

@geseq Yeah, I considered omitting them from the specification, but because Tengo has no defined classes nor definitions, it made more sense to me to not artificially limit which collection scopes allowed receiver passing.

Syntax
I've  been thinking about the method declaration syntax, and these are a few thoughts I've had on the subject. This is all just speculative brainstorming. I based my ideas off of this python snippet:
class Obj:
   def __init__(self, y):
      self.x = y

   def getX(self):
      return self.x
//...
o = Obj(23)
n = o.getX() //n = 23

Translated to Tengo-ish syntax:
newObj := func() {
   return {
      x: 23
      getX: func(self) {
         return self.x
      }
   }
}

n := newObj().getX() //n = 23

Pros:

The "self" keyword makes the receiver-nature of the method call obvious.

Cons:

Adding "self" to the function definition looks messy, and is a bit obtuse.

If we went with a standard keyword, self should be it IMO. It's more intuitive than the c++/java/JS/c# flavored this. However, we should not include it in the definition (too cluttery) - that said if we did both of those things, it then becomes a compile-time challenge as to how to figure out that a function is in fact a method. The obvious check, I suppose, would be to verify if the self variable is ever accessed while inside a function body, and then modify the FuncLitExpr in order to reflect that.
To avoid that, we could set up a new definition keyword to append to func or to replace func. This version may end up looking something like:
newObj := func() {
   return {
      x: 23
      getX: func method () {
         return self.x
      }
   }
}

n := newObj().getX() //n = 23

Here I am using method as a new keyword. I kinda hate this formatting: it's weird to actually see the word method in code... Maybe that's just a personal thing. And now that I think about it, it doesn't quite make sense to refer to this feature as a 'true' method, because the defined function is not actually bound to the parent map.
Perhaps changing func method to func& or func* would be slightly less jarring?
This format would likely open itself to having a self.parent hierarchy access syntax, which may be a nice-to-have.
However, this idea does make it less intuitive to capture a receiver via a closure.
e.g:
Current Branch
m := {
   grab: func(outer)() {
      return func(inner)() {
         return outer
      }
   }
}

f := m.grab()
f() // returns m

Possible Change with 'Self'
m := {
   grab: func*() {
      outer := self
      return func*() {
         return outer
      }
   }
}

f := m.grab()
f() // returns m

Personally, I think this is relatively niche, but I thought I'd mention it, due to how many hours have been lost figuring out what this means in a JavaScript context. If Tengo can prevent that sort of head-scratching at the syntax level, I think it might be worth it.
Overall though, If we don't do with the syntax proposed in the PR comment, I think that the above snippet is the second-best candidate.

I've spent some time to try this, but, I'm still not quite convinced if we should make this change. This is a significant changes and increases the maintenance costs by a lot (more bugs and edge cases) and makes the syntax a bit more alienating to Go coders in my opinion. But my main concern is maintainability to be honest.
I'm actually more interested in Go's context-like approach: is immutable, can be safely passed around, and, (like @DawDavis mentioned earlier) can be potentially useful if we use it to pass from actual Go context value.

@d5 , I have had half a mind to create a module that includes ctx stuff for Tengo, due to the project I upstreamed this PR from. Is that a direction that you're willing to explore with Tengo moving forward?

I'm sure there will be more details we will have to figure out, but, I think Go-like "context" construct is better because it's more easily understood and very commonly used by most Go coders. One obvious question is should that be explicitly declared? Or should we make it some kind of intrinsic value (or keyword)?

How about this approach?
fmt := import("fmt")

newCgroup := func(name) {
    cg := {name:name, pids:[]}

    cg.addPid = func(pid) {
        fmt.println("add ", pid, " to cgroup ", cg.name)
        cg.pids = append(cg.pids, pid)
        fmt.println("all pids:", cg.pids)
    }

    return cg
}

cg1 := newCgroup("cg1")
cg2 := newCgroup("cg2")

cg1.addPid(123)
cg1.addPid(456)

cg2.addPid(111)
cg2.addPid(222)
cg2.addPid(333)

cg1.addPid(789)

//output:
//add 123 to cgroup cg1
//all pids:[123]
//add 456 to cgroup cg1
//all pids:[123, 456]
//add 111 to cgroup cg2
//all pids:[111]
//add 222 to cgroup cg2
//all pids:[111, 222]
//add 333 to cgroup cg2
//all pids:[111, 222, 333]
//add 789 to cgroup cg1
//all pids:[123, 456, 789]


Clarity on editable lab files

We should make it clear (early on) that the lab files (.md) should be edited directly when doing the exercises. We've had reports of students creating their own .cry files for doing the exercises, and this makes getting the module name (file path) stuff an impediment early on.

We've clarified this in the README.md and in standard preliminary text for each of the labs.  Let's close this.


Please add Unit to the output of a disability assessment

At the moment, "Unit" is greyed-out for a disability assessment, however these are sometimes quantitative (e.g. 6 minute walk test will have an output of "412 meters").  May require a change to the CSV template also?

Minimal change at toolkit and CSV documentation, but yes it require a change


company-quickhelp-frontend error

Hi,
i have something wrong like blow
Company: frontend company-quickhelp-frontend error "Symbol's function definition is void: pos-tip-hide" on command hide

how i to do with it.

Me too

Please provide steps to reproduce this, including platform and emacs version.

Xubuntu 16.04    and  emacs-version "24.5.1"

C-x b  and want to select a buffer-name . can't switch buffer and occur the error.

Okay, and you're running Emacs in a terminal window, or a GTK/X window?
(In any case, see https://github.com/expez/company-quickhelp/issues/64, which I think will solve this problem once merged.)

Thank you for your reply and help. I really use Emacs in a terminal window. And i will have a try soon.

Okay, i remove the old .emacs.d and git clone again, now it is ok in GUI window and terminal window.

my emacs is 25.1.1 and in terminal of mac 10.12.3. I have deleted the old .emacs.d and clone the latest version of .emacs.d but the problem is still occurs

This problem should go away when https://github.com/expez/company-quickhelp/issues/64 is merged upstream.

I believe this is now fixed upstream in company-quickhelp.


Send generic template questions to audience

Send generic template questions to audience that help us to get feed back in single shot.

This feature can not be implemented right now due to limitation of of messenger api.


get error report when using heatmap.pl

(perl /NAS4/lien/Hi-C/scripts_dekkerlab/cworld-dekker-master/scripts/perl/heatmap.pl -i K5__30000__10.matrix.gz -i GM__30000__10.matrix.gz -o K5__GM__30000__10__median)
I just want to test the script (heatmap.pl),but got error report.
The error report:
Can't load '/NAS7/home/caulien/bin/localperl/lib/site_perl/5.26.0//x86_64-linux/auto/GD/GD.so' for module GD: libiconv.so.2: cannot open shared object file: No such file or directory at /NAS7/home/caulien/bin/localperl/lib//5.26.0/x86_64-linux/DynaLoader.pm line 193.
at /NAS7/home/caulien/bin/localperl/lib/site_perl/5.26.0//x86_64-linux/GD/Simple.pm line 160.
Compilation failed in require at /NAS7/home/caulien/bin/localperl/lib/site_perl/5.26.0//x86_64-linux/GD/Simple.pm line 160.
BEGIN failed--compilation aborted at /NAS7/home/caulien/bin/localperl/lib/site_perl/5.26.0//x86_64-linux/GD/Simple.pm line 160.
Compilation failed in require at /NAS4/lien/Hi-C/scripts_dekkerlab/cworld-dekker-master/scripts/perl/heatmap.pl line 13.
BEGIN failed--compilation aborted at /NAS4/lien/Hi-C/scripts_dekkerlab/cworld-dekker-master/scripts/perl/heatmap.pl line 13.
how can I deal with it? Thank you so much!

I think you forgot to export PERL5LIB path in your bashrc file.  Look at this section: https://github.com/dekkerlab/cworld-dekker/#building-and-installing-cworld


data fetching improvements

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#138  👈 (View in Graphite)
#137
#136
#135
#134
#133
#132
main

This stack of pull requests is managed by Graphite. Learn more about stacking.


Library weirdness

Hi,
If I use this package, I get this strange behaviour with the Library where these plugin providers think they always need to update when they do not:

If I check the plugins directory, these plugins exist and are the most up-to-date version.
If I use the Rack @ https://vcvrack.com/downloads/RackFree-2.1.2-lin.zip there is no issue
So it really must be an issue with this build, but very strange, any ideas?

This is because our patch allows installing system-wide plugins to /usr/lib/vcvrack/plugins but Library installs and updates go to your home folder ~/.Rack2.
We should eventually fix the patch to prefer the version in your home directory over the system-wide installed version, since it may confuse users.
I can look into this after my vacation but someone else may already go and bump the _plugin_ver and pkgrel as soon as upstream has a git tag for the new version.

@mysterybear the order of loading plugins is now changed in the patch. Thanks for the feedback.


Encounter environment  bug-->OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.

I encountered environment  bug that is OMP: Error #15: Initializing libiomp5md.dll, but found libiomp5md.dll already initialized.
Therefore, I try to use some code to fix it please reference to below:
import os
os.environ["KMP_DUPLICATE_LIB_OK"]  =  "TRUE" that cna fix it

I don't know if the problem has been solved yet. I'm gonna write it anyway.
I run into a similar problem while using jupyter notebook. so I check libiomp5md.dll in my anaconda file. The result was,
Screenshot 2022-06-19 135321
After that, I try to move out (delete) each file to see if it works. It seems like when I delete the one its path was C:\Users\phudi\anaconda3\Library\bin. the code works fine.
I'm neither an expert nor experienced. So I don't know if this approach has any side effects. But it does work for me.

这是来自QQ邮箱的假期自动回复邮件。你好，我最近正在休假中，无法亲自回复你的邮件。我将在假期结束后，尽快给你回复。


Add merchant nature provides

Closes #654

Thank you, will this appear on this page? https://getmonero.org/community/merchants/

@gavhub It will appear on that page under the "Goods" section after this
pull request is merged. (Hopefully soon)


Ensure equality when hashing default args and no args in actions

Summary of the Pull Request
#10297 found a bug in ActionMap where the ToggleCommandPalette key chord could not be found using GetKeyBindingForAction.
This was caused by the following:

AddAction: when adding the action, the ActionAndArgs is basically added as {ToggleCommandPalette, ToggleCommandLineArgs{}} (Note the default ctor used for the action args)
GetKeyBindingForAction: we're searching for an ActionAndArgs structured as {ToggleCommandPalette, nullptr}
Since these are technically two different actions, we are unable to find it.

This issue was fixed by making the Hash(ActionAndArgs) function smarter! If the ActionAndArgs has no args, but the ShortcutAction supports args, generate the args using the default ctor.
By making Hash() smarter, everybody benefits from this logic! We can basically now enforce that ActionAndArgs{ <X>, nullptr } == ActionAndArgs{ <X>, <default_ctor> }.
Validation Steps Performed

Added a test.
Tested this on #10297's branch and this does fix the bug

#It seems static InternalActionID Hash(const Model::ActionAndArgs& actionAndArgs) might have some hash collisions for non-equal inputs but each of its callers assumes that InternalActionID being equal means the ActionAndArgs is equal. That's not caused by this PR, though.

This can't be serviced to Stable as that code doesn't exist in Stable. Be careful with those servicing tags...

My bad. Wasn't sure if ActionMap was in stable or not. Removing the tag.


add Map::retain method

[x] I've included my change in CHANGELOG.md

Codecov Report
Patch coverage has no change and project coverage change: -0.37 :warning:

Comparison is base (8fa9995) 85.65% compared to head (b4db797) 85.29%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #460      +/-   ##
==========================================
- Coverage   85.65%   85.29%   -0.37%
==========================================
  Files          61       61
  Lines        7760     7793      +33
==========================================
  Hits         6647     6647
- Misses       1113     1146      +33

Impacted Files
Coverage Δ

src/value/mod.rs
46.42% <0.00%> (-3.96%)
:arrow_down:

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

Force-pushed accordingly, thanks for the great review :D .


add rds mapping for t4g.xlarge

To clear the following:
No mapping found for RDS instance type for db.t4g.xlarge

I wonder if we could get these default value programmatically?

I wonder if we could get these default value programmatically?

I think we could at least make a script and include it with the alert. I have a couple of ideas


Allow omitting "dirty" from the version string.

NumPy patches its license files with platform appropriate information before building release wheels, consequently all the version strings are marked "dirty". We have fixed that locally by replacing "--dirty" by "--dirty=" in the git describe calls, but it would be nice if there was a setup.cfg option like "show_dirty" that achieved the same result.

There are existing styles that do not include dirty. See How do I select a version style?
Do any of those suffice? If not, I feel like adding an additional style would be conceptually simpler than adding another configuration option.

When you turn an option into an enumeration entry you then just end up with a linear matrix of all the option...  combinations?  Or just an enumeration of projects that use versioneer.

Do any of those suffice?

What I would like is pep440 style without the [dirty].