qjackctl: 0.9.0 -> 0.9.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/qjackctl/versions.
meta.description for qjackctl is: "A Qt application to control the JACK sound server daemon"
meta.homepage for qjackctl is: "https://github.com/rncbc/qjackctl"
meta.changelog for qjackctl is: ""
Updates performed

Version update

To inspect upstream changes

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS

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

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

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

found 0.9.1 with grep in /nix/store/776v43vjxvgwf35k36rbshwb7g05rzmj-qjackctl-0.9.1

directory tree listing: https://gist.github.com/a1d08ad442b88f9259b24d85979fd9c2

du listing: https://gist.github.com/6c67e0b894ef6a46327c13be5710e8d6

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

3 total rebuild path(s)

1 package rebuild(s)

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

First fifty rebuilds by attrpath
qjackctl

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/776v43vjxvgwf35k36rbshwb7g05rzmj-qjackctl-0.9.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/776v43vjxvgwf35k36rbshwb7g05rzmj-qjackctl-0.9.1
ls -la /nix/store/776v43vjxvgwf35k36rbshwb7g05rzmj-qjackctl-0.9.1/bin

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

1 package built:

qjackctl

Maintainer pings
cc @cillianderoiste for testing.

new release available


A new commit for a test PR

This is a test PR!
To test jenkins integration

Can one of the admins verify this patch?

jenkins

reset this please

OK to test

OK to test

test this please


Buy gold for other users

Currently it seems like it is only possible to buy gold for yourself. But gold is way more commonly bought for other users so it would be cool if the bot could support that, maybe even gilding a comment via the bot. (not sure if the API supports that) It could even leave a comment there that someone gilded via the bot.
Commands could look like this:
subject: +gold
content: buy <username>

subject: +gold
content: buy <link to comment>

i will add possibility to buy gold for someone, and i need to look for comment gilding :)

Alternative syntax:
+/u/sodogetip gold
You would reply this directly below the comment or post.


server tree loading

Hello!
Could you tell me if it's possible to have the collapsed arrows next to the nodes? See the picture:
https://ibb.co/LJDQVL3
The problem is that the Virtual and COM nodes isn't loaded yet and I can't follow the normal way where i set loaded state to false and get data via ajax. What i'm doing now is something like this
if (node.count_child > 0)   node.removeClass("jstree-leaf").addClass("jstree-closed");
but it dissapears as i collapse the root node and then expand it.
Anyway I have to hardcode this in a way, cuz i don't have a choise haha

Sorry for wasting your time. setting state.loaded to false is fine.


Cache user-selected mappings for future uploads

If a user maps a CSV to a DataObject / bulk loader, then that mapping could be stored for future imports, so the same work doesn't need to be done twice.

I've started this work using cache class. Looks like cache might be expiring too soon though.


[#4360] fix build fail

fix build fail

Codecov Report

Merging #4375 into master will increase coverage by 0.01%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #4375      +/-   ##
==========================================
+ Coverage   40.85%   40.87%   +0.01%
==========================================
  Files        2440     2440
  Lines       75241    75241
  Branches    10204    10204
==========================================
+ Hits        30742    30753      +11
+ Misses      41679    41670       -9
+ Partials     2820     2818       -2

Impacted Files
Coverage Δ

...corp/pinpoint/plugin/akka/http/AkkaHttpPlugin.java
0% <0%> (ø)
:arrow_up:

...pinpoint/profiler/instrument/AccessorAnalyzer.java
57.14% <0%> (-8.58%)
:arrow_down:

...java/com/navercorp/pinpoint/rpc/DefaultFuture.java
72.5% <0%> (-1.67%)
:arrow_down:

...rp/pinpoint/rpc/server/PinpointServerAcceptor.java
89.72% <0%> (+4.79%)
:arrow_up:

...pc/server/LoggingServerMessageListenerFactory.java
100% <0%> (+10%)
:arrow_up:

...vercorp/pinpoint/rpc/packet/ServerClosePacket.java
68% <0%> (+16%)
:arrow_up:

...p/pinpoint/rpc/client/WriteFailFutureListener.java
75% <0%> (+18.75%)
:arrow_up:

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 0951843...b4454d4. Read the comment docs.


Updated support Ember

Ember updates
On Ember 2.6 I received deprecation warnings about init functions not calling super. This resolves those warnings.
src$ ember nw
DEPRECATION: Overriding init without calling this._super is deprecated. Please call `this._super.init
&& this._super.init.apply(this, arguments);` addon: `nw`
    at src/node_modules/ember-cli/lib/models/project.js:404:38
DEPRECATION: Overriding init without calling this._super is deprecated. Please call `this._super.init
&& this._super.init.apply(this, arguments);` addon: `nw:package`
    at src/node_modules/ember-cli/lib/models/project.js:404:38
DEPRECATION: Overriding init without calling this._super is deprecated. Please call `this._super.init
&& this._super.init.apply(this, arguments);` addon: `nw:test`
    at src/node_modules/ember-cli/lib/models/project.js:404:38

NWJS Updates
NWJS 0.13 did not appear to have window.nwDispatcher defined which made the shims non-operational. The shims now look for window.nw.

The changes to the commands look good. I don't have any experience with the nwDispatcher change, @brzpegasus will have to chime in on that part...

Thanks for this! Would you mind breaking up the PR into two? One for the deprecation issue, and one for the NW.js update?
Also, it would be nice if you could make the shims compatible with both window.nw and window.nwDispatcher.

Ok, this PR has been updated to just include Ember deprecation fixes. NWJS PR coming next.

jshint doesn't seem to like the update. Perhaps there's a rule to disable that particular complaint.

All passing now. Updated the .jshintrc file to have "expr": true. The warning was triggered by the syntax:
this._super.init && this._super.init.apply(this, arguments);

Thanks! One last favor: could you please squash the commits?

@bdevel Need help squashing?

Squashed.

Hmm, something's not quite right. Looks like the changes contain the NW changes, which are already on master. Could you rebase? Sorry for being a pain!

Sorry about that. How about now?

@bdevel 👍 Thank you!


Redux Store called more than ones.

I created a simple example with Outwatch and Redux. It works fine, but in the debugger you see that the reducer is called 4 times for each event:

Did I miss something? Here is my code: StopWatch.scala
The project can be run with >sbt ~fastOptJS

That's very very odd! It might be some bug with RxJS or Chrome, but it's guaranteed, that the action is only run once. I tried replicating your issue and get the same problem, however, the increment is only done once. I can't really say exactly what's causing it, but I'll try to investigate further soon!

I think this is "normal" behavior, the reducer is called for each subscriber.
The solution would be to change the store source like so:
  val source: Observable[State] = sink
    .scan(initialState)(reducer)
    .startWith(initialState)
    .share

so it will have a single subscriber that multicast the reducer results to all the other subscribers.
In some cases is nice to have the latest reducer result automatically emitted, in which case you could use:
val source: Observable[State] = sink
    .scan(initialState)(reducer)
    .startWith(initialState)
    .publishReplay(1)
    .refCount

That works perfectly, thanks. So I had to do my 'own' outwatch.util.Store. Would be great to have these 2 cases available in the Store util. Let me know if I should make a pull request for that.

You could use your own store wrapper:

import outwatch.util.{Store => OutwatchStore}

case class Store[State, Action](wrapped: OutwatchStore[State, Action])

object Store {
  implicit def toSink[Action](store: Store[_, Action]): Sink[Action] = store.wrapped.sink
  implicit def toSource[State](store: Store[State, _]): Observable[State] = store.wrapped.source.share
}

I think to add an own Store is easier to understand (at least for me):
`final case class Store[T, U](initialState: T, reducer: (T,U) => T) {
val sink = createHandlerU
val source = sink
.scan(initialState)(reducer)
.startWith(initialState)
.publishReplay(1)
.refCount
def subscribe(f: T => Unit) = source.subscribe(f)
}
object Store {
implicit def toSink[U](store: Store[,U]): Sink[U] = store.sink
implicit def toSource[T](store: Store[T,]): Observable[T] = store.source
}`

I think I might add a MulticastStore soon, or you could create a PR. Thank you guys both very much! :)

How about something like this instread of a MulcicastStore:
final case class Store[State, Action](source: Observable[State], sink: Sink[Action]) {

  def subscribe(f: State => Unit): Subscription = source.subscribe(f)

  def map[S](project: State => S): Store[S, Action] = Store(source.map(project), sink)

  def share: Store[State, Action] = Store(source.share, sink)
}

object Store {

  implicit def toSink[Action](store: Store[_, Action]): Sink[Action] = store.sink
  implicit def toSource[State](store: Store[State, _]): Observable[State] = store.source

  def apply[State, Action](initialState: State, reducer: (State, Action) => State): Store[State, Action] = {
    val sink: Observable[Action] with Sink[Action] = createHandler[Action]()
    val source: Observable[State] = sink
      .scan(initialState)(reducer)
      .startWith(initialState)

    apply(source, sink)
  }
}


Newbie Attempting to Run Tutorial get Metclass Conflict

Ubuntu 22.04, Python 3.10.
Had a lot of pip conflicts but resolved them all except for conflict with nicegui being globally installed, but am guessing this shouldn't matter. Attempting to get started with tutorial failed:
(venv) > reflex init
Traceback (most recent call last):
  File "/home/martin/.local/bin/reflex", line 5, in <module>
    from reflex.reflex import cli
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/reflex.py", line 18, in <module>
    from reflex.custom_components.custom_components import custom_components_cli
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/custom_components/custom_components.py", line 23, in <module>
    from reflex.utils.pyi_generator import PyiGenerator
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/utils/pyi_generator.py", line 26, in <module>
    from reflex.components.component import Component
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/components/__init__.py", line 4, in <module>
    from . import lucide
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/components/lucide/__init__.py", line 3, in <module>
    from .icon import Icon
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/components/lucide/icon.py", line 3, in <module>
    from reflex.components.component import Component
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/components/component.py", line 24, in <module>
    import reflex.state
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/state.py", line 56, in <module>
    from reflex.utils import console, format, prerequisites, types
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/utils/prerequisites.py", line 32, in <module>
    from reflex import constants, model
  File "<frozen importlib._bootstrap>", line 1075, in _handle_fromlist
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/__init__.py", line 224, in __getattr__
    module = importlib.import_module(_MAPPING[name])
  File "/usr/lib/python3.10/importlib/__init__.py", line 126, in import_module
    return _bootstrap._gcd_import(name[level:], package, level)
  File "/home/martin/.local/lib/python3.10/site-packages/reflex/model.py", line 136, in <module>
    class Model(Base, sqlmodel.SQLModel):
TypeError: metaclass conflict: the metaclass of a derived class must be a (non-strict) subclass of the metaclasses of all its bases
(venv) >

Spent some time looking up metaclasses, and inheritance conflicts, but it appears I would have to define a new metaclass in the library to resolve the conflict with sqlmodel, and this can't be the best way to proceed to just getting started with reflex. Any suggestions? Thanks.

Thanks for raising - this is resolved in #3026 and will be available soon. Hopefully we can get you unblocked soon with these dependencies.


Error when network isn't in the list

Hello,
I encounter an error when the social network does't exist:
TypeError: Cannot read property 'type' of undefined
is it possible that it silently fail instead of trowing an error?
thanks in advance

