AGFi  TAXATION CHANGE

Modify Agfi Tax on Buys and Sells
To reduce total taxes by 28%
Apply a 5% tax on buys (currently 12%)
Leave sell tax at 13% change the parameters.(currently 13%)
As mentioned in main to try generate extra volume. Proposal made to change tax % and change tax chanel distribution:-
Buys 5% :-
1% operations
4% treasury
Sells 13% :-
7% treasury
3% rewards
2% operations
1% autoburn
The idea behind the change is to hopefully create extra buy pressure inturn creating volume.
Pros:- more % tax overall will go to the Treasury.
Cons:- less eth rewards distributed to holders.
This proposal is more to see if lower taxes on buys will gain volume. Most members feel rewards can be added back in the future. Also think the rewards are better invested to treasury giving trader the chance to build treasury at a faster pace.

How does this reduce taxes by 28%?

At the moment taxes are 25% the reduction takes it to 18% total taxes, which is the equivalent of a 28% reduction in total taxes.

After closing staking, the reward became 4,5%, the idea to remove from buy taxe is OK but from sell taxe better to be 4,5% if remove all the holders taxe, its no more points to hold agfi like on the beginning.
Remember last time you where saying no buyback to burn from trade profit...
If you remove or reduce too much taxes for holders and never buy back , what's the point to hold?
Thanks

After closing staking, the reward became 4,5%, the idea to remove from buy taxe is OK but from sell taxe better to be 4,5% if remove all the holders taxe, its no more points to hold agfi like on the beginning. Remember last time you where saying no buyback to burn from trade profit... If you remove or reduce too much taxes for holders and never buy back , what's the point to hold?
Thanks

A change in the distribution is not a problem. The answer to your question why hold. Idea is to get treasury up faster so trader has more funds to play with inturn will get reward ladder into play.

Anymore thoughts in sell tax distribution?

I agree on the tax change but would change the Sell tax to:
Sells 13% :-
6% treasury
3% rewards
2% autoburn
2% operations
Just my 2 cents.

change

The more input the better thanks for spending a few moments with your thoughts

I think the % to ETH rewards is only good with volume. So if it's more attractive to buy there is more upside from the price impact than the rewards. Good idea to change buy tax to 5% and sell tax should be 8% treasury 4% operations to allow for a future marketing cushion.

to

I understand your views on eth rewards, however before posting the proposal we had a discussion with the comunitee and 70% did mention they would be happy to take a drop in % but most felt uncomfortable to not have any rewards completely
Also with operations and future marketing this is a very important subject and will put an extra 1% on sells and reduce treasury on sells to 6%.
We also have to remember these taxes can be changed with any new proposal if circumstances change within the project.
But to have better chances of this proposal being approved by holders the eth rewards on sells will stay the same 3% .

Origional proposal tax channel allocations changed to the following:-
Buys 5%
1% operations
4% treasury
Sells 13%
3% operations
3% rewards
6% treasury
1% autoburn

This Proposal is clean.  I'd approve to advance to vote.

Proposal passed by Agfi Pm's.
Opened for vote on snapshot:-
https://snapshot.org/#/aggregatedfinance.eth/proposal/0x2c90768fb0d227c5fb2460b55a75cc6e40dd8f342dd3dd50f6045f31af72128f

Proposal changes executed based on vote outcome:
https://etherscan.io/tx/0x6fc293a0e0f9caa0fc3955d8cc3b64839f3e74a6b1baf08ef5184f28e6f7782e
https://etherscan.io/tx/0xc55f9d94affb5a676e2383cff1d4d2ba791df45b520539db4da0e27c789496e0


[Question] Contact Callback Alternative?

Currently, we can get contacts like:
const callback = new PhysX.PxSimulationEventCallbackImpl();
callback.onContact = (pairHeader: number, pairs: number, nbPairs: number): void => {
	// ...
}

However, callbacks seem like a roundabout way to get a list of contacts (and eNOTIFY_TOUCH_PERSISTS causes a large hit to performance). Instead, is there simply a list of contacts (Persistent Contact Manifold) we can just iterate through after simulating a step?
scene.simulate(timeStep);
scene.fetchResults(true);

// Iterate through contacts in Persistent Contact Manifold

Thank you for your help! 😄

Please see an example of how iterating through a Persistent Contact Manifold's contacts can be done in Bullet Physics, (which offers both an iterable list of contacts or a callback-based approach):
//Assume world->stepSimulation or world->performDiscreteCollisionDetection has been called

int numManifolds = world->getDispatcher()->getNumManifolds();
for (int i = 0; i < numManifolds; i++)
{
    btPersistentManifold* contactManifold =  world->getDispatcher()->getManifoldByIndexInternal(i);
    const btCollisionObject* obA = contactManifold->getBody0();
    const btCollisionObject* obB = contactManifold->getBody1();

    int numContacts = contactManifold->getNumContacts();
    for (int j = 0; j < numContacts; j++)
    {
        btManifoldPoint& pt = contactManifold->getContactPoint(j);
        if (pt.getDistance() < 0.f)
        {
            const btVector3& ptA = pt.getPositionWorldOnA();
            const btVector3& ptB = pt.getPositionWorldOnB();
            const btVector3& normalOnB = pt.m_normalWorldOnB;
        }
    }
}

Hmm, in PhysX I'm not aware of any other method than the callback approach. There's a section about extracting contact information in the PhysX docs, but they also only mention the simulation callback onContact function so I don't think there is another way.


Proxied files include directory indexes

If a directory contains a period {and thus has an 'extension'} will request it from upstream and cache it.
Example: https://repo.panda-lang.org/releases/activesoap/activesoap/1.0-20050615.083700
It's served as a file, but is a web page. Better option would be to filter our any html file returned from upstream. Probably worth filtering out most mime types for common web files such as images.

Addressed in #544


Updated member logo

DGI's logo has been added to the member page. Closing the pull request. Please reopen if there are any issues.


linker rust-lld not found

🐛 Bug description
On the latest version of rust nightly, attempting to run wasm-pack build fails with the following error:
error: linker `rust-lld` not found
  |
  = note: The system cannot find the file specified. (os error 2)

error: aborting due to previous error

cargo build on the other hand does produce output.
🌍 Your environment
wasm-pack version: 0.8.0
rustc version: rustc 1.35.0-nightly (428943cc2 2019-04-02)

i'm working on reproducing this right now! thanks for the bug report @ZacLiveEarth - were you able to try other rust nightlies? it may be that this is a bug in nightly and not in wasm-pack. additionally, you can feel free to use stable for wasm-pack :) (just in case you didn't know)

ag-dubss-MacBook-Pro:hello-wasm ag_dubs$ wasm-pack build
[INFO]: 🎯  Checking for the Wasm target...
[INFO]: 🌀  Compiling to Wasm...
   Compiling proc-macro2 v0.4.27
   Compiling unicode-xid v0.1.0
   Compiling syn v0.15.29
   Compiling wasm-bindgen-shared v0.2.39
   Compiling cfg-if v0.1.7
   Compiling bumpalo v2.1.0
   Compiling lazy_static v1.3.0
   Compiling wasm-bindgen v0.2.39
   Compiling log v0.4.6
   Compiling quote v0.6.11
   Compiling wasm-bindgen-backend v0.2.39
   Compiling wasm-bindgen-macro-support v0.2.39
   Compiling wasm-bindgen-macro v0.2.39
   Compiling console_error_panic_hook v0.1.6
   Compiling hello-wasm v0.1.0 (/Users/ag_dubs/OpenSource/rustwasm/hello-wasm)
    Finished release [optimized] target(s) in 31.71s
[INFO]: ⬇  Installing wasm-bindgen...
[INFO]: Optional fields missing from Cargo.toml: 'description', 'repository', and 'license'. These are not necessary, but recommended
[INFO]: ✨   Done in 32.02s
[INFO]: 📦   Your wasm pkg is ready to publish at ./pkg.
ag-dubss-MacBook-Pro:hello-wasm ag_dubs$ rustc --version
rustc 1.35.0-nightly (428943cc2 2019-04-02)

i was not able to reproduce. can you tell us more about your system @ZacLiveEarth ?

I am on a Windows machine, I see you are on a Mac. Also, I see from the compilation logs there that you  are dependent on wasm-bindgen 0.2.39, I am using 0.2.40. Anything else you would like to know?
Also, I need nightly because I rely on alloc. I wish there were a way to opt into experimental features without being on nightly, but alas.

that's great info @ZacLiveEarth - thanks! i'll let you know and do my best to reproduce!

I suspect this is likely an upstream rust-lang/rust issue at https://github.com/rust-lang/rust/issues/59661 which is being fixed at https://github.com/rust-lang/rust/pull/59672

thanks @alexcrichton !

This is working now on the latest nightly of rust. Thanks.


refactor: remove instance_type from codemagic.yaml and README.md

Is unnecessary.

⬇ Generated builds by Codemagic for commit 07657f3e342ebc2a3a151816adf5a30389e4087f ⬇

iOS
Android

  Download link
  Download link


fluentd got exception on big log files with 1 million lines

fluentd or td-agent version.
td-agent-3.1.1-0.el7.x86_64
Environment information, e.g. OS.
centos
Your configuration
<source>
  @type tail
  path /var/log/testlogs/*.log
  pos_file /tmp/webapps.log.pos
  read_from_head true
  tag webapps
...
</source>
<source>
  @type tail
  path /home/centos/jobtestlogs/*/*.log,/home/centos/jobtestlogs/*/*/*.log
  exclude_path ["/home/centos/jobtestlogs/webapps/*"]
  pos_file /tmp/jobs.log.pos
  read_from_head true
  tag jobs
...
</source>

Your problem explanation. If you have an error logs, write it together.
The td-agent forward to fluentd, my jobs log file has almost 1 million lines, I got below issue in fluentd and the logs did not write to elasticsearch, if I tructated the logfile to 10000 lines I saw the logs could be written to elasticsearch:
2018-02-26 20:50:31 +0000 [warn]: #0 failed to flush the buffer. retry_time=0 next_retry_seconds=2018-02-26 20:50:32 +0000 chunk="56623a3aebc14c36300fc2f8ad0ae17c" error_class=Fluent::Plugin::ElasticsearchOutput::ConnectionFailure error="Could not push logs to Elasticsearch after 2 retries. Connection reset by peer (Errno::ECONNRESET)"
  2018-02-26 20:50:31 +0000 [warn]: #0 /usr/lib/ruby/gems/2.4.0/gems/fluent-plugin-elasticsearch-2.7.0/lib/fluent/plugin/out_elasticsearch.rb:460:in `rescue in send_bulk'
  2018-02-26 20:50:31 +0000 [warn]: #0 /usr/lib/ruby/gems/2.4.0/gems/fluent-plugin-elasticsearch-2.7.0/lib/fluent/plugin/out_elasticsearch.rb:446:in `send_bulk'
  2018-02-26 20:50:31 +0000 [warn]: #0 /usr/lib/ruby/gems/2.4.0/gems/fluent-plugin-elasticsearch-2.7.0/lib/fluent/plugin/out_elasticsearch.rb:433:in `write'
  2018-02-26 20:50:31 +0000 [warn]: #0 /usr/lib/ruby/gems/2.4.0/gems/fluentd-1.1.0/lib/fluent/plugin/output.rb:1094:in `try_flush'
  2018-02-26 20:50:31 +0000 [warn]: #0 /usr/lib/ruby/gems/2.4.0/gems/fluentd-1.1.0/lib/fluent/plugin/output.rb:1319:in `flush_thread_run'
  2018-02-26 20:50:31 +0000 [warn]: #0 /usr/lib/ruby/gems/2.4.0/gems/fluentd-1.1.0/lib/fluent/plugin/output.rb:439:in `block (2 levels) in start'
  2018-02-26 20:50:31 +0000 [warn]: #0 /usr/lib/ruby/gems/2.4.0/gems/fluentd-1.1.0/lib/fluent/plugin_helper/thread.rb:78:in `block in thread_create'
