fix null parameter being mistaken for the string type

Always try to set the DbType of the pameter to avoid the null value being mistaken for the string type.
code
var data = connection.ExecuteQuery<decimal?>("select @value", new { value = (decimal?)null }).First();

exception
System.InvalidOperationException
  HResult=0x80131509
  Message=No coercion operator is defined between types 'System.String' and 'System.Nullable`1[System.Decimal]'.
  Source=System.Linq.Expressions
  StackTrace:
   at System.Linq.Expressions.Expression.GetUserDefinedCoercionOrThrow(ExpressionType coercionType, Expression expression, Type convertToType)
   at System.Linq.Expressions.Expression.Convert(Expression expression, Type type, MethodInfo method)
   at System.Linq.Expressions.Expression.Convert(Expression expression, Type type)
   at RepoDb.Reflection.Compiler.ConvertExpressionToTypeExpression(Expression expression, Type toType) in D:\Code-git\RepoDB\RepoDb.Core\RepoDb\Reflection\Compiler\Compiler.cs:line 574

analysis
Expression generated by Compiler.GetPlainTypeToDbParametersCompiledFunction is
DbCommand.CreateParameter("name", value, new Nullable<DbType>());

When the third parameter is not specified and the value is null, sql server will treat the parameter as a string.
So DbDataReader.GetFieldType(n) will return DbType.String, the read Expression will use DbDataReader.GetString(n), and then the string will be converted to the return type decimal and an error will occur.
So this PR is mainly to set Parameter.DbType as much as possible to avoid misjudgment of the type when it is null.
If you have any questions, please let me know, and I will modify it as soon as possible.
thank

Thanks for this PR, we will review and revert to you soon. Btw, we just pushed the newly build and might be the last build of this year. So please let us know if this needs to be on beta release so we can issue it for you ASAP.

No time pressure, no need for beta.
thank

The processing method has been changed.
Use ClientTypeToDbTypeResolver instead of TypeMapper.fallback.
And Remove unnecessary logic.
Please review again.
thanks

The processing method has been changed.
Use ClientTypeToDbTypeResolver instead of TypeMapper.fallback.
And Remove unnecessary logic.
Please review again.
thanks

I just finished the review for this and I will do the merge now 😺 . Though it is up to you if you would like to make an additional push on the minor comments I made, but the logic is now okay and reviewed.
Thank you always and please continue to do and maturize this library 🚀

I just finished the review for this and I will do the merge now 😺 . Though it is up to you if you would like to make an additional push on the minor comments I made, but the logic is now okay and reviewed.
Thank you always and please continue to do and maturize this library 🚀


Recent update seems to have broker Apple Home Integratio

Suddenly seeing non-response areas for Envoy items in Apple Home and also getting errors in Homebridge on start of child bridge with recent release (9.3.4 now) suggesting Homebridge needs to be version2.0> and "Enphase, Error: Requesting inventory error: enserblesis not defined,trying again."
Will moving to HB 2.0 fix this?  I'm running other plugins so perhaps a roll back to one of the Version 8's of the Enhphase plug-in?

Screenshot 2024-08-31 at 3.56.44 PM.pdf
Screenshot 2024-08-31 at 3.54.44 PM.pdf

fixed in 9.3.5


feat: Migrate from docker-compose to kubernetes

Pytest-splunk-addon migration from docker to kubernetes.

All the tests are executing by spinning up the kubernetes resources (Splunk, SC4S, UF). (Github Actions, local)
Once all the tests will be executed, in the SessionFinish all the kubernetes resources will be destroyed. (If --keep-alive is not passed)
To execute addons test using --splunk-type=kubernetes, please find the steps here: https://github.com/splunk/pytest-splunk-addon/blob/test/migrate-k8s-poc/README-test.md

Let's not merge this one to main, but to develop.

What is the time difference in running these tests using Kubernetes comparing to Docke?

By implementing parallelisation, the PSA CI/CD test execution time has been reduced to approximately 35 minutes.

The proposed solution doesn't work on mac and windows. Also, we should consider and redesign the architecture IMHO we cannot base on subprocess and execute the external command as long PSA is a python package. Things like jq, kubectl and crudini should be replaced by Python implementation. eg kubectl implementation should be done using official https://github.com/kubernetes-client/python lib. We should also avoid hardcoded sleep with magic numbers and improve logging. Spinning up tests can hang for a long time (1h+) without any information. Any manual precondition should be automated. It will be good if we will make a health check before spinning up env.

Crudini has been replaced with addonfactory-splunk-conf-parser-lib, and jq is also replaced with re. Kubectl utility has been replaced with kubernetes-client and shell scripts has been replaced with the python based methods to create and destroy kubernetes resources. Also, retry mechanism has been implemented for kubernetes resources creation.

Let's not merge this one to main, but to develop.

PR for develop: https://github.com/splunk/pytest-splunk-addon/pull/569, will close this after PR of develop gets merged.

PR for main: https://github.com/splunk/pytest-splunk-addon/pull/575, will close this after mentioned PR will get merged.


TQDM Progress Bar doesn't work with Native Notebooks

It's outputting it all and not overwriting per step.

I get a similar issue in the Python interactive window on macOS. Works fine on Linux.

@fonnesbeck Please could you file a separate issue, this issue tracks the bug related to the Preview Notebook Editor.

@DonJayamanne will do, apologies.

@fonnesbeck No need to apologise & thanks for creating the new issue


Misspelling in exception

apistar.exceptions.ConfigurationError: Route wtih name "welcome" exists more than once. Use an explicit name="..." on the Route to avoid a conflict.
apistar/components/router.py, line 27, in init

PR here: https://github.com/encode/apistar/pull/348

Obsoleted by the upcoming #400. Thanks!


[Feedback] error when using headless init

Page: /cli/usage/headless
Feedback:
I get this feedback in the CLI after attempting to use the headless init described on this page.
Note: It is recommended to run this command from the root of your app directory

For more information on AWS Profiles, see:
https://docs.aws.amazon.com/cli/latest/userguide/cli-configure-profiles.html

⠧ Initializing your environment: dev(node:89636) UnhandledPromiseRejectionWarning: Error: connect EPERM <IP_ADDRESS>:443 - Local (<IP_ADDRESS>:0)
    at internalConnect (net.js:921:16)
    at defaultTriggerAsyncIdScope (internal/async_hooks.js:296:12)
    at GetAddrInfoReqWrap.emitLookup [as callback] (net.js:1063:9)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (dns.js:69:10)
(node:89636) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:89636) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
⠋ Initializing your environment: dev

The last line shows a spinner infinitely.
Initializing your environment: dev
Here is my script to initialize amplify.
#!/bin/bash
set -e
IFS='|'

# required
AMPAPPID="${1}"

# dev,qa,prod
AMPENV="${2:-dev}"

# Headless Init resources:
# https://docs.amplify.aws/cli/usage/headless

AWSCLOUDFORMATIONCONFIG="{\
\"configLevel\":\"project\",\
\"useProfile\":false,\
\"profileName\":\"default\",\
\"accessKeyId\":\"$AWS_ACCESS_KEY_ID\",\
\"secretAccessKey\":\"$AWS_SECRET_ACCESS_KEY\",\
\"region\":\"$AWS_REGION\"\
}"

AMPLIFY="{\
\"appId\":\"$AMPAPPID\",
\"projectName\":\"l12n\",\
\"envName\":\"$AMPENV\",\
\"defaultEditor\":\"code\"\
}"

REACTCONFIG="{\
\"SourceDir\":\"src\",\
\"DistributionDir\":\"build\",\
\"BuildCommand\":\"npm run-script build\",\
\"StartCommand\":\"npm run-script start\"\
}"

FRONTEND="{\
\"frontend\":\"javascript\",\
\"framework\":\"react\",\
\"config\":$REACTCONFIG\
}"

PROVIDERS="{\
\"awscloudformation\":$AWSCLOUDFORMATIONCONFIG\
}"

amplify init \
--amplify $AMPLIFY \
--frontend $FRONTEND \
--providers $PROVIDERS \
--yes

My goal is to run the script above on a Jenkins server. For now, I invoke the script above on my local terminal like this, from package.json
  "scripts": {
    "server": "amplify mock",
    "amplify-init-dev": "AWS_ACCESS_KEY_ID=$(aws configure get aws_access_key_id) AWS_SECRET_ACCESS_KEY=$(aws configure get aws_secret_access_key) AWS_REGION=$(aws configure get region) ./amplify-init-cicd.sh OMITTED dev",
    "amplify-init-qa": "AWS_ACCESS_KEY_ID=$(aws configure get aws_access_key_id) AWS_SECRET_ACCESS_KEY=$(aws configure get aws_secret_access_key) AWS_REGION=$(aws configure get region) ./amplify-init-cicd.sh OMITTED qa",
    "amplify-init-prod": "AWS_ACCESS_KEY_ID=$(aws configure get aws_access_key_id) AWS_SECRET_ACCESS_KEY=$(aws configure get aws_secret_access_key) AWS_REGION=$(aws configure get region) ./amplify-init-cicd.sh OMITTED prod",
  }

@cyrfer What OS, Amplify Version and Node Version are you using?

closing the issue for lack of response.
feel free to open another issue if you are still blocked.

@UnleashedMind @ammarkarachi please reopen. I’m on OS X high Sierra. Node 12. All recent Amplify versions.

Hey @cyrfer, I tried to reproduce this on Amplify CLI version 4.43.0. I used the same script you provided and the script was executed and it initialized the project without any errors. Could you confirm if you are still facing this issue?
I further searched for the error you mentioned, and it looks like a similar issue - (1, 2) is known with aws-sdk-js that occurs when running the code in an environment that doesn't have profiles configured.

I think the issue was my local environment. I have not attempted this since the initial post. However, many other errors stopped happening when I upgraded my local to newer than node 12. I might revisit this soon.

@cyrfer Thanks for the update will close this for now


Enshrine existing always-email-updates policy into Privacy Statement

