Xamarin.iOS build task fails due to comma ',' in certificate name.

As reported by users in Mobile Center when we use msbuild for the task it fails:
[command]/bin/rm -f _xcodetasktmp.plist
[command]/bin/cp -f /Users/ci/agent/vstsagent/_work/1/s/.certs/ios_cert.mobileprovision /Users/ci/Library/MobileDevice/Provisioning Profiles/355441d3-5dv4-46ce-819e-5c8z92e3a66a.mobileprovision
[command]/Library/Frameworks/Mono.framework/Versions/4/bin/msbuild /Users/ci/agent/vstsagent/_work/1/s/SadPirates.sln /p:Configuration=Beta /p:Platform=iPhone /p:BuildIpa=true /t:Rebuild /p:CodesignKeychain=/Users/ci/agent/vstsagent/_work/1/s/_xamariniostasktmp.keychain /p:Codesignkey=iPhone Distribution: The Sad Pirates, LLC (ZQ1PUR9RGF) /p:CodesignProvision=355441d3-5dv4-46ce-819e-5c8z92e3a66a
Microsoft (R) Build Engine version <IP_ADDRESS>
Copyright (C) Microsoft Corporation. All rights reserved.

MSBUILD : error MSB1006: Property is not valid.
Switch:  LLC (ZQ1PUR9RGF)

For switch syntax, type "MSBuild /help"
##[error]Xamarin.iOS task failed with error Error: /Library/Frameworks/Mono.framework/Versions/4/bin/msbuild failed with return code: 1. For guidance on setting up the build definition, see https://go.microsoft.com/fwlink/?LinkId=760847.

got same error with configuration of Release, but same repo with Ad-Hoc configuration build well

We have determined this happens when using "msbuild" option in the task inputs due to bug https://github.com/Microsoft/msbuild/issues/471. We are investigating a way to apply the workaround in the task.

@madhurig when will this fix be available on Mobile Center?

@jamesatgithub in Mobile Center we hotfixed that problem by rolling back to xbuild tool. Try to resave your branch configuration. The new VSTS task is planned to go live in a week or so.

@nevalenny thanks I can confirm the hotfix works!

This is still a problem with on-premise TFS update 2, when using msbuild it does not quote properly for the Codesignkey property. I added a comment to the original issue as well because it seems like spaces are treated as delimiters as well.

@ckrempp91: These changes didn't make it into TFS 2017, they are included in TFS 2018. You can try building the task and uploading to your TFS server using the  tfs-cli: https://github.com/Microsoft/tfs-cli
Thanks,
Madhuri


added nutrition page

Description
Added a nutrition page that gives information about food groups and diet plans
Related Issues
[Cite any related issue(s) this pull request addresses. If none, simply state “None”]

Closes #1481

Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)
https://github.com/user-attachments/assets/f968aa29-da16-4847-9753-a9b5b4501690
Checklist

[x] I have gone through the contributing guide
[x] I have updated my branch and synced it with project main branch before making this PR
[x] I have performed a self-review of my code
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
GSSoC'24

Please review my pull request @khushi-joshi-05

@samarsajad instead of navbar, put it somewhere else on the homepage

@samarsajad instead of navbar, put it somewhere else on the homepage

Should I create a pop up kind of button that links to the nutrition page? @khushi-joshi-05


Update C26400.md

@seshenoy : Thanks for your contribution! The author, @mikeblome, has been notified to review your proposed change.

@mikeblome This is a test PR... please ignore the same. I will close this shortly.

#hold-off

#please-close

#hold-off


Update the SharePoint Framework Examples

Category

[ ] Question
[X] Bug
[ ] Enhancement

As you know many of the examples are no longer able to be gulp serve because they have many errors in the log. They need to be updated so the group of individuals in the dev community may learn this technology. I am able to resolve some of these but not always.

+1.  I could not bundle the react-textboxio bundle.  Bunch of index.d.ts errors

This is a community driven initiative. You can be part of it :1st_place_medal: . If you update a web part for yourself, you can create pull request to that repo with the updated code to keep the repo up to date. :+1:

I rebuilt this webpart using a fresh yo @microsoft@sharepoint scaffold. I did so by following the "recipe" here which was a great resource.

@lbranjord  thanks again for bringing this to our attention.
I'll close this issue, as the samples and the SPFx scaffolding has changed significantly since you opened the issue, but if you feel that there is still more work to do, please feel free to open another issue.
We also welcome your contributions! #SharingIsCaring!


extensions: make naming and layout consistent accross all extensions

breaking change:

some extensions were exposing instance() instead of device()

includes:

renaming function pointer member to fns
moving name(), fp(), device()/instance() functions at end of file
adding missing device()/instance() functions
using result() instead of into()

I guess we want to get this in after #495?

I guess we want to get this in after #495?

The two PRs are independent AFAIK.

This PR also converts some of the .into() calls to .result(). Those should disappear as soon as #495 is merged, hence the suggestion to merge that one in first (and reduce the size of this diff a little).

This PR also converts some of the .into() calls to .result(). Those should disappear as soon as #495 is merged, hence the suggestion to merge that one in first (and reduce the size of this diff a little).

Ok. Makes sense.

Not seeing any red flags with this PR, looks good overall. Thanks for the hard work!

You're welcome.
Just pushed some commit log rewording.

There are two "extensions" I left untouched:

ext::PhysicalDeviceDrm
experimental::amd


feat: pass target_tabpage to ext.on_save

Allows extensions to determine if the session being saved is tab-scoped, and if so which tabpage the extension should save.
Preemptively takes care of the issue I mentioned here.

Thanks for the PR!


Investigate why sys/const.go GasTable is not currently used.

Seems to be commented out in contract.go:
https://github.com/perlin-network/wavelet/blob/65877aca9d15ebf52bc61224a04093f8b5e72cff/contract.go#L107-L115

GasTable will be re-used when we figure out the economics for smart contract fees.


Add path and stream to dimensions if they exists

In Docker environment path is not set-up but logs could be acquired from
STDOUT stream.
Change-Id: I755fa3d72bb81b61a4fa083fd974735bb13e4295

cla-recheck

CI will be failing because this plugin is not supporting Logstash >= 5.


New Feature: Minimum hardware requirements

Hi,
I am not sure how easy it is to compare these as it obviously depends on the amount of data. But perhaps it would be possible to give an indication per product how much the minimum CPU and RAM requirements are.
Cheers

Perhaps (in order to get a binary outcome (tick/cross) this could be listed as "Runs on a Raspberry Pi" assuming a Pi with some pre-defined specs (e.g. Pi 5 4Gb)? This might be a useful benchmark or "minimum standard". I.e. if something can run on a Rpi with, say 4Gb RAM, you'd expect it to be fine on something more powerful?
This is also commonly included in documentation of these packages, so shouldn't be too difficult to find.

I probably should have started by thanking you for this extremely useful resource :)
I understand where you're coming from, but that's why you can choose an arbitrary line in the sand. In fact, you already have three categories of "Yes", "No" and "Maybe", so we could use them?
Since this is your project, you can choose that you will give anything that "will run (as confirmed in their documentation) on a Rpi 4 with 4GB RAM and no additional dependencies" (or whatever specs you think are appropriate) a tick, those that don't a cross, and those that are unclear or have extra dependencies a "Maybe" (🚧). I completely agree that trying to set all these things up on an Rpi would be difficult and time consuming, so that's why I suggest just basing this on the docs.
I'm happy to assist via a PR if that's helpful. I realise it probably won't be perfect, but I also think that it would be helpful to users.
On that note, it may be worth updating the heading/readme to state that this project is a resource provided as best effort, and no guarantees are made to it's accuracy or completeness"? That way if you get any heat for something being incomplete or incorrect, you just point to that and say "sorry, I tried my best".


Added cancelled handler. Fixes #88

CancellationNotification is missing in python sdk. On timeout the server would fail and not restart due to validation issue.
Motivation and Context
https://github.com/modelcontextprotocol/python-sdk/issues/88
How Has This Been Tested?
Tested on stdio server https://github.com/rusiaaman/wcgw
Breaking Changes
No
Types of changes

[x] 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 change)
[ ] Documentation update

Checklist

[x] I have read the MCP Documentation
[x] My code follows the repository's style guidelines
[x] New and existing tests pass locally
[ ] I have added appropriate error handling
[ ] I have added or updated documentation as needed

Additional context
Unsure if changes require elsewhere.

I think https://github.com/modelcontextprotocol/python-sdk/pull/85 is a better fix.


WIP: Add some MADX common pitfalls in the FAQ

Bit of a scope increase:

Fixed admonitions with no title for new version of mkdocs-material
Removed deprecated steps in GA workflows
Updated pylhc/machine_settings_info.md to be consistent with latest version of the (was very old) and added usage examples
Added a bit to Mael's content about MAD-X B2 tracking caveats
Added content about LSA querying with machine_settings_info

Good that we're finally "starting" this page. Hopefully in the future we have a bit more of a habit to write a little something when these type of questions come up.


pie is not work in web ,But it is ok on mobile

this is on mobile

this is on web

I found this way in #95
flutter run -d chrome --dart-define=FLUTTER_WEB_USE_SKIA=true --release
it's work ,but...

all chinese garbled
so how can i fix this problem,if you konw something about this
tell me pls, thans a lot

+1

+1

Exactly same problem here

+1

Any update on this issue?

