An ability to replace distro logo with a picture

Current state:
Not implemented, i think... Did not find anything relative in the config file.
Wanted state:
Being able to use any .svg/.png file as a distro logo with the ability
to change the size of a picture.
This feature is implemented in the neofetch and can be configured in the "# Backend Settings" section of the config file.

Referenced feature:

This is planned but not implemented yet, as it is completely terminal depended so a lot of code needs to be written. I will also need to  completely rework the way the logo is printed, currently it is done line by line, with the info in between. This doesn't work when displaying pictures, as they need to be rendered at once. And fastfetch is still in a too early stage to focus on such features. so don't expect it to soon, sorry to disappoint you.

I now keep track of planned features in DEVELOPMENT.md, as there are too many to use issues for that.


R114-R1 Fails to boot from SD card on Orange Pi 5 Plus

According to the documentation, an image with any target storage generated by the .run file should also boot from a MicroSD card.
It does not: at least for me.
Armbian boots fine from the same MicroSD card, so there's nothing wrong with the hardware.
I have ordered an M.2 drive. When that arrives I can report back on wether it solves the issue or not.
It should be noted that I have a Samsung Odyssey G9 monitor (5120x1440@240Hz resolution), so it might be that the OS fails to set the display mode and gives up. The display works fine in Armbian, though, in both 5120x1440@60Hz and 2560x1440@120Hz, so the OPi is compatible with the monitor.
Steps to reproduce

