Is it necessary for environment name in database.yml?

I encountered this exception ActiveRecord::AdapterNotSpecified: 'development' database is not configured. Available: ["default", "development_master", "development_slave"] If I configure like the following.
In database.yml:
default: &default
  adapter: postgresql
  encoding: unicode
  pool: 5
  username: testapp
  password: testapp
  database: testapp_development

development_master:
  <<: *default
  host: <IP_ADDRESS>

development_slave:
  <<: *default
  host: <IP_ADDRESS>

In initializer:
 SwitchPoint.configure do |config|
   config.define_switch_point :db1,
     readonly: :"#{Rails.env}_slave",
     writable: :"#{Rails.env}_master"
 end

That's fine If I configure like the following.
In database.yml:
default: &default
  adapter: postgresql
  encoding: unicode
  pool: 5
  username: testapp
  password: testapp
  database: testapp_development

development:
  <<: *default
  host: <IP_ADDRESS>

development_slave:
  <<: *default
  host: <IP_ADDRESS>

In initializer:
 SwitchPoint.configure do |config|
   config.define_switch_point :db1,
     readonly: :"#{Rails.env}_slave",
     writable: :"#{Rails.env}"
 end

So is it necessary for environment name(like development, production and test) in database.yml?

switch_point doesn't require "development" configuration, but your Rails app might require it because "development" is the default configuration for ActiveRecord::Base connection.
Could you paste the backtrace of ActiveRecord::AdapterNotSpecified ? If the backtrace contains switch_point, it might be a bug of switch_point.

I'm using Rails 5.1.3, Ruby 2.4.1 and PostgreSQL 9.6.3
This is the backtrace. It seems that the backtrace doesn't contain switch_point. Rails must require development.
$ bin/rake db:create --trace
Running via Spring preloader in process 4588
** Invoke db:create (first_time)
** Invoke db:load_config (first_time)
** Execute db:load_config
** Execute db:create
rake aborted!
ActiveRecord::AdapterNotSpecified: 'development' database is not configured. Available: ["default", "development_master", "development_slave"]
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activerecord-5.1.3/lib/active_record/connection_adapters/connection_specification.rb:246:in `resolve_symbol_connection'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activerecord-5.1.3/lib/active_record/connection_adapters/connection_specification.rb:227:in `resolve_connection'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activerecord-5.1.3/lib/active_record/connection_adapters/connection_specification.rb:141:in `resolve'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activerecord-5.1.3/lib/active_record/connection_handling.rb:55:in `establish_connection'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activerecord-5.1.3/lib/active_record/tasks/database_tasks.rb:139:in `create_current'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activerecord-5.1.3/lib/active_record/railties/databases.rake:27:in `block (2 levels) in <top (required)>'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/task.rb:250:in `block in execute'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/task.rb:250:in `each'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/task.rb:250:in `execute'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/task.rb:194:in `block in invoke_with_call_chain'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/2.4.0/monitor.rb:214:in `mon_synchronize'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/task.rb:187:in `invoke_with_call_chain'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/task.rb:180:in `invoke'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:152:in `invoke_task'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:108:in `block (2 levels) in top_level'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:108:in `each'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:108:in `block in top_level'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:117:in `run_with_threads'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:102:in `top_level'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:80:in `block in run'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:178:in `standard_exception_handling'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/rake-12.0.0/lib/rake/application.rb:77:in `run'
/vagrant/testapp/bin/rake:9:in `<top (required)>'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:286:in `load'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:286:in `block in load'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:258:in `load_dependency'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/gems/2.4.0/gems/activesupport-5.1.3/lib/active_support/dependencies.rb:286:in `load'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/home/vagrant/.rbenv/versions/2.4.1/lib/ruby/2.4.0/rubygems/core_ext/kernel_require.rb:55:in `require'
-e:1:in `<main>'
Tasks: TOP => db:create

That's your app's issue.
I recommend using readonly: :"#{Rails.env}_slave", writable: :"#{Rails.env}" style as you mentioned in the issue description.
switch_point itself doesn't require Rails.env connection, but Rails uses Rails.env connection by default in some cases.

I see. Thank you.


Poetry run make html returning FileNotFoundError

