Dynamic loop creation DOM，passing a callback function as a component property，cannot be obtained in the component

I packaged a component, import the component,dynamic loop creation DOM  , Passing a callback function as the component property，In packaged component, the property is undefined，I use the method is wrong？
in AnimateImage.js
This line of code is wrong
// print undefined, If don't create DOM dynamically, this property can be obtained.
console.log(onPress, 'onPress');

Game.js
import React, { Component } from 'react';
import {
  AppRegistry,
  StyleSheet,
  TouchableWithoutFeedback,
  Text,
  View

} from 'react-native';

import AnimateImage from '../control/AnimateImage';
import _ from 'lodash';

export default class Game extends Component {
  constructor(props){
    super(props);
    let {imageArray} = this.props;
    this.state = {
      rows: [],
      imageArray: imageArray || [],
    };
  };

  componentDidMount(){
    this.createPokers();
  };

  onPress = () => {
    console.log('sucess');
  }

  //imageArray = [1,2,3,4]
  createPokers = () => {
    let self = this;
    let rows = imageArray.reduce(function(memo, value){
      memo.push(
          <AnimateImage
            key={'backImage'+ value}
            style={{left: 0 - value * 120}}
            animate="bounceInLeft"
            imageHeight={220}
            imageWidth={150}>
            onPress={self.onPress}
          </AnimateImage>
      );
      return memo;
    }, []);
    this.setState({rows: rows});
  };

  render() {
    return (
      <View>
        <View ref="viewPoker" style={[styles.viewRow, styles.AnimateImage]}>
          {this.state.rows}
        </View>
      </View>
    );
  }
}

const styles = StyleSheet.create({
  viewRow: {
    flexDirection: 'row',
    position: 'absolute',
  },
  AnimateImage: {
    left: 150,
    top:300,
  }
});

AppRegistry.registerComponent('Game', () => Game);

AnimateImage.js
import React, { Component } from 'react';
import {
  AppRegistry,
  StyleSheet,
  Image,
  TouchableWithoutFeedback,
  Text,
  View
} from 'react-native';

import * as Animatable from 'react-native-animatable';

export default class AnimateImage extends Component {
  constructor(props){
    super(props);
    let {animate, text, imageHeight, imageWidth, style, onPress} = this.props;
    console.log(onPress, 'onPress');  // print undefined
    this.state = {
      animate: animate || '',
      imageHeight: imageHeight || 300,
      imageWidth: imageWidth || 200,
      style: style || {},
      callback: onPress || {}
    };
  };

  buttonPress = () => {
    this.refs.view.fadeOutUpBig(1500).then((endState) => {
      this.state.callback();
    });
  };

  render() {
    return (
      <TouchableWithoutFeedback onPress={this.buttonPress}>
        <Animatable.View animation={this.state.animate} ref="view">
          <Image
            style={[this.state.style, {height: parseInt(this.state.imageHeight), width:parseInt(this.state.imageWidth)}]}
            source={require('./../../src/images/poker-back.png')}
          />
        </Animatable.View>
      </TouchableWithoutFeedback>
    );
  }
}

AppRegistry.registerComponent('AnimateImage', () => AnimateImage);

@facebook-github-bot stack-overflow

Hey @LittleChild and thanks for posting this! @ide tells me this issue looks like a question that would be best asked on StackOverflow. StackOverflow is amazing for Q&A: it has a reputation system, voting, the ability to mark a question as answered. Because of the reputation system it is likely the community will see and answer your question there. This also helps us use the GitHub bug tracker for bugs only. Will close this as this is really a question that should be asked on SO.

I see. Thank you.


Incorrect control center state at the end of an on-demand playback media

When playing a media until the end with the control center open, the end control state is not correct (pause button instead of play button).
Issue type
Incorrect behavior
Environment information

Library version: 1.13 (and probably earlier)
iOS version: Any
Device: Physical

Reproducibility
Always reproducible
Steps to reproduce

Open the SWI VOD example.
Seek near the end.
Open the control center.
Wait until playback ends. The state of the UI does not reflect the fact that playback ended.