1. What's the name of the policy?
https://github.com/github/site-policy/blob/master/Policies/github-privacy-statement.md
2. Is this issue related to a specific section within one of our policies (e.g. the Terms of Service)? If so, please include a link to the section or subsection.
https://github.com/github/site-policy/blob/master/Policies/github-privacy-statement.md#changes-to-our-privacy-statement
5. Why do you think this section or language needs improvement?
This section implies that the user may have to manually check the GitHub website at least as often as every 30 days in order to know whether the Privacy Statement has changed.  Since historically GitHub always updates users by email (in addition to updating the website), make it easier for users to comply by simply stating what already happens in practice.
In particular, "posting a notice on our home page or sending email" should be changed to "posting a notice on our home page and sending email" - the only modification here is "or" -> "and".
With the above change, users will not have to check the GitHub website frequently to see if a change has been made - instead they can rely on receipt of an email to determine whether that has occurred.

On Fri, Jul 28, 2017 at 05:46:52PM +0000, Denver Gingerich wrote:

In particular, "posting a notice on our home page or sending email"
should be changed to "posting a notice on our home page and sending
email" - the only modification here is "or" -> "and".

There's similar language a few sections earlier 1:
… and we will notify you on our website or by email before any
transfer of your User Personal Information.
In both cases, one interpretation is yours, where GitHub may
unilaterally decide which channel to use.  Another interpretation for
conditional email (which I think it more likely) is that the user may
have opted out of receiving these types of emails (although I can't
find setting for toggling emails for those reasons).
I think we can clarify both cases using a pattern like:
… on our website and{, if you've enabled {whatever setting},} by email…
Where {whatever setting} is a link to the appropriate setting widget,
and we skip the whole conditional if there is no way to opt-out of
that email.
This wording also doesn't distinguish between “on our home page” and
“on our website” (e.g. possibly via 2).  For things like policy
changes, I think users hitting most github.com pages should be
notified of the change without having to hit https://github.com/
itself.

Since historically GitHub always updates users by email (in addition to updating the website), make it easier for users to comply by simply stating what already happens in practice.

To be fair, GitHub has never updated users by email until about three weeks ago — this is the first time we've ever tried mailing our users about a Terms of Service change, and it was because we were announcing this new site policy repository.
Now that we have established this repository as our primary means of communicating policy changes to our users, we will probably update our Privacy Statement and Terms of Service to refer people to it.
That said, please understand that what this policy means:

We will provide notification to Users of material changes to this Privacy Statement through our Website at least 30 days prior to the change taking effect by posting a notice on our home page or sending email to the email address specified in your GitHub primary account. For changes to this Privacy Statement that do not affect your rights, we encourage visitors to check this page frequently.

...is that we will actually notify you of changes that affect you. You don't have to keep checking the web page and looking at the Terms of Service or Privacy Statement; we'll let you know if something that affects your rights has changed. If something changes that doesn't affect your rights, like us fixing a typo or changing an address, we won't send a notification about that. Because that would get annoying pretty fast.


python310Packages.google-cloud-tasks: 2.10.0 -> 2.10.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.google-cloud-tasks is: "Cloud Tasks API API client library"
meta.homepage for python310Packages.google-cloud-tasks is: "https://github.com/googleapis/python-tasks"
meta.changelog for python310Packages.google-cloud-tasks is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 2.10.1 with grep in /nix/store/ba910lvfp17biid73ipnxyb9w9cbbhdk-python3.10-google-cloud-tasks-2.10.1
found 2.10.1 in filename of file in /nix/store/ba910lvfp17biid73ipnxyb9w9cbbhdk-python3.10-google-cloud-tasks-2.10.1

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.google-cloud-tasks
python39Packages.google-cloud-tasks

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ba910lvfp17biid73ipnxyb9w9cbbhdk-python3.10-google-cloud-tasks-2.10.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.google-cloud-tasks https://github.com/r-ryantm/nixpkgs/archive/b6edb4f49cc5e2e43d5676c4ed3efda9fd585f6b.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/ba910lvfp17biid73ipnxyb9w9cbbhdk-python3.10-google-cloud-tasks-2.10.1
ls -la /nix/store/ba910lvfp17biid73ipnxyb9w9cbbhdk-python3.10-google-cloud-tasks-2.10.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.google-cloud-tasks
python39Packages.google-cloud-tasks

Maintainer pings
cc @SuperSandro2000 for testing.

Result of nixpkgs-review pr 186189 run on x86_64-darwin 1

2 packages built:

python310Packages.google-cloud-tasks
python39Packages.google-cloud-tasks


feat(root): add cspell to lint grammar

Summary of the changes
Integrates cspell to the repo
Related issue
#2093
Checklist
General

[ ] Changes to docs package checked and committed.
[ ] All acceptance criteria reviewed and met.

Testing

[ ] Relevant unit tests and visual regression tests added.
[ ] Visual testing against Figma component specification completed.
[ ] Playground stories in React Storybook up to date, with any prop changes and additions addressed.

Accessibility

[ ] Accessibility Insights FastPass performed.
[ ] A11y unit test added and yields no issues.
[ ] A11y plug-in on Storybook yields no issues.
[ ] Manual screen reader testing performed using NVDA and VoiceOver.
[ ] Manual keyboard testing for keyboard controls and logical focus order.
[ ] Correct roles used and ARIA attributes used correctly where required.
[ ] Logical heading structure is maintained, and the HTML elements used for headings can be changed to fit within the wider page structure.

Resize/zoom behaviour

[ ] Page can be zoomed to 400% with no loss of content.
[ ] Screen magnifier used with no issues.
[ ] Text resized to 200% with no loss of content.
[ ] Text spacing increased as per the WCAG 1.4.12 success criterion with no loss of content.

System modes

[ ] Browser setting 'prefers reduced motion' tested. No animations or motion visible whilst this setting is on.
[ ] Windows High Contrast mode tested with no loss of content.
[ ] System light and dark mode tested with no loss of content.
[ ] Browser support tested (Chrome, Safari, Firefox and Edge).

Testing content extremes

[ ] Min/max content examples tested with no loss of content or overflow.
[ ] All prop combinations work without issue.
[ ] Tested for FOUC (Flash of Unstyled Content) in both SSR (Server-Side Rendering) and SSG (Static Site Generation) settings.
[ ] Controlled and uncontrolled input components tested.

Hi @evenstensberg, thank you for your contribution! Please have a read of our CONTRIBUTING.md for info on how to format commits in the ic-ui-kit repo

@GCHQ-Developer-112 will fix commits tomorrow 👍🏾

@GCHQ-Developer-112 will fix commits tomorrow 👍🏾
Edit: Do I also need to amend the individual commits? If you merge this, you can just have one commit which is the PR title.
2nd edit: commitlinting done, waiting for feedback about merging 1st commit or both of them in this pr

Hi @evenstensberg, please create a commit for each scope - scoping commits correctly is important for our release process and for an accurate record of changes in the CHANGELOG.md

@GCHQ-Developer-112 okay. Maybe we should merge the main commit first (integration of cspell) and start linting each mono-repo package in a separate pr?

@GCHQ-Developer-112 okay. Maybe we should merge the integration of cspell first, then the fixes of spelling in seperate prs?

One PR with multiple commits is fine, given that the work is related. It makes it easier for us to review and keep track of the changes related to the spell checker

@GCHQ-Developer-112 All source code is now linted. FYI, you might need to update the snapshots that contain wrong wording.
I imagine this will take some time to review, so here's some more information that's good to know:

The "words" prop in the cspell json file contains all the words cspell didnt find. After you've reviewed, we can gradually remove some words if you find any wrong ones.
After reviewing the code, update snapshots and do tests on this branch/PR.

Let me know if you have any questions.

Hi @evenstensberg, I can see you've made a commit per word added to .cspell.json. This isn't needed. For this PR, you only need 5 commits as the changes are in 5 scopes: root, web-components, react, canary-web-components and canary-react. Please squash all the commits within the same scope into one commit e.g. all the changes in the root directory should be in one commit with a commit message that summarises the changes made within the root directory

@GCHQ-Developer-112 Okay. I thought it would be better for you to review. If one word is wrong, we can just revert the word  along with the word fix. Fixing this tomorrow.

@GCHQ-Developer-112 Okay. I thought it would be better for you to review. If one word is wrong, we can just revert the word along with the word fix. Fixing this tomorrow.

Ah no. Having this many commits makes it harder to review as part of our review process is making sure that the changes in the commits are scoped correctly. If there are any changes that need to be made, I advise using an interactive rebase

@GCHQ-Developer-112 Done rebasing :)

@GCHQ-Developer-112 Done rebasing :)

Thank you for making these changes. It's not quite ready to be approved yet. The commits are still not scoped correctly. Each scoped commit should only include changes related to the associated directory or sub-directory. For example, in the screenshot below, is a commit you've scoped to canary-react. In this commit, there should only be changes made within the canary-react sub-directory.

Please can you also clean up the commit message. Currently where the commits have been squashed, the previous commit messages have been added. They are not needed. My apologies, I should have said when you do the interactive rebase and squash the commits, it's best to pick the fixup option so the commit messages aren't melded together.

Closing as it's a duplicate PR (new PR: #2115)


When viewing branches, the diff doesn't ignore whitespace

If you are viewing a branch, for example:
https://bitbucket.org/owner/app/branch/some_branch_name, ideally the "w=1" parameter is added.

@stevebeck89, the org I'm with is no longer on Bitbucket so I'm not maintaining this Chrome extension anymore. Let me know if would be interested in taking over the project.


Lab 3

If there are only 2 graded exercises for the third lab, why does the challenge website say "You have completed 2 out of 6 questions?"

There is another part of Lab 3 that will be released on the 10th of this month

why make it so confusing then? it doesn't say this anywhere

The challenge website incorrectly reports the number of completed questions. There are only two graded exercises for the third lab, but the website incorrectly states that two out of six questions have been completed. This discrepancy is likely due to an error in the website's tracking mechanism.

