Issue with python 3.12.3 - ModuleNotFoundError: No module named 'distutils'

Running python -m pip install git+https://github.com/MinshuG/pyUE4Parse.git results in this:
ModuleNotFoundError: No module named 'distutils'
It appears that python 3.12 removed distutils, see stackoverflow:
https://stackoverflow.com/questions/77247893/modulenotfounderror-no-module-named-distutils-in-python-3-12
pip install --upgrade setuptools doesn't help either.
How to install it on python 3.12?

OK this is weird but this allowed me to build. You may re-check allowed toml properties because it gave me hell.
diff --git a/pyproject.toml b/pyproject.toml
index 8b61abb..0c48953 100644
--- a/pyproject.toml
+++ b/pyproject.toml
@@ -1,22 +1,13 @@
 [project]
 name = "UE4Parse"
 description = "ue4/5 asset parser"
-authors = [
-    "MinshuG"
-]
-license = "MIT"
 readme = "README.md"
-python = "^3.8"
-homepage = "https://github.com/MinshuG/pyUE4Parse"
-repository = "https://github.com/MinshuG/pyUE4Parse"
-
 keywords = ["UE4", "UE5", "Unreal Engine"]
-
+version="1.0.0"
 classifiers = [
     "Programming Language :: Python :: 3",
     'License :: OSI Approved :: MIT License'
 ]

 [build-system]
-requires = ["setuptools~=56.0.0", "Cython~=3.0a5"]
-build-backend = "setuptools.build_meta"
+requires = ["setuptools>=30.3.0", "Cython~=3.0a5"]
diff --git a/requirements.txt b/requirements.txt
index 0696067..758eed6 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,3 +1,3 @@
 Cython~=3.0a5
-setuptools~=56.0.0
+setuptools>=30.3.0
 Pillow
diff --git a/setup.py b/setup.py
index 879a556..712bfc5 100644
--- a/setup.py
+++ b/setup.py
@@ -1,7 +1,7 @@
 from Cython.Build import cythonize
 from setuptools import find_packages
-from distutils.core import setup
-from distutils.extension import Extension
+from setuptools import setup
+from setuptools.extension import Extension
 import pathlib

 HERE = pathlib.Path(__file__).parent

With the changes above, it seems it doesn't run dependencies so I had to install them in the command line, like so:
pip install pycryptodome lz4 pyUsmap pillow quicktex aes

And then install the module from the repo directory:
pip install .

I wasn't able to install astc_decomp (looks like it suffers the same 3.12 issue) but I didn't really need it.
I use it in my project, https://github.com/joric/supraland

try now it should work

Looks like 3.12 is fixed. My thing with coordinates stays, but it's another issue I have to investigate.
You may ditch the [tex] thing though, it doesn't seem necessary, astc_decomp_faster worked.
Tried with pip install .[tex] on 3.12, no errors.

@joric try:
pip install -e "UE4Parse[tex] @ git+https://github.com/MinshuG/pyUE4Parse.git"

pip install -e "UE4Parse[tex] @ git+https://github.com/MinshuG/pyUE4Parse.git"
ERROR: UE4Parse[tex] @ git+https://github.com/MinshuG/pyUE4Parse.git is not a valid editable requirement. It should either be a path to a local project or a VCS URL (beginning with bzr+http, bzr+https, bzr+ssh, bzr+sftp, bzr+ftp, bzr+lp, bzr+file, git+http, git+https, git+ssh, git+git, git+file, hg+file, hg+http, hg+https, hg+ssh, hg+static-http, svn+ssh, svn+http, svn+https, svn+svn, svn+file).

@MinshuG the [tex] part in the readme should be
pip install UE4Parse[tex]@git+https://github.com/MinshuG/pyUE4Parse.git // with texture decoders

If possible can you make a PR?

I can fix the readme for starters https://github.com/MinshuG/pyUE4Parse/pull/25


python message.dead_letter(description) does not add description to the dead lettered message

If you do: message.dead_letter(description="SETTING A reason")
That description cannot be found in the dead letter properties:
for message in messages:        # pylint: disable=not-an-iterable
print(message)
print(message.header)
print(message.properties)
print(message.user_properties)
print(message.annotations)

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

ID: 47bc6b40-39cd-eb95-1911-ddff96dda210
Version Independent ID: d91a6110-e9c0-3a34-a321-6850778baaef
Content: Quickstart: Use Azure Service Bus queues with Python
Content Source: articles/service-bus-messaging/service-bus-python-how-to-use-queues.md
Service: service-bus-messaging
GitHub Login: @axisc
Microsoft Alias: aschhab

@alexespencer Thank you for your feedback! We will review and update as appropriate.

@alexespencer Looks like this is an issue in the underlying amqp library - Azure/azure-uamqp-python#155 - which is documented in the code as well.
It is best to subscribe to the above issue for updates on it and also to have more insightful discussion on the same.
Since there is no doc update required here, we will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.

Thanks Pramod - I've subscribed to that issue.


Is there an fontawesome-markers support for fontawesome 4.3.0

Hi,
first of all thank you for that magical tool/modue, that runs perfectly.
As far as I know, currently only fonatawesome 4.2.0 is supported. Is there a plan to support the current version of fontawesome (4.3.x)?
Thank you,
B0rner

See #6

Oh. looks good. This means I will able to create the icons for every new version? Like 4.4.0, which is current release?

Have published support for fontawesome markes v4.3 v4.4 v4.5 v4.6 and v4.6.1 in 1fa02d0807668416feabba88dd9e35824fd12cfa


New docker stuff

This change is

Reviewed 23 of 23 files at r1, 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Update opentelemetry-sdk-testing to 1.35.0

About this PR
📦 Updates io.opentelemetry:opentelemetry-sdk-testing from 1.11.0 to 1.35.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.opentelemetry", artifactId = "opentelemetry-sdk-testing" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "io.opentelemetry", artifactId = "opentelemetry-sdk-testing" }
}]

labels: test-library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #652.


Thank you!

I just want to say a huge thank you for the work you've put into this component, it's incredibly impressive. Keep up the great work and thanks again!!

Hey alexcroox,
Thank you so much.

Hey alexcroox,
Thank you so much.


fix(core) Root hierarchy should have proper inheritance

Signed-off-by: Jerome Simeon<EMAIL_ADDRESS>Issue #228
Changes

squeeze core classes Event Transaction Asset Participant back in the type hierarchy
fixes tests
add missing timestamp to Event and Transaction
strangely sometimes we had identifiers generated even when not declared, maybe this was still what we wanted but I was recalling the opposite
fixes an unrelated bug in isExplicitlyIdentified API call sometimes returning undefined

Flags