Hello @jbrialon,
thank you for your input, this is now fixed and throw a console warning instead :)

thanks @nicolasbeauvais 👍


Data description upgrader takes care of wrong funder name

Fixes #23
The Organization.FUNDERS only includes AI, NINDS, and SIMONS. We have several assets with AIND as funder. In case the specified funder is not among the possible ones, it is set to Organization.AI.
Note: I tried to avoid hard-coding supported funders, with this
@jtyoung84 @dyf @Sun-flow  I have a feeling there is probably a better way to do that (basically get the inner types of an Annotated Union). Thoughts?

I think it's better just to map AIBS and AIND to AI. Will that cover the cases you've seen, Alessio?

yes, so just making a dictionary with a map?

I just noticed that the map was already there. Updated

yes, so just making a dictionary with a map?

yeah that sounds right.

@dyf tried to simplify the logic a bit. Can you take a look?


Content in table headers that are not promoted, doesnt rerender in rotated modus

Added tests that should ensure this is not an issue anymore.


chore: bump dashboard links lib

part of fixing https://github.com/canonical/kubeflow-dashboard-operator/issues/213
bumps the KubeflowDashboardLinks lib to Patch 3, lib was updated in https://github.com/canonical/kubeflow-dashboard-operator/pull/219

CI should be fixed by

https://github.com/canonical/kfp-operators/pull/545
https://github.com/canonical/kfp-operators/pull/543


WIP: Ingress node firewall APIs review

request to review new operator APIs, implementation is based on operator-sdk framework
repo where the APIs and controller are implemented is
https://github.com/openshift/ingress-node-firewall
review comments will be addressed in PR against ingress-node-firewall repo directly I shared in api forum for reviews
Signed-off-by: Mohamed Mahmoud<EMAIL_ADDRESS>

I addressed some of your comments here https://github.com/openshift/ingress-node-firewall/pull/76 maybe can continue there as it easier to verify and test the changes ?

I kept the nodeSelector in firewallconfig types as map[string]string to match up with DaemonSet Spec.Template.Spec.NodeSelector

Can you update this PR with the changes as described, lets keep the conversation here until we are happy with the design, then we can move across to the other repo
Keeping it here allows me to see the entire API, not just the diffed sections in isolation

Can you update this PR with the changes as described, lets keep the conversation here until we are happy with the design, then we can move across to the other repo
Keeping it here allows me to see the entire API, not just the diffed sections in isolation

Thanks, I uploaded the new changes webhook change will be address in separate PR by @martinkennelly


783 sequential wiring and transmission losses

Apply the wiring loss and then the transmission loss, so that the numbers can't be greater than 100%. Update the loss calculations so this appropriately shows up in the loss diagram. Transmission losses were added in SAM PR 1000
I'm happy to add a unit test for this, but wanted to confirm the loss behavior with you prior to writing it.

A little testing looks good, one thing this does bring up is that the warning about the inverter being oversized seems to get triggered downstream of the actual inverter calculation (after AC and transmission losses), which is probably not the intent of that warning. Possibly a separate issue? Thoughts?

A little testing looks good, one thing this does bring up is that the warning about the inverter being oversized seems to get triggered downstream of the actual inverter calculation (after AC and transmission losses), which is probably not the intent of that warning. Possibly a separate issue? Thoughts?

I'm willing to lump that in here - the tricky part is that there isn't currently a timeseries output that has the data needed to fix that issue. Would adding something like "inverter output AC gross" as a timeseries output be helpful? Preferences on naming?


suppress-none-returning = true won't work

For these configurations suppress-none-returning = true would be ignored.

pyproject.toml
[tool.ruff]
line-length = 100
select = ["ALL"]
target-version = "py38"
ignore = [
    "TID252",
    # we use asserts in tests and to hint mypy
    "E501", # line too long, handled by black.
    "S101",
    "S102",
    "S104",
    "S324",
    "EXE002",
    # maybe we can enable this in future
    # we'd want to have consistent docstrings in future
    "D",
    "ANN101", # missing annotation for self?
    # definitely enable these, maybe not in tests
    "ANN001",
    "ANN002",
    "ANN003",
    "ANN102",
    "ANN201",
    "ANN202",
    "ANN204",
    "ANN205",
    "ANN206",
    "ANN401",
    "PGH003",
    "PGH004",
    "RET504",
    "RET505",
    "RET506",
    "RET507",
    "BLE001",
    "B008",
    "N811",
    "N804",
    "N818",
    # Variable `T` in function should be lowercase
    # this seems a potential bug or opportunity for improvement in ruff
    "N806",

    # first argument should named self (found in tests)
    "N805",

    "N815",

    # shadowing builtins
    "A001",
    "A002",
    "A003",

    "ARG001",
    "ARG002",
    "ARG003",
    "ARG004",
    "ARG005",
    "FBT001",
    "FBT002",
    "FBT003",

    "PT001",
    "PT023",

    # enable these, we have some in tests
    "B006",
    "PT004",
    "PT007",
    "PT011",
    "PT012",
    "PT015",
    "PT017",
    "C414",
    "N802",

    "SIM117",
    "SIM102",

    "F841",
    "B027",
    "B905",
    "ISC001",

    # same?
    "S105",
    "S106",

    "DTZ003",
    "DTZ005",

    "RSE102",
    "SLF001",

    # in tests
    "DTZ001",

    "EM101",
    "EM102",
    "EM103",

    "B904",
    "B019",

    "N801",
    "N807",

    # pandas
    "PD",

    # code complexity
    "C",
    "C901",

    # trailing commas
    "COM812",

    "PLR",
    "INP",
    "TRY",
    "SIM300",
    "SIM114",
    "DJ008",
]
fix = true
src = ["<source>", "tests"]

[tool.ruff.flake8-annotations]
suppress-none-returning = true

Do you mind including a code snippet + command on which this reproduces? Thanks!

Hey @charliermarsh Thanks for you great work here. sorry for not including enough information.
reproduce-return-none-ruff
run pre-commit run -a
and
def return_implicit_none() -> Optional[int]:
    if random.randint(1, 2) == 2:
        return 2

would become
def return_implicit_none() -> Optional[int]:
    if random.randint(1, 2) == 2:
        return 2
    return None

repo: https://github.com/nrbnlulu/reproduce-return-none-ruff/tree/main

No worries! Thanks for the added info. I think you may be mixing up responsibilities. suppress-none-returning only applies to the flake8-annotation rules (those that stat with ANN), and is used to suppress annotation requirements for functions that don't return anything.
What you're seeing is the expected behavior for that rule (RET503). I'd suggest adding RET503 to your ignore list if it's not something you want to enforce!

Thanks!


Used fixed seed for test_beam_search

Fixes #72

Job PR-99/2 is complete.
Docs are uploaded to http://gluon-nlp-staging.s3-accelerate.dualstack.amazonaws.com/PR-99/2/index.html

@leezu @sxjscience what's the root cause for the test failure? is it a code problem?

I suggest we merge this now as it is annoying to retrigger CI if it failed due to test_beam_search. Regarding the root cause, @sxjscience is in a better position to answer as he wrote that code. Even if this is a code problem, it's in the code already and if so @sxjscience is aware and can fix it or let us know to fix it if he is busy?

We can merge this in first. I’m busy this week.
Get Outlook for iOShttps://aka.ms/o0ukef

From: Leonard Lausen<EMAIL_ADDRESS>Sent: Tuesday, May 8, 2018 7:15:54 AM
To: dmlc/gluon-nlp
Cc: Xingjian SHI; Mention
Subject: Re: [dmlc/gluon-nlp] Used fixed seed for test_beam_search (#99)
I suggest we merge this now as it is annoying to retrigger CI if it failed due to test_beam_search. Regarding the root cause, @sxjsciencehttps://github.com/sxjscience is in a better position to answer as he wrote that code. Even if this is a code problem, it's in the code already and if so @sxjsciencehttps://github.com/sxjscience is aware and can fix it or let us know to fix it if he is busy?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/dmlc/gluon-nlp/pull/99#issuecomment-387235103, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AE8D7mGOMlYPDWKqI0YY1h8xg6iO0UCTks5twNWqgaJpZM4T1wm3.


chore(network): change the way protobuf types are being imported to improve readability

Pull Request type
Please check the type of change your PR introduces:

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no API changes)
[ ] Build-related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?

Issue Number: N/A
What is the new behavior?

Does this introduce a breaking change?

[ ] Yes
[ ] No

Other information

This change is

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

Current dependencies on/for this PR:

main

PR #1531

PR #1532

PR #1534

PR #1535

PR #1536   👈

This stack of pull requests is managed by Graphite.


[NSETM-2310] Allow to use the cache in readonly mode

New Features:

Add cache_config.readonly, to be able to use an existing cache without exclusive locking [NSETM-2310].
Add cache_config.store_type, to change the file format (experimental).
Add cache_config.skip_features, to skip writing the features DataFrames (not implemented yet).

Deprecations:

Deprecate output, use cache_config.path instead.
Deprecate clear_cache, use cache_config.clear instead.

Codecov Report
Attention: Patch coverage is 82.78689% with 21 lines in your changes are missing coverage. Please review.

Project coverage is 91.84%. Comparing base (b7cd430) to head (1e12b0b).

Files
Patch %
Lines

src/blueetl/config/analysis_model.py
76.92%
6 Missing and 3 partials :warning:

src/blueetl/cache.py
86.88%
6 Missing and 2 partials :warning:

src/blueetl/config/analysis.py
73.33%
2 Missing and 2 partials :warning:

Additional details and impacted files
@@               Coverage Diff               @@
##           multi_index      #36      +/-   ##
===============================================
- Coverage        92.42%   91.84%   -0.59%
===============================================
  Files               45       45
  Lines             2601     2672      +71
  Branches           518      540      +22
===============================================
+ Hits              2404     2454      +50
- Misses             121      135      +14
- Partials            76       83       +7

Flag
Coverage Δ

pytest
91.84% <82.78%> (-0.59%)
:arrow_down:

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


[question] Is it possible to get a number of Clones?

Like the Traffic tab in the Graphs section?
It would be very-very useful. Thank you.

Not directly. But you should be able to approximate it by counting number of fork events: https://developer.github.com/v3/activity/events/types/#forkevent

That I know. But fork is not a clone. Ok, thanks


Use python ruther than bash

Currently zappa deploy script is written in bash https://github.com/frictionlessdata/dpr-api/blob/master/zappa_deploy.sh
Think it would be better it to be python

FIXED


Move postcss dependency to peerDependencies

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Correct iTerm shell integration mark placement

Related issue already closed: https://github.com/rafaelrinaldi/pure/issues/116. This PR further improves iTerm shell integration with pure.

I'm waiting for iTerm 3.3 to merge this one (see https://gitlab.com/gnachman/iterm2/issues/7906)

Cool thank for the clarification

I pushed some tests for _pure_place_iterm2_prompt_mark and bump version to 2.3.1
@schrodincat, could you:

[ ] review the tests?
[ ] write documentation (if need be)
[ ] release

@edouard-lopez done☺ Thank you for the tests!👍


Fix gitDir Bug for git specific executables

Changelog

changing res.bin !== 'npm' to res.bin === 'git'