Works on iOS 13.2. I would wait until control center implementation has been rewritten (#182), then close this issue.


chore: improve uring performance

Use io_uring_submit_and_get_events to both submit events and also fetch completions in single
syscall.
Make the critical section around blocking I/O command wait_for_cqe as small as possible to
increase the chances that another thread will notify the proactor in time. That should
decrease the amount of false positives where proactor blocks and then immediately wakes up
do to notifications via kernel.

Performance tests:
dragonfly is running on a 8-cpu server (aarch64), memtier client with 16 cpus:
memtier_benchmark -s <IP_ADDRESS> --command=PING -t 16 -c 18 -n 60000 --hide-histogram --distinct-client-seed
PING because we test pure networking stuff.
 Please review.

Comparison is base (7824c85) 78.73% compared to head (5d48ded) 78.74%.

Files
Patch %
Lines

util/fibers/uring_proactor.cc
94.73%
1 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##           master     #183      +/-   ##
==========================================
+ Coverage   78.73%   78.74%   +0.01%
==========================================
  Files         100      100
  Lines        7335     7335
==========================================
+ Hits         5775     5776       +1
+ Misses       1560     1559       -1

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

For same 3 configurations with GETs on empty database (testing the networking + 1 single hop, noop command):
memtier_benchmark -s <IP_ADDRESS> --ratio=0:1 -t 16 -c 18 -n 60000 --hide-histogram --distinct-client-seed
Dragonfly with all the improvements
============================================================================================================================
Type         Ops/sec     Hits/sec   Misses/sec    Avg. Latency     p50 Latency     p99 Latency   p99.9 Latency       KB/sec
----------------------------------------------------------------------------------------------------------------------------
Gets       740704.48         0.00    740704.48         0.38514         0.38300         0.55100         0.66300     28853.47

Dragonfly upto #193
============================================================================================================================
Type         Ops/sec     Hits/sec   Misses/sec    Avg. Latency     p50 Latency     p99 Latency   p99.9 Latency       KB/sec
----------------------------------------------------------------------------------------------------------------------------
Gets       716695.29         0.00    716695.29         0.40247         0.40700         0.59100         0.75100     27918.21

Dragonfly v1.13
============================================================================================================================
Type         Ops/sec     Hits/sec   Misses/sec    Avg. Latency     p50 Latency     p99 Latency   p99.9 Latency       KB/sec
----------------------------------------------------------------------------------------------------------------------------
Gets       689701.00         0.00    689701.00         0.42315         0.43100         0.61500         0.74300     26866.67


Input text in login prompts while on headless mode - try if Xvfb in Linux works

Hi,
I am currently trying to access an internal site using python-rpa and I am stuck on the login prompt.

How do I input details on this type of prompts when I am on headless mode?
I tried r.type() but it needs to have a target, r.keyboard() needs to have visual init but I am on headless mode.
Thanks,
Fred

Hi @frederick0291, I'm afraid in the headless mode this can't work for rpa package. The reason is because it depends on TagUI engine, which would wait until Chrome responds back to the instruction. But an alert popup would be a blocking process that would not return the control back to the engine until users click it.
If you are on Linux, can you try running with virtual display? See below Colab example. The virtual display would allow using computer vision to click on something. However, this is not tested before and you probably need to install OpenCV and Tesseract manually in this way - https://sikulix-2014.readthedocs.io/en/latest/newslinux.html
https://colab.research.google.com/drive/13bQO6G_hzE1teX35a3NZ4T5K-ICFFdB5?usp=sharing

Thanks @kensoh.
I discovered that you can actually bypass login prompts by passing the username and password to the URL like this:
<EMAIL_ADDRESS>You need to url escape your user and password though so every special character gets converted. No need to handle the prompt.

Thanks @frederick0291 this is a great tip! I'll keep this in mind for future users' questions.
There is another use case which above still might not work, those popup with a button to click Ok or Yes.


Add #to_yaml method for ImmutableMash & ImmutableArray

Description
- Psych module to_yaml not working as expected for ImmutableMash & ImmutableArray.
 - So parse first to Hash/Array then convert it to YAML formatted string.
eg.

If hash is assgined to node attribute it is returning ImmutableMash

> node.default['test'] = {'bar' => ['baz'], 'bing' => 'boo'}
> node['test'].class # ImmutableMash

If Array is assigned to node attribute it is returning ImmutableArray

> node.default['test'] = [{'bar' => ['baz']}, {'bing' => 'boo'}]
> node['test'].class # ImmutableArray

If any other value is assigned to node to_yaml working as expected.

Related Issue

https://github.com/chef/chef/issues/8820
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Chore (non-breaking change that does not add functionality or fix an issue)

Checklist:

[ ] I have read the CONTRIBUTING document.
[ ] I have run the pre-merge tests locally and they pass.
[ ] I have updated the documentation accordingly.
[x] I have added tests to cover my changes.
[x] All new and existing tests passed.
[x] All commits have been signed-off for the Developer Certificate of Origin.
Signed-off-by: Vivek Singh<EMAIL_ADDRESS>

should probably add this API for the VividMash/ArrayAttr classes as well since users can get at those out of the components. i would think we'd need to add something in Chef::Node::Attribute as well to make this change visible.

Have added to_yaml method for VividMash/AttrArray and also for Chef::Node::Attribute.
Fix to_json is missing Chef::Node::Attribute that raises error Wrong number of an argument while calling on object
Refactor the specs using a shared example.

@lamont-granquist  could you please have a look again?
Thanks!


[WIP] Add docs for non-deterministic error

need more work to convert from https://docs.google.com/document/d/1JbNMUIldrXU8WzYyjgbCfByrVbqbDm1BTSgSFsefLvU

close because I don't have permission on uber repo anymore.
Will use this one https://github.com/uber/cadence/pull/2957


HV-1490 Don't fallback to the TCCL when detecting features in ConstraintHelper

We need to be able to access the class from the HV CL when we extract
the validated type from the validator generics.

https://hibernate.atlassian.net/browse/HV-1490

Jenkins, retest this please

Could we alternative also load the class using the TCCL? I.e. check and load the class using the same class loader? I think we had this discussion in the past but can't quite remember the outcome. Assuming the constraint validator class doesn't require any HV specifics (or we can restructure their code so that they don't) this also may let WF users use the Money constraints if they provide this as part of the deployment. WDYT?

After discussing with @gsmet we agreed that loading via the TCCL isn't feasible as the constraint validator classes of HV won't be visible there.
Merging as proposed.


Cost policy behaviors (e.g. don't post a comment if estimate < threshold)

We published a new blog about native support for cost policies in infracost comment as of v0.9.20 (using Open Policy Agent). I'm creating this issue so the community can discuss what behaviors are needed, some ideas are:

If estimate is crazy high, fail the build; e.g. don’t let users merge a PR that increases the cost estimate by $50K.
If estimate is over a threshold, leave a warning with an action; e.g. talk to person X, see link Y. Don’t fail the build in this situation.
Always show a green tick and post the comment, it's re-assuring that Infracost checked the cost estimate and it passed (similar to how unit tests show a green tick).
If the estimate is under a threshold, don’t add a comment, it’s just noise.

Note for community
Which behaviors make sense for you and why?
Also, feel free to 👍 if you'd like to upvote this or receive updates.

Just FYI that I also created https://github.com/infracost/infracost/issues/1727 that users watching this issue might be interested in.


Possible non-fatal issue in decoder

As far as i understand, here https://github.com/MarcoForte/FBA_Matting/blob/master/networks/models.py#L230
resnet backbone will return such feature maps: [original_image, conv_bn_relu out, layer1 out, layer2 out, layer3 out, layer4 out]
In the decoder https://github.com/MarcoForte/FBA_Matting/blob/master/networks/models.py#L350
you concatenate: (x, conv_out[-6][:, :3], img, two_chan_trimap).
But conv_out[-6][:, :3] is the same as img. Are you sure that image should be concatenated twice?

Possibly the same issue https://github.com/MarcoForte/FBA_Matting/issues/49#issuecomment-1027875080


fix middleman/ruby process 100% CPU usage problem ( in macOS 11.x Big Sur )

before

after

@guanting112 did you discover a solution? we're happy to bump this dependency if it improves things?


Missing redirection method that would make it easy to change the window.location

It would be nice to have a new redirection function in the router that would work like the current ones but that would set window.location.

A function on widget or the router? How would we name it?

I'm not sure if it belongs to the router or not, but for the sake of consistency, I would put it there (and on my in widget, just like the other routing methods).


No such file or directory: 'gaussian_fit.pt'

Hi!
I find your work to be very interesting,
As I tried to reproduce the result from the given code, I encountered the following error:
FileNotFoundError: [Errno 2] No such file or directory: 'gaussian_fit.pt'
It seems like the file is missing from the repo, could you please upload it?
PS
I run: python3 rec_mult.py --config configs_stylegan2.yml

Thanks for your comment! The file 'gaussian_fit.pt' is actually the mentioned shape_predictor downloaded by the provided instruWelcomeFeel free to contact me if you have any further question.

I understand, thank you for the reply!


Specify compatible Python versions

It would be useful to have the compatible Python versions listed somewhere. I see a mention to Python 3.x in the README but it would be best to know which ones exactly. I'd recommend committing to support 3.6+ only since conda-forge no longer builds 3.5 packages.
In particular, it would be good to specify the python_requires argument to setup.py so that pip knows which versions are compatible.

I'll update the docs to explicitly say which versions of Python are supported.

I'd recommend committing to support 3.6+ only since conda-forge no longer builds 3.5 packages.

Thanks, I think that's a fair limit on Python 3.x support. PVGeo will, however, continue full support for Python 2.7 until ParaView switches to Python 3.7 (likely on release 5.8 next fall).
Most users of PVGeo will hopefully be transitioning to using vtki (which we are working towards only supporting 3.6+) rather than ParaView for the supporting visualization package. The wrappings that make PVGeo available as plugins directly within ParaView is a major selling point to many users - thus Python 2.7 will have to remain for this project.

@leouieda: I implemented changes to address this, but would you please close this issue when you think these points are resolved?

:+1: looks good to me


add more fields similar to nationatlity / currency

subtype, subcategory, etc.

@shadiakiki1986 you can merge the branch export with the origin, I did the necessary tests.

@minerva22 Great, thanks! Just don't close the issue next time. We'll close it after we merge with the master branch

closing this in favor of #4


Added line colours

Added GO Transit line colours. Fixes #6 .

I appreciate the work you did to help out, but I have since refactored the application and am steadily converting it to an Angular codebase. I've also changed my approach from scraping of the GO Transit website to using their newly discovered API.


[Devfile] odo needs to be storing namespace in local env.yaml file

/kind bug
What versions of software are you using?
Operating System:
macOS
Output of odo version:
odo from master
Actual behavior
I've been looking at writing integration tests for odo's devfile support and was hitting a bizarre issue: tests would intermittently fail because it was trying to retrieve Kube resources or do an odo push in a different namespace than what was expected, thus causing a number of errors
What was happening is that the integration tests would be running in parallel, and standing up their own namespace/project for each test. Since odo push --devfile always just uses the current active namespace (rather than one specified by the user with a --namespace flag or the namespace where the component was pushed to), this would mean a number of issues could occur:
- odo push fails because the namespace is being terminated
- odo push pushes to the wrong namespace
- Unable to retrieve pods because the namespace we did the odo push in, is no longer the active namespace
We should modify odo push for devfiles to do the following:

Add a --namespace flag to the command, allowing the user to specify the namespace to be used

Store the namespace in env.yaml

If no value was passed in with the flag, check If a namespace exists in env.yaml and if so, use it
Use the current active namespace if no namespace is set in either --namespace or in the env.yaml

Expected behavior
odo push doesn't always use the current active namespace

/area devfile

We should modify odo push for devfiles to do the following:

Add a --namespace flag to the command, allowing the user to specify the namespace to be used

Store the namespace in env.yaml

If no value was passed in with the flag, check If a namespace exists in env.yaml and if so, use it

Use the current active namespace if no namespace is set in either --namespace or in the env.yaml

+1
A little bit of context:
We haven't had this problem before, as for "LocalConfig" components (based on s2i) odo is storing namespace in LocalConfg in .odo/config.yaml with other values. But this is not a good solution as it mixes application definitions and environment-specific config in one file.
What you are proposing makes sense.
But for your testing problem, there is a solution even with the current implementation. It should be possible to just copy the current $KUBECONFIG file into a new location and set KUBECONFIG to this copy in  BeforeSuite function https://onsi.github.io/ginkgo/#parallel-specs.
Putting it here just for a record. Not saying that we need to do this. We will need --namespace flag anyway

@elsony Per your request, In this issue we can
Implement
Store namespace info into env.yaml if user specify namespace when running odo create
For

If no value was passed in with the flag, check If a namespace exists in env.yaml and if so, use it

Let me turn this into user story
User Story

as odo user I want to use my own namespace and not the namespace. (If I git clone repository with devfile.yaml I should not be forced to use namespace that is defined in devfile.yaml)
as odo user that works on two separate components in different projects, I don't want to be forced to always switch namespaces using kubectl or oc. Odo should remember the correct namespace.
This is an example of a bad experience:cd mycomponent1
kubectl config set-context --current --namespace=project1
odo push

cd mycomponent2
kubectl config set-context --current --namespace=project2
odo push

Acceptance criteria

if the project is not set in env.yaml or --project flag is not used odo push should work against the current namespace as defined in KUBECONFIG
if --project  flag for odo push is  set, use the project specified by the flag
odo config set project <project name> should save the project name in the environment-specific config file (env.yaml)
if odo push is executed and there is a project set in env.yaml the project from env.yaml should be used
if both --project flag and project in env.yaml are set the flag has priority

Based on the design discussion, we are using --project instead of --namespace for the command to make it consistent with the odo s2i scenario.  The value that we store in the env.yaml will continue to use namespace since the eventual goal is to turn the command later to use --namespace in the future.


NPM Is Out Of Date

NPM is 2.0.2. The version here is 2.0.3.

Hello @ewwwgiddings,
Thank you for your interest in working with our products, this issue is solved in the latest version (v2.0.4).
All the best,
Stefan


Add GitHub auth

PR Description 📜

Fixes #163 #168

Type of Change

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

Changes

Add GitHub Auth
Run eslint through Prettier to fix whitespaces and semicolons
fix dependencies by running npm audit

[x] I follow CONTRIBUTING GUIDELINE & CODE OF CONDUCT of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I have followed proper naming convention showed in CONTRIBUTING GUIDELINE
[x] I have added screenshot for website preview in assets/images
[x] I have added README.md in my folder

Add your screenshots(Optional) 📸
Github authentication(you can see your name and profile pic)

Thank you soo much for contributing to our repository 💗

@trishanu-init Kindly follow these instructions to create your own github app
https://authjs.dev/guides/configuring-github#registering-your-app

@trishanu-init Even after merging this branch with main, I don't see any changes on the website.


AIX test failure on JDK8 - java/lang/ClassLoader/Assert.java.Assert

Failed
java/lang/ClassLoader/Assert.java.Assert (from java_lang_ClassLoader_Assert.java)
Execution failed: exit code 1
This was running on Adopt as well as hyc-runtimes-jenkins.swg-devops.com, and still same failures.
SDK Url ; https://github.com/AdoptOpenJDK/openjdk8-binaries/releases/download/jdk8u-2019-03-11-11-19/OpenJDK8U-jdk_ppc64_aix_openj9_2019-03-11-11-19.tar.gz
https://hyc-runtimes-jenkins.swg-devops.com/view/Test_grinder/job/Grinder/1770/parameters/

I will request to exclude this test to make the AIX build green.

Thanks for looking at these @archanaNogriya
Some triage suggestions:

it will be more useful to paste the console output, as Jenkins jobs are transient (and especially in the case of internal job links):

10:29:16 TEST: java/lang/ClassLoader/Assert.java
10:29:16 TEST JDK: /home/jenkins/workspace/Grinder/openjdkbinary/j2sdk-image/jre/bin/../..
10:29:16
10:29:16 ACTION: shell -- Failed. Execution failed: exit code 1
10:29:16 REASON: User specified action: run shell/timeout=300 Assert.sh
10:29:16 TIME:   0.041 seconds
10:29:16 messages:
10:29:16 command: shell Assert.sh
10:29:16 reason: User specified action: run shell/timeout=300 Assert.sh
10:29:16 elapsed time (seconds): 0.041
10:29:16 STDOUT:
10:29:16 Unrecognized system!
10:29:16 STDERR:
10:29:16 rerun:
10:29:16 cd /home/jenkins/workspace/Grinder/jvmtest/openjdk_regression/work/scratch &&
10:29:16 HOME=/home/jenkins
10:29:16 LANG=en_US
10:29:16 PATH=/bin:/usr/bin
10:29:16 TZ=America/Toronto
10:29:16 TESTSRC=/home/jenkins/workspace/Grinder/openjdk-tests/openjdk_regression/openjdk-jdk/jdk/test/java/lang/ClassLoader
10:29:16 TESTSRCPATH=/home/jenkins/workspace/Grinder/openjdk-tests/openjdk_regression/openjdk-jdk/jdk/test/java/lang/ClassLoader
10:29:16 TESTCLASSES=/home/jenkins/workspace/Grinder/jvmtest/openjdk_regression/work/classes/java/lang/ClassLoader
10:29:16 TESTCLASSPATH=/home/jenkins/workspace/Grinder/jvmtest/openjdk_regression/work/classes/java/lang/ClassLoader
10:29:16 COMPILEJAVA=/home/jenkins/workspace/Grinder/openjdkbinary/j2sdk-image/jre/bin/../..
10:29:16 TESTJAVA=/home/jenkins/workspace/Grinder/openjdkbinary/j2sdk-image/jre/bin/../..
10:29:16 TESTVMOPTS='-ea -esa -Xmx512m -Xcompressedrefs'
10:29:16 TESTTOOLVMOPTS='-J-ea -J-esa -J-Xmx512m -J-Xcompressedrefs'
10:29:16 TESTJAVACOPTS=
10:29:16 TESTJAVAOPTS=
10:29:16 TESTTIMEOUTFACTOR=8.0
10:29:16 TESTROOT=/home/jenkins/workspace/Grinder/openjdk-tests/openjdk_regression/openjdk-jdk/jdk/test
10:29:16 FS=/
10:29:16 PS=:
10:29:16 NULL=/dev/null
10:29:16     sh
10:29:16         /home/jenkins/workspace/Grinder/openjdk-tests/openjdk_regression/openjdk-jdk/jdk/test/java/lang/ClassLoader/Assert.sh
10:29:16
10:29:16 TEST RESULT: Failed. Execution failed: exit code 1
10:29:16 --------------------------------------------------
10:38:54 Test results: passed: 428; failed: 1
10:39:01 Report written to /home/jenkins/workspace/Grinder/jvmtest/openjdk_regression/report/html/report.html
10:39:01 Results written to /home/jenkins/workspace/Grinder/jvmtest/openjdk_regression/work
10:39:01 Error: Some tests failed or other problems occurred.
10:39:01
10:39:01 jdk_lang_0_FAILED
It will be good if you can take a look at the code for Assert.sh, to see what would cause the test to hit the "Unrecognized system!" output.

As this is an openjdk test case, follow the guidance in https://github.com/AdoptOpenJDK/openjdk-tests/wiki/Guidance-for-Creating-OpenJDK-Test-Defects to check if this is an known defect.  If so, the exclude you will create, should link to the jbs defect.

Already reported:
java/lang/ClassLoader/Assert.sh https://bugs.openjdk.java.net/browse/JDK-8037013

JDK-8037013 is marked as resolved, should see why we do not have the fix, if that is the case, does it need to be ported elsewhere?

If it was not found in JBS as already reported, you could check if this fails for both vm implementations (openj9 & hotspot), if only openj9, then you would open an openj9 defect and use the openj9 issue link in your exclude.

Should verify if this is resolved or not: https://github.com/adoptium/aqa-tests/blob/master/openjdk/excludes/ProblemList_openjdk8-openj9.txt#L27

Error message Unrecognized system! JBS https://bugs.openjdk.org/browse/JDK-8037013, fixed in jdk9 and up. Not backport to jdk8. Apply the change and run in grinder https://ci.adoptium.net/view/Test_grinder/job/Grinder/11384/  - passed.
Solutions

Help backport from upstream or
Label as won't fix and keep the test excluded.

@smlambert which would you prefer?

Let's take the general approach to always prefer fixing issues over excluding test cases (when possible / when a backport would be accepted).  If backport not possible or accepted, I am fine with moving it to a permanent exclusion for this testcase.

Backport PR https://github.com/openjdk/jdk8u-dev/pull/604


chore(deps): update yarn to v4

This PR contains the following updates:

Package
Type
Update
Change
Pending

yarn
packageManager
major
3.6.1 -> 4.0.0
4.0.2 (+1)

Release Notes

yarnpkg/berry
v4.0.0
Compare Source
Major Changes

With Node.js 16's now being End of Life'd, we dropped support for Node.js versions lower than 18.12.

Some important defaults have changed:

yarn init and yarn set version will prefer using packageManager rather than yarnPath when possible (when they detect COREPACK_ROOT in your environment variables).

yarn init will no longer use zero-install by default. You still can enable it, but it should make it easier to start one-of projects without having to rewrite the configuration afterwards.

As a result, enableGlobalCache now defaults to true. If your project uses Zero-Installs, the first yarn install you run after migrating to 4.0 will automatically set enableGlobalCache: false in your local .yarnrc.yml.

yarn workspaces foreach now requires one of --all, --recursive, --since, or --worktree to be explicitly specified; the previous default was --worktree, but it was rarely what users expected.

compressionLevel now defaults to 0 rather than mixed. It's been proved significantly faster on installs, and the size impact was reasonable enough to change the default. Note that it benefits you even if you use Zero-Installs: as per our tests, a zero-compression is actually easier to handle for Git (you can see by yourself with those examples using compressionLevel: 0 vs compressionLevel: mixed).

To avoid making the upgrade too disruptive, Yarn will check whether Zero-Installs are enabled the first time you run yarn install after migrating from 3.6 to 4.0. If you do, it will automatically set the old default (compressionLevel: mixed) in your .yarnrc.yml file. You can then remove it whenever you feel ready to actually change the compression settings.

All official Yarn plugins are now included by default in the bundle we provide. You no longer need to run yarn plugin import for official plugins (you still need to do it for third-party plugins, of course).

This doesn't change anything to the plugin API we provide, which will keep being maintained.
Yarn still has a modular architecture and uses the exact same APIs as contrib plugins; all that changes is how we distribute our own features.

Yarn's UI during installs has been greatly improved:

Packages added and removed from the lockfile are now explicitly reported.
Fluctuations in the project cache size are now reported as a single line.
Unactionable warnings (node-gyp and transitive peer dependency errors) have been removed.
Skipped builds are now only reported during initial installs and manual yarn rebuild calls.
The Yarn version is now displayed on installs to help us investigate issues when reported as screenshots.
Deprecation checks have been moved to yarn npm audit.

Some settings were renamed or removed:

caFilePath is now httpsCaFilePath
preferAggregateCacheInfo has been removed (it's now always on)
pnpDataPath has been removed to adhere to our new PnP specification. For consistency, all PnP files will now be hardcoded to a single value so that third-party tools can implement the PnP specification without relying on the Yarn configuration.

The yarn npm audit command has been reimplemented:

The audit registry must now implement the /-/npm/v1/security/advisories/bulk endpoint.
The npmAuditRegistry can be used to temporarily route audit queries to the npm registry.
Deprecations are now returned by default. To silence them, use yarn npm audit ! --no-deprecations.

Some legacy layers have been sunset:

Plugins cannot access the Clipanion 2 APIs anymore (upgrade to Clipanion 3)
Plugins cannot access the internal copy of Yup anymore (use Typanion instead)
Yarn will no longer remove the old Yarn 2.x .pnp.js file when migrating.
The --assume-fresh-project flag of yarn init has been removed.

API Changes
The following changes only affect people writing Yarn plugins:

The ZipFS and ZipOpenFS classes have been moved from @yarnpkg/fslib to @yarnpkg/libzip. They no longer need or accept the libzip parameter.

Reading the zip archives is now done on the Node.js side for performance; as a result, the open, ZIP_CREATE, and ZIP_TRUNCATE bindings are no longer needed for ZipFS and have also been removed.

The dependencies field sent returned by Resolver#resolve must now be the result of a Configuration#normalizeDependencyMap call. This change is prompted by a refactoring of how default protocols (ie npm:) are injected into descriptors. The previous implementation caused various descriptors to never be normalized, which made it difficult to know what were the descriptors each function should expect.

Similarly, the descriptors returned by Resolve#getResolutionDependencies are now expected to be the result of Configuration#normalizeDependency calls.

Note that this only applies to the dependencies field; the peerDependencies field is unchanged, as it must only contains semver ranges without any protocol (with an exception for workspace:, but that's not relevant here).

The Resolve#getResolutionDependencies function must now return an object of arbitrary string keys and descriptor values (instead of a map with DescriptorHash keys). Those descriptors will be resolved and assigned to the same keys as the initial object. This change allows resolvers to wrap resolution dependencies from other resolvers, which wasn't possible before since it'd have caused the key to change.

The generateLoader function in @yarnpkg/pnp no longer generates the $$SETUP_STATE function, it now needs to be present in the loader passed to the function.

The getCustomDataKey function in Installer from @yarnpkg/core has been moved to Linker.

renderForm's options argument is now required to enforce that custom streams are always specified.

npmConfigUtils.getAuditRegistry no longer takes a Manifest as its first argument.

The FetchOptions.skipIntegrityCheck option has been removed. Use FetchOptions.cacheOptions.skipIntegrityCheck instead.

MapConfigurationValue has been removed. Use miscUtils.ToMapValue instead.

Manifest.isManifestFieldCompatible and Manifest.prototype.isCompatibleWith{OS,CPU} have been removed. Use Manifest.prototype.getConditions and structUtils.isPackageCompatible instead.

versionUtils.{fetchBase,fetchRoot,fetchChangedFiles} have been moved from @yarnpkg/plugin-version to @yarnpkg/plugin-git. Use gitUtils.{fetchBase,fetchRoot,fetchChangedFiles} instead.

For consistency reasons:

Link{Resolver,Fetcher} have been renamed to Portal{Resolver,Fetcher}
RawLink{Resolver,Fetcher} have been renamed to Link{Resolver,Fetcher}

FakeFS classes are now required to implement lutimes{Sync,Promise}.

workspace.dependencies has been removed. Use workspace.anchoredPackage.dependencies instead.

The Installer class must now return BuildRequest structures instead of BuildDirective[]. This lets you mark that the build must be skipped, and the reason why.

startCacheReport has been removed, and is now part of the output generated by fetchEverything.

forgettableNames & forgettableBufferSize have been removed (the only messages using them have been removed, making the forgettable logs implementation obsolete).

workspace.locator has been removed. You can instead use:

workspace.anchoredLocator to get the locator that's used throughout the dependency tree.
workspace.manifest.version to get the workspace version.

configuration.{packageExtensions,refreshPackageExtensions} have been removed. Use configuration.getPackageExtensions instead.

configuration.normalizePackage now requires a packageExtensions option.

ProjectLookup has been removed. Both Configuration.find and Configuration.findProjectCwd now always do a lockfile lookup.

Installs

Yarn now caches npm version metadata, leading to faster resolution steps and decreased network data usage.
The pnpm linker avoids creating symlinks that lead to loops on the file system, by moving them higher up in the directory structure.
The pnpm linker no longer reports duplicate "incompatible virtual" warnings.

Features

enableOfflineMode is a new setting that, when set, will instruct Yarn to only use the metadata and archives already stored on the local machine rather than download them from the registry. This can be useful when performing local development under network-constrained environments (trains, planes, ...).
yarn run bin now injects the environment variables defined in .env.yarn when spawning a process. This can be configured using the injectEnvironmentFiles variable.
yarn workspaces foreach now automatically enables the yarn workspaces foreach ! --verbose flag in interactive terminals.
Constraints can now be written in JavaScript. See the revamped documentation for more information.

Bugfixes

yarn dlx will no longer report false-positive UNUSED_PACKAGE_EXTENSION warnings
yarn workspace will now set $INIT_CWD to the CLI working directory rather than the workspace root.

Shell

The builtin shell now supports whitespace-only commands.

Compatibility

The patched filesystem now supports FileHandle.readLines.
PnP now reports missing files when in watch mode.

v3.7.0
Compare Source
v3.6.4
Compare Source
v3.6.3
Compare Source
v3.6.2
Compare Source

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, click this checkbox.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update artifacts related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you click the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: yarn.lock
installing v2 tool corepack v0.23.0
npm WARN EBADENGINE Unsupported engine {
npm WARN EBADENGINE   package<EMAIL_ADDRESS>npm WARN EBADENGINE   required: { node: '>=18.17.1' },
npm WARN EBADENGINE   current: { node: 'v16.18.0', npm: '8.19.2' }
npm WARN EBADENGINE }

added 1 package in 276ms
linking tool corepack v0.23.0
0.23.0
Installed v2 /usr/local/buildpack/tools/v2/corepack.sh in 1 seconds
skip cleanup, not a docker build: 55cc3e608e48
Usage Error: This tool requires a Node version compatible with >=18.12.0 (got 16.18.0). Upgrade Node, or set `YARN_IGNORE_NODE=1` in your environment.

Yarn Package Manager - 4.0.0

  $ yarn <command>

You can also print more details about any of these commands by calling them with
the `-h,--help` flag right after the command name.

File name: package.json
Command failed: yarn run allow-scripts auto


give_item() reliably crashes client in windows

This happens reliably on current development head (@7485437b509f910fdd08336d770c8096e3d22c60), but not in master (@911053f767d328fcf14392146cb3ccba78d98795)
http://i.imgur.com/biczpuB.png
Here's the relevant bit of starbound.log:
Info: UniverseClient: Client disconnecting...
Warn: Perf: StarApplicationBase::run.innerLoop millis: 1784
Info: UniverseClient: Client disconnecting...
 (2)
  00402028 (/Users/builder/starbound-slave/releasebuilder-windows/build/source/client/StarClientApplication.cpp:780)
  0040AAFD (/Users/builder/starbound-slave/releasebuilder-windows/build/source/application/StarApplicationBase.cpp:212)
  00407E74 (/Users/builder/starbound-slave/releasebuilder-windows/build/source/client/main.cpp:38)
  004EC0C1 (\SDL-1.2.15/./src/main/win32/SDL_win32_main.c:318)

and from debug.log from StarryPy
014-02-11 08:54:15,296 - starrypy - DEBUG - Reaping dead connections.
2014-02-11 08:54:15,298 - starrypy - DEBUG - No connections reaped.
2014-02-11 08:54:15,298 - starrypy - DEBUG - Factory created, endpoint of port 21025
2014-02-11 08:54:15,298 - starrypy - DEBUG - Attempting to listen on TCP port 21025
2014-02-11 08:54:15,309 - starrypy - INFO - Listening on port 21025
2014-02-11 08:54:25,296 - starrypy - DEBUG - Reaping dead connections.
2014-02-11 08:54:25,296 - starrypy - DEBUG - No connections reaped.
2014-02-11 08:54:35,296 - starrypy - DEBUG - Reaping dead connections.
2014-02-11 08:54:35,296 - starrypy - DEBUG - No connections reaped.
2014-02-11 08:54:45,296 - starrypy - DEBUG - Reaping dead connections.
2014-02-11 08:54:45,296 - starrypy - DEBUG - No connections reaped.
2014-02-11 08:54:55,296 - starrypy - DEBUG - Reaping dead connections.
2014-02-11 08:54:55,296 - starrypy - DEBUG - No connections reaped.
2014-02-11 08:55:03,177 - starrypy - DEBUG - Building protocol to address IPv4Address(TCP, '<IP_ADDRESS>', 61174)
2014-02-11 08:55:03,177 - starrypy - INFO - Connection established from IP: <IP_ADDRESS>
2014-02-11 08:55:03,197 - starrypy - DEBUG - Client protocol instantiated.
2014-02-11 08:55:04,381 - starrypy.plugins.player_manager - INFO - Player Slitherrr (UUID: ac8ac8ac8ac8ac8ac8acac88, IP: <IP_ADDRESS>) logged in
2014-02-11 08:55:04,414 - starrypy.utility_functions - DEBUG - Giving item coalore (count: 200) to Slitherrr
2014-02-11 08:55:04,421 - starrypy.utility_functions - DEBUG - Giving item alienburger (count: 5) to Slitherrr
2014-02-11 08:55:04,428 - starrypy - DEBUG - Sent chat message with text: Welcome to the server! Here are some starter items to get you off to a good start.
2014-02-11 08:55:04,450 - starrypy.plugins.new_player_greeter_plugin - INFO - Gave starter items to Slitherrr.
2014-02-11 08:55:04,457 - starrypy - DEBUG - Sent chat message with text: Message of the Day:
2014-02-11 08:55:04,463 - starrypy - DEBUG - Sent chat message with text: Welcome to the server! Play nice.
2014-02-11 08:55:04,474 - starrypy - DEBUG - Sent chat message with text: ^#F7434C;Slitherrr^#F7EB43; joined.
2014-02-11 08:55:06,469 - starrypy.plugins.player_manager - INFO - Player Slitherrr is now on a ship.
2014-02-11 08:55:06,493 - starrypy.plugins.player_manager - INFO - Player disconnected: Slitherrr
2014-02-11 08:55:06,528 - starrypy - DEBUG - Sent chat message with text: ^#F7434C;Slitherrr^#F7EB43; left.
2014-02-11 08:55:06,542 - starrypy - DEBUG - Sent chat message with text: ^#F7434C;Slitherrr^#F7EB43; left.
2014-02-11 08:55:06,546 - starrypy - DEBUG - Reaping dead connections.
2014-02-11 08:55:06,546 - starrypy - DEBUG - No connections reaped.
2014-02-11 08:55:06,869 - starrypy - INFO - Losing connection from IP: <IP_ADDRESS>
2014-02-11 08:55:06,892 - starrypy - DEBUG - Sent chat message with text: ^#F7434C;Slitherrr^#F7EB43; left.
2014-02-11 08:55:15,296 - starrypy - DEBUG - Reaping dead connections.
2014-02-11 08:55:15,296 - starrypy - DEBUG - No connections reaped.
2014-02-11 08:55:25,296 - starrypy - DEBUG - Reaping dead connections.
2014-02-11 08:55:25,296 - starrypy - DEBUG - No connections reaped.
2014-02-11 08:55:35,296 - starrypy - DEBUG - Reaping dead connections.
2014-02-11 08:55:35,296 - starrypy - DEBUG - No connections reaped.
2014-02-11 08:55:45,296 - starrypy - DEBUG - Reaping dead connections.
2014-02-11 08:55:45,296 - starrypy - DEBUG - No connections reaped.
2014-02-11 08:55:49,292 - starrypy.config.ConfigurationManager - DEBUG - Writing configuration file.
2014-02-11 08:55:49,299 - starrypy.plugins.new_player_greeter_plugin - DEBUG - new_player_greeter_plugin plugin object deactivated
2014-02-11 08:55:49,299 - starrypy.plugins.user_management_commands - DEBUG - user_management_commands plugin object deactivated
2014-02-11 08:55:49,299 - starrypy.plugins.udp_forwarder - DEBUG - udp_forwarder plugin object deactivated
2014-02-11 08:55:49,299 - starrypy.plugins.colored_names_plugin - DEBUG - colored_names_plugin plugin object deactivated
2014-02-11 08:55:49,299 - starrypy.plugins.admin_messenger - DEBUG - admin_messenger plugin object deactivated
2014-02-11 08:55:49,299 - starrypy.plugins.bouncer - DEBUG - bouncer plugin object deactivated
2014-02-11 08:55:49,299 - starrypy.plugins.motd_plugin - DEBUG - motd_plugin plugin object deactivated
2014-02-11 08:55:49,299 - starrypy.plugins.warpy_plugin - DEBUG - warpy_plugin plugin object deactivated
2014-02-11 08:55:49,299 - starrypy.plugins.plugin_manager - DEBUG - plugin_manager plugin object deactivated
2014-02-11 08:55:49,301 - starrypy.plugins.chat_logger - DEBUG - chat_logger plugin object deactivated
2014-02-11 08:55:49,301 - starrypy.plugins.command_dispatcher - DEBUG - command_dispatcher plugin object deactivated
2014-02-11 08:55:49,301 - starrypy.plugins.planet_protect - DEBUG - planet_protect plugin object deactivated
2014-02-11 08:55:49,301 - starrypy.plugins.announcer_plugin - DEBUG - announcer_plugin plugin object deactivated
2014-02-11 08:55:49,301 - starrypy.plugins.starbound_config_manager - DEBUG - starbound_config_manager plugin object deactivated
2014-02-11 08:55:49,301 - starrypy.plugins.mute_manager - DEBUG - mute_manager plugin object deactivated

This is almost certainly related to the timing of the call--if I move give_items() into an "on_chat_sent" handler (and then send a chat), the crash doesn't happen.

Please verify this still occurs with protocol 691 and either reopen this issue or create a new one. Closing #99.


Can cipher_stream structs be made compatible with Send?

I'd like to be able to pass an EncryptionStream to a thread that pumps bytes from a source into an encrypted sink, and similar for DecryptionStream. But these structs are !Send, so I can't. Can they be marked Send using unsafe, or reconfigured in some way to allow it using safe Rust?

Good to know, thank you! I'm still very much a beginner and so I don't know if I could make a good PR for this, but in a pinch I can mark my container for the cipher_stream as Send, using unsafe.

Fair enough! I'll get to this in May in that case :)


M2 FireCuda 530 Not Detected on Synology DS923+

Hello,
I'm experiencing an issue where my M2 storage FireCuda 530 is not being detected on my Synology DS923+, currently running DSM 7.2.0.
Ive executing the script here's the result :

I reboot but still not working, It only detected my SSD SATA :

Did storage manager show the NVMe drive before you ran the script?

Actually, everything was working perfectly on DSM version 7.1.1, but then I updated DSM to its latest version and it started saying that the M2 disk was unknown. I completely formatted my DSM and now I realize it no longer detects my M2 disk even before running the script, and even after running the script, the disk remains undetectable. I suspect it might be due to the latest DSM version 7.1.2, but I'm not certain.

Schedule syno_hdd_db.sh to run the with -n option at startup as root: /volume1/test/syno_hdd_db.sh -n
https://github.com/007revad/Synology_HDD_db/blob/main/how_to_schedule.md
Then reboot. If the NVMe drive is still missing, reboot again.

I've scheduled the script and restart multiple times, but I still can't see my disk appearing.

Make sure the only script scheduled to run at boot is syno_hdd_db.sh -n
Then remove the NVMe drive. Reboot the NAS.  Then boot the NAS.
While the NVMe drive is out of the NAS you could delete all the partitions that are on it (if you can connect it to a computer).

I followed the procedure but the disk is still not found on DSM.
I formatted the disk and deleted all the partitions, but it didn't help. The only script scheduled to run at boot is syno_hdd_db.sh -n.
Despite these steps, the disk remains undetected on DSM.

Can you run this script and reply with a screenshot of the output: https://github.com/007revad/Synology_HDD_db/blob/test/nvme_check.sh

Here's the result :
/volume1/Scripts$ sudo ./nvme_check.sh
Password:
DS923+
DSM 7.2.1-69057 Update 5
2024-06-02 11:50:29
Checking support_m2_pool setting
/etc.defaults/synoinfo.conf: yes
/etc/synoinfo.conf:          yes
Checking supportnvme setting
/etc.defaults/synoinfo.conf: yes
/etc/synoinfo.conf:          yes
Checking synodisk --enum -t cache
Checking syno_slot_mapping
System Disk
Internal Disk
01: /dev/sata1
02:
03:
04:
05:
06:
07:
08:
09:
10:
11:
12:
13:
14:
15:
16:
Esata port count: 0
USB Device
01:
02:
03:
04:
05:
06:
07:
08:
09:
10:
11:
12:
13:
14:
15:
16:
17:
18:
Internal SSD Cache:
01:

Checking udevadm nvme paths
nvme0: /devices/pci0000:00/0000:00:1d.0/0000:6d:00.0/nvme/nvme0
Checking if nvme drives are detected with synonvme
nvme0: It is a NVMe SSD
nvme0: Vendor name: Seagate
nvme0: Model name: Seagate FireCuda 530 ZP2000GM30
Checking nvme drives in /run/synostorage/disks
Checking nvme block devices in /sys/block
nvme0n1
Checking logs
Current date/time:   2024-06-02 11:50:29
Last boot date/time: 2024-06-02 11:46:07

Your NVMe drive is missing in syno_slot_mapping and /run/synostorage/disks. If I remember correctly this can be caused by the device tree blob (model.dtb) not containing the correct nvme information, or it's missing the power_limit which Synology added in DSM 7.2.1 Update 1.
Someone else has 2 NVMe drives that DSM is not seeing and they're sending those NVMe drives to me so I can work out why DSM is not seeing them.
You could reinstall DSM 7.2.1 which will restore any corrupt or missing files. It's no different than doing a DSM update.

Disable the syno_hdd_db schedule.
Run https://github.com/007revad/Synology_DSM_reinstall
Manually install https://global.synologydownload.com/download/DSM/release/7.2.1/69057-1/DSM_DS923%2B_69057.pat
DSM will automatically update itself to DSM 7.2.1 update 5.
Check if the drive shows in storage manager as a M.2 Cache drive.

I followed the steps exactly as described, and it successfully reinstalled DSM. However, when I go to Storage Manager, nothing is displayed.

Is it possible to downgrade to version 7.1.1 to confirm that the problem is with the new version ?

You can downgrade to 7.1.1 but it's not easy. And you lose all the data on the drives.

Remove the existing drives.
Insert any old spare HDD.
Boot the DS923+.
Use Synology Assistant to find the DS923+
Do the initial setup process.

Then see if you can downgrade to DSM 7.1.1
I'd follow these steps https://www.blackvoid.club/dsm-7-to-dsm-6-downgrade/ but modify them for 7.2 to 7.1.1
In steps 3 and 5 change the contents of the VERSION file to this:
majorversion="7"
minorversion="1"
major="7"
minor="1"
micro="0"
productversion="7.1"
buildphase="GM"
buildnumber="42661"
smallfixnumber="0"
nano="0"
base="42661"
builddate="2022/04/01"
buildtime="17:48:27"

In step 5 if the Telnet password is not 101-0101 you can generate the DSM telnet 'password of the day' with the following on any computer that can run bash:
#!/bin/bash

# Get current month and day
month=$(date +%m) # Month (01 to 12)
day=$(date +%d) # Day of the month (01 to 31)

# Function to calculate greatest common divisor in Bash
gcd(){
    # $1 decimal month as decimal
    # $2 decimal day as decimal
    if [ $2 -eq 0 ]; then
        echo $1
    else
        gcd $2 $(($1 % $2))
    fi
}

# Calculate greatest common divisor between month and day
gcd_result=$(gcd $month $day)

# Format and print the password
printf "Password for today is: %x%02d-%02x%02d\n\n" $month $month $day $gcd_result

Or if you prefer python: https://blog.thomasmarcussen.com/synology-nas-recovery-password-telnet/
In step 6 use this pat file: https://global.synologydownload.com/download/DSM/release/7.1.1/42962/DSM_DS923%2B_42962.pat

Hello sorry for the delay.
I downgraded to version 7.1.1 and it actually works well :

Weird that the M.2 drive isn't detected by DSM 7.2.1 but is in DSM 7.1.1


Not working credentials

PluginProxy credentials are not working, asking to for credentials again
//Not working
const [page] = await browser.pages()
//Working
const page = await browser.newPage()

I can confirm, same issue


The action sometimes fails installing some java version

Description:
Im using the action to install java 8.0.275 for compilation, and it fails for some tests but succeeds for others, moreover if I rerun the failed tests it sometimes succeeds.
Task version:
v3
Platform:

[X] Ubuntu
[ ] macOS
[ ] Windows

Runner type:

[x] Hosted
[ ] Self-hosted

Repro steps:
A description with steps to reproduce the issue. If your have a public example or repo to share, please provide the link.
Expected behavior:
No failure in installation.
Actual behavior:
Installed distributions
  Trying to resolve the latest version from remote
  Error: Could not find satisfied version for SemVer '8.0.275'.
   Thank you for your report. Could you please provide a link to a public repository to reproduce the issue. Besides, which distribution do you use ?

@dmitry-shibanov Unfortunately I don't have a public repository to share, but I can share the config.
 - name: Install Java for compilation (8.0.272)
        uses: actions/setup-java@v3
        with:
          java-version: 8.0.272
          java-package: jdk
          distribution: adopt-hotspot
          architecture: x64

Also seeing this on v2

@allen-branch There is some bug that makes it fail some times

Hello @uriariel. Does the issue reproduce? Could you please try to switch to v3 tag ?


targeted ic-confirm on elements parent

There is a list of items, every single item can be edited or removed. E.g.:

        Item 1
       Edit
       Delete

...

Is there a way to trigger confirmation only for delete action?
Is there a way to integrate libs like bootboxjs in easy way?
Thanks in advance.

You'll have to inline it on the delete links....
On January 29, 2017 at 8:03:28 AM, ygwain<EMAIL_ADDRESS>wrote:
There is a list of items, every single item can be edited or removed. E.g.:

        Item 1
       Edit
Delete

...

Is there a way to trigger confirmation only for delete action?
Is there a way to integrate libs like bootboxjs in easy way?
Thanks in advance.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/LeadDyno/intercooler-js/issues/161, or mute the thread
https://github.com/notifications/unsubscribe-auth/AAcov21oS99TwGcLtGoT0b7lybO7pw7Qks5rXLhKgaJpZM4Lw05m
.


ES6ify connect

This replaces #47
No functional changes, just syntax sugar and move finalMapToComputed/finalDispatchToActions to default args.

Also, handleChange is moved to an anonymous function.  I can undo that part if handleChange is considered public API.


Dev dependency updates

Codecov Report
Attention: Patch coverage is 50.00000% with 1 line in your changes missing coverage. Please review.

Project coverage is 71.17%. Comparing base (b115370) to head (7e45ead).

Files
Patch %
Lines

src/Application/Security/Password.php
50.00%
1 Missing :warning:

Additional details and impacted files
@@            Coverage Diff             @@
##             develop     #135   +/-   ##
==========================================
  Coverage      71.17%   71.17%
  Complexity       238      238
==========================================
  Files             38       38
  Lines            902      902
==========================================
  Hits             642      642
  Misses           260      260

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Boxes with versions do not get removed

Issue
Need to have vagrant-nuke respect aka destroy all versioned boxes.

fixed with v0.0.5


[cmake] Using Protobuf v27 make python pybind11 test failed

Tests impacted
here the list of impacted tests...
To test:
cmake -S. -Bbuild -DBUILD_PYTHON=ON -DBUILD_CXX_SAMPLES=OFF -DBUILD_CXX_EXAMPLES=OFF
cmake --build build -j 8
(cd build && ctest -R "python_")
...
96% tests passed, 13 tests failed out of 332

Total Test time (real) = 349.67 sec

The following tests FAILED:
	11 - python_pdlp_pdlp_test (Subprocess aborted)
	14 - python_routing_model_test (Subprocess aborted)
	19 - python_scheduling_rcpsp_test (Subprocess aborted)
	21 - python_math_opt_solver_test (Subprocess aborted)
	170 - python_math_opt_advanced_linear_programming (Subprocess aborted)
	171 - python_math_opt_basic_example (Subprocess aborted)
	172 - python_math_opt_cutting_stock (Subprocess aborted)
	173 - python_math_opt_integer_programming (Subprocess aborted)
	174 - python_math_opt_linear_programming (Subprocess aborted)
	175 - python_math_opt_linear_regression (Subprocess aborted)
	176 - python_math_opt_time_indexed_scheduling (Subprocess aborted)
	178 - python_pdlp_simple_pdlp_program (Subprocess aborted)
	439 - python_python_rcpsp_sat (Subprocess aborted)
Errors while running CTest
Output from these tests are in: /usr/local/google/home/corentinl/work/main/build/Testing/Temporary/LastTest.log
Use "--rerun-failed --output-on-failure" to re-run the failed cases verbosely.

note: using Protobuf  58baeb4c3b664f8918d24cef5151083d9da9767c everything pass...
Regression seem to have been introduced by http://cl/602725967
Investigation
Testing one broken test
cmake -S. -Bbuild -DBUILD_PYTHON=ON -DBUILD_CXX_SAMPLES=OFF -DBUILD_CXX_EXAMPLES=OFF
cmake --build build -j 8
source build/python/venv/bin/activate
python ortools/routing/python/model_test.py

Trace:
Running tests under Python 3.12.2: /usr/local/google/home/corentinl/work/main/build/python/venv/bin/python
[ RUN      ] ModelTest.testConstantDimensionTSP
[       OK ] ModelTest.testConstantDimensionTSP
[ RUN      ] ModelTest.testCtor
<ortools.routing.python.model.RoutingModel object at 0x7faea8f9d4b0>
[       OK ] ModelTest.testCtor
[ RUN      ] ModelTest.testDimensionTSP
[       OK ] ModelTest.testDimensionTSP
[ RUN      ] ModelTest.testDimensionWithVehicleCapacitiesTSP
[       OK ] ModelTest.testDimensionWithVehicleCapacitiesTSP
[ RUN      ] ModelTest.testDimensionWithVehicleTransitsTSP
[       OK ] ModelTest.testDimensionWithVehicleTransitsTSP
[ RUN      ] ModelTest.testDimensionWithVehicleTransitsVRP
[       OK ] ModelTest.testDimensionWithVehicleTransitsVRP
[ RUN      ] ModelTest.testDisjunctionPenaltyTSP
[       OK ] ModelTest.testDisjunctionPenaltyTSP
[ RUN      ] ModelTest.testDisjunctionTSP
[       OK ] ModelTest.testDisjunctionTSP
[ RUN      ] ModelTest.testMatrixDimensionTSP
[       OK ] ModelTest.testMatrixDimensionTSP
[ RUN      ] ModelTest.testMatrixDimensionVRP
[       OK ] ModelTest.testMatrixDimensionVRP
[ RUN      ] ModelTest.testRoutingLocalSearchFiltering
First solution statistics:
                  | Time (s)
PATH_CHEAPEST_ARC | 3.3e-05
Local search filter statistics (PATH_CHEAPEST_ARC):
                      |     Calls |   Rejects | Time (s) | Rejects/s
VehicleVariableFilter |        12 |         0 | 8.3e-06  |       0
 VariableDomainFilter |        12 |         0 | 7.8e-06  |       0
                Total |        24 |         0 | 1.6e-05  |       0

[       OK ] ModelTest.testRoutingLocalSearchFiltering
[ RUN      ] ModelTest.testRoutingModelParameters
WARNING: All log messages before absl::InitializeLog() is called are written to STDERR
F0000 00:00:1720594007.067703 3589844 generated_message_reflection.cc:3620] Check failed: file != nullptr
*** Check failure stack trace: ***
Fatal Python error: Aborted

Current thread 0x00007faeaa0d0040 (most recent call first):
  File "/usr/local/google/home/corentinl/work/main/ortools/routing/python/model_test.py", line 650 in testRoutingModelParameters
  File "/usr/lib/python3.12/unittest/case.py", line 589 in _callTestMethod
  File "/usr/lib/python3.12/unittest/case.py", line 634 in run
  File "/usr/lib/python3.12/unittest/case.py", line 690 in __call__
  File "/usr/lib/python3.12/unittest/suite.py", line 122 in run
  File "/usr/lib/python3.12/unittest/suite.py", line 84 in __call__
  File "/usr/lib/python3.12/unittest/suite.py", line 122 in run
  File "/usr/lib/python3.12/unittest/suite.py", line 84 in __call__
  File "/usr/lib/python3.12/unittest/runner.py", line 240 in run
  File "/usr/local/google/home/corentinl/work/main/build/python/venv/lib/python3.12/site-packages/absl/testing/_pretty_print_reporter.py", line 82 in run
  File "/usr/lib/python3.12/unittest/main.py", line 281 in runTests
  File "/usr/lib/python3.12/unittest/main.py", line 105 in __init__
  File "/usr/local/google/home/corentinl/work/main/build/python/venv/lib/python3.12/site-packages/absl/testing/absltest.py", line 2653 in _run_and_get_tests_result
  File "/usr/local/google/home/corentinl/work/main/build/python/venv/lib/python3.12/site-packages/absl/testing/absltest.py", line 2689 in run_tests
  File "/usr/local/google/home/corentinl/work/main/build/python/venv/lib/python3.12/site-packages/absl/testing/absltest.py", line 2234 in main_function
  File "/usr/local/google/home/corentinl/work/main/build/python/venv/lib/python3.12/site-packages/absl/app.py", line 254 in _run_main
  File "/usr/local/google/home/corentinl/work/main/build/python/venv/lib/python3.12/site-packages/absl/app.py", line 308 in run
  File "/usr/local/google/home/corentinl/work/main/build/python/venv/lib/python3.12/site-packages/absl/testing/absltest.py", line 2236 in _run_in_app
  File "/usr/local/google/home/corentinl/work/main/build/python/venv/lib/python3.12/site-packages/absl/testing/absltest.py", line 2131 in main
  File "/usr/local/google/home/corentinl/work/main/ortools/routing/python/model_test.py", line 675 in <module>

Extension modules: google._upb._message (total: 1)
zsh: IOT instruction  python ortools/routing/python/model_test.py

https://github.com/google/or-tools/blob/f9adb26d1df687ce2362e864ee713f2db00897bc/ortools/routing/python/model_test.py#L648-L651

Protobuf Version
Python Test

v26.1
Pass

v27.0
Failed

v27.1
Failed

v27.2
Failed

continue to investigate...
ref: https://github.com/protocolbuffers/protobuf/blob/63def39e881afa496502d9c410f4ea948e59490d/src/google/protobuf/generated_message_reflection.cc#L3616-L3620

TLDR: using Protobuf (cmake based build) as a "Static" library will lead to an ODR violation, until now this ODR was without impact/side effect but the Protobuf change this behaviour amd make it crash the runtime.

Also seems to break fzn-cp-sat:
F0801 20:51:14.314146 2793569 generated_message_reflection.cc:3620] Check failed: file != nullptr

Fixed


Change generated polygon centroids label_placement to match vector tiles 1.0

When we release Mapzen vector tiles 1.0, we should change our synthesized polygon centroid features (enabled with generate_label_centroids on GeoJSON/TopoJSON sources) to match the new terminology:
Instead of label_placement = yes, it is now label_placement = true.

👍

I can change this. Should we accept both true and "yes" for backwards compatibility with a depreciation warning thrown when "yes" is used? Or just peel the bandaid off all at once?

Hmm, accepting both for backwards compatibility would be nice, but it would require special handling since this feature works by just generating new feature properties that are then filtered (with the filter) like any other... so it would need special-case code :/
We can probably get away with deprecating since this feature is not in heavy use yet.

@burritojustice

On Aug 8, 2016, at 07:49, Brett Camper<EMAIL_ADDRESS>wrote:
Hmm, accepting both for backwards compatibility would be nice, but it would require special handling since this feature works by just generating new feature properties that are then filtered (with the filter) like any other... so it would need special-case code :/
We can probably get away with deprecating since this feature is not in heavy use yet.
―
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

fine to rip off the bandaid, just a couple of instances (that I know) of that are easily changed.


Upgrade Available Button

Can you add to the wallet when a new version is available for download?
If you have time can you also make it so when you push the upgrade button it auto downloads and installs?  That might be asking to much?
Thanks again.

We have the "Help > Check for Updates" button in the menu bar as a first step, which when triggered, does check for updates and will allow you to automatically download new releases.
However, a design decision we made when starting this project was that the wallet itself would never connect to any server unless the user specifically asked it to (for security reasons). Having it automatically check and notify of updates goes against this design.
While it would be useful to automatically notify the user of upgrades, I'm not sure if we want to change our stance on this philosophy at this time.

All great points!  And I agree with that direction.  If you want you can remove this thread.


Converting project to use browserify and CommonJS for the structure/build

A bunch of folders have been converted to use require to get dependencies, and module.exports to export resources.
Building can be done by running npm run build and that should output to build/glam.js. Make sure to do an npm install before starting development for the first time, to install the dev dependencies. Currently the actual dependencies have not been added, and it might be a good idea to do that after everything has been converted to using CommonJS.
The build works by looking in src/index.js and then following require() calls to other files.
The final built file creates a global variable glam which is equal to the module.exports within src/index.js
Converted Folders:

animations
behaviours
cameras
controllers
core
events
graphics (It seems that there's a missing glam.Composer dependency here)

Hey it looks like you made the commits against master instead of the branch? Unless I am misreading this

Oh, it's master from my fork, but it'd be merged into browserify-build on in your version. Probably should have made a branch in my fork, too. :P

Cool - I guess this is a Github dumbass question then because I tried to figure out what branch it was forked from and couldn't. Any tips on how to do that?

Oh, I forked from master originally. Then I merged with your master in 6436bce, then I merged with your browserify-build branch in 7ce192c.

OK I'm going to assume that your PR won't clobber the current build system in master? I want to be sure about this before I switch everybody over (but especially myself ;->)

Yeah that worked - it's all in the branch. OK I'll test this out over the next day or so. In and out for the rest of the weekend. Thanks again!

No problem. Also, it doesn't really build anything usable for now. And probably won't until its all converted. :P

@RangerMauve Hey finally picking this up a year later :-) I fixed a trailing comma in the JSON (checked in) but the build gives me the errors below. Any clues?
$ npm run build

<EMAIL_ADDRESS>build /Users/Tony/dev/Github/glam
watchify ./ -o -s glam build/glam.js

You MUST specify an outfile with -o.
npm ERR! Darwin 14.5.0
npm ERR! argv "/usr/local/bin/node" "/usr/local/bin/npm" "run" "build"
npm ERR! node v4.2.2
npm ERR! npm  v3.3.12
npm ERR! code ELIFECYCLE
npm ERR<EMAIL_ADDRESS>build: watchify ./ -o -s glam build/glam.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script 'watchify ./ -o -s glam build/glam.js'.
npm ERR! Make sure you have the latest version of node.js and npm installed.
npm ERR! If you do, this is most likely a problem with the glam package,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR!     watchify ./ -o -s glam build/glam.js
npm ERR! You can get their info via:
npm ERR!     npm owner ls glam
npm ERR! There is likely additional logging output above.

My bad! I messed up setting up the auto-rebuild script. this line should be changed to
"watch": "watchify ./ -s glam -o  build/glam.js",


Hash partitioning not working

In brain image testing, hash partitioning shows issues when using two or more workers. For example, when setting the worker number to 2, worker 1 and worker 2 both have data from 10 sections, but we only have 10 sections in total. At the end, both workers cannot output any sections because neither of them have a complete section and they hold parts of each section.

I will take a look.


Cleanup patches for KW41Z IEEE 802.15.4 driver

Cleanup patches for KW41Z IEEE 802.15.4 driver.

Reuploaded


I can't achieve mAP (77.x)

I tried to run many times with different parameters. But I could not achieve the reported mAP (over 77%).
Almost mAP which I get are 71.x%.
Could you tell me how to set the training environment??
Thank you in advance.

@lesonly your mAP 71.x% that used pre-trained model or your own trained model?

@lesonly your mAP 71.x% that used pre-trained model or your own trained model?

Thank you for your reply! I use the weights of vgg16_reducedfc.pth，Does the pre-trained model mean the weight of vgg16?

i mean pre-trained model is ssd300_mAP_77.43_v2.pth this file and own trained model is using vgg16_reducedfc.pth to train from scratch

@lesonly i trained from scratch, but only get mAP about 0.45, and inference time is bigger than use ssd300_mAP_77.43_v2.pth to run eval.py


rename default file name

I guess main.yml is the default file of "include OS specific configuration",so I renamed it.
Another suggestion:
The default file should not contain any configuration, of course it's up to you.
If you agree with this, I will modify it

Is there any progress？

Thank you very much for your PR.
I have just transferred it to the main branch.

But it was not a good idea.
vars/main.yml is read in initially and thus defines all available variables, which are then overwritten by OS-specific ones if necessary.
vars/default.yml' was originally a fallback for an unsupported OS. I have now turned the PR back and removed the reference to defaults.yml`.

My original intention was to run it on centos.
But if it encounters an incompatible system, it will report an error on "include OS specific configuration".
I wish it could return an empty config if it encounters an unrecognized OS
like this:
- name: Fetch OS dependent variables
  include_vars:
    file: '{{ item }}'
    name: 'os_vars'
  with_first_found:
    - files:
        - '{{ ansible_facts.distribution }}_{{ ansible_facts.distribution_major_version }}.yml'
        - '{{ ansible_facts.distribution }}.yml'
        - '{{ ansible_facts.os_family }}_{{ ansible_facts.distribution_major_version }}.yml'
        - '{{ ansible_facts.os_family }}.yml'
      skip: true
  tags: always

In this case,if the file does not exist, the task will be skipped.but in your role ,it will report an error because 'lookup' will return an empty dict '[]'.

This role does not support CentOS ...
But you could create a suitable file under vars and define the required variables.

Thanks for your suggestion, my problem is solved


[Core HTTP] [App Config] No meaningful error thrown if deserialization went wrong

TO REPRO: https://github.com/HarshaNalluru/azure-sdk-for-js/pull/new/harshan/app-config/next-gen-error-repro

This is still 100% true for anything that uses OperationSpec - but realistically I don't think we could start throwing from core without a pretty major change. At this point I'd like us to wait for the new codegen that does not use OperationSpec for deserialization.


add support of modules with providers to MockBuilder factory parameters

v12.3.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.


Setup-Lab fails on Windows 2016

When performing Setup-Lab I receive the following error:
PSDesiredStateConfiguration\user : A duplicate resource identifier '[User]administrator' was found while processing
the specification for node 'Win10Ent'. Change the name of this resource so that it is unique within the node
specification.
At D:\autolab\Configurations\Windows10\VMConfiguration.ps1:49 char:10

     user $env:username {

     ~~~~

CategoryInfo          : InvalidOperation: (:) [Write-Error], ParentContainsErrorRecordException
FullyQualifiedErrorId : DuplicateResourceIdInNodeStatement,PsDesiredStateConfiguration\User

Compilation errors occurred while processing configuration 'AutoLab'. Please review the errors reported in error
stream and modify your configuration code appropriately
This is a fatal error and the VMs are not created.

This project is now under new ownership. The 3.x version line is obsolete. Version 4.0.0 has been published to the PowerShell Gallery with new updates, configuration, and documentation. It is expected that this version will resolve most if not all of the problems you were experiencing. Read Updating for more information.
No further action will be taken on this issue and it will most likely be closed at some point. If you still have the same issue with the new version, then go ahead and open a new issue.


Disallow setting of sort parameter as part of ResourceSyncParams

Describe the bug
Since the sync logic depends on sort by _lastUpdated field, we should disallow clients to set sort param as it may cause issues with subsequent syncs.
Component
Core library

@aditya-07 @Tarun-Bhardwaj I would like to work on this issue. Please assign this issue to me.


os-bind: zone transfer "none" allows zone transfer by default

Information

Plugin version: 1.13
Package version: bind 9.16.5_1
Configuration URI: /ui/bind/general/index#domains

Problem
A master zone has "Allow Transfer" option to choose which ACL the server allows for transfer requests,
but if you select the option "none" there is no allow-transfer {none;}; option set in named.conf.
This allows a zone transfer per default, which states a security risk
Possible solutions
Add allow-transfer {none;} if "none" is selected.
Workarounds
A) Create an ACL for e.g. <IP_ADDRESS> and chose this in the "Allow Transfer" option.
B) Block TCP Queries in Firewall for DNS/BIND Port (e.g. 53), since zone transfer is done via TCP.

Not sure how to proceed here.
None should be default, if one requires security an acl can be added to it.

None should be default, if one requires security an acl can be added to it.
Maybe it should be made clear that "none" does not mean no zone transfer allowed.
I assumed, if I select "none" there is no possibility to transfer a zone, which is not the case.

Maybe it would be possible to add an Option "NoACL" to the drop down list to have the choice between, "NoACL", "None" and the defined ACLs. "None" is in my Opinion a bad label in the bind context for saying there is no ACL configured.

Give me a week when I am back at a Computer to think about it

Ok, I had a look. The problem is that OPNsense calls nothing selected as none but BIND uses none as noone. So this is a bit misleading when coming from BIND. As I don't want to break current setups where things work cause of not using an ACL, I'd suggest to enhance the help-text that transfer is allowed from everywhere when nothing is set.


[e2e] add more VM test cases

Add Test Cases

[x] test_create_stopped_vm
[x] test_clone_running_vm
[x] test_clone_stopped_vm
[x] test_create_with_two_volumes
[x] test_create_with_existing_volume

Misc

improve and fix fixture bug
add marker virtualmachines
improve VMSpec in harvester_api

Tested on Jenkins harvester-runtests#195, some (harvester) bugs found and I will file issues for them.

fix some timing bug and re-run on Jenkins harvester-runtests#200.


Can't resolve allure-report-data artifact while evaluating the plugin

We are using TeamCity with many different agents (Windows, Linux, OS X, Solaris, AIX etc). We are living behind the proxy server and use the single access to remove repositories with Nexus Professional (Nexus OSS, Artifactory are similar repository software). Our Maven installations on agents configured with separated global settings.xml (with the list of local repositories on our Nexus) and user's settings.xml in ~/.m2/settings.xml with secured credentials for basic authentication in Nexus for downloading all maven artifacts.
The allure-teamcity-plugin has direct URLs for getting necessary artifacts and cannot be used in this environment. I tried many steps for making it work, but unsuccessfully:

Setting of M2_HOME cannot help
Setting maven.home and user.home variables (according the code of clay-maven-settings-builder v. 2.3) also does not work
I downloaded allure-report-builder trunk and concatenated it with allure-teamcity-plugin - unsuccessfully
I downloaded necessary jar * war manually and modified allure-report-builder for using local jars. The main issue has been skipped, but build failed because of dependencies of allure-report-data.jar was not downloaded and not added to the classpath. Hell!
I found that clay-maven-settings-builder read only one settings.xml (which will be found first), I modified sources for reading both global and user settings.xml, but also unfotunately - the library now skip messages about unavailability of hardcoded repo URLs (repo1.maven.org and oss.sonatype.org), but I'm still not lucky:

=======================================================================
[19:39:50]Allure report generation
[19:39:50][Allure report generation] analyse results pattern **/allure-results
[19:39:51][Allure report generation] analyse results directories [C:\TeamCity\buildAgent\work\d6f20466435135e0\common\reports\allure-results, C:\TeamCity\buildAgent\work\d6f20466435135e0\cte\target\allure-results]
[19:39:51][Allure report generation] prepare allure report directory [C:\TeamCity\buildAgent\temp\agentTmp\allure]
[19:39:51][Allure report generation] prepare report generator with version: 1.4.15
[19:39:51][Allure report generation] process tests results to directory [C:\TeamCity\buildAgent\temp\agentTmp\allure]
[19:39:51]
[Allure report generation] ru.yandex.qatools.allure.report.AllureReportBuilderException: ru.yandex.qatools.clay.AetherException: Can't resolve given artifact ru.yandex.qatools.allure:allure-report-data:jar:1.4.15
at ru.yandex.qatools.allure.report.AllureReportBuilder.processResults(AllureReportBuilder.java:185)
at ru.yandex.qatools.allure.teamcity.AgentBuildEventsProvider.beforeBuildFinish(AgentBuildEventsProvider.java:72)
at sun.reflect.GeneratedMethodAccessor26.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at jetbrains.buildServer.util.EventDispatcher.dispatch(EventDispatcher.java:120)
at jetbrains.buildServer.util.EventDispatcher$2.invoke(EventDispatcher.java:67)
at com.sun.proxy.$Proxy6.beforeBuildFinish(Unknown Source)
at jetbrains.buildServer.agent.impl.buildStages.finishStages.FireBeforeBuildFinishFStage.doFinishStage(FireBeforeBuildFinishFStage.java:32)
at jetbrains.buildServer.agent.impl.buildStages.BuildFinishStagesExecutor.runFinishStage(BuildFinishStagesExecutor.java:28)
at jetbrains.buildServer.agent.impl.buildStages.BuildFinishStagesExecutor.doBuildFinishStages(BuildFinishStagesExecutor.java:20)
at jetbrains.buildServer.agent.impl.BuildRunActionImpl.runBuild(BuildRunActionImpl.java:58)
at jetbrains.buildServer.agent.impl.BuildAgentImpl.doActualBuild(BuildAgentImpl.java:281)
at jetbrains.buildServer.agent.impl.BuildAgentImpl.access$100(BuildAgentImpl.java:55)
at jetbrains.buildServer.agent.impl.BuildAgentImpl$1.run(BuildAgentImpl.java:245)
at java.lang.Thread.run(Thread.java:745)
Caused by: ru.yandex.qatools.clay.AetherException: Can't resolve given artifact ru.yandex.qatools.allure:allure-report-data:jar:1.4.15
at ru.yandex.qatools.clay.Aether.resolveWithTransitives(Aether.java:179)
at ru.yandex.qatools.clay.Aether.resolve(Aether.java:131)
at ru.yandex.qatools.clay.Aether.resolve(Aether.java:109)
at ru.yandex.qatools.allure.report.AllureReportBuilder.processResults(AllureReportBuilder.java:175)
... 15 more
Caused by: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact ru.yandex.qatools.allure:allure-report-data:jar:1.4.15
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:384)
at ru.yandex.qatools.clay.Aether.resolveWithTransitives(Aether.java:177)
... 18 more
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Could not find artifact ru.yandex.qatools.allure:allure-report-data:jar:1.4.15
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDependencies(DefaultRepositorySystem.java:367)
... 19 more
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Could not find artifact ru.yandex.qatools.allure:allure-report-data:jar:1.4.15
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:434)
... 21 more
=======================================================================
Unfortunately, I can't set system proxy on all agents or set the proxy into user's maven settings.xml - everything should use the single Nexus server for accessing artifacts from maven, gradle, grapes etc.
Please, add the support of separated settings.xml and using of them with highest priority because they're main configuration files for everybody who are living outside of Internet.
Or add the reading of environment variables with paths of global settings.xml and user's settings.xml for ignoring default Internet URLs.
Thanks!

