Update PLY to SLY

dabeaz has rewritten PLY from scratch and modernized everything. The new project is called SLY. It has not hit a stable release yet. However, we should prepare for its stable release and begin our rewrite and refactor soon. More information about SLY on the project page:
https://github.com/dabeaz/sly

SLY requires the use of Python 3.6 or greater.  Older versions of Python are not supported.

This makes it unusable for me, at least for the time being. I'm not sold on the benefit of migrating just for the sake of it, especially if we lose Python 2 support in the process.

Dropping Python 2 support is a good thing in my opinion. I'm fine with waiting on this change, but there is a wall fast approaching that people need to get ready for. Perhaps we make this change a version 3.0 milestone. Version 1.x and 2.x would use PLY and keep maintenance releases until the death of Python 2. Also, I'm not recommending this for the sake of it. PLY may not be maintained after SLY is ready. I just took a class with dabeaz a few weeks ago and his recommendation is to switch to SLY.
https://pythonclock.org/
I like the quote on the docs site for requests:
"The use of Python 3 is highly preferred over Python 2. Consider upgrading your applications and infrastructure if you find yourself still using Python 2 in production today. If you are using Python 3, congratulations — you are indeed a person of excellent taste." —Kenneth Reitz

Looks like there's finally a release of SLY. I'll be looking at how to start the migration.

I've written a new core.py and objects.py that uses SLY.
There are still things to do, but it parses rulesets effectively using the lexing, parsing, and objects based on the official YARA project.
The basic parsing and function names are different enough that calling it plyara isn't accurate.
Would it be more appropriate to create a new slyara project?

Sounds like this is the logical successor. I have no objection to renaming this org/project, so all the old links still work. @utkonos you have owner-permissions here already, and I think you're in the best position to decide this. Let me know if you need anything from me, to update CI/docs or anything.

I have thought about renaming in conjunction with this, but I would like to think long and hard about it.
@malvidin Do you have these changes in a repo somewhere?
The goal I have with this update is to have the current unit tests pass with the new undercarriage. Also, I am going to be attending a training with dabeaz (PLY/SLY author) in about a week and a month. I want to get some insights about SLY from the horse's mouth so-to-speak.

Yes, I just pushed it here, https://github.com/malvidin/plyara/tree/slyara.
There is still things that are not finished.

tracking imports and externals in the condition
-- test_conditions can't find filename
-- test_detect_dependencies
-- test_detect_imports
condition_terms is not used
no JSON export of the rule (test_strings)
comments are not retained
raw sections are not retained
command_line isn't created.

Great! Thanks! I should have some time coming up to wrangle everything together.

@malvidin I would prefer not changing the name of the whole project just because the change in the upstream library. It would cause unnecessary confusion and require people to change their code. Can you make a PR with the SLY code to the SLY branch on plyara?
Also, with the changes made recently, the code coverage has gone down. One of my goals is to get the unit test coverage back up as high or higher than it was before the recent PR/s.

I have started the steps to build the new 3.0.0 version of plyara based on the SLY library. This is a from the ground up rewrite using a better paradigm of organization of the code. Each step is now separated by functionality. The first part I'm working on is the core data model. The next step will be the tokenizer based on SLY. After that, the export functionality. Three goals with the export functionality:

JSON file that matches the export from plyara 2.x
New JSON file that may conform to most or all of the 2.x JSON schema components but may deviate to address as many or all of the issues raised at the moment. This format should be informed by the official Go parser and yara-python.
Back to a valid YARA rule

I have a new branch for tracking this work here:
https://github.com/plyara/plyara/tree/prep-3.0
The last part will be the parser which may or may not be based on SLY. An alternative is a custom PEG parser.

Minor correction: I am working on the output of valid YARA rules along with the model. This functionality in the 2.x version of plyara can use the most improvement. Therefore I'm solving this problem first.
A good part of the model and output is implemented and correct. Each class and output has a prototype unit test as well.
Comments are more than welcome:
https://github.com/plyara/plyara/tree/prep-3.0

One decision that I've made is to use YARA documentation as the style guide for the output formatting.


Incorporate these changes:

https://github.com/reagent-project/reagent-template/commit/b0a0d61ae571c892cb0399f0d1d8f5435ec9e6ba

Changes included in #3.


Reproducible builds

Is your feature request related to a problem? Please describe.
The other day I tried to install the project on my node, following the installation guide and found the process a bit frustrating because I tried to set up an virtual environment to isolate the installation and its dependencies (to avoid conflicts with other python tools that I use in my node), and for tools like poetry or pipenv is hard to figure out a graph of dependencies without end up with bunch of version conflicts. Had to tweak the requirements.txt a little bit myself to make it work.
Describe the solution you'd like
I think tools like poetry or pipenv might be a good addition to the project along with the proper instructions on to install de dependecies using such tools.
Describe alternatives you've considered
As I said, I considered poetry and pipenv as dependency resolution tools, I prefer poetry because it is in active development and maintenance.
Additional context

Besides that, I didn't find a .gitignore file, wihch is very useful at the time to have a clean development environment.

Thanks for sharing this information, I will take note of this issue and also checkout your pullrequest. :)

Awesome, if you have questions, don't hesitate to ask. I like this tool a lot.


[Feature Enhancement] Quickinfo with Navigation links

Feauture added in Clickable QuickInfo with "go to type"
I really love this feature and I think we can take it a lot further than its initial implementation

Allow navigation to modules

Allow navigation to function bindings

Allow navigation to operator definitions (type or module)

Allow navigation to discriminated union and enum cases

Allow navigation to type members/methods/properties

In signatures link to other signatures, not implementation files

In implementation files link to other implementation files

(Eventually) allow navigation to external symbols via metadata signature generation

Some additional comments documenting the functionality would also be useful, especially in Quickinfo Provider.fs, just from looking at the source it's unclear how the navigation functionality works and where one should look to see it's implementation.  I'd already forgotten where it was by today and had to go digging back into the PR to find it.
cc @majocha , @cartermp, @smoothdeveloper

Thank you, @cloudRoutine. I have a small improvement to add so I'll write missing comments with it and also make it a bit less scattered.
The interesting stuff of the implementation is deep inside, true :) Searching all references to NavigableTaggedText helps here.
It builds on @vladima's titanic commit ed948aba. The idea is to piggyback some more info on top of the classified text in Layout that in the end is being used in quick info. I tried to identify places where types are laid out and pass navigational data there.
With this approach making more entities browsable is possible as long as the required data is available at the point the layout is created. I'll try to work on this.
Another thing that worth considering is using PreferProvisionalTab option. Currently it is buggy, causing occasional duplicate tabs :(
Navigating to .fs instead of .fsi looks hard. Currently EntityRef.DefinitionRange is used and it seems it always points to .fsi definition for referenced projects.

Couldn't you move quickinfo down in the compilation order, move the tooltip generation to a class method, construct the class with an MEF import on the gotodefinition class and then use that to handle the navigation?

We use PreferProvisionalTab in FSharpGoToDefinitionService and it works OK I think.

@majocha that small tooltip-for-tooltip should be colorized as well ;)

...and has links to navigate to, say, intermediate module... ;)

@vasily-kirichenko colorized and browsable, yes :)
I'm not sure what's going on with the ProvisionalTab. Should work.

@cloudRoutine I can try, but in the and GotoDefinition service also just calls TryNavigateToSpan.

@cloudRoutine Now I see that would be the correct approach. GoToDefinitionService sometimes blocks for quite some time, but that should not happen in our case. At the moment quick info shows up, the document is parsed and checked already.

Hey, right click / find all references could be useful too!

:)

@majocha I've addressed the speed issue in my generate metadata PR, so eventually that won't be a big deal

More entities allow navigation now. In the end there is no obstacle to make everything navigable,
but it doesn't always look nice:

GoToDefinitionService is used now but there is some repetition here I'm not happy with. Basically we give it the position we want to go to, because we already have it. The service makes an unnecessary roundtrip to look up the symbol and then navigates.
https://github.com/Microsoft/visualfsharp/compare/master...majocha:navigable-improvements

@majocha I'll PR some of the gotodef speed improvements I made onto your branch and try to get rid of that roundtrip

@cloudRoutine I don't think we can get rid of it because it's what GoToDefinitionService do, it looks up a definition.

@majocha I totally got rid of it ;) https://github.com/majocha/visualfsharp/pull/1

@majocha totally got rid of it https://github.com/majocha/visualfsharp/pull/1

Awesome! One minute because I was mucking around with it later and there's a conflict.

I think we can close it now?

@cartermp Close it?


proxy

any recomend for proxy sir? country and ISP

Working Proxies as of NOV 2024：https://app.proxiware.com $1.5 per residential proxy


GUI page does not respond to key events and does not adjust the focus

IMPORTANT: Before you create an issue, please take a look at our Issue Reporting Guide.
Briefly summarize your issue:

GUI page does not respond to key events and does not adjust the focus
What is the expected behavior?

While runing the sample app with the step on https://developer.amazon.com/en-US/docs/alexa/alexa-smart-screen-sdk/ubuntu.html on a PC . when I say that "show my to-do list"， Alexa will return a list page that shows my to-do list . Then , press the key ArrowDown , focus of the page will move to the first item and highlight it
What behavior are you observing?

When I built this to my own machine and open the index.html in the same way ,then I say "show my to-do list" and press the key
ArrowDown ,there's no thing happend . And after a while ,the websocket process crashed
Provide the steps to reproduce the issue, if applicable:

Tell us about your environment:

What version of the AVS Device SDK are you using?
  <2.6>

Tell us what hardware you're using:

[ ] Other - tell us more:linux development board with browser

Tell us about your OS (Type & version):

[ ] Linux

Have you tried the same use case with AVS Device SDK SampleApp?

[ ] The issue is not applicable to the AVS Device SDK SampleApp.

Here are some question I want to ask

[ ] First , I notice that the index.html import the file main.bundle.js，do I need other file to support this ?  Or some files need to be provided to the SDK process ?

