Draft 2 of Tasks TOC

This change is

@pwittrock let me know if there's a better person to give stuff like this to.

@steveperry-53 why did you merge this? The CI build failed?

@lavalamp This PR was actually just against the docsv2 staging branch (experimental), and shouldn't require review.

I see, ok, thanks. @foxish, do you know off the top of your head if there's
a way to configure the submit queue to ignore this branch? I can't recall.
On Mon, Aug 22, 2016 at 4:43 PM, Phillip Wittrock<EMAIL_ADDRESS>wrote:

@lavalamp https://github.com/lavalamp This PR was actually just against
the docsv2 staging branch (experimental), and shouldn't require review.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/kubernetes.github.io/pull/1074#issuecomment-241584772,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAngliXtuyJX5Xqe9HCN-8U7Y_jv-Tyjks5qijQVgaJpZM4JqaGt
.


Vcx mobile builds

This only addresses android builds for now.
@KitHat @Artemkaaas, could you guys take a look and review the logic in androidBuildArtifact?

Hey! I am not sure if this is the right place to do this, but it seemed like the same vein (and there are seriously no other ways to let you guys know that something is broken)
The Java wrapper is no longer working because the maven repository is down
https://repo.sovrin.org/repository/maven-public

@Artemkaaas can you look at this? Or point us at another repo?

@NanoBytesInc You're correct, this is not the best place to report this kind of issue. :) In the future, the quickest way to get in contact with us is to reach out to the Sovrin devops team at #devops on our chat.
Were we're already aware of the issue and it has since been fixed.


 The "actual" underlying fantasy console is CHIP-8, and a lot of resources can be found here: https://chip-8.github.io/ (Octo is pretty cool and should stay on the list).
There is also Zany80, which is based around the Z80 processor : https://pixelhero.dev/zany80/ ; it's rough and hasn't been updated in ages (though not more than other projects on the list), but I think it's interesting that it's based on actual hardware, both retro (used in many 80s computers) and current (still used in a lot of things).

Thanks for the info.
The maintainer's intention is also considered. Zany80 was on the list and has been removed by the author.
CHIP-8 is at the edge. It describes itself a programming language, sometimes a classic computer (which is very close to an FC I think). It is also often used to guide designing actual hardwares, I prefer to name it a VM (i.e. JVM), or independent architecture (i.e. RISK-V).

Too bad for Zany80.
Maybe you could list "retired" projects? A lot of the projects in the list haven't been updated in several years and, from the comments, don't work at all. I could help you with that.
CHIP-8 is described everywhere I see exactly like a fantasy console:
https://chip-8.github.io/links/

Created in 1977, CHIP-8 is the original fantasy console.

https://en.wikipedia.org/wiki/CHIP-8

CHIP-8 programs are run on a CHIP-8 virtual machine. It was made to allow video games to be more easily programmed for these computers.

I think it'd be interesting to at least mention its existence and legacy?

Maybe you could list "retired" projects?

Added a retired wiki page. Feel free to edit it.
Also feel free to mention if any of them on the main list is not working at all.

CHIP-8 is described everywhere I see exactly like a fantasy console

I see. But the official site only provides instructions to build virtual/actual CHIP-8 computers. I'd say ok to add it if there were official downloadable CHIP-8 interpreter. Some other softwares are implementing CHIP-8 compatibles, but they are just referring it as an open standard. Correct me if I'm missing anything here, but I'd be glad to mention its existence.

Thanks for the wiki page :)
I'll try to check the list and see if any stand out as "not working" (I can't try them all).

But the official site only provides instructions to build virtual/actual CHIP-8 computers

That's because it's not an official site, it's just a regular store selling stuff under the CHIP8 name ; there aren't even legal infos of the company. CHIP-8 is indeed an open standard ; the link I posted earlier ( https://chip-8.github.io/ ) is the best one I found for the documentation.
There's also VDP16, trying to simulate a 16bits console: https://github.com/Brunni132/vdp16-samples/tree/gh-pages

A few other ones that should probably go straight to "retired":

PQ93, last updated mid-2020: https://pennie.itch.io/pq93
Micro16, last updated sept 2020: https://bitblitter.itch.io/micro16

CHIP-8: added a link
PQ93, Bitmelo: added to the main list
Micro16: will learn more about it


CLI distribution for macOS as pkg installer

📚 Context
macOS users who don't use homebrew or macports should be able to install the CLI using a pkg installer.
✔ Solution
oclif framework already provides a way to produce artifacts for a pkg installer
https://oclif.io/docs/releasing#macos-installer
📈 Subtasks

[x] create infrastructure code for a S3 bucket to host cli distributions
[x] create cloudfront distribution for the S3 bucket, using the domain https://cli.sunodo.io
[ ] research how to sign the package
[ ] setup a CI job to do the release

🎯 Definition of Done

[ ] macOS users should be able to install and update the CLI using the installer

@tuler Can we use the same S3 bucket that we use for debian ?

To sign a macOS package (.pkg file), we need to use the productsign command-line tool provided by Apple. This tool is used to digitally sign installer packages to ensure their authenticity and integrity. Here's how we can sign a package:

Obtain an Apple Developer ID:
To sign a package, we need a valid Apple Developer ID certificate. We can obtain this by enrolling in the Apple Developer Program.

Generate a Developer ID Installer Certificate:
Once we have a Developer ID, we'll need to generate a Developer ID Installer certificate using the Keychain Access app on the macOS machine. This certificate is used to sign the package.

Sign the Package:
Open Terminal and use the productsign command to sign the package. Replace "Developer ID Installer: Your Developer ID" with the common name of your Developer ID Installer certificate.

productsign --sign "Developer ID Installer: our Developer ID" /path/to/input.pkg /path/to/signed.pkg

Verify the Signature:
We can verify the signature of the signed package using the spctl command:

spctl -a -vv /path/to/signed.pkg

Sunodo should enroll in the Apple Developer Program as an Organization.
https://developer.apple.com/programs/enroll/
But we don't have a D-U-N-S number for Sunodo yet.
So we need to postpone this task.


HSEARCH-4571 Follow-up to fix tests

Follows up on #3054 .
@marko-bekhta You may be interested in the first commit. I missed that during my review, otherwise I would have told you Hibernate Search has a built-in feature to make indexing synchronous :) We generally only use that in tests, because performance is bad, but it's very useful for tests.

It's funny 😃 yesterday I thought that I should probably point out the usage of await as it was causing the problem with ES tests, but then I thought that you probably saw it and were OK with it 🙈


Code editor breaks after some time

https://github.com/enso-org/enso/assets/3919101/ab6c4855-06a0-4305-90ca-c07e7eecfa8b
Logs from another run:
localhost-1701952176893.log

It seems fixed by AST changes, but still is a bit laggy. Also found another issues, report them soon.


bcpg in release 1.78 now requires bcutil dependency

bcpg-jdk18on in release 1.78 needs bcutil-jdk18on dependency because of CryptlibObjectIdentifier now living there. Previously bcutil was not needed. the bcpg-jdk18on-1.78.jar I pulled from Maven central does not state the new dependency in it's pom file, it only lists bcprov-jdk18on.

I'll fix the maven dependency as part of sorting out the OSGI issue. Note, if you're using Java 9, the module entry was also missing from the requires statement - the 1.78.1 release candidate on https://www.bouncycastle.org/betas has this fixed in it as well.

同问

please add tag 1.78

This is now fixed in 1.78.1 which is starting to appear on Maven Central and bouncycastle.org.
And yes, I'm still waiting on that CVE ID. Expecting it any moment now...

Confirmed, for my project's Maven build, in version 1.78.1 bcpg now automatically pulls in bcutil.
Thanks!


different font glyph display

In imgui, it seems only several font glyph types supported. Does this mean that, you can not display all kinds of utf8 characters at the same time?  But oftentimes, you may need to display Chinese, Thai, etc. at the same time.  Is this possible with Imgui?

I haven't tried it myself, but I think it should be possible to use FontGlyphRange::from_slice to generate a set of unicode glyph ranges, including for example Chinese and Thai at the same time. If you then have a font that has all these glyphs, I think it should work.
For example, something like this (not actually tested):
let range = FontGlyphRange::from_slice(&[
  0x0020, 0x00FF, // Basic Latin + Latin Supplement
  0x2010, 0x205E, // Punctuations
  0x0E00, 0x0E7F, // Thai
  0x3000, 0x30FF, // Punctuations, Hiragana, Katakana
  0x31F0, 0x31FF, // Katakana Phonetic Extensions
  0xFF00, 0xFFEF, // Half-width characters
  0x4e00, 0x9FAF, // CJK Ideograms
  0,
])

I know this is a 2 years old issue, but I can confirm this works in 0.5:
    let custom_ranges = FontGlyphRanges::from_slice(&[
        0x0020, 0x00FF, // Basic Latin + Latin Supplement
        0x2200, 0x22FF, // a range that contains some miscellaneous symbols
        0x2600, 0x26FF, // another range with miscellaneous symbols
        0]); // this 0 is required to close the ranges list

    imgui_context.fonts().add_font(&[FontSource::TtfData {
        data: include_bytes!("../some/nice/font.ttf"),
        size_pixels: my_font_size,
        config: Some(imgui::FontConfig {
            glyph_ranges: custom_ranges,
            size_pixels: my_font_size,
            ..Default::default()
        }),
    }]);

The font must contain the character (or emoji) in the provided custom ranges. You can verify that with a tool like fontforge (which also allows you to edit the ttf font in case you need it!).


Some error While test

Hello,
It's working fine except few exceptions.  Please go through the config.h and ESP32 code of my project.
config.h.txt
Universal_Strength_24.txt
ESP32 Pin Configuration
DT  = 36
SCK = 33
Here is some line code of your interest to check
LINE 1139 While running sub
Initializing_Scale()
Line 2277 When Click on Start Test
Now Observation are

When we start new test then it's showing last result. Where as i reset the variable =0.
Can i increase sampling speed. currently it's #define SAMPLES 32. I think reducing sample may fix the problem. i will check.
For same weight its showing fluctuated reading. but while doing calibration it's shows perfect every time.
In my project there are 4 Modes. and when we select other mode then Direct this this happens.

Project Use ILI9488 TFT display.
Thanks and regards
Sudarshan Patil

I have done

initialize again before test begin.
Reduced  setSamplesaInUse(4) from 32.

This fix the issues I am having
Thanks
Sudarshan Patil

Thanks for the update.


Refactor(cli): Refactor CLI Command and Code Structure

Decided to not to go in this direction with the refactor.


fix: Job::runs_on

fixes: #28

Thanks for the fix! Saw your post and interesting in the project - will get some feedback as well in the coming days.


Mark publishable instances in Photoshop

Is your feature request related to a problem? Please describe.
There is currently no way of knowing which layers or group in photoshop are publishable, once they were tagged with the creator. There's also no way of un-tagging something to make it no longer publishable.
Describe the solution you'd like
Once the user tags a layer for publishing, we need to somehow visually let the user know which layers are tagged. Hard to tell what options we have. Using colours is not great, because studios tend to already use them for various purposes. We could possibly append something to layer names, but that's also not great.
Another option, which would be ideal in the long term and also cross-host is extending creator to actually show any instances in the scene and let the user work with them to a certain extend.

Another option, which would be ideal in the long term and also cross-host is extending creator to actually show any instances in the scene and let the user work with them to a certain extend.

A separate UI was my initial thoughts on this. Its also a problem in Harmony I guess.

yeah I agree that a good UI would probably be the best overal


Decision Tree Regressor #121

Decision Tree Regressor #121
Adding practical implementation of Decision Tree Regressor Algorithm using a project as  Campus Placement Analysis & Prediction as per the project structure mentioned.

