Report when seed kubeconfig has expired in gardener/example/provider-extensions/seed/configure-seed.sh

How to categorize this issue?

/area quality
/kind bug
What would you like to be added:
Right now when the following command fails
https://github.com/gardener/gardener/blob/8a80f8c644482cc4fe002846a19c27a74bbc80e4/example/provider-extensions/seed/configure-seed.sh#L135
It is expected that the cause is a non-Shooted cluster and the script tries to promote it to a seed. But the same command can fail if the seed kubeconfig has expired.
Why is this needed:
It is easy to forget that the seed kubeconfig has expired and the following messages from the seed promotion steps are confusing
https://github.com/gardener/gardener/blob/8a80f8c644482cc4fe002846a19c27a74bbc80e4/example/provider-extensions/seed/configure-seed.sh#L157-L160

Run that caused the error
$ kubectl get configmaps -n kube-system shoot-info --kubeconfig <seed-kubeconfig-path>
E0624 15:03:39.417727   91892 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0624 15:03:39.477950   91892 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0624 15:03:39.535583   91892 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0624 15:03:39.593648   91892 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
E0624 15:03:39.667631   91892 memcache.go:265] couldn't get current server API group list: the server has asked for the client to provide credentials
error: You must be logged in to the server (the server has asked for the client to provide credentials)


error while running training job

HI
Nice work !!
i am getting an error while running the training job. Any idea?
AlgorithmError: Exception during training: [Errno 2] No such file or directory: '/opt/ml/input/data/checkpoint/' Traceback (most recent call last): File "/opt/ml/code/train", line 95, in  file_list = os.listdir(tfrecord_pretrained_checkpoint_path) FileNotFoundError: [Errno 2] No such file or directory: '/opt/ml/input/data/checkpoint/'

figured it out. I didnt add the checkpoint channel. Closing


Feat: Adding trello util

Signed-off-by: Daniel Hu<EMAIL_ADDRESS>Summary
Adding trello util

Merging for now since it's already in another branch and we will test it from there.


add arrow indicator for url transformation

Enter your suggestions in details:
It took me embarrassingly long time figuring out which is the original URL and which is the modified one, but making it explicit would be nice.
As-is
🔥 /index.html /posts/index.tsx

To-be
🔥 /posts/index.tsx -> /index.html

Additional notes
I'm willing to open a PR when accepted (since it's tiny)

I wouldn't want to change the order of the files, because the most important part (I think) is the final URL. What do you think about reversed arrow?
🔥 /index.html <- /posts/index.tsx

i too think the final URL is important. however since most of the time sentences are read from left-to-right (e.g typescript function signature), thought using -> might make sense.

I'm thinking of maybe the original file would be visible only in DEBUG mode, but not by default (INFO mode). When the site has many pages or files to copy, there is too much text in the terminal. In DEBUG mode we can show them in the same order you're proposing. What do you think?

i think it's better to be explicit by default.


Update to major version 5

Summary

Decouplesnode-sass from this module, and requires users to explicitly set a compiler of their choice.
Upgrades our out-of-date dependencies (which also requires some minor changes to the test suite).
Bumps minimum Node version to 12.

