Add AppConfig support for Lambda

Description
Add AWS AppConfig support for AWS Lambda. This functionality uses Lambda Extension to retrieve the config.
Motivation and Context
It is extending the AWS AppConfig functionality to support AWS Lambdas properly.
Testing
I created the AWS Lambda app and configure it with AppConfig using this new extension.
Types of changes

[ ] 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 change)

Checklist

[x] My code follows the code style of this project
[x] My change requires a change to the documentation
[x] I have updated the documentation accordingly
[x] I have read the README document
[x] I have added tests to cover my changes
[x] All new and existing tests passed

License

[x] I confirm that this pull request can be released under the Apache 2 license

I'm waiting impatiently for this to be merged!

Thanks for adding this, @mgorski-mg! Hopefully, this will get merged soon to start migrating our Lambda configs from SSM parameters to AppConfig, 👏👏👏.

@mgorski-mg I tested your AddAppConfigForLambda extension and is working perfectly, 👍. Thanks again!
I just have a comment about your recommendation to build IConfiguration in every invocation. I don't think this is desirable or practical or even necessary. I think a better recommendation is that if you wish for very fast reloading, you could use a very small reloadAfter value while using the WaitForSystemsManagerReloadToComplete method at the end of each request. This will achieve the same thing without having to constantly rebuild your configuration on each request and constantly calling the AWS AppConfig extension in each invocation.
In this function I just migrated to AppConfig, I configured the AWS AppConfig Lambda Extension to get a new configuration every 5 minutes. Then, I configured my Lambda function to reload the configuration after 1 minute, while adding the WaitForSystemsManagerReloadToComplete method at the end of each request. This way, I'm not either rebuilding IConfiguration or calling the AppConfig extension on every single invocation of the function (which could be a lot per minute). Instead, each lambda function reloads its configuration every 1 minute from the extension, and the extension checks for a new configuration every 5 minutes, which means that I'll get an updated configuration in my lambdas at most 6 minutes later (which in my use case, is good enough).
If you need very quick reloading, you could leave the AppConfig extension with the default poll interval (45 seconds) and set your lambda function to reload after 1 to 10 seconds (for example, depending on how fast you really need the reloading to happen). You will get a lot more calls to the AppConfig extension (which are super-quick) but without having to constantly rebuild IConfiguration.
In general, I don't think making a recommendation about the speed of reloading should be part of the readme, as this will vary from case to case. I think a single section for "Reloading in AWS Lambda" with just adding an example of using AddAppConfigForLambda with a reloadAfter parameter, and indicating that WaitForSystemsManagerReloadToComplete is needed, should be enough. Btw, the AddSystemsManager example doesn't show a reloadAfter parameter which I think it should.

I recommend it because reloading is done for us by Lambda Extension.
In all invocations after the cold start call to AppConfig last around 1ms because it's local communication.
But I think it's a good point, that maybe it shouldn't be recommended in the Readme, because it depends on what types of other configurations are you adding to the builder.
Let's wait for @normj and @philasmar and their opinion :)
Another topic is waiting for completion.
WaitForSystemsManagerReloadToComplete is required only for Parameter Store I think because there you have internet communication and the whole config needs to be downloaded.
In AppConfig with Lambda Extension, you don't need to do any magic to wait for reload, because reloading is done on Lambda Extension level and in Lambda Handler is downloaded by local communication and takes around 1ms.
Btw. Thanks for testing my solution!!

@arturomonge I just realized that you are super right!
If we are building the IConfiguration in the AWS Lambda handler we are losing the caching at all because a new ClientId is created and a LastConfig version is also reset... Thank you so much! :)
Readme edited.
I also found one bug. When we are using Lambda Extension and the config is bigger than 2KB, the ContentLength property in the response from AppConfig(in this case from Lambda Extension) is 0, no idea why.
Because of that, I change the logic of checking if the config needs to be parsed and cached in IConfiguration to verify the ConfigurationVersion property instead.

@arturomonge you are also right about waiting for reloading to be completed using WaitForSystemsManagerReloadToComplete method. Readme updated.
Thanks :)

@mgorski-mg Nice catch! I hadn't even thought about the ClientId being re-created every time IConfiguration was rebuilt, but glad you caught that.
About WaitForSystemsManagerReloadToComplete, yes, it's necessary if you are not rebuilding IConfiguration which now we know we shouldn't do for any reason, 😉. I see in your example you added it at the beginning of each invocation. In my case, I've added it at the end. This way, while the function is being executed, the reload is happening (which is an async process). If the reload finishes first, we don't have to wait for it as it will be completed by the time we call WaitForSystemsManagerReloadToComplete. But if the invocation is faster, then at the end of the invocation we will wait for the reload to complete. This way, we also give the OnChange token time to kick in while the invocation is occurring. I felt that if we call WaitForSystemsManagerReloadToComplete right at the beginning, the OnChange event might not have been triggered yet and we might miss it (sort of a race condition). It has been working great in a Lambda function already in production which I migrated to AWS AppConfig as a test.
Checking your commits, I had missed the use of AWS_APPCONFIG_EXTENSION_PREFETCH_LIST. Nice! I will add it right away to my functions to reduce cold start times, 👍.

@normj @philasmar There is an important bug in the support for AWS AppConfig that needs to be fixed, and it is fixed in this PR. It's when the AppConfig LambdaExtension returns 0 for content length if the config size is greater than 2Kb. I know you are full of things, but any possibility that you can give some attention to this PR? It would be extremely helpful. Thank you!

I have created PR #103  that consolidates this open PRs along with this change. Because of the breaking changes across the PRs including this one I am planning on a major version bump to 4.
Some significant rework was done on this PR in the consolidated PR to switch to the new IAmazonAppConfigData service client for how to get config data from AppConfig. I also switch to talking to the Lambda extension with a direct HttpClient calls.
I'm going to close this PR and track the work in #103. Please feel free to review that PR for the changes I made from this PR.


Kpt package upgrade

What this PR does / Why we need it
Enable deployment through kpt
Which issue(s) this PR fixes
Fixes https://github.com/mercari/spanner-autoscaler/issues/41

NOTE: This PR depends on #40

Converted to draft because it includes the changes from #40 too. Will be ready for review after #40 is merged.


[Question] How to access to multiselect component ref

I want to make a cascade componet A-multiselect with B-multiselect comp by a list  dynamically
<multiselect v-for="item in list"
  v-ref:item.value    // not work in vue@1
>
</multiselect>

how can i access the comp when it updated , selected or removed ?
suggestion: can the multiselect comp can expose the refs when emit event ?

You can’t. You can however, detect which component emitted the event by using the :id prop.
The code would look like this:

  <multiselect :id="$index" @update="handleUpdate">
  </multiselect>

methods: {
  handleUpdate (newVal, id) {
    console.log(`Multiselect with id: ${id} emitted new value: `, newVal)
  }
}
Of course the `:id` doesn’t have to be the `$index`. It can also be a string, so if your `item.value` is a string you can pass it as the `id` prop.

Yes,I update to the latest Multiselect , use the :id prop and v-ref directive.
  <multiselect v-for="item in list"
      :id="item.value"
      v-ref:item // return an object refs
      :options="item.options"
      :selected="item.selected"
     @update="handleUpdate">
  </multiselect>

methods: {
  handleUpdate (newVal, id) {
    if (id === 'A' ) {
        let compB = this.findCompById( 'B' )
        compB.value = this.setCompBOptionBy( newVal ,'B')
    }
   ...
  },
  setCompBOptionBy( newVal, id ) {
    //loop the` this.list`
  },
  findCompById (id) {
   // loop the` this.$refs.item`
  }
}

not elegantly but satisfied my requirement temporarily.

Why do you need to find the element anyway?

Let me try to explain that. I will put the reproduction in JSFiddle later.

My app is a simple "fields condition + result tables", fields change, result tables change.
All the fields and the Multi-Select options fetch by ajax  from server (Vue-Resource),
Some fields options is not independent, so need to find the element in order to change the other options

All things is dynamic, it really makes apps complex. It also have some problems when data inits, comp is ready but the data is fetching, it  triggers the watcher twice? Maybe I should rethink that.

I think that this is might be a bad pattern to operate on components from this.$refs list. Also, I don’t think that passing a value to the id prop and then changing it is a good practice too. I believe it would be better to always operate on the data model and let the reactivity system do the work on updating the DOM.
Please provide the mentioned JSFiddle, so I could potentially help. :)

Sorry for the busy days and thank to your attention.
I do have some confuse about data init , ajax and  reactivity , need some good practices :)
JSFilddle is here
//html dependent on vue@1 and vue-multiselect@latest

Filters

  <multiselect
      v-for="item in list"
      :id="item.name"
      :multiple="true"
      :hide-selected="true"
      v-ref:item
      :selected="item.selected"
      :options="item.options"
      :placeholder="item.name"
      @update="updateSelected">
    </multiselect>

0" width="100%">

	results

      no results

//javascript
new Vue({
  el: 'body',
  components: {
  	multiselect: VueMultiselect.Multiselect
  },
  created:function(){
  	//ajax
  	var self = this
  	setTimeout(function(){
            self.list = [
          	{name:'A',selected: [],options: ['list_a', 'of_a', 'options_a']},
                {name:'B',selected: [],options: []},//is empty and according 'A' dynamic change
                {name:'C',selected: [],options: ['list_c', 'of_c', 'options_c']}
             ]
    },500)
  },
  data: {
      list:[],
      results:[]
  },
  computed: {
  	condition () {
    	    let arr = []
            this.list.forEach(item=>{
            if(item.selected.length>0){
        	arr.push(item.name + '=' + item.selected.join(','))
           }
      })

      return arr
    }
  },
  ready: function() {
  },
  methods: {
    updateSelected (newSelected,id) {
    		let item
        if (id === 'A') {
        	// change 'B' according to 'A'
          const compA = this.queryCompById(this.$refs.item, id)
          const compB = this.queryCompById(this.$refs.item, 'B')

          item = this.queryListById(compB.id)
          item.selected = []
          item.options = item.options.length > 0 ? item.options.reverse() : ['list_b', 'of_b', 'options_b']
        }
        //update all multiselects
        item = this.queryListById(id)
        item.selected = newSelected

				//load results
        this.$nextTick(()=>{
          this.fetchData(this.condition)
        })
    },
    queryCompById (comps,id) {
      for (let i = 0; i < comps.length; i++) {
        let comp = comps[i]
        if (comp.id === id) return comp
      }
    },
    queryListById (id) {
      for (let i = 0; i < this.list.length; i++) {
        if (this.list[i].name === id) {
          return this.list[i]
        }
      }
    },
    fetchData (condition) {
   	 //ajax
    	var self = this
  	setTimeout(function(){
      	    self.results= []
            self.condition.forEach(item=>{
        	self.results.push(item)
            })
      },500)
    }

  }
})

