Add support for inclusion of RestKit as a Clang Module

Maintains support for the use of vendored dependencies inside the main Xcode project itself, rather than using subprojects.
@blakewatters this is necessary to support the use of RestKit as a proper framework via CocoaPods.

I've opened an issue: https://github.com/aharren/LibComponentLogging-Core/issues/26
Looks like the implicit transformation of #includes to an import breaks the X macros for the log components.

It's the fact that, under modules, includes aren't textual.
-Samuel E. Giddins
On Jan 26, 2015, at 10:29 PM, Arne Harren<EMAIL_ADDRESS>wrote:
I've opened an issue: aharren/LibComponentLogging-Core#26
Looks like the implicit transformation of #includes to an import breaks the X macros for the log components.
—
Reply to this email directly or view it on GitHub.

Any news on this? Cocoapods 0.36 is out but Restkit still doesn't work when compiled with the use_frameworks! option

Sorry, there's no general solution for LCL yet. Perhaps it's possible to add the changes to lcl_config_components_RK.h via a #ifdef and keep the old definition of _RKlcl_component. Then, we can change RestKit and adapt LCL independently and we don't break the un-embedding.

LCL hasn't been the holdup, I'm fine with me just committing those changes until LCL has been updated. I just need to work out how to fix everything else :)

@segiddins Have you tried including the seg-clang-modules branch in a podspec?  I was playing around with it and it does build successfully in a dynamic framework if included in a Podfile, however, I attempted to include it in a podspec that I created for my framework, and it won't pass the lint, giving the error below.
    - ERROR |  RestKit/Code/ObjectMapping/RKObjectMapping.h:25:12: error: include of non-modular header inside framework module 'RestKit.RKObjectMapping'
    - ERROR |  RestKit/Code/ObjectMapping.h:30:12: error: include of non-modular header inside framework module 'RestKit.ObjectMapping'
    - ERROR |  Test.swift:9:8: error: could not build Objective-C module 'RestKit'

This PR needs a lot of work, but I'd definitely appreciate contributions to fix things!
-Samuel E. Giddins
On Mar 20, 2015, at 8:24 AM, Jeremy Bone<EMAIL_ADDRESS>wrote:
@segiddins Have you tried including the seg-clang-modules branch in a podspec? I was playing around with it and it does build successfully in a dynamic framework if included in a Podfile, however, I attempted to include it in a podspec that I created for my framework, and it won't pass the lint, giving the error below.
- ERROR |  RestKit/Code/ObjectMapping/RKObjectMapping.h:25:12: error: include of non-modular header inside framework module 'RestKit.RKObjectMapping'
- ERROR |  RestKit/Code/ObjectMapping.h:30:12: error: include of non-modular header inside framework module 'RestKit.ObjectMapping'
- ERROR |  Test.swift:9:8: error: could not build Objective-C module 'RestKit'

—
Reply to this email directly or view it on GitHub.

I haven't found a solution yet, but if I do I'll definitely add it.  I pointed a test project to my local podspec for my dynamic framework that has the RestKit dependency (using seg-clang-modules branch), and confirmed that I get the same error when I build it manually.  What's weird is on the initial build I get the error I posted above.  Then I tried pointing it to #import "RKValueTransformers.h" instead of #   import <RKValueTransformers/RKValueTransformers.h> and as expected, get the error: 'RKValueTransformers.h' file not found. But then, after I set the file back like it originally was and build again, it builds successfully.

I'm starting to think it may be a CocoaPods related issue, perhaps with the RestKit podspec.

No, it's definitely a RestKit issue.

@mrackwitz if you're ever looking for a random thing to work on, I'd appreciate some help getting this to work.

+1

I did fallback to not using use_frameworks! but now I would like to use the cocoapod XCGLogger which is a swift framework and requires the use_frameworks! option.
It looks like I can't use that library until RestKit allows to use it.

@besi I'm sorry, I just haven't had the time to dedicate to fixing this up. Feel free to make a pull request improving the situation!

@segiddins: I just ran into another situation where I would like to use a new swift cocoapod. Could you compile a list of things which would need to be fixed in order for RestKit to be use_frameworks!-friendly?

@segiddins Can you clarify what you mean when you say the pull request needs a lot of work? I am definitely down to chip in if it means we can get framework support in cocoa pods.

@pat2man the easiest solution is probably going to be properly using the submodule dependencies as subprojects, so we can use namespaced imports everywhere.

@segiddins makes sense, thanks for the update.

@segiddins what still needs to be done on this PR before it can be merged in?

The example apps need to compile (and CI needs to pass)
-Samuel E. Giddins
On Jun 16, 2015, at 7:30 AM, Erik Ackermann<EMAIL_ADDRESS>wrote:
@segiddins what still needs to be done on this PR before it can be merged in?
—
Reply to this email directly or view it on GitHub.

I am successfully using this branch in my project now:
pod 'RestKit', :git => 'https://github.com/RestKit/RestKit.git', branch: 'seg-clang-modules'

:+1:

@erikackermann I opened #2254 to fix the issues with the example projects and CI.
@segiddins could let me know if there is anything else you need in order to get this merged in?

Hi @segiddins & @adolfo
Thanks very much for your hard work! I've developed a library called DiscogsAPI based on RestKit and I'm trying to use it in a swift project.
To try your recent changes I've setted the podfile as:
source 'https://github.com/CocoaPods/Specs.git'
use_frameworks!

target "DiscogsAPIDemo" do
    platform :ios, '8.0'
    pod 'RestKit', :head
	pod 'DiscogsAPI', :path => '../'
end

But when I build it, I still get errors like:
While building module 'RestKit' imported from /Users/maximeepain/Gits/DiscogsAPI/Demo-swift/Pods/RestKit/Code/ObjectMapping.h:23:
In file included from <module-includes>:1:
In file included from /Users/maximeepain/Gits/DiscogsAPI/Demo-swift/Pods/Target Support Files/RestKit/RestKit-umbrella.h:3:
In file included from /Users/maximeepain/Gits/DiscogsAPI/Demo-swift/Pods/RestKit/Code/CoreData.h:22:
/Users/maximeepain/Gits/DiscogsAPI/Demo-swift/Pods/RestKit/Code/ObjectMapping.h:21:9: error: include of non-modular header inside framework module 'RestKit.ObjectMapping' [-Werror,-Wnon-modular-include-in-framework-module]
#import <RKValueTransformers/RKValueTransformers.h>
        ^

am I missing something ?
Thanks again,
Maxime

Can you try depending directly on the development Branch?

Same result with:
source 'https://github.com/CocoaPods/Specs.git'

target "DiscogsAPIDemo" do
    platform :ios, '8.0'
    use_frameworks!
    pod 'RestKit', :git => 'https://github.com/RestKit/RestKit.git', :branch => 'development'
	pod 'DiscogsAPI', :path => '../'
end

@maxep CocoaPods version?

@maxep looks like DiscogsAPI.podspec includes RestKit as a dependency:
s.dependency 'RestKit'
...
// Make RestKit globally available
#import <RestKit/RestKit.h>

@adolfo ,
Is it an issue? cocoapods takes care of including dependencies once so it gets code from the dev branch.

Hi I'm having the same issue my project give error here is my pod file
source 'https://github.com/CocoaPods/Specs.git'
platform :ios, '8.0'
target 'ExpSDK_Example', :exclusive => true do
pod "ExpSDK", :path => "../"
pod 'RestKit', :git => 'https://github.com/RestKit/RestKit.git', :branch => 'development'
end
target 'ExpSDK_Tests', :exclusive => true do
pod "ExpSDK", :path => "../"
pod 'Kiwi'
end
use_frameworks!

I am having the same problem using development branch as @cesar-oyarzun-m.  Have there been any new updates or fixes to this issue.
I am trying to reference RestKit (via CocoaPods) in a Swift Framework.

@briangbutterfield Thanks but I already fix the problem!!

@cesar-oyarzun-m Can I ask how you fixed your problem?

@cesar-oyarzun-m Could you please let us know how did you solve this problem? Thank you very much.
I am now using dev branch of RestKit, but still getting errors regarding non-modular headers. I am basically stucked now with my project.

Im trying to use restkit as a dynamic framework, through cocoapods's use_framework! and experience the same issues you guys are having. How on earth did you fix this?

I never did get it to work. I used a different swift-based library.

@briangbutterfield :+1:

Me neither. What I did was that I dropped the Swift library in my project and removed use_framework! from Podfile.

So, I actually solved this. I am now using RestKit as a dynamic framework. The problem was two-fold.

The latest version of restkit 0.26.0 doesnt' build properly using cocoapods. The solution was to use 0.25.0 for the time being. This made the missing headers actually be included and build. See more  here #2356

Secondly, because I use CocoaLumberjack which RestKit has a dependency on (if its found), I either had to include it as a subspec of restkit or include it as a dependency through post_install in my Podfile. Read more: http://stackoverflow.com/questions/31923006/restkit-and-cocoalumberjack-integrated-as-frameworks-in-xcode7

post_install do |installer|
  installer.pods_project.targets.each do |target|
    if target.to_s == 'RestKit'
      target.build_configurations.each do |config|
        config.build_settings['OTHER_LDFLAGS'] = '$(inherited) -framework "CocoaLumberjack"'
      end
    end
  end
end

Hope this helps anyone else having the same issues I had.

Hey Guys,
Have the same issue, I had to rollback to 0.25.0. Any alternative to this? I would like to keep RestKit up to date too.
@tskulbru did you manage to upgrade to 0.26 ?
Regards,
H.

@hernangonzalez no I haven't tried again, but it seems like https://github.com/RestKit/RestKit/commit/cdfe23ff3df684e7cc97ac85578266ec6d2a2449 fixes it. Either try to use HEAD or wait for next release. But I haven't tried it so no guarantees. The commit closed #2356 .

I have this configuration @briangbutterfield @andrejbroncek
source 'https://github.com/CocoaPods/Specs.git'
use_frameworks!

target 'ExpSwift_Example', :exclusive => true do
pod "ExpSwift", :path => "../"
end