here is another part of Lab 3 that will be released on the 10th of this month

Is there mentioned anywhere?


Test ResizeObserver's callback method

Documentation Feedback
Testing an app that uses a ResizeObserver instance in which a callback method assigns a new value to a ref will result in a incomplete coverage.

Documentation could be enhanced by explaining the appopriate way to implement such testing procedure.

Can you provide a minimal repro?


Add E2E

Codecov Report

Merging #25 (862732f) into main (ebf1c2d) will increase coverage by 3.03%.
The diff coverage is n/a.

@@             Coverage Diff             @@
##             main       #25      +/-   ##
===========================================
+ Coverage   96.96%   100.00%   +3.03%
===========================================
  Files          19         3      -16
  Lines          99         7      -92
  Branches       15         2      -13
===========================================
- Hits           96         7      -89
+ Misses          3         0       -3

Impacted Files
Coverage Δ

src/components/BtcRate/BtcRate.component.tsx
100.00% <0.00%> (ø)

...onents/FormInputError/FormInputError.component.tsx
100.00% <0.00%> (ø)

src/api/btc/get/btc-get.handler.ts

src/api/errors/ValidationErrorResponse.ts

src/api/validation.ts

src/api/btc/btc.service.ts

src/api/login/login.validation.ts

src/api/utils/methodNotAllowedResponse.ts

src/api/notFound.handler.ts

src/api/utils/jsonResponse.ts

... and 8 more

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 ebf1c2d...862732f. Read the comment docs.


More logs needed for efficient debugging

More logs make it easier to debug and trace issues on sentry.
Almost every part of the code needs more logs. Debug logs are best for reporting variables before an exception occurs when used in a loop. They're best used when it's not needed for normal review of the process status, just for when things go wrong.
Use from sanic.log import logger to log.
Places where additional logging is needed:
helpers/ratinghelper.py
helpers/statshelper.py
db/models.py (lots of utility functions)

Fixed quite a  while ago.


Should not highlight object properties - it's not a reserved word

VSCode Version: 1.6.0
OS Version: Windows 7

Steps to Reproduce:
This is about javascript and typescript.

Create the following object:

let myObj = {
  in: '123',
  of: '9876',
  delete: () => {},
  instanceof: false,
  as: '',
  is: 'something',
  new: () => {},
  typeof: '',

  yo: '!'
}

Try to access any of the props of myObj and all of them, but yo, will be highlighted as a reserved word.

myObj.in // highlights 'in', as a reserved keyword
myObj.instanceof // highlights 'instanceof', as a reserved keyword
// and on and on
myObj.yo // works properly

Just as a comparison, atom doesn't highlight any of those properties.

Regex that'll have to be fixed:
https://github.com/Microsoft/vscode/blob/master/extensions/javascript/syntaxes/JavaScript.tmLanguage.json#L256,
https://github.com/Microsoft/vscode/blob/master/extensions/typescript/syntaxes/TypeScript.tmLanguage.json#L275
and
https://github.com/Microsoft/vscode/blob/master/extensions/typescript/syntaxes/TypeScriptReact.tmLanguage.json#L255
I'm going to prepare a PR.

@ericmdantas we have created a new grammar that is in beta right now? Can you try it from the marketplace to see if it resolves your issue?
If it doesn't resolve your issue please open an issue / PR on the grammar's repo

@waderyan it's working as expected, thanks!


repos: add option include_all_branches to template repo request

This option, when set to true, the created repository will get files
from all the branches, not just the default branch.
See create-a-repository-using-a-template for more information.

Thank you, @zhouhaibing089 !
Please run go generate ./... and then push (please do not force-push in this repo) the changes made to this PR in order to get the tests to pass.
See CONTRIBUTING.md for more information.

@gmlewis: Thanks for the tip. I now followed the guide.


Memory leak when using Typed Memory View and np array of	objects (since 2013)

Hello,
I encountered a problem with my compiled code: the memory is leaking with each call to the cpdef function. Memory profiling shows lots of memoryview objects remaining.
Googling quickly found a couple of similar bug reports, some of them pretty old. The main one, I think, is this one<EMAIL_ADDRESS>I checked the attached test there — the latest Cython 0.25.2 is leaking as well.
Please advise how to avoid this — my Cython functions are executed thousands to millions of times and 200 MB program grows to >10 GB because of the leak.
leaktest.tar.gz

Is anybody looking at these issues at all?

Bump. I'm experiencing this issue, as well.
Repro:
# Compile: cythonize -bi y.pyx

# Run: python -c 'import y; y.main()'

from cpython cimport array
import array
import time
import psutil

cdef f():
	cdef array.array a = array.array('d', [0.0] * 10000)
	cdef double[:] ca = a # Commenting this out prevents the leak

def mem():
	print str(round(psutil.Process().memory_info().rss/1024./1024., 2)) + ' MB'

def main():
	mem()
	for i in xrange(10000):
		f()
	mem()
	time.sleep(1.0)
	mem()

Output:
$ python -c 'import y; y.main()'
10.9 MB
774.6 MB
774.6 MB

Does anyone know of a workaround?

After applying the patch:
$ python -c 'import y; y.main()'
12.96 MB
13.23 MB
13.23 MB

Is this an issue only in Python 2.x or did anyone encounter it also in Python 3?

Only in Python2, by the looks of it:
$ python3 -c 'import y; y.main()'
11.64 MB
12.13 MB
12.13 MB


Application stats

Now we only provide runtime spec (by fukata/golang-stats-api-handler). This is not enough for debugging.
This PR will opens application stats like number of consume, number of publish so that we can detect something wrong on nozzle. Not only application stats, but enables net/http/pprof for tuning. This is initial step. We should add more stats in future.
Now we have three endpoints,

/stats/runtime
/stats/app
/debug/pprof

@CAFxX Please review. It's deployed on our internal lab

The idea is to use watchtower to pull the stats, right?

@CAFxX Yes


updated macupdate-desktop (6.1)

Current hash is incorrect; download fails.

Travis disagrees, but I get the same as you. Restarting.

This is still failing, I've kicked it again.


There is still a problem uploading the file

Right click and then point sftp:upload no problem, but using the shortcut key will need to select the local path, then prompt permission denied

The files on the server after uploading are often blank, and then you can't diff


Promote include name in search

What's the problem this feature will solve?

Currently when a user searches for a particular package, often by the name seen in an include package or from package include class line, the most relevant result is rather often not the top result, leading to potentially incorrect or malicious packages coming up first.
Describe the solution you'd like

I'd like to see the common include name, if it matches the search term, promoted in the results.
Additional context

Go to pypi
Search for pil, or PIL
The actual Pillow package isn't even in the first page of results.
Search for pandas
The top result is "pandas2" whatever that is.
There are likely other criteria that might be useful to promote e.g. downloads, GitHub stars, etc.

Duplicate of #10718.

Duplicate of #5375


Dss support

Added support for reading dss files local and on cloud storage

@barne856 this looks good! A couple suggestions:

Update .python-version with 3.8.14
Put a basic DSS example in the README
Include the pydsstools wheel directly in the repo (maybe in a directory called ./wheels?). Not great obviously but perhaps a bit more reliable than pulling the wheel directly from the current master branch of that external repo.


[BUG] Missing onContextChange callback for version 2.8

Summary
The StrorefrontPreview component is supposed to receive a few arguments one of which is onContextChange callback. For version 2.8 the passed callback is ignored and it is not passed to the window.STOREFRONT_PREVIEW object. That's because it is not present in the list of properties for the StorefrontPreview component in pwa-kit-react-sdk (https://github.com/SalesforceCommerceCloud/pwa-kit/blob/release-2.8.x/packages/pwa-kit-react-sdk/src/ssr/universal/components/storefront-preview/index.jsx)
The version 3 of the component has the onContextChange as property though https://github.com/SalesforceCommerceCloud/pwa-kit/blob/94af623ad8028a0f9bf6776f24d8a1f5e5a37c46/packages/commerce-sdk-react/src/components/StorefrontPreview/storefront-preview.tsx#L30
I needed the callback so I created a workaround. Added in app/components/_app/index.jsx
useEffect(() => {     if (typeof window !== 'undefined' && detectStorefrontPreview()) {       window.STOREFRONT_PREVIEW.onContextChange = (context) => {         console.log('Force onContextChange for 2.8', context)         handleContextChange(context)       }     }   }, [])
This workaround works when deployed to MRT.
The documentation clearly says that this callback can be passed when setting it up for version 2.8. Which leads me to believe that the missing onContextChange in version 2.8 is a bug.
I see two options:

Add the callback to the STOREFRONT_PREVIEW props.
Remove the onContextChange from the documentation for version 2.8

But since it works on MRT, I think it is better to go with 1)
Steps To Reproduce
Pass onContextChange callback with simple console.log
Set preview options from Managed Runtime
Expected result
See the console.log in the browser console showing that callback is called.
Actual result
Nothing happens.
System Information (as applicable)
Browser: Any
Node version: Any
pwa-kit version: 2.8.2
Desktop OS: Any
Mobile Device Info: Any
Additional information

Thanks for letting us know about this @denchev. I'll add a ticket for us to follow up on this.

Thank you for submitting this issue. We have reviewed the issue, but based on the severity of the issue described and the workaround you provided, we do not have plans to fix this issue at this time. Please comment and reopen the issue if you’d like to propose increasing the priority level.


Figure out which intersection surfaces have low/high error pct.

Some polygon intersections work well, others are way off. Find out which ones perform well and which ones don't.

Fixed through e35da75b97c0ded902bb5d0641c1392d21025f71


Tests: Stop invoking UB in AK::NeverDestroyed's tests

Instead of attempting a stack use-after-free by reading an out-of-scope object's data member, let's keep a flag that checks if the destructor had been called in the outer scope.
Fixes #64

Can confirm this fixes #64.


Multiple Gateway Bug on OPNsense 18.7.5_1-amd64

