text:
CSV export panic

Repro is with zq commit fcad36bc and the attached test file repro.tzng.gz:
#0:record[_path:string,ts:time,ts_delta:duration,peer:bstring,gaps:uint64,acks:uint64,percent_lost:float64]
0:[capture_loss;1521835214.3314;111.694792;zeek;15;72667;0.020642;]
#port=uint16
#1:record[event_type:bstring,src_ip:ip,src_port:port,dest_ip:ip,dest_port:port,vlan:array[uint16],proto:bstring,app_proto:bstring,alert:record[severity:uint16,signature:bstring,category:bstring,action:bstring,signature_id:uint64,gid:uint64,rev:uint64,metadata:record[signature_severity:array[bstring],former_category:array[bstring],attack_target:array[bstring],deployment:array[bstring],affected_product:array[bstring],created_at:array[bstring],performance_impact:array[bstring],updated_at:array[bstring],malware_family:array[bstring],tag:array[bstring]]],flow_id:uint64,pcap_cnt:uint64,ts:time,tx_id:uint64,icmp_code:uint64,icmp_type:uint64,community_id:bstring]
1:[alert;13.107.4.50;80;10.47.8.154;51006;-;TCP;http;[3;SURICATA STREAM ESTABLISHED packet out of window;Generic Protocol Command Decode;allowed;2210020;1;2;[-;-;-;-;-;-;-;-;-;-;]]1741344505971013;1650919;1521835214.3314;-;-;-;1:kZkWyvbJTmfVpW38Axh1yk/fHKE=;]
#2:record[_path:string,ts:time,peer:bstring,mem:uint64,pkts_proc:uint64,bytes_recv:uint64,pkts_dropped:uint64,pkts_link:uint64,pkt_lag:duration,events_proc:uint64,events_queued:uint64,active_tcp_conns:uint64,active_udp_conns:uint64,active_icmp_conns:uint64,tcp_conns:uint64,udp_conns:uint64,icmp_conns:uint64,timers:uint64,active_timers:uint64,files:uint64,active_files:uint64,dns_requests:uint64,active_dns_requests:uint64,reassem_tcp_size:uint64,reassem_file_size:uint64,reassem_frag_size:uint64,reassem_unknown_size:uint64]
2:[stats;1521835214.3314;zeek;534;1650918;473585160;-;-;-;1060403;1060403;29135;87;1446;392651;1453;1447;1217499;0;4155;6;15;0;64425;0;0;0;]

$ zq -version
Version: v0.27.0-1-gfcad36bc

$ zq -f csv repro.tzng.gz
panic: runtime error: slice bounds out of range [11:2]

goroutine 1 [running]:
github.com/brimsec/zq/zcode.(*Iter).Next(0xc00021f8c0, 0x2, 0x51, 0xc000343600, 0x0, 0x0, 0x1d)
	/Users/phil/work/zq/zcode/iter.go:34 +0x22a
github.com/brimsec/zq/zng.(*TypeArray).StringOf(0xc00030c160, 0xc00035062f, 0x2, 0x51, 0x3, 0x0, 0x51, 0x20)
	/Users/phil/work/zq/zng/array.go:58 +0x165
github.com/brimsec/zq/zng.Value.Format(...)
	/Users/phil/work/zq/zng/value.go:74
github.com/brimsec/zq/zio/csvio.(*Writer).Write(0xc000312080, 0xc00031a320, 0x0, 0x0)
	/Users/phil/work/zq/zio/csvio/writer.go:97 +0x45e
github.com/brimsec/zq/zbuf.CopyWithContext(0x1a13b80, 0xc000038080, 0xa100088, 0xc000312080, 0x1a03ae0, 0xc000316000, 0x0, 0x0)
	/Users/phil/work/zq/zbuf/zbuf.go:63 +0x86
github.com/brimsec/zq/zbuf.Copy(...)
	/Users/phil/work/zq/zbuf/zbuf.go:71
github.com/brimsec/zq/proc/fuse.(*writeCloser).Close(0xc00030c040, 0xc0002d9c50, 0x1a13e40)
	/Users/phil/work/zq/proc/fuse/writer.go:23 +0x91
main.(*Command).Run(0xc0002a5080, 0xc0000320b0, 0x1, 0x1, 0x0, 0x0)
	/Users/phil/work/zq/cmd/zq/zq.go:185 +0x83f
github.com/mccanne/charm.(*instance).run(0xc00000fc20, 0xc000032090, 0x3, 0x3, 0x0, 0x0)
	/Users/phil/.go/pkg/mod/github.com/mccanne/charm@v0.0.3-0.20191224190439-b05e1b7b1be3/instance.go:53 +0x293
github.com/mccanne/charm.(*Spec).ExecRoot(0x1e54d00, 0xc000032090, 0x3, 0x3, 0xc00021ff78, 0x1007f65, 0xc00009a058, 0x0)
	/Users/phil/.go/pkg/mod/github.com/mccanne/charm@v0.0.3-0.20191224190439-b05e1b7b1be3/charm.go:77 +0x96
main.main()
	/Users/phil/work/zq/cmd/zq/main.go:9 +0x85

I've also confirmed this is not a new bug. While the automatic fuse for CSV is new functionality, if I go back to the prior GA release of zq tagged v0.26.0, I can trigger the same repro if I include an explicit call to fuse.
$ zq -version
Version: v0.26.0

$ zq -f csv 'fuse' repro.tzng.gz
panic: runtime error: slice bounds out of range [11:2]

goroutine 1 [running]:
github.com/brimsec/zq/zcode.(*Iter).Next(0xc00089d760, 0x2, 0x51, 0xc00099fa00, 0x0, 0x0, 0x1d)
	/Users/phil/work/zq/zcode/iter.go:34 +0x22a
github.com/brimsec/zq/zng.(*TypeArray).StringOf(0xc00000e120, 0xc0009d462f, 0x2, 0x51, 0x3, 0x0, 0x51, 0x20)
	/Users/phil/work/zq/zng/array.go:58 +0x165
github.com/brimsec/zq/zng.Value.Format(...)
	/Users/phil/work/zq/zng/value.go:74
github.com/brimsec/zq/zio/csvio.(*Writer).Write(0xc0000d87c0, 0xc0001803c0, 0x0, 0x0)
	/Users/phil/work/zq/zio/csvio/writer.go:85 +0x45e
github.com/brimsec/zq/driver.(*CLI).Write(0xc0000df050, 0x0, 0x1a0e2c0, 0xc00000e220, 0x0, 0x0)
	/Users/phil/work/zq/driver/driver.go:118 +0xcd
github.com/brimsec/zq/driver.runMux(0xc0001800f0, 0x1a0aa00, 0xc0000df050, 0x0, 0xc0000d8680, 0xc00089da70)
	/Users/phil/work/zq/driver/driver.go:86 +0x25a
github.com/brimsec/zq/driver.Run(0x1a0aa80, 0xc0000df080, 0x1a0aa00, 0xc0000df050, 0x19f9b80, 0xc0000ded80, 0xc0000d8680, 0x19fa4c0, 0xc0000deff0, 0x0, ...)
	/Users/phil/work/zq/driver/driver.go:32 +0x1d1
main.(*Command).Run(0xc000102900, 0xc000180080, 0x2, 0x2, 0x0, 0x0)
	/Users/phil/work/zq/cmd/zq/zq.go:183 +0xa25
github.com/mccanne/charm.(*instance).run(0xc0001a2e00, 0xc000180060, 0x4, 0x4, 0x0, 0x0)
	/Users/phil/.go/pkg/mod/github.com/mccanne/charm@v0.0.3-0.20191224190439-b05e1b7b1be3/instance.go:53 +0x293
github.com/mccanne/charm.(*Spec).ExecRoot(0x1e46c40, 0xc000180060, 0x4, 0x4, 0xc00089df78, 0x1007f65, 0xc000182058, 0x0)
	/Users/phil/.go/pkg/mod/github.com/mccanne/charm@v0.0.3-0.20191224190439-b05e1b7b1be3/charm.go:77 +0x96
main.main()
	/Users/phil/work/zq/cmd/zq/main.go:9 +0x85

