stored procedure

Is it possible to add a feature, for example, to execute stored procedures in the same way as PLSQL, by filling out tables and clicking execute.

Thank you for the feature request!

Hello @oneforever
Please provide more info about your request.
Examples will be helpful.
You can now choose the "Execute procedure" option in the navigator tree. And it will create a query with parameters. In the execution step, you need just replace these parameters, and the query will be executed.

It's been a while since no update here. If the issue is still actual please let me know and provide additional information.


refactor(consensus):

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#825  👈
#824
#795
#741
#740
#739
#738
#737
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @matan-starkware and the rest of your teammates on  Graphite


encounter connetion timeout

##here is the code
from daily import *
from PIL import Image
from openai import OpenAI
import argparse
import io
import os
import time
import wave
from base64 import b64decode
Daily.init()
CAMERA_WIDTH = 1024
CAMERA_HEIGHT = 1024
speaker = Daily.create_speaker_device(
"my-speaker", sample_rate=16000, channels=1)
camera = Daily.create_camera_device(
"my-camera",
width=CAMERA_WIDTH,
height=CAMERA_HEIGHT,
color_format="RGB")
Daily.select_speaker_device("my-speaker")
client = CallClient()
meetting="https://autoark.daily.co/XXXXX"
print()
print(f"Joining {"https://autoark.daily.co/XXXX"} ...")
client.join(meetting, client_settings={
"inputs": {
"camera": {
"isEnabled": True,
"settings": {
"deviceId": "my-camera"
}
},
"microphone": False
}
})
client.leave()
client.release()
##and the error
{"timestamp":"2024-07-19T06:19:04.006385Z","level":"ERROR","fields":{"message":"Failed to fetch room information: GET failed: Transport(Transport { kind: ConnectionFailed, message: Some("Connect error"), url: Some(Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("gs.daily.co")), port: None, path: "/rooms/check/autoark/1r4by424NvuhJS8hOpRF", query: None, fragment: None }), source: Some(Error { kind: TimedOut, message: "connection timed out" }) })"},"target":"daily_core::call_client"}
{"timestamp":"2024-07-19T06:19:04.006411Z","level":"ERROR","fields":{"message":"Failed to fetch room information: GET failed: Transport(Transport { kind: ConnectionFailed, message: Some("Connect error"), url: Some(Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("gs.daily.co")), port: None, path: "/rooms/check/autoark/1r4by424NvuhJS8hOpRF", query: None, fragment: None }), source: Some(Error { kind: TimedOut, message: "connection timed out" }) })"},"target":"daily_core::event"}
{"timestamp":"2024-07-19T06:19:04.007353Z","level":"ERROR","fields":{"message":"join (request 0) encountered an error: Connection(Api(RoomLookup(RoomInfoFetchFailed(Get(Transport(Transport { kind: ConnectionFailed, message: Some("Connect error"), url: Some(Url { scheme: "https", cannot_be_a_base: false, username: "", password: None, host: Some(Domain("gs.daily.co")), port: None, path: "/rooms/check/autoark/1r4by424NvuhJS8hOpRF", query: None, fragment: None }), source: Some(Error { kind: TimedOut, message: "connection timed out" }) }))))))"},"target":"daily_core::native::ffi::call_client"}
##envrionment
a clound server

Hi @linyubupa ! That looks like a network issue. Are you still running into this issue?

I'll be closing this since this seemed a temporary network issue. Please, feel free to re-open if you run into it again.


1 small line of code, 1 great leap in accuracy

What if we didn't ask about it...
damn

Haha cute title. Looks good to me.

thanks :)

Seriously, OMG.


Fix import order

Separated from #36368

/// <reference lib="es2015.promise" />
/// <reference lib="es2015.iterable" />

Note that the problem is that the order of overloads wrongly looks like
    race<T>(values: Iterable<T | PromiseLike<T>>): Promise<awaited T>;
    race<T>(values: readonly (T | PromiseLike<T>)[]): Promise<awaited T>;

from the current definition
/// <reference lib="es2015.generator" />
/// <reference lib="es2015.promise" />
/// <reference lib="es2015.iterable" />

but actually
    race<T>(values: readonly (T | PromiseLike<T>)[]): Promise<awaited T>;
    race<T>(values: Iterable<T | PromiseLike<T>>): Promise<awaited T>;

because es2015.generator loads es2015.iterable. This misleading confuses us.

This won't affect the resolution order, as the order is explicitly specified in commandLineParser.ts

This fix the definition order which doesn't match the resolution order.

The order they are specified in the lib files shouldn't matter in the slightest. The order they are loaded (and the order of the definitions) should come from the libEntries array in commandLineParser.ts. We did this explicitly so that it didn't matter what order you specify them in your "libs" or via /// <reference /> directives so that we would preserve the correct ordering of overloads.

The current definition order sometimes confuses us as I mentioned at https://github.com/microsoft/TypeScript/pull/37510#issuecomment-602545912. And as you said "This won't affect the resolution order", you have no reason to keep the current definition order which doesn't match the resolution order.

I think we need this for the playground to generate a reasonable lib.d.ts.
@typescript-bot pack this
@typescript-bot cherry-pick this to release-3.9 and LKG

I agree that this list should at least strive to match the one that we reorder automatically. Not doing so has caused issues. Maybe the list should start with a leading comment.

It definitely matters. Just annoying that I have to redo the VS-side syncing now.

Thanks @falsandtru!


Please add instructions for login in the first launch of power bi

Attendees are always confused when launching power bi for the first time as they get asked to log in. They always seem to log in with their personal email which they used for learnondemand.
Might I suggest adding instructions to log in with the email provided to them under the resources tab (maybe add a reference to click on it). Or you can ask them to cancel and add these instructions later on when they get to the publishing steps.

@dtarek1 thank you for the feedback.
We maintain these uniform exercise instructions for all modalities - self-paced and instructor-led.
In ILT courses, we value and rely on instructors to provide additional context and guidance to students.
Please let us know how we can support your deliveries without impacting the instructions for self-paced learners. Maybe this would be better suited for informational slides for instructors or the trainer prep guide.


Weak type detection for intersection types

TypeScript Version:  2.6.0-dev.20171018
Code
interface X { x: string }
interface Y { y: number }
interface Z { z?: boolean }

type XY = X & Y;
const xy: XY = {x: 'x', y: 10};

const z1: Z = xy;
// (1) compiles without any errors

const z2: Z = xy as Pick<XY, keyof XY>;
// (2) produces error: Type 'Pick<X & Y, "x" | "y">' has no properties in common with type 'Z'.

Expected behavior:
(1) should produce an error similar to (2) because there are no common properties for XY and Z types.
Actual behavior:
(1) compiles without any errors.

I looked at the code and I think the exclusion of intersection sources is a side-effect of the original implementation, which only worked on object types. But it's trivial to allow intersections as source types.
I didn't see any new errors on the user tests, and on Definitely Typed, only in react-native-sortable-list and react-native-swiper, where we now detect the assignment of a branded number to an object type. The branded number came from a mapped type, so this is a subtle bug, and a very good catch.
I'll make a test and send out a PR.


V3 view field Suspended for orgs

The V3 API allows you to see the status of organizations. make this field visible in order to make it available for other developments that use the cloudfoundry go cli library.
Exemple, the community cf_exporter release uses the go library from the cloudfoundry cli in order to retrieve the metrics on the organizations. Currently only the name, guid and quota metrics are reported.
Would it be possible to recover the status of the organizations.
This feature is necessary for applications that use the cli product in go development such as cf_exporter in order to have additional metrics on the org.
This feature don't cause a breaking change.  Users will not be affected by this change
Make the Suspended value returned by the V3 cloudfoundry API available to orgs metrics.

It looks like there is already a PR that fixes this issue. I am going to close it, let me know if there is any work that is still needed.


share content using system share sheet

This commit fixes #2 by removing the WRITE_EXTERNAL_STORAGE permission (which isn't granted on Android 13 and up!), and may not pass app review for the GPS.
Instead, it uses a FileProvider to provide content URIs for a file written to the internal storage of the app, and provides READ permission to the receiving app. This commit was tested against Android 13, with more tests to follow.

Definition of done:

[x] Prototype for sharing tested on Android 13
[x] Manifest permission removed from app
[x] Sharing via content URIs implemented
[x] old code removed
[ ] tested on Android 5
[ ] tested on Android 7
[ ] tested on Android 9
[ ] tested on Android 11
[x] tested on Android 13

also closes #4.


Any way to change a model stub?

Laravel Version: 5.5.36
Voyager Version: 1.0.16
PHP Version: 7.1.0
Database Driver & Version: n/a

Description:
Is there a way to change original model stub? I want all Voyager models to be extended from my custom model automatically, so I don't have to edit each model after it's created.
Steps To Reproduce:
Create model 😄

I solved it. First I created custom custom:make:model {name} command which extends TCG\Voyager\Commands\MakeModelCommand and overrides getStub method to return different stub. Then I published Voyager controllers and copied store method from TCG\Voyager\Http\Controllers\VoyagerDatabaseController into my (published) VoyagerDatabaseController, but instead of calling voyager:make:model I'm calling custom:make:model in that method... and it works 😄


bugfix: alternate option now loads properly from .bertconfig

Pull Request Test Coverage Report for Build<PHONE_NUMBER>5
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 93.811%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1819

Relevant Lines:
1939

💛  - Coveralls


add svelte + FAST starter projects

This PR adds starter projects for:

Svelte + FAST + Vite
Svelte + FAST + Vite + TypeScript

The indentation char is not the correct one.
Tabulation are used.
You can run npm run format to automatically fix this.

@MacFJA thank you for the review and comment!  I have fixed the formatting.


gh-2573: Replace hasTrait usages with Operation

Related Issue

Resolve #2573

Codecov Report

Merging #2574 (5b839d4) into gh-2552-remove-deprecated (d081ca6) will increase coverage by 3.38%.
The diff coverage is n/a.

:exclamation: Current head 5b839d4 differs from pull request most recent head cf33701. Consider uploading reports for the commit cf33701 to get more accurate results

@@                       Coverage Diff                       @@
##             gh-2552-remove-deprecated    #2574      +/-   ##
===============================================================
+ Coverage                        65.30%   68.69%   +3.38%
+ Complexity                        2431      487    -1944
===============================================================
  Files                              872       81     -791
  Lines                            27186     1514   -25672
  Branches                          3165      120    -3045
===============================================================
- Hits                             17755     1040   -16715
+ Misses                            8034      390    -7644
+ Partials                          1397       84    -1313

Impacted Files
Coverage Δ

.../src/main/java/uk/gov/gchq/gaffer/graph/Graph.java

...esultcache/handler/util/GafferResultCacheUtil.java

.../src/main/java/uk/gov/gchq/gaffer/store/Store.java

...affer/store/operation/OperationChainValidator.java

