text:
Client example not working as shown

Hi there,
I have been trying to use the client on both my Raspberry Pi 2 running Node.js 4.2 and my Mac running Node.js 5.5. When I try the client example I can configure, but when trying to list feeds I cannot get similar results to the guide. I configured my username and key from adafruit.io using the config command and that seemed to work fine (though not sure how to check that it did).
Here is what I get on both systems when I try the client:
nik@DN51skbb:~$ adafruit-io client feeds all
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
[info] Success
[]

I looked this line up and found some links to an issue with swagger [https://github.com/swagger-api/swagger-js/issues/689]
Tried also just to get one feed test from my account
nik@DN51skbb:~$ adafruit-io client feeds get test
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
[error] [object Object]

Similar thing if I try to send some data (which does not send):
nik@DN51skbb:~$ adafruit-io client data send test 10
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
Method getMockSignature is deprecated
Methods createJSONSample and getSampleValue are deprecated
? data.value (optional): 10
? data.lat (optional):
? data.lon (optional):
? data.ele (optional):

Not sure what is going wrong. any thoughts on what might be happening?

@nikmart i'm actually working on client updates today, so i'll let you know when those errors are fixed

authors: nikmart toddtreece

repo: adafruit/adafruit-io-node


text:
Fails in wordbreak and linebreak algorithms

When implementing the grapheme break algorithm I wrote a little test program that uses the unicode test files to check the output of my implementation.
see http://www.unicode.org/Public/9.0.0/ucd/auxiliary/
I did adapt the program for the linebreak and wordbreak algorithms.
according to this the wordbreak implementation fails 2 tests: line 1361 and 1363 and the linebreak fails 532 out of roughly than 7300 tests.
Is this intentional? Are you interested in the programs to see for yourself? They are pretty simple...

Oh well... I did use the 9.0.0 testsuite, maybe that one is not the right one to use?

9.0.0 is the correct version, we should be up to date.
Thanks for reporting this, and great timing, as my plan for this week was to add a test suite to libunibreak. :)
Could you please create a pull request with the suite, or alternatively just send me the code and I'll integrate it with the build system?
Thank you very much, this is highly needed. :)

Let me clean them up a bit and I will append them here in a while. They are very similar to the test program that is included in my pull-request, just adapted to use the other funktion calls and defines for the other algorithms and of course to use the other test specs.

Great, thanks!

@roever, btw, I have some free time in the next few days if you want, I'd happily create this based on the code from your PR.

OK, I have update the pull request. It includes the latest grapheme test program. It includes your comments but also some additions. For example it now also converts the string to utf8 and checks with that encoding. I'm more fluent with C++ so some of the stuff is a bit clunky... I really hate C string handling... anyway you might want to use that as a starting point for your test programs. Maybe even have a common test program to test all 3 interfaces... whatever. Conversion is straighforward:

exchange test file name
change function names for the interface to test
change default values written into the desired_breaks array

@roever, thanks, I added a test suite based on your code.
I also checked the issues with the wordbreak algorithm and to me they look like an issue with the test data, and not the implementation. I sent an email to the Unicode mailing list, will update as I get a reply.
@adah1972, please take a look at the linebreak issues. Just run "make check" (you'll may need to disable the wordbreak test in the makefile because it too is failing at the moment).

Thank you both! A test suite is very useful.
I see the errors, and I look into them deeply at weekend.
By the way, do you mind if I reformat the test code? It seems a strange mix of GNU style and our current style. I can also check in my clang-format configuration then. We may then only discuss the configuration items when we have code style issues (well, the parenthesis one not included).

I added my clang-format configuration first. Even though it does not use the latest clang-format options and we do not have complete consensus about everything, I think it may serve as a good starting point. We can change it later.

Yes, please do. That's why I asked for it, I knew I was doing it wrong.
On 22 Nov 2016 2:18 p.m., "Wu Yongwei" notifications@github.com wrote:

Thank you both! A test suite is very useful.
I see the errors, and I look into them deeply at weekend.
By the way, do you mind if I reformat the test code? It seems a strange
mix of GNU style and our current style. I can also check in my clang-format
configuration then. We may then only discuss the configuration items when
we have code style issues (well, the parenthesis one not included).
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/adah1972/libunibreak/issues/19#issuecomment-262251822,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAGofjdgmiuzB-YPLWeJ-aansSuKY-r2ks5rAvmmgaJpZM4K3oxm
.

OK, I made some quick changes. The function is also a bit long to my taste, but I did not change this for the moment.

For reference, here's my mail in the unicode mailing list archive: http://www.unicode.org/mail-arch/unicode-ml/y2016-m11/0146.html

Update: wordbreak now passes the test suite.

Btw, @adah1972, we should probably make a libunibreak release once you finished fixing the issues. It looks like this release will include many bug fixes and a new feature (grapheme break), so I'd love to have it in production.

Yup. Unicode 9.0 support, bug fixes, and a new feature. :-)

There are quite a few issues with line breaking. I am not sure whether I can make all the test suite pass quickly, but I am in the process of fixing it.
There is one specific thing that I want your input. This is what the UAX#14 says about CJ (Conditional Japanese Starter):

This character class contains Japanese small hiragana and katakana. Characters of this class may be treated as either NS or ID.
CSS Text Level 3 (which supports Japanese line layout) defines three distinct values for its line-break behavior:

strict, typically used for long lines
normal (CSS default), the behavior typically used for books and documents
loose, typically used for short lines such as in newspapers

These have different sets of “kinsoku” characters which cannot be at the beginning or end of a line; strict has the largest set, while loose has the smallest. The motivation for the smaller number of kinsoku characters is to avoid triggering justification that puts characters off the grid position.
Treating characters of class CJ as class NS will give CSS strict line breaking; treating them as class ID will give CSS normal breaking.

The test suite implies it uses the ‘strict’ mode, while I use ‘normal’. I still think ‘normal’ is better as the default. So I think these are the options:

Do not fix it, and let the test fail.
Change the default behaviour, and the behavioural change may surprise people.
Add a function like set_linebreak_mode(enum LineBreakMode); keep the current default, but set the strict mode for testing.

I think the last option is the best, don’t you agree? Also, do you see such a mode useful in word breaking and grapheme breaking? (I guess not.)

The disadvantage of a  set_linebreak_mode is that you can no longer use it in a multi-threaded environment. As far as I can see now.. right now no function has internal state and can potentially be called in different threads. With set_mode you'd destroy that property

what about "on the fly" adaptation of the tests. Whenever you encounter a character that requires the strict linebreaks replace it with one that has the same character class for normal linebreak.

Right, I thought about the multi-threading problem, and the right solution is to create an object and do the rest with the object. It is a big interface change, and I am not sure it is worthwhile.
On-the-fly adaptation will make the test pass, but it is a test-only solution. It is a little bit ugly. I am wondering whether it is worse than introducing a global variable...

there are other "ugly" possibilities:

add a new parameter to the linebreak function with the linebreak mode, the current function calles the new function with the normal linebreak modus. User who require a differen mode use the new function. No global state or object required, no interface change for existing applications, but it doesn't scale in case other parameters are added

Exactly the reason why Windows had DoSomething and then DoSomethingEx. Some people said their company even had ...ExEx. ;-)
No, if I were to add a new API, I would definitely make it an object. It would be more future-proof. It is now more about how to make a reasonable change without breaking the existing API.

I'd add a new API with an object. It's the only reasonable way going forward if you ask me.
With that being said, I do have a fairly clean hacky solution in mind: set the mode in the language parameter. That is accept "jp-normal", "jp-strict" as potential values. Though I'd rather you add the object API discussed above.

I think the key question is: is the change worth while? and how about word break and grapheme break?
Personally, I do not feel the reason for change is strong enough: it arises only from a test instead of real-world cases. This said, if you both agree, we can release a version without fixing this test case, and then work on a new version with an object-oriented API.

Although I initially called it a hack, maybe the solution I proposed above is a good one. Setting the language to "jp-strict" and "jp-normal" to control this behaviour. What do you think?
If you disagree with the above, I think it's a good idea to release a version without fixing this test case, because as we said, it's not broken, just a different mode.

Yes, I think the "jp-strict" solution sounds very appealing to me. maybe use "jp-mode_strict" so that the parameter is always within the string, so that when another parameter must be given it can be done by "jp-mode_normal-parameterx_normal" that way normal can be used for all upcomming additional parameters
Regarding the tests. If it is only one test that fails then ok. But if there are multiple tests that fail due to it, I'd ask, if it is possible to automatically detect these cases (maybe by the usage of a certain character) and not check them or maybe even automatically fix them within the test tool, (by replacing those characters).

So far, the "strict" language option seems the best. I'll do it. I'll make "ja-jp_strict" or "ja_strict" trigger the strict mode.
The tests have more failures, but this is the only one that is related to strict vs. normal rendering. The next headache is the Object Replacement Character. It seems I need to add an additional row/column absent in table 2 to implement fully LB20. The reference code in UAX#14 does not implement this either.

I don't like the "mode_strict" suggestion. I don't think encoding parameters in the string is a good idea. It just happens to work for mode, because it's essentially a variation of the Japanese language, which is what lang is for.
Object replacement character: I don't know if you remember, but that was one of my first contributions (if not the first) to the project, liblinebreak was triggering an assert with this char. This char is actually quite common, at least in my usecase, so let's make it work. :P

One gotcha, I cannot even use "ja...strict" in the test, as the "ja" language changes the line breaking behaviour and makes more tests fail. It seems I can only check for the "_strict" suffix.

We have language specific behaviour in the linebreak algo? I didn't know that. I guess yes, just check for the prefix. Btw, I prefer using a - over _ so it can't be mistaken as a location.
So:
"ja-strict"
"ja_JP-strict"
over
"ja_strict"
"ja_JP_strict"