Run orangepi5-openfyde-r114_r1.run in Ubuntu 22.04 (WSL2)
Select Orange Pi 5 Plus and M. 2 NVME or EMMC in the menu (I've tried both)
Write resulting image to an SD card using Raspberry Pi Imager 1.7.5 in Windows 11
Plug MicroSD into Orange Pi 5 Plus
Power on system

Expected
System to boot
Observed

No image on screen.
Status LED is red with quick green (or blue?) flashes a few times every second.
Waiting for 5+ minutes does not help.

Thanks to the team. I  like Openfyde.
I have the same issue as @noname22 only i observed:

System boots and goes into setup
But when I get to select a drive, no drive shows up in the Box

When I go back into "try out", everything sets up as expected and works fine.
Only when I try to  "install Openfyde", again no drive appears in the Box to chose from and I can only  go back to "Try".


:bug: Fix(vm): Fix issues with tsup and package.json

Description
Issues with package including

bad folder path (copy pasta)
linking to wring esm/cjs modules in package.json
not compiling cjs

Testing
Explain the quality checks that have been done on the code changes
Additional Information

[ ] I read the contributing docs (if this is your first contribution)

Your ENS/address:

Current dependencies on/for this PR:

main

PR #708

PR #709   👈

This stack of pull requests is managed by Graphite.


Upgrade to IDEA 2017.2

I think they have just released 2017.2 and we need to upgrade.

@fharms I wonder if you can find time to upgrade

Oh it was IDEA 2017.1.2 I think I may mistakenly have seen as 2017.2.

So is this plugin work now?
I can see the camel icon but no popup when I write my endpoint.
IDEA : 2017.1.2
camel plugin : 0.4.0
camel : 2.19.0

@abccbaandy its better to open a new ticket
And you can look in the event log / idea log for any kind of error.

@fharms if you get some time you are welcome to upgrade to the new 2017.2 release.

Sure. will look into it this week


Correct color picker default location

Fix issue where default color picker displayed off-screen.
Fixes #15418

This will just make the color picker go off the left side of the screen

This will just make the color picker go off the left side of the screen

All of the color picker settings I've seen are on the right side of the screen, so picker goes off to the right. Are there settings which display on the left side of the screen?

Latest commit takes into account the client's current monitor for positioning details and resolves the multi-monitor problem.

added in https://github.com/runelite/runelite/commit/707ab78cdb6da090032c59f72e4ebfbc245126b1


Pretrain Huggingface LayoutLM model with different language

Describe the bug
LayoutLM
The problem arises when using:
LayoutLM model is available in huggingface transformers now. Is it possible to pretrain the LayoutLM model with custom corpus(German language) with huggingface transformers now?
It will be really good if we can pretrain on own forms or invoice for different languages.
Looking forward for your response.

@Sharathmk99 We are working on the multilingual LayoutLM. Please stay tuned.

@wolfshow any date when multilingual model will be available?

Hey! Great work and intuition on the LayoutLM pre-training approach. Indeed, having a multilingual model would be also interesting to me. Any estimation on when will be released? Looking forward to it, thanks!

multilingual或者中文版的模型开源了的时候，踢我一下，谢谢！🙏

multilingual或者中文版的模型开源了的时候，踢我一下，谢谢！🙏

everyone looking for multilingual support kindly go through this project derived from layoutlm https://github.com/knitemblazor/Multilingual_LayoutLM

hi, where to get or pretrain the models for Japanese, Korean, etc<EMAIL_ADDRESS>


Implementing a more generic version of jalr.

Still not the full generic version: only supports zero offset.

Conflicts?

Can't be conflicts, it built and executed. Maybe the VM crashed?


make default values stored by ERR_get_error_all() and friends more co…

When chasing a regression in an error reporting test of our CMP contribution
I came again across the issue that the documentation of ERR_get_error_all() and friends
does not state that they touch storage locations for which pointers are given only on success and
does not state which values are stored in case no respective data (e.g., line number or function name) is available. Therefore it remains unclear if callers should initialize the respective locations beforehand and how they should detect the absence of a an actual value.
Moreover, the default pointer values provided by these functions in case the requested information is unset so far are rather inconsistent: "" vs. "NA" vs. "N/A".
This PR clarifies these things in the documentation and suggests a consistent default for pointer values: NULL. I chose NULL rather than "" because the latter could be more easily confused with a legitimate value. If for compatibility with existing usage a proper pointer is needed (though I did not notice any such need at least in the existing test suite), I'd say "" is better than "NA" or any other non-empty string because such a non-empty string could collide with a real value (e.g., function name).

Checklist

[x] documentation is added or updated
[ ] tests are added or updated

Cleaner code too.  I'm all for it.

As the existing code never returned NULL pointers in the file/line/func/data output values, I'd really prefer if this was kept with the current patch. Otherwise it would be a slight API break that could produce crashes in the existing third party code that uses these API calls.
I have no problem with making it all consistent and empty strings.

As for the documentation improvement I'd have another suggestion (which does not block this PR, but could be added to it) - it should be mentioned that the data value is valid only until any other OpenSSL API calls that can manipulate the error stack are called, because after that call the data value can be deallocated.

Thanks @t8m also for the following comment:

As the existing code never returned NULL pointers in the file/line/func/data output values, I'd really prefer if this was kept with the current patch. Otherwise it would be a slight API break that could produce crashes in the existing third party code that uses these API calls.
I have no problem with making it all consistent and empty strings.

I was considering this, too, as indirectly indicated in my original comments to this PR.
Still my preference is to return NULL (rather than "") in case of unset values because

this is the most clean approach,
so far the behavior in such cases was undefined, so any prudent application developer
will not have relied on always obtaining non-NULL pointers here, and
even when passing a NULL pointer to printf ( ...%s...) or any similar output function, this does not result in a crash but in, e.g., <NULL> being output.

Are there further voices on this design decision?

Passing NULL pointer to %s printf format is undefined behavior. Yes, it currently does not crash with glibc but it could.
Yes, any prudent app developer would probably take care of properly handling NULL because there was nothing said about the possibility of getting NULL in the docs. However I'd expect there definitely are applications that do not check for NULLs and blindly pass the pointers to the %s printf formats or similar APIs. There could be also app developers that looked up the source and saw that the code had explicit handling by overriding NULLs with NA or empty string.
Not having test case in the OpenSSL code that would test for this is not really indicative that much.

BTW, I've just updated also the reference to ERR_GET_LIB(3) in the docs because location info in the error code meanwhile has become less usable due to the deprecation of the function code.

@t8m, I tend to agree that to be on the safe side it may be better to return "" rather than NULL for unset pointer values.
@levitte, since you already approved the NULL solution, what do you (meanwhile) think about that?
Of course, I can easily (re-)add the requested defensive checks on NULL in get_error_values().
Any other strong opinions in either direction?

even when passing a NULL pointer to printf ( ...%s...) or any similar output function, this does not result in a crash but in, e.g., <NULL> being output.

You can't trust this.  Some C libraries do this, others don't (worst case scenario, they crash).  According to the C language standard, an unexpected value or type leads to undefined behaviour.

I'm a bit ambivalent about the what's being discussed.  I do like returning NULL as an indicator of no value present, but at the same time, @t8m is entirely correct that this might be unexpected.  The more cautious approach would be to return the empty string as an indicator (i.e. change "NA" and "N/A" to "").

Since nobody else gave his opinion on this matter and @levitte retracted this approval, I've changed the value returned for unset pointers from NULL to "" as requested by @t8m to be on the safe side.

How about merging this now?

Yes, thanks for the reminder

I squashed the commits into one, that seemed appropriate.
df0822688fc3432cf800cdc07c7f9016ea201170 Make default values by ERR_get_error_all() and friends more consistent


PLAT-67808: Async ilib workaround for moonstone

Checklist

[x] I have read and understand the contribution guide

[x] A CHANGELOG entry is included

[ ] At least one test case is included for this feature or bug fix

[x] Documentation was added or is not needed

[ ] This is an API breaking change

Issue Resolved / Feature Added
moonstone needs to load a resource bundle from a path that cannot be shared with resBundle that i18n/I18nDecorator uses. This lead us to create an internal $L function but it will only load resources synchronously.
Resolution
Added a MoonstoneI18NDecorator and internal/i18n/resBudnle to handle asynchronous resource fetching and translating.
Additional Considerations

$L lives outside the react component lifecycle and will not be updated upon resource loading. This can result in failure in translation if the component renders before the resources load.
Note the capitalization in N which differs from i18n/I18nDecorator

@viodragon2 - Do you think there a need for a standardized hook in i18n for userspace resource loading? For example, an app could make locale-dependent external service calls which are synchronized with the global locale change infrastructure in I18nDecorator. This same infrastructure could support preloading ilib resources as is required to shim async support into moonstone.

Doesn't the app already handle onlocalechange event to run locale-dependent logics? I can't think of a good reason why an app would need to know when the "resources" are available as the apps don't really manage resources on their source codes. It does sound like a good idea to support hooks in asynchronous loading, but I am not 100% sure whether <Suspense> already solves that problem or not.

I think the primary possibility this enables is a consistent means to preload ilib resources before the app renders. So as I look ahead to how to balance customer demands for synchronous retrieval for native-like experiences on a web platform that favors asynchronous methods, one option is to retrieve some/all external resources in batch before render so that all subsequent requests need not wait.
One concern I have with the proposed solution here is that it only addresses string resolution and, as you noted, doesn't provide a means for $L usage to be refreshed upon update, particularly when blocked by shouldComponentUpdate.
By providing the hook, the app (browser, in this case) can inject the string resolution code (and any other ilib resources they discover they need) and Moonstone and i18n can remain ignorant of those requirements.
Does that line of thinking make sense?

I'm not educated enough on Suspense yet to say! You're right that apps wishing to using async ilib right now should use Text over $L. The hope with this PR is to provide a workaround to support the existing $L usage in moonstone which we can't easily change at this point.
Primarily, I want to minimize the change we make to moonstone to support this under the assumption that we'll make broader changes later when async is fully supported. In that light, we could use Suspense when sync: false in MoonstoneDecorator but I'd also be okay holding off on that and allowing the app to manage that deferred rendering for the time being.

Is the description on this ticket still accurate?  Should we remove the reference to MoonstoneI18NDecorator?


Template.Tests consistently fail on Windows due to selenium and npm failures

I have not been able to make the tests pass on Windows. The tests are frequently failing with one of two issues. Any ideas what to change?

Several tests fail when Seleium fails to start

Templates.Test.SpaTemplateTest.SpaTemplate_Works_NetCore(template: "vue") [FAIL]
OpenQA.Selenium.WebDriverException : Cannot start the driver service on http://localhost:64591/
Stack Trace:
            at OpenQA.Selenium.DriverService.Start()
            at OpenQA.Selenium.Remote.DriverServiceCommandExecutor.Execute(Command commandToExecute)
            at OpenQA.Selenium.Remote.RemoteWebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
            at OpenQA.Selenium.Remote.RemoteWebDriver.StartSession(ICapabilities desiredCapabilities)
            at OpenQA.Selenium.Remote.RemoteWebDriver..ctor(ICommandExecutor commandExecutor, ICapabilities desiredCapabilities)        C:\dev\aspnet\Universe2\modules\Templating\test\Templates.Test\Helpers\WebDriverFactory.cs(23,0): at Templates.Test.Helpers.WebDriverFactory.CreateWebDriver()
        C:\dev\aspnet\Universe2\modules\Templating\test\Templates.Test\Helpers\AspNetProcess.cs(103,0): at Templates.Test.Helpers.AspNetProcess.VisitInBrowser()

Perpetual npm issues.

Failed   Templates.Test.SpaTemplateTest.SpaTemplate_Works_NetCore(template: "aurelia")

....

 ==> cmd /c "npm install" [C:\dev\aspnet\Universe2\modules\Templating\test\Templates.Test\bin\Debug\netcoreapp2.0\TestTemplates\bd302f03473b47c79813574f3739e840]
 [ERROR] npm WARN read-shrinkwrap This version of npm is compatible with lockfileVersion@1, but npm-shrinkwrap.json was generated for lockfileVersion@0. I'll try to do my best with it!
 [ERROR] npm WARN deprecated<EMAIL_ADDRESS>Please upgrade to 1.0.4 for node 0.10, 0.12, or to 2.0+ for node 4+
 [ERROR] npm ERR! path C:\dev\aspnet\Universe2\modules\Templating\test\Templates.Test\bin\Debug\netcoreapp2.0\TestTemplates\bd302f03473b47c79813574f3739e840\node_modules\fsevents\node_modules\dashdash\node_modules
 [ERROR] npm ERR! code EPERM
 [ERROR] npm ERR! errno -4048
 [ERROR] npm ERR! syscall scandir
 [ERROR] npm ERR! Error: EPERM: operation not permitted, scandir 'C:\dev\aspnet\Universe2\modules\Templating\test\Templates.Test\bin\Debug\netcoreapp2.0\TestTemplates\bd302f03473b47c79813574f3739e840\node_modules\fsevents\node_modules\dashdash\node_modules'
 [ERROR] npm ERR!  { Error: EPERM: operation not permitted, scandir 'C:\dev\aspnet\Universe2\modules\Templating\test\Templates.Test\bin\Debug\netcoreapp2.0\TestTemplates\bd302f03473b47c79813574f3739e840\node_modules\fsevents\node_modules\dashdash\node_modules'
 [ERROR] npm ERR!   stack: 'Error: EPERM: operation not permitted, scandir \'C:\\dev\\aspnet\\Universe2\\modules\\Templating\\test\\Templates.Test\\bin\\Debug\\netcoreapp2.0\\TestTemplates\\bd302f03473b47c79813574f3739e840\\node_modules\\fsevents\\node_modules\\dashdash\\node_modules\'',
 [ERROR] npm ERR!   errno: -4048,
 [ERROR] npm ERR!   code: 'EPERM',
 [ERROR] npm ERR!   syscall: 'scandir',
 [ERROR] npm ERR!   path: 'C:\\dev\\aspnet\\Universe2\\modules\\Templating\\test\\Templates.Test\\bin\\Debug\\netcoreapp2.0\\TestTemplates\\bd302f03473b47c79813574f3739e840\\node_modules\\fsevents\\node_modules\\dashdash\\node_modules' }
 [ERROR] npm ERR!
 [ERROR] npm ERR! Please try running this command again as root/Administrator.
 [ERROR]
 [ERROR] npm ERR!      C:\Users\namc\AppData\Roaming\npm-cache\_logs\2017-10-26T23_36_51_972Z-debug.log

My machine
dotnet: 2.0.3-servicing-007037
npm: 5.3.0
node: 8.1.3
Runtime Environment:
OS Name:     Windows
OS Version:  10.0.16299
OS Platform: Windows
RID:         win10-x64
cc @jkotalik - who was also unable to get tests passing on his machine

@SteveSandersonMS any idea on this? Any special instructions needed?

For issue 2, does "perpetual" mean "failing in the same way every time" or just "frequent but intermittent"? If it's intermittent, you probably need to ensure Windows Defender excludes the directory where NPM is creating and moving thousands of small files, otherwise if it's holding a lock on a file on the wrong moment, you do get those kinds of access denied errors. NPM has zero tolerance for temporary file access issues. If it's consistent, it might be path-length limitations, though I doubt it because the path in your error message is only 190 chars long.
For issue 1, could this be that you're on Windows 10 Creators Fall Update? As per our conversation before, the Edge driver for Selenium didn't appear to support that OS, so we need to either update our Selenium dependency if they have published a fix, or modify the logic about detecting browser automation support to return false if you're on Fall Update.

Issue 2 - frequent but intermittent. It is frequently failing with "EPERM: operation not permitted, scandir", but the folder it shows in the error message changes. It's not Windows Defender: I have an exclusion for the folder containing the tests.
Side note: I wonder if this means npm install is also frequently failing for our users. In my hobby projects, I switched to yarn because NPM continually had these kinds of errors, even in npm5.
Issue 1 - that's most likely it. Selenium.WebDriver.MicrosoftDriver 16.16299.0 was released last week and appears to resolve it.

Looks like the scandir issue is worse than the usual NPM random glitches on Windows: https://github.com/npm/npm/issues/17747
You might want to downgrade to NPM 4.x until the 5.x line has a proper fix for this.
@natemcmaster If you agree that this is specifically an issue in NPM that we can't directly do anything about, I'd recommend we close this as an external issue.

Yeah, it seems there isn't much we can do about npm's issues, except perhaps, abandon it for yarn. But let's consider that a separate issue.
You can leave this open by assign to me to ensure #136 get's ported to dev.

OK, assigning to you.
We can use yarn in our internal build infrastructure if we want; we just have to not rely on it as part of templates (as in, we shouldn't assume that people using the templates to create projects have it installed).

Would adding this package to templates be reasonable? It would remove the need for a global install of yarn. https://github.com/natemcmaster/Yarn.MSBuild And if not, would it be okay to add it as a flag? dotnet new react --with-yarn?

Using Yarn.MSBuild would still force all developers to install their own copy of yarn, unless I'm mistaking how it works. yarn and npm aren't exactly compatible replacements for each other - for example, if you're using yarn then you're keeping lock information in yarn.lock, and if you're using npm then you're keeping it in npm-shrinkwrap.json (or the NPM 5 equivalent). Neither tool understands the other's lockfile format. So if we have MSBuild targets that invoke yarn, things will only behave consistently if the developer is also using yarn themselves when they do package installations/upgrades. Since this forces us to pick one of the two, it's safer to pick npm because everyone who has Node also has NPM.

And if not, would it be okay to add it as a flag?

That would be possible, but then we have a new possible failure condition where the two lockfiles are inconsistent and our tests give false positives (e.g., we have the correct version for something in yarn.lock but the wrong version in npm-shrinkwrap.json).
If it's essential to use Yarn to have our tests work reliably, my first inclination would be something more like automating the process of generating a yarn.lock file from the npm-shrinkwrap.json during test execution, guaranteeing there's only one source of truth about versions.

Using Yarn.MSBuild would still force all developers to install their own copy of yarn, unless I'm mistaking how it works

Yarn is bundled in that package, no global install needed.
Yeah, I get there are bigger concerns with switching to yarn as the default. Probably not the right move at the moment. And for the sake of test reliability, it might be more work than it's worth. Thinking about this more, it's probably worth getting community feedback on this before we invest the effort. I'll open an separate issue and let's see if we get any kind of feedback on it.

I'll open an separate issue and let's see if we get any kind of feedback on it.

I'd be cautious about reading much into what replies you get from posting an issue. Anyone posting is self-selected to be a highly interested and involved developer, exactly the kind who's likely to have already installed yarn or is willing to do so. The other 90% have never heard of yarn and won't reply to the issue.

Yeah good points. You're the subject-matter expert here so I trust your judgment. I just wanted to suggest the idea independently of our test-reliability discussion on this thread.

Fixed in #148


Documentation could use an update

Goals
The documentation at  https://realm.io/docs/swift/latest/#migrations could use a slight tweak with more up to date information about how too delete Realm files.
Expected Results
The documentation could make reference to the method
public static func deleteFiles(for config: Configuration) throws -> Bool
on line 918 of Realm.swift
In the section Deleting Realm files at https://realm.io/docs/swift/latest/#migrations, the documentation explains a way to delete Realm files with FIleManager, but RealmSwift actually seems to provide a better approach via the method deleteFiles(for config Configuration:).  It would be helpful if this method were mentioned in the documentation.
Actual Results
embarrassment: A client asked me to look into whether I should be using the code recommended in the documentation in my project for him.  I snapped back that this was the approach recommended by Realm at their site, so it must be the right way.  I then found the above method while researching something else and had to eat crow. Not fun.
Steps for others to Reproduce
The error is with the documentation, so I guess reading the documentation is all that needs to happen...

Hi @jaywardell,
Thank you for your suggestion.
I am working on a PR to update the documentation and will let you know as soon as it's done.
Kind regards,
Dominic

Hi @jaywardell,
Thank you for your suggestion.
I am working on a PR to update the documentation and will let you know as soon as it's done.
Kind regards,
Dominic

@jaywardell You can find the updated version at https://realm.io/docs/swift/latest/#deleting-realm-files
Thanks for pointing this out!

@jaywardell You can find the updated version at https://realm.io/docs/swift/latest/#deleting-realm-files
Thanks for pointing this out!

@jaywardell You can find the updated version at https://realm.io/docs/swift/latest/#deleting-realm-files
Thanks for pointing this out!

Thanks Dominic. That was fast.

@jaywardell You can find the updated version at https://realm.io/docs/swift/latest/#deleting-realm-files
Thanks for pointing this out!

Thanks Dominic. That was fast.


Upgrade to dotnet 3.1 to support current Azure Cloudshell

Rebased to clean up the history and merge issues.


Fix Text Align

Add this Code to fix the Align text, because the it was inverted the justify left and right.
Also I use the anchor to set in the same place that sprite graphic in the origin 0x , 0y in the local position from the text .
http://pixijs.download/release/docs/PIXI.Text.html#anchor

You are Welcome, I hope to help you more frequently. This is an interested project!
Thanks! :)


ERROR: relation "search" does not exist (SQLSTATE 42P01)

During first run and clean database:
2024/03/04 11:12:25 log.go:24: OK<PHONE_NUMBER>4715_init.sql (136.28ms)
2024/03/04 11:12:25 log.go:24: goose: successfully migrated database to version:<PHONE_NUMBER>4715
2024/03/04 11:12:25 main.go:37: starting server at http://<IP_ADDRESS>:7070
2024/03/04 11:13:06 worker.go:105: Refreshing feeds
2024/03/04 11:13:07 item.go:372: ERROR: relation "search" does not exist (SQLSTATE 42P01)
2024/03/04 11:13:08 item.go:372: ERROR: relation "search" does not exist (SQLSTATE 42P01)
2024/03/04 11:13:08 item.go:372: ERROR: relation "search" does not exist (SQLSTATE 42P01)

I see that search isn't supported yet. Are you planning to port that to postgres?

Yes it's been on my backlog since I reworked things but I haven't gotten around to it. Feel free to implement it if you want but it doesn't really affect the usability of the app as far as I can tell. I'll get around to it soon :tm: ;)