...eration/handler/export/ExportOperationHandler.java

...re/operation/FederatedOperationChainValidator.java

...gaffer/federatedstore/util/FederatedStoreUtil.java

...q/gaffer/rest/controller/PropertiesController.java

...ava/uk/gov/gchq/gaffer/data/graph/GraphWindow.java

...gaffer/store/operation/handler/ForEachHandler.java

... and 781 more

Continue to review full report at Codecov.

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

You considered creating a static util method somewhere ?
public static boolean hasTrait(Trait trait){
boolean isDynamic;
                 try {
                     isDynamic = graph.execute(new HasTrait.Builder()
                             .trait(trait)
                             .currentTraits(false)
                             .build(), new Context());
                 } catch (final OperationException e) {
                     throw new GafferRuntimeException("Error performing HasTrait Operation while validating Views in OperationChain.", e);
                 }
return isDynamic

@GCHQDev404 could do but maybe seems silly to replace a function with an Operation called by a function, only used 4 times anyway.


Weird white line

Dev Home version
<IP_ADDRESS>
Windows build number
10.0.23471.1000
Other software
OS Build Version: 10.0.23471.1000.amd64fre.ni_prerelease.230526-1341
.NET Version: .NET 6.0.16
Steps to reproduce the bug
When I drag to resize the window I see a line from the top left to the bottom right flicker on the screen.
Expected result
To not see a line.
Actual result
I saw a line
Included System Information
CPU: AMD Ryzen 9 3900X 12-Core Processor
Physical Memory: 31.93GB (19.94GB free)
Processor Architecture: x64
Included Extensions Information
Extensions:
Microsoft.Windows.DevHome_<IP_ADDRESS>_x64__8wekyb3d8bbwe
Microsoft.Windows.DevHomeGitHubExtension_<IP_ADDRESS>_x64__8wekyb3d8bbwe

Closing as I can't reproduce this. If you still see it, let me know. It would be helpful to know if there's a specific page where it happen, what theme your OS is in, and what theme your app is set to.


build-script-impl: Add a flag for SourceKit to skip install pass under some conditions

Related to https://github.com/apple/swift/pull/5387.

@swift-ci Please smoke test


Domain file and problem file shouldn't require to have case sensitive domain name identical

PDDL is a case unsensitive language the name of the domain should match but do not require to be the same case.

This is now fixed. Took a while.


Rephrase description of provide-api-key

Move the description of the default value of provide-api-key for new actions to the beginning of the description, before explaining the behavior when not specified in an existing action. This is to avoid confusion about the value of provide-api-key when not provided.
Related to this suggestion (not a direct issue).

Codecov Report

Merging #4654 into master will decrease coverage by 4.11%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #4654      +/-   ##
==========================================
- Coverage    82.9%   78.78%   -4.12%
==========================================
  Files         183      183
  Lines        8377     8377
  Branches      566      566
==========================================
- Hits         6945     6600     -345
- Misses       1432     1777     +345

Impacted Files
Coverage Δ

...core/database/cosmosdb/RxObservableImplicits.scala
0% <0%> (-100%)
:arrow_down:

...ore/database/cosmosdb/cache/CacheInvalidator.scala
0% <0%> (-100%)
:arrow_down:

...core/database/cosmosdb/CosmosDBArtifactStore.scala
0% <0%> (-95.89%)
:arrow_down:

...tabase/cosmosdb/cache/CacheInvalidatorConfig.scala
0% <0%> (-94.74%)
:arrow_down:

...sk/core/database/cosmosdb/CosmosDBViewMapper.scala
0% <0%> (-92.6%)
:arrow_down:

...e/database/cosmosdb/cache/ChangeFeedListener.scala
0% <0%> (-86.67%)
:arrow_down:

...e/database/cosmosdb/cache/KafkaEventProducer.scala
0% <0%> (-76.48%)
:arrow_down:

...whisk/core/database/cosmosdb/CosmosDBSupport.scala
0% <0%> (-74.08%)
:arrow_down:

...a/org/apache/openwhisk/common/ExecutorCloser.scala
0% <0%> (-66.67%)
:arrow_down:

...abase/cosmosdb/CosmosDBArtifactStoreProvider.scala
4% <0%> (-52%)
:arrow_down:

... and 32 more

Continue to review full report at Codecov.

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


Zones with more than 100 records not handled

my source zone has approx 300 records in it.
on the first run all the records were created in route53.
on the next run however some records were attempted to be created again

Transferring zone example.com from server <IP_ADDRESS>
Getting VPC SOA serial from Route 53
Comparing SOA serial<PHONE_NUMBER> with<PHONE_NUMBER>
Updating as CREATE for A record test TTL 300 in zone example.com with [<DNS IN A rdata: <IP_ADDRESS>>]
An error occurred (InvalidChangeBatch) when calling the ChangeResourceRecordSets operation: Tried to create resource record set [name='test.example.com.', type='A'] but it already exists
ERROR: Unable to update zone example.com

it appears that the software does not account for the fact that ListResourceRecords by default returns 100 records at a time.
see: http://docs.aws.amazon.com/Route53/latest/APIReference/API_ListResourceRecordSets.html
since only 100 records are fetched from route53, then remaining records are assumed missing and scheduled for creation. when the create is attempted it fails because the record already exists.

I'm in favor. This is a one-line fix, is easy to test, and it worked on my source zone with over 3600 RRs. Please merge.


MailSlurper gets slow after a few thousand emails are stored

After MailSlurper stores a few thousand emails, the interface becomes sluggish.

Resolved


Element fix

https://developer.mozilla.org/en-US/docs/Web/API/Element/innerHTML
InnerHTML and other properties are a properties of Element, but not HTMLElement. This API mismatch caused inproper usage of JSO api which caused working incorrect code https://github.com/konsoletyper/teavm/issues/916
Incorrect code is fixed now, so properties should be moved to correct place.

Why closed this PR? It isn't incorrect and puts properties to the correct place and is backward compatible.

This PR is incorrect.

It actually fixes issues I presented in https://github.com/konsoletyper/teavm/issues/916 when I create ElementNS, I can assign class to its classlist or setInnerHTML in JS. Due to this methods presence in JSO HTMLElement, this methods are inaccessible at all. What are you suggesting then?

I don't understand the problem. Can you please clarify?

Element svg = HTMLDocument.current().createElementNS("svgschema", "svg);
// i want to set inner HTML or classList but I can't because it's not present in Element interface

Earlier it worked due to wrong typechecking on JS side. Due to this fact, I didn't check that it's not in Element and used it against HTMLElement. Now it is broken because you fixed JS type system. So now we need to put properties in correct place. Please check MDN link I provided.

First of all, MDN is non-normative and you can't refer on it. Second, there are two Element interfaces: from DOM spec and from HTML spec, and the one from DOM spec does not contain innerHTML property, and especially properties like clientWidth, since in general case a DOM application does not provide any visual representation.
 When I said "this PR is incorrect" this means this PR is incorrect and you should accept it and try to figure out why youself.


Cannot use buffer slice with instancing

I can't seem to figure out how to issue a draw() command with instancing while only using part of the instance buffer.
I have two structs, Vertex and VertexInstance. The vertex buffer is a Arc<ImmutableBuffer<[Vertex]>>, and the instance buffer is a Arc<CpuAccessibleBuffer<[VertexInstance]>>.
I'm trying to figure out what to put for the vertex_buffer parameter in AutoCommandBufferBuilder::draw(). I cannot use a tuple like the instancing example or I get:
expected struct `std::vec::Vec`, found tuple

I can provide both buffers within a vec![] macro, but only the whole buffers. I want to allocate the buffers ahead of time with a fixed size and then reuse said buffers by writing to them. Thus I only want to draw the instances that are "fresh" in the buffer. If I try to use a BufferSlice, it is typed with the vertex struct, so if I try to use them in draw(), I get:
expected struct `Vertex`, found struct `VertexInstance`

Is there something I'm missing? How do I use these together?

I don't know much about instances, otherwise I could provide some more helpful feedback. Sounds to me though, that this is a bug.

This is probably fixed now that vertex buffers are specified in a very different way?


How to get user profile info?

Hi everyone!
What method i must to use for retrive user info like first_name and last_name?
Thx/

The Telegram bot api don't have independent method than return information about user but you can get information then when him enter some command or word in telegram
for example:
bot.onText(/\/help/, function (msg) {
console.log(msg);
var fromId = msg.from.id;
bot.sendMessage(fromId, msg.from.first_name + ' ' + msg.from.last_name );
});


Add kubernetes api schema validation to linter

Kubernetes has a validation engine which can be used to ensure yaml conforms to the relevant API group before its deployed via the --validate=true flag. It would be exceedingly useful to leverage this functionality to identify template formatting issues. Since the linter is rules based it seems like a reasonable place to add this feature rather than adding a new command like validate.

We looked at this before, and the consensus was that helm lint must not require an active network connection in order to stay backward compatible. However, it would be possible to do client-side validation by using the JSON Schema files.

I looked at using local schema files, but I'm not sure you can guarantee they will be present on a client system. They are cached on initial server access? Plus without a server available you are still faced with the dilemma of what schema version to use. Is there some default schema version available client side that I'm unaware of?
Another option would be to make this is own CLI parameter - 'validate' perhaps? I'm still inclined to think this is linting type functionality though.

Putting this back on the backlog milestone until someone takes it on

/remove-lifecycle stale
/lifecycle frozen

What about providing a CLI option that would permit connections to a live cluster?  We've run into problems with Helm over and over where the Kubernetes YAML turned out to be incorrect (though valid YAML itself), and when it failed, the k8s error was swallowed by a Helm error, leading to red herrings.  This would have been prevented if we could clearly see from Kubernetes that the YAML wasn't a fully valid spec.

For kubectl, --validate is an option for apply and create commands.  How about adding --validate option to helm install & upgrade to be consistent with kubectl?  Then we can bypass the helm lint no networking problem too right?

#2585 was due to inactivity. If someone is interested in pushing this feature along the finish line, please write a PR against Helm 3. As per the announcement on the mailing list, Helm 2.15.0 is the last release where we will be merging new features for Helm 2. Thanks!

I would like to highlight that due to the missing validation functionality, things may actually fail in quite subtle ways and I suggest raising the priority of this issue because of this.
The "obvious" way things fail without validation, as already mentioned above, is that a release ends up failed because the manifests were invalid Kubernetes objects. You may get strange error messages from helm sometimes due to this and it is of course annoying.
What is worse though, is that the release may succeed just fine, without any warnings or other signs of problems, but the manifests may still be invalid and the API server will use default values instead of whatever you provided. This means that you may think that everything is configured in a certain way even though it is not. Very confusing and potentially dangerous.
How can this be? Let me show the example that thought me this:
A tired human happens to put the strategy field of a Deployment under spec.template.spec instead of spec, where it belongs. A simple mistake that is quite hard to spot. It looks something like this:
...
spec:
  replicas: {{ .Values.replicaCount }}
  # This is where strategy should be
  template:
    spec:
      # This is not valid: strategy should be under spec, not spec.template.spec
      strategy:
        type: RollingUpdate
        rollingUpdate:
          maxUnavailable: 0
          maxSurge: 1
...

This is not valid, and if you try to kubectl apply the manifest, it will fail with a suggestion that you can set --validation=false if you want to ignore the problem. But if you use helm directly instead there is no error or warning. This is what actually ended up in Kubernetes:
...
spec:
  replicas: 1
  strategy:
    rollingUpdate:
      maxSurge: 25%
      maxUnavailable: 25%
    type: RollingUpdate
...

That is a correct manifest and the default if you don't specify anything else. The API server simply ignores "extra" fields and adds defaults as needed. This is quite dangerous, very confusing and frustrating to debug if you are lucky enough to spot the difference in the first place.
There are a couple of issues that I think should be counted as duplicates of this one, namely:

#5836
#5577 (note how this shows exactly how the API server ignores completelyRandomName: my.conf)

#6663 is also related but different. I'm not sure how the helm template --validate works, but a quick test indicates that it does not check that the manifest is valid, but rather that it is possible to apply it on the server. If I "validate" the example above I still get the invalid manifest as output, i.e. strategy is in the wrong place.
TL;DR: I think this issue deserves a higher priority. Alternatively, a new issue should be opened to adress validation during upgrade/install.

should this work the same way as what people are describing?
helm install --dry-run --debug . | kubectl apply -f -

should this work the same way as what people are describing?
helm install --dry-run --debug . | kubectl apply -f -

Nevermind, I see that it has a bunch of other things that don't allow the manifests to be processed

There's helm template --validate available in Helm 3, which performs the same operation as what's described here. PRs welcome to port that over for helm lint.

Hey everyone! Googling "help api validation" brought me here.
Here's a curious thing we stumbled upon at my workplace this week: Cronjobs have a 52 character limit for their names.
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: did-you-know-that-k8s-limits-cronjob-names-to-52-characters
spec:
  schedule: "*/1 * * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
            - name: hello
              image: busybox
              imagePullPolicy: IfNotPresent
              args:
                - /bin/sh
                - -c
                - date; echo Hello from the Kubernetes cluster
          restartPolicy: OnFailure

Kubernetes will not accept this object:
kubectl apply -f cronjob.yaml
The CronJob "did-you-know-that-k8s-limits-cronjob-names-to-52-characters" is invalid: metadata.name: Invalid value: "did-you-know-that-k8s-limits-cronjob-names-to-52-characters": must be no more than 52 characters

We can put this in a chart and then lint it, template it, and dry-run the install, but none of these catch the issue:
helm lint  ./testchart/
helm template --validate ./testchart/
helm install --dry-run --debug testchart ./testchart/

Somewhat off topic, but disappointingly, kubeval also doesn't see anything wrong with this:
cat cronjob.yaml | kubeval
PASS - stdin contains a valid CronJob (did-you-know-that-k8s-limits-cronjob-names-to-52-characters)

It is only when you do server side validation with kubectl that you can actually spot this:
kubectl apply --dry-run=server -f cronjob.yaml
The CronJob "did-you-know-that-k8s-limits-cronjob-names-to-52-characters" is invalid: metadata.name: Invalid value: "did-you-know-that-k8s-limits-cronjob-names-to-52-characters": must be no more than 52 characters

In the end, on top of helm lint on the linting step of our pipeline, we also added:
helm template --validate ./testchart/ | kubectl apply -f - --dry-run=server

So we can know that the Kubernetes API will accept our object definitions.
@bacongobbler maybe this is worth a new feature request? I'm not sure if I'm missing something here. It would be nice to be able to do this type of server side validation (--dry-run=server) with helm.
Tested with helm 3.5 and k3s 1.20

Hey everyone! Googling "help api validation" brought me here.
Here's a curious thing we stumbled upon at my workplace this week: Cronjobs have a 52 character limit for their names.
apiVersion: batch/v1beta1
kind: CronJob
metadata:
  name: did-you-know-that-k8s-limits-cronjob-names-to-52-characters
spec:
  schedule: "*/1 * * * *"
  jobTemplate:
    spec:
      template:
        spec:
          containers:
            - name: hello
              image: busybox
              imagePullPolicy: IfNotPresent
              args:
                - /bin/sh
                - -c
                - date; echo Hello from the Kubernetes cluster
          restartPolicy: OnFailure

Kubernetes will not accept this object:
kubectl apply -f cronjob.yaml
The CronJob "did-you-know-that-k8s-limits-cronjob-names-to-52-characters" is invalid: metadata.name: Invalid value: "did-you-know-that-k8s-limits-cronjob-names-to-52-characters": must be no more than 52 characters

We can put this in a chart and then lint it, template it, and dry-run the install, but none of these catch the issue:
helm lint  ./testchart/
helm template --validate ./testchart/
helm install --dry-run --debug testchart ./testchart/

Somewhat off topic, but disappointingly, kubeval also doesn't see anything wrong with this:
cat cronjob.yaml | kubeval
PASS - stdin contains a valid CronJob (did-you-know-that-k8s-limits-cronjob-names-to-52-characters)

It is only when you do server side validation with kubectl that you can actually spot this:
kubectl apply --dry-run=server -f cronjob.yaml
The CronJob "did-you-know-that-k8s-limits-cronjob-names-to-52-characters" is invalid: metadata.name: Invalid value: "did-you-know-that-k8s-limits-cronjob-names-to-52-characters": must be no more than 52 characters

In the end, on top of helm lint on the linting step of our pipeline, we also added:
helm template --validate ./testchart/ | kubectl apply -f - --dry-run=server

So we can know that the Kubernetes API will accept our object definitions.
@bacongobbler maybe this is worth a new feature request? I'm not sure if I'm missing something here. It would be nice to be able to do this type of server side validation (--dry-run=server) with helm.
Tested with helm 3.5 and k3s 1.20

@DanielCalvo see also my comment above. This behavior can actually hide errors since helm basically disables validation like if you run kubectl apply --validation=false. Of course if it is a critical error like the CronJob name length, it won't be accepted anyway, but if it is something like you specified a field in the wrong place it will just silently ignore it. :scream:

@DanielCalvo see also my comment above. This behavior can actually hide errors since helm basically disables validation like if you run kubectl apply --validation=false. Of course if it is a critical error like the CronJob name length, it won't be accepted anyway, but if it is something like you specified a field in the wrong place it will just silently ignore it. :scream:

Feel free to propose PRs to improve Helm's validation logic.

Feel free to propose PRs to improve Helm's validation logic.


The renderer option allows you to render tokens in a custom manor

From README.md: The renderer option allows you to render tokens in a custom manor

manor
noun(also manor house)
a large country house with lands; the principal house of a landed estate.
manner
noun
a way in which a thing is done or happens

Apologies if this was intentional/ironic.

Closing as non-issue. I do not believe it's ironic. Please submit PR with fix as we focus on getting things back under control around here. :)


feat(word): support emoji on github pages

Signed-off-by: ito-san<EMAIL_ADDRESS>In this PR https://github.com/autowarefoundation/open-ad-kit-docs/pull/32, speck check failed.
https://github.com/autowarefoundation/open-ad-kit-docs/actions/runs/3149471148/jobs/5121125738

https://squidfunk.github.io/mkdocs-material/reference/icons-emojis/
materialx
twemoji

Ah, please update autoware-spell-check-dict/.cspell.json instead.

@kenji-miyake

Ah, please update autoware-spell-check-dict/.cspell.json instead.

Sorry! Fixed in https://github.com/tier4/autoware-spell-check-dict/pull/358/commits/57ddccbd1f99bf290f0d2c517894669b6d140fe3.


Improving version v.22.05.30

@ all
This v.23.05.30 demo version, I closed https://github.com/sunflowerit/waftlib/pull/34 and create this new one, any new idea will be welcome.

@ all
Don't merge this branch to master, still need more work.


Content Database Limits - wrong description on limit

[Enter feedback here]
The description of the content database limitations, is from upload size:
"The default file size is 2047 MB, which can be increased to a maximum of 10 GB. Multiple site collections can share a single content database. Each site collection needs to be fully stored in a single content database. "
This should be corrected.
Thanks.

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

ID: 76d1a46c-4a3b-f99d-cca8-326b36235b1d
Version Independent ID: d99a6050-b1af-afa2-8948-b1bba2ea7398
Content: Software boundaries and limits for SharePoint Server 2016
Content Source: SharePoint/SharePointServer/install/software-boundaries-and-limits-0.md
Product: sharepoint-server-itpro
GitHub Login: @Techwriter40
Microsoft Alias: kirks

@danone1985 thanks for  your feedback. What should the value be ?? and has this been tested?

Thanks for feedback @danone1985 and fix @tseward !

As per MSDN, It is suggested that for ease of backup and restore that individual site collections within a content database be limited to 100 GB.
if site collection storage consumption is more than that, then how to restrict the site collection to use new content database rather than old existing one?


The results of the two operations are different when i use standarSqlFormat，the indent before '(' are not the same

I have a sql
insert into user(name, age) values('text', 11)

the first time i format it, i get the result
insert into
  user(name, age)
values
('text', 11)

Based on the last result，Continue to format，i get the result
insert into
  user(name, age)
values
  ('text', 11)

i expect the same sql get the same result just like the second
the version i used was 4.0.2

Problem still present in latest master. Likely related to values( looking like a function and getting formatted differently from values (.

This is now finally fixed in 9.0.0-beta1


cloud hosting / microsoft onedrive

hi could someone please tell me if there is any scope for integrationg functions that automatically store uploaded files on cloud servers line one drive. thanks

I'd suggest you to start reading here: https://laravel.com/docs/5.2/filesystem#the-public-disk
Im not sure if these drivers are currently compatible with ticketit, i'll take a loom

@sb-lc Now I checked the source and there's no attachment support in the stable (0.2) release at all. You can only insert images in the editor, that's it. In 1.0 however you can upload files but the code doesn't use Laravel's flysystem, uploads are handled via native php calls. Since 1.0 is discontinued and never be released, but it kinda works, I suggest you to fork that branch and do whatever you want in order to use flysystem.
If you dont like that way you can wait for v2, however it's very far from release.


Current week tasks not showing in calendar view

Search first

[X] I searched and no similar issues were found

What Happened?
Since last update 3.10.4, and possibly connected to my previous request #313, in calendar view I don't see the tasks that take more than one day in the current week (bit I see them in the adjacent ones), while I see the daily tasks set on journal pages.
Reproduce the Bug
open agenda3, calendar view, with tasks taking more than one week
Screenshots

Environment Information
Windows 10, Logseq 0.10.9, Agenda 3.10.2
Additional Context
No response
Are you willing to submit a PR? If you know how to fix the bug.

[ ] I'm willing to submit a PR (Thank you!)

Could you provide the original text of the task in logseq?

Here it is,
TODO Analisi
SCHEDULED: <2024-04-17 Wed>
:AGENDA:
end: 2024-05-31
:END:

If I may make a guess, could it be more of an aestetic matter? I did some tests and if I reduce the number of tasks, they do appear again. They disappear in bulk when they are enough to saturate the vertical space of the calendar cell.
To replicate it, you could try adding more todos untill you fill all the available space.
I hope it helps.
Thanks

Can the task displayed after click "+1 more" button?

Can you send me the original text of all tasks that need to be displayed this week? I still haven't reproduced this issue on my end.


2D Shapes Example does not compile

2D Shapes Example does not compile
The 2D shapes example is missing some code (the compiler was actually very helpful here). During the spawning of the bundles, most of the shapes are missing an inner .into() call.
Code for the setup() function should be:
fn setup(
    mut commands: Commands,
    mut meshes: ResMut<Assets<Mesh>>,
    mut materials: ResMut<Assets<ColorMaterial>>,
) {
    commands.spawn(Camera2dBundle::default());

    // Circle
    commands.spawn(MaterialMesh2dBundle {
        mesh: meshes.add(shape::Circle::new(50.).into()).into(),
        material: materials.add(Color::PURPLE.into()),
        transform: Transform::from_translation(Vec3::new(-150., 0., 0.)),
        ..default()
    });

    // Rectangle
    commands.spawn(SpriteBundle {
        sprite: Sprite {
            color: Color::rgb(0.25, 0.25, 0.75),
            custom_size: Some(Vec2::new(50.0, 100.0)),
            ..default()
        },
        transform: Transform::from_translation(Vec3::new(-50., 0., 0.)),
        ..default()
    });

    // Quad
    commands.spawn(MaterialMesh2dBundle {
        mesh: meshes.add(shape::Quad::new(Vec2::new(50., 100.)).into()).into(),
        material: materials.add(Color::LIME_GREEN.into()),
        transform: Transform::from_translation(Vec3::new(50., 0., 0.)),
        ..default()
    });

    // Hexagon
    commands.spawn(MaterialMesh2dBundle {
        mesh: meshes.add(shape::RegularPolygon::new(50., 6).into()).into(),
        material: materials.add(Color::TURQUOISE.into()),
        transform: Transform::from_translation(Vec3::new(150., 0., 0.)),
        ..default()
    });
}

It does compile.
if you git clone https://github.com/bevyengine/bevy.git and cargo run --example 2d_shapes, you'll notice it compile correctly. In fact, we have a fairly extensive CI setup to guarantee this doesn't occurs.
You might have tried to run a main example using the release bevy version. To get an example that compiles with the latest released version of bevy use the latest branch.
Here is a link the the 2d shape example that compiles on 0.12.1: https://github.com/bevyengine/bevy/blob/latest/examples/2d/2d_shapes.rs

@nicopap Ahh yes this is exactly what happened. Thank you!


The editor crashes after writing "X++" in GDscript and saving

Godot version:
4.0 dev Build with VS2019
OS/device including version:
windows10 Vulkan/NVIDIA - NVIDIA GeForce GTX 1060 6GB
Issue description:
Feel free to create a GDScript script which contains statements:
var i=0
i=i++
Steps to reproduce:
Then save the entire project, Godot crashed immediately, and I couldn't immediately intercept the information output from the console. And the project cannot be opened again unless the statement "i++" is deleted from the outside.
As long as "X++" appears, your editor will crash.
Minimal reproduction project:
All you need the GDScript:
Node2D.zip

OK，After several observations, I found that he failed to capture any relevant information.

I can confirm this on Linux Mint 20.04, Intel Integrated Graphics, Godot 4.0 custom build.

Here is the backtrace.
Vulkan: Early out of date swapchain, recreating.
handle_crash: Program crashed with signal 11
Dumping the backtrace. Please include this when reporting the bug on https://github.com/godotengine/godot/issues
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7f4e498b7210] (??:0)
[2] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x3816134] (/home/amor/Desktop/projects/parent_godot/modules/gdscript/gdscript_compiler.cpp:208)
[3] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x38173f7] (/home/amor/Desktop/projects/parent_godot/modules/gdscript/gdscript_compiler.cpp:721)
[4] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x3818664] (/home/amor/Desktop/projects/parent_godot/modules/gdscript/gdscript_compiler.cpp:796)
[5] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x3824858] (/home/amor/Desktop/projects/parent_godot/modules/gdscript/gdscript_compiler.cpp:1825)
[6] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x381faff] (/home/amor/Desktop/projects/parent_godot/modules/gdscript/gdscript_compiler.cpp:1971)
[7] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x382c11c] (/home/amor/Desktop/projects/parent_godot/modules/gdscript/gdscript_compiler.cpp:2444)
[8] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x382d04b] (/home/amor/Desktop/projects/parent_godot/modules/gdscript/gdscript_compiler.cpp:2612)
[9] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x37bc1aa] (/home/amor/Desktop/projects/parent_godot/modules/gdscript/gdscript.cpp:?)
[10] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x37c6313] (/home/amor/Desktop/projects/parent_godot/modules/gdscript/gdscript.cpp:?)
[11] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x37c9b8a] (/home/amor/Desktop/projects/parent_godot/./core/object/reference.h:220)
[12] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x61f46e6] (/home/amor/Desktop/projects/parent_godot/core/io/resource_saver.cpp:?)
[13] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x3f11ace] (/home/amor/Desktop/projects/parent_godot/editor/editor_node.cpp:1084)
[14] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x3f12456] (/home/amor/Desktop/projects/parent_godot/./core/templates/cowdata.h:380)
[15] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x48ed3ed] (/home/amor/Desktop/projects/parent_godot/editor/plugins/script_editor_plugin.cpp:?)
[16] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x3dddc64] (/home/amor/Desktop/projects/parent_godot/editor/editor_data.cpp:381)
[17] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x3f1a1ab] (/home/amor/Desktop/projects/parent_godot/./core/templates/list.h:185)
[18] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x3f190dd] (/home/amor/Desktop/projects/parent_godot/./core/templates/cowdata.h:380)
[19] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x3f0608c] (/home/amor/Desktop/projects/parent_godot/./core/templates/cowdata.h:380)
[20] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x3f74c70] (/home/amor/Desktop/projects/parent_godot/./core/variant/binder_common.h:214)
[21] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x62bd9ef] (/home/amor/Desktop/projects/parent_godot/core/variant/callable.cpp:?)
[22] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x6556251] (/home/amor/Desktop/projects/parent_godot/core/object/object.cpp:?)
[23] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x65548b3] (/home/amor/Desktop/projects/parent_godot/core/object/object.cpp:1099)
[24] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x4e42de6] (/home/amor/Desktop/projects/parent_godot/scene/gui/popup_menu.cpp:1379)
[25] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x4e4f1cc] (/home/amor/Desktop/projects/parent_godot/scene/gui/popup_menu.cpp:?)
[26] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x4e28bc0] (/home/amor/Desktop/projects/parent_godot/scene/gui/menu_button.cpp:52)
[27] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x4478739] (/home/amor/Desktop/projects/parent_godot/./core/object/reference.h:220)
[28] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x4478600] (/home/amor/Desktop/projects/parent_godot/./core/variant/binder_common.h:357)
[29] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x4478346] (/home/amor/Desktop/projects/parent_godot/./core/variant/variant.h:127)
[30] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x4c6d173] (/home/amor/Desktop/projects/parent_godot/./core/variant/variant.h:256)
[31] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x4ca1503] (/home/amor/Desktop/projects/parent_godot/scene/main/viewport.cpp:?)
[32] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x4cce1f3] (/home/amor/Desktop/projects/parent_godot/scene/main/window.cpp:919)
[33] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x4ce0ea9] (/home/amor/Desktop/projects/parent_godot/./core/object/reference.h:220)
[34] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x62bd9ef] (/home/amor/Desktop/projects/parent_godot/core/variant/callable.cpp:?)
[35] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x2ea3b9c] (/home/amor/Desktop/projects/parent_godot/platform/linuxbsd/display_server_x11.cpp:?)
[36] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x624904b] (/home/amor/Desktop/projects/parent_godot/./core/object/reference.h:220)
[37] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x624a18f] (/home/amor/Desktop/projects/parent_godot/./core/templates/list.h:274)
[38] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x2ea6ae5] (/home/amor/Desktop/projects/parent_godot/./core/templates/local_vector.h:253)
[39] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x2e8ff25] (/home/amor/Desktop/projects/parent_godot/platform/linuxbsd/os_linuxbsd.cpp:276)
[40] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x2e8d302] (/home/amor/Desktop/projects/parent_godot/platform/linuxbsd/godot_linuxbsd.cpp:60)
[41] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7f4e498980b3] (??:0)
[42] /home/amor/Desktop/projects/godot_source/4.0/bin/godot.linuxbsd.opt.tools.64.llvm() [0x2e8d18e] (??:?)

