xSQLServerDatabaseOwner: Helper function Get-SqlDatabaseOwner is missing localization key 'FailedToGetOwnerDatabase'

Details of the scenario you try and problem that is occurring:
Helper function Get-SqlDatabaseOwner is referencing localization key 'FailedToGetOwnerDatabase' but it does not exist in xSQLServer.strings.psd1.
Localization key needs to be added with a correct descriptive error message.
The DSC configuration that is using the resource (as detailed as possible):
n/a
Version of the Operating System, SQL Server and PowerShell the DSC Target Node is running:
n/a
Version of the DSC module you're using, or 'dev' if you're using current dev branch:
Dev

Bug fixed in PR #409


docs: add Scorecard badge

Looks good to me. Thank you for doing that and for keeping the high Score bar!


Consider use of RESTful term in the guidelines

The guidelines lead with term RESTful, and while there are some use of the constraints, use of hypermedia in particular is limited (mostly to drive pagination).
They guidelines don't argue against REST, but nor do they advocate strongly for example, for content models that use a state machine driven approach, where transitions are performed by clients working with document links.
It's arguable then, the term could be removed from the leading material and point to the discussion elsewhere in the document on tradeoffs.
If done, this might require a new github project as "restful" is in the project url.

Linking the trigger of this: https://twitter.com/stilkov/status/806979435429773312 :smirk:

Still waiting for an answer to https://twitter.com/ebowman/status/807154435755536384 ...

The reply: https://twitter.com/stilkov/status/807219063185408000
Github API,, of course :)

Github API,, of course :)

Totally disagree. They just provide links for reading. There is not state changed initiated through links.

I personally think this discussion is rather academic and provides no value for us. However, I propose to complement our guidelines with the footnote that we stick to usage of the term for our REST approximations (like the very industry majority) --> see #169


Allow Gyro to enable API's

GCP requires services are enabled before they are set to be in use. When running gyro up for the first time, we encounter errors such as:
Identity and Access Management (IAM) API has not been used in project xxxxxxxxxxxxx before or it is disabled. Enable it by visiting https://console.developers.google.com/apis/api/iam.googleapis.com/overview?project=xxxxxxxxxxxxx then retry. If you enabled this API recently, wait a few minutes for the action to propagate to our systems and retry.
This requires enabling in the console, and isn't ideal for starting up new projects.
We should have a way to enable GCP API's through Gyro so this isn't such a manual process

Docs for implementation ref: https://cloud.google.com/service-usage/docs/libraries#java


Model efficiency

Thanks for your open code.  I want to know that how much time for one epoch（like compGCN-ConvE）?

Hi @zhifei1993,
It depends on the dataset at hand. As far as I remember, on FB15k-237 it used to take around 2-3 days to converge which is around 300 epochs. So it is not that slow.


Feat :sparkles: Fix PS8 compatibility by disabling hook execution

Adding a message to the dashboard in order to install the new version of MBO

Questions
Answers

Branch?
2.0.x

Description?
Fix the PS8 compat. The hooks are not executed anymore, so the module does not break the shop. Add a  panel to the dashboard that link the user to the addons page of the module. Problem saw here

Type?
bug fix / improvement

Translations are still missing. Also, the design of the panel may be changed.

I close this PR because the autoupgrade module will correctly update the ps_mbo module during an upgrade between 1.7.8 -> 8.0 of PS.


Release v0.9.0

Make the release v1.0.0 if cosmos-sdk graduates from release candidate status.

Blocked by https://github.com/iov-one/iovns/issues/265.


#0: CMake: Remove stdlib interface library

Ticket
NA
Problem description
Cleanup
Avoid needing to export this library at install time.
Don't use i/f library for libc++ linkage, we are propagating it everywhere, even deps. Just use global flags.
https://github.com/tenstorrent/tt-metal/pull/14320/files#diff-1e7de1ae2d059d21e1dd75d5812d5a34b0222cef273b7c3a2af62eb747f9d20aR51-R59
What's changed

Remove the interface library "stdlib"
Move project_dir check after project command
Organize project options into local cmake module

Checklist
https://github.com/tenstorrent/tt-metal/actions/runs/11535260653

[ ] Post commit CI passes
[ ] Blackhole Post commit (if applicable)
[ ] Model regression CI testing passes (if applicable)
[ ] Device performance regression CI testing passes (if applicable)
[ ] New/Existing tests provide coverage for changes

@afuller-TT
Having an after thought.
Should we propagate the -stdlib=libc++ compiler flag to consumers of tt_metal ?
this pr does not consider that.
normally that would require setting it as a public “target_compile_option” I think.
If we don’t do it, people could run into nasty linker errors due to libc++ vs libstdc++ clashing.
I really hope we can get rid of libc++ so no one has to think about this in the future.

normally that would require setting it as a public “target_compile_option” I think.

I think we can do this later if it becomes an issue
But let’s not worry for now unless you want to
if clang and enable_libcxx
target_compile_options(tt_metal PUBLIC -stdlib=libc++)

Should we propagate the -stdlib=libc++ compiler flag to consumers of tt_metal ?

No.  Could you imagine pulling in 2 different dependencies and each one decided to force "their" compiler settings/toolchain?  The top-level should decide on the toolchain.  If we only support a specific toolchain we should document that.  But ideally we should be capable of operating with most toolchains.
Certainly this "we only work with the non-default lib" is going to bite someone sooner or later.  Hopefully we can come back around to fix it before it does bite someone.


Finish converting docstrings

This PR aims to wrap up the docstring conversion.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Do we really want to render type hints? It feels quite bloated and not very readable.

The comments should have been taken care of. If this works for you, @adrinjalali, I'd like to merge this PR in the feature branch and acentralize the discussion about next steps there.


How can I hide a View

Is there a way to hide view and save the current state of the view?
I tried
this.ref.element.setNativeProps({
    hidden: true
});

but failed.
Is it possible to expose native components hidden` property.
It would be great if there is a way to hide the element and save its state.

The react native philosophy is that you shouldn't (I think), there has been some discussion around supporting display:none, however simply removing the view from the tree saves memory, which is about as vital as saving the re-render, depending on your use case.  If you really need this, you could expose that property from a custom view in obj-c.

As @JohnyDays  said, in React, you should change your View based on your current State.

@checkraiser  I tried to create some component like TabBarIOS with customed button to toggle the content views without reset the content`s state every time.
Is there any way to achieve that?

Yes, i still not try, but i think you can wrap your view into a Custom View, then use the property subView.hidden=YES in your View Manager.
Good luck.

@checkraiser  Thx!!!

Or try set height to 0

If you need measurements for said view set opacity to 0 instead of height

@JohnyDays +1

please refer to this answer in stack overflow hide show component

You can use my module react-native-display to show/hide components.

You can use my module react-native-display to show/hide components.

https://medium.com/@maulikdhameliya/how-to-make-view-visible-invisible-in-react-native-8532c4bd0957


Any options set on a javadoc task will now be included in the task uptodate check

Fixes #4841

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

Changes to how known options are calculated ensures that if new options are added to these classes (in a newer version of javadoc), maintainers will not have to remember to add them to a separate list of known options.

@bot-gradle test this

OK, I've already triggered the following builds for you:

PullRequestFeedback build

@bot-gradle test this

@bot-gradle test and merge


[5.6] Streamline the dropIndex handling on \Illuminate\Database\Schema\Blueprint

Changed?
Added an optional index name property as in $table->index();
Why?
When using $table->index('some_field'); the $this->createIndexName(); method is used to build an index name because no custom name was specified. So assuming you simple want to delete your created some_field index and using $table->dropIndex('some_field'); it will not work because the index name was created as tablename_some_field_index by the default basic convention.
This also fixed the case when creating an joined index with an specified index name. So for $table->createIndex(['some_field', 'some_other_field'], 'fields_index'); $table->dropIndex('fields_index'); wont work again because of that basic convention.

This PR changes some method signatures. As such it is a breaking change and should target the 5.7 release (the master branch). There's also 22 broken or failing tests from these changes.

@sisve just saw the travis-ci... also I haven't thought about the breaking change thing. Thanks for the fast response, will look into 5.7 release.

You can use $table->dropIndex(['some_field']); and then it will recreate that name for you.
Notice the [ and ] bracket

@victorlap good point. But the index usage is not really intuitive when just coming from the docs. You currently need to look into the souce code to know that you can specify an index name or to learn about that basic name convention. Maybe I should just PR the docs instead.

It is mentioned in the docs, under Database > Dropping Indexes

If you pass an array of columns into a method that drops indexes, the conventional index name will be generated based on the table name, columns and key type:

If you expected to find this somewhere else, I suggest you PR the docs.

Okay, will PR the docs and try to make that more clearer.


The entity name must immediately follow the '&' in the entity reference

Plug-in Version 3.4.0

As for the title the error message it's the same

"The entity name must immediately follow the '&' in the entity reference"

tested also on version 3.3.1 and this version doesn't have this issue.
Thanks

Hi @justodepp!
Do you have any sample string that I can use to reproduce the error?
Thanks!

Hi Adrían,
sure here one for example, "T & C"
this one is inside the project the one coming from POEditor it's just
something like this "T & C"
Saluti
Gianni Andrea Cavalli
Il giorno gio 18 mag 2023 alle ore 17:40 Adrián García <
@.***> ha scritto:

Hi @justodepp https://github.com/justodepp!
Do you have any sample string that I can use to reproduce the error?
Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/hyperdevs-team/poeditor-android-gradle-plugin/issues/66#issuecomment-1553248470,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AB6R4EW552BDYF3GIZTKBUTXGY7HJANCNFSM6AAAAAAYGFBWWE
.
You are receiving this because you were mentioned.Message ID:
@.***
.com>

Had the same issue just now. Because of the same string :)

Hey @justodepp @carlosrivin! Sorry for replaying so late.
I've been testing version 3.4.1 of the plug-in with these strings:
    "test_issue_66_1" -> "T&C"
    "test_issue_66_2" -> "T & C"
    "test_issue_66_3" -> "T & C"

and got the following results:
    <string name="test_issue_66_1">"T&C"</string>
    <string name="test_issue_66_2">"T & C"</string>
    <string name="test_issue_66_3">"T &amp; C"</string>

These should be the proper escape sequences so I believe the plugin is working as expected. Does the error happen when using the plugin or when compiling your apps?

We've had the same issue in one of our own projects.
PoEditor CMS contains the following string:

