Driver Interface has Restart, but Host Restart doesn't use it.

Host Restart will do a start and stop regardless of whether there is a specific driver restart method.

+1


music_player.py

The code provides a basic music player interface with features for playing, managing playlists, and controlling playback options. It's a simple, interactive application for playing music files on a computer.

Thank you for contributing @ShashiNova, make sure to check your contributions on GitHub Pages.


Look for "desktop" gradle task in addition to "jvm"

The kotlin multiplatform wizard (https://kmp.jetbrains.com/) now generates projects where the desktop target is called "desktop", not "jvm" as it apparently did previously.
This results in a "desktopJar" gradle task being created -- not the "jar" or "jvmJar" tasks that this plugin looks for.
This PR adds support for finding "desktop" prefixed tasks and classpaths.

Plugin v1.9 is published with this change. Does it work for you?


where the data is?

Hello Team,
Where I can find the data before dedupilcating? I have similar tasks to test dedupilcation algorithms.
Thanks,
Jianshu

We tested our paper on open-source datasets: wiki-40b, C4, LM1B. You can find these datasets in, e.g., TFDS or hugging face.


Recreate from scratch 06 Simple app navigation

Start from 02  change name:

Copy the content of 06 simple app navigation to a local folder
Rename 06 simple app navigation to 05 simple app navigation
Delete all the content in 05 simple app navigation but readme.md
Copy the contents of 02Change name to 05 simple app navigation (but readme.md)
Reproduce the sample from scratch.

Watch out which version or react-router you are installing, check if in the readme stands version 3 not 4

can i work on this ?

Hi @discoveranirban fork and give a shot :), thanks


one to one messaging app

hi
how can i create one to one messaging app?
in fact witch property of socket cluster should i use to create one to one messaging app?

@mahdiyousofun This is a bug tracker. For casual questions, please, use the Gitter chat room.


Added Boltwall Server to the stack

under alt/bitcoind I think we can remove them or add them to .gitignore since they're autogenerated

under alt/bitcoind I think we can remove them or add them to .gitignore since they're autogenerated

Ops!!! I missed that, I just updated the PR


Update dependencies

There are many dependencies that have newer versions with fixes of all kinds, especially security related ones. This PR updates all dependencies to the latest.

Hey @tobert and @nshalman . Is this repo still being maintained?

A few of us at Equinix have been bumping versions along on demand. It may
be worth looking at newer otel launchers that are likely more robust by
now. When we wrote it, it was among the first of its kind.
Thanks Nahum. Let's have a chat in January about responsible ongoing
maintenance of otel-init-go.
-Amy
On Mon, Dec 11, 2023, 12:03 PM Nahum Shalman @.***>
wrote:

@.**** approved this pull request.
I don't know if I count as a maintainer, but we should certainly keep this
repo maintained.
—
Reply to this email directly, view it on GitHub
https://github.com/equinix-labs/otel-init-go/pull/34#pullrequestreview-1775684227,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACWSHSHTUWCUEFAZMNBNM3YI44GJAVCNFSM6AAAAAA7JPKYWOVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTONZVGY4DIMRSG4
.
You are receiving this because you were mentioned.Message ID:
@.***>

newer otel launchers that are likely more robust by now
I didn't realize those existed. I'll have to look around at what's out there.

Smee migrated off like so:
https://github.com/tinkerbell/smee/commit/b10ee0321942f041e7706aab10cc802585a24b48


Add new Lint/RegexpInCondition cop

Problem
If a regexp literal is in condition, the regexp matches $_ implicitly.
For example:
# test.rb
$_ = 'foo'
if /foo/
  p 1
end

$_ = 'bar'
if /foo/
  p 2
end

# It outputs 1, but it does not output 2.
$ ruby test.rb
1

The behaviour is confusing. I guess the feature is designed for one-liner. So, we should not use the feature in production code.
Solution
Add this cop 😄
Lint/LiteralInCondition?
This cop is very similar to Lint/LiteralInCondition cop. But this should be a different cop from Lint/LiteralInCondition.
There are two reasons.
First, these cops target different issues. Lint/LiteralInCondition targets the issue that a condition is evaluated as true. But Lint/RegexpInCondition targets the issue that a regexp literal matches $_ implicitly.
Second, these cops have different implementation.
Note
Currently, this cop does not work on ! and not.
For example:
# This code has the problem, but the cop does not add offence for the code.
!/re/

It is a parser gem's bug, and the bug is already fixed in master.
https://github.com/whitequark/parser/pull/376

Before submitting the PR make sure the following are checked:

