Include Header files in BridgingHeader without --no-package-directories

I use Swift and have a file translated as:

I do not use this option: --no-package-directories.
In my BridgingHeader I have to include the file as:
#import "BTimer.h" instead of #include "core/helper/timer/BTimer.h".
Why does the second version fail? The packages included with j2objc can also be included like:
#import "java/util/List.h"

Always use #import not #include.
Follow the instructions regarding USER_HEADER_SEARCH_PATHS here:
https://github.com/j2objc-contrib/j2objc-gradle/blob/master/FAQ.md#how-do-i-manually-configure-my-xcode-project-to-use-the-translated-libraries

There's no modification to the plugin required here.


Task :react-native-community_masked-view:mergeReleaseGeneratedProguardFiles FAILED

Bug
Hi, it makes it impossible to compile my application for Android with "assembleRelease", I tried to redo a project but same problem.
Error :
> Task :react-native-community_masked-view:mergeReleaseGeneratedProguardFiles FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':react-native-community_masked-view:mergeReleaseGeneratedProguardFiles'.
> Collection contains no element matching the predicate.

Environment info
react-native info output:
 System:
    OS: macOS 10.15.4
    CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
    Memory: 465.12 MB / 16.00 GB
    Shell: 5.7.1 - /bin/zsh
  Binaries:
    Node: 12.16.2 - /usr/local/bin/node
    Yarn: 1.12.1 - /usr/local/bin/yarn
    npm: 6.14.4 - /usr/local/bin/npm
    Watchman: 4.9.0 - /usr/local/bin/watchman
  Managers:
    CocoaPods: 1.9.1 - /usr/local/bin/pod
  SDKs:
    iOS SDK:
      Platforms: iOS 13.4, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
    Android SDK: Not Found
  IDEs:
    Android Studio: 3.5 AI-191.8<IP_ADDRESS>77832
    Xcode: 11.4/11E146 - /usr/bin/xcodebuild
  Languages:
    Java: 11.0.1 - /usr/bin/javac
    Python: 2.7.16 - /usr/bin/python
  npmPackages:
    @react-native-community/cli: Not Found
    react: 16.11.0 => 16.11.0
    react-native: 0.62.2 => 0.62.2
  npmGlobalPackages:
    *react-native*: Not Found

Library version: 0.1.10
Steps To Reproduce