+1

Flutter has some problems with BlendMode on the web 1, 2,....
And FL Chart uses BlendMode.dstIn for clearing sectionsSpace, that's why you see a blank screen instead of a PieChart,
I decided to ignore PieChartData.sectionsSpace if you are running on the web.
BTW, I'm happy to say that you can run it on the web without --dart-define=FLUTTER_WEB_USE_SKIA=true, in the 0.9.4 version.
Thanks for letting me know, and for sure thank you for your patience!

Please try to run it and approve that it's working to close this issue.
Thanks!

Flutter has some problems with BlendMode on the web 1, 2,....
And FL Chart uses BlendMode.dstIn for clearing sectionsSpace, that's why you see a blank screen instead of a PieChart,
I decided to ignore PieChartData.sectionsSpace if you are running on the web.
BTW, I'm happy to say that you can run it on the web without --dart-define=FLUTTER_WEB_USE_SKIA=true, in the 0.9.4 version.
Thanks for letting me know, and for sure thank you for your patience!

Oh！I tried it in 0.9.4 version.
pie is work on the web！！！
Thanks for your hard work


Appearance controller system

Basically, decouple game logic from visuals like sprite or (in 3D) models.
Stuff like a battery component pushes data into an appearance controller which acts upon it. This can be any implementation, such as toggling sprite overlays, an FSM for 3D animations, ...

FSM FTW TBH.

This is kinda done. Appearance visualizers are in. Specific ones for preset FSMs are something we'll worry about later.


Can not have license ID

Can not have license ID
Exec Command :
syft packages sonatype/nexus3 -o cyclonedx-json

But can not have license id  :
      "licenses": [
        {
          "license": {
            "name": "http://www.apache.org/licenses/LICENSE-2.0.txt"
          }
        }
      ],

Good json：
      "licenses": [
        {
          "license": {
            "id": "Apache-2.0"
          }
        }
      ],

