Fix qemu img version

What this PR does / why we need it:
Running make rpms-update fails with Package qemu-img-17:7.1.0-3.el9 does not exist
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 #
Special notes for your reviewer:
Release note:

None

/cc @andreabolognani

do you think it is better to update other components too or only qemu version is enough?

At some point over the next week or two I'm planning to bump all RPM versions to roughly match what's going to be in RHEL 9.2 - so QEMU 7.2.0, libvirt 9.0.0 and so on. In the meantime, picking a later build of QEMU 7.1.0 to keep make rpm-deps working should be fine.

Note that QEMU 7.1.0-6 is in CentOS Stream 9 as well, so you could go with that slightly more updated version. It won't matter once we switch to QEMU 7.2.0 :)

Close this, the version has been fixed by da2ab494dc3564140c5e798a1793177bdfe61031


chore(typo): remove duplicate...

What does this PR do?
chore(typo): remove duplicate backtick
Signed-off-by: Nick Boldt<EMAIL_ADDRESS>Screenshot/screencast of this PR
N/A
What issues does this PR fix or reference?
N/A (or see commit message above for issue number)
How to test this PR?
N/A
PR Checklist
As the author of this Pull Request I made sure that:

[x] Code produced is complete
[ ] Code builds without errors
[ ] Tests are covering the bugfix
[ ] Relevant user documentation updated
[ ] Relevant contributing documentation updated

Reviewers
Reviewers, please comment how you tested the PR when approving it.

/cherry-pick release-1.3

This fixes the rendering of docs on safari browser.
Before:

After:


Margin Right examples look weird in docs, cause?

As seen above, it evidently isn't a recurring theme. Thus, why is there that little black box to the right of the actual example? Was this intentional?

The little black box is the element being pushed to the right by the element with a declared margin right.

Whoops. Didn't check the code did I?
Regards,
Enoch Appathurai
On Tue, Aug 18, 2015 at 8:09 PM, Adam Morse<EMAIL_ADDRESS>wrote:

Closed #43.
Reply to this email directly or view it on GitHub:
https://github.com/mrmrs/tachyons/issues/43#event-385192331


HHH-18027 Clear expansions after JdbcParameterBindings created to allow query reusing

https://hibernate.atlassian.net/browse/HHH-18027

Could someone review this?

Thanks, but the fix was not quite right. Superseded by https://github.com/hibernate/hibernate-orm/pull/8440


dev-ops-edit - Make pipeline only choice on that step

so the wizard is not cluttered. And move those chat room / issue tracker to a new step.
And then move the execute code to the save step, so its all done at the end. Hopefully that makes the wizard snappier in the next button, and then the user can expect some slowdown at the save as then forge is doing a lot of stuff.

Also the chat room / issue tracker wizard uses a lot of completion proposals which is a server side event which is slow in the web console. We could try to optimize that or the proposals.

The wizard now shows a pipeline ui element on the next page

Two tasks

remove that weird pipeline
move save step into step 2 so there is a finish button and the wizard is a bit faster


operators trivy-operator (2.2.0)

Thanks submitting your Operator. Please check below list before you create your Pull Request.
New Submissions

[ ] Are you familiar with our contribution guidelines?
[ ] Have you packaged and deployed your Operator for Operator Framework?

[ ] Have you tested your Operator in all supported installation modes?
[ ] Have you considered whether you want use semantic versioning order?
[ ] Is your submission signed?
[ ] Is operator icon set?

Updates to existing Operators

[x] Did you create a ci.yaml file according to the update instructions?
[x] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[x] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[x] Have you tested an update to your Operator when deployed via OLM?
[x] Is your submission signed?

Your submission should not

[ ] Modify more than one operator
[ ] Modify an Operator you don't own
[ ] Rename an operator - please remove and add with a different name instead
[ ] Modify any files outside the above mentioned folders
[ ] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[x] Description about the managed Application and where to find more information
[x] Features and capabilities of your Operator and how to use it
[x] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[x] Human readable name and 1-liner description about your Operator
[x] Valid category name1
[x] One of the pre-defined capability levels2
[x] Links to the maintainer, source code and documentation
[x] Example templates for all Custom Resource Definitions intended to be used
[x] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

@J0zi @mvalarh It is a git pull error please rerun the test.

@devopstales, to rerun use hold and unhold next time. See bellow.

/hold

/hold cancel

THX @J0zi

/merge possible

/retest

/merge possible

/retest

/hold

/merge possible


Channel page empty and profile page almost empty

After cloning<EMAIL_ADDRESS>to<EMAIL_ADDRESS>and exporting its content, https://hubzilla.nl/channel/gif is empty and  https://hubzilla.nl/profile/gif almost empty. Channels I cloned before this one don't have problems.

This is what I have in the devug log:
2015-09-03 13:33:35:0d809p2t023kspcq3c9g0cnph7 identity.php:740:profile_load: profile error: channel/gif

Oh BTW, I followed the troubleshooting information.

OH Wait! I just cloned a simple, almost unused channel from my redmatrix hub and it now gives the same error as the GIF channel. So I suppose last night something was changed in the code causing this?

Now it says that database update has failed 1151. Related?

Thanks that works, at least for new cloned channels. Is there a way to fix that GIF channel or should I nuke it and try it again?


rancher:
  console: ubuntu
  services_include:
    open-vm-tools: true
    open-iscsi: true
    qemu-guest-agent: true
    kernel-headers: true
    kernel-extras: true

this is the command
docker-machine create -d vmwarevsphere --vmwarevsphere-network "VM Network" --vmwarevsphere-datacenter "Datacenter" --vmwarevsphere-datastore "SSD" --vmwarevsphere-boot2docker-url http://..../rancheros-vmware.iso --vmwarevsphere-password ..... --vmwarevsphere-username ..... --vmwarevsphere-vcenter ....  --vmwarevsphere-cloudinit http://..../cloud-init.yml --vmwarevsphere-cfgparam disk.enableUUID=TRUE --vmwarevsphere-cpu-count 4 --vmwarevsphere-folder /k8s --vmwarevsphere-pool /Datacenter/host/*/Resources/k8s k8s-rancher

The host's clock is off by 4 years?

O.o I didn't see it, thank you very much, now it's working as expected :) 👍


Runtime Error: You are using the runtime-only build of Vue where the template compiler is not available.

Hi,
I'm getting the following error in chrome when I try to use the vue-flash-message:
main.ts:23 [Vue warn]: You are using the runtime-only build of Vue where the template compiler is not available. Either pre-compile the templates into render functions, or use the compiler-included build.
found in
--->
 at src\App.vue

I'm running the project in development mode with the vue-cli.  It's a brand new project.  I'm using Typescript.
Here are few relevant code snippets.
main.ts
import Vue from 'vue'
import VueFlashMessage from 'vue-flash-message';
Vue.use(VueFlashMessage);
App.vue

I'm pretty sure I need to use a different version of Vue than what I'm including via import Vue from 'vue' but I can't figure out how to make things work.

I figured it out - I needed to add runtimeCompiler: true in my vue.config.js file like this:
const vueConfig = {
runtimeCompiler: true
}

@theironcook Thank you very much for sharing the solution.


numpy-style docstrings

In the file "src/git_bob/_utilities.py", please make sure that all functions have proper numpy-style docstrings.
Do absolutely NOT modify the Python code otherwise.
git-bob solve

This message was generated by git-bob (version: 0.2.0, model: claude-3-5-sonnet-20240620), an experimental AI-based assistant. It can make mistakes and has limitations. Check its messages carefully.
I'm sorry, I encountered an error while processing your request. Here is the error message:
Error in solve_github_issue: Extra data: line 3 column 1 (char 31)
This is how far I came:
Using language model: claude-3-5-sonnet-20240620
-> get_most_recent_comment_on_issue(haesleinhuepf/git-bob, 105)
-> add_reaction_to_last_comment_in_issue(haesleinhuepf/git-bob, 105, +1)
-> solve_github_issue(haesleinhuepf/git-bob, 105)
-> summarize_github_issue(haesleinhuepf/git-bob, 105)
-> get_github_issue_details(haesleinhuepf/git-bob, 105)
-> list_repository_files(haesleinhuepf/git-bob)

More Details...


Does ingress for azure subscription events gets charged?

As per EventGrid pricing page, we are charged for both ingress and delivery of events.

Event Grid is priced as pay-per-use based on operations performed. Operations include ingress of events to Domains or Topics, advanced matches, delivery attempts, and management calls.

For event grid subscriptions that receive events from Azure Subscription topic type, do we get charged for every ingress? I imagine Azure-generated events might be treated differently from the events we push to custom event topics, hence the question.

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

ID: 1b572f63-312f-4567-5f06-d09bcccf303e
Version Independent ID: df817c5f-24e4-bdc7-511c-141d07a53d15
Content: Event filtering for Azure Event Grid
Content Source: articles/event-grid/event-filtering.md
Service: event-grid
GitHub Login: @spelluru
Microsoft Alias: spelluru

@sandeepiiit Thanks for the question! We're investigating this and will get back to you shortly.

@sandeepiiit Operations in Event Grid include all ingress events, advanced match, delivery attempt, and management calls. You’re charged per million operations with the first 100,000 operations free each month.

@spelluru Any thoughts here?

That solves all my concerns!
Thanks for the help with the filter creation using OR. From the azure portal description (and docs), it was pretty clear that multiple filters get AND-ed, but the OR support inside a filter is not well documented :)
I will create another github issue by using the feedback link on the page that describes advanced filtering. Hope that's helpful.
Thanks again. Closing this.


Use proper output fd for juicefs commands

juicefs mount prints log messages to stderr even if everything is ok, while users may expect to see them in stdout.
We should fix it and check outputs of other commands as well.

The current behavior is expected:

JuiceFS writes command output (e.g: juicefs info, juicefs status) to Stdout.
Logs are by default written to Stderr, no matter what level a log entry is; this ensures that logs will not mess up with normal command outputs.


No render if =no article

Type

🔧 Fix
Value
Makes the linter happy.
And stops a 500 error.

Closing in favour of #1028


[Flink] [hudi-0.11] build error

对于FSDataOutputStream(java.io.ByteArrayOutputStream), 找不到合适的构造器
Compile and integrate CDH,

you can update code to fix, default stats null

Hadoop3.. use like this:
112     try (FSDataOutputStream outputStream = new FSDataOutputStream(baos, null)) { 113       try (HoodieParquetStreamWriter<IndexedRecord> parquetWriter = new HoodieParquetStreamWriter<>(outputStream, avroParquetConfig)) { 114         for (IndexedRecord record : records) { 115           String recordKey = getRecordKey(record).orElse(null); 116           parquetWriter.writeAvro(recordKey, record); 117         } 118         outputStream.flush(); 119       } 120     }

