[stable/jenkins] Allow to specify resource limits

What this PR does / why we need it:
~Allow to specify resource limits for jenkins container in a more extensible way.~
~Edit: Just saw PR #5978. I believe my PR is a more elegant and future-proof fix. @oguzy you were first, you can cherry pick my changes and I'll close my PR.~

This PR:

makes it possible to configure cpu and memory requests and limits for jenkins master, in a backward compatible and future proof way.
bumps appVersion to reflect the current LTS version of Jenkins (see https://jenkins.io/changelog-stable).

Related PRs: #5978 and #6102 and #6295

/assign @viglesiasce

Hey @Nodraak since this is a backwards incompatible change we would need to do a major version bump or risk breaking many folks.
Is there way to make this backwards compatible? Can we make the same change for the agent resources?

Concerning the agent, it would be a good idea to do the same change (principle of lesser surprise), although there is a lesser need to customize the values (the agent resource consumption/requirements dont change much from one user to another, compared to containers that can host a small task needing a few Mo or a very big job requiring several Go). Let's do the same as whatever we decide for the Jenkins master, to be consistent.
It is indeed a breaking change (although helm wont crash if values.yaml contains an unknown key, but obviously this is a very non user-friendly behavior).
I see two options:

Fully backward compatible: use .resources if specified, else .cpu/.memory, else default values (through default .resources). We can always remove .cpu/.memory in the future, after a "deprecation" warning was present for some time
Breaking: ditch .cpu/.memory and leave .resources as the only option

The best way is probably to avoid breaking changes. What do you think?

Hi @Nodraak,
can we make the same change for the initContainer as well?

/ok-to-test

We can add the init-container in a separate PR

Hi again! I reworked my PR:

I updated jenkins Master and Agent resources config. I have chosen to makes my changes in a backward compatible way. I expect to not break anyone current config.
I have lowered the default request.cpu in order to enable the Pod to start in more constrained environments. The default limits are chosen to be very high to prevent unexpected performance limitation or process termination, while still having resource limitation in case Jenkins becomes wild.
I included the jenkins appVersion bump from #6102 (bump to last LTS version).

@muehlburger, the initContainer is a temporary container and I don't think configuring resources for it is really worth it. As lachie83 said, you can include it in a separate PR. If you believe this is useful, please do :)

I have verified that the resource update works as expected with the following test:
I have fetched the latest jenkins chart version, applied my PR, and  prepared several values.yaml files:

jenkins: jenkins-0.16.4 chart (helm repo update + helm fetch + tar xzf)
values-new-empty.yaml: user provided values.yaml does not contains .resources. Expected: use default values.yaml from the chart

Master:

values-new.yaml: user provided values.yaml does contains .resources. Expected: use them

Master:
  resources:
    requests:
      cpu: "new requests.cpu"
      memory: "new requests.memory"
    limits:
      cpu: "new limits.cpu"
      memory: "new limits.memory"

values-old.yaml: user provided values.yaml does not contains .resources, but does contains .Cpu or .Memory. Expected: use .Cpu and .Memory

Master:
  Cpu: "old Cpu"
  Memory: "old Memory"

I run helm install with each file and check the generated result:
for f in $(\ls *.yaml)
do
    echo $f
    helm install ./jenkins --dry-run --debug -f $f | grep -E "# Source: jenkins/templates/jenkins-master-deployment.yaml|    resources" -A 6
done

/lgtm

@Nodraak I have a case of a k8s cluster setup that requires to have request limits set even for initContainers. The container does not start without limits set. My workaround is to patch the stable/jenkins chart locally to include the limits. I'm happy to create a seperate PR. :-)

@muehlburger another workaround could be to define a LimitRange in your namespace:
https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace/#create-a-limitrange-and-a-pod
That feels kind of heavy-handed, but could work for your use case.

I know, but that is not the way we want to go. We want to be explicit as
possible with the limits.
Jacob LeGrone<EMAIL_ADDRESS>schrieb am Mi., 27. Juni 2018,
22:41:

@muehlburger https://github.com/muehlburger another workaround could be
to define a LimitRange in your namespace:
https://kubernetes.io/docs/tasks/administer-cluster/manage-resources/cpu-default-namespace/#create-a-limitrange-and-a-pod
That feels kind of heavy-handed, but could work for your use case.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/charts/pull/6077#issuecomment-400822027,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAIn5bm2a_9kL9zYP5qHWlhJZakyG4Fxks5uA-3-gaJpZM4UkgXQ
.

@muehlburger I did not thought about this use case, but you are right. I have not really found a satisfying strategy regarding resources: I just set Requests on important Pods so they are not in BestEffort category, but that's all.
Anyway, the PR have been merged, but please do create a PR :)


show move info properly

I wonder if there's some iterator magic we could do in get_move_history to skip the first one


[SPARK-15539][SQL] DROP TABLE throw exception if table doesn't exist

What changes were proposed in this pull request?
Same as #13302, but for DROP TABLE.
How was this patch tested?
DDLSuite

@hvanhovell

Test build #59302 has started for PR 13307 at commit 54bb453.

Test build #59302 has finished for PR 13307 at commit 54bb453.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59302/
Test FAILed.

Test build #59314 has started for PR 13307 at commit 2ca7bd6.

@yhuai

Seems we should convert those disabled tests to our tests? Or we should put those disabled tests to HiveQuerySuite or HiveWindowFunctionQuerySuite?

Test build #59314 has finished for PR 13307 at commit 2ca7bd6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/59314/
Test PASSed.

Merged build finished. Test PASSed.

OK, let's do that in a follow-up patch. Thanks, merging into master 2.0.

https://issues.apache.org/jira/browse/SPARK-15576


fix(messaging): APN message with critical sound causing a hidden error

Description
For IOS devices, if we have CriticalSound value in the APS payload, seems like FirebaseMessaging.onMessageOpenedApp.listen doesn't get triggered.
Related Issues
https://github.com/FirebaseExtended/flutterfire/issues/5398
Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]).
This will ensure a smooth and quick review process. Updating the pubspec.yaml and changelogs is not required.