{
"$schema": "http://cyclonedx.org/schema/bom-1.4.schema.json",
"bomFormat": "CycloneDX",
"specVersion": "1.4",
"serialNumber": "urn:uuid:e1d1d486-6700-4643-8a40-ddd50cb1788a",
"version": 1,
"metadata": {
"timestamp": "2023-07-27T19:08:01+08:00",
"tools": [
{
"vendor": "anchore",
"name": "syft",
"version": "0.85.0"
}
],
"component": {
"bom-ref": "106ffa560fa7d498",
"type": "container",
"name": "sonatype/nexus3",
"version": "sha256:65878677e7195c74d34871eb7a2acfd5d9051890731675ca62f535e8e11dd404"
}
},
"components": [
{
"bom-ref": "pkg:maven/org.hdrhistogram/HdrHistogram@2.1.12?package-id=81b53904decf82ec",
"type": "library",
"group": "org.hdrhistogram",
"name": "HdrHistogram",
"version": "2.1.12",
"licenses": [
{
"license": {
"name": "http://creativecommons.org/publicdomain/zero/1.0/, https://opensource.org/licenses/BSD-2-Clause"
}
}
],
"cpe": "cpe:2.3:a:HdrHistogram:HdrHistogram:2.1.12:::::::",
"purl"<EMAIL_ADDRESS>"externalReferences": [
{
"url": "",
"hashes": [
{
"alg": "SHA-1",
"content": "6eb7552156e0d517ae80cc2247be1427c8d90452"
}
],
"type": "build-meta"
}
],
"properties": [
{
"name": "syft:package:foundBy",
"value": "java-cataloger"
},
{
"name": "syft:package:language",
"value": "java"
},
{
"name": "syft:package:metadataType",
"value": "JavaMetadata"
},
{
"name": "syft:package:type",
"value": "java-archive"
},
{
"name": "syft:cpe23",
"value": "cpe:2.3:a:hdrhistogram:HdrHistogram:2.1.12:::::::"
},
{
"name": "syft:location:0:layerID",
"value": "sha256:dfd807fb9360ed946984f55eec1c495463e647c0e486af4f2b8099311c8e56bb"
},
{
"name": "syft:location:0:path",
"value": "/opt/sonatype/nexus/system/org/hdrhistogram/HdrHistogram/2.1.12/HdrHistogram-2.1.12.jar"
},
{
"name": "syft:metadata:-:artifactID",
"value": "HdrHistogram"
},
{
"name": "syft:metadata:-:groupID",
"value": "org.hdrhistogram"
},
{
"name": "syft:metadata:virtualPath",
"value": "/opt/sonatype/nexus/system/org/hdrhistogram/HdrHistogram/2.1.12/HdrHistogram-2.1.12.jar"
}
]
},

Hi, I wanted to add a bit more context on this, hopefully providing some useful info.
We're also affected by this, as tools such as dependency-track rely on license id to keep track of license usages.
In java there are multiple ways to express a jar's license, so far I've been able to identify these cases:

Bundle-License: https://www.apache.org/licenses/LICENSE-2.0.txt in META-INF/MANIFEST.MF: usually this is an URL pointing to the license itself. This is the current method syft uses to retrieve the license and produces a license name entry in the generated bom. License ID could potentially be inferred from this url
Include-Resource: META-INF/LICENSE.txt=LICENSE.txt another attribute in META-INF/MANIFEST.MF, sometimes the license is described as an actual file, included in the archive and referenced as relative path. In this case License ID could be parsed from the textual license. Note that the Include-Resource and Bundle-License attributes could both be present in the MANIFEST file.
None of the above: I've found license files sitting in META-INF as-is, with no reference in the MANIFEST. Names might vary, so far I've found: LICENSE, LICENSE.txt and license.txt

Hope this helps.

Thanks @rogueai for the context - Is there a value dependency-track will accept if an SBOM tool is unable to determine the license ID?
For example https://www.foo.org/licenses/LICENSE-2.0.txt <-- If the URL is the reference, but we're running in an air gapped scenario and cannot derive it from the text of the URL what would you expect the field to include so that you are not getting an error?

Hi @spiffcs, thanks for looking at this!
Quoting dependency-track's readme it just says:

Supports standardized SPDX license ID’s and tracks

So I suppose DT only recognizes license references as SPDX ID, and specified as <id> (not <name>) in the bom as in this snippet:
<licenses>
  <license>
    <id>Apache-2.0</id>
  </license>
</licenses>

The tool has an internal list of all the possible license definitions, and uses their SPDX IDs to correlate components with.
Just a clarification: we're not getting any "hard errors", but all our components report "license violations" as DT cannot correlate, say, "name: https://www.apache.org/licenses/LICENSE-2.0.txt" to "id: Apache-2.0".
IMHO, in a more general view and ignoring dependency-track specifics, if a valid SPDX License ID cannot be retrieved, it's fine to just leave it in the <name> field, I think it should be a "best-effort" case to retrieve the id, while keeping the bom valid in the worst case scenario.

references #725


Disabling Workbench › Editor: Enable Preview From Quick Open has no effect

Does this issue occur when all extensions are disabled?: Yes/No
Yes

VS Code Version: 1.58.1
OS Version: MacOS Catalina 10.15.7 - Darwin x64 19.6.0

Steps to Reproduce:
https://user-images.githubusercontent.com/6603389/125759741-44db52f2-bca2-40eb-b88d-f5251551c6c0.mp4

I confirm this, v1.58.1

Also happens when using the right arrow, to open multiple files from Quick Open, they are opened in "preview" mode.

I can reproduce this in 1.58.1 but not in the insiders version. Please download insiders https://code.visualstudio.com/insiders/ and give it a try. If it works there it means the next release will include this fix if not please let me know.


Increase Responsiveness of the banner

Currently only the about section seems to be responsive, but the UI for the banner breaks on smaller screens.

I think this issue seems to be solved by the latest merge. Will close this issue then


[Doc] Add FluentMenuProvider notes

[Doc] Add FluentMenuProvider notes
Adding these notes

Important notes
With version 4.10 (and higher), we've introduced a new provider: FluentMenuProvider which corrects some menu
positioning problems. See #2510
By default, this provider is enabled. You must therefore add  to your application.
See Code Setup page of the documentation for more information.

Note must be added to WHATSNEW.md (in root folder) as well

Done


Integrating model hyperparameters

Integrating over model hyper-parameters needs to be implemented and offered as an option when hyper-priors are used in the models. This can provide fundamentally different (and many times better) results than optimizing the models as it is currently done.

#203 closes this issue


Some confusion about "self.pipeline.datamanager.train_image_dataloader.msg_status".

Hello, about the code, there are some parts that I don't understand and I hope to get your help. At line 60 of ros_trainer.py, "self.pipeline.datamanager.train_image_dataloader.msg_status", we know that msg_status is a method of the ROSDataloader class. The ROSDataManager class instantiates an instance of ROSDataloader as train_image_dataloader in its setup_train method to call msg_status, but I don't understand why the instance of ROSDataloader, train_image_dataloader, can be called by datamanager because there doesn't seem to be any connection between datamanager and train_image_dataloader.

I'm not sure that I understand the question. The dataloader is an object that is initialized by the datamanager to generate training samples.

Closing this due to inactivity.


Dynamic environment variables

Hi,
I'm trying to setup an etcd cluster managed by rancher on each rancher-os server. The problem is that etcd needs a variable (ETCD_NAME) to be different on each server.
Currently if I deploy etcd instances on each node using the option to run the service on every node in the cluster, I can setup only static environment variables.
How can I set for example:
environment:
  ETCD_NAME=$$hostname

@teodor-pripoae we are currently working on the feature that will enable support for that:
https://github.com/rancher/rancher/issues/1271
And here is more doc: https://github.com/sonchang/cattle/wiki/Rancher-Packaging-and-Catalog

Closing the ticket as we are going to keep track of the metadata feature in its own ticket mentioned above.


Add AdditionalUserDataFiles field

What this PR does / why we need it:
Add AdditionalUserDataFiles field to allow users to write arbitrary files to instances during cloud-init.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #57
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
Release note:

NONE

/hold

@detiber I updated the template logic. It took way too long to figure out how to omit empty lines when owner and permissions where empty! https://play.golang.org/p/AhjuCJrDC9u

This looks good
/approve
/assign @detiber
for lgtm

I need to squash before this merges, FYI

@ncdc the approve label should stick around after changes to the PR, it's the LGTM that goes away, right?

@chuckha correct

Then I'm not really sure why you mention you have to squash before you merge? Makes sense if I was leaving an /lgtm label on here, but this was the approve label so @detiber could /lgtm later after the squash.
Would you prefer a different workflow?

That was more an indication to Jason not to remove the hold until I had squashed

lgtm once squashed

Squashed

/lgtm
/hold cancel


No 'Mark Read' button in expanded motification

Hi!
I see only 'Quick Reply' and 'Open' buttons in notification. It would be helpful if one could just mark message read and dismiss the notification.
Not sure whether this issue is already created, sorry in case of any inconvenience caused.

In particular, 'Mark as Read' could easily replace 'Open', since we can already open the notification by tapping on the body.


Improved default config of the html serverconfiguration

Also added a line of documentation.

You need to squash and rephrase the commit according to https://www.conventionalcommits.org/


Minting Step 4/5: Bitcoin was sent and System is stuck (10 hours) sending proof to sidechain - Lost funds at this point

The sytem got stuck at Step 4/5 of Minting for more than 10 hours. As far as I'm concerned, I lost my Bitcoin and I did not get an TBTC token. That is a very serious problem, as no user would use it again if this happens in Production.
I don't know what needs to be improved/changed here, but it needs to be looked at, as this behavior is unacceptable in a production system.
Bitcoin Transaction - Bitcoin Lost so far:
https://sochain.com/tx/BTCTEST/b8835dbe2ef28ce37c1453526891869fced1356c46fccf3ecf2b2a5ae22f7de5
Minting Step where it is stuck (10 hours+)
https://dapp.test.tbtc.network/deposit/0xd018eddFfCd11b39015496afC0405977FE13567a/prove

Will did deeper with the URL. In the meantime, please attach logs when you get a chance. You should have a button in the footer that allows you to download them.

Attached is the log (file is inside the Word doc, I copied the content as well)
Minting Log.docx

It finally went through, took 3 days...
https://dapp.test.tbtc.network/deposit/0xd018eddFfCd11b39015496afC0405977FE13567a/congratulations


Support != filter expression in data viewer columns

Had a customer ask for this in a QP

Is it possibly <>?

Customer was trying to do != fwiw 🤷♀

Doesn't look like this is supported right now.

!= should be supported (at least for Python)

Closing this issue as there haven't been any upvotes on this feature request


Suggestion for maps

I had a possible suggestion for maps that could be helpful, especially for long long repetitive maps.
I have a big json with hundreds of keys that I want to map to a smaller json, mapping about a dozen variables. Currently, in its simplest form the map needs to be declared as followed :
map example {
  key1 = key1
  key2 = key2
  key3 = key3
  ...
  key100 = key100
}

It would be helpful if the simplest declaration we could make was:
map example {
  key1
  key2
  key3
  ...
  key100
}

The second form is more readable and easier to maintain. Each line translates to root.keyX = this.keyX

Hey @nikosgpet, the syntax looks neat but I'll need to think through whether the parser would introduce ambiguities. In the meantime you can probably tidy this up by using an array literal of your key names and using fold and merge to construct the object, it'd look like this:
map example {
  root = [
    "key1",
    "key2",
    "key3",
    "key100",
  ].fold({}, item -> item.tally.merge({
    item.value: this.get(item.value)
  }))
}

root = this.apply("example")

oh, that's neat, thanks!


Notification on removed file available?

Is it possible to detect / be notified in case a user deletes / renames a file which is still uploading?
In my implementation (JS Client)
xhr.send(this._source.slice(start, end)); is called in an endless loop with same start and end values after renaming or deleting the source file.

I apologize for my late reply, I lost this issue from radar.

Is it possible to detect / be notified in case a user deletes / renames a file which is still uploading?

Unfortunately, this is not possible since the tus protocol does have a mechanism for it. Normally, tus-js-client will begin a new upload if the previous one could not be resumed. Could you try this with the latest version of tus-js-client?

Closing this issue due to inactivity. Feel free to leave a comment if you want to continue the discussion :)


[Feature request] Add Bewithcment support

What I mean by that is to make it so when bewitchment is installed, the extractor can drop raw silver from bewitchment at a simular rate to gold

Added


UE 5.3 The following modules are missing or built with a different engine version. Engine modules cannot be compiled at runtime

Hi,
I get the following error while trying to add the plugin to my project in UE 5.3

The following modules are missing or built with a different engine version:
LightAwareness
Engine modules cannot be compiled at runtime. Please build through your IDE.

Steps to reproduce:
1.- Download LightAwarness 1.0.1 from Github
2.- Place LightAwareness Plugin under : Drive:\UE\Engine\Plugins\Marketplace\LightAwareness
3.- Activate the plugin in your project plugins
4.- Reopen the project
5.- Project says that LightAwarness was built for UE 5.4 accept
6.- This error appears saying that the module cannot be built

Hello, recommended version is 5.4 however you can use in 5.3
Please Re-Download the project from

https://github.com/cem-akkaya/LightAwareness/archive/refs/heads/master.zip
Place your project under plugins not in Engine -  Drive:\YOURPROJECT\Plugins\LightAwareness\
Rebuild your project from IDE - I feel that your project is blurprint only, if so you may have to convert it to a Source Code Project.
If you get errors regarding materials you have to download this and place them under your plugin folder.

Yep this fixed the issue, thanks!


Visiblity of @SimpleProperty getters and setters

Describe the bug
If the userVisible property of a setter type @SimpleProperty is set to false, it's corresponding getter will also be invisible in the components block panel. The same happens with a setter if it's getter is userVisible = false.
Affects

[ ] Designer
[ ] Blocks editor
[ ] Companion
[ ] Compiled apps
[ ] Buildserver
[ ] Debugging
[x] Other... (Components and extensions?)

Expected behavior
The visibility of a setter should not affect that of a getter and vice versa. Now, one might suggest simply not creating, for example, the setter block if it is to be kept invisible from the user, but that doesn't really help in case you need a @DesignerProperty. For a @DesignerProperty, a corresponding setter type @SimpleProperty is necessary.
Steps to reproduce

Create an extension with a pair of getter and setter @SimpleProperty. For example:
// Setter -- Should not be visible to the users
@SimpleProperty(userVisible = false)
public void Foo(int i) { /* ... */ }

// Getter -- Should be visible to the users
@SimpleProperty(userVisible = true)
public int Foo() { /* ... */ }

Import the extension in AI2. Neither the setter nor the getter for Foo will be visible in extension's block panel.

If only someone can confirm this is not an intended behavior but in fact a bug, I'd like to fix it.

https://groups.google.com/g/app-inventor-open-source-dev/c/vcg4a-EIeK0/m/dbSWG9arAgAJ


Discover dependent project package versions through asset manifests instead of package inspection

Today, we discover which package versions to insert into project's Versions.props files by inspecting all nupkg files in the project's artifacts folder (filtering to the newest version of each asset).
When we move to allowing dev builds, developers can end up in a state where they've done a development build and now all future builds (official or otherwise) only pick up dev builds as they're versioned <IP_ADDRESS>. Additionally, switching between dev branches could end up in a bad state selecting the wrong version of packages.
We already have a known-accurate manifest of all produced assets, the asset manifest. We can extract package versions from the manifest and use that information to update the Versions.props files. Additionally, we can use this same logic to solve https://github.com/dotnet/source-build/issues/4297 and a similar scenario in the arcade repo project.

Note that there are multiple variants of (build) asset manifests.
Repo manifests
We produce 1 to n repo manifests per inner-repo in a VMR vertical build. In most cases it's just 1 manifest but a few repos like sdk produce multiple ones.
Merged vertical manifest
This one gets produced at the end of the VMR vertical build
Final merged verticals manifest
This one is the manifest that gets uploaded to BAR and can only be created at a join point.
The ones that we should as an input for this are the repo manifests: https://github.com/dotnet/installer/blob/0bfd2dd757482b30745b799ee0a92cad3d8f5b50/src/SourceBuild/content/repo-projects/Directory.Build.props#L41


The DEnsemble model doesn't use the dvalid data.

There is no early_stopping_round parameter the config yaml file of double ensemble model. So according to the source code, each sub-model will only use dtrian data to train the sub-model for a specific number of epochs.  The data between "2015-01-01" and "2016-12-31" does not contribute to the model at all. Is it designed this way?

Here is a reference from the paper.
Here is the setting for LightGBM for baseline models, which DoubleEnsemble shares. The epoch is fixed.

Besides, we happened to discuss with the author and were told that the epoch is fixed.

Thank you so much for your response, I now understand that the epochs is fixed. And I noticed that only train dataset is uesed for retriving the loss curve and determining the weights. In order to prove it,  I randomly drop 50% of valid dataset. And the pred scores remain the same. Thanks again for your detailed answer！


back for #130

needs for #130

I think that it will be helpful to add feature to delete unknown question directly, i.e. without giving answer. It should help to filter some spam or duplicated questions
@l3r8yJ, what do you think?

@Andrew-Sem sure, create a ticket please


button rename

Now that the bSDD xslx is here (Yes!!) it may be a good idea to rename the 'Load Excel File' to something like 'xlsx to IDS xml'?

good idea! fix!


Fixed CI and added more tests

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a9d2324). Click here to learn what that means.
The diff coverage is 60%.