fixed via https://github.com/allure-framework/allure-teamcity-plugin/pull/28 . The release and documentation is coming soon.


Generate launch.json and tasks.json

Fixes #13
When the user creates a new Quarkus project with the "Quarkus: Generate a Maven project" command, the new Quarkus debug config will be created:

This allows the user to hit F5 to debug, and have the mvn quarkus:dev command run automatically.
When the user exits the debug session, they are presented with this modal:

Clicking 'Cancel' will close the modal and will not terminate the quarkus:dev task.
Clicking 'Yes' or 'No' will cause a new modal to appear:

For this modal, clicking 'Cancel' has the same effect as clicking 'No'.
If 'Yes' is clicked, the two modals will not show up again, and the quarkus:dev task will terminate or will not terminate (depending on what the user clicked earlier) everytime the debug session is closed.
If 'No' is clicked, the two modals will show up again when a debug session is closed.
The user can also set the behaviour in VS Code settings:

There is one problem I found, however. If the user follows these steps:

Open VS Code
Open Quarkus project folder, but don't open any files
Set the config to 'Always terminate'

Start the debug session with F5.
Close the debug session

In this case, we would expect that the quarkus:dev task to terminate, but it does not. This is because vscode-quarkus is not running. It is not running because the user did not invoke a vscode-quarkus command / did not open application.properties. To fix this, there needs to be a way to start the vscode-quarkus extension when debugging a Quarkus project.
Signed-off-by: David Kwon<EMAIL_ADDRESS>

