Can not assert via bluetooth on iOS or Android with G290 Bobcat

Hi there, I've been attempting to get a G290 bobcat setup, have been able to successfully flash with https://github.com/NebraLtd/helium-bobcat-rk3566/releases/tag/v1.1.1-helium-bobcat-rk3566-2023-08-16-OpenFleet (v1.1) and log into the web interface, showing bluetooth on, and can see it via the nebra and helium applications on iOS (tried iphone and ipad) but it fails to complete - get an error saying "Device [ID] was disconnected" each time and never finishes, happens each time.  Also reset and reflashed a few times.  On various Android devices they simply do not discover the device which is strange (stuck on scanning for hotspots page), did hear that it should work asserting via these.  Attempting via Helium app on iOS says the device needs updating but never works (completely different version).  Showing "Awaiting Location Assertion" under the Helium status tab as to be expected and will not attach to your dashboard.
Bobcat RK3566 Hotspot (2GB RAM)
Nebra Firmware: v1.1.1 (ced1242) [latest at time of posting]
Loader: rk356x_spl_loader_ddr1056_v1.06.110.bin
helium-bobcat-rk3566-2023-08-16.img (as link above)
Android devices attempted with: Samsung Galaxy S6, Sony G83141 (Sony Xperia XZ Premium) and newer Google Pixel 6.
iOS: iPhone XS Max, Ipad Mini 5.
Is there anyhting else I can try as can not use the device until this is done apparently?  The device does show a Helium hotspot name and address which was same when I flashed again on the nebra web interface.
Cheers!
Just an update, I've also applied the previous firmwares, v1.1.x appeared to boot on the device but same issue asserting via bluetooth.

Helium app will not work. And on android you need to have precise location permissions enabled.

We are aware of BT issues with these bobcats (not only G290 btw) But as mentioned try above as to what Shawaj suggested.


Right Click Harvesting

Wanna have the right click harvesting feature. A feature with which you can harvest fully grown crops with just a right click and replant them automatically.

Hey, cool mod! Nice to see some new modders. If you need help with this you can look at my src code here. This crop has right-click harvesting with instant planting again.
https://github.com/EwyBoy/Cultivated-Tech/blob/master/src/main/java/com/ewyboy/cultivatedtech/common/blocks/crops/BlockCropScorch.java

thank you! I will look at that and maybe use a few things if it's ok.

Yeah, my code is open source for a reason. So other people can use it and hopefully learn something.

ok, I'll do it in within the next days, thank you for open source :D


No easy way to restart ICE

At peerconnection.c:406, it says:
	case options != nil:
		return SessionDescription{}, fmt.Errorf("TODO handle options")

I don't see any other way to restart ICE on an existing PC.  (I'm currently working around the issue by tearing down the connection and creating a new one, but that has other problems, such as requiring a keyframe even if the interruption was short-lived.)

Yea we really need to do this.
https://github.com/pion/ice/issues/190 was filed, but I never made any progress on it. I really don't think it will be that difficult either.
Will keep you updated, but my guess is ~4 days of work so I think I can make this happen within the month!


Exploring Unnecessary Conditionals: Autosuggest

What is the context of this PR?
#3013 As the ticket checked the following actions
Actions

List params not present in markdown file.
Establish if these are legacy code or else coming from elsewhere - double bracket to see if the param has a value.
Remove if not necessary.
Ensure testing remains intact / update as required.

What has changed
Added ariaLimitedResults param in _macro-options.md
How to review this PR
Check that params mentioned in examples are present in readme
Checklist
This needs to be completed by the person raising the PR.

[x] I have selected the correct Assignee
[x] I have linked the correct Issue

Can you update the description to say what changes have been made? Its difficult to see what params have been added/removed. ariaLimitedResults I think is the only one youve added?

Can you update the description to say what changes have been made? Its difficult to see what params have been added/removed. ariaLimitedResults I think is the only one youve added?

Yes, that's the only one


Manage all nugets for solution.sln

It would be nicer if had an option to right-click on .sln file and manage nugets

Closing as duplicate of #15


bump metronome on dcos 1.12 to 0.5.0

High-level description
What features does this change enable? What bugs does this change fix?
Corresponding DC/OS tickets (obligatory)
These DC/OS JIRA ticket(s) must be updated (ideally closed) in the moment this PR lands:

DCOS_OSS-3897 Upgrade Metronome to 0.5.0 on DCOS 1.12.

Related tickets (optional)
Other tickets related to this change:

METRONOME-246 Support Secrets.
METRONOME-238 Migrate from joda time to Java time.
METRONOME-218 Better handling of errors with zk storage.
Large move to the latest Marathon 1.6 as a library

Checklist for all PRs

[x] Added a comprehensible changelog entry to CHANGES.md or explain why this is not a user-facing change:
[x] Included a test which will fail if code is reverted but test is not. If there is no test please explain here:
[x] Read the DC/OS contributing guidelines
[x] Followed relevant code rules Rules for Packages and Systemd

Checklist for component/package updates:
If you are changing components or packages in DC/OS (e.g. you are bumping the sha or ref of anything underneath packages), then in addition to the above please also include:

[x] Change log from the last version integrated (this should be a link to commits for easy verification and review): diff
[x] Test Results: CI/Test
[x] Code Coverage (if available): N/A

@mesosphere-mergebot bump-ee

@mesosphere-mergebot Label Ready for Review

rebased

@mesosphere-mergebot bump-ee

The version in master is already higher than this - https://github.com/dcos/dcos/commit/98351a9b8f126df5e611a5991214a3c45a806ded
Discarding this PR.


Firebase Return differently when comes to map

Firstly ,
My data   :
data :
    10:150
    20:250

return data:{10: 150, 20: 250},

Secondly,
when data stored likes  :
data :
    1:150
    2:250

return data:[null, 150,  250],
``

Closing due to lack of detail and staleness. Please provide some more details about what plugin this is along with a reproduction case.


Merge pull request #21 from wilsongp/development

Updated npm description

Coverage remained the same at 100.0% when pulling aa550e1ce7bbea77cc46dafc3ba7938158db764b on master into 897d4a8ef3c310c1c27521578c22c17e027b49ed on development.


Error when uses transfer_learning.train