Java indexer: add callgraph edges [phab:D704]

Created by schroederc at 2016-02-10 22:32:20:
See: https://www.kythe.io/docs/schema/callgraph.html

schroederc wrote at 2016-02-10 22:41:05:
Doc

zarko accepted this revision at 2016-02-10 23:40:16

schroederc closed via commit a38ae8ec5ceae38c5d874c53962d95a82a035039 at 2016-02-11 16:40:36


Maven wrapper doesn't work with spaces in quotes

mvnw doesn't work

mvn works for spring-petclinic

mvnw in another spring project works for it.

@Eskibear we don't need an issue and a PR. A PR is enough.
Closing in favour of #405


remove executable on parser_test.go

What problem does this PR solve?
It seems that the parser_test.go should not be executable.
What is changed and how it works?
chmod -x parser_test.go
Check List
Tests

Unit test

Code changes
Side effects
Related changes

LGTM

there are some files in ast dir that should not be executable.
could you fix them by the way?

Ok, I will trim them later today.
kennytm<EMAIL_ADDRESS>周三06:27写道：

@kennytm approved this pull request.
LGTM
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pingcap/parser/pull/458?email_source=notifications&email_token=ACF4VXUHN5SHGSMF337TNGTQEMYNVA5CNFSM4IK6C4B2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCBO6LQY#pullrequestreview-274589123,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACF4VXQIN7UJGY2JWNOQ3BDQEMYNVANCNFSM4IK6C4BQ
.


New version: Google.Chrome.Canary version 129.0.6623.0

Created by 🥟 Dumplings in workflow run #6931.

Log
Updated: 129.0.6622.0 → 129.0.6623.0
Submitting WinGet manifests
Creating manifests
Uploading manifests and making commits
Creating a pull request

Microsoft Reviewers: Open in CodeFlow

/azp run

/azp run

/azp run


dev_providerconfigs not find

in config/crd/kustomization.yaml
use
 resources:
- bases/terraform.core.oam.dev_configurations.yaml
- bases/terraform.core.oam.dev_providerconfigs.yaml

the  bases/terraform.core.oam.dev_providerconfigs.yaml not find in bases/

@lxd5866 Thanks for reporting this issue.
My bad, I changed bases/terraform.core.oam.dev_providerconfigs.yaml to bases/terraform.core.oam.dev_providers.yaml, but I didn't update config/crd/kustomization.yaml. Fix in https://github.com/oam-dev/terraform-controller/pull/6
As the standard name for Terraform HCL/JSON files is Configuration, I changed ProviderConfig to Provider.


fix: conflict metric on watched resource not found

This is intended to fix a scenario where watched CRD is deleted and the watch ends and attempts to restart. In this scenario a conflict metric may not have been reported if the watch fails before receiving a deleted event.
Follow up to https://github.com/GoogleContainerTools/kpt-config-sync/pull/1366

/assign @karlkfi


Windows SDL setup isn't needed any more

Since https://github.com/pimoroni/32blit-beta/pull/433 is merged, it should be possible to drop ci/install_sdl_vs.sh and the reference in build.yml.

Good point; seems to work fine without it so I will now try and work out how to merge a PR (if I can...)

Looks like I have a new place to create work for @Gadgetoid :)

Realised I can remove the script as well as the call to it, which should have come through in the PR too (if I did it right)


Microsoft Libman Restore failing