Oh, you are right. I was confused by "_" and "-". I should check for "-strict". The complication is that we use "zh_CN" in shell LANG, but "zh-CN" in HTML lang attribute. :-(

I may be mistaken, but if memory serves, zh_CN is the standard way of doing it, regardless of what there may be in html.

http://stackoverflow.com/questions/11318961/what-is-the-difference-between-html-lang-en-and-html-lang-en-us
:-)

OK. One small improvement committed and pushed. Now test suite completeness is 97%.

I fixed the U+FFFC issue. However, there are still quite a few failures, and I would like you to check the failed tests and give some comments.
These words are in LineBreakTest-9.0.0.txt:

Note: The Line Break tests use tailoring of numbers described in Example 7 of Section 8.2 Examples of Customization.
They also differ from the results produced by a pair table implementation in sequences like: ZW SP CL.

I can see the following categories about failures:

The number-related cases as mentioned above.
Similar cases where UAX#14 treats as indirect break opportunity but the test treats as direct break opportunity, as in "%(".
The current implementation does not break after leading spaces, but the test does.
Treatment of pairing RI characters (cannot be covered by the pair table).

Personally, I consider only the last category as bugs and would like to fix them. This would lead to impossibility to achieve 100% test pass.
What are your opinions?

RI treatment is done now.

Generally I do agree with you observations. Two questions though: what difference makes the tayloring in the example... it doesn't state that in the text of the example as far as I can see.
2nd have you ever though about a good way that users of the library can do the changes for this kind of tayloring without requiring to change the library? I am just curious here...

It seems to me Example 7 of Section 8.2 gives tailoring that is better suited for a regexp-based implementation. One specific example is that the current implementation does not allow any breaks in either "12,345" or "word,3", but Example 7 and the tailoring would allow breaking after the comma in the latter case. It is arguably better, but requires more complicated processing, and the benefit is not that big in my eyes.

I'm OK with ignoring the offending lines. I think the best solution would be to add a mechanism to ignore specific lines of the test, so this way our suite would still pass indicating that everything is as expected, but we would still be able to use the unicode test data. If you are OK with this, I can implement it. I'll just ignore all of the tests currently failing.

I am curious how you wanted to do that. I thought about it, but did not come up with a good solution. E.g. if I skip tests with numbers, I may skip more tests than the failing ones. . . .

Skip tests based on line numbers. Why more tests than the failing ones? We know exactly which are failing, and I'll only skip those. Next time, when we update to Unicode 10, we will have to review the tests we skip again, but that's not much of a big deal, and better than the alternatives.

OK, that will work (I was thinking along the line of regex). The line numbers in the test probably are not that stable, but I really do not have a better solution.

I was considering regex, but as you said, it's too dangerous.

@adah1972, please make a new release.

source: gharchive/issue

authors: adah1972 roever tasn

license: Zlib

license_type: permissive

license_source: github-api


text:
+verbosity at component loading AttributeError

targets #380

@adamghill LGTM, can we merge this?

Sorry this took so long, but it is merged now.

source: gharchive/pull-request

authors: adamghill hendi nerdoc

repo: adamghill/django-unicorn

license: MIT


text:
Added support for Exoscale.