2018-02-26 20:50:31.145091703 +0000 fluent.info: {"message":"Connection opened to Elasticsearch cluster => {:host=>\"elasticsearch\", :port=>9200, :scheme=>\"http\"}"}
2018-02-26 20:50:31.191919856 +0000 fluent.warn: {"retry_time":0,"next_retry_seconds":"2018-02-26 20:50:32 +0000","chunk":"56623a3aebc14c36300fc2f8ad0ae17c","error":"#<Fluent::Plugin::ElasticsearchOutput::ConnectionFailure: Could not push logs to Elasticsearch after 2 retries. Connection reset by peer (Errno::ECONNRESET)>","message":"failed to flush the buffer. retry_time=0 next_retry_seconds=2018-02-26 20:50:32 +0000 chunk=\"56623a3aebc14c36300fc2f8ad0ae17c\" error_class=Fluent::Plugin::ElasticsearchOutput::ConnectionFailure error=\"Could not push logs to Elasticsearch after 2 retries. Connection reset by peer (Errno::ECONNRESET)\""}

This seesm fluent-plugin-elasticsearch or elasticsearch issue. Closed.


Weight carries over to different yoyos despite the material when switching hands

I was trying out different materials on yoyos to see which one does the most damage but has the most durability and speed when I noticed somethings, speed carries over between yoyos when switching to your off-hand. I had two yoyos, a cobalt one with a manyullyn axle and string cord and a manyullyn one with a manyullyn axle and string cord, so it could be a fair test. I had the manyullyn one in my off-hand and the cobalt one in my main hand. I threw out the cobalt one and switched to the manyullyn one. Surprisingly it moved at the same speed as the cobalt one, which enabled me to absolutely destroy everything. I tried to show it in a photo, but I couldn't ¯_(ツ)_/¯

The damage doesn't carry over, it stays independent of the yoyos


Getting a 'train_version is no longer a used argument on FastlaneCore' message while uploading to TestFlight

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
I'm using Fastlane version 2.125.2.
Running the following command
Command executed
  lane :beta do
    # increment_build_number
    sync_code_signing(type: "appstore")
    build_app(workspace: "myapp.xcworkspace", scheme: "myapp")
    dsym_name = Time.new.strftime('%Y.%m.%d.%H.%M')
    dsym_zip(dsym_path: "./myapp.#{dsym_name}.app.dSYM.zip")
    upload_symbols_to_crashlytics(
      dsym_path: "./myapp.#{dsym_name}.app.dSYM.zip",
      gsp_path: "./myapp/App/GoogleService-Info.plist")
    upload_to_testflight
    slack_success_message
  end

train_version is no longer a used argument on FastlaneCore::BuildWatcher. Please use :app_version instead.
Environment
✅ fastlane environment ✅
Stack

Key
Value

OS
10.14.3

Ruby
2.3.7

Bundler?
false

Git
git version 2.20.1 (Apple Git-117)

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.14.3 (18D109)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib

OpenSSL Version
LibreSSL 2.6.4

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
10.2.1

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

fastlane files:
`./fastlane/Fastfile`
# This file contains the fastlane.tools configuration
# You can find the documentation at https://docs.fastlane.tools
#
# For a list of all available actions, check out
#
#     https://docs.fastlane.tools/actions
# https://github.com/fastlane/examples/blob/master/MindNode/Fastfile
# https://medium.com/ios-development-tips-and-tricks/slack-fastlane-%EF%B8%8F-about-one-of-continuous-integration-puzzles-6ca03576003e
ENV["SLACK_URL"] ||= "https://hooks.slack.com/services/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"
#"https://hooks.slack.com/services/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"
ENV["BUILD_NUMBER"] ||= get_info_plist_value(path: "./way2vat/App/AppMain/way2vat-info.plist", key: "CFBundleVersion") #get_build_number()

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

default_platform(:ios)

platform :ios do

  before_all do
    setup_circle_ci
    update_fastlane
  end

  desc "Create ipa"
  lane :build do
    gym(
        workspace: "way2vat.xcworkspace",
        scheme: "way2vat",
        clean: true,
        output_directory: "./builds",
        output_name: "way2vatIOS"
        )
  end

  desc "Ad-hoc build"
    lane :adhoc do
      match(
            git_url: "https://github.com/WAY2VAT/iOS_Certifications.git",
            type: "adhoc",
            app_identifier: ["com.way2vat.way2vatV2", "com.way2vat.WVUtils", "com.way2vat.way2vatV2.picker"],
            username<EMAIL_ADDRESS>            )
      gym(
            export_method: "ad-hoc",
            workspace: "way2vat.xcworkspace",
            scheme: "way2vat",
            clean: true,
            output_directory: "./builds",
            output_name: "way2vatIOS"
          )
    end

  desc "Push a new beta build to TestFlight"
  lane :beta do
    # increment_build_number
    sync_code_signing(type: "appstore")
    build_app(workspace: "way2vat.xcworkspace", scheme: "way2vat")
    dsym_name = Time.new.strftime('%Y.%m.%d.%H.%M')
    dsym_zip(dsym_path: "./WAY2VAT.#{dsym_name}.app.dSYM.zip")
    upload_symbols_to_crashlytics(
      dsym_path: "./WAY2VAT.#{dsym_name}.app.dSYM.zip",
      gsp_path: "./way2vat/App/AppMain/GoogleService-Info.plist")
    upload_to_testflight
    slack_success_message
  end

  desc "Push a new beta build to TestFlight"
  lane :crashlytics_upload do
    dsym_name = Time.new.strftime('%Y.%m.%d.%H.%M')
    dsym_zip(dsym_path: "./WAY2VAT.#{dsym_name}.app.dSYM.zip")
    upload_symbols_to_crashlytics(
      dsym_path: "./WAY2VAT.#{dsym_name}.app.dSYM.zip",
      gsp_path: "./way2vat/App/AppMain/GoogleService-Info.plist")
    clean_build_artifacts
  end

  desc "Run Unit Tests"
  lane :tests do
    # run_tests(scheme: "way2vat")
    scan(
      workspace: "way2vat.xcworkspace",
      devices: ["iPhone 6s"]
    )
  end

  desc "Refresh DSYM"
  lane :refresh_dsyms do
    download_dsyms # Download dSYM files from iTC
    upload_symbols_to_crashlytics(gsp_path: "../way2vat/App/AppMain/GoogleService-Info.plist") # Upload them to Crashlytics
    clean_build_artifacts # Delete the local dSYM files
  end

  desc "Slack success message"
  lane :slack_success_message do
    slack(
      message: "App successfully uploaded to iTunesConnect.",
      success: true,
      slack_url: ENV["SLACK_URL"],
      payload: {
        "Build Date" => Time.new.to_s,
        "Built by" => "Fastlane",
      },
      default_payloads: [:git_branch, :git_author, :last_git_commit_message],
      attachment_properties: {
        fields: [
           {
               title: "Build number",
               value: ENV["BUILD_NUMBER"],
           }
        ]
      }
    )
  end

  def on_error(exception)
       slack(
           message: "Something went wrong!",
           success: false,
           slack_url: ENV["SLACK_URL"],
           attachment_properties: {
               fields: [
                   {
                       title: "Error message",
                       value: exception.to_s
                   }
               ]
           }
       )
  end

  error do |lane, exception|
    if ENV["SLACK_URL"]
      slack(
           message: "Something went wrong!",
           success: false,
           slack_url: ENV["SLACK_URL"],
           attachment_properties: {
               fields: [
                   {
                       title: "Error message",
                       value: exception.to_s
                   }
               ]
           }
       )
    end
  end
  desc "Run match"
  lane :certificates do
    match(app_identifier: ["com.way2vat.way2vatV2", "com.way2vat.way2vatV2.picker"],
    type: "development")
    match(app_identifier: ["com.way2vat.way2vatV2", "com.way2vat.way2vatV2.picker"],
    type: "adhoc")
    match(app_identifier: ["com.way2vat.way2vatV2", "com.way2vat.way2vatV2.picker"],
    type: "appstore")
  end
end

`./fastlane/Appfile`
app_identifier("com.way2vat.way2vatV2") # The bundle identifier of your app
<EMAIL_ADDRESS># Your Apple email address

itc_team_id "118503468" # iTunes Connect Team ID
team_id "37DSD9P5SF" # Developer Portal Team ID

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

fastlane gems

Gem
Version
Update-Status

fastlane
2.125.2
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.0

slack-notifier
2.3.2

atomos
0.1.3

CFPropertyList
3.0.0

claide
1.0.2

colored2
3.1.2

nanaimo
0.2.6

xcodeproj
1.8.1

rouge
2.0.7

xcpretty
0.3.0

terminal-notifier
2.0.0

unicode-display_width
1.3.2

terminal-table
1.8.0

plist
3.4.0

public_suffix
2.0.5

addressable
2.5.2

multipart-post
2.0.0

word_wrap
1.0.0

tty-screen
0.6.4

tty-cursor
0.5.0

tty-spinner
0.8.0

babosa
1.0.2

colored
1.2

highline
1.7.10

commander-fastlane
4.4.6

excon
0.62.0

faraday
0.15.0

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20180417

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

fastimage
2.1.1

gh_inspector
1.1.3

json
<IP_ADDRESS>

mini_magick
4.5.1

multi_xml
0.6.0

rubyzip
1.2.2

security
0.1.3

xcpretty-travis-formatter
1.0.0

dotenv
2.4.0

bundler
1.16.1

faraday_middleware
0.12.2

naturally
2.1.0

simctl
1.6.4

jwt
2.1.0

google-cloud-env
1.0.5

google-cloud-core
1.3.0

uber
0.1.0

declarative
0.0.10

declarative-option
0.1.0

representable
3.0.4

retriable
3.1.1

mime-types-data
3.2016.0521

mime-types
3.1

multi_json
1.13.1

signet
0.11.0

little-plugger
1.1.4

logging
2.2.2

memoist
0.16.0

os
0.9.6

googleauth
0.6.2

httpclient
2.8.3

google-api-client
0.23.9

digest-crc
0.4.1

google-cloud-storage
1.16.0

emoji_regex
0.1.1

io-console
0.4.5

libxml-ruby
2.9.0

psych
<IP_ADDRESS>

generated on: 2019-06-13

I have successfully uploaded the build to TestFlight but at the end, I have got the above message from Fastlane

It's not a code signing issue. Just like @naorcho my build is signing & uploading just fine. It's just weird to see a warning afterwards.

It is definitely not code sign in issue. As you can see in the screenshot the build was successfully uploaded to TestFlight. I agree with @downie

I have the very same message (i.e. "train_version is no longer a used argument on FastlaneCore::BuildWatcher. Please use :app_version instead.") - and code-signing works fine. Must be some other issue.

It's seems that is a warning of BuildWatcher file:
https://github.com/fastlane/fastlane/blob/master/fastlane_core/spec/build_watcher_spec.rb
In this file they are using train_version prop in many methods, so I guess they (fastlane programmers) have to replace it for app_version. I'm just supposing.
I'm using Fastlane 2.125.2 too and Beta and Release app versions are been submitted successfully.

I updated plugins with fastlane update_plugins and fastlane with fastlane update_fastlane and this was fixed :D

Updating to the latest version did solve the problem!