Is it the issue with missing expression between +, or do we have increment operator like in C++? 😃
Does it also crash with i--? Or any operator for that matter.

Is it the issue with missing expression between +, or do we have increment operator like in C++? :smiley:

There are no ++ and -- operators in GDScript. The ideal would be to display an error message to tell the user to use += 1 and -= 1 instead.

Does it also crash with i--? Or any operator for that matter.

Yes it happens with ++ and -- and not with ** or //.
Crashes also when we type -- without any operand.
The issue occurs only inside a function. Not outside.

Related issue: #19128.


Inconsistent gd-script execution

Godot version
3.5.1.stable
System information
Windows 10
Issue description
Attached project runs inconsistently. It looks like there is something uninitialized in gd-script processing code. If breakpoints are placed at first lines of all methods of main.gd there may be 3 scenarios of how it runs.

It may first get into _ready() and debugger detaches as soon as execution gets to the 2-d line of _ready().
It may first enter into _get_sun_direction() without entering _ready() and stop because of null variable (which is indeed null).
It may first enter _ready() and proceed without any troubles without even entering _get_sun_direction() at all.

Steps to reproduce

In main.gd place breakpoints at the first lines of _ready() and _get_sun_direction(), see the screenshot attached.
Run the project.
Step through the code by pressing F10.
It may either enter _ready() and detach the debugger at the 2-d line, or it may enter _get_sun_direction() and stop due to null variable, or it may step through the _ready() all the way with no problems at all.
Go to step 2), next time you run it, it may exhibit the same or different behavior. In order to get all 3 scenarios, it is necessary to run it many times.