Dear all,
since last upgrade I have several issues on all my OPNsense firewalls with 2 PPPOE:

OPNSense 18.7.5_1-amd64:
2 PPPOE links
routing depending on  firewall rule selecting a gateway (pppoe0 or pppoe1)
All this worked fine between the upgrade :/

netstat -rn show me only pppoe0
public ips are on lo0
My ADSL provider gives me public ip, but they got the same gateway.
I cannot route traffic to the non default gateway with packet filter
This is a major issue from my point of view

Here are candidates from the 18.7.5, assuming you were on 18.7.4 before:
o backend: fix CPU hogging when reading on already disconnected streams
o ports: mpd5 upstream MTU fix
You can switch back to older mpd5 via:
# opnsense-revert -r 18.7.4 mpd5

You can undo patch 942ddc996 for the backend via:
# opnsense-patch 942ddc996

Both require internet connectivity.
From my point of view it's unclear what caused this disruption so let's suspend judgement. :)

PS: you can also revert to 18.7.4 core package directly
# opnsense-revert -r 18.7.4 opnsense

Thanks for your fast answers, rollback will be useful  !
I'm not sure I was on 18.7.4 is there somewhere any history of the updates ?

there should be a file /usr/local/opnsense/version/opnsense.last but it has been deprecated with 18.7.5 now so it may not be accurate or available.

why this issue is tagged as support and not a bug ?

because you receive free support. if we know what to fix or add, we will change it to a bug or feature. :)

sorry for me, the tagg of the ticket should be a bug not a support it confusing somebody who would like to correct an issue. It's like you manage the ticketing as a private project :/

You receive the same gateway for both pppoe connections?

yes this is the same provider with the same gateway but different public IP on each PPPOE.

And this worked with pre 18.7.5 or did you receive different gateways before perhaps?

The configurations didn't changed nope

Yes, but the gateway you receive via LCP is a decision by the provider ...

yes sure and ?

I just try to understand the problem.
So, when you revert back to 18.7.4 all works fine again?

There are two kernel changes in 18.7.4 -> 18.7.5:
https://github.com/opnsense/core/commit/5f5f8bf8
https://github.com/opnsense/core/commit/027d8fc8
Second one being the more likely candidate.
Can you grep and provide the route-to rules in the working state?
# grep route-to /tmp/rules.debug

yes sure:
pass out log route-to ( pppoe0 $IP_GW ) from {pppoe0} to {!(pppoe0:network)} keep state allow-opts label "let out anything from firewall host itself"
pass out log route-to ( pppoe1 $IP_GW ) from {pppoe1} to {!(pppoe1:network)} keep state allow-opts label "let out anything from firewall host itself"
# pass in quick on igb0_vlan100 route-to ( pppoe1 $IP_GW ) inet from {(igb0_vlan100:network)} to $Video_Wildix keep state set prio (4, 4) label "USER_RULE" # e7509540f71ef91623f1a3c10cf06b72
pass in quick on igb0_vlan100 route-to ( pppoe0 $IP_GW ) inet from {(igb0_vlan100:network)} to {any} keep state label "USER_RULE: Default allow LAN to any rule" # 1a8e19dfe7c0b041baf28059c0db7cc2
# pass in quick on igb0_vlan30 route-to ( pppoe1 $IP_GW ) inet proto tcp from {(igb0_vlan30:network)} to {!(igb0_vlan30:network)} keep state label "USER_RULE" # af7c0fe3720b8275c375d4a5f3c75acb

@sachaz is this still the case on 18.7.7 ?

the problem remain at version 18.7.7 .

An idea of where the issue is coming from ?

Firewall : Settings : Advanced : Disable force Gateway ... ticked or not?

Disable force Gateway is unchecked.

Can you enable it for testing? I usually always enable it on Multi WAN setups, otherwise you might have problems with port forwards on both WANs

Timeout.

Disable force Gateway is checked
still not working
a rule with a specific gateway => flow outgoing but not incoming


clean some unused titles

Some titles in docs/imported/community/keps.md reference null content.
This patch cleans them

@grodrigues3 would you take a look at this PR? Since this is an import file, the changes should probably be done "upstream", but we don't have a completely solid import/update pipeline in any automated fashion as yet. At least a couple of the titles aren't in use - wasn't sure if they were placeholders for yet-upcoming content, or if they should be removed per @WanLinghao suggestion.
Do you have an opinion on this PR? Go ahead and accept it, or refuse and request any updates to upstream content?
/cc @chenopis
/assign

/hold

/closed

/close


geopy 2.0

This is a branch where geopy 2.0 development takes place. See #292 for the plan.
All new PRs should still be made against the master branch. I'll port them to this branch by myself.
I'll extensively do force-pushes to this branch, so please don't do anything on top of it.

Closing this PR. All commits have been merged to master in a series of separate smaller PRs (which are linked above this comment).

Released geopy==2.0.0rc1, see https://github.com/geopy/geopy/issues/292#issuecomment-647173056


[Improvement] Using the configOption in RssTezConfig #1303

What changes were proposed in this pull request?
Using the ConfigOption to unify all client and server config style.
Why are the changes needed?
Unify all client and server config style.
Does this PR introduce any user-facing change?
How was this patch tested?

@guixiaowen
Will you continue to commit this PR future ?


[Docs] Expand API parsing and rendering

The Animated module exposes a lot of functionality, including internal classes. This diff extracts properties and classes from modules and renders them recursively.
This also adds Animated to the autogen docs now that they more capable, although it needs way more docblocks and such which will come later.
Before:

After:

@vjeux, can you do a quick review?

Oops, looks like an extra diff got in there - let me get rid of that.

Also cc @hansonw - would be nice to bring these changes into codex and wrap the whole thing into an open source npm module...

Fixed a bug...

Sounds good to me

Looks great @sahrens! :tada:


silx.gui.plot3d.ParamTreeView and silx.gui.widgets.FloatEdit: Added typing + cleanup

Python typing done while working on #3971.
This also removes some unused signals in ParamTreeView editors.
I splitted it in 2 PRs to make it easier to review.

Rebase to fix conflict


Payment method saved even though validation fails

If a card fails zip or cvc validation, and we pass save_payment_method: true the payment method will still be saved. Is this intended behaviour?
const result = await stripe.confirmCardPayment(clientSecret, {
        payment_method: paymentMethod,
        save_payment_method: true,
});

Closing this out for now. If you have further questions, feel free reach out to support!


Windows Support

@k2kobayashi Thank you for your work!
Could you please make it more Windows friendly like you did it with https://github.com/k2kobayashi/sprocket?
The file path rules in crank on windows is a disaster...I think you have already know about it :D

Hi, I don't know what is the exact reason you cannot run on Windows.
crank is implemented for Linux environment as well as sprocket. I think wsl2 may help you to run on windows.


CAMEL-11393: sql-stored - Add support for typeNames and scale in grammar

Thanks. I tried to fix these.

It seems you still use Spring ClassUtils in ParseHelper. Can you check there and update it to use Camel's ClassResolver instead

Sorry for bug. Now it should use.

Thanks for the PR it has been merged. Do you mind closing this?

Btw do you mind opening a new PR to update the docs with new information. Its this file:
https://github.com/apache/camel/blob/master/components/camel-sql/src/main/docs/sql-stored-component.adoc

Thank you. I'll update docs.


UI/UX: Content moderator dashboard

The content moderation dashboard is in desperate need to have a rework. Settings should be easily found and not hidden within layers. It's also way too in the face in some spots.

[x] Content management should be default page after logging in

Closed in #133


Define a Rasa command that bundles all the relevant files for a bot in an archive file

Description of Problem:
Have a CLI command to package all the relevant files for a bot (NLU + Stories training data, configuration, domain, endpoints, credentials, and anything else I might have missed) into an archive (like a tar.gz)
Definition of Done:

[ ] Tests are added
[ ] Feature is documented
[ ] Update changelog

Can't they just use zip?

Yes, but the target demography for this that I had in mind (people new to Rasa) might not know what files to include.

Mhm, so this would pack everything except logs and models?

Yeah

@msamogh I put it in discussion since I am not convinced by the use case behind that and would like to hear the opinion of the others.
@MetcalfeTom You reacted with a thumbs up, what's your take on this?

When would people use this? Assembled everything on their laptop and want to send it somewhere else to train?
Also, this command would be something someone new to rasa doesn't know either; they'd have to either look up what files are required or how to run this command. So basically if this is neccessary it'd be better to clarify what's needed in the docs rather than add this command.

Assembled everything on their laptop and want to send it somewhere else to train?

Yes, that's one of the use cases in mind.

Also, this command would be something someone new to rasa doesn't know either; they'd have to either look up what files are required or how to run this command.

Agreed. But it's also just a matter of convenience. It's simpler to, say, do a rasa bundle rather than handpicking the files.

mhm atm I'd say we rather go and add the command to do this to the documentation. I am not sure we have figured out this workflow of sharing the bot. Initially, I thought this is meant to provide insights and help if there is an issue and that this should be attached to a created gh issue.

So, shall I remove the discussion tag, then?

mhm atm I'd say we rather go and add the command to do this to the documentation

This sounds more like adding the zip command to the docs for me?

yes, that was my intention: do not change code but describe how to achieve the result using standard tools like zip or tar

I think we can remove the discussion label and move this to unplan.
I think it is a good idea, but I think the need isn't strong enough at the moment


Exclude com.github.stephenc.jcip:jcip-annotations from Azure extensions

@jamesnetherton could you please explain, why is the exclusion needed? Don't we perhaps want to ban jcip-annotations altogether?

Why is the exclusion needed

To avoid some dependency convergence check errors. I don't think the dependency has much value on the runtime classpath so figured it was ok if it were excluded.

Don't we perhaps want to ban jcip-annotations altogether?

Yes we can try to do that. I can open an issue.


Updated 7_-_app_tp_onboarding.yaml file to match the latest changes in the Settings screen.

Task/Issue URL:
Description
Steps to test this PR
Feature 1

[ ]
[ ]