Why
It's not possible to get the getDir path for git specific executions, in underlying directory paths and doing a precommit for lint-staged. Using 'git' options specifically declares to use options that include the getDir option for doing precommits.
TODO

[x] use 'git' options only

Notes

Error report
SyntaxError: Unexpected token import at transformAndBuildScript (gui/node_modules/jest-
    runtime/build/transform.js:320:12)

Closes #158

Hey @DeFuex! Thanks for your contribution. Can you please add a description to your PR so we have a paper trail?
Also, can you add a code comment explaining why is this line ever needed? See https://github.com/okonet/lint-staged/issues/158#issuecomment-299910965
Thanks!

One issue that I'm having is that res.bin gives me an absolute path to git, so this condition will never work, perhaps we should check if res.bin ends with git?

Can you please also add a test for this case? After that it's good to merge! Thanks again for taking your time on this one.

There is a test already that is tests that git is called with the correct arguments. We'll need to update the test and check that other tasks aren't.

@okonet Doesn't this https://github.com/okonet/lint-staged/blob/master/test/runScript.spec.js#L98 cover that test?
Will add a test for findBin, is there a way to add to this PR without going through @DeFuex's branch?

Looks like you're right! I think then it can be merged. 👍

sry guys, was at an event today, everythings merged 😄

Any thought on when this change will be released?

@tnguyen14 it's released @3.4.2


Wrong link in "Read thousands of coding articles" button in https://www.freecodecamp.com/settings

Issue Description

In Settings, the Read thousands of coding articles button points to the wrong page. The href is the same as the one in the Add freeCodeCamp to my LinkedIn button.
Screenshot

I've got this.

It seems the issue is the "Add freeCodeCamp to my LinkedIn" button

I don't actually see where the code actually assigns these links.

@AlanGabbianelli thanks for the issue. Yes, this seems like an error. I'm not sure what the correct link should be though.
cc/ @QuincyLarson do you know what link is supposed to be here?

It's probably meant to link to the Medium publication - https://medium.freecodecamp.org/

Thanks for raising this issue. Sorry it took me so long to notice this issue. I've fixed this.


#174764844 Added feed endpoint

You will need to run the app in docker. Then in a separate terminal window, run the test_posting.py script, which will demonstrate that the functionality is working.
There are three responses in this file, so expect to see some duplicate information and a random spread of user scores at the beginning.
@biotom I've also added str casting to the UUID as a temporary solution.

I can write up a user story over the weekend to format the response.
On Thu, 24 Sep 2020 at 18:58, Kameron Rodrigues<EMAIL_ADDRESS>wrote:

@rodriguesk commented on this pull request.

In test_posting.py
https://github.com/ClimateMind/climatemind-backend/pull/61#discussion_r494507342
:

@@ -20,3 +20,9 @@

request = requests.post(url, json=obj, headers=headers)
print(json.dumps(request.json(), indent=4))

+url = "http://<IP_ADDRESS>:5000/feed"
+params = {"session-id": "6f3225f5-5fd8-4f58-a505-670592e46b9b"}
+request = requests.post(url, params=params)

+print(json.dumps(request.json(), indent=4))
The format is likely needed to be changed to fit what the frontend wants.
But we can figure those details out I guess after the first merge?
@NickCallaghan https://github.com/NickCallaghan
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ClimateMind/climatemind-backend/pull/61#pullrequestreview-495817949,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKVPTWMJIXFUKWUWXVOFU3LSHOCFNANCNFSM4RYK6IDQ
.
--
Nicholas Callaghan
161/3 Easter Rd
Edinburgh
EH7 5QB
07585 600 101

The only thing that is returned is the node title as specified in the
pivotal tracker spec
On Fri, Sep 25, 2020, 3:16 AM Kameron Rodrigues<EMAIL_ADDRESS>wrote:

@rodriguesk approved this pull request.
For future, please attach screenshot of the results you get from testing
the code using docker. This will help reviewers and the frontend give
feedback without needing to repeat everything themselves. 👍
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ClimateMind/climatemind-backend/pull/61#pullrequestreview-495835251,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCZ6OWG75AFH5XQUY4R7UDSHOEHPANCNFSM4RYK6IDQ
.


Support for kpack service bindings

It would be great if the tool could support creating the service bindings for kpack.
Would it also be a volume mount to the builder?
Sofar I don't know how one would add the bindings of this sort via kpack.
Or could it look something like this, where "..." is the URI to the file (might also be an https URL)?
apiVersion: v1
kind: Secret
metadata:
  name: dependencies
type: service.binding/dependency-mapping
stringData:
  type: dependency-mapping
  0d82ad4821b55d276d25486132f708f4cc747e242a9ce256fdf1c7f21979a94c : ...
  2bda48088925a5cead341ff9ae8b12c4075937f444827946a268ba773cf0339b : ...
  4f07a1c52b47c77b4e6a50623055de584d347002954ffa0029aedc915c035a17 : ...
  583d7da65e1b3f4b470e595c21d55dd3eb176789c7dea7d15cbec42b74877b50 : ...
  73c602ff0790a4ab325db06cae45f488f7e3613d781d688a204efa6325cebdd0 : ...
  74de76313848ef719d066854fe94dcec53fdcd111c630921b6b24e1b2e6897e7 : ...
  7d1056af3efbc998ac62c31197e18f32f7e58ac086d4636e559cc57d5edfb23d : ...
  883a25a15a6aa9d74ae35b23efdb6dced85e52b9519fc590313cec6c2626af79 : ...
  b389036c7ba1eca72c784c73c02d9397e81ced07a713f289430d7089376aac7f : ...
  c0feff461fb48d6b5745638fa6ac3901238b5fcbf09a2fcc5e771c55a743f0df : ...
  cf23e85f5a6b4e22007ce2572d38182f535ad22fcf937def8f781181fbb86b65 : ...
  d9e9ba6e872c2d7073e69407196be29db27d4fcd22de6ca7dde40840b934c286 : ...

@dmikusa - We are looking for similar feature, so is there any plan to get this in near future ?

Please check out https://github.com/paketo-buildpacks/rfcs/pull/302. I think this is going to be the path forward for most users with respect to dependency mapping. Please let me know though.
To move this one forward, i think I'd need to get some examples of what we need the tool to generate. I don't have kpack deployed, so I can't easily make them. If you give me some templates, it's pretty easy to make the tool generate them.

If my understanding is right ,currently  pack users should use the --volume flag to mount a binding directory into the build or app containers. Users of the kpack platform should store key value pairs in a Kubernetes Secret and provide that secret and associated metadata to an Image as described in the kpack documentation(opens in a new tab).
Is binding tool going to supports creation of secrets in future ?

@dmikusa - Can above format be possible from the bt tool ?

Yes, the tool could definitely generate secrets.
What is your thought on how to tell the CLI you want it to generate the secrets file? I could add a flag to bt dm, like bt dm --k8s-secrets that when set would also write the secrets file.
Also, what is your thought on running the command multiple times? I suspect that we'd need to read the secrets file, locate the particular dependency mapping and then update it (if modified) or add new mappings to the list of mappings. Does that sound reasonable?

Yes, Something like  bt dm --k8s-secrets should work.
I think we can just add new mappings to the list when command is run multiple times.

@dmikusa  Just checking if the above capability is added to the tool?

Sorry @doddisam I went to look at this again, and I'm not sure I follow in terms of what the value of the secret should be. In the example you provided, it's pointing to artifactory, which isn't really consistent with what the tool does now. It's purpose is to fetch from remote URLs and to generate a local folder structure that could be used as place from which to fetch the dependencies. Given that, the value would probably be file://... but I'm not sure what makes the most sense there in terms of K8s. What were you thinking?
I would also refer you back to https://github.com/dmikusa/binding-tool/issues/5#issuecomment-2026102918 because if you're just trying to point your buildpacks to an artifactory cache that you have already set up, you can do that with the dependency mirror RFC, which has been implemented for all of the Java-based buildpacks.
See https://paketo.io/docs/howto/configuration/#dependency-mirrors for docs on using that.

@dmikusa is dependency mirrors work for dotnet build pack also ?

I believe that it should. It looks like packit implemented the RFC a few months back, see https://github.com/paketo-buildpacks/packit/pull/563.
So long as that set of buildpack has updated packit to at least https://github.com/paketo-buildpacks/packit/releases/tag/v2.13.0.
I don't think there should be anything else that's needed.


Istio does not work in cluster with restricted psp as default

Rancher Version
master 8/28
Similar to https://github.com/rancher/rancher/issues/20229, but for validating Istio.
Steps to reproduce

Create a custom cluster with pod security policy enabled and the default set to restricted
After the cluster has been created, enable Istio.

With the default configurations, Istio proxy sidecars require NET_ADMIN capability to set iptable rules, which is not ideal from security perspective.
To address this, A proper way is to use the Istio CNI plugin that operates iptables in the CNI layer, so that the sidecars can work without additional capabilities.
Here is the workflow to do that at the moment:

Create/Edit a RKE cluster with the following configuration:

services:
    kubelet:
      extra_binds:
        - '/lib/modules:/lib/modules'

So that the cni plugin can leverage the iptables module to set networking rules.
2. Make System project nonrestricted, or grant proper PSP so that Istio control plane can set up as expected.
3. Install the cni plugin to the cluster:
# The istio-cni chart is in istio/cni repo.
helm template install/kubernetes/helm/istio-cni --name=istio-cni --namespace=kube-system \
    --set logLevel=info \
    --set excludeNamespaces={"istio-system,kube-system"} | kubectl apply -f -

enable Istio with a custom answer istio_cni.enabled: true

After these steps, Istio injected sidecars can work with restricted PSP.
NB: The Istio CNI plugin is in alpha version at the moment, see.

Tested the above steps on a PSP enabled master setup. With the workaround, Istio is functional.Graphs are displayed correctly.
Note: With the Istio CNI plugin, only Istio-proxy sidecar is deployed. Istio-init sidecar is not deployed . (In a regular setup without PSP enabled, both istio-proxy and istio-init containers are deployed)

@rancher-max Please follow these instructions to get PSPs working with Istio. https://rancher.com/docs/rancher/v2.x/en/cluster-admin/tools/istio/setup/enable-istio-in-cluster/enable-istio-with-psp/

These instructions have been validated as working exactly as is. Please note that this uses istio-cni, which is currently in Alpha status at the time of the writeup: https://istio.io/about/feature-stages/


14.1 Version

Hi Andreas,
first of all thanks for the great launcher. How can I update to 14.1 as Server version?
All the best
Martin

Hi Martin,
i updated the project to the current version 14.1. You can now pull the newest version.
Kind Regards
Andreas

WoW thanks so much for the quick push to 14.1 <3


[MPoW] Owner should be able to approve the request of joining the group

Member needs to have work report, so it is no need to import this mechanism


Transcrypt: Inherit from a JS prototype?

I am prototyping with KiwiJS and i it works the "JavaScript" way, but since Transcrypt uses python syntax i wanted to use the "Typescript" way using classes, see this.
So how to inherit a Transcrypt class from a JS prototype?
In my case  i want this to work:
# Kiwi obviously the KiwiJS library
class GameState(Kiwi.State):
    gameOver = False

    def checkGameOver(self):
        pass

    def update(self):
      Kiwi.State.prototype.update(this)

    def postUpdate(self):
      Kiwi.State.prototype.postUpdate(this);
      this.gameOver = this.checkGameOver();

