Technology Bonuses WIP

Work in progress on Technolgy page - part II not mentioned to finish te PR

extended tooltip for technolgy, not sure if put there also unlocked recipes, now only units count and ingredients
added two lists to technology page for unlocked items and unlocked fluids
[Experimental] added list with technology bonuses, like braking force, ammo damage, since the bonuses are not prototype based, it is not simple to get needed info to display correct all possible bonuses from base game, not mentioning possible new bonuses from mods like QoL research (I included it to PR just to show you if you are interested in it, but as i see it now, it would cost too much work with quite small benefit to the mod, and it should be removed)

Thanks for your hard work! I do like the bonuses and you implemented them well, but I don't think they're really in-scope for a Recipe Book. Additionally, we can't use the actual bonus icons, so I agree that it should be removed.
The items and fluids and tooltip are great though! Thank you. Just one small change: could you move the item and fluid lists up above the prerequisites list? Perhaps put them in alphabetical order (fluid, item recipe).

I have removed all the Bonus related code and reordered lists on technology page.
Also refactored formatter and extracted tooltip formatters into separate files (hope it is not too cheeky from me)

Thanks, I'll go ahead and merge it and do some other formatter cleanup as well.


changing font size / buttons slider bugs

Using the sliders for changing font size / buttons size sometimes moves the song list slider.
I also noticed that using changing font size / buttons size sliders often crashes the app.

When it crashes the app, does it just close or does an assertion popup appear?
I assume the first, but just to be sure.

Alright I found a crash when pressing the font-path button twice while there was no settings file on application start.
I will update the last release with the fix.
But I could not replicate a crash when resizing the font.


Cherry pick HBASE-24713 RS startup with FSHLog throws NPE after HBASE-21751

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
2m  0s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m 18s
branch-2.2 passed

+1 :green_heart:
compile
0m 58s
branch-2.2 passed

+1 :green_heart:
checkstyle
1m 19s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m  2s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 38s
branch-2.2 passed

+0 :ok:
spotbugs
3m 24s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 23s
branch-2.2 passed

_ Patch Compile Tests _

-1 :x:
mvninstall
2m 24s
root in the patch failed.

-1 :x:
compile
0m 38s
hbase-server in the patch failed.

-1 :x:
javac
0m 38s
hbase-server in the patch failed.

+1 :green_heart:
checkstyle
1m 15s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

-1 :x:
shadedjars
3m  1s
patch has 16 errors when building our shaded downstream artifacts.

-1 :x:
hadoopcheck
1m 47s
The patch causes 16 errors with Hadoop v2.8.5.

-1 :x:
hadoopcheck
3m 40s
The patch causes 16 errors with Hadoop v2.9.2.

-1 :x:
hadoopcheck
5m 31s
The patch causes 16 errors with Hadoop v2.10.0.

-1 :x:
hadoopcheck
7m 27s
The patch causes 16 errors with Hadoop v3.1.2.

-1 :x:
hadoopcheck
9m 24s
The patch causes 16 errors with Hadoop v3.2.1.

+1 :green_heart:
javadoc
0m 32s
the patch passed

-1 :x:
findbugs
0m 39s
hbase-server in the patch failed.

_ Other Tests _

-1 :x:
unit
0m 40s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
0m 13s
The patch does not generate ASF License warnings.

37m 47s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2134

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux fcc5d5c17963 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-2134/out/precommit/personality/provided.sh

git revision
branch-2.2 / 8dec49abb3

Default Java
1.8.0_181

mvninstall
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-mvninstall-root.txt

compile
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-compile-hbase-server.txt

javac
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-compile-hbase-server.txt

shadedjars
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-shadedjars.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-javac-2.8.5.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-javac-2.9.2.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-javac-2.10.0.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-javac-3.1.2.txt

hadoopcheck
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-javac-3.2.1.txt

findbugs
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-findbugs-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/testReport/

Max. process+thread count
96 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m 40s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
5m 52s
branch-2.2 passed

+1 :green_heart:
compile
1m  1s
branch-2.2 passed

+1 :green_heart:
checkstyle
1m 36s
branch-2.2 passed

+1 :green_heart:
shadedjars
4m 41s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 39s
branch-2.2 passed

+0 :ok:
spotbugs
4m  0s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 56s
branch-2.2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
6m 15s
the patch passed

+1 :green_heart:
compile
1m 19s
the patch passed

+1 :green_heart:
javac
1m 19s
the patch passed

+1 :green_heart:
checkstyle
1m 55s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
5m 27s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
32m 59s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 46s
the patch passed

+1 :green_heart:
findbugs
4m 28s
the patch passed

_ Other Tests _

-1 :x:
unit
330m 46s
hbase-server in the patch failed.

+1 :green_heart:
asflicense
0m 34s
The patch does not generate ASF License warnings.

414m 52s

Reason
Tests

Failed junit tests
hadoop.hbase.client.TestSnapshotTemporaryDirectory

hadoop.hbase.master.TestAssignmentManagerMetrics

hadoop.hbase.client.TestFromClientSide3

hadoop.hbase.client.TestSnapshotDFSTemporaryDirectory

hadoop.hbase.client.TestAdmin1

hadoop.hbase.client.TestSnapshotTemporaryDirectoryWithRegionReplicas

hadoop.hbase.replication.multiwal.TestReplicationSyncUpToolWithMultipleAsyncWAL

Subsystem
Report/Notes

Docker
Client=19.03.9 Server=19.03.9 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2134

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 92e9b5cb441b 4.15.0-101-generic #102-Ubuntu SMP Mon May 11 10:07:26 UTC 2020 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-2134/out/precommit/personality/provided.sh

git revision
branch-2.2 / 8dec49abb3

Default Java
1.8.0_181

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/2/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/2/testReport/

Max. process+thread count
4242 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
0m 43s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-0 :warning:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ branch-2.2 Compile Tests _

+1 :green_heart:
mvninstall
6m 42s
branch-2.2 passed

+1 :green_heart:
compile
1m 15s
branch-2.2 passed

+1 :green_heart:
checkstyle
1m 48s
branch-2.2 passed

+1 :green_heart:
shadedjars
5m 11s
branch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
javadoc
0m 43s
branch-2.2 passed

+0 :ok:
spotbugs
4m  2s
Used deprecated FindBugs config; considering switching to SpotBugs.

+1 :green_heart:
findbugs
3m 59s
branch-2.2 passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
6m 42s
the patch passed

+1 :green_heart:
compile
1m 17s
the patch passed

+1 :green_heart:
javac
1m 17s
the patch passed

+1 :green_heart:
checkstyle
1m 46s
the patch passed

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
shadedjars
5m 34s
patch has no errors when building our shaded downstream artifacts.

+1 :green_heart:
hadoopcheck
30m 57s
Patch does not cause any errors with Hadoop 2.8.5 2.9.2 2.10.0 or 3.1.2 3.2.1.

+1 :green_heart:
javadoc
0m 35s
the patch passed

+1 :green_heart:
findbugs
3m 19s
the patch passed

_ Other Tests _

+1 :green_heart:
unit
170m 58s
hbase-server in the patch passed.

+1 :green_heart:
asflicense
0m 35s
The patch does not generate ASF License warnings.

248m 37s

Subsystem
Report/Notes

Docker
Client=19.03.12 Server=19.03.12 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/3/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/2134

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux dbd61907d3f8 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/Base-PreCommit-GitHub-PR_PR-2134/out/precommit/personality/provided.sh

git revision
branch-2.2 / 8dec49abb3

Default Java
1.8.0_181

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/3/testReport/

Max. process+thread count
4745 (vs. ulimit of 10000)

modules
C: hbase-server U: hbase-server

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-2134/3/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.11.1 https://yetus.apache.org

This message was automatically generated.

please make sure commit messages start their subject with the jira key


docs: fixes import mistake in README

SafeAreaView is exported as default Class , but in example in README it is imported in wrong way like
import {SafeAreView} from 'react-native-safe-area-view'

instead of
import SafeAreView from 'react-native-safe-area-view'

Please merge this PR; I wasted ages today trying to get this to work with the curly braces

merged elsewhere but this library is deprecated now 07011a2 - use react-native-safe-area-context instead :)

merged elsewhere but this library is deprecated now 07011a2 - use react-native-safe-area-context instead :)


Update container image tags to use an appropriate major.minor version rather than latest.

We shouldn't always use latest as the tag as this could expose us to compatability issues. We also don't want to pin to a particular sha, that way we can get patches (including security patches).

Closing in favor of #1997


How to store catalogue issues

issues are tight to verbatim records which an assembled cataligue strictly does not have. Either we create empty dummy v records to keep issues or we refactor issues to be tight to the various entities directly which is very invasive.
assembly dummy v records could maybe also be used to track provenance better. e g links to source ids

there is a new VerbatimSource entity now that stores issues and holds the source id for projects & releases


[RFC] Support a ecma script version declaration in package.json

Do you want to request a feature or report a bug?
feature
What is the current behavior?
The adoption of ES2015 is growing. Node supports most of it natively and evergreen browsers can handle most of it. And it's going even further with Node.js natively supporting features from ES2017.
But we still need to transpile things to ES5 for some older but still relevant browsers. And even in evergreen browsers with full ES2017 support you may need to transpile some ES2018 code supported by Node if packages adopt it before 100% of evergreen browsers support it (e.g. native object rest/spread properties).
This is relevant to WebPack because it means in the WebPack ecosystem we have to choose one of an undesirable set of bad options:

Don't transpile anything in node_modules – More packages targeted at only supported releases of Node.js will start using ES6 code and you'll eventually install one that breaks websites. We will also see some smaller parts of even the client ecosystem (Polymer, subsets of React) shipping ES6 code in packages.
Transpile all of node_modules with babel-loader - A huge portion of your deps are already pre-transpiled to ES5, especially the packages made for client side use instead of Node.js use. Parsing all of these will be a lot of pointless work and slow WebPack down.
Manually exempt certain packages from the exclusion and transpile them. This is a list that will grow and grow, and it should not be up to the package user to identify which packages they are using need transpilation.

On top of this, a growing portion of packages offer multiple variants of the code within the same package. e.g. A src/ folder with ES6 code and a lib/ folder with ES5 code, whether you need to transpile will depend on how you import, it will be different between users. So old suggestions like extending engines to allow {"engines": {"ecma": ">= 6"}}.
Note that this is a separate topic from modules. WebPack supports ES6 modules with "module", but the code inside them is otherwise expected to be transpiled to whatever version of ES the package owner expects you to use.
What is the expected behavior?
The WebPack and Rollup ecosystem seems to have had some success with getting people to adopt "browser", "module", "sideEffects". I think it's reasonable we could get a large enough portion of the ecosystem to adopt a ecmascript version declaration in package metadata. We will still have to do 3. occasionally for uncooperative or absent package maintainers. But at least this will make it necessary to do this manual handling less often.
I have a proposal for an "ecma": {"glob": version} field. WebPack will only have two simple responsibilities here. One would be to expose the version number for a file to loaders, so loaders like babel-loader can have the option of passing this to presets that may decide to skip unnecessary transforms. And second to provide this to include and exclude conditional functions, so we can opt-in and write very simple loader rules that will apply babel-loader to node_modules but only on files declared with certain ecmascript versions.
If people like this idea, I'll try and write up a spec repo like what the browser field in package.json had in order to discuss this further.

I'll save details and discussion about the exact detail for a spec repo. Right now I want to know if there is a willingness within the WebPack community to implement support for something like it and promote it's usage in the WebPack documentation like module and sideEffects.

I've written up a spec for a proposed ecma field in package.json:
https://github.com/dantman/package-ecma-version-field-spec

This needs someone to review it and make a decision.

I still would like to see this happen. It just needs a maintainer to look at it and provide feedback.

It is proposal officially supported?

@evilebottnawi No, what support are you expecting? This proposal does not have any effect inside of Node.js itself, only bundlers. So "official" support is up to WebPack, Rollup, etc... maintainers accepting it.

@dantman so PR welcome with tests. In babel people how write RFC implement PoC before dicussion


tf.contrib.layers.Conv2D and MaxPool2D in tf.keras.layers

I am trying to convert the following lines of code to TensorFlow 2.0. These are written in tf.contrib.layers and now I need to put them in tf.keras.layers.
net1_h = layers.conv2d(input, 32, 3, stride=1, scope="Enc_conv_1")
net2 = layers.max_pool2d(input, kernel_size=2, stride=2, scope="Enc_maxpool_1")

The documentation for tf.keras.layers.Conv2D under TF2 states that input is not listed for Conv2D and MaxPool2D does not have input or kernel_size.
Any suggestions?

@teenazral
Please refer to this migration link for the mentioned issue, you may try "pip --forceinstall tensorflow==1.15", also have you imported conv2f and other parameters with tf else you could run into error, please share error log if any and stand alone code if you face any errors.


[FEAT] better support for callout

Is your feature request related to a problem? Please describe.
Yes, when I use spaced repetition with a callout, I get in trouble. If I use single-line syntax in a callout (in a second level list), latex will not render correctly. Then I think maybe I can let the whole callout to be a card with a multi-line syntax, but I still fail.
Describe the solution you'd like
I think make a whole callout to be a flashcard will be a good idea.
Additional context
Some other plugin's function will not render correctly, like obsidian-tikzjax. Yes I'm using spaced repetition to study my mathematics note 😁! Thanks for the efforts of the developers.

try this snippet
`#sr-easy-btn {
background-color: #344835a8;
}
#sr-hard-btn, #sr-good-btn, #sr-easy-btn {
height: 48px;
margin: auto;
color: #8f8d8d;
}
#sr-show-answer {
height: 48px;
line-height: 48px;
width: 96%;
text-align: center;
position: absolute;
bottom: 0;
cursor: pointer;
background-color: #23282f;
color: #aeafb1;
border-radius: 4px;
user-select: text;
}
#sr-good-btn {
background-color: #2b3a46;
}
#sr-hard-btn {
background-color: #402e2d;
}
.modal-content.sr-modal-content {
position: unset !important;
}
.sr-link {
float: unset !important;
}
#sr-flashcard-view {
padding-right: 10px;

}`

Thanks for your help!

Hi @Rsssstt
I'm wondering if the help provided by @monstertank solves the problem?
If not, please attach a markdown file that demonstrates the problem, as well as an annotated screenshot of what currently happens and what you prefer.
Cheers
Ronny


Add missing torch.no_grad() to streaming inference

Codecov Report

Merging #300 (a828be6) into master (02bb7d6) will increase coverage by 0.00%.
The diff coverage is 69.04%.

@@           Coverage Diff           @@
##           master     #300   +/-   ##
=======================================
  Coverage   68.33%   68.34%
=======================================
  Files          96       96
  Lines       10727    10727
=======================================
+ Hits         7330     7331    +1
+ Misses       3397     3396    -1

Impacted Files
Coverage Δ

neural_sp/models/seq2seq/speech2text.py
71.61% <69.04%> (+0.22%)
:arrow_up:

Continue to review full report at Codecov.

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


Fix parameter name in InformationPane

pn.pane.Markdown() called from within InformationPane currently throws an error because the argument style should be styles

Just to add a piece of information. This is a dependency issue.
panel==1.4.2 raises the reported issue and the proposed solution seems to be correct.
However, downgrading to panel==1.3.8 may also fix the issue while this MR is not merged.


[Fix] Fix the bug when do the 2d label mapping

Move the parsing logic for 2d annotations from LoadAnnotations3D to Det3DDataset to to do the label mapping for 2d labels

Has been fixed by @ZCMax


[Cycle times] Fractional end days not always properly accounted for

Put this code at the bottom of TrelloReports:
    function doTest(a, b) {
        console.log("bizDays", a, "-", b, "=", calcBizDays(a, b));
    }
    doTest(new Date(2014, 5, 5, 12), new Date(2014, 5, 6, 12)); // expected 1 - correct
    doTest(new Date(2014, 5, 6, 12), new Date(2014, 5, 7, 12)); // expected 0.5 - got 1
    doTest(new Date(2014, 5, 7, 12), new Date(2014, 5, 8, 12)); // expected 0 - got 1
    doTest(new Date(2014, 5, 5, 12), new Date(2014, 5, 6, 18)); // expected 1.25 - correct
    doTest(new Date(2014, 5, 6, 12), new Date(2014, 5, 7, 18)); // expected 0.5 - correct
    doTest(new Date(2014, 5, 7, 12), new Date(2014, 5, 8, 18)); // expected 0 - got 0.75
    doTest(new Date(2014, 5, 3, 18), new Date(2014, 5, 4, 12)); // expected 0.75 - correct
    doTest(new Date(2014, 5, 6, 18), new Date(2014, 5, 7, 12)); // expected 0.25 - 0.75

@redmunds I think this is due to the issues I mentioned with the loop stopping condition in calcBizDays().

@peterflynn @pthiess Since we're now using Waffle this issue is obsolete. Closing.


docs about migrations, version by version

can be written based on braking changes from CHANGELOG.md.

v11.6.0 has been released and contains a fix for the issue. Feel free to reopen the issue or to submit a new one if you meet any problems.


Get resolved color for current scheme in javascript land

Motivation:
Some features of rn don't currently allow to use platform color: for example tintColor for ActionSheetIOS or interpolating colors for animations. For those use cases it would be nice to get the resolved color value for the current scheme (Appearance.getColorScheme()).
Example:
// platform-colors.config.js
module.exports = {
  "colors": {
    "background": {
      "light": "#ffffff",
      "dark": "#000000"
    },
    "accent": "pink"
  },
}

// somewhereelse.js
resolveColor("background")
resolveColor(Colors.background)

In this case resolveColor would query Appearance.getColorScheme() for the appropriate scheme and then return the actual color value.
Of course, this could already be done by importing the config and selecting from colors but it would be nice to have a importable function and type checked color names for this.

This would be a native module then? Do you think it makes sense for this functionality to be in react-native core or should it be a part of this library? (I know your feelings about contributing to core...)

If we exclude the high contrast colors for now, this can already be done in js-land by just using Appearance.getColorScheme(). The way that I have currently set this up:
interface DynamicColor {
  dark: string;
  light: string;
}

export const dynamicColors = {
  background: { dark: "rgb(18,18,18)", light: "rgb(255,255,255)" },
}

export function resolveDynamicColor(color: DynamicColor): string {
  const scheme = Appearance.getColorScheme();
  return scheme === "dark" ? color.dark : color.light;
}

then it can be resolved by using:
resolveDynamicColor(dynamicColors.background);

Regarding high contrast, this could / should probably be added to Appearance in the core and can then be made available here.

Well, problem is that you then wouldn't have a single source of truth. It's quite possible for JS and native colors to get out of sync, so I think I would prefer a native module in that case.

Isn't the single source of truth platform-colors.config.js? The rest is just generated code.

It's the source of truth when generating the files, but in runtime it's the generated file. Also a dynamic color might be manually maintained, or provided by the OS itself too

Closing as this is resolved in 0.2.0.


The hooks package is not working properly when consumed