target 'ExpSwift_Tests', :exclusive => true do
pod "ExpSwift", :path => "../"
end

and the .podspec
  s.platform     = :ios, '8.0'
s.requires_arc = true

s.source_files = 'Pod/Classes/**/*'
s.resource_bundles = {
'ExpSwift' => ['Pod/Assets/*.png']
}

# s.public_header_files = 'Pod/Classes/**/*.h'
# s.frameworks = 'UIKit', 'MapKit'
s.dependency 'PromiseKit','3.0.0'
s.dependency 'Alamofire','3.1.2'
s.dependency 'Socket.IO-Client-Swift','4.1.2'
s.dependency 'JSONWebToken','1.4.1'
end

Has this been fixed? I'm using RestKit 0.26 and when I addes use_frameworks! to the podfile RestKit is unusable. I'm getting import errors?

@r3econ no, its not possible on 0.26 you have to either use HEAD or continue to use 0.25


fix(module:message): fix the z-index of overlay

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #8010

由于 .cdk-global-overlay-wrapper 是绝对定位，给 .cdk-global-overlay-wrapper 的子元素设置 z-index 是无效的。
What is the new behavior?

将 z-index 样式设置到 .cdk-global-overlay-wrapper 上。
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information
在此之前的 nz 的 cdk-overlay 预建样式是不完整的，此 PR 将导入完整的 @angular/cdk/overlay-prebuilt.css，用户不再需要自行导入该样式，我希望这点会在 CHANGELOG 中特别指出。

Hi @HyperLife1119,
The changes in this PR leaded to the following error during my sample Angular 16.2 project:
./src/theme.less - Error: Module build failed (from ./node_modules/.pnpm/css-loader@6.8.1_webpack@5.88.2/node_modules/css-loader/dist/cjs.js):
Error: Can't resolve<EMAIL_ADDRESS>in 'R:\Projects\tmp\testsite\src'

./src/theme.less?ngGlobalStyle - Error: Module build failed (from ./node_modules/.pnpm/mini-css-extract-plugin@2.7.6_webpack@5.88.2/node_modules/mini-css-extract-plugin/dist/loader.js):
HookWebpackError: Module build failed (from ./node_modules/.pnpm/css-loader@6.8.1_webpack@5.88.2/node_modules/css-loader/dist/cjs.js):
Error: Can't resolve<EMAIL_ADDRESS>in 'R:\Projects\tmp\testsite\src'

I have a theme.less file under src folder with content below (generated by ng add ng-zorro-antd and choose "Set up custom theme file" to yes)
@import "../node_modules/ng-zorro-antd/ng-zorro-antd.less";

It seems the tilde in this patch.less file can't be recognized.
@import<EMAIL_ADDRESS>
Are you able to build successfully in this case?
Thanks.

I use npm to install dependencies and everything works fine.

Interesting, I'm using pnpm. Not sure if that's the reason, I'll try npm when I get a chance.
Thanks.

It's definitely an issue of pnpm, I have to ng add @angular/cdk explicitly on my project other than depending on the cdk dependency of ng-zorro-antd itself to make it work.

Hi, @HyperLife1119 Are these issues(#8119 #8106 ) caused by that pr, please take a look? Also the switching theme on the official website is unusually

@OriginRing 通过 #8122 修复这一问题。


update conda.recipe with build numbers

updated

Thanks.  Merging.

Now to go see if binstar-build likes it...

So after merging this we started getting these errors https://binstar.org/blaze/datashape/builds/14/17
I removed the offending line in https://github.com/ContinuumIO/datashape/commit/bc2cda3f84ce88f0a68e8946133e62f852e70381, thinking that it wasn't necessary now that we're using git describe but oddly we're only seeing the new build number show up on windows builds and not linux ones.
Windows: https://binstar.org/blaze/datashape/builds/15/17
Linux: https://binstar.org/blaze/datashape/builds/15/1
Thoughts @jreback ?
Looks like this problem also exists in Blaze but not yet in into.

no idea
we are using a very similar structure for other repos
maybe @cpcloud would know


block-images: fix bbc.com link

https://bbc.com doesn't appear to work.

Is this a bug? It works for me in chrome, although it forwards me to the http site.

It's dreadfully slow for me. Caused timeout issues running the sample a couple of times last night.
What about https://news.google.com instead?

Sure

PTAL


add build handling for npm publishing

Fixes #66

What does this achieve, exactly?
I think it creates a new grunt command "grunt build", which will call "grunt clean" and "grunt copy" in that order, but why?
This seems to need an update to README to describe how one uses the functionality (and why).

What does this achieve, exactly?
I think it creates a new grunt command "grunt build", which will call "grunt clean" and "grunt copy" in that order, but why?

It cleans out the out/ directory to make sure we start fresh, it then copies the files listed in the files array in Gruntfile.js to out/. This is done to ensure we explicitly choose which files should be part of the NPM published package, hence it fixes what you saw in #66.
I can change the names of the build command if it makes it more clear?
Do you want to add the npm publish step to this as well or keep it separate (i.e. grunt build > check that files are OK > npm Publishj)?

This seems to need an update to README to describe how one uses the functionality (and why).

Sure I can add steps on how to prepare and publish this as an NPM package.

I guess all of this can be handled by just populating .npmignore properly. Closing....


feat(2095): Handle multiple unclosed closeables in same try

Fix #386
This PR is a minor extension to the UnclosedResourcesProcessor that simply makes it respect an existing try-with-resources, and add resources to it rather than delete it and create a new one (which would cause resources to be lost; only the very last resource processed would ever appear in the resource block of the try). By extension, this allows the processor to deal with multiple unclosed resources in the same try-block. Here's how that works:

There's one violation for each unclosed resource
The first violation is fixed first (due to iteration order of the AST), and creates a try-with-resources block, with any remaining violating elements being placed within it
Any further violations are fixed simply by deleting the violating element and adding it the the (now existing) try-with-resources

This is the code that corresponds to the patch in this PR.

There are a gazillion corner cases which this does not cover. I will keep improving this processor with tiny PRs every once in a while. Next up is #540.

@slarse thank you!


THEEDGE-2929

Description
Currently, handleClose event in UpdateVersionTable.js is hardcoding to go back to inventory page every time an update is trigger. That's not the case when updating from system details page or group details page. This PR is changing handleClose to redirect to previous correct page using history.go(-2) instead of history.push()
Fixes # (issue)
THEEDGE-2929
Type of change
What is it?

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Documentation update
[X] Tests update

Checklist:

[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] 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] I run npm run lint:js:fix to check that my code is properly formatted

Functionality works as expected. I have tested on my local front end

Codecov Report
Base: 30.23% // Head: 30.23% // No change to project coverage :thumbsup:

Coverage data is based on head (d62882a) compared to base (bfbef21).
Patch coverage: 0.00% of modified lines in pull request are covered.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #619   +/-   ##
=======================================
  Coverage   30.23%   30.23%
=======================================
  Files         127      127
  Lines        2821     2821
  Branches      878      878
=======================================
  Hits          853      853
  Misses       1800     1800
  Partials      168      168

Impacted Files
Coverage Δ

src/Routes/Devices/UpdateVersionTable.js
0.00% <0.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


add htmlFilePath to the jatos.studyProperties

add htmlFilePath to the jatos.studyProperties, it already exists in jatos.componentProperties

Done, my liege: in jatos.studyProperties you can find "dirName" now, use it together with /study_assets/dir_name/my_path.


[Dialog] Typings of PaperProps prop doesn't allow all Paper props

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
You can't set component prop in PaperProps without TS errors even though the prop exists in Paper component.
Expected behavior 🤔
You should be able to set all Paper component props in PaperProps prop of Dialog.
Steps to reproduce 🕹
Steps:
Write the following code and see the TS errors on the latter.
<Paper component={"form"} onSubmit={handleSubmit} />
<Dialog
  PaperProps={{
    component: "form",
    onSubmit: handleSubmit,
  }}
/>

Context 🔦
I am trying to use the Dialog as a form by changing Paper component into form. I cannot just wrap the whole Dialog with form because I have portal enabled for the Dialog.
Your environment 🌎

`tsconfig.json`
```
{
  "extends": "../tsconfig.base.json",
  "compilerOptions": {
    "rootDir": "..",
    "baseUrl": ".",
    "composite": false,
    "declaration": false,
    "declarationMap": false,
    "sourceMap": false,
  }
}
```

Maybe related? https://github.com/mui/material-ui/issues/27703

@jussirantala
You are correct. This and #27703 have the same root problem, which is that the interface PaperProps doesn't have component as a key.
I opened a pull request here: https://github.com/mui/material-ui/pull/32404


fix: feature package templates pubspec.lock does not respect routing param

This needs a reconsider wheter the create command uses a melos bs, a recursive flutter pub get with pregenerated pubspec_overrides.yaml or a recursive flutter pub get with pregenerated pubspec_overrides.yaml and pubspec.lock.

We stick with recursive pub get for now


Sync

Update make testbigperf and synch folder so correct commands used to get data.  Still, data is closed.

Just FYI, going to squash and merge since not tested in jenkins.


Release v1.7.0

What this PR does:

[BUGFIX] Fix nginx extraContainers to indent correctly #373
[DEPENDENCY] Update dependency nginx to v1.23 #375
[DEPENDENCY] Update dependency kiwigrid/k8s-sidecar to v1.19.2 #370
[DEPENDENCY] Update quay.io/cortexproject/cortex Docker tag to v1.13.0 #381
[DEPENDENCY] Update kiwigrid/k8s-sidecar Docker tag to v1.19.4 #387
[DEPENDENCY] Update kiwigrid/k8s-sidecar Docker tag to v1.19.5 #392

Which issue(s) this PR fixes:
Checklist

[ ] CHANGELOG.md updated - the order of entries should be [CHANGE], [FEATURE], [ENHANCEMENT], [BUGFIX]

HI @kd7lxl, can you +1 this new release cut? 🙏

Is there any extra step to actually cut the release? I still only see up to 1.6.0 available.