Hi,
at the end of ch11 when executing poetry run make html I'm getting this error:
FileNotFoundError

 [WinError 2] Nie można odnaleźć określonego pliku

 at ~\AppData\Local\Programs\Python\Python38\lib\subprocess.py:1307 in _execute_child
     1303│             sys.audit("subprocess.Popen", executable, args, cwd, env)
     1304│
     1305│             # Start the process
     1306│             try:
   → 1307│                 hp, ht, pid, tid = _winapi.CreateProcess(executable, args,
     1308│                                          # no special security
     1309│                                          None, None,
     1310│                                          int(not close_fds),
     1311│                                          creationflags,

I was trying to fix this issue on my own but I ran out of ideas
You can find my repository with uptimer here

Hi Łukasz,
It seems like poetry is having some problems with make command under Windows. You can use the following command as a workaround that will run the sphinx-build command directly:
sphinx-build -b html source build

Here is an explanation of what is does, but in a nutshell, make html should call sphinx-build under the hood (which in your case doesn't happen). Sorry for the trouble.


Improve performance

We are still a bit behind better-sqlite3. For example, there's more overhead in get():
penberg@vonneumann libsql-js % node perf/perf-libsql.js

cpu: Apple M1
runtime: node v18.19.0 (arm64-darwin)

benchmark      time (avg)             (min … max)       p75       p99      p999
------------------------------------------------- -----------------------------
• Statement
------------------------------------------------- -----------------------------
get(1)      1'969 ns/iter   (1'911 ns … 2'539 ns)  1'970 ns  2'424 ns  2'539 ns

summary for Statement
  get(1)

penberg@vonneumann libsql-js % node perf/perf-better-sqlite3.js
cpu: Apple M1
runtime: node v18.19.0 (arm64-darwin)

benchmark      time (avg)             (min … max)       p75       p99      p999
------------------------------------------------- -----------------------------
• Statement
------------------------------------------------- -----------------------------
get(1)        587 ns/iter     (555 ns … 1'122 ns)    584 ns    944 ns  1'122 ns

The assumption that a lot of this is memory memory allocations and copies as values are passed between the C, Rust, and JavaScirpt layers. We also suspect that Neon Bindings may be less efficient than better-sqlite3 is which seems to hook into the V8 APIs directly.
Let's improve the benchmarks, profile, and fix performance to be on-par with better-sqlite3.

This would be great; think there is most every feature I want here in replacing and improving on better-sqlite3 (once extension support in 0.40 lands), except performance.


Update CI/CD GHA scripts.

Issue #: https://github.com/bcgov/entity/issues/4997
Description of changes:

Update CI/CD github action scripts and update github secrets;

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of the bcrs-entities-create-ui license (Apache 2.0).

If any OS config has changed, will you update the JSON/param files in the GH project accordingly (so we can rebuild via script if needed).


Permissions for(role)

Please describe the changes this PR makes and why it should be merged:
Allows role resolveables to be passed to permissionsFor() to check the resolved permissions for a given role after channel overwrites. (also adds a resolveRole method to the client data resolver, and cleans up a second instance where duplicate code existed)
Semantic versioning classification:

[x] This PR changes the library's interface (methods or parameters added)
[ ] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)
[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

iirc there is no typedef for RoleResolvable. There are also other instances (GuildMember role stuff) where the resolveRole method could be used for consistency.

a shitload of code is duplicated in those the if/else can you reuse some code plz ❤

Perhaps I am missing what you are seeing? But I see no code that can be reused... Given the way permissions must be applied to resolve correctly that is.

Perhaps I am missing what you are seeing? But I see no code that can be reused... Given the way permissions must be applied to resolve correctly that is.

I think there is always an @everyone overwrite and assuming that's true, one way to do it is the following:

Make an array with guild id for @everyone overwrite
If role is provided, push role id to array. If member is provided, push member id and role ids to array.
Iterate through array and do the bitwise operators.

This might be a little shorter.

That is specifically what you cannot do. Permissions must be applied in a specific manner according to https://support.discordapp.com/hc/en-us/articles/206141927-How-is-the-permission-hierarchy-structured- That was how it permissionsFor was coded before an earlier pr of mine, and it caused incorrect permission resolution in several edge cases.


Tasklist bug

When looking for print it duplicates the keyword.
When looking for print( everything works correctly...

Did occur when using strip-comment-symbols = 1 in .gitviper/config because it was printing #1


Make bridge more stable or implement protection so tokens get returned back if bridge is down

Hello, there were a request from Russain-speaking community that Kristof noted and asked to translate to him:

he says
" Dear developers, your bridge to Binance chain is regularly going down and when tokens are sent they just got stuck in the bridge. Please please modify it so it returns tokens back if it does not work since you are putting tokens owner in a bad position, token price is moving and not frozen. Please let's be respectful to each other"
I've informed that this request was passed directly to Kristof.
Can we do something about it?

https://github.com/threefoldfoundation/tft/issues/138

The bridge is more stable now and if there are still stability issues, we need to address them.


Hide last scene if background is transparent

Version

react-native-router-flux v1.0.3
react-native v0.39

Expected behaviour
Do not show last scene behind new one if there is no background or if it is transparent, without poping the last scene from navigation stack.
If you have a background image that you want to be shown on all of your scenes, but you want to define it before the Router.
If it is defined init the scene there is background overlapping on animation transition.
<View style={{ flex: 1 }}>

...

Styles for Router:
flex: 1,
backgroundColor: 'transparent',
shadowColor: null,
shadowOffset: null,
shadowOpacity: null,
shadowRadius: null,

I've got using custom animationStyle function. But i've got issue with handling POP/PUSH animation.
Have issue:
SCENE1 -(vertical)-> SCENE2 -(horizontal)-> SCENE3
So if I set correct animation for VERTICAL - i'm getting it vertical even for POP from Scene 3 to Scene 2.. but there should be horizontal...


Add support for Prometheus Operator's ServiceMonitor resource

What changes were proposed in this pull request?

add support for ServiceMonitor resource which is provided by prometheus-operator

How was this patch tested?
helm upgrade/install on a testing cluster, k8s v1.11.8, prometheus-operator-4.3.3 chart

It looks like @tczekajlo hasn't signed our Contributor License Agreement, yet.

The purpose of a CLA is to ensure that the guardian of a project's outputs has the necessary ownership or grants of rights over all contributions to allow them to distribute under the chosen licence.
Wikipedia

You can read and sign our full Contributor License Agreement here.
Once you've signed reply with [clabot:check] to prove it.
Appreciation of efforts,
clabot

[clabot:check]

@confluentinc It looks like @tczekajlo just signed our Contributor License Agreement. :+1:
Always at your service,
clabot

Could you update the docs also

@qshao-pivotal I've updated docs. I hope this is the correct place.

This looks super helpful and ready to go, with documentation updates in place. Any reason why it hasn't been merged?

  Error: unable to build kubernetes objects from release manifest: error validating "": error validating data: ValidationError(Service.spec.ports[0].port): invalid type for io.k8s.api.core.v1.ServicePort.port: got "string", expected "integer"
  Error: plugin "diff" exited with error

I get this when running through helmfile

Any reason for this to still not be merged? Seems like the checks failed becaus of server maintenance, could we retry the checks?


Transparent background for banner gameURL

This PR

Fixes a bug

Describe the changes below:
Use transparent background for banner gameURL to support different browser color themes.
Currently, when using a dark theme for the dev console, both the background and the text are white.

👍

👍


Weird behavior when using port ranges

Cookbook version
2.15.2
Chef-client version
12.18.31
Platform Details
Debian Jessie 4.8.15-2~bpo8+2
Scenario:
I'm trying to create a new container running ProFTPd accepting connections passive mode.
The container should bind ports 50000-50010 to the same ports on the host.
I use this port config option:
port ['20:20', '21:21', '50000-50010:50000-50010']
Steps to Reproduce:
As the issue has nothing todo with ProFTPD, it can reproduced with a simple alpine container:
docker_container 'test' do
  repo 'alpine'
  tag 'latest'
  port ['20:20', '21:21', '50000-50010:50000-50010']
  command 'tail -f /dev/null'
  kill_after 3
  action :run
end

Expected Result:
docker ps output regarding ports:
<IP_ADDRESS>:20-21->20-21/tcp,
<IP_ADDRESS>:50000-50010->50000-50010/tcp

Actual Result:
<IP_ADDRESS>:20-21->20-21/tcp,
<IP_ADDRESS>:50005->50005/tcp,
<IP_ADDRESS>:50010->50000/tcp,
<IP_ADDRESS>:50009->50001/tcp,
<IP_ADDRESS>:50008->50002/tcp,
<IP_ADDRESS>:50007->50003/tcp,
<IP_ADDRESS>:50006->50004/tcp,
<IP_ADDRESS>:50004->50006/tcp,
<IP_ADDRESS>:50003->50007/tcp,
<IP_ADDRESS>:50002->50008/tcp,
<IP_ADDRESS>:50001->50009/tcp,
<IP_ADDRESS>:50000->50010/tcp

The ports in the container are not bound to their corresponding ports on the host. Only port 50005 is bound correctly.

I ran into this as well. This is what I did:
...
port ['21:21', '990:990'] + (10090..10100).collect { |p| "#{p}:#{p}" }
...


Grey space after Icon

Hey, great plugin! I'm having a little problem where the space inbetween the icon and the label has a grey background. This is probably some colour setting, but I've no idea what to set to change it. Any ideas?
Thanks!

I've seen something like this going on in #52 as well.
Can you try to see if setting the follows has any effect on the color:
let g:webdevicons_conceal_nerdtree_brackets = 0

It might be helpful to debug that specific column: http://vim.wikia.com/wiki/Identify_the_syntax_highlighting_group_used_at_the_cursor
If you can send or show your vimrc I can also try to replicate
Thanks

So the brackets thing removed the colour and I ended up with this.

Using that link you gave me, the cursor says...
hi<hideBracketsInNerdTree> trans<hideBracketsInNerdTree> lo<hideBracketsInNerdTree>
That mean anything to you?
My vimrc is here.
Thanks for helping!

No problem. There is definitely something going on here. I guess for now that is a workaround but I feel like this is very much solvable (either by me or someone else).
The output doesn't mean too much to me yet but definitely seems to have to do with the custom bracket hide syntax.
Thanks for the vimrc link, I will see what I can do to replicate and hopefully fix.

@stuartmemo can you tell me if it is the same regardless of vim or gvim ? And which are the screenshots from?
Sorry but also can you tell me the exact font you are using?
I tested with your vimrc even after installing the same plugins. I tested with Droid Sans patched and Droid Sans (true Mono) patched and could not replicate :disappointed:

@stuartmemo My bad! I just got this issue. I was only doing PluginInstall instead of PluginUpdate so when updated to version 4.0.2 I can now see the issue!

I had a few hunches and I think I have a fix for this but not really 100% sure why it fixes it
Changing this:
autocmd FileType nerdtree syntax match hideBracketsInNerdTree "\]" contained conceal cchar=  containedin=ALL

to:
autocmd FileType nerdtree syntax match hideBracketsInNerdTree "\]" contained conceal containedin=ALL

seems to solve the issue. From what I understand though not explicitly setting the cchar sets it to a space by default

Ah, amazing! That worked a treat.
The icons are quite tight with the text though now, it was quite nice having a bit more space. I know, never happy :frog:

@stuartmemo

Great to know it worked for you as well.

About the tightness that is actually configurable :wink:

Per the readme:
the amount of space to use after the glyph character (default ' ')
let g:WebDevIconsNerdTreeAfterGlyphPadding = '  '

@ryanoasis You rule the school. Thank you so much.

Hi,
I'm having the same bug. It is caused by Conceal highlighting in the color scheme.
Adding
hi Conceal guibg=NONE

To vimrc solves the issue.

@kristijanhusak Thanks, yeah I believe the autocmd change will fix it. Just to confirm did the autocmd change I posted work for you?
If not I will at least add your fix as a possibility on the readme.

@ryanoasis Yes, autocmd works for me, and as i said, it's better solution because of colors with cursorline.
You could add it if you want as an alternative solution, if autocmd does not work for someone.

fixed/completed with latest release


Modify Delete command

As a user, I can delete a specific patient’s details from the app so that I can remove patients that are no longer relevant or needed.

No change needed for Delete command


Add retained message

Implement retained messages via kv store

#70

please fix travis ci

Codecov Report

Merging #118 (3ed037e) into main (aba2165) will decrease coverage by 1.45%.
The diff coverage is 32.87%.

@@            Coverage Diff             @@
##             main     #118      +/-   ##
==========================================
- Coverage   45.54%   44.09%   -1.46%
==========================================
  Files         106      109       +3
  Lines        4514     4887     +373
  Branches      673      726      +53
==========================================
+ Hits         2056     2155      +99
- Misses       2104     2371     +267
- Partials      354      361       +7

Impacted Files
Coverage Δ

...g/apache/rocketmq/mqtt/common/model/Constants.java
0.00% <ø> (ø)

...rg/apache/rocketmq/mqtt/cs/session/QueueFresh.java
90.00% <ø> (ø)

...ketmq/mqtt/ds/meta/RetainedPersistManagerImpl.java
3.33% <3.33%> (ø)

...cs/protocol/mqtt/handler/MqttSubscribeHandler.java
42.70% <4.08%> (-40.97%)
:arrow_down:

...e/rocketmq/mqtt/ds/store/LmqQueueStoreManager.java
51.85% <41.17%> (+0.68%)
:arrow_up:

...q/mqtt/ds/upstream/processor/PublishProcessor.java
66.66% <47.36%> (-33.34%)
:arrow_down:

...che/rocketmq/mqtt/cs/session/infly/PushAction.java
57.57% <57.14%> (-0.32%)
:arrow_down:

...va/org/apache/rocketmq/mqtt/common/model/Trie.java
81.62% <73.91%> (-4.71%)
:arrow_down:

...org/apache/rocketmq/mqtt/common/model/Message.java
74.46% <88.88%> (+1.21%)
:arrow_up:

...org/apache/rocketmq/mqtt/common/util/TrieUtil.java
93.75% <93.75%> (ø)

... and 5 more

Continue to review full report at Codecov.

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

add some unit tests

The KV will be removed and the code can be submitted to the Develop branch based on the state machine

close due to #131.


fix(dropdown): Calculate tabwidth (and auto height) in componentDidRender()-method

Description says it all.
How to test
Open the react project in the sandbox. Reload the page and make sure the tabs are of equal width.

Oh! Don't forget to LINK first, to actually try it out in the react sandbox.

Might I suggest that we add a cursor:no-drop to the :hover on the disabled tabs, to correspond with the style of the disabled buttons. But we might need to check that with design first?

@AlbinFarstun  - I think the name of PR is misleading, I guess it is about "inline-tabs".

Got the linking to work now and it looks great!
Would be nice if we could add the cursor:not-allowed on the disabled tabs and have the style not be inline. But that could be a future PR.


Playback issue, playback info resets to previous value

Playback info is getting reset to previous value when setting the value in onActivityResult().
In my use case, I have 2 activities, one of them having a feed containing videos and other being the full screen video activity. When returning back from full screen to the feed, I want to save the playback info of the video. I am doing this in onActivityResult().
The problem is that the value gets rewritten to the old state, from tmpStates when onWindowVisibilityChanged is called for Container.java, which is after onActivityResult().
Am I using it the wrong way?
If yes, whats the right to achieve this.
If no, what is the workaround for this.
Thanks in advance.

@prat-z How you save and restore the PlaybackInfo using onActivityResult()? The tmpStates should do nothing related to the Activity I think.

@eneim I am calling the method savePlaybackInfo() of Container class in onActivityResult().
The onWindowVisibilityChanged method of Container is called after that, which resets my change.

@eneim Yes, orientation change is happening in my case. The orientation of the next screen is fixed to Landscape, without setting flags 'configChange'.

@prat-z I see, so switching to full-screen = the App will switch to landscape mode? And if user turn off full-screen, does your app go back to portrait? Or it stays in landscape mode from there? Can you double check my CustomLayoutActivity demo? Of can you give a few lines of code of your Activity or Fragment where you start the full-screen? Especially the way you use onActivityResult. Will take some time on this asap.


⚠ Bofrost.fr has degraded performance

In 3d4bdc3, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 1390 ms

Resolved: Bofrost.fr performance has improved in 0b4beb2 after 28 minutes.


feat: allow hive sql to be provided as config

Summary of Changes
This pr is to fix https://github.com/lyft/amundsen/issues/552 which allows user to provide hive metastore sql.
Tests
yes. add a unit test to test the new config.
Documentation
What documentation did you add or modify and why? Add any relevant links then remove this line
CheckList
Make sure you have checked all steps below to ensure a timely review.

[ ] PR title addresses the issue accurately and concisely. Example: "Updates the version of Flask to v1.0.2"

In case you are adding a dependency, check if the license complies with the ASF 3rd Party License Policy.

[ ] PR includes a summary of changes.
[ ] PR adds unit tests, updates existing unit tests, OR documents why no test additions or modifications are needed.
[ ] In case of new functionality, my PR adds documentation that describes how to use it.

All the public functions and the classes in the PR contain docstrings that explain what it does

[ ] PR passes make test

Codecov Report

Merging #312 into master will decrease coverage by 0.27%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #312      +/-   ##
==========================================
- Coverage   74.30%   74.03%   -0.28%
==========================================
  Files         105      105
  Lines        4492     4494       +2
  Branches      419      396      -23
==========================================
- Hits         3338     3327      -11
- Misses       1049     1053       +4
- Partials      105      114       +9

Impacted Files
Coverage Δ

...builder/extractor/hive_table_metadata_extractor.py
94.33% <100.00%> (+0.22%)
:arrow_up:

databuilder/loader/file_system_neo4j_csv_loader.py
83.33% <0.00%> (-5.96%)
:arrow_down:

...ilder/transformer/regex_str_replace_transformer.py
92.85% <0.00%> (-3.58%)
:arrow_down:

...tabuilder/extractor/postgres_metadata_extractor.py
93.54% <0.00%> (-1.62%)
:arrow_down:

...abuilder/extractor/snowflake_metadata_extractor.py
93.75% <0.00%> (-1.57%)
:arrow_down:

databuilder/extractor/mssql_metadata_extractor.py
94.02% <0.00%> (-1.50%)
:arrow_down:

...tor/dashboard/redash/redash_dashboard_extractor.py
91.50% <0.00%> (-0.95%)
:arrow_down:

databuilder/publisher/neo4j_csv_publisher.py
83.49% <0.00%> (-0.95%)
:arrow_down:

databuilder/task/neo4j_staleness_removal_task.py
84.16% <0.00%> (-0.84%)
:arrow_down:

Continue to review full report at Codecov.

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


Where is the MessageForwardingService?

I use the custom activity, but when I override onNewIntent , I couldn't found the MessageForwardingService. It's not in the reference.

Docs are here: https://firebase.google.com/docs/cloud-messaging/cpp/client#custom_message_handling_on_android
The MessageForwardingService isn't in the reference since it only responds to an Intent there isn't really a function level API surface.
If you're looking for the AAR / JAR to build your activity library against, it's distributed in firebase-messaging-unity.srcaar - it's actually just a plain aar - which is copied / renamed into Plugins/Android/ when the Android Resolver runs so that it can be built as part of your final APK.

@ShonnVR haven't heard from you so I'll assume your problem is resolved, please ping this issue if it isn't.


How to access AWX databases when in a Docker installation

I have AWX installed via Docker. So there's a separate postgres container. Being sort of unfamiliar with Docker and Postgres, how do I configure awx-migrate-wrapper to connect to the postgres container?

If you're using the Ansible playbooks that the AWX project supplies you with, you can also publish those ports by adjusting the docker-compose.yaml.j2 template or by adjusting the Ansible playbook itself, depending on your version of AWX:
In versions 2.1.0 and 3.0.1 (and probably other earlier versions as well) - Edit the local_docker/tasks/standalone.yaml file to include published_ports for the postgres container task:
- name: Activate postgres container
  docker_container:
    name: postgres
    state: started
    restart_policy: unless-stopped
    published_ports:
      - 5432:5432
    image: "{{ postgresql_image }}"
    volumes:
      - "{{ postgres_data_dir }}:/var/lib/postgresql/data:Z"

In version 4.0.0 and other later versions (I've only been playing with 4.0.0 lately) - Edit the local_docker/templates/docker-compose.yml.j2 file to add a port publishing argument:
  {% if pg_hostname is not defined %}
  postgres:
    image: postgres:9.6
    container_name: awx_postgres
    restart: unless-stopped
    volumes:
      - {{ postgres_data_dir }}:/var/lib/postgresql/data:Z
    environment:
      POSTGRES_USER: {{ pg_username }}
      POSTGRES_PASSWORD: {{ pg_password }}
      POSTGRES_DB: {{ pg_database }}
      PGDATA: /var/lib/postgresql/data/pgdata
    ports:
      - "5432:5432"
  {% endif %}

Then re-run the playbook to provision the changes to your Docker containers:
sudo ansible-playbook -i installer/inventory installer/install.yml
Once you've done that, you should have published the specified port on the container to the specified port on the host, and the script ought to be able to communicate with the Postgres container then.

I think @se7entyse7en 's blog post about using socat to connect to a container with an unpushed port is brilliant.


Loading of mapping file is failed.

When I open ObfuscarMappingParser and chooses my mapping.txt file it cast this error:
Title: Loading of mapping file is failed.
Description: File: mapping.txt Reason: Unexpected token at 1:0

Preview of my "mapping.txt" file:
Renamed Types:
[CastleExplorer]Lidgren.Network.NetBigInteger -> [CastleExplorer]A.B
{
[CastleExplorer]Lidgren.Network.NetBigInteger::GetByteLength1 -> A
[CastleExplorer]Lidgren.Network.NetBigInteger::MakeMagnitude[3]( [System.Runtime]System.Byte[], [System.Runtime]System.Int32, [System.Runtime]System.Int32 ) -> A
.....

Never mind, solved it by my self. ;)
Enable XML mapping by adding  to Obfuscar configuration file. This is important. Txt mapping files are not supported.


Clarify error for repo-based dependencies when publishing.

Elaborate on the exact error cause and directions on how to resolve it.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. Due to the way GitHub handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks! I do like that from before the message included the url of the source in question as I think that can be useful in tracking this down, perhaps that could still be included? Additionally, could this match what Cargo does for other longer error messages? The general guidelines are:

A summary sentence with no uppercase letter or final punctuation
A newline
A longer summary typically wrapped at 80 chars w/ punctuation

Okay, my plan is to do:
``
crates cannot be published to crates.io with dependencies sourced from a repository
either publish {} as its own crate on crates.io and specify a crates.io
version as a dependency or pull it into this repository and specify it with a
path and version

But I don't see why the repo URL actually helps since the dependency is called out by name. I think that's just extraneous noise that will also be hard to read because it will probably be a long URL.

That message looks good to me! Let's leave the repo URL in there just to be explicit though. Having it on a new line and not intermingled with the message should be ok

I've added the repo URL and ran all relevant tests locally, hopefully this looks good now.

@bors: r+
Thanks!

:pushpin: Commit 450da94 has been approved by alexcrichton

:hourglass: Testing commit 450da94 with merge 25b8457...

:sunny: Test successful - status-appveyor, status-travis
Approved by: alexcrichton
Pushing 25b8457388f4cd4a85d6b2f4f910b693c4ccd965 to master...


add dependency, update README

Summary
This PR adds the deepnightLibs dependency to the haxelib.json file, which should resolve #11 and #12
In the process of making this PR, I ran into an error where I needed to install hlsdl, so I added that to the README.
➜  samples git:(master) ✗ haxe buildAll.hxml
Error: Error: Cannot process [hlsdl]: Library hlsdl is not installed : run 'haxelib install hlsdl'

I can change that part in the README, or take it out of this PR, if that shouldn't be included in here.
Testing
Ran the JS tests, and it returned with a success message
➜  ldtk-haxe-api git:(master) ✗ haxe tests/js.hxml

Success.

Caveats
I've never done Haxe development of any kind, so I have no idea if this is good or right :man_shrugging:

Hello,
Thanks for the PR.
I will only change one thing after merge: the dependency in haxelib.json should be pointing to latest release of deepnightLibs version instead of a specific one :)


Any plans on make it available for paralleled processing like paradigms or even better a turbo version?

Thank you for your contribution on this project. Yet, I can't help wondering if you have any plans on make it available for paralleled processing like paradigms or even better a turbo version.

Yeah, we are planning to do it! Stay tuned :)


fix(sbb-header): fix header shadow on keyboard navigation

Doesn't show the shadow if the header is not in position: fixed.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

:exclamation: No coverage uploaded for pull request base (main@7d768aa). Click here to learn what that means.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #2508   +/-   ##
=======================================
  Coverage        ?   93.66%
=======================================
  Files           ?      298
  Lines           ?    24373
  Branches        ?     2036
=======================================
  Hits            ?    22829
  Misses          ?     1511
  Partials        ?       33

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


KEP-4601: Promote AuthorizeWithSelectors / AuthorizeNodeWithSelectors to beta

Description
Promotes https://github.com/kubernetes/enhancements/issues/4601 to beta
/hold for https://github.com/kubernetes/kubernetes/pull/128168
/sig auth
/cc @deads2k

/approve
/hold cancel
The upstream change has been merged.

/lgtm


Upgrading from 2.0.4 to 2.0.5 causes the application to crash with a SIGSEGV in the JRE

Environment details

Specify the API at the beginning of the title. For example, "BigQuery: ...").
General, Core, and Other are also allowed as types: google-cloud-secretmanager
OS type and version: Alpine Linux base docker image - eclipse-temurin:11-jre-alpine
Java version: OpenJDK Runtime Environment Temurin-11.0.13+8 (11.0.13+8) (build 11.0.13+8)
secretmanager version(s): 2.0.5

Steps to reproduce

Upgrade from 2.0.4 to 2.0.5
Application crashes with a segmentation fault in the JRE

Stack trace
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  SIGSEGV (0xb) at pc=0x0000000000003efe, pid=1, tid=36
#
# JRE version: OpenJDK Runtime Environment Temurin-11.0.13+8 (11.0.13+8) (build 11.0.13+8)
# Java VM: OpenJDK 64-Bit Server VM Temurin-11.0.13+8 (11.0.13+8, mixed mode, tiered, compressed oops, serial gc, linux-amd64)
# Problematic frame:
# C  0x0000000000003efe
#
# Core dump will be written. Default location: /core.%e.1.%t
#
# An error report file with more information is saved as:
# /tmp/hs_err_pid1.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
# The crash happened outside the Java Virtual Machine in native code.
# See problematic frame for where to report the bug.

Hey @lesv - I no longer work on Secret Manager. Sorry

Is there a temporary solution to this.

Any chance you can provide the code that your using to do this?  (without any PII)
Our samples still run, so we aren't seeing the problem you are having.

Changing the Dataproc image version for creating cluster to 2.0-debians from 1.5 solved my problem. This was used for spinning Spark cluster.

Sounds like the issue is solved.

Related to https://github.com/grpc/grpc-java/issues/8751


Changing a default object limitation

Currently, the default directory service quota is 50,000 objects. If at least one verified domain is added, the default directory service quota in Azure AD is 300,000 objects. See URL below.
https://support.microsoft.com/en-us/help/2812409/you-receive-a-this-company-has-exceeded-the-number-of-objects-that-can

@juntakata : Thanks for your contribution! The author, @curtand, has been notified to review your proposed change.

Hi @junkata. Thanks for sharing this! I'm working on verifying it with the team. I will update docs as soon as the information comes back.

Verified.
#sign-off


Avoid copy! scalar indexing error for GPU arrays

julia> using CUDA, LinearAlgebra; CUDA.allowscalar(false); u=CUDA.rand(100); v=copy(u); copy!(v,u)
ERROR: Scalar indexing is disallowed.
Invocation of getindex resulted in scalar indexing of a GPU array.
This is typically caused by calling an iterating implementation of a method.
Such implementations *do not* execute on the GPU, but very slowly on the CPU,
and therefore are only permitted from the REPL for prototyping purposes.
If you did intend to index this array, annotate the caller with @allowscalar.
Stacktrace:
 [1] error(s::String)
   @ Base ./error.jl:35
 [2] assertscalar(op::String)
   @ GPUArraysCore ~/.julia/packages/GPUArraysCore/rSIl2/src/GPUArraysCore.jl:78
 [3] getindex
   @ ~/.julia/packages/GPUArrays/EVTem/src/host/indexing.jl:9 [inlined]
 [4] copy!(dst::CuArray{Float32, 1, CUDA.Mem.DeviceBuffer}, src::CuArray{Float32, 1, CUDA.Mem.DeviceBuffer})
   @ Base ./abstractarray.jl:886
 [5] top-level scope
   @ REPL[21]:1
 [6] top-level scope
   @ ~/.julia/packages/CUDA/tTK8Y/src/initialization.jl:52

julia> copyto!(v, u)
100-element CuArray{Float32, 1, CUDA.Mem.DeviceBuffer}:
 0.8615155
 0.58178407
 0.98993677
 0.24981835
 0.49794912
 0.91618365
 ⋮
 0.69272184
 0.22738884
 0.9707413
 0.6807149
 0.444413

There are two relevant methods for copy!
[4] copy!(dst::AbstractVector, src::AbstractVector) in Base at abstractarray.jl:881
[5] copy!(dst::AbstractArray, src::AbstractArray) in Base at abstractarray.jl:891

The AbstractVector one, [4], calls setindex!, and [5] calls copyto!

julia> using CUDA, LinearAlgebra; CUDA.allowscalar(false); u=CUDA.rand(100); v=copy(u); copy!(v,u)
ERROR: Scalar indexing is disallowed.
Invocation of getindex resulted in scalar indexing of a GPU array.
This is typically caused by calling an iterating implementation of a method.
Such implementations *do not* execute on the GPU, but very slowly on the CPU,
and therefore are only permitted from the REPL for prototyping purposes.
If you did intend to index this array, annotate the caller with @allowscalar.
 @ChrisRackauckas this is done

Just use copyto!?

copyto! doesn't do size checks so is error prone

Why is this not an upstream issue to solve in GPUArrays/CUDA then to add a copy! dispatch?

i created an issue in CUDA but i need a workaround while it is addressed

would the best workaround be the _copy!stuff i put together or just use copyto! and add a link to the issue?

Wouldn't it take just like 2 minutes to make a PR to GPUArrays.jl that does copy! = copyto! on CuArrays? I don't see how this will take so long to get a real fix for. Holding onto upstream stuff like this for small changes is not good for maintenance: just fix the real issue.

ok wasn't sure about the workflow. will do the PR

Generally if the issue is some upstream package not implementing an interface correctly, it's preferred to fix that package. Hardcoding a fix here will still make it not work in other places, so other people will hit it too, and other parts of the code could hit it. So it's almost always recommended to fix upstream. That said, if it looks like this is going to take months to merge or something, then it could make sense to carry a workaround. But this looks like a 5 minute job and others will be happy, so to me it's clear copy! for GPUs should just fixed and no one then needs a workaround.

understood. thanks for explaining. GPUArrays PR is here: https://github.com/JuliaGPU/GPUArrays.jl/pull/414


BUG: Compilation errors on Windows

Cloned repo doesn't compile on Windows 10 with Visual Studio 2022.
It seems that @marcomanno has fixed it in his fork.
Following these changes I was able to compile the library but keep running into #15 with all the demos (rotation, stencil etc.) and my own custom tests.
@marcomanno - are you experiencing the same issues?

Dear Mariusz,
Thanks for the tip. We tested our code on Windows before releasing the code. Currently, we cannot test the code on Windows, so we prefer not to apply any changes.

One of our co-authors has been able to test the code on Windows.
We are going to upload a fix shortly.

Thanks. On my machine, I had to apply the fix from the fork and change the CMakeSettings as follows. The first configuration is the default one and it resulted in #15 also on the meshes shipping with the library. Switching to the second configuration made the bugs dissapear:
{
  "configurations": [
    {
      "name": "x64-Debug",
      "generator": "Ninja",
      "configurationType": "Debug",
      "inheritEnvironments": [ "msvc_x64_x64" ],
      "buildRoot": "${projectDir}\\out\\build\\${name}",
      "installRoot": "${projectDir}\\out\\install\\${name}",
      "cmakeCommandArgs": "",
      "buildCommandArgs": "",
      "ctestCommandArgs": ""
    },
    {
      "name": "x64-Release",
      "generator": "Visual Studio 17 2022 Win64",
      "configurationType": "Release",
      "inheritEnvironments": [ "msvc_x64" ],
      "buildRoot": "${projectDir}\\out\\build\\${name}",
      "installRoot": "${projectDir}\\out\\install\\${name}",
      "cmakeCommandArgs": "",
      "buildCommandArgs": "",
      "ctestCommandArgs": ""
    }
  ]
}

I can confirm that https://github.com/gcherchi/InteractiveAndRobustMeshBooleans/commit/7081647a8cc7cc823015044964cd071767947f66 fixes the issue.


Is :from_file still an option?

I wonder if I'm missing something about :from_file.
It's parsed like a JSON file, and wants to read repository information from it.
Is it still created?

It looks like the place :from_file is used should be :from. I renamed that at some point, but somehow that slipped through without breaking any tests.


[airflow] Update latest version to 2.5.0

@ephraimbuddy according to its website release date is different than what you have written

@ephraimbuddy according to its website release date is different than what you have written

It was a mistake on the release, I'm going to update it

@usta can you check again?

@ephraimbuddy yep it looks like it is fixed ,thank you i am also merging this pr


Add the option to specify a custom seperator

This PR adds the option to specify a custom separator between the rounded value and units. This is helpful to me as I do not want a space between my value and units (i.e. '1.34k' instead of '1.34 k').
Comes with tests, README updates. Let me know if there's anything missing and I'll add it!

LGTM, thanks :)

Published as 0.5.0.


pk_core: implement list addition

This commit implements list addition. A new list is allocated, and
the contents of l1 and l2 are concatenated onto the list.
This is done by extending the buffer template macro to support a
concat operation, which given an other buffer, appends all
elements of the other buffer to the end of the self buffer.
Allocations are done as needed.
We implement this additional operation, since the alternative would
be to call reserve() for each write() operation, which doesn't
seem ideal.
Issue: #55

@ThakeeNathees love the CI pipeline, wow!

This indeed is a better way than having to iterate and check the capacity, each time.
Thanks!

Nice work here! :)