In this case, we would expect that the quarkus:dev task to terminate, but it does not. This is because vscode-quarkus is not running. It is not running because the user did not invoke a vscode-quarkus command / did not open application.properties. To fix this, there needs to be a way to start the vscode-quarkus extension when debugging a Quarkus project.

There is an activation event for debugging: onDebugResolve:type, where type is the debug configuration type (ie, java, python, etc). Of course, if we have onDebugResolve:java, vscode-quarkus will start when debugging any java application, which is not what we want.

If I disconnect the debugger, I get no popup

Ok so it didn't start the vscode-quarkus extension, so no popup was invoked

For the activation issue, I'm afraid we're gonna need to add a new Quarkus command, that'll basically look for and execute the launch configuration, it's the only way to guarantee the extension will register its debug listener. I've tried to add "workspaceContains:**/target/wiring-devmode" as an activation event, but it only works if the workspace already contains that directory. Activating on all java debug events is excessive.

I've added a new command called "Quarkus: Debug current Quarkus project" that starts the debugger, but for now, it assumes that the project is located in the first open workspace folder.
If the user has multiple folders open with multiple Quarkus projects open, we need to determine which project to debug.
I've also updated the PR so that the tasks, launch json content are read from files.

I've made the updates.
Changed the modal to an Information message and changed the button names:

The change from modal to information message was because the button layout for modals seem to be platform dependent. I could not control where the 'Cancel' button was being placed.
Maybe vscode #47899 would help us create input boxes with checkboxes in the future.
A problem with this PR is that we assume that the user would never change the quarkus:dev task label in tasks.json.

I think it looks better. However, since we now know the user's choice, we could be more specific on the 2nd popup:
Do you want to always [terminate the task|keep the task running]? Remember my choice / Ask again next time

Made the changes, the second information message looks like this:

This is the DebugSession object given from the onDidTerminateDebugSession() function:

Since the user is able to change preLaunchTask or change name, my idea was to iterate through all tasks to find tasks that call the maven quarkus:dev command. I can retrieve all tasks through the VS Code api with tasks.fetchTasks(). Once I find those tasks, I can find the correct task names and compare them with preLaunchTask. @fbricon what do you think?

I can't think of a more surefire way to identify that task so yeah you can try

I've made the changes. Since there were so many cases, I opted for a try catch to keep things clean and reduce the if (variable == undefined) return checks.
First, I check if there if the debug session has a prelaunch task.
Then I gather all quarkus:dev tasks that are running AND defined in the current debugSession's workspace folder, into a list.
Then, I just compare preLaunchTask with the contents of the list.

@xorye can you fix the conflict and merge?