(The original repro was actually seen by importing test pcap https://archive.wrccdc.org/pcaps/2018/wrccdc.2018-03-23.010014000000000.pcap.gz into Brim with a zqd based on a recent commit, then trying to use the new CSV export option without entering an explicit query and hence requesting all the data be exported as very wide CSV. I'd not noticed this issue before because in the verification of the CSV export feature, I happened to have used an explicit Z query of _path=http or _path=ssl first to isolate diverse records that would need the auto-fuse treatment, but apparently that was not the right data to trigger this bug. I've since confirmed that just the diversity in those three lines above is all that it takes to trigger it, though.)

Verified in zq commit fbf5fe4c.
Using the repro fragment above, the CSV is now generated without panic.
$ zq -version
Version: v0.27.0-6-gfbf5fe4c

$ zq -f csv repro.tzng.gz
_path,ts,ts_delta,peer,gaps,acks,percent_lost,event_type,src_ip,src_port,dest_ip,dest_port,vlan,proto,app_proto,alert.severity,alert.signature,alert.category,alert.action,alert.signature_id,alert.gid,alert.rev,alert.metadata.signature_severity,alert.metadata.former_category,alert.metadata.attack_target,alert.metadata.deployment,alert.metadata.affected_product,alert.metadata.created_at,alert.metadata.performance_impact,alert.metadata.updated_at,alert.metadata.malware_family,alert.metadata.tag,flow_id,pcap_cnt,tx_id,icmp_code,icmp_type,community_id,mem,pkts_proc,bytes_recv,pkts_dropped,pkts_link,pkt_lag,events_proc,events_queued,active_tcp_conns,active_udp_conns,active_icmp_conns,tcp_conns,udp_conns,icmp_conns,timers,active_timers,files,active_files,dns_requests,active_dns_requests,reassem_tcp_size,reassem_file_size,reassem_frag_size,reassem_unknown_size
capture_loss,2018-03-23T20:00:14.3314Z,111.694792,zeek,15,72667,0.020642,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,2018-03-23T20:00:14.3314Z,,,,,,alert,13.107.4.50,80,10.47.8.154,51006,,TCP,http,3,SURICATA STREAM ESTABLISHED packet out of window,Generic Protocol Command Decode,allowed,2210020,1,2,,,,,,,,,,,1741344505971013,1650919,,,,1:kZkWyvbJTmfVpW38Axh1yk/fHKE=,,,,,,,,,,,,,,,,,,,,,,,,
stats,2018-03-23T20:00:14.3314Z,,zeek,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,534,1650918,473585160,,,,1060403,1060403,29135,87,1446,392651,1453,1447,1217499,0,4155,6,15,0,64425,0,0,0

The same is true for the original larger ZNG based on the pcap linked above (line count is +1 as expected due to the CSV header line).
$ zq -t 'count()' all.zng
#0:record[count:uint64]
0:[670822;]

$ zq -f csv all.zng > all.csv

$ wc -l all.csv
  670823 all.csv

Thanks @mccanne!

Verified in zq commit fbf5fe4c.
Using the repro fragment above, the CSV is now generated without panic.
$ zq -version
Version: v0.27.0-6-gfbf5fe4c

$ zq -f csv repro.tzng.gz
_path,ts,ts_delta,peer,gaps,acks,percent_lost,event_type,src_ip,src_port,dest_ip,dest_port,vlan,proto,app_proto,alert.severity,alert.signature,alert.category,alert.action,alert.signature_id,alert.gid,alert.rev,alert.metadata.signature_severity,alert.metadata.former_category,alert.metadata.attack_target,alert.metadata.deployment,alert.metadata.affected_product,alert.metadata.created_at,alert.metadata.performance_impact,alert.metadata.updated_at,alert.metadata.malware_family,alert.metadata.tag,flow_id,pcap_cnt,tx_id,icmp_code,icmp_type,community_id,mem,pkts_proc,bytes_recv,pkts_dropped,pkts_link,pkt_lag,events_proc,events_queued,active_tcp_conns,active_udp_conns,active_icmp_conns,tcp_conns,udp_conns,icmp_conns,timers,active_timers,files,active_files,dns_requests,active_dns_requests,reassem_tcp_size,reassem_file_size,reassem_frag_size,reassem_unknown_size
capture_loss,2018-03-23T20:00:14.3314Z,111.694792,zeek,15,72667,0.020642,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,
,2018-03-23T20:00:14.3314Z,,,,,,alert,13.107.4.50,80,10.47.8.154,51006,,TCP,http,3,SURICATA STREAM ESTABLISHED packet out of window,Generic Protocol Command Decode,allowed,2210020,1,2,,,,,,,,,,,1741344505971013,1650919,,,,1:kZkWyvbJTmfVpW38Axh1yk/fHKE=,,,,,,,,,,,,,,,,,,,,,,,,
stats,2018-03-23T20:00:14.3314Z,,zeek,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,,534,1650918,473585160,,,,1060403,1060403,29135,87,1446,392651,1453,1447,1217499,0,4155,6,15,0,64425,0,0,0

The same is true for the original larger ZNG based on the pcap linked above (line count is +1 as expected due to the CSV header line).
$ zq -t 'count()' all.zng
#0:record[count:uint64]
0:[670822;]

$ zq -f csv all.zng > all.csv

$ wc -l all.csv
  670823 all.csv

Thanks @mccanne!

repo: brimsec/zq


text:
ApplyBQSR into Skeleton pipeline

ApplyBQSR adapted to fit into the Skeleton pipeline
command-line version still works and passes tests (including cloud)
BaseRecalibrator's testPlottingWorkflow now passes

(please don't press the "merge" button. Once this is OK I still have to squash/rebase into master, and disentangle this from the bqsr PR that's in flight in parallel.)

Will review this one once it's rebased and in its final form -- ping me when it's ready.

I have it ready at #835 (tests pass locally, hopefully they will work on Travis too!)

source: gharchive/pull-request

authors: droazen jean-philippe-martin

repo: broadinstitute/hellbender

license_type: permissive

license_source: bigquery


text:
[JN-378] Add question templates list

This adds the ability to select the "Question templates" list in the form designer's table of contents and delete question templates (if they are not referenced by a question).

Rebased to resolve conflicts after merging #444.

repo: broadinstitute/juniper

license_source: github-api


text:
Ability to configure default username

i use the same login name on most sites i'm on. for example here i am "anarcat". there are exceptions to the rule, naturally, but I would like it if I wouldn't have to specify that login name in every password I use and instead allow some default to be configured in the Browserpass configuration. it would greatly reduce the work I have to make automatic login work...

I like this idea, will be considered as part of v3.

Implemented in v3 😉 I'll push as 3.0.2 later tonight, see #331 if you already want to try

source: gharchive/issue

authors: anarcat maximbaz

repo: browserpass/browserpass

license: MIT


text:
Original Faust DSP code ?

Great project !
I understand that the DSP code have been generated from Faust DSP (bandsplit.dsp,  delay.dsp and Gain.dsp). Are the original files DSP files somewhere ?

Hi Stéphane Letz
Yes, I've forgotten to add them, done now. Unfortunately I ain't found my base file for the slowgear any more.

Thank !


text:
issue_1

Added file for JSON feed. For #hacktoberfest, Issue #1
I have stripped the HTML from the content, and summary.
creates a folder _site/feed/index.json
Example from a test I ran off of my Local Host.
{
  "version": "https://jsonfeed.org/version/1",
  "home_page_url": "http://0.0.0.0:4000",
  "description": "My personal website.",
  "feed_url": "http://0.0.0.0:4000/feed.json",
  "favicon": "http://0.0.0.0:4000/favicon.png",
  "author" : {
      "url" : "http://0.0.0.0:4000",
      "name" : "Bryan Braun"
  },
  "items": [
    {
      "id": "/2017/10/01/why-i-like-to-spend-my-time-in-core-web-technologies",
      "url": "http://0.0.0.0:4000/2017/10/01/why-i-like-to-spend-my-time-in-core-web-technologies/",
      "date_published": "2017-10-01T06:48:00-04:00",
      "title": "Why I like to spend my time in core web technologies",
      "author" : "Bryan Braun",
      "summary": "Look at where you actually spend your time in a given day. Is it spent in a testing framework? Cleaning up data? Creating APIs? Reviewing code? Installing a CMS? Setting up CI workflows? Writing CSS? Configuring Webpack?\n\n",
      "content_html": "Look at where you actually spend your time in a given day. Is it spent in a testing framework? Cleaning up data? Creating APIs? Reviewing code? Installing a CMS? Setting up CI workflows? Writing CSS? Configuring Webpack?\n\nWhatever you spend your time doing, day after day, is the thing that you will become an expert at. That’s why, as a web developer, I like to spend most of my time in “core” web technologies… things like HTML, CSS, JavaScript, the DOM, SQL and others. These are technologies I can invest in because they’re going to be around for the long haul (many of them are baked into browsers, after all). Knowing them well is likely to bring me value for years to come.\n\nSpending time in fringe technologies is like buying shares of AAPL, TSLA, or whatever else is hot right now. It can be fun, and it might be a good investment, but it’s a gamble. On the other hand, those core web technologies are like index funds. Kind of boring, but you can expect them to be valuable in the long term. And for careers, like investing, the long term is where all the interesting stuff happens.\n"
    },

@ajkendal, thanks for the PR! I should be able to test this out this weekend. 👍

@ajkendal, this is a great start and it's working great. I'll go ahead and merge this and if I find anything I want to tweak, I'll do that outside of this PR.
Thank you! 🎉

authors: ajkendal bryanbraun

license: mit


text:
add support for yield/progress calls

hope you like it :)

the name of the variable comes actually from the object unpacking:
let { receive_progress } = action.options;

now receive_progress is defined as option in autobahn-js.
but if you insist, i can bloat the code to please the linter ;)

Ahh, sure enough. While I prefer lower camel case in JS, since it's an inherited from autobahn name I guess I can live with it ;) I'll let you decide if you want to update it or not, not a big deal either way.
Could you maybe add a test for progress so we don't break it down the road by accident?

Hi dear @dodo !
I know you might be quite busy,  but can you comment this PR?

authors: Firanolfind brycedarling dodo

repo: brycedarling/redux-autobahn-js

license: WTFPL


text:
you should add some margin left and right to the datesheet

Assign me this issue, so that I can fix it

Alright I just assigned you

you can close this issue now @brycehadl

repo: brycehadl/stat-sheet


text:
Readme.md

'components' => [
...
'sendGrid' => [
'class' => 'bryglen\sendgrid\Mailer',
'username' => 'your_user_name',
'password' => 'your password here',
//'viewPath' => '@app/views/mail', // your view path here
],
...
],
class here is wrong

Whats wrong?
Sent from my iPad

On 2 Apr 2016, at 3:24 AM, BP notifications@github.com wrote:
'components' => [
...
'sendGrid' => [
'class' => 'bryglen\sendgrid\Mailer',
'username' => 'your_user_name',
'password' => 'your password here',
//'viewPath' => '@app/views/mail', // your view path here
],
...
],
class here is wrong
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub

When I downloaded it with composer the class in composer.json autoload psr4 was different than 'class' => 'bryglen\sendgrid\Mailer'. Now it's all good

authors: BenasPaulikas bryglen


text:
make rails3 the new master and make master into rails2

Paste-friendly :D
git checkout master
git checkout -b rails2
git push origin rails2
git checkout rails3
git branch -D master
git checkout -b master
git push -f origin master
git push origin :rails3

See my issue in the pull request: https://github.com/brynary/rack-bug/pull/39  If you just isolated the upgrade to 3 into a separate PR (since that pull request will merge into master) I'd merge it.  The issue is by doing all the pull requests from the same branch you include all the commits in each one.  And you added docs telling people how to use a branch, but the PR will merge rails 3 into master.
Make sense?

This issue is about changing brynary/master to being rails3 (not releated to my (now fixed) pull-requests)

Is this gonna happen? I sadly implemented my own fixes for rails3.
Having a gem released too would be nice!

authors: grosser halorgium timocratic

repo: brynary/rack-bug


text:
[Question] ValueError: columns cannot be a set

I have downloaded the dataset, but encountered the following error when importing the dataset. How can I fix it?

ValueError                                Traceback (most recent call last)
Cell In[22], line 1
----> 1 dataset = load_RML201610A_dataset(path=data_path)
2 print(len(dataset))
3 pprint(dataset.get_examples_per_class())
File G:\xxxcode\rfml-master\notebooks..\rfml\data\converters\rml_2016.py:129, in load_RML201610A_dataset(path)
121 UNPICKLED_PATH = "RML2016.10a_dict.pkl"
123 loader = RML2016DataLoader(
124     cache_path=CACHE_PATH,
125     remote_url=REMOTE_URL,
126     unpickled_path=UNPICKLED_PATH,
127     warning_msg=WARNING_MSG,
128 )
--> 129 return loader.load(path=path)
File G:\xxxcode\rfml-master\notebooks..\rfml\data\converters\rml_2016.py:35, in RML2016DataLoader.load(self, path)
30     if not os.path.exists(path):
31         raise ValueError(
32             "If path is provided, it must actually exist.  Provided path: "
33             "{}".format(path)
34         )
---> 35     return self._load_local(path=path)
37 # If this function has previously been called before to fetch the dataset from the
38 # remote, then it will have already been cached locally and unpickled.
39 if os.path.exists(self.UNPICKLED_PATH):
File G:\xxxcode\rfml-master\notebooks..\rfml\data\converters\rml_2016.py:53, in RML2016DataLoader._load_local(self, path)
51         for iq in data[(mod, snr)]:
52             builder.add(iq=iq, Modulation=mod, SNR=snr)
---> 53 return builder.build()
File G:\xxxcode\rfml-master\notebooks..\rfml\data\dataset_builder.py:156, in DatasetBuilder.build(self)
150 def build(self) -> Dataset:
151     """Build the Dataset based on the examples that have been added.
152
153     Returns:
154         Dataset: A compiled dataset consisting of the added examples.
155     """
--> 156     df = pd.DataFrame(self._rows, columns=self._keys)
157     return Dataset(df)
File G:\Users\xxx\anaconda3\envs\LYY2\Lib\site-packages\pandas\core\frame.py:675, in DataFrame.init(self, data, index, columns, dtype, copy)
673     raise ValueError("index cannot be a set")
674 if columns is not None and isinstance(columns, set):
--> 675     raise ValueError("columns cannot be a set")
677 if copy is None:
678     if isinstance(data, dict):
679         # retain pre-GH#38939 default behavior
ValueError: columns cannot be a set

Same problem here...

Try setting your pandas version to 1.4.4, the newer versions need some code fixes.
pip insatall pandas==1.4.4
Also, it looks like there is a PR to resolve this, I have not tried it yet however, you could also just clone that fork and work from there:
https://github.com/brysef/rfml/pull/5

Thanks @gawdygoda for alerting me to the activity here, #5 has been merged, hope it solves your issue! And thanks for @ArashSameni contribution.

authors: brysef gawdygoda yoavay zpsandzzc

repo: brysef/rfml


text:
Internal denoising doesn't work when 'render threads' is set to '0'

I'm working on a fix for this tonight but I just wanted to get it on the books in case anybody else runs across this. Long story short the denoise command line expects an actual number for rendering threads.  -1 works but '0' causes the denoiser to not launch, triggering an error

FYI I'm planning to put in code that will covert the setting to the proper thread count if the user sets it to '0' in the exporter.

Yep oh sorry I had a similar conversation with ryan a few months ago
On Saturday, June 18, 2016, Jon D notifications@github.com wrote:

I'm working on a fix for this tonight but I just wanted to get it on the
books in case anybody else runs across this. Long story short the denoise
command line expects an actual number for rendering threads. -1 works but
'0' causes the denoiser to not launch, triggering an error
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/bsavery/PRMan-for-Blender/issues/285, or mute the
thread
https://github.com/notifications/unsubscribe/ABzffNUDtP-keaTeEjfm4RrkfGvqxO4iks5qNHNpgaJpZM4I5DES
.

--
brian.savery@gmail.com
508-274-8700

repo: bsavery/PRMan-for-Blender


text:
cannot train when new vocab file is generated .

I included some of your own data and my own data and created vocab file. But when I trained the model bottrainer.py it starts for running first epoch and then stops giving the error as:
Traceback (most recent call last):
File "bottrainer.py", line 161, in
bt.train(res_dir)
File "bottrainer.py", line 88, in train
step_result = self.model.train_step(sess, learning_rate=learning_rate)
File "/home/ruksin/PycharmProjects/chatlearner/chatbot/modelcreator.py", line 122, in train_step
feed_dict={self.learning_rate: learning_rate})
File "/home/ruksin/PycharmProjects/chatlearner/venv/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 889, in run
run_metadata_ptr)
File "/home/ruksin/PycharmProjects/chatlearner/venv/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1120, in _run
feed_dict_tensor, options, run_metadata)
File "/home/ruksin/PycharmProjects/chatlearner/venv/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1317, in _do_run
options, run_metadata)
File "/home/ruksin/PycharmProjects/chatlearner/venv/lib/python3.5/site-packages/tensorflow/python/client/session.py", line 1336, in _do_call
raise type(e)(node_def, op, message)
tensorflow.python.framework.errors_impl.InvalidArgumentError: pos 0 out of range for stringb'' at index 0
[[Node: Substr = Substr[T=DT_INT32](arg0, Substr/pos, Substr/len)]]
[[Node: IteratorGetNext = IteratorGetNextoutput_shapes=[[?,?], [?,?], [?,?], [?], [?]], output_types=[DT_INT32, DT_INT32, DT_INT32, DT_INT32, DT_INT32], _device="/job:localhost/replica:0/task:0/device:CPU:0"]]
can anyone please help me with this. Im I doing any wrong?
i reduced the batch size to 2 and also the units to 800. I was able to train with your own data before , but when i tried it for my own data along with some of your data it shows this.
the vocab generator python file shows this result:
Vocab size after all base data files scanned: 256
Vocab size after cornell data file scanned: 18354
The final vocab file generated. Vocab size: 18380
Please can anyone help me with this.