@KnightChess @shaqf thanks for sharing the workaround.
@walkhan Does the above suggestions work for you?

@walkhan following up on this, have you tried the change as suggested? For Hadoop 3 upgrade, there is also one WIP PR addressing all issues: #5402.

@walkhan : do you have any updates on this regard.

@yihua We may need to support Hadoop 3.x in release 0.12.0

FYI this is the PR with the latest changes for Hadoop, Hive, and Spark 3.x upgrades: #5786.

@walkhan : did you get a chance to check out the updates in this issue. are you still looking for any assistance? if not, feel free to close it out


Make Tensor.product(squeezingAxes:) differentiable

Tensor.product(squeezingAxes: Tensor<Int32>) is currently not @differentiable.
We should do the following:

Add the attribute @differentiable(wrt: self, vjp: _vjpProduct(squeezingAxes:) where Scalar: TensorFlowFloatingPoint) to Tensor.product(squeezingAxes: Tensor<Int32>).
Define func _vjpProduct(squeezingAxes axes: Tensor<Int32>).
Mark Tensor.product(squeezingAxes: [Int]) and Tensor.product(squeezingAxes: Int) as @differentiable. No registered derivative is needed because they call Tensor.product(squeezingAxes: Tensor<Int32>).

TensorFlow reference implementation of ProdGrad.
Use case from mailing list.

cc @kongzii

Continuing the discussion at Use case from mailing list, I will start working on this :)

Done in https://github.com/tensorflow/swift-apis/pull/550.


API documentation?

Hi,
I was looking at your documentation and I couldn't find a guide to the API (Props the components accepts, Emitted events)
Could you please guide me?
I want to increase the area that triggers the scroll and dont want to show the ghost ... are these things possible?

Hello, the document is fully inherited from Sortablejs. I have added the API module to the document. You can check it out. Thank you for your suggestion.

Hey... Thanks for the response and updating the readme... It is a big help.
I checked the API and tried To use the scrollsensitivity, but it didn't work
<VueDraggable
    v-model="formStructure[sectionIndex]"
    animation="150"
    ghostClass="ghost"
    chosenClass="ghost"
    dragClass="drag"
    handle=".handle"
    group="questions"
    @choose="sorting = true"
    @unchoose="sorting = false"
    :sort="true"
    :scrollSensitivity="75"
  >

I also tried
<VueDraggable
    ...
    scrollSensitivity="75"
  >

But neither seemed to have an effect


BUG: JWT-generating jsonwebtoken

Describe the bug:
Installed jsonwebtoken library. Tried to create a token with jwt.sign() function. It throws an error starts with "TypeError: Cannot read property 'toLowerCase' of undefined"
Link to the blitz that caused the error
https://stackblitz.com/edit/node-hfhmh5?file=index.js
Steps to reproduce:

Go to 'Link of blitz'
Open Terminal
Run following command in terminal -> node index.js
See error

Expected behavior:
Server should run normally.
Version of webcontainer:
Hash: cb1eb6b301af424e8dffb694972509f06ea6b5db
Screenshots:

Desktop (please complete the following information):
Browser name  = Chrome
Full version  = 91.0.4472.77
Major version = 91
navigator.appName = Netscape
navigator.userAgent = Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.77 Safari/537.36
performance.memory = {
"totalJSHeapSize": 88641875,
"usedJSHeapSize": 85220759,
"jsHeapSizeLimit":<PHONE_NUMBER>
}
Additional context:

@mefaba I think this is fixed now! :tada:


Robosuite version check is not correctly working for Robosuite v1.3

https://github.com/ARISE-Initiative/robomimic/blob/2804dd97dd1625ec861298a35cb677129d3bfacc/robomimic/envs/env_robosuite.py#L52
The comment says that "only support robosuite v0.3 and v1.2+".
Since Robosuite v1.3 is released, the version check should be updated if Robotmimic actually supports v1.3.

Thank you for bringing this issue to our attention! Indeed, the repository is fully functional with robosuite datasets collected on v1.3 (but for reproducing our exact experiments we recommend being on the offline_study robosuite branch which is based off of v1.2) - we will fix this in an upcoming PR.

This should be fixed now (see here).


Update project to latest jenkins java17

Testing done

Submitter checklist

[ ] Make sure you are opening from a topic/feature/bugfix branch (right side) and not your main branch!
[ ] Ensure that the pull request title represents the desired changelog entry
[ ] Please describe what you did
[ ] Link to relevant issues in GitHub or Jira
[ ] Link to relevant pull requests, esp. upstream and downstream changes
[ ] Ensure you have provided tests - that demonstrates feature works or fixes the issue

2 tests fail when I run the tests on my RHEL 8.10 machine with Java 21.0.3 and the command:
mvn clean -DforkCount=1 verify

There are spotbugs warnings that need to be resolved as well.


Optional parameter is not cleared when navigating to same page with a different set of parameters

When navigating to a page which has two @page directives with one or two parameters, the optional one is not always cleared when navigating to this page when the optional parameter should have be set to its default.
In the documentation it is said to use two @page directives for support for optional parameters.
To Reproduce:
Start with the sample app of Razor Components, and add a new page:
@page "/node/{Id:int}"
@page "/node/{ParentId:int}/{Id:int}"

@functions {
    [Parameter]
    private int? ParentId { get; set; } = null;

    [Parameter]
    private int Id { get; set; }
}

update NavMenu.cshtml to include:
<NavLink href="node/1">First click me</NavLink>
<NavLink href="node/2/3">Then click me</NavLink>
<NavLink href="node/4">And finally click me</NavLink>

Start the app.
Navigating to node/1 works: ParentId is null and Id is 1.
Navigating to node/2/3 works: ParentId is 2 and Id is 3.
Navigating to node/4 works but gives: ParentId stays 2, and Id is 4.
Expected behavior
When navigating to node/4 I expect ParentId to be null again and Id to be 4. ParentId is a Parameter, and should be set to null when the route does not provide the information.
 It was fixed but then reverted. See this #6864. Hopefully both problems will be solved in preview 3.

@SteveSandersonMS, is this fixed already?

@mkArtakMSFT We fixed it in 0.7.0, but then we had to revert the fix just prior to the 0.7.0 release because it caused a bad regression elsewhere. We don't yet have a design for what the replacement fix should be. It should remain on the backlog, but it's not at the top of the priority list in my opinion.

Thanks @SteveSandersonMS. Can you please dupe this one with that one you reference and close this issue?

@SteveSandersonMS, I assume you meant 0.8.0 there, did you?

Yes, 0.8.0. Thanks!
The change where we originally fixed this was #4797, but then we reverted it in #6931.
I've searched and can't find another issue on the backlog tracking making a further long-term fix, so perhaps this issue can be that one for us now :)
Putting on backlog.

Plan following offline discussion:

Make Router figure out the union of all the route parameter names across all the route templates for each component. Then when supplying parameters, supply null for any not in the current route.
Check that components can receive null for value-type parameters and they get treated as default(T).

@SteveSandersonMS I might be mistaken, but this won't take into account properties default value and will erase them right (OP problem) ?

It will only erase parameters that match route tokens, not others.

In case anyone else stumbles upon this, I solved an issue where I thought the page wouldn't reload data based upon the parameters in the URL / Querystring changing.  What worked for me was overriding the "OnParametersSetAsync()" event handler (instead of code I had in the "OnAfterRenderAsync(bool firstRender)" event handler.  For example:
private readonly object _synclock = new object();

protected override async Task OnParametersSetAsync()
{
	IList<Model.MyModelClass> myModelClasses = await MyService.GetByStartUtcDateAsync(MinStartUtcDate);
	lock (_synclock)
	{
	ClearMyCollections();
	...ReloadMyCollections...
	}
}

Note, I added the locking code because I was originally observing some inconsistent behavior where sometimes the collections I was loading contained up to three times the number of expected data records.  The OnParametersSetAsync() method seems to fire multiple times and I figured it was a threading issue; haven't dug too deep there.


Use ruby 2.4.2 to addess multiple security vulnerabilities

does 2.4.2 address that proxy issue that was fixed in master but not released yet?


Icon of the body part in black instead of white

Pull Request to fix this issue:
https://github.com/SlimeVR/SlimeVR-Server/pull/1075


[epScript] Reduce overuse of DoActions in basic actions

Copied from phu54321/eudplib#9

Copied from phu54321/epScript#5

function afterTriggerExec() {
  while(Bring(P1, AtLeast, 1, "Zerg Drone", "Anywhere")) {
    MoveLocation("loc", "Zerg Drone", P1, "Anywhere");
    RemoveUnitAt(1, "Zerg Drone", "loc", P1);
    CreateUnit(1, "Zerg Mutalisk", "loc", P1);
  }
}

/* __epspy__ makes 3 Triggers for 3 actions, 2 objects are wasted.
def afterTriggerExec():
  if EUDWhile()(Bring(P1, AtLeast, 1, "Zerg Drone", "Anywhere")):
    DoActions(MoveLocation("loc", "Zerg Drone", P1, "Anywhere"))
    DoActions(RemoveUnitAt(1, "Zerg Drone", "loc", P1))
    DoActions(CreateUnit(1, "Zerg Mutalisk", "loc", P1))
  EUDEndWhile()
*/

It should use 1 DoActions in a series of actions for performance and map file size.

Only when all arguments of actions are ConstExpr, can they be merged into 1 DoActions, which is less common case as EUDVariable is used in common usage.


Update sentry release action

Verify the failure cause for sentry release action and fix it.
Acceptance criteria:
1 - Successful sentry release action.

@mike-audi could you review the auth token in sentry? The log says it is expired. I don't have access to secrets in app repo.
https://github.com/tiki/app/blob/5658a8bbd86708fbb77851f451f714b9c88c7f12/.github/workflows/release.yml#L126

@ricardobrg please test. Should be all set.


Refactor ricardian contracts

Ricardian contracts are required somebody with "god"-mode who will perform the order of arbitration.

PR #276


What is the relationship between the two projects DB-GPT and DB-GPT-HUB?

Search before asking

[X] I had searched in the issues and found no similar feature requirement.

Description
在DB-GPT的执行过程中似乎没有用到微调过的text2sql模型
Documentation Links
No response
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

DB-GPT is an AI data application development framework, and DB-GPT-HUB is a tool specifically designed for fine-tuning text2sql.

Thank you for answering. Has the DB-GPT project utilized the results of the DB-GPT-HUB project?

DB-GPT is an AI data application development framework, and DB-GPT-HUB is a tool specifically designed for fine-tuning text2sql.

yeah, we will integrate DB-GPT-HUB text2sql pipeline in DB-GPT


Timeouts / addon stops working