Unfortunately, this is still happening for me with fast lane 2.172.1.
Would it be better to re-open this issue or create a new one?
✅ fastlane environment ✅
Stack

Key
Value

OS
10.14.3

Ruby
2.3.7

Bundler?
true

Git
git version 2.21.0

Installation Source
/usr/local/bin/fastlane

Host
Mac OS X 10.14.3 (18D109)

Ruby Lib Dir
/System/Library/Frameworks/Ruby.framework/Versions/2.3/usr/lib

OpenSSL Version
LibreSSL 2.6.4

Is contained
false

Is homebrew
false

Is installed via Fabric.app
false

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

Xcode Version
10.2

System Locale

Variable
Value

LANG
en_US.UTF-8
✅

LC_ALL
en_US.UTF-8
✅

LANGUAGE

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

#######################################################################

opt_out_usage
skip_docs
fastlane_version "2.127.1"

# if ENV["CIRCLECI"] == "true"
#  print "\n***** skipping xcversion check because CircleCI apparently doesn't like it.\n"
# else
#  xcversion(version: "9.3")
# end

default_platform :ios

#######################################################################
# Project-Specific Variables
#######################################################################

# PATHS
PROJECT_PATH                    = "App.xcodeproj"
INFO_PLIST_PATH                 = "App/Resources/Info.plist"

# CONSTANTS
TARGET_NAME                     = "App"

# CONFIGURATIONS
CONFIG_NAME_STORE               = "Release"

# SCHEMES
SCHEME_NAME_STORE               = "App Release"

# Bundle IDs
BUNDLE_ID_DEV                   = "net.chrisdownie.beta.app.dev"
BUNDLE_ID_BETA                  = "net.chrisdownie.beta.app.beta"
BUNDLE_ID_STORE                 = "net.chrisdownie.beta.app"

# Bundle Names
BUNDLE_NAME_DEV                 = "App Dev"
BUNDLE_NAME_BETA_PROD           = "App β"
BUNDLE_NAME_STORE               = "App"

# TAGGING
TAG_NAME                        = "App"
TAG_BUILD_STYLE_DEV             = "Dev"
TAG_BUILD_STYLE_BETA            = "Beta"
TAG_BUILD_STYLE_STORE           = "Store"
TAG_BUILD_ENVIRONMENT_DEV       = "Dev"
TAG_BUILD_ENVIRONMENT_PROD      = "Prod"

platform :ios do

  #######################################################################
  # Lifecycle Hooks
  #######################################################################

  before_all do |lane|
    setup_circle_ci
    #ENV["SLACK_URL"] = "https://hooks.slack.com/services/REPLACEME"
    #ensure_git_status_clean
    clear_derived_data
  end

  after_all do |lane|

  end

  # error do |lane, exception|
  #   slack(
  #     use_webhook_configured_username_and_icon: true,
  #     success: false,
  #     message: "Fastlane error: #{exception.to_s}",
  #     payload: {
  #         'Build Date' => Time.new.to_s,
  #         'Built by' => 'Fastlane',
  #         'Output' => exception.to_s
  #       },
  #     default_payloads: [:git_branch, :git_author]
  #   )
  # end

  #######################################################################
  # Carthage
  #######################################################################

  desc "Updates all carthage dependencies and (re)generates our 3rd party license file"
  lane :carthage_update do
    carthage(command: "update",
	  use_submodules: false,
	  platform: "iOS"
    )
    sh "cd ../scripts && ./generate_legal.swift"
  end

  desc "Builds all carthage dependencies and (re)generates our 3rd party license file"
  lane :carthage_build do
    carthage(command: "build",
	  platform: "iOS"
    )
    sh "cd ../scripts && ./generate_legal.swift"
  end

  #######################################################################
  # Test Lanes
  #######################################################################

  desc "Runs unit tests"
  lane :run_unit_tests do
    # We'd like to do this, but Fastlane isn't working well with Xcode 9 simulators (yet)…
    # reset_simulators

    scan(
      project: PROJECT_PATH,
      device: "iPhone X",
      scheme: "All Unit Tests",
      clean: true,
      skip_build: true,
      configuration: "Debug-Development",
      slack_only_on_failure: true,
      xcargs: "COMPILER_INDEX_STORE_ENABLE=NO"
    )
  end

  desc "Runs unit tests and SwiftLint on CircleCI"
  lane :run_unit_tests_and_lint_via_circleci do
    run_unit_tests

    # Hsoi 2018-04-11 -  While targets do have Run Script build phases and SwiftLint does run,
    # I've seen times on CI where it claims to run and I know there are violations, yet nothing prints.
    # Since we really want this because we believe it's important to our CI process, we'll manually invoke
    # SwiftLint. Yes maybe it means things run twice, but then so be it.
    swiftlint(
      mode: :lint,
      reporter: "html",
      output_file: "swiftlint.result.html",
      config_file: ".swiftlint.yml",
      strict: true,
      ignore_exit_status: false,
      quiet: false
    )
  end

  desc "Run the static analyzer"
  lane :analyze do
    # Downie 2019-05-20 - The static analyzer is a great tool to find bugs, but it's expensive to
    # run. Perfect for CI! Unfortunately, it's not easy to determine in CI what static analyzer
    # errors xcodebuild found during execution. However, we can detect that errors _were_ found.
    # If errors are found, run the analyzer on Xcode on your machine, and Xcode's graphical
    # reporter will point out what error sit caught.

    # 1. Build the Debug-Development scheme.
    output_file = "/tmp/circleci-artifacts/clang"
    target_scheme = "#{TARGET_NAME}-Debug-Development"
    xcodebuild(
      analyze: true,
      destination: "generic/platform=iOS",
      scheme: target_scheme,
      xcargs: "\
        CODE_SIGN_IDENTITY='' \
        CODE_SIGNING_REQUIRED=NO \
        CODE_SIGNING_ALLOWED=NO \
        CLANG_ANALYZER_OUTPUT=plist-html \
        CLANG_ANALYZER_OUTPUT_DIR=" + output_file
    )

    # 2. Run a shell command to see if the output_file is created.
    sh "find", output_file, "-name", "*.html" do |status, result, command|
      unless status.success?
        UI.error "Command #{command} (pid #{status.pid}) failed with status #{status.exitstatus}"
      end

      # 3. If it's created, then xcodebuild found errors. Analyze in Xcode to see why.
      if result.empty?
        UI.message "Static analyzer didn't find any issues."
      else
        UI.error "Analyzer found issues."
        UI.user_error!("The static analyzer found issues. Look in #{output_file} to see what they are.")
      end
    end
  end

  #######################################################################
  # Side Effect Lanes
  #######################################################################

  desc "Bump and tag version"
  lane :bump do
    ensure_git_status_clean

    bump_message = "Bump build number."
    last_message = last_git_commit[:message]

    # If our latest commit isn't a build bump, then bump the build.
    unless last_message.include? bump_message
      increment_build_number
      commit_version_bump(
        message: bump_message,
        xcodeproj: PROJECT_PATH
      )
      add_git_tag
      push_to_git_remote
    end
  end

  desc "Submit latest versioned build to testflight"
  lane :submit_to_testflight do |options|
    # 1. Do some math to get build tags
    build_number = get_build_number(xcodeproj: PROJECT_PATH)
    last_build_number = build_number.to_i - 1
    build_tag = "builds/iosbump/" + build_number
    last_build_tag = "builds/iosbump/" + last_build_number.to_s

    # 2. Generate a change log
    comments = changelog_from_git_commits(
        between: [last_build_tag, build_tag],
        pretty: "- %s",
        date_format: "short",
        match_lightweight_tag: false,
        merge_commit_filtering: "exclude_merges"
    )

    # 3. Build the app without simulator architectures
    ENV["SHOULD_REMOVE_SIMULATOR_ARCHITECTURES"] = "true"
    match(type: "appstore", readonly: true, skip_docs: true)
    configuration = options[:configuration] || "Release"
    environment = options[:environment] || "Production"
    target_scheme = "#{TARGET_NAME}-#{configuration}-#{environment}"
    build_app(
      scheme: target_scheme,
      xcargs: "COMPILER_INDEX_STORE_ENABLE=NO"
    )

    # 4. Upload it to testflight
    groups = options[:groups] || "All Builds"
    upload_to_testflight(
      changelog: comments,
      distribute_external: true,
      groups: groups
    )
  end
end

`./fastlane/Appfile`
app_identifier ENV["net.chrisdownie.beta.app"]  # set in the Fastfile, as a lane executes since we have different identifiers per build.

apple_id<EMAIL_ADDRESS># Your Apple email address

team_id "98Q2NDWZ5B" # Developer Portal Team ID

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

fastlane gems

Gem
Version
Update-Status

fastlane
2.127.1
✅ Up-To-Date

Loaded fastlane plugins:
No plugins Loaded
Loaded gems

Gem
Version

did_you_mean
1.0.0

bundler
2.0.1

io-console
0.4.5

CFPropertyList
3.0.0

public_suffix
2.0.5

addressable
2.6.0

atomos
0.1.3

babosa
1.0.2

claide
1.0.2

colored
1.2

colored2
3.1.2

highline
1.7.10

commander-fastlane
4.4.6

declarative
0.0.10

declarative-option
0.1.0

digest-crc
0.4.1

unf_ext
<IP_ADDRESS>

unf
0.1.4

domain_name
0.5.20190701

dotenv
2.7.4

emoji_regex
1.0.1

excon
0.64.0

multipart-post
2.0.0

faraday
0.15.4

http-cookie
1.0.3

faraday-cookie_jar
0.0.6

faraday_middleware
0.13.1

fastimage
2.1.5

gh_inspector
1.1.3

jwt
2.1.0

memoist
0.16.0

multi_json
1.13.1

os
1.0.1

signet
0.11.0

googleauth
0.6.7

httpclient
2.8.3

mime-types-data
3.2019.0331

mime-types
3.2.2

uber
0.1.0

representable
3.0.4

retriable
3.1.2

google-api-client
0.23.9

google-cloud-env
1.2.0

google-cloud-core
1.3.0

google-cloud-storage
1.16.0

json
2.2.0

mini_magick
4.5.1

multi_xml
0.6.0

plist
3.5.0

rubyzip
1.2.3

security
0.1.3

naturally
2.2.0

simctl
1.6.5

slack-notifier
2.3.2

terminal-notifier
2.0.0

unicode-display_width
1.6.0

terminal-table
1.8.0

tty-screen
0.7.0

tty-cursor
0.7.0

tty-spinner
0.9.1

word_wrap
1.0.0

nanaimo
0.2.6

xcodeproj
1.11.0

rouge
2.0.7

xcpretty
0.3.0

xcpretty-travis-formatter
1.0.0

generated on: 2019-07-18


[Barz] Allow deriving multiple addresses from a single public key

Salt is passed to functions as a parameter now instead of being hardcoded to 0

@rsrbk please fix Android tests

ios test is not passing @rsrbk


29178D

https://www.facebook.com/100065932031832/posts/270946288446437/http://<IP_ADDRESS>.8099/https://forum.developer.samsung.com/t/samsung-internet-android-auto-fill-api/9532

This is spam.


Add Excluded Taxa to Index Calc

Need on-screen check box for Excluded Taxa routine prior to calculation of MMI.

Added but commented out the code that launches the function BioMonTools::markExcluded().

Added BioMonTools::markExcluded() function to correct location and tested. Functions properly.


Use the configured session timeout and set it as the expire time for the redis key

No version of the plugin currently sets the expire time for the session keys in Redis. This can cause the session store to fill up over time, unless the keys are cleaned up through some other process.
This fix sets the timeout to the value as specified in tomcat and the web.xml.
This addresses the issue reported here:
https://github.com/pivotalsoftware/session-managers/issues/9