updated

sorry, please do not merge this yet. I must fix a problem that arises when the extension runs after being installed from a .vsix.

Fixed. The problem was that the files that we being read for tasks.json and launch.json were located in the vscode-quarkus/src directory. I moved them out to a new vscode-quarkus/vscode-debug-files directory.

So if you try to debug a gradle-based project (any simple gradle java project), nothing happens. there should be a popup indicating why command could not run

New error messages have been implemented.

(This message above is what appears when a gradle project is open and the debug command is called)

There are some TODO comments that I've added. I can make the github issues to address them after this is merged.


Enable Nutch "stopping"

update view to send "STOPPING" state.
refactor nutch crawl task
refresh crawl model to detect "STOPPING" state
immediately return from crawl and set state to "STOPPED"

This is ready for review.  It's small enough that I'm happy to try and merge it for 0.4

Closes https://github.com/memex-explorer/memex-explorer/issues/729

Looks fine to me.


Core Dumped After each print job

OS: Ubuntu 20.04 LTS
Ver.: CUPS 2.3.1
Printer and drivers: Samsung M2070 Series, driverless, cups-filters 1.27.4
After each job, which is succesfully finished (the printer DOES print), cups crashes and takes 3 minutes to get back online, here the status report:
● cups.service - CUPS Scheduler
     Loaded: loaded (/lib/systemd/system/cups.service; enabled; vendor preset: enabled)
     Active: deactivating (stop-sigterm) (Result: core-dump) since Wed 2022-01-26 10:52:35 CET; 2s ago
