Usability: Warning when user calls "return" from their autoqasm entry point function

Issue #, if available:
Description of changes:
Warn if the called function returns a value
Testing done:
New unit tests
Merge Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your pull request.
General

[x] I have read the CONTRIBUTING doc
[x] I used the commit message format described in CONTRIBUTING
[x] I have updated any necessary documentation, including READMEs and API docs (if appropriate)

Tests

[x] I have added tests that prove my fix is effective or that my feature works (if appropriate)
[x] I have checked that my tests are not configured for a specific region or account (if appropriate)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Looks great!


query Id

Can you add query Id mode?

bro this bot already have query option

bro this bot already have query option

Sorry, true, have :)


[Bug]: typespec-azure-resource-manager and typespec-azure-core still uses enum

Describe the bug
https://github.com/Azure/typespec-azure/blob/main/packages/typespec-azure-resource-manager/lib/arm.foundations.tsp#L435-L451
https://github.com/Azure/typespec-azure/blob/main/packages/typespec-azure-core/lib/foundations.tsp#L17-L33
If they are open enum, it should be written as union.
see https://azure.github.io/typespec-azure/docs/howtos/DataPlane Generation - DPG/06types
Reproduction
SDK emitters would deprecate @fixed and interpret typespec enum as closed enum. That require all open enum written as union in core libs and spec repo.
playgroud
typespec-autorest still interpret it as open enum "modelAsString": true.
Checklist

[X] Follow our Code of Conduct
[X] Check that this issue is about the Azure libraries for typespec. For bug in the typespec language or core libraries file it in the TypeSpec repo
[X] Check that there isn't already an issue that request the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

This was done by design to give one sprint migration help to in flight teams. If we made the change immediately users spreading our enums(now unions) would have received errors that are much more confusing than the current warning with a codefix.

Thanks Timothee.
I can understand that the behavior of typespec-autorest is to provide this one sprint migration time.
However, without the change of enum -> union in core libs, SDK emitter would had to wait for the completion of core lib change, before itself do the change (it had to take enum as open enum, till core lib done the migration).
I am fine with the SDK emitter wait for next sprint. It just that some language emitter already switched, hence there be some inconsistency between emitters.

Yeah we should not see any bare enums (apart from the ones in the typespec lib) as the linting rule to ban those is in.
The behavior for this sprint is:

use @fixed to be explicit if you want a fixed enum
use open union
no unannotated enum

next sprint:

remove @fixed

Thanks Timothee. Got it, then emitter would switch in next sprint as well. You can close the issue.

@markcowl
The one in typespec-azure-core still is enum https://github.com/Azure/typespec-azure/blob/main/packages/typespec-azure-core/lib/foundations.tsp#L17-L33
And devcenter uses it https://github.com/Azure/azure-rest-api-specs/blob/main/specification/devcenter/DevCenter/DevBox/models.tsp#L733

Attempt a PR here https://github.com/Azure/typespec-azure/pull/851

There are a few other enums in ARM lib, e.g. https://github.com/Azure/typespec-azure/blob/main/packages/typespec-azure-resource-manager/lib/common-types/types.tsp#L112-L125
Are they supposed to be union as well?


Genoa: detour instead of straight

When I was in Genoa last month I realized that the navigation suggested a little detour around a traffic light. Is this a graphhopper issue or an OSM mapping issue?
https://www.openstreetmap.org/directions?engine=graphhopper_car&route=44.41466%2C8.91347%3B44.41162%2C8.90804#map=18/44.41299/8.91075

The problem is a turn restriction: https://www.openstreetmap.org/relation/3650936
I changed it: https://www.openstreetmap.org/changeset/60231263
Hope it works.


Made ngAnimate an optional dependency

Made ngAnimate an optional dependency to satisfy issue #125.  Updated corresponding documentation and added minified version of toaster.js

Thank you for the PR!

@jirikavi  My pleasure :)


AWS ECS Fargate Docker image changes not recognized

I followed the steps described here: https://pulumi.io/quickstart/aws/tutorial-containers-ecs-fargate.html
The following snippets works fine for the initial setup of ECS/Fargate.
const cloud = require("@pulumi/cloud-aws");

let service = new cloud.Service("pulumi-nginx", {
    containers: {
        nginx: {
            build: "./app",
            memory: 128,
            ports: [{ port: 80 }],
        },
    },
    replicas: 2,
});

// export just the hostname property of the container frontend
exports.url = service.defaultEndpoint.apply(e => `http://${e.hostname}`);

When I change the Docker image and rebuild it with pulumi update I see the newly built Docker image in ECR but the ECS/Fargate Task won't be update. Is this a wanted behaviour? I would expect that the newly built Docker image will be deployed on AWS Fargate.
If I use an image e.g. with image: "nginx:1.15.3" instead of the build definition everything works as expected.

This issue was moved to pulumi/pulumi-cloud#595


chore: clarify sort for blobs

Partially addresses https://github.com/celestiaorg/celestia-core/issues/887 by removing two exported methods which are no longer needed after this refactor: https://github.com/celestiaorg/celestia-core/pull/879#discussion_r1019587387 and addressing this feedback: https://github.com/celestiaorg/celestia-core/pull/879#discussion_r1019596230
Testing
After this change, celestia-app can sort a slice of blobs via:
sort.Sort(coretypes.BlobsByNamespace(data.Blobs))

and verify a slice of blobs is sorted via:
if sort.IsSorted(coretypes.BlobsByNamespace(data.Blobs)) {
    // ...
}

No need for separate issue, will keep https://github.com/celestiaorg/celestia-core/issues/887 open until the rename is complete

why is the generated proto failing? that doesn't make any sense

I am having the same proto files fails on my branch. Apparently, the local version of proto is different from the CI one

Looks like a test flake
--- FAIL: TestTransportHandshake (0.03s)
    transport_test.go:616: read tcp <IP_ADDRESS>:43525-><IP_ADDRESS>:37216: i/o timeout


{CI} Add check init.py file in all extensions

Check if the vendored_sdks directory contains __init__.py in all extensions.
Will exclude empty vendored_sdks dir, for example:
azure-cli-extensions\src\containerapp-preview\azext_containerapp_preview\vendored_sdks is a empty dir that didn't contain any files.
Test screenshot:

Add check for init.py file

I think an alternative solution is to use find_namespace_packages to build a namespace package, but this is not an easy job.

I think an alternative solution is to use find_namespace_packages to build a namespace package, but this is not an easy job.

This is a very good suggestion, it solves the problem fundamentally, but we need to modify the setup.py files of all extensions
Test screenshot:


form.parse callback is not called when run on Firebase functions (Node v8)

Support plan

which support plan is this issue covered by? (e.g. Community, Sponsor, or
Enterprise):
is this issue currently blocking your project? (yes/no): yes
is this issue affecting a production system? (yes/no): yes

Context

node version: 8 & 10
module (formidable) version: 1.2.2 & 2.0.0-canary.20200504.1
environment (e.g. node, browser, native, OS): Firebase functions
used with (i.e. popular names of modules): Express
any other relevant information:

What are you trying to achieve or the steps to reproduce?

exports.importExcelSpreadsheet = functions.https.onRequest(async (req, res) => {
  try {
    console.log('Parsing multipart form');

    const parsedForm = await new Promise((resolve, reject) => {
      console.log('Start parsing form');

      const form = new formidable.IncomingForm();
      form.parse(req, (err, fields, files) => {
        console.log('Finished parsing form');

        if (err) {
          return reject(err);
        }

        resolve({fields: fields, files: files});
      });
    });

    console.log('parsedForm', parsedForm);

    var file = parsedForm.files.fileToUpload;
    if (!file) {
      throw new Error("No file to upload, please choose a file.");
    }

    console.log('processing file ', file);
    res.status(200).send({});
  } catch (e) {
    res.status(500).send(e);
  }
});

What was the result you got?
The form.parse callback is never called.
What result did you expect?
The form.parse callback is called.
This seems similar to issue https://github.com/node-formidable/formidable/issues/396.
Wrapping the form.parse in a Promise is the recommended solution but it hasn't worked for me

StackOverflow: Firebase cloud function for file upload
StackOverflow: nodejs formidable async issue

What can I do to understand what's happening under the covers?

Yes, known issue. Use the package serverless-formidable. It will be integrated and handled in the next major release, so stay tuned and update to it when it's out of canary/beta.

Great news, thx!

@tunnckoCore I tried the latest canary release of formidable but that didn't work so maybe it's not currently in there. When do you think roughly the next major release will be?

Had this same issue too, when I deployed my code to Google Cloud using Firebase Functions. Only had it fixed when I used formidable-serverless-2. Thanks, guys!

@lexNwimue do you have the link of this package? I did not found it.
Thanks

https://www.npmjs.com/package/formidable-serverless-2


[BUG] size is not always equivalent to h- and w-

Describe the bug
While in general it is a good idea to use size- instead of h- and w-, those two definitions are not the same in all situations.
In particular if the selected tokens do not com from the spacing scale, the same names can mean different things.
It could also happen, that the size- utility does not exist at all.
To Reproduce
Steps to reproduce the behavior:

Define the following tailwind settings:export default {
    theme: {
        width: {
            dialog: "26rem"
        },
        height: {
            dialog: "30rem"
        }
    }
};

Use the tokens like this: class="h-dialog w-dialog". This works as intended.
Run eslint autofixes with tailwindcss-plugin installed. This replaces the above with class="size-dialog".
The size-dialog class does not actually exist, because dialog does not exist in the spacing nor in the size scale. In fact the area is not even square.

Expected behavior
Ideally the linting rules would detect, that the two variants are not equivalent and not suggest the replacement.
Environment (please complete the following information):

OS: Arch Linux
Softwares + version used:

<EMAIL_ADDRESS><EMAIL_ADDRESS>

@bodograumann thank you for reporting this issue.
I made a basic test on Tailwind Play https://play.tailwindcss.com/PS0lBwtsJc
In the test the config I use  has the same value for the square key on both width and height
      width: {
        custom: '160px',
        square: '100px',
      },
      height: {
        custom: '90px',
        square: '100px',
      },

Yet, the size-square classname is not generated by Tailwind... The size classnames are in fact based on the spacing key of the configuration...
I'll work on it soon, for now you can simply disable the entire rule or just specific lines where it is needed.

Please try it via npm i<EMAIL_ADDRESS>-D and let me know how it goes. 😉

Thanks for looking at this so quickly, @francoismassart .
I can confirm that the change in https://github.com/francoismassart/eslint-plugin-tailwindcss/commit/228f3b78d399d69225df4490d9cf1a6c7ee635c5 indeed avoids the problem.
It is a bit too conservative though, I feel. There are some values allowed for size- that should work well.
Not sure about all the details of the tailwind implementation, but e.g. size-full is the same as h-full w-full, as long as the user has not overriden any of those utils.

I thought (reading their doc) that it was only based on the spacing config...
But I can see a dedicated entry in the config for size in the Tailwind CSS repository.
I'll release a new beta later today

@bodograumann  Please try this beta version:
npm i<EMAIL_ADDRESS>-D
and give me feedbacks.