This needs quite a bit more testing especially of the base types and new type hierarchy
I'm quite confused about timestamp why are event an transaction have a timestamp but the other classes do not? what's the criteria?
Somewhat mixed confidence that this is really what we intended to do (but I believe it's at least closer to that goal)

@mttrbrts : this is a good test of the new build script, with successful linting and unit testing but regression on coverage.


Added missing no-switch-case-fall-through config

Added missing no-switch-case-fall-through rule configuration to the list of all configuration rules
PR checklist

[ ] Addresses an existing issue: #0000
[ ] New feature, bugfix, or enhancement

[ ] Includes tests

[x] Documentation update

Overview of change:
Is there anything you'd like reviewers to focus on?

CHANGELOG.md entry:

Thanks for your interest in palantir/tslint, @wvankuipers! Before we can accept your pull request, you need to sign our contributor license agreement - just visit https://cla.palantir.com/ and follow the instructions. Once you sign, I'll automatically update this pull request.

I think technically its not missing, as it seems to have been intentionally placed not in the list (see line 279). Curious as to why this was the case and doing some investigating to try to find out what the reasoning was.

Closing this PR as non-actionable per johnwiseheart's comment. @wvankuipers if you're interested in putting the rule back into the config, we can discuss in a separate issue.


Suggestion: Improve example documentation generation

Currently I see that the examples directory has to be manually synced between the python examples and the markdown ones. Could we somehow have tooling that auto-generates the markdown examples from python ones? This would help keep the two directories in sync and potentially improve the contribution experience.

That is correct @samj1912 While I think there are solutions to this I fear we might have a hard time doing the translation to an RTD example 100% correctly, all the time, particularly if contributors add explanations as comments around the example code. What if, instead of going from Python to MD we go from MD to Python? That is, we first switch all examples to Markdown exclusively (delete the examples folder). Then, we add a script that parses out the code content between backtick characters, as others have tried? I do worry about user confusion, though... perhaps documentation an examples/README can alleviate the confusion? Thoughts?

MD to Python also sgtm. As long as we have some way to generate one from the other.


Update config customization notebook

What should we add?
[BUG]
In the Config Customization notebook, ct.lattice decorator is called with an unnecessary parenthesis and get_metadata is called without any arguments.

Either the notebook linked is incorrect or has been updated since I cannot find references of both ct.lattice OR get_metadata. So, this issue can be closed perhaps?


feat: timestamp future check

Audit specification:
-Entry too far in the future DOS attack

Disable the possibility to publish to far in the future. I chose a forward buffer of 10s, but to be fair, it will never reach this far (logically)


Special formatting for UI docs in GD

@AndrewJakubowicz yes, Also ui.track. Plus we were going to add more UI methods. Currently we put them in methods so this way.


Get state store from Materialized

So I have this use case I'm not too sure how to address:
val stateStore = "store"
val materialized = Materialized.as[String, Long, ByteArrayKeyValueStore](stateStore)
...
table1.join(table2, materialized)((a, b) => a + b)

val testDriver = createTestDriver(builder)
...
testDriver.getKeyValueStore[String, Long](stateStore).get("1") shouldBe 2

To me it sounds like we should be able to get the store from/with the Materialized object. It's much better typed than a String:
val materialized = Materialized.as[String, Long, ByteArrayKeyValueStore](stateStore)
...
table1.join(table2, materialized)((a, b) => a + b)

val testDriver = createTestDriver(builder)
...
testDriver.getKeyValueStore(materialized).get("1") shouldBe 2

I'm not sure if that's the way to do it exactly so feel free to comment.

Retest this

Retest this, please

I don't think we can fix this -- note that TopologyTestDriver does not know anything about the DSL, but only about a Topology. The DSL is an independent layer on top that produces a Topology, and Materialize is a DSL object.
It's good design to keep both layers independent, and the lower level Topology layer should not be "polluted" with DSL concept.
Closing this stale PR.


Support SubjectName/Issuer (SNI) certificate authentication for Service Principals

Moving this to the Iron semester

Related: https://github.com/AzureAD/microsoft-authentication-library-for-python/issues/60

Completed by https://github.com/Azure/azure-sdk-for-net/pull/14636


ome-dundeeomero and nightshade-web to 5.3.3

University of Dundee OMERO server ecosystem, known as "Nightshade", upgraded to 5.3.3, with the latest versions of the OMERO.web apps distributed via pypi.
Internal OME Trello card: https://trello.com/c/kW9gdajk/21-production-server-upgrades

Flags for upgrades added via the ansible-playbook commands - see the text files in this comment for usage, and output.
Run against decoupled OMERO server ome-dundeeomero:

check mode: ansible_run-533_upgrade-CHECK-ome-dundeeomero_20170628-175128Z.txt
live run: ansible_run-533_upgrade-ome-dundeeomero_20170628-175447Z.txt

Run against decoupled webserver ns-web:

check mode (missing omero_web_upgrade extra var): ansible_run-533_upgrade-CHECK-nightshade-web_20170628-175908Z.txt
with --extra-vars upgrade_webapps=True: ansible_run-533_upgrade-nightshade-web_20170628-180122Z.txt
with --extra-vars omero_web_upgrade=True: ansible_run-533_upgrade-nightshade-web_20170628-180434Z.txt


Property fields of type Option are not mandatory

Problem
I want to use Option as a property field.
I want to enforce users of my component provide me with that property always, which can be None or Some(something) but must be populated.
According to https://yew.rs/docs/concepts/function-components/properties#derive-macro-field-attributes:
When deriving Properties all fields are required by default.

Steps To Reproduce
Steps to reproduce the behavior:

Write the following code:

#[derive(Properties, PartialEq)]
pub struct Props {
    pub mandatory: Option<String>,
}

#[function_component]
fn HelloWorld(_props: &Props) -> Html {
    html! {}
}

// Then supply the prop
#[function_component]
fn App() -> Html {
    html! {<HelloWorld/>}
}

Expected behavior
Since all fields are mandatory and I'm not passing the mandatory field of property, I expect this code to not compile.
I suggest either the behaviour is changed so Option is also mandatory (as stated in the docs). People not needing this can always use #[prop_or_default]. Otherwise at least update the docs to reflect this special case for Option fields
Environment:

Yew version: 0.20
Rust version: latest stable

Questionnaire

[X] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

...if this is confirmed as a bug and somebody points me in the right direction, I'd be happy to contribute with a PR

I feel the current behaviour is more desirable than requiring user to write a prop when the prop is Option<T>.
Currently a prop: Option<T> accepts the following for a prop:

(nothing) -> prop: None

prop={val} -> prop: Some(val)

prop={Some(val)} -> prop: Some(val)

prop={None} -> prop: None

Requiring a prop to present only takes away 1 but not 2, that does not sound right to me.
If we take away both 1 and 2, then it becomes quite inconvenient to force users to write.
It is not possible to take away both 1 and 2 based on whether #[prop_or_default] is present as 2 is provided via impl IntoPropValue<Option<T>> for T blanket implementation.
I think this is also consistent with the behaviour of HTML Elements, where omitted attributes are treated as null if you call Element.getAttribute("prop").
However, I do agree that the documentation should be adjusted to reflect this behaviour.

thanks.
I'm not sure I understand what you mean by "Requiring a prop to present only takes away 1 but not 2".
Option 1 is not providing the property and (unless prop_or_default is used) according to the documentation all fields are required. So, not taking away 2 is not an issue. Taking away 1 but not 2 is absolutely fine.
Regarding forcing users, whoever develops de component is responsible for making it convenient or not to the component users. There is already a way to "use default if not provided"; prop_or_default.
If I search for code containing #[prop_or_default] with fields being Option, I get several results: https://github.com/search?q=repo%3Ayewstack%2Fyew %23[prop_or_default]&type=code
(I also founds occurrences in my code)
So, my point is, it looks like this behavior of needing properties even if they are Option was already there at some point, otherwise why would we have annotated so many Option fields with #[prop_or_default] when it's not needed?
all in all, I'd suggest we treat all types of fields the same as there already is a documented (and used) way of "using default if not provided".

... and after re-reading your message again I think I see what you meant about option 2 doing the "val -> Some(val)" conversion behind the scenes.
I have no strong opinion there on whether that is good (convenient) or bad (treating a certain type different to others), as the main driver for me is to have a way to have mandatory properties which happen to be of type Option

in case this is of any value, I was curious to find out why was I using #[prop_or_default] in for Options so I tested with yew 0.20, 0.19, 0.18 and 0.17.
On 0.17 this was failing at compile time:
error[E0599]: no method named `build` found for struct `app::PropsBuilder<app::PropsBuilderStep_missing_required_prop_mandatory>` in the current scope
  --> src/app.rs:49:9
   |
3  |   #[derive(Properties, PartialEq, Clone)]
   |            ---------- method `build` not found for this struct
...
49 | /         html! {
50 | |             <Child />
51 | |         }
   | |         ^
   | |_________|
   |           method not found in `PropsBuilder<PropsBuilderStep_missing_required_prop_mandatory>`
   |
   = note: the method was found for
           - `app::PropsBuilder<app::PropsBuilderStep_build>`
   = note: this error originates in the macro `proc_macro_call_0` which comes from the expansion of the macro `html` (in Nightly builds, run with -Z macro-backtrace for more info)

@futursolo I noticed a proposal tag change, I personally do in fact consider it a bug, or at least the fact that it leads to bugs for properties that are supposed to always get an Option value, yet Yew currently allows you to simply forget to pass it.

Requiring a prop to present only takes away 1 but not 2, that does not sound right to me.

It sounds right to us though. This is simply about not providing the prop at all. If an equivalent syntactic prop={}, prop={ () } or prop={ ! } could be made instead for your odd behavior equating "no value typed out in code means none variant", this could be a middle-ground solution. I think not requiring Some is something that Rust should also do, by doing "either T or None::<T>".

I think this is also consistent with the behaviour of HTML Elements, where omitted attributes are treated as null

This is not a good argument. That is JS, this is Rust. null is not Option::None, there are no nulls in Rust. You do not call value_opt.do_something(), you have to explicitly check the value's presence (e.g. value_opt.unwrap().do_something()), and this is one of great things of having a stronger type system compared to whatever JS has. Also, props are not attributes, we consider attributes optional strings of elements, but we consider props actual in-code values of strong types.

@futursolo I noticed a proposal tag change, I personally do in fact consider it a bug, or at least the fact that it leads to bugs for properties that are supposed to always get an Option value, yet Yew currently allows you to simply forget to pass it.

I removed the bug label because this behaviour is intentionally introduced, although the documentation didn't reflect this special behaviour for Option<_>. This is not an indication of the current behaviour is better than the one purposed.
This issue is proposing a behaviour different than what this macro is currently trying to do.

a middle-ground solution

I do not think these solutions are better than writing prop={None}, if you have to explicit say something.
They are not much shorter or easier to understand than assigning None.

That is JS, this is Rust.

This behaviour can also be observed in Rust.
web_sys::Element::get_attribute also returns None when the attribute does not present.

You do not call value_opt.do_something(), you have to explicitly check the value's presence (e.g. value_opt.unwrap().do_something()), and this is one of great things of having a stronger type system compared to whatever JS has.

Since there is no compile stage in ordinary JavaScript, you cannot complain about JavaScript does not give you compile time errors. JavaScript is horrible in many ways, but this is not one of them.

instead for your odd behavior equating "no value typed out in code means none variant",

I think this behaviour is consistent with HTML Elements, if you want an attribute to be set, then it is present, if you want it to be null-ish, then do not have it present. You never pass an explicit value to an attribute to represent a null / None / nil-ish value.
If I have to say, I would argue explicit passing None here is the odder behaviour of the 2.

If/when I develop a component who's property field is Option<something> and the property is not fundamental to my component (only I as the developer of the component can tell if this option is required or not), I can happily annotate with prop_or_default and my users can pass None or not pass at all (but again, the component developer, not the framework, made that clear and documented choice).
If/when I develop a component who's property field is Option<something> and the property is fundamental to my component, this (bug/feature) is the only way I can force my users to pass that property (even if they pass None, which is just as valid as any other value). (I can also define my own Option-like enum which is less than ideal)
I think we're really mixing passing None with not passing something, and this may be ok in some scenarios but I don't think the framework should be opinionated here (and it already provides prop_or_default in case I want to bypass the 'all fields are mandatory' rule).
If there was a #[mandatory_prop] I could use here I'd use that, as again the component developer can choose what semantics to give to the property fields.
all in all, it does look like a special/arbitrary case when the possibility of transform behavior (prop_or_default) are already there.
The "magic" converting something={value} to something={Some(value)} is different in my opinion; if the property is Option<something> and I pass something, without this "magic" things would not even compile. So, the framework is making something compile which would otherwise not.
The "magic" converting not passing a property to passing a something={None}, is assuming the developer intended to pass None, which may or may not be the case.

if you have to explicit say something

You have to. Missing #[prop_or...] means there is no "or", there has to be a prop. You have to type out the name, at least in some way, to signal that the prop exists. The fix was meant to be a nice fix for Some, not a bug for None.

when the attribute does not present

consistent with HTML Elements, if you want an attribute

Attributes, attributes, attributes. I said that props are not attributes. An equivalent for attributes would be a #[prop_or_default], since the agreed-upon behavior for attributes missing is None; this is not the case for the usual properly-typed props.

there is no compile stage in ordinary JavaScript

I don't think I mentioned compile-time? I said it was about types, and types are more-or-less checked in JS at runtime. I did in fact use Option in JS for my projects, and the proposal for JS pattern matching does mention using an Option equivalent.

thanks. I'll give it a try; if anybody is already doing this or has some hints on where to look at please let me know to avoid reinventing the wheel.

@horacimacias https://github.com/yewstack/yew/blob/73f4bb91cfa7e631c5a84cc9e4bab9f6fba075bf/packages/yew-macro/src/derive_props/field.rs#L19-L20 i think related to this, they have a separate thing for Option

As far as I remember, Yew doesn't guarantee backwards-compatibility until version 1.0, so we could just get rid of the special case, or we can add a #[required] attribute to the derive(Properties) macro, which would override the special treatment of the Option type when applied to a field of type Option, which approach would be better?

@schvv31n I'm certain that adding #[required] would not only make you forget to use the prop whenever the attribute is missing, you would actually also forget to write #[required] in your component's code.
The whole Rust language is built upon making strict limitations to ensure bug-free experience, and only then opening it up bit by bit once the unrestricting logic can be figured out - see Non-Lexical Lifetimes. This #[required] situation would be akin to mut vs const, there it is wanted that users opt-in to mutability with the mut, rather than opting-out of it with a const. In our case the None path was opened because of a somewhat hasty attempt to unrestrict Some, which violates this philosophy of minimal opening that I observed. I consider this a bug (an undocumented change - I can consider this situation undefined behavior of sorts), thus no backwards compatibility should be preserved.
If you get rid of special case, try ensuring that Some::<T> still can be pulled from T. I'm not even certain I ever used it, but it does seem a reasonable QoL feature.

while #[required] might help my specific use case (property fields of type Option be mandatory), I think it's adding a corner case of a corner case. Unless there is a technical reason for this, I'd stick to the existing prop_or_* annotations.
Comparing:

all property fields are mandatory, except if prop_or_* is used.
all property fields are mandatory, except if prop_or_* is used, except if field is Option which is then NOT mandatory and can be made so by using #[required]

I'd say option 1 is clear, elegant, concise. Good. option 2 sounds like a clumsy workarround.


Detail view

Finished with this one for now, moving to the EditView. Will be back to add tomato timer!


Update keep-common dependency to pretty-print diagnostics

The reference to keep-common has been updated to a branch that has improvement to pretty print diagnostics JSON.
See: https://github.com/keep-network/keep-common/pull/107
When the PR in keep-common is merged to main we need to update the reference in go.mod here.

@nkuba, fyi, https://github.com/keep-network/keep-common/pull/107 is merged now

Closing this PR as the dependency was already updated in the meantime.


bug with round brackets

my javascript:
var length = data.length - (positionOne + someOne); // example 96 - (34 + 32) = 30

converted coffeescript:
 length = data.length - positionOne + someOne

anybody here?

hey there! I'm here, but I'm a bit preoccupied to be making patches at the moment.
the a - (b - c) is handled correctly, but the a - (b + c) isn't — PR's are welcome!

Okay, v2.0.4 is out to fix this. http://js2.coffee

@rstacruz Thank you so much!


Add return value if profile was transformed

Describe your changes
Add boolean information if profile was transformed.
Issue ticket number and link
https://github.com/EVerest/libocpp/issues/908
Checklist before requesting a review

[x] I have performed a self-review of my code
[x] I have made corresponding changes to the documentation
[ ] If OCPP 2.0.1: I have updated the OCPP 2.0.1 status document
[x] I read the contribution documentation and made sure that my changes meet its requirements

Closing this as a result of the discussion in the last cloud WG call, because with these changes profileTransformed is not on the correct level, since conversions are implemented per ChargingSchedulePeriod and not per ChargingProfile.
We can continue to discuss solutions for this within https://github.com/EVerest/libocpp/issues/908


Billy url

issue #4
(rather than merge into master)

every time that I refresh the page i have to setup my wallet again although the ks is set in local storage.

it also breaks the back button on the transfer app

@muxe is incorporating this merge into branch MaxDeepLink


[veeam-backup-and-replication] Add automation

Relates to https://github.com/endoflife-date/endoflife.date/pull/4418 and https://github.com/endoflife-date/endoflife.date/pull/4493.

Only expected updates, merging.


Update convert_and_optimize_asr.py

Update convert_and_optimize_asr.py with quantization code of whisper model

Thanks, @zhuo-yoyowz. Did you test it in the app? Will it work with Optimum Intel (app uses HF interface)?
Is it possible to quantize it using OVQuantizer from Optimum Intel?

Hi Adrian, I've tested it in app.py. Without changing any code in app.py, the current pipeline could also load and compile the quantized model successfully. Haven't done testing the OVQuantizer from Optimum Intel. I'm still a bit uncertain about how to se the configuration for setting up the calibration dataset and defining the preprocess function.

Good job!


[node-agent] Delete systemd unit files and drop-ins only if the unit has been created by node-agent

How to categorize this PR?

/area robustness|
/kind bug
What this PR does / why we need it:
Currently gardener-node-agent always deletes a systemd unit file and the drop-in folder when the unit was deleted from OperatingSystemConfig.
While this correct for units which have been created by gardener-node-agent, it incorrectly deletes *.service file and the drop-in folder for units created by other parties (like default OS units). This can be the case if we use the unit to add additional drop-ins or in order to change the start command.
With this PR, unit file and drop-in folder are deleted only if Unit.Content of the old unit is not nil.
Otherwise, it keeps the unit file and deletes the drop-in files only.
Which issue(s) this PR fixes:
Fixes #10809
Special notes for your reviewer:
/cc @rfranzke
Release note:

`gardener-node-agent` deletes unit files and drop-ins only if it created them previously.

@maboehm Since you recently looked into a similar topic, do you want to take a look at this one?


Chart.js

Expected Behavior

Current Behavior

Possible Solution

Steps to Reproduce (for bugs)

Context

Environment

Chart.js version:
Browser name and version:
Link to your project:

Closing as empty


fix: use build system to pre-render YAML anchors

Closes #3
@mamachanko I'd appreciate if you could give those a look, I compared your pre-rendered, anchor-less files with dyff, there shouldn't be any differences.

I may have led you down the wrong path. It turns out that https://github.com/catppuccin/k9s/issues/3 is not related to anchors at all, but k9s expects skins to have .yaml as a file extension and not .yml. The documentation on k9s#skins isn't very forthcoming about this limitation.
In the end it makes sense that anchors aren't the issue because they unmarshal skins with the off-the-shelf go-yaml library: https://github.com/derailed/k9s/blob/982bf6a72873131773862779694520e1ef2dc7e8/internal/config/styles.go#L544
Again, really sorry about the noise @nekowinston !
I think we can close this.

No worries, I meant to rework the build system for this repo at some point anyways.
So, we need to rename the extensions from .yml -> .yaml then? I'll just amend this PR.

No worries, I meant to rework the build system for this repo at some point anyways. So, we need to rename the extensions from .yml -> .yaml then? I'll just amend this PR.

Very nice! Ty

I still can't get Skins to work with 0.30, there are so many conflicting docs for Skin usage out there 😕
Can you please give me your config with how you got it to work?
I tried ~/.config/k9s/skins/catppuccin-latte.yaml ~/.config/k9s/catppuccin-latte_skin.yaml
k9s:
  ui:
    skin: catppuccin-latte

k9s:
  skin: catppucin-latte

and nothing works

This is my setup:
❯ pwd
/Users/*****/.config/k9s

❯ tree
Ignoring .git and .idea
.
├── aliases.yaml
├── config.yaml
└── skins
    └── catppuccin-mocha.yaml

❯ cat config.yaml | yq .k9s.ui.skin
catppuccin-mocha

❯ head skins/catppuccin-mocha.yaml
base: '#1e1e2e'
blue: '#89b4fa'
crust: '#11111b'
flamingo: '#f2cdcd'
green: '#a6e3a1'
lavender: '#b4befe'
mantle: '#181825'
maroon: '#eba0ac'
mauve: '#cba6f7'
overlay0: '#6c7086'

I think that on macOS k9s used (or still uses?) ~/Library/Application\ Support/k9s. Which means your changes in ~/.config/k9s might get ignored. I am unsure, but https://github.com/derailed/k9s/issues/1324#issuecomment-1649601099 is a recent comment and mentions a similar issue.

@nekowinston you did get around the issue eventually?

No noise at all. Glad to hear it worked out eventually! Thanks for the PR.


TextFieldElement doesn't allow defaultValue to be set.

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Summary 💡
We should probably expose the defaultValue from the ControllerProps instead of the one from the TextInput and apply it to the Controller
export type TextFieldElementProps<T extends FieldValues = FieldValues> = Omit<
  TextFieldProps,
  'name' | 'defaultValue'
> & {
  validation?: ControllerProps['rules']
  parseError?: (error: FieldError) => string
} & Pick<ControllerProps<T>, 'control' | 'defaultValue' | 'name'>

If you don't get around to it, I'll try and create a PR.
Examples 🌈
No response

@dohomi react-hook-form supports this natively, see Controller docs: https://react-hook-form.com/api/usecontroller/controller
We're build a product add to cart form:

We call useForm at a high level and create a context for it.
In a different part of the system we add fields that is dependent on the product type that is being loaded: <BundleProductOptions/> / <ConfigurableProductOptions/> / <DownloadableProductOptions/>

Exampe of the structure we're using
function ProductPage() {
  const product: ProductInterface = { __typename: 'bla', other: 'fields' }

  return (
    <AddProductsToCartForm uid={product.uid}>
      {isTypename(product, ['ConfigurableProduct']) && <ConfigurableProductOptions />}
      {isTypename(product, ['BundleProduct']) && <BundleProductOptions />}
      {isTypename(product, ['DownloadableProduct']) && <DownloadableProductOptions />}
    </AddProductsToCartForm>
  )
}

Inside Configurable/Bundle/Downloadable we've got fields and some of them have a defaultValue, we'd like to set this through the react-hook-form Controller's defaultValue

@paales yes thats what the defaultValues of useForm are doing. If you check the Storybook you see that you can set the defaultValues on the form hook. It sets the defaultValue on each controller of each field.
https://react-hook-form-material-ui.vercel.app/?path=/story/textfieldelement--pre-defined
Or am I misunderstanding something? You'd set on the useForm hook the default values and it should be passed in. If you have different requirement either set up a codegen or pass a PR I am happy to have a look

@dohomi I'll try and create a PR, I think it is a fairly small change :)


feat(gateway)!: move http support behind twilight_http feature

Only meant for proxys.
Enabling TLS unfortunately pulls in twilight-http either way through twilight-gateway-queue, only way to solve this with current cargo features is to make twilight-gateway-queue optional too.

Related to, but does not fully resolve (iiuc) #1514

Will be rebased on #1809

Ready for rebase.


Lowlife 2090:  Changed attribute descriptions to be more in line with Cyberpunk trappings

Changes / Comments
I've just changed a few of the attribute descriptions, by request of the author of the system.  No functional changes, merely cosmetic/informative.
Roll20 Requests
Comments are very helpful for reviewing the code changes. Please answer the relevant questions below in your comment.

[x] Does the pull request title have the sheet name(s)? Include each sheet name.

Character Sheet Info Roll20 Internal Use only.

Character Sheet Info Roll20 Internal Use only.


ResponseBodyInBytes is null when the response is not parseable

In our scenario, we do not call directly ElasticSearch. We have a Web Load Balancer in the middle to balance the load between Nodes. Plus, we have an Nginx in the same server for security reasons.
Each one of those elements can return a response by themselves, and thus, the response might not be parseable by NEST. I those cases, it's vital for us to have the raw response. In NEST 1.7 we could read it. Now we cannot.
We have DisableDirectStreaming set to true, and we haven't set ThrowExceptions

Also, if the Status Code of the response is 4XX - 5XX, it will throw the exception, so ResponseBodyInBytes will be null, also

Hey @TioLuiso this has already been fixed and will be in the next release (v2.0.5).  See https://github.com/elastic/elasticsearch-net/issues/1856 for details.

Looks really great. Any idea when 2.0.5 will be out?

Just a question. With the default HttpConnection implementation, that uses an HttpWebRequest, when it issues the request, if it receives a 4XX - 5XX status code, it will throw a WebException. That will be caught by OnRequestCompleted handler, but a response won't be returned to the caller (other than the exception).
I have tried you HttpConnection-CoreFx, which uses HttpClient instead, will let you handle the responses and the status codes peacefully.
Do you have any plan to:
a) Update the HttpWebRequest based HttpConnection so that it will return a response.
b) Make HttpClient based HttpConnection available for regular .NET framework?
Thanks a lot