Issue related to
Modbus TCP to Modbus RTU
Describe the issue/bug
It seems after some time of running home assistant stops receiving sensor information and they all become unavailable.  When I login I find the Sunsynk/Deye Inverter Add-on (multi) has stopped even though watchdog is enabled. The logs show the following;
2023-05-09 19:35:10,404 ERROR   Read Error: <class 'Exception'>: (1,3,5)
2023-05-09 19:35:10,426 INFO    ############################################################
2023-05-09 19:35:10,427 INFO    No response on the Modbus interface tcp://<IP_ADDRESS>:502, try checking the wiring to the Inverter, the USB-to-RS485 converter, etc
2023-05-09 19:35:10,428 INFO    ############################################################
2023-05-09 19:35:10,429 CRITICAL This Add-On will terminate in 30 seconds, use the Supervisor Watchdog to restart automatically.
[cmd] ./run.py exited 0
[cont-finish.d] executing container finish scripts...
[cont-finish.d] done.
[s6-finish] waiting for services.
[s6-finish] sending all processes the TERM signal.
If I start the addon at this point it logs the same error and stops. The modbus rtu plugin is still running with multiple entries shown below and seems to start logging this at the time everything stops working. Looks like a connection from a local ip in the 172 range which is strange because my network is not in that range.
Expected behavior
The modbus addon shouldn't stop sending info to the mqtt server
Your environment

Home Assistant version: 2022.5.1
Addon version: 2021.10.1
Inverter make: Sunsynk
Inverter Model: 8kw
Inverter Firmware: M6.0.1 4 / S <IP_ADDRESS> / CE.4.2.4

Logs
09 May 2023 19:34:35 conn_close(): closing connection from <IP_ADDRESS>
09 May 2023 19:35:08 conn_open(): accepting connection from <IP_ADDRESS>
09 May 2023 19:35:15 conn[<IP_ADDRESS>]: timeout, closing connection
09 May 2023 19:35:15 conn_close(): closing connection from <IP_ADDRESS>

172.30.x.x is a private IP address used internally by Docker, so it simply shows that the Multi addon connects to the mbusd addon on the same Docker host. It maps to your external <IP_ADDRESS>/24 range
The watchdog might stop restarting the addon if it exits repeatedly. What you see in the log is only the last time you/the watchdog restarted the addon.
Could anything have changed wrt the USB-RS485 adaptor/your wiring etc?
Have you tried restarting the mbusd addon? (Mine has probably been running for a year on a Pi 1b without being restarted, so unlikely its the mbusd application,- but could still be your HW/wiring etc)