I will look into it after work. :)


Crash Reporter not working on WINDOWS 8 with NODE 0.12

Crash Reporter is unable to send the notification to the URL mentioned in the start() once the process is being crashes ( via process. crash()).
This includes : https://gist.github.com/zcbenz/9c75ccda4f925faf92ca
https://github.com/hokein/electron-sample-apps/tree/master/crash-report
This same thing is working fine on UBUNTU. Can anyone please see if this is really on issue or there is specific problem with the code mentioned in the above URL's.
Alternatively we are receiving the following error too -> ERROR:crash_reporter_win.cc(75)] Cannot initialize out-of-process

@panbhatt we did some mock test to see whether crash reports are generating. we are able to generate them. will upload a git sample so you could test see if it  works.

Check this out https://github.com/kamesh-a/electron-samples/tree/master/CrashReporter
sample log in mac, windows8 also we tested
Spec :
node --version : v2.3.3 ( iojs )
npm --version : 2.11.3
node 12.7 has same module version should be equivalent to this version.
Hope this helps !!!
crashreporter =============== START
 Headers :  { host: '<IP_ADDRESS>:3000',
  'content-type': 'multipart/form-data; boundary=---MultipartBoundary-sezuGs3Jd5YbbtEU0cg4wIbwJy12OkjM---',
  accept: '*/*',
  'transfer-encoding': 'Chunked',
  cookie: 's_pers=%20s_fid%3D27123FF0A10925B1-3B1EDD6A1790CD5C%7C1479058412411%3B%20s_vs%3D1%7C1415901812411%3B%20s_nr%3D1415900012412-New%7C1447436012412%3B',
  'user-agent': 'crashpad_handler (unknown version) CFNetwork/673.3 Darwin/13.4.0 (x86_64) (MacBookPro11%2C3)',
  'accept-language': 'en-us',
  'accept-encoding': 'gzip, deflate',
  connection: 'keep-alive' }
****** Parsing formdata *****
{ fields:
   { _companyName: 'GitHub, Inc',
     _productName: 'crash-report-demo',
     _version: '0.1.0',
     guid: '690dbc1e-33c3-419c-924a-d5dc81f5bb4d',
     platform: 'darwin',
     process_type: 'renderer',
     prod: 'Electron',
     ver: '0.30.2' },
  files:
   { upload_file_minidump:
      { domain: null,
        _events: {},
        _eventsCount: 0,
        _maxListeners: undefined,
        size: 237472,
        path: '/var/folders/wk/qvmk0tkj34d2lgn42rsdy_1m0000gn/T/upload_94a1794ed7cf2114937ebcbe0bbf71ee',
        name: 'a253b92e-d292-4047-afa7-2ed4f912fe1d.dmp',
        type: 'application/octet-stream',
        hash: null,
        lastModifiedDate: Wed Aug 05 2015 15:12:49 GMT+0530 (IST),
        _writeStream: [Object] } } }
 crashreporter =============== END

@kamesh-a Tried to clone your repo and start it with "electron ." . sorry to say it is not working. here is my env details
npm : 2.11.3
node : V0.12.7
Errror while starting the program>
[87248:0805/113829:ERROR:crash_reporter_win.cc(75)] Cannot initialize out-of-process crash handler
[96688:0805/113830:INFO:renderer_main.cc(200)] Renderer process started
[71596:0805/113830:INFO:renderer_main.cc(200)] Renderer process started
on click on Crash in the HTML window i receive the following.

I am running windows 8.1. seems like there is some problem in starting CRASH HANDLER whilethe app is start. or may be i am doing something which is wrong here.

I'm also having problems with the crash-reporter on Windows. I tried both Windows 10 and Windows 7 with node v0.12.7 + electron v0.32.2 and the simple crash-reporter-test gist: https://gist.github.com/zcbenz/9c75ccda4f925faf92ca.
The crash is not reported:
 node .\node_modules\electron-prebuilt\cli.js .
[1040:0914/154400:INFO:renderer_main.cc(200)] Renderer process started

Here's what it looks like when it does work with the same code and versions of node and electron on Mac:
node ./node_modules/electron-prebuilt/cli.js .
[6579:0914/153922:ERROR:file_io.cc(30)] read: expected 40, observed 0
[6583:0914/153922:INFO:renderer_main.cc(200)] Renderer process started
{ _companyName: 'GitHub, Inc',
  _productName: 'crash-reporter-test',
  _version: '',
  guid: '0045a572-db57-45fc-9abd-d4eff6ea4536',
  platform: 'darwin',
  process_type: 'renderer',
  prod: 'Electron',
  ver: '0.32.2' }
[0914/153923:ERROR:http_transport_mac.mm(186)] The network connection was lost. (NSURLErrorDomain -1005)

Ok, so after looking at the crash-reporter code, it looks like this is user error on my part. On Windows the crash reporter spawns a new process based on the path of the original process, so you shouldn't run electron with node cli.js that comes with electron-prebuilt.
When I use the electron.exe executable, crash reports work. @panbhatt You might want to see if you were doing the same thing I was.

Ok, some more debugging... The 32-bit version works, but not the 64-bit version.
Also, despite what the documentation says, you need to start crash-reporter in the renderer process on Windows too.

Appears that the crash reporter being broken on 64-bit windows is a known issue: https://github.com/atom/electron/blob/f1787d747afbfcc9e6c416b298d7bf32a366241d/spec/api-crash-reporter-spec.coffee#L19

Reopening this since is broken again after the upgrade to Chrome 50.


How to specify a dictionnary key with --config option

I have a configfile such as:
paramA:
  status: False
  content: "hello"

I don't know how to use the option --config to change the value of the parameter paramA["status"].
Any idea ?

As far as I can tell, there's no way of doing this, since the parsing is done here:
https://github.com/snakemake/snakemake/blob/5349f2a428ea2da511d64271fc15b65e5615b1c2/snakemake/__init__.py#L901
I think that the way to handle this is to specify a configfile overwriting the value you want to overwrite only.


HDFS-17528. FsImageValidation: set txid when saving a new image

Description of PR
HDFS-17528

When the fsimage is specified as a file and the FsImageValidation tool saves a new image (for removing inaccessible inodes), the txid is not set. Then, the resulted image will have 0 as its txid.
When the fsimage is specified as a directory, the txid is set. However, it will get NPE since NameNode metrics is uninitialized (although the metrics is not used by FsImageValidation).

How was this patch tested?
Tested manually

before: the output file is fsimage.ckpt_0000000000000000000 (i.e. txid is 0)

2024-05-14 13:37:27,531 [main] INFO  namenode.FSImageFormatProtobuf (FSImageFormatProtobuf.java:save(732)) - Saving image file .../fsimage/current/newFsImage5968764763996132609/current/fsimage.ckpt_0000000000000000000 using no compression
2024-05-14 13:37:30,522 [main] INFO  namenode.FSImageFormatProtobuf (FSImageFormatProtobuf.java:save(736)) - Image file .../fsimage/current/newFsImage5968764763996132609/current/fsimage.ckpt_0000000000000000000 of size 200392059 bytes saved in 2 seconds .

after: the output file is fsimage.ckpt_0000000023945925442 with correct txid

2024-05-14 13:38:32,414 [main] INFO  namenode.FSImage (FSImage.java:save(1223)) - save fsimage with txid=23945925442 to .../fsimage/current/newFsImage4409944859316006440
2024-05-14 13:38:32,436 [main] INFO  namenode.FSImageFormatProtobuf (FSImageFormatProtobuf.java:save(732)) - Saving image file .../fsimage/current/newFsImage4409944859316006440/current/fsimage.ckpt_0000000023945925442 using no compression
2024-05-14 13:38:35,437 [main] INFO  namenode.FSImageFormatProtobuf (FSImageFormatProtobuf.java:save(736)) - Image file .../fsimage/current/newFsImage4409944859316006440/current/fsimage.ckpt_0000000023945925442 of size 200392062 bytes saved in 3 seconds .

For code changes:

[X] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[NA] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[NA] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[NA] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

@vinayakumarb , thanks a lot for reviewing this!

The jenkins builds keep getting stuck for a day and then fail.  Not sure if it is a known problem?

The last few lines of the Jenkins build before failure:
[2024-06-03T20:14:42.551Z] cd /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-6828/ubuntu-focal/src/hadoop-hdfs-project/hadoop-hdfs
[2024-06-03T20:14:42.551Z] /usr/bin/mvn --batch-mode -Dmaven.repo.local=/home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-6828/yetus-m2/hadoop-trunk-patch-0 -Dsurefire.rerunFailingTestsCount=2 -Pparallel-tests -P!shelltest -Pnative -Drequire.fuse -Drequire.openssl -Drequire.snappy -Drequire.valgrind -Drequire.zstd -Drequire.test.libhadoop -Pyarn-ui clean test -fae > /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-6828/ubuntu-focal/out/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt 2>&1
[2024-06-05T05:43:40.181Z] wrapper script does not seem to be touching the log file in /home/jenkins/jenkins-home/workspace/hadoop-multibranch_PR-6828@tmp/durable-db261340
[2024-06-05T05:43:40.181Z] (JENKINS-48300: if on an extremely laggy filesystem, consider -Dorg.jenkinsci.plugins.durabletask.BourneShellScript.HEARTBEAT_CHECK_INTERVAL=86400)
script returned exit code -1