Fix unit test after Binary Ninja 3.5 release

We have released Binary Ninja 3.5 last Friday. I thought we simply need to update the binja version check here: https://github.com/mandiant/capa/blob/master/tests/test_binja_features.py#L72, since it explicitly checks for version 3.4.
However, as it seems, the failures is more deadly than expected: it seems BN 3.5 crashes during the unit test: https://github.com/mandiant/capa/actions/runs/6235434766/job/16924696404#step:7:70. I will have a look at what have changed and see how it can be fixed

Oh, this might not be that bad. We have deprecated BinaryViewType.get_view_of_file, and now we should use binaryninja.load to load a binary file. This explains why all of the test are failing


graphql-tools 3.0.2

I havent been able to narrow it down yet, but using graphql-tools": "^3.0.2" and merging schemas breaks queries.
Running the merge schema example code should replicate this issue. Need to actually pull the source to confirm.

Possibly related: https://github.com/apollographql/graphql-tools/issues/753

Works fine with example repo. Closing.


Is it planned to release a alpine 3.10 based docker image?

Looking at Dockerfile all I can see is alpine 3.9 and alpine 3.10 is available :)
Thanks again

Feel free to open a PR :wink:

alpine 3.10 is available

:smile:
Timestamp on this issue: 2019-06-20 at 2:29am PDT
Timestamp of https://github.com/docker-library/official-images/pull/6121 merging: 2019-06-19 at 1:11pm PDT
(See https://github.com/docker-library/docker/pull/161 for the PR @J0WI already opened :+1:)


Update end-to-end-demo.md

Hi there,
I try to replicate this demo: apt (on Ubuntu 20.04) doesn't find gstreamer1.0-dev but rather finds libgstreamer1.0-dev.  So, am I right to correct to libgstreamer in this page?
Didier

this seems right to me ... when i run apt-get install -y libgstreamer1.0-0 gstreamer1.0-dev, I see:
Note, selecting 'libgstreamer1.0-dev' for regex 'gstreamer1.0-dev'

we should adjust this in all of our docs.

You're welcome: I may come with a couple additional ones coming from my trial on the demo. Didier


auto-limit java heap size

Let's add these keys to JVM settings for all services:
-XX:+PrintCommandLineFlags -XX:+UnlockExperimentalVMOptions -XX:+UseCGroupMemoryLimitForHeap

Thus we wouldn't need to limit the java heap size, it will be done automatically by reading container limits.

Thanks for the suggestion!
It is probably not good to enable the experimental vm options. Not sure whether it will impact the service stability. Do not hear any service recommends to use the experimental vm options.
Inherit the container limits may have unexpected limits. Currently the container max memory is not a must-have parameter when creating the service. The default container max memory is -1, which allows the container to use as many memory as possible. Usually one node will only run one stateful service. So the stateful service could safely use all memory. JVM process may have the off-heap handling to reduce the java GC imapct. For example, Cassandra could have offheap memtable, see Cassandra JVM tuning. It would be better to separate the configs for JVM heap and container max memory.

Thank you for the explanation!


mcjtylib_ng

I use rftools in a custom Modpack (MC-Version 1.10.2). I have McJtyLib installed but it frequently asks for McJtyLib_ng 2.3.10 or higher on startup. Why is this or where do I get mcjtylib_ng?
Greetz
Felix

mcjtylib_ng is just the latest McJtyLib released on curse for 1.10.2/1.11.2 (same release for these two versions of Minecraft)

Latest is version 2.4.3 btw

fast*


Talent Tree Respecing

Is your feature request related to a problem? Please describe.
You cannot pull points out of a talent if this would cause the talent tree to be invalid. This means you have to clear talents all the way down to the talent you are trying to remove points from.
Describe the solution you'd like
I would like there to be an error message if the talent tree has an invalid arrangement. This would allow an easier time for respecing. There should be a count of points in each tier to let the user know if they are missing points or if everything is present.
Describe alternatives you've considered
The only other way to utilize this is by using an outside talent tree calculator and it seems redundant to respec in one calculator just to move to the other.
Additional context
Add any other context or screenshots about the feature request here.

Thanks for the suggestion! Unfortunately, this matches the behavior of wowhead's talent calculator, and it's done that way because it prevents users from making easy mistakes.


Badge for most valuable contributor

Is your feature request related to a problem? Please describe.
As part of the Badge Gamification, it seems interesting to honor the contributor with the most valuable contributions
Describe the solution you'd like
The badge of the most valuable contributor is part of the common badge list.
The rule is:
Sum up all scores of a contributor, order by highest sum and give the badge to each token owned by that contributor

done


x32 port

Create a port x32 platform

Do we only have x86? What are your motives behind creating a x32 variant? (Out of curiosity).

Currently ia32 (x86) and x86_64 (amd64), I got the kernel to compile and
boot for arm but didn't get it to work correctly.
x32 generates 64 bits code the same way as x86_64 but using pointers and
ints of 32 bits, using less memory (similar to ia32), so you get the best
of both worlds. The only drawback it has is that although being 64 bits
process can manage only up to 4GB of ram, but I find this more than
convenient and in fact if we do the port I would sort of deprecate the
x86_64 one...
El 22/6/2016 2:46, "Lite McFish"<EMAIL_ADDRESS>escribió:

Do we only have x86? What are your motives behind creating a x32 variant?
(Out of curiosity).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/253#issuecomment-227613659, or mute
the thread
https://github.com/notifications/unsubscribe/AAgfvqQGtRF91Dgn60PlLqfgDR9hmxfdks5qOIXSgaJpZM4I6gsR
.

@piranna ah mkay. So is it 4 gigs of ram per node process? Would there be a way to escape into the 64bit space and use more ram?
What would we have to accomplish in order to get a working x32? I'm assuming that ia32 and x32 aren't the same thing?

@piranna are you referring to the x32 ABI? Maybe we should mention "ABI" for clarity, because I a bit confused at first, and others probably will be also.

@piranna so I did some research to see where v8 stands in terms of x32 support and there's a lot of work that would go into porting to the x32 abi platform. Here's an extract from a thread discussing porting to the x32  abi with one of the v8 developers:

OK - do you plan to add that support? Just asking e.g. so I can take the right action as maintainer of v8 package in Gentoo. It's fine for me if you don't have such plans. :)

