Make the password parameter optional to support *.cer and *.crt.

#6
2. When give a .cer or .crt in the input than don't ask for a -p (password) as a mandatory inout parameter
I fixed it because I needed it too.

merged!  I'll publish the new version soon.

Hey thanks for adding this feature and the app in general.
I'm also thinking that the passwordKeyPath needs to be made optional too but maybe I've missed something? The use case is when you are using the tool to add a custom/private root certificate. You generally don't have access to the private key and/or don't want to use it out with the CA.
I'm working on a fix for this and can turn it in to a pull request if it would be useful?
Cheers
Dave

Hi @ekwus!  My pleasure.
Yeah go for it, pull requests are more than welcome! :)
Yohan


Update optionsresolver.py

Fix problem with parse queue_consumers_connected

Great! Thank you!
(Related to #24)


IGListStackedSectionController to respect children insets

New issue checklist

[x] I have reviewed the README and documentation
[x] I have searched existing issues and this is not a duplicate

General information

IGListKit version: 2.1.0
tvos version(s): 10.1
CocoaPods/Carthage version: 1.2.0
Xcode version: 8.2.1

Issue
IGListStackedSectionController encapsulates child section controllers.
If insets were set for each separate child section controllers,
insets of the child section controllers are not applied.
Instead, the set inset of IGListStackedSectionController is the only visible change.
Child section controller's insets are not changed, so layout is not desirable.

@ninokierulf Dup with #448


let g:loaded_lightspeed = 1

If you type:
:echom loaded_
and hit TAB
you'll see that well behaved plugins set this flag.
Can you set it too?

Thank you :)

Note that for Lua plugins this is a bit redundant, as you can simply check package.loaded.lightspeed.


Cannot upload in airplane mode, even with wifi on

Summary:
Following #923, it is not possible to click on the "Upload all" button when in airplane mode, even when Wireless is enabled (Wifi is automatically disabled when Airplane mode is activated, but it can be manually re-enabled afterwards - Airplane mode is mainly concerned with disabling the cellular antenna).
I believe the condition implemented in https://github.com/openfoodfacts/openfoodfacts-androidapp/pull/926 is too strict, since I can and frequently scan products while on Airplane mode. Maybe I don't see the exact usage scenario, but it seems that testing "Network connectivity" might be sufficient.
Overall, this is a minor issue since airplane mode can often be disabled without much issue, it's just a bit unexpected. Feel free to close this if not deemed worth of the effort.
Steps to reproduce:

Scan products without connectivity (to add them to the Offline edit list)
Activate airplane mode
Enable wireless
Go to offline edit and click Upload All

Expected behavior:
I should be able to click Upload All, since there is network connectivity via wireless.
Observed behavior:
I got the message about "Airplane mode enabled" described in https://github.com/openfoodfacts/openfoodfacts-androidapp/pull/926.
Device and Android version:
Motorola Moto X Style, Stock Android 6.0 Marshmallow
Screenshots:
(I uploaded the products after leaving airplane mode to test, so I don't have an Offline edit list anymore to easily reproduce it and capture a screenshot)

This is fixed in the PR #3072
Closing this bug


Reading all data sometimes requires socket to close

If I run (with PR #9):
perl6 -Ilib -e 'use IO::Socket::Async::SSL; my $conn = await IO::Socket::Async::SSL.connect("httpbin.org", 443); $conn.print("GET / HTTP/1.1\r\nHost: httpbin.org\r\n\r\n"); react { whenever $conn { .print }; }; $conn.close'
content gets printed up to </html, at which point I have to wait for the connection to timeout before receiving the final >. Adding a Connection: close also works around this.
If I run (with PR #9):
perl6 -Ilib -e 'use IO::Socket::Async::SSL; my $conn = await IO::Socket::Async::SSL.connect("httpbin.org", 443); $conn.print("GET / HTTP/1.1\r\nHost: httpbin.org\r\n\r\n"); react { whenever $conn { .print }; }; $conn.close'
(same as before, but to /ip)
nothing gets printed until the connection gets closed via timeout.

The two code examples look the same to me after five readings; did I really manage to miss it every time or are they the same? :-)
As to the issue - this would happen just to same with IO::Socket::Async, I'd expect. We can't know there's nothing more coming, and we can't normalize without knowing what the next codepoint will be, unless we see a control and then we know we can just spit it out unconditionally since nothing ever combines with a control. This isn't a bug, it's just a consequence of a Str being normalized.
This doesn't seem problematic to me: if you're making a super-cheaty HTTP client then Connection: close is fine and if you're making a non-cheaty one you have to implement it in binary mode (to cope with images etc.) and handle content-length properly anyway.
Unless there's something more than just the final char being delayed here, this counts as "working as designed", I think.

This is why the example in the README used HTTP/1.0, fwiw. :-)

Gah you're right, the second one should have said GET /ip HTTP/1.1
I also totally forgot to do whenever $conn.Supply(:bin), which of course is the proper way.


Add Training Overview Page

Page from old website with all the professional / industry training opportunities.

Information was sent over slack.  Can be added now.

The link of the page is "https://asrg.io/training/"
And I added the company name as well on the list display as we mentioned above.

Hi Usman, looks good, but I have some changes.

Please remove "Company Name:"

Can you remove the "Training" and add a ":"

Removed the word Company

Added " : " and removed the word Training


As a pack CLI user, I can customize stacks

Proposed change to config.toml:
Current:
default-stack-id = “some.official.stack”
[[stacks]]
id = “some.official.stack”
run-images = ["my-org/run", "registry2.org/my-org/run" ]
build-images = ["my-org/build"]
builder = "my-org/builder"

New:
default-stack-id = “my.official.stack:custom”
[[stacks]]
id = “some.official.stack”
run-images = ["my-org/run", "registry2.org/my-org/run" ]
build-image = "my-org/build"
builder = "my-org/builder"

[[stacks]]
id = “some.official.stack:custom”
run-images = ["my-org/run", "registry2.org/my-org/run" ]
build-image = "my-org/build-different"
builder = "my-org/builder-different"

Changes:

Tagging the ID with :something, such that the LABEL contains that ID, but the PACK_STACK_ID env var does not would make it easy to customize stacks with extra packages without breaking buildpack compatibility and without worrying about unsafe rebases (where packages could be missing)
build-images -> build-image -- thinking about this more, there is no reason to specify multiple of these.

From the perspective of a buildpack author (which is what primarily concerns me), seems like a harmless change.  I've got no problem with it beyond the obvious avenue for stack proliferation and fragmentation.
@sclevine What do you think the support obligation for buildpack authors is?  Do you think that we will have a responsibility to ensure that our buildpacks work on these variants since they appear to be the same stack?

It seems to me like it would be the responsibility of the producer of some.official.stack:custom to ensure buildpacks that specify some.official.stack run on this stack.

I think I prefer the mixin approach.
My concern with allowing custom additions and not stating that in PACK_STACK_ID is that the buildpack designed for the custom version of the stack has no way to state that, and so will fail in a confusing way when run somewhere else.
The mixin approach removes my above concern (I think)


Resume from the last completed stage

Hi,
When I use the Ratatosk ,it may have terminated prematurely because out of RAM. The output is Ratatosk_sr.fasta and Ratatosk2.fasta. Is there any way to resume from the last completed stage?
lynn

Hi @lyrk50 ,
Unfortunately no, this is not possible  at the moment.
Guillaume


[Do-Not-Merge]Dev mlservices 2019 10 01 - private repo pr Azure/azure-rest-api-specs-pr#902

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Automation for azure-sdk-for-python

Already approved PR on private repo. https://github.com/Azure/azure-rest-api-specs-pr/pull/902

Already approved PR on private repo
https://github.com/Azure/azure-rest-api-specs-pr/pull/902

Can one of the admins verify this patch?

Automation for azure-sdk-for-go

I'm part of a team that is trying to upgrade the arm-machinelearningservices package for our use.
We were using this version before
and are trying to upgrade to this version in the PR
We are having issues with the operationId: "MachineLearningCompute_ListNodes"
We noticed that even in the example response for amlComputeNodes, it returns a nextLink but in the machineLearningServices.json file, that resource does not have the x-ms-pageable property, thus we have no way to put that nextLink to page through the nodes.
If someone could verify whether or not  "MachineLearningCompute_ListNodes" is pageable, that'd be great.
Note that "MachineLearningCompute_ListNodes" was pageable in the previous version (2018-11-19).

@vrushg-ms Hello. Once the pr is ready, please ping me and help you merge this PR.

@vrushg-ms Hello. Is this PR ready?

@vrushg-ms Hello. Is this PR ready?

@vrushg-ms Hello. Is this PR ready?

We want to merge this on  November 1st.

@MyronFanQiu , The PR is now ready for merging


Feat: Kusion server supports updating workspace.yaml via API

What would you like to be added?
Kusion server supports updating workspace.yaml via API
Why is this needed?
Kusion server supports updating workspace.yaml via API

Fixed by #1311


custom paneitem font size

I would like to custom paneitem font size as below
PaneItem(
icon: const Icon(FluentIcons.button_control),
title: const Text('control', style: TextStyle(fontSize: 22)),
),
it seem to not working
but paheitemHeader Can do !
Thanks

Noted with thanks !


Analysis script

A couple of things need to do:

the inputs are hard coded,
when saving the model, you saved an empty model. I need a trained model like coefficients of the features.
when I load the model, make sure I don't need to train them.
Also save R^2 value

Hi @suuuuperNOVA . Thanks for the comment.

The inputs at the top are the default values. Once you pass something in the command line, it should use those inputs
The object I saved is a Pipeline object, so you will need to access the named steps and extract the estimator. However, I updated this part just now. I will share the code on how to get the model object.
Good idea. I will try to save a table and a figure for hyper-parameter tuning.


Remove CAS/Stormpath integration module/docs

From stormpath:

This is an important system reminder that the Stormpath API is shutting down on August 17th at noon PDT. All data in Stormpath will be deleted at that time and must be exported beforehand.

Just one note: why not remove it in 5.1?

possible, though we are technically in freeze mode, and this is not quite a bug fix. I guess it also allows anyone to take advantage of the integration until August 17th :) and there is no rush to doing this.

Got ya.. Well, one warning - whoever is using this module (anyone really?) in 5.1 would be "pleasantly" surprised after August 17... But, in all fairness, not a CAS problem ;-)

Thanks. I missed that information. I'll do the same on pac4j side: https://github.com/pac4j/pac4j/issues/910

Should be able to test the fix in about an hour or so, by using the new SNAPSHOT.


🐛 [Bug report]: Unable to Load Plays on "reactplay.io/plays" Page

Descrcibe the bug?
ReactPlay users are experiencing difficulties loading plays from the "reactplay.io/plays" page. The problem appears to be related to network resource loading errors.
Steps to reproduce the bug?

Navigate to "https://reactplay.io".
Click on the "Browse" button.
A loading screen will appear, and you will notice the plays are not loading.