When using this config (which doesn't specify the unescapeHtmlTags field), we get the error:
poEditor {
    apiToken.set("xxx")
    projectId.set(123)
    order.set("terms")
    tags.set(listOf("android", "app"))
    unquoted.set(true)
}

However, when turning unescapeHtmlTags to false, it works without any issues:
poEditor {
    apiToken.set("xxx")
    projectId.set(123)
    order.set("terms")
    tags.set(listOf("android", "app"))
    unquoted.set(true)
    unescapeHtmlTags.set(false)
}

<string name="puf_details_solutions">Common problems & solutions</string>
This happens because the default value of unescapeHtmlTags is true. It seems rather confusing that we need to toggle the default value of the unescapeHtmlTags field in order to affect ampersand parsing, as it should work regardless of this config value.
A related problem is that when using unescapeHtmlTags set to false, we get HTML strings like this:
<string name="puf_details_report">Report a problem</string>
Which are not wrapped in a <![CDATA[ ... ]] block, hence are not handled properly on Android. Should this be reported as a separate bug?

This started happening in our project when we updated:
from AGP 4.2.2 + gradle 6.9 + java 8
to AGP 8.3.0 + gradle 8.4 + java 17 (build), java 11 (source)
It happens both with plugin version 3.4.2 and 4.2.0.
Caused by: org.xml.sax.SAXParseException; lineNumber: 1601; columnNumber: 59; The entity name must immediately follow the '&' in the entity reference.
        at java.xml/com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:262)
        at java.xml/com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:342)
        at com.hyperdevs.poeditor.gradle.ktx.DocumentExtensionsKt.toStringsXmlDocument(DocumentExtensions.kt:41)
        at com.hyperdevs.poeditor.gradle.xml.XmlPostProcessor.splitTranslationXml(XmlPostProcessor.kt:113)
        at com.hyperdevs.poeditor.gradle.xml.XmlPostProcessor.postProcessTranslationXml(XmlPostProcessor.kt:55)
        at com.hyperdevs.poeditor.gradle.PoEditorStringsImporter.importPoEditorStrings(PoEditorStringsImporter.kt:146)
        at com.hyperdevs.poeditor.gradle.tasks.ImportPoEditorStringsTask.importPoEditorStrings(ImportPoEditorStringsTask.kt:184)

Nice that unescapeHtmlTags = false fixes the issue. It introduces some other changes though. Some seem fine, so can be problematic.
This seems fine - it changes emoji codes/formats, but they still work.
For instance, it changes this string 🤩 into 🤩. Both resolve to the same emoji - 🤩. The first one is the emoji Hex code point (as it was originally, before upgrading AGP, gradle and Java). The second one is the Decimal code point of the same emoji.
This does not seem fine though - it encodes tags, so they don't work anymore. For instance, it breaks tags like .
You might be using this tag to make text bold in the Android UI (works even in Toast messages). For instance: John is \"awesome\", really! to output "John is "awesome", really!", it will be broken when using unescapeHtmlTags = false: John is \"awesome\", really! - which appears exactly like that in the UI.

Having the same exact issue.
Plugin version: 4.2.0
The term in POEditor is:

Enable Alarm & Reminders - issue reproduces, gradle task fails
Enable Alarm & Reminders - task succeeds, the result is "Enable Alarm & Reminders" (& breaks Android strings in that case)
Enable Alarm &amp; Reminders- task succeeds, produces correct Android string: "Enable Alarm & Reminders"


Improve performance samples and use source name in RasterizingTileLayer

Done:

Mostly samples except for one thing in the RasterizingTileLayer where the source of the RasterizingTileLayer.Name is set to the source. This is like in the RasterizingLayer.
Changed the naming of the ISample.Name and the files itself to reflect the technology used in the samples which I think is the important part for the users. This is what they need to start looking into.
Added a sample for the RasterizingTileLayer and the LineString with many vertices. It is much faster than the RasterizingLayer.


[v6] How can I dispatch 'inialiaze' in a right way?

I need to give my form new initialValues, so i need to dispatch 'initialize' action.
I tried to follow docs section on initialize:
initialize(form:String, data:Object, fields:Array<String>)
How i try to do it:
// import actionCreator & wrap it in dispatch:
import { initialize as initializeForm } from 'redux-form'
...
const ActionModalForm = reduxForm({ form: 'actionModal' })(ActionModal)
return connect(state =>
  ({ initialValues: state.actionValue}),
  { initialize: initializeForm }
)
(ActionModalForm)

//Execute init action when i need it:
initialize('actionModal', newValue)

Then in console i see action details:

So no init value were passed
My solution with redux-actions:
forceInit: createAction('redux-form/INITIALIZE', action => action, () => ({ form: 'actionModal' }))

form components are injected an initialize prop function, did you try that?

I think you forget to dispatch initialize action.

@eloytoro You are right, initialize from prop forks fine for me, thanks!


chore: use annotations from the future

The goal here is to reduce the use of the name "Scenario" in the docs, to control where it appears when the docs are included at ops.readthedocs.io.
Using from __future__ import annotations seems to make Sphinx much happier when doing the class signatures, avoiding odd text like ~scenario.state.CloudCredential instead of the expected link with text "CloudCredential" and destination that class.
When adding those imports, pyupgrade transformed all the type annotations - I wasn't previously aware that the future import made this possible in 3.8, but it seems to be the case. I've run all the tests with 3.8, 3.9, 3.10, 3.11, and 3.12 and they all pass, and I've manually tested in 3.8 and everything seems to work without any problems. I like this much more, so it seems like a win-win.
The pyupgrade pre-commit hook was running twice, one with no version restrictions for a specific file that doesn't seem to exist any more, so I've removed the duplication. I've also changed pyupgrade and pyright to target 3.8 compatibility.
A couple of docstrings are changed to use the State() style rather than scenario.State() style.

Huh, but then it fails in CI. Weird. I'll move to draft and look into this more later.

@PietroPasotti what do you think about this? I know PEP 563 is in a bit of a limbo state, but by the time that's resolved it'll be some later version of Python that supports the more minimal style of type annotations anyway, so it seems like a win to do this now? For what it's worth, I'm keen to do this in ops too.


(PUP-6831) Change reverse.each to reverse_each

Eliminate the temporary array created by reverse.each.

@puppetlabs/puppet-maintainers for review

CLA signed by all contributors.

👍


high CPU load during evaluating

Hi, I ran the code of PointPillars on KITTI dataset. I found that the CPU average load is too high when evaluating on KITTI dataset. I don't know how this phenomenon came about, and I want to know if there is a way to decrease CPU load during evaluating. Thanks!

During KITTI evaluation, all the calculation based on prediction and gt will be done on CPU, and we use numba to accelerate calculating speed, which may result in a higher CPU load, you can try to remove numba decorator in kitti_utils.py


Bootstrap stage 2 build failure in Microsoft.Build.Tasks.Git.LocateRepository task

/vmr/.dotnet/sdk/8.0.100-preview.4.23219.1/Sdks/Microsoft.Build.Tasks.Git/build/Microsoft.Build.Tasks.Git.targets(26,5): error MSB4018: The "Microsoft.Build.Tasks.Git.LocateRepository" task failed unexpectedly.
System.InvalidCastException: [A]System.Runtime.CompilerServices.StrongBox`1[Microsoft.Build.Tasks.Git.GitRepository] cannot be cast to [B]System.Runtime.CompilerServices.StrongBox`1[Microsoft.Build.Tasks.Git.GitRepository]. Type A originates from 'System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' in the context 'Default' at location '/vmr/.dotnet/shared/Microsoft.NETCore.App/8.0.0-preview.4.23217.4/System.Private.CoreLib.dll'. Type B originates from 'System.Private.CoreLib, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=7cec85d7bea7798e' in the context 'Default' at location '/vmr/.dotnet/shared/Microsoft.NETCore.App/8.0.0-preview.4.23217.4/System.Private.CoreLib.dll'.
   at Microsoft.Build.Tasks.Git.RepositoryTask.TryGetCachedRepositoryInstance(String cacheKey, Boolean requireCached, GitRepository& repository)
   at Microsoft.Build.Tasks.Git.RepositoryTask.GetOrCreateRepositoryInstance()
   at Microsoft.Build.Tasks.Git.RepositoryTask.ExecuteImpl()
   at Microsoft.Build.Tasks.Git.RepositoryTask.Execute()
   at Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
   at Microsoft.Build.BackEnd.TaskBuilder.ExecuteInstantiatedTask(ITaskExecutionHost taskExecutionHost, TaskLoggingContext taskLoggingContext, TaskHost taskHost, ItemBucket bucket, TaskExecutionMode howToExecuteTask) [/vmr/src/source-build-reference-packages/artifacts/source-build/self/src/src/targetPacks/ILsrc/microsoft.netcore.app.ref/7.0.0/Microsoft.NETCore.App.Ref.7.0.0.csproj]

This occurs in the dependency project build of SBRP when attempting to build Microsoft.NETCore.App.Ref.7.0.0.
Build link (internal only)

[Triage] The fix for https://github.com/dotnet/sdk/pull/31863 should have come in this morning so this should be fixed.

This is still not resolved.

It's possible the packages from prebuilts are causing this.  Removing them in https://github.com/dotnet/installer/pull/16176.

It's possible the packages from prebuilts are causing this. Removing them in dotnet/installer#16176.

Unfortunately it didn't resolve the issue.

@tmat, @ViktorHofer - Could you help in determining the cause of this failure?
For context, this is failing in the bootstrap build workflow where we source-build the https://github.com/dotnet/dotnet repo once and then use the outputted SDK as the toolset to build the source again. It fails in that second build.
I've attached the build's binlog:
sourcebuild-dependency-projects.zip
What's odd about the exception message is that it's complaining that Type A can't be cast to Type B even though it reports that Type A and B are the same type from the same assembly file. I suspect that it's possible the message is actually wrong here given that it's a generic type and the real casting issue is with the GitRepository type. It doesn't indicate anything about that type's assembly in the error.
Here's the relevant code doing the cast: https://github.com/dotnet/dotnet/blob/e2903bde31921e07bebca58f03f6b1395dd74802/src/sourcelink/src/Microsoft.Build.Tasks.Git/RepositoryTask.cs#L150
It's possible that use of an MSBuild registered task object is a factor here.