Thanks a lot for reaching out. Upon verification with Alexa Smart Screen SDK 2.6, I am able to see focus on the page moving to the first item with highlight. Can you please share the core dump for the crash?
First , I notice that the index.html import the file main.bundle.js，do I need other file to support this ? Or some files need to be provided to the SDK process
main.bundle.js is a js bundle and should have all the dependencies included.

Thanks a lot,we have figured it out .But we find a new problem . We update the SDK version to 2.8, two new problems occured.
(1) press keydown to the fist item ，focus will move to it ,but in sample app ,there are two options at end of tje item ,but in our machine , there is no options .
(2)By using the chrome package on the https://developer.amazon.com/alexa/console/avs/preview/resources/details/SmartScreen SDK Voice Chrome Extension ,chrome is shown ,but it do not show the listening state ,just thinking, speaking and others, is it supported the listening state ？Cause the thinking state is showed correctly , I guess that is not a code error , have you ever got this and hava a solution ？
Wish to get your reply, thanks


Update tsconfig-paths dependency to v4

That would be a breaking change. Duplicate of #2447 and countless others.


Add time limit and reduce "boring" sections

I just played the game for a longer time, here some wishes:

increase click area (#4)
there is apparently no time limit, i.e. the game is endless and I just aborted it after getting bored. A time limit would be helpful to not let the player leave the game being bored
the game difficulty apparently does not increase, i.e. a lot of times it was just boring (just one customer asking for "stuff" and only one factory delivering it)
some customers never get fully dressed (this looks stupid, I constantly deliver products to 3 out of 4 customers and the forth still has only trousers on)

@hjacobs thanks! This makes a pretty definitive list of what needs to be done.
Regarding the last item, we also had an idea of placing all fully dressed customers in one line and replacing them with the fresh ones.

Hey @w0rm @aryszka @vigneshshanmugam @kolja, what's the status of this issue? Do you still agree with the suggestions? Have you implemented any/all of them? If there's work to be done within project scope, let's add a "Help Wanted" label.


Support for use with sub-modules

It would be really handy if pre-commit would also run scripts when repositories were used as submodules
http://stackoverflow.com/questions/10848191/git-submodule-commit-hooks
`git rev-parse --git-dir`/hooks

I have no idea how difficult this would be to implement.

Would be nice, but I don't know if should be default functionality. It might make sense to opt-in for in some way. Accepting pull requests for this as it's not really functionality that I would personally use.

I am stuck with a couple of sub-modules for awhile. I'll update this ticket, if I start working on it a PR.

What do you mean by submodules ?
Being able to npm test at the root and run others npm test in submodules ?
If so, i'm really interest and if someone implemented it, please let me know.

Any update on this?

I have found that when I include a git repository as a submodule of a another repository, that the hooks don't fire.
I have found that if I have a 'parent' repository A, and I include a submodule that is repository B then.

B does not have a folder .git
A has a folder .git/modules/B/ which looks like B's .git repository

I have found that when I include a git repository as a submodule of a another repository, that the hooks don't fire.
I have found that if I have a 'parent' repository A, and I include a submodule that is repository B then.
B does not have a folder .git
A has a folder .git/modules/B/ which looks like B's .git folder


Add jiwang576 as a reviewer for kfserving.

What this PR does / why we need it:
jiwang576 helps code reviews on PRs in tools/tf2openapi.

This change is

I signed it!

/cc ellisbigelow


Implement BasicObject#instance_exec and improve #instance_eval

I feel like the implementation to implement the scoping requirements of instance evaling code is quite brittle now, but I didn't have a better idea on how to implement this properly.
If you have any ideas about this let me know.

My instinct tells me this is going to bite us in the butt very soon, but I have absolutely nothing to back that up.
I will try to get a thorough read of the change tomorrow, because I don't think I've ever seen this part of the code before

https://github.com/natalie-lang/natalie/commit/7631c2826573a9c562a154aa1f570aa8f9d1b71e
I found the first commit a bit hard too read, since it tried to do two things.  I found this easier to read.
// block.hpp
void set_self(Value self) {
    m_original_self = m_self;
    m_self = self;
}

// object.cpp, in instance_eval
block->set_self(this);
// run the block
block->set_self(block->original_self());

This last line effectively swaps the values of m_original_self and m_self. This means the old context get preserved, and if we call a block a second time in an instance_eval context, we might end up with the wrong context:
class KlassWithSecret
  def initialize(secret)
    @secret = secret
  end
end
k99 = KlassWithSecret.new(99)
k77 = KlassWithSecret.new(77)
block = lambda do |obj|
  if obj == k99
    k77.instance_eval(&block)
  else
    @secret
  end
end
p k99.instance_eval(&block)
k77.instance_eval { p block.call(self) }

The output in MRI, JRuby and Truffleruby (all the latest stable versions) is 77 and nil, but Natalie with this branch returns 77 twice. If you remove the k99.instance_eval line, the output is nil for both runtimes.
My first  thought was to reset the m_self value instead:
// block.hpp
void restore_original_self() {
    m_self = m_original_self;
    m_original_self = nullptr;
}

And replace the line block->set_self(block->original_self()); with block->restore_original_self();. This prints 77 only once, but that's because it terminates with a segfault before it can print the second value. So I guess we need a stack of selfs.

Mh I feel like having nested instance_evals will break the current implementation nonetheless, because after executing the inner instance_eval we will reset GlobalEnv::the()->instance_evaling()  and the code executed afterwards thinks it will not be in an instance evaluation. Maybe one way to refactor this is implementing a stack of instance eval contexts on the global env. One of those context objects could hold the env in which instance_eval was called and the original self of the block. This way we could eliminate the "original self" on the block and the caller()->caller() hack. What do you think?

@herwinw @seven1m I quickly implemented the idea that I described earlier. Now the script from @herwinw prints the same value in MRI and in Natalie! Let me know what you think about this solution!

Nice!


gnome-keyring requirement for Linux not mentioned in README

Hi!
For a long time we couldn't launch our app on Arch Linux because we didn't know that gnome-keyring is required for the libsecret to work.
Only with the latest release we got the proper error log, and I think that this requirement should be mentioned in "Configure Linux Version" section of README to avoid other's frustration.

gnome-keyring is not required at all. What is required is application that runs as secret service (provides dbus interface for that). I'm running mine with keepassxc and works quite fine.
In other words:

you need dbus session (also mentioned in #464)
secret store provider app (gnome-keyring, kde waller, keeassxc, pass-secret-store or other)

I may revisit statement above as someone mentioned that might be required as libsecret before certain version uses gnome-keyring protocol instead of new generic secret protocol. I was checking gnome-keyring-daemon 0.42.1 and that seem not work well together.
Seems like only specific combination of libsecret and gnome-keyring would work.

@inexcode can you tell with what versions you found working combination?

@inexcode can you tell with what versions you found working combination?

Not sure now, all I can tell is that we used libsecret 0.20.5 in our flatpak builds.

I am closing all older issues. If this issue still exists in the latest version, please let me know.


Misleading variable names in Icinga 2 API feature

As already discussed 'in real life' there are some variables with misleading names.
The variable ca_host inside the API feature for example is incorrect from an Icinga 2 technical point of view, as the "parent host" must be specified here in a distributed system with satellites. Naming to parent_host or similar would be more suitable.
Other examples are ca_host_port  and icinga2_delegate_to.
As @mkayontour said, we need to make sure to have a transition phase for that. We could deprecate them and remove them in future versions.

The way this feature works, ca_host is the correct name to go with, in my opinion, as the collection will indeed default to delegating the certificate creation to the ca_host.


add methods for getting diagnostics report to health endpoint

https://jira.mesosphere.com/browse/QUALITY-1819
Corresponding dcos PR https://github.com/dcos/dcos/pull/2485

Currently broken because it needs to be updated to use the ARNodeApiClientMixin.


Binary responses?

Have you figured out a way to output binary responses (like dynamic images, etc.)?
Last time I looked, API Gateway can be configured to pass through anything from upstream, but Lambda will only return JSON-formatted responses (i.e. no binary responses without base64-encoding, which couldn't be decoded on API Gateway at the time).

Based on my experience, the response from an AWS solutions architect would be to write your dynamic image or binary data to a bucket on S3 from within the Lambda function and have information about that binary file be returned within the JSON response from Lambda.

@mojodna I believe (though I may be wrong) that you are limited to serving JSON.  API Gateway was just released last month.  AWS is very competitive, I hope that they can allow this because being able to serve dynamic static assets would be so damn cool :+1:
Please let me know if you see them offering this somehow.  I want to hack with it asap.

@mojodna - I'm proposing a slightly different architecture in issue #25, which would address your challenge as you can return binary data.

@hj1980 You're right!  I'm going to publish a JAWS Road Map this weekend.  In there, I'll suggest to incorporate more of your architecture, especially for special use-cases like this one.  Perhaps we can include the AWS Javascript Browser SDK in the JAWS site boilerplate and add some simple examples for common use-cases (like the one above).  Since you're familiar with this architecture already, perhaps you can help with this part and provide some awesome boilerplate code?


Failures during ngcc postinstall interrupt ng update

This issue impacts 9.0.0-rc.0 and happened while updating https://github.com/johannesjo/super-productivity.
One of the migrations during the update to version 9 will add a postinstall script to the project that runs ngcc. If ngcc fails to process a package, the update process will fail.
This is problematic for a couple of reasons:

a user should be able to update to version 9 and use VE instead even if ngcc cannot process a library
there's no point during the update process where a user can stop the postinstall hook from being added
it only takes one of these libraries to wholly prevent a user from using ng update
some libraries might need to be updated to be ngcc-compatible, but the update guide instructs users to update Angular before updating the libraries
it will also prevent ng add from functioning properly, and due to i18n changes we instruct users to run ng add @angular/localize

kamik@RED-X1C6 MINGW64 /d/sandbox/super-productivity (update-9)
$ ng update @angular/cli @angular/core --next --force
The installed Angular CLI version is older than the latest published version.
Installing a temporary version to perform the update.
Installing packages for tooling via npm.
C:\Users\kamik\AppData\Local\Temp\.ng-temp-packages-Xmt0sz\ng -> C:\Users\kamik\AppData\Local\Temp\.ng-temp-packages-Xmt0sz\node_modules\@angular\cli\bin\ng

><EMAIL_ADDRESS>postinstall C:\Users\kamik\AppData\Local\Temp\.ng-temp-packages-Xmt0sz\node_modules\@angular\cli
> node ./bin/postinstall/script.js

+<EMAIL_ADDRESS>added 254 packages from 205 contributors in 17.661s
Installed packages for tooling via npm.
Using package manager: 'npm'
Collecting installed dependencies...
Found 87 dependencies.
Fetching dependency metadata from registry...
                  Package "@angular/core" has a missing peer dependency of "tslib" @ "^1.10.0".
                  Package "@ngx-translate/core" has an incompatible peer dependency to "@angular/core" (requires ">=7.0.0", would install "9.0.0-rc.0").
                  Package "@angular/common" has a missing peer dependency of "tslib" @ "^1.10.0".
                  Package "@ngx-translate/http-loader" has an incompatible peer dependency to "@angular/common" (requires ">=7.0.0", would install "9.0.0-rc.0").
                  Package "@angular/animations" has a missing peer dependency of "tslib" @ "^1.10.0".
                  Package "@angular/forms" has a missing peer dependency of "tslib" @ "^1.10.0".
                  Package "@ngx-formly/core" has an incompatible peer dependency to "@angular/forms" (requires ">=7.0.0", would install "9.0.0-rc.0").
                  Package "@angular/compiler" has a missing peer dependency of "tslib" @ "^1.10.0".
                  Package "@angular/platform-browser" has a missing peer dependency of "tslib" @ "^1.10.0".
                  Package "@angular/compiler-cli" has a missing peer dependency of "tslib" @ "^1.10.0".
                  Package "@angular/service-worker" has a missing peer dependency of "tslib" @ "^1.10.0".
                  Package "@angular/platform-server" has a missing peer dependency of "tslib" @ "^1.10.0".
                  Package "@angular/router" has a missing peer dependency of "tslib" @ "^1.10.0".
                  Package "@angular/platform-browser-dynamic" has a missing peer dependency of "tslib" @ "^1.10.0".
    Updating package.json with dependency @angular/cli @ "9.0.0-rc.0" (was "8.3.17")...
    Updating package.json with dependency @angular/core @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/common @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/animations @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/forms @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/language-service @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/compiler @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/platform-browser @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/compiler-cli @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/service-worker @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/platform-server @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/router @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular/platform-browser-dynamic @ "9.0.0-rc.0" (was "8.2.9")...
    Updating package.json with dependency @angular-devkit/build-angular @ "0.900.0-rc.0" (was "0.803.4")...
    Updating package.json with dependency zone.js @ "0.10.2" (was "0.9.1")...
    Updating package.json with dependency typescript @ "3.6.4" (was "3.5.3")...
UPDATE package.json (6816 bytes)
√ Packages installed successfully.
** Executing migrations of package '@angular/cli' **

>  Update an Angular CLI project to version 9.

** Executing migrations of package '@angular/core' **

>  Static flag migration.
   Removes the `static` flag from dynamic queries.
   As of Angular 9, the "static" flag defaults to false and is no longer required for your view and content queries.
   Read more about this here: https://v9.angular.io/guide/migration-dynamic-flag
UPDATE src/app/ui/inline-markdown/inline-markdown.component.ts (5025 bytes)
UPDATE src/app/ui/inline-input/inline-input.component.ts (1595 bytes)
UPDATE src/app/core/banner/banner/banner.component.ts (1728 bytes)
UPDATE src/app/features/tasks/task/task.component.ts (18537 bytes)
UPDATE src/app/features/bookmark/bookmark-bar/bookmark-bar.component.ts (3188 bytes)
UPDATE src/app/features/note/note/note.component.ts (1314 bytes)
√  Migration succeeded.

>  Missing @Injectable migration.
   In Angular 9, enforcement of @Injectable decorators for DI is a bit stricter.
   Read more about this here: https://v9.angular.io/guide/migration-injectable
√  Migration succeeded.

>  ModuleWithProviders migration.
   In Angular 9, the ModuleWithProviders type without a generic has been deprecated.
   This migration adds the generic where it is missing.
   Read more about this here: https://v9.angular.io/guide/migration-module-with-providers
√  Migration succeeded.

>  NGCC postinstall migration.
   Adds an ngcc invocation to npm/yarn's postinstall script.
    Please add a generic type argument to the ModuleWithProviders type. If this occurrence is in library code you don't control, please contact the library authors.

    at ClusterWorker.compile (D:\sandbox\super-productivity\node_modules\@angular\compiler-cli\ngcc\src\main.js:170:27)
    at Worker.<anonymous> (D:\sandbox\super-productivity\node_modules\@angular\compiler-cli\ngcc\src\execution\cluster\worker.js:41:42)
    at Worker.emit (events.js:198:13)
    at process.Worker.process.on (internal/cluster/worker.js:28:12)
    at process.emit (events.js:198:13)
    at emit (internal/child_process.js:832:12)
    at process._tickCallback (internal/process/next_tick.js:63:19)
    at ClusterMaster.onWorkerMessage (D:\sandbox\super-productivity\node_modules\@angular\compiler-cli\ngcc\src\execution\cluster\master.js:158:27)
    at D:\sandbox\super-productivity\node_modules\@angular\compiler-cli\ngcc\src\execution\cluster\master.js:46:95
    at ClusterMaster.<anonymous> (D:\sandbox\super-productivity\node_modules\@angular\compiler-cli\ngcc\src\execution\cluster\master.js:238:57)
    at step (D:\sandbox\super-productivity\node_modules\tslib\tslib.js:136:27)
    at Object.next (D:\sandbox\super-productivity\node_modules\tslib\tslib.js:117:57)
    at D:\sandbox\super-productivity\node_modules\tslib\tslib.js:110:75
    at new Promise (<anonymous>)
    at Object.__awaiter (D:\sandbox\super-productivity\node_modules\tslib\tslib.js:106:16)
    at EventEmitter.<anonymous> (D:\sandbox\super-productivity\node_modules\@angular\compiler-cli\ngcc\src\execution\cluster\master.js:232:32)
    at EventEmitter.emit (events.js:198:13)
Compiling @ngx-formly/material/radio : es2015 as esm2015
Compiling @ngx-formly/material/checkbox : es2015 as esm2015
Compiling @ngx-formly/material/multicheckbox : es2015 as esm2015
Compiling @angular/cdk/drag-drop : es2015 as esm2015
Compiling @ngx-formly/material/select : es2015 as esm2015
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>postinstall: `ngcc --properties es2015 browser module main --first-only --create-ivy-entry-points`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>postinstall script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\kamik\AppData\Roaming\npm-cache\_logs\2019-11-01T16_51_17_783Z-debug.log
× Package install failed, see above.
The update failed. See above.
git HEAD was at 85f08a4d93e684566f751e38e2a2feffe0194cd9 before migrations.
×  Migration failed. See above for further details.

Closed via https://github.com/angular/angular-cli/pull/16145 and https://github.com/angular/angular/pull/33727.


v1.15 Backports 2024-12-03

[ ] #35697 (@learnitall)

Once this PR is merged, a GitHub action will update the labels of these PRs:
 35697

/test-backport-1.15


Adding back proxypool param as it is in code

the parameter proxypool is still in the code for the cmdlet
however it should not be used.
https://github.com/MicrosoftDocs/office-docs-powershell/issues/3946

Docs Build status updates of commit 574111b:
:clock10: Full build: the average full build time is 14 min(s) 25 sec(s), this is based on the last 1000 build(s) for this repository.

Docs Build status updates of commit 574111b:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

skype/skype-ps/skype/Move-CsUser.md
:white_check_mark:Succeeded
View (skype-ps)

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


CMakeLists.txt file is missing in Extern/ImGuiFileDialog

Describe the bug
configuration for building rayx gives an error:
To Reproduce

get newest version via git: git pull --recurse-submodules
start clean build in visual code: cmake: "Clean Reconfigure All Projects"

Expected behavior
Configurations ends up with no errors
Screenshots
Instead it stops here:
[cmake] -- Found Python: /usr/bin/python3.10 (found version "3.10.12") found components: Interpreter
[cmake] CMake Error at Extern/CMakeLists.txt:6 (add_subdirectory):
[cmake]   The source directory
[cmake]
[cmake]     /home/usrename/RAY/RAY-X/Extern/ImGuiFileDialog
[cmake]
[cmake]   does not contain a CMakeLists.txt file.
[cmake]
[cmake]
[cmake] CMake Error at Extern/CMakeLists.txt:8 (target_include_directories):
[cmake]   Cannot specify include directories for target "ImGuiFileDialog" which is
[cmake]   not built by this project.
[cmake]
[cmake]
[cmake] -- Configuring incomplete, errors occurred!
Desktop (please complete the following information):

Ubuntu 22.04

Additional context
CMakeLists.txt file is missing in my folder

Maybe this is also necessary?..
git submodule update --init --recursive

Additional context
CMakeLists.txt file is missing in my folder

Does git status also show this file as removed?
If yes, do git checkout -- CMakeLists.txt to get it back.


Add new proxy types

Description

This PR adds two new proxy types: Transfer and SmallTransfer.
The Transfer proxy allows only Balances::transfer_* extrinsics including keep alive, allow death, and transfer all.
The SmallTransfer proxy only allows transfers for amounts below SMALL_TRANSFER_LIMIT which is set to 0.5 TAO
These new proxy types help to make key management more flexible. By allowing more proxy types such as these one can separate the responsibility of different keys instead of using the parent key, potentially exposing all operations.
An example setup is to have key A use the existing staking proxy type and key B use the transfer type. And then if A becomes compromised an attacker may only stake/unstake. If B becomes compromised, an attacker may only transfer free-balance (i.e. excluding any stake). Thereby reducing the attack surface, while allowing keys to be used in otherwise "hot" deployments.
Type of Change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update
[ ] Other (please describe):

Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have run cargo fmt and cargo clippy to ensure my code is formatted and linted correctly
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Additional Notes
Please provide any additional information or context that may be helpful for reviewers.

Needs spec bump


[GF_Cyrillic_Core] language + speakers redefinition - adding languages

This pull request updates the definition of GF_Cyrillic_Core based on languages and the number of speakers (from 3,000,000 onwards).
Following the cross-reference to update Cyrillic Plus (see #227), some languages with a large number of speakers were identified as candidates that should be included in this glyph set, redefining it by the specified range.
cc @yanone, @moyogo

@yanone, same comment as in #227. We can merge this here and then, if necessary, update with the additional data definitions per glyphset if we identify some extra glyphs needed.


Will this repository continue to keep up to date with the latest version camunda?

I'm currently working with camunda, and i chose this nuget package Camunda.Api.Client to deal with rest api request.But when i use interface related to UserTask, i found that some interfaces was not provided by this nuget package. Such as /task/{id}/bpmnError, /task/{id}/bpmnEscalation and some others.
Am i using the code with a wrong way ? Or is this nuget package just  out of date?

Please see #91


Problem when loading MultiverseCore

I have this problem when I run my server. It is under Paper 1.8.8.
https://hastebin.com/sidiqiheli.sql

MC 1.8.x You will need to use an even older version of Multiverse - 2.5 should work (not the same as 2.5.0): https://dev.bukkit.org/projects/multiverse-core/files/898527


Move the mimimal port of elliptic library to its own repository.

The minimal port of  elliptic is located at secretk/src/commonMain/kotlin/io/eqoty/crypto/elliptic/

moved to https://github.com/eqoty-labs/kryptools


[Snyk] Upgrade @aws-sdk/client-secrets-manager from 3.410.0 to 3.450.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @aws-sdk/client-secrets-manager from 3.410.0 to 3.450.0.
As this is a private repository, Snyk-bot does not have access. Therefore, this PR has been created automatically, but appears to have been created by a real user.
:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 21 versions ahead of your current version.
The recommended version was released 22 days ago, on 2023-11-13.

Release notes

Package name: @aws-sdk/client-secrets-manager

3.450.0 - 2023-11-133.450.0(2023-11-13)
Documentation Changes

fix typo in client template (#5476) (c24b638e)

New Features

clients:  update client endpoints as of 2023-11-13 (74076a84)
client-transcribe-streaming:  This release enables customers to call the AWS Transcribe streaming service with the capability of identifying multiple languages in the stream. (09ffb2ad)
client-emr:  Updated GetClusterSessionCredentials API  to allow Amazon SageMaker Studio to connect to EMR on EC2 clusters to support IdentityCenter/PEZ integration. (0b470534)
client-ec2:  Adds the new EC2 DescribeInstanceTopology API, which you can use to retrieve the network topology of your running instances on select platform types to determine their relative proximity to each other. (ce5a2b07)
client-database-migration-service:  Added new Db2 LUW Target endpoint with related endpoint settings. New executeTimeout endpoint setting for mysql endpoint. New ReplicationDeprovisionTime field for serverless describe-replications. (0f12860e)
client-dataexchange:  Removed Required trait for DataSet.OriginDetails.ProductId. (de1396a7)
client-ecs:  Adds a Client Token parameter to the ECS RunTask API. The Client Token parameter allows for idempotent RunTask requests. (2cbe6552)
client-service-catalog-appregistry:  When the customer associates a resource collection to their application with this new feature, then a new application tag will be applied to all supported resources that are part of that collection. This allows customers to more easily find the application that is associated with those resources. (5364e1dc)

For list of updated packages, view updated-packages.md in assets-3.450.0.zip

3.449.0 - 2023-11-103.449.0(2023-11-10)
Chores

add package entrypoints enforcement script (#5468) (657c9adf)

Documentation Changes

client-rds:  Updates Amazon RDS documentation for zero-ETL integrations. (ec1318c4)
client-fms:  Adds optimizeUnassociatedWebACL flag to ManagedServiceData, updates third-party firewall examples, and other minor documentation updates. (aae5cdde)

New Features

client-marketplace-entitlement-service:  Add paginators to GetEntitlements. (18d6d947)
client-controltower:  AWS Control Tower supports tagging for enabled controls. This release introduces TagResource, UntagResource and ListTagsForResource APIs to manage tags in existing enabled controls. It updates EnabledControl API to tag resources at creation time. (360b88a2)
client-cost-and-usage-report-service:  This release adds support for tagging and customers can now tag report definitions. Additionally, ReportStatus is now added to report definition to show when the last delivered time stamp and if it succeeded or not. (1f24b222)
client-ec2:  EC2 adds API updates to enable ENA Express at instance launch time. (b4b5fdd5)
client-mediaconvert:  This release includes the ability to specify any input source as the primary input for corresponding follow modes, and allows users to specify fit and fill behaviors without resizing content. (b8924baf)

For list of updated packages, view updated-packages.md in assets-3.449.0.zip

3.445.0 - 2023-11-073.445.0(2023-11-07)
Chores

codegen:

update smithyVersion to 1.40.0 (#5462) (aa2e38fd)
bump codegen version to 0.19.0 (#5450) (5538f3be)

New Features

clients:  update client endpoints as of 2023-11-07 (46616b4f)
client-dlm:  Added support for pre and post scripts in Amazon Data Lifecycle Manager EBS snapshot lifecycle policies. (eafa4171)
client-dataexchange:  Updated SendDataSetNotificationRequest Comment to be maximum length 4096. (8292e07d)
client-rds:  This Amazon RDS release adds support for the multi-tenant configuration. In this configuration, an RDS DB instance can contain multiple tenant databases. In RDS for Oracle, a tenant database is a pluggable database (PDB). (c28ec75c)

Bug Fixes

cloudfront-signer:  add tslib (#5460) (54cc5c4b)
core:  add tslib (#5459) (35a1aed1)

For list of updated packages, view updated-packages.md in assets-3.445.0.zip

3.441.0 - 2023-11-013.441.0(2023-11-01)
Chores

client-sqs:  create coercing serializers for awsQueryCompat (#5440) (88213abe)

New Features

client-rds:  This release adds support for customized networking resources to Amazon RDS Custom. (0c0921a9)
client-global-accelerator:  Global Accelerator now support accelerators with cross account endpoints. (e4aa35f2)
client-connect:  Adds the BatchGetFlowAssociation API which returns flow associations (flow-resource) corresponding to the list of resourceArns supplied in the request. This release also adds IsDefault, LastModifiedRegion and LastModifiedTime fields to the responses of several Describe and List APIs. (6e0eda33)
client-sagemaker:  Support for batch transform input in Model dashboard (1725b9ce)
client-redshift:  Added support for Multi-AZ deployments for Provisioned RA3 clusters that provide 99.99% SLA availability. (1ef476e4)
lib-dynamodb:  large number handling (#5427) (4c7fe9cf)

For list of updated packages, view updated-packages.md in assets-3.441.0.zip

3.438.0 - 2023-10-27

3.437.0 - 2023-10-26

3.436.0 - 2023-10-25

3.435.0 - 2023-10-24

3.433.0 - 2023-10-20

3.432.0 - 2023-10-19

3.431.0 - 2023-10-18

3.430.0 - 2023-10-17

3.429.0 - 2023-10-16

3.428.0 - 2023-10-12

3.427.0 - 2023-10-06

3.425.0 - 2023-10-04

3.423.0 - 2023-10-02

3.421.0 - 2023-09-27

3.418.0 - 2023-09-22

3.414.0 - 2023-09-15

3.413.0 - 2023-09-14

3.410.0 - 2023-09-11

    from @aws-sdk/client-secrets-manager GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

already changed on the recent PR merge. Hence Closing this PR


Add aarch64-musl binaries to release artifacts

Would it be possible to add a statically linked aarch64-musl binary as a release artifact? The x86_64 version already has a musl release binary available. Does this just require another entry in .github/workflows/CICD.yml? Happy to contribute the changes!

Sure, please do


llmblock: Set a more reasonable default for num_tokens

97cee87 llmblock: Set a more reasonable default for num_tokens
commit 97cee87606e7d04a8277dd315d30f9c8b4652cc7
Author: Russell Bryant<EMAIL_ADDRESS>Date:   Thu Jul 11 22:17:10 2024 -0400
llmblock: Set a more reasonable default for num_tokens

This parameter is part of the OpenAI API for creating a chat
completion.

https://platform.openai.com/docs/api-reference/chat/create#chat-create-max_tokens

In our default flows, we configure many LLMBlocks explicitly to use
`max_tokens` of 2048, but many do not have it set and rely on the
default here.

In some testing with vllm, it was observed that this caused a
significant performance hit to vllm's cache. A value this high is
unnecessary, as we have observed that most of our responses are closer
to 2k, anyway.

A follow-up to this would be to look closer at which blocks we are
explicitly setting to use 2k, and which we are allowing to use the
larger default. It's not clear to me if they are all intentional or
not. Tracked via #126.

This change originally comes from https://github.com/aakankshaduggal/sdg/pull/3/commits/04e33982dd8fba05f52700a9eedccdb115609e80

Co-authored-by: shiv<EMAIL_ADDRESS>Co-authored-by: Aakanksha Duggal<EMAIL_ADDRESS>Co-authored-by: Kai Xu<EMAIL_ADDRESS>Signed-off-by: Russell Bryant<EMAIL_ADDRESS>

pushed an update, but it only updated the commit message


Update Zone for Nat Gateway

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR has modified HISTORY.rst describing any customer-facing, functional changes. Note that this does not include changes only to help content. (see Modifying change log).

[ ] I adhere to the Command Guidelines.

@tjprescott yup, same NRP api version

@tjprescott yup, same NRP api version

@khannarheams, didn't you need to bump up the api version to 2019-04-01. Don't you need this newer api-version for this feature?

@khannarheams the API change has been merged. You should rebase your PR on top of that.

@tjprescott  https://github.com/Azure/azure-cli/pull/9575 created new PR


How to use native audio

Hello
First of all, thanks for providing this plugin.
No matter what I do it loads the WebAudioProvider from the factory. I have installed cordova-plugin-media. I have tried with both ionic view app and building with xcode.
Any ideas?

@sjosen Have you built the demo project included? Is it not working with native audio either?

I get native audio with Android and html audio in iOS. Html audio is working fine though, so perhaps it doesn't matter. I was just wondering :)

I haven't had the chance to test on iOS. Still having trouble?
Just upgraded the module to Ionic 2 final.  See http://arielfaur.github.io/ionic-audio/2.0/index.html

Is this still occurring? Otherwise can we close this issue?

I can test it soon. I can open a new issue if it's still a problem


Creating a sub_log does not respect the initial log level

Given the folllowing code:
let my_log = Dream.sub_log ~level:`Error "my.log"

let () =
  Dream.run
  @@ Dream.logger
  @@ Dream.router
       [ Dream.get "/" (fun _ -> Dream.html "Welcome to my website")
       ; Dream.get "/echo/:word" (fun req ->
           my_log.warning (fun log -> log ~request:req "echo path");
           Dream.html (Printf.sprintf "Hello, %s" @@ Dream.param req "word"))
       ]
;;

I expect that echo path will not be logged, as it is a warning, and this sub_log is only configured with errors.
However, it is still being logged:
15.09.23 10:00:58.532       dream.log  INFO REQ 1 GET /echo/dream <IP_ADDRESS>:45198 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/51
15.09.23 10:00:58.532          my.log  WARN REQ 1 echo path
15.09.23 10:00:58.532       dream.log  INFO REQ 1 200 in 87 μs

"Manually" setting the log level with the following line:
let () = Dream.set_log_level "my.log" `Error

Makes it behave as expected:
15.09.23 10:03:37.447       dream.log  INFO REQ 1 GET /echo/dream <IP_ADDRESS>:33510 Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/51
15.09.23 10:03:37.447       dream.log  INFO REQ 1 200 in 56 μs

I am running OCaml 4.14.1 under WSL2

Thank you! This has been fixed in the linked commit and will be out in the next release.
The whole logging initialization code could probably use a rework, as it was already complex when only trying to integrate with Logs, but it is now even more complex because of Mirage support, and it's difficult to follow.


chore(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/event-notifications/ibm (source)
module
patch
1.3.1 -> 1.3.2

terraform-ibm-modules/kms-all-inclusive/ibm (source)
module
minor
4.8.5 -> 4.9.1

Release Notes

terraform-ibm-modules/terraform-ibm-event-notifications (terraform-ibm-modules/event-notifications/ibm)
v1.3.2
Compare Source
Bug Fixes

deps: update terraform ibm to latest for the deployable architecture solution (#181) (3cb09f9)

terraform-ibm-modules/terraform-ibm-kms-all-inclusive (terraform-ibm-modules/kms-all-inclusive/ibm)
v4.9.1
Compare Source
Bug Fixes

deps: update terraform ibm to latest for the deployable architecture solution (#457) (1c1a350)

v4.9.0
Compare Source
Features

added a region dropdown to the DA in catalog- renamed existing_resource_group to use_existing_resource_group- renamed existing_kms_guid to existing_kms_instance_crn and now ask for CRN instead of GUID. (#454) (b70f698)

v4.8.7
Compare Source
Bug Fixes

deps: update module to require >= 1.64.0 ibm provider to pull in fix for https://github.com/IBM-Cloud/terraform-provider-ibm/issues/5154 - service_endpoints now defaults to private for the DA solution  (#453) (05d1ff1)

v4.8.6
Compare Source
Bug Fixes

deps: update terraform ibm to latest for the deployable architecture solution (#449) (4968957)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

:tada: This PR is included in version 1.6.1 :tada:
The release is available on:

GitHub release
v1.6.1

Your semantic-release bot :package::rocket:


Bugs with native postgresql enums

Describe the bug
I'm testing out the new native postgresql enums and I have encountered a few problems.
1. down migration doesn't drop type
Native enums still get non-native alter table "table_name" drop constraint if exists "nonexistent_check_constraint" instead of a drop type statement.
This also makes it hard to roll back and then roll forward since you'll get an error that the type already exists:
$ yarn mikro-orm migration:up
$ yarn mikro-orm migration:down
$ yarn mikro-orm migration:up
DriverException: create type "user_role" as enum ('Member', 'Admin'); - type "user_role" already exists

And apparently create type doesn't accept an if not exists clause so we can't work around it that way.
2. Can't convert non-native enum with a default to native enum
Trying to convert a non-native enum with a default (i.e. it is a text column with a constraint) will result in this SQL:
    this.addSql('create type "org_plan" as enum (\'Free\', \'Business\', \'Enterprise\');');
    this.addSql('alter table "org" alter column "plan" type "org_plan" using ("plan"::"org_plan");');

Which will result in this error:

DriverException: alter table "org" alter column "plan" type "org_plan" using ("plan"::"org_plan"); - default for column "plan" cannot be cast automatically to type org_plan

AFAIK, we have to use drop default and then set default:
    this.addSql('alter table "org" alter column "plan" drop default;');
    this.addSql('create type "org_plan" as enum (\'Free\', \'Business\', \'Enterprise\');');
    this.addSql('alter table "org" alter column "plan" type "org_plan" using ("plan"::"org_plan");');
    this.addSql('alter table "org" alter column "plan" set default \'Free\';');

This also has to be done in the down migration otherwise the column type will be text but the default will be the enum type (I didn't think this was possible but it is).
Take this property:
enum OrgPlan {
  Free = 'Free',
  Business = 'Business',
  Enterprise = 'Enterprise',
}

@Entity()
export class Org {
  // ... stuff omitted ...

  @Enum({
    nativeEnumName: 'org_plan', // <--- this line was added for the migration
    items: () => OrgPlan,
    default: OrgPlan.Free,
  })
  plan: OrgPlan = OrgPlan.Free;
}

Running migration:create creates the following migration:
export class Migration20240109192818_ConvertOrgPlanToNativeEnum extends Migration {

  async up(): Promise<void> {
    this.addSql('alter table "org" drop constraint if exists "org_plan_check";');

    this.addSql('create type "org_plan" as enum (\'Free\', \'Business\', \'Enterprise\');');
    this.addSql('alter table "org" alter column "plan" type "org_plan" using ("plan"::"org_plan");');
  }

  async down(): Promise<void> {
    this.addSql('alter table "org" drop constraint if exists "org_plan_check";');

    this.addSql('alter table "org" alter column "plan" type text using ("plan"::text);');
    this.addSql('alter table "org" add constraint "org_plan_check" check ("plan" in (\'Free\', \'Business\', \'Enterprise\'));');
  }

}

But this is what we need:
export class Migration20240109192818_ConvertOrgPlanToNativeEnum extends Migration {

  async up(): Promise<void> {
    this.addSql('alter table "org" drop constraint if exists "org_plan_check";');

    this.addSql('alter table "org" alter column "plan" drop default;');
    this.addSql('create type "org_plan" as enum (\'Free\', \'Business\', \'Enterprise\');');
    this.addSql('alter table "org" alter column "plan" type "org_plan" using ("plan"::"org_plan");');
    this.addSql('alter table "org" alter column "plan" set default \'Free\';');
  }

  async down(): Promise<void> {
    this.addSql('alter table "org" alter column "plan" drop default;');
    this.addSql('alter table "org" alter column "plan" type text using ("plan"::text);');
    this.addSql('alter table "org" add constraint "org_plan_check" check ("plan" in (\'Free\', \'Business\', \'Enterprise\'));');
    this.addSql('alter table "org" alter column "plan" set default \'Free\';');

    this.addSql('drop type "org_plan";');
  }

}

3. Rollback issue when adding to an enum
Take this example, adding SelfHosted to the enum above:
export class Migration20240109203600_AddSelfHostedOrgPlan extends Migration {

  async up(): Promise<void> {
    this.addSql('alter type "org_plan" add value \'SelfHosted\';');
  }

  async down(): Promise<void> {
    // this is wrong but does not break things
    this.addSql('alter table "org" drop constraint if exists "org_plan_check";');
  }

}

If you try to roll back and then migrate again you will get this error:
$ yarn mikro-orm migration:up
$ yarn mikro-orm migration:down
$ yarn mikro-orm migration:up
DriverException: alter type "org_plan" add value 'SelfHosted'; - enum label "SelfHosted" already exists

Adding if not exists to the alter type statement will fix this issue.
4. Can't remove values from the enum
Since PostgreSQL does not allow removals from types, this may be considered an intended limitation. But there are ways to work around it, and other frameworks do implement this.
By renaming the existing type and creating the new type, we will be able to remove an entry from the enum.
export class Migration20240109204535_RemoveEnterpriseOrgPlan extends Migration {

  async up(): Promise<void> {
    this.addSql(`alter type "org_plan" rename to "org_plan_old"`);
    this.addSql(`create type "org_plan" as enum('Free', 'Business')`);
    this.addSql(`alter table "org" alter column "plan" drop default;`);
    this.addSql(`alter table "org" alter column "plan" type "org_plan" using "plan"::"text"::"org_plan";`);
    this.addSql(`alter table "org" alter column "plan" set default 'Free';`);
    this.addSql('drop type "org_plan_old";');
  }

  async down(): Promise<void> {
    this.addSql(`create type "org_plan_old" as enum('Free', 'Business', 'Enterprise')`);
    this.addSql(`alter table "org" alter column "plan" drop default;`);
    this.addSql(`alter table "org" alter column "plan" type "org_plan_old" using "plan"::"text"::"org_plan_old";`);
    this.addSql(`alter table "org" alter column "plan" set default 'Free';`);
    this.addSql('drop type "org_plan";');
    this.addSql(`alter type "org_plan_old" rename to "org_plan"`);
  }

}

This should preferably only be used when removing things from the enum, because using this for adding to the enum may make the migration unnecessarily expensive if the table is very very large. I think adding to a type is super cheap the way it is now.
Not the end of the world if this wasn't supported in mikro-orm.
5. Should multiple columns be able to use the same type?
This might be overkill but wouldn't it be cool if you could use the same type for both of these columns?
enum UserRole {
  Member = 'Member',
  Admin = 'Admin',
}

@Entity()
export class Org {
  // ... stuff omitted ...

  @Enum({
    nativeEnumName: 'user_role',
    items: () => UserRole,
    default: UserRole.Member,
  })
  defaultUserRole: UserRole = UserRole.Member;
}

@Entity()
export class User {
  // ... stuff omitted ...

  @Enum({
    nativeEnumName: 'user_role',
    items: () => UserRole,
    default: UserRole.Member,
  })
  role: UserRole = UserRole.Member;
}

Right now it will try to create the type twice, which will fail.
If this was allowed then the user would run into trouble when attempting to remove one of the columns.
Reproduction
I hope the code above is enough to repro. Please let me know if any of it is unclear.
What driver are you using?
@mikro-orm/postgresql
MikroORM version
6.0.1
Node.js version
v18.19.0
Operating system
No response
Validations

[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Slack.
[X] The provided reproduction is a minimal reproducible example of the bug.

Thanks for the write-up, I should have spent more time testing this, heh.

Ok, I guess I've addressed most of this, exceptions are removing of type values and removing types, that can come later. Let me know how it works.


README: describe environement variable for running tests locally

The test suite checks if the GeoServer version is read correctly. The value has to be provided via an environment variable. This is done in the CI automatically. But for running the tests locally it is necessary to set it manually.
export GEOSERVER_VERSION=2.20.1

@chrismayer true, your suggestion is a bit shorter and sufficient for this purpose


Services page : Navigation issue after opening connection config page

Affected module
UI
Describe the bug
On Services page, if we navigate to connection config and try to navigate back , the UI is stuck on the connection config page.
To Reproduce

Navigate to services page from Settings drop-down
Click on connection config
Navigate back using the back button in browser
UI shows connection config tab

https://user-images.githubusercontent.com/67048554/157179667-e21a421f-aff9-4e30-898d-f209dba138c5.mp4
Expected behavior
On navigating back the previous page should be displayed
Version:

OpenMetadata version: 0.9.0

Additional context
NA

@darth-coder00 @Sachin-chaurasiya @ShaileshParmar11


Item 57: Minimize the scope of local variables

Minimize the accessibility of classes and members.” By minimizing the scope of local variables, you increase the readability and maintainability of your code and reduce the likelihood of error.
Highlights

[x] Powerful Technique
[x] Local Variable Initialization
[x] Loop Variable Declaration
[ ] Final Technique

Powerful Technique
Older programming languages like C mandated local variables to be declared at the head of the block and some programmers continue to do that. As a gentle reminder, Java lets you to declare variables anywhere the statement is legal as does C. since C99

The most powerful technique for minimizing the scope of a local variable is to declare it where it is first used.

Disadvantages

If a variable is declared before it is used, it’s just clutter

One more thing to distract the reader who is trying to figure out what the program does. By the time the variable is used, the reader might not remember the variable’s type or initial value.

Declaring a local variable prematurely can cause its scope not only to begin too early but also to end too late.

The scope of a local variable extends from the point where it is declared to the end of the enclosing block. If a variable is used accidentally before or after its region of intended use, the consequences can be disastrous.

Local Variable Initialization

Nearly every local variable declaration should contain an initializer.

If you don’t yet have enough information to initialize a variable sensibly, you should postpone the declaration until you do.
Exceptional Case

One exception to this rule concerns try-catch statements.

If a variable is initialized to an expression whose evaluation can throw a checked exception, the variable must be initialized inside a try block (unless the enclosing method can propagate the exception). If the value must be used outside of the try block, then it must be declared before the try block, where it cannot yet be “sensibly initialized.”

Loop Variable Declaration
Loops present a special opportunity to minimize the scope of variables. The for loop, in both its traditional and for-each forms, allows you to declare loop variables, limiting their scope to the exact region where they’re needed.

Prefer for loops to while loops

The region consists of the body of the loop and the code in parentheses between the for keyword and the body. Assuming the contents of the loop variable aren’t needed after the loop terminates. As while loop requires the variable to be declared prior before checking the condition of the loop to run.
Ref - 7ae04ef

Final Technique

To minimize the scope of local variables is to keep methods small and focused.

If we combine two activities in the same method, local variables relevant to one activity may be in the scope of the code performing the other activity. To prevent this from happening, simply separate the method into two: one for each activity.

The important thing to notice about this idiom is that it has two loop variables, i and n, both of which have exactly the right scope. The second variable, n, is used to store the limit of the first, thus avoiding the cost of a redundant computation in every iteration.
Ref - 62e7ea8


Branch ppp

Codecov Report

Merging #266 (37b1913) into master (628de7b) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #266   +/-   ##
=========================================
  Coverage     50.66%   50.66%
  Complexity      606      606
=========================================
  Files           107      107
  Lines          2556     2556
  Branches        297      297
=========================================
  Hits           1295     1295
  Misses         1195     1195
  Partials         66       66

Continue to review full report at Codecov.

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


[Components] Button integration

https://zeroheight.com/1186e1705/v/latest/p/34b742-button/b/32e1a2


Please invite me to the GitHub Community Organization

Name
spiderman
Discord Username (if applicable)
spiderman
Additional Context
Hello, I want to join your team.
I am a senior frontend & web3 developer with high skills and rich experience.

It's great having you contribute to this project
If you would like to continue contributing to open source and would like to do it with an awesome inclusive community, you should join our Discord Server and our GitHub Organisation - we help and encourage each other to contribute to open source little and often 🤓 . Any questions let us know.

Invitation sent for the GitHub Organisation. Welcome to the community 🎉#
Don't forget after accepting to make it public so it appears on your GitHub profile for everyone else to see, you can do this by finding your name in the GitHub organisation list and change the dropdown to public https://github.com/orgs/jaidevstudio/people
Like this

Tips for practising:
Remember contributing to open source is not just about code, its about collaboration, communication and adding value
I hope that helps

Please check your email or organisation page 🙏


Running balance not calculating properly.

Name of Defective Feature

Running Balance

System Settings (Required)

ToolKit Version: 2.7.1
Operating System (Mac/Windows/Etc): Winows 10
Browser (Chrome/Firefox/Safari): Chrome
Browser Version: 67.0.3396.79
Other Extensions:

Export of Toolkit Settings (Bottom Left of Settings Page)

Settings Export
[{"key":"AccountsDisplayDensity","value":"1"},{"key":"AccountsEmphasizedOutflows","value":false},{"key":"AccountsStripedRows","value":true},{"key":"AdditionalColumns","value":true},{"key":"AdjustableColumnWidths","value":true},{"key":"AutoDistributeSplits","value":false},{"key":"BetterScrollbars","value":"2"},{"key":"BudgetCategoryFeatures","value":true},{"key":"BudgetProgressBars","value":"0"},{"key":"BudgetQuickSwitch","value":false},{"key":"CalendarFirstDay","value":"0"},{"key":"CategoryActivityCopy","value":false},{"key":"CategoryActivityPopupWidth","value":"0"},{"key":"ChangeEnterBehavior","value":false},{"key":"CheckCreditBalances","value":true},{"key":"CheckNumbers","value":false},{"key":"ClearSelection","value":false},{"key":"CollapseSideMenu","value":true},{"key":"ColourBlindMode","value":false},{"key":"CompactIncomeVsExpense","value":true},{"key":"CreditCardEmoji","value":true},{"key":"CurrentMonthIndicator","value":false},{"key":"CustomFlagNames","value":false},{"key":"DaysOfBuffering","value":false},{"key":"DaysOfBufferingHistoryLookup","value":"0"},{"key":"DisableToolkit","value":false},{"key":"DisplayTargetGoalAmount","value":"0"},{"key":"DisplayTotalMonthlyGoals","value":false},{"key":"DisplayUpcomingAmount","value":false},{"key":"EasyTransactionApproval","value":false},{"key":"EditAccountButton","value":"2"},{"key":"EnableRetroCalculator","value":false},{"key":"EnlargeCategoriesDropdown","value":true},{"key":"EnterToMove","value":false},{"key":"GoalIndicator","value":false},{"key":"GoalWarningColor","value":true},{"key":"GoogleFontsSelector","value":"0"},{"key":"HideAccountBalancesType","value":"0"},{"key":"HideAgeOfMoney","value":false},{"key":"HideHelp","value":false},{"key":"HideReferralBanner","value":true},{"key":"HighlightNegatives","value":true},{"key":"ImportNotification","value":"2"},{"key":"IncomeFromLastMonth","value":"0"},{"key":"IncomeVsExpenseHoverHighlight","value":true},{"key":"LargerClickableIcons","value":false},{"key":"MonthlyNotesPopupWidth","value":"0"},{"key":"NavDisplayDensity","value":"2"},{"key":"Pacing","value":"0"},{"key":"PrintingImprovements","value":true},{"key":"PrivacyMode","value":"0"},{"key":"QuickBudgetWarning","value":false},{"key":"ReconciledTextColor","value":"0"},{"key":"RemovePositiveHighlight","value":false},{"key":"RemoveZeroCategories","value":false},{"key":"ResizeInspector","value":false},{"key":"RightClickToEdit","value":true},{"key":"RowHeight","value":"1"},{"key":"RowsHeight","value":"0"},{"key":"RunningBalance","value":"1"},{"key":"SeamlessBudgetHeader","value":false},{"key":"ShowCategoryBalance","value":false},{"key":"ShowIntercom","value":true},{"key":"SpareChange","value":false},{"key":"SplitKeyboardShortcut","value":true},{"key":"SplitTransactionAutoAdjust","value":false},{"key":"SquareNegativeMode","value":true},{"key":"StealingFromFuture","value":false},{"key":"SwapClearedFlagged","value":false},{"key":"TargetBalanceWarning","value":false},{"key":"ToBeBudgetedWarning","value":false},{"key":"ToggleMasterCategories","value":false},{"key":"ToggleSplits","value":false},{"key":"ToggleTransactionFilters","value":"0"},{"key":"TransactionGridFeatures","value":true},{"key":"ViewZeroAsEmpty","value":false},{"key":"goalIndicator","value":false},{"key":"highlightNegativesNegative","value":true},{"key":"l10n","value":"0"},{"key":"pacing","value":"0"},{"key":"popupCalculator","value":false},{"key":"reports","value":true}]

Steps to Reproduce the Behavior

Open an account view;
Make some of the entries cleared and others not cleared;
The calculation of the running balance is wrong.

Expected Behavior

Running balance properly calculated considering all the entries, cleared or not.
Actual Behavior

The running balance is miscalculated.

I too am seeing weirdness with running totals.  Here is an example.  Notice how it appears to calculate all the debits before applying the credit on a day with both...

Also having this issue. Looks like the running balance is filling in from the top down instead of bottom up per date.

Same issue - Running Balance incorrect.
The left hand menu showing all accounts displays the correct running balance, but the column added by the toolkit showing the running balance is miscalculated and shows incorrect figure.

Hey @avcandre the fix for this should be in our current release! If you notice the issue still exists and you're definitely running the newest version of the toolkit, please reopen! Thanks!
Please note, all browser can take up to an hour to provide updates to all users. You can force an update if it's available for you by going to chrome://extensions and clicking the "Update" button. Firefox users can go to about:addons, click the setting cog, and click "Check for updates...".


dlopen failed: cannot locate symbol "aligned_alloc"

Why can I run on Android 10 and 9 and report an exception on 7.1.1? Is it an Android version problem？

Hi @Asssssert, Could you please provide the steps to reproduce the above error. Thanks!

I refered to your official documentation for step-by-step production, gesture recognition and pose recognition both have the same error. I downloaded the SDK as setup_android_sdk_and_ndk.sh script. I looked at my local SDK and saw that the platforms version was 29, I changed it to 25 and recompiled but the system reported other errors. My current development environment is：
ubuntu 20.04 for windows
python 3.8
bazel 3.7.2
I found a few examples of errors running on version 7.1 for some users.

Hi @jiuqiant I download your example and reported the same error on android version 7.1.1

https://en.cppreference.com/w/cpp/memory/c/aligned_alloc is introduced in C++17. I guess Android 7 (released in 2016) is a little bit old?

Hi @Asssssert, Take a look at the above comment

Thanks, as I have a couple of demos that work on Android 7.1, I was wondering why there was a problem, so have you considered adapting to Android 7, which I feel is used by quite a lot of people.

We have Prerequisite documentation.

Hi Asssssert, Could you please respond to my above comment. Thanks!

Hi @sgowroji  , Sorry I missed your message. When I was reading the prerequisites documentation, I didn't notice "Setup Android SDK release 28.0.3 and above".
I would recommend that you consider compatibility with lower versions.


Add initial column API functions

Goal
This PR aims just to add the start of a basic API related to enhancing support for the column. So we want to be able have some basic functions for creating columns, for knowing that they are columns, and what's in them.
Solution Overview
The PR adds a new namespace/api: tablecloth.column.api. As @genmeblog said, this separate API can help provide a "separation between dataset operations vs column operations."
Within this new namespace, we start with these functions:

column - creates a column from a vector or list
column? - determines whether an item is a column or not
typeof - returns the data type of the column's elements
typeof? - check to see if elements match a datatype
zeros - returns a column filled with zeros
ones - returns a column filled with ones

The ideas behind this small set of functions are as follows:

We are basically creating a new API for columns whereas up until now tablecloth has been only about the dataset.
We want to be able to create a column independently of a dataset, hence column. This gives the column some independence.
Since we have an independent column, we should be able to identify that an item is a column, hence column?.
Columns are uniformly typed entities (unless they are mixed in which case they are uniformly filled with :object). So we should be able to identify the datatype of the column's elements: typeof. This naming mimics R's vectors.
From numpy & matlab, we take the function names zeros & ones for functions that can fill a column with some values.

How to test
There's a test suite add with this PR @ test/tablecloth/column/api/column_test.clj.

Take look to see if they tests are making sense
Run tests: lein midje tablecloth.column.api.column-test

[ ] confirm tests pass

@genmeblog per our discussion I changed the target for this PR to be a new dev branch: ethan/column-api-dev-branch-1.

@genmeblog this is an interesting idea:

The other option to create a column whould be use a dummy dataset. It will pass then all of the inference patterns we need. Something like:
(-> (dataset {:some-name [1 2 3]}) :some-name)

I know we'd discussed this in relation to one way of supporting 2-d columns. Can you explain what you are referring to by "inference patterns"?

@genmeblog I'm going to merge this PR into the column API dev branch. I want to address the types in a separate PR. For the moment, I don't see a problem with type inference on the new-column function, so sticking with that for now. See discussion on that latter issue here: https://github.com/scicloj/tablecloth/discussions/74


TAA rendering pipeline: Fix ghosting issues at start

See https://forum.babylonjs.com/t/taa-with-aces-and-fixed-background/52972/5

Please make sure to label your PR with "bug", "new feature" or "breaking change" label(s).
To prevent this PR from going to the changelog marked it with the "skip changelog" label.

Snapshot stored with reference name:
refs/pull/15514/merge
Test environment:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15514/merge/index.html
To test a playground add it to the URL, for example:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15514/merge/index.html#WGZLGJ#4600
Links to test babylon tools with this snapshot:
https://playground.babylonjs.com/?snapshot=refs/pull/15514/merge
https://sandbox.babylonjs.com/?snapshot=refs/pull/15514/merge
https://gui.babylonjs.com/?snapshot=refs/pull/15514/merge
https://nme.babylonjs.com/?snapshot=refs/pull/15514/merge
To test the snapshot in the playground with a playground ID add it after the snapshot query string:
https://playground.babylonjs.com/?snapshot=refs/pull/15514/merge#BCU1XR#0

WebGL2 visualization test reporter:
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15514/merge/testResults/webgl2playwright/index.html

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15514/merge/testResults/webgpuplaywright/index.html

Visualization tests for WebGPU (Experimental)
https://snapshots-cvgtc2eugrd3cgfd.z01.azurefd.net/refs/pull/15514/merge/testResults/webgpuplaywright/index.html


pio install-plugin

A good way to handle install plugins (which is more than pip, ex: moving/editing config files around). What should it do?
pio install-plugin <plugin> --version <v> --from-url <url>

--from-url for installing from git repos

Initial bits are there, but needs lots of error handling


Updated UserGuide

Task parameters changed
Added taskcal and taskdone commands into the guide

Coverage remained the same at 62.041% when pulling ec663060f5a8d2f6c18f8ea9e66b748615d27f48 on cchj1995:Documentation into 7bebda620c72e280ce247c6af71c6d46fb8be4fd on CS2103-AY1819S2-W17-2:documentation.


changing the size of book

The size is quite huge -> align it to smaller + all the books to same size

Hey @legendarykamal can I work on this issue?

sounds nice, go ahead @aigerimmmm
how to start is mentioned in the readme , good luck :+1:


#20765 use  name for nullable data types

You can suggest another name instead of <undefined>
For tester: ask me about the database to check

 tells nothing about what is undefined. I'd prefer I little bit longer, but clearer: unknown type

Verified

Verified


JSON API Method to update the job's progress

Hello all,
Thank for this awesome tool. I have patched the code in order to modify with JSON API the jobs's progress
Sorry i feel unconfortable with git so I copy/paste my code here.
In ./lib/http/routes/json.js
/**
 * Update job :id :frames :totalFrames.
 */

exports.updateProgress = function(req, res){
  var id = req.params.id
    , frames = req.params.frames , totalFrames = req.params.totalFrames;

  Job.get(id, function(err, job){
    if (err) return res.send({ error: err.message });
    job.progress(frames, totalFrames);
    job.save(function(err){
      if (err) return res.send({ error: err.message });
      res.send({ message: 'updated Progress' });
    });
  });

};

And in ./lib/http/index.js
app.put('/job/:id/progress/:frames..:totalFrames', provides('json'), json.updateProgress);

Here an example:
curl -X PUT "http://domain:port/job/163/progress/1200..3000"
Sorry for my english.

@behrad I don't agree with you. It's very useful feature.
Right now JSON API is completely unuseful and it's sad. Kue as a stand-alone (micro-)service is much more preferable than just a nodejs module. And it's simple to move Kue this way - just make JSON API more powerful.


updated secret for private docker registry credentials

Changed secret for private docker registry. With 'regcred' its not able to pull images from private azure registry.

@vyshali-chitikeshi  can you update your commit message to follow conventional commits? Thanks!

Updated PR title


Engineering CRS

The CityGML 2 specification allowed to define an engineering CRS as CityModel metadata property (Example G.9, pp. 301, Building_LOD1-LocalEngineeringCRS.gml). Will this still be possible in CityGML 3?

We discussed this issue at the web conference on 17 May 2019.
We did not come to a conclusion whether this will still be possible, because GML 3 does not provide the metadata property any more. We will ask Clemens on this issue.
Furthermore, we are not sure if any software exists that could handle engineering CRS. Thus, is it in that case still necessary to include engineering CRS?

Engineering CRS would be helpful for BIM-GIS integration. I believe that geometry with higher levels of detail such as the interior of buildings which is originally given in a geo-referenced cartesian coordinate system should not be converted to geographic coordinate systems and could cause integration problems.
If there are externally defined canonical engineering CRS with different units of measurement, then it  would not be necessary to define these CRS inline, but reference by URI would be sufficent.

We did not come to a conclusion whether this will still be possible, because GML 3 does not provide the metadata property any more.

In order to do this with the latest GML version, a property "engineeringCRS" should be added to CityModel, with the corresponding type from ISO 19111, and the tagged value "isMetadata" on this property should be set to "true".

In the modelling subgroup meeting on 21 October 2019 we agreed on implementing this issue in the way suggested by Heidi.


difftastic: 0.56.1 -> 0.57.0

Signed-off-by: Muhammad Falak R Wani<EMAIL_ADDRESS>Description of changes
Diff: https://github.com/wilfred/difftastic/compare/0.56.1...0.57.0
Changelog: https://github.com/Wilfred/difftastic/blob/0.57.0/CHANGELOG.md

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.05 Release Notes (or backporting 23.05 and 23.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

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

Works for me with cargoHash = "sha256-y2e1EV0q+bQaZc5i8ztBM6Ex1qIglVlTHZU373aY/Oc=";

Setting this PR to draft until all the feedback comments are resolved.


Chinese Growth fails pytest -- after a long time

I found this while trying to reinstall the Econ-ARK virtual machine.  I guess the reason we haven't noticed it before is that we have somewhere excluded Chinese Growth from our tests, but that exclusion does not get incorporated when the tests are done by the automated
pytest --nbval-lax Chinese-Growth line that gets executed in the
finish scripts.
Is there a better version of the pytest command that would incorporate any future exclusions or caveats we make that allow the automated tests to work?
Chinese-Growth-Fails.txt

The fail is because of individual cell timeout. The second last cell in the notebook takes 2.5 hours to execute locally on my machine, and successfully creates this plot.

You can increase the timeout with something like
pytest --nbval-lax --nbval-cell-timeout=144000

Ok, I have a theory:  when I execoit natively on my machine it takes like 5
min.  My guess is that it is massively memory intensive but my machine has
64gb so that’s not a problem.  But Linux VM might have 4gb of which only 2
is overhead, so everything gets done on disk.
I guess this tells us that the machines that do the tests on GH are well
endowed.
But is there a simple way to exclude it from testing except on gh?
On Sun, Sep 12, 2021 at 8:41 AM Mridul Seth @.***>
wrote:

The fail is because of individual cell timeout. The second last cell in
the notebook takes 2.5 hours to execute locally on my machine, and
successfully creates this plot.
[image: Screenshot 2021-09-12 at 14 35 36]
https://user-images.githubusercontent.com/5363860/132987944-479cab02-531f-492a-a55f-3440eb3116e2.png
You can increase the timeout with something like
pytest --nbval-lax --nbval-cell-timeout=144000
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/econ-ark/DemARK/issues/163#issuecomment-917628817,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKCK77U5VRKAOV3ICBAZUTUBSNYJANCNFSM5DNWL4KA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

--
Sent from Gmail Mobile


updatehub: Create updatehub recipe

Create updatehub recipe with cargo-bitbake. The cargo-bitbake tool
generate all dependecies to applications development in rust language.
Signed-off-by: Luan Rafael Carneiro<EMAIL_ADDRESS>

This PR replaces the PR number #65 (ba2171da)

Please upgrade this recipe using the latest version.

Updated but still not tested. Wait for validation.


Update code of isValidHttpurl() in util.js

[x] Updated Simplified version of the previous code of isValidHttpurl()

We don't need to check the protocol property of the URL object explicitly, as the constructor automatically assigns a default value of "http:" to the protocol property if the input string doesn't specify one. Therefore, we can rely on the constructor to set the protocol property correctly and simply return true if no error occurs.

Thanks for the PR! However, as stated in the stackoverflow post, your code will incorrectly match urls like javascript:void(0)

The function is only used when checking if we must use the fetch method (if file system disabled or it is an HTTP url) or whether we must load from a local file (in node)
So, is there a reason you would need to load non-HTTP urls?

Oh alrightyyy got it!
Loved the repo imma keep tryna best to contribute 🚀🫡


Geo works don't all have iiif thumbnails

Vector and raster works don't have iiif thumbnails. Image works probably do.
https://github.com/pulibrary/plum/blob/9688451be22ee54e08bda8bd418b474049321208/app/controllers/catalog_controller.rb#L26

Thumbnails and representative images aren't appearing on the show page (including image works show pages). Partial overrides?


Typo "Azure Cosmos explorer"→"Azure Cosmos DB Explorer"

https://docs.microsoft.com/en-us/azure/cosmos-db/configure-synapse-link

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

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


Mccalluc/update readme

@pkerpedjiev : Biggest question for me is whether the whole file preparation section could be replaced with a reference to Clodius?

I think replacing the file preparation section with a reference to the clodius wiki should be fine. Only file upload belongs in higlass - server.


"Load More" feedback

When there are no more bounties to load, there should be feedback that lets a user know they have reached the last bounty when they click the "Load More" button at the bottom of the page.

we have toast notifications for this now


MapAdapter.build does not flatten list value from plain dict

It should be possible to pass a list value to a custom URL converter when building. However, after some other changes to the code to support MultiDict, a regression was introduced that made that difficult.
This changes the behavior so flattening single-item lists only happens when passing MultiDict, where values will always be lists, and are mainly coming from request.args where this behavior makes sense. For plain dicts, neither of these things are done, it is assumed that the user will intentionally pass a list or single item depending on what's appropriate.
Additionally, build no longer filters None items from list values. Either the list will be passed to a URL converter, where it's the converter's job to handle the value passed to it, or it's a query arg, and url_encode already filters out None.
fixes #2249
continues #2261

🎉 Yeah!


adding a license

👋 hello!
Would you consider adding a license? MIT is most common for tree-sitter grammars but for the sake of packaging, just about any license will do. (Disclaimer: I am not a lawyer)
Thanks!

Added license in #27


Live chat for support?

So, a glutin user pointed this out to me (@slmjkdbtl), that winit has no channel for real time chatting, which is something that, I feel, is better suited for providing support to users than filing an issue.
I could setup a freenode-matrix-gitter triplet like I did for glutin if you folks are interested. Users can hop onto whichever of the three they are more conformable with and their traffic gets relayed to the other two channels.
The channels would likely be #glutin-winit for freenode (since I already own #glutin-*) #Winit:matrix.org for matrix and ZeGentzy/winit for Gitter.
Alternatively (and this is what I'd prefer), we could share the existing channels for glutin between both projects as the channels will probably be really low traffic and users have a hard time as-it-is distinguishing glutin issues from winit ones.

I'd not be against any of these solutions.
If glutin's chatroom is indeed low-traffic, it may make sens to unite them, given there is indeed a large set of interactions between the two projects.

Closing this now that #818 has been merged.


[Diag] [Typechecker] Diagnose throw in defer properly

The body of a defer statement is an implicit FuncDecl, but that's implementation detail and it shouldn't leak into diagnostics. For example, we end up emitting an incorrect diagnostic when using a throw in a defer:
defer { throw Foo.bar } // error is not handled because the enclosing function is not declared 'throws'

Treat throw the same way we treat other control flow statements, like return, break & yield when used inside a defer.

cc @xedin

@swift-ci please smoke test and merge

@theblixguy Looks like there is a problem in verifier.

@xedin Hmm this makes sense since we're backing out of error type checking if we're in a defer body. I have fixed it now. Could you trigger the test again? Should be all good!

@swift-ci please smoke test and merge

@swift-ci please smoke test and merge

@swift-ci please smoke test

@xedin Could you trigger the CI again? Had to make a small change! Thank you!

@swift-ci please smoke test

Unrelated build failure:

15:10:35 The following build commands failed:
15:10:35 	PhaseScriptExecution Install\ Swift\ compiler\ resources /Users/buildnode/jenkins/workspace/swift-PR-osx-smoke-test/branch-master/buildbot_incremental/lldb-macosx-x86_64/lldb.build/CustomSwift-Release/LLDB.build/Script-49DD45051B4EDB4A00DB3579.sh

@swift-ci please smoke test macOS platform

Seems like the bots are not working correctly today 😅

We'll just have to wait until that's cleared, unfortunately...

No problem!

Okay, let's give the tests one more try. @xedin can you invoke the CI?

@swift-ci please smoke test

@swift-ci please smoke test

All tests have passed 🙏 🎉

Ok, great! Let's run source compatibility just in case...

@swift-ci please test source compatibility

@swift-ci please test source compatibility

Hmm I don't think the source compat test ran (or maybe the CI screwed up) 🤔

Problem accessing /job/swift-PR-source-compat-suite/2695/. Reason:
Not Found

@swift-ci please test source compatibility


rebuild for python3.12 + libpq16

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

Applies python 3.12 + libpq16 migrations to 2.x.x branch.
Anybody have thoughts on if 2.x.x should be added to abi migration so that it continues to receive migrations?  psycopg 2 and psycopg 3 are not compatible and can live side-by-side, so folks like me will be running both into the foreseeable future as I work through migrating various code bases....

@conda-forge-admin please rerender

Thanks @akrherz!

CI seems to be getting hit pretty hard these days.  I'll put the automerge label on and we'll see how it goes...

Thanks @xylar , sorry about embedding my question above in the PR, but you have thoughts about adding an abi migration branch to main for this?   I'd be happy to PR it, of course.

@akrherz, I see, I did miss that.  Feel free to make a PR to main to add 2.x.x to migrations.


Integrate faker-cli in faker-ruby organization

Checklist

[ ] Update README.md
[ ] Update README.md in faker-core to mention this repository

I'm deleting this repository since we're going to use the original fakerbot repository.
We basically wanted to keep the stars and watchers @stympy


Improve folder structure

We will have multiple associated services in our repo next to the connector, e.g. registration service for DID functionality.
I suggest to update the folder structure in a way that makes it easier to understand, which code belongs to which service.
Proposal:
/docs                       overall docs
/common                     shared libs, like the service loading framework
/services                   all services that form the connector ecosystem
e.g.
/services/connector         the connector itself :-)
/services/did-registration  registration service that crawls ION network
/services/catalog           ...

each service can have the following subfolders
.../core                core business functionality of the service
.../launcher            one or more bundles / launchers
.../scripts             e.g. helm charts
.../extensions          extensions that can get bundled
.../interfaces (or spi) extension interfaces

What do you think?
 Moritz Keppler<EMAIL_ADDRESS>Daimler TSS GmbH, legal info/Impressum

+1

I think that's great idea. What do you think about restructuring the extension directory, too?
It would be nice if the directory structure would show which part of the system is extended.
Examples:

/filesystem/configuration-fs -> /configuration/filesystem
/filesystem/vault-fs -> /vault/filesystem
/aws/s3/provision -> /transfer/provision/aws/s3
/aws/s3/s3-schema -> /schemas/aws/s3
/azure/transfer-process-store-cosmos -> transfer/store/azure-cosmos
/azure/vault -> /vault/azure

Would it be fine when I create a draft pull-request with these changes?