[x] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[x] My PR includes unit or integration tests for all changed/updated/fixed behaviors (See Contributor Guide).
[x] All existing and new tests are passing.
[x] I updated/added relevant documentation (doc comments with ///).
[x] The analyzer (melos run analyze) does not report any problems on my PR.
[x] I read and followed the Flutter Style Guide.
[x] I signed the CLA.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require plugin users to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change.
[x] No, this is not a breaking change.

Thanks for your pull request. It looks like this may be your first contribution to a Google open source project (if not, look below for help). Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/ to sign.
Once you've signed (or fixed any issues), please reply here with @googlebot I signed it! and we'll verify it.
What to do if you already signed the CLA
Individual signers

It's possible we don't have your GitHub username or you're using a different email address on your commit. Check your existing CLA data and verify that your email is set on your git commits.

Corporate signers

Your company has a Point of Contact who decides which employees are authorized to participate. Ask your POC to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the Google project maintainer to go/cla#troubleshoot (Public version).
The email used to register you as an authorized contributor must be the email used for the Git commit. Check your existing CLA data and verify that your email is set on your git commits.
The email used to register you as an authorized contributor must also be attached to your GitHub account.

ℹ Googlers: Go here for more info.

@googlebot I signed it!

Oh dang, nice spot! This must have changed when we tweaked the variable naming in review.


Fix test import page-object and update dependencies

fix https://github.com/kaliber5/ember-drag-sort/issues/76

Fix import page-object (solves problem https://github.com/embroider-build/embroider/issues/1153)
Update dependencies ember-cli-babel, ember-cli-htmlbars
Move eslint-plugin-varspacing to devDependencies

I encountered the same problem today while updating embroider and this PR fixed my problem.
Thank for doing that!
For everyone else... If you don't want to get slowed down use:
"ember-drag-sort": "mkszepp/ember-drag-sort#fix-test-and-update-dependencies",
until it gets merged.

@lolmaus @simonihmig @andreasschacht it would be great to get a release with this changes?

Thank you so much and please excuse me it took so long.
Released as 3.0.1.


Set workflow timeout to 10 minutes

Airlift contribution check list

[x] Git commit messages follow https://cbea.ms/git-commit/.
[ ] All automated tests are passing.
[ ] Pull request was categorized using one of the existing labels.

https://github.com/airlift/airlift/pull/1220 run for 6 hrs for each job.

cc @electrum @dain @martint


[question] choice of Barrier impl

In TVMBackendParallelBarrier, is there any reason why this particular implementation is used instead of the more "standard" one which uses a mutex+cond_var?

The barrier was used by multiple threads to prevent one thread from running too fast (and flush the common L2 cache of another one). This happens when all the threads are doing their works and it is desirable to have a busy spinning strategy than mutex which traps into OS.
In most cases, the introduction of barrier only brings small improvement so it is OK to leave the implementation empty, and correctness won't get hurt

A most informative answer. Thanks very much!


§ Section Sign Exception

Expected behavior
I coded a recursive /tpall command that uses MiniMessage to add a click component to ask for confirmation to the sender first (code below).
MiniMessage should allow the use of the section sign § instead of throwing an exception, with maybe a warning at most (in some config/properties: warn-about-legacy-usage-of-section-sign=true by default, with whatever better name someone will come up with).
Observed/Actual behavior

Steps/models to reproduce
  /**
   * Builds a string that can be parsed by MiniMessage to add a run command click component to a piece of text.
   *
   * @param command The command to run.
   * @param text    The text that should have a click component added to it.
   * @return String that can be parsed by MiniMessage
   */
  public static String buildClickCommand(String command, String text) {
    String clickText = "<click:run_command:/%s>" + text + "<reset>";
    return clickText.formatted(command.replace("/", ""));
  }

@Override
  public void handle(CommandSenderAdapter sender, String[] args) {
    final PaperCommandSenderAdapter paperSender = (PaperCommandSenderAdapter) sender;
    final Player player = ((Player) paperSender.getCommandSender());
    final int len = args.length;
    final String keyword = "§confirm";

    if (len >= 1) {
      if (args[len - 1].equalsIgnoreCase(keyword)) {
        for (Player target : Bukkit.getOnlinePlayers()) {
          target.teleport(player.getLocation());
        }
        return;
      }
    }
    sendMessage(sender,
        buildClickCommand("tpall " + String.join(" ", args) + " " + keyword, "Are you sure?")
        );
  }

Plugin and Datapack List
LuckPerms, Utilities (custom Essentials), PluginCore (custom)
Paper version
This server is running Paper version git-Paper-540 (MC: 1.19.4) (Implementing API version 1.19.4-R0.1-SNAPSHOT) (Git: f9f9079)
You are running the latest version
Previous version: git-Paper-527 (MC: 1.19.4)
Other
NB: This is only about the wrong exception thrown when § is used outside of its legacy color code usage, not about how I could do an anti-player filter more efficiently etc... I don't really care as it's not that much of an issue with the very few people who would have the tpall permission + a modified client to allow typing the section sign + would know this cmd would work with a confirm keyword as well. And it would only need to bypass a simple click.
cc. @Machine-Maker

I'm going to close this issue as not planned as there is currently no good reason for us to modify the handling of section signs in MiniMessage. In your example, the client would be kicked if they were sent such a component anyway. Additionally, this is not a good reason for us to spend a good deal of time rewriting the parsing logic to handle this as entity/player selectors are already a thing that exist in vanilla Minecraft. Unless someone has a valid reason for needing section signs in MiniMessage that justifies the time that would be spent, we will not be making such a change.

Sometimes I really wonder why is it worth spending 30min writing an issue with repro etc when you guys don't even read correctly or until the end with the Nota Bene...
Anyway, thanks for the quick answer I guess.

I did read your note and the issue as a whole. You mention in your note:

This is only about the wrong exception thrown when § is used outside of its legacy color code usage

The exception is not wrong - it says "Legacy formatting codes have been detected in a MiniMessage string" which is correct. In your example, legacy formatting codes were in the MiniMessage string, behaviour which is unsupported by MiniMessage at this time.
Additionally, you mention at the beginning of your message that "MiniMessage should allow the use of the section sign § instead of throwing an exception". This will not and never will be the case because we want MiniMessage to be a consistent format that is the same for all end users of the library. This is the same reason why we don't allow changing the tag characters, for example.
The only part of your issue that needed addressing was whether we should allow section signs in areas that won't be rendered as colour codes, such as the "run command" click action. That was where my response came from, that it is not worth us spending the time to fix such a minor issue, especially when there are myriad workarounds (e.g., use a different symbol, write a custom tag, replace after the component is created).


Update certificates.h

Just a note, Grafana changed their root CA provider this update points to the new root of trust (previously Let's Encrypt, now Digicert)


Attestation

Attestation overview on home page does not work for me

White overview works now, it shows wrong values in some cases. Will merge to main for now to develop further.


Synchronize right-dock state in module metadata

Store the docs-opening state in the same place where camera position is (per method)
If there is no info about it, just open the doc panel if there's any documentation to show.
We don't want to store it in the file, because it should not be synchronized between users.

We should also store right-dock width.


[FLINK-26362][hive] fix IndexOutOfBoundsException when subquery selec…

…ts all fields using hive dialect.

What is the purpose of the change
To fix the issue that the IndexOutOfBoundsException will be thrown when subquery select all fields using hive dialect.
Brief change log
Add  a project node in the case that it's needed to do type conversion but can't find any project node.
Verifying this change
Add sub_query.q that contains the sql statements that will throw exception before this fix.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): no
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? no
If yes, how is the feature documented? NA

@beyond1920 @wuchong Could you please help review?


Add point to lex dialog

Codecov Report

Merging #88 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #88   +/-   ##
=======================================
  Coverage   71.34%   71.34%
=======================================
  Files          17       17
  Lines         698      698
=======================================
  Hits          498      498
  Misses        156      156
  Partials       44       44

Impacted Files
Coverage Δ

events/lex.go
0% <ø> (ø)
:arrow_up:

Continue to review full report at Codecov.

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


Add: compressor with saturation.

Not with saturation, but done. Saturation will be handled by dist/overdrive.


Restoring HOME

I setup a new Manjaro Sway installation but did not properly set it up. Then I deleted the partition that contained my home directory, thinking it was not that important, as I needed the space.
Now when I boot, Sway shows an error and I have no idea how to do anything.
Through https://github.com/Manjaro-Sway/manjaro-sway/issues/174 I found https://github.com/Manjaro-Sway/desktop-settings.
Will installing manjaro-sway-settings suffice to restore the relevant files?

No, you need to copy in your dotfiles

Thanks! I did cp -rf /etc/skel/.??* ~ and it worked :)
In the live ISO, basic key combinations where listed in the bottom left, was this part of the wallpaper or some option? How can I get that back?

Thats available via a shortcut, given you have nwg-wrapper on your machine. Then it should be Super + ?

Thanks, works flawlessly :)


I finally ran the bot but it said token invalid, anyone know why?

yeah i just dont know

please help I just made the application

Did you add your token to your config?

yeah

what is your config file named?

config.js

wait where do I put the token in config?

Ah sorry I just realized the token goes in the .env file. Please check if it is there.

yeah it is

and what if your .env file name?

.env

right before your client.login in the index.js file can you add
console.log(process.env.DISCORD_TOKEN);

then show the result

k

like client.login is line 86, do I do line 87?

above the client.login would work

k

This is GitHub, not Discord, please take chatting to https://discord.gg/vXVxsAjSMF.

still invalid

This is GitHub, not Discord, please take chatting to https://discord.gg/vXVxsAjSMF.

he is helping me tho

I'm closing and locking this issue, this is spamming everyone's notifications (and emails). Chatting isn't something you do at GitHub, you're supposed to give meaningful messages, not streaks of "k"s.
Please take this support chat to the official server with the aforementioned link.


Add support for multiple cameras

Currently, Cesium for Unity exclusively uses Camera.main for tile selection. We need to provide users with a way to add more cameras when needed. Something like Cesium for Unreal's CameraManager is a good catch-all, but there are probably some easier/automatic things we can do as well, such as collecting all cameras tagged MainCamera.
Requested here: https://community.cesium.com/t/about-more-main-camera-in-unity/24433/4
And here: https://community.cesium.com/t/get-location-or-bounds-of-tileset/25177/5

I found this Main Cam issue as load time seemed awful, I.e. not loading from nearest point but filling from the far back frustrum, so changed my AR cams to not be main and used the main cam for a top down view, rendering AR views of the content loaded from other cams, it worked 10-20x faster than having it try and load in a full horizontal type view! good call though although I think your talking about the opposite problem of only using one cameras view over many.

I have run into this issue as well, although I am a Unity newbie and might be misusing a camera.  In my experience,  if a second camera is added, the landscape in general does not fill in, on one or the other of the cameras.  I believe that this is the same problem as described in the original posting by @kring.

Yes that sounds like the same problem @dhyams.

I was looking and trying to fix this; and it seems pretty clear that (at least at first implementation) all it would take would be to iterate through all cameras and add ViewStates to the returned array
https://github.com/CesiumGS/cesium-unity/blob/3bd1519845f92a236727c93810e92936a51fe51a/native~/Runtime/src/CameraManager.cpp#L85
But, I don't see any API for getting all cameras on the C++ side, equivalent to https://docs.unity3d.com/ScriptReference/Camera-allCameras.html
I was wondering if anyone knew how to go get a list of cameras on the C++ side; I am sure I'm missing something.  But I'd like to help.

Making new Unity functionality available to C++ is easy. See here:
https://cesium.com/blog/2023/01/26/developing-for-unity/
In short, you just need to add some code that uses Camera.allCameras to the ConfigureReinterop.cs file and let Unity compile it.

@king Thank you for that....got me going on it.  Another word of advice though might really help; so far I have added the following to ExposeCPP():
Camera c = Camera.main;
Camera[] cams = Camera.allCameras;
int ncams = Camera.allCamerasCount;
Camera camera_get = cams[0]; // <- I thought this would help with the problem below, but didn't

But it still doesn't seem to expose any "getter" on the C++ side to be able to read an item from an array.  So on the C++ side, I can't iterate through a list of cameras and get each camera from the list, like the following (some logic removed for clarity)

::DotNet::System::Array1<Camera> cameras = Camera::allCameras();
for (int i = 0; i < cameras.Length(); i++) {
     Camera camera = cameras[i]; // won't compile; tried cameras.Item() also but only was a setter not a getter
     // do something with the camera, like add it to the list of ViewStates
}

cameras[i] is correct. Did you let Unity recompile the source code after you added Camera camera_get = cams[0];? Also make sure you have #include <DotNet/System/Array1.h> at the top.

Also note that there are two ConfigureReinterop.cs files. Make sure you have modified the correct one (if in doubt, try adding it to both).

@kring Yes, I have let Unity recompile multiple times; I will have to admit that I am not 100% sure of the right procedure though.  What I have been doing is

modify ConfigureReinterop.cs
load a project in Unity that uses this as a package to let it recompile; close the project
rebuild the C++ project and code (both of the cmake steps in the Developer guide)
load the project in Unity again, and try things out.

I'm pretty sure that I modified the right ConfigureReinterop.cs file; as the changes I've made in ExposeToCPP have exposed the Camera.allCameras api.  It's com.cesium.unity/Runtime/ConfigureReinterop.cs.  I have not been modifying com.cesium.unity/Editor/ConfigureReinterop.cs.
I'm sure that my difficulties are probably just being a newbie and not quite understanding the architecture of the plugin yet.

Hmm I'm not sure then. There are other (working) examples of arrays being accessed by index, so I don't know any reason it wouldn't work in your case. Sometimes it's useful to just add a comment to ConfigureReinterop.cs and save it to force Unity to recompile. My workflow is generally to keep Unity open all the time. When you change ConfigureReinterop.cs and save, Unity will recompile and reload the assembly. You may start getting errors about the native code being mismatched, but that's ok. You should then be able to use the new functionality from C++ immediately. The only time you need to shut down Unity and restart it is when you compile the native code, because Unity is not capable of hot-reloading it.

