Dependency is not compatible on 2022.x (Microsoft.CodeAnalysis.Scripting 4.4.0)

Hello there,
I'm a big fan of Polyglot Notebook, and when I found UnityNotebook, I thought it would be very interesting and useful.
However, when I used the package, I got the following exception.

NotImplementedException - The method or operation is not implemented.
  at Microsoft.CodeAnalysis.Scripting.Hosting.CoreAssemblyLoaderImpl.LoadFromStream (System.IO.Stream peStream, System.IO.Stream pdbStream) [0x00000] in <7e18d96c074143d381e7b567cf05908a>:0
  at Microsoft.CodeAnalysis.Scripting.Hosting.InteractiveAssemblyLoader.LoadAssemblyFromStream (System.IO.Stream peStream, System.IO.Stream pdbStream) [0x00000] in <7e18d96c074143d381e7b567cf05908a>:0
  at Microsoft.CodeAnalysis.Scripting.ScriptBuilder.Build[T] (Microsoft.CodeAnalysis.Compilation compilation, Microsoft.CodeAnalysis.DiagnosticBag diagnostics, System.Boolean emitDebugInformation, System.Threading.CancellationToken cancellationToken) [0x000c6] in <7e18d96c074143d381e7b567cf05908a>:0
  at Microsoft.CodeAnalysis.Scripting.ScriptBuilder.CreateExecutor[T] (Microsoft.CodeAnalysis.Scripting.ScriptCompiler compiler, Microsoft.CodeAnalysis.Compilation compilation, System.Boolean emitDebugInformation, System.Threading.CancellationToken cancellationToken) [0x00026] in <7e18d96c074143d381e7b567cf05908a>:0
  at Microsoft.CodeAnalysis.Scripting.Script`1[T].GetExecutor (System.Threading.CancellationToken cancellationToken) [0x0002b] in <7e18d96c074143d381e7b567cf05908a>:0
  at Microsoft.CodeAnalysis.Scripting.Script`1[T].RunAsync (System.Object globals, System.Func`2[T,TResult] catchException, System.Threading.CancellationToken cancellationToken) [0x0001b] in <7e18d96c074143d381e7b567cf05908a>:0
  at Microsoft.CodeAnalysis.Scripting.Script`1[T].RunAsync (System.Object globals, System.Threading.CancellationToken cancellationToken) [0x00000] in <7e18d96c074143d381e7b567cf05908a>:0
  at Microsoft.CodeAnalysis.CSharp.Scripting.CSharpScript.RunAsync[T] (System.String code, Microsoft.CodeAnalysis.Scripting.ScriptOptions options, System.Object globals, System.Type globalsType, System.Threading.CancellationToken cancellationToken) [0x00019] in <1e780c89915643f7b317d08d1cb15611>:0
  at Microsoft.CodeAnalysis.CSharp.Scripting.CSharpScript.RunAsync (System.String code, Microsoft.CodeAnalysis.Scripting.ScriptOptions options, System.Object globals, System.Type globalsType, System.Threading.CancellationToken cancellationToken) [0x00000] in <1e780c89915643f7b317d08d1cb15611>:0
  at UnityNotebook.Evaluator.ExecuteCodeAsync (System.String code) [0x00066] in .\Library\PackageCache\com.mstevenson.unitynotebook@3351f7b719\Editor\Evaluation\Evaluator.cs:99

So I started debugging the package, this worked well in 2021.x so I started to debug them and I finally discovered that it was using reflection in the AssemblyLoaderImpl with CoreClrShim used by the InteractiveAssemblyLoader in Microsoft.CodeAnalysis.Scripting and the logic that determines if it is CoreCLR.
AssemblyLoaderImpl in 4.4.0 : https://github.com/dotnet/roslyn/blob/1ce8866c9de4c2d67351ef6863699dee03b0804a/src/Scripting/Core/Hosting/AssemblyLoader/AssemblyLoaderImpl.cs#L24-L34
CoreClrShim in 4.4.0 :  https://github.com/dotnet/roslyn/blob/1ce8866c9de4c2d67351ef6863699dee03b0804a/src/Compilers/Shared/CoreClrShim.cs#L22-L23
Because of the issues with checking to see if it's CoreCLR in this way, in 2022.x assumes that the reflection type exists (defined in mscorlib) and uses the abstract CoreAssemblyLoaderImpl class, which is not implemented.
In the latest version of the source code, I found that this is implemented to be completely decoupled via compiler preprocessing instructions.
https://github.com/dotnet/roslyn/blob/09ef0c03d033b17f0e5750f265275ed6d1f3cca7/src/Scripting/Core/Hosting/AssemblyLoader/AssemblyLoaderImpl.cs
However, I have not yet confirmed that this can be resolved with the latest version, I will update this issue when I got some results, also I'll open a pull request if there is a clean solution.

Update : I tried to use newer dependencies with it but somehow it's still uses CoreClrShim, so I have trying this workaround, it works well!
I'll do request PR with it soon.


Ms.aKa

file:///detection_rules/main.py%0A%0AREAD%20MORE%0A%0A%C2%A0Michael%20Elkan

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

ID: 55f2bb3a-6619-88c0-ba29-23af30fcb301
Version Independent ID: 0ede4455-b1df-ffef-743f-126a5e9a1a00
Content: Service status - Azure DevOps
Content Source: docs/user-guide/service-status-info.md
Product: devops
Technology: devops-accounts
GitHub Login: @chcomley
Microsoft Alias: chcomley

@feliciousity -- Felicia, thank you for your feedback.  Please the clarify your intended task.  Meanwhile, consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@feliciousity -- Felicia, thank you for your feedback. Please the clarify your intended task. Meanwhile, consider these resources:

Azure DevOps Services
Azure DevOps on Stack Overflow

@feliciousity -- Felicia, I'm still not sure what this issue is regarding.  Please provide additional context.


Improve unparser MySQL compatibility

Please let me know if you prefer me to split this into separate PRs. Combined as the changes are related/follow the same logic and to avoid resolving conflicts after PRs are merged.
Which issue does this PR close?
PR addresses unparser issues producing invalid sql for MySQL and implements support for IntervalStyle::MySQL
1. Invalid CAST(col AS Timestamp) SQL for MySQL.
MySQL cast function does not support Timestamp for CAST and requires DATETIME

DATETIME[(M)]
Produces a DATETIME value. If the optional M value is given, it specifies the fractional seconds precision.

Timezone information is correctly handled by MySQL when casting with DATETIME.
2. Unsupported date_part function to extract Datetime subfield
MySQL does not support date_part function so PR introduces configurable option to specify Datetime subfield extraction style for unparsing. Different DBMSs follow different standards; popular ones are:
date_part('YEAR', date '2001-02-16')
EXTRACT(YEAR from date '2001-02-16')

Some DBMSs, like Postgres, support both, whereas others like MySQL, Amazon Athena require EXTRACT.
3. invalid CAST(col AS BigInt) SQL for MySQL.
MySQL cast function does not support BigInt and requires SIGNED for CAST

SIGNED [INTEGER]
Produces a signed BIGINT value.

Note: sqlparser crate does not have Signed type so we use ast::DataType::Custom as a workaround
Rationale for this change
PRs implements IntervalStyle::MySQL  and adds support for alternate formats for Timestamp, Int64, Datetime part unparsing via Dialect customization.
What changes are included in this PR?
Please see above
Are these changes tested?
Manual testing + unit test for each modification.
Are there any user-facing changes?
CustomDialectBuilder now supports more options for Dialect customization (Timestamp, Int64 unparsing and Datetime part extraction).

Thanks again @sgrebnov

Thank you Andrew @alamb!


Add NumPy pad

Would be nice to have NumPy's pad implemented for Dask Arrays. May also help clean up some other code by having this exposed as part of the API.

Presumably this would help with map_overlap?
On Mon, Jun 5, 2017 at 2:41 PM, jakirkham<EMAIL_ADDRESS>wrote:

Would be nice to have NumPy's pad
https://docs.scipy.org/doc/numpy-1.12.0/reference/generated/numpy.pad.html
implemented for Dask Arrays. May also help clean up some other code by
having this exposed as part of the API.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/dask/dask/issues/2415, or mute the thread
https://github.com/notifications/unsubscribe-auth/AASszKkNbNJIxc-ibwguQHbU8TZo-NmTks5sBEv1gaJpZM4NwaQT
.

Possible duplicate of #1926.

OTOH maybe we could just re-present ghost under the numpy.pad API. We don't support every option that numpy.pad does, but maybe what we provide is already good enough for common use cases. That should allow us to get some feedback on these internals. It would also allow improvements to ghost to be captured by map_overlap pretty easily.

Have an implementation of pad for Dask Arrays in PR ( https://github.com/dask/dask/pull/3578 ). Feedback welcome.


Place istio.metadata_exchange before RBAC filters for network and HTTP filters

Please provide a description of this PR:
Fixes #41066
In istio 1.12, RBAC filter shows up before metadata exchange filter for both network and HTTP (subfilters of http_connection_manager) filters. This was preventing the metadata to be populated for requests that were denied (403 in case of HTTP or dial failed for TCP) in OAP access logs. This PR fixes the order by putting RBAC filter(both network and http) before istio.metadata_exchange filter while generating network or http filters.
This exists even in istio 1.15 and will need a separate fix because a lot of code changed around plugins between 1.12 and 1.15.

Hi @aniketsingh03. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hi @aniketsingh03, 1.12 was EOL as of July 12th.  So if this merged there would not be another official release/build with the fix.  Is this still present in 1.13 / 1.14 / 1.15?

Hi @GregHanson. Yes, this is present in 1.13, 1.14 and 1.15.

@aniketsingh03 can you submit this to the master branch then?  I think you will have to close this one and open another.  We normally fix the problem in master branch first and then cherry-pick the fix to the individual release branches.  You can add the cherrypick/release-1.13,cherrypick/release-1.14, and cherrypick/release-1.13 labels to that new PR, and those PR's will get created automatically once the one to master merges

@GregHanson I think the cherry picks won't work directly because a lot of code has changed between 1.12 and master, so manual cherry picks have to be created. I raised https://github.com/istio/istio/pull/41261 for master.


@XmlAttribute is ignored if @XmlAccessorType(XmlAccessType.NONE) is used by swagger-core 1.5.16 and master

If the @XmlAccessorType(XmlAccessType.NONE) is used on some model class and explicit annotation of fields or methods with the @XmlAttribute annotation has no effect.
The issue occurs using swagger-core 1.5.16 and even the most recent one within master seems to have the same code base in this respect.
Problem is likely the io.swagger.jackson.ModelResolver.ignore(Annotated,XmlAccessorType,String,Set) method, which just honors the @XmlElement annotation in this case, but not the @XmlAttribute one.
Example code can be found at https://github.com/dranuhl/swagger-bug-examples using swagger 1.5.16 for Jersey 1.x and 2.x.
See also Swagger Online forum report.

The following diff resolves the above described issue with v1.5.16:
diff --git a/modules/swagger-core/src/main/java/io/swagger/jackson/ModelResolver.java b/modules/swagger-core/src/main/java/io/swagger/jackson/ModelResolver.java
index 035d49f..ac36489 100644
--- a/modules/swagger-core/src/main/java/io/swagger/jackson/ModelResolver.java
+++ b/modules/swagger-core/src/main/java/io/swagger/jackson/ModelResolver.java
@@ -54,6 +54,7 @@ import javax.validation.constraints.Pattern;
 import javax.validation.constraints.Size;
 import javax.xml.bind.annotation.XmlAccessType;
 import javax.xml.bind.annotation.XmlAccessorType;
+import javax.xml.bind.annotation.XmlAttribute;
 import javax.xml.bind.annotation.XmlElement;
 import javax.xml.bind.annotation.XmlRootElement;
 import javax.xml.bind.annotation.XmlSchema;
@@ -617,7 +618,8 @@ public class ModelResolver extends AbstractModelConverter implements ModelConver
             return false;
         }
         if (xmlAccessorTypeAnnotation.value().equals(XmlAccessType.NONE)) {
-            if (!member.hasAnnotation(XmlElement.class)) {
+            if (!member.hasAnnotation(XmlElement.class) &&
+                !member.hasAnnotation(XmlAttribute.class)) {
                 return true;
             }
         }

See also pull request #2409, which even includes some tests.

This issue duplicates #1847.

merged #2409


ulimits are ignored for systemd processes

ISSUE TYPE

Bug Report

COMPONENT NAME

packaging

CLOUDSTACK VERSION

N/A

CONFIGURATION

N/A
OS / ENVIRONMENT

RHEL7+
SUMMARY

We are setting max process limits in /etc/security/limits.conf to unlimited for cloud user. But RHEL7+ uses systemd which ignores the limits set in /etc/security/limits.conf or /etc/security/limits.d/*.conf.
STEPS TO REPRODUCE

Run cat /proc/$(ps aux |grep cloudstack-management|grep -v grep |awk '{print $2}')/limits
This will print the limit for the cloudstack-management process. The max process limit is not set to unlimited.

EXPECTED RESULTS

The max process limit is set to unlimited.

ACTUAL RESULTS

The max process limit is not set to unlimited.

@vishesh92 , is this limited to RHEL7+ or is this specific to the use of systemd, i.e. loads of systems suffer from this?

@vishesh92 , is this limited to RHEL7+ or is this specific to the use of systemd, i.e. loads of systems suffer from this?

I noticed this in RHEL. But it's probably specific to the use of systemd.
The fix should be simple for this.

The fix will be to specify the limits in systemd configuration file.
Ref.: https://access.redhat.com/solutions/1257953

Fixed by https://github.com/apache/cloudstack/pull/10040


Implement TryFromIntError conversion for AnchorError

I noticed it was a bit painful to cast integers with try_into and try_from because you have to either unwrap() or map_err(||).
What about implementing TryFromIntError for Error so we can use the ? operator?

Sure! I have added a test case.

My bad, I should have thought about it!

Feel free to modify the changelog entry if the description is not clear.


Update aind stage step size when loading in mouse

Pull Request instructions:

Please follow the update protocol
Answer the questions below in detail. Your responses will be emailed to experimenters.
If the experimenters must do anything new, provide detailed step by step instructions on the wiki
If computer maintainers need to manually update anything, provide detailed step by step instructions
Use markdown syntax in order for your comments to be rendered reliably in the email: "1." instead of "1)", use four spaces for indents.
If you use the keyword "skip email" in the title, it will skip the email updates
Merges from "develop" into "production_testing" should use the keyword "production merge" in the title for reliable indexing of updates
Merges from "production_testing" into "main" should use the keyword "update main"

Describe changes:

Updates step size for aind stage when loading in a mouse

What issues or discussions does this update address?

resolves #808

Describe the expected change in behavior from the perspective of the experimenter

Step size will update when user loads in mouse

Describe any manual update steps for task computers

None

Was this update tested in 446/447?

[x] 447

Thanks for the fix. Looks good


Broken link

The link to Outbox pattern is broken. @mvelosop can you help figure out where it should go?

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

ID: c5ab515b-a39a-983d-2a09-13ca5ccf5125
Version Independent ID: 82f66a0e-6ad3-c419-36cb-ecc985b9b192
Content: Asynchronous message-based communication
Content Source: docs/architecture/microservices/architect-microservice-container-applications/asynchronous-message-based-communication.md
Product: dotnet-architecture
Technology: microservices
GitHub Login: @nishanil
Microsoft Alias: nanil

Hi @mairaw, updated, used an equivalent link to a recent blog post.


Fix Tests by adding example app entitlements

Adds entitlements to the example app so that calls to the keychain are possible in unit tests.

Coverage remained the same at 80.692% when pulling ba40dce71342143b9082b5ccbd09673d95be4e18 on fix_tests into a66aa176d059a974bd925e31c4114a00cb6c8946 on master.

👍 Green - my favorite color!


Multi-day events not showing in week or day views

Context:

Browsers: Chrome Version 130.0.6723.92 (Official Build) (arm64) and safari Version 18.0.1 (206<IP_ADDRESS>.7)
Schedule-X version [e.g. v1.1.0] Please make sure that you've tried the latest version before reporting the bug.
2.4.1

Describe the bug
Multi day events are not showing on the Day on Week views, only the Month view. (this feels more likely to be a misunderstanding on my part than a bug so apologies in advance for that.
To Reproduce
I've created an empty remix app (pnpx create-remix@latest) and added the smallest subset of code I can make that reproduces the problem. This is the relevant calendar code:
import {
  viewDay,
  viewMonthAgenda,
  viewMonthGrid,
  viewWeek,
} from "@schedule-x/calendar";
import { ScheduleXCalendar, useCalendarApp } from "@schedule-x/react";
import<EMAIL_ADDRESS>import { addDays } from "date-fns";

export default function Index() {
  const events = [
    {
      id: "f-0",
      title: "foo",
      description: "foo event",
      start: new Date().toISOString(),
      end: addDays(new Date(), 1).toISOString(),
    },
  ];
  const calendar = useCalendarApp({
    views: [viewDay, viewWeek, viewMonthGrid, viewMonthAgenda],
    events,
  });

  return (
        <ScheduleXCalendar calendarApp={calendar} />
  );
}

Expected behavior
Expected to see the multi-day event on all three views.
Screenshots
Day view:

Week view:

Month view:

Things that could speed up the process

[ ] I can picture implementing at least parts of this fix
[ ] I believe I know how to do this, and am willing to implement the whole thing.
[ ] I have a Schedule-X premium license

...adding my own:

[X] Assessing Schedule-X with the intention of buying a premium licence for the resource scheduler functionality

ok it looks like a date format issue. i was using date.toISOString() which formats dates like this: '2024-11-05T09:17:27.287Z'. if i change the dates to this: '2024-11-05 09:17' all three views work.
leaving this issue open for now as it feels like inconsistent behaviour for it to work on the monthly view but not on the daily or weekly - and for it to not throw an error when given a date in an invalid format.
would say that either always working with an ISO date string or always throwing a descriptive error would be good fixes, though my preference would be for the first.

I think the library should probably better start throwing errors or at the least output console errors for unsupported date string format.
We can leave this issue open until I’ve added such validation. Thanks for reporting!