Unclear how to turn off "listening for events" notification

I looked through all the options twice to figure out how to turn off this notification, then after googling it, I found issue #300, which explained it goes away when turning off "enable background sync". The "enable background sync" setting should clearly state that it has a persistent notification, and the notification itself should have text that matches with the setting that enables it, for example, instead of "listening for events", it should say "background sync", to correspond for the setting. Also, there is a section called "notifications", and a setting "enable notifications for this account", if you turn it off, all notification section settings turn off, but the persistent notification stays. This is a horrible misleading ui and needs to change somehow.
Also, separate bug probably, it would be nice if we could have no notification: I run syncthing which does background syncing with no notification.
I'm using version 5.5.4 from f-droid.

Yes, please add an option to toggle this off.
Yes, some ROMs (eg. Huawei or Xiaomi) are too aggresive at killing the apps, but plenty others are not, exclude it in Doze and carry on.
Eg. Conversations, I've tested it (without GCM!) with Sony 5.1.1/6.0.1 and Samsung 5.0.2/6.0.1 and it always worked great without the need to force the foreground service (and the obligatory permanent notification).

I would also like having an option to hide this notification (while keeping all other event notifications).

One more option could be to stop and start the service for every sync. This should hide the notification for most of the time and when visible it would convey some meaning to the user.
Since the default sync interval is 600 seconds and a typical sync request might last for about 6 seconds, the notification will be visible only for 1% of the time.

Yes, please add an option for this, it’s really annoying.

On Android O you can disable the notification channel for that notification.
Go to your phone Settings -> Apps & notifications -> Riot.im -> App notifications and disable the "Listen for events" category. That way you still get every other notification from Riot but the persistent "Listening for events" is disabled.
I additionally excluded Riot from battery optimizations to make sure it is not killed. I have not yet missed any messages.

@flocke unfortunately still Android N.

Here is some information on the options in Conversations. When the app is first installed, the user does not recieve any prompts, but shortly after installing, I got the following dialog.

That was followed by another dialog which I assume is from the operating system instead of the app itself.

In the settings, conversation has an option to enable a foreground service seen below.

The notification does not show up on the bar normally, but when the notification bar is expanded you can see the Conversations service notification.

Conversations works perfectly fine with either the foreground service or the battery optimizations disabled. Personally I don't mind the foreground notification, but I have talked to a lot of other people who don't like it.
It looks like the android client already has code for battery optimizations in the preference manager. Disabling battery optimizations enables background sync without a foreground process for many users on Conversations, so it should work here as well. Maybe the background sync setting could be modified to have two options (disabled battery optimizations or persistent notification) on newer devices using Marshmallow or later.
The two issues below are tangentially related to background sync so I wanted to include them in this issue thread.
#1801 #2196

I had the exact same problem. and eventually uninstalled riot.
@ all devs: I would fix most of the 323 open bugs before implementing any other improvement.
Thx @ian-kelling for creating this issue and everyone contributing.


Create type clases for Address, Bytes, etc.

          I really like these functions in the separate file!!

I think at some point we should consolidate on these conversions, and maybe create class types for Address & Hash to make conversions easier
I added some suggested changes/ideas at the end of types.py but I think in the long term we should try to make these as concise as possible or change some of the naming to avoid errors - i.e hex_or_none returns a hex string in one case so we could call it hex_string_or_none etc
Originally posted by @spencer-tb in https://github.com/ethereum/execution-spec-tests/pull/167#discussion_r1248205001

Fixed by #207


Question: Linux Builds

I'm currently compiling the mod from source using information from the main branch.
As of now there isn't any linux builds on gamebanana, are there plans for making some or is it solely windows?

I can send you a Linux build zip if you want.
Are you on Ubuntu 21.04/have glibc 2.33?

Will send a link to a probably universally compatible version in 5 minutes

I've compiled the binaries myself already... just didnt know if there was any plans for having linux builds as most mods i've seen either dont support linux or forget it exists entirely

ah

I did go ahead and repost the mod on gamebanana working under the license agreement on this repo. It does have dfkj and wasd control variants though lol


MQTT Support

Is it possible to send the results over MQTT?

As far as I know, when a wifi device is in monitor/promiscuous mode only can listen to packets and it cannot get connected to a wifi network at the same time, but, I guess that you can use two ESP8266 modules. One listening for packets and other connected to your network, and use the first one listening packets to send results to the other module by one UART line and push these results to the MQTT server from this second one.

That's exactly what I'm working on. Thanks for the wonderful script. Works like charm.

Or you could switch from promiscuous to normal STA mode from time to time, to send the collected data out in intervals, thus needing just 1 module.

Any idea on how I can achieve this with STA mode?  I'm not that good in programming.

See https://github.com/esp8266/Arduino/blob/master/doc/esp8266wifi/readme.md#station

I know this is a very old thread, but I've learnt much from your project. This scenerio with MQTT is something that my new Approximate library makes easy for both ESP32 and ESP8266 > https://github.com/davidchatting/Approximate#close-by-mqtt---make-a-connection-to-the-cloud

I know this is a very old thread, but I've learnt much from your project. This scenerio with MQTT is something that my new Approximate library makes easy for both ESP32 and ESP8266 > https://github.com/davidchatting/Approximate#close-by-mqtt---make-a-connection-to-the-cloud

@davidchatting seems like a very interesting project, glad to know you have learned something from this small one :) thanks for sharing!


[Backport] [2.x] Update Gradle to 7.6

Signed-off-by: Andriy Redko<EMAIL_ADDRESS>
Description
Update Gradle to 7.6
Issues Resolved
Backport of https://github.com/opensearch-project/OpenSearch/pull/5381 to 2.x
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[X] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Gradle Check (Jenkins) Run Completed with:
* **RESULT:** FAILURE x

* **URL:** https://build.ci.opensearch.org/job/gradle-check/7351/