UI changes

Before
After

!(Upload before screenshot)
(Upload after screenshot)

Current dependencies on/for this PR:

develop

PR #3378   👈

This comment was auto-generated by Graphite.


Difficulty Using Function Calling in OpenAI Batch API

Confirm this is a feature request for the .NET library and not the underlying OpenAI API

[X] This is a feature request for the .NET library

Describe the feature or improvement you are requesting
I am trying to implement function calling using the OpenAI Batch API as mentioned in the documentation here. The documentation states that function calling is supported in both the Chat Completions API, Assistants API, and the Batch API. However, I am having trouble getting it to work with the Batch API.
Despite following the guidelines provided, I cannot seem to find a way to utilize function calling effectively within the Batch API. If anyone has experience or insights regarding this functionality, I would greatly appreciate your assistance.

Additional context
I have reviewed the examples provided for function calling in the Chat Completions API and Assistants API, but I haven't found similar examples for the Batch API. My goal is to implement a conversational assistant that can process multiple requests in a batch while utilizing function calling to retrieve and respond with real-time data.
I am particularly interested in understanding the specific requirements or limitations when using function calling with the Batch API. If there are any differences in implementation compared to the other APIs, that information would be very helpful.

I think the Batch API in this case is more about delayed execution of a large volume (within 24 hours and with a discount) than about fast parallel processing of requests, which I think you mean and this happens in some other APIs
In general, this is just the same series of Messages, which will contain function calls/results of these calls, and I don't see any difference here


Using ruby json for health rack

for #11

This PR wasn't for master branch, I'm confused now

my last PR all depended on each other  so merging them one by one without conflicts was OK.
sorry should have mentioned it somewhere.


add function about cube render boundary

I add a rendering constraint, a bounding box that controls the extent of the rendered scene.

This is my first time participating in an open source project, adding a rendering constraint function. The format may be a little loose, but I have added code comments. Thank you very much for your open source project.

Thank you so much for introducing new functionality! However, the goal of the main branch is to maintain a minimal example of the viewer. So I prefer not to add too many functions into the main branch. Feel free to push to new branch!


an error in "src\components\start\index.js"

Describe the bug
When I used "yarn run start" in Git Bush, it show "Failed to compile".