@@          Coverage Diff           @@
##             master    #2   +/-   ##
======================================
  Coverage          ?   80%
  Complexity        ?    21
======================================
  Files             ?     5
  Lines             ?    90
  Branches          ?     9
======================================
  Hits              ?    72
  Misses            ?    16
  Partials          ?     2

Impacted Files
Coverage Δ
Complexity Δ

...ava/sweetfactory/compiler/SweetFactoryProcessor.kt
81.48% <ø> (ø)
6 <0> (?)

...ava/sweetfactory/compiler/FactoryImplementation.kt
100% <ø> (ø)
3 <0> (?)

...n/java/sweetfactory/compiler/MessagerExtensions.kt
0% <0%> (ø)
0 <0> (?)

...ory/compiler/SweetFactoryDeclarationImplementer.kt
94.44% <100%> (ø)
9 <0> (?)

...factory/src/main/java/sweetfactory/SweetFactory.kt
75% <50%> (ø)
3 <1> (?)

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 a9d2324...13c722f. Read the comment docs.


get rid of vulnerable version of protobufjs

Fixes #18744

Oh @adamdmharvey sorry I hadn't seen that one! Mine does go one step farther though, pulling up gax too.


Are uint8[] arrays converted to strings?

It looks like so, I'm experiencing this issue:
a custom ROS msg has a field like
uint8[8]  intensities
and after
json_str = json_message_converter.convert_ros_message_to_json(data)
I see it is turned into a string (printing it with rospy.loginfo(json_str)).
Is it a bug or a feature?
Is it possible to force it to not consider it as a string?
Thank you.

I believe it is a feature, as described in issue #15
Problem is, my desidered behaviour is the one that was considered a bug.
My workaround is removing from line 260 of message_converter.py
the condition field_type.startswith('uint8[') or , so that line becomes just return field_type.startswith('char[')
I understand that this would reopen aforementioned issue #15 - maybe convert_ros_message_to_json function could take an optional parameter to request the desired behaviour?
Thanks.

You are correct, it's not a bug, it's the desired behavior in most cases. It's also in line with what rospy does: If you receive a message with a uint8[*] field, rospy will treat it as a str. But I understand that's not always the desired behavior.

maybe convert_ros_message_to_json function could take an optional parameter to request the desired behaviour?

I think I would be okay with such a parameter; let's call it binary_array_as_str or something. The default should be True to preserve the existing behavior. Unfortunately, since _is_ros_binary_type is nested so deep within the function calls, it means that flag has to passed down through all intermediate function calls until _is_ros_binary_type is finally called.
By the way, I first thought the opposite direction (convert_dictionary_to_ros_message) would also need some adjustments, but it turns out it can already handle lists of int. I've just added a test that verifies this:
https://github.com/uos/rospy_message_converter/blob/c980ac3080b32ff0e3c4294b248214103b5259cf/test/test_message_converter.py#L276-L286

the condition field_type.startswith('uint8[') or , so that line becomes just return field_type.startswith('char[')

Note that char is just an ancient, deprecated alias for uint8, so both should be handled the same. In other words, the whole _is_ros_binary_type check should be skipped. That way, it'll be handled by the _is_field_type_a_primitive_array case.
If you could provide these changes as a pull request (with accompanying tests, see test_ros_message_with_3uint8_array for a start), I'd be glad to review it.

Thank you.
I'll try to do this fix.
In the meantime I see you added some more tests, but I'm getting the following errors on a couple of them:
[Testcase: test_dictionary_with_3uint8_array_str] ... ERROR!
ERROR: a bytes-like object is required, not 'str'
  File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/usr/lib/python3.6/unittest/case.py", line 605, in run
    testMethod()
  File "test_message_converter.py", line 271, in test_dictionary_with_3uint8_array_str
    dictionary = {'data': standard_b64encode(expected_message.data)}
  File "/media/sf_ADAS/adas/3rdparty/ROS/venv/lib/python3.6/base64.py", line 95, in standard_b64encode
    return b64encode(s)
  File "/media/sf_ADAS/adas/3rdparty/ROS/venv/lib/python3.6/base64.py", line 58, in b64encode
    encoded = binascii.b2a_base64(s, newline=False)
--------------------------------------------------------------------------------

[Testcase: test_dictionary_with_uint8_array_str] ... ERROR!
ERROR: a bytes-like object is required, not 'str'
  File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/usr/lib/python3.6/unittest/case.py", line 605, in run
    testMethod()
  File "test_message_converter.py", line 250, in test_dictionary_with_uint8_array_str
    dictionary = {'data': standard_b64encode(expected_message.data)}
  File "/media/sf_ADAS/adas/3rdparty/ROS/venv/lib/python3.6/base64.py", line 95, in standard_b64encode
    return b64encode(s)
  File "/media/sf_ADAS/adas/3rdparty/ROS/venv/lib/python3.6/base64.py", line 58, in b64encode
    encoded = binascii.b2a_base64(s, newline=False)
--------------------------------------------------------------------------------

I just fixed that: #46

Thank you very much, but I'm sorry to say that I'm still gettin a (new) error:
[Testcase: test_dictionary_with_uint8_array_bytes_unencoded] ... FAILURE!
FAILURE: 'Invalid base64-encoded string: number of da[51 chars]of 4' != 'Incorrect padding'
- Invalid base64-encoded string: number of data characters (1) cannot be 1 more than a multiple of 4
+ Incorrect padding

  File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/usr/lib/python3.6/unittest/case.py", line 605, in run
    testMethod()
  File "test_message_converter.py", line 306, in test_dictionary_with_uint8_array_bytes_unencoded
    context.exception.args[0])
  File "/usr/lib/python3.6/unittest/case.py", line 829, in assertEqual
    assertion_func(first, second, msg=msg)
  File "/usr/lib/python3.6/unittest/case.py", line 1203, in assertMultiLineEqual
    self.fail(self._formatMessage(msg, standardMsg))
  File "/usr/lib/python3.6/unittest/case.py", line 670, in fail
    raise self.failureException(msg)
--------------------------------------------------------------------------------

Next week I'll try to find the time to do the fix I proposed.

Ok, I've fixed that too. I tested on python2.7 and 3.8, but I didn't expect that 3.6 behaves differently... oh well.

Thank you very much for the quick fix!
I've done the fix we discussed on a local branch: how can I submit it to you? I can't push the branch.
Thank you.

Please open a pull request.

I see that the test I added is passing only on noetic and failing on both kinetic and melodic, but I actually have melodic (with python 3.6) and the test was passing. As they say, "it works on my machine"...!

Let's move the discussion over to the Pull Request!


(Re)implement critical hits

[x] Crits increase damage
[x] Working crit mult stat
[x] Crits make dmg numbers a different color
[x] Perhaps color grade dmg numbers now?

* We should have somewhere in the game inform players that headshots exists, maybe in the tutorial and/or loadingscreen (maybe tip users that some barrels do not grant headshot crits)

Added a loading screen tip. No crit area on the dummies in training mode, so I plonked down some instrument bots to at least give the players something

The crit color is very similar in color to the cratertown background. Maybe do a gradient animation similar to the one on secret names in weapon select? (but maybe only use green and orange instead of the entire HSV rainbow lol)

Turned the text color green.

I think the crits need to have more feedback. They should probably have their own SFX (or at least a unique recognizable pitch), and we might also want to color the hitmarker in the crosshair red when critical damage is served

Crits now turn the crosshair green, and I made a pitch-shifted variant of the hit sounds for this. Ideally we'd also want different hit sounds for you vs other players, so we'll need to refurbish them at a later point -_-


Enhance/speak after single cancel

This is my suggestion for having speech after you cancel a timer from the GUI.  It even uses the name if available.

Wrong branch.  Want me to PR to https://github.com/emphasize/skill-ovos-timer/tree/fix/gui_timer_delete


Stopped comand in last state when low RAM

Bot not starting with state recovery after stopped by low memory

Hi!
This is the expected and correct reaction. If the strategy was "stopped" for various reasons, it cannot be restarted with the status restored. These ones don't make sense. In this case, check the log if it is necessary to adjust the settings and start again.
Regard's, Jerry.

Hi!
As an option, after the restart, inform about the 'stopped' state and request OK to continue the launch.

Fixed in v1.2.3


Arm32 support

I see that Jetpack Compose supports Linux arm64 and x64 but it doesn't seem to support Linux arm32. Is there a plan to support Linux arm32?
Sorry if that got mentioned somewhere, I couldn't find anything related to not supported ABIs.
Thank you.