TriggeredBy: ● cups.path
             ● cups.socket
       Docs: man:cupsd(8)
    Process: 24864 ExecStart=/usr/sbin/cupsd -l (code=dumped, signal=ABRT)
   Main PID: 24864 (code=dumped, signal=ABRT)
      Tasks: 1 (limit: 18837)
     Memory: 3.3M
     CGroup: /system.slice/cups.service
             └─24949 implicitclass://Samsung_M2070_Series_SEC30CDA71ABF6A_/ 9 manfucci Twitter.png.pdf 1 MediaType=Stationery number-up=1 >

gen 26 10:51:58 manfucci-Inspiron-7501 systemd[1]: Started CUPS Scheduler.
gen 26 10:52:35 manfucci-Inspiron-7501 cupsd[24864]: free(): invalid pointer
gen 26 10:52:35 manfucci-Inspiron-7501 systemd[1]: cups.service: Main process exited, code=dumped, status=6/ABRT

Someone is freeing an invalid pointer

Hi @almanfu ,
cups-2.3.1 is several years old, the current CUPS version is 2.4.1 - it would be great if you reported the issue to your OS maintainers.
I can only check whether the current code is affected as well, but I would need a backtrace from the crash - would you mind providing it?
Thank you in advance!

Thanks for your quick reply. Will probably install the newest version. Here is the backtrace.
#0  __GI_raise (sig=sig@entry=6) at ../sysdeps/unix/sysv/linux/raise.c:50
#1  0x00007f7241694859 in __GI_abort () at abort.c:79
#2  0x00007f72416ff3ee in __libc_message (action=action@entry=do_abort,
    fmt=fmt@entry=0x7f7241829285 "%s\n") at ../sysdeps/posix/libc_fatal.c:155