@szetszwo we can resubmit once and I think the issue is fixed.

@slfan1989 , thanks for the info!  Let me resubmit.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 31s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
46m  6s

trunk passed

+1 :green_heart:
compile
1m 20s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
1m 17s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
1m 12s

trunk passed

+1 :green_heart:
mvnsite
1m 25s

trunk passed

+1 :green_heart:
javadoc
1m  8s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 47s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
3m 16s

trunk passed

+1 :green_heart:
shadedclient
35m 51s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 11s

the patch passed

+1 :green_heart:
compile
1m 13s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
1m 13s

the patch passed

+1 :green_heart:
compile
1m  7s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
1m  7s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 59s

the patch passed

+1 :green_heart:
mvnsite
1m 15s

the patch passed

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 35s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
3m 14s

the patch passed

+1 :green_heart:
shadedclient
35m 37s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
226m 34s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 45s

The patch does not generate ASF License warnings.

366m 31s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.fsdataset.impl.TestFsDatasetImpl

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/6/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6828

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 2eee5c0a5c7a 5.15.0-106-generic #116-Ubuntu SMP Wed Apr 17 09:17:56 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 256d41de8f0f4b5d5718380e6e56795372950b1d

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/6/testReport/

Max. process+thread count
4432 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/6/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 31s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 10s

trunk passed

+1 :green_heart:
compile
1m 22s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
1m 17s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
1m 10s

trunk passed

+1 :green_heart:
mvnsite
1m 22s

trunk passed

+1 :green_heart:
javadoc
1m  8s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 46s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
3m 20s

trunk passed

+1 :green_heart:
shadedclient
35m 59s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 13s

the patch passed

+1 :green_heart:
compile
1m 12s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
1m 12s

the patch passed

+1 :green_heart:
compile
1m  8s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
1m  8s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 59s

the patch passed

+1 :green_heart:
mvnsite
1m 16s

the patch passed

+1 :green_heart:
javadoc
0m 53s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 35s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
3m 15s

the patch passed

+1 :green_heart:
shadedclient
35m 45s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
227m 54s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 47s

The patch does not generate ASF License warnings.

366m 20s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.fsdataset.impl.TestFsDatasetImpl

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/7/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6828

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 32f9b1d96c7c 5.15.0-106-generic #116-Ubuntu SMP Wed Apr 17 09:17:56 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / d61a831e4ff7d92f80e921a00f5dfe7f5ec9cdc9

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/7/testReport/

Max. process+thread count
3245 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/7/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Now, the unit tests are failing.

you can ignore that test failure, I have dropped a comment on the original ticket which caused that, it is failing in our daily build as well.
The previous build crashing was due to the surefire-upgrade which is reverted, there is a thread on hdfs-dev@ about it

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 30s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+0 :ok:
detsecrets
0m  1s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 27s

trunk passed

+1 :green_heart:
compile
1m 22s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
compile
1m 18s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
checkstyle
1m 12s

trunk passed

+1 :green_heart:
mvnsite
1m 23s

trunk passed

+1 :green_heart:
javadoc
1m  8s

trunk passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 44s

trunk passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
3m 16s

trunk passed

+1 :green_heart:
shadedclient
35m 39s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 13s

the patch passed

+1 :green_heart:
compile
1m 14s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javac
1m 14s

the patch passed

+1 :green_heart:
compile
1m  7s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
javac
1m  7s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 58s

the patch passed

+1 :green_heart:
mvnsite
1m 12s

the patch passed

+1 :green_heart:
javadoc
0m 54s

the patch passed with JDK Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1

+1 :green_heart:
javadoc
1m 37s

the patch passed with JDK Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

+1 :green_heart:
spotbugs
3m 20s

the patch passed

+1 :green_heart:
shadedclient
35m 52s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
228m  8s
/patch-unit-hadoop-hdfs-project_hadoop-hdfs.txt
hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

366m 19s

Reason
Tests

Failed junit tests
hadoop.hdfs.server.datanode.fsdataset.impl.TestFsDatasetImpl

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/8/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6828

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux ae1a75664bb4 5.15.0-106-generic #116-Ubuntu SMP Wed Apr 17 09:17:56 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 972adb793f34e32f82728c74ddd86f38225903d9

Default Java
Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.22+7-post-Ubuntu-0ubuntu220.04.1 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_402-8u402-ga-2ubuntu1~20.04-b06

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/8/testReport/

Max. process+thread count
3412 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/8/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
12m  5s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s

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

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
44m 59s

trunk passed

+1 :green_heart:
compile
1m 22s

trunk passed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2

+1 :green_heart:
compile
1m 15s

trunk passed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

+1 :green_heart:
checkstyle
1m 12s

trunk passed

+1 :green_heart:
mvnsite
1m 24s

trunk passed

+1 :green_heart:
javadoc
1m  8s

trunk passed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2

+1 :green_heart:
javadoc
1m 41s

trunk passed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

+1 :green_heart:
spotbugs
3m 20s

trunk passed

+1 :green_heart:
shadedclient
35m 59s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
1m 11s

the patch passed

+1 :green_heart:
compile
1m 13s

the patch passed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2

+1 :green_heart:
javac
1m 13s

the patch passed

+1 :green_heart:
compile
1m 11s

the patch passed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

+1 :green_heart:
javac
1m 11s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
checkstyle
0m 58s

the patch passed

+1 :green_heart:
mvnsite
1m 12s

the patch passed

+1 :green_heart:
javadoc
0m 54s

the patch passed with JDK Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2

+1 :green_heart:
javadoc
1m 32s

the patch passed with JDK Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

+1 :green_heart:
spotbugs
3m 16s

the patch passed

+1 :green_heart:
shadedclient
35m 42s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
224m  0s

hadoop-hdfs in the patch passed.

+1 :green_heart:
asflicense
0m 46s

The patch does not generate ASF License warnings.

374m 33s

Subsystem
Report/Notes

Docker
ClientAPI=1.45 ServerAPI=1.45 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/9/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/6828

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient spotbugs checkstyle codespell detsecrets

uname
Linux 1d13e6522e6d 5.15.0-106-generic #116-Ubuntu SMP Wed Apr 17 09:17:56 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
trunk / 173dab67a7854ba781425badac53a31cbc34b482

Default Java
Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.23+9-post-Ubuntu-1ubuntu120.04.2 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_412-8u412-ga-1~20.04.1-b08

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/9/testReport/

Max. process+thread count
3970 (vs. ulimit of 5500)

modules
C: hadoop-hdfs-project/hadoop-hdfs U: hadoop-hdfs-project/hadoop-hdfs

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-6828/9/console

versions
git=2.25.1 maven=3.6.3 spotbugs=4.2.2

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

This message was automatically generated.

Finally, this is able to pass all the tests.
@vinayakumarb, @slfan1989,  thanks again for reviewing this!


update docker-client to 3.1.8

pulls in a fix for the image digest format changing in Docker v1.8

@gimaker @rohansingh @davidxia

:+1:


jssor fails tests because its still using non-passive Event Listeners

Hi,
You need to make all your scrolling event listeners 'passive' this has been the rule of thumb for several years now.
For more info you can see the following info links:
https://developers.google.com/web/tools/lighthouse/audits/passive-event-listeners
Google dev dated 2016: https://developers.google.com/web/updates/2016/06/passive-event-listeners
Please can you update them to be all set to passive!
The problem can be shown in this video: https://www.youtube.com/watch?v=65VMej8n23A
Thanks.

not ready for some browsers yet, will change later

@jssor
Can you add this now? Browser support is very good.

Only IE11 is an issue, don't care about Malware chinese browsers.


feat: add GPG signed checksums

Signed-off-by: Andrew J. Huffman<EMAIL_ADDRESS>Closes #69

@JefeDavis, this needs testing, because I'm not 100% sure the fingerprint env var is correct.  We'll find out when we can test.


Allow "async" as identifier for object literal property shorthand

Closes #186

:+1: but the test case should include a trailing comma, right?

Current coverage is 94.57% (diff: 100%)

Merging #187 into master will decrease coverage by 1.57%

@@             master       #187   diff @@
==========================================
  Files            19         19
  Lines          3169       3189    +20
  Methods         333        333
  Messages          0          0
  Branches        832        839     +7
==========================================
- Hits           3047       3016    -31
- Misses           63         94    +31
- Partials         59         79    +20

Powered by Codecov. Last update 9b6e243...b52561b

👍 but the test case should include a trailing comma, right?

LOL. I love that I had a test case in the issue and I still made this mistake. Good catch 👍.
I've pushed an update


(Fix RUSTSEC2024-0019 by) run cargo update

Just running cargo update on it's own bumped our transitive dependency on mio from 0.8.11 to 0.8.12 which fixed an actual serious security vulnerability

Benchmarking locally confirms that performance is unchanged, thanks for the PR!


04/02/2018 17:49 : Create Pull Request for branch prTesting_2018040217 -> master

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/updateTestCon.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Divergent Transcript