It is very likely that your data is having some kind of problem, but I cannot tell without looking at the details. You can google around, and I believe I have seen similar errors before from someone else.


text:
Problem parsing % character as plain text

Hi, I've been using this awesome plugin but I found that there are some issues when a % symbol is written onto the .md file as plain text
Let me show a couple of examples

... test coverage of at least 70%. (Measures to show this for each PR will need to be investigated)

Threw this error

And had to be changed to

... test coverage of at least 70 percent (Measures to show this for each PR will need to be investigated)

Another example (with the url changed - in bold the part that stays the same and has the problem)

For that, first you need to configure kubectl like described here: https://mypage.com/folder/anotherfolder/guides_%26_docs/yetanotherfolder

Threw this error

And had to be changed to be shown as a link to work

For that, first you need to configure kubectl like described here DOCUMENTATION

While this kind of error requires a workaround that is not that terrible to do, the main issue at least for me was to actually understand what was going on. I think it worth checking if there's something that can be done for this.

Hi @sebastianaguerre
Thanks to use such plugin and for your valuable feedbacks.  I'll check asap

Hi @sebastianaguerre
I've find out the problem. during markdown parsing has been used String.format() and then % is marked as special char.
Currently you can add another % as workaround
test coverage of at least 70%%. (Measures to show this for each PR will need to be investigated)

Hi @sebastianaguerre
I've deployed version 7.9-SNAPSHOT with the fix. Please take a chance to test it so I can arrange a new production release

Also ran into this exact issue. Nice seeing it already being solved.
There's is an issue with 7.9 not being available however:
https://search.maven.org/artifact/org.bsc.maven/confluence-reporting-maven-plugin
https://mvnrepository.com/artifact/org.bsc.maven/confluence-reporting-maven-plugin
Strangely enough I was able to fetch 7.9-SNAPSHOT and can confirm that the fix  solves the issue with "%" in md files. (also figured out the "%%" workaround)
I would like however to use 7.9 and not  7.9-SNAPSHOT or 7.8+%% workaround so please lookinto the issue with 7.9 not being available

repo: bsorrentino/maven-confluence-plugin


text:
Update CHANGELOG.md

@btzr-io  Sorry! I notice that you merge the previous PR. So this is the Update on CHANGELOG, I discovered how to do :smile:

Oh lol, I was faster, thanks anyway :v:

authors: DaniAcu btzr-io

repo: btzr-io/Villain


text:
Make Go MaxThreads configurable

We're running into an issue where threads occassionally back up on IO, leading the service to crash with this error:
runtime: program exceeds 10000-thread limit
fatal error: thread exhaustion

Our host has sufficient spare memory to handle a much larger number of threads during IO hiccups, so we'd like to configure this value higher.
Is this a change you'd be open to upstreaming?
I've validated the MaxThreads limit gets set locally, but I'm open to also adding an automated test if it seems worthwhile (I'd run the service with BAZEL_REMOTE_MAX_THREADS=1 and expect a core dump with a runtime: program exceeds 1-thread limit error. I'm open to other suggestions).

Which version of bazel-remote are you running? In particular, I wonder if it has this fix or not: #480

We're running 2.3.4, which does indeed have that fix.
Sidenote: would it be worth setting the file removal semaphore based on this config too?

Sidenote: would it be worth setting the file removal semaphore based on this config too?

Perhaps. I wonder if you could share a stack trace when the issue occurs? It would be good to see where all the OS threads are being used.

We increased provisioned IOPS/throughput on the EBS device that backs our cache, and IOWait and used file handles both plummeted. I'm pretty sure this will solve our pain point, so maybe making this max thread count configurable isn't necessary - 10,000 OS threads is quite a lot as it is.. that said, having the option might be nice in a pinch, so open to discuss either way.

I wonder if you could share a stack trace when the issue occurs? It would be good to see where all the OS threads are being used.

I've attached it on this comment (it's rather large). Here's the summary of the goroutine states:
{'chan receive, 1 minutes' -> '1147'}
{'chan receive' -> '3357'}
{'chan receive, 4240 minutes' -> '48'}
{'chan send' -> '1'}
{'IO wait, 16 minutes' -> '1'}
{'IO wait, 1 minutes' -> '22'}
{'IO wait' -> '252'}
{'IO wait, 2 minutes' -> '2'}
{'IO wait, 3 minutes' -> '1'}
{'IO wait, 4221 minutes' -> '1'}
{'runnable' -> '8676'}
{'select, 10 minutes' -> '13'}
{'select, 11 minutes' -> '8'}
{'select, 13 minutes' -> '2'}
{'select, 14 minutes' -> '4'}
{'select, 15 minutes' -> '5'}
{'select, 16 minutes' -> '1'}
{'select, 17 minutes' -> '6'}
{'select, 18 minutes' -> '6'}
{'select, 19 minutes' -> '1'}
{'select, 1 minutes' -> '33'}
{'select, 23 minutes' -> '5'}
{'select, 25 minutes' -> '3'}
{'select, 26 minutes' -> '2'}
{'select, 27 minutes' -> '5'}
{'select, 29 minutes' -> '1'}
{'select, 2 minutes' -> '28'}
{'select, 3 minutes' -> '7'}
{'select, 4 minutes' -> '5'}
{'select, 5 minutes' -> '20'}
{'select, 6 minutes' -> '1'}
{'select, 7 minutes' -> '5'}
{'select, 8 minutes' -> '5'}
{'select' -> '9206'}
{'select, 9 minutes' -> '3'}
{'syscall' -> '1246'}
{'syscall, 1 minutes' -> '76'}

d481-crash-dump.tar.gz (sha256: 7a8329ce781726de03a3a3355d4cefb7bb92b91f4f3eafbb20902c08ba99bf32)

Thanks for providing the goroutine stack trace data.
I think a lot of these threads are blocked waiting for the file removal semaphore- grep -c Acquire bazel-remote-d481-dump.txt gives 6538 hits, which I think means there must have been 5000 in-flight operations that had already acquired the semaphore and were waiting for files to be removed.

We increased provisioned IOPS/throughput on the EBS device that backs our cache, and IOWait and used file handles both plummeted. I'm pretty sure this will solve our pain point, so maybe making this max thread count configurable isn't necessary - 10,000 OS threads is quite a lot as it is.. that said, having the option might be nice in a pinch, so open to discuss either way.

I think this is a better solution for your users- IMO the cache is less useful the slower it is.
I would prefer not to add new configuration options that might not be necessary, is it OK with you if we close this PR? We can always reopen it later if needed.

Yeah that sounds reasonable; thanks for the help :)

authors: SrodriguezO mostynb

repo: buchgr/bazel-remote


text:
Public user guide for audit tool

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

stupid backspace

repo: buda-base/asset-manager

license: Unlicense


text:
Missing buf_push symbol

When running gazelle with rules_buf v0.2.0 it generates the following BUILD file
load("@rules_buf//buf:defs.bzl", "buf_push")

buf_push(
    name = "buf_push",
    config = "buf.yaml",
    lock = "buf.lock",
    targets = ["@buf_deps_api//ride/driver/v1alpha1:v1alpha1_proto"],
)

However when running bazel build //... it throws the following error
ERROR: Traceback (most recent call last):
        File "/Users/debkanchan/Code/ride/backend/driver-service/api/BUILD.bazel", line 1, column 35, in <toplevel>
                load("@rules_buf//buf:defs.bzl", "buf_push")
Error: file '@rules_buf//buf:defs.bzl' does not contain symbol 'buf_push'
ERROR: package contains errors: api
ERROR: package contains errors: api: Traceback (most recent call last):
        File "/Users/debkanchan/Code/ride/backend/driver-service/api/BUILD.bazel", line 1, column 35, in <toplevel>
                load("@rules_buf//buf:defs.bzl", "buf_push")
Error: file '@rules_buf//buf:defs.bzl' does not contain symbol 'buf_push'
ERROR: Skipping '//...': Error evaluating '//...': error loading package 'api': Package 'api' contains errors
WARNING: Target pattern parsing failed.
ERROR: Error evaluating '//...': error loading package 'api': Package 'api' contains errors
INFO: Elapsed time: 12.372s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (14 packages loaded)

I see, gazelle is still generating them. I'll update it to exclude buf_push. Thank you for reporting this!

authors: DebkanchanSamadder srikrsna-buf


text:
TypeError: Cannot read property 'createErrorBoundary' of undefined

Following the Bugsnag Docs to config the project and run got this error from:
const ErrorBoundary = Bugsnag.getPlugin('react').createErrorBoundary(React);

react 16.11.0
react-native 0.62.2
@bugsnag/react-native 7.5.0

Hi @duzliang ,
Could you confirm what error you are seeing? Also could you share you Bugsnag configuration code for both your JS and native layers. Feel free to email support@bugsnag.com if you don't want to share this information publicly.
Thanks

@johnkiely1 Thank you for viewing this issue:
Both the Android and iOS configuration are set up step by step by the Docs
Below is a simple Javascript code snippets:

App.js

import Bugsnag from '@bugsnag/react-native';

import ErrorView from './containers/ErrorView';

const ErrorBoundary = Bugsnag.getPlugin('react').createErrorBoundary(React);

export default class AppRepair extends React.Component {
  constructor(props) {
    Bugsnag.start();
  }

 render() {
    return (
      <ErrorBoundary FallbackComponent={ErrorView}>
        <Provider store={store}>
          <Routes handleExit={this.handleExit} />
        </Provider>
      </ErrorBoundary>
    );
  }
}

index.js

import { AppRegistry } from 'react-native';
import App from './src/App.js';
import { name as appName } from './app.json';

AppRegistry.registerComponent(appName, () => App);