[x] DevIncept Participant
[x] Contributor

Closes: #121
Describe the changes you've made

Added Decision Tree Regressor folder in Algorithms folder of  Machine Learning folder which contains-:

README.md file with proper documentation and
decision_tree_regressor.ipynb file with practical implementation.
Images folder with all code images.

Type of change
What sort of change have you made:

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Code style update (formatting, local variables)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Performance done by accuracy check and error check.
Checklist:

[x] My code follows the guidelines of this project.
[x] I have performed a self-review of my own code.
[x] I have commented my code, particularly whereever it was hard to understand.
[ ] I have made corresponding changes to the documentation.
[x] My changes generate no new warnings.
[ ] I have added test cases that prove my fix is effective or that my feature works.

This is an exclusive work. can't get anything better than this. Great going ayushi. Super proud of you.✨👏👌 @ayushi424

Thankyou so much @prathimacode-hub


Throttling on Exceptions (RoutePolicy)

Our project recently needed a circuit breaker that stop consuming messages from the from endpoint. I noticed that the Camel circuit breakers consumed from the endpoint even in the open mode and controlled access to the to endpoints on the route.
Based on this Stack Overflow answer, I created a circuit breaker that will stop consuming from the starting endpoint based on exceptions being thrown. It is using a RoutePolicy and imitates the existing ThrottlingInflightRoutePolicy as well as the CircuitBreakingLoadBalancer.
Not sure if there is any interest in adding it to Camel.
Thanks

Can you add ASF license headers to the files.
And if possible fix any checkstyle errors which you can check with
mvn compile -P sourcecheck

will do

Thanks @CodeSmell.
Can you open a JIRA ticket about this new functionality, so we have a ticket about this.
Also I wonder if you could work on a new PR that adds JMX to this route policy.
See how we do it for the existing
org.apache.camel.api.management.mbean.ManagedThrottlingInflightRoutePolicyMBean
And then create a similar for this policy.

No problem.
I created this issue for this PR
https://issues.apache.org/jira/browse/CAMEL-10718
I also created this issue for the JMX part
https://issues.apache.org/jira/browse/CAMEL-10719
I could not assign it but I'll take a crack at this later


Support for custom names from schematics or parts

Add a new field in the custom json field that allows you to specify custom names that should be appended either to parts, or completed tools.
This is needed to be able to hide material names from unique parts

This has been fixed


[nodefw/drainer] add a drain flag and file

Description
Add a drain file to control the firewall if needed.
Test Plan
RUST_LOG=info cargo bpf run -- --drain-file /tmp/drain
then rm or touch the file at /tmp/drain.  the firewall will unload or be prevented from loading if present.
https://github.com/MystenLabs/sui/assets/123987499/0a21b9f0-b9ca-47c4-a5b2-6217c350a75d

Release notes
Check each box that your changes affect. If none of the boxes relate to your changes, release notes aren't required.
For each box you select, include information after the relevant heading that describes the impact of your changes that a user might notice and any actions they must take to implement updates.

[ ] Protocol:
[ ] Nodes (Validators and Full nodes):
[ ] Indexer:
[ ] JSON-RPC:
[ ] GraphQL:
[ ] CLI:
[ ] Rust SDK:

i'm withdrawing this pr after speaking with will.  there is a preference from mark to write on or off to the file vs simply checking for existence.


How to set checkHostsUpdate

When using energized -C the file does not open and with energized -C checkHostsUpdate=true it seems that is not added to the file since energized -C displays nothing.

Just installed and having same problem


share functionality added

Fixes #72
GIF:

Please make sure these boxes are checked before submitting your pull request - thanks!

[x] Run the unit tests with ./gradlew check to make sure you didn't break anything

[x] If you have multiple commits please combine them into one commit by squashing them.

@oorjitchowdhary thanks for showing interest in Mifos :)

@SaumyaSingh1 i made this PR for a task which now seems to be removed now, can you look into it?

Hey @rachittt , Here is the task link : https://codein.withgoogle.com/dashboard/tasks/5886206831755264/

@SaumyaSingh1 i made this PR for a task which now seems to be removed now, can you look into it?

The link you provided is opening for me . Recheck it : )

@rachittt  claim the task on GCI dashboard and submit your work there(provide the link of this P.R  ) .

The claim button does not work for this task(I do not have any pending task).
Even if you search it on GCI website, it shows "no task found."
Can you help me with it ? @SaumyaSingh1

The claim button does not work for this task(I do not have any pending task).
Even if you search it on GCI website, it shows "no task found."
Can you help me with it ? @SaumyaSingh1

@rachittt  yes you will be able to claim it . Give me some time : )

@SaumyaSingh1 hey, i have claimed and submitted this task now. Sorry for all the disruption caused earlier :)


Add a drop file feature to load zcad files and gltf files.

Make it possible to simply drag n drop files into the viewer.

If no cad file is already loaded, then show the drop here overlay.
If a user drops a zcad file, or a gltf file, then load that file.
IF a user drags and drops another file, then ideally it could load the second file.

See here for this previous effort that was never finished.
https://github.com/ZeaInc/gltf-loader/pull/2/commits/b013f95105ef1916d36754fe637069aa61b6a118

It looks like dropping glb files isn't quite working.
Here is the original implementation that does work.
https://github.com/ZeaInc/gltf-loader/commit/b013f95105ef1916d36754fe637069aa61b6a118#diff-8db0ea56b4cdff062269c7ea165c52fbec6e2693c52bf7118f54a7069e2175e1R174-R188
https://github.khronos.org/glTF-Sample-Viewer-Release/assets/models/2.0/GearboxAssy/glTF/GearboxAssy.gltf


Remote Control: Missing explicit UA and call selection for commands

While trying to build a simple multi-UA WebGUI with a single baresip instance I ran into the problem that the MQTT API is missing an explicit UA selection for each command sent from my UI to baresip.
All commands are directed to the "current" UA but it nearly impossible to preselect a specific UA via MQTT.
baresips current command implementation is like that:
/baresip/command {"command":"dial","params":"music","token":"123"}
You can only toggle between UAs by calling uanext or uafind but you are even unable to get a valid JSON-formated response from reginfo command to get a feedback which of them are available and which is currently selected.
Even if you manage to get that in case of multiple MQTT clients anybody else could change the "active" UA in the meantime by running uanext or  uafind again (kind of race condition).
In the other direction all events published by baresip already include the accountaor value which can be used to distinguish between the UAs. Example:
/baresip/event {"type":"CALL_ESTABLISHED","class":"call","accountaor":"sip:123456789@<IP_ADDRESS>","direction":"incoming","peeruri":"sip:+4912345678901<EMAIL_ADDRESS>So I would suggest to add an optional "accountaor" attribute to all the commands like this
/baresip/command {"command":"dial","params":"sip:+4912345678901","accountaor":"sip:123456789@<IP_ADDRESS>","token":"123"}
and to add a new subtopic (e.g. /baresip/accounts) or event which publishes and updates the list of UAs with a JSON-formated content whenever there is a modification of the internal state (idea and data from /reginfo)
{
 "selected_index":1,
 "accountaors": [
   {"index":1,"accountaor":"sip:12345678901@<IP_ADDRESS>","state":"OK"},
   {"index":2,"accountaor":"sip:12345678902@<IP_ADDRESS>","state":"OK"},
   {"index":3,"accountaor":"sip:12345678903@<IP_ADDRESS>","state":"OK"},
 ]
}

yes I think it is a good idea to explicitly specify the UA account.
we currently have the concept of a "current" UA, but perhaps it is time to get rid of it ?

Alfred E. Heggestad writes:

yes I think it is a good idea to explicitly specify the UA account.
we currently have the concept of a "current" UA, but perhaps it is
time to get rid of it ?

My baresip app is making one uag_current_set() call, but I don't
anymore remember what its purpose is.  Perhaps none.

getting rid of "current" UA is a big task but not impossible :)
the current UA is mostly needed when making an outgoing call.
some ideas:

when the number of UAs is 1, this UA will be used for all operations

when using multiple UAs we can add a default flag to indicate the default UA.

when dialing to a domain, the target domain can be matched against the domain
of all UAs. if a match is found that UA will be used.

It is not only the "current" UA but also the "current" call (or line-id) of the UA :-)
I think there is no need to remove the "current"-concept in general.
But some optional specific command parameters could help a lot.
So maybe adding an optional aor parameter to the dial command and a id parameter to the hangup command for example would help a lot. If they are specified they should override the "current" selection.

what you can try is to run the uafind command in front of e.g. dial
  /uafind ..                   Find User-Agent <aor>
  /dial ..            d ..     Dial

/uafind<EMAIL_ADDRESS>/dial sip:+4912345678901

if you run the application yourself, you should be in control of which
user interfaces are enabled. for example you can disable stdio.so.
the incoming commands from MQTT should be executed in sequence,
as they are processed in the main thread. there should not be
any race conditions.
we could add explicit UA to some commands but we have to find out
on which level. The command system is split into 2 logical blocks:

Raw commands
Commands via a protocol (e.g. MQTT)

if we add aor= and callid= to 1.) then it can be re-used also by e.g. stdio.so
if we add it to 2.) then it cannot be reused by stdio.so

what you can try is to run the uafind command in front of e.g. dial
/uafind<EMAIL_ADDRESS>/dial sip:+4912345678901

This is exactly what I do at the moment but even this MAY be disturbed by a background job which rolls through all UAs (32 in my testcase here with MADI audiointerface) and requests the list of active calls the same way.

we could add explicit UA to some commands but we have to find out
on which level. The command system is split into 2 logical blocks:
1. Raw commands

2. Commands via a protocol (e.g. MQTT)

if we add aor= and callid= to 1.) then it can be re-used also by e.g. stdio.so
if we add it to 2.) then it cannot be reused by stdio.so

Anyway it is important that the published callids are unique across all UAs and that they match in lists (pull) and events (push). Currently there is a concept of line numbers per UA in lists and unique(?) ids in events and log.
I think the "current" implementation is ok for stdio.so as simple human interface but the remote control interface might have other requirements as it may be the base for advanced UIs or automation in any way.

here is a list of UI/Ctrl modules:

stdio
cons
http
mqtt
ctrl_tcp

each of these should/could have its own struct ui
we could find a way to transport the ua/call context from
ui module via ui/command to the actual command handler.

here is a WIP patch:
diff --git a/modules/debug_cmd/debug_cmd.c b/modules/debug_cmd/debug_cmd.c
index 136e0cb..3a993a2 100644
--- a/modules/debug_cmd/debug_cmd.c
+++ b/modules/debug_cmd/debug_cmd.c
@@ -70,10 +70,11 @@ static int cmd_config_print(struct re_printf *pf, void *unused)
 }

-static int cmd_ua_debug(struct re_printf *pf, void *unused)
+static int cmd_ua_debug(struct re_printf *pf, void *arg)
 {
-	const struct ua *ua = uag_current();
-	(void)unused;
+	struct cmd_arg *carg = arg;
+	const char *aor = carg->data;
+	const struct ua *ua = uag_find_aor(aor);

 	if (ua)
 		return ua_debug(pf, ua);
diff --git a/modules/mqtt/subscribe.c b/modules/mqtt/subscribe.c
index 340eb63..5d12297 100644
--- a/modules/mqtt/subscribe.c
+++ b/modules/mqtt/subscribe.c
@@ -24,6 +24,7 @@ static void handle_command(struct mqtt *mqtt, const struct pl *msg)
 	struct re_printf pf = {print_handler, resp};
 	struct odict *od = NULL;
 	const struct odict_entry *oe_cmd, *oe_prm, *oe_tok;
+	const char *aor;
 	char buf[256], resp_topic[256];
 	int err;

@@ -42,6 +43,8 @@ static void handle_command(struct mqtt *mqtt, const struct pl *msg)
 		goto out;
 	}