Thanks for the interesting project! I am trying to apply the project on a smaller chess board. When performing model fine tuning, I encountered the following error, for which I have not found a way around. Could you please help? The error message is below:
"
jetson@yahboom:~/chesscog$ python3.9 -m chesscog.transfer_learning.train
[2023-04-19 14:29:52,990] {train.py:43} INFO - Starting training for occupancy_classifier
[2023-04-19 14:29:53,164] {train.py:55} INFO - Starting training in /home/jetson/chesscog/runs/transfer_learning/occupancy_classifier
[2023-04-19 14:29:53,165] {train.py:61} WARNING - The folder /home/jetson/chesscog/runs/transfer_learning/occupancy_classifier already exists and will be overwritten by this run
Traceback (most recent call last):
File "/usr/lib/python3.9/runpy.py", line 197, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/usr/lib/python3.9/runpy.py", line 87, in _run_code
exec(code, run_globals)
File "/home/jetson/chesscog/chesscog/transfer_learning/train.py", line 44, in
_train_model(model_type)
File "/home/jetson/chesscog/chesscog/transfer_learning/train.py", line 35, in _train_model
train_model(cfg, run_dir, model, is_inception,
File "/home/jetson/chesscog/chesscog/core/training/train.py", line 80, in train_model
dataset = build_dataset(cfg, Datasets.TRAIN)
File "/home/jetson/chesscog/chesscog/core/dataset/dataset.py", line 70, in build_dataset
dataset = torchvision.datasets.ImageFolder(root=URI(cfg.DATASET.PATH) / mode.value,
File "/home/jetson/.local/lib/python3.9/site-packages/torchvision/datasets/folder.py", line 310, in init
super(ImageFolder, self).init(root, loader, IMG_EXTENSIONS if is_valid_file is None else None,
File "/home/jetson/.local/lib/python3.9/site-packages/torchvision/datasets/folder.py", line 145, in init
classes, class_to_idx = self.find_classes(self.root)
File "/home/jetson/.local/lib/python3.9/site-packages/torchvision/datasets/folder.py", line 221, in find_classes
return find_classes(directory)
File "/home/jetson/.local/lib/python3.9/site-packages/torchvision/datasets/folder.py", line 42, in find_classes
raise FileNotFoundError(f"Couldn't find any class folder in {directory}.")
FileNotFoundError: Couldn't find any class folder in /home/jetson/chess_data/transfer_learning/occupancy/train.
"

Try running python -m chesscog.occupancy_classifier.create_dataset and python -m chesscog.piece_classifier.create_dataset before the training. More detailed instructions can be found in section C.2.3.2 here.

Yes. It unblocked the training. Thanks for the quick response!


Downlinks are only transmitted after a second uplink

Is this a bug or a feature request?
Feature
What did you expect?
A node I use can request a answer from an application running on a server. This answer has to be transmitted in either RX1 or RX2 as depends on the time. The answer takes up to 100ms to generate and is transmitted to the lora application server using the MQTT "application/+/node/+/tx" topic. I expect the answer to be transmitted in the next RX1 or RX2, depending on the settings of the node.
What happened?
The answer is added to the downlink queue and is transmitted only after the next packet is received by the network server. This causes the answer to be outdated and useless.
What version are your using?
loraserver version 0.19.0
How can your issue be reproduced?
Write an application that answers uplink packets with the frame count of the uplink packet. Any downlink will contain the frame count of the uplink of one packet earlier.
Could you share your log output?
MQTT output:
gateway/+/rx {"rxInfo":{"mac":"*","time":"0001-01-01T00:00:00Z","timestamp":3309996588,"frequency":868500000,"channel":2,"rfChain":1,"crcStatus":1,"codeRate":"4/5","rssi":-79,"loRaSNR":8.5,"size":32,"dataRate":{"modulation":"LORA","spreadFactor":9,"bandwidth":125}},"phyPayload":"QDKH1AaAAgABPJ8RvZdKYyd1VkIIqP+pQJOZHk5Yw9Q="}
application/17/node/aaaaaaaaaaaaaaaa/rx {"applicationID":"17","applicationName":"*","nodeName":"*","devEUI":"aaaaaaaaaaaaaaaa","rxInfo":[{"mac":"*","rssi":-79,"loRaSNR":8.5,"name":"*","latitude":0,"longitude":0,"altitude":0}],"txInfo":{"frequency":868500000,"dataRate":{"modulation":"LORA","bandwidth":125,"spreadFactor":9},"adr":true,"codeRate":"4/5"},"fCnt":2,"fPort":1,"data":"*"}
application/17/node/aaaaaaaaaaaaaaaa/tx {"confirmed": false, "data": "*", "fPort": 6, "reference": "aaaaaaaaaaaaaaaa_1511307081.18"}
gateway/+/rx {"rxInfo":{"mac":"*","time":"0001-01-01T00:00:00Z","timestamp":3339995316,"frequency":868100000,"channel":0,"rfChain":1,"crcStatus":1,"codeRate":"4/5","rssi":-81,"loRaSNR":12,"size":32,"dataRate":{"modulation":"LORA","spreadFactor":9,"bandwidth":125}},"phyPayload":"QDKH1AaAAwABLlWyCu4vAHFRvcuiuXVfhKPcdIUnHuM="}
application/17/node/aaaaaaaaaaaaaaaa/rx {"applicationID":"17","applicationName":"*","nodeName":"node1","devEUI":"aaaaaaaaaaaaaaaa","rxInfo":[{"mac":"*","rssi":-81,"loRaSNR":12,"name":"*","latitude":0,"longitude":0,"altitude":0}],"txInfo":{"frequency":868100000,"dataRate":{"modulation":"LORA","bandwidth":125,"spreadFactor":9},"adr":true,"codeRate":"4/5"},"fCnt":3,"fPort":1,"data":"*"}
gateway/+/tx {"txInfo":{"mac":"*","immediately":false,"timestamp":3341995316,"frequency":869525000,"power":14,"dataRate":{"modulation":"LORA","spreadFactor":12,"bandwidth":125},"codeRate":"4/5","iPol":null},"phyPayload":"YDKH1AYAAAAGayXpe6lY3zgeLhc="}

The LoRa app-server:
Nov 21 21:12:31 * lora-app-server[14421]: time="2017-11-21T21:12:31+01:00" level=info msg="handler/mqtt: publishing data-up payload" topic="application/17/node/aaaaaaaaaaaaaaaa/rx"
Nov 21 21:12:31 * lora-app-server[14421]: time="2017-11-21T21:12:31+01:00" level=info msg="data-down item requested by network-server, but queue is empty" dev_eui=aaaaaaaaaaaaaaaa
Nov 21 21:12:31 * lora-app-server[14421]: time="2017-11-21T21:12:31+01:00" level=info msg="handler/mqtt: data-down payload received" topic="application/17/node/aaaaaaaaaaaaaaaa/tx"
Nov 21 21:12:31 * lora-app-server[14421]: time="2017-11-21T21:12:31+01:00" level=info msg="downlink queue item enqueued" dev_eui=aaaaaaaaaaaaaaaa id=34
Nov 21 21:13:01 * lora-app-server[14421]: time="2017-11-21T21:13:01+01:00" level=info msg="handler/mqtt: publishing data-up payload" topic="application/17/node/aaaaaaaaaaaaaaaa/rx"
Nov 21 21:13:01 * lora-app-server[14421]: time="2017-11-21T21:13:01+01:00" level=info msg="downlink queue item deleted" id=34
Nov 21 21:13:01 * lora-app-server[14421]: time="2017-11-21T21:13:01+01:00" level=info msg="data-down item requested by network-server" confirmed=false dev_eui=aaaaaaaaaaaaaaaa fcnt=0 id=34

It appears that the network server queries the downlink queue of the application server ASAP. As the application takes up to 100 ms to generate the answer, the answer is transmitted to the application server after the network server issued the downlink queue.
I think that the downlink queue should be queried just before the deadline for RX1/RX2 and not ASAP. This allows any application to generate an answer to be transmitted to the node within the same "cycle". On the other hand, it is important that any transmission commands to the gateway are issued before RX1/RX2 closes. This results in some deadline before which any answer from the application must be transmitted to the application server. The deadline for RX1/RX2 depends on the latency of the gateway, the internal processing time of the gateway, etc. A dynamic algorithm to determine this deadline would be ideal, but for example the following would suffice:
deadlineRx1 = RxDelay / 2
deadlineRx2 = RxDelay / 2 + 1

I'm currently in the process of refactoring the downlink queue, also with future class b in mind. This will be one of the things that might get improved. Please note that you can increase the following config value to give the application-server more time to enqueue data as a response to an uplink:
--get-downlink-data-delay value         delay between uplink delivery to the app server and getting the downlink data from the app server (if any) (default: 100ms) [$GET_DOWNLINK_DATA_DELAY]

https://docs.loraserver.io/loraserver/install/config/

Ah, that configuration parameter fixes my problem! Thank you!

Is there any rules, of how the confirmed downlink with ack getting timeout will be retransmitted again?
Does server generally makes this retransmition? How much attempts will make server? Is there any dependencies on working in different LoRa classes?

I've just released a new version which sends either an ACK or nACK. Then it is up to your application if you want to re-transmit or not. The server won't schedule any re-transmissions anymore.


Servo TSC Meeting November 2024

Date: Monday 25th November 2024 at 16:00 UTC
Location: https://meet.jit.si/Servo-TSC

Agenda

Status update
Roadmap
Use of cargo-vet
More self-hosted GA runners (build/test servers)
Crowdfunding
Outreach
AOB

Agenda item please: use of https://github.com/mozilla/cargo-vet

Agenda Item:
More self-hosted GA runners (build/test servers):

I propose we set up some:

5 min (self hosted) vs 15+ min build time (hosted)

Is the TSC generally in favour of this?
Do TSC members have particular suggestions?

macOS server?
build vs WPT?

For the roadmap, we have been using a document that we could use during the call today: https://hackmd.io/@rego/servo-roadmap-discussion/edit
That's collecting the proposals from #109, so we could try to sort them out during the call. If it takes too long maybe we can come back to the issue/zulip and continue the discussion there as a follow-up.


Move to latest nginx version

Description
Move to latest nginx version
Type of change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration. Is it a breaking change which will impact consuming tool(s)?

[x] make e2e

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] Any dependent changes have been merged and published in downstream modules

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 88.921%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1862

Relevant Lines:
2094

💛  - Coveralls


update dependencies

Signed-off-by: Anthony Voutas<EMAIL_ADDRESS>

@jsaur your thoughts on this latest error would be appreciated. I tried reverting crypto-random-string to 3.3.1 but the error persisted so it might be caused by the jest update, not sure

Ya, I'm seeing the same thing... want about reverting jest to an earlier build? (or does it have security issues?)
The other option I'm seeing is potentially to use babel-jest to do the transforms instead of ts-jest
https://stackoverflow.com/questions/59879689/jest-syntaxerror-cannot-use-import-statement-outside-a-module
This would require adding a new dev module and a babel config, etc...

I just reverted all the jest related dependencies and the error is still occuring

Might need to go with the babel-jest option


Fatal Crash on Startup of Kitematic (12" Macbook )

On launching Kitematic, at about 9% my MacBook shuts down (black screen of death.)  Totally repeatable.  Here are specs:
Model Name:	MacBook
Model Identifier:	MacBook8,1
Processor Name:	Intel Core M
Processor Speed:	1.2 GHz
Number of Processors:	1
Total Number of Cores:	2
L2 Cache (per Core):	256 KB
L3 Cache:	4 MB
Memory:	8 GB
Boot ROM Version:	MB81.0164.B02
SMC Version (system):	2.25f85
Yosemite 10.10.3
r

@RickBL99 Thanks for this. This is an issue that's harder to troubleshoot. We will try to get our hands on the new 12" macbook for testing.
Thanks!

No worries.  Good luck.  Will try on different machine.
r

On Jun 19, 2015, at 4:26 PM, Michael Chiang<EMAIL_ADDRESS>wrote:
@RickBL99 https://github.com/RickBL99 Thanks for this. This is an issue that's harder to troubleshoot. We will try to get our hands on the new 12" macbook for testing.
Thanks!
—
Reply to this email directly or view it on GitHub https://github.com/kitematic/kitematic/issues/672#issuecomment-113670552.

Rick Leckrone
CEO
Corporate Headquarters:
774 Homewillow Ave
Las Vegas, NV 89123
Blend Seattle:
501 East Pine Street
Suite 200
Seattle WA  98122
C:  +1<PHONE_NUMBER>
F:  +1<PHONE_NUMBER>
Web: http://www.blendimages.com http://www.blendimages.com/
Twitter: http://twitter.com/blendimages http://twitter.com/blendimages
Facebook: http://www.facebook.com/pages/Blend-Images/100390375008 http://www.facebook.com/pages/Blend-Images/100390375008
LinkedIn: http://www.linkedin.com/companies/141069/Blend Images http://www.linkedin.com/companies/141069/Blend Images

Did happen for me too.  Kernel panic log if it helps solving it:
Mon Jun 29 16:04:11 2015
*** Panic Report ***
panic(cpu 0 caller 0xffffff8001017cc2): Kernel trap at 0xffffff810b75c6c0, type 14=page fault, registers:
CR0: 0x0000000080010033, CR2: 0x00000001043033e0, CR3: 0x0000000221ca203a, CR4: 0x00000000003627e0
RAX: 0x00000001043033e0, RBX: 0x0000000000000000, RCX: 0x000000000000000a, RDX: 0x0000000000000000
RSP: 0xffffff800d508f50, RBP: 0xffffff800d508f50, RSI: 0x0000000000000001, RDI: 0x0000000000000015
R8:  0x0000000000000000, R9:  0xffffff800d508ea8, R10: 0x00000001043032a0, R11: 0x0000000000000015
R12: 0xffffff800d50d000, R13: 0x0000000000000000, R14: 0xffffff7f8370a0a0, R15: 0xffffff800d508fc0
RFL: 0x0000000000010202, RIP: 0xffffff810b75c6c0, CS:  0x0000000000000008, SS:  0x0000000000000010
Fault CR2: 0x00000001043033e0, Error code: 0x0000000000000001, Fault CPU: 0x0 SMAP fault
Backtrace (CPU 0), Frame : Return Address
0xffffff800d508c00 : 0xffffff8000f2bda1
0xffffff800d508c80 : 0xffffff8001017cc2
0xffffff800d508e40 : 0xffffff8001034b73
0xffffff800d508e60 : 0xffffff810b75c6c0
0xffffff800d508f50 : 0xffffff810b73d550
0xffffff800d508f70 : 0xffffff810b75afbb
0xffffff800d508fb0 : 0xffffff810b7edb1e
0xffffff810cceb9c0 : 0xffffff810b75b2fd
0xffffff810cceba00 : 0xffffff7f836d9ab5
0xffffff810ccebaa0 : 0xffffff7f836e16d0
0xffffff810ccebb30 : 0xffffff8001180fb9
0xffffff810ccebb80 : 0xffffff800116f7f6
0xffffff810ccebc10 : 0xffffff8001164693
0xffffff810ccebe00 : 0xffffff80013ae84b
0xffffff810ccebe30 : 0xffffff80013ed7c4
0xffffff810ccebf50 : 0xffffff800144ba86
0xffffff810ccebfb0 : 0xffffff8001035376
Kernel Extensions in backtrace:
org.virtualbox.kext.VBoxDrv(4.3.18)[22E424AA-7433-7745-C24C-72982B3936F8]@0xffffff7f836d1000->0xffffff7f83727fff
BSD process name corresponding to current thread: VBoxHeadless
Mac OS version:
14D136
Kernel version:
Darwin Kernel Version 14.3.0: Mon Mar 23 11:59:05 PDT 2015; root:xnu-2782.20.48~5/RELEASE_X86_64
Kernel UUID: 4B3A11F4-77AA-3D27-A22D-81A1BC5B504D
Kernel slide:     0x0000000000c00000
Kernel text base: 0xffffff8000e00000
__HIB  text base: 0xffffff8000d00000
System model name: MacBookPro12,1 (Mac-E43C1C25D4880AD6)
System uptime in nanoseconds:<PHONE_NUMBER>67
last loaded kext at<PHONE_NUMBER>: org.virtualbox.kext.VBoxNetAdp  4.3.18 (addr 0xffffff7f83735000, size 28672)

@nicklaslof Is that from the 12" Macbook as well?

No. a brand new 13" Macbook Pro.
Attached a screenshot with details:

This is screen shot of mine.
https://www.dropbox.com/s/mlqm0wygea9rn1a/Screenshot 2015-06-29 15.00.56.png?dl=0 https://www.dropbox.com/s/mlqm0wygea9rn1a/Screenshot 2015-06-29 15.00.56.png?dl=0
r

On Jun 29, 2015, at 2:12 PM, Nicklas Löf<EMAIL_ADDRESS>wrote:
No. a brand new 13" Macbook Pro.
Attached a screenshot with details:
https://cloud.githubusercontent.com/assets/331622/8418556/4dd7a7d8-1eb4-11e5-89a4-51f41ba3a9aa.png
—
Reply to this email directly or view it on GitHub https://github.com/kitematic/kitematic/issues/672#issuecomment-116847685.

Rick Leckrone
CEO
Corporate Headquarters:
774 Homewillow Ave
Las Vegas, NV 89123
Blend Seattle:
501 East Pine Street
Suite 200
Seattle WA  98122
C:  +1<PHONE_NUMBER>
F:  +1<PHONE_NUMBER>
Web: http://www.blendimages.com http://www.blendimages.com/
Twitter: http://twitter.com/blendimages http://twitter.com/blendimages
Facebook: http://www.facebook.com/pages/Blend-Images/100390375008 http://www.facebook.com/pages/Blend-Images/100390375008
LinkedIn: http://www.linkedin.com/companies/141069/Blend Images http://www.linkedin.com/companies/141069/Blend Images

Screenshot…
https://www.dropbox.com/s/mlqm0wygea9rn1a/Screenshot 2015-06-29 15.00.56.png?dl=0 https://www.dropbox.com/s/mlqm0wygea9rn1a/Screenshot 2015-06-29 15.00.56.png?dl=0

On Jun 29, 2015, at 1:53 PM, Michael Chiang<EMAIL_ADDRESS>wrote:
@nicklaslof https://github.com/nicklaslof Is that from the 12" Macbook as well?
—
Reply to this email directly or view it on GitHub https://github.com/kitematic/kitematic/issues/672#issuecomment-116843886.

Rick Leckrone
CEO
Corporate Headquarters:
774 Homewillow Ave
Las Vegas, NV 89123
Blend Seattle:
501 East Pine Street
Suite 200
Seattle WA  98122
C:  +1<PHONE_NUMBER>
F:  +1<PHONE_NUMBER>
Web: http://www.blendimages.com http://www.blendimages.com/
Twitter: http://twitter.com/blendimages http://twitter.com/blendimages
Facebook: http://www.facebook.com/pages/Blend-Images/100390375008 http://www.facebook.com/pages/Blend-Images/100390375008
LinkedIn: http://www.linkedin.com/companies/141069/Blend Images http://www.linkedin.com/companies/141069/Blend Images

Did happen for me too.
Fatal Crash on Startup of Kitematic (12" Macbook )
main problem maybe==> libnode.dylib  isn't work on macbook pro 12' device
please fix it as soon as ..

Had a similar problem on a OS X Yosemite 10.10.4, the problem is probably related to boot2docker issue:
https://github.com/boot2docker/boot2docker/issues/800
Downloading latest 4.3.x VirtualBox release helped:
https://www.virtualbox.org/wiki/Download_Old_Builds_4_3

Should be fixed with latest Docker Toolbox by using the latest VirtualBox


Offset of Multiple Lines with Variable offset Values

Can it done with this Clipper
Offset of Multiple Lines with Variable offset Values[for each of those Lines/Curves] having Proper Angled Edges at the End

If you mean multiple offset with combined output , this not possible.

No there are N number of lines with N number of offsets.. they're end product to be combined.

I don't understand your question.
Can you show an example?

Can this be done??

Did you try to create this?
Based on your image you can get this result by using Graft  because the curves in the same list will combined.

yes I made filter for line close by that's not relevant.. how can I get offsets to these lines.??

yes.. graft is not solution I want those outer edges to be fillet

Clipper always combined curves in the same list , the only solution is graft.

This is not related to Clipper , you may ask in the forum


Reimplement tosa.rescale/tosa.apply_scale lowering to not use 64-bit math and vectorize.

We ran into an issue with an i8 quantized model (https://storage.googleapis.com/download.tensorflow.org/models/tflite_11_05_08/mobilenet_v2_1.0_224_quant.tgz) that was trying to use 64-bit math in VMVX (not supported by default). This highlighted that we are still doing the full expansion of rescale ops to non-trivial 64-bit math:
%145 = "tosa.rescale"(%144) {double_round = true, input_zp = 0 : i32, multiplier = [1764866200 : i32], output_zp = -128 : i32, per_channel = false, scale32 = true, shift = [36 : i32]} : (tensor<1x7x7x1280xi32>) -> tensor<1x7x7x1280xi8>

      func @main_dispatch_72(%arg0: !stream.binding {stream.alignment = 32 : index}, %arg1: !stream.binding {stream.alignment = 32 : index}) {
            ...
            scf.for %arg4 = %6 to %c1280 step %7 {
              %8 = affine.min #map56(%arg2)[%workgroup_size_2]
              %9 = affine.min #map56(%arg3)[%workgroup_size_1]
              %10 = affine.min #map53(%arg4)[%workgroup_size_0]
              %11 = flow.dispatch.tensor.load %0, offsets = [0, %arg2, %arg3, %arg4], sizes = [1, %8, %9, %10], strides = [1, 1, 1, 1] : !flow.dispatch.tensor<readonly:1x1x1x1280xi32> -> tensor<1x?x?x?xi32>
              %12 = linalg.init_tensor [1, %8, %9, %10] : tensor<1x?x?x?xi8>
              %13 = linalg.generic {indexing_maps = [#map12, #map12], iterator_types = ["parallel", "parallel", "parallel", "parallel"]} ins(%11 : tensor<1x?x?x?xi32>) outs(%12 : tensor<1x?x?x?xi8>) {
              ^bb0(%arg5: i32, %arg6: i8):  // no predecessors
                %14 = arith.subi %arg5, %c-6272_i32 : i32
                %15 = "tosa.apply_scale"(%14, %c21913098_i32, %c30_i8) {double_round = false} : (i32, i32, i8) -> i32
                %16 = arith.addi %15, %c-128_i32 : i32
                %17 = arith.cmpi slt, %16, %c-128_i32 : i32
                %18 = select %17, %c-128_i32, %16 : i32
                %19 = arith.cmpi slt, %c127_i32, %16 : i32
                %20 = select %19, %c127_i32, %18 : i32
                %21 = arith.trunci %20 : i32 to i8
                linalg.yield %21 : i8
              } -> tensor<1x?x?x?xi8>
              flow.dispatch.tensor.store %13, %1, offsets = [0, %arg2, %arg3, %arg4], sizes = [1, %8, %9, %10], strides = [1, 1, 1, 1] : tensor<1x?x?x?xi8> -> !flow.dispatch.tensor<writeonly:1x1x1x1280xi8>
            }
          }

(note that the apply_scale survives long into translation)
->
        llvm.func internal @main_dispatch_72(%arg0: !llvm.ptr<struct<"iree_hal_executable_dispatch_state_v0_t", (array<3 x i32>, array<3 x i32>, i64, ptr<i32>, i64, ptr<ptr<i8>>, ptr<i64>, ptr<func<i32 (ptr<func<i32 (ptr<i8>)>>, ptr<i8>)>>, ptr<ptr<func<i32 (ptr<i8>)>>>)>>, %arg1: !llvm.ptr<array<3 x i32>>, %arg2: !llvm.ptr<i8>) -> i32 attributes {sym_visibility = "private"} {
         ...
        ^bb7:  // pred: ^bb6
          %63 = llvm.mul %1, %2  : i64
          %64 = llvm.add %59, %63  : i64
          %65 = llvm.add %64, %63  : i64
          %66 = llvm.add %65, %63  : i64
          %67 = llvm.add %66, %61  : i64
          %68 = llvm.getelementptr %51[%67] : (!llvm.ptr<i32>, i64) -> !llvm.ptr<i32>
          %69 = llvm.load %68 : !llvm.ptr<i32>
          %70 = llvm.sub %69, %4  : i32
          %71 = llvm.mlir.constant(29 : i8) : i8
          %72 = llvm.sext %71 : i8 to i64
          %73 = llvm.shl %17, %72  : i64
          %74 = llvm.sext %70 : i32 to i64
          %75 = llvm.mlir.constant(21913098 : i64) : i64
          %76 = llvm.mlir.constant(30 : i64) : i64
          %77 = llvm.mul %74, %75  : i64
          %78 = llvm.add %77, %73  : i64
          %79 = llvm.ashr %78, %76  : i64
          %80 = llvm.trunc %79 : i64 to i32
          %81 = llvm.add %80, %5  : i32
          %82 = llvm.icmp "slt" %81, %5 : i32
          %83 = llvm.select %82, %5, %81 : i1, i32
          %84 = llvm.icmp "slt" %6, %81 : i32
          %85 = llvm.select %84, %6, %83 : i1, i32
          %86 = llvm.trunc %85 : i32 to i8
          %87 = llvm.getelementptr %60[%67] : (!llvm.ptr<i8>, i64) -> !llvm.ptr<i8>
          llvm.store %86, %87 : !llvm.ptr<i8>
          %88 = llvm.add %61, %3  : i64
          llvm.br ^bb6(%88 : i64)
          ...

Going i8 -> i64 -> i8 is excessive but more importantly on 32-bit platforms (including mobile GPUs) this will be emulated math and much slower than it needs to be. Even on 64-bit platforms this (if it vectorized, which it doesn't) would effectively halve the amount of work we can do by using up twice as much register space. According to https://discord.com/channels/689900678990135345/804059051750457404/915274606837903380 tflite and the ARM compute library both use i32 math and we should do the same.
Here's the aarch64 intrinsic version using 32-bit math: https://github.com/ARM-software/ComputeLibrary/blob/7dcb9fadb98cad05fca72de3273311d570d98b4e/src/core/NEON/kernels/arm_gemm/quantized.cpp
This shows roughly the mix of instructions we should be ending up with and a benchmark for how close we are to doing that. Today we are quite far:
.LBB65_16:
	.loc	2 254 12
	ldr	q5, [x23, x26]
	dup	v6.2d, x6
	add	x26, x26, #16
	mov	v7.16b, v6.16b
	add	v5.4s, v5.4s, v4.4s
	ext	v16.16b, v5.16b, v5.16b, #8
	smlal	v6.2d, v5.2s, v1.2s
	smlal	v7.2d, v16.2s, v1.2s
	shrn	v5.2s, v6.2d, #30
	shrn2	v5.4s, v7.2d, #30
	smax	v5.4s, v5.4s, v0.4s
	umin	v5.4s, v5.4s, v2.4s
	xtn	v5.4h, v5.4s
	eor	v5.8b, v5.8b, v3.8b
	xtn	v5.8b, v5.8h
	str	s5, [x24, x27]
	add	x27, x27, #4
	cmp	x27, #64

oh, and this matters because in a quantized model nearly every single kernel ends up with a rescaling operation, meaning that we are likely running nearly everything in this degraded state:

Here's some additional information from MatthewARM:

I've found out a bit more - George at Arm tells me that the int64 is unavoidable in reference code, but the optimised Arm code avoids it with the sqrdmul instruction

tflite reference:
https://github.com/tensorflow/tensorflow/pull/50290/files
I vaguely recall us talking about a better lowering path than having apply_scale tunnel all the way down so that we could use the instructions and avoid the extra work but that seems to have not been done and only tosa->std exists:
https://github.com/llvm/llvm-project/blob/a54f4eae0e1d0ef5adccdcf9f6c2b518dc1101aa/mlir/lib/Conversion/TosaToStandard/TosaToStandard.cpp#L58
Would be good to evaluate how to better lower that to vector dialect so that we can get the proper fusion/folding with that as we switch off of LLVM autovectorization.

If we need an op in the VM to do this I can add it - or emulate it - but not having to add a tosa.apply_rescale and instead using something standard would be ideal.

The best way forward I see is to not promote to 64-bit to begin with. This was done to match the reference implementation I think. For the quantized path, thats overly conservative? Would be really good to just resolve this at TOSA level without it even surviving to IREE core?

agreed that'd be ideal - it should just be math - I think the issue was that the saturating multiply had no representation in arith so no way to get that lowered through without emulating it (as it does with those compares) - but this may just mean a single arith op like fma for multiply w/ saturation and then we're done

There's also some silly cases that show up with double-rescales that don't seem to get cleaned up - moving to more standard ops will hopefully let some of that fall out but we may want tosa-level optimizations as well:
%166 = "tosa.rescale"(%165) {double_round = true, input_zp = 0 : i32, multiplier = [1257485775 : i32], output_zp = -19 : i32, per_channel = false, scale32 = true, shift = [39 : i32]} : (tensor<1x14x14x64xi32>) -> tensor<1x14x14x64xi8>
    %167 = "tosa.rescale"(%166) {double_round = false, input_zp = -19 : i32, multiplier = [1999568813 : i32], output_zp = 0 : i32, per_channel = false, scale32 = true, shift = [12 : i32]} : (tensor<1x14x14x64xi8>) -> tensor<1x14x14x64xi32>

It also looks like there are many cases where it goes rescale->[ conv | rescale ], which causes the rescales to be in their own dispatch region today - ensuring they are always fused with producers (when narrowing) and consumers (when widening) is going to be critical (right now we do things like rescale i8->i32 into memory and then read those i32 in the consumers) - maybe something that is easier to tackle once this is all represented right.

I cant see the types in the snippet you have, but rescale -> conv needs to be represented as a new named op.

agreed that'd be ideal - it should just be math - I think the issue was that the saturating multiply had no representation in arith so no way to get that lowered through without emulating it (as it does with those compares) - but this may just mean a single arith op like fma for multiply w/ saturation and then we're done

yeah we probably need to add more ops to arith dialect for that. That is the easy part.

Ahh we may need a few of those named ops then - I think the important thing is that we aren't materializing into memory in unquantized/widened values, but also want to ensure that within a dispatch we aren't rescaling multiple times - the composition of that with linalg -> dispatch region formation -> loops escapes me though :P

do you think we'll still be able to make the guarantees that across dispatch regions we aren't materializing full unquantized values into memory if we remove all of the semantics? (I could see ways to try to ensure the I/O edges are on narrow/widen, but in my mind the solutions to implement that are all hacky)

Patterns like this are what we see a lot of:
  %210 = "tosa.depthwise_conv2d"(%209, %101, %62) {dilation = [1, 1], pad = [1, 1, 1, 1], quantization_info = {input_zp = -128 : i32, weight_zp = 31 : i32}, stride = [1, 1]} : (tensor<1x14x14x576xi8>, tensor<3x3x576x1xi8>, tensor<576xi32>) -> tensor<1x14x14x576xi32>
  %211 = "tosa.rescale"(%210) {double_round = true, input_zp = 0 : i32, multiplier = [1279693056 : i32], output_zp = -128 : i32, per_channel = false, scale32 = true, shift = [34 : i32]} : (tensor<1x14x14x576xi32>) -> tensor<1x14x14x576xi8>
  %212 = "tosa.conv2d"(%211, %63, %64) {dilation = [1, 1], pad = [0, 0, 0, 0], quantization_info = {input_zp = -128 : i32, weight_zp = 26 : i32}, stride = [1, 1]} : (tensor<1x14x14x576xi8>, tensor<96x1x1x576xi8>, tensor<96xi32>) -> tensor<1x14x14x96xi32>
  %213 = "tosa.rescale"(%212) {double_round = true, input_zp = 0 : i32, multiplier = [1666054802 : i32], output_zp = -1 : i32, per_channel = false, scale32 = true, shift = [39 : i32]} : (tensor<1x14x14x96xi32>) -> tensor<1x14x14x96xi8>
  %214 = "tosa.rescale"(%213) {double_round = false, input_zp = -1 : i32, multiplier = [1073741824 : i32], output_zp = 0 : i32, per_channel = false, scale32 = true, shift = [11 : i32]} : (tensor<1x14x14x96xi8>) -> tensor<1x14x14x96xi32>
  %215 = "tosa.rescale"(%207) {double_round = false, input_zp = -1 : i32, multiplier = [2031709950 : i32], output_zp = 0 : i32, per_channel = false, scale32 = true, shift = [12 : i32]} : (tensor<1x14x14x96xi8>) -> tensor<1x14x14x96xi32>
  %216 = "tosa.add"(%214, %215) : (tensor<1x14x14x96xi32>, tensor<1x14x14x96xi32>) -> tensor<1x14x14x96xi32>
  %217 = "tosa.rescale"(%216) {double_round = true, input_zp = 0 : i32, multiplier = [1713159654 : i32], output_zp = -2 : i32, per_channel = false, scale32 = true, shift = [50 : i32]} : (tensor<1x14x14x96xi32>) -> tensor<1x14x14x96xi8>

if the depthwise_conv2d and conv2d end up in different regions we want them to have the rescale edges, and if the add gets fused into the conv2d (which it should) we want the intermediate rescales to be elided

I am not saying we remove the semantics. The semantics should be captured using named ops. Potentially also need some arith operations that do the special math. That is the only way I see possible.

ah ok didn't think of named arith ops - perhaps attributes are another route to avoid needing to have 1:1 copies of things - but if you see a path that's awesome :)

if the depthwise_conv2d and conv2d end up in different regions we want them to have the rescale edges, and if the add gets fused into the conv2d (which it should) we want the intermediate rescales to be elided

If the rescale is combined with the conv2d, the edge carries the information in types?

it currently falls over today if the rescales have multiple uses and such - but hopefully not a limitation forever!

thats a separate issue. I am saying tosa.rescale -> tosa.conv2dis insteadtosa.conv2d_some_type_input_some_type_output`.

Many of the tosa.rescales can be optimized away (on my list) so I wouldn't focus on them. Many are actually no-ops or broadcasts.
As for tosa.rescale, the important focus is on tosa.apply_scale: due to how tosa performs its rescale it is guaranteed we either need some custom arith-ops that do mul-add-shift (iirc) OR we need to do the math in i64. It would be valuable to have some arith operators to prevent this but I am not the expert on what those ops should look like.

We may not want to get rid of all the rescales to early, though - that's the compositional complexity here and what Mahesh's proposal may help with. If we got rid of the information encoded in the IR that a value can be represented in i8 we can't get that back later. I believe it's only after dispatch region formation we'd want to fold away the rescaling math - assuming we don't do silly things (like we do today) like putting rescales in their own dispatch regions and such - also something Mahesh's proposal should help with (a named conv_with_rescale can't be split apart too early).

We do vectorize tosa.apply_scale in Linalg and then lower it to a vector native or emulated 64-bit integer implementation when lowering to LLVM

Dropping codegen label for now based on above reply. Will let Rob close it out.

Completed. There is now an optional pass that lowers to purely 32-bit operations. Used for the RISC-V lowerings.


Readme suggestion

Perhaps include information on how to make the daemon start at boot? At least on OpenBSD.
A helpful piece of information I discovered is that if you are configuring qotdd in /etc/rc.local (a la FAQ 10.3) then you must put an "&" at the end of the command invocation, otherwise the boot process will hang. I thought others may benefit from this kind of information.

That was my fault. I forgot the call to daemon(). All the daemons are now fixed.
FWIW, writing an rc script would be better:
#!/bin/sh
#
# $OpenBSD$

daemon="/usr/local/sbin/qotdd"

. /etc/rc.d/rc.subr

rc_reload=NO

rc_stop() {
        pkill -USR1 -xf "${pexp}"
}

rc_cmd $1

Thanks for the tip! I'll give that a try.


Change get_current_edited_scene_history_id() to handle negative indices

2023-09-09 19:22:48.438831-0700 godot.macos.editor.double.arm64[67638:487576] ERROR: FATAL: Index p_index = 0 is out of bounds (size() = 0).
at: get (./core/templates/cowdata.h:155)
ERROR: FATAL: Index p_index = 0 is out of bounds (size() = 0).
at: get (./core/templates/cowdata.h:155)

The code change modifies the condition in get_current_edited_scene_history_id() to handle negative indices properly. This ensures that the function returns the correct history ID when the current edited scene is a valid index or within the range of edited scenes.
I am not sure if I'm able to find a minimal reproduction project for this. Will try to narrow it down.

Close because I can't recreate the bug.


Fix styling of email fields in AbstractEmailForm example

classname="full" is incorrect here (it generates excessive padding); also, using a FieldRowPanel
can make the display neater.

Merged. Thanks!
P.S: Just noticed that FieldRowPanel adds padding-left. I'll create a separate issue.


Move carrier server inside the cluster

While we refactor the various commands to talk to the Carrier server, it make sense to have the Carrier server running inside the cluster as a deployment instead of starting it locally.
This simplifies the tests (they don't have to start and stop external processes) and is closer to the final result. As soon as all commands are migrated, there is nothing left to do (compared to the local server solution we are using now).
During development, it still makes sense to manually start a local server instead of generating a new image, pushing it and deploying Carrier again. We should make sure this development workflow, with the local server, is still possible.
Acceptance Criteria

carrier install creates a deployment running the Carrier server
There is a pipeline that builds and pushes the carrier server image to a public registry.
The release pipeline tags the image with the version of the release.
All migrated commands talk to the server running inside the cluster instead of starting a local one.
The carrier server is accessible through an ingress and its url is discovered automatically if not set explicitly through the command line.
[Optional] The first time we discover the url, we write it to the carrier config so we don't have to do that again every time. Can be moved to a separate issue to keep the scope small.

We are trying to implement it in a way that works both for released versions but also while doing development. Here is the proposal.
Release CI:

Builds the binary which references a container image of the same version (the version under release).
This images doesn't exist yet.
Builds and publishes the container image which includes the very same binary.
Now the image exists and the binary is ready to be used for carrier install.

Development workflow:

The developer runs make build. This creates a binary that references an image of the same version. This image doesn't exist yet. This is exactly the same process like above.
The developer runs a make patch-carrier target which does the following:

Creates a PVC and a dummy pod that mounts it.
Runs kubectl cp and copies the binary inside the pod on the location where the PVC is mounted (thus putting the binary on the PVC)
Patches the carrier server deployment to change the image to be an existing one (e.g. the base image used in the release CI) and adds amount of the same PVC as above on the location where the carrier binary is expected. This creates a patched deployment which uses an existing image and has the binary produced with the make build above.

The proposed development process above should be rather fast because it doesn't require us to build and publish any new images after every make build. We'll come up with exacts numbers soon.

PR #260 satisfies all the acceptance Criteria except for 4,half of 5 and 6. These will be implemented in a separate PR to avoid stepping on each other with issues #239 and #253


Fix WP events processor to import events data

Some events in WP don't have fields that are required in Wagtail. Rather than make then non-required, I've refactored the code so it doesn't fail the imports, but will still not convert the page over.
Changes

Changed eventpage.py processor to check to see if start and end dates exist before assignment.

Testing

./cfgov/manage.py import-data events eventpage --parent events -u user -p pass

Review

@richaagarwal
@kave

Notes

There are currently 12 events that don't have the necessary fields for conversion.

Todos

Add import-data to our build flow and send email notifications on errors

:+1:


n_jobs defaults to -1 and machine runs out of memory

Trying to overide n_jobs to a lower number than the number of cores available on my P4000 Paperspace linux machine but no matter what value I assign n_jobs in paramGrid below, I see in the output "[Parallel(n_jobs=-1)]: Using backend LokyBackend with 8 concurrent workers."
Why is this?
Then I get the error below because I think the machine runs out of memory:
TerminatedWorkerError: A worker process managed by the executor was unexpectedly terminated. This could be caused by a segmentation fault while calling the function or by an excessive memory usage causing the Operating System to kill the worker. The exit codes of the workers are {SIGKILL(-9)}
Please advise?
`import parfit.parfit as pf
import numpy as np
from sklearn.model_selection import ParameterGrid
from sklearn.metrics import mean_squared_error
paramGrid = ParameterGrid({
'min_samples_leaf': [1,3,5],
'max_features': [15,26,28,32], #'sqrt', 'log2',
'n_estimators': [60],
'n_jobs': [4],
'random_state': [23]
})
X_train,y_train=prepare_data_rf(df_train,cat_names,cont_names,dep_var)
X_train=X_train.fillna(X_train.mean())
X_val,y_val=prepare_data_rf(df_valid,cat_names,cont_names,dep_var)
X_val=X_val.fillna(X_train.mean())`
Output
-------------FITTING MODELS-------------
[Parallel(n_jobs=-1)]: Using backend LokyBackend with 8 concurrent workers.
[Parallel(n_jobs=-1)]: Done   1 tasks      | elapsed:  7.0min
[Parallel(n_jobs=-1)]: Done   3 out of  12 | elapsed: 10.3min remaining: 31.0min
[Parallel(n_jobs=-1)]: Done   5 out of  12 | elapsed: 14.0min remaining: 19.6min
[Parallel(n_jobs=-1)]: Done   7 out of  12 | elapsed: 14.7min remaining: 10.5min
[Parallel(n_jobs=-1)]: Done   9 out of  12 | elapsed: 14.7min remaining:  4.9min
TerminatedWorkerError                     Traceback (most recent call last)
 in
/opt/conda/envs/fastai/lib/python3.6/site-packages/parfit/parfit.py in bestFit(model, paramGrid, X_train, y_train, X_val, y_val, nfolds, metric, greater_is_better, predict_proba, showPlot, scoreLabel, vrange, cmap, n_jobs, verbose)
63     else:
64         print("-------------FITTING MODELS-------------")
---> 65         models = fitModels(model, paramGrid, X_train, y_train, n_jobs, verbose)
66         print("-------------SCORING MODELS-------------")
67         scores = scoreModels(models, X_val, y_val, metric, predict_proba, n_jobs, verbose)
/opt/conda/envs/fastai/lib/python3.6/site-packages/parfit/fit.py in fitModels(model, paramGrid, X, y, n_jobs, verbose)
49         myModels = fitModels(model, paramGrid, X_train, y_train)
50     """
---> 51     return Parallel(n_jobs=n_jobs, verbose=verbose)(delayed(fitOne)(model, X, y, params) for params in paramGrid)
/opt/conda/envs/fastai/lib/python3.6/site-packages/joblib/parallel.py in call(self, iterable)
932
933             with self._backend.retrieval_context():
--> 934                 self.retrieve()
935             # Make sure that we get a last message telling us we are done
936             elapsed_time = time.time() - self._start_time
/opt/conda/envs/fastai/lib/python3.6/site-packages/joblib/parallel.py in retrieve(self)
831             try:
832                 if getattr(self._backend, 'supports_timeout', False):
--> 833                     self._output.extend(job.get(timeout=self.timeout))
834                 else:
835                     self._output.extend(job.get())
/opt/conda/envs/fastai/lib/python3.6/site-packages/joblib/_parallel_backends.py in wrap_future_result(future, timeout)
519         AsyncResults.get from multiprocessing."""
520         try:
--> 521             return future.result(timeout=timeout)
522         except LokyTimeoutError:
523             raise TimeoutError()
/opt/conda/envs/fastai/lib/python3.6/concurrent/futures/_base.py in result(self, timeout)
430                 raise CancelledError()
431             elif self._state == FINISHED:
--> 432                 return self.__get_result()
433             else:
434                 raise TimeoutError()
/opt/conda/envs/fastai/lib/python3.6/concurrent/futures/_base.py in __get_result(self)
382     def __get_result(self):
383         if self._exception:
--> 384             raise self._exception
385         else:
386             return self._result
TerminatedWorkerError: A worker process managed by the executor was unexpectedly terminated. This could be caused by a segmentation fault while calling the function or by an excessive memory usage causing the Operating System to kill the worker. The exit codes of the workers are {SIGKILL(-9)}

Hi @cinbez,
There is a bit of confusion here. You've specified n_jobs=4 for the parameter grid object, which gets passed into your estimator.
What you want is to set n_jobs=4 for the parfit function e.g. bestFit(n_jobs=4), which is the parallelization over the grid of estimators that are being fitted (1 per combination in your parameter grid).
Let me know if that helps!

Thanks very much @jmcarpenter2! This makes sense. Another issue I'm having is that the package seems to select the model with the highest score for the metric chosen. What if the metric is MSE and you want the model with the lowest MSE? I know in GridSearchCV you can say scoring='neg_mean_squared_error' which is the same as maximizing -1 * MSE. How can I accomplish this with parfit?

Hi @cinbez,
Please check out the docs. There is a parameter in the parfit functions called greater_is_better. Set that to False to to make the "best" output be the one with a lower score e.g. MSE.
Additionally, the likely reason for different in output is because you haven't set the random_state for GridSearchCV. Try setting random_state to the same value for both parfit models and GridSearchCV. You should receive the same result. If you don't please let me know!
Thanks for the questions :)
Jason


The config/rm_auth.py does not include a CatAPI example

The config/rm_auth.py does not include a CatAPI example

It does now


ColumnExpr with Relation queries

Hi,
I've been looking for functionality similar to ColumnExpr() that will select into the right field when used in a Relation query.
Although it's a different module, go-pg's Issue #1852  describes this exact problem.
This could, perhaps, be addressed be implementing a function similar to *InsertQuery.Value(column string, expr string, args ...interface{}), so that the name of the column could be taken as a separate argument. Then, maybe it could be handled similar to the way #139 addressed this?
See this gist for a clearer example.
Any help would be much appreciated.

Can you try:
func AlsoAnInvalidRelationQuery(q *bun.SelectQuery) *bun.SelectQuery {
	return q.ColumnExpr("? AS author__name", "Ronald")
}

Sorry for your time, the issue was that the Relation() apply func was being used in different joins (with different prefixes / aliases)...
The solution is to pass the prefix / alias (eg "author__") to a parent func
func GetRelationQuery(joinPrefix string) func(*bun.SelectQuery) *bun.SelectQuery {
	return func(q *bun.SelectQuery) *bun.SelectQuery {
		return q.ColumnExpr("? AS ?", "Ronald", bun.Ident(joinPrefix+"name"))
	}
}


BUGFIX: initcond.f90 acos causing NaN for some params

Sometimes, when the routine to fix the initial end-to-end distance of the polymer got a small number like 0.0_dp units for the end-to-end distance, there was a numerical instability in its calculation of the initial bead positions that caused NaN's to propagate into the rest of the simulation.
The initial configuration is supposed to be two line segments, intersecting at an angle $\alpha$. The first line is layed along the x-axis with one end at $(0,0,0)$, and the other segment starts half the polymer's length along the x-axis, with the other end sitting in the $xy$-plane with $x>0$ and $y>0$.
The $\acos(\ldots{})$ used to calculate $\alpha$ was the source of the instability, as occasionally it would be asked to apply $\acos$ to a value slightly e.g. below $-1$.


Remove clownbackpack honk

It's spammable and although the storage one also needs nerfing for spam this is far more obnoxious.
:cl:

fix: Remove honk sound on clowns opening backpacks due to too many people spamming it.

would anything go wrong if a use delay was added? i think a backup bike horn is cool if clown loses it / uses for honkbot, but the flashbang is bad

would anything go wrong if a use delay was added? i think a backup bike horn is cool if clown loses it / uses for honkbot, but the flashbang is bad

This


Update gisaid ingest schedule to 1pm CET every day

Long term:

Change the start of pull-and-ingest time from 3AM UTC to 12PM UTC (should be 1pm CET), so that we catch the latest download update from GISAID (should be around 11am CET) - with room for delays on their end

Short term:

Run pull-and-ingest every day (not just M-F) for the short-term to pull in new Omicron sequences ASAP

Not tested!

Looks fine to me.

It modifies only GISAID workflow. Should GenBank be adjusted for symmetry?

We chatted with Emma on Slack and agreed to also adjust the schedule for GenBank, so that they happen at the same time.
I also added the links that Victor mentioned above as comments to the yaml, for people (me) who search every time how to write a correct cron expression


Remove page model from Razor file in "Introduction to Razor Pages in ASP.NET Core"

Per @danroth27  Here’s what I would suggest:
The first razor page we introduce people too should look like this (just a simple page with some dynamic HTML:
@page

Hello, world!

The time on the server is @DateTime.Now

Then we introduce page models as a class in a separate file and with the @model directive:
============ Index2.cshtml ================
@page
@using RazorPages
@model IndexModel2

Separate page model

    @Model.Message

============ Index2.cshtml.cs    ============
using Microsoft.AspNetCore.Mvc.RazorPages;
using System;

namespace RazorPages
{
    public class IndexModel2 : PageModel
    {
        public string Message { get; private set; } = "PageModel in C#";

        public void OnGet()
        {
            Message += $" Server time is { DateTime.Now }";
        }
    }
}

I don’t think we should have any examples showing defining the page model class in the cshtml file.
I do think it’s worth mentioning as an aside/note that the default page model class is the page itself and that for simple cases you can define the page model members in the page model in a @functions block. We should state that having a separate page model class makes your page model testable and is considered best practice.

:shipit:

I'd like us to have no mention of @functions anywhere in our docs. Omitting a page model is fine for the introduction case when there's no logic, but as you say the next step should be adding a page model.

@Rick-Anderson Can this be bumped up in priority? We're still getting feedback on this.

@scottaddie Can you help out here?

Hey Dan,
In your opinion, is more budget for docs from me forthcoming (albeit
delayed) or not happening in the foreseeable future? Just trying to plan.
Thanks!
Steve
On Fri, Sep 8, 2017 at 1:49 AM, Daniel Roth<EMAIL_ADDRESS>wrote:

@scottaddie https://github.com/scottaddie Can you help out here?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/aspnet/Docs/issues/4102#issuecomment-328005487, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAvvLyEM08k1DLn_tEuFn003oylVi3nRks5sgNWCgaJpZM4PCoX7
.

--
Steve Smith
http://ardalis.com | http://twitter.com/ardalis

@danroth27 I will look at this on Monday morning.


Asset list

Adds assets list view under /assets
Allows viewing paginated asset lists, with sorting parameter selection.
Missing features:

selecting sector (rather than MBTiles layer)
selecting other variables than direct damages
handling of domain configurations for field parameters, with live resolving of parameter option lists (currently the dropdowns allow combinations of parameters that are not present in the data)

Merging this in, with remaining features to be implemented as a follow-up


[1.3] update env file for transformers and spacy

Checklist before submitting

[x] Did you read the contributor guide?
[ ] Did you update any affected documentation?
[ ] Did you write any tests to validate this change?

Description
Fixes open-ce/transformers-feedstock#15.
Review process to land

All tests and other checks must succeed.
At least one maintainer must review and approve.
If any  maintainer requests changes, they must be addressed.

Closing this PR as now these changes will be covered in PRs that update pins for transfrormers and spacy respectively.


Registry:get() should error if the given entity does not have a component

Main motivation for this is that it is impossible to accurately type the function as it is now, this change would make the current type accurate.
Secondary motivation is that when it is known an entity should have a specific component, and you attempt to get it, an error will be raised if it does not which can help catch if you have made a mistake in a previous system where the expected component has not been assigned.
Those doing something like:
local value = registry:get(id, comp)
if value then
    print(value)
end

will have to change to:
if registry:has(id, comp) then
    local value = registry:get(id, comp)
    print(value)
end

Looking for feedback on this change.

I have decided to implement this because I think that type safety is a must-have. Leaving this function as it is has the potential for runtime errors when you expect a value but get nil instead.
A new method Registry:try_get() has been implemented that has the old behavior of Registry:get() and only takes a single component argument.


Extract eirini-controller from eirini and eirini-release

As our controller grows and evolves, trying to make the old REST codebase coexist with the new CRDs one is getting more and more convoluted. Let's extract all the CRD-related code to a new repository called eirini-controller. The new repository should include all CRD-releated code, tests, deploy manifests, scripts.
As we do this, let's understand which code is shared by the two implementations, wether it's worth duplicating it, importing in the new project as a library, or rewriting it, maybe leveraging the controller runtime client instead of the clientset?

After some experiments and discussions we decided that we would not use the kubebuilder development flow/tools as they do not really fit our use cases. Instead we are just going to pick up things we like, e.g. generating CRD yamls.
I have copied the https://github.com/cloudfoundry-incubator/eirini repo to https://github.com/cloudfoundry-incubator/eirini-controller (in order to preserve the valuable history), deleted non-eirini-controller bits (might be more leftovers though) and removed the references to eirini (so that eirini-controller has no dependencies to eirini)


Display fps on screen

Why not? People will ask about this (as well as the time it takes to transmit a message and draw it to screen but that's a bit trickier to calculate).

Interesting frequencies include:

Drawing frequency (Update)
Update frequency (Fixed Update)
Received message frequency

Is anything done (or will ever be done) in fixed update?
Definitely update, after all this gives us fps.
Possibly received message frequency, but maybe as X messages/second as we would be receiving simulation state messages at 1 kHz and pose messages at 120 Hz.

We should read from the serial port in fixed update. Getting all the messages is critical for logging. If we read from serial in update and the frame rate drops, flimnap will be dropping messages.

I figured a low priority background thread would be continuously reading from the serial port, not necessarily at any fixed rate.

That makes more sense, yes.


Did anyone find a wallet?

I ran this script for two days and did not find any wallet, Did anyone find a wallet?

Brute forcing is a process that can take up to weeks.


Fix JSON serialization of message attributes with a custom data type

Closes #947
Additional info:

Added custom data type to existing tests in AmazonJavaSdkTestSuite - note the tests will succeed also without changes in MessageAttributesSupport , because aws-java-sdk-sqs version used is 1.12.472 (pre-1.12.584 when JSON protocol was introduced)
Added additional tests to AmazonJavaSdkV2TestSuite basing on AmazonJavaSdkTestSuite (some of these tests will not succeed without changes in MessageAttributesSupport)
The new tests also are able to reproduce the issue described in https://github.com/softwaremill/elasticmq/issues/946, occurring when a binary message attribute is used - need to uncomment "green" -> BinaryMessageAttribute("dog".getBytes("UTF-8")) lines in AmazonJavaSdkV2TestSuite. This PR does not fix this issue.

Moved to a different fork: https://github.com/softwaremill/elasticmq/pull/950


Adding GDAL as implementation of tiled-assets extension

Related Issue(s): #
none
Proposed Changes:

Adding GDAL as tiled-asset implementor

PR Checklist:

[x] This PR is made against the dev branch (all proposed changes except releases should be against dev, not master).
[x] This PR has no breaking changes.
[x] I have added my changes to the CHANGELOG or a CHANGELOG entry is not required.

We did not do the update yet, but we decided recently to not add implementations/catalogs to the extensions any longer as it requires a lot of updates/maintenance, but instead add them to STAC Index and link to the Index from here.

We did not do the update yet, but we decided recently to not add implementations/catalogs to the extensions any longer as it requires a lot of updates/maintenance, but instead add them to STAC Index and link to the Index from here.

Thank you anyway. I have just added GDAL to STAC Index.

Thank you anyway. I have just added GDAL to STAC Index.


2261 update heidelberg hackathon page

I'm not really sure why these PRs were merged into a feature branch instead of main. Took me a while to figure out why they weren't showing up on the live site. I guess that this was an accident @heylf ?
Anyway, merging this PR should make them go live.

@nf-core-bot fix linting


Typescript is not able to detect powerbi specific properties

Hello @howlowck,
In the 0.9.0 release, typescript is not able to determine the powerBI specific properties:
TS2322: Type '{ id: string; embedUrl: string; accessToken: string; filterPaneEnabled: false; navContentPaneEnabled: false; height: string; mobile: boolean; }' is not assignable to type 'IntrinsicAttributes & PowerBIEmbeddedProps & { children?: ReactNode; }'.
  Property 'embedUrl' does not exist on type 'IntrinsicAttributes & PowerBIEmbeddedProps & { children?: ReactNode; }'.

It complains about all power-bi client specific models:

embedUrl
accessToken
height

My report is pretty simple:
        <PowerbiEmbedded
          id={props.report.id}
          embedUrl={props.report.embedUrl}
          accessToken={props.embed.token}
          filterPaneEnabled={ false }
          navContentPaneEnabled={ false }
          height="800px"
          mobile={matches.phone}
        />

I think it is related to this commit:
https://github.com/howlowck/react-powerbi/commit/1bde300cf6f0963349d02974abbde8de9604680a#diff-0e3ac3694919aca1db302bc3ebe669f2

yikes.. that's not good. I'll take a look today

I also have this exact problem.

Hey upgrade to 0.9.1 and it should fix the typing issue.

I deleted node_modules and upgraded packages, it solved the problem. Will
try the new version also.
On Mon, 29 Jun 2020, 18:26 Hao Luo<EMAIL_ADDRESS>wrote:

Hey upgrade to 0.9.1 and it should fix the typing issue.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/howlowck/react-powerbi/issues/28#issuecomment-651226794,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABNJV3IABNGGRUHBTDXMGZTRZC6ELANCNFSM4OEHRT7Q
.

Thanks!


[NFT Marketplace] Implement NFT Marketplace on CasperDash Web

Is your feature request related to a problem? Please describe.
As the NFT Holder, I would like to

List my NFT
Buy NFT

Describe the solution you'd like
TBD
Describe alternatives you've considered
N/A
Additional context
N/A

Here is my proposed wireframe: https://app.moqups.com/GuICw1vYeLN7ytRDAVQRvOknDWgbGLP6/view?ui=0
hi @djhahe @hoailinh1210 a @duc-q , please have a look then we can discuss more on Saturday. Thanks.

I will close this ticket because of wrong repo.


get_local.cache is {'LlamaSdpaAttention.forward': []}

@mrwu-mac Hello, when I run the llava_roc.py,  I got the below errors:
File "/controlmllm/task/ROC/llava_roc.py", line 217, in main
    mean_att = torch.cat([att.to(device) for att in attention_maps], 0).mean(0)
RuntimeError: torch.cat(): expected a non-empty list of Tensors.

I find the line 212,
ori_attention_maps = get_local.cache['LlamaSdpaAttention.forward']
get_local.cache['LlamaSdpaAttention.forward'] is empty([])
Can you give some suggestions? Thanks.

Hello, did you install the transformers from https://github.com/mrwu-mac/transformers? If you install the transformers from the official repository, you should ensure the following steps are completed.

First, the LLM attention in your model should be wrapped with the @get_local decorator from the visualizer to extract attention maps. For LLaVA_1.5, it should be in the LlamaSdpaAttention function in the transformers/src/transformers/models/llama/modeling_llama.py file.

Second, in the llava_roc.py file, you should call get_local.activate() before importing your model.

If these steps are followed correctly, the attention map will be stored as a dict in get_local.cache after the model inference. Please be mindful of the dict keys, as they may differ from those we provided. Please feel free to ask any questions if the issue persists.

In addition, in the LlamaSdpaAttention function, you need to obtain the attn_weights instead of the attn_output, and make sure that the attn_weights are not reassigned within the forward function.

@mrwu-mac
Thanks for your reply. I use  your latest code and your transformers library. I have check the items your listed above, it is consistent with your codes. The issue still exists.

I just tried the code we provided again with the reconfigured environment, and it works fine. Can you check if the value of attn_weights in the forward function of LlamaSdpaAttention is normal during model inference?

@mrwu-mac  Thanks for your reply.  I discovered that the reason was that my torch version was lower than 2.1.1, which does not support the sdpa mode in llama attention, and it supports eager mode by default. After updating my torch version,  it can work well.


Effective DataModel when used with Rest API based datasource

When Datagrid is used with common database like data sources, it is common, that receiving total count for paging cost extra one query. When working with REST API datasource it is best practice that response for getting resource collection contains information about total count.
For the purposes of creating query only offset and limit is necessary. The total count is necessary for two reasons. First is to show UI component with list of pages. Second to check if requested page number is not higher that collection maximum.
The problem with current model is, that the order in witch get total count is received cost two calls on Rest API endpoint instead of one. I suggest to move call of getCount() method after getting data. When working with DB, it does not matter if the getCount() call is sooner or later with performance in mind.
If this kind of change is too big BC break, another possibility would be to create interface for data model and enable change of DataModel. One will be more strict in terms of pagination overflow and another less.

Closing in favor of https://github.com/contributte/datagrid/pull/1038


How to add custom styles to an element

💬 Questions and Help
Hi,
I am new to styled-components, and xstyled.  So far, I am enjoying the possibilities of using such tools.  But I was wondering if there is a way to add custom styles to an element (kind of in-line styles)
For example, I have the following code.

const theme = {
  tables: {
    default: css`
      color: red;
    `,
    primary: css`
      color: pink;
    `,
    secondary: css`
      color: purple;
    `
  }
}

const variants = variant({
  // Variants are found in `theme.tables`
  key: 'tables',
  default: 'default'
})

const StyledTable = styled.table`
  ${system}
  ${variants}
`

This code works well, when using the styles from the theme. For example:
  <StyledTable variant="primary>
      // Table code ...
   </StyledTable>

But what if I want to add specific style just for this specific element, is it possible?
Something like:
<StyledTable variant="primary css={css`width: 100%;`}>
  // Table code ...
</StyledTable>

PS: I tried searching online and tried different ways, like style prop, className prop, and adding it as a variant with a function but could not make it work.  Sorry if this is a dumb question.
Thanks

Nevermind,
I was able to add the custom style with a function. Something like:

const StyledTable = styled.table`
  ${system}
  ${variants}
  ${p => p && p.css ? css`${p.css}` : ``}
`

Thanks


devcontainer: Migrate to Debian

While it works fine in VSCode, GitHub Codespaces doesn't support Alpine. How sad.
Hopefully someday this can be reverted!

I'm going to take the imitative to merge this anyway and see what happens. The failing action may be a strange interaction with my fork.

Action passes when pushed to master, that was fun.


Ageing reports

Reports:

[x] 1. how many requests closed by category per week
[x] 2. how many requests closed per week by organization / dept
[x] 3. by category (total requests) for selected period of time
[ ] 4. delegated to each organization / dept (total requests) per week for selected period of time
[x] 5. by category wise daily summery report

This issue separated to issue #39 #40 #41 #42 #43


[c2m] extern return struct by value, potential bug

Hey all, I've been building a proof of concept live-coding system by binding MIR (c2m specifically) with raylib (a gfx/audio/input library) and may have uncovered a bug. The current implementation uses MIR_load_external for all of the raylib functions and works very well until I attempt to call an extern function that returns one of the various raylib structs by value (e.g., Color r = GetColor(0xFF0000FF);).
 I've run this on Mac/Win64/Linux with the same sort of result:
$ ./c2m c2mir-tests/external-ret-by-val.c -eg
ret ptr: 0x7fffc44db4e4, val: 46291618
byval_extern: 89abcdef (-1985229329)
byval_ptr_extern: 89abcdef (-1985229329)
jit result: 46291618<PHONE_NUMBER>)
FAIL

$ ./c2m c2mir-tests/external-ret-by-ptr.c -eg
ret ptr: 0x7fffc7c4be00
byval_extern: 89abcdef (-1985229329)
byval_ptr_extern: 89abcdef (-1985229329)
jit result: 89abcdef (-1985229329)

In my tests return by value works perfectly if the function is local, but when the function is an extern the value of the struct is a memory address.
I've tried to isolate/fix this issue, but it's unclear to me where this issue occurs (AST creation vs AST to MIR vs MIR to machine code). I'd be happy to keep poking at this if it is a good first issue, but I'd probably need a hint to get me started!

In my tests return by value works perfectly if the function is local, but when the function is an extern the value of the struct is a memory address.

c2m is not binary compatible with other C compilers yet.  ABIs on many targets requires to return and pass small structures through registers.   c2m passes and returns structures by address only.  Other C compilers use the same for bigger structures only.
The only way currently to generate ABI compatible code by c2m is to pass and return structures by pointer.  If you can not change function compiled by other C compilers (e.g. it is a library), you need an intermediate function compiled by ABI compatible C compiler.
I'll try to achieve ABI compatibility for c2m before the release but it is not easy task.  ABIs for passing/returning structures might be very complicated.

@vnmakarov hey! thank you for the quick response and information about why this is the way it is. Seems like I might have been a bit too ambitious with thinking this was a minor issue I could fix this myself, haha!
I was able to work around this using codegen to shim these byval function calls on the guest and host side
raylib-host.h
Color *raylib_host_GetColor(int hexValue) {
  byval_Color = GetColor(hexValue);
  return &byval_Color;
}
//...
MIR_load_external(ctx, "_GetColor", raylib_host_GetColor);

raylib.h (as seen by the jit'd code)
extern Color *_GetColor(int hexValue);

// Returns a Color struct from hexadecimal value
Color GetColor(int hexValue) {
  return *_GetColor(hexValue);
}

not ideal for production level code, but this is a POC and this unblocks me. Thanks again!


tests(cts): update send_event/send_events tests adding timestamp

Docs: https://github.com/algolia/algoliasearch-client-specs/pull/31/files.
Here is an example on python: https://github.com/algolia/algoliasearch-client-python/pull/433/files.
Goal: make sure developers can set the event timestamp when sending events using send_event/send_events.

Users can send timeStamp with the InsightsEvent class which is in the signature of every sendEvents method
https://github.com/algolia/algoliasearch-client-java-2/blob/d608948f081987ecc6f903e5ede44674db1b4692/algoliasearch-core/src/main/java/com/algolia/search/InsightsClient.java#L140
and
https://github.com/algolia/algoliasearch-client-java-2/blob/d608948f081987ecc6f903e5ede44674db1b4692/algoliasearch-core/src/main/java/com/algolia/search/models/insights/InsightsEvent.java#L14


Question about Nevigator fouction such as popUtil and push and RemoveUtil.

Steps to Reproduce

this problem not only occur on my application. when i use popUtil or pushAndRemoveUntil we will pop to last page .Does it design for this?

use popUtil or pushAndRemoveUntil
code like
  void _logout() {   Navigator.popUntil(context, ModalRoute.withName('/login')); }
this is
not pop to my page which i want. some time just pop one page .

And i see the code is
 static void popUntil(BuildContext context, RoutePredicate predicate) {
    Navigator.of(context).popUntil(predicate);
  }

void popUntil(RoutePredicate predicate) {
    while (!predicate(_history.last))
      pop();
  }

@optionalTypeArgs
  Future<T> pushAndRemoveUntil<T extends Object>(Route<T> newRoute, RoutePredicate predicate) {
    assert(!_debugLocked);
    assert(() { _debugLocked = true; return true; }());
    final List<Route<dynamic>> removedRoutes = <Route<dynamic>>[];
    while (_history.isNotEmpty && !predicate(_history.last)) {
      final Route<dynamic> removedRoute = _history.removeLast();
      assert(removedRoute != null && removedRoute._navigator == this);
      assert(removedRoute.overlayEntries.isNotEmpty);
      removedRoutes.add(removedRoute);
    }
    assert(newRoute._navigator == null);
    assert(newRoute.overlayEntries.isEmpty);
    final Route<dynamic> oldRoute = _history.isNotEmpty ? _history.last : null;
    newRoute._navigator = this;
    newRoute.install(_currentOverlayEntry);
    _history.add(newRoute);
    newRoute.didPush().whenCompleteOrCancel(() {
      if (mounted) {
        for (Route<dynamic> route in removedRoutes)
          route.dispose();
      }
    });
    newRoute.didChangeNext(null);
    if (oldRoute != null)
      oldRoute.didChangeNext(newRoute);
    for (NavigatorObserver observer in widget.observers) {
      observer.didPush(newRoute, oldRoute);
      for (Route<dynamic> removedRoute in removedRoutes)
        observer.didRemove(removedRoute, oldRoute);
    }
    assert(() { _debugLocked = false; return true; }());
    _cancelActivePointers();
    return newRoute.popped;
  }

both of them is used
!predicate(_history.last)

so is it the problem cause the porblem i can't pop the page diractly and accuracy.?
Thanks for you answer.~
Logs

[✓] Flutter (Channel dev, v0.9.2, on Mac OS X 10.12.6 16G1314, locale zh-Hans-CN)
    • Flutter version 0.9.2 at /Users/changfeifan/flutter
    • Framework revision 85b4670b2a (35 hours ago), 2018-09-19 14:59:23 -0700
    • Engine revision 2e8e96fad1
    • Dart version 2.1.0-dev.4.0.flutter-4eb879133a

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/changfeifan/Library/Android/sdk
    • Android NDK at /Users/changfeifan/Library/Android/sdk/ndk-bundle
    • Platform android-28, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)
    • All Android licenses accepted.

[!] iOS toolchain - develop for iOS devices (Xcode 9.2)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 9.2, Build version 9C40b
    ✗ ideviceinstaller is not installed; this is used to discover connected iOS devices.
      To install, run:
        brew install --HEAD libimobiledevice
        brew install ideviceinstaller
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 28.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1024-b01)

[✓] IntelliJ IDEA Ultimate Edition (version 2017.3.4)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 26.0.1
    • Dart plugin version 173.4700

[✓] Connected devices (1 available)
    • iPhone X • 3B71A8B3-7F15-45EE-B908-A564793F76B9 • ios • iOS 11.2 (simulator)

Please consider asking support questions in one of the other channels listed at http://flutter.io/support .

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


How can i start using this?

I have never worked with apis so i dont know how to set it up? can you tell me step by step?

You can start looking the sample project


Currently selected animation is broken

"Reset" Animation is broken after updating to v1.0.2. All steps will be shown as currently selected (height and width does not reset, background and bordercolor does somehow) after being selected once.
<StepIndicator
      stepCount={stepCount}
      currentPosition={currentPage}
      onPress={onStepPress}
/>

v1.0.2:

Also the whole Step-Indicator seems to ignore parent containerstyles now as he is misaligned after the update.
v.0.x:

cc: @peterpme

Fixed in 1.0.3


ci(syntax): fix deprecated actions syntax. Fixes #6

Description
Remove usage of set-output on the Github Actions Workflows
Describe what you did and why.
I followed the specs on the issue with the help wanted label
Related issue (if any): fixes #6
Checklist

[x] I have followed this repository's contributing guidelines.
[x] I will adhere to the project's code of conduct.

Additional information

Anything else?

@all-contributors add @altmas5 for infra


Magic link button is not aligned  in multi option authentication windows.

Describe the issue:
Magic link button is not aligned  in multi option authentication windows.

How to reproduce:

login to management console
Configure application
Configure Multi option authentication
Access the application

Expected behavior:
Login option UI button should be aligned properly
Environment information (Please complete the following information; remove  any unnecessary fields) :

Product Version: IS 6.0.0-beta
OS: Mac
Database: MSSQL
Userstore: JDBC

Optional Fields
Related issues:

Suggested labels:

This issue is fixed by the following PR - https://github.com/wso2/identity-apps/pull/3261


Code formatting? Perhaps black to match xgcm

I'm suggesting here something similar to https://github.com/xgcm/xgcm/pull/131

Definitely needed!
@jbusecke recently polished up all of the CI for xgcm. Maybe he can do some of the same for xrft? Julius, do you use xrft? It's very important to those of us who do spectral stuff.

Nope have not used it, but I can format it for sure!

Should I wait for #112 before starting this? I think it will make all the diffs a mess.

#112 is merged ;)


Shades of Morton - diary string

🐛 Bug Report
Currently the firemaking diary boost says it is for the hard morytania diary however it's obtained via elite diary
Brought up in testing by Krisk

Fixed but not commited


Upgrade to connect-redis 7 and update other dependencies

Followed upgrade notes here:
https://github.com/tj/connect-redis/releases/tag/v7.0.0

Well that didn't work 🤔


v1.1.4 rollup into master

Coverage increased (+1.4%) to 77.336% when pulling b5fdfa2ff35982d11029328b35859305e81eba81 on v1.x into d13f2c25b0779f6d4734ec0c46b856f023d7f23e on master.


Docu: link customization contain invalid example

In the link customization docu there is the line:
// Also usable: _diagram.Options.Links.DefaultLinkComponent = typeof(ThickLink);
this doesnt work and should be:
// Also usable: _diagram.Options.Links.DefaultLinkComponent = typeof(ThickLinkWidget);
( maybe you should also mention the model version )
_diagram.Options.Links.Factory = ( diagram, port ) => new ThickLink( port );

Hello,
You are right! Thank you.


ChildAction shoudn't reset _cacheKey for OutputCacheFilter

This wasn't raising awareness in Orchard community as the official code base does not use Child Actions (they use shapes).
Previously there is reentrancy-prevention code in OnResultExecuted to filter out Child Actions so that OnResultExecuted only gets executed once per request and only for the parent Action. However, this reentrancy-prevention code is being incorrectly placed in the try-catch block, that the finally-block can get executed more than once if parent Action includes any Child Action. This wasn't an issue until commit 117dd09f (first included in release 1.10) which resets _cacheKey in that finally-block via ReleaseCacheKeyLock. Now for every request that uses Child Actions, the finally block will be executed at least once during Child Action's OnResultExecuted, leaving the _cacheKey as null. Later after all Child Actions finish execution, the parent Action's OnResultExecuted will now see a _cacheKey of null, thus causing NRE in captureStream.Captured event handling code.

That is some seriously nice problem analysis and troubleshooting!
I knew @sebastienros shouldn't have messed around with my implementation... ;)
This looks solid to me, but can you retarget on 1.10.x please?

Hi @DanielStolt
Thanks, and thanks for the suggestion. PR #6726 is created. Closing this one.


Unregister entity UI seems to be broken when there are no entities

If we don't get any entities from the api/catalog/entities API, in that case we get an empty array. Now, in the UnregisterEntityDialog.tsx when we try to unregister entity we don't have any entity but still we show the UI which displays the list of entities, which seems to be broken. This results in

 with a bullet but no text content inside it.
This is happening because we are making the following check in our UnregisterEntityDialog component
{entities ? JSX : null}, here entities will evaluate to true even if the array is empty because Boolean([]) is true. Instead we should check for length of the array.
Expected Behavior
We should not show the UI which shows the list of entities because that results in li with only a bullet and nothing else after that.
Current Behavior

Possible Solution
We can check the length of array instead checking the existence of array.
Steps to Reproduce

Go to http://localhost:3000/catalog/Component/default:playback-order/ci-cd
Select the menu with three dots from top right.
Select "Unregister entity" from dropdown.
You will see the li with bullet but no content inside li because there are no entities in entities array.

Context
I am looking to contribute to open-source community and I find this project very interesting.
Your Environment

NodeJS Version (v12): v14.13.1
Operating System and Version (e.g. Ubuntu 14.04): macOS Catalina 10.15.7 (19H2)
Browser Information: Version 86.0.4240.80 (Official Build) (x86_64)

I see it doesn't even list itself either 😬
So you wanna tackle this? 😀

I see it doesn't even list itself either 😬
So you wanna tackle this? 😀

I would love to raise a PR for this

Done.


🎉 1.0.0

ℹ About this release

Version: 1.0.0
Type: major
Last Release: -
Commits to merge: 31 [?]

:tada: This PR is included in version 1.0.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release
v1.0.0

Your semantic-release bot :package::rocket:


straight--build-compile: properly set load-path

Previous method involved looking up each package's dependencies.
It did not account for local-repo names and transitive dependencies.
Now we just recursively add straight's build dir to the load-path
when byte-compiling. This should cover all cases.

Hmmm... that seems like it would almost always work, but doesn't it technically make the environment a bit nondeterministic on account of random old things lying around in ~/.emacs.d/straight/build could be added to the load-path?


Timeline mobile view fixed

./src/App.js
Module not found: Can't resolve './components/Nav/Navbar' in 'C:\Users\ASUS\Desktop\dsc-webathon\src'


Auto create index pages for guides

https://joshuatz.com/posts/2019/gatsby-automatic-directory-listing-pages-beginners-attempt/
related to breadcrumbs ( #52  )
For example, if we have
guides/cs-plus/stats.md
navigating to the url guides/cs-plus/
should list out all the majors
potentially

lol, related to #71  , index pages have different slugs so it makes calculating the github index page harder

after considering for 10 minutes, its not worht polluting our codebase with more complexity. there wont be that many index pages we have to make, and it will allow us to give better names and everything if we can customize them in markdown


Future Plans about AT command generation

I am currently writing a similar crate to interface with AT modules. I see that you have actually got something talking to a module which is far more progressed than I am.
Where my implementation differs however is that I am using traits for both creating and parsing the commands as well as sending and receiving data.
My main question is if you had any thoughts on how you want to generate the AT commands? I have created a macro that will expand an enum out into a send command, state and received data enums. These are defined by:
#[atat("\n")]
        enum TelitCommand {
            AT (None,(u8,u16), ()),
            AT_ (None,(u8,u16), (i64)),
            AT__ (None,(&'b[u8]), (u32)),
        }

This expands out to being able to send AT=u8,u16 and returns an OK(()), AT?u8,u16 and returns an i64 and AT?=[u8] and returns a u32.
The state at the moment is that the crate can create the command and send it to a generic buffer. I have started the parse side and that will take a generic buffer and return the parsed data.
I also plan to have a straight command pass through for unusual commands.

Cool.
This crate currently works really great for AT commands (request, response and unsolicited responses), but lacks a bit when you want to use it in a socket mode, or pure data mode.
This is what i am working on currently though.
I am still refining the traits of this crate a bit, to be able to do all that i want it to.
 You can have a look in tests.rs for a simple usage example with just AT Commands..
Further more this type of interface allows for extended usages like:
#[derive(Debug, Clone)]
pub enum ResponseType {
    SingleSolicited(Response),
    // MultiSolicited(Vec<Response, heapless::consts::U10>),
    Unsolicited(UnsolicitedResponse),
    ExtendedData(Packet),
    None,
}

#[derive(Debug, Clone)]
pub enum RequestType {
    Cmd(Command),
    Data(Vec<u8, consts::U1024>),
    ExtendedData(Packet),
}

impl ATRequestType for RequestType {
    type Command = Command;

    fn try_get_cmd(self) -> Option<Self::Command> {
        match self {
            RequestType::Cmd(c) => Some(c),
            RequestType::ExtendedData(_p) => {
                // Attempt to extract any AT Cmd
                None
            }
            _ => None
        }
    }

    fn get_bytes(&self) -> &str {
        match self {
            RequestType::Cmd(c) => c.get_cmd().as_str(),
            RequestType::ExtendedData(p) => {
                p.pack().as_str()
            }
            _ => ""
        }
    }
}

impl ATCommandInterface for Command {
    type Response = ResponseType;
    ...
}

This code currently does not compile though, as i am battling the borrowchecker regarding ATRequestType
I am working actively on this every day though, and if you think it looks good, I would be happy to work out some collaboration..
My hope is to make a crate that can be widely used for AT devices in the rust community, although there is still a lot of potential optimizations..
My goal is to have it fully no_std, and heapless (maybe an alloc feature gate eventually for Box optimizations).

Also you can have a look at https://github.com/BlackbirdHQ/ublox-short-range-rs for a real life implementation.
It comes with a working linux example in the examples folder.

From what I have seen, I think some of your ideas are better than mine.
I still think it should be possible to automatically generate 80% of the commands just by describing the command, inputs and output in a enum or struct. Having some specific types to deal with those odd cases is a good idea.
For me, the end goal is being able to send a UPD or TCP packet without having to worry about all the fiddly bits of AT modules.
The other use case is a lot of modules also have GPS or other location services that can be extracted. Making that simple would be nice.
FWIIW, here is the output of the macro. Might help with your borrowchecker issues.
# [derive (Debug, Clone, Copy)]
 enum TelitCommand
{ AT, AT_, AT__, _CGI, UBD,
  RawCommandPassthrough
}

use ufmt :: uwrite ;

#[derive (Debug)]
enum TelitCommandCreate < 'b >
{ AT (u8, u16), AT_ (u8, u16), AT__ (),
RawCommandPassthrough (& 'b [u8]), }

impl < 'a > ATATCreate < 'a > for TelitCommandCreate < '_ >
{
    type ATATState = TelitCommand ;
    type Buffer = & 'a mut Cursor < [u8] > ;
    fn create_command (& self, buffer_out : Self :: Buffer) -> Result <TelitCommand, ATATError >
    {
        match self
        {
            Self :: AT (element_0, element_1) =>
            {
                uwrite!(buffer_out, "AT+AT={}{}\n", element_0, element_1).map_err (| _e | ATATError :: CreateError) ? ;
               Ok (TelitCommand :: AT)
            }, Self :: AT_ (element_0, element_1) =>
            {
                uwrite!(buffer_out, "AT+AT?{}{}\n", element_0, element_1) .map_err (| _e | ATATError :: CreateError) ? ;
               Ok(TelitCommand :: AT_)
            }, Self :: AT__ () =>
            {
                uwrite!(buffer_out, "AT+AT=?\n",) . map_err(| _e | ATATError :: CreateError) ? ;
                Ok(TelitCommand :: AT__)
            }, Self :: RawCommandPassthrough (data) =>
            {
                for i in data . iter ()
                {
                    uwrite ! (buffer_out, "{}", i) . map_err
                    (| _e | ATATError :: CreateError) ? ;
                } Ok (TelitCommand :: RawCommandPassthrough)
            }, _ => Err (ATATError :: UnknownCommandError)
        }
    }
}
enum TelitCommandParse { AT (), AT_ (), AT__ (), }

 impl < 'a > ATATParse <'a > for TelitCommandParse
{
    type ATATState = TelitCommand ;
     type Buffer = & 'a mut Cursor < [u8] > ;
    fn parse_response (state : TelitCommand, buffer_in : Self :: Buffer) ->
    Result < Self, ATATError >
    {
        match state
        {
            TelitCommand :: AT => { Err (ATATError :: UnknownCommandError) },
            TelitCommand :: AT_ => { Err (ATATError :: UnknownCommandError) },
            TelitCommand :: AT__ =>
            { Err (ATATError :: UnknownCommandError) }, _ => Err
            (ATATError :: UnknownCommandError)
        }
    }
}

I'll post my code to github anyway and see if we can agree on a common direction.


Fix flush_cache issues in yum_package

Fixes #4691. I hope.

yeah i think delete the two TODO lines and delete the else clause entirely.
my bet is that doing so doesn't cause any regression.
if it does cause a regression, it'll be way less bad than the regression we're currently suffering under.
if we get that regression, then we can pick the best way to fix it after we see it.

I don't think we can delete the else clause as we have to make it a hash if if it's not. But I'll nuke the todo.

When I change this code it fixes it, but monkey patching it from a library doesn't seem to... not sure why. Still playing.

OK @lamont-granquist I don't think I can monkey patch that using property keyword... property does magic...  so either I need to get a version cut with this ASAP or I need help with magic above my head :)

uh hrm, yeah i suspect property does do lots of magic.
dunno what to tell you about getting new versions cut, i think we're still about 2 weeks-ish away from the next scheduled release based on when the last one went out.  beat on your support contract a bit and you might make it happen tho.  although we've got a bad outstanding regression in master i just cut today #5257, but i don't think it'll be anything insurmountable to fix, just another bug.

chef_gem is evil, we don't use it so not worried. Installing gems via gem on prod systems is asinine.
Any ideas on how to monkey patch wahtever methods are being jammed into the YumPackage class?  ANd I CC'd you on the ZenDesk ticket already.

so we don't document using this property as anything other than a hash or an array.  i don't think boolean true/false have been an option?
although i don't mind adding that -- but i thought that else clause was intended to only catch the empty-hash '{}' case and attempt to coerce it into returning the same value...

and no, my suggestion would just be to open the class and copypasta this one 'line' into it...
its possible coerce arguments get pushed into an array and you need to blow away the array?

Chef::Resource::YumPackage.properties.delete(:flush_cache)?

Haha I tried something simialr, but it doesn't work yet:
  Chef::Resource::YumPackage.properties[:flush_cache][:coerce] = proc { |v|
          if v.is_a?(Array)
            v.each_with_object({}) { |arg, obj| obj[arg] = true }
          elsif v.any?
            v
          else
            { before: v, after: v}
          end
          }

yeah i'd try just nuking the property and then using the DSL to rebuild it all...

Ha! This does it:
  opts = Chef::Resource::YumPackage.properties[:flush_cache].options
  opts[:coerce] = proc { |v|
          if v.is_a?(Array)
            v.each_with_object({}) { |arg, obj| obj[arg] = true }
          elsif v.any?
            v
          else
            { before: v, after: v}
          end
          }
  Chef::Resource::YumPackage.properties[:flush_cache] = opts

delete doesn't work:
chef (12.13.37)> Chef::Resource::YumPackage.properties.delete(:flush_cache)
 => #<Chef::Property:0x00000000e03b48 @options={:default=>{:before=>false, :after=>false}, :coerce=>#<Proc:0x00000000e04598@/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.13.37/lib/chef/resource/yum_package.rb:30>, :instance_variable_name=>:@flush_cache, :name=>:flush_cache, :declared_in=>Chef::Resource::YumPackage, :is=>Hash}>

chef (12.13.37)> Chef::Resource::YumPackage.properties[:flush_cache]
 => #<Chef::Property:0x00000000e03b48 @options={:default=>{:before=>false, :after=>false}, :coerce=>#<Proc:0x00000000e04598@/opt/chef/embedded/lib/ruby/gems/2.1.0/gems/chef-12.13.37/lib/chef/resource/yum_package.rb:30>, :instance_variable_name=>:@flush_cache, :name=>:flush_cache, :declared_in=>Chef::Resource::YumPackage, :is=>Hash}>

OK this seems to work....
  Chef::Log.info('Monkey-patching yum_package resource')
  opts = Chef::Resource::YumPackage.properties[:flush_cache].options
  opts[:coerce] = proc { |v|
          if v.is_a?(Array)
            v.each_with_object({}) { |arg, obj| obj[arg] = true }
          elsif v.any?
            v
          else
            { before: v, after: v}
          end
          }
  Chef::Resource::YumPackage.property(:flush_cache, opts)

If I specify a type, the validator becomes ... is => [Hash, Hash] which is weird.

OK, @lamont-granquist pushing that out to the 12.13.37 hosts. We'll see how that goes. You OK merging this meantime?

replaced {} with do/end cause... style.

I just figured out the actual problem!!!!
On the tier effected one of the earliest packages was setting 'flush_cache [:before]` - and since the bug was that it was additive and not per-package... that's what fucked us.

wtf is this:
/home/travis/build/chef/chef/lib/chef/resource/yum_package.rb:31:in `proc': tried to create Proc object without a block (ArgumentError)

that's not true.

whoah it wasn't per-package?  so it like updated the default value more or less?  yikes...

yeah and i was just gonna suggest do..end, its different in subtle and annoying ways...

so do..end breaks things. I'll go back to {} because...  That's better. :)

that explains why i couldn't replicate either, nobody reported that you had to call flush_cache once and then it flushed the cache every time after that...

wasn't exactly easy to figure out :) @joshuamiller01 mentioned it was only happening on one of our tiers, so I grepped the code-base for flush_cache and then saw it was only in that cookbook, and that combined with the "we're appending, which seems odd" TODO comment, made it all click.

OK, @lamont-granquist all the tests pass.