Now that we require users to install their own compilers, it is not strictly necessary for us to bump our minimum Node version, but supporting Node versions that have hit EOL could complicate things in the future. It's worth noting that node-sass has adopted Node 12 as a minimum requirement.
New API
Major version 5 requires users to explicitly set a compiler by passing it to a curried function (per https://github.com/dlmanning/gulp-sass/pull/802#issuecomment-861236154). Both node-sass and sass compilers are permitted.
For example, in gulpfile.js:
# v4
- const sass = require('gulp-sass');
- const dartSass = require('sass');
- sass.compiler = dartSass;
# v5
+ const sass = require('gulp-sass')(require('sass'));

If the compiler is not set, gulp-sass will throw an error advising the user of this API.
Miscellaneous fixes
These issues relate either to the current version of the project bundling node-sass@4, or to our dependencies currently being outdated.

Issue list

resolves #801
resolves #797
resolves #785
resolves #782
resolves #780
resolves #799
resolves #798
resolves #775
resolves #768

Tasks

[x] Move node-sass to dev dependencies; update to version 6
[x] Update gulp to major version 4, to support new node-sass

[x] Update gulp plugins used for tests
[x] Update mocha tests for gulp compatiblity

[x] Change API for setting compiler, update tests to match
[x] Add new error about setting compiler
[x] Update other dependencies not broken by node-sass / Node 12 for better future stability
[x] Update readme, changelog

[x] Add a warning that fibers is not supported in Node 16 (per #771). Best practice is to use sync importers for now, and the Dart Sass team is working on a fix.

[ ] Update tests to provide confidence about dart-sass as compiler See https://github.com/dlmanning/gulp-sass/pull/802#discussion_r652940083

Thanks for all this effort. The comment about broad version support was with intention of not needing to bump the major to limit the impact on the ecosystem.
I agree the changes to support versions in node-sass forces our hand here, and we had planned to bump the major in order to make node-sass optional anyway.

Can the previously proposed updates the CONTRIBUTING.md and README.md also be ported into this PR?

Additionally, given we're bumping the major and updating the gulp dependencies, are you to confirm whether these proposed `README.md' make sense to be ported to this PR also?
Apologies I'm not in touch with gulp anymore.

Thanks for looking at my work! I can give the changes to Readme and Contributing a more thoughtful look tomorrow!
I noticed that the initial API for setting the compiler had users passing an argument, as with gulpSass(compiler). Should I revert to that, or keep the API where users set a compiler prop after defining gulpSass?

When I used gulp heavily the gulpSass(compiler) was a common pattern so I'd favour that approach unless there's a strong argument against it. I believe that linked commit is fairly close to feature complete, so I'd suggest taking that a starting point for this work.

That's for all the great effort. I'll take a closer look in the next couple days.

Thanks, @xzyfer! I still need to update the docs, and I can do that over the next couple days if you want!

Awesome!

Hey, @dlmanning! I've updated the README file to

document the new API
provide a short migration guide
warn about the EOL of node-fibers (we now suggest switching to renderSync)
use examples written for Gulp 4
include new badges to provide more info about this package

Here's the rendered markdown.
I have not updated the Changelog yet, as I saw that the Changelog consists mostly of your cut releases, and i can't cut those. Let me know if I should do anything else!

Amazing work!

Hi,
Thanks for this update. Is it possible to import this as an ES module ?
Like : import sass from 'gulp-sass';

Hey @cyrilverloop,
This release can’t be imported as an esmodule. I’m open to working on a release that supports both commonjs and esmodules (if @xzyfer thinks it’d be useful), but that would take a bit of effort.

Would this also require dart-sass and node-sass adopt esm?
On Sun, 27 Jun 2021, 9:22 am EJ Mason, @.***> wrote:

Hey @cyrilverloop https://github.com/cyrilverloop,
This release can’t be imported as an esmodule. I’m open to working on a
release that supports both commonjs and esmodules (if @xzyfer
https://github.com/xzyfer thinks it’d be useful), but that would take a
bit of effort.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dlmanning/gulp-sass/pull/802#issuecomment-869073122,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAENSWB7GN62JFOURM64FCDTUZOKLANCNFSM46WECMZQ
.

I don't know about dart-sass and node-sass, but using import worked in gulp-sass v4.

Can the compiler compiler be defined after the import ?

I might be wrong about ESM support here! I’ll test it when I’m at my desk. But yes, the compiler can be defined after import.

@cyrilverloop not sure you figured it out but this is my implementation after updating to v5
import dartSass from 'sass';
import gulpSass from 'gulp-sass';
const sass = gulpSass( dartSass );

@mae829 thanks for the import. Your solution works for me.
I recommend to put it in the documentation.

Thank you, @mae829! I agree that this should be in the docs and I will make a PR about it soon.


[Story] Setup a Discord server for OpenChallenges

What product(s) is this story for?
No response
As a user, I want
No response
Description

Review the server configuration of the NLP Sandbox Discord server
Collect the specifications for OC Discord server
Propose an architecture for OC Discord server

Acceptance criteria
No response
Tasks
No response
Anything else?
No response
Have you linked this story to a GitHub Project?

[X] I have linked this story to a GitHub Project and set its metadata.

Tentatively assigning @mdsage1

@tschaffter I just want to confirm that this:

Review the server configuration of the NLP Sandbox Discord server

will operate independently from our OpenChallenges infrastructure, i.e. I do NOT need to build this in via our Dev container?

[ ] Created an OpenChallenges server from the template proved on NLP Sandbox Discord server

@tschaffter What is meant by these:

Collect the specifications for DREAM Discord server
Propose an architecture for DREAM Discord server

Is this basically developing OpenChallenge specific channels?

I initially drafted the ticket to created a server for DREAM but let's create one for OC first. I updated the description of the ticket accordingly.
We can keep the "architecture" light for now with only a few channels (e.g. general, announcements). We also need a few roles, e.g. for admins, for members of the OC Team, and people who have accepted the Code of Conduct.
I accepted the invite and I'm now in the server. Thanks!

@tschaffter There are 5 channels that members can read and send messages. I've assigned roles for us and sent invitations to Verena and Rong.

Reopening because the Discord server is not fully configured yet (e.g. logo, rules)

@tschaffter
I have the OpenChallenges logo in the Server Overview tab. I'm unsure where else I should have added it.

@tschaffter I thought that we were using the new Rules feature that came standard with Discord.

See below. The rules are also empty, could you please find a suitable set of rules that you think the participants to the server should abide? There are probably many templates available out there so we shouldn't need to write our own from scratch.

Mentions of NLP sandbox have been replaced w/OpenChallenges in COMMUNITY/team, COMMUNITY/users, INFORMATION CHANNELS/rules, and INFORMATION CHANNELS/welcome.

Added the OpenChallenges logo to Discord.

The rules are updated and I have sent an invitation link to Gaia to become a member.

Added a new member requirement to send a message "Accept" in the rules channel.


Isolate configs among Hub

This pull request solves a legacy issue that we can not create multiple hub instances during one process.
Refs: #98

Codecov Report

Merging #100 into master will decrease coverage by 5.66%.
The diff coverage is 58.25%.

@@            Coverage Diff             @@
##           master     #100      +/-   ##
==========================================
- Coverage    53.2%   47.54%   -5.67%
==========================================
  Files          35       33       -2
  Lines        2545     2217     -328
  Branches      473      403      -70
==========================================
- Hits         1354     1054     -300
+ Misses       1020     1000      -20
+ Partials      171      163       -8

Impacted Files
Coverage Δ

src/presets/index.js
83.33% <ø> (-8.34%)
:arrow_down:

src/presets/ssr-auth-chain.js
1.24% <0%> (ø)
:arrow_up:

src/presets/ssr-auth-chain-b.js
0% <0%> (ø)
:arrow_up:

src/presets/mux.js
4.16% <0%> (+0.05%)
:arrow_up:

src/presets/obfs-http.js
0% <0%> (ø)
:arrow_up:

src/presets/ssr-auth-aes128.js
1.78% <0%> (+0.02%)
:arrow_up:

src/presets/auto-conf.js
3.79% <0%> (ø)
:arrow_up:

src/presets/ssr-auth-chain-a.js
0% <0%> (ø)
:arrow_up:

src/presets/ssr-auth-aes128-md5.js
0% <0%> (ø)
:arrow_up:

src/presets/ssr-auth-aes128-sha1.js
0% <0%> (ø)
:arrow_up:

... and 17 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 69a3d34...73a32ed. Read the comment docs.


Need to update information about rewards in the "Invite your friends now" feed transaction card and actualize it to our November event.

the campaign is just for november. this is not cruicial


circleci support for opentracing-java

build jar files using circleci

How do we test that this works?


[nrf fromtree] scripts: size_report: fix bug where key is used

https://github.com/zephyrproject-rtos/zephyr/pull/34213
When printing the unassigned values the 'sym' variable is
used as a dict from which we try to get the 'name' value.
However, 'symbols['unassigned']' gives a list of keys, so
we get an 'TypeError' when trying to access ['name'] of
a string (the key).
Fix this issue by iterating over the values from
the 'symbols['unassigned']' dict instead.
Signed-off-by: Håkon Øye Amundsen<EMAIL_ADDRESS>

can be closed, included in upmerge #507


rtabmap_ros: 0.20.22-1 in 'melodic/distribution.yaml' [bloom]

Increasing version of package(s) in repository rtabmap_ros to 0.20.22-1:

upstream repository: https://github.com/introlab/rtabmap_ros.git
release repository: https://github.com/introlab/rtabmap_ros-release.git
distro file: melodic/distribution.yaml
bloom version: 0.11.2
previous version for package: 0.20.20-1

Note: Merge https://github.com/ros/rosdistro/pull/35604 before this one.


Update existing commands and add updateVariable to the

Update WebRelay fork to make it compatible with new WebRelay xml endpoints.
These changes were made per the following spec found under section 3.2 of WebRelay Dual II X-301 Users Manual, revision 1.6.

@alobaidizt could we publish this to npm with a version

@jakesjews for sure!


uuid should be a production dependency?

The uuid dependency is imported in utils/context, but is only mentioned in devDependencies:
https://github.com/googleapis/nodejs-logging/blob/f4e892ed1342f3aacb8056212d75792959ab43b5/src/utils/context.ts#L31
https://github.com/googleapis/nodejs-logging/blob/f4e892ed1342f3aacb8056212d75792959ab43b5/package.json#L92
It feels like uuid should be a production dependency?

This is fixed in #1119


⚠ SceneTime has degraded performance

In 7996a8e, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 16043 ms

Resolved: SceneTime performance has improved in a12d899 after 6 minutes.


Add back function signature for compat

https://github.com/apache/druid/pull/13904
Added a 4th argument to a commonly-used public static method on Expressions.  This is commonly used in anything that happens to be planning aggregation from an extension, which means that it risks breaking extensions.  This PR re-adds the original signature, deprecated, with comments about how to update to avoid extension breakage.

The previous run of the tests on this failed with 2 types of failures:
Other tests failed due to coverage.  I think we can ignore that for now.
The Static Checks failed with
Error:  processing/src/main/java/org/apache/druid/data/input/MaxSizeSplitHintSpec.java:45 -- Field has one usage but it is not reachable from entry points.
Error:  processing/src/main/java/org/apache/druid/data/input/SegmentsSplitHintSpec.java:43 -- Field has one usage but it is not reachable from entry points.

Which is very much unrelated to my change.  I've added some supressions that hopefully make those disappear, but even if they don't, I think this is safe to merge.  Objections?


Change all non-valid values in leader 05 to c and report the change

Codecov Report

Merging #368 (f6e3e55) into main (2cb036a) will increase coverage by 0.09%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #368      +/-   ##
==========================================
+ Coverage   62.72%   62.81%   +0.09%
==========================================
  Files          81       81
  Lines        8072     8092      +20
==========================================
+ Hits         5063     5083      +20
  Misses       3009     3009

Flag
Coverage Δ

unittests
62.81% <100.00%> (+0.09%)
:arrow_up:

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

Impacted Files
Coverage Δ

src/folio_migration_tools/report_blurbs.py
100.00% <ø> (ø)

...ols/marc_rules_transformation/rules_mapper_bibs.py
66.51% <100.00%> (+0.38%)
:arrow_up:

tests/test_rules_mapper_bibs_no_folio.py
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Disable scroll zoom on occurrence page map

On an occurrence page, you can currently zoom the map with the scroll wheel (or touchpad): http://demo.gbif.org/occurrence/1233599085
As this functionality is also used to scroll up and down the page, it can become difficult to scroll beyond the map, especially on mobile devices. Try to put the cursor above the map and scroll down the page: instead of scrolling further, you zoom out on the map.
I would disable the scroll zoom on the map and have users use the + and - buttons. Scroll should be reserved for page scroll only.

The scroll is already disabled per default and only activated when interacting with the map. The height of the map is responsive such that it is always smaller than the height of the screen. This is exactly to ensure that the user do not get caught on the map on e.g. mobile devices and small screens.
We could consider disabling it completely. That might be acceptable for the occurrence page where little interaction is probably required. But for other pages with maps I would think that the above described behaviour makes better sense.
example of very small screen and the map adapting size

Great, didn't realize zoom was disabled if you didn't interact with the map first + map height not being too high. Well done, leave it as it is! 👍


p2os: 2.1.0-0 in 'lunar/distribution.yaml' [bloom]

Increasing version of package(s) in repository p2os to 2.1.0-0:- upstream repository: https://github.com/allenh1/p2os- release repository: https://github.com/allenh1/p2os-release.git- distro file: lunar/distribution.yaml- bloom version: 0.6.6- previous version for package: 2.1.0-0

uhm... That's some interesting behavior, right there... Please disregard this, I suppose.
@nuclearsandwich Is bloom Python 3 support close? I had been patching my way to this point and this happened...

I'm afraid that this will not have much visibility and doesn't provide much information to work on.
Did you consider opening an issue on the bloom repository with the details of what currently doesnt work ? or submitting PRs with your patches and details about why they are necessary?

@mikaelarguedas for sure! Wanted to investigate it more myself first. I was hoping for a valient "just working" type of patch, but, instead, made a bunch of noise and freaked everyone out.
I'll definitely post back when I know more!

@nuclearsandwich Is bloom Python 3 support close? I had been patching my way to this point and this happened...

It works up to a point, and that point is currently up to but not including pull request creation.

Wanted to investigate it more myself first. I was hoping for a valient "just working" type of patch, but, instead, made a bunch of noise and freaked everyone out.

If you can open a pull request with your current changes (it's okay if they are very WIP or unpolished as long as you mention as much) that will keep me from duplicating your work as I've also been looking for the time to get it fixed up.


The issue occurs after a userspace reboot.

After reboot, Dopamine automatically changes to "User," which prevents it from opening. It needs to be switched to "System" using Trollstore to function properly.

After reboot, Dopamine automatically changes to "User," which prevents it from opening. It needs to be switched to "System" using Trollstore to function properly.

It should be said that it occurs after Dopamine OTA, not userspace reboot.


how to selected value on select/select2?

I have like this
typeTest: {
    type: String,
    optional: true,
    autoform: {
      type: "select2", // or select
      options: function () {
        return [
          {label: "2013", value: 2013},
          {label: "2014", value: 2014},
          {label: "2015", value: 2015}
        ];
      }
    },
    defaultValue: "2015"
  }

I would like selected on 2015.
Please help me.

Maybe defaultValue: 2015 (without "")

Work fine.


Bug in Installing Unofficial patch for Stronghold Crusader. !!!

All this time I played on the English version of the Stronghold Crusade, and the Unofficial patch was installed normally. It was only worth upgrading to the Russian version of Stronghold Crusader, I got an error in the installation.

need help ....

Get the HD patch http://www.strongholdcrusaderhd.com/patch.html

@Sh0wdown Yes. But there is no Russian language there ...

Seems like the Russian version is very different from other versions in the "extended gamespeed" and "remove xtreme magic bar" settings. So either install without those settings or use a different language.
I will take a closer look later today.

@Sh0wdown it's fine ... I will play in the English version for now.

I will take a closer look later today.

ok thank you

@Sh0wdown
By the way, I finished the translation ...

@Sh0wdown
By the way, I finished the translation ...

Thanks! But you missed the UCP-Bugfix.aic.

@Sh0wdown hmm ...

seems liek this has been resolved, reopen if not!


add a year progress bar plugin

Looks like this:
28% ▓▓▓▓▓▓▓▓▓░░░░░░░░░░░░░░░░░░░░░░░ 104/365

I'm sorry but at some point we have to start rejecting plugins given the vast amount of them that already come prebundled. You can use your plugin as a custom plugin looking at the Customization wiki or even make a dedicated github repository and adding it to the list of external plugins. Thanks for your understanding.


SCT-5-AdminInterface - CRUD USER

also, I am thinking na yung function of updating and deleting ay nasa Profile/Profile Setting window ganern. What do u think @MostDeadDeveloper @elcuenca ?

What we can do is just to make the code more clean, import the data
retrieval functions from another library class
On Wed, 29 Dec 2021, 4:13 am Micaela Cerilla, @.***>
wrote:

also, I am thinking na yung function of updating and deleting ay nasa
Profile/Profile Setting window ganern. What do u think @MostDeadDeveloper
https://github.com/MostDeadDeveloper @elcuenca
https://github.com/elcuenca ?
—
Reply to this email directly, view it on GitHub
https://github.com/MostDeadDeveloper/student-concern-ticketing-system/issues/8#issuecomment-1002265458,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALT5OZW6RDLY6FH56DJORLTUTIK6TANCNFSM5KDNGM5A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID:
<MostDeadDeveloper/student-concern-ticketing-system/issues/8/1002265458@
github.com>

What we can do is just to make the code more clean, import the data retrieval functions from another library class
…
On Wed, 29 Dec 2021, 4:13 am Micaela Cerilla, @.***> wrote: also, I am thinking na yung function of updating and deleting ay nasa Profile/Profile Setting window ganern. What do u think @MostDeadDeveloper https://github.com/MostDeadDeveloper @elcuenca https://github.com/elcuenca ? — Reply to this email directly, view it on GitHub <#8 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ALT5OZW6RDLY6FH56DJORLTUTIK6TANCNFSM5KDNGM5A . Triage notifications on the go with GitHub Mobile for iOS https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Android https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub. You are receiving this because you were mentioned.Message ID: <MostDeadDeveloper/student-concern-ticketing-system/issues/8/1002265458@ github.com>

uhh medj diko mavisualize yung tinutukoy mo but sige noted


Buttons not working in Firefox

Buttons not working in Firefox

need source map for the scalajs build but
after updating project to latest tried to build js with  JsDev/fullOptJS
etcbut no joysbt:OpenStrat>Dev/fullOptJS error No such setting/task
also documentation on website fail
On Tuesday, 14 February 2023 at 14:24:36 GMT, Rich<EMAIL_ADDRESS>wrote:

Assigned #210 to @w0d.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were assigned.
Message ID: @.***>

tiz verking now..


gyp ERR! find VS unknown version "undefined" found at "C:\Program Files\Microsoft Visual Studio\2022\Community"

I am getting following error
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| win32 | x64
gyp info find Python using Python version 3.10.0 found at "C:\Users\harip\AppData\Local\Programs\Python\Python310\python.exe"
gyp ERR! find VS
gyp ERR! find VS msvs_version was set from command line or npm config
gyp ERR! find VS - looking for Visual Studio version 2022
gyp ERR! find VS running in VS Command Prompt, installation path is:
gyp ERR! find VS "C:\Program Files\Microsoft Visual Studio\2022\Community"
gyp ERR! find VS - will only use this version
gyp ERR! find VS unknown version "undefined" found at "C:\Program Files\Microsoft Visual Studio\2022\Community"
gyp ERR! find VS could not find a version of Visual Studio 2017 or newer to use
gyp ERR! find VS looking for Visual Studio 2015
gyp ERR! find VS - not found
gyp ERR! find VS not looking for VS2013 as it is only supported up to Node.js 8
gyp ERR! find VS msvs_version does not match this VS Command Prompt or the
gyp ERR! find VS installation cannot be used.
gyp ERR! find VS
gyp ERR! find VS **************************************************************
gyp ERR! find VS You need to install the latest version of Visual Studio
gyp ERR! find VS including the "Desktop development with C++" workload.
gyp ERR! find VS For more information consult the documentation at:
gyp ERR! find VS https://github.com/nodejs/node-gyp#on-windows
gyp ERR! find VS **************************************************************
gyp ERR! find VS
gyp ERR! configure error

Initially there were issue related to [gyp ERR! find VS find VS msvs_version not set from command line or npm config?]

So tried following commands and other options to resolve it,

>npm config set msvs_version 2022 --global
>npm config set msbuild_path "C:\Program Files\Microsoft Visual Studio\2022\Community\Msbuild\Current\Bin\MSBuild.exe"
>yarn install --global --production windows-build-tools

Downloaded and installed the microsoft build tools with Desktop development with C++.
tried setting the environment variable for VCINSTALLDIR to "C:\Program Files\Microsoft Visual Studio\2022\Community\VC"

But still there are errors mentioned as above
what could be the solution to this?

I'm getting the same error when trying to install dependencies for a large project.
I tried the same steps as you did to no avail as well.
Interestingly enough, I tried simply running the command MSBuild in command prompt and recieved an error as well.
I then set C:\Program Files\Microsoft Visual Studio\2022\Community\Msbuild\Current\Bin in my PATH environment variable.
The command works now in command prompt and PowerShell, but installing dependencies with yarn does not.
So basically +1. Looking forward to hearing ideas to fix this.

it doesn't worked for me with node 14
i have the path set correctly

VS2022 support was added in v8.4.0. The version you are using was not supported. Please try with the newer version.

Closing this issue, since the version of node-gyp used doesn't even support VS2022.


New package: Eltima.SerialOverEthernet version 9.0.1253

Checklist for Pull Requests

[x] Have you signed the Contributor License Agreement?
Resolve #160604

Manifests

[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.6 schema?

Note: <path> is the directory's name containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Verify:

This application requires purchase before it will allow enough interaction to verify the version it shows.

https://github.com/microsoft/winget-pkgs/issues/142854


Compiler does not have C++17 filesystem feature

Hey,
cmake durting configure decided that, let me quote:
2021-08-15T17:02:44.0016370Z -- -- Library stdc++fs NOT found -> linking utils without stdc++fs library

Anyway, build crashes with error:
2021-08-15T17:39:31.2269850Z cd /opt/local/var/macports/build/_Users_runner_work_1_s_ports_devel_retdec/retdec-devel/work/build/src/utils && /usr/bin/clang++ -DRETDEC_BUILD_DATE=\"2021-08-15T17:02:42Z\" -DRETDEC_GIT_COMMIT_HASH=\"GITDIR-NOTFOUND\" -DRETDEC_GIT_VERSION_TAG=\"HEAD-HASH-NOTFOUND\" -I/opt/local/var/macports/build/_Users_runner_work_1_s_ports_devel_retdec/retdec-devel/work/retdec-18b434f02b64bfb85232525ca10a6026b5d1f54f/include -I/opt/local/var/macports/build/_Users_runner_work_1_s_ports_devel_retdec/retdec-devel/work/retdec-18b434f02b64bfb85232525ca10a6026b5d1f54f/deps/whereami -pipe -Os -DNDEBUG -I/opt/local/include -stdlib=libc++ -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -fvisibility-inlines-hidden -Wall -Wextra -Wcast-align -Wcast-qual -Wswitch-default -Wuninitialized -Wold-style-cast -Wno-unused-parameter -arch x86_64 -isysroot /Library/Developer/CommandLineTools/SDKs/MacOSX10.14.sdk -mmacosx-version-min=10.14 -fPIC -std=c++17 -MD -MT src/utils/CMakeFiles/utils.dir/binary_path.cpp.o -MF CMakeFiles/utils.dir/binary_path.cpp.o.d -o CMakeFiles/utils.dir/binary_path.cpp.o -c /opt/local/var/macports/build/_Users_runner_work_1_s_ports_devel_retdec/retdec-devel/work/retdec-18b434f02b64bfb85232525ca10a6026b5d1f54f/src/utils/binary_path.cpp
2021-08-15T17:39:31.2542160Z In file included from /opt/local/var/macports/build/_Users_runner_work_1_s_ports_devel_retdec/retdec-devel/work/retdec-18b434f02b64bfb85232525ca10a6026b5d1f54f/src/utils/binary_path.cpp:9:
2021-08-15T17:39:31.2544360Z In file included from /opt/local/var/macports/build/_Users_runner_work_1_s_ports_devel_retdec/retdec-devel/work/retdec-18b434f02b64bfb85232525ca10a6026b5d1f54f/include/retdec/utils/binary_path.h:10:
2021-08-15T17:39:31.2547370Z /opt/local/var/macports/build/_Users_runner_work_1_s_ports_devel_retdec/retdec-devel/work/retdec-18b434f02b64bfb85232525ca10a6026b5d1f54f/include/retdec/utils/filesystem.h:19:3: error: "Compiler does not have C++17 filesystem feature."
2021-08-15T17:39:31.2548520Z         #error "Compiler does not have C++17 filesystem feature."

Thus, v4.0 builds well on this machine.
To make it easy, I've attached the full log of building for both v4.0 and master.
12.txt

Hi, the CMake message is not related to the error. It is useful only for gcc.
The problem is with <filesystem> include and its implementation in clang. The c++17 filesystem implementation in clang was included in macOS 10.15 ([Xcode release notes]) and from the logs, I see that you are using 10.14. I thought, however, that 10.14 does have experimental support. Can you check if you can compile a simple c++ program with the <experimental/filesystem> header?  There is a conditional include <experimental/filesystem> for this purpose in retdec/utils/filesystem.h.

@xkubov the hardest part: I haven't got access to this machine. I can reproduce it via macport's CI :)
Anyway, for me this issues related to unclear wording, nothing more.

Anyway, for me this issues related to unclear wording, nothing more.

@xkubov can you please address this (e.g. better message) and close this?


Availability of Predicted Data

Thanks for your exceptional work! I was wondering if you could provide the predicted data on Alpaca and Databricks datasets using the RL+Curiosity model.
Thanks for your assistance in advance!

Hi @qtli
Could you elaborate a bit about what "predicted data" is?

Thanks for your reply.
In section 4.4, we see that the red-team model can activate LLaMA2-7b-chat-hf, and Table 1 presents several examples. Since the paper discusses the curiosity-driven approach discovered 196 prompts that can elicit toxic responses. Can you please provide the complete list of these prompts? Also, if possible, can you share any remaining prompts during the optimization that do not make LLaMA2-7b-chat-hf unsafe? Thanks again for your assistance. I aim to use this information for further exploration.

Hi @qtli  , I've sent those prompts to you via email since I'm not sure if those prompts are appropriate to be made public.


Reverted changes related with removing php sdk dependency

Hello. I tested with different version of prestashop and revealed that some of them use guzzle composer package and there is conflict with guzzle  of php sdk(different versions). I decided to  back changes to previous version of our prestashop plugin.

Hey @chalk777, thanks for letting me know / reverting the change. will this still work with the docker container after the revert?

Hello. Yes.


MPI support

It is more a question than a proper issue for this feedstock.
I'd need fftw3_mpi in conda-forge. Similar to these Debian package:

https://packages.debian.org/stretch/libfftw3-mpi
https://packages.debian.org/stretch/libfftw3-mpi-dev

These packages depend on libfftw3 and openmpi. They do not contain the libfftw3 libraries.
It would be nice to have the same structure on conda, i.e. that the conda packages fftw and fftw_mpi would be compatible (fftw would be a dependence of fftw_mpi).
The code for fftwmpi-feedstock would be very similar than the one for this feedstock and it would also produce the same libraries as this recipe, so I'm wondering if it's a good thing to have another feedstock or if it would be possible with one feedstock to create two packages.

A few options.

We could have a nompi option similar to hdf5.
We should check howFFTW works. Maybe all of the libraries can coexist?

If we had a separate feedstock, we would only want to ship the MPI libs or make it incompatible with this one if they have to ship the same libs.

I have not used the MPI functionality, but I am pretty sure these get built as separate libraries in addition to the current ones.
I think aside from adding the MPI dependency in meta.yaml we just need to add --enable-mpi in the build scripts to get these variants.
See:
http://www.fftw.org/fftw3_doc/FFTW-MPI-Installation.html

Perhaps @rainwoodman might have a better idea as I think he has recent experience with MPI and FFTW

Based on a past PR that was never completed for pyFFTW, it seems that the library names for MPI are indeed different and have the same precision suffixes as the serial case:
e.g. libfftw3-mpi, libfftw3f-mpi, libfftw3l-mpi and there is a separate fftw3-mpi.h header corresponding to these.

Are there changes in the symbols in the other libraries?

@beckermr
For hdf5 does the version without nompi provide both serial and MPI variants along side each other or is it MPI only?
For FFTW it looks like both variants can coexist together. I think the main benefit of a nompi here would just be allowing the dependency on MPI to be removed and give a smaller download for users who aren't interested in that functionality.

Are there changes in the symbols in the other libraries?

As far as I can tell, it looks like all functions have _mpi in the function name, so the symbols do not conflict with those in the serial library.  e.g. fftw_mpi_execute_dft instead of fftw_execute_dft
see:
https://github.com/FFTW/fftw3/blob/master/mpi/fftw3-mpi.h#L201-L203

IDK about hdf5.
I think actually more than one output in this recipe is the right way to do this.
We build everything here in this feedstock. Then we supply two outputs.

an fftw-mpi package that has the dependence on the MPI provider and the MPI headers and SO's. 2. an fftw output that holds everything else

We build everything here in this feedstock. Then we supply two outputs.

That sounds reasonable. I didn't realize that was a possibility. I looked it up and found the following issue that links to an example recipe using the approach: in https://github.com/conda-forge/conda-forge.github.io/issues/746

Yep. This is documented in the anaconda docs as well. I can do this, but not until next week or so.

OK. Since the mpi libs can simply be installed along side everything else, I have instead decided to configure things like hdf5. There will be a preferred nompi package, but mpi-enabled variants can be installed. Packages build against the nompi variant can link to the mpi variants at runtime as well.

The configuration is a bit strange -- the mpi / no mpi does not feel like a variant. The mpi version may depend on the nompi version though.
I'd suggest splitting into two packages, fftw3 and fftw3-mpi, then treating mpich/openmpi as variants of the mpi package, either of which depends on fftw3.
This way the MPI package shall only ship with files for the MPI support (libfftw3-mpi.* and the mpi header). I know that conda supports generating subpackages, though I am not very familiar with the syntax.
fftw3
fftw3-mpi[openmpi]
fftw3-mpi[mpich]

The configuration is a bit strange -- the mpi / no mpi does not feel like a variant. The mpi version may depend on the nompi version though.

The mpi versions ship all of the normal files plus the mpi headers and libs, so there is no dependence between them.

I'd suggest splitting into two packages, fftw3 and fftw3-mpi, then treating mpich/openmpi as variants of the mpi package, either of which depends on fftw3.
This way the MPI package shall only ship with files for the MPI support (libfftw3-mpi.* and the mpi header).

Given the docs for MPI in conda-forge and what has been done for hdf5, we probably have to keep it this way. See the docs http://conda-forge.org/docs/maintainer/knowledge_base.html#message-passing-interface-mpi.

I know that conda supports generating subpackages, though I am not very familiar with the syntax.

I know this syntax and thought this originally at first too. However, given the packaging of hdf5, it makes more sense to do things this way.
The final bit here is that FFTW is not setup to have the MPI installation split out into separate packages. The installer is made to do it all at once (even though it does ship separate headers/libs). However this is an implementation detail of the upstream package. In the long term, mucking around here to split the monolithic build is not good practice. If we want a split build, we should make an issue upstream.

The conda-forge policy may be problematic.
Consider the scenario if a user needs a package A that depends on nompi and a package B that depends on mpich at the same time -- the policy seems to say the A and B cannot be co-installed in the same environment, even though they actually should be able to co-exist.
There are plenty of prior experience to follow. On Fedora, both packages are split into mpi and nonmpi sub-packages. The FFTW mpi subpackage depends on the nompi subpackage, while the HDF mpi subpackage doesn't. What about debian, gentoo, and ArchLinux?
============================================================== Name Matched: fftw* ===============================================================
fftw.x86_64 : A Fast Fourier Transform library
fftw-devel.x86_64 : Headers, libraries and docs for the FFTW library
fftw-static.x86_64 : Static versions of the FFTW libraries
fftw-mpich-devel.x86_64 : Headers, libraries and docs for the FFTW MPICH library
fftw-mpich-static.x86_64 : Static versions of the FFTW MPICH libraries
fftw-openmpi-devel.x86_64 : Headers, libraries and docs for the FFTW OpenMPI library
fftw-openmpi-static.x86_64 : Static versions of the FFTW OpenMPI libraries

========================================================= Summary & Name Matched: hdf5* ==========================================================
hdf5-mpich.x86_64 : HDF5 mpich libraries
hdf5-devel.x86_64 : HDF5 development files
hdf5-static.x86_64 : HDF5 static libraries
hdf5-devel.x86_64 : HDF5 development files
hdf5-static.x86_64 : HDF5 static libraries
hdf5-openmpi.x86_64 : HDF5 openmpi libraries
hdf5-mpich-devel.x86_64 : HDF5 mpich development files
hdf5-mpich-static.x86_64 : HDF5 mpich static libraries
hdf5-openmpi-devel.x86_64 : HDF5 openmpi development files
hdf5-openmpi-static.x86_64 : HDF5 openmpi static libraries

I don't make the rules. Raise this issue on the main conda-forge repos if you feel strongly.
The way this is addressed now is in the docs starting around

This doesn’t extend to nompi

and the build number bump and the lack of a run export for the nompi version.
For any package built against nompi fftw, the current build allows an mpi version to be used at run time. Thus for this build it is fine.

Thanks for the explanation. Now I see how it works, and the uneasiness is no longer as strong.  I am OK to  assume there are no packages where the nompi ABI and the nompi portion of the mpi ABI are incompatible. The magic number 100 still stinks, but not bad enough for changing the rule.


Support schemas in query builder

I might be missing something, but I don't see any examples of using the query builder to run a query in a specific schema. Looking through the code, I don't see any functions on the query builder to add a schema prefix either. I tried the snippet below to query my database:
const users = await db.table("app.user").where("id", 1).execute();
console.log(users);

But it fails with a PostgresError: relation "app.user" does not exist

Did you solve the above issue?

I wasn't able to solve the issue using the query builder. I had to write out the whole query.


Infer --app-version from package.json

This infers the --app-version from the package.json version property if it has not been passed in through the command line.
For an app using Electron 1.2.6 with a package.json version of 1.1.0:

Before
After

cc pairing with @kevinsawicki @jlord
Fixes #306

I added the docs-needed tag because I think this needs to be mentioned in at least docs/api.md. Not sure if it needs to be mentioned in the readme.

@malept Oh yeah, of course! Our oversight. I'll add that 👍

The consistent CI failures on OSX remind me why I didn't implement this feature myself - I couldn't figure out a way to get Wine to cooperate on Travis CI's OSX workers, so I just disabled those tests. Might have to do the same thing here.

I think I'm going to drop this for the 7.6.0 release and save it for a future non-patch release (which will cause a merge conflict in NEWS.md).

Got specs passing on Travis CI using wine, https://travis-ci.org/electron-userland/electron-packager/builds/153046665

Nice! The question becomes, is it consistent, or will tests time out sometimes? The inconsistent timeouts were why I had to stop installing wine on Travis OSX in the first place.

The question becomes, is it consistent, or will tests time out sometimes?

Yeah, since this PR causes way more tests to call rcedit via wine and the build passed on all 3 macs in the matrix configuration, I'm optimistic that things will be consistent given the new way wine is being installed and configured.
I haven't seen any failures on https://travis-ci.org/kevinsawicki/wine-darwin once the WINEDLLOVERRIDES env var was set which is also set now in this PR.

Not that I want to drag this PR out any longer, but should we have a test for the case where no app-version is specified and (for some reason) there is no version in any of the package.json files found?

I asked:

[...] should we have a test [...]

We talked about it this morning - I believe where we ended up is that it would be nice but it would take a lot of effort to handle this case, because you'd have to either:

Copy a fixture to a temporary directory (so that the electron-packager package.json doesn't get detected by get-package-info) - and even then, there could be inconsistent failures on dev machines where someone puts a package.json in their root temporary directory
Refactor that code to stop at the first package.json - I'm generally in favor of this method, but the concern was that it would break existing code (even though that wasn't an explicit feature)

@kevinsawicki please correct me if I'm misremembering.
My inclination is for the second option to happen, but not in this PR. It would also obviously be a breaking change that requires a major version bump.

🎉

Feel free to release 7.7.0 (or I can do it sometime after this afternoon). I need to add a couple of steps to the release docs for after running git push:

Create a new GitHub release from the pushed tag with the contents of NEWS for that version
Close the milestone associated with the version if one is open


Generics are not supported

TypeScript Generics are not currently supported, and importing a project with generics can cause a crash.
Cannot read properties of undefined (reading 'getSubInheritances')
TypeError: Cannot read properties of undefined (reading 'getSubInheritances')
    at Inheritance.setSuperclass (C:\Users\Cris\Documents\GitHub\FamixTypeScriptImporter\src\lib\famix\src\model\famix\inheritance.ts:20:19)
    at C:\Users\Cris\Documents\GitHub\FamixTypeScriptImporter\src\ts2famix.ts:115:35
    at Array.forEach (<anonymous>)
    at C:\Users\Cris\Documents\GitHub\FamixTypeScriptImporter\src\ts2famix.ts:110:28
    at Array.forEach (<anonymous>)
    at TS2Famix.famixRepFromPath (C:\Users\Cris\Documents\GitHub\FamixTypeScriptImporter\src\ts2famix.ts:99:29)
    at Object.<anonymous> (C:\Users\Cris\Documents\GitHub\FamixTypeScriptImporter\src\ts2famix-cli.ts:17:26)
    at Module._compile (node:internal/modules/cjs/loader:1101:14)
    at Module.m._compile (C:\Users\Cris\AppData\Roaming\npm\node_modules\ts-node\src\index.ts:1310:23)
    at Module._extensions..js (node:internal/modules/cjs/loader:1153:10)

To support generics, the metamodel will have to be adapted as in parameterizable types in Java. But this requires significant study of generics in TypeScript.
In the short-term, it is possible to prevent the crashing of the tool. See 20acaf02eeb6982ba9eb86a527dc70b7081ada01

Partially fixed in #9 but need more tests


Add per-command tracking to API out output detail page

Sorry for another undigestable refactor, but no way to do this incrementally.
This adds per-command tracking inside build environments and on the build
detail page. Instead of lumping build output together, this starts to break out
output and errors into logical chunks that will be easier to understand by end
users. The front end pieces make use of KnockoutJS for data binding objects to
the DOM. It performs an ajax call to the build api to return updates on the
build object and commands that are attached to the build object.
The API has the following changes:

:fire: API v1 build endpoint
Makes API v2 build endpoint usable
Adds API v2 command endpoint for adding commands
API v2 build endpoint returns nested commands for easier API calls
Adds necessary permissions to allow admin creation and authed/anonymous user
read-only access

Other than the inline comments: awesome!
That will make the build page so much better.
I haven't tried this locally, only looked at your screenshot. Can the output be scrolled horizontally?

And yeah, command/output elements are all independently horizontally scrollable

Looks good to me. :ship:

The UI really looks good in production :)
I noticed that the builds for the tickets #1028 #1572 do not contain any output:
https://readthedocs.org/projects/treeherder/builds/3256997/
https://readthedocs.org/projects/mongooseim/builds/3256523/
However, the users were able to provide a error message (stating something about wrong parameters to init). I wonder if the informational output got less after the deploy of this change.


SqlUpdate - Updating data in other tables

Dear,
I have the following situation several tables of equipment (computer, printers, projectors and etc ...) and a table of maintenance where register the maintenance of the equipment.
In the zyxGrid of each equipment there is an inline button that opens the Maintenance form and fills it with initial data (ID, patrimony, situation and model), when I change the situation from "Active" to "Maintenance" I want to change in the equipment table to situation.
Testing, I was able to do to a table using aftersave, the question how to check all tables.
Follow the code that is in the Maintenance repository.

Button that opens the Maintenance form.

After changing the situation to Maintenance and clicking the record button, triggers the event that changes the condition of the equipment in the source table.
Note: There are several tables that feed the Maintenance table.

Thank you

I solved by adding the maintenance table to the TypeEquipment field and doing the if in the repository

Thank you


Version 3.0 and above, the candidate words obtained are incomplete

Version 3.0 and above, the candidate words obtained are incomplete, and there is no prompt for the existing phrases in the custom dictionary.
The 2.0 version works normally.
Screenshot of the above situation:

Can you consider fixing this problem? Because I really like the new features of the 3.0 version, and the corresponding speed is faster, unlike the 2.0 version, there is a stuttering phenomenon.
Best wishes!

It is because version 3.0 and above only use prefix match, not partial match.
https://github.com/tadashi-aikawa/obsidian-various-complements-plugin/releases

Use prefix match instead of the partial match to reduce noisy suggestions

It needed to improve performance, so it is not easy to support them. If you want to use partial match at the expense of speed, please create another issue as a Feature Request. (I'll consider it if many people need it.)
Best regards.

I just came up with a workaround implementation.
You don't need to create a new issue, maybe :)

I just came up with a workaround implementation.

Wow, great, look forward to it.

Hi, @tyf2018.
I have uploaded beta version to tadashi-aikawa/obsidian-plugin-dev-sandbox 🚀
Could you confirm the above release note and try it by using BRAT?

Could you confirm the above release note and try it by using BRAT?

Your development efficiency is amazing! But I am outside now, I will continue to go back to the computer at night.

Could you confirm the above release note and try it by using BRAT?

After trial, it runs normally. Users can customize the settings according to their personal needs, which is very good! It is recommended to add it to the official version, thank you!

Users can customize the settings according to their personal needs, which is very good! It is recommended to add it to the official version,

Of course 👍 I want to release it this weekend.

Released at v3.2.0 🚀 .


Display Entity Tag even it has a wrong/no data

Ideally, add a remove button at the end of the EntityTag so the user may erase that invalid connection.

To handle:

[ ] empty class


admadl-sdk: required file ADL_SDK_6.0.zip is no longer available for download

pkgs/development/misc/amdadl-sdk requires ADL_SDK_6.0.zip from http://developer.amd.com/tools-and-sdks/graphics-development/display-library-adl-sdk/, but the oldest version available to download from that page is 7.0.

Any news on this issue?

package not in nixpkgs anymore


documentation should identify offset < 0 feature of uv_fs functions

Version: v1.x
Platform: N/A

I am just starting to use libuv, and was perplexed that there isn't a function to read from a file descriptor without seeking in the file. However, seeing some example code online, and upon examining the code, I've found that if -1 is used as the offset, then it does exactly this. However, this is not mentioned in the documentation at all. It just says "same as preadv".

PRs to improve the docs are always welcome - they are admittedly sparse in some places.

Will gladly do it if you point me at a file!

Sure thing: https://github.com/libuv/libuv/blob/v1.x/docs/src/fs.rst


[MAJOR] Link issues: Deleting one link, deleted both from one entity to two different ones.

Steps to reproduce

Create at least 3 labels
Put links from one entity to other (in one direction)
Delete one of links

Expected result
The selected link deletes.
Actual result
By deleting one link, both are being removed.
screen-capture (10).webm

Verified.


TEST: Feature/use multiprocessing.manager.queue

Critical Changes
Changes
Issues Closed

multiprocessing.Manager().Queue() was too slow.


Support grpclb address in the c-ares resolver

This change is

No significant performance differences

Overall, this looks great!  Just a few structural suggestions.

Reviewed 5 of 5 files at r1.
Review status: all files reviewed at latest revision, 5 unresolved discussions, some commit checks failed.

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.c, line 66 at r1 (raw file):

union {
grpc_resolved_addresses **addrs;
grpc_lb_addresses lb_addrs;
} addrs_out;
/ if true, the output addresses are in the format of grpc_lb_addresses,
otherwise they are in the format of grpc_resolved_addresses */
bool lb_addrs_out;

Instead of plumbing this difference through the whole code, I suggest having the resolver code always generate a grpc_lb_addresses struct, and then convert from that to grpc_resolved_addresses inside of grpc_resolve_address_ares_impl().

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.c, line 183 at r1 (raw file):

      for (i = prev_naddr; i < (*lb_addresses)->num_addresses; i++) {
        memset(&(*lb_addresses)->addresses[i], 0, sizeof(grpc_lb_address));
        if (hostent->h_addrtype == AF_INET6) {

I suggest making this a switch statement, so that the two sections (IPv6 and IPv4) are self-documenting.

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.c, line 315 at r1 (raw file):

      }
    }

Nit: Please remove blank lines within functions.  (Both here and throughout.)

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.c, line 432 at r1 (raw file):

  resolve_address_ares_impl(exec_ctx, name, default_port, interested_parties,
                            on_done, (void **)addrs,
                            true /* is_lb_addrs_out */);

Instead of hard-coding this here, how about adding a bool check_grpclb parameter to grpc_dns_lookup_ares() (which you've called grpc_resolve_grpclb_address_ares())?  That way, we can just have grpc_resolve_address_ares_impl() call grpc_dns_lookup_ares() and won't need an extra level of indirection.

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.h, line 62 at r1 (raw file):

  scheduled with \a exec_ctx, it must not try to acquire locks that are being
  held by the caller. */
void grpc_resolve_grpclb_address_ares(grpc_exec_ctx *exec_ctx, const char *addr,

Once you merge in the changes from #10706, which I merged this morning, you can just change the grpc_dns_lookup_ares() function that I wrote to return a grpc_lb_addresses struct instead of a grpc_resolved_addresses struct.

Comments from Reviewable

Thanks a lot for your review!

Review status: 1 of 5 files reviewed at latest revision, 6 unresolved discussions.

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.c, line 66 at r1 (raw file):
Previously, markdroth (Mark D. Roth) wrote…

union {
grpc_resolved_addresses **addrs;
grpc_lb_addresses lb_addrs;
} addrs_out;
/ if true, the output addresses are in the format of grpc_lb_addresses,
otherwise they are in the format of grpc_resolved_addresses */
bool lb_addrs_out;

Instead of plumbing this difference through the whole code, I suggest having the resolver code always generate a grpc_lb_addresses struct, and then convert from that to grpc_resolved_addresses inside of grpc_resolve_address_ares_impl().

As grpc_resolve_address_ares_impl() and grpc_dns_lookup_ares() are async operations, we'll need an extra level of callback for grpc_resolve_address_ares_impl() to convert the result from grpc_lb_addresses to grpc_resolved_addresses. It will also bring some extra memory allocs, frees, and copies.
It might be good to save this extra level of callback and the memory operations, by still having these fields in grpc_ares_request and handling the conversion in on_hostbyname_done_cb.

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.c, line 183 at r1 (raw file):
Previously, markdroth (Mark D. Roth) wrote…
I suggest making this a switch statement, so that the two sections (IPv6 and IPv4) are self-documenting.

Done.

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.c, line 315 at r1 (raw file):
Previously, markdroth (Mark D. Roth) wrote…
Nit: Please remove blank lines within functions.  (Both here and throughout.)

Done.

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.c, line 432 at r1 (raw file):
Previously, markdroth (Mark D. Roth) wrote…
Instead of hard-coding this here, how about adding a bool check_grpclb parameter to grpc_dns_lookup_ares() (which you've called grpc_resolve_grpclb_address_ares())?  That way, we can just have grpc_resolve_address_ares_impl() call grpc_dns_lookup_ares() and won't need an extra level of indirection.

Done.

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.h, line 62 at r1 (raw file):
Previously, markdroth (Mark D. Roth) wrote…
Once you merge in the changes from #10706, which I merged this morning, you can just change the grpc_dns_lookup_ares() function that I wrote to return a grpc_lb_addresses struct instead of a grpc_resolved_addresses struct.

Changed grpc_dns_lookup_ares() to handle both grpc_lb_addresses and grpc_resolved_addresses.

Comments from Reviewable

No significant performance differences

No significant performance differences

Reviewed 3 of 4 files at r2, 1 of 1 files at r3.
Review status: all files reviewed at latest revision, 1 unresolved discussion, some commit checks failed.

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.c, line 66 at r1 (raw file):
Previously, y-zeng (Yuchen Zeng) wrote…
As grpc_resolve_address_ares_impl() and grpc_dns_lookup_ares() are async operations, we'll need an extra level of callback for grpc_resolve_address_ares_impl() to convert the result from grpc_lb_addresses to grpc_resolved_addresses. It will also bring some extra memory allocs, frees, and copies.
It might be good to save this extra level of callback and the memory operations, by still having these fields in grpc_ares_request and handling the conversion in on_hostbyname_done_cb.

I'll leave it up to you, but I suspect that the extra level of indirection would be the better approach here.  It's true that the extra level of indirection would be slightly less efficient, but it's not in the fast path, so it shouldn't really hurt anything.  And I think the benefit of the cleaner code would be worth the trade-off.

Comments from Reviewable

No significant performance differences

No significant performance differences

Review status: 2 of 5 files reviewed at latest revision, all discussions resolved.

src/core/ext/filters/client_channel/resolver/dns/c_ares/grpc_ares_wrapper.c, line 66 at r1 (raw file):
Previously, markdroth (Mark D. Roth) wrote…
I'll leave it up to you, but I suspect that the extra level of indirection would be the better approach here.  It's true that the extra level of indirection would be slightly less efficient, but it's not in the fast path, so it shouldn't really hurt anything.  And I think the benefit of the cleaner code would be worth the trade-off.

I've thought about the options, and moved the conversion code to the callback of  grpc_resolve_address_ares_impl() as you suggested.  After c-ares resolver becomes the default one, client channel should only use grpc_ares_dns_lookup(). The extra level of indirection will only affect the credential verification process. Thanks a lot for your suggestion!

Comments from Reviewable

No significant performance differences

Performance differences noted:
Benchmark                         cpu_time    real_time
--------------------------------  ----------  -----------
BM_HasClearGrpcStatus<ErrorNone>  +4%         +4%

No significant performance differences

No significant performance differences

No significant performance differences

No significant performance differences

Known issues:
Asan C++: #11120
Basic Tests Linux: #11122
Basic Tests Mac: #11223, #9380

Filed #11424 for https://grpc-testing.appspot.com/job/gRPC_pull_requests_tsan_c/5092/testReport/junit/(root)/c_linux_tsan_native/bins_tsan_sequential_connectivity_test_GRPC_POLL_STRATEGY_epollsig/

Still LGTM.  Thanks for doing this!

Thanks a lot for your review!


Clarification on Metrics in ChatKBQA Results Reproduction

Hello,
I am attempting to reproduce the results of ChatKBQA on the WebQSP dataset, and I have some confusion regarding the metrics used. Specifically, I am trying to determine which of the provided metrics in the repository corresponds to the "F1 Hits@1 Acc 79.8 83.2 73.8" reported in the paper's results.
In the repository, the following metrics are provided for the WebQSP dataset:
total:1639,                      ex_cnt:1026,                      ex_rate:0.6259914582062233,                      real_ex_rate:0.6424546023794615,                      contains_ex_cnt:1227,                      contains_ex_rate:0.74862721171446                     real_contains_ex_rate:0.7683155917345021
I would appreciate it if you could help me understand which of these metrics corresponds to the "F1 Hits@1 Acc" reported in the paper. This clarification will greatly assist me in accurately reproducing the results.
Thank you for your assistance.
Best regards,

This is just an intermediate result; we still need to evaluate the KBQA result with Retrieval.

Thanks for clearance, after evaluation I got following results, seems match with paper:
Number of questions: 1639 Average precision over questions: 0.785 Average recall over questions: 0.814 Average f1 over questions (accuracy): 0.783 F1 of average recall and average precision: 0.799 True accuracy (ratio of questions answered exactly correctly): 0.740 Hits@1 over questions: 0.829
Regards the evaluate process, I found some predicted answers format is unmatched with the label. For example, for question: "WebQTest-362", the predict answer is ['1968-01-01 00:00:00'], while the label are "'m.016j83', 'm.01gqg3', 'm.037pbp', 'm.03kz35', 'm.03r8xj', 'm.03xvj', 'm.03ymyvf', 'm.045...."
This will lead to a decrease of the final accuracy, right?

It should be. The outcome of the query seems to be time-related, but in reality, it's a collection of entities of the label type.

Continue to evaluate the other entries
The problem WebQTest-2024 is not in the prediction set
Continue to evaluate the other entries
The problem WebQTest-2025 is not in the prediction set
Continue to evaluate the other entries
The problem WebQTest-2027 is not in the prediction set
Continue to evaluate the other entries
The problem WebQTest-2028 is not in the prediction set
Continue to evaluate the other entries
The problem WebQTest-2029 is not in the prediction set
Continue to evaluate the other entries
The problem WebQTest-2030 is not in the prediction set
Continue to evaluate the other entries
The problem WebQTest-2031 is not in the prediction set
Continue to evaluate the other entries
Number of questions: 1639
Average precision over questions: 0.000
Average recall over questions: 0.000
Average f1 over questions (accuracy): 0.000
测试过程中出现上述的结果，是Virtuoso 没成功开启吗？

Hello, I have a question about the difference between "Train LLMs for Logical Form Generation" and "Beam-setting LLMs for Logical Form Generation"when fine-tuning the large model，can I make ft directly in Beam search.

Training LLMs for Logical Form Generation is the SFT phase, which is the training phase. Beam-setting LLMs for Logical Form Generation uses the SFT-trained model to perform beam search generation, which is not a training phase.


telegram bot forwarding message format

Describe the bug
telegram bot forwarding message needs newline for better reading
Steps to reproduce

send public memos
check the channel to view the format of forwarded memos

Screenshots or additional context
No response

fixed in https://github.com/edonyzpc/memos/commit/28251fd8f58c6f883a9aeef6b32bc43f8230dbf4


Manual build instructions fails with dex exception

The current manual build instructions throws a multiple dex files exception.
Build instructions:
Manual

You can copy this library jar and all its dependency jars to a folder as follows:

git clone git@github.com:coinbase/coinbase-android-sdk.git
cd coinbase-android-sdk
mvn dependency:copy-dependencies -DincludeScope=runtime -DoutputDirectory=$YOUR_JAR_DIRECTORY
mvn package
cp target/coinbase-android-sdk-1.0.1.jar $YOUR_JAR_DIRECTORY

Error seen:
UNEXPECTED TOP-LEVEL EXCEPTION:
com.android.dex.DexException: Multiple dex files define Lorg/apache/http/annotation/GuardedBy;
	at com.android.dx.merge.DexMerger.readSortableTypes(DexMerger.java:596)
	at com.android.dx.merge.DexMerger.getSortedTypes(DexMerger.java:554)
	at com.android.dx.merge.DexMerger.mergeClassDefs(DexMerger.java:535)
	at com.android.dx.merge.DexMerger.mergeDexes(DexMerger.java:171)
	at com.android.dx.merge.DexMerger.merge(DexMerger.java:189)
	at com.android.dx.command.dexer.Main.mergeLibraryDexBuffers(Main.java:454)
	at com.android.dx.command.dexer.Main.runMonoDex(Main.java:303)
	at com.android.dx.command.dexer.Main.run(Main.java:246)
	at com.android.dx.command.dexer.Main.main(Main.java:215)
	at com.android.dx.command.Main.main(Main.java:106)
Error:Execution failed for task ':app:dexDebug'.
> com.android.ide.common.process.ProcessException: org.gradle.process.internal.ExecException: Process 'command '/Library/Java/JavaVirtualMachines/jdk1.8.0_45.jdk/Contents/Home/bin/java'' finished with non-zero exit value 2

The library that causes this error is httpclient-4.0.1.jar. The fix is to remove it:
rm $YOUR_JAR_DIRECTORY/httpclient-4.0.1.jar

Thanks, updated README. I would highly suggest you use gradle instead of the manual method though.

I was trying to use the patch that opened the Coinbase app if available. :)

Ah, for future reference you can run mvn install to install the dev version (1.0.2-SNAPSHOT) into your local maven repository and point your gradle at 'com.coinbase.android:coinbase-android-sdk:1.0.2-SNAPSHOT'
The Coinbase app does not yet support native authentication.


Updating Resources From Environment File Not Possible

When we upload aasx, json or xml files from the environment container, we can not update these resources again.
We need to restart the container - or start a new one - to upload the static file information again.
If the data is persisted in MongoDB, an exception is thrown in the "upload"-SpringBean on a new startup of the environment container.
We should handle exceptions and upload the updated resources when restarting the environment-container.
Possible approach:

use the "administration" attribute with version and revision to indicate that the resource (shell, content-description, submodel) changed
always override resources when no version or revision is assigned to the existing resource and the new resource
if version or revision is set, update the resource only if at least one of the attributes changed

Nice to have:
Monitor file changes with spring integration and handle file changes to upload aasx resources

Closed with linked PR.


[form-field] add md-error-container directive to content projection

Bug, feature request, or proposal:
Proposal
Currently
If a user wishes to surround MdErrors with a structural directive, the errors will no longer be projected inside the mat-input-subscript-wrapper.
<!-- This will not work -->
<md-form-field>
  <input mdInput>
  <ng-container *ngFor="let error of allErrors">
    <md-error *ngIf="showError(error)">{{error.message}}</md-error>
  </ng-container>
</md-form-field>

This is (sort of) expected behavior if you know that content projection works only on top level elements. Still, if you want to conditionally render your errors with ngFor and ngIf you have to use one of the workarounds (listed under Motivation).
Proposed
<!-- This could work -->
<md-form-field>
  <input mdInput>
  <md-error-container *ngFor="let error of allErrors">
    <md-error *ngIf="showError(error)">{{error.message}}</md-error>
  </md-error-container>
</md-form-field>

<!-- form-field.html -->
...

<div *ngSwitchCase="'error'" [@transitionMessages]="_subscriptAnimationState">
  <ng-content select="md-error, md-error-container"></ng-content>
</div>

Reproduction
This is an example showing how it could work
http://plnkr.co/edit/6c6Zi6m1dNAnF10smWPK?p=preview
Motivation
Couple of issues bringing this up
https://github.com/angular/material2/issues/5263
https://github.com/angular/material2/issues/5292
Workarounds:
https://github.com/angular/material2/issues/5263#issuecomment-309915318
https://github.com/angular/material2/issues/5263#issuecomment-324671153

Good ideia, however it still fails if you want to abstract some complex logic in a separated component, like this:
<md-form-field>
  <input mdInput>
  <app-form-validation [control]="myCtrl"></app-form-validation>
</md-form-field>

app-form-validation.component.ts:
<md-error-container *ngIf="control.errors | keys | first as firstError">
  <md-error [translate]="'errors.messages.' + firstError"
            [translateParams]="getFormattedError(firstError)"></md-error>
</md-error-container>

Good point. I suppose it could also work as an attribute?
<md-form-field>
  <input mdInput>
  <app-form-validation md-error-container [control]="myCtrl"></app-form-validation>
</md-form-field>

<md-form-field>
  <input mdInput>
  <ng-container md-error-container *ngFor="let error of allErrors">
    <md-error *ngIf="showError(error)">{{error.message}}</md-error>
  </ng-container>
</md-form-field>

@willshowell, I do not remember where I found it, but you can use, as an acceptable workaround, the ngProjectAs (maybe I'm not getting right the big picture here):
<md-form-field>
  <input mdInput>
  <ng-container *ngFor="let error of allErrors" ngProjectAs="md-error">
    <md-error *ngIf="showError(error)">{{error.message}}</md-error>
  </ng-container>
</md-form-field>

I will look for the reference where I got this.

Whoa thank you @julianobrasil! I've skimmed that article a half dozen times but somehow missed it each time. Personally, I think utilizing ngProjectAs is better than adding more fluff to the api, though I do agree that it requires the consumer to know ng-content is being used internally.
@rafaelss95 what do you think? That should also solve your logic encapsulation use case, right?

@julianobrasil @willshowell It's an awesome solution for simple cases, but for the case that I descibred (until I'm missing something here) it still fails.
Reproduction

@rafaelss95, I think you are right. The using of ngProjectAs won't work because <md-error> would be two levels bellow <md-form-field>. Unless someone finds out that there is another "undocumented" way to nest ngProjectAs or something like that, @willshowell's idea (the directive) seems to be the way to follow IMO.

@julianobrasil At the first, I thought the same, however the surprise (at least for me) is that it works when it's wrapped by two (or even more) "tags"...
Check this plunker

I think there may be a bug in core. This shows all 4 errors (3 from app-form-validation):
  <md-form-field>
    <input mdInput [formControl]="myControl" required>
    <app-form-validation ngProjectAs="md-error"></app-form-validation>
    <ng-container ngProjectAs="md-error">
      <md-error>This field is required</md-error>
    </ng-container>
  </md-form-field>

http://plnkr.co/edit/2VqnymNAkTzRCOyK0dT1?p=preview
...while (as demoed), this doesn't show any:
  <md-form-field>
    <input mdInput [formControl]="myControl" required>
    <app-form-validation ngProjectAs="md-error"></app-form-validation>
  </md-form-field>

I agree. It really seems like a bug in core. Do you mind to fill an issue there?

Oh, these are great news! It would be kind of frustrating to find out that ngProjectAs "almost" solved the problem. Hope this is just a bug.

I tried to reproduce to file an issue, but have had no luck. @rafaelss95, @julianobrasil could either of you look over this to make sure I'm not missing something?
http://plnkr.co/edit/pF09Kc7DwZS7Wb1Mj6L8?p=preview
It may actually be an issue specific to MdFormField. In that case, this issue could be repurposed to make sure ngProjectAs can be properly used for error messages.

@willshowell, I saw no problem with your code. In fact I tried something similar with md-list, and md-select. But the problem is that these two work even without ngProjectAs: https://plnkr.co/edit/v16XIXmeH1jgID7X7HJH?p=preview.
We're running out of options (except for blaming md-form-field).

This mess a little bit with ngProjectAs too (the icon goes to the end of the line):
 <md-list-item *ngFor="let note of notes">
    <ng-container ngProjectAs="md-icon">
      <md-icon md-list-icon>folder</md-icon>
    </ng-container>
    <h4 md-line>{{note.name}}</h4>
    <p md-line> {{note.updated | date}} </p>
  </md-list-item>

Plunk: https://plnkr.co/edit/WcfB6eZySPXMPlTXZDG6?p=preview

Haven't tested by running it locally, but it looks to be due to the @ContentChildren query for MatErrors
https://github.com/angular/material2/blob/7fe1b81a47b6de036ae85c183328400e45c40b15/src/lib/form-field/form-field.ts#L157
I suspect if it were to use {descendants: true}, then you could abstract the logic to a child component. However, I don't know if there are any downsides to this (cc @mmalerba).
Here's an updated StackBlitz of the issue.

I think it should be fine to use {descendants: true}, anyone want to send a PR?

@willshowell do you mind to send a PR?

I gave it a shot, and I could be missing something, but it looks like descendants: true is for deeper levels of content projection, not for looking inside other components. This was not the easy-out that I hoped it might be.
I then figured you should be able to provide your custom error component as MatError
providers: [
  { provide: MatError, useClass: MyFancierError }
]

but I discovered QueryChildren matches on Type instead of InjectionToken, so I think that's a dead end too..?
Since ngProjectAs handily covers my initial purpose in opening this issue, I'm going to close it.
@rafaelss95 if you ever discover a way to achieve what you need or end up filing something in core, please report back!


No information in official doc regarding implementation of class_weight in customized model.fit() method

Hi,
I have customized the standard model.fit() method based on the help/steps described in the official page. Now, I would like to use the class_weight in this customized function but I do not see any help regarding class_weight implementation in official page under the heading Supporting sample_weight & class_weight. Kindly help me to understand how to implement class_weight in this case?
Note: This issue is raised here after feedback from @saikumarchalla (earlier raised here)
Best Regards

@n33lkanth Could you please refer to this thread and let us know if it helps?
Thanks!


Mx7 construct error on widget

Hi, I tried running the widget in mx v7 and got the 'No constructor found for widget' error. Could you please upgrade it as we need to use it for our project. I have used it previously and its a great widget overall.
If you need contact me please feel free to do so on<EMAIL_ADDRESS>for any testing that might be require.d
Thanks in advance,
Savan

I have tested v5.2.1 in Mx 7.0.2 and don't get any error. Could you please check this version for me? If the issue persists, I need to have some kind of error or test-project to test this. Please contact Support.


Refactor AddPipdeForm

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

/approve


High Level Goals for the next Third

This is a high level overview of potential plans for this repo over the next few months:
Priorities

[x] Wrap up the light-client release - https://github.com/informalsystems/tendermint-rs/milestone/1 (any other issues?)~~
[x]  Wrap up the light-client verification spec (support with IBC)
[x] Integrate model-based testing for the light client and more comprehensive test suite - #320, #330, #393
[ ] Support IBC effort with anything it might need from light-client or tendermint types - https://github.com/informalsystems/ibc-rs/issues/60
[ ] Fork accountability spec and support for the Go implementation
[ ]  Light Client Evidence Submission - #415
[x] Upgrade to be compatible with Tendermint v0.34 (ie. protobuf migration!) - #305

Common Goals

[x] Wrap up the fork detection English spec (not sure if we should focus on the TLA+ for it now)
[x] Absorb rust-abci repo (and potentially build out a rust abci client) - #29

[ ]  Potentially also support some very basic application development framework

[x] Improve the websocket connection - #311, #313
[x]  Release 0.16.0 - https://github.com/informalsystems/tendermint-rs/milestone/3
[ ] Type Generalizations - #416
[x]  Productionization Efforts  (documentation, crate organization, release process) - #323
[x] Compiling to WASM - #463

Stretch Goals

[ ] Implement the Tendermint MConnection, bring back SecretConnection from tmkms, and run a simple node that can make p2p connections to tendermint full nodes and exchange PEX messages (without any logic or address book ...) - to discuss and open issues about

I may suggest absorbing @devashishdxt https://github.com/devashishdxt/abci-rs instead, as 1) it works with rust async (so doesn't bring in legacy tokio 0.1 deps), 2) it was planned to replace the current rust-abci implementation:
https://github.com/tendermint/rust-abci/pull/112 but delayed for the moment.
So I think it's a better starting point -- instead of the custom wrapper types, it can perhaps reuse parts of tendermint-rs?

I may suggest absorbing @devashishdxt's rearchitected devashishdxt/abci-rs instead, as 1) it works with rust async, 2) has some desired features in place (e.g. unix domain socket support), 3) it was planned to replace the current rust-abci implementation:
tendermint/rust-abci#112 but delayed for the moment.

I agree with making this change. I would just like to point out that this may change some of the goals listed above as the current implementation may not be compatible with 0.34 of Tendermint-Go (state-sync, block pruning, runtime event indexing, ...).

I may suggest absorbing @devashishdxt's rearchitected devashishdxt/abci-rs instead, as 1) it works with rust async, 2) has some desired features in place (e.g. unix domain socket support), 3) it was planned to replace the current rust-abci implementation:
tendermint/rust-abci#112 but delayed for the moment.

I agree with making this change. I would just like to point out that this may change some of the goals listed above as the current implementation may not be compatible with 0.34 of Tendermint-Go (state-sync, block pruning, runtime event indexing, ...).

will any of those have a big impact on abci-rs? For state-sync, it may just be protobuf update + extra trait / functions for it + expecting one more TCP/UDS connection?

I think this issue's been open for much longer than the initially anticipated quarter :slightly_smiling_face: I'm closing it for now in favor of the Q3 2021 milestone. I've moved the majority of the still-open issues/requirements to this new milestone with the exception of:

Fork accountability spec and support for the Go implementation (is there an issue specifically for this somewhere in one of our repos?)
Type generalizations #416


⚠ Bofrost.lu has degraded performance

In 8880fb4, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1578 ms

Resolved: Bofrost.lu performance has improved in d395c47 after 6 minutes.


Glorfindel: Blacklist ketonesbodyprotry.com

Glorfindel requests the blacklist of the following website(s):

ketonesbodyprotry.com - MS search

ketonesbodyprotry.com has been seen in 29 true positives, 0 false positives, and 0 NAAs.


When i deploy the bot

Heruko wants me too enter payment methods
https://prnt.sc/t90sas
but everything is free
https://prnt.sc/t90shy
how to fix

To be able to use plugins in general, you have to enter credit card information.
It won't charge you, it's just to verify the account.


getPixelForTick is confusing and possibly inconsistent

It looks to me like sometimes it's doing getPixelForTick and sometimes it's doing something more akin to getPixelForIndex. This gets especially confusing in certain cases like when autoSkip is enabled or you have auto tick generation on the time scale where ticks and indexes don't map 1:1.

I can't seem to find where its used akin to getPixelForIndex?
I'd keep the data separated from scale interface - so scale does not need to know how data is input, parsed or stored internally by the controllers.
If getPixelForIndex is required, it should be placed in controller. But I'd rather not have such a method, it does not make sense if data is object:
data: { Jan: {o: 10, h: 11, c: 9, l: 8}, Feb: ...}

I think getPixelForTick acts like getPixelForIndex in the category scale where that's by design

The main reason I'm confused is that when we autoSkip we pass in tick._index, which is the original index before the autoSkip happened (getPixelForGridLine is a wrapper around getPixelForTick):
https://github.com/chartjs/Chart.js/blob/a3392e0e59ae77a9c081b4c14de2c95a35422e18/src/core/core.scale.js#L1014

That may be because for the longest time, the auto skip was just not drawing the ticks. Now that we reduce the tick array into the smaller to draw array, I think we should pass the index in that array


README.md: Fixed typo and follow link

Changed 'Table of content' to 'Table of contents'.
Clicking on 'Contribution Guidelines' now follows the link.

The CI failure can be resolved by rebasing onto the latest commits from master.

WIll create another pull request


Integer Test case added

Fixes #2016
Please have a look and let me know if this is what was required

Might want to flatten the commits as well, as I made a small mistake by making the input a string before

We always squash commits, so no need to worry about it.


Campaign proposal: Withholding unpaid review work from profitable publishers

Action
This campaign will ask researchers to pledge to refuse to serve as unpaid scientific reviewers from profitable publishers once a threshold of pledges has been received.
Threshold
Pledges will activate when 100 researchers have pledged to quit reviewing.
Anonymity
Pledges will be optional- people can choose whether they want their names to be public or not.
Rationale

Scientific publishers rely on the unpaid labour of reviewers and editors to reap massive amounts of profit. This one is obvious.

Publishers have pitted us against each other.
The publishing industry has created the perfect system that makes everyone feel like they should contribute for free.
Authors need editors and reviewers. Editors need to find reviewers. Reviewers (sometimes) need to review papers “for their jobs”. All for free. If one part of the triangle quits, the others suffer. Why do we feel bad about turning down reviews when the publisher is clearly taking advantage of us all?

There is no way to improve our review system.
There are many problems with peer review, but with the current publishing system it’s nearly impossible to fix these issues. How do you hold reviewers accountable for passing a bad paper? For late reviews? For writing a mean or hurtful review?  Stop inviting them?  That’s not much of a punishment when it’s just free work.

Some thoughts and Questions
The letter
I have created a draft letter that can be returned to the editor when a review request is received. I welcome comments and feedback on it. Although, I think individuals will probably need to tailor it a bit for their own situation.
Review response.docx
1. Which publishers/journals to boycott/support?
Based on this information (https://www.wischenbart.com/upload/Global50-2018_overview_ToC.pdf) I compiled a list of the most profitable publishers who publish psychology journals. I suggest we boycott the following publishers:
Elsevier (RELX Group)
Springer Nature (Nature Publishing Group including Frontiers Media)
Wiley
Taylor & Francis (Informa PLC)
Oxford University Press
Wolters Kluwer
APA (not in the above document)
Sage (no published profit information)
1b. Where to review instead?
Rather than creating a list of 'blacklisted' journals, which would be very long, it's probably easier to create a 'whitelist' of fee-free/community-friendly journals. This list is under development here. Please add any journals that you think should be on there by editing the document.
2. Do we begin with limiting pledges to psychology/behavioural science?
Perhaps we can expand to other fields if there is enough interest.
3. I also think we should continue to write and submit articles like normal, but just stop reviewing.
I think it's too much to ask people to quit submitting papers, as well. So I propose that we continue to submit papers to the outlets that we are no longer reviewing for. This will serve a few purposes. First, it will create a backlog of papers that need to be reviewed, keeping the demand for payment steady. Second, we technically do get paid to produce research. Third, this campaign is not about boycotting publishing as a whole (as much as I love preprints), or even about boycotting publishers, so we need to pick our battles. Plus, we all probably want to continue our work.
4. Timeline
How long should the pledge stage operate? If we don’t receive enough pledges within a certain period of time, what do we do?
5. How many pledges until the boycott starts?
Is 100 a reasonable number to begin the boycott?
Some extra literature and information
https://nces.ed.gov/surveys/libraries/aca_data.asp
https://figshare.com/articles/Journal_subscription_costs_FOIs_to_UK_universities/1186832
https://alexholcombe.wordpress.com/2015/05/21/scholarly-publisher-profit-update/
https://www.pnas.org/content/early/2014/06/11/1403006111.abstract

Awesome work @jonmcphetres! I think this campaign will get a lot of traction. Some initial thoughts:

2. Reviewers (sometimes) need to review papers “for their jobs”.

I watched a seminar on peer review yesterday where an editor for an Elsevier journal explicitly stated that Elsevier collect data on you as a peer reviewer (number of accepted/rejected, lag time etc), and use this to evaluate you for potential editorial roles. So I would remove the word 'sometimes' from this sentence :)

Do we begin with limiting pledges to psychology/behavioural science?

Great question. We're also considering this in the Registered Reports campaign thread (#8). I should preface by saying that the eventual plan is for the platform to classify people automatically (using ORCID profiles) and display statistics for each field separately, but we need a developer to make this happen so for now we're stuck with simple metrics that just show the total number of pledges.
Pros of limiting pledges to psychology:

we can clearly articulate which journals are 'allowed' vs not (as you have above) -- doing this for all fields would be a nightmare
rates of dissatisfaction with peer review are highest in psych, so should get relatively high adoption
people can self-identify as psychology researchers before pledging
it actually solves the collective action problem, which operates at the field level (i.e. if pledges activate and you're the only psych researcher in the cohort, you're effectively acting alone!)

Cons:

gets less people involved in the movement
cannot 'test the waters' in other fields and find out which ones would have the most traction

So at this stage I think to limit to psychology, and we can host extra campaigns for other fields down the track.

@CooperSmout Thanks for the comments!
One thing:

Reviewers (sometimes) need to review papers “for their jobs”.

I watched a seminar on peer review yesterday where an editor for an Elsevier journal explicitly stated that Elsevier collect data on you as a peer reviewer (number of accepted/rejected, lag time etc), and use this to evaluate you for potential editorial roles. So I would remove the word 'sometimes' from this sentence :)

What I meant was that I am not aware that reviewing is necessary for one's job as a grad student/postdoc/professor (or even in non-academic jobs). I have never had any sort of evaluation or requirement that I engage with unpaid reviewing work and I don't know of others who have that requirement. Becoming an editor can benefit promotion but it is not required.
I agree, though, limiting to psych is better for the reasons you mentioned.

I am not aware that reviewing is necessary for one's job as a grad student/postdoc/professor

Very good point, it's more of an implicit expectation than an explicit one, which should help us in getting pledges.

How long should the pledge stage operate? If we don’t receive enough pledges within a certain period of time, what do we do?

Good question. We could either take the campaign down, or consult with the community of pledgers to see if they want to extend the deadline (suggested by @samgrobson in the Registered Reports thread #8)?

Is 100 a reasonable number to begin the boycott?

Sure... I guess :) This is all new ground for the project, so really not sure. Personally I'd really like to see a short-term win for the project (i.e. reach threshold), so that we can generate some publicity and set the stage for bigger campaigns in the future (e.g. same campaign but 10x person threshold), which would suggest a small target. But then, if we go too small it might be seen as having little-to-no effect and fail to give some people the assurance they need to sign. 100 seems like a reasonable target for now (and has a nice ring to it), but let's leave it open to revision later when we have a better idea of community sentiment. On a related note, I think it would help each campaign to have some number of people committed to signing prior to it going live, e.g. 10% of the proposed target. So perhaps we could see how many people engage with the idea prior to posting, and use this to gauge what target we should set.
Some additional thoughts:

Should we stipulate that pledgers need to have completed a review in the past, to ensure that we're tapping into the actual reviewer pool? Otherwise our ranks may be filled with people who aren't likely to review in the future.

It would be good if there were some way to monitor compliance, so we can learn about success/failure of the campaign. Not sure if this is a good idea, but maybe we could ask pledgers to forward any rejection emails they send, so we can keep a tally?

Where to review instead?

PLoS One is another one to add (not-for-profit). I can't think if there's any other journals in the PLoS range that publish psych articles.

On a related note, I think it would help each campaign to have some number of people committed to signing prior to it going live, e.g. 10% of the proposed target. So perhaps we could see how many people engage with the idea prior to posting, and use this to gauge what target we should set.

Right- good point.

PLoS One is another one to add (not-for-profit). Not sure if there's any other journals in the PLoS range that publish psych articles.

We should definitely add PLOS to the list (I mentioned it on Twitter but forgot about it here).

Some additional thoughts:

Should we stipulate that pledgers need to have completed a review in the past, to ensure that we're tapping into the actual reviewer pool? Otherwise our ranks may be filled with people who aren't likely to review in the future.

These are good points. Maybe we could have people identify whether they have reviewed in the past somehow? This way people can still pledge even if they haven't reviewed before.

It would be good if there were some way to monitor compliance, so we can learn about success/failure of the campaign. Not sure if this is a good idea, but maybe we could ask pledgers to forward any rejection emails they send, so we can keep a tally?

I like the idea of forwarding emails, but a lot of times they are "confidential". Perhaps we can ask people to send something saying they got an invite, but honestly, I wouldn't have high hopes for a lot of emails though. It's an extra step thats easy to skip.

 Or are people free to return to their previous ways after some time period, e.g. 3 years?

I think permanent is the way to go.

And again, another tweet about charging companies for reviews. James' last post called for comments to indicate interest in receiving the template, and has 192 responses at the time of writing (will update later). This is handy, as we can use it as a rough starting point for how big the threshold should be. Just need to bear in mind that although the OP is from the field of psychology, not all of his followers will be, and also not all of those would be comfortable signing a pledge.

@jonmcphetres I edited your OP to include a couple more journals, as per this tweet.
It was also suggested that we should choose between having a whitelist or a blacklist, and let the other be defined by default, but not try to do both (as your OP currently tries to do). I suspect it will be easier to do a whitelist, given how many for-profit journals there are out there, and I also prefer it to a blacklist because it highlights the 'good' journals rather than the bad ones.

As a note, I have been using the reviewer response letter that @jonmcphetres drafted as a template to respond to selected reviewer requests. If anyone else is also doing this, it might be worthwhile to compile journal responses (or lack thereof) somewhere. Or perhaps not worth the time... Feel free to reach out.

If we pick this up again, it may be worth encouraging the peer-review of pre-prints (rather than for-profit journals) via Review Commons or Peer Community In


[BUG] No coins after update

windows 10
Wallet ver. SIT 1.1.3
Wallet status: Synced
Upgrade from 1.0.X
.sit was deleted before upgrade

The mainnet had restarted.


Convert images upon ingest

As a rival solution to #118, this branch explores the viability of converting large images upon ingest to a format supported by the GDALFileTileSource class (so that we can utilize vsicurl and avoid downloading the whole file)
I was able to use large-image-converter successfully, but when I do so, we lose some information from the metadata endpoint. Without conversion and using OMETiffFileTileSource, we get metadata like this, which includes channelMap:
{
  "levels": 4,
  "size_x": 5001,
  "size_y": 5001,
  "tile_size": 1024,
  "additional_metadata": {
    "levels": 4,
    "sizeX": 5001,
    "sizeY": 5001,
    "tileWidth": 1024,
    "tileHeight": 1024,
    "magnification": 19.912385503783355,
    "mm_x": 0.0005022,
    "mm_y": 0.0005022,
    "frames": [
      {
        "LightPath": {},
        "ID": "Channel:0:0",
        "Name": "NUCLEI",
        "SamplesPerPixel": "1",
        "IndexC": 0,
        "Frame": 0,
        "Index": 0,
        "Channel": "NUCLEI"
      },
      ...
    ],
    "IndexRange": {
      "IndexC": 12
    },
    "IndexStride": {
      "IndexC": 1
    },
    "channels": [
      "NUCLEI",
      "CD4",
      "CD3",
      "PD1",
      "KI67",
      "CD8",
      "EOMES",
      "GRZB",
      "IDO",
      "TBET",
      "CD68",
      "CD45"
    ],
    "channelmap": {
      "NUCLEI": 0,
      "CD4": 1,
      "CD3": 2,
      "PD1": 3,
      "KI67": 4,
      "CD8": 5,
      "EOMES": 6,
      "GRZB": 7,
      "IDO": 8,
      "TBET": 9,
      "CD68": 10,
      "CD45": 11
    }
  }
}

When I do convert and use the same tile source code, we get metadata like this:
{
  "levels": 6,
  "size_x": 5001,
  "size_y": 5001,
  "tile_size": 256,
  "additional_metadata": {
    "levels": 6,
    "sizeX": 5001,
    "sizeY": 5001,
    "tileWidth": 256,
    "tileHeight": 256,
    "magnification": null,
    "mm_x": null,
    "mm_y": null,
    "frames": [
      {
        "Frame": 0,
        "Index": 0
      },
      {
        "Frame": 1,
        "Index": 0
      },
      ...
      {
        "Frame": 11,
        "Index": 0
      }
    ]
  }
}

Unless there are configurable options to the convert function that will allow us to maintain this important metadata, this is the less viable contender.

For completeness, did you run a timing test with this solution (as you did for fuse mounting)?

For completeness, did you run a timing test with this solution (as you did for fuse mounting)?

No, not yet, but I'll do that for this solution and the local storage solution.


Checked with LinuxMint-17.2. and added support

The devstack works fine with destro : LinuxMint-17.2.
So updated the destro check line and added LinuxMint-17.2.
if [[ ! ${DISTRO} =~ (trusty|vivid|wily|7.0|wheezy|sid|testing|jessie|f21|f22|f23|rhel7|LinuxMint-17.2.) ]]; then

Otherwise it gives the below error for LinuxMint-17.2.:
` echo "WARNING: this script has not been tested on LinuxMint-17.2."`
`die 198 "If you wish to run this script anyway run with FORCE=yes"`

Thank you for contributing to openstack-dev/devstack!
openstack-dev/devstack uses Gerrit for code review.
Please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.