+	aor = odict_string(od, "accountaor");
+
 	debug("mqtt: handle_command:  cmd='%s', token='%s'\n",
 	      oe_cmd ? oe_cmd->u.str : "",
 	      oe_tok ? oe_tok->u.str : "");
@@ -55,7 +58,7 @@ static void handle_command(struct mqtt *mqtt, const struct pl *msg)
 	err = cmd_process_long(baresip_commands(),
 			       buf,
 			       str_len(buf),
-			       &pf, NULL);
+			       &pf, (void *)aor);
 	if (err) {
 		warning("mqtt: error processing command (%m)\n", err);
 	}

the JSON element accountaor is extracted from the mqtt message
the accountaor string is passed to the command system via "data" (opaque)
the example command "cmd_ua_debug" use the aor to find the correct UA.

something similar can also be done for callid.

I also have a different patch that adds a new optional parameter to
selected commands, to use that specific useragent.
the syntax is something like this:
/dial<EMAIL_ADDRESS>1234
with this option we have 2 different options that we can try out:

add an optional aor parameter to all commands in MQTT.
this will not affect the other UI/CTRL modules

add an optional aor parameter to selected commands that is relevant for UA.
this will affect all UI/CTRL modules, incl. stdio and mqtt.

I would suggest to add the optional accountaor (and id) parameters to all "software" remote control paths with priority. I think this is only JSON MQTT and JSON ctrl_tcp (netstring) for the moment (more could be added as module in future). But if it is easier to add it to all paths/modules then add it to all paths.
As the uafind works fine as a workaround for an accountaor parameter the more urgent thing is to add the id to all call-related commands, especially hangup as there is no workaround.

is there a consensus for implementing option 1.) ?
NOTE: both ua and call will be added. we are now trying to establish how in
the baresip framework it will be solved, possibly affecting a lot of code.
the chosen solution will also be used for the long term future, we will not
revisit this problem again in 6 months.

Maybe we should ask @jmillan and @oej for this ?

is there a consensus for implementing option 1.) ?

As long as this includes both MQTT and ctrl_tcp, yes.

I’m not sure about adding aor in command.
/uafind is cleaner and faster when you have to dial multiple extensions.
Like this:
/uafind<EMAIL_ADDRESS>/dial 100
/dial 101
/dial 102
We don’t need to call uag_find_aor each time.
Maybe we just need to implement /callfind ID ?

@GGGO I agree with you.
Just to clarify, the aor parameter is optional and if missing the current UA will be used.
here is my patch for reference:
diff --git a/modules/debug_cmd/debug_cmd.c b/modules/debug_cmd/debug_cmd.c
index 136e0cb..3f72cdd 100644
--- a/modules/debug_cmd/debug_cmd.c
+++ b/modules/debug_cmd/debug_cmd.c
@@ -70,10 +70,51 @@ static int cmd_config_print(struct re_printf *pf, void *unused)
 }

-static int cmd_ua_debug(struct re_printf *pf, void *unused)
+static int split_params(struct ua **uap, struct cmd_arg *carg)
 {
-	const struct ua *ua = uag_current();
-	(void)unused;
+	static char buf[256];      /* NOTE */
+	struct pl pl_ua, pl_prm;
+	struct ua *ua;
+	char aor[256];
+	int err;
+
+	re_printf("input prm: '%s'\n", carg->prm);
+
+	if (0 == re_regex(carg->prm, str_len(carg->prm),
+			  "ua=[^ ]+[ \t]*[^]+", &pl_ua, NULL, &pl_prm)) {
+
+		re_printf("ua: '%r'\n", &pl_ua);
+
+		err  = pl_strcpy(&pl_ua, aor, sizeof(aor));
+		err |= pl_strcpy(&pl_prm, buf, sizeof(buf));
+		if (err)
+			return err;
+
+		ua = uag_find_aor(aor);
+		if (!ua) {
+			warning("ua not found (%s)\n", aor);
+			return ENOENT;
+		}
+
+		*uap = ua;
+		carg->prm = buf;
+	}
+
+	return 0;
+}
+
+
+static int cmd_ua_debug(struct re_printf *pf, void *arg)
+{
+	struct cmd_arg *carg = arg;
+	struct ua *ua = uag_current();
+	int err;
+
+	err = split_params(&ua, carg);
+	if (err)
+		return err;
+
+	info("filtered param: '%s'\n", carg->prm);

 	if (ua)
 		return ua_debug(pf, ua);

If I understand correctly, split_params will be called each time we call /dial 100, right ?
I don't know about the re_regex performance but I would prefer to not have split_params implemented in commands.
I think this kind of logic should stay in ui/ctrl module.
ref: https://github.com/alfredh/baresip/issues/51#issuecomment-152301084

@premultiply can you test the patch please, I don't have mqtt.

@alfredh This works like a charm for me.
Tried it with dial and hangup commands from our web GUI in development.
What may be a bit misleading is that the call-id is named only id in outgoing event and needs to be named callid in incoming command.

pushed to master.
thanks for good input and testing.


Missing device configuration:  DONEXON varmo TZ eco

Checklist

[X] It is not in the configuration DB

[X] It was not merged recently or has a pending PR

Which device is missing?
DONEXON varmo TZ eco
Manufacturer ID
0x0148.0
Product Type
0x0004
Product ID
0x0148.0x0003.0x0004
Firmware Version
0.16
Is the device listed on the Z-Wave Alliance website?
https://products.z-wavealliance.org/products/3328
Do you have a manual?

need help

Hi,
i have Change the File:
https://github.com/zwave-js/node-zwave-js/commit/229fee4b35efead21bc698b09501a866a9551fe0
But I don't know what to do next

fixed in https://github.com/zwave-js/node-zwave-js/pull/5274


invalid_request

Hi
When I request access token by access into oauth/access_token, there is an error message as following: "The request is missing a required parameter, includes an invalid parameter value, includes a parameter more than once, or is otherwise malformed. Check the "grant_type" parameter.". Here is my header:
Content-Type: x-www-form-urlencoded
grant_type: facebook
I also try to pass grant_type through url parameter, but it still display the same error.

it should be passed in the query string indeed. Facebook is a grant type you declared i assume. Check if you registered it correctly

here is my application information:

url: http://sportpill.app:8000/api/oAuth/access_token?grant_type=facebook

my registration:

'grant_types' => [
'facebook' => [
'class' => 'App\Library\oAuth\FacebookGrant',
'callback' => function($fb_access_token, $fb_id) {
        },
        'access_token_ttl' => 3600
    ]
],

NOTE: I use Laravel 5.0

When I change http method from POST to GET. It return another error as following: "The authorization grant type "facebook" is not supported by the authorization server."

Dont know why! Now everything is OK! thanks


procfs is for processes, not random things

Can we please switch to using debugfs for the kernel module filesystem interface?  It's simpler, cleaner, and that is explicitly what it is there for.
procfs is for processes, and no new things that are not processes should be added to it.
I'll be glad to write the patch if you all want :)

Aha, nice suggestion! Assuming at least one of @asteinha or @mmdriley are OK with the idea in the abstract, I'd be happy to review a PR implementing this, as at the very least it'd give me an opportunity to learn how to run/test that demo.

I will be glad to do so if the license is put back to GPLv2.


change example lib name to agree with the explanatory text

I don't believe this is correct. The "lib" prefix gets added automatically.

On linux, it justs looks in LD_LIBRARY_PATH for whatever you put in that string—with the added so extension.

Camelia runs on SUSE and I also tested on Bodhi Linux (fork of Ubuntu). The 'lib' prefix gets added automatically in both cases. What distro are you running that doesn't get the lib added?
<ZoffixWin> m: use NativeCall; sub foo is native('something') {}; foo
<camelia> rakudo-moar 868d8b: OUTPUT«Cannot locate native library 'libsomething.so': libsomething.so: cannot open shared object file: No such file or directory␤  in method setup at /home/camelia/rakudo-m-inst-1/share/perl6/sources/24DD121B5B4774C04A7084827BFAD92199756E03 (NativeCall) line 2…»

zoffix@zoffix-VirtualBox:~$ perl6 -e 'use NativeCall; sub foo is native("something") {}; foo'
Cannot locate native library 'libsomething.so': libsomething.so: cannot open shared object file: No such file or directory
  in method setup at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/sources/24DD121B5B4774C04A7084827BFAD92199756E03 (NativeCall) line 279
  in method CALL-ME at /home/zoffix/.rakudobrew/moar-nom/install/share/perl6/sources/24DD121B5B4774C04A7084827BFAD92199756E03 (NativeCall) line 290
  in block <unit> at -e line 1

zoffix@zoffix-VirtualBox:~$

My memory fails me, you're right @zoffixznet.

Alright. I reverted this commit and also added clarification that lib gets added automatically.


JIT compile fail when using functional.generalized_rspmm with CUDA on Linux

Hey,
Most likely this is an error with torch drug itself however when I try to run any of the examples from the readme, the code will crash with the following error:
spmm.cuda.o.d -DTORCH_EXTENSION_NAME=spmm -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -isystem /home/user/miniconda3/envs/path/lib/python3.8/site-packages/torch/include -isystem /home/user/miniconda3/envs/path/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -isystem /home/kkjj450/miniconda3/envs/path/lib/python3.8/site-packages/torch/include/TH -isystem /home/user/miniconda3/envs/path/lib/python3.8/site-packages/torch/include/THC -isystem /opt/scp/software/CUDA/11.1.0/include -isystem /home/kkjj450/miniconda3/envs/path/include/python3.8 -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 --compiler-options '-fPIC' -O3 -std=c++14 -c /home/user/miniconda3/envs/path/lib/python3.8/site-packages/torchdrug/layers/functional/extension/spmm.cu -o spmm.cuda.o
FAILED: spmm.cuda.o
/opt/scp/software/CUDA/11.1.0/bin/nvcc --generate-dependencies-with-compile --dependency-output spmm.cuda.o.d -DTORCH_EXTENSION_NAME=spmm -DTORCH_API_INCLUDE_EXTENSION_H -DPYBIND11_COMPILER_TYPE=\"_gcc\" -DPYBIND11_STDLIB=\"_libstdcpp\" -DPYBIND11_BUILD_ABI=\"_cxxabi1011\" -isystem /home/user/miniconda3/envs/path/lib/python3.8/site-packages/torch/include -isystem /home/user/miniconda3/envs/path/lib/python3.8/site-packages/torch/include/torch/csrc/api/include -isystem /home/user/miniconda3/envs/path/lib/python3.8/site-packages/torch/include/TH -isystem /home/user/miniconda3/envs/path/lib/python3.8/site-packages/torch/include/THC -isystem /opt/scp/software/CUDA/11.1.0/include -isystem /home/user/miniconda3/envs/path/include/python3.8 -D_GLIBCXX_USE_CXX11_ABI=0 -D__CUDA_NO_HALF_OPERATORS__ -D__CUDA_NO_HALF_CONVERSIONS__ -D__CUDA_NO_BFLOAT16_CONVERSIONS__ -D__CUDA_NO_HALF2_OPERATORS__ --expt-relaxed-constexpr -gencode=arch=compute_70,code=compute_70 -gencode=arch=compute_70,code=sm_70 --compiler-options '-fPIC' -O3 -std=c++14 -c /home/user/miniconda3/envs/path/lib/python3.8/site-packages/torchdrug/layers/functional/extension/spmm.cu -o spmm.cuda.o
/opt/software/CUDA/11.1.0/include/cuComplex.h: In function ‘float cuCabsf(cuFloatComplex)’:
/opt/software/CUDA/11.1.0/include/cuComplex.h:179:16: error: expected ‘)’ before numeric constant