I think it's working now, thanks @kring!  I'm getting tiles in all cameras now.  Performance is taking a hit; to be expected, and probably the reason it was implemented as it was.  I'll put together a pull request as soon as I can, but definitely don't recommend merging until there's an option to only turn this on if the developer wants.  Also getting a lot of tile dropouts on all cameras, which is something that I haven't seen before on the main camera.
I basically did the naive thing and just populated the ViewStates C++ vector with the viewstates from all enabled cameras.

Ok, I'll take a look when you open the PR. I wouldn't expect any performance impact from this approach in the case where you have just one camera, so maybe something is wrong.

Sorry, I wasn't clear; no performance impact that I can see with just one camera...I had four going.

Ok, so that will force it to load tiles of the appropriate LOD to satisfy all of the cameras. If they're looking at totally different areas it could end up being 4x slower. That's pretty unavoidable, though.
Perhaps rather than using all cameras, we should have a component that you can add to your camera in order to designate it as a camera to use for tile selection?

Agreed; that would make sense, although for me, I want good tiles in every camera...it's multiple camera views watching an object moving through the world.
In the end, I think a lot of my confusion stemmed from Visual Studio not updating its evaluation of what was legal and what was not; and I was trusting the red squiggles to know if I was doing something wrong.  When I started rebuilding without worrying about the squiggles, it built fine.  Just put too much trust in VStudio in this case, being so unfamiliar with the code base.

Agreed; that would make sense, although for me, I want good tiles in every camera...it's multiple camera views watching an object moving through the world.

👍

In the end, I think a lot of my confusion stemmed from Visual Studio not updating its evaluation of what was legal and what was not

I've had good luck with Visual Studio Code, FWIW.

For reference, or if someone wants to pick it up and test to see what their results are.  While tiles show up in all cameras now, performance is poor (for me), and there are many situations in which all tiles don't show up (holes in the terrain, etc).
https://github.com/dhyams/cesium-unity/tree/add_support_for_multiple_cameras_327

thank you for this @dhyams it was very helpful

Another use case that would benefit from this: https://community.cesium.com/t/having-photorealistic-3d-tiles-content-ready-when-the-camera-arrives/31635

This was added in #421.


az aks use-dev-spaces NOT WORKING

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks use-dev-spaces Extension Name: dev-spaces. Version: 1.0.6.
Errors:
The command failed with an unexpected error. Here is the traceback:
<urlopen error [Errno 11001] getaddrinfo failed>
Traceback (most recent call last):
  File "urllib\request.py", line 1354, in do_open
  File "http\client.py", line 1252, in request
  File "http\client.py", line 1298, in _send_request
  File "http\client.py", line 1247, in endheaders
  File "http\client.py", line 1007, in _send_output
  File "http\client.py", line 947, in send
  File "http\client.py", line 1414, in connect
  File "http\client.py", line 918, in connect
  File "socket.py", line 787, in create_connection
  File "socket.py", line 918, in getaddrinfo
socket.gaierror: [Errno 11001] getaddrinfo failed

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\knack/cli.py", line 231, in invoke
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 657, in execute
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 720, in _run_jobs_serially
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 691, in _run_job
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/__init__.py", line 328, in __call__
  File "D:\a\1\s\build_scripts\windows\artifacts\cli\Lib\site-packages\azure/cli/core/commands/command_operation.py", line 121, in handler
  File "C:\Users\Pradeep\.azure\cliextensions\dev-spaces\azext_dev_spaces\custom.py", line 42, in ads_use_dev_spaces
    azds_cli = _install_dev_spaces_cli(update, do_not_prompt)
  File "C:\Users\Pradeep\.azure\cliextensions\dev-spaces\azext_dev_spaces\custom.py", line 136, in _install_dev_spaces_cli
    urlretrieve(setup_url, setup_file)
  File "urllib\request.py", line 247, in urlretrieve
  File "urllib\request.py", line 222, in urlopen
  File "urllib\request.py", line 531, in open
  File "urllib\request.py", line 640, in http_response
  File "urllib\request.py", line 563, in error
  File "urllib\request.py", line 502, in _call_chain
  File "urllib\request.py", line 755, in http_error_302
  File "urllib\request.py", line 525, in open
  File "urllib\request.py", line 542, in _open
  File "urllib\request.py", line 502, in _call_chain
  File "urllib\request.py", line 1397, in https_open
  File "urllib\request.py", line 1357, in do_open
urllib.error.URLError: <urlopen error [Errno 11001] getaddrinfo failed>

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks use-dev-spaces -g {} -n {} --space {} --yes

Expected Behavior
Environment Summary
Windows-10-10.0.19041-SP0
Python 3.8.9
Installer: MSI

azure-cli 2.26.1

Extensions:
dev-spaces 1.0.6

Additional Context

route to service team

Please kindly guide me at least temporary fixes.

Azure Dev Spaces has been retired since May 15th, 2021. The extension cannot function without the backend support for it.
The replacement functionality is Bridge to Kubernetes - please check that out and see if it will meet your needs!

@yonzhan I don't have access to close this out - can you please do so?


Use the default Gardener network addresses

Description
Changes proposed in this pull request:

Use the default Gardener network addresses

Related issues

/check-required-lables


KAFKA-3209: KIP-66: Flatten and Cast single message transforms

@kkonstantine @hachikuji Could you review? These are 2 of the last 3 built-in SMTs we have from KIP-66. I'd like to get these in since we've seen asks for both on the mailing lists (directly, for casting when the connector can't constrain the range of values, and indirectly for Flatten for use with connectors that can only handle flat schemas).
The final SMT missing is TimestampConverter, which I think is really useful, but probably too complex (both implementation + testing) to squeeze in. However, these two are useful enough that I think we should push them through if possible.

Just a followup on the mapping's split and the unchecked exception warning.
But these are not blockers, so LGTM.

Any updates here?
It'd be nice if KIP-66 was updated with which transformers are implemented in Kafka 0.10.2 and which aren't.

@hachikuji @kkonstantine Took another pass at this and I think I've addressed all the comments. Interesting how tricky some of these transformations can get, @shikhar's observation about optional/default values for Flatten in particular...
@xiongtx I'll update the wiki to include that info

/cc @gwenshap Not sure how I omitted you thus far, pretty sure you want to see some of these transformations included :)


✨ [API] Make client connection pool configurable

Make client connection pool configuration configurable from Glide's config:
https://github.com/EinStack/glide/blob/6960732bd9e99b64a798dadbeca1c5b14af8f9b6/pkg/providers/openai/client.go#L43-L50
Let's do this across all providers.

@roma-glushko  I've taken this.


Create view with extract and summarization / aggregation

Describe / create the view - the files and what is the aggregation.

Views:
10702 and 10714 which read output (token) from 10700.
in SAFRWBTR environment 4 (DM12).

View ids 10700, 10702 and 10714 are in Database=DM12; Schema=SAFRWBTR; SAFR Environment= Training Master(4).
The view 10700 is an Extract Phase view that looks up to the Order file and writes to a SAFR Token. The SAFR token is read by two Token reading Format Phase views 10702 and 10714. View 10714 also does an effective date lookup.
Description of view 10700: Reads the Item Event file and looking up to the Order file to obtain information including the Order Date to be used by views reading the SAFR Token this is writing to.
Description of view 10702: Reads SAFR Token from view 10700. This does a lookup to the Customer file to obtain the original date the customer's account was create. The output file contains a record of the summary of Current Year Sales, Previous 5 Years Sales, Prior 6 to 10 Year Sales and Total Sales per unique Customer Id. This writes to the DDName = DCUSTORO.
Description of view 10714: Reads SAFR Token from view 10700. This does an effective date lookup to the Customer Name file to obtain the Customers Name when the order occurred. It does an effective date lookup to the Customer Address file to obtain the Customer Address when the order occurred. The output file contains a record of the summary of Current Year Sales, Previous 5 Years Sales, Prior 6 to 10 Year Sales and Total Sales per unique Customer Id, Customer Name and Customer Address. This writes to the DDName = DCOBYSTO.

View built, issue complete.


app_home_opened event fires twice when the 'messages' tab is clicked

Using app.action to monitor app_home_openend fires twice when a user clicks on the messages tab
 app.event("app_home_opened", async context => {
    console.log(context.payload.tab);
  });

What type of issue is this? (place an x in one of the [ ])

[x] bug
[ ] enhancement (feature request)
[ ] question
[ ] documentation related
[ ] testing related
[ ] discussion

Requirements (place an x in each of the [ ])

[x] I've read and understood the Contributing guidelines and have done my best effort to follow them.
[x] I've read and agree to the Code of Conduct.
[x] I've searched for any related issues and avoided creating a duplicate issue.

Bug Report
Reproducible in:
package version: 1.5.0
node version: v10.14.1
OS version(s): OSX 10.14.6
Steps to reproduce:
 app.event("app_home_opened", async context => {
    console.log(context.payload.tab);
  });

Expected result:
Clicking back and forth between the Home and Messages tab should appear in the console as:
home
messages
home
messages
Actual result:

👋I tried to reproduce your issue but it never happened with my simple app. Also, although I have been working with Bolt for months, I've never heard of this problem yet.
I'm afraid the issue may be happening due to something specific to your app or its settings. How about creating a brand-new Slack app and verifying the app also has the same problem?
Also, to help us reproduce your situation, can you share a bit more details? I'm still not sure what is necessary yet but sharing the whole application code, your Slack app configuration, etc. may help others figure out what the cause is.

Thank @seratch I'll try creating a sample app to demo what I'm seeing.

Hey @seratch I did some more investigation and was able to replicate the issue with this sample app.
At a high level the app settings were:

Brand new Slack app, not distributed
Subscribed only to he app_home_opened events
Bot user (shown as always online)
OAuth bot scope (not other scopes)

I can share the complete app settings if that would help?
I also used NGROK to check what event calls Bolt was receiving.  There were two incoming calls each time the messages tab is opened (and only one call when the home tab is opened). The two messages tab calls always have different values for event_id but will mostly (though not always) have the same value for the event_time.
Let me know if I can help with any more detail. I'm kind of at the end of what I'm able to look at :)

@jamesfmac
Thanks for the information with us. I tried to reproduce your situation again, but I was not able to. I did the following steps. The issue didn't occur to me.