So by default webexceptions won't bubble out of the client mimicing the behavior of HttpClient.
Using the default WebRequest based HttpConnection if we see a 500 you will get back an invalid response (response.IsValid == false) and response.ApiDetails.Response will have a copy of the response if you disable directstreaming (since #1856).
However if the response is not json or empty we would still throw (something now fixed as per #1913) again something that will make it into 2.0.5 which we'll release today.


Add "*Contains(value)" and "*NotContains(value)" Query Helpers

I added *Contains(value) and *NotContains(value) query helper methods generation into String type columns.
We have another option that generates *Glob(pattern) and *NotGlob(pattern) instead of *Contains.
However I prefer *Contains to *Glob because I feel *Glob is too low-level abstraction.

Come to think about it, *Contauns looks lack of unifomity than oher helper methods.
I'm going to recreate PR that add *Glob helpers.
Sorry.

:eye: 👁


(GPT-J) (Prompts Learning) - How to transpose the prefix prompt weights?

Hi all,
I'm using GPT-J model and I just start to explore the soft prompts tuning on it.
FY, to experiment with it I'm following the idea behind this repo https://github.com/exelents/soft-prompt-tuning
I'm looking for an easy way to transpose the prefix prompt weights to the required shape, as written in the official documentation here
[num_layers, 2, num_heads, perfix_seq_len, size_per_head]
Is there any script or example that you already used for soft prompts tuning and to convert the weights in the desired shape?
Thanks for your help

No. We don't have a public model to demonstrate how to use soft-prompt-tuning in FT.
For model converting, we use python to convert and reshape/transpose them directly. You can post the shape of your prompt weight and we may be able to provide some ideas.

Close this bug because it is inactivated. Feel free to re-open this bug if you still have any problem.


Need clearer indicator that combat mode is on.

Right now combat mode still basically locks up most interactions. It's not that bad anymore because there's a button now at least, but it could still be better.
Maybe like make the cursor red? Would require custom mouse cursors.

I'll take this one up if that's ok.

Picked up work on this again. I'll have a prototype out soon.

Picked up work on this again. I'll have a prototype out soon.

Still waiting on that prototype.

working on custom mouse cursors partially for this, i swear ill actually have something done

working on custom mouse cursors partially for this, i swear ill actually have something done

i lied i don't understand opengl or glfw enough to do this but I still want to at some point

We have it in the hotbar now which I think it good 'nuff.


Handle Zarr IO errors for Beam

See #13

Dataflow will retry failed tasks four times, so nothing more is needed here.


disableAllowlist was removed, creating a backwards incompatible change

PR #220 removed the ContextValue property of disableAllowlist.
This change is backwards incompatible. This change was neither documented nor is there an explanation for people using <=1.0.30 on how to correctly change their code.
I discovered this after a dependency upgrade brought in the latest @yfi/sdk v1.1.1 and our build immediately failed with a TypeScript error referencing this property.
What is the correct way to change code that previously relied on disableAllowlist? Does just removing the use of property fix it, or is additional work required?

@cjthompson sorry about that, we deliberated about how to handle the use of the allow list a lot, and I don't think we did it very well unfortunately, with a lot of back and forth. You should be able to remove it from the Context object - on versions >1.0.31 the allow list is always used, validating all writes made by the sdk on chain

@jstashh thanks for the info - please feel free to close as we've removed disableAllowList from where we use the constructor everywhere.


Initial conversion to translation API

Fixes #28; implements the language API.  Documentation for this is not as rich as I would hope; I had to reverse-engineer the MM2 code a bit and discovered https://github.com/MichMich/MagicMirror/issues/2389 in the process, but I worked around that by using " " instead of "" where it broke things.
@McMornan, I'd like to specifically ask you for three things, if you're willing:

Provide feedback on whether this conversion enables you to do your German translation properly
Give me a PR adding the German translation to the repo
Run it for a few days and see if you notice any text glitches

Hi, thanks for your efforts! I'll do my best to help !

Hi, I added a language file for Germany (de.json) und made a pull request in a fork. However the size of the graphs for my Tesla powerwall is now screen filling. Also my global language setting from magicmirror does not seem to be used. (language is set to "de" in global config setting in config.js.

Hm, I'm not sure what's going on with the graph size, and I don't see that on my machine after switching to German.  I did find the issue with the translations not being used -- two issues, actually.  :-)  Give the merged branch a test?

Yea, did that. Works ! Thanks for your fast reply and support!
Von: Mike Bishop<EMAIL_ADDRESS>Gesendet: Donnerstag, 31. Dezember 2020 17:36
An: MikeBishop/MMM-Powerwall<EMAIL_ADDRESS>Cc: McMornan<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Betreff: Re: [MikeBishop/MMM-Powerwall] Initial conversion to translation API (#29)
Hm, I'm not sure what's going on with the graph size, and I don't see that on my machine after switching to German. I did find the issue with the translations not being used -- two issues, actually. :-) Give the merged branch a test?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/MikeBishop/MMM-Powerwall/pull/29#issuecomment-753001455 , or unsubscribe https://github.com/notifications/unsubscribe-auth/AGUURTQEGZU44BP6ARUTIT3SXSR5FANCNFSM4VO3XY5Q .  https://github.com/notifications/beacon/AGUURTWRFMIATKNGK4AV7BTSXSR5FA5CNFSM4VO3XY52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOFTQ6H3Y.gif

I'll go ahead and merge this; if there are further "rough" places you'd like to improve in the translation, feel free to send a PR and/or let me know what needs to be rearranged.

I'll go ahead and merge this; if there are further "rough" places you'd like to improve in the translation, feel free to send a PR and/or let me know what needs to be rearranged.


Make journal's name optionnal

Rebased @AnasGhrab's work on PR #29

Coverage decreased (-0.5%) to 95.188% when pulling e49d38de1c4c99ced557c525124895f958339dc6 on AnasGhrab-patch-1 into 608b0bd85c55bf241cec5aea7311fff6e77628f7 on master.

Coverage decreased (-0.5%) to 95.188% when pulling e49d38de1c4c99ced557c525124895f958339dc6 on AnasGhrab-patch-1 into 608b0bd85c55bf241cec5aea7311fff6e77628f7 on master.


Can't install on Hoobs

Can't install on Hoobs because of missing miio.git ? any clue?
`hoobs@hoobs:/var/lib/homebridge $ sudo npm install -g homebridge-xiaomi-roborock-vacuum@latest --unsafe-perm
npm ERR! path git
npm ERR! code ENOENT
npm ERR! errno ENOENT
npm ERR! syscall spawn git
npm ERR! enoent Error while executing:
npm ERR! enoent undefined ls-remote -h -t git://github.com/nicoh88/miio.git
npm ERR! enoent
npm ERR! enoent
npm ERR! enoent spawn git ENOENT
npm ERR! enoent This is related to npm not being able to find a file.
npm ERR! enoent

Try:
sudo su -
npm install -g homebridge-xiaomi-roborock-vacuum@latest --unsafe-perm

sudo su - is important

I have tried with sudo su - too without any success, same errors. Wonder if this could be related just to Hoobs

Ok, I found a solution. You need first install git "apt-get install git" to make this work on Hoobs then you don't even need sudo su -
Thanks anyway.

Thanks, you've saved my day! Had exactly the same issue, installing git first resolved it.


NullPointerException | 1.8.8

I had this error today in my console:
I've no ideia what caused it.
[16:21:54 WARN]: [LoginSecurity] Task #163 for LoginSecurity v2.1.6 generated an exception java.lang.NullPointerException         at com.lenis0012.bukkit.loginsecurity.modules.general.GeneralModule$3$1.run(GeneralModule.java:140) ~[?:?]         at org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftTask.run(CraftTask.java:71) ~[Spigot%201.8.8.jar:git-Spigot-21fe707-e1ebe52]         at org.bukkit.craftbukkit.v1_8_R3.scheduler.CraftScheduler.mainThreadHeartbeat(CraftScheduler.java:350) [Spigot%201.8.8.jar:git-Spigot-21fe707-e1ebe52]         at net.minecraft.server.v1_8_R3.MinecraftServer.B(MinecraftServer.java:723) [Spigot%201.8.8.jar:git-Spigot-21fe707-e1ebe52]         at net.minecraft.server.v1_8_R3.DedicatedServer.B(DedicatedServer.java:374) [Spigot%201.8.8.jar:git-Spigot-21fe707-e1ebe52]         at net.minecraft.server.v1_8_R3.MinecraftServer.A(MinecraftServer.java:654) [Spigot%201.8.8.jar:git-Spigot-21fe707-e1ebe52]         at net.minecraft.server.v1_8_R3.MinecraftServer.run(MinecraftServer.java:557) [Spigot%201.8.8.jar:git-Spigot-21fe707-e1ebe52]         at java.lang.Thread.run(Unknown Source) [?:1.8.0_111]
Also, there's a small bug. When you use /logout, the plugin kicks you for taking too long to login (instantly). So it doesn't reset/stays counting the time even after login.
I've tested the /lac rmpass, and when you removes the password of a player and he keeps online, the map doesn't update and you get kicked for wrong captcha.
The map does not get removed from your inventory if you use /register and do not type the password.
Another two errors I found right now (/lac rmpass bug):
http://hastebin.com/abutobuqub.md
Now some ideas

[ ] Like the another thread, /register   would be really useful.
[ ] The map captcha is great, but sometimes if the player spawns in a block - e.g. I reset his password and he logs in again - it's impossible to see the map, so no way to complete it. Maybe teleport him to somewhere or make sure he is not glitching?
[ ] /unregister command? I know there's /lac rmpass, but only for admins.

Seems to be caused by version.getType().toString()

These are quite a few issues/suggestions.
ill see when i have time

Fixed the issue, it's in the latest dev build.
As for the feature requests.
Like the another thread, /register [password] [confirm password] would be really useful.
Please see #67
I will make a separate issue for the other 2 requests.


Publish UTM to the iOS App Store!

Since Apple allowed emulators to the App Store, why not publish UTM?

also I do NOT have a Mac!


packetLoss endpoint has CORS set to speed.cloudflare.com

Hi there, the default config is failing because the packetLoss test queries https://speed.cloudflare.com/turn-creds
However, the CORS policy for this page is set to only accept cloudflare domains (e.g., access-control-allow-origin: speed.cloudflare.com)
A workaround is to remove packetLoss calculations from the test, but I'd love to be able to also use packetLoss stats in the reporting on my app!

+1

+1 having issues with the turn-creds CORS

@96imranahmed how did you do the workaround for packetLoss??

Sorry I wasn't clear - I don't have a solution for getting a packetLoss metric. I just ignore the test entirely by removing it from the list of default measurements that are run when you make a test.
    { type: 'latency', numPackets: 1 }, // initial ttfb estimation
    { type: 'download', bytes: 1e5, count: 1, bypassMinDuration: true }, // initial download estimation
    { type: 'latency', numPackets: 20 },
    { type: 'download', bytes: 1e5, count: 9 },
    { type: 'download', bytes: 1e6, count: 8 },
    { type: 'upload', bytes: 1e5, count: 8 },
    { // Remove this line
      type: 'packetLoss',
      numPackets: 1e3,
      batchSize: 10,
      batchWaitTime: 10, // ms (in between batches)
      responsesWaitTime: 3000 // ms (silent time after last sent msg)
    },
    { type: 'upload', bytes: 1e6, count: 6 },
    { type: 'download', bytes: 1e7, count: 6 },
    { type: 'upload', bytes: 1e7, count: 4 },
    { type: 'download', bytes: 2.5e7, count: 4 },
    { type: 'upload', bytes: 2.5e7, count: 4 },
    { type: 'download', bytes: 1e8, count: 3 },
    { type: 'upload', bytes: 5e7, count: 3 },
    { type: 'download', bytes: 2.5e8, count: 2 }

We will apply a fix in the next days.

@joao-reis Please let me know when fix is released  :D

Fixed 👍

Works perfectly! Let me close this!


missing entity object for extrusionDirection

Nice catch. Thanks for the commit. I'll get this in soon.


chore(e2e): Update cypress 13.3.0 devDependencies in ui

Description
https://docs.cypress.io/guides/references/changelog#13-3-0

Fixed an issue where actionability checks trigger a flood of font requests. Removing the font requests has the potential to improve performance and removes clutter from Test Replay.

Checklist

[ ] Investigated and inspected CI test results
[x] ~Unit test and regression tests added~

Testing Performed

yarn in ui
yarn start in ui
yarn cypress-open in ui/apps/platform

compliance/hideScanResults.test.js

Closed because of errors with Cypress 13.y releases and instead temporarily downgraded in #7920


Jd thanks

Rickie's stuff
Barry's Stuff
Other Details

The roses in the thanks section are a nice touch!


Adding Wollo University.

@shimelsD First stage of verification passed, official domain is wu.edu.et as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@shimelsD Thank you for your patience while waiting for a review and processing your request. Pull request merged.


Merging in auto generated slack actions

This PR merges in the actions from the auto-generated Slack pack:
https://github.com/StackStorm/st2-slack
All existing actions and configs remain for backwards compatibility.

Are we abandoning st2-slack?

We need to collapse these one way or the other.  I went this way so people that already had the pack can just reinstall and get the updates...no need to find the new location.


[2.6] exclude some status checks for some providers

2.6 version of https://github.com/rancher/rancher/pull/31890
ISSUE: #11496
PROBLEM:
Not all providers implement component status correctly, e.g. AKS shows the scheduler in an error state. We need to ignore some component statuses as they can be misleading.
SOLUTION:
Added a filter to the health syncer that does not return some component statues based on provider.
TESTING:
I was unable to get access to an AKS cluster but, I could filter components out of a k3os cluster by adding it to the exclusion map.

Will this actually work for imported clusters (of those types) and modern clusters that disable HTTP on the components? (e..g anything created with a current kubeadm version)
(It feels, for a quick fix, like an option to disable those statuses that can be set on any cluster might be useful. In some cases, where the stuff is running, but without the insecure port that component-statuses demand, the option to designate a filter to find the pods' health checks to monitor instead might be better, but harder to implement...)

Hi,
With AKS it's ignoring the Controller Manager and Scheduler just fine. But like @mohag is mentioning, it would be nice to also apply this for imported clusters.
Is it somehow possible?


pivpn return code

When executing pivpn command, most cases end with return code 1. This is inconsistent with conventions : 0 = OK, 1 = Error.
In my case this blocks proper automation of pivpn docker container creation. My Makefile runs the following command to validate the installation :
docker-compose exec rpi-pivpn /usr/local/bin/pivpn -l

As return code is 1, make command fails with error (return code <> 0) :
: NOTE : The first entry should always be your valid server!

::: Certificate Status List :::
 ::  Status  ||   Name   ::
     Valid   ::   server_kKVj19oJviuCCvvD

Makefile:34 : la recette pour la cible « test » a échouée
make: *** [test] Erreur 1

I will submit a patch for this, and also share my running docker pivpn image for raspberry pi zero when I'll have finished :)

There is already one similar project, might be worth taking a look at it: https://github.com/InnovativeInventor/docker-pivpn
Will mark this as enhancement so we can take a look at the exiting error codes.
Thanks for your interest.

Any update on this thread? Always exit with 1 fails all python subprocess calls to pivpn.

that has already been changed in test branch:
https://github.com/pivpn/pivpn/commit/9f20f50e6168d4d24d40e938cbb9b48c2f4ee383

this has been merged today into Master branch.
Closing


is draggable option supported in CustomMarker?

Hi,
I am  using in maps in my application where I wish show the custom marker and provide the drag functionality. I tried using CustomMarker with draggable option. But it seems not to be working.
Is there any workaround I can try?
Thanks

No this isn't yet supported but it's something we can add.

What about AdvancedMarker, e.g. this?

nvm - I was going about it the wrong way trying to get a ref (didn't work) and binding a listener to that, but had a eureka moment when I realized I could just bind the event.
<AdvancedMarker
	ref="markerRef"
	:options="{ position: center, gmpDraggable: true }"
	@dragend="onDragEnd"
/>

☝ I think this would be handy to show examples of this somewhere. The documentation for events only says "You can listen for the following events...".

I was in the same boat but I got it to work by overriding the content
const markerOptions = computed(() => {
  if (!siteForm.lat || !siteForm.lng) return {};

  return {
    position: { lat: siteForm.lat, lng: siteForm.lng },
    gmpDraggable: true,
    content: createCustomPin()
  }
});

const createCustomPin = () => {
  const img = document.createElement('img');
  img.src = '/imgs/google_map_pin.png';
  img.style.width = '100%';
  img.style.height = '100%';
  return img;
}


The entire Setting Compendium is blank

Describe the bug
The entire compendium for setting is blank, the tabs like The Drift, or Triune is there. But when clicked, it's the title, And blank, nothing there at all.
To Reproduce
Open the Setting Compendium
Expected behavior
To be able to see the Compendium
Screenshots

Technical details (please complete the following information):

OS: Windows 10
Browser: Chrome
Foundry Version: 12.328
SFRPG Version: 0,26.1

Additional context
Add any other context about the problem here.

I can confirm that this is true for the top of development at the moment. Though in my local environment I can fix this entirely by forcing the cook process to push through the consistency errors. This should be resolved by #1361.

I'm going to close this as #1361 has been merged into development.


remove_training_nodes (Python Lib) Removes Identity Node Even When is Output

remove_training_nodes removes Identity nodes even if that node is the specified graph output.
For example if the Identity node was used to name and make more easily locatable the output of the graph.

@drpngx I believe you wrote this code?  Could you please comment.

@petewarden who contributed the original code.
@cancan101 Could you send a simple, compact repro case?
Not sure, we have another case internally where replacing the if clause fixed a problem.
      while input_name in names_to_splice:
        full_input_name = names_to_splice[input_name]
        input_name = re.sub(r"^\^", "", full_input_name)
      new_node.input.append(full_input_name)

Fix submitted, but not quite sure when/how this will propagate here.

Thanks! We try to push every day, hopefully it'll be there tomorrow. If you included Fixes#8181 in your CL description, then it'll close this issue automatically when the fix is merged.

Looks like the fix is in, but I don't seem to be able to close this myself...

Can you link to PR?

I think that would be https://github.com/tensorflow/tensorflow/pull/8402.

In particular: https://github.com/tensorflow/tensorflow/pull/8402/commits/221cfa1e31be026a6f459410f0ed930befd8371d
Did that work for you @cancan101 ?

Not sure, the issue I was having was that the last node (the output node) was of type Identity and that was getting pruned itself.

Can you try with the updated code?
On Mar 15, 2017 8:26 AM, "Alex Rothberg"<EMAIL_ADDRESS>wrote:

Not sure, the issue I was having was that the last node (the output node)
was of type Identity and that was getting pruned itself.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/issues/8181#issuecomment-286776834,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT_SbSABKLY6MGZHs_qO2zrHX_RHeMAwks5rmAMAgaJpZM4MWQgu
.

Oh, then this may not fix your problem...

Here is a short example demonstrating the issue:
import tensorflow as tf
from tensorflow.python.framework.graph_util_impl import remove_training_nodes

with tf.Graph().as_default() as g:
    input = tf.placeholder(tf.float32)
    output = tf.identity(input, name='output')
    graph_def = g.as_graph_def()
    print("Before:")
    print([n.name for n in graph_def.node])
    print("After:")
    print([n.name for n in remove_training_nodes(graph_def).node])

which produces:
Before:
[u'Placeholder', u'output']
After:
[u'Placeholder']

In this case the signature of remove_training_nodes might need to be changed to list the set of nodes that should not be removed.
Thoughts?

@drpngx What's the status?

We changed the remove_training_nodes to include a new parameter protected_nodes, which are kept unconditionally. @cancan101 would that work for you?

That should work.

Great!

Maybe I have the same problem. TensorFlow VERSION  1.1.0
Has it been fixed in 1.1.0?
I specifed ["input", "output"] as the input and output nodes of my model  by tf.identity.
After frozen,  I can found "input", "output" in graph_def.node.
After optimized, "input" is still there, but "output" is lost.
train.py
def inference(images):
  images = tf.identity(images, 'input')
... ...
  softmax_linear = tf.identity(softmax_linear, 'output')
  return softmax_linear

package.py -- Generate model file
# -*- coding: utf-8 -*-
# Preparing a TF model for usage in Android
# pylint: disable=missing-docstring
from __future__ import absolute_import
from __future__ import division
from __future__ import print_function
import sys
import tensorflow as tf
from tensorflow.python.tools import freeze_graph
from tensorflow.python.tools import optimize_for_inference_lib

MODEL_NAME = 'carc34'
path='.'
input_graph_path = '%s/graph.pbtxt' % path
checkpoint_path = '%s/model.ckpt-100000' % path
input_saver_def_path = ""
input_binary = False
input_node_names = "input"
output_node_names = "output,softmax_linear/softmax_linear"
restore_op_name = "save/restore_all"
filename_tensor_name = "save/Const:0"
output_frozen_graph_name = 'frozen_'+MODEL_NAME+'.pb'
output_optimized_graph_name = 'optimized_'+MODEL_NAME+'.pb'
clear_devices = True

# Freeze the graph
freeze_graph.freeze_graph(input_graph_path, input_saver_def_path,
                          input_binary, checkpoint_path, output_node_names,
                          restore_op_name, filename_tensor_name,
                          output_frozen_graph_name, clear_devices, "")

# Optimize for inference
input_graph_def = tf.GraphDef()
with tf.gfile.Open(output_frozen_graph_name, "rb") as f:
    data = f.read()
    input_graph_def.ParseFromString(data)
    output_graph_def = optimize_for_inference_lib.optimize_for_inference(
                input_graph_def,
                input_node_names.split(","),  # an array of the input node(s)
                output_node_names.split(","), # an array of the output nodes
                tf.float32.as_datatype_enum)

# Save the optimized graph
f = tf.gfile.FastGFile(output_optimized_graph_name, "w")
f.write(output_graph_def.SerializeToString())
##tf.train.write_graph(output_graph_def, './', output_optimized_graph_name)   #

show_nodes.py -- Print all nodes in frozen and optimized
from __future__ import absolute_import
from __future__ import division
from __future__ import print_function
import os.path
import numpy as np
import tensorflow as tf
from tensorflow.python.framework import graph_util
from tensorflow.python.framework import tensor_shape
from tensorflow.python.platform import gfile
from tensorflow.python.util import compat

MODEL_OUTPUT_TENSOR_NAME = 'output'
with tf.Graph().as_default() as graph:
    model_filename = os.path.join('.', 'frozen_carc34.pb')
    with gfile.FastGFile(model_filename, 'rb') as f:
      graph_def = tf.GraphDef()
      graph_def.ParseFromString(f.read())
      ##for n in graph_def.node:
      ##  print (n.name)
      output_tensor = tf.import_graph_def(graph_def, name='', return_elements=[MODEL_OUTPUT_TENSOR_NAME])
      print ("Found in frozen")

    model_filename = os.path.join('.', 'optimized_carc34.pb')
    with gfile.FastGFile(model_filename, 'rb') as f:
      graph_def = tf.GraphDef()
      graph_def.ParseFromString(f.read())
      ##for n in graph_def.node:
      ##  print (n.name)
      output_tensor = tf.import_graph_def(graph_def, name='', return_elements=[MODEL_OUTPUT_TENSOR_NAME])
      print ("Found in optimized")

Hi Xiusir
I need you help, I am facing the same issue while running the optimize_for_inference.py script.
My arguments are as below:
python optimize_for_inference.py --input=res101_faster_rcnn_iter_5600.pb --output=optimized_graph.pb --input_names="input" --output_names="final_result"
My pb file is based on Resnet-101. I am sharing my res101_faster_rcnn_iter_5600.ckpt.custom file below to see it's contents:
`node {
name: "Placeholder"
op: "Placeholder"
attr {
key: "dtype"
value {
type: DT_FLOAT
}
}
attr {
key: "shape"
value {
shape {
dim {
size: 1
}
dim {
size: -1
}
dim {
size: -1
}
dim {
size: 3
}
}
}
}
}
node {
name: "Placeholder_1"
op: "Placeholder"
attr {
key: "dtype"
value {
type: DT_FLOAT
}
}
attr {
key: "shape"
value {
shape {
dim {
size: 1
}
dim {
size: 3
}
}
}
}
}
node {
name: "Placeholder_2"
op: "Placeholder"
attr {
key: "dtype"
value {
type: DT_FLOAT
}
}
attr {
key: "shape"
value {
shape {
dim {
size: -1
}
dim {
size: 5
}
}
}
}
}
node {
name: "resnet_v1_101/Pad/paddings"
op: "Const"
attr {
key: "dtype"
value {
type: DT_INT32
}
}
attr {
key: "value"
value {
tensor {
dtype: DT_INT32
tensor_shape {
dim {
size: 4
}
dim {
size: 2
}
}
tensor_content: "\000\000\000\000\000\000\000\000\003\000\000\000\003\000\000\000\003\000\000\000\003\000\000\000\000\000\000\000\000\000\000\000"
}
}
}
}
node {
name: "resnet_v1_101/Pad"
op: "Pad"
input: "Placeholder"
input: "resnet_v1_101/Pad/paddings"
attr {
key: "T"
value {
type: DT_FLOAT
}
}
attr {
key: "Tpaddings"
value {
type: DT_INT32
}
}
}
node {
name: "resnet_v1_101/conv1/weights/Initializer/truncated_normal/shape"
op: "Const"
attr {
key: "_class"
value {
list {
s: "loc:@resnet_v1_101/conv1/weights"
}
}
}
attr {
key: "dtype"
value {
type: DT_INT32
}
}
attr {
key: "value"
value {
tensor {
dtype: DT_INT32
tensor_shape {
dim {
size: 4
}
}
tensor_content: "\007\000\000\000\007\000\000\000\003\000\000\000@\000\000\000"
}
}
}
}
node {
name: "resnet_v1_101/conv1/weights/Initializer/truncated_normal/mean"
op: "Const"
attr {
key: "_class"
value {
list {
s: "loc:@resnet_v1_101/conv1/weights"
}
}
}
I am getting tyhe below error :
_result" /home/arun/anaconda3/lib/python3.6/importlib/_bootstrap.py:219: RuntimeWarning: compiletime version 3.5 of module 'tensorflow.python.framework.fast_tensor_util' does not match runtime version 3.6 return f(*args, **kwds) /home/arun/anaconda3/lib/python3.6/site-packages/h5py/init.py:34: FutureWarning: Conversion of the second argument of issubdtype fromfloattonp.floatingis deprecated. In future, it will be treated asnp.float64 == np.dtype(float).type. from ._conv import register_converters as _register_converters Traceback (most recent call last): File "optimize_for_inference.py", line 146, in  app.run(main=main, argv=[sys.argv[0]] + unparsed) File "/home/arun/anaconda3/lib/python3.6/site-packages/tensorflow/python/platform/app.py", line 48, in run _sys.exit(main(_sys.argv[:1] + flags_passthrough)) File "optimize_for_inference.py", line 90, in main FLAGS.output_names.split(","), FLAGS.placeholder_type_enum) File "/home/arun/anaconda3/lib/python3.6/site-packages/tensorflow/python/tools/optimize_for_inference_lib.py", line 109, in optimize_for_inference placeholder_type_enum) File "/home/arun/anaconda3/lib/python3.6/site-packages/tensorflow/python/tools/strip_unused_lib.py", line 83, in strip_unused raise KeyError("The following input nodes were not found: %s\n" % not_found) KeyError: "The following input nodes were not found: {'input'}\n"
Please help me identifying what arguments you passed to run the script.
python touch.py -m res101_faster_rcnn_iter_5600.ckpt.meta -o res101_faster_rcnn_iter_5600.pb -b
and my touch.py has following contents, which I took from some repository:
#! /usr/bin/python3
#generate a pb file !
from future import print_function
import tensorflow as tf
import argparse
import os
if name == 'main':
parser = argparse.ArgumentParser()
parser.add_argument('-m','--model',required=True, type=str, metavar='' ,help="model meta graph AKA .ckpt.meta file to start with")
parser.add_argument('-o', '--output_file', type=str, required=True, metavar='',help="Where to save the output file ")
parser.add_argument('-b','--bin',dest='binary_file',action='store_true', help="saves file as binary instead of default text file")
parser.add_argument('-v','--verbose',dest='verbosity',action='store_true',help="trigger the verbose output (show tensorflow debug info)")
args = parser.parse_args()
#get output dir from output file name
output_dir = os.path.dirname(args.output_file)
if output_dir == "":
    output_dir="."
output_file_name = os.path.basename(args.output_file)
#setting verbosity
os.environ['TF_CPP_MIN_LOG_LEVEL'] = '3'
if args.verbosity:
    os.environ['TF_CPP_MIN_LOG_LEVEL'] = '0'
print ("Welcome to tensorflow graph saver")
print ("loading ",os.path.basename(args.model))
#opening a new session
with tf.Session() as sess:
    new_saver = tf.train.import_meta_graph(args.model)
    new_saver.restore(sess,args.model.replace(".meta","") )
    print ("model",os.path.basename(args.model),"loaded correctly... converting it to graph")
    tf.train.write_graph(sess.graph, output_dir ,output_file_name, as_text=not args.binary_file)
    print("conversion done, output file saved as",args.output_file)


Errors inside Search Console

Hello guys,
I’ve installed the Google Web Stories Beta plugin and I submitted a story to test it.
Here's the story:
https://durmonski.com/stories/the-selfish-gene/
Sadly, I’m getting the following errors inside Google Search console:

Tag ‘amp-story’ is not allowed to have any sibling tags (‘body’ should only have 1 child).
2.
A mandatory AMP HTML tag is missing from this document.
3.
Tag found outside the document head which is only allowed as a direct child of the document head.
4.
Only amp-boilerplate and amp-custom ‘style’ tags are allowed, and only in the document head.
I don’t have the AMP plugin installed. Should I? If yes, shouldn’t the Google stories run without the AMP plugin?
I posted this issue inside WordPress AMP forum, here:
https://wordpress.org/support/topic/errors-inside-search-console/#post-13318315
Your colleagues there said the following:

Also, it appears there may be a compatibility problem with WP Rocket. You may want to mention this in your GitHub issue.

Can you please check?
Thanks!
Ivaylo Durmonski

@durmonski Thank you for submitting this issue! The reason why these errors occur is because the Web Story post is an AMP document. AMP is a framework built with its own optimizations. AMP documents must also adhere to certain specifications in the code to be valid AMP. Search Console will flag the URL when valid code is being altered or invalid code is added.

Also, it appears there may be a compatibility problem with WP Rocket. You may want to mention this in your GitHub issue.

Could you exclude the "/stories/" URL in WP Rocket settings to prevent optimization on those posts under Advanced Rules > Never Cache URL(s).

OK, thanks. I've excluded the stories.
So, I should add the AMP plugin if I want to use the stories?
This part I didn't get.

You don't need to add the AMP plugin if you want to use Web Stories.
I did notice your story URL showed some validation errors on the AMP test results that are like error messages occurring on another issue . Could you please try this in-development version and let us know if you see any changes. Download:
web-stories.zip

Hi @durmonski ! Just following up that the most recent version 1.0.0-rc.1 contains a fix for the issue you experienced. Please let us know if updating the plugin resolves the validation errors you received in Search Console.

@durmonski the stable version of the plugin 1.0.0 has been released. I will close your issue now, but please feel free to update and reach out to us in our WordPress.org support forum if you should still experience the issue. Happy to help!


article: Django REST Framework Pagination Snippet

closes #261

@Bashamega Am i not allowed to create a pr for my code i submitted?

@Bashamega Am i not allowed to create a pr for my code i submitted?

I am very sorry. I thought you wanted me to work on it. I will close this pr and i will assign the issue to you.


DirecTV Receiver Media Player Component

Description:
This adds support for DirecTV receivers.  Able see what is currently playing, and able to control playback.  Auto discovery is also available
Related issue (if applicable): fixes #
Pull request in home-assistant.io with documentation (if applicable): https://github.com/home-assistant/home-assistant.io/pull/659
Example entry for configuration.yaml (if applicable):
media_player:
  platform: directv
  host: <IP_ADDRESS>
  name: DirecTV Living Room

Checklist:
If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated in home-assistant.io

If code communicates with devices, web services, or a:

[X] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[X] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[X] New dependencies are only imported inside functions that use them ([example][ex-import]).
[X] New dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[X] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

I'll publish a new version of netdisco tonight.

New version of Netdisco published. Once comment addressed this is good to go 👍

Bueno 🐬


Specify arg count when promisifying generateAuthorizationCode

This call doesn't seem to finish when specifying generateAuthorizationCode as an async function using TypeScript.
I tried to create a unit test for this case in this repository but couldn't get it to fail so I am guessing that this works by accident for JS.
But obviously this call to promisify is incorrect, as the promisify-any documentation mentions:

If the function expects arguments, the number of arguments (not including the callback) MUST be provided as a 2nd argument to promisify.

This solves #492

Having the same problem mentioned in #492 . Why this hasn't been merged?

I would guess nobody is actively maintaining the project currently?

@sgronblo could you add a failing test to demonstrate this?


Isolation and sharing between contexts

There was a previous discussion regarding this (#2092), when marshalling fields between contexts had just become more permissive, but I still had some questions that remained.
Baseline: to what extent do contexts on the same thread and runtime share data?

Do values share the reference count?
Are all types of values shareable?
Can I reuse script results between contexts?
Are there any gotchas?

Perhaps it's easier the name the things that are not shared?
Since JsCreateSharedArrayBufferWithSharedContent was recently implemented, I can only assume there are some limitations.
The catalyst for this discussion stems from chakracore-rs#14 — how to manage JsRelease in destructors. JsRelease requires an active context, and this cannot be ensured in destructors with chakracore-rs current implementation. Therefore I was contemplating whether a default context could be used to support JsRelease (for cases when the user no longer have any active contexts).

Let's answer your question on JsRelease first.
Yes, JsRelease doesn't care which context you have, so you can set a default context in general
To be more precise though:

For JsContextRef, you can call JsRelease without any context set (itself being a context)
For JsValueRef, you can get the context of the object using JsGetContextOfObject to get the context
For JsPropertyIdRef, require some context to be set, so you can use a default context

To answer your general question about cross context:

Are all types of values shareable?

Any JsValueRef can be used on any context as long as they are created from the same JsRuntimeHandle

Do values share the reference count?

Yes, they share the same reference count for JsAddRef/JsRelease.

Can I reuse script results between contexts?

Yes

Are there any gotchas?

The only gotchas is that using JsValueRef value from another JsContextRef is slightly slower, because it needs to go thru some cross context thunk to track the transitions.
Note that I didn't use share in my answer above, just because the word share in JsCreateSharedArrayBufferWithSharedContent has a different meaning.  That is an API to create SharedArrayBuffer, analogous to ArrayBuffer, new to the ECMAScript spec https://tc39.github.io/ecma262/#sec-sharedarraybuffer-objects.
The purpose of this language feature is to enable concurrent access to a shared buffers between threads.  You can use JsGetSharedArrayBufferContent to get the buffer content of a SharedArrayBuffer, and use JsCreateSharedArrayBufferWithSharedContext on a JsContextRef from another JsRuntimeHandle.

Thanks a ton! I believe this answers all of my questions.


Drop Python 2 support

Python 2 had reached EOL on 2020-01-01.
In fact, we are not making any changes in this release that break compatibility, but we no longer officially support it. This means that we do not run any CI tests for Python 2, and free to develop code compatible only with Python 3+.

We might need to update this workflow also
https://github.com/cossacklabs/themis/blob/master/.github/workflows/test-python.yaml#L56

Yep, thanks, already saw it. Fixed.


How should I set the referrer for a navigation request?

Newbie here, both go and Chromedp  which I enjoy very much and have used for my simple purpose rather easily. However I can't seem to achieve adding a referrer to my requests so I'd like a bit of guidance here, or links to suitable documentation
What did you do? Include clear steps.
I am browsing some pages , using as a basis the examples provided. Similar to:
ctx, cancel := chromedp.NewContext(context.Background())
defer cancel()

err := chromedp.Run(ctx,
	chromedp.Emulate(device.Pixel2),
	chromedp.Navigate(`https://example.com`),
);

Now I also need to set the referer and I could not find what seem the proper way to do that.
The withReferrer method is on the page object which chromedp.Navigate() does not let me access.
So I tried to replace chromedp.Navigate() with my own:
tasks = append(
	tasks,
	chromedp.ActionFunc(func(ctx context.Context) error {
		_, _, _, err := page.Navigate(url).WithReferrer(referrer).Do(ctx)
		if err != nil {
			return err
		}
		return chromedp.WaitLoaded(ctx)
	},
	),
)
err := chromedp.Run(ctx,
	chromedp.Emulate(device.Pixel2),
	tasks,
);

and that sort of works but not really because chromedp.waitLoaded() is not exported so I had to modify chromedp.nav to export it.
Alternatively, I added a NavigateWithReferrer() method to chromedp (to be able to access waitLoaded()):
func NavigateWithReferrer(urlstr string, referrer string) NavigateAction {
	return ActionFunc(func(ctx context.Context) error {
		_, _, _, err := page.Navigate(urlstr).WithReferrer(referrer).Do(ctx)
		if err != nil {
			return err
		}
		return waitLoaded(ctx)
	})
}

That works fine of course but is obviously not a solution.
So what's the proper way to set the referrer a request?
Many thanks

Any update on this ? :(

The answer for navigation options is indeed to call page.Navigate directly. We don't want the high-level chromedp.Navigate API to suddenly get extra options; the main reason it exists is to be simple.
The solution to your problem is indeed to expose waitLoaded, somehow. I've been thinking about that for a while, because it's also useful when one clicks a button that triggers a navigation, for example. I've filed https://github.com/chromedp/chromedp/issues/641, so we can keep the discussion there.
Thanks!

@cleey If you have followed #641, you should find that mvdan has came up with a general solution for such kind of requirements:
https://github.com/chromedp/chromedp/blob/f50e6240fa873d8c103c54a028b78266f4b09138/chromedp.go#L431-L441
With chromedp.RunResponse, we can do it like this:
if _, err := chromedp.RunResponse(ctx,
	chromedp.ActionFunc(func(ctx context.Context) error {
		_, _, _, err := page.Navigate("https://www.bing.com/").
			WithReferrer("https://www.google.com/").
			Do(ctx)
		return err
	}),
); err != nil {
	log.Fatal(err)
}


Hyundai longitudinal (CAN): don't send FCA12 on non-FCA cars

Description

Added int flag USE_FCA12. Some platforms such as the GENESIS_G80 do not have both FCA11 and FCA12. This PR introduces a new int flag that conditionally checks if FCA12 exists on the CAN bus. If FCA12 does not exist, we do not try to send FCA12 when openpilot longitudinal control is enabled.
Renamed int flag USE_FCA --> USE_FCA11

Verification

openpilot Longitudinal Control (Alpha) engaged successfully on the GENESIS_G80, which does not have FCA11 and FCA12.

Route

Route: fc0b0898f920f030/00000001--ab82eecd02

Prerequisite of

https://github.com/commaai/openpilot/pull/32580

Thanks to community 2018 Genesis G80 owner gogrant43 (Discord).

We've moved the car interfacing code to our opendbc repository, which is now the new home for car ports and fingerprints. Please re-open your pull request against opendbc at your convenience by using this command below. This will transform all changes under selfdrive/car/ to opendbc_repo/opendbc/car/. Make sure you have initialized submodules beforehand and have checked out the latest opendbc commit.
PR_NUMBER=33045
curl -L https://github.com/commaai/openpilot/pull/$PR_NUMBER.patch | sed -e 's/selfdrive\/car/opendbc_repo\/opendbc\/car/g' | git apply -v --reject

Simply replace the PR number with your own. Once done, add the files, fix any conflicts, and open a new PR. Alternatively, you may start a new PR from scratch if that is easier for you.


Derivation inputs determined by another derivation? (metaprogramming question)

Question about Nix programming style which I hope is on topic for this repo! (Or maybe I should have posted to nixos/nix?)
Is there a straightforward idiom for defining derivations whose inputs are calculated dynamically e.g. where one derivation determines the inputs to another?
For example suppose that I have this file at url http://foo.com/foo.yaml:
sources:
  - http://foo.com/a.tar.gz
  - http://foo.com/b.tar.gz
  - http://foo.com/c.tar.gz

and now I want to write a nix expression that first "manually" fetches http://foo.com/foo.yaml and then also "automatically" fetches each of the sources that are listed in that file?
The use case is processing log files with nix. The simple case is to process the log from one process (e.g. a.tar.gz). The hard case is making it possible to define a set of processes whose logs should be processed in combination (that's what foo.yaml is for.)

There is a feature that does just that, named "import from derivation": you can do import "${foo}/bar.nix".

Except builtins.fetchurl caches and is hard to force-expire the cache. See https://github.com/NixOS/nix/issues/1223

Thanks for the info guys. Let me just check if I understand correctly before closing this issue.

There is a feature that does just that, named "import from derivation": you can do import "${foo}/bar.nix"

Neat. So in my example I could have a first derivation (d1) that downloads the foo.yaml file and transforms it into a nix expression listing some sources, then a second derivation (d2) that loads this from the output of the first?
let d1 = mkDerivation { src = fetchurl "http://foo.com/foo.yaml"; ... };
    d2 = mkDerivation { src = import "${d1}/inputs.nix"; ... }; in

and this would be perfectly valid nix code and nothing to be ashamed about? :-)

@lukego We try to avoid it in nixpkgs because this makes determining and printing build plan impossible (Those will be built...., those will be fetched....), but that's completely okay in general!

Thank you for the very helpful explanations!


How to add custom headers?

How can custom request headers be added? The ra-data-feathers REST client is a function that can be called with type, resource and params, but where can the HTTP headers be changed?

The underlying Feathers instance offers hooks that can be used to change/add HTTP headers:
const feathersApp = feathers();

// [...]

feathersApp.configure((app: Application) => {
  app.hooks({
    before: {
      all: [
        hook => {
          if (!hook.params.headers) {
            hook.params.headers = {};
          }
          hook.params.headers['x-client'] = 'react-admin';
        }
      ]
    }
  })
});

// [...]

import { authClient, restClient } from 'ra-data-feathers';
// [...]
const dataProvider = restClient(feathersClient, restClientOptions);

In some cases this custom header (X-Client) must be allowed by the server by sending its header name (CORS).
(Note: The RFC user agent header can't be changed in current browsers by the way).
FeathersJS server / backend:
// Allow `X-Client` custom HTTP request header from clients (CORS)
app.use((req, res, next) => {
  res.setHeader('Access-Control-Allow-Headers', 'x-client');
  next();
});


Simplified initialSetup() function

swapped let for const when appropriate
simplified initialSetup() function

@mitchspano just wanted to get a little PR going here, but I have a much bigger question - any reason for not using TypeScript for this repo? It would make refactoring some of these functions a lot easier (especially places where the sync version of fs functions are being used at present) and allow you to express things like the severity levels being returned from the scanner in a type-safe way

As an example of why I find TS to be the ultimate helper for these things - it found the (obvious) bug in the solution I just submitted:

I'll snap off another commit with that fix

Hey @jamessimone  thank you so much for your contribution!
Regarding TypeScript, I would be definitely open to refactoring this to TypeScript - I only chose JavaScript because of my familiarity with the language and the readily available documentation.
If we can make this work with TypeScript it would provide the benefits you mentioned above and (perhaps selfishly) be an excellent learning opportunity for me to get familiar with a new language.

@mitchspano I included another example of how helpful TypeScript can be in the PR I tagged you in on my own fork. There is going to be (in my experience locally developing this application) a significant pain point in keeping node_modules as part of this project's source code, but we would also need to prove out that the tools which bundle dependencies with a TypeScript action actually include the sfdx-cli dependency (since that is being invoked via a child process, which probably precludes the ability for tree shaking to find the dependency properly).
Regardless - I think there's a lot of potential to do additional cleanup even if the project remains entirely javascript-based. Here's an example of what I'm talking about (which I only have locally):
async function main() {
  const { inputs, pullRequest, scannerCliArgs } = initialSetup();
  validatePullRequestContext(pullRequest);
  const filePathToChangedLines = getDiffInPullRequest(pullRequest);
  await recursivelyMoveFilesToTempFolder(filePathToChangedLines);
  const diffFindings = performStaticCodeAnalysisOnFilesInDiff(scannerCliArgs);
  const existingComments = await getExistingComments(pullRequest);
  const filePathToComments = filterFindingsToDiffScope(
    diffFindings,
    filePathToChangedLines,
    inputs,
    pullRequest
  );
  writeComments(
    existingComments,
    filePathToComments,
    pullRequest,
    hasHaltingError // this is still a "global" variable, but now it's the only one
  );
}

Changes like these are meant to remove variables from global state, creating a more idiomatic program control flow. I'm happy to re-create these changes in the pure javascript version here as well.

Yes, I would like to remove node_modules, however when writing a Javascript GitHub action they actually instruct you to include node_modules:

There is an alternative which involves using vercel to compile all the contents of node_modules into one file, but when I tried following the provided instructions, I was unable to get it to work, so I fell-back on ye olden node_modules folder.
I have created this issue to track the work of removal of node_modules in favor of Vercel.


Requests for additions to the standard libraries

This is a meta-issue for tracking all requests for libraries

[ ] MultiSet
[ ] map2 on lists (for FStar.List.Tot.fst, already in FStar.List.fst)
[ ] Implement all functions from FStar.List.fst in FStar.List.Tot.fst
[ ] No fold for sequences?
[ ] unique on lists containing some eqtype

This idea might not be a good fit for fstar but, I was wondering to what extent there is support for concurrency. Would it be possible to leverage the fstar typesystem to implement a safe concurrency library?

I am not much knowledgeable on that particular topic but I think that it would be very interesting. There is a particular complexity related to realisation due to the fact that F* is extracted to multiple languages. That said there is certainly a common threading model that could be written as a first step.. ?!?

This paper describes an fstar that could support the creation of a safe concurrency library : http://research.microsoft.com/en-us/um/people/nswamy/papers/fstar-jfp.pdf
Does the current fstar support affine types ?

No affine types anymore.
But, you may still be able to define a safe concurrency library using a partitioned heap model, e.g., something like fstar.hyperheap

Added some requests from #816.


performance Performance problem create too many scanner task

Proposed changes
cherry pick the pr: #38430

run buildall


Masterkeys Pro L RGB volume control issue

What are you experiencing an issue with?

[ ] Aurora
[ ] Aurora supported game, (Fill in the game)
[ ] Aurora Wrapper
[ ] Aurora Profile
[ ] Aurora supported device, (Fill in problematic devices)
[ ] Aurora Scripts
[ ] Aurora Updater
[ ] Aurora Lighting issue
[x ] Other, (When using FN+VOLUME UP/VOLUME DOWN to change the volume)

What kind of an issue is it?

[ ] Crash
[ ] Performance problems
[ ] Visual bug
[ ] Localization issue
[ ] Enhancement suggestion
[ ] Device issue
[x ] Other, (it either has a delay, doesn't even react or it repeatedly presses VOLUME UP or VOLUME DOWN)

Expected behavior:
It should normally change the windows volume by 2.
Actual behavior:
When pressing FN+VOLUME UP/VOLUME DOWN there is a high chance that it will repeatedly press the button until it is multiple times presses to stop it. If this isn't the case than there is either a delay or it doesn't even react to that press.
How often does this problem occur?

This problem occurs everytime Aurora is running and I press FN+VOLUME UP/VOLUME DOWN.
Please describe the steps to reproduce this issue:
The issue can be reproduced by doing following steps:

Start Aurora
Press FN+VOLUME UP or VOLUME DOWN multiple times
See a delay, no reaction, volume becoming repeatedly higher or lower without pressing anything

What is the version of Aurora you are experiencing this issue with?

My version is beta v0.6.1-dev4.
Does the previous version of Aurora have this issue?
beta v0.6.0, yes.
Please include any logs, screenshots, or files that are related to this issue:

/

I was unable to replicate the issue with the latest dev build and my CM MK750, are you sure it is an issue with Aurora and not the keyboard? With my Wooting One I sometimes get it spamming the pause button after I click it once, which has nothing to do with Aurora.


Replace opencflite with CoreFoundation from Swift

Package name: CoreFoundation
Latest released version: 6.0

The open-source CoreFoundation is available here, the opencflite repository hasn't been updated since 2015: https://github.com/apple/swift-corelibs-foundation/tree/release/6.0/CoreFoundation
This is already packaged as darwin.swift-corelibs-foundation but the package hard depends on launchd right now so doesn't compile on Linux as-is.

Current version on the unstable channel: 476.19.0
Current version on the stable/release channel: 476.19.0

[x] Checked the nixpkgs pull requests

Related: #110357
Notify maintainers

@reckenrode I suppose, nobody really updated either of these ever since they were added and I think you're doing related toolchain stuff

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

opencflite was updated to 635.21.8 in https://github.com/NixOS/nixpkgs/pull/296780, which is from 2022. The source was changed to https://github.com/gerickson/opencflite/.

Oh, my bad, I missed that. Looks like there is even a release of 1153.18 on the Apple open source page, which would be newer -- but still, that's a release from 2015 if the license header is to be believed, and I read a comment somewhere saying that up to date releases of CoreFoundation are now in that Swift repo.

According to the release notes for that release, opencflite has cherry-picked some changes from newer versions including 1153.18. I don’t think its version corresponds exactly to Apple’s.
Can you elaborate on the need for swift-corelibs-foundation? Darwin doesn’t use swift-corelibs-foundation anymore. It’s from 2018 and probably won’t be updated.

What I want to is the following:

CoreFoundation is packaged twice in nixpkgs when I don't see why it needs to be
Apple's up to date and actively maintained CF is in that Swift repo (kinda has to be since as far as I can tell Swift runtime builds on top of it), and opencflite, even the new repo, isn't getting any of those updates

Hence, my suggestion is, drop opencflite, make Swift CF build for all platforms and move it to pkgs.CoreFoundation (or lowercase, whatever).

Can you elaborate on the need for swift-corelibs-foundation?

I mean idk, it's packaged, both packaged versions are out of date, and there's at least one package depending on opencflite. (I'm considering using it for something I'm working on, at least as an alternative dependency to GNUstep, that's why I came across this in the first place.)

There’s a third implementation in nixpkgs: swiftPackages.Foundation on Linux includes CoreFoundation. There’s no separate libCoreFoundation.so, but the symbols appear to be included in libFoundation.so. One complication is there are no headers. Those would have to be added to the output.
Whether to merge or replace opencflite with the other implementations is up to @wegank, but I would be against adding a top-level CoreFoundation package. It risks creating confusion about whether it should be used on Darwin and could cause packages to depend on it accidentally and unintentionally. The source-based CF was dropped on x86_64-darwin for 23.11, and the changes for 24.11 will finish removing the hooks that supported it. It’s too much of a maintenance burden, and newer releases of macOS have issues with it due to added hardening in the system CoreFoundation.

I want to add that my objection is based on the name and potential to cause issues for Darwin. Moving swift-corelibs-foundation to the top-level (and by-name presumably) is not a bad idea in itself.
From what I can tell, making it build on Linux would involve more work than just dropping launchd. There are also patches for the Darwin build that would have to be made conditional. I also don’t know whether it would use objc4 or some other runtime.


[6.5.x] RHBPMS-4518: Add engine-level reproducer

This adds engine-level reproducer for RHBPMS-4518. Although it is a bug in the engine it mostly influence Workbench remote APIs since signalling there is done through SignalEventCommand.

The reproducer is testExecuteSignalEventCommandWithPerProcessInstanceStrategy which fails but it seems it also affects other tests. I will try to fix it.

The tests have been updated and only the reproducer should fail now.

@livthomas I know this is reproducer but specific case that refers to lie-remote but from jbpm services point of view it's wrong usage. You should use https://github.com/droolsjbpm/jbpm/blob/master/jbpm-services/jbpm-services-api/src/main/java/org/jbpm/services/api/ProcessService.java#L127
taking into consideration RHBPMS-4518 was nack'ed and won't be fixed I opt at closing this. wdyt?

@mswiderski, I know there is a better way to send a signal using ProcessService and I have just tried to reproduce the problem in the underlying functionality of KIE remote service. Since the RHBPMS-4518 has not been approved, we can close this.


Fix incorrect reporting of script instance ids

The layer component of InstanceID isn't maintained so that objects can be moved across layers without updating every script connection. As a consequence of that, the GUI was reporting an incorrect instance ids for objects not on layer 0. I'm not sure if this is the right approach to fixing the problem; it is kind of a hack to just re-add the layer information in the GUI.

Yeah, this definitely isn't the right approach, ideally we'd propogate the ID change down the connection list.


No Volume attach action in VM instance's volume UI page

This feature request is firstly raised in https://github.com/zstackorg/zstack/issues/5
Since it is an UI feature, so open it here:
on UI side,when want to attach volume from Instances,double click instance name,and click Volume Tab,and select Attach Volume from Actions Menu,there is no data volume listed in box.

Fixed


LOW_LATENCY can't play audio with volume bigger than 1.0

More context here: https://github.com/flame-engine/flame/pull/195

This also implies figuring out what volume greater than 1 means, if it makes sense, if it's consistent between android and ios and then fix any inconsistencies and update the docs to reflect that.

We can't play louder than 1.0, closing this.


[Feature]: Allow instance admins to manage users at the instance level

Is there an existing issue for this?

[X] I have searched the existing issues

Summary
Instance admins need the ability to see and manage the details of those who have signed up and created an account.

See the instance level accounts.
See which workspaces a user has access to (across entire instance)
Delete a user account
Reset a password

Why should this be worked on?
Here's an example scenario:
We’re going to run a self-hosted community edition pilot instance. I’m going to invite a handful of users to join the pilot. They’ll Sign Up for an account using the Form Login and be on their way.
After a bit, I’ll want to be able to see who Signed up and created an account. So I’d want to be able to see the instance’s accounts. Or maybe I’ll want to delete a user’s account for some reason. Maybe they leave the company or are no longer part of the pilot. How would I do that?

In my case, my user's, whom I have added, type in the wrong email and set up a new account, which then needs to be deleted as they keep accessing the 'wrong' account, rather than the correct one, by typing in the wrong email, again, and again, and again. In one case, the guy actually created 4, get this, FOUR wrong email accounts, and I have no way to view or delete them. Sigh.

The instance admin should be able to manage users from Admin settings in Community Edition. Community Request
As this is primarily an instance management feature and not an access control feature, we don't need to have the invite user and assign role/group functionality. We can achieve this by showing the Users page of GAC in the community edition and not having the below functionalities. The admin will then be able to keep tabs on users in the instance and remove unnecessary users as required.
Add Users
Edit User (2 entry points - 1. from the 3-dot menu and 2. from clicking on user email)

Needs to be prioritised again.