Expected behavior
Expecting to view plays created by contributors.
Desktop (Please provide your system information)
OS: Windows 11
Browser: Chrome
Version 119.0.6045.200
Mobile (Please provide your device information)
N/A
Screenshot / Screenshare

Relevant log output

Record

[X] I have checked the existing issues
[X] I have read the Contributing Guidelines
[ ] I want to work on this issue
[X] I am in Hacktoberfest

Code of Conduct

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

Yes, I am also experiencing the same issue.

Recently Nhost has deprecated the old backend URL and we had to move to the new URL convention.. else the data fetching will fail.
join our discord server for updates
https://discord.com/channels/982239924227031070/983209230729379901/1184336384127934504

fixed https://github.com/reactplay/react-play/pull/1405

Thanks for the fix.


Set ECR imagePushedAt to current date and time

This implements the enhancement for ECR images stated in issue #2228

Coverage decreased (-0.2%) to 92.854% when pulling 5563030a3d0a51f10668c16c4f7943e8f746ca2b on queue-tip:ecr-set-date-in-put-image into d25a7ff9363967a713599b7b0b974b4c6be2e708 on spulec:master.

Coverage decreased (-0.2%) to 92.854% when pulling 5563030a3d0a51f10668c16c4f7943e8f746ca2b on queue-tip:ecr-set-date-in-put-image into d25a7ff9363967a713599b7b0b974b4c6be2e708 on spulec:master.

Coverage decreased (-0.2%) to 92.854% when pulling 5563030a3d0a51f10668c16c4f7943e8f746ca2b on queue-tip:ecr-set-date-in-put-image into d25a7ff9363967a713599b7b0b974b4c6be2e708 on spulec:master.


Added checkExist on error in step upload/postFile + Added getVersions check in step activateVersion