by the way this works fine:
gameState = __new__( Kiwi.State('gameState'))

def game_preload():
    Kiwi.State.prototype.preload.call(this)
    this.addImage('logo','kiwilogo.png')

def game_create():
    Kiwi.State.prototype.create.call(this)

    this.logo = __new__(Kiwi.GameObjects.StaticImage(this, this.textures['logo'], 100, 100) )
    this.addChild(this.logo)

def game_update():
    Kiwi.State.prototype.js_update.call( this )
    this.logo.rotation += 0.01

gameState.preload = game_preload
gameState.create = game_create
gameState.js_update = game_update

game.states.addState(gameState, True)

Also i found this question on stackoverflow.com with same question.
thanks in advance.

Hi,
I've attempted an answer at:
https://stackoverflow.com/questions/44213824/transcrypt-inherit-from-a-js-prototype/44333571#44333571
Let me know if it works for you.
Kind regards
Jacques

Hello,
I was busy graduating (from yesterday, i can say i am a telecommunication engineer).
i will test it and report soon.

Hello,
I was busy graduating (from yesterday, i can say i am a telecommunication engineer).
i will test it and report soon.

Congratulations!

Thank you, i tried to understand but this is not clear for me, can you make a simple example code ?

I realize this is 5 months old, but I posted a demo today that does what I think you are after.  Jacques recommends using composition, and I tried that first.  But I think I have it working in the "normal" way, although Jacques may correct my method.  But here's how I extended React.Component, which is a pure JS class:
class MyComponent(object, React.Component.prototype):
    def __init__(self, props):
        object.__init__(self)
        React.Component.apply(self, [ props ])

By extending both Transcrypt's object and the JS prototype I wanted, I get the behavior of both.  Inside init, I had to call the JS class' constructor by using .apply.  The resulting class (prototype) had attributes of both supers.
The full code is here: https://github.com/doconix/pyreact/blob/master/scripts/pyreact.py

@doconix Thanks!


[kf5textwidgets] new port

Describe the pull request

What does your PR fix?
Adds new kf5textwidgets port.
Depends on:

[x] #16562. Was merged to this PR for testing purposes, but please review separately. I will rebase once it gets merged upstream.

Which triplets are supported/not supported? Have you updated the CI baseline?
All official.

Does your PR follow the maintainer guide?
Yes.

Yes.

@JonLiu1993 this no longer depends on any PRs, all dependencies are in master. All requests solved as well.

I'd like to see a solution to https://github.com/microsoft/vcpkg/pull/19195#pullrequestreview-744280457 before merging this

I'd like to see a solution to #19195 (review) before merging this

Same solution as noted in https://github.com/microsoft/vcpkg/pull/19195#discussion_r703106264

@wrobelda ,This pr also depends on #20090

@wrobelda ,This pr also depends on #20090 ?

@JonLiu1993 not really, the #20016 provided all the fixes for kf5i18n. Once #20090 gets merged, I'll update kf5i18n and remove its patch.
@20016 was merged to master already, so I rebased this PR and it's good to go.

Thanks again!


unable to retrieve child resources

Preflight Checklist

[X] I have installed the latest version of Storage Explorer.
[X] I have checked existing resources, including the troubleshooting guide and the release notes.
[X] I have searched for similar issues.

Storage Explorer Version
1.26.1
Regression From
No response
Architecture
x64
Storage Explorer Build Number
No response
Platform
Windows
OS Version
Windows 10
Bug Description
unable to expand the child file shares from a storage account

Steps to Reproduce

Launch explorer
expand storage account
expand file share
getting below error ( detailed error attached)

Storage explorer error.txt

Actual Experience
getting error when expand file share
Expected Experience
show the list of file share
Additional Context
No response

@RanjithMadathil do you know if you have access to the keys for the storage account you are trying to list file shares for?

Closing due to lack of response. If you still have this issue, please open a new issue instead.


Update 1.1 tests

Tests for:

Presenters
Use Cases
Repositories
Some data layer classes

Codecov Report

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

@@            Coverage Diff            @@
##             master       #3   +/-   ##
=========================================
  Coverage          ?   40.78%
=========================================
  Files             ?       67
  Lines             ?      966
  Branches          ?      117
=========================================
  Hits              ?      394
  Misses            ?      542
  Partials          ?       30

Impacted Files
Coverage Δ

...wsfeed/presentation/ui/details/DetailsPresenter.kt
64% <ø> (ø)

...tek/newsfeed/presentation/ui/list/ListPresenter.kt
59.25% <ø> (ø)

...voltek/newsfeed/presentation/base/BasePresenter.kt
100% <ø> (ø)

...src/main/java/com/voltek/newsfeed/domain/Mapper.kt
74.07% <ø> (ø)

...ltek/newsfeed/presentation/ui/list/ListFragment.kt
0% <0%> (ø)

...ewsfeed/presentation/ui/details/DetailsFragment.kt
0% <0%> (ø)

...resentation/ui/news_sources/NewsSourcesFragment.kt
0% <0%> (ø)

...newsfeed/presentation/ui/splash/SplashPresenter.kt
42.3% <0%> (ø)

...eed/domain/exception/WrongNewsSourceIdException.kt
100% <100%> (ø)

...domain/exception/NoNewsSourcesSelectedException.kt
100% <100%> (ø)

... and 3 more

Continue to review full report at Codecov.

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


Expose the HTML backend so that simply comments can be converted

Original reporter: david.waern@
The haddock library currently does not expose functionality for
converting strings of Haddock markup to HTML.
This functionality is needed by Hackage, for example, to render
package description text. Hackage duplicates the haddock parsing and
lexing code rather than using it directly:
http://code.haskell.org/hackage-server/Distribution/Server/Pages/Package/
We should add functions to the Haddock API for parsing the markup.

I believe this was resolved by https://github.com/haskell/hackage-server/commit/0617b1bb8e485bc56aeec1dc49abae5e76bddc89


Duplicate block of parameter

There is 3 times a parameter block.

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

ID: 316bada1-dbc7-f07a-4afa-d67330edef50
Version Independent ID: d9380f67-a05a-ddd0-425c-af7023222c69
Content: New-UnifiedGroup (exchange)
Content Source: exchange/exchange-ps/exchange/users-and-groups/New-UnifiedGroup.md
Service: exchange-powershell
GitHub Login: @chrisda
Microsoft Alias: chrisda

@aavdberg I realize it's a lot like playing "Where's Waldo?", but if you look closely, there should be at least one parameter difference between the blocks. For example, in your PR #1630, Set3 contains the SubscriptionEnabled parameter that isn't in Set2. And Set1 contains the MailboxRegion parameter that isn't available in the other two. Really, the presence or absence of multiple Syntax blocks (parameter sets) is determined by code, and shouldn't be manually modified unless multiple sets are absolutely identical in every way.
I took the liberty of running the updated version of platyPS in Exchange Online to re-dump the New-UnifiedGroup cmdlet, which gave meaningful names to the parameter sets, which I used to update the topic. And, I closed your pull request #1630, which was sitting in limbo because you need to sign the Contributor License Agreement.
Thanks for the feedback.


Passing JS callback function from WebView A to WebView B through Bridge

Hi,
First, thanks for this project.
Second, I have more of a general question of "can this be done using this bridge". Apologies in advance if this is not the right place to ask.
Say I have two different WebViews A and B. I would like to use the bridge to pass a JS callback function from A to B. B can then store the JS callback and fire it at any time and it will hit back to the origination on A's WebView.
Does this sound like something that can be done? If not, do you or anyone have any recommendations on how to achieve this? I appreciate any insight.

Every message sent over WebViewJavascriptBridge gets JSON encoded. Since
there is no way to JSON encode a function, you can't send one over the
bridge.
It would be easier to understand what you want to accomplish if you include
example code.
Cheers,
Marcus
On Sat, Jan 24, 2015 at 11:35 AM, Mike Wilcox<EMAIL_ADDRESS>wrote:

Hi,
First, thanks for this project.
Second, I have more of a general question of "can this be done using this
bridge". Apologies in advance if this is not the right place to ask.
Say I have two different WebViews A and B. I would like to use the bridge
to pass a JS callback function from A to B. B can then store the JS
callback and fire it at any time and it will hit back to the origination on
A's WebView.
Does this sound like something that can be done? If not, do you or anyone
have any recommendations on how to achieve this? I appreciate any insight.
—
Reply to this email directly or view it on GitHub
https://github.com/marcuswestin/WebViewJavascriptBridge/issues/121.

Say I have some listening code on WebView A:
    PlansActions.prototype.addIOSListeners = function (bridge) {
        var _this = this;
        bridge.init();
        bridge.registerHandler('SUBSCRIBE:PlansStore', function (data, responseCallback) {
            log('Bridge Handler is storing iOS callback with Plans Store', responseCallback);
            Dispatcher.dispatch({
                type: 'SUBSCRIBE_PLANS_STORE',
                callback: responseCallback
            });
        });
    };

Now, in WebView B I have a component there who wants to talk to WebView A, specifically to get inside the 'SUBSCRIBE:PlansStore' handler on WebView A.
To start the communication in WebView B I create a wrapper around .callHandler and pass in the handlerName and callback:
this.BridgeService.subscribeToStore('Plans', this.updatePlans.bind(this));

BridgeService.prototype.subscribeToStore = function (storeName, callback) {
  var handler = 'SUBSCRIBE:' + storeName + 'Store';
  if (this._bridge)
    this._bridge.callHandler(handler, callback);
  else
    this._queue.push({ type: 'subscribe', handler: handler, callback: callback });
};

Now this is where it breaks down a little for me, admittedly my ObjC knowledge is not the greatest...
In ObjC I listen for the callHandler from WebView B and then I'd like to take a callback function that WebView B passes and call from Bridge to JS with it and store it in WebView A so WebView A can call it back at a later date. Something that could theoretically look like this?
    [_bridge registerHandler:@"SUBSCRIBE:PlansStore" handler:^(id data, WVJBResponseCallback responseCallback) {
        NSLog(@"Heard that you want to subscribe to plans store: %@", responseCallback);

        [_bridge callHandler:@"SUBSCRIBE:PlansStore" data:nil responseCallback: responseCallback];
    }];

I can get as far as seeing that I have heard from WebView B in ObjC. After seeing your response, I guess will probably have to think of another way to solve this?

So I went about it a little differently, but I think it solves my problem. Basically I added a new handler that will be called for change events. Then, WebView B can register for this handler and the callback can be stored there. WebView A calls the handler when something changes, B hears it, and calls the callback. This way don't need to pass callbacks.
Cheers!

Sounds like you solved your problem, yes?
Good stuff! Cheers :)
-- while mobile
On Sat, Jan 24, 2015 at 6:24 PM, Mike Wilcox<EMAIL_ADDRESS>wrote:

So I went about it a little differently, but I think it solves my problem. Basically I added a new handler that will be called for change events. Then, WebView B can register for this handler and the callback can be stored there. WebView A calls the handler when something changes, B hears it, and calls the callback. This way don't need to pass callbacks.
Cheers!
Reply to this email directly or view it on GitHub:
https://github.com/marcuswestin/WebViewJavascriptBridge/issues/121#issuecomment-71342675