Create a new Slack app
Run your Bolt app with the issued signing secret
Add a bot user
Enable Event Subscriptions & add app_home_opened (the outcome is the same with bot events or/and workspace events)
Sign up for App Home open beta
Install the app to its development workspace
Restart the Bolt app with the issued bot token
Open Home / Messages tabs associated to the bot user on Slack

This issue doesn't seem to be Bolt-specific. So, as a Bolt maintainer, there is nothing further I can do for you. 🙇
I'm afraid something is happening with your Slack app configuration or workspace. Even if you build the endpoint with other tools, the problem will remain. If you don't mind, could you contact Slack's support next year? In case your Slack app has some server-side issues, they may cooperate with related teams (sharing your app id would be helpful for them).

Thanks @seratch!  agree that it doesn't look like a Bolt issue :) I'll test again in a fresh workspace and if the issue persists I'll follow your advice and raise it with Slack support.

@jamesfmac did you finally solve this issue?

@mogadanez I retested and this no longer seems to be occurring. There were no changes on my side, I can only assume that something was fixed on the Slack side.

Ya I believe it was an issue with on Slacks side that day and has been resolved. @mogadanez are you seeing similar behavior?

@stevengill I know I am having this issue.

@stevengill I am also having the same issue.

I wrote to slack support and they confirmed that its known issue

@mogadanez, Is there any way we can handle this issue for now?

something like custom rate-limit
In my case put flag  to Redis as soon as possible in request works pretty good


Implement Compilation and Linking classes and fill out main logic to support them

Using the established Task classes, we can now move onto the compilation and linking process.  As well as creating classes this also means laying out the required logic to perform these steps and some supporting testing.
At the same time very slight rework of the Task class to support a future queue system
Closes #33, closes #34

Opened #46 to deal with the unit testing - we have coverage here thanks to the system testing but it would be better to test more thoroughly, and for that it seems we might need a more significant expansion of the capabilities there

And as to the exec tests - would you rather I rework them here, or shall I open an issue for "Now that Fab produces an exec, drop the old output for the main Fab application and update its tests"?

And as to the exec tests - would you rather I rework them here, or shall I open an issue for "Now that Fab produces an exec, drop the old output for the main Fab application and update its tests"?

I think it's best to do it here rather than add something which we immediately remove.

Okay, that's the smaller things pushed, will have a look at reworking the system tests now


Broken boundary when aliasing id field

The Problem
Similar to https://github.com/movio/bramble/issues/90. There still appears to be sensitivity around id being aliased within the execution pipeline, even while running the reserved namespace safeguards in https://github.com/movio/bramble/pull/92. For example, this query still fails:
query {
  shop1 {
    products {
      id: name
    }
  }
}

Here's the message:
{
  "message": "got a null response for non-nullable field \"id\"",
  "path": [
    "shop1",
    "products",
    0,
    "id"
  ]
}

This issue is very specific to the id field, which suggests that the special execution handling of the id field causes the problem. Ideally, id should operate as a normal member of the GraphQL schema without restrictions.
Proposed fix
The work in https://github.com/movio/bramble/pull/92 is a big step in the right direction here, however it leaves the special execution rule around id in place. To close this out once and for all, I'd suggest removing all special considerations from the id field and to rely exclusively on the reserved __id namespace for federation mapping. With that, the complete schema will be an open book for standard GraphQL patterns, and only __id and __typename will impose restrictions about customizing their use.

Great spotting @gmac. I'll have a chat with @lucianjon on what would be the best way to address this.

The implementation of #90 in https://github.com/movio/bramble/pull/94 also fixes this. I’ll tidy up that PR later tonight and formally open it for consideration.


[Emails] Disable some notifications for non-admin users

This fixes #2498.
Two notifications generated by email actions (messages_missing_template and messages_action_scheduled) now add extra tag "only-for-admins".
New condition in base.html checks for this tag when displaying messages. If the tag is present on the message, then that message is shown only for administrator users. If the tag is not present, then the message is shown as usual.
Writing unit tests for this was a little bit tricky, as I wasn't able to inject adding messages to a view. So instead I moved the logic to the template tag and tested it instead of testing the view output.

@elichad Ready for your review.


You can drag potted plants through airlocks

Description
While dragging potted plants you can phase them through airlocks.
Reproduction
drag a potted plant and use the drag keybind to shove it into an airlock
Screenshots

Dupe https://github.com/space-wizards/space-station-14/issues/15332


Fix various content type issues on LIO request helpers

As pointed out internally.

plain/text is exactly backwards; it's actually text/plain.
The MIME type spec is redundant there anyways. StringContent implicitly means text/plain by default until specified otherwise.
And the only place that used the StringContent path was wrong anyway, it was supposed to be doing application/x-www-form-urlencoded. Which FormUrlEncodedContent is for, and is now used in the relevant context.

Mind you, all this seems to have absolutely no impact on anything whatsoever and be 100% academical, because as far as I can see, on local environment the web LIO endpoint just responds with 204 anyways, with or without this PR. I'd expect 415 if it didn't like anything above, so I'm wagering it just didn't care or check and all of this had an impact of exactly none whatsoever.

the parameters are ignored when they're invalid so it has been a noop.
also might as well just pass it as json and remove support for the other type...

also might as well just pass it as json and remove support for the other type...

Sorry, I'm going to ask for clarification, as this is ambiguous to me. Are you saying that the lio endpoint in question supports json? And thus we can just send json in a similar shape?