I took a shot in the dark and added a call to dotnet build-server shutdown right before this line:
https://github.com/dotnet/dotnet/blob/e2903bde31921e07bebca58f03f6b1395dd74802/src/source-build-reference-packages/eng/Build.props#L181
But that made no difference.

Seems like a dup: https://github.com/dotnet/sourcelink/issues/1007, https://github.com/dotnet/msbuild/issues/8478
@rainersigwald

@rainersigwald - Please work with @tmat / sourcelink folks to determine a fix or workaround for this. This is blocking the source-build release of 8.0 Preview 4.

As a workaround I can add try-catch around the cache lookup. It will be a potential build perf issue, but not correctness issue.

Here: https://github.com/dotnet/sourcelink/pull/1008

I'm gonna close this issue as it should be addressed by the above workaround. Still keeping the msbuild issue opened to track the root cause.

I'd rather keep this open until our build is actually passing.

@mthalman
The log https://github.com/dotnet/source-build/issues/3399#issuecomment-1517922022 shows there are two copies of Source Link assembly loaded to the build process:

Is this expected?

I would think that's a possibility. It would be a scenario where a project has a compile-time dependency on Microsoft.Build.Tasks.Git and the logic of the SDK has a runtime dependency on Microsoft.Build.Tasks.Git.

That shouldn't be a conflict; the compile-time dependency shouldn't be loaded by any part of MSBuild in a persistent way, while the SDK reference (UsingTask) would.
The log shows that the assembly is being loaded in the latter way from two different paths:

This looks like it might be fallout from the temporary situation where that task is present both in the SDK and via package--and I'd expect the long-term fix to be that the package goes away and only the SDK copy is used in sourcebuild.


fix: unification stmt eval scope

1. Does this PR affect any open issues?(Y/N) and add issue references (e.g. "fix #123", "re #123".):

[ ] N
[x] Y

fix #1637
fix: unification stmt eval scope

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

10 of 10 (100.0%)  changed or added relevant lines in 1 file are covered.
63 unchanged lines in 5 files lost coverage.
Overall coverage decreased (-0.09%) to 70.547%

Files with Coverage Reduction
New Missed Lines
%

kclvm/evaluator/src/scope.rs
3
89.09%

kclvm/tools/src/LSP/src/inlay_hints.rs
3
92.31%

kclvm/runtime/src/value/val_type.rs
12
62.62%

kclvm/tools/src/LSP/src/state.rs
12
82.57%

kclvm/runtime/src/value/val_union.rs
33
77.36%

Totals

Change from base Build<PHONE_NUMBER>1:
-0.09%

Covered Lines:
51204

Relevant Lines:
72581

💛  - Coveralls


[Do not merge] PR check experimental PR

Many thanks for submiting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors' guide
[ ] Pull Request title is properly formatted: [KOGITO-XYZ] Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket
[ ] Your feature/bug fix has a unit test that verifies it
[ ] You've tested the new feature/bug fix in an actual OpenShift cluster

/jenkins test

/jenkins test

Full BDD tests for https://github.com/kiegroup/kogito-cloud-operator/pull/615
There seems to be some problem with Keycloak, though possibly not related.

/jenkins test

/jenkins test


Document Library and list item Views not working with SPFx Extension.

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
💥 SharePoint Framework
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[ ] 💥 Microsoft Edge
[X] 💥 Google Chrome
[ ] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

browser version: 105.0.5195.102
SPFx version: 1.15
Node.js version: v16.14.0
etc

Describe the bug / error
I'm having issues with the document libraries and List Views in SP Online after deploying my Application Extension (React). It's the list's title and some elements with fixed top distance.

as you may see, this is where the list's title has to be. If a remove some margin directly in the element:

I tried to target the element via CSS but because of the hashing is too hard to select the element and change the value.
Steps to reproduce

Create an SPFx Extension with some height tlike 60px
Go to document Library or ListView Allitem.aspx page

Expected behavior
As in the second picture, is expected that the title does not disappear when using the extension

Hello AJIXuMuK, I'm using both placeholders. my CSS is not overriding the SharePoint css, as far as I can see.
I'm using tailwind and also hashing my classes.
here's a look of the placeholder inject

Its the same for the footer and header. Maybe is because of the height? try to increase the height on your sandbox component

Hello, any idea about this?


Add error logging to code generation

Purpose

This PR will fix syntax errors when generating the open api service using a given yaml file.

This PR has been updated to resolve https://github.com/ballerina-platform/ballerina-lang/pull/15227#discussion_r281187602 suggestion.
Fixes #15001

Codecov Report

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

@@            Coverage Diff            @@
##             master   #15255   +/-   ##
=========================================
  Coverage     23.24%   23.24%
  Complexity     5065     5065
=========================================
  Files          1342     1342
  Lines         67457    67457
  Branches       9193     9193
=========================================
  Hits          15680    15680
  Misses        50039    50039
  Partials       1738     1738

Continue to review full report at Codecov.

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


update bird config to work with bird 1.5 and above

changed 'route limit' to 'import limit' because 'route limit' won't work in bird 1.5 and above