I needed support for Exoscale. They are using Cloudstack as platform, but we use their own terraform plugin that is not yet supported (https://github.com/exoscale/terraform-provider-exoscale).
This small patch is sufficient to build an inventory from terraform's tftate file produced with this plugin.

Thank you! Would you mind adding an example of an Exoscale resource to parser_test.go, so we can be sure not to break this in the future?

I have updated parser_test.go

authors: PhilippeChepy adammck

repo: adammck/terraform-inventory

license: mit

license_source: bigquery


text:
🛑 relay.dresden.network is down

In 6827eeb, relay.dresden.network (https://relay.dresden.network/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.dresden.network is back up in fd08a4b after 17 minutes.


text:
🛑 mastodon-relay.moew.science is down

In e14720c, mastodon-relay.moew.science (https://mastodon-relay.moew.science/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: mastodon-relay.moew.science is back up in 750fc69 after 8 minutes.


text:
🛑 relay.mistli.net is down

In 5fd50d6, relay.mistli.net (https://relay.mistli.net/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.mistli.net is back up in 3ad542e after 34 minutes.


text:
🛑 relay.c.im is down

In 32c0daa, relay.c.im (https://relay.c.im/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.c.im is back up in 51e2626.


text:
🛑 relay.masto.social is down

In ee1e9cd, relay.masto.social (https://relay.masto.social/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.masto.social is back up in d7daa4d.


text:
🛑 relay.homunyan.com is down

In bca1e43, relay.homunyan.com (https://relay.homunyan.com/actor) was down:

HTTP code: 0
Response time: 0 ms

Resolved: relay.homunyan.com is back up in 1e12bab.


text:
Can you provide an example of a situation where an iOS app is running in (Designed for iPad) mode?

Can you provide an example of a situation where an iOS app is running in (Designed for iPad) mode? 😊📱

The pointer interaction is working for me in Designed for iPad mode. I'm not quite sure how pinch/pan would work, I'll have to see how the touch locations for multi-finger gestures appear on a trackpad. good idea :)

Most likely, you won't have information about numberOfTouches and touch positions. Only the initial pointer point and scale. A good challenge is to implement it ;) 🚀

authors: adamwulf tigrim

repo: adamwulf/HandShadowsExample


text:
Do not always regenerate site; crashes on Heroku

As far as I understand, rack-jekyll now always (re)generates the site (see 1088b1b615198e33a96a3bb4c601676b62ea59d4). This crashes on Heroku (read-only file system)!
Besides, also users who do not deploy on Heroku should have the option to avoid regeneration; it's very slow for a big site, so in this case deploying a previously generated site might be the better option.
The default behaviour should IMO be to not regenerate an already existing _site dir; this is the behaviour of the current (but outdated) RubyGems release, 0.4.1.
Note that we failed to switch www.ruby-lang.org to Jekyll 2 with both of the following approaches:

use rack-jekyll from RubyGems: in combination with Jekyll 2 this forces a very old version of rack-jekyll (0.3.5, because of dependencies); this version is buggy and truncates files due to wrong Content-Length headers
use the development branch version from GitHub: this version crashes on Heroku, because of the changed (re)generation behaviour

Please fix this issue and release a new version.

See ruby/www.ruby-lang.org/issues/1073.

Currently we use a patched version of rack-jekyll 0.4.1 that has more liberal dependencies on Jekyll and rake, see my fork stomar/rack-jekyll. I would prefer switching back to official gem releases some time in the future, though.

Anyone looking for a quick fix should think about changing your rack-jekyll dependency in your Gemfile to the following: gem 'rack-jekyll', '~> 0.4.1', :git=>'git://github.com/adaoraul/rack-jekyll.git'.
This will grab the gem from this github repository instead of rubygems (which is outdated).

Solved with 0.4.2.

authors: lcfg stomar

repo: adaoraul/rack-jekyll


text:
Temporarily serve a page while the site is rendering.

In environments like OpenShift, Rack starts before the site is rendered.
The 'wait_page' feature allows Rack to serve an attractive page while
rendering progresses letting the user know that they should check back
soon instead of a generic error page with minimal information.

Any particular reason this got closed?  Or are you just not interested in the feature itself?

Sorry, i closed the wrong pull request. I'll consider your pull request today.

Merged! Thank you @awood

authors: adaoraul awood


text:
Can't use github master version

Trying to use the master version, running into this error:
/Users/Patrick/.rvm/rubies/ruby-2.2.0/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in require': cannot load such file -- parse-ruby-client (LoadError) 	from /Users/Patrick/.rvm/rubies/ruby-2.2.0/lib/ruby/site_ruby/2.2.0/rubygems/core_ext/kernel_require.rb:54:in require'
from app.rb:1:in `'
This is my Gemfile:
source 'https://rubygems.org'
gem 'sinatra'
gem 'parse-ruby-client', git: 'https://github.com/adelevie/parse-ruby-client.git'
Any idea what could be causing the problem?

@patwhitehead1 what's in your app.rb at line 1?

Additionally, what command are you using to run your code?

This is all I have in app.rb:
require 'sinatra'
require 'parse-ruby-client'

get '/hi' do
  "Hello World!"
end

And I'm running it with ruby app.rb

This seems to work when I run it with:
bundle exec ruby app.rb

@patwhitehead1 yes, you need to execute with bundle. See http://bundler.io/v1.11/bundle_exec.html
This command executes the command, making all gems specified in the Gemfile(5) available to require in Ruby programs.

authors: Xavdidtheshadow patwhitehead1 rhymes

repo: adelevie/parse-ruby-client


text:
chore: update peerDeps to support/remove warning when installing in react 18 project

Related issue https://github.com/adiathasan/mui-react-hook-form-plus/issues/3
What's updated

update package.json react peerDeps

Thank you again bryantobing12 🎉

repo: adiathasan/mui-react-hook-form-plus


text:
Background color of search results

Describe the bug
Search results are not clearly visible because of it's background color
Screenshots

Can You please assign it to me. I would like to contribute

@adityakmrmishra Could I know why is this issue closed?

Don't worry there was a little confusion I'm reopening it

@adityakmrmishra I have made changes which solves this issue and pulled a request #34

repo: adityakmrmishra/Geet


text:
新版如何docker升级呢？

之前是2.8'1，如何docker下升级最新版本呢？谢谢

拉取新版本镜像
停用老版本容器，如果老版本conf目录挂载出来了，直接停；如果没有挂载，新加个挂载目录，进入容器bash，使用命令把conf目录复制到新挂载的目录，复制出来的conf目录用于下一步
创建新版本容器，挂载conf配置目录

版本2.8.1

装载路径该如何填写呢？尝试/conf 挂载，但是配置目录没有新文件生成，已经给了写入权限，谢谢

repo: adminpass/aliyundrive-subscribe


text:
Reloading configuration first adds hooks, then removes them

OS: CentOS Linux release 7.1.1503 (Core)
webhook version: from https://github.com/adnanh/webhook/pull/143
When I edit hooks.yaml with vim then after saving it I see the following in webhook log:
Jul 07 09:56:36 host.company.com webhook[16452]: [webhook] 2017/07/07 09:56:36 hooks file /opt/webhook/current/conf/hooks.yaml overwritten
Jul 07 09:56:36 host.company.com webhook[16452]: [webhook] 2017/07/07 09:56:36 attempting to reload hooks from /opt/webhook/current/conf/hooks.yaml
Jul 07 09:56:36 host.company.com webhook[16452]: [webhook] 2017/07/07 09:56:36 found 2 hook(s) in file
Jul 07 09:56:36 host.company.com webhook[16452]: [webhook] 2017/07/07 09:56:36         loaded: merge-request
Jul 07 09:56:36 host.company.com webhook[16452]: [webhook] 2017/07/07 09:56:36         loaded: monitoring
Jul 07 09:56:36 host.company.com webhook[16452]: [webhook] 2017/07/07 09:56:36 hooks file /opt/webhook/current/conf/hooks.yaml removed, no longer watching this file for changes, removing hooks that were loaded from it
Jul 07 09:56:36 host.company.com webhook[16452]: [webhook] 2017/07/07 09:56:36         removing: merge-request
Jul 07 09:56:36 host.company.com webhook[16452]: [webhook] 2017/07/07 09:56:36         removing: monitoring
Jul 07 09:56:36 host.company.com webhook[16452]: [webhook] 2017/07/07 09:56:36 removed 2 hook(s) that were loaded from file /opt/webhook/current/conf/hooks.yaml

..and the hooks are in fact not loaded - requests to them result in 404s.

This is the issue of the *nix signals and editor implementations, instead of sending MODIFIED signal when overwriting the existing file, some editors actually delete the file, and create a new one with the new contents (i.e. direct result of working in a temporary file, and then copying it over the original one).
Try using different editor, or if that is not an option, or does not help, you will unfortunately be unable to use the -hotreload flag. In that case, you can still use kill -USR1 webhookpid to reload the hooks without the webhook restart.

Thanks for a prompt answer! :)
I would add a warning in the docs if this feature is not compatible with so popular editors as vim then.

Feel free to do it! :-)

Fixed in v2.6.6 by #172

authors: adnanh gdubicki

repo: adnanh/webhook


text:
Remove attributes from elements

Elements in snap.svg have the attr method, to get or set attributes to them.
But they lack the removeAttr counterpart, to delete those same attributes.
I used jquery as a workaround for this, but it would be nice to have the method on snap objects as well.

Tried just setting it to null/'' or something ?

Yeah, setting it to null just changes the attribute value to the string "null".

In that case, I assume you could just do   element.node.removeAttribute("class"); or have a plugin which calls that, or have a simple plugin...
Snap.plugin( function( Snap, Element, Paper, global ) {         Element.prototype.removeAttr = function( attr ) {             return this.node.removeAttribute( attr )         }; });

Nice! I wasn't aware of the node attribute. Will certainly do this. :+1:
Anyway, I think this should be a nice addition to Snap object :smile:

Setting attribute to empty string will remove it.

authors: DmitryBaranovskiy ibrierley vlribeiro


text:
Incorrect generation of action urls when using another AIO_runtime_apihost

Describe the bug

Urls generated in the UI within the web-src/src/config.json use the CDN domain adobeio-static.net which internally points to the Runtime Apihost adobeioruntime.net.
Urls shown in the terminal for headless apps use a subdomain namespace.apihost

both are a problem, in 1. the actions will be deployed to the apihost specified in .env while the UI would use the CDN domain that points to adobeioruntime.net. In 2. the OpenWhisk apihost might not support namespace subdomains as this is a feature implemented in runtime.
To Reproduce

create an app with a web-assets and actions
set AIO_runtime_apihost to a different OpenWhisk host via .env
deploy the app
action urls in the UI point to adobeio-static.net meaning there are not accessible

Expected behavior
Use the specified apihost if different than adobeioruntime.net to generate the action urls in web-src/src/config.json
Workaround
hardcode urls in the UI

Assigning to @rajarju for review while he's working on UI related enhancements.

authors: meryllblanchet moritzraho

repo: adobe/aio-cli-plugin-app


text:
Update getLibraryInfo functionalTest to include applyPropositions

Description
Update getLibraryInfo functional test to include new applyPropositions changes.

Related Issue
applyPropositions updated without updating libraryInfo commands.

Motivation and Context
Passes c2589 functionalTest

Screenshots (if appropriate):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Improvement (non-breaking change which does not add functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[x] I have signed the Adobe Open Source CLA or I'm an Adobe employee.
[x] I have made any necessary test changes and all tests pass.
[x] I have run the Sandbox successfully.

Thanks for fixing this. I updated the v2.11.0 branch to include this fix.

authors: adityaguruprasad jonsnyder

repo: adobe/alloy


text:
App with target SDK 31+ crashes on Android 12+

Expected Behaviour
App does not crash when starting location monitoring.
Actual Behaviour
App crashes when starting location monitoring.
Reproduce Scenario (including but not limited to)
Start location monitoring in build targeting SDK 31+ on Android 12+ device.
Google are now requiring all apps to target at least SDK 31.
places-monitor-android does not support SDK 31+, because it doesn't use the correct flags for pending intents.
Steps to Reproduce

Build Android app with target SDK 31+
Call FlutterACPPlacesMonitor.start() on Android 12+ device.

Platform and Version
Flutter 3.3.9, flutter_acpplaces_monitor 2.0.1, Android 12
Sample Code that illustrates the problem
FlutterACPPlacesMonitor.start()
Logs taken while reproducing problem
E/AndroidRuntime(13768): java.lang.IllegalArgumentException: <redacted>: Targeting S+ (version 31 and above) requires that one of FLAG_IMMUTABLE or FLAG_MUTABLE be specified when creating a PendingIntent.
E/AndroidRuntime(13768): Strongly consider using FLAG_IMMUTABLE, only use FLAG_MUTABLE if some functionality depends on the PendingIntent being mutable, e.g. if it needs to be used with inline replies or bubbles.
E/AndroidRuntime(13768):        at android.app.PendingIntent.checkFlags(PendingIntent.java:375)
E/AndroidRuntime(13768):        at android.app.PendingIntent.getBroadcastAsUser(PendingIntent.java:645)
E/AndroidRuntime(13768):        at android.app.PendingIntent.getBroadcast(PendingIntent.java:632)
E/AndroidRuntime(13768):        at com.adobe.marketing.mobile.PlacesLocationManager.getPendingIntent(PlacesLocationManager.java:375)
E/AndroidRuntime(13768):        at com.adobe.marketing.mobile.PlacesLocationManager.access$100(PlacesLocationManager.java:45)
E/AndroidRuntime(13768):        at com.adobe.marketing.mobile.PlacesLocationManager$1.onSuccess(PlacesLocationManager.java:139)
E/AndroidRuntime(13768):        at com.adobe.marketing.mobile.PlacesLocationManager$1.onSuccess(PlacesLocationManager.java:127)
E/AndroidRuntime(13768):        at com.google.android.gms.tasks.zzm.run(com.google.android.gms:play-services-tasks@@18.0.2:1)
E/AndroidRuntime(13768):        at android.os.Handler.handleCallback(Handler.java:938)
E/AndroidRuntime(13768):        at android.os.Handler.dispatchMessage(Handler.java:99)
E/AndroidRuntime(13768):        at android.os.Looper.loopOnce(Looper.java:201)
E/AndroidRuntime(13768):        at android.os.Looper.loop(Looper.java:288)
E/AndroidRuntime(13768):        at android.app.ActivityThread.main(ActivityThread.java:7839)
E/AndroidRuntime(13768):        at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(13768):        at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:548)
E/AndroidRuntime(13768):        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1003)

??

Places monitor is no longer supported, it is deprecated in August 2021.

@cacheung Yes, I know. I had to create my own fork of it to make it work. Why are you using it in this package, and why is there no mention of that in the documentation for this package?

@peter-nilsson-scotts Thanks for the feedback.  We added the deprecation message in the readme.
Thanks,
Calise

@cacheung Thanks. Don't forget to update https://pub.dev/packages/flutter_acpplaces_monitor as well. :-)

We won't be able to update the readme there without a release. We marked the package DISCOUNTIUED.
Thanks,
Calise


text:
Include Backend URL in Gateway Response

let's say you have https://unviersal.runtime.com/helix-services/git-resolve-ref... and it is routed to AZURE and fails.
so it's probably important to include the backend request url in the response....
Originally posted by @tripodsan in https://github.com/adobe/helix-deploy/issues/20#issuecomment-745001907

@trieloff how is this fixed by #20 ?

authors: trieloff tripodsan

repo: adobe/helix-deploy


text:
feat(rum-explorer) conversions can be tuned in a headless mode

It provides a headless alternative for #523 - will still need some sort of a ux on top.

@trieloff - do you want me to make further changes ? Perhaps squashing commits ?

repo: adobe/helix-website


text:
Add documentation for CSS variables usage

We need to add documentation for using Spectrum CSS with the CSS custom properties model introduced in #108

Threw together a Codepen in the meantime: https://codepen.io/lazd/pen/axXMRL?editors=1100

repo: adobe/spectrum-css


text:
TNT-41936 - telemetry handling for server state and double digit precision for telemetry decimal values

Description

New TelemetryProvider fn for serverState telemetry entries (used by at.js)
Limit precision for execution and parsing telemetry values to max of 2 fixed decimal digits

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

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

Coverage decreased (-0.2%) to 92.446% when pulling 6607e19beb57920dad6f96f788abcf2edb6f5608 on dcottingham:TNT-41936 into 5f9b177a57d20c44982a58326d2302fd86f84187 on adobe:main.

authors: coveralls dcottingham

repo: adobe/target-nodejs-sdk


text:
[PEP] Load FEDS After IMS

One experiment idea from the GNAV team is that we can test out always load feds after ims is loaded. This could help make IMS and adobeProfile stabler and shouldn't have too much impact on our pages.
Resolves: https://jira.corp.adobe.com/browse/MWPW-137828?filter=381833
Test URLs:

Before: https://stage--express--adobecom.hlx.page/express/
After: https://feds-after-ims--express--adobecom.hlx.page/express/

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

Project coverage is 34.23%. Comparing base (29b0aad) to head (541a452).

Additional details and impacted files
@@            Coverage Diff             @@
##            stage     #679      +/-   ##
==========================================
- Coverage   34.50%   34.23%   -0.27%
==========================================
  Files         129      129
  Lines       25117    25117
==========================================
- Hits         8667     8600      -67
- Misses      16450    16517      +67

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

authors: JingleH codecov-commenter

repo: adobecom/express


text:
A fatal error has been detected by the Java Runtime Environment

Please provide a brief summary of the bug
EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffc66780056, pid=13732, tid=17052
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.6+10 (17.0.6+10) (build 17.0.6+10)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.6+10 (17.0.6+10, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
#
V  [jvm.dll+0x7a0056]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# C:\Users\Jack\AppData\Roaming\PrismLauncher\instances\FTB StoneBlock 3.minecraft\hs_err_pid13732.log
#
# If you would like to submit a bug report, please visit:
#   https://github.com/adoptium/adoptium-support/issues
#
[thread 820 also had an error]
AL lib: (EE) alc_cleanup: 1 device not closed
Process exited with code 1.
Please provide steps to reproduce where possible
ok so I have the prism launcher and java 17 and I am trying to play mc with my brother on FTB Stone Block 3 but when I got to join the sever I get in then 2 seconds late it crashes and I don't know why I tried everything bewtten rebooting the pc to uninstalling java and reinstalling it and it still does the same thing
Expected Results
I just expected to be able to play without it crashing for no reason
Actual Results
I get in and then it immediately crashes
What Java Version are you using?
17.6.10
What is your operating system and platform?
windows 11
How did you install Java?
ninte
Did it work before?
no
Did you test with other Java versions?
no because it wants java 17
Relevant log output
No response

same happened to me, but instead in trying to run it in a development enviroment.
im using JDK17.0.6_10 trying to open minecraft gradle

this is the message i get
#
# A fatal error has been detected by the Java Runtime Environment:
#
#  EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffc6c262b60, pid=15592, tid=6708
#
# JRE version: OpenJDK Runtime Environment Temurin-17.0.6+10 (17.0.6+10) (build 17.0.6+10)
# Java VM: OpenJDK 64-Bit Server VM Temurin-17.0.6+10 (17.0.6+10, mixed mode, sharing, tiered, compressed oops, compressed class ptrs, g1 gc, windows-amd64)
# Problematic frame:
# C  [atio6axx.dll+0x192b60]
#
# No core dump will be written. Minidumps are not enabled by default on client versions of Windows
#
# An error report file with more information is saved as:
# D:\Arquivos do Usuario\Documentos\GitHub\Rereskillable-Rereforked\run\hs_err_pid15592.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.
#

[error occurred during error reporting (), id 0xc0000005, EXCEPTION_ACCESS_VIOLATION (0xc0000005) at pc=0x00007ffc6e04da79]

Most of the time this is a video driver issue.  Please update to latest NVidia or AMD drivers.

authors: Jacktrooperc dotRelith karianna

repo: adoptium/adoptium-support


text:
Release pipeline generation make use of "USE_ADOPT_SHELL_SCRIPTS": false, which fails on Mac

Release pipeline jobs use the "user" configuration pointing at the user remote tag/branch, but the necessary dual pass Mac eclipse-codesign depends on  "USE_ADOPT_SHELL_SCRIPTS": true.

so to not rush for a big change just before 2023 Jan release, propose to make a workaround for Mac release pipeline.
the idea is to: passing down USE_ADOPT_SHELL_SCRIPTS when release-openjdkXX-pipeline trigger downstream job
jdkXX u-release-mac-x64-temurin and jdkXXu-release-mac-aarch64-temurin
so the jobs jdkXX u-release-mac-x64-temurin and jdkXXu-release-mac-aarch64-temurin will still use "master" branches from ci-jenkins-pipeline and temurin-build for this release.
We still need a proper long term solution for this fix.

some thoughts for future fix:

less code change but add new step before release process
before we create release tag (e.g v2023.01.09) for ci-jenkins-pipeline and temurin-build and helper, we create a new commit to change the content of defaults.json (snippet and assume two new tags both called v2023.01.09)
from

    "repository"             : {
        "build_url"          : "https://github.com/adoptium/temurin-build.git",
        "build_branch"       : "master",
        "test_dirs"          : "/test/functional",
        "pipeline_url"       : "https://github.com/adoptium/ci-jenkins-pipelines.git",
        "pipeline_branch"    : "master",
        "helper_ref"         : "master"
    },

to
    "repository"             : {
        "build_url"          : "https://github.com/adoptium/temurin-build.git",
        "build_branch"       : "v2023.01.09",
        "test_dirs"          : "/test/functional",
        "pipeline_url"       : "https://github.com/adoptium/ci-jenkins-pipelines.git",
        "pipeline_branch"    : "v2023.01.09",
        "helper_ref"         : "v2023.01.09"
    },

along with changes from https://github.com/zdtsw/ci-jenkins-pipelines/tree/issue/571_2
in this case, we have USE_ADOPT_SHELL_SCRIPTS to true for all release pipelines and jobs
the branch names are defined in both DEFAULTS_JSON and ADOPT_DEFAULTS_JSON, we do not use the values set in USER_REMOTE_CONFIGS
Drawback of this is: the commit with changes in defaults.json cannot get merged into master. which means, release champion need to branch out from master, do the change, push to origin repo, tag it.

modify in ADOPT_DEFAULTS_JSON  and DEFAULTS_JSON by code
still need the change in https://github.com/zdtsw/ci-jenkins-pipelines/blob/issue/571_2/pipelines/build/regeneration/release_pipeline_generator.groovy
then in build_job_generator.groovy update ADOPT_DEFAULTS_JSON and DEFAULTS_JSON

ADOPT_DEFAULTS_JSON['repository']['pipeline_branch'] = ${params.REPOSITORY_BRANCH}
ADOPT_DEFAULTS_JSON['repository']['build_branch'] = ${params.REPOSITORY_BRANCH}
DEFAULTS_JSON['repository']['pipeline_branch'] = ${params.REPOSITORY_BRANCH}
DEFAULTS_JSON['repository']['build_branch'] = ${params.REPOSITORY_BRANCH}

need to add  support for DEFAULTS_JSON['repository']['helper_ref'] and ADOPT_DEFAULTS_JSON['repository']['helper_ref'] which is not setting in https://ci.adoptopenjdk.net/job/build-scripts/job/utils/job/release_pipeline_jobs_generator_jdkXXu yet

Workaround still fails: https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/release/job/jobs/job/jdk17u/job/jdk17u-release-mac-x64-temurin/8/consoleFull

@zdtsw I think we should change to doing a release branch, like for aqa-tests, and we change defaults.json in it...

i think, https://ci.adoptopenjdk.net/job/build-scripts/job/jobs/job/release/job/jobs/job/jdk17u/job/jdk17u-release-mac-x64-temurin/8/ was from the old run, not after last evening's regenerate.

i see the problem from last night's run, i will fix that.

@zdtsw I think we should change to doing a release branch, like for aqa-tests, and we change defaults.json in it...

yeah, seems it is difficult to hijack USE_ADOPT_SHELL_SCRIPTS,
changed to set tag in defaults.json https://github.com/adoptium/ci-jenkins-pipelines/pull/576

authors: andrew-m-leonard zdtsw

repo: adoptium/ci-jenkins-pipelines


text:
Re-order build pipeline build stages prio to AQA-tests

Fixes #1086
Re-order the build stages to before AQA-tests, and gate running AQA-tests on the successful completetion of all the build stages.

run tests


text:
aqa-tests/terminateTestProcesses.sh terminating executors on linux host dockerhost-equinix-ubuntu2004-x64-1

dockerhost-equinix-ubuntu2004-x64-1 is a docker "host" with 5 container executors, however it seems test jobs are running "directly" on dockerhost-equinix-ubuntu2004-x64-1, which means the aqa-tests/terminateTestProcesses.sh terminates other test jobs, see:
Teminating job: https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/613/consoleFull
"Terminated" job: https://ci.adoptium.net/job/Test_openjdk11_hs_extended.system_x86-64_linux/865/consoleFull
Has the docker host being incorrectly labelled?
From the config log history looks like "ci.role.test" got added to the host node on 20th Nov 2023: https://ci.adoptium.net/computer/dockerhost-equinix-ubuntu2004-x64-1/jobConfigHistory/configOutput?type=xml&timestamp=2023-11-20_18-30-39

Reverted the label changes.
Noting that https://github.com/adoptium/infrastructure/issues/3279 is related as those jobs were (incorrectly I expect) running on this machine too.

authors: andrew-m-leonard sxa

repo: adoptium/infrastructure


text:
Verify CycloneDX dependencies after download

Currently, we download a set of cyclonedx dependencies at the end of each build.
However, we do not appear to verify the contents of these files, so when curl downloads a html error message instead of the .jar it was actually trying to download, we don't find out until we try to use the .jar file and fail.
Example: https://ci.adoptium.net/job/build-scripts/job/jobs/job/release/job/jobs/job/jdk11u/job/jdk11u-release-alpine-linux-x64-temurin/5/console
In that scenario, we tried to download the jackson-databind jar file, but the contents were this:

<title>502 Bad Gateway</title>

502 Bad Gateway

So I ask that we verify the file contents, ideally followed by a pause and a retry if the download failed.
Also, a more useful error message would be good. So if we did get HTML, maybe cat the file contents?

I think I've found the problem.
A conditional does not modify an existing property if the value has already been set, and any property in a macrodef appears to persist between executions.
So if my checksum matches the download's checksum, the property is set to true. If the next match fails, we use the property value from the previous download, and we only claim that the checksum matched. Which is wrong.
To fix this, I propose modifying the download-file madrodef like so:
	<local name="downloaded.file.checksum"/>
      <checksum file="@{destdir}/@{destfile}" algorithm="@{algorithm}" property="downloaded.file.checksum" />
	<local name="checksum.match"/>
      <condition property="checksum.match">
        <equals arg1="${downloaded.file.checksum}" arg2="@{checksum}"/>
      </condition>

The addition of those two "local" elements enforces the macrodef-instance-only scope of those two properties, ensuring that we're using a fresh, unset property every time we run the check.
Now, I haven't created a PR because several of the downloads now fail to match their checksums. I'm identifying all of the failures and calculating new checksums.

Ok, of the 9 SBOM dependencies, these 3 match their checksums:

cyclonedx-core-java.jar
commons-codec.jar
commons-io.jar

And these 6 do not:

jackson-core.jar
jackson-dataformat-xml.jar
jackson-databind.jar
jackson-annotations.jar
json-schema.jar
github-package-url.jar

For each of the latter 6 jars, my plan is to:

Verifying their source website via the lock symbol on the browser's address bar.
Download each jar.
Verify each jar using the checksums on their website.
Copy that checksum into our code.

Once complete, and tested locally, I'll create a PR.

https://github.com/adoptium/temurin-build/pull/3424

PR is merged. Closing this issue as resolved.

repo: adoptium/temurin-build


text:
chore(deps): update renovatebot/github-action action to v39.2.4

This PR contains the following updates:

Package
Type
Update
Change

renovatebot/github-action
action
patch
v39.2.3 -> v39.2.4

Release Notes

renovatebot/github-action (renovatebot/github-action)
v39.2.4
Compare Source
Documentation

update references to renovatebot/github-action to v39.2.3 (e0d1315)

Miscellaneous Chores

deps: lock file maintenance (f38d4d6)
deps: lock file maintenance (1bb9d4a)
deps: update dependency eslint to v8.56.0 (3102427)
deps: update dependency ts-node to v10.9.2 (53af493)
deps: update linters to v6.14.0 (70df8a3)
deps: update linters to v6.15.0 (9ab8225)

Build System

deps: update dependency @semantic-release/github to v9.2.6 (e36d581)

Continuous Integration

deps: update renovate docker tag to v37.100.0 (b8d7a01)
deps: update renovate docker tag to v37.100.1 (6102c20)
deps: update renovate docker tag to v37.101.0 (d6c3db5)
deps: update renovate docker tag to v37.102.0 (062c41b)
deps: update renovate docker tag to v37.102.1 (1a02fa1)
deps: update renovate docker tag to v37.104.1 (622e856)
deps: update renovate docker tag to v37.105.0 (09cf62b)
deps: update renovate docker tag to v37.105.1 (4c2ca89)
deps: update renovate docker tag to v37.105.3 (85451b7)
deps: update renovate docker tag to v37.107.0 (4621cfe)
deps: update renovate docker tag to v37.107.1 (af361d7)
deps: update renovate docker tag to v37.108.1 (40718c2)
deps: update renovate docker tag to v37.109.0 (be63e1f)
deps: update renovate docker tag to v37.110.0 (6de6cea)
deps: update renovate docker tag to v37.111.1 (7d6f1b3)
deps: update renovate docker tag to v37.98.0 (49750fe)
deps: update renovate docker tag to v37.98.1 (35f3128)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Edited/Blocked Notification
Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.
You can manually request rebase by checking the rebase/retry box above.
⚠ Warning: custom changes will be lost.

repo: adrien-guesnel/portfolio


text:
no output generated

Describe the bug
Trying to run on Copernicus and not getting any output
To Reproduce
python run.py -p "/proj/ads/abstracts/data/EGU/EGU.101623/wes-8-1625-2023.xml" -t jats -f copernicus.110323
Additional context
log file complaint: 'NoneType' object has no attribute 'find'
{"asctime": "2023-11-03T18:32:31.150Z", "name": "manual-parser", "processName": "MainProcess", "filename": "run.py", "funcName": "main", "levelname": "WARNING", "lineno": 145, "module": "run", "threadName": "MainThread", "message": "Error parsing record (/proj/ads/abstracts/data/EGU/EGU.101623/wes-8-1625-2023.xml): 'NoneType' object has no attribute 'find'", "timestamp": "2023-11-03T18:32:31.150Z", "hostname": "adsnest.cfa.harvard.edu"}

The problem is primarily with ADSManualParser here.  One issue is that the current production directory ingest/ADSManualParser is behind the current github main @HEAD.  Another issue is that the content type is copernicus rather than jats.  This will be resolved when I rebuild the production directory's virtual environment (Monday Nov 6, 2023).

You can now get a record using python run.py -p "/proj/ads/abstracts/data/EGU/EGU.101623/wes-8-1625-2023.xml" -t copernicus -f copernicus.110323.  Note that the pagination is not being captured correctly, which is a bug in the copernicus parser.

repo: adsabs/ADSIngestParser


text:
Icon request: Hexonet

URL of the site or app (required): https://www.hexonet.net/
Logo resources for the icon (optional, but recommended): https://www.hexonet.net/assets/pdf/HEXONET_brand_guidelines.pdf

Here you go!
https://github.com/aegis-icons/aegis-icons/blob/master/SVG/HEXONET.svg
❓ How to add icon(s) to Aegis?

repo: aegis-icons/aegis-icons


text:
Icon request: Arch Linux

URL of the site or app https://archlinux.org
Logo resources for the icon https://archlinux.org/art/

Here you go!
https://github.com/aegis-icons/aegis-icons/blob/master/SVG/Arch Linux.svg
❓ How to add icon(s) to Aegis?


text:
Icon request: GNOME

URL of the site or app
https://www.gnome.org/
Logo resources for the icon
https://foundation.gnome.org/logo-and-trademarks/
Anything else?
There Forum Has An Authenticator based Two-Step Verification https://discourse.gnome.org/
PS. Simple Icons Also Has One, If You Wanna Use That As A Reference. https://github.com/simple-icons/simple-icons/blob/521c96fd04b0ea93034db8715eda5a4de27a58bb/icons/gnome.svg

Rejected: only really popular forums can get their own icon.
Use one of the Discourse icons.


text:
not working any more

bot is not talking any more everybody miss them please bring bot back

bot restarted!

authors: aelesia cvaliente

repo: aelesia/reddit-bot-amos


text:
Add ability to runtime list / introspect resources

Checklist

[x] make test-all (UNIX) passes. CI will also test this
[x] unit and/or integration tests are included (if applicable)
[x] documentation is changed or added (if applicable)

Description of change
Inside https://github.com/aelsabbahy/goss/pull/607#discussion_r478365909 I made a hack to allow me to iterate over the different types of resources.
This PR introduces the same pattern to resources as exists already for outputs.
I spent an afternoon trying to come up with a way to cover this in a unit test that would start to fail if a new resource type was ever added, but didn't come up with something. I tried iterating over the exported structs inside of the resources package, but failed to find a way of checking whether they implemented the Resource interface; golang doesn't maintain a type registry, so this was some pretty gnarly reflection.
Having made that attempt, I actually now think it would be simpler to do something like:
var resourceTypes = map[string]Resource{
  "addr": Addr{},
  "command": Command{},
  ...
  "user": User{},
}

func Resources() map[string]Resource {
  return resourceTypes
}

and similarly for Outputers (but where the Outputer interface grows a FormatOptions() []string that returns a constant set.
The cons are that to add a new one, you have to remember add an entry to the map. I think this is no worse than the current setup, where you must remember to make the init that calls RegisterOutputer.
The pros, though:

no longer need the init entry per file (3 lines of code * 16)
no need for the RegisterResource or RegisterOutputer funcs, or mutexes, because the maps are already statically defined and externally, they're read-only via the getter func (unless I've misunderstood how by-value/by-ref works, of course, it wouldn't be the first time)
no need for the mutexes inside the of the Outputers() or FormatOptions()
since Outputer.FormatOptions() would now exist, IsValidFormatOption() becomes a map lookup

What do you think? I'd be happy to make a separate PR to change to this approach for Outputer, so you can see it, and if you like that more, that could merge and then I could adapt this one.

I agree with your observation, the simple map seems like the better solution.
The whole init/register thing is great if goss was being used as a library and we want to allow users to register their custom types, but that doesn't matter since the genny stuff won't work.
The outputs can be dynamically added without anything else breaking. So, changing that would drop that "feature".. but.. it's not exactly an advertised feature.
I say switch to simple maps and see if anyone complains

@aelsabbahy cool - I'll change this branch so that it moves to that pattern for both outputers and resources.

@aelsabbahy what do you think with the refactor to maps?

@ripienaar I would love your take on this. You're the only one I know who may be impacted by this.

I would like to create a registry of all known types and eventually have the ability to register new resources on the fly when embedded, so this seems like a tiny step in the right direction - getting where I want is a giant undertaking, maybe over the holidays end of year hehe

authors: aelsabbahy petemounce ripienaar

repo: aelsabbahy/goss


text:
[BUG] forecaster.cutoff should be Period and Timestamp not PeriodIndex and DatetimeIndex

Describe the bug
There was a new bug introduced with sktime==0.16.0, the cutoff attribute of a forecaster is now PeriodIndex but in past it was Period, same for Timestamp and DatetimeIndex
To Reproduce
from sktime.datasets import load_airline
from sktime.forecasting.naive import NaiveForecaster
y = load_airline()
forecaster = NaiveForecaster(strategy="drift")
forecaster.fit(y)

y_pred = forecaster.predict(fh=[1,2,3])
forecaster.cutoff

With sktime==0.15.1 this returns Period('1960-12', 'M') and Timestamp('1960-12-31 00:00:00', freq='M')
With sktime==0.16.0 this returns PeriodIndex(['1960-12'], dtype='period[M]', name='Period') and DatetimeIndex(['1960-12-31'], dtype='datetime64[ns]', name='Period', freq='M')
Expected behavior

Additional context

Versions

related https://github.com/sktime/sktime/pull/2965

repo: aeon-toolkit/aeon


text:
[ENH] Add STOMP anomaly detector.

Reference Issues/PRs
Fixes #1638
What does this implement/fix? Explain your changes.
Adds the STOMP algorithm for anomaly detection.
PR checklist

For all contributions

[x] I've added myself to the list of contributors. Alternatively, you can use the @all-contributors bot to do this for you.
[x] The PR title starts with either [ENH], [MNT], [DOC], [BUG], [REF], [DEP] or [GOV] indicating whether the PR topic is related to enhancement, maintenance, documentation, bugs, refactoring, deprecation or governance.

For new estimators and functions

[x] I've added the estimator to the online API documentation.
[ ] (OPTIONAL) I've added myself as a __maintainer__ at the top of relevant files and want to be contacted regarding its maintenance. Unmaintained files may be removed. This is for the full file, and you should not add yourself if you are just making minor changes or do not want to help maintain its contents.

For developers with write access

[ ] (OPTIONAL) I've updated aeon's CODEOWNERS to receive notifications about future changes to these files.

Thanks for the contribution, looks good!

authors: MatthewMiddlehurst wenig


text:
🛑 r6 is down

In 107a4e1, r6 (https://r6.patriick.dev) was down:

HTTP code: 530
Response time: 114 ms

Resolved: r6 is back up in f17967a after 47 minutes.

repo: aeqe/upptime


text:
Adding OSS snapshot repo, mainly for jenkins client

@aliok @wtrocki @odra
Be able to use latest SNAPSHOT from our jenkins-client dependency. @khmarbaise was kind enough to deploy a snapshot to sonatypes OSS repo

Retest this please

Verified using local build. Merging back!

This is awesome.
Thanks @khmarbaise

authors: aliok matzew wtrocki

repo: aerogear/digger-java


text:
"npx graphback-cli generate" throws an error

Module: graphback-cli
Version: 0.16.2
Node.js / npm versions:
Example/snippet of the model that is causing issue

npx graphback-cli generate

Cannot find module 'graphql'
Require stack:
- .npm/_npx/83078/lib/node_modules/graphback-cli/node_modules/@graphback/core/dist/crud/mappingHelpers.js
- .npm/_npx/83078/lib/node_modules/graphback-cli/node_modules/@graphback/core/dist/crud/index.js
- .npm/_npx/83078/lib/node_modules/graphback-cli/node_modules/@graphback/core/dist/index.js
- .npm/_npx/83078/lib/node_modules/graphback-cli/node_modules/graphback/dist/index.js
- .npm/_npx/83078/lib/node_modules/graphback-cli/dist/components/generate.js
- .npm/_npx/83078/lib/node_modules/graphback-cli/dist/components/index.js
- .npm/_npx/83078/lib/node_modules/graphback-cli/dist/index.js

@craicoverflow I know you once encountered a similar issue, not sure if its related so opening this here to see if we are planning to do anything about it.

/cc @craicoverflow, @wtrocki
Automatically generated comment to notify maintainers

This is expected, users will have to run yarn graphback generate from inside their template for it to work. I see this as a docs issue.

This is expected, users will have to run yarn graphback generate from inside their template for it to work. I see this as a docs issue.

Sure, it what I have gone with when documenting the generate command #2053.
But id the project is missing graphql, it will still err right? What would be the impact of making  graphql a dependency in the cli?

Yes it would also error, the template will need graphql installed to use the generate command

What would be the impact of making graphql a dependency in the cli?

This would fix the CLI to a certain version, the CLI might have v15 of graphql but the user uses v14, these are incompatible.

Yes it would also error, the template will need graphql installed to use the generate command

I think I've that explicit-ed in the docs.

What would be the impact of making graphql a dependency in the cli?

This would fix the CLI to a certain version, the CLI might have v15 of graphql but the user uses v14, these are incompatible.

Sure, I am going to close this as docs will indicate how to use the cli.

repo: aerogear/graphback


text:
Openshift - VNC DISCONNECTED

Couldn't find the root cause of the following;
VNC Disconnected on Browser Screen and Pods have the following error logs.
Moon 2.5.0
RedHat Openshift
Kubernetes v1.23.5+012e945
Chrome Network

HTTP 101 : ws://moon.aerokube.local.apps.company.com/ws/vnc/chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76
HTTP 101 : ws://moon.aerokube.local.apps.company.com/ws/logs/chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76

2023/05/16 12:14:51 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: creating config map
2023/05/16 12:14:51 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: config map created
2023/05/16 12:14:51 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: creating pod
2023/05/16 12:14:51 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: pod created
2023/05/16 12:14:51 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: waiting pod
2023/05/16 12:14:55 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: pod is up
2023/05/16 12:14:55 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: waiting driver
2023/05/16 12:14:55 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: driver is up
2023/05/16 12:14:56 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: session created: 5.103s
2023/05/16 12:15:00 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: proxy from vnc: <nil>
2023/05/16 12:15:25 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: connect vnc: dial tcp 10.60.9.99:5900: connect: connection refused
2023/05/16 12:15:41 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: connect vnc: dial tcp 10.60.9.99:5900: connect: connection refused
2023/05/16 12:18:51 moon-6595754c5f-zqbvr: moon: chrome-112-0-5615-165-5-23578b6f-ffc1-4fed-aa18-0064452f8f76: connect vnc: dial tcp 10.60.9.99:5900: connect: connection refused

Config
vnc-server:
      repository: quay.io/aerokube/vnc-server
      resources:
        limits:
          cpu: 200m
          memory: 128Mi
        requests:
          cpu: 100m
          memory: 128Mi

x-server:
      repository: quay.io/aerokube/xvfb-server
      resources:
        limits:
          cpu: 200m
          memory: 128Mi
        requests:
          cpu: 100m
          memory: 128Mi

BrowserSet
apiVersion: moon.aerokube.com/v1
kind: BrowserSet
metadata:
  annotations:
    meta.helm.sh/release-name: moon
    meta.helm.sh/release-namespace: moon-dev
  creationTimestamp: "2023-05-04T07:59:59Z"
  generation: 1
  labels:
    app.kubernetes.io/managed-by: Helm
  name: default
  namespace: moon-dev
  resourceVersion: "835680657"
  uid: 3d688301-829b-235f-bd68-4as46e76074c
spec:
  cypress:
    chrome:
      repository: quay.io/browsers/cypress-chrome
    chromium:
      repository: quay.io/browsers/cypress-chromium
    edge:
      repository: quay.io/browsers/cypress-edge
    electron:
      repository: quay.io/browsers/cypress-electron
    firefox:
      repository: quay.io/browsers/cypress-firefox
  devtools:
    chrome:
      repository: quay.io/browser/devtools-google-chrome-stable
  playwright:
    chrome:
      repository: quay.io/browser/playwright-chrome
    chromium:
      repository: quay.io/browser/playwright-chromium
    firefox:
      repository: quay.io/browser/playwright-firefox
    webkit:
      repository: quay.io/browser/playwright-webkit
  selenium:
    MicrosoftEdge:
      default: 112.0.1722.58-5
      repository: quay.io/browser/microsoft-edge-stable
    chrome:
      default: 112.0.5615.165-5
      repository: quay.io/browser/google-chrome-stable
    firefox:
      default: 112.0.2-4
      repository: quay.io/browser/firefox-mozilla-build
    opera:
      default: 98.0.4759.15-6
      repository: quay.io/browser/opera-stable
    safari:
      default: 15.0-0
      repository: quay.io/browser/safari

vnc-server
17/05/2023 08:01:59 passing arg to libvncserver: -passwd
17/05/2023 08:01:59 passing arg to libvncserver: -rfbport
17/05/2023 08:01:59 passing arg to libvncserver: 5900
17/05/2023 08:01:59 x11vnc version: 0.9.16 lastmod: 2019-01-05 pid: 11
17/05/2023 08:01:59
17/05/2023 08:01:59 wait_for_client: WAIT:0
17/05/2023 08:01:59
17/05/2023 08:01:59 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560
17/05/2023 08:01:59
17/05/2023 08:01:59 Listening for VNC connections on TCP port 5900
17/05/2023 08:01:59 Listening for VNC connections on TCP6 port 5900
17/05/2023 08:01:59 listen6: bind: Address already in use
17/05/2023 08:01:59 Not listening on IPv6 interface.
17/05/2023 08:01:59
The VNC desktop is: moon-6777d5bd8d-8xg8c:0
PORT=5900

That is very strange, vnc desktop should be something like chrome-:0 and
not moon-:0. Looks like you are doing something wrong.
ср, 17 мая 2023 г., 11:03 Murat Mercan @.***>:

vnc-server
17/05/2023 08:01:59 passing arg to libvncserver: -passwd
17/05/2023 08:01:59 passing arg to libvncserver: -rfbport
17/05/2023 08:01:59 passing arg to libvncserver: 5900
17/05/2023 08:01:59 x11vnc version: 0.9.16 lastmod: 2019-01-05 pid: 11
17/05/2023 08:01:59
17/05/2023 08:01:59 wait_for_client: WAIT:0
17/05/2023 08:01:59
17/05/2023 08:01:59 initialize_screen: fb_depth/fb_bpp/fb_Bpl 24/32/2560
17/05/2023 08:01:59
17/05/2023 08:01:59 Listening for VNC connections on TCP port 5900
17/05/2023 08:01:59 Listening for VNC connections on TCP6 port 5900
17/05/2023 08:01:59 listen6: bind: Address already in use
17/05/2023 08:01:59 Not listening on IPv6 interface.
17/05/2023 08:01:59
The VNC desktop is: moon-6777d5bd8d-8xg8c:0
PORT=5900
—
Reply to this email directly, view it on GitHub
https://github.com/aerokube/moon/issues/378#issuecomment-1550940288, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKY23MA5DMUCMR6TNCY2WTXGSA55ANCNFSM6AAAAAAYDS2YRM
.
You are receiving this because you commented.Message ID:
@.***>

This is how it seems;

@muratme our Helm chart is parameterized by namespace name (all charts actually do), so reinstalling everything from scratch should just work.

authors: aandryashin muratme vania-pooh

repo: aerokube/moon


text:
FAILED_TO_STOP_VIDEO_CONTAINER]

I configured Selenoid, pull all dependencies
CONTAINER ID   IMAGE                              COMMAND                  CREATED          STATUS                    PORTS                    NAMES
264b1a3eeb2c   aerokube/selenoid-ui               "/selenoid-ui --sele…"   19 minutes ago   Up 19 minutes (healthy)   0.0.0.0:8090->8080/tcp   selenoid-ui
486aa91d40ab   aerokube/selenoid:latest-release   "/usr/bin/selenoid -…"   20 minutes ago   Up 20 minutes             0.0.0.0:4444->4444/tcp   selenoid
Images
REPOSITORY                TAG              IMAGE ID       CREATED         SIZE
aerokube/selenoid-ui      latest           cd995503ebba   4 days ago      17.1MB
aerokube/selenoid-ui      latest-release   cd995503ebba   4 days ago      17.1MB
aerokube/selenoid-ui                 5167c67666be   6 days ago      17.1MB
selenoid/vnc_firefox      106.0            ee42cad2660a   12 days ago     1.19GB
selenoid/chrome           latest           0567aed9d175   3 weeks ago     1.15GB
selenoid/vnc_chrome       106.0            0567aed9d175   3 weeks ago     1.15GB
aerokube/cm               latest           ab4aa6c69760   3 months ago    16.3MB
aerokube/selenoid         latest-release   3b109a9b5eaa   3 months ago    15.8MB
aerokube/cm               latest-release   9c98e75d2f39   16 months ago   17.4MB
selenoid/video-recorder   latest-release   654b710209f9   22 months ago   37.6MB
selenoid/vnc_chrome       84.0             f339430e17f3   2 years ago     894MB
selenoid/video-recorder   latest           c8018c23fcb7   4 years ago     30.4MB
selenoid/vnc_chrome       65.0             dff07a4cfe6d   4 years ago     959MB

After running below script i didnt get any errors
WebDriver driver2;
@BeforeEach
public void setUp() throws MalformedURLException {

    ChromeOptions chromeOptions = new ChromeOptions();
    chromeOptions.addArguments("--disable-notifications");
    chromeOptions.addArguments("start-maximized");
    chromeOptions.setCapability("enableVNC",false);
    chromeOptions.setCapability("enableVideo", true);
    chromeOptions.setCapability("videoName","test_video.mp4");

    driver2 = new RemoteWebDriver(new URL(" http://localhost:4444/wd/hub/"),chromeOptions);
}

@Test
public void method()
{
    driver2.get("https://www.onet.pl/");
    driver2.quit();
}

but i saw errors i powershel after command docker logs selenoid
2022/10/25 18:34:10 [-] [INIT] [Loading configuration files...]
2022/10/25 18:34:10 [-] [INIT] [Loaded configuration from /etc/selenoid/browsers.json]
2022/10/25 18:34:10 [-] [INIT] [Video Dir: /opt/selenoid/video]
2022/10/25 18:34:10 [-] [INIT] [Your Docker API version is 1.41]
2022/10/25 18:34:10 [-] [INIT] [Timezone: UTC]
2022/10/25 18:34:10 [-] [INIT] [Listening on :4444]
2022/10/25 18:36:47 [-] [NEW_REQUEST] [unknown] [172.17.0.1]
2022/10/25 18:36:47 [-] [NEW_REQUEST_ACCEPTED] [unknown] [172.17.0.1]
2022/10/25 18:36:47 [19] [LOCATING_SERVICE] [chrome] []
2022/10/25 18:36:47 [-] [DEFAULT_VERSION] [Using default version: 106.0]
2022/10/25 18:36:47 [19] [USING_DOCKER] [chrome] [106.0]
2022/10/25 18:36:47 [19] [CREATING_CONTAINER] [selenoid/vnc_chrome:106.0]
2022/10/25 18:36:47 [19] [STARTING_CONTAINER] [selenoid/vnc_chrome:106.0] [6861aa549c98bad3bc095970c76a0f8328eaa6b9305004cf5f3f3217727005c6]
2022/10/25 18:36:48 [19] [CONTAINER_STARTED] [selenoid/vnc_chrome:106.0] [6861aa549c98bad3bc095970c76a0f8328eaa6b9305004cf5f3f3217727005c6] [0.30s]
2022/10/25 18:36:48 [19] [CREATING_VIDEO_CONTAINER] [selenoid/video-recorder:latest-release]
2022/10/25 18:36:48 [19] [STARTING_VIDEO_CONTAINER] [selenoid/video-recorder:latest-release] [499312dcf9c49cff0e3489790ca46dff9d330c74f150b8a1fac5833f849cceb4]
2022/10/25 18:36:48 [19] [VIDEO_CONTAINER_STARTED] [selenoid/video-recorder:latest-release] [499312dcf9c49cff0e3489790ca46dff9d330c74f150b8a1fac5833f849cceb4] [0.34s]
2022/10/25 18:36:48 [19] [SERVICE_STARTED] [selenoid/vnc_chrome:106.0] [6861aa549c98bad3bc095970c76a0f8328eaa6b9305004cf5f3f3217727005c6] [0.36s]
2022/10/25 18:36:48 [19] [PROXY_TO] [6861aa549c98bad3bc095970c76a0f8328eaa6b9305004cf5f3f3217727005c6] [http://172.17.0.4:4444/]
2022/10/25 18:36:48 [19] [SESSION_ATTEMPTED] [http://172.17.0.4:4444/] [1]
2022/10/25 18:36:49 [19] [SESSION_CREATED] [2e691484f4a47c4274293538da1c962c] [1] [1.76s]
2022/10/25 18:36:50 [21] [SESSION_DELETED] [2e691484f4a47c4274293538da1c962c]
2022/10/25 18:36:50 [19] [STOPPING_VIDEO_CONTAINER] [499312dcf9c49cff0e3489790ca46dff9d330c74f150b8a1fac5833f849cceb4]
2022/10/25 18:36:50 [19] [FAILED_TO_STOP_VIDEO_CONTAINER] [499312dcf9c49cff0e3489790ca46dff9d330c74f150b8a1fac5833f849cceb4] [Error response from daemon: Cannot kill container: 499312dcf9c49cff0e3489790ca46dff9d330c74f150b8a1fac5833f849cceb4: Container 499312dcf9c49cff0e3489790ca46dff9d330c74f150b8a1fac5833f849cceb4 is not running]
2022/10/25 18:36:50 [19] [REMOVING_CONTAINER] [6861aa549c98bad3bc095970c76a0f8328eaa6b9305004cf5f3f3217727005c6]
2022/10/25 18:36:51 [19] [CONTAINER_REMOVED] [6861aa549c98bad3bc095970c76a0f8328eaa6b9305004cf5f3f3217727005c6]
2022/10/25 18:36:51 [19] [VIDEO_ERROR] [Failed to rename /opt/selenoid/video/selenoid8116f2bd7da67237685f070ebf555eb7.mp4 to /opt/selenoid/video/test_video.mp4: rename /opt/selenoid/video/selenoid8116f2bd7da67237685f070ebf555eb7.mp4 /opt/selenoid/video/test_video.mp4: no such file or directory]
What i have to do to make it work i have videos?

it is possible that problem is with WSL Version?
after typeing command to powershell --list --verbose
i get
NAME                   STATE           VERSION

docker-desktop         Running         2
docker-desktop-data    Running         2
it means that have i version two of WSL?

@ltoczek seems to be a permissions issue in WSL when trying to mount c:\Users\user\.aerokube\selenoid\video to video recorder container.

authors: ltoczek vania-pooh

repo: aerokube/selenoid


text:
Integrate authentication

OAuth / Oauth2 through annotations for API requests
@Authentication annotation on controller methods + provide Apex's way to handle authentication

And :

Login facilities (i.e. login view ?)
redirect automatically to login view when user is not authenticated
authentication against some services (Auth providers)
inject session when the user asks for it it

wait for : https://groups.google.com/forum/#!topic/vertx-dev/Z2k4CKDW8HA before working on it

keep an eye on : https://github.com/vert-x3/vertx-apex/issues/81

First draft is done with @Auth(method=AuthMethod.BASIC, authority="admin)

repo: aesteve/vertx-nubes


text:
Filter tables by date and time interval

Please describe the problem that your request should resolve.

Describe the solution you'd like

Is it already possible to achieve the same outcome in any other way? If so, how?

Additional context

Duplicate of https://github.com/aeternity/aescan/issues/615

repo: aeternity/aescan

license: ISC


text:
Teach Dialyzer to check for unknown functions and types

Do not merge as CI fails!

I see :0: Unknown type http_uri:uri/0, I need to understand why. I am re-compiling locally from scratch.

I see :0: Unknown type http_uri:uri/0, I need to understand why. I am re-compiling locally from scratch.

I see it is jesse.erl and jesse_state.erl

Looks good so far...

I force pushed:

I rebased on master;
I enriched the commit re workaround of http_uri types by depending on a modified jesse version. I did not propose this upstream as the copied type is applicable only to recent OTP versions;
I reordered the commits so CI is meant to pass at each commit.

The proposed http_uri patch is submitted to OTP (1724) and already went through a round of review. Though it is not yet merged so it is not in any released tag. Hence I propose to merge this PR with the http_uri workarounds so that we have unknown Dialyzer option enabled in master.

authors: hanssv lucafavatella

repo: aeternity/epoch


text:
Remove from Lookup Rollup Summary Schedule Items when Parent is deleted

Scenario:

Bulk load Accounts (Parent) & Invoices (Child) from API
Hundreds of Thousands of triggers scheduled
Some Accounts are mass deleted
Scheduled Job runs, where accounts are deleted error: "entity is deleted : ENTITY_IS_DELETED ()"
These Schedule Items stay in Lookup Rollup Summary Schedule Items list

Should these get removed automatically from the Lookup Rollup Summary Schedule Items list?
OR should there be a way to bulk delete them?  If manually bulk delete it's hard to tell which ones you should delete vs. new ones that should be run during the next schedule.

Good catch, auto delete i would say, should be doable.... thanks for marking as enhancement.

Added in v2.4.1.

authors: JimBTek afawcett


text:
java.lang.NullPointerException                                                                           at android.support.v4.graphics.drawable.DrawableWrapperDonut.getState(DrawableWrapperDonut.java:147)

`E/CrashException: DateTime:2016-06-01 11:15:09
ExceptionName:null
                                                                  android.support.v4.graphics.drawable.DrawableWrapperDonut	DrawableWrapperDonut.java[147].getState
                                                                  android.support.v4.graphics.drawable.DrawableWrapperDonut	DrawableWrapperDonut.java[267].setTintList
                                                                  android.support.v4.graphics.drawable.DrawableCompatBase	DrawableCompatBase.java[42].setTintList
                                                                  android.support.v4.graphics.drawable.DrawableCompat$BaseDrawableImpl	DrawableCompat.java[94].setTintList
                                                                  android.support.v4.graphics.drawable.DrawableCompat	DrawableCompat.java[390].setTintList
                                                                  com.afollestad.materialdialogs.internal.MDTintHelper	MDTintHelper.java[45].setTint
                                                                  com.afollestad.materialdialogs.DefaultAdapter	DefaultAdapter.java[67].getView
                                                                  android.widget.AbsListView	AbsListView.java[2255].obtainView
                                                                  android.widget.ListView	ListView.java[1263].measureHeightOfChildren
                                                                  android.widget.ListView	ListView.java[1175].onMeasure
                                                                  android.view.View	View.java[16566].measure
                                                                  android.view.ViewGroup	ViewGroup.java[5147].measureChildWithMargins
                                                                  android.widget.FrameLayout	FrameLayout.java[310].onMeasure
                                                                  android.view.View	View.java[16566].measure
                                                                  android.view.ViewGroup	ViewGroup.java[5147].measureChildWithMargins
                                                                  android.widget.LinearLayout	LinearLayout.java[1427].measureChildBeforeLayout
                                                                  android.widget.LinearLayout	LinearLayout.java[713].measureVertical
                                                                  android.widget.LinearLayout	LinearLayout.java[606].onMeasure
                                                                  android.view.View	View.java[16566].measure
                                                                  com.afollestad.materialdialogs.internal.MDRootLayout	MDRootLayout.java[199].onMeasure
                                                                  android.view.View	View.java[16566].measure
                                                                  android.view.ViewGroup	ViewGroup.java[5147].measureChildWithMargins
                                                                  android.widget.FrameLayout	FrameLayout.java[310].onMeasure
                                                                  android.view.View	View.java[16566].measure
                                                                  android.view.ViewGroup	ViewGroup.java[5147].measureChildWithMargins
                                                                  android.widget.LinearLayout	LinearLayout.java[1427].measureChildBeforeLayout
                                                                  android.widget.LinearLayout	LinearLayout.java[713].measureVertical
                                                                  android.widget.LinearLayout	LinearLayout.java[606].onMeasure
                                                                  android.view.View	View.java[16566].measure
                                                                  android.view.ViewGroup	ViewGroup.java[5147].measureChildWithMargins
                                                                  android.widget.FrameLayout	FrameLayout.java[310].onMeasure
                                                                  com.android.internal.policy.impl.PhoneWindow$DecorView	PhoneWindow.java[2316].onMeasure
                                                                  android.view.View	View.java[16566].measure
                                                                  android.view.ViewRootImpl	ViewRootImpl.java[1979].performMeasure
                                                                  android.view.ViewRootImpl	ViewRootImpl.java[1132].measureHierarchy
                                                                  android.view.ViewRootImpl	ViewRootImpl.java[1339].performTraversals
                                                                  android.view.ViewRootImpl	ViewRootImpl.java[1044].doTraversal
                                                                  android.view.ViewRootImpl$TraversalRunnable	ViewRootImpl.java[5818].run
                                                                  android.view.Choreographer$CallbackRecord	Choreographer.java[768].run
                                                                  android.view.Choreographer	Choreographer.java[581].doCallbacks
                                                                  android.view.Choreographer	Choreographer.java[551].doFrame
                                                                  android.view.Choreographer$FrameDisplayEventReceiver	Choreographer.java[754].run
                                                                  android.os.Handler	Handler.java[733].handleCallback
                                                                  android.os.Handler	Handler.java[95].dispatchMessage
                                                                  android.os.Looper	Looper.java[136].loop
                                                                  android.app.ActivityThread	ActivityThread.java[5333].main
                                                                  java.lang.reflect.Method	Method.java[-2].invokeNative
                                                                  java.lang.reflect.Method	Method.java[515].invoke
                                                                  com.android.internal.os.ZygoteInit$MethodAndArgsCaller	ZygoteInit.java[895].run
                                                                  com.android.internal.os.ZygoteInit	ZygoteInit.java[711].main
                                                                  dalvik.system.NativeStart	NativeStart.java[-2].main

                                                                  null
                                                                  ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
                                                                  java.lang.NullPointerException
                                                                      at android.support.v4.graphics.drawable.DrawableWrapperDonut.getState(DrawableWrapperDonut.java:147)
                                                                      at android.support.v4.graphics.drawable.DrawableWrapperDonut.setTintList(DrawableWrapperDonut.java:267)
                                                                      at android.support.v4.graphics.drawable.DrawableCompatBase.setTintList(DrawableCompatBase.java:42)
                                                                      at android.support.v4.graphics.drawable.DrawableCompat$BaseDrawableImpl.setTintList(DrawableCompat.java:94)
                                                                      at android.support.v4.graphics.drawable.DrawableCompat.setTintList(DrawableCompat.java:390)
                                                                  	at com.afollestad.materialdialogs.internal`

sorry，i didn't check you release note 0.8.5.8,it's solved already !!!

Just got the same error running core-0.8.6.2, support lib version 25.0.0
Fatal Exception: java.lang.NullPointerException        at android.support.v4.graphics.drawable.DrawableWrapperDonut.getState(DrawableWrapperDonut.java:147)        at android.support.v4.graphics.drawable.DrawableWrapperDonut.setTintList(DrawableWrapperDonut.java:267)        at android.support.v4.graphics.drawable.DrawableCompatBase.setTintList(DrawableCompatBase.java:42)        at android.support.v4.graphics.drawable.DrawableCompat$BaseDrawableImpl.setTintList(DrawableCompat.java:94)        at android.support.v4.graphics.drawable.DrawableCompat.setTintList(DrawableCompat.java:391)        at com.afollestad.materialdialogs.internal.MDTintHelper.setTint(MDTintHelper.java:45)        at com.afollestad.materialdialogs.DefaultAdapter.getView(DefaultAdapter.java:67)        at android.widget.AbsListView.obtainView(AbsListView.java:2310)        at android.widget.ListView.measureHeightOfChildren(ListView.java:1274)        at android.widget.ListView.onMeasure(ListView.java:1186)        at android.view.View.measure(View.java:16749)        at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5295)        at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)        at android.view.View.measure(View.java:16749)        at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5295)        at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1404)        at android.widget.LinearLayout.measureVertical(LinearLayout.java:695)        at android.widget.LinearLayout.onMeasure(LinearLayout.java:588)        at android.view.View.measure(View.java:16749)        at com.afollestad.materialdialogs.internal.MDRootLayout.onMeasure(MDRootLayout.java:199)        at android.view.View.measure(View.java:16749)        at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5295)        at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)        at android.view.View.measure(View.java:16749)        at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5295)        at android.widget.LinearLayout.measureChildBeforeLayout(LinearLayout.java:1404)        at android.widget.LinearLayout.measureVertical(LinearLayout.java:695)        at android.widget.LinearLayout.onMeasure(LinearLayout.java:588)        at android.view.View.measure(View.java:16749)        at android.view.ViewGroup.measureChildWithMargins(ViewGroup.java:5295)        at android.widget.FrameLayout.onMeasure(FrameLayout.java:310)        at com.android.internal.policy.impl.PhoneWindow$DecorView.onMeasure(PhoneWindow.java:2439)        at android.view.View.measure(View.java:16749)        at android.view.ViewRootImpl.performMeasure(ViewRootImpl.java:2080)        at android.view.ViewRootImpl.measureHierarchy(ViewRootImpl.java:1176)        at android.view.ViewRootImpl.performTraversals(ViewRootImpl.java:1380)        at android.view.ViewRootImpl.doTraversal(ViewRootImpl.java:1063)        at android.view.ViewRootImpl$TraversalRunnable.run(ViewRootImpl.java:5993)        at android.view.Choreographer$CallbackRecord.run(Choreographer.java:761)        at android.view.Choreographer.doCallbacks(Choreographer.java:574)        at android.view.Choreographer.doFrame(Choreographer.java:544)        at android.view.Choreographer$FrameDisplayEventReceiver.run(Choreographer.java:747)        at android.os.Handler.handleCallback(Handler.java:733)        at android.os.Handler.dispatchMessage(Handler.java:95)        at android.os.Looper.loop(Looper.java:136)        at android.app.ActivityThread.main(ActivityThread.java:5584)        at java.lang.reflect.Method.invokeNative(Method.java)        at java.lang.reflect.Method.invoke(Method.java:515)        at com.android.internal.os.ZygoteInit$MethodAndArgsCaller.run(ZygoteInit.java:1268)        at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1084)        at dalvik.system.NativeStart.main(NativeStart.java)

repo: afollestad/material-dialogs