apart of the oauth, I think they all support all parameter types (as long it's valid)

oh and while at it maybe don't customize the request content if the post object is null...

@bdach here's an example of json usage: https://github.com/ppy/osu-ass/blob/289397bd71f296eed1cfc92d54e9f6c01a532d20/osu.Server.AutobahnSurveillanceSystem/User.cs#L834

I was gonna still address the points above, but I guess now that this is merged I... won't? Should have marked as blocked I guess :shrug:

Alright, I'll do a round 2 then.


ASP.NET Core 7.0 Documentation | Servers > Kestrel > Endpoints Section Header Text Overlapping

The text of header/section title is overlapping documentation panel on the right.

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

ID: 312df0ba-e769-c904-40b2-733c291704a0
Version Independent ID: fd9cc0c2-3ea3-f437-e0ac-8789fb96faf7
Content: Configure endpoints for the ASP.NET Core Kestrel web server
Content Source: aspnetcore/fundamentals/servers/kestrel/endpoints.md
Product: aspnet-core
Technology: aspnetcore-fundamentals
GitHub Login: @tdykstra
Microsoft Alias: riande

@rajgog Thanks for reporting that! The fix should be live later today or tomorrow.


getting empty test-explorer tab when using vscode-remote-wsl

I have a project that i'm trying to run in vscode-remote-wsl, but the test tab appears blank.  I've installed all the correct plugins, I believe -- Mocha Test Explorer, and Test Explorer.  The Test Explorer and Mocha Test Explorer output windows are completely empty, as well.
None of the other output tabs make any mention of the extension as far as I can see.
Any ideas?

Does it work when you open the folder locally? Is there a repo with which I can reproduce this?

hmmm.  Good question.  It had been working in local Windows, but not in WSL.. but at the moment it's not doing anything in either.  I can see it refreshing in the Test Explorer tab when I make changes to the test files, but nothing shows up, and no log information.

Try setting mochaExplorer.logpanel to true, then you'll get an output channel called "Mocha Explorer Log" that shows what the test adapter is doing.

Thanks, looks like it's some sort of problem in determining what files have tests:
[2019-11-21 16:49:21.927] [DEBUG] Looking for test files ["./test/test-*.js"] in d:\src\asset-bundle-service
[2019-11-21 16:49:21.994] [DEBUG] Found test files []

Any way to get a better handle on why it thinks none of my test-* files have tests?

try replacing ./test/test-*.js with test/test-*.js

alright, i changed that in my mocha.opts .. now it errors in Windows due to having a Linux binary (expected) in node_modules, and it works in WSL! nice.  Thanks for the assist there. I wonder if the search for test files can be made more robust to handle ./ or at least the extension could provide some information when nothing is found, without enabling special debug options?

Yeah, I was surprised about this too - I'm using a VS Code API to find the files and would have expected it to work with a glob that starts with ./.
I'll think about how to handle this situation better.

This is fixed in version 2.2.1 of the Mocha Test Explorer.


With $modal, Bootstrap 3.3.0 works, Bootstrap 3.3.1 does not

When I pop up a $modal, it has a clear background on Bootstrap 3.3.1. I'm using the demo plunkr here to show the error: http://plnkr.co/edit/Z9C41lgsTge115c4BFSf?p=preview
(Change 3.3.1 to 3.3.0 and it works.)

May be bug in BS 3.3.1
Background is visible with this tablet:
.modal-backdrop {
bottom: 0;
}

I found the same problem today, fixed with alexander's solution as well

For reference, the cause was the merging of twbs/bootstrap#14927 in 3.3.1 which changes the positioning of .modal-backdrop to absolute and sets the height dynamically rather than from the positioning.
For compatibility with the current twbs/bootstrap CSS, $modal will need to dynamically set the backdrop height and provide an equivalent to .handleUpdate() for dynamically updating the height.  However, there appears to have been quite a bit of fallout from this change, including twbs/bootstrap#15314, twbs/bootstrap#15136, twbs/bootstrap#15345, and the new requirement of calling .handleUpdate() when modal content changes described in twbs/bootstrap#15106.  So it may make sense to see how these are fixed and before diving in (in particular whether fixed positioning returns with scrollbar-sized padding).
The fix suggested by @alexander-konovalov works as long as the modal content height is not longer than the viewport height (if it is, the backdrop ends at the initial viewport bottom edge).  Setting position: fixed would avoid this (and mostly reverts the problematic commit) but would cause the behavior in twbs/bootstrap#14916.  To avoid this, I've been limiting the height of the .modal-content element of my modals and setting overflow-y: auto to move the scrollbar onto .modal-content.  Although it's not ideal for a number of reasons, it works for now.

One additional update:  I just realized UI Bootstrap places .modal-backdrop outside of .modal (as Twitter Bootstrap did before twbs/bootstrap#14724).  So adding bottom: 0 and position: fixed to .modal-backdrop should completely solve the issue (I think position: fixed is required if the modal extends below the end of the body content, but I haven't tested to be sure).  So a potential fix for UI Bootstrap would be to add these styles inline.

@kevinoid That sounds more like a workaround then a real fix though. A real fix, in my opinion, would be one where we don't deviate from the workings which Bootstrap uses. So making sure .modal-backdrop gets rendered inside of .modal.

Actually, now that twbs/bootstrap#15881 has landed, Twitter Bootstrap has gone back to placing  .modal-backdrop outside of .modal and has re-added bottom: 0 and position: fixed.  So this issue will be fixed with the next release of Twitter Bootstrap.  No changes to UI Bootstrap are required (unless I've overlooked something).

Just passing through on my way to issue #2970.

This looks like it's a Bootstrap issue with a simple temporary workaround - feel free to reopen this issue if there is more evidence that it should be fixed in UI Bootstrap.

i confirm and the issue is solved in bootstrap 3.3.4


git-cli task

I wonder why GHA haven't run on this PR, WDYT @vdemeester? 🤔 At least the e2e tests should have run for the PR, but nothing.

@Aneesh-M-Bhat needs a rebase 🙏🏼

 # ./test/helper/helper.sh: line 27: declare: tmpl_file: readonly variable


Intellisense for strings within a type's Union doesn't work properly for JSX

Bug Report
Getting intellisense (auto-complete) from strings literals that belong to a union members in JSX components seems to only work, if we do it inside the "curly braces", if we try to get intellisense from plain "quotes", nothing will come up, even though TS still evaluates well the types.
🔎 Search Terms
#intellisense  #string literals
🕗 Version & Regression Information
Since version 4.7, according to my tests, this was working correctly in version 4.6.4.

This changed between versions 4.6.4 and 4.7.4

⏯ Playground Link
Playground Link
💻 Code
type Props = {age: number} | { name: "box" };

declare function sampleFn(args: Props): any
declare function SampleComponent(args: Props): any

// Intelissense on the `name` property ✅
const a1 = sampleFn({name: "box"});

// Intelissense on the `name` property ✅
const a2 = <SampleComponent name={""} />

// No intelissense on the `name` property ❌
const a3 = <SampleComponent name="" />

🙁 Actual behavior
We don't get intellisense:

🙂 Expected behavior
Intesllisense should be available, since it is for regular TS functions.

@Andarist


Fix question about Bundles

load() method in ExtensionInterface has been modified.
Symfony commit: https://github.com/symfony/symfony/commit/85c271b7a2be7e4f9c686e30106acc7288a02686

Hi,
this question still stay true in certification for 2.3, you should add a question in Symfony3 catalog.
Mickaël


Run Submit-PullRequest.ps1 on PR creation

Changed azurepolicy.json files are validated when a PR is created.


Populate solver_stats for ECOS_BB, ECOS & SCS

Fixes #1322.
I have taken this opportunity to pass solver stats for ECOS and SCS as well when there is no solution (similar to gurobi_conif.py).

LGTM.


Temprate rainforest biomes used oaks instead of rewoofs and firs?

When I go to the temprate rainforest  biome it uses oaks shaped like firs and redwoods but not redwoods is there a way to fix this it looks bad and too unrealistic (what conifer has leafs it makes no sense?)

Yeah I'm having a similar issue. 1.18.2, version 0.11.0-Beta6. In jungle biomes, the jungle trees are replaced with dark oak.


types(icons) - adds 'colourful', uses it

Problem:
The NPM logo isn't ours, and comes in One Colour Only. This creates an icon for it using the colourful colour name, so we can use it for other things that don't neatly fit into the monochromatic colour scheme.
Fix:
Added colourful to type, added new icon Icons.NpmLogo

is the icon asset already merged? I don't see it in this PR.

@balazsbajorics it is indeed


Use lodash.get() for complex accessor

closes #187
prerequisites:

[x] branch is up-to-date with the branch to be merged with, i.e. develop
[x] build is successful
[x] code is cleaned up and formatted
[ ] tested with Firefox 52, Firefox 57+, Chrome 64+, MS Edge 16+

Summary
see also #253 but for v4 with special treatment for the 2.7 typings

so far the builder weren't using the complex accessor functions when deriving data.


Update azure-stack-windows-server-faq.md

Changed link name from AHUB to BYOL

@avishwan : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off

@avishwan: I'm sorry - only the author of this article, @sethmanheim, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

@avishwan Looks good, thanks!
#sign-off


PathPrefix().Handler seems doesn`t work

I implement 2 forms  the first form the middlewares are executed and the second form the middleware aren`t executed just the wrap handler.
1 ex:
package test

import (
    "net/http"
    "os"

    "github.com/gorilla/mux"
    "github.com/urfave/negroni"
    "shelfgit.com/nuveo/cartman/middleware"
)

const (
    path = "/bug"
)

func routes(r *mux.Router) {
    r.Handle("/test", negroni.New(middleware.JwtMiddleware(os.Getenv("CARTMAN_JWT_KEY")), middleware.RuleMiddleware(), negroni.Wrap(http.HandlerFunc(func(w http.ResponseWriter, r *http.Request) {
        w.Write([]byte("Ola"))
    }))))
}

func RegisterRoutes(r *mux.Router) {
    testRouter := r.PathPrefix(path).Subrouter()
    routes(testRouter)
}

ex 2:
package test

import (
    "net/http"
    "os"

    "github.com/gorilla/mux"
    "github.com/urfave/negroni"
    "shelfgit.com/nuveo/cartman/middleware"
)

const (
    path = "/bug"
)

func routes(r *mux.Router) {
    r.HandleFunc("/test", func(w http.ResponseWriter, r *http.Request) {
        w.Write([]byte("Ola"))
    })
}

func RegisterRoutes(r *mux.Router) {
    testRouter := r.PathPrefix(path).Subrouter()
    r.PathPrefix(path).Handler(negroni.New(middleware.JwtMiddleware(os.Getenv("CARTMAN_JWT_KEY")), middleware.RuleMiddleware(), negroni.Wrap(testRouter)))
    routes(testRouter)
}

Hi @felipeweb,
The issue with your second example is that you are registering the routes directly on a subroter linked with the original router so it'll circumvent the middlewares. Assuming I'm understanding correctly that you want to link up a set of middlewares with a specific path prefix (/bug) you should be able to do something like:
package main

import (
        "log"
        "net/http"

        "github.com/gorilla/mux"
        "github.com/urfave/negroni"
)

const (
        path = "/bug"
)

func routes(r *mux.Router) {
        r.HandleFunc("/test", func(w http.ResponseWriter, r *http.Request) {
                w.Write([]byte("Ola"))
        })
}

func RegisterRoutes(r *mux.Router) {
        bugRouter := mux.NewRouter().PathPrefix(path).Subrouter()
        routes(bugRouter)

        r.PathPrefix(path).Handler(negroni.New(negroni.NewLogger(), negroni.Wrap(bugRouter)))
}

func main() {
        r := mux.NewRouter()
        RegisterRoutes(r)
        http.Handle("/", r)
        log.Fatal(http.ListenAndServe(":3000", nil))
}

Where you create an independent router that you wire up the routes to and then wire it to the top level router via negroni.Wrap().
Let me know if this helps!

it`s very helpful thank you


Merge theoraplay improvements upstream

Lots of improvements to seeking, single-threaded operation, custom allocators, etc. Push this stuff back to TheoraPlay itself.

I want to solve #8 before doing this, though.

This got pushed a little while ago.


Option for Keyboard remap/ shortcut's to keep original key press

Description of the new feature / enhancement
When i make a shortcut or remap, both the original key press and the shortcut/ remap, happens.
Scenario when this would be used?
In my scenario, i like to use my media keys to do both their media controls and to act as F10 or F9 depending on volume up or down respectively.
Why? Because i use another software for volume controls and i dont get a volume slider when controliong volume. So i use another (3rd) software for a volume slider.
Supporting information
No response

So you remapped a key that is used by a different system like a volume slider that uses the same key strokes under the hood, correct?

if so, i doubt we can do anything here as Windows cannot tell what device an input has happened on, only an input happened

I use Voicemeeter Banana for audio control. Voicemeeter uses my volume
wheel so i cant see a volume slider if im not looking at VB.
I used to have a Corsair keyboard that allowed me to remap and also use
it's volume wheel for its original purpose. And with the remapping used
another software for volume control with the remapped keys (F9 and F10).
Now i have another keyboard so cant use Corsair software. And im looking
for a software to allow me to remap volume wheel and also use it as a
volume wheel at the same time.
I hope that clears my request. I don't know if windows would allow that, or
if its a hardware thing Corsair figured out.
On Tue, Sep 28, 2021, 15:03 Clint Rutkas @.***> wrote:

if so, i doubt we can do anything here as Windows cannot tell what device
an input has happened on, only an input happened
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/microsoft/PowerToys/issues/13449#issuecomment-929497117,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AVZV5JZQUERA2HTUFUVGCZLUEH7OFANCNFSM5EZTHXAQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

Corsair i bet actually remapped at a hardware / driver level.  We're one level above.  We just see a vkey and remap.  https://github.com/microsoft/PowerToys/issues/1460 was the tracking issue but the API just doesn't exist.


alertify.alert doesnt work in mithril (m.request) response

i am working on a project where i am using mithril.js and also using alertify.js in the response i want to alert some data it doesnt work and if the same alert i am using before m.request it works fine
        function send_data()
        {
         m.request({
            method: "GET",
            url: url_root,
            config: xhrConfig
        }).then(
            function(response) {
             alertify.alert("test");
          });
     }
send_data();

Works for me using alertify 3.11. v0.5rc1 can't even execute without breaking ('alertify is undefined'). What problem are you facing?

Thanks Dude :) u made my day !
Problem was indeed with the version

@aatifbandey no worries :) – does that mean I get an 'answer accepted' on the SO question? :D


Add jest config in package.json to capture both js/ts files, transform ts

Adds jest config necessary to run both js and ts tests at the same time from the top-level directory snapp-cli directory.
Fixes o1-labs/snapp-cli/issues/30.

This is great! Works well. Thanks!


Fix NPE in SdlRouterService

Fixes #1869
This PR is [not ready] for review.
Risk
This PR makes [no] API changes.
Testing Plan

[x] I have verified that I have not introduced new warnings in this PR (or explain why below)
[x] I have run the unit tests with this PR
[x] I have tested this PR against Core and verified behavior (if applicable, if not applicable, explain why below).
[x] I have tested Android

Unit Tests
n/a
Core Tests
I tested manually setting the HashMap registerApps to null just before the spot where the NPE was hitting and connecting to a Sync 3 tdk.
Summary
This PR adds a null check in the RouterService to prevent an NPE from appearing for a partner app.
CLA

[x] I have signed the CLA

Will target develop and merge once #1853 is approved and merged into develop as well.


[Middenheim: City of the White Wolf] [Power Behind the Throne] the grand duchy of Middenheim journal text overlap

The Grand Duchy of Middenheim, many pages appear with text overlapping more textFrom: @telles007foundry: 11.315wfrp4e: 7.0.3wfrp4e-altdorf: 4.0.1wfrp4e-archives1: 4.0.2wfrp4e-core: 4.0.2wfrp4e-dotr: 4.0.2wfrp4e-eis: 4.0.1wfrp4e-middenheim: 4.0.2wfrp4e-pbtt: 4.0.2wfrp4e-up-in-arms: 4.0.1wfrp4e-wom: 4.0.1Active Modules: ATL, CautiousGamemastersPack, JB2A_DnD5e, SharedVision, WhisperBox, advanced-drawing-tools, autoanimations, autocomplete-whisper, colorsettings, df-curvy-walls, dice-so-nice, drag-ruler, forge-vtt-shared-compendiums-ingredients-feitos-por-mim, forge-vtt-shared-compendiums-landing-page, forge-vtt-shared-compendiums-telles-compendium, foundryvtt-simple-calendar, healthEstimate, image-hover, item-piles, journal-icon-numbers, journal-whiteboard, lib-df-buttons, lib-wrapper, monks-active-tiles, monks-bloodsplats, monks-combat-details, monks-combat-marker, monks-common-display, monks-little-details, party-overview, perceptive, popout, remote-highlight-ui, routinglib, sequencer, settings-extender, smart-doors, smarttarget, socketlib, token-action-hud-core, token-action-hud-wfrp4e, token-attacher, torch, wfrp4e-dotr-maps, wfrp4e-eis-maps, wfrp4e-gm-toolkit, wfrp4e-pbth-maps, wfrp4e-ubersreik-maps, forge-vtt

It seems to happen only when viewing the journals in multiple pages

Closing until further details provided


docs: add Xite to users list

We use superset in our company for quite a while now and would like to be there as one of users!

Codecov Report

Merging #11775 (6900fb9) into master (db73869) will decrease coverage by 4.67%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #11775      +/-   ##
==========================================
- Coverage   67.20%   62.53%   -4.68%
==========================================
  Files         903      446     -457
  Lines       43719    27409   -16310
  Branches     4199        0    -4199
==========================================
- Hits        29380    17139   -12241
+ Misses      14235    10270    -3965
+ Partials      104        0     -104

Flag
Coverage Δ

cypress
?

javascript
?

python
62.53% <ø> (-0.96%)
:arrow_down:

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

Impacted Files
Coverage Δ

superset/db_engines/hive.py
0.00% <0.00%> (-85.72%)
:arrow_down:

superset/databases/commands/create.py
32.65% <0.00%> (-59.19%)
:arrow_down:

superset/db_engine_specs/hive.py
54.08% <0.00%> (-29.97%)
:arrow_down:

superset/views/database/mixins.py
59.64% <0.00%> (-22.81%)
:arrow_down:

superset/db_engine_specs/presto.py
69.76% <0.00%> (-12.53%)
:arrow_down:

superset/db_engine_specs/mysql.py
79.59% <0.00%> (-12.25%)
:arrow_down:

superset/databases/commands/update.py
85.71% <0.00%> (-8.17%)
:arrow_down:

superset/databases/dao.py
94.11% <0.00%> (-5.89%)
:arrow_down:

superset/databases/api.py
81.93% <0.00%> (-5.47%)
:arrow_down:

superset/views/database/validators.py
78.94% <0.00%> (-5.27%)
:arrow_down:

... and 474 more

Continue to review full report at Codecov.

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

Awesome @shashankkoppar ! Go ahead and add yourself in alphabetical order and this will be good to merge!

Ah okay! doing it! :)

Welcome aboard!


Deployment 2017.01.27

Deployment 2017.01.27
Status: Planned
Planned production date: 01/31/2017
Focus: bug fixes, preparation for scoped API keys
Services to Deploy:

V2 Gallery

Related blog posts/docs:

None

Deployed commit:
Deployment Process

[ ] Update DB schema (not applicable)
[ ] Deploy services
[ ] Update deployments overview
[ ] Deploy secondary region

Test Plan:

[ ] Run all functional tests
[ ] Smoke testing

Changes

Build

Improved build script (PR https://github.com/NuGet/NuGetGallery/pull/3477)
Enable UseBasicParsing on PowerShell web requests (PR https://github.com/NuGet/NuGetGallery/pull/3488)

Test

Allow functional tests to run against any URL (issue https://github.com/NuGet/NuGetGallery/issues/3483, PR https://github.com/NuGet/NuGetGallery/pull/3489)
Fix functional tests (issue https://github.com/NuGet/Engineering/issues/188, PR https://github.com/NuGet/NuGetGallery/pull/3501)

Functional

Filter out unsupported credentials (PR https://github.com/NuGet/NuGetGallery/pull/3479)
Renew SSL certificate (https://github.com/NuGet/Engineering/issues/96)

Add Cert update changes in here too?

yup, good idea.

Done.

Redeploying these changes to Dev, it missed the config changes from nuget deployment to add new certs.

deploying to INT as well.

search svc deployed to prod (all regions)


LC3 decoding is slow

 Are there plans to improve fixed-point computing?
 In the decoding comparison test, LC3 is much slower than opus custom's decoding speed. The test samples are 16000 sample rate, 32000 bits rate, frame 10ms, Opus Custom decoding time is 6ms, LC3 is 18~19ms.
The test platform is a 48MHz Cortex-M0+.

Thanks for your test.
Sure, all the samples processing is made in floating point. If you don't have FPU, the performance is in fact catastrophic.
The performance of floating point processing on common CPU w/FPU, is generally much better than fixed point processing, as you don't have to handle the multiples normalization shifting / rounding.
So you mention :

~90 MCPS for LC3 decoding
~29 MCPS for Opus decoding

As a comparison, I can share some results I have running Corex M33, with 10 ms frame at 32 kbps :

LC3 Encoding: 12.1 MCPS   Decoding : 5.1 MCPS
Opus Encoding : 27.3 MCPS   Decoding : 19.2 MCPS
So, it should run in this configuration more than 2x faster than Opus.

A porting to fixed point will give you a boost around 10x less computation needs (will certainly result in < 10 MCPS).
Unfortunately, there is no plan at this time for a such porting.
Can you share your use case, is it for HFP or LE Audio?
Is there a lot of interest for the porting?

@asoulier
Thanks for your reply.
I plan to develop a low-cost LE Audio that can run on a 48MHz Cortex-M0+ MCU. Unfortunately, most of these MCUs do not have FPUs.
I tested the floating-point performance of the opus custom and it took 18.4ms, slightly better than LC3.
I noticed that your test data actually has some differences between OPUS and OPUS Custom, OPUS consists of Silk and Celt, while OPUS Custom only applies Celt.
OPUS uses 48kHz by default when encoding, decoding is also 48kHz, and finally resampling to the target frequency. This is not the case with Opus Custom (CELT), which is encoded and decoded at the frequency of interest without resampling.

Sounds good, but definitely needs to run in fixed point.
I have done a quick porting of the MDCT here.
Of course will be not enough, but that will be time consuming to port all the code.
About the benchmarks, they are a bit old, and I cannot remember exactly what are the parameters of Opus.
But I think it's probably using "Low latency" application mode (disable SILK I guess), and complexity set to 0.
By the way, CELT and LC3 core algorithms are quite close, looks normal that performance are also somewhat close.

@asoulier
I tested the new fixed-point branch and the decoding speed was greatly improved, about 14ms. However, there is a function lc3_ltpf_synthesize(), which sometimes consumes a lot of computing power, increasing the time from 14ms to 36ms.
Expect you to have new good news。

Yes, it's normal, there is a FIR that is activated when a pitch is detected by the encoder.
On higher bitrates, this filter is always disabled.
This filter needs also to be ported in fixed point.


Update google-auth-library-credentials to 1.26.0

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

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.google.auth", artifactId = "google-auth-library-credentials" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "com.google.auth", artifactId = "google-auth-library-credentials" }
}]

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

Superseded by #388.


added richard wang

Just added myself to the contributors list!

Hi  @richardlwang, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


🏹👆 : make that arrow interactive

Problem

currently non Clickable
me / user thinking it's clickable
and clicking again and again
but nothing happens

Solution

which will redirect to
the section next to it
ie. About
with transition

Yes, this can be done. Good idea.
Do you want to open a Pull Request for this, @withrvr?

@HarshKapadia2
y not
and it's very small only
and I will also learn how to contribute
but will do it tomorrow


Documentation

What needs occurred
also refer to an issue
What you changed (What reviewers have to see)
list them ALL
also refer an issue of development declaration
Description
Write something reviewers may be difficult to understand without explanation
Check list

[ ] Code styles confirmed
[ ] Test confirmed

Codecov Report
Attention: 8 lines in your changes are missing coverage. Please review.

Comparison is base (1a21a43) 94.52% compared to head (2d5db6f) 93.46%.
Report is 3 commits behind head on dev.

Files
Patch %
Lines

AnimatedWordCloud/Animator/Animator.py
20.00%
8 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##              dev      #68      +/-   ##
==========================================
- Coverage   94.52%   93.46%   -1.06%
==========================================
  Files          27       27
  Lines         657      673      +16
==========================================
+ Hits          621      629       +8
- Misses         36       44       +8

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


Release 2.1.0-rc.1

Release Checklist

Attention: the examples below use the version 2.1.0-rc.1 but you should update
them to use the version you're releasing.

Git Preparation

[x] Decide on a version number based on the current version number and the
common rules defined in Semantic Versioning. E.g.
2.1.0-rc.1.
[x] Update this ticket name to reflect the new version number, following the
pattern "Release 2.1.0-rc.1".
[x] Cut a branch for the new release out of the develop branch, following
the gitflow naming pattern release/2.1.0-rc.1.

Code Preparation

[x] Update the project's version in package.json accordingly.
[x] Update the CHANGELOG.md with the new version number and release notes.
[x] Run tests and linting, and make sure the version running in the default
branch is working end-to-end. At least the minimal end-to-end manual tests
is mandatory.
[x] 🚨 DO NOT RELEASE before holidays or weekends! Mondays and Tuesdays are
preferred. This doesn't apply if you're releasing a release-candidate
(pre-release).

Merging the Branches

🚨 ATTENTION: in the following steps, do merge commits and NOT
squash-and-merge!

[x] When the team is confident the release is stable, you'll need to create
two pull requests:

[x] ~release/2.1.0-rc.1 -> main: This PR should be merged with a merge commit.~
Skip this step if releasing a release-candidate (pre-release).
[x] release/2.1.0-rc.1 -> develop: this should be merged after the main
branch is merged. This PR should be merged with a merge commit. #115

Publishing a Pre-Release

[x] After the pre-release branch is merged to develop, create a new release
on GitHub with the name 2.1.0-rc.1 and the use the same changes from the
CHANGELOG.md file.

[x] Make sure to mark the release as a pre-release.
[x] The pre-release should automatically publish a new version of the docker
image to Docker Hub. Double check if that happened.
[x] The pre-release should not update the latest tag on Docker Hub.

Released: https://github.com/stellar/stellar-disbursement-platform-frontend/releases/tag/2.1.0-rc.1


Possible naming improvements

I was a bit surprised when approaching the package by the complexity of the naming.
What surprised me :

the tool is named pyannotate but you must import pyannotate_runtime to use it
collect_types.init_types_collection() ? Does the name really need to be that long ? Do we really need to explicitly init by the way ? Why not initialize on first resume() ?
dump_stats() is ok but dump() is good too

Suggestions :

allow to import directly from pyannotate
3 functions only : start(), stop(), dump()
initialize on first start() or rename init_types_collection() to init()

By the way, I am looking into contributing to pyannotate.

Even dump() could be left to an atexit handler.

The reason for the unusual module naming is that I want the runtime support to be separate from the command line tool that reads the JSON file and updates your source code.
The reason for the separate init_types_collection() call is that this should be called before starting any threads, at least if you're interested in getting results from other threads (at Dropbox we have a solid use case for this). I suppose we can rename this to init().
Doing the dump() in atexit() feels too late and too implicit.
Honestly I would rather (first) see a contribution that added good documentation, so we can stop referring to the blog post, instead of further changes to the API naming (which feels pretty shallow).
In terms of features I'd like to see a way of merging multiple type_info.json files, e.g. to combine results gathered by multiple tests run as separate processes (possibly on separate hosts), perhaps similar to the functionality in coverage.py for merging coverage results.

Thanks for the clear feedback.
I don't get the point about the threads though. If you want to collect type information from other threads, you should call start() before any of these threads gets started, and start will implicitly call init() so all is fine.
And if your threads are active, even if you call start() (and so init()) late in their lifetime, you should still capture their live type information. Am I missing something ?
If you look at monkey type, their code instrumentation is much much simpler to use. Just do monkeytype run  or just use one context manager.
I'll try to work on the missing aspects. Python 3 type annotations is top priority to me, beause after 10 years of lobbying, it looks like the world mostly has switched to Python 3 (eventhough Dropbox and a few other codebase are resisisting).
Improved documentation is also indeed important and should not be that difficult to get.
Then I agree that merging multiple type_info is a critical feature. This allows to collect type information in different environements and benefit from it. In my opinion, pyannotate should even propose some modes where existing function type information is enhanced with external type information, to get a more granularity for the incremental typing.

The use case for threads is the Dropbox Client. We have a debug version that lets a developer start and stop type collection using a menu entry. This is handy so you can collect types for a specific sequence of operations in the app (but not for the rather long app startup sequence). The init() method needs to be called when the app initializes itself, because the app creates long-running threads. If init() was implicitly called by start(), we would collect no types from threads that have already started.
As a compromise, I think it's fine to have start() call init() if it hasn't been called yet -- we must make sure that calling init() multiple times is okay.
Note that init() also has a optional argument used to filter filenames. This makes more sense here than for start(). Similarly, dump_stats() is separate because it takes an output filename. (You can use dumps_stats() if you want to do something else with the data -- though I think it's a shame there's no API to get the JSON as a dict instead of as a string.)
What we could also use is an API that resets all the global state -- similar to what collecting_types() in pyannotate_runtime/tests/test_collect_types.py does.
So, all in all I am open to API changes but I want certain functionality to be available.


evdev and fbdev changes from 'master' into 'beta'

Sync devel branch 'beta' to current 'master', which contains important fbdev- and evdev-related changes.

Thank you!


Publish FAQ

Describe the issue
The FAQs have been approved and we need to find a place to put them. We are restricted in our ability to post internally or externally based on interregnum, but we want to make sure this resource is available.
Which Sprint Priority is this issue related to?
The 'Milestone' should clearly list Sprint Priorities - which one is this issue related to?
Additional context
Add any other context, attachments or screenshots
Definition of done

FAQs being placed in a location that is accessible to government employees.
follow up has happened with CITZ Comms people for suggestions on where to put FAQs

Majority of FAQ content incorporated into webpage updates. FAQs won't be published separately, but will be retained as an internal resource.

Majority of FAQ content incorporated into webpage updates. FAQs won't be published separately, but will be retained as an internal resource.


Update to reduce redundancies and simplify code

Details will be noted in the changes;

By the way, good job on documenting your code, It was honestly not hell to go through despite being in python ;)
I appreciate the credit youve given me on this, I have been programming since i was in middleschool but never took documentation of my half finished projects/work seriously until a few years ago so ive just been trying to make up for it on my resume. If you ever want to collab on like another fusion addon or project let me know id be happy to help if it interests me! I do have an addon or two I was thinking would be great to have while i am actively developing my big project.

Thanks for updating your PR!
That you're using it in a big project gives me confidence to release a new version to the app store. NoComponentDrag is actually the add-in I use the least, as I tend to CAD small things. (Note: The Autodesk approval process usually takes a few weeks).
In work projects, it is often customary to squash the commits and I think I will do that in this case.


Remove support for weighted threshold conditions

Assuming we wish to follow the reference implementation (interledger/five-bells-condition). See commit https://github.com/interledgerjs/five-bells-condition/commit/2059af5550c085ba8f6ca6d981b7f92b08aca211
Rewriting the commit message here for convenience:

The fact that threshold conditions are weighted doesn't seem to provide enough of a benefit to warrant the complexity this feature adds. We will take out the weights for now and possibly add a weighted threshold condition type in the future.
BREAKING: Threshold condition are no longer weighted.

closing as it is part of #51


uyuniadm/uyunictl needs to be run as root

When running uyuniadm/uyunictl not as root, I see the following warning:
uyuniadm
❯ uyuniadm -h
5:55PM INF Welcome to uyuniadm
zerolog: could not write event: can't open new logfile: open /var/log/uyuni-tools.log: permission denied
Uyuni administration tool used to help user administer uyuni servers on kubernetes and podman

(...)

After running, it once with sudo and then again without it, the output is changing:
❯ sudo uyuniadm -h
5:59PM INF Welcome to uyuniadm
Uyuni administration tool used to help user administer uyuni servers on kubernetes and podman

(...)
❯ uyuniadm -h
5:59PM INF Welcome to uyuniadm
zerolog: could not write event: can't rename log file: rename /var/log/uyuni-tools.log /var/log/uyuni-tools-2023-11-17T16-59-32.150.log: permission denied
Uyuni administration tool used to help user administer uyuni servers on kubernetes and podman

(...)

dgedon on 🌐 b660 in /var/log🔒
❯ ll /var/log/ | grep uyuni
.rw------- root   root            252B Fri Nov 17 17:59:27 2023   uyuni-tools.log

dgedon on 🌐 b660 in /var/log🔒

uyunictl
❯ uyunictl exec -ti bash
zerolog: could not write event: can't rename log file: rename /var/log/uyuni-tools.log /var/log/uyuni-tools-2023-11-20T13-11-53.982.log: permission denied
zerolog: could not write event: can't rename log file: rename /var/log/uyuni-tools.log /var/log/uyuni-tools-2023-11-20T13-11-53.982.log: permission denied
zerolog: could not write event: can't rename log file: rename /var/log/uyuni-tools.log /var/log/uyuni-tools-2023-11-20T13-11-54.145.log: permission denied
zerolog: could not write event: can't rename log file: rename /var/log/uyuni-tools.log /var/log/uyuni-tools-2023-11-20T13-11-54.145.log: permission denied

~
❯ sudo uyunictl exec -ti bash
[sudo] password for root:
uyuni-server:/ # exit
exit

❯ uyunictl cp dom.test server:/root/
2:22PM INF Welcome to uyunictl
zerolog: could not write event: can't rename log file: rename /var/log/uyuni-tools.log /var/log/uyuni-tools-2023-11-20T13-22-43.956.log: permission denied
2:22PM INF Executing command: cp
zerolog: could not write event: can't rename log file: rename /var/log/uyuni-tools.log /var/log/uyuni-tools-2023-11-20T13-22-43.956.log: permission denied
2:22PM FTL Unknown container kind:
zerolog: could not write event: can't rename log file: rename /var/log/uyuni-tools.log /var/log/uyuni-tools-2023-11-20T13-22-44.140.log: permission denied

~
❯ sudo uyunictl cp dom.test server:/root/
[sudo] password for root:
2:22PM INF Welcome to uyunictl
2:22PM INF Executing command: cp

~ took 5s
❯ sudo uyunictl exec -ti bash
uyuni-server:/ # ls -l /root/
total 4
drwxr-xr-x 1 root root   0 Mar 15  2022 bin
-rw-r--r-- 1 root root   0 Nov 20 14:17 dom.test
-rw-r--r-- 1 root root 846 Nov 20 13:43 spacewalk-answers
drwx------ 1 root root 276 Nov 20 13:44 ssl-build
uyuni-server:/ # exit
exit

The log file issue has been fixed in the mean time


chore: migrate stacks-ui part 4 + 5

Try out this version of Leather — download extension builds.

@pete-watters I think I am done addressing comments on my branch. You'll have to rebase here again, sorry.

Looks like great progress @pete-watters 👍

~@pete-watters I think I am done addressing comments on my branch. You'll have to rebase here again, sorry.

Awh thanks! It's no problem to rebase if needed, thats the nature of a task like this

Noting here, I had a merge conflict I just realized on my new branch I didn't resolve correctly. I will push up a fix to the base branch. It was with creating the error.label color. Will fix!

@fbwoolf I've just been pushing stuff here, my outstanding items are listed here: https://github.com/leather-wallet/extension/issues/4381
I need to stop now as my eyes hurt but we made good progress!

Merging this into part 3 so I pull the changes into my part 1 branch.


About overfitting during model training

Hi, thank you very much for your work! I found that most of the models auc converged to the maximum value in the first 20% epoch during the training process, and the auc began to decline, but the train loss decreased all the time. Does this mean that overfitting occurred in the model training process? I hope you can answer this question.

Yes. you are right. if the training loss decreases but the validation loss or test loss increases, the model has gotten overfitting for the given dataset.


Multipart Media Responses Don't Work in Python3

The multipart parser doesn't work with Python3
https://github.com/refindlyllc/rets/blob/master/rets/parsers/get_object.py#L9
In short, bytes=string in Py2 and unicode=string in Py3. So we need to decode the response.content in Py3, do the splitting up of the images, and then encode the individual images back to bytes for saving as valid images. The encode/decode process is a little tricky.

Working in 0.4


Last "realm-cocoa" version incorrect on Release Notes

Hi all!
Looking at the last Release Notes, the last version number is v5.5.1
(7ec5df0) when the previous version was  v10.7.2 (ae8e646).
I'm not aware of the project but from what I've seen on https://github.com/realm/realm-cocoa/commit/7ec5df0a700ef76ad930dcedb9c63c1b354979e1 this seems like a kind of limitation on publishing new versions. If so I suggest adding a note in the beginning of the text and explaining which real version it corresponds to.
Thanks,
Ricardo Barroso

@RicardoBarroso Thanks for your feedback, we will keep it in mind. v5.5.1 was a back-ported release that addressed a few issues. v10.7.2 is what you should use if you are developing with Realm from now on. If that is all, would you mind closing the issue? Thanks!


concat function

The TOSCA specification says that The concat function is used to concatenate two or more string values within a TOSCA service template.
For the following service template
tosca_definitions_version: tosca_simple_yaml_1_3
node_types:
  MySoftware:
    derived_from: tosca.nodes.SoftwareComponent
    capabilities:
      endpoint:
        type: tosca.capabilities.Endpoint
topology_template:
  node_templates:
    compute:
      type: tosca.nodes.Compute
      attributes:
        public_address: my.compute.com
    software:
      type: MySoftware
      capabilities:
        endpoint:
          properties:
            protocol: http
            port: 3000
            url_path: api/v1/software
      requirements:
        - host: compute
  outputs:
    my_software_endpoint_url:
      type: string
      value:
        concat:
          - get_property: [software, endpoint, protocol]
          - "://"
          - get_attribute: [compute, public_address]
          - ":"
          - get_property: [software, endpoint, port]
          - "/"
          - get_property: [software, endpoint, url_path]

one could expect that the value of the my_software_endpoint_url output will be http://my.compute.com:3000/api/v1/software.
But here, the 5th parameter of the concat function is not a string but a PortDef integer.
Processing this service template with different TOSCA parsers produces different behaviors:

No error with Puccini
No error with Ubicity Validator after removing the line type: string else one parsing error
No error with xOpera parser but one runtime exception when trying to get the outputs after deploying the template
One typing error (i.e. the 5th parameter is not a string) with Cloudnet TOSCA toolbox

So the given service template is not portable to various TOSCA implementations.
Then the specification of the TOSCA concat function should be improved to clearly define that:

each parameter SHALL BE of type string XOR each parameter SHALL BE convertible to a string, e.g. a PortDef integer could be stringified
if convertible, which types can be convertible to a string? Is a complex data type convertible?
what happens if a parameter refers to an unset attribute/property? Is it a parsing error? is it a runtime error? Does the parameter set to an empty string? other behavior?

Any opinions?

The Ubicity orchestrator incorrectly flagged the “type” keyword in the output definition as an error. We have fixed this in the latest version.
You are correct that the spec needs to clearly define whether types other than strings can be used in concat (and other) functions.

You are correct that the spec needs to clearly define whether types other than strings can be used in concat (and other) functions.

I propose that at least YAML Types (string, integer, float, boolean, timestamp), TOSCA version, and TOSCA scalar-unit types could be used in concat functions.  Other types (null, range, list, map, complex data type) could be also used but it will be needed to define precisely how they are stringified.

As I stated elsewhere, I think TOSCA should treat functions like dynamic languages (Python, Ruby, JavaScript) do. That is: arguments can be of any type and return values can be of any type. This allows functions to have their own special semantics. For example, a function can return one type in one circumstance and another type in another circumstance. get_property indeed works that way.
Still, we do need to make sure that internal functions are properly documented. I agree with @philippemerle that allowing the stringification of primitive types is a good idea, but even that has to be documented. For example, there is no one way to stringify floats or even large integers (exponential format). Complex type stringification is too complex, I propose not supporting that.

On second thought, I would like to make another point -- I don't think TOSCA parsers should check the return type or value at all during design-time validation at all, even for a "static" function like get_property (indeed, as you noticed Puccini does not normally test for this, unless you specifically ask to --coerce functions). The reason is that even if the semantics of a function (like built-in functions) is well known, at best we can test for the general type. But because we might not have the value itself until runtime (get_attribute) then we can't check if the value adheres to other constraints (e.g. max_length). So, I would say that whatever value you get from such design-time validation is quite limited and provides not a lot of confidence.
And the implementation could be complex -- because functions can be nested, you would have to mark any expression that has get_attribute at any level of its nesting as "can't validate its value". If we add support for custom functions, too, we would have to add some way to mark them as either "dynamic" (like get_attribute) or "static" (like concat) for this purpose. I don't think this added complexity is worth the limited benefits.
My design principle with Puccini is that anytime a user uses a function it essentially cannot be validated until deployment time, even for seemingly "static" functions. Yes, I know I advocate strongly for putting as much design-time validation as possible in TOSCA, but even I try to choose my battles carefully. :)

Ubicity checks whether the return types of a function is compatible with the type of the property for which it is defined as the value. It handles nested functions, and it also flags cases where a function value for a mandatory property references an optional value.

That's great, but the question is whether we want to standardize this behavior. The cost can be very significant. For Puccini it would mean that for every function (including custom functions) there would need be both the regular function, as well as a special "validation function" path that calculates the return type. As I stated before, the usefulness of this return type validation is rather limited -- without an actual value we can't validate whether it would adhere to constraints on that type.
Having to add this companion function to every function for the rather limited usefulness of having a strictly primitive return type seems like far too much of a cost. Even if this were standardized in TOSCA I would not implement it. To be clear, the errors would appear in Puccini -- but only when functions are explicitly called, which happens during Day 1 and 2, not during Day 0 (unless specifically enforced with the --coerce argument, which of course cannot handle get_attribute calls very meaningfully beyond their default values).

I’m not suggesting we should standardize this. However, when we revisit the discussion about custom functions, we should discuss whether these custom functions should define their return type (my vote would likely be yes).

My vote would be no because I would like custom functions to have the same heuristic freedom as the built-in functions, e.g. get_attribute having a different return type depending on the attribute. I can see custom functions as a way to plug in custom graph traversal languages, not just for the TOSCA topology, but also for various embedded or external data sources.
As stated before, I would like TOSCA function to work like functions in dynamic languages (Python, Ruby, JavaScript, etc.). The function has a name. The function has a variable number of arguments. The function returns a single value, which can be of any type. This is a very familiar calling mechanism that would be easily understood by users.

Ubicity checks whether the return types of a function is compatible with the type of the property for which it is defined as the value. It handles nested functions, and it also flags cases where a function value for a mandatory property references an optional value.

Cloudnet TOSCA toolbox does the same checks.


Missing user_id in SendEvent

src/GA4.php
Forgetting to make use of the userId set on line 47...
public function sendEvent(array $eventData): array
    {
        if (! $this->clientId && ! $this->clientId = session(config('ga4-event-tracking.client_id_session_key'))) {
            throw new MissingClientIdException;
        }

        $this->validateEvent($eventData);

        $response = Http::withOptions([
            'query' => [
                'measurement_id' => config('ga4-event-tracking.measurement_id'),
                'api_secret' => config('ga4-event-tracking.api_secret'),
            ],
        ])->post($this->getRequestUrl(), [
            'client_id' => $this->clientId,
            'events' => [$eventData],
        ]);

        if ($this->debugging) {
            return $response->json();
        }

        return [
            'status' => $response->successful(),
        ];
    }

Line 78 should get updated to...
        ])->post($this->getRequestUrl(), [
            'client_id' => $this->clientId,
            'user_id' => $this->userId,
            'events' => [$eventData],
        ]);

Lemme know if you need a PR or can just fix it yerself...

Hello @bcbud is this package working for you? or maybe you went with an alternative? this seems to be based on https://github.com/protonemedia/laravel-analytics-event-tracking

@accexs @bcbud I ended up forking this package myself to resolve several small issues in this package, @accexs's fork, and the original package.
See https://github.com/devproca/laravel-ga4-event-tracking