* **CommitID:** [58bfa0b](https://github.com/opensearch-project/OpenSearch/commit/58bfa0bab46259f555457ca1944efea4f0c1e6c9)
  Please examine the workflow log, locate, and copy-paste the failure(s) below, then iterate to green.
  Is the failure [a flaky test](https://github.com/opensearch-project/OpenSearch/blob/main/DEVELOPER_GUIDE.md#flaky-tests) unrelated to your change?

It seem like Gradle Retry plugin is not compatible with Gradle 7.6? :D :`(
> Receiver class org.gradle.testretry.internal.executer.RetryTestResultProcessor does not define or inherit an implementation of the resolved method 'abstract void failure(java.lang.Object, org.gradle.api.tasks.testing.TestFailure)' of interface org.gradle.api.internal.tasks.testing.TestResultProcessor.

I just opened #5383 to update test-retry on the 2.x branch to be in line with main. Gradle 7.6 support was added in test-retry 1.4.0.

I just opened #5383 to update test-retry on the 2.x branch to be in line with main. Gradle 7.6 support was added in test-retry 1.4.0.

I did it here as well, do you want to spit it in several commits?

I just opened #5383 to update test-retry on the 2.x branch to be in line with main. Gradle 7.6 support was added in test-retry 1.4.0.

I did it here as well, do you want to spit it in several commits? This guy seems to be green and ready to merge :)

I don't see the test-retry upgrade in this PR? Am I missing it?

I just opened #5383 to update test-retry on the 2.x branch to be in line with main. Gradle 7.6 support was added in test-retry 1.4.0.

I did it here as well, do you want to spit it in several commits? This guy seems to be green and ready to merge :)

I don't see the test-retry upgrade in this PR? Am I missing it?

Oops, sorry about it, I did the change but forgot to push, apologies

I just opened #5383 to update test-retry on the 2.x branch to be in line with main. Gradle 7.6 support was added in test-retry 1.4.0.

Approved, thank you!


Sublime like snippets

I love how in sublime cfml plugin we can do shortcuts to do insertions of constructs like this:
like this:
 // super+alt+d  <cfdump var="##">
    {
    "keys": ["shift+command+d"], "command": "insert_snippet",
    "args": { "contents": "<cfdump var=\"#${1:$SELECTION}#\" />" },
    "context":
	    [
	        {"key": "selector", "operator": "equal", "operand": "embedding.cfml"},
      {"key": "selector", "operator": "not_equal", "operand": "source.cfml.script"}
	    ]
	},

Is this possible? I know you can have snippets, but shortcuts for insertions would be cool

It seems to be doable: https://manual.macromates.com/en/snippets
Sublime supports TextMate snippets, doesn't it?

I am not familiar with TextMate, but sure :)

Are you asking about keybindings to snippets?
If so, one for cfdump would just require the following added to your keybindings.json:
{
    "key": "shift+ctrl+d",
    "mac": "shift+cmd+d",
    "command": "editor.action.insertSnippet",
    "when": "editorTextFocus",
    "args": {
        "langId": "lang-cfml",
        "name": "cfdump"
  }
}

In this case, the context is based on language ID, which is the same for tag and script syntaxes, instead of a syntax scope selector. The rest of the linked page contains everything documented about snippets in VS Code.

Wow, yes that worked.  However the mac command didn't work in mac. I had to use the key instead.  I will close this ticket, since I can see this more of a user thing and not core.

Ok, let me reopen with one more addition. How do you distinguish if you are in cfscript mode or in tag mode?

I added the mac part because I've seen it used in keybindings for extensions, but I don't have OSX to test. It might not work for user keybindings at all or perhaps I misunderstood how it is supposed to work.
Regarding script or tag, again the context is the language ID which is the same for both. This has been discussed in other issues already, but having separate language IDs would solve this and some other issues surrounding the differences.

I would vote for having two different language IDs as you can do certain things in script that you can't in tags and vice versa

If we have proper CFML parser then it should work for one language ID, I think. The first thing I want to do for the next version is to update TextMate syntax script to understand CFML, cfscript, CFML components, HTML and SQL contexts. As I understood this is the approach used for PHP plugin, for example.
Current TextMate syntax is few years old and should be updated.
I also did research if it is possible to provide highlighting via language server. Unfortunately it doesn't seem to be doable, because of VS Code performance implications.

Do you think we should have language ID & snippets for CFC's and CFM's?

Yes, definitely.  Each context should have its own snippets. But yes, you need the language ID differentiated.  Also remember that you can do code islands in CFML as well, basically having in a cfm or tag based file the cfscript tags. Which would be difficult as well.
The Java plugin using a Java binary for the language server, which we can easily do with commandbox as well as it works the same way.

You could have the extension dynamically change various things based on context within the same language ID, which a proper parser could facilitate, but I don't think that is the best solution. I think dynamically changing the language ID in those cases would be ideal, and the associated settings for that language ID would simply be used in those contexts. In the case of static items like user snippets and user keybindings, you can only reasonably base them off of language ID as there is no access to a more specific context.

agreed!  Exciting!!!

Ok, will close this now.


More detailed documentation

Hey,
i'm using Hubot for rocket chat and i'm guessing what the hubot base url could be.
Also, if self hosted bitbucket server, which hook addon should i use with which options?

@stefuNz
The Hubot base URL is your public-facing hubot address, such as hubot.herokuapp.com. This is an accessible endpoint for Bitbucket POSTs.
On a self-hosted Bitbucket server, I'm honestly unsure. I don't have any experience with self-hosted Bitbucket and don't know the interface. If you're using the new Bitbucket and version v0.4 <= of this plugin, you'll want to create a Webhook using this interface.

Hi @stefuNz, I'm marking this issue as closed. If you have any other questions, please let me know.


fix(VirtualTimeScheduler): rework flush so it won't lose actions

Description:
Previously VirtualTimeScheduler.flush would lose the action that was on a verge of maxFrames limit which rendered testing of observables that are ticking indefinitely impossible. After the fix the user can set maxFrames, flush, make assertions and repeat the process as many times as needed.
Related issue:
None

Thanks for the PR. I will have a look at this tomorrow. (I also need to look at what's causing the dtslint run with TypeScript next to effect the errors in the Travis log - something that's unrelated to this PR.)

@cartant Hi! Did you have a chance to take a look?

I looked at it briefly.
My concern is that maxFrames is no longer relevant given that its set to POSITIVE_INFINITY in TestScheduler#run. And that is the recommended mechanism for writing marble tests.
I'll wait to see what other's have to say about it.


Write blog post about what's new on v0.18

This was my process, feel free to use it or to change it 😊
### Where to communicate on the new Release and in which order:

- Documentation should be published on GitHub.
- Slack community should be first warned that the new release is out.
- After some time, we should communicate on Twitter with a blog post.
- If the release brings a lot of new features, consider publishing it on LinkedIn and reddit.

This was my process, feel free to use it or to change it 😊
### Where to communicate on the new Release and in which order:

- Documentation should be published on GitHub.
- Slack community should be first warned that the new release is out.
- After some time, we should communicate on Twitter with a blog post.
- If the release brings a lot of new features, consider publishing it on LinkedIn and reddit.

I'll add this into the repo (we want to be as public as possible). @react-learner if you have any details you want to add to this about publishing a new release doc side.

I'll add this into the repo (we want to be as public as possible). @react-learner if you have any details you want to add to this about publishing a new release doc side.

This was my process, feel free to use it or to change it 😊
### Where to communicate on the new Release and in which order:

- Documentation should be published on GitHub.
- Slack community should be first warned that the new release is out.
- After some time, we should communicate on Twitter with a blog post.
- If the release brings a lot of new features, consider publishing it on LinkedIn and reddit.

See #77 for that.

This was my process, feel free to use it or to change it 😊
### Where to communicate on the new Release and in which order:

- Documentation should be published on GitHub.
- Slack community should be first warned that the new release is out.
- After some time, we should communicate on Twitter with a blog post.
- If the release brings a lot of new features, consider publishing it on LinkedIn and reddit.

See #77 for that.

I'm adding here the comment in made in #76 if it may help you on your first blog post Caro!

About the blog post, based a bit on what RUST does when ever they publish a new release: https://blog.rust-lang.org/2020/12/31/Rust-1.49.0.html, I try to be as explanatory as possible.
For example, about the tokenizer, I would explain a little how it works and what we had before. In order for users to observe that we are evolving. As it took us so long to make that change, it should be at least a bit praised.
So I would say:

new features (may they impact the user or not)
new addition to the API (clearly showing with example how to use it)
Breaking changes (for example the default value of the payload limit going from 10mb to 100mb is a breaking change that should be communicated).

Those are all what I use to do, it is of course up to you guys to decide if this is a direction you like.
For the last bit of information, the release article is always popular when they are published. So I think people like to read what is new. So don't be shy :D

I'm adding here the comment in made in #76 if it may help you on your first blog post Caro!

About the blog post, based a bit on what RUST does when ever they publish a new release: https://blog.rust-lang.org/2020/12/31/Rust-1.49.0.html, I try to be as explanatory as possible.
For example, about the tokenizer, I would explain a little how it works and what we had before. In order for users to observe that we are evolving. As it took us so long to make that change, it should be at least a bit praised.
So I would say:

new features (may they impact the user or not)
new addition to the API (clearly showing with example how to use it)
Breaking changes (for example the default value of the payload limit going from 10mb to 100mb is a breaking change that should be communicated).

Those are all what I use to do, it is of course up to you guys to decide if this is a direction you like.
For the last bit of information, the release article is always popular when they are published. So I think people like to read what is new. So don't be shy :D

@CaroFG: can @react-learner & I review it?

@CaroFG: can @react-learner & I review it?

Reviewed, would like to take a second look before publication if possible.

Reviewed, would like to take a second look before publication if possible.

https://blog.meilisearch.com/v0-18-0/
Congrats on the great blog post @CaroFG !

https://blog.meilisearch.com/v0-18-0/
Congrats on the great blog post @CaroFG !


Added typed OidcUserInfo

Resolves #795

Done, added optional generic params and updated Profile.tsx to include an example of an extended custom userinfo object


Release cleanup fails locally

I run a deploy to a local staging test env the cleanup process fails with the below error:
DEBUG [45e8d81a] Running /usr/bin/env ls -x /Library/WebServer/Documents/faces_staging/releases on <IP_ADDRESS>
 DEBUG [45e8d81a] Command: /usr/bin/env ls -x /Library/WebServer/Documents/faces_staging/releases
 DEBUG [45e8d81a]<PHONE_NUMBER>5410<PHONE_NUMBER>5440<PHONE_NUMBER>2907<PHONE_NUMBER>3153<PHONE_NUMBER>3509
20180426143538<PHONE_NUMBER>3659<PHONE_NUMBER>3721<PHONE_NUMBER>3811<PHONE_NUMBER>3921
20180426144219<PHONE_NUMBER>5342
 DEBUG [45e8d81a] Finished in 0.022 seconds with exit status 0 (successful).
  WARN Skipping cleanup of invalid releases on <IP_ADDRESS>; unexpected foldername found (should be timestamp)

When I run the production instance and push to the actual production server the releases are cleaned up correctly as defined by :keep_release.  I have checked all folder and user permissions and they are all correct. This is all done locally on a Mac OSX 10.11.16.
deploy.rb
# config valid for current version and patch releases of Capistrano
lock "~> 3.10.2"

set :application, "faces"

set :repo_url<EMAIL_ADDRESS>set :branch, 'master'

set :format, :pretty
set :pty, true
set :keep_releases, 2

append :linked_dirs, "images"

staging.rb file
set :stage, :staging
role :app, %w{<IP_ADDRESS>}

server '<IP_ADDRESS>', user: ENV['CAP_USER'], roles: %w{app}

set :deploy_to, "/Library/WebServer/Documents/staging/"

SSHKit.config.command_map[:bash] = "/bin/bash"
SSHKit.config.command_map[:composer] = "/usr/local/php5-5.6.30-20170213-115230/bin/php /usr/local/bin/composer.phar"

#Deploy tasks
namespace :deploy do

  desc "Update composer dependencies"
  task :composer_install do
    on roles(:app) do

        within release_path do
            info "Running composer"
            execute 'composer', 'install', '--no-dev', '--optimize-autoloader'
        end
    end
  end

  after :updated, "deploy:composer_install"
end

LMK if there is anything else I need to supply. I have been searching for some time and not finding much at all on the "unexpected foldername found" error.
Thanks,

@gonzoinc did you figure out what the problem was?

Nope, releases folder currently contains the following folders and nothing more. All are 14 digits long.
20180426125410
20180426143153
20180426143659
20180426143921
20180426190358
20180430192515
20180501123043
20180521184927
20180521185746
20180525181623
20180426125440
20180426143509
20180426143721
20180426144219
20180430191855
20180430192534
20180501151227
20180521185118
20180521191521
20180525181710
20180426142907
20180426143538
20180426143811
20180426175342
20180430192350
20180430192600
20180501151447
20180521185233
20180525181517
20180525182022

@gonzoinc Could you try adding the following snippet to your config/deploy.rb and then run bundle exec cap production temp_testing:cleanup (modify production if you are using a different environment).
namespace :temp_testing do
  desc "Clean up old releases"
  task :cleanup do
    on release_roles :all do |host|
      releases = capture(:ls, "-x", releases_path).split
      valid, invalid = releases.partition { |e| /^\d{14}$/ =~ e }

      puts "There are #{valid.count} valid entries"
      puts "There are #{invalid.count} invalid entries"
      if invalid.any?
        puts "invalid.any? returned true"
        invalid.each do |e|
          puts "Invalid entry: #{e.inspect}"
        end
      end
    end
  end
end

Sorry to hijack but having exactly the same problem right now. I've done some digging and inspected the releases variable and it seems that it's failing to split things correctly, so invalid actually contains tab chars and new line chars so technically are wrong. And in some cases it hasn't actually split them at all. I modified my locally installed gem slightly and added the following debug lines
puts "RAW #{capture(:ls, "-x", releases_path)}"
puts "RELEASE #{releases}"

And I'm getting the following output:
RAW<PHONE_NUMBER>5014<PHONE_NUMBER>1751<PHONE_NUMBER>5146<PHONE_NUMBER>2813<PHONE_NUMBER>5224
20190214134828<PHONE_NUMBER>5857<PHONE_NUMBER>3359<PHONE_NUMBER>4729<PHONE_NUMBER>1152
20190215152609<PHONE_NUMBER>3536<PHONE_NUMBER>1444<PHONE_NUMBER>2943<PHONE_NUMBER>5034
20190218150454<PHONE_NUMBER>5104

RELEASE ["20190213095014\t20190213101751\t20190213115146\t20190213162813\t20190214095224", "\n20190214134828\t20190215135857\t20190215143359\t20190215144729\t20190215151152", "\n20190215152609\t20190215153536\t20190215171444\t20190215172943\t20190218135034", "\n20190218150454\t20190218155104"]

As you can see, the releases array has been split incorrectly so it's not surprising that the partition call isn't working as expected

@pareeohnos what is the value of $; in your Ruby environment? By default it is nil, which will cause split with no arguments to split based on whitespace. Based on your output my guess is that your environment is different, hence the odd behavior you are seeing.
puts "RAW #{capture(:ls, "-x", releases_path)}"
puts "RELEASE #{releases}"
puts $;.inspect

In any case, I agree that we should change the code to split(" ") because that removes any implicit dependence on $;. Would you be interested in opening a PR?
Thanks for digging into this and reporting your results!

@mattbrictson That statement is giving me nil as well so doesn't seem to be that. Is it possible that a different shell might cause the result of the capture to be slightly different? Our staging server is running zsh so not sure if that's interfering at all?
Yeah would be happy to open a PR for this :)

split and split(' ') should behave identically, so I am confused why changing that makes a difference.
$ irb
>> "20190213095014\t20190213101751\t20190213115146\t20190213162813\t20190214095224".split
[
    [0] "20190213095014",
    [1] "20190213101751",
    [2] "20190213115146",
    [3] "20190213162813",
    [4] "20190214095224"
]
>> "20190213095014\t20190213101751\t20190213115146\t20190213162813\t20190214095224".split(" ")
[
    [0] "20190213095014",
    [1] "20190213101751",
    [2] "20190213115146",
    [3] "20190213162813",
    [4] "20190214095224"
]

Perhaps you are right, that zsh on the server is the problem. Is ls -x outputting in color, for example? Those non-printable characters might be screwing things up. Maybe try this, so you can see the non-printable characters:
puts "RAW #{capture(:ls, "-x", releases_path)}".inspect

I've done a little more digging, and it's really strange behaviour but it seems the issue only comes up when there are enough releases that ls returns its result over multiple lines. At that point, the result of it contains \n and \t chars which is what appears to be messing it up. As a test I added in some extra files into the releases directory and tried the following:
releases = "2018000000000\t20180000000000\t20180000000001\t20180000000002\t20180000000003\n20180000000004\t20180000000005\t20180000000006\t20180000000007\t20180000000008\n20180000000009\t20180000000010\t20190215171444\t20190215172943\t20190218135034\n20190218150454\t20190218155104"

puts a.split
[
  [0] "2018000000000\t20180000000000\t20180000000001\t20180000000002\t20180000000003",
  [1] "\n20180000000004\t20180000000005\t20180000000006\t20180000000007\t20180000000008",
  [2] "\n20180000000009\t20180000000010\t20190215171444\t20190215172943\t20190218135034",
  [3] "\n20190218150454\t20190218155104"
]

puts a.split(' ')
[
  [ 0] "2018000000000",
  [ 1] "20180000000000",
  [ 2] "20180000000001",
  [ 3] "20180000000002",
  [ 4] "20180000000003",
  [ 5] "20180000000004",
  [ 6] "20180000000005",
  [ 7] "20180000000006",
  [ 8] "20180000000007",
  [ 9] "20180000000008",
  [10] "20180000000009",
  [11] "20180000000010",
  [12] "20190215171444",
  [13] "20190215172943",
  [14] "20190218135034",
  [15] "20190218150454",
  [16] "20190218155104"
]

I'm not sure why split and split(' ') are different - as you say they should behave identically but something here isn't right

That split behavior is truly bizarre. What is the a variable in your example? Shouldn't it be releases.split?
I'm also curious what you get for these:
a.class # => String < Object
a.method(:split).source_location # => nil

Oh sorry that is meant to be releases. I had put a in my actual test since I'm lazy and just forgot to correct those when I pasted the output. But good call on the source_location. Turns out we've got some legacy code which is monkey patching the String class and replacing the split method, and even though it appears that whoever set it up used slightly different arguments to the ruby default which is causing the issues. Instead of setting the first argument to $; it is set to the regex pattern /$/ which if you put into the default split implementation causes the strang behaviour I've been seeing.
So after all that, turns out to be a bug in our app not capistrano

Turns out we've got some legacy code which is monkey patching the String class and replacing the split method, and even though it appears that whoever set it up used slightly different arguments to the ruby default which is causing the issues.

If you're on a new enough version of Ruby and don't feel like lobotomising the legacy code just yet, you might think about fencing it in with refinements https://docs.ruby-lang.org/en/2.4.0/syntax/refinements_rdoc.html to reduce the scope leak of your string monkey patch?

Ah I'd forgotten about them. Though fortunately the code is so old I'm pretty certain it's not being used so will just rip it out :)


INVALID_SYNTAX_CANNOT_PARSE for at sign (@)

Description
Since release 9.1.0, Lucene's SyntaxParser have been uncapable to parse @ in a query, throwing a Syntax Error (INVALID_SYNTAX_CANNOT_PARSE).
Version 9.0.0 is the last I tested that still can parse this character.
Two similar examples that throw INVALID_SYNTAX_CANNOT_PARSE in 9.1.0, but not in 9.0.0:

\\ an@tomy
\\ @natomy

Leaving some log dump here:
Syntax Error, cannot parse \\ an@tomy:
INVALID_SYNTAX_CANNOT_PARSE: Syntax Error, cannot parse \\ an@tomy:
	at org.apache.lucene.queryparser.flexible.standard.parser.StandardSyntaxParser.generateParseException(StandardSyntaxParser.java:2093)
	at org.apache.lucene.queryparser.flexible.standard.parser.StandardSyntaxParser.jj_consume_token(StandardSyntaxParser.java:1961)
	at org.apache.lucene.queryparser.flexible.standard.parser.StandardSyntaxParser.TopLevelQuery(StandardSyntaxParser.java:115)
	at org.apache.lucene.queryparser.flexible.standard.parser.StandardSyntaxParser.parse(StandardSyntaxParser.java:92)
	at org.apache.lucene.queryparser.flexible.core.QueryParserHelper.parse(QueryParserHelper.java:214)
	at org.apache.lucene.queryparser.flexible.standard.StandardQueryParser.parse(StandardQueryParser.java:280)
        ...

Version and environment details

JDK: temurin-17.0.3
OS: MacOS Monterey 12.6 and alpine-java17:latest (docker image)
Lucene: 9.1.0

not a bug, but related to new features added to the parser. see the associated message in MIGRATE.txt:
## Minor syntactical changes in StandardQueryParser (Lucene 9.1)

LUCENE-10223 adds interval functions and min-should-match support to StandardQueryParser. This
means that interval function prefixes ("fn:") and the '@' character after parentheses will
parse differently than before. If you need the exact previous behavior, clone the StandardSyntaxParser from the previous version of Lucene and create a custom query parser
with that parser.

Also, please note that you can quote the ampersand in terms - this will behave like before. I don't think it's a bug, sorry it caused you trouble but the new functionality is worth it (try it!).

Hey again,
So if I want my queries to support @, what should be my approach to keep the parsing compatibility from this version on?
If there is no way to parse it right now, how should one escape the character? Would the regular escaping \\ be enough in this case?

You can escape the at character:
am\@zing

or you can quote the term:
"am\@zing"

Or you can set up flexible query parser with your own syntax parser (which you'd source from a previous Lucene version).

So why isn't this method escaping @ then?
https://github.com/apache/lucene/blob/5b24a233bdfd2c1feb177a5de4fc5eb62baf6015/lucene/queryparser/src/java/org/apache/lucene/queryparser/classic/QueryParserBase.java#L965-L978

Note this class is in a different package - it's a different query parser. There are many. They all behave differently. It's a project with long history.

OK, thank you very much for the clarification 👍


Removed outdated and confusing bower.json file

Related to issues #134 #116

Added tests for log and debug.

Sorry there was no response to this, the project was in stasis for a while, but we recently refactored the code. However, this pr would still be useful if you're interested in rebasing and updating the code  at bit (changes should be somewhat minor). Either way I appreciate it.

closing due to lack of response


Moving domain to ghpages

cloudflare is set up but pointing via CNAME to github pages.
https://mothereffinganimatedgif.com/
if you see saveasbro issues in the console then it hasn't been updated. But i THINK i have the configuration of everything set up... just waiting for propagation..

nice. I was going to suggest moving this site to HTTPS...
The only console error I see is that its missing a favicon so will open a separate issue for that.

yup!
i think the propagation finished now. we good!


protractor tests : using $interval instead of $timeout for notify duration management

Hi,
I use this module in my application, and I started to write e2e tests with protractor.
There is no problem when writing tests for function using notification which stay on screen, but notification with duration attribute are not testable. This issue comes from the $timeout service to manage notification duration : protractor waits for $timeouts (and $http) before to run actions and expectation. So notification with duration can't be tested as they disappears before protractor tests them.
In documentation (https://github.com/angular/protractor/blob/master/docs/timeouts.md), protractor team precognise to replace $timeout services by $interval services to this kind of issue.
Can you try that to allow protractor testing of notifications with duration ?

:+1: We are running into the same issue, and using $interval would solve a big headache for us.

I have made a fork that changes to $interval here: https://github.com/peakon/angular-notify

Coud that be used in the main branch ? Otherwise we will have to implement our own...

@holm thanks for your fork, it works for me :+1:


Add option visiblePropertyPhetioInstrumented to Node?

Because of #1180, I find that I'm having to do this quite a bit when visibility is derived:
visiblePropertyOptions: { phetioReadOnly: true }

… 14 times in Graphing Quadratics, 10 times in Natural Selection, … 51 occurrences in all PhET code.
Now that I’ve been introduced to inputEnabledPropertyPhetioInstrumented, maybe there's a better way.  Looking in Node, I see:
  'pickablePropertyPhetioInstrumented', // {boolean} - When true, create an instrumented pickableProperty when this Node
...
  'enabledPropertyPhetioInstrumented', // {boolean} - When true, create an instrumented enabledProperty when this Node
...
   'inputEnabledPropertyPhetioInstrumented', // {boolean} - When true, create an instrumented inputEnabledProperty when this Node is instrumented, see setInputEnabledPropertyPhetioInstrumented() for more documentation

So there is an option for all settable Properties except visibleProperty.  Should there be a visiblePropertyPhetioInstrumented?

Those flags seem like they're for whether it's instrumented at all, but not whether it's read-only. I'd defer to @zepumph on this.

Should there be a visiblePropertyPhetioInstrumented?

every instrumented Node gets an instrumented visibleProperty, the option like inputEnabledPropertyPhetioInstrumented is only for Properties that are "opt in".

Sorry if I'm being dense, but still not clear... "Opt in" for what? Instantiation? Instrumentation? Both?

A request for this feature came up in a Molecule Polarity with @arouinfar and @kathy-phet.  It generalizes to all sims.  The designers would like to instrument some Properties of checkbox labels -- for example textProperty of a Text Node -- but not instrument the visibleProperty, because a checkbox without a label makes no sense. (This is also true of some other UI components, like Aqua radio buttons.)  We could use visibilePropertyOptions: { phetioReadOnly: true } to prevent the label Node from being hidden.  But it would be preferrable to not instrument visibleProperty at all, since it serves no purpose.
So... Above, @zepumph said:

every instrumented Node gets an instrumented visibleProperty, the option like inputEnabledPropertyPhetioInstrumented is only for Properties that are "opt in".

I realize that is currently the case, but it's unnecessary and undesirable for every instrumented Node to have an instrumented visibleProperty.  What's the problem with adding visiblePropertyPhetioInstrumented with a default of true, and allowing clients to opt out?

The options we're discussing here were renamed in https://github.com/phetsims/scenery/issues/1202, so I've adjusted the title of this issue accordingly.  For example, inputEnabledPropertyPhetioInstrumented is now phetioInputEnabledPropertyInstrumented.

The request from @pixelzoom sounds reasonable to me, unless @zepumph had something else in mind.  @zepumph can you please recommend how to proceed?

Sounds good to me! I'll add it.

Added above. I was able to successfully test with this patch

Index: js/HomeScreenView.js
IDEA additional info:
Subsystem: com.intellij.openapi.diff.impl.patch.CharsetEP
<+>UTF-8
===================================================================
diff --git a/js/HomeScreenView.js b/js/HomeScreenView.js
--- a/js/HomeScreenView.js	(revision 207264bc008a8f37535bf475521bb0b1c7d267d3)
+++ b/js/HomeScreenView.js	(date<PHONE_NUMBER>978)
@@ -48,6 +48,7 @@
     }, options );

     super( {
+      phetioVisiblePropertyInstrumented: false,
       layoutBounds: LAYOUT_BOUNDS,
       tandem: tandem,

This is the first visibleProperty in most sims. I also noted that when I regenerated an API, it removed this visibleProperty from the API.
@pixelzoom, sorry this is a bit late, but perhaps you would like to update your sim usage now. Over to you, feel free to close.

👍🏻 closing.


Close definition popup if the reader clicks on the audiobook icon on reading screen

If the popup is open, it should close if the reader clicks on the audiobook icon to begin playing the book audio. When the popup closes, the audio for the definition should stop playing as well.

duplicate of #166

just delete the second sentence


DNS Root Migration

Prepare for and participate in the DNS root migration of some of our key domains.

Today's meeting was postponed. We may do this asynchronously instead of on a video call, not sure.

@tedcahalleos and I migrated the SOA, NS, and A records for eosnetwork.com. from Google Domains to AWS Route 53 this morning around 2022-12-17 11:12 EST. We were able to verify that dig is returning the expected records and tested the website at eosnetwork.com, docs.eosnetwork.com, and eosnetwork.com from Blacksburg VA, Manassas VA, Israel, and Hong Kong. We also tested api.learn.eosnetwork.com with curl, and were able to send email to our domain using at least three different external providers.
I put this ticket in Awaiting Review to indicate the work is done. I will close on Monday if there are no issues reported.


⚠ Bofrost.fr has degraded performance

In 478c497, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1651 ms

Resolved: Bofrost.fr performance has improved in cfc42e8 after 13 minutes.


feat(async): introduce sequence

Signed-off-by: azjezz<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

3 of 3 (100.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0001%) to 99.881%

Totals

Change from base Build<PHONE_NUMBER>:
0.0001%

Covered Lines:
3353

Relevant Lines:
3357

💛  - Coveralls


HtmlInput changeType new instance causes side effects

In one of the previous versions a breaking change with HtmlInput.setAttribute was introduced.
Currently, when changing type of HtmlInput a new instance is created and the instance worked on is no longer attached.
Looks like this behavior is intended but causes undesired side effects as the user has absolutely no way knowing they are working on a stale object.
(HtmlElementBuilder is a helper class we created, it basically just creates a StringWebResponse and passes it to to PageCreator)
Example 1 :
@Test
public void testInput() {
        HtmlPage page = HtmlElementBuilder.createPageFromString("");
        HtmlElement input = (HtmlElement) page.createElement("input");
        input.setAttribute("type", "hidden");
        input.setAttribute("name", "test");
        page.getBody().appendChild(input);

        System.out.println(page.asXml());
}

Which result in this result:
<?xml version="1.0" encoding="UTF-8"?>

   <input type="hidden"/>

Another case:
@Test
public void testInput() {
        HtmlPage page = HtmlElementBuilder.createPageFromString("");
        HtmlElement input = (HtmlElement) page.createElement("input");
        page.getBody().appendChild(input);
        input.setAttribute("type", "hidden");
        input.setAttribute("name", "test");

        System.out.println(page.asXml());
    }

Results in:
<?xml version="1.0" encoding="UTF-8"?>

    <input type="hidden"/>

There are workarounds for this but this feels very error prone.

related to #658

Any good suggestions?

As a user an UnsupportedOperationException when passing type to force us to use changeType would have friendlier but I'm not sure how viable that is.


<EMAIL_ADDRESS>hash check failed

Here is my console output:
Installing 'spotify-latest' (<IP_ADDRESS>9.gced9e0f5) [64bit]
SpotifyFullSetup.exe (74.7 MB) [========================================================================================] 100%
Checking hash of SpotifyFullSetup.exe ... ERROR Hash check failed!
App:         spotify/spotify-latest
URL:         https://download.scdn.co/SpotifyFullSetup.exe
First bytes: 4D 5A 90 00 03 00 00 00
Expected:    5abf27318a30c4d18ea2d68a558d063678c375e7978dce73990631099fbaaf05
Actual:      35ce7176234b5a050472f00e102fc50ab64ad8e96d53eff66f30f2217938723d

Please try again or create a new issue by using the following link and paste your console output:
https://github.com/TheRandomLabs/Scoop-Spotify/issues/new?title=spotify-latest%4<IP_ADDRESS>9.gced9e0f5%3a+hash+check+failed

I've tried to scoop update; scoop uninstall spotify-latest; scoop install spotify-latest but no luck.

Fixed!


Move samples/js/perf to js/perf

@mikegray TBR
@sunglim FYI

lgtm, thanks for cleaning all this up!


export error with JOBs

While exporting I had errors only with “LOB” and “JOB” object_type (We have on that schema almost 100 jobs, non of them where exported), schema2ddl export that out.
Almost all finished with following error
export: SEND_FLEXMAIL_QUEUE[JOB]             => 20:00:20 (Exporter,ERROR) sql error: ORA-31600: invalid input value SEND_FLEXMAIL_QUEUE for parameter NAME in function GET_DDL
ORA-06512: at "SYS.DBMS_METADATA", line 6681
ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
ORA-06512: at "SYS.DBMS_METADATA", line 6558
ORA-06512: at "SYS.DBMS_METADATA", line 9672
ORA-06512: at line 1

Sample JOB :
BEGIN
DBMS_SCHEDULER.CREATE_JOB (
job_name => '"MBA".""',
job_type => 'STORED_PROCEDURE',
job_action => 'MBA.AUC_PRE_INTERFACE.REFRESH_PRE_ALL',
number_of_arguments => 0,
start_date => TO_TIMESTAMP_TZ('2020-11-03 08:40:08.000000000 EUROPE/PRAGUE','YYYY-MM-DD HH24:MI:SS.FF TZR'),
repeat_interval => 'FREQ=HOURLY',
end_date => NULL,
enabled => FALSE,
auto_drop => TRUE,
comments => 'Refresh webpage data by hour.');
DBMS_SCHEDULER.SET_ATTRIBUTE(
         name => '"MBA".""',
         attribute => 'store_output', value => TRUE);
DBMS_SCHEDULER.SET_ATTRIBUTE(
         name => '"MBA".""',
         attribute => 'logging_level', value => DBMS_SCHEDULER.LOGGING_OFF);

DBMS_SCHEDULER.enable(
         name => '"MBA".""');

END;
/

The object types differ between ALL_OBJECTS and DBMS_METADATA. A mapping between the two fixed it.


New package: DFTforge v0.9.3

Registering package: DFTforge
Repository: https://github.com/KAIST-ELST/DFTforge.jl
Created by: @bluehope
Version: v0.9.3
Commit: f1a0d95abad61e65cf2731cce4f6a7a140507f53
Git reference: master
Release notes:

DFTforge: the DFT postprocessing environment
Simplify obtaining Hamiltonian, Eigenvalue, Eigenvector from DFT results, and Pre-caching them for parallelized calculations.
Pre-cached results are easy to use when calculating in k and q space.
DFTforge
The wrapper for calculating Hamiltonian, Eigenvalue, Eigenvector from DFT results.

read DFT results from OpenMX, Wannier90
Calculate Phi, Enk, Hks,

Etc. functionalities

K-point representation in INT (for unique K,Q).
Gennerate K-points.
Generalised argument parser (support TOML sytle input).

@JuliaRegistrator register

@JuliaRegistrator [noblock]

Please add (at least)
[compat]
julia = "1"

to your project file and retrigger the bot.

#5007


Authentication error on main branch

kibana_system authentication fails
I am trying to set up a minimal EFK stack, using this template as the basis. I cloned this repo then rm'd the logstash directory alongside logstash references in docker-compose.yml, and setup/entrypoint.sh. On running docker-compose up I get the following error in the logs:
elasticsearch_1  | {"@timestamp":"2022-06-20T13:35:17.467Z", "log.level": "INFO", "message":"Authentication of [kibana_system] was terminated by realm [reserved] - failed to authenticate user [kibana_system]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[2d1b52f444b2][transport_worker][T#3]","log.logger":"org.elasticsearch.xpack.security.authc.RealmsAuthenticator","trace.id":"1a2cf9dc05394c8eab7693ead37a4f3d","elasticsearch.cluster.uuid":"4HB73jFPQciK5-Vc5fRzEQ","elasticsearch.node.id":"lnh-MPQTSDWxnKh5HDBb-Q","elasticsearch.node.name":"2d1b52f444b2","elasticsearch.cluster.name":"docker-cluster"}

I have seen #666 and #671 which, IIUC, negates the need to manually setup passwords as in the docs. Meaning docker-compose up should just work.
Stack configuration
Changes:

Remove ./logstash
Remove logstash service in docker-compose.yml
Remove logstash roles and user in setup/entrypoint.sh
Remove logstash password in .env
Change passwords in .env
Changed license to basic
Change ELASTIC_VERSION to 8.2.2 in .env

Diff on Pastebin
Docker setup

docker version

$ docker version

Client: Docker Engine - Community
 Version:           20.10.17
 API version:       1.41
 Go version:        go1.17.11
 Git commit:        100c701
 Built:             Mon Jun  6 23:02:56 2022
 OS/Arch:           linux/amd64
 Context:           default
 Experimental:      true

Server: Docker Engine - Community
 Engine:
  Version:          20.10.17
  API version:      1.41 (minimum version 1.12)
  Go version:       go1.17.11
  Git commit:       a89b842
  Built:            Mon Jun  6 23:01:02 2022
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.6.6
  GitCommit:        10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
 runc:
  Version:          1.1.2
  GitCommit:        v1.1.2-0-ga916309
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker-compose version

$ docker-compose version

docker-compose version 1.29.2, build 5becea4c
docker-py version: 5.0.0
CPython version: 3.7.10
OpenSSL version: OpenSSL 1.1.0l  10 Sep 2019

Container logs
Pastebin (some characters are mangled, possibly clipboard encoding error of some sort)
Reprex
git clone git@github.com:aphilas/efk-reprex.git
cd efk-reprex
docker-compose up

ETA:
Simply cloning this repo and running docker-compose up yields the same result.

Change passwords in .env

This will only work on the first run. If you ever ran docker-compose up prior to changing these, you will also need to reset the passwords manually directly inside Elasticsearch.
If you don't have any critical data stored in Elasticsearch, the easiest way to fix your issue is to run docker-compose down -v then run the stack again. This time, passwords will be initialized based on what you have in your .env file.

I have run docker-compose down v and/or docker-compose rm setup and then docker-compose up to no avail.

Could you please try this:

ETA:
Simply cloning this repo and running docker-compose up yields the same result.

It works for me, and our automated tests are green.
It would be a pretty big issue if the default config wasn't working.
Deleting the repo and cloning it again does not delete Elasticsearch's data and does not reset the state of the setup container.
Like I said, if this doesn't work, there is surely a mismatch between your env file and the stored state of Elasticsearch.

@LonnyX that's a different issue. OP's Kibana doesn't start at all, whereas your problem is likely related to an outdated Compose version.
See the warning at https://github.com/deviantony/docker-elk#host-setup

@aphilas here is the execution log of your custom stack running on my machine from scratch:
$ git clone git@github.com:aphilas/efk-reprex.git
Cloning into 'efk-reprex'...
remote: Enumerating objects: 21, done.
remote: Counting objects: 100% (21/21), done.
remote: Compressing objects: 100% (15/15), done.
remote: Total 21 (delta 2), reused 21 (delta 2), pack-reused 0
Receiving objects: 100% (21/21), 4.04 KiB | 4.04 MiB/s, done.
Resolving deltas: 100% (2/2), done.

$ cd efk-reprex

$ docker-compose up -d
Creating network "efk-reprex_elk" with driver "bridge"
Creating volume "efk-reprex_setup" with default driver
Creating volume "efk-reprex_elasticsearch" with default driver
Building setup
[+] Building 250.0s (8/8) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 336B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 191B                                                                                0.0s
 => [internal] load metadata for docker.elastic.co/elasticsearch/elasticsearch:8.2.2                                                                   5.0s
 => [internal] load build context                                                                                0.0s
 => => transferring context: 5.03kB                                                                                0.0s
 => [1/3] FROM docker.elastic.co/elasticsearch/elasticsearch:8.2.2@sha256:0101bbe4f8e9deeb01768955c7007d0a2927c3ea320fa6fb1f87ef04992caf9d           244.1s
 => => resolve docker.elastic.co/elasticsearch/elasticsearch:8.2.2@sha256:0101bbe4f8e9deeb01768955c7007d0a2927c3ea320fa6fb1f87ef04992caf9d             0.0s
 => => sha256:4e6476fa627dfa17b1fc40d68fb1bdcbd3e785a0f9f2252ec79495c3cca6df77 9.18kB / 9.18kB                                                         0.0s
 => => sha256:1885934a00e5a435238a471bd508bf6926db90b179e2844d3635d48e6dc83009 31.78MB / 31.78MB                                                      20.1s
 => => sha256:c2eb4fa6ff9008275a5b365ed69b96ca0db2d423074d32d99e3e241a9e559726 20.17MB / 20.17MB                                                      18.4s
 => => sha256:0101bbe4f8e9deeb01768955c7007d0a2927c3ea320fa6fb1f87ef04992caf9d 710B / 710B                                                             0.0s
 => => sha256:3078c1afe36bea72370470326b8ce0eb9499317ceba37a1ff425e3fe2e73d1aa 4.54kB / 4.54kB                                                         1.0s
 => => sha256:1a44b907475952a0b33d2a02989bee89c70df96891390bcc2d813d1d12988f96 1.73kB / 1.73kB                                                         0.0s
 => => sha256:1cf5d68c57b195345ec15dd8c454bfd3d2f1ec611f5db23f8d249fed56ceae4e 584.77MB / 584.77MB                                                   228.6s
 => => sha256:e91173fecb9241e58f4912f7dc2945e6b0834b5626be2181dfa3eb58ff8567c3 10.16kB / 10.16kB                                                      18.6s
 => => sha256:5be1f45ee957b70294ffc87f564a5a5b2bcb4c44374eb6fd6b541335e51efdbd 1.80kB / 1.80kB                                                        18.8s
 => => sha256:ffaf8984b1dc71da71558fb7a9021f5296e00a986087720d4debf7f1dea76e20 210.97kB / 210.97kB                                                    19.3s
 => => sha256:4287ca9f47987b342f3f6447ae8e8456bc49aa13efafcc1eced65cf4d3701c76 421B / 421B                                                            19.6s
 => => sha256:53e07ab99ab14681b37a05a73bef43a896ad4b5ef3aa6d401f198512af54c8d8 109.39kB / 109.39kB                                                    19.9s
 => => extracting sha256:1885934a00e5a435238a471bd508bf6926db90b179e2844d3635d48e6dc83009                                                              1.6s
 => => extracting sha256:c2eb4fa6ff9008275a5b365ed69b96ca0db2d423074d32d99e3e241a9e559726                                                              0.9s
 => => extracting sha256:3078c1afe36bea72370470326b8ce0eb9499317ceba37a1ff425e3fe2e73d1aa                                                              0.0s
 => => extracting sha256:1cf5d68c57b195345ec15dd8c454bfd3d2f1ec611f5db23f8d249fed56ceae4e                                                             14.9s
 => => extracting sha256:e91173fecb9241e58f4912f7dc2945e6b0834b5626be2181dfa3eb58ff8567c3                                                              0.0s
 => => extracting sha256:5be1f45ee957b70294ffc87f564a5a5b2bcb4c44374eb6fd6b541335e51efdbd                                                              0.0s
 => => extracting sha256:ffaf8984b1dc71da71558fb7a9021f5296e00a986087720d4debf7f1dea76e20                                                              0.0s
 => => extracting sha256:4287ca9f47987b342f3f6447ae8e8456bc49aa13efafcc1eced65cf4d3701c76                                                              0.0s
 => => extracting sha256:53e07ab99ab14681b37a05a73bef43a896ad4b5ef3aa6d401f198512af54c8d8                                                              0.0s
 => [2/3] COPY . /                                                                                0.5s
 => [3/3] RUN set -eux;  mkdir /state;  chown elasticsearch /state;  chmod +x /entrypoint.sh                                                           0.3s
 => exporting to image                                                                                0.1s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:9a3a23a07036518159a5fed1d847337cb32e23a960e7918d8f42768ec0290585                                                           0.0s
 => => naming to docker.io/library/efk-reprex_setup                                                                                0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
WARNING: Image for service setup was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Building elasticsearch
[+] Building 1.4s (5/5) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 271B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 129B                                                                                0.0s
 => [internal] load metadata for docker.elastic.co/elasticsearch/elasticsearch:8.2.2                                                                   1.2s
 => CACHED [1/1] FROM docker.elastic.co/elasticsearch/elasticsearch:8.2.2@sha256:0101bbe4f8e9deeb01768955c7007d0a2927c3ea320fa6fb1f87ef04992caf9d      0.0s
 => exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:8de4dfc9a146c82d22def80a6e1163ffe80b35df5835b9ce936fe6e67cced2af                                                           0.0s
 => => naming to docker.io/library/efk-reprex_elasticsearch                                                                                0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
WARNING: Image for service elasticsearch was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Building kibana
[+] Building 147.0s (5/5) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 241B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 129B                                                                                0.0s
 => [internal] load metadata for docker.elastic.co/kibana/kibana:8.2.2                                                                                2.5s
 => [1/1] FROM docker.elastic.co/kibana/kibana:8.2.2@sha256:f024c0d47b7a207aacb342c5638a0b79011e8dd988e112f059a306e8f6c765f7                         144.4s
 => => resolve docker.elastic.co/kibana/kibana:8.2.2@sha256:f024c0d47b7a207aacb342c5638a0b79011e8dd988e112f059a306e8f6c765f7                           0.0s
 => => sha256:0ad58e9fd51ec50166d355ab9f07c0068e30a500331c00d8f5a724779b6e9eb3 8.65kB / 8.65kB                                                         0.0s
 => => sha256:c349a5b888e45f599d4fa424c6be5e88f3f46d6e4e834a9eee2b0f123d38ca5b 201B / 201B                                                             0.6s
 => => sha256:1992aa49f199f010afb1aca4fa87d70573eb146911dd29a0ba8b5fc50d99cee7 10.15kB / 10.15kB                                                       0.6s
 => => sha256:adf5a8c7436a08a3cf92f726ce3763ac0b93d2b9e74d9d2dd1b9863612b1634e 2.69kB / 2.69kB                                                         0.0s
 => => sha256:f024c0d47b7a207aacb342c5638a0b79011e8dd988e112f059a306e8f6c765f7 685B / 685B                                                             0.0s
 => => sha256:f71664fc597a0578e571240fdeb6625a36a5dc1991ff78e668c3123514ba0782 22.70MB / 22.70MB                                                       8.9s
 => => sha256:9362dc907f7a7da2f533368c1de6f460a35c5e7dc538256120728f9a8ca775a4 17.83MB / 17.83MB                                                      23.9s
 => => sha256:89732bc7504122601f40269fc9ddfb70982e633ea9caf641ae45736f2846b004 39B / 39B                                                               0.9s
 => => sha256:030d09510f9457350ba66feb68dfa7ce2c810666a4a643eefed7e90291996974 5.92kB / 5.92kB                                                         1.2s
 => => sha256:89c579d1a96ca06e37e5df30d3c10965d3fe5b9f050ddfa4af7b83525fe45f94 290.10MB / 290.10MB                                                   127.8s
 => => sha256:af0d3a2d16733288c93d66316c8ef82363757c51083ab3a862985d0e310ac02e 142B / 142B                                                             9.1s
 => => extracting sha256:f71664fc597a0578e571240fdeb6625a36a5dc1991ff78e668c3123514ba0782                                                              1.0s
 => => sha256:aae240ad8849f405a001095a202cc16a7de98e1a51cdee75481203ac0f29654e 418B / 418B                                                             9.3s
 => => sha256:a9182908b4a86d075434becf5f0a1b888c5d582eae9072ae257e34b6cb48235f 4.81kB / 4.81kB                                                         9.5s
 => => sha256:fd935a4efbc88095473c33c40efa803cb3fca7eb072f0142041fb074552cd622 418B / 418B                                                             9.6s
 => => sha256:d4bd6c860c416dfe118ec8ba4274120ce246ff89144ba1e16f7d857ed8127d65 208.24kB / 208.24kB                                                    10.0s
 => => extracting sha256:1992aa49f199f010afb1aca4fa87d70573eb146911dd29a0ba8b5fc50d99cee7                                                              0.0s
 => => sha256:02da536ed84ee43f4e4bc304fc094c89415bf547754dc9f76324e297842b0975 2.02kB / 2.02kB                                                        10.2s
 => => extracting sha256:c349a5b888e45f599d4fa424c6be5e88f3f46d6e4e834a9eee2b0f123d38ca5b                                                              0.0s
 => => extracting sha256:9362dc907f7a7da2f533368c1de6f460a35c5e7dc538256120728f9a8ca775a4                                                              0.4s
 => => extracting sha256:89732bc7504122601f40269fc9ddfb70982e633ea9caf641ae45736f2846b004                                                              0.0s
 => => extracting sha256:030d09510f9457350ba66feb68dfa7ce2c810666a4a643eefed7e90291996974                                                              0.0s
 => => extracting sha256:89c579d1a96ca06e37e5df30d3c10965d3fe5b9f050ddfa4af7b83525fe45f94                                                             15.5s
 => => extracting sha256:af0d3a2d16733288c93d66316c8ef82363757c51083ab3a862985d0e310ac02e                                                              0.0s
 => => extracting sha256:aae240ad8849f405a001095a202cc16a7de98e1a51cdee75481203ac0f29654e                                                              0.0s
 => => extracting sha256:a9182908b4a86d075434becf5f0a1b888c5d582eae9072ae257e34b6cb48235f                                                              0.0s
 => => extracting sha256:fd935a4efbc88095473c33c40efa803cb3fca7eb072f0142041fb074552cd622                                                              0.0s
 => => extracting sha256:d4bd6c860c416dfe118ec8ba4274120ce246ff89144ba1e16f7d857ed8127d65                                                              0.0s
 => => extracting sha256:02da536ed84ee43f4e4bc304fc094c89415bf547754dc9f76324e297842b0975                                                              0.0s
 => exporting to image                                                                                0.0s
 => => exporting layers                                                                                0.0s
 => => writing image sha256:0ad58e9fd51ec50166d355ab9f07c0068e30a500331c00d8f5a724779b6e9eb3                                                           0.0s
 => => naming to docker.io/library/efk-reprex_kibana                                                                                0.0s

Use 'docker scan' to run Snyk tests against images to find vulnerabilities and learn how to fix them
WARNING: Image for service kibana was built because it did not already exist. To rebuild this image you must use `docker-compose build` or `docker-compose up --build`.
Creating efk-reprex_elasticsearch_1 ... done
Creating efk-reprex_setup_1         ... done
Creating efk-reprex_kibana_1        ... done

No worries, glad it works!

#!/bin/bash
docker run --rm -v $(pwd)/config.yaml:/etc/loki/config.yaml -v $(pwd)/data:/tmp/loki -p 3100:3100 grafana/loki:2.5.0 "-config.file=/etc/loki/config.yaml"
Greetings,
your logs indicate that your machine is low on storage. Since the default values are percentage based, they will trigger even if you still have plenty of storage left,
but exceed 90% of your total storage.
Elastic search fails to retrieve the password hash when a shard is not available due to low storage:
elasticsearch_1  | {"@timestamp":"2022-06-20T13:56:06.973Z", "log.level":"ERROR", "message":"failed to retrieve password hash for reserved user [kibana_system]", "ecs.version": "1.2.0","service.name":"ES_ECS","event.dataset":"elasticsearch.server","process.thread.name":"elasticsearch[ecfad7cdffbc][transport_worker]
[```

This happens due to the default values of the high disk watermark, which are set at 90% for high and 95% for flood:

elasticsearch_1  | {"@timestamp":"2022-06-20T13:55:57.997Z", "log.level": "WARN", "message":"high disk watermark [90%] exceeded on [7dX6kMvsRvmjXZVi0ugi_w][ecfad7cdffbc][/usr/share/elasticsearch/data] free: 4.6gb[9.9%], shards will be relocated away from this node; currently relocating away shards totalling [0] bytes; the node is expected to continue to exceed the high disk watermark when these relocations are complete", "ecs.version":
[```
You can adjust those settings via the elasticsearch config:
diff --git a/elasticsearch/config/elasticsearch.yml b/elasticsearch/config/elasticsearch.yml
index 3e82379..f0a3e15 100644
--- a/elasticsearch/config/elasticsearch.yml
+++ b/elasticsearch/config/elasticsearch.yml
@@ -5,6 +5,11 @@
 cluster.name: "docker-cluster"
 network.host: <IP_ADDRESS>

+cluster.routing.allocation.disk.threshold_enabled: true
+cluster.routing.allocation.disk.watermark.flood_stage: 5gb
+cluster.routing.allocation.disk.watermark.low: 30gb
+cluster.routing.allocation.disk.watermark.high: 20gb
+
 ## X-Pack settings
 ## see https://www.elastic.co/guide/en/elasticsearch/reference/current/security-settings.html
 #

If its not an stora
changeme
elk-setup-1          | {"error":{"root_cause":[{"type":"validation_exception","reason":"Validation Failed: 1: passwords must be at least [6] characters long;"}],"type":"validation_exception","reason":"Validation Failed: 1: passwords must be at least [6] characters long;"},"status":400}
Best Regards
Mydayyy

Thanks a lot, I'll try this out.


Adding 200m structures to biopandas

Small update to support AF2 v3.
Very high structure:code ratio in this PR 😁

Hello @a-r-j! Thanks for opening this PR.

In the file biopandas/mmcif/pandas_mmcif.py:

Line 83:89: E501 line too long (144 > 88 characters)
Line 94:89: E501 line too long (124 > 88 characters)
Line 116:89: E501 line too long (135 > 88 characters)

In the file biopandas/pdb/pandas_pdb.py:

Line 131:89: E501 line too long (151 > 88 characters)
Line 142:89: E501 line too long (124 > 88 characters)
Line 165:89: E501 line too long (138 > 88 characters)

Do see the Hitchhiker's guide to code style

Thanks a lot for the update!

It looks like tests are failing due to metadata changes in the local AF2 pdb/mmcif files. I'll fix this up.

Thanks! So it looks like they also updated the previous alphafold-v2 structures? If that's just the meta-data, theoretically we could also just check for Atom entries. Otherwise, I am not sure whether we would have to update the check every few months or so 😅

It looks like it was just metadata. They just changed the date in the PDB file. In the mmCIF there were more changes but coords are unaffected. I added another block to test for the latest release but updated the old test to make sure everything works nicely with retrieving structures from previous releases too.

Awesome, thanks!


Update sbt-assembly to 0.15.0

Updates com.eed3si9n:sbt-assembly from 0.14.10 to 0.15.0.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.eed3si9n", artifactId = "sbt-assembly" } ]

labels: sbt-plugin-update, semver-minor

Codecov Report

Merging #1 (aae9e84) into master (1e27808) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##            master        #1   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            1         1
=========================================
  Hits             1         1

Continue to review full report at Codecov.

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

Superseded by #80.


Laravel 10 support

Summary of problem or feature request
In a fresh LARAVEL 10.0.3 project, after only adding composer require laravel/ui and php artisan ui bootstrap --auth, installing the latest yajra/laravel-datatables-oracle throws an error concerning conflicting libraries.
Code snippet of problem
PS> composer require yajra/laravel-datatables-oracle:"^10.0"
./composer.json has been updated
Running composer update yajra/laravel-datatables-oracle
Loading composer repositories with package information
Info from https://repo.packagist.org: #StandWithUkraine
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires yajra/laravel-datatables-oracle 10.0 -> satisfiable by yajra/laravel-datatables-oracle[v10.0.0].
    - yajra/laravel-datatables-oracle v10.0.0 requires illuminate/database ^9 -> found illuminate/database[v9.0.0, ..., v9.52.0] but these were not loaded, likely because it conflicts with another require.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

System details

Windows 11 Version 22H2
PHP Version 8.2.3
Laravel Version 10.0.3
Laravel-Datatables Verssion 10

It works in the latest version 10.3.
composer require yajra/laravel-datatables-oracle:"^10.3"

Closed by creator.

The documentation should be adapted...


pass email , username , message in customer or visitor sdk

I want to pass name, email, message at the start of chat just like live chat own app on their website and after that will continue the chat?

import React, { useRef, useEffect } from 'react';
import LiveChat from '../LiveChat';
const Chat = ({}) => {
const chat = useRef(null);
useEffect(() => {
if (chat.current != null) {
chat.current.visitorSDK.setVisitorData({
name: 'Testing name costumer',
email<EMAIL_ADDRESS>pageUrl: 'http://example.org/pricing',
pageTitle: 'Pricing',
customProperties: {
login: 'dadsad',
customerId: '31231232',
},
});
}
}, [chat]);
return (

);
};
export default Chat;

@eduduardo Is there any solution for passing username and email to the chat end ?
Any suggestions?


Add TypeScript types

Thank you for this pr. As long as I really like TS and cannot imagine coding without it, this package will remain as a non-ts package.


Remove unused code blocks

Any code block that's not being used currently should be removed from the controller.

Removed move, copy, create file actions as they weren't being used


26/10/22  There is a typo error on the OPEN SCIENCE page

Correcting the typo error on the OPEN SOURCE page

]](https://osc-ksa.com/)

@sandygudie @alswajiab @BatoolMM I want to take up this task to make all necessary corrections

Hello @BatoolMM @alswajiab @sandygudie I am an outreachy student and I would love to take up this task in order to make all necessary corrections. Thanks

@GuddyTech go ahead and solve it


How to show only table

What feature do you want to see added?
I need to show only pure table data. No charts, graphs ...
It is possible here.  I checked the code and can not find any solution for that now.
Thx
Upstream changes
No response

Hi,
sorry for the late response. No, that is not possible for now. You can have a look into the example data files, processed by the plugin. Do you have an example of your data input? Then we can have a look, if we can implement such a feature.

Hi, thx for answer. In need ust simple .csv format. That means 2 dimensional array
List<List>
Ex:
Date;Node name;Reason
10.10.2022 17:11:50.571;OracleServer8_05;java.lang.Exception: The node "OracleServer8_05" will be marked as unrepairable.
10.10.2022 22:36:30.063;SLES15_02;java.lang.Exception: <strong>The command on the node SLES15_02 cause exception!
11.10.2022 05:04:09.771;OracleServer8_05;Failed checkout repository _Library_Test_Jenkins on branch master.;
11.10.2022 05:04:09.862;OracleServer8_05;java.lang.Exception: The node "OracleServer8_05" will be marked as unrepairable.
11.10.2022 05:09:42.226;OracleServer8_05;Failed checkout repository _Library_Test_Jenkins on branch master.

Looks like a log file ;-) But it will be helpful to have it. (because of sorting, paging and filtering)
But any way, I discuss it with @uhafner and I thing it will be fine, when the step is implemented in data-table-plugin as well. But nobody has time for that now.

Hmm honestly I don't have any time right now too. I can offer to deal with it during the christmas season.

Dont worry, when my boss will see the tables in Jenkins, then my answer will be that the company shall spend 'few' hours and we shall implemented in (here or data-tables does not matter ) ;-) . Other words, it will be nice, but not must have. About christmas seasonthat the reason why I am under pressure now. I will keep this time with my family. But of core when you want and has time, you can do that ;-) . One last thing, maybe is the csv format too simple. Maybe it shall be json format with all information, that the table self needs. I mean ID, Columns-definition and Data(rows) So it will be possible to show int / date / string / html content ... , and no extra parser or what ever will be necessary. And (very nice feature), when usersomehow' mark the column you can show the trend data and charts as well. For ex, marking column 'Node name' shall count how often the node 'OracleServer8_05' will appears. (but I see a possible way now. Maybe it can be done by next-gen-warnigns plugin, hm I will try it)

There is an open issue on how to display multilevel (#54 ).
Moreover in your data, there is no value (aim of this plugin is to condensate, parse and display sums, and various statistics).
I wonder if the best is to use warning ng which aims to parse and analyze error reports. Then convert the csv file format into an official error format (xml, ???). There is dozens of supported file formats. Depending on the kind of log and numbers of column, one of these format should match.

Yeh, but anyway show simple table will be use case.

I have a job node-labeler which runs every day and set correct labels on our nodes. That means admin does not care about that and no body can broke our nodes. In this case I print on the end list of all nodes with assigned resources.
Or other example a job named try-ot-repair -nodes which runs every day and try to correct common mistakes on all our nodes. When is finished I print all the nodes info in log.

For this uses cases is useless to parse all of the line in warnings-ng. It will be better to show it in a simple table. But as I mentioned about I will create new step in the data-table-plugin when no body can do it here.
Thx for your time guys

@mPokornyETM I think it makes more sense, if we add this basic table step to the data-table-api-plugin. I can help you with this if you want.

It will be great when you do that, because at the moment I am totally over by my daily business and lockable-resource-plugin. Maybe in begins next year (Hopefully) have more time for new development.

But anyway, you can close this item here. I thing we have a consensus, that it has nothing to do with this plugin. Sorry to waste your time.


Roll Flutter Engine from bedc49efc85c to 48137f005d49 (12 revisions)

https://github.com/flutter/engine/compare/bedc49efc85c...48137f005d49
2023-10-27<EMAIL_ADDRESS>Roll Skia from 22f5419438c4 to 0122c0e18d26 (1 revision) (flutter/engine#47373)
2023-10-27<EMAIL_ADDRESS>Roll Skia from 5262cbff56b1 to 22f5419438c4 (1 revision) (flutter/engine#47372)
2023-10-27<EMAIL_ADDRESS>Roll Skia from fe61b3467547 to 5262cbff56b1 (1 revision) (flutter/engine#47371)
2023-10-27<EMAIL_ADDRESS>Roll Skia from fbdd7d97b26e to fe61b3467547 (1 revision) (flutter/engine#47370)
2023-10-27<EMAIL_ADDRESS>Roll Skia from 2246f3473053 to fbdd7d97b26e (2 revisions) (flutter/engine#47369)
2023-10-27<EMAIL_ADDRESS>Roll Skia from ec4c6b3a6690 to 2246f3473053 (1 revision) (flutter/engine#47366)
2023-10-27<EMAIL_ADDRESS>[Impeller] Add FilterContents::GetSourceCoverage to enable filtered saveLayer clipping. (flutter/engine#47183)
2023-10-27<EMAIL_ADDRESS>Roll Skia from bc8ca57868d2 to ec4c6b3a6690 (1 revision) (flutter/engine#47365)
2023-10-27<EMAIL_ADDRESS>Don't re-initialize the default RenderSurface when returning from hybrid composition mode (flutter/engine#47358)
2023-10-27<EMAIL_ADDRESS>Manual roll Dart SDK from 360370ff93b0 to 18678a3eddb7 (9 revisions) (flutter/engine#47357)
2023-10-26<EMAIL_ADDRESS>Roll Skia from 93a0ad4d7ca6 to bc8ca57868d2 (2 revisions) (flutter/engine#47359)
2023-10-26<EMAIL_ADDRESS>Roll Fuchsia Mac SDK from YSn00b0Trsu2vdhIq... to 1ngqKBnmTtmFM6aBD... (flutter/engine#47363)
Also rolling transitive DEPS:
fuchsia/sdk/core/mac-amd64 from YSn00b0Trsu2 to 1ngqKBnmTtmF
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC aaclarke@google.com,rmistry<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To file a bug in Flutter: https://github.com/flutter/flutter/issues/new/choose
To report a problem with the AutoRoller itself, please file a bug:
https://issues.skia.org/issues/new?component=1389291&template=1850622
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+doc/main/autoroll/README.md

Commit queue failed; closing this roll.


How to get expiry date [valid to] from a certificate?

Hello Team,
I would like to know how to get the expiry date of certificate . This is to check before doing cert pinning .  There are some ways to get using openssl, however I would like know if there is a way in iOS security API to get the expiry date of a certificate.
Appreciate your input.

For general help, please ask on StackOverflow.


lock file version 4 requires -Znext-lockfile-bump

Problem

I have tried so many time  but always fail.
Cargo build act, but anchor build not act
help me seniors
Steps
No response
Possible Solution(s)
No response
Notes
No response
Version
No response

Lockfile v4 has been stable since Rust 1.78.  We are making it the default version as of 1.83 nighties unless your MSRV is below 1.78.
I would look into

If you can bump your Rust version
Enforce a lower Rust version is used for anyone who generates the lockfile
Set package.rust-version, if applicable

Thank you for your response.

`[workspace]
members = [
"programs/*"
]
resolver = "2"
[profile.release]
overflow-checks = true
lto = "fat"
codegen-units = 1
[profile.release.build-override]
opt-level = 3
incremental = false
codegen-units = 1
`

I provide this info, give me advice, seniors

Can you provide full reproduction steps with only cargo?

Thank you for your help.
I just modify resolver=4 to resolver=3 in Cargo.toml and run anchor build, then this issue is resolved.

@Kelvin-1013
In ### Cargo.toml, I changed###  resolver=2 to ### resolver=3, and then I got the following error:
palash@DESKTOP-QPUGO84:~/my-project$ anchor build
Error: Error reading manifest from path: /home/palash/my-project/Cargo.toml
Caused by:
0: TOML parse error at line 5, column 12
|
5 | resolver = "3"
|            ^^^
unknown variant 3, expected 1 or 2
1: TOML parse error at line 5, column 12
     |
   5 | resolver = "3"
     |            ^^^
   unknown variant `3`, expected `1` or `2`

resolver is for a different meaning than lockfile version

@epage
Then what should I update? Could you please guide me?

As this issue is about lockfiles and you are changing the manifest, this is different.  It would be good to provide standard details for someone to help you

Reproduction steps outside of anchor
What problem you are trying to solve by switching to workspace.resolver = "3"
What version of Cargo is being used.

This also looks to more be a Cargo support concern than a bug or feature request, so I would recommend posting about this on https://users.rust-lang.org/

I'm getting the same error

Solution in https://github.com/coral-xyz/anchor/issues/3392#issuecomment-2508412018.
Sorry for the disturbance. It would be nice to lock this issue, given the problem is not about this repository.

Modify the version = "4" at the top of the Cargo.lock file to version = "3".

@kaka527  Thanks a lot, it’s all good now!

Modify the version = "4" at the top of the Cargo.lock file to version = "3".

Only solution that worked for me, thanks @kaka527

Modify the version = "4" at the top of the Cargo.lock file to version = "3".

yes. It worked. I don't understand why.

yes, it worked. Many thanks!

I am going to close this, as there is no action needed.
See the updated PR description that provides some solutions if you're stuck.


featureadd monotonice timer for pipeline task

Proposed changes
Add monotonice timer for piplinetask;
WaitBfTime

Task1BeginExecuteTime
Task2EosTime
Task3SrcPendingFinishOverTime
Task4DstPendingFinishOverTime
Task5TotalTime
Task6ClosePipelineTime

How to use
 PipelineTask  (index=2):(Active:  69.748ms,  %  non-child:  0.00%)
                                  -  Sink:  AggSinkOperator(10004)
                                  -  OperatorIds(source2root):  [ScanOperator(10002),  HashJoinProbeOperator(10003)]
                                  -  CoreChangeTimes:  0
                                  -  ExecuteTime:  69.47ms
                                      -  CloseTime:  93.209us
                                      -  FinalizeTime:  60ns
                                      -  GetBlockTime:  66.822ms
                                      -  OpenTime:  587.750us
                                      -  PrepareTime:  2.496us
                                      -  SinkTime:  825.889us
                                  -  GetBlockCounter:  828
                                  -  NumBlockedBySinkTimes:  0
                                  -  NumBlockedBySrcTimes:  1
                                  -  NumBlockedTimes:  4
                                  -  NumScheduleTimes:  4
                                  -  NumYieldTimes:  0
                                  -  Task1BeginExecuteTime:  5s541ms
                                  -  Task2EosTime:  5s680ms
                                  -  Task3SrcPendingFinishOverTime:  5s680ms
                                  -  Task4DstPendingFinishOverTime:  5s680ms
                                  -  Task5TotalTime:  5s680ms
                                  -  Task6ClosePipelineTime:  5s680ms
                                  -  TaskCpuTime:  69.645ms
                                  -  WaitBfTime:  993.535ms
                                  -  WaitScheduleTime:  32.7us
                                  -  WaitSinkTime:  0ns
                                  -  WaitSourceTime:  70.755ms
                                  -  WaitWorkerTime:  2.199ms

1 Task1BeginExecuteTime= 5s541ms, it means the task wait bf or wait dependence costs 5s+ before begin to execute first time.
Then wait bloom filter time :WaitBfTime = 993.535ms,
Wait dependence time,  current task is hash probe, then we can see HashBuildCosts 5s
 PipelineTask  (index=3):(Active:  640.78us,  %  non-child:  0.00%)
                                  -  Sink:  HashJoinBuildSink(10001)
                                  -  OperatorIds(source2root):  [ExchangeSourceOperator(10000)]
                                 -  WaitSourceTime:  5s488ms

2 Task2EosTime=5s680ms, it means task get a eos flag time since task is created
3 Task3SrcPendingFinishOverTime:  5s680ms and Task4DstPendingFinishOverTime:  5s680ms, task finish pendingfinish status since task is created, Task3SrcPendingFinishOverTime - Task2EosTime  = the real time cost in pending finish
4 Task6ClosePipelineTime=5s680ms means PiplineContext try to close_a_pipeline since task is created.

run buildall

(From new machine)TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 53.64 seconds
stream load tsv:          544 seconds loaded<PHONE_NUMBER>9 Bytes, about 131 MB/s
stream load json:         19 seconds loaded<PHONE_NUMBER> Bytes, about 118 MB/s
stream load orc:          65 seconds loaded<PHONE_NUMBER> Bytes, about 16 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
insert into select:          28.8 seconds inserted 10000000 Rows, about 347K ops/s
storage size:<PHONE_NUMBER>6 Bytes


How to work with your package

Hi, I have am using your package but having some trouble getting up and going and can't seem to find any documentation or help besides this:
I am using the javascript from the Plaid API documentation so the user picks their back and enters their credentials.  Then I receive a public token which I pass to a PlaidController where I am trying to implement your package to exchange it for an access token and check balance.
I get as far as getting a public token and sending it to my controller, but using your package I am not sure how I exchange that for an access token or get the balance, etc.
Here is what the Plaid API documentation gave me for the pop up to select back and enter credentials:
`<script src="https://cdn.plaid.com/link/v2/stable/link-initialize.js"></script>
<script type="text/javascript">
var handler = Plaid.create({
  clientName: 'Plaid Walkthrough Demo',
  env: 'sandbox',
  key: 'abc12345667890', // Replace with your public_key to test with live credentials
  product: ['auth', 'transactions'],
  //webhook: '[WEBHOOK_URL]', // Optional – use webhooks to get transaction and error updates
  selectAccount: false, // Optional – trigger the Select Account
  onLoad: function() {
    // Optional, called when Link loads
  },
  onSuccess: function(public_token, metadata) {
    // Send the public_token to your app server.
    // The metadata object contains info about the institution the
    // user selected and the account ID, if `selectAccount` is enabled.
    $.post('/get_access_token', {
      _token: $('meta[name=csrf-token]').attr('content'),
      public_token: public_token,
    });

    console.log(public_token);
    console.log(metadata);
  },
  onExit: function(err, metadata) {
    // The user exited the Link flow.
    if (err != null) {
      // The user encountered a Plaid API error prior to exiting.
    }
    // metadata contains information about the institution
    // that the user selected and the most recent API request IDs.
    // Storing this information can be helpful for support.
  }
});

$('#link-button').on('click', function(e) {
  handler.open();
  // Alternatively, you can have a specific institution
  // prompt for authentication. Example:
  //
  // handler.open('ins_100000');
  //
  // This will open Link with Union Bank as the institution.
});
</script>`

Once I do that I receive a public token in my PlaidController but how do I interact with their API and exchange this for an access token using your package?

Yeah - Sorry my documentation isn't complete yet. I recently replied to another person with the following answer: https://github.com/oldtimeguitarguy/plaid/issues/1#issuecomment-266752990
Please take a look at that - hopefully it can point you in the right direction. Based on what I'm seeing here, it looks like you're using JS to get the token from the API, then you aim to use that token to make requests via your PHP server.
I'm not too familiar with what the JS API returns, but assuming that this "public token" is the same thing as the "access token" required with each PHP request, I would say you need to just post that to your server after you receive it from Plaid. When the server grabs it, you need to throw it into a class that implements OldTimeGuitarGuy\Plaid\Contracts\User. Then you just pass an instance of that class into each request type you need to perform.
Take a look at the link - I have a pretty good example there.


Uncaught TypeError: Array.prototype.indexOf called on null or undefined

[Enter steps to reproduce:]

Saving a tex file

Atom: 1.16.0 x64
Electron: 1.3.13
OS: Microsoft Windows 7 Enterprise
Thrown From: atom-latex package 0.7.6
Stack Trace
Uncaught TypeError: Array.prototype.indexOf called on null or undefined
At C:\Users\fmheu\.atom\packages\atom-latex\lib\manager.coffee:240

TypeError: Array.prototype.indexOf called on null or undefined
    at indexOf (native)
    at Manager.module.exports.Manager.prevBibWatcherClosed (/packages/atom-latex/lib/manager.coffee:240:21)
    at /packages/atom-latex/lib/manager.coffee:220:29
    at Array.map (native)
    at Manager.module.exports.Manager.findDependentFiles (/packages/atom-latex/lib/manager.coffee:214:20)
    at /packages/atom-latex/lib/manager.coffee:162:14)
    at emitTwo (events.js:106:13)
    at FSWatcher.emit (events.js:191:7)
    at /packages/atom-latex/node_modules/chokidar/index.js:191:15)
    at FSWatcher._emit (/packages/atom-latex/node_modules/chokidar/index.js:233:5)
    at /packages/atom-latex/node_modules/chokidar/lib/nodefs-handler.js:263:16)
    at FSReqWrap.oncomplete (fs.js:123:15)

Commands
     -2:47.4.0 markdown-writer:insert-new-line (input.hidden-input)
     -2:47.4.0 editor:newline (input.hidden-input)
     -2:46.7.0 intentions:highlight (input.hidden-input)
     -0:29.1.0 markdown-writer:insert-new-line (input.hidden-input)
     -0:29.1.0 editor:newline (input.hidden-input)
     -0:28.5.0 markdown-writer:insert-new-line (input.hidden-input)
     -0:28.5.0 editor:newline (input.hidden-input)
     -0:28.4.0 intentions:highlight (input.hidden-input)
     -0:28.4.0 core:paste (input.hidden-input)
     -0:27.6.0 markdown-writer:insert-new-line (input.hidden-input)
     -0:27.6.0 editor:newline (input.hidden-input)
     -0:26.9.0 core:move-up (input.hidden-input)
 12x -0:26.7.0 core:move-right (input.hidden-input)
  7x -0:25.4.0 core:select-right (input.hidden-input)
     -0:18.8.0 intentions:highlight (input.hidden-input)
     -0:18.7.0 core:save (input.hidden-input)

Non-Core Packages
advanced-open-file 0.16.6
atom-beautify 0.29.23
atom-clock 0.1.7
atom-latex 0.7.6
autocomplete-bibtex 0.7.0
autocomplete-python 1.8.63
autoupdate-packages 1.3.1
busy-signal 1.4.1
editorconfig 2.2.2
file-icons 2.1.4
git-plus 7.7.0
highlight-selected 0.13.1
imdone-atom 2.2.5
intentions 1.1.2
keybinding-cheatsheet 0.1.1
language-markdown 0.21.0
language-matlab 0.2.1
language-pfm 0.82.0
languagetool 0.1.1
latex-autocomplete 1.0.0
linter 2.1.4
linter-coffeelint 1.2.1
linter-flake8 2.2.1
linter-proselint 3.2.1
linter-ui-default 1.2.3
linter-write-good 0.9.0
markdown-preview-plus 2.4.9
markdown-toc 0.4.2
markdown-writer 2.6.4
merge-conflicts 1.4.4
minimap-split-diff 0.3.7
multi-cursor 2.1.5
open-terminal-here 2.3.0
pdf-view 0.57.0
project-manager 3.3.4
script 3.14.1
split-diff 1.3.0
sync-settings 0.8.1
tasks 2.6.6
termination 0.5.0
wordcount 2.10.4
Zen 0.16.4

Hey,
I am aware of this, made a typo in my last commit, fix is on the way!

I am now receiving this error. Error message links to this issue.
[Enter steps to reproduce:]

...
...

Atom: 1.22.1 x64
Electron: 1.6.15
OS: Mac OS X 10.13.1
Thrown From: atom-latex package 0.8.2
Stack Trace
Uncaught TypeError: Array.prototype.indexOf called on null or undefined
At /Users/cnsetzer/.atom/packages/atom-latex/lib/builder.coffee:37

TypeError: Array.prototype.indexOf called on null or undefined
    at indexOf (<anonymous>)
    at Builder.module.exports.Builder.saveonBuild (/packages/atom-latex/lib/builder.coffee:37:34)
    at Builder.module.exports.Builder.build (/packages/atom-latex/lib/builder.coffee:19:18)
    at /packages/atom-latex/lib/main.coffee:33:48)
    at CommandRegistry.handleCommandEvent (/Applications/Atom.app/Contents/Resources/app/src/command-registry.js:381:36)
    at KeymapManager.module.exports.KeymapManager.dispatchCommandEvent (/Applications/Atom.app/Contents/Resources/app/node_modules/atom-keymap/lib/keymap-manager.js:621:22)
    at KeymapManager.module.exports.KeymapManager.handleKeyboardEvent (/Applications/Atom.app/Contents/Resources/app/node_modules/atom-keymap/lib/keymap-manager.js:412:28)
    at WindowEventHandler.module.exports.WindowEventHandler.handleDocumentKeyEvent (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:100:42)
    at HTMLDocument.<anonymous> (/Applications/Atom.app/Contents/Resources/app/src/window-event-handler.js:3:65)

Commands
     -9:12.3.0 core:save (input.hidden-input)
     -8:54.7.0 application:open (atom-pane.pane.active)
     -8:38.6.0 atom-latex:build (input.hidden-input)
  3x -8:31.2.0 core:undo (input.hidden-input)
  2x -8:22.9.0 editor:newline (input.hidden-input)
  2x -8:22.2.0 core:move-up (input.hidden-input)
     -8:17.9.0 application:open (input.hidden-input)
     -7:54.1.0 core:copy (input.hidden-input)
     -7:51.5.0 core:paste (input.hidden-input)
  2x -7:46.8.0 core:delete (input.hidden-input)
  2x -7:44.8.0 atom-latex:build (input.hidden-input)
     -7:31.8.0 core:save (input.hidden-input)
     -7:29.8.0 atom-latex:build (input.hidden-input)
     -6:16.9.0 core:backspace (input.hidden-input)
     -6:09.6.0 core:paste (input.hidden-input)
  2x -6:05.7.0 atom-latex:build (input.hidden-input)

Non-Core Packages
atom-latex 0.8.2
autocomplete-python 1.10.5
busy-signal 1.4.3
grammar-token-limit 0.1.1
intentions 1.1.5
language-latex 1.1.1
linter 2.2.0
linter-pycodestyle 2.1.3
linter-ui-default 1.6.10
pdf-view 0.61.0

@cnsetzer
While the error message is the same, the issue is from elsewhere.
Could I request you to open up the Dev console (ctrl+shift+i)  and report back the output what the output of atom_latex.latex.texFiles looks like when you encounter this error?

@ashthespy
When I open the console and look through, there is no output for atom_latex.latex.texFiles. It appears that atom_latex.latex has no attribute .texFiles. It returns
> atom_latex.latex.texFiles
<- undefined

As expected, the usual questions:
How do you define the LaTeX root file, and what does your project structure look like?

Ah that's it. It seems that this only happens when I am starting a new project from an exisiting .tex file, i.e. where I only have a *.tex file in my directory. If I am working with a project that has all of the build/auxiliary files I do not run into this issue. This could be because I have been using the Build command rather than Build Here, without having an absolute path explicitly defined.
Yes, the atom_latex.latex.mainFile is defined as expected, ~/.../file.tex. My project structure is simply to isolate my latex into its own self-contained directory and edit/build everything there.

@cnsetzer
It should still work with just a *.tex by trying to automagicly determine which is the main file when running build it has nothing to do with the other build/auxiliary files.  Especially so if you have a single 'Atom Project' with just one file.tex. Or, even if you have mixed project with code and LaTeX, it should still work, for example take this package's repo structure. Opening spec/latex_project/main.tex and hitting build should work.
Could you share more details on your exact project structure that throws this error so I can try reproducing it?

@ashthespy
I would like to, but I'm embarrassed to say I cannot successfully recreate the issue anymore. Though nothing (I know of) should have changed from yesterday to today, when I repeat the steps that I listed above I cannot replicate the error as was happening yesterday. I'm sorry for bothering you with this, I'll let you know if I find out what has happened to change the situation.