[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Used the same coding conventions as the rest of the project.
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[x] Added tests.
[x] Added an entry to the Changelog if the new code introduces user-observable changes. See changelog entry format.
[x] All tests(rake spec) are passing.
[x] The new code doesn't generate RuboCop offenses that are checked by rake internal_investigation.
[x] The PR relates to only one subject with a clear title
and description in grammatically correct, complete sentences.
[x] Updated cop documentation with rake generate_cops_documentation (required only when you've added a new cop or changed the configuration/documentation of an existing cop).

Let's improve the cop name and their messages subsequently.


Conda installation hangs forever

Describe the bug
Very similar to https://github.com/mne-tools/mne-python/issues/10014, however, I'm trying to install several other packages as well. If I remove mne from the list, I'm able to install them (also, slow, but conda is never fast...). With mne included, I waited for about a day give or take a few hours, and it was still at 100% CPU "solving" something. Obviously, this is also a conda bug, but conda is beyond repair, so, unfortunately, others need to work around its problems.
The way I discovered the problem was by running conda build of a project that has a dependency on mne. So, unfortunately, I cannot use mamba, because boa is still in experimental stage. However, further investigation showed that:
conda install -y --strict-channel-priority --override-channels -c conda-forge \
    "python==3.8" \
    "conda==4.13.0" \
    "pandas" \
    "matplotlib" \
    "scipy" \
    "scikit-learn" \
    "h5py" \
    "pyxdf" \
    "mne" \
    "textdistance"

exhibits the same behavior.
This happens on Linux. I don't think that flavor or kernel version etc. are important, but will provide those if you think they are.
Expected results
The library installs in reasonable amount of time (at least under one hour!)
Actual results
No traceback. Also, conda swallows pdb errors, so, it's impossible to debug w/o much setup. When interrupted, the install doesn't show traceback.
Additional information
Impossible to run mne.sys_info() since it fails to install.

It seems like other requirements don't matter. Simply installing mne hangs forever, i.e.:
conda install -y --strict-channel-priority --override-channels -c conda-forge mne

is enough to reproduce the problem.

Further experiments showed that mne-base can be installed in the same context.

what do you mean by context? current environment?

Message ID: @.***>

I mean that it worked with Python 3.8 and conda 4.13.0, also all the other packages listed in the first post can be installed if I replace mne with mne-base.

ok but mne-base is very light weight. mne requires a bunch of stuff (3D
libs, GUIs etc)
can you try on a fresh env or using mamba in you local environment?

Message ID: @.***>

I have to leave now, but I'll loop back to this tonight, so, hopefully will have more results.
Luckily for me, I only really needed the stuff from mne-base anyways, just didn't know it was a thing.

mamba has no problems installing mne with all the same requirements.

so let's use mamba ;)

Message ID: @.***>

ok so if all you really need is mne-base and it works with the version of conda that you want, then this can be closed, yes?  (If not we may need to close anyway as unfortunately there's little we can do to make conda's solver work better)

Maybe drop a line to Anaconda's people? I'm too tired of reminding them how conda is broken. They probably ignore this coming from the same person anyways.
Or, at the minimum, you could write in installation instructions to not use conda, since it doesn't work. Would save people some headache.

Since you seem to be very unhappy with conda, have you tried using pip? This is the official Python package manager, and I have found pip to work extremely well. I do not use conda/mamba for the same reasons you seem to have, so maybe pip is worth a try?

Nowadays we mostly advocate for using our installers. Closing as a (mostly) upstream issue


Is it possible to use drag inside of an iframe?

I'd like to be able to use drag inside of an iframe. I don't need to drag in or out of it, just inside is fine.
It looks like it knows when it's been clicked, but doesn't know the mouse is moving afterwards.
Here's an example: https://codesandbox.io/s/use-gesture-inside-of-iframe-q8s6e

Im not in front of a computer but I understand why this might fail. Try using the pointer or window option see this https://github.com/react-spring/react-use-gesture/pull/48

Sorry, I must have missed that option!
Supplying the window option works perfectly. Thank you!
Updated sandbox for reference: https://codesandbox.io/s/use-gesture-inside-of-iframe-1qowo


Spatial Provider / Observer errors reported with only Core and SDK installed

XRTK - Mixed Reality Toolkit Bug Report
Describe the bug
If you start a new XRTK project with only Core and SDK installed, once you configure a scene you get several errors reported about the Spatial system
To Reproduce

Create a new project
Install XRTK-Core and SDK
Configure a Scene
See error

Expected behavior
No errors, or just a warning about using spatial on a non-spatial system
Actual behavior
4 Errors appear
Unable to register a service with a null concrete IMixedRealitySpatialObserverDataProvider type.
UnityEngine.Debug:LogError(Object)
XRTK.Services.MixedRealityToolkit:CreateAndRegisterService(Type, SupportedPlatforms, Object[]) (at Library/PackageCache/com.xrtk.core@0.1.20/Services/MixedRealityToolkit.cs:852)
XRTK.Services.MixedRealityToolkit:InitializeServiceLocator() (at Library/PackageCache/com.xrtk.core@0.1.20/Services/MixedRealityToolkit.cs:434)
XRTK.Services.MixedRealityToolkit:ResetConfiguration(MixedRealityToolkitConfigurationProfile) (at Library/PackageCache/com.xrtk.core@0.1.20/Services/MixedRealityToolkit.cs:117)
XRTK.Inspectors.MixedRealityToolkitInspector:OnInspectorGUI() (at Library/PackageCache/com.xrtk.core@0.1.20/Inspectors/MixedRealityToolkitInspector.cs:99)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Failed to start Windows Mixed Reality Spatial Mesh Observer!
UnityEngine.Debug:LogError(Object)
XRTK.Services.MixedRealityToolkit:InitializeServiceLocator() (at Library/PackageCache/com.xrtk.core@0.1.20/Services/MixedRealityToolkit.cs:441)
XRTK.Services.MixedRealityToolkit:ResetConfiguration(MixedRealityToolkitConfigurationProfile) (at Library/PackageCache/com.xrtk.core@0.1.20/Services/MixedRealityToolkit.cs:117)
XRTK.Inspectors.MixedRealityToolkitInspector:OnInspectorGUI() (at Library/PackageCache/com.xrtk.core@0.1.20/Inspectors/MixedRealityToolkitInspector.cs:99)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Unable to register a service with a null concrete IMixedRealitySpatialObserverDataProvider type.
UnityEngine.Debug:LogError(Object)
XRTK.Services.MixedRealityToolkit:CreateAndRegisterService(Type, SupportedPlatforms, Object[]) (at Library/PackageCache/com.xrtk.core@0.1.20/Services/MixedRealityToolkit.cs:852)
XRTK.Services.MixedRealityToolkit:InitializeServiceLocator() (at Library/PackageCache/com.xrtk.core@0.1.20/Services/MixedRealityToolkit.cs:434)
XRTK.Services.MixedRealityToolkit:ResetConfiguration(MixedRealityToolkitConfigurationProfile) (at Library/PackageCache/com.xrtk.core@0.1.20/Services/MixedRealityToolkit.cs:117)
XRTK.Inspectors.MixedRealityToolkitInspector:OnInspectorGUI() (at Library/PackageCache/com.xrtk.core@0.1.20/Inspectors/MixedRealityToolkitInspector.cs:99)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Failed to start Lumin Spatial Observer Data Provider!
UnityEngine.Debug:LogError(Object)
XRTK.Services.MixedRealityToolkit:InitializeServiceLocator() (at Library/PackageCache/com.xrtk.core@0.1.20/Services/MixedRealityToolkit.cs:441)
XRTK.Services.MixedRealityToolkit:ResetConfiguration(MixedRealityToolkitConfigurationProfile) (at Library/PackageCache/com.xrtk.core@0.1.20/Services/MixedRealityToolkit.cs:117)
XRTK.Inspectors.MixedRealityToolkitInspector:OnInspectorGUI() (at Library/PackageCache/com.xrtk.core@0.1.20/Inspectors/MixedRealityToolkitInspector.cs:99)
UnityEngine.GUIUtility:ProcessEvent(Int32, IntPtr)

Your Setup (please complete the following information)

Unity Version 2019.1.14
XRTK Version Core - 0.1.20 / SDK 0.1.14

Target Platform (please complete the following information)

Standalone

This isn't a bug, but it makes sense seeing as there aren't any platform specific spatial observers in the project if only the SDK and the Core are installed.
This will likely be something that would be a warning per #331. But it seems that you only did one core service, but not all to be formatted in this way.

Then we should change this to check and be a warning too like the other warnings.  I'll do a PR and update.

Still not sure I agree that it should be a warning though. If you're targeting a platform, and missing the platform dependencies that is a problem the developer needs to address. As far as our default configuration tho, yeah it shouldn't be throwing errors at all unless you really are missing something.

I see the real issue now is the editor platform checking. These should have never ran in the editor anyway since their platform options exclude them from running in the editor.


Update renovatebot/github-action action to 34.23.1

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
patch
v34.23.0 -> v34.23.1

Release Notes

renovatebot/github-action
v34.23.1
Compare Source
See the the changelog for changes in all releases.
34.23.1 (2022-11-12)
Bug Fixes

deps: update renovate/renovate docker tag to v34.23.1 (c40a4e7)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

@balena-ci I self-certify!


ci: Use GITHUB_OUTPUT envvar instead of set-output command

save-state and set-output commands used in GitHub Actions are deprecated and GitHub recommends using environment files.
This PR updates the usage of ::set-output to "$GITHUB_OUTPUT"
Instructions for envvar usage from GitHub docs:
https://docs.github.com/en/actions/using-workflows/workflow-commands-for-github-actions#setting-an-output-parameter

Thanks for fixing this up here as well @arunsathiya!


Markdown syntax fix

Hi @msms6174, I'm your friendly neighborhood Microsoft Open Technologies, Inc. Pull Request Bot (You can call me MSOTBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSOTBOT;

The number of ='s doesn't matter for this kind of heading.


Fix wrong order in params

The order of the params is important in this case, so with the previous implementation the last param was ignored and therefore the file was not saved.

Thank you for merging that. Do you have a plan to release a newer version?

Thanks for the PR.
I will create a new release in about half an hour 😉


[SelectableEnhance] Remove style-propable mixin

Removed unnecessary allocation (comment)

All good :+1:

@newoga Thanks!


Configure injector to ignore constructor parameters of certain types

I'd like to configure Injector to ignore all constructor parameters that are typed with str, int or bool. Is this possible? Right now I have to leave off the type declarations for these parameters, even if they also have a default value. If I don't, it will pass through an empty string for str parameters (not sure about other types).

You can either disable auto_bind Injector-wide (it won't provide types you didn't explicitly bind to implementations) or use noninjectable (https://injector.readthedocs.io/en/latest/api.html#injector.noninjectable) in those cases.

Hang on, but how are you constructing those types that have constructors with str-typed parameters anyway? Either you construct them yourself, and then Injector won't provide anything, or you use AssistedBuilder and Injector will let you fill in the blanks. Can you provide some code?

noninjectable is exactly what I was looking for. Thank you so much!
Using auto_bind wasn't practical in the project I'm working in. I don't recall exactly why now, but I have a feeling it was because it would attempt to auto-bind all classes (including in third-party packages), rather than just non-vendor code. As we still wanted to separate out the DI config from the rest of the codebase, we ended up overriding Injector.create_object() and performing auto-binding there, but only for classes in our own project. This ended up also being the correct place to use noninjectable.

Either you construct them yourself, and then Injector won't provide anything

If I create an instance of this class using Injector.create_object(), then self.param1 ends up as an empty string, rather than the default value specified in the signature.
from injector import Injector

class MyClass(object):
    def __init__(self, param1: str = 'test'):
        self.param1 = param

di = Injector(auto_bind=True)
myobj = di.create_object(MyClass)
print(myobj.param1) # prints '', not 'test'

Oh, I see - I'm glad that noninjectable is helpful here, you're welcome.


cargo check doesn't check documentation code fences

Considering a lot of people would use the output of cargo check in their editors to verify correctness of their code before running their tests, one would assume that cargo check --all would run compiler checks of the code in the docs tests, unfortunately that doesn't seem to be the case.
Current Behavior
It's possible for cargo check --all to run clean but cargo test to fail with compiler errors.
Expected Behavior
When docs have code fences that have compiler errors:
cargo check --all
and a new command option:
cargo check --docs
would fail.

Actually this looks like a duplicate of #3431 -- that issue is still open because cargo check --all does not include tests or doc tests. Closing as a duplicate, thank you for the report! ❤


Duplicate entries in connection with Alex and Happy

This might be the same problem as #353 .
From these files in the source directory:
LBNF
├── Abs.hs
├── ErrM.hs
├── Lex.hs
├── Lex.x
├── Par.hs
├── Par.y
├── Print.hs
├── Skel.hs
└── Test.hs

I am getting this entry in the generate .cabal file:
library
  exposed-modules:
      LBNF.Abs
      LBNF.ErrM
      LBNF.Lex
      LBNF.Lex
      LBNF.Par
      LBNF.Par
      LBNF.Print
      LBNF.Skel
      LBNF.Test

Cabal does not like this:
$ hpack && cabal build
generated Foo.cabal
Resolving dependencies...
Error:
    Module name  LBNF.Lex  is exported multiple times.
    In the stanza 'library'
    In the inplace package 'Foo...'

Manually deleting the duplicate entries helps.
Suggestion: nub the generated list.

@andreasabel hey! Thanks for bringing this up!
Not opposed to your suggestion of remove duplicates.  But I would still want to have the full picture first.
How did Lex.hs/Par.hs end up in your source tree?  I would assume that Cabal generates them in dist/build/autogen (or some new-style equivalent).

Thanks for the quick fix.

@andreasabel hey! Thanks for bringing this up!
Not opposed to your suggestion of remove duplicates. But I would still want to have the full picture first.
How did Lex.hs/Par.hs end up in your source tree? I would assume that Cabal generates them in dist/build/autogen (or some new-style equivalent).

These files have been sitting in the source tree since I originally did not use any cabal configuration for this project (just a Makefile).  To generate a cabal file, I used hpack and then ran into the problem of duplicates.
I think in case of Alex and Happy, my problem can be circumvented by not checking in the generated hs files into the source tree.  However, Alex and Happy are natively supported by Cabal.  Other build tools (such as my own, BNFC) do not enjoy the support by Cabal.  Therefore, I also check in the files generated by the build tool into the source tree.


Fix Jpms test

Fixes #28724
Two issues

remove redundant options after #28291 - this should fix test on Jenkins

github action test use Java11 as default, as gradle setting requires it here: https://github.com/apache/beam/blob/170310ee83a11e0f4dd9010068be7ab08f1fc91c/sdks/java/testing/jpms-tests/build.gradle#L24

Please add a meaningful description for your change here

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI or the workflows README to see a list of phrases to trigger workflows.

Run Jpms Direct Java 17 PostCommit

Example run on fork: https://github.com/Abacn/beam/actions/runs/6342390089/job/17228019422 the test runs (though failing due to gcs credential not exist in fork). On beam repo currently test jar fails to compile

R: @magicgoody @damccorm

Run Jpms Direct Java 17 PostCommit

Run Jpms Direct Java 17 PostCommit

Run Jpms Direct Java 11 PostCommit

Run Jpms Direct Java 11 PostCommit

Run Jpms Direct Java 17 PostCommit

I don't think I understand the current or desired test behavior here well enough to review without doing some more research, so I will defer to @kennknowles for review

I restarted the failed job, which seems to have failed to upload the cache. Seems there may be concurrency errors in Gradle caching. Not sure if that is GHA related or just Gradle remote cache generally.

thanks, now all tests passed (the one in checks and github action postcommits - commented above)


Question about Polaris

Did the authors of Polaris, Shopify, really setup up their styles with RGD colors like I see in this repo?
 background-color: rgb(246, 246, 247)

Is that unique to this repo? Just curious. Would it not have been better to have swappable palettes? I enjoy how Tailwind does color and palettes. So I am wondering, did Shopify miss the bus or something?

Most of the time Polaris uses Tokens via CSS variables: https://polaris.shopify.com/tokens/colors
This gem is still on Polaris 7, so some components might be using an old approach. I'm working on upgrading gem to Polaris 10.


fix(align-equals): align named factories as well

What & Why
Sometimes in our codebase, we export factories and require them to be used in tests instead of relying on the global Factory object. This results in the following code:
const UserFactory = require('../factories/user');

const user = UserFactory.build();

This PR also considers *Factory variables when checking for alignment.

LGTM

LGTM


Pytree Protocol

Hey! I'd like to propose that apart from the current registration mechanism JAX allowed users to define pytrees via a Pytree Protocol. There are two reasons for doing this:

Simplifies the definition of custom Pytrees. Currently the best mechanism is to ensure that a class and all its subclasses are registered is to override the __init_subclass__ method and perform the registration there, implementing a protocol is more straightforward as __init_subclass__ is not widely known.
As the concept of a Pytree becomes more wide spread within the Python ecosystem (e.g. pytorch/pytorch#65761, and dm-tree) a protocol could be a simple way of getting cross-library compatibility if the different implementations adopt it.

Implementation
The idea would be to take the same mechanism implemented in register_pytree_node_class but with "special methods":
class Pytree(Protocol):
    def __tree_flatten__(self) -> Tuple[Sequence[Any], Any]:
        ...

    @classmethod
    def __tree_unflatten__(cls, children: Sequence[Any], aux: Any) -> Any:
        ...

Any object that defines these method would be treated as a Pytree at runtime.
Other comments/ideas

Pytree seems like a general concept orthogonal to numeric computing, making JAX's Pytree implementation a separate project that JAX depended on would have a positive impact on the whole Python ecosystem.
Libraries that focus on general Pytree manipulation like Treeo could start to be useful independent of JAX.

@froystig My initial thought was that this protocol would be used with unregistered types that implement it, but the registration mechanism would still be around because of what you say about basic python types.
If the protocol will me expanded with an additional metadata field it would be nice if additional information from the caller like is_leaf is passed through it to the user. As a motivation for this, I found a solution to #7919 but it didn't work if is_leaf was passed to tree_flatten because jax currently doesn't forward that information.

@froystig My initial thought was that this protocol would be used with unregistered types that implement it, but the registration mechanism would still be around because of what you say about basic python types.

What I was hoping to convey is not only that a registry would still be around, but that we might consider explicitly passing it to tree_flatten and to the flatten/unflatten methods of the protocol in order to keep recursive flattening well-defined. JAX's registry is currently a hidden input to the pytree library, but if we fork a library for pytrees (per https://github.com/pytorch/pytorch/issues/65761#issuecomment-936507005) then there will naturally be several such registries.

@hawkinsp mentions sorting out the order of arguments to tree_unflatten. If we're willing to make a compatibility break like that, then there's a couple of other things that I think might be desirable to sort out at the same time:
"PyDags"
(c.f. #7919)
At present unflatten(flatten(...)) is not the identity function.
It will create separate copies of elements that appear multiple times in the tree. There are times when this is undesirable; a notable one is when using PyTrees to represent parameterised functions -- e.g. a PyTorch-like Module system -- a la Equinox, Treex etc.
In principle I don't think this should break any existing PyTree uses: these assume referential transparency so they should be agnostic to whether they get a copy of each leaf/subtree or not.
No auxiliary data
This is something I've been thinking about for a while now. My current belief is that the auxiliary data output is actually unnecessary.
I think this is muddling up two separate notions: (a) partitioning a PyTree into two (or even n) pieces; (b) (un)flattening a PyTree. A simpler/neater API is to have everything be a leaf, and then invoke some tree1, tree2 = partition(tree, partition_rule) -- or even some tree1, tree2, tree3 = partition(...) etc. -- and then pass tree1 and tree2 separately across an API boundary. Each of tree1, tree2 are PyTrees with the same structure as tree; each contain some subset of the leaves and have some dummy value for the leaves they don't have.
The above discussion on custom flatteners corresponds to a choice of partition rule.

PyDags

I totally agree with @patrick-kidger that if there is going to be a refactor / formalization its a great opportunity to support PyDags.

No auxiliary data

This would mean that in general for Mappings, keys would be leaves which would be very inconvenient for a simple tree_map over a dict.

This would mean that in general for Mappings, keys would be leaves which would be very inconvenient for a simple tree_map over a dict.

I think this should be doable. Choosing just the values would be part of a partition rule. (I think the cleanest API for this is still up for debate, though.) Conversely, having the keys static means that it is currently impossible to do a tree_map over the keys of a dict.


add nodeSelector for lb-svc

Pull Request

[ ] Make sure you have followed Kube-OVN Code Style.

What type of this PR

Features

Which issue(s) this PR fixes
Fixes #4756

Pull Request Test Coverage Report for Build<PHONE_NUMBER>6
Details

0 of 25 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 18.668%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/controller/service_lb.go
0
25
0.0%

Totals

Change from base Build<PHONE_NUMBER>8:
-0.01%

Covered Lines:
8682

Relevant Lines:
46507

💛  - Coveralls


yard doc first pass on elasticache code

It feels like the Yard docs are repetitive, but let's see what docs we can generate with them.
This also include ref_elasticache.rb. ref_full.rb + additional specs coming in another PR.

Nice! :shipit:

@dblessing if you have time to look at the docs that would be nice

@metadave some minor comments, but once those are addressed I'm :+1: - this should also get a squash before merging

Going ahead and merging this since its better than what we have!


Work in progress: node-fetch v2

DO NOT MERGE
This PR will be continuously updated as more updates roll in. Feel free to initiate pull requests against this branch to help with this process.
Work needed to be done

[x] Use Babel
[ ] Add iterator interface to Headers (#174)
[ ] Convert all classes to use the class keyword
[ ] Split and merge #140

Discussion

Code style: it seems to be preferred that spaces are used instead of tabs for most people (myself included), so should we use that instead?

Convert all classes to use the class keyword

What's the advantage of doing this? It's perfectly valid to use prototypes with es6.

Code style: it seems to be preferred that spaces are used instead of tabs for most people (myself included), so should we use that instead?

Oh gosh +1

Coverage remained the same at 100.0% when pulling 2874af4218c059e9990de47596d0d9da1872cdf9 on v2 into 3c053ce32760d2d5d6cb8712fb4115b44e4083d4 on master.

Coverage remained the same at 100.0% when pulling 2874af4218c059e9990de47596d0d9da1872cdf9 on v2 into 3c053ce32760d2d5d6cb8712fb4115b44e4083d4 on master.

Code style: it seems to be preferred that spaces are used instead of tabs for most people (myself included), so should we use that instead?

Tab is just my preference, if Node.js community like spaces, I say why not.

Can you add use const/let instead of var + use strict?

Are they worth it for the incompatibility they bring? If you use Babel, you end up with a polyfill anyway?

It's perfectly valid to use prototypes with es6.

Yes, but ES6 classes are a bit easier to read in my opinion.

Babel transpile what you want it to transpile. That's the good thing about modular

Coverage remained the same at 100.0% when pulling 993d4cdea1b63db4ec41a994873e6044f26cde85 on v2 into 3c053ce32760d2d5d6cb8712fb4115b44e4083d4 on master.

I have a second thought on code style: it might actually be better to keep tabs just because we can see the actual changes in files (formatting them to spaces and we lost ability to view blame in github).
If we are making breaking changes might as well make it easy for others to troubleshoot breaking changes.

Sounds good to me.

Coverage decreased (-0.7%) to 99.291% when pulling 838071247d986a3f706392640ea299ec37f67073 on v2 into 3c053ce32760d2d5d6cb8712fb4115b44e4083d4 on master.

On item WHATWG streams support:
Do we want WHATWG stream on Node.js? Or do we just want similar API so people can write isomorphic code (res.body.getReader etc.)?
I still don't know how Node.js Streams and Web Streams are going to consolidate, and then there is adoption, do we start to see modules that accept both type of streams?
I think it's safe to assume as of now, if a developer opt to use Web Streams on Node.js, they probably need to patch/rewrite existing modules from ground up to avoid conversion between streams.

Coverage remained the same at 100.0% when pulling 4d81cb4877cb047c46abd2fdbd3086d9ea16b8f9 on v2 into 3c053ce32760d2d5d6cb8712fb4115b44e4083d4 on master.

Coverage remained the same at 100.0% when pulling 4d81cb4877cb047c46abd2fdbd3086d9ea16b8f9 on v2 into 3c053ce32760d2d5d6cb8712fb4115b44e4083d4 on master.

Coverage remained the same at 100.0% when pulling c2c6550e549e34ea0ce65a9fac9b7d1c80a61498 on v2 into 3c053ce32760d2d5d6cb8712fb4115b44e4083d4 on master.

Coverage remained the same at 100.0% when pulling 67326e3873ba1ee3dff79871f256fdf77dff0ab2 on v2 into 3c053ce32760d2d5d6cb8712fb4115b44e4083d4 on master.

Current coverage is 100% (diff: 100%)

No coverage report found for master at 3c053ce.

Powered by Codecov. Last update 3c053ce...b9b0341

@bitinn said:

Do we want WHATWG stream on Node.js? Or do we just want similar API so people can write isomorphic code (res.body.getReader etc.)?

Indeed, I think most people wanting to use WHATWG streams probably do so for the isomorphism provided by them. WHATWG streams can be easier to use than Node.js streams. How about we just use the same approach I took for textConvert()? Make body a getter for the WHATWG stream, while adding a rawBody getter that maintains the current behavior for body?

Make body a getter for the WHATWG stream, while adding a rawBody getter that maintains the current behavior for body?

I think it's worth keeping res.body.pipe compatible with Node.js stream, 2 arguments:

As far as I know, WHATWG stream will avoid pipe() method, so there won't be any confusion, if you use pipe(), you want Node.js streams.

It will break many codebases, I consider text() with non-UTF encoding support a fairly minor use cases (important only if you use node-fetch as a crawler). But removing pipe() from body may cause many users to not upgrade.

So I say we keep res.body.pipe even though it's not in spec.

WHATWG streams can be easier to use than Node.js streams

I haven't seen a popular WHATWG streams implementation, so people really use it on Node.js?

I saw that #185 was merged behind a global flag. I think that this is very bad for a number of reasons. First of all, I think that following the spec should be the behavior that we want. Secondly, it totally breaks your expectations when requiring the library. If you depend on two libraries which both uses node-fetch, one doesn't set FOLLOW_SPEC and the other one sets it to true. Then the behavior will be modified for the one library that didn't set any flags.
What would be the downside to having the Headers follow the spec be the only available behavior?
ping @TimothyGu

So I found #181 and I now understand why one would maybe not want to follow the spec exactly at this point 😞
My second point still stands though, since that global flag is shared between all users of the library, I really think that it should be solved in another way...

Just needed Response.redirect today... Almost created a new issue


Improved 'fonts' task

The fonts task scans bower_components and includes every font found in the build.
This is not an optimal solution for two reasons:

Scanning all of bower_components is slow
You might get more fonts than you want, e.g. the modernizr package includes some fonts for testing that you probably don't want even though you use modernizr

I have used this task as a workaround for a specific project:
gulp.task('fonts', function () {
    return gulp.src('bower_components/material-design-icons/iconfont/**/*.woff*')
        .pipe(gulp.dest('target/tmp/fonts'))
        .pipe(gulp.dest('target/dist/fonts'));
});

but a more permanent solution would be welcome :)
I guess you should be able to configure which fonts to include.

Well, we will need of some kind of a list (in config section of the gulpfile.js), saying what fonts we want to include.
Scanning the whole node_modules will remain as a default behavior.
Will such solution work for you ?

We would prefer to set a list of folders to scan by gulp. It could be gulpfile.js.

Yes, a list of folders in the gulpfile configuration would be fine for me.

ok then, expect the update :sunglasses:

released 0.0.37


Query beginendblock-panic.ql : potential problems

Hi,
Thanks for this great repo!
I was recently looking into the beginendblock-panic.ql and trying to understand it.
In particular, the query uses mayPanic() as an indicator that the function would panic.
The problem is, however, that mayPanic() will return true almost always, the only exception being a couple of built-in functions (as discussed in this codeQL issue).
This also means that the beginendblock-panic.ql will not be precise (because mayPanic() is not precise).
I believe there is a second problem in the query: namely, calling getParent*, which repeatedly calls the function getParent.
The problem is that getParent is not returning a function call parent, but an AST node parent (where the top ancestor is a file in which the call resides) .
Does this make sense?
In case I got things wrong, please let me know.

For the context: the discussion and the resolution of this issue is in the PR #4


Spatial search filter

From @rukku on November 25, 2015 10:58
Scenario:
User inputs a place name (provinces level for now, lower if possible) and the map will zoom to that area's extents/bounding box.
Copied from original issue: phl-microsat-dpad/libra#10

May be we can use Geonames API or Nominatim for the initial setup. We can also dump the Geonames data for the Philippines in Postgis so we can have our own geocoding service.
Geonames Data
http://www.geonames.org/export/
Geonames for Postgis
https://github.com/jvarga/geonames-for-postgis
Dumping geonames data into postgis
https://github.com/colemanm/gazetteer/blob/master/docs/geonames_postgis_import.md


added server use cause description

Список команд бота #13

@dronmdf please, pay attention to this pull request

Job gh:dronmdf/telebot#26 is in scope.

Bug was reported: +15 points just awarded to @chniks, total is +15.

Job gh:dronmdf/telebot#26 assigned to @alexandersamrega, please go ahead (policy).

@ChNikS Ты первый. Поздравляю.

@0crat assign me

@0crat assign me (here)

@DronMDF Job gh:dronmdf/telebot#26 assigned to @dronmdf, please go ahead (policy).

Oops! You need to have one of these roles in order to do what you're trying to do: ARC, PO. I'm sorry to say this, but at the moment you've got no roles in this project (your GitHub login is "0crat").

Oops! You need to have one of these roles in order to do what you're trying to do: ARC, PO. I'm sorry to say this, but at the moment you've got no roles in this project (your GitHub login is "0crat").

@dronmdf this job was assigned to you 8 days ago.
It will be taken away from you after 10 days from start (this is our policy).

@dronmdf resigned from gh:dronmdf/telebot#26, please stop working.

Oops! Job gh:dronmdf/telebot#26 is not assigned to anyone.

Oops! Job gh:dronmdf/telebot#26 is not assigned to anyone.

@0crat out (here)

@DronMDF @meladark resigned from gh:dronmdf/telebot#26, since the job is not in scope anymore.

@0crat out (here)

@DronMDF Job gh:dronmdf/telebot#26 is now out of scope.


Add terraform completion

Recreating https://github.com/robbyrussell/oh-my-zsh/pull/3499
CC @pmoust @robbyrussell @dlsniper

Looks great overall, minor stuff missing. one could go through https://www.terraform.io/docs/commands/index.html to check for more.
imho, it's great to have this merged in. If an update is due (and it's bound to be since TF is only v0.6.1 and wildly adopted) the community will offer it pretty fast.

I'll send a PR against the repo @gkze has shortly fixing the above issues and doing a read on all the commands / options to be sure none is missed.

I've sent the PR with the changes but I have one doubt about it. Could someone please help me with the push command as it's a bit more tricky: terraform remote SUBCOMMAND [options] where SUBCOMMAND is one of these: config, pull and push and then the options apply. Thank you.

Thank you again @dlsniper and @pmoust ! I just merged the v0.6.1 updates into my fork

@dlsniper not sure, googling right now :)

Let's pull in what we have at least.
/cc @robbyrussell


Expose the default-client and default headers

Draft PR, gathering feedback. Still WIP.

Implemented the default header merging like what i understand curl does. Not sure if that's the best way. Maybe the implementation could be more generic?

@lispyclouds I made a PR myself here: https://github.com/babashka/http-client/pull/9
My intention wasn't to expose the default client itself, but only the options to construct it. Re-using the default client over multiple requests has the benefit of re-using connections if you make multiple requests.
I also added the option to pass :request options to client so it remembers those options whenever you make a request. I used that in the construction of the default client.
Let me know if you spot anything weird.

yep, looks much better! closing mine.

Thanks, your PR helped the hammock process even if it wasn't merged ;)

yeah it was a lot of fun for me too! avoiding the deep merge is probably a better choice.


More configurability

Add the ability to choose between debug/release. Pass down any other useful rustc flags.

Being able to pass arguments to libfuzzer, such as -max_size= or the location of the corpus, would also be useful. Currently I run cargo fuzz --fuzz-target fuzzer_script_1 to trigger the build, kill it, and then I start fuzz/target/debug/fuzzer_script_1 with the desired flags.
Simply passing on any extra arguments to the target program would be sufficient.

Yep. cargo fuzz --fuzz-target foo -- FUZZ ARGS BLAH BLAH is what we'd probably use.

You can pass args to the underlying binary now
(try cargo fuzz run target -- -help=1)
It is still desirable to have more configuration for how the fuzz target is compiled (release/debug, debug-assertions on or off, etc)

Just asking for confirmation: Ignoring a function/crate (like https://clang.llvm.org/docs/SanitizerSpecialCaseList.html) would need rustc support, right?
(In my case rayon is triggering ASan though I believe that is https://github.com/rust-lang/rust/issues/39882.)

No, not really. It likely can be expressed through -C llvm-args in RUSTFLAGS.

I did try RUSTFLAGS="-C llvm-args=-fsanitize-blacklist=blacklist.txt" cargo fuzz run fuzzer_script_1 but that only results in
error: failed to run `rustc` to learn about target-specific information
Caused by:
  process didn't exit successfully: `rustc - --crate-name ___ --print=file-names -C llvm-args=-fsanitize-blacklist=blacklist.txt -Cpasses=sancov -Cllvm-args=-sanitizer-coverage-level=3 -Zsanitizer=address -Cpanic=abort --crate-type bin --crate-type dylib --crate-type proc-macro --crate-type rlib --target x86_64-unknown-linux-gnu` (exit code: 1)
--- stderr
rustc: Unknown command line argument '-fsanitize-blacklist=blacklist.txt'.  Try: 'rustc -help'
rustc: Did you mean '-dfsan-abilist=blacklist.txt'?

Research led me to this commit hence my assumption.


Installation fails due to conflicting redis version

Hi, users are unable to run ScrapyRedisBloomFilterBlockCluster due to dependency conflict with redis package.
As shown in the following full dependency graph of ScrapyRedisBloomFilterBlockCluster, ScrapyRedisBloomFilterBlockCluster requires redis>=2.10，while redis-py-cluster requires redis==2.10.6.
According to pip’s “first found wins” installation strategy, redis==3.3.6 is the actually installed version. However, redis==3.3.6 does not satisfy redis==2.10.6.
Dependency tree
scrapy-redis-bloomfilter-block-cluster-1.0.1
| +-redis(version range:>=2.10)
| +-redis-py-cluster(version range:>=1.3.4)
| | +-redis(version range:==2.10.6)
| +-scrapy(version range:>=1.4)
| | +-queuelib(version range:*)
| | +-twisted(version range:>=13.1.0,<=19.2.0python)
| | +-twisted(version range:>=13.1.0python)
| | +-w3lib(version range:>=1.17.0)
| +-six(version range:>=1.5.2)
| +-twisted(version range:==18.9.0)

Thanks for your help.
Best,
Neolith

Solution

Fix your direct dependency to be redis==2.10.6 redis-py-cluster==1.3.6 .
I have checked this revision will not affect your downstream projects now.
Fix your direct dependency to be redis-py-cluster==1.3.4，and redis>=2.10.2
Ask your upstream project redis-py-cluster to loose the version range of redis.

Which solution do you prefer, 1 or 2?
@leffss Please let me know your choice. I can submit a PR to solve this issue.

Repaired in lastest version.


package.json repository info

Describe what happened
repository data is not properly declared in your package.json and, as side-effect, NPM page does not link to this Github project.
Steps to reproduce the issue:

Open https://www.npmjs.com/package/@datadog/build-plugin
No links to this repo is found

Expected behaviour:
repository data properly declared as in documentation:
https://docs.npmjs.com/cli/v10/configuring-npm/package-json#repository
Actual behaviour:
Incorrect declaration
Additional context

Thanks for the heads up and sorry for the delay.
We're currently revamping the plugin, and this will be covered in the next major release.


Figuring out how to proceed on Windows

Windows is the worst, because is designed by the monkeys of the monkeys for the monkeys. Unfortunately we shall deal with it, offering a Windows way of life for people wanting to use MoorDyn (i.e. not spending much neurons on the task).
The Python solution is on its way:
https://github.com/FloatingArrayDesign/MoorDyn/pull/132
But on C we have some problems... Mainly because MinGW and MSVC are not compatible. Each one has its merits...

MinGW can easily deal with fortran, but it is rather impossible to build the Python wrapper on any modern CPython implementation, i.e. > 3.4 (see https://wiki.python.org/moin/WindowsCompilers#GCC_-MinGW-w64.28x86.2C_x64.29).
 On the other hand, it can easily deal with Python and VTK.

Thus, I suggest to change the documentation:

Recommend to Python users to install it with pip
Recommend to Windows C users to use the installer provided on the automatic releases (https://github.com/FloatingArrayDesign/MoorDyn/releases/download/nightly/Moordyn-2.2.0-win64.exe was the last one)
Provide a compilation guide for both MSVC and MinGW for more advanced users (if they want to deal with that)

Can any of you, @RyanDavies19 or @AlexWKinley, try out the Windows installer? it is a bit outdated, but shall be functional anyway

@sanguinariojoe I am on MacOS so I can't. However someone from the WECSim team has compiled for windows (with the Matlab wrapper). He said it worked fine once he disabled the Fortran and Python wrappers.

Trying out the windows installer I've thus far run into 2 strange issues.
Firstly, during the install process, when I ask it to add MoorDyn to the system path the installer throws an error that the system path is too long, and it can't add to it.

I'm certainly able to add to the path myself, so I'm not sure what's the cause of this error.
The next issue I ran into when trying to use the installed MoorDyn was that it wanted the moordynf.lib file but it didn't exist.
My cmake file looked like
cmake_minimum_required(VERSION 3.10)

project(MDTest)

add_executable(MDTest
    src/main.cpp
)

find_package(MoorDyn REQUIRED)
target_link_libraries(MDTest
    MoorDyn::moodyn
)

And the output of running cmake (through vscode) is
[proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -SC:/Users/A.Kinley/Documents/moordyn_install_test -Bc:/Users/A.Kinley/Documents/moordyn_install_test/build -G "Visual Studio 17 2022" -T host=x64 -A x64
[cmake] Not searching for unused variables given on the command line.
[cmake] -- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.22621.
[cmake] CMake Error at C:/Program Files/MoorDyn-2.2/lib/cmake/moordyn/MoorDynTargets.cmake:98 (message):
[cmake]   The imported target "MoorDyn::moordynf" references the file
[cmake]
[cmake]      "C:/Program Files/MoorDyn-2.2/lib/moordynf.lib"
[cmake]
[cmake]   but this file does not exist.  Possible reasons include:
[cmake]
[cmake]   * The file was deleted, renamed, or moved to another location.
[cmake]
[cmake]   * An install or uninstall procedure did not complete successfully.
[cmake]
[cmake]   * The installation package was faulty and contained
[cmake]
[cmake]      "C:/Program Files/MoorDyn-2.2/lib/cmake/moordyn/MoorDynTargets.cmake"
[cmake]
[cmake]   but not all the files it references.
[cmake]
[cmake] Call Stack (most recent call first):
[cmake]   C:/Program Files/MoorDyn-2.2/lib/cmake/moordyn/MoorDynConfig.cmake:19 (include)
[cmake]   CMakeLists.txt:10 (find_package)
[cmake]
[cmake]
[cmake] -- Configuring incomplete, errors occurred!
[proc] The command: "C:\Program Files\CMake\bin\cmake.EXE" --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -SC:/Users/A.Kinley/Documents/moordyn_install_test -Bc:/Users/A.Kinley/Documents/moordyn_install_test/build -G "Visual Studio 17 2022" -T host=x64 -A x64 exited with code: 1

I'm not familiar enough with how things are set up and the like to know if this is an error of my own causing, or if a file isn't getting included that should be.
Keep me in the loop if there's anything I can do to help with windows stuff, Kelson primarily uses Windows so I have access to both my development machine and other machines that are yet untouched by MoorDyn.

Argh! Sorry! Totally my bad... the installer (master branch) is way more
outdated than i thought. It is still using the intel one sdk.
I will try to craft you an installer later.
Ty so much!
On Thu, 21 Sept 2023, 19:00 AlexWKinley, @.***> wrote:

Trying out the windows installer I've thus far run into 2 strange issues.
Firstly, during the install process, when I ask it to add MoorDyn to the
system path the installer throws an error that the system path is too long,
and it can't add to it.
[image: Screenshot 2023-09-21 125326]
https://user-images.githubusercontent.com/129765925/269697166-8c18968f-484b-48eb-ac91-1c95783669c6.png
I'm certainly able to add to the path myself, so I'm not sure what's the
cause of this error.
The next issue I ran into when trying to use the installed MoorDyn was
that it wanted the moordynf.lib file but it didn't exist.
My cmake file looked like
cmake_minimum_required(VERSION 3.10)
project(MDTest)
add_executable(MDTest
src/main.cpp
)
find_package(MoorDyn REQUIRED)
target_link_libraries(MDTest
MoorDyn::moodyn
)
And the output of running cmake (through vscode) is
[proc] Executing command: "C:\Program Files\CMake\bin\cmake.EXE" --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -SC:/Users/A.Kinley/Documents/moordyn_install_test -Bc:/Users/A.Kinley/Documents/moordyn_install_test/build -G "Visual Studio 17 2022" -T host=x64 -A x64
[cmake] Not searching for unused variables given on the command line.
[cmake] -- Selecting Windows SDK version 10.0.22000.0 to target Windows 10.0.22621.
[cmake] CMake Error at C:/Program Files/MoorDyn-2.2/lib/cmake/moordyn/MoorDynTargets.cmake:98 (message):
[cmake]   The imported target "MoorDyn::moordynf" references the file
[cmake]
[cmake]      "C:/Program Files/MoorDyn-2.2/lib/moordynf.lib"
[cmake]
[cmake]   but this file does not exist.  Possible reasons include:
[cmake]
[cmake]   * The file was deleted, renamed, or moved to another location.
[cmake]
[cmake]   * An install or uninstall procedure did not complete successfully.
[cmake]
[cmake]   * The installation package was faulty and contained
[cmake]
[cmake]      "C:/Program Files/MoorDyn-2.2/lib/cmake/moordyn/MoorDynTargets.cmake"
[cmake]
[cmake]   but not all the files it references.
[cmake]
[cmake] Call Stack (most recent call first):
[cmake]   C:/Program Files/MoorDyn-2.2/lib/cmake/moordyn/MoorDynConfig.cmake:19 (include)
[cmake]   CMakeLists.txt:10 (find_package)
[cmake]
[cmake]
[cmake] -- Configuring incomplete, errors occurred!
[proc] The command: "C:\Program Files\CMake\bin\cmake.EXE" --no-warn-unused-cli -DCMAKE_EXPORT_COMPILE_COMMANDS:BOOL=TRUE -SC:/Users/A.Kinley/Documents/moordyn_install_test -Bc:/Users/A.Kinley/Documents/moordyn_install_test/build -G "Visual Studio 17 2022" -T host=x64 -A x64 exited with code: 1
I'm not familiar enough with how things are set up and the like to know if
this is an error of my own causing, or if a file isn't getting included
that should be.
Keep me in the loop if there's anything I can do to help with windows
stuff, Kelson primarily uses Windows so I have access to both my
development machine and other machines that are yet untouched by MoorDyn.
—
Reply to this email directly, view it on GitHub
https://github.com/FloatingArrayDesign/MoorDyn/issues/135#issuecomment-1729965658,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAMXKKAOSKADK47FQXSYMGLX3RXA7ANCNFSM6AAAAAA5BJ6QWQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@AlexWKinley you have the new installer here. Please, give it a shot

@sanguinariojoe Well besides the same path error problem, it unfortunately still doesn't seem to work, but for a different reason.
I used the same cmake file (although fixed the typo in target link libraries), and now it succesfully builds, but when trying to run, it tries to find a moordyn.dll, fails, and then exits. It seems like the installer provided a moordyn.lib, which somehow didn't get statically linked I guess? If I look at the executable dependencies, it lists moordyn.dll, and that it didn't find it

I'll attach the entire test project folder, including the build folder, in case that provides any useful information.
I did compile with clang on windows (using the windows toolchain), but compiling with MSVC ran into the same issue, and I figured the ninja files, and clang commands might be a little easier to look through than solution files.
We're in agreement on the frustration of windows. As always let me know what assistance I can provide.
moordyn_install_test.zip

I tried this and works just fine with your test @AlexWKinley . Regarding the PATH issues, it is caused by your own PATH which is already too long. In my testing computer it worked

@sanguinariojoe It looks like once I fix my path to have C:\Program Files\MoorDyn-2.2\bin, then worked with that build you linked. I would agree my path is probably longer than most users'. So I'm in agreement that things work.

This is then fixed on #139


Should check global permissions firstly

I'm implementing the tests for your project.
The problem occur when I'm trying to add a new object checking for this permissions. I have to assing a global permission when that's not a dependent model, but that permission is never checked.
E.g: (This should be true, but is not working today)
def test_post_list_with_permission(self):
        assign_perm('test_app.add_project', self.user)

        # [fixme] - should check firstly global permissions!

        resp = self.api_client.post(
            self.api_url,
            format='json',
            authentication=self.get_credentials(),
            data=self.build_data_to_post()
            )

        self.assertHttpCreated(resp)

This was fixed

This was fixed


Rework grid plugin

The grid plugin is currently a mess. It needs a huge rework, and it must support the following things:

Support animating more than 1 window at a time
Restore the geometry on set_maximized(false) when maximized to any of the slots
Change tiled windows' geometry on the reserved-workarea signal

Another possibility is to expand the tiling plugin to tile only specific views and integrate grid and tile. However, this will require much more work to the unfinished tile plugin and possibly goes outside of its scope.

Resolved in master.


DraftJs current editor focus should be inbuilt

Do you want to request a feature or report a bug?
feature In case of multiple DraftJS editors. The draftJs requires a container element and a ref to get into focus.
What is the current behavior?
Extra code require for something which should be built by default into the container
If the current behavior is a bug, please provide the steps to reproduce and if possible a minimal demo of the problem.
The current recommendation by DraftJS is not a clean implementation of an editor should come into focus mode.
What is the expected behavior?
The DraftJS should automatically detect that when a user is typing into the box it is in focus.
Which versions of Draft.js, and which browser / OS are affected by this issue? Did this work in previous versions of Draft.js?
All versions of DraftJS.

The recommended link : https://draftjs.org/docs/advanced-topics-managing-focus/#translating-container-clicks-to-focus


Allow logging to slf4j

Is your feature request related to a problem? Please describe.
As user of the fhir-validation-distribution we would like incorporate info / warning / error log messages into our own logs.
Describe the solution you'd like
Provide slf4j as a logging option.
Describe alternatives you've considered
Additional context
It looks like there is some Java logging used, but it does not appear to be universal. For example, FHIRValidator does not log and instead uses a public DEBUG static to switch on console output.

We do not plan on moving from java.util.logging to slf4j. There is a JUL -> SLF4J bridge available here:
http://www.slf4j.org/api/org/slf4j/bridge/SLF4JBridgeHandler.html
This can be used in conjunction with:
http://logback.qos.ch/manual/configuration.html#LevelChangePropagator

Per discussion, we addressed any System.out calls and put as loggers and tuned the logging.
Please let us know if we can further help.


Document how to run with a UI

Once https://github.com/kiva/ssi-wizard-sdk/issues/67 and https://github.com/kiva/protocol-gateway/issues/41 are complete, document here how to run the entire Protocol stack on localhost.

I am adding the following work breakout.

[ ] get the front end running locally.  There is a configuration change required.
[ ] get the front end running on both Mac
[ ] and Windows
[ ] get the back end running on windows
[ ] writing step by step documentation for running entire stack on windows
[ ] writing step by step documentation for running entire stack on macos


Idea: Per-tier configuration of EMC generators, links, and power flowers

Currently, almost all of the EMC related stats for the new blocks and items added by the mod are hard-coded, including:

The per-second EMC generation for collectors.
The per-second EMC transfer rate and bonus for relays.
The per-second EMC generation multiplier for power flowers.

This is currently configurable globally, but not per-tier.

The per-second EMC limit for EMC Links.
The per-second item I/O limit for EMC Links.

With the default values being proportional to O(n!) in the tier of the block, the scaling may be too harsh and some modpacks may want to nerf the higher tiers, while leaving the lower tiers untouched. On the other hand, a modpack may make each tier cost a lot more EMC than the last, to the point where the total cost quickly outpaces the default values.
I propose adding the following six lists to the config, one for each of the seven values, with one entry per tier starting at tier 1 and going through the final tier:

Collectors - Production rate (EMC/s)
Relay - Max transfer rate (EMC/s)
Relay - Bonus rate (EMC/s)
Power Flower - Multiplier (EMC/s)

The actual generation rate is derived from the production and bonus rates for the collectors and relays respectively.

EMC Link - Max EMC import limit (per second)
EMC Link - Max item I/O limit (per second)

Ideally, the values in the new config options should be able to support numbers up to 1.79769×10308.
If that's not possible, the next best upper limit is 263-1 ≈ 9.223 quintillion.

I'm absolutely not going to make a config option for every single tiered block, at best you're getting a multiplier
powerflowers already have this and I have no plans to spread this to other blocks


bug: error after updating

What version of daisyUI are you using?
3.9.4
Which browsers are you seeing the problem on?
Firefox
Reproduction URL
https://codeberg.org/diamonc/observer
Describe your issue
The error seems to be with the tailwind.config.cjs file, and this line (and another line like it for light theme) in particular:
   ...require("daisyui/src/colors/themes")[
                        "[data-theme=dark]"
                    ],

it worked just fine on ^2.28.0, but whenever i tried to update to ^3.9.4, i get this error:

Change ...require("daisyui/src/colors/themes") to ...require("daisyui/src/theming/themes")
This change was in daisyUI version 3 update.
Docs: https://daisyui.com/docs/themes/#-7


python312Packages.pygitguardian: 1.16.0 -> 1.17.0

Diff: https://github.com/GitGuardian/py-gitguardian/compare/refs/tags/v1.16.0...v1.17.0
Changelog: https://github.com/GitGuardian/py-gitguardian/blob/v1.17.0/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

Result of nixpkgs-review pr 344029 run on x86_64-linux 1

6 packages built:

ggshield
ggshield.dist
python311Packages.pygitguardian
python311Packages.pygitguardian.dist
python312Packages.pygitguardian
python312Packages.pygitguardian.dist


Preference metadata schema

Adds schema for #8 on top of label and core constraints schemas of #6.

Rebased without most of #6 following discussion in 2-Nov-2020 meeting to approve only the meta attributes to be included in the spec itself (see https://github.com/AMWA-TV/nmos-receiver-capabilities/issues/5#issuecomment-720544547)

Something regarding preference came into my mind today. While the constraint_sets is an array - do we want to ignore the ability that we technically could sort our preferred sets? E.g. Sorting the sets by their preference-value?
If a controller whishes it could partially decode the constraint and immediately stops when it finds a match on the top, knowing the following are lower rated anyways?

Interesting... We'd have to make that a "MUST" requirement for that to be useful. And the controller most likely needs to have parsed the entire JSON in order to extract the array, so I'm not sure how useful it would be in practice. A controller should probably make two passes through the list to rule out "meta:enabled": false and order by "meta:preference", before evaluating the constraint sets.

And the controller most likely needs to have parsed the entire JSON in order to extract the array

Yes, but it does not have to re-check multiple times if the first (= best) match was already OK.
IMO this just saves a couple extra steps / checks for not quite a small effort. As a receiver you only have to sort your stuff before putting it into the array.

In the spirit of being "liberal in what you accept, and conservative in what you send", I suspect that putting the onus on Controllers is simplest to ensure the right behaviour.
We have already recommended Controllers MAY check the version (updated by PR #11), and pre-filtering on meta:enabled (added by PR #12) and pre-sorting on meta:preference  makes sense before re-evaluating any Constraint Sets.
A real system could involve thousands of Senders and Receivers, so scalable Controllers are likely to maintain their own data structures for the results of Constraint Set evaluation, rather than perform NSenders * NReceivers evaluations directly.

Hm, I'm not really sure if that principle (although I support it) should be used as an hard argument pro / contra something while defining technical details. In the end, it is about the behavior and if you really want to be that liberal, a controller later on can ignore the fact that the array should be sorted and check the preference values by itself neglecting the order.
The fact that the sets have to be sorted in the array by their preference value would be a very easy thing to test with the testsuite. What will happen if it's not sorted correctly? You can figure it out quickly with the testsuite, and during production the controller might use / apply a less-preferred (but working!) sender / configuration, or has a couple repeated checks more (which we would have always in the case of having an unsorted array). Of course, the latter is not ideal, but when we require sorted sets, the error here is clearly on the receiver side, not the controller.
Don't get me wrong, it is ok for me to not require a sorted constraint_sets-array. It just feels wrong for me to ignore the fact that the array is on its own already sorted and we are putting some prio-values in it in a mixed order...

I think I understand your argument and I agree it has merit.
We would probably need to specify whether meta:enabled should also influence the sort order, and to draw attention to the fact that constraint sets without meta:preference should be sorted 'in the middle' (after sets with positive values, with sets that have explicit 0, before ones with negative values). Receivers would have to re-sort the list every time any of these meta values changed by a reconfiguration. Which, as you say, didn't ought to be hard for the Receiver, but it is an area that would be hard to test.
Several constraint sets could have the same meta:preference value, which a Controller may wish to consider all together?
In the future, might there be another meta value that would also be useful to sort on?


2168

Creating a design history for work on allowing automated email scheduling in the admin console.

Publishing a post on how we designed the new email scheduling screens in the admin console.


Add Redis 2.0

CI failure appears unrelated. Looks like the failure is related to https://github.com/aspnet/BuildTools/issues/787. Unfortunately this means the normal checks for external packages are not actually executing.

@natemcmaster So should I wait or just merge?


[Content group with pictograms] scroll animation design exploration

Overview
Continuing the work of #4873 this work explores the detailed design aspects of introducing scroll animations into this component. We need to figure out what settings are used, when, and too what parts of this component if at all.
Here is a list of components that could potentially be impacted by this work and should be considered at some level.

Pictogram Item

Acceptance

[ ] design exploration
[ ] design review
[ ] design approval
[ ] design specs updated

Resources

Scroll animation [box][codepen][research]
Scroll into view [box]

Won't do. Limiting animation to components without big chunks of body copy.


⚠ Contemporanea has degraded performance

In 0e9fbe9, Contemporanea ($SITE_CNTM) experienced degraded performance:

HTTP code: 200
Response time: 6362 ms

Resolved: Contemporanea performance has improved in b42cfad.


Custom validators

Replaces #235
Changes proposed in this pull request:

Support for custom validators

This example returns the complete list of validation errors instead of returning a single error:
from connexion.decorators.validation import RequestBodyValidator
from connexion.problem import problem
from connexion.utils import is_null
from jsonschema.validators import validator_for

class CustomRequestBodyValidator(RequestBodyValidator):
    def validate_schema(self, data):
        if self.is_null_value_valid and is_null(data):
            return None

        cls = validator_for(self.schema)
        cls.check_schema(self.schema)
        errors = tuple(cls(self.schema).iter_errors(data))

        if errors:
            error_list = [ e.message for e in errors ]
            return problem(400, 'Bad Request', {'errors': error_list}, type='validation')

        return None

if __name__ == '__main__':
    validator_map = {
        'body': CustomRequestBodyValidator,
    }
    app = connexion.App(__name__, ..., validator_map=validator_map)

Coverage remained the same at 100.0% when pulling fcb77b18593a5a3e2bf66cda038b4092c65aaaff on rafaelcaricio:custom-validators into 6f4e69c4f2476cdc36fab88571bc582afdd4a8c6 on zalando:master.

Coverage remained the same at 100.0% when pulling 6ff8bc79229cc62badb1a7f25a61d848ac81929f on rafaelcaricio:custom-validators into 6f4e69c4f2476cdc36fab88571bc582afdd4a8c6 on zalando:master.

@hjacobs @jmcs any feedback?

It's a cool feature but we need to document it.

This could help to workaround #287.

@rafaelcaricio this PR is quite stale (+conflicts) and I haven't really looked at it --- please resolve conflicts if we should go forward.

We should move this forward. I will update it when I get time.

This fixes https://github.com/zalando/connexion/issues/138.

I resolved documentation and some validator enhancements on https://github.com/zalando/connexion/pull/352. Can I somehow help to get this PR rebased? And my PR on top of that. I'd be thankful if we get this feature to master soon.

@phoracek Thank you for doing that. I will close this PR then and we move forward with your new PR #352 .


Installs fine but cannot run (Macbook M1)

I figure this is related to having an M1, any ideas?
╭─ericjohnson@ej-mba-m1 ~
╰─$ npm install -g layout-shift-gif
added 126 packages, and audited 127 packages in 15s
11 packages are looking for funding
run npm fund for details
found 0 vulnerabilities
╭─ericjohnson@ej-mba-m1 ~
╰─$ layout-shift-gif --url https://blacklivesmatter.com/ --device mobile --output layout-shift.gif
TimeoutError: Timed out after 10000 ms while trying to connect to the browser! Only Chrome at revision r869685 is guaranteed to work.
at Timeout.onTimeout (/opt/homebrew/lib/node_modules/layout-shift-gif/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:205:20)

This should be resolved in https://github.com/workeffortwaste/layout-shift-gif/releases/tag/1.3.0


Add multi-arch support

[x] This feature is not on the latest version

Request
I think a great addition would be to add support for more architectures than x86_64.
According to here, it would only need to add a manifest list with all the supported architectures and since alpine/ruby already support a few maybe the exact number could be included here?
Examples
armhf, ppc, sparc, etc.

Hi !

Using the arm32v6/ruby images to start with, it is just a couple of changes related to injecting qemu-user-static :
https://github.com/Blafy/jekyll-docker-arm/commit/f8dd42e4846f45f5521fd544fafd74ba6563711e
https://travis-ci.org/Blafy/jekyll-docker-arm/builds
https://hub.docker.com/r/blafy/jekyll
Here is a demonstration with a Raspberry Pi first generation (armv6 alias armhf)
pi@raspberrypi:~ $ uname -a
Linux raspberrypi 4.14.98+ #1200 Tue Feb 12 20:11:02 GMT 2019 armv6l GNU/Linux

pi@raspberrypi:~ $ docker run blafy/jekyll:stable
ruby 2.6.3p62 (2019-04-16 revision 67580) [arm-linux-musleabihf]
jekyll 3.8.5 -- Jekyll is a blog-aware, static site generator in Ruby

Usage:

  jekyll <subcommand> [options]

Options:
        -s, --source [DIR]  Source directory (defaults to ./)
        -d, --destination [DIR]  Destination directory (defaults to ./_site)
            --safe         Safe mode (defaults to false)
        -p, --plugins PLUGINS_DIR1[,PLUGINS_DIR2[,...]]  Plugins directory (defaults to ./_plugins)
            --layouts DIR  Layouts directory (defaults to ./_layouts)
            --profile      Generate a Liquid rendering profile
        -h, --help         Show this message
        -v, --version      Print the name and version
        -t, --trace        Show the full backtrace when an error occurs

Subcommands:
  docs
  import
  build, b              Build your site
  clean                 Clean the site (removes site output and metadata file) without building.
  doctor, hyde          Search site and print specific deprecation warnings
  help                  Show the help message, optionally for a given subcommand.
  new                   Creates a new Jekyll site scaffold in PATH
  new-theme             Creates a new Jekyll theme scaffold
  serve, server, s      Serve your site locally

I need to clean a few things, try to add the aarch64 (no need for armv7, as it supports v6 binaries) and then I can submit a PR 🙂
@envygeeks How do you want to handle the additionnal images in the repos ? By adding -arm a the end of the tag ?

@Blafy tonight I'll set it up so that our images use a configuration tag for the image, so we can split them off into repos with symlinked build files and a configuration that changes the base image each one uses.  That way when they get build each one can use it's own base!

Some news :
I managed to build an arm64 with success (tested on a ARM-64 server).
There is a simple way to link several architectures to one tag, using the experimental manifest feature : https://medium.com/@mauridb/docker-multi-architecture-images-365a44c26be6

Some news :

I managed to build an aarch64 image with success (tested on a ARM-64 server at Scaleway).

There is a simple way to link several architectures to one tag, using the experimental manifest feature : https://medium.com/@mauridb/docker-multi-architecture-images-365a44c26be6. This is great because it will prevent any breaking changes for people pulling the jekyll/latest, as it will automatically select the right arch.
.

Closing this since it's a dangling issue, if somebody plans to work with me on this I'll reopen it!


Duplicated controller input game mode

The fix in 45-1 didn't help "Fixed a bug when using steam-plus session where input devices were being duplicated in steam".
All controllers show duplicated. Bluetooth section shows 1, but Controller sections shows 2 controllers. Tested with 2 dualsense and 1 dualshock. In desktop mode steam properly detects only 1 controller.
As-Is
A single dualsense controller is detected as 2 controllers: PS5 controller and PlayStation 5 controller. This causes a lot of issues and makes the gamemode almost unusable.
To-Be
Steam gamemode properly detects a single controller as 1 controller.
Context
ChimeraOs: 45-1
Steam Version:<PHONE_NUMBER>
CPU: AMD Ryzen 7 5700x
RAM: 32GB
GPU: AMD Radeon RX 7900 XT

Are you using the steam-plus session?

Yes, I thought it's used automatically. I quickly checked the supposed config location and found nothing.
After several hours I gave up, switched to Bazzite linux and that solved the issue.


merge logging into retic_core

Marius worked on a logger and we want to start using it.

got the other pull requests resolved


Added yarn file

Codecov Report

Merging #295 into master will not impact coverage.

@@           Coverage Diff           @@
##           master     #295   +/-   ##
=======================================
  Coverage   81.29%   81.29%
=======================================
  Files           2        2
  Lines        2812     2812
  Branches      625      625
=======================================
  Hits         2286     2286
  Misses        526      526

Continue to review full report at Codecov.

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

Why does Squel need a Yarn file?

@hiddentao Many developers are now switched to yarn for manage packages. yarn.lock will lock dependent lib when yarn install squel. All well known npm lib now adding yarn.lock file.
Related post: https://yarnpkg.com/blog/2016/11/24/lockfiles-for-all

Yeah, but since squel only has dev dependencies, what benefit does a
yarn.lock provide ?

Director
HiddenTao Ltd
www.hiddentao.com
(Sent from my mobile, apologies for brevity)
On 28 February 2017 5:31:27 a.m. Munir Khakhi<EMAIL_ADDRESS>wrote:

@hiddentao Many developers are now switched to yarn for manage packages.
yarn.lock will lock dependent lib when yarn install squel. All well known
npm lib now adding yarn.lock file.
Related post: https://yarnpkg.com/blog/2016/11/24/lockfiles-for-all
--
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub:
https://github.com/hiddentao/squel/pull/295#issuecomment-282946555

Ah. I haven't noticed that all dependencies are dev only. Then yarn.lock not needed.


lambdas are being treated as concrete types in the array literal constructor

Expected Behavior
When I create a literal array of tuples of lambdas, where all of the lambdas have the same type signature, I expect the compiler to recognize that the signatures are the same and generate an array of objects that conform to an interface.
Observed Behavior
The compiler generates an array of a union of concrete anonymous types. This code snippet demonstrates the issue:
    let lit = [(lambda(s:String): String ref => String().append(s) end, lambda(s:String): String ref => String().append(s) end),
               (lambda(s:String): String ref => String().append(s).append(s) end, lambda(s:String): String ref => String().append(s).append(s) end),
               (lambda(s:String): String ref => String().append(s).append(s).append(s) end, lambda(s:String): String ref => String().append(s).append(s).append(s) end)]

    var result = String()
    for (la, lb) in lit.values() do
      result = result.append(la("a")).append(lb("b"))
    end

When I try to compile it, I get the following error:
Error:
/Users/aturley/development/pony-bugs/types-in-literals/tests.pony:63:9: can't destructure a union using assignment, use pattern matching instead
    for (la, lb) in lit.values() do
        ^
Error:
/Users/aturley/development/pony-bugs/types-in-literals/tests.pony:58:71: right side type: (($1$6 val, $1$7 val) | ($1$8 val, $1$9 val) | ($1$10 val, $1$11 val))
    let lit = [(lambda(s:String): String ref => String().append(s) end, lambda(s:String): String ref => String().append(s) end),

The issue here is that lambdas (actually, all object literals) are given an expression type that is their concrete anonymous type. As a result, an array literal of these has an element type that is a union of the concrete types, since the concrete types are not subtypes of each other.
That means in the Array[A], A is:
(({(String): String ref} val, {(String): String ref} val}) | ({(String): String ref} val, {(String): String ref} val}))

That is, a union of tuples, where each of those is actually a separate concrete type.
Currently, the compiler then sees the assignment of a union to a tuple and fails, even though it knows that the union of tuples is a subtype of the tuple of unions (operator.c:414).

If the clause in operator.c from lines 428-452 is removed, then the problem is in safe_to_write, safeto.c:93. If we can't rely on only getting tuple types, then this code will have to extract every possible type that could be assigned to each element of the tuple.
In other words, @andymcn, this is another example of the "canonical type representation" problem, I think.

Is this code snippet fixed by simply adding as {(String): String ref} val: to the start of the array, as we have to do with numeric literals? [as U8: 1, 2, 3]

Yes, it is. It needs the full tuple, then it works:
[as ({(String): String ref} val, {(String): String ref} val): ...]

@jemc Will this be fixed by #2168?

let lit = [({(s: String): String ref => String().>append(s) }, {(s: String): String ref => String().>append(s)})]
    var result: String ref = "".string()
    for (la, lb) in lit.values() do
      result = result.>append(la("a")).>append(lb("b"))
    end

@aturley  It's works.
@SeanTAllen This issues can be closed.

The original snippet by @aturley, if updated for contemporary Pony syntax still gets roughly the same error:
actor Main
  new create(env: Env) =>
    let lit = [({(s:String): String ref => String().>append(s) }, {(s:String): String ref => String().>append(s) })
               ({(s:String): String ref => String().>append(s).>append(s) }, {(s:String): String ref => String().>append(s).>append(s) })
               ({(s:String): String ref => String().>append(s).>append(s).>append(s) }, {(s:String): String ref => String().>append(s).>append(s).>append(s) })]

    var result = String()
    for (la, lb) in lit.values() do
      result = result.>append(la("a")).>append(lb("b"))
    end

0.35.0-3d00d409 [release]
Compiled with: LLVM 9.0.1 -- Clang-9.0.0-x86_64
Defaults: pic=true
Error:
main.pony:9:9: can't destructure a union using assignment, use pattern matching instead
    for (la, lb) in lit.values() do
        ^


Databricks Documentation: Typo error on navigation panel

I found a typo error on left navigation panel - Bigint is written as Bitint

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

ID: 4db5d36e-d6cb-4fa0-2482-dd5cfe9201db
Version Independent ID: 525616a9-f054-f4d4-8b62-da7142b796e3
Content: BIGINT type - Azure Databricks - SQL Analytics
Content Source: databricks/sql/language-manual/data-types/bigint-type.md
Service: azure-databricks
Sub-service: databricks-sql-analytics
GitHub Login: @mssaperla
Microsoft Alias: saperla

@saurabh-py -
Thanks for the feedback! We have assigned the issue to the content author to further review this and update the document as appropriate.

@leifbro , @mssaperla  - Could you please review the above doc bug feedback and update it accordingly. Thank you

Thanks for providing feedback that helps improve our documentation. This issue has been resolved and the content has been updated. We are closing the issue.
#please-close

#please-close


Plugins log everything through their _log attribute

This big pull request does the following:

Provide a well-managed (automatic level) BeetsPlugin._log for each plugin
This is in the first 4 commits. It related to issue #1044 (and #916? some issues seem redundant) and is a big step for #431.
The next commits are the application of this new feature to the whole code base.

Make all plugins use _log
This is quite huge. Since there are BeetPlugins that

don't use logging → ok
only call their own methods → painless conversion
use a few other classes → those receive the logger at init
use objects often instantiated → those receive the logger as a class attribute
call multiple functions → depends on the look of the module

I sometimes passed the logger object around to several functions
other times I converted those functions to methods of the plugin. This has the downside of moving a lot of code around, an error-prone and hard-to-review process

have several service providers, each living in a function →each function turned into a class, all of them sharing the same parent (lyrics and fetchart)

Also note that

plugins don't prefix their message with a [pluginname] since this is automatically handled by their logger.
as explained in issue #431, registration of the listeners had to be adapted as well

Update the tests!
Since some (23) are skipped on my machine, I may have missed error.

Update the docs
coming soon

Awesome! This is indeed a big one. All this code reorganization was a heroic effort. A round of applause!
I'm going to scan over all of this now.

OK, looks about ready to merge! (We can tackle docs afterward.)
I think something's wrong with PyPy on Travis' end, so ignore the red build status.

Here's a small doc update. I'm not sure if that what you envisioned of if it's enough — it's pretty terse.

Thank you again! I started merging this up, but I've run in to a fairly serious stumbling block: the -v flag no longer controls plugin loggers' verbosity. This means that self._log.debug() never prints anything, even in verbose mode. We somehow need a way to keep what we have now in ordinary circumstances but make everything verbose when the root logger is verbose. Investigating…


Use _map function for match analysis

In order to defer value evaluation so that the ParameterContext
dependency can later on be removed from the ExpressionAnalyzer.

@matriv please review


Bug with color

System Details

OS: Windows 10 22h2
Thorium Version 124.0.6367.218

Problem
I have a sidebar and red color selection
Screenshots

Additional Notes
I have these extensions:

Unfortunately, I have the same issue.

Same issue on my Linux Mint

same here on windows 10

@Y2K350 @omnitrix9991 @den1source @RIRafi @rongpengli Known issue. There has been similar "red colored UI element bugs" in the past. However, this probably was not noticed, overlooked, or marked "wontfix" by the Chromium team, since the non-CR23 side panel is removed in M125 anyway. I couldn't find any Chromium bugs related to it.
Because of the above mentioned thing, this will be removed anyway in M125, and using the CR23 side panel will be the default. I enabled this feature to allow people to use the traditional non-CR23 side panel variant for as long as possible until they force enable CR23, but it had the unintended consequence of this bug.
Anyway, just wait until M125.

Workaround is'nt working anymore.
Device :- Windows 11

Workaround is'nt working anymore. Device :- Windows 11

still works for me

The command --disable-features=NoChromeRefresh2023 worked for me. After updating Windows, the old command --disable-features=CustomizeChromeSidePanelNoChromeRefresh2023 stopped working. I hope this helps someone!

oot: i found this red, when i pin and unpin shortcut on new-tab


Fix Duplicate Job Requeuing From K8S Controller

I don't think this fix actually helps with de-dup. Basically, in this version we don't have duplicates because we don't queue duplicated jobs anymore. And if we do that, we can just use a "regular" controller to achieve the same effect. In the current implementation, we queue additional jobs for a good reason - to reconcile in case the targets have drifted, such as an admin going to the cluster and manually deleted the helm chart. We can't rely on jobs being queued every 10 or 20 hours - that's too long. The de-dup is supposed to reduce number of unnecessary jobs, but we can't get rid of recurring jobs all together. It's not straightforward to judge when a job should be requeued or not, but I guess in general: 1. if job fails due to validation errors then there's no point of requeuing. 2. if there's an active job that is already in progress. I can't think of other cases we don't want the job to be requeued. Make sure what you propose covers these cases:

When the target is turned off for extended period of time. We don't know when the target will come back, so we have to keep trying. In this case, we need to ensure that we don't enqueue multiple jobs.
When the target drifts from the desired state by itself.

we did keep the reconcile logic in the new queueing controller:
if isRemoval || reconciliationInterval == 0 {
	// remove, don't need to reconcile
	// If the reconcile policy is once (interval == 0 or state==inactive), we should not queue a new job and return
	return metrics.DeploymentQueued, ctrl.Result{}, nil
} else {
	return metrics.DeploymentQueued, ctrl.Result{RequeueAfter: reconciliationInterval}, nil
}


Added 32 bit and 64 bit links for Python 2.7.12

Solved issue https://github.com/MicrosoftDocs/visualstudio-docs/issues/1697#issue-370816572
Added Debug Symbol links for 32 bit and 64 bit Python 2.7.12

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

Thanks for doing that. I have to admit that Python 2 isn't much on my radar, hence my neglecting to add the update. I appreciate your taking the time for fill in the detail!

#sign-off

Close https://github.com/MicrosoftDocs/visualstudio-docs/issues/1697


AMBARI-24089 Cannot add component to 25+ hosts

How was this patch tested?
21800 passing (31s)
48 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/2693/
Test FAILed.
Test FAILured.

retest this please


🔧 Update Travis CI configuration with latest major Node.js versions (v1.x legacy)

Supports #69 and #68.
Update test matrix to include all currently supported versions listed at https://nodejs.org/en/about/releases/.

CI build passed on all known supported versions, and failed (as expected) in Node.js 13.x.
Merging this for #68 and #69 to rebase.


"Maid" is not a valid Dart package name.

I tried to run flutter create . on my mac but got error
"Maid" is not a valid Dart package name.

The name should be all lowercase, with underscores to separate words, "just_like_this".Use only basic Latin letters and Arabic digits: [a-z0-9_].Also, make sure the name is a valid Dart identifier—that it doesn't start with digits and isn't a reserved word.
See https://dart.dev/tools/pub/pubspec#name for more information.
Try "maid" instead.

Ahh i noticed that before, its because the project name is capitalized so when you clone into it the default folder is Maid, you can rename it to maid and it works fine. Ill rename the project for you though as its no issue


Can't install, please have clearer instructions for installation

-- CPack generators: ZIP;TGZ
-- Configuring incomplete, errors occurred!
See also "/Users/thwilliams/Code/ion-c-1.0.3/build/debug/CMakeFiles/CMakeOutput.log".
make: *** No rule to make target `clean'.  Stop.

When I download the newest zip and unzip then run ./build-debug.sh or ./build-release.sh I get the error above on Mac OS X.
In the other file I ran in Linux and Mac OS X using the example from site. The given cookbook example doesn't compile even if I link the .so. The is that a macro variable in decimal is not defined. Even when running ./build-debug.sh or ./build-release.sh.

https://github.com/therapon/ion-c-examples/tree/master/system-installed
I made this a while ago but should still work. Let me know if this helps/resolves the issue you are having

The lack of documentation for building and using the C library is not helpful.
Please specify which platforms the cmake system has been set up to support.
It seems broken for Windows builds.


Update multibuild concurrency

Coded live in the community call
This starts by aligning the content with the getting-started guide, and then replacing the go errgroup concurrency with nothing to let buildkit handle the concurrency for us

https://discord.com/channels/707636530424053791/1037791976696840218/1045701987678818386
We should remove reference of errgroup in the getting started docs as well.


Where to put private module data in the JavaScript Module Object?

In order to minimize the risk of EMs to interfere with each other's data in the browser (JavaScript) and to not "pollute" the global scope, encapsulation is highly encouraged, such as wrapping code in immediately invoked function expressions.
The JavaScript Module Object built into the EM framework is another good place to put any module-related data, as it guarantees a unique namespace.
However, there is no "safe place" defined where such data (objects, functions, etc) could be put in order to not risk being interfered with with future updates (on the PHP side, ->framework was invented to solve this problem).
Thus, I'd propose to reserve, by defining them in the documentation, at least one (or a few) keywords that the EM framework will never use and thus will be safe to use by module authors.
Candidates would be:

data
methods
private
public
api

api and public might be useful to expose properties/functions to external modules. All others are to be considered private.
A reason for having more than just one such reserved place in the JSMO is to fit semantics and personal preferences of developers.
Open for discussion. To implement, only docs need to be updated (and the promise kept ;)

Have you considered encapsulation within your own uniquely named global object?  I'm doing so when I have such a need, and I've seen others do it as well.  It's easily accessible throughout your module, unlikely to conflict with anything else at the global scope, and (IMO) more maintainable than modifying the JMO.
Though, my situation might not align with yours.  I've yet to move any of my production modules beyond the original base framework, where the JMO was only just beginning.

My thought was: Since the JMO is available, why not use it for this purpose instead of having another (putatively) uniquely named object.
But this would require the framework to never uses at least some names.
The JMO will likely see more use in the future, as it will shortly support internationalization of display strings.

This is a great question.  I think my personal preference might be a separate object like @dr01d3r suggested so that the two contexts are completely separate and you don't even have to think about conflicts between the two.  I'd be curious to hear input from others.

But wasn't the point of EM namespacing to isolate them from each other (and the system)? Why would you want to have things that are part of the EM life outside of that? This makes no sense to me.
At least one safe place within the JSMO should be defined for authors to use. That would be the best solution in my opinion. And it comes at only the cost of putting it in the docs.

I suppose it depends on your perspective.  I personally like having two layers of context separation (between built-in objects for different modules, and also between a built in methods and those defined by the module).  I don't see any reason to restrict other development styles though.  Part of me wonders if we should put all framework methods under a framework child object like we did in PHP to prevent conflicts, but even that we're debating abstracting away with magic methods.  It seems like a fine line to walk between protection against pitfalls, clean syntax, and an API that isn't too opinionated.  I would really like to hear input from others before making any decisions.


logging: sidecar injector - GetAppID

Description
sidecar injector - GetAppID will not default to any other name if not set and will fail the injection if not appID not set

Issue reference

Please reference the issue this PR will close: #5141
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[x] Created/updated tests
[x] Unit tests passing
[x] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

Is this a breaking change?

Yes. @sadath-12 we actually want to allow users to default a pod name if an ID isn't specified and I know at least one company using Dapr like that. Could you please change this PR to only log a warning that an app-id isn't set and that a pod name is used instead?

Can this PR also add a end-to-end or functional test scenario to catch the breaking change? Unit-test usually don't catch those.

Can this PR also add a end-to-end or functional test scenario to catch the breaking change? Unit-test usually don't catch those.

Not making a breaking change


[Bug]:

Minimal, reproducible example
// create browser instance and create page
		const browser = await puppeteer.launch({ headless: "new" });
		const page = await browser.newPage();

		// create buffer from html content
		await page.setContent(HTMLTemplateString, { waitUntil: "domcontentloaded" });
		const attachmentBuffer = await page.pdf(PDFFileOptionsObject);
		const attachmentMimeType = "application/pdf";

		// close browser instance
		await browser.close();

Error string
Error: Failed to launch the browser process!
Bug behavior

[ ] Flaky
[X] PDF

Background
trying to create pdf.
Expectation
pdf should create
Reality
error
Puppeteer configuration file (if used)
No response
Puppeteer version
"puppeteer": "^19.2.2"
Node version
18
Package manager
yarn
Package manager version
1.22.17
Operating system
Linux

This usually happens when browser is not install property. Sometime yarn does not run the postinstall scripts please see if running node ./node_modules/puppeteer/install.js and rerun your script.
If the error persist please post the full logs from the error.


Update some dependencies

The main impetus for this PR is to update the very outdated rack dep, which keeps registering critical issues in our vulnerability scanners.
While I was at it, I updated a few others. Would be nice to update rack-test to 2.1 and mocha as well, but they require more extensive changes.
Also fixed a CI issue and faraday 1.x/2.x compat issue while I was at it.

@drstrangelooker let me know if this looks ok .. I have no idea why the CI runs are failing.

the CI runs fail because you are working from a fork. When I have a chance on Monday I'll pull your changes into a local branch, then rerun the CI.
Thanks
Mike


Fix error!

How to fix the code execution cannot proceed because cudart68_80 was not found while run BitCrack64.exe?
Thanks

Hi there,
Do you have an nVidia card with the latest drivers installed?

How to fix the code execution cannot proceed because cudart68_80 was not found while run BitCrack64.exe?
Thanks

You have an old version of the program, download the latest v0.21 and download CUDA 9.2 (after unpacking, extract 'cudart64_92.dll' and place it in the folder with BitCrack64)