ORT should fail gracefully ...

ORT's analyzer crashes on .ort.yml with invalid fields or an incorrectly specified --repository-configuration-file.
The expected behaviour would an analyzer error in the report and ORT should carry on.
Only a fatal error that makes it impossible for the analyzer (or ORT as a whole) to produce meaningful results should terminate execution.
18:26:18 ________ _____________________
18:26:18 \_____  \\______   \__    ___/ the OSS Review Toolkit, version 6e3c27d.
18:26:18  /   |   \|       _/ |    |    Running 'analyze' on Java 10 and Linux with
18:26:18 /    |    \    |   \ |    |    JAVA_HOME = /opt/jdk-10
18:26:18 \_______  /____|_  / |____|    ANDROID_HOME = /opt/android-sdk-linux
18:26:18         \/       \/
18:26:18
18:26:18 The following package managers are activated:
18:26:18 	Bower, Bundler, Cargo, DotNet, GoDep, Gradle, Maven, NPM, NuGet, PhpComposer, PIP, SBT, Stack, Yarn
18:26:18 Analyzing project path:
18:26:18 	/workspace/project/Downloader/unknown/Client%20Microservices/unknown
18:26:18 16:26:18.628 INFO  - Using configuration file '/workspace/project/Downloader/unknown/Client%20Microservices/unknown/.ort.yml'.
18:26:19 Exception in thread "main" com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "projects" (class com.here.ort.model.config.Excludes), not marked as ignorable (2 known properties: "paths", "scopes"])
18:26:19  at [Source: (File); line: 148, column: 140] (through reference chain: com.here.ort.model.config.RepositoryConfiguration["excludes"]->com.here.ort.model.config.Excludes["projects"])
18:26:19 	at com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException.from(UnrecognizedPropertyException.java:61)
18:26:19 	at com.fasterxml.jackson.databind.DeserializationContext.handleUnknownProperty(DeserializationContext.java:823)
18:26:19 	at com.fasterxml.jackson.databind.deser.std.StdDeserializer.handleUnknownProperty(StdDeserializer.java:1153)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownProperty(BeanDeserializerBase.java:1589)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.handleUnknownProperties(BeanDeserializerBase.java:1543)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeUsingPropertyBased(BeanDeserializer.java:504)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.deserializeFromObjectUsingNonDefault(BeanDeserializerBase.java:1287)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:326)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:159)
18:26:19 	at com.fasterxml.jackson.databind.deser.SettableBeanProperty.deserialize(SettableBeanProperty.java:530)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeWithErrorWrapping(BeanDeserializer.java:528)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializer._deserializeUsingPropertyBased(BeanDeserializer.java:417)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializerBase.deserializeFromObjectUsingNonDefault(BeanDeserializerBase.java:1287)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserializeFromObject(BeanDeserializer.java:326)
18:26:19 	at com.fasterxml.jackson.databind.deser.BeanDeserializer.deserialize(BeanDeserializer.java:159)
18:26:19 	at com.fasterxml.jackson.databind.ObjectMapper._readMapAndClose(ObjectMapper.java:4013)
18:26:19 	at com.fasterxml.jackson.databind.ObjectMapper.readValue(ObjectMapper.java:2921)
18:26:19 	at com.here.ort.analyzer.Analyzer.analyze(Analyzer.kt:164)
18:26:19 	at com.here.ort.commands.AnalyzerCommand.runCommand(AnalyzerCommand.kt:156)
18:26:19 	at com.here.ort.CommandWithHelp.run(CommandWithHelp.kt:53)
18:26:19 	at com.here.ort.Main.runCommand(Main.kt:112)
18:26:19 	at com.here.ort.CommandWithHelp.run(CommandWithHelp.kt:53)
18:26:19 	at com.here.ort.Main.run(Main.kt:95)
18:26:19 	at com.here.ort.Main.main(Main.kt:75)
18:26:19
18:26:19 FAILURE: Build failed with an exception.

Looks like this is related to @fviernau's removal of project excludes in https://github.com/heremaps/oss-review-toolkit/pull/1639.

This should be the relevant line by now:
https://github.com/oss-review-toolkit/ort/blob/42845fa5eb5fbb1a9bc617aa778c2979ca0da26d/cli/src/main/kotlin/commands/AnalyzerCommand.kt#L174
But I'm wondering whether throwing an exception isn't the right thing to do on a corrupted / invalid repository configuration file. Or should be just create an OrtIssue / analyzer error instead, @oss-review-toolkit/core-devs?

Ping again @oss-review-toolkit/core-devs, and esp. @fviernau and @adambhere! Is this relevant?

In my opinion ORT behavior is good as-is. I've fixed a bunch of issues for such exceptions, and IIRC I was always able to identify the root cause quickly based on the exception message.
Besides that, behavior IIRC is consistent with how serialization issues of package configurations and curations  or other configurations files are handled.

Agreed, so let's close this.


[HOTFIX] Disable Java style checker

cc @JoshRosen

Test build #49817 has started for PR 10853 at commit 93dbf30.

Test build #49817 has finished for PR 10853 at commit 93dbf30.

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/49817/
Test PASSed.


Destroyed our cluster

This recommendation destroyed our clusters. The letters for the mounted drives changed. Please clarify in all the docs how mounted drives are supposed to be handled regarding mounting and letters. A lot of extensions including Service Fabric needs a hard coded value for paths.

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

ID: ad2cf190-169c-73de-2e33-e2763d1930a8
Version Independent ID: 858cd630-1380-1ac4-166e-4779c9d7f943
Content: Patch the Windows operating system in your Service Fabric cluster - Azure Service Fabric
Content Source: articles/service-fabric/how-to-patch-cluster-nodes-windows.md
Service: service-fabric
GitHub Login: @sukanyamsft
Microsoft Alias: sukanyas

@FredrikDahlberg Thank you for reaching out to us!  We've assigned this to the document author for further review.

Hi @FredrikDahlberg, Added recommendation to the doc.  This issue is resolved in a PR.  Here is the link to the PR - https://github.com/MicrosoftDocs/azure-docs-pr/pull/196522
#Please-close this issue


SelfAccessorFixer - Fix type declarations replacement

Fixes #3079.

👍

why not 2.2 ?

Because of PHP bug #60573 which was fixed in PHP 5.4.1. As 2.2 supports PHP 5.3, it would be affected by the bug because of the changes applied by the fixer. An alternative would be to disable the fixer on the project so we can target 2.2.

:+1: for disabling the fixer when running on PHP 5.4.1 (and remove support for PHP 5.4.1 in composer.json)

2.2 shall not bump php requirement

We cannot disable the fixer conditionally as we can't apply the change without breaking the tool on PHP 5.3: CI builds would fail on higher versions, where the fixer would still be enabled and try to apply the change again.

2.2 shall not bump php requirement

no one suggested that, I just suggest we black list 5.4.1, so no bump

We cannot disable the fixer conditionally

we can check in the isCandidate is running on PHP 5.4.1 no, and on CI we can pick any other PHP 5.4.x version but 5.4.1?

bug was not present only in 5.4.1, it was present in 5.4.1 and lower, won't it ?

hmm indeed,
5.1.6 - 5.4.0, hhvm-3.10.1 - 3.22.0
https://3v4l.org/3dLV3
do not raise the warning during linting

The issue is the change in SignatureInterface that triggers the error on PHP lower than 5.4.1.

@Korikulum this PR should resolve your issue, do you maybe have time to review or test as well?

@SpacePossum Hi, I've tested the changes & it seems that it still doesn't work when the type declarations are nullable, eg:
class Foo
{
    public function bar(?Foo $foo): ?Foo {}
}

Other then that, everything is working fine.

@SpacePossum And I just realized I was testing on php 7, not 7.1, so I have to correct myself again, ?self does work in PHP, so my initial statement was correct, the fix doesn't work when the type declarations are nullable:
class Foo
{
    public function bar(?Foo $foo): ?Foo {}
}

Sorry about the confusion.

ping @julienfalque :)

Is there anything left to do here? ?self seems to work fine.

I think, IIUC, that this test is missing:
            [
                 '<?php interface Foo { public function bar(): ?self; }',
                 '<?php interface Foo { public function bar(): ?Foo; }',
             ],

Test added (and fixed as it was actually failing).

Looks solid to me.
Can I bother you; the last fix has a class variant for fixing proving the fixer works correctly, can we've a interface with comment- and whitespace-mess as well? (something like <?php interface D{public function a()\t/**/?:/**/Foo;})
after that and test are green :+1: lets :ship:

Test added.

Thank you @julienfalque.


Support for XGLM: How to achieve faster inference speed?

Describe a requested feature
Thanks for releasing this great library! I am currently working on deploying facebook/xglm-7.5B, which is currently not supported by parallelformers.
POLICY.md provides a comprehensive guide for parallelizing my own models. But I am a little bit unsure of

which weights to be parallelized and
how many GPUs should be used

for a better inference speed.
Architecture of XGLM-7.5B
root
├── model (XGLMModel)
│   ├── embed_tokens (Embedding) weight:[256008, 4096]
│   ├── embed_positions (XGLMSinusoidalPositionalEmbedding) weights:[2050, 4096]
│   ├── layers (ModuleList)
│   │   └── 0-31(XGLMDecoderLayer)
│   │       ├── self_attn (XGLMAttention)
│   │       │   └── k_proj,v_proj,q_proj,out_proj(Linear) weight:[4096, 4096] bias:[4096]
│   │       ├── self_attn_layer_norm,final_layer_norm(LayerNorm) weight:[4096] bias:[4096]
│   │       ├── fc1 (Linear) weight:[16384, 4096] bias:[16384]
│   │       └── fc2 (Linear) weight:[4096, 16384] bias:[4096]
│   └── layer_norm (LayerNorm) weight:[4096] bias:[4096]
└── lm_head (Linear) weight:[256008, 4096]

@hyunwoongko Many thanks for your support :)

Hi @hyunwoongko May I have an update on this feature?

@z-bookworm Sorry for late. can you make a policy of the model?

You can refer to https://github.com/tunib-ai/parallelformers/blob/main/parallelformers/policies


Added a font and a text command for emojis

Just as the title says: simply an added font and a text command for using black and white emojis, nothing changed in working features.

looks good to me.


Improved query string encoding and decoding

Following up on https://github.com/ts-rest/ts-rest/pull/80, I've transitioned the nest library to use req.query and req.params rather than parsing them from the URL. This now allows the usage of arrays and nested objects in query params. I've made sure that this use-case is also covered in the clients by changing convertQueryParamsToUrlString to use qs.stringify which is the same library used internally by express.js.
Also tweaked the Nest implementation such that the all contracts' AppRoutes are added to their respective methods' metadata. This happens only once during runtime at startup, and therefore does need to be added to each request object. This allows us to maintain a single instance of ApiRouteInterceptor in the IoC container across all routes.
I've also changed how the status and response body are returned from ApiRouteInterceptor. Throwing an HttpException meant that no other interceptors could have been used since the thrown exception goes straight to Nest's base exception filter.
Added some tests in the example-nest app.

Hey @Gabrola! I was discussing how we could improve the query params parsing whilst chatting with a Colleague yesterday, so this is amazing!
My only concern was the added peer dependency, and whether it was worth the extra 9.8kB (Gz) requirement for qs (especially in the core package)
Do you think this is a worthy requirement? 🤔

Thinking on this, as we should support Nest and Express with as few dependencies as possible is it worthwhile to keep using encodeURIComponent in the client(s), then qs or Nest/Express specific implementations on the server libs?
qs is not likely to be an existing dep on many frontends right?

