Makes the game crash

Installed and everything worked fine (honestly it worked great!), but then when the last person left the dedicated server, the game crashed with the following description:
"Exception in server tick loop"
At the same time (seconds after) it also created another crash-report with description:
Watching Server
java.lang.Error: Watchdog
at net.minecraft.class_3178.run(class_3178.java:52)
at java.lang.Thread.run(Thread.java:748)
Both said this:
net.dv8tion.jda.api.exceptions.MissingAccessException: Cannot perform action due to a lack of Permission. Missing permission: VIEW_CHANNEL
at net.dv8tion.jda.internal.entities.AbstractChannelImpl.checkAccess(AbstractChannelImpl.java:307)
at net.dv8tion.jda.internal.entities.AbstractChannelImpl.checkPermission(AbstractChannelImpl.java:316)
at net.dv8tion.jda.internal.entities.AbstractChannelImpl.checkPermission(AbstractChannelImpl.java:313)
at net.dv8tion.jda.internal.entities.TextChannelImpl.sendMessage(TextChannelImpl.java:353)
at fr.arthurbambou.fdlink.discordstuff.DiscordBot.sendToLogChannels(DiscordBot.java:315)
at fr.arthurbambou.fdlink.discordstuff.DiscordBot.sendToLogChannels(DiscordBot.java:294)
at fr.arthurbambou.fdlink.discordstuff.DiscordBot.sendMessage(DiscordBot.java:267)
at fr.arthurbambou.fdlink.FDLink1_16.handleText(FDLink1_16.java:69)
at net.minecraft.server.MinecraftServer.handler$zik000$sendMessage(MinecraftServer.java:3712)
at net.minecraft.server.MinecraftServer.method_9203(MinecraftServer.java)
at net.minecraft.class_3324.method_14616(class_3324.java:810)
at net.minecraft.class_3244.method_10839(class_3244.java:1114)
at net.minecraft.class_2535.method_10768(class_2535.java:396)
at net.minecraft.class_3242.method_14357(class_3242.java:186)
at net.minecraft.server.MinecraftServer.method_3813(MinecraftServer.java:882)
at net.minecraft.class_3176.method_3813(class_3176.java:312)
at net.minecraft.server.MinecraftServer.method_3748(MinecraftServer.java:811)
at net.minecraft.server.MinecraftServer.method_29741(MinecraftServer.java:670)
at net.minecraft.server.MinecraftServer.method_29739(MinecraftServer.java:257)
at java.lang.Thread.run(Thread.java:748)
Now when I open the server back up, it loads and after loading advancements, it says the same problem with "Exception in server tick loop" and the server wont start...
Now the crash reports are telling me to "try our sister game, Minceraft!"
If you can help it would be appreciated :)

UPDATE: I had hidden my log channel in the server and the bot could not access it. This made the game crash. It no longer crashes after I give the bot permissions: To avoid this, i probably could have given the bot administrator permissions, but i just gave it relevant permissions in the specific hidden discord channel

so the issue is resolved?


feat: add underlay feature of data

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

Comparison is base (5973c54) 6.17% compared to head (92230b0) 6.16%.
Report is 77 commits behind head on main.

Files
Patch %
Lines

packages/board/src/lib/viewer.ts
0.00%
20 Missing and 3 partials :warning:

packages/renderer/src/draw/underlay.ts
0.00%
6 Missing and 1 partial :warning:

packages/renderer/src/index.ts
0.00%
2 Missing and 1 partial :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff            @@
##            main    #266      +/-   ##
========================================
- Coverage   6.17%   6.16%   -0.02%
========================================
  Files         76      77       +1
  Lines       4403    4415      +12
  Branches     871     873       +2
========================================
  Hits         272     272
- Misses      3289    3299      +10
- Partials     842     844       +2

Flag
Coverage Δ

unittests
6.16% <0.00%> (-0.02%)
:arrow_down:

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

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


proposal: x/crypto/acme/autocert: add mechanism for providing a private key for a new certificate

Autocert currently generates a private key when there is no valid certificate in the cache and a certificate is requested.
I would like the ability to provide the private key for a certificate when it is requested for the first time.
Current prototype:  https://github.com/mjl-/autocert/commit/2f3f1cee58be111786546ecde8b55eaf981718da
I can look into making a CL for this change.
My use case: I am writing a mail server. The incoming SMTP server offers TLS with STARTTLS. Historically there has been no validation of TLS certificates in that situation. Two new opt-in mechanisms now exist: 1. MTA-STS, which requires common-CA-validation (which I already support); 2. DANE, which requires validation against a public key in DNS (in a TLSA record, protected with DNSSEC). When a new domain is set up in my mail server, I plan to generate a private key, tell the user the DANE TLSA record to add to their DNS (after which I cannot easily get a user to change it, especially with rollover), and request a certificate through ACME for the key. This approach should allow validation with both MTA-STS and DANE.
While making the change, I found that autocert appears to reuse private keys for renewals when a valid certificate is present in the cache. Generating a new private key seems like a safer default. TestRenewFromCacheAlreadyRenewed in renewal_test.go has checks about a new private key, but only in the context of another process already having placed a new certificate with new private key in the cache. It does not check if a new certificate with a new private key was requested. The test may be better off checking if the entire certificate from the updated cache is returned.
When an expired certificate is in the cache, it seems to be ignored and its private key not reused for the newly requested certificate. I don't know if the difference in behaviour around private key reuse for expired-and-renewed and preemptive-renewal is intentional, but I found it a bit surprising.

CC @FiloSottile @rolandshoemaker @golang/security
(Copied from an earlier issue for autocert, not sure if I should be doing this or it should be triaged by someone from the Go team)


[Feature Request] Make five minutes auto update feature configurable (allow enable/disable by user)

I'd love to see the new https://github.com/gluap/pyduofern-hacs/releases/tag/v0.4.1 Add a low-key auto update by letting the devices schedule an update themselves every five minutes when duofern asks for their state feature a configurable one.
Maybe by using two services to enable/disable it:

duofern.enable_constant_state_check
duofern.disable_constant_state_check

This (or any other) way users can benefit from other changes in the newer versions and specifically decide on their own if they prefer to use this feature or not (and e. g. use the duofern.ask_for_update service along with certain entities in case states are not reported reliably).
I fear constant RF noise as I'm using duoFern with plenty of devices. Being able to enable and disable the above mentioned feature would also allow me to check if it really solves the randomly missing states issue.

