MemoryError

When I try to upload a file with
api.post('/path/data', file=file('filename', 'rb'))

I get a MemoryError. It is because my server has only 512 mb ram and my upload size does not fit into memory usually. I think it is possible to do a streaming upload but I don't have enough knowledge on requests library.

It's definitely a bug. Even though requests library itself support uploading large files, smartfile library doesn't.
from smartfile import BasicClient

api = BasicClient(settings.SMARTFILE_API_KEY, settings.SMARTFILE_API_PASSWORD)
with open('large.file', 'rb') as file:
    api.upload('test.large', file)
...
Traceback (most recent call last):
  File "<stdin>", line 2, in <module>
  File "/usr/local/lib/python3.6/site-packages/smartfile/__init__.py", line 146, in upload
    return self.post('/path/data/', file=arg)
  File "/usr/local/lib/python3.6/site-packages/smartfile/__init__.py", line 131, in post
    return self._request('post', endpoint, id=id, data=kwargs)
  File "/usr/local/lib/python3.6/site-packages/smartfile/__init__.py", line 110, in _request
    return self._do_request(request, url, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/smartfile/__init__.py", line 207, in _do_request
    return super(BasicClient, self)._do_request(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/smartfile/__init__.py", line 53, in _do_request
    response = request(url, stream=True, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/api.py", line 110, in post
    return request('post', url, data=data, json=json, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/api.py", line 56, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 474, in request
    prep = self.prepare_request(req)
  File "/usr/local/lib/python3.6/site-packages/requests/sessions.py", line 407, in prepare_request
    hooks=merge_hooks(request.hooks, self.hooks),
  File "/usr/local/lib/python3.6/site-packages/requests/models.py", line 305, in prepare
    self.prepare_body(data, files, json)
  File "/usr/local/lib/python3.6/site-packages/requests/models.py", line 483, in prepare_body
    (body, content_type) = self._encode_files(files, data)
  File "/usr/local/lib/python3.6/site-packages/requests/models.py", line 164, in _encode_files
    body, content_type = encode_multipart_formdata(new_fields)
  File "/usr/local/lib/python3.6/site-packages/requests/packages/urllib3/filepost.py", line 86, in encode_multipart_formdata
    body.write(data)
MemoryError


usm: http2: Fix status codes 304 and 404

What does this PR do?
Fixes handling of status codes 304 and 404 in USM's HTTP/2 support. These are part of the static table in HPACK but were missing in a switch statement, resulting in all transactions with these codes being assigned a status code of zero and being marked as incomplete.
Also it adds all the status codes in the static table to the status codes test case.

Motivation

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Disallowing types as values at runtime?

Types are values. This is required for user-defined functions since their signatures are themselves Spackel programs. However, we might want to disallow using types as values at runtime; you can't do anything useful with them currently and if you could, we would probably run into all sorts of nightmares with dependent typing. The best way I see to go about this would be to distinguish between functions that can be called at runtime and functions that can only be called at compile time, à la comptime in Zig. We would then end up with three kinds of functions: fn (only callable at runtime), const? fn (callable both at runtime and compile time) and const fn (only callable at compile time). Generic types could then be simulated with const fn.

It is also worth noting that the signature resolution only supports PushType(_) right now; some day we'll have to extend it to a full compile time Spackel interpreter, preferably without duplicating too much work.

The ideal solution will be to implement signature resolution in terms of the existing type checker and interpreter, only flipping some switches to e.g. disable IO and allow types to be left on the stack at the end of the program.


Compilation error for Android

I'm trying to compile the source code for Xamarin.Android but there's some errors:
 •QStatus is not found

 •some casting errors like comparaison of int and intptr

Is there something to do with that?
thanks.

@abdelkader27 This should be fixed. Let me know if you're still seeing this.

Hi, thank you it's compiling fine now.


Atom.io & Sublime Text 3 not displaying Japanese characters?

Prerequisites

[x] Can you reproduce the problem in safe mode?
[x] Are you running the latest version of Atom?
[x] Did you check the debugging guide?
[x] Did you check the FAQs on Discuss?
[x] Are you reporting to the correct repository?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?

Description
Atom nor Sublime display Japanese characters properly to me. I've tried changing to Fonts in File>Settings to some Japanese fonts I have installed, such as Meiryo and MS Mincho Regular, I am on Windows 10, and have installed added Japanese language packs, yet the problem still persists
Versions
1.9.2

Atom supports Japanese character sets and, based on your issue, I'm assuming the file has been incorrectly encoded.
To change the character set manually, press ALT + U and you'll be greeted with encoding options.

We need to remove this bot from conversation.　It is unimportant and spammy to leave this messages.


Can't pipe result of z -t

z -t | cat differs from z -t, any way to get around this?
I'm trying to z -t | awk '{ print $2 }' | fzf which doesn't work :(

Looks like z -et fixed it


No such file or directory issue

when I run

from peregrinearb import get_opportunity_for_market
import asyncio
opportunity = asyncio.get_event_loop().run_until_complete(get_opportunity_for_market('BTC/USD'))

I receive
Traceback (most recent call last):
File "", line 1, in
File "/usr/local/Cellar/python/3.6.5/Frameworks/Python.framework/Versions/3.6/lib/python3.6/asyncio/base_events.py", line 468, in run_until_complete
return future.result()
File "/usr/local/lib/python3.6/site-packages/peregrinearb/async_find_opportunities.py", line 61, in get_opportunity_for_market
finder = OpportunityFinder(ticker, exchanges=exchanges, name=name)
File "/usr/local/lib/python3.6/site-packages/peregrinearb/async_find_opportunities.py", line 16, in init
exchanges = get_exchanges_for_market(market_name)
File "/usr/local/lib/python3.6/site-packages/peregrinearb/utils/general.py", line 24, in get_exchanges_for_market
with open('./../peregrinearb/collections/collections.json') as f:
FileNotFoundError: [Errno 2] No such file or directory: './../peregrinearb/collections/collections.json'
What should I do?
I Installed all the modules peregrinearb required.

Hi, I will look into fixing this. I know the cause right now.
For future reference, could you please submit Python errors as preformatted text? It makes them much easier to read and avoids markdown errors (such as __init__ becoming a bold init)

This has been fixed. See: https://github.com/wardbradt/peregrine/commit/2673acfff417ec8bf1cb970a5a645fea339e76de


Fetch Images setting not preserved

I set Fetch Images to false, but it keeps getting reset to true (v1.4.5).

Thanks new release has a fix!

should be fixed with v1.4.6, please comment if you encounter issue again on some devices. Thank you!


[Framer Motion] -> [React Animation Libraries]

Framer Motion
Framer Motion is an animation library for React
Link: https://www.framer.com/motion/
Checklist:

[X] I have performed a self-review of submitted resource and it follows the guidelines of the project.

Closing.


UI Form Refactoring and Improvements

The goal of this epic is to improve the form we have in the UI and use the Antd form everywhere.

Better validation and validation should be aligned with JSON schema
Form state should be managed by the form itself, we should not have the local states
We should use the Form props over our own props

List of forms to be worked on

[ ] Signup
[ ] SignIn
[ ] Forget Password
[ ] Team
[ ] User
[ ] Roles
[ ] Policy
[ ] Rule
[ ] Service

[x] Configure Service Form  https://github.com/open-metadata/OpenMetadata/pull/11734
[ ] Database
[ ] Dashboard
[ ] Pipeline
[ ] Messaging
[ ] Ml Models
[ ] Metadata
[ ] Storage

[ ] Ingestion ( Workflow )
[ ] Activity Feeds
[ ] Alerts
[x] Custom Attributes  #11656

[x] Tables
[x] Topics
[x] Pipelines
[x] Dashboards
[x] Ml Models
[x] Containers

[ ] Search index Pipelines
[ ] Data Insight Pipelines
[ ] Email Configuration
[ ] Bots
[ ] Test Suites
[ ] Table test
[ ] Column Test
[ ] KPIs
[x] Glossary https://github.com/open-metadata/OpenMetadata/pull/11780
[x] Glossary Term https://github.com/open-metadata/OpenMetadata/pull/11780
[x] Classification https://github.com/open-metadata/OpenMetadata/pull/11706

[x] Tags

@Sachin-chaurasiya where are we with this? and what are the blockers?

@Sachin-chaurasiya where are we with this? and what are the blockers?

Hello @harshach , the major part of aligning entity names with json schema is done, now minor improvements and refactoring is pending, will take care of it in 1.2.

@Sachin-chaurasiya what is remaining here?

Closing this issue as we are using the antd Form everywhere now and only bots one is pending which will be handled in https://github.com/open-metadata/OpenMetadata/issues/12882


add option to query variations matching some range of image_consistency

with image_consistency added to filename of variations and ability to "resume" with arbitrary variation settings, we can make scenes where images have a range of variances. ...oh hey, maybe it could be fun to specify a variations as a range, or a distributional RV like specifying alpha and beta of a beta distribution. users would probably be overwhelmed, so maybe I could parmeterize it that way under the hood, but then expose it to users differently... or even just parameterize it as mean and variance of the probability and then clean it up under the hood.

migrated to #34


Regarding changes in Django file.

Amazing Page with a detailed procedure but it would be really great if also you start from the very basics (already build Django project on the local system to azure).
There aren't many articles on the internet which explain the changes to be made to default settings that are already provided while creating the Django project for deploying in azure.
Whereas Her**ku documentation clearly explains everything from scratch.
overall 8,5/10

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1a96d5fc-0dd1-a344-5416-44039cee39b8
Version Independent ID: 72844ca4-b087-de15-be00-e0d87020a48b
Content: Tutorial: Deploy a Python Django app with Postgres - Azure App Service
Content Source: articles/app-service/tutorial-python-postgresql-app.md
Service: app-service
GitHub Login: @cephalin
Microsoft Alias: cephalin

Nikhil,  Thanks for taking time to share your valuable feedback on this Azure doc. We really appreciate the suggestions.
The doc aims to show step-step instructions on how to deploy Django web app and connect it to an Azure Database for Postgres database. The tutorial is meant to show something more involved, but still allow readers to learn things beyond a specific framework. For example, here you learn how to set environment variables and access them, create and connect with Azure Database for PostgreSQL database, deploying code to App Service and updating the code. This doc doesn’t aim to teach Django, but provides a walkthrough with the sample app only.
You may wish to check these docs for more additional info:
Azure for Python Developers
Quickstart: Create a Python app using Azure App Service on Linux

Configure a Linux Python app for Azure App Service
Hope this explanation helps.


usm: http2: Enable terminated_http2_monitoring_flag

What does this PR do?
Enables the const terminated_http2_monitoring_enabled so terminated_http2_batch_flush will be enabled

Motivation
The flag controlled the flush batches for the terminated_http2 connection map but it was disabled, thus we didn't flush anything

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Add test to verify routes replacing shared "state derived" routes

@kyranjamie this issue was generated from the list of items here which I believe you created? https://github.com/hirosystems/stacks-wallet-web/issues/1048 ...what are you thinking needs to be tested here?

This one was to think of any integration test flows we might want to test, specifically to test those that touch the routes that were previously derived, wallet unlocked state, for example.


Upload latest version on Hackage

The current version from Hackage does not include the latest fix that puts the token in the header. Therefore, all requests fail with "invalid_auth".
Thanks.

@dciug Thanks for opening the issue! I uploaded the latest version to Hackage.


/hub doesn't work in some games

for example, in tntrun, using /hub does not teleport you back to the hub has tntrun takes over. The plugin needs to be updated to allow dynamic commands for /hub, for example, /hub would by default teleport the player to the hub world. In TNTRun, /hub would run /tntrun leave, same for bedwars, etc.

Fixed by https://github.com/STEMMechanics/STEMCraft/pull/5


Makefile: install docs as non-executable

This removes the executable bits from the man pages. The 644 permissions are properly being applied to other docs already, but it was missed for the two man pages.

You can see the openSUSE package details with this patch here:
https://build.opensuse.org/package/show/network:utilities/newsboat
https://build.opensuse.org/request/show/560213

Coverage remained the same at 36.169% when pulling 99a8de121aec186b67a1acaff83711249422d179 on avindra:patch-3 into 8e90e96669f511b2222b351c90e76d33d2be5b7e on newsboat:master.

Good catch, thank you very much!


Graph API permissions clarification

The README mentions a permission called Synchronization.ReadWrite.OwnedBy, however, I don't find that API permission and instead Synchronization.ReadWrite.All, which I think can manage any application's synchronization configuration in the tenant.
I think clarification is needed. Thanks

Apologies - that was a typo. Updated the readme. It was correct in the blog link. Thank you for catching that.


helm3: Fix update state calculation and status resource for long running deploys

Porting https://github.com/giantswarm/chart-operator/pull/406 to helm3 branch.

Getting helm3 branch in sync. Going with a ping.


Remove yaml tests

Prior to this commit, some of our examples tests were duplicated as yaml tests. The main difference between the two tests was that in examples tests, the yaml was applied via kubectl create, and in the yaml tests, the yaml was applied via ko create. However, the yaml tests no longer include PipelineRuns that use images built by Tekton, so they are redundant with the examples tests.
This commit removes yaml tests, speeding up e2e test execution.
/kind cleanup
closes https://github.com/tektoncd/pipeline/issues/6844
Submitter Checklist
As the author of this PR, please check off the items in this checklist:

n/a Has Docs if any changes are user facing, including updates to minimum requirements e.g. Kubernetes version bumps
[x] Has Tests included if any functionality added or changed
[x] Follows the commit message standard
[x] Meets the Tekton contributor standards (including functionality, content, code)
[x] Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
n/a Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings). See some examples of good release notes.
n/a Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes
NONE

/lgtm


Dynamic composite bar

Add to composite bar when new composite is added
Sequential order for in-built viewlets

Required for https://github.com/Microsoft/vscode/issues/43645

@sandy081 thanks for the PR. This makes sense.
What I do not understand is why composites which get registered later are added as not pinned to the CompositeBar?
Why do you need that option and distinction?

If you always pin it, then it will override the existing pinned viewlet when refreshed

I will update the PR to handle following correctly

When a viewlet is added for the first time, it has to be pinned but do not show

Pin it by its order
Do not show

When a viewlet is added after refresh (was already added before)

Pin it at the position it was before
Show if it was shown before

When a viewlet is removed after refresh but was there before, then pinned should not have it.

Hope I cover all cases.

If you always pin it, then it will override the existing pinned viewlet when refreshed.

Can you please clarify this with an example. Just so we are on the same page.
Multiple viewlets can be pinned at the same time. If a user adds Azure viewlet and it is pinned that just means it is shown in the activity bar and this should not affect any other viewlet afaik.

I think pinning is not the issue. It is about showing the viewlet. When adding a viewlet, it pins and shows automatically. This is overriding the viewlet that is currently shown (after refresh).

Ok. Yeah compositeBar should support to show a new pinned viewlet without it being the active one.

@isidorn Updated the PR with following changes

Store all current composites with pinned state and retain the composites states
Compute pinned composites from loaded composite states and  current composites
Pin the added composite at correct location
Parameter in add api to activate the added composite
Store states on shutdown

@sandy081 I took a look at the PR and previsouly we were storing a list of pinned composite ids.
A now we store a list of objects, where each object has an id and if it is pinned. So basically the difference is that each composite bar also stores unpinned composite ids. Why is that?
Can't the owner of the composite bar store that so we do not change what we store in the composite bar?

Ok this makes sense. I tried it out and nothing seems broken.
Did you test it out with contributed viewlets? To be sure I would try out the following cases:

search moved to panel and back to activity bar
screen resized such that not all viewlets can be fit - make sure that the active one is still shown always
You can rearrange and hide viewlets

I tried with the contributed viewlets and some of the test cases you mentioned. Will test all cases and confirm.

@sandy081 great, then feel free to merge this in. A  test plan item would also be good.

Thanks and will have the testing part of activity groups contributions.


Cannot define multiple 'included' blocks for a Concern

Hi,
in jirb
irb(main):001:0> require 'active_record'
=> true
irb(main):002:0>
irb(main):003:0* ActiveRecord::Base.establish_connection(
irb(main):004:1*     :adapter   => 'jdbcmysql',
irb(main):005:1*     :reconnect => true,
irb(main):006:1*     :database  => 'XXX',
irb(main):007:1*     :pool      => 5,
irb(main):008:1*     :username  => 'XXX',
irb(main):009:1*     :password  => 'XXX',
irb(main):010:1*     :host      => 'localhost'
irb(main):011:1> )
I get ==>
ActiveSupport::Concern::MultipleIncludedBlocks: Cannot define multiple 'included' blocks for a Concern
in padrino everything is working...!!!!
what can I do?? any suggestions??
markus

able to reproduce and it's not just 4.2 that fails unexpectedly under JRuby :
jruby-1.7.19 :001 > require 'active_record'
 => true
jruby-1.7.19 :002 > ActiveRecord::Base.establish_connection( :adapter => 'oracle' )
/opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:587 warning: already initialized constant Reference
/opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.2.1/lib/active_support/values/time_zone.rb:37 warning: already initialized constant MAPPING
/opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.2.1/lib/active_support/values/time_zone.rb:189 warning: already initialized constant UTC_OFFSET_WITH_COLON
/opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.2.1/lib/active_support/values/time_zone.rb:190 warning: already initialized constant UTC_OFFSET_WITHOUT_COLON
/opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activerecord-4.2.1/lib/active_record/relation/delegation.rb:40 warning: already initialized constant BLACKLISTED_ARRAY_METHODS
ActiveSupport::Concern::MultipleIncludedBlocks: Cannot define multiple 'included' blocks for a Concern
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.2.1/lib/active_support/concern.rb:126:in `included'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activerecord-4.2.1/lib/active_record/relation/delegation.rb:54:in `ClassSpecificRelation'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activerecord-4.2.1/lib/active_record/relation/delegation.rb:51:in `Delegation'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activerecord-4.2.1/lib/active_record/relation/delegation.rb:6:in `ActiveRecord'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activerecord-4.2.1/lib/active_record/relation/delegation.rb:5:in `(root)'
	from org/jruby/RubyKernel.java:1071:in `require'
	from /opt/local/rvm/rubies/jruby-1.7.19/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:69:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:240:in `load_dependency'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.2.1/lib/active_support/dependencies.rb:274:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activerecord-4.2.1/lib/active_record/base.rb:1:in `(root)'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activerecord-4.2.1/lib/active_record/base.rb:23:in `(root)'
	from org/jruby/RubyKernel.java:1107:in `eval'
	from (irb):1:in `(root)'
	from (irb):2:in `evaluate'
	from org/jruby/RubyKernel.java:1507:in `loop'
	from org/jruby/RubyKernel.java:1270:in `catch'
	from org/jruby/RubyKernel.java:1270:in `catch'
	from /opt/local/rvm/rubies/jruby-1.7.19/bin/irb:13:in `(root)'

jruby-1.7.19 :001 > gem 'activerecord', '4.0.13'
 => true
jruby-1.7.19 :002 > require 'active_record'
 => true
jruby-1.7.19 :003 > ActiveRecord::Base.establish_connection( :adapter => 'oracle' )
/opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:556 warning: already initialized constant Reference
NameError: Undefined method == for class 'ActiveSupport::ProxyObject'
	from org/jruby/RubyModule.java:2330:in `undef_method'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/proxy_object.rb:5:in `ProxyObject'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/proxy_object.rb:4:in `ActiveSupport'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/proxy_object.rb:1:in `(root)'
	from org/jruby/RubyKernel.java:1071:in `require'
	from /opt/local/rvm/rubies/jruby-1.7.19/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:69:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:1:in `(root)'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:229:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:214:in `load_dependency'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:229:in `require'
	from org/jruby/RubyKernel.java:1071:in `require'
	from /opt/local/rvm/rubies/jruby-1.7.19/lib/ruby/shared/rubygems/core_ext/kernel_require.rb:69:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/duration.rb:1:in `(root)'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:1:in `(root)'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:229:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:214:in `load_dependency'
... 14 levels...
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:229:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:214:in `load_dependency'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:229:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/time.rb:12:in `(root)'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:1:in `(root)'
	from org/jruby/RubyKernel.java:1107:in `eval'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:229:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:214:in `load_dependency'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activesupport-4.0.13/lib/active_support/dependencies.rb:229:in `require'
	from /opt/local/rvm/gems/jruby-1.7.19@jdbc/gems/activerecord-4.0.13/lib/active_record/base.rb:6:in `(root)'
	from (irb):1:in `(root)'
	from (irb):3:in `evaluate'
	from org/jruby/RubyKernel.java:1507:in `loop'
	from org/jruby/RubyKernel.java:1270:in `catch'
	from org/jruby/RubyKernel.java:1270:in `catch'
	from /opt/local/rvm/rubies/jruby-1.7.19/bin/irb:13:in `(root)'jruby-1.7.19 :004 > exit

please note that you're not loading any AR-JDBC code, closing as duplicate of #638
... this is likely related to load-path expansion which should be fixed in JRuby 1.7.20


Add option for rpc-product and update file lookup

The Master branch of rpc-o has added an rpc-release file, this change
allows the RPC-Differ to extract data from the new release file and
lookup the RPC product information.
Signed-off-by: Kevin Carter<EMAIL_ADDRESS>

Tested using the following command: # rpc-differ --debug -rr "ansible-role-pike-requirements.yml" --update -rp pike -r "https://github.com/rcbops/rpc-openstack" --update "c4132cd226087c3d1394d5c4cf6ff0292a437034" "d8cfda6b7c434774c8575b8fa3726afab99340b9"
Output:
This report shows changes from ``c4132cd226087c3d1394d5c4cf6ff0292a437034`` to ``d8cfda6b7c434774c8575b8fa3726afab99340b9`` in
RPC-OpenStack.

rpc-openstack
-------------

4 commits were found in
`rpc-openstack <https://github.com/rcbops/rpc-openstack>`_ from ``c4132cd2`` to
``d8cfda6b``:

...


the problem of request consumption of gateway network

I spent more network request time with the gateway。
http://localhost:8362/api/user/info?id=1 20ms - service address
http://localhost:3164/api/user/info?id=1 200ms-ocelot gateway
I've tried many times.I'm not very aware of the source code now, I will spend a certain amount of time studying ocelotsource code 。
I'm not sure the specific reason, but I hope you can restore this scene

try to delete Console Logger @jakey188


Please add DuckDuckGo to 'General Search Engines' list

Hi!
Please add DuckDuckGo to "General Search Engines" list:
- [DuckDuckGo](https://duckduckgo.com/)

Best regards

Hi, thank you for your interest in this project.
I already thought about it, but I discovered it's a simple wrapper aroung Bing. For this reason I don't think it's worth adding.
For other suggestions I'm here ready to reply. Have a nice day :)


Checkout how capitalization is used in other package listing sites for namespaces

We have a bug around capitalization... we are actually limited to DNS-1123 names.
We should evaluate how others handle this. Are uppercase letters allowed? What about internationalization, since DNS-1123 is an ascii subset?

As the Helm Hub has been turned down, this issue no longer applies. Closing


calibre: use webengine i/o webkit

Motivation for this change
As of v4, calibre supports qtwebengine so use that instead of the
deprecated qtwebkit.
This way we don't have to compile qtwebkit locally which is a PITA.
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Thanks. I missed that one when reviewing 16fe6037509c49c89291c6a362dd31f79d5af467


Add scaffolding for cluster creation

As a person in an operations role, I'd like to be able to spin up the Kubernetes cluster itself in an automated manner.

Fixed in change 5b578d8


Update README.md (typo fix)

Hey guys, I just did a minor typo fix here.
Currently looking into libGDX + kotlin (trying to learn both at the same time 😄). Found your project and was impressed. I guess I need to learn the libGDX api first though 😃

Thanks for the pull request. Just so you know, we typically update master only during releases, and develop is the active development branch.

You‘re welcome! Yeah sorry that was my bad, actually it’s a widespread convention with master and develop branch. Didn’t think about it and tried using the GitHub feature (in browser file edit) for the first time.

It's OK, don't worry, every contribution is welcome. :)


Using fleet_adapter_template with nav_graph

I'm trying to make a new fleet adapter using this template. I understand the use of the RobotClientAPI, but when I run the adapter template is raises the next error:
operator[] call on scalar
I think that may be is something wrong with my config.yaml or my nav_graph.yaml. Is it possible to get two example files of this files or any detailed information about the data inside?

Hi there,
Could you share the entire python stack trace to help understand where the error arises? The example config.yaml file is provided here. The nav_graph.yaml is generated by building_map_generator. Typically for RMF deployments, this gets built and installed along when compiling the maps package. For example, building rmf_demos_maps will generate and install the nav_graphs to ~/rmf_demos_ws/install/rmf_demos_maps/share/rmf_demos_maps/maps/office/nav_graphs/

Here is the trace:
Starting fleet adapter...
Traceback (most recent call last):
File "/home/ubuntu/ros2_ws/install/fleet_adapter_template/lib/fleet_adapter_template/fleet_adapter", line 11, in
load_entry_point('fleet-adapter-template==0.0.0', 'console_scripts', 'fleet_adapter')()
File "/home/ubuntu/ros2_ws/install/fleet_adapter_template/lib/python3.8/site-packages/fleet_adapter_template/fleet_adapter.py", line 239, in main
adapter, fleet_handle, robots = initialize_fleet(
File "/home/ubuntu/ros2_ws/install/fleet_adapter_template/lib/python3.8/site-packages/fleet_adapter_template/fleet_adapter.py", line 80, in initialize_fleet
nav_graph = graph.parse_graph(nav_graph_path, vehicle_traits)
RuntimeError: operator[] call on a scalar
I'm using the traffic editor to generate de nav_graph.yaml.

It was my mistake, i was using the file .building.yaml instead of the file .yaml that comes from building map_generator. So the  flow to build nav_map is the next?

Generate a map using traffic-editor and generate building_map_path
ros2 run rmf_building_map_tools building_map_generator nav
${building_map_path} ${output_nav_graphs_dir}
Use the output file in the template

Is it correct?

Yes, that would be the right approach 👍🏼


Conda Package

Many people use conda instead of pip to create Python virtual environments.
Many Sphinx projects already have Conda package.  It would make it much easier to install this using Conda if a Conda recipe was contributed at conda-forge by following the contribution instructions.

Hello !
I'm not a conda user so while I'm ok doing a package, I won't be the best person to test it or make sure it keeps working. Do you want to be the contact for conda-related issues in the future ?

Yeah

The rest will happen there: https://github.com/pulls?q=is%3Apr+is%3Aopen+author%3A%40me+archived%3Afalse+sort%3Aupdated-desc

Shall we close ?

Shall we close ?

Sounds good.  👍


To Do list: add & remove

Removed hardcoded items from the tasks array.
Created app.js for new functionality.
Implement a function for adding a new task.
Implement a function for deleting a task.
Implement a function for editing task descriptions.
All changes are saved in local storage.

Hi @didierganthier  , thanks for your feedback!
I've worked on fixing your observations on the right branch
Please let me know if everything is ok by now. 😄


update download links to apache distros

Description
This PR updates the download links to use the Apache distro servers.

Thanks for your contribution @aaronmarkham
@mxnet-label-bot[pr-awaiting-merge]


Number of comments given by user X for "Reviewed pull request"

Description:
Would like to see the possibility to track and/or filter on comments for pullrequests. Comments user made regardless if it's their own PR or others.
Feature request:

Number of comments given by user X for "Reviewed pull request"

Optional request:

Eliminate duplicate code check-ins (for example, merging same code into different branches)

Yeah, I've often hand-rolled VSTS API queries for "comments on other developer's PRs" to see which developers are contributing to our pull-request process, even if they're not final approver this is helpful activity information.

I'd love to see that too!

Would like to see this kind of information too.
@Pxtl I'm interested in your workaround... do you have any information how and where to build such query?


Handle cases where content-type is not exactly application/json

Fixes https://github.com/StackStorm/st2web/issues/981

Our production Nginx configuration has set charset utf-8; making Content-Type header to be application/json; charset=utf-8, not just application/json.
@stackstorm/module-api compares headers['content-type'] to be exactly application/json.

Some comments about the request function:

It seems like it's been migrated from st2client.js
@key10 and I reviewed it and it seems like there is an opportunity to improve it

Some possible improvements/questions:

Should raw return the data without doing any JSON.parse? If so, then transformResponse should not be used.
On line 234, body is assigned data. Assuming data is a string at this moment, body is not a pointer of data, but rather a copy. Then, the changes done on body on lines 244-248 (for parsing JSON) are superfluous, since the function is returning data.
Line 232 could be done before 229, and not have to repeat defaulting to {} on both 229 and 230.

Let us know about those comments/questions and we can apply changes as needed.

@amanda11 @armab
I'd appreciate if you can check this one out when you have a chance.
Thank you

think I've found the problem with st2web, and I'm looking at a PR to fix.

@luislobo If you can merge in latest master this should hopefully build ok now.

Sure, will do.

Seems like tests passed now :)


The internal Cypress web server responded with > 404: Not Found

This perhaps may be a general understanding problem.
(i run the tests locally in cmd under Windows (working directory the root dir of the app))
I run the tests via:
docker run -v %cd%:/e2e -w /e2e cypress/included:10.3.0
this is my cypress.config.ts file:
import { defineConfig } from "cypress";
import { environment } from "src/environments/environment.prod";

export default defineConfig({
  e2e: {
    // baseUrl: 'http://localhost:4200',
    setupNodeEvents(on, config) {
      // implement node event listeners here
    },
    specPattern: "cypress/e2e/*.cy.{js,jsx,ts,tsx}"
  },
  env: {
    apiUrl: environment.apiUrl,
    pass: 'FuSoNic!'
  },
  "reporter": "cypress-multi-reporters",
  "reporterOptions": {
    "reporterEnabled": "cypress-mochawesome-reporter, mocha-junit-reporter",
    "cypressMochawesomeReporterReporterOptions": {
      "reportDir": "cypress/reports",
      "charts": true,
      "reportPageTitle": "My Test Suite",
      "embeddedScreenshots": true,
      "inlineAssets": true
    },
    "mochaJunitReporterReporterOptions": {
      "mochaFile": "cypress/reports/junit/results-[hash].xml"
    }
  },
  "video": false
});

the output I get is:
The internal Cypress web server responded with > 404: Not Found
Question:
Does this error appear because the app is not running?
Do we actually need to start the app? Or does the cypress docker-container handle this?

@AGuyCoding this error is because the app is not running.


Tentatively work around MSVC compiler bug in CPUID

The noinline is a tentative work-around for what might be a MSVC miscompile.
The symptom is that MSVC builds incorrectly report some CPU features as supported. This only happens for CPU feature bits in the EDX output register, which would make sense if the compiler omitted to save that output register after CPUID instructions.
The other things done in this PR are:

Use memcpy for proper bit-casting, don't just cast uint32_t to int and back: that is UB when not in int range, which happens concretely here with compile-time constant values (hence the compiler can actually see that's UB): eax=0x80000000u).
Drop some futile inline keywords.

should we file a bug with MSVC if it isn't already filed ?

This is for now just a theory as I haven't been able to fully make sense of the disassembly.  Let's wait until someone can rerun iree-cpuinfo on Windows on one of the 7950x boxes where it used to incorrectly report amx- features. If that's fixed then we can reasonably infer that it was indeed a MSVC bug, since the most likely effective change here is that __declspec(noinline), and if that does have an effect then it confirms the compiler-bug theory.


Long press is too aggressive

Several times while testing, while trying to tap a link, I triggered the 'Link copied to clipboard' function which prevented me from navigating to the link.
We should probably relax the duration a bit.  Wondering what others feel about this. @ishammahajan ?

The timeout set on long pressing the link is the same as long pressing the header, or any message (500ms). That seems like enough time to me for the user to tap on it (if he doesn't want to long press it). This experience might have been a bug if clicking on it leads to a long press. If it is, would you please detail how to reproduce it? (I don't think it is but there might be a chance).
If it's not, I don't think 500ms is a short time, personally. I think it's worth checking if other users have also faced this problem though.

I feel like in my anecdotal experience, most apps do a significantly longer longpress timeout than 500ms.

@timabbott @borisyankov the material design page has a video showing a long-press. If we extract the video and look at it frame by frame, the time used in that is 650ms. However, the default timeout for onLongPress is 500ms https://stackoverflow.com/questions/1930895/how-long-is-the-event-onlongpress-in-the-android. I'm not sure which timing to follow, any thoughts?

the time used in that is 650ms

FWIW, I think that was slightly long just for demonstration purposes.

I did a bit of googling a few days ago (don't have links handy), and there's a lot of sites/questions/etc. around increasing the timeout on Android, so I'm pretty sure the default of 500ms is not known to be an ideal choice.

I searched a bit, and yes there seems to be a large amount of people who want an increased timeout. My point in this case was that people would be used to a 500ms timeout since all of Google's apps use the same. It would surely be increased if our users found it hard to properly click on elements of the UI.

might have been a bug

I suggested that because when I was working on related code, in the process of refactoring the logic I had accidentally triggered a bug where repeatedly clicking on an element triggered the longpress on it. There might be a similar bug in master right now, which is why I was concerned.
I don't know what timing to change it to though, how about material.io's 650ms?

the material design page has a video showing a long-press. If we extract the video and look at it frame by frame, the time used in that is 650ms.

Awesome, thanks for that detailed investigation :smile:
Another data point: the default on iOS looks to also be 500ms:
https://developer.apple.com/documentation/uikit/uilongpressgesturerecognizer/1616423-minimumpressduration
Other things I learn from a bit of googling:

There's a system setting for this, under Settings > Accessibility: https://support.google.com/accessibility/android/answer/6006989?hl=en

The default seems to be "Short", based on checking in an emulator -- so some people will have gone in there to make it longer.
We should probably respect that choice. If we want we could make ours longer... but when the user's increased it in system settings we should increase accordingly.
Here's where that is in the Android SDK: https://developer.android.com/reference/android/view/ViewConfiguration.html#getLongPressTimeout()
Not sure if it's handy in RN somewhere, but won't be hard to expose ourselves if needed.

Those settings are said to correspond to 500ms, 1000ms, and 1500ms: https://www.xda-developers.com/how-to-reduce-the-long-press-delay-beyond-its-lowest-setting/ Also that page describes a hilarious way to choose another value as a user, if e.g. 500ms is too slow for you.
Oh actually the truth seems to be 400ms, 1000ms, 1500ms ! See source: https://android.googlesource.com/platform/packages/apps/Settings.git/+/06dfd7566/res/values/arrays.xml#731

Helpful info here: https://stackoverflow.com/questions/1930895/how-long-is-the-event-onlongpress-in-the-android

... Hmm, but on that last SO question, some people say the long-press time is in addition to the normal-press time. That would affect things. Not sure exactly how long that is.

Hmm, but on that last SO question, some people say the long-press time is in addition to the normal-press time. That would affect things. Not sure exactly how long that is.

Hmm, that's slightly confusing. My assumption was that just like click_event docs on MDN, the short press only fired when both a mousedown and a mouseup is detected.

click fires after both the mousedown and mouseup events have fired, in that order.

If you go into the docs link provided by another answer in the same SO question, and search for getTapTimeout, it tells you that the tap timeout is

the duration in milliseconds we will wait to see if a touch event is a tap or a scroll. If the user does not move within this interval, it is considered to be a tap.

So I created an android application to test this out, fairly simple code, just to import the library and call

Log.d("test", "onClick: " + ViewConfiguration.getTapTimeout());

Turns out the timeout is 100ms.

test: onClick: 100

So the 400ms seems to check out (if you consider tap + long press = long press timeout to be true), since the total is 500ms now.
I think getting the native long press timeout and setting that seems to be the best way to solve this problem. I found no way to get this though, even asking on SO didn't yield anything, so not sure how to solve things.


Feature Request: Clock Divider Spread

Hi Jerry,
a feature request for the next versions of Clock Divider: Clock Spread, for example for the usual musical divisions 1,2,3,4,6,8,12,16,32 etc.... or better CV controllable, of course :-)

easy peasy.  I also make it easy to create your own if you do any development, in SynthDevKit


Autosolve reserved model suffix

Currently the Data, Resource and Collection are served for Resource, so the codegen should change the name of that model is not a Resource.

dup with https://github.com/Azure/azure-sdk-for-net/issues/28948


Bitcoin Cash potentially lost after deposit address conversion with https://cashaddr.bitcoincash.org/

*** Edit *** The problem is resolved - it was my mistake.
The URL (https://cashaddr.bitcoincash.org/) was supplied by the Trezor wallet interface and I input my Binance Bitcoin Cash deposit address.
The input address: 1HrdSCp6PfHtjthMQcZCB6BN3Wy6z8QA59
The output given was: qzuwfncx5asl7lr0t9ts3fr6z26dp0dszqydl4tdex
I don't believe that I've deposited Bitcoin Cash to my Binace account before but the above CashAddr has various other transactions.

Damn it...  I see my error.  I need new glasses.  I copied the donation address from the conversion page and unintentionally sent my Bitcoin Cash to it.  Could whoever owns that address contact me at<EMAIL_ADDRESS>

I'm not sure I understand the issue.  The output given is the correct conversation.  Were you able to get your funds back from Binance?


Will there be any issue if the firebase is configured on both iOS and dart side.

Hello,
I'm trying to setup rich notifications on iOS. Because I need metrics on delivered and opened. According to docs, I need to make native side changes. but I'm confused on one thing, we already have firebase messaging as our push provider and we initiate the firebase on dart side + requesting notification permissions on dart side. but the docs mentioned, to add these code
 // Configure Firebase
     FirebaseApp.configure()

     // in case, you haven't asked for permissions
     let authOptions: UNAuthorizationOptions = [.alert, .badge, .sound] // Options: .alert, .badge, .sound
     UNUserNotificationCenter.current().requestAuthorization(options: authOptions, completionHandler: {

         (granted, error) in

         if granted {
             // Register after we get the permissions.
             UNUserNotificationCenter.current().delegate = self
         }
     })

     // Set FCM messaging delegate
     Messaging.messaging().delegate = self

     // You should register for remote push when the app starts.
     UIApplication.shared.registerForRemoteNotifications()

I'm confused on why this is needed, since I already do this on dart side,

Will implementing this break my existing push notifications handlers from Firebase messaging
Is this the only way to get delivered and opened metrics on customer.io

Great question! Thanks for asking.
When using our Flutter SDK today, there is some native code that is required. However, because you mentioned that you already have Firebase setup using dart, you may not need all of the native code.
While following the push setup instructions for our Flutter SDK, be sure to follow all of the instructions, including all of the native code setup. This includes the AppDelegate instructions and creating a new target in Xcode and adding the NotificationService class.
The only part that you could modify is FCM device token registration.
You can try to remove this native code from your app:
 func application(
     _ application: UIApplication,
     didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]? = nil
 ) -> Bool {
     FirebaseApp.configure() // <-- remove this

     Messaging.messaging().delegate = self // <-- remove this
   }

// Remove this entire `extension AppDelegate: MessagingDelegate` block
 extension AppDelegate: MessagingDelegate {
   func messaging(_ messaging: Messaging, didReceiveRegistrationToken fcmToken: String?) {
     MessagingPush.shared.messaging(messaging, didReceiveRegistrationToken: fcmToken)
   }
 }
//

Then, in your dart code, when the Firebase SDK provides a device token to your app, send that device token to the CustomerIO Flutter SDK:
CustomerIO.registerDeviceToken(deviceToken: '<device token provided by Firebase SDK>')

All of the other native code is required to enable features such as opened and delivered push metrics.
This native code should not interfere with the dart Firebase SDK. Yes, the native code is the only way today to enable push metrics in a Flutter app.

@levibostian thanks I did tried what you mentioned with few modification to the code from the docs.

Updated my iOS minimum deployment target to 14 as the pod's minimum deployment target was 14

had to add use_frameworks! in
target 'NotificationServiceExtention' do
use_frameworks!
pod 'CustomerIO/MessagingPushFCM', '~> 2.7.4'
end

Now I get this error. I guess flavors are messing with the rich notifications setup.
Error (Xcode): Cycle inside Runner; building could produce unreliable results.
Cycle details:
→ Target 'Runner': CodeSign /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app
○ That command depends on command in Target 'Runner': script phase “[CP] Embed Pods Frameworks”
○ That command depends on command in Target 'Runner': script phase “Copy GoogleServices.Plist depending on flavor”
○ That command depends on command in Target 'Runner': script phase “Thin Binary”
○ Target 'Runner' has process command with output '/Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/Info.plist'
○ Target 'Runner' has copy command from '/Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/NotificationServiceExtention.appex' to '/Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/PlugIns/NotificationServiceExtention.appex'

Raw dependency cycle trace:

target:  ->

node: <all> ->

command: <all> ->

node: /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/_CodeSignature ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug-staging:CodeSign /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app ->

node: /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/Frameworks/Alamofire.framework/ ->

directoryTreeSignature: � ->

directoryContents: /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/Frameworks/Alamofire.framework ->

node: /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/Frameworks/Alamofire.framework ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug-staging:PhaseScriptExecution [CP] Embed Pods Frameworks /Users/Gokul/Library/Developer/Xcode/DerivedData/Runner-awnrwydsjbkumjewxzhtrvyqttwm/Build/Intermediates.noindex/Runner.build/Debug-staging-iphonesimulator/Runner.build/Script-DF6C8D67CA4379C61BADF79D.sh ->

node: /Users/Gokul/Library/Developer/Xcode/DerivedData/Runner-awnrwydsjbkumjewxzhtrvyqttwm/Build/Intermediates.noindex/Runner.build/Debug-staging-iphonesimulator/Runner.build/InputFileList-DF6C8D67CA4379C61BADF79D-Pods-Runner-frameworks-Debug-staging-input-files-b1fff4ece98ae9a5785cb17be7e36d0f-resolved.xcfilelist ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug-staging:WriteAuxiliaryFile /Users/Gokul/Library/Developer/Xcode/DerivedData/Runner-awnrwydsjbkumjewxzhtrvyqttwm/Build/Intermediates.noindex/Runner.build/Debug-staging-iphonesimulator/Runner.build/InputFileList-DF6C8D67CA4379C61BADF79D-Pods-Runner-frameworks-Debug-staging-input-files-b1fff4ece98ae9a5785cb17be7e36d0f-resolved.xcfilelist ->

CYCLE POINT ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase5-copy-googleservices-plist-depending-on-flavor> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase5-copy-googleservices-plist-depending-on-flavor ->

node: <execute-shell-script-18c1723432283e0cc55f10a6dcfd9e02e959943d87f407fd09b34c83311eb3e6-target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-> ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug-staging:PhaseScriptExecution Copy GoogleServices.Plist depending on flavor /Users/Gokul/Library/Developer/Xcode/DerivedData/Runner-awnrwydsjbkumjewxzhtrvyqttwm/Build/Intermediates.noindex/Runner.build/Debug-staging-iphonesimulator/Runner.build/Script-5593BB0F26D17CDA00A0020C.sh ->

node: /Users/Gokul/Library/Developer/Xcode/DerivedData/Runner-awnrwydsjbkumjewxzhtrvyqttwm/Build/Intermediates.noindex/Runner.build/Debug-staging-iphonesimulator/Runner.build/Script-5593BB0F26D17CDA00A0020C.sh ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug-staging:WriteAuxiliaryFile /Users/Gokul/Library/Developer/Xcode/DerivedData/Runner-awnrwydsjbkumjewxzhtrvyqttwm/Build/Intermediates.noindex/Runner.build/Debug-staging-iphonesimulator/Runner.build/Script-5593BB0F26D17CDA00A0020C.sh ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase4-thin-binary> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase4-thin-binary ->

node: <execute-shell-script-18c1723432283e0cc55f10a6dcfd9e02f1eee2015e8ff5ebcd27678f788c2826-target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-> ->

command: P2:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug-staging:PhaseScriptExecution Thin Binary /Users/Gokul/Library/Developer/Xcode/DerivedData/Runner-awnrwydsjbkumjewxzhtrvyqttwm/Build/Intermediates.noindex/Runner.build/Debug-staging-iphonesimulator/Runner.build/Script-3B06AD1E1E4923F5004D2608.sh ->

node: /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/Info.plist/ ->

directoryTreeSignature: r ->

directoryContents: /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/Info.plist ->

node: /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/Info.plist ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug-staging:ProcessInfoPlistFile /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/Info.plist /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/ios/Runner/Info.plist ->

node: /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/PlugIns/NotificationServiceExtention.appex ->

command: P0:target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49-:Debug-staging:Copy /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/Runner.app/PlugIns/NotificationServiceExtention.appex /Users/Gokul/Downloads/Work Stuff/magnifi-mobile-app/build/ios/Debug-staging-iphonesimulator/NotificationServiceExtention.appex ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase6--cp--embed-pods-frameworks> ->

command: P0:::Gate target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase6--cp--embed-pods-frameworks ->

node: <target-Runner-18c1723432283e0cc55f10a6dcfd9e0288a783a885d8b0b3beb2e9f90bde3f49--fused-phase5-copy-googleservices-plist-depending-on-flavor>

Updated my iOS minimum deployment target to 14 as the pod's minimum deployment target was 14

The Customer.io SDK has a minimum target of 13. What SDK has a minimum target of 14?

had to add use_frameworks! in

This is quite common to add.

Now I get this error.

If I had to guess, coccoapods did not succeed in generating the Xcode workspace.
Could you run the command pod install --repo-update --project-directory=ios in your project and send me the output of running that? It would also be helpful to see the contents of your Podfile.

changed the minimum deployment target to 13.

Logs

 pod install --repo-update --project-directory=ios
❯ pod install --repo-update --project-directory=ios
Updating local specs repositories

CocoaPods 1.12.1 is available.
To update use: `sudo gem install cocoapods`

For more information, see https://blog.cocoapods.org and the CHANGELOG for this version at https://github.com/CocoaPods/CocoaPods/releases/tag/1.12.1

Analyzing dependencies
cloud_firestore: Using Firebase SDK version '10.9.0' defined in 'firebase_core'
firebase_analytics: Using Firebase SDK version '10.9.0' defined in 'firebase_core'
firebase_core: Using Firebase SDK version '10.9.0' defined in 'firebase_core'
firebase_dynamic_links: Using Firebase SDK version '10.9.0' defined in 'firebase_core'
firebase_messaging: Using Firebase SDK version '10.9.0' defined in 'firebase_core'
firebase_performance: Using Firebase SDK version '10.9.0' defined in 'firebase_core'
Downloading dependencies
Installing Alamofire (4.9.1)
Installing Amplitude (8.17.1)
Installing Analytics (4.1.6)
Installing AnalyticsConnector (1.0.1)
Installing AppAuth (1.6.2)
Installing AppsFlyerFramework (6.9.1)
Installing BoringSSL-GRPC (0.0.24)
Installing CryptoSwift (1.7.1)
Installing CustomerIO (2.7.7)
Installing CustomerIOCommon (2.7.7)
Installing CustomerIOMessagingInApp (2.7.7)
Installing CustomerIOMessagingPush (2.7.7)
Installing CustomerIOMessagingPushFCM (2.7.7)
Installing CustomerIOTracking (2.7.7)
Installing FBAEMKit (15.1.0)
Installing FBAudienceNetwork (6.14.0)
Installing FBSDKCoreKit (15.1.0)
Installing FBSDKCoreKit_Basics (15.1.0)
Installing FMDB (2.7.5)
Installing Firebase (10.9.0)
Installing FirebaseABTesting (10.13.0)
Installing FirebaseAnalytics (10.9.0)
Installing FirebaseCore (10.9.0)
Installing FirebaseCoreExtension (10.13.0)
Installing FirebaseCoreInternal (10.13.0)
Installing FirebaseDynamicLinks (10.9.0)
Installing FirebaseFirestore (10.9.0)
Installing FirebaseInstallations (10.13.0)
Installing FirebaseMessaging (10.9.0)
Installing FirebasePerformance (10.9.0)
Installing FirebaseRemoteConfig (10.13.0)
Installing FirebaseSessions (10.13.0)
Installing Flutter (1.0.0)
Installing GTMAppAuth (1.3.1)
Installing GTMSessionFetcher (2.3.0)
Installing GoogleAppMeasurement (10.9.0)
Installing GoogleDataTransport (9.2.5)
Installing GoogleSignIn (6.2.4)
Installing GoogleUtilities (7.11.5)
Installing IOSSecuritySuite (1.9.9)
Installing Libuv-gRPC (0.0.10)
Installing OktaAuthFoundation (1.4.2)
Installing OktaAuthSdk (2.4.3)
Installing OktaIdx (3.0.9)
Installing Plaid (4.2.0)
Installing PromisesObjC (2.3.1)
Installing PromisesSwift (2.3.1)
Installing PurchasesHybridCommon (5.2.3)
Installing ReachabilitySwift (5.0.0)
Installing RevenueCat (4.23.1)
Installing Segment-Amplitude (3.3.2)
Installing Sentry (8.7.2)
Installing SentryPrivate (8.7.2)
Installing Try (2.1.1)
Installing abseil (1.20211102.0)
Installing app_links (0.0.1)
Installing app_tracking_transparency (0.0.1)
Installing appsflyer_sdk (6.8.0)
Installing cloud_firestore (4.7.1)
Installing connectivity_plus (0.0.1)
Installing customer_io (1.2.3)
Installing device_info_plus (0.0.1)
Installing facebook_app_events (0.0.1)
Installing firebase_analytics (10.4.1)
Installing firebase_core (2.13.0)
Installing firebase_dynamic_links (5.0.17)
Installing firebase_messaging (14.3.0)
Installing firebase_performance (0.9.0-16)
Installing flutter_jailbreak_detection (1.0.0)
Installing flutter_keyboard_visibility (0.0.1)
Installing flutter_secure_storage (6.0.0)
Installing flutter_segment (3.12.1)
Installing gRPC-C++ (1.44.0)
Installing gRPC-Core (1.44.0)
Installing gallery_saver (0.0.1)
Installing google_sign_in_ios (0.0.1)
Installing http_certificate_pinning (1.0.3)
Installing image_picker_ios (0.0.1)
Installing launch_review (0.0.1)
Installing leveldb-library (1.22.2)
Installing local_auth_ios (0.0.1)
Installing nanopb (2.30909.0)
Installing okta_idx_flutter (0.0.1)
Installing open_filex (0.0.2)
Installing package_info_plus (0.4.5)
Installing path_provider_foundation (0.0.1)
Installing permission_handler_apple (9.0.4)
Installing plaid_flutter (0.0.1)
Installing purchases_flutter (5.2.2)
Installing quick_actions_ios (0.0.1)
Installing segment-appsflyer-ios (6.9.1)
Installing sentry_flutter (0.0.1)
Installing shared_preferences_foundation (0.0.1)
Installing sign_in_with_apple (0.0.1)
Installing speech_to_text (0.0.1)
Installing sqflite (0.0.2)
Installing syncfusion_flutter_pdfviewer (0.0.1)
Installing uni_links (0.0.1)
Installing url_launcher_ios (0.0.1)
Installing webview_flutter_wkwebview (0.0.1)
Generating Pods project
Integrating client project
Pod installation complete! There are 42 dependencies from the Podfile and 100 total pods installed.

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.debug-prod.xcconfig` or include the `Target Support Files/Pods-Runner/Pods-Runner.debug-prod.xcconfig` in your build configuration (`Flutter/Debug.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.debug-staging.xcconfig` or include the `Target Support Files/Pods-Runner/Pods-Runner.debug-staging.xcconfig` in your build configuration (`Flutter/Debug.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.release-prod.xcconfig` or include the `Target Support Files/Pods-Runner/Pods-Runner.release-prod.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.release-staging.xcconfig` or include the `Target Support Files/Pods-Runner/Pods-Runner.release-staging.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.profile-prod.xcconfig` or include the `Target Support Files/Pods-Runner/Pods-Runner.profile-prod.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

[!] CocoaPods did not set the base configuration of your project because your project already has a custom config set. In order for CocoaPods integration to work at all, please either set the base configurations of the target `Runner` to `Target Support Files/Pods-Runner/Pods-Runner.profile-staging.xcconfig` or include the `Target Support Files/Pods-Runner/Pods-Runner.profile-staging.xcconfig` in your build configuration (`Flutter/Release.xcconfig`).

[!] The `Runner [Debug-prod]` target overrides the `ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES` build setting defined in `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug-prod.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `Runner [Debug-staging]` target overrides the `ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES` build setting defined in `Pods/Target Support Files/Pods-Runner/Pods-Runner.debug-staging.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `Runner [Release-prod]` target overrides the `ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES` build setting defined in `Pods/Target Support Files/Pods-Runner/Pods-Runner.release-prod.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `Runner [Release-staging]` target overrides the `ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES` build setting defined in `Pods/Target Support Files/Pods-Runner/Pods-Runner.release-staging.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `Runner [Profile-prod]` target overrides the `ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES` build setting defined in `Pods/Target Support Files/Pods-Runner/Pods-Runner.profile-prod.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `Runner [Profile-staging]` target overrides the `ALWAYS_EMBED_SWIFT_STANDARD_LIBRARIES` build setting defined in `Pods/Target Support Files/Pods-Runner/Pods-Runner.profile-staging.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `NotificationServiceExtention [Debug-prod]` target overrides the `CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER` build setting defined in `Pods/Target Support Files/Pods-NotificationServiceExtention/Pods-NotificationServiceExtention.debug-prod.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `NotificationServiceExtention [Debug-staging]` target overrides the `CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER` build setting defined in `Pods/Target Support Files/Pods-NotificationServiceExtention/Pods-NotificationServiceExtention.debug-staging.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `NotificationServiceExtention [Release-prod]` target overrides the `CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER` build setting defined in `Pods/Target Support Files/Pods-NotificationServiceExtention/Pods-NotificationServiceExtention.release-prod.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `NotificationServiceExtention [Release-staging]` target overrides the `CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER` build setting defined in `Pods/Target Support Files/Pods-NotificationServiceExtention/Pods-NotificationServiceExtention.release-staging.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `NotificationServiceExtention [Profile-prod]` target overrides the `CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER` build setting defined in `Pods/Target Support Files/Pods-NotificationServiceExtention/Pods-NotificationServiceExtention.profile-prod.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

[!] The `NotificationServiceExtention [Profile-staging]` target overrides the `CLANG_WARN_QUOTED_INCLUDE_IN_FRAMEWORK_HEADER` build setting defined in `Pods/Target Support Files/Pods-NotificationServiceExtention/Pods-NotificationServiceExtention.profile-staging.xcconfig'. This can lead to problems with the CocoaPods installation
    - Use the `$(inherited)` flag, or
    - Remove the build settings from the target.

 PodFile
# Uncomment this line to define a global platform for your project
platform :ios, '13.0'

# CocoaPods analytics sends network stats synchronously affecting flutter build latency.
ENV['COCOAPODS_DISABLE_STATS'] = 'true'

project 'Runner', {
  'Debug' => :debug,
  'Profile' => :release,
  'Release' => :release,
}

def flutter_root
  generated_xcode_build_settings_path = File.expand_path(File.join('..', 'Flutter', 'Generated.xcconfig'), __FILE__)
  unless File.exist?(generated_xcode_build_settings_path)
    raise "#{generated_xcode_build_settings_path} must exist. If you're running pod install manually, make sure flutter pub get is executed first"
  end

  File.foreach(generated_xcode_build_settings_path) do |line|
    matches = line.match(/FLUTTER_ROOT\=(.*)/)
    return matches[1].strip if matches
  end
  raise "FLUTTER_ROOT not found in #{generated_xcode_build_settings_path}. Try deleting Generated.xcconfig, then run flutter pub get"
end

require File.expand_path(File.join('packages', 'flutter_tools', 'bin', 'podhelper'), flutter_root)

flutter_ios_podfile_setup

target 'Runner' do
  use_frameworks!
  use_modular_headers!
  pod 'CustomerIO/MessagingPushFCM', '~> 2.7.4'
  flutter_install_all_ios_pods File.dirname(File.realpath(__FILE__))
end

 target 'NotificationServiceExtention' do
   use_frameworks!
   pod 'CustomerIO/MessagingPushFCM', '~> 2.7.4'
 end
post_install do |installer|
  installer.pods_project.targets.each do |target|
   flutter_additional_ios_build_settings(target)
   target.build_configurations.each do |config|
      if target.respond_to?(:product_type) and target.product_type == "com.apple.product-type.bundle"
        target.build_configurations.each do |config|
            config.build_settings['CODE_SIGNING_ALLOWED'] = 'NO'
        end
      end
    config.build_settings['IPHONEOS_DEPLOYMENT_TARGET'] = '14.0'
    config.build_settings['GCC_PREPROCESSOR_DEFINITIONS'] ||= [
            '$(inherited)',
        'PERMISSION_CAMERA=1',
    ]
   end
  end
 end

Thanks for that information. That's very helpful.
Looking at the Podfile you sent, this file seems similar to the Podfile of our sample Flutter app. Therefore, I do not believe that Podfile is causing this issue for you.
Could you provide more details what steps that you're taking to reproduce this issue? What steps are you taking or commands you're running to get to the error Error (Xcode):?

No actually, after making all the changes outlined above and the docs. When I try to run the app, the build get failed with the above xcode error.

Sure @levibostian.

the error looks like conflict between flavors and the native implementation of customer.io. Nothing wrong with the package, Closing this issue for now, Wil reopen If needed.


Some builders raise runtime errors

digitalme builder
ERRORED   (Executed in 2015.11645 seconds)

  File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/usr/lib/python3.6/unittest/case.py", line 605, in run
    testMethod()
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/test/builder/test02_apps.py", line 19, in test001_digitalme
    j.builders.apps.digitalme.build(reset=True)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 162, in wrapper_action
    res = self.apply_method(func, kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 93, in apply_method
    return func(**kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/apps/BuilderDigitalME.py", line 37, in build
    j.builders.runtimes.lua.build()  # will build openresty & lua & openssl
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 162, in wrapper_action
    res = self.apply_method(func, kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 93, in apply_method
    return func(**kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/runtimes/BuilderLua.py", line 40, in build
    self.lua_rocks_install()
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/runtimes/BuilderLua.py", line 123, in lua_rocks_install
    self.lua_rock_install(line)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/runtimes/BuilderLua.py", line 49, in lua_rock_install
    self._execute(C)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 375, in _execute
    showout=showout,
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/sal/process/SystemProcess.py", line 103, in execute
    replace=replace,
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/core/InstallTools.py", line 1175, in execute
    raise RuntimeError(msg)

Could not execute: 'bash /tmp/builders/lua/builder_lua.sh'stdout:
    Installing https://luarocks.org/lua-path-0.3.1-1.src.rock

stderr:
    + cd /tmp/builders/lua
    + . /tmp/builders/lua/env.sh
    ++ export LIBRARY_PATH=/lib/x86_64-linux-gnu:/lib:/usr/local/lib:/usr/lib
    ++ LIBRARY_PATH=/lib/x86_64-linux-gnu:/lib:/usr/local/lib:/usr/lib
    ++ export LD_LIBRARY_PATH=/lib/x86_64-linux-gnu:/lib:/usr/local/lib:/usr/lib
    ++ LD_LIBRARY_PATH=/lib/x86_64-linux-gnu:/lib:/usr/local/lib:/usr/lib
    ++ export 'LDFLAGS=-L/lib/x86_64-linux-gnu -L/lib -L/usr/local/lib -L/usr/lib'
    ++ LDFLAGS='-L/lib/x86_64-linux-gnu -L/lib -L/usr/local/lib -L/usr/lib'
    ++ export CPPPATH=/usr/include
    ++ CPPPATH=/usr/include
    ++ export CPPFLAGS=-I/usr/include
    ++ CPPFLAGS=-I/usr/include
    ++ export PS1=PYTHONBUILDENV:
    ++ PS1=PYTHONBUILDENV:
    ++ export PYTHONHTTPSVERIFY=0
    ++ PYTHONHTTPSVERIFY=0
    ++ export LC_ALL=en_US.UTF-8
    ++ LC_ALL=en_US.UTF-8
    ++ export LANG=en_US.UTF-8
    ++ LANG=en_US.UTF-8
    + luarocks install lua-path
    Warning: The directory '/root/.cache/luarocks' or its parent directory is not owned by the current user and the cache has been disabled. Please check the permissions and owner of
        that directory. If executing /tmp/builders/lua/luarocks/src/bin/luarocks with sudo, you may want sudo's -H flag.

    Error: Could not fetch rock file: Error fetching file: Failed downloading https://luarocks.org/lua-path-0.3.1-1.src.rock - lua-path-0.3.1-1.src.rock

ardb builder
ERRORED   (Executed in 11.85391 seconds)

  File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/usr/lib/python3.6/unittest/case.py", line 605, in run
    testMethod()
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/test/builder/test07_db.py", line 71, in test004_ardb
    j.builders.db.ardb.build(reset=True)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 162, in wrapper_action
    res = self.apply_method(func, kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 93, in apply_method
    return func(**kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/db/BuilderARDB.py", line 23, in build
    self.build_forest_db()
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/db/BuilderARDB.py", line 75, in build_forest_db
    self._execute(C)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 375, in _execute
    showout=showout,
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/sal/process/SystemProcess.py", line 103, in execute
    replace=replace,
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/core/InstallTools.py", line 1175, in execute
    raise RuntimeError(msg)

Could not execute:    bash /tmp/builders/ardb-server/builder_ardb.sh

stderr:
    + cd /tmp/builders/ardb-server/github/couchbase/forestdb
    + mkdir build
    + cd build
    + cmake ../
    CMake Error: Could not find CMAKE_ROOT !!!
    CMake has most likely not been installed correctly.
    Modules directory not found in
    /sandbox/share/cmake-3.15
    CMake Error: Error executing cmake::LoadCache(). Aborting.

influxdb builder
ERRORED   (Executed in 1.71842 seconds)

  File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/usr/lib/python3.6/unittest/case.py", line 605, in run
    testMethod()
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/test/builder/test07_db.py", line 105, in test006_influx
    j.builders.db.influxdb.build(reset=True)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 162, in wrapper_action
    res = self.apply_method(func, kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 93, in apply_method
    return func(**kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/db/BuilderInfluxdb.py", line 18, in build
    self.system.package.install(["npm", "bzr"])
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 162, in wrapper_action
    res = self.apply_method(func, kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 93, in apply_method
    return func(**kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderSystemPackage.py", line 169, in install
    self.install(package)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 162, in wrapper_action
    res = self.apply_method(func, kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 93, in apply_method
    return func(**kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderSystemPackage.py", line 166, in install
    self._execute(cmd)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 375, in _execute
    showout=showout,
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/sal/process/SystemProcess.py", line 103, in execute
    replace=replace,
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/core/InstallTools.py", line 1175, in execute
    raise RuntimeError(msg)

Could not execute: 'bash /sandbox/builder_systempackage.sh'stdout:
    Reading package lists...
    Building dependency tree...
    Reading state information...
    Some packages could not be installed. This may mean that you have
    requested an impossible situation or if you are using the unstable
    distribution that some required packages have not yet been created
    or been moved out of Incoming.
    The following information may help to resolve the situation:

    The following packages have unmet dependencies:
     npm : Depends: node-gyp (>= 0.10.9) but it is not going to be installed

stderr:
    + cd /sandbox
    + . /sandbox/env.sh
    ++ export LC_ALL=en_US.UTF-8
    ++ LC_ALL=en_US.UTF-8
    ++ export LUALIB=/sandbox/openresty/lualib
    ++ LUALIB=/sandbox/openresty/lualib
    ++ export LANG=en_US.UTF-8
    ++ LANG=en_US.UTF-8
    ++ export 'LUA_PATH=?.lua;/sandbox/openresty/lualib/?/init.lua;/sandbox/openresty/lualib/?.lua;/sandbox/openresty/lualib/?/?.lua;/sandbox/openresty/lualib/?/core.lua;/sandbox/openr
        esty/lapis/?.lua'
    ++ LUA_PATH='?.lua;/sandbox/openresty/lualib/?/init.lua;/sandbox/openresty/lualib/?.lua;/sandbox/openresty/lualib/?/?.lua;/sandbox/openresty/lualib/?/core.lua;/sandbox/openresty/la
        pis/?.lua'
    ++ export PBASE=/sandbox
    ++ PBASE=/sandbox
    ++ export 'LUA_CPATH=/sandbox/openresty/lualib/?.so;./?.so'
    ++ LUA_CPATH='/sandbox/openresty/lualib/?.so;./?.so'
    ++ export GOPATH=/sandbox/go_proj
    ++ GOPATH=/sandbox/go_proj
    ++ export PYTHONHTTPSVERIFY=0
    ++ PYTHONHTTPSVERIFY=0
    ++ export HOME=/root
    ++ HOME=/root
    ++ export GOROOT=/sandbox/go
    ++ GOROOT=/sandbox/go
    ++ export HOST=c9dbf9aaad91
    ++ HOST=c9dbf9aaad91
    ++ export DEBIAN_FRONTEND=noninteractive
    ++ DEBIAN_FRONTEND=noninteractive
    ++ export PYTHONPATH=/sandbox/lib:/sandbox/lib/jumpscale:/sandbox/lib/jumpscale
    ++ PYTHONPATH=/sandbox/lib:/sandbox/lib/jumpscale:/sandbox/lib/jumpscale
    ++ export PATH=/sandbox/go/bin:/sandbox/go_proj/bin:/sandbox/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
    ++ PATH=/sandbox/go/bin:/sandbox/go_proj/bin:/sandbox/bin:/bin:/sbin:/usr/bin:/usr/sbin:/usr/local/bin:/usr/local/sbin
    ++ export 'PS1=3BOTDEVEL:c9dbf9aaad91:\W: '
    ++ PS1='3BOTDEVEL:c9dbf9aaad91:\W: '
    ++ export LAPIS_OPENRESTY=/sandbox/bin/openresty
    ++ LAPIS_OPENRESTY=/sandbox/bin/openresty
    + apt-get install npm -y
    E: Unable to correct problems, you have held broken packages.

syncthing builder
ERRORED   (Executed in 99.68607 seconds)

  File "/usr/lib/python3.6/unittest/case.py", line 59, in testPartExecutor
    yield
  File "/usr/lib/python3.6/unittest/case.py", line 605, in run
    testMethod()
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/test/builder/test08_storage.py", line 36, in test002_syncthing
    j.builders.storage.syncthing.build(reset=True)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 162, in wrapper_action
    res = self.apply_method(func, kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 93, in apply_method
    return func(**kwargs)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/storage/BuilderSyncthing.py", line 33, in build
    self._execute("cd %s && go run build.go" % self.package_path)
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/builder/system/BuilderBaseClass.py", line 375, in _execute
    showout=showout,
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/sal/process/SystemProcess.py", line 103, in execute
    replace=replace,
  File "/sandbox/code/github/threefoldtech/jumpscaleX/Jumpscale/core/InstallTools.py", line 1175, in execute
    raise RuntimeError(msg)

Could not execute:    bash /tmp/builders/syncthing/builder_syncthing.sh

stderr:

The first error is mostly a network issue.

influxdb error is caused by a system broken package; try install/reinstall libssl1.0-dev

ran ardb in a fresh container works ok


Update software.yml

Added Bitwig Studio.

Hello, thank you for this, do we have by chance a list of opcodes supported by Bitwig?

Thanks for the update! I heard back from Bitwig and these are the supported opcode:
alternate
default_path
end
group_label
hikey
hivel
key
lokey
loop_continuous
loop_crossfade
loop_end
loop_mode
loop_start
loop_sustain
loop_type
loopcrossfade
loopend
loopmode
loopstart
looptype
lovel
offset
pitch_keycenter
pitch_keytrack
region_label
sample
transpose
tune
volume
xfin_hikey
xfin_hivel
xfin_lokey
xfin_lovel
xfout_hikey
xfout_hivel
xfout_lovel

Thank you!

This is great. I went through the release notes of Bitwig for all major versions since version 3.3 (released 26 Nov 2020) up to 5.0.11, so that we have an update since the last post (only regarding the opcodes). The unmentioned versions up to 5.0.11 did not have any changes.
Bitwig 4.0 - Bitwig 4.0.8:

SFZ import: The seq_length opcode is now imported as Round-robin [26609]

Bitwig 4.1 - Bitwig 4.1.6:

Any region using seq_position imports as Round-robin


Re-apply Parallax on Window Resize

Hi,
I have a parallax set for larger screens with the following code:
    // PARALLAX VARS - IMAGES
    var largeScreenParallax = new Rellax('.parallax-large-screen', {
        speed: 2,
        center: true,
        wrapper: null,
        round: true,
        vertical: true,
        horizontal: false
    });

On small screen sizes I have removed it with the destroy() method.
    // REMOVE PARALLAX CLASS
    function removeParallaxClass() {
        if (window.innerWidth < 981) {
            largeScreenParallax.destroy();
        }
    }
    removeParallaxClass()
    addEventListener("resize", removeParallaxClass, false)

However I can't work out how to re-add the parallax when the window is resized back up again?
I thought this would work, by adding the refresh() method, but it doesn't:
    // RE-ADD PARALLAX ON WINDOW RESIZE IF DESTROYED ABOVE
    function reAddParallaxClass() {
        if (window.innerWidth > 980) {
            largeScreenParallax.refresh();
        }
    }
    reAddParallaxClass()
    addEventListener("resize", reAddParallaxClass, false)

When you've removed a parallax on smaller window sizes, how do you re-add/re-set it for when the window is re-sized back up again?
Many thanks,
Paul.

I'm having a similar problem, there seems to be an open pull request that may relate to this issue.


Rustup

Tendril::as_byte_slice is unchanged, but moved to be next to Tendril<Bytes>::deref_mut which is very similar.
r? @Ms2ger
@metajack Could you set up homu on this repository?

@bors-servo: r+


Add CI to detect public API changes in Swift

Update Danger to turn on GitHub public tag
Generate a report in PR for public API changes

Both of these are likely using DocC to get the API docs

Update: DocC likely isn't necessary for this.
# Generate symbol graphs from Swift Package manifest. From the root of the repo:
mkdir -p .build/symbol-graphs
swift build --target FirebaseMLModelDownloader -Xswiftc -emit-symbol-graph -Xswiftc -emit-symbol-graph-dir -Xswiftc .build/symbol-graphs

A JSON file will exist at .build/symbol-graphs/FirebaseMLModelDownloader.symbols.json that contains the API surface.

@yifanyang Please take a look at this issue

Fixed by @sunmou99


AVLTree isn't working as expected

Just try insert in the order 1, 3, 2 and notice that tree isn't balancing itself

I tried. To me it looks correct.  Why do you think AVL tree is not balancing?
1 is root then 3 goes to right. Then 2 goes to 3s left. So now tree is unbalanced from 1s perspective so we do right rotation at 3 to make 2 root and 3 as its right child and then we do left rotation at 1 to make 2 as root and 1 as left and 3 as right child.

When I run with 3 nodes it doesn't balances
For example insert 1, 2, 3
   1
    \
     \
     2
      \
      3

When 1, 2, 3, 4 is inserted then output tree is like this (which balances it self)
   2
  / \
 /   \
 1   3
      \
      4

it never like below
1
2
3
it is   2    if you look at preorder and inorder traversal.
1   3

Preorder traversal of tree is 2 1 3. Which means 2 is root 1 is left and 3 is right child. Look at the preorder traversal in the output.
It is never 1 2 3 as you are saying.

Sorry , my bad.
The issue occurred because of some of my changes in the code.
Thanks for the prompt reply.


chore: Bump CLI to ^5.0.1

Summary
Upgrade RN CLI to stable 5.0.1. The biggest thing it fixes is selecting device/simulator on Xcode 12.5.
Targeting 0.64-stable branch, as master is on v6 already. cc @kelset @grabbou
Release notes: https://github.com/react-native-community/cli/releases/tag/v5.0.1
Changelog

[General] [Fix] - Bump CLI to ^5.0.1
Test Plan

@thymikee Do you have any insight to the circleci failures?

@lunaleaps not quite. This would need a rebase to be sure

Do we still need this PR? It's against the 64 branch, does it mean that we need to do a new patch release for 64?

Technically this CLI bump is within the semver range, I don't have a strong opinion here.

Have there been raised issues with 12.5 for 0.64? I guess we can merge this regardless and if someone wants to drive a patch release, then sure?
What do you guys think @kelset, @thymikee? Just trying to get a resolution on this PR.

@lunaleaps around Xcode 12.5 you can find more info here -> https://github.com/facebook/react-native/issues/31480
I don't have strong feelings either for a new patch release for 0.64; there was some folks that wanted it https://github.com/react-native-community/releases/issues/232 so maybe we merge this then do a 0.64 patch as a "pairing experience" to teach you/some FB folks on the process in a learn by doing fashion?

From discussion on https://github.com/react-native-community/releases/issues/232, we won't be releasing a 0.64 patch. cc @kelset
Closing this for now, please re-open with concerns


Pipeline Output - Opening Child Item opens same child item type for all objects on the pipeline output

Describe the Issue
When multiple parent objects in the Pipeline output share the SAME sub child types, opening one child item will open all other items of the same type.
To Reproduce
Script Sample
$Services = Get-Service
$Services | ForEach-Object{
    Write-Output $_
}

Run Script
Open the Pipeline output
Expand a parent item (service)
Expand child item (DependentSerivces)
Notices this expands for ALL objects on the pipeline
Output is also null - Is this a bug ?

Screenshots

Resolved. We need to make sure we have a key property set on our objects so the table knows they are unique. The dependent services are just empty in your example. If you expand some of the ServicesDependOn properties you'll see they have items.


upstream: Add support for sharing alt-svc entries between hosts.

Add a "canonical suffix" list to the Alt-Svc cache so that Alt-Svc entries can be shared across origins which share the same hostname suffix.
Signed-off-by: Ryan Hamilton<EMAIL_ADDRESS>Risk Level: Low
Testing: New unit tests
Docs Changes: Update proto docs
Release Notes: Updated

/assign @alyssawilk


How to use ng-message with the directive?

In angular material the input element and ng-messages are wrapped with md-input-container to show error messages properly. As the md-input-container is already included in the directive i can't see a way to include the ng-messages part in there.
What would be the correct way to show an error message?

I don't think there is a proper way to show error messages for now. I take a look at it, and try to implement similar solution to what md-datepicker offers. By the way, which attributes do you want to support ngMessages? I think about min-date, max-date, required and valid.

Thanks. In my case i only needed required, but min-date, max-date and valid seem also reasonable.

I've added support for ngMesages. If you think the problem solved, please close the issue.

Thank you!


BBCode is parsed inside [code]

From @pafcu on December 7, 2014 14:14
When writing posts, bbcode inside [code] blocks is still parsed normally. No parsing should be done inside [code] blocks.
Copied from original issue: friendica/red#725

@pafcu This issue is closed because Redmatrix evolved into Hubzilla. When this is still an issue in the most recent version of Hubzilla, please recreate this issue over there. We're sorry for any inconvenience this will maybe give you.


Make DisplayText Non-Mandatory for Various Forms.

Description
This PR is for making field DisplayText Non-Mandatory for Various Forms mentioned in issue #6855.
This PR...

Types of changes

[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] New feature (non-breaking change which adds functionality)
[ ] Bug fix (non-breaking change which fixes an issue)
[X] Enhancement (improves an existing feature and functionality)
[ ] Cleanup (Code refactoring and cleanup, that may add test cases)

Feature/Enhancement Scale or Bug Severity
Feature/Enhancement Scale

[ ] Major
[X ] Minor

Bug Severity

[ ] BLOCKER
[ ] Critical
[ ] Major
[X ] Minor
[ ] Trivial

Screenshots (if appropriate):
How Has This Been Tested?

Tested on local environment and unit Tests.

@blueorangutan package

@DaanHoogland a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan package

@DaanHoogland a Jenkins job has been kicked to build packages. It will be bundled with  KVM, XenServer and VMware SystemVM templates. I'll keep you posted as I make progress.

@blueorangutan test

@DaanHoogland a Trillian-Jenkins test job (centos7 mgmt + kvm-centos7) has been kicked to run smoke tests

Trillian test result (tid-6354)
Environment: kvm-centos7 (x2), Advanced Networking with Mgmt server 7
Total time taken: 43587 seconds
Marvin logs: https://github.com/blueorangutan/acs-prs/releases/download/trillian/pr7180-t6354-kvm-centos7.zip
Smoke tests completed. 108 look OK, 0 have errors, 0 did not run
Only failed and skipped tests results shown below:

Test
Result
Time (s)
Test File


Improve error messages

This pull request uses .......^ to indicate the location of errors within SQL statements.
Below is an example:
[ksp] SQL validation error: The expression evaluation was failed. The parameter "unknown" is not found at [unknown]:7. Available parameters are: [id, street, version]. at [
insert into address
    (address_id, street, version)
values
    (/* id */0, /* unknown */'', /* version */0)
............................^
returning
    address_id, street, version
]:4:29.

This is great when logging locally, but when logging to something like Grafana Loki on a production cluster, multi-line logs are recorded by default as one log line per line... so word wrap could mess up the .....^ indications... (apart from being printed backwards by default, since you want to view the most recent logs first...). I usually keep the logs printed in production on one line for that reason...

@dave08  Thank you for your feedback.
I have modified the code to indicate the error location using >>> and <<<.
[ksp] SQL validation error: The expression evaluation was failed. The parameter "unknown" is not found at [unknown]:0..7. Available parameters are: [id, street, version]. at [
insert into address
    (address_id, street, version)
values
    (/* id */0, >>>/* unknown */<<<'', /* version */0)
returning
    address_id, street, version
]:4:16..29.

What do you think about this?

@dave08 I've  improved error messages further.
[ksp] SQL validation error: The expression evaluation failed. The parameter "unknown" is not found at [unknown]:1:1. Available parameters are: [id, street, version]. at [
insert into address
    (address_id, street, version)
values
    (/* id */0, >>>/* unknown */<<<'', /* version */0)
returning
    address_id, street, version
]:4:17.

1:1 indicates that there is an issue at line 1, column 1. Similarly, 4:17 indicates a problem at line 4, column 17.


[minor]The Kryo of Hudi conflicts with the Kryo of Flink

Change Logs
Describe context and summary for this change. Highlight if any code was copied.
Impact
Describe any public API or user-facing feature change or any performance impact.
Risk level: none | low | medium | high
Choose one. If medium or high, explain what verification was done to mitigate the risks.
Contributor's checklist

[ ] Read through contributor's guide
[ ] Change Logs and Impact were stated clearly
[ ] Adequate tests were added if applicable
[ ] CI passed

@cuibo01 @danny0405 do you still plan to land this?

@cuibo01 @danny0405 do you still plan to land this?

Let's not land this until we clarify what exactly caused the conflict. https://github.com/apache/hudi/pull/6522#discussion_r1014118759

@danny0405 do you know if this is still an issue on master and in the recent Hudi releases?

I didn't see any reports about it in recent releases.

I didn't see any reports about it in recent releases.

Got it.  Closing this stale PR now.


Racecard fixes for missing data

I've noticed the Racecard data from BetFair can be more than a little flimsy, so I've added a few more real responses, which have a load of data missing, and fixes in the parser to cope with it.

Coverage remained the same at 92.278% when pulling 4d5fca34b9989f347da99d662c869472c205cb16 on seaders:master into 49692b0e03851cd3bfd8e5fe4666d42cf687a0fc on liampauling:master.


Streamline provisioning UI: add floating IP dropdown, SSH key upload

@skanthed does this required the updated esi sdk code? if so, can you link that PR here?

@skanthed does this required the updated esi sdk code? if so, can you link that PR here?

yes -  https://github.com/CCI-MOC/esisdk/pull/11

Just converting this to WIP because an esisdk change will have to be merged and packaged first.


Add a sample numpy image getter

It would be nice to have a handy function that one can call like so:
from rsbox import ml
img = ml.get_img()

which would return some canonical image that you can use to test various functions.

For example, a 128x128 image would be good.

Use something like:
from PIL import Image
import requests
url = 'http://images.cocodataset.org/test-stuff2017/000000027833.jpg'
img = Image.open(requests.get(url, stream=True).raw)

Added.