Thanks for clearing up the internal docker IP. My setup is still new. I only just got it up and running recently and I'm unable to keep it running for more than 24 hours at a time. It seems to stop working each day. Nothing gets touched or moved in that period and works perfectly before failing randomly. On 10 May 2023 06:11, Johann Kellerman @.***> wrote:
172.30.x.x is a private IP address used internally by Docker, so it simply shows that the Multi addon connects to the mbusd addon on the same Docker host. It maps to your external <IP_ADDRESS>/24 range
The watchdog might stop restarting the addon if it exits repeatedly. What you see in the log is only the last time you/the watchdog restarted the addon.
Could anything have changed wrt the USB-RS485 adaptor/your wiring etc?
Have you tried restarting the mbusd addon? (Mine has probably been running for a year on a Pi 1b without being restarted, so unlikely its the mbusd application,- but could still be your HW/wiring etc)
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.>
[
{
@.": "http://schema.org",
@.": "EmailMessage",
"potentialAction": {
@.": "ViewAction",
"target": "https://github.com/kellerza/sunsynk/issues/138#issuecomment-1541326770",
"url": "https://github.com/kellerza/sunsynk/issues/138#issuecomment-1541326770",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
@.***": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]

This does not seem right. You can try the pymodbus driver to connect to the serial interface directly if you suspect mbusd - see #131
Although for me mbusd seems bulletproof. I do not run the mbusd addon directly, but have not had any complaints from others

I'm still experiencing this issue even after moving to pymodbus. The last update definitely improved the stability but it still drops every second day. I can confirm its not the mbusb issue as I do not need to restart this.

Try the latest version of the addon and if this still persists, please open a new issue.


Remove webhooks for deleted services

https://github.com/rancher/rancher/issues/7214

I don't want to do this change. It means n+1 api calls where n is the number of webhooks. Also, I think the additional interface method is not going to generally applicable to all drivers and it will make implementing more drivers confusing.
Honestly, I don't think we necessarily even need to change anything with this one. The driver config is an opaque json blob. We shouldn't have to do this level of view filtering on it.

I added an additional comment t othe connected issue. I'm going to close this PR and will have the necessary debate with the powers that be in that issue.


feat(ec2): Ensure public IPs are not assigned to network interfaces

Context
This check verifies whether Amazon EC2 launch templates are configured to assign public IP addresses to network interfaces upon launch. The check fails if an EC2 launch template is set to assign a public IP address to network interfaces or if any network interface has a public IP address.
Description
Added ec2_launch_template_no_public_ip check with metadata and respective unit tests.
Checklist

Are there new checks included in this PR? Yes

If so, do we need to update permissions for the provider? No

[X] Review if the code is being covered by tests.
[X] Review if code is being documented following this specification https://github.com/google/styleguide/blob/gh-pages/pyguide.md#38-comments-and-docstrings

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

Can we also check the second part of the check?
"The control fails if an EC2 launch template is configured to assign a public IP address to network interfaces or if there is at least one network interface that has a public IP address."


Ensure that exception specifications match for delete overloads

Fixes #1737

Coverage: 99.323%. Remained the same when pulling 3cd307953102da283ab8b0a9769dcff8e59a2f89 on CiderMan:fix-build-without-exceptions-on-centos-7 into fd25857ee8b3dbf7a324eaa400d94c55081fb257 on cpputest:master.

@basvodde Is there a problem with the 'CMake GCC ARM embedded (pull_request)' build? It seems to have failed with a 404 error long before getting close to the CppUTest code but that has resulted in a load of other (also relevant) tests being cancelled...

@basvodde Is there a problem with the 'CMake GCC ARM embedded (pull_request)' build? It seems to have failed with a 404 error long before getting close to the CppUTest code but that has resulted in a load of other (also relevant) tests being cancelled...

It seems like there has been work in the QEMU area in the last week or two, meaning that the URL for the .deb is no longer valid. I've picked what looks like the closest and it now runs. I am happy to revert the change, if you would like to deal with updating the workflows separately. The new failure (CMake Linux Clang 14) fails on the current master branch so is not due to my change.

@thetic What do you think? Ack?

Just to update, the failure was not the same as on master (one was Apple and the other Linux and similar, but different, tests) but I think that it is the same root cause. The tests are potentially racey as they access memory after it is freed so I wonder if that is what causes occasional failures. I did notice that there was a typo in one of the tests so have fixed that while in there but I don't not think that the typo was the cause of the failure.

#1725

#1725

Should I revert the commits addressing the Qemu and the typo in the test so that this PR can be delivered or are you happy to deliver this as-is and subsequently deal with them on master?

I would roll back your qemu changes and cherry-pick #1739. It has proven too fragile to try to maintain.
I'm not sure about #1725. It's been open for a while.

OK. I've reverted the Qemu change - I'll leave #1739 to be delivered separately as it is basically unrelated. I've left the typo fix in place as it is correct (I believe) until such time as the tests are removed or changed by #1725. Hopefully that will allow this PR to be merged.

Ok, thanks


[Bug]: Http Status Code 418 has the wrong description

Tempest Version
1.0-alpha4
PHP Version
8.3
Operating System
Linux, MacOS, Windows
Description
This is important... the 418 status code has the wrong description.
Steps to Reproduce
Look at the Http status code 418.

What's wrong with it?

Spec says "I'm a Teapot." Also, on two or three enum values, their factory method is not covered by tests and actually is failing.
I saw this by running coverage on unit tests, not the integration tests. 😛🙃


[recom post] Obsolete guidance re glyph names

The 'post' section states:

Note that names for all glyphs must be supplied as it cannot be assumed that all Microsoft platforms will support the default names supplied on the Macintosh.

Is this obsolete guidance that can be removed?

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

ID: 95e88b53-d670-0240-422c-72748258ab2a
Version Independent ID: b5fff1ee-cf03-e424-a2dc-aee58e0429e4
Content: Recommendations for OpenType Fonts - Typography
Content Source: typographydocs/opentype/spec/recom.md
Product: typography
GitHub Login: @PeterCon
Microsoft Alias: PeterCon

It's still possible to make a post table according to Apple's old spec, omitting standard Mac glyph names. I would say something like 'OpenType fonts should either provide glyph names for all glyphs or none (format 3)', without going into the reasons why this differs from the Apple TT spec.

either provide glyph names for all glyphs or none (format 3)

Version 2 post table also allows partial coverage (not all glyphs has name), doesn’t it?

'post' v2 requires an index into some name data for every glyph in the font, but multiple GIDs can use index 0, which means ".notdef".

I’m sure I have seen fonts where some glyphs did not have names (otherwise the possibility wouldn’t have occurred to me).
The table has numGlyphs glyphs that should but not required to be the same as numGlyphs in maxp table, so it is quite possible to have numGlyphs that is less than the number of glyphs in the font and not have any entries for the top glyph IDs.
I modified FontTools to allow me to generate such a font, and it seems to be functional so far. FontBook complains about the post table being unusable but otherwise allows me to install and use it. FreeType gives .notdef for the glyphs with missing names, but HarfBuzz just synthesizes names for them. I didn’t do more testing, though. But probably the spec needs to use a stronger word than should if this is not supposed to be possible.

Apple's spec says

Note that the numberOfGlyphs field must be equal to the numGlyphs field of the 'maxp' (Maximum Profile) table.

But you're right, the OT spec says

Number of glyphs (this should be the same as numGlyphs in 'maxp' table).

I'm not too surprised that things pretty much work. ("We don't need no stinkin' glyph names!")

But probably the spec needs to use a stronger word than should if this is not supposed to be possible.

I'm not going to push for that. Hey, I was just wondering if we need to keep that odd-sounding bit about default names supplied by the Mac.

In my view glyph names are optional and mostly a debugging information, any tool that depend on them is broken by design. That is a different issue that what is being raised here, sorry for hijacking it.

Proposed change for the next version, along the lines suggested by John:

Note that names for all glyphs must be supplied as it cannot be assumed that all Microsoft platforms will support the default names supplied on the Macintosh.Some applications might not implicitly support standard Macintosh glyph names. Any glyph names should be provided explicitly in the font.


[feat add]: rating system for resume

Fixes #128
Changelog

added Resume Rating Sytem
fixed repeated caching
update documentation

Thank you for submitting your pull request! 🙌 We'll review it as soon as possible. In the meantime, please ensure that your changes align with our CONTRIBUTING.md. If there are any specific instructions or feedback regarding your PR, we'll provide them here. Thanks again for your contribution! 😊

LGTM🤺


Unfreeze cyvcf2

This PR adds | fixes:

new version of cyvcf2!

How to prepare for test:

prepare a new image for scout with this base image

How to test:

deploy to cv-vm1
reload variants for a case

Expected outcome:

[ ] variant loading should proceed nominally

Review:

[ ] Code approved by
[ ] Tests executed by
[ ] "Merge and deploy" approved by

This version is a:

[ ] MAJOR - when you make incompatible API changes
[ ] MINOR - when you add functionality in a backwards compatible manner
[ ] PATCH - when you make backwards compatible bug fixes or documentation/instructions

Should be fine, but before merging let's try that both images build

python3.7.3-slim-stretch-cyvcf2-venv builds fine 🆗

It is currently used by Mutacc --> https://github.com/Clinical-Genomics/mutacc/blob/1999bb9d75a78a543d2cec4df601387c89827a85/Dockerfile#L4
But it's fine since Mutacc is using version 1 and this will be version 2
Pushed to Docker Hub 🆗

python3.8-cyvcf2-venv builds also fine 🆗

I don't think it is actually in use but we might always use it, since it saves time to install CyVCF2
Pushed to Docker Hub: 🆗


"Maia" is listed in the drop-down menu

Description:
When user writes "Maia" the location appears in the drop-down menu next to the comune and the county witch is a part according to the law
Precondition:
The website is up an running.

Step 1
Write in the search bar "Maia"
Expected results
The location appears in the drop-down menu as "Comuna Maia, ** IALOMIȚA**"

Step 2
Press "x" button.

Expected results
The location was deleted from the search bar.

Step 3
Write in the search bar "Maia"

Expected results
The location appears in the drop-down menu as "Sat Maia, IALOMIȚA (Maia)".


feat: add apex code coverage reporters

What does this PR do?
Add code coverage reporters as provided via istanbul APIs
What issues does this PR fix or reference?
@W-11025210@
Functionality Before
Does not exist
Functionality After
Add CoverageReporter class, which provides interface to create code coverage reports from ApexCodeCoverageAggregate or ApexCodeCoverage data. The class consumes istanbul API that generate coverage reports.
Report types included are: see istanbul for details

clover
cobertura
html-spa
html
json
json-summary
lcovonly
teamcity
text
text-summary
lcov and text-lcov have been exclude. Report text-lcov writes to the console exclusively and lcov duplicates html and locvonly.

@peternhale do you have an idea of the documentation changes we might want to add with this? I've added our doc writer @sbudhirajadoc to make sure we update our docs to match the new functionality here, for instance on our apex Commands reference page.


InfernalVoidScans: update domain

Checklist:

[x] Updated extVersionCode value in build.gradle for individual extensions
[x] Updated overrideVersionCode or baseVersionCode as needed for all multisrc extensions
[x] Referenced all related issues in the PR body (e.g. "Closes #xyz")
[x] Added the isNsfw = true flag in build.gradle when appropriate
[x] Have not changed source names
[x] Have explicitly kept the id if a source's name or language were changed
[x] Have tested the modifications by compiling and running the extension through Android Studio
[x] Have removed web_hi_res_512.png when adding a new extension

Closes #5187

Did you test to make sure it works (since you didn't check the checklist that you tested your changes)? Sometimes it's not as simple as updating the domain.

Untested, will aim to test this weekend

Ok, tested and confirmed that this works


feat: remove old reports + add overall report

This model is incredibly bad
Summary by Sourcery
Remove old individual reports and introduce a new overall report to improve data management and reporting efficiency.
New Features:

Add an overall report to consolidate information from multiple sources.

Enhancements:

Remove outdated individual reports to streamline data management and reduce clutter.

Thanks!


Tweak error handling

Adds a target for foreground logging during E2E
Removes a pointless return of an input pointer variable
Adds error handling when the Get for the deletion object fails

/hold

/unhold


Preview with draft and private post

I have managed to get preview to work for published post, but not for draft and private post and getting 404 page as a result. Does preview work with these post status or only for published post?
I setup TylerBarnes's using-gatsby-source-wordpress-experimental starter and also converted gatsby-starter-wordpress with gatsby-source-wordpress-experimental, tested locally through ngrok and through Gatsby Cloud.
There is no mention of it in the preview's page nor Gatsby Cloud newest WordPress getting started page.
Running:

WP Gatsby 0.4.8
WP GraphQL 0.10.2
WP 5.4.2
gatsby-source-wordpress-experimental 1.0.2
Preview through Gatsby Cloud and further test locally through ngrok

Just updated to the 1.0.3 with WP Gatsby v0.4.9, but still getting 404 on draft preview. Gatsby Cloud logged as a successful built with the draft preview request.

Managed to get this partially resolved, as It was an issue with Gatsby Cloud, where it always triggered TWO preview build processes per single preview click, and while Gatsby Cloud is still building the preview, WordPress end will get a Gatsby 404 error before the built is completed. Once the built is completed, requesting a preview again on draft post will then be displayed.
Still trying to figure out why it triggers webhook twice on a single preview request though, but this issue is resolved.


Cannot move on the start of the chapter

In the Readium test app and our custom implementation moving on chapters doesn't work on one of our epub files. See the video below:
https://github.com/readium/kotlin-toolkit/assets/26696190/66f0b28b-1b91-4752-828e-8ac3a698abfe

Hi, please follow the bug report issue template to make sure we can reproduce the issue in the same conditions: https://github.com/readium/kotlin-toolkit/issues/new?assignees=&labels=&projects=&template=bug_report.md&title=

In version 2.3.0 everything works correctly


Fix AutoBackup name typo

Interesting, now CI is complaining... 🤔

Interesting, now CI is complaining... 🤔

🤷🏼♂


renaming the Go module name to github.com/rog-golang-buddies/rapidmidiex

I noticed here that the Go module is going to cause issues given its not the same as the repo url but the organisation name, this could cause conflicts later on, can this be fixed?

@adoublef fixed. Changed it to github.com/rog-golang-buddies/rapidmidiex


Bitbucket Support

Does renovate support Bitbucket at all? If not is there any plan to add support?

Bitbucket is not currently supported, and I don't have any plans currently. However, the code is structured in such a way that adding new providers should be fairly easy from now on.
We added GitLab support a month or two ago. An example of the API required can be found in the GitLab API source: https://github.com/singapore/renovate/blob/master/lib/api/gitlab.js
If you're interested in helping, or for anyone reading this in future who is, you can see how we worked through GitLab support here: https://github.com/singapore/renovate/issues/65
Essentially, an interested user checked the GitLab API for compatibility and after that I wrote the code accordingly. I don't mind doing the same for Bitbucket if there's an interested user or two who I know will be around to test it, because I'm not an active user of Bitbucket myself.

This looks like it might be somewhat of a feat of strength. For one, it does not look like Bitbucket has auth token support.

app passwords sounds like one way: https://confluence.atlassian.com/bitbucket/app-passwords-828781300.html

@rarkins have you had a chance to look into the requirements? I'd be keen to help out if needed.

@jribeiro actually I will be looking into this again in the next week or two, I'll update here

If you can examine how BitBucket's tokens/password support works and report back though, it would be a helpful start. Ideally we want something like the "personal access tokens" we use in GitHub, GitLab and VSTS

Hi @rarkins,
I've been looking at Bitbucket app passwords and they seem to work. The idea is that you create an app password and you associate specific permissions with it. In my test, adding write PR permissions also added read PR and read/write repository.
The above gives you back a token which you can use in combination with your bitbucket username to generate the Authentication: Basic <token> header.
The only pitfall with this is that in order to use API v2 - which I use in these examples - you need to have 2-factor authentication in place.
I've also compiled a list of endpoints similar to the list created for Gitlab:
BaseURL: https://api.bitbucket.org/2.0/

Please note that the repo name, in bitbucket, seems to be a combination of the username and the repo slug - ${owner}/${repoName}

initRepo

GET repos/${repoName}

res.body.owner.login
res.body.default_branch

GET /repositories/${owner}/${repoName}

res.body.owner.username
res.body.mainbranch.name

getBranchCommit

GET repos/${config.repoName}/git/refs/heads/${branchName}

res.body.object.sha

GET /repositories/${owner}/${config.repoName}/refs/branches/${branchName}

res.body.target.hash

getCommitTree

GET repos/${config.repoName}/git/commits/${commit}

res.body.tree.sha
Don't think this is actually supported atm. See: https://bitbucket.org/site/master/issues/9279/changed-files-between-commits-bb-10390
When you request /repositories/${owner}/${repoName}/commits/${commitId} there's a few links including the diff which might be helpful (?)

getRateLimit

GET rate_limit

res.body
No end-point. 5k/hour for file req; 1k/hour for listing repos, commits, etc
https://confluence.atlassian.com/bitbucket/rate-limits-668173227.html

findFilePaths

GET search/code?q=repo:${config.repoName}+filename:${fileName}
No known equivalent in bitbucket. It's possible to retrieve a list of all repository root files:
GET /repositories/${owner}/${repoName}/src
And then request sub-folders:
GET /repositories/${owner}/${repoName}/src/${branchName}/${subFolder}

branchExists

GET repos/${config.repoName}/git/refs/heads/${branchName}
GET /repositories/${owner}/${repoName}/refs/branches/${branchName}

createBranch

POST repos/${config.repoName}/git/refs
Not supported in bitbucket cloud. You can create a branch when making a commit:
POST /repositories/${owner}/${repoName}/src
message
branch
https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/{username}/{repo_slug}/src#post

deleteBranch

DELETE repos/${config.repoName}/git/refs/heads/${branchName}
Not supported in bitbucket

updateBranch

PATCH repos/${config.repoName}/git/refs/heads/${branchName}
No known equivalent, but the create branch end-point may work

getBranchPr

GET repos/${config.repoName}/pulls?+state=open&base=${config.defaultBranch}&head=${config.owner}:${branchName}
No known equivalent. It's possible to retrieve a list of all pull requests, and filter on that
GET /repositories/${owner}/${repoName}/pullrequests/activity

addAssignee

POST repos/${config.repoName}/issues/${issueNo}/assignees

Not sure but this may help: https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/{username}/{repo_slug}/issues#post
addLabels

POST repos/${config.repoName}/issues/${issueNo}/labels

Not supported from what I can see
findPr

GET repos/${config.repoName}/pulls?head=${config.owner}:${branchName}

No known equivalent. It's possible to retrieve a list of all merge requests and filter on that https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/{username}/{repo_slug}/pullrequests
checkForClosedPr

GET repos/${config.repoName}/pulls?state=closed&head=${config.owner}:${branchName}

Same as above. You can pass state filter which can be one of MERGED / SUPERSEDED / OPEN / DECLINED
https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/{username}/{repo_slug}/pullrequests
createPr

POST repos/${config.repoName}/pulls
POST /repositories/${owner}/${repoName}/pullrequests
https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/{username}/{repo_slug}/pullrequests#post

getPr

PATCH repos/${config.repoName}/pulls/${prNo}
PUT /repositories/${owner}/{repoName}/pullrequests/{pull_request_id}
https://developer.atlassian.com/bitbucket/api/2/reference/resource/repositories/{username}/{repo_slug}/pullrequests/{pull_request_id}#put

getFile/getFileContent/getFileJson

GET repos/${config.repoName}/contents/${filePath}?ref=${branchName}
GET /repositories/${owner}/{repoName}/downloads/{filename}

writeFile

PUT repos/${config.repoName}/contents/${filePath}
POST /repositories/${owner}/${repoName}/src

commitFile -> createBlob -> createTree -> createCommit
No known equivalent end-points for these functions. However, you may be able to create the required commit and file for that commit, using the commit end-point
Hope it helps.

@jribeiro that's definitely really helpful and it looks very promising. Hopefully enabling 2FA is not a problem if people wish to utilise this with APIv2.
FYI I have moved the GitHub implementation away from using API find/search endpoints and instead doing as you suggested - downloading a complete list the first time it's needed and then caching it. This applies to the file list, PR list, and branch list. The app is generally limited by network/API time so reducing requests is really helpful.
I'd like to note here one more thing to look up: is BitBucket happy with forward slashes / in repository and branch names in the URL, or do they need them escaped with %2F. GitHub is fine with them but GitLab recently moved to escaping and it's been painful.
@iamstarkov has offered to fork and start a WIP soon, I will then fill out a kind of skeleton of functions necessary and any tips/comments for implementation. Combined with your above notes on the endpoints, we can hopefully get this done soon!

We should also note here any peculiarities of BitBucket compared to others. It seems they follow the same naming conventions as GitHub (e.g. Pull Requests). I remember seeing previously that they only support markdown bodies for PRs though (not HTML), which is like VSTS.

@jribeiro this is hell of a research

@iamstarkov here, i will look into this starting from tomorrow

i figured out how to auth myself againt BB api. I will file initial WIP pull-request today

its happening https://github.com/renovateapp/renovate/pull/1226

Awesome @iamstarkov! I've subscribed to the PR. Happy to help testing if needed

Happy to help with this

Happy to help/test on a Bitbucket Server instance (:

cant wait for this XD

Also happy to help on bitbucket server support. I added bitbucket server support to DangerJS, and that work included adding TS types for a lot of the API responses, which may be beneficial here.
https://github.com/danger/danger-js/blob/master/source/danger.d.ts#L61

If anyone is interested to help test, the code in #2238 runs now.
Clone the repo, check out the bitbucket branch, run yarn, and then yarn start .....
You will need authentication, see https://github.com/renovatebot/renovate/blob/234b910b2b98ae19cfa3a38c4e623de6889f431f/lib/platform/bitbucket/README.md for details
So it might look like one of these:
BITBUCKET_TOKEN=abc yarn start --log-level=debug thatsme/myrepo
yarn start --username=thatsme --password=something --log-level=debug thatsme/myrepo

It has been tested against BitBucket Cloud for now, when we are happy with it being good enough then it will be merged into master. In theory nearly everything should work with BitBucket Server too and feedback on that compatibility is very welcome. We'll decide based on the complexity whether to fix server compatibility in the same branch or wait until after the merge.

Bitbucket support has now been merged into master, and ready for beta testing.
For details, see:
https://renovatebot.com/blog/bitbucket-cloud
https://github.com/renovatebot/renovate/blob/master/lib/platform/bitbucket/README.md
https://github.com/renovatebot/renovate/blob/master/docs/self-hosting.md
If you have any config questions or trouble getting started, please post an issue to the dedicated Config Help repo instead: https://github.com/renovatebot/config-help

More up to date links regarding BitBucket:
https://github.com/renovatebot/renovate/blob/master/docs/usage/self-hosting.md
Are there more thorough/comprehensive examples out there for BitBucket Cloud?

Please do not post in old issues. Open a new discussion for request help
https://github.com/renovatebot/docker-renovate/blob/master/docs/bitbucket.md


Register APNs token with debug=true

Describe the bug
It appears that Endpoint ChannelType is always APNS even when pinpoint is configured to debug mode (instead of APNS sandbox)
To Reproduce
Register for push notifications with
// Instantiate Pinpoint
let pinpointConfiguration = AWSPinpointConfiguration.defaultPinpointConfiguration(launchOptions: launchOptions)

// Set debug mode to use APNS sandbox, make sure to toggle for your production app
pinpointConfiguration.debug = true

Which AWS service(s) are affected?
Pinpoint Push notifications for iOS
Expected behavior
Store the token with ChannelType = "APNS_SANDBOX"
Environment:
PODS:
  - Amplify (1.4.4):
    - Amplify/Default (= 1.4.4)
  - Amplify/Default (1.4.4)
  - AmplifyPlugins/AWSCognitoAuthPlugin (1.4.4):
    - AWSAuthCore (~> 2.19.0)
    - AWSCognitoIdentityProvider (~> 2.19.0)
    - AWSCognitoIdentityProviderASF (~> 2.19.0)
    - AWSCore (~> 2.19.0)
    - AWSMobileClient (~> 2.19.0)
    - AWSPluginsCore (= 1.4.4)
  - AmplifyPlugins/AWSPinpointAnalyticsPlugin (1.4.4):
    - AWSCore (~> 2.19.0)
    - AWSPinpoint (~> 2.19.0)
    - AWSPluginsCore (= 1.4.4)
  - AWSAuthCore (2.19.1):
    - AWSCore (= 2.19.1)
  - AWSCognitoIdentityProvider (2.19.1):
    - AWSCognitoIdentityProviderASF (= 2.19.1)
    - AWSCore (= 2.19.1)
  - AWSCognitoIdentityProviderASF (2.19.1)
  - AWSCore (2.19.1)
  - AWSIoT (2.19.1):
    - AWSCore (= 2.19.1)
  - AWSMobileClient (2.19.1):
    - AWSAuthCore (= 2.19.1)
    - AWSCognitoIdentityProvider (= 2.19.1)
    - AWSCognitoIdentityProviderASF (= 2.19.1)
    - AWSCore (= 2.19.1)
  - AWSPinpoint (2.19.1):
    - AWSCore (= 2.19.1)
  - AWSPluginsCore (1.4.4):
    - Amplify (= 1.4.4)
    - AWSCore (~> 2.19.0)
    - AWSMobileClient (~> 2.19.0)

Dependency Manager: Cocoapods
Swift Version : 5
Device Information (please complete the following information):
Device: iPhone 11 Pro
iOS Version: iOS 13.0
Specific to simulators: No
Additional context
The below is output from get-user-endpoints from the aws CLI to better illustrate the issue:
{
  "ChannelType": "APNS",
  "Address": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "EndpointStatus": "ACTIVE",
  "OptOut": "NONE",
  "RequestId": "d2889dec-420d-435d-95b2-dc9e0e857a7e",
  "Location": {
    "Country": "xx"
  },
  "Demographic": {
    "Make": "apple",
    "Model": "iPhone",
    "Timezone": "Asia/Jerusalem",
    "Locale": "en_IL",
    "AppVersion": "0.1",
    "Platform": "ios",
    "PlatformVersion": "13.6.1"
  },
  "EffectiveDate": "2020-12-14T07:13:33.889Z",
  "Attributes": {},
  "Metrics": {},
  "User": {
    "UserId": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
    "UserAttributes": {}
  },
  "ApplicationId": "xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx",
  "Id": "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx",
  "CreationDate": "2020-12-14T07:13:33.889Z"
}

@rochabr  Thanks for the workaround, it also worked for me.  I burned alot of time until I found this but would have burned alot more had I not.

Amplify.Analytics currently does not support push notification, we will take this as a feature request and post updates here when we have more info.

For me the workaround did not work, as I was also using Amplify AWSCognitoAuthPlugin and initialized Pinpoint with a AmplifyAWSCredentialsProvider according to instructions here: https://github.com/aws-amplify/amplify-ios/issues/662
I tried all sorts of stuff and what did it was to replace AmplifyAWSCredentialsProvider with AWSCognitoCredentialsProvider.
So this line:
let credentialsProvider = AmplifyAWSCredentialsProvider()
replaced by:
let credentialsProvider = AWSCognitoCredentialsProvider(regionType: <REGION>, identityPoolId: "********************")

Does this PR fixes the issue? You can try the latest amplify-ios version.

Closing due to inactivity


Support for rbegin / rend

Since the containers support random-access given adequate underlying container, it would be nice for them to provide the typedefs
 reverse_iterator
 const_reverse_iterator

and the families of function rbegin() / rend() / crbegin() / crend()

Why do you need that? Iterating a unordered container is more or less random anyways


updated dependencies and gradles

Travis needs to pass.
This changes the target API, has this been tested? E.g. HTTPS strictmode
I'm wary about accepting binaries. Might prefer to update that through me or @bobheadxi

@d4rken

yeah im working on that
ive had no problems with other apps ive worked on when changing target api
thats fine if you wish to do it that way

ok so the problem is
* Where:
Build file '/home/travis/build/TacoTheDank/reddit-android-appstore/app/build.gradle' line: 70
* What went wrong:
A problem occurred configuring project ':app'.
> No signature of method: java.lang.String.positive() is applicable for argument types: () values: []
  Possible solutions: notify(), tokenize(), size(), size()

and im not sure what exactly is wrong, could yall help?
https://github.com/TacoTheDank/reddit-android-appstore/blob/dev/app/build.gradle#L70

ive had no problems with other apps ive worked on when changing target api

If you have checked all screens with an Android P and non Android P ROM, e.g. lowest target API, it should be okay.

and im not sure what exactly is wrong (though its not the api being changed), could yall help?

Hmm, try compare it too https://github.com/d4rken/android-java-starter/blob/master/app/build.gradle#L57

hmm the only difference is that my fork has parenthesis after gitSha, gonna try removing that

nope, so i added stacktrace to travis and the output is this
https://travis-ci.com/TacoTheDank/reddit-android-appstore/builds/80964865

hmm the only difference is that my fork has parenthesis after gitSha, gonna try removing that

It needs to be gitSha() because it's a function that's being called.

ill redo this in a separate pull request

Thanks for taking the time to work on this @TacoTheDank !

yea no problem, i like contributing to apps i use :3


Protractor e2e tests fail on prod build

I'm submitting a ...  (check one with "x")
[x] bug report => search github for a similar issue or PR before submitting
[ ] feature request
[ ] support request => Please do not submit support request here, instead see use [gitter](https://gitter.im/mgechev/angular2-seed) or [stackoverflow](https://stackoverflow.com/questions/tagged/angular2)

Current behavior
Local protractor e2e-tests against a dev build run successfully, while the same tests against the prod build fail with the error message: "Timed out waiting for asynchronous Angular tasks to finish after 60 seconds." I am aware of the protractor timeout documentation and the fix to run asynchronous requests outside of the angular zone. However this does not solve my problem, since my tests runs through against a dev build.
Expected behavior
e2e tests with protractor show the same behavior on the production build as well as on the development build of the angular seed.
Minimal reproduction of the problem with instructions
Executing the gulp tasks for dev e2e tests:

npm run webdriver-start

npm run serve.e2e

npm run e2e

vs. Executing gulp tasks for e2e tests against prod:

npm run e2e.ci.dev

What is the motivation / use case for changing the behavior?
The tests fail without clear indication why.
Please tell us about your environment:
OSX 10.11.6, WebStrom 2017.1.4, NPM 3.10.8, protractor: ^5.1.2, @types/gulp-protractor: ^1.0.29, @types/selenium-webdriver: ^3.0.3

Angular Seed Version: aaaaf75
649257dc3f76f76c5b553e6c269db5fab6846d11

Node: node --version =
NPM 3.10.8

@tobiaseisenschenk thanks for reporting this issue. Will take a look ASAP.

Tried to reproduce the issue. The protractor tests run successfully for me. Probably this is environment specific issue.

Same issue here, the test ran successfully when I create the build using "ng build", but not "ng build --prod", it keeps telling me that the protractor is not seeing the elements that leads to timeout issues.
Could you please tell me what is the different here?
Thanks


View team is broken for new teams

Fixed, here is the regression test
  it 'Issues 139 - View team is broken for new teams (edit page)', ->
    project       = 'bsimm'
    team          = 'aaaaaa-bbb'
    team_Data_Url = "/api/v1/team/#{project}/get/#{team}"
    team_Data     = {}

    options =
      url_Location    : "/view/#{project}/#{team}/edit"
      url_Template_Key: 'pages/.page.html'

    inject ($injector)->
      $injector.get('Render_View')(options)
                      .set_Expect_Get team_Data_Url, team_Data
                      .run()
                      .html.assert_Contains('TeamEditController')

  it 'Issues 139 - View team is broken for new teams (edit page)', ->
    project       = 'bsimm'
    team          = 'aaaaaa-bbb'
    options =
      url_Location    : "/view/#{project}/#{team}/table"
      url_Template_Key: 'pages/.page.html'

    inject ($injector)->
      $injector.get('Render_View')(options)
               .set_Expect_Get "/api/v1/data/#{project}/#{team}/score", {}
               .set_Expect_Get "/api/v1/data/#{project}/#{team}/score", {}
               .set_Expect_Get "/api/v1/data/#{project}/#{team}/score", {}
               .set_Expect_Get "/api/v1/team/#{project}/get/#{team}"  , {}
               .set_Expect_Get "/api/v1/team/#{project}/get/#{team}"  , {}
               .set_Expect_Get "/api/v1/team/#{project}/get/#{team}"  , {}
               .run()
               .html.assert_Contains('<div id="teamMenu">')


Click on a tab only see bathrooms for that gender (instead of all bathrooms in a floor)

Finished.

When a user clicks on the "All" tab, they see all floors with bathrooms.
When a user clicks on the "Men" tab, they see all floors with men and gender-neutral bathrooms. When they click on a floor, they only see men and gender-neutral bathrooms.
When a user clicks on the "Women" tab, they see all floors with women and gender-neutral bathrooms. When they click on a floor, they only see women and gender-neutral bathrooms.
When a user clicks on the "Gender-Neutral" tab, they see all floors with gender-neutral bathrooms. When they click on a floor, they only see gender-neutral bathrooms.


Custom Format with name CRiT skipped because another CF already exists with that name

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When running recyclarr sync below warning is displayed on console:
[WRN] Custom Format with name CRiT (Trash ID: 16622a6911d1ab5d5b8b713d5b0036d4) will be skipped because another CF already exists with that name (ID: 246). To fix the conflict, delete or rename the CF with the mentioned name
I checked all the configs being used and nowhere else CRiT is being used with a different Trash ID.
Expected Behavior
It should not give this warning because CRiT isn't being used as duplicate name with a different ID.
Steps To Reproduce

Use the pre-made yml from: https://github.com/recyclarr/config-templates/blob/master/radarr/uhd-bluray-web.yml & https://github.com/recyclarr/config-templates/blob/master/radarr/hd-bluray-web.yml
Run recyclarr sync

Environment & Versions
- Operating System: Debian + Official docker container
- Architecture: x64
- Recyclarr Version: 5.1.1+Branch.tags-v5.1.1.Sha.4d0ce0d09f367ce2520eca53c4043568efa328fd
- Recyclarr Build: 5.1.1+Branch.tags-v5.1.1.Sha.4d0ce0d09f367ce2520eca53c4043568efa328fd
- Sonarr Version: <IP_ADDRESS>8
- Radarr Version: <IP_ADDRESS>16

Recyclarr Log File(s)
recyclarr_2023-06-30_13-16-33.debug.log
cache.zip
configs.zip
recyclarr_2023-06-30_13-16-33.verbose.log
Configuration YAML
Added in the Log Files as configs.zip

Sonarr / Radarr Logs
No response

Could you attach the verbose log file too? Thank you!

Could you attach the verbose log file too? Thank you!

Done

Thanks for those extra logs. After investigating, looks like the problem is the way you've set up the instances. You should not point 2 or more config instances at the same actual service. In this case, your Radarr instances hd_bluray_web and uhd_bluray_web both point to the same server. There's some confusing behavior in Recyclarr when you do this, because it thinks both of those are separate instances of Radarr. So in that sense, your Radarr instance is conflicting with itself.
For now, I recommend you consolidate your configuration files. Copy & paste the configuration (minus the radarr: root element) into the same file.

I am having this same warning message and yet I do not have multiple sonarr/radarr instances. My config has one instance of radarr and one of sonarr. I assume the CF IDs are generated in Sonarr, if so, would this not be caused by a Sonarr change?

I am having this same warning message and yet I do not have multiple sonarr/radarr instances. My config has one instance of radarr and one of sonarr. I assume the CF IDs are generated in Sonarr, if so, would this not be caused by a Sonarr change?

Here's a link of my config: https://pastebin.com/dGyEG2mJ

To add. SiC is the only CF doing this, I have multiple same CF's across different configs and those aren't giving a warning.
Such as AM

It happened for a large number of CFs in my case. Here's the log: recyclarr_2023-07-01_14-35-28.debug.log

@apapushoy Please archive & attach your cache directory and also provide the corresponding verbose.log file. I will take a look.
@jpdsc Please consolidate your config files and test again. If the issue still happens, I will dig further. It's easier if we can rule out one thing at a time.
For now I will reopen since another has posted about the issue here. I certainly want to make sure there's no bug here.

Here you go:
recyclarr_verbose.tar.gz
cache.tar.gz
Thanks.

@apapushoy Can you walk me through anything unusual you have done with your Radarr instance named movies? Your cache says you have those CFs already on your instance but with different IDs. Typically this happens when you import them manually, or change the Radarr instance or installation in some way (for example, localhost:7878 pointed at an old instance and you installed a new one in its place).
The only way IDs get confused like this is when something happens to the CFs in Radarr that Recyclarr didn't know about, including changing the URL to a different instance (indirectly).
Understanding the history of what you did will reveal the root cause.
If you aren't interested in the reason/cause, simply set replace_existing_custom_formats: true, performing a single recyclarr sync and then changing that setting back to false will clear the warnings.

I'm running everything on a NAS via docker. Initially the Starr apps talked to each other via the network hostname of the NAS. However, this generated 380k unnecessary DNS queries to the gateway over the course of the week so I changed everything to refer to the individual docker container names since they're all on the same network. So recyclarr config went from http://nas to http://radarr.
replace_existing_custom_formats wasn't aware of this option, had to manually remove all the CFs by hand and resync.

After removing the CFs manually and doing the resync, did the warnings go away or did they remain?
When you changed from the network hostname to docker DNS names, I presume this resulted in the base_url values changing. If so, that would have generated a new cache, but the warnings would have still been there because the CFs already existed.
Either deleting all the CFs by hand or flipping replace_existing_custom_formats to true would have resolved the warnings. Please let me know!

I'm going to close this issue again. I did significant testing yesterday and I was not able to reproduce the issue.
@apapushoy I think it would have helped if you were more clear about whether or not these are current or past symptoms. I originally assumed it was the former. I'll watch for your answer to my last rely just in case, but I suspect it's the latter. If so, there was never a bug to begin with. You have a misunderstanding of the behavior. While I recognize is isn't as straightforward as I'd like it to be, you cannot swap your base_url and expect Recyclarr to know it's the same instance of Radarr. The upgrade guide for v5.0 pretty clearly states the workaround for this situation, and the YAML reference guide has documentation for replace_existing_custom_formats.
I'm not really sure what I could do to make this less confusing for people. Contributions are always welcome for the wiki if someone feels like there's an improvement to be made.
Thanks to everyone for providing logs and other information to help rule out any bugs.

After removing the CFs manually and doing the resync, did the warnings go away or did they remain?
When you changed from the network hostname to docker DNS names, I presume this resulted in the base_url values changing. If so, that would have generated a new cache, but the warnings would have still been there because the CFs already existed.
Either deleting all the CFs by hand or flipping replace_existing_custom_formats to true would have resolved the warnings. Please let me know!

This was a current issue at the time of posting but I didn’t want to leave it in that state so I took manual action. I had removed the CFs by hand, resynced and the warnings disappeared.

I'm going to close this issue again. I did significant testing yesterday and I was not able to reproduce the issue.
@apapushoy I think it would have helped if you were more clear about whether or not these are current or past symptoms. I originally assumed it was the former. I'll watch for your answer to my last reply just in case, but I suspect it's the latter. If so, there was never a bug to begin with. You have a misunderstanding of the behavior. While I recognize is isn't as straightforward as I'd like it to be, you cannot swap your base_url and expect Recyclarr to know it's the same instance of Radarr. The upgrade guide for v5.0 pretty clearly states the workaround for this situation, and the YAML reference guide has documentation for replace_existing_custom_formats.
I'm not really sure what I could do to make this less confusing for people. Certainly, if you don't read the documentation, that'll cause problems and I can't help you there. Contributions are always welcome for the wiki if someone feels like there's an improvement to be made.
Thanks to everyone for providing logs and other information to help rule out any bugs.

Thanks for the tip regarding the upgrade docs. I did run a migration command but hadn’t considered checking the wiki. Having so many containers, I just use Pullio to perform updates and that makes it easy to miss release-related instructions. At least with the main Starr apps there’s a release notes page that’s easy to check. Also the cron nature of recyclarr makes it easy to miss issues one keeps in mind to periodically check the logs, which I happened to do because of the host name change.

just use Pullio to perform updates and that makes it easy to miss release-related instructions

I recommend you use the major version number docker tag. In this case, it would be 5. It's a good balance between maintenance burden and keeping things working. I can pretty much guarantee you that every major upgrade will have breaking changes. Using the tag 5 will still get you automatic feature and bugfix releases but require manual change/review for breaking changes. Then all you need to do is head over to the Upgrade Guide section of the wiki and see what you need to do before changing it to 6.
Glad you got everything worked out.


[ISSUE] Update Keycloak values in the values file

Describe the issue:
With CP 8.2 release, we moved to a newer Keycloak chart however, the CP8 values file still uses the older format under identity.keycloak.
Actual behavior:
CP8 values file uses the older Keycloak chart syntax, e.g. identity.keycloak.auth.tls.enabled: true.
Expected behavior:
CP8 values file should use (even for comments) the newer Keycloak chart syntax, e.g. identity.keycloak.auth.tls: true.
Environment:
Please note: Without the following info, it's hard to resolve the issue and probably it will be closed.

Platform: Any
Helm CLI version: 3.9.3
Chart version: 8.2.2
Values file: N/A

Hi @aabouzaid I am interested in this issue and will try on my own to see if I could figure something

@aabouzaid
Did anyone fix this? I searched the repo for identity.keycloak.auth.tls.enabled but didn't find anything related, and according to https://artifacthub.io/packages/helm/bitnami/keycloak/12.2.0 it doesn't have auth.tls it uses tls directly and I see it implemented in this repo with no issue.

@mustafaelghrib it would be great if you worked on this issue :rocket:

Hi @aabouzaid I may need some guidance

@mustafaelghrib feel free to ask any question.

@aabouzaid Did anyone fix this? I searched the repo for identity.keycloak.auth.tls.enabled but didn't find anything related, and according to https://artifacthub.io/packages/helm/bitnami/keycloak/12.2.0 it doesn't have auth.tls it uses tls directly and I see it implemented in this repo with no issue.

@mustafaelghrib We are using Keycloak as a dependency for Identity. So all vars under the key identity.keycloak is passed to Keycloak 12.3.0 chart (you can see the chart version in Identity Chart.yaml file) (that also means you will not see that key in this repo).
What you mentioned is the actual issue we need to fix. We need to ensure that all vars in the Camunda repo are actually used in Keycloak chart.
So identity.keycloak.auth.tls.enabled is wrong, it should be identity.keycloak.tls.enabled because if we checked  Keycloak 12.3.0 chart values, you will not find it and we need to change that in Camunda's values file.
I hope that clarifies the issue we are trying to solve here. But always feel free to ask.

I have confirmed that all keycloak values seem to be updated based on the 12.3.0 chart.  Therefore this issue can be closed.


Debug with VSCode

Please describe your issue:
Unable to start/debug the app using VSCode.

Console output when you run electron-forge with the environment variable DEBUG=electron-forge:*. (Instructions on how to do so here. Please include the stack trace if one exists.
With below launch.json configuration,
"configurations": [
	{
	    "name": "Launch Program",
	    "type": "node",
	    "request": "launch",
	    "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron.cmd",
	    "program": "${workspaceRoot}/es6-init.js",
	    "cwd": "${workspaceRoot}"
	}
]

I m getting below error:
c:\eapp/node_modules/.bin/electron.cmd --debug-brk=21609 --nolazy es6-init.js

App threw an error duri
ng load
Error: Cannot fi
nd module 'c:\eapp\--debug-brk=21609'
    at Module._resolveFilename (module.js:455:15)
    at Function.Module._resolveFilename (c:\eapp\node_modules\electron-prebuilt-compile\node_modules\electron\dist\resources\electron.asar\common\reset-search-paths.js:35:12)

With below launch.json configuration,
"configurations": [
	{
	    "name": "Launch Program",
	    "type": "node",
	    "request": "launch",
	    "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron-forge.cmd",
	    "cwd": "${workspaceRoot}",
	    "args": [
	        "start"
	    ]
	}
]

I m getting below error:
c:\eapp/node_modules/.bin/electron-forge.cmd --debug-brk=41000 --nolazy start
√ Checking your System
  error: unknown option `--debug-brk'

What command line arguments are you passing?
Can be seen in above section
What does your config.forge data in package.json look like?
    "forge": {
        "make_targets": {
            "win32": [
                "squirrel"
            ],
            "darwin": [
                "zip"
            ],
            "linux": [
                "deb",
                "rpm"
            ]
        },
        "electronPackagerConfig": {
            "ignore": [
                "node_modules/sqlite3/build",
                "node_modules/sqlite3/deps",
                "node_modules/sqlite3/src"
            ]
        },
        "electronWinstallerConfig": {
            "name": "tixcart",
            "loadingGif": "./assets/img/install-splash.png",
            "iconUrl": "http://ticketmirchi.com/favicon.ico",
            "setupIcon": "./assets/img/icon.ico",
            "noMsi": true
        },
        "electronInstallerDebian": {},
        "electronInstallerRedhat": {}
    }

Can you please let me how to configure properly? Thanks.

error: unknown option `--debug-brk'

This is because electron-forge expects your command to be
electron-forge start --debug-brk=41000 --nolazy
You should go ask on the VS Code repository how to make the node debug arguments appear after your custom arguments (["start"])

I've tried the same, but still getting error (ran from cmd prompt):
C:\eapp>electron-forge start --debug-brk=41000
√ Checking your System
- Locating Application
  error: unknown option `--debug-brk'

By the way, thanks for the tip about VSCode. I got some clues from https://github.com/Microsoft/vscode/issues/16173.
Below is how I've configured VSCode:
"configurations": [
    {
        "name": "Launch Program",
        "type": "node",
        "request": "launch",
        "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron-forge.cmd",
        "port": 41000,
        "runtimeArgs": [
            "start",
            "--debug-brk=41000",
            "--nolazy"
        ],
        "cwd": "${workspaceRoot}"
    }
]

What version of electron forge are you using?  The latest version definitely shouldn't throw that error

Now I've switched to 2.2.0, and things are different now.
When I didn't pass `--debug-brk' switch, app is starting more than one electron process and app window is launching.
c:\eapp>node_modules\.bin\electron-forge.cmd start
√ Checking your System
√ Locating Application
√ Preparing native dependencies 1/1
√ Launching Application

But when I pass --debug-brk, only one electron process is starting and no visible window is launched. But the command o/p is same though.

I am unfamiliar with the fine art of attaching a debugger to the main Electron process and this isn't really an issue with electron-forge rather a usage question regarding Electron itself which can be summarised as.
"How can I debug the main process of Electron through VS Code?"
A good guide exists in the Electron repository.
https://github.com/electron/electron/blob/master/docs/tutorial/debugging-main-process-vscode.md
If that guide doesn't work you can ask for help in the Electron community or Slack Channel.

I think I m not clear enough. All the above output is from running the app from command line. No VSCode here :)

@manikantag Everything after the word start in that command is simply passed through to the electron command.
c:\eapp>node_modules\.bin\electron-forge.cmd start --debug-brk=41000

Is exactly the same as
c:\eapp>node_modules\.bin\electron.cmd . --debug-brk=41000

Therefore if that command doesn't do what you expect it to do or you can't figure out what the syntax is that you want, you need to ask over at the Electron community / slack areas.  The electron-forge issues section hopefully is to remain for forge specific issues 👍

Excuse me for bothering you. Still I think I m not clear.
As I mentioned, the same app is starting when I use electron-forge.cmd start, but not starting when I use electron-forge.cmd start --debug=5858 (this again from cmd, not from VSCode).
And, node_modules\.bin\electron . --debug=5858 is working perfectly.

But when I pass --debug-brk, only one electron process is starting and no visible window is launched.

This is to be expected, --debug-brk means "attach the debugger and pause execution on program entry", so the main process of your app is paused on startup waiting for you to step/continue execution via the debugger. When you do continue execution the main process will then go on and create all the other processes (renderer, GPU, etc.). If you don't want your app to pause on entry then use the --debug flag.
By the way, VSCode debug configurations have a boolean property called stopOnEntry that toggles this --debug-brk flag.

@enlight Yeah, I've figured it out. Now I m using 'Attach' mode to run the app. Somehow I m having issues with 'Launch' mode.

All this confusion is because even though I've mentioned --debug=41000, but still electron is starting 5858 as debug port and thus VSCode is not able to attach to the port=41000 specified in launch.json.
Below is the command line args of the app process tree.
Parent node process is having correct command line args: (--debug=41000)

Child node process is having incorrect command line args: (--debug 41000) (mind the missing =)

I m not sure why is like this :(


[Code Change Request] Codeunit 7322 "Create Inventory Pick/Movement" - procedure CreatePickOrMoveLine - Local to global

We need to call the procedure "CreatePickOrMoveLine" in Codeunit 7322 "Create Inventory Pick/Movement" from our own code.
Please change procedure from local to global.
OLD CODE:
local procedure CreatePickOrMoveLine(NewWhseActivLine: Record "Warehouse Activity Line"; var RemQtyToPickBase: Decimal; OutstandingQtyBase: Decimal; ReservationExists: Boolean)
NEW CODE:
procedure CreatePickOrMoveLine(NewWhseActivLine: Record "Warehouse Activity Line"; var RemQtyToPickBase: Decimal; OutstandingQtyBase: Decimal; ReservationExists: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


Validation: Investigate what "useful validation error message" means

From @andrewthecoder on February 3, 2015 15:11
Figure out what is or isn't required in the RDF schema and how to explain that to the user in words
Copied from original issue: HeriotWattMEng2015/ShExDemo#9

An easy first step would be to collapse absolute URLs back to their prefixes in the validation output


"Fix" scrollbars in Chrome 121+

"Fixed" the thicc blocky scrollbar (which isn't that ugly when set to thin, but still worse than wfrp4e's one).
What happens is that Chrome from 121 onward will flat out ignore all -webkit-scrollbar-* selectors if either scrollbar-color or scrollbar-width is set.
And unsetting it on specific selectors (like .app.window-app.sheet.wfrp4e) does not work, it must be removed from :root (where Foundry sets it).
However, this means that some other apps that do not use Warhammer's scrollbars will revert now to default look... and that would probably mean that either Warhammer scrollbar should be defined on :root, or the scrollbar-color and scrollbar-width would need to be set manually on specific apps.
One app I know reverts to default browser scrollbar which this change is File Picker.

Yes, I hate hacky ways of fighting with upstream CSS.
Yes, I hate when browsers do drastic changes like that...
"Source":
https://stackoverflow.com/a/77884484
PS: I do not expect you to outright merge this PR, mostly putting it here as an example and explanation, at least to the extend I understand the matter. Maybe there is better way that I yet fail to see.

I said unset doesn't work on specific selectors. But turns out initial !important does. So for example:
.app.window-app.sheet.wfrp4e.actor {
    scrollbar-color: initial !important;
    scrollbar-width: initial !important;
}

helps too. A little less hacky than the :root with unset


How to publish AOT?

If I publish the sample app, I still get a managed .NET dll file with an executable host file and all the .NET runtime dll files. But when I publish a console project with AOT I get a single unmanaged executable. This is what I've expected for Winforms as well.
I used this command dotnet publish -r win-x64 and then went to the publish folder.

Question. Are you have .NET 7 SDK installed? I have 7.0.100-rc.2.22452.3 (and previously version was working fine) and everything was working. Are you have either <PublishAot>true</PublishAot> or <PackageReference Include="Microsoft.DotNet.ILCompiler" Version="7.0.0-*" /> (not needed in .NET 7) in your project file?

My SDK is 6.0.400 and I'm building the winforms sample project, <PublishAot>true</PublishAot> was missing, <PackageReference Include="Microsoft.DotNet.ILCompiler" Version="7.0.0-*" /> not.
I've now added <PublishAot>true</PublishAot> and published again but still no AOT.

I think this is your answer. https://github.com/dotnet/runtime/issues/61231#issuecomment-1235385283 or maybe slightly earlier for context. For now .NET 6 SDK a bit broken. You can either use specific version of ILCompiler or wait for NET 6 SDK to land fix, or install NET 7 preview

How can I use a specific version of the ILCompiler?

Try
<PackageReference Include="Microsoft.DotNet.ILCompiler" Version="7.0.0-preview.6.22324.4" />

With this I get: error : The ResolvedILCompilerPack ItemGroup is required for target ImportRuntimeIlcPackageTarget

NativeAOT does not support .NET 6, so I probably would limit my attempts here too. Let me know if you still need this.

Yeah it works fine with .NET 7. But it is normal that the output files are extremely huge in release mode? And that there are still many other files in the output directory?
For a console project a get a rather small app with only one executable.

native dll which is in the output dir you most likely can ignore. They are coming from WPF and that's SDK issue. Probbaly nobody bother with this yet.  Not sure what can be done to this, but this is mostly related to WinForms code.

Yeah I was talking about all of these:
clrjit.dll
D3DCompiler_47_cor3.dll
mscordbi.dll
vcruntime140_cor3.dll

and so on. There are 21 additional files with a total size of 21mb.

Not quite clear why do you have 21 additional files. If they are from your external libs, probably you need them.
For me, tipical WinForms App + NativeAOT uses only

D3DCompiler_47_cor3.dll
PenImc_cor3.dll
PresentationNative_cor3.dll
vcruntime140_cor3.dll
wpfgfx_cor3.dll
Size of 8MB. You can safely delete these files, if you don't have some WPF dependency which probably anyway would not work.

Other files, I never seen them. I assume we did not count PDB files, they are not required obviously.

I dont count PDB file. It is a simple "hello world" Winforms app with no other external lib / dependency than WinFormsComInterop. Deleting all code reduces it to 17 additiona files.
<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>WinExe</OutputType>
    <TargetFramework>net7.0-windows</TargetFramework>
    <Nullable>enable</Nullable>
    <UseWindowsForms>true</UseWindowsForms>
    <ImplicitUsings>enable</ImplicitUsings>
    <PlatformTarget>x64</PlatformTarget>
    <AllowUnsafeBlocks>true</AllowUnsafeBlocks>
    <PublishAot>true</PublishAot>
    <_SuppressWinFormsTrimError>true</_SuppressWinFormsTrimError>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="WinFormsComInterop" Version="0.3.2" />
  </ItemGroup>

</Project>

Project file:
WinFormsNativeAOTTest.zip

What command do you use for publish? dotnet publish. Also I belive PlatformTarget is redundant.

Can you run just dotnet publish without additional switched, and open bin\Debug\net7.0-windows\win-x64\publish\ folder?

Doesn't matter, I published through VS but using dotnet publish without any additional parameter generates the same output:
\bin\Debug\net7.0-windows\win-x64\publish:

do you have <PublishAot>true</PublishAot> inside your csproj?

I've attached the project file above, yes I have.

I unpack application to C:\Users\User\Downloads\WinFormsNativeAOTTest

Run dotnet publish

Now I have following files

If you have something else, you some issues in your setup. Maybe you have some Directory.Build.props above which annulls PublishAot or something else. Files which you are show indicates that you publish as regular self-contained app, not as NativeAOT application

hey bro. i can build winform native oat but i click button and it notifi errors
See the end of this message for details on invoking
just-in-time (JIT) debugging instead of this dialog box.
************** Exception Text **************
System.NullReferenceException: Object reference not set to an instance of an object.
at getcpu.Form1.checkactive() + 0x19d
at System.Windows.Forms.Button.OnClick(EventArgs) + 0xcf
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs) + 0xb1
at System.Windows.Forms.Control.WmMouseUp(Message&, MouseButtons, Int32) + 0x268
at System.Windows.Forms.Control.WndProc(Message&) + 0x670
at System.Windows.Forms.ButtonBase.WndProc(Message&) + 0x161
at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Interop.User32.WM msg, IntPtr wparam, IntPtr lparam) + 0x70
************** Loaded Assemblies **************
System.Private.Xml
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Diagnostics.TraceSource
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Security.Principal.Windows
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Runtime.Numerics
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Drawing.Primitives
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.WebHeaderCollection
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Drawing.Common
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Design
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Text.Encoding.CodePages
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Runtime.InteropServices
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.IO.Compression.Brotli
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Diagnostics.FileVersionInfo
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.Primitives
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Windows.Forms.Primitives
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.Sockets
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Runtime.Serialization.Formatters
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Drawing.Design
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.ComponentModel
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Security.Cryptography
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.Security
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Collections.NonGeneric
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
WinFormsComInterop
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.WebClient
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Collections.Specialized
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Private.Uri
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
Accessibility
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Diagnostics.DiagnosticSource
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Reflection.Metadata
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
Microsoft.Win32.SystemEvents
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.ObjectModel
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Private.CoreLib
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Threading
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.ComponentModel.EventBasedAsync
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Collections
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.IO.Compression
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
Microsoft.Win32.Registry
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Collections.Concurrent
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Windows.Forms.Design
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.NetworkInformation
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.ServicePoint
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.Requests
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Security.Claims
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Security.Cryptography.Algorithms
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.ComponentModel.TypeConverter
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Linq
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
form
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Threading.Channels
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Drawing
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Windows.Forms
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.IO.MemoryMappedFiles
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Private.TypeLoader
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.ComponentModel.Primitives
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.Quic
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Collections.Immutable
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Management
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Text.RegularExpressions
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.NameResolution
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Net.Http
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
System.Private.Reflection.Execution
Assembly Version: <IP_ADDRESS>
Win32 Version: n/a
CodeBase:
************** JIT Debugging **************

@NCLnclNCL can you show what's in your Form1.checkactive function? Can you confirm that this is name of event handler for button click?

@NCLnclNCL can you show what's in your Form1.checkactive function? Can you confirm that this is name of event handler for button click?
hey bro, i know .net framework has .net native and it supports compiling for x86, why is it difficult to compile x86 for native aot at .net core


PnP Site Proviosning Exclude Specific Site Fields

Hi,
While creating a site proviosning template, we are not able to exclude specific site columns. Is there any command available to exclude them the same way we can exclude for content types.

Hi,
Unfortunately, as far as I know, we don't have such a capability. You can always create a custom extension to do that, if needed. Thanks.


Using Buffer without new will soon stop working after Node 7?

(node:30742) DeprecationWarning: Using Buffer without new will soon stop working. Use new Buffer(), or preferably Buffer.from(), Buffer.allocUnsafe() or Buffer.alloc() instead.
Maybe u should change the use of Buffer

I added a pull request for this. Just a few 'new'. It seems to work fine.

For future references, that pull request is #35.

#37

As @niceue already stated, this error is still there and could be easily circumvented as described above.
When using ncc to "compile" the app then this error
[DEP0005] DeprecationWarning: Buffer() is deprecated due to ... is spit out.
Thoughts?


Feature request: Screensaver Choose album

I was wondering if a feature could possibly be implemented in which you can choose to only have the screensaver slideshow use pictures from a certain album you choose.

Switching the linked user will still show all the albums for the current linked user. It would be great if user can specify the album for the screensaver. Thank your for your effort and the app is wonderful!

You can already do this, see my post above yours.  Hit your right arrow to select the album.

Thanks! Finally got it 🙏
Rakesh
On Tue, Jun 4, 2019 at 2:29 PM Chris Taylor<EMAIL_ADDRESS>wrote:

You can already do this, see my post above yours. Hit your right arrow to
select the album.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/chtaylo2/Roku-GooglePhotos/issues/178?email_source=notifications&email_token=AICWFP7OO6EFBXLLPWTLKWDPY27AJA5CNFSM4GSQA2D2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODW5TX2Q#issuecomment-498809834,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AICWFP2YFY7U4AYAMIQYB33PY27AJANCNFSM4GSQA2DQ
.

--
Regards,
Rakesh Raj Shrestha
<EMAIL_ADDRESS>(641) 472-7000 ext. 3435
Instructor of Computer Science
Maharishi University of Management
http://mscs.mum.edu

Mine doesn't have:  Under Screensaver > Custom Settings > Select Linked User > Directions on Screen.
Mine only has two options:  Browse screensavers or Change wait time
What am I doing wrong?

@Sarahholt14 I see this as well. Keep going to the right.
Settings > Screensaver > Browse screensavers (you're here in your photo) > PhotoView > Change screensaver settings > Select Linked User and Albums > (your account/email) > (your albums)

Yay!!!  Thank you so much!  It worked!  It seems to always be pulling from the first 1000 photos instead of the 2nd 1000 photos in my screensaver folder, but it sounds like there's nothing I can do about that, unfortunately.  Oh well....this is better than seeing random photos that I don't care to see on my screensaver!  Thanks for your help!