This only occurs on a GPU linux machine, which is using CUDA 11.1 and GCC 10.3.

Many thanks!

Hi! This looks like a compilation error in CUDA head files and not in TorchDrug.
I just skim through cuComplex.h and I think the cause is that the type float2 (a.k.a. cuFloatComplex) is not recognized correctly by the compiler. I guess the reason is either your GPU hardware doesn't support complex numbers or we miss some compilation flags to turn on the feature.
As we don't need to compile spmm/rspmm for complex tensors, maybe you can try to turn off the compilation for complex tensors in PyTorch JIT? I guess it might be some C++ macro but not sure what it is exactly.

We use V100 too, so it sounds weird to me. The code is mainly developed and tested on V100 + PyTorch 1.8.1 + CUDA 10.2. We also know it is good on A100 + PyTorch 1.8.2 LTS + CUDA 11.1.
If you run this code with PyTorch 1.10 or newer, it will consume slightly more memory for the 0-th GPU, and the default batch size will cause OOM for a 32GB V100 on some datasets. Other than this, we don't see any problem for newer PyTorch versions.

Hey @KiddoZhu I managed to solve this and it seemed to be some weird mismatch between conda and the native CUDA libraries installed on the HPC system. I now have it running using the python provided on the HPC and everything is working now.
Thanks for your quick reply! I will now close the issue but I had a quick question about model check pointing -- are checkpoints only saved at the end of each epoch? If so, can this be changed to save after n update steps?

Hello, I met similar problems as you. It seems that ninja cannot compile spmm/rspmm.  I ran the code on A40 + pytorch 1.8.1/1.8.0 + CUDA 11.1. I don't know where the mismatch is.


⚠ Bofrost.at has degraded performance

In 5ec5f04, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1241 ms

Resolved: Bofrost.at performance has improved in 1861232 after 6 minutes.


odo push fails for storage provision on IBM Cloud openshift cluster

/kind failing-test
What versions of software are you using?
Operating System:
All supported
Output of odo version:
odo v2.2.3 (1579dd5be)
How did you run odo exactly?
odo create nodejs tbwdcd
cp odoexampledir/devfile-with-volume-components.yaml ./devfile.yaml
odo storage list
odo push  -v4

Actual behavior
odo push --context /tmp/035026500 -v4]
[odo] Validation
[odo]  •  Validating the devfile  ...
 ✓  Validating the devfile [172561ns]
[odo]
[odo] Updating services
[odo]  ✓  Services and Links are in sync with the cluster, no changes are required
[odo]
[odo] Creating Kubernetes resources for component tbwdcd
[odo]  ✓  Added storage secondvol to tbwdcd
[odo]  ✓  Added storage firstvol to tbwdcd
[odo]  •  Waiting for component to start  ...
...
[odo] I0726 16:14:08.566417  244796 deployments.go:188] Deployment Condition: {"type":"Available","status":"False","lastUpdateTime":"2021-07-26T10:44:08Z","lastTransitionTime":"2021-07-26T10:44:08Z","reason":"MinimumReplicasUnavailable","message":"Deployment does not have minimum availability."}
[odo] I0726 16:14:08.566471  244796 deployments.go:188] Deployment Condition: {"type":"Progressing","status":"True","lastUpdateTime":"2021-07-26T10:44:08Z","lastTransitionTime":"2021-07-26T10:44:08Z","reason":"ReplicaSetUpdated","message":"ReplicaSet \"tbwdcd-app-7cbdfb99d\" is progressing."}
[odo] I0726 16:14:08.566489  244796 deployments.go:199] Waiting for deployment "tbwdcd-app" rollout to finish: 0 of 1 updated replicas are available...
[odo] I0726 16:14:08.566504  244796 deployments.go:206] Waiting for deployment spec update to be observed...
[odo]  ✗  Waiting for component to start [5m]
[odo]  ✗  Failed to start component with name "tbwdcd". Error: Failed to create the component: error while waiting for deployment rollout: timeout while waiting for tbwdcd-app deployment roll out

Expected behavior
odo push should pass
Any logs, error output, etc?
oc describe pods -n storagetest
Name:           tbwdcd-app-54f9848585-9qcmr
Namespace:      storagetest
Priority:       0
Node:           <none>
Labels:         app=app
                app.kubernetes.io/instance=tbwdcd
                app.kubernetes.io/managed-by=odo
                app.kubernetes.io/managed-by-version=v2.2.3
                app.kubernetes.io/name=test-devfile
                app.kubernetes.io/part-of=app
                component=tbwdcd
                pod-template-hash=54f9848585
Annotations:    openshift.io/scc: restricted
Status:         Pending
IP:
IPs:            <none>
Controlled By:  ReplicaSet/tbwdcd-app-54f9848585
Init Containers:
  copy-supervisord:
    Image:      registry.access.redhat.com/ocp-tools-4/odo-init-container-rhel8:1.1.10
    Port:       <none>
    Host Port:  <none>
    Command:
      /usr/bin/cp
    Args:
      -r
      /opt/odo-init/.
      /opt/odo/
    Environment:  <none>
    Mounts:
      /opt/odo/ from odo-supervisord-shared-data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-z9chv (ro)