Yes. I'll close this.
Thanks for your responses! :)


Remove lots of hardcoded values for config, and adds the authenticate hook

Fixes typedefs from #412.

Also, #412 defined legacy hooks, while there's only one hook in 1.x.


[WIP] Only delete storage profiles on full EMS refresh

Purpose or Intent
Fix an issue where storage profile records were being deleted when a targeted refresh of a VM or Host was run.  Now only delete storage profiles when a full EMS refresh is run (same as folders, resource pools, etc...)
Steps for Testing/QA
Using the rails console:

Run a full refresh
EmsRefresh.refresh(ExtManagementSystem.first)
Check the number of storage profiles and storage profile - storage associations
StorageProfile.count
StorageProfileStorage.count
Run a targeted refresh
EmsRefresh.refresh(Vm.first)
Confirm the number of storage profiles hasn't changes
StorageProfile.count
StorageProfileStorage.count

@miq-bot add-label bug, providers/vmware/infra

@miq-bot add-label wip

@miq-bot remove-label wip

A lot of Hashes and arrays in here, but I guess thats all good
So, besides the entities.nil? probably being entities.empty?, LGTM

@durandom fixed the entities.empty?

:+1: from me, although I have to admit that I dont fully understand the code and business logic behind this. But this is due to my lack of knowledge in the Vmware and Refresh business.
@blomquisg good to merge
@miq-bot assign blomquisg

@agrare this is darga/no, correct?  I don't think there's any storage profile support in darga...

@blomquisg correct darga/no for all storage profile stuff


Made it so up can target environment and fixed no op issues

Description
This includes two fixes: 1) allow the up command to target environments to modify in addition to datacenters to create a new env in, 2) Improved the no-op assignment so that resources with no-op'd dependencies are capable of being no-op'd.
Closes https://github.com/architect-team/arcctl/issues/149
Closes https://github.com/architect-team/arcctl/issues/90
Closes https://github.com/architect-team/arcctl/issues/145
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How Has This Been Tested?
$ arcctl create env test ...
$ arcctl deploy architectio/kratos:latest -e test
# Do it again to make sure everything no-ops
$ arcctl deploy architectio/kratos:latest -e test
# Use up command to target test environment
$ arcctl up . -e test

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules
[x] I have checked my code and corrected any misspellings

@mueschm I found a lot of issues with the code that you reviewed the first time. Can you review again to make sure new code isn't stupid?


content of page does not agree with portal - i don't see Monitoring + Managment anywhere

Azure documentation issue guidance
Thanks for opening an issue in the Azure technical documentation repository.
We use GitHub issues as the primary channel for customer and community feedback about the Azure documentation.
Creating an issue
We prefer that you create documentation feedback issues using the Feedback link on the published article - the feedback control on the doc page creates an issue that contains all the article details so you can focus on the feedback part.
You can also create a feedback issue here in the repo. If you do this, please make sure your issue lists:

[ ] The relevant Azure service or technology.
[ ] A link to the published documentation article that you have feedback about.
[ ] Clear, specific feedback that the author can act on.

Pull requests and article contributions
If you know the change that is needed in an article, we encourage you to submit the changes directly using a pull request. If the change is large, or if you want to contribute an entire article, follow these guidelines:

[ ] Don't surprise us with a big pull request or a pull request with a new article! Submit an issue that describes the details of the proposed large change or new article.
[ ] Include the service or technology area.

We'll route the issue to the appropriate content team for review and discussion.
Tech support and product feedback
If you would like to contact Microsoft about other things, such as product feedback or tech support, please review these guidelines:

If you need technical support using Azure, the paid and free support options are described here: https://azure.microsoft.com/support/options/.

Each article in the Azure technical documentation contains a product feedback button - it's best to submit product feedback directly from a relevant article. Otherwise, you can submit product feedback for most Azure products in the following product feedback forum: https://feedback.azure.com/forums/34192--general-feedback.

@TomCJones  can you please post a link to the documentation page you are referring to?

@TomCJones We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


C_CPP: Greedy-Car Sell Problem

Description
Documentation for car selling problem to achieve maximum possible profit. Code snippet added is in C and C++.
Domain
C/CPP
Type of Contribution
Documentation
Code of Conduct

[X] I follow Contributing Guidelines & Code of conduct of this project.

/assign


LESS pre-processor and LESS template

Description
As discussed in catppuccin-rfc/userstyles as well as on discord, we wish to transistion the userstyles ports to use the LESS pre-processor. Hopefully, streamlining the process of userstyle port creation and debugging.
Acceptance Criteria

[ ] Convert all current userstyles ports to use the less preprocessor
[x] Create a userstyles template to help improve port creation process.