What is this request referring to?
A non-coding transcript linked to a gene's bidirectional promoter but transcribed on the opposite strand (presumably expressed according to similar chromatin state rules).
What is the name you would like SO to give the term?
transcription_regulatory_region: "divergent_transcript"
What is the definition that you would like for this term?
see HGNC gene group https://www.genenames.org/data/genegroup/#!/group/1990
"Divergent transcripts: The HGNC defines divergent transcripts as long non-coding RNA genes that are within 300-500 nucleotides of a protein coding gene on the opposite strand. These lncRNA genes are named with the format [protein coding gene symbol]-DT e.g. DHX33-DT for ‘DHX33 divergent transcript’. [Source: HGNC curator]"
Rather than just calling these anti-sense, non-coding  transcripts there is also a notion that they are part of a bidirectional promoter for a protein coding gene making a hybrid, protein-coding/non-coding RNA transcriptional relationship within the regulation of gene expression .
Synonyms
a kind of ncRNA as well?
Parent Term
Propose to put this under transcription_regulatory_region:divergent_transcript SO:0001679 ?
Relevant Publications
Please list a number of relevant publications that support the name, definition, and ontological location of the term you are requesting. It is best if you can include a PubMed ID or the last name of the first author along with the publication year, journal-title and potentially the article title.
Gene ID: 107986587; computed; ABCF1-DT
Gene ID: 100506125;  Pubmed: 19212623; ACDY6-DT
Gene ID: 653483; Pubmed: 31981317; AFDN-DT
Pubmed: 27115538
Pubmed: 19597342
...
and drill into the entire HGNC gene group here
https://www.genenames.org/data/genegroup/#!/group/1990
I think these transcripts might be connected to miRNA regulation and other types of under-represented forms of non-coding gene regulation:
see https://www.ncbi.nlm.nih.gov/pmc/articles/PMC6468922/
...but what is unique about the concept is that they are likely transcribed WITH a partner gene sharing a bidirectional promoter. This is an area of research, it exists, but right now? Expressing these computationally for RNAseq and expression studies in GFF is limited - correct me if i am wrong.
humbly submitted for your review,
apologies in advance if this is covered in some way by the SO already
Daniel J McGoldrick Ph.D

Thank you for your patience Dr. McGoldrick. It might take me a bit to review everything and get back to you, but you should be able to expect a response from me by next Thursday.

No problemo Evan,
Hope you are well
Daniel
On Thu, May 27, 2021 at 7:28 PM Evan Christensen @.***>
wrote:

Thank you for your patience Dr. McGoldrick. It might take me a bit to
review everything and get back to you, but you should be able to expect a
response from me by next Thursday.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/The-Sequence-Ontology/SO-Ontologies/issues/497#issuecomment-850065525,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AELLUI56X2W7SH47CAZVGKTTP35TVANCNFSM4SBBHS5Q
.

--
Daniel J McGoldrick Ph.D
UW Genome Sciences Center (GRC),
Center for Mendelian Genomics (CMG)
Box 355065Seattle, WA  98195(206) 685-7342

Sorry for the delay, we were waiting on a fix to OwlTools so that we can update all of the ontology files. That has been fixed so we can keep working through the queue again. Would you happen to be available next Thursday to discuss your request? If so, what time zone are you in? I think we can make some changes to the ontology as you suggest, but I have a couple questions to make sure I'm understanding correctly.

Closing since I haven't heard back in a while. Please reopen this issue if you'd like to continue this conversation.


H265 category not found

I heard spotweb is working on H265 category but I still can't find it. Is it a bug on my side or is the category not yet released to the public?

Where did your hear this?

Closing, no activity.


Change S0 notation in fitting functions

This is confusing that it is the signal, but it is rather the state/MZ magnetization
Maybe Mz0 ?

Changed


NFSIOStat Check

What does this PR do?
Adds a check for nfsstatio-sysstat
Motivation
Someone wanted one.
Testing Guidelines
I have a very simple test to ensure that the metrics exist. I need to mock them out before this can be approved
Additional Notes
Should we parse the data from /proc/self/mountstats ourselves?

I reference the man page in the comments in the check, but do not want to reproduce too much of it in the check comments. So, I am copying it here:
NFSIOSTAT-SYSSTAT(1)                                                           Linux User's Manual                                                          NFSIOSTAT-SYSSTAT(1)

NAME
       nfsiostat-sysstat - (the nfsiostat command from the sysstat package) Report input/output statistics for network filesystems (NFS).

SYNOPSIS
       nfsiostat-sysstat [ -h ] [ -k | -m ] [ -t ] [ -V ] [ interval [ count ] ]

DESCRIPTION
       The nfsiostat-sysstat command displays statistics about read and write operations on NFS filesystems.

       The  interval  parameter specifies the amount of time in seconds between each report. The first report contains statistics for the time since system startup (boot). Each
       subsequent report contains statistics collected during the interval since the previous report.  A report consists of an NFS header row followed by a line  of  statistics
       for  each  network filesystem that is mounted.  The count parameter can be specified in conjunction with the interval parameter. If the count parameter is specified, the
       value of count determines the number of reports generated at interval seconds apart. If the interval parameter is specified  without  the  count  parameter,  the  nfsio‐
       stat-sysstat command generates reports continuously.

REPORT
       The  Network  Filesystem  (NFS) report provides statistics for each mounted network filesystem.  Transfer rates are shown in 1K blocks by default, unless the environment
       variable POSIXLY_CORRECT is set, in which case 512-byte blocks are used.  The report shows the following fields:

       Filesystem:
              This columns shows the hostname of the NFS server followed by a colon and by the directory name where the network filesystem is mounted.

       rBlk_nor/s (rkB_nor/s, rMB_nor)
              Indicate the number of blocks (kilobytes, megabytes) read by applications via the read(2) system call interface. A block has a size of 512 bytes.

       wBlk_nor/s (wkB_nor/s, wMB_nor/s)
              Indicate the number of blocks (kilobytes, megabytes) written by applications via the write(2) system call interface.

       rBlk_dir/s (rkB_dir/s, rMB_dir/s)
              Indicate the number of blocks (kilobytes, megabytes) read from files opened with the O_DIRECT flag.

       wBlk_dir/s (wkB_dir/s, wMB_dir/s)
              Indicate the number of blocks (kilobytes, megabytes) written to files opened with the O_DIRECT flag.

       rBlk_svr/s (rkB_svr/s, rMB_svr/s)
              Indicate the number of blocks (kilobytes, megabytes) read from the server by the NFS client via an NFS READ request.

       wBlk_svr/s (wkB_svr/s, wMB_svr/s)
              Indicate the number of blocks (kilobytes, megabytes) written to the server by the NFS client via an NFS WRITE request.

       ops/s
              Indicate the number of operations that were issued to the filesystem per second.

       rops/s
              Indicate the number of 'read' operations that were issued to the filesystem per second.

       wops/s
              Indicate the number of 'write' operations that were issued to the filesystem per second.

OPTIONS
       -h     Make the NFS report easier to read by a human.

       -k     Display statistics in kilobytes per second.

       -m     Display statistics in megabytes per second.

       -t     Print the time for each report displayed. The timestamp format may depend on the value of the S_TIME_FORMAT environment variable (see below).

       -V     Print version number then exit.

ENVIRONMENT
       The nfsiostat-sysstat command takes into account the following environment variables:

       S_TIME_FORMAT
              If this variable exists and its value is ISO then the current locale will be ignored when printing the date in the report header.  The  nfsiostat-sysstat  command
              will use the ISO 8601 format (YYYY-MM-DD) instead.  The timestamp displayed with option -t will also be compliant with ISO 8601 format.

       POSIXLY_CORRECT
              When this variable is set, transfer rates are shown in 512-byte blocks instead of the default 1K blocks.

BUG
       /proc filesystem must be mounted for nfsiostat-sysstat to work.

FILE
       /proc/self/mountstats contains statistics for network filesystems.

WARNING
       The  nfsiostat command from the sysstat package (nfsiostat-sysstat) is now obsolete and is no longer maintained.  It will be removed in a future sysstat version.  Please
       use now the nfsiostat command from the nfs-utils package.

AUTHOR
       Written by Ivana Varekova (varekova <at> redhat.com)

SEE ALSO
       nfsiostat(8), sar(1), pidstat(1), mpstat(1), vmstat(8), iostat(1), cifsiostat(1)

Linux                                                                             JANUARY 2014                                                              NFSIOSTAT-SYSSTAT(1)

I realized that the man page says it's deprecated. I'm gonna rewrite this to use the proper one.

Here's the man file for the new one, we'll need to release an agent for this check to work. I will prepare a PR for omnibus-software.
nfsiostat(8)                                                                 System Manager's Manual                                                                nfsiostat(8)

NAME
       nfsiostat - Emulate iostat for NFS mount points using /proc/self/mountstats

SYNOPSIS
       nfsiostat [[<interval>] [<count>]] [<options>][<mount_point>]

DESCRIPTION
       The nfsiostat command displays NFS client per-mount statisitics.

       <interval>
              specifies  the  amount of time in seconds between each report.  The first report contains statistics for the time since each file system was mounted.  Each subse‐
              quent report contains statistics collected during the interval since the previous report.

       <count>
              If the <count> parameter is specified, the value of <count> determines the number of reports generated at <interval> seconds apart. if the interval  parameter  is
              specified without the <count> parameter, the command generates reports continuously.

       <options>
              Define below

       <mount_point>
              If  one  or  more  <mount point> names are specified, statistics for only these mount points will be displayed.  Otherwise, all NFS mount points on the client are
              listed.

       The meaning of each column of nfsiostat's output is the following:
               - op/s
                      This is the number of operations per second.
               - rpc bklog
                      This is the length of the backlog queue.
               - kB/s
                      This is the number of kB written/read per second.
               - kB/op
                      This is the number of kB written/read per each operation.
               - retrans
                      This is the number of retransmissions.
               - avg RTT (ms)
                      This is the duration from the time that client's kernel sends the RPC request until the time it receives the reply.
               - avg exe (ms)
                      This is the duration from the time that NFS client does the RPC request to its kernel until the RPC request is  completed,  this  includes  the  RTT  time
                      above.

       Note  that if an interval is used as argument to nfsiostat, then the diffrence from previous interval will be displayed, otherwise the results will be from the time that
       the share was mounted.

OPTIONS
       -a  or  --attr
              displays statistics related to the attribute cache

       -d  or  --dir
              displays statistics related to directory operations

       -h  or  --help
              shows help message and exit

       -l LIST or  --list=LIST
              only print stats for first LIST mount points

       -p  or  --page
              displays statistics related to the page cache

       -s  or  --sort
              Sort NFS mount points by ops/second

       --version
              show program's version number and exit

FILES
       /proc/self/mountstats

SEE ALSO
       iostat(8), mountstats(8), nfsstat(8)

AUTHOR
       Chuck Lever<EMAIL_ADDRESS>

                                                                                15 Apr 2010                                                                      nfsiostat(8)


[REQ] Do not open the keyboard when tapping on a trend