Containers:
  runtime:
    Image:      quay.io/eclipse/che-nodejs10-ubi:nightly
    Port:       3000/TCP
    Host Port:  0/TCP
    Limits:
      memory:  1Gi
    Requests:
      memory:  1Gi
    Environment:
      FOO:             bar
      PROJECTS_ROOT:   /projects
      PROJECT_SOURCE:  /projects
    Mounts:
      /data from firstvol-tbwdcd-app-vol (rw)
      /projects from odo-projects (rw)
      /secondvol from secondvol-tbwdcd-app-vol (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-z9chv (ro)
  runtime2:
    Image:      quay.io/eclipse/che-nodejs10-ubi:nightly
    Port:       <none>
    Host Port:  <none>
    Command:
      /opt/odo/bin/supervisord
    Args:
      -c
      /opt/odo/conf/devfile-supervisor.conf
    Limits:
      memory:  1Gi
    Requests:
      memory:  1Gi
    Environment:
      ODO_COMMAND_RUN:              cat myfile.log
      ODO_COMMAND_RUN_WORKING_DIR:  /data
    Mounts:
      /data from firstvol-tbwdcd-app-vol (rw)
      /data2 from secondvol-tbwdcd-app-vol (rw)
      /opt/odo/ from odo-supervisord-shared-data (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from default-token-z9chv (ro)
Conditions:
  Type           Status
  PodScheduled   False
Volumes:
  firstvol-tbwdcd-app-vol:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  firstvol-tbwdcd-app
    ReadOnly:   false
  secondvol-tbwdcd-app-vol:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  secondvol-tbwdcd-app
    ReadOnly:   false
  odo-projects:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  odo-supervisord-shared-data:
    Type:       EmptyDir (a temporary directory that shares a pod's lifetime)
    Medium:
    SizeLimit:  <unset>
  default-token-z9chv:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  default-token-z9chv
    Optional:    false
QoS Class:       Burstable
Node-Selectors:  <none>
Tolerations:     node.kubernetes.io/memory-pressure:NoSchedule op=Exists
                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                 node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason             Age                   From                Message
  ----     ------             ----                  ----                -------
  Warning  FailedScheduling   22m                   default-scheduler   0/9 nodes are available: 9 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling   22m                   default-scheduler   0/9 nodes are available: 9 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling   20m                   default-scheduler   0/9 nodes are available: 9 node(s) had volume node affinity conflict.
  Normal   NotTriggerScaleUp  2m40s (x21 over 22m)  cluster-autoscaler  pod didn't trigger scale-up:

Warning  FailedScheduling   22m                   default-scheduler   0/9 nodes are available: 9 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling   22m                   default-scheduler   0/9 nodes are available: 9 pod has unbound immediate PersistentVolumeClaims.
  Warning  FailedScheduling   20m                   default-scheduler   0/9 nodes are available: 9 node(s) had volume node affinity conflict.

This suggests something is happening with cluster storage setup.
What storage classes are configured on the cluster?
What happens if yo try to create simple deployment with PVC like this?
kind: PersistentVolumeClaim
apiVersion: v1
metadata:
  name: test-pvc
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 1Gi

---
apiVersion: apps/v1
kind: Deployment
metadata:
  labels:
    app: test
  name: test
spec:
  replicas: 1
  selector:
    matchLabels:
      app: test
  template:
    metadata:
      labels:
        app: test
    spec:
      volumes:
        - name: data
          persistentVolumeClaim:
            claimName: test-pvc
      containers:
        - image: busybox
          name: busybox
          command:
            - "sleep"
            - "infinity"
          resources: {}
          volumeMounts:
            - name: data
              mountPath: /data

and than getting info about it
kubectl describe deployments.apps test

kubectl describe pvc test-pvc

What storage classes are configured on the cluster?

On default its ibmc-vpc-block-10iops-tier, I think for storage on IBMcloud we are using Block storage for VPC

What happens if yo try to create simple deployment with PVC like this?

For the simple deployment with PVC you shared works fine. Pods were able to spin up.
kubectl describe deployments.apps test
Name:                   test
Namespace:              default
CreationTimestamp:      Wed, 28 Jul 2021 09:58:47 +0530
Labels:                 app=test
Annotations:            deployment.kubernetes.io/revision: 1
Selector:               app=test
Replicas:               1 desired | 1 updated | 1 total | 1 available | 0 unavailable
StrategyType:           RollingUpdate
MinReadySeconds:        0
RollingUpdateStrategy:  25% max unavailable, 25% max surge
Pod Template:
  Labels:  app=test
  Containers:
   busybox:
    Image:      busybox
    Port:       <none>
    Host Port:  <none>
    Command:
      sleep
      infinity
    Environment:  <none>
    Mounts:
      /data from data (rw)
  Volumes:
   data:
    Type:       PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)
    ClaimName:  test-pvc
    ReadOnly:   false
Conditions:
  Type           Status  Reason
  ----           ------  ------
  Available      True    MinimumReplicasAvailable
  Progressing    True    NewReplicaSetAvailable
OldReplicaSets:  <none>
NewReplicaSet:   test-9d46557cd (1/1 replicas created)
Events:
  Type    Reason             Age    From                   Message
  ----    ------             ----   ----                   -------
  Normal  ScalingReplicaSet  2m50s  deployment-controller  Scaled up replica set test-9d46557cd to 1

kubectl describe pvc test-pvc \
>
Name:          test-pvc
Namespace:     default
StorageClass:  ibmc-vpc-block-10iops-tier
Status:        Bound
Volume:        pvc-74e4a5e0-1ab2-4c22-80f0-a07bc199c727
Labels:        <none>
Annotations:   pv.kubernetes.io/bind-completed: yes
               pv.kubernetes.io/bound-by-controller: yes
               volume.beta.kubernetes.io/storage-provisioner: vpc.block.csi.ibm.io
Finalizers:    [kubernetes.io/pvc-protection]
Capacity:      10Gi
Access Modes:  RWO
VolumeMode:    Filesystem
Used By:       test-9d46557cd-kp7wn
Events:
  Type    Reason                 Age                From                                                                                Message
  ----    ------                 ----               ----                                                                                -------
  Normal  Provisioning           92s                vpc.block.csi.ibm.io_ibm-vpc-block-csi-controller-0_cf26be28-fd68-4e3c-9ca6-2bd0e898563b  External provisioner is provisioning volume for claim "default/test-pvc"
  Normal  ExternalProvisioning   19s (x6 over 92s)  persistentvolume-controller                                                               waiting for a volume to be created, either by external provisioner "vpc.block.csi.ibm.io" or manually created by system administrator
  Normal  ProvisioningSucceeded  13s                vpc.block.csi.ibm.io_ibm-vpc-block-csi-controller-0_cf26be28-fd68-4e3c-9ca6-2bd0e898563b  Successfully provisioned volume pvc-74e4a5e0-1ab2-4c22-80f0-a07bc199c727

When ever we are using two pv that are created in two different zones then the pods are failing with error volume node affinity conflict.
for example
-> oc get pv
NAME                                       CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                                                 STORAGECLASS                 REASON   AGE
pvc-0f9b8ffb-4661-42f7-a372-3a41e148669e   10Gi       RWO            Delete           Bound    cmd-devfile-storage-test228ubx/secondvol-awhmll-app   ibmc-vpc-block-10iops-tier            14h
pvc-22e0a37c-4f2b-4abc-a4cb-617b1f1eca14   10Gi       RWO            Delete           Bound    storage-test/firstvol-test-devfile-app                ibmc-vpc-block-10iops-tier            19h
pvc-3092082f-2b76-4e01-b433-af74815363ea   10Gi       RWO            Delete           Bound    cmd-devfile-storage-test228pxs/secondvol-xadwvi-app   ibmc-vpc-block-10iops-tier            14h
pvc-3c236748-4c64-45e2-8fe8-ebdff6431b54   10Gi       RWO            Delete           Bound    storage-test/secondvol-test-devfile-app               ibmc-vpc-block-10iops-tier            19h
pvc-74e4a5e0-1ab2-4c22-80f0-a07bc199c727   10Gi       RWO            Delete           Bound    default/test-pvc                                      ibmc-vpc-block-10iops-tier            15m
pvc-94beff15-e0f9-40b3-b52a-cc17e8a2c6c1   10Gi       RWO            Delete           Bound    cmd-devfile-storage-test228ubx/firstvol-awhmll-app    ibmc-vpc-block-10iops-tier            14h
pvc-a63a6c91-35c5-43fe-9e70-c4166ded7ac6   10Gi       RWO            Delete           Bound    cmd-devfile-storage-test228pxs/firstvol-xadwvi-app    ibmc-vpc-block-10iops-tier            14h

-> oc get pv pvc-0f9b8ffb-4661-42f7-a372-3a41e148669e -o yaml
apiVersion: v1
kind: PersistentVolume
...
nodeAffinity:
    required:
      nodeSelectorTerms:
      - matchExpressions:
        - key: failure-domain.beta.kubernetes.io/region
          operator: In
          values:
          - eu-de
        - key: failure-domain.beta.kubernetes.io/zone
          operator: In
          values:
          - eu-de-1
  persistentVolumeReclaimPolicy: Delete
  storageClassName: ibmc-vpc-block-10iops-tier
  volumeMode: Filesystem
status:
  phase: Bound

->  oc get pv pvc-94beff15-e0f9-40b3-b52a-cc17e8a2c6c1 -o yaml
apiVersion: v1
kind: PersistentVolume
...
  nodeAffinity:
    required:
      nodeSelectorTerms:
      - matchExpressions:
        - key: failure-domain.beta.kubernetes.io/region
          operator: In
          values:
          - eu-de
        - key: failure-domain.beta.kubernetes.io/zone
          operator: In
          values:
          - eu-de-1
  persistentVolumeReclaimPolicy: Delete
  storageClassName: ibmc-vpc-block-10iops-tier
  volumeMode: Filesystem
status:
  phase: Bound

and for filing case its
oc get pv pvc-3092082f-2b76-4e01-b433-af74815363ea -o yaml
apiVersion: v1
kind: PersistentVolume
...
  nodeAffinity:
    required:
      nodeSelectorTerms:
      - matchExpressions:
        - key: failure-domain.beta.kubernetes.io/region
          operator: In
          values:
          - eu-de
        - key: failure-domain.beta.kubernetes.io/zone
          operator: In
          values:
          - eu-de-3
  persistentVolumeReclaimPolicy: Delete
  storageClassName: ibmc-vpc-block-10iops-tier
  volumeMode: Filesystem
status:
  phase: Bound

-> % oc get pv pvc-a63a6c91-35c5-43fe-9e70-c4166ded7ac6 -o yaml
apiVersion: v1
kind: PersistentVolume
...
  nodeAffinity:
    required:
      nodeSelectorTerms:
      - matchExpressions:
        - key: failure-domain.beta.kubernetes.io/region
          operator: In
          values:
          - eu-de
        - key: failure-domain.beta.kubernetes.io/zone
          operator: In
          values:
          - eu-de-1
  persistentVolumeReclaimPolicy: Delete
  storageClassName: ibmc-vpc-block-10iops-tier
  volumeMode: Filesystem
status:
  phase: Bound

Whenever we are using two pv that are created in two different zones then the pods are failing with error volume node affinity conflict and pods fail to spin up.

this looks like infra inssue

I was thinking if we can create the cluster on one zone only, we can avoid this problem, I guess there should be an option to select only one zone to create a cluster.

I was thinking if we can create the cluster on one zone only, we can avoid this problem

This could be the solution that helps us fix it. Saying based on this answer on stackoverflow. We don't need to spread our cluster among zones for CI, do we? It's not a long running cluster anyway, right?

We don't need to spread our cluster among zones for CI, do we?

No, but I am currently not sure if IBMcloud have any option to select zone before creating cluster.

It's not a long running cluster anyway, right?

No, it will be a long running cluster just like the cluster we have on PSI

I was thinking if we can create the cluster on one zone only, we can avoid this problem, I guess there should be an option to select only one zone to create a cluster.
@rnapoles-rh does IBMCloud gives us such option while creating a cluster?

@anandrkskd  yes, we can have clusters using only one zone instead of three.
The Cluster named devtools-1-4vcpu-16gb-3w was provisioned using only one zone (eu-de-1) . You should be able to see it in the IBM Cloud web UI under OpenShift clusters.

@rnapoles-rh Running 10 consecutive test for the above situation passed successfully on the cluster with only one zone.

@rnapoles-rh Running 10 consecutive test for the above situation passed successfully on the cluster with only one zone.

@anandrkskd  This is perfect, can we close this issue now?

@rnapoles-rh yes, we can close this issue.

@rnapoles-rh yes, we can close this issue.

Maybe close it as well?
/remove-triage ready
/triage support
/close


⚠ Bofrost.nl has degraded performance

In 4e3f855, Bofrost.nl (https://www.bofrost.nl) experienced degraded performance:

HTTP code: 200
Response time: 2751 ms

Resolved: Bofrost.nl performance has improved in 869a5d0.


lenovo: deliberately try to break profile

This has failed with proper error message at https://travis-ci.org/NixOS/nixos-hardware/builds/321451543#L5489.


building placment

can still make buildings even if you dont have the resources
it just starts going into minus numbers

Fixed


Add variables to default config

Describe your PR, what does it fix/add?
This PR adds variables for programs that user can exec with default binds. It allows users to easier change the default behavior of binds and  makes default config more readable for new users
Is there anything you want to mention? (unchecked code, possible bugs, found problems, breaking compatibility, etc.)
No
Is it ready for merging, or does it need work?
I guess so

just because your shell sanitizes those doesn't mean every single one will, besides, it's confusing.

Variables in Hyprland work anyways in a line-to-line basis, meaning no quotes, no nothing.
See envvar as they work the same way:
https://wiki.hyprland.org/Configuring/Environment-variables/
Hyprland puts the raw string to the envvar with the env keyword. You should not add quotes around the values.


fix unused variable warning on new projects

Running anchor init and then anchor build always returns:
warning: unused variable: `ctx`
 --> programs/deleteme/src/lib.rs:9:23
  |
9 |     pub fn initialize(ctx: Context<Initialize>) -> Result<()> {
  |                       ^^^ help: if this is intentional, prefix it with an underscore: `_ctx`
  |
  = note: `#[warn(unused_variables)]` on by default

warning: `deleteme` (lib) generated 1 warning (run `cargo fix --lib -p deleteme` to apply 1 suggestion)

This is a bit of an unnecessary distraction. This PR silences the warning by simply logging the program ID in the default function handler.
Additionally, context is spelt context to be consistent with the rest of Anchor. Right now prelude, program, initialize, handler, wallet, are all full words without contractions but ctx is contracted, and when discussing Anchor we have to consistently remind people of this by saying "context, spelled 'see tee ecks'". It's a change, but people that already know anchor should easily understand that context is ctx and people new to anchor can save some unnecessary confusion.

Got It,ctx it is. Updated.


Update documentation for components

need to update documentation for all components

Related Libraries:

Storybook
storybook-readme - plugin to render README files in storybook

Superseded by #22.


Laravel 10.17.1 Shift

This pull request includes updates for the recent minor version release of Laravel as well as updates to your package dependencies. Feel free to commit any additional changes to the shift-ci-v10.17.1 branch.
Before merging, you need to:

Checkout the shift-ci-v10.17.1 branch
Review all pull request comments for additional changes
Run composer update
Thoroughly test your application (no tests?, no CI?)

:x: Shift was unable to run composer update. Please be sure to run composer update before merging to ensure your dependency changes are fully compatible and reflected in your composer.lock file.


HADOOP-17369. Bump up snappy-java to <IP_ADDRESS>.

https://issues.apache.org/jira/browse/HADOOP-17369

The changes in snappy-java side: https://github.com/xerial/snappy-java/compare/<IP_ADDRESS>...<IP_ADDRESS>

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 31s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 58s

trunk passed

+1 :green_heart:
compile
0m 22s

trunk passed with JDK Ubuntu-11.0.9+11-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
compile
0m 21s

trunk passed with JDK Private Build-1.8.0_272-8u272-b10-0ubuntu1~18.04-b10

+1 :green_heart:
mvnsite
0m 26s

trunk passed

+1 :green_heart:
shadedclient
50m  5s

branch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 24s

trunk passed with JDK Ubuntu-11.0.9+11-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 25s

trunk passed with JDK Private Build-1.8.0_272-8u272-b10-0ubuntu1~18.04-b10

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
0m 14s

the patch passed

+1 :green_heart:
compile
0m 14s

the patch passed with JDK Ubuntu-11.0.9+11-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javac
0m 14s

the patch passed

+1 :green_heart:
compile
0m 13s

the patch passed with JDK Private Build-1.8.0_272-8u272-b10-0ubuntu1~18.04-b10

+1 :green_heart:
javac
0m 13s

the patch passed

+1 :green_heart:
mvnsite
0m 15s

the patch passed

+1 :green_heart:
whitespace
0m  0s

The patch has no whitespace issues.

+1 :green_heart:
xml
0m  1s

The patch has no ill-formed XML file.

+1 :green_heart:
shadedclient
14m 33s

patch has no errors when building and testing our client artifacts.

+1 :green_heart:
javadoc
0m 17s

the patch passed with JDK Ubuntu-11.0.9+11-Ubuntu-0ubuntu<IP_ADDRESS>

+1 :green_heart:
javadoc
0m 18s

the patch passed with JDK Private Build-1.8.0_272-8u272-b10-0ubuntu1~18.04-b10

_ Other Tests _

+1 :green_heart:
unit
0m 17s

hadoop-project in the patch passed.

+1 :green_heart:
asflicense
0m 34s

The patch does not generate ASF License warnings.

71m 20s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2451/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/2451

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient xml

uname
Linux 7b969b6887ea 4.15.0-112-generic #113-Ubuntu SMP Thu Jul 9 23:41:39 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 9a9ab5b48e3

Default Java
Private Build-1.8.0_272-8u272-b10-0ubuntu1~18.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.9+11-Ubuntu-0ubuntu<IP_ADDRESS> /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_272-8u272-b10-0ubuntu1~18.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2451/1/testReport/

Max. process+thread count
414 (vs. ulimit of 5500)

modules
C: hadoop-project U: hadoop-project

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-2451/1/console

versions
git=2.17.1 maven=3.6.0

Powered by
Apache Yetus 0.13.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

Thanks, @sunchao , @viirya and @aajisaka .  I'm merging this.


Add weighted logic to collision hands

This is an implementation of weighted hands based on the current logic for holding objects in XR Tools.
It's far from perfect but it does a decent job within the current constraints of XR tools.
The main missing bit that would be an improvement is missing angular momentum when an object is held in a single hand (as dual wielding already compensates to an extent). But in order to do so we really need to tie properly into the physics engine and that requires a completely different type of logic for holding objects (I have been doing experimentation for this and may implement that approach for XR tools 2).
The other shortcoming is that when the user teleports, the movement breaks the maximum distance and we let go of the object. This I plan to resolve in a follow up PR as this requires proper signals being hooked up to our teleport system and I'm already planning work on this.
Contributed by Khronos Group through the Godot Integration Project

not sure if its related but i cant properly grab the sniper handle, it disconnects as in not being able to fully grab it.
will have to play more with this pr but it is a good start.

If the object you pick up is too heavy that it lags behind too much, we'll eventually let it go. One thing I do need to fix here is that player movement is added into this as well.

Player movement is now directly applied to collision hands (and poke body while I was in there) including when you use teleporting.
The only scenario where we're not automatically reacting is if the player is moved outside of the player body methods (a few movement providers do this) but I need to react differently depending on how the player is moved.

Player movement is now directly applied to collision hands (and poke body while I was in there) including when you use teleporting.
The only scenario where we're not automatically reacting is if the player is moved outside of the player body methods (a few movement providers do this) but I need to react differently depending on how the player is moved.

right now even with your settings its not acceptable, upon performing turn movement it twitches and it seems that your recent changes made the still movement of the hands when holding, twitch just a lil as well and i think this wasnt the case before.
Too bad this really needs another pair of eyes, one that can actualy suggest code changes instead of my 8ball comments

Hmm, I wonder why its that much more stable for me and what I've missed.
Turning and moving shouldn't have an effect anymore because we no longer apply the weight simulation. Same with teleport.
So there must be some scenarios where we're getting some oscillation.
Malcolm also noticed that because we're now properly testing for collisions, we're getting into trouble when we attach items to snap zones that bring collisions close to the hands, such as adding the scope to the gun.

Hmm, I wonder why its that much more stable for me and what I've missed. Turning and moving shouldn't have an effect anymore because we no longer apply the weight simulation. Same with teleport. So there must be some scenarios where we're getting some oscillation.
Malcolm also noticed that because we're now properly testing for collisions, we're getting into trouble when we attach items to snap zones that bring collisions close to the hands, such as adding the scope to the gun.

indeed, its a hornets Nest..
what i have noticed is that indeed the interactables on the sniper are malfunctioning most of the time, just not when the sniper is hoizontal from the side.

OK, as far as I can tell the issues we were having had to do with self colliding between our collision hands logic and the objects we had picked up, especially if those object had attachments.
As anything that is picked up or attached is added to physics layer 17, and there is no point for the  hands to collide with what we've picked up, I've removed layer 17 from the layer mask on collision hands.
That seems to have solved some of the weird issues.
I've also added an extra set of hands to visualise where our hands actually are located. This needs a little more tweaking as it doesn't work right when we're using specific grip points for the left or right hands as we hide things but thats something to tweak a little more later.

I've set this ready for review because I think this is as good as I'll get it for now.
I'm still at a loss to explain the issue with snap rotation and the held object seeming to lag. I think it may have something to do with the remote transform updating the remote nodes position incorrectly.
Seeing we already handle all the logic here I wonder if it even makes sense to use RemoteTransform here and not just apply that logic ourselves.


Interactive mode limits

Hi, first of all thanks for the repo. I have one question. In the README you state
some binaries, like the diacritizer, might take very long time to start. Hence, this option (Standalone) is preferred when you have long text and you want to do it only once.
In addition, loading the diacritizer in Interactive mode raises the following warning
[2024-07-17 11:03:58,511 - farasapy_logger - WARNING]: Be careful with large lines as they may break on interactive mode. You may switch to Standalone mode for such cases.
By the way, I'm trying to discover a limit to the Diacritizer, but I'm not able to find it. Do you have any idea of how long the text should be to break the Diacritizer? There is a text that really breaks it, or simply it doesn't work well with long text?

Thanks for the issue @lbdave94 , I, unfortunately, do not have much details on this. Thie is models dependent and it can be different from model to model. If you are more interested, you can contact farasa authors for that [https://farasa.qcri.org/]. If you have long lines, you can just run the package in the standalone mode, just to be safe. You can, by the way, evaluate both modes on your datasets and analyze the difference.


Sedflux input files

Hi Eric,
I wasn't able to find the example input files: https://github.com/mcflugen/sedflux/blob/master/docs/running.txt
Could you please give some help?

Alternatively, where I can learn the syntax of the input files?

I've created a new repository for sedflux input files. To get things started I threw up some input files for a sedflux simulation for Ohau, NZ. I'll add more later.
The new repository is here: https://github.com/mcflugen/sedflux-input

Hi Eric,
Thank you, will check the repository soon.


git clone command wrong for Scala setup

The git clone command provided for the scala setup on OSX (on page https://mxnet.incubator.apache.org/install/osx_setup.html) seems to be wrong. When I use
git clone --recursive https://github.com/apache/incubator-mxnet.git mxnet --branch 0.12.0 ~/mxnet
I get this error:
Too many arguments.
Using this it works fine:
git clone --recursive --branch 0.12.0 https://github.com/apache/incubator-mxnet.git ~/mxnet

Thanks for reporting! We'll change it accordingly.

Should be fixed by #8824


Bump administrate from 1.0.0.beta1 to 1.0.0.beta2

Updated the administrate gem from version 1.0.0beta1 to 1.0.0beta2.

Refactored the synonym show page test to check for a Destroy button instead of a link, in line with changes noted in the changelog https://github.com/thoughtbot/administrate/blob/main/CHANGELOG.md#100beta2-october-25-2024, specifically the update found in https://github.com/thoughtbot/administrate/pull/2516/.

Asana ticket

@f-moya thanks for tackling this one! It seems we also need to check if any override from the following list has changed and update accordingly:
The following templates have changed since v1.0.0.beta1:

app/views/administrate/application/_collection.html.erb app/views/administrate/application/_collection_item_actions.html.erb app/views/administrate/application/_index_header.html.erb app/views/administrate/application/_javascript.html.erb app/views/administrate/application/edit.html.erb app/views/administrate/application/index.html.erb app/views/administrate/application/new.html.erb app/views/administrate/application/show.html.erb app/views/fields/belongs_to/_form.html.erb app/views/fields/has_many/_form.html.erb app/views/fields/polymorphic/_form.html.erb app/views/fields/rich_text/_form.html.erb app/views/fields/rich_text/_index.html.erb app/views/fields/rich_text/_show.html.erb app/views/fields/select/_form.html.erb app/views/fields/text/_form.html.erb app/views/layouts/administrate/application.html.erb

@FerPerales Thanks for pointing that out, I'm realizing now that this is requires a bit more work than what I anticipated I'm gonna close and reopen.


Feature/node unity integrate

I make WebSocket server on node Express.
When you use webSocket# on unity, protocols must be switched!!

あっぶねーー！


Add to LuaRocks

Hey! I'm not actively adding features to this repo anymore. If you want to take the time to add to LuaRocks, I would review and accept a PR, but I don't have the time to add new features. Sorry for the trouble!


demo: create gist with docker compose to run all demo deps

closing in favour of https://github.com/ideal-lab5/murmur/issues/29


Generic Cluster Provider to enable IMDSv2 by default

Describe the feature
IMDSv2 enforcement is a security best practice. All AWS provided open-source projects should be secure by default and implement best practices. This project does not provide options to enable the setting of the requireImdsv2 property for the Generic Cluster Provider's launchTemplate.
Use Case
I want to provision and manage secure EKS clusters, and without the option to configure my instances to use IMDSv2 I am open to the vulnerabilities detailed in https://aws.amazon.com/blogs/security/defense-in-depth-open-firewalls-reverse-proxies-ssrf-vulnerabilities-ec2-instance-metadata-service/
Proposed Solution
The Generic Cluster Provider's launchTemplate could include an requireImdsv2 option, which if not specified, will default to true.
Potential updates include:
https://github.com/aws-quickstart/cdk-eks-blueprints/blob/main/lib/cluster-providers/types.ts
/**
 * Configuration options for the custom AMI.
 */
export interface LaunchTemplateProps {
    /**
     * The custom AMI for the node group.
     */
    machineImage?: ec2.IMachineImage;

    /**
     * The userData for worker node when using custom AMI. Only applicable when customAmi is used.
     */
    userData?: ec2.UserData;

    /**
     * Custom Tags for launch template which will propogate to worker nodes.
     */
    customTags?: {
        [key: string]: string;
    };

    /**
     * Whether IMDSv2 should be required on worker nodes.
     * @default true
     */
    requireImdsv2?: boolean;
}

https://github.com/aws-quickstart/cdk-eks-blueprints/blob/da641bd9b930dde52d49bd9f9e688bdd0fd4ee9b/lib/cluster-providers/generic-cluster-provider.ts
const requireImdsv2 = nodeGroup.launchTemplate?.requireImdsv2 ?? true;
const lt = new ec2.LaunchTemplate(cluster, `${nodeGroup.id}-lt`, {
                machineImage: nodeGroup.launchTemplate?.machineImage,
                userData: nodeGroup.launchTemplate?.userData,
                requireImdsv2: requireImdsv2
            });

Other Information
This feature has been implemented in the terraform-aws-eks-blueprints (see https://github.com/aws-ia/terraform-aws-eks-blueprints/issues/284)
Acknowledgements

[ ] I may be able to implement this feature request

CDK version used
2.72.1
EKS Blueprints Version
1.6.1
Node.js Version
v18.15.0
Environment details (OS name and version, etc.)
macOS 13.3

Good thing to know that Karpenter already applies a safer default IMDS settings to the provisioned instances:
https://github.com/aws/karpenter/blob/v0.27.1/website/content/en/v0.27.0/concepts/node-templates.md#specmetadataoptions

Thanks for the heads up on that.
Just taking a look at the Karpenter best practices and it recommends that the Karpenter controller should run on Fargate or a node group: https://aws.github.io/aws-eks-best-practices/karpenter/#run-the-karpenter-controller-on-eks-fargate-or-on-a-worker-node-that-belongs-to-a-node-group.
This suggests, that even when utilising Karpenter, there would still be a need for this feature.

AFAIK IMDS is not accessible from Fargate, so you can schedule Karpenter on EKS Fargate by adding a fargate profile like so:
getClusterInfo().cluster.addFargateProfile('karpenter-fargate-profile', {
  fargateProfileName: 'karpenter',
  selectors: [{ namespace: "karpenter" }]
})

(It becomes quite a bit more involved if you want to enable log forwarding from Fargate to Cloudwatch)
On a Karpenter deployment with 2 replicas, 250m cpu and 250Mi memory requests, this costs around $0.50 per day to run.
I believe your feature request is still valid of course, I'm just spreading the upsides of relying on Karpenter and forget about node groups altogether.

What's querying the metadata? I'd prefer it to be disabled.


[Looking for team]: Solidity + Frontend Dev

Background
Solidity + Frontend Dev 🇯🇵

3 years experience as a blockchain engineer, writing Solidity smart contract and integration to Frontend.
Participated in some ETH Global Hackathon and got prizes
(ETH NYC22, ETH Bogota 22, ETH Denver 23, ETH Tokyo 23)
Built Cross-chain NFT bridge, web3 messaging protocol, NFT trading system etc...
Worked as a business development at Financial Institution, built M&A strategy tool for investment banks.

Skills

[ ] Smart Contracts (Solidity)
(ERC20, ERC721, ERC4337(AA), CrossChain-Messaging, ERC6551 etc...)
[ ] Frontend Development (Typescript, React, Next, Vite)
[ ] dApps (ethers.js, web3.js)
[ ] Design product architecture.

Communication

[ ] telegram: Yuzurypto
[ ] twitter: @0x_Yuzu

Hi, there.
I would love to hear more about your NFT swap project. Something that is very similar to my ideas.
https://github.com/ethereumjp/find-hackathon-team/issues/5

@Aqrare hi, I DM'ed you on Telegram.


[ko] Update outdated in dev-1.21-ko.8 (M13-M40)

Related issue: #29253

[ ]  M13.  content/en/docs/concepts/services-networking/network-policies.md  | 1(+XS) 1(-)
[ ]  M14.  content/en/docs/concepts/services-networking/service.md  | 2(+XS) 2(-)
[ ]  M15.  content/en/docs/concepts/storage/storage-classes.md  | 24(+S) 1(-)
[ ]  M16.  content/en/docs/concepts/workloads/controllers/daemonset.md  | 3(+XS) 1(-)
[ ]  M17.  content/en/docs/concepts/workloads/controllers/job.md  | 2(+XS) 1(-)
[ ]  M18.  content/en/docs/concepts/workloads/pods/_index.md  | 11(+S) 0(-)
[ ]  M19.  content/en/docs/concepts/workloads/pods/disruptions.md  | 1(+XS) 1(-)
[ ]  M20.  content/en/docs/concepts/workloads/pods/init-containers.md  | 2(+XS) 1(-)
[ ]  M21.  content/en/docs/concepts/workloads/pods/pod-lifecycle.md  | 2(+XS) 2(-)
[ ]  M22.  content/en/docs/contribute/generate-ref-docs/quickstart.md  | 7(+XS) 8(-)
[ ]  M23.  content/en/docs/reference/_index.md  | 1(+XS) 1(-)
[ ]  M24.  content/en/docs/reference/command-line-tools-reference/feature-gates.md  | 3(+XS) 0(-)
[ ]  M25.  content/en/docs/reference/glossary/api-eviction.md  | 1(+XS) 1(-)
[ ]  M26.  content/en/docs/reference/glossary/kube-scheduler.md  | 1(+XS) 1(-)
[ ]  M27.  content/en/docs/reference/kubectl/overview.md  | 1(+XS) 1(-)
[ ]  M28.  content/en/docs/reference/labels-annotations-taints.md  | 2(+XS) 1(-)
[ ]  M29.  content/en/docs/reference/tools/_index.md  | 1(+XS) 1(-)
[ ]  M30.  content/en/docs/reference/using-api/health-checks.md  | 2(+XS) 2(-)
[ ]  M31.  content/en/docs/setup/best-practices/cluster-large.md  | 3(+XS) 0(-)
[ ]  M32.  content/en/docs/setup/production-environment/tools/kubeadm/install-kubeadm.md  | 7(+XS) 5(-)
[ ]  M33.  content/en/docs/setup/production-environment/windows/user-guide-windows-containers.md  | 6(+XS) 6(-)
[ ]  M34.  content/en/docs/tasks/access-application-cluster/port-forward-access-application-cluster.md  | 2(+XS) 2(-)
[ ]  M35.  content/en/docs/tasks/administer-cluster/kubeadm/adding-windows-nodes.md  | 2(+XS) 2(-)
[ ]  M36.  content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-certs.md  | 12(+S) 1(-)
[ ]  M37.  content/en/docs/tasks/administer-cluster/kubeadm/kubeadm-upgrade.md  | 33(+M) 33(-)
[ ]  M38.  content/en/docs/tasks/administer-cluster/network-policy-provider/cilium-network-policy.md  | 39(+M) 25(-)
[ ]  M39.  content/en/docs/tasks/configmap-secret/managing-secret-using-kubectl.md  | 1(+XS) 1(-)
[ ]  M40.  content/en/docs/tasks/manage-daemon/update-daemon-set.md  | 2(+XS) 1(-)

/assign @seokho-son

감사합니다!
/lgtm
/approve


Phid fetcher error

I get the following error when Phabricator sends a story to this app:
Successfully connected to Phabricator over Conduit
Phabricator-Slack connector server started on port 8085
storyID=316&storyType=PhabricatorApplicationTransactionFeedStory&storyData%5BobjectPHID%5D=PHID-CMIT-6xoj432vhfuvakcimuyj&storyData%5BtransactionPHIDs%5D%5B0%5D=PHID-XACT-CMIT-caaq75jvku4r6wg&storyAuthorPHID=PHID-USER-x2goqaxi44vaa6d25ho6&storyText=steve.workman+added+a+comment+to+rFTLd92f04ac653c%3A+Fixes+schema.org+for+reviews+with+0+reviews.&epoch=1441749295
/Users/tvdashboard/dashboards/phabricator-slack-feed/node_modules/babel/node_modules/core-js/shim.js:346
  if(it == undefined)throw TypeError('Function called on null or undefined');
                     ^
TypeError: Function called on null or undefined
    at TypeError (native)
    at assertDefined (/Users/tvdashboard/dashboards/phabricator-slack-feed/node_modules/babel/node_modules/core-js/shim.js:346:28)
    at toObject (/Users/tvdashboard/dashboards/phabricator-slack-feed/node_modules/babel/node_modules/core-js/shim.js:178:20)
    at Function.o.(anonymous function) (/Users/tvdashboard/dashboards/phabricator-slack-feed/node_modules/babel/node_modules/core-js/shim.js:739:19)
    at /Users/tvdashboard/dashboards/phabricator-slack-feed/src/Conduit/PhidFetcher.js:42:35
    at Request._callback (/Users/tvdashboard/dashboards/phabricator-slack-feed/node_modules/canduit/canduit.js:96:5)
    at Request.self.callback (/Users/tvdashboard/dashboards/phabricator-slack-feed/node_modules/canduit/node_modules/request/request.js:198:22)
    at Request.emit (events.js:110:17)
    at Request.<anonymous> (/Users/tvdashboard/dashboards/phabricator-slack-feed/node_modules/canduit/node_modules/request/request.js:1073:14)
    at Request.emit (events.js:129:20)

It looks like no response is coming from phabricator, I've got my config set like this:
{
  "server": {
    "port": 8085
  },
  "slack": {
    "username": "phabricator",
    "url": "https://hooks.slack.com/services/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"
  },
  "conduit": {
    "user": "slack",
    "api": "http://server.domain.com/",
    "cert": "cli-*****************"
  },
  "misc": {
    "ignore-ca": false
  }
}

Any ideas?

There's no error coming back from the fetch method, it's that the response from Conduit is empty when the query is made. I added a check for a null response and it doesn't crash - though I don't get links from Phabricator in the Slack messages.
I still don't know what's actually wrong though - where it's failing or what I've done wrong

Hi. It seems like the bot is failing to fetch the "More info" link for messages, which is what the API call for conduit is for. Essentially, the bot requests more info about the PHID mentioned in the story which usually contains a link. Here's what I can think of at the moment:

A conduit version incompatibility
A bug in the bot

There's a new version of the bot rewritten in go under the go branch. However, I haven't written docs on how to set it up yet.


features endpoint

Allows modules to declare features and display if they enabled or not. Originally, this was the /cloud endpoint, but /features made more sense as I was building it.
Endpoint output looks like this
{
    "enabled": [
        {
            "type": "Spring Cloud Bus",
            "name": "org.springframework.cloud.consul.bus.ConsulBusAutoConfiguration$$EnhancerBySpringCGLIB$$a9c6359d",
            "version": "1.1.0.BUILD-SNAPSHOT",
            "vendor": "Pivotal Software, Inc."
        },
        {
            "type": "Circuit Breaker",
            "name": "com.netflix.hystrix.contrib.javanica.aop.aspectj.HystrixCommandAspect",
            "version": "1.4.13",
            "vendor": null
        },
        {
            "type": "DiscoveryClient",
            "name": "org.springframework.cloud.consul.discovery.ConsulDiscoveryClient",
            "version": "1.1.0.BUILD-SNAPSHOT",
            "vendor": "Pivotal Software, Inc."
        },
        {
            "type": "LoadBalancerClient",
            "name": "org.springframework.cloud.netflix.ribbon.RibbonLoadBalancerClient",
            "version": "1.1.0.BUILD-SNAPSHOT",
            "vendor": "Pivotal Software, Inc."
        }
    ],
    "disabled": [
        "LockService"
    ]
}

Feature types
There are two types of 'features': abstract and named.

Abstract features are features where an interface or abstract class is defined that an implementation creates, such as DiscoveryClient, LoadBalancerClient or LockService. The abstract class or interface is used to find a bean of that type in the context. The version displayed is bean.getClass().getPackage().getImplementationVersion().
Named features are features that don't have a particular class they implement, such as "Circuit Breaker", "API Gateway", "Spring Cloud Bus", etc... These features require a name and a bean type.

Howto declare features:
Any module can declare any number of HasFeature beans. Examples:
@Bean
public HasFeatures commonsFeatures() {
  return HasFeatures.abstractFeatures(DiscoveryClient.class, LoadBalancerClient.class);
}

@Bean
public HasFeatures consulFeatures() {
  return HasFeatures.namedFeatures(
    new NamedFeature("Spring Cloud Bus", ConsulBusAutoConfiguration.class),
    new NamedFeature("Circuit Breaker", HystrixCommandAspect.class));
}

@Bean
HasFeatures localFeatures() {
  return HasFeatures.builder()
      .abstractFeature(Foo.class)
      .namedFeature(new NamedFeature("Bar Feature", Bar.class))
      .abstractFeature(Baz.class)
      .build();
}

Each of these beans should go in an appropriately guarded @Configuration.

/cc @dussab @dsyer @mstine @adriancole @joshlong

This is slick. :+1:

looks good. maybe add a test/example of how disabling works?

A feature shows up as disabled if there is not bean of that type. There's a potential that features won't show up in disabled at all, say "Circuit Breaker": the feature definition needs to be guarded by @ConditionalOnClass(HystrixCommandAspect.class) or something, so it wouldn't even show up (Unless there was an option for a String class name).

ps probably overengineering, but i might use buildVersion. That would only matter if we have an abstract notion of version.
ps. here's some plugin/feature/extension related prior api art
http://developer.openstack.org/api-ref-identity-v3.html
http://docs.rackspace.com/servers/api/v2/cs-devguide/content/get_extensions.html
http://apidocs.cloudfoundry.org/215/feature_flags/get_all_feature_flags.html

ps LGTM!

Closed via 93455532f922538b62770f4fc648785be22cf343


CommunityToolkit.Mvvm AlsoNotifyChangeForAttribute class

Description
Hi,
I'm using CommunityToolkit.Mvvm version 7.1.2 in MAUI project.
The "AlsoNotifyChangeForAttribute" cannot be found in version 8.0.0 after update NuGet project packages.
Regards
Antonio
Version
Other (please put exact version in description textbox)
Previous behavior
the project can be compiled.
New behavior
Severity	Code	Description	Project	File	Line	Suppression State
Error	CS0246	The type or namespace name 'AlsoNotifyChangeFor' could not be found (are you missing a using directive or an assembly reference?)	SmartWedgePLCApp (net6.0-android), SmartWedgePLCApp (net6.0-windows10.0.19041.0)	C:\Users\anton\source\repos\DacksSmartWedgPLC\SmartWedgePLCApp\BaseController.cs	14	Active
Type of breaking change

[ ] Binary incompatible: Existing binaries may encounter a breaking change in behavior, such as failure to load/execute or different run-time behavior.
[ ] Source incompatible: Source code may encounter a breaking change in behavior when targeting the new runtime/component/SDK, such as compile errors or different run-time behavior.

Reason for change
stay updated
Recommended action
do not update to CommunityToolkit.Mvvm version 8.0.0
Feature area
C#
Affected APIs
No response

This issue was moved to MicrosoftDocs/CommunityToolkit#129


[Docs] Adding region support, and emissary changes

Signed-off-by: jonahjon<EMAIL_ADDRESS>
Adding support for different regions for EKS-A packages.
Adding new Emissary version, and note about multiple instances of packages.

For emissary new version, could you update this index file as well?
Everything else looks good to me!

/lgtm
you can decide when to merge it :)

/approve

/cherrypick release-0.13


The performance of pre-trained model on ImageNet?

Could you offer the accurate accuracy or error rate on the ImageNet of the pre-trained model?
In your code of resnet, the first 7x7 conv is replaced by three 3x3 convs. This will improve the performance obviously. Therefore, I want to know the accurate accuracy of your pre-trained resnet model to make some ablation study.
Thank you.

You can directly use our pretrained model to evaluate performance on ImageNet.


Remove GoGet option from repository and handle it with ?go-get=1 instead

The normal go get protocol is to show the go-import meta tag when ?go-get=1 is appended to the url. This commit implements that behaviour and cleans the go-get option from the repository settings page.

Thanks your PR!


Pass dry-run flag to plugins

When implementing dry-run options for restores (#448) or backups, plugins will have to know not to actually act on creating things like new volumes from snapshots, or new snapshots. Thus, a dry-run flag should be added so that plugins can do the right thing.

Covered by
https://github.com/heptio/ark/issues/448#issuecomment-435910201


Plugin version rot

I'm new to the Metalsmith ecosystem, so I've been combing through the various plugins to find the ones I need. I'm primarily interested in pre- and post-processing transformations on my styles and scripts. This means that Metalsmith plugins are an intermediate dependency wrapping the real depepency on, e.g, autoprefixer or coffee-script.
Unfortunately, many of the inner dependencies are months out-of-date. This is a big issue, given the rapidly developing front-end ecosystem. peerDependencies in a future version of Node will help with this, but that's at worst a hypothetical solution and at best a long way off.
Many of these plugins are just 20-100 LOC, which is tempting me to just copy them into my own plugins directory. However, summed over a dozen plugins, this becomes a maintenance nightmare.
I don't have a proposal for a great solution, but I wanted to voice the problem. One option is to bring the most popular plugins under direct management by SegmentIO/Metalsmith. This is, of course, more work, but Metalsmith has also quickly become one of the most used static site generators (by GH stars).
Another option is to extend the Metalsmith core. Many of these plugins basically take a subset of files, output a transform, and usually drop the originals. This might sound like I'm suggesting Metalsmith become more like Gulp, which I suppose I am. But consider this excerpt from an excellent SO answer:

It's true that Gulp has certain advantages over Metalsmith. Ease of writing plugins, sadly, is not one of them. Creating new files from a Gulp plugin is harder than it should be, as is correct error handling. There's also a strong impedance mismatch between the streaming approach, and the nature of static sites to need cross-file operations.

[...]For these kind of tasks, the Metalsmith plugin API is unequivocally superior to Gulp's. [...]Basically, Metalsmith is really the Gulp of static site generators, while Gulp is the Gulp of streaming build systems. And you can combine the strengths of both, using Gulpsmith."

(http://stackoverflow.com/questions/23227248/is-there-some-gulp-plugin-that-lets-it-perform-the-function-of-a-static-site-gen/23858857#23858857)

So perhaps there's a cleaner way to take advantage of gulp's stronger, more active plugin ecosystem? And if not, how about an improved plugin infrastructure that abstracts out a lot of the plugin boilerplate? What if we could do..
Metalsmith(__dirname).
    .process({files: ['styles/screen.styl'], processors: [stylus(), autoprefixer(), csso()]})
    .process({files: ['scripts/app.coffee'], processors: [coffee(), coffeelint(), uglify()]})
    .build()
)

I'm extremely new to Metalsmith, so I hope none of the above is totally off-base!

I have not used this but it seems to be similar to what you describe https://github.com/pjeby/gulpsmith

What kinds of things are you seeing rotting? My guess it was around the 1.0 release which had some backwards incompatibility? I don't really foresee any further backwards incompatibility though so it seems like fixing them would be a single-time thing, at least for the foreseeable future. What do you think?

@ianstormtaylor It's not that the plugins are incompatible with Metalsmith. It's that the plugins are sporadically maintained, resulting in really stale versions for the underlying tools.
Example #1: metalsmith-jade uses Jade version 1.8.2. This was released in December. There have been three releases since then, the current version is 1.9.2.
Example #2: metalsmith-stylus uses Stylus version 0.47.1. This was released in July, eight months ago. This is nine releases behind the current version, 0.50.0.
This makes the plugin system as currently implemented a bit broken. Either "core" plugins need to be actively maintained, or the use of plugins which heavily depend on external libs should be heavily discouraged.

Ahhh gotcha. I think those plugins should be updated to not list jade or stylus directly in their package.json, so that it takes whatever the user has pegged as their version instead from the top-level dependencies. That's what used to happen with other Jade plugins we used to use for component at least and it seemed to work well.

Closing with that fix ^

@ianstormtaylor That's not a fix until those packages actually change. Feels a bit like punting on the issue. As the parent project, Metalsmith should take responsibility for, and monitor progress on, a change expected to occur at the plugin level.

@pikeas Actually, the whole point of the Metalsmith's core being so simple (~250 lines) is because plugins aren't its responsibility—by design. When opinionated plugins become the responsibility of a core library, the core library slowly becomes more opinionated and more complex over time.
Those packages are maintained by people (some may even be maintained by me) who are capable of merging any pull request you make, or writing the fixes themselves, assuming they agree. If you want to point them this closed issue to help explain the logic for unpegging the versions, that sounds good to me!


fix: Fixes #442. Only run moveWindowUp when Fether window "frameless" and when showing window

This didn't fix the shrinking problem unfortunately (windows)

@Tbaut I've pushed some more commits to resolve it. Primarily making it frame: false for taskbar app


[shipping] rename shippingservice to shipping

Changes
Renames shippingservice to shipping
This is part of getting all services renamed based on the overall https://github.com/open-telemetry/opentelemetry-demo/issues/1788 effort for all components in the demo.
Merge Requirements
For new features contributions, please make sure you have completed the following
essential items:

[x] CHANGELOG.md updated to document new feature additions
[ ] Appropriate documentation updates in the docs
[ ] Appropriate Helm chart updates in the helm-charts

Maintainers will not merge until the above have been completed. If you're unsure
which docs need to be changed ping the
@open-telemetry/demo-approvers.

hey @Sozhan308 could you take care of the merge conflicts?

https://www.appdynamics.com/blog/cloud/how-to-observe-opentelemetry-demo-app-in-appdynamics-cloud/ -> this link seems to be invalid


[BEAM-9748] Move Reparallelize transform to Reshuffle

Some DoFn based IOs like JdbcIO and RedisIO rely on the Reparallelize transform, a combination of a an empty PCollectionView and Reshuffle to force the materialization and reparallelize a PCollection. The idea of this issue is to extract this transform and expose it as part of the internal Reshuffle transform to avoid repeating the code for transforms (notably IOs) that require to reparallelize its output.
R: @lukecwik

Why do we want to do this over Reshuffle.viaRandomKeys which should get us the output parallelization we want?
I think that's the case, maybe @jkff who created that code may confirm.

The comments inside Reparallelize explain how this transform differs from Reshuffle.viaRandomKey(): it performs dramatically better on Dataflow in case the input PCollection is generated highly sequentially, as in the case of reading several GB of JDBC results. It almost certainly performs somewhat worse if the input PCollection is generated in a well-parallelized way, but I haven't measured that; I haven't measured the former case for non-Dataflow runners either.
I think it's reasonable to move this to Reshuffle, but rename it to something more clear: maybe Reshuffle.forSequentiallyGeneratedInput()?

Changes addressed and renamed to the suggested name by Eugene. PTAL again @lukecwik

The comments inside Reparallelize explain how this transform differs from Reshuffle.viaRandomKey(): it performs dramatically better on Dataflow in case the input PCollection is generated highly sequentially, as in the case of reading several GB of JDBC results. It almost certainly performs somewhat worse if the input PCollection is generated in a well-parallelized way, but I haven't measured that; I haven't measured the former case for non-Dataflow runners either.
I think it's reasonable to move this to Reshuffle, but rename it to something more clear: maybe Reshuffle.forSequentiallyGeneratedInput()?

This was true at some point in time for Dataflow but I don't think we have rerun benchmarks to see how it performs now.

retest this please

I had forgotten about this one. Suggestions made, can you PTAL again @lukecwik @jkff . Thanks!


Crux migrating to Maven Central

Hi, a quick heads up that we're looking to migrate Crux over to Maven Central shortly - we've got a couple of non-Clojure modules coming soon, and would generally like to make Crux more accessible/appealing to folks outside of the Clojure community too. We've mirrored our Clojars dependencies onto Central, and have re-released 1.17.1 (currently as 1.17.1-rc1) so that users can migrate without having to upgrade Crux.
Crux PRs here:

https://github.com/juxt/crux/pull/1543
https://github.com/juxt/crux/pull/1550

Could you let us know if this will cause you any issues, or whether there's anything we should do/avoid doing? Otherwise, if this works for you, I'm happy to raise a quick PR with the required changes(!)

This sounds great to me!  I'm just doing some simple tests locally (requires making the changes that need to go into a PR anyway, so no worries I will create a PR here).

Looks good to me: I'll leave the linked PR as draft until the non-RC versions hit MC, and then will update accordingly.  Are we expecting that relatively imminently?  (We're planning to cut our next Egeria release imminently, so would be nice to have this wrapped in as well 😁 )

https://twitter.com/juxtpro/status/1410289961820164105 :)


EntityState marker interface

This PR adds a new marker interface for the messages representing entity state.
From now on, all messages marked as (entity) of some kind will be marked as EntityState.
They can thus be distinguished from the generic messages and other message types such as EventMessage e.g. when creating method overloads.
The interface which is applied to all entity state messages can be configured as follows:
modelCompiler {
    interfaces {
        mark messages().entityState(), asType("some.custom.EntityState")
    }
}

Please note, that just like for all other marker interface types, the specified custom interface should extend the io.spine.base.EntityState interface used by default.
Spine version advances to 1.1.11.

@armiol PTAL.

@dmdashenkov PTAL.

@dmdashenkov PTAL again.


BUG - Bad Wizard Does not shoot projectiles.

@wadek2 Working for me. Make sure projectiles have sprites!

@wadek2 Ensure projectile settings:

Is Kinematic: OFF
Use Gravity: OFF
Projectile Speed on boss is high enough (maybe I make range only over 2.0?)