No. (For reasoning, see below.)
Adding support is not just a matter of fixing a few lines. It would be an entire new platform port (albeit similar to the existing ia32/x64 ports); roughly 40K lines of code.

Got it. For reference - would you accept patches adding such a port? Note that I'm rather not going to work on it atm, but someone else might be interested.

It's not just the initial creation of a new platform port that's a bunch of work, it's also the ongoing maintenance of it (i.e. making it keep up with the continuing development of V8). As long as the potential user base for x32 is as small as it currently is, it doesn't make sense for the team to spend resources on that.
The obvious alternative is a third-party maintained port in a separate repository that tracks V8, as our MIPS port is currently doing it (https://github.com/paul99/v8m-rb). This model can work with or without upstreaming of the changes, but either way with a clear statement that the core V8 team does not commit to making sure the port works and is up to date.

The whole thread is here: https://groups.google.com/forum/#!topic/v8-users/c-_URSZqTq8
We can attempt to undertake the port as a third party and people may potentially join, or we could wait for the people using the platform to grow and be sufficient for the v8 team to do it themselves. As massive an undertaking as this might be, the performance gains shouldn't be overlooked. Interesting suggestion!

So is it 4 gigs of ram per node process?

Yes, the same as in ia32/x86.

Would there be a way to escape into the 64bit space and use more ram?

No, because pointers are of 32 bits :-)