Is there any extra step to actually cut the release? I still only see up to 1.6.0 available.

helm repo update? :D


Will you join us?

Hello NeXyon.
We are now a small Blender audio developers team, we're 3 people and probably we'll become 5.
Will you be the 6th?
Thanks in advance for either.

That sounds awesome! May I ask what your plan is for the future? Do you want to stay in Python world or actually tackle C/C++ blender code?

We're going to use Python, mainly.
The Plug-in is almost ready, we just need to review the code, make the AddOn depending from Animation Nodes and

I see. I could help with reviewing C/C++ code for Blender, but I think for anything else I don't really have time. I'm anyway in maintenance and bug fixing mode only for Blender. I wish I would have more time to develop new features...


Add support for dry-run to print out only the things that will be changed

Hi. We are faced with a problem when we're running dry-run with verbosity and gitlabform shows diff in cases where nothing is going to be changed.
Output example:
                                  default_branch: "master"   => "master"
           only_allow_merge_if_pipeline_succeeds: true       => true
only_allow_merge_if_all_discussions_are_resolved: true       => true
               resolve_outdated_diff_discussions: true       => true
             printing_merge_request_link_enabled: true       => true
                           snippets_access_level: "disabled" => "disabled"
                               wiki_access_level: "enabled"  => "enabled"
                                    wiki_enabled: true       => true
                                    merge_method: "ff"       => "ff"
                                      visibility: "private"  => "private"
                remove_source_branch_after_merge: true       => true
Skipping section 'project_push_rules' - not in config.
Processing section 'merge_requests' in dry-run mode.

GitLabForm version
2.5.0
GitLab version
14.0.0-ee

up

Hi @mkryva, sorry for the long response time!
This is actually how this feature has always worked...

As a workaround I use this when running it in CI:
# sed explanation:
# 1. Removes all lines with not in config. It adds nothing valuable
# 2. Removes all lines stating processing in dry-run mode.
# 3. Removes all lines which indicate no change, for example true => true
# 4. Adds color coding to lines that do change
gitlabform ALL_DEFINED ${DRY_RUN:+--noop} --verbose \
  | sed -e '/not in config.$/d' \
  | sed -e '/in dry-run mode.$/d' \
  | sed -re '/:\s(\S*|".*")\s+=>\s\1/d' \
  | sed -re 's,.*=>.*,\x1B[1;33m&\x1B[0m,'

We are also trying to use --noop in a CI pipeline with gitlabform 3.4.1. In our case we hope to use the dry-run in branch pipelines as a way to show what might be changed, so having a way to limit the output to only the expected changes would be very useful. The last two sed tricks used by @tmeijn in the comment above don't work in our case because the ghcr.io Docker image for gitlabform is based on Alpine, and sed behaves differently under POSIX.
+1 on this issue; it would be great if we had a way to see only changes in the output, with the option to colorize it, using the official Docker image.

That's is a good remark @lmaughan-ep. In my case I just run apk add sed before executing GitLabForm which installs the gnu-sed IIRC. Also using the official image btw, no custom build.

Does the issue title/description need to be adjusted?
I only asked, because to me it sounds like the ask is:
Can the functionality be added to support printing out only the things that will be changed
Seems that is the case, based on the others who've commented about using sed to clear up the output 😄

I'd sure love to try! Might be a few days before I come back with anything reasonable though 😎


Allow automatic linking of issues everywhere