The functionality of the hooks package is working fine when testing from inside the storybook for it, but it's not working when trying to import the build output of it. (inside the components package storybook for example)

Fixed via #40


SparkSQL support

We are using Azkaban to manage our jobs, which mostly running Hive SQLs. Azkaban is great and very helpful.
And it would be better to support SparkSQL. As SparkSQL is replacing Hive in many places. Currently it only seems to support summiting Spark jar jobs.

This is a great idea. Would you like to submit PR?

As we plan the same thing, @ameyamk what do you recommend to develop a such thing? (clone existing plugin etc..) I could give some help on it.


Revise source_id FGOALS-f3-H adding OMIP activity_id

Add an "OMIP" activity_participation entry for FGOALS-f3-H
@yongqiangyu
Fix #854

@yongqiangyu that update is now in place, please review CMIP6_source_id.html and let me know of any further tweaks required


Update jest and puppeteer

 Upgrade jest and puppeteer

Coverage remained the same at 100.0% when pulling 8843c5cd5e0b97da38ffc73fa8b9b041d59753fa on feature/puppeteer-jest-update into 920480560de46f6bc388586c7da953817b4fa3a3 on master.


Creating additional .traineddata files, (tessdata_best and tessdata_fast) gives couple of .traineddata files in each folder. Which one is best or which one is fast among them?

creating additional .traineddata files after training with make traineddata creates two folders tessdata_best and tessdata_fast. Each folder contains couple of .traineddata files. For example tessdata_best contains
foo0.06_614.traineddata
foo0.135_613.traineddata
foo0.185_613.traineddata
foo0.205_613.traineddata
foo0.258_612.traineddata
foo0.305_606.traineddata
foo0.331_599.traineddata
foo0.376_598.traineddata
foo0.429_598.traineddata
foo0.506_597.traineddata
foo0.532_590.traineddata
foo0.564_579.traineddata
foo0.589_579.traineddata
foo0.809_577.traineddata
foo0.868_576.traineddata
foo0.933_572.traineddata
foo10.782_321.traineddata
foo1.131_568.traineddata
foo1.239_562.traineddata
foo1.327_559.traineddata
foo13.853_307.traineddata
foo1.478_546.traineddata
foo15.155_261.traineddata
foo1.568_542.traineddata
foo16.427_243.traineddata
foo17.691_214.traineddata
foo1.919_532.traineddata
foo19.303_196.traineddata
foo2.05_528.traineddata
foo21.782_169.traineddata
foo22.783_132.traineddata
foo2.309_525.traineddata
foo2.644_520.traineddata
foo26.6_96.traineddata
foo2.774_504.traineddata
foo3.079_500.traineddata
foo3.263_492.traineddata
foo3.647_472.traineddata
foo37.217_64.traineddata
foo4.435_465.traineddata
foo4.839_456.traineddata
foo5.058_444.traineddata
foo5.436_436.traineddata
foo6.333_428.traineddata
foo6.762_420.traineddata
foo7.235_407.traineddata
foo8.016_374.traineddata
foo9.484_365.traineddata
foo9.918_341.traineddata

Which one is the best among all of them?

The number after the model name indicates the CER achieved on the test data. In your case foo0.06_614.traineddata is the best model with CER=0.06 %.


LIMIT order placed instead or MARKET order

Hi, While I placed the orders through the 'place_order' method, I could see the orders placed as 'LIMIT' order instead of 'MARKET' order, even after mentioning that it should be a market order. PFB the screenshot shown below from the debugger which shows the finally constructed order object, there it is showing as 'MARKET'. However, when the order gets executed, it goes to 'LIMIT' as shown in the next screenshot.
Also check the 'Price' and 'Average price' values that I have highlighted. If it is placed as market order, then it should right away fill the available price. I am confused why some value is show in the 'Price' field even though I passed the price value as zero as you can see in the first screenshot. The weird part is, the instrument never came to that price or 42 in that candle. I verified it with the minute level candle. So from where this number is coming? Kindly help.
Finally, if you see the order update time or exchange time, the values are shown as 04:00:58. Whereas this order was executed morning at 09:30:58 am. I don't know whether this is related to API or SAS Online. But this is also an issue. Please note that the server timing and all other stuffs are set to proper Indian time zones. Thanks.

I checked with SAS Online for these issues and got it rectified. The 'Price' field value is due to their newly introduced 'Market Protection Range' of 20% for options. So they asked me to ignore the value shown in the 'Price' field. All Market orders will hereafter be executed as Limit orders and the timing is related to some time zone conflict which they resolved. Thanks.


The custom logo is loaded only in light mode

Describe the bug
custom logo only appeans on light mode removed cache and relogin multiple times.
Screenshots
public folder

Desktop (please complete the following information):

OS: Nobara39
Browser chrome

This issue is occurring for me as well. Although I have both logo_light.png and logo_dark.png in the public folder, only the light logo is changing in the frontend


"No such file or directory - pod" when using jenkins --- but "pod install" in command line works fine

Issue Description
No such file or directory - pod
Command executed
fastlane ent_build config:InHouse build_number:1297 output_dir:/Users/Shared/Jenkins/Home/jobs/Jenkinsfile/builds/1297/archive
Complete output when running fastlane, including the stack trace and command used

 [22:36:09]: fastlane detected a Gemfile in the current directory
[22:36:09]: however it seems like you don't use `bundle exec`
[22:36:09]: to launch fastlane faster, please use
[22:36:09]:
[22:36:09]: $ bundle exec fastlane ent_build config:InHouse build_number:1297 output_dir:/Users/Shared/Jenkins/Home/jobs/Jenkinsfile/builds/1297/archive
[22:36:09]:
[22:36:09]: Get started using a Gemfile for fastlane https://docs.fastlane.tools/getting-started/ios/setup/#use-a-gemfile
[22:36:10]: ------------------------------
[22:36:10]: --- Step: default_platform ---
[22:36:10]: ------------------------------
[22:36:10]: Driving the lane 'ios ent_build' 🚀
[22:36:10]: -----------------------
[22:36:10]: --- Step: cocoapods ---
[22:36:10]: -----------------------
[22:36:10]: $ pod install
+------------------+---------------+
|           Lane Context           |
+------------------+---------------+
| DEFAULT_PLATFORM | ios           |
| PLATFORM_NAME    | ios           |
| LANE_NAME        | ios ent_build |
+------------------+---------------+
[22:36:10]: No such file or directory - pod
+------+------------------+-------------+
|           fastlane summary            |
+------+------------------+-------------+
| Step | Action           | Time (in s) |
+------+------------------+-------------+
| 1    | default_platform | 0           |
| 💥   | cocoapods        | 0           |
+------+------------------+-------------+
[22:36:10]: fastlane finished with errors
[22:36:10]: Error accessing file, this might be due to fastlane's directory handling
[22:36:10]: Check out https://docs.fastlane.tools/advanced/#directory-behavior for more details
#######################################################################
fastlane 2.121.1 is available.
You should use the latest version.
Please update using sudo gem install fastlane.
#######################################################################
2.121.1 Improvements