I've made some tests and the tomcat containers cleans up the session at the configured timeout.
However it might be a good idea to also setup a timeout (maybe longer than the tomcat) in case of a disaster.
What do you think?

OK, this test is done using one (or more) instances that share sessions? I'm wondering whether our problem could be related to the special case where sessions might linger in case we replace the existing nodes with new ones? If the sessions aren't active in the new instance, they most probably never get cleaned out either.
Using the Redis TTL/expire as a safety measure sounds like a legit solution to the problem. In this case there should, however, be some configuration for the safety margin. We flush the sessions after every request to Redis, so for us the margin doesn't need to be big, but a more general case would probably warrant one.

I haven't test with multiple instances, just one.
I agree with you, this could be a safe mode for, as I said, a disaster situation where your nodes are down.

By the way, the only limitation for this solution is the sessions set. Its contents will never expire so either we live with this caveat or we design a particular solution (if possible).

Is it strictly necessary to keep the list of available keys in a separate entry in Redis? Is it required to be transactionally correct for existing sessions?
I'm not familiar enough with the internals of Tomcat to know how often this value is accessed, and is it always queries before accessing the actual stored session-object. At least in RedisStore the value is not read at session load.
Would it be sufficient to do a scan at start, and keep a local cache of it in memory, and potentially having another thread occasionally update the cache through additional scan-requests?
Given the way the sessions seem to build up over time, I'm a bit worried what happens in the long run with the sessions-key, when we have a multitude of nodes talking to the same cache.
I'm happy to add this implementation in a separate pull request, but only if it is deemed a good enough solution, and not leading to severe performance problems.

Scan might not be a good choice due to future cluster support (I'm working on it right now).
Also scan usually perform interruption at the redis server creating a potential performance bottleneck.
Maybe we could think of a solution that wouldn't demand the entire key set, to be honest I havn't thought about it much yet.

Thank you for the contribution.  Merged.


Fully automate dev setup with Gitpod

This commit implements a fully-automated development setup using Gitpod.io, an
online IDE for GitHub and GitLab that enables Dev-Environments-As-Code.
This makes it easy for anyone to get a ready-to-code workspace for any branch,
issue or pull request almost instantly with a single click.

Sorry.  I was trying to do this on my fork.  Ignore.  Sorry for hitting your tests.


emit a loaded event in mergeData

Emit an event after mergeData is finished (as used by redis-brain) so we don't have to do hacky workarounds in scripts (see remind.coffee for an example).

Think we should emit the data too?

emits the data now as well (:


trim issues after upgrade from v0.8.2 to v0.9.0

What version of CUE are you using (cue version)?

$ cue version
cue version v0.9.0

go version go1.22.4
      -buildmode exe
       -compiler gc
       -trimpath true
     CGO_ENABLED 0
          GOARCH arm64
            GOOS darwin
cue.lang.version v0.9.0

Does this issue reproduce with the latest stable release?
Yes - is new with v0.9.0 - not present in v0.8.2
What did you do?
$ cue trim ./elevation/...
imported and not used: "strings":
    ./elevation/apps/config/satebatcher.cue:4:2

But I am....
$ ack -A 1 -B 1 "strings\." --  ./elevation/apps/config/satebatcher.cue
                        for zone in #edgeAppZones {
                                let suffix = strings.SliceRunes(zone.name, strings.LastIndex(zone.name, "-")+2, len(zone.name))
                                #satebatcherComponent & {

So I added _what: strings.Split("what-the", "-")[0] to the file ...  and re-ran the trim
$ cue trim ./elevation/...
< LARGE DIFF with a bunch of stuff removed >
Aborting trim, output differs after trimming. This is a bug! Use -i to force trim.
You can file a bug here: https://cuelang.org/issues/new?assignees=&labels=NeedsInvestigation&template=bug_report.md&title=
make: *** [cue/trim] Error 1

Most, but not all of the - in the diff are for comprehensions....
I am going to see if I can create a minimal re-producer, but don't have one yet.

What did you expect to see?
No change really ... this is an upgrade to v0.9.0 from a project that was using v0.8.2
What did you see instead?
See above.

I've tried to put together a re-producer, but I haven't been able to and I don't think it's a good idea to publicly make available the private cue bits.

Oddly enough I changed our cue fmt makefile target to run and it runs fine (the mindepth there is due to the layout of the repo and how we use cue export)
find ./elevation -type d -mindepth 6 | xargs -n 1 -I % sh -c "echo cue trim -s --strict %; cue trim -s --strict %"

@freeformz if you're unable to reduce the reproducer to be shared publicly, can you send it to me privately, for example via Slack? I can then do the reduction work so that we can have a small reproducer to investigate and add as a regression test.
Without a reproducer it might be hard for us to investigate this bug properly, as you can imagine.

@mvdan Thx. Sent via slack.

Apologies for the slowness, @freeformz, I've been on holiday recently.
@cuematthew and I have reduced the "unused import" error to this testscript:
exec cue trim input.cue

-- input.cue --
package apps

import "strings"

#values: {
	list: _
}
#values & {
	list: [
		for never in []
		let trimmed = strings.TrimSpace(never)
		{ trimmed }
	]
}

Rather than succeeding as expected, by for example trimming the file or doing nothing at all, we get a confusing error like yours:
> exec cue trim input.cue
[stderr]
imported and not used: "strings":
    ./input.cue:3:8
[exit status 1]
FAIL: test.txtar:1: unexpected command failure

It's worth pointing out that CUE v0.8.2 failed in your code when running cue trim with a single package, but when running on all packages, it seemingly hid the error - which doesn't look right:
$ cue-v0.8.2 trim ./elevation/apps/config
imported and not used: "strings":
    ./elevation/apps/config/satebatcher.cue:4:2
$ cue-v0.8.2 trim ./...
$ echo $?
0

Something changed between 0.8 and 0.9 where CUE now consistently shows the error, rather than inconsistently hiding it:
$ cue-v0.9.0 trim ./elevation/apps/config
imported and not used: "strings":
    ./elevation/apps/config/satebatcher.cue:4:2
$ cue-v0.9.0 trim ./...
imported and not used: "strings":
    ./elevation/apps/config/satebatcher.cue:4:2

So it seems to us like the underlying "imported and not used" bug in trim already existed in v0.8, it was just being hidden from you when you ran cue trim ./.... That bug still seems like a problem and we will look into it - but now we have a much smaller reproducer, and it's interesting to see that it existed for a while.

We found the cause :) In your config, you had a list comprehension that always resulted in zero elements (./elevation/apps/config._satebatcherValues.app.components, which also has conflicting list types between [...string] and [...{}]?), so cue trim was trying to delete the entire comprehension and leave an empty list. This comprehension is where strings.SliceRunes was used, so when the only use of the strings import was removed, we should remove the import as well.
cue trim uses https://pkg.go.dev/cuelang.org/go/cue/ast/astutil#Sanitize to remove such unused imports, but it didn't do that correctly, hence the error. I'll send a fix shortly for the astutil package.
It's worth noting that, after the fix, cue trim ./elevation/apps/config still results in an error, due to cue trim having other bugs:
Aborting trim, output differs after trimming. This is a bug! Use -i to force trim.
You can file a bug here: https://cuelang.org/issues/new?assignees=&labels=NeedsInvestigation&template=bug_report.md&title=

But you can use cue trim -i ./elevation/apps/config to skip past that sanity check error and trim the files on disk, which does result in the expected changes I explain above. We are aware of the "output differs after trimming" bugs, and @cuematthew is looking at a new trim algorithm to resolve those.
So, in short - CUE v0.8.2's cue trim ./... seemed to be a no-op. Not only did it fail to trim due to a bug, it didn't even show you any error message at all. CUE v0.9.0 and master fail due to the astutil bug above, which we will fix - and then trimming will make changes with the -i flag.
From a quick look, the changes that cue trim -i ./... does make after the astutil fix don't look right. However, as I showed above with the existing breadth of trim issues, that's not entirely surprising. We will leave this issue open after the astutil fix, so that we can try trimming your project with the new algorithm once it is ready.

@mvdan TY for the explanation and detailed break down!

@mvdan I'm not sure how ./elevation/apps/config._satebatcherValues.app.components could have conflicting types of [...string] and [...{}] - any thoughts on debugging that ?

AFAICT I'm essentially doing this: https://cuelang.org/docs/tour/expressions/fieldcomp/
_satebatcherValues: xyz.#values & {
	app: {
		name: _meta.name
		components: [
			for zone in _something
			let suffix = strings.SliceRunes(zone.name, strings.LastIndex(zone.name, "-")+2, len(zone.name)) {
				_satebatcherComponent & {
                                     ...
				}
			},
		]
	}
}

The astutil.Sanitize fix is now at https://review.gerrithub.io/c/cue-lang/cue/+/1198351.
Please ignore my mention of a list type mismatch - we spent a while aggressively reducing your code to reach the dozen lines of CUE I shared yesterday, and at some point during that process we made the list comprehension produce a list of strings rather than a list of structs. Your original code doesn't have this issue, as you correctly point out. The reproducer I shared ended up not having this issue either in the end, as we swapped list: [...{}] for list: _ and the bug still reproduced.


Inconsistent table sizes on some move dialogues

e.g.

vs

Check the others and obsolete dialogue as well.

This is due to the error message @joelvdavies. This is so that an error message doesn't trigger the use of a vertical scroll bar in the dialog

also the table size is different due the "add button" which is expected

@joshuadkitenge But they both have error messages, and both have fixed sizes only they don't match anymore.


No command wrappers in node lib

In powershell library we have plenty of the wrapper that do make code cleaner and easier to use, like Write-VstsUploadFile
https://github.com/Microsoft/azure-pipelines-task-lib/blob/master/powershell/Docs/Commands.md#write-vstsuploadfile
In Node lib this is missing and it would make the code I'm writing way cleaner.
I was wondering, would a PR with some of the commands be welcome?

Sure, that sounds like a good improvement!

Fixed by #477


No IP addresses

For some reason my preview deployments have no IPs assigned by default.

Related issue maybe: https://community.fly.io/t/the-deployed-app-has-no-ip-assigned/4671

Was use error, see thread linked above.


Looks cool, no idea to find out what it is

A little extra in the README along with some functionality provided would be nice to get an idea :)

The title is brilliant XD Thank you so much!
It's true 😅
This project isn't finished, but for sure there may be some examples of what we has right now.


Sync editor on theme change

https://github.com/user-attachments/assets/d24c193a-874e-4d65-8d63-5adf7e30e738
Shall close #480

A full resize event would trigger a complete reflow of the page. Maybe just doing it on the view would be more economical.
Also, is the resize the only thing that triggers a redraw of the view?

Also, is the resize the only thing that triggers a redraw of the view?

That sounds good, thanks @SylvainCorlay.
I at the moment can't think of any other way but I'm happy to discuss and iterate over it.

Just calling update() on the Lumino panel of the 3-D view should do it. People more familiar with Lumino on the team will know the proper way to do.

you can use MessageLoop.sendMessage to send the Widget.ResizeMessage message to the 3D view widget.
https://github.com/jupytercad/JupyterCAD/blob/7e6b49b8be3948b9b0dd24aa2db6fc4414ea7f0c/packages/base/src/panelview/formbuilder.tsx#L37

you can use MessageLoop.sendMessage to send the Widget.ResizeMessage message to the 3D view widget.
https://github.com/jupytercad/JupyterCAD/blob/7e6b49b8be3948b9b0dd24aa2db6fc4414ea7f0c/packages/base/src/panelview/formbuilder.tsx#L37