Describe the problem that needs solving
Currently when you tap a trend it focuses on the text field and opens the androids keyboard. This is a bit annoying.
Describe the solution you'd like
Add an option to disable this.

This is fixed in the latest v3.0.0-beta3. Please re-open if this is still an issue!


Parse Byron Base58 address using str reader

For some reason, we were using the auto reader to parse Base58
addresses in the Byron CLI.
Because the auto reader uses the Read typeclass, this would require
the user to specify the address on the command-line in an odd way, e.g.
'"base58AddressHere"' or \"base58AddressHere\".

bors merge


Use consistent conditionals in render_system.hpp

These header files define the XVisualInfo type, which is used later in this header based on different conditionals. In particular, the evaluation of these conditionals differ on BSD, which appears to have the headers needed so I don't believe that __linux__ is the correct conditional to use.
This was the only change I needed to make to rviz to build on FreeBSD.
Here's the spot where the type is used: https://github.com/ros2/rviz/blob/f7112b1ae4337363c4d8177bffe7cce6bbcabf29/rviz_rendering/include/rviz_rendering/render_system.hpp#L164-L168

Pulls: ros2/rviz#1294
Gist: https://gist.githubusercontent.com/ahcorde/6284765d50ba9fefda518b5807eba560/raw/1d04e083aa5b939c5615c0be959ec9465c24a9ee/ros2.repos
BUILD args:   --packages-above-and-dependencies rviz_rendering --packages-above-and-dependencies rviz_rendering
TEST args:  --packages-above rviz_rendering --packages-above rviz_rendering
ROS Distro: rolling
Job: ci_launcher
ci_launcher ran: https://ci.ros2.org/job/ci_launcher/14802

Linux
Linux-aarch64
Linux-rhel
Windows


Dynamodb StreamScan hangs forever if a client error happens

The code produces a stream from a None terminated queue.
However in the onError method of the subscriber, the exception thrown by the dynamo client is raised, but a None is not published to the underlying Queue and therefore the stream never terminates.

This can potentially be tested by injecting a dynamodb client that fails predictably (e.g. setting up the connection acquisition timeout of the underlying httpclient to 1 nano).


Ominous comment in symcopy.h

Looking through some source files, I have found an ominous comment in symcopy.h:
https://github.com/xianyi/OpenBLAS/blob/6bc079687fc09546d02e08951494c51baa9a5535/symcopy.h#L39C23-L39C24
This dates back to GotoBLAS, and the file has not seen any meaningful changes since then.
Does anyone have a guess what Goto et. al could have meant by "completely wrong", or is it lost to history?
The functions defined in it are getting used in kernel/generic/symv_k.c so they are certainly working to some extent.
I can try carefully reading the code in symcopy.h, to figure out if I can see any potential problems, but I am asking in case someone already knows.

No errors have been traced back to this in about 20 years, so I am inclined to read it as "this works, but it is a lot less elegant than I think it could be". Given that there is next to no development history from Goto's time(apart from research papers and release tarballs), it is even conceivable that he did rewrite whatever part it was that worried him, but did not want (or remember) to remove the comment right away

Thanks, I may go through the code anyways when I have the time.


Use a disclosure widget for language selection