These still need to be converted to the less pre-processor:
-[] wikiwand
-[] tutanota
-[] vercel
-[] SearXNG
-[] reddit (there could be a theme overhaul soon might be worth waiting on this one)
-[] proton
-[] modrinth
-[] libreddit
-[] lastfm
-[] ichi.moe
-[] hacker-news
-[] github (i'm told its being worked on)
-[] elk
-[] deepl
-[] codeberg
-[] brave-search


Change minted on floor.fun to minted on rally.xyz

User description
Mint Ingestor:
Functionality Supported

Ingesting from URL: Yes / No
Ingesting from Contract address: Yes / No
Supported Networks: Base / Ethereum / Arbitrum / Zora / Polygon / Others..

Before you submit

[ ] Ensure your generated MintTemplate works 😄
[ ] Ensure that your code is restricted to a single folder in src/ingestors
[ ] Ensure that all required assets are included (e.g. ABIs)
[ ] Ensure ABIs are trimmed to include only methods (1) used in the ingestor or (2) required to mint
[ ] Ensure that all exported methods are prefixed with the name of your ingestor e.g. myMintingPlatformGetContractDetails
[ ] Ensure that a test exists for generating a MintTemplate that will always succeed
[ ] Ensure that your code accesses no external resources except those passed in the resources object

PR Type
enhancement

Description

Updated the minting comment in the Zora metadata provider to reflect the change from "Minted on floor.fun" to "Minted on rally.xyz".

Changes walkthrough 📝
Relevant filesEnhancement

zora-metadata.tsUpdate minting comment to reflect new platform

src/ingestors/zora-internal/zora-metadata.ts
Updated the minting comment from "Minted on floor.fun" to "Minted on rally.xyz".

+1/-1

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

hey @chrismaddern i started a new PR from a fresh clone for this
now a bunch of the highlight tests are failing? not sure why

@agans highlight tests are failing on main :(
Not a problem with your code -- seems something about their API / contracts are no longer accepting mints


socket.Receive always return length 0

socket.Receive always return length 0 in WhatsNetwork Class Please help with this.

@Shahid-Awan have you had any success in this? please get in contact with me or pm me.

same problem :(

same problem!


[DO NOT MERGE] CI monitor

/retest

@yutongz: The following test failed, say /retest to rerun them all:

Test name
Commit
Details
Rerun command

prow/e2e-simpleTests.sh
cfef247b5be867ea2ed6fe3d5e58dec8c5c3ff12
link
/test e2e-simple

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.


Update README.md

Updated the readme fo fix:
-The Title format so it shows up as bold.
-Updated the link that points to the startup.ps1 template since it has been moved from on-http to on-taskgraph

@RackHD/veyron


Fix construction of varacset from FinDomFunctor

(::Type{ACS})(F::FinDomFunctor) would previously give back an ACS{Any} if ob_map(F,:someAttr) was a VarSet and an ACS{Union{AttrVar,T}} if ob_map(F,:someAttr) was TypeSet{Union{AttrVar,T}}.

Thanks for the fix, Kevin!
Confused about what is going on the CI here: the tests haven't run for the latest commit.


⚠ Bofrost.be has degraded performance

In f63256e, Bofrost.be (https://www.bofrost.be) experienced degraded performance:

HTTP code: 200
Response time: 2152 ms

Resolved: Bofrost.be performance has improved in c7654b7.


fix: init --remote breaks on Using foreign key constraint on a remote table

Should fix #150

The problem is that ForeignKeyConstraintOn can either be a string or an object.
I introduced a custom type to cope with both variants.

The problem is that ForeignKeyConstraintOn can either be a string or an object. I introduced a custom type to cope with both variants.

thanks for clarification!


sys/linux/socket_netlink_route: add specific policies for IFLA_LINKINFO

Add interface specified policies for IFLA_LINKINFO. I only added the
interfaces we create in initial setup. Remain other types of interfaces
in the TODO list.
Signed-off-by: Hangbin Liu<EMAIL_ADDRESS>

Thanks!


KubeClientCertificateExpiration always alert

What did you do?
wget https://codeload.github.com/coreos/prometheus-operator/tar.gz/v0.23.1 install prometheus-operator use kubectl create -f prometheus-operator-0.23.1/contrib/kube-prometheus/manifests/ || true
What did you expect to see?
all components work correctly.
Environment

K8s version: v1.11.0

Prometheus Operator version: v0.23.1

Kubernetes cluster kind:
      install k8s cluster use binary package  https://storage.googleapis.com/kubernetes-release/release/v1.11.0/kubernetes.tar.gz

Manifests:

[2] Firing
--
Labels
alertname = KubeClientCertificateExpiration
job = apiserver
prometheus = monitoring/k8s
severity = critical
Annotations
message = Kubernetes API certificate is expiring in less than 1 day.runbook_url = https://github.com/kubernetes-monitoring/kubernetes-mixin/tree/master/runbook.md#alert-name-kubeclientcertificateexpirationSource

Labels
alertname = KubeClientCertificateExpiration
job = apiserver
prometheus = monitoring/k8s
severity = warning
Annotations
message = Kubernetes API certificate is expiring in less than 7 days.runbook_url = https://github.com/kubernetes-monitoring/kubernetes-mixin/tree/master/runbook.md#alert-name-kubeclientcertificateexpiration

I used cfssl generate pem and keys
# openssl x509 -in /etc/kubernetes/ssl/ca.pem -text -noout
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            6f:b9:70:eb:80:73:e6:73:f9:c8:29:98:99:5e:b5:f2:6d:a3:0e:49
    Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=CN, ST=Shanghai, L=Shanghai, O=k8s, OU=System, CN=kubernetes
        Validity
            Not Before: Aug  8 09:54:00 2018 GMT
            Not After : Aug  7 09:54:00 2023 GMT
        Subject: C=CN, ST=Shanghai, L=Shanghai, O=k8s, OU=System, CN=kubernetes
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:c8:ae:16:d6:0c:5b:30:95:97:a2:5b:16:cf:db:
                    f1:bd:68:8c:c6:0c:84:5b:a4:46:b4:79:0b:2b:c4:
                    b2:c0:5f:ab:e4:4a:33:46:d3:82:a3:33:bf:a7:f7:
                    ec:a3:4e:b3:70:34:e8:15:24:8e:56:b7:4d:68:9b:
                    e0:dc:0a:3a:3c:36:3e:f2:5c:be:d1:5d:fa:fa:e0:
                    7d:5b:2a:5d:e2:fc:94:9f:ea:a9:ce:ca:ad:2f:fd:
                    16:bc:fb:83:f6:45:fd:2f:9a:ac:94:e3:fd:49:90:
                    a1:31:95:cd:f2:30:2b:cd:31:34:69:b1:3a:b8:6a:
                    b8:7a:ef:f1:e9:ee:a2:5d:81:a8:59:80:77:c1:43:
                    85:3c:29:d8:02:fb:24:b9:9a:1f:e4:61:82:ec:8d:
                    49:3d:91:f7:0a:50:25:b1:a4:51:ba:f3:d6:77:07:
                    e2:50:ed:b8:af:30:18:d8:23:d6:e9:17:b1:a0:1c:
                    8c:74:f3:87:56:08:c7:49:86:c0:90:5e:16:a4:1e:
                    07:49:ef:b2:dc:9e:22:4c:b9:9b:7f:38:47:d7:26:
                    17:15:92:79:51:cc:a9:3f:4b:a1:6d:03:94:5b:9c:
                    03:c0:19:7e:d1:4e:c9:77:84:b1:e4:5b:a6:2b:54:
                    95:d0:a3:ef:39:d6:c3:88:77:af:4f:31:cd:ba:f7:
                    cc:3b
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Key Usage: critical
                Certificate Sign, CRL Sign
            X509v3 Basic Constraints: critical
                CA:TRUE, pathlen:2
            X509v3 Subject Key Identifier:
                BC:9F:D1:BD:4C:26:E1:77:C0:7F:CF:04:3E:DF:64:86:BE:23:F3:7F
            X509v3 Authority Key Identifier:
                keyid:BC:9F:D1:BD:4C:26:E1:77:C0:7F:CF:04:3E:DF:64:86:BE:23:F3:7F

    Signature Algorithm: sha256WithRSAEncryption
         78:b7:65:4d:53:e1:0c:7d:d6:9e:d5:aa:f8:1a:34:e4:1d:c0:
         22:4b:42:72:86:86:e9:73:e2:fd:89:90:e1:10:56:a7:f2:15:
         71:14:79:ce:67:9a:ca:5d:4d:e8:25:3d:70:2a:0a:3b:08:09:
         02:8a:d9:2d:ed:85:cd:10:38:60:75:d7:f5:a7:b2:ee:86:05:
         dd:50:38:04:a4:7a:bc:f5:02:b2:a5:d9:a2:a1:71:7d:e5:ce:
         dd:c8:5a:a7:25:61:de:c3:76:c3:87:3e:5a:4c:eb:36:91:51:
         8b:fc:ef:9d:aa:35:58:3a:ba:fc:2a:3c:4f:b3:54:e8:0d:a5:
         32:25:91:dd:93:75:33:53:2b:94:9e:f1:cb:e9:58:17:a6:dc:
         07:1c:96:5e:93:40:d6:c8:2b:67:49:3b:3f:1f:a8:3a:41:65:
         29:03:f3:18:f9:d3:66:a8:49:14:1e:7f:cb:6b:f6:26:1d:7b:
         6f:46:c6:27:a1:69:fe:62:7f:da:fb:41:7d:fc:ab:12:77:b8:
         b3:4c:92:a5:5c:d2:8c:25:a1:aa:1e:2f:a2:de:38:e5:9a:96:
         2f:b2:bb:3c:32:de:db:7f:80:eb:f0:01:be:2d:ff:00:09:35:
         ea:2b:8d:33:6e:6c:2c:6d:37:a2:c4:b3:c9:eb:ac:3f:ec:e5:
         5d:61:50:66

# openssl x509 -in /etc/kubernetes/ssl/kubernetes.pem -text -noout
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            76:64:c7:59:95:aa:fb:9b:8c:b2:26:c0:82:24:c5:0a:8d:95:a2:1e
    Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=CN, ST=Shanghai, L=Shanghai, O=k8s, OU=System, CN=kubernetes
        Validity
            Not Before: Aug  8 09:54:00 2018 GMT
            Not After : Aug  5 09:54:00 2028 GMT
        Subject: C=CN, ST=Shanghai, L=Shanghai, O=k8s, OU=System, CN=kubernetes
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:b9:7e:1b:a9:9a:95:21:42:5a:e8:3e:79:94:e6:
                    c1:35:87:93:22:3d:3c:c9:65:be:b6:99:4b:47:25:
                    1a:22:db:4a:a5:b8:59:0d:2d:a0:0d:e5:c6:35:3b:
                    8e:2c:e3:fe:3a:d9:bc:63:9b:a0:98:c2:26:98:4c:
                    be:8b:71:20:37:a3:19:21:34:03:0b:10:d7:cb:7c:
                    b6:d8:68:90:1b:e1:6b:ee:b8:0e:6f:3d:33:2b:3f:
                    87:9a:4f:6c:59:08:f4:22:a6:2a:b6:d5:d6:00:b8:
                    7e:3c:90:aa:99:5c:6e:7c:93:f2:6b:6a:6f:5b:c6:
                    35:60:e0:14:62:5e:91:cc:20:eb:88:ea:cc:7a:10:
                    d7:f1:5f:b3:fb:aa:c4:a7:f5:95:3e:8a:44:ee:09:
                    12:6b:aa:29:05:40:df:1e:54:25:05:e2:8c:cb:d7:
                    32:e8:c5:ff:0c:48:11:27:c9:52:81:f2:53:b0:82:
                    b0:1b:7f:ad:08:fd:cd:b6:c1:4e:43:da:2d:f0:90:
                    90:cb:97:a2:2a:31:bc:65:2c:9f:a9:72:90:dd:b0:
                    5e:3b:7d:1c:37:d6:ca:22:13:2a:da:27:1d:61:94:
                    8f:36:9f:9d:6a:d1:6c:b9:17:58:5d:9c:0d:b1:d8:
                    2a:98:f1:54:d7:87:c6:da:ff:05:c9:a2:c5:91:5a:
                    77:23
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment
            X509v3 Extended Key Usage:
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 Basic Constraints: critical
                CA:FALSE
            X509v3 Subject Key Identifier:
                B3:1C:65:F4:DA:61:57:1F:68:06:05:46:36:31:BC:AF:E1:D5:06:7C
            X509v3 Authority Key Identifier:
                keyid:BC:9F:D1:BD:4C:26:E1:77:C0:7F:CF:04:3E:DF:64:86:BE:23:F3:7F

            X509v3 Subject Alternative Name:
                DNS:kubernetes, DNS:kubernetes.default, DNS:kubernetes.default.svc, DNS:kubernetes.default.svc.cluster, DNS:kubernetes.default.svc.cluster.local, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>, IP Address:<IP_ADDRESS>
    Signature Algorithm: sha256WithRSAEncryption
         2d:a6:ee:28:71:0f:ea:69:ff:90:25:d6:04:4e:4c:e1:3d:ff:
         34:f1:64:67:4f:ab:80:ee:f5:d9:16:53:48:0c:c4:fd:9a:f0:
         09:13:71:b1:ba:52:b0:36:38:6b:51:be:ac:cc:14:30:2b:e7:
         a9:87:00:76:fe:1a:58:72:45:27:0a:59:51:74:65:6a:30:ea:
         37:f3:c9:79:59:f0:09:87:e9:94:99:00:11:d7:20:9c:90:5c:
         de:ee:09:ff:53:07:41:06:4c:91:8d:8a:d1:d5:ff:30:06:3b:
         53:32:4c:dd:70:f0:22:7f:7d:e6:02:f2:eb:a6:fd:5a:de:d6:
         0d:fa:b5:e9:f0:95:5a:79:bb:f9:b5:a5:47:01:13:3f:b0:12:
         c6:35:11:45:2f:6b:f3:71:26:92:8f:34:90:0f:42:d8:2a:12:
         0f:ad:96:1f:60:54:5c:27:f3:0f:c3:4e:f5:ef:58:75:51:7a:
         df:8c:f3:b2:d4:b8:70:99:ff:e3:5a:ee:a9:00:69:84:a3:c2:
         df:7e:9b:55:e1:ab:92:bb:55:8b:54:6c:aa:05:c4:ea:29:8e:
         56:72:15:11:c2:6e:49:72:b5:d7:30:06:7b:c4:a2:0a:82:87:
         19:83:b7:1e:3a:86:02:35:f5:21:e8:e6:bf:5e:51:c0:ec:f0:
         c1:3d:15:35

# openssl x509 -in /etc/kubernetes/ssl/admin.pem -text -noout
Certificate:
    Data:
        Version: 3 (0x2)
        Serial Number:
            30:7e:a9:d4:1c:0a:04:d7:3b:2a:38:7a:b3:ca:25:fb:65:e3:e6:72
    Signature Algorithm: sha256WithRSAEncryption
        Issuer: C=CN, ST=Shanghai, L=Shanghai, O=k8s, OU=System, CN=kubernetes
        Validity
            Not Before: Aug  8 09:55:00 2018 GMT
            Not After : Aug  5 09:55:00 2028 GMT
        Subject: C=CN, ST=Shanghai, L=Shanghai, O=system:masters, OU=System, CN=admin
        Subject Public Key Info:
            Public Key Algorithm: rsaEncryption
                Public-Key: (2048 bit)
                Modulus:
                    00:cb:10:41:82:61:ec:93:e8:4d:bf:3e:2d:88:45:
                    ce:e8:57:ee:c6:90:8c:a2:e7:7b:16:ae:9e:fc:6e:
                    60:25:5c:f4:26:c2:50:c7:b5:1e:d3:91:d8:54:e9:
                    5b:6f:85:0e:0a:56:2c:e8:4d:69:dc:06:1e:94:92:
                    29:b9:7c:6f:cd:bd:25:13:bf:c9:9b:98:dd:81:f2:
                    0e:df:27:17:75:c9:4f:d8:9a:9c:5c:b0:db:9c:ed:
                    bb:a5:1f:c1:df:85:9a:f9:62:6b:a8:7a:96:69:30:
                    93:2f:e9:e3:16:dc:74:5f:4d:68:5d:e3:05:ae:01:
                    bd:60:72:d0:30:7c:3b:01:7a:13:9f:4c:ef:62:f2:
                    6c:47:6a:25:6f:b4:0c:7a:53:db:78:a4:71:00:c8:
                    6c:a7:c6:39:42:cf:da:e0:20:ce:66:02:36:43:13:
                    5a:56:7d:da:77:ad:01:4f:ab:56:54:6d:b9:27:08:
                    4e:d6:95:8b:cd:90:5f:28:c2:63:de:d8:f9:77:4f:
                    6d:35:02:9b:6c:cf:27:43:8a:47:b0:74:7e:25:c5:
                    6c:2d:7a:4b:e1:49:af:e7:28:d1:e0:3b:2a:21:1d:
                    bd:09:80:f7:4f:ee:a9:23:50:8c:65:55:0b:fd:d8:
                    4b:4b:b3:82:cb:2a:9f:33:c7:d3:88:63:91:ca:f9:
                    e1:a7
                Exponent: 65537 (0x10001)
        X509v3 extensions:
            X509v3 Key Usage: critical
                Digital Signature, Key Encipherment
            X509v3 Extended Key Usage:
                TLS Web Server Authentication, TLS Web Client Authentication
            X509v3 Basic Constraints: critical
                CA:FALSE
            X509v3 Subject Key Identifier:
                DA:B4:8B:36:C7:E9:9C:C0:6E:AC:8D:1F:D6:18:93:76:4D:6E:78:1F
            X509v3 Authority Key Identifier:
                keyid:BC:9F:D1:BD:4C:26:E1:77:C0:7F:CF:04:3E:DF:64:86:BE:23:F3:7F

    Signature Algorithm: sha256WithRSAEncryption
         2f:69:9c:6f:53:bb:7a:42:e3:4e:8f:b4:17:00:10:90:c3:1c:
         be:68:05:f3:15:6a:aa:0c:53:eb:89:c6:0c:2e:c2:0a:75:14:
         16:09:7e:68:0e:83:5c:c9:79:e0:ab:86:ee:93:d7:de:50:66:
         98:3d:5a:43:e0:7f:dd:dc:8a:b8:83:84:84:d4:0f:a5:c5:a1:
         b2:4a:65:76:15:e7:85:f3:7d:37:ee:e2:50:70:28:85:e8:05:
         05:d1:60:74:40:e2:67:7a:31:32:39:e3:96:e3:5b:fe:5e:eb:
         36:ef:cf:fa:95:37:9c:f1:3a:f5:11:80:e8:80:f9:1c:39:04:
         a0:14:af:e0:e7:ac:ce:6f:ad:4a:f3:e8:24:13:20:72:46:15:
         da:9a:e3:1d:88:c5:3d:93:12:7c:71:d3:77:95:5b:cd:f7:3b:
         b3:33:5d:10:31:7e:d9:ba:0e:ed:c8:61:9a:e7:df:fa:75:f1:
         f4:e5:67:81:be:3b:4a:5d:1e:82:1e:64:f7:16:14:4c:d9:e1:
         09:56:81:f4:64:21:47:79:f2:50:55:bb:e1:28:21:40:22:7d:
         f6:b7:f1:cd:3f:99:e5:96:c9:ee:76:be:03:68:da:7a:94:f5:
         ad:bb:40:66:cc:8c:85:36:91:3d:6a:5e:f6:d8:71:23:9e:f1:
         97:ff:73:ea

my k8s cluster  and prometheus  seems fine. but  KubeClientCertificateExpiration always trigger alert, how do I fix it ?

Hi! I'm new to Kubernetes and I'm sorry if it's a dumb question, but how exaclty the apiserver_client_certificate_expiration_seconds histogram and metric can be useful? We can't really tell, who was that client with the expiring certificate, so what's the big point in it then?
It would be much better if we would have metrics (like at least notAfter property) for each certificate that is used in the cluster directly in the API (for all components, like etcd/front-proxy/controller manager etc.) the same way we can get them with kubeadm certs check-expiration. If you have another etcd or some other component on some node, you should be able to retrieve that data through API as well. And metric's description should clearly state what it's puprose.
I understand that with kubeadm you get these on the file level from PKI directory, but this just looks very strange that you can't really get this data natively through API and that in such cases you have to use 3rd party solutions, like x509-certificate-exporter.

I managed to fix this by upgrade prometheus from 2.37.1 to current latest version 2.44.0（only tested on this version）

Still receiving these alerts


KAFKA-10361: Windows batch files that use /bin/windows/kafka-run-class.bat fail with a class path error on fresh installation

This contribution is based on public information from https://medium.com/@praveenkumarsingh/confluent-kafka-on-windows-how-to-fix-classpath-is-empty-cf7c31d9c787
I license my version of the work to the project under the project's open source license.

Bump!


No way to inspect content of request with FormData payload

Steps to reproduce
Tell us about your environment:

Puppeteer version: 1.5.0
Platform / OS version: macOSX Mojave
URLs (if applicable):
Node.js version: v8.15.0

What steps will reproduce the problem?
I have a process in React that looks something like this:
handleButtonClick() {
  const payload = new FormData();
  payload.append('foo', someFileBlobContent);
  payload.append('notes', 'Some notes');
  axios.post('/my-api/', payload);
}

When a button is clicked, some data is compiled as FormData, then sent as the payload in a POST request to an API.
In my Jest/Puppeteer tests, I'm trying to confirm that the request contains the data that it should:
page.click('.my-button');

await page.waitForRequest(request => {
  if (request.url().match(/my-api/) && request.method() === 'POST') {
    expect(request.postData()).toBeDefined();
    expect(JSON.parse(request.postData()).notes).toEqual('Some notes');
    return true;
  }
});

In this scenario request.postData() is undefined.
When running the process in Chrome, I can see the FormData displayed in the network requests via Chrome devtools, so I know the data is being sent, but I'd like to assert it.
What is the expected result?
For postData() or some other method to provide the request's form data that is visible in the dev tools.
What happens instead?
postData() returns undefined and no other methods are available that would provide this information.

Bump.

I have the same problem and the use case does not seem to so far-fetched. Not, that I'd be keen on parsing multi-part-form-data myself; but as an alternative could we get access to the raw req.body?


GhulCompiler property default not set for GenerateAssembliesJson target

If the GhulCompiler property is not set it should default to ghul-compiler. However, this is only being done for the CoreCompile target and not the GenerateAssembliesJson target. (Ideally property default setting should be moved into its own target and then referenced from each with DependsOnTargets or BeforeTargets

Actually looks like GhulCompiler default is not set properly at all, due to an incorrect condition in the CoreCompile target


suffix option

Sometimes need to hide include constructions from html by comments.
Can you add suffix option like in grunt-include-replace?

consider to use meta-templater as a dep.

Good. You may open issue for some corrections or ideas.

2a67d07463d82ca95389e6edfb4bd82a1e65ee93


Add tests

Fixes #26. Inspired by the bedevere testing approach.

This is far from 100% test coverage, but its a lot better than nothing and will make adding tests in the future very easy. The tests are of limited utility since we cannot actually interact with github. We're only testing how we think github should act. It should catch some easy issues such as #25 and make development easier though.


Oops, remix.init failed - no such file or directory, open '/cypress/support/delete-user.js'

Have you experienced this bug with the latest version of the template?
Yes
Steps to Reproduce

run npx create-remix@latest
name the app
create a pre-configured stack
select Indie
select TypeScript
select Yes to have it npm install.

Windows 10
Node 16.16.0
npm 8.15.1
Expected Behavior
remix.init shouldn't fail
Actual Behavior

I am also having issues, but for me the file that is missing is:
/cypress/support/commands.js

I just ran this again and got \cypress\support\commands.js insted of the delete-user.js

I've also seen the same behaviour described above, delete-user.js first, and commands.js on subsequent runs.
macos 12.5
node 16.16
npm 8.11

There is a typo in init script. I am preping a fix and a workaround

So to workaround a problem for now if you use Typescript:
Decline offer to install dependencies.
Edit init script like this: https://github.com/remix-run/indie-stack/compare/main...Guria:indie-stack:patch-1
Run:
npm i
npx remix init

This will be fixed by #144


Add compile and linking security flags that should not affect runtime…

… performance

This change is

The perf results are 20% slower, this is an unacceptable drop in IOPS:

24/PR-29
4243066
3447761
861947
4309707
0.13
0.13
0.32
0.32
0.53
0.54
1.15
1.15
15.76 GiB
124.92 GiB
12.6

121/PR-48
3748101
2917313
729335
3646648
0.16
0.17
0.36
0.37
0.58
0.59
1.36
1.37
15.68 GiB
125.01 GiB
12.5

I will rerun the tests to make sure this is not an issue with our CI.


Encryption

Add an encrypted transport such as TLS 1.3.

Better than adding a TLS transport is to implement transport agnostic protocol encryption. That will run on all platforms. If you are willing to add an extra handshake, I can happily help with implementing the crypto side of things with a proper ECDHE key exchange.

Encrypting every single message would be an overkill, adding a way to encrypt just some messages would be the best option.

Encrypting every single message would be an overkill, adding a way to encrypt just some messages would be the best option.

Depends, if you go with a stream cipher like ChaCha20 and Poly1305 for authentication it's actually not overkill at all. If you want to go down the blockcipher route with AES and SHA for the HMAC, then it will probably be quite overkill. A per message encryption & authentication is prefered imho.
That's why I don't suggest using a TLS transport.
Here is an example in how it is done in cough:
InvokeRpc(RpcMethod, SecurityFlags.Encrypt);
InvokeRpc(RpcMethod, SecurityFlags.Encrypt | SecurityFlags.Authenticate);
InvokeRpc(RpcMethod, SecurityFlags.Authenticate);

What's speaking against using (D)TLS and just encrypting everything? Surely the overhead is neglectable

What's speaking against using (D)TLS and just encrypting everything? Surely the overhead is neglectable
(I'm not an expert on this, so if this is wrong please do enlighten me)

What's speaking against it is that there is no benefit to being TLS compliant.
TLS is built into .NET but it's not well ported to all platforms, and since we are in a closed protocol there is 0 benefit to being TLS compliant. You are just increasing development time by many times and are increasing the handshake process.
What I did In my personal projects is that I wrote a ECDHE implementation in C#, used BouncyCastle's BigInt (you can use the .NET one tho), and then .NET's AES & HMAC.

But .Net already has ECDHE, doesn't it?

But .Net already has ECDHE, doesn't it?

Yes, but it's not ported to Mono. That's why we had to write our own.

A generic encryption layer would be cool and all.
But let's focus on MVP (Minimum Viable Product):  What is the bare minimun necessary and simplest way to get secure communication?
Simple TLS is better than nothing and relatively trivial to implement, that is where we should start.
Later we can think of a more generic encryption layer that can work with other transports.

Isn't it https://github.com/mono/mono/blob/master/mcs/class/referencesource/System.Core/System/Security/Cryptography/ECDiffieHellmanCng.cs ?

A generic encryption layer would be cool and all.
But let's focus on MVP (Minimum Viable Product): What is the bare minimun necessary and simplest way to get secure communication?
Simple TLS is better than nothing and relatively trivial to implement, that is where we should start.
Later we can think of a more generic encryption layer that can work with other transports.

Isn't it https://github.com/mono/mono/blob/master/mcs/class/referencesource/System.Core/System/Security/Cryptography/ECDiffieHellmanCng.cs ?

Try it in Unity's Mono version. As you can see by the copyright, it's microsofts implementation.

I want to wrap Telepathy in TLSStream and call it a start.
it is all about the Minimal Viable Product

For people looking to do this today -- you could just use TLS termination to stay compatible with mirror and then proceed to use a service in the middle that knows how to talk it.

termination to

If you are not session identified you are still vulnerable to MITM attacks, even if you use a secure side channel.

Excuse the ignorance, I'm new to Mirror and my main focus is not cryptography and security, so if you can break it down that's be great.
Assuming a secure origin proxy in front of an application server running Mirror that terminates to the the application server / game server, what is the hypothetical attack that enables a MITM?

Excuse the ignorance, I'm new to Mirror and my main focus is not cryptography and security, so if you can break it down that's be great.
Assuming a secure origin proxy in front of an application server running Mirror that terminates to the the application server / game server, what is the hypothetical attack that enables a MITM?

Alice is the server, Bob is the connecting client. Authy is like a secure web server. Mallory is between Alice and Bob.
Bob connects to Alice, Mallory allows this. Bob then sends Authy a message saying "tell Alice that the game connection x.y.z is me!". Now you have done secure authentication. Mallory never got to see that token, but he still has escalated privileges because he can still intercept the game server messages. This is unless you treat them as separate entitys completley and never combine the two, in which case you have just made your life hell and are running two game servers to avoid rather than fixing the problem.
The truth here is that implementing a TLSStream is fairly easy (given there is support or that the Mirror project is fine in having BouncyCastle as a dep), and even protocol stuff is not all too time-consuming, I remain my offer to support the implementation of it. Especially now that I see people actually launching games and actually sending unencrypted data. It's a responsibility of the library in my eyes.
But then again, the views of Mirror is for everything to be REALLY easy to use. One I don't always agree with but certainly, one that I can respect. The reality is that when implementing encryption you ARE making it more difficult for end users. They have to manage certificates for their dedicated servers or have secured messaging relays of hosts. But it can certainly be made easier with good documentation.
For my personal projects for example, I wrote a certificate generator that issues a CA cert and then self signs a certificate and prints instructions. This makes it dead simple to get started with encryption.
You can see that here (Tell me if that link is not allowed) It's all open source.

Oh, and btw, I started working on a transport adapter with encryption and it works fine. I just used the ECDHE implementation from my personal projects, BigInt from Bouncy and it works. (Note that I only spent like 2 hours writing it so it's dirty af), but it shows that this isn't a rocket science project. It can be done in very little time with a so-called "MVP". If you want integration to the lib tho, and not just have every message sent you might need more work. Right now I just used a hack where I used channel based encryption & authentication.
So you basically make this crypto transport your main, then you can plop another transport into it (for example multiplexer), and then add your final transports there. Like a chain. Not pretty but works.

@TwoTenPvP that sounds good.   And yes,  the chained transport is exactly how I envisioned this.
Any chance you can send a Pull request for that?

@TwoTenPvP that sounds good. And yes, the chained transport is exactly how I envisioned this.
Any chance you can send a Pull request for that?
Making it optional (so you can pick if you want a message encrypted or not) is trivial:
have 2 channels, one encrypted one non encrypted. the non encrypted channel would just be a passthrough to the underlying channel.

If you want it in the main repo, maybe. I will still have to clean it up. I am building it to conform to the MLAPI's validation system, which means that Mirror will be able to use MLAPI's tools to generate developer certificates and such super easily. I might be able to get it all completed during this weekend. I have a ton of new tooling for this purpose, thus it would be of great benefit to Mirror users to be able to use my cert generators and such to make certificate management a breeze. Everything is open sourced.
It's really up to you guys if you are fine with Bouncy's BigInt implementation being in your main repo and also our ECDHE implementation. If not I can do it as a standalone transport that users can download as a DLL.
As for making it optional, it sure is. But it's super limited rn due to the fact that it's a big hack. For example, we need to send authentication messages on encrypted channels. But I wouldn't say it's "trivial" to be optional. Much more a nice to have. Especially if you go with a fast stream cipher like ChaCha you have nothing to lose really.

Let's start with a separate transport,   if there is enough demand for it,  we can always merge it in master.
In the same theme, I will make my async based TcpTransport an addon and add support for TLS.

IMHO a transparent ECDHE handshake with each client would be nice, then you would only use it if you need it.
I ended up using RSA/AES because it doubles as a server signature... and because there is no DiffieHellmann implementation "out of the box" on unity, while there is for RSA.

That is just insecure.. There is a reason people use DiffieHellman. And my implementation is open source, no reason not to use it.

@TwoTenPvP  if you wish to write a PR, I would definitely take a look.
In my mind,  the reasonable way to do it would be to write an EncryptedTransport,  which takes another transport and whatever config you need.   It would encrypt the messages and pass it to the underlying transport.

Hello, I am currently looking at the possibility to use a secure connection from mobile app (android and ios) and windows clients (exe and UWP), using IL2cpp build. Is the Websocket Secure transport a valid option? Or is it something that should be used for webgl builds only? Thanks

closing because it's been almost two years.
if anyone wants to make an encryped transport then please open a PR :)

Implementing TLS is not so simple because of the self-signed certificate requirement. .NET has not contained the functionality to generate self-signed certificates until quite recently, and that functionality is not available in Unity Mono. This adds an additional dependency on something like Mono.Security just to generate the encryption certs. I have not had much success in using certs generated by Mono.Security in securing telepathy. I just get cryptic error messages about failed handshakes without any further details. I am considering implementing my own Diffie-Hellman key exchange just to be done with it.

@TwoTenPvP do you have a link to your ECDHE implementation?

I honestly don't see why you'd want a fully encrypted transport. If you are doing heavy network I/O, then you'll already probably be stressing out Unity, and then adding the encryption process on top of that stress is likely to cause even more lag/stutters.
It's probably better to encrypt the data before you send it over the wire, rather than letting the transport try to encrypt/decrypt the whole packet. In reality, the chances of someone spying on your networked game and sniffing for secrets in the data is low (but not zero). Even then, you shouldn't be putting sensitive stuff in your game anyway, if you're transmitting passwords or whatnot, you should be using some sort of hashing method - not plain text strings.
And if you're looking for a solid crypto implementation, I'd probably recommend using BouncyCastle's C# Crypto library. That is tried and true, used by many systems including Android itself. So go check that out.

@SoftwareGuy sorry you are mistaken about the requirement for encryption. Sending sensitive information is kind of the whole point of the software that I'm working on. Unity is used for more than video games. Encrypting at a higher layer on the networking stack makes no sense either since then I would have to implement encryption everywhere instead of one place, including modifying the Dissonance voice comms library.
I will check out the BouncyCastle C# crypto library, thanks for the tip. I am also planning on contributing back to Mirror once I get an implementation working.

@TwoTenPvP do you have a link to your ECDHE implementation?

EC https://github.com/MidLevel/MLAPI.Cryptography/blob/master/MLAPI.Cryptography/EllipticCurves/EllipticCurve.cs
ECDH-E https://github.com/MidLevel/MLAPI.Cryptography/blob/master/MLAPI.Cryptography/KeyExchanges/ECDiffieHellman.cs
ECDH-E with certificate https://github.com/MidLevel/MLAPI.Cryptography/blob/master/MLAPI.Cryptography/KeyExchanges/ECDiffieHellmanRSA.cs

Implementing TLS is not so simple because of the self-signed certificate requirement. .NET has not contained the functionality to generate self-signed certificates until quite recently, and that functionality is not available in Unity Mono. This adds an additional dependency on something like Mono.Security just to generate the encryption certs. I have not had much success in using certs generated by Mono.Security in securing telepathy. I just get cryptic error messages about failed handshakes without any further details. I am considering implementing my own Diffie-Hellman key exchange just to be done with it.

Also here is how I created certs: https://github.com/MidLevel/DevelopmentCertificateGenerator

Encryption with TLS and certificates (both signed and self-signed via BouncyCastle) are now implemented in https://github.com/vis2k/Telepathy/pull/96
After this pull request is accepted there will have to be some additional code changes in the Mirror repository to expose the encryption configuration options in the inspector.

This is being worked on in HushHush.
HushHush will be a middleware transport,  meaning it works on top of your existing transport and adds an encryption layer.
HushHush uses industry standard DTLS to encrypt messages before passing it down to the underlying transport.

Closing as Monke Transport was added months ago.


decode string of disk list fixed

fixed error of decode string in disk_list function of osd.
 TypeError: startswith first arg must be bytes or a tuple of bytes, not str
this patch solved this problem which happened in python3.(compatible with python2.7)

Can one of the admins verify this patch?

ok to test

jenkins, retest this please

jenkins, retest this please


Comments should not resort based on Karma while you have them open

I think we fixed this awhile ago.


init: Chromium headless-shell at stable (110.0.5481.77)

Description of changes
Chrome's headless-shell is a special stripped-down version of the browser designed to be used in headless environments like servers, for purposes like testing, profiling, and taking screenshots. It's nice to use because the main chromium derivation is quite bulky. It can be used in place of normal Chrome with browser automation tools like Puppeteer or chromedp.
The bulk of the work is getting the gnFlags correct in headless-shell.nix. For this I took a lot of inspiration from the docker-headless-shell project. The PR also has some minor refactoring in order to

reuse the meta attrset by moving it to meta.nix
avoid passing certain flags like use_system_libffi which the headless_shell build target doesn't recognize.

Here's the closure size difference:
> nix path-info -Sh .#chromiumHeadlessShell
/nix/store/aw777181vziiild0f84cv3pd0z718d60-chromium-headless-shell-unwrapped-110.0.5481.77      340.1M

> nix path-info -Sh .#chromium
/nix/store/389w77yx3q31ai2y009y99bjrr7icn4k-chromium-110.0.5481.77         1.2G

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] 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

[X] 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
[X] Tested basic functionality of all binary files (usually in ./result/bin/) (NB I tested with a version cherry-picked onto release-22.11)
23.05 Release Notes (or backporting 22.11 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

[X] Fits CONTRIBUTING.md.

I'm not keen on maintaining another Chromium package so chromiumHeadlessShell would need a dedicated maintainer (probably you). The maintainer would have to test major version bumps in advance (so that we don't delay security updates) and fix potential issues.

Sure, I'm happy to maintain it. I just added myself to the maintainers. In my experience of cherry-picking this onto different Nixpkgs versions, the headless_shell flags are a bit more stable than the general Chromium flags. I'd also be happy to add some smoke tests in the form of a Chrome Devtools Protocol test harness.

Nix isn't "efficient" in terms of storage space

Well, the great thing about this variant is that it's so slimmed down. The actual built headless-shell is only 259MB, and the rest of the dependencies in the closure are shared with normal Chromium. Surely that amount of extra space is more palatable than the other Chromium variants.

I'm not sure if there's enough demand for this package to justify adding it to Nixpkgs

IMO headless shell is an awesome variant and there would be more usage if it were easier to get one's hands on. All of the major Chrome automation and CI tools I've seen mention it. The problem is that it's hard to get a built version for your distro and even harder to build from scratch (which is why docker-headless-shell is so popular). I think Nixpkgs could take the lead here and help shrink everyone's browser CI images by hundreds of megabytes.
Pretty please? :)


References Section

We need a references section. Can build it out of:
Official CPS wiki References Section
Asking at project meetings about any extra references.
Once we have a draft of the referenes section, we should be able to close out this issue.

Agenda item has been added to ask.

Below is the references section from the official cps repo:
Reference Documentation
Facts, specifics, and other information
Reference documentation for CPS is maintained in the CPS specification. Since precision and review are important to maintaining a specification, those documents are maintained using a more structured pull request workflow. Please use PRs and issues on the CPS repo itself to contribute to the CPS specification.

So far we only have the cps specification. But I'd suggest in this section we should have basic documentation on any cps related tooling as well.


Added reading feature flag config from Azure AppConfig

Updated the ConfigurationFeatureSettingsProvider.GetFeatureConfiguration to try reading the Azure AppConfig key name, so this library can be used with Azure AppConfig features.
More info:
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/azure-app-configuration/manage-feature-flags.md
WARNING!
Azure AppConfig is still in preview!
I.e. this code works, but how feature flags are stored may change.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: Reyhn3 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Actually, this is not needed.
Feature flags are read when configuring the AppConfig like this:
var centralizedConfig = new ConfigurationBuilder()
	.AddAzureAppConfiguration(o =>
		{
			o.Connect(appConfigConnectionString);
			o.UseFeatureFlags();
		})
	.Build();