arm32 support is not planned.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


New Luos engine repo organization

Comments for current PR

add your comments here
...

!!! WARNING : DO NOT EDIT THE CHECKLIST BELOW !!!
Checklist : Merge to DEVELOP branch
Code Quality

[x] Each function has a header (description, inputs, outputs)
[x] Code is commented (particularly in hard to understand areas)
[x] There are no new warnings that can be corrected
[x] Commits policy is respected (constitancy commits, clear commits comments)

Tests Review

[x]  Manual Tests for new features have been reviewed
[x]  Automatic Tests for new features have been reviewed

Tests are passed the best as I can

[x]  Non regression existing tests are passed OK
[x]  New tests for new features & bug fixes are passed OK

Documentation

[x] Documentation is up to date
[x] Changelog for next release is up-to-date : fill here
[x] If needed, tests are briefly described in test repository

Main is now the root branch of this repo. We don't merge this PR because of it.


FullScreen WindowState

What does the pull request do?
This adds the FullScreen WindowState.
What is the current behavior?
Currently, OSX has this notion of fullscreen windows, but our other platforms dont. Adding this window state means you can cover the same concept across all platforms.
What is the updated/expected behavior with this PR?
support fullscreen via window state property.
How was the solution implemented (if it's not obvious)?
win32 - I ported code from chromium... @kekekeks / @grokys
Reviewers:
OSX = @MarchingCube / @kekekeks
Win32 = @grokys @MarchingCube
Linux = @kekekeks @jmacato

@grokys @MarchingCube seems that window decorations being changed when inside fullscreen mode doesn't make sense. So I had to add a load of code to workaround that in win32, now on osx I'm doing the same workarounds.  Should this fix be moved into the window class, so we don't implement several times for each backend.
Basically if your in fs mode and decorations change, you need to not change the decorations, and keep a note until you come out of fs.
Seems like backend logic but right now osx and win32 could use the same fix, x11 might be same

@grokys @MarchingCube seems that window decorations being changed when inside fullscreen mode doesn't make sense. So I had to add a load of code to workaround that in win32, now on osx I'm doing the same workarounds. Should this fix be moved into the window class, so we don't implement several times for each backend.
Basically if your in fs mode and decorations change, you need to not change the decorations, and keep a note until you come out of fs.
Seems like backend logic but right now osx and win32 could use the same fix, x11 might be same

Putting this in backend logic.

OSX you cant change the WindowState for Borderless Windows... I would prefer to tackle this in a seperate PR...
https://github.com/AvaloniaUI/Avalonia/issues/3868

OSX you cant change the WindowState for Borderless Windows... I would prefer to tackle this in a seperate PR...
#3868

This actually now fixes that issue also.


UseDataClass: False positive with expected class

This class
expect class OAuthClientSettings() {
    val environment: Environment
    internal val authFlowFactory: CodeAuthFlowFactory
    internal val store: SettingsStore
}

triggers the following warning:
OAuthClientSettings.kt:9:14: The class OAuthClientSettings defines no functionality and only holds data. Consider converting it to a data class. [UseDataClass]

However, it is prohibited to create "expected" data classes:
Modifier 'expect' is incompatible with 'data'

Your Environment

Version of detekt used: 1.23.7
Version of Gradle used (if applicable): 8.10.1

Yeah that's a bug in the UseDataClass rule

Many thanks!


Hidden y-axis causes chart to shift to the right

Bug report
When there are multiple hidden y-axis in the chart, they each cause the first visible axis as well as the rest of the chart to be shifted to the right by minWidth + some padding
This happens even if the hidden axis have opposite: true which makes it especially confusing
With multiple charts in sync this a) makes it look  worse because they are not ligned up correctly and b) causes some issues with the sync i believe.
Screenshot

Codepen
https://codepen.io/vavido/pen/QWjMJWK
Explanation
Expected behaviour:
Hidden y-axis does not conribute to layout of the chart at all
What is happening instead:
Even hidden axis add padding on the left

While trying to reproduce the bug in the codepen, I found that it only appears when labels.minWidth is set on the hidden axis.
So as a workaround, I set it to undefined on my hidden axis for now.
However, I still think it's a bit confusing behaviour and should at least be documented somewhere.

I am still having the same issue. When I add an hidden y-axis, the whole chart is pushed to the right. Setting the hidden y-axis 'labels.show' to false and forcing an undefined or 0 for 'labels.min/maxWidth' does not resolve the issue for me. I've tried forcing every show to false and removing paddings etc but nothing seems to work. It is very annoying how lacking the documentation is about this.
I am using "vue3-apexcharts": "^1.6.0" and "apexcharts": "^3.52.0" in the Quasar framework.

I am still having the same issue. When I add an hidden y-axis, the whole chart is pushed to the right. Setting the hidden y-axis 'labels.show' to false and forcing an undefined or 0 for 'labels.min/maxWidth' does not resolve the issue for me. I've tried forcing every show to false and removing paddings etc but nothing seems to work. It is very annoying how lacking the documentation is about this.
I am using "vue3-apexcharts": "^1.6.0" and "apexcharts": "^3.52.0" in the Quasar framework.

I implemented it with react
I had the same issue
porbably you are defining everything for y axis like title, lables  even though you are hiding them.
atleast that's what I was doing
how I fixed is that just define the seriesName don't define anything else


React Generator

Think it would be a good idea to get React up in here, up in here.

@raksonibs Hey you don't have an issue queue on your repo generator-jekyllrb-react -- but I ran into an error and seems likely its related to this pull request.
Background
I'm fairly new to yeoman, so this could totally be PEBCAK or RTFM.
I tried to research a bit, found this #154 -- which seems similar.  However some manual fixes equivalent to this fix #155 solves.  So I'm at a loss, though I do recall a lodash depreciation when I installed something related to yeoman last night, I think: generator-jekyllrb
My Setup
All that said, I'm using ubuntu 15.10 with global installs set to my local user path per NPM Docs.  Except for some outdated generators, my setup seems to be functioning ok ... but it did take me awhile to figure out to install various dependencies ...  which might be related here ... or might be a simple lodash update that I'm unsure how to do.
Error
Note: I modified output path to include $HOME
events.js:154
      throw er; // Unhandled 'error' event
      ^

ReferenceError: yeoman is not defined
    at eval (eval at template ($HOME/.node/npm-global/lib/node_modules/generator-jekyllrb-react/node_modules/yeoman-generator/node_modules/lodash/dist/lodash.js:6306:22), <anonymous>:8:11)
    at underscore ($HOME/.node/npm-global/lib/node_modules/generator-jekyllrb-react/node_modules/yeoman-generator/lib/util/engines.js:23:45)
    at Generator.actions.engine ($HOME/.node/npm-global/lib/node_modules/generator-jekyllrb-react/node_modules/yeoman-generator/lib/actions/actions.js:216:32)
    at Generator.template ($HOME/.node/npm-global/lib/node_modules/generator-jekyllrb-react/node_modules/yeoman-generator/lib/actions/actions.js:191:19)
    at Generator.gruntfile ($HOME/.node/npm-global/lib/node_modules/generator-jekyllrb-react/app/index.js:370:8)
    at $HOME/.node/npm-global/lib/node_modules/generator-jekyllrb-react/node_modules/yeoman-generator/lib/base.js:409:16
    at processImmediate [as _immediateCallback] (timers.js:516:17)

Hey @mdrmike, I ended up pivoting this branch into another opensource repo: https://github.com/raksonibs/generator-jekyll-react-es6. Let me know if you have problems there and I can sort through them. I think the development will separate quite away from this great start by @robwierzbowski!


picard-tools: 2.23.3 -> 2.23.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/broadinstitute/picard/releases.
meta.description for picard-tools is: "Tools for high-throughput sequencing (HTS) data and formats such as SAM/BAM/CRAM and VCF"
meta.homepage for picard-tools is: "https://broadinstitute.github.io/picard/"
meta.changelog for picard-tools is: ""
Updates performed

Version update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

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

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

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

found 2.23.4 with grep in /nix/store/5snq3zhmdw87cp96pk6v3zczpdh7iy31-picard-tools-2.23.4

directory tree listing: https://gist.github.com/762e79f109e638b61d2505175b626690

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

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

4 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
1 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
picard-tools

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/5snq3zhmdw87cp96pk6v3zczpdh7iy31-picard-tools-2.23.4 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/5snq3zhmdw87cp96pk6v3zczpdh7iy31-picard-tools-2.23.4
ls -la /nix/store/5snq3zhmdw87cp96pk6v3zczpdh7iy31-picard-tools-2.23.4/bin

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

1 package built:

picard-tools

Maintainer pings
cc @jbedo for testing.

LGTM.


ASN.1 Encoding

This package provides amazing Decoding support, but I'm struggling to find how to perform Encoding.
My use case is some CryptoKit.Curve25519.PublicKey data which I want to be encoded as DER, which unfortunately Apple's native API's can't do either (ref and ref).
Wouldn't it be quite straightforward to add toDER functions to all types to support this? I don't want to write all tags in my end-user codebase, but rather reuse the ones from a library such as this one.

Working a bit on it in https://github.com/DominikHorn/ASN1Parser/compare/main...hermanbanken:ASN1Parser:main.
Maybe this also is what #1 author is trying to do (hence exposing the swiftValue), or maybe it is just the usage of the digit, not sure. But I also exposed it at first before moving the Encoder inside the fork (had an extension in my own codebase at first).