What would we have to accomplish in order to get a working x32? I'm assuming that ia32 and x32 aren't the same thing?

As you could have already seen, no, they are not the same thing ;-)

@piranna are you referring to the x32 ABI? Maybe we should mention "ABI" for clarity, because I a bit confused at first, and others probably will be also.
@lite20

Good idea, thanks by changuing the issue title :+1:

The whole thread is here: https://groups.google.com/forum/#!topic/v8-users/c-_URSZqTq8
We can attempt to undertake the port as a third party and people may potentially join, or we could wait for the people using the platform to grow and be sufficient for the v8 team to do it themselves. As massive an undertaking as this might be, the performance gains shouldn't be overlooked.

Or we could simply just use the correct arch option on Node.js ;-)

Yes, the same as in ia32/x86.
Once I found out you were reffering to the ABI it all made sense.

Gee, I know programs that will easily bust the 4 gigs of ram limit, especially on servers. Maybe we ought not deprecate the 64bit version to support said cases. If done right, three platforms shouldn't be too much to maintain?

No, they shouldn't only just to give x86_64 a little bit less love ;-)
Anyway, I find a single theaded process more than 4GB of data a little bit
bad designed... I vet it could be parallelized some way on several
simultaneous process and use several cores.
El 23/6/2016 12:50 AM, "Lite McFish"<EMAIL_ADDRESS>escribió:

Yes, the same as in ia32/x86.
Once I found out you were reffering to the ABI it all made sense.
Gee, I know programs that will easily bust the 4 gigs of ram limit,
especially on servers. Maybe we ought not deprecate the 64bit version to
support said cases. If done right, three platforms shouldn't be too much to
maintain?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/253#issuecomment-227900939, or mute
the thread
https://github.com/notifications/unsubscribe/AAgfvuaSDjLPUQcLwxuW8SUIT1ZGbEnPks5qObwpgaJpZM4I6gsR
.

@piranna each thread can use 4GB? Mkay that makes a bit more sense. It's generally communication servers that will bust that 4GB mark.

Threads share the memory region, so no, apps using threads will still be
limited to 4GB.
El 23/6/2016 2:36, "Lite McFish"<EMAIL_ADDRESS>escribió:

@piranna https://github.com/piranna each thread can use 4GB? Mkay that
makes a bit more sense. It's generally communication servers that will bust
that 4GB mark.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/253#issuecomment-227917894, or mute
the thread
https://github.com/notifications/unsubscribe/AAgfvnymk_dsZJTwe1OWv07XI_ouecZXks5qOdT0gaJpZM4I6gsR
.

@piranna just when I was beginning to understand hahaha. Okay, so that's what I had originally thought. What's your opinion of Minecraft servers than which will use 16gb RAM if it's available? :P

Probably they are not single threaded ;-) Is there any of them build in
node.js?
El 23/6/2016 2:56, "Lite McFish"<EMAIL_ADDRESS>escribió:

@piranna https://github.com/piranna just when I was beginning to
understand hahaha. Okay, so that's what I had originally thought. What's
your opinion of Minecraft servers than which will use 16gb RAM if it's
available? :P
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/253#issuecomment-227920933, or mute
the thread
https://github.com/notifications/unsubscribe/AAgfvjVKBr6ARKVW7jSR62uadM-8wbvXks5qOdnAgaJpZM4I6gsR
.

XD no, I don't think so, and I sure hope they aren't single threaded but I thought you said all threads of a program share the same heap?

Yes, al threads on a program share the heap, that's why they are usually
faster for intercomunication but also more insecure.
El 23/6/2016 10:02 PM, "Lite McFish"<EMAIL_ADDRESS>escribió:

XD no, I don't think so, and I sure hope they aren't single threaded but I
thought you said all threads of a program share the same heap?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/NodeOS/NodeOS/issues/253#issuecomment-228166844, or mute
the thread
https://github.com/notifications/unsubscribe/AAgfvmM_uHBUR5fqqbrltirb7ShmTteWks5qOuZygaJpZM4I6gsR
.

ah okay that makes sense @piranna. Comming from my high-level programming to low level programming always leaves a few knowledge gaps. Thanks for helping me out :stuck_out_tongue:

ah okay that makes sense @piranna. Comming from my high-level programming to low level programming always leaves a few knowledge gaps. Thanks for helping me out :stuck_out_tongue:

You are welcome :-) I always loved to know the low level bits, so... :-P


Add-on directory permissions error

Problem
While attempting to install LuiExtended, the following error occurs:
❯ eso-addons add https://www.esoui.com/downloads/info818-LuiExtended.html
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Os { code: 13, kind: PermissionDenied, message: "Permission denied" }', src/addons.rs:182:62

It seems this is related to a permissions issue with a directory in the archive:
❯ ls -l LuiExtended/media/icons/
total 0
dr-xr-xr-x  2 arviceblot  staff  64 Jan  4 20:32 abilities

I'm not sure why the archive is created this way, but it leads the directory to be created as unwritable, causing the permission error when writing additional files for it.
Potential solutions

Apply unix file permissions after all files are written. I'm not really a fan of this because you would have to store permissions for all file as the archive is iterated.
Use default permissions for directories to ensure they are writable. Also not a big fan of this because of hardcoding permissions.

P.S.
@Trojan295 I would love your feedback on this. I really enjoy the spirit of this program, as it means I don't have to use Minion :P

The packaging of the zip is a bit strange. If I unzip it and then try to delete, I get permission denied errors also, as there are no write permissions on the files. So if, we change the permissions to the ones in the zip after unzipping all, then we would have problems, when removing the addon.
I think the way to go, is to ensure that all files have write permissions. I don't see any use case, where a read-only permission for a file would make sense. This should be an easy fix, just removing this block, which sets unix permissions:
https://github.com/Trojan295/eso-addons/blob/24ac0ded7252e6ebb103583c7c50524e07250f56/src/addons.rs#L188


Tile overlaps in tilemap sometimes doesn't trigger