when running the App, get the error:
TypeError: Cannot read property 'createErrorBoundary' of undefined

I'm having the same problem here.

react 16.13.1
react-native 0.63.2
@bugsnag/react-native 7.5.1

@duzliang
The issue is that you're calling Bugsnag.getPlugin('react') before you call Bugsnag.start().
Bugsnag.start() must be called before any other method so you'll need to move it out of the constructor of your component.

Move it out of the constructor also get the Error while open the Debug mode of React Native Debug Menu
import Bugsnag from '@bugsnag/react-native';

import ErrorView from './containers/ErrorView';

Bugsnag.start();

const ErrorBoundary = Bugsnag.getPlugin('react').createErrorBoundary(React);

export default class AppRepair extends React.Component {
  constructor(props) {
  }

 render() {
    return (
      <ErrorBoundary FallbackComponent={ErrorView}>
        <Provider store={store}>
          <Routes handleExit={this.handleExit} />
        </Provider>
      </ErrorBoundary>
    );
  }
}

That does look like a bug, although one that would only have an impact when the debugger is attached.
We'll look into whether this can be resolved in a future release.

Is there a workaround for this? Being unable to attach a debugger makes getPlugin unusable.
I'm using the reactNavigation, being core app functionality I'm not sure there's a way to lazily load this.
Any recommendations on a fix? happy to help if I can get pointed in the right direction.

Hey @adkenyon, we're looking into a fix for this notifier side. But, in the meantime you can guard against this by checking whether the getPlugin() call returns undefined, and in these cases point your application to a no-op ErrorBoundary, for example:
class NoopErrorBoundary extends React.Component {
    // define your Noop Error Boundary here
}

var ErrorBoundary;
if (typeof Bugsnag.getPlugin('react') === 'undefined') {
    ErrorBoundary = NoopErrorBoundary;
} else {
    ErrorBoundary = Bugsnag.getPlugin('react').createErrorBoundary(React);
}

// use the ErrorBoundary as normal

When running without the debugger, Bugsnag will continue as normal with the Bugsnag error boundary.

@xander-jones thank you for the workaround!

Can you please reference this in your documentation until this is released?
I just spend 2-3 hours thinking I setup my app was wrong, meticulously looking at the docs, but it looks like this feature just doesn't work at all, even with the base case in the documentation.

Can you please reference this in your documentation until this is released?
I just spend 2-3 hours thinking I setup my app was wrong, meticulously looking at the docs, but it looks like this feature just doesn't work at all, even with the base case in the documentation.

Fixed in v7.6.1

Fixed in v7.6.1

What i can do with code push if i need call asyncronus
const data = await codePush.getUpdateMetadata();
  const codePushVersLabel = `${data?.label}-${getVersion()}`;
  Bugsnag.start({
    codeBundleId: codePushVersLabel,
    onError,
  });

const ErrorBoundary = Bugsnag.getPlugin('react').createErrorBoundary(React);
and
<ErrorBoundary
      onError={onError}
      FallbackComponent={ErrorFullscreenComponent}>
      {props.children}
    </ErrorBoundary>

Bugsnag is crashing and i have to add second block Bugsnag.start call
Bugsnag.start({
  onError,
});

👋  Hey @interhub, you should start Bugsnag synchronously as soon as you can in your application to ensure that you're capturing all errors. This also means that you'll be able to create your ErrorBoundary as soon as possible too, which I suspect would alleviate the need to start Bugsnag outside of your async await method. A second call to Bugsnag.start(), if Bugsnag is already running, would be ignored, you'd see the following in your console:
[bugsnag] Bugsnag.start() was called more than once. Ignoring.

I appreciate that you're looking to get the CodePush label async on the launch of the application to set the codeBundleId, however, this codeBundleId should be hardcoded into your JS bundle as it's needed at launch immediately. You may wish to inject this codeBundleId value at bundle build time as with CodePush, you'll always know what the next label is going to be as it's always going to be vX+1 where vX is the current label.
If you're seeing Bugsnag crash though, please do let us know with a new issue on this repo with details of the crash & what's happening to cause the crash, and we'll take a look into this! :)

you should start Bugsnag synchronously as soon as you can in your application to ensure that you're capturing all errors.

appreciate that you're looking to get the CodePush label async on the launch of the application to set the codeBundleId, however, this codeBundleId should be hardcoded into your JS bundle as it's needed at launch immediately. You may wish to inject this codeBundleId value at bundle build time as with CodePush, you'll always know what the next label is going to be as it's always going to be vX+1 where vX is the current label.

@xander-jones I think this is related to an issue I think a lot of user's might have which is that while starting Bugsnag should be synchronous, CodePush users want to specify the codeBundleId when starting Bugsnag which is asynchronous:
await CodePush.getUpdateMetadata(CodePush.UpdateState.RUNNING)
Perhaps you could add some docs on how to "inject this codeBundleId value at bundle build time" OR specify in the docs https://docs.bugsnag.com/platforms/react-native/react-native/codepush/ that users should figure out how to do this themselves.
Should I start a separate issue on this topic? I feel a few Bugsnag + CodePush users might have this issue as I've had this on multiple apps.

Hey @henrymoulton, sure; it's difficult to specify an exact method that you should use as people use all sort of different build pipelines, and architect their apps in different ways. However, hopefully the following information will be hopefully be starting point for you? The concept here is to prep the source to have a codeBundleId equal to the binary version and the future CodePush label, if it's a CodePush update, else it'll just be set to the binary version
First, in index.js, I've added the following to grab version and codePushLabel from the package.json:
import Bugsnag from '@bugsnag/react-native';

const version = require("./package.json").version
const codePushLabel = require('./package.json').codePushLabel

Bugsnag.start({
  codeBundleId: version + (codePushLabel == null ? '' : '_' + codePushLabel)
});