(Initial thoughts: https://github.com/gluap/pyduofern-hacs/issues/24#issuecomment-1423775805)

don't know if it is related to the new 0.4.1 version or not. But since yesterday I sometimes get Unknown msg in my logs:
Logger: /usr/local/lib/python3.10/site-packages/pyduofern/duofern.py
Source: /usr/local/lib/python3.10/site-packages/pyduofern/duofern.py:709
First occurred: 07:58:13 (7 occurrences)
Last logged: 09:26:41
Unknown msg: 0000407f0e6f12340181000000000000000000000000
Unknown msg: 6f123401810000000000000000000000000000000000
Unknown msg:<PHONE_NUMBER>00407f0e6f123401810000000000000000
Unknown msg: 00407f0e6f1234018100000000000000000000000000
Unknown msg:<PHONE_NUMBER>004100120000407f0e6f12340181000000
I only have 1 Rademacher RolloTron Standard DuoFern 1400 and 1 Rademacher Sonnensensor 9478.
Maybe the solar sensor internal battery is recharged again with rescent sunny days and the threshold is reached for sun on/off.
Is there a decryption tool somewhere to decode the duofern's msg's ?
Is above a bug, it looks like the message contains the same codes, but is shifted left or right.

Please check the other issues or create a separate issue as this is not related to this feature request at all.

I'd love to see the new https://github.com/gluap/pyduofern-hacs/releases/tag/v0.4.1 Add a low-key auto update by letting the devices schedule an update themselves every five minutes when duofern asks for their state feature a configurable one.
Maybe by using two services to enable/disable it:

duofern.enable_constant_state_check

duofern.disable_constant_state_check

This (or any other) way users can benefit from other changes in the newer versions and specifically decide on their own if they prefer to use this feature or not (and e. g. use the duofern.ask_for_update service along with certain entities in case states are not reported reliably).

I fear constant RF noise as I'm using duoFern with plenty of devices. Being able to enable and disable the above mentioned feature would also allow me to check if it really solves the randomly missing states issue.

(Initial thoughts: https://github.com/gluap/pyduofern-hacs/issues/24#issuecomment-1423775805)

Did you think about this @gluap  ?

@bcutter
I've thought about this and looked at whether it could be easily enabled/disabled via service. So if it indeed is troublesome we could make it configurable. But with that beta out for a month now without substantial reports about interference I guess it's not an issue after all?

Depends on how many downloads that version has since than. For me e. g. I'm not even on that version yet.
I would really really like to be able to have control over this and continue testing all new (beta) versions.
Once you have more than a dozen DuoFern devices, RF noise starts to be a thing... 😀

The messages take about 0.007 seconds to send (at least that's what I see using rtl-sdr to analyze the RF communication) . So I'd think you would need way more than 12 devices for an update for every device every 5 minutes to cause issues. Of course there will be correlation and re-sent messages occasionally, but even assuming a generous 15 messages a device update should not take more than 1/10 of a second of airtime. So for a dozen of devices you would be at 2 seconds and the 15 messages are a gross overstatement, normally 2-3 should suffice.
I'm willing to implement this, but with no issues reported with the autoupdating so far I suspect that it may have worked for its intended purpose. And purely for analyzing whether it did I see the following as a possible workaround that would require no extra debug function for toggling the update-request functionality to be implemented:
The comparison between "using 5 minute auto update" and "not using 5 minute auto update" can be done by switching between 0.4.0 and 0.4.3 (or "latest" if you feel adventurous for that matter).

Switching between releases always needs a HA Core restart - using a service would not... ;-)
Did I get this wrong maybe? On a random basis every device sends its status every 5 minutes.
For ten devices:

Without 5 minutes auto update: zero times a day if no commands are sent or received

With 5 minutes auto update: 2.880 updates a day (that's what's in my head when using the word "RF noise")

When I started to use the cover.stop_cover service to specifically trigger an update of a single device, after a time I knew (when and) which devices need more "care" while others update quite reliable.
Hammering every five minutes when not needed just feels like it's not the perfect or smartest approach to fix the randomly missing device status updates. As I still don't have a better idea the only thing I ask for is why not providing users the option to decide if they need/want this feature.

What's the downside of giving this control?
What about a second config option on the interval (if I want 15 or 60 or 3 (or 0) minutes instead of the hard coded 5)?

The downside is that it will take about 2-3 hours of work on my side - which competes with different projects and family duties on my side. And I have yet to see an argument that "not having this control" poses any problem beyond "I feel that 2880 is a large number".
I would phrase it this way:
Realistically there will be 3 messages per device every 5 minutes, so 6 seconds of radio frequency transmission per device per day. 6 seconds sounds very small to me and unless these 6 seconds really are problematic I don't see why it needs to be toggleable.

I understand the time resource part. Really.
I (and I'm not the only one, see linked comment) simply don't like this solution (workaround) for the initial problem (missing device status updates) as it is neither smart nor efficient - it's the hammer method.
My former automation based device status update already was "smarter" as it only forced status updates when there's a medium to high chance the device status has actually been changed (and might be missed) taking sensors into account.
The "5 minutes auto update setting" just blindly sends the status, independently of a status change.

"Hey, I'm (still) opened|closed." (Yes, I know)
"Hey, I'm (still) opened|closed." (Yes, I know)
"Hey, I'm (still) opened|closed." (Yes, I know)
Me too.
Me too.
Me too.
Me also.
Me also.
Me also.
So am I.
So am I.
So am I.
...

If I miss one status update for one device a day (which I don't according to my long-term log on that issue), why should we stoically send 3 messages for every device every 5 minutes all day.
There might be scenarios where 5 minutes are way to often and there might even be some where a guaranteed instant update is needed so 5 minutes are too rare.
As long as we can't find a smarter approach for the core issue, this still just sounds like a classic setting which should be user configurable.
As discussion seems to not make fundamental progress (two opinions and the dev in the need overrules all other opinions 😃), maybe you can quickly elaborate

why every 5 minutes should be the sweet spot working for everyone
if you had/have any other ideas in mind to work around the core issue (infrequent missing device status updates) we could discuss

E. g. what about drastically resending the device status once an actual state happens? Can we discover this? Like "device status changed --> send new status 10 times within 30 seconds". That would be much more tailored to the initial problem, wouldn't it?

As I said: Feel free to open a PR about this. I'm not opposed to the feature.

So

"some preapration to allow setting the auto update timeout later." in https://github.com/gluap/pyduofern-hacs/releases/tag/v0.4.3 is still valid?
I understood https://github.com/gluap/pyduofern-hacs/issues/27 right that all that noise was wiped out of the logs (still exists but is simply ignored now)?

Just catching up the latest releases and stumbled over those two things as direct impact of the auto update feature.

1.) doing the preparation made me realize the amount of work required to do it proper and lie the project aside because of that.
2.) yes. Because it seems people get stuck up on log messages instead of reporting whether their blinds move which I fail to understand. I would love to keep a lot more logs but half the issues I get are "there's a log message and homeassistant presents it like it shouldn't be there". Even if the event is harmless that causes a lot of work. Reducing verbosity seems to be the only way to make people focus on their blinds.

This was implemented in 0.5.x


[FR] move categories and stock locations into the main menu (UI Improvement)

Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find a similar feature request

Problem statement
For quickly navigating a rather large parts list the quick-access menu with a list of categories (in Parts view) and stock locations (in Stock view) is already super helpful. Unfortunately you cannot make that menu stay reachable when scrolling right now - which would be another productivity boost for heavy use of the UI.
The menu currently:

Suggested solution
Since the main menu can be made sticky in the settings, why not move these quick-access menus there as well as drop downs?
Imagine it like this:

The breadcrumb-links next to the current quick menu (or more precisely "current path"-links) could stay as they are, just without the menu icon...
I could contribute that, in case there is support for that change. I think this could make the UI a little more accessible/consistent - but that could also just be my personal view. In other words: comments appreciated!
Describe alternatives you've considered
.
Examples of other systems
No response
Do you want to develop this?

[X] I want to develop this.

I like the idea, especially because it removes layout shifts. Interested in other perspectives.


sigh: Couldn't extend enterprise provisioning profiles anymore

Issue Description
We use the fastlane toolchain in our company to build some enterprise apps.
First of all, thanks for the great toolchain, saved us a lot of hours! :+1:
But since yesterday we have a problem with sigh:
We have used this tool with the parameter force:true, so that existing provisioningProfiles will be extended with every new build, to have a maximum of one year expiration time for this app.
Unfortunately, this workflow broke yesterday, see output from sigh:
"resultCode"=>8331, "resultString"=>"In House distribution provisioning profiles for this account are not yet available. Within two weeks of your program activation this will be available to you."
Complete output when running fastlane, including the stack trace and command used
+-------------------------------------+------------------------------------------------------+
|                                   Summary for sigh 1.4.0                                   |
+-------------------------------------+------------------------------------------------------+
| username                            | jenxxx@xxxxxxxxxx                                    |
| provisioning_name                   | Kxxxxxxxxxxxxxxxxxxxxxxxxxx                          |
| app_identifier                      | de.xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx                |
| cert_id                             | T8xxxxxxxxx                                          |
| adhoc                               | false                                                |
| skip_install                        | false                                                |
| development                         | false                                                |
| force                               | true                                                 |
| ignore_profiles_with_different_name | false                                                |
| skip_fetch_profiles                 | false                                                |
| skip_certificate_verification       | false                                                |
+-------------------------------------+------------------------------------------------------+

[22:02:21]: Starting login with user 'jenxxx@xxxxxxxxx'
[22:02:27]: Successfully logged in
[22:02:27]: Fetching profiles...
[22:02:41]: Found 1 matching profile(s)
[22:02:41]: Updating the provisioning profile
[22:02:43]: Variable Dump:
[22:02:43]: {:DEFAULT_PLATFORM=>:ios, :PLATFORM_NAME=>:ios, :LANE_NAME=>"ios build", :VERSION_NUMBER=>"2.0.0"}
[22:02:43]: {"responseId"=>"11f0d606-c8f7-xxxx-9e4a-e38ba6565c13", "resultCode"=>8331, "resultString"=>"In House distribution provisioning profiles for this account are not yet available. Within two weeks of your program activation this will be available to you.", "userString"=>"In House distribution provisioning profiles for this account are not yet available. Within two weeks of your program activation this will be available to you.", "creationTimestamp"=>"2016-03-03T21:02:43Z", "protocolVersion"=>"QH65B2", "userLocale"=>"en_US", "requestUrl"=>"https://developer.apple.com/services-account/QH65B2/account/ios/profile/regenProvisioningProfile.action", "httpCode"=>200}

Configuration Files
Relevant sigh command:
  sigh(
    username: devMember_ID,
    force: true,
    provisioning_name: provProfile_name,
    app_identifier: bundle_identifier,
    cert_id: newest_certificate_ID,
    output_path: "/tmp"
  )

Environment
latest fastlane version: 1.65.0

Hi @alexmanzer Thanks for reporting. I think something is going wrong on Apple's side. Please see this forum post: https://forums.developer.apple.com/thread/40124 It seems like this same issue is happening to people using the dev portal since the upgrade yesterday.

Oh, I was not aware, that others have the same problems with their enterprise account.
Ok, let's wait for a Solution from Apple.
Thanks for investigation! 👍🏻


Double tooltips appear in TextField label

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Steps to reproduce 🕹
Link to live example:
Steps:

I forked https://mui.com/material-ui/react-text-field/#basic-textfield
And then, I added the Tooltip component to the TextField label prop.
I created a state value using useState for the tooltip open state.
Finally, I passed the props (open, onOpen, onClose) to Tooltip.

Current behavior 😯
Double Tooltip components appear.

Expected behavior 🤔
Only one Tooltip component appears.

Context 🔦
I'm trying to add a Tooltip to a label prop of the TextField. And I also want to control Tooltip open state manually.
Of course, if I don't add open prop to Tooltip, it works fine.
Your environment 🌎

npx @mui/envinfo
  Browser:
    Google Chrome Version 115.0.5790.98 (Official Build) (64-bit)
  System:
    OS: Windows 10 10.0.22621
  Binaries:
    Node: 18.16.0 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 9.5.1 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: Not Found
    Edge: Spartan (44.22621.1848.0), Chromium (114.0.1823.82)
  npmPackages:
    @emotion/react: latest => 11.11.1
    @emotion/styled: latest => 11.11.0
    @mui/base:  5.0.0-beta.8
    @mui/core-downloads-tracker:  5.14.1
    @mui/material: latest => 5.14.1
    @mui/private-theming:  5.13.7
    @mui/styled-engine:  5.13.2
    @mui/system:  5.14.1
    @mui/types:  7.2.4
    @mui/utils:  5.14.1
    @types/react:  18.2.15
    react: latest => 18.2.0
    react-dom: latest => 18.2.0
    typescript:  5.1.6

This is codesandbox url: https://codesandbox.io/s/tender-panka-wgdhp3?file=/Demo.js

@Pluto0104 For an outlined Textfield, the label prop is only used for internal layout, the actual label component is InputLabel, which cannot be customized directly in a TextField
For your case, you could compose your own TextField like this:
<FormControl>
  <Tooltip>
    <label htmlFor="component-outlined">Name</label>
  </Tooltip>
  <OutlinedInput
    id="component-outlined"
    defaultValue="Composed TextField"
    label="Name"
  />
</FormControl>

Material UI's TextField is composed of these same components (with the exception of the custom label), refer to this part of the  docs for more details: https://mui.com/material-ui/react-text-field/#components

Thanks for your answer. @mj12albert


it work after manual loading with sudo yabai --load-sa when every reboot, and can it auto load?

it work after manual loading with sudo yabai --load-sa when every reboot, and can it auto load?

https://github.com/koekeishiya/yabai/wiki/Installing-yabai-(latest-release)

thank you! @koekeishiya


TestPipeline parameter should be removed from the template ci.yml

We already have a few instances of partners copying the template without realizing the parameter should be removed: https://github.com/Azure/azure-sdk-for-net/search?l=YAML&q=TestPipeline
I think it can be auto-calculated based on the template service name.
cc @chidozieononiwu @weshaggard @benbp

auto-calculating parameter values does not work for yaml. Perhaps we could use add a comment indicating that it should be removed when used in a not template pipeline.

auto-calculating parameter values does not work for yaml. Perhaps we could use add a comment indicating that it should be removed when used in a not template pipeline.

Can we base this condition on the artifact name?

Can we base this condition on the artifact name?

Can we base this condition on the artifact name? Or ServiceDirectory?

Yes we can. But we also need it for here

Can we base this condition on the artifact name? Or ServiceDirectory?

Yes we can. But we also need it for here

Let's keep it open until we fix occurrences in the C# repo

Let's keep it open until we fix occurrences in the C# repo


Updating Default value to return single submitted value where fieldWi…

fix Issue #109
Update to return single value if not multi submit field

Thank you, @BarryGibson 👍 I'm working on a new release which should be out shortly and will include this 😄


Roadmap

[x] Working prototype
[x] More examples (your ideas are very welcome)
[x] Support different types of blur: light, extra light and dark

The Apache Indians

The Apache Indians were associated with the label "Shaman" basically this is what pop out after the has been an overwhelming injustices of acta against them typically woman mothers because they have no one to defend them and the wait on God enduring heartache. That once time has matured it's like a cycle begins to come back in the direction it began its an eye opening awakening experience. This rare gems used to be called witch doctor but basically they began to understand other peoples intentions around them.


Disable toggle switch when  is disabled

When a <fieldset> is disabled, the spec says that so should it'd descendent form elements.
from: https://developer.mozilla.org/en-US/docs/Web/HTML/Element/fieldset#attr-disabled

disabled
If this Boolean attribute is set, the form controls that are its descendants [...] are disabled

Is this an enhancement that could be made?

+1


[Feature] Change poll_interval from u64 to Duration

Component
provider, pubsub
Describe the feature you would like
this is mainly useful as duration:
https://github.com/alloy-rs/alloy/blob/main/crates/rpc-client/src/client.rs#L182-L183
returning this as duration makes it harder to mess up the u64 -> Duration::from_millis call
Additional context
No response

Same for set

I will take this.

exact scope is to change the return-type for the function, NOT to change the struct prop type


Removed extra c++ tag

The readme in conflicting, please compare it with the latest repository.

The readme in conflicting, please compare it with the latest repository.

Sure I'll check that


Allow Clone subclassing

See 2nd commit's details as I had to do a lot in that one commit.

Due to verbosity, should the Model's names be reduced by removing the TextArea part? For example:

StyledTextAreaModel should remain the same
StyleClassedTextAreaModel --> StyleClassedModel
CodeAreaModel --> CodeModel
InlineCssTextAreaModel --> InlineCssModel

Since this PR assumed that StyledTextAreaModel would be subclass-able and since it is clear that that isn't the best approach, I'm closing this PR.


CoinLedger Post Processor

Create a post processor for Coinledger
https://help.coinledger.io/en/articles/2584884-manual-import-guide
test with sycamore, and commercial api.

@pharr117 have time to chat about this tonight?


Clangd disagrees with clang-format on main header ordering

clang-format correctly sorts an implementation file's main header include first when the appropriate settings are set.
However, when formatting with clangd, the main include is sorted alphabetically with other includes.
Example:
$ touch .clang-format
$ printf '#include "a.hpp"\n#include "b.hpp"\n' > b.cpp
$ clang-format b.cpp
#include "b.hpp"
#include "a.hpp"

However, formatting with clangd (:fmt on Helix) not only leaves the a include first, but actually reorders it to appear first if formatting with clang-format.
This also doesn't work with IncludeBlocks: Regroup in .clang-format
System information
clangd --version:
clangd version 16.0.6
Features: linux
Platform: x86_64-pc-linux-gnu

clang-format --version:
clang-format version 16.0.6

Editor: Helix
Operating system: Arch Linux

Could you post clangd logs from a session where you open this example file and clangd formats it incorrectly?

These are the logs, oddly seem to be missing any actual action for the formatting. Also I noticed when formatting a range including the headers the faulty behaviour is not seen. Starting to think this might be a Helix issue.
I[09:31:10.616] clangd version 16.0.6
I[09:31:10.616] Features: linux
I[09:31:10.616] PID: 199243
I[09:31:10.616] Working directory: /home/emilylime/hi
I[09:31:10.616] argv[0]: /usr/bin/clangd
I[09:31:10.616] argv[1]: --function-arg-placeholders
I[09:31:10.616] argv[2]: --completion-style=detailed
I[09:31:10.616] argv[3]: --clang-tidy
I[09:31:10.616] argv[4]: --log=verbose
V[09:31:10.616] User config file is /home/emilylime/.config/clangd/config.yaml
I[09:31:10.616] Starting LSP over stdin/stdout
V[09:31:10.616] <<< {"id":0,"jsonrpc":"2.0","method":"initialize","params":{"capabilities":{"general":{"positionEncodings":["utf-8","utf-32","utf-16"]},"textDocument":{"codeAction":{"codeActionLiteralSupport":{"codeActionKind":{"valueSet":["","quickfix","refactor","refactor.extract","refactor.inline","refactor.rewrite","source","source.organizeImports"]}},"dataSupport":true,"disabledSupport":true,"isPreferredSupport":true,"resolveSupport":{"properties":["edit","command"]}},"completion":{"completionItem":{"deprecatedSupport":true,"insertReplaceSupport":true,"resolveSupport":{"properties":["documentation","detail","additionalTextEdits"]},"snippetSupport":true,"tagSupport":{"valueSet":[1]}},"completionItemKind":{}},"hover":{"contentFormat":["markdown"]},"inlayHint":{"dynamicRegistration":false},"publishDiagnostics":{"versionSupport":true},"rename":{"dynamicRegistration":false,"honorsChangeAnnotations":false,"prepareSupport":true},"signatureHelp":{"signatureInformation":{"activeParameterSupport":true,"documentationFormat":["markdown"],"parameterInformation":{"labelOffsetSupport":true}}}},"window":{"workDoneProgress":true},"workspace":{"applyEdit":true,"configuration":true,"didChangeConfiguration":{"dynamicRegistration":false},"didChangeWatchedFiles":{"dynamicRegistration":true,"relativePatternSupport":false},"executeCommand":{"dynamicRegistration":false},"fileOperations":{"didRename":true,"willRename":true},"inlayHint":{"refreshSupport":false},"symbol":{"dynamicRegistration":false},"workspaceEdit":{"documentChanges":true,"failureHandling":"abort","normalizesLineEndings":false,"resourceOperations":["create","rename","delete"]},"workspaceFolders":true}},"clientInfo":{"name":"helix","version":"23.10 (dbac78bb)"},"processId":199232,"rootPath":"/home/emilylime","rootUri":"file:///home/emilylime","workspaceFolders":[{"name":"emilylime","uri":"file:///home/emilylime"}]}}

I[09:31:10.616] <-- initialize(0)
I[09:31:10.617] --> reply:initialize(0) 0 ms
V[09:31:10.617] >>> {"id":0,"jsonrpc":"2.0","result":{"capabilities":{"astProvider":true,"callHierarchyProvider":true,"clangdInlayHintsProvider":true,"codeActionProvider":{"codeActionKinds":["quickfix","refactor","info"]},"compilationDatabase":{"automaticReload":true},"completionProvider":{"resolveProvider":false,"triggerCharacters":[".","<",">",":","\"","/","*"]},"declarationProvider":true,"definitionProvider":true,"documentFormattingProvider":true,"documentHighlightProvider":true,"documentLinkProvider":{"resolveProvider":false},"documentOnTypeFormattingProvider":{"firstTriggerCharacter":"\n","moreTriggerCharacter":[]},"documentRangeFormattingProvider":true,"documentSymbolProvider":true,"executeCommandProvider":{"commands":["clangd.applyFix","clangd.applyTweak"]},"foldingRangeProvider":true,"hoverProvider":true,"implementationProvider":true,"inlayHintProvider":true,"memoryUsageProvider":true,"referencesProvider":true,"renameProvider":{"prepareProvider":true},"selectionRangeProvider":true,"semanticTokensProvider":{"full":{"delta":true},"legend":{"tokenModifiers":["declaration","definition","deprecated","deduced","readonly","static","abstract","virtual","dependentName","defaultLibrary","usedAsMutableReference","usedAsMutablePointer","constructorOrDestructor","userDefined","functionScope","classScope","fileScope","globalScope"],"tokenTypes":["variable","variable","parameter","function","method","function","property","variable","class","interface","enum","enumMember","type","type","unknown","namespace","typeParameter","concept","type","macro","modifier","operator","comment"]},"range":false},"signatureHelpProvider":{"triggerCharacters":["(",")","{","}","<",">",","]},"standardTypeHierarchyProvider":true,"textDocumentSync":{"change":2,"openClose":true,"save":true},"typeDefinitionProvider":true,"typeHierarchyProvider":true,"workspaceSymbolProvider":true},"serverInfo":{"name":"clangd","version":"clangd version 16.0.6 linux x86_64-pc-linux-gnu"}}}

V[09:31:10.617] <<< {"jsonrpc":"2.0","method":"initialized","params":{}}

I[09:31:10.617] <-- initialized
V[09:31:10.618] <<< {"jsonrpc":"2.0","method":"textDocument/didOpen","params":{"textDocument":{"languageId":"cpp","text":"#include \"b.hpp\"\n#include \"a.hpp\"\n","uri":"file:///home/emilylime/hi/b.cpp","version":0}}}

I[09:31:10.618] <-- textDocument/didOpen
V[09:31:10.619] config note at /home/emilylime/.config/clangd/config.yaml:1:0: Parsing config fragment
I[09:31:10.619] config warning at /home/emilylime/.config/clangd/config.yaml:9:2: Unknown InlayHints key 'BlockEnd'
V[09:31:10.619] config note at /home/emilylime/.config/clangd/config.yaml:1:0: Parsed 1 fragments from file
V[09:31:10.619] Config fragment: compiling /home/emilylime/.config/clangd/config.yaml:1 -> 0x0000726588002910 (trusted=true)
I[09:31:10.619] --> textDocument/publishDiagnostics
V[09:31:10.619] >>> {"jsonrpc":"2.0","method":"textDocument/publishDiagnostics","params":{"diagnostics":[{"message":"Unknown InlayHints key 'BlockEnd'","range":{"end":{"character":10,"line":8},"start":{"character":2,"line":8}},"severity":2,"source":"clangd-config"}],"uri":"file:///home/emilylime/.config/clangd/config.yaml"}}

I[09:31:10.619] Failed to find compilation database for /home/emilylime/hi/b.cpp
I[09:31:10.619] ASTWorker building file /home/emilylime/hi/b.cpp version 0 with command clangd fallback
[/home/emilylime/hi]
/usr/bin/clang -std=c++20 -Wall -Wextra -Wpedantic -Weverything -Wno-c++98-compat -Wno-c++98-compat-pedantic -resource-dir=/usr/lib/clang/16 -- /home/emilylime/hi/b.cpp
V[09:31:10.620] Driver produced command: cc1 -cc1 -triple x86_64-pc-linux-gnu -fsyntax-only -disable-free -clear-ast-before-backend -disable-llvm-verifier -discard-value-names -main-file-name b.cpp -mrelocation-model pic -pic-level 2 -pic-is-pie -mframe-pointer=all -fmath-errno -ffp-contract=on -fno-rounding-math -mconstructor-aliases -funwind-tables=2 -target-cpu x86-64 -tune-cpu generic -mllvm -treat-scalable-fixed-error-as-warning -debugger-tuning=gdb -fcoverage-compilation-dir=/home/emilylime/hi -resource-dir /usr/lib/clang/16 -internal-isystem /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../include/c++/13.2.1 -internal-isystem /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../include/c++/13.2.1/x86_64-pc-linux-gnu -internal-isystem /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../include/c++/13.2.1/backward -internal-isystem /usr/lib/clang/16/include -internal-isystem /usr/local/include -internal-isystem /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../x86_64-pc-linux-gnu/include -internal-externc-isystem /include -internal-externc-isystem /usr/include -Wall -Wextra -Wpedantic -Weverything -Wno-c++98-compat -Wno-c++98-compat-pedantic -std=c++20 -fdeprecated-macro -fdebug-compilation-dir=/home/emilylime/hi -ferror-limit 19 -stack-protector 2 -fgnuc-version=4.2.1 -fno-implicit-modules -fcxx-exceptions -fexceptions -no-round-trip-args -faddrsig -D__GCC_HAVE_DWARF2_CFI_ASM=1 -x c++ /home/emilylime/hi/b.cpp
V[09:31:10.620] Building first preamble for /home/emilylime/hi/b.cpp version 0
V[09:31:10.624] indexed preamble AST for /home/emilylime/hi/b.cpp version 0:
  symbol slab: 0 symbols, 120 bytes
  ref slab: 0 symbols, 0 refs, 128 bytes
  relations slab: 0 relations, 24 bytes
I[09:31:10.624] Built preamble of size 217552 for file /home/emilylime/hi/b.cpp version 0 in 0.00 seconds
I[09:31:10.625] Indexing c++20 standard library in the context of /home/emilylime/hi/b.cpp
V[09:31:10.629] indexed file AST for /home/emilylime/hi/b.cpp version 0:
  symbol slab: 0 symbols, 120 bytes
  ref slab: 0 symbols, 0 refs, 128 bytes
  relations slab: 0 relations, 24 bytes
V[09:31:10.629] Build dynamic index for main-file symbols with estimated memory usage of 248 bytes
I[09:31:10.629] --> textDocument/publishDiagnostics
V[09:31:10.629] >>> {"jsonrpc":"2.0","method":"textDocument/publishDiagnostics","params":{"diagnostics":[{"code":"pp_file_not_found","message":"'b.hpp' file not found","range":{"end":{"character":16,"line":0},"start":{"character":9,"line":0}},"severity":1,"source":"clang"}],"uri":"file:///home/emilylime/hi/b.cpp","version":0}}

V[09:31:10.826] <<< {"id":1,"jsonrpc":"2.0","method":"textDocument/inlayHint","params":{"range":{"end":{"character":0,"line":2},"start":{"character":0,"line":0}},"textDocument":{"uri":"file:///home/emilylime/hi/b.cpp"}}}

I[09:31:10.826] <-- textDocument/inlayHint(1)
V[09:31:10.826] ASTWorker running InlayHints on version 0 of /home/emilylime/hi/b.cpp
I[09:31:10.826] --> reply:textDocument/inlayHint(1) 0 ms
V[09:31:10.826] >>> {"id":1,"jsonrpc":"2.0","result":[]}

I[09:31:12.102] Indexed c++20 standard library: 14543 symbols, 3000 filtered
V[09:31:12.130] Build dynamic index for header symbols with estimated memory usage of 8542740 bytes
V[09:31:12.622] <<< {"jsonrpc":"2.0","method":"textDocument/didChange","params":{"contentChanges":[{"range":{"end":{"character":0,"line":1},"start":{"character":0,"line":0}},"text":""},{"range":{"end":{"character":0,"line":1},"start":{"character":0,"line":1}},"text":"#include \"b.hpp\"\n"}],"textDocument":{"uri":"file:///home/emilylime/hi/b.cpp","version":1}}}

I[09:31:12.622] <-- textDocument/didChange
I[09:31:12.673] Failed to find compilation database for /home/emilylime/hi/b.cpp
I[09:31:12.673] ASTWorker building file /home/emilylime/hi/b.cpp version 1 with command clangd fallback
[/home/emilylime/hi]
/usr/bin/clang -std=c++20 -Wall -Wextra -Wpedantic -Weverything -Wno-c++98-compat -Wno-c++98-compat-pedantic -resource-dir=/usr/lib/clang/16 -- /home/emilylime/hi/b.cpp
V[09:31:12.674] Driver produced command: cc1 -cc1 -triple x86_64-pc-linux-gnu -fsyntax-only -disable-free -clear-ast-before-backend -disable-llvm-verifier -discard-value-names -main-file-name b.cpp -mrelocation-model pic -pic-level 2 -pic-is-pie -mframe-pointer=all -fmath-errno -ffp-contract=on -fno-rounding-math -mconstructor-aliases -funwind-tables=2 -target-cpu x86-64 -tune-cpu generic -mllvm -treat-scalable-fixed-error-as-warning -debugger-tuning=gdb -fcoverage-compilation-dir=/home/emilylime/hi -resource-dir /usr/lib/clang/16 -internal-isystem /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../include/c++/13.2.1 -internal-isystem /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../include/c++/13.2.1/x86_64-pc-linux-gnu -internal-isystem /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../include/c++/13.2.1/backward -internal-isystem /usr/lib/clang/16/include -internal-isystem /usr/local/include -internal-isystem /usr/bin/../lib64/gcc/x86_64-pc-linux-gnu/13.2.1/../../../../x86_64-pc-linux-gnu/include -internal-externc-isystem /include -internal-externc-isystem /usr/include -Wall -Wextra -Wpedantic -Weverything -Wno-c++98-compat -Wno-c++98-compat-pedantic -std=c++20 -fdeprecated-macro -fdebug-compilation-dir=/home/emilylime/hi -ferror-limit 19 -stack-protector 2 -fgnuc-version=4.2.1 -fno-implicit-modules -fcxx-exceptions -fexceptions -no-round-trip-args -faddrsig -D__GCC_HAVE_DWARF2_CFI_ASM=1 -x c++ /home/emilylime/hi/b.cpp
V[09:31:12.674] Rebuilding invalidated preamble for /home/emilylime/hi/b.cpp version 1 (previous was version 0)
V[09:31:12.686] indexed preamble AST for /home/emilylime/hi/b.cpp version 1:
  symbol slab: 0 symbols, 120 bytes
  ref slab: 0 symbols, 0 refs, 128 bytes
  relations slab: 0 relations, 24 bytes
I[09:31:12.710] Built preamble of size 217552 for file /home/emilylime/hi/b.cpp version 1 in 0.04 seconds
V[09:31:12.713] indexed file AST for /home/emilylime/hi/b.cpp version 1:
  symbol slab: 0 symbols, 120 bytes
  ref slab: 0 symbols, 0 refs, 128 bytes
  relations slab: 0 relations, 24 bytes
V[09:31:12.713] Build dynamic index for main-file symbols with estimated memory usage of 248 bytes
I[09:31:12.713] --> textDocument/publishDiagnostics
V[09:31:12.713] >>> {"jsonrpc":"2.0","method":"textDocument/publishDiagnostics","params":{"diagnostics":[{"code":"pp_file_not_found","message":"'a.hpp' file not found","range":{"end":{"character":16,"line":0},"start":{"character":9,"line":0}},"severity":1,"source":"clang"}],"uri":"file:///home/emilylime/hi/b.cpp","version":1}}

V[09:31:15.582] <<< {"id":2,"jsonrpc":"2.0","method":"textDocument/inlayHint","params":{"range":{"end":{"character":0,"line":2},"start":{"character":0,"line":0}},"textDocument":{"uri":"file:///home/emilylime/hi/b.cpp"}}}

I[09:31:15.582] <-- textDocument/inlayHint(2)
V[09:31:15.582] ASTWorker running InlayHints on version 1 of /home/emilylime/hi/b.cpp
I[09:31:15.582] --> reply:textDocument/inlayHint(2) 0 ms
V[09:31:15.583] >>> {"id":2,"jsonrpc":"2.0","result":[]}

Yeah, if clangd were doing the formatting, I would expect to see textDocument/formatting in the logs.
So the most likely explanation is that your editor is configured to run some other formatter (like perhaps a different plugin) when the editor's format shortcut is invoked. In vscode, the plugin that handles formatting for a file type can be configured with "editor.defaultFormatter". I'm not familiar with helix but presumably it has some equivalent configuration option.


Update version and pypi hash

Checklist

[x] Used a personal fork of the feedstock to propose changes
~Bumped the build number (if the version is unchanged)~
[x] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Indeed, Niklas's github page is a 404 now. I e-mailed him.

Indeed, Niklas's github page is a 404 now. I e-mailed him.

He replied very quickly. The timescale for resolving this is not in our hands and the patch is time-sensitive (for the upcoming DPG), so for expediency I've simply removed him. I'll open an issue to add him back once this is resolved.


Match cache key to invalidate stale data

Re:  Issue #170
Appears that there was a mismatch between the key get and key delete.

I wonder if it's just as simple as this? The get/delete names don't match, so I'd expect that would cause some problems here at least.
Could not test due to time constraints - it appears the docs are out of date a bit and and the docker-compose.yml file is unmaintained (I'd be happy to bring the docker files up to date, if you think they'd be useful for anyone.)

LOL, it may well be @denning  - I must have been tired when adding that.
I'll try that now, and see if that resolves it.
Docker and docker compose
Yes, it would indeed be helpful to get the dockerfiles updated. I'll create an issue separately, as I spent a bit of time faffing around with this to get github actions working, and some of that work might by relevant. I'd really like to be able to run this with somethign like gitpod or github codespaces - that would bring down the barriers to entry substantially.
https://github.com/thegreenwebfoundation/admin-portal/blob/master/.github/workflows/run-tests.yml

Oh my. I think that was the issue was the reason. I've checked the naming convention on production and it was indeed missing the s. Thanks for this! I'm going to merge it
https://github.com/thegreenwebfoundation/admin-portal/issues/173


[stable/chartmuseum] fixed name of service account

What this PR does / why we need it:
There is a bug in the chart museum helm chart. There is a value Values.serviceAccount.name that allows you to specify the name of your service account. This is important because the name of the service account needs to be known for IRSA role mapping. However, the helm chart always defaults to {{ include "chartmuseum.fullname" . }}.
This PR solves this with the usual conditional logic for these values.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] DCO signed
[x] Chart Version bumped
[x] Title of the PR starts with chart name (e.g. [stable/mychartname])

/lgtm
thanks

/ok-to-test


Floating windows implementation idea

It's been a long time this feature #10121 was requested but I have an implementation idea.
I apologize for don't have the time to develop it and contribute with you guys, but I hope to contribute only with this suggestion.
The VSCode team says that it is hard to implement floating windows because vscode's Electron architecture and a huge refactor is needed to accomplish this feature.
But I think it is not necessary a huge transformation.
Why you don't develop a second Electron application that only renders an editor tab, spawned by vscode main editor window? That way you end up with two Electron instances running, I know, but it's easier to develop the communication with the main editor and another program than make the main program support another window.
Anyway, it is just an idea. Sorry if I was inconvenient.

It is not a duplicate, it is an implementation idea. It isn't even an issue. The bot may hide you this idea for the future. Anyway...


fix(backend-proxy-middleware): make onProxyReq handler more robust

In some rare cases it could happen that the proxyReq in https://github.com/SAP/open-ux-tools/blob/main/packages/backend-proxy-middleware/src/base/proxy.ts#L41 is missing the path property. If this the case then the proxy request will throw an exception. This PR introduces a check for the path property to make the onProxyReq handler more robust.

Thanks @tobiasqueck @longieirl


Native fs logs are missing from endpoint

Environment info

NooBaa Version: master-20210718
Platform: OCP 4.7

Actual behavior

Native FS logs are missing

Expected behavior

Native FS logs should continue to come during IO operation

Steps to reproduce

Enabled debugLevel: 5 by editing "oc edit noobaas noobaa".
Did IO run, IO logs showed logs with FS:FSWorker  logs.
After a while, these logs stopped printing while doing IO

Uploading must-gather for debugging.
@liranmauda / @jackyalbo : Since you added this code last time to work with debug 5, would you be able to fix this one. Thanks
More information - Screenshots / Logs / Other output

must-gather-1.tar.gz

@nimrod-becker , this can become a big problem for long runs. Kindly have this triaged.

Hi @nimrod-becker , I have not seen this bug lately but do you suspect it to be a problem in code and should this be investigated considering we have cleared high priority defects.

Hi @akmithal
The code handling debug was changed in #6697
In your case (the pervious method) you had to set the debug to it's level (5)
In the new code you are only changing according to the debug config (our case nsfs).
If this bug doesn't repeat, I think it is safe to close it.
WDYT?

Ok, let's close it as not seen since some time now.


$PSVersionTable.GitCommitId based on generated constant

Resolve #3676
Fix #3739
Generate C# file with a constant containing current version GitCommitId.
Correct a test for GitCommitId.

@lzybkr Please clarify - currently  git --git-dir=".git" describe --dirty --abbrev=60 return v6.0.0-alpha.18-60-gb09e9b570c757b9869f454276aa708eac307f5b1 where last part is a hash - do you want change formatting? v6.0.0-alpha.18-60 Commit Hash: gb09e9b570c757b9869f454276aa708eac307f5b1

I'm always a fan of better formatting.
I suggest reading the documentation on describe, and we might consider using --long to always get the hash.
Note that the g is not part of the hash, the format (with --long) is {tag}-{# of commits past tag}-g{hash of head}.

We would parse the long formatted "git describe" and output in the desired form, ex.:
 Version: v6.0.0-alpha.18 Commits: 60 Commit Hash: b09e9b570c757b9869f454276aa708eac307f5b1

Sounds good, though I would omit Commits if it is 0 (which will be the common case) and maybe use the phrase Additional Commits.

@lzybkr powershell.version is still used in Install-PowerShellRemoting.ps1.
I see #2671 Should we fix the script here? If yes how can we fix this? Can we use there PSVersionTable.PSVersion?
/cc @mirichmo

I added commit to fix #3739

@iSazonov thanks for fixing this. The hard-coded alpha string caused me huge effort in beta.1 release.
I have 2 comments:

Could you please resolve the conflicts?
If you search the usage of powershell.version, you will find it's used in following files:

E:\PowerShell\.gitignore
E:\PowerShell\.spelling
E:\PowerShell\build.psm1
E:\PowerShell\build.sh
E:\PowerShell\build.sh
E:\PowerShell\src\powershell-native\Install-PowerShellRemoting.ps1
E:\PowerShell\src\powershell-unix\powershell-unix.csproj
E:\PowerShell\src\powershell-win-core\powershell-win-core.csproj
E:\PowerShell\src\System.Management.Automation\engine\PSVersionInfo.cs
E:\PowerShell\src\System.Management.Automation\engine\PSVersionInfo.cs
E:\PowerShell\test\powershell\Host\PSVersionTable.Tests.ps1

Some of those files are not updated in this PR. I think all appearances of powershell.version need to be reviewed and updated.

This is the third conflict over the past 24 hours in build.psm1 😄 - I'll resolve tomorrow.
I use powershell.version file in tests. So you might have to leave it in .gitignore
I'm afraid that I won't be able to fix build.sh - can I delegate this anybody?

@iSazonov Sorry that I have to change build.psm1 many times in the past day -- obviously our release process and test infrastructure are still far away from perfect 😦
As for build.sh, writing an equivalent bash script to do the same would be (1) not easy (2) hard to maintain 2 scripts for the same thing in future. One option is to extract this logic and write C# code to do it, like the existing ResGen and TypeCatalogGen. Then we can just call dotnet run from both powershell script and bash script.
I'm not sure how many people are using build.sh honestly, and not really sure if this worth the effort.
@SteveL-MSFT @joeyaiello @lzybkr do we have any data to show how important build.sh is? Can we just remove that support?

appveyor temporary failed - I restart.

I only fix but don't test 'Install-PowerShellRemoting.ps1'.

@iSazonov - I ran across this relevant blog post which suggests an assembly attribute that we should also use.
I think we can ignore the part in that blog post about finding the sha without git - we've been using git to do this already with no complaints.

This is exactly what we use.  Used to use GitVersion but now we're doing our own computation of build metadata:
Get-FileVersionInfo P:\Repositories\BuildResults\Foo_Master_CompleteBuild\<IP_ADDRESS>\64BitDevelopment
\Release\Foo.dll | ForEach-Object ProductVersion

5.2.0+105.Branch.master.Sha.31e45082cd1093133b6687dd172daa04b2a10940.Built.20170505T1739

And we do use git to get the SHA1, branch, etc.  This is the function we use:
function GetGitBuildMetadata([string]$SemVer, [string]$Revision) {
    $timestamp = Get-Date -Format yyyyMMddTHHmm
    $sha1   = git rev-parse --verify HEAD
    $branch = git rev-parse --abbrev-ref HEAD
    if (!$branch -or ($branch -eq 'HEAD')) {
        if ($env:BUILD_SOURCEBRANCH) {
            $branch = $env:BUILD_SOURCEBRANCH.Trim().Replace("refs/heads/", "").Replace("refs/","")
        }
        else {
            $branch = 'unknown'
        }
    }

    $prereleaseTag = if ($branch -notmatch 'master|release') { '-prerelease' } else { '' }

    $metadata = "${SemVer}${prereleaseTag}+${Revision}.Branch.${branch}.Sha.${sha1}.Built.${timestamp}"
    $metadata
}

We can add 'AssemblyInformationalVersionAttribute' in System.Management.Automation\AssemblyInfo.cs by Start-PSBuild.
But Git will see that as a change - how can we resolve the problem?

On our official build machine, we process the AssemblyInfo.cs file and don't care if Git thinks it's an untracked change.  That working directory will get scorched on the next build.
For dev builds, you could either hard-code that value (indicating it isn't an official build) or process it and then reset the file before the build exits.

I like the AssemblyInformationalVersionAttribute idea. If going that direction, then we don't need to generate the PSVersionInfo.generated.cs during the build. Instead, we write code in PSVersionInfo.cs to get the ProductionVersion of the S.M.A.dll by FileVersionInfo]::GetVersionInfo([psobject].Assembly.Location).ProductVersion, and then parse the string to get PSVersion and GitCommitId.
As discussed in http://stackoverflow.com/a/752209/7129704

FileVersion and ProductVersions are only likely to be different if the assembly in question is not just part of one product (e.g. a reusable third party library), if just used in a single application there seems little reason not to keep them the same.

So I think we need to think about setting AssemblyFileVersionAttribute as well, to be the same as AssemblyInformationalVersionAttribute.
However, I don't think we should try adding the attributes in AssemblyInfo.cs file, but instead use MSBuild to do this dynamically somehow. AssemblyFileVersionAttribute and AssemblyInformationalVersionAttribute correspond to FileVersion and InformationalVersion MSBuild properties. I think we should solve it using MSBuild.

One question though: if we depend on AssemblyFileVersionAttribute or AssemblyInformationalVersionAttribute to generate PSVersion and GitCommitId, is there any security concern? (e.g. FileVersion and ProductVersion can be somehow changed by an attacker and thus affecting our code ??)

We could use both option: generating  PSVersionInfo.generated.cs for PSVersionTable and MSBuild-ing attributes for files.

The more we depend on our build script to generate .cs file, the harder it will be to get powershell core built in VS2017 in future. And also build.sh could be a problem

Closed the PR by accident 🤕

@daxian-dbw GetVersion isn't still ported 😕 https://github.com/GitTools/GitVersion/issues/1175

@daxian-dbw I don't believe that tampering with version attributes of a file by itself is a security concern, since are many other ways of file tampering for malicious purposes.  The way to guard against file tampering is with application white listing (and black listing for deprecated versions) where approved file versions are validated through file signing or catalog signing.

I took the next step. Now all projects have common properties and assemblies get version from Start-PSBuild.

This PR is getting too complex, and I think we'd better break it down.
We need a conclusion about how to dynamically generate PSVersion and GitCommitId. There are three proposals so far:

Add script in Start-PSBuild to parse git describe string, and generate c# source file to keep the information. Pros: easy to implement. Cons: (1) hard to bring build.sh up-to-date (e.g. hard to write the equivalent bash script, hard to maintain two scripts that do the same thing) (2) make it harder to eventually build the powershell core in Visual Studio as we have another necessary step burnt into the script.
Add a C# project, maybe named PSVersionGen, like ResGen and TypeCatalogGen to do the code generation. Pros: (1) easy to update build.sh, and only one implementation to maintain. (2) it may be easier to eventually build the powershell core in Visual Studio 2017. Cons: a bit harder to implement comparing using the script.
Dynamically generate AssemblyFileVersionAttribute and AssemblyInformationalVersionAttribute via MSBuild, and change code in PSVersionInfo.cs to parse the FileVersion string to get PSVersion and GitCommitId when PSVersionTable is generated for the first time. Pros: clean, no magical code generation at build time, maybe the easiest to move to Visual Studio 2017 in future. Cons: hard to implement -- csproj changes + more robust logic to parse FileVersion in production code. The MSBuild part definitely need extra research and trial/error (build + NuGet package geneation both depend on csproj. A side topic, .NET Core team use different csproj files for build and package, maybe we should go that direction.)

We need to draw to a conclusion first to know what work items would be. Then we break down the work items so that they can be addressed in multiple PRs, instead of one PR with too many changes.
I vote for NO.3 proposal. @lzybkr @iSazonov please share your opinions.

In brief I agree with NO.3
Perhaps we should create a Meta Issue to split the work on small pieces:
Meta Issue - "Move Start-PSBuild to MSBuild":

Clean up Start-PSBuild from FullClr code and old code.
Generate MSBuild variables with version strings based on Git tags
Move common csproj properties to a common targets file.
Unify  AssemblyFileVersionAttribute and AssemblyInformationalVersionAttribute for all assemblies.
Fix  PSVersionInfo.cs to parse the FileVersion string or/and use MSBuild variables with version.
Use different  csproj  files for build and package.
???

The PR shouldn't be merged - it is only for tracking multiple changes. We split the PR on some light-weight PRs.
There we are trying set assembly attributes by MSBuild based on git version tag and also expose the version to PSVersion table and PowerShell startup banner.
Some Microsoft projects (Roslin, CoreFX/CoreCLR ...) use such version format.
@lzybkr @daxian-dbw  Could you please comment? How can we resolve the conflict with telemetry?

The work is covered b #4863. So close this PR.


chore: update dependencies incl. reqwest

Bumping everything except for pep440_rs. @tdejager do you know what we should do with this regarding the UV integration? Is it time to bump it?

No leave it at the current version :)


OCSVTransformer test and refactor

Hi
In this PR I suggest new test metods for OCSVTransformerTest.java
And some refactoring OCSVTransformer.java with solving issue #54

Great! Thanks @profeg.


Drop depenency on base64

#759 added base64 as a depenency in order to suppress a warning/error on Ruby 3.3/3.4
Since base64 is mostly just a wrapper around the pack/unpack methods it's easy to just replace.
Other gems have taken a similar approach:

https://github.com/rubocop/rubocop/pull/12313
https://github.com/rack/rack/pull/2110
https://github.com/elastic/elasticsearch-ruby/pull/2295
https://github.com/socketry/protocol-http/pull/51
etc.

Oh. Yeah. Encoding seems better.
On Thu, 8 Feb 2024, 16:53 Tony Arcieri, @.***> wrote:

@.**** commented on this pull request.
In lib/http/chainable.rb
https://github.com/httprb/http/pull/778#discussion_r1483206451:

@@ -213,9 +211,9 @@ def auth(value)
def basic_auth(opts)
user  = opts.fetch(:user)
pass  = opts.fetch(:pass)

 creds = "#{user}:#{pass}"

 strict_base64_encoded_creds = ["#{user}:#{pass}"].pack("m0")

Or how about HTTP::Encoding, where there are probably a few other things
you could stick there to provide a nicer facade for various bits in the
standard library
—
Reply to this email directly, view it on GitHub
https://github.com/httprb/http/pull/778#discussion_r1483206451, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAXEPWCD5FSNV35FP4M4QTYSTYJPAVCNFSM6AAAAABC7LIHV2VHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQNZQGYYTAOBVGA
.
You are receiving this because you commented.Message ID:
@.***>


load handlebars preload

when display the template again, do not compile it, cache the greated HTML.

save compiled somehow,\

https://github.com/gruntjs/grunt-contrib-handlebars

http://handlebarsjs.com/precompilation.html


HTTP Client POST not working as intended

Recently, a community user attempted to use the HTTP client, but was unable to, because the client sends POST requests to the incorrect URL.
The issue is that the library uses a URL generated in part by URIPath, which includes the namespace and name of the resource. However, when targeting routes with POST, this results in incorrect paths.
The library should handle these situations gracefully and come up with the correct URL when instructed to use POST.

I was the reporter of this bug in Slack.
The above issue doesn't fully summarize the problem. URIPath is valid when posting to a resource that already exists. The problem is when using client.PostResource to create a resource, URIPath is going to generate a non-existent resource path that cannot be used for creates. As a concrete example, consider using PostResource to generate a new check config. The URL that needs to be POST'd to is something like /api/core/v2/namespaces/<ns>/checks but because PostResource is relying on newRequest which in turn calls on the underlying CheckConfig's URIPath, it's going to get a url like /api/core/v2/namespaces/<ns>/checks/<check-name> which is incorrect.
I wonder if it would be better to expand the API for the client to have resource-specific CRUD operations rather than generic *Resource actions. At the cost of making the API for the client significantly larger in terms of number of methods, it would allow us to provider a more user-friendly API that handles all the low level resource machinery for you.


Empty results data for one column in the first row = entire column doesn't render

If results= contains no value (undefined) for particular column in the first row - entire column doesn't render, despite the column data for other rows exists.
Is that expected Griddle behavour or there is something to look for in approach?

@greenais Can you try supplying a columnMetadata prop and see if this fixes things?
The code branches here which may be causing your problem:
https://github.com/GriddleGriddle/Griddle/blob/master/scripts/griddle.jsx#L915-L925

@babenzele Hi, columnMetadata  is in use already.

Well, that stumps me. I added that code to fix the same problem.

Not an issue in v1+.


Sorting was not required, it was a testing setup issue

This test creates a predictable field index order when creating new fields.

+1 on green build.


Developer Portal Visibility is not working as expected

Description:
If the user set API's Developer Portal Visibility as 'Visible to my domain' and logs in to that dev portal with a tenant user, that API is visible.
Steps to reproduce:
Create and publish an API
Set API's Developer Portal Visibility as 'Visible to my domain'

Go to the devPortal and logout (Can't see the our API anonymously)
Log in to the devPortal with a tenant user
Affected Product Version:
API-M 4.0.0
Environment details (with versions):

OS: Windows 10
DB : MSSQL 2019

Suggested Labels:
API-M 4.0.0
Suggested Assignees:

This issue is not reproducible in the latest built pack with MSSQL configured.
Steps followed:

Created API as super tenant admin
Set the visibility as Visible to my domain
Logged in to Devportal as tenant user - The API is not listed


Fix leaking global 'uncaughtException' handler

Description
Description of the Change
Applicable issues
closes #4144

Coverage increased (+0.03%) to 92.847% when pulling 71ce33c37721e137719d0563140ef2456564420e on juergba/event-leak into 69339a3e7710a790b106b922ce53fcb87772f689 on master.

@weswigham could you run a test with this batch in your environment, please?


Adds maskWords() for masking each words of the string separated by a separator

Not every word can be masked in the text that is masked with mask. It takes extra effort to do this.
Each word can be masked according to the separator specified with maskWords.
Example:
use Illuminate\Support\Str;

$str = 'Yusuf Onur SARI';

return [
    Str::mask($str, "*", 1),
    Str::maskWords($str),
];

/*
[
    "Y**************",
    "Y**** O*** S***",
]
*/

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If possible, please consider releasing your code as a package so that the community can still take advantage of your contributions!
If you feel absolutely certain that this code corrects a bug in the framework, please "@" mention me in a follow-up comment with further explanation so that GitHub will send me a notification of your response.


Add about page to BinderHub

This adds a simple about page to BinderHub and the possibility to extend it with a short message.
The idea is to use the space for the message to put some details about who is operating the page and how to contact them. In some jurisdictions you have to put that kind of information on a web property. For mybinder.org we can use it to insert a message about how to get hold of the team, abuse, seucrity reports, etc.
This is my idea for implementing https://github.com/jupyterhub/binder/pull/139#issuecomment-438377209

This is what the default page looks like with an extra "Hello world" message:

If repo2docker was a direct dependency that is installed in the same container we could even dispaly its version:

It would be quite useful for debugging to have that kind of information and maybe even at a later point BinderHub might want to expose that in a machine-readable format for the purposes of federation/compatibility. Not quite sure how to get it though without asking the builder to spawn a pod and start repo2docker in it :-/ Maybe sth for a new PR.

very cool! would it make sense to include a "...running JupyterHub version XXX" in there too?

Added a short bit of docs. Is this the place you had in mind?
Showing the JupyterHub version as well would be super. Again, not quite sure how we could obtain it in a computationally cheap fashion :-/
Also made a small change to the circle config as apparently the build directory for the docs has changed.

https://115-89419368-gh.circle-artifacts.com/0/html/customizing.html

yep, that's a good start, we can iterate in subsequent PRs as it becomes clearer how to expose this to users. I'm +1 once travis is happy!

ok, mergy merge merge! now the fun process of figuring out what this language should be on mybinder.org :-)
@betatim, interested in opening a PR to get the ball rolling there? I imagine we could merge that PR and the binder docs PR at the same time once we like the language


Zodiac Safe App URL change

Name/Description
New URL for Zodiac Safe App
Type

Update

Code for review
https://github.com/gnosis/zodiac-safe-app
IPFS hash/App URL
https://zodiac.gnosisguild.org/
Desired date
asap 🙏

Done. Thank you!


Adds tests for gen_external_params.py quantize function

doubles the time of the ci but I dont see a way to avoid that. lgtm

doubles the time of the ci but I dont see a way to avoid that. lgtm

Interesting. Locally took about 1.5 min. Used a smaller opt model for testing to speed it up, maybe I can look to find something even smaller that works that can speed it up eventually


[Alert Manager] Unit test script preparation and execution

Issue/Feature Description:
Alert manager module has several python files. Unit test scripts need to be written for all these function
Why this issue to fixed / feature is needed(give scenarios or use cases):
Files for which the unit test to be carried out includes:
../dolphin/alert_manager/trap_receiver.py
../dolphin/alert_manager/alert_processor.py
../dolphin/alert_manager/rpcapi.py
../dolphin/drivers/dell_emc/vmax/alert_handler.py
How to reproduce, in case of a bug:
Other Notes /  Environment Information: (Please give the env information, log link or any useful information for this issue)

PRs raised, review/rework in progress

PRs are closed


Cannot pip install recently released package from test.pypi after few hours from release

Describe the bug
We've uploaded new version of ibm-watson-machine-learning package on test PyPI - version 1.0.247
Twine upload seems to have worked correctly:
...
Uploading distributions to https://test.pypi.org/legacy/

Uploading ibm_watson_machine_learning-1.0.247-py3-none-any.whl

100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.8/1.8 MB • 00:00 • 56.1 MB/s

Uploading ibm_watson_machine_learning-1.0.247.tar.gz

100% ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 668.7/668.7 kB • 00:00 • 90.9 MB/s

View at:

https://test.pypi.org/project/ibm-watson-machine-learning/1.0.247/

But when we try to install this version of package, we are getting error:
% pip install -i https://test.pypi.org/simple/ ibm-watson-machine-learning==1.0.247 --no-cache-dir
Looking in indexes: https://test.pypi.org/simple/
ERROR: Could not find a version that satisfies the requirement ibm-watson-machine-learning==1.0.247 (from versions: ...
...
ERROR: No matching distribution found for ibm-watson-machine-learning==1.0.247

I can see the package under link here: https://test.pypi.org/project/ibm-watson-machine-learning/1.0.247/
But I can't see it in simple API:
% curl -sH 'Accept-Encoding: gzip, deflate' https://test.pypi.org/simple/ibm-watson-machine-learning/ | gunzip - | grep "1.0.247"
(py310_x86) danielryszka@Daniels-MacBook-Pro ibm_watson_machine_learning %

I can see previous version though in there:
% curl -sH 'Accept-Encoding: gzip, deflate' https://test.pypi.org/simple/ibm-watson-machine-learning/ | gunzip - | grep "1.0.246"
    ibm_watson_machine_learning-1.0.246-py3-none-any.whl

    ibm_watson_machine_learning-1.0.246.tar.gz

The similar situation seems to have occured in the past with other packages based on previous issues in the repo, e.g.: https://github.com/pypi/warehouse/issues/11512
Expected behavior
New version of the package should be available to install.
To Reproduce
Try to install ibm-watson-machine-learning-package in version 1.0.247.
E.g.:
pip install -i https://test.pypi.org/simple/ ibm-watson-machine-learning==1.0.247

My Platform
I've tried it on two different platforms: Mac OS X (pip 21.2.4), RHEL
Additional context
N/A

I manually purged this page from our CDN and the release is there now. Closing this as a duplicate of https://github.com/pypi/warehouse/issues/12214.


syslog: enable INFO by default [RFC]

Using printk for logging errors and warnings and even for informative
messages is all great when you have a console connected and are able to
view those messages but in many cases this will not be the case and in a
production environment such messages will need to be managed differently,
i.e. cached into a buffer, written to a filesystem or sent via the network.
This enabled syslog by default to encourage using SYS_LOG_XXX for any
messages with the benefit of being able to implement a logger hook that
would make it possible to view those messages on demand and using other
means than just a connected console.
The cost is minimal as by default those macros just redirect to printk.
This also moves debug/information output from printk to syslog making this type
of information available to any syslog backend we might have in the system,
not only to the serial console.

will be resubmitted.


Missing "/usr/src/plugins/*.phar" files during docker build process

I followed the instructions to build the docker image based on the Dockerfile of this repo, but during the process, I obtained the same output as the last GitHub Actions output on the last build execution:

https://github.com/tiredofit/docker-osticket/actions/runs/4056256319/jobs/6980514420#step:9:496

 > [3/4] RUN set -x &&     cd /usr/src/plugins &&     php make.php hydrate &&     for plugin in $(find * -maxdepth 0 -type d ! -path doc ! -path lib); do cp -r ${plugin} /assets/install/include/plugins; done;     cp -R /usr/src/plugins/*.phar /assets/install/include/plugins/ &&     cd / &&         git clone https://github.com/clonemeagain/osticket-plugin-archiver /assets/install/include/plugins/archiver &&     git clone https://github.com/clonemeagain/attachment_preview /assets/install/include/plugins/attachment-preview &&     git clone https://github.com/clonemeagain/plugin-autocloser /assets/install/include/plugins/auto-closer &&     git clone https://github.com/bkonetzny/osticket-fetch-note /assets/install/include/plugins/fetch-note &&     git clone https://github.com/Micke1101/OSTicket-plugin-field-radiobuttons /assets/install/include/plugins/field-radiobuttons &&     git clone https://github.com/clonemeagain/osticket-plugin-mentioner /assets/install/include/plugins/mentioner &&     git clone https://github.com/philbertphotos/osticket-multildap-auth /assets/install/include/plugins/multi-ldap &&     mv /assets/install/include/plugins/multi-ldap/multi-ldap/* /assets/install/include/plugins/multi-ldap/ &&     rm -rf /assets/install/include/plugins/multi-ldap/multi-ldap &&     git clone https://github.com/clonemeagain/osticket-plugin-preventautoscroll /assets/install/include/plugins/prevent-autoscroll &&     git clone https://github.com/clonemeagain/plugin-fwd-rewriter /assets/install/include/plugins/rewriter &&     git clone https://github.com/clonemeagain/osticket-slack /assets/install/include/plugins/slack &&     git clone https://github.com/ipavlovi/osTicket-Microsoft-Teams-plugin /assets/install/include/plugins/teams &&         touch /var/log/msmtp.log &&     chown nginx:www-data /var/log/msmtp.log &&        apt-get clean &&     rm -rf /var/lib/apt/lists/* &&     rm -rf /tmp/* &&     rm -rf /usr/src/* &&     rm -rf /root/.composer/cache:
#0 0.279 + ' ' cd /usr/src/plugins
#0 0.279 /bin/bash: line 1:  : command not found
#0 0.279 + cp -R '/usr/src/plugins/*.phar' /assets/install/include/plugins/
#0 0.280 cp: cannot stat '/usr/src/plugins/*.phar': No such file or directory
------
WARNING: buildx: failed to get git commit: fatal: ambiguous argument 'HEAD': unknown revision or path not in the working tree.
Use '--' to separate paths from revisions, like this:
'git <command> [<revision>...] -- [<file>...]'
Dockerfile:52
--------------------
  51 |         git clone -b develop https://github.com/osTicket/osTicket-plugins /usr/src/plugins
  52 | >>> RUN set -x && \    cd /usr/src/plugins && \
  53 | >>>     php make.php hydrate && \
  54 | >>>     for plugin in $(find * -maxdepth 0 -type d ! -path doc ! -path lib); do cp -r ${plugin} /assets/install/include/plugins; done; \
  55 | >>>     cp -R /usr/src/plugins/*.phar /assets/install/include/plugins/ && \
  56 | >>>     cd / && \
  57 | >>>     \
  58 | >>> # Add Community Plugins
  59 | >>>     ## Archiver
  60 | >>>     git clone https://github.com/clonemeagain/osticket-plugin-archiver /assets/install/include/plugins/archiver && \
  61 | >>>     ## Attachment Preview
  62 | >>>     git clone https://github.com/clonemeagain/attachment_preview /assets/install/include/plugins/attachment-preview && \
  63 | >>>     ## Auto Closer
  64 | >>>     git clone https://github.com/clonemeagain/plugin-autocloser /assets/install/include/plugins/auto-closer && \
  65 | >>>     ## Fetch Note
  66 | >>>     git clone https://github.com/bkonetzny/osticket-fetch-note /assets/install/include/plugins/fetch-note && \
  67 | >>>     ## Field Radio Buttons
  68 | >>>     git clone https://github.com/Micke1101/OSTicket-plugin-field-radiobuttons /assets/install/include/plugins/field-radiobuttons && \
  69 | >>>     ## Mentioner
  70 | >>>     git clone https://github.com/clonemeagain/osticket-plugin-mentioner /assets/install/include/plugins/mentioner && \
  71 | >>>     ## Multi LDAP Auth
  72 | >>>     git clone https://github.com/philbertphotos/osticket-multildap-auth /assets/install/include/plugins/multi-ldap && \
  73 | >>>     mv /assets/install/include/plugins/multi-ldap/multi-ldap/* /assets/install/include/plugins/multi-ldap/ && \
  74 | >>>     rm -rf /assets/install/include/plugins/multi-ldap/multi-ldap && \
  75 | >>>     ## Prevent Autoscroll
  76 | >>>     git clone https://github.com/clonemeagain/osticket-plugin-preventautoscroll /assets/install/include/plugins/prevent-autoscroll && \
  77 | >>>     ## Rewriter
  78 | >>>     git clone https://github.com/clonemeagain/plugin-fwd-rewriter /assets/install/include/plugins/rewriter && \
  79 | >>>     ## Slack
  80 | >>>     git clone https://github.com/clonemeagain/osticket-slack /assets/install/include/plugins/slack && \
  81 | >>>     ## Teams (Microsoft)
  82 | >>>     git clone https://github.com/ipavlovi/osTicket-Microsoft-Teams-plugin /assets/install/include/plugins/teams && \
  83 | >>>     \
  84 | >>> ### Log Miscellany Installation
  85 | >>>     touch /var/log/msmtp.log && \
  86 | >>>     chown nginx:www-data /var/log/msmtp.log && \
  87 | >>>    \
  88 | >>> ## Cleanup
  89 | >>>     apt-get clean && \
  90 | >>>     rm -rf /var/lib/apt/lists/* && \
  91 | >>>     rm -rf /tmp/* && \
  92 | >>>     rm -rf /usr/src/* && \
  93 | >>>     rm -rf /root/.composer/cache
  94 |
--------------------
ERROR: failed to solve: process "/bin/bash -c set -x && \\    cd /usr/src/plugins &&     php make.php hydrate &&     for plugin in $(find * -maxdepth 0 -type d ! -path doc ! -path lib); do cp -r ${plugin} /assets/install/include/plugins; done;     cp -R /usr/src/plugins/*.phar /assets/install/include/plugins/ &&     cd / &&         git clone https://github.com/clonemeagain/osticket-plugin-archiver /assets/install/include/plugins/archiver &&     git clone https://github.com/clonemeagain/attachment_preview /assets/install/include/plugins/attachment-preview &&     git clone https://github.com/clonemeagain/plugin-autocloser /assets/install/include/plugins/auto-closer &&     git clone https://github.com/bkonetzny/osticket-fetch-note /assets/install/include/plugins/fetch-note &&     git clone https://github.com/Micke1101/OSTicket-plugin-field-radiobuttons /assets/install/include/plugins/field-radiobuttons &&     git clone https://github.com/clonemeagain/osticket-plugin-mentioner /assets/install/include/plugins/mentioner &&     git clone https://github.com/philbertphotos/osticket-multildap-auth /assets/install/include/plugins/multi-ldap &&     mv /assets/install/include/plugins/multi-ldap/multi-ldap/* /assets/install/include/plugins/multi-ldap/ &&     rm -rf /assets/install/include/plugins/multi-ldap/multi-ldap &&     git clone https://github.com/clonemeagain/osticket-plugin-preventautoscroll /assets/install/include/plugins/prevent-autoscroll &&     git clone https://github.com/clonemeagain/plugin-fwd-rewriter /assets/install/include/plugins/rewriter &&     git clone https://github.com/clonemeagain/osticket-slack /assets/install/include/plugins/slack &&     git clone https://github.com/ipavlovi/osTicket-Microsoft-Teams-plugin /assets/install/include/plugins/teams &&         touch /var/log/msmtp.log &&     chown nginx:www-data /var/log/msmtp.log &&        apt-get clean &&     rm -rf /var/lib/apt/lists/* &&     rm -rf /tmp/* &&     rm -rf /usr/src/* &&     rm -rf /root/.composer/cache" did not complete successfully: exit code: 1

In a past commit, we have this change: https://github.com/tiredofit/docker-osticket/commit/c3cd5baea3b2b0b6159a96e51303b285f9e2942d#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557R51-R52
And that breaks the process of Docker because the /usr/src/plugins path doesn't persist to the next step; I'm proposing a patch to solve that, only removing the RUN set -x && \\ part and continuing with the "one-line" command and should success the process to obtain the OSTicket image.

Ahh that looks like my development process crept into the final Dockerfile there. You are correct - The additional RUN statement is making the rest of the build process "forget" what it had already done. I can remove it for you quickly enough.

Going to give this image some love and get it up to date - Give me 5 minutes.

Thank you so much!!


python311Packages.pyopnsense: 0.3.0 -> 0.4.0

Description of changes

Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

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

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

[ ] Fits CONTRIBUTING.md.

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

5 packages built:

home-assistant-component-tests.opnsense
python310Packages.pyopnsense
python310Packages.pyopnsense.dist
python311Packages.pyopnsense
python311Packages.pyopnsense.dist

six is no longer required: https://github.com/mtreinish/pyopnsense/compare/0.3.0...0.4.0#diff-4d7c51b1efe9043e44439a949dfd92e5827321b34082903477fd04876edb7552L6


Make HTTP/2's DISCONNECT_AT_END more graceful.

Rather than immediately and violently closing the HTTP/2 stream,
we initiate the shutdown sequence for a graceful disconnect.
This fixes StreamAllocation to avoid creating new streams on
shutdown connections. That behavior is not well tested, however.
That will come by integrating dave-r12's PR:
See https://github.com/square/okhttp/pull/2889

@dave-r12 this is the miniature version of #2889. We don’t attempt to violently close the socket, and all of our nondeterminism and strangeness goes away.
If this passes tests (I really hope it does) then I’d like you to take the rest of #2889 and apply it on-top!

Gotcha - did you want to integrate this first? Or want me to apply directly on this PR?

Lemme merge this as-is and you can rebase!


1.0

This issue represents the goals and scope of the project.
Requirements
The library reactive-vis will support the creation of interactive data visualizations. A layered approach will be taken wherein visualization components can be built up from sub-components (mixins), and visualization components can be composed in various ways.
Restrictions

SVG Only (No Canvas, No WebGL)

Composition

Adjacent - Visualizations may be placed next to one another within the same SVG element. The placement should be able to follow a nested box layout.
Layered - It should be possible to place a visual component on top of another in a layered manner. Examples:

Color legend on top of a stacked bar chart in the upper right corner.
Area chart behind a bar chart

Nested - Hybrid visualizations in which visual components are nested within other visual components should be trivial to assemble. Examples:

Facet (small multiples in X and/or Y)
Scatter plot of pie charts
Treemap of line charts

Dynamism

Interactions

Brushing

Quadtree
R-Tree

Hovering

Voronoi Overlay

Pan
Zoom

Linked Views

Linked Highlighting
Focus + Context
Crossfilter

Transitions
Updates in configuration should manifest as transitions where possible.
It should be possible to customize the transitions (e.g. bounce in bars on enter).

Visual Components
Visual components include both marks and "chart types".
Foundational Components

Circle
Rectangle
Scatter Plot
Bar Chart

Stacked
Grouped
Horizontal variations (Bar Chart, Stacked, Grouped)

Pie Chart
Line Chart

Variant with multiple lines
Variant with spline interpolation

Area Chart

Stacked Area Chart
Streamgraph

Treemap

Add-on Components
The following components should be implemented as separate packages that build upon this library.

Sankey
Chord
Parallel Coordinates
Choropleth
Tree (tidy)
Box Plot

Extensibility
Visual components should be extensible without requiring modification of the original code. Something like inheritance should be possible. The following should be accessible:

Visual marks should be accessible for appending additional marks or adding interactions.

e.g. adding text labels to each bar in a bar chart

Scales should be inspectable.

e.g. for using in a color legend

Nested composition is the most fun


Modify IRnifty/Nifty255 Mods for SpaceDock Rehost

1890 [1] FATAL CKAN.NetKAN.Program (null) - Could not get the mod from SD, reason: Mod not published..

Fixed. Sorry about that.


feat: Add support for Langchain Callbacks

Solves Issue https://github.com/traceloop/openllmetry-js/issues/133: 🚀 Feature: re-write Langchain instrumentation to use Langchain Callbacks

⚠ This PR is actually in WIP status until we find a way to monkey patch class constructors ⚠

Implemented a BaseCallbackHandler (source for the interface). The main idea is that the handler has some state for each of the spans it starts, so that when handleXXEnd or handleXXError are invoked, the same span can be properly ended. To do that, we are using a stack, the logic is as follows:

We start a Span whenever handleXXStart is called and push it into the stack.
If handleXXEnd is called:

If there are no Span instances in the stack, we throw an Error, as handleXXEnd cannot be called before the corresponding handleXXStart.
Otherwise, we pop the Span from the stack, and end it accordingly.

If handleXXError is called, we follow a similar logic as for handleXXEnd.

This approach has the benefit of being able to properly handle nested spans.

Tests
Unit tests
npm run build:all && npx nx run @traceloop/instrumentation-langchain:test

Integration tests (aka sample-app)

Modified the sample-app for LangChain (this is expected to go away before merging this PR, as it's just for my own testing purposes) to:

Not depend on OpenAI stuff, as I lack an API key 🥲
Make it faster by just running a single workflow
Disable manual instrumentation of LangChain modules
Instantiate and pass the TraceloopCallbackHandler to check if the spans are generated properly

Start Ollama serving llama2 LLM by running:

docker run -d -v ollama:/root/.ollama -p 11434:11434 --name ollama ollama/ollama && docker exec -it ollama ollama run llama2

Ran the sample app via:

TRACELOOP_API_KEY=<REDACTED> npx nx run sample-app:run:langchain

Verified that there is a trace in my Traceloop development stage, but it lacks the spans from the CallbackHandler, as I'm using a ProxyTracerProvider, which defaults to NoOp tracer when no delegate is provided. This behavior should change, and spans will be sent once we manage to mockey-patch LangChain constructors, and inject the CallbackHandler in constructor params.
For the moment, I just verified the behavior via logs.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Xabier Lahuerta Vázquez seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@Xabilahu just for my own records, linking our discussion from Slack where I suggested a solution to the problems you've raised here.


(BOLT-648, BOLT-649) Support _catch_errors, _run_as

Add support for _catch_errors and _run_as to apply. Previously
_catch_errors=true was the default behavior, now it will default to
false and allow it to be changed to true.

Relies on work in https://github.com/puppetlabs/bolt/pull/508 and is going to have some conflicts with https://github.com/puppetlabs/bolt/pull/509 and https://github.com/puppetlabs/bolt/pull/512.

CLA signed by all contributors.

The new acceptance test appears to have some issues, working on it.

Got it working. There were some surprises around tty with the facts plan and sudo on macOS.


Continue switching commands from libkpod to libpod

Taking over https://github.com/kubernetes-incubator/cri-o/pull/862

Looks fine now, LGTM. Let's get the tests run and get this merged.

As soon as travis passes trigger the e2e tests.

ooops, CI isn't happy.

Need to wait for https://github.com/containers/storage/issues/102.

Latest containers/storage needs to be vendored in https://github.com/kubernetes-incubator/cri-o/pull/899

[retest]

[retest]

This job failed due to infrastructure problems by the look of it: https://hurl.corp.redhat.com/7844cd5

[retest]

@rhatdan how can I trigger a test if tests are working again?

You need to rebase and then we can trigger it.

rebased

/test all

@rhatdan I am looking at the link under Details, and I am not sure if I am understanding it correctly. The reason of the failure is a build that timed out?

/test e2e_rhel

@umohnani8 Lets try to just test that component.

@umohnani8 A couple of tests are failing. https://ci.openshift.redhat.com/jenkins/job/test_pull_request_crio_integration_rhel/23/s3/download/testout.txt

/test all

@stevekuznetsov @cevich Can't seem to get tests to run?

@rhatdan same here -- maybe the Jenkins queue got backed up, but the tests did end up running in the end :)

Ok so E2E tests are running and no longer reporting success when one of the tests failed.  Since 148/149 are passing, and we know the same tests is failing for everyone, I say this passed. e2e test.  Now will look at integration tests.

Looks like success, I will merge.


Example for cc2640r2f

Hello ,
are there plans for adding as an example the cc2640r2f platform? Or has this already been added and I am missing something (I'm new to OT and TI MCUs).
I'm currently exploring the "Porting" guide on https://openthread.io/guides but I don't know if I'm going in the right direction.
Thanks in advance!

Just learned that the CC2640R2F is not able to operate in IEEE 802.15.4 mode. My bad!


Test against AGP 8.1.0 as latest supported stable version

I had some test failures running this locally that looked like flakes (failed running all of functionalTest but pass when running individually in IDE), lets see if CI agrees

Thanks!


TLS 1.2 support on Android 4.1-4.4

According to Google, Android support TLS 1.2 since Android 4.1, but for various reasons it must be manually activated by the developer in versions 4.1, 4.2, 4.3 and 4.4.
Would it be possible to activate it by default in Jsoup ?
Thanks in advance.

Have you got some pointers on how to, in a non-Android specific way (i.e. Jsoup does not have any Android specific code/dependencies).
I had a bit of a look around and it looks like you just need to set some Android static SSL configs, which wouldn't conflict with what jsoup's doing.

(Closing out old, dormant bugs. If you are still impacted by this, please reopen & vote.)

Here's how I solved this:

Create a class TLSSocketFactory

import java.io.IOException;
import java.net.InetAddress;
import java.net.Socket;
import java.net.UnknownHostException;
import java.security.KeyManagementException;
import java.security.NoSuchAlgorithmException;

import javax.net.ssl.SSLContext;
import javax.net.ssl.SSLSocket;
import javax.net.ssl.SSLSocketFactory;

public class TLSSocketFactory extends SSLSocketFactory {

    private SSLSocketFactory internalSSLSocketFactory;

    public TLSSocketFactory() throws KeyManagementException, NoSuchAlgorithmException {
        SSLContext context = SSLContext.getInstance("TLS");
        context.init(null, null, null);
        internalSSLSocketFactory = context.getSocketFactory();
    }

    @Override
    public String[] getDefaultCipherSuites() {
        return internalSSLSocketFactory.getDefaultCipherSuites();
    }

    @Override
    public String[] getSupportedCipherSuites() {
        return internalSSLSocketFactory.getSupportedCipherSuites();
    }

    @Override
    public Socket createSocket() throws IOException {
        return enableTLSOnSocket(internalSSLSocketFactory.createSocket());
    }

    @Override
    public Socket createSocket(Socket s, String host, int port, boolean autoClose) throws IOException {
        return enableTLSOnSocket(internalSSLSocketFactory.createSocket(s, host, port, autoClose));
    }

    @Override
    public Socket createSocket(String host, int port) throws IOException, UnknownHostException {
        return enableTLSOnSocket(internalSSLSocketFactory.createSocket(host, port));
    }

    @Override
    public Socket createSocket(String host, int port, InetAddress localHost, int localPort) throws IOException, UnknownHostException {
        return enableTLSOnSocket(internalSSLSocketFactory.createSocket(host, port, localHost, localPort));
    }

    @Override
    public Socket createSocket(InetAddress host, int port) throws IOException {
        return enableTLSOnSocket(internalSSLSocketFactory.createSocket(host, port));
    }

    @Override
    public Socket createSocket(InetAddress address, int port, InetAddress localAddress, int localPort) throws IOException {
        return enableTLSOnSocket(internalSSLSocketFactory.createSocket(address, port, localAddress, localPort));
    }

    private Socket enableTLSOnSocket(Socket socket) {
        if(socket != null && (socket instanceof SSLSocket)) {
            ((SSLSocket)socket).setEnabledProtocols(new String[] {"TLSv1.1", "TLSv1.2"});
        }
        return socket;
    }
}

Call HttpsURLConnection.setDefaultSSLSocketFactory(new TLSSocketFactory()); in onCreate() before doing any networking task


State of Tick in 2023

Issues:

Sparse array serialization segfaults on various platforms with various versions of python
Various deprecation warnings for csc/csr_matrix
A number of tests are only failing on OSX

Tests to be disabled generally:
grep -A 1 -r "\.skip" .
./tick/survival/tests/convolutional_sccs_test.py:    @unittest.skip("issue with StratifiedKFold")
./tick/survival/tests/convolutional_sccs_test.py-    def test_LearnerSCCS_fit_KFold_CV(self):
--
./tick/solver/tests/sdca_test.py:    @unittest.skip("Is failing by a small amount - to assess")
./tick/solver/tests/sdca_test.py-    def test_sdca_identity_poisreg(self):
--
./tick/random/tests/random_test.py:    @unittest.skip("Needs checking with scipy benchmark")
./tick/random/tests/random_test.py-    def test_uniform_int_random(self):
--
./tick/random/tests/random_test.py:    @unittest.skip("Needs some clarity around what we should assert")
./tick/random/tests/random_test.py-    def test_poisson_random(self):

For the moment I will be configuring Github actions to only show the builds which do in fact finish. This is not ideal, but considering the state of things I think it's best to have something that we know consistently works for people to make PRs against. Once this is done I can try adding python3.10 on all platforms and checking if it builds ok.

Are there any plans for maintaing this package in the long term?

@oresthes I'm aiming to get a new release on pypi/pip in the near future


k8sutil: remove CreateEtcdNodePortService

NodePort Svc is some useless legacy code

lgtm. thank for cleaning up the codebase.

@etcd-bot retest this please


remove texture extension on export

Title of this PR says it's a fix on export. yet actual fix is on "open", and not only that but in the actual module. This isn't an optimal solution plus it does one thing but claims to do another.

Doing another PR


Update a2_questionnaire_design_part_a.md

What changes are you trying to make? (e.g. Adding or removing code, refactoring existing code, adding reports)
Answered the questions.
What did you learn from the changes you have made?
Was there another approach you were thinking about making? If so, what approach(es) were you thinking of?
Were there any challenges? If so, what issue(s) did you face? How did you overcome it?
How were these changes tested?
A reference to a related issue in your repository (if applicable)
Checklist

[ ] I can confirm that my changes are working as intended

Hi Amanda, thanks for pointing it out. I have updated the assignment and
added the observational units. Should I create a new pull request?
Regards,
Shruti.
On Tue, Nov 12, 2024 at 11:04 AM amanda-ng518 @.***>
wrote:

@.**** requested changes on this pull request.
A2 observational units missing
—
Reply to this email directly, view it on GitHub
https://github.com/ShrutiPatil-SAP/sampling/pull/2#pullrequestreview-2430036486,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BKQP5TVDHQUSRCSHYPQSHPT2AIRKHAVCNFSM6AAAAABRQSLRISVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDIMZQGAZTMNBYGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Changed 'paran' to 'param'

Good catch 😁 👍  btw were you able to test out the feature as well?

I haven't actually tested anything. I'm not entirely sure how to go about setting up a test environment. I'm hoping to actually code in some features, but the testing is the part I'm not sure of.


rultor hello

@rultor hello

@rultor hello

@l3r8yj Hi there! I understand a few simple commands: "merge", "deploy", etc. This page explains them briefly. Any questions or bug reports are welcome. Have fun :)


Rename SubDetectorHitNumbers -> SubdetectorHitNumbers

Needed after https://github.com/key4hep/EDM4hep/pull/188

https://github.com/key4hep/k4LCIOReader/pull/33/files#diff-82e068f9eeb5c25dcf68be28ba534d1b7a09f5990172f5a294c10a9de6f520c4R44-R51
as minimal solution to some backwards compatibility