Yes, now it works for h-full and w-full. :heart:
Still to make completely sure, that the replacement does not change the design, I think the following should be done:

Lookup w- in the width scale.
Lookup h- in the heigth-scale.
Lookup size- in the size-scale.
Check that all three have identical values.

I mean it is an edge case, that someone decides to define a size- value which does not conform to the w- and h- values, but you never know. Given that the change is done automatically with --fix, I think we should rather be careful.

@bodograumann please take the time to configure this edge case inside a Tailwind Play and share its URL so that I can test it out.

Here you go: https://play.tailwindcss.com/XPnP68FJ85

Fixed in the latest release<EMAIL_ADDRESS>

Thanks for all your effort!

Does anyone have this problem: after eslint converts all to size, somehow tailwind does not build into CSS this size- class so my UI is all broken because of lacking width and height. So I have to manually convert all size- back to h- and w-

@nguyenleccss361 for now disable the enforce shorthand rule. And if you want me to take a look at it, share a minimal project exposing the issue.


ImproveRunningTestsResults

Improve current progress output of dotnet test
#2173

@DineshChirnanchu We do not have the spec closure here. Why are we still working on this one ?

This needs more thinking, closing it for now. We'll pick this up later.


Epic Roadmap

Describe the bug
A clear and concise description of what the bug is.
Browser
Choose a browser
[ ] IE11
[ ] Chrome
[ ] FireFox
[ ] Safari
Edge
Version
[X] Azure DevOps/VSTS
[ ] TFS 2017 Update 2/3
[ ] TFS 2018
Screenshots

I tried with Epic Roadmap… it was working OK when there was two Epics.. Now I have 6 Epics and the following message is arising:
"Expecting constant value. The error is caused by <<)>>"

I am experiencing this issue as well. Near as I can tell, there are no Epic work items that have ) in their title (at least in the team project where I see this crop up)

We are also getting this issue.
Currently have 7 epics, so I don't know when it started, but I do know it was working fine when I demoed the feature with just one.
One of the epics contains an & and another contains a -, the rest have no special characters. None contain a ).


added _guess_info

closes #97

Codecov Report

Merging #105 (b50db46) into master (3896b5d) will decrease coverage by 5.40%.
The diff coverage is 10.00%.

: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
Additional details and impacted files

@@            Coverage Diff             @@
##           master     #105      +/-   ##
==========================================
- Coverage   78.93%   73.54%   -5.40%
==========================================
  Files          22       22
  Lines        1111     1149      +38
==========================================
- Hits          877      845      -32
- Misses        234      304      +70

Flag
Coverage Δ

unittests
73.54% <10.00%> (-5.40%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

cordex/utils.py
17.39% <10.00%> (-49.28%)
:arrow_down:

cordex/preprocessing/preprocessing.py
63.03% <0.00%> (-17.07%)
:arrow_down:

cordex/cmor/cmor.py
64.68% <0.00%> (+0.23%)
:arrow_up:

cordex/cmor/utils.py
92.07% <0.00%> (+0.90%)
:arrow_up:


Exposing option to enable support for asserts w/ messages

From @sethladd on September 2, 2015 19:25
Following on the work from https://github.com/dart-lang/sdk/issues/24217
We'd love a flag so a user can opt-in and try this out.
Thanks!
Copied from original issue: dart-lang/analyzer_cli#59

From @bwilkerson on September 2, 2015 19:39
One possible approach for this would be to add the flag via the .analysis_options file.

From @stereotype441 on September 2, 2015 20:22

One possible approach for this would be to add the flag via the .analysis_options file.

The difficulty with this approach is that it interacts badly with our shared test infrastructure.  At the moment the only way for the shared test runner to specify to the implementations (the VM, dart2js, and the analyzer) that a work-in-progress feature should be enabled is to pass in a command line flag.  So we have to support the command line flag no matter what.
In principle, we could add .analysis_options support as an additional mechanism, however given that this DEP is a small backward-compatible feature addition, I suspect that it won't be too long before we just turn the feature on unconditionally.  In which case any additional work we do to support it in .analysis_options is going to be wasted effort.

From @sethladd on September 2, 2015 19:41
You read my mind! :)

This issue was moved to dart-lang/sdk#25142

From @bwilkerson on September 2, 2015 21:55
A command-line option for the command-line analyzer is fine, but that doesn't play nicely with the analysis server. It seems like overkill to ask clients to add a flag when invoking server and then turn around and ask them to remove it. And if we're going to support putting the option in the file for server, then we could just as easily support it that way for the command-line analyzer. It's sad that we have to duplicate effort to satisfy the test framework, but it's not that much work and the options file approach can be shared.

This issue was moved to dart-lang/sdk#25141

Duplicate of #25142 .


feat(RHTAPREL-732): update magefile for release-service-catalog repo

Description
Our goal is to test release-service-catalog changes with the release-pipelines suite. We do not need to deploy a special version of the release-service for this task, for now.
Issue ticket number and link
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/test redhat-appstudio-e2e

/retest

/lgtm

/test redhat-appstudio-e2e


Kubernetes-101,  Chapter 1, "Instructions for Minikube" Fail

I purchased the Kubernetes-101 book via Amazon via your link several months ago and then I contracted COVID and it lingering effects.  So I am just now running through the book.
I use a MacBook Pro, 2019 running Ventura 13.3.1., 32 Gb DDR4, Radeon Pro 55600 -8Gb.
I use Virtual Box 7.0 and, recently, Parallels newest version to support Windows.
(Retired Programmer 42+ years OTJ now helping out family and friends with computer issues for free.)
Following the instructions to install minikube it failed with a notification to use VirtualBox 5.6 and the 3 GitHub issues listed that basically said the same thing as the install fail notification upon examination.
I deleted minikube, kubectl, and VirtualBox.  Shutdown to a cold boot and then followed the instructions again with the same issue resulting.  So, I deleted all again, hard boot and this time use curl instead of brew to install the three packages.  Same thing.  (I know that was a "if x ='1' then move '1' to x" solution but I thought what the heck, stranger things have happened.)
I am now thinking that this obviously worked at the writing date in 2021 so it must be a time and versioning bug.
I went to the Kubernetes K8s minikube start page and followed the instruction but this time I used Parallels with the minikube start as my VM and it worked.
At this point I thought about redoing using the start and the --VirtualBox option but I was so happy to have a working system and to be able to continue with the book that I said I'd try that at a later date.
Just thought this might be something to incorporate in a revision.
However--
One caveat:  All of this could be the way I have setup my MacBook.  Up until about 2 years prior to my retirement, my work involved IBM iron and Microsoft.  Mac and Linux were really only used after 4/1/2016 with regularity.  So a big block of salt.
Big fan of you vids and always look forward to the next installment.  Kudos!

Correction: Radeon 5500 not 55600. Fat fingered.


Using the DVDPlayer

Hi,
I have mounted a valid DVD ISO file to a virtual DVD drive, and it is playing fine with VLC.
When I try to use the DvdPlayerElement to play it, I get the following exception:
A first chance exception of type 'System.Exception' occurred in WPFMediaKit.dll
Additional information: Could not find the sub picture pin out
What do you think could be the issue here?
Thanks!

Looks like some problems with your codecs. Can you play any video on a local disk with MediaUriElement?


Terminal is Crashing when trying to open new tab

Environment
Windows build number: [run `[Environment]::OSVersion` for powershell, or `ver` for cmd]
Windows Terminal version (if applicable): Latest from Microsoft Store