Minimal reproduction project
failing_scene.zip

Launched more than 20 times, always the same result:
F5
-> Break on line 10
F10
-> Break on line 20
F12
-> Break on line 20
F5
...

3.5.1.stable on Windows 10

Assuming it is consistent, it it normal that being at line 10, when F10 is pressed, instead of going to line 11 if jumps straight to line 20 without leaving _ready() first?

Maybe a problem because it's a getter?
If we set a valid value for "ret" (e.g. ret = Basis()), and remove the breakpoint on line 20, the debugger acts normally, but if we keep the breakpoint, then then debugger keeps going back to line 21

Maybe a problem because it's a getter?

It acts as if GD-script had preemptive execution. There are no references in _ready() which could call _get_sun_direction() in any possible way. Despite of that it gets into _get_sun_direction() between lines 10 and 11 of _ready(). And potentially _get_sun_direction() could change some state variables (if there were any). Which means that lines 10 and 11 may potentially run under different conditions, see the example below.
For example:
extends ViewportContainer

var a: int = 1
var b: int = 1

export(Basis) var direction setget ,_get_sun_direction

func _ready():
    var x: int = a
    var y: int = b
    print( "sum: ", x + y ) # We expect the result to be either 2 or 4. But due to getter is called in between, we get 3.

func _set_sun_direction( b: Basis ):
    pass