@trungleduc When i try MessageLoop.sendMessage in model.ts it says
Property 'sendMessage' does not exist on type
'typeof import("/Users/arjunverma/Desktop/Arjun/JupyterCAD/node_modules/@lumino/messaging/types/index")'

but the same works in formbuilder.tsx

My 2 cents, we used to depend on the lightTheme attribute in the React component state to change the background color according to it: https://github.com/jupytercad/JupyterCAD/blob/main/packages/base/src/3dview/mainview.tsx#L1444
This seems to not be used anymore! So we should probably remove lightTheme from the state, but we should probably modify this _handleThemeChange method there to force a this.update() of the react component to trigger a re-render, instead of setting that old unused state attribute.


Generate AppImage

Replaces #2027 as it had merge conflicts due to macOS -> OS X rename. Rebased to fix failing Pester test run.
@probonopd and @TravisEz13 please review that I fixed conflicts correctly.
Push build is here.

Hi @andschwa, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Andy Schwartzmeyer). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Push build succeeded. Pester tests ran and AppImage was created successfully.

Thanks, looks good to me.

@TravisEz13 can you try out the AppImage?

@andschwa I see the images generated here, but you don't have artifacts enabled so I cannot download them.  https://travis-ci.org/andschwa/PowerShell/builds/155445453

@TravisEz13 ah, of course. Here's an upstream build which should upload the artifacts when its complete.

Upload succeeded, download_url: https://s3.amazonaws.com/powershell-artifacts/PowerShell/PowerShell/258/258.1/powershell-6.0.0-alpha.9-x86_64.AppImage
Will test now.

Tested on Ubuntu 16.04, runs.

LGTM. @TravisEz13?

@probonopd I have a hold that came internally, we can't merge this yet.
@KrisBash can you please explain?

@KrisBash nevermind, I spoke with @probonopd.

Hm, I can't assign @KrisBash to the issue.
@lzybkr should we add him as a collaborator?

I am using powershell AppImage on linux , available at https://bintray.com/probono/AppImages/PowerShell .  It helps in single portable binary executable file getting executed on various linux distributions.
I will humbly request and very strongly recommend that each powershell release by the powershell development team, should also officially happen in AppImage format , and should be available at https://github.com/PowerShell/PowerShell/releases

Hello, and thank you for your input @zaxebo1. I am following up internally on why this is still blocked; we should have a better answer here soon. Thanks again :smile:

Working on getting resolution on this, won't happen til next week earliest

Thanks for following up @SteveL-MSFT 😄

@andschwa this has been approved, but we must include some attribution, I'll send them to you via email to include in the image

the above are trivial conflicts - that is, conflicts only in markdown files and a shell script, which can be quickly resolved. Request you to kindly take up  on early/priority - to resolve these conflicting files

@zaxebo1 I think I don't have the permissions, only @andschwa can do this since he opened this PR based on a previous one from me.

@probonopd is right, since I can fix this up next week.

@andschwa ping

@vors is there a !remindme bot for GitHub? If not, there should be. Adding this to my task list...

I will play its role for now :)

@vors this is ready now as far as I know.

Steve can you send the attributions requirements again?

[x] Rebased and merge conflicts resolved
[x] Pinned external code download to specific commit hash
[x] Included additional third party licenses from legal
[x] Successful build of AppImage binary
[ ] Anything else?

@PowerShell/powershell-maintainers you'll want to include the AppImage binary in the next release on GitHub, and fix the link in the readme.

@SteveL-MSFT handing over to you for final review and merge 😄

Anything else?

@andschwa just another rebase ;)

@joeyaiello your turn!

Never ending story ;-) @andschwa

Thanks for merging. Minor cosmetic glitch, in README.md it now says [.AppImage][rl-ai] which doesn't look right.

@raghushantha do you need to update your publishing pipeline to generate the appimage?  once we have an official appimage, can you update the link to point to it?

Woo hoo!

Let's celebrate @andschwa :1st_place_medal:

@SteveL-MSFT I have integrated AppImage generation as part of the Release pipeline.
Got a couple of concerns which I will followup offline


Pin.close() questions

According to the documentation for Pin.close()

After this method is called, this Pin instance may no longer be used to query or control the pin’s state.

But observe:
>>> from gpiozero.pins.rpigpio import RPiGPIOPin
>>> pin = RPiGPIOPin(21)
>>> pin.function
u'input'
>>> pin.state
0
>>> pin.function = 'output'
>>> pin.state = 1
>>> pin.close()
>>> pin.state
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "gpiozero/pins/__init__.py", line 130, in <lambda>
    lambda self: self._get_state(),
  File "gpiozero/pins/rpigpio.py", line 133, in _get_state
    return GPIO.input(self._number)
RuntimeError: You must setup() the GPIO channel first
>>> pin.function
u'input'
>>> pin.function = 'output'
>>> pin.state
1

i.e. merely setting the RPiGPIOPin's function property is enough to automatically 're-open' the pin!
Should the Pin implementations have a closed property, like GPIODevice, with a corresponding PinClosed exception for any operations performed on a closed pin? Or is the "this Pin instance may no longer be used" statement in the documentation merely "advisory"? (or is the documentation simply wrong?)
Hmmm, I see that GPIODevice.close() calls pin.close(), which means we get this behaviour:
>>> from gpiozero.pins.rpigpio import RPiGPIOPin
>>> from gpiozero import GPIODevice
>>> pin = RPiGPIOPin(21)
>>> device = GPIODevice(pin)
>>> device.value
False
>>> device.close()
>>> device.closed
True
>>> device2 = GPIODevice(pin)
>>> device2.value
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  File "gpiozero/devices.py", line 323, in value
    return self._read()
  File "gpiozero/devices.py", line 245, in _read
    return self.pin.state == self._active_state
  File "gpiozero/pins/__init__.py", line 130, in <lambda>
    lambda self: self._get_state(),
  File "gpiozero/pins/rpigpio.py", line 133, in _get_state
    return GPIO.input(self._number)
RuntimeError: You must setup() the GPIO channel first

TBH I've got no idea what the expected/intended behaviour is :-/
Perhaps I'm just mucking around at too low a level, and at the "LEDs and Buttons" level that gpiozero is typically used at, everything magically comes out in the wash? ;-)

I guess this is a minor bug. No one will really care that they can mess around with a closed device and later be able to read its state, but it should probably be addressed somehow (i.e. stop the ability to set the pin function when closed).
Also would it be possible to stop RPi.GPIO RuntimeErrors coming through?

Sorry I'm not around much at the mo (picamera 1.11 dragging on!). Briefly:

Pins can't really be closed (from this perspective the docs are simply wrong). This is because Pin(2) is Pin(2) is True; i.e. separately constructed Pin objects are actually the same instance provided they refer to the same physical pin. This is in order to ensure we maintain knowledge about things we can't query from the hardware like pull-up status.

Pin.close() is basically akin to RPi.GPIO's cleanup() - it just resets the pin to its "default" state, i.e. input (although actually this isn't entirely "default" for some GPIOs which should theoretically default to one of the alt-function states). Frankly, close() should probably be renamed something better like "reset".

The error you're getting on re-construction of GPIODevice against the same pin I'd consider an RPi.GPIO bug. The pin's actually in input state (at the hardware level) but because you've called cleanup() on it RPi.GPIO think it's in "unknown" state (despite the fact its own gpio_function() function will tell you it's in input mode...). More specifically it's because gpio_direction for that pin is -1 after cleanup (it's another good example of having "multiple versions of the truth" - there's what the hardware actually is, and RPi.GPIO's idea of the hardware which is out of sync with reality).


Chore: Fix dependabot

Description
I don't know how, but it doesn't seem to pick up dependencies anymore with [workspace.dependencies].

Seems to actually be issue getting deltars

Fixed


Update error message checks for new collections.

This was causing issues with the S3 tests, possibly others.
Also fix an error message copy/paste error and fix the branch key check
to work as intended.

I didn't go through and check if we could just check for the structured error that the collection returns, but that's probably a better fix

LGTM - I think we'll revisit the keycheck later, but this is great for now.


enhancement support single replica compaction

Support single replica compaction, once a replica want to do compaction, it should ask peer replica if it is necessary to do
it or it can fetch result from peer result. More details is in issue #10300
Proposed changes
Issue Number: close #10300
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

Why is it not merged into master? Is this enhancement obsolete?


vocabulary: Converst relation_type to vocabulary

closes https://github.com/inveniosoftware/invenio-app-rdm/issues/695

We need to align on "should demo records get custom vocabularies from users?" cuz I do agree with hardcoding but if users expect demo records to have their own, we might have an issue there...


Using Redis on shared server with multiple Laravel application

Laravel Version: 5.5
PHP Version: 7.1
Database Driver & Version: Mysql

We have hosted two Laravel application on one server. Installed Redis & Supervisor.
In supervisor configuration (/etc/supervisord.conf) added two configuration
Application 1 configuration
[program:app1-supervisor]
process_name=%(program_name)s_%(process_num)02d
command=php //path/to/application/1/artisan queue:work redis --sleep=3 --tries=3 --daemon
autostart=true
autorestart=true
user=ladybirq
numprocs=8
redirect_stderr=true
stdout_logfile=/path/to/application/1/worker.log

Application 2 configuration
[program:app2-supervisor]
process_name=%(program_name)s_%(process_num)02d
command=php //path/to/application/2/artisan queue:work redis --sleep=3 --tries=3 --daemon
autostart=true
autorestart=true
user=ladybirq
numprocs=8
redirect_stderr=true
stdout_logfile=/path/to/application/2/worker.log

When application 1 sends email, It sends from application 2 mail configuration.
Email configuration is stored in database and on fly application set in the configuration
Example
$email = Email::first();
config(“mail.driver.$email->driver”);

So some values in the application 1 email get replaced with application 2 values.
Not sure where I am going wrong.
Have anyone configured Redis on the single server with multiple applications. Both our application are same.
We are using cPanel on this server and both the application are hosted in different cPanel account on the same server

Try setting a different value for this setting
https://github.com/laravel/laravel/blob/master/config/queue.php#L63

Hi there,
Welcome to Laravel and we are glad to have you as part of the community.
Unfortunately this github area is not a support area for general application issues. This is only for issues/bugs with the framework code itself. In this case - the problem is you are using the same queue tube name for both applications.
Can I please suggestion closing your issue ticket here. Instead trying asking your question on one of the many great community support areas that will likely give you a better answer more quickly:

Laravel Slack (https://larachat.co/)
Laravel.io Forum (https://laravel.io/forum)
Laracasts Forum (https://laracasts.com/discuss)
StackOverflow (http://stackoverflow.com/questions/tagged/laravel)

Thanks in advance.


add MOCK_PIPELINE env var to runner if exists

Adds MOCK_PIPELINE to managed ai-runner container if exists.  Assists with quickly testing go-livepeer updates where pipeline results are not necessary.

@ad-astra-video, could we use the optimization_flags to pass this environment variable to the container?

Member

Never mind I see why you would want this when people don't use managed containers 👍🏻. Let's update the patch instead.

@ad-astra-video I like this addition 🚀. I updated the patch file to give people the ability to use ENV variables instead of the config file (see ea24a706d7bc42109b02ad954fd82d70166784a8). A branch in which the patch is applied is found here https://github.com/livepeer/ai-worker/pull/117. Let's close this for now since we don't want the MOCK ability in the main branch since people can abuse it.


out/index.html already exists

When running a Netlify CLI build locally or building at Netlify I get the same error. The NextJS build goes fine but the plugin stops on copying files to "out".
To Reproduce
Steps to reproduce the behavior locally:

In terminal netlify build

Steps to reproduce the behavior on Netlify:

Create a new site using https://github.com/matt-antone/navalign-next-js

Expected behavior
A complete build and deployment on Netlify
Versions

Next.js:  "next": "^10.2.0",
plugin (if installed at fixed version): "<EMAIL_ADDRESS>
If you're using the CLI to build

OS: [e.g. macOS, Windows] macOS
netlify/cli version: netlify-cli/3.30.7 darwin-x64 node-v14.16.0

If you're using file-based installation
netlify.toml:
[build]
command = "yarn build"
publish = "out"
functions = "functions"
[[plugins]]
package = "netlify-plugin-cache-nextjs"
# These options will cache the build directory at ${NETLIFY_BASE}/frontend/.next-build
[plugins.inputs]
# The path to the build directory
build_dir_path = "frontend"
# Custom build directory if you aren't using .next (https://nextjs.org/docs/api-reference/next.config.js/setting-a-custom-build-directory)
# custom_build_dir_name = ".next"
[context.production.environment]
NEXT_SERVERLESS = "true"
NODE_ENV = "production"
Output from local build:
────────────────────────────────────────────────────────────────
Netlify Build
────────────────────────────────────────────────────────────────
❯ Version
@netlify/build 11.18.1
❯ Flags
{}
❯ Current directory
/Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0
❯ Config file
/Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/netlify.toml
❯ Context
production
❯ Loading plugins

<EMAIL_ADDRESS>from Netlify app and package.json
<EMAIL_ADDRESS>from netlify.toml

────────────────────────────────────────────────────────────────

onPreBuild command from @netlify/plugin-nextjs
────────────────────────────────────────────────────────────────

info  - Loaded env from /Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/.env.local
info  - Using webpack 5. Reason: future.webpack5 option enabled https://nextjs.org/docs/messages/webpack5
Image domains set in next.config.js are ignored.
Please set the env variable NEXT_IMAGE_ALLOWED_DOMAINS to "res.cloudinary.com" instead
No Next.js cache to restore.
(@netlify/plugin-nextjs onPreBuild completed in 468ms)
────────────────────────────────────────────────────────────────
2. onPreBuild command from netlify-plugin-cache-nextjs
────────────────────────────────────────────────────────────────
No cache found for the .next folder at the location frontend/.next/cache
(netlify-plugin-cache-nextjs onPreBuild completed in 123ms)
────────────────────────────────────────────────────────────────
3. build.command from netlify.toml
────────────────────────────────────────────────────────────────
$ yarn build
yarn run v1.22.10
$ next build
info  - Using webpack 5. Reason: future.webpack5 option enabled https://nextjs.org/docs/messages/webpack5
info  - Checking validity of types
info  - Creating an optimized production build
info  - Compiled successfully
info  - Collecting page data
[=== ] info  - Generating static pages (0/291)[react-markdown] Warning: please pass a string as children (not: In addition to the equity market declines, what stands out about 2018 is the breadth of negative returns across almost every type of asset class and financial market, whether bonds, equities, or commodities. Even core investment-grade bonds were in the red. It was extremely difficult to make money in the financial markets last year.,[object Object])
[==  ] info  - Generating static pages (145/291)[react-markdown] Warning: please pass a string as children (not: In addition to the equity market declines, what stands out about 2018 is the breadth of negative returns across almost every type of asset class and financial market, whether bonds, equities, or commodities. Even core investment-grade bonds were in the red. It was extremely difficult to make money in the financial markets last year.,[object Object])
info  - Generating static pages (291/291)
info  - Finalizing page optimization
Page                                                                  Size     First Load JS
┌ ● /                                                                 3.9 kB          256 kB
├ ● /[slug]                                                           3.44 kB         255 kB
├   ├ /careers
├   ├ /disclosures
├   ├ /form-crs
├   └ [+4 more paths]
├ ○ /404                                                              3.05 kB        68.1 kB
├ ● /services                                                         1.47 kB         148 kB
├ ● /services/[slug]                                                  5.67 kB         258 kB
├   ├ /services/2018-in-review-worst-year-since-great-recession
├   ├ /services/4-financial-priorities-young-families-should-address
├   ├ /services/401k-the-retirement-marathon
├   └ [+121 more paths]
├ ● /services/business/[slug]                                         6.67 kB         259 kB
├   ├ /services/business/401k-and-pension-plan-fiduciary
├   ├ /services/business/business-owner
├   └ /services/business/succession-exit-planning
├ ● /services/family/[slug]                                           6.66 kB         259 kB
├   ├ /services/family/empty-nesters
├   ├ /services/family/married-no-children
├   ├ /services/family/raising-a-family
├   └ [+2 more paths]
├ ● /services/individual/[slug]                                       6.67 kB         259 kB
├   ├ /services/individual/business-executive
├   ├ /services/individual/doctors-physicians
├   ├ /services/individual/entertainment-industry
├   └ [+3 more paths]
├ ● /updates                                                          1.47 kB         148 kB
├ ● /updates/[slug]                                                   5.67 kB         258 kB
├   ├ /updates/2018-in-review-worst-year-since-great-recession
├   ├ /updates/4-financial-priorities-young-families-should-address
├   ├ /updates/401k-the-retirement-marathon
├   └ [+121 more paths]
├ ● /what-we-do                                                       1.38 kB         253 kB
├ ● /what-we-do/[slug]                                                3.48 kB         255 kB
├   ├ /what-we-do/401k-and-pension-plan-fiduciary
├   ├ /what-we-do/fiduciary-financial-planning
├   ├ /what-we-do/fiduciary-investment-services
├   └ [+2 more paths]
├ ● /who-we-are                                                       1.65 kB         254 kB
└ ● /who-we-are/[slug]                                                8.48 kB         260 kB
├ /who-we-are/christopher-carter
├ /who-we-are/david-jacobs
├ /who-we-are/index
└ [+7 more paths]

First Load JS shared by all                                         65 kB
├ chunks/commons.b12e07.js                                          13.5 kB
├ chunks/framework.85c078.js                                        42.6 kB
├ chunks/main.d2a1b3.js                                             6.9 kB
├ chunks/pages/_app.feb5a5.js                                       1.03 kB
└ chunks/webpack.14e883.js                                          1 kB

λ  (Lambda)  server-side renders at runtime (uses getInitialProps or getServerSideProps)
○  (Static)  automatically rendered as static HTML (uses no initial props)
●  (SSG)     automatically generated as static HTML + JSON (uses getStaticProps)
(ISR)     incremental static regeneration (uses revalidate in getStaticProps)
✨  Done in 12.54s.
(build.command completed in 12.7s)
────────────────────────────────────────────────────────────────
4. onBuild command from @netlify/plugin-nextjs
────────────────────────────────────────────────────────────────
** Running Next on Netlify package **
🚀 Next on Netlify 🚀
💼 Copying static NextJS assets to out
────────────────────────────────────────────────────────────────
Plugin "@netlify/plugin-nextjs" internal error
────────────────────────────────────────────────────────────────
Error message
Error: 'out/_next/static/JeCJ-lXogoq2R7bQ8v0od/_buildManifest.js' already exists
Plugin details
Package:        @netlify/plugin-nextjs
Version:        3.3.1
Repository:     git+https://github.com/netlify/netlify-plugin-nextjs.git
npm link:       https://www.npmjs.com/package/@netlify/plugin-nextjs
Report issues:  https://github.com/netlify/netlify-plugin-nextjs/issues
Error location
In "onBuild" event in "@netlify/plugin-nextjs" from Netlify app and package.json
at mayCopyFile (/Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/node_modules/fs-extra/lib/copy-sync/copy-sync.js:62:11)
at onFile (/Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:10)
at getStats (/Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/node_modules/fs-extra/lib/copy-sync/copy-sync.js:48:44)
at startCopy (/Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/node_modules/fs-extra/lib/copy-sync/copy-sync.js:38:10)
at copyDirItem (/Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/node_modules/fs-extra/lib/copy-sync/copy-sync.js:122:10)
at /Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/node_modules/fs-extra/lib/copy-sync/copy-sync.js:115:39
at Array.forEach ()
at copyDir (/Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/node_modules/fs-extra/lib/copy-sync/copy-sync.js:115:23)
at onDir (/Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/node_modules/fs-extra/lib/copy-sync/copy-sync.js:105:10)
at getStats (/Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/node_modules/fs-extra/lib/copy-sync/copy-sync.js:45:37)
Resolved config
build:
command: yarn build
commandOrigin: config
environment:
- NEXT_SERVERLESS
- NODE_ENV
publish: /Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/out
functionsDirectory: /Users/antone/Dropbox (Personal)/DevProjects/Glyphix/navalign3.0/functions
plugins:
- inputs: {}
origin: ui
package: '@netlify/plugin-nextjs'
- inputs: {}
origin: config
package: netlify-plugin-cache-nextjs

@matt-antone hey matt! check out the CLI build part of our README: https://github.com/netlify/netlify-plugin-nextjs#cli-usage
unfortunately right now the CLI experience is still a bit fidgety as described in the README. we're getting a lot closer to cleaning up CLI builds under the hood to make this experience a lot easier (for plugin devs and plugin users)!
the reason you might be seeing your error in particular is if your node_modules changed/purged between builds. the best way to handle that in this case is to just delete out and rebuild. i looked at your repo and don't see anything preexisting in out that you would want to keep (from deleting between builds, when you see this error).
let me know if this solves your issue!

@lindsaylevine I'm seeing a similar issue, but it's not working on the Netlify build process. Plot twist though, it works locally using the CLI.
I'm not sure how to debug at the moment seeing as I can't see the interim output on Netlify.

@tmilewski hmmm, how strange! what is the exact error you're seeing? regardless of that answer, though, i'll probably need a repo that reproduces your issue to figure out what's going on exactly 🙏

I'm on my phone currently, so I'll try and provide more later, but I'm running an NX monorepo with two front-end NextJS applications. At first, I was running into an error around .next/static not having files. I fixed that by manually setting the Next configuration distDir with an ENV variable to dist/apps/[app name]/.static/. That's where I then wound up where it's complaining that a chunk already exists in _next/.

@matt-antone hey matt! check out the CLI build part of our README: https://github.com/netlify/netlify-plugin-nextjs#cli-usage
unfortunately right now the CLI experience is still a bit fidgety as described in the README. we're getting a lot closer to cleaning up CLI builds under the hood to make this experience a lot easier (for plugin devs and plugin users)!
the reason you might be seeing your error in particular is if your node_modules changed/purged between builds. the best way to handle that in this case is to just delete out and rebuild. i looked at your repo and don't see anything preexisting in out that you would want to keep (from deleting between builds, when you see this error).
let me know if this solves your issue!

Hi Lindsay,
Just picking this up again. I went so far as to rebuild using the next-netlify-starter. Deloying worked locally all day yesterday without having to delete any folders. Woke up this morning and ran the build in the same terminal with no changes made for giggles. And it started throwing errors again.
I've updated manually to 3.4.1 and am still having the same issue in both local and netlify builds. Just deleting the /out folder doesn't work for me locally.
Link to the latest deploy log:
https://app.netlify.com/sites/loving-shaw-92ea86/deploys/60ba761c5261020008cbb365#L5-L10

I'm hitting the same issue. I recently converted a react codebase to next js and installed the plugin via the manual installation directions in the README. Using "@netlify/plugin-nextjs": "^3.4.2".
Fails on netlify, but yarn build works fine locally.
12:25:59 AM: ────────────────────────────────────────────────────────────────
12:25:59 AM:   3. onBuild command from @netlify/plugin-nextjs
12:25:59 AM: ────────────────────────────────────────────────────────────────
12:25:59 AM:
12:25:59 AM: ** Running Next on Netlify package **
12:25:59 AM: 🚀 Next on Netlify 🚀
12:25:59 AM: 🌍 Copying public/ folder to out
12:26:00 AM: 💼 Copying static NextJS assets to out
12:26:00 AM: 💫 Setting up API endpoints as Netlify Functions in netlify/functions
12:26:00 AM: 💫 Setting up pages with getInitialProps as Netlify Functions in netlify/functions
12:26:00 AM: 💫 Setting up pages with getServerSideProps as Netlify Functions in netlify/functions
12:26:00 AM: 🔥 Copying pre-rendered pages with getStaticProps and JSON data to out
12:26:00 AM: 💫 Setting up pages with getStaticProps and fallback: true as Netlify Functions in netlify/functions
12:26:00 AM: 💫 Setting up pages with getStaticProps and revalidation interval as Netlify Functions in netlify/functions
12:26:00 AM: 🔥 Copying pre-rendered pages without props to out
12:26:00 AM: Building 22 pages
12:26:00 AM: 💼 Copying WP4 dynamic import chunks to netlify/functions/next_prayers/nextPage
12:26:00 AM: 💼 Copying WP4 dynamic import chunks to netlify/functions/next_prayers_id/nextPage
12:26:00 AM:
12:26:00 AM: ────────────────────────────────────────────────────────────────
12:26:00 AM:   Plugin "@netlify/plugin-nextjs" internal error
12:26:00 AM: ────────────────────────────────────────────────────────────────
12:26:00 AM:
12:26:00 AM:   Error message
12:26:00 AM:   Error: 'out/index.html' already exists
12:26:00 AM:
12:26:00 AM:   Plugin details
12:26:00 AM:   Package:        @netlify/plugin-nextjs
12:26:00 AM:   Version:        3.4.2
12:26:00 AM:   Repository:     git+https://github.com/netlify/netlify-plugin-nextjs.git
12:26:00 AM:   npm link:       https://www.npmjs.com/package/@netlify/plugin-nextjs
12:26:00 AM:   Report issues:  https://github.com/netlify/netlify-plugin-nextjs/issues
12:26:00 AM:
12:26:00 AM:   Error location
12:26:00 AM:   In "onBuild" event in "@netlify/plugin-nextjs" from netlify.toml and package.json
12:26:00 AM:       at mayCopyFile (/opt/build/repo/node_modules/fs-extra/lib/copy-sync/copy-sync.js:62:11)
12:26:00 AM:       at onFile (/opt/build/repo/node_modules/fs-extra/lib/copy-sync/copy-sync.js:54:10)
12:26:00 AM:       at getStats (/opt/build/repo/node_modules/fs-extra/lib/copy-sync/copy-sync.js:48:44)
12:26:00 AM:       at startCopy (/opt/build/repo/node_modules/fs-extra/lib/copy-sync/copy-sync.js:38:10)
12:26:00 AM:       at handleFilterAndCopy (/opt/build/repo/node_modules/fs-extra/lib/copy-sync/copy-sync.js:33:10)
12:26:00 AM:       at copySync (/opt/build/repo/node_modules/fs-extra/lib/copy-sync/copy-sync.js:26:10)
12:26:00 AM:       at setupStaticFileForPage (/opt/build/repo/node_modules/@netlify/plugin-nextjs/src/lib/helpers/setupStaticFileForPage.js:12:3)
12:26:00 AM:
12:26:00 AM:   Resolved config
12:26:00 AM:   build:
12:26:00 AM:     command: yarn build
12:26:00 AM:     commandOrigin: config
12:26:00 AM:     publish: /opt/build/repo/out
12:26:00 AM:   functions:
12:26:00 AM:     '*': {}
12:26:00 AM:   plugins:
12:26:00 AM:     - inputs: {}
12:26:00 AM:       origin: config
12:26:00 AM:       package: '@netlify/plugin-nextjs'
12:26:00 AM: Caching artifacts
12:26:00 AM: Started saving node modules
12:26:00 AM: Finished saving node modules
12:26:00 AM: Started saving build plugins
12:26:00 AM: Finished saving build plugins
12:26:00 AM: Started saving yarn cache
12:26:00 AM: Finished saving yarn cache
12:26:00 AM: Started saving pip cache
12:26:00 AM: Finished saving pip cache
12:26:00 AM: Started saving emacs cask dependencies
12:26:00 AM: Finished saving emacs cask dependencies
12:26:00 AM: Started saving maven dependencies
12:26:00 AM: Finished saving maven dependencies
12:26:00 AM: Started saving boot dependencies
12:26:00 AM: Finished saving boot dependencies
12:26:00 AM: Started saving rust rustup cache
12:26:00 AM: Finished saving rust rustup cache
12:26:00 AM: Started saving go dependencies
12:26:00 AM: Finished saving go dependencies
12:26:04 AM: Build failed due to a plugin error: Build script returned non-zero exit code: 3
12:26:04 AM: Creating deploy upload records
12:26:04 AM: Failing build: Failed to build site
12:26:04 AM: Failed during stage 'building site': Build script returned non-zero exit code: 3
12:26:04 AM: Finished processing build request in 1m23.358990405s

closing since we haven't received a response/repro. please re-comment if you continue to need help!

While not ideal, (see: losing caching, etc) what I wound up doing to make this workable in my Nx monorepo is creating a plugin and placing it before @netlify/plugin-nextjs:
const { copySync } = require('fs-extra');

module.exports = {
  onBuild: async () => {
    const currentProject = process.env.PROJECT_NAME;

    if (currentProject) {
      copySync(
        `/opt/build/repo/dist/apps/${currentProject}/`,
        '/opt/build/repo',
        { overwrite: true }
      );
    }
  },
};

[[plugins]]
  package = "./tools/plugins/netlify/stop-build"

[[plugins]]
  package = "netlify-plugin-contextual-env"

[[plugins]]
  package = "./tools/plugins/netlify/nx-nextjs"

[[plugins]]
  package = "@netlify/plugin-nextjs"

@tmilewski take a look at #433! this will go out in our next release :)

I've had the same issue. Actually the error message perfectly described the problem. In my project I've migrated from CRA to Nextjs and there was still an index.html in the public/ folder which is being copied to out/.
After deleting the obsolete index.html from my public/ folder it all worked fine. duh


Other coins disappear on the top bar

Let's say I add four tickers: BTC, ETH, LTC and XRP. When I restart my PC or restart coinprice-indicator, all coin tickers disappear except the main one (BTC). I have to re-add the tickers every time I restart, why is that? I'm on Ubuntu 16.04 LTS by the way.

@sirajuddin97 you can configure which tickers are loaded by editing startmany.yaml and then running the app with make many or python3 coin/coin.py --file=startmany.yaml that way it will always start the same tickers.

Oh.. I wasn't aware of that. Thanks @bluppfisk!


RangeError: Duplicate use of selection JSON ID cell

Hi, I'm trying to use this amazing component but the following error is thrown when i import it:

I'm using it as the README.md says.
Template side:
<quasar-tiptap v-bind="options" />
Script side:
import { QuasarTiptap, RecommendedExtensions } from "quasar-tiptap";
import "quasar-tiptap/lib/index.css";
export default {
    components: {QuasarTiptap},
    data() {
        return {
        options: {
		content: "content",
		editable: true,
		extensions: [
			...RecommendedExtensions,
			// other extenstions
			// name string, or custom extension
		],
		toolbar: [
			"add-more",
			"separator",
			"bold",
			"italic",
			"underline",
			// other toolbar buttons
			// name string
		],
	},
        }
    }
}

Current version is:  "quasar-tiptap": "^1.9.1"
I love this amazing project, I hope you could help me.
PD: My project is just a Vue/Nuxt project, not Quasar project.

quasar-tiptap is a quasar-based project, which depends on quasar and some quasar's components.

quasar-tiptap is a quasar-based project, which depends on quasar and some quasar's components.

I'm also experiencing this on a quasar project.
here are dependency versions:
"dependencies": {
    "@quasar/extras": "^1.0.0",
    "algoliasearch": "^4.8.5",
    "axios": "^0.18.1",
    "core-js": "^3.6.5",
    "katex": "^0.11.1",
    "mermaid": "^8.9.2",
    "qs": "^6.7.0",
    "quasar": "^1.0.0",
    "quasar-tiptap": "^1.9.1",
    "tiptap": "^1.32.1",
    "tiptap-extensions": "^1.35.1",
    "vue-autosuggest": "^2.2.0",
    "vue-codemirror": "^4.0.6",
    "vue-horizontal": "^0.8.8",
    "vue-i18n": "^8.0.0",
    "vue-instantsearch": "^3.4.3",
    "vue-plugin-load-script": "^1.3.2"
  },

I have  the same problem. Using tiptap only seems to work ...
Any idea how to fix this?

I have the same problem. Using tiptap only seems to work ...
Any idea how to fix this?

I was able to resolve it by uninstalling all of quasar tiptap's dependencies and reinstalling. Then make sure you are configuring quasar-tiptap to run only the client in your boot file

This is all a bit new to me but what I have found out is this:
quasar-tiptap package.json specifies "prosemirror-utils": "^0.9.6" but the latest version of "prosemirror-utils" is "1.0.0-0"
So, when quasar-tiptap installs, it creates its own (nested) node_modules folder and installs prosemirror-utils and its out-of-date dependency prosemirror-tables. I think the presence of two versions of prosemirror-tables is what is causing the error.
So, to my app's package.json I added the following to ensure I have the latest versions in my app,
"prosemirror-tables": "^1.1.1",
"prosemirror-utils": "^1.0.0-0",

then deleted the node_modules folder within myapp/node_modules/quasar-tiptap folder so the imports within quasar-tiptap use the latest version from the main node_modules and there were no duplicate prosemirror packages.
quasar dev with the basic demo from the README.md page and all seems well.
As far as actually using quasar-tiptap though, there are a few more issues and a question here: #76
Murray


Switch from using GOV.UK Jenkins to Travis

This project isn't owned by GOV.UK Publishing anymore so it needs to stop using Jenkins to publish changes.
Ideally I'd use a deploy key for this, but it turns out that you can't attach the same deploy key to more than one repo. This means that we're going to use a GitHub token attached to the govuk-ci user - this should be moved to a different user in the future. To make that happen:

Add the personal access token as a secure Travis env var
Change the Git URLs to push over HTTPS, not SSH

The gem_publisher gem expects there to be a file at .gem/credentials. I've encrypted that file for Travis and added that file to the Travis worker.
Same deal for the npm publish step.

I've deleted the webhook and disabled the Jenkins job.

Yay, it's working now I think. Had some trouble with encrypting multiple files for a while.

Add "DO NOT MERGE" so that this stops notifying my team's Slack until somebody is ready to review it.

This means that we're going to use a GitHub token attached to the govuk-ci user - this should be moved to a different user in the future

Should move from govuk-ci to a different user? That seems like a good fit for now.
Otherwise, i think we're happy with the changes and the next step is to merge and test the various deployment setup/providers - as we have with other repos.


Run CI test on multiple versions of Python, Django and Wagtail

Following Wagtail's tests, testing with Django 1.8 and 1.10 on Python 2.7 and Django 1.10 only on Python 3.4, 3.5, 3.6 (I'm not sure why not Python 2.7 since Django 1.10 is compatible with it but I'm sure they have their reasons). For all those combinations, testing against Wagtail 1.7, 1.8, 1.9.
Close #22.

Rebased master onto the branch. Hopefully everything still works 😕


Modify incflo to work with moving redistribution from AMReX-Hydro into amrex

https://github.com/AMReX-Codes/amrex/pull/3378
https://github.com/AMReX-Codes/AMReX-Hydro/pull/109


docs: update azure search langchain notebook

Description: Update the azure search notebook to have more descriptive comments, and an option to choose between OpenAI and AzureOpenAI Embeddings

@baskaryan please take a look


qtquickcontrols is blocking channels

qtquickcontrols failure is blocking KDE https://hydra.nixos.org/build/125404486. cc @petabyteboy @ttuegel

According to git bisect, the commit that caused this issue is<PHONE_NUMBER>f0bef7aa4963f14cf599b74e9fd7e8 by @ttuegel. The error message I see during the build is:
mkdir: cannot create directory '/nix/store/w8k3lq0mxlwkjxqvak956p3jfrhhbmx7-qtdeclarative-5.14.2-bin/lib/qt-5.14.2/qml/QtQuick/Controls': Permission denied
make[2]: *** [Makefile:1642: install_qmlcacheinst] Error 1
make[2]: Leaving directory '/build/qtquickcontrols-everywhere-src-5.14.2/src/controls'
make[1]: *** [Makefile:64: sub-controls-install_subtargets] Error 2
make[1]: Leaving directory '/build/qtquickcontrols-everywhere-src-5.14.2/src'
make: *** [Makefile:61: sub-src-install_subtargets] Error 2
builder for '/nix/store/682c2y33slg99jznhp1nzcymjs8jxdnb-qtquickcontrols-5.14.2.drv' failed with exit code 2

https://github.com/NixOS/nixpkgs/pull/96248 fixes the issue for me.


Front-page example doesn't compile on Rust stable (1.2)

I copied-and-pasted the front-page example for “Deserialization without Macros”—specifically the section on structs—and tried to compile it, but it fails to compile.
All but one of the compiler errors are due to the PointField type being referred to as Field. I fixed those errors, but there remains one compiler error, which is at line 92 in the list below.
src/main.rs:62:26: 62:31 error: use of undeclared type name `Field`
src/main.rs:62             type Value = Field;
                                        ^~~~~
src/main.rs:68:31: 68:39 error: failed to resolve. Use of undeclared type or module `Field`
src/main.rs:68                     "x" => Ok(Field::X),
                                             ^~~~~~~~
src/main.rs:68:31: 68:39 error: unresolved name `Field::X`
src/main.rs:68                     "x" => Ok(Field::X),
                                             ^~~~~~~~
src/main.rs:69:31: 69:39 error: failed to resolve. Use of undeclared type or module `Field`
src/main.rs:69                     "y" => Ok(Field::Y),
                                             ^~~~~~~~
src/main.rs:69:31: 69:39 error: unresolved name `Field::Y`
src/main.rs:69                     "y" => Ok(Field::Y),
                                             ^~~~~~~~
src/main.rs:92:5: 121:6 error: method `visit_struct` is not a member of trait `serde::de::Visitor`
src/main.rs:92     fn visit_struct<V>(&mut self,
src/main.rs:93                        _fields: &[&str],
src/main.rs:94                        mut visitor: V) -> Result<Point, V::Error>
src/main.rs:95         where V: serde::de::MapVisitor
src/main.rs:96     {
src/main.rs:97         let mut x = None;
               ...
src/main.rs:102:22: 102:30 error: unresolved enum variant, struct or const `X`
src/main.rs:102                 Some(Field::X) => { x = Some(try!(visitor.visit_value())); }
                                     ^~~~~~~~
src/main.rs:103:22: 103:30 error: unresolved enum variant, struct or const `Y`
src/main.rs:103                 Some(Field::Y) => { y = Some(try!(visitor.visit_value())); }

I looked through the Serde documentation and source code but was unable to figure out what the call to visit_struct is supposed to be. Perhaps this example has gotten lost in the Serde API changes?
I understand that the Serde Serialize and Deserialize macros are first-class and that applications shouldn't be rolling out custom visitors for serialization and deserialization. However, the macros don't support renaming fields (#140), handling elided fields during deserialization (#90, #44), nor eliding default values during serialization (#43), and I need these features. So until the macros catch up with my use case, I must fall back to custom visitors.
Can someone explain what the call to visit_struct is supposed to be?
And perhaps someone can explain what the _fields parameter in serde::de::Deserializer::visit_struct is for?
And maybe someone can explain what “elt” means, as in serde::ser::Serializer::visit_struct_elt?

Oops sorry about that! I just pushed up a working example. I think this was just an older example I forgot to update.
I'm currently writing up documentation for serde, I'm sorry it's been taking so long. I personally think it's fine to write visitors, they are just a little complicated and I haven't yet figured out a great way to simplify them while keeping their performance. Anyway, some serializers and deserializers serialize structs differently than maps, such as bincode, which serializes structs essentially as a tuple with no field names. The visit_struct methods are hooks for those serializers to do something more optimal with these fields. The fields argument is a &[&str] of all the field names in a struct. The elt in visit_struct_elt is for serializing a single element of a struct. It serializes the field name and the field value as a pair in the serializer.
One thing that might help is to actually look at what serde_macros is generating. You can do this by writing up:
#![features(plugin)]
#![plugin(serde_macros)]

extern crate serde;

#[derive(Serialize, Deserialize)]
pub struct Point {
  x: usize,
  y: usize,
}

Then run: cargo build -v, grab the rustc command and run rustc ... -Z unstable-options --pretty expanded to pretty print out the whole crate. This isn't a long term requirement for writing complex visitors, but I hope it'll help you get started. Please let me know if there's more I can do to help.

Erick, thanks for the quick response!
The documentation isn't bad—aside from having up-to-date examples and more explanation for parameters and abbreviations.
Regarding visitors, what I found most confusing is the overloaded use of the word “visit.” While it's intuitive to have visitor types such as Visitor and MapVisitor with methods named visit, visit_struct, etc., I struggled at first with the Serializer and Deserializer types also having methods named visit*. It was unclear to me what was doing the visiting and what was being visited, though now, in hindsight, it's entirely clear.
In Go the idiom is to name interfaces with a noun ending in “-er.” E.g., a Reader has a Read method, a Closer has a Close method, and a Decoder has a Decode method. This is one of the many things that makes Go easy to use for beginners and experts alike.
Rust has traits instead of interfaces, but I think the “-er” naming scheme works well in many cases, just the same. For Serde, this suggests that, say, the Deserializer trait should have methods named deserialize*, not visit*. The specific names here don't matter, only that the API distinguishes between visitors and visitees. Just a thought.

Thanks, that's interesting idea, I've filed https://github.com/serde-rs/serde/issues/151 to track it.


window.XMLHttpRequest Blocking firebase calls

Hi I am using:
 "react": "16.0.0",     "react-native": "0.51.0",     "react-native-fetch-blob": "^0.10.8",
when i am using "window.XMLHttpRequest" i can upload my image to firebase bat canot write to firebas no more, whan i remove this i can write bat not upload the image.
my code is heare https://stackoverflow.com/questions/48215067/react-native-fetch-blob-is-blocking-firebase-calls-n-react-native-app
i dont know how to clear the window.XMLHttpRequest declaration on react native or reset it so the app can reach other calls.
please help

I am uploading to my node js app and from there connecting to firebase for uploading and saving the images in any size/blob....working 100%

I'm having the exact same problem-- did anyone figure out how to resolve this?

@terranball if this helps at all, what I did was the following (again, my issue was making a call specifically from my React Native app to Firebase Cloud Firestore):
As you see, it's a little hacky, but is currently working well for me. I set the window.XMLHttpRequest to a temp variable, then do my thing with react-native-fetch-blob, then later on, right before I am about to make my call to Cloud Firestore, I reset window.XMLHttpRequest to the original temp variable.
const Blob = RNFetchBlob.polyfill.Blob;
window.Blob = Blob;
const tempWindowXMLHttpRequest = window.XMLHttpRequest;
window.XMLHttpRequest = RNFetchBlob.polyfill.XMLHttpRequest;
...
window.XMLHttpRequest = tempWindowXMLHttpRequest;

Could this be re-opened?  It is causing problems with Firebase's SDK for Google Cloud Firestore as well.  It would be really nice if the polyfill could be fixed to be fully compatible or else better scope its usage so that it doesn't affect other libraries.

Hi, I'm new to react-native. Im also getting the same issue when I wanna upload an image to firebase. Can I know where is the "window" variable is declared? and what is it?


buildMozillaMach: Apply musl compat patch up to 114.0

A slightly modified version landed in 114.0a1.
Related: mozbz#1830040
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

The condition is wrong?  This rebuilds firefox which shouldn't happen.  (just a quick glance for now)

yes, it should be versionOlder version "114.0"

Multitasking is hard. Apparently I even tested this against lib.versionAtLeast. :tired_face:


Document for common service integration

@chenzhiwei @gyliu513 @DanielXLee
I create a document to guide other common services to integrate with the common service operator.
Please review and improve.

@horis233 Let's first rename the CRDs https://github.com/IBM/common-service-operator/issues/3, then update this doc.

@chenzhiwei Roger~

Thanks @horis233 , +1 with @chenzhiwei , we can start the work to rename the CRD now.
FYI @shikhasriva

@gyliu513 I have created a PR for the CRD name update, for the e2e-test part, @horis233 please continue work on it.
https://github.com/IBM/common-service-operator/pull/26

Updated the CRDs name.

@gyliu513 Updated, I will make another PR to update the API from common-service-operator to meta-operator as well.

Thanks @horis233 for the update.
/lgtm
/approve


[GOBBLIN-944] Provide the flexibility of deriving platform field in a different way for subclasses of BaseDatasetDescriptor

Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[X] My PR addresses the following [Gobblin JIRA]

https://issues.apache.org/jira/browse/GOBBLIN-944

Description

[X] Here are some details about my PR, including screenshots (if applicable):
Move two lines of code to a protected method for subclasses to override.

Tests

[X] My PR adds the following unit tests OR does not need testing for this extremely good reason:

Commits

[X] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

Hi @jack-moseley, can you review it? Thank you.

Codecov Report

Merging #2794 into master will increase coverage by 0.01%.
The diff coverage is 100%.

@@             Coverage Diff              @@
##             master    #2794      +/-   ##
============================================
+ Coverage     45.32%   45.33%   +0.01%
- Complexity     8862     8865       +3
============================================
  Files          1894     1894
  Lines         70910    70911       +1
  Branches       7799     7799
============================================
+ Hits          32141    32150       +9
+ Misses        35803    35798       -5
+ Partials       2966     2963       -3

Impacted Files
Coverage Δ
Complexity Δ

...service/modules/dataset/BaseDatasetDescriptor.java
73.33% <100%> (+0.91%)
14 <1> (+1)
:arrow_up:

...e/gobblin/runtime/locks/ZookeeperBasedJobLock.java
63.33% <0%> (-1.12%)
15% <0%> (-1%)

...lin/elasticsearch/writer/FutureCallbackHolder.java
62.85% <0%> (+1.42%)
4% <0%> (ø)
:arrow_down:

...lin/restli/throttling/ZookeeperLeaderElection.java
72.22% <0%> (+2.22%)
13% <0%> (ø)
:arrow_down:

...he/gobblin/writer/FineGrainedWatermarkTracker.java
84.67% <0%> (+2.41%)
29% <0%> (+1%)
:arrow_up:

...lin/util/filesystem/FileSystemInstrumentation.java
100% <0%> (+14.28%)
4% <0%> (+1%)
:arrow_up:

...a/org/apache/gobblin/util/limiter/NoopLimiter.java
60% <0%> (+20%)
3% <0%> (+1%)
:arrow_up:

Continue to review full report at Codecov.

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