This fix is to fix the following bug/error:
Error: An error occured. Try running the command again with -D,--debug flag. { res: undefined,   err:    Error: SSL Error: ERR_TLS_CERT_ALTNAME_INVALID        at Request.onRequestResponse (C:\Development\Source\GIT\*******\build\node_modules\request\request.js:948:24)

Thanks for contributing @TimKara! Can you please have a look at the conflicts and resolve. Also there are some tests failing:

><EMAIL_ADDRESS>test
> npm run lint && npm run test:unit

><EMAIL_ADDRESS>lint
> eslint --ignore-path .gitignore ./

/home/circleci/project/lib/code.js
  132:1   error  Line 132 exceeds the maximum line length of 120  max-len
  133:13  error  Expected space(s) after "if"                     keyword-spacing
  136:20  error  Expected space(s) after "if"                     keyword-spacing
  423:13  error  Expected space(s) after "if"                     keyword-spacing
  427:25  error  Expected space(s) after "if"                     keyword-spacing

✖ 5 problems (5 errors, 0 warnings)
  4 errors and 0 warnings potentially fixable with the `--fix` option.

Hi @TimKara , following up here to see, if you can check the conflicts and also resolve https://github.com/SalesforceCommerceCloud/sfcc-ci/pull/186#issuecomment-725393040.
Thanks!


Fixed References, Commented, Code Coverage.

References to code.google.com were removed.
Comments were added so that go vet and friends would stop complaining.
Additional tests were added to get code coverage up.
There is an issue with the conversion of a mnemonic back
into bytes, it does not work for test vectors 0, 4, and 8.

My assumption is that you either do not like the code in the pull request, or that you have some other reservation for declining to merge.
Shall I retract the pull request?

I have not declined merging. The looks pretty good but I haven't yet had time to go through it more thoroughly. I'll try to get to it soon.

Okay @DrHayt this looks good to me. Thanks for the work. I'll look into those issues you've pointed out.


Ignoring inherited fields

My model class inherits from a library class (necessary for json serialization/deserialization), so I'm using the @Table notation which seemed like a good solution. The problem, however, is that the library class I'm inheriting from has its own fields. I can't use @Ignore because I can't change the parent class. I thought that using @Column in the rest of my fields will make Sugar ORM ignore the rest of the unannotated fields, but that doesn't seem to be the case. To make it worse, the library class also has an id field of type String and no matter how I try to hide the id by defining a new id of type Long, Sugar ORM always tries to use the library class's id field which results in an error. Isn't there anyway to ignore fields not annotated with @Column or inherited fields? Or is there any better way to go about this?

Same problem.


bug: Fixing url resolution to behave properly for base address that includes relative part.

Problem: Currently the baseUrl resolution uses new URL(url, base). This has the limitation that your base cannot have any path part, because it is going to get ignored.
Example: Trying to combine /bar with https://abcdef.gh/foo will result in request being issued to https://abcdef.gh/bar instead of https://abcdef.gh/foo/bar
The solution is to bring the resolution algorithm from Axios, which is already battle tested, small & licensing allows for reuse.

The path shouldn't be ignored by new URL(url, base);, provided the url portion is relative.
e.g.
new URL('./bar', 'https://example.com/foo/').toString(); // https://example.com/foo/bar

Your example does work, but the more usual way to express API relative paths which would be:
new URL('/bar', 'https://example.com/foo/').toString(); doesn't work and yields:

My guess is that is also why Axios is not using new URL(... for combining paths and they came up with a home


feat(runtime): add shell environment validators for runtime lock

Description

add shell environment validators for runtime lock
remove runtime build useless validators
related:

https://github.com/star-whale/starwhale/issues/751
https://github.com/star-whale/starwhale/issues/741

Modules

[x] Client

Checklist

[x] run code format and lint check
[ ] add unit test
[ ] add necessary doc

LGTM


Change/simplify connections

This is hopefully just the start of a big refactoring in the core of phergie. I think this serie is ready for master, despite the size of a patch that can spoil the review fun a bit.

This may be simplifying things in terms of reducing the amount of code, but it also makes fairly sweeping BC-breaking changes to an area that I wouldn't presently consider to be painful for plugin developers. We do need to figure out a solution to the dependencies situation (see http://groups.google.com/group/phergie/browse_thread/thread/711c6c0f77f3ee42), but I'm not convinced this is a good approach to that end.


Remove unused full_control related code

Summary

Remove unused code related to full_control.

Tests

CI green.

I missed a couple lines, one more time w/ the +1 please @masenf


preliminary 1.1 doc "Citadel Health Checking" fails when deploying citadel health checking

Describe the bug
{{
https://preliminary.istio.io/docs/tasks/security/health-check/
$kubectl apply -f install/kubernetes/istio-citadel-with-health-check.yaml
serviceaccount/istio-citadel-service-account configured
service/istio-citadel configured
The Deployment "istio-citadel" is invalid: spec.template.metadata.labels: Invalid value: map[string]string{"istio":"citadel"}: selector does not match template labels
Looks like the Deployment in install/kubernetes/istio-citadel-with-health-check.yaml needs to be:
apiVersion: extensions/v1beta1
kind: Deployment
metadata:
name: istio-citadel
namespace: istio-system
spec:
replicas: 1
template:
metadata:
labels:
app: security
chart: security
heritage: Tiller
release: istio
istio: citadel
}}
Expected behavior
{{
kubectl apply -f install/kubernetes/istio-citadel-with-health-check.yaml
succeeds
}}
Steps to reproduce the bug
{{
Follow steps
kubectl apply -f install/kubernetes/istio-demo-auth.yaml
}}
Version
{{
istio-1.1.0-snapshot.6
}}
Installation
{{
Follow doc steps
}}
Environment
{{
minikube version: v0.34.1
}}
Cluster state
{{ N/A }}

I will try to fix if the health check. If the feature is broken and hard to fix, we may remove this feature for now.

Now only the user guide needs to be improved.


Re-enable and fix e2e tests that take user away from dashboard

cypress/e2e/tests/pages/home.spec.ts Can click on support links

ranchermanager.docs.rancher.com
slack.rancher.io

tests disabled as part of bump to cypress 10.11.0 and pending release

as part of that i've fixed the cy.origin for them both
however now it throws context based error (see below)

  1) Home Page
       "before each" hook for "Can click on support links":
     CypressError: `cy.scrollIntoView()` failed because it requires a DOM element.
The subject received was:
  > `undefined`
The previous command that ran was:
  > `cy.get()`
Because this error occurred during a `before each` hook we are skipping the remaining tests in the current suite: `Home Page`
      at ensureElement (https://<IP_ADDRESS>/__cypress/runner/cypress_runner.js:147634:76)
      at validateType (https://<IP_ADDRESS>/__cypress/runner/cypress_runner.js:147457:16)
      at $Cy.ensureSubjectByType (https://<IP_ADDRESS>/__cypress/runner/cypress_runner.js:147493:9)
      at $Cy.pushSubject (https://<IP_ADDRESS>/__cypress/runner/cypress_runner.js:158018:12)
      at wrapped (https://<IP_ADDRESS>/__cypress/runner/cypress_runner.js:157507:19)
  From Your Spec Code:
      at HomeClusterListPo.checkVisible (webpack:///./cypress/e2e/po/components/component.po.ts:39:23)
      at HomePagePo.goToAndWaitForGet (webpack:///./cypress/e2e/po/pages/home.po.ts:26:20)
      at Context.eval (webpack:///./cypress/e2e/tests/pages/home.spec.ts:14:15)

fixed in https://github.com/rancher/dashboard/pull/9421


React Build Script Issue - strip-bom 3

Hello, I am receiving the following error when trying to create a production build for a react application with react-scripts which uses version 1.1.11 of the csvtojson package.
$ react-scripts build
Creating an optimized production build...
Failed to compile.

Failed to minify the code from this file:

        ./node_modules/strip-bom/index.js:2

Read more here: http://bit.ly/2tRViJ9

error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

I think it's because version 3 of strip-bom uses an ES6 function declaration and the react build script expects the source be using ES5 (as noted here). I was able to create a successful build by changing the 2nd line inside the node module source of strip-bom to this:
module.exports = function (x) {

I don't know how important react support is for this library, but I figured I would bring it up. This is the commit where the strip-bom version was updated: https://github.com/Keyang/node-csvtojson/commit/ac1b871af413a728ff49af93f5c9086faebc96f2
React applications using react-scripts to build can still create production builds with csvtojson 1.1.9 for now.

Here is a link as well to an older discussion on ES5 transpilation in the strip-bom repository: https://github.com/sindresorhus/strip-bom/issues/7

thanks for pointing this out.
released in 1.1.12

No problem at all, happy to help.
Looks like that did the trick, thank you for such a quick fix!


Documentation for template usage

I'm currently building a CLI with Teletype, which so far I'm loving - great work on the user experience of getting from zero to a decent CLI tool!
One thing that's not at all clear is how to make use of templates. Every command seems to generate a sub-directory in templates/, which I presume is meant to have a bunch of Erb files dropped in it or something, but there's no documentation I can find on how to actually make use of those templates!

Hi Jon 👋
Thanks for using tty! You're right about the intention behind templates. This functionality isn't documented as it is not implemented yet. Adding templates generation was the first step but then I simply run out of steam. There is a plan on where this tool is going explained here:  https://github.com/piotrmurach/tty/issues/50#issuecomment-593937127


Code workflow

This pipeline configuration builds the application and produces a build for the Release configuration.

 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.:x: ReygenM sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.


Does this library support serializing objects with circular references?

thank you!

@mrjjwright circular references are handled quite gracefully actually. You just need to define the target type you want them to be serialized with.
const stringify = sjs({
  a: attr('boolean'),
  b: attr('number'),
  circular: attr('string'), // <= Target type
});

const obj = {
  a: true,
  b: 42,
}

obj.circular = obj;

const str = stringify(obj);
// => {"a":true,"b":42,"circular":"[object Object]"}

But you can also customize how the serialization is handled in the first place.
Remove circular property
const stringify = sjs({
  a: attr('boolean'),
  b: attr('number'),
  circular: attr('string', () => undefined),
});

const str = stringify(obj);
// => {"a":true,"b":42}

Add a placeholder for the property
const stringify = sjs({
  a: attr('boolean'),
  b: attr('number'),
  circular: attr('string', () => '<circular>'),
});

const str = stringify(obj);
// => {"a":true,"b":42,"circular":"<circular>"}

Freaking awesome, thanks!!

Can I serialize recursive schemas/structures?

What is the difference between a circular structure and a recursive structure? Could you provide an example?


The terminal will stuck when exec source ~/.zshrc

It takes a few seconds to respond

Same here - I timed it. it took 3 seconds to start.
When I typed exit it took 17 seconds to exit (close the terminal)

i find a .git under of the ~, delete it and resolve

@bronze  lm just curious - you mean you found ~/.git
You deleted it and everhthing is fine.
All is fine for me to. After an update everything was back to normal. I had
lots of problems though. Would be nice to know what went wrong instead of
just been given medicin i like to know why i am sick in the first place.
Glad everything worked out fine for you too
Regards
PJ
Den lør. 25. nov. 2017, 08:24 skrev bzone<EMAIL_ADDRESS>
Closed #6446 https://github.com/robbyrussell/oh-my-zsh/issues/6446.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/robbyrussell/oh-my-zsh/issues/6446#event-1357747676,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALjJ5yWvAzPsPD6ZyoMxBR0G-68WsScVks5s58CugaJpZM4Qm7BP
.


[GHSA-5p3h-7fwh-92rc] Remote Code Execution due to Full Controled File Write in mlflow

Updates

Affected products

Comments
added patched version

Hi @mberges21, I appreciate your contribution to the GitHub Advisory Database. Upon further review it appears that the code was patched in version 2.9.2.


HDDS-5610. Remove or clarify doc regarding OM federation

What changes were proposed in this pull request?
In the OM part of the Ozone document, OM federation is not implemented, but there is no remarks, which will cause users to mislead when reading.
Solution: clarify that this is the possibility of future improvement by adding a note after this paragraph.
If OM federation is successfully implemented in the future, delete this sentence.
What is the link to the Apache JIRA
https://issues.apache.org/jira/projects/HDDS/issues/HDDS-5610
How was this patch tested?
Local hugo pass.

Thanks @sky76093016 for updating this docs.
In Chinese part, I think it should be 发展 -> 开发.

Thanks @cku328  for reviewing it.Chinese part has been modified.

Thank You @sky76093016 for fix and @cku328 for review.


Investigate better approach to value to string-ish comparison

Currently:
    friend
    bool
    operator==(
        value const& lhs,
        value const& rhs) noexcept
    {
        return lhs.equal(rhs);
    }

Thus, jv == "some string" is equivalent to jv == value("some string"), which allocates.
Consider adding an overload similar to one for string .

I'm ok with this though

bool op==( value const&, string_view) noexcept;
bool op==( string_view, value const&) noexcept;

but this could introduce ambiguities.

I don't think we should do this. Instead, we should document the rationale for why we aren't doing it.

I mis-named the issue. The problem isn't just with strings, it's also present with objects and array.
There are 2 issues:

operator== will silently allocate when a value is compared against a string, an array or an object.
operator== works with string_view, but not with std::string_view.

Is there a way to compare against initializer list without explicitly spelling out std::initializer_list?


[CARBONDATA-1892]updated documentation for disability of single_pass on first load

Correction In the documentation of single_pass is required as now single_pass is not disabled for the first load, with reference to https://github.com/apache/carbondata/pull/1622

Build Success with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/695/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1924/

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2254/

SDV Build Fail , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/2255/

retest this, please

Build Failed with Spark 2.2.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/740/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/1971/

LGTM


Implement ockam vault list command

Hi @mrinalwadhwa,
the issue seems to be a duplicate of https://github.com/build-trust/ockam/issues/3935
https://github.com/build-trust/ockam/pull/4073
Best regards,
Harald

Thank you 🙏


Remove obsolete defaulting in service/rest.go

@bgrant0607 for #1502

LGTM. Will wait for travis to pass before merging.


⚠ Avatar API Endpoint has degraded performance

In 0a9be47, Avatar API Endpoint (https://avatar.roblox.com/v1/avatar-rules) experienced degraded performance:

HTTP code: 200
Response time: 1015 ms

Resolved: Avatar API Endpoint performance has improved in 22b32a5 after 10 minutes.


Metric Scores and NQ Evaluation

Hi there, thanks very much for such an amazing work!
Currently, I'm trying to reproduce the results from the paper, but I have the following problems:

Metric scores: lm-eval-harness would return acc and acc_norm at the same time. Do you have a preference to use one of them?
NQ evaluation: I've checked the evaluation codebase and your starter scripts, but have no clues about the evaluation on the Natural Questions (NQ) dataset (it is not implemented in lm-eval-harness yet).
Did you write an evaluation script, or adopt an existing repo to get the scores?

Thank you so much for your time and response~

Hi! Sorry for the late reply:
I have update the script for evaluation nq, boolq and gsm8k here at run_eval.sh. We use nq_open in the harness repo.
We also updated the metrics we use in README.md file.
Hope it helps and feel free to reach out again for any further questions!

Thank you very much for the reply and the code update~


Cannot get terminal to open

alt - shift - T: does nothing
cmd - shift - T:
Console Output
Uncaught TypeError: Cannot read property 'file' of undefined [~]/.atom/packages/atom-terminal/lib/atom-terminal.coffee:62

Assuming this was fixed. If not, feel free to reply.

Still broken for me with ctrl+shift+t
Exception popup:


Validation not triggered on draft save

Link to reproduction
https://github.com/christoph-reps/payload/tree/validate-length-with-draft
To Reproduce

Add text to the seeded post which is longer than 20 chars.
Click save draft

Describe the Bug
Savings drafts seems to not trigger validation.
If you create a post and publish it validation will be triggered.
This is not the case when you save it as a draft.
I guess as a user i would expect both buttons to behave the same for validation. Or thought a bit further builtin validation for min / max character fields should trigger onChange or onBlur for text fields
Payload Version
1.8.5

Hey @christoph-reps — this is actually by design. Because drafts can be saved in an unfinished state, saving a draft does not enforce validation.
We have discussed potentially building a flag to enable validation for drafts, therefore removing the ability to save an incomplete draft, but this would be a new feature that would be opt-in.
What do you think?  I'll convert this to a Feature Request discussion and we can keep the conversation going there!


Avoid type-checking (part 2) require PHP 7+

Type hinting require PHP 7+
Maybe for you it will be news, but not everyone has switched to the PHP 7+

Thank you Peter


[MISC]: Cannot post-process cartesian wrfout data

What is your issue?
I am attempting to load and analyse data from an idealised run of a tropical cyclone. Because this run is idealised, the projection is Cartesian.
My code is as follows:
import xarray as xr
import xwrf

directory_path = "path/to/output/out/"

# Open the NetCDF file
ds = xr.open_mfdataset(
        directory_path + "wrfout_d01*",
        engine='netcdf4',
        concat_dim="Time",
        combine="nested"
        )
print(f"Projection No.: {ds.attrs['MAP_PROJ']}\nProjection name: {ds.attrs['MAP_PROJ_CHAR']}")
ds = ds.xwrf.postprocess()

This yields the following error:
Projection: 0
Projection name: Cartesian
Traceback (most recent call last):
  File "/g/data/x77/me5758/programs/cyclone-analysis/import_test.py", line 14, in <module>
    domain_data = domain_data.xwrf.postprocess()
                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/g/data/x77/me5758/programs/venv/analysis_venv/lib/python3.11/site-packages/xwrf/accessors.py", line 147, in postprocess
    ds = ds.pipe(_include_projection_coordinates)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/g/data/x77/me5758/programs/venv/analysis_venv/lib/python3.11/site-packages/xarray/core/common.py", line 815, in pipe
    return func(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/g/data/x77/me5758/programs/venv/analysis_venv/lib/python3.11/site-packages/xwrf/postprocess.py", line 95, in _include_projection_coordinates
    grid_components = _wrf_grid_from_dataset(ds)
                      ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/g/data/x77/me5758/programs/venv/analysis_venv/lib/python3.11/site-packages/xwrf/grid.py", line 58, in _wrf_grid_from_dataset
    raise NotImplementedError(f'WRF proj not implemented yet: {proj_id}')
NotImplementedError: WRF proj not implemented yet: 0

Is this simply a case where Cartesian projections are unsupported, or is there something more odd going on?
Help would be appreciated

Hi @MaxEtherington, thanks for the issue. It is indeed simply the case that the treatment of cartesian coordinates is not yet implemented in WRF as this is not a very typical use case. You can see this here:
https://github.com/xarray-contrib/xwrf/blob/3163abc64ec3650b5a67129834f9cee2efc695ed/xwrf/grid.py#L41-L58
Unfortunately, I won't be able to do this in the near future but Pull Requests are always very welcome :)
Also, be aware that xwrf is written with mostly real simulations in mind. If there are some additional kinks in the netcdfs for idealized cases, we might not be aware of them (but would appreciate any input).


Incident webhook/notification

Describe the solution you'd like
I would like an option when creating a webhook/notification to enable incident creation/updating to be included in these notifications.
Additional context
A tick box when creating the notification to toggle it off/on so you dont have to have these incidents in your notifications.

Attempting to add in #725


When is 1.4.0rc out??

really need some of the changes and it seems to be taking a while

@Gillardo It's already out!

Just released 1.0.0-rc.5 with working drop-up functionality.


After sync setting, the extensions didn't install

🐛 Describe the bug
After I set up my token and gist with code-setting-sync. My extensions didn't install. Then I execute force download. The info show up the setting is already latest version. But extensions still not install
🌴 Visual Studio Code Version : [ 1.26.1 ]
🌴 Code Settings Sync Version : [ 3.1.2 ]
🌴 Operating System : [ macOS 10.13.6 ]
🌴 Occurs On: [ Download  ]
🌴 Proxy Enabled: [ No ]
🌴 Gist Id: [ c5d0a61fb1fd7d111dc43d0f99a17d87 ]

are you using code insiders or standard version

@shanalikhan I used standard version.
I fix that while I reinstall vscode.


Write tests automatically (feature request)

The debugger has the model, msg and the new model. So if you tell it that the new model is indeed the expected return value from update msg model, it can write that test for you. I've gone into more detail with an example here: https://github.com/elm-lang/elm-make/issues/138#issuecomment-270371165

This is an amazing concept and the kind of out of the box thinking that I love when I see it occur in the Elm community!
Conceptually, it's a tool for record an integration test that is at the data model level instead of the UI level (and thus sidestepping certain bugs like when buttons/inputs change class/id/positions).
Although perhaps the benefit is somewhat short lived as the generated test would have to be hand pruned if the message type changes (which I imagine would happen quite often under development). But it does make complex interactions easily encodable.
Still, absolutely worth exploring, though it might be a conversation best taken to the Elm Discussion Group since the Issues queue isn't where discussions are promoted to occur as per the contribution checklist.

Thanks Peter. I've taken the discussion to elm-discuss: https://groups.google.com/forum/#!topic/elm-discuss/QwxCP-GXY7U

Yeah, this is something that seems like a good direction to go with this kind of tool. Want to keep issues for tracking bugs though, so closing.


x/vgo: vgo removed -insecure flag

What version of Go are you using (go version)?
go version go1.10.2 linux/amd64
Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/baas/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/baas/git/go"
GORACE=""
GOROOT="/home/baas/my/go"
GOTMPDIR=""
GOTOOLDIR="/home/baas/my/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build608113082=/tmp/go-build -gno-record-gcc-switches"
What did you do?
$ curl -I http://rnd-github.huawei.com/db/parser/sql?go-get=1
HTTP/1.1 404 Not Found
Via: 1.1 <IP_ADDRESS> (McAfee Web Gateway <IP_ADDRESS>.0.23766)
Date: Thu, 17 May 2018 03:47:45 GMT
Server: GitHub.com
Status: 404 Not Found
X-Runtime: 0.006361
Content-Type: text/html; charset=utf-8
X-Request-Id: 715f56762358f8dbcf8968484163ceb3
Content-Length: 129318
X-Frame-Options: deny
Proxy-Connection: Keep-Alive
X-XSS-Protection: 1; mode=block
X-GitHub-Request-Id: 0f75ee93-d875-48d1-8dc7-8bcfa529656f
X-Content-Type-Options: nosniff
Content-Security-Policy: default-src 'none'; base-uri 'self'; block-all-mixed-content; child-src 'self'; connect-src 'self' http://rnd-github.huawei.com https://status.github.com rnd-github.huawei.com; font-src 'self'; form-action 'self' rnd-github.huawei.com; frame-ancestors 'none'; frame-src 'self'; img-src * data:; media-src 'none'; script-src 'self'; style-src 'unsafe-inline' 'self'
Connection: close

$ vgo get -insecure rnd-github.huawei.com/db/parser/sql

What did you expect to see?
get the rnd-github.huawei.com/db/parser/sql from github enterprise
What did you see instead?
flag provided but not defined: -insecure
usage: get [build flags] [packages]
Run 'go help get' for details.

@rsc Was the removal of the -insecure flag intentional? Should it stay removed?

Insecure was probably removed because many commands can now hit remote servers. Adding insecure flags to all such commands is probably not great idea.
Perhaps if this remains a requirement we could introduce a new environment variable that takes a list of host prefixes to whitelist.
GO_WHITELIST_ALLOW_INSECURE=internal.mycorp.local/vcs:vcs.test.local

I would prefer if this was a flag. I would like to see it with the ps command as that is easier to audit. Environment variables are significantly harder to trace in this manner.

This is the first report I've seen of GitHub Enterprise running over HTTP instead of HTTPS. Is it really not available under HTTPS in your environment?
One workaround is to put something in your ~/.gitconfig to tell git to rewrite https://your.server to http://your.server.

@rsc
Thank you for your answer very much.
 Here's an example:
git config url.http://localhost:8080/:.insteadof https://github.com/

Notice the : before the .insteadof.
Also, you'll need to ensure that you don't have old configs that are potentially clashing:
git config -l | grep -i insteadof

But like @rsc asked, do you really not have https available?

@myitcv
Thank you very much.
I tested it, this does not solve the problem
baas@SZX1000428520:~/git/go/src/sql$ git config -l | grep -i insteadof
url.http://rnd-github.com/:.insteadof=https://rnd-github.com/
baas@SZX1000428520:~/git/go/src/sql$ vgo build
vgo: finding rnd-github.huawei.com/db/parser v0.0.0-20180125184044-316ea1d6f45f
FindRepo: Get https://rnd-github.huawei.com/db/parser?go-get=1: cannotconnect
vgo: rnd-github.huawei.com/db/parser: Get https://rnd-github.huawei.com/db/parser?go-get=1: cannotconnect

For the follow problem,　I have used nginx agent to solve this problem:）
But like @rsc asked, do you really not have https available?

@rsc @myitcv
Thank you for your support, I have use a nginx proxy to support https

Just for the record, it looks like the insteadof config didn't work because you were using the incorrect domain. vgo was trying to resolve rnd-github.huawei.com yet your config was for rnd-github.com.
So you would need to have the following:
git config url.http://rnd-github.huawei.com/:.insteadof https://rnd-github.huawei.com/

I have use a nginx proxy to support https

Glad you have a solution.

@myitcv
I feel sorry for my mistake
I tested it again, but it still can not solve the problem
baas@SZX1000428520:~/git/go/src/sql$ git config -l | grep .insteadof
url.http://rnd-github.huawei.com/:.insteadof=https://rnd-github.huawei.com/
baas@SZX1000428520:~/git/go/src/sql$ vgo build
vgo: finding rnd-github.huawei.com/db/parser v0.0.0-20180125184044-316ea1d6f45f
FindRepo: Get https://rnd-github.huawei.com/db/parser?go-get=1: cannotconnect

I found that vgo does not use .gitconfig's url map：

func lookupCustomDomain(path string) (Repo, error) {
    var body io.ReadCloser
    err := web.Get(
        getLookupURL(path),
        web.Non200OK(),
        web.Body(&body),
    )
    if body != nil {
        defer body.Close()
    }

    //...
}

func getLookupURL(path string) string {
    scheme := "https://"

    if isInsecure(path) {
        scheme = "http://"
    }

    return scheme + path + "?go-get=1"
}

@saibing are you using the latest commit of vgo?
Looks like you are using an old version, pre https://github.com/golang/go/issues/24915
Can you check:
go get -u golang.org/x/vgo
(command cd $(go list -f "{{.Dir}}" golang.org/x/vgo); git rev-parse HEAD)

outputs:
6a94eb3b5ccc04453d2fb45c23641e5993118068

for me.

@myitcv
me too:)
baas@SZX1000428520:~/git/go/src$ (command cd $(go list -f "{{.Dir}}" github.com/golang/vgo); git rev-parse HEAD)
6a94eb3b5ccc04453d2fb45c23641e5993118068

Sorry, I've also missed something obvious here. rnd-github.huawei.com is a custom domain. Hence the issue we're seeing here happens before git is called; because it's the resolution of https://rnd-github.huawei.com/db/parser?go-get=1 that is failing here. This step is required so that vgo can understand where the underlying VCS repo lives, and which tool to use (git, svn etc).
I'll defer to @rsc on whether we want to align this with the go tool or not.

Do you really not have https available?

If a company runs GitHub Enterprise or something similar behind VPN, they typically do not use HTTPS because setting it up is a hassle. For example, if they use their own custom domain like .internal it is not possible to get a "real" (trusted by major CAs) certificate, and creating their own CA and make it trusted on all hosts is painful.
So -insecure flag should ignore certificate check errors (if HTTPS is used with a self-signed certificate or certificate is issued by a custom CA), and should try HTTP is HTTPS is not available.


Use xcodebuild to run tests instead of xctool

Also uses Xcode 8 for Swift 2.3 support

Fix https://github.com/Automattic/WordPressComKit/issues/17

Looks fine to me. We'll adopt these changes for now until we swap over to Buddybuild.


Add submit_command_extra and cancel_command_extra arguments

submit_command_extra and cancel_command_extra (config options
jobqueue.X.submit-command-extra and jobqueue.X.cancel-command-extra)
are lists of strings that are arguments passed on as-is to condor_submit
and condor_rm when submitting or removing HTCondor jobs.
Fixes #411.

I tested a bit more and have a problem I cannot understand.
cluster = HTCondorCluster(cores=1, memory="1GB", disk="100MB", submit_command_extra=["-name","schedd2"] ,cancel_command_extra=["-name", "schedd2"])

cluster.scale(1)
cluster.scale(0)

strangely leaves stale jobs. Any clue?

@matyasselmeci , can you reproduce my problem with the "-name" argument?
Any clue how to effectively check that the params have been passed? Your idea from https://github.com/dask/dask-jobqueue/issues/411#issuecomment-613032232 was actually really good I think. But this won't do for the cancel_command I guess.

Job._close_job() appears to be a class method: https://github.com/dask/dask-jobqueue/blob/master/dask_jobqueue/core.py#L343-L348
so it's not using the instance-specific cancel_command attributes.

Job._close_job() appears to be a class method: /dask_jobqueue/core.py@master#L343-L348
so it's not using the instance-specific cancel_command attributes.

Sorry I missed this one (don't hesitate to ping me if you need input in general), no objection to make it a normal method rather than a class method.

Sounds good, thanks!
One idea for a test case for cancel_command is to add -name {wrong_name} as an argument and watch condor_rm fail; then replace that with -name {right_name} and watch it succeed.

thx!! Ping me or remove the draft status, if you like me to review/test it .

One thought: It might make sense to split this PR and merge it in 2 batches to see that the tests are working as expected, but I can also manually revert the class variable part and test it locally. I think it might be a bit of a hassle otherwise, as all this is logically connected.
Maybe the title of the PR should mention that this only adds the commands to HTCondor (should maybe add more tickets to remind the other groups to add this to their schedulers if it makes sense or track the status across schedulers in the ticket and ask for comments,)

should maybe add more tickets to remind the other groups to add this to their schedulers if it makes sense or track the status across schedulers in the ticket and ask for comments,

It seems to me that this is very HTCondor specific and I have not seen anyone express a  need for more flexibility along this axis in other job schedulers.
I agree there it would be great to keep some uniformity between schedulers (mostly for stability/maintenance reasons) but at the same time I think it is fine having some scheduler-specific developments if there is a strong use case behind it.

LGTM. Tested it on our cluster with the sched arg manually. Anything left to do? If you remove the draft status the CI should also run. Can't wait for the merge...

seems like there are some side effects to making the method an instance method: #442 (I just cherry-picked your commit, anyone working on this should probably do the same to distangle the problem).
There seem to be some unwanted leftovers: I didn't see that when manually testing if the arguments work (calling the cancel command seemed to work fine for me...)
BTW: @lesteve: can we turn on github actions for draft PRs?

BTW: @lesteve: can we turn on github actions for draft PRs?

It seems like the CI ran fine. Did you mean "turn off" rather than "turn on"?

It seems like the CI ran fine. Did you mean "turn off" rather than "turn on"?
it ran after @matyasselmeci marked it as ready for review. That is why the problem with the instance method only became apparent now. It did not run until deccacb but on ee54cd6.

But don't mind, I looked at the CI and this seems to be a problem with Github actions recently: https://github.community/t/github-actions-not-being-triggered-on-draft-pr/16390 . I guess it also OK to put [WIP] in the title if you want CI but no merge until this is fixed.

Anybody still planning to work on this?

Just to document it, the workaround why I personally gave up was that HTCondor can actually handle crucial extra-args that cannot be passed via the job description also via the the environment variable so I am doing this instead:
os.environ["_condor_SCHEDD_HOST"] = "login-l.sdil.kit.edu"
Still the problem that @matyasselmeci  ran into are really strange and it seems like some kind of bug that should be documented (maybe even in dask distributed).
It for sure needs some in depth debugging effort.  Should I open a ticket regarding the problem of making job_close an instance method? And then rather close this PR for now (can be reopened if ticket is then fixed)

Still the problem that @matyasselmeci ran into are really strange and it seems like some kind of bug that should be documented (maybe even in dask distributed).

You think it could come from dask.distributed?

It for sure needs some in depth debugging effort. Should I open a ticket regarding the problem of making job_close an instance method? And then rather close this PR for now (can be reopened if ticket is then fixed)

Do we need this now for anything else that this problem? Or is this just because you think it would be cleaner?

You think it could come from dask.distributed?

Actually it was good that you asked! It triggered me to look into the design. I actually now figured out a way to do this in #514 . It seems that the _close_job is a class method by design, probably because it is used in the weakref finalizer (guessing) . The actual interface was close , so it was rather easy to move the cancel_command derefferencing into this.
I however now have the huge problem of getting @matyasselmeci tests to run properly. Everything seems to be just fine, however, the new test design that actually uses failing submit_commands is really a challenge, because I somehow cannt figure out a way how to really catch that.

I hope it is OK if I close this one in favour of #514 , which includes the majority of changes and has been reviewed.


The Tags parameter definition is inconsistent across resources.

For example in elasticache.ReplicationGroup we have to define Tag as:
    Tags=Tags({'Creator': creator_name}, {'Environment': env_type})
but in ec2.SecurityGroup we have to define as follow:
    Tags=[Tag("Creator", creator_name),
          Tag("Environment", env_type)])

To be honest for VPCEndpoint we can add tags using CLI but you cannot add using CF :)


added dark mode

Acceptance Criteria for 1

[x]  Mentor is added to pr
[x]  AC copied to pr description
[ ]  Link to deployed version is added to pr
[ ]  Added layout of Search Bar
[ ]  Rewritten all styles with Module Styles
[ ]  Implemented dynamic theme change logic

Acceptance Criteria for 1*

[ ]  Implemented logic for fetching user's theme.
[ ]  Saved theme to the Local storage.
[ ] Note: if we have saved theme in Local storage, we use it first after reloading of the page

Could you provide a default theme for first render, to fix borders issues

Pay attention for this issue please
https://github.com/DavidTereshchenko/fe-react-2024/pull/4#issuecomment-2104657872

Consider adding the ability for user to add more then one item of the same product into cart, for example user wants to buy five
"Mid-Century Modern Wooden Dining Table" or two  Smartwatches...


FIX Implementing custom read resolver to fix permission issue

This is required because the default  resolver in GraphQL checks permissions against fresh data objects. Elemental areas require that they are saved before permission checks can be accurate
Fixes #586
/cc @scott1702

Thanks for the suggestion @Cheddam . I have now (finally) added a Behat test to cover a less privileged user.


Add codecov

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@8b22f42). Click here to learn what that means.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #18   +/-   ##
=========================================
  Coverage          ?   75.75%
=========================================
  Files             ?       20
  Lines             ?      961
  Branches          ?       59
=========================================
  Hits              ?      728
  Misses            ?      213
  Partials          ?       20

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 8b22f42...4c448e9. Read the comment docs.

I rebased, after accepting (almost all of) your changes. Now, it looks like those comments are hidden. I'm not sure how to "accept" them, or somehow mark them as changed.

You can click on "Show outdated" above to see each change and my comments.
I responded to your set_compile_options vs SET(CMAKE_C_FLAGS ...) response.

LGTM.


No Background Mode

#321 after, maybe this pull request usefull or, waiting that pull request #144

@c0b41 it seems a problem with elementary OS. Check this https://github.com/electron/electron/issues/5050

@grunjol yeah, look like elementary os problem GtkStatusIcon, but problem still #303

I would rather fix this by detecting Tray support (when https://github.com/electron/electron/issues/5065 is fixed in Electron). Let's give that issue a week, in case it's an easy fix for Electron to make. Then we can avoiding adding a preference option for this.
But adding a Linux-specific command line flag / launcher option does not seem clean. Plus, then the user has to remember to launch the app in the correct way each time.
@c0b41 In any case, thanks for attempting a fix for this :)


Use package artifacts to store the geodata.

Julia has added a mechanism for managing package artifacts. It would be nice to use it.

Turns out the Pkg artifacts can only be used to download tar files and not zip files and probably not that useful here.


Support for connecttech GMSL serdeser board?

Hello,
I'm using xavier with GMSL serdeser board from connecttech
(http://connecttech.com/product/xavier-gmsl-camera-platform/)
Is it possible to use ADK with this?
It seems board support comes with binary form.

We do not support the Connected Tech board at the moment. There is no current plan to support it in the future. We recommend the D3 engineering board. https://store.d3engineering.com/product/designcore-nvidia-jetson-serdes-card/


working on usability features

@justinbmeyer thanks for the comments. I'll fix all the things you addressed in a new PR.


Segmentation fault.. Oops

This input leads to Segmentation fault:
cd /bin && ls | grep c > ~/file1 && cd ~ && cat file1
Need to debug and fix what wrong.

The problem in the ~/file1 argument. It doesn't translate in the absolute path, as should.
So, ExecManager tries to open file with that name, and then the FILE* descriptor passed into fileno() function, where SEGFAULT is occurring.


Multipart upload server side encryption parameter

Error: UnexpectedParameter: Unexpected key 'ServerSideEncryption' found in params.MultipartUpload.Part
Probably connected to this:
Base on Amazon recent changes on serverSideencryption
I did a hot fix and quick fix. looking forward for more efficient fix.
It happens only on bigger files, (over 5MB, due to AWS multipart upload method)

much thanks for hot fix; will give it a read and merge soon

much thanks for hot fix; will give it a read and merge soon

Thanks, e might be a better solution in aws-sdk API, The fix here is done quickly only to make the system works again.

Hi @hasnat is this will be checked and merged soon?


  Expect.equals("hello world!", cs.fromUtf8());
  cs.free();
  foo = "";
  for (int i = 0; i < 100000; ++i) {
    foo = 0x8fffffff00000000;
  }
}

The problem is that the VISIT_FROM/VISIT_TO annotations in RawPointer aren't respected because the virtual VisitPointers is only used for predefined classes. Since the cid is for CString, not Pointer, it gets scanned like any regular object.


Add variance information to custom Lazy implementation

@JakeWharton

I'm using JetBrains' Kotlin extensions now. It's disappointing to have never received a response. 🤷♂

I'm using JetBrains' Kotlin extensions now. It's disappointing to have never received a response. 🤷♂


Add vision_visp system dependencies.

Hello,
I would like to release vision_visp into Fuerte.
To do so, I need the following system dependencies to be added.
Can you pull these modifications?
Thanks,

based on discussions on ros-release, there is consensus that keys should:

Have the exact same name as their ubuntu package equivalent
Avoid bundling multiple dependencies, where possible.

Can you reissue the pull request with these changes?  Although base.yaml does not follow this yet, updating now will prevent future changes.

Done, thanks for the feedback. See pull request 8 (https://github.com/ros/rosdistro/pull/8/).


docs: 更新README.md添加洞察分析

👀 PR includes

🔧 Chore

[ ] Test case
[x] Docs / demos update
[ ] CI / workflow
[ ] Release version
[ ] Other ()

增加 repo 数据洞察

英文的 README 忘改了

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


Create bootstrap script for install deps in Ubuntu 14.04 VM

Mostly SURFsara HPC cloud in mind

Following packages are needed:
build-essential
git
libproj-dev


Merge incremental-parser branch into Master

Purpose

Merge incremental-parser branch into Master

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Codecov Report

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

@@           Coverage Diff           @@
##           master   #23203   +/-   ##
=======================================
  Coverage   14.59%   14.59%
=======================================
  Files          51       51
  Lines        1411     1411
  Branches      219      219
=======================================
  Hits          206      206
  Misses       1189     1189
  Partials       16       16

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 623d289...623d289. Read the comment docs.


Updating mainnet-seedlist

Seedlist:
https://docs.google.com/spreadsheets/d/19EHDAOiF6EmqQtqkp38eOGoKWeS3oN5Jgped1vD_kPQ/edit#gid=976104442

LGTM - would you edit the description to remove the google docs link though? We shouldn't make that public.

LGTM - would you edit the description to remove the google docs link though? We shouldn't make that public.

Done


[CVE-2023-28155] request package dependency has known vulnerability

Context
In order to help us troubleshoot issues with this project, you must provide the following details:

ElasticDump version: 6.99.0

Describe the bug
The npm audit command is showing that the request package (2.88.2) is impacted by CVE-2023-28155:
request  *
Severity: moderate
Server-Side Request Forgery in Request - https://github.com/advisories/GHSA-p8p7-x288-28g6
No fix available
node_modules/request
  elasticdump  *
  Depends on vulnerable versions of aws-sdk
  Depends on vulnerable versions of request
  Depends on vulnerable versions of requestretry
  node_modules/elasticdump
  requestretry  *
  Depends on vulnerable versions of request
  node_modules/requestretry

Expected behavior
There is currently no releases of request with a fix for this. There is an open PR which should resolve the issue but the library is no longer maintained and has not seen an update in 3 years. You may want to look at using alternatives to the request package.

These are adversaries, also it's important to read these, this issue isn't explotable in elasticsearch-dump


Enable multiple http/https ports for service that map to Ingress' ports 80/443

Is this a request for help?:
No
Is this a BUG REPORT or FEATURE REQUEST? (choose one):
FEATURE REQUEST

Version of Helm and Kubernetes:
Kubernetes  1.11.0
Helm 2.9
Which chart:
nginx-ingress
What happened:
Cannot expose multiple http/https ports from Ingress Controller Service.
What you expected to happen:
It should be configurable (nginx-ingress/value.yaml) Nginx Controller service to expose multiple http/https ports that map to Ingress' ports 80/443. For example, the nginx-ingress chart should be flexible to define target Nginx Controller Service as the following;
apiVersion: v1
kind: Service
metadata:
  labels:
    app: nginx-ingress
  name: nginx-ingress-controller-svc
spec:
  loadBalancerIP: xx.xxx.xxx.xxx
  ports:
  - name: 80-http
    nodePort: xxxxx
    port: 80
    protocol: TCP
    targetPort: http
  - name: 8080-http
    nodePort: xxxxx
    port: 8080
    protocol: TCP
    targetPort: http
  - name: 443-https
    nodePort: xxxxx
    port: 443
    protocol: TCP
    targetPort: https
  - name: 8443-tcp
    nodePort: xxxxx
    port: 8443
    protocol: TCP
    targetPort: https
  type: LoadBalancer

I have a pull request https://github.com/helm/charts/pull/8225 for this change.


tonic-build: Regression in generated code dependency surface area

Bug Report
https://github.com/hyperium/tonic/commit/6c898a239fd5e0000ec8120ef29a0444f3680f2e appears have to introduced a regression of sorts in tonic-build: now that futures_core is explicitly referenced in generated code, code that would previously compile now fails with, e.g.:
error[E0433]: failed to resolve: use of undeclared crate or module `futures_core`
    |
277 | ...erve method."] type ObserveStream : futures_core :: Stream < Item = Result < super :: TapEvent , tonic :: Status >> + Send + Sync + 's...
    |                                        ^^^^^^^^^^^^ use of undeclared crate or module `futures_core`

I assume that this means that applications need to pull in a dependency on futures-core explicitly? It seems preferable for tonic to re-export everything generated code depends on so that applications don't have to worry about these dependencies. I.e., generated code should depend on something like ::tonic_codegen::Stream

Totally! We should make Stream part of the codegen module and use that re-export from the generated code.

Actually, I was wrong about the cause: I updated tonic-build without updating tonic (thanks, Dependabot). So, the futures_core re-export was missing in generated code.
I think technically 6c898a2 was an API breakage, but I'm okay now that I've just updated tonic.


Replication of Diffusion Results

Hi, I'm trying to replicate your results for applying SaShiMi in a diffusion context, and have run into some questions about implementation details along the way. It'd be awesome if you could help me out with them.

I have found the diffusion version of the SaShiMi model at https://github.com/HazyResearch/state-spaces/blob/diffwave/sashimi/sashimi.py. I assume that one is the reference implementation. If yes, what parameters did you use? Just bidirectional=True, unet=True, diffwave=True and set the rest to the values specified in Appendix C.2.2 of the paper and their respective default values?
In the original model, you use mu-law quantization for the model. Is this something you also use with the diffusion implementation? And are you using an embedding encoder & sequence decoder like for the AR model? If so, how are you implementing this setup, also in regards to e.g. the additive noise?

Best,
Stefan

Hi Albert,
Thank you very much for the incredibly quick help once again!
I already guessed that you were basing your implementation of that repo judging from the references in the reused code. It would be awesome if you could release a fork with your changes as you mention that can be used to replicate your results, especially as I have also been facing some issues stemming from the upsampling method in SaShiMi in my reproduction attempts.

My Diffwave implementation is released at https://github.com/albertfgu/diffwave-sashimi. It took longer than planned since I ended up improving the infra to make it easier to train new models, beyond just reproducing results.

Thank you very much! Doubly so for putting in all of the effort to improve it further to make working on it easier!


Shiming stopped working

Hi, when I add any shim into my config I receive following error:
TypeError: Cannot read property 'acceptFiles' of undefined
    at BundleSource.addFile (/Users/tomi/Github/packages/webpack2-typescript/node_modules/fuse-box/dist/commonjs/BundleSource.js:47:71)
    at files.forEach.f (/Users/tomi/Github/packages/webpack2-typescript/node_modules/fuse-box/dist/commonjs/CollectionSource.js:17:37)
    at Array.forEach (native)
    at resolveFiles.then.files (/Users/tomi/Github/packages/webpack2-typescript/node_modules/fuse-box/dist/commonjs/CollectionSource.js:16:19)

Here is my config (when I remove the shim, error disappears). I run this with gulp louis;
gulp.task("louis-ui", ['copy-louis-html'], () => {
    fsbx.FuseBox.init({
        homeDir: "src",
        log: false,
        sourceMap: {
            bundleReference: 'louis.js.map',
            outFile: `${devReactFolder}/louis.js.map`
        },
        shim: {
            "crypto": {
                exports: "{ randomBytes: () => crypto.getRandomValues(new global.Uint16Array(1))[0] }"
            }
        },
        plugins: [
            typescriptTransform,
            fsbx.JSONPlugin(),
            fsbx.TypeScriptHelpers(), [
                fsbx.CSSResourcePlugin({
                    resolve: (f) => `/resources/${f}`
                }),
                fsbx.CSSPlugin()
            ],
        ],
        outFile: `${devReactFolder}/louis.js`,
    }).devServer("> client/modules/_stories/index.tsx", {
        httpServer: false,
        port: 5678
    });
});

gulp.task('louis-server', function () {
    if (node) node.kill()

    node = spawn('node', ['src/client/modules/_stories/server.js'], {
        stdio: 'inherit'
    })
    node.on('close', function (code) {
        if (code === 8) {
            gulp.log('Error detected, waiting for changes...');
        }
    });
});

gulp.task("copy-louis-html", () => {
    gulp.src("src/client/modules/_stories/louis.html")
        .pipe(gulp.dest(devReactFolder))
});

gulp.task('louis', ['louis-ui'], function () {
    runSequence(['louis-server']);
});

Oops, roger that will fix it and cover

Incredibly sorry for that one to slip through. We need more tests, I will move milestones and release the fix with tests very soon.

Hey, don't worry about it. You guys created a piece of software that already made several of my days ;) Have already converted all my project to it ;)


increase the default vector size testing the GPU kernels for the solvers

In this bugfix I increase the default vector size to 597. This is larger than the default thread block size (512), the purpose of the size increase is to check correctness when launching multiple blocks.
With at most 43 column, this can result in a memory requirement of 20 MB. I feel this is acceptable: if people want to use the GPU back-end, they need a device featuring that amount of memory.

LGTM, but again the change to fix cgs gen_mtx is here and it's most likely better to introduce this elsewhere.

Yeah, I just started #44 to have this fix asap


Add typings

Adds typescript support.

In order to avoid adding external typing dependencies, I've left log() typings fairly generic.  There is an @types/winston package available, but its probably not necessary.

@efredin : Could you create a PR to the branch named typescript. I can test your changes on the separate branch hence.

Sure.  Do you want this PR closed?

Let me close this PR #36

🚀 PR was released in branch typescript for hacktoberfest


feat: Lemmas about integrals of bounded continuous functions.

This PR adds some lemmas about integrals of bounded continuous functions. The lemmas are collected in a separate file.

Existing lemmas about integrals of bounded continuous functions, especially from MeasureTheory.Measure.FiniteMeasure, are moved to the new file specifically devoted to this purpose.
The use case for the newly added lemmas is the proof of the last implication of portmanteau theorem.

✌ kkytola can now approve this pull request. To approve and merge a pull request, simply reply with bors r+. More detailed instructions are available here.

bors r+

✌ kkytola can now approve this pull request. To approve and merge a pull request, simply reply with bors r+. More detailed instructions are available here.

bors r+

bors r+


Day of week headers not rendering

In App.js the headers in the container day of week header  are not rendering in spite of the following code
const week_header = [];
for(let i = 0; i < day_of_week_lookup.length; i++)
{
console.log(day_of_week_lookup[i])
week_header.push(<Header description={day_of_week_lookup[i]} key={"a112d" + grid_row_id++}/>);
}
if(!viewType.render_weekend)//remove sat, and sun header
{
week_header.pop();
week_header.pop();
}
//in return

{week_header_formatted}

Closed with commit b78214dcd7335b74a6ef1c9af2bd83b61fcd717f


[Test] Parent Child test broken with es 2.0.0-SNAPSHOT

The test below does not pass anymore on master branch (for es 2.0.0-SNAPSHOT):
mvn clean test -Dtests.method="testScriptingParentChild_51" -Dtests.class=org.elasticsearch.river.couchdb.CouchdbRiverIntegrationTest -Dtests.couchdb=true

Works fine with elasticsearch 1.5.0-SNAPSHOT (es-1.x branch)

Was due to mix between Lucene versions. This https://github.com/elasticsearch/elasticsearch-parent/commit/22163c79426b59a77bb74f761a790bb1a3dfb9cf fix it.


Identify the indicator section

Hi, Thanks for making this library.

I have a question is there a way to identify the indicator will be in which section.
I have to show some initial value and my pointer can be +- to the initial value and this value should always background of yellow.
For eg if min = 0 ; max will be 10 x initial value = 1000 and pointer value is 1100. So how to set initial value background always yellow.
Can you help me out.

So you need to have your initial value in a specific section.
If your section has a range of 0.5 to 0.7 you need to set pointer at 50%. You can use this.
// move indicator to percent value (50%)
speedometer.speedPercentTo(50)


Multi threaded code

Sometimes the threads hang I don't know why - this causes the program to hang. Performance is far better.

Thanks for your contribution, the hanging threads could have to do with #3. I will not do a new release anytime soon, was a while since I did anything related to Terraria.


ZipDeploy to Web App via Github Actions fails without any error details

Hi,
I'm setting up a new deploy pipeline with Github Actions. The action was initially created from Azure via the Deployment Center for the web app in question.
The project that gets build is a classic ASP.NET Framework (4.5.1) application. The web-app that I'm trying to deploy to has been around for many years (if that matters).
I have tried to run the deploy script both when the web-app is started and when it is stopped (to exclude locking issues).
The Github action is defined as follows:

# Docs for the Azure Web Apps Deploy action: https://github.com/Azure/webapps-deploy
# More GitHub Actions for Azure: https://github.com/Azure/actions

name: Build and deploy ASP app to Azure Web App - <webapp-name>(<webapp-slot-name>)

on:
  push:
    branches:
      - <branch-name>
  workflow_dispatch:

jobs:
  build:
    runs-on: 'windows-latest'

    steps:
    - uses: actions/checkout@v2

    - name: Setup MSBuild path
      uses<EMAIL_ADDRESS>
    - name: Setup NuGet
      uses<EMAIL_ADDRESS>
    - name: Restore NuGet packages
      run: nuget restore .\<path-to-solution>\<solution-name>.sln

    - name: Publish to folder
      run: msbuild .\<path-to-project>\<project-name>.csproj /nologo /verbosity:m /t:Build /t:pipelinePreDeployCopyAllFilesToOneFolder /p:Configuration="Release" /p:_PackageTempDir="\published\"

    - name: Upload artifact for deployment job
      uses: actions/upload-artifact@v2
      with:
        name: ASP-app
        path: '/published/**'

  deploy:
    runs-on: 'windows-latest'
    needs: build
    environment:
      name: '<webapp-slot-name>'
      url: ${{ steps.deploy-to-webapp.outputs.webapp-url }}

    steps:
    - name: Download artifact from build job
      uses: actions/download-artifact@v2
      with:
        name: ASP-app

    - name: Deploy to Azure Web App
      id: deploy-to-webapp
      uses: azure/webapps-deploy@v2
      with:
        app-name: '<webapp-name>'
        slot-name: '<webapp-slot-name>'
        publish-profile: ${{ secrets.AzureAppService_PublishProfile_<publish-profile-id> }}
        package: .

So, the source gets built, and the zip is uploaded to local/Temp and is extracted. But then it just stops and I get the following error message:
Cleaning up temp folders from previous zip deployments and extracting pushed zip file D:\local\Temp\zipdeploy\<file-id>.zip (16.98 MB) to D:\local\Temp\zipdeploy\extracted
Error: Failed to deploy web package to App Service.
Error: Deployment Failed with Error: Package deployment using ZIP Deploy failed. Refer logs for more details.

I can see that the zip has been extracted into D:\local\Temp\zipdeploy\extracted. So my guess is that something happens after that. I have enabled detailed logging but it does not give any further information about what goes wrong.
As I said, this web app has been around for many years. And there has been multiple deploy-methods. For example, I don't know if deploy.cmd is invoked in this process. If it is, there might be some mismatch there.
Grateful for any advice about how to diagnose the error and get the deploy working.

I am experiencing the exact same issue! I have also hit a wall with the logs - the "Refer logs" in the error message hasn't exactly helped either.

@sanchitmehta Any idea about this?

@bjomi @UncleJazzmus  can you try adding a secret ACTIONS_STEP_DEBUG and set the value true and see if it helps debug the issue.

@BALAGA-GAYATRI thanks for getting back!
I mentioned it in my original description of the issue, but not very clear. I did enable debugging and it did not give me any further information unfortunately.

I added ACTIONS_STEP_DEBUG  but it didn't add any new knowledge. I gave up on github actions and went back to a known working solution.

I am also running into the same issue and have tried a number of things..

ACTIONS_STEP_DEBUG : no change
Scaling up and down plan: no change
Deployments in Advanced Tools shows the deployment commits properly.. but the deployment logs only show

2021-06-20T11:41:38  An unknown error has occurred. Check the diagnostic log for details. 2021-06-20T11:41:38  An unknown error has occurred. Check the diagnostic log for details.
I have checked all available kudo and trace log files.. but nothing is showing up.. wondering if this could possibly be a webpack 5 issue.. but it builds successfully both locally and through the action.. it is just the deploy piece that is jacked up.  Possibly need to enable the ability to flip up to node 16?? but it looks like app service only supports 14LTS?
`Using Node version:
v14.15.1
Using Yarn version:
1.22.10
Running 'yarn install --prefer-offline'...
yarn install v1.22.10
[1/4] Resolving packages...
[2/4] Fetching packages...
info<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
info<EMAIL_ADDRESS>is an optional dependency and failed compatibility check. Excluding it from installation.
[3/4] Linking dependencies...
warning "@zeit/next-css ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "@zeit/next-css ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning "react-flow-renderer ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has incorrect peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
warning "ts-migrate > ts-migrate-plugins ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>|| ^5.0.0".
[4/4] Building fresh packages...
Done in 239.00s.
Running 'yarn run build'...
yarn run v1.22.10
$ next build
info  - Using webpack 5. Reason: Enabled by default https://nextjs.org/docs/messages/webpack5
info  - Checking validity of types...
info  - Creating an optimized production build...
An unknown error has occurred. Check the diagnostic log for details.
Error: Failed to deploy web package to App Service.
Error: Deployment Failed with Error: Package deployment using ZIP Deploy failed. Refer logs for more details.`
Any insight would be helpful.. on a short timeline here.. and now on like day 3 of failed deployments

I have also tried to use VC Deploy to Azure package since that uses zip deploy and I was wondering if I would get better results.. but it seems as if that one is failing as well.. same generic error with nothing in the logs to point a way forward

I have finally got it going again... it seems that Azure App Service is having an issue with webpack 5. I haven't the fainest what it is .. but if I disable webpack 5 and make the nextjs proejct use the older 4 then it will finally deploy without error.
I would maybe guess that it has to do with App Service only supporting Node 14 LTS. It would help if maybe the error messages or logging were a little clearer on what was happening and also if we had the ability to chose the desired Node version like we can in the build service.

@ehamai @JasonFreeberg Does App Service supports only Node 14LTS? The above comments says so. Your thoughts?

What is this status of this bug? When I try to deploy a file of .zip type, I get an error saying this file isn't supported. I can add images if need be.

I had the same issue with a Node+Angular app and App Service with Node 16 ... but it magically went away overnight.
Package deployment using ZIP Deploy initiated.
Error: Failed to deploy web package to App Service.
Error: Deployment Failed with Error: Package deployment using ZIP Deploy failed. Refer logs for more details.

It could have been some mixup with a previous canceled build ... as I was trying different things and canceled some builds that were taking too long. The next day pushing just a readme change triggered a successful build.
Now the build works fine, I just wanted to add here the info about canceled builds.

The same issue occurred deploying a .NET 6 application, however the next run completed successfully

@bjomi Are you using Windows? Is it still happening?

@bjomi we are closing this issue for now.
You can always re-create/re-open the issue.


txm: minimal feature set

[x] Nonce management: https://smartcontract-it.atlassian.net/browse/BCI-1112
[x] Removing Tx batching: https://smartcontract-it.atlassian.net/browse/BCI-1113
[x] Confirmation logic + tx tracking: https://smartcontract-it.atlassian.net/browse/BCI-1114
[x] fixing test cases

Yeah I reported it to Aaron, it seems to be a race in the test


Re-encrypt a repository with a new key

This would normally involve these steps:

Decrypt repository data with the old key
Re-encrypt decrypted repository data with new key
Replace old data (encrypted with the old key) with new data (encrypted with the new key)
Replace old key with new key

This feature is important in order to recover from a security compromise (if someone steals your repo keys).
Thinking of it now, step 2 is closely related to #82, so you could merge these issues, if that makes more sense.

In contrast to LUKS, which has to do the whole resigning process in place, attic has enough space to re-encrypt. Reasons to do so can be found in restic/restic#320.


Blender executable not found in expected path on Ubuntu

I noticed your CI workflow for pytest-blender didn't work again.
https://github.com/matyalatte/pytest-blender/actions/runs/8296295224/job/22705050051
In some cases, blender-downloader expects blender-x.y.z-linux-x64.tar as an output directory.
I mean, it fails to remove .tar from the path.
I think the cause is the iteration order for a Python set in controlled_full_splitext. It's arbitrary. (Idk why it worked until now tho.)

In some cases, blender-downloader expects blender-x.y.z-linux-x64.tar as an output directory.
I mean, it fails to remove .tar from the path.

You're right, the problem is to use a set there.

Hello Matya, sorry for bothering you here but we haven't spoken in a long time, you disappeared from the discrod servers and your social networks. I'm still working on the FFVIIR and Crisis Core mods. I would need help from you to be able to successfully extract audio files from a .uasset file. My intention is to be able to mute some sound files in the battle menu.
Please reply to this email. please!!
https://discord.com/channels/919508629646897234/1051817171858235472/1221769195776118835


Adding Tournament Team APIs

@adityatMS,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


[Bug]: SIGTRAP on Jest v27 + Node 16.9 in GH?

Version
27.1.0
Steps to reproduce
I haven't been able to reproduce this locally, but it fails in GitHub CI:
https://github.com/milesj/packemon/pull/86/checks?check_run_id=3571895050
Expected behavior
It should not fail on a SIGTRAP.
Actual behavior
Jest hard fails in GitHub CI with a SIGTRAP (I've never seen this before).
#
# Fatal error in , line 0
# Check failed: !holder_map.has_named_interceptor().
#
#
#
#FailureMessage Object: 0x7ffe44ff40e0
 1: 0xb691f1  [node]
 2: 0x1bf3094 V8_Fatal(char const*, ...) [node]
 3: 0x10ac4a1 v8::internal::ConcurrentLookupIterator::TryGetPropertyCell(v8::internal::Isolate*, v8::internal::LocalIsolate*, v8::internal::Handle<v8::internal::JSGlobalObject>, v8::internal::Handle<v8::internal::Name>) [node]
 4: 0x1c5aa55  [node]
 5: 0x1c5b9eb v8::internal::compiler::JSGlobalObjectRef::GetPropertyCell(v8::internal::compiler::NameRef const&, v8::internal::compiler::SerializationPolicy) const [node]
 6: 0x1e61ba3 v8::internal::compiler::JSNativeContextSpecialization::ReduceNamedAccess(v8::internal::compiler::Node*, v8::internal::compiler::Node*, v8::internal::compiler::NamedAccessFeedback const&, v8::internal::compiler::AccessMode, v8::internal::compiler::Node*) [node]
 7: 0x1e623c4 v8::internal::compiler::JSNativeContextSpecialization::ReducePropertyAccess(v8::internal::compiler::Node*, v8::internal::compiler::Node*, v8::base::Optional<v8::internal::compiler::NameRef>, v8::internal::compiler::Node*, v8::internal::compiler::FeedbackSource const&, v8::internal::compiler::AccessMode) [node]
 8: 0x1e62f0c v8::internal::compiler::JSNativeContextSpecialization::ReduceJSLoadProperty(v8::internal::compiler::Node*) [node]
 9: 0x1df5e0a v8::internal::compiler::Reducer::Reduce(v8::internal::compiler::Node*, v8::internal::compiler::ObserveNodeManager*) [node]
10: 0x1c92604  [node]
11: 0x1df60be v8::internal::compiler::GraphReducer::Reduce(v8::internal::compiler::Node*) [node]
12: 0x1df7895 v8::internal::compiler::GraphReducer::ReduceTop() [node]

 ERROR

 Failed to execute pipeline. The following errors have occurred:

 Command was killed with SIGTRAP (Debugger breakpoint): jest --coverage --colors
  --logHeapUsage
13: 0x1df7c48 v8::internal::compiler::GraphReducer::ReduceNode(v8::internal::compiler::Node*) [node]
14: 0x1ca03fd v8::internal::compiler::InliningPhase::Run(v8::internal::compiler::PipelineData*, v8::internal::Zone*) [node]
15: 0x1ca1291 v8::internal::compiler::PipelineImpl::CreateGraph() [node]
16: 0x1ca1668 v8::internal::compiler::PipelineCompilationJob::PrepareJobImpl(v8::internal::Isolate*) [node]
17: 0xd94f5d v8::internal::OptimizedCompilationJob::PrepareJob(v8::internal::Isolate*) [node]
18: 0xd96358  [node]
19: 0xd97e70 v8::internal::Compiler::CompileOptimized(v8::internal::Isolate*, v8::internal::Handle<v8::internal::JSFunction>, v8::internal::ConcurrencyMode, v8::internal::CodeKind) [node]
20: 0x11f4463 v8::internal::Runtime_CompileOptimized_Concurrent(int, unsigned long*, v8::internal::Isolate*) [node]
21: 0x15e67f9  [node]

 ERROR

 Failed to execute pipeline. The following errors have occurred:

 Command was killed with SIGTRAP (Debugger breakpoint): jest --coverage --colors
  --logHeapUsage

Additional context
I've hit this on multiple PRs now, so reporting here for others to see.
I'm trying to reproduce this locally with no luck, so I have to keep pushing to trigger CI.
I will attempt different versions and combinations and report back:
FAILS:

node 16.9, jest 27.1 --logHeapUsage --coverage - https://github.com/milesj/packemon/pull/86/checks?check_run_id=3571895050
node 16.9, jest 27.1 --logHeapUsage
node 16.9, jest 27.1 - https://github.com/milesj/packemon/pull/86/checks?check_run_id=3571950244
node 16.9, jest 27.0 - https://github.com/milesj/packemon/pull/86/checks?check_run_id=3571997318

Environment
This is my local machine and not GitHub CI.
  System:
    OS: macOS 11.5.2
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 16.9.1 - ~/.nvm/versions/node/v16.9.1/bin/node
    Yarn: 3.0.0 - ~/.nvm/versions/node/v16.9.1/bin/yarn
    npm: 7.21.1 - ~/.nvm/versions/node/v16.9.1/bin/npm
  npmPackages:
    jest: 27.1.0

I wonder if this fixes it: https://github.com/nodejs/node/commit/1b335d41a405f491a84c4d8cb51fabd4615c0306

Yeah seems like it: https://github.com/nodejs/node/issues/40030

yup


Sqlglot version pinned

Describe your changes
Issue number
Closes #X
Checklist before requesting a review

[ ] Performed a self-review of my code
[ ] Formatted my code with pkgmt format
[ ] Added tests (when necessary).
[ ] Added docstring documentation and update the changelog (when needed)

:books: Documentation preview :books:: https://jupysql--961.org.readthedocs.build/en/961/

we can merge it as is. but I think you said the problem was 0.20
shouldn't the change be <20.0.0?

shouldn't the change be <20.0.0?

yes it was a typo i meant <=19.9.0. Fixed it now @edublancas


gh-2881-Problems with getOriginalSchema in Federated and Proxy Stores

Related Issue

Resolve #2881

Codecov Report

:exclamation: No coverage uploaded for pull request base (v2-alpha@1f4eaed). Click here to learn what that means.
The diff coverage is n/a.

:exclamation: Current head 6ee9138 differs from pull request most recent head 33d63be. Consider uploading reports for the commit 33d63be to get more accurate results

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             v2-alpha    #2884   +/-   ##
===========================================
  Coverage            ?   69.46%
  Complexity          ?      494
===========================================
  Files               ?       79
  Lines               ?     1513
  Branches            ?      114
===========================================
  Hits                ?     1051
  Misses              ?      380
  Partials            ?       82

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

This PR also includes changes to remove use of and delete the following deprecated methods from the Federated Store:

getSchema from FederatedGraphStorage.java.
getFederatedWrappedSchema from FederatedStoreUtil.java.

6 tests from FederatedGraphStorageTest which had been marked as deprecated (due to using the above getSchema method) have been migrated to StoreSchemaTest.

Approved.


The Firebug alpha changes Firefox DE's dark theme to the default Firebug light theme

I'm not sure if there's major compatibility issues with this theme (see #225 for an example of one in which the dark theme actually works better), but it doesn't seem very nice to force users to change themes when they install Firebug (especially when the theme flips all the colors).

think that firebug should inherit colors from default user theme,
for me its better to work with dark theme, and if you say that i must use light theme for new features, its something wrong with addon. addon should apper with theme that i want to use.

Well, I also actually think that FB should "augment" the default themes instead of setting a new one. But in any case - it's not that huge of a deal. However I would be really happy if the theme is only applied to the inspector tools and not to the whole firefox??? Is it at all possible?


setuptools_scm replaces version with local git reference

What happened:
Trying to build h5netcdf 0.14.1 from source extracted from the h5netcdf pypi source tarball, but stored locally in a git repo, the version file gets corrupted to a random reference derived from my local git repo.
The file corruption is triggered when running the clean rule with setup.py. It must be a consequence of the setuptools_scm change to setup.py introduced in PR #146  (commit 5a29b6c)
For instance, running from the source dir which also happens to contain a .git folder,
/build/python-h5netcdf$ cat h5netcdf/_version.py
# coding: utf-8
# file generated by setuptools_scm
# don't change, don't track in version control
version = '0.14.1'
version_tuple = (0, 14, 1)

/build/python-h5netcdf$ python3 setup.py clean
running clean

/build/python-h5netcdf$ cat h5netcdf/_version.py
# coding: utf-8
# file generated by setuptools_scm
# don't change, don't track in version control
version = '0.13.0.dev3+g26a0104'
version_tuple = (0, 13, 0, 'dev3', 'g26a0104')

The last local git commit (which loaded the h5netcdf source into the git repo) was 26a0104064, giving a clue where the corrupted version reference came from.
It looks like the new PR #146 arrangement using setuptools_scm is not robust.   _version.py gets overwritten by local git conditions.
If setup.py is no longer supposed to be used to build the package, since there is a pyproject.toml file, then maybe setup.py should be removed altgether? (the new PEP 518 regime)
What you expected to happen:
The version should remain unchanged as 0.14.1
Anything else we need to know?:
The h5netcdf is stored in a git repo for debian package, https://salsa.debian.org/science-team/python-h5netcdf
The pypi source tarball is used since usually it represents the source as intended for installation and usage. The source tarball provided by github is sometimes discrepant from the release tarball.
Version
0.14.1

It's the tool.setuptools_scm entry in pyproject.toml that's causing the version file corruption.

@drew-parsons Thanks for bringing this to attention. I'll have a look into this. If you have any idea how to resolve this, please let us know.

From all what I could gather in short time, the suggestion of setuptools_scm devs is to use environment variable SETUPTOOLS_SCM_PRETEND_VERSION end provide the wanted version there during the build. That was especially recommended for debian-packaging, see https://github.com/pypa/setuptools_scm/issues/361.
This works flawless locally:
$ cat h5netcdf/_version.py
# coding: utf-8
# file generated by setuptools_scm
# don't change, don't track in version control
version = '1.14.1'
version_tuple = (1, 14, 1)

$ SETUPTOOLS_SCM_PRETEND_VERSION=1.14.1 python setup.py clean
running clean

$ cat h5netcdf/_version.py
# coding: utf-8
# file generated by setuptools_scm
# don't change, don't track in version control
version = '1.14.1'
version_tuple = (1, 14, 1)

XRef<EMAIL_ADDRESS>

Thanks for checking on it.  I'll look into what our build tools are doing with SETUPTOOLS_SCM_PRETEND_VERSION

@drew-parsons Did you come any further with this? h5netcdf is approaching version 1.0 in late March. Would be good if there are no blocking issues for packaging.

In the short term I've worked around it by patching out the setuptools_scm configuration.  We can continue doing that until we tracked down how SETUPTOOLS_SCM_PRETEND_VERSION gets used.
SETUPTOOLS_SCM_PRETEND_VERSION is referenced in /usr/share/perl5/Debian/Debhelper/Buildsystem/pybuild.pm from the debian dh-python package. I'm trying to confirm if the code path using it gets activated during the h5netcdf build.

Thanks, good to hear you have a working state. I'll leave this open until resolved.

I think I can see what's going on Setting SETUPTOOLS_SCM_PRETEND_VERSION explictly will no doubt work, but the debian pybuild tool already provides management of the variable.  What pybuild does is check whether setuptools-scm has been included in the build dependencies for the package. If so, then pybuild uses the debian build configuration to set a value for SETUPTOOLS_SCM_PRETEND_VERSION (if it isn't already set).
So the solution for the debian package is simple: just need to add Build-Depends: python3-setuptools-scm to the package.
With that done, we can close this Issue.

Yes sorry, this will be fixed in #158.

Looks like it's under control then.  The problem I reported here is a build configuration issue, not a h5netcdf issue, so I'll close this issue now.

Great.  I'll package 0.15.0 once it's done.


Enhancement/2968/add summary card

What is the context of this PR?
Added a new summary variant where the groups are rendered in a card layout as shown in this prototype
How to review this PR
Navigate to the summary components and compare the new  example-summary-card-grouped with the available prototype
Checklist
This needs to be completed by the person raising the PR.

[x] I have selected the correct Assignee
[x] I have linked the correct Issue

We will probably need to cover some of this new functionality with some tests too

A border has been added to the bottom of the example-summary-multiple summary

There is a border added to summaries that have a link at the bottom that stretches right across the card

This looks a bit odd when there is an error, is it supposed to look like this?

A border has been added to the bottom of the example-summary-multiple summary

There is a border added to summaries that have a link at the bottom that stretches right across the card

A border has been added to the bottom of the example-summary-multiple summary

This is present in the main branch code also, should I change it?

A border has been added to the bottom of the example-summary-multiple summary

There is a border added to summaries that have a link at the bottom that stretches right across the card

A border has been added to the bottom of the example-summary-multiple summary

This is present in the main branch code also, should I change it?

Yeah ok forget the multiple one but the other one has the border but it doesn't look so odd because it doesn't stretch right across when all the other borders have gaps either side

Household summary with rows looks good but when there are no rows it doesn't look right anymore

This problem exists in main branch as well when there are no rows, but will look into this!

Household summary with rows looks good but when there are no rows it doesn't look right anymore

This problem exists in main branch as well when there are no rows, but will look into this!

I don't think it is an issue in main, this is how it is meant to look https://service-manual.ons.gov.uk/design-system/components/summary/example-summary-household-no-rows I think the card version just needs some padding and the removal of the border


Merge back master to develop

I do not fully understand why the diff shows that many changes although the files are identical on master/develop. I'll close this and create a branch with a merge commit instead.


bump java to grpc 1.5.0

LGTM
Let's see if Travis will pass here.

I saw the same class not found issue locally but wanted to see if travis would get passed it. Doesn't seem to be, so I'm investigating.

@michael-berlin this is working now.  The error message changed which was breaking some tests, so I fixed that. I also upped the timeout on the test because sometimes on my machine or under load it may take longer than 4s for the vtgate to be accepting queries.
I also tried removing the netty-tcnative-boringssl-static, but couldn't. In fact I had to update it to latest as well.

Sounds good! Thank you for doing this :-)
Merging now.


Issue in parallel plesk

I have installed letsencrypt-plesk, but getting an error like

This operation is taking too long. Check the results in a few minutes

Anybody has any idea ?

Please check the log file /usr/local/psa/var/modules/letsencrypt/logs/letsencrypt.log
What is the last record there?

In the latest version 1.7 of the extension we use --non-interactive flag, that should prevent hanging (waiting for input) and properly report errors.
Please, check the issue again and feel free to reopen.