func _get_sun_direction():
    a = 2
    b = 2
    var ret: Basis = Basis.IDENTITY
    return ret

There is absolutely something up with the debugger.
Note: Testing in Windows 10, Godot 3.5.1, 3.5.2, and 3.6 beta 2, they all show the same behavior.
My hypothesis is that the source of the inconsistency is the debugger reading the variables for display. More precisely, when it breaks on _ready, it wants to read the variables to show them to you, but it finds a getter (which also has a breakpoint, but it can't get to it because it is currently on a breakpoint). I don't know if Godot uses deferred execution in this case, if it doesn't that could explain the experienced crashes.

Executing as instructed, the behavior I got was first the breakpoint in _ready, then error in _get_sun_direction
In Godot 3.5.1, I believe it did once not enter _get_sun_direction but I was unable to reproduce that. I suspect it might be timing.

I modified the code to this:
extends ViewportContainer

export(Basis) var light_direction = Basis.IDENTITY setget _set_sun_direction, _get_sun_direction

var _light: DirectionalLight = null

func _ready():
	prints("_ready started")
	var a: int = 0
	var b: int = 1
	var c: int = 2
	prints("_ready ended")

func _set_sun_direction( b: Basis ):
	prints("_set_sun_direction started")
	_light.transform.basis = b
	prints("_get_sun_direction ended")

func _get_sun_direction():
	prints("_get_sun_direction started")
	var ret: Basis = _light.transform.basis
	prints("_get_sun_direction ended")
	return ret

And when ran, the output was:
_ready started
_ready ended

And no crash or error.
Which means it didn't get into _get_sun_direction at all. Ergo: executing _get_sun_direction is a debugger only behavior.

Adding breakpoints like this:

Then the execution breaks in _ready before the prints statement is executed. If I try to click on the call stack, and we experience an editor crash (the process remains in execution, which I discovered after trying to clear logs, which didn't have any errors), also the game does not crash, but does not resume either (the scene is never shown, it does not update the graphics, the windows responds to OS messages).
If instead I resume the execution, then we get to the error in _get_sun_direction. The output is:
_get_sun_direction started

And it will repeat the line every time we try to resume after we got the error.

Ah, but if you add the breakpoints like this:

Then the editor gets to the breakpoint in _ready and we experience an editor crash (as described above). About the logs, the output was:
_ready started
_get_sun_direction started


2.0.3 http request node - TLS certificate verification no longer succeeds

Current Behavior
When running nodered v1.3.5 everything works as expected, all http request nodes leveraging TLS with a certificate authority present and verification enabled, work without issue.
Post upgrade to 2.0.3 every http request node leveraging a TLS profile that verifies the certificate fails with "RequestError: self signed certificate in certificate chain" appearing in debug and SELF_SIGNED_CERT_IN_CHAIN displayed as the node status for the http request node.  The only way I've found around this is to disable certificate verification.  Validating certificate of the server the http node is hitting in openssl against the same certificate uploaded to the TLS config under CA certificate works and passes verification.
Restoring my backup prior to upgrade to go back to 1.3.5, the same flow works again.  Upgrade a 2nd time, and it no longer works with the same behavior.
Expected Behavior
http request node querying a server with a valid cert, and CA present in TLS config, should not fail certificate verification.
Steps To Reproduce
Using the example flow (modify to your environment) Import your Certificate Authoirty cert into the TLS config.  Change the http request URL to a valid host that has a valid certificate issued by your CA.  The request will fail due to certificate verification failure.
Example flow
[
    {
        "id": "ede8f8bc3ed1d623",
        "type": "http request",
        "z": "90a227ad3d39d234",
        "name": "",
        "method": "POST",
        "ret": "txt",
        "paytoqs": "ignore",
        "url": "https://em01.ag.home.lab/api/login",
        "tls": "06b9d026eb93bb05",
        "persist": false,
        "proxy": "",
        "authType": "",
        "credentials": {},
        "x": 400,
        "y": 400,
        "wires": [
            [
                "7ff06071f1d48158"
            ]
        ]
    },
    {
        "id": "06b9d026eb93bb05",
        "type": "tls-config",
        "name": "CA Verify",
        "cert": "",
        "key": "",
        "ca": "",
        "certname": "",
        "keyname": "",
        "caname": "ca01.ag.home.lab.crt",
        "servername": "",
        "verifyservercert": true,
        "alpnprotocol": "",
        "credentials": {}
    }
]

Environment

Node-RED version: 2.0.3
Node.js version: 14.17.2
npm version: 6.14.13
Platform/OS: Ubuntu 20.04 LXC container
Browser: Google Chrome 92.0.4515.107

Think I've found the cause.
The got module we've moved to in 2.x has decided to rename some of the standard core node.js TLS properties "for better readability". So we can't just pass in a standard tls config object.
https://github.com/sindresorhus/got/blob/main/documentation/5-https.md#certificateauthority

This looks like got uses the opt.https.certificateAuthoritynotopts.https.ca`

Armed with the knowledge above, I did a quick test of updating opts.ca to opts.certificateAuthoirty in 05-tls.js allows certificate verification to work again.

That is not a good fix as multiple other nodes make use of the TLS configuration node and they all expect opts.ca


Issue 526

Coverage increased (+0.08%) to 62.989% when pulling 93a867a031137ba1c2ef5c59e6fb948b38eae3ce on rmarinsky:ISSUE-526 into 846316749dbbcf9ca026c06f79f5aa96683f9381 on codeborne:master.

Codecov Report

Merging #527 into master will increase coverage by 0.07%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master     #527      +/-   ##
============================================
+ Coverage     58.85%   58.92%   +0.07%
  Complexity      691      691
============================================
  Files           131      131
  Lines          2610     2610
  Branches        264      264
============================================
+ Hits           1536     1538       +2
+ Misses          968      966       -2
  Partials        106      106

Impacted Files
Coverage Δ
Complexity Δ

...codeborne/selenide/webdriver/WebDriverFactory.java
68.23% <0%> (ø)
34 <0> (ø)
:arrow_down:

...e/selenide/impl/WebDriverThreadLocalContainer.java
79.86% <0%> (+1.38%)
30% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

@rmarinsky Can you rebase your branch and leave only one commit?

@asolntsev Okey, i will do it


Remove tobin tax

Description
This is the code change to go along with a draft CIP.
Other changes
Describe any minor or "drive-by" changes here.
Tested
An explanation of how the changes were tested or an explanation as to why they don't need to be.
Related issues

Fixes #[issue number here]

Backwards compatibility
Brief explanation of why these changes are/are not backwards compatible.
Documentation
The set of community facing docs that have been added/modified because of this change

I think this issue should be implemented in the Mento repo rather than this one: https://github.com/mento-protocol/mento-core
Mento contracts are soon to be deleted here: https://github.com/celo-org/celo-monorepo/pull/10124

I think this issue should be implemented in the Mento repo rather than this one: https://github.com/mento-protocol/mento-core
Mento contracts are soon to be deleted here: #10124

We can close that from my side. The PR is already linked in the Mento issue for this, so I'll just leave the branch as is for now.


Min SDK 19

Nice work, can you find a way to reduce the min SDK to around 16?

Thank u @bedann . I just opened #4 pull request to reduce the minSdkVersion to 16.
Ciao ciao

Merged, thanks for your support.


oscm-app-aws  logfile is empty

[Build]
docker  2018/10/23
[Steps to reproduce]
create a file<log4j.ess.aws.properties> in <apache/conf>
[Expected result]
errors are logging in <app-aws.log>
[Observed result]
logfile <app-aws.log> is empty.

In the essence, errors are actually logged, but not in every scenario. Errors usually should only be logged by unexpected/unhandled actions. Actions like providing wrong credentials, etc. should not log errors (at most it should be a debug level).
I think that current behavior is correct and in case we would want to log more information overall then it would be an enhancement/feature.
In example this is the place where errors are logged.
https://github.com/servicecatalog/oscm/blob/dbd251fe61def705bb6a9287c6cf7f03dcabbda0/oscm-app-aws/javasrc/org/oscm/app/aws/controller/AWSController.java#L460-L497

Some additional logs and changes to log4j templates that allow info logs to be saved in the .log files merged in commit https://github.com/servicecatalog/oscm/commit/37ebb6b0a1e133219b4f8beb7323deefa659ba9a.


[BEAM-725] Migrate to use the generic Google credentials library

Be sure to do all of the following to help us incorporate your contribution
quickly and easily:

[x] Make sure the PR title is formatted like:
[BEAM-<Jira issue #>] Description of pull request
[x] Make sure tests pass via mvn clean verify. (Even better, enable
Travis-CI on your fork and ensure the whole test matrix passes).
[x] Replace <Jira issue #> in the title with the actual Jira issue
number, if there is one.
[ ] If this contribution is large, please file an Apache
Individual Contributor License Agreement.

Generic library has Apiary and gRPC library support instead of the Apiary only credentials we are currently using.
Dependency diff for modified pom files (old = left, new = right):
beam-sdks-java-core:
8d7
< [INFO] |  \- com.google.auth:google-auth-library-credentials:jar:0.4.0:compile
26c25,26
< [INFO] +- com.google.auth:google-auth-library-oauth2-http:jar:0.4.0:compile
---
> [INFO] +- com.google.auth:google-auth-library-credentials:jar:0.6.0:compile
> [INFO] +- com.google.auth:google-auth-library-oauth2-http:jar:0.6.0:compile
49d48
< [INFO] +- com.google.oauth-client:google-oauth-client-java6:jar:1.22.0:compile
53c52,53
< [INFO] |  \- com.google.api-client:google-api-client-jackson2:jar:1.22.0:compile
---
> [INFO] |  +- com.google.api-client:google-api-client-jackson2:jar:1.22.0:compile
> [INFO] |  \- com.google.oauth-client:google-oauth-client-java6:jar:1.22.0:compile

beam-runners-google-cloud-dataflow-java:
9d8
< [INFO] |  |  \- com.google.auth:google-auth-library-credentials:jar:0.4.0:compile
26d24
< [INFO] |  +- com.google.auth:google-auth-library-oauth2-http:jar:0.4.0:compile
41c39
< [INFO] |  +- com.google.oauth-client:google-oauth-client-java6:jar:1.22.0:compile
---
> [INFO] |  +- com.google.oauth-client:google-oauth-client:jar:1.22.0:compile
52d49
< [INFO] +- com.google.oauth-client:google-oauth-client:jar:1.22.0:compile
61a59,60
> [INFO] +- com.google.auth:google-auth-library-credentials:jar:0.6.0:compile
> [INFO] +- com.google.auth:google-auth-library-oauth2-http:jar:0.6.0:compile
64c63,64
< [INFO] |  \- com.google.api-client:google-api-client-jackson2:jar:1.22.0:compile
---
> [INFO] |  +- com.google.api-client:google-api-client-jackson2:jar:1.22.0:compile
> [INFO] |  \- com.google.oauth-client:google-oauth-client-java6:jar:1.22.0:compile

beam-sdks-java-io-google-cloud-platform:
20d19
< [INFO] |  +- com.google.auth:google-auth-library-oauth2-http:jar:0.4.0:compile
33c32
< [INFO] |  +- com.google.oauth-client:google-oauth-client-java6:jar:1.22.0:compile
---
> [INFO] |  +- com.google.oauth-client:google-oauth-client:jar:1.22.0:compile
44c43,44
< [INFO] |  \- com.google.api-client:google-api-client-jackson2:jar:1.22.0:compile
---
> [INFO] |  +- com.google.api-client:google-api-client-jackson2:jar:1.22.0:compile
> [INFO] |  \- com.google.oauth-client:google-oauth-client-java6:jar:1.22.0:compile
57d56
< [INFO] |  +- com.google.auth:google-auth-library-credentials:jar:0.4.0:compile
69c68,69
< [INFO] +- com.google.oauth-client:google-oauth-client:jar:1.22.0:compile
---
> [INFO] +- com.google.auth:google-auth-library-credentials:jar:0.6.0:compile
> [INFO] +- com.google.auth:google-auth-library-oauth2-http:jar:0.6.0:compile

R: @tgroh


Use more caching to speed up javasrc2cpg for large projects

The biggest performance gains from this PR are that solveType calls resulting in SOEs are now cached. There is still a WIP replacement for the JavaParserTypeSolver (that gets type information from source files) coming that should give much better results, but for now this reduced the AST creation time for elasticsearch to about 11 minutes on my workstation.

Closing in favour of https://github.com/joernio/joern/pull/1986


Create new slide file 0000-01-02-mkoehle5.md

Add 2nd slide to the slide show

Sometimes it is not easy to determine where the bot ends and GitHub starts, and vice versa.

See above...


Translation warnings

Steps to reproduce
Build for android
Expected behaviour
no warnings
Actual behaviour
warning: string 'catalyst_debugjs' has no default translation.
warning: string 'catalyst_element_inspector' has no default translation.
warning: string 'catalyst_jsload_error' has no default translation.
warning: string 'catalyst_jsload_message' has no default translation.
warning: string 'catalyst_jsload_title' has no default translation.
warning: string 'catalyst_reloadjs' has no default translation.
warning: string 'catalyst_settings' has no default translation.
warning: string 'catalyst_settings_title' has no default translation.

@stoffern I still have this one. Did you solved this? It's just warnings but annoying though.

I have the same issue. Any ideas?

oh, dont remember why i closed it. lets reopen it then 😉

I have de same problem


custom validation not working with meteortemplates:forms

Hey Jon,
Nice piece of work...thanks...Jon, I'm having a bit of trouble getting SimpleSchema custom validation working with forms...my app simply crashes however, when I use the same piece of code in another project I'm working on all is well. Is there something I need to know when writing SimpleSchema custom validation with forms? A heads up on this would be great.

I believe I have found the source of this bug. Will push an update as soon as I verify.

Tested locally using the following schema (taken from the SimpleSchema tests):
confirmSchema = new SimpleSchema
  password:
    type: String
    instructions: "Enter a password!"
    custom: ->
      console.log("this", this)
  confirmPassword:
    type: String
    custom: ->
      console.log("this", this)
      console.log("this.field('password')", this.field('password'))
      if this.value isnt this.field('password').value
        return "passwordMismatch"
    instructions: "Confirm your password!"

Using this schema, my app wasn't crashing before the update--but I noticed this.field was undefined. After the update, everything works for me.
Form elements are now validated using the surrounding form block's data context where available, which means you should be able to use all the properties and methods on this as usual in your custom validation.

There is one caveat--this.field() will only have access to values that have passed validation.
I'm assuming this is the best way to go. If you think it's better to allow invalid values at this step, I'm open to discussing it in a separate issue.

Thanks Jon...will give it a go later...

Hey Jon...Thanks for your help, everything seems to be working fine.

Thanks for letting me know. I'm here if you have any other questions or concerns. :+1:

Doesn't work for me ..
password:
  type: String
confirmPassword:
  type: String
  custom: ->
    console.log @field('password').value
    if @value isnt @field('password').value
      return 'passwordMismatch'

So whenever I use the confirmPassword field, I don't get the value of password logged but undefined.

Hi, I'm having trouble getthing this.field() to work. @jonjamz, I replaced my code with the code you pasted in your comment on Jan 12 and the result is as follows:
this
Object {key: "confirmPassword", genericKey: "confirmPassword", definition: Object, isSet: true, value: "thisisatest"…}
password
Object {isSet: false, value: undefined, operator: undefined}

As you can see the returned values for this.field are all unset/undefined. Any ideas what could be wrong?
FYI
aldeed:simple-schema            1.3.3
templates:forms                 1.14.2


rockspec is missing opeth.opeth.init

That file is not being installed. Thanks!

opeth/opeth/init.moon hasn't been implemented yet. I'll do soon.


Do not output stuff to console during testing

It looks ugly.:)

Thanks :) Not sure why I didn't think of that earlier! :fearful:


textbox' object has no attribute 'type' error

Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/ui.py", line 460, in create_ui
txt2img_prompt, txt2img_prompt_styles, txt2img_negative_prompt, submit, _, _, txt2img_prompt_style_apply, txt2img_save_style, txt2img_paste, extra_networks_button, token_counter, token_button, negative_token_counter, negative_token_button = create_toprow(is_img2img=False)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/ui.py", line 288, in create_toprow
prompt = gr.Textbox(label="Prompt", elem_id=f"{id_part}_prompt", show_label=False, lines=3, placeholder="Prompt (press Ctrl+Enter or Alt+Enter to generate)")
File "/usr/local/lib/python3.9/dist-packages/gradio/components.py", line 300, in init
IOComponent.init(
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/scripts.py", line 536, in IOComponent_init
add_classes_to_gradio_component(self)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/scripts.py", line 521, in add_classes_to_gradio_component
comp.elem_classes = ["gradio-" + comp.get_block_name(), *(comp.elem_classes or [])]
AttributeError: 'Textbox' object has no attribute 'elem_classes'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 337, in
webui()
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 240, in webui
shared.demo = modules.ui.create_ui();shared.demo.queue(concurrency_count=999999,status_update_rate=0.1)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/ui.py", line 654, in create_ui
ui_extra_networks.setup_ui(extra_networks_ui, txt2img_gallery)
File "/usr/local/lib/python3.9/dist-packages/gradio/blocks.py", line 1097, in exit
self.config = self.get_config_file()
File "/usr/local/lib/python3.9/dist-packages/gradio/blocks.py", line 1073, in get_config_file
"props": utils.delete_none(block.get_config())
File "/usr/local/lib/python3.9/dist-packages/gradio/components.py", line 322, in get_config
"type": self.type,
AttributeError: 'Textbox' object has no attribute 'type'

same error today

some problem with versions on a colab i think

same!!

I comply with reporting to see if I'm not the only one who had the error, thanks guys, i will wait for some fix or if someone can explain the matter, anyway if Ben reads this I want to thank you for all your work, especially for those of us who do not have a high-end PC

same

The error of mine.
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 337, in
webui()
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/webui.py", line 240, in webui
shared.demo = modules.ui.create_ui();shared.demo.queue(concurrency_count=999999,status_update_rate=0.1)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/ui.py", line 457, in create_ui
modules.scripts.scripts_txt2img.initialize_scripts(is_img2img=False)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/scripts.py", line 290, in initialize_scripts
script = script_class()
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/extensions/sd-webui-controlnet/scripts/controlnet.py", line 229, in init
self.txt2img_w_slider = gr.Slider()
File "/usr/local/lib/python3.9/dist-packages/gradio/components.py", line 662, in init
IOComponent.init(
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/scripts.py", line 536, in IOComponent_init
add_classes_to_gradio_component(self)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/scripts.py", line 521, in add_classes_to_gradio_component
comp.elem_classes = ["gradio-" + comp.get_block_name(), *(comp.elem_classes or [])]
AttributeError: 'Slider' object has no attribute 'elem_classes'

Here too.

use the latest notebook

use the latest notebook

working but this
Error loading script: loopback.py
Traceback (most recent call last):
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/scripts.py", line 256, in load_scripts
script_module = script_loading.load_module(scriptfile.path)
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/modules/script_loading.py", line 11, in load_module
module_spec.loader.exec_module(module)
File "", line 846, in exec_module
File "", line 983, in get_code
File "", line 913, in source_to_code
File "", line 228, in _call_with_frames_removed
File "/content/gdrive/MyDrive/sd/stable-diffusion-webui/scripts/loopback.py", line 57
match denoising_curve:
^
SyntaxError: invalid syntax

that's not caused by the notebook, it's caused by A1111 repo

I'm doing this locally on my PC and the same thing is happening.

SD-Webui API layer loaded
Loading weights [fc2511737a] from E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\models\Stable-diffusion\chilloutmix_NiPrunedFp32Fix.safetensors
Creating model from config: E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\configs\v1-inference.yaml
LatentDiffusion: Running in eps-prediction mode
DiffusionWrapper has 859.52 M params.
Loading VAE weights specified in settings: E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\models\Stable-diffusion\final-pruned.vae.pt
Applying xformers cross attention optimization.
Textual inversion embeddings loaded(0):
Model loaded in 2.1s (create model: 0.3s, apply weights to model: 0.6s, apply half(): 0.7s, load VAE: 0.4s).
Traceback (most recent call last):
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\modules\ui.py", line 460, in create_ui
txt2img_prompt, txt2img_prompt_styles, txt2img_negative_prompt, submit, _, _, txt2img_prompt_style_apply, txt2img_save_style, txt2img_paste, extra_networks_button, token_counter, token_button, negative_token_counter, negative_token_button = create_toprow(is_img2img=False)
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\modules\ui.py", line 288, in create_toprow
prompt = gr.Textbox(label="Prompt", elem_id=f"{id_part}_prompt", show_label=False, lines=3, placeholder="Prompt (press Ctrl+Enter or Alt+Enter to generate)")
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\python\lib\site-packages\gradio\components.py", line 300, in init
IOComponent.init(
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\modules\scripts.py", line 544, in IOComponent_init
add_classes_to_gradio_component(self)
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\modules\scripts.py", line 529, in add_classes_to_gradio_component
comp.elem_classes = ["gradio-" + comp.get_block_name(), *(comp.elem_classes or [])]
AttributeError: 'Textbox' object has no attribute 'elem_classes'
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\webui.py", line 343, in
webui()
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\webui.py", line 243, in webui
shared.demo = modules.ui.create_ui()
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\modules\ui.py", line 459, in create_ui
with gr.Blocks(analytics_enabled=False) as txt2img_interface:
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\python\lib\site-packages\gradio\blocks.py", line 1097, in exit
self.config = self.get_config_file()
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\python\lib\site-packages\gradio\blocks.py", line 1073, in get_config_file
"props": utils.delete_none(block.get_config())
File "E:\Projects\AIpaint\stable-diffusion-webui_23-02-17\python\lib\site-packages\gradio\components.py", line 322, in get_config
"type": self.type,
AttributeError: 'Textbox' object has no attribute 'type'. Did you mean: 'style'?

use the latest notebook

I do, but there is still error with loopback.py. After replacing code, just like in recomendation, UI started to work, but hard and very slow, not genereation, but UI itself. PNG info and placing in frompt field don't wark at all. And UI became, don't even know how to write this... more narrow.

I moved all the extensions to a different directory and it started working.

Same error with me

Same to me. But it goes smoothly just few weeks before, how would it be such troublesome now? I guess there's something wrong with the version.

use the latest notebook

use the latest notebook

Would you please tell me/us how to use the last notebook. I am sure a lot of users like me just followed a step-by-step procedure to install A1111 without an idea of what is going on.

Click on the thumbnails in the main page of the repo

Thank you


Feat/abi compatibility

Started with abi-compatibility, but ended up out-scoping it. This PR adds more tests for the metaregistry and introduces a few fixes in the contracts.

I update ed's script to check for missing pools and instead output a table with comparisons for which functions are missing/available. Makes it more readable and easier to see if a certain function is only used for a certain registry.


Add compute & memory optimized VM Sizes

Add support for additional VM sizes

And very important - Custom HDD size on Windows worker.
Customer has many different Windows Pods (images) which are quite big. This breaks the deployments!
A sizing up to 300GB per worker node should be possible.
--> the current fix size of the deployed images only works in small to midsize  environments


iotdb-go-client

please move all client related files to client folder or others.

please move all client related files to client folder or others.
copy that

dependency thrift should be claimed in LICENSE-binary file.
see: https://github.com/apache/iotdb/blob/master/LICENSE-binary

dependency thrift should be claimed in LICENSE-binary file.
see: https://github.com/apache/iotdb/blob/master/LICENSE-binary

copy that

Thank you Yanhong!


longStackTraces only includes lines starting with "at"

When longStackTraces are enabled, only lines that start with "at" are included in each event's trace, at least on V8.  Here's the regexp from captured_trace.js that does this filtering:
    var v8stackFramePattern = /^\s*at\s*/;

I've been doing my own manipulation of stack traces, adding lines starting with "Caused by: ...", to represent nested errors.  Those "Caused by" lines get thrown out.
I'm sure there's some good reason for filtering the lines in some way.  If someone could provide more background, I can try to come up with a fix that makes Promise.longStackTraces() play nicely with other manipulations of error.stack.

It's not really possible to know when to retain custom text or even differentiate between custom text and the default text that must be discarded.
When stitching stack traces together individual frames or groups of frames can be discarded and it's not possible to know whether some related 3rd party text should be retained or not.

Thanks for the quick response.
I can think of a couple solutions.  The first is my preferred, though I'm not sure it is practical yet, and the second seems at least better than what we have today.

Instead of using a regexp to choose the line you do want, use patterns to identify the lines you do not want.  (I only say this might not be practical because I'm not certain how much stuff there is to screen, and how often it changes.  So far, though, all I've noticed is that some lines that start "Error:" need to be removed)
Allow this to be configurable in the call to Promise.longStackTraces()

It is moot, though, if you don't think the use case I stated before is important.  This is a facility of other languages that I have become accustomed to (chaining exception causes from low level to high level).

@aaronyo well, what I do is instead of relying on the a mutated stack is throw meaningful Errors and attach properties to them as I go, that way in the final catch I can extract everything I need for them (some of my error types have as much as 4 different stages attaching properties and useful information to them. You can also augment error.message IIRC.

The issue with just depending on custom vars is that you often don't have control of whatever top level error handler is catching your exception and printing it out.  For example, when running automated tests, the testing harness will typically print err.stack when an error bubbles to the top, and it won't know about your custom vars.


Default value for module properties

We should switch "example" to "default" in module properties and use that to valuate fields if no user input can be found

Maybe defaultValue as default conflicts with the Java keyword.

@DamnClin @pascalgrimaud
Need your suggestion here regarding the filling of default values in fields, what should be trigger to valuate empty fields:-

First option is to fill the default values whenever clicking on a module (landscape or patch):-

This is good for new project usecases, so that new values are always prefilled.
This may be annoying for user if he wants to enter existing project path afterwards as current logic does not override already filled values (default values in this case)

Second option is to fill the default values on path change (blur):-

This is good for existing projects where the values can be filled as per existing project
This makes default values useless as an already generated project will have most of values (its only good for new modules being applied/patched).

Thinking about it I don't think it is a good idea to actually "fill" the fields. I think we should just use the default value when validating for fields that are not valuated by the users.
Filling the field will be annoying since users will have to delete the value before adding it again.

@DamnClin Yes I made the change locally and tried it, did not feel very elegant on UX.
Did you mean to allow users to Apply modules even with empty mandatory properties and use default value in backend for generation?

Did you mean to allow users to Apply modules even with empty mandatory properties and use default value in backend for generation?

Yep

Adding a bounty on this great feature
Don't forget to claim it @swarajsaaj
Thanks @DamnClin for the review

Thanks @pascalgrimaud and @DamnClin
claimed the bounty here https://opencollective.com/generator-jhipster/expenses/100676

@swarajsaaj : approved


[GIT PULL] add io_uring_enable_rings.3 man page, fix a few other man page things

Add a man page for io_uring_enable_rings(3) (#863 )
Fix a few other minor things up spotted while studying man pages
Normalize all "cancellation/cancelled" to "cancelation/canceled". This is kinda questionable in terms of churn. The former is our American spelling, the latter the British spelling. UNIX spelling quoth ECANCELED sides with the latter. If you'd rather not commit this, let me know and I'll pull it out of the PR.

git request-pull output:
The following changes since commit 2ea05c2a5750ff36a6ee4ce33f85e2989e91be5f:

  src/setup: minor style cleanups (2023-05-16 07:41:30 -0600)

are available in the Git repository at:

  https://github.com/dankamongmen/liburing dankamongmen/man

for you to fetch changes up to c6a68e3ebe0a14137756d6ffd2879770844b5b4f:

  man: add io_uring_enable_rings.3 (2023-05-31 08:57:06 -0400)

----------------------------------------------------------------
nick black (2):
      Settle on canceled/cancelation
      man: add io_uring_enable_rings.3

 man/io_uring_enable_rings.3        | 40 ++++++++++++++++++++++++++++++++++++++++
 man/io_uring_enter.2               |  2 +-
 man/io_uring_prep_link_timeout.3   | 16 ++++++++--------
 man/io_uring_prep_poll_add.3       |  2 +-
 man/io_uring_prep_timeout.3        |  2 +-
 man/io_uring_prep_timeout_update.3 |  2 +-
 src/include/liburing/io_uring.h    |  2 +-
 test/accept.c                      |  4 ++--
 test/defer.c                       |  6 +++---
 test/fpos.c                        |  2 +-
 test/io-cancel.c                   |  8 ++++----
 test/multicqes_drain.c             | 10 +++++-----
 test/poll-cancel.c                 |  4 ++--
 test/timeout.c                     |  2 +-
 14 files changed, 71 insertions(+), 31 deletions(-)
 create mode 100644 man/io_uring_enable_rings.3

Click to show/hide pull request guidelines
Pull Request Guidelines

To make everyone easily filter pull request from the email
notification, use [GIT PULL] as a prefix in your PR title.

[GIT PULL] Your Pull Request Title

Follow the commit message format rules below.
Follow the Linux kernel coding style (see: https://github.com/torvalds/linux/blob/master/Documentation/process/coding-style.rst).

Commit message format rules:

The first line is title (don't be more than 72 chars if possible).
Then an empty line.
Then a description (may be omitted for truly trivial changes).
Then an empty line again (if it has a description).
Then a Signed-off-by tag with your real name and email. For example:

Signed-off-by: Foo Bar<EMAIL_ADDRESS>
The description should be word-wrapped at 72 chars. Some things should
not be word-wrapped. They may be some kind of quoted text - long
compiler error messages, oops reports, Link, etc. (things that have a
certain specific format).
Note that all of this goes in the commit message, not in the pull
request text. The pull request text should introduce what this pull
request does, and each commit message should explain the rationale for
why that particular change was made. The git tree is canonical source
of truth, not github.
Each patch should do one thing, and one thing only. If you find yourself
writing an explanation for why a patch is fixing multiple issues, that's
a good indication that the change should be split into separate patches.
If the commit is a fix for an issue, add a Fixes tag with the issue
URL.
Don't use GitHub anonymous email like this as the commit author:
<EMAIL_ADDRESS>
Use a real email address!
Commit message example:
src/queue: don't flush SQ ring for new wait interface

If we have IORING_FEAT_EXT_ARG, then timeouts are done through the
syscall instead of by posting an internal timeout. This was done
to be both more efficient, but also to enable multi-threaded use
the wait side. If we touch the SQ state by flushing it, that isn't
safe without synchronization.

Fixes: https://github.com/axboe/liburing/issues/402
Signed-off-by: Jens Axboe<EMAIL_ADDRESS>

By submitting this pull request, I acknowledge that:

I have followed the above pull request guidelines.
I have the rights to submit this work under the same license.
I agree to a Developer Certificate of Origin (see https://developercertificate.org for more information).

I like making the cancel bits consistent, and it's a separate patch so good like that. Made a few comments on the other patch.

@dankamongmen ping on the above...

I finally gave up waiting on OP and pulled this, fixing up my complaints after the fact.


Connection failure

Expected behavior
The connection pool should perform good even under poor network condition
Actual behavior
many connection timeout be found in logs, all connections failed, however, not every key produce such error.
org.springframework.data.redis.RedisConnectionFailureException: Cannot get Jedis connection; nested exception is redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool Caused by: redis.clients.jedis.exceptions.JedisConnectionException: Could not get a resource from the pool
bellow is my pool configuration
redis.pool.maxActive=512 redis.pool.maxIdle=200 redis.pool.maxWait=1000 redis.pool.testOnBorrow=true
Steps to reproduce:
Don't know how to reproduce, restart application sometimes recover, but the pool would be broken after a while.
Redis / Jedis Configuration
Jedis version:
redis_version:2.6.10
Redis version:
Java version:
java 1.7

Jedis version: 2.4.0

@Gilbert2189 is there a chance you can upgrade Jedis? You're using a super old version which we are not supporting anymore.
Lots of connections bug fixes were added since 2.4

so this can be closed?

Let's close due to inactivity


thumbnails are missing

Generated markdown are with broken video images

It's giving a 404 right now, probably because of the Render.com hosting which has been noticeably slow and unreliable.
I'm looking for ways to fix it but it's not really getting anywhere yet.
I think I'll try moving it to another host soon or at some point.

Sorry for the downtime. Render is still not working for me. I'm trying to move the hosting, but updating the CNAME records can take a few hours to take effect.

As a temporary workaround, you can try setting the base_url to https://ytcards.vercel.app/.
Eventually ytcards.demolab.com will point to that domain, but this can take several hours to complete.
Once the DNS is fully propogated, it is recommended to use demolab as it will be more flexible if host changes are needed in the future.

What about accessing images directly?
https://i.ytimg.com/vi/<--Video ID-->/default.jpg
Image Size Weight 120px Height 90px
https://i.ytimg.com/vi/<--Video ID-->/mqdefault.jpg
Image Size Weight 320px Height 180px
https://i.ytimg.com/vi/<--Video ID-->/hqdefault.jpg
Image Size Weight 480px Height 360px
https://i.ytimg.com/vi/<--Video ID-->/sddefault.jpg
Image Size Weight 640px Height 480px
https://i.ytimg.com/vi/<--Video ID-->/maxresdefault.jpg
Image Size Weight 1280px Height 720px

The thumbnail is only part of the YouTube cards, the image also includes the duration, title, number of views, and relative time ago it was published dynamically

Should be temporarily fixed by #35 (temporarily made https://ytcards.vercel.app/ the default base url.
Will hopefully be changed back to demolab when that's working.
If you make a new workflow run, it should update and work correctly.

There were some configuration issues that needed to be resolved and it should be working on demolab also, as it used to.
(Now using Vercel as a host instead of Render)


1.21 update

I'm not opening this as a "please do this urgently" type of thing (even because 1.21 will be dropped officially only Thursday), instead just as a way to mark it's not compatible yet.

Any updates on this?

Any updates on this?

Working on 1.21.1 for Fabric and NeoForge.

Working on 1.21.1 for Fabric and NeoForge.

THANK YOU! THE GOAT IS BACK!!!!!

Working on 1.21.1 for Fabric and NeoForge.

please 1.21.4 too

Fixed in 1.21.1-0.4.0.  I am trying to find out the relative popularity of 1.21.4 to see if my time investment would pay off. ;)


Consider shortening the output

Currently in hand generated code there are tricks to make the code shorter and cleaner such as use of imports. A good example is the following:
https://github.com/scala-native/scala-native/blob/master/nativelib/src/main/scala/scala/scalanative/posix/dirent.scala
The keys points are the imports that eliminate the native. and Nat. prefixes. Also, in hand generated code the struct is just named dirent.

Related with https://github.com/kornilova-l/scala-native-bindgen/issues/32
The generated code is longer and more explicit by design to avoid having to keep track of whether declarations in the generated code shadows a declaration being imported.

It seems that you have already covered this issue. I hoped the native.XXX could be shortened to XXX. Also, there is an issue in Scala Native related. https://github.com/scala-native/scala-native/issues/1197

I think that it is a good idea.
Shorter code may be a default option since names in native and Nat are not common in C, but there also might be an option to generate code with all prefixes.
It will just take some time to make sure that bindgen always generates valid code.

Okay, let's keep it open, but I think we should give it pretty low priority for now since there are a lot of more important things to address.

I found another thing that might help. When functions are generated they are given parameter names as anonymous0, anonymous1, ... anonymousn. This could probably be p0, p1, ... pn for params.

I agree, I also do not like anonymous...


Add support of readonly user in custom bootstrap ldif

This PR adds support of readonly users attributes LDAP_READONLY_USER_USERNAME and LDAP_READONLY_USER_PASSWORD_ENCRYPTED to custom ldif scripts.

Thanks,
merged in 1.2.0 :)

Also merged in 1.1.11 :)


On Windows, incorrect link "All files »"

On Windows, when the resolved relative path for a source file contains more than one folder, then the link "All files »" is incorrect in the generated html report.
It appears that lib/report/html.js uses path.sep (\ on Windows) to tokenize node.relativeName, which would be something like path/to/source\ which should generate ../../../index.html as the href for the "All files »" link. But using \ as the path separator when trying to .split() something like path/to/source\ results in ['path/to/source', ' '], which leads to the creation of the incorrect href ../index.html.
So when viewing the coverage for path/to/source.js which is at path/to/source/index.html, the link "All files »" takes you to path/to/index.html (which doesn't exist) instead of index.html.
Below is an image with an example:

@gotwarlost this has long since been resolved. Might be closed for good.


Does not build on Android ARM

It unconditionally uses NEON it seems. Not all Android devices have NEON so we need to compile it in conditionally and detect at runtime.
libtool: compile:  arm-linux-androideabi-gcc -fuse-ld=gold -DHAVE_CONFIG_H -I. -DGRAPHENE_COMPILATION=1 -DG_LOG_DOMAIN="Graphene" -I../src -I../src -DGRAPHENE_ENABLE_DEBUG --sysroot=/home/jenkins/workspace/cerbero-android/workdir/android-ndk-r9d/platforms/android-9/arch-arm -I/home/jenkins/workspace/cerbero-android/workdir/android-ndk-r9d/platforms/android-9/arch-arm/usr/include -DANDROID -DPIC -D__ARM_ARCH_5__ -D__ARM_ARCH_5T__ -D__ARM_ARCH_5E__ -D__ARM_ARCH_5TE__ -O3 -ffast-math -fstrict-aliasing -I/home/jenkins/workspace/cerbero-android/workdir/dist/android_arm/include/glib-2.0 -I/home/jenkins/workspace/cerbero-android/workdir/dist/android_arm/lib/glib-2.0/include -fvisibility=hidden -I/home/jenkins/workspace/cerbero-android/workdir/dist/android_arm/include/glib-2.0 -I/home/jenkins/workspace/cerbero-android/workdir/dist/android_arm/lib/glib-2.0/include -Wall -Wshadow -Wstrict-aliasing=2 -Wno-uninitialized -Wcast-align -Wstrict-prototypes -Werror=logical-op -Werror=pointer-arith -Werror=missing-declarations -Werror=redundant-decls -Werror=implicit-function-declaration -Werror=format=2 -Werror=missing-include-dirs -Werror=init-self -Werror=empty-body -Werror=declaration-after-statement -mfpu=neon -Wall -g -Os --sysroot=/home/jenkins/workspace/cerbero-android/workdir/android-ndk-r9d/platforms/android-9/arch-arm -I/home/jenkins/workspace/cerbero-android/workdir/android-ndk-r9d/platforms/android-9/arch-arm/usr/include -ffunction-sections -funwind-tables -fstack-protector -no-canonical-prefixes -fPIC -mthumb -fomit-frame-pointer -fno-strict-aliasing -finline-limit=64 -march=armv5te -mtune=xscale -msoft-float -DANDROID -DPIC -D__ARM_ARCH_5__ -D__ARM_ARCH_5T__ -D__ARM_ARCH_5E__ -D__ARM_ARCH_5TE__ -Wa,--noexecstack -g -MT libgraphene_1_0_la-graphene-point.lo -MD -MP -MF .deps/libgraphene_1_0_la-graphene-point.Tpo -c graphene-point.c  -fPIC -DPIC -o .libs/libgraphene_1_0_la-graphene-point.o
graphene-alloc.c: In function 'graphene_alloc':
In file included from graphene-config.h:38:0,
from graphene-types.h:32,
from graphene-matrix.h:27,
from graphene-matrix.c:35:
/home/jenkins/workspace/cerbero-android/workdir/android-ndk-r9d/toolchains/arm-linux-androideabi-4.8/prebuilt/linux-x86_64/lib/gcc/arm-linux-androideabi/4.8/include/arm_neon.h:32:2: error: #error You must enable NEON instructions (e.g. -mfloat-abi=softfp -mfpu=neon) to use arm_neon.h
#error You must enable NEON instructions (e.g. -mfloat-abi=softfp -mfpu=neon) to use arm_neon.h

Works now, thanks :smile:


Add missing indexArray to server-side runtime.

Add missing indexArray to server-side runtime.
prevent cannot access property "length" of undefined when passing undefined to mapArray on the server

Looks good thanks.


Windows builds failing because of gitpython dependency

Applying the patches from Phabricator currently fails because of a broken dependency in the latest docker containers:
C:\ws\workspace\amd64_windows_vs2017\llvm-project>python C:\ws\workspace\amd64_windows_vs2017/llvm-premerge-checks/scripts/phabtalk/apply_patch2.py --comment-file C:\ws\workspace\amd64_windows_vs2017/build/.phabricator-comment  --token **** --url https://reviews.llvm.org 245836
Traceback (most recent call last):
  File "C:\ws\workspace\amd64_windows_vs2017/llvm-premerge-checks/scripts/phabtalk/apply_patch2.py", line 26, in <module>
    from git import Repo, GitCommandError
  File "C:\Python38\lib\site-packages\git\__init__.py", line 38, in <module>
    from git.exc import *                       # @NoMove @IgnorePep8
  File "C:\Python38\lib\site-packages\git\exc.py", line 9, in <module>
    from git.compat import UnicodeMixin, safe_decode, string_types
  File "C:\Python38\lib\site-packages\git\compat.py", line 16, in <module>
    from gitdb.utils.compat import (
ModuleNotFoundError: No module named 'gitdb.utils.compat'

So i disabled the build feedback in Phabricator:
https://reviews.llvm.org/harbormaster/step/view/4/

See https://github.com/gitpython-developers/GitPython/issues/983.

@Harmon758 thx for looking into this. Upgrading gitpython to 3.0.6 solves the problem.