react-native init project
install React Navigation (https://reactnavigation.org/docs/getting-started)
cd android
./gradlew assembleRelease

And error.

Same problem on windows

try to use :
cd android && gradlew clean

try to use :
cd android && gradlew clean

thanks @DurandSacha this solved the issue for me :D

I tried running  cd android && gradlew clean and didn't work for me :/
* What went wrong:
Execution failed for task ':react-native-community_masked-view:compileDebugJavaWithJavac'.
> Could not find tools.jar. Please check that /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home contains a valid JDK installation.

Facing the same issue as @roadev

Facing the same issue as @roadev

@vallavans @roadev @oneberto
After setting
org.gradle.java.home=/adoptopenjdk-8.jdk/Contents/Home
in gradle.properties
It fixes that issue above. Hope it helps someone.

@vallavans @roadev @oneberto
After setting
org.gradle.java.home=/adoptopenjdk-8.jdk/Contents/Home
in gradle.properties
It fixes that issue above. Hope it helps someone.

Thanks @hengsok, It worked for me

@rohit7209 no worries. Glad it helps you! Happy coding.

hi, can anybody solve it? I have the same problem with lottie.

Task :lottie-react-native:mergeReleaseGeneratedProguardFiles FAILED

FAILURE: Build failed with an exception.

What went wrong:
Execution failed for task ':lottie-react-native:mergeReleaseGeneratedProguardFiles'.

Collection contains no element matching the predicate.

I have the same issue please helpp

Task :react-native-community_masked-view:compileDebugJavaWithJavac FAILED

Hi! After some days i resolve the issue by rub this command in terminal
cd android && gradlew clean
But if it not work for you so rebuild your project and it will work.

Thanks to help @mamonaabdullah122


Null reference exception at ServerRequestParameters.ts in populateQueryParams

Library

[x]<EMAIL_ADDRESS>
Framework
Found while using Angular 9 with @azure/msal-angular 1.0.0-beta.4 but that's irrelevant, the bug is in msal-core.
Description
There is a null reference bug at msal-core/src/ServerRequestParameters.ts in function 'populateQueryParams' at line 116:
// sanity check for developer passed extraQueryParameters
const eQParams: StringDict = request.extraQueryParameters;
Where 'request' can be null. There is a check above on line 88 'if (request)' but line 116 is outside of that.
This happens when the 'populateQueryParams' is called from msal-core/src/UserAgentApplication.ts
in function 'acquireTokenSilent' at line 644:
serverAuthenticationRequest.populateQueryParams(account, null, adalIdTokenObject);
Note the second param passed is null.
The code in ServerRequestParameters.ts line 116 should have a null check or be moved into the above 'if (request)' block.
Security
No
Regression
Unknown
Configuration
Irrelevant.
Reproduction steps

Call acquireTokenSilent with AuthenticationParameters containing values set to flow into this block on line 640 of UserAgentApplication.ts:
// if user didn't pass login_hint/sid and adal's idtoken is present, extract the login_hint from the adalIdToken
else if (!account && !StringUtils.isEmpty(adalIdToken)) {
See that null gets passed on line 644
And that in line 116 of ServerRequestParameters.ts a null exception occurs causing a runtime script exception visible in the console.

Expected behavior
Expect no script errors, and for aquireTokenSilent to function correctly.
Browsers
Not browser specific.

This is the commit which introduces the bug: https://github.com/AzureAD/microsoft-authentication-library-for-js/commit/bf86b898d120760e4a1c62126becd088deb78b55#diff-01b40b5f69b6021ac7031ce85ef0d452L120-L123

@Porges It is not getting typechecked because strictNullChecks is disabled (which we are aware of and plan to fix, #1097).
I'll take a look at that PR, thanks!

@JasonPaape This was included in<EMAIL_ADDRESS>which was just released. Let us know if this is still an issue. Thanks!


jetbrains

Please, when it is used in jetbrains?

I don't use JetBrains. You need to ask someone from that community to write a similar extension if they don't have it already.


Packing entries into AppendEntries requests is slow

This is closely related to #160. Adding 4000 entries totaling 1 megabyte to the AppendEntries request takes about 900 milliseconds. That's too long.
The first problem is that there's probably too many invocations of request.ByteSize(). It'd be better to accumulate entry.ByteSize() instead as an approximation.
We may also want a limit on the number of entries, since each one requires some CPU time to process.

I started on this, but I want to benchmark it in a real-world scenario, so it probably depends on #168. In case someone (likely @nhardt if anyone) needs it before then, here's a patch that might help:
diff --git a/Server/RaftConsensus.cc b/Server/RaftConsensus.cc
index ee6fab9..196771f 100644
--- a/Server/RaftConsensus.cc
+++ b/Server/RaftConsensus.cc
@@ -2201,6 +2201,7 @@ void
 RaftConsensus::appendEntries(std::unique_lock<Mutex>& lockGuard,
                              Peer& peer)
 {
+    using Core::Util::downCast;
     uint64_t lastLogIndex = log->getLastLogIndex();
     uint64_t prevLogIndex = peer.nextIndex - 1;
     assert(prevLogIndex <= lastLogIndex);
@@ -2235,25 +2236,45 @@ RaftConsensus::appendEntries(std::unique_lock<Mutex>& lockGuard,
     // Add as many as entries as will fit comfortably in the request. It's
     // easiest to add one entry at a time until the RPC gets too big, then back
     // the last one out.
+    //
+    // Calculating the size of the request ProtoBuf is a bit expensive, so this
+    // estimates high, then if it reaches the size limit, corrects the estimate
+    // and keep going.  It gets
+    // the number of calls to request.ByteSize() down to about 15 even with
+    // extremely small entries (10 bytes of payload data in each of 50,000
+    // entries filling to a 1MB max).
     uint64_t numEntries = 0;
+    uint64_t baseSize = downCast<uint64_t>(request.ByteSize());
+    uint64_t currentSize = baseSize;
     if (!peer.forceHeartbeat) {
         for (uint64_t index = peer.nextIndex;
              index <= lastLogIndex;
              ++index) {
             const Log::Entry& entry = log->getEntry(index);
             *request.add_entries() = entry;
-            uint64_t requestSize =
-                Core::Util::downCast<uint64_t>(request.ByteSize());
-            if (requestSize < SOFT_RPC_SIZE_LIMIT || numEntries == 0) {
-                // this entry fits, send it
-                VERBOSE("sending entry <index=%lu,term=%lu>",
-                        index, entry.term());
-                ++numEntries;
-            } else {
-                // this entry doesn't fit, discard it
-                request.mutable_entries()->RemoveLast();
-                break;
+            // Each member of a repeated message field is encoded with a tag
+            // and a length. We conservatively assume the tag and length will
+            // be up to 10 bytes each (2^64), though in practice the tag is
+            // probably one byte and the length is probably two.
+            currentSize += entry.ByteSize() + 20;
+
+            if (currentSize >= SOFT_RPC_SIZE_LIMIT) {
+                // The message might be too big: calculate more exact but more
+                // expensive size.
+                uint64_t actualSize = downCast<uint64_t>(request.ByteSize());
+                assert(currentSize >= actualSize);
+                currentSize = actualSize;
+                if (currentSize >= SOFT_RPC_SIZE_LIMIT && numEntries > 0) {
+                    // this entry doesn't fit and we've already got some
+                    // entries to send: discard this one and stop adding more
+                    request.mutable_entries()->RemoveLast();
+                    break;
+                }
             }
+            // this entry fits, send it
+            VERBOSE("sending entry <index=%lu,term=%lu>",
+                    index, entry.term());
+            ++numEntries;
         }
     }
     request.set_commit_index(std::min(commitIndex, prevLogIndex + numEntries));

This patch does seem to help significantly when you're packing 10 or 100-byte log entries. I wasn't able to measure a significant difference for 1000-byte objects with the benchmark I was running (that had several seconds of overhead).

In the benchmarks I ran on my laptop, the above patch took packing 1MB of:

1000 byte objects down from 60ms to 2ms
100 byte objects down from 4s to 30ms.
10 byte objects (10 bytes of command data, each entry is ~55 bytes, 19064 entries) down to 42ms (original time before patch not measured).

So this patch is definitely needed and pretty much does the job. Leaders flip like crazy with 100-byte objects before the patch and are stable after.
42ms is still a bit high for packing very small entries, so I think I'll limit each request to 5000 entries max as well.


LanguageServerProtocolJSONRPCTests: add Windows stubs

This set of changes is the last set of changes required to build the
entire test suite on Windows.  Although the tests do not yet fully pass,
this is a prerequisite for getting the test suite passing.

Sounds good to me

@swift-ci please test


change to 7d removal of data if not required, solve daily cert OK alerts

https://www.zabbix.com/documentation/3.0/manual/discovery/low_level_discovery
Search for "Keep lost resources period (in days)"

:+1:

:+1:


Validations

@MelindaCardenas @crchong1

Everything looks good to me so far. Lemme know when u add the rest of the validations

things look good to me too, cool regex work 👍 I was also wondering, for dates, is it required for people to use "-" between numerical values (eg: birth date 01-15-1998) or is it possible that a user would use "/" to separate numerical values?

@MelindaCardenas basically we use a datepicker react component to get the date information for us, so we dont have to worry about people entering manual dates

@joeyszhao once you add the username/password validations, just ping me on slack and we can merge


Feature Request Flex Server Node Inject

Feature
Building a server for different types of machines. For each machine I would like to have a dedicated namespace so:
Machinetype1 --> ns=2
Machinetype2 --> ns=3
The different machine types might have similar variables (for example machine state) wich i would like to give the same node id on both machine types so for example:
Machine State i=1001
Leading to:
Machinetype1 --> ns=2;i=1001
Machinetype2 --> ns=3;i=1001
To my experiance and trials so far the node id and borsw name must be unique per namespace.
As I underdstand the server so far I can only add nodes to ns=1 on the aso server.
Request:
Either give the ability (or descirbe if it is already possible) to add namespaces to the aso server
or
I can crate the namespaces with the flex server and then allow to inject objects into the flex server by selecting the node type and organizaional node.
At the moment I have the feeling that I would have to code the full server object stack inside the Flex server address space tab which to my oppinion is not the node-RED way to do it.
Thanks and best regards!

I would prefer the flex server in that case and you'll have all features of node-opcua


App Center distribute fails since 7/6/2022

App Center is failing on distributing to IOS TestFlight beginning on 7/6/2022. I think they are aware of it, but it continues - and we are on day 3!

Seeing the same.  Return Internal Server Error.  If I try to reconnect to the Store it says" "No apps found on App Store Connect" even though prior to 7/6/2022 everything was working fine and we made no change.  If I push the build from AppCenter via Transporter it works fine.

Any news here?

Still down for me this morning and this is what the Status page says (see below).  Wondering what the "external dependency" is but it's hard to rely on AppCenter when there is this much down time.  First the new xcode versions not being available for weeks and now this.  Good product but needs to be more reliable.
From status page:
Distribute is Experiencing Issues
Update - We are continuing to investigate this issue.
Jul 11, 12:01 UTC
Investigating - App Center is experiencing issues when distributing to the Apple App Store due to an external dependency.
We apologize for the inconvenience.
Jul 7, 11:04 UTC

We still have the service connection through ADO, but yeah now can't use appcenter anymore

Any updates?

Their status page report this about an hour ago:
Monitoring - A fix has been implemented and we are monitoring the results. In order for your build to
pick up the changes, you need to open your build configuration and just click save. Jul 12, 14:10 UTC

Still does not work for me either.

Adding this here since it looks like it's related:
https://github.com/fastlane/fastlane/issues/20444

The distribution target in our build configuration is App Store Connect Users, but the build was distributed to Collaborators group.
I've saved twice, but the build still went to Collaborators.
Is App Center forcing distribution to Collaborators group, ignoring the build configuration?

is this issue related to apple app store connect as well?

Any update on this?
Still having issues.

Same here. Still having issue to distribute the build. Seems they last updated on 13rd July.

I contacted App Center support and they gave me another temporal workaround:

Build app through App Center without distribution step. You can disable the "Distribute build" section in your branch configuration on App Center.

Download the .ipa

Run the following command (works only on Mac)
xcrun altool --upload-app -f <PathToFile>.ipa -u <Username> -p <app-specific-password> -type <the-type>

In case of errors or conflicts, consult manual for altool (man altool)
  --type "{macos | ios | appletvos}".
This has worked for me in case anyone else is stuck.

I dont know if anyone is following here but https://github.com/fastlane/fastlane/issues/20444#issuecomment-1188134428

hey so its fixed https://github.com/fastlane/fastlane/pull/20480 I was able to push to store with appcenter

hey so its fixed fastlane/fastlane#20480 I was able to push to store with appcenter

Same, built and distributed to App Store just now.

Issue is fixed


Sprint 27 Review

Added

Added --quiet grunt CLI flag for suppressing linter warnings.
Added JS unit testing and code coverage through Mocha and Istanbul.
Added cf-notifications stylesheet to style notifications
Added cf_notifier plugin for sending UI notifications
Added cf_formValidator plugin for validating form inputs
Added Grunt build task and set it as default.

Changed

Updated grunt-browserify to ^3.8.0.
Updated grunt-eslint to ^13.0.0.
Moved eslint config file to home directory.
Moved jQuery download to package.json.
Updated grunt-banner to ^0.4.0 and updates banner ascii art and format.
Changed bower.json authors array field to use homepage in place of url,
and adds email field.
Adds path variables to Gruntfile.
Updated form-validation script to use cf_formValidator and cf_notifier
Changed Grunt jsdev and cssdev to js and css.
Moved testing to build task.

Fixed

Fixed macro on offices page template
Fixed subscribe macro in events archive and archive single, and press
resources
Replaced missing string_score library for the type-and-filter plugin

Removed

Removed string-replace:static-legacy Grunt task.
Alert.js plugin
alert macro

Pending PRs

#551, #550, #549
Gruntfile work by @anselmbradford
bugfixes from @kimberlymunoz

Review done.

:+1:


versionist: Add repo.yml file to start versioning commits

So that we can better track bug reports lets start to version this tool.
Signed-off-by: Alex Gonzalez<EMAIL_ADDRESS>

@balena-ci I self-certify!


WAGTAIL_GROUP_USER_PAGES_ISOLATE = [] // if user belongs to group in …

…the list, the user will only see his blogs

Please check the following:

[ ] Do the tests still pass?[^1]
[ ] Does the code comply with the style guide?

[ ] Run make lint from the Wagtail root.

[ ] For Python changes: Have you added tests to cover the new/fixed behaviour?
[ ] For front-end changes: Did you test on all of Wagtail’s supported environments?[^2]

[ ] Please list the exact browser and operating system versions you tested:
[ ] Please list which assistive technologies [^3] you tested:

[ ] For new features: Has the documentation been updated accordingly?

Please describe additional details for testing this change.
[^1]: Development Testing
[^2]: Browser and device support
[^3]: Accessibility Target

Hi @sahilrl - thanks for the contribution. However, I don't think this is a good fit for Wagtail core, for a few reasons:

In Wagtail, this kind of rule is usually managed through permission records (https://docs.wagtail.org/en/stable/topics/permissions.html#page-permissions) - this allows administrative users to update those rules without having to make changes within the codebase. (In fact, by giving users Add but not Edit permission, I believe you could set up something very similar, or identical, to this PR.)
To properly block pages from being edited, customising the index view isn't sufficient, since it's still possible for users to visit the URL to the "edit" view directly, or reach it through some other route (such as the page explorer in the sidebar menu, or a report, or a custom view set up through ModelAdmin). Wagtail has a PagePermissionTester class that all permission checks go through - this logic would be better placed in there.
This is a lot of extra code to handle one specific permission setup - if we added something similar for every setup that a Wagtail user wanted, the codebase would quickly become unmaintainable and developers would be overwhelmed with configuration options. We'd rather look for more general-purpose mechanisms that can be configured in the way the user wants.
Finally, any new feature like this needs to be accompanied by tests and documentation.


cdrkit: fix build with clang 16

Description of changes

Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 266627 run on aarch64-darwin 1

8 packages marked as broken and skipped:

cloud-init
cloud-init.dist
devede
devede.dist
diffoscope
diffoscope.dist
diffoscope.man
zpool-auto-expand-partitions

7 packages built:

cdrkit
cloud-utils
cloud-utils.guest
diffoscopeMinimal
diffoscopeMinimal.dist
diffoscopeMinimal.man
html2text


Etl-68/buckets

Slight bucket refactor in preparation for workflow PR
Instead of just input/output buckets,
renamed input to source
renamed output to parquet
created a bucket called "intermediate" for the unpacked json and the job temp dir

I'm going to merge this PR to unblock some work -- please leave comments if there's an issue and I'll revisit.

@tthyer LGTM


Update version of yaml-cpp to 0.6.2-0f9a586-p1

I've followed this guide
step by step carefully. [Yes]

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/mdouaihy/hunter/builds/25832056
https://travis-ci.org/mdouaihy/hunter/builds/555996029

Testing:

https://ci.appveyor.com/project/ingenue/hunter/builds/25837638
https://travis-ci.org/ingenue/hunter/builds/556100192?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.23.201


Gulp task help descriptors incorrect

Good Morning,
I noticed that the help comments are switched on two tasks, build-rtl reads "Watch files as RTL" and watch-rtl reads "Build all files as RTL".
I was also curious if there could be an effort to remove unneeded tasks conditionally based on your install options. Since I chose to not include RTL in my install, I would prefer that those tasks not be included.
Thanks,
ewh

These options are removed conditionally.
https://github.com/Semantic-Org/Semantic-UI/blob/master/gulpfile.js#L76

Thanks for the reply jlukic.
I did notice that there were conditional statements in ./semantic/gulpfile.js that should be working. Perhaps it is specific to my usage somehow. I'm working in VS2015 (using the task runner explorer), followed the recipes/advanced-usage guide on semantic-ui.com, and imported the watch and build tasks with the specified path (/semantic/tasks/watch and build); However, I have not been able to observe any impact to the tasks when the /semantic/gulpfile.js is edited or even entirely commented out. There doesn't seem to be any caching going on either. I suspect that the expected inheritance is not occurring. By chance are you familiar with this issue?

I've also found that I actually have the gulpfile.js from https://github.com/Semantic-Org/Semantic-UI/blob/master/tasks/config/npm/gulpfile.js at /Semantic/gulpfile.js instead of the one you linked. Perhaps this is an issue?

That is correct, there's actually two ways to install, from npm install semantic-ui and gulp install
I've modified the help text to swap them back


Prioritize non-storage sink links, narrow source link identification

Storage link should only get energy when other links are full.
Look for source links next to mining position only.

This Pull Request has been merged by GitConsensus.
Vote Totals

Yes
No
Abstain
Voters

3
0
0
3

Vote Breakdown

User
Yes
No
Abstain

tedivm
✔

PostCrafter
✔

dragoonreas
✔

Vote Results

Criteria
Result

Has Quorum
True

Has Votes
True


Support for OpenID Connect ID Tokens

This issue was originally created by @AlanTBarlow here, before being automatically moved:
https://github.com/angel-dart-archive/oauth2/issues/8

I am trying to find a way to create an OIDC provider using dart since it is not recommended to use OAuth for authentication and only for authorization. since OIDC is build on top of oauth2, its possible to add the additional features to make this a OIDC packages instead.

@thosakwe commented:
If this is functionality you need, you’re more than welcome to send in a PR, but OpenID Connect is not necessarily on the priority list right now. If you are familiar with the OpenID specification, though, it should probably be pretty to implement on top of the AuthorizationServer class.


Adding options field to ext_management_system

This will add the serialzed column options to ExtManagementSystem.
There is also a migration for ManageIQ::Providers::Kubernetes::ContainerManager options that where saved in CustomAttributes and general settings but should be there. This takes inspiration from https://github.com/ManageIQ/manageiq/pull/13826 and https://github.com/ManageIQ/manageiq/pull/14106 but the options details will be added in a later stage in the appropriate provider modules.
RFE BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1462835

cc @simon3z @blomquisg

I am not sure I understand, if we dont migrate these kubernetes options and
not the ones from the settings, what should we migrate?
On Jun 20, 2017 12:56 AM, "Federico Simoncelli"<EMAIL_ADDRESS>wrote:
@simon3z commented on this pull request.
In db/migrate/20170619161514_add_options_to_ext_management_system.rb
https://github.com/ManageIQ/manageiq/pull/15398#discussion_r122835092:

serialize :serialized_value

end

def up
add_column :ext_management_systems, :options, :text

say_with_time("Migrating Kubernetes provider options") do

 ExtManagementSystem.where(:type =>

"ManageIQ::Providers::Kubernetes::ContainerManager").each do |cp|

   migrated_options = {}

   migrated_options[:image_inspector_repository] =

Settings.ems.ems_kubernetes.image_inspector_repository

   migrated_options[:image_inspector_registry] =

Settings.ems.ems_kubernetes.image_inspector_registry

   CustomAttribute.where(

     :resource_type => cp.type,

     :resource_id => cp.id,

     :section =>

ManageIQ::Providers::Kubernetes::ContainerManager::Scanning::Job::ATTRIBUTE_SECTION,

     :name    =>

ManageIQ::Providers::Kubernetes::ContainerManager::Scanning::Job::PROXY_ENV_VARIABLES).each
do |ca|
@enoodle https://github.com/enoodle I don't think we want to reply on the
Kubernetes module dependency here for this migration. cc @blomquisg
https://github.com/blomquisg
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/ManageIQ/manageiq/pull/15398#pullrequestreview-44984879,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AC-ogKxtxMuepzazq7RdtTYwaxaFyXH5ks5sFu5vgaJpZM4N-kbK
.

I am not sure I understand, if we dont migrate these kubernetes options and
not the ones from the settings, what should we migrate?

@enoodle I don't want you to prepopulate the values in the db for the Settings ones... otherwise we can't change the defaults going forward.
Read more carefully the comment about the kubernetes options, it's about the module dependency.

Current implementation adding a generic options json column to ext_management_system LGTM :+1:.
Of course I am also considering the downside of this approach. The table authentications just recently added the same options json column so I assume we reached the same conclusion on the need for a more flexible field for special best-of-breed options (of course it must be used with care).
For completeness I want to mention that since most of the times (I'd say always?) these are also global settings, e.g.:
:ems:
  :ems_kubernetes:
    :miq_namespace: management-infra
    :image_inspector_registry: docker.io
    :image_inspector_repository: openshift/image-inspector

It's worth mentioning that this could be achieved also using ExtManagementSystem specific settings in the settings_changes table:

id
resource_type
resource_id
key
value

100
ExtManagementSystem
1
/ems/ems_kubernetes/image_inspector_registry
mydockerregistry.io

101
ExtManagementSystem
2
/ems/ems_kubernetes/image_inspector_registry
myotherdockerregistry.io

I am not sure of the implications of this second approach though.
cc @blomquisg

I have added deletion of the old CustomAttribute's with the settings and also made sure that the migration is happening on Kubernetes and Openshift Providers.

@blomquisg @Fryguy can you review?

Database migrations have now been moved to the https://github.com/ManageIQ/manageiq-schema repo.  Please see http://talk.manageiq.org/t/new-split-repo-manageiq-schema/2478 for instructions on how to transfer your database migrations.  If this PR contains only migrations, I will leave it open for a short time during the transition, after which I will close this if it has not been moved over.

cc @Loicavenel


Question: Is oauthlib being stricter than OIDC spec, disallowing use of prompt=none without 'id_token_hint'?

According to the OIDC spec:

id_token_hint
OPTIONAL. ID Token previously issued by the Authorization Server being passed as a hint about the End-User's current or past authenticated session with the Client. If the End-User identified by the ID Token is logged in or is logged in by the request, then the Authorization Server returns a positive response; otherwise, it SHOULD return an error, such as login_required. When possible, an id_token_hint SHOULD be present when prompt=none is used and an invalid_request error MAY be returned if it is not; however, the server SHOULD respond successfully when possible, even if it is not present. The Authorization Server need not be listed as an audience of the ID Token when it is used as an id_token_hint value.

(emphasis added)
Right now, the oauthlib library seems to be making that decision for the caller. The OIDC validator raises an InvalidRequestError if prompt=none is sent without an accompanying id_token_hint parameter.
Is this what we want to be doing here? The spec leaves open the possibility for the server to identify the user by some other method (e.g. login cookie) even if id_token_hint is missing. In practice, I think that would be hard to do with oauthlib as currently written. Is the intention that the calling application could catch the InvalidRequest exception and handle it (as with the LoginRequired and ConsentRequired errors)? If so, how? The calling app would have to set some kind of value for id_token_hint to avoid hitting that check again.

@skion I know it's been a while, but do you remember when you added this validation if you had something specific in mind for how a calling application could recover and proceed without an id_token_hint?

Hi @bjmc, I didn't implement that logic, but did run into it while fixing something around prompt=none, which is probably the commit you saw. Just didn't have a need (nor time) to look into it in more detail.
So I agree its a bug, would you have any ideas on how to fix it?


[CSL-73] Fix transactions processing (add sortings)

@gromak
Transactions processing is broken if some transaction references another transaction from the same block.

We don't do any topographical sort, i. e. transactions appear in blocks in arbitrary order and are verified in arbitrary order.
txVerifyBlocks uses the single version of utxo and doesn't modify it during processing.

Alternatively we can prohibit such transactions.

@gromak
We had a discussion with @mrodin regarding this issue, mostly bitcoin approach.

In bitcoin such transactions are legal, personally I don't see any reason to prohibit them, so let's not prohibit them.
Bitcoin reference implementation doesn't do topographical sort, but instead it works in the following way:

In terms of utxo it looks like creating a temporary utxo where all transaction outputs from the block being validated are marked as unspent, then with each transaction input either the present or temporary utxo gets modified. Then if block gets accepted, temporary utxo is added to the present one becoming the new present utxo. Otherwise, present utxo is rolled back.
More details are here: https://en.bitcoin.it/wiki/Protocol_rules#.22block.22_messages

Transactions in block can be inn arbitrary order. It is up to verifier to process them in correct order.

So let's improve our txVerifyBlocks so that it works fine with transactions referencing other transactions in the same block. I don't know who will do it, but it's up to him to decide how to do it (topographical sort or bitcoin approach or something else).

@georgeee
Bitcoin approach sounds like some working hacks, not transparent.
Let's do topsort, it's straightforward, easy to understand and describe.


It seems like I have installed the ARM64 version of VSC2019 and I need to download the x64 version. Any idea on how to fix this?

Please check for duplicates, similar issues or closed issues with the same problem, as well performing simple troubleshooting steps (such as deleting the export folder if it's an issue with compiling, reinstalling Kade Engine) before submitting an issue.
If you are playing a downloaded version of the game, what operating system are you using?
Windows (x86), Windows (x86_64), Linux, or macOS? Specify below.
What version of the game are you using? Look in the bottom left corner of the main menu.
Have you identified any steps to reproduce the bug? If so, please describe them below. Use images if possible.
Please describe your issue. Provide extensive detail and images if possible.

lmao lime cant build arm unless its for android or ios lmaoooooooooo


Add IsWindows to test utils

Simplifies having to import and run runtime.GOOS in every test suite targeting windows and linux.

/assign quintonamore


Coaching Ritter

Date of Coaching: TBD
Topics:

How to structure the documentation and specification to be userfriendly
How to communicate to the user(developer)?
How to make a simple visual interface

Terminanfrage für 10. Januar versendet


Gofmt/swagger compatibility for go version > 1.18

Changes to gofmt in go 1.19 break swagger documentation generation (see https://github.com/go-swagger/go-swagger/issues/2759), the solution is to indent the swagger documentation so that gofmt treats it as a preformatted block.
Additionally I have edited some remaining comments to ensure they are not modified when we run gofmt.

@markylaing will anything detect if new/changed documentation breaks these rules in the future?

@markylaing will anything detect if new/changed documentation breaks these rules in the future?

Nothing specific for this but I think the swagger docs will fail to build if the yaml spec for an endpoint is not valid. Also, gofmt is enabled for golangci-lint so if any comments are not correctly formatted it should be caught.

Thanks


Clear canvas before write chart

I use code like this
$.ajax({
        type: "GET",
        url: url,
        dataType: "json",
        error: function () {
            showFlash("error", "Wystąpił nieoczekiwany błąd podczas pobierania wykresu");
        },
        statusCode: {
            200: function (data) {
                $(".stat-pie-chart-panel").show();
                // Get the context of the canvas element we want to select
                var ctx = document.getElementById("hoursPerDateUserCanvas").getContext("2d");
                var hoursPerUserToday = new Chart(ctx).Pie(data, {
                    responsive: true,
                    //maintainAspectRatio: !2,
                    tooltipTemplate: function (valuesObject) {
                        // do different things here based on whatever you want;
                        var hours = Math.floor(valuesObject.value / 60);
                        var minutes = valuesObject.value % 60;
                        return valuesObject.label + " (" + ((hours < 10 && hours >= 0) ? '0' : '') + hours +
                            ":" + ((minutes < 10 && minutes >= 0) ? '0' : '') + minutes + ")";
                    }
                });

            }
        }
    });

Ajax request -> draw chart.
It's works fine but if I call AJAX once again chart was written in front of old, and i have some buggy view.
Maybe before libary draw chart, it should clear canvas?

There's clear() method mentioned in docs but its usage is rather weird since it belongs to specific chart type (Line in my case) instead of Chart object so you have to keep the reference to call it before render.

@meron1122 it sounds like you are recreating the chart for each AJAX request. Have you called destroy on the old chart? If not, you must do this before re-using the canvas for another chart.

see #1551

Closing as implementation issue. destroy() needs to be called on the old chart before the canvas is reused.

correction .. see also #1511 and #1558
var chart = new Chart(ctx).Bar(oldData, {})

$.ajax({..}).done(function (newData) {
  // destory old
  chart.destroy()

  // create new
  chart = new Chart(ctx).Bar(newData, {})
})

You can use update for v2
var chart_ctx = document.getElementById("chart").getContext("2d");

var chart = new Chart(chart_ctx, {
	type: "pie",
	data: {}
	options: {}
}

$.ajax({
	...
}).done(function (response) {
    chart.data = response;
    chart.update();
});


[Feature request] Allow open integrated terminal aside

Another feature request. In case of working with huge terminal output, I suppose it will be very conveniently to be able to open terminal aside (like editor splitting)

Duplicate https://github.com/Microsoft/vscode/issues/2806


Null control added for new credential dialog

When create new credential dialog cancelled, it give failed assertion.Boolean expression must not be null.Bug fixed.

There is a conflict, here @uzunemre

For the reason of conflict, l’m gonna add these lines by hand. Thank you so much.


Tip 13 adding files

issue #6
Added charp.md, java.md & python.md files and templates. Code examples and expected behavior still need to be added and validated for each.

@janackeh did we want to close this PR?


Custom training that uses BigQuery Python library should use an explicit PROJECT_ID

Expected Behavior
Some notebooks that demonstrate custom training use an inferred project:
from google.cloud import bigquery

client = bigquery.Client()

This will cause permission issues. See:
See https://cloud.google.com/vertex-ai/docs/workbench/managed/executor#explicit-project-selection.
Solution
Use an explicit project id:
import os

from google.cloud import bigquery

project_number = os.environ["CLOUD_ML_PROJECT_ID"]

client = bigquery.Client(project=project_number)

This seems obsolete. There are no notebooks referenced here.


Servers coming back 'down' when they're all up

Testing all my servers via their internal and external URL's and IP addresses - all of which are UP - but the script is telling me they all 'went down'.
Not sure what other information I can provide here...

Do you have ICMP blocked on the server firewall?


add to babel-loader webpack config for es5 compilation

I had to do this in my webpack config to get this working on IE:
{
        test: /\.js$/,
        exclude: /node_modules\/(?:(?!url-parse-lax)(?!prepend-http))/,
        use: ['babel-loader']
}

Just leaving it here in case someone else runs into the same issue.

This module mainly targets Node.js, not the browser. It's up to you to transpile it with Babel if you want to use it in the browser. You can find a more detailed explanation here: https://github.com/sindresorhus/ama/issues/446
If you use Webpack, check out babel-engine-plugin, which transpiles only the dependencies that needs to be transpiled.
If you use Create React App, upgrade to Create React App v2. It supports automatic transpilation of dependencies, which will make this package just work.


appRoot cannot be an absolute path

Line 128 in router.js, it's doing a "join", which blindly concatenates the two paths.

In setting up for SolidStarts next Beta Phase built on Nitro and Vinxi we are closing all PRs/Issues that will not be merged due to the system changing. If you feel your issue was closed by mistake. Feel free to re-open it after updating/testing against 0.4.x release. Thank you for your patience.

See https://github.com/solidjs/solid-start/pull/1139 for more details.


Remove vestigal nullOk parameter from Localizations.localeOf

Description
This removes the nullOk parameter on the Localizations.localeOf method. This was already changed to have a maybeLocaleOf method, but the nullOk parameter wasn't removed because some third party tests failed. Those have been updated, so this can go in now.
Related Issues

Fixes https://github.com/flutter/flutter/issues/68637

Tests

Updated the widgets_test

Breaking Change

[X] Yes, this is a breaking change that will require a migration guide.

[X] I wrote a design doc
[X] I submitted it for input from the developer relations team, specifically from: @RedBrogdon
[X] I wrote a migration guide: In https://github.com/flutter/website/pull/4921

Looks like flutter_svg's hash needs to be updated in the tests repository to pick up the removal of nullOK in that package: https://github.com/flutter/tests/blob/master/registry/flutter_svg.test#L3

Looks like flutter_svg's hash needs to be updated in the tests repository to pick up the removal of nullOK in that package: https://github.com/flutter/tests/blob/master/registry/flutter_svg.test#L3


feat: add toml config

this pr enables the user to be able to configure aoede not only with env vars but also with a config.toml

could u maybe label the repo with hacktoberfest or this pr with hacktoberfest-accepted so that it counts towards my contribs?

I added the label to the repo so it hopefully should count.

Looks good, just that last question on macro usage.


Kachasu Release

Codecov Report

Merging #318 into master will decrease coverage by 0.28%.
The diff coverage is 91.32%.

@@            Coverage Diff             @@
##           master     #318      +/-   ##
==========================================
- Coverage   92.94%   92.66%   -0.29%
==========================================
  Files          63       68       +5
  Lines        2466     2535      +69
  Branches      218      229      +11
==========================================
+ Hits         2292     2349      +57
- Misses        146      153       +7
- Partials       28       33       +5

Impacted Files
Coverage Δ

datahub/metadata/views.py
100% <ø> (ø)
:arrow_up:

datahub/investment/urls.py
100% <ø> (ø)
:arrow_up:

datahub/company/management/commands/sync_ch.py
86.25% <ø> (ø)
:arrow_up:

datahub/core/viewsets.py
88.88% <ø> (ø)
:arrow_up:

datahub/v2/repos/utils.py
97.64% <ø> (ø)
:arrow_up:

datahub/korben/spec.py
83.33% <ø> (ø)
:arrow_up:

datahub/korben/utils.py
79.01% <ø> (ø)
:arrow_up:

datahub/company/views.py
100% <100%> (ø)
:arrow_up:

datahub/omis/order/views.py
100% <100%> (ø)

datahub/investment/views.py
92.94% <100%> (-1.18%)
:arrow_down:

... and 21 more

Continue to review full report at Codecov.

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


Include Imagery that exemplifies our experience offered

User will want to see a page that not only is for a steakhouse, but a steakhouse that will give them a feeling of luxury, an experience. Which ties to our name LuxCore. Luxury at our core. Selling the meaning. ex Coffee on a coffee shop doesn't excite anyone as they can get coffee anywhere. We need to create visuals that portray something beyond steak. Our restaurants craftsmanship and delicacy.

I believe we have this, we have excellent images showcasing luxury and a peaceful quality experience

Done!


Update MongoDB vCore compatibility tables

The tables on that page seem to be incomplete. It would be great if they could be brought up to date with the latest MongoDB features.
For example, https://www.mongodb.com/docs/manual/reference/method/db.createView/#mongodb-method-db.createView is missing.

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

ID: 43a8d9b2-59d2-0a37-b645-fdd1133b9e72
Version Independent ID: 30014099-4923-e3f6-03c2-7bfa69d4c14f
Content: Compatibility and feature support - Azure Cosmos DB for MongoDB vCore
Content Source: articles/cosmos-db/mongodb/vcore/compatibility.md
Service: cosmos-db
Sub-service: mongodb-vcore
GitHub Login: @suvishodcitus
Microsoft Alias: suvishod

@letmaik Thanks for your feedback! We will investigate and update as appropriate.

@letmaik
Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can take a look at it accordingly.

Thank you for your feedback, @letmaik
We considered your feedback along with other actions we are taking to improve documentation. At this time, we have elected to prioritize other documentation improvements and cannot act on this feedback. For now, we are closing this issue.
#please-close


Update frontend and backend to ensure signup, login and logout functionalities

https://github.com/user-attachments/assets/cbb7d2ab-e699-43ef-a600-cbc7c2c6ca21
fixes #50

Fixes #50


No public supply data for states in 1950?

Not coming through in json.
I think we need a data audit for years and categories.

Thermoelectric too

Also odd that DC goes from such a big number for public supply in 1985 to almost none in 1990?

example of data audit needs:

bar on the bottom is smaller than 1980, but the area on the map doesn't make sense with that (it shrinks)

redundant w/ #75


Allow overriding OS_TYPE and ARCH. This will allow signing locally on e.g. mac

Summary
To execute make sign you need to be able to issue the signing command. There is a script for this, but it presumes that the architecture you're signing for is the same as what you're running.
This is problematic if you are on mac, as OS_TYPE will register as darwin. To override this, we allow you to override OS_TYPE, e.g. set it to linux. We will also allow overriding ARCH, since this may be set to arm64 on newer macs.
Test Plan
Verify signing works with these new changes, e.g.:
ARCH=amd64 OS_TYPE=linux make sign

Codecov Report

Merging #595 (8f9c5d8) into develop (c454446) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head 8f9c5d8 differs from pull request most recent head f32ecc7. Consider uploading reports for the commit f32ecc7 to get more accurate results

@@           Coverage Diff            @@
##           develop     #595   +/-   ##
========================================
  Coverage    47.55%   47.55%
========================================
  Files           25       25
  Lines         3863     3863
========================================
  Hits          1837     1837
  Misses        1745     1745
  Partials       281      281

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 c454446...f32ecc7. Read the comment docs.

Since this is for signing, would this change only affect our team? Also, would we get a help message or some doc so we know we can pass in these new variables as described in the test plan ARCH=amd64 OS_TYPE=linux make sign ?

Since this is for signing, would this change only affect our team? Also, would we get a help message or some doc so we know we can pass in these new variables as described in the test plan ARCH=amd64 OS_TYPE=linux make sign ?

Correct, this is internal only. I am updating the release doc right now.


update marimo deps (0.9.9)

Checklist

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

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found some lint.
Here's what I've got...
For recipe/meta.yaml:

requirements: run: pyyaml >= 6.0 should not contain a space between relational operator and the version, i.e. pyyaml >=6.0
requirements: run: narwhals >= 1.9.0 should not contain a space between relational operator and the version, i.e. narwhals >=1.9.0

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe/meta.yaml) and found it was in an excellent condition.

Closes #131 #132 #133 #134


[data2vec] The pre-trained vision model and code

Hi!
When will the pre-trained vision model and code of data2vec be released ?

@alexeib Hi, I'm wondering whether the code of data2vec (vision part) will be released recently.

yes i am working on it. the problem is that we implemented it in a different codebase (beit) and now need to port it over to fairseq

Great! I'm also looking for the vision part of the model :D

Me too :)

Has anyone been able to implement it based on @alexeib 's suggestion ?

@alexeib is there an ETA on the update or should we try to modify the beit code?
Echoing @mritunjaymusale 's request, has anyone implemented the suggestion? We'd rather not reproduce work.

I'm currently working on it, you can review my implementation here
According to the paper, I think Data2Vec for vision is more than just changing the loss calculation method of Beit, because Beit uses two images; one is the masked image of 224x224 pixels as inputs and the second is the visual tokens of the smaller image (112x112 encoded by a discrete Variational Auto Encoder like DALL-E) as targets. The task is for the model to predict these tokens based on the masked pixel inputs.
Based on what I understand from the paper, Data2Vec uses only one image tokenized by the dVAE model. My hypothesis is that the method would be as follows:

Transform the input image (according to the paper, random resized crop, horizontal flipping, color jittering)
Split the image into 14x14 patches of size 16x16 pixels each and tokenize the image using DALL-E to convert to visual tokens. (flatten 14x14 patches to a tensor of 196 items)
Apply masking to the tokens

And the rest is like NLP because we're now dealing with discrete tokens.
@alexeib I'd be glad to know if the above hypothesis is correct or not. In addition what would be the mask token id here? because I suppose all 8192 tokens are reserved by the image tokenizer (DALL-E)! Can I manually set a random number in that boundary?
Best,
Aryan

I just found this nice implementation from @Guillem96 who has exclusively worked on the vision part.

Alright, some of my assumptions above are wrong! The targets are contextualized and there's no need for a tokenizer. The images are patched, masked and fed to the network.
I just completed the vision implementation in my repo. There might be some minor details left to do which I will apply later on but the main body of work is done.

Official code and models released here: https://github.com/facebookresearch/data2vec_vision/tree/main/beit
I've reviewed the code briefly and can verify that most of the codes in my repo and @Guillem96 's conform to their implementation, but I'll go through it deeply to resolve any missing parts.


Installing qgis using conda on macOS Sierra

I am unable to install the qgis 2.18 using the condo-forge and still getting error

PackageNotFoundError: Package missing in current osx-64 channels:

qgis

kindly suggest

Hello,
I am also having this issue. I noticed on the main page that you have listed a "Disabled" Flag for the OSX build. Any info about when this will be back up?
Thanks

We never got a working recipe going for QGIS2 for Mac/Windows, but we finally have builds for Mac/Windows for QGIS 3.4 :tada:! There's a few caveats right now that I summarized in the PR for the recipe (full gory details in the PR...)
https://github.com/conda-forge/qgis-feedstock/pull/45#issuecomment-477300713


Add support for DotNet to the provider

The failure is due to missing test code - this is unrelated


kde: conflict with plasma-manager

The plasma-manager home-manager "extension" overwrites some of the files that are used by stylix (specifically "kcminputrc", "kded5rc", and "kdeglobals").
At first I thought of opening up the issue there, but I think it'd be worthwhile to look into using this to do our KDE management instead, since it might be easier later on to add options to stylix (and also compatibility because I could see other people using both at the same time).
This may also be related to pull request #142, since its inclusion would remove the need for "kdeglobals"

I'm actually working on this now, but I was wondering if there were to be any interest in this if I were to open up a pull request, or would it be not needed?
I think one of the main problems is that plasma-manager makes an option called "plasma.enable" that we could possibly use for stylix's mkEnableTarget.

As it turns out, after doing some more poking around, this is a bug with my configuration not with stylix. I'm closing it, but I will probably open another one with the possibility of using plasma-manager still, since I think it's still useful to avoid some of the messiness of the module. For now I'll start my improvements there, and then probably come here again with some suggestions on that.

If we replaced the module with plasma-manager, then everyone would be required to have that installed to get theming. We could try something similar to the situation with NeoVim, where there are separate targets for the built in Home Manager module and NixVim.


use the terminfo database instead of the json database

I'm working on a small library for reading terminfo files in pure go.
It is used like this:
package main

import (
    "log"

    "github.com/nhooyr/terminfo"
    "github.com/nhooyr/terminfo/caps"
)

func main() {
    log.SetFlags(0)
    ti, err := terminfo.Open()
    if err != nil {
        log.Fatal(err)
    }
    log.Println(ti.Names[0])
    log.Println(ti.BoolCaps[caps.BackColorErase])
    log.Println(ti.NumericCaps[caps.MaxColors])
    log.Println(ti.StringCaps[caps.SetAForeground])
}

Its a WIP so any ideas or changes are welcome.
What do you think of using this instead of the json database?

The binary format for terminfo isn't documented or standard so I'm loathe to depend on it.
Additionally I've found that terminfo is deficient in various ways. For example it lacks mouse reporting details.
So while I appreciate the effort if I'm honest I'm unlikely to switch to your code away from the database format I've created.

Alright, thanks anyways.

Bump. A lot of my users hit this. The terminfo database is the standard, it's folly to use a baked-in homebrew format instead.

There is a well maintained fork of my package that is used by a few very popular Go packages.
https://github.com/xo/terminfo
Going to reopen this issue.

I'm working on a solution that uses infocmp dynamically as a fallback.  I'm loathe to hardcode the undocumented GNU file format.

And for the record, the terminfo database isn't standard at all.  If you think it is, then that's because you have insufficient experience with other platforms that have different binary file formats.

Well, it's the closest thing to a standard we've got, and it works on a number of platforms. The alternative is the dozens of bug reports I've had to endure for users who aren't in the hardcoded special-snowflake database.

There is in fact a different alternative. Which I have taken as of yesterday. Sent from my Verizon, Samsung Galaxy smartphone
-------- Original message --------From: Drew DeVault<EMAIL_ADDRESS>Date: 6/13/19  6:09 AM  (GMT-08:00) To: gdamore/tcell<EMAIL_ADDRESS>Cc: gdamore<EMAIL_ADDRESS>State change<EMAIL_ADDRESS>Subject: Re: [gdamore/tcell] use the terminfo database instead of the json database (#93) Well, it's the closest thing to a standard we've got, and it works on a number of platforms. The alternative is the dozens of bug reports I've had to endure for users who aren't in the hardcoded special-snowflake database.
—You are receiving this because you modified the open/close state.Reply to this email directly, view it on GitHub, or mute the thread.
[
{
"@context": "http://schema.org",
"@type": "EmailMessage",
"potentialAction": {
"@type": "ViewAction",
"target": "https://github.com/gdamore/tcell/issues/93?email_source=notifications\u0026email_token=AAJ4G7NCGBP5RJQ65Y34ZG3P2JBIBA5CNFSM4CBU26B2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXTUHQY#issuecomment-501695427",
"url": "https://github.com/gdamore/tcell/issues/93?email_source=notifications\u0026email_token=AAJ4G7NCGBP5RJQ65Y34ZG3P2JBIBA5CNFSM4CBU26B2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODXTUHQY#issuecomment-501695427",
"name": "View Issue"
},
"description": "View this Issue on GitHub",
"publisher": {
"@type": "Organization",
"name": "GitHub",
"url": "https://github.com"
}
}
]


add recipe for kiritan & ofuton_p_utagoe db (singing voice synthesis)

Hi, This recipe intends for training vocoder for singing voice synthesis on kiritan & ofuton_p_utagoe dataset. The vocoder can be directly used in Muskits, open-source singing voice synthesis toolkits https://github.com/SJTMusicTeam/Muskits. Pre-trained models will be uploaded to google drive soon.
Please check to see if there is anything that needs to be modified. @ftshijt @kan-bayashi

@PeterGuoRuc Thank you for your contribution! I will review today!

Hi @kan-bayashi , we name the recipe based on the convention of its source. While the db is regarded as the official name for both the oniku and ofuton (they are also from the same source with many overlapped songs), Kiritan seems to be a bit independent.
In addition, we would be appreciated if following the convention in our Muskit toolkit as well (i.e., https://github.com/SJTMusicTeam/Muskits

OK, I see! Then that is no problem.

Thank you for your contribution!


Images look very small

Hello,
It works good when i zoom in or out but at first images look very small.
Check screenshot please

How can i fix it ?

What is image size and view size?

Image size is iphone 6 screenshot, view size is full screen on storyboard

Please update new 1.2 version and tell me this bug happen again or not


Update format-output-azure-cli.md

@dcaro, I read each of these changes audibly to make sure the grammar sounded correct. Merging.


Messaging: Surveys site app migration

Messaging
Context
Surveys users are moving off of the site app, on to the JS SDK for launch. No action required, but it's nice to be given a heads-up!
Goal
No goal we can track here.
Format
1x email
Audience / Targeting
@neilkakkar will share (over Slack) a list of emails we need to hit with this message.
Resources, timeline, responsibilities
We'll send this week, ASAP.
Requested input
Feedback on (incoming) copy.

@neilkakkar Curious if best to target by Org, or individual user here?
If Org, I need Org_Ids. If individual, I need specific emails.

oh, I didn't know you can easily target by org_ids - orgs would indeed be better, will send those instead!

oh, I didn't know you can easily target by org_ids - orgs would indeed be better, will send those instead!

Yep, though I try to avoid it for very long lists due to this bug.
Org IDs mean I have to create a cohort first. Emails I can just import into Customer.io. As long as it's less than 200 teams, Org_ID is fine.

I have good news, the bug is no more 😋

Ah, just realised I missed something important: people not using the snippet can be on an old version of posthog-js where this doesn't work, so the upgrade path needs to be more manual for them - otherwise we'll break surveys - I shouldn't disable the site app for them 😬.
Hmm, now wondering if the automation is more trouble than it's worth here. (cc: @liyiy ). I think I'll add a banner in app to tell them the upgrade path as well, but should mention it in the email too:
So, new doc (sorry @joethreepwood ):
Surveys require posthog-js version 1.81.1 to work.
1a. If you're using the snippet, you can just toggle on surveys on the surveys page and everything will work fine.
1b. If you're using a package manager, you should update posthog-js to 1.81.1 and then enable surveys in app.

You can then disable the "surveys app" app which will shortly be deprecated.

I think as long as we are consistent everywhere and clear with saying "Surveys is being deprecated off of the site app. If you're using posthog-js through package manager, upgrade to version 1.81+ instead"
Since users already have to edit their posthog init with opt_in_site_apps in the original experience, it should be fine having them update. Definitely more annoying than an automatic transition but better to do it now than later when there's even more users!

Better?

I chose the Oct 9th deadline to coincide with other surveys announcements.

Does re-enable surveys link to app.posthog.com/surveys ? And Oct 9 is good - good call to be explicit with dates here 👍 .
One edit: Update posthog-js to at least version 1.81.1 & then re-enable surveys.

And yes, much better, thank you!

Does re-enable surveys link to app.posthog.com/surveys ?

It does

Amended


Issue with unauthorized after login (followup to #1165)

I just wanted to point out that many people in #1165  were having issues with putting https:// or the port number on their REGISTRY_HTTP_HOST and the ticket was closed because that is an incorrect thing to do..
However, the documentation clearly shows this in the example:
https://docs.docker.com/registry/configuration/
http:
  addr: localhost:5000
  prefix: /my/nested/registry/
  host: https://myregistryaddress.org:5000

Thanks,
Stephen

The registry changed to serving relative URLs as of 2.3.0 which means the host can take both forms.


Explain advanced filtering modes: simple history, first parent, full history, and full history with simplified merges

As a developer
I want to understand the functionality of each advanced filtering mode
So that I can efficiently use the history.
Possible solutions:

provide the (git) command options of each advanced filtering mode.
describe each filtering mode and give examples

The provided link https://git-scm.com/book/en/v2/Git-Basics-Viewing-the-Commit-History isn't very helpful, the mapping between the filtering modes and git commands is missing.

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

ID: c6de6ffd-afcc-17f9-8e89-6845c0a5bd6c
Version Independent ID: caea7004-b42b-9084-befc-6b33168570b4
Content: View commit history - Azure Repos
Content Source: docs/repos/git/commit-history.md
Product: devops
GitHub Login: @steved0x
Microsoft Alias: sancha

I wondered about this too. Here is my guess at the mapping:

Option
Command

Simple history (default)
git log

First parent
git log --first-parent

Full history
git log --full-history

Full history (simplify merges)
git log --full-history --simplify-merges


Cleanup libgit2 build

Fixing the libgit2 iOS build and removing unused defines.

Correct spelling of LIBSSH2_INCLUDE_DIRS (fixes #481)
Disable CURL on iOS
Remove obsolete OPENSSL_* defines (libgit2 now uses SecureTransport on Apple platforms)
Add tests for git_libgit2_features flags

So we don't need OpenSSL no more? Then we could as well get rid of the target and enable Travis again because OpenSSL uses 15 of the 20 minutes build time.

libssh2 still needs OpenSSL, it's just libgit2 that has dropped it as a dependency. So the iOS build still has to deal with that huge compile time. I hope libssh2 drops it too.

I will test and review this.

Tests are green, cloning is working :+1:

:green_heart:

@phatblat @joshaber What do you guys think of a new release? I could volunteer to do it if @joshaber no one else finds time.

Awesome work :+1: I'll cut a new release now.

The Mac tests currently failing:
expect(@(git_features & GIT_FEATURE_SSH)).to(beTruthy());

Stupid question: Did you remove External/libgit2.a so that it rebuilds it?

On 10 Jul 2015, at 15:52, Josh Abernathy<EMAIL_ADDRESS>wrote:
The Mac tests currently failing:
expect(@(git_features & GIT_FEATURE_SSH)).to(beTruthy());
—
Reply to this email directly or view it on GitHub https://github.com/libgit2/objective-git/pull/483#issuecomment-120415478.

Yep. That file's presence causes update_libgit2 script to skip building.

On 10 Jul 2015, at 15:52, Josh Abernathy<EMAIL_ADDRESS>wrote:
The Mac tests currently failing:
expect(@(git_features & GIT_FEATURE_SSH)).to(beTruthy());
—
Reply to this email directly or view it on GitHub https://github.com/libgit2/objective-git/pull/483#issuecomment-120415478.

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

Yup, removed and rebuilt but it's still failing.

I just cloned again and they are still green Xcode 6.4 on 10.10.4 :cry:

@joshaber is your brew --prefix set to /opt/boxen? I mistakenly hard-coded the path to libssh2.h

Nah, it's /usr/local. I'm looking into this. Not sure what's happening :frowning:

Try removing LIBSSH2_INCLUDE_DIRS from update_libgit2. That may not be necessary in the Mac build.

No joy unfortunately.

Also try blowing away External/libgit2/build as the CMakeCache.txt file caches the arguments passed to cmake.

Even if I give CMake the explicit path to libssh2, it can't seem to find it:
  -DCMAKE_INCLUDE_PATH:PATH=/usr/local/Cellar/libssh2/1.6.0/include/ \
  -DCMAKE_LIBRARY_PATH:PATH=/usr/local/Cellar/libssh2/1.6.0/lib/ \

-- LIBSSH2 not found. Set CMAKE_PREFIX_PATH if it is installed outside of the default search path.

:cry:

A fresh clone also fails.
Where do you all have libssh2 installed?

Via brew:
$ brew info libssh2
libssh2: stable 1.6.0 (bottled), HEAD
C library implementing the SSH2 protocol
http://www.libssh2.org/
/usr/local/Cellar/libssh2/1.6.0 (178 files, 1.3M) *
  Poured from bottle
From: https://github.com/Homebrew/homebrew/blob/master/Library/Formula/libssh2.rb
==> Dependencies
Recommended: openssl ✔
Optional: libressl ✘
==> Options
--with-libressl
	build with LibreSSL instead of OpenSSL
--without-openssl
	Build without openssl support
--HEAD
	Install HEAD version

./script/update_libgit2 output:
$ ./script/update_libgit2
-- The C compiler identification is AppleClang <IP_ADDRESS>20053
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc
-- Check for working C compiler: /Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Found PkgConfig: /usr/local/bin/pkg-config (found version "0.28")
-- Found Security /System/Library/Frameworks/Security.framework
-- Found CoreFoundation /System/Library/Frameworks/CoreFoundation.framework
-- checking for module 'libcurl'
--   found libcurl, version 7.30.0
-- Could NOT find HTTP_Parser (missing:  HTTP_PARSER_INCLUDE_DIR HTTP_PARSER_LIBRARY)
-- http-parser was not found or is too old; using bundled 3rd-party sources.
-- Found ZLIB: /usr/lib/libz.dylib (found version "1.2.5")
-- checking for module 'libssh2'
--   found libssh2, version 1.6.0
-- Looking for libssh2_userauth_publickey_frommemory in ssh2
-- Looking for libssh2_userauth_publickey_frommemory in ssh2 - found
-- Found Iconv: -L/usr/lib -liconv
-- Performing Test IS_WNO-MISSING-FIELD-INITIALIZERS_SUPPORTED
-- Performing Test IS_WNO-MISSING-FIELD-INITIALIZERS_SUPPORTED - Success
-- Performing Test IS_WSTRICT-ALIASING=2_SUPPORTED
-- Performing Test IS_WSTRICT-ALIASING=2_SUPPORTED - Success
-- Performing Test IS_WSTRICT-PROTOTYPES_SUPPORTED
-- Performing Test IS_WSTRICT-PROTOTYPES_SUPPORTED - Success
-- Performing Test IS_WDECLARATION-AFTER-STATEMENT_SUPPORTED
-- Performing Test IS_WDECLARATION-AFTER-STATEMENT_SUPPORTED - Success
-- Performing Test IS_WNO-UNUSED-CONST-VARIABLE_SUPPORTED
-- Performing Test IS_WNO-UNUSED-CONST-VARIABLE_SUPPORTED - Success
-- Performing Test IS_WNO-UNUSED-FUNCTION_SUPPORTED
-- Performing Test IS_WNO-UNUSED-FUNCTION_SUPPORTED - Success
-- Performing Test IS_WNO-DEPRECATED-DECLARATIONS_SUPPORTED
-- Performing Test IS_WNO-DEPRECATED-DECLARATIONS_SUPPORTED - Success
-- Looking for include file pthread.h
-- Looking for include file pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - found
-- Found Threads: TRUE
-- Looking for clock_gettime in rt
-- Looking for clock_gettime in rt - not found
-- Configuring done
-- Generating done
-- Build files have been written to: /Users/pietbrauer/Documents/Projects/objective-git/External/libgit2/build
Scanning dependencies of target git2
[  0%] Building C object CMakeFiles/git2.dir/src/annotated_commit.c.o
[  1%] Building C object CMakeFiles/git2.dir/src/attr.c.o
[  2%] Building C object CMakeFiles/git2.dir/src/attr_file.c.o
[  3%] Building C object CMakeFiles/git2.dir/src/attrcache.c.o
[  3%] Building C object CMakeFiles/git2.dir/src/blame.c.o
[  4%] Building C object CMakeFiles/git2.dir/src/blame_git.c.o
[  5%] Building C object CMakeFiles/git2.dir/src/blob.c.o
[  6%] Building C object CMakeFiles/git2.dir/src/branch.c.o
[  6%] Building C object CMakeFiles/git2.dir/src/buf_text.c.o
[  7%] Building C object CMakeFiles/git2.dir/src/buffer.c.o
[  8%] Building C object CMakeFiles/git2.dir/src/cache.c.o
[  9%] Building C object CMakeFiles/git2.dir/src/checkout.c.o
[ 10%] Building C object CMakeFiles/git2.dir/src/cherrypick.c.o
[ 10%] Building C object CMakeFiles/git2.dir/src/clone.c.o
[ 11%] Building C object CMakeFiles/git2.dir/src/commit.c.o
[ 12%] Building C object CMakeFiles/git2.dir/src/commit_list.c.o
[ 13%] Building C object CMakeFiles/git2.dir/src/config.c.o
[ 13%] Building C object CMakeFiles/git2.dir/src/config_cache.c.o
[ 14%] Building C object CMakeFiles/git2.dir/src/config_file.c.o
[ 15%] Building C object CMakeFiles/git2.dir/src/crlf.c.o
[ 16%] Building C object CMakeFiles/git2.dir/src/curl_stream.c.o
[ 17%] Building C object CMakeFiles/git2.dir/src/date.c.o
[ 17%] Building C object CMakeFiles/git2.dir/src/delta-apply.c.o
[ 18%] Building C object CMakeFiles/git2.dir/src/delta.c.o
[ 19%] Building C object CMakeFiles/git2.dir/src/describe.c.o
[ 20%] Building C object CMakeFiles/git2.dir/src/diff.c.o
[ 20%] Building C object CMakeFiles/git2.dir/src/diff_driver.c.o
[ 21%] Building C object CMakeFiles/git2.dir/src/diff_file.c.o
[ 22%] Building C object CMakeFiles/git2.dir/src/diff_patch.c.o
[ 23%] Building C object CMakeFiles/git2.dir/src/diff_print.c.o
[ 24%] Building C object CMakeFiles/git2.dir/src/diff_stats.c.o
[ 24%] Building C object CMakeFiles/git2.dir/src/diff_tform.c.o
[ 25%] Building C object CMakeFiles/git2.dir/src/diff_xdiff.c.o
[ 26%] Building C object CMakeFiles/git2.dir/src/errors.c.o
[ 27%] Building C object CMakeFiles/git2.dir/src/fetch.c.o
[ 27%] Building C object CMakeFiles/git2.dir/src/fetchhead.c.o
[ 28%] Building C object CMakeFiles/git2.dir/src/filebuf.c.o
[ 29%] Building C object CMakeFiles/git2.dir/src/fileops.c.o
[ 30%] Building C object CMakeFiles/git2.dir/src/filter.c.o
[ 31%] Building C object CMakeFiles/git2.dir/src/fnmatch.c.o
[ 31%] Building C object CMakeFiles/git2.dir/src/global.c.o
[ 32%] Building C object CMakeFiles/git2.dir/src/graph.c.o
[ 33%] Building C object CMakeFiles/git2.dir/src/hash.c.o
[ 34%] Building C object CMakeFiles/git2.dir/src/hashsig.c.o
[ 34%] Building C object CMakeFiles/git2.dir/src/ident.c.o
[ 35%] Building C object CMakeFiles/git2.dir/src/ignore.c.o
[ 36%] Building C object CMakeFiles/git2.dir/src/index.c.o
[ 37%] Building C object CMakeFiles/git2.dir/src/indexer.c.o
[ 37%] Building C object CMakeFiles/git2.dir/src/iterator.c.o
[ 38%] Building C object CMakeFiles/git2.dir/src/merge.c.o
[ 39%] Building C object CMakeFiles/git2.dir/src/merge_file.c.o
[ 40%] Building C object CMakeFiles/git2.dir/src/message.c.o
[ 41%] Building C object CMakeFiles/git2.dir/src/mwindow.c.o
[ 41%] Building C object CMakeFiles/git2.dir/src/netops.c.o
[ 42%] Building C object CMakeFiles/git2.dir/src/notes.c.o
[ 43%] Building C object CMakeFiles/git2.dir/src/object.c.o
[ 44%] Building C object CMakeFiles/git2.dir/src/object_api.c.o
[ 44%] Building C object CMakeFiles/git2.dir/src/odb.c.o
[ 45%] Building C object CMakeFiles/git2.dir/src/odb_loose.c.o
[ 46%] Building C object CMakeFiles/git2.dir/src/odb_mempack.c.o
[ 47%] Building C object CMakeFiles/git2.dir/src/odb_pack.c.o
[ 48%] Building C object CMakeFiles/git2.dir/src/oid.c.o
[ 48%] Building C object CMakeFiles/git2.dir/src/oidarray.c.o
[ 49%] Building C object CMakeFiles/git2.dir/src/openssl_stream.c.o
[ 50%] Building C object CMakeFiles/git2.dir/src/pack-objects.c.o
[ 51%] Building C object CMakeFiles/git2.dir/src/pack.c.o
[ 51%] Building C object CMakeFiles/git2.dir/src/path.c.o
[ 52%] Building C object CMakeFiles/git2.dir/src/pathspec.c.o
[ 53%] Building C object CMakeFiles/git2.dir/src/pool.c.o
[ 54%] Building C object CMakeFiles/git2.dir/src/posix.c.o
[ 55%] Building C object CMakeFiles/git2.dir/src/pqueue.c.o
[ 55%] Building C object CMakeFiles/git2.dir/src/push.c.o
[ 56%] Building C object CMakeFiles/git2.dir/src/rebase.c.o
[ 57%] Building C object CMakeFiles/git2.dir/src/refdb.c.o
[ 58%] Building C object CMakeFiles/git2.dir/src/refdb_fs.c.o
[ 58%] Building C object CMakeFiles/git2.dir/src/reflog.c.o
[ 59%] Building C object CMakeFiles/git2.dir/src/refs.c.o
[ 60%] Building C object CMakeFiles/git2.dir/src/refspec.c.o
[ 61%] Building C object CMakeFiles/git2.dir/src/remote.c.o
[ 62%] Building C object CMakeFiles/git2.dir/src/repository.c.o
[ 62%] Building C object CMakeFiles/git2.dir/src/reset.c.o
[ 63%] Building C object CMakeFiles/git2.dir/src/revert.c.o
[ 64%] Building C object CMakeFiles/git2.dir/src/revparse.c.o
[ 65%] Building C object CMakeFiles/git2.dir/src/revwalk.c.o
[ 65%] Building C object CMakeFiles/git2.dir/src/settings.c.o
[ 66%] Building C object CMakeFiles/git2.dir/src/sha1_lookup.c.o
[ 67%] Building C object CMakeFiles/git2.dir/src/signature.c.o
[ 68%] Building C object CMakeFiles/git2.dir/src/socket_stream.c.o
[ 68%] Building C object CMakeFiles/git2.dir/src/sortedcache.c.o
[ 69%] Building C object CMakeFiles/git2.dir/src/stash.c.o
[ 70%] Building C object CMakeFiles/git2.dir/src/status.c.o
[ 71%] Building C object CMakeFiles/git2.dir/src/stransport_stream.c.o
[ 72%] Building C object CMakeFiles/git2.dir/src/strmap.c.o
[ 72%] Building C object CMakeFiles/git2.dir/src/submodule.c.o
[ 73%] Building C object CMakeFiles/git2.dir/src/sysdir.c.o
[ 74%] Building C object CMakeFiles/git2.dir/src/tag.c.o
[ 75%] Building C object CMakeFiles/git2.dir/src/thread-utils.c.o
[ 75%] Building C object CMakeFiles/git2.dir/src/tls_stream.c.o
[ 76%] Building C object CMakeFiles/git2.dir/src/trace.c.o
[ 77%] Building C object CMakeFiles/git2.dir/src/transaction.c.o
[ 78%] Building C object CMakeFiles/git2.dir/src/transport.c.o
[ 79%] Building C object CMakeFiles/git2.dir/src/tree-cache.c.o
[ 79%] Building C object CMakeFiles/git2.dir/src/tree.c.o
[ 80%] Building C object CMakeFiles/git2.dir/src/tsort.c.o
[ 81%] Building C object CMakeFiles/git2.dir/src/util.c.o
[ 82%] Building C object CMakeFiles/git2.dir/src/vector.c.o
[ 82%] Building C object CMakeFiles/git2.dir/src/zstream.c.o
[ 83%] Building C object CMakeFiles/git2.dir/src/transports/auth.c.o
[ 84%] Building C object CMakeFiles/git2.dir/src/transports/auth_negotiate.c.o
[ 85%] Building C object CMakeFiles/git2.dir/src/transports/cred.c.o
[ 86%] Building C object CMakeFiles/git2.dir/src/transports/cred_helpers.c.o
[ 86%] Building C object CMakeFiles/git2.dir/src/transports/git.c.o
[ 87%] Building C object CMakeFiles/git2.dir/src/transports/http.c.o
[ 88%] Building C object CMakeFiles/git2.dir/src/transports/local.c.o
[ 89%] Building C object CMakeFiles/git2.dir/src/transports/smart.c.o
[ 89%] Building C object CMakeFiles/git2.dir/src/transports/smart_pkt.c.o
[ 90%] Building C object CMakeFiles/git2.dir/src/transports/smart_protocol.c.o
[ 91%] Building C object CMakeFiles/git2.dir/src/transports/ssh.c.o
[ 92%] Building C object CMakeFiles/git2.dir/src/transports/winhttp.c.o
[ 93%] Building C object CMakeFiles/git2.dir/src/xdiff/xdiffi.c.o
[ 93%] Building C object CMakeFiles/git2.dir/src/xdiff/xemit.c.o
[ 94%] Building C object CMakeFiles/git2.dir/src/xdiff/xhistogram.c.o
[ 95%] Building C object CMakeFiles/git2.dir/src/xdiff/xmerge.c.o
[ 96%] Building C object CMakeFiles/git2.dir/src/xdiff/xpatience.c.o
[ 96%] Building C object CMakeFiles/git2.dir/src/xdiff/xprepare.c.o
[ 97%] Building C object CMakeFiles/git2.dir/src/xdiff/xutils.c.o
[ 98%] Building C object CMakeFiles/git2.dir/src/unix/map.c.o
[ 99%] Building C object CMakeFiles/git2.dir/src/unix/realpath.c.o
[100%] Building C object CMakeFiles/git2.dir/deps/http-parser/http_parser.c.o
Linking C static library libgit2.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libgit2.a(auth_negotiate.c.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libgit2.a(winhttp.c.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libgit2.a(auth_negotiate.c.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: libgit2.a(winhttp.c.o) has no symbols
[100%] Built target git2
libgit2.a -> ../../libgit2.a
libgit2 has been updated.

Trying on another Mac and I'm now able to reproduce the SSH feature test failure. Odd thing is that Xcode (6.4), OS X (10.10.4), libssh2 (1.6.0) and brew --prefix all match between the two Macs. Only discrepancy I've found so far is the cmake version: 3.2.3 on Mac without issue, 3.2.2 on Mac with failing test.

Aha! I didn't have pkg-config. With that installed it seems to work :metal:
I wonder if we should add that to REQUIRED_TOOLS in script/bootstrap.

Found the cause of the failures on my other Mac. I used to use Boxen on it and both libssh2 and cmake were still installed from the old homebrew location.
$ ll `which cmake`
lrwxr-xr-x  1 ben  staff    29B Feb 10 12:16 /usr/local/bin/cmake -> /opt/boxen/homebrew/bin/cmake

$ brew doctor

Warning: You have unlinked kegs in your Cellar
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run `brew link` on these:

    cmake
    libssh2

Re-linking these from /usr/local resolved my issues (I already had pkg-config installed) and now the Mac tests are all green.

:cool:
I'm in the process of making the necessary changes to our internal CI. Will TravisCI support this?

Looks like it. The TravisCI VMs have homebrew installed

Now that we've found the root cause we could build a new version \o/

Just tagged a new release: https://github.com/libgit2/objective-git/releases/tag/0.8.6
Thanks all!


env add tries to add to non-existent project

In a clean directory, with no projects named BadGoose, archer env add attempts to add an environment to a project named BadGoose.
~/ecs/ecs-devx/testing/archer$ ls -a
.	..

~/ecs/ecs-devx/testing/archer$ tree -a
.

0 directories, 0 files

~/ecs/ecs-devx/testing/archer$ archer project ls
12334

~/ecs/ecs-devx/testing/archer$ archer env add
? What is your environment's name? foo
Error: couldn't find a project named BadGoose in account xxxxxxxxxxxx and region us-west-2

I think the best thing to do for this is to do a best effort guess at if we're in a Git workspace, and pin the workspace root at the same level as the .git dir.

We renamed the directory to ecs-project/ which should reduce the occurrences of this problem. I think sufficient time has passed without being surprised by this issue. I'll resolve this and create a new one if a customer complains.


Add: logo files

png and svg in img folder

Looks good, although the outer circle isn't there in most Julia logos.
@kytrinyx could you take a look if this fits the usual exercism-logo requirements?

This works, either with or without the outer circle.

indeed, the outer circle was an artistic license I took
I'm happy to modify the logo and take it out

I'm fine with the circle. It looks good, thanks for creating the logo! :)
Just to be sure: There shouldn't be any license issues because it's so different to the original Julia logo, right?

There shouldn't be any license issues because it's so different to the original Julia logo, right?

I'm pretty sure loosely inspired by is fine. For future reference, though, what is the license on the Julia logo?

I can't find any info on the logo itself but the julialang.org contents (does that include the logo?) is licensed under the MIT license: https://github.com/JuliaLang/julialang.github.com/blob/master/LICENSE.md
In the past people have just asked Stefan Karpinski (creator of the logo) directly for permission to use it, so if we want to be 100% sure, I can send a mail and ask.

In the past people have just asked Stefan Karpinski (creator of the logo) directly for permission to use it, so if we want to be 100% sure, I can send a mail and ask.

I think it would be worth asking, making sure to mention that that this doesn't represent the language Julia, but the language track on Exercism.
I might be overly cautious.

He's given us the permission to use it.
@kytrinyx I forwarded you the email in case you want a record of it.

Sweet, thanks so much!

julia's wikipedia page links to this discussion about the logo and its license
it seems they are using the same policy of python

I've added the attribution/licensing info the README & will merge this on tuesday unless there are any objections.
Thanks a lot for creating a logo for our track, @alemelis

@SaschaMann my pleasure :)

@alemelis The SVG appears to have unused whitespace around it. The logo appears smaller than the other icons on the language list. Could you adjust that?

@SaschaMann you're right, sorry about that! The svg should now be fixed


A newsletter ?

do we need one ?

No, we should go public to twitter always for discussion
On Saturday, February 13, 2016, Clément Renaud<EMAIL_ADDRESS>wrote:

do we need one ?
—
Reply to this email directly or view it on GitHub
https://github.com/protocultural/protocultural.org/issues/24.


Re-enable Prosit tests

Was this just for avoiding the error on TeamCity or also on the nightly builds? If it was just the former (so code inspection would still run for example) then I think muting the test on TeamCity would have been more expedient/convenient. Those mutes can be set to expire either when the test starts passing or on a certain date.

Was this just for avoiding the error on TeamCity or also on the nightly builds? If it was just the former (so code inspection would still run for example) then I think muting the test on TeamCity would have been more expedient/convenient. Those mutes can be set to expire either when the test starts passing or on a certain date.

I didn't know about muting tests. Yes, I should have probably done that instead. Thanks!


Simplify TLS client auth code

Additional requirement: Allow both auth methods to be used at the same time; if both are present, then check both.


[all hosts] (TOC) Move preview tag from name to displayName

Docs Build status updates of commit 27d8a6d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/toc.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Invoke-SqlCmd fails with security error when attempting to connect to a database that does not encrypt connections

Fresh, default install of SQL server 2019 developer edition.
Updated to latest release version of SqlServer .
Executed
Invoke-SqlCmd -serverInstance localhost -query "SELECT 'Hello, world'"

fails with error
Invoke-SqlCmd : A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL
Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.)
At line:1 char:1
+ Invoke-SqlCmd -serverInstance localhost -query "SELECT 'Hello, world' ...
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [Invoke-Sqlcmd], SqlException
    + FullyQualifiedErrorId : SqlExceptionError,Microsoft.SqlServer.Management.PowerShell.GetScriptCommand

Powershell version 5.1.19041.2673
SqlServer module 22.0.59
I know you've launched new encryption features, but this has broken basic development workflow.  The error message is not informative because it made us assume the server was returning an untrusted self-signed certificate somehow.
We ran into this onboarding a new student developer.  He and one of our developers spent the whole day trying to figure out how his development server was configured wrong, assuming there was a problem in their SQL server, not realizing that we'd simply installed the latest version of the module onto this new machine.

Hi @Pxtl,
There's not much I can (or want :-)) to do about it. Security has a cost... and sometimes that means making things a little harder for users. I acknowledge that.
But the documentation should and the message should be informative enough: if you trust the server you are connecting to, just add a simple -TrustServerCertificate and you'll be fine.

@Matteo-T could we at least maybe get a clearer error-message for cases where the target SQL server is not using an encrypted connection?
"The certificate chain was issued by an authority that is not trusted." is not correct at all.  There is no certificate chain.  The server's connection is unencrypted.  The error message is misleading and costs time in debugging.

@Pxtl - the error message comes straight from the Microsoft.Data.SqlClient, so I'm not sure how easy/hard it would be to try and catch it and massage it to something else.
The message is actually accurate, in the sense that your server is simply giving back a self-signed certificate that your client (the Invoke-Sqlcmd cmdlet, in this case) is not trusting. If you put that certificate into the right location in your certificate store (if you know what you are doing), the message will go away.
You can log a new Issue and I'll see what I can do about it.

Ah, thanks for the correction. I didn't realize SQL server uses a self-signed cert if it's not configured with a shared cert.  Yes, I'll create a new issue.


How can i inject different dependencies  with autofac.

I have a bootstraper class that i run i soon as application start, usually i register services, repositories and other classes there and set an dependency resolver, and in controllers i use constructor inject to get the services and repositories. Can someone give me an example how can i do the same thing in bot framework.
In the message controller i need to resolve a service which creates some logs and saves them in Database.

I am closing this due to the fact that this repos issues are for platform DCRs only.
In addition, the post is:
a.  it doesn't identify the SDK
b. it is a request for help and those should be done via stack overflow.
To get help with an issue with your bot

"How To" questions should be submitted on Stack Overflow.

To file an issue against a component please go to the components repo

Create Azure Bot Framework Service or Channel issue
Create Bot Builder Tools issue
Create Bot Builder SDK V3 (.NET or Javascript) issue
Create Bot Builder SDK V4 .NET issue
Create Bot Builder SDK V4 Javascript issue
Create Bot Builder SDK V4 Java issue
Create Bot Builder SDK V4 Python issue


Added new link JavaScript Garden - Documentation about the most quirk…

…y parts of the JavaScript
JavaScript Garden - Documentation about the most quirky parts of the JavaScript
https://discussions.udacity.com/t/resource-javascript-garden-documentation-about-the-most-quirky-parts-of-the-javascript/441917

LGTM.Thanks so much for your first PR  🎉


Fix cmake library path for libpng16.a #18950

System information

OS: Linux Fedora 26
Tensorflow: installed from source (master branch)
GCC 7.3.1
CMake 3.11
No GPU

Problem
The CMake build fails on Fedora in normal build. libpng16 is using

CMAKE_INSTALL_LIBDIR

as the library destination for non-WIN32 systems. In some linux distribution like fedora this path corresponds to lib64
Steps to reproduce
$ git clone https://github.com/tensorflow/tensorflow
$ cd tensorflow/tensorflow/contrib/cmake
$ mkdir build && cd build
$ cmake  ..
$ make

Logs
[...]
make[3]: *** No rule to make target 'png/install/lib/libpng16.a', needed by 'proto_text'.
Stop.
make[2]: *** [CMakeFiles/Makefile2:8959: CMakeFiles/proto_text.dir/all] Error 2
make[1]: *** [CMakeFiles/Makefile2:5441: CMakeFiles/tf_core_framework.dir/rule] Error 2
make: *** [Makefile:1919: tf_core_framework] Error 2

I signed it!

I signed it!

Nagging Assignee @ebrevdo: It has been 15 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 30 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 45 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

LGTM. Nice catch!

Nagging Assignee @ebrevdo: It has been 16 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 31 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 46 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

Nagging Assignee @ebrevdo: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.


Support for Arm-based Docker images

Describe the feature
Actually, all the Docker images are built using the amd64 architecture.
https://github.com/clastix/capsule/blob/12237ae106d6e9bbcb49e1091318534a901f29cd/Dockerfile#L27
Capsule should be runnable also on Arm and Arm64-based infrastructures since there are plenty of projects running Kubernetes at the edge.
What would the new user story look like?

Definitely, we have to switch from quay.io based Docker image creation to GitHub Actions, requiring to provide a new GitHub Secret to allow push of built Docker images
Using docker buildx to allow the creation of multi-arch images
Evaluate if we need a hub.docker.com account

Expected behavior
Running clastix/capsule:v0.0.5 (YMMV) container image on an Arm-based Kubernetes cluster, Capsule should be up and running.

Done some tests on arm and arm64 platforms;
here we have some critical points:

the bitnami/kubectl image used inside "jobs" is not ready for arm use;
instead I'd take a look at kubesphere -> TESTED OK, I'll modify default helm chart values for this ;
RBAC Proxy image is not ready for arm use -> REMOVED with #246 PL ;
docker build is striclty dependant from GOARCH var (and other flags) and it's impossible to produce only one multiarch manifest directly using docker buildx -> actually trying goreleaser

the bitnami/kubectl image used inside "jobs" is not ready for arm use;
instead I'd take a look at kubesphere/kubectl -> TESTED OK, I'll modify default helm chart values for this ;

LGTM

docker build is strictly dependant from GOARCH var (and other flags) and it's impossible to produce only one multiarch manifest directly using docker buildx -> actually trying goreleaser

Let's move out the build process from Docker to goreleaser

According to latest PR, few updates.

we're going to provide a Clastix kubectl container image since we noticed some missing supported architectures
no need for goreleaser, in the end, we can easily use the base golang:1.16 container image with a target architecture with build provided by the GH Action docker/build-push-action@v2


aizynthfinder process is killed after loading config.yml

Hi,
I am trying to run Retrosynthesis on a small sample of Building Blocks. From the published paper "AiZynthFinder: a fast, robust and flexible open-source software for retrosynthetic planning".
I got 2 hdf5 for policy configuration and 1 hdf5 for zinc stock from the reference: https://figshare.com/articles/dataset/AiZynthFinder_a_fast_robust_and_flexible_open-source_software_for_retrosynthetic_planning/12334577/1
My config file is shown as follows:
config.yml starts here
properties:
exclude_target_from_stock: False
iteration_limit: 100
time_limit: 10
cutoff_cumulative: 0.995
cutoff_number: 50
max_transforms: 5
policy:
files:
uspto:
- ~/repos/full_uspto_03_05_19_rollout_policy.hdf5
- ~/repos/full_uspto_03_05_19_unique_templates.hdf5
stock:
files:
zinc: ~/repos/zinc_stock_17_04_20.hdf5
config.yml ends here
After loading the config.yml, the aizynthfinder process is unexpectedly killed without any error message. Here is the log:
log starts here
(aizynth-env) [user1@c0308a-s25 Lib-INVENT]$ aizynthcli --smiles ../sample_output/AC_SMILES_split_0.smi --config ../sample_run/config.yml --output ../sample_output/aizynthfinder_output_AC.hdf5
Setting exclude target from stock to False
Setting iteration limit to 10000000
Setting time limit to 100
Setting cutoff cumulative to 0.9
Setting cutoff number to 25
Setting max transforms to 4
Loading template-based expansion policy model from ~/repos/full_uspto_03_05_19_rollout_policy.hdf5 to uspto
Loading templates from ~/repos/full_uspto_03_05_19_unique_templates.hdf5 to uspto
Loading stock from ~/repos/zinc_stock_17_04_20.hdf5 to zinc
Killed
(aizynth-env) [user1@c0308a-s25 Lib-INVENT]$
log ends here
I have tried adjusting the time limit and all other variables in my config.yml, but it will always be killed within 20 seconds. I wonder what is the cause and how I can fix it.
Thank you!

Hi, I figured that if I use the stockfile.hdf5 file from "https://github.com/SeemonJ/combinatorial-library-design-dpp/tree/main/publication_example", aizynthfinder will work.

Hello. Thanks for your respons.
My initial thought is that you ran out of memory when trying to load the rather large ZINC stock.
Looking at your input file, it appears that you are running on old version of aizynthfinder with old model files. I would recommend upgrading to the latest version and downloading the models files anew with "download_public_data" script.

Closing due to inactivity


adds addFields function

adds addFields function to AggregationCursor.prototype for adding a addFields stage to the aggregation pipeline

@MassiveFermion it looks like there is a linting error here, once thats fixed we merge this immediately. Thanks for putting up with the minutia here :)

ping @MassiveFermion, there is a linting error with your patch

@mbroadst , fixed it


chore: Add httpjson server-side streaming showcase tests

Thank you for opening a Pull Request! For general contributing guidelines, please refer to contributing guide
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[x] Make sure to open an issue as a bug/issue before writing your code! That way we can discuss the change, evaluate designs, and agree on the general idea
[x] Ensure the tests and linter pass
[x] Code coverage does not decrease (if any source code was changed)
[x] Appropriate docs were updated (if necessary)

Part of #1439☕

Draft PR

Thanks for the review! I forgot to change it haha


Fix 0..9 keys in article view

In article view, numeric keys open a URL with a given number. I broke that behaviour in 485082f43f49f1c30974621107b1fa197618bf67 because I didn't fill articleview's links field, so the view thought that there are no links to open.
@j605, please confirm that this fixes the problem for you. Thanks for reporting it, too!

Coverage decreased (-0.2%) to 39.765% when pulling 8f744697d225ae518ee1ff06e14db1256ed5ba99 on bugfix/numeric-keys-in-articleview into eda3c3ec54a6c3c802631c4097bfd9f8715a20ef on master.

It fixes the issue, thanks :)


[DOCS] Update docs to not suggest to package Spark before running tests.

What changes were proposed in this pull request?
Update docs to not suggest to package Spark before running tests.
How was this patch tested?
Not creating a JIRA since this pretty small. We haven't had the need to run mvn package before mvn test since 1.6 at least, or so I am told. So, updating the docs to not be misguiding.

I believe that's right; @vanzin can probably confirm. I have usually built the assembly anyway when I test.

Test build #67295 has started for PR 15572 at commit 858e50d.

Test build #67295 has finished for PR 15572 at commit 858e50d.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67295/
Test PASSed.

Merged build finished. Test PASSed.

LGTM, merging to master.

Test build #67299 has started for PR 15572 at commit 52d3517.

Test build #67299 has finished for PR 15572 at commit 52d3517.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/67299/
Test PASSed.

Merged build finished. Test PASSed.