Hi,
I use microsoft libman to manage my assets but i've a problem with<EMAIL_ADDRESS>when I restore, sometimes I've this problem:
It's in french but the download fail for http://unpkg.com/<EMAIL_ADDRESS>Microsoft.Web.LibraryManager.Contracts.ResourceDownloadException: Le téléchargement de la ressource à partir de "http://unpkg.com/<EMAIL_ADDRESS>a échoué
   at Microsoft.Web.LibraryManager.WebRequestHandler.GetStreamAsync(String url, CancellationToken cancellationToken)
   at Microsoft.Web.LibraryManager.CacheService.DownloadToFileAsync(String url, String fileName, CancellationToken cancellationToken)
   at Microsoft.Web.LibraryManager.CacheService.RefreshCacheAsync(IEnumerable`1 librariesCacheMetadata, CancellationToken cancellationToken)
   at Microsoft.Web.LibraryManager.Providers.Unpkg.UnpkgProvider.RefreshCacheAsync(ILibraryInstallationState state, CancellationToken cancellationToken)
Failed to restore "{<EMAIL_ADDRESS>unpkg, wwwroot\lib\@fortawesome/fontawesome-free}"
  - [LIB010]: Le téléchargement de la ressource à partir de "http://unpkg.com/<EMAIL_ADDRESS>a échoué

What can be the reason ?

This should be fixed now.

Thanks
https://www.youtube.com/watch?v=oRdxUFDoQe0
PS: sorry

https://unpkg.com/<EMAIL_ADDRESS>always a problem

This still always fails and locks up Visual Studio whilst it tries. Will there ever be a solution? Only happens with Font Awesome although there was a phase when it was happening with packages on cdnjs but this resolved itself.
I have to comment out the section in libman and I have also found that if I add any more packages to libman that any commented out lines are deleted.

For c# projects I use libman and now I made like this:
    {
      "provider": "cdnjs",
      "library"<EMAIL_ADDRESS>      "destination": "wwwroot/lib/font-awesome/"
    }

(I use cdnjs for font-awesome)

@robinwilson16
For c# projects I use libman and now I made like this, I use cdnjs for font-awesome, but the problem is still here for unpkg.
    {
      "provider": "cdnjs",
      "library"<EMAIL_ADDRESS>      "destination": "wwwroot/lib/font-awesome/"
    }

Hello, thanks that works for me too.
I couldn't find Font Awesome on CDNJS at all previously so either I was looking in the wrong place or it has been re-added.
Thanks for the info.
Robin

Yes no problem @robinwilson16 but I think the problem need to be resolved and its not the case @mjackson

Yes this should not be closed and say it is fixed as it never was and has remained an issue unless the fix is to not use unpkg for any projects.
At least now it is on cdnjs it doesn't matter if unpkg are unable to resolve their issue, well until cdnjs next goes down! Always good to have a backup.


msvcp140.dll missing on win 7

Hi everyone :)
I installed Tensorflow on Windows 7 ultimate with Python 3.5.4, via the pip3 install --upgrade tensorflow command. It even stated it successfully installed version 1.4
But if I try to invoke import tensorflow as tf in the shell I get the following error:

Of course I installed the recommended Visual C++ 2015 Redistributablle 64bit Update 3, but there is neither the .dll file in my system folder, nor does tensorflow work. I get the same error as before.
Any help is appreciated, Thank you :)

@simonhuber95 This sounds like a problem that's specific to your machine or installation, rather than a problem with TensorFlow.  I'd suggest investigating online for msvcp140.dll problems.
E.g. this StackOverflow issue suggests downloading Visual C++ Redistributable for Visual Studio 2015:
https://stackoverflow.com/questions/32998902/msvcp140-dll-missing
Closing this out, since there isn't much we can do on the TensorFlow side to fix this.


[PE-D][Tester C] Traces of AB3 still remain in CLI

In the above image, the app logs Initializing AddressBook and Stopping AddressBook when starting and exiting your app. This could be confusing to the user as your app name is EduConnect, not AddressBook.
Instead, you could change the app name in your logs to your app name EduConnect upon start up and exiting of the program.

Labels: severity.Low type.DocumentationBug
original: limyixiang/ped#3

Not 100% sure if it's a bug (meaning we can fix it) but even then, not a big issue for us to worry about


Fix delivery locations endpoint for M2 items

Fixes delivery locations endpoint for M2 items. The function existed to retrieve delivery locations by M2 customer code, but the route wasn't calling it.
Also:

Improves a long-standing issue where we query SCSB for all barcodes regardless of their holding location (which should be used to restrict the queried barcodes to just those items that have ReCAP holding locations). Now we only query SCSB for ReCAP customer codes for those items that have ReCAP holding locations.
Centralize item barcode extraction and ReCAP holding location check.

Was this work overlooked or just not ticketed?

Was this work overlooked or just not ticketed?

Should have been part of https://jira.nypl.org/browse/SCC-3415


Remove caveat about importWorkboxFrom: 'local' and InjectManifest

New functionality was added to Workbox in https://github.com/GoogleChrome/workbox/pull/1290
This PR updates the Workbox docs to reflect the change.

:+1:

:tada: This has been pushed live to https://developers.google.com/web/


logicalcluster machinery refactoring

[x] Create a new repo, github.com/kcp-dev/logicalcluster

[x] Move github.com/kcp-dev/apimachinery/pkg/logicalcluster into the root of the above repo, rename LogicalCluster to Name (put in name.go) https://github.com/kcp-dev/logicalcluster/pull/1
[x] Add script to verify there are no k8s.io/* imports https://github.com/kcp-dev/logicalcluster/pull/1
[x] Enable said script in CI https://github.com/kcp-dev/logicalcluster/pull/1
[x] Tag logicalcluster repo v1.0.0 https://github.com/kcp-dev/logicalcluster/releases/tag/v1.0.0

[x] Remove logicalcluster from kcp-dev/apimachinery https://github.com/kcp-dev/apimachinery/pull/26
[x] Update kcp-dev/kubernetes to use new repo/package
[ ] ~Remove the Cluster struct from https://github.com/kcp-dev/kubernetes/blob/feature-logical-clusters-1.23/staging/src/k8s.io/apiserver/pkg/endpoints/request/context_cluster.go#L34-L41 - we only need logicalcluster.Name from above~ edit: I'm actually adding something to this struct, so let's keep it for now.

should we also add an item here to remove logicalcluster from github.com/kcp-dev/apimachinery?

I've got branch with the cluster struct removed but don't think I got all the references to it cleaned up properly

I actually need it for #1072 - just realized that today. I updated the description to strike through that line.


compactor: Warnings on optional retention

Thanos version: 0.17.2
Im getting from compactor this logs already exists in bucket:
{"caller":"retention.go:31","level":"info","msg":"start optional retention","ts":"2021-01-24T10:24:56.260315417Z"}
{"caller":"retention.go:40","id":"01EWPFEQGWTB8E5YA5JYGEMXA9","level":"info","maxTime":"2021-01-21 00:00:00 +0000 UTC","msg":"applying retention: marking block for deletion","ts":"2021-01-24T10:24:56.260335143Z"}
{"caller":"block.go:143","err":"file 01EWPFEQGWTB8E5YA5JYGEMXA9/deletion-mark.json already exists in bucket","level":"warn","msg":"requested to mark for deletion, but file already exists; this should not happen; investigate","ts":"2021-01-24T10:24:56.261179244Z"}
{"caller":"retention.go:40","id":"01EWPJ0M3BT302Y5348G1DFK7X","level":"info","maxTime":"2021-01-21 00:00:00 +0000 UTC","msg":"applying retention: marking block for deletion","ts":"2021-01-24T10:24:56.261200393Z"}
{"caller":"block.go:143","err":"file 01EWPJ0M3BT302Y5348G1DFK7X/deletion-mark.json already exists in bucket","level":"warn","msg":"requested to mark for deletion, but file already exists; this should not happen; investigate","ts":"2021-01-24T10:24:56.261993065Z"}
{"caller":"retention.go:46","level":"info","msg":"optional retention apply done","ts":"2021-01-24T10:24:56.262015451Z"}

I don't know exactly why
This are the retention congiruation:
  retentionResolutionRaw: 3d
  retentionResolution5m: 30d
  retentionResolution1h: 1y

Any idea why he prints it out ?

Hello @kfirfer, could you provide a little more information about your stack? Let's make sure you run a single instance of the compactor. And also this could happen when compactor hasn't finished its run. Do you see any unexpected shutdown for the compactor process?

Hey @kakkoyun, I am experiencing the same issue, and am also on v0.17.2.
We are running a single compactor instance on a K8S cluster, pushing to an S3 bucket.  We do not see any shut downs / restarts of the compactor pod.  Our retention configuration is as follows:
--retention.resolution-raw=14d
--retention.resolution-5m=30d
--retention.resolution-1h=180d

This is occurring only on our production instance. We have an integration instance on the same version and with different retention periods 7d / 14d / 30d where this issue is not occurring.

reopened

Closing for now as promised, let us know if you need this to be reopened! 🤗

/reopen

@kfirfer @Robbie558 hello! do you resolve problems with not working retention? I have the same troubles

Hi,
I am new to Thanos project, and this same issue brought me here.
Retention policies:
--retention.resolution-1h = 20d
--retention.resolution-5m =15d
--retention.resolution-raw = 4d

In my case, a configuration error was causing the data to not be deleted. Specifically, despite being run on Docker, the directory specified with --data-dir was not set as persistent storage, causing the issue.
In my environment which is in the evaluation phase, containers are frequently being recreated. This was causing the deletion flags to be set again, resetting the deletion wait time and ultimately, preventing the data from being deleted.

Hello,
I have a similar problem here. We are running prometheus and thanos (sidecar, store, compact, query) in containers on a "cluster" environment with two nodes. A few day ago, I have updated to thanosio/thanos:v0.32.5 (and prom/prometheus:v2.47.2).
This morning, I found messages from thanos compact like these on all nodes:
2024-01-10T10:18:43.776690123+01:00 compact: stdout F {"caller":"block.go:185","err":"file 01HCH6CKY1HZZJQ1QMYQCP9QEM/deletion-mark.json already exists in bucket","level":"warn","msg":"requested to mark for deletion, but file already exists; this should not happen; investigate","ts":"2024-01-10T09:18:43.775840039Z"}
In my case, data-dir IS persistent (see below).
Any hint how to resolve this situation?
I have already tried to stop compactor, move the file, start compactor again. No success :-(
Here is how tha thanos compact containers are set up:
podman create -t --pod pod_prometheus --restart unless-stopped --user 1001:1001
--log-opt path=/data/monitoring/data/logging/compact_c1_n2.json
--log-level=warn
-v /data/monitoring/etc/thanos:/etc/thanos
-v /data/monitoring/data/logging:/data/logging:rw
-v /data/monitoring/data/compact:/data/compact:rw
-v /data/monitoring/data/store:/data/store:rw
--name compact
thanosio/thanos:v0.32.5  compact
--log.level=warn  --log.format=json
--data-dir=/data/compact
--objstore.config-file=/etc/thanos/bucket.yml
--http-address=<IP_ADDRESS>:10906
--http-grace-period=10s
--retention.resolution-raw=90d
--retention.resolution-5m=120d
--retention.resolution-1h=150d
--consistency-delay=30m
--wait
--wait-interval=1m
Appreciate your input :-)

Joining thread since I have had the same issue, running in k8s
However, it went away after a few days, the number of warn messages kept getting smaller and smaller and then disappeared.
So to me it seems this has something to do with slowly processing the data or something.

Facing similar issue :
=01HN0MJXQVXER7ZBRCDCERZV2W
ts=2024-01-31T08:15:34.203847082Z caller=block.go:185 level=warn group="0@{monitor="prometheus", replica="prometheus-0"}" groupKey=0@3532490200403507638 msg="requested to mark for deletion, but file already exists; this should not happen; investigate" err="file 01HN0MJXQVXER7ZBRCDCERZV2W/deletion-mark.json already exists in bucket"
ts=2024-01-31T08:15:34.204125119Z caller=compact.go:1256 level=info group="0@{monitor="prometheus", replica="prometheus-0"}" groupKey=0@3532490200403507638 msg="marking compacted block for deletion" old_block=01HN0MMRAVXBDQQDGDDY1JBXPY
ts=2024-01-31T08:15:34.205521779Z caller=block.go:185 level=warn group="0@{monitor="prometheus", replica="prometheus-0"}" groupKey=0@3532490200403507638 msg="requested to mark for deletion, but file already exists; this should not happen; investigate" err="file 01HN0MMRAVXBDQQDGDDY1JBXPY/deletion-mark.json already exists in bucket"
ts=2024-01-31T08:15:34.205815917Z caller=compact.go:1256 level=info group="0@{monitor="prometheus", replica="prometheus-0"}" groupKey=0@3532490200403507638 msg="marking compacted block for deletion" old_block=01HN0MPJXV1PDV06V06W54898F
ts=2024-01-31T08:15:34.207107562Z caller=block.go:185 level=warn group="0@{monitor="prometheus", replica="prometheus-0"}" groupKey=0@3532490200403507638 msg="requested to mark for deletion, but file already exists; this should not happen; investigate" err="file 01HN0MPJXV1PDV06V06W54898F/deletion-mark.json already exists in bucket"
ts=2024-01-31T08:15:34.207502477Z caller=compact.go:1256 level=info group="0@{monitor="prometheus", replica="prometheus-0"}" groupKey=0@3532490200403507638 msg="marking compacted block for deletion" old_block=01HN0MRDGVTD1D5MTQZTD2FH1H
ts=2024-01-31T08:15:34.209100892Z caller=block.go:185 level=warn group="0@{monitor="prometheus", replica="prometheus-0"}" groupKey=0@3532490200403507638 msg="requested to mark for deletion, but file already exists; this should not happen; investigate" err="file 01HN0MRDGVTD1D5MTQZTD2FH1H/deletion-mark.json already exists in bucket"
ts=2024-01-31T08:15:34.209387556Z caller=compact.go:1256 level=info group="0@{monitor="prometheus", replica="prometheus-0"}" groupKey=0@3532490200403507638 msg="marking compacted block for deletion" old_block=01HN0MT83VP357JF8FTWKX52D4
ts=2024-01-31T08:15:34.211040192Z caller=block.go:185 level=warn group="0@{monitor="prometheus", replica="prometheus-0"}" groupKey=0@3532490200403507638 msg="requested to mark for deletion, but file already exists; this should not happen; investigate" err="file 01HN0MT83VP357JF8FTWKX52D4/deletion-mark.json already exists in bucket"
ts=2024-01-31T08:15:34.211320093Z caller=compact.go:1256 level=info group="0@{monitor="prometheus", replica="prometheus-0"}" groupKey=0@3532490200403507638 msg="marking compacted block for deletion" old_block=01HN0MW2PTCM367DWZM2FRKJEG
Also seeing the number of Objects increasing rapidly in Object Store .
Object Storage used: Open Stack swift
thanos : /thanos:v0.32.5
args:
- compact
- --log.level=info
- --data-dir=/tmp/thanos-compact
- --objstore.config-file=/creds/swift_access_info.yml
###- --sync-delay=5m
- --retention.resolution-raw=2d
- --retention.resolution-5m=10d
- --retention.resolution-1h=30d
- -w
###- --delete-delay=24h
###- --sync-block-duration=5m
- --compact.concurrency=15
Object Storage NUmber of Objects counts increasing rapidly:
Object Count45202
Size223.18 GB
Date CreatedJan 1, 1970
Public AccessLink


SAK-42839 Syllabus: Update success and error banners.

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

See the complete overview on Codacy

Ok @fostersdesign , replaced all those banners by sak-banner-warn.

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 1

See the complete overview on Codacy


Providing options to build

Hi,
I am trying to mimic the following command using this gem, but couldn't figure out how to provide the options like --pull. Can you please help me?
$ docker build --pull -t myimage:latest -f docker/Dockerfile docker/

It seems I figured it out. Sorry for the noise. Will be back if anything else comes in the way.


RequestHeader set X-Forwarded-Context /gitblit does not affect repositoryURL in Website

Hello, this might be a duplicate of:  Barnum (pt) download link is incorrect for war deployment #898
I have gitblit GO behind a Apache 2.2 webserver with mod_proxy. I have set
RequestHeader set X-Forwarded-Context /gitblit
as I need to run different services on this vhost.
This works fine so far, but when I open a repository on the gitblit WebSite and look for the git repository URLs, I miss the "/gitblit" part.
I see
<EMAIL_ADDRESS>but it should be:
<EMAIL_ADDRESS>

Odd.  The url generation supports X-Forwarded-Context.

Huh.  What if you set X-Forwarded-Proto or X-Forwarded-Port ?

This is the section in my apache ssl.conf vhost:
ProxyPass /gitblit http://localhost:8080/gitblit
ProxyPassreverse /gitblit http://localhost:8080/gitblit
Header edit Location ^http://([^/]+)/gitblit/ https://$1/gitblit/
RequestHeader set X-Forwarded-Proto https
RequestHeader set X-Forwarded-Port 443
RequestHeader set X-Forwarded-Context /gitblit
AllowEncodedSlashes NoDecode

fixed it, no bug - but a configuration issue: forgot to specify the /gibtlit part in the web.canonicalUrl parameter
Sorry for this issue,
Olaf


Virtual Arrays: Step Repeat as Node-Type

Proof of concept.

Add Special Operation: Virtual Array.
Virtual Array currently limited to 2x2 50% 50% for bed size.
Virtual Array does not simulate accurately.

Not sure I particularly like the name VirtualArray - RepeatGrid might be a better name.
If I read the code correctly, you create an Opnode which is a VirtualArray anywhere in the op tree and this holds details of the repeats and steps) and when you execute, the existence is noted and an additional step added at the end of the plan to do the repeat step - in which case it would do the step repeat on the optimised cut-code.
I am not sure whether using a special Opnode is the way to go - in my Design / Prepare / Burn philosophy (Design being tools to manipulate elements, Prepare being tools to set up the operations, Burn being Execute & Simulate combined, then I might want to be able to set the step-repeat values in Prepare (where they would be saved as special ops when I save the SVG file) or alternatively to dynamically add the step-repeat in fields in a panel on the Burn screen.

This isn't an opnode since those are references to elems, it's just an operation subnode specifically a virtualarray node type.


Passing props for Required PropTypes

I have a component that requires a function (onIncrement). Is there a way to specify the prop when it's initialized? When there are multiple examples, I can pass in props for each, but I didn't see a way to do this when there aren't tabs.
I usually see errors like this:
Warning: Failed propType: Required prop `onIncrement` was not specified in `Counter`. Check the render method of `SG.Sections`.

Would help to see an example; we do not support a tab-less experience at the moment (PR welcome). The 'Example' tab renders out what you return in render()
https://github.com/theogravity/react-styleguide-generator-alt/blob/master/example/components/Features/Additional examples via doc comment.js


Add issuer template to Helm chart

Every time after installing cert-manager via Helm we need to create Issuer/ClusterIssuer
I'm suggest to add a template to chart and make it possible to set issuer in values.yaml
/kind feature

This has been asked before, and is not going to be accepted. You should create this in your own chart/configuration file after installing cert-manager, else we'll be replicating the API schema for (Cluster)Issuer into the helm values file without any versioning capability.
It is also incompatible with the --installCRDs option too.
Some more background here: https://github.com/jetstack/cert-manager/issues/259 (and I think there's a few other issuers over the past few years where we've gone into this)


Respect watchFiles and watchDirs in the transform return

This allows transform to also set watchFiles and watchDirs in its return.  Its useful for implementing PostCSS directory dependency messages (e.g. for tailwindcss JIT watching).

Thank you for spotting and fixing this!


No class found Exception setting up DataConnector in attributes-resolver.xml

Working with 5.1.0-SNAPSHOT and trying to setup Shibboleth attributes-resolver.xml.  We need to use a different ldap connection than what we use to authenticate for attribute resolution.  Getting the following error when deploying with an attributes-resolver.xml that has a DataConnector defined.
Caused by: java.lang.NoClassDefFoundError: org/ldaptive/provider/ConnectionStrategy
	at net.shibboleth.idp.attribute.resolver.spring.dc.ldap.impl.LDAPDataConnectorParser.doV2Parse(LDAPDataConnectorParser.java:134) ~[idp-attribute-resolver-spring-3.2.1.jar:?]
	at net.shibboleth.idp.attribute.resolver.spring.dc.impl.AbstractDataConnectorParser.doParse(AbstractDataConnectorParser.java:157) ~[idp-attribute-resolver-spring-3.2.1.jar:?]
	at org.springframework.beans.factory.xml.AbstractSingleBeanDefinitionParser.parseInternal(AbstractSingleBeanDefinitionParser.java:85) ~[spring-beans-4.3.4.RELEASE.jar:4.3.4.RELEASE]
	at org.springframework.beans.factory.xml.AbstractBeanDefinitionParser.parse(AbstractBeanDefinitionParser.java:61) ~[spring-beans-4.3.4.RELEASE.jar:4.3.4.RELEASE]
	at net.shibboleth.ext.spring.util.BaseSpringNamespaceHandler.parse(BaseSpringNamespaceHandler.java:96) ~[spring-extensions-5.2.0.jar:?]
	at net.shibboleth.ext.spring.util.SchemaTypeAwareBeanDefinitionParserDelegate.parseCustomElement(SchemaTypeAwareBeanDefinitionParserDelegate.java:66) ~[spring-extensions-5.2.0.jar:?]
	at net.shibboleth.ext.spring.util.SchemaTypeAwareBeanDefinitionParserDelegate.parseCustomElement(SchemaTypeAwareBeanDefinitionParserDelegate.java:49) ~[spring-extensions-5.2.0.jar:?]
	at net.shibboleth.ext.spring.util.SpringSupport.parseCustomElement(SpringSupport.java:178) ~[spring-extensions-5.2.0.jar:?]
	at net.shibboleth.ext.spring.util.SpringSupport.parseCustomElements(SpringSupport.java:157) ~[spring-extensions-5.2.0.jar:?]
	at net.shibboleth.idp.attribute.resolver.spring.impl.AttributeResolverParser.parse(AttributeResolverParser.java:68) ~[idp-attribute-resolver-spring-3.2.1.jar:?]
	at net.shibboleth.ext.spring.util.BaseSpringNamespaceHandler.parse(BaseSpringNamespaceHandler.java:96) ~[spring-extensions-5.2.0.jar:?]
	at net.shibboleth.ext.spring.util.SchemaTypeAwareBeanDefinitionParserDelegate.parseCustomElement(SchemaTypeAwareBeanDefinitionParserDelegate.java:66) ~[spring-extensions-5.2.0.jar:?]
	at net.shibboleth.ext.spring.util.SchemaTypeAwareBeanDefinitionParserDelegate.parseCustomElement(SchemaTypeAwareBeanDefinitionParserDelegate.java:49) ~[spring-extensions-5.2.0.jar:?]
	at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.parseBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:178) ~[spring-beans-4.3.4.RELEASE.jar:4.3.4.RELEASE]
	at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.doRegisterBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:142) ~[spring-beans-4.3.4.RELEASE.jar:4.3.4.RELEASE]
	at org.springframework.beans.factory.xml.DefaultBeanDefinitionDocumentReader.registerBeanDefinitions(DefaultBeanDefinitionDocumentReader.java:94) ~[spring-beans-4.3.4.RELEASE.jar:4.3.4.RELEASE]
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.registerBeanDefinitions(XmlBeanDefinitionReader.java:508) ~[spring-beans-4.3.4.RELEASE.jar:4.3.4.RELEASE]
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.doLoadBeanDefinitions(XmlBeanDefinitionReader.java:392) ~[spring-beans-4.3.4.RELEASE.jar:4.3.4.RELEASE]
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:336) ~[spring-beans-4.3.4.RELEASE.jar:4.3.4.RELEASE]
	at org.springframework.beans.factory.xml.XmlBeanDefinitionReader.loadBeanDefinitions(XmlBeanDefinitionReader.java:304) ~[spring-beans-4.3.4.RELEASE.jar:4.3.4.RELEASE]
	at org.springframework.beans.factory.support.AbstractBeanDefinitionReader.loadBeanDefinitions(AbstractBeanDefinitionReader.java:181) ~[spring-beans-4.3.4.RELEASE.jar:4.3.4.RELEASE]
	at net.shibboleth.ext.spring.util.SpringSupport.newContext(SpringSupport.java:125) ~[spring-extensions-5.2.0.jar:?]

Is ldaptive anywhere on the classpath?

yes, in cas-server-support-ldap

Share your resolver xml please.

<resolver:DataConnector id="ucdLDAP" xsi:type="dc:LDAPDirectory"
    ldapURL="LDAP_URL"
    baseDN="BASE_DN"
    principal="PRINCIPAL"
    principalCredential="CREDENTIAL"
    useStartTLS="true">
    <dc:FilterTemplate>
        <![CDATA[
            (uid=$requestContext.principalName)
        ]]>
    </dc:FilterTemplate>
</resolver:DataConnector>

On Fri, Dec 2, 2016 at 10:12 AM Misagh Moayyed<EMAIL_ADDRESS>wrote:

Share your resolver xml please.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apereo/cas/issues/2157#issuecomment-264522158, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABdcAMoMMQxiprjXqql0GKj2xrleaMmrks5rEF-GgaJpZM4LC0Ex
.

Looks like I found the issue.  The shibbleth IdP jars appear to be compiled against Ldaptive 1.1.1 and the 5.1.0-SNAPSHOT was updated to 1.2.1

Possibly, but I do see the same missing class in 1.2.1 as well. My guess is that when the IdP context is created to resolve attributes, it's not loading the ldaptive jar at all.

ConnectionStrategy was removed from Ldaptive 1.2.1.  If you look at
LDAPDataConnectorParser from the shib-idp-3.2.1.jar, it is trying to use
ConnectionStrategy which only exists in versions of Ldaptive < 1.2.0
On Fri, Dec 2, 2016 at 2:09 PM Misagh Moayyed<EMAIL_ADDRESS>wrote:

Possibly, but I do see the same missing class in 1.2.1 as well. My guess
is that when the IdP context is created to resolve attributes, it's not
loading the ldaptive jar at all.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apereo/cas/issues/2157#issuecomment-264575836, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AS0kvbEBeXDdl-ZmY838xH7gRpwTQoE2ks5rEJcHgaJpZM4LC0Ex
.

OK we did a little checking. If you review ldaptive tags on github you'll find the ConnectionStrategy available for both 1.2.1 and 1.2.0. However, it seems like it's not quite available for 1.1 and below which makes sense since the IdP uses an older version of it.
Have you tried forcing 1.0.x for ldaptive and see if that makes a difference? What's your use case?

It looks like it has been refactored to reside a package higher. The idp
jar is looking for it under org.ldaptive.provider.   I tried to
downgrade to 1.1.1, but then Beans.java and other ldap config classes
complained.
On 12/02/2016 02:39 PM, Misagh Moayyed wrote:

OK we did a little checking. If you review ldaptive tags on github
you'll find the |ConnectionStrategy| available for both 1.2.1 and
1.2.0. However, it seems like it's not quite available for 1.1 and
below which makes sense since the IdP uses an older version of it.
Have you tried forcing 1.0.x for ldaptive and see if that makes a
difference? What's your use case?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apereo/cas/issues/2157#issuecomment-264581729, or
mute the thread
https://github.com/notifications/unsubscribe-auth/AS0kvWReH2WOp5x2x4kWPKGHCALm3lDdks5rEJ4VgaJpZM4LC0Ex.

I tried upgrading to shib idp 3.3.0 library jar, but I get the same
error.  It looks to me like it might be built with version 1.0.9
https://build.shibboleth.net/nexus/content/repositories/thirdparty/org/ldaptive/ldaptive/
For CAS to be compatible it would need to be downgraded.
On 12/02/2016 02:39 PM, Misagh Moayyed wrote:

OK we did a little checking. If you review ldaptive tags on github
you'll find the |ConnectionStrategy| available for both 1.2.1 and
1.2.0. However, it seems like it's not quite available for 1.1 and
below which makes sense since the IdP uses an older version of it.
Have you tried forcing 1.0.x for ldaptive and see if that makes a
difference? What's your use case?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apereo/cas/issues/2157#issuecomment-264581729, or
mute the thread
https://github.com/notifications/unsubscribe-auth/AS0kvWReH2WOp5x2x4kWPKGHCALm3lDdks5rEJ4VgaJpZM4LC0Ex.

Gotcha. We are not going to downgrade; you could potentially open a JIRA with Shibboleth and ask them to upgrade to latest ldaptive? That may already be on the roadmap in fact.

Actually we might be able to circumvent this somehow; I think rather than having you use an attribute-resolver.xml file we might be able to adopt the same strategy we have with person directory and just manually autowire everything based on cas properties. So we'd just be using data connectors as a framework underneath and we could expose properties for ldap and rdbms data connectors easily. I think this strategy will basically have you declare attribute definitions in an xml file (and that we might also be able to do away with, specially if we let each resolver control its own attributes as is described in #2083 )

I started down that path Friday afternoon then I found
cas.ldap.attributesRepository which should do exactly what I am looking
for.  I will verify it first thing in the morning that it works.  Maybe
just need to note that DataConnectors of type LDAPDirectory will not be
supported in Shibboleth attribute-resolver.xml.
On Sun, Dec 4, 2016 at 5:46 PM Misagh Moayyed<EMAIL_ADDRESS>wrote:

Actually we might be able to circumvent this somehow; I think rather than
having you use an attribute-resolver.xml file we might be able to adopt the
same strategy we have with person directory and just manually autowire
everything based on cas properties. So we'd just be using data connectors
as a framework underneath and we could expose properties for ldap and rdbms
data connectors easily. I think this strategy will basically have you
declare attribute definitions in an xml file (and that we might also be
able to do away with, specially if we let each resolver control its own
attributes as is described in #2083
https://github.com/apereo/cas/issues/2083 )
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/apereo/cas/issues/2157#issuecomment-264750291, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABdcAOcPDMn0G0zyRoHg5lSWdloVP_ITks5rE2zjgaJpZM4LC0Ex
.

Yup. We very well could advertise; I am however moving more and more towards removing the ability to support the xml file. At the time when we supported this behavior, configuring person-directory was just too difficult, but now that it's all props-based I wonder if we could just automate it all. What do you think?

I have made sure the crash is accounted for and caught with a warning message. I will also update the docs for the time being to make the ldap incompatibilities known. Thanks very much for the report. LMK if you find anything buggy on the attributes side.

FYI https://issues.shibboleth.net/jira/browse/IDP-1095


feat(influxdb): add path and protocol to config input

Draft PR to add protocol and path to influxdb client
closes #205

tested and works well :)

This looks pretty clean and nice @maurerle, let me please just re-test it in my environments and I think it will be ready to merge...

@maurerle I have (with your kind permission) adjusted couple things to make it better fit the rest of the code.
The InfluxDB settings layout is now responsive single line to consume less space. The http|https is now specified for app config where I think it belongs, and not just for the InflxuDBBackend... the rest is just tweaks and housekeeping and addressing TS errors...
Could you please test whether it works as expected before we merge it?

works well, LGTM :)

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Decorator for more easily implementing common agent flows (e.g. ReAct)

Description

partially sparked from the discussion in #709

The original goal for Mirascope was to provide a single-order abstraction on top of LLM APIs to provide a more consistent interface across providers. We're continuing to improve this with new features, and we're actively working towards making the interface even more provider-agnostic (see #729).
I firmly believe Mirascope should remain a lightweight toolkit (rather than trying to do everything), but I also see value in implementing second-order abstractions on top of our call decorators to make it easier to implement common flows. Since we already have mirascope.core, this won't remove the lower-level control we often want when implementing more complex flows. Instead, we'll implement separate functionality that (optionally) operates on top of the existing functionality.
Here is my rough thought:
from mirascope.core import Messages
from mirascope.agents import agent

@agent.react("openai:gpt-4o-mini", tools=[...])
def customer_support_bot(query: str) -> Messages.Type:
    return [
        Messages.System("You are a customer support bot"),
        Messages.User(query),
    ]

response = customer_support_bot("I need help with my recent bill")
print(response.content)  # agent's final string response
print(response.messages)  # the full history of messages that went into producing the response

The idea here would be that the @agent.react decorator operates just like the llm.call decorator would except that under-the-hood it will run through the ReAct tool calling flow and call the tools on behalf of the user. Everything else should work the same (including things like response_model, structured streaming, dynamic configuration, etc.).
Alternatively, we could create an Agent class and have the @agent.react decorator return an Agent instance (thus operating as shorthand). For example:
from mirascope.agents import Agent

agent = Agent(...)

@agent.tool()
def tool(...) -> ...: ...

@agent.system_prompt()
def system_prompt(...) -> str: ...

Then, the above customer_support_bot definition would instead be an Agent class (rather than a function), and we could call it moreso like customer_support_bot.run(...).
Biggest thing to think through will be how to best write the prompt such that you can make multiple sequential calls to the agent while injecting history. My thinking here is that is that we'll do something like always inject history into the array of messages right before the final user message and always ahead of the system message, and the resulting decorated method (i.e. customer_support_bot) would accept a keyword argument (e.g. history or messages) for the running history.
One benefit of the Agent class is that it enables more internal state management of the message history. The downside of this approach if not done correctly would be removing too much user control. We'll have to strike the right balance between what Mirascope handles and what the user handles (or some version of overriding so that the user can optionally take back control when desired/necessary).
This feature request is very early and definitely requires additional thought, so any and all feedback is welcome here.

Could we use MCP to standardize context handling for agents? If so, Mirascope could be the first framework to implement it. By providing a set of community-supported context protocols, MCP would accelerate agent development by eliminating the need to re-implement common functionalities like:

Environment interaction (database access, tool usage)
Short-term and long-term memory management

This would allow developers to focus on building the agent's core logic instead of repeatedly building the same context management infrastructure. What do you think?

We're currently working on adding support for MCP. We have the server side implemented but still need to iron out the details on the client side. Once we figure that out, we should be able to hook the MCP client up to Mirascope calls, so hooking it up to an agent as described here should be possible.
I really like the idea of standardization on context, and MCP seems like the perfect fit for that.

@minhquan23102000 we just released MCP support in v1.12, would love to know your thoughts. I think the way we've implemented it should make it easy to hook the client up to an llm call (or new agent decorator as described in this issue) to easily provide tools/resources etc. through a common interface for all providers.


 tag deprecated in HTML5

Replaced all occurrences of <strike>  tag and styling rules with HTML5
compliant <del> tag.

Thanks for improving the semantics of the slides!


Added UPLC for untyped Plutus core, and smaller changes

This patch mainly adds the UPLC module.
It also adds

elam2 for two argument lambas
Some StandaloneKindSignatures
Removes constraints from Core.Term definition.
Replaced Dict with Coercion.

https://github.com/Plutonomicon/plutarch-plutus/issues/501

Replaced by https://github.com/Plutonomicon/plutarch-plutus/pull/575


update server metrics

changes include -

https://github.com/metamx/server-metrics/pull/8 - Add custom
dimensions for Jvm and Sys monitors
https://github.com/metamx/server-metrics/pull/9 - Add net, tcp,
uptime and cpu metrics

LGTM


Feature Request Map resize?

So my corp has need for more space on the map in height not in width is there a option to change this? or can i edit css code?, if so can i get some info on this?

:grey_exclamation: Duplicate Issue
Thanks for your contribution. There is already an open Issue about this topic. "Layout" #470
Feel free to participate in the discussion and share your thoughts in the comments.
:x: Issue closed

Auto-generated response


Automatic PR from RestAPI-PR2225

Generated from RestAPI PR: https://github.com/Azure/azure-rest-api-specs/pull/2225

See https://github.com/Azure/azure-sdk-for-python/pull/1923


fix(docs): update access control link

Corrected a non-functioning hyperlink in the access control documentation

Closed because this wrong link is in many places in the docs.
Better to do everything in one PR


path.parse is only available in node 0.12

Massive uses path.parse in the walkSqlFiles helper function. However this method is only available in node 0.12 (and not in 0.10).
This means that the users can't use the "SQL Files as Functions" functionality. If I place a .sql file in the "db" directory, massive will crash immediately with:
TypeError: Object #<Object> has no method 'parse'

I believe it means that users can’t use this functionality unless they’ve upgraded, which, in your case, appears to be the problem. So my choice is to change the codebase, impacting our current users, publish a change and make sure nothing breaks… or you just upgrade your Node install.
As a software developer, which would you choose?
On April 28, 2015 at 2:46:44 PM, Paulo Vieira<EMAIL_ADDRESS>wrote:
Massive uses path.parse in the walkSqlFiles helper function. However this method is only available in node 0.12 (and not in 0.10).
This means that the users can't use the "SQL Files as Functions" functionality. If I place a .sql file in the "db" directory, massive will crash immediately with:
TypeError: Object # has no method 'parse'
—
Reply to this email directly or view it on GitHub.

I note a bit of irony in your reply, which is probably justified given the lack of clarity in my message.
Obviously this is only a "problem" for those who don't want (or can't) upgrade from 0.10 to 0.12. But given that 0.12 is only a few weeks old and people have had apps in production using 0.10 for a long time, I would say the percentage of developers who would like to try massive and are using 0.10 is quite large.
I would suggest at least adding the "engines" property to package.json (or simply adding the 0.12 requirement to the readme). If that information is not present, I would assume the module works with 0.10.
By the way, the parse-filepath module seems to be a good substitute for path.parse:
https://www.npmjs.com/package/parse-filepath
If there's interest, I'm happy to submit a PR with this change, thus making massive compatible with 0.10 (hopefully).

Thank you :) and yes, that would be lovely (a PR)

On Apr 29, 2015, at 03:42, Paulo Vieira<EMAIL_ADDRESS>wrote:
I note a bit of irony in your reply, which is probably justified given the lack of clarity in my message.
Obviously this is only a "problem" for those who don't want (or can't) upgrade from 0.10 to 0.12. But given that 0.12 is only a few weeks old and people have had apps in production using 0.10 for a long time, I would say the percentage of developers who would like to try massive and are using 0.10 is quite large.
I would suggest at least adding the "engines" property to package.json (or simply adding the 0.12 requirement to the readme). If that information is not present, I would assume the module works with 0.10.
By the way, the parse-filepath module seems to be a good substitute for path.parse:
https://www.npmjs.com/package/parse-filepath
If there's interest, I'm happy to submit a PR with this change, thus making massive compatible with 0.10 (hopefully).
—
Reply to this email directly or view it on GitHub.

Solved with PR


link from CQRS

[Enter feedback here]
Good information. A minor comment in last section:
For a comparison of CQRS with other architectural styles, see Architecture styles.
There's no comparison of CQRS in "Architecture styles", maybe want to link to "https://docs.microsoft.com/en-us/azure/architecture/patterns/ " ?

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

ID: 0c0ec92e-c237-f3a6-1835-f2078486dcb3
Version Independent ID: f597c9a2-f18f-3722-57f9-acd535472b0b
Content: Command and Query Responsibility Segregation (CQRS) pattern - Cloud Design Patterns
Content Source: docs/patterns/cqrs.md
Service: architecture-center
Sub-service: cloud-fundamentals
GitHub Login: @dragon119
Microsoft Alias: pnp

Hi @tao-sj - Thank you for your feedback! We have assigned this issue to the author to review further and take the right course of action.

@tao-sj - Thanks, we originally had CQRS as one of the styles but we demoted it 😸 ... as it's really more of a design pattern.


Fix a bunch of docs

This task tracks a bunch of doc fixes needed, most are quite short and small and fixes can be combined in a single PR:

[ ] Fix for subspace NUFFT related docs in https://mind-inria.github.io/mri-nufft/nufft.html#subspace-projection-model
[ ] References in CG example https://mind-inria.github.io/mri-nufft/generated/autoexamples/GPU/example_cg.html needs to be made same as other example, i.e. at the end.
[ ] In CG method, make sure math is used for Ax = B in first cell.
[ ] https://mind-inria.github.io/mri-nufft/generated/autoexamples/GPU/example_learn_samples_multicoil.html : model_sense_op seems some minor fixes.
[ ] Get utils.py somehow to binder/collab https://github.com/mind-inria/mri-nufft/blob/master/examples/utils.py

FYI: CG example has "Inpirations" instead of "Inspirations"


Reintroduce local temp state

and extract stripped debug info into filesystem
Signed-off-by: Kemal Akkoyun<EMAIL_ADDRESS>

The error we got from CodeQL is a bit weird. I'll consider it as a flake for now and I'll fix it if it happens again.

Feel free to merge since this was opened from your fork.


Kicad Gerber File Board outline not detected by JLCPCB

Hello,
i created the Gerber files wit KiCad and uploaded it to JLCPCB, but the outlines are not detected.

This are my settings.

I tried different settings, but every time the same problem.
Any suggestions?

Can output correct gerbers with those settings.
What version are you using?

It works. Many thanks.
I use version 6.0.0-rc1-dev-1291

@BenRoe do you mind sharing the gerber files for crone classic please? I met similar issues on JLCPCB. thank you!

I'm also ordering from JLCPCB. What size should I indicate?


Common Data Model folder view not supported in Power Query Online

Power Query Online, does not seem to support "Common Data Model" folder view and that distinction I think would be good to call out.

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

ID: de89bef7-dbd7-c901-d329-f9838f8dbaf9
Version Independent ID: 583cc4ae-3fdb-0d6c-6314-8aaf8e51e922
Content: Analyze data in Azure Data Lake Storage Gen2 by using Power BI
Content Source: powerquery-docs/Connectors/DataLakeStorage.md
Service: powerquery
GitHub Login: @bensack
Microsoft Alias: bensack

Hi @rajrao -
This feature was introduced in February 2021.


Manifests and configs downloaded for all platforms by default

Description

Manifests and configs downloaded for all platforms by default when we pull an image from ctr.
More detailed discussions can be found in comment https://github.com/containerd/containerd/pull/3067#discussion_r267840771.
 For example, the manifest 59db9e5cc365f2f493317d3cf4847f02671fd88e9164acfbf464467df8f4cfdc is for ppc64le platform and has nothing to do with the layer we will download
Output of containerd --version:
containerd github.com/containerd/containerd v1.2.0-329-ga15b6e20.m a15b6e2097c48b632dbdc63254bad4c62b69e709.m

Which is the master head when I produced the output.

This should be fine.  Only the layers for your current platform are fetched, the manifests and configs are minimal in size.  Are there any bugs coming from this default functionality?

@crosbymichael if we can get the cross repository push logic to work without first downloading, we might be able to consider changing the default back. In that case the push logic will need to be able to read manifests from the registry during push, which is a permission the push flow should already have to accomplish that. I think we can keep this open for now.


Package Requested

[X] I would like someone else to build the manifest.
[ ] I would like help so I can submit the manifest.
[ ] I have performed a search and couldn't find this package.
[ ] I have checked that the installer for this package is not a standalone or portable executable or a .zip file
[ ] I think there is a new version available and I have provided the URL.

Please provide the following information
Publisher: KDE e.V.
Publisher Url: http://kde.org
Package Name: KDE.Konversation.Nightly
Description: http://apps.kde.org/konversation
Package Version: master-973
Installer URL: http://binary-factory.kde.org/view/Windows 64-bit/job/Konversation_Nightly_win64/lastSuccessfulBuild/artifact/konversation-master-973-windows-msvc2019_64-cl.exe
Current Package Identifier (for new versions): master-973

Duplicate of #39190
Please post your KDE requests here


Fixed IN Onboarding Failed Test Messages

This PR fixed the following:
Accession numbers for the failed ones - 3558a700-e5a3-494b-b0b8-bf6ae1004166 9ef9098e-c4b2-4916-b1c2-a5f53aa75851
They are for VDF Unity facility with CLIA - 14D2212079.
Error description is - The code for Ordered Test name is missing. Blank identifiers in segments HL7LabReport.HL7PATIENT_RESULT.ORDER_OBSERVATION.ObservationRequest.UniversalServiceIdentifier
Test Steps:

./gradlew clean package
./

Changes

Include a comprehensive list of changes in this PR
(For web UI changes) Include screenshots/video of changes

Checklist
Testing

[x] Tested locally?
[x] Ran ./prime test or ./gradlew testSmoke against local Docker ReportStream container?
[ ] (For Changes to /frontend-react/...) Ran npm run lint:write?
[ ] Added tests?

Process

[ ] Are there licensing issues with any new dependencies introduced?
[ ] Includes a summary of what a code reviewer should test/verify?
[ ] Updated the release notes?
[ ] Database changes are submitted as a separate PR?
[ ] DevOps team has been notified if PR requires ops support?

Linked Issues

Fixes #issue

To Be Done
Create GitHub issues to track the work remaining, if any

#issue

Specific Security-related subjects a reviewer should pay specific attention to

Does this PR introduce new endpoints?

new endpoint A
new endpoint B

Does this PR include changes in authentication and/or authorization of existing endpoints?
Does this change introduce new dependencies that need vetting?
Does this change require changes to our infrastructure?
Does logging contain sensitive data?
Does this PR include or remove any sensitive information itself?

If you answered 'yes' to any of the questions above, conduct a detailed Review that addresses at least:

What are the potential security threats and mitigations? Please list the STRIDE threats and how they are mitigated

Spoofing (faking authenticity)

Threat T, which could be achieved by A, is mitigated by M

Tampering (influence or sabotage the integrity of information, data, or system)
Repudiation (the ability to dispute the origin or originator of an action)
Information disclosure (data made available to entities who should not have it)
Denial of service (make a resource unavailable)
Elevation of Privilege (reduce restrictions that apply or gain privileges one should not have)

Have you ensured logging does not contain sensitive data?
Have you received any additional approvals needed for this change?

This PR add the iHealth COVID-19 Antigen Rapid Test,97097-0,"iHealth COVID-19 Antigen Rapid Test_iHealth Labs, Inc.",,Y,,,,,, with Equipment UUID blank back to the LIVD-Supplemental.csv.


Add rustic-test-failure to compilation-error-regexp-alist

Add regexp to compilation-error-regexp-alist to match test failures for rustic-cargo-test-mode.
This make test output like
---- fail stdout ----
thread 'fail' panicked at src/main.rs:20:5:
assertion `left == right` failed
  left: 1
 right: 2

navigatable.
Closes #573

Please note that I'm not so sure about the error type / level. Mabe 0 or 1 would be more suitable.

The more I think about it, the more I feel this was the wrong approach and rustic-compilation-panic needs to be fixed. #575

Closed in favor of #575.


Java support

Adds java support for recompilation, code completion, go to declaration and go to documentation #208.

 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.You have signed the CLA already but the status is still pending? Let us recheck it.

Looks like the travis build is broken:
Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.17' not found (required by /home/travis/atom/usr/share/atom-beta/resources/app/apm/node_modules/git-utils/build/Release/git.node)

According to this issue the travis build should use the trusty distribution instead of precise. Maybe this fixes the build?
The tests are successful on my machine..

Cool! Thanks a lot for this!
Could you try changing to trusty in this PR and see if it helps?
I'll merge anyway, but maybe that's fastest… :)

Works. ;)

Awesome, thanks!


There is no need to create SSH key-pair per user

@rutgervandeelen
In the code referred below, you seem to check and create a SSH key pair per user.  This is to my understanding not necessary.
The entire QaaS can just use one key pair with the private key held by (and only accessible for) the QaaS service user; while the public key is distributed into users' ~/.ssh/authorized_keys file.  This already allows QaaS service user to SSH into individual user's account.
https://github.com/Donders-Institute/hpc-qaas/blob/9bb5d69688f42c2e565113340027bb9cdacca184/internal/server/handlers.go#L81

You are correct. I will pick this up as soon as possible.


Can't edit the capture image

i make the package work well and i can take snaps but i can't edit it it automaticly saved on my gallery!

@abdallaemadeldin  @WeslleyNasRocha Can you share your code of App.js?

@SwagatRanjit84 mine use of this component was this
<SafeAreaView style={{
    height,
    width,
    backgroundColor: '#000'
  }}>
  <AndroidScanner
    ref={ref => (this.androidScanner = ref)}
    onPictureTaken={(data) => {console.log(data)}}
    noGrayScale
    onProcessing={() => this.setState({ scannerReady: false })}
    enableTorch={torch}
    style={PixelRatio.get() >= 3
      ? {
        flex: 1,
        marginBottom: height * 0.16,
        marginTop: height * 0.04
      }
      : {
        flex: 1
      }}
    detectionCountBeforeCapture={6}
  />

</SafeAreaView>

@WeslleyNasRocha please share complete App.js code
onPictureTaken directly storages image on phone and throws only path of image. I want image data, but not store directly on phone. Any idea?

@SwagatRanjit84 Most of the time you only need the path. What do you want to do?


added container dependencies to docker compose

Pull Request Test Coverage Report for Build 28

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 100.0%

Totals

Change from base Build 26:
0.0%

Covered Lines:
1883

Relevant Lines:
1883

💛  - Coveralls


Incorrect use of process_request silently aborts connections

async def process_request(path, headers):
    return (200, [], b"Hello, world")

async def main():
    async with websockets.serve(connection, "localhost", 8000, process_request=process_request):
        await asyncio.Future()

The documentation for process_request correctly says that the first value should be an HTTPStatus; however, this example passes a plain int instead.
Expected result: An exception is thrown or displayed on the console. (Or ideally, this particular case should work correctly, since IntEnum and integer are mostly interchangeable.)
Actual result: The exception is swallowed by # Last-ditch attempt to avoid leaking connections on errors and the connection is summarily closed with no message to client or console.
Requesting that the last-ditch handler report errors to the console, possibly with a message indicating how this could be suppressed.

I completed your example as follows:
#!/usr/bin/env python

import asyncio
import websockets

async def connection(ws):
    await asyncio.sleep(1)
    await ws.send("it works")

async def process_request(path, headers):
    return (200, [], b"Hello, world")

async def main():
    async with websockets.serve(connection, "localhost", 8000, process_request=process_request):
        await asyncio.Future()

if __name__ == "__main__":
    asyncio.run(main())

It doesn't crash:
$ curl -v http://localhost:8000/
*   Trying <IP_ADDRESS>:8000...
* Connected to localhost (<IP_ADDRESS>) port 8000 (#0)
> GET / HTTP/1.1
> Host: localhost:8000
> User-Agent: curl/8.1.2
> Accept: */*
>
< HTTP/1.1 200 OK
< Date: Sat, 21 Oct 2023 13:30:35 GMT
< Server: Python/3.11 websockets/12.0.dev36+ged6cb1b
< Content-Length: 12
< Content-Type: text/plain
< Connection: close
<
* Closing connection 0
Hello, world%

It was fixed in #1309..

Ahh cool, that solves this particular issue. It may still be possible to cause other types of errors that will silently abort connections though. Is there any other way to write the handler that will result in the same last-ditch exception handler being triggered?

Based on code inspection, in the old asyncio implementation, you should get an HTTP 500 error and a message at the ERROR log level in that case.
In the new asyncio implementation and the threading implementation, there's a test to check that an HTTP 500 error is returned if process_request or process_response raise an unexpected exception. See test_process_request_raises_exception and test_process_response_raises_exception.

Requesting that the last-ditch handler report errors to the console, possibly with a message indicating how this could be suppressed.

I don't want to do this because it can be very noisy with connection error, misbehaving clients, and internet background noise, depending on the context in which you're deploying websockets.
Configuring logging in Python is tricky: you can configure it only once. (Technically, you can attempt to reconfigure it, but the behavior is so tricky that everyone gets it wrong; that's why I say that you can configure it only once.) Since websockets is a library and doesn't know in which context it will be used, it would be inappropriate from websockets to take over configuration of logging. I expect the developer of the application to do it in a way that makes sense for their context.
See https://websockets.readthedocs.io/en/stable/topics/logging.html#configure-logging


Add option to select rolltemplate format

see:
https://app.roll20.net/forum/permalink/9567975/

Hey @MadCoder253!
I'm looking to make my first code contribution, and I love D&D. I would love to help out, but I'm not sure exactly what you're looking for in a template. I'm going to do my part and ask a web dev friend to get some clarification, but let me know if you have a moment to talk it over with me, and I'll get right on it!
Cheers,
Jeff

Hi @JGarnerDev !
I have the templates worked out. For the GURPS sheet there's the main rolltemplate that has a lot of custom coding. I recently added a new simple rolltemplate for users to use with custom macros. In the rolltemplate, there's an option to select a style type. There's Basic, DnD5e and Pathfinder. The basic is like the current main rollemplate, with the option to select color sets. DnD5e and Pathfinder are styles that I took from Roll20s wiki page. This task is just adding the ability for users to use DnD5E and Pathfinder styles with the main rolltemplate.


cinder-csi-plugin does not have options for leader election

Of all the containers in the pod template of the  csi-cinder-controllerplugin StatefulSet, docker.io/k8scloudprovider/cinder-csi-plugin is the  only one that does not appear to have options for leader election.
Isn't this a requirement to run in HA with a multi-replica Deployment?

/assign
I am not expert, but I can take a look, if I will not able to fix it, I will unassign myself :)

/kind feature

ok, I mostly figured this out, will submit a PR soon..

@adisky it shows to me that we are using RPC server here, while some other containers like external-provisioner is using controller, my search shows the leader election only applied to controller, so do we have any comments on whether we still can use leader election here?

@jichenjc if leader election is not necessary for this particular container, then the StatefulSet with replicas=1 should be replaced with a Deployment with appropriate leader election flags on the containers that support it.
The comments in the docs suggest that the StatefulSet is being used precisely to avoid having more than one pod at all times... this led me to believe that leader election is not yet supported.

ok, I will take another look at this and paste some comments if I have . thanks for the info~ @bgagnon

just for record, I think using CSI-lib https://github.com/kubernetes-csi/csi-lib-utils will be a good choice to include leader election stuff as manila CSI did, then in turn encounter some issue and need fix https://github.com/kubernetes-csi/csi-lib-utils/pull/32 first

@jichenjc any updates on this issue?

/remove-lifecycle stale

sorry, busy in other stuffs recently, I unassign myself and will continue to work on it later if someone is not going to work on it

/remove-lifecycle stale

/remove-lifecycle stale

/assign

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle rotten

I don't understand why do we need to add leader election flag to driver. Leader election (lease) in case of csi are only for controllers to avoid race condition when watching/updating resources on api server. However csi driver act only as a gRPC server and which serves requests by other csi controllers (the ones that already support leader election). Only the one controller which is leader calls its side-car driver.


Time ranges in "zed lake log" not printed as timestamps (regression at dcce5c2)

Repro is with Zed commit dcce5c2.
Notice the presentation of the time: values in the last line of the following:
$ zed -version
Version: v0.29.0-341-gdcce5c22

$ rm -rf $ZED_LAKE_ROOT

$ zed lake init
using environment variable ZED_LAKE_ROOT
lake created: file:///Users/phil/logs

$ zed lake create -p logs -orderby ts:desc
pool created: logs

$ zed lake load -p logs ~/work/zed-sample-data/zeek-default/snmp.log.gz
1txOhfwBqD5PekxEQTlAD4ivziW committed 1 segments

$ zed lake log -p logs
commit 1txOhfwBqD5PekxEQTlAD4ivziW
Author<EMAIL_ADDRESS>Date:   2021-06-14T21:49:54Z

    Add 1txOhlkccB7oHqdkXIZJ96bEpBs 2KiB950B bytes 65 records
       from time: (00 52 5a 1c 89 d7 3d 2a) to time: (60 35 95 90 57 d5 3d 2a)

This behavior started appearing at that Zed commit dcce5c2, which is associated with #2729 (cc: @mccanne). In Zed commit 7c92f41 that came right before that one, these appeared in the expected ISO timestamp format.
$ zed -version
Version: v0.29.0-340-g7c92f41f

$ rm -rf $ZED_LAKE_ROOT

$ zed lake init
using environment variable ZED_LAKE_ROOT
lake created: file:///Users/phil/logs

$ zed lake create -p logs -orderby ts:desc
pool created: logs

$ zed lake load -p logs ~/work/zed-sample-data/zeek-default/snmp.log.gz
1txP29yUwEQPnqfO112R9k8AHCq committed 1 segments

$ zed lake log -p logs
commit 1txP29yUwEQPnqfO112R9k8AHCq
Author<EMAIL_ADDRESS>Date:   2021-06-14T21:52:37Z

    Add 1txP2DKHSY6kPIKyK63sKrau0Q0 4KiB581B data 2KiB950B file 65 records
       from 2018-03-24T17:35:53Z to 2018-03-24T17:15:47Z

Verified in Zed commit 6cc190b.
Repeating the repro steps, we see that the final output of the log now shows properly-formatted timestamps.
$ zed -version
Version: v0.29.0-392-g6cc190b9

...

$ zed lake log -p logs
commit 1uJETrZhoysOuunb8hao7P6WWAB
Author<EMAIL_ADDRESS>Date:   2021-06-22T15:21:42Z

    Add 1uJETwzInpg4T8qNfwo62KllNTb 2998B bytes 65 records
       from 2018-03-24T17:35:53.529248Z to 2018-03-24T17:15:47.618446Z

Thanks @mccanne!


Added new metrics to be scraped from in cluster monitoring

Jira: https://issues.redhat.com/browse/RHSTOR-3346
Signed-off-by: Kaustav Majumder<EMAIL_ADDRESS>

quick info, are these needed for ocs alerts?

@leelavg these are the metrics we need to also federate when observatorium is integrated, but not sure if they will be used for any ocs alerts.
Referring to this Jira: https://issues.redhat.com/browse/RHSTOR-3346

@ezio-auditore Please rebase

@nb-ohad  this should only go when #208 is merged. These are all in-cluster monitoring metrics hence no use federating them now.

@nb-ohad this should only go when https://github.com/red-hat-storage/ocs-osd-deployer/pull/208 is merged. These are all in-cluster monitoring metrics hence no use federating them now.

@ezio-auditore You can add do-not-merge/hold label to this PR :smile:

@ezio-auditore What is the status of this PR?  is the fix still viable? are we going to close it or merge it?

still viable, i would like to rebase with main and test it

Closing this, since we are only pushing metrics from provider clusters and the metrics mentioned in the PR are only related to consumer clusters.