Is your feature request related to a problem?
In #53 we're adding localization support for English and French. This is a simple link toggle being worked on for that issue, but it would be good to use a disclosure widget, incase we have additional locales to support in the future.
Describe the solution you'd like
@greatislander suggested using the disclosure widget (see: https://github.com/inclusive-design/guide.inclusivedesign.ca/issues/53#issuecomment-907804477 ) and referenced this example https://www.w3.org/TR/wai-aria-practices/examples/disclosure/disclosure-navigation.html
Additional context or notes
Depends on #53

I started looking into this as part of #53 but decided to move to its own issue so that we could get the localization changes in sooner. This will also be affected by changes to #54.
In progress work can be seen in https://github.com/jobara/guide.inclusivedesign.ca/commit/0e8ff1e5e85bd6adc8ee5136bf823d939768d622

@jobara can you add and add/remove the hidden attribute from the mobile and desktop navigation containers?


Bypassing automated crawler detection by Firewalls

Is there a solution for websites behind WAFs like PerimeterX, Cloudflare, Akmai etc.?

Thank you for raising this important question about bypassing Web Application Firewalls (WAFs) like PerimeterX, Cloudflare, and Akamai. While completely bypassing advanced WAFs can be challenging and may raise ethical concerns, Crawl4ai already has several features that can help mitigate some basic anti-bot measures:

User-Agent Customization: You can set a custom User-Agent to mimic legitimate browser requests:
crawler.crawler_strategy.update_user_agent("Your Custom User-Agent")

Proxy Support: Use proxies to distribute requests across different IP addresses:
crawler = AsyncWebCrawler(proxy="http://your-proxy-url:port")

JavaScript Execution: Crawl4ai can execute JavaScript, which is crucial for rendering dynamic content:
result = await crawler.arun(url="https://example.com", js_code="Your JavaScript Code")

Session-Based Crawling: Maintain sessions to mimic human-like browsing behavior:
result = await crawler.arun(url="https://example.com", session_id="unique_session_id")

Custom Headers: Set custom headers to include necessary cookies or authentication information:
crawler.crawler_strategy.set_custom_headers({"Cookie": "your_cookie_value"})

These features can help in many cases, but not specifically for WAFs, but for other applications we're considering features. like enhanced browser fingerprinting, CAPTCHA, human-like behaviour and more.
I'd love to hear more about your specific use case. Are there particular websites or WAFs you're encountering issues with?

could be nice if you can confirm your code can scrapy this page https://www.realestate.com.au/property-house-qld-indooroopilly-145860356? @unclecode


Add boardfarm recovery from a broken state

There are two parts to this task:
The physical setup needs to ensure that, even with the usb kmod failing, the ethernet connection lets boardfarm download an image to fix itself.
Apart from that the software needs to be able to recover itself from a fail state and flash a stable image, so that any PR that breaks boardfarm won't break all other PRs.

Surely if we use the u-boot consoles 'nand write' command over serial we could write the new images in an recoverable way?
Alternative is to do what we used to do on old projects and boot from JTAG


[Hub Generated] Review request for Microsoft.Aadiam to add version stable/2020-03-01

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
Latest improvements:

### Contribution checklist:
- [ ] I have reviewed the [documentation](https://github.com/Azure/azure-rest-api-specs#basics) for the workflow.
- [ ] [Validation tools](https://github.com/Azure/azure-rest-api-specs/blob/master/documentation/swagger-checklist.md#validation-tools-for-swagger-checklist) were run on swagger spec(s) and have all been fixed in this PR.
- [ ] The [OpenAPI Hub](https://aka.ms/openapiportal) was used for checking validation status and next steps.
### ARM API Review Checklist
- [ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
- adding/removing APIs.
- adding/removing properties.
- adding/removing API-version.
- adding a new service in Azure.
Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

Please do not change the default template of description, this is used by BOT to identify the type of changes.
Please go through the contribution checklist and ARM API Review Checklist added as part of the review and mark them completed. It will help you fix most of the issues and improve the quality of swagger and help close the PR faster. This is a requirement before review can be continued.

@jianyexi previous lintdiff had the following errors:
The response is defined but without a default error response implementation.Consider adding it.'
The schema 'ErrorResponse' is considered an object but without a 'type:object', please add the missing 'type:object'.
current lintdiff has these errors:
The new version adds a response code 'default'.
The new version has a different type 'object' than the previous one ''.
Looking for guidance, is this a required breaking change for PR approval?

The new version adds a response code 'default'.

this change needs a breaking change approval


Use debian stretch and geos 3.5 in Docker image, Update logging levels

Upgrade from geos 3.4.2 to 3.5.1 (via stretch instead of jessie) in Dockerfile
Log zones without name as DEBUG instead if WARN

Before merging, I need to confirm it runs without problem on a planet file.

The docker image run on a planet file successfully :tada:
I also changed a log level (on a missing level in libpostal rules) from INFO to DEBUG.


Provide a Purl in the root component of the SBOM

What would you like to be added:
A Package Url from the docker image is missing in the generated SBOM.
Could you please provide the purl for the root component (metadata.component.purl)?
Here you can find examples for purls from docker images: https://github.com/package-url/purl-spec#some-purl-examples.
Why is this needed:
This is needed to have a specific identifier for an artifact deployed from a docker image.
Additional conext:
There is an "Executive Order on Improving the Nation’s Cybersecurity" providing urgency about delivering sboms for your published products to be compliant. For docker images, you should be able to map your archived sboms to your deployed artifacts via an identifier (purl).

Great idea!
In the internal model this could probably go in the source.Metadata (needs more thought), and for each format we'd need to identify the correct location in the SBOM (seems like you're referring to CycloneDX for metadata.component.purl, yes?).

Yes, you're right, I am referring to the CycloneDx format.

Hello @wagoodman,
is there anything planned by your side related to this?

Hello @wagoodman, is there anything planned by your side related to this?

I have not seen that you added this to your backlog. Sorry for the inconvenience, thanks a lot! 🚀

Yes, we've added this to the backlog and will get to it in due time. Thanks, @MeikelVielhauer!


fsnotify: correctly check for event operation

fsnotify Event.Op is a bit mask and testing for strict equality might
not detect the event operation correctly.
This patch make it so we check for fsnotify event operation
consistently as documented at https://github.com/fsnotify/fsnotify.

test-me-please

@kAworu This probably needs backporting, right?

retest-runtime


Handle associations properly

default factory generator handles the references properly

Thanks for the patch, but we only pull in changes with tests. I'm closing this, but feel free to open a new pull request with tests.


Leverage Terraform resource providers

Is your feature request related to a problem? Please describe.
I would really like a LOT more content for Lyra. Doing incremental content releases is good, but to prove out what Lyra can do, it needs a lot more content to be useful.
Describe the solution you'd like
It would be really great if Lyra could leverage Terraform's resource providers. They already have a ton of content that would be awesome if we could use without re-inventing the wheel.
Additional context
Prior art in this space:

Pulumi Terraform bridge
CloudFormation bridge

I think we have the core functionality here working. What do you think about closing this issue? There is probably an endless stream of work we can do in this area, like bridging more providers or fixing edge cases, but I think we can track that as individual issues.

Sounds good 👍 @ahpook ?

👍 i will make a new epic that has some specific high-value providers to add. could be a good starting point for new contributors


can't find API

Loving Infinitive, but I can't seem to GET any of the API except /api/zone/1/config.
../heatpump and ../airhandler produce a 404?
Any thoughts? Any way I can help contribute (logs or similar)?
Thanks!

Which version are you running?
The code on acd/infinitive master should have the api at host:port/api/zone/1/heatpump etc.
For my branch - will1604/master they're at  host:port/api/heatpump etc. As the heat pump and furnace/fan coil are not specific to a zone I was proposing the zone out of the URL.

built from source, works great!


fix json parse and split not defined issues

the problem is, that "window.addEventListener('message', listener, false)" attached to all "message" events, that will be triggered on hubs window and it is possible, that some other modules calls "postMessage" on hub, so following errors shows up on the browser console:
Example: $("#CrossStorageClient-XXX")[0].contentWindow.postMessage("bla", "http://localhost")
Error: Uncaught SyntaxError: Unexpected token br._listener @ xshub:11
or
Example: $("#CrossStorageClient-XXX")[0].contentWindow.postMessage('{"bla":"bla"}', "http://localhost")
Error: Uncaught TypeError: Cannot read property 'split' of undefinedr._listener @ xshub:11

Looks good, thanks!

Thanks for the speedy feedback, can you please bump the bower and npm version, build and publish?


document -a

in the usage/help message

I should probably remove -a instead because -fdump-ast is a preferred (and documented) option.

Removed in 7f4172dc2b2b449ede248280ec48d64fb633d0dd.


Update 4.x example

Update the example for 4.x so that it works with the current tip of the 4.x branch.
Closes #2552

Coverage remained the same at 97.405% when pulling 7a6059ef73bfdbb076b09fff38b684609331d4fd on akrabat:update-example into 94b7634a11ad64e865f66fe821c16f7427e6ea02 on slimphp:4.x.

In a future version I would add links to the documentation for each step.

Agreed.
Thanks for looking over it!


x/pkgsite: align attribute gets stripped from headings in README.md

What is the URL of the page with the issue?
<EMAIL_ADDRESS>What is your user agent?

Mozilla/5.0 (X11; Linux x86_64; rv:96.0) Gecko/20100101 Firefox/96.0
Screenshot

What did you do?

Here is the source of the README: https://raw.githubusercontent.com/Snaipe/boa/9ac3c07bc342a675b3bd5dbda8ca58c5c5b0ea96/README.md
You'll notice on the first line that the <h1> tag has align="center".
What did you expect to see?
I expected the image to be centered. Github renders the image as such: https://github.com/Snaipe/boa/blob/9ac3c07bc342a675b3bd5dbda8ca58c5c5b0ea96/README.md
What did you see instead?
The image is not centered. It seems to be because the align attribute is not allowed in the sanitized HTML: https://github.com/golang/pkgsite/blob/a70a3c2b473c9294b83bc93a6068c8ebcc9c4ecb/internal/frontend/readme.go#L169
I think allowing the attribute on heading seems innocent enough. Thoughts?

A workaround for this issue seems to wrap the HTML with an outer <div> and put the align tag on that div. The result is indeed centered.

I think it is reasonable to allow the align attribute.


Can't start the Time Entry in some scenarios

Mari reported that she can't start the Time Entry by pressing the Start button in Timer Bar.
We have to investigate it carefully.
💻 Environment
Platform: macOS
OS Version: macOS 10.14
Toggl Version: Stable 7.4.330
🐞 Actual behavior

Sometime, we can't start the Time Entry, even we already fill the Description in TimerBar
Restart the app will resolve this problem

💯 Expected behavior

Should work as expected 💯

It is fixed in latest beta with 488fb120d0fd81b9f4f7ac46b10b093966c87ab6


fetch api built

@jerinpetergeorge Is this pr still relevant? Seems an API endpoint is already accessible. Else clarify.
Cheers.


Change priorities

I couldn't figure out how to change the priority of an already installed constraint.
Changing the priority of an NSLayoutConstraint is a cheap operation, and using a combination of priorities and .LessThanOrEqual + .GreaterThanOrEqual for animations is what Apple suggests.
It may even be nice to add some wrapper for this. You'd install
x ≦ 40
x ≧ 40 with priority P
x ≧ 20 with priority P + 1

and you'd then be able to switch x between 40 and 20 by changing the priority on the last constraint between P - 1 and P + 1.

It's probably best we allow altering priorities via snp_updateConstraints. I'll see what this would entail and if it would have any implications.

@danieleggert the develop branch now has support for updating priorities:
var constraint: Constraint? = nil
view.snp_makeConstraints { (make) -> Void in
    constraint = make.edges.equalTo(UIEdgeInsetsMake(10,10,10,10)).priorityHigh()
}
constraint?.updatePriorityLow()

Hi @robertjpayne !
I'm trying to update priority as stated on the last comment.
But i Got this error:

What seems to be the problem? Using Snapkit 4.0.0

Worth to mention that it is not allowed to change priority from .required to lower value.


Feature/jolokia plugin

I wrote a simple JVM plugin based on jolokia rest api.
I needed to add some new methods in testutil/accumulator.go hence I refactor the oldest to use them.

@saiello can you please write a README for this plugin?
you can use the CPU readme as an example: https://github.com/influxdb/telegraf/blob/master/plugins/system/CPU_README.md

@saiello, I'm not super familiar with JMX/jolokia/MBeans, but it seems like this information is more generically called an mbean? Should the plugin be called mbeans or JMX?

@saiello nevermind about renaming the plugin, I get it now, jolokia is good :+1:

Once you write a README and address my comments I'll merge it, thanks a bunch @saiello!

@sparrc I added a README to jolokia plugin. I hope to have fixed the indentation as well :grin: Thanks

thank you @saiello!


Issue40

This pull request prepares the code in the module to address issues #40 and #115.
I want to merge it now so there are not too many divergences from the main branch.

I tried it out and I see that the "0" are not removed anymore. They should be replaced by "NA".


Getting Login failed

Description of the issue
I have setup an application account in Secret Server, and I have verified that it works by trying the Windows TSS SDK client.
Now, when I'm trying with the Go SDK, setting TSS_USERNAME to my application account name and having tried with TSS_PASSWORD set to either the SDK key or the application account's password and passing in a secret to retrieve - I get "Login failed".
Obviously, I missing something fundamental here, but I fail to understand what.
With the Windows TSS SDK client, you initialize the SDK with the URL, key and role, but I don't see anything equivalent in the Go SDK?

Forgot to mention that in the Go SDK, I have also set the TSS_TENANT to a valid value

TLD is com, so not setting that.
Tenant is cloudsg (full URL https://cloudsg.secretservercloud.com/)
What value should be used for TSS_PASSWORD? SDK key?

TSS_PASSWORD=ActualAccountPassword
To debug if needed, navigate to https://cloudsg.secretservercloud.com/, select "Local Login" and enter the username/password you are using with the tss-sdk-go API calls.

Im not familiar enough with the windows sdk to advise. The go sdk does not require initialization.

@tibco-postman Can you try to get token using your application account username and password through postman first. You can refer secret server rest API guide for this https://cloudsg.secretservercloud.com/RestApiDocs.ashx?doc=oauth-help.

I've verified that Webservices is enabled, but still get "Login Failed".
Tried using Postman, same result:

I managed to get the Postman call to work. What was needed was to add the parameter domain to the call.
Adding that to the Credentials var made things work!
Thanks for help!


Remove dependency from mina_numbers from compile config

#14516 introduced a dependency on mina_numbers for mina_compile_config. This broke the build of src/nonconsensus (see https://buildkite.com/o-1-labs-2/mina-end-to-end-nightlies/builds/1273#018d686f-508b-4630-b49e-3dddd6ee9e7d).
This PR removes that dependency by making the parameters int and delegation to runtime_config the conversion to Global_slot.t, as it happens already in other branches.

!ci-build-me

!ci-nightly-me

!ci-build-me


[BREAKING] Transition from Tapir to Mooncake

[!WARNING]
Breaking change: AutoTapir is no longer supported, replaced by AutoMooncake (see https://github.com/SciML/ADTypes.jl/pull/89)

DI deps

[x] Replace Tapir with Mooncake, bump ADTypes compat

DI extensions, tests, CI

[x] Rename everything from Tapir to Mooncake
[ ] Handle new Mooncake.Config (ping @willtebbutt)
[ ] Implement multi-argument support
[ ] Reactivate other tests

I think multi-argument support is operational, care to take a look? All you need to know is that:

contexts can contain any number of arguments (including 0), wrapped in specific types like Constant <: Context
one can access the actual data with unwrap, e.g. unwrap(Constant(c)) == c


Bug report: Flink cannot list file status through object storage interface

Describe the bug
Using ChubaoFS as storage of Flink through s3.
Calling the listStatus() method does not get any data.
Environment
SDK info:
aws-sdk-java/1.11.271 Linux/3.10.0-693.5.2.el7.jd_3313.x86_64 Java_HotSpot(TM)_64-Bit_Server_VM/25.131-b11 java/1.8.0_131 scala/2.11.12, presto

To Reproduce
Using ChubaoFS as storage of Flink through s3 and calling the listStatus() method to list file status which store in ChubaoFS.
Expected behavior
Method returns status of files.
Additional context
NONE.

This compatibility issue was resolved by adjusting the xml structure of the ListObjects interface response body.
Modify name of xml root node from ListBucketResults to ListBucketResult.
Following java SDK have been tested:
AWS S3 SDK v1
<dependency>
            <groupId>com.amazonaws</groupId>
            <artifactId>aws-java-sdk-s3</artifactId>
            <version>1.11.437</version>
        </dependency>

AWS S3 SDK v2
<dependency>
            <groupId>software.amazon.awssdk</groupId>
            <artifactId>s3</artifactId>
            <version>2.10.24</version>
        </dependency>

The fix code for this issue is included in the PR #428 .


Does this still work?

Yes, I'm only using it for one troublesome bulb that kept falling off my ZHA coordinator. Connected to the Sengled hub, the bulb is stable.
This integration is allowing me on/off control, brightness, and white hue.
It's not as foolproof as a directly connected bulb to Home Assistant, but works.


[Accessibility]A11y_VSCode_ShowOpenedEditors_keyboard: after clicking on "Tab" key the opened "Editor" get closed

Environment Details:
VSCode Version : 1.24.0
OS Version : MAC OS HighSierra10.13.5
Additional Details:
Keyboard,MAS3.2.1,MAS2.1.1,MAS2.4.3
Repro Steps:
1.Launsch VsCode
2.Navigate   to welcome screen and beside opened editors pane at top(in middle   pane)->Select More(…)->Select "Show Opened Editors" from   dropdown.
3.Click on "Tab" key.
4.Observed that, after clicking on "Tab" key then opened "Editor" get closed.
Actual:
When user click on "Tab" key then opened "Editor" get closed.
Expected:
When user click on "Tab" key then focus should goes on expanded dropdown values instead of closing the opened "Editor".
Recommendations:
Refer below link which is repository of bug fixes code snippets:
https://microsoft.sharepoint.com/teams/msenable/mas/Pages/browse-fixes.aspx
User Impact:
User will get confused on which key the proper action will performed
MAS Reference:
MAS3.2.1: https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={a4bbd37d-ee11-485e-b5c8-0539f0ac94b2}
MAS2.1.1: https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={8492c4eb-c179-40ae-8777-cd044ed725a2}
MAS2.4.3: https://microsoft.sharepoint.com/:w:/r/teams/msenable/_layouts/15/WopiFrame.aspx?sourcedoc={0de7fbe1-ad7e-48e5-bcbb-8d986691e2b9}
Attachment For Refernce:
a.pptx
Does this issue occur when all extensions are disabled?: Yes

/duplicate #51850


[Question]: Add additional html

Hi,
as I can see, there is no possibilty to add aditional attributes like following, right?
e.G:
<input type="text" size="2" data-encrypted-name="expiryMonth"/>`

Thanks in advance.

At the moment, there is no support for attributes that VFG does not recognize.  You can, however, implement a custom field and add support for your attributes there.

ok. I see. I'll to figure it out.
Thanks for the hint.

I think I've come up with a quick and easy way to add support for "additional attributes" by modifying "abstractField" and adding an "attributes" directive.
	directives: {
		attributes: {
			bind: function(el, binding, vnode) {
				let attrs = objGet(vnode.context, 'schema.attributes', []);
				forEach(attrs, (val, key) => {
					console.log('v-attributes', key, val);
					el.setAttribute(key, val);
				});
			}
		}
	},

We can then use this directive on the input elements of the various components, to add support for unknown attributes (such as "data-toggle", "data-target", etc).
We can extend this functionality even further by adding support for "wrapper attributes, input attributes, label attributes, etc" ...
	directives: {
		attributes: {
			bind: function(el, binding, vnode) {
				let attrs = objGet(vnode.context, 'schema.attributes', []);
				let container = binding.value;
				if(isString(container)) {
					attrs = objGet(attrs, container, []);
				}
				forEach(attrs, (val, key) => {
					console.log('v-attributes', key, val);
					el.setAttribute(key, val);
				});
			}
		}
	},

We would then use this in the field* templates like:
<template lang="pug">
  .wrapper(v-attributes="'wrapper'")
    input.form-control(
      // clipped
      v-attributes="'input'"
</template>

The field schema could then look like this:
{
  type: "input",
  inputType: "text",
  label: "My Input",
  model: "myText",
  attributes: {
    input: {
      data-toggle: "tooltip",
      title: "Custom Tooltip Text for Bootstrap Tooltip"
    }
  }
}

We could use inputAttributes, wrapperAttributes, etc rather than a nested object structure ...

We could also simplify the templates for things like fieldInput where certain attributes are simple ... such as "disabled", "formmethod", "autocomplete", etc ... these could all be removed from the template and just merged into the attributes directive ... by pulling them out of the schema using an array of white-listed schema properties.
This would take the fieldInput.vue template, which currently looks like this:
<template lang="pug">
.wrapper(v-attributes="'wrapper'")
	input.form-control(
		:id="getFieldID(schema)",
		:type="schema.inputType.toLowerCase()",
		:value="value",
		@input="onInput",
		@blur="onBlur",
		:class="schema.fieldClasses",
		@change="schema.onChange || null",
		:disabled="disabled",
		:accept="schema.accept",
		:alt="schema.alt",
		:autocomplete="schema.autocomplete",
		:checked="schema.checked",
		:dirname="schema.dirname",
		:formaction="schema.formaction",
		:formenctype="schema.formenctype",
		:formmethod="schema.formmethod",
		:formnovalidate="schema.formnovalidate",
		:formtarget="schema.formtarget",
		:height="schema.height",
		:list="schema.list",
		:max="schema.max",
		:maxlength="schema.maxlength",
		:min="schema.min",
		:minlength="schema.minlength",
		:multiple="schema.multiple",
		:name="schema.inputName",
		:pattern="schema.pattern",
		:placeholder="schema.placeholder",
		:readonly="schema.readonly",
		:required="schema.required",
		:size="schema.size",
		:src="schema.src",
		:step="schema.step",
		:width="schema.width",
		:files="schema.files"
		v-attributes="'input'")
	span.helper(v-if="schema.inputType.toLowerCase() === 'color' || schema.inputType.toLowerCase() === 'range'") {{ value }}
</template>

and make it look like this:
<template lang="pug">
.wrapper(v-attributes="'wrapper'")
	input.form-control(
		:id="getFieldID(schema)",
		:value="value",
                :disabled="disabled",
		@input="onInput",
		@blur="onBlur",
		:class="schema.fieldClasses",
		@change="schema.onChange || null",
		v-attributes="'input'")
	span.helper(v-if="schema.inputType.toLowerCase() === 'color' || schema.inputType.toLowerCase() === 'range'") {{ value }}
</template>

We would then whitelist the following properties, accept, alt, autocomplete, checked, dirname, formaction, formenctype, formmethod, formnovalidate, formtarget, height, list, max, maxlength, min, minlength, multiple, name, pattern, placeholder, readonly, required, size, src, step, width, files ...
Alternatively, we could create a list of "internal" properties, such as type, inputType, disabled, required which would be shorter ... and then use lodash's filter to create a version of the schema property without the internal properties, anything that's not used internally would then just be passed to the attributes directive and attached to the appropriate element (usually the 'input').

Ok. Thanks for your answer.
To be honest, I do not have any clue to get this running in my component.
I am new to vue, so this is very challenging.

@maximaexchen sorry, I hijacked your question and turned it into a feature request.
For now, what you'd want to do is create a custom field component, following the instructions in the docs.
You would then add support for your custom attributes in the custom field, and refer to that field in your form schema.

ok. good to know. :-)
Are there any practical examples for custom fields? I don't get it.
I have following warning:
[Vue warn]: Property or method "cvc" is not defined on the instance but referenced during render. Make sure to declare reactive data properties in the data option.

main.js
import fieldCvc from "./components/fieldCvc.vue";
Vue.component("fieldCvc", fieldCvc);

Here is my "fieldCvc.vue":

<template>

            <input
                    class="form-control"
                    type="text"
                    v-model="cvc"
            >

</template>

And here the form:
<template>
    <form-wizard @on-complete="onComplete"
                 shape="tab"
                 back-button-text="zurück"
                 next-button-text="weiter"
                 finish-button-text="Abschließen"
    >

Ihr  Model

        <tab-content title="Ihr Paket"
                     icon="ti-user" :before-change="validateFirstTab">

            <vue-form-generator :model="model"
                                :schema="firstTabSchema"
                                :options="formOptions"
                                ref="firstTabForm"
            >

            </vue-form-generator>

        </tab-content>

        <tab-content title="Zahlungsmethode"
                     icon="ti-settings" :before-change="validateSecondTab">

            <vue-form-generator :model="model"
                                :schema="secondTabSchema"
                                :options="formOptions"
                                ref="secondTabForm"
            >
            </vue-form-generator>

        </tab-content>

        <tab-content title="Persönliche Angaben"
                     icon="ti-check">

Your json is ready!

        </tab-content>

    </form-wizard>
</template>

maybe you could give me a hint?
Or a catchword I can google for. I have also no idea to implement my
data-encrypted-name="expiryMonth" to be filled.
Thanks in advance.

The "v-model" would use the "value" property, inherited from abstractField.
As for the custom html attributes, you would just implement these by adding them to your form schema ...
{
  type: "cvc",
  label: "your label",
  model: "model",
  encryptedName: "expiryMonth"
}

You would then use these in fieldCvc.vue in the template like so:

<template>

            <input
                    class="form-control"
                    type="text"
                    v-model="value"
                    data-encrypted-name="schema.encryptedName"
            >

</template>

I would recommend using the fieldInput.vue as a boilerplate though, to ensure you bring over all the needed attributes ...
I'd recommend against using "row" and "col-sm/col-md" classes in your component, and instead using the "styleClasses" properties provided by VFG and the .wrapper class for your components top-level element, as this will ensure maximum compatibility and reduce headaches later when you're trying to figure out why certain fields are acting differently than others after updating site styles.

Thank you very much for the advice and the demo. Helped me a lot!
The wrapper thing is not that clear by now. Do you mean I should use pug?
Ther rest is working now.

By wrapper, I mean ...
<template>

</template>

Which, in the pug templates, looks like this:
<template>
  .wrapper
</template>

Just suggesting that your custom fields follow the same markup and css classes as other VFG fields, to prevent headaches in the future trying to figure out why your custom fields are different than the VFG fields in the browser.

dynamic attributes are now supported in v3, but unfortunately they do not exist in the v2 branch.  I'm closing this issue as it has been resolved for a future release.


Create value choice menus for each term in register

we need to provide all potential values for the terms in light of future updates, and describe those here

Habitats:
marine
estuarine
terrestrial
freshwater

combinations
e.g. marine | estuarine, marine | terrestrial, marine | freshwater, marine | estuarine | freshwater | terrestrial etc. etc.

hope you guys can assist in doing this in a non-manual fashion...

@timadriaens, I'm assuming that the sequence is not important, so marine | estuarine is the same as estuarine | marine?

Where would these values lists be used?
I would argue we need to normalize the data first (e.g. splitting habitat information in several rows). This is also done in a Darwin Core Archive. We can then just use the controlled vocabulary, rather than providing every permutation of combinations.

Just for reference: this has been done by @stijnvanhoey at https://github.com/inbo/alien-species-checklist/commit/4c0c1034a0b5dc6e1e283b5020cb4609b98df827


Feature/pretty output

What is the progress of this?
Please produce a screenshot of the pretty output. We can use that screenshot at https://github.com/fulldecent/structured-acceptance-test/blob/master/implementations/ruby/README.md

In this PR done:
Update our Ruby implement to add this outputting option
Update example consumer from https://github.com/fulldecent/structured-acceptance-test/issues/25 to use this new outputting format

Default output:

Output with -s (simple output) option:


Test stub matching partial function mapping request to response

Allows test stub to match partial function like:
stub.whenRequestMatchesPartial({
  case r if r.method == Method.POST => Response(Right(10), 200, Nil, Nil)
  case r if r.uri.path.endsWith(List("partialAda")) => Response(Right("Ada"), 200, Nil, Nil)
})

Could you also add docs here: https://github.com/softwaremill/sttp/blob/master/docs/backends/testing.rst & to credits: https://github.com/softwaremill/sttp/blob/master/docs/credits.rst ?

Docs added

released in 1.0.1


Triton and twenty first re exports pr

For your consideration.
As I understand it, the dependency tree for triton/neptune crates logically looks like this:
neptune-core
 |- tasm-lib
      |- triton-vm
           |- twenty-first
               |- bfieldcodec_derive

and maybe some more, but those are the one's I'm most interested in right now.   But instead here is the actual output of cargo tree, with version info stripped:
$ cargo tree --no-dedupe -f "{lib}" | grep "neptune\|twenty\|triton\|tasm\|bfield"
neptune_core
├── tasm_lib
│   ├── derive_tasm_object
│   ├── triton_vm
│   │   ├── twenty_first
│   │   │   ├── bfieldcodec_derive
│   └── twenty_first
│       ├── bfieldcodec_derive
├── triton_vm
│   ├── twenty_first
│   │   ├── bfieldcodec_derive
├── twenty_first
│   ├── bfieldcodec_derive

This PR is aimed at moving us towards the first dep tree.
This PR does two things, in two separate commits:

re-exports triton_vm and triton_vm::twenty_first in lib.rs like so:

pub use triton_vm;
pub use triton_vm::twenty_first; // less verbosity

changes all use twenty_first:: statements to use crate::twenty_first.

The purpose of [1] is to help out crates that depend on us (eg neptune-core), so they don't have to specify a version of triton_vm or twenty_first, but automatically get our version.
The purpose of [2] is so that we are using the twenty_first from triton_vm and don't need to have a dep of our own.
Unfortunately [2] is complicated by a strange situation with bfieldcodec_derive::BFieldCodec, which hard-codes string references to ::twenty_first in its derive macro, forcing crates that use it to have a dep on twenty-first.   So until that is resolved tasm-lib won't compile without a twenty-first dep, and thus I left it in.
As for resolving it, the simplest thing, to my mind, is to move bfieldcodec_derive::BFieldCodec into twenty-first.  But then I do not know any history of why it is a separate crate, or why I can't seem to find the repo for it.
[2] is a much bigger change, as it touches a lot of source files.  I made this separate commits, so that if [2] is not accepted, hopefully we can still get [1] merged.
my motivation:
Mainly just to cleanup deps, and minimize dependency-hell in accordance with rust best practices.
But also, I have in the past encountered conflicts in neptune-core where this would have helped.

Final thought:  this PR is just for triton_vm and twenty_first that I know are used in the public API.   There may well be types from other crates exposed in the API.   So best practice would be to review the public API for such cases.

bfieldcodec is located here:
https://github.com/Neptune-Crypto/twenty-first/tree/master/bfieldcodec_derive
Maybe this line and its explanation provide some relevant info about the twenty_first hard-coded crate name.
https://github.com/Neptune-Crypto/twenty-first/blob/10afd069f0de8de0d693bca291fb0f06b4961a16/twenty-first/src/lib.rs#L19

bfieldcodec is located here: https://github.com/Neptune-Crypto/twenty-first/tree/master/bfieldcodec_derive

thx!

Maybe this line and its explanation provide some relevant info about the twenty_first hard-coded crate name. https://github.com/Neptune-Crypto/twenty-first/blob/10afd069f0de8de0d693bca291fb0f06b4961a16/twenty-first/src/lib.rs#L19

yes I read that comment before.  It speaks to intent, but not really why a derive macro needs to be hard-coding a crate name.  I've never written a derive macro, so I can't speak to what is or isn't possible.  It's just that I don't believe I've ever seen behavior like that before in any macro from a public crate, so I feel like there must be another way to do it.
That said, I have an idea for a work-around to achieve my goal without altering the macro much.   Basically, I just replaced all ::twenty-first in the macro with crate::twenty-first.  Then, so long as the depending crate places a use twenty_first in lib.rs, it should work.  And that could actually be a use triton_vm::twenty_first, for example.  So no Cargo.toml dep required.  So far the bfieldcodec_derive crate compiles fine with that change, but I haven't tried to build any dependent crate yet.   getting late here, will try in the am.

yeah, so as commented in https://github.com/Neptune-Crypto/twenty-first/pull/180, this approach is working, so I think we should go ahead and merge both PRs.
$ cargo tree --no-dedupe -f "{lib}" | grep "triton\|twenty\|neptune\|tasm_lib\|bfield"
tasm_lib
└── triton_vm
    ├── twenty_first
    │   ├── bfieldcodec_derive

But let me know if there are concerns.   I will wait until Monday if I don't hear anything before.


TypeError thrown by document_table in getWhereForDoc

I have run into TypeError being throw when evaluating the conditions == "*" line in getWhereForDoc. Conditions here is set to the defaults found in arg_types.js. When I examine the conditions object, it is just prototype, nothing else there. This seems consistent with the behavior lined out in arg_types.findArgs().
Should this (document_table.js line 88:34 )be a non-coercive call?
Where can we set these conditions?  I don't see it as an argument to document_table.js.findDoc().

I hate to say I have no idea what you're talking about :/ can you show me your failing code and the error you're getting? I'll do my best to help.

We've updated several of our project's dependencies. Upon doing so line 99 in document_table.js started throwing a TypeError. Here is the stack trace:
160809/135207.679, [error] message: Uncaught error: Cannot convert object to primitive value stack: TypeError: Uncaught error: Cannot convert object to primitive value
    at __dirname.getWhereForDoc (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/massive/lib/document_table.js:88:34)
    at exports.findDoc (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/massive/lib/document_table.js:76:20)
    at Object.services.find (tasks.js:84:24)
    at handler (task-find-get-config.js:25:63)
    at Object.internals.handler (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/hapi/lib/handler.js:96:36)
    at Items.serial (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/hapi/lib/handler.js:63:26)
    at done (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/hapi/node_modules/items/lib/index.js:31:25)
    at done (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/hapi/node_modules/items/lib/index.js:63:25)
    at pre (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/hapi/lib/handler.js:49:28)
    at finalize (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/hapi/lib/handler.js:281:20)
    at wrapped (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/hapi/node_modules/hoek/lib/index.js:872:20)
    at internals.Response._processPrepare (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/hapi/lib/response.js:457:16)
    at internals.Response._prepare (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/hapi/lib/response.js:396:21)
    at process.nextTick (/home/jadams/projects/generators/generator-samples/hapi-app/todo-list/app/node_modules/hapi/lib/reply.js:151:22)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)

The code in question is the second part of the OR statement:
|| conditions == "*")
I think this should be:
|| conditions === "*")
The change does solve my problem. However, I am not a javascript expert and wanted to call it out here. There may be a legitimate reason why you chose the coercive syntax. Note that by changing it to ===, the code evaluates to false as I would expect. It does not attempt to convert {} to a string.
'conditions' itself is populated in arg_types.js.searchArgs, where the default is set to {}. That is the value the 'conditions variable' that is causing the error.  I would also like to know how to set that value instead of taking the Default. This might also help me solve the problem without requiring a change here.

I do appreciate you troubleshooting this for me, however I'm still very unclear on what the problem is. I can't tell from the code you've provided what is actually triggering this error.
Let's try this again.
You're passing Massive something and I need to know what that is. Specifically: what is the API call you're making. I can tell that tasks is your document table and you're trying to find something, but without knowing the criteria (and options) it's impossible to troubleshoot this.

we are trying to find all tasks with the query {} and setting limit and offset.
var query = {};
var options = {
  limit:10,
  offset: 0
};

db.tasks.findDoc(query, options, function (err, tasks)  {
    // do something
});

I did some more work on this today. Turns out upgrading hapi.js from 11.x to 12.+ causes the condition to manifest.  For now we are staying at hapi 11.x till I get this figured out.  Also, I am currently putting together a hapi project using massive to attempt to reproduce minus the complexity of the rest of our project. I am having no luck here either. I have no idea what code state is actually triggering the error :/

Wild. I'll be ditching the Args library in v3... man I just need to finish this project I'm on and we're off...

Don't case this for now. I'll keep working my end. I suspect its one of our dependencies somewhere that causes the problem. I'll reopen if I can ever reproduce in a simple project.


Text Classification -> term frequency inverse document frequency

Implement term frequency inverse document frequency classification and see whether it is applicable for the project or not

done


Remove API docs from README

Also removes the packageManager I added to package.json accidentally

@jaakkonakaza, go ahead and nuke the Usage info as well and then this is perfect. All that info is already on the doc site. Then this is ready to go.