#3  0x00007f724170747c in malloc_printerr (
    str=str@entry=0x7f72418274ae "free(): invalid pointer") at malloc.c:5347
#4  0x00007f7241708cac in _int_free (av=<optimized out>, p=<optimized out>,
    have_lock=0) at malloc.c:4173
#5  0x00007f724189b1de in ?? () from /lib/x86_64-linux-gnu/libcups.so.2
#6  0x00007f724189b143 in ippDelete () from /lib/x86_64-linux-gnu/libcups.so.2
#7  0x000055bb1c57c7ac in ?? ()
#8  0x000055bb1c5b6b98 in ?? ()
#9  0x000055bb1c573b74 in ?? ()
#10 0x00007f72416960b3 in __libc_start_main (main=0x55bb1c573220, argc=2,
    argv=0x7fff7ce38148, init=<optimized out>, fini=<optimized out>,
    rtld_fini=<optimized out>, stack_end=0x7fff7ce38138)
    at ../csu/libc-start.c:308
#11 0x000055bb1c574eee in ?? ()

@almanfu please install the debuginfo packages and get the backtrace once again - the current has many undefined stuff.
Thank you in advance!

No response for a month, closing the issue.


Extending the list of standard response formats (i.e. CIF, POSCAR)

There have been discussions about exposing CIF data (#329) or any entry-related files (#211) through OPTIMADE. Now I remembered the provision of endpoint-specific response_format which could be used to ask for specific representations of entries or their collections. Up to now OPTIMADE only supports json response format. I suggest standardizing other optional response formats that could be used by clients to retrieve representations of entries, and my immediate suggestions would be CIF (cif, native structure data format for the COD) and POSCAR (poscar). Upon request for response_format=cif client would receive plain CIF file for an entry (or several entries) and could directly use it in calculations etc.
It may also be true that I misunderstood the intention of response_format. Maybe it is supposed to specify a carrier format for OPTIMADE data. Then foreseen additions to existing json would be xml and yaml, which would carry the same property information wrapped in their specific syntax. If this is the case, then #211 is worth pursuing to provide other representations of entries instead.

I think this is a very nice idea, and very much in line with what I imagine response_format is useful for.
However, to actually include response_format=cif in the standard requires a bit of work. IMO we must specify exactly how all standard OPTIMADE entries are mapped into the cif format, including things like relationships between entries (although, for anything optional it could say output_format=cif does not support it and it MUST be omitted for now). This to ensure that every database returns consistent cif output. You may say "cif is already a standard" and obviously the mapping should adhere completely to that standard. But there are definitely things in the OPTIMADE -> cif mapping that isn't obvious, and it would be a shame to end up with 43 dialects of cif output all using their own representation of, e.g., assemblies.
May I suggest that you start with creating a response_format=_cod_cif to work out the details of this mapping. I'd be more than happy to discuss ideas about how to best do these various mappings, but the decisions would be all yours since this is under your namespace.
Then, at some future point, you'll come to OPTIMADE with your design and propose to adopt it as the standard for response_format=cif. Perhaps then we are happy to adopt it exactly as designed, or we will see a need to consider some adjustments to meet requirements of others in the consortium. But we can take that discussion at that point.

I also think that it is a very nice idea... It might be worth looking at some previous work by @merkys (https://github.com/cod-developers/CIF2JSON)

I am mostly interested in standardizing OPTIMADE methods to access other resource representations, such as CIF and POSCAR for structures, BibTeX for references and so on. I am not much interested in expressing OPTIMADE-specific details (i.e., relationships and so on) in these representations, because OPTIMADE already has means for querying and retrieving this information.
Standardizing CIF is a tedious task on its own. COD contains CIF files from more than 43 sources, and we leave the standardization (more like interpretation) to the client, because standardization usually means making assumptions about data, and care should be taken not to overinterpret or invent any data. Of course, conservative inferences and standardizations may be applied, but I would better leave them to the client. There are a lot of tools preparing CIF files for inputs to QM and other calculations. I would prefer implementations providing CIF files in any way that is compatible with already existing CIF standard.
CIF2JSON would maybe be useful for representing CIF in JSON (something like response_format=cif+json), if there was a need for that as well.

Revisiting this discussion and re-reading @rartino's comment I am more and more inclined to give this proposal up in favor of #211.

As said before, I have conflated alternative OPTIMADE response formats and file representations of OPTIMADE entries into a single issue. Now as #360 is merged, I am closing this issue.


Fix NoSuchFieldException: MAINHAND crash on load

Fixes #26.
My guess as to what's happening:
Gson wants to ultimately serialize EquipmentSlot here
https://github.com/Draylar/tiered/blob/cbaf6f6e4eb8f31b4e3006f8c1537c822cf99ac6/src/main/java/draylar/tiered/Tiered.java#L109
and by default uses the EnumTypeAdapter.
This specifically runs
          String name = constant.name();
          SerializedName annotation = classOfT.getField(name).getAnnotation(SerializedName.class);

So classOfT.getField(name) searches for the field MAINHAND inside the class EquipmentSlot.
What's the issue? Obfuscation.
There is no field with the name MAINHAND, but it's field_6173 (in intermediary).
The fix is to add a straight forward serializer for the enum.

Some more information:
I could reproduce #26 with a "vanilla" client (only Fabric, Fabric API and Tiered) on every world load.
Interestingly, I couldn't reproduce it in the dev environment.
Was wondering why, so I tested EquipmentSlot.class.getField("MAINHAND") on both; it failed when running normally, but succeeded in the dev environment, which can only mean that it's actually running the client "unobfuscated" (with yarn mappings).
I never use the dev env and I guess this is another reason to not use it on the daily.

Yep, just a simple mapping issue. It worked previously because I was never using my GSON instance to serialize (and the data files had the proper slot name, which deserialized fine in-code), but I forgot to add the slot serializer after serializing in my sync packet.
Thanks for the fix!


kernel: Remove unused timeout_q from z_kernel

This commit removes the timeout_q from the struct z_kernel since it
is no longer used.
Note that the new kernel timeout implementation introduced in the
commit 987c0e5fc1fa665ce629796c97529f219380e0a7 uses timeout_list
global variable in place of it.
Signed-off-by: Stephanos Ioannidis<EMAIL_ADDRESS>

What about instead removing timeout_list static variable in kernel/timeout.c keeping the list(spinlock as well) in _kernel.timeout_q. I think, this helps to maintain kernel data structure easier.


Gas/Liquid Canister resprites

About the PR
Changes the old gas/liquid canister sprites out for new sprites that have some more detail and depth then their older counterparts. This PR also changes the tube attachment from a connector slightly for canisters, scrubbers tube has not been changed.
Media

Left tank in right connected to connector

All changed canisters excluding dark-blue (which is still updated to match just not showcased here)

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Changelog
:cl:

tweak: Canister sprites changed
tweak: Canister tube attachment changed
tweak: Canister tank door changed

with flat top it doesnt really look like canister

The perspective is a bit off from top compared to bottom

I don't think these canisters for a few reasons which I'll elaborate on here.
First of all, the perspective between the top and bottom of the canister body fluctuates quite a bit, resulting in a significant difference in the curvature. This also applies to the top of the canister itself, where the top ring is smushed on the back side.
Beyond that, theres a heavy use of dithering in the shading of these sprites which is a general no-no in terms of our asset style. We exclusively use shading with a fixed set of values (or in the case of some legacy assets, a gradient).
In terms of the detail work, i feel like the simplification of the design harms the readability of the asset as a canister at all. The omission of the larger valve, other panels, and the top handle all just make the sprite look more generically sci-fi in a way that I dont think meshes with our art style.
I do think some other servers would probably be open to accepting these assets, as ive seen quite a few other servers with similar visual styles to this. However, I do not think these would be a good fit with our current art.
Thank you for your contribution, but I'm going to close this PR. Feel free to contribute again in the future.