Describe the bug
https://makecode.com/_hoxJ9c7Pk4U2
Teleporting from the orange sphere to the teal one should then instantly teleport you to the top of the screen, but if the player does not change the direction of movement, they are not teleported. Tile overlaps is also only called on sprite movement.

@riknoll does your PR resolve this issue? Or is there more to address here? Asking because it was assigned to me.

That PR should fix this issue, yes


Add correct Mime Type to S3, DO Spaces, Azure, and GCP Storage

According to the import maps spec, import maps are required to send the mime type application/importmap+json in their response headers. SystemJS does not enforce this, but Chrome's native implementation does. We should update our io-methods so that AWS, Digital Ocean, Microsoft Azure, and GCP Storage are all instructed to do so whenever we modify the import map.
More info at https://github.com/WICG/import-maps#installation

i'll take it in on #52

Resolved in #52


Updating Drafts with Attachments

Came across this issue when working with drafts that may have attachments on rails 3.2.8 (although suspect it affects newer versions).
Attachments are saved on save but doesn't look like draft_update triggers this method so images get marked to be saved but never moved since the save method doesn't get triggered.
While this is in an issue with paperclip, curious if there's a work around that you maybe able to recommend?

For those coming across a similar issue I found adding,
:preserve_files => "true"
and running the manual attachment.save method to work.

@ss44 This is an interesting scenario that I hadn't considered. In my project, I have a completely separate model for storing the attachment and link up the record in the main model with belongs_to. Then the part that is actually drafted is the foreign key to the appropriate attachment. That way, both file uploads are still preserved fully. Does that make sense?
Could you show a more complete example of your workaround for me to consider?

Handling files is not on the road map for now. Marking as won't.
A PR is always welcome.


Add fix for RelationBroken fired when relation isn't breaking

https://bugs.launchpad.net/juju/+bug/1979811
RelationBroken fired on departing unit when relation isn't breaking. If unit is leader unit, it will delete database_provides databags when it shouldn't

@carlcsaposs-canonical I have escalated the the bugreport. Fingerscrossed.
Meanwhile, here is the previos workaround implementation: https://github.com/canonical/mysql-operator/pull/40


JSON parser has problem with parsing array of elements with key equal "properties"

1. Prepare JSON like:
{
    "features": [
        {
            "type": "Feature",
            "geometry": {
                "type": "GeometryCollection",
                "geometries": [
                    {

                        "type": "Point",
                        "coordinates": [
                            19.883992823270653,
                            50.02026203045478
                        ]
                    }
                ]
            },
            "properties": {
                "gridId": 6
            }
        },
        {
            "type": "Feature",
            "geometry": {
                "type": "GeometryCollection",
                "geometries": [
                    {
                        "type": "Point",
                        "coordinates": [
                            19.901266347582094,
                            50.07074684071764
                        ]
                    }
                ]
            },
            "properties": {
                "gridId": 7
            }
        }
   ]
}
2.
Here are two examples of code. First one is working, second is not.
List<String> typeList= JSON.jsonPath().get("features.geometry.type"); //It's
working
List<Integer> gridIdList= JSON.jsonPath().get("features.properties.gridId");
//It's not working

In second case I should get list of all gridIds but its not working, it returns
null. I
assumed it is connected with property name = "properties". The example above is
valid GeoJson format.

What is more interesting I can do something like that and it's working:
Integer gridId = JSON.jsonPath().get("features[0].properties.gridId");

Version: 2.4.0

Original issue reported on code.google.com by<EMAIL_ADDRESS>on 21 Apr 2015 at 9:07

As a workaround I think you can do "features.'properties'.gridId"

Original comment by<EMAIL_ADDRESS>on 7 Jun 2015 at 4:49


Can't load the job having 2627 images

My actions before raising this issue
I had annotated approximately 1300 images, then I did control+S and closed the window. I am trying to open the job but just keeps loading.....
frames = 0-2625
segment size = 2626
image quality = 70

@spt3009 , could you please provide more information? Which version of CVAT do you use (CVAT.ai cloud or on-prem)? If you use self-hosted version is it the latest release CVAT v2.4.0?
We just need steps to reproduce the issue on our side.

Computer Vision Annotation Tool
CVAT is completely re-designed and re-implemented version of Video Annotation Tool from Irvine, California tool. It is free, online, interactive video and image annotation tool for computer vision. It is being used by our team to annotate million of objects with different properties. Many UI and UX decisions are based on feedbacks from professional data annotation team.
Server version: 2.4
Core version: 8.2.0
Canvas version: 2.16.2
UI version: 1.49.3

Project #20542 created by shivam4 on March 20th 2023

Computer Vision Annotation Tool
CVAT is completely re-designed and re-implemented version of Video Annotation Tool from Irvine, California tool. It is free, online, interactive video and image annotation tool for computer vision. It is being used by our team to annotate million of objects with different properties. Many UI and UX decisions are based on feedbacks from professional data annotation team.
Server version: 2.4
Core version: 8.2.0
Canvas version: 2.16.2
UI version: 1.49.3
Project #20542 created by shivam4 on March 20th 2023

On 22-Mar-2023, at 12:50 PM, Nikita Manovich @.***> wrote:
@spt3009 https://github.com/spt3009 , could you please provide more information? Which version of CVAT do you use (CVAT.ai cloud or on-prem)? If you use self-hosted version is it the latest release CVAT v2.4.0?
We just need steps to reproduce the issue on our side.
—
Reply to this email directly, view it on GitHub https://github.com/opencv/cvat/issues/5898#issuecomment-1479028352, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYHBEIPI6P7VENA7V2JSLB3W5KR2VANCNFSM6AAAAAAWDMMJ5A.
You are receiving this because you were mentioned.

You must add your images to a .zip archive , and upload it.

so, I will I have to delete the task and re-annotate the images ?

so, I will I have to delete the task and re-annotate the images ?

On 22-Mar-2023, at 4:44 PM, outforz @.***> wrote:
You must add your images to a .zip archive , and upload it.
—
Reply to this email directly, view it on GitHub https://github.com/opencv/cvat/issues/5898#issuecomment-1479372125, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYHBEIN5RSGIQ2S2DT7PQR3W5LNJBANCNFSM6AAAAAAWDMMJ5A.
You are receiving this because you were mentioned.

I think I misunderstood your question!
In your case, I would recommend stopping docker and restarting it.
I have encountered a similar situation.

i am not using docker.

On 22-Mar-2023, at 4:50 PM, outforz @.***> wrote:
I think I misunderstood your question!
In your case, I would recommend stopping docker and restarting it.
I have encountered a similar situation.
—
Reply to this email directly, view it on GitHub https://github.com/opencv/cvat/issues/5898#issuecomment-1479381749, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYHBEIK7Z5WEWI6JVILBTC3W5LN6LANCNFSM6AAAAAAWDMMJ5A.
You are receiving this because you were mentioned.

@jhaux-askui, it seems like a different problem with the space left on the server. If the server is under your control, please check if there is enough disk space, and it is allowed for use by the containers.
@spt3009, #5974 may fix the problem once merged. It addresses long responses from the server on the job loading, leading to timeout errors.

Thanks for the quick answer @zhiltsov-max!
I'll check out if the servers are managed by us.
Today when I tried to load the job I got this error:
Error: Request failed with status code 500. "\n<!doctype html>\n\n\n <title>Server Error (500)</title>\n\n\n
Server Error (500)

\n\n\n".

Then after refreshing it actually worked and loaded everything! It might be because I have a better internet connection today.
I hope that helps :slightly_smiling_face:

I have a similar problem. After having annotated 1500 images I cannot open the job anymore. In the console I get only a timeout error.
If I want to export the annotations from jobs page I get the following error:
Could not export dataset for the job xxx

Error: Request failed with status code 500. "django.db.utils.OperationalError: could not resize shared memory segment "/PostgreSQL.1284416766" to 33554432 bytes: No space left on device\nCONTEXT: parallel worker\n\n".

It looks like there is no space left on the servers?
Is there any way I can debug what is going wrong? I would really like to not lose those annotations.

Try to increase shared memory size for cvat_db container https://docs.docker.com/compose/compose-file/compose-file-v3/#domainname-hostname-ipc-mac_address-privileged-read_only-shm_size-stdin_open-tty-user-working_dir

I hope the issue was solved. Do not hesitate to reopen in any case.


My sync node got error InvalidStateRoot unexpectedly.

Description
I started a sync node since 2023-11-06.
Every workday, it was connected to our internal testnet when I started work, and it was stopped after I got off work.
Every two or three days, I re-compiled a new Axon binary with latest commit on main branch.
Current version is 0828794.
I was trying to write a tool to connect p2p network directly today (2023-11-17), so I didn't use my sync node whole day, but it was still started in background.
Half an hour ago, I tried to start it manually, but it could not do sync anymore.
It printed the following errors again and again.
[INFO core_consensus::synchronization] [synchronization]: synced block, status: number:655420
[WARN overlord::state::process] Overlord: state receive an outdated status, height 655421, self height 655421
[WARN core_consensus::message] sync: receive remote block ProtocolError { kind: Consensus, error: InvalidStateRoot { expect: 0x33dbabe0f76b1e79948e0038bbf0c2b050e099a71b4c831c35f495a2ae7849c9, actual: 0x
e1f9583e2438d2718a3875435f237c68e534c759ade4e33aa21ffa488e93addc } }
[INFO core_consensus::synchronization] [synchronization]: sync start, remote block number 671754 current block number 655420
[INFO core_consensus::synchronization] [synchronization]: try syncing block, current_consented_number 655420,syncing_number 655421
[DEBUG core_executor::system_contract] execute addr 0xffffffffffffffffffffffffffffffffffffff01
[ERROR core_consensus::synchronization] [synchronization]: commit block 655420 error
[ERROR core_consensus::synchronization] [synchronization]: err, current_number 655420 err_msg: ProtocolError { kind: Consensus, error: InvalidStateRoot { expect: 0x33dbabe0f76b1e79948e0038bbf0c2b050e099a
71b4c831c35f495a2ae7849c9, actual: 0xe1f9583e2438d2718a3875435f237c68e534c759ade4e33aa21ffa488e93addc } }

I found the first error was happened at 2023-11-17T10:44:44.267931834+08:00.
From then, my sync node had not synced any blocks.
Update-1
I tried:

:x: 0828794
:x: 684610f
:x: 37cddb7
:x: b514a1d
:x: ad4375b
:white_check_mark: 9a0bdbd

Update-2
Commits between ad4375b..9a0bdbd are:

:white_circle: ad4375b 2023-11-02 chore: remove empty crates (#1521)
:question: 68aa8a9 2023-11-02 feat: move axon-tools to axon (#1519)
:question: 552b328 2023-11-02 chore: make blst portable (#1520)
:question: 166506f 2023-10-30 refactor: remove the limitation of set ckb related info (#1517) :point_left: I guess it's this.
:white_circle: f9974e6 2023-10-30 chore(deps): bump Namchee/conventional-pr from 0.14.1 to 0.15.1 (#1515)
:white_circle: 2774ef8 2023-10-29 ci: adjust CI after migrating the test projects (#1513)
:white_circle: 6303cb9 2023-10-27 chore: DO NOT change a tag on a remote repository (#1512)
:white_circle: 6494d69 2023-10-27 chore(CI): Remove the duplicated Smoking test job (#1510)
:white_circle: 363b49f 2023-10-27 chore(CI): build a portable binary in CI for different CPU architectures (#1504)
:white_check_mark: 9a0bdbd 2023-10-24 (HEAD) refactor: more details for JSON RPC errors (#1495)

Skip the changes that don't modify source codes, there are only 3 commits which could introduced the break change, as I flagged above.
Update-3
I found another bad block at number 656501.
I tried:

:x: 552b328
:x: 166506f
:white_check_mark: f9974e6

Result
:dart: The commit 166506f introduced the break change.

Since I don't have bad data anymore, and the data is too large that I don't want to sync them again. (ref: #1574)
:sos: So my investigation is stopped. I won't work on this issue anymore.
Please assign another one to continue this task, based on my works above.

Result
🎯 The commit 166506f introduced the break change.

cc @KaoImin
related PR: https://github.com/axonweb3/axon/pull/1517

Conclusion

https://github.com/axonweb3/axon/pull/1517 and https://github.com/axonweb3/axon/pull/1576 should
be placed in https://github.com/axonweb3/axon/issues/1596,
not in https://github.com/axonweb3/axon/pull/1537


Cannot build on React Native 0.41.2

Current behavior:
Cannot build.
Reproduce:
$ React native awesome
$ cd awesome
$ npm i --save lottie-react-native
└─┬<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>
$ react-native link lottie-ios
rnpm-install info Linking lottie-ios ios dependency
rnpm-install info iOS module lottie-ios has been successfully linked

$ react-native link lottie-react-native/
rnpm-install info Linking lottie-react-native/ android dependency
rnpm-install info Android module lottie-react-native/ has been successfully linked
rnpm-install info Linking lottie-react-native/ ios dependency
rnpm-install info iOS module lottie-react-native/ has been successfully linked

$ react-native run-ios
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTAnimatableLayer.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTEllipseShapeLayer.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTGroupLayerView.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTLayerView.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTMaskLayer.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTRectShapeLayer.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTShapeLayerView.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTAnimatableBoundsValue.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTAnimatableColorValue.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTAnimatableNumberValue.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTAnimatablePointValue.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTAnimatableScaleValue.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTAnimatableShapeValue.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTShapeRectangle.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTAnimationCache.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTComposition.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTShapeGroup.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTMask.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTShapeStroke.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTLayer.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTAnimationView.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTShapePath.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTShapeTransform.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTShapeFill.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTShapeTrimPath.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTShapeCircle.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(CAAnimationGroup+LOTAnimatableGroup.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(CGGeometryAdditions.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(UIColor+Expanded.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(LOTAnimationTransitionController.o)) was built for newer iOS version (10.2) than being linked (8.0)
ld: warning: object file (/Users/yuhogyun/test/awesome/ios/build/Build/Products/Debug-iphonesimulator/libLottie.a(Lottie_vers.o)) was built for newer iOS version (10.2) than being linked (8.0)
Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_LOTStrokeShapeLayer", referenced from:
      _OBJC_CLASS_$_LOTCircleShapeLayer in libLottie.a(LOTEllipseShapeLayer.o)
      _OBJC_CLASS_$_LOTRoundRectLayer in libLottie.a(LOTRectShapeLayer.o)
      objc-class-ref in libLottie.a(LOTShapeLayerView.o)
  "_OBJC_METACLASS_$_LOTStrokeShapeLayer", referenced from:
      _OBJC_METACLASS_$_LOTCircleShapeLayer in libLottie.a(LOTEllipseShapeLayer.o)
      _OBJC_METACLASS_$_LOTRoundRectLayer in libLottie.a(LOTRectShapeLayer.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

** BUILD FAILED **

The following commands produced analyzer issues:
	Analyze Modules/RCTRedBox.m
(1 command with analyzer issues)

The following build commands failed:
	Ld build/Build/Products/Debug-iphonesimulator/awesome.app/awesome normal x86_64
(1 failure)

Installing build/Build/Products/Debug-iphonesimulator/awesome.app
An error was encountered processing the command (domain=NSPOSIXErrorDomain, code=22):
Failed to install the requested application
The bundle identifier of the application could not be determined.
Ensure that the application's Info.plist contains a value for CFBundleIdentifier.
Print: Entry, ":CFBundleIdentifier", Does Not Exist

Command failed: /usr/libexec/PlistBuddy -c Print:CFBundleIdentifier build/Build/Products/Debug-iphonesimulator/awesome.app/Info.plist
Print: Entry, ":CFBundleIdentifier", Does Not Exist

So, I open my iOS project ,clean and then build
But error log here
Undefined symbols for architecture x86_64:
  "_OBJC_CLASS_$_LOTStrokeShapeLayer", referenced from:
      _OBJC_CLASS_$_LOTCircleShapeLayer in libLottie.a(LOTEllipseShapeLayer.o)
      _OBJC_CLASS_$_LOTRoundRectLayer in libLottie.a(LOTRectShapeLayer.o)
      objc-class-ref in libLottie.a(LOTShapeLayerView.o)
  "_OBJC_METACLASS_$_LOTStrokeShapeLayer", referenced from:
      _OBJC_METACLASS_$_LOTCircleShapeLayer in libLottie.a(LOTEllipseShapeLayer.o)
      _OBJC_METACLASS_$_LOTRoundRectLayer in libLottie.a(LOTRectShapeLayer.o)
ld: symbol(s) not found for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

My environment is OS X Elcapitan 10.11
$ node -v
v7.5.0

$ npm -v
4.1.2

$ react-native -v
react-native-cli: 2.0.1
react-native: 0.41.2

Comment
The recent lottie-ios is 1.0.3 but lottie-react-native dependency ios is 1.0.2
Is it related to the version dependency?
Editted
$ react-native upgrade
Then i can use lottie.
but animation not showing without any error.

Same error here, temporarily fixed by creating a new project using the guide in #31

no animation here and I cannot build. #52

Same error

Same for me

I got it working by adding Lottie.framework to Embedded Binaries in XCode.

@jozan Awesome! It works for me

@jozan  it workd for me too ;) Thanks !!

In more detail,

Worked for me also, thanks.

It Resolved For me, so closed

Its still a bug though and needs to be resolve, doesn't it?

@yoohoogun114 Same error. and solved by your answer.
But I have new error:

Can not run react-native run-ios  to start simulator, build success, run crash.
Launch simulator from Xcode, no error. but not show animation.

Do you have same question?

I had the same experience. I can compile, but no animation or image rendering.

I've RN 0.39.2 and been trying all guides here, still having the same error á 'Lottie/Lottie.h' file not found inside node_modules/lottie-react-native/lib/ios/LottieReactNative/LRNContainerView.h
Do you guys think it's RN 0.39.2 being the bad guy?

@leesolway same here, trying to figure out why rendering is not working (https://github.com/airbnb/lottie-react-native/issues/52)

It works for me, but looks like not others. so Reopen.

@olle-moren-schibsted Are you sure you have linked lottie-iosas well?
react-native link lottie-ios

@jozan having node version 6.5.0 and RN 0.39.2 doing like this:
<EMAIL_ADDRESS>└─┬<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └──<EMAIL_ADDRESS>
react-native link lottie-ios
rnpm-install info Linking lottie-ios ios dependency
rnpm-install info iOS module lottie-ios has been successfully linked
react-native link lottie-react-native
rnpm-install info Linking lottie-react-native android dependency
rnpm-install info Android module lottie-react-native has been successfully linked
rnpm-install info Linking lottie-react-native ios dependency
rnpm-install info iOS module lottie-react-native has been successfully linked```
![xcode](https://cloud.githubusercontent.com/assets/5330517/23119669/700e2d52-f759-11e6-9551-ccc29ebd50fc.png)

@olle-moren-schibsted Those are the steps I got it working on RN 0.41.2.

For anyone that is still having problem. Error is something like this
Class LOTStrokeShapeLayer is implemented in both
...
...

This can be fixed by deleting libLottie.a and adding Lottie.framework in the embeded binaries section instead. The final linked libraries should be like this.

Thanks @PanJ !

Can this be added to the readme?

@kyle-ssg see PR #86

It is working only if this condition is met and correctly linked:
Embedded binary + Lottie.framework
Link Frameworks and LIbrary +  libLottieReactNative.a

I had both of these, but was still getting a blank image where the animation should have been.

@leesolway Can you confirm that LibLottie.a isn't linked ? Can you provide a screenshot of your Embedded binary and Link Frameworks and LIbrary ?

Hi guys,
Posting here because I've got a similar problem. I succeeded to make lottie work on my RN project using Lottie 1.0.6 and RN 0.39 on iOS in debug. I removedlibLottie.a as said above from the linked frameworks and libraries and it's building well on the simulator and animations correctly appear.
However, when using fastlane to generate an .ipa to deploy on Testflight for my team, the build is not working and I've got the following message node_modules/lottie-react-native/lib/ios/LottieReactNative/LRNContainerView.h:19:9: 'Lottie/Lottie.h' file not found
http://cl.kowaio.me/2w0M2027462S
I don't know why it's doing this in release since everything seems to work. Did you encounter this while trying to build on your side?
Thanks again guys

@Kowaio seems like you don't have link the Lottie.Framework. Can you provide a screenshot of your Embedded binary and Link Frameworks and LIbrary ?

@Kowaio can't help sorry. Maybe see this comment.
Open a proper issue to get more accurate help.

@g3r4n
As requested

I believe this should now be fixed in<EMAIL_ADDRESS>Please try it out and let me know if you still have trouble. Closing this issue for now. Thanks!

Hello @lelandrichardson,
Sorry to come back to you only now. I tested with<EMAIL_ADDRESS>but I've got the same problem while building for release.
Here's a screenshot: http://cl.ly/0s0U1a211f2j
Thanks

@Kowaio same here.


Add Connecto Data to the list

Connecto Data is a member of Microsoft for Startups and delika (something like GitHub for data sharing) in the source column in the list is written in F# for the most part.

@kos59125  Could you also add a testimonial to https://fsharp.org/testimonials please? By doing that it helps us verify the addition here. Thanks

Connecto Data is a Japanese company so that its website is written in Japanese. Does it make sense to add a Japanese description to the listing? Or do I need to translate it into English?

I think having both English and Japanese would be great!  The social proof offered by testimonials in one's own language is very high


Laravel 5.6 compatible

When will it be compatible with version 5.6 of laravel?
When I install the package I get the following error.
c:\xampp\htdocs\panelhotel>composer require yajra/laravel-datatables-buttons:^3.0
./composer.json has been updated
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.
Problem 1
- Installation request for yajra/laravel-datatables-buttons 3.0 -> satisfiable by yajra/laravel-datatables-buttons[v3.0.0].
- Conclusion: remove laravel/framework v5.6.11
- Conclusion: don't install laravel/framework v5.6.11
- yajra/laravel-datatables-buttons v3.0.0 requires illuminate/console 5.4.|5.5. -> satisfiable by laravel/framework[5.4.x-dev, 5.5.x-dev], illuminate/console[5.4.x-dev, 5.5.x-dev, v5.4.0, v5.4.13, v5.4.17, v5.4.19, v5.4.27, v5.4.36, v5.4.9, v5.5.0, v5.5.16, v5.5.17, v5.5.2, v5.5.28, v5.5.33, v5.5.34, v5.5.35, v5.5.36, v5.5.37, v5.5.39].

Operating System
PHP Version 7.1
Laravel Version 5.6
Laravel-DataTables Version 8.0

Use it in composer.json
"yajra/laravel-datatables-buttons": "~3.2"

It's working for me.

@sangnguyenplus, your recommendation works for me as well.
I am having issues adding custom buttons. Have you had any success with Laravel 5.6 adding a custom button?


Discover Listings Are Not Always Consistent

Reported by @dtarb on 11/1/2020
I just went to HydroShare and noticed an inconsistency in Discover
I first saw

Notice two resources authored by Salehabadi.  These are what I am working with her on, and there were 3 resources we worked on yesterday.  I was puzzled why the 3rd was not listed in the default last modified listing.   I found the resource by clicking on it – it is a member of the collection.  Then when I went back to discover it is there.

This may be hard to reproduce – but there is something causing Discover listings to not always be consistent.

Unable to reproduce need more information

Closing.  I suspect this may be due to arbitrariness in the way ties are resolved sorting by last modified date.  But as hard to document an error am closing.


Trait for more concise conversions

If math libraries implement this trait, it will allow conversions between two different libraries' types, which would previously have always been written mint::Foo::from(x).into(), to be written as x.convert() when types are unambiguous. This makes mint more ergonomic when dealing with downstream crates written against a specific math library. Bikeshedding welcome.

I don't want mint to have any traits at all. Ideally, it's just a bunch of plain old data with strong semantics that is easy to interop with.
Note that the primary use case of mint doesn't involve converting between different math libraries. The whole point is having mint on the boundary, so there are only conversion to and from it.

That's frequently not going to happen, though. Many libraries target a specific crate and aren't going to change. There's even the significant case of interoperability between different versions of the same math crate.
Supporting mint is already a matter of implementing several traits, so it seems odd to categorically reject one additional impl.

Many libraries target a specific crate and aren't going to change.

Please provide examples.

Supporting mint is already a matter of implementing several traits, so it seems odd to categorically reject one additional impl.

Yes, you are right, but these are only standard traits, which are in prelude. Mint is a thing that needs to be small, so we can't just expand it because "seems odd to categorically reject one additional impl".

Please provide examples.

nalgebra and ncollide, I think the entire amethyst ecosystem, certainly most things I publish...

we can't just expand it because "seems odd to categorically reject one additional impl".

Indeed that's not reason for inclusion; I was only illustrating that "no traits" isn't a sensible rule in and of itself.
A more interesting argument is that something like this is also useful for implementing crates that put mint on the interface. Compare:
fn foo<T: From<mint::Vector3<f32>>>() -> T {
    T::from(na::Vector3::zero().into())
}
fn foo<T: From<mint::Vector3<f32>>>() -> T {
    na::Vector3::zero().convert()
}

It's not a huge difference, but ergonomic wins make "use mint on your interface" that much easier a sell.
The version drafted in this PR is less applicable to arguments where you want Into instead of From, but a revised approach can resolve that:
pub trait Minty {
    type Equivalent;
}

/// Conversion directly between types that implement `From` for `mint` types.
pub trait Convert: Minty + Into<<Self as Minty>::Equivalent> {
    /// Convert into a compatible type
    fn convert<T: From<Self::Equivalent>>(self) -> T {
        T::from(self.into())
    }
}

nphysics and ncollide, I think the entire amethyst ecosystem, certainly most things I publish...

Ah, ok, I see what you mean.
Sorry, I don't feel that convert() is needed, still. I can see how it makes some of the use cases smoother, but I want to reduce the type magic and keep the API minimalistic.

No worries, just a thought.


Warning while rendering shadows

Hi! Sometimes while using react-sketchapp 2.1.0 shadows property we get the following warning:
Warning: Failed prop type: checker is not a function. (In ‘checker(propValue, key, componentName, location, propFullName + ‘.’ + key, ReactPropTypesSecret)’, ‘checker’ is an instance of Object)
   in View (created by Button)
   in Button (created by Controls)
   in view (created by View)
   in View (created by Controls)
   in view (created by View)
   in View (created by Controls)
   in Controls
   in view (created by View)
   in View (created by Sample)
   in Sample
   in view (created by View)
   in View (created by Story)
   in view (created by View)
   in View (created by Story)
   in Story
   in artboard (created by Artboard)
   in Artboard
   in page (created by Page)
   in Page
   in document (created by Document)
   in Document
   in Unknown

While not breaking the build, it's pretty annoying. Any ideas how to avoid this? Thanks!

found it


Add city configuration files x 6

This pull request will add configuration files and update cities.json for:

Adelaide
Auckland
Cologne
Graz
Sydney
Valencia

I believe @shiqin-liu ended up pulling in all the city configs in #17. If that isn't the case, let me know. If it is the case, we can close this PR I believe.

Yes, @gboeing I did, I think you can close this PR. and I just added the rest of the four cities config #25


AzDO, 5.9: truncate intermediate output files to save space

Ugh, I forgot about 5.9...

Anyway, it worth to wait for VS2022 checks.


0.7.6 issue with protocol relative URL

Not sure if this is an issue or not... With 0.7.5 it didn't happen. With 0.7.6 my css includes this
@font-face{font-family:'Open Sans';font-style:normal;font-weight:400;src:local('Open Sans'),local('OpenSans'),url(http://themes.googleusercontent.com/static/fonts/opensans/v7/cJZKeOuBrn4kERxqtaUH3aCWcynf_cDxXwCLxiixG1c.ttf) format('truetype')}@font-face{font-family:'Open Sans';font-style:normal;font-weight:700;src:local('Open Sans Bold'),local('OpenSans-Bold'),url(http://themes.googleusercontent.com/static/fonts/opensans/v7/k3k702ZOKiLJc3WVjuplzInF5uFdDttMLvmWuJdhhgs.ttf) format('truetype')}@font-face{font-family:'Open Sans';font-style:italic;font-weight:400;src:local('Open Sans Italic'),local('OpenSans-Italic'),url(http://themes.googleusercontent.com/static/fonts/opensans/v7/xjAJXh38I15wypJXxuGMBp0EAVxt0G0biEntp43Qt6E.ttf) format('truetype')}

which is because I have
<link rel="stylesheet" href="//fonts.googleapis.com/css?family=Open+Sans:400,400italic,700">

But I'm not sure this makes sense to include it since it beats the point of using the google fonts.

I wonder, why does it output such strange font-faces, why just doesn't copy them to output file as they are?


Speech client library version update.

Codecov Report

Merging #618 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #618   +/-   ##
=========================================
  Coverage     55.84%   55.84%
  Complexity      202      202
=========================================
  Files            74       74
  Lines          2052     2052
  Branches        131      131
=========================================
  Hits           1146     1146
  Misses          874      874
  Partials         32       32

Continue to review full report at Codecov.

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

@lesv FYI, there's an improvement in async calls in the updated version of the client library.


chore: set ANDROID_STL to c++_shared

This defaults to c++_static but we need to use the shared version to make exceptions (and other STL types) across shared object boundaries work correctly. See https://developer.android.com/ndk/guides/cpp-support#selecting_a_c_runtime for further information.

🤯


Use showcase image with notification plugin

Deploy the janus-idp showcase based on quay.io/janus-idp/backstage-showcase:pr-885 image that was created by https://github.com/janus-idp/backstage-showcase/pull/885
Due to a bug in the notification plugin, the DB should be created manually by
CREATE DATABASE backstage_plugin_notifications;
GRANT ALL PRIVILEGES ON DATABASE backstage_plugin_notifications TO postgres;

Currently the showcase image fails with:
Backend failed to start up error: database "backstage_plugin_notifications" does not exist
    at Parser.parseErrorMessage (/opt/app-root/src/node_modules/pg-protocol/dist/parser.js:287:98)
    at Parser.handlePacket (/opt/app-root/src/node_modules/pg-protocol/dist/parser.js:126:29)
    at Parser.parse (/opt/app-root/src/node_modules/pg-protocol/dist/parser.js:39:38)
    at Socket.<anonymous> (/opt/app-root/src/node_modules/pg-protocol/dist/index.js:11:42)
    at Socket.emit (node:events:517:28)
    at addChunk (node:internal/streams/readable:335:12)
    at readableAddChunk (node:internal/streams/readable:308:9)
    at Readable.push (node:internal/streams/readable:245:10)
    at TCP.onStreamRead (node:internal/stream_base_commons:190:23) {
  length: 115,
  severity: 'FATAL',
  code: '3D000',
  detail: undefined,
  hint: undefined,
  position: undefined,
  internalPosition: undefined,
  internalQuery: undefined,
  where: undefined,
  schema: undefined,
  table: undefined,
  column: undefined,
  dataType: undefined,
  constraint: undefined,
  file: 'postinit.c',
  line: '941',
  routine: 'InitPostgres'
}

@mareklibra is working on making a notifications plugin dynamic. We need to change how we deploy notifications once he will complete his work

A new PR will be created once the notification is available as a dynamic plugin.