Now, in package.json I've put a placeholder codePushLabel key, with a value of null:
{
  "name": "CodePushHarness",
  "version": "1.0.0",
  "codePushLabel": null,
// ...

Next, we need to manipulate that codePushLabel value before we make a build. In this case, if releasing a binary, it should be set to null, else it should be set to the label which CodePush is going to set in future when you release.
This is where things diverge slightly depending on how you're building, but the following is a Node.js example I've put together, you can call this using node codepush.js STAGE BINARYVERSION.
It will:

Make a call to AppCenter to work out what the current label is for the stage provided
Increment that label by one and write it to the package.json's codePushLabel key, or set it to v1 if no CodePush release has happened yet.
Run the CodePush release (releaseCodepushUpdate())

⚠ This is example code, and I'd highly recommend testing this before pushing anything live to production! Whilst I've tested this on a simple application, it doesn't take into account if you're running multiple parallel binary versions with CodePush updates on each.
const exec = require('child_process').exec
const fs = require('fs')

if (process.argv.length < 4) {
    console.error("Missing input args. Usage: node codepush.js STAGE BINARYVERSION")
    process.exit(1)
}

// Which stage are you deploying to?
const stage = process.argv[2]
console.debug("stage", stage)

// Which binary version is being targeted?
const binaryVersion = process.argv[3]
console.debug("binaryVersion", binaryVersion)

function injectLabelToPackage(label) {
    const pjsonFilename = "./package.json"
    const pjsonHandle = require(pjsonFilename)
    pjsonHandle.codePushLabel = label
    fs.writeFile(pjsonFilename, JSON.stringify(pjsonHandle, null, 2), function writeJSON(err) {
        if (err) {
            console.error(err)
            process.exit()
        } else {
            return console.debug(`Set codePushLabel to ${label} in ${pjsonFilename}`)
        }
    })
}

function releaseCodepushUpdate() {
    exec(`appcenter codepush release-react -d ${stage} -t ${binaryVersion} --output-dir build`, function(error, stdout, stderr){
        console.log(stdout)
        console.error(stderr)
    })
}

exec("appcenter codepush deployment list --output json", function(error, stdout, stderr){
    var codePushDeploymentList = JSON.parse(stdout)
    var thisDeployment = codePushDeploymentList.find(obj => {
        return obj.name == stage
    })

    console.debug("codePushDeploymentList", codePushDeploymentList)
    console.debug("thisDeployment", thisDeployment)

    if (thisDeployment !== undefined) {
        var newLabel = null

        if (thisDeployment.latestRelease.label !== undefined) {
            // a CodePush label already exists for this stage
            const currentLabel = thisDeployment.latestRelease.label
            console.debug("currentLabel", currentLabel)
            newLabel = "v" + (parseInt(currentLabel.substring(1, currentLabel.length)) + 1)
        } else {
            // no CodePush releases have been made yet for this stage, so this will be v1
            newLabel = "v1"
        }

        console.debug("newLabel", newLabel)
        injectLabelToPackage(newLabel)

        // execute your CodePush release here.
        releaseCodepushUpdate()
    } else {
        console.error(`Stage '${stage}' doesn't exist`)
        process.exit(1)
    }
})

In our docs we do mention that the codeBundleId does not need to match the label at all and that it's up to you to decide what you want this value to be, but it does need to be incremented for each release. It's purely just an identifier for matching source maps and can be anything, a semver, or a commit SHA etc.: https://docs.bugsnag.com/platforms/react-native/react-native/codepush/#setting-a-code-bundle-id

Hi @neb-b - Bugsnag.getPlugin('react') would only return undefined if BugsnagPluginReact is not passed into the Bugsnag.start() plugins property, or if Bugsnag.getPlugin('react') is called before Bugsnag.start().
Is it possible that one of these conditions were met when you saw your production crash (e.g. if Bugsnag.start was wrapped inside some condition that prevented it from being called prior to getting the plugin)?

@luke-belton thanks for the info. Based on that, there must have been issues with the app reading the bugsnag api key, so I'm guessing it was undefined.

@luke-belton upon further investigation, it doesn't appear that the app would have issues reading the api key so everything was passed in correctly. Bugsnag.start also wasn't wrapped in any conditional that would have prevented it from not being called.
Our issue started from netlify network request errors, but our error logs were filled with TypeError: Cannot read property 'createErrorBoundary' of undefined at the same time, so it seems to be there could be some other case where Bugsnag.getPlugin('react') could start returning undefined (albeit not under normal circumstances)

Hi @neb-b, we're not aware of any other case in which the call to Bugsnag.getPlugin('react') would return undefined. If the configuration is as above (with Bugsnag.start() being called first, passing in BugsnagPluginReact) we would always expect this to return the initialised plugin. However if you're able to provide a reproduction case we'd be more than happy to investigate further.

@yousif-bugsnag it appears there were a lot of network errors from netlify around that time. Could it be possible that the POST request to session.bugsnag.com failed in a way that would lead to Bugsnag.getPlugin('react') returning undefined? Could you share where that code is so I can try to reproduce? I am having issues finding it

Hi @neb-b, failed network requests to sessions.bugnsag.com would not cause Bugsnag.getPlugin() to return undefined. This would only happen in the scenarios described above.

Could you share where that code is so I can try to reproduce? I am having issues finding it

Here is the getPlugin() implementation in the client in case it helps debugging your issue: https://github.com/bugsnag/bugsnag-js/blob/2005796d965e6a8460896c2946337489d7e619e7/packages/core/client.js#L190-L192
And the React plugin lives here: https://github.com/bugsnag/bugsnag-js/tree/master/packages/plugin-react

Since nextjs cannot render on the build step, does this mean you can't use the ErrorBoundary there?
https://github.com/bugsnag/bugsnag-js/blob/next/examples/js/nextjs/lib/bugsnag.js

authors: adkenyon duzliang henrymoulton interhub johnkiely1 kennethjiang luke-belton mattdyoung neb-b parkwherever wildseansy xander-jones yousif-bugsnag

repo: bugsnag/bugsnag-js


text:
Problem with main repo app: book purchase

After deploying the app both in local env and production env (zeit), I found: a regular user could not open the book and read the chapter even though:

it shows the book on the list of 'Your books' after going through the purchasing procedure.

After trying open it, it show the TOC, and big blue 'Buy button'

but it worked when I follow the instructions and code of chapter-8 book/8-end

I am using macPro, chrome.

thanks

Hi @klyburke
The issue is related to the main repository, not about the tutorial code (book chapter-8 code).
the only changes in my clone are

the ROOT_URL
all kinds of env variables

-John

Hi @klyburke
I tried a clean deployment locally with my own secrets, and completed the purchase process with the demo-book (forked from your demo-book repository), I checked the database:

No Purchase document inside the purchase collect

there is parameter  purchasedBookIds in the User document as below:

{
    "_id": {
        "$oid": "5b7ac4c6672fe01f04a62e89"
    },
    "isAdmin": false,
    "purchasedBookIds": [
        "5b7ac4ad672fe01f04a62e88"
    ],
    "freeBookIds": [],
    "isGithubConnected": false,
    "createdAt": {
        "$date": "2018-08-20T13:40:22.868Z"
    },
     .....

    "__v": 0
}

let me know if you need more information to resolve it.
thanks
-John

@johnking Thanks for your response about DB.
The fact that your User doc has purchasedBookIds (line 237 does run) but Purchase doc is not created (line 265 does not run) - means that either AWS SES or Mailchimp returned caught error. And code that created Purchase doc did not run.
@johnking please take a look at below snippet:
https://github.com/builderbook/builderbook/blob/146ade6be3f39261d174360a08cd55921667bd03/server/models/Book.js#L237-L272
Clear DB and try purchasing book again.
Please monitor logs in your terminal, you should see either server error:
logger.error('Email sending error:', error);
or
logger.error('Mailchimp error:', error);
@klyburke Thanks for narrowing down on potential problem.

Hi @tima101 @klyburke ,
I repeated the steps based on your instructions, but I did not find any log errors related to AWS SES or Mailchimp, and I did not receive the purchase notification email either. I could receive the notification email based on chapter 8-end code.

both the console logs and in-application message give me a not found error message.
The DB has the same status, there is no Purchase document created inside the purchase collection.

@johnking Alright, this helps to narrow down problem even further.
You did not get purchase email via AWS SES.
Was your email address added to Mailchimp list?
Please comment out these 2 blocks of code and test purchase again (remember to clear relevant data in DB):
    const template = await getEmailTemplate('purchased', {
      userName: user.displayName,
      bookTitle: book.name,
      bookUrl: `https://builderbook.org/books/${book.slug}/introduction`,
    });

    try {
      await sendEmail({
        from: `Kelly from builderbook.org <${process.env.EMAIL_SUPPORT_FROM_ADDRESS}>`,
        to: [user.email],
        subject: template.subject,
        body: template.message,
      });
    } catch (error) {
      logger.error('Email sending error:', error);
    }

    try {
      await subscribe({
        email: user.email,
        listName: 'purchased',
      });
    } catch (error) {
      logger.error('Mailchimp error:', error);

The goal is to create Purchase doc successfully.
After that we will investigate why purchase email was not sent by AWS SES.
Thanks.

Hi @tima101 ,
The purchase flow is successful this time by commenting out the lines as specified above!
I double checked that my second gmail address IS in the mailchimp MAILCHIMP_PURCHASED_LIST_ID.
let me know what I should test next.
thanks

@johnking Great. This means that Mailchimp works as expected but not AWS SES.
Please comment out only this block of code to confirm our conclusion:
    const template = await getEmailTemplate('purchased', {
      userName: user.displayName,
      bookTitle: book.name,
      bookUrl: `https://builderbook.org/books/${book.slug}/introduction`,
    });

    try {
      await sendEmail({
        from: `Kelly from builderbook.org <${process.env.EMAIL_SUPPORT_FROM_ADDRESS}>`,
        to: [user.email],
        subject: template.subject,
        body: template.message,
      });
    } catch (error) {
      logger.error('Email sending error:', error);
    }

If purchase works then problem is within above code block.
I may have found the problem, try fixing, replace purchased with purchase inside:
const template = await getEmailTemplate('purchased', {
I think your DB has docs in EmailTemplates collection, one has name welcome and second has name purchase. Thus error.
This means that third-party APIs work fine and you created/added proper env variables. Problem is in wrong name for email template. template variable is likely undefined in:
    const template = await getEmailTemplate('purchased', {
      userName: user.displayName,
      bookTitle: book.name,
      bookUrl: `https://builderbook.org/books/${book.slug}/introduction`,
    });

If you confirm all above, please create pull request for fix.
Thanks for running code and debugging, I could not run app since my env variable are on different machine.

@johnking Have you seen our SaaS boilerplate: https://github.com/async-labs/saas ?
If you happen to run/test/use our SaaS app, you are welcome to create pull requests in that repo as well.
Thanks.

hi @klyburke ,
thanks for your invitation, I will try your SaaS boilerplate later.

authors: johnking klyburke tima101

repo: builderbook/builderbook


text:
IFC Version NOT required

Note: moved here from https://github.com/CBenghi/ids-tool/issues/1 by @cicciopage
The tool requires that "ifcVersion" attribute inside "Specification" node is mandatory.
According to XSD, the "ifcVersion" attribute must be present but it could be empty.
Example:

<ids:specification ifcVersion=""
		                   name="Spec 1"
		                   minOccurs="1"
		                   maxOccurs="1">
	<ids:applicability/>
	<ids:requirements/>
</ids:specification>

<ids:specification ifcVersion="IFC2X3 IFC4 IFC4X3"
		                 name="Spec 2"
		                 minOccurs="1"
		                 maxOccurs="unbounded">
	<ids:applicability/>
	<ids:requirements/>
</ids:specification>

XSD:
<xs:attribute name="ifcVersion" use="required">
	<xs:simpleType>
		<xs:list>
			<xs:simpleType>
				<xs:restriction base="xs:string">
					<xs:enumeration value="IFC2X3"/>
					<xs:enumeration value="IFC4"/>
					<xs:enumeration value="IFC4X3"/>
				</xs:restriction>
			</xs:simpleType>
		</xs:list>
	</xs:simpleType>
</xs:attribute>

Thanks @cicciopage,
I'm actually not sure how I would interpret the empty string.
I see two options:

no schema is acceptable (in which case the error is justified).
all schemas are acceptable, but then why not list them all?

What would you do? I think this conversation needs to be had on the main IDS schema repository.
Best,
Claudio

XSD Schema is quite clear: IFCVersion attribute is required but it can be an empty string. One way to resolve the problem, that I can suggest, is if IFCVersion is empty not return an error but manage the file like if IFCVersion value is all available IFC versions.

I agree, but I think this needs to be a conversation on the main repository for IDS.

Ok, I think it's better we move the conversation on main repository, but I don't know how.

Just open a new issue there IDS

moved here:
https://github.com/buildingSMART/IDS/issues/160

authors: CBenghi cicciopage

repo: buildingSMART/IDS-Audit-tool


text:
redirection via > is not possible

e.g.: I can't disable quoting even though the command option of the docker plugin should allow me to pass things verbatim.
A step like this:
  - label: ':bash: Lint: SH'
    command: ''
    artifact_paths:
      - web/target/shellcheck-*.xml
    plugins:
      - 'docker#v3.3.0':
          image: 'koalaman/shellcheck:v0.7.0'
          debug: false
          workdir: /workdir
          command:
            - '-x'
            - a.sh
            - '--format'
            - checkstyle
            - '>'
            - web/target/shellcheck-42820572-83ee-4588-abf2-4f761754dba9.xml

results in:
koalaman/shellcheck:v0.7.0 -x x.sh --format checkstyle \> web/target/shellcheck-42820572-83ee-4588-abf2-4f761754dba9.xml

which means the output of the docker image is not redirected and thus not picked up as an artifact.

This is not specific to shellcheck but to any docker image - just in case you want to suggest using https://github.com/buildkite-plugins/shellcheck-buildkite-plugin for this particular problem: it also can't redirect the output and shellcheck doesn't have a first-class --out my.file flag either.

I reckon this is probably outside the scope of what the docker plugin is supposed to do 🤔
I'd be happy to add support to the shellcheck plugin to write to a file? Alternately, perhaps it's easier to just call docker directly in a shellscript for this usecase?

I can definitely write a wrapper or something, but I think output redirection would be a responsibility of the plugin?

From what I can see, this would be expected (albeit quite annoying) behaviour.
The command docker run ... image arg1 arg2 arg3 > output_file would redirect the output of the docker command, not what is run inside of the container itself. As you are clearly specifying that the redirection character is part of the docker command, it needs to be escaped or it wouldn't be passed on to the command running in the container... which will error out or ignore it. This is mostly because output redirection is a feature of terminal shells, not docker nor the programs run in them.
The way to workaround this issue is to use a shell as the command being executed. For example:
- label: ':bash: Lint: SH'
    command: ''
    artifact_paths:
      - web/target/shellcheck-*.xml
    plugins:
      - 'docker#v3.3.0':
          image: 'koalaman/shellcheck:v0.7.0'
          command:
            - '/bin/sh'
            - '-c'
            - 'shellcheck -x a.sh --format checkstyle > web/target/shellcheck-42820572-83ee-4588-abf2-4f761754dba9.xml'

Which is exactly what happens when you specify the command to be run through the step's command instead of the plugin's command option:
- label: ':bash: Lint: SH'
    command: 'shellcheck -x a.sh --format checkstyle > web/target/shellcheck-42820572-83ee-4588-abf2-4f761754dba9.xml'
    artifact_paths:
      - web/target/shellcheck-*.xml
    plugins:
      - 'docker#v3.3.0':
          image: 'koalaman/shellcheck:v0.7.0'

Note that this assumes that the image you are using is not forcing a particular executable through entrypoints (in which case you may have to override it)

I believe there is nothing wrong with the plugin so I am closing this issue. Feel free to reply if you think it shouldn't have and we'll re-open it and continue the discussion

authors: joscha lox toote


text:
Allow junits_dir to match hidden files and dirs

Hi! 👋
Had a build pipeline that involved uploading files from directories nested within a hidden directory.
The artifact path is able to pick up hidden files and folders on upload and download, so I think the plugin should follow the same behaviour.
Hope everyone at buildkite is doing well.

Hi @cursande! Sorry for the long delay! 😅 This looks good, thanks for your contributions! 🙏🏻

No worries @pzeballos :smile: though looks like the assertion in the test I originally wrote needs to be updated due to more recent mainline changes

Are you able on doing those changes @cursande? This time will be faster 😅

@pzeballos
https://github.com/buildkite-plugins/junit-annotate-buildkite-plugin/pull/156

authors: cursande pzeballos


text:
No fake exits

follows on from #899 to add a feature where the golang implementation detail-derived -1 exit status is never passed to Buildkite, meaning that it will henceforth only be returned from Buildkite itself, and thus have a single meaning
please see EXPERIMENTS.md where I’ve put together a description of what this aims to achieve

@ticky what's left to get this into a ready for review state?

Backend support, unfortunately; Buildkite/Buildkite#4802

It'd still be a great idea for this to be resurrected!

authors: chloeruka ticky

repo: buildkite/agent


text:
Naming inconsistency between docs and version 0.1.0

Howdy 👋
I was delighted and surprised to see Swift support in Test Analytics 🎉 🙇♂ Thank you very much for that. It's not every day that I found a CI tool with early support for Apple-platform tooling.
I've been trying to setup Test Analytics in one of our libraries at Automattic and noticed a minor issue.
Issue
The docs, which I assume are code-generated from the README.md say to use BuildkiteTestCollector as the package name, but in version 0.1.0 the name is BuildkiteCollector.
This will result in errors along the lines of:
error: product 'BuildkiteTestCollector' required by package '...' target '...' not found.

Proposed Solution
I think tagging a new version should be enough to solve this issue, given that BuildkiteTestCollector is the current name of the package.
Thanks ✨

Hey @mokagio!
Thanks for bringing this up. I've just created v0.1.1, can you confirm it's working as expected.
Also, would love to get your feedback on the collector after you've had a chance to test it out :)

Hey @iampatbrown 👋 Thank you for the super quick followup 🎖
The name update worked:

However, xcodebuild failed to compile the package 🤔
▸ Compiling Tracer+Live.swift
--
  |
  | ❌  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/SourcePackages/checkouts/test-collector-swift/Sources/Core/Tracer/Tracer+Live.swift:32:38: cannot assign value of type 'Double?' to type 'TimeInterval' (aka 'Double')
  |
  | span.duration = span.startAt.map { endAt - $0 }
  | ^~~~~~~~~~~~~~~~~~~~~~
  |
  |
  |
  | ❌  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/SourcePackages/checkouts/test-collector-swift/Sources/Core/Tracer/Tracer+Live.swift:19:88: missing argument for parameter 'duration' in call
  |
  | let span = Trace.Span(section: section, startAt: systemUptime(), detail: detail)
  | ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
  |
  |
  | ▸ Compiling Tracer.swift
  |
  | ❌  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/SourcePackages/checkouts/test-collector-swift/Sources/Core/Tracer/Tracer+Live.swift:32:38: cannot assign value of type 'Double?' to type 'TimeInterval' (aka 'Double')
  |
  | span.duration = span.startAt.map { endAt - $0 }
  | ^
  |
  |
  |
  | ❌  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/SourcePackages/checkouts/test-collector-swift/Sources/Core/Tracer/Tracer+Live.swift:19:88: missing argument for parameter 'duration' in call
  |
  | let span = Trace.Span(section: section, startAt: systemUptime(), detail: detail)
  | ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
  |
  |
  |
  | ⚠  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/Build/Intermediates.noindex/BuildkiteTestCollector.build/Debug-iphonesimulator/Core.build/Objects-normal/x86_64/Tracer.dia:1:1: Could not read serialized diagnostics file: error("Invalid diagnostics signature") (in target 'Core' from project 'BuildkiteTestCollector')
  |
  | Command CompileSwift failed with a nonzero exit code
  | ^
  |
  |
  | ▸ Compiling UploadClient+Live.swift
  |
  | ❌  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/SourcePackages/checkouts/test-collector-swift/Sources/Core/Tracer/Tracer+Live.swift:32:38: cannot assign value of type 'Double?' to type 'TimeInterval' (aka 'Double')
  |
  | span.duration = span.startAt.map { endAt - $0 }
  | ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
  |
  |
  |
  | ❌  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/SourcePackages/checkouts/test-collector-swift/Sources/Core/Tracer/Tracer+Live.swift:19:88: missing argument for parameter 'duration' in call
  |
  | let span = Trace.Span(section: section, startAt: systemUptime(), detail: detail)
  | ^
  |
  |
  |
  | ⚠  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/Build/Intermediates.noindex/BuildkiteTestCollector.build/Debug-iphonesimulator/Core.build/Objects-normal/x86_64/UploadClient+Live.dia:1:1: Could not read serialized diagnostics file: error("Invalid diagnostics signature") (in target 'Core' from project 'BuildkiteTestCollector')
  |
  | Command CompileSwift failed with a nonzero exit code
  | ^
  |
  |
  | ▸ Compiling UploadClient.swift
  |
  | ❌  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/SourcePackages/checkouts/test-collector-swift/Sources/Core/Tracer/Tracer+Live.swift:32:38: cannot assign value of type 'Double?' to type 'TimeInterval' (aka 'Double')
  |
  | span.duration = span.startAt.map { endAt - $0 }
  | ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
  |
  |
  |
  | ❌  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/SourcePackages/checkouts/test-collector-swift/Sources/Core/Tracer/Tracer+Live.swift:19:88: missing argument for parameter 'duration' in call
  |
  | let span = Trace.Span(section: section, startAt: systemUptime(), detail: detail)
  | ^
  |
  |
  |
  | ⚠  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/Build/Intermediates.noindex/BuildkiteTestCollector.build/Debug-iphonesimulator/Core.build/Objects-normal/x86_64/UploadClient.dia:1:1: Could not read serialized diagnostics file: error("Invalid diagnostics signature") (in target 'Core' from project 'BuildkiteTestCollector')
  |
  | Command CompileSwift failed with a nonzero exit code
  | ^
  |
  |
  | ▸ Compiling DispatchGroup.swift
  |
  | ❌  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/SourcePackages/checkouts/test-collector-swift/Sources/Core/Tracer/Tracer+Live.swift:32:38: cannot assign value of type 'Double?' to type 'TimeInterval' (aka 'Double')
  |
  | span.duration = span.startAt.map { endAt - $0 }
  | ~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
  |
  |
  |
  | ❌  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/SourcePackages/checkouts/test-collector-swift/Sources/Core/Tracer/Tracer+Live.swift:19:88: missing argument for parameter 'duration' in call
  |
  | let span = Trace.Span(section: section, startAt: systemUptime(), detail: detail)
  | ^
  |
  |
  |
  | ⚠  /usr/local/var/buildkite-agent/builds/builder/automattic/tracks-ios/.build/derived-data/Build/Intermediates.noindex/BuildkiteTestCollector.build/Debug-iphonesimulator/Core.build/Objects-normal/x86_64/DispatchGroup.dia:1:1: Could not read serialized diagnostics file: error("Invalid diagnostics signature") (in target 'Core' from project 'BuildkiteTestCollector')

I get the same errors when trying on my local machine.

Also, would love to get your feedback on the collector after you've had a chance to test it out :)

I'm just going through the setup steps. I haven't been able to see any analytics yet 🤔 Even when using version 0.1.0 with the appropriate name, I don't see any results coming through in the tests analytics UI. That is, it still shows the "Complete setup" flow.
One thing I noticed is that the examples in the repo use swift test. So far, I tried to include it in the WordPress iOS repo, using SPM from Xcode, and the repo linked above, which is an internal library. Neither of them uses swift to run the tests, actually, both use Fastlane, which uses xcodebuild under the hood. I'm pointing this out in case swift test is the only supported way in which the integration works.

@mokagio I'll fix that asap. That was a mistake on my end :) It should work fine with xcodebuild I believe 0.1.0 had an old endpoint as well. I'll get back yo you in more detail shortly. Wan't to fix the duration bug quickly.

@mokagio I re-released it as v0.1.1. Sorry about that. I had included a change from a dev branch unintentionally.

No worries. I'll try it out right now 👍

@iampatbrown Happy to report that the fixed 0.1.1 version resulted in a green build... and I now have access to the Test Analytics 🎉

I wonder why it didn't work before with version 0.1.0? 🤔
I'm going to be trying on WordPress iOS between today and tomorrow. WordPress iOS uses Nimble here and there, which should answer the question from #12.
As far as I'm concerned, this issue can be closed. Thanks again 🙇♂

Regarding swift test and xcodebuild both should work. I have been using GitHub workflows during development and would test across all platforms. Here is a workflow that uses xcodebuild. I haven't tested with Fastlane myself, but will look at setting something up.
The plan is to use Buildkite pipelines (see Configure Buildkite pipelines (#2)) for the main branch as well as provide more comprehensive examples. We didn't have enough time to get this set up before launch but it's in the works.
There is also a bit undocumented/wip so if you have anymore questions just ask and I can help fill in the gaps :)

@mokagio Awesome thanks for your patience :)
I noticed you were using it with an ObjC test target. I never actually tested this myself. I'll make a note to add an ObjC test case/example as well.
Let me know if there are any more issues.
Thanks for giving it a test drive! :)

authors: iampatbrown mokagio

repo: buildkite/test-collector-swift


text:
🛑 Our Collective Experience is down

In 21d78c9, Our Collective Experience (http://www.ourcollectiveexperience.com/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Our Collective Experience is back up in 3de86f0.

repo: buligadragos/UpTime


text:
🛑 GOTO Parking is down

In ed69563, GOTO Parking (https://gotoparking.ro) was down:

HTTP code: 0
Response time: 0 ms

Resolved: GOTO Parking is back up in 8a3149e.


text:
Fix invitation lists test

A second attempt to close #1028.
Going with the sleep method because of the failure presented here

FWIW, things are consistently passing locally for me. Maybe there's something on the CI environment that I'm missing.

Just re-ran the job for this PR a couple of times, here are the last three times.
https://app.circleci.com/pipelines/github/bullet-train-co/bullet_train/2796/workflows/1bf3cea2-77f7-4d49-b6a8-e7cb07dc3c63/jobs/15103
https://app.circleci.com/pipelines/github/bullet-train-co/bullet_train/2796/workflows/88972ffd-f739-4d7f-9d37-cc30f67cb3db/jobs/15117
https://app.circleci.com/pipelines/github/bullet-train-co/bullet_train/2796/workflows/d1a1cf73-7737-4d30-bf6c-80651c6ac295/jobs/15123

Dang. Doesn't seem like this did the trick:
https://app.circleci.com/pipelines/github/bullet-train-co/bullet_train/2803/workflows/ba23073a-70a4-439e-97ca-115851487e00/jobs/15178?invite=true#step-114-6850_20

authors: gazayas jagthedrummer


text:
Bundler prints some warnings to standard output

For example, running bundle exec some_command when an outdated Bundler is installed produces output like:
The latest bundler is 1.15.3, but you are currently running 1.15.1.
To update, run `gem install bundler`

That is a helpful message to be sure, but the warning message is printed to STDOUT instead of STDERR, which is problematic if you are trying to consume the output of some_command. I could (almost) see Bundler being lax about where the output for Bundlers own commands like bundle install get printed, but bundle exec is there to provide a way to run Bundler-enabled scripts, which quite reasonably should not expect their output stream to contain messages from Bundler.

Bundler will print warnings to stderr in version 2

Also, in 1.15.3, that warning won't be printed at all when running bundle exec

authors: colby-swandale segiddins zetetic

repo: bundler/bundler


text:
Limit bundler's own update notice to stable releases

When running bundle, it (currently) shows the following update notice:
The latest bundler is 1.16.0.pre.3, but you are currently running 1.15.4.
To update, run `gem install bundler --pre`

Although I like to update my tools, I usually don't want to install prerelease versions.
Please add an option to limit the update notice to stable releases. (or better yet, make that the default and add an option to include prereleases)

The update notification has been disabled by default in the next release. See #6031


text:
Bundler 1.17.0 fails if no path set

Trying to install my Gemfile with bundler 1.17.0 always fails, but downgrading bundler to 1.16.1 succeeds.
Also the recommended resolution is not in proper format:
gem install CFPropertyList -v '3.0.0' --source 'https://rubygems.org/' does not work, but   gem install CFPropertyList --source 'https://rubygems.org/' -v '3.0.0'
does.
Gemfile
source "https://rubygems.org"
gem 'fastlane', '~> 2.104.0'
gem 'earlgrey', '~> 0.1.5'
gem 'cocoapods', '~> 1.5.3'
gem 'versionomy', '~> 0.5.0'
Output
Brices-MacBook-Pro% bundle install
Fetching gem metadata from https://rubygems.org/.........
Fetching gem metadata from https://rubygems.org/.
Resolving dependencies...
Using CFPropertyList 3.0.0
ArgumentError: comparison of Pathname with String failed
An error occurred while installing CFPropertyList (3.0.0), and Bundler cannot continue.
Make sure that gem install CFPropertyList -v '3.0.0' --source 'https://rubygems.org/' succeeds before bundling.
In Gemfile:
cocoapods was resolved to 1.5.3, which depends on
xcodeproj was resolved to 1.7.0, which depends on
CFPropertyList

thanks for the speedy fix!


text:
Ensure git is executed inside the gemspec dir

What was the end-user problem that led to this PR?
Executables from bundled gems weren't available.
Gem::Exception: can't find executable <EXEC-FILENAME> for gem <GEM-NAME>
  /Users/elia/.rvm/rubies/ruby-2.3.4/lib/ruby/site_ruby/2.3.0/bundler/rubygems_integration.rb:458:in `block in replace_bin_path'
  /Users/elia/.rvm/rubies/ruby-2.3.4/lib/ruby/site_ruby/2.3.0/bundler/rubygems_integration.rb:478:in `block in replace_bin_path'
…

What was your diagnosis of the problem?
When a Gemfile was pointing to a local gem using git to list its files the git command
was executed from within the wrong dir.
What is your fix for the problem, implemented in this PR?
Initially I added -C #{__dir__} to the git ls-files -z command.
Why did you choose this fix out of the possible options?
Realized -C wasn't safe and opted for stuff already available in the corelib, i.e. Dir.chrid instead of, say, escaping with shellwords.

I know the line is long-ish, happy to fix it in the way you want

@bundlerbot r+

authors: colby-swandale elia


text:
🛑 doubledouble is down

In e18b763, doubledouble (https://doubledouble.top/) was down:

HTTP code: 0
Response time: 0 ms

Resolved: doubledouble is back up in 7f8fd6f after 42 minutes.


text:
🛑 doubledouble is down

In 44715c8, doubledouble (https://doubledouble.top/) was down:

HTTP code: 502
Response time: 589 ms

Resolved: doubledouble is back up in 3bda13f after 5 minutes.


text:
brew cu : "Error: private method load' called for Hbc:Module" and exits 1 after brew update`

Hi,
After a brew upate called by brew cu, I get this :
==> Finding outdated apps
Error: private method `load' called for Hbc:Module
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/extend/hbc.rb:45:in `rescue in load_cask'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/extend/hbc.rb:42:in `load_cask'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/extend/hbc.rb:14:in `block in installed_apps'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/extend/hbc.rb:11:in `map'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/extend/hbc.rb:11:in `installed_apps'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/bcu.rb:66:in `find_outdated_apps'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/bcu.rb:24:in `process'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/cmd/brew-cu.rb:34:in `<top (required)>'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/Homebrew/Library/Homebrew/utils.rb:18:in `require?'
/usr/local/Homebrew/Library/Homebrew/brew.rb:93:in `<main>'

$ echo $?
1
$ brew --version
Homebrew 1.7.1-20-ga1f0ff4
Homebrew/homebrew-core (git revision 837545; last commit 2018-07-25)
$ brew cask --version
Homebrew-Cask 1.7.1-20-ga1f0ff4
Homebrew/homebrew-cask (git revision 43373; last commit 2018-07-25)

I thought issue #102 was related but the brew cask outdated command proposed there is broken on my system because of java7 so I cannot go further on this track.
Then I tried the following commands below but it did not solve the pb. :
$ brew untap buo/cask-upgrade
Untapping buo/cask-upgrade...
Untapped 2 commands (78 files, 78KB).
$ brew cu
Error: Unknown command: cu
$ brew tap buo/cask-upgrade
==> Tapping buo/cask-upgrade
Cloning into '/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade'...
remote: Counting objects: 21, done.
remote: Compressing objects: 100% (18/18), done.
remote: Total 21 (delta 0), reused 12 (delta 0), pack-reused 0
Unpacking objects: 100% (21/21), done.
Tapped 2 commands (57 files, 49KB).
$ brew cu
==> Options
Include auto-update (-a): false
Include latest (-f): false
==> Updating Homebrew
Already up-to-date.
==> Finding outdated apps
Error: private method `load' called for Hbc:Module
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/extend/hbc.rb:45:in `rescue in load_cask'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/extend/hbc.rb:42:in `load_cask'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/extend/hbc.rb:14:in `block in installed_apps'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/extend/hbc.rb:11:in `map'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/extend/hbc.rb:11:in `installed_apps'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/bcu.rb:66:in `find_outdated_apps'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/lib/bcu.rb:24:in `process'
/usr/local/Homebrew/Library/Taps/buo/homebrew-cask-upgrade/cmd/brew-cu.rb:34:in `<top (required)>'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.3.7/lib/ruby/2.3.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/Homebrew/Library/Homebrew/utils.rb:18:in `require?'
/usr/local/Homebrew/Library/Homebrew/brew.rb:93:in `<main>'
$ echo $?
1

Hey @sebma , please run brew cask outdated to figure out, which casks are not maintained any more and remove them. After that it should work.

Also you can take a look into this issue where this was as well discussed: https://github.com/buo/homebrew-cask-upgrade/issues/100

@ondrejfuhrer
$ brew cask outdated
Error: undefined method `undent' for #<String:0x000000010425a058>
Follow the instructions here:
  https://github.com/Homebrew/homebrew-cask#reporting-bugs
/usr/local/Caskroom/java7/.metadata/1.7.0_80/20170503124403.890/Casks/java7.rb:72:in `block in load'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cask.rb:36:in `instance_eval'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cask.rb:36:in `initialize'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cask_loader.rb:31:in `new'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cask_loader.rb:31:in `cask'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cask_loader.rb:67:in `cask'
/usr/local/Homebrew/Library/Homebrew/compat/hbc/cask_loader.rb:15:in `cask'
/usr/local/Caskroom/java7/.metadata/1.7.0_80/20170503124403.890/Casks/java7.rb:1:in `load'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cask_loader.rb:57:in `instance_eval'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cask_loader.rb:57:in `load'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/caskroom.rb:34:in `block in casks'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/caskroom.rb:28:in `map'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/caskroom.rb:28:in `casks'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/outdated.rb:13:in `block in run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/abstract_command.rb:47:in `casks'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/outdated.rb:13:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/abstract_command.rb:33:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:93:in `run_command'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:159:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:124:in `run'
/usr/local/Homebrew/Library/Homebrew/cmd/cask.rb:7:in `cask'
/usr/local/Homebrew/Library/Homebrew/brew.rb:87:in `<main>'

@sebma As suggested in all the related issues, remove the cask. In your case java7
rm -rf /usr/local/Caskroom/java7

Upstream issue: https://github.com/Homebrew/homebrew-cask/issues/49716

authors: ondrejfuhrer sebma yurikoles

repo: buo/homebrew-cask-upgrade


text:
Setup code coverage

https://docs.codeclimate.com/docs/setting-up-test-coverage

I can do this - do I need codeclimate access? when I log in via github I get an account from a diff company

@zfoster I'm not sure. I got in and tried to add you, but can't see anywhere to do that.

authors: southpolesteve zfoster

repo: bustlelabs/shep


text:
New busy not working in Internet Explorer

Expected behavior
New busy should work in Internet Explorer.
Actual behavior
The page is blank. No content appears.
How to reproduce

Go to new busy in Internet Explorer

Browser: Internet Explorer 11
Operating system: Windows 10

Wanted to comment - I started looking into this. The console has errors about Object does not have property assign.
This is somewhat expected since, in the ES6 compatibility table, Object.assign is not supported by IE11.
From what I've looked into so far, my guess is that it might have to do with us not loading babel-polyfill in webpack. But I haven't investigated enough yet to verify.
I'm currently working on another issue so if anyone else feels like taking this on in the meantime, hopefully these notes will help. If not, I'll come back to it.

I tried using the ff. in webpack-dev-server.js
  entry: {
    main: ['babel-polyfill', path.resolve(baseDir, './src/index.js')]
  },

it loaded in IE11, however the ff. error still occurs:
SCRIPT65535: Invalid calling object

authors: eastmaels espoem ryanbaer

repo: busyorg/busy


text:
Add Korbit

Would like to see korbit.co.kr add, understand its KWR and not USD, but there is a lot of opportunities. Any reason a KWR to USD lookup could not be done in real-time?

Blackbird is not designed to handle other currencies than USD. Looking up the USD/KRW rate is not enough: you need to trade your USD to KRW first.
On a BTC/USD arbitrage opportunity where Korbit is one of the exchanges, you would need to trade:

arbitrage entry: USD → KRW → BTC
arbitrage exit: BTC → KRW → USD

Plus, you need to hedge against the USD/KRW risk.

authors: butor tonymorella

repo: butor/blackbird


text:
Yoda rule is not available despite docs

The original eslint yoda rule both allows and disallows yoda conditionals.
Recently @JayAndCatchFire updated the doc (#348) to state that the rule is provided natively by TSLint's binary-expression-operand-order, however this rule can only disallow yoda - it's not configurable.
I'd like to have a go at implementing a TSLint rule (not sure where to start, but worth a go) - we use yoda in PHP so I'd like to enforce it in TS. But can you advise whether I should create a new rule here, named yoda, or whether I should submit a PR to palantir extending the binary-expression-operand-order?
Cheers

I would ask the guys at palantir if they would be willing to add that functionality (or if they accept a PR to add it). If they say no then ter-yoda is welcomed in this project.

authors: antonyoneill jmlopez-rod

repo: buzinas/tslint-eslint-rules


text:
🛑 Sai Gardens Temple Side is down

In 9346683, Sai Gardens Temple Side (https://cloud.tymly.in/status/1074) was down:

HTTP code: 521
Response time: 206 ms

Resolved: Sai Gardens Temple Side is back up in b8d86d4.

repo: bvenkysubbu/tymlymonitor


text:
🛑 Dasta Concerto Entrance is down

In a0f3719, Dasta Concerto Entrance (https://cloud.tymly.in/status/1137) was down:

HTTP code: 521
Response time: 20230 ms

Resolved: Dasta Concerto Entrance is back up in 66e4ead.


text:
🛑 Madhuban Brindavan B Block is down

In 2e7422b, Madhuban Brindavan B Block (https://cloud.tymly.in/status/1136) was down:

HTTP code: 521
Response time: 230 ms

Resolved: Madhuban Brindavan B Block is back up in 1dc3f0e.


text:
🛑 Prestige Lakeside Habitat Tower 13 is down

In d16646d, Prestige Lakeside Habitat Tower 13 (https://cloud.tymly.in/status/1100) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Prestige Lakeside Habitat Tower 13 is back up in 5602494.


text:
🛑 PSR Aster 1 is down

In 5232b39, PSR Aster 1 (https://cloud.tymly.in/status/1059) was down:

HTTP code: 521
Response time: 20241 ms

Resolved: PSR Aster 1 is back up in ba8c362.


text:
🛑 PSR Aster 1 is down

In 397c9d9, PSR Aster 1 (https://cloud.tymly.in/status/1059) was down:

HTTP code: 521
Response time: 20216 ms

Resolved: PSR Aster 1 is back up in d3542ab.


text:
🛑 Nitesh Flushing Meadows Block D is down

In 115d701, Nitesh Flushing Meadows Block D (https://cloud.tymly.in/status/1049) was down:

HTTP code: 521
Response time: 20233 ms

Resolved: Nitesh Flushing Meadows Block D is back up in 5ccc38c.


text:
🛑 Madhuban Brindavan A Block is down

In 93c700d, Madhuban Brindavan A Block (https://cloud.tymly.in/status/1135) was down:

HTTP code: 521
Response time: 228 ms

Resolved: Madhuban Brindavan A Block is back up in c457675.


text:
🛑 Mahaveer Varna A4 is down

In c22e60b, Mahaveer Varna A4 (https://cloud.tymly.in/status/1084) was down:

HTTP code: 521
Response time: 224 ms

Resolved: Mahaveer Varna A4 is back up in 8de6c2c.


text:
🛑 Trifecta Esplanade is down

In 473f8b4, Trifecta Esplanade (https://cloud.tymly.in/status/1003) was down:

HTTP code: 521
Response time: 21062 ms

Resolved: Trifecta Esplanade is back up in 943ce58.


text:
🛑 Madhuban Brindavan 4 Block is down

In 0040f65, Madhuban Brindavan 4 Block (https://cloud.tymly.in/status/1183) was down:

HTTP code: 521
Response time: 237 ms

Resolved: Madhuban Brindavan 4 Block is back up in e145908.


text:
🛑 PSR Aster 1 is down

In bbd217d, PSR Aster 1 (https://cloud.tymly.in/status/1059) was down:

HTTP code: 521
Response time: 20231 ms

Resolved: PSR Aster 1 is back up in b1a597d.


text:
🛑 SMR Vinay Cascade B Block is down

In 8a84dcb, SMR Vinay Cascade B Block (https://cloud.tymly.in/status/1093) was down:

HTTP code: 502
Response time: 6856 ms

Resolved: SMR Vinay Cascade B Block is back up in 3f798a2.


text:
🛑 Trifecta Esplanade D Block is down

In 6d12bd7, Trifecta Esplanade D Block (https://cloud.tymly.in/status/1156) was down:

HTTP code: 521
Response time: 20233 ms

Resolved: Trifecta Esplanade D Block is back up in 31a140a.


text:
🛑 Urban Greens is down

In 3355e46, Urban Greens (https://cloud.tymly.in/status/1046) was down:

HTTP code: 521
Response time: 20234 ms

Resolved: Urban Greens is back up in c30a0cb.


text:
🛑 Madhuban Brindavan A Block is down

In d279fdd, Madhuban Brindavan A Block (https://cloud.tymly.in/status/1135) was down:

HTTP code: 521
Response time: 229 ms

Resolved: Madhuban Brindavan A Block is back up in b272f63.


text:
🛑 Trifecta Esplanade M Block is down

In ba8e8a1, Trifecta Esplanade M Block (https://cloud.tymly.in/status/1003) was down:

HTTP code: 521
Response time: 230 ms

Resolved: Trifecta Esplanade M Block is back up in d51339f.


text:
🛑 Trifecta Esplanade C Block is down

In bb711ae, Trifecta Esplanade C Block (https://cloud.tymly.in/status/1155) was down:

HTTP code: 521
Response time: 20236 ms

Resolved: Trifecta Esplanade C Block is back up in 51ab2b2.


text:
🛑 Sterling Shalom F Block is down

In 0eb31fe, Sterling Shalom F Block (https://cloud.tymly.in/status/1013) was down:

HTTP code: 521
Response time: 20237 ms

Resolved: Sterling Shalom F Block is back up in 2eedbe8.


text:
🛑 Amrutha Sarovar is down

In 4a36c60, Amrutha Sarovar (https://cloud.tymly.in/status/1016) was down:

HTTP code: 521
Response time: 231 ms

Resolved: Amrutha Sarovar is back up in bbc5de6.


text:
🛑 VBHC Serene Town D Block is down

In 3f77c6c, VBHC Serene Town D Block (https://cloud.tymly.in/status/1131) was down:

HTTP code: 521
Response time: 20248 ms

Resolved: VBHC Serene Town D Block is back up in 37de907.


text:
🛑 Trifecta Esplanade Multipurpose Hall is down

In c4f3ba8, Trifecta Esplanade Multipurpose Hall (https://cloud.tymly.in/status/1169) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Trifecta Esplanade Multipurpose Hall is back up in 8957448.


text:
🛑 Dasta Concerto Basement 2 is down

In 4ad0b3c, Dasta Concerto Basement 2 (https://cloud.tymly.in/status/1188) was down:

HTTP code: 521
Response time: 20235 ms

Resolved: Dasta Concerto Basement 2 is back up in e355069.


text:
🛑 SMR Vinay Cascade B Block is down

In 1630628, SMR Vinay Cascade B Block (https://cloud.tymly.in/status/1093) was down:

HTTP code: 521
Response time: 20231 ms

Resolved: SMR Vinay Cascade B Block is back up in 03c3ef4.


text:
🛑 Trifecta Esplanade N Block is down

In b0338fa, Trifecta Esplanade N Block (https://cloud.tymly.in/status/1165) was down:

HTTP code: 521
Response time: 242 ms

Resolved: Trifecta Esplanade N Block is back up in 859e7e2.


text:
🛑 Trifecta Esplanade L Block is down

In 993ed21, Trifecta Esplanade L Block (https://cloud.tymly.in/status/1164) was down:

HTTP code: 521
Response time: 269 ms

Resolved: Trifecta Esplanade L Block is back up in 2ac8889.


text:
🛑 SMD Altezz Block B is down

In 698f793, SMD Altezz Block B (https://cloud.tymly.in/status/1176) was down:

HTTP code: 521
Response time: 20251 ms

Resolved: SMD Altezz Block B is back up in 442e4cf after 21 minutes.


text:
🛑 VBHC Serene Town C Block is down

In 90cdee8, VBHC Serene Town C Block (https://cloud.tymly.in/status/1132) was down:

HTTP code: 521
Response time: 20227 ms

Resolved: VBHC Serene Town C Block is back up in c295f28.


text:
🛑 White Breeze 1 is down

In 73f6356, White Breeze 1 (https://cloud.tymly.in/status/1096) was down:

HTTP code: 521
Response time: 219 ms

Resolved: White Breeze 1 is back up in 10abca9.


text:
🛑 SMR Vinay Cascade A Block is down

In 7861ded, SMR Vinay Cascade A Block (https://cloud.tymly.in/status/1094) was down:

HTTP code: 521
Response time: 20236 ms

Resolved: SMR Vinay Cascade A Block is back up in 4044621.


text:
ModuleNotFoundError: No module named 'ConfigArgparse' on MacOS Big Sur

See next entry

Sorry, my mistake. I didn't see the configargparse.py file. I'm assuming that is correct. So the actual problem is this.
python3 -c "import ConfigArgparse"
Traceback (most recent call last):
File "", line 1, in
ModuleNotFoundError: No module named 'ConfigArgparse'
Yet pip3 list shows:
Package        Version

certifi        2020.12.5
chardet        4.0.0
ConfigArgParse 1.2.3
idna           2.10
pip            20.3.3
requests       2.25.1
setuptools     41.2.0
six            1.15.0
urllib3        1.26.2
wheel          0.33.1

Ok, if I just put configargparse.py in the same dir as I run the command it works and if I go into /Users/david/Library/Python/3.8/lib/python/site-packages and run the command there, it also works.

This seems to me like a problem of more than one python version installed, or PYTHONPATH set incorrectly.


text:
The 'nice' initial camera position is breaking

The 'nice' initial camera seems to be working for the 'Damaged Helmet' model perfectly but seems to be breaking for other models such as the one attached to this issue .
The attached model exits with a panic . I've also attached the panic error message .
GLTF File : https://transfer.sh/mWi4F/lighter.zip
thread 'main' panicked at 'called Result::unwrap()on anErrvalue: VBoxCutFailed', /checkout/src/libcore/result.rs:906:4 stack backtrace:    0: std::sys::imp::backtrace::tracing::imp::unwind_backtrace              at /checkout/src/libstd/sys/unix/backtrace/tracing/gcc_s.rs:49    1: std::sys_common::backtrace::_print              at /checkout/src/libstd/sys_common/backtrace.rs:68    2: std::panicking::default_hook::{{closure}}              at /checkout/src/libstd/sys_common/backtrace.rs:57              at /checkout/src/libstd/panicking.rs:381    3: std::panicking::default_hook              at /checkout/src/libstd/panicking.rs:397    4: std::panicking::rust_panic_with_hook              at /checkout/src/libstd/panicking.rs:577    5: std::panicking::begin_panic              at /checkout/src/libstd/panicking.rs:538    6: std::panicking::begin_panic_fmt              at /checkout/src/libstd/panicking.rs:522    7: rust_begin_unwind              at /checkout/src/libstd/panicking.rs:498    8: core::panicking::panic_fmt              at /checkout/src/libcore/panicking.rs:71    9: core::result::unwrap_failed              at /checkout/src/libcore/macros.rs:23   10: <core::result::Result<T, E>>::unwrap              at /checkout/src/libcore/result.rs:772   11: gltf_viewer::viewer::GltfViewer::screenshot              at src/viewer.rs:326   12: gltf_viewer::viewer::GltfViewer::multiscreenshot              at src/viewer.rs:345   13: gltf_viewer::main              at src/main.rs:108   14: __rust_maybe_catch_panic              at /checkout/src/libpanic_unwind/lib.rs:101   15: std::rt::lang_start              at /checkout/src/libstd/panicking.rs:459              at /checkout/src/libstd/panic.rs:365              at /checkout/src/libstd/rt.rs:58   16: main   17: __libc_start_main   18: _start

I can't reproduce it - the screenshots look bad, but there's no panic. I've used this
CARGO_INCREMENTAL=1 cargo run -- target/lighter/scene.gltf -vv -s target/lighter.png -c 3 (macOS)
What line is it failing on? The line numbers in your message don't seem to match master.

I'm sorry , seems like it's failing on my branch , sorry about the confusion. But is there someway the screenshots could be made proper ?

Hmm, it renders much better on gltf-viewer.donmccurdy.com, so it shouldn't be too hard to fix I hope (the camera positioning is based on Don McCurdy's code).

I haven't looked into fixing the auto camera positioning yet, but there are now some CLI parameters for the camera: #20.

This should fix it:  #21. The lighter looks much better, so do (almost) all sample models (-> load_all_samples.sh)

authors: bwasty siddhartpai

repo: bwasty/gltf-viewer

license: unlicense


text:
implement interaction request signing verification

i had previously written a small lib to do this: bsdlp/discord-interactions-go, and this is basically copypasta from there.
https://discord.com/developers/docs/interactions/slash-commands#security-and-authorization

Hi! This library hasn't traditionally featured any type of HTTP server functionality, but given the new interactions feature I think that this might be a good addition to consider! A few things I'm unsure about:

Do we really need a third-party dependency on github.com/kevinburke/nacl/sign? The check can be completed by crypto/ed25519 outright, and I'd prefer not adding additional third-party dependencies (especially crypto ones!) if it's not necessary.
Is there a particular reason that you've vendored all dependencies in this change? We haven't previously, and while I'm not inherently against it, I think that it's a bit out of the scope of this change.

you're 100% right. i've removed the external lib dependency. thanks!

build is failing due to crypto/ed25519 not existing in go stdlib before 1.13. imo those versions can be dropped, go release policy says the currently supported releases are 1.14 and 1.15.

Why do you touch the request body? Seems unnecessary

Why do you touch the request body? Seems unnecessary

Why do you touch the request body? Seems unnecessary

Looks like we need to read the request body to validate the signature, so a copy of the original io.Reader body is created to replace the request body
after it's read from for the signature check before we return. Other functions later that use the same request can then read the body in normally.

Why do you touch the request body? Seems unnecessary

Looks like we need to read the request body to validate the signature, so a copy of the original io.Reader body is created to replace the request body
after it's read from for the signature check before we return. Other functions later that use the same request can then read the body in normally.

Thank you for the addition! This should definitely be useful for the adoption of webhook interactions 😃

Thank you for the addition! This should definitely be useful for the adoption of webhook interactions 😃

thanks for your work on this lib!

thanks for your work on this lib!

authors: CarsonHoffman Jleagle bsdlp ewohltman

repo: bwmarrin/discordgo


text:
New devices cant be found - but old ones updating

I cant seem to get alexa to find new UDP devices im adding into HABRIDGE.  If I delete an existing device from alexa app, it picks it up again through discovery and re adds it in.
But adding in new devices Alexa just keeps saying no new devices found.
Ive updated HaBridge to 5.4.1RC1 and this hasnt fixed it.
Also weirdly my new devices start with 100, or 101, or 102 - which is odd as I dont have 100 devices
Any ideas?

Fixed it - updated to 5.4.1RC! - enabled Oct 9 in settings, renumbered devices and now its working,

repo: bwssytems/ha-bridge


text:
Template/ISO Agreement appears with the scroll at the end of the page

Steps to reproduce:

Open VM creation
Click on Installation source
Select Template or ISO with tag: "csui.template.agreement"
Click on "Create" VM

Actual result
Agreement dialog appears with the scroll at the end of the page
Expected result
Agreement dialog appears with the scroll at the start of the page
Environment
Browser:
- [ ] Chrome version XX
- [ ] Firefox version XX
- [ ] Safari version XX
- [ ] Opera version XX
- [ ] IE version XX
- [ ] Edge version XX

Others:

Connected feature ID
vm_creation_agreement
Screenshots
Initial form state

Proposal:

PO approved these changes

Test on:  1186
Test:
vm_creation_agreement

Tested on 1186

authors: HeyRoach rennervo tamazlykar

repo: bwsw/cloudstack-ui