[deliver] screenshots are binary data, write as such (#14655) via Jan Piotrowski
[action] app_store_build_number (and latest_testflight_build_number) don't raise error if using :initial_build_number (#14654) via Josh Holtz
[spaceship] Authentication documentation (#14524) via Jan Piotrowski
[deliver] fix ipad 3rd gen naming to prevent future collisions (#14653) via Josh Holtz
[frameit] add missing documentation for title_min_height option (#14651) via Bruno Virlet
[pilot] fix typo in message (#14646) via Piet Jaspers

2.121.0 Improvements for deliver, spaceship, and actions

[action] allow modify_services to enable data_protection (#14571) via martinkasa
[deliver] apple tv privacy policy upload and download handling added (#14569) via aniketgaur
[deliver] iPad Pro (12.9-inch) (3rd generation) ambiguity resolution (#14576) via Viktoras Laukevičius
[spaceship] make Spaceship::Tunes::DisplayFamily main data source for screenshot information (#14574) via Liam Nichols
[action] cert: Prevent from crash when keychain_path param wasn't passed (#14620) via Dmitrii Celpan
[frameit] fix frameit percentage padding (#14596) via Christophe Wagner
[action] pod_lib_lint: Add support for use_module_headers and subspecs (#14599) via Raymond Hoagland
[action] app_store_build_number: Pass teamID when selecting itunes team (#14604) via Dmitrii Celpan
[spaceship] Include 'DES' cookie into FASTLANE_SESSION (#14301) (#14525) via Maksym Grebenets
[spaceship] Automate phone number selection for "request code via SMS" in 2FA with SPACESHIP_2FA_SMS_DEFAULT_PHONE_NUMBER env var (#14436) via Jan Piotrowski
[deliver] Test Deliver::AppScreenshot methods and fix uncovered bugs (#14588) via Liam Nichols
[action] Post line break characters as actual interpreted line break through slack integration (#14612) via Albert
[action] artifactory: Add a read timeout option (#14580) via Raymond Hoagland
[action] pod_lib_lint: Add new cocoapods 1.7 parameters of the lint command (#14579) via Martin Fiebig
[action] sonar: new optional param for branch name (#14611) via Husyn
[action] register_devices changed to actions/register_devices/ (#14582) via Morten Bøgh
[deliver] upload_screenshots_spec to test screenshot collection (#14533) via Liam Nichols
[deliver] Fix builds whose versions have components with leading zeros infinitely wait for submission (#14513) via Justin Hill

2.120.0 Fix pilot, fix build watcher, and other improvements

[spaceship] [spaceship] migrate "olympus" authentication endpoint to appstoreconnect api (#14509) via Stefan Natchev
[pilot + spaceship] fix pilot, build watcher, and beta groups to use new App Store Conneect API  (#14523) via Josh Holtz
[fastlane] add the ability to specify Step Name for all actions (#14423) via Adrien Becchis
[gym] fix provisioning profile detection for projects based on inherited xcconfigs (#14360) via José Miguel Brocal Gallego
[spaceship] Add app screenshot download endpoint to README.md (#14519) via Maksym Grebenets
[action] Continue git_commit action execution if there is nothing to commit (#14501) via Daniel Jankowski
[fastlane] fix syntax error changes introduced in ruby 2.6 (#14508) via Stefan Natchev
[fastlane] git: more responsible, Windows-compatible shellout (#14471) via Artem Sheremet
[snapshot] Make the sleep waiting for animations optional (#14498) via Xaver Lohmüller
[deliver] do not set ratings_resets to null if not specified. (#14490) via Carlos Fonseca
[scan] added env_name values for commonly used options (#14492) via Jacob Aleksynas
[action] add --set-upstream option to push_to_git_remote (#14496) via Guillermo García
[sign] fix sigh not using custom keychain path (#14462) via Josip Ćavar

To see all new releases, open https://github.com/fastlane/fastlane/releases
Please update using sudo gem install fastlane
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/open3.rb:199:in spawn': No such file or directory - pod (Errno::ENOENT) 	from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/open3.rb:199:in popen_run'
from /System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib/ruby/2.3.0/open3.rb:190:in popen2e' 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/helper/sh_helper.rb:54:in sh_control_output'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/helper/sh_helper.rb:12:in sh' 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/actions/cocoapods.rb:27:in run'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/runner.rb:253:in block (2 levels) in execute_action' 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/actions/actions_helper.rb:50:in execute_action'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/runner.rb:232:in block in execute_action' 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/runner.rb:227:in chdir'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/runner.rb:227:in execute_action' 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/runner.rb:157:in trigger_action_by_name'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/fast_file.rb:154:in method_missing' 	from Fastfile:76:in block (2 levels) in parsing_binding'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/lane.rb:33:in call' 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/runner.rb:49:in block in execute'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/runner.rb:45:in chdir' 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/runner.rb:45:in execute'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/lane_manager.rb:56:in cruise_lane' 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/command_line_handler.rb:36:in handle'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/commands_generator.rb:108:in block (2 levels) in run' 	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:178:in call'
from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/command.rb:153:in run' 	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/runner.rb:476:in run_active_command'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane_core/lib/fastlane_core/ui/fastlane_runner.rb:76:in run!' 	from /Library/Ruby/Gems/2.3.0/gems/commander-fastlane-4.4.6/lib/commander/delegates.rb:15:in run!'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/commands_generator.rb:333:in run' 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/commands_generator.rb:41:in start'
from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/fastlane/lib/fastlane/cli_tools_distributor.rb:113:in take_off' 	from /Library/Ruby/Gems/2.3.0/gems/fastlane-2.114.0/bin/fastlane:23:in <top (required)>'
from /usr/local/bin/fastlane:22:in load' 	from /usr/local/bin/fastlane:22:in '
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Deploy)
Stage "Deploy" skipped due to earlier failure(s)
[Pipeline] }
[Pipeline] // stage
[Pipeline] stage
[Pipeline] { (Declarative: Post Actions)
[Pipeline] echo
One way or another, I have finished
[Pipeline] echo
I failed :(
[Pipeline] sh
[Docs_App_Jenkinsfile] Running shell script
Error when executing failure post condition:
hudson.AbortException: script returned exit code 1
at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$Execution.exited(DurableTaskStep.java:512)
at org.jenkinsci.plugins.workflow.steps.durable_task.DurableTaskStep$HandlerImpl.exited(DurableTaskStep.java:593)
at org.jenkinsci.plugins.durabletask.FileMonitoringTask$Watcher.run(FileMonitoringTask.java:488)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$201(ScheduledThreadPoolExecutor.java:180)
at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:293)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

python /Users/Shared/Jenkins/Home/workspace/Jenkinsfile/../bin/lark-robot-push.py 2 InHouse
Traceback (most recent call last):
File "/Users/Shared/Jenkins/Home/workspace/Jenkinsfile/../bin/lark-robot-push.py", line 4, in
import requests
ImportError: No module named requests
[Pipeline] }
[Pipeline] // stage
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // withEnv
[Pipeline] }
[Pipeline] // node
[Pipeline] End of Pipeline
ERROR: script returned exit code 1
Finished: FAILURE

Environment

 🚫 fastlane environment 🚫
Stack

Key
Value

OS
10.14.4

Ruby
2.5.1

Bundler?
false

Git
git version 2.20.1 (Apple Git-117)

Installation Source
~/.rvm/gems/ruby-2.5.1/bin/fastlane

Host
Mac OS X 10.14.4 (18E226)

Ruby Lib Dir
~/.rvm/rubies/ruby-2.5.1/lib

OpenSSL Version
OpenSSL 1.1.1b  26 Feb 2019

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

Xcode Path
/Applications/Xcode.app/Contents/Developer/

Xcode Version
10.2

System Locale

Error

No Locale with UTF8 found 🚫

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
#
# For a list of all available plugins, check out
#
#     https://docs.fastlane.tools/plugins/available-plugins
#

# Uncomment the line if you want fastlane to automatically update itself
# update_fastlane

default_platform(:ios)

platform :ios do

  before_all do
  end

  desc "Docs App Build If Need"
  lane :build_upload_if_needed do |options|
    branch = options[:current_branch]
    build_if_needed(current_branch: branch, key_commit: "--pipeline")

    user_email = options[:user_email]

    # https://docs.fastlane.tools/actions/cocoapods/
    cocoapods(
      use_bundle_exec: false,
      podfile: "../Podfile",
      try_repo_update_on_error: true
    )

    gym(
      workspace: "Docs.xcworkspace",
      configuration: "Beta",
      export_method: "enterprise",
      scheme: "Docs",
      output_directory: "~/Desktop/docs_ipa",
      output_name: "Docs.ipa",
      clean: true
    )

    upload_to_ee(author_email: user_email, last_commit: last_git_commit[:message])
  end

  # https://docs.fastlane.tools/actions/gym/
  desc "Docs App Build And Upload"
  lane :build_upload do |options|
    user_email = options[:user_email]

    # https://docs.fastlane.tools/actions/cocoapods/
    cocoapods(
      use_bundle_exec: false,
      try_repo_update_on_error: true
    )

    gym(
      workspace: "Docs.xcworkspace",
      configuration: "Beta",
      export_method: "enterprise",
      scheme: "Docs",
      output_directory: "~/Desktop/docs_ipa",
      output_name: "Docs.ipa",
      clean: true
    )

    upload_to_ee(author_email: user_email, last_commit: last_git_commit[:message])
  end

  desc "Enterprise Build"
  lane :ent_build do |options|
    cocoapods(
      use_bundle_exec: false,
      try_repo_update_on_error: true
    )

    # begin
    #   xcodebuild(
    #     test: true,
    #     scheme: "Docs",
    #     workspace: "Docs.xcworkspace",
    #     destination: "platform=iOS Simulator,name=iPhone 8,OS=12.0"
    #   )
    # rescue => ex
    #   UI.error("docs test fail for: #{ex}")
    # end

    config = options[:config]
    build_number = options[:build_number]
    output_dir = options[:output_dir]

    increment_build_number(
      build_number: build_number,
      xcodeproj: "Docs.xcodeproj"
    )

    gym(
      workspace: "Docs.xcworkspace",
      configuration: config,
      export_method: "enterprise",
      scheme: "Docs",
      output_directory: output_dir,
      output_name: "Docs.ipa",
      clean: true
    )
  end

  desc "Development Build"
  lane :dev_build do |options|
    cocoapods(
      use_bundle_exec: false,
      try_repo_update_on_error: true
    )

    config = options[:config]
    build_number = options[:build_number]
    output_dir = options[:output_dir]

    increment_build_number(
      build_number: build_number,
      xcodeproj: "Docs.xcodeproj"
    )

    gym(
      workspace: "Docs.xcworkspace",
      configuration: config,
      export_method: "development",
      scheme: "Docs",
      output_directory: output_dir,
      output_name: "Docs.ipa",
      clean: true
    )
  end

  # desc "仅供本地测试，不作远程服务"
  # lane :just_for_local_test do |options|
  #   upload_to_ee(author_email<EMAIL_ADDRESS>last_commit: last_git_commit[:message])
  # end
end

`./fastlane/Appfile`
# app_identifier("[[APP_IDENTIFIER]]") # The bundle identifier of your app
# apple_id("[[APPLE_ID]]") # Your Apple email address

# For more information about the Appfile, see:
#     https://docs.fastlane.tools/advanced/#appfile

fastlane gems

Gem
Version
Update-Status

fastlane
2.121.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.2.0

executable-hooks
1.6.0

bundler-unload
1.0.2

rubygems-bundler
1.4.5

bundler
1.17.3

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.0

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.8.2

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.5.0

terminal-table
1.8.0

plist
3.5.0

public_suffix
2.0.5

addressable
2.6.0

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.6.5

tty-cursor
0.6.1

tty-spinner
0.9.0

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

faraday
0.15.4

unf
0.1.4

domain_name
0.5.20180417

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.5

gh_inspector
1.1.3

mini_magick
4.5.1

multi_json
1.13.1

multi_xml
0.6.0

rubyzip
1.2.2

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.7.2

faraday_middleware
0.13.1

naturally
2.2.0

simctl
1.6.5

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.2

mime-types-data
3.2019.0331

mime-types
3.2.2

jwt
2.1.0

signet
0.11.0

memoist
0.16.0

os
1.0.0

googleauth
0.6.7

httpclient
2.8.3

google-api-client
0.23.9

google-cloud-env
1.0.5

google-cloud-core
1.3.0

digest-crc
0.4.1

google-cloud-storage
1.16.0

emoji_regex
1.0.1

excon
0.64.0

unf_ext
<IP_ADDRESS>

json
2.2.0

openssl
2.1.0

date
1.0.0

fileutils
1.0.2

mini_portile2
2.3.0

nokogiri
1.8.5

ipaddr
1.2.0

psych
3.1.0

generated on: 2019-04-30

btw, workaround in issue#4247 does not help

Could you update your fastlane to the most recent version please?
Can you run your lane with --verbose added at the end and post its output? Maybe that tells us what is happening during pod install.

I solved this by not letting fastlane do the pod stuff.


Test pass only if singleRun is false

I'm experiencing an issue where this test pass only if singleRun is false.
When I set singleRun to true the test fails because template.html() is empty.
I've tried to add timeouts or to fire more digests but it always fails.
It seems that the template of my-app-language-switcher (it uses templateUrl) is not correctly loaded and the directive is not compiled if singleRun is true: I've tried to console.log the document.body after the digest and the directive is not compiled.
-- karma conf file
ngHtml2JsPreprocessor: {
  moduleName: 'templates',
  stripPrefix: 'app/',
},
preprocessors: {
  'test/unit/**/*.js': ['babel'],
  'app/views/directive/*.html': ['ng-html2js']
},
files: [
  'test/res/inject-raven.js',
  'app_babel/scripts/**/*.js',
  'app/views/directive/*.html',
  'test/unit/**/*.js'
]

-- test
describe('Language switcher suite', () => {
  let $compile, $scope;

  beforeEach(angular.mock.module('myApp'));
  beforeEach(angular.mock.module('templates'));

  beforeEach(inject((_$compile_, _$rootScope_) => {
    $compile = _$compile_;
    $scope = _$rootScope_.$new();
  }));

  it('Should show the language switcher', () => {
    // pending();
    const template = $compile('<my-app-language-switcher />')($scope);
    document.body.appendChild(template[0]);
    $scope.$digest();
    expect(template.html()).toContain('flag-icon-gb');
  });
});

It works if I use singleRun true and Chrome as the browser.
The test fails if it runs on phantomjs.

+1 i am facing this problem too not just for chrome but also phantom js
If single run is true  at EventEmitter. (AppData\Roaming\npm\node_modules\npm\lib\utils\lifecycle.js:279:16)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at EventEmitter.emit (events.js:192:7)
14 verbose stack     at ChildProcess. (C:\Users\mohammed.uddin\AppData\Roaming\npm\node_modules\npm\lib\utils\spawn.js:40:14)
14 verbose stack     at emitTwo (events.js:106:13)
14 verbose stack     at ChildProcess.emit (events.js:192:7)
14 verbose stack     at maybeClose (internal/child_process.js:890:16)
14 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)


Hi everyone, I think there is an error in Keras documentation https://keras.io/models/sequential/. For compile method, for loss_weights parameter, near the end of description, it says "tensor" instead of "dictionary".

Please make sure that the boxes below are checked before you submit your issue. If your issue is an implementation question, please ask your question on StackOverflow or join the Keras Slack channel and ask there instead of filing a GitHub issue.
Thank you!

[ ] Check that you are up-to-date with the master branch of Keras. You can update with:
pip install git+git://github.com/keras-team/keras.git --upgrade --no-deps

[ ] If running on TensorFlow, check that you are up-to-date with the latest version. The installation instructions can be found here.

[ ] If running on Theano, check that you are up-to-date with the master branch of Theano. You can update with:
pip install git+git://github.com/Theano/Theano.git --upgrade --no-deps

[ ] Provide a link to a GitHub Gist of a Python script that can reproduce your issue (or just copy the script here if it is short).

Hi everyone, I think there is an error in Keras's documentation (https://keras.io/models/sequential/). For compile method, for loss_weights argument, near the end of description, it says "tensor" instead of "dictionary".


Update deps

xmlschema had a breaking change, so some refactoring was necessary.
Bandit flagged the solution of importing ElementTree from xml.etree as an issue, and defusedxml is supposed to be the answer.

There was a change in xmlschema from release 2.0.0 https://github.com/sissaschool/xmlschema/releases/tag/v2.0.0. In which they refactored, and removed some code, which we were previously importing.
Then Bandit was complaining that directly using the other solution I used, (which I don't remember exactly what it was, but likely xml.etree.ElementTree.parse), to process user data was unsafe, with the suggestion to instead use defusedxml https://bandit.readthedocs.io/en/latest/blacklists/blacklist_calls.html?highlight=defusedxml#b313-b320-xml

I'll try to remember to provide the full info with references in the PR description. Ah, the commit message had some more context as well.


update partner signup.

broken link for developer registration

Hi - are you MSFT? The original link seems to work?

I'm not MSTF. The link https://developer.microsoft.com/en-us/microsoft-store/register renders a blank page for me. Even opened in incognito mode.

I'm hoping it's a temporary glitch, as it works now..?


Corrupted the only option

ADD ISSUE DESCRIPTION HERE
Version: 1.78.0-puter-1.0.2
Commit: cf9a8c6eeec996ed45cf2128dd83d143871c6b39
User Agent: Mozilla/5.0 (Linux; Android 10; K) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Mobile Safari/537.36
Embedder: unknown
Extension version: 0.0.1

This will be better because it won't be forever ❤♾

/needsMoreInfo

Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelines. Please take the time to review these and update the issue.
Happy Coding!

Have u been watching me 2 ?

From: VSCode Triage Bot @.>
Sent: Sunday, 21 July 2024 4:56 am
To: microsoft/vscode @.>
Cc: Skandiakiwi13 @.>; Author @.>
Subject: Re: [microsoft/vscode] Corrupted the only option (Issue #222290)
Thanks for creating this issue! We figured it's missing some basic information or in some other way doesn't follow our issue reporting guidelineshttps://aka.ms/vscodeissuereporting. Please take the time to review these and update the issue.
Happy Coding!
—
Reply to this email directly, view it on GitHubhttps://github.com/microsoft/vscode/issues/222290#issuecomment-2241206027, or unsubscribehttps://github.com/notifications/unsubscribe-auth/BII4VTWILQEBDKHNQTN3CQTZNKJFJAVCNFSM6AAAAABLF763N6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDENBRGIYDMMBSG4.
You are receiving this because you authored the thread.Message ID: @.***>

Not too much to it really its only being manipulatively ironic

/spam


Metal: Improve reduce and softmax kernels

30-40% improvement to throughput for reduce, arg_reduce, and softmax.
Also adds contiguous impl for reduce and arg_reduce

Hi thanks for this work.
I couldn't run it, because this crashes on M3 (as in real crash, everything hangs and nothing responds.
My attempt:
cargo run --example phi --release  --features metal  -- --prompt "What is Deep Learning?" --sample-len 10  --model 1.5

Could you provide more insights into your bench, and what it actually gives out (ideally both the pure softmax op, I'm guessing 30/40% but it'd be nice to have ideas of the throughputs AND a real model use case scenario, where it's likely to be a slimmer increase but still).
Overall I find the code much less readable, with lots of spread macros/functions doing a different part of the work, but being tied together subtly, which is a recipe to create bugs imho.
For instance here, since it crashes the entire computer it's kind of hard to figure out where (especially in the macros).
#pragma unroll should be available I think if it's only about unrolling loops for instance.

haha no worries. Norwegians can be fairly direct as well ;)
And finding out it's broken is pretty gosh darn important hehe.
I actually found the code easier to read after introducing templates (nice to get rid of all the \s), but that's probably just because I wrote it.
I have some improvements coming in already which will 1. make it not broken and 2. improve readability.

Will continue work in #1819


got 500 error for  js of child theme

added this file in child theme
using Orchard.UI.Resources;
namespace Guang.BootstrapBase
{
public class ResourceManifest : IResourceManifestProvider
{
public void BuildManifests(ResourceManifestBuilder builder)
{
var manifest = builder.Add();                    manifest.DefineScript("myCustom").SetUrl("mycustom.js").SetDependencies("jQuery");
}
}
}
then
Script.Require("myCustom");
in a .cshtml file in child theme
got this:
Failed to load resource: the server responded with a status of 500 (Internal Server Error)

Got the same thing yesterday, and figured out why, so this one is easy. Open the project and change the target framework to 4.5.1.

my all projects have targeted to 4.5.1

also 500 for favicon.ico

Does your folder have a web.config with a StaticFile handler configured? Something like:
<?xml version="1.0" encoding="UTF-8"?>
<configuration>
  <system.webServer>
	<staticContent>
	  <clientCache cacheControlMode="UseMaxAge" cacheControlMaxAge="7.00:00:00" />
	</staticContent>

	<handlers accessPolicy="Script,Read">
	  <!--
	  iis7 - for any request to a file exists on disk, return it via native http module.
	  accessPolicy 'Script' is to allow for a managed 404 page.
	  -->
	  <add name="StaticFile" path="*" verb="*" modules="StaticFileModule" preCondition="integratedMode" resourceType="File" requireAccess="Read" />
	</handlers>
  </system.webServer>
</configuration>

just retested it, the same issue.
web.config is no problem

I've had the same problem trying to use Bootstrap theme in Orchard (all using the latest versions directly from github, so even more recent than orchard 1.10 and Bootstrap theme 3.3.5).
To find out the real error under the 500, in the Orchard web.config, comment out the line:
        <!-- Prevent IIS 7.0 from returning a custom 404/500 error page of its own. -->
        <!--<httpErrors existingResponse="PassThrough" />-->
Then you can see the real error in the browser by requesting one the individual files in folder Scripts, Content or Styles, for example:
http://localhost:30321/OrchardLocal/Themes/PJS.Bootstrap/Content/Swatches/journal_th.png
The error I get is:
HTTP Error 500.19 - Internal Server Error
The requested page cannot be accessed because the related configuration data for the page is invalid.
Config Error	   Cannot add duplicate collection entry of type 'add' with unique key attribute 'name' set to 'StaticFile'
Config File	   \\?\C:\.......\Orchard-1.10.x- 2440e68\src\Orchard.Web\Themes\PJS.Bootstrap\Content\web.config
<add name="StaticFile" path="*" verb="*" modules="StaticFileModule" preCondition="integratedMode" resourceType="File" requireAccess="Read" />
So rtpHarry was on the right track.
To fix this, I've added
<remove name="StaticFile"/>
above each of the
<add name="StaticFile"....
in all web.config files in the Bootstrap Theme.
What I don't understand is other themes, such as TheThemeMachine, also have child web.config in subfolder Styles for example, and they don't cause a problem when used. So what other settings somewhere affects this?
I'm discussing this on the Bootstrap theme ticket:
https://github.com/psenechal/PJS.Bootstrap/issues/12

Fixed it NOW it works with Orchard 1.9.3 or 1.10 or dev build from today.
Fully tested Zip file with fixed PJS.Bootstrap for 1.10 adding JetBrains.Annotations also you should add it to Orchard with package manager.
ZIp file for PJS.Bootstrap
Read below as this is how you fix old modules also.
Add PJS.Bootstrap as a new project in VS. 1.0 or dev and look at the references.
Core and Framework have old references
MVC is version <IP_ADDRESS>.
Remove then add correct ones. For MVC just remove MVC reference then use package manager to add MVC 5.3.0 and it will add MVC and the other updated  correct assemblies for PJS.Bootstrap not Orchard
PJS.Bootstrap.csproj is outdated
Change
<?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="4.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
To new Tools Version
<?xml version="1.0" encoding="utf-8"?> <Project ToolsVersion="12.0" DefaultTargets="Build" xmlns="http://schemas.microsoft.com/developer/msbuild/2003">
add
<ItemGroup>     <Content Include="packages.config" />   </ItemGroup>
then copy packages.config from any module to root of PJS.Bootstrap.
<?xml version="1.0" encoding="utf-8"?> <packages>   <package id="Microsoft.AspNet.Mvc" version="5.2.3" targetFramework="net451" />   <package id="Microsoft.AspNet.Razor" version="3.2.3" targetFramework="net451" />   <package id="Microsoft.AspNet.WebPages" version="3.2.3" targetFramework="net451" />   <package id="Microsoft.Web.Infrastructure" version="<IP_ADDRESS>" targetFramework="net451" />   <package id="Newtonsoft.Json" version="7.0.1" targetFramework="net451" /> </packages>
Change root web.config from
<remove assembly="System.Data.DataSetExtensions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
to
<add assembly="System.Web.Entity, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
<add assembly="System.Data.DataSetExtensions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
Update PJS web.config to 4.5.2 and MVC 5.2.3
Then use package Manager
Add JetBrains.Annotations
After installation you should have in root package file.

The above is how you would fix old modules also
References to core and framework and MVC. Then adding JetBrains.Annotations for some of the modules, as they were built with resharper and you get  [UsedImplicitly] and a dead reference to
using JetBrains.Annotations;
Mostly Themes and Old Modules were built having referenced
<remove assembly="System.Data.DataSetExtensions, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=B77A5C561934E089" />
which needs
<add assembly="System.Web.Entity, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=B77A5C561934E089" />


Only use custom AWS credentials when necessary

This actually fixes #1937.
I believe it was incorrectly closed because updating the library should have fixed it, but I found it was still not working in our ECS environment. Doing some more digging, I found that the credential provider chain was being re-implemented in distribution to accommodate the accesskey and secretkey configuration. This patch only uses credentials.StaticProvider when the configuration values are available -- when they aren't, it will use the default credential chain in aws-sdk-go.

Please sign your commits following these rules:
https://github.com/moby/moby/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "aws-credential-chain" git@github.com:keichan34/distribution.git somewhere
$ cd somewhere
$ git commit --amend -s --no-edit
$ git push -f

Amending updates the existing PR. You DO NOT need to open a new one.

is there any plan to get this merged ?

FYI Looks like this change made it in via #3245


Remove version: 8x8.VirtualOfficeDesktop version <IP_ADDRESS>

Consolidating into 8x8.Work. Related to: #135119
Microsoft Reviewers: Open in CodeFlow

URL: https://vod-updates.8x8.com/ga/work-64-msi-v7.9.4-2.msi
Status Code: 200
(Automated message - build 656)


azidentity: sync.Cond.Wait is not being called in syncer

Bug Report

import path of package in question: github.com/Azure/azure-sdk-for-go/sdk/azidentity
SDK version: latest
output of go version: go version go1.20.5 linux/amd64

What happened?

In sync.go implementation, we are using a sync.Cond to coordinate multiple goroutines access to the token value: https://github.com/Azure/azure-sdk-for-go/blob/246ae74957001c6165253c132edb4529fd3d62fb/sdk/azidentity/syncer.go#L59-L79
But giving the sync.Cond is using sync.Mutex as lock, I don't think the s.cond.Wait will be called at all: https://github.com/Azure/azure-sdk-for-go/blob/99ae59de1e55b6d2d33b40fa8f2cd3a091e7042a/sdk/azidentity/syncer.go#L72-L73
In cache miss case, the first goroutine enters the for-loop with obtaining s.authing and auth status, then break the loop. However, this goroutine will still hold the s.cond.L lock, as a result, other goroutines will be blocked in the s.cond.L.Lock() line, so no further calls will reach s.cond.Wait. We can confirm this behavior by checking the code path coverage from unit test.

What did you expect or want to happen?

I think it depends. From syncer's unit test: https://github.com/Azure/azure-sdk-for-go/blob/246ae74957001c6165253c132edb4529fd3d62fb/sdk/azidentity/syncer_test.go#L101-L103
It's expecting there will be N calls to the silent auth when there are N goroutines concurrently accessing the token. If this is the case, I think we can simplify the code to use a sync.Mutex only?
If that's not the case, I think we need to move the s.cond.L.Unlock right outside the for loop so other goroutines can enter the for loop to wait, like this:
        s.cond.L.Lock()
-       defer s.cond.L.Unlock()
	for {
		at, err = s.silent(ctx, opts)
		if err == nil {
			// got a token
			break
		}
		if !s.authing {
			// this goroutine will request a token
			s.authing, auth = true, true
			break
		}
		// another goroutine is acquiring a token; wait for it to finish, then try silent auth again
		s.cond.Wait()
	}
+	s.cond.L.Unlock()

	if auth {
		at, err = s.reqToken(ctx, opts)
+
+		s.cond.L.Lock()
+		s.authing = false
+		s.cond.Broadcast()
+		s.cond.L.Unlock()
	}

But this will increase calls to silent auth though.

How can we reproduce it?

Check with code path coverage from unit test.

Anything we should know about your environment.

Follow up question:

We also want to confirm if the access control here is for limiting all access to the token, even the request option is different. We are using this library in a first party environment, therefore, we will need to request tokens for different tenants or different scopes at the same time.

Thanks for opening this! You're right, the condition is unused and therefore devolves to a mutex, so we may as well have just the mutex and simpler code.

But this will increase calls to silent auth though.

We'll still try silent auth once for every GetToken call, which is what we want because that's how we search the token cache.

We also want to confirm if the access control here is for limiting all access to the token, even the request option is different.

Currently we allow only one goroutine to authenticate with a credential instance at a time to avoid hitting a rate limit with redundant token requests. This enables sharing a credential instance--and thereby its token cache--with an arbitrary number of clients/goroutines.

We are using this library in a first party environment, therefore, we will need to request tokens for different tenants or different scopes at the same time.

I suppose it would be possible to synchronize goroutines more precisely by considering the parameters of the requested token. However, that would be much more complex than the current implementation and I imagine not much better for most applications. If the performance characteristics of the current implementation aren't acceptable for your application, I'd like to understand the bottlenecks through concrete perf data before jumping to a solution.


settings validations: implement certificate chain verification

When using the new Certificate option, the validate_settings should ensure the certificate can be verified using the optional certificate_chain provided by the user.
See https://github.com/kubewarden/verify-image-signatures/blob/b6a1c64abfcb1f78fd20937e3b30d97ea65576b8/src/settings.rs#L108-L109
This is part of https://github.com/kubewarden/verify-image-signatures/issues/39

This depends on https://github.com/kubewarden/policy-evaluator/issues/200

https://github.com/kubewarden/verify-image-signatures/pull/47 implements it, but missing e2e tests in a new PR.


Sioyek

First of all, thank you for the plugin: very helpful.
If you want to add instructions for Sioyek, the required configuration within the texlab lsp-config forwardSearch is simply:
executable = 'sioyek' ,
args = {'--reuse-instance', "--inverse-search", [[nvim-texlabconfig -file %1 -line %2]], "--forward-search-file", "%f", "--forward-search-line", "%l", "%p"}

I just saw your commit, that was fast! I just want to point out that in Sioyek you do not need to put the name of the file in quotes, so it is %1 not '%1'. Apparently, Sioyek already does it when passing the variable.

Thanks


Update scalafmt-core to 3.0.6

Updates org.scalameta:scalafmt-core from 3.0.4 to 3.0.6.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "scalafmt-core" } ]

labels: library-update, semver-patch

Superseded by #124.


Segmentation fault when calling function after fmiUnload()

Description
When I call a function after fmiUnload I get an segmentation fault and Julia crashes.
How to reproduce
I have a FMU that I can't share that produces this error, but I can't get a FMU from the Modelica Standard Library to simulate because of #63. But I guess this should work for any FMU.
using FMI

myFMU = fmiLoad("someFMu.fmu")
fmiInstantiate!(myFMU)
success, simData = fmiSimulate(myFMU, 0.0, 1.0)
fmiUnload(myFMU)

fmiInfo(myFMU)

Of course I expect an error, but not a segmentation fault.

Version 'n stuff
OS: Ubuntu 20.04
Julia:
Julia Version 1.7.1
Commit ac5cc99908 (2021-12-22 19:35 UTC)
Platform Info:
  OS: Linux (x86_64-pc-linux-gnu)
  CPU: Intel(R) Core(TM) i7-10700KF CPU @ 3.80GHz
  WORD_SIZE: 64
  LIBM: libopenlibm
  LLVM: libLLVM-12.0.1 (ORCJIT, skylake)

(@v1.7) pkg> status FMI
      Status `~/.julia/environments/v1.7/Project.toml`
  [14a09403] FMI v0.3.6

Hey Andreas,
I agree that an error message should be the way to go, instead af a crash. As you expected, this issue affects any FMU. I will try to find a nice solution for this. Until then, don't do such evil things and let that dead piece of memory in peace after fmiUnload 😅

this can be closed, please reopen if this is still the case with v0.13.0


Minor fix, again and again

actually proof-read this time. Hopefully my eyes are not in their terminal stage of cancer.

Hydrogen the liquid is missing its key and some crafting recipes don't show up in the manual for whatever reason and Rocket's page is not correctly displayed halp

You really need to fix the formatting

You really need to fix the formatting

Jesus fuck I checked the formatting this time why still aw cmon


Adding Hazelcast Management Center to the exporter list

Adding Hazelcast Management Center to the exporter list

Is this really an exporter? It seems to be the application itself exposing metrics.
Where can I find the relevant source code?

Hello @brian-brazil , the Management Center is a monitoring tool that gathers metrics from Hazelcast nodes, and exports the metrics to Prometheus.
The relevant source code is in this package: https://github.com/hazelcast/management-center/tree/master/src/main/java/com/hazelcast/webmonitor/service/prometheus
Also the relevant integration test: https://github.com/hazelcast/management-center/blob/master/src/test/java/com/hazelcast/webmonitor/service/prometheus/PrometheusExportIntegrationTest.java

Those links don't work. Is this basically a proxy for JMX?

the Management Center is a monitoring tool that gathers metrics from Hazelcast nodes,

That's not the preferred architecture for Prometheus, which should scrape processes directly. This is both more efficient, more scalable, and avoids artifacts and weirdness.

Also, do you have a link to an architecture diagram? Most of what I can find about Hazelcast is marketing material, so I can't figure out how this all fits together.

Hello,
you may look into the Architecture section of the HZ reference manual, though it doesn't include management center:  https://docs.hazelcast.org/docs/latest-dev/manual/html-single/#hazelcast-imdg-architecture

Thanks, but that appears to be software architecture rather than systems architecture. I want to understand what sort of inter-process communication is going on here.

Briefly, Hazelcast nodes (cluster members) can be connected to a Management Center application, which is partly a monitoring tool. The nodes stream metrics to MC using Hazelcast's own server-client communication protocol. Most of the metrics are related to the distributed objects (operation latencies, data structure sizes, cache hit ratios, etc).
The list of metrics can be found here: https://github.com/hazelcast/hazelcast/blob/master/hazelcast/src/main/java/com/hazelcast/internal/metrics/MetricDescriptorConstants.java

Okay, so this isn't an exporter then but software exposing Prometheus metrics. Can these metrics be obtained more directly from the nodes, such as via JMX?

It is an exporter as Management Center is exporting our internal metrics into a Prometheus end point.
It is possible to obtain metrics directly from the nodes using JMX from the nodes but there are a number of important advantages by using the Management Center exporter:

Management Center provides a Clustered overview as part of metrics
Hazelcast is designed to allow nodes to be added/removed from the cluster which would require the Prometheus config to be updated if pulling the metrics directly.  Using the Management Center Prometheus exporter removes that requirement
Management Center supports connections to multiple clusters
As requested by our customers, having a Prometheus exporter within Management Center removes an additional hop

It is an exporter as Management Center is exporting our internal metrics into a Prometheus end point.

That doesn't make it an exporter automatically, by that definition the Alertmanager is an exporter - which it isn't. Exporters exist with a primary aim of producing metrics from 3rd party systems, and this is all 1st party.

Management Center provides a Clustered overview as part of metrics
Hazelcast is designed to allow nodes to be added/removed from the cluster which would require the Prometheus config to be updated if pulling the metrics directly. Using the Management Center Prometheus exporter removes that requirement
Management Center supports connections to multiple clusters

These are all considered anti-patterns, service discovery, scraping, and aggregation are the responsibility of Prometheus - not of targets.

As requested by our customers, having a Prometheus exporter within Management Center removes an additional hop

This is actually adding a hop, adds a SPOF, latency, and can cause artifacts. The Prometheus way is to talk to targets directly.

It is possible to obtain metrics directly from the nodes using JMX

Our general policy is not to try not to list duplicates, so as these metrics are already available in a more Promethean way via an existing exporter so this PR is not the way to go and I'm going to close this for noe.
If your nodes gain a Prometheus endpoint at some point, we can list them under software exporting Prometheus metrics.


Add description for priority of pp and cpp

What type of PR is this?
/kind documentation
What this PR does / why we need it:
Add description for priority of pp and cpp
Which issue(s) this PR fixes:
Fixes #422
Special notes for your reviewer:
None

/cc @jwcesign

/assign


New slinky integration

Is there a reason why App is not as Slinky-fied as it could be?

@react annotation
Hooks
web.html components

No, not much thought have gone into it. I thought it was pretty close to yours, but if anything is missing/different feel free to add it - you should have write access here now.
The only thing i knowingly left out was your css, and that was just laziness. feel free to re-add that as well

A more precise question. Since you said:

i think it would be nice to have a few react demos done in a duo/trio with only scalablytyped, with slinky, and possible with scalajs-react

This is the only scalablytyped.
If I Slinky-fy it, it becomes the one with slinky.
So how you have imagined the duo?
In the meanwhile I will take care of the css.
At the same time, thank you for all the lessons. I start to see that doing it with or without Slinky is more or less the same with no so great differences.

Ok forget, this last comment, I now see that there is an antd-slinky demo!

It seems good to go.
Maybe you want first to publish the improved react-slinky-facade so that I can be added as an external dependency.
Just a minor point. In the slinky version, I moved from
val noteTitle: js.UndefOr[String]
to
val noteTitle: String
My idea is that you want less js around as possible and also you should know the props needed by the component you intend to use.
Or maybe we could have val noteTitle: String = "Note" with a given default.

Awesome stuff @mcallisto. Im afk until tomorrow late, so will have a better look then.
Will definitely publish the new facade before we merge this, though I've hoped to experiment a bit and see what other improvements can be found :)

Everything you pushed looked good @mcallisto . I gave it a go to make a facade for Route, WDYT?

Ok, I had a bit more time to flesh out how I imagine a slinky facade layer can look like. Take a look at AntdFacade and ReactRouterFacade in the newest commit, and see how they are used. I can describe these ideas in more text if it's not clear, but some input on this would be very very useful now :)

Really positively impressed.
I think the two layers solution (ScalableSlinky + individual library facade) is great.

encourages others to try writing facades, they have a blueprint
makes the final code clearer and cleaner, short and in accordance with Slinky "dialect"

Happy you like it so far @mcallisto . I'll let this stay open for some more days and think about what else we can do to make the situation better :)

Just a headsup: I just pushed a commit which wont build until we update it with the new ScalablyTyped build in the morning
We no longer need to write all the props forwarders, since i put them in a trait :)

I merged the slinky integration now, so it'll be released tomorrow. merging this after that.


[SPARK-38523][SQL] Fix referring to the corrupt record column from CSV

What changes were proposed in this pull request?
In the case when an user specifies the corrupt record column via the CSV option columnNameOfCorruptRecord:

Disable the column pruning feature in the CSV parser.
Don't push filters to UnivocityParser that refer to the "virtual" column columnNameOfCorruptRecord. Since the column cannot present in the input CSV, user's queries fail while compiling predicates. After the changes, the skipped filters are applied later on the upper layer.

Why are the changes needed?
The changes allow to refer to the corrupt record column from user's queries:
spark.read.format("csv")
  .option("header", "true")
  .option("columnNameOfCorruptRecord", "corrRec")
  .schema(schema)
  .load("csv_corrupt_record.csv")
  .filter($"corrRec".isNotNull)
  .show()

for the input file "csv_corrupt_record.csv":
0,2013-111_11 12:13:14
1,1983-08-04

the query returns:
+---+----+----------------------+
|a  |b   |corrRec               |
+---+----+----------------------+
|0  |null|0,2013-111_11 12:13:14|
+---+----+----------------------+

Does this PR introduce any user-facing change?
Yes. Before the changes, the query above fails with the exception:
java.lang.IllegalArgumentException: _corrupt_record does not exist. Available: a, b
	at org.apache.spark.sql.types.StructType.$anonfun$fieldIndex$1(StructType.scala:310) ~[classes/:?]

How was this patch tested?
By running new CSV test:
$ build/sbt "sql/testOnly *.CSVv1Suite"
$ build/sbt "sql/testOnly *.CSVv2Suite"
$ build/sbt "sql/testOnly *.CSVLegacyTimeParserSuite"

thanks, merging to master!

Shall we do the same thing for JSON?


fix(members): fix members creating and importing. Fixes MEMB-865

:tada: This PR is included in version 1.2.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Repository] add a check to ensure a quickstart directory name follows our conventions

we had an issue where the directory name for this quickstart was set to Jumpstart - Quickstart, which is invalid as it breaks when we load the quickstarts into our service. The directory should be lowercase-hyphenated.
Acceptance Criteria

[ ] Add a check so we can check to make sure the directory name is set correctly to lowercase-hyphenated.

@aswanson-nr I'm curious if this is now enforced by the catalog service, and this is no longer a concern for the repo. What do you think?

This would not be handled by the catalog service since the catalog service is unaware of the repo structure. This would need to be handled repo-side to enforce a particular repo structure.

@jerelmiller Thank you!


Better documentation of input/output dimensions

Thanks for this great package! I think the documentation could be improved be defining the expected input dimensions better.
I think some thing like this would help a lot:
Operator kernel layer
v_{t+1}(x) = \sigma(W v_t(x) + \mathcal{K} \{ v_t(x) \} )

where x \in R^d, v_{t}\in R^c_in and v_{t+1}\in R^c_out.
Arguments

ch: A `Pair` of input (`c_in`) and output channel size  (`c_out`), e.g. 64=>64.

modes: The modes to be preserved. A tuple of length `d`.

...

permuted: Whether the dim is permuted. If permuted=true, layer accepts data in the order of (c_in, x_1, ... x_d, batch), otherwise the order is (x_1, ... x_d, c_in, batch).

(sorry, I'm not sure why the format is off)

Or more directly, it should conform to what's described in the SciML Style for this: https://github.com/SciML/SciMLStyle#documentation .
The new SciMLSensitivity.jl documentation is a good model to follow: https://sensitivity.sciml.ai/dev/

actually, I am thinking about not to support the permuted option to keep things simple... 😕

Thanks for looking into this! Some other remark regarding documentation:
The docs of the "models" FourierNeuralOperator and MarkovNeuralOperator could need some improvements as well. For example, I somehow expected that I can define a model with more or less layers depending on the length of the ch argument.
Looking at the code, however, it seems that both function define a fixed architecture. It is also interesting that they are almost the same  - which is very surprising given the very different names! (There seems nothing especially Markovian in MarkovNeuralOperator , it's more the application).
It may be more transparent to remove this wrapper functions from the API and instead define them in the application examples/tutorials.

@scheidan As for the models, on one hand, it is more like a doc to me to understand how to intergrate OperatorKernel with other layers. On the other hand, the reason why the FourierNeuralOperator and MarkovNeuralOperator will work, discribed in the original paper. I have also try with some other architecture including increase or decrease the number of OperatorKernel layer, but they all turns out to give worse result. Therefore, I descided to implement the model APIs in a fixed architecture (maybe the SOTA architecture). The model APIs is to provide a easy way for one to get quick start with NeuralOperators.jl. For advenced user, one can just build their own model with OperatorKernel layer and regarde the model APIs as the doc 😄

Now I understand your reasoning for the models, makes sense! :)
A short sentence like:
"The models are based on the layers described above and implement the architecture used in referenced paper."
should help to clarify the issue.

@scheidan Thanks for the advice. Please take a look at the PR.

That a big improvement, thanks! Especially the models should be clear now.
Unfortunately I could not comment on the PR directly (or I did not know how to :)
There are two points that are not well defined yet:

A tuple of length c where d is the dimension of data. What is the the dimension of the data? The channels are also a dimension...
layer accepts data in the order of (ch, ..., batch) Here we should explain what the ... stand for. This was the most confusing point for me at the beginning.

To avoid this confusion I proposed above that we first define d, ch_in, ch_out and x1, ..., x_d in mathematical terms using the equation for the operator kernel. Then we can write
(ch_in, x1, ... , x_d, batch)

@scheidan Please take a look at the PR and see if this works for you 😄

I would like to merge and temporary close this issue. Please feel free to re-open the issue if needed.


[Wrong path] Ion RangeSlider skin

The path is no good in Ion RangeSlider css files
for example Nice skin
This is pointing to
background: url(../../img/sprite-skin-nice.png) repeat-x;

and this should point to
background: url(../../dist/img/sprite-skin-nice.png) repeat-x;

Same thing for flat skin

Thank you for letting me know. I meant to seperate images that belong to plugins from the dist folder and put them with their respective plugin as in the case with iCheck.
Fixed in master.


Retina screenshots ftw

Screenshot made using cmd + 4 + Space (native mac screenshot tool) and then resize when uploaded to github.

Well you can't deny it's pixelated and therefore shitty quality.

Juha

Valerii Sorokobatko<EMAIL_ADDRESS>kirjoitti 22.5.2018 kello 18.41:
Screenshot made using cmd + 4 + Space (native mac screenshot tool) and then resize when uploaded to github.
―
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.


Fix: Avatar background color

This update fixes an issue with the avatar button background color. In #685 we add replace the <div> with a <button> when the Avatar component is actionable. By doing that the default button background was still present. Now it will be a transparent background.
Before

After

Remove avatar animation
This update add an animation sequence to remove an avatar. It will add a border animation, force load the fallback image and fade out the actual avatar. When the animation is completed, the avatar will not be clickable anymore

Right now this animation is only valid for the circle shape.

I pushed another update with the full remove avatar animation. This last commit completed what was needed for the Avatar

@tinkertrain I fixed the issue on firefox. It seems that FF does not support modifying the svg circle attributes from CSS, I create a helper that would allow us to set the attribute directly on the svg element
I'll go ahead with merging the PR


Add name and year to license copyright

Thanks for the great library!
Just a pedantic little nitpick: The license file currently has the default "Copyright (c) [year] [fullname]"

Silly me.
Fixed in 81a33897e31f7eaf5dc0ebbfaa00961db95c0cc9


firefox scroll error

When reporting a bug, make sure you provide all required info below. Reports without this information may be closed.
Output of gemini --version:
5.0.0-alpha.2
Contents of .gemini.yml file:

Test source code:
//basic.md对应ui测试用例
gemini.suite('basic', function(suite) {
    suite.setUrl('/docs/basic.html')
        .setCaptureElements('body')
        .capture('plain', function(actions, find) {
            let button = find('.next-btn-primary');
            actions.click(button);

            //用于延迟多少毫秒,解决一些执行时间较长时导致截取中间态的问题
            actions.wait(waitTime);
        });
});

//customize-footer.md对应ui测试用例
gemini.suite('customize-footer', function(suite) {
    suite.setUrl('/docs/customize-footer.html')
    .setCaptureElements('.example')
    .capture('plain', function(actions, find) {

      //用于延迟多少毫秒,解决一些执行时间较长时导致截取中间态的问题
      //actions.wait(waitTime);
    });
});

Command used to run the test:

Publically accessible URL of the page you are testing against:
http://
I have  a dialog component , when i click the button the dialog will open . I have twe demo page, the first page i capture after click the button, but affect the second page;
Result:

...
Expected behaviour:
...

it is strange that it will affect on the next suite, but the third will be ok.

looks like this moveTo fails https://github.com/gemini-testing/gemini/blob/master/lib/browser/new-browser.js#L266

Hi @nanjixiong218 . You use selenium standalone? You can show the configuration file to run the tests in firefox?


[Mention]: Fix Cursor Follower to Disappear on Cursor Exit from Webpage

Is your feature request related to a problem? Please describe.
Description:
The website currently features a cursor follower element that tracks the cursor position across the page. However, when the cursor exits the webpage (e.g., when moving outside the browser window), the follower remains visible and stops at the boundary of the page. This behavior is visually distracting and disrupts the user experience. The desired behavior is for the cursor follower to disappear when the cursor leaves the webpage and reappear as soon as the cursor reenters.
Steps to Reproduce:

Open the webpage with the cursor follower enabled.
Move the cursor towards the edge of the window until it exits the webpage.
Observe that the cursor follower remains at the boundary and does not disappear.

Expected Behavior:
The cursor follower should:

Disappear when the cursor leaves the webpage.
Reappear and resume following the cursor as soon as it reenters the webpage.

Describe the solution you'd like.
Proposed Solution:
Add event listeners to detect when the cursor exits and reenters the webpage:

On mouseleave, hide or remove the cursor follower.
On mouseenter, make the cursor follower visible again and resume tracking the cursor.

Describe alternatives you've considered.
No response
Additional context.
Additional Context:
This change will enhance the website’s interactivity by providing a cleaner experience, especially when users switch tabs or move the cursor outside the browser window.
Show us the magic with screenshots

Checklist

[X] I have checked the Existing Issues
[X] I have read the Contributing Guidelines
[X] I want to work on this issue. (optional)

Thank you for raising the issue.
But for now it is not required.
So I am closing this issue.
Please understand.
And one more thing this project is already inactive including me also due to some of my works.
Please do contribute to other projects.

@CoderFleet assigning this issue to you.
Make sure to complete this fast within an hour.
This will be the only issue that I will assign you.
As I have said earlier this project will be inactive from today night including me also.

Very Thank You... started working on it right away