Thank you for your review! Yes, you're absolutely correct. qs is already a dependency of express/nest for its parse function, but it seems like the convertQueryParamsToUrlString function is only used by the frontend libraries. I agree though that it seems too large for what we need from it.
It should be straightforward to implement what we need, since qs has too many options (and code) to cater to other options such as comma-delimited arrays, etc.
Which makes me think, do you think it makes sense to add an option client-side to plug in a custom query serializer? Generally on the frontend you would be able to do this easily by passing your query params as string directly to fetch/got/axios, etc. However, by serializing in ts-rest we are essentially locking everyone in to our kinda-opinionated serialization.
There are some cases I could think of that might want to be handled differently in different apps. For example, in case of null do we serialize as ?foo=null, or just ?foo, or do we omit it entirely? What about undefined?
If we provide the option of passing a custom serializer (or qs 😆), we'd have the best of both worlds of not requiring an extra dependency with the core library, while also giving developers the flexibility if needed. Seems fitting now, since on the backend we are directly consuming req.query, so its already a hands-off experience when it comes to deserialization. But now the point raised in https://github.com/ts-rest/ts-rest/pull/80 comes into contention, I think now it'd make sense to allow custom style and explode options for query serialization in OpenAPI.

I like your suggestion.
Proposed Client queryParamsEncode

// qs
export const postsClient = initQueryClient(postsApi, {
  ...
  queryParamsEncode: ({params, route}) => `?${qs.stringify(params)}`
});

// JSON (or any other preferred encoding?)
export const postsClient = initQueryClient(postsApi, {
  ...
  queryParamsEncode: ({params, route}) => `?json=${JSON.stringify(params)}`
});

If we did this with the client it would allow any general encoding to be applied to a query client
In terms of standardisation, it's quite messy overall... doing this approach could allow ts-rest users to work with third-party API, no matter how they encode their params I suppose.
Proposed new default behaviour behaviour
My next question is what we standardise on, as the default between ts-rest clients and server implementations.
I don't like the unintuitive behaviour given that right now arrays don't function correctly...
Implement our own formatted query string (OpenAPI standard)
Can probably do this if we limit the scope to explode and deepObject
As can be seen here, Nest.js and Express happily parse these.

There is still a problem here, we still need to use Zod or similar to parse strings into numbers, enums etc. 🤔

@Gabrola, this was deceivingly simple... I'll keep trying some more unit tests.

cc @joshjacks this may help what we discussed last week 🤔

@Gabrola I just checked every imaginable data shape, nested structure, array, array in an array, dates, null, undefined etc and landed on this solution
/**
 *
 * @param query - Any JSON object
 * @returns - The query url segment, using explode array syntax, and deep object syntax
 */
export const convertQueryParamsToUrlString = (
  query: Record<string, unknown>
) => {
  const queryString = encodeQueryParams(query);
  return queryString?.length > 0 ? '?' + queryString : '';
};

export const encodeQueryParams = (query: Record<string, unknown>) => {
  return Object.keys(query)
    .flatMap((key) => tokeniseValue(key, query[key]))
    .map((pair) => {
      const [key, ...rhs] = pair.split('=');
      return `${key}=${rhs.map(encodeURIComponent).join('=')}`;
    })
    .join('&');
};

const tokeniseValue = (key: string, value: unknown): string[] => {
  if (Array.isArray(value)) {
    return value.flatMap((v, idx) => tokeniseValue(`${key}[${idx}]`, v));
  }

  if (value instanceof Date) {
    return [`${key}=${value.toISOString()}`];
  }

  if (value === null) {
    return [`${key}=`];
  }

  if (value === undefined) {
    return [];
  }

  if (typeof value === 'object') {
    return Object.keys(value).flatMap((k) =>
      // @ts-expect-error - accessing object keys
      tokeniseValue(`${key}[${k}]`, value[k])
    );
  }

  return [`${key}=${value}`];
};

This is considerably better than a 10KB dependency on the client (I think!), hopefully, we can then just utilize the express/nest built-in parsers.
Also for every test I ran the resulting query string though qs, to make sure it was able to parse it happily.
Note!
There is one difference, I went with the ?foo[0][0]=bar&foo[0][1] syntax to achieve nested arrays, fully qs compatible I believe.

@oliverbutler that's pretty neat! That's a much simpler than what I was working on since I was using the ?foo=bar&foo=baz format for arrays and that brought a bit of complexity. I'll add your implementation in with the extra unit tests I wrote and let me know what you think

@Gabrola I'm going to push this change to main, to be honest, it's not breaking as right now anyone who used an array/object definitely got runtime errors
Plus it's already got all of the unit tests, once that's done maybe just rebase from main? :)

wait correction, I can just push to your branch so we can polish this.

Concerning doing zod validations, I've messed a bit with it and finally landed on this solution.
const stringNumberTransform = (val: string, ctx: z.RefinementCtx) => {
  const parsed = parseInt(val, 10);
  if (Number.isNaN(parsed)) {
    ctx.addIssue({
      code: z.ZodIssueCode.custom,
      message: 'Not a number',
    });
    return z.NEVER;
  }
  return parsed;
};

export const contract = c.router({
  findAll: {
    method: 'GET',
    path: '/posts',
    summary: 'Get a paginated list of posts',
    query: z.object({
      page: z.string().default('1').transform(stringNumberTransform),
      pageSize: z.string().default('50').transform(stringNumberTransform),
    }),
    responses: {
      200: c.response<Post>(),
    },
  },
});

This gives us an input type of
{
    page?: string | undefined;
    pageSize?: string | undefined;
}

and an output type of
{
    sort: "asc" | "desc";
    sortBy: "name" | "createdAt" | "updatedAt";
    page: number;
    pageSize: number;
}

The recommended solution by zod is to use .preprocess() but that causes the input types to be unknown.

yeah, this is pretty much identical to how we solved a problem on our side like this... It's not perfect

@oliverbutler sure, yeah that sounds better if you push onto this branch. I pushed my changes to it so far, and split the query functionality into its own file.

@Gabrola Pushed! 👍 Commented out the query.ts export temporarily so you can reconcile the two implementations

@oliverbutler Perfect, thanks!

@Gabrola I think I tested pretty much everything, but if there are any oversights happy to help out.

@oliverbutler Your code passes all of the unit tests I thought of as well so it seems like everything's good. Only thing is that it seems like square brackets in the keys need to be URL encoded too, so I'll make sure that it done too.

Btw @Gabrola you've absolutely helped smash some awesome improvements out, I decided to add the allcontributors.org bot! Hopefully, you'll appear in the README :)
I really appreciate the help and ideas!

@oliverbutler So glad to hear that! I appreciate it mate!

@Gabrola Just pushed the fix to next and core to remove server-utils, is all good feature wise on your side, I'm super happy with this!


Update sbt-dependency-tree to 1.10.5

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

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scala-sbt", artifactId = "sbt-dependency-tree" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "org.scala-sbt", artifactId = "sbt-dependency-tree" }
}]

labels: sbt-plugin-update, early-semver-minor, semver-spec-minor, version-scheme:early-semver, commit-count:1

Superseded by #52.


pull request for e2e test at 01/16/2017 01:56:15

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Reuse the IngressLoadBalancerStatus structure

Why don't v1beta1.IngressLoadBalancerStatus and networking v1.IngressLoadBalancerStatus and corev1.LoadBalancerStatus and v1.LoadBalancerStatus reuse the same structure, so that the upper layer call will be more convenient
Versions before 1.26 returned v1.LoadBalancerStatus, why was version 1.26 removed?

For example

Make sure you do not remove things from the ingress status, otherwise external-dns would not work for ingress, which is the main purpose of it.

After upgrading the API of 1.26, the structure has changed

Maybe I miss something but https://kubernetes.io/docs/reference/kubernetes-api/service-resources/ingress-v1/#IngressStatus shows loadBalancer.ingress.hostname for example. I guess there are only added data, no?
// IngressLoadBalancerStatus represents the status of a load-balancer.
type IngressLoadBalancerStatus struct {
	// ingress is a list containing ingress points for the load-balancer.
	// +optional
	Ingress []IngressLoadBalancerIngress `json:"ingress,omitempty" protobuf:"bytes,1,rep,name=ingress"`
}

// IngressLoadBalancerIngress represents the status of a load-balancer ingress point.
type IngressLoadBalancerIngress struct {
	// ip is set for load-balancer ingress points that are IP based.
	// +optional
	IP string `json:"ip,omitempty" protobuf:"bytes,1,opt,name=ip"`

	// hostname is set for load-balancer ingress points that are DNS based.
	// +optional
	Hostname string `json:"hostname,omitempty" protobuf:"bytes,2,opt,name=hostname"`

	// ports provides information about the ports exposed by this LoadBalancer.
	// +listType=atomic
	// +optional
	Ports []IngressPortStatus `json:"ports,omitempty" protobuf:"bytes,4,rep,name=ports"`
}

source tree in master

Ah I see v0.25
type IngressStatus struct {
	// LoadBalancer contains the current status of the load-balancer.
	// +optional
	LoadBalancer v1.LoadBalancerStatus `json:"loadBalancer,omitempty" protobuf:"bytes,1,opt,name=loadBalancer"`
}

and v0.26
type IngressLoadBalancerStatus struct {
	// Ingress is a list containing ingress points for the load-balancer.
	// +optional
	Ingress []IngressLoadBalancerIngress `json:"ingress,omitempty" protobuf:"bytes,1,rep,name=ingress"`
}

it is explained in the PR https://github.com/kubernetes/kubernetes/pull/106242
Ingress and Loadbalancer used the same fields until 1.26, but the one got new fields that does not apply to the other

That is correct - the shape of the struct determines the API, not the Go struct type names (they are not part of the public API).

@smarterclayton @aojea The attributes in this structure are the same, why not continue the design before 1.26, and use a public structure to return, which is more conducive to upper-level calls, isn’t it more reasonable?

If each type returns its own internal structure, this increases the complexity of the upper-level call, and the same set of code needs to maintain three copies

@aojea I get each Ingress and do the same operation, and now it cannot be shared, which will cause my same implementation to be unable to call directly


[Observ] Mutilple PromSQL or metrics template support on one pannel

Supported in this commit https://github.com/kubegems/dashboard/commit/c56deafcdb9b2c0835c1f7aecd0f0e52c65bd887


Dummy commit to test CLA bot

Please ignore