Nginx Container Loads Content over HTTP not HTTPS

Your docker-letsencrypt-nginx-proxy-companion works perfect with apache containers.
https://hub.docker.com/_/wordpress/
https://hub.docker.com/r/_/owncloud/
But I have problems to get a working nginx container like:
https://hub.docker.com/r/tlongren/docker-wordpress-nginx-ssh/
https://hub.docker.com/r/oskarhane/docker-wordpress-nginx-ssh/
I Already tried ~ 5-10 other nginx wordpress containers and also build my own container
with diffrent "etc/nginx/nginx.conf" and "/etc/nginx/sites-available/default" files with no luck.
A HTTPS force always trunsaltes in an 502 Error, so that also does not help.
Here is an example how a new nginx container is looking like:
https://freeunitygames.org
Thank you for your efforts :)

Hi,
sorry but it's not the right place to speak about nginx configuration.
My container only create letsencrypt certificates.
I didin't know about to help you about your nginx problem.
Try to report issues to author of docker-wordpress-nginx-ssh.


Add docs: how to access K8s cluster and troubleshooting

Is this strictly intended for internal use, or any info that customers/community might find useful?

This is specific to our usage

yep, just for internal usage

@cpanato Is this still a WIP? Or ready for PM review?

Just a couple of questions, will continue review after :)

@jasonblais thanks, i also need to update some parts to fix some issues in who to connect


Userspace symbol resolving via addr2line

This change implements additional symbol resolving for stack traces, which
improve the support for userspace stack traces.
A challenge with the stack traces obtained via ebpf is that they just contain
a raw address inside the virtual memory space of the process, which
requires some extra steps to be translated into a function name. This change
provides most of the infrastructure to provide the translation via a DefaultResolver
type which can resolve both kernelspace and userspace functions based on
a PID and address. In addition in adds a SymbolResolver trait that allows to customize
resolving behavior and extend it further.
I originally looked into just using the StackTrace::resolve
function. However I noticed that the information that is at the moment stored
in the StackTrace struct is not sufficient for resolving, e.g. due to missing the PID
and being unable to account for the virtual -> physical memory address translation.
Therefore this change uses a new resolver infrastructure.
Usage via a suitable EBPF program that sends stack traces and process IDs:

/// The BPF program populates this Queue with the process ID, kernel-space and user-space
/// stack trace IDs.
/// The former can be obtained via `bpf_get_current_pid_tgid()`, the stack
/// traces via `aya_bpf::maps::StackTrace`.
let mut stacks = Queue::<_, [u64; 3]>::try_from(bpf.map_mut("STACKS")?)?;
let stack_traces = StackTraceMap::try_from(bpf.map_mut("STACK_TRACES")?)?;
let resolver = DefaultResolver::new().unwrap();

loop {
    match stacks.pop(0) {
        Ok([pid_tgid, ktrace_id, utrace_id]) => {
            let tgid = pid_tgid & 0xFFFFFFFF;

            if let Ok(trace) = stack_traces.get(&(ktrace_id as u32), 0) {
                for f in trace.frames() {
                    let mut symbol = SymbolInfo::unresolved_kernel(f.ip);
                    resolver.resolve(&mut symbol);
                    println!("Resolved kernel address: 0x{:x} to {:?}", f.ip, symbol);
                }
            }

            if let Ok(trace) = stack_traces.get(&(utrace_id as u32), 0) {
                for f in trace.frames() {
                    let mut symbol = SymbolInfo::unresolved_user(tgid as _, f.ip);
                    resolver.resolve(&mut symbol);
                    info!("Resolved pid {}, address: 0x{:x} to {:?}", tgid, f.ip, symbol);
                }
            }
        }
    }
}

BPF code:
static STACK_TRACES: StackTrace = StackTrace::with_max_entries(10, 0);

static STACKS: Queue<[u64; 3]> = Queue::with_max_entries(1024, 0);

pub fn testprobe(ctx: ProbeContext) -> u32 {
    unsafe {
        let pid_tgid = bpf_get_current_pid_tgid();
        let ustack = STACK_TRACES.get_stackid(&ctx, BPF_F_USER_STACK as _);
        let kstack = STACK_TRACES.get_stackid(&ctx, 0);

        match (kstack, ustack) {
            (Ok(kstack), Ok(ustack)) => {
                if let Err(e) = STACKS.push(&[pid_tgid, kstack as _, ustack as _], 0) {
                    info!(&ctx, "Error pushing stack: {}", e);
                }
            },
            _ => {}
        }

        0
    }
}