Any other software?
```None

# Steps to reproduce

<!-- A description of how to trigger this bug. -->
1. Launch Windows Terminal
2. Try to open new tab

# Expected behavior

<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->
It should open new tab normally

# Actual behavior

<!-- What's actually happening? -->
It's trying to open new tab, but then it crashes

You’ve filed 3 new bugs then immediately closed them. Is everything okay?

Yeah, Sorry, it was my bad, because it was my first time when I was opening
issue on GitHub
sob., 12 wrz 2020, 09:21 użytkownik Dustin L. Howett <
<EMAIL_ADDRESS>napisał:

You’ve filed 3 new bugs then immediately closed them. Is everything okay?
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/terminal/issues/7613#issuecomment-691433155,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQ66ZFAQMXRTWY6SALHRV2TSFMOQHANCNFSM4RJDOMDA
.


[Bug]: Fix fusion to echart UI consistency issues

Is there an existing issue for this?

[X] I have searched the existing issues

Description
There are multiple issues that will be listed down here to maintain the consistency between fusion charts and echarts.
Steps To Reproduce
NA
Public Sample App
No response
Environment
Production
Issue video log
No response
Version
Cloud

@laveena-en
Can you please help with an acceptance criteria of all the edge cases that should be supported in the widget ?
Based on that list, we can decide how to fix those cases and request the user to convert to custom echart for use cases beyond those edge cases.
cc : @somangshu @dilippitchika


TLS handshake with Harbor failing

Bug report:
This may be an issue with our Harbor, but just wanted to see if this is something you have seen @gaius-qi  @jim3ma
{
  "level": "error",
  "ts": "2023-12-20 15:14:45.808",
  "caller": "proxy/proxy.go:476",
  "msg": "handshake failed for <REDACTED HARBOR URL>:443: EOF",
  "stacktrace": "d7y.io/dragonfly/v2/client/daemon/proxy.(*Proxy).handleHTTPS
            /go/src/d7y.io/dragonfly/v2/client/daemon/proxy/proxy.go:476
d7y.io/dragonfly/v2/client/daemon/proxy.(*Proxy).ServeHTTP
            /go/src/d7y.io/dragonfly/v2/client/daemon/proxy/proxy.go:355
net/http.serverHandler.ServeHTTP
            /usr/local/go/src/net/http/server.go:2936
net/http.(*conn).serve
            /usr/local/go/src/net/http/server.go:1995"
}

Expected behavior:
Successful TLS handshake with Harbor
How to reproduce it:
Attempt to download a singularity image with Harbor using dfdaemon in proxy mode.
This was seen in a very small percentage of a large number of downloads, around 0.02%
Environment:

Dragonfly version:v2.0.10
OS: Linux
Kernel (e.g. uname -a): 5.x
Others:

There is no evidence that this is an issue with Dragonfly, so I am closing it.


Add configurable gpu thermal zone

I noticed a bug where the tempFile was the entire path (instead of just the subpath) leading to some issues. So I fixed that and also added an option to set the entire path via the config since I'm not sure if the path will be the same for everyone.
If the path: device/hwmon/hwmon0/temp1_input won't change across machines then the configuration addition probably isn't needed since you can configure the card.

Thank you for the PR!
This review is a bit more pedantic, since I want the config variables to behave consistent. I hope you understand :)
Some general points:

Can you make the config variable relative to /sys/class/drm/<card>/? (Since there is already a selector for the specific card)
The config variable + documentation is missing from data/config

Yeah for sure. I wasn't sure if that was how you wanted it done since it would be a little different than setting a CPU thermal zone (since for that we set a full path instead of a partial). To remove this difference between gpu/cpu's It might be worth changing things to only use full paths instead of setting the drmAmdCard with extra configuration for the sub path.
For example we could have config options for

AmdGpuUtilizationPath
AmdGpuThermalPath
AmdGpuVramPath

Removing the need for setting an explicit DrmAmdCard which is a little more work for the user, but a lot less confusing then adding arbitrary partial paths.
This would make things more inline with how things are set for the CPU. Let me know what you think, otherwise I can move forward with the points above (:

Hmm, good points. I've thought about it a little and I think I still prefer relative paths, though:

Absolute paths would require either breaking old configs by removing DrmAmdCard or basically duplicating functionality in case AmdGpu* are not set. I'm not particularly fond of either of these options.
The 4 file configs (utilization, total vram, current vram and thermal zone) would all need to be present and each manually configured when changing the card index. IMHO this is a bit too much, especially since probably most (if not all) users will never want to change 3 of the 4 files.

Yeah sounds good, using relative paths is good for now, I'll get this updated to use them. It might be worth at some point looking into using a dependency or library that handles these queries in the future, or looking at what other bars/widgets do to solve this, not that it is that big of a deal haha.

Last thing missing now is an entry in data/config with documentation (Can be copy-pasted from module.nix). Other than that, LGTM.

LGTM, thanks!


hard to get started

im having a lot of errors since im implemeting from 0
Theres no simple code to copy/paste and get started

https://docs.sheetjs.com/#parsing-workbooks
Enjoy!


Enumerate project dependencies in the setup.py

install_requires=[
          'termcolor', 'six'
      ],

can be checked by using python install virtualenv
pyvenv prefix
source prefix/bin/activate
pip install termcolor
pip install six

We read the install_requires in requeriments.txt and assing them in required var.


Training will ony run over 3 steps

Hi,
i have tried to run your code but for some reason when training in Train.py line 70 it will only run for 3 steps and then finish. this seems a bit odd as i would have assuemed it would run over all the images?!
hope for quick feedback :)

Line 70 of Train.py seem data loader. If your dataset structure is different to README file, some errors will occur from data loader. Could you show your error message?

this is what i have changed in the parameters.py file:
class Parameters():
    save_path = "data/savefile/"
    model_path = ""
    train_root_url="data/dataset/train_set/"
    test_root_url="data/dataset/test_set/"

in the data_loader.py file i have changed the location to:
with open("data/dataset/five.json") as f:

the structure of the data folder is see the attached file.
i hope you can guide me to fixing this :)
tree.txt

It looks fine. If you show me your error message, debugging will be more clear

File "main.py", line 81, in Train
lane_agent.save_model(int(step/100), loss_p)
File "/root/handler.py", line 312, in save_model
self.p.save_path + str(epoch) + '' + str(loss) + '' + 'lane_detection_network.pkl'
File "/usr/local/lib/python3.7/dist-packages/torch/serialization.py", line 369, in save
with _open_file_like(f, 'wb') as opened_file:
File "/usr/local/lib/python3.7/dist-packages/torch/serialization.py", line 234, in _open_file_like
return _open_file(name_or_buffer, mode)
File "/usr/local/lib/python3.7/dist-packages/torch/serialization.py", line 215, in init
super(_open_file, self).init(open(name, mode))
FileNotFoundError: [Errno 2] No such file or directory: 'savefile/0_tensor(5.8034)_lane_detection_network.pkl'

i am currently using python3.7

It looks like path problem. Try to set the path to absolute path


TIC website improvements

added games rating, click to  to +1
show game views for the game owner
added popular/new sorting
added title, description and etc metadata to the page header

added simple 16x16 avatar editor to user profile

added comments counter to the main page

added notifications page
it shows you users who commented/likes your games

more in next versions
closing...


Faster oom test

Build on top of #97, so drafting.
Also haven't tested that this test actually fails before streaming was merged. (yet)

Added beef55f , which can be dropped before merging as per reviewers preference. It verifies that the test case actually fails when run against the old non-streaming version of Wharfix - primarily as a help for this review.

Ok..
1a9dd4c converts to callPackage.
fb489f8 takes it a step further and converts the "positive" and "negative" oom scenario into two different test cases. It has the advantages that we don't need to re-run the negative test each time wharfix changes, especially since the negative test is slooow due to having to wait for docker pull 5 times retry before it finally gives up. It also underlines why having the negative scenario in there is perhaps a bad idea in the first place? One could argue that we should add negative scenarios for all tests then (i.e. for "ref" as well)? Also, it makes it obvious that the wharfix flake now depends on an older version of self (which is maybe not nice?) - which - it did before fb489f8 as well; only difference is that now it has become more visible.
I'm fine with merging this with or without the negative scenario :) it's up to the reviewer.

Consider e.g. if the kubernetes image for some reason changes size at some point with a nixpkgs bump

I thought of that too, but I didn't wanna pin and instantiate an entire nixpkgs (and potentially re-build kubernetes) just to get a reproducible layer :p Instead, we could do something like this: 20c7596 . Basically just download and pin some big enough artifact  (which is not an output). Let me hear what you think.

Consider e.g. if the kubernetes image for some reason changes size at some point with a nixpkgs bump

I thought of that too, but I didn't wanna pin and instantiate an entire nixpkgs (and potentially re-build kubernetes) just to get a reproducible layer :p Instead, we could do something like this: 20c7596 . Basically just download and pin some big enough artifact (which is not an output). Let me hear what you think.

Let's do this then, seems reasonable enough :+1:

Mind re-approving then? :) Then let's just merge this.


Fix hover stuttering.

For #11422
We were too aggressive in our hover closing. The bug was caused by hovering over one item closing another. This is unnecessary if inside the same window still.
Note, this isn't a regression, but while figuring out if it was a regression or not, I just fixed it instead.

Codecov Report

Merging #11675 into master will decrease coverage by 0.61%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11675      +/-   ##
==========================================
- Coverage   61.27%   60.65%   -0.62%
==========================================
  Files         593      627      +34
  Lines       32493    33879    +1386
  Branches     4594     4765     +171
==========================================
+ Hits        19910    20550     +640
- Misses      11581    12335     +754
+ Partials     1002      994       -8

Impacted Files
Coverage Δ

.../datascience/jupyter/interpreter/jupyterCommand.ts
9.48% <0.00%> (-45.69%)
:arrow_down:

src/client/datascience/jupyter/jupyterVariables.ts
25.00% <0.00%> (-25.58%)
:arrow_down:

src/client/datascience/jupyter/jupyterUtils.ts
57.14% <0.00%> (-20.36%)
:arrow_down:

src/client/common/net/httpClient.ts
72.50% <0.00%> (-18.13%)
:arrow_down:

src/client/common/errors/errorUtils.ts
50.00% <0.00%> (-16.67%)
:arrow_down:

src/client/common/process/types.ts
84.61% <0.00%> (-15.39%)
:arrow_down:

src/datascience-ui/react-common/arePathsSame.ts
75.00% <0.00%> (-12.50%)
:arrow_down:

src/client/common/utils/platform.ts
64.70% <0.00%> (-11.77%)
:arrow_down:

...t/datascience/jupyter/kernels/jupyterKernelSpec.ts
92.30% <0.00%> (-7.70%)
:arrow_down:

.../datascience/editor-integration/codeLensFactory.ts
52.56% <0.00%> (-6.21%)
:arrow_down:

... and 147 more

Continue to review full report at Codecov.

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


Not having this as the Main View

I want to Segue into this from my LoginRegisterViewController, but I think that requires me messing with the code that is in the AppDelegate.swift
When I removed the code in the AppDelegate.swift, the navigation bar was completely gone. I'm pretty new to iOS dev, and was wondering how I'd manage to extend this so that once the user logs in, I'll show the next view which is essentially this. I'm having a hard time creating a Navigation Bar without relying on the code in AppDelegate (which doesn't let me have an initial view being the LoginRegister view)

Actually, I just fixed this issue by removing all AppDelegate.swift code and creating my own Navigation Bar:
var navBar: UINavigationBar = UINavigationBar(frame: CGRectMake(0, 0, self.view.bounds.width, 64))

navBar.barTintColor = UIColor.blackColor()
navBar.translucent = false

then, at the end of viewDidLoad, I wrote:
navBar.addSubview(navbarView)
self.view.addSubview(navBar)

Of course, you need to take care to make navBar 64 points, and edit some things accordingly so that everything looks right. Also, at the very beginning, all the titles stack on top of one another until you begin scrolling, so you have to make sure to initialize all the titles (except the first one) with an alpha of 0.0.


[Regression] Flickering animations

Animations used to be smooth (two weeks ago), but now they aren't.

That's strange, I don't recall changing anything graphics-related (https://github.com/ozkriff/zemeroth/compare/b0ddd4d9d...master).

Oops.
You were right indeed.


Feature/op 17660

https://devopsmx.atlassian.net/browse/OP-17660
We prefer small, well tested pull requests.
Please refer to Contributing to Spinnaker.
When filling out a pull request, please consider the following:

Follow the commit message conventions found here.
Provide a descriptive summary for your changes.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Add inline code comments to changes that might not be obvious.
Squash your commits as you keep adding changes.
Add a comment to @spinnaker/reviewers for review if your issue has been outstanding for more than 3 days.

Note that we are unlikely to accept pull requests that add features without prior discussion. The best way to propose a feature is to open an issue first and discuss your ideas there before implementing them.

This PR  triggered this build in this execution, please wait for it  and child pipelines to succeed before merging:  https://isd.prod.opsmx.net/deck/#/applications/gcp-gitprtrigger/executions/details/01GD0Z0Z5JPNJ3AM14AXVNDV8P

This PR  triggered this build in this execution, please merge to master only if this succeeds:  https://isd.prod.opsmx.net/deck/#/applications/gcp-gitprtrigger/executions/details/01GD0Z1HES1DEE6M2DMENK77MY


3rd party types can't be constructed

Describe the bug
TLDR; There must be an automatic way to translate methods for 3rd party types used in a public API translated by frb.
Many struct-based types have only private members. They require a method being called to constcut them or a builder being created that will spit them out. When these options are not available on the Dart side, the type can't be constructed.
Specifically, I'm using PathBuf in my public API.
How do I conctruct a PathBuf on the Dart side?
It seems only stuff that is marked with #[frb(...)] gets translated. But PathBuf is part of a 3rd party crate (std) so I can't impl on it because of Rust's orphan rules.
I also don't want to create a wrapper struct MyPathBuf(PathBuf) because the amounf of boilerplate this approach entails (and the naming mess) for any 3rd party type is nuts. I.e. it would make using frb as labor-intensive, as the old way, via a manual FFI.
See also #310. But PathBuf is just one of a gazillion types I may want to use.
Steps to reproduce
None
Logs
none

Expected behavior
No response
Generated binding code
No response
OS
No response
Version of flutter_rust_bridge_codegen
No response
Flutter info
No response
Version of clang++
No response
Additional context
No response

On that note: it seems trait impls also do not get translated.
I have:
impl TryFrom<String> for FileInfo {
    type Error = anyhow::Error;

    #[frb(sync)]
    fn try_from(string: String) -> Result<Self> {
        let path_buf = PathBuf::from(string);
        Ok(Self {
            metadata: Metadata::try_from(path_buf.clone())?,
            path: path_buf,
        })
    }
}

But there is no tryFrom() generated to the Dart side. What am I missing?

How do I conctruct a PathBuf on the Dart side?

There are several ways (possibly I should add sth into doc):

Use https://cjycode.com/flutter_rust_bridge/guides/third-party/automatic/override-methods. i.e. #[ext] pub impl PathLib { fn new() -> ... }
For this specific one, https://cjycode.com/flutter_rust_bridge/guides/types/translatable/custom may be interesting, e.g. you may want String on dart side.

It would really be helpful to have a way to tell frb to reflect all methods of a type (or crate) to the Dart side.
The approach you suggested again means I have to write a ton of boilerplate. Look at the number of methods on e.g. BigDecimal (#2106). I don't want to type them all in rust/third-party/bigdecimal/mod.rs.
No difference if I go for wrapping those methods as you suggest in the Override Methods guide.
One of the reasons to use frb over the old approach with a hand-crafted FFI and PODs is the promise of easy-peasy type interchange between the languanges.
But as far as Rust goes this need to include easy-peasy exposition of methods because many types are opaque and if they're 3rd party types, this can't be changed.
So member access and construction is handled exclusively through methods. Exposing these methods on the Dart side with a single attribute or the like should be possible.

What do you think? I guess maybe we either can find out some way to solve things like that, or maybe we can provide an attribute like #[frb(unignore)] to force something to be scanned.

Why would the  #[frb(sync)] (or any frb attribute) on a trait method not be enough to tell frb to reflect that trait impl on the Dart side? Why would a new atrribute be needed?

It would really be helpful to have a way to tell frb to reflect all methods of a type (or crate) to the Dart side.
I don't want to type them all in rust/third-party/bigdecimal/mod.rs.
Exposing these methods on the Dart side with a single attribute or the like should be possible.

That's what https://cjycode.com/flutter_rust_bridge/guides/third-party aims to solve! We should not type them manually and it should be one-click.

The approach you suggested again means I have to write a ton of boilerplate. Look at the number of methods on e.g. BigDecimal (https://github.com/fzyzcjy/flutter_rust_bridge/issues/2106). I don't want to type them all in rust/third-party/bigdecimal/mod.rs.

No, I suggested the manual way because it is PathBuf. For example:

For PathBuf - I suggest just convert it to/from a String, since it seems when we have some paths in normal Dart code, we just use Strings.
For BigDecimal - looks like (a) auto translate whole crate (b) translating to https://pub.dev/packages/big_decimal just like translating PathBuf to String both looks good. I personally may prefer the latter, since I guess this needs to have a lot of things like operator += or some Dart-specific syntax sugar to maximize developer friendliness.
For other many crates (e.g. web-audio-rs which is an audio interface that can be used on native despite the name) - suggest use the "auto translate third party crate" feature (and it is in the frb CI as well).

Why would the  #[frb(sync)] (or any frb attribute) on a trait method not be enough to tell frb to reflect that trait impl on the Dart side? Why would a new atrribute be needed?

Nice suggestion! So the rule may be:

[ ] If there is #[frb] or #[frb(whatever)], we treat it as needed to be handled instead of ignored.


Fix URL to dask example

It seems that the continuum folks moved the bolg. They have a redirect at the old URL, but unfortunately it's broken. This appears to be the new url: https://www.anaconda.com/blog/developer-blog/xray-dask-out-core-labeled-arrays-python/

thanks!


fix abbreviations for languages have long weekday name

After updating to the latest version with multi-language support, I realized that the translations of weekday name for DE, IT, FR are too long. These new abbreviations allows library users to use multiple languages at the same time without applying different styles.
Thanks.

Can you merge this pull request as Localization is unusable the way it is right now.

Hi @moduval since I created the PR for the initial localization translation(which doesn't include proper abbreviations for some languages, my apologies), I would suggest to change the styles for languages like it and de while waiting for this PR to be merged. thanks

@fengshuo What do you mean by

change the styles for languages

Thanks


Macro for storage initialisation

Storage definition also verbose default initialization and storage slot assignment should be done automatically => “double definition” (once the struct, once the init method) also potentially error prone
From Philogy (and random discord messages too)

Closed via https://github.com/AztecProtocol/aztec-packages/pull/4200.


JSONAPISerializer Doc Needs to be updated

On page http://www.ember-cli-mirage.com/docs/v0.2.0-beta.9/serializers/ there is an example of using the JSONAPISerializer for the application serializer that reads:
import JSONAPISerializer from 'ember-cli-mirage';

export default JSONAPISerializer;

and should be:
import { JSONAPISerializer } from 'ember-cli-mirage';

export default JSONAPISerializer;

This was causing me to get the following error (in case others are experiencing it):
Pretender intercepted GET http://localhost:4000/api/v1/features but encountered an error: Cannot read property 'embed' of undefined

Good catch, thanks for opening the issue!
If you have time, could you click the "Improve this page" link at the top of that doc, editing the file + proposing a change?

Oh cool, I hadn't seen that link. I just sumbitted a PR. Thanks again for your work on Mirage. It's fantastic.

https://github.com/samselikoff/ember-cli-mirage/pull/751 closes


Upgrade (dev)dependencies to latest version

Upgrading cheerio avoids using the deprecated CSSselect (and CSSwhat)
packages in favor of css-select (and css-what). I thought I'd also
upgrade mocha while I was at it.

Thank you.
❯ np patch
 ✔ Prerequisite check
 ✔ Git
 ✔ Cleanup
 ✔ Installing dependencies
 ✔ Running tests
 ✔ Bumping version
 ✔ Publishing package
 ✔ Pushing tags

 lets-get-meta 2.1.1 published 🎉


Latest Docker images are arm64 only

The latest Docker images are only for the arm64 architecture. Shouldn't it be possible that the "latest" tag is available for all supported architectures, and not only arm?

Hmm it should be available for all architecture possibly it's been over written by one of slower arm builds

Ah I see the issue is from splitting the build out into seperate jobs causing them to overwrite each other

Ive fixed the logic in the docker workflow but I'm getting timeout again working on a fix

Thanks - hope you can get it to work properly - built-in arm support is much appreciated. 👍

The build takes nearly 30 minutes but given this only runs on main or tags I think that's alright

This looks much better - thanks!


ccui.TextField size is not correctly calculated in V3.2

I am trying to align the left of the TextField at the midle of the Scene. So I use the bellow formula to calculate the value for the textField.y.
textField.x = (cc.winSize.width + textField.width) / 2;
When there are EVENT_INSERT_TEXTor EVENT_DELETE_BACKWARD event fired on this textField, I  use the above formula to re-calculate the textField.y again. And I also print the textField.width to see the actual width change. I set the textField.placeHolder to "Please input your user name ...". So at the first EVENT_INSERT_TEXT event, it prints the textField.width = 290, but from the second input character, I sae the textField.width increase from 11. When I press the backward key, the textField.width decrease accordingly, I press the backward key until there is no input in the textField, it shows the textField.width = 11, but actually currently the textField shows the placeHolder string, and it looks like jumps to the left, looks very ugly.
I think the textField.width value is mis-calculated every time at the event, I believe that it holds the previous value.
Please take a look at this.

I didn't understand why did use width to calculate textField's y position.
Please try to use this:
textField.y = (cc.winSize.height+ textField.height) / 2;
Hopes to help
David

Hi dingpinglv,
Sorry, it should be the x property. Just now I fixed the problem by the following formula:
textField.x = (cc.winSzie.width + textField.getVirtualRendererSize().width) / 2;
Seems we shall not use the widht or height property of textField directly.

Hi @jeromeyan ,
ccui.TextFiled's height property is a function to return contentSize.height.
I'll test this issue your feedback.
Thanks,
David

This issue has been fixed at : https://github.com/cocos2d/cocos2d-html5/pull/2634
Cocos2d-x will fix it soon.
Thanks for feedback.
David


Typescript Fixes

Best setup:

Use VSCode
Install Deno-Extension
Install Deno

=> All errors are gone

And yes we need the .ts extensions in the files! This repo will be pushed with no change to deno.land/x/surrealdb

@minerj101 Thanks for the PR!
The only change that doesn't break anything is the tsconfig. But I am not a big fan of that much comments. So I think this will not get merged.
Could you close this PR?

@minerj101 @tobiemh can be closed


Cursor changes incorrectly when an interactive object is destroyed

Version

Phaser Version: 3.24.1

Operating system: Windows

Browser: Chrome

Description

When hovering the cursor over an interactive object with the useHandCursor option enabled, if another interactive object with  useHandCursor enabled is destroyed, the cursor changes back to an arrow.
Expected behavior is that the cursor will only change if there is no longer an interactive object with the useHandCursor option under the pointer.
Example Test Code

Paste this code into the Phaser 3 sandbox. After running, click one of the images.
var config = {
    type: Phaser.AUTO,
    width: 800,
    height: 600,
    parent: 'phaser-example',
    scene: {
        preload: preload,
        create: create
    }
};

var game = new Phaser.Game(config);

var image1, image2;

function preload ()
{
    this.load.image('logo', 'assets/sprites/phaser3-logo.png');
}

function create ()
{
    image1 = this.add.image(400, 300, 'logo')
              .setInteractive({ useHandCursor: true})
              .on('pointerdown', ()=> {
                  image2.destroy();
              })
    image2 = this.add.image(100, 100, 'logo')
              .setInteractive({ useHandCursor: true})
              .on('pointerdown', ()=> {
                  image1.destroy();
              })
}

Additional Information

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

Thank you for submitting this issue. We have fixed this and the fix has been pushed to the master branch. It will be part of the next release. If you get time to build and test it for yourself we would appreciate that.

Awesome. Just out of curiosity, will this also handle objects that are stacked? I.e. if the destroyed object is above a different one, will the cursor take into account the object which is interactive below the destroyed object?

 It won't update until you next move the mouse.

That was my guess. If I want to add this myself in my game, where should I start? Would I iterate through all children of the scene and somehow check the pointer position for collision with the hit area if they are interactive objects?

Nevermind on this, I figured out a solution. I just call the mouse move update function on the scene's input plugin to refresh the hover state:
this.sys.input.update(Phaser.Input.MOUSE_MOVE, [this.input.activePointer]);


Is there a way to make this work on PHP?

Not yet, I guess.

It works for me, in that you can run :CocCommand prettier.formatFile while editing a php buffer, and it will use Prettier to format the current file. But adding php to coc.preferences.formatOnSaveFiletypes in coc-settings.json is not working - my buffer is not formatted upon saving. I don't know why this is.
You can separately configure vim to run the current buffer through prettier using an autocmd:
autocmd BufWritePre *.php :CocCommand prettier.formatFile

my buffer is not formatted upon saving

@euoia try increase coc.preferences.willSaveHandlerTimeout in your coc-settings.json, the default timeout is 500ms that some formatter maybe failed to run in time.

I am getting this error [coc.nvim] php not supported by prettier when running :CocCommand prettier.formatFile

You have to use local prettier and make sure your prettier have support for php


use consul acl token

untested :sun_with_face:
fixes #49

it looks like this is included in #53... is that correct?

That was accidental!

included in #53


Updates for cmake changes

Make the github action build the runtime again after recent cmake changes.
Some notes:

This moves BUILD_AIR_PCIE definition to the toolchain file and makes it the default for x86.
Use the x86 toolchain file in the github builder
Make clang-12 the x86 default to match github builder
Don't hard-code LibXAIE_ROOT

None of the utility scripts are updated to properly build the runtime, but this is a start.

The builder logs now contain,
Compiling AIR runtime for x86
TOOLCHAIN=/home/runner/work/mlir-air/mlir-air/build_assert/../cmake/modules/toolchain_x86.cmake

and,
-- Found LibXAIE: /home/runner/work/mlir-air/mlir-air/aienginev2/install/include
Building PCIe runtime (BUILD_AIR_PCIE=ON)

So the following can be removed from the build-mlir-air-pcie.sh script?
    -DVitisSysroot="" \
    -DLibXAIE_DIR=${LibXAIE_DIR} \
    -DARM_TOOLCHAIN_OPT="" \
    -DBUILD_AIR_PCIE=ON \


fix: ignore .git folder when checking orphaned files

Fixes #168
See it in action: https://github.com/nextauthjs/next-auth/actions/runs/3861334319/jobs/6582249201

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


Warnings are not shown in console in runner mode

During the discovery we collect warnings to explain to the users if something is not good.
Warning can lead to a test session failure for instance for zero tests ran, but without the console output is hard to understand what's wrong.
Here looks like we send the warning to the logger inside the bridge but we don't send it to the display output https://github.com/microsoft/testfx/blob/main/src/Adapter/MSTest.TestAdapter/Discovery/UnitTestDiscoverer.cs#L73
cc: @Evangelink

This should be fixed on next insertion. I'll try to add an integration test when it gets inserted.

Closed by #2070


Avoid error while retrievening Open ID token

There's an error in console that's shows when registering and retrieving Open ID token.

PR: #2778

QA:

Make sure the kyma OAuth client is defined on the testing server
After logging in/registering there should not be an error displayed as a global message, nor an error in the console/network tab related to /token endpoint.

Tested on dev2. Works now. No . more token error.


Question: Where is the models such as wall, burger, obstacle, box of goal

Hi :)
I was about to add other goal box but I couldn't find the location.
There is no code related to models in the catkin_ws/src/turtlebot3_simulations/turtlebot3_gazebo/models/turtlebot3_burger
The source code not contains "goal" model not "goal_box".
<?xml version='1.0'?>
<sdf version='1.6'>
  <model name='goal_box'>
    <pose frame=''>0 0 0 0 -0 -1.5708</pose>
    <link name='goal_box'>
      <visual name='goal_box'>
        <pose frame=''>0 0 0.0005 0 -0 0</pose>
        <geometry>
          <box>
            <size>0.5 0.5 0.001</size>
          </box>
        </geometry>
        <material>
          <script>
            <uri>file://media/materials/scripts/gazebo.material</uri>
            <name>Gazebo/Grey</name>
          </script>
          <ambient>1 0 0 1</ambient>
        </material>
      </visual>
      <pose frame=''>0 0 0 0 -0 0</pose>
    </link>
    <static>1</static>
  </model>
</sdf>

In the respawnGoal.py,
self.modelPath = os.path.dirname(os.path.realpath(__file__))
        self.modelPath = \ self.modelPath.replace('turtlebot3_machine_learning/turtlebot3_dqn/src/turtlebot3_dqn',
                         'turtlebot3_simulations/turtlebot3_gazebo/models/turtlebot3_square/goal_box/model.sdf')

I have checked that which object is set. there were total 4 objects(burger, sqaure, goal, ground_plane). but I am not really sure where it is.

How could you set the model such as box of goal ?
Thank you

I have solved.
let me know how can I solve it.
Close.

I have solved.
let me know a person who are curious so that I share it.
Close.

Hello! I am facing the same issue, can you please share how you solved it ?

@hyunsooda hi!
Could you let me know how you solved it?

I cloned https://github.com/ROBOTIS-GIT/turtlebot3_simulations repo to catkin_ws/src. It has all required files


Test the promise being rejected due to an error

These are (roughly) the tests.
I was unable to do this because mocha flips out when the fetch method throws an error. If anyone knows a way to test this code path – let me know!

This is what's holding me back from 100% code coverage :expressionless:


CORE-31388 use XDM keys and values for event types

Description
Using the xdm spec for event type designations.  Key off of this for determining if the page is a viewStart or not.
Related Issue

CORE-31388
Motivation and Context
The event type was not being passed on and only used internally.  This data should be passed to Konductor so that it can be reported on.
Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] All tests pass and I've made any necessary test changes.
[x] I have run the Sandbox successfully.

@jonsnyder Since we decided to remove the type: viewStart property and replace it with isViewStart: true|false, we can close this PR now. I will create a ticket for Konductor to account for this new prop.
cc: @Aaronius

Sounds good.  We should probably add eventType: "web.webpagedetails.pageViews", to the payload for the events in the sandbox.


Several packages seem to be incompatible with the new react-native on platform Android

New Version
0.73.0-rc.1
Old Version
0.72.5
Build Target(s)
Android
Output of react-native info
System:
OS: Linux 6.1 Manjaro Linux
CPU: (16) x64 AMD Ryzen 7 5800H with Radeon Graphics
Memory: 5.39 GB / 13.51 GB
Shell:
version: 5.1.16
path: /bin/bash
Binaries:
Node:
version: 20.7.0
path: /tmp/yarn--1696745056791-0.4798124459808675/node
Yarn:
version: 1.22.19
path: /tmp/yarn--1696745056791-0.4798124459808675/yarn
npm:
version: 10.1.0
path: /usr/bin/npm
Watchman:
version: 2<IP_ADDRESS>
path: /usr/bin/watchman
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java:
version: javac 21
path: /usr/bin/javac
Ruby: Not Found
npmPackages:
"@react-native-community/cli": Not Found
react:
installed: 18.2.0
wanted: 18.2.0
react-native:
installed: 0.73.0-rc.1
wanted: 0.73.0-rc.1
npmGlobalPackages:
"react-native": Not Found
Android:
hermesEnabled: true
newArchEnabled: false
iOS:
hermesEnabled: Not found
newArchEnabled: Not found
Issue and Reproduction Steps
Steps to reproduce:

Create a fresh<EMAIL_ADDRESS>project
Install @react-native-async-storage/async-storage
Build application

Then, I can see the following error:
A problem occurred configuring project ':react-native-async-storage_async-storage'.
> defaultConfig contains custom BuildConfig fields, but the feature is disabled.
  To enable the feature, add the following to your module-level build.gradle:
  `android.buildFeatures.buildConfig true`

I had to patch<EMAIL_ADDRESS>and add the following code to eliminate this error:
android {
    // ...
    buildFeatures {
        buildConfig true
    }
    // ...
}

The same thing is happening to react-native-blob-util, @react-native-community/blur and some more packages.
Here are some real-world examples that showcase this error:

https://github.com/thu-info-community/thu-info-app/actions/runs/6445352956/job/17499307819
https://github.com/thu-info-community/thu-info-app/actions/runs/6445418469/job/17499448561

What is the proper way to solve this issue?
Thanks!

Repro: https://github.com/UNIDY2002/repro-rn-73-android


Check page sizes for each editor.

Confirm content sizing is accurate for different editors.  Confirm there are no blank pages and line count/line size is accurate:  No wrapping, etc.

Problems with printer prevented testing all of them.  Got word, wordpad, rtf, and pdf working good.  Edit plus sort of.  Notepad and notepad ++ not sure what is going on because they don't recognize the page break form feed.


Problems with e.g City:  in Quicksearch

If the the default city (fetched from www.geonames.org?) contains the nordic letter ö (o with dots) it is displayed (and searched) wrongly and no match is found in the database.
Besides this,  if trying empty out the city field this looks ok, but the search in the database still use the previous suggested city name.
But if one enter the SQL wildcard "%" the lookup works ok. But this is
farfetched for a non-developer.
Regards
Hakan

public static function getCity($sIpAddress = null)
    {
        try {
            // Encode to UTF8 for Latin and other characters of the GeoIP database are displayed correctly
            $sCity = utf8_encode(static::get($sIpAddress)->city->name); <==  Remove the encode here to get "Linköping" correct

            // TODO: When support PHP 7.1, specify multiple exceptions using "|" pipe
        } catch (AddressNotFoundException $oE) {
            $sCity = '';
        } catch (InvalidDatabaseException $oE) {
            $sCity = null;
        }

        return $sCity;
    }

Thanks for tying to debug that one. Encoding can be a big nightmare. Do you mind to open a Pull Request with your working fix?

Thanks, WIll do!

Thanks, WIll do!

Awesome. Can't wait to see it! 😊

Was fixed here: https://github.com/pH7Software/pH7-Social-Dating-CMS/pull/734


Write metricminer data to Google Sheets using GitHub Actions

Purpose/implementation Section
What changes are being implemented in this Pull Request?

.github/workflows/write-data.yaml: YAML file that triggers a GitHub Action every 2 minutes.
R/write-data.R: R script that grabs data from Google Analytics in a list format and writes the data to this publicly accessible Google Sheet.

What was your approach?
I followed these two blog posts:

https://rfortherestofus.com/2023/05/github-actions
https://www.simonpcouch.com/blog/2020-12-27-r-github-actions-commit/

However, I think that in order to authorize("google"), we will need to store the token somewhere and then point to the location of this token in the YAML.
Tell potential reviewers what kind of feedback you are soliciting.
This PR is not ready yet, so will be in draft mode.

I found it complicated to be running GHA within an R package, so created another repo solely for running GHA: https://github.com/fhdsl/metricminer-actions

Based on the strategy I've outlined above and toward the goal of making maintenance easier, let's not use the https://github.com/fhdsl/metricminer-actions repo. Is that okay? hopefully you've not done too much work on that yet.

I'm going to close this PR in favor of #52 And then I will be using that foundational work to return to this goal.


Textureless base mesh

Hi @galmetzer, is it ok for you to share all the base mesh that you've used in your work?

I believe most of them are from ModelNet40, according to the paper. I haven't located the exact ones used in the paper, but maybe would help.

Hi,
in the paper's acknowledgments you can find the credit list for all the meshes used throughout the paper


When I send a file single file use sample code, ,i got a page reload

When I send a file single file use sample code,i got a page reload,,
I want to stay on the current page what should I do?
thank you.

can you share you code?

onClick(e) {
const fileUpload = this.fileUpload.nativeElement;
fileUpload.onchange = (e) => {
for (let index = 0; index < fileUpload.files.length; index++)
{
const file = fileUpload.files[index];
this.files.push({ data: file, inProgress: false, progress: 0});
}
this.uploadFiles();
};
fileUpload.click();
}
private uploadFiles() {
this.fileUpload.nativeElement.value = '';
this.files.forEach(file => {
this.uploadFile(file);
});
}
uploadFile(file) {
const formData = new FormData();
formData.append('file', file.data);
formData.append('url', "http://localhost:4200/api/upload");
Upload.http({
url: 'http://localhost:4200/api/upload',
data: file
})
html:
<input type="file" #fileUpload id="fileUpload" name="fileUpload" multiple="multiple" accept="image/*" style="display:none;" />
result：
The file was uploaded, but the page was reload.
thank you！

thank you.


Aws xray daemon got shutdown signal after some time

Hello, We are running xray daemon as a side car for our fargate application. When there are no traces from application for some time , daemon logs an error message as 'Got shutdown signal: terminated' and daemon does not accept any new traces. Is someone else also facing the same issue?

@goyatajay How long is it ususally before the daemon is terminated? Is it consistent?

@srprash : this usually comes after 20 minutes , if no hits comes to daemon.

Can you provide your fargate application configuration and post the task definition?


[BUG] Migrate from Microsoft.WindowsAzure.Storage.Table to Azure.Data.Tables - deserialization issues

Library name and version
Azure.Data.Table 12.7.1
Describe the bug
I'm in the process of migrating code from Microsoft.WindowsAzure.Storage.Table to the Azure.Data.Tables. The issue described appears on querying entities with content that don't match the datatype. Consider the following snippet of migrated code:
public class WorkstationInfoTableEntity : Azure.Data.Tables.ITableEntity
{
    //ITableEntity
    public string PartitionKey { get; set; }
    public string RowKey { get; set; }
    public DateTimeOffset? Timestamp { get; set; }
    public ETag ETag { get; set; }

    //
    public byte[] Documents { get; set; }
    public DateTime? MyDocumentsLastRestoreDate { get; set; }
    public DateTime? MyDocumentsModifiedOn { get; set; }
    ....
    //
}

var table = tableServiceClient.GetTableClient(CloudTableNames.Workstations);
var workstations = table.Query<WorkstationInfoTableEntity>(c => c.PartitionKey == customerId);
var results = workstations.OrderBy(c => c.Name).ToArray();

If the table contains an entity that holds some string: "[RME]" (any non base64 string) in the Documents column then the Query will fail complaining that :
"System.FormatException: 'The input is not a valid Base-64 string as it contains a non-base 64 character, more than two padding characters, or an illegal character among the padding characters." because it expects a base64 string but the value is just some string.
Or if the MyDocumentsModifiedOn column contains some empty string inside then the query crashes with the error:
"System.FormatException: 'String was not recognized as a valid DateTime."
The Microsoft.WindowsAzure.Storage.Table library would have populated the property with a null value if a deserialization problem had occurred.
Expected behavior
Expected are a list of entities whose properties that failed being deserialized are set to null.
Actual behavior
The code crashes
Reproduction Steps
Details are in the bug description
Environment
No response

Thank you for your feedback.  Tagging and routing to the team member best able to assist.

Hi @VolvoTruckExpress - Are these invalid values expected in your dataset, or are they corrupt somehow? I'm just curious how the entities would get into this state in the first place. We'll look into a fix for this.
As a side note, it should be possible to grab these from the table using the TableEntity class, which is type agnostic.

If the data is intentionally now a byte array, would you need to convert these entities to the new values via Merge operations? If so, you may need to use the TableEntity as an interim step in either case. One option could be to wrap these areas of code with a try/catch and retry with the TableEntity to property convert them to the new entity shape.


Best way to redirect the homepage to another page

Issue Summary
Eventbrite is using Wagtail as a headless CMS. We're going to be creating page models for a number of different areas of the site, and retrieving data via the API. This means that we don't want the homepage /.
We'd like to intercept any attempt at accessing the default Wagtail homepage and redirect it to the main Eventbrite homepage. After some digging it appears that all of this is handled by the guts of Wagtail and we couldn't determine how to override this.
Is there any way for us to manage this on our own? Our fallback would be to do a redirect at our load balancer.

Hi @commadelimited,
You can accomplish this in several ways:

do the redirect at the server level (or load balancer)
Use the before_serve_page hook if you want this to happen for more than just the homepage.
Override the serve method for your homepage model - https://docs.wagtail.io/en/v2.4/reference/pages/model_recipes.html#overriding-the-serve-method

I would probably do this at the server level as you skip reaching the application and is scalable.

A more general note: #4276 is somewhat related to this in that there is currently no way to have Wagtail be purely headless because of wagtail_serve

You could also manage this with standard Django URL routing, e.g. with a RedirectView for / in your urls.py:
https://docs.djangoproject.com/en/2.1/ref/class-based-views/base/#redirectview

@zerolab the before_serve_page hook sounds perfect actually. We don't want to allow any public facing pages generated by Wagtail to be visible. We'll only be using the admin, and API drive pages in other areas around our site. Thanks!
@tomdyson that's good to know as well, thank you!

These are all great suggestions so I'm going to close this issue now. Thank you both for your time, and assistance.


[🚀] SBOM for packaged releases

:rocket: Feature request
Description
As your releases are not just tags but complete assembled/bundled packages,
it would be great to ship a software bill of materials with each individual release package.
This application may ship outdated and vulnerable components on purpose.
Having SBOM as part of the package would allow users to identify what they are hosting/using, so that they know the risks better.
Solution ideas
as this is already an OWASP project, I'd recommend using another OWASP project for generating the SBOM: OWASP CycloneDX.
Alter the build-processes and the release-processes for each OS/node-version

generate BOMs via all of these

server-side(node/NPM): https://www.npmjs.com/package/@cyclonedx/cyclonedx-npm
frontend(Angular/webpack): https://www.npmjs.com/package/@cyclonedx/webpack-plugin

have the generated BOMs added to the package

the files in the bom should be named bom-fromtend.cdx.json and bom-backend.cdx.json
to reflect https://cyclonedx.org/specification/overview/#recognized-file-patterns
Possible alternatives
 Have you considered any alternative solutions or workarounds?

I could pullrequest a solution, if you'd like.

CC @stevespringett @msymons

Sounds interesting.
When you say "have the generated BOMs added to the package" how does that work / to what would they be added?

if this was already implemented, then each of v15's release assets' packages would include a file bom-serverside.{json,xml} and bom-frontend.{json,xml} inside each of the juice-shop-*.{tgz,zip} files.
the individual BOMs would be generated during build processes for frontend(during ng build) and serverside(after npm install and before npm pack) for each build target individually, to reflect the actually used packages and components that are in the final package for each OS/nodeVersion combination, that is part of a release.

updated the feature request: added expected file names according to https://cyclonedx.org/specification/overview/#recognized-file-patterns

It is essentially an equivalent to a package.lock file but in a tech stack independent format, correct? I'm not sure who the target audience would be, though and what the use cases are for having these. I get it for "normal" applications, but Juice Shop simulates the worst possible security posture in a web app, so it definitely wouldn't come with a CDX manifest in that scenario. I'm concerned we'd be making it easier for security tools to analyze than it would normally be under the "we're terrible at security" premise.

but Juice Shop simulates the worst possible security posture in a web app

I totally understand.
If I gave people access to the in-house hosted juice-shop they would not get access to the source code; they would not have access to the content of the node_modules folder not a package.json not a BOM.
If they had access to a package.json and a node_modules folder, it was easy to gather the basic information a BOM would provide. So there is no downside here, I assume.
Target audience of that BOM would be

people who want to host a juice-shop: they need to know the risks and what they are actually  running. They need to know which attack surfaces to expect. Therefore, they need to know the components (packages/names/versions), so that these components can be aggregated and categorized by scanners like dependency-check, dependency-track and security-related tools.
people who want to reproduce the build or know build details: there is no lock file in the packaged releases. So it is hard to know which software was used to build/assemble the packages.

It is essentially an equivalent to a package.lock file but in a tech stack independent format, correct?

Yes, that is correct. But it can contain even more met data, like build time, assembly line descriptions, and so on.
If I wanted a juice-shop hosted for an in-house training or CTF, then mu secOps/devOps team would ask me for a BOM of the application, to know what security impact to expect. If I told them it was a web-app that was designed to be as vulnerable as possible, then they would not let me, unless they knew the risks and which layer of protection they needed to enclose the host-environment.
Having such a BOM would make it easy for my secOps/devOps team, to gather the needed information.

An alternative I see, if the general BOM was accepted, but it must not be in the package: have it as a separate release assets.
like the current *.md5 files, there could be files like juice-shop-15.0.0_node18_linux_x64-BOM_frontend.cdx.json

So there is no downside in providing a BOM, I assume.
Alright, let's try it out then.

will prepare a PR so we could see how it turns out and what it might look like.

proposed solution: #2031

got fixed via #2031
as of release v15.1.0
the individual SBOMs for backend and frontend bundled with every artifact. and with every docker image.
for backend it is bom.{json,xml} in the package root dir,
for frontend it is bom.{json,xml} in frontend/dist/bom/ dir.


✔ Minor Changes (Demo)

Description of Changes

changed MDLabel usage in demo

@HeaTTheatR I had tried to make my fork update with original kivymd. In this process many of the files had changed, sorry :pray: for taking your time (for telling issues in code). Also thanks for your advices.

@Kulothungan16 You just overwrote my pull request, which I already create all these fixes.

@Kulothungan16
Run git pull, make changes and make a new pull request

@Kulothungan16 You just overwritten all my changes


get_latest_model() for models

So returning a from sagemaker.model import Model object from the SageWorks Model() class would be a nice convenience function.

Okay, done.
sage_model = m.latest_model_object()


How to activate the password recovery thingy

what the title says

also how do i send a test message so ik that the email is working fine
im using a custom SMTP server

bump


Updating to adapt to changes from gofn-prosper

Coverage remained the same at 52.006% when pulling 79246826d4cbfd9c47619dea9cb14d5c3fd7eaf4 on client-ptr into 56ed0d37f28249c32f059081a9724c2403e006e1 on master.


Add support for ubernetes-lite

Requires a 1.2 upgrade. See https://github.com/kubernetes/kubernetes/blob/release-1.2/docs/proposals/federation-lite.md

Should be available in aws after https://github.com/Capgemini/kubeform/pull/64 https://github.com/Capgemini/kubeform/pull/77


Audio Reflection Realtime

Realtime audio reflections causing a high Audio DPS (CPU usage???) load on unity which causes audio quality to degrade significantly
Related issue for steam audio https://github.com/ValveSoftware/steam-audio/issues/140
Probably in scene design, look into making simple scene and working out bugs with baked reflection.

Somewhat handled by PR #83 by lowering the sound quality. Will have to look into future for resolving this issue.


debugging main process command

Hello! I am very new with electron-vue. I have npm run dev very simular with vue-cli boilerplate. But I can't find any command to start main process debugging in package.json
So my question is it a lack or I miss something?

There currently isn't any preset way to debug the main process in electron-vue. This is worth considering, but will be put on the back burner for the moment.

Maybe repacking npm pack:main and debugging app from dist folder as in electron "debugging main process" manual help us first time?

<EMAIL_ADDRESS>will be adding support for Node's Inspector Agent, making this process super simple with Chrome. There will be documentation about this usage; closing.
https://github.com/electron/electron/issues/6634

https://stackoverflow.com/questions/48091899/electron-main-and-renderer-process-debug-configuration/50787937#50787937


quickfix for: https://github.com/makotot/react-scrollspy/issues/112

renamed unsafe lifecycle componentWillReceiveProps to UNSAFE_componentWillReceiveProps

@apolopena Thank you!


iter_content returned size is far bigger than chunk_size

I expect iter_content to return me chunk_size number of bytes, but it never does. It returns me a far larger and random number of bytes. In contrast, urllib.request returns me exactly the number of bytes I request using its .read(chunk_size) method.
It is not acceptable for the returned chunk to use up to 5x more memory as evidenced below. Imagine this happening in say 64 threads at once. It should return exactly the number of bytes I asked for (or less at the end).
Expected Result
>>> import requests
>>> requests.__version__
'2.21.0'
>>> req = requests.get('http://docs.python-requests.org/en/latest/user/advanced/', stream=True)
>>> it = req.iter_content(8192)
>>> len(next(it))
8192
>>> len(next(it))
8192
>>> len(next(it))
8192

Actual Result
>>> import requests
>>> requests.__version__
'2.21.0'
>>> req = requests.get('http://docs.python-requests.org/en/latest/user/advanced/', stream=True)
>>> it = req.iter_content(8192)
>>> len(next(it))
3345
>>> len(next(it))
48672
>>> len(next(it))
47182

System Information
$ python -m requests.help

{
  "chardet": {
    "version": "3.0.4"
  },
  "cryptography": {
    "version": ""
  },
  "idna": {
    "version": "2.8"
  },
  "implementation": {
    "name": "CPython",
    "version": "3.7.2"
  },
  "platform": {
    "release": "4.18.0-15-generic",
    "system": "Linux"
  },
  "pyOpenSSL": {
    "openssl_version": "",
    "version": null
  },
  "requests": {
    "version": "2.21.0"
  },
  "system_ssl": {
    "version": "1010007f"
  },
  "urllib3": {
    "version": "1.24.1"
  },
  "using_pyopenssl": false
}

The docs mention that the returned item length may be different because of decoding, so I believe this is expected behavior.

The chunk size is the number of bytes it should read into memory. This is not necessarily the length of each item returned as decoding can take place.

(See docs for Response.iter_content)

It may be expected but it's wrong. urllib has no such problem. It works perfectly all the time and returns the bytes I .read(n).

this is expected behavior, if what you're saying is correct @rHuggler

Any update? I cannot use requests for a project until this issue is correctly resolved. Thanks.

Does the problem go away if you don't use compression?


Feature: Automatic tagging

What feature or improvement do you think would benefit Files?
Similar to both #12937 and #11992, I thought it might be interesting if Files automatically tagged files. For example, all .docx files are automatically tagged with the Work tag, and files in the user's Pictures library might be marked as Photos.
Requirements

This proposal will make it easier for the user to make full use of the tabs function
This proposal will better implement an existing feature, namely the tags.

Files Version
<IP_ADDRESS>
Windows Version
10.0.22631.4317
Comments
This might use a lot of processing power, perhaps it's best to add this as a setting in the Settings menu.

This would be done with #11992

That's not what I meant.
I meant that Files automatically, seamlessly, adds tags to all the user's folders and files on first install. #11992 is more like a poweruser tool that adds tags by regular expression, or so I gathered from it.

It could be set up so that if a file meets certain parameters it could automatically tag it

The description in #11992 covers scenarios like this. While we haven't yet decided whether to add this feature, if we do, including an option to enable presets for photos and other file formats is definitely worth considering.


ARROW-16809: [C++] Add Benchmarks for FilterNode

Add filter_benchmark.cc and add to arrow/compute/exec/CMakeLists

Hi @westonpace, this is a similar PR to #13314, just switched out the ProjectNode for a FilterNode.
I had some questions about the expression complexity and if we would want to adjust that for these benchmarks!

For a filtering operation I think there is an extra parameter which is the selectivity (what percentage of rows are kept). I think it would be valuable to add that as a parameter but it would make test data generation more complicated.

@westonpace one idea I had to benchmark selectivity is perhaps using the existing 'null_percent/proportion' generators we already have, and then using is_null as the filter. Let me know if you think that would be the right approach.

Sorry it took so long.  I wanted to be able to run on my dev machine so was waiting for that to finish moving (had to ship it).  Thanks for the cleanup, it's very promising that we can share so much between nodes.  I think you've captured a good set of interesting cases here.
I agree with your conclusions.  We also seem to continue to have peak performance in the 10k-100k rows-per-batch range.

Just a few minor nits.  This looks pretty good.

Hi @westonpace, was wondering if you could publish the changes you requested -- I don't think I can see them yet.

Hi @westonpace, was wondering if you could publish the changes you requested -- I don't think I can see them yet.

@iChauster Done, sorry :facepalm:

Excellent, if there's nothing else I think this is ready to go @westonpace!

How about this: https://github.com/apache/arrow/commit/f7109966366f389ba3bace571aa55571f70b2aec

moves the benchmark utilities for exec plans into a new benchmark_util that is in the compute/exec folder.  This change isn't strictly necessary but helps keep the code separated.
removes any dependency on googletest and instead changes the functions to return a status.  Then only the benchmark needs to depend on googletest (and can do ASSERT_OK in one spot).
changes the build slightly so that the benchmark_util.cc file is only built when building benchmarks so that this code doesn't get included with the libarrow.so (or libarrow_compute.so) files.

Locally, tests seem to pass on my fork.

@westonpace, that looks great, thanks for the help! I can run all the benchmarks on my system as well -- I think this is ready to go.

The build failure appears unrelated.  I will merge.  Thanks again.


Suggestion: Truncate address only when detect insufficient screen width

On each of the "Create a new account" pages (i.e. create username, save secret phrase, confirm secret phrase, and enter password screens) it shows the user's address "0x..." in full, but after signing up the "Accounts" page shows a truncated version of the same address even though there's sufficient space to show it in full in portrait view. Possibly consider only truncating the address when detect a screen size that isn't wide enough

The screen size will always be sufficient IMO because of the narrow electron window.
The reason why we truncated the address on the account overview is because users tend to try to select the address to copy it, which is not possible (because each account is a card).
Still we needed users to be able to see the full address at some point.. that's why it's fully visible in the account view, because they also can copy it.
Does that make sense to you?


Error message due to currency null

I got this message:
[2020-12-22 17:48:05.694 GMT] FATAL PipelineCallServlet| ....(removed data)... |akeQ_n_Lsb custom.Adyen [] Adyen: TypeError: Cannot call method "toString" of null in int_adyen_overlay/cartridge/scripts/util/adyenHelper.js:557
This is caused by this:
if (basket) {
     **paymentAmount = basket.getTotalGrossPrice() ? AdyenHelper.getCurrencyValueForApi(basket.getTotalGrossPrice()) : 1000;**
     currencyCode = basket.currencyCode;
   }

Sometimes you have basket but the basket.getTotalGrossPrice() (from Money Class) the money will exists, but will have N/A values and it generates error inside the getCurrencyValueForApi(Amount).
I think you check first if ' basket.getTotalGrossPrice().isAvailable() ' :
**paymentAmount = basket.getTotalGrossPrice() && basket.getTotalGrossPrice().**isAvailable ?** AdyenHelper.getCurrencyValueForApi(basket.getTotalGrossPrice()) : 1000;**
Many Thanks.

Hi @fabioGoncalves20,
Thank you for raising this issue. I will test it on my sandbox as well and will create an internal ticket to follow up on this.
Kind Regards,
Zaid
Adyen

The issue was addressed in this PR https://github.com/Adyen/adyen-salesforce-commerce-cloud/pull/442
Thanks,
Zaid
Adyen


Fuzzing in afl++ mode on android device

Hi!
Read the doc, but could not figure it out.
Have a binary with a function (that takes buffer and lenght) on Android device.
Can I fuzz it with fpicker?
Wanted to use afl++ mode on it.
I saw fuzzing on network device, but how to fuzz on an Android mobile?
Or I should somehow install ssh on the mobile?
Maybe I am missing something.
Thanks,

Actually, installing ssh server in emulator (via termux for example) does not seem to work. I hope I can use adb port forward, right?

In general fpicker should work on Android. I didn't try it yet, but I don't see why it wouldn't.
However, AFL++ mode will only work in local mode, which means fpicker, afl++, and the target need to run on the same system. Fpicker strictly requires shared memory when in AFL++ mode. So it wouldn't work over network or USB.
If your target is running on your Android device and you have both fpicker and AFL++ running on your Android device, you can fuzz it like shown in the readme:
afl-fuzz -i examples/test-network/in -o ./examples/test-network/out -- \\
    ./fpicker --fuzzer-mode afl -e attach -p target -f ./examples/test-network/harness.js

If you would want to fuzz it over USB or network, you could also use fpicker in standalone mode. However, I would then suggest to either use a custom mutator command or implement a better one, as the random mutator that's currently available is really just a proof of concept.
If you wanted to do it via USB it should work by running frida-server on the Android device and running fpicker with something like:
./fpicker --fuzzer-mode active -e attach -p target -D USB -o examples/test/out/ -i examples/test/in/  \\
    -f fuzzer-agent.js --communication-mode send

Important here are -D USB and --communication-mode send.
I hope that helps!

Actually it should work if you put he afl network proxy in between afl-fuzz and fpicker.
Check out util/afl_proxy in afl++

@vanhauser-thc Cool.
@ttdennis Any ideas how to add it? I can try ...
afl-proxy.c
/* here you have to create the magic that feeds the buf/len to the
       target and write the coverage to __afl_area_ptr */

    // ... the magic ...

Would be cool to be able to use fpicker with AFL++ on remote device.

I am just in the phone I think my pointer was wrong. Not afl_proxy but util/afl_network_proxy or something like that

Yes, in theory you should be able to use the afl_network_proxy (https://github.com/AFLplusplus/AFLplusplus/tree/stable/utils/afl_network_proxy) to use AFL mode over the network.
I didn't try it (because it's not really something I need right now) but you could possibly do it as follows:
On your target device run something like this:
afl-network-server -i 1111 -m 25M -t 1000 --  ./fpicker --fuzzer-mode afl -e attach \\
    -p test-service -f test-agent.js

And on the host:
afl-fuzz -i in -o out -t 2000+ -- afl-network-client TARGET-IP 1111

But then you still need to run fpicker on your target device/system. And if that's possible then you could just run AFL++/fpicker entirely on that device. The network proxy will probably cost you a ton of performance.

Thank you for your explanations.
I actually managed to compile Fpicker on Android.
Got stuck with compiling AFL++.
Anyway, Android uses ashmem instead of shared mem. Would this not be a blocker for AFL++ and Fpicker setup? In any form? Local and network
Found a library that can emulate shmem on Android via LD_PRELOAD
@vanhauser-thc are there any AOSP/Android binaries of AFL++ available? Compiling in chroot environment with clang11 (termux) and via AOSP failed for me.

Hmmmm
Tried with 2 different targets, including the ´test´ from example.
Looked good until crash :/ Any idea why Frida (Frida Server) gets access violation? What can I try? @ttdennis
In active mode it seems to work. (just fpicker and harness - fuzzer-agent.js)
On physical Android device. Running everything as root.
Terminal output:
[+] Loaded environment variable AFL_NO_AFFINITY with value 1
afl-fuzz++3.13a based on afl by Michal Zalewski and a large online community
[+] afl++ is maintained by Marc "van Hauser" Heuse, Heiko "hexcoder" Eißfeldt, Andrea Fioraldi and Dominik Maier
[+] afl++ is open source, get it at https://github.com/AFLplusplus/AFLplusplus
[+] NOTE: This is v3.x which changes defaults and behaviours - see README.md
[+] No -M/-S set, autoconfiguring for "-S default"
[*] Getting to work...
[+] Using exponential power schedule (FAST)
[+] Enabled testcache with 50 MB
[!] WARNING: LD_PRELOAD is set, are you sure that is what to you want to do instead of using AFL_PRELOAD?
[*] Checking core_pattern...
[*] Checking CPU scaling governor...
[+] You have 6 CPU cores and 1 runnable tasks (utilization: 17%).
[+] Try parallel jobs - see docs/parallel_fuzzing.md.
[*] Setting up output directories...
[+] Output directory exists but deemed OK to reuse.
[*] Deleting old session data...
[+] Output dir cleanup successful.
[!] WARNING: Not binding to a CPU core (AFL_NO_AFFINITY set).
[*] Scanning 'in'...
[+] Loaded a total of 1 seeds.
[*] Creating hard links for all input files...
[*] Validating target binary...
[*] Spinning up the fork server...
[+] All right - fork server is up.
[*] No auto-generated dictionary tokens to reuse.
[*] Attempting dry run with 'id:000000,time:0,orig:test'...

[-] Oops, the program crashed with one of the test cases provided. There are
    several possible explanations:

    - The test case causes known crashes under normal working conditions. If
      so, please remove it. The fuzzer should be seeded with interesting
      inputs - but not ones that cause an outright crash.

    - In QEMU persistent mode the selected address(es) for the loop are not
      properly cleaning up variables and memory. Try adding
      AFL_QEMU_PERSISTENT_GPR=1 or select better addresses in the binary.

    - Least likely, there is a horrible bug in the fuzzer. If other options
      fail, poke<EMAIL_ADDRESS>for troubleshooting tips.
[!] WARNING: Test case 'id:000000,time:0,orig:test' results in a crash, skipping
[+] All test cases processed.

[-] PROGRAM ABORT : We need at least one valid input seed that does not crash!
         Location : main(), src/afl-fuzz.c:1808

Logs:
05-09 18:24:27.933  9678  9678 I fpicker :        __       _      _
05-09 18:24:27.933  9678  9678 I fpicker :       / _|     (_)    | |
05-09 18:24:27.933  9678  9678 I fpicker :      | |_ _ __  _  ___| | _____ _ __
05-09 18:24:27.933  9678  9678 I fpicker :      |  _| '_ \| |/ __| |/ / _ \ '__|
05-09 18:24:27.933  9678  9678 I fpicker :      | | | |_) | | (__|   <  __/ |
05-09 18:24:27.933  9678  9678 I fpicker :      |_| | .__/|_|\___|_|\_\___|_|
05-09 18:24:27.933  9678  9678 I fpicker :          | |
05-09 18:24:27.933  9678  9678 I fpicker :          |_|        Frida-Based Fuzzing Suite
05-09 18:24:27.933  9678  9678 I fpicker : - - - - - - - - - - - - - - - - - - - - - - -
05-09 18:24:27.933  9678  9678 I fpicker :
05-09 18:24:27.933  9678  9678 I fpicker : Running fpicker using the following configuration:
05-09 18:24:27.933  9678  9678 I fpicker : - fuzzer-mode: 			FUZZER_MODE_AFL
05-09 18:24:27.933  9678  9678 I fpicker : - coverage_mode: 		COVERAGE_MODE_STALKER_SUMMARY
05-09 18:24:27.933  9678  9678 I fpicker : - standalone_mutator: 		STANDALONE_MUTATOR_NULL
05-09 18:24:27.933  9678  9678 I fpicker : - communication_mode: 		COMMUNICATION_MODE_SEND
05-09 18:24:27.933  9678  9678 I fpicker : - input_mode: 			INPUT_MODE_IN_PROCESS
05-09 18:24:27.933  9678  9678 I fpicker : - exec_mode: 			EXEC_MODE_ATTACH
05-09 18:24:27.933  9678  9678 I fpicker : - device_type: 			DEVICE_LOCAL
05-09 18:24:27.933  9678  9678 I fpicker : - process_name: 		test
05-09 18:24:27.933  9678  9678 I fpicker : - command: 			(null)
05-09 18:24:27.933  9678  9678 I fpicker : - fuzzer_timeout: 		1000000
05-09 18:24:27.933  9678  9678 I fpicker : - fuzzer_sleep: 		100
05-09 18:24:27.933  9678  9678 I fpicker : - agent_script: 		/data/local/tmp/fpicker/fuzzer-agent.js
05-09 18:24:27.933  9678  9678 I fpicker : - corpus_dir: 			(null)
05-09 18:24:27.933  9678  9678 I fpicker : - out_dir: 			(null)
05-09 18:24:27.933  9678  9678 I fpicker : - metrics: disabled
05-09 18:24:27.933  9678  9678 I fpicker :
05-09 18:24:27.933  9678  9678 I fpicker : [*] SHM_ENV_VAR = 9
05-09 18:24:27.935  9678  9678 I fpicker : [*] Found 2 Frida devices.
05-09 18:24:27.935  9678  9678 I fpicker : [*] Found desired Frida device: Local System(0)
05-09 18:24:27.935  9678  9678 I fpicker : [*] Trying to attach to process test
05-09 18:24:27.945  9678  9678 I fpicker : [*] Found process test with PID 9627
05-09 18:24:27.962     0     0 D [2:    logd.reader: 3422] logd: logdr: UID=0 GID=0 PID=9681 b tail=0 logMask=10 pid=0 start=0ns timeout=0ns
05-09 18:24:28.050  9678  9678 I fpicker : [*] Attached to process test on frida device Local System
05-09 18:24:28.056  9678  9678 I fpicker : [*] Agent script created
05-09 18:24:28.061  9678  9678 I fpicker : [*] Agent script loaded
05-09 18:24:29.062  9678  9678 I fpicker : [*] Slept a bit to give the agent script some time.
05-09 18:24:29.067  9678  9679 I fpicker : [*] MODULE=/data/local/tmp/fpicker/test, start=0x5555555000, end=0x5555558000
05-09 18:24:29.068  9678  9678 I fpicker : [*] Harness preparation done
05-09 18:24:29.069  9678  9678 I fpicker : [*] Everything ready, starting to fuzz!
05-09 18:24:29.085  9678  9678 I fpicker : [*] frida post: ["frida:rpc", 1, "call", "fuzz", ["MQo="]]
05-09 18:24:29.095  9678  9679 I fpicker : [->] error_send_message: {"type":"send","payload":["frida:rpc",1,"error","access violation accessing 0xa879","Error","Error: access violation accessing 0xa879\n    at fuzz (test-fuzzer.js:38)\n    at fuzzInternal (../../harness/fuzzer.js:273)\n    at fuzz (../../harness/fuzzer.js:103)\n    at apply (native)\n    at <anonymous> (frida/runtime/message-dispatcher.js:13)\n    at c (frida/runtime/message-dispatcher.js:23)",{"message":"access violation accessing 0xa879","type":"access-violation","address":"0x7d24392220","memory":{"operation":"read","address":"0xa879"},"context":{"pc":"0x7d24392220","sp":"0x7d171c63f0","x0":"0xa879","x1":"0xffffffffffffffff","x2":"0x55555557a8","x3":"0x3efffffff9","x4":"0x7d171c67b0","x5":"0x7d12333438","x6":"0xffffffffffffffff","x7":"0x7d1742b870","x8":"0x7d171c6520","x9":"0x7d24392174","x10":"0x7d171c6760","x11":"0x7d171c67a0","x12":"0xc7ade1b7e176e469","x13":"0x7","x14":"0x7d170781e0","x15":"0x80000000","x16":"0x55555557a8","x17":"0x7d1742b870","x18":"0x0","x19":"0x7d16f21000","
05-09 18:24:29.124     0     0 I [0:           init:    1] init: Untracked pid 9678 received signal 15

Weird is that it works in active mode (frida server, agent/harness), but not when in AFL++ mode :/

you can set AFL_DEBUG=1 and see if there is output of the target that crashes.
also you can try to generate the core file and see with gdb what makes it crash

@marcinguy Can you please share the full solution (or a PR)? I am interested in running this on Android as well.

@marcinguy Can you please share the full solution (or a PR)? I am interested in running this on Android as well.

Can you please share the full solution (or a PR)? I am interested in running this on Android as well.

Can you please share the full solution (or a PR)? I am interested in running this on Android as well.

Tested again fpicker AFL mode on Android 12 in the emulator in Docker and it works. I am not aware of other setups other than AFL++ + QEMU by @Gr33nh4t (to also have access to processes/services on device). Am I wrong here?
In the past used it to refind Stagefright bug CVE 2020-0411 within hours (several months after being 0 day)
I plan a private or public release. Stay tuned.

@ttdennis
Here are my notes:
https://github.com/marcinguy/fpicker-aflpp-android/
If you want I can put it somewhere in your project.
Thanks,

Awesome :) Sure, feel free to send a PR!


Upsert typo?

Is this a typo? upsert should be insert?
https://github.com/dynatrace-oss/dynatrace-monitoring-as-code/blob/389a293894d51515214afd7887687df1d6ead164/pkg/rest/config_upload.go#L32 and https://github.com/dynatrace-oss/dynatrace-monitoring-as-code/blob/389a293894d51515214afd7887687df1d6ead164/pkg/rest/config_upload.go#L78

Its in fact not a typo. This method checks internally, if the config already exists (by resolving it via the name). If it does not exist, it performs a POST against the API, otherwise a PUT.


Fixes for README - Incorrect yaml reference: projectFile

I know: being lazy by not forking/PR'ing to fix this by myself right now. :(
Change projectFile to project in the 2 occasions here: https://github.com/davidfowl/Micronetes#service-descriptions

Fixed


Rearchitect pass fitsfile

WIP, see #39

This change is

pros and cons of the new method
pros

the mutability of the fitsfile ensures non-concurrent access
the hdu methods that change the file can return a new hdu which is a
nice side effect. The old one cannot be used as it's moved into the
altering methods.

cons

the fitsfile is always mutable

this means when reading a file, and it does not seem like it needs to be
mutable. On the other hand this matches the stdlib e.g. File where
reading a file requires a mutable file

I need to see an entry in the changelog for this.