So the bot is busted :(

Are you fixing the bot?

I don't know how, but we should investigate.


[BUG] Vehicle disappears in no clip

txAdmin/FXServer versions:
v4.11.0 atop FXServer 5181
Describe the bug
Vehicles disappear if you noclip while inside of it
To Reproduce
Steps to reproduce the behavior:

Spawn a vehicle and get inside
Toggle noclip on
Go around for some seconds (go far away from the place you toggled noclip)
Toggle noclip off
Vehicle disappeared and is buggy somewhere in the map (sometimes i can find it looking around)

Expected behavior
Vehicle not to disappear

Bug confirmed.
Appears only to happen when you move somewhat far from where the noclip originally happened.
@GoatG33k Can you maybe help us solve this?

I think this one is unfixable, unfortunately :(


missing parent, merotelic attachment

meroterically attached lagging mitotic chromosomes (FYPO:0004382)
should be a child of
merotelic kinetochore attachment during mitosis (FYPO:0004381)

there is a link:
id: FYPO:0004382
name: meroterically attached lagging mitotic chromosomes
relationship: has_part FYPO:0000228 ! lagging mitotic chromosomes
relationship: has_part FYPO:0004381 ! merotelic kinetochore attachment during mitosis

seems OK
https://www.pombase.org/term/FYPO:0004381


System.IO.FileNotFoundException after install via nuget

Exact same issue as #240
I happen to have the exact same issue... And I'm banging my head at it since several hours, without a shred of success... 😞
Error message
Basically, I got same message as @wowfood but in French:  Could not load file or assembly '...' or one of its dependencies. The system cannot find the file specified.
The message differs between version on the PublicKeyToken.
With version v1.1.0
System.Windows.Markup.XamlParseException : FileNotFoundException : 'Impossible de charger le fichier ou l'assembly 'GongSolutions.WPF.DragDrop, PublicKeyToken=null' ou une de ses dépendances. Le fichier spécifié est introuvable.'
With latest version v2.0.1
System.Windows.Markup.XamlParseException : FileNotFoundException : 'Impossible de charger le fichier ou l'assembly 'GongSolutions.WPF.DragDrop, PublicKeyToken=91f1945125b7a587' ou une de ses dépendances. Le fichier spécifié est introuvable.'
Environment

Windows 10 Pro 1809
Visual Studio 2017
Project : .NET Framework 4.5

XAML code sample
Don't know if it's relevant, but anyway.
I only followed the first part of the usage wiki page by adding dd:DragDrop.* to my ItemsControl.
<!--  Widgets  -->
<ItemsControl
	dd:DragDrop.IsDragSource="True"
	dd:DragDrop.IsDropTarget="True"
	ItemsSource="{Binding Path=Widgets}">
	<ItemsControl.ItemsPanel>
		<ItemsPanelTemplate>
			<WrapPanel IsItemsHost="True" />
		</ItemsPanelTemplate>
	</ItemsControl.ItemsPanel>
</ItemsControl>

What I tried

Full cleanup of solution, full re-regenerate
Deleting .suo solution file
Deleting packages solution folder
Trying version 1.1.0 and 2.0.1
Trying different xmlns (xmlns:dd="urn:gong-wpf-dragdrop" and xmlns:dd="clr-namespace:GongSolutions.Wpf.DragDrop;assembly=GongSolutions.Wpf.DragDrop" )

I'm out of idea... I need your help.
@wowfood can you be more precise with the "and all the other stuff"?
Thanks a lot.

Sorry I can't be much more precise as this was a long while back, and we dropped drag and drop as a requirement.
My "something isn't right" cleanup process though, is as follows
Clear VS cache.
  But this won't work if you don't have things stored in git.

Thanks for getting back 😄
After fiddling for a while, I managed to get it to work.
I followed the first part of this article to clean the VS cache. No luck, same issue 😞 . Then I tried the full reset. Same issue 😞 . Then I tried the nuking from orbit as you say (we use TFSVC but process is similar), and.... same issue with a clean repo 😞
Then I remembered that the project using WpfDragDrop is actually a library. The main application is in another project and which referenced the project library.
On a hunch, I added the GongSolutions.Wpf.DragDrop Nugget to the main project, compiled and run and... It works! 😄
So the main takeaway here is: if a library needs a Nugget, the main project needs it as well. Now I'll know...
Thanks a lot!

If you don't have control over the main project and can't add this as a dependency to it, You can try this.
https://stackoverflow.com/questions/1373100/how-to-add-folder-to-assembly-search-path-at-runtime-in-net


make courses page heading dynamic based on the active URL

Can you include the Services page as well as a new commit?

@billyjason  you mean the one we had before


Info storage

Export flag is part of https://github.com/googlei18n/fontmake/issues/20, but this addresses some other things as well.

@adrientetar @anthrotype @moyogo does anyone mind taking a look?

I’m not familiar with this part of the code.

Lgtm

Thanks!


feat(command): add shell completion support for fish

resolves #90

This is super awesome. Thanks so much @c4spar

You are welcome 😉


Remove console log printed when uploading a file to Glance

Response from the Glance API when uploading a file is empty (evaluated as an empty string in response) when the upload succeed.
Anyway, there should be not log printed on the standard output.

Good catch!  Thanks for jumping in and taking care of that.


chore(deps): update common-dev-assets digest to 63e86bc

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
35a1d9b -> 63e86bc

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

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


[Feature Request] Typed Search Attributes

see https://github.com/temporalio/features/issues/336

Sorry if this is an incorrect place to report this. But I have a bug recently when using tab stash. For some reason it breaks the very top line of pixil's on my firefox browser itself. The line above the tabs basically the top border of the program. I've isolated the behaviour to Tabstash. Very strange, just wanted to make you aware of the issue, and see if there is anything you might be able to think of that would be causing this behaviour. Otherwise, love the functionality.


test_conv_embed_db (ctest -> gtest)

Moving part of the conv_2d test to gtest.
Test is automatically picked up by gtest.

@alexandraBara BTW Is it really a draft or is it ready for review?

@JehandadKhan Hmm... Do we really want to move test_conv_embed_db (which should be run only when we embed databases) gtest?

@alexandraBara Please rename the title. This PR moves test_conv_embed_db.

@JehandadKhan Oops, I see now. But https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2168#discussion_r1222130686 remains still.
Please also look at Q at https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2168#issuecomment-1581458532

@JehandadKhan Oops, I see now. But #2168 (comment) remains still.
Please also look at Q at #2168 (comment)

@atamazov , I have updated test names as below. Please note no underscore is allowed in gTest names
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/2b656e53fd217526dab15e307f9e99c8dc045adb/test/gtest/conv_embed_db.cpp#L210

@JehandadKhan Hmm... Do we really want to move test_conv_embed_db (which should be run only when we embed databases) under the gtest's jurisdiction?

@atamazov , indeed this test should fail without embed database according to this line in
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/2b656e53fd217526dab15e307f9e99c8dc045adb/test/CMakeLists.txt#LL522C1-L522C102
This mechanism has been integrated here.
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/2b656e53fd217526dab15e307f9e99c8dc045adb/test/gtest/conv_embed_db.cpp#L75
Could you resolve this conversation if this has been resolved?

@JehandadKhan Hmm... Do we really want to move test_conv_embed_db (which should be run only when we embed databases) under the gtest's jurisdiction?

@atamazov , indeed this test should fail without embed database according to this line in
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/2b656e53fd217526dab15e307f9e99c8dc045adb/test/CMakeLists.txt#LL522C1-L522C102
This mechanism has been integrated here.
https://github.com/ROCmSoftwarePlatform/MIOpen/blob/2b656e53fd217526dab15e307f9e99c8dc045adb/test/gtest/conv_embed_db.cpp#L75
Could you resolve this conversation if this has been resolved?

@JehandadKhan Hmm... Do we really want to move test_conv_embed_db (which should be run only when we embed databases) under the gtest's jurisdiction?

@atamazov , indeed this test should fail without embed database according to this line in
(https://github.com/ROCmSoftwarePlatform/MIOpen/blob/2b656e53fd217526dab15e307f9e99c8dc045adb/test/CMakeLists.txt#LL522C1-L522C102)
This mechanism has been integrated here.
MIOpen/test/gtest/conv_embed_db.cpp
Line 75 in 2b656e5
EXPECT_FALSE(capture.find("Perf Db: record not found") != std::string::npos);
Could you resolve this conversation if this has been resolved?

Please also look at Q at #2168 (comment)

@atamazov I have replied below. Thanks

@xinlipn "[R]" means "Recommendation", "[Q]" is "Question".

@xinlipn Please resolve conflicts (no force-pushing please) and ping me when ready for the next review round (== you think that PR is ready for merging).

@xinlipn Please resolve conflicts (no force-pushing please) and ping me when ready for the next review round (== you think that PR is ready for merging).

@atamazov , CI is still running "Performance Tests - gfx90a", which should be a residual issue and has supposedly been disabled. I believe I have addressed your comments. Could you help review? Thanks

@xinlipn

CI is still running "Performance Tests - gfx90a", which should be a residual issue and has supposedly been disabled.

Maybe. We need a kind of approval from @junliume that this PR has passed CI tests.

@xinlipn
Please note the following comments:

https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2168#discussion_r1211964117
https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2168#discussion_r1211980597

These were hidden as resolved which is not actually so. Due to that I had do duplicate some review comments. Let's hide review comments after they explicitly marked [Resolved], if possible.
Please also provide an answer to https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2168#issuecomment-1602820706. Thank you!

@xinlipn BTW testing is not covered in the PR description. I means testing of the test itself, does it perform as expected.
Have you run this test with MIOPEN_LOG_LEVEL=5 and checked if the log matches your expectations?

Will upload

@xinlipn BTW testing is not covered in the PR description. I means testing of the test itself, does it perform as expected.
Have you run this test with MIOPEN_LOG_LEVEL=5 and checked if the log matches your expectations?

@atamazov , CTest and gTest cover the same test cases, after having it reviewed by JD, there are a few issues, e.g. warning message that test_drive was called more than once. Have been working on them...

Almost done. Two things left:

https://github.com/ROCmSoftwarePlatform/MIOpen/pull/2168#discussion_r1238661871
resolve merge conflicts

@xinlipn BTW testing is not covered in the PR description. I means testing of the test itself, does it perform as expected.
Have you run this test with MIOPEN_LOG_LEVEL=5 and checked if the log matches your expectations?

@atamazov , there was some discrepancies in terms of initiated solvers for test coverage between develop branch and this branch, e.g.   Forward convolution: ConvAsmImplicitGemmV4R1DynamicFwd_1x1 in Develop vs ConvHipImplicitGemmV4R1Fwd in current branch for
Input tensor: 128, 512, 7, 7
Weights tensor: 2048, 512, 1, 1
Output tensor: 128, 2048, 7, 7
Took some time to remove the discrepancies by updated cmake flags.

Log from Develop branch:

devleop_make_test_conv_embed_db_stdout.log

Log from current branch

branch_ctest.log
Please note MIOPEN_LOG_LEVEL=5 has been enabled, but it has affected the gtest serial spew. I have been working on this, which may need a separate ticket.


[Request]Menu and others

A menu would be nice to put in for RPG's. Other RPG elements can be added such as a healthbar and a combat system like Legend of Zelda and Pokémon. Another thing that can be added is warp to a scene and warp back to the previous scene and go back to where you were. Thanks.

The warping back and forth can just be done with the 'Switch scene' command. It's the easiest way I think.
The pokemon combat system has been discussed in #41. Something like zelda's combat system and more in #33. and a proper in-game menu in my post #24.

I'd like to be able to use a variable to determine where 'switch scene' warped to- I think right now a specific scene has to be chosen in advance which makes switching to a menu map and then back to where you were standing difficult

You could create a "room number" variable, changing in every room. When you leave the menu, just check "room number" to switch to the correct room. The only problem are the players coordinates. If there would be a way to check x and y for the player, a menu would be no longer a problem.

@Igerow A method for checking an Actors position is already merged into the develop branch


Update block.html

I should have been careful before.

Closing this pull request because of no response in a meantime


docs: update the main page with new copy

Hello @nicks,
Please review the following commits I made in branch nicks/docsinde:
4da092bd83ac4156ae0ae61c733774a9ce7f40e5 (2020-06-05 17:52:48 -0400)
docs: update the main page with new copy
Code review reminders, by giving a LGTM you attest that:

Commits are adequately tested
Code is easy to understand and conforms to style guides
Incomplete code is marked with TODOs
Code is suitably instrumented with logging and metrics

this is just copied from the main github readme


[INFO] Some things to note by users.

Default serializer for Nullable types fallback to serializer of underlying type (e.g. int? to int, etc), except for DateTime. There is a related bug #116. I suggest to adjust behaviour serialization of DateTimeOffset to be identical with DateTime, right now they are different.

Default enum serializer relies on assemblies, generated by Reflection.Emit on every call of SerializationContext constructor, so SerializationContext better be reused. Creating it on per-request basis will give a huge performance problems. I do not know if SerializationContext thread-safe or not. I suggest caching of assemblies in default enum serializer.

Hope, it's useful.

Thank you for suggestions! As you say, DateTimeOffset serializer's behavior should be same as DateTime one. I will fix it. But I cannot understand well for second suggestion. Is "SerializationContext is designed as thread-safe" correct answer for it?

It was not a real suggestion. Yep, it's good that SerializationContext is thread-safe. Other problem is that if you have several instances of that context and use it for serializing of one enum type, each instance of default enum serializer will generate a dynamic assembly. Which can be a perfomance problem. So, it is better to reuse context.

Yes, as you said, reusing context is better obviously. It is free for users to choice them (it is reason why SerializerContext is implemented as thread-safe). In addition, SerializationContext is "context" of serialization and they have own serializer instances and settings by design.
So, what did you mean about? I think I do not understand your post well.

The first issue was fixed in 0.6.3 (sorry I wrote wrong commit log). Please check it.

Thank you. It's good.


Change QEMU Cortex M3 machine to more flexible one

Is this request related to a missing driver support for a particular hardware platform, SoC or board? Please describe.
Currently we are using ti_lm3s6965 as qemu_cortex_m3 but it seems it's not flexible for SRAM size.  For emulating Cortex M3 with QEMU, I believe most of users don't really care which board we are running but does care the fact that it's a Cortex M3 machine and is capable running users application in emulation mode.
qemu_cortex_m3 can't really support running network applications due to limited SRAM size.  With the current origin/main:
$ git describe
zephyr-v3.2.0-482-g2666702cd10
$ west build -t run -b qemu_cortex_m3 zephyr/samples/net/sockets/echo_server -- -DOVERLAY_CONFIG=overlay-qemu_cortex_m3_eth.conf
    :
    :
[291/302] Linking C executable zephyr/zephyr_pre0.elf
FAILED: zephyr/zephyr_pre0.elf zephyr/zephyr_pre0.map /home/yashi/src/zephyr-project/build/zephyr/zephyr_pre0.map
: && ccache /home/yashi/zephyr-sdk-0.15.1/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc  -gdwarf-4 zephyr/CMakeFiles/zephyr_pre0.dir/misc/empty_file.c.obj -o zephyr/zephyr_pre0.elf  zephyr/CMakeFiles/offsets.dir/./arch/arm/core/offsets/offsets.c.obj  -fuse-ld=bfd  -Wl,-T  zephyr/linker_zephyr_pre0.cmd  -Wl,-Map=/home/yashi/src/zephyr-project/build/zephyr/zephyr_pre0.map  -Wl,--whole-archive  app/libapp.a  zephyr/libzephyr.a  zephyr/arch/common/libarch__common.a  zephyr/arch/arch/arm/core/aarch32/libarch__arm__core__aarch32.a  zephyr/arch/arch/arm/core/aarch32/cortex_m/libarch__arm__core__aarch32__cortex_m.a  zephyr/lib/libc/minimal/liblib__libc__minimal.a  zephyr/soc/arm/ti_lm3s6965/libsoc__arm__ti_lm3s6965.a  zephyr/subsys/net/libsubsys__net.a  zephyr/subsys/net/l2/ethernet/libsubsys__net__l2__ethernet.a  zephyr/subsys/net/ip/libsubsys__net__ip.a  zephyr/subsys/net/lib/config/libsubsys__net__lib__config.a  zephyr/subsys/net/lib/conn_mgr/libsubsys__net__lib__conn_mgr.a  zephyr/subsys/random/libsubsys__random.a  zephyr/drivers/console/libdrivers__console.a  zephyr/drivers/serial/libdrivers__serial.a  zephyr/drivers/ethernet/libdrivers__ethernet.a  zephyr/drivers/timer/libdrivers__timer.a  modules/mbedtls/libmodules__mbedtls.a  -Wl,--no-whole-archive  zephyr/kernel/libkernel.a  -L"/home/yashi/zephyr-sdk-0.15.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/thumb/v7-m/nofp"  -L/home/yashi/src/zephyr-project/build/zephyr  -lgcc  zephyr/arch/common/libisr_tables.a  -no-pie  -mcpu=cortex-m3  -mthumb  -mabi=aapcs  -mfp16-format=ieee  -Wl,--gc-sections  -Wl,--build-id=none  -Wl,--sort-common=descending  -Wl,--sort-section=alignment  -Wl,-u,_OffsetAbsSyms  -Wl,-u,_ConfigAbsSyms  -nostdlib  -static  -Wl,-X  -Wl,-N  -Wl,--orphan-handling=warn && cd /home/yashi/src/zephyr-project/build/zephyr && /usr/bin/cmake -E echo
/home/yashi/zephyr-sdk-0.15.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.bfd: zephyr/zephyr_pre0.elf section `noinit' will not fit in region `RAM'
/home/yashi/zephyr-sdk-0.15.1/arm-zephyr-eabi/bin/../lib/gcc/arm-zephyr-eabi/12.1.0/../../../../arm-zephyr-eabi/bin/ld.bfd: region `RAM' overflowed by 18208 bytes
collect2: error: ld returned 1 exit status
ninja: build stopped: subcommand failed.
FATAL ERROR: command exited with status 1: /usr/bin/cmake --build /home/yashi/src/zephyr-project/build --target run

What do you think if I propose changing to another board with much bigger SRAM size or flexible with CONFIG_SRAM_SIZE or DT.
Describe why you are asking for this support?
I'd like qemu_cortex_m3 to be more flexible machine so that we can all use it with our own requirements.

FWIW, we already have mps2_an385, which is a Cortex-M3 board that runs on QEMU with 4MiB "flash" and RAM.

Indeed, the following command just works with zeth described at https://docs.zephyrproject.org/3.2.0/connectivity/networking/qemu_eth_setup.html
$ west build -t run -b mps2_an385 zephyr/samples/net/sockets/echo_server -- -DOVERLAY_CONFIG=overlay-smsc911x.conf
-- west build: generating a build system
Loading Zephyr default modules (Zephyr base).
-- Application: /home/yashi/src/zephyr-project/zephyr/samples/net/sockets/echo_server
-- Found Python3: /usr/bin/python3.10 (found suitable exact version "3.10.8") found components: Interpreter
-- Cache files will be written to: /home/yashi/.cache/zephyr
-- Zephyr version: 3.2.99 (/home/yashi/src/zephyr-project/zephyr)
-- Found west (found suitable version "0.14.0", minimum required is "0.7.1")
-- Board: mps2_an385
-- ZEPHYR_TOOLCHAIN_VARIANT not set, trying to locate Zephyr SDK
-- Found host-tools: zephyr 0.15.1 (/home/yashi/zephyr-sdk-0.15.1)
-- Found toolchain: zephyr 0.15.1 (/home/yashi/zephyr-sdk-0.15.1)
-- Found Dtc: /usr/bin/dtc (found suitable version "1.6.1", minimum required is "1.4.6")
-- Found BOARD.dts: /home/yashi/src/zephyr-project/zephyr/boards/arm/mps2_an385/mps2_an385.dts
-- Generated zephyr.dts: /home/yashi/src/zephyr-project/build/zephyr/zephyr.dts
-- Generated devicetree_generated.h: /home/yashi/src/zephyr-project/build/zephyr/include/generated/devicetree_generated.h
-- Including generated dts.cmake file: /home/yashi/src/zephyr-project/build/zephyr/dts.cmake

warning: QEMU_ICOUNT_SHIFT (defined at boards/Kconfig:67) was assigned the value '7' but got the
value ''. Check these unsatisfied dependencies: QEMU_ICOUNT (=n). See
http://docs.zephyrproject.org/latest/kconfig.html#CONFIG_QEMU_ICOUNT_SHIFT and/or look up
QEMU_ICOUNT_SHIFT in the menuconfig/guiconfig interface. The Application Development Primer, Setting
Configuration Values, and Kconfig - Tips and Best Practices sections of the manual might be helpful
too.

Parsing /home/yashi/src/zephyr-project/zephyr/samples/net/sockets/echo_server/Kconfig
Loaded configuration '/home/yashi/src/zephyr-project/zephyr/boards/arm/mps2_an385/mps2_an385_defconfig'
Merged configuration '/home/yashi/src/zephyr-project/zephyr/samples/net/sockets/echo_server/prj.conf'
Merged configuration '/home/yashi/src/zephyr-project/zephyr/samples/net/sockets/echo_server/overlay-smsc911x.conf'
Configuration saved to '/home/yashi/src/zephyr-project/build/zephyr/.config'
Kconfig header saved to '/home/yashi/src/zephyr-project/build/zephyr/include/generated/autoconf.h'
-- The C compiler identification is GNU 12.1.0
-- The CXX compiler identification is GNU 12.1.0
-- The ASM compiler identification is GNU
-- Found assembler: /home/yashi/zephyr-sdk-0.15.1/arm-zephyr-eabi/bin/arm-zephyr-eabi-gcc
CMake Warning at /home/yashi/src/zephyr-project/zephyr/subsys/random/CMakeLists.txt:11 (message):

      Warning: CONFIG_TEST_RANDOM_GENERATOR is not a truly random generator.
      This capability is not secure and it is provided for testing purposes only.
      Use it carefully.

CMake Warning at /home/yashi/src/zephyr-project/zephyr/CMakeLists.txt:809 (message):
  No SOURCES given to Zephyr library: drivers__net

  Excluding target from build.

-- Configuring done
-- Generating done
-- Build files have been written to: /home/yashi/src/zephyr-project/build
-- west build: running target run
[1/309] Preparing syscall dependency handling

[8/309] Generating include/generated/version.h
-- Zephyr version: 3.2.99 (/home/yashi/src/zephyr-project/zephyr), build: zephyr-v3.2.0-482-g2666702cd105
[298/309] Linking C executable zephyr/zephyr_pre0.elf

[302/309] Linking C executable zephyr/zephyr_pre1.elf

[308/309] Linking C executable zephyr/zephyr.elf
Memory region         Used Size  Region Size  %age Used
           FLASH:      150640 B         4 MB      3.59%
             RAM:       85200 B         4 MB      2.03%
        IDT_LIST:          0 GB         2 KB      0.00%
[308/309] To exit from QEMU enter: 'CTRL+a, x'[QEMU] CPU: cortex-m3

uart:~$ *** Booting Zephyr OS build zephyr-v3.2.0-482-g2666702cd105  ***
[00:00:04.340,000] <err> eth_smsc911x: net_recv_data: -22
[00:00:04.350,000] <inf> net_config: Initializing network
[00:00:04.350,000] <inf> net_config: IPv4 address: <IP_ADDRESS>
[00:00:04.460,000] <inf> net_config: IPv6 address: 2001:db8::1
[00:00:04.460,000] <inf> net_config: IPv6 address: 2001:db8::1
[00:00:04.460,000] <inf> net_echo_server_sample: Run echo server
[00:00:04.460,000] <inf> net_echo_server_sample: Network connected
[00:00:04.460,000] <inf> net_echo_server_sample: Starting...
[00:00:04.460,000] <inf> net_echo_server_sample: Waiting for TCP connection on port 4242 (IPv6)...
[00:00:04.460,000] <inf> net_echo_server_sample: Waiting for TCP connection on port 4242 (IPv4)...
[00:00:04.460,000] <inf> net_echo_server_sample: Waiting for UDP packets on port 4242 (IPv6)...
[00:00:04.460,000] <inf> net_echo_server_sample: Waiting for UDP packets on port 4242 (IPv4)...
[00:01:29.870,000] <dbg> net_echo_server_sample: process_udp: (udp4): UDP (IPv4): Received and replied with 1 bytes
[00:01:29.870,000] <dbg> net_echo_server_sample: process_udp: (udp4): UDP (IPv4): Received and replied with 6 bytes
[00:01:29.870,000] <dbg> net_echo_server_sample: process_udp: (udp4): UDP (IPv4): Received and replied with 4 bytes
[00:01:29.870,000] <dbg> net_echo_server_sample: process_udp: (udp4): UDP (IPv4): Received and replied with 26 bytes
[00:01:29.870,000] <dbg> net_echo_server_sample: process_udp: (udp4): UDP (IPv4): Received and replied with 1280 bytes
[00:01:29.870,000] <dbg> net_echo_server_sample: process_udp: (udp4): UDP (IPv4): Received and replied with 1 bytes
[00:01:29.870,000] <dbg> net_echo_server_sample: process_udp: (udp4): UDP (IPv4): Received and replied with 256 bytes
uart:~$

based on the comments above, seems to be addressed already.


ERROR The function passed to Apify.main() threw an exception: Error: spawn ps ENOENT

Hi, I have a problem running the spider. I also tried the basic https://sdk.apify.com/docs/examples/basic-crawler (new Apify.BasicCrawler) and puppeteer https://sdk.apify.com/docs/examples/puppeteer-crawler (new Apify.PuppeteerCrawler). None works. If I try await Apify.launchPuppeteer it works.
Apify running inside Docker container.
INFO  System info {"apifyVersion":"0.21.1","apifyClientVersion":"0.6.0","osType":"Linux","nodeVersion":"v12.18.2"}
WARN  Neither APIFY_LOCAL_STORAGE_DIR nor APIFY_TOKEN environment variable is set, defaulting to APIFY_LOCAL_STORAGE_DIR="/home/node/app/apify_storage"
INFO  PuppeteerCrawler: Final request statistics: {"avgDurationMillis":null,"perMinute":0,"finished":0,"failed":0,"retryHistogram":[]}
ERROR The function passed to Apify.main() threw an exception:
  Error: spawn ps ENOENT
      at Process.ChildProcess._handle.onexit (internal/child_process.js:267:19)
      at onErrorNT (internal/child_process.js:469:16)
      at processTicksAndRejections (internal/process/task_queues.js:84:21)

Hi, apparently you're running a very small docker image that does not include the ps program. You can use one of our images that come preinstalled with everything that's needed. You can visit the repo to see their source.
Small image that does not include Chrome browser. Good for use with CheerioCrawler.
FROM apify/actor-node-basic

Image with Chrome, to be used with PuppeteerCrawler and headless: true
FROM apify/actor-node-chrome

Image with XVFB for use with a headful browser (headless: false).
FROM apify/actor-node-chrome-xvfb

My Dockerfile. Chrome installed. Puppeteer works well, but without crawler wrapper.
FROM node:12-slim

ARG project_root=.

RUN apt-get update

RUN apt-get update \
    && apt-get install -y wget gnupg \
    && wget -q -O - https://dl-ssl.google.com/linux/linux_signing_key.pub | apt-key add - \
    && sh -c 'echo "deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main" >> /etc/apt/sources.list.d/google.list' \
    && apt-get update \
    && apt-get install -y google-chrome-unstable fonts-ipafont-gothic fonts-wqy-zenhei fonts-thai-tlwg fonts-kacst fonts-freefont-ttf libxss1 \
      --no-install-recommends \
    && rm -rf /var/lib/apt/lists/*

# for https
RUN apt-get install -yyq ca-certificates

# install libraries
RUN apt-get install -yyq libasound2 libatk1.0-0 libc6 libcairo2 libcups2 libdbus-1-3 libexpat1 libfontconfig1 libgcc1 libgdk-pixbuf2.0-0 libglib2.0-0 libgtk-3-0 libnspr4 libnss3 libpango-1.0-0 libpangocairo-1.0-0 libstdc++6 libx11-6 libx11-xcb1 libxcb1 libxcomposite1 libxcursor1 libxdamage1 libxext6 libxfixes3 libxi6 libxrandr2 libxrender1 libxss1 libxtst6

# tools
RUN apt-get install -yyq wget xdg-utils

# and fonts
RUN apt-get install -yyq fonts-liberation

USER node

RUN mkdir -p /home/node/app && \
	chown -R node:node /home/node/app && \
	mkdir /home/node/app/node_modules && \
	chown -R node:node /home/node/app/node_modules && \
	mkdir /home/node/.npm-global && \
	chown -R node:node /home/node/.npm-global

ENV PATH=/home/node/.npm-global/bin:$PATH
ENV NPM_CONFIG_PREFIX=/home/node/.npm-global

WORKDIR /home/node/app

COPY ${project_root}/browserless-rest-api /home/node/app

RUN npm install --quiet --no-progress --global npm@latest
RUN npm install --quiet --no-progress --global nodemon
RUN npm install --quiet --no-progress --global

COPY --chown=node:node . .

EXPOSE 8080

CMD ["nodemon", "--legacy-watch", "server.js"]

I'm not sure why Crawler would not work. Could you provide more details?
Regarding the browserWSEndpoint. Yes, it will work. You'll need to provide a Custom launchPuppeteerFunction and use puppeteer.connect() there and return its return value (the Browser instance) from the launchPuppeteerFunction

Hi, thanks for reply. I have another problem now. If I run the following script for the first time, it's fine. If I run the script again, no page is scraped.
Script:
const Apify = require('apify');

Apify.main(async () => {
    const sources = [
        'https://apify.com/store?category=TRAVEL',
        'https://apify.com/store?category=ECOMMERCE',
        'https://apify.com/store?category=ENTERTAINMENT',
    ];

    const requestList = await Apify.openRequestList('categories', sources);
    const requestQueue = await Apify.openRequestQueue();

    const crawler = new Apify.CheerioCrawler({
        maxRequestsPerCrawl: 50,
        requestList,
        requestQueue,
        handlePageFunction: async ({ $, request }) => {
            console.log(`Processing ${request.url}`);

            // This is our new scraping logic.
            if (request.userData.detailPage) {
                const urlArr = request.url.split('/').slice(-2);

                const results = {
                    url: request.url,
                    uniqueIdentifier: urlArr.join('/'),
                    owner: urlArr[0],
                    title: $('header h1').text(),
                    description: $('header p[class^=Text__Paragraph]').text(),
                    lastRunDate: new Date(
                        Number(
                            $('time')
                                .eq(1)
                                .attr('datetime'),
                        ),
                    ),
                    runCount: Number(
                        $('ul.stats li:nth-of-type(3)')
                            .text()
                            .match(/\d+/)[0],
                    ),
                };
                console.log('RESULTS', results);
            }

            // Only enqueue new links from the category pages.
            if (!request.userData.detailPage) {
                await Apify.utils.enqueueLinks({
                    $,
                    requestQueue,
                    selector: 'div.item > a',
                    baseUrl: request.loadedUrl,
                    transformRequestFunction: req => {
                        req.userData.detailPage = true;
                        return req;
                    },
                });
            }
        },
    });

    await crawler.run();
});

Result of repeated code execution:
INFO  System info {"apifyVersion":"0.21.3","apifyClientVersion":"0.6.0","osType":"Linux","nodeVersion":"v12.18.2"}
WARN  Neither APIFY_LOCAL_STORAGE_DIR nor APIFY_TOKEN environment variable is set, defaulting to APIFY_LOCAL_STORAGE_DIR="/home/node/app/apify_storage"
INFO  CheerioCrawler:AutoscaledPool:Snapshotter: Setting max memory of this run to 498 MB. Use the APIFY_MEMORY_MBYTES environment variable to override it.
INFO  CheerioCrawler:AutoscaledPool: state {"currentConcurrency":0,"desiredConcurrency":2,"systemStatus":{"isSystemIdle":true,"memInfo":{"isOverloaded":false,"limitRatio":0.2,"actualRatio":null},"eventLoopInfo":{"isOverloaded":false,"limitRatio":0.7,"actualRatio":null},"cpuInfo":{"isOverloaded":false,"limitRatio":0.4,"actualRatio":null},"clientInfo":{"isOverloaded":false,"limitRatio":0.3,"actualRatio":null}}}
INFO  CheerioCrawler: All the requests from request list and/or request queue have been processed, the crawler will shut down.
INFO  CheerioCrawler: Final request statistics: {"avgDurationMillis":null,"perMinute":0,"finished":0,"failed":0,"retryHistogram":[]}

Same behavior for PuppeteerCrawler.

And another errors.
INFO  Launching Puppeteer {"args":["--no-sandbox","--user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.89 Safari/537.36"],"timeout":15000,"headless":false,"defaultViewport":{"width":1366,"height":768}}
ERROR PuppeteerCrawler:PuppeteerPool: Browser launch failed {"id":2}
  Error: Failed to launch the browser process!
  Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
  [1224:1224:0727/204459.484649:ERROR:browser_main_loop.cc(1469)] Unable to open X display.
  [0727/204459.492981:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
  Most likely you need to configure your SUID sandbox correctly
  [0727/204459.493089:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
  Most likely you need to configure your SUID sandbox correctly

  TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

      at onClose (/home/node/app/node_modules/apify/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
      at Interface.<anonymous> (/home/node/app/node_modules/apify/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:183:68)
      at Interface.emit (events.js:327:22)
      at Interface.close (readline.js:416:8)
      at Socket.onend (readline.js:194:10)
      at Socket.emit (events.js:327:22)
      at endReadableNT (_stream_readable.js:1221:12)
      at processTicksAndRejections (internal/process/task_queues.js:84:21)
ERROR PuppeteerCrawler: handleRequestFunction failed, reclaiming failed request back to the list or queue {"url":"https://www.google-analytics.com","retryCount":3}
  Error: Failed to launch the browser process!
  Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
  [1224:1224:0727/204459.484649:ERROR:browser_main_loop.cc(1469)] Unable to open X display.
  [0727/204459.492981:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
  Most likely you need to configure your SUID sandbox correctly
  [0727/204459.493089:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
  Most likely you need to configure your SUID sandbox correctly

  TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

      at onClose (/home/node/app/node_modules/apify/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
      at Interface.<anonymous> (/home/node/app/node_modules/apify/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:183:68)
      at Interface.emit (events.js:327:22)
      at Interface.close (readline.js:416:8)
      at Socket.onend (readline.js:194:10)
      at Socket.emit (events.js:327:22)
      at endReadableNT (_stream_readable.js:1221:12)
      at processTicksAndRejections (internal/process/task_queues.js:84:21)

and
INFO  Launching Puppeteer {"args":["--no-sandbox","--user-agent=Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/84.0.4147.89 Safari/537.36"],"timeout":15000,"headless":false,"defaultViewport":{"width":1366,"height":768}}
ERROR PuppeteerCrawler:PuppeteerPool: Browser launch failed {"id":3}
  Error: Failed to launch the browser process!
  Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
  [1795:1795:0727/204613.818868:ERROR:browser_main_loop.cc(1469)] Unable to open X display.

  TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

      at onClose (/home/node/app/node_modules/apify/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
      at ChildProcess.<anonymous> (/home/node/app/node_modules/apify/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:184:79)
      at ChildProcess.emit (events.js:327:22)
      at Process.ChildProcess._handle.onexit (internal/child_process.js:275:12)
Request https://news.ycombinator.com/ failed too many times
INFO  PuppeteerCrawler: All the requests from request list and/or request queue have been processed, the crawler will shut down.
INFO  PuppeteerCrawler: Final request statistics: {"avgDurationMillis":null,"perMinute":0,"finished":0,"failed":1,"retryHistogram":[null,null,null,1]}
ERROR PuppeteerCrawler:PuppeteerPool: Cannot close the browsers.
  Error: Failed to launch the browser process!
  Fontconfig warning: "/etc/fonts/fonts.conf", line 100: unknown element "blank"
  [1756:1756:0727/204613.506537:ERROR:browser_main_loop.cc(1469)] Unable to open X display.
  [0727/204613.517190:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
  Most likely you need to configure your SUID sandbox correctly
  [0727/204613.517401:ERROR:nacl_helper_linux.cc(308)] NaCl helper process running without a sandbox!
  Most likely you need to configure your SUID sandbox correctly

  TROUBLESHOOTING: https://github.com/puppeteer/puppeteer/blob/main/docs/troubleshooting.md

      at onClose (/home/node/app/node_modules/apify/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:193:20)
      at Interface.<anonymous> (/home/node/app/node_modules/apify/node_modules/puppeteer/lib/cjs/puppeteer/node/BrowserRunner.js:183:68)
      at Interface.emit (events.js:327:22)
      at Interface.close (readline.js:416:8)
      at Socket.onend (readline.js:194:10)
      at Socket.emit (events.js:327:22)
      at endReadableNT (_stream_readable.js:1221:12)
      at processTicksAndRejections (internal/process/task_queues.js:84:21)
Crawler finished.

See the getting started. You need to run it with
apify run -p

or delete the contents of ./apify_storage after each run.
Regarding the Puppeteer errors, please see the TROUBLESHOOTING link provided in the error messages or use one of the pre-configured docker images I linked above. This looks like your Dockerfile does not include all the necessary libraries and that's not an issue with Apify.

Thanks, I will try it.

I'll close this since there's no bug. Feel free to continue conversation, if you have any more issues with running the SDK.


Allow user to specify service annotation on Spark UI service

Currently, there's no way to specify annotations on Spark UI services. One example of how this can be useful, is that we can add annotation on Spark UI services such that it can be ignored by Istio Pilot.

@googlebot I signed it!

@googlebot I consent.

Please bump up the chart version and resolve the conflict.

Updated to 1.1.3, conflict resolved.


keepassxc can't load libbotan-2.so.19

Describe the bug
keepassxc stopped working recently (I'm currently running a bisect)
Steps To Reproduce

install keepassxc
run keepassxc or keepassxc-cli
it fails about a botan lib error

I'm not sure, but it may seem to work if you had a previously working keepassxc and the lib, so it's better to use the nixos test with the VM. 🤷♀
Expected behavior
keepassxc shouldn't crash
Screenshots
nix-build nixos/tests/keepassxc.nix output
subtest: Can create database and entry with CLI
machine: must succeed: su - alice -c 'keepassxc-cli db-create -k foo.keyfile foo.kdbx' >&2 &
(finished: must succeed: su - alice -c 'keepassxc-cli db-create -k foo.keyfile foo.kdbx' >&2 &, in 0.06 seconds)
machine: must succeed: su - alice -c 'keepassxc-cli add --no-password -k foo.keyfile foo.kdbx bar' >&2 &
machine # [   17.497271] su[985]: Successful su for alice by root
machine # [   17.504461] su[985]: pam_unix(su:session): session opened for user alice(uid=1000) by (uid=0)
(finished: must succeed: su - alice -c 'keepassxc-cli add --no-password -k foo.keyfile foo.kdbx bar' >&2 &, in 0.08 seconds)
(finished: subtest: Can create database and entry with CLI, in 0.13 seconds)
subtest: Ensure KeePassXC starts
machine: must succeed: su - alice -c 'keepassxc >&2 &' >&2 &
machine # [   17.570614] su[990]: Successful su for alice by root
machine # [   17.594655] su[990]: pam_unix(su:session): session opened for user alice(uid=1000) by (uid=0)
(finished: must succeed: su - alice -c 'keepassxc >&2 &' >&2 &, in 0.14 seconds)
machine: waiting for KeePassXC 2.7.1 to appear on screen
machine: sending monitor command: screendump /build/tmplsy6fqtu/ppm
machine: waiting for monitor prompt
(finished: waiting for monitor prompt, in 0.01 seconds)
(finished: sending monitor command: screendump /build/tmplsy6fqtu/ppm, in 0.01 seconds)
machine # [   17.735390] su[995]: Successful su for alice by root
machine # [   17.760768] su[995]: pam_unix(su:session): session opened for user alice(uid=1000) by (uid=0)
machine # [   17.840780] su[995]: pam_unix(su:session): session closed for user alice
machine # /run/current-system/sw/bin/keepassxc-cli: error while loading shared libraries: libbotan-2.so.19: cannot open shared object file: No such file or directory
machine # /run/current-system/sw/bin/keepassxc-cli: error while loading shared libraries: libbotan-2.so.19: cannot open shared object file: No such file or directory
machine # /run/current-system/sw/bin/keepassxc: error while loading shared libraries: libbotan-2.so.19: cannot open shared object file: No such file or directory
machine # [   18.072553] su[990]: pam_unix(su:session): session closed for user alice
machine # [   18.073625] su[985]: pam_unix(su:session): session closed for user alice
machine: sending monitor command: screendump /build/tmpvs927j3q/ppm
machine: waiting for monitor prompt
(finished: waiting for monitor prompt, in 0.01 seconds)
(finished: sending monitor command: screendump /build/tmpvs927j3q/ppm, in 0.01 seconds)

Notify maintainers
@jonafato @turion
Metadata
 - system: `"x86_64-linux"`
 - host os: `Linux 5.19.1-xanmod1, NixOS, 22.11 (Raccoon), 22.11.20220918.f677051`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.11.0`
 - channels(root): `""`
 - nixpkgs: `/nix/store/iw3xi0bfszikb0dmyywp7pm590jvbqvs-source`

Did it still work in https://github.com/NixOS/nixpkgs/pull/188104? It's a shame we can't see the result of an ofborg run in merged PRs...

I have a different error :thinking:
kill vlan (pid 5)
error: builder for '/nix/store/5dkgxpj719gcwkxpk8wqf1y7sby7bz3f-vm-test-run-keepassxc.drv' failed with exit code 1;
       last 10 log lines:
       > machine # [   38.389177] traps: .keepassxc-wrap[1019] trap int3 ip:7fe78c1b719f sp:7ffe8e7880d0 error:0 in libglib-2.0.so.0.7200.3[7fe78c179000+8c000]
       > (finished: must succeed: sleep 5, in 5.08 seconds)
       > machine: must succeed: ps -e | grep keepassxc
       > machine: output:
       > Test "Can open existing database" failed with error: "command `ps -e | grep keepassxc` failed (exit code 1)"
       > cleanup
       > kill machine (pid 6)
       > machine # qemu-kvm: terminating on signal 15 from pid 4 (/nix/store/xf1k5k05vg3zn7dfcpfh1qa7ga48hi3m-python3-3.10.6/bin/python3.10)
       > (finished: cleanup, in 0.04 seconds)
       > kill vlan (pid 5)
       For full logs, run 'nix log /nix/store/5dkgxpj719gcwkxpk8wqf1y7sby7bz3f-vm-test-run-keepassxc.drv'.

but in #188104 the binary was still working

It's working again.


Forms-customizer opens in a new TAB

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
[X] 💥 Microsoft Edge
[ ] 💥 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: Version 128.0.2739.42 (Offizielles Build) (64-Bit)
SPFx version 1.19.0 & also in 1.18.2
Node.js version: 18.19.0

Describe the bug / error
Today, suddenly creating a new list item in a custom list, opens the Form in a new Browser-TAB which will not close after saving.
It was working today morning!
We have several Applications in production, running with Forms-Customizer which do not work now.
It looks like it has to do with the new List-Design. Forms-Customizer running in the old Design are working and do not open in a new TAB.
Hopefully, you can fix that quickly.
Steps to reproduce

Create a Forms-Customizer (SPFX)
Attach the Customizer with PS
Create a new list-Item

Expected behavior
Should not open in a new TAB and can be saved.

Hi,
even Lists which had the old List-Design are having now (since today morning) the new Design and the Forms-Customizer are not working anymore! - but that is different for some users.
Please help, a lot of our Applications and Processes stopped working because of this!

Hi, we face the same issue as of this morning in all our own and customer tenants (even in standard release!)
Also custom command bar actions for selected items are not loading. This is business critical in some of our solutions.
Can you please make sure to load the old modern UI again asap as long as the new one is not working properly?
Why do we have a first release option if you release not well tested stuff to production tenants directly?!
Thanks for fixing.
Kind regards
@VesaJuvonen

I opened a Ticket:<PHONE_NUMBER>000557 and have a discussion in some minutes. let's see what they say...

My Meeting with MS is over. They understand that this is critical and will discuss it in Development- and Global-Team today.
Hopefully they fix it, soon or even rollback the latest update. I will keep you informed.

Awesome, thanks @EA12

Same here. But funny story is that we reported the issue to MS a few weeks ago. For some users it showed UI from MS List. For those users workarounds mentioned in thread https://github.com/SharePoint/sp-dev-docs/issues/9514#issuecomment-2328680668 helped. But as of today those workarounds don't help and the issue has also become critical.
What I found, that if you change default form of the list to Power Apps, list will open in previous UI. But in our case this is not a real workaround.

I am still in discussion with MS. currently the issue is in discussion with 3rd level Agents. i provived all the details, screenshots and even recordings. They will come back to me, later that day....

Their answer: Issue is OOB for our support as it falls under developer support.
As we get no help here, I will open a ticket with Premier/Unified Support.
@VesaJuvonen : Can you help? - This is so frustrating...

Thanks Microsoft for rolling everything back. Please, in the future just roll out in first release tenants and give us the possibility to test and keep opening custom forms in the panel or the dialog.

Phew, that was really tiring again. No transparency whatsoever for roll-outs of this type, no feedback despite open tickets - Unfortunately, we have known this for years and that is what makes it so exhausting overall. I can also confirm that it is now working again. - Get well soon!

Rolling back the update helped to solve the issue

Thanks Microsoft for rolling everything back. Please, in the future just roll out in first release tenants and give us the possibility to test and keep opening custom forms in the panel or the dialog.

It was rollout in first release in March I think. People reported already issues that time. But looks like, there is something wrong at Microsoft, that thay didn't care about that.


Stop mscs on start

Hello, how to stop mscs to start on system starting (Ubuntu)

If you are using systemd, this should work:
sudo systemctl disable mscs.service


can not capture other fields value when update one field only

that filed should in where clause or in other places .Otherwise we can not update target by pk.

Hi,
What is your supplemental logging level ? If it is "all columns"  all fields of table is written to log redo  . Could you please check it out ?
Thanks.

the problem has been solved, Thanks.

Thank you.


[SPARK-42864][ML] Make IsotonicRegression.PointsAccumulator private

What changes were proposed in this pull request?
Make IsotonicRegression.PointsAccumulator private, which was introduced in https://github.com/apache/spark/commit/3d05c7e037eff79de8ef9f6231aca8340bcc65ef
Why are the changes needed?
PointsAccumulator is implementation details, should not be exposed
Does this PR introduce any user-facing change?
no
How was this patch tested?
existing UT

Merged to master.

branch-3.4 is handled via https://github.com/apache/spark/pull/40500 yesterday.

thanks for reivews


[AutoPR containerregistry/resource-manager] [Do not merge] Swagger and Examples for the new Scoped tokens feature of Azure Container registry

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/5543

This PR has been merged into https://github.com/Azure/azure-sdk-for-js/pull/3013


add configparer depends

Looks ok, why was this necessary?

This change:
https://github.com/wandb/client/pull/526
added a dependency on:
https://pypi.org/project/configparser/
since configparser is a python 3+ thing, this backports full configparser
capability to 2.7.  the six implementation was causing problems
On Sun, Sep 8, 2019 at 1:51 PM Chris Van Pelt<EMAIL_ADDRESS>wrote:

Looks ok, why was this necessary?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/wandb/client/pull/529?email_source=notifications&email_token=AAN7MP4LDYJKL7IPVN4MP6LQIVQU5A5CNFSM4IUUUG6KYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD6FZDNI#issuecomment-529240501,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAN7MPY7VZP5UYHGMTWDKC3QIVQU5ANCNFSM4IUUUG6A
.


fix(input): Revert "feat(input): allow clearing the input element (#177)"

This reverts commit 1af74972e04bd2746a3d397d2669385e079a8ca5.

What this PR does 📖

i was getting a BorrowMut error when sending a chat. i need to be more creative in figuring out how to clear the input box  :(

Which issue(s) this PR fixes 🔨

Resolve #

Special notes for reviewers 🗒
Additional comments 🎤

Didn't spot any new bugs while testing 👍


Upgrade xorm to v1.3.7 to fix a resource leak problem caused by Iterate

Mainly fix an error https://gitea.com/xorm/xorm/issues/2393

I was unable to create a backport for 1.21. @lunny, please send one manually. :tea:
go run ./contrib/backport 28891
...  // fix git conflicts if any
go run ./contrib/backport --continue


feat(atoms): add SfColor component

Related issue
Closes #590
Scope of work
Created button for filtering colors
Checklist

[ ] I followed composition rules for my component
[ ] I tested the component in most common device sizes (can be tested in Storybook from viewport addon in top menu)

@filrak Added lighter border, like on VSF theme

@aniamusial blocked, we should wait for the design


[Bug] Youtube Subscriptions page won't load

Hi, first of all, thanks so much for this extension, it's great!
Since a day or two my subscriptions feed won't load when this add-on is enabled.
I've disabled every other extension but Remove Youtube Shorts and it still won't load.
Enabling everything except Remove Youtube Shorts makes it work fine.
I don't see anything obvious in the console/network tab, although I don't know exactly what to look for.
I'm on firefox if that helps. If you need any more info, let me know!
Add-on info:

Version: 1.2
Last Updated: 14 May 2023

Sorry for any inconvenience caused. As I had used list view in subscription page for years, I forgot that there is grid view as well.
I have just uploaded a new version, trying to fix problems in grid view.
May you update the extension and test if it works?
And if you are using list view, and still encounter this problem, please let me know.


[Feature Request] COSMIC core image

Now this image does not include either system76-power or power-profile-daemon, once installed with rpm-ostree it just works (tested with ppd). It may be good to include ppd for now and perhaps a system76 image later with system76-power?

Following.


Make it easier to buy DEV

Scenario: I have a DEV badge in my repos. A user wants to support me by staking one of my projects. They know nothing about cryptocurrency. When they land on my asset pool page, they see a "Buy DEV" button. It just opens Uniswap. The user has no idea how to go from fiat USD to DEV. I think the "Buy DEV" button should open a modal that explains the situation better and give some options.
Is there any service that makes it super easy to buy ETH with fiat which we could recommend in such a modal?
The ideal scenario is that there a way to have some kind of automatic "user's USD => USD to ETH => Uniswap => DEV" flow.

I had been thinking of something like this as well. There are solutions that allow u to directly purchase ETH with your bank card such as https://www.moonpay.com/. I think @defi-er might have some opinions on this :)?

I am also considering this issue. Ideally, Stakes.social should use user-friendly APIs to get cryptocurrencies—for example, Moonpay. (However, the tedious KYC process still stands in front of a user)

I am also considering this issue. Ideally, Stakes.social should use user-friendly APIs to get cryptocurrencies—for example, Moonpay. (However, the tedious KYC process still stands in front of a user)

I'm pretty much the person you're talking about, knowing nothing. I figured out how to go from fiat to DEV, but now I want to stake it and have no idea how.

I'm pretty much the person you're talking about, knowing nothing. I figured out how to go from fiat to DEV, but now I want to stake it and have no idea how.

Please keep this open.


New resources for Web development according to Google

@raulgonzalezcz contribute here https://github.com/Ishaan28malik/Get-Dev-Resources


[Question] I want to use Mask3D features instead if ISBNET for dc_features computation

Hello,
Thanks again for the work,
I used Mask3D features to compute the dc_features; I was wondering which ones you used for the results reported in the paper (with mask3d): the 128-dimensional (mask feature) or the 96-dimensional (Backbone Point cloud features)?
Many thanks,
Mohamed

Hi @aminebdj ,
We extracted feature after the mask_features_head in Mask3D (here).
Best.

Hey @ngoductuanlhp,
Thanks for the clarification,
Best

Hey @ngoductuanlhp,
Thanks for the clarification,
Best

did you figure out how to extract Mask3D features?
for example. how to save the dc_features and cls_agnostic_3d_proposals in Mask3D like ISBNet below:
    if self.dataset_name == "scannet200":
        save_path = os.path.join(self.dc_200, scan_ids[0] + ".pth")
        # torch.save((voxel_mask_features[v2p_map.long()].cpu()), save_path)
    if self.dataset_name == "scannetpp":
        save_path = os.path.join(self.dc_pp, scan_ids[0] + ".pth")
    torch.save((voxel_mask_features[v2p_map.long()].cpu()), save_path)

    if self.dataset_name == "scannet200":
        saved_masks = [m["pred_mask"] for m in pred_instances]
        saved_confs = [m["conf"] for m in pred_instances]
        torch.save(
            {"ins": saved_masks, "conf": saved_confs},
            os.path.join(self.isbnt_200, scan_ids[0] + ".pth"),
        )
    if self.dataset_name == "scannetpp":
        saved_masks = [m["pred_mask"] for m in pred_instances]
        saved_confs = [m["conf"] for m in pred_instances]
        torch.save(
            {"ins": saved_masks, "conf": saved_confs},
            os.path.join(self.isbnt_pp, scan_ids[0] + ".pth"),
        )


cli: Add a message telling user to do 'quilt show' after 'quilt run'

Previously, after a successful 'quilt run', there would be no user
feedback. This commit adds a hint telling the user to use 'quilt show'
to check the status of their deployment.

@luise I've made the changes you requested


Ability to monkey patch libraries

Home Assistant release with the issue:
0.87.1
Last working Home Assistant release (if known):
N/A
Operating environment (Hass.io/Docker/Windows/etc.):
Raspbian 9.6/Linux campi 4.14.79-v7+
Also, via Docker
Component/platform:
Any
Description of problem:
Is there a way to monkey patch a library/libraries used by a component?
I have a specific request for async_upnp_client and wish to help this user with his use case, but don't want to introduce code for this (very) specific use case and also don't want to expose this behavior through home assistant (via configuration). Exposing this behavior will certainly confuse other users and result in more bug reports/questions for home assistant.
There are certainly problems with regard to upgrading of used versions and old patches, but I think it is fair to place this burden on the user who introduced the monkey patch. S/he will probably know what s/he is doing, since monkey patching already requires a lot of knowledge.

Tagging @balloob as suggested by @dgomes.

I believe this should be discussed in
https://github.com/home-assistant/architecture

/move
https://github.com/home-assistant/architecture

/move to architecture


how about the performance compare with CPU?

hi, how about the performance compare with CPU?
thank you!

I ran it on Apple M2 with the 13B foundational model, and the generation time of the first 100 tokens average out to be 699 ms/token. This is slower than llama.cpp since for example it doesn't have flash attention for now. If there is demand, I might tinker with it a bit more to potentially add it to the converter.

Another note: the LinearInt8 layer in the output model has only ARM NEON acceleration for now, so everything ran on the CPU.

Another note: the LinearInt8 layer in the output model has only ARM NEON acceleration for now, so everything ran on the CPU.

thank you for your reply, do you have any plan to write GPU instrinct for LinearInt8 layer?

I don't plan to write GPU code before I finish my current project.


STM32 IWDG watchdog is not started automatically

Describe the bug
When option CONFIG_WDT_DISABLE_AT_BOOT is not set, STM32 IWDG is not started during device init.
Since : https://github.com/zephyrproject-rtos/zephyr/commit/842a6ba02dfd95d0148491796b5b4b02785dc073, IWDG wathdog is not started in iwdg_stm32_install_timeout but in iwdg_stm32_setup.
The problem is only iwdg_stm32_install_timeout is called during watchdog device initialization. Thus watchdog is not started anymore.
To Reproduce
Using samples/drivers/watchdog sample code is enough to reproduce.
When entering main watchdog is still disabled
Expected behavior
Watchdog timer should be started during device driver initialization
Environment (please complete the following information):

OS: Linux
Zephyr SDK 0.16.3
main

thanks @vgeneves to report your observation
I understand from the https://docs.zephyrproject.org/latest/hardware/peripherals/watchdog.html  that "IWDG wathdog is not started in iwdg_stm32_install_timeout but in iwdg_stm32_setup." --> this as expected
The wdt_install_timeout function is for preparing a watchdog which is started after, by the wdt_setup()  (wdt_install_timeout is not supposed to star the watchdog)

Yes, my issue was not about that.
It is about WDT_DISABLE_AT_BOOT. From my understanding if WDT_DISABLE_AT_BOOT is disabled, watchdog should be configured with default timeout (CONFIG_IWDG_STM32_INITIAL_TIMEOUT) and started.
Actually the driver only configure the watchdog with wdt_install_timeout but it is not started.
Or maybe my understanding of WDT_DISABLE_AT_BOOT is wrong. Anyway the behavior of the iwdg changed since https://github.com/zephyrproject-rtos/zephyr/commit/842a6ba02dfd95d0148491796b5b4b02785dc073.

if WDT_DISABLE_AT_BOOT is set "Disable watchdog at Zephyr system startup."
so that if WDT_DISABLE_AT_BOOT is not set , as you say --> watchdog should be configured with default timeout (CONFIG_IWDG_STM32_INITIAL_TIMEOUT)  by  iwdg_stm32_install_timeout function and started by wdt_setup function
So this could be:
diff --git a/drivers/watchdog/wdt_iwdg_stm32.c b/drivers/watchdog/wdt_iwdg_stm32.c
index 2be891e9b59..012921f4837 100644
--- a/drivers/watchdog/wdt_iwdg_stm32.c
+++ b/drivers/watchdog/wdt_iwdg_stm32.c
@@ -192,8 +192,9 @@ static int iwdg_stm32_init(const struct device *dev)
 	struct wdt_timeout_cfg config = {
 		.window.max = CONFIG_IWDG_STM32_INITIAL_TIMEOUT
 	};
-
+	/* Watchdog should be configured and started by `wdt_setup`*/
 	iwdg_stm32_install_timeout(dev, &config);
+	iwdg_stm32_setup(dev, 0);
 #endif

 	/*

I tested it and it works for me.


removes start event from telemetry

Describe your changes
when recording telemetry events, we used to store a start and success/fail event. to reduce the number of events, we only trigger success/fail now.
the actual change is just a few lines of code, the rest are tests that had to be updated
once this is approved, I can make a new release
Issue number
Closes #X
Checklist before requesting a review

[ ] Performed a self-review of my code
[ ] Formatted my code with pkgmt format
[ ] Added tests (when necessary).
[ ] Added docstring documentation and update the changelog (when needed)

:books: Documentation preview :books:: https://ploomber-core--77.org.readthedocs.build/en/77/

merging this since I discussed with @idomic that removing the started event is acceptable


Handle empty data arrays for stacked-area

Description
Added handling for when data is an empty array
Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x ] My code follows the code style of this project.
[x ] My change requires a change to the documentation.
[x ] I have updated the documentation accordingly.
[x ] I have read the CONTRIBUTING document.
[ x] I have added tests to cover my changes.
[x ] All new and existing tests passed.

LGTM
Awesome! Thanks!


add no_std feature

this adds support for no_std applications/libraries (like microcontrollers) by using conditional features

rust-lang/cargo#633

On nightly with no_std:
#  rustup run nightly cargo test --features no_std                                                                                <<<
    Finished dev [unoptimized + debuginfo] target(s) in 0.0 secs
     Running target/debug/deps/crc-c3e90d0dfab413be

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured

     Running target/debug/deps/crc-9d7b680262789a74

running 10 tests
test crc32::checksum_castagnoli ... ok
test crc32::checksum_ieee ... ok
test crc32::digest_castagnoli ... ok
test crc32::checksum_koopman ... ok
test crc32::digest_ieee ... ok
test crc64::checksum_ecma ... ok
test crc32::digest_koopman ... ok
test crc64::digest_iso ... ok
test crc64::checksum_iso ... ok
test crc64::digest_ecma ... ok

test result: ok. 10 passed; 0 failed; 0 ignored; 0 measured

     Running target/debug/deps/hash-bb44b103cb920ad0

running 2 tests
test hasher::checksum_hashcrc32 ... ok
test hasher::checksum_hashcrc64 ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured

   Doc-tests crc

running 2 tests
test src/lib.rs -  (line 6) ... ok
test src/lib.rs -  (line 27) ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured

on stable with std:
# rustup run stable cargo test
   Compiling crc v1.4.0 (file:///home/garrett/projects/ruststuff/crc-rs)
    Finished dev [unoptimized + debuginfo] target(s) in 1.64 secs
     Running target/debug/deps/crc-57a43f894e443797

running 0 tests

test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured

     Running target/debug/deps/crc-79b2fcd023832a0c

running 10 tests
test crc32::checksum_castagnoli ... ok
test crc32::checksum_ieee ... ok
test crc32::checksum_koopman ... ok
test crc32::digest_castagnoli ... ok
test crc32::digest_ieee ... ok
test crc64::checksum_iso ... ok
test crc64::checksum_ecma ... ok
test crc64::digest_ecma ... ok
test crc32::digest_koopman ... ok
test crc64::digest_iso ... ok

test result: ok. 10 passed; 0 failed; 0 ignored; 0 measured

     Running target/debug/deps/hash-da1e5eadb26ad3bb

running 2 tests
test hasher::checksum_hashcrc32 ... ok
test hasher::checksum_hashcrc64 ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured

   Doc-tests crc

running 2 tests
test src/lib.rs -  (line 27) ... ok
test src/lib.rs -  (line 6) ... ok

test result: ok. 2 passed; 0 failed; 0 ignored; 0 measured
#

As a developer who deploys to embedded devices: I would not use a library that employs lazy_static. Not only there is no reason whatsoever to calculate CRC tables at runtime when you can simply include them in the source code--it's not like they ever change--or at least do it at compile-time, but on a real-time system this would easily cause a missed deadline by whichever code path calls the corresponding CRC function first.

Huh, I wasn't thinking about that. Two questions :

why is it not a table already? Can I open a PR for that?
it seems to me like rust should be able to have a build_static crate that can do const evaluations like this at build time (using build.rs). Do you have thoughts on that?

it seems to me like rust should be able to have a build_static crate that can do const evaluations like this at build time (using build.rs). Do you have thoughts on that?

I feel like this is unnecessary complexity and a simple accessory binary included in the source code for posterity and verification but never normally built is more than enough.

I created a crate for this purpose. I could definitely also make a
constructor that can be used for "scripts"!
https://github.com/vitiral/build_const

sent from my Android

On May 29, 2017 12:54 AM, "whitequark"<EMAIL_ADDRESS>wrote:

it seems to me like rust should be able to have a build_static crate that
can do const evaluations like this at build time (using build.rs). Do you
have thoughts on that?
I feel like this is unnecessary complexity and a simple accessory binary
included in the source code for posterity and verification but never
normally built is more than enough.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/mrhooray/crc-rs/pull/13#issuecomment-304586480, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AFVCyz4_TGd2BNEUX2Kk8C1obtVdoEy5ks5r-mu9gaJpZM4NoylW
.

just finished using build_const in the build.rs. I would say it is pretty simple -- but then again I am the developer of build_const.
If you would like I could put it in a script instead so the constant files could be generated whenever was convienient (build_const has helpers to make this transition seamless)

Fixes #11
Can this be merged? There is literally no benefit to lazy_static for this crate anymore.

Looks like the crate author hasn't been active on github or twitter for a few months now. Maybe creating a new crate with the improvements in the open PRs could be considered.

@mrhooray if you could give me rights on cargo I would gladly take over this repo! I totally understand that sometimes life gets hard 😄

@vitiral Would you be interested in making a fork of this crate and put it on crates.io to use until the author shows up? I can help out with it if needed.

@vitiral @oyvindln sorry for the late response and thanks @vitiral for integrating with his module to have build time constants
Not very familiar with build process, would this be a breaking change or it'd be fully compatible with v1?

@mrhooray it is not a breaking change, it just removes a dependency (and adds one) and allows for use in no_std libraries.


Icon settings

Please add the icon for the settings

this is currently cog in the outline folder
src/outline/general/cog.svg


Starport Elevator

Both the upper and lower starport elevators in new atlantis have stopped working.

Details
Both the upper and lower starport elevators in new atlantis have stopped working. This includes the main level and waterfall elevators. I have seen online that the same on in the well is not functioning however in my save it still works.
The doors still open for me in contrast to some who are having trouble with the doors working. In my case the touchpad the player interacts with to pick a floor is not selectable on both the starport and waterfall levels.
Game Version
1.7.36
New Game
No
Reproduction Steps
I am unsure of how i would even recreate this bug as it has not been working for a long time without my noticing. Reloading older saves on the broken character have the same issue, so I cannot tell at which point it stopped working.
Creating a new character fixes the issue, so I can at least assume it is a problem which may occur after some time of playing.

Can confirm this, doesn't work after doing the vanguard questline

Confirmed. Once the spaceport gets back to normal after the terrormorph attack in the vanguard quest line, the spaceport/well/waterfall elevator stops working from each location. One has to use the elevator in the MAST NAT station to get to the well and they have to boost jump up to the waterfall platform when that area is needed for Sarah’s companion quest.

Similar to https://www.starfieldpatch.dev/issues/839

Will use #839 as it has more specific details.


Changing blur amount

Hey! Love the module, a lot of people have been looking for something that can do exactly what this module aims at for a long time. I just had one question, the blur is good, but it doesn't match with the other windows 10 programs.
Here's an example between the application I'm making and the settings window.

Is it possible to change the amount of blur so it matches? maybe this has already been implemented and I can't see how to do it? Otherwise maybe this is a good option to try and add?

After looking at this issue, I found that there is a way to express the Blur effect more closely from RS4 to the Blur effect of the UWP app. Adding Acrylic Blur to your Windows 10 (Redstone 4) desktop apps
Originally, the AccentState of the SetWindowCompositionAttribute API was designated as ACCENT_ENABLE_BLURBEHIND, but from RS4 it is said that there is an option that is closer to the UWP app called ACCENT_ENABLE_ACRYLICBLURBEHIND. I didn't notice because it's an not documented API.
I will reflect this amendment in the next update. Thank you.

@Seo-Rii thanks for looking into it! Again, I appreciate this module so much! Looking forward to the update

Solved on https://github.com/Seo-Rii/electron-acrylic-window/commit/f1bdc9d1a7393a78d9b6b7acdda26ad975e5c06e.
Additionally, I added the option to choose the theme!
I'll publish it into npm after solving bug https://github.com/Seo-Rii/electron-acrylic-window/issues/3.

Thanks so much @Seo-Rii!

v0.3.0 now published. Now you can see the improvements!

@Seo-Rii Can I change blur amount of effect blur not acrylic? Acrylic is very slow.


*: Simplify join executor translation

What problem does this PR solve?
Issue Number: ref #5351
Problem Summary:
For detailed design consideration, please refer to #5351.
What is changed and how it works?

update join executor test API from ASTTableJoin::Kind to tipb::JoinType
update relevant tests accordingly

Check List
Tests

[x] Unit test
[ ] Integration test
[ ] Manual test (add detailed scripts or steps below)
[ ] No code

Side effects

[ ] Performance regression: Consumes more CPU
[ ] Performance regression: Consumes more Memory
[ ] Breaking backward compatibility

Documentation

[ ] Affects user behaviors
[ ] Contains syntax changes
[ ] Contains variable changes
[ ] Contains experimental features
[ ] Changes MySQL compatibility

Release note

None

/run-unit-test

/run-all-tests

/run-all-tests

/run-unit-test

/run-all-tests

/run-all-tests

/run-all-tests

/run-all-tests

/merge


Refactoring of base.jl, while splitting into types/base.jl and utils/base.jl

@Michele21 and I tidied up the AbstractModel interface, which now lives in types/base.jl together with LeafModel.
We enriched some docstrings (more content, added the missing ones, See also are now ordered, !!! note and !!! warning sections) but we still need to add # Examples section sometimes.
We also added some missing exports to SoleModels.jl.
Currently, we are working on src/utils/base.jl, where every AbstractModel implementation lives.
Our work is still not finished, for now we have come to do: ConstantModel, FunctionModel, Rule, Branch, DecisionList.

Tests should be fixed, though.
Il giorno ven 25 ott 2024 alle ore 18:42 Mauro Milella <
@.***> ha scritto:

@mauro-milella https://github.com/mauro-milella requested your review
on: #30 https://github.com/aclai-lab/SoleModels.jl/pull/30 Refactoring
of base.jl, while splitting into types/base.jl and utils/base.jl.
—
Reply to this email directly, view it on GitHub
https://github.com/aclai-lab/SoleModels.jl/pull/30#event-14879974290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AF3CJLLLSMJOTQGJK5OQAMLZ5JYHHAVCNFSM6AAAAABQTUTWQ2VHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUHA3TSOJXGQZDSMA
.
You are receiving this because your review was requested.Message ID:
@.***>

Hi Gio, thank you for the review.
I and @Michele21 are looking forward to implementing new tests and writing/reviewing the documentation related to all the AbstractModels.
Actually the purpose of this pull request had not yet been fully achieved, which is why we will continue in #32.