Output when fetching stack traces of a kprobe on sendmmsg on a test program:
Resolved kernel address: 0xffffffff81a62691 to SymbolInfo { virtual_address:<PHONE_NUMBER>1589734033, object_address: Some(18446744071589734033), process_id: None, function_name: Some("__sys_sendmmsg"), object_path: None }
Resolved kernel address: 0xffffffff81a62870 to SymbolInfo { virtual_address:<PHONE_NUMBER>1589734512, object_address: Some(18446744071589734512), process_id: None, function_name: Some("__x64_sys_sendmmsg"), object_path: None }
Resolved kernel address: 0xffffffff81da30a3 to SymbolInfo { virtual_address:<PHONE_NUMBER>1593144483, object_address: Some(18446744071593144483), process_id: None, function_name: Some("do_syscall_64"), object_path: None }
Resolved kernel address: 0xffffffff81e0007c to SymbolInfo { virtual_address:<PHONE_NUMBER>1593525372, object_address: Some(18446744071593525372), process_id: None, function_name: Some("entry_SYSCALL_64_after_hwframe"), object_path: None }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x7fccf3b2adee to SymbolInfo { virtual_address:<PHONE_NUMBER>29358, object_address: Some(1195502), process_id: Some(22158), function_name: None, object_path: Some("/usr/lib/x86_64-linux-gnu/libc-2.31.so") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570cd66cc to SymbolInfo { virtual_address:<PHONE_NUMBER>1548, object_address: Some(947916), process_id: Some(22158), function_name: Some("tokio::io::async_fd::AsyncFdReadyGuard<Inner>::try_io"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570cd43e6 to SymbolInfo { virtual_address:<PHONE_NUMBER>2614, object_address: Some(938982), process_id: Some(22158), function_name: Some("quinn_udp::imp::UdpSocket::poll_send"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570ccd31f to SymbolInfo { virtual_address:<PHONE_NUMBER>3743, object_address: Some(910111), process_id: Some(22158), function_name: Some("<quinn::endpoint::EndpointDriver as core::future::future::Future>::poll"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570cc2400 to SymbolInfo { virtual_address:<PHONE_NUMBER>8912, object_address: Some(865280), process_id: Some(22158), function_name: Some("<core::future::from_generator::GenFuture<T> as core::future::future::Future>::poll"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570cd0e8d to SymbolInfo { virtual_address:<PHONE_NUMBER>8957, object_address: Some(925325), process_id: Some(22158), function_name: Some("tokio::runtime::task::harness::poll_future"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570cd160a to SymbolInfo { virtual_address:<PHONE_NUMBER>0874, object_address: Some(927242), process_id: Some(22158), function_name: Some("tokio::runtime::task::harness::Harness<T,S>::poll"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570c6ef25 to SymbolInfo { virtual_address:<PHONE_NUMBER>7701, object_address: Some(524069), process_id: Some(22158), function_name: Some("std::thread::local::LocalKey<T>::with"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570c7e505 to SymbolInfo { virtual_address:<PHONE_NUMBER>0645, object_address: Some(587013), process_id: Some(22158), function_name: Some("tokio::runtime::basic_scheduler::Context::run_task"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570c7b2fa to SymbolInfo { virtual_address:<PHONE_NUMBER>7834, object_address: Some(574202), process_id: Some(22158), function_name: Some("tokio::macros::scoped_tls::ScopedKey<T>::set"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570c7de7c to SymbolInfo { virtual_address:<PHONE_NUMBER>8972, object_address: Some(585340), process_id: Some(22158), function_name: Some("tokio::runtime::basic_scheduler::BasicScheduler::block_on"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570c75a3d to SymbolInfo { virtual_address:<PHONE_NUMBER>5117, object_address: Some(551485), process_id: Some(22158), function_name: Some("tokio::runtime::Runtime::block_on"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570c5c597 to SymbolInfo { virtual_address:<PHONE_NUMBER>1527, object_address: Some(447895), process_id: Some(22158), function_name: Some("std::sys_common::backtrace::__rust_begin_short_backtrace"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570c59d44 to SymbolInfo { virtual_address:<PHONE_NUMBER>1204, object_address: Some(437572), process_id: Some(22158), function_name: Some("core::ops::function::FnOnce::call_once{{vtable.shim}}"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }
02:46:16 [INFO] ayatest: [ayatest/src/main.rs:98] Resolved pid 22158, address: 0x564570ecc763 to SymbolInfo { virtual_address:<PHONE_NUMBER>7891, object_address: Some(3004259), process_id: Some(22158), function_name: Some("std::sys::unix::thread::Thread::new::thread_start"), object_path: Some("/mnt/c/Users/matth/Code/rust/quinn/target/release/bulk") }

@dave-tucker I noticed this has some overlap with #329 - at least both changes implement parsing of /proc/[pid]/maps - which can probably be in a single place. Maybe also with symbol resolving, since I think a part of that is also implemented in #329, but in a more low level fashion than here (this PR just asks addr2line instead of going more low level). I really just wanted to get some basic stack traces working, and used the tools that seemed to require the least effort for this. I don't have a ton of experience with ELF files and no strong opinion on how it should look like :-)

Ping. I just rebased this on top of main. I will also add a few comments on my thoughts

@mstange @kakkoyun you've built profilers with aya, tagging you in case you have any inputs

Thanks for tagging me, I have a lot of opinions on this topic! :)
Symbol resolution can be quite a big topic, depending on how deep you want to go. I'm not sure if aya is the right place to offer a full symbol resolution API and choose which trade-offs to make; I'm thinking it might be better to offer just enough information so that absolute addresses can be mapped to relative address (along with the file path of the library), so that the user can call into a different crate to do the actual symbol resolution. I was already pondering whether I should make such a crate; I think this PR has convinced me that it would be worth doing.
The following design questions come to mind:

When do you read proc maps? Whenever symbols are requested, or do you maintain a cached representation? Do you handle libraries being loaded and unloaded during program observation? Perf does the following: It reads proc maps once at the start of recording, and then sets perf_event_attr.mmap2 = true so that it receives PERF_RECORD_MMAP2 records for any newly loaded libraries. Then it can map absolute addresses to the right library at any point during recording.
Which type of "relative address" do you store? When you map an absolute address to a relative address, there are two types of relative addresses you might choose: file offsets or "stated virtual memory addresses" (SVMAs). The former is easy to compute from the proc maps info, but the latter is what addr2line wants. This is a source of bugs because, for many libraries, the two end up being the same, so you don't notice the discrepancy until you run into a library in which the two are different. For example, libxul.so (from Firefox) is one where the two are different; libxul.so contains an ELF LOAD command whose file offset and the virtual memory address are different. Perf stores relative addresses as file offsets (it calls them "rip", i.e. "relative instruction pointer") and then resolves those to SVMAs (which it calls "objdump addresses") only whenever it calls out to addr2line / objdump. Samply stores SVMAs; it has to look at the library's section information before it can compute any relative addresses.
Where do you look for symbol information? Only in the actual loaded binary, or do you search other places as well? Do you support split dwarf? Do you use debuginfod to pull additional debug files from the web?
How do you handle libraries which have incomplete symbol information? You may want to generate placeholder symbols based on function start addresses from unwind information. If you don't do this, you may end up with many misleading function names for unrelated addresses.
Do you handle proc mountinfo information? I think this is needed when observing ubuntu snap builds such as the snap Firefox build. Those load many libraries from the snap file system, so you can't just trust the paths in the proc maps.

Personally, I think I'd like it aya to maintain a process mapping over time (one for each process), and have it tell me when libraries are loaded and unloaded, and when processes appear and disappear.
I'll close with one piece of advice: Watch out when resolving symbols for return addresses, i.e. any non-topmost address in a call stack. If you get file+line information from addr2line, or if you get inlines, you need to make sure that the "lookup address" is shifted into the "call" instruction. By default, addresses in stacks are usually "return addresses", i.e. the address of the instruction which will be executed after the call returns. The common remedy is to just subtract one byte from all return addresses, i.e. ask addr2line to resolve return_address - 1. If you don't do this, you can end up with wrong line numbers and wrong inline stacks.
Oh, also, please don't discard inline stack data. Yes, the callee-most function of an inline stack on its own is usually not very useful, but the outer function on its own is often not very useful either. For best results you really want to keep the entire inline stack for each address.

Thanks for tagging me as well. I'm still catching up with my review requests. I'll have an in-depth look at this.

As far as the #329 is concerned, the only similarity is that it requires more fields that are currently exposed from /proc/$pid/maps - we need the VMAs for find_by_offset, which yields the proc map entry for a given relative address, so you can compute an absolute address. All ELF parsing is related to the special USDT notes format, which contains the instruction pointer(s) used to attach to. No symbol resolution is required.
TL;DR: There should be no conflicts between this PR, and my one... and even if there were they should be trivial to resolve.

Symbol resolution can be quite a big topic, depending on how deep you want to go. I'm not sure if aya is the right place to offer a full symbol resolution API and choose which trade-offs to make; I'm thinking it might be better to offer just enough information so that absolute addresses can be mapped to relative address (along with the file path of the library), so that the user can call into a different crate to do the actual symbol resolution. I was already pondering whether I should make such a crate; I think this PR has convinced me that it would be worth doing.

@mstange this :point_up: feels like the right approach to me.
I know very little about stack traces and symbol resolution, but given my recent experience with /proc/$pid/maps I'll weigh in on a few points below...

Personally, I think I'd like aya to maintain each process's mappings over time, and have it tell me when libraries are loaded and unloaded, and when processes appear and disappear..

I certainly feel like the first item would be ~easy to do. I'd already considered a lazy-init cache for proc/maps, and using something (inotify?) to keep it updated until the proc is closed. Adding a public API to register a callback when the cache is updated for a given PID would hopefully fulfil the requirement.
I'm not sure how we'd handle "when process appear or disappear" without watching procfs for new pids... and how Aya would know which pids are interesting... :thinking: It might be easier to defer that to the user, and to let them register interesting PIDs with Aya via the same API as described above?

When you call perf_event_open, you can request event records for new processes, i.e. "task" (fork) records. And you can also request "comm" records for process renames / execs. These records are written into the perf event's mmap buffer, but I'm not really sure how this buffer interacts with the buffer that has the PerfEventArray output - or if that's even the exact same buffer.
Here's some code which requests these records: https://github.com/mstange/samply/blob/da71321c597d4499730976923a7d0695147030b7/samply/src/linux/perf_event.rs#L313-L315
You can parse these records with https://docs.rs/linux-perf-event-reader/.

I tried taking a stab at resolving symbols here https://github.com/zz85/profile-bee/blob/main/profile-bee/src/symbols.rs
The approach is similar to this PR but falls back to loading symbols from the ELF format. There's definitely still some rough edges (don't think it's handling relocations/offsets correctly) but putting it out here in case it's useful to anyone looking into symbol lookups

Bringing this back up with #705: what's the preferred implementation here? We all agree on the need for a SymbolResolver trait, but no consensus. Is the memory mapping monitor popular enough to justify a sample implementation?


xSQLAlias: Replace WMI with CIM

This PR makes the following changes:

All usage of *-WMIObject have been replaced by CIM cmdlets (Issue #203)
Updated unit tests to validate CIM changes
Renamed internal function Get-WmiOSArchitecture to Get-OSArchitecture to remove WMI reference
Updated README to reflect changes

This change is

I work also in xSQLAlias in PR #147
So I replaced Get-WmiObject by Get-CimInstance.

@nabrond Please resolve merge conflicts.

@johlju No need to resolve the merge conflict, this PR duplicates effort in PR #147. I will just close and delete it.


Problem about hypernerf2colmap.py

Hellow
Thank you very much for your code, I would like to ask the following questions.

May I ask why the following problem occurs as long as I change 2x to 1x in hypernerf2colmap.py?

hi, because the dataset only has "2x" folder.

Hello, sorry, I am using hypernerf's misc_espresso, which contains dataset has "1x" folder

Hi, if you want to use "1x", I think you can change the imagesize, camera parameters of line 71.
Maybe that will work?

不好意思，但是他的image size是讀camera json檔案的image size，那個camera json檔案的image size，就是1x的image size

我这里是2x的，我觉得你只要把71行的那个
    print(idx,"SIMPLE_PINHOLE",image_size[0]/2,image_size[1]/2,cam['focal_length']/2,cam['principal_point'][0]/2,cam['principal_point'][1]/2,file=object_cameras_file)
改成
    print(idx,"SIMPLE_PINHOLE",image_size[0],image_size[1],cam['focal_length'],cam['principal_point'][0],cam['principal_point'][1],file=object_cameras_file)，是不是就行了

成功了 非常感謝您的幫忙!


Some bugs/questions/Feature request [v0.7.7]

1. Feature request: Display this date format -> 04/19/2020 20:30, instead of "3 days ago" for the most recent files

in case you are not interested in changing this, the text "5 days ago", "4 hours ago", etc. are they translated automatically? because they are still in English

2. These icons of the properties dialog do not change color when put in dark mode.

3. Folder size is not displayed
4.   - Network folders appear empty

Feature request: display disconnected network locations like in windows file explorer

5. Feature request: highlight folder when you drag a file over it
6. The shortcuts do not appear (this happens from previous versions)
7. In grid view, the icon of the first file is not displayed correctly:

8. strings need to be added for these:

also in the second screenshot, the dialog is white when the app was in dark mode

You can change the date format in the apps settings.
Shortcuts are not supported yet #328.
Can you mention the missing strings in #37? The second dialog is going to be replaced with a modern one instead of the Windows 8 style, the theme issue should be fixed when that is taken care of.

It would help if you opened individual issues for the other items, this way if someone wants to work on one of the items, they can do that without taking up all the other issues.

@yaichenbaum As i understand, currently it is not possible to translate this string, as new tab detection based on "new tab" string.

@tsvietOK Which string?

changing the date format only affects older files:

also that "11 hours ago" is not automatically translated into Spanish

@yaichenbaum "New tab" string. As in your PR #640 . I think this change could break new tab detection.

https://github.com/duke7553/files-uwp/issues/638#issuecomment-617963511


Sort Logic Update

Could you describe what the update to the sort logic will be in more detail?

Could you describe what the update to the sort logic will be in more detail?

already attached it in another PR :)
talked with Matt about it last meeting, very minor change to the parsing logic

Great, seems good.


Disconnect entities when they are using intra-process communication

A relevant problem of ROS2 is that it wastes resources when you have both inter and intra-process communication enabled.
For example:

Process 1: Node A publishes on my_topic, Node B subscribes on my_topic. They use intra-process communication.
Process 2: Node C subscribes on my_topic.

In this configuration Node A is publishing both inter and intra-process.
The RMW is not aware of the existence of Intra-process communication, so, every message published inter-process is delivered to both nodes.
Currently the subscription in Node B would discard the inter-process message received from Node A (since they are in the same intra-process context). However, this is done at the rclcpp layer, after the message has been sent and deserialized.
Is there a plan for implementing a feature for "disconnecting" entities that are already using intra-process communication?
Does CycloneDDS already provide functions for disconnecting a pair of entities without deleting them?
Thank you

It is something that worth considering, certainly, but the various "ignore" functions in the DDS specification are not (yet) available in Cyclone. All there is today is the "ignore local publications" flag in the rmw_create_subscription function, which I implemented in the Cyclone RMW as ignoring publications local to the same ROS node/DDS participant:
https://github.com/atolab/rmw_cyclonedds/blob/5299a8391638276267808ffbfa262205fc26ce52/rmw_cyclonedds_cpp/src/rmw_node.cpp#L634-L636
In Cyclone the "ignore local" setting is actually a tri-state that also allows you to ignore everything in the same process. It sounds like that might the behaviour that you are looking for. What I am unsure about is the expected behaviour of the RMW layer, whether there is a way for the RMW implementation to know whether intra-process communication in ROS is enabled in the first place, and whether that setting should be used regardless of the "ignore local publications" flag if intra-process communication is enabled.
The true solution to the problem (in my, perhaps a bit biased, view) is that ROS2 should not even do any intra-process optimization: and instead leave that to the RMW/DDS implementations ... I believe that certainly in the case of Cyclone it should be fairly straightforward to avoid the serialization and copying in the cases where the intra-process optimizations of ROS2 apply.

Thank you!
I was not aware of the different values for that setting.
I changed that line and I was able to achieve my desired behavior.
 if (ignore_local_publications) {
     dds_qset_ignorelocal (qos, DDS_IGNORELOCAL_PROCESS);
}

This works fine in my use-case, where I know that all the nodes will have Intra-Process Communication enabled.
From my point of view, Intra-Process Communication in ROS2 is something coupled to the concept of ROS2 context. Assuming that you have a single context per process (I haven't seen any example of a different case), the RMW layer can use the context implementation to keep track of which entities are using intra-process communication or not.
ROS2 architecture [1] depicts that intra-process communication (along with type masquerading optimizations) belongs in the language-specific client library.
http://docs.ros2.org/dashing/developer_overview.html#internal-ros-interfaces

The true solution to the problem (in my, perhaps a bit biased, view) is that ROS2 should not even do any intra-process optimization: and instead leave that to the RMW/DDS implementations.

In theory, I agree. The problem is that, as of today, none of the RMW providers that we are aware of, have the required mechanisms (avoiding serialization, copies) for efficient intra-process communication.
This fact pushed us to create a new intra-process-manager in rclcpp.
https://github.com/ros2/design/pull/239
https://github.com/ros2/rclcpp/pull/778

@joxoby thanks for the links ... too bad I didn't discover that proposal and those changes a month earlier.
I was thinking of a simple extension to RMW along the lines of passing a smart pointer to publish & from take. For Cyclone, that would be sufficient to defer serialisation until the message would actually have to be transmitted. If all matching subscriptions would be in the same process, that moment would then never come (well, probably unless a C/C++ mixture were to be used), because the intra-process communication in Cyclone already completely avoids the protocol stack.
So now these optimisations really are being done twice ...
Cyclone will keep them because they were and will remain valuable for it outside the context of ROS2. I can imagine that people might still be interested in relying on the lower layers, as that would eliminate having to extend the rclcpp implementation if the set of features of DDS that ROS2 relies on were to grow. (And I think it will: keys and a keep-last history per key value is bound to come one day, for example driven by sensor suites tracking multiple objects.)
But that's a discussion for another day. In any case, @alsora, I'm happy that you found that setting helpful. And thank you for giving me the background on the "context"s, I wondered what they were for and ignored them for the time being. It sounds like something smarter than ignoring them is possible.


Require applications to be referenced by name instead of ID

Contributor Comments

Added get_app_id() utility function to allow users to pass application name instead of ID
Updated configurations to accept app_name instead of app_id
Added unit tests for get_app_id and updated existing tests to use it

Pull Request Checklist
Thank you for submitting a contribution to easy_sast!
In order to streamline the review of your contribution we ask that you review and comply with the below requirements:

[x] Ensure that make build completes successfully
[x] Keep our reports up-to-date by committing the output of make report
[x] Rebase your branch against the latest commit of the target branch, which likely should be master
[x] If there is an issue associated with your Pull Request, align your PR title with this documentation

Codecov Report

Merging #37 into master will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #37   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          922       954   +32
  Branches       173       179    +6
=========================================
+ Hits           922       954   +32

Impacted Files
Coverage Δ

main.py
100.00% <ø> (ø)

veracode/api.py
100.00% <100.00%> (ø)

veracode/config.py
100.00% <100.00%> (ø)

veracode/constants.py
100.00% <100.00%> (ø)

veracode/utils.py
100.00% <100.00%> (ø)

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 f3f8ddf...b8e9536. Read the comment docs.

@pb-seiso merge conflict.  Let's hold on this until #36 is in, then rebase on master and take it from there.

@SeisoLLC/cto Rebased on master, fixed conflicts, updated reports, and ran a quick end-to-end to make sure everything still looks good. Let me know if you have any other feedback.

@JonZeolla Are you waiting for anything else from me before reviewing this?

No, sorry it's on my backlog

@pb-seiso please rebase on master

Codecov Report

Merging #37 (3f474f4) into master (f86a8ad) will not change coverage.
The diff coverage is 100.00%.

@@            Coverage Diff            @@
##            master       #37   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            8         8
  Lines          905       937   +32
  Branches       170       176    +6
=========================================
+ Hits           905       937   +32

Impacted Files
Coverage Δ

main.py
100.00% <ø> (ø)

veracode/api.py
100.00% <100.00%> (ø)

veracode/constants.py
100.00% <100.00%> (ø)

veracode/utils.py
100.00% <100.00%> (ø)

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 f86a8ad...3f474f4. Read the comment docs.

@pb-seiso please rebase on master

Done, ready for your review.

@JonZeolla This is ready again for review.  You can just review this one.
Note there will be a lint error on #43 since the commit lacks a body message. Please either fix that upstream or let me know if you want me to edit it when I rebase.

@pb-seiso this is good to go now; force pushed a commit rewording.  A simple conflict resolution is to just accept them as-is then re-generate them all.

@JonZeolla This is rebased and ready again for review. I ran basic integration tests on the app_name parameter which looked good, but please feel free to re-test.
Note that I've also included a fix to change the Docker image to one that uses Python 3.9.


ci: setup cancel-in-progress

Cancel confirmed by

https://github.com/hi-ogawa/vite-plugins/actions/runs/8516420019/job/23325412514


Improve Slider and song download

This commit does the following:

Improve song slider and make it like smooth like spotify.. only updating position when let go.
Improve song download format and button

Thanks for contributing, @Razamindset.


[Feature] docker image is missing curl tool for health check.

Feature Request
Is your feature request related to a problem? Please describe:
Fix tidb operator tikv command health check, ref: https://github.com/pingcap/tidb-operator/issues/4764
Describe the feature you'd like:
Add curl command into docker image.

Closed by #13765


Obsolete code example

The segment about localization using cookies tells to use "this.HttpContext", now the member is named Context, not HttpContext. (ASP .NET core 3)

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

ID: 15e7c51d-1839-1849-813a-23c4d21c64ae
Version Independent ID: d6f07538-228e-9f96-680f-6c324caf11d6
Content: ASP.NET Core Blazor globalization and localization
Content Source: aspnetcore/blazor/globalization-localization.md
Product: aspnet-core
Technology: aspnetcore-blazor
GitHub Login: @guardrex
Microsoft Alias: riande

Thanks @ThomasPrioul ... I'll mark this for triage and get to it asap.

@ThomasPrioul ... Context isn't available in the current context of either PageBase or ControllerBase. I can't repro a problem with what the topic shows in either case.

Created a PR #20239 about what I meant.

@ThomasPrioul ... Context isn't available in the current context of either PageBase or ControllerBase. I can't repro a problem with what the topic shows in either case.

The member comes from the RazorPage class. The snippet is to be used in a .cshtml file

The base class for a Razor page is PageBase. _Host.cshtml is based on Microsoft.AspNetCore.Mvc.RazorPages.Page, which is a PageBase.
I think we need two examples ... one for each of PageBase and RazorPage class. I'll modify your PR and ask Pranav to take a look.

Fixed by https://github.com/dotnet/AspNetCore.Docs/pull/20239.