We have been limiting the channels where automatic linking issues can be used (See #566).
Since we haven't seen any potential issue with it, we can allow it everywhere to avoid updating it every two days or because of missing channels.
Closes #630.

@kosayoda I agree that those changes should be done, but isn't it out of scope for this PR?

@kosayoda I agree that those changes should be done, but isn't it out of scope for this PR?

My opinion is after this PR, the scope of automatic detection and linking essentially goes from 3 non-staff channels located at the bottom of the server to every single channel in the server, which is a potentially huge issue given the number of problems still present in the feature.

@kosayoda I agree that those changes should be done, but isn't it out of scope for this PR?

My opinion is after this PR, the scope of automatic detection and linking essentially goes from 3 non-staff channels located at the bottom of the server to every single channel in the server, which is a potentially huge issue given the number of problems still present in the feature.

Sounds good, will do that this afternoon 👍

@kosayoda the requested changes have been addressed. I took the liberty of rewriting the cog in https://github.com/python-discord/sir-lancebot/pull/642/commits/08b1348b33d2d865987f2677a68ba62645db2abe because the old code base was too complicated to work with. Should be good to go now!

Automatic linking has been extended to other organisation! Closes python-discord/organisation#345.


Is it possible to generate ply file

Hi thank you for your great work, I saw that the demo is generating sequence of images by interpolating image pose, I wonder if it is possible to generate the 3D object (maybe .ply file) for entire scene instead so we can open it using software like blender.

Hi, thanks for your interest in this project. Theoretically, it can generate ply files using some techniques like marching cubes, but the mesh quality should not be very good and may have many noises.

Ok I got it, thank you for your response


Replace unsafe C functions like strcpy with safer alternatives

Inspired by https://github.com/urbit/archaeology/pull/71, there are numerous calls to strcpy(), sprintf(), and other "unsafe" functions. Many of these are harmless...but a few actually seem feasibly exploitable! Kinda!
In any case, in my fork (https://github.com/darighost/vere) I replaced all of the calls to strcpy(), sprintf() with calls to snprintf  instead. It's also possible I'm breaking a bunch of stuff without realizing. My fork compiles and I ran it and did Urbit stuff but who knows, there's an infinite amount of behavior I didn't test so yeah.
If this is desired, I'd also like to replace some other functions as well. But I wanted to check, is this even a change you guys want? Also, I'm using this as a chance to "practice" contributing to this repo, so please let me know if I should be doing something differently.
Thanks!
PS: I know, I know, we're all awaiting Ares with bated breath. What can I say. I also like PHP and Visual Basic 5, sue me.

@darighost such a PR would be welcome, we shouldn't be using the unchecked versions of those string functions.


Engagement Phase Tweaks

Issue #992 :
https://github.com/bcgov/met-public/issues/992
-Remove engagement icon for readiness decision
-Rename one of the engagements
Reason: Marie Anik's request
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the met-public license (Apache 2.0).

Codecov Report

Merging #1032 (7a24860) into main (b2dc6ad) will decrease coverage by 5.74%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main    #1032      +/-   ##
==========================================
- Coverage   73.64%   67.89%   -5.75%
==========================================
  Files         217      134      -83
  Lines        5975     2934    -3041
  Branches      391      391
==========================================
- Hits         4400     1992    -2408
+ Misses       1532      899     -633
  Partials       43       43

Flag
Coverage Δ

metapi
?

metweb
67.89% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

met-web/src/models/engagementPhases.tsx
100.00% <ø> (ø)

met-api/src/met_api/constants/user.py

met-api/src/met_api/models/widget.py

met-api/src/met_api/utils/template.py

met-api/src/met_api/models/pagination_options.py

met-api/src/met_api/resources/apihelper.py

met-api/src/met_api/schemas/widget.py

met-api/src/met_api/resources/feedback.py

met-api/src/met_api/schemas/engagement_survey.py

met-api/src/met_api/models/engagement_status.py

... and 74 more


Update README.md

This is initial pull request for the work ahead of us.

Initial pull request

So, I've left out the web config deliberately because it contains app secrets, such as email credentials, database connection strings, etc.
I'm willing to merge this in, but it will mean we need to move app secrets to some other location. This article lays out how to do that: https://www.asp.net/identity/overview/features-api/best-practices-for-deploying-passwords-and-other-sensitive-data-to-aspnet-and-azure and I can make that happen.

I've merged your PR. I've just now committed a few related items:

The real web.config, web.debug.config, and web.release.config
Moved the secrets out of web config and into AppSettings.Debug.Secrets.config and AppSettings.Release.Secrets.config
Moved the connection strings out of web config and into ConnectionStrings.Debug.Secrets.config and ConnectionStrings.Release.Secrets.config

I've also updated .gitignore to exclude these secrets files. If you need the debug secrets, just shoot me an email and I'll send them over.

That is great, I had these changes as well in my next pull request. I will need to get your latest first. My goal right now to be able to run the code completely locally:

Sample music files with album art
Seed database with sample data
Simple unit tests for C#

Thanks, Max

I want to set up seeder with simple data points, so if we have other devs who would like to assist they can without special info. For emails, I was thinking using configuration to write to txt files. What are your thoughts on that?

Sure, I'm cool with setting up a seed function to get started easier, if that's what you mean.

"For emails, I was thinking using configuration to write to txt files. What are your thoughts on that?"

You're talking about any time we send emails in the app, to replace that to write to txt files in debug, and making that happen via config? If that's what you mean, sure. I'm OK with sending emails even in debug, but if you want to move that out so it writes to txt files instead in debug, sure, it would be a nice-to-have.


Remove RelativeLayout from Database quickstart

See #1217
I kept all the layouts the same except I changed a lot of the padding/margin values to be the standard 8/16/24 scale instead of the 5/10/15 that was being used in this app.
activity_main

Before
After

activity_new_post

Before
After

activity_post_detail

Before
After

activity_sign_in

Before
After

fragment_all_posts
N/A this is a FrameLayout
include_post_author

Before
After

include_post_text

Before
After

item_comment

Before
After

item_post

Before
After

@rosariopfernandes I can't assign you directly but please review this one when you get a chance!

@rosariopfernandes I can't assign you directly but please review this one when you get a chance!

@rosariopfernandes thanks for the quick comments!  I think I addressed them now.

@rosariopfernandes thanks for the quick comments!  I think I addressed them now.


Scrolling is stucking on the page

Description
Scrolling is sticking on the page
For reproduce the bug create next:

Create new notebook in JupyterLab
Create 3 or more cells with next content and change 1.png and 1.png to any your images

text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text
text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text
text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text
text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text
text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text
text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text
text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text text

:::{image} images/1.png
:::
:::{image} images/2.png
:::

Go to bottom the page and try scroll to up page

Hello, I've fixed this issue!
This is what I've done:
I've identified the issue causing the scrolling to stick on the page. The problem was in the CSS for the MySTMarkdownCell. I've updated the style/base.css file to allow scrolling within the cell content. Here's what I've done:

Modified the CSS for .jp-MySTMarkdownCell to enable scrolling.
Adjusted the overflow property for the input area and its child widgets.
Ensured that the rendered content has proper overflow handling.

These changes should resolve the scrolling issue while maintaining the existing functionality.
I also created pull request: https://github.com/jupyter-book/jupyterlab-myst/pull/251

[!CAUTION]
Disclaimer: This fix was created by Latta AI and you should never merge before you check the correctness of generated code!

This bug was fixed for free by Latta AI - https://latta.ai/ourmission


Is it possible to have a "merge" function

Like in Mantle there are methods like mergeValuesForKeysFromModel: and mergeValueForKey: fromModel.
Is it possible for ObjectMapper to support that since during mapping we have typed all the keys, and we can use a set to record them?
It may be not easy but is it possible?

Unfortunately due to the structure of the code, I do not think this is possible.

I have found a temporary solution. You can create an extension of Dictionary:
extension Dictionary {     mutating func merge(with: Dictionary){         for (k, v) in dict {             updateValue(v, forKey: k)         }     } }
Then you can use your objects as JSONs to merge them, for example:
`
var user1 = User()
user1.name = "Mario"
var user2 = User()
user2.name = "Pedro"
user2.email =<EMAIL_ADDRESS>var user1JSON = user1.toJSON()
var user2JSON = user2.toJSON()
user1JSON.merge(with: user2JSON)
print(user1JSON)
// Result = ["name": "Pedro", "email"<EMAIL_ADDRESS>`


Indicate if a deployment was done with a different (non-console) client

Is your feature request related to a problem? Please describe.
Users sometimes attempt to modify deployments not done using console. Example https://discord.com/channels/747885925232672829/1053359341144653957/1089949113916850227
Users need to be able to quickly know (and ideally filter) which deployments were done using console vs. other clients
Describe the solution you'd like
I can think or two ways to handle this:

Add some messaging (could be an icon or label next to the deployment name) -- this is the easiest but doesn't allow sorting or filtering)
Column to indicate if a deployment was not done using console - a "check" or something indicates that a different client was used - probably a little more work but will let the user sort and quickly see all deployments done with and without console
Filtering option (when we do support filters on this page)

** Implementation hint **
Check to see if we have the SDL. If we do then Console did the deployment. If not, some other client did.
Describe alternatives you've considered
Do nothing.
Additional context
There are multiple (vertically focused) clients for deploying on Akash: https://github.com/akash-network/community/tree/main/sig-clients

Additional label might work. Attaching a draft for "Certificates" where one indicates the label was created on a different computer - my suggestion is to create one solution to serve two purposes. (indicating a remote certificate, indicating a different deployment tool)

@aktdenis - thanks, that's an interesting idea but I fear that it may confuse users into thinking that the deployment is "remote" as in runs on a server not owned by them (which is not the intention)

@anilmurty i'm thinking we should play around with wording. Maybe "static" or "non-updatable" to clearly communicate that the deployment cannot be changed. In contrast "updatable" may be misinterpreted or cause confusion.
I'm an advocate for creating an additional label in "status" column - because that column already provides important information about the current state of the deployment. I believe this approach would help reduce visual clutter.
Attaching 3 examples for further discussion:

additional column "updatable + info/tooltip"

label within "status" column named: "non-updatable + lock icon" + info

label within "status" column named: "static + lock icon" + info/tool tip

@jtary feel free to chime in, so we can make the final decision.

Thanks @aktdenis. Did you mean to include a screenshot with the "updatable?" Column as well?
Re. The labels. I did think of that option too initially but decided not to go that route because the user wouldn't be able to sort and quickly group all non-console deployments together (we do not currently have filtering available). But ofcourse it wouldn't be a problem if we did have filtering supported.

Maybe one option is to go with the new column + "check" for now and then update to label when we can support filtering on this table

@anilmurty sorry! posted the wrong screenshot above. you had something like this in mind?

Yes - that's exactly what I had in mind @aktdenis . If it's ok with you I'd like to run with that for now and then move to your (nicer) design when we have filtering capabilities. Sound ok?

@anilmurty yes, sure!

Hi there, I wanted to know if that's how the implementation is supposed to work?

Only we want a right check mark reading info state.

Probably following things can help
  const [sdl, setSdl] = useRecoilState(deploymentSdl);

and
          {
            label: 'Updatable',
            value: sdl ? 'Yes' : '',
          },

Would like to get your opinion.

@jtary - please review when you have a moment

@Amit0617 for the deployment to be updatable two things have to be true:

It has to be active (that's what the original check was looking for).
You have to have an SDL for it.

Technically, you don't need the original SDL. You can update a deployment with any SDL as long as the group config matches (ie: same storage and compute requirements). You will have to update the deployment version as well, but that's generally a given unless you are updating with the exact same SDL.
For the sake of simplicity, we work of the assumption that we only can update if we have the original SDL. This so we can drop the user back into the SDL Configuration screen with the locked-in group requirements.
TL;DR:
canUpdateDeployment = deployment[deployment.state] === 'active' && sdl !== undefined;

Hope that helps.

I wasn't able to access that page in browser. I hope the above PR achieves the required.


Spike: helm chart repo creation on Github

Description
As a developer I want to create a public bevel helm chart repo on the current hyperledger/bevel git repository using github pages
Steps:

Explore the process of creating public helm chart repo on GitHub using GitHub Pages.
Test the process on bevel forked repo

Acceptance Criteria

The process steps are documented.
The changes required in bevel repo to support hosting chart repo are documented.

Process steps
1. Create a branch called gh-pages.
This branch will be used to build the github pages, the name matters if you want to use automated option for creating the charts artifacts
2. Configure the github pages in the repo setting
Configure as shown below

Remove the platforms folder as this code in it throws linting error while the pages are build. We should keep the gh-pages branch with just the readme files or custom files for the site
3. Create the charts folder
Have all the charts that needs to be in helm repo under charts folder in /root of repo, this should be in main branch
Example below:

4 . Create the helm repo chart artifacts: Option 1: automated
Pros: Automates the creation of chart tar files and index.yaml, and stores the tar in release artifacts
Cons: Creates releases for each charts under charts folder, which will clutter the release pages if there are many charts in charts folder
Create a workflow as show in the image below in the main branch (this uses chart-releaser-action workflow)

4 . Create the helm repo chart artifacts: Option 2: Manual
Pros: No release is created, full control over the index.yaml file create and the tars
Cons: Have to manually create the index.yaml file and tars and store them in gh-pages branch
This needs to be done the gh-pages branch
Package your Helm charts
Helm package charts/
Create the index.yaml file for the Helm repository
Helm repo index --url <github_repository_path>


Pull request #105: [Crypto] Use MBEDTLS_PRIVATE to access the session and othe…

… ssl params
Merge in WMN_STACKS/openthread from bugfix/fix-dtls-api-to-support-mbedtls-3.0 to staging/bugfix/fix-dtls-api-to-support-mbedtls-3.0
Squashed commit of the following:
commit 56e9d32e5d84f69ca0322b26876c3002ab10d5b9
Author: Hemanth Rao<EMAIL_ADDRESS>Date:   Wed Oct 13 15:28:17 2021 +0100
Make Pretty changes

commit 84ce733f2183863de2aafe2caed8079bd1c179fa
Author: Hemanth Rao<EMAIL_ADDRESS>Date:   Wed Oct 13 15:23:42 2021 +0100
Use MBEDTLS_PRIVATE to access the session and othe ssl params

@jwhui @LuDuda There was one API that needs updating to support mbedTLS 3.0. Can you guys have a look at this PR?

Alternatively, we could completely remove this function as probably, it is not used by anyone.

Thank you @LuDuda I did not know if anyone else used the API so let it as it is.

@ChrIgiSta , are you aware of any users of this API?


more C++ bindings

This extends the C++ bindings with subclasses for isl_schedule_node.

This exports lists differently that we have already, we probably don't wont to keep both at the same time

On Thu, Dec 07, 2017 at 04:57:13PM +0000, ftynse wrote:

This exports lists differently that we have already, we probably don't wont to keep both at the same time

The way I export lists here is how I plan to export
them in mainline.  Does it look reasonable?
As to the one that was in place in ntv_dev, I haven't
looked at it in full detail yet, but I think it's best
to keep it until we have migrated completely to
the other one.  That means in particular, that
we first need to decide what to do with isl_id and
we probably want to support range-based for loops
on top of the mainline lists.
Do you see any risk of conflict in the mean time?
skimo

The lists look reasonable on a higher level. Alex had some earlier approaches which looked slightly different.
He also had patches for generating iterator based loops: https://github.com/PollyLabs/isl/pull/20/commits/1fa18f61c51ff92a7298111613f21e7a9fc14491
Here some more thoughts about range-based loops: https://github.com/PollyLabs/isl/issues/5

I find the approach we have with templates more idiomatic C++: list is a container with element type as template argument.  What one should do if they want to export a new list now?
We have a minimalistic id export here https://github.com/PollyLabs/isl/pull/21.  No user pointers to be compatible with Python, the argument being "if you want to access user pointers, you are using isl C way and should use C interface".
We also have a separate patchset for the lists support currently used in ntv_dev in https://github.com/PollyLabs/isl/pull/20/files

On Fri, Dec 08, 2017 at 09:56:49AM +0000, ftynse wrote:

I find the approach we have with templates more idiomatic C++: list is a container with element type as template argument.  What one should do if they want to export a new list now?

Change ISL_DECLARE_LIST(*) to ISL_DECLARE_EXPORTED_LIST(*)
skimo

I meant more generally, with two approaches available, which one should
be chosen?
On 08/12/2017 11:20, skimo-openhub wrote:

On Fri, Dec 08, 2017 at 09:56:49AM +0000, ftynse wrote:

I find the approach we have with templates more idiomatic C++: list
is a container with element type as template argument. What one should
do if they want to export a new list now?

Change ISL_DECLARE_LIST(*) to ISL_DECLARE_EXPORTED_LIST(*)
skimo
—
You are receiving this because your review was requested.
Reply to this email directly, view it on GitHub
https://github.com/nicolasvasilache/isl/pull/67#issuecomment-350227671,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABcTa_1WetiP6LwgG7YY2H2s2GvWltuAks5s-Q2FgaJpZM4Q5gZL.

I think both are reasonable choices. I also have a slight preference to Alex's more idiomatic template approach, but would also be fine with Sven's approach. I am sure Michael and Alex also would have comments. ;-)

On Fri, Dec 08, 2017 at 10:22:43AM +0000, ftynse wrote:

I meant more generally, with two approaches available, which one should
be chosen?

As long as we are in this intermediate state,
I think we should consider this question if and when
it arises.
skimo


Fixed a few typos and missing return types

Awesome mate, in the end I never got to use this for the project :( Glad someone can tidy it up and get some use maybe.  Thanks!

No problem, it was great to find someone had created definitions for cannon.js! Have you considered submitting to DefinitelyTyped?


LivestreamLink: fix flicker when a child updates

Ticket
Closes #1358 - flicker on livestream tile when viewers updates

Test
inf

Change
Defining the component that way results in unique Card wrapper on each resolve, so everything gets torn down and re-mounted, causing the flicker.
There is a css side-effect with the fix though: the tags changed from red to black. But tags are inconsistent through the app ... sometimes black, sometimes red (I think it should always be red + smaller font from the body).

Thank you! Will file a ticket to re-address the tags.


How to use inline equation with KaTex

Does something like $a=b-1$ works?
Thank you.

Hello,
maybe you want to use a specific class for elements that should be converted to latex, and convert all elements of that class to latex.
example:

This equation : f(x)=0

with this script at the end of the body:


Avoid module init on build/install

Hi, we are looking to add pyautogui as a dependency to our own testing toolbox. Unfortunately, the build process is not straightforward as the import of the version string in setup.py invokes module init because of the import of the __version__string. This breaks the installation in headless environments (e.g. in our daily builds on Jenkins).
The proposed change fixes installation issues in headless environments (examples: #78, #101).
I also configured and ran some test builds on travis to verify the patches work for different python versions on linux and OSX.

This has already been fixed in a different merge, but thanks anyway! I'm adding you to the authors file. Thanks again!


Running omnisci tests is slow

Investigate where is the boddle-neck of running omniscidb queries containing UDF calls.
For instance, running the 14 tests in test_ndarray_methods takes about 17 seconds (omniscidb server runs on the same host).

In the way we structure tests, Numba will compile all ndarray_{method} tests every single time a test is executed. That's why this file is too slow.

Yes, this can be the case here. We can restructure the tests as follows:
ndarray_methods = [
    ('fill', 'double[](int64, double)', (5, 4), [4.0, 4.0, 4.0, 4.0, 4.0]),
   ... ]
...
def test_ndarray_methods(omnisci, method, signature, args, expected):
    omnisci.reset()
    from rbc.omnisci_array import Array

    def ndarray_fill(size, v):
        a = Array(size, 'double')
        a.fill(v)
        return a
    ...

    omnisci(signature)(eval('ndarray_{method}'))

    query = 'select ndarray_{method}'.format(**locals()) + \
            '(' + ', '.join(map(str, args)) + ')'
    _, result = omnisci.sql_execute(query)
    ...


v2.0.0

Handle passing in an array of tokenIds to Utils.list
Bump to bitbox-sdk v4.0.0

:tada: This PR is included in version 1.1.13 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


69 extractor class for each source with inheritance from a base extractor class

modularized extraction
base extractor class
source-specific extractor classes
mixin classes for PyTorch and TensorFlow
modified unittests according to most recent changes

Codecov Report
Base: 79.43% // Head: 80.87% // Increases project coverage by +1.44% :tada:

Coverage data is based on head (19022da) compared to base (495e4fa).
Patch coverage: 78.74% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master      #91      +/-   ##
==========================================
+ Coverage   79.43%   80.87%   +1.44%
==========================================
  Files          21       23       +2
  Lines         953     1025      +72
  Branches      167      145      -22
==========================================
+ Hits          757      829      +72
  Misses        163      163
  Partials       33       33

Flag
Coverage Δ

unittests
80.87% <78.74%> (+1.44%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

thingsvision/custom_models/official_clip.py
100.00% <ø> (ø)

thingsvision/custom_models/openclip.py
85.71% <ø> (ø)

thingsvision/core/extraction/helpers.py
70.93% <69.33%> (-12.41%)
:arrow_down:

thingsvision/core/extraction/mixin.py
80.76% <80.76%> (ø)

thingsvision/core/extraction/extractor.py
83.11% <80.95%> (+10.43%)
:arrow_up:

thingsvision/core/extraction/base.py
90.62% <90.62%> (ø)

thingsvision/utils/storing/helpers.py
61.95% <100.00%> (+0.41%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Application GaGaMall has not been registered？

Application GaGaMall has not been registered. This is either due to a require() error during initialization or failure to call AppRegistry.registerComponent.

这个问题，两种解决方案:
1.模拟器测试一下，直接运行命令。
2.真机和电脑连接同一个Wifi，然后真机设置电脑的IP和默认8081端口，运行命令。
注意一定要查看一下React Native Server打开了没

另外的可能，你是不是也有其他项目运行着？可以先关闭其他一切项目，运行本项目即可

i am also having the same issue and i am using
"dependencies": {
"react": "16.4.1",
"react-native": "0.55.0"
},
"devDependencies": {
"babel-jest": "23.6.0",
"babel-preset-react-native": "5.0.2",
"jest": "23.6.0",
"react-test-renderer": "16.4.1"
},
"jest": {
"preset": "react-native"
}
}
can any one suggest any solution about thi sproblem i have spent 2 days at this issue and this doesnot seems to be going anywhere


Remove Jackson usage in Attestation, Models Repository, Quantum Jobs, and Video Analyzer Edge

Description
Removes the usage of Jackson in the following packages:

azure-iot-modelsrepository
azure-media-videoanalyzer-edge
azure-quantum-jobs
azure-security-attestation

All SDK Contribution checklist:

[x] The pull request does not introduce [breaking changes]
[x] CHANGELOG is updated for new features, bug fixes or other significant changes.
[x] I have read the contribution guidelines.

General Guidelines and Best Practices

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

Testing Guidelines

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

API change check
APIView has identified API level changes in this PR and created following API reviews.
com.azure:azure-iot-modelsrepository

@microsoft-github-policy-service rerun

@microsoft-github-policy-service rerun

/check-enforcer evaluate


Fixed includes in arch/arm/src/stm32l4/hardware/.

Several header files in arch/arm/src/stm32l4/hardware/ had the
following line included:
#include "chip.h"
The problem with this was that the chip.h file is missing in this
directory (in arch/arm/src/stm32l4/hardware/). The intended chip.h
file to include was probably in arch/arm/src/stm32l4/chip.h. If any of
the headers in arch/arm/src/stm32l4/hardware/ got included from a
directory that did not contain a chip.h file, the compilation
failed.
After looking deeper into this I realized that the following files
were also including files with the wrong paths:

arch/arm/src/stm32l4/hardware/stm32l4_syscfg.h
arch/arm/src/stm32l4/hardware/stm32l4_pinmap.h

Finally, it seems as if a lot of headers, but not all, included:
#include <nuttx/config.h>
In this case, the include is only useful if a CONFIG_* define is
being referenced. These includes were removed from files that had no
CONFIG_* references and added to files that had CONFIG_* references,
but was missing the include.
The final change to be mentioned, was the moving of the GPIO defines
from arch/arm/src/stm32l4/stm32l4_gpio.h to
arch/arm/src/stm32l4/hardware/stm32l4_gpio.h. This was done to supply
arch/arm/src/stm32l4/hardware/stm32l4*_pinmap.h with a local include
for their GPIO references.
This patch changes no functionality. It simply cleans up includes and
allows inclusion of the headers in arch/arm/src/stm32l4/hardware/
from anywhere, without causing compiler errors.

I don't believe this change should be incorporated upstream.  It does not handle the include paths and it takes perfectly compliant code and makes it inconsistent with everyother architecute.  Consistency must be preserved.

Hi wingunder, please note that normally header files included inside stm32l4/hardware/ directory are mainly used for internal chip registers definitions and the headers at base of stm324/ contains definitions that will be outside of arch/ dir i.e. inside boards/ . Also note that all arch follow this logic, if you want to change it you need to do it for all arch, not only for stm32l4.

Hi @patacongo & @acassis,
Thank you for you feedback. I accept your reasoning.
Regards


Bump pion/ice and pion/turn

gortc import paths have changed from github to gortc.io
Updating to use version that doesn't import those paths

Codecov Report

Merging #749 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #749   +/-   ##
=======================================
  Coverage   76.66%   76.66%
=======================================
  Files          58       58
  Lines        4041     4041
=======================================
  Hits         3098     3098
+ Misses        689      687    -2
- Partials      254      256    +2

Impacted Files
Coverage Δ

sctptransport.go
74.34% <0%> (-1.32%)
:arrow_down:

dtlstransport.go
67.83% <0%> (+1.16%)
:arrow_up:

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 a6c3eaf...e9d0951. Read the comment docs.


Fix escaped go vet error

Find one escaped go vet error:
$ cd pkg/httputils/
$ go vet .
httputils_test.go:28: arg response for printf verb %q of wrong type:
*net/http.Response

You can also find it with
$ go vet github.com/docker/docker/pkg/httputils/

or
$ go vet ./...

Signed-off-by: Zhang Wei<EMAIL_ADDRESS>

This is kind of funny, also confused me, see that
$ go vet ./pkg/httputils/
pkg/httputils/httputils_test.go:27: arg response for printf verb %q of wrong type: *net/http.Response
exit status 1
$ go vet ./pkg/httputils/httputils_test.go
$

Not sure why. But maybe we should go vet pkg instead of standalone file?

I'm not sure if it's the case here, but one issue I've run into a few times with go vet is that it sometimes misses issues when compiled packages aren't present: https://github.com/golang/go/issues/9439


Add a new application idea

Thought about an idea for an app that I as a developer would need

@roopeshsn finally deployed after correction, could you please merge it


Bump SCIM2 version to 3.4.103

Changes in this PR

$subject to get the changes in [1] which was released in [2].

[1] https://github.com/wso2-extensions/identity-inbound-provisioning-scim2/pull/575
[2] https://github.com/wso2-extensions/identity-inbound-provisioning-scim2/tree/v3.4.103

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/12232224315

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/12232224315
Status: success


lxc cluster add shouldn't have any alias

Signed-off-by: Simon Deziel<EMAIL_ADDRESS>

This pull request didn't trigger Jenkins as its author isn't in the whitelist.
An organization member must perform one of the following:

To have this branch tested by Jenkins, use the "ok to test" command.
To have a one time test done, use the "test this please" command.

Those commands are simple Github comments of the format: "jenkins: COMMAND"

Thanks, not sure how that got in there!


fix: change the builder resolve plugin

Description

fix: change the builder resolve plugin
Related Issue

Types of changes

[ ] Docs change / Dependency upgrade
[x] Bug fix
[ ] New feature / Improvement
[ ] Refactoring
[ ] Breaking change

Checklist

[x] I have added changeset via pnpm run change.
[ ] I have updated the documentation.
[ ] I have added tests to cover my changes.

The Description of this PR is too brief and does not introduce the background of this change.

The Description of this PR is too brief and does not introduce the background of this change.

fix:  app-tools builder-webpack 没注册公共的 plugin(builderPluginAdapterModern), 导致缺失一些逻辑。
fix:  把 builder 中的 resolve 插件的一些逻辑抽到 shared 层，是用 modifyBundlerChain 来进行修改。使得上层框架一些共有逻辑可以使用  modifyBundlerChain  来处理，而不用考虑执行顺序等问题


How to augment multi_variate time series data?

I noticed that while augmenting multi-variate time series data, augmented data is concatenated on 0 axes, instead of being added to a new axis ie third axis.
Let suppose data shape is (18,1000), after augmentation it turns to be (72,1000), but i believe it should be (4,18,1000). simply reshaping data.reshape(4,18,1000) resolve the problem or not?

@talhaanwarch An input X should be a numpy array with shape (n,), (N, n), or (N, n, c), where n is the length of each series, N is the number of series, and c is the number of channels. Therefore, if we have a single original time series with 18 channels and 1000 time points, the shape of X should be (1, 1000, 18). Augmenting it by M times will return an output with shape (M, 1000, 18).
X = np.cumsum(np.random.normal(size=(1,1000, 18)), axis=1)  # (1, 1000, 18)
plot(X)

aug = tsaug.RandomTimeWarp() * 4
X_aug = aug.run(X)    # (4, 1000, 18)
plot(X_aug)

How can I get an original signal after augmentation, I think I lost that, if I don't save it explicitly and then concatenate augmented and the original signal


Single export (RAFT in full) possible?

Hi there,
I didn't find any other possibility to contact you, so I created this issue.
Could you let me know why you decided to do three separate exports of the three submodels? Wouldn't it theoretically be possible to export the full RAFT model as it is and then let it run completely on a GPU?
I am asking as I am trying this at the moment, but am running in some problems during C++ Libtorch inference. Did you try this as well and did you run into similar problems?
Best
Christian

I haven't tried to do anything with this project yet, but maybe the 3 exports are due to the 3 main blocks of RAFT. RAFT is not just a straight feed forward neural net, it has the feature extraction block (f_net), the context encoder (c_net) and the update block.
Here's a (very) high level overview of how RAFT works:

f_net extracts features from frame 1 and frame 2
c_net extracts features from frame 1 (reference frame)
The Correlation Pyramid is obtained from the features from f_net
The Lookup operator samples features from the Correlation Pyramid
Both the c_net features and the sampled correlation features are passed to the update block for iterative refinement
And finally the output is upsampled Via Convex Upsampling.

I haven't tried to do anything with this project yet, but maybe the 3 exports are due to the 3 main blocks of RAFT. RAFT is not just a straight feed forward neural net, it has the feature extraction block (f_net), the context encoder (c_net) and the update block.
Here's a (very) high level overview of how RAFT works:

f_net extracts features from frame 1 and frame 2
c_net extracts features from frame 1 (reference frame)
The Correlation Pyramid is obtained from the features from f_net
The Lookup operator samples features from the Correlation Pyramid
Both the c_net features and the sampled correlation features are passed to the update block for iterative refinement
And finally the output is upsampled Via Convex Upsampling.

The ovweview of RAFT is right. But why a network with multiple networks as components can not be exported as ONNX? RAFT itself is also a network, it must can be transfered once all its op are defined in torch.onnx opset


[Bug?]: Error: Hydration Mismatch with component from node_modules

Duplicates

[X] I have searched the existing issues

Latest version

[X] I have tested the latest version

Current behavior 😯
When I try to import a component from the current project no issue
If I export the same component to another project, i have an hydration issue :
Error: Failed attempt to create new DOM elements during hydration. Check that the libraries you are using support hydration.
    at create (dev.js:124:37)
    at fn (dev.js:129:120)
    at index.tsx:127:3
    at Icon (index.tsx:146:10)
    at dev.js:552:12
    at untrack (dev.js:442:12)
    at Object.fn (dev.js:548:37)
    at runComputation (dev.js:698:22)
    at updateComputation (dev.js:681:3)
    at devComponent (dev.js:559:3)
dev.js:278 Uncaught (in promise) Error: Hydration Mismatch. Unable to find DOM nodes for hydration key: 0-0-0-0-0-0-0-0-0-1-0-0-0-0-0-0-1-0-0-3-0-0
    at getNextElement (dev.js:278:37)
    at ErrorBoundary.tsx:32:3
    at ErrorMessage (ErrorBoundary.tsx:59:79)
    at dev.js:552:12
    at untrack (dev.js:442:12)
    at Object.fn (dev.js:548:37)
    at runComputation (dev.js:698:22)
    at updateComputation (dev.js:681:3)
    at devComponent (dev.js:559:3)
    at createComponent (dev.js:1265:17)

Expected behavior 🤔
Should render the component without hydration issue.
Steps to reproduce 🕹
Steps:

Create a solid-start project (A) and create a component
Create a solid-start project (B) with SSR Enabled, Install project A as deps (PNPM)
Import component into project B in src/routes/index.tsx
Go to this page

Context 🔦
No response
Your environment 🌎
System : POP OS 22.04

Node : v18.18.2

PNPM : 8.7.5

    "solid-js": "1.8.5",
    "solid-start": "^0.3.9",
    (Same between project A and B)

VITE CONFIG :
import legacy from '@vitejs/plugin-legacy';
import solid from 'solid-start/vite';
import imagemin from 'unplugin-imagemin/vite';
import { defineConfig } from 'vite';

export default defineConfig({
  plugins: [
    solid({
      ssr: true,
    }),
    legacy({
      targets: ['defaults', 'not IE 11'],
    }),
    imagemin(),
  ],
});

I have created a sample reproduction :

Project who export a cmp : https://github.com/qlaffont/solid-start-cmp
Project who use this cmp : https://github.com/qlaffont/solid-start-project / https://github.com/qlaffont/solid-start-project/blob/master/src/routes/index.tsx

also having this issue

Me too experienced this issue

@wakaztahir @qlaffont I found that this was a problem on build, Solid builds differently for server and client, maybe using something like this can help you guys as well, I got this fixed using the rollup preset that supports this.
You guys can also look at the differences on the solid playground that has different output modes for each type of compilation.

Helpful resource: https://www.youtube.com/watch?v=0zadjVUV7zM&list=PLU7qJA_m4fneqc9S7MvJAEB5JNBeafxA8&index=3&t=3054s

this is probably not an issue with Solid Start itself, but just a warning that our code really doesn't support hydration as it mentions

@gabrielmfern for me is not related with the code because i use the same code and if the component is on the project i have no hydration issue

@gabrielmfern for me is not related with the code because i use the same code and if the component is on the project i have no hydration issue

I didn't mean a problem directly with the code, I meant a problem in our end not in Solid Start's.
The same happened exact thing was happening to me, as I mentioned if you want to import the library you'll need to compile in a specific way for Solid to run hydration properly. The error doesn't happen when you have the code in the project because when building/running dev with vite it already generates the code for hydration properly.

I understand you point but i'm importing the source code and not the compiled version of the component so for me it doesn't make sense

I understand you point but i'm importing the source code and not the compiled version of the component so for me it doesn't make sense

maybe it won't fail if you add noExternal: ['PACKAGE_NAME'] to your ssr vite config

@qlaffont were you able to fix it?

The error starts happening barely a few minutes after you initialise the project (I'm using the drizzle starter) and with every save/hmr the error pops up. This is a huge barrier for those trying out solid start for the first time.

@robertwach Hydration mismatches can happen for a number of reasons. It is more likely that these issues are unrelated. If you have a reproduction I recommend reporting a seperate issue.

@robertwach Hydration mismatches can happen for a number of reasons. It is more likely that these issues are unrelated. If you have a reproduction I recommend reporting a seperate issue.

Thanks for the quick reply, I fixed the issue by just changing the starter template to prisma. Much appreciation for this amazing framework.


[Typescript] raw query with native bigint parameter binding

Environment
Knex version: 0.95.14
Database + version: MySQL 5.7.33
OS: MacOS 10.15.7
If issue is about TypeScript definitions, tag @lorefnon.
Feature discussion / request
I am trying to use raw query with native bigint.
const rawQuery = 'INSERT INTO `my_table`(`name`, `credit`) VALUES(?, ?)';
await knex.raw(rawQuery, ['my_name', 1000n]);

Although this statement works well on javascript(looks like the bigints are converted into strings), I get this error on typescript.
error TS2769: No overload matches this call.
  Overload 2 of 3, '(sql: string, bindings: readonly RawBinding[] | ValueDict): Raw<any>', gave the following error.
    Type 'bigint' is not assignable to type 'Value | QueryBuilder<any, any>'.

It seems it's because type Value does not contain bigint.
https://github.com/knex/knex/blob/9f4db5ee2284a21899ac17011e9531e5976f3852/types/index.d.ts#L413-L424
Of course, that query above doesn't have to be written in raw expression, but I'm using other complicated raw queries too.
How about adding bigint there? If it should not, then how should I handle the raw query with native bigint?

This is not safe, because not sure all drivers supports bigint. I advise you test corner cases, i.e. inserting  BigInt(Number.MAX_SAFE_INTEGER)+BigInt(2) - it should insert<PHONE_NUMBER>740993.
(I've done some research in #3710, but unfortunately gave up, feel free to use for new PR)

Just ran into this as well. Postgres supports bigints, so we are attempting to pass bigints into our knex queries as parameters and noticing that the typing doesn't allow it. We're having to cast the bigint into a number as a workaround, which is not great.
Example:
const query = knex('locations')
	.join('team_users', 'locations.team_id', '=', 'team_users.team_id')
    .whereIn('locations.team_id', teamIds as unknown as number[])
    .where('team_users.user_id', userId as unknown as number);

The full error, without casting, is:
No overload matches this call.
  Overload 1 of 18, '(columnName: "team_users.user_id", value: DbColumn<any> | null): QueryBuilder<any, DeferredKeySelection<any, never, false, {}, false, {}, never>[]>', gave the following error.
    Argument of type 'bigint' is not assignable to parameter of type 'DbColumn<any> | null'.
  Overload 2 of 18, '(columnName: string, value: Value): QueryBuilder<any, DeferredKeySelection<any, never, false, {}, false, {}, never>[]>', gave the following error.
    Argument of type 'bigint' is not assignable to parameter of type 'Value'.
  Overload 3 of 18, '(sql: string, bindings?: RawBinding | readonly RawBinding[] | ValueDict | undefined): QueryBuilder<any, DeferredKeySelection<any, never, false, {}, false, {}, never>[]>', gave the following error.
    Argument of type 'bigint' is not assignable to parameter of type 'RawBinding | readonly RawBinding[] | ValueDict | undefined'.ts(2769)


Laravel 10.x Compatibility

Ensure package is compatible with Laravel 10.x.

Cannot proceed until https://github.com/JackieDo/Laravel-Dotenv-Editor provides Laravel 10.x support. There is a pull request on the repo that adds it, so we'll wait until it's merged.
https://github.com/JackieDo/Laravel-Dotenv-Editor/pull/48


Closes: #1

Updated validations.py python script.
Fixed the behavior of validate_user function in validations.py by verifying that the first character is a letter.

@googlebot I signed it!


Data Structure Writeup

link to blog

Total Points 3.7875 / 4
Extra Points 0 / 1
Collections - Total 3 / 3, Grade 1/1
Blog Python Model code and SQLite Database.
Show your unique collection/table in database, display rows and columns in the table of the SQLite database from VSCode using SQLite3 Editor.
Show your unique code that was created to initialize table and create test data from VSCode model.
Lists and Dictionaries - Total 3/3, Grade 1/1
Blog Python API code and use of List and Dictionaries.
Show a list as extracted from database as Python objects in VSCode using Debugger.
Show two distinct examples of dictionaries, show Keys/Values using debugger in VSCode.
APIs and JSON - Total 6/7, Grade 0.85/1
Blog Python API code and use of Postman to request and respond with JSON.
Show Python API code definition for request and response using GET, POST, UPDATE methods in VSCode. Discuss algorithmic condition used to direct request to appropriate Python method based on request method.
Show algorithmic conditions used to validate data on a POST condition in VSCode.
Show URL request and Body requirements for GET, POST, and UPDATE methods in Postman.
Show the JSON response data for 200 success conditions on GET, POST, and UPDATE methods in Postman.
Show the JSON response for error for 400 when missing body on a POST request in Postman.
Show the JSON response for error for 404 when providing an unknown user ID to a UPDATE request in Postman.
Frontend - Total 7.5/8, Grade 0.9375/1
Blog JavaScript API fetch code and formatting code to display JSON.
Show response of JSON objects from fetch of GET, POST, and UPDATE methods in Chrome inspect.
Show a demo (GET) of obtaining an Array of JSON objects that are formatted into the browsers screen in the Chrome browser.
Describe fetch and method that obtained the Array of JSON objects in JavaScript code.
Show code that performs iteration and formatting of data into HTML in JavaScript code.
Show a demo (POST or UPDATE) gathering and sending input and receiving a response that show update. Repeat this demo showing both success and failure in the Chrome browser.
Show and describe code that handles success. Describe how code shows success to the user in the Chrome Browser screen in JavaScript code.
Show and describe code that handles failure. Describe how the code shows failure to the user in the Chrome Browser screen in JavaScript code.
Optional/Extra, ML Algorithm Analysis - Total 0/5, Grade 0/1
Machine Learning Algorithm Analysis
Show algorithms and preparation of data for analysis. This includes cleaning, encoding, and one-hot encoding.
Show algorithms and preparation for predictions.
Discuss concepts and understanding of Linear Regression algorithms.
Discuss concepts and understanding of Decision Tree analysis algorithms.


Support Mandarin?

In the language support table, only English supports acoustic adaptation.
However, I can select zh-CH locale in custom speech portal -> adaptation data. Does it mean Mandarin also support acoustic adaptation? Thanks.

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

ID: 50d8bb98-fbcd-7562-99ed-54211fd9afd3
Version Independent ID: bd23e619-aee5-2b6e-b2d7-03ab5f7302af
Content: Create an acoustic model with the Speech Service - Azure Cognitive Services
Content Source: articles/cognitive-services/Speech-Service/how-to-customize-acoustic-models.md
Service: cognitive-services
GitHub Login: @PanosPeriorellis
Microsoft Alias: panosper

@hei9gag Thank you for the feedback!  We are investigating this and will get back to you shortly.

@hei9gag Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@PanosPeriorellis Hi, there is a difference between the Azure portal and the document, can you please check it and update the document  as necessary? Thanks a lot!

@YutongTie-MSFT please reassign to @erhopf

@hei9gag , We do support acoustic adaptation for zh-CN | Chinese (Mandarin, simplified).
Please see https://docs.microsoft.com/en-us/azure/cognitive-services/speech-service/language-support. Thank you.

#please-close

Thanks all!


Added get all groups and users implementation

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


Cluster fails to read non-existing value on start

OSX 10.11.5
Last login: Tue Jul 12 16:58:43 on ttys001

| ~ @ Antons-MBP-2 (necrogami)
| => /Applications/Kube-Cluster.app/Contents/Resources/up.command; exit;
Data disks do not exist, they will be created now ...
Creating 2GB Data disk for Master ...
2GiB 0:00:01 [1.49GiB/s] [=======================================================================================>] 100%
Created 2GB Data disk for Master
Please type Nodes Data disk size in GBs followed by [ENTER]:
[default is 10]:
Creating 10GB Data disk for Node1...
10GiB 0:00:06 [1.48GiB/s] [=======================================================================================>] 100%
Created 10GB Data disk for Node1
Creating 10GB Data disk for Node2...
10GiB 0:00:06 [1.48GiB/s] [=======================================================================================>] 100%
Created 10GB Data disk for Node2
Starting k8smaster-01 VM ...
[WARN] unable to run "defaults read /Library/Preferences/SystemConfiguration/com.apple.vmnet.plist" Shared_Net_Address ...
[WARN] ... assuming macOS default value (<IP_ADDRESS>)
[WARN] unable to run "defaults read /Library/Preferences/SystemConfiguration/com.apple.vmnet.plist" Shared_Net_Mask ...
[WARN] ... assuming macOS default value (<IP_ADDRESS>)
[ERROR] exit status 1
Master VM has not booted, please check '~/kube-cluster/logs/master_vm_up.log' and report the problem !!!
Press [Enter] key to continue...

this is corectl problem , I opened an issue at https://github.com/TheNewNormal/corectl/issues/83

ok, issue is fixed with the latest corectl v0.7.9 to which you can update via corectl.app menu option Check for corectld updates


v2.4.7/8 bug

I am not sure what exactly is causing this. Will try to figure it out when I get some time.
In the meanwhile, if you can get something out of this error, it would be great!
The same code works fine with 2.4.6. setSeriousness is a meteorMethod in a collection and the same Class has an afterSave event, which seems to be triggering this error.
 => awaited here:
    at Promise.await (/opt/s.portal/app/programs/server/npm/node_modules/meteor/promise/node_modules/meteor-promise/promise_server.js:60:12)
    at [object Object]._.extend.apply (packages/ddp-server/livedata_server.js:1624:22)
    at callStandardMeteorMethod (packages/jagi:astronomy/lib/modules/storage/utils/callStandardMeteorMethod.js:7:21)
    at Class.applyMethod (packages/jagi:astronomy/lib/modules/methods/class_prototype_methods/applyMethod.js:18:10)
    at Class.setSeriousness (packages/jagi:astronomy/lib/modules/methods/utils/wrapMethod.js:23:16)
    at Class.create.events.afterSave (common/imports/api/group/collection.js:398:33)
    at packages/jagi:astronomy/lib/modules/events/class_prototype_methods/dispatch_event.js:43:5
    at arrayEvery (/opt/s.portal/app/programs/server/npm/node_modules/meteor/jagi_astronomy/node_modules/lodash/_arrayEvery.js:16:10)
    at every (/opt/s.portal/app/programs/server/npm/node_modules/meteor/jagi_astronomy/node_modules/lodash/every.js:53:10)
    at Class.dispatchEvent (packages/jagi:astronomy/lib/modules/events/class_prototype_methods/dispatch_event.js:42:3)
    at triggerAfterSave (packages/jagi:astronomy/lib/modules/storage/utils/trigger_after_save.js:5:6)
    at documentUpdate (packages/jagi:astronomy/lib/modules/storage/utils/document_update.js:97:5)
    at Class.save (packages/jagi:astronomy/lib/modules/storage/class_prototype_methods/save.js:144:20)
    at Class.create.meteorMethods.setSeriousness (common/imports/api/group/collection.js:493:10)
    at [object Object].astronomyExecute (packages/jagi:astronomy/lib/modules/methods/meteor_methods/astronomyExecute.js:34:17)

It's hard to tell without reproduction. It looks like the problem is in the meteor-promise package.

The problem arises due to a recursion happening when I run a meteorMethod in afterSave which saves the same document. It happened when I created a new document, after which afterSave ran, modified the doc and then went into an infinite loop.
I am not sure if it is a bug or a problem with my code. But somehow, this code had no issues earlier. Still, I secured my code by moving the change on afterUpdate instead of afterSave, and the problem has gone.
I will try to dig deep later, but for now I will close this.


Keyword arguments in JIT function calls

Fix #728: Add keyword argument support for Overloaded objects.
Fix #729: Support calling functions with keyword arguments inside a numba compiled function.

This looks good to me.

Yeah, I needed this over the weekend.

Although, I think we need to get funcsigs into our binstar account (and then eventually into anaconda) before we merge this.  Requiring pip in a conda environment to get a Numba dependency is not something we want to do.

Ok, I've pushed some conda packages for funcsigs.

Excellent.  I especially like that keyword argument support works when calling nopython mode functions from inside nopython mode.


Add support for private keys provided as strings

Note: happy to update documentation for this once merged.

This request provided the ability for private keys to be provided as strings.
Use Case: When working with systems with ephemeral filesystems one would need to put the key file on the server, potentially committing it to git which is a fairly large security hole.
This means that you can safely use this plugin on Heroku.

Unfortunately I can't merge it at this moment - 3 test are failing:

test_if_challenge_is_valid
test_if_challenge_request_is_invalid_if_it_is_larger_than_256_bytes
test_if_challenge_request_is_invalid_when_is_smaller_than_128_bits

Figured out what my issue was.
The fixtures persisted in the db after my initial test runs and so when removing code form the test_helper and running test to see if things worked there was a hidden bug, the fixtures were not loaded.
Might be worth using a db cleaner? Either way, latest push should fix the things I broke!

Merged, thanks! :)


rechunker object has no attribute "persist"

using 0.4.2, when trying to persist a Rechunker object on a dask cluster, an AttributeError gets raised.
E.g. when running the tutorial, cell 11 raises:
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
<ipython-input-11-d4bee8fff75b> in <module>
----> 1 future = array_plan.persist()
      2 progress(future)

AttributeError: 'Rechunked' object has no attribute 'persist'

OK, it seems that an array_plan.plan.persist() is needed instead. I will make a PR

Thanks for reporting!
I'm puzzled why this API has changed.

This seems to be the cinnut that introduced the change https://github.com/pangeo-data/rechunker/commit/b6b4a52c72c0d3bc497bc6bb6f6c7b7a48ed760f


Use policy name instead of config file parameter

Reading through the PR it is not clear what is what. Config is now an overloaded term, in topaz config was/is referring to the configuration of the topaz engine, now we are introducing config for the topaz CLI, and allow 0:N different topaz engine instance configurations which are going to be named. I would suggest we use the term config for the topaz CLI configuration and contexts as the named entity for a topaz enginer configuration


Meaningful Use -> CMS Quality Reporting Programs

This PR goes along with https://github.com/projecttacoma/bonnie/pull/868.
Pull requests into Bonnie require the following. Submitter and reviewer should :white_check_mark: when done. For items that are not-applicable, note it's not-applicable ("N/A") and :white_check_mark:.
Submitter:

[x] This pull request describes why these changes were made.
[X] JIRA ticket for this PR: https://jira.mitre.org/browse/BONNIE-1113
[x] JIRA ticket links to this PR
[X] Code diff has been done and been reviewed
[X] If UI changes have been made, google WAVE plug-in has been executed to ensure no 508 issues were introduced.
[X] Tests are included and test edge cases (N/A--too simple of a change)
[X] Tests have been run locally and pass (remember to update Gemfile when applicable)
[X] Automated regression test(s) pass

If JIRA tests were used to supplement or replace automated tests:

[X] JIRA test links: (N/A)
[X] Justification for using JIRA tests: (N/A)
[X] JIRA tests have been added to sprint (N/A)

Reviewer 1:
Name: @jbradl11

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

If JIRA tests were used to supplement or replace automated tests:

[ ] JIRA tests have been run and pass
[ ] You agree with the justification for use of JIRA tests or have provided input on why you disagree

Reviewer 2:
Name: @c-monkey

[ ] Code is maintainable and reusable, reuses existing code and infrastructure where appropriate, and accomplishes the task’s purpose
[ ] The tests appropriately test the new code, including edge cases
[ ] You have tried to break the code

If JIRA tests were used to supplement or replace automated tests:

[ ] JIRA tests have been run and pass
[ ] You agree with the justification for use of JIRA tests or have provided input on why you disagree

@c-monkey @hossenlopp Bridget has ok'd this modification. Please review.


Cannot select entities inside the scene viewport.

Only entities with a texture attached to a sprite component cannot be selected.

Issue was fixed in the most recent commit 155 9a6d3abb3058844cfd3b0a5aa78d093bb4026e94


ApplePay - onClick event

Is your feature request related to a problem? Please describe.
I need to intercept button click to like i can do with Google Pay.
Describe the solution you'd like
Exactly the same as Google Pay button.
Describe alternatives you've considered
Rendering button myself and adding logic myself.

Hi @lluzak,
Thanks for opening this issue. We were planning on to adding support for this, but we prioritized it. (See PR #592).
I'll close this ticket, feel free to reopen if you have any more comments or feedback on this.
Hope this helps!


remove hypens that mark linebreaks

Since the text flows differently on small phone screens than on printed paper the app should detect words that are separated by hyphens and remove the hyphen.

That would be a nice touch.

included in next release


Example publishing a tweet with preview

I am trying to publish a tweet that contains a shorted nurl (http://foo.com/123) that represents a seperate url. When I publish, the preview information is not being shown on the tweet, just the shortened url. I have tried to find a way to embed the original url in there, in hopes that Twitter will preview that url, but have had no luck. Is there an easy sample to do this?

Hello there,
What do you mean by publishing a tweet with preview?
Cheers,
Linvi

First example here
https://developer.twitter.com/en/docs/tweets/data-dictionary/overview/intro-to-tweet-json

Hello there,
I can look into it further but I have not yet found anything in the documentation that would suggest how to configure this "preview".
This feature (if supported by API 1.1) will be done in next version.
Cheers,
Linvi

It seems like you just need a url object to entities

The link you provide is the json returned by Twitter for a tweet.
The main question is to figure out how to "POST" a tweet similar to this.
You can find the documentation here : https://developer.twitter.com/en/docs/tweets/post-and-engage/api-reference/post-statuses-update
But nothing mentions this feature.
I will speak with Twitter staff to see if the documentation has not been updated but as I mentioned I cannot make this a priority right now.

Did you ever have a chance to chat with Twitter? If it is easy, I might be able to do a pr

Hello there,
Unfortunately I did not yet have time to mention this limitation to twitter.
You can do so here : https://twittercommunity.com/
If you want to do a PR I will be more than happy to look at it.
Though would you please create it against Tweetinvi 5.0 which is now available in the master branch.
Thanks,
Linvi


Quickly switch (search) open tabs

Hi,
It would be great to have the Vimium Shift+T functionality, which allows a user to search through their open tabs with fuzzy matching.
the shortcuts b and shift+b (new tab) for searching for the bookmarks would also be awesome to have.
Thanks for the awesome work!

I bought "tab Switcher" app because of the lack of this feature. Having this one built-in would be really great.

For those who don't know, safari (tested on 14.0.1) has a Shift-Command-\ short-cut that lets you search open tabs. It's not fuzzy search but gets the job done. Agree having this built-in to Vimari would be great though.

For those who don't know, safari (tested on 14.0.1) has a Shift-Command-\ short-cut that lets you search open tabs. It's not fuzzy search but gets the job done. Agree having this built-in to Vimari would be great though.

The only downside to the tab overview suggested above is that as far as I know there's no way to use the keyboard to select a searched result! You still have to move to the mouse to select the resulting tab, otherwise this would be a fine replacement.


Machinist syntax features

So, I like the brevity of the machinist syntax, but factory_girl has some features that put it ahead (like FactoryGirl.reload, for one).  However, the machinist syntax is much more in-depth than factory_girl's implementation is.  It would be great to have the following:

User.blueprint(:admin) do ... end -- to define multiple blueprints on a model
User.make :admin, last_name: 'AdminGuy' -- using the above feature

Machinist doesn't have the following feature, but factory_girl already does, so it would be great to also have this:
User.make :admin, do |u|
  u.last_name = 'Grrrr' if some_function_returns_a_boolean
end

Blocks are good!

@wulftone we were actually thinking of either deprecating the various syntaxes (to be removed) or extracting them out to separate gems that other maintainers can manage. What do you think?

Ah, well, I much prefer the Machinist syntax--it's shorter and easier to remember what model you're actually making.  With the regular FactoryGirl syntax, I end up with factories labeled :this_or_that_kind_of_user instead of just User.make :some_variant, and the namespace doesn't get polluted if I want a User.make :admin and an Address.make :admin, so things are much clearer in general.
Though I think these things could be maintained by non-core FactoryGirl people, it'd probably turn out better if the core group maintained them since they're already deeply immersed in the codebase and will be more likely to be aware of any potential issues.

I'm open to looking at any pull requests you write modifying the existing machinist syntax, assuming it behaves like the existing machinist code does. The idea is that the machinist wrapper shouldn't modify any existing behavior of factory girl, so that should keep the pull request small. Closing this issue, and I'll keep an eye out for any pull requests. Thanks!