The error message is as follows:
src\components\start\index.js
Syntax error: Unexpected token (694:31)
692 |     .then(res => res.data).then(data => {
693 |       console.log("Fetched");

694 |       var event = data.events.[Math.floor(Math.random() * data.events.length)];
|                               ^
695 |       date.setYear(event.year);
696 |
697 |       tmpWdgt.data.date = date.toLocaleDateString("en-US", {

To Reproduce
Steps to reproduce the behavior:

clone project from github
Go to "win11React" file
open Git Bush in this file
type in "yarn"
type in "yarn run start"
and see the error

Expected behavior
Maybe this is a grammar mistake
Actually I have no idea.
Screenshots
The broswer screenshot：

Git Bash screenshot：

Desktop (please complete the following information):

OS: [windows10]
Browser [chrome, microsoft edge]

Additional context
I hope someone answers it... and thanks those answers this problem!

Use npm instead of yarn and see what happens

Use npm instead of yarn and see what happens

I try to use npm but it show the same error.....

Use npm instead of yarn and see what happens

I try to use npm but it show the same error.....

no error for me in npm

remove the error, by removing the dot after data.event

actually it should be fixed as per latest commit, can you check again @ZeHongHe

actually it should be fixed as per latest commit, can you check again @ZeHongHe

It works by removing the dot! Thank you!

this issue should be closed

Thanks for help！


go get -u github.com/gobuffalo/packr/v2/...

go get -u github.com/gobuffalo/packr/v2/...
package github.com/gobuffalo/packr/v2/...: github.com/gobuffalo/packr/v2/...: invalid import path: malformed import path "github.com/gobuffalo/packr/v2/...": double dot

go version go1.11.3 linux/amd64

Go 1.11.3 has a bug that might explain this.
Try upgrading to 1.11.4 (which was released shortly after 1.11.3) or falling back to 1.11.2.

Hmm it's not packaged for Archlinux yet.
I'll close this then. Thanks.


Add debug level logging for library imports

fix https://github.com/Azure/cadl-azure/issues/1201

One thing I wonder is if we shouldn't have individual flags so --debug doesn't get super verbose? E.g. TS has --trace-module-resolution which you can use to understand which libraries are loaded and why.
This seems fine but something to think about going forward probably.

Hhm, yeah that could be a good idea. --trace.module-resolution and then we have have
trace: TraceFlags;

interface TraceFlags {
 "module-resolution"?: boolean;
 "xyz"?: boolean;
}

Just a note on the additional change, the previous PR adding coloring and code preview did require a special logger.browser.ts file which was left quite empty however this change trigger the logger from being used in the playground so updated the browser stub to be accurate


Cannot retrieve any data from simulator using any version

Hello,
I am looked for any SNMP simulator that can be run on docker side and I found this project, but I can't get any data from device.
I tried run snmpsim locally without docker and inside docker. I have prepared data named self.snmprec inside data folder and run it using command:
snmpsim-command-responder --agent-udpv4-endpoint=<IP_ADDRESS>:161 --data-dir=/usr/local/snmpsim/data --process-user=snmpsim --process-group=snmpsim
of course I get logs and information that simulator is listening.
After that I am trying easy snmpwalk
snmpget -v3 -c public -l authPriv -u simulator -A auctoritas -X privatus <IP_ADDRESS> 1.3
and get
No SNMP response received before timeout
I am not sure what I am doing wrong,

Thanks for answerr.
As I mentioned I was also run Simulator without docker, just using python and commands provided im quick start section in documentantion. The same behavior. Even I tried to reach demo.pysnmp.com with provided credentials. The same error. Anything else I am doing wrong?

Which documentation are you referring to? Our team is working on the latest release and snmpsim-lextudio package, but even that remains a work in progress. You will have to wait till we move further, or dig further into the code base yourself.

All other documentation site you visited (created by others) can be out-of-date.

demo.pysnmp.com supports several test credentials, as we documented in this page. simulator isn't one of them.

I am using this page quick start so I believe most updated one for now.
So when I am run command snmpwalk -v2c -c index demo.pysnmp.com 1.3.6 taken from one of example I thought it will returns me the same things as documented but now I am getting Error: No SNMP response received before timeout.

My scenario:
So after running snmpsim-command-responder and trying to send something to this I was getting
Error: No SNMP response received before timeout. but I am not sure if this is the real problem.. as I run docker again now with  <IP_ADDRESS> binding,
This is my Dockerfile
FROM python:3.12-slim RUN pip install pipenv RUN pipenv --python 3.12 RUN pipenv install snmpsim-lextudio RUN adduser --system snmpsim RUN addgroup --system snmpsim ADD data /usr/local/snmpsim/data RUN chown -R snmpsim:snmpsim /usr/local/snmpsim/data EXPOSE 161/udp CMD pipenv run snmpsim-command-responder --agent-udpv4-endpoint=<IP_ADDRESS>:161 --data-dir=/usr/local/snmpsim/data --process-user=snmpsim --process-group=snmpsim $EXTRA_FLAGS
After running it it seems to work, and when I am trying to get something by using this command:
snmpwalk -v3 -c public -l authPriv -u simulator -A auctoritas -X privatus <IP_ADDRESS> 1.3
Simulator is crashing
`  Listening at UDP/IPv4 endpoint <IP_ADDRESS>:161, transport ID <IP_ADDRESS>.<IP_ADDRESS>
Shutting down variation modules:
Variation module "writecache" shutdown OK
Variation module "subprocess" shutdown OK
Variation module "error" shutdown OK
Variation module "multiplex" shutdown OK
Variation module "redis" shutdown OK
Variation module "delay" shutdown OK
Variation module "sql" shutdown OK
Variation module "notification" shutdown OK
Variation module "numeric" shutdown OK
Process terminated
Traceback (most recent call last):
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/carrier/asyncore/dispatch.py", line 45, in runDispatcher
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/asyncore/init.py", line 207, in loop
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/asyncore/init.py", line 188, in poll2
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/asyncore/init.py", line 123, in readwrite
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/asyncore/init.py", line 108, in readwrite
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/asyncore/init.py", line 420, in handle_read_event
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/carrier/asyncore/dgram/base.py", line 170, in handle_read
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/carrier/base.py", line 80, in _cbFun
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/entity/engine.py", line 151, in __receiveMessageCbFun
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/proto/rfc3412.py", line 327, in receiveMessage
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/proto/mpmod/rfc3412.py", line 509, in prepareDataElements
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/proto/secmod/rfc3414/service.py", line 1048, in processIncomingMsg
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/proto/secmod/rfc3414/priv/des.py", line 160, in decryptData
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmpcrypto/des.py", line 76, in decrypt
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmpcrypto/init.py", line 141, in generic_decrypt
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmpcrypto/init.py", line 96, in _cryptography_decrypt
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmpcrypto/des.py", line 45, in _cryptography_cipher
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/cryptography/hazmat/backends/init.py", line 11, in default_backend
ModuleNotFoundError: No module named 'cryptography.hazmat.backends.openssl'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/root/.local/share/virtualenvs/-x-v5uFv0/bin/snmpsim-command-responder", line 8, in
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/snmpsim/commands/responder.py", line 916, in main
File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/carrier/asyncore/dispatch.py", line 50, in runDispatcher
pysnmp.error.PySnmpError: poll error: Traceback (most recent call last):
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/carrier/asyncore/dispatch.py", line 45, in runDispatcher
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/asyncore/init.py", line 207, in loop
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/asyncore/init.py", line 188, in poll2
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/asyncore/init.py", line 123, in readwrite
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/asyncore/init.py", line 108, in readwrite
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/asyncore/init.py", line 420, in handle_read_event
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/carrier/asyncore/dgram/base.py", line 170, in handle_read
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/carrier/base.py", line 80, in _cbFun
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/entity/engine.py", line 151, in __receiveMessageCbFun
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/proto/rfc3412.py", line 327, in receiveMessage
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/proto/mpmod/rfc3412.py", line 509, in prepareDataElements
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/proto/secmod/rfc3414/service.py", line 1048, in processIncomingMsg
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmp/proto/secmod/rfc3414/priv/des.py", line 160, in decryptData
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmpcrypto/des.py", line 76, in decrypt
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmpcrypto/init.py", line 141, in generic_decrypt
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmpcrypto/init.py", line 96, in _cryptography_decrypt
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/pysnmpcrypto/des.py", line 45, in _cryptography_cipher
;  File "/root/.local/share/virtualenvs/-x-v5uFv0/lib/python3.12/site-packages/cryptography/hazmat/backends/init.py", line 11, in default_backend
;ModuleNotFoundError: No module named 'cryptography.hazmat.backends.openssl'
caused by <class 'ModuleNotFoundError'>: No module named 'cryptography.hazmat.backends.openssl'`

Ok I have digging a little more, and tried several scenarios so I have found strange issue.
I write helm chart for me to host this snmp simulator on k8s with service that exposing a node port using UDP. After this finally it started work (probably there was some issues with normal docker earlier).
Because I was used SNMPv3 and when I send a request by snmpwalk like this:
snmpget -v3 -l authPriv -u simulator -A auctoritas -X privatus clusterIP:31161 1.3.6
then this from above exception is throw.
Whenever I am calling the same simulator but for a different SNMP version then everything is working. I tried several times to reinstall this cryptography package but nothing help in this case. Could you please check if SNMPv3 is working on your side for Simulator hosted on docker?
Thanks for help

In short, my team is still working on an up-to-date revision to address documentation gaps. You will have to wait.
But we do finish some very simple guide on this page,
https://docs.lextudio.com/snmpsim-data/#local-simulation
Let us know if that teaches you enough on what you should expect from the simulator.

We didn't fully upgrade the simulator to latest PySNMP yet, so anything can happen (including crashes).
That is on our radar too. We expect to give an update some time next week.

While we are still working on a complete update, the cause of your failed attempt with SNMP v3 is actually clear now.
You can see from the article actually -n switch is needed to specify the context name. Without that, the simulator simply drops your request. The value of context name for a specific emulated device is set to the v1/v2c community name (for whatever reason), which is also the data file name.
So in your case, you need to read the simulator output to learn the right community name and then pass via -n.

Unfortunetly I used -n switch and the same error. In my data I have a lot of data from setup-snmpsim-data.
PS X:\docker-snmpsim-master> snmpget -v2c -c network/wifi/ubiquiti-m5 <IP_ADDRESS> sysDescr.0
SNMPv2-MIB::sysDescr.0 = DisplayString: Linux <IP_ADDRESS> #1 Wed May 21 18:37:41 EEST 2014 mips
Shutting down...
PS X:\docker-snmpsim-master> snmpget -v3 -l authPriv -u simulator -A auctoritas -n network/wifi/ubiquiti-m5 -X privatus <IP_ADDRESS> sysDescr.0
No SNMP response received before timeout

And same exception on simulator side with this No module named 'cryptography.hazmat.backends.openssl.
Also I started considering how should I name files .snmprec to not be forced to add this -n and -c switches for tools. My application which must have a feature to communicate over SNMP to retrieve information from real devices is not have an option to pass something like context names or others. I would select only device ip address, SNMP version, auth key and private key eventually to get the data from this. I assumed that this simulator could help me. But btw did you checked on your side this -n? I am not sure if I am doing something wrong or what?

That seems to be something wrong with your machine, but beyond the scope of this repo or even our own fork.
BTW, we started to add unit test cases for PySNMP/PySMI and now the simulator, so you can refer to cases like this where we specified the context name (public) to match the data file name (public.snmprec). And you can see the test results on all major platforms.

There seems to be something wrong with your machine

So... I have still digged a little bit more. I suppose the problem was with my dockerfile.. For me it was strange as everything was worked when I hosted simulator locally (on my host machine directly) but when I run in the same way on docker side, then this snmpv3 was crashed with this information that no module found.
I seen that you also provide a docker file for this and I tried it and it looks like it was started working.
So I don't know exactly what was the issue, but when I deleted pipenv from my dockerfile, and process-group switch, then SNMP v3 started work correctly.


Minor fixes

Fixed issue #748 again, now tested to work correctly with posts in the system
Suspected fix for all games showing up in the LD-specific games feed (missing parent/superparent method), but I can't easily test. Please confirm.
Added basic  website to automate adding an event in the test server. (sandbox/dev_events.php)

The games definitely have parents (otherwise the website wouldn't work right). I will take a closer look at this in the morning.

Yes, the games have parents but the query does not currently use the parent method to restrict the feed to games with the right parent. So LD39 games shows all LD38 games at the moment.

Ah doh! Okay.


#11 Add template for nginx and dockerized HTTP service

Close #11

Maybe we continue this at a later point.


peer: do not require static remote for peers with legacy channels

This PR updates the peer package to downgrade the static remote key feature bit from required to optional in the case where we have legacy channels with the peer. Without this change, lnd will not connect to peers that do not recognize the feature bit, and any legacy channels with these peers will be unusable.
The last commit in this PR adds a workflow which tests the upgrade path, since we do not have a way to test different versions in our itests. Rather than spin up an eclair mobile node (which does not recognize the feature bit), test test uses lnd 0.7.0-beta, which does not recognize the feature bit, to test the upgrade path. Open question as to whether we want to clean up this commit and include it, left it in for visibility.
Fixes #4800

I think we shouldn't merge it

Agreed, also the bash has begun to sprawl so happy to axe the last commit 😅

sad that it has to go but that's life 😿

Valar Morghulis ⚔
Bash test in personal fork if it's still needed.


The key and value types can't be covariant

The key and value types can't be covariant, for API soundness
e.g. here’s a bad use-case
use papaya::HashMap;

// abuse variance of V
fn extended_lifetime_v(x: &str) -> &'static str {
    let m = HashMap::new();
    m.pin().insert((), x);
    let extended: &str = m.pin().get(&()).unwrap();
    extended
}

// abuse variance of K
fn extended_lifetime_k(x: &str) -> &'static str {
    let m = HashMap::new();
    m.pin().insert(x, ());
    let extended: &str = m.pin().get_key_value(x).unwrap().0;
    extended
}

fn main() {
    let s = "Hello dear friend of use-after-free!".to_owned();
    let r1 = extended_lifetime_k(&s); // either
    let r2 = extended_lifetime_v(&s); // works
    drop(s);
    println!("{r1}");
    println!("{r2}");
}

Hmm, thanks for catching this. Would T: 'static be an appropriate fix?

No, the way to make them invariant would be to replace the PhantomData<(K, V)> in raw::HashMap with something like PhantomData<Cell<(K, V)>>.
T: 'static bounds actually (surprisingly) don't help with variance, as you can still have subtyping relationships such as between Box<dyn for<'a> Fn(&'a str)> and Box<dyn Fn(&'static str)>.

While I'm at it, I'd also like to point out the Sync implementation as problematic. I assume sharing a HashMap<K, V, …> can result in the destructor of K or V values running in a different thread than where they were constructed; in which case HashMap<K, V, …>: Sync should not just require K: Sync, V: Sync, but actually K: Send + Sync, V: Send + Sync.

Ah yes, that is true. I believe both of these issues apply to flurry well.

Just looking at the API docs, for flurry, it seems like their internal usage of AtomicPtr should ensure invariance, and their insert-like methods all require Send + Sync for K and V. I haven't tested it though.
It does make me wonder though; these Send + Sync bounds are effectively even somewhat more restrictive (you can't really use the map at all with non threadsafe types); if there's something about the reclamation via seize that makes simply constraining the Sync implementation of the map itself insufficient.

Ah, I see why this is an issue now. The generics K and V should really be on raw::Table, which is what is stored behind AtomicPtr, to ensure invariance.
I do think flurry's bounds are overly restrictive, seize doesn't internally spawn any threads, so the Send bound would only be necessary if you are able to initiate reclamation from a different thread, i.e. the HashMap is Send or Sync.

Actually I am unsure about this now, but I still think it is correct. If HashMap exposed access to the inner Collector, it would be possible to cause reclamation on another thread without actually sharing the map. Neither flurry nor papaya do this, and the map owns the collector, so I think this is avoided. Additionally, any guards created before transferring ownership of the collector the map must have been dropped or leaked, so no other thread can have been active once the map is created.

I think so, too. The thread-locals all seem contained to the object, so completely single-threaded use would never involve any other threads; and the only other remaining question would be whether HashMap: Send needs Sync on K or V, but I don’t see any way in which any shared access to the K or V could come about in such a case, either. So it seem alright to just to the K & V: Send+Sync for HashMap: Send

Released the fixes in 0.1.7. Thanks for the report!


[Cosmos] Query direct execution with-out query-plan

Describe the solution you'd like
Ability for application to by-pass query-pan and execute the query directly with BE
QueryPlan caching: can it include aggregates as well?
Or direct pass through as option.
ETA: TBD (Risky)
@xinlian12 to update it.
Main feature: #28266

Use disallowQueryPlanRetrieval, also added examples with PR: https://github.com/Azure/azure-sdk-for-java/pull/28431


windows vgpu bugs

new gide text tabs always blank (only sometimes true on mac.)
perhaps relatedly, new gide windows open blank -- need a resize to trigger open.  perhaps use new show event??

seems to be fixed but will track on gide issues if re-occurring.  not a general gi issue -- most stuff works fine.


[Improvement-13911][JSON] Improve the readability of workflow exported json files

Purpose of the pull request

close: #13911
Improve the readability of workflow exported json files

Brief change log

before

after

Verify this pull request
manually tested

Codecov Report

Merging #13912 (2fce888) into dev (f9f88cb) will decrease coverage by 0.03%.
The diff coverage is 0.00%.

:exclamation: Current head 2fce888 differs from pull request most recent head 5d49d7b. Consider uploading reports for the commit 5d49d7b to get more accurate results

@@             Coverage Diff              @@
##                dev   #13912      +/-   ##
============================================
- Coverage     38.90%   38.87%   -0.03%
- Complexity     4457     4461       +4
============================================
  Files          1158     1158
  Lines         42429    42429
  Branches       4776     4772       -4
============================================
- Hits          16505    16493      -12
- Misses        24108    24121      +13
+ Partials       1816     1815       -1

Impacted Files
Coverage Δ

...api/service/impl/ProcessDefinitionServiceImpl.java
35.09% <0.00%> (ø)

... and 3 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more

I've restarted failed CI job. Waiting for CI to pass.


Inheritance of search keywords not working / Vererbung von Such-Schlagwörtern nicht funktional

EN: The inheritance of search keywords (for variants) is currently disabled by default, but cannot be reactivated. After saving, changes made will be automatically revoked.
DE: Die Vererbung von Such-Schlagwörtern (in Varianten) ist aktuell per Default aufgehoben, lässt sich allerdings auch nicht wieder aktivieren. Nach dem Speichern wird die Änderung immer wieder automatisch rückgängig gemacht.

[public] Automated response: This issue is linked to the internal issue https://shopware.atlassian.net/browse/NEXT-34071.
[created from NEXT-34071, comment 485950]

[public] Hello,
Within our company roadmap and work capacity, we try to address each bug or improvement request but admit that not each one will be resolved. To continue our culture of honesty and openness, we are closing this issue to focus on our roadmap on behalf of all Shopware users.
If you feel like this issue is still impacting you, please create a new issue and let us know. Thank you again for your valuable feedback.
[created from NEXT-34071, comment 501235]


Added running site page to documentation

Adding additional documentation - no review

Codecov Report

Merging #16 (4c9cb06) into develop (279656f) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop      #16   +/-   ##
========================================
  Coverage    33.74%   33.74%
========================================
  Files            8        8
  Lines         2886     2886
========================================
  Hits           974      974
  Misses        1912     1912

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 279656f...4c9cb06. Read the comment docs.


Add EFS storage driver

emccode/libstorage#231

The EFS storage driver has been merged into emccode/libstorage on 08/16/2016.


IOS XR specific session password format

Environment

Python version: 3.5.3
Peering Manager version:  master

Steps to Reproduce
Apply a password to a peering session on an IX mapped to a Cisco XR device

Expected Behavior
Password applied as password encrypted 045612150A22595C0C090404011C03162E

Observed Behavior
Password applied as password encrypted 7 045612150A22595C0C090404011C03162E

You could use something like this in a template:
{# Check if the password is encrypted #}
{% if session.password.startswith("7 ") %}
password encrypted {{ session.password[2:] }}
{% else %}
password {{ session.password }}
{% endif %}

A helper filter exposed to the Jinja2 templating engine could help though.


python310Packages.glean-parser: 7.2.1 -> 9.0.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.glean-parser is: Tools for parsing the metadata for Mozilla's glean telemetry SDK
meta.homepage for python310Packages.glean-parser is: https://github.com/mozilla/glean_parser
meta.changelog for python310Packages.glean-parser is: https://github.com/mozilla/glean_parser/blob/v8.0.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.0.0 with grep in /nix/store/idh9ajcikgqnj05n65haz1cgvvwc7mlk-python3.10-glean-parser-8.0.0
found 8.0.0 in filename of file in /nix/store/idh9ajcikgqnj05n65haz1cgvvwc7mlk-python3.10-glean-parser-8.0.0

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

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
mozillavpn
mozphab
python310Packages.glean-parser
python310Packages.glean-sdk
python311Packages.glean-parser
python311Packages.glean-sdk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/idh9ajcikgqnj05n65haz1cgvvwc7mlk-python3.10-glean-parser-8.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.glean-parser https://github.com/r-ryantm/nixpkgs/archive/e1264c57dd34beee9c86b18831511e993d4f2577.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/idh9ajcikgqnj05n65haz1cgvvwc7mlk-python3.10-glean-parser-8.0.0
ls -la /nix/store/idh9ajcikgqnj05n65haz1cgvvwc7mlk-python3.10-glean-parser-8.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages failed to build:

mozphab
python310Packages.glean-sdk
python311Packages.glean-sdk

3 packages built:

mozillavpn
python310Packages.glean-parser
python311Packages.glean-parser

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.glean-parser is: Tools for parsing the metadata for Mozilla's glean telemetry SDK
meta.homepage for python310Packages.glean-parser is: https://github.com/mozilla/glean_parser
meta.changelog for python310Packages.glean-parser is: https://github.com/mozilla/glean_parser/blob/v8.1.1/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.1.1 with grep in /nix/store/hl8b01q4kya4zimw11k1fr9wsrrwa2yq-python3.10-glean-parser-8.1.1
found 8.1.1 in filename of file in /nix/store/hl8b01q4kya4zimw11k1fr9wsrrwa2yq-python3.10-glean-parser-8.1.1

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

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
mozillavpn
mozphab
python310Packages.glean-parser
python310Packages.glean-sdk
python311Packages.glean-parser
python311Packages.glean-sdk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/hl8b01q4kya4zimw11k1fr9wsrrwa2yq-python3.10-glean-parser-8.1.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.glean-parser https://github.com/r-ryantm/nixpkgs/archive/7947a48ef621516002805ac46369bd49923a5e9d.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/hl8b01q4kya4zimw11k1fr9wsrrwa2yq-python3.10-glean-parser-8.1.1
ls -la /nix/store/hl8b01q4kya4zimw11k1fr9wsrrwa2yq-python3.10-glean-parser-8.1.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

3 packages failed to build:

mozphab
python310Packages.glean-sdk
python311Packages.glean-sdk

3 packages built:

mozillavpn
python310Packages.glean-parser
python311Packages.glean-parser

Maintainer pings

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.glean-parser is: Tools for parsing the metadata for Mozilla's glean telemetry SDK
meta.homepage for python310Packages.glean-parser is: https://github.com/mozilla/glean_parser
meta.changelog for python310Packages.glean-parser is: https://github.com/mozilla/glean_parser/blob/v9.0.0/CHANGELOG.md
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 9.0.0 with grep in /nix/store/6dj4fxyp93f4syl5vx9bm8hqysjyji80-python3.10-glean-parser-9.0.0
found 9.0.0 in filename of file in /nix/store/6dj4fxyp93f4syl5vx9bm8hqysjyji80-python3.10-glean-parser-9.0.0

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

6 total rebuild path(s)

6 package rebuild(s)

First fifty rebuilds by attrpath
mozillavpn
mozphab
python310Packages.glean-parser
python310Packages.glean-sdk
python311Packages.glean-parser
python311Packages.glean-sdk

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/6dj4fxyp93f4syl5vx9bm8hqysjyji80-python3.10-glean-parser-9.0.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.glean-parser https://github.com/r-ryantm/nixpkgs/archive/9a42b3e4e8b8f678e8d1d07e349dccb5c2c36ef6.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/9a42b3e4e8b8f678e8d1d07e349dccb5c2c36ef6#python310Packages.glean-parser

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/6dj4fxyp93f4syl5vx9bm8hqysjyji80-python3.10-glean-parser-9.0.0
ls -la /nix/store/6dj4fxyp93f4syl5vx9bm8hqysjyji80-python3.10-glean-parser-9.0.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

6 packages built:

mozillavpn
mozphab
python310Packages.glean-parser
python310Packages.glean-sdk
python311Packages.glean-parser
python311Packages.glean-sdk

Maintainer pings


Copy/Paste on readonly cell will overwrite content

Hi,
Copying one cell, and pasting it on a readonly cell will write the data regardless.
I expect a readonly cell to be really readonly. For such I already provided you with a pull request regarding autofillserial, that also had this problem. And now create this issue reagrding copy/pasting. This copy/pasting logic goes quite a bit deeper in the solution and touches quite a lot of aspects of ReoGrid. So I don't feel confident doing this change without diving a lot deeper into Reogrid. I hope you can help here.
Regards,
Koen

Hi! thanks for the pull request and Issue. Does #33 solve this issue?

It seems the copy action is blocked properly. But I don't see a popup message why not. I took the liberty to look at the change you made, and it seems to suggest a message should be shown to the user.
I'm not sure if my test is proper, though. I hijacked the feature/SetEditableRange demo, and set the cells to readonly instead of making them the only ones you can edit.
However, it is a workable solution for me. The data is readonly cells is preserved, which is what I'm after.
An inconsistancy is now introduced, though. Your fix for copy paste will abort the whole action in case of readonly cells. The pull request I prepared for you that guards readonly cells during autofill serial just ignores the readonly cells, but does provide data to writable cells. I can imagine you'd wish to keep that the same, and abort the AutoFill serial action in case readonly cells are in range as well.

But I don't see a popup message why not. I took the liberty to look at the change you made, and it seems to suggest a message should be shown to the user.

ReoGrid allows application to decide whether show a dialog to end user. This code makes exception happen:
https://github.com/unvell/ReoGrid/pull/33/files#diff-945770d4e9b0480b548f3d87af699e9eR312
To catch it and show a dialog:
workbook.ExceptionHappened += (s, e) =>
{
  if (e.Exception is OperationOnReadonlyCellException)
  {
    MessageBox.Show(this, LangResource.Msg_Operation_Aborted,
      "ReoGrid Editor", MessageBoxButtons.OK, MessageBoxIcon.Stop);
  }
};

As you pointed out, the ReoGrid Editor should do this, I have update the pull request #33.
Shall we do this same check in your pull request #31 for the auto filling feature?

That was my intent by mentioning the inconsistency. I updated the pull request to throw an exception when readonly cells are in range, similar to your fix.


feat(navigation-universal): add <rh-navigation-universal>

What I did

Add the <rh-navigation-universal> element.

Testing Instructions

View the DP for Universal Navigation:

Demo
Bordered (includes a dropdown)
Docs

Compare to Figma and what exists on live properties.

To Do's

[ ] Add docs
[ ] Add tests
[x] Add "All Red Hat" dropdown
[ ] Implement default value for accessible-label in docs

Notes to Reviewers
Right now, there's variant="bordered" which mimics what exists on redhat.com.

This design is not in the Figma library. Should it exist?

If so, designers: make sure everything jives with this variant.

In the Figma Library, there's 16px of padding around each link. This results in what I perceive to be much larger height than what's in production.

Should it be 16px? FWIW, I have it set to 8px as of this writing.

Double check that my values in repoStatus.yaml are correct.
Developers: added an any type to fix Argument of type 'DocumentFragment | undefined' is not assignable to parameter of type 'Node'. Would love some help getting the #getDetailsContentHTML() function properly typed, if applicable.
Some noticeable FOUC. What should we do about that?

We should limit the design to a single universal nav, preferably the right-aligned nav with the borders on hover (like redhat.com). The left-aligned design competes with the RH logo—almost "blocking" the eye, IMO.

@adamjohnson Looks like we also have to also account for personalizations.

@adamjohnson Personalization being the Large retailer delivers ... text in the upper left corner.

@coreyvickery will the info icon (left) and/or chevron (right) change? Or are those spots always those particular icons?

@coreyvickery will the info icon (left) and/or chevron (right) in the personalization message change? Or are those spots always those particular icons?

@adamjohnson Not to my knowledge no, but let's make sure we're using current icons from Brand for both.


Test account.

Test account is not showing test sats.

Verified this issue on dev app v2.0.75(463)


Add Blackpill boards to the compatible demos

This is only to add these popular boards to the demos with compatible transports since the Blackpills support serial and serial-usb. I've tested these demos successfully on ROS Foxy only. Later, I can do the same for ROS Galactic as well.
Signed-off-by: Branilson Luiz<EMAIL_ADDRESS>

@mergfy backport galactic main

Please notify when galactic is tested

Please notify when galactic is tested

Following the suggestion of @Acuadros95, I've tested successfully with fast-DDS.
bash $ sudo apt install ros-galactic-rmw-fastrtps-cpp
And to activate it on each terminal:
bash $ export RMW_IMPLEMENTATION=rmw_fastrtps_cpp

@mergify backport galactic main


python310Packages.pulumi-aws: 5.10.0 -> 5.13.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.pulumi-aws is: "Pulumi python amazon web services provider"
meta.homepage for python310Packages.pulumi-aws is: "https://github.com/pulumi/pulumi-aws"
meta.changelog for python310Packages.pulumi-aws is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 5.13.0 with grep in /nix/store/f5ni46l4f5jxlavnjwnxbx9fcqfnx4vl-python3.10-pulumi-aws-5.13.0
found 5.13.0 in filename of file in /nix/store/f5ni46l4f5jxlavnjwnxbx9fcqfnx4vl-python3.10-pulumi-aws-5.13.0

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.pulumi-aws
python39Packages.pulumi-aws

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/f5ni46l4f5jxlavnjwnxbx9fcqfnx4vl-python3.10-pulumi-aws-5.13.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.pulumi-aws https://github.com/r-ryantm/nixpkgs/archive/3faeb0fe0117905d49d59c11a89e87d7bb983091.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/f5ni46l4f5jxlavnjwnxbx9fcqfnx4vl-python3.10-pulumi-aws-5.13.0
ls -la /nix/store/f5ni46l4f5jxlavnjwnxbx9fcqfnx4vl-python3.10-pulumi-aws-5.13.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.pulumi-aws
python39Packages.pulumi-aws

Maintainer pings
cc @costrouc for testing.

Result of nixpkgs-review pr 190500 run on x86_64-linux 1

2 packages built:

python310Packages.pulumi-aws
python39Packages.pulumi-aws


[ Aesthetics ] Same height for colored panel headers.

The colored panel header is a little shorter.
I think it's because of the lack of a separation line
Maybe you could also add an "invisible" separation line, of the name color as the header.

This seems fixed


npm unfinished package

So I just spent the last week making a fully working react native module for Spotify on iOS and Android, but I found that you had already taken the react-native-spotify package name in npm. It doesn't make a lot of sense to have a react native package that only works on iOS in npm, and since it doesn't seem like you're maintaining it, I was wondering if there's any way you could transfer the package name to me, since I have a module that works in both iOS and Android?
The module is here

No reply ?


Dockerized the application

Is this okay?
@SANTHOSH17-DOT
#8

Docker compose file should be used
Run go run main.go host as well.

I guess if we run
docker compose build
which will build the image
After that if we run
docker compose run --rm are-you-bombed
then the "go run main.go host" will also run

Please review this PR @SANTHOSH17-DOT

It doesn't work that way @i-am-yuvi
We should add a docker-compose file to the project that uses the image configuration(Dockerfile)
You may refer to this example

Okay


Fix typo

occured→occurred

Thanks for the PR, @eltociear!
Eliot

Thanks you too @EliotSeattle !


Fixing NameError in Results#edit

Showing /var/www/markus_apps/csca08f17/app/views/results/edit.html.erb where line #274 raised:
undefined local variable or method `files' for #<#Class:0x0000000751f548:0x007fc32988e9d0>
Did you mean?  @files

Thanks, @MeowsterEric! This is absolutely correct.

Thanks, @MeowsterEric! This is absolutely correct.


Position of comments on analysis (observation): could please be indented better

Example: https://github.com/hl7-be/hl7-be-fhir-laboratory-report/tree/master/testing/Macsys/815333045

Issue made on visualiser github


The demo code has a lot of duplications

The OpenAIAzure and OpenAIAnyscale demos are pretty much copy-pasta of the original OpenAI.
There is a lot of room for refactoring, as well as making it explicit, which capabilities are supported by each provider.
For example, at the moment Azure OpenAI doesn't support the streaming flavor and Anyscale doesn't support chat+vision.

@the-gigi SonarCloud's quality metrics have worsened after merging your PR https://github.com/sashirestela/simple-openai/pull/92. Demo code is not a priority right now. The code to support other vendors needs an overall refactor. Please, don't make more contributions until more news.


Update httptreemux to 3.7.0

What does this PR do?
Thanks to https://github.com/dimfeld/httptreemux/pull/43, we can now use a safe-mode for adding routes during runtime.

👍


fix multiplyTransformTransform doc comment

Fix a doc comment causing issues on https://www.itwinjs.org/reference/core-geometry/cartesiangeometry/transform/multiplytransformtransform/

Nice catch!

@pmconne gets the credit

@mergifyio backport release/4.2.x


manager: simplify implementation of DaemonStates

Simplify implementation of DaemonStates by removing field daemons.

LGTM. Looks like that idxBySnapshotID is not needed anymore too

removed too:)


Fix/27

Create hdbtable parser based on the Antlr4 grammar

New issue is created regarding defaultValue property of columns in hdbtable definition:
https://github.com/SAP/xsk/issues/119


Sidecar manager

See: #26

 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 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.

/test all

/test pull-istio-lint

/test all

/test all

/test all


LLMLingua doesn't work on CPU as device_map

Hi. I've been trying to use LLM Lingua on CPU Linux Machine.  When I start by python file. it just stops like the attached screenshot

The code I'm using is as simple as following:
PromptCompressor(device_map="cpu")

Hi @MrTBH, it looks like out of memory. You might want to try using a smaller model like lgaalves/gpt2-dolly or a quantized version of the model.

In my case
llm_lingua = PromptCompressor(
    model_name="meta-llama/Llama-3.2-1B",
    device_map="cpu",
)

Doesnt detect cpu configuration
RuntimeError: Found no NVIDIA driver on your system. Please check that you have an NVIDIA GPU and installed a driver from http://www.nvidia.com/Download/index.aspx


[web][SIMS #1093] UI updates for Student Application - Start new application page

replaced start new application page with vue form;
added containerClass to FullPageContainer and StudentPageContainer;
changed modal text and button;

I still didn't delete the studentapplication.json. Should I?

I still didn't delete the studentapplication.json. Should I?

Yes @andrepestana-aot.


fix(cli): display internal commands in a subcommand #343

Overview
Put each internal commands in a subcommands visible for all users.
close #343
BTW should I remove the ping command ? (related to the TODO comment in file)
Checklist

[X] Updated the documentation (code documentation, command help, ...)
[x] Tested the change (unit or integration tests)
[X] Amended the changelog in release.nix (see release.nix for instructions)

cc @curiousleo

@curiousleo My bad ! Thanks ! It's up to date now :)

Very nice, thanks for increasing the test coverage! Did you check that this test would have caught the wrong command in shell.rs?
https://github.com/target/lorri/blob/c38e0f09c36a1b27d86eb01ba5672fdffa950641/src/ops/shell.rs#L59

In fact the previous test didn't catch it. Now the new one catch it :)

up

Squashed & rebased on master. Merging once green.


fix: throw correct exception if one uses _version

without primary key in a select statements where
clause

ack


SPM - Resolving Package Graph Failed

Describe the bug

To Reproduce
Steps to reproduce the behavior:

Add rollbar-apple as a dependency

Rollbar-Apple SDK version: v...
2.0.0-beta.14
Calling the SDK from (x-mark all suitable):
[] Objective-C
[x] Swift
[] Other:
Runtime environment (please complete the following information as applicable):

Device: iPhone 11 Pro
OS: iOS
OS version: 14.5

Additional context
Xcode 12.5
Note that version 2.0.0-beta.13 works fine

Thanks @akornich!

@jsahoo , you are welcome! Let me know if you run into any other issues. Also, general feedback on  SDK (its design, API, quality, performance) is very welcome. And of cause, any suggestion for a new feature or improving an existing one is welcome.


Adding a small cube root finding program

It's a python program which uses bisection search method / peak finding.

can you please add hacktoberfest-accepted label? ( I'm a beginner I don't know is it ok to ask for it? )