According to your salt states you are using the stock debian jessie version (https://packages.debian.org/jessie/bird), which is 1.4.5.
https://github.com/freifunk-fulda/saltstack-config/blob/master/state/bird/init.sls#L3-L5


Update Notifications

Admin users should get a notification that a new version is available.
Information should be pulled via github releases API. Opt-out setting.

Where do you suggest this info shows up? permanently in the page-header? as an email? or only when he visits the admin section?
maybe an icon in the header which leads to the settings page containing a bigger banner, with an explanation & a link to the github release. What do you think?

I think maybe an update icon next to the admin button. Then in the admin area a header that's like
"An update is available!


chore: fix yarn.lock

SSIA, should sync yarn.lock

self mergining to make it in before segment plugin actually releases.


Implement tree item pinning

TODO: add some screenshots once I have IDs and the build is successful
TODO: is it possible to make the inline icon always visible for the "unpin" action? It seems like most of the time (across the software world in general, not necessarily just VSCode), when something is pinned, that icon is always visible.

Looks good to me. Should we revisit once we have tree item IDs figured out?

Yep, I think that makes sense. @philliphoff do you have any plans on the IDs yet?

Looks good to me. Should we revisit once we have tree item IDs figured out?

With this being merged, should we revisit this PR now?

Looks good to me. Should we revisit once we have tree item IDs figured out?

With this being merged, should we revisit this PR now?

Yes

Closing in favor of #679


[SPARK-26851][SQL][FOLLOWUP] Fix cachedColumnBuffers field for Scala 2.11 build

What changes were proposed in this pull request?
Per https://github.com/apache/spark/pull/23768/files#r259083019 the last change to this line here caused the 2.11 build to fail. It's worked around by making _cachedColumnBuffers a field, as it was never set by callers to anything other than its default of null.
How was this patch tested?
Existing tests.

Test build #102601 has started for PR 23864 at commit 351614d.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8152/
Test PASSed.

Merged build finished. Test PASSed.

lgtm. I was a little worried about cacheBuilder.copy(cachedPlan = plan) not wiping out _cachedColumnBuffers, but a quick test of case classes shows that it will.
Maybe @maropu wants to take a look?

Yeah I had a look at why on earth constructors can have multiple arg lists (i.e. there is no such thing as currying here), and the reasons I could find didn't apply here. I'm not sure why this existed in this way.

Test build #102601 has finished for PR 23864 at commit 351614d.

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

Merged build finished. Test FAILed.

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

retest this please

Test build #4563 has started for PR 23864 at commit 351614d.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/8160/
Test PASSed.

Test build #102609 has started for PR 23864 at commit 351614d.

LGTM

Test build #4563 has finished for PR 23864 at commit 351614d.

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

Thanks! Merged to master.

Test build #102609 has finished for PR 23864 at commit 351614d.

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

Merged build finished. Test PASSed.

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


Please improve the component filtering and add the postal_code feature

Hi,
In the Geocoding of google, you have now the possibility to do a restriction on the postal code.
You can append this like that : components=country:CH|postal_code:8000
Here the documentation from Google : Geocoding FAQ
This will feature will be appreciate...
Thank you in advance and sorry for my english, I speak only french.
Regards

Hello,
Thank you for your suggestion! In the latest version, we've introduced a setComponents method that allows you to set postal code restrictions. Feel free to give it a try.
import {setKey, setComponents, fromAddress} from 'react-geocode';

setKey('AIzaSyDUAzKPR3MoFHwZz7wEYThVptNvnq_cBJY');

setComponents('locality:santa+cruz|country:ES');

fromAddress('high st hasting')
  .then(({results}) => {
    console.log(results);
  })
  .catch(console.error);

import {setKey, geocode} from 'react-geocode';

setKey('AIzaSyDUAzKPR3MoFHwZz7wEYThVptNvnq_cBJY');

geocode('components', 'locality:santa+cruz|country:ES')
  .then(({results}) => {
    console.log(results);
  })
  .catch(console.error);

If you have further questions or need assistance, don't hesitate to ask.


Deploy workflow setup not working

Unable to deploy the app also getting an error while loading some of the dependencies in the steps.
Error: Unable to resolve action peaceiris/action-gh-pages@v3, repository not found

Error persists.


Using a path from DNX_PACKAGES if defined

(Should fix build break)

Hi @moozzyk, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

:shipit:


support of weaver test framework

support of weaver test framework
this framework works best when a tested code is based on cats effect.
i'm keen to contribute

Hi @bwiercinski !
We are ready for contributions and could help you with this.
A few points I want you to have in mind:

New API approach (from the current scalatest integration) will be more friendly for the weaver.
It looks like the weaver can share resources across suites. It's a great feature for the testcontainers. Scalatest doesn't have a normal way of sharing containers across suites, which is unfortunate. It would be cool if you could use this feature in your integration layer.


Fix of requests propagation to Scheduler from middlewares and engine

This has these goals:

Make spider middleware pass the requests and therefore affecting behavior of other middlewares less in the chain.
Fix the problem of redirected requests in Python 3.
Clarify things.

Guys @ZipFile, @voith, @isra17 what do you think?
Now user can put spider middleware anywhere in the chain, but he has to mark requests as seeds if he wants them to be enqueued from Scrapy spider. Also there are clear rules of what passes to in-memory queue in scheduler.
I think that makes things clearer.

Codecov Report

Merging #276 into master will increase coverage by <.01%.
The diff coverage is 88.23%.

@@            Coverage Diff             @@
##           master     #276      +/-   ##
==========================================
+ Coverage   70.18%   70.19%   +<.01%
==========================================
  Files          68       68
  Lines        4722     4730       +8
  Branches      633      634       +1
==========================================
+ Hits         3314     3320       +6
- Misses       1270     1271       +1
- Partials      138      139       +1

Impacted Files
Coverage Δ

frontera/contrib/scrapy/schedulers/frontier.py
96.77% <100%> (+0.07%)
:arrow_up:

...ntera/contrib/scrapy/middlewares/seeds/__init__.py
73.68% <66.66%> (-4.89%)
:arrow_down:

Continue to review full report at Codecov.

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

Quite a mess you have with merge requests, I think.
I'm not really sure about use case behind flagging requests, though. What kind of middleware you expect to be in the chain? What will be the source of seeds for them?

@sibiryakov Code wise Looks good to me. @isra17 has a good suggestion. I would like to know the pros and cons of your approach vs @isra17's suggestion.

@ZipFile

I'm not really sure about use case behind flagging requests, though. What kind of middleware you expect to be in the chain? What will be the source of seeds for them?

enqueue_request() will get every request returned by spider and downloader middlewares and scheduled manually from Engine. The same is true for start_urls and start_requests fields in Spider class. So, there is no other way to figure out in scheduler enqueue_request method that request came from start_urls or start_requests except marking them explicitly in spider code.
Currently (master version) will transform every request coming from engine or middlewares to Frontera add_seeds event, which isn't right.

@ZipFile see above comment to Israel for suggestions of possible middlewares.

@redapple and @kmike, hi guys, we discuss integration between Frontera and Scrapy here. I believe this discussion could be interesting to you.


Need Heroku Support

Kindly add support for deploying to heroku

I don't use Heroku myself, but it doesn't look like it would be hard to do and I'll happily accept a pull request from you.

i will try


If the index is not loaded into the cache, load it from storage.

Context / purpose
If the index is not loaded into the cache, load it from storage in a lazy manner.
Description
https://github.com/quickwit-inc/quickwit/issues/50
The open_index function of the Metastore trait will be moved to the private function of the SingleFileMetastore.
Change functions that operate splits, such as list_splits, stage_split, publish_split, mark_split_as_deleted and delete_split to lazily load the index's metadata set into the cache if the index is not open.
How was this PR tested?
Ran cargo test -- --nocapture test_single_file_metastore
Checklist
Remove or complete this list if required.

[x] tested locally
[x] added unit tests
[x] included documentation

I update the PR. Please take another look.


HTTP API helpers

What changed?
Implements helpers for HTTP API as proposed at https://github.com/temporalio/proposals/pull/79, primarily around payload formatting. Specifically:

Added go.temporal.io/api/internal/temporaljsonpb package

Added JSONPBMaybeMarshaler and `JSONPBMaybeUnmarshaler interfaces which protos can implement for custom, optional JSON support
A copy of https://github.com/gogo/protobuf/blob/v1.3.2/jsonpb/jsonpb.go but with support for those interfaces

Added go.temporal.io/api/internal/temporalgateway package

Implements gogo-supported equivalent of https://pkg.go.dev/github.com/grpc-ecosystem/grpc-gateway/runtime#JSONPb akin to https://github.com/gogo/gateway but with JSONPBMaybeMarshaler/JSONPBMaybeUnmarshaler support

Added go.temporal.io/api/internal/temporalcommonv1 package

Implements JSONPBMaybeMarshaler and JSONPBMaybeUnmarshaler for Payloads and Payload to support shorthand JSON representation
Makefile updated to copy code written here to go.temporal.io/api/common/v1 where it lives alongside generated code (instead of trying to write code directly alongside generated code)

Updated go.temporal.io/api/proxy

Added JSONPBMarshaler/NewJSONPBMarshaler and JSONPBUnmarshaler/NewJSONPBUnmarshaler to create marshalers to support maybe-JSON interfaces (so for Payload shorthand)
Added NewGRPCGatewayJSONPBMarshaler to create a https://pkg.go.dev/github.com/grpc-ecosystem/grpc-gateway/runtime#Marshaler from the above marshaler/unmarshaler

Added tests for shorthand payloads and gRPC gateway
Updated Makefile to support building with gRPC gateway + Google HTTP annotations

This is ready for review. This will not have the generated code updates until the API PR is merged. Related PRs:

Depends on https://github.com/temporalio/api/pull/301
Depended on by https://github.com/temporalio/temporal/pull/4543

If this depends on open PRs, please make a stacked PR to make review easier (e.g. push all the dependencies to some arbitrary branch and then set that as the base here).

It's more than that. It depends on a submodule from another repo being updated and a Makefile rerun (or rather a GitHub workflow triggered manually probably). You cannot just merge the other and then this magically is ok to merge. The PRs are in different repos and are inherently different things to review. Not sure how these different-repo PRs can be made any easier to review.


Add memory checks for prover_input, as well as range_checks for prover_input, syscalls/exceptions

This PR addresses the prover_input and syscalls/exceptions points from this issue.

STACK_BEHAVIORS is addressed to add stack constraints for prover_input.
CTLs and ArithmeticStark are updated to include range checks for prover_input, syscalls and exceptions in the CpuStark.

The latest push was to rebase on main, since the PR had conflicts with this merged PR.

@nbgl Thank you for your review!
I replaced the u32 values for range checks by U256 to simplify things, as you suggested.
Regarding the use of ctl_arithmetic_base_rows instead of additional CTLs, since the columns required, on the cpu side, for syscalls and exceptions are different from the other operations, I not only range checked the gas but also the handler addresses and syscall/exc_info, since they are also U256s and are already in the "correct" rows. What do you think of this approach?

@nbgl I pushed a new version that does not introduce a new CTL for the range checks but instead adds a column in ArithmeticStark containing the opcode if the operation is a range check.
I constrained the new opcode column to be 0 when the operation is anything but a range check.
What do you think of this approach?

@nbgl I pushed a new version that doesn't introduce a new CTL: the idea is that instead of range-checking the last memory channel for arithmetic operations, we check the next row's mem_channels[0] which should also contain the result (since it contains the new top of the stack). This enables us to check the new top of the stack for prover_inputs, syscalls and exceptions, which contains the values we want to range check. What do you think of this approach?

Hey @Nashtare -- are you going to be reviewing this to get it merged?

@pgebheim  yeah I can, though I didn't as @nbgl  was assigned the review already


Tiny tidy up commits

Unify the use of multiple sed commands.
Use "assing default value" expansion for defaults
On tiny shorthand conditional

Hey, the new way of setting default parameters doesn't seem to work, i tested these changes and PRIVATE_KEY is empty as set in the beginning of the script.
Also if using [[ (shell-builtin) works for you please use that instead of [ (external command /bin/[).

The [[ => [ still was left over when I thought I'd convert the script to posix shell.
The Assign default value did not assume the variable to be null instead of unset. Usually I prevent pollution by using unset. Fixed now.

Some parts of this have become unnecessary with some of the changes i just pushed (especially setting default config values), some have been merged in one of my last commits, and I'll merge some more with later cleanup commits, so i'll close this pull-request now.


Added an option to avoid emitting quotes.

This fixes the issue #26.
Also, I wonder if it is possible to use str::contains with an array of char.

I don't think this needs to be configurable. Let's just put quotes if quotes are necessary and not put quotes otherwise. I can't imagine anybody requires a way to put quotes in places they are not required.

I notice that you said When the string looks like a date (e.g. 2014-12-31)...  in the comment, but it is not handled in the condition. Will it be a problem for other parsers? (Although yaml-rust does not recognizes date type anyway.)

@chyh1990 At first, I thought it was needed to have this condition, but it is not since the date format contains dashes (-) and I already check for dashes.


add s3 acl support

What problem are we solving?
s3 acl https://github.com/seaweedfs/seaweedfs/issues/4519

The S3 integration test has passed. Project URL: https://github.com/shichanglin5/aws-s3-tests.

Feel free to make any changes to this PR if anything else is not optimal.

updates?

updates?

应该没有需要改动的了

Go tests are not passing
S3 tests are not passing
The PR is too big. Please split into smaller PRs.


[meson.build] Change join_paths to / in meson.build files

Replace join_paths in meson.build files to /
Check issue #709 for more details
Signed-off-by: hyeonseok lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #796. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

Please use "Resolves #709" like statement in PR description to auto close the related issue when this PR is merged.

Please use "Resolves #709" like statement in PR description to auto close the related issue when this PR is merged.
LGTM once above comment is resolved


No unreachables when handling wire messages

We have added a few more unreachables with #684 when handling wire::MakerToTaker messages in taker_cfd.rs:
match msg {
    // ...
    wire::MakerToTaker::Heartbeat => {
        unreachable!("Heartbeats should be handled somewhere else")
    }
    wire::MakerToTaker::ConfirmOrder(_)
    | wire::MakerToTaker::RejectOrder(_)
    | wire::MakerToTaker::Protocol { .. } => {
        unreachable!("These messages should be sent to the `setup_taker::Actor`")
    }
}

We should split up this enum so that we can rely on the compiler to know that we're correctly handling all messages.

[x] Handling in taker_cfd.
[ ] Handling in maker_cfd.

This is so old and irrelevant now :D


fix wrong keyword

fix wrong xpath in configuration.robot and wrong step in project-m
embers.robot
fix replication case for new delete progress

Coverage decreased (-0.02%) to 64.515% when pulling 9701622d5971f63b779e2418135abdfd05e3e5c9 on sigsbee:fixcase into 8f9e2644075744e091b91d7a5fdab73973c28b50 on vmware:master.


7.1.7 is not stating

Can't seem to find a way to start newer verisons of DAT.
Tried both in the Current branch folder and copying it to DAT installed locally in Program FIles.
All I see is this:

Same here. 7.1.7 is not extracting files anymore.

The latest verison that starts correctly is Beta Build 7.1.1

Please use the latest release here - https://github.com/maurice-daly/DriverAutomationTool/blob/master/Current Branch/7.1.8/DriverAutomationTool.exe

Please use the latest release here - https://github.com/maurice-daly/DriverAutomationTool/blob/master/Current Branch/7.1.8/DriverAutomationTool.exe

No luck starting it with exe for some reason - same blank white window as on  the screenshot above. Managed to succesfully start it with ps1 though


color theme

Hello!
Will you improve current color themes? I use light one, but check the dark and it is the same, the color for keyword, types and so on often are limited compare to vs comunity, will you try to improve them? If the answer is mb later then link me to topics where can I find how to separate member in json of theme, like enums, generic, class and so on, I will try my own.
That is the only thing which keeps me in vs community, I've tried a lot of themes (especially light ones), and thay are limited for c#, sadly

@xandudex which light/dark themes specifically are you using?  I would generally recommend the 'Visual Studio 2019 Dark' or 'Visual Studio 2019 Light' themes for use with the extension.  Those should be pretty similar to what VS has by default.
If you don't like the colors for keywords and other items in the themes, it isn't too hard to customize it either.  See https://code.visualstudio.com/docs/getstarted/themes#_editor-semantic-highlighting
For example, if you wanted to change the color of enums, you would first find the semantic token type for enum using the 'Developer: Inspect Editor Tokens and Scopes' command.

Then in your settings.json you could add additional customizations for the 'enum' token type
"editor.semanticTokenColorCustomizations": {
        "rules": {
            "enum": {
                "foreground": "#e30c0c",
                "bold": true
            }
        }
    }

@xandudex If you are still having trouble, please reopen and provide the requested information.


Just use RPGmaker or something, sheesh...

bababooey²
Changelog:

Cleaned up README.md with proper linting this time I swear 👀
Added future page [Named Arguments] to give you more work (ha)
Wrote VSCode installation guide
Either VSCode lied to me or your render thingy is poopoo, anyways fixed >> on bitflags page...probably
Added Arguments and Associated Lists pages (WIP)


Mod isn't compatible with 1.18.2

I don't know why the mod is advertised to work on 1.18 on Modrinth

Modrinth metadata aside, you can get version 1.2.6, which is compatible with 1.18.2. The two versions are functionally equivalent.


libjili.so appears to be missing

Hi there,
I've been trying out the Java Engine, and I have noticed that I cannot run the JVM because of a missing library.
I haven't done any modifications, so I believe this is on a standard build of the Java Engine?

Regards,
Andrew

Thanks for submitting this, I'll make sure the package maintainer has a look at the package, in the meantime, you can use sun-jdk8 as your 'runtime' to work around this error.
Boxfile
build:
  java_runtime: 'sun-jdk8'


Use .format() and keyword argument for string formatting and remove relative parameter

For flexibility and easy of extension, I suggest using the following pattern for string formatting:
f.write(move.format(dx=dx, dy=dy, x=x, y=y)

Using this approach, all of the following configuration actually work as expected (not that they would be correct g-code):
move = "G00 {x:.4f} {y:.4f}\n"
move = "G00 {y:.4f} {x:.4f}\n"
move = "G00 {dx:.4f} {dy:.4f}\n"
move = "G00 {dy:.4f} {dx:.4f}\n"

Benefit:

the relative parameter can be removed
more flexibility of the user
more flexibility to add many other variable that may be useful to the user (e.g. line_number, segment_number, layer_id, etc.,)

Again, since this changes the configuration file format (user must use the {} notation), this change is best done early.

Completed in 0.4.0

Completed in 0.4.0


Pyomo6

Pull Request Description
What issue does this change request address?
#1580
What are the significant changes in functionality due to this change request?
Removes pyomo 5.7 forcing.

For Change Control Board: Change Request Review
The following review must be completed by an authorized member of the Change Control Board.

[ ] 1. Review all computer code.
[ ] 2. If any changes occur to the input syntax, there must be an accompanying change to the user manual and xsd schema. If the input syntax change deprecates existing input files, a conversion script needs to be added (see Conversion Scripts).
[ ] 3. Make sure the Python code and commenting standards are respected (camelBack, etc.) - See on the wiki for details.
[ ] 4. Automated Tests should pass, including run_tests, pylint, manual building and xsd tests. If there are changes to Simulation.py or JobHandler.py the qsub tests must pass.
[ ] 5. If significant functionality is added, there must  be tests added to check this. Tests should cover all possible options.  Multiple short tests are preferred over one large test. If new development on the internal JobHandler parallel system is performed, a cluster test must be added setting, in  XML block, the node <internalParallel> to True.
[ ] 6. If the change modifies or adds a requirement or a requirement based test case, the Change Control Board's Chair or designee also needs to approve the change.  The requirements and the requirements test shall be in sync.
[ ] 7. The merge request must reference an issue.  If the issue is closed, the issue close checklist shall be done.
[ ] 8. If an analytic test is changed/added is the the analytic documentation updated/added?
[ ] 9. If any test used as a basis for documentation examples (currently found in raven/tests/framework/user_guide and raven/docs/workshop) have been changed, the associated documentation must be reviewed and assured the text matches the example.

Note: This is do not merge because it depends on un-merged branches in LOGOS and HERON.

This PR can be closed, duplicate PR to #1482


postgresql11Packages.cstore_fdw: 1.6.2 -> 1.7.0

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://github.com/citusdata/cstore_fdw/releases.
meta.description for postgresql11Packages.cstore_fdw is: '"Columnar storage for PostgreSQL"'.
meta.homepage for postgresql11Packages.cstore_fdw is: '"https://www.citusdata.com/"

Checks done (click to expand)

built on NixOS

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

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

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

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

du listing: https://gist.github.com/9d3f7fd6b7d6b5957c586fd4a19cbdb5

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

8 total rebuild path(s)
2 package rebuild(s)
2 x86_64-linux rebuild(s)
2 i686-linux rebuild(s)
2 x86_64-darwin rebuild(s)
2 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
postgresql11Packages.cstore_fdw
postgresqlPackages.cstore_fdw

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/x0g4m05y2mvn33z38q1z0g1n9lxj1d95-cstore_fdw-1.7.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

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

cc @thoughtpolice for testing.

addressed by https://github.com/NixOS/nixpkgs/pull/80488


Scottx611x/include submitter emails in notifications

Add configurable include_submitter_email setting to send submitter emails in the subject of notification emails
Fixes #119

@schneidmaster This is also my first time touching ruby, so I'm probably doing something weird (Codeclimate and CI were helpful though, thanks for that)

Thanks! This will be out shortly once it works through the CD pipeline

@schneidmaster Just a heads up I haven't been recieveing notification emails since #124 was merged. Not sure if this is related.

@scottx611x Thanks for the heads up. Wasn't related to your PR, I had sidekiq misconfigured from the work I did recently (ActiveJob was enqueueing things to a mailers queue but sidekiq was only checking the default). Should be sorted now.


[ENH] add airspeed velocity benchmark

Closes # .

Changes proposed in this pull request:

closed in favor of #900


FEATURE REQUEST: Remove the "Lock Hotbar" button

Dunno if this is possible or not, but at some point in v11 they added a new, kind of pointless button to the Hotbar, the "Lock Hotbar" button, which basically is a button that takes up nearly as much room as an actual macro button, but all it does is prevent you from moving around the macro buttons. It'd be great if Minimal UI could add an option to remove this button from view. I figure this makes much more sense as a thing you set and then never touch again, so having it permanently take up space just feels pointless to me.

Yeah - it makes sense, thanks for the idea. First I am looking into stopping to break the players list and navigations panel... Foundry is driving me mad with that


Changes Version of 'active_model_serializers' Dependency

Adjusts the gem's dependency manifest, and makes adjustments to get the test suite to pass.
Resolves #1.

@bryanmtl
Any objection to merging this?

Nope, go for it.


[Website] The Slack joining instructions are missing and "Pulsar Slack" button does a google search

Describe the bug
The Slack joining instructions are missing and "Pulsar Slack" button does a google search.
https://pulsar.apache.org/community#section-discussions
The old content seems to be available at https://pulsar.apache.org/contact/
To Reproduce
Steps to reproduce the behavior:

Go to https://pulsar.apache.org/community#section-discussions
The information to join Pulsar Slack is missing. Previous there was a link to https://apache-pulsar.herokuapp.com/ .
Clicking "Pulsar Slack" does a Google search instead of going directly to Pulsar Slack,

Expected behavior
Providing this information is necessary about Pulsar Slack:

The Slack instance is at https://apache-pulsar.slack.com/
You can self-register at https://apache-pulsar.herokuapp.com/

This issue has been resolved. Thanks for your confirmation. @SignorMercurio


Output to Browser

I'm using monolog successfully, but in case of unhandled PHP errors (e.g. Warning: Division by zero) this error message still appears in the browser.
Of course I can deactivate errors in the browser with display_errors = 0, but I would prefer an "anonymous" error message to be sent to the browser (e.g. "we are already on it"). I can overwrite this error message with set_error_handler, but then monolog doesn't get the error anymore - or do I see it wrong?
Another idea would be to write an echoHandler for monolog, but then PHP would still issue the error message.
What's the best practice here? Thanks for your answer!

This is typically handled by the framework (responding with an error page when an unhandled error occurs). The best practice is definitely to run production with display_errors=0 because otherwise you might leak sensitive information to the user.
How exactly you go about rendering a page I am not sure, depends on how your application is built really, but I would say this shouldn't really be monolog's responsibility, as it's about reporting an error to the user and not about logging for devs. The goal is different and the information conveyed as well.


Sparse MPI redundant computation fix

This basically makes _dist_datamap and _support memoized method based on the gridpoints (coordinates).
This reduce the call to _dist_datamap to 1 instead of 8 per operator call per sparse function
For example:
Allocating memory for rec(1355, 159600)
Allocating memory for rec(1355, 159600)
Allocating memory for rec(1355, 159600)
Allocating memory for rec(1355, 159601)

args_defaults (currently) takes 36 minutes on this size (4 MPI ranks), in testing with this
update

Ok so overall yes, I agree, there needs to be a rework of Sparse in general but I think all these 4 options are just different way to do this temporary patch.

I have a feeling we can't accept the solution in this PR as if you have 1M receivers as you were saying, you may leak a lot of memory

Well the coordinates are quite cheap still, even the case of couple M of receivers, it's only a couple Mb of memory so nothing that is gonna crash anything. The data is massive memorywise not the coordinates.
Options 1
This is overall the best long term option but needs a lot of rethinking and refactoring as the coordinates data is two levels down SparseFunction inside its Subfunction's data. This would need to setup setters/getters to know when and where something changes and probably rethink Subfunction.
So probably the best option long-term but way ahead of this PR.
Option 2
This one may not be doable as the expensive part isn't really the loop but the global_to_rank inside it for each coordinate.
Support itself doesn't need to be memoized as it's quite quick, I only memoized it too for homogeneity, but dist_map is the costly one.
May make things a bit better to do it, but overall dist_map is called 8 times at prepare args and 8 times at post_process args so 16 times overall when nothing changes.
Options 3
I think link to what I said for Option 1
Option 4
Not sure how much we'd gain from the current case
To summarize, yes sparse needs a lot of work, this is a temporary patch that I think is fairly cheap (couple Mb is something we can leave with), while actually fixing something that for large number of rec (even couple 100k) takes (a lot) more than 50% of the total runtime for a 3D TTI modeling that is already quite expensive, and up to over 80% of the time for acoustic, up to hours of pre/post processing of sparse arguments.

@mloubout OK... I think I can live with this
however, could you just tell me which line exactly is responsible for slowing everything down?
is it https://github.com/devitocodes/devito/pull/1109/files#diff-5d662e9e9c311233ce7b83c1d18d291aR121
?


sub, rsub and isub

I'd propose a behavior change of the __sub__ operator to align with how the other operators work.  Right now v - w  will do the equivalent of v + (-w) where the neg takes the inverse of w.  I think it should align instead with what __add__ does and use v.eadd(w, add_op=MINUS).  The old behavior can still be had by adding the negation.  This makes all the binary operations consistent, and allows me to make a scalar construction like w - 5  which would become w.apply_second(MINUS, 5).  Any thoughts @szarnyasg and @marci543 ?  I made a PR #69.

@michelp Good question... this can get a bit counter-intuitive (which is a challenge when trying to turn it into a Pythonic API). I had a slide about this in my tutorial:

There are at least two questions:

What happens when an element becomes 0 -- is it kept as an explicit zero or is it dropped? (GraphBLAS keeps it, I think it would be intuitive to drop it).
What is the result of implicit zero element - x, +x or -x? (GraphBLAS returns +x, I think -x would be more intuitive.)

I agree it has some counter intuitive behavior, but consistency with GraphBLAS I think is key here.   And the old behavior can be had with v + (-w).  As for the two questions:
1: The zero value is kept, this lines up with GraphBLAS where it's really only monoids and semirings that have an "implicit zero" value when they are applied.  Unstored values in matrices and vectors are uninterpreted until a monoidal operation applies.
2: Same things GraphBLAS does, +x.  Since there aren't two values the operator doesn't apply and the only present value passes through.  Ditto with apply_first/second, they only apply to entries with stored values.
The upside here is that now it is consistent with scalar application, so you can do w - 5  and 5 - w which will apply_second/first with the MINUS operator with no effect on unstored values.

Indeed, the scalar application works around the counter-intuitiveness of point 2. I think there will be an explicit zero but that's easy to get rid of.
Understood regarding point 1 that you need a monoid/semiring to interpret whether something is actually zero or not.
So the direction of this the issue and the relevant pull request looks good to me.

And you know, the more I think about it, + and * maybe aren't the best map to eWiseAdd and eWiseMult which are really much more like & (union) and | (intersection) operations that just happen to default to plus and times operations and the actual math operations are just nice shortcuts to eadd with fixed operations.  Maybe I'm overthinking it.

Yeah, it is quite counter-intuitive. I once wasted an hour on this, and this experience led me to make that slide.

The current behaviour of __sub__ follows MATLAB as discussed in #27 and one of our conversations.
Although v - w ≡ v + (-w) seems more intuitive for a beginner and more pythonic, I think pygraphblas can follow the GraphBLAS behaviour, in which case the tutorials should explain the correct way of subtraction and emphasize that - in (py)graphblas is nothing more than having the union (∪) of present elements as result and GraphBLAS only applies binary operators if necessary, i.e. if both operands are present.
Related issues which can be closed if the decision is that v - w is v.eadd(w, add_op=MINUS) and operations keep explicit 0s:

Behaviour of operator / #46
Explicit zeros in results #47

P.S. I think you swapped the operators here.

& (union) and | (intersection) operations

As we discussed all math operators are now A.eadd(B) with the appropriate binary operator.  I'll address the possibility of union and intersection operators in another issue.


process eth logs similar to normal erc20 logs instead of having separate system for them

          Create issue for TODO or address it in this PR.

Originally posted by @MicahZoltu in https://github.com/DarkFlorist/TheInterceptor/pull/653#discussion_r1318545989

let's do this when we are deprecating our multicall so we can get rid of code for old stuff


S3 Content-Type not set in Ruby 1.9.2

REE:
ree-1.8.7-2011.03 :001 > require 'rubygems'
=> true
ree-1.8.7-2011.03 :002 > require 'right_aws'
=> true
ree-1.8.7-2011.03 :003 > s3 = RightAws::S3.new(ENV['AMAZON_ACCESS_KEY_ID'], ENV['AMAZON_SECRET_ACCESS_KEY']); 0
=> 0
ree-1.8.7-2011.03 :004 > b = s3.bucket('brucie')
ree-1.8.7-2011.03 :006 > b.put 'testing', 'something', {}, 'public-read', { 'Content-Type' => 'image/png' }
=> true
ree-1.8.7-2011.03 :012 > curl -I https://brucie.s3.amazonaws.com/testing | grep png
% Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     9    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
=> "Content-Type: image/png\r\n"
1.9.2:
ruby-1.9.2-p180 :001 > require 'right_aws'
=> true
ruby-1.9.2-p180 :002 > s3 = RightAws::S3.new(ENV['AMAZON_ACCESS_KEY_ID'], ENV['AMAZON_SECRET_ACCESS_KEY']); 0
=> 0
ruby-1.9.2-p180 :003 > b = s3.bucket('brucie'); 0
=> 0
ruby-1.9.2-p180 :004 > b.put 'testing', 'something', {}, 'public-read', { 'Content-Type' => 'image/png' }
=> true
ruby-1.9.2-p180 :005 > curl -I https://brucie.s3.amazonaws.com/testing | grep png  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
Dload  Upload   Total   Spent    Left  Speed
0     9    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
=> ""

I've found that using lowercase 'content-type' as the key fixes this problem.

closed

How is this closed?   Shouldn't the keys be case-insensitive.  At the very least, match the case of AWS documentation (but really, header keys should be case insensitive).  we spent a lot of time tracking down why our CDN wasn't working on IE after an upgrade (turns out Content-Type wasn't being set anymore by our upload to s3 process).    I'd love to see this reopened and resolved.   Thanks.

thanks, should be fixed now: plz try out "development" branch


t2 with no command doesn't show the manual

(again)
➜  t2-cli git:(master) t2

command argument is required

Usage: t2 <command>

command     one of: install-drivers, crash-reporter, provision, restart, run, push, erase, list, init, wifi, key, rename, update, version, ap, root

Should show each of those commands with their descriptors.
Probably, one of the commands of the CLI is missing a .help field. To fix, make sure every command on the CLI has a .help field which describes what it is/how to use it.

I found the missing "help", did you want to fix it, or should I make a PR?

you go ahead! Thanks


fix request produce after check empty stop program

when produce request async, program maybe stop early

wrong way to slove it


Install NumPy from PyPI

NumPy provides wheels for Python 3.13t in PyPi so there is no need to use nightly wheels.

Pipeline 19323847 passed


Replace aws-s3 gem with aws-sdk-v1.

The aws-s3 gem is no longer being maintained and is out of date. This PR replaces that gem with the first version of aws-sdk built by Amazon. The aws-sdk-v1 gem is used because it is the full production ready version of the aws-sdk available and will not cause issues if aws-sdk version 2 is also loaded on a system (v2 is not backward compatible but can live on the same system as v1).
A runtime dependency has been added to attachment_fu for aws-sdk-v1 to make installing and using the attachment_fu gem easier out of the box

Once again, this is fantastic, thank you!
One point of discussion though, for my primary usage of attachment_fu, I use the file system for storage so I wouldn't want the aws-sdk gem installed unnecessarily.  Do you feel strongly about needing the dependency in the gemspec?

You're welcome.
Either way is fine with me. I just didn't want users (new or old) running into the frustration of not having a dependency loaded when they decided to use S3 instead of the file store.
I'll leave the deciding vote to you. If you want me to update the PR to change it to a requirement let me know.

I changed it to be a requirement.

Great, thanks.
One other thing, I believe this gem is used by a number of users with automated builds as it starts getting downloads from rubygems pretty quickly after I post a new version (over 100 since you're last update -- which of course probably didn't really need a new gem build since it was just test cases, but I was just keeping it current).  In order to not suddenly break any existing installations, are you willing to add a conditional test for the presence of either the aws-sdk-v1 gem or the aws-s3 gem and use the appropriate code?  That way anyone using the s3 gem can continue to use it if they desire.

I can do that but I'm going to have to think a bit on how I'm going to pull it off. Both gems have the same underlying name space so collision makes them not play nice together. I'll get back to you in a couple of days. Do you want me to keep this PR open or close it and cut a new one when ready?

Presumably people would choose one or the other and not have both S3 gems installed, so the namespace collision shouldn't be a problem.   I'm thinking that you just try the new code first with a rescue block around it to revert to the old code if it fails to find the new classes.
Of course testing could be trickier  to have both gems installed to ensure either gem option worked.
You can just keep this PR open until it's ready.
Thanks again!

I think this is a great improvement and am eager to merge it in.  While it would be great to support either S3 gem transparently, if you don't think it will work to be able to support both gem options, I can just bump up the gem version so that any automated builds dependent on the old gem won't automatically pick it up.

I think that might be for the best. I've been really busy at work and haven't found the time to figure out the duel support completely. Bumping the version will clear the way for other merges and let us figure out the duel support in the future if it's still needed.

Any news? I'm considering using this fork to support attachment_fu on a Rails 3.0 app (crap, yes). Good idea?
Thanks!

Sorry I've let this sit so long.  I'll bump up the version to 3.3 and merge this in


Enable User To Select Which Flow To Work On

I was about to create a new flow but then didn't because I didn't want to lose the flow I'm working on. I know I can export a flow and then import it later to resume work on it.
Wouldn't it be great if you could, instead, select from a list of flows you're working on currently! Something like the chat history side panel of ChatGPT where you can open flows and delete them when you're done with them.

Thanks for raising this issue, it is something Corbus mentioned on Medium as well. Tabs for multiple flows is one of those nice things that I nonetheless can’t justify prioritizing over things like undo/redo and Chat Turn nodes, given that I am the only person working on the project. But with enough time we should get around to this.


Python: chat completion config does not propagate stop sequence to ai services

Describe the bug
similar with #1880, stop sequences are not passed into ai_services.

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform

OS: [e.g. Windows, Mac]
IDE: [e.g. Visual Studio, VS Code]
Language: [e.g. C#, Python]
Source: [e.g. NuGet package version 0.1.0, pip package version 0.1.0, main branch of repository]

Additional context
Add any other context about the problem here.

temporal solution commit: https://github.com/microsoft/semantic-kernel/pull/2223/commits/bc61d2e6183c4d47669aa7edf4a2a6f9ac4dd4ca

@joowon-dm-snu  thanks for raising this. @lemillermicrosoft / @awharrison-28 could you take a look into this?

Closing this as the following issue is no longer relevant. The execution settings have been redone since then. If you have a new issue with the latest code, please file a new GitHub issue. Thank you.


Search isn't working

There appears to be something wrong with the search function. I'm seeing the following in javascript error console

The JSON search index seems to be available at https://docs.sensu.io/js/lunr/PagesIndex.json, so I'm not sure whats going on.

looks like there are a number of null values in the JSON


[FLOC-3326] Convergence sleeps appropriately

https://clusterhq.atlassian.net/browse/FLOC-3326
http://build.clusterhq.com/boxes-flocker?branch=convergence-sleeps-appropriately-FLOC-3326
XXX provide pre- and post-AWS usage numbers.
After each iteration of convergence loop we decide how long to sleep:

If we've done nothing this iteration, sleep for max interval set by the deployer. (If configuration/cluster state changes in way that requires action the loop will wake up thanks to work in previou branches.)
If we've done something, sleep for short period of time. The theory is that many configuration changes (e.g. "move a dataset here") require multiple steps so it's worth doing another iteration soon after.

Previously pattern of interactions was:

Iteration.
Sleep 1.0 seconds
Iteration
Sleep 1.0 seconds
... etc.

New pattern will be like this for block device deployer:

Iteration. Did some stuff.
Sleep 0.1 seconds
Iteration. Did some stuff.
Sleep 0.1 seconds
Iteration. Did nothing.
Sleep 60 seconds (with some noise)

So while doing work we iterate rather more, but then we sleep for much longer after the work is done.
0.1 was picked out of a hat.

Thanks @itamarst
Would be good to grep the acceptance test logs for API call count before and after this change and include that when you put it up for review.
Please proceed.

Can someone verify this PR?

Thanks.  Some optional inline comments.  Lots of build errors, unfortunately.  Merge when you're satisfied with the code and you get buildbot into the right shape.


[WIP] [Logging] Support debug level log verbosity

Objective
Add a "verbosity" degree-of-freedom to debug level structured logging output. In pursuit of maintainability, this SHOULD generalize such that it can support all CLI binaries (e.g. node, client, etc.).
Conceptually, debug log verbosity has a consumer side and producer side:
Consumer
As an end-user, I only want to see log out put which is either actionable or necessary to support/enable continued operation so that I don't waste time considering output that does not require action. Typically this excludes the debug level altogether but in some circumstances, I need to see additional, debug level, logs (e.g. troubleshooting). In these scenarios, I prefer to see the "minimal useful" (i.e. lowest degree of verbosity) debug level output, by default.
As a contributor, while debugging, I want to be able to exclude excessively "noisy", debug-level, log output so that I can more easily locate more relevant debug log lines and ignore irrelevant ones. I would prefer the lowest degree of verbosity by default but sometimes, I need to be able to consider higher degrees (e.g. validating assumptions, debugging edge-cases). I would also find it quite convenient to be able to specify the verbosity of a particular module independently of others.
Examples (illustrative only):
p1 Query Height
#=> 100

p1 -v Query Height
#=> Low verbosity debug-level log...
#=> 100

p1 -vv Query Height
#=> Low verbosity debug-level log...
#=> Medium verbosity debug-level log...
#=> 100

p1 -vvv Query Height
#=> Low verbosity debug-level log...
#=> Medium verbosity debug-level log...
#=> High verbosity debug-level log...
#=> 100

Per-module verbosity:
# P2P module only
p1 -v p2p
p1 -vv p2p
...

# P2P and Consensus modules only
p1 -v p2p,consensus
p1 -vv p2p,consensus
...

Producer
As a contributor, while writing code, I want to be able to include debug-level log output around mission critical and/or show-stoppingly significant parts of the code (e.g. maxing out OS resource limits). However, I don't want to have to be too concerned about the "noisiness" of the log output such that it requires real consideration in the debug logging code (i.e. debug logging should not need to be that complex).
Example (illustrative only):
logger.Debug().Msg("Low verbosity debug-level log")

... ¯\_(ツ)_/¯ ...

Origin Document

Goals
Consumer

MUST be able to specify some optional degree of verbosity.
MUST be able to couple to optional CLI flags (e.g. -v, -vv, etc.) while maintaining separation of concerns between library and CLI binary code.
SHOULD default to the lowest degree of verbosity

Producer

MUST be able to specify some degree of verbosity.
SHOULD default to the least verbose degree.
MAY support overriding the default degree of verbosity.

Related Code
... app/pocket/main.go ... need to add cobra integration, be consistent with [good example ?]
... LoggerModule ...
Open Questions
... how to signal to localnet? ... makefile? :roll_eyes:
Deliverable

...

Non-goals / Non-deliverables

...

General issue deliverables

[ ] Update the appropriate CHANGELOG(s)
[ ] Update any relevant local/global README(s)
[ ] Update relevant source code tree explanations
[ ] Add or update any relevant or supporting mermaid diagrams

Testing Methodology

[ ] Task specific tests or benchmarks: make ...
[ ] New tests or benchmarks: make ...
[ ] All tests: make test_all
[ ] LocalNet: verify a LocalNet is still functioning correctly by following the instructions at docs/development/README.md
[ ] k8s LocalNet: verify a k8s LocalNet is still functioning correctly by following the instructions here

Creator: @bryanchriswhite
Co-creator(s): @h5law

Adding valuable context from @bryanchriswhite so its not lost.


Fix typo

Warnings

:warning:
This PR is approved with no milestone set. If merged, it won't appear in the detekt release notes.

  Generated by :no_entry_sign: dangerJS against 7c2b663720d92a997e378c5f1a3f6be1ded2ed89


[Python] Method to lazily read a collection of multiple Arrow IPC stream files

Describe the enhancement requested
It would be nice to have some method available in PyArrow to lazily read a collection of Arrow IPC stream files. This would be a great complement to the Arrow over HTTP project, because a common use case is for the user to download multiple Arrow IPC stream files from the HTTP server and then read them into Python.
The dataset API works with files in the Arrow IPC file format, but it does not currently work with files in the Arrow IPC stream format.
Also, as far as I can tell, it is not currently possible to create a record batch stream reader from a collection of multiple Arrow IPC stream files with the same schema.
Maybe there is some way to achieve this with itertools?
Component(s)
Python

It's easy enough to create a record batch reader from a collection of multiple Arrow IPC stream files with the same schema like this:
import pyarrow as pa
import glob

def get_schema(paths):
    with open(path, "rb") as file:
        reader = pa.ipc.open_stream(file)
        return reader.schema

def get_batches(paths):
    for path in paths:
        with open(path, "rb") as file:
            reader = pa.ipc.open_stream(file)
            for batch in reader:
                yield batch

paths = glob.glob("*.arrows")

reader = pa.ipc.RecordBatchStreamReader.from_batches(
    get_schema(paths),
    yield_batches(paths)
)

Still, it would be nice to have a method in PyArrow that makes this more efficient and concise to express.


[Bug] SVG custom icon with color doesn't work!

Version
^0.23.3
Link to Minimal Reproduction
https://visactor.io/vtable/demo/custom-render/custom-icon
Steps to Reproduce

Current Behavior
SVG icon color not change.
Expected Behavior
SVG icon color should change.
Environment
- OS: Windows 10
- Browser: Webview2
- Framework: Svelte

Any additional comments?
No response

Sorry，VTable is currently not possible to parse svg to automatically modify color.

sorry，the example in the website with color is a mistick ,i will delete it .


Refactor to support new metalog interface

Landed in https://github.com/metarhia/impress/commit/e65a26f1e2b3231caab5ece4b8eb8d1b828ee5b9 and https://github.com/metarhia/impress/commit/dfbb1a4ab213ef088c51e3922f90a66cad3ccd18


Refactor the footer and add 'Plan for jobs' logo

Trello card
https://trello.com/c/sSthJElz/1590-improve-design-of-footer-with-links-to-accessibility-etc
Context and changes
The main goal of this PR was to add the 'Plan for jobs' logo to the footer. This was hampered slightly by the footer CSS, so I rewrote it. Now it uses flexbox and I've removed all the pixel-specific measurements.
Borders, margins, gaps etc might need a little more attention @gazcarr but I think it looks pretty decent and the stylesheet's way easier to work with now.

Desktop
Mobile

Old

New

@peteryates I had this on the preview app on Safari:

Mobile:


fix an invalid DynamicObject* cast

Scope objects are not always "DynamicObject"s (e.g. may be of type
"WithScopeObject"). Use RecyclerObject instead.

similar issue in PatchGetPropertyScoped as well

similar issue in PatchGetPropertyScoped as well

You are right, fixed in update

Thanks @Penguinwizzard @rajatd


Dark Mode for Mojave

Will there be a dark mode for FaviconBar so that it blends in with Dark Mode in macOS Mojave?

Generally faviconbar looks great under Mojave dark mode beta 1.  There are a few known issues, #47 #48 and #52 which will be addressed if Apple doesn't fix them for us in future betas.
As long as you don't have blend into background enabled in settings it looks good on a day-to-day basis right now.


not able to use webUrl in iframe.

I am using this api 'https://graph.microsoft.com/v1.0/users/${id}/drive' to get user's onedrive. I am getting 'webUrl' in response. But not able to use this 'webUrl' in iframe. my main concern is that, this 'webUrl' is not contained any unique id to authenticate the user.
if i am using the wrong api then let me know the exact api to get user onedrive root 'webUrl' to display in iframe.
If am using this api 'https://graph.microsoft.com/v1.0/me/drive/items/{id}/createLink' with {  "type": "embed" } then not getting the expected result and getting:
400 - Bad Request
{
"error": {
"code": "invalidRequest",
"message": "Link type must be either 'edit' or 'view'.",
"innerError": {
"date": "2020-09-14T12:01:56",
"request-id": "85f1702f-a119-40e9-888c-.........",
"client-request-id": "85f1702f-a119-40e9-888c............."
}
}
}

Thanks for your feedback. Could you please clarify whether this is an issue with OneDrive Personal or OneDrive for Business?
Unfortunately, the createLink API only supports embed in OneDrive Personal - so the API's behavior would be expected if your request is for OneDrive for Business.
https://docs.microsoft.com/en-us/graph/api/driveitem-createlink?view=graph-rest-1.0&tabs=http


Allow generators to go up/down when spanning a lattice

tristan bay — Today at 10:17 AM

The "span lattice" tool should have a way to let the user add a single instance of a generator going in both directions at the same time (e.g. 3 5/4s forward and 2 5/4s backward).

In SW3 alpha.


renode-unstable: 1.15.2+20240914gitcb658f346 -> 1.15.3+20240927gitbb819bb49

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for renode-unstable is: Virtual development framework for complex embedded systems
meta.homepage for renode-unstable is: https://renode.io
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.15.3+20240927gitbb819bb49 in filename of file in /nix/store/j85iw5hl3rm1js3skjssp36lh8i8kwy3-renode-unstable-1.15.3+20240927gitbb819bb49

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

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath

renode-unstable

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j85iw5hl3rm1js3skjssp36lh8i8kwy3-renode-unstable-1.15.3+20240927gitbb819bb49 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/2f6bd555eef686f8ca922bd435cf9f4dbfade946#renode-unstable

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/j85iw5hl3rm1js3skjssp36lh8i8kwy3-renode-unstable-1.15.3+20240927gitbb819bb49
ls -la /nix/store/j85iw5hl3rm1js3skjssp36lh8i8kwy3-renode-unstable-1.15.3+20240927gitbb819bb49/bin

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

1 package built:

renode-unstable

Maintainer pings
cc @otavio for testing.

[!TIP]
As a maintainer, if your package is located under pkgs/by-name/*, you can comment @NixOS/nixpkgs-merge-bot merge to automatically merge this update using the nixpkgs-merge-bot.

Add a :+1: reaction to pull requests you find important.

@NixOS/nixpkgs-merge-bot merge


Meross Humidifier exposed as a Humidifier tiles not a fan

Please explain your feature request in a one or two sentences.

I have just bought the Meross Humidifier (MSXH0). I realised that it is exposed as a fan tile. Homekit has a humidifier tile, as seen in the photo below (from a Vocolinc Flowerbud) which is very useful, as Siri works correctly, and it allows you to create the correct shortcut.

Is your feature request related to a problem? Please describe.
It would be amazing if this plugin could expose the Humidifier as a humidifier instead of a fan

Any particular Meross devices that this relates to?
Meross MSXH0 and probably any other humidifier or diffuser..

Anything else?

Hi @Marfre888
Any Homekit humidifier accessory type requires the current air humidity to be set. In this case the meross humidifier doesn’t report the current humidity, this is why I had to expose as a fan accessory type instead.
The homekit humidifier UI is based around the target and the current humidity, turning on and off when required automatically. So even hard coding a current humidity value of say 50% would seem more counter intuitive than a simple fan.
I can potentially look into exposing as a humidifier if you have another meross device sensor in the room that provides a current humidity value?

Hey @bwp91
Yes, I see where you are coming from.
However, the Homebrdige Broadlink RM Pro plugin also has the same problem when exposing an HVAC system, as the IR blaster doesn't have a temperature readout.
As a workaround, they have integrated two options into homebridge (1), either the ability to set a target value (which is only for aesthetics), or you can push the room temperature to a file on the host device which the plugin will read from. I have set up through homekit automation where every time the temp changes, it collects the temp and pushes to the set file through ssh (2), however, iOS 15.0 broke the ssh command.
(1) 'pseudoDeviceTemperature': 0
OR
'temperatureFilePath': "****"
(2) cd /home/pi/Documents/
echo "Number" > temperature.txt
This would mean that the current settings of 50% for intermittent and 100% for continuous would need to be moved to a separate switch, or incorporated into a slide if that is possible.
Furthermore, the led is exposed as a slider, however in this case it is only possible to turn it on or off. Would it be possible to expose it as below?

With regards to the led is it not possible to change the brightness or the colour?

Ahh shoot, Homekit doesn't allow you to change the led colors if the tile is an on/off light right?
What do you think about the other suggestions?

Is it possible to choose between Continuous or Intermittent when setting up the on/off switch?
I don't really mind about having a dedicated switch for the two states, I only want to be able to start the humidifier in Intermittent mode as it's the only mode I use.


Fixup a number of issues with the credhub integration

In experimenting with the CredHub integration I came across a number of issues while debugging.
Once this PR passes CI, I'll abandon the separate PRs I made for these earlier today.
See also related https://github.com/concourse/concourse/pull/1725.

@vito - thanks for merging the PR in the Concourse bosh release yesterday. Not sure if you saw this one or not, but wanted to draw it to your attention as you'll need to take at least some of the commits in this PR too before cutting a new bosh release, else anyone who isn't explicitly setting --insecure-skip-verify will see a nasty panic when atc starts up.

@aeijdenberg, can you be a little more explicit about your changes here. Assume they are not obvious.

Hi @jtarchie,
Here are some details:

Changes atc to fail validation of arguments at startup if an unexpected positional argument is specified. This is to prevent a re-occurrence of a bug like https://github.com/concourse/concourse/pull/1725, whereby if atc is invoked with:

atc ... --credhub-insecure-skip-verify false

then this would actually have the opposite behavior than desired. ie since it's a boolean parameter, no value is expected, just specifying it sets it to true, and any value passed, prior to the change, was silently ignored by atc.

The latest version of github.com/cloudfoundry-incubator/credhub-cli/credhub which seems to be installed on your CI server, has some slightly changed method names, so this updates to compile. i.e Get() changes to GetLatestVersion(), and SkipTLSValidation() now takes a parameter.

IsConfigured() was previously incorrectly requiring that all parameters were set (and it was missing some). Changes this to check if any parameters are set, so that the Validate() method is invoked any time the user specifies intent to use CredHub.

Changes Validate() to actually validate all required arguments, instead of a subset.

Fix NewVariablesFactory() so that it stops passing a nil credhub.Option which would cause a panic() on start up any time that --credhub-insecure-skip-verify was not set.

Adds the credential manager set of options to the credsGroup instead of the authGroup. I'm less sure of this one - it appeared to me that this is more cosmetic fix.

I suspect there are probably more issues, but these changes at least allow atc to startup successfully when --credhub-insecure-skip-verify is not set, which was previously (a) not possible due to the panic() and (b) difficult to invoke due to the other ERB generation bug.
My suspicions is that we'll need some extra parameters to include a CA cert for UAA, which may have a different CA than CredHub (current that's the default behavior for a bosh install, see https://github.com/cloudfoundry/bosh-deployment/pull/157), but I hadn't gotten to that point of testing yet.
Hope that helps.

@vito @jtarchie
I note that v3.6.0 Concourse is now released, without this patch. I've tested it locally and verified that a previously valid configuration of:
- type: replace
  path: /instance_groups/name=web/jobs/name=atc/properties?/credhub
  value:
    client_id: foo
    client_secret: bar
    url: https://<IP_ADDRESS>
    tls:
      ca_cert: |
        a cert

will cause a segfault on startup:
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x0 pc=0xaade3a]

goroutine 1 [running]:
github.com/cloudfoundry-incubator/credhub-cli/credhub.New(0x7ffd4f0dce19, 0x11, 0xc42004b340, 0x2, 0x2, 0xc42004b320, 0x412b08, 0x60)
	/var/vcap/packages/atc/src/github.com/cloudfoundry-incubator/credhub-cli/credhub/new.go:29 +0x10a
github.com/concourse/atc/creds/credhub.CredHubManager.NewVariablesFactory(0x7ffd4f0dce19, 0x11, 0x7ffd4f0dceb1, 0xa, 0xc4201f0790, 0x1, 0x1, 0x0, 0x7ffd4f0dce7b, 0x3, ...)
	/var/vcap/packages/atc/src/github.com/concourse/atc/creds/credhub/manager.go:61 +0xf2
github.com/concourse/atc/creds/credhub.(*CredHubManager).NewVariablesFactory(0xc4200f8a00, 0x11363a0, 0xc420052c60, 0xc42000e298, 0x1, 0x1, 0x11363a0)
	<autogenerated>:1 +0x92
github.com/concourse/atc/atccmd.(*ATCCommand).Runner(0xc4201c8000, 0xc420173c00, 0x0, 0x6e, 0x6f, 0xc420173c00, 0x0, 0x6e)
	/var/vcap/packages/atc/src/github.com/concourse/atc/atccmd/command.go:249 +0x5ae
github.com/concourse/atc/atccmd.(*ATCCommand).Execute(0xc4201c8000, 0xc420173c00, 0x0, 0x6e, 0x0, 0x0)
	/var/vcap/packages/atc/src/github.com/concourse/atc/atccmd/command.go:203 +0x4d
main.main()
	/var/vcap/packages/atc/src/github.com/concourse/atc/cmd/atc/main.go:24 +0xe4

Operators can workaround by explicitly setting insecure_skip_verify: true, ie:
- type: replace
  path: /instance_groups/name=web/jobs/name=atc/properties?/credhub
  value:
    client_id: foo
    client_secret: bar
    url: https://<IP_ADDRESS>
    tls:
      insecure_skip_verify: true
      ca_cert: |
        a cert

however without taking some of the commits in this PR, it is not possible to enable TLS validation (which was always documented as default, but only became so, and possible to enable via the bosh release in v3.6.0).

thanks a bunch!


setup: fix typo!

Else running the setup script gives a SyntaxError

Looks good to me. Thanks Luke!


game_scores table added

Description
A new table has been created based on the discussion to have a new table called game_scores.
Fixes # (New table)
How to test?
knex migrate:latest
Mysql
Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have merged the latest version of the source branch (typically develop) into this branch before pushing my changes
[ ] This PR is ready to be merged and not breaking any other functionality

This PR has been deleted because it has (Some checks were not successful) and Krithi has created a new PR  #139