Error with last update changing opn to open

I pulled the last updated where you change "opn" to "open" but npm on my machine was not updated and could not find module open
App threw an error during load
Error: Cannot find module 'open'
I have installed open "npm install open" and now it's working but you may wish to warn users

Thanks for your kind report. Usually, it should be installed by npm install after git pull but sometimes it could not be installed properly. I don't know why, but I'll add this into README.md


[BUG]install failed on task [platform : build bcg729]

Describe the bug
ansible was stopped to install LibreSBC
To Reproduce

Steps to reproduce the behavior
tried to install on debian 10.11 it's failed as well with the same reason failed to build bcg729

Log & Screenshots

please find the log in the attached file below:
libreSBC_install_failed.log

Additional context

Ansible server:
root@ansible:~/libresbc/build/ansible/ ansible --version
ansible [core 2.11.6]
config file = /root/libresbc/build/ansible/ansible.cfg
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3/dist-packages/ansible
ansible collection location = /root/.ansible/collections:/usr/share/ansible/collections
executable location = /usr/bin/ansible
python version = 3.9.2 (default, Feb 28 2021, 17:03:44) [GCC 10.2.1 20210110]
jinja version = 2.11.3
libyaml = True

LibreSBC server:
Distributor ID: Debian
Description:    Debian GNU/Linux 11 (bullseye)
Release:        11
Codename:       bullseye
root@libresbc-id:  python --version
Python 2.7.18
root@libresbc-id: python3 --version
Python 3.9.2

issue resolved after installing cmake package

thanks @bcahyadi, I will add task for install cmake soon


graphics: Particle lib

Inspired by https://github.com/pixijs/pixi-particles

I don't know but examples/particles should be enough.


spin + dapr demo

#121 adds the default executor to the spin shim to allow it run with Linux containers side-by-side in a pod. Now we need to add a demo for Spin + Dapr integration.
@0xE282B0 are you interested in taking this issue?

Sure you can assign me.
I think a simple demo could be using the Kubernetes Events to trigger a Spin application that writes to Spin's Key-Value Store.
What other demos would you like to see? Maybe pub/sub with rabitmq or nats?

Sounds good to me!

@salaboy FYI


[rclc_lifecycle, Rolling] Segfault in example_lifecycle_node

Calling ros2 lifecycle get to the current rolling example_lifecycle_node results in a segfault.
Calling ros2 lifecycle set to the current rolling example_lifecycle_node stalls.

This one is weird, as it keeps disappearing when I try to debug with gcc.
One suspicion of mine is that the context is not properly passed to the service, though. @JanStaschulat while looking at this, it seems that we don't have any tests for service with context?!

@norro , there is a test case with service with context:
https://github.com/ros2/rclc/blob/27b4d4fc30149339da50376acd08893141748aa5/rclc/test/rclc/test_executor.cpp#L2566

But indeed, the unit test does not check if the context was passed correctly:
https://github.com/ros2/rclc/blob/27b4d4fc30149339da50376acd08893141748aa5/rclc/test/rclc/test_executor.cpp#L2617
there it should have checked srv1_id (which is assigned the value of the context).
https://github.com/ros2/rclc/blob/27b4d4fc30149339da50376acd08893141748aa5/rclc/test/rclc/test_executor.cpp#L325
We need to update this unit test!

While this is true, this is not the root cause for the segfault.
I am rather passing a context that doesn't remain in scope.

hmm, then I would look into the service callback function, if the a test for NULL pointer is done after the conversion of the context.

Was able to fix the segfault, get state and get available states services work as expected.
Change state service also works as expected when called via ros2 service, e.g., ros2 service call /rclc/lifecycle_node/change_state lifecycle_msgs/ChangeState "{transition: {id: 1, label: configure}}". It still stalls, when called via ros2 lifecycle set ..., but this seems to be a different issue.


Wrong Typescript type for ErrorCode

Description
I console log an Adapty error and get this object:
{
    "adaptyCode": 1006,
    "localizedDescription": "Product purchase failed"
    "message": "#undefined (1006): Product purchase failed"
}

adaptyCode seems to be one of the keys of const ErrorCode declared in node_modules/react-native-adapty/lib/dist/types/error.d.ts
But the type is defined as such :
export declare type ErrorCode = typeof ErrorCode[keyof typeof ErrorCode];

which, according to my editor, translates to (see screenshot):

It seems to me that the correct type should be:
export declare type ErrorCode = keyof typeof ErrorCode;

Is that correct?
Version
v2.4.2
What platforms are you seeing the problem on?
iOS, Android
System info
System:
    OS: macOS 13.0.1
    CPU: (10) arm64 Apple M1 Pro
    Memory: 157.39 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.16.0 - ~/.nvm/versions/node/v16.16.0/bin/node
    Yarn: 1.22.19 - ~/.nvm/versions/node/v16.16.0/bin/yarn
    npm: 8.11.0 - ~/.nvm/versions/node/v16.16.0/bin/npm
    Watchman: 2<IP_ADDRESS> - /opt/homebrew/bin/watchman
  Managers:
    CocoaPods: 1.11.3 - /Users/kamiranoff/.rbenv/shims/pod
  SDKs:
    iOS SDK:
      Platforms: DriverKit 22.1, iOS 16.1, macOS 13.0, tvOS 16.1, watchOS 9.1
    Android SDK: Not Found
  IDEs:
    Android Studio: Electric Eel 2022.1.1 Patch 2 Electric Eel 2022.1.1 Patch 2
    Xcode: 14.1/14B47b - /usr/bin/xcodebuild
  Languages:
    Java: 18.0.2 - /usr/bin/javac
  npmPackages:
    @react-native-community/cli: Not Found
    react: 18.1.0 => 18.1.0
    react-native: 0.70.6 => 0.70.6
    react-native-macos: Not Found
  npmGlobalPackages:
    *react-native*: Not Found

Also on a side note, I try to omit the error when a user discards the IOS modal without completing a purchase. Is 1006 the proper error code for that? I don't see any specific error like user cancelled or something like this. I can also open another issue if you would like.

Oh, that's right! I've messed with what I've wanted there
I'm to change it to keyof, and probably should add another field with that written code, so users can choose what they want
Thank you for noticing that!

Great library btw!

@kamiranoff, please check v2.4.3 for the fix. I believe the problem should be gone.
Let me dive into second part of your question a little later today

Thank you for the new issue! Have you tried this one?

I tried and it's all good! Thanks for the quick fix!


Unable to run regexploit in Windows machine with python

And the error message is what?

I can run it on Linux OS. For Windows,

Running regexploit from that directory won't work. Try it two levels up and then python3 regexploit/bin/regexploit.py or better: install the package.


v10 Upgrade Handler

Context and purpose of the change
Upgrade handler for v10 upgrade
Brief Changelog

Migrated tendermint consensus params [source]
Migrated channel capability from stakeibc → icacontroller [source]
Pruned expired tendermint clients [source]
Migrated icacallback proto from google proto (deprecated) to cosmos proto
Reduced STRD staking rewards. Double check me on these numbers!!
Set MinInitialDepositRatio
Removed an unnecessary setup call from past unit tests
Cleaned up makefile and docs
Added localhost client for ibc-go v7.1

Should I re-review this @sampocs?


Hello, do you know how to generate the  pickle file for miniImagenet?

Hello, do you know how to generate the  pickle file for miniImagenet?

I don't use pickle in my project. You may refer to my dataloader if you don't need to use pickle. Otherwise, you may refer to the official documents for pickle.


.NET 5 Source Generator support

Hi,
Is there a plan to implement .NET 5 Source Generator support?

Closing as duplicate of #3089

Unofficial generator: https://www.nuget.org/packages/H.NSwag.Generator/


Konflux update ttest1

Pipelines as Code configuration proposal
To start the PipelineRun, add a new comment with content /ok-to-test
For more detailed information about running a PipelineRun, please refer to Pipelines as Code documentation Running the PipelineRun
To customize the proposed PipelineRuns after merge, please refer to Build Pipeline customization

Pipelines as Code CI has failed.There was an error creating the PipelineRun: test1-on-pull-request-
creating pipelinerun test1-on-pull-request- in namespace rcerven-test has failed.
Tekton Controller has reported this error: the namespace of the provided object does not match the namespace sent on the request

Pipelines as Code CI/ttest1-on-pull-request has failed.
Namespace: rcerven-test
PipelineRun: ttest1-on-pull-request-vsrkb

Task Statuses:

StatusDurationName

✅ Succeeded
6 seconds
init

✅ Succeeded
23 seconds
clone-repository

❌ Failed
8 seconds
build-container

✅ Succeeded
9 seconds
show-summary

Failure snippet:
task build-container has the status "TaskRunCancelled":
TaskRun "ttest1-on-pull-request-vsrkb-build-container" was cancelled. TaskRun cancelled as the PipelineRun it belongs to has been cancelled.


allow library to specify cts buffer cell for openroad

Adds ability for library to specify openroad cts buffer
Fills in clkbuf and buf section of sky130

@nmoroze on line 220, the openroad driver copies in the values in openroad_cts_clock_buffer to cts_clock_buffer (this is a single entry not a list, the tcl driver was fixed to ensure a single entry is used instead of a list.)

@nmoroze yes that is the correct priority order. I need to rewrite the openroad driver to pull more defaults from the pdk and mainlib


B-21667 B-21374 I-13550 INT

Agility Issue
Agility ticket B-21667
Agility ticket B-21374
Summary
B-21374 fix
A mysterious 0 value was appearing on the allowance details in the case of 0 dependents under 12 and 0 over 12. Issue was written up for it, fix was just adding a > 0 for the each of the checks for info?.dependentsTwelveAndOver || info?.dependentsUnderTwelve in src/components/Office/DefinitionLists/AllowancesList.jsx.
B-21667 fix
As part of troubleshooting the above, noticed that the Unaccompanied Baggage Allowance field was not appearing on the Allowance section. Needed to update ubAllowance to unaccompaniedBaggageAllowance, after changing that variable as part of B-21487, which I have merged into my B-21667 branch.
How to test

Login as a customer, creating a UB shipment with the UB FF turned on, selecting no dependents
Log in as an SC and view the Allowances section for the move.
Check that the DB has 0 values for the dependents under 12 and dependents 12 and over.
Verify that you do not see the 0 just hanging out in the dependents section
Should NOT see this 0:

Check that you have a non-zero value in the UB allowance column of the order entitlement
Verify that you see the Unaccompanied Baggage Allowance field in the Allowances section with the UB allowance value.

Warnings

:warning:
This PR does not include changes to unit tests, even though it affects app code.

  Generated by :no_entry_sign: dangerJS against 413d5c91330131d16e849c61293192b7fead8efc

The 0 value seems to be working for me.


Bug in FireStore

First of all thank you Flutter team for such an amazing Platform.
I dug into FireStore and discovered that it is creating a a new instance everytime Firestore.instance is called
==============================buggy code================================
static Firestore get instance => Firestore();
==============================buggy code================================
First i thought it was correct but then i wrote a test to verify it
==============================TEST CODE============================
void main() {
// CREATE TWO INSTANCE
Fire.instance;
Fire.instance;
}
class Fire {
static Fire get instance => Fire();
Fire.();
factory Fire() {
print("fire");
return Fire.();
}
}
==============================TEST CODE============================
=============Output=================
fire
fire
=============Output=================
This shows it creates a new instance every time Firestore.instance is called .I think this is not the expected behaviour,
Thanks in advance

I forgot to tell the fix
replace  static Firestore get instance => Firestore();
with   static Firestore get instance = Firestore();

Hi @Chetan11-dev
for what I can see the issue is related to a FlutterFire plugin,
please open the issue in the dedicated github.
Closing, as this isn't an issue with Flutter itself,
if you disagree please write in the comments and I will reopen it
thank you


Add VxLAN Support

Hi,
This is a feature request. :)
I see we have a lot of encapsulations supported, but not VxLAN. Actually VxLAN is so a common encapsulation in data centers. Basically we will add the OUTER SMAC, OUTER DMAC, OUTER IP SRC, OUTER IP DST, OUTER SPORT, OUTER DPORT (4789), OUTER PROTO (UDP), VNID, and VXLAN FLAGS (as plus) for egress, and remove this headers for ingress.
Most of the fields can be made to be configurable, just like INNER frames. In my case, my traffic is 100% VxLAN, so I did a very hacky implementation just to meet my deadline:
https://github.com/yicwang/P4TG/commit/b6553b2eb3418314a49ec81c8bcfd59f7b0831e3
Only challenge is we have to deal with the checksum correctly.
I am very happy to contribute a formal VxLAN encap/decap implementation when I've got some time.
Thanks very much!
Regards,
Yichen

Hi,
good idea. I just looked at the VxLAN RFC and it seems reasonable to support it.
Thanks for the preliminary implementation!
I'd like to implement it as with the other encapsulation methods, i.e., the generated packet is already a VxLAN packet and the dataplane rewrites its headers.
Could you explain the "remove this header for ingress" part? Is this for the "analyze" mode, i.e., when P4TG only forwards traffic, or also for the generation mode?
Best
Steffen

Hi Steffen,
Yes, generated and rewrite is a better idea!
It is for analyzing. As in today's ingress code, we do parse out all the encapsulations (VLAN/QinQ/MPLS) because we want to see the actual UDP payload with the P4TG header. Same thing that is needed for VxLAN as well. For VxLAN it is tricky because you will need to parse more layers to reach the final payload. Something like:
    state parse_ethernet {
        pkt.extract(hdr.ethernet);
        transition select(hdr.ethernet.ether_type) {
            ETHERTYPE_IPV4 : parse_ipv4;
            ETHERTYPE_ARP: parse_arp;
            default : reject;
        }
    }

    state parse_ipv4 {
        pkt.extract(hdr.ipv4);
        transition select(hdr.ipv4.protocol) {
            IP_PROTOCOL_TCP : parse_tcp;
            IP_PROTOCOL_UDP : parse_udp;
            default : reject;
        }
    }

    state parse_udp {
        pkt.extract(hdr.udp);
        transition select(hdr.udp.dst_port) {
            UDP_PORT_VXLAN: parse_vxlan;
            default: accept;
        }
    }

    state parse_vxlan {
        pkt.extract(hdr.vxlan);
        transition parse_inner_ethernet;
    }

    state parse_inner_ethernet {
        pkt.extract(hdr.inner_ethernet);
        transition select(hdr.inner_ethernet.ether_type) {
            ETHERTYPE_IPV4 : parse_inner_ipv4;
            ETHERTYPE_IPV6 : parse_inner_ipv6;
            default: reject;
        }
    }

    state parse_inner_ipv4 {
        pkt.extract(hdr.inner_ipv4);
        transition select(hdr.inner_ipv4.protocol) {
            IP_PROTOCOL_TCP : parse_inner_tcp;
            IP_PROTOCOL_UDP : parse_inner_udp;
            default : reject;
        }
    }

    state parse_inner_udp {
        pkt.extract(hdr.inner_udp);
        transition accept;
    }

Regards,
Yichen

Ah okay, gotcha.
Its on the list, should not take too long 👍🏼

A first version with VxLAN support is available at acf07de on the VxLAN branch.

It is possible to combine VxLAN tunnel with all available encapsulations (VLAN, QinQ, MPLS).
The outer UDP checksum is set to zero as recommended in RFC 7348, but the inner UDP checksum (from the P4TG header) is still updated correctly.
Would be great if you could test it if it works on your side too.

You got this done so fast... The original controller crashed with my VxLAN P4 code:
[2024-03-07T23:27:25Z INFO  p4tg_controller::core::traffic_gen] Calculated traffic generation for stream #1. #1 packets per 8352 ns. Rate: 1 Gbps. Accuracy: 100.00%.
thread 'tokio-runtime-worker' panicked at src/core/traffic_gen.rs:511:59:
called Option::unwrap() on a None value
, and not sure what was the problem. Was debugging that and saw your new feature already released, so I gave it a try.
So I loaded the controller, initially the "settings" page is not loading in Chrome. So I changed to Firefox, and it loaded fine. The feature works as expected! Thanks a lot!
During testing, I found another good thing to have, will open other ticket.
Regards,
Yichen

Great to hear!
The blank settings page is probably due to the change of the stream description (now includes vxlan) and your old stored description in the local storage of your browser.
After you delete your local storage and reload the page, it should be re-initialized correctly.
Will be merged into the dev branch and after some more testing and enhancements into main.

Merged in ed6605db8decac194bd35c83507fb695f50043a6 to dev.


MWPW-146342 Implement the base functionality for MEP on the Global Nav bar

Minimal implementation for MEP to work with the global navigation component.
Tested using a sharepoint site (see 'After' url below. See here for the manifest used during testing)
Resolves: MWPW-146342
Test URLs:
Before: https://main--milo--adobecom.hlx.page/?martech=off
After: https://gnav-mep--milo--sharmrj.hlx.page/?martech=off
Before: https://main--moo--sharmrj.hlx.page/?mep=%2Fpersonalization.json--target-challenger+name&martech=off
After: https://main--moo--sharmrj.hlx.page/?mep=%2Fpersonalization.json--target-challenger+name&milolibs=gnav-mep--milo--sharmrj&martech=off

Is this PR so that any gnav "feature" can be personalized, just as it is currently possible with blocks?
Since the current limitation is that only complete navs can be swapped out, rather than individual elements

Is this PR so that any gnav "feature" (brand, menu, universal nav, etc.) can be personalized, just as it is currently possible with blocks?
Since the current limitation is that only complete navs can be swapped out, rather than individual elements
Yes any of the incoming html can be personalized with this implementation.

@vgoodric Can you ping the other Milo PR on this? Is it already merged?

@vgoodric Can you ping the other Milo PR on this? Is it already merged?
cc: @narcis-radu @overmyheadandbody

@salonijain3 , just need to finish the unit tests, but no PR yet

@sharmrj @salonijain3 @narcis-radu @overmyheadandbody : New PR ready https://github.com/adobecom/milo/pull/2252


Documentation Clarity

Description of the bug:
n/a
Actual vs expected behavior:
n/a
Any other information you'd like to share?
Better documentation for this tool is needed. The current guide assumes too much prior knowledge, making it challenging for newcomers. It lacks clear explanations and context, feeling as if written by someone deeply familiar with the tool rather than from a user's perspective.

Hi @HatmanStack, thanks for pointing this out. The tool is currently on version 0.1.1 so I expect this to be true for quite awhile. As we move towards version 1.0 this will likely be rectified.

I have no doubt, I've seen great results when not using quantized models which I'm sure is a focus and will get better.  The CPU restriction when using torch also made things difficult.  Initially, I had to experiment with different models / loading strategies.  Transformers for instance rather than the stock Pytorch models.  More examples here would be helpful for others.  Keep up the Good Work!


Unattributed cut&paste?

This isn't an issue so much as a heads-up. Looks like this Medium article pretty much plagiarized the guide in this repo.
https://medium.com/developingnodes/setting-up-kubernetes-cluster-on-raspberry-pi-15cc44f404b5

Author modified the article to provide attribution


rkt run should offer to do container cleanup

Similar in functionality to docker run --rm.
This would make writing cli tools which wrap rkt run cleaner. When operating outside of systemd, the state of the art as of now is to resort to bash traps and the like for cleaning up transient rkt containers after they have exited.
\cc @aaronlevy

Another call for #621


Can not precompile Gallium

I'm relatively new to Julia and wanted to try out Gallium.jl
When I tried I get this error:

I tried to build, remove/add, and checkout the package. But I still get the same error.
Help! Plz?

I am working on a Mac with macOS Sierra. Julia version 0.5.0. Gallium version 0.0.4

Pkg.free("DWARF") might help. (Independent but also recommended, you might want to upgrade to 0.5.2.)

Unfortunately, Pkg.free("DWARF") didnt work.
Also how do I upgrade without deleting my current julia and reinstall it. Will I have to reinstall all of my packages?

If you built from source it should be git pull && make. You should make sure you're on the release-0.5 branch. If you downloaded a binary you should just download a fresher one, deleting the old one.

Unfortunately, Pkg.free("DWARF") didnt work.

What does "didn't work" mean? Did it give an error message, or did it just not solve the problem? For more help you'll probably need to post the results of Pkg.status().

Sorry, I meant that it did not fix the problem

I then kept getting the same error.
 The issue is likely that there may be a partial migration towards 0.6 support, and from Gallium's perspective 0.6 is a totally different beast from 0.5. If you stick with tagged packages you have greater odds of having it work.

Do you recommend upgrading to v0.6?

Gallium doesn't work on 0.6 yet AFAIK. Otherwise, yes, 0.6 is very nice. We're on release candidates now, but it seems that the official release could come in a matter of days.

i end up in a similar error (struct not defined) on a linux box and v0.5.2 julia, and unfortunately
julia> Pkg.free("Gallium")
INFO: Freeing Gallium
WARNING: julia is fixed at 0.5.2 conflicting with requirement for Cxx: [0.6.0,∞)
INFO: No packages to install, update or remove

Is this issue currently being worked on?

Its been figured out
On Thu, Aug 10, 2017 at 3:55 PM, Andrey Shedko<EMAIL_ADDRESS>wrote:

Is this issue currently being worked on?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Keno/Gallium.jl/issues/193#issuecomment-321656552,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APb1LPFCn-olEHnPS2pynELVT8oMo4m7ks5sW2BIgaJpZM4N77Py
.

Still fails as follows:
julia> using Gallium

WARNING: deprecated syntax "local declfile="", declline=0" at /home/rra/.julia/v0.6/Gallium/src/Gallium.jl:455.
Use "local declfile, declline = "", 0" instead.

WARNING: deprecated syntax "local dbgs=nothing, cu=nothing, sp=nothing" at /home/rra/.julia/v0.6/Gallium/src/Gallium.jl:466.
Use "local dbgs, cu, sp = nothing, nothing, nothing" instead.

WARNING: deprecated syntax "abstract LocationSource" at /home/rra/.julia/v0.6/Gallium/src/Gallium.jl:690.
Use "abstract type LocationSource end" instead.
INFO: Precompiling module Gallium.

WARNING: deprecated syntax "local declfile="", declline=0" at /home/rra/.julia/v0.6/Gallium/src/Gallium.jl:455.
Use "local declfile, declline = "", 0" instead.

WARNING: deprecated syntax "local dbgs=nothing, cu=nothing, sp=nothing" at /home/rra/.julia/v0.6/Gallium/src/Gallium.jl:466.
Use "local dbgs, cu, sp = nothing, nothing, nothing" instead.

WARNING: deprecated syntax "abstract LocationSource" at /home/rra/.julia/v0.6/Gallium/src/Gallium.jl:690.
Use "abstract type LocationSource end" instead.

WARNING: deprecated syntax "abstract ReplacementLoc" at /home/rra/.julia/v0.6/ASTInterpreter/src/ASTInterpreter.jl:155.
Use "abstract type ReplacementLoc end" instead.
ERROR: LoadError: syntax: extra token ".¬" after end of expression
Stacktrace:
 [1] include_from_node1(::String) at ./loading.jl:569
 [2] include(::String) at ./sysimg.jl:14
 [3] anonymous at ./<missing>:2
while loading /home/rra/.julia/v0.6/ASTInterpreter/src/ASTInterpreter.jl, in expression starting on line 914
ERROR: LoadError: Failed to precompile ASTInterpreter to /home/rra/.julia/lib/v0.6/ASTInterpreter.ji.
Stacktrace:
 [1] compilecache(::String) at ./loading.jl:703
 [2] _require(::Symbol) at ./loading.jl:456
 [3] require(::Symbol) at ./loading.jl:398
 [4] include_from_node1(::String) at ./loading.jl:569
 [5] include(::String) at ./sysimg.jl:14
 [6] anonymous at ./<missing>:2
while loading /home/rra/.julia/v0.6/Gallium/src/Gallium.jl, in expression starting on line 3
ERROR: Failed to precompile Gallium to /home/rra/.julia/lib/v0.6/Gallium.ji.
Stacktrace:
 [1] compilecache(::String) at ./loading.jl:703
 [2] _require(::Symbol) at ./loading.jl:490
 [3] require(::Symbol) at ./loading.jl:398

^ Am having the same problem, can't precompile

I'm having the same error as @Qiyamah  too.

Same error as @Qiyamah

I also got an error when compiling Gallium (see in the attached file
Gallium_error.txt. Could anyone please help me with this? Thanks in advance!

I also got some similar issues with Julia 0.7. I have updated the packages.
in expression starting at /usr/people/jingpeng/.julia/packages/DebuggerFramework/9yZZM/src/DebuggerFra
mework.jl:13
ERROR: LoadError: Failed to precompile DebuggerFramework [67417a49-6d77-5db2-98c7-c13144130cd2] to /us
r/people/jingpeng/.julia/compiled/v0.7/DebuggerFramework/0bKxs.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] macro expansion at ./logging.jl:313 [inlined]
 [3] compilecache(::Base.PkgId, ::String) at ./loading.jl:1185
 [4] _require(::Base.PkgId) at ./logging.jl:311
 [5] require(::Base.PkgId) at ./loading.jl:852
 [6] macro expansion at ./logging.jl:311 [inlined]
 [7] require(::Module, ::Symbol) at ./loading.jl:834
 [8] include at ./boot.jl:317 [inlined]
 [9] include_relative(::Module, ::String) at ./loading.jl:1038
 [10] include(::Module, ::String) at ./sysimg.jl:29
 [11] top-level scope at none:2
 [12] eval at ./boot.jl:319 [inlined]
 [13] eval(::Expr) at ./client.jl:399
 [14] top-level scope at ./none:3
in expression starting at /usr/people/jingpeng/.julia/packages/ASTInterpreter2/b1fAq/src/ASTInterprete
r2.jl:4
ERROR: LoadError: Failed to precompile ASTInterpreter2 [e6d88f4b-b52a-544c-a8d3-7a4f12cb39c3] to /usr/
people/jingpeng/.julia/compiled/v0.7/ASTInterpreter2/XrlMa.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] macro expansion at ./logging.jl:313 [inlined]
 [3] compilecache(::Base.PkgId, ::String) at ./loading.jl:1185
 [4] _require(::Base.PkgId) at ./logging.jl:311
 [5] require(::Base.PkgId) at ./loading.jl:852
 [6] macro expansion at ./logging.jl:311 [inlined]
 [7] require(::Module, ::Symbol) at ./loading.jl:834
 [8] include at ./boot.jl:317 [inlined]
 [9] include_relative(::Module, ::String) at ./loading.jl:1038
 [10] include(::Module, ::String) at ./sysimg.jl:29
 [11] top-level scope at none:2
 [12] eval at ./boot.jl:319 [inlined]
 [13] eval(::Expr) at ./client.jl:399
 [14] top-level scope at ./none:3
in expression starting at /usr/people/jingpeng/.julia/packages/Gallium/GrKGN/src/Gallium.jl:4
ERROR: Failed to precompile Gallium [87a02803-f0ee-5d26-846e-298423f06ab0] to /usr/people/jingpeng/.ju
lia/compiled/v0.7/Gallium/rhqmC.ji.
Stacktrace:
 [1] error(::String) at ./error.jl:33
 [2] macro expansion at ./logging.jl:313 [inlined]
 [3] compilecache(::Base.PkgId, ::String) at ./loading.jl:1185
 [4] _require(::Base.PkgId) at ./logging.jl:311
 [5] require(::Base.PkgId) at ./loading.jl:852
 [6] macro expansion at ./logging.jl:311 [inlined]
 [7] require(::Module, ::Symbol) at ./loading.jl:834

You may want to try Rebugger.jl for a 1.0 debugger.
@keno Should we archive Gallium.jl for now?


Issues with future MRT stations

The object for Marina Bay Financial CTR (Bus stop 03391) has the following listed as MRT stations:
[
  "ce2",
  "ns27"
],
[
  "ce2",
  "ns27",
  "te20"
],
[
  "dt17"
]

The 2 MRT stations it is near are Marina Bay (NS27, CE2, TE20) and Bayfront (DT17). However, there is a repeat of Marina Bay, the second of which does NOT have the ref for TE20.
This is because the LTG page for NSL hasn't yet updated the refs for TE as it's hasn't been build:

(No TE20 with Marina Bay)

Can fix manually.

Fixed by completely removing future MRT stations.
Waiting for LTA and LTG to update the site when the new lines are complete. This could take until 2023 ...


use category_id as the category identifier instead of category_name

Codecov Report

Merging #160 (f5f6cd4) into main (8b24ebb) will increase coverage by 0.11%.
The diff coverage is 75.09%.

:exclamation: Current head f5f6cd4 differs from pull request most recent head d4312f8. Consider uploading reports for the commit d4312f8 to get more accurate results

@@            Coverage Diff             @@
##             main     #160      +/-   ##
==========================================
+ Coverage   81.91%   82.02%   +0.11%
==========================================
  Files          56       56
  Lines        3389     3510     +121
==========================================
+ Hits         2776     2879     +103
- Misses        613      631      +18

Impacted Files
Coverage Δ

.../active_learning/strategies/hard_example_mining.py
100.00% <ø> (ø)

...leuth/active_learning/strategies/hybrid_learner.py
100.00% <ø> (ø)

...euth/active_learning/strategies/random_sampling.py
100.00% <ø> (ø)

...sleuth/active_learning/strategies/retrospective.py
100.00% <ø> (ø)

label_sleuth/analysis_utils/labeling_reports.py
27.39% <50.00%> (ø)

label_sleuth/app.py
57.81% <52.71%> (+3.72%)
:arrow_up:

...leuth/training_set_selector/train_set_selectors.py
41.17% <54.54%> (ø)

...h/data_access/file_based/file_based_data_access.py
90.76% <58.33%> (ø)

label_sleuth/orchestrator/orchestrator_api.py
67.74% <64.75%> (-0.12%)
:arrow_down:

...hestrator/core/state_api/orchestrator_state_api.py
90.90% <86.66%> (-2.77%)
:arrow_down:

... and 13 more

Continue to review full report at Codecov.

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


Fix I2C4 not working

Use GPIO_AF6_I2C4 for alternate function

Unable to confirm this works. Tested on the daisy field, replaced I2C1 with I2C4, which should work since they share pins, but it stops working. More digging may be needed.

Sorry for the back and forth, I was able to retest and confirm this is working. Thanks for your contribution!


Document website not available

looks the domain is expired

Project is dead. RIP.

But for who's looking for an alternative for the documentation though: Archive

@QimatLuo @italodeandra In case you’re looking for an actively maintained alternative, I’m working on https://github.com/nut-tree/nut.js, an enhanced framework for desktop automation combining possibilities of robot-js with image matching via OpenCV.
It provides a nice API and additional features like highlighting desktop regions or retrieval of window coordinates / dimensions.

https://nicedoc.io/octalmage/robotjs
@QimatLuo Maybe moving here.


No check in place for if all pubspec deps are compatible with AndroidX before migrating

There appear to be two missing resources in values.xml from the release output from cloud_firestore.
Steps to Reproduce

migrate project to AndroidX using Android studio
add cloud_firestore  and shared_preferences as flutter dependencies
run flutter build apk

Expected output:

         *********************************************************
WARNING: This version of shared_preferences will break your Android build if it or its dependencies aren't compatible with AndroidX.
         See https://goo.gl/CP92wY for more information on the problem and how to fix it.
         This warning prints for all Android build failures. The real root cause of the error may be unrelated.
         *********************************************************
FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':cloud_firestore:verifyReleaseResources'.
> java.util.concurrent.ExecutionException: com.android.builder.internal.aapt.v2.Aapt2Exception: Android resource linking failed
  F:\...\build\cloud_firestore\intermediates\res\merged\release\values\values.xml:276: error: resource android:attr/fontVariationSettings not found.
  F:\...\build\cloud_firestore\intermediates\res\merged\release\values\values.xml:277: error: resource android:attr/ttcIndex not found.
  error: failed linking references.

Flutter Doctor
$ flutter doctor -v
[√] Flutter (Channel beta, v1.1.8, on Microsoft Windows [Version 10.0.17134.556], locale en-US)
    • Flutter version 1.1.8 at C:\flutter_windows_v0.11.11-beta\flutter
    • Framework revision 985ccb6d14 (5 weeks ago), 2019-01-08 13:45:55 -0800
    • Engine revision 7112b72cc2
    • Dart version 2.1.1 (build 2.1.1-dev.0.1 ec86471ccc)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\Jackie\AppData\Local\Android\sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-28, build-tools 28.0.3
    • Java binary at: C:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)
    • All Android licenses accepted.

[√] Android Studio (version 3.3)
    • Android Studio at C:\Program Files\Android\Android Studio
    • Flutter plugin version 32.0.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[!] IntelliJ IDEA Ultimate Edition (version 2018.2)
    • IntelliJ at C:\Program Files\JetBrains\IntelliJ IDEA 2018.2.4
    X Flutter plugin not installed; this adds Flutter specific functionality.
    • Dart plugin version 182.5124
    • For information about installing plugins, see
      https://flutter.io/intellij-setup/#installing-the-plugins

[√] VS Code (version 1.31.1)
    • VS Code at C:\Users\Jackie\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 2.22.3

[√] VS Code, 64-bit edition (version 1.26.1)
    • VS Code at C:\Program Files\Microsoft VS Code
    • Flutter extension version 2.22.3

[√] Connected device (1 available)
    • SM N910T • c253d892 • android-arm • Android 6.0.1 (API 23)

! Doctor found issues in 1 category.

I'd be happy to add my pubspec.yaml if that'd help.

Thanks for filing an issue!
It's really common to still see that error if there's AndroidX incompatibilities somewhere in the app still, even though the message looks completely unrelated. You mention that you've already migrated, so I'm guessing that either the migration missed something somehow or there's still an issue with another plugin you're including being incompatible.

I'd be happy to add my pubspec.yaml if that'd help.

That would be really useful, thanks.

Let me know how I can help :)
name: timeswap_core
description: A new Flutter project.

# The following defines the version and build number for your application.
# A version number is three numbers separated by dots, like 1.2.43
# followed by an optional build number separated by a +.
# Both the version and the builder number may be overridden in flutter
# build by specifying --build-name and --build-number, respectively.
# Read more about versioning at semver.org.
#
# the number after '+' is the version code -- version name is before
version: 0.1.0+1

environment:
  sdk: ">=2.0.0-dev.68.0 <3.0.0"

dependencies:
  flutter:
    sdk: flutter

  flutter_localizations:
    sdk: flutter

  cloud_firestore:

  firebase_auth:

  google_sign_in:

  flutter_facebook_login:

  flutter_firebase_ui:

  dotenv:

  colorize:

  progress_hud:

  square_in_app_payments:

  uuid:

  flutter_slidable:

  flutter_sms:

  dynamic_theme:

  shared_preferences:

  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^0.1.2

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_driver:
    sdk: flutter
  test: 1.5.1
  flutter_launcher_icons:

flutter_icons:
  android: true
  ios: true
  image_path: "assets/icon/icon.png"

# For information on the generic Dart part of this file, see the
# following page: https://www.dartlang.org/tools/pub/pubspec

# The following section is specific to Flutter.
flutter:

  # The following line ensures that the Material Icons font is
  # included with your application, so that you can use the icons in
  # the material Icons class.
  uses-material-design: true

  # To add assets to your application, add an assets section, like this:
  assets:
    - cfg/env.json
    - assets/

  # An image asset can refer to one or more resolution-specific "variants", see
  # https://flutter.io/assets-and-images/#resolution-aware.

  # For details regarding adding assets from package dependencies, see
  # https://flutter.io/assets-and-images/#from-packages

  # To add custom fonts to your application, add a fonts section here,
  # in this "flutter" section. Each entry in this list should have a
  # "family" key with the font family name, and a "fonts" key with a
  # list giving the asset and other descriptors for the font. For
  # example:
  # fonts:
  #   - family: Schyler
  #     fonts:
  #       - asset: fonts/Schyler-Regular.ttf
  #       - asset: fonts/Schyler-Italic.ttf
  #         style: italic
  #   - family: Trajan Pro
  #     fonts:
  #       - asset: fonts/TrajanPro.ttf
  #       - asset: fonts/TrajanPro_Bold.ttf
  #         weight: 700
  #
  # For details regarding fonts from package dependencies,
  # see https://flutter.io/custom-fonts/#from-packages

Same issue for me!

@fpiruzi
Using "add reaction" on the initial comment would increase priority while +1 comments are rather pointless and cause lots of people to get notified for no reason.
To get notified yourself use the [Subscribe] button to the top right instead.

I have the same.
My gradle properties
org.gradle.jvmargs=-Xmx1536M android.useAndroidX=true android.enableJetifier=true
I have also changed targetSdkVersion 28
My pubspec.yaml
cloud_firestore: 0.9.0+1   firebase_auth: 0.8.1

WARNING: This version of cloud_firestore will break your Android build if it or its dependencies aren't compatible with AndroidX.
D8: Cannot fit requested classes in a single dex file (# methods: 67113 > 65536)
         See https://goo.gl/CP92wY for more information on the problem and how to fix it.

FAILURE: Build failed with an exception.
         This warning prints for all Android build failures. The real root cause of the error may be unrelated.
         This warning prints for all Android build failures. The real root cause of the error may be unrelated.

         *********************************************************
* What went wrong:
Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
> com.android.builder.dexing.DexArchiveMergerException: Error while merging dex archives: C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\3.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\4.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\5.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\6.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\7.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\8.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\9.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\10.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\11.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\12.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\13.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\14.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\15.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\16.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\17.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\18.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\19.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\20.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\21.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\22.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\23.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\24.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\25.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\26.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\27.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\28.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\29.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\30.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\31.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\32.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\33.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\34.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\35.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\36.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\37.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\38.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\39.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\40.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\41.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\42.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\43.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\44.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\45.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\46.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\47.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\48.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\49.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\50.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\51.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\52.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\53.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\54.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\55.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\56.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\57.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\58.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\59.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\60.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\61.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\62.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\63.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\64.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\65.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\66.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\67.jar, C:\Users\byxta\Documents\projects\TrainingsDiary\build\app\intermediates\transforms\dexBuilder\debug\68.jar
  The number of method references in a .dex file cannot exceed 64K.
  Learn how to resolve this issue at https://developer.android.com/tools/building/multidex.html

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

BUILD FAILED in 4s
Finished with error: Gradle task assembleDebug failed with exit code 1

I commented out cloud_firestore and firebase_auth, now my project is compiled and run

@xTaz1 your specific error isn't related to AndroidX. It's a really unfortunate limitation of how many Java methods can be included in an Android APK at a time by default. Error while merging dex archives: The number of method references in a .dex file cannot exceed 64K. We're tracking this at #20747 and #27702. You can find more info about it and links to fixing it in this comment.
@DarthWindu thanks! That gives me enough info to debug the problem. It's unfortunately pretty tricky.
So in your pubspec these plugins are still using the deprecated libraries, at least right now:

flutter_facebook_login
flutter_firebase_ui

This means that you can't migrate your app to AndroidX yet, because those plugins will always try to bring in the old support libraries still and crash at compile time. So for your case you're probably going to want to revert your migration and downgrade to the earlier versions of the plugins, from before they were migrated to AndroidX:
  cloud_firestore: ^0.8.2+3
  firebase_auth: ^0.6.2
  google_sign_in: ^3.2.4
  shared_preferences: ^0.4.3

On the plugins side it would be really helpful if we could diagnose incompatible plugins like this better. #27748 is similar to this, it's about automatically handling dependency matching in pub. Ideally for now we could at least update the guide with some type of command to run to check and make sure that your plugins are all compatible with AndroidX before migrating. I think theoretically we should be able to print transitive dependencies with Gradle at the command line and grep through them.

For anyone having difficulty reverting, here's the pubspec.yaml that worked for both iOS and Android (release and debug) builds.
dependencies:
  flutter:
    sdk: flutter

  flutter_localizations:
    sdk: flutter

  cloud_firestore: 0.8.2+1

  firebase_auth: 0.7.0

  # google_sign_in:

  colorize:

  progress_hud:

  square_in_app_payments: 1.0.1

  uuid:

  flutter_slidable:

  flutter_sms: 0.0.3

  dynamic_theme:

  shared_preferences: 0.4.3

  # The following adds the Cupertino Icons font to your application.
  # Use with the CupertinoIcons class for iOS style icons.
  cupertino_icons: ^0.1.2

dev_dependencies:
  flutter_test:
    sdk: flutter
  flutter_driver:
    sdk: flutter
  test: 1.5.1
  flutter_launcher_icons:

flutter_icons:
  android: true
  ios: true
  image_path: "assets/icon/icon.png"

@mklim Why is this happening? I have exactly the same problem using cloud_firestore and shared_preferences even though they should be migrated. I overlooked this issue and thus created another one, which I close, but it has a more detailed description: https://github.com/flutter/flutter/issues/28294
This seems really severe and I cannot figure out why this is happening.

@creativecreatorormaybenot I reopened your original issue and replied there, it sounds like a different problem than this one.

downgrading gradle from 5.4.1 to 4.10.2 fixed this for me...

[   +3 ms] Note: there were 2 references to unknown classes.
[   +2 ms]       You should check your configuration for typos.
[   +1 ms]       (http://proguard.sourceforge.net/manual/troubleshooting.html#unknownclass)
[   +1 ms] Note: there were 1 references to unknown class members.
[   +1 ms]       You should check your configuration for typos.
[   +1 ms] Note: there were 210 unkept descriptor classes in kept class members.
[   +1 ms]       You should consider explicitly keeping the mentioned classes
[   +1 ms]       (using '-keep').
[   +1 ms]       (http://proguard.sourceforge.net/manual/troubleshooting.html#descriptorclass)
[   +1 ms] Note: there were 55 unresolved dynamic references to classes or interfaces.
[   +1 ms]       You should check if you need to specify additional program jars.
[   +1 ms]       (http://proguard.sourceforge.net/manual/troubleshooting.html#dynamicalclass)
[   +1 ms] Note: there were 21 accesses to class members by means of introspection.
[   +1 ms]       You should consider explicitly keeping the mentioned class members
[   +1 ms]       (using '-keep' or '-keepclassmembers').
[   +3 ms]       (http://proguard.sourceforge.net/manual/troubleshooting.html#dynamicalclassmember)
[   +3 ms] Warning: there were 6 unresolved references to classes or interfaces.
[   +2 ms]          You may need to add missing library jars or update their versions.
[   +1 ms]          If your code works fine without the missing classes, you can suppress
[   +1 ms]          the warnings with '-dontwarn' options.
[   +2 ms]          (http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedclass)
[   +2 ms] Warning: there were 1 unresolved references to library class members.
[   +2 ms]          You probably need to update the library versions.
[   +2 ms]          (http://proguard.sourceforge.net/manual/troubleshooting.html#unresolvedlibraryclassmember)
[   +3 ms] Warning: Exception while processing task java.io.IOException: Please correct the above warnings first.
[   +1 ms] > Task :app:transformClassesAndResourcesWithProguardForRelease FAILED
[   +1 ms] Thread(Tasks limiter_1): destruction
[   +6 ms]          *********************************************************
[   +1 ms] WARNING: This version of cloud_firestore will break your Android build if it or its dependencies aren't compatible with AndroidX.
[   +1 ms]          See https://goo.gl/CP92wY for more information on the problem and how to fix it.
[   +1 ms]          This warning prints for all Android build failures. The real root cause of the error may be unrelated.
[   +2 ms]          *********************************************************
[   +2 ms] 242 actionable tasks: 241 executed, 1 up-to-date
[ +367 ms] Running Gradle task 'bundleRelease'... (completed in 454.5s, longer than expected)
[   +1 ms] *******************************************************************************************
[   +1 ms] The Gradle failure may have been because of AndroidX incompatibilities in this Flutter app.
[   +1 ms] See https://goo.gl/CP92wY for more information on the problem and how to fix it.
[   +4 ms] *******************************************************************************************
[  +16 ms] "flutter appbundle" took 481,340ms.
Gradle task bundleRelease failed with exit code 1
#0      throwToolExit (package:flutter_tools/src/base/common.dart:28:3)
#1      _buildGradleProjectV2 (package:flutter_tools/src/android/gradle.dart:751:5)
#2      _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:71:64)
#3      _rootRunUnary (dart:async/zone.dart:1132:38)
#4      _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#5      _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#6      Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#7      Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#8      Future._completeWithValue (dart:async/future_impl.dart:522:5)
#9      _AsyncAwaitCompleter.complete (dart:async-patch/async_patch.dart:30:15)
#10     _completeOnAsyncReturn (dart:async-patch/async_patch.dart:288:13)
#11     runCommandAndStreamOutput (package:flutter_tools/src/base/process.dart)
#12     _asyncThenWrapperHelper. (dart:async-patch/async_patch.dart:71:64)
#13     _rootRunUnary (dart:async/zone.dart:1132:38)
#14     _CustomZone.runUnary (dart:async/zone.dart:1029:19)
#15     _FutureListener.handleValue (dart:async/future_impl.dart:137:18)
#16     Future._propagateToListeners.handleValueCallback (dart:async/future_impl.dart:678:45)
#17     Future._propagateToListeners (dart:async/future_impl.dart:707:32)
#18     Future._completeWithValue (dart:async/future_impl.dart:522:5)
#19     Future._asyncComplete. (dart:async/future_impl.dart:552:7)
#20     _rootRun (dart:async/zone.dart:1124:13)
#21     _CustomZone.run (dart:async/zone.dart:1021:19)
#22     _CustomZone.runGuarded (dart:async/zone.dart:923:7)
#23     _CustomZone.bindCallbackGuarded. (dart:async/zone.dart:963:23)
#24     _microtaskLoop (dart:async/schedule_microtask.dart:41:21)
#25     _startMicrotaskLoop (dart:async/schedule_microtask.dart:50:5)
#26     _runPendingImmediateCallback (dart:isolate-patch/isolate_patch.dart:116:13)
#27     _RawReceivePortImpl._handleMessage (dart:isolate-patch/isolate_patch.dart:173:5)

am also stuck in this for 5 days.


relighting by own dataset

Thank you for your work!
is it possible to relight by own background images?
I hope you will release code which treat wild dataset(preprocess code).

Hi. What do you mean when you say 'own background images'?
The diffusion model takes an environment map as the lighting condition by default.

Hello, thank you for your replying.
I mean I want to use my own image as background.
Is it possible? should we need to prepare panoramic view image like below image?

Hi, our model is not conditioned on the background image.
For your requirement, I would suggest you take a look at IC-Light:
https://github.com/lllyasviel/IC-Light


Fix GCSE qualifications design

Context
The bugs

The heading of the summary card for the qualifications should reflect the qualification type, not say ‘GCSE’. So if a user selects ‘GCE O Level’, that’s what should appear as the card title.

On the qualification type page, there should be an ‘or’ divider before the last option.

Changes proposed in this pull request

Before

After

Guidance to review
👀

Link to Trello card
https://trello.com/c/gYaHY1qn/1251-fix-gcse-qualifications-design
Things to check

[X] This code doesn't rely on migrations in the same Pull Request
[X] If this code includes a migration adding or changing columns, it also backfills existing records for consistency
[X] API release notes have been updated if necessary
[X] New environment variables have been added to the Azure config

Love it, such a quick response time!


OSSA support for Box types. AccessedStorage Box handling. isBorrowedAddress utility.

These 4 commits are interdependent as far as avoiding test regressions. The two main features are

Unify Box/Class/Tail handling in AccessedStorage/MemAccessUtils.
Add isBorrowedAddress, which is required for OSSA-based transformations.

Add a tiny BorrowedAddress utility.
Determines whether an address might be inside a borrowed scope. If so,
then any address substitution needs to find that scope boundary to
avoid violating its basic guarantee that all uses are within scope.

MemAccessUtils: unify Box/Class/Tail storage for consistency and usability
It was originally convenient for exclusivity optimization to treat
boxes specially. We wanted to know that the 'Box' kind was always
uniquely identified. But that's not really important. And now that
AccessedStorage is being used more generally, the inconsistency is
problematic.

A consistent model is also must easier to understand and explain.

This also make the implementation of the utility simpler and more powerful.

Functional changes:

isRCIdentical will look through mark_dependence and mark_uninitialized.

findReferenceRoot is used consistently everywhere increasing analysis precision.

The isBorrowedAddress utility will help fix https://github.com/apple/swift/pull/38672 (OSSA+TempRVO fix) and is required by https://github.com/apple/swift/pull/38470 (OSSA utilities)

@swift-ci test

@swift-ci test source compatibility

@swift-ci benchmark

Performance (x86_64): -O

Regression
OLD
NEW
DELTA
RATIO

DictionaryOfAnyHashableStrings_insert
3444
5586
+62.2%
0.62x

Set.isDisjoint.Int25
263
341
+29.7%
0.77x (?)

Set.isDisjoint.Int50
263
337
+28.1%
0.78x (?)

FlattenListFlatMap
4421
5135
+16.2%
0.86x (?)

DictionaryKeysContainsNative
22
25
+13.6%
0.88x (?)

ArrayAppendOptionals
2040
2300
+12.7%
0.89x (?)

DictionaryRemove
3170
3500
+10.4%
0.91x (?)

TypeName
904
980
+8.4%
0.92x (?)

Code size: -O
Performance (x86_64): -Osize

Improvement
OLD
NEW
DELTA
RATIO

ArrayAppendGenericStructs
2010
1330
-33.8%
1.51x (?)

FlattenListLoop
4864
3976
-18.3%
1.22x (?)

Code size: -Osize
Performance (x86_64): -Onone

Regression
OLD
NEW
DELTA
RATIO

NSStringConversion.Rebridge.Long
276
314
+13.8%
0.88x (?)

NSStringConversion.Rebridge.Medium
276
313
+13.4%
0.88x (?)

Improvement
OLD
NEW
DELTA
RATIO

String.data.Small
89
83
-6.7%
1.07x (?)

Code size: -swiftlibs

How to read the data
The tables contain differences in performance which are larger than 8% and
differences in code size which are larger than 1%.
If you see any unexpected regressions, you should consider fixing the
regressions before you merge the PR.
Noise: Sometimes the performance results (not code size!) contain false
alarms. Unexpected regressions which are marked with '(?)' are probably noise.
If you see regressions which you cannot explain you can try to run the
benchmarks again. If regressions still show up, please consult with the
performance team (@eeckstein).

Hardware Overview
  Model Name: Mac Pro
  Model Identifier: MacPro6,1
  Processor Name: 12-Core Intel Xeon E5
  Processor Speed: 2.7 GHz
  Number of Processors: 1
  Total Number of Cores: 12
  L2 Cache (per Core): 256 KB
  L3 Cache: 30 MB
  Memory: 64 GB

Build failed
Swift Test Linux Platform
Git Sha - f351cb4e8528e7a8f2005e0df4372a75575e575f

Build failed
Swift Test OS X Platform
Git Sha - f351cb4e8528e7a8f2005e0df4372a75575e575f

All SCK builds passed (although I don't know how to make them build with -sil-verify-all).

@swift-ci test

Thanks @atrick ! lgtm


[WIP, ENH] Abstracted volume registration again

Another version of #9515, but with fewer tests modified. The relevant ones pass locally at least.
@alexrockhill feel free to test _USE_PREALIGN=False to see if it works better now!

The key commit is https://github.com/mne-tools/mne-python/pull/9521/commits/87948130c60fabb38893cfa6bb15b0137cbc2eb7

So this issue is how you apply a reg_affine to an elec_image. I don't think you can while preserving the integer voxels values. So for the ieeg case, I think you have to use pre_align.
For the other case it would be nice to use the same code, but that seems like a large overhaul of tests and visualizations because they are not functionally equivalent.

So this issue is how you apply a reg_affine to an elec_image. I don't think you can while preserving the integer voxels values

Sure you can, same way as you do for the SDR -- you use interpolation='nearest'

For the other case it would be nice to use the same code, but that seems like a large overhaul of tests and visualizations because they are not functionally equivalent.

This part I don't understand. What is the "other case" here, non-nearest (i.e., linear) case?

You could move the coordinates to aligned space and make the elec_image that way so that it doesn't have to be registered but that throws a wrench in our API because you apply the reg_affine to the input image and then apply the SDR so that complicates things as well. The pre_align works great and I think is preferable API simplicity.

Basically the commit uses resample(..., interpolation='nearest') but this is not exposed by Dipy so it just dups the code they use:
https://github.com/mne-tools/mne-python/commit/87948130c60fabb38893cfa6bb15b0137cbc2eb7#diff-780e284e0c926dd24e28047f79e10f0138e800e5a91a35b88c17689edd1909b8R1789
The morph tests suggest the prealign is slightly less accurate than the apply-then-SDR. Can you check to see if on this branch things look the same or better for your sEEG data?

This part I don't understand. What is the "other case" here, non-nearest (i.e., linear) case?

The other case being the volumetric source space warp. That one can't just be switched to pre-align because it causes all the tests to fail.

The pre_align works great and I think is preferable API simplicity.

I agree it's slightly simpler internally to use prealign, but users never see it. So if the prealign is less accurate (as the morph tests suggest) then I'd rather use our apply-then-SDR case...

Basically the commit uses resample(..., interpolation='nearest') but this is not exposed by Dipy so it just dups the code they use:
8794813#diff-780e284e0c926dd24e28047f79e10f0138e800e5a91a35b88c17689edd1909b8R1789
The morph tests suggest the prealign is slightly less accurate than the apply-then-SDR. Can you check to see if on this branch things look the same or better for your sEEG data?

Ok, I misunderstood, I think this is great then!

Do you want to try porting over your reg-on-the-fly (and test that it still works!) and any other change(s) from #9515? If it all tests well at your end I'll push a commit to remove all prealign stuff, and port in the SourceMorph attribute updates from #9503 then we should be good to go hopefully!
I won't get to it until Tuesday, though, so if you want to take a shot at doing the above as well, feel free. Otherwise if you're more interested in moving on to the GUI stuff feel free to do that!

Do you want to try porting over your reg-on-the-fly (and test that it still works!) and any other change(s) from #9515? If it all tests well at your end I'll push a commit to remove all prealign stuff, and port in the SourceMorph attribute updates from #9503 then we should be good to go hopefully!
I won't get to it until Tuesday, though, so if you want to take a shot at doing the above as well, feel free. Otherwise if you're more interested in moving on to the GUI stuff feel free to do that!

Sure, I can do that. I think for the reg-on-the-fly as you call it you have to change 4 tests but not too much (just loosen slightly). I'll take at Alex Gramfort's issue and then get to it.

I think for the reg-on-the-fly as you call it you have to change 4 tests

I'm only talking about this tutorial change:
https://github.com/mne-tools/mne-python/pull/9515/files#diff-f802a9dfc7b418c33db03c47e5eb7353f3e124121ff07c4b867fa274d83d0d88R132-R134
No changes to internal code for "reg on the fly" (as opposed to hard-coded values)

I think for the reg-on-the-fly as you call it you have to change 4 tests

I'm only talking about this tutorial change:
https://github.com/mne-tools/mne-python/pull/9515/files#diff-f802a9dfc7b418c33db03c47e5eb7353f3e124121ff07c4b867fa274d83d0d88R132-R134
No changes to internal code for "reg on the fly" (as opposed to hard-coded values)

Ah I thought you meant you didn't move the out_affine code back which fixes the MR-CT alignment. Ok checking now!

Ok, the example runs at full resolution just fine and all the tests pass! And, thinking about it, it is consistent with how the affine registration is done (applying before each optimization). I'm happy, looks great to merge.

We'll just have to see how long it takes to run on CircleCI. If it's many minutes, we might still want to hard-code the result (and just comment out the high-res / best version). On Tuesday I can add back the SourceMorph changes unless you beat me to it

We'll just have to see how long it takes to run on CircleCI. If it's many minutes, we might still want to hard-code the result (and just comment out the high-res / best version). On Tuesday I can add back the SourceMorph changes unless you beat me to it

It was 2.5 minutes to run locally, that's okay right?

It was 2.5 minutes to run locally, that's okay right?

That's probably too slow for CircleCI -- < 1 min is best for an example like this, and CircleCI is slower than most workstations so it's going to probably take 5+ minutes there if I had to guess (assuming you're not running on an underpowered laptop or anything)

It was 2.5 minutes to run locally, that's okay right?

That's probably too slow for CircleCI -- < 1 min is best for an example like this, and CircleCI is slower than most workstations so it's going to probably take 5+ minutes there if I had to guess (assuming you're not running on an underpowered laptop or anything)

2:29 when run locally...

This actually isn't as bad as I expected:
Total running time of the script: ( 2 minutes 10.853 seconds)

This might be a problem (<1.5 GB is better):
Estimated memory usage: 1778 MB

I'll push a commit to comment out the affine since it makes it much faster and memory efficient; locally I saw:

61.62 sec 1765.1 MB with zooms version / fec45f1
303.02 sec 3488.9 MB with zooms=None to get the affine
38.53 sec 1614.2 MB using the hard-coded affine
41.92 sec 830.6 MB using hard-coded affine plus np.asarray(img.dataobj) rather than img.get_fdata in several places (this allows smaller datatypes than np.float64 to be used in a few places)

@alexrockhill want to take one last look at the example and make sure everything is okay, then we merge? Here it is:
https://30428-1301584-gh.circle-artifacts.com/0/dev/auto_tutorials/clinical/10_ieeg_localize.html#sphx-glr-auto-tutorials-clinical-10-ieeg-localize-py

I would use the zooms=dict(translation=5) version if you're going to comment it out. The hard-coded affine is in previous commits.

Looks like there is issues with one too many "`" in the warning about zooms for the SDR

I would use the zooms=dict(translation=5) version if you're going to comment it out. The hard-coded affine is in previous commits.

Okay, I thought at one point you said this was no longer necessary, but if it works at least as well why not! I'm planning to put in whatever affine I get from locally using this code, hopefully it matches well what was there before

I would use the zooms=dict(translation=5) version if you're going to comment it out. The hard-coded affine is in previous commits.

Okay, I thought at one point you said this was no longer necessary, but if it works at least as well why not! I'm planning to put in whatever affine I get from locally using this code, hopefully it matches well what was there before

You can use zooms=None but that takes twice as long, the outputs are equivalent just trying to save you some time.

Okay locally it works, I'll go ahead and merge to save the CIs some cycles. Thanks @alexrockhill !

... I say that then make flake tells me there is a problem. I'll just let CIs finish.


Additional tests + propositon of implementation

Do not merge this pr
This pr contains additonal tests that covers situation with mandatory/optional arguments for commands
It also contains propositon of simplified the implementation (see MateuszCommands folder)

@matiduck can I close this PR? We can continue our discussion on the PR I've opened with revise implementation.

@MarcinIN , you can close this pr as all of the inital doubts were cleared.
All other discussion will be contiued in Version/1.0 pr


[7773] - replace webdriver gem

Context
webdriver is no longer needed and selenium-webdriver should be used instead
Changes proposed in this pull request

Removes webdriver and adds selenium-webdriver
Smoke testing has been run by @d-a-v-e and still works with new gem-set

 Update/review really old gem webdrivers


[0.x] Publish PHAR

This PR offers the possibility to publish a the .phar within the release the assets, everytime a release is created
cf. https://github.com/laravel/pint/issues/28

Nice. Thanks @lucasmichot

Let's have a look at the build when a new release is created.
Hopefully this action won't need any adjustment


how to chance color of selected bar ?

hello, thanks for this awesome library !
my question is that how to chance color of selected bar ?

As mentioned in the issue template, the issues are not meant to be used for this kind of questions.

Actually this is constructive feedback, in the sense that the wiki should be clearer about this. Added a section: https://github.com/i-schuetz/SwiftCharts/wiki/Bars#selection-handling


Zeus

Zeus (chain blitz angriff)
Originally posted by @quiode in https://github.com/quiode/TroyTD/issues/39#issuecomment-1014247439

(chain blitz angriff)

chain angriff gemacht, braucht nurnoch Texturen @Tixfun


[BUG] aiohttp deflate error

Describe the bug
Error when adding the integration for the Stretch.
Evidence
2020-08-21 23:20:18 ERROR (MainThread) [custom_components.plugwise.config_flow] Unexpected exception
Traceback (most recent call last):
  File "/config/custom_components/plugwise/config_flow.py", line 130, in async_step_user
    api = await validate_input(self.hass, user_input)
  File "/config/custom_components/plugwise/config_flow.py", line 74, in validate_input
    await api.connect()
  File "/usr/local/lib/python3.8/site-packages/Plugwise_Smile/Smile.py", line 161, in connect
    result = await resp.text()
  File "/usr/local/lib/python3.8/site-packages/aiohttp/client_reqrep.py", line 1009, in text
    await self.read()
  File "/usr/local/lib/python3.8/site-packages/aiohttp/client_reqrep.py", line 973, in read
    self._body = await self.content.read()
  File "/usr/local/lib/python3.8/site-packages/aiohttp/streams.py", line 358, in read
    block = await self.readany()
  File "/usr/local/lib/python3.8/site-packages/aiohttp/streams.py", line 380, in readany
    await self._wait('readany')
  File "/usr/local/lib/python3.8/site-packages/aiohttp/streams.py", line 296, in _wait
    await waiter
aiohttp.client_exceptions.ClientPayloadError: 400, message='Can not decode content-encoding: deflate'

Home Assistant Core (please complete the following information):

Version: 0.114.3
Deployment: hassio
Installed plugwise version: plugwise-beta pre-v0.7.0a0 code
Installed through: HACS

Smile (please complete the following information):

Sort of Smile: Stretch v2
Firmware: 2.3.12

Additional context
Adding this: headers = {'Accept-Encoding': 'gzip'} make the error go away.

Investigation shows that this is indeed an existing aiohttp-error.
There are pull-request in the master-branch fixing this error.
Solutions:

a temporary work-around using headers = {'Accept-Encoding': 'gzip'} in Plugwise_smile
use aiohttp > 3.6.2 when available


Switch to IKG file tracking from analyzer when in --preview-dart-2

IKG has an API to report list of files used for compilation as well as incremental updates to that list. Flutter tools should use that instead of analyzer (https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/dart/dependencies.dart).
Note that IKG API will be used to provide list of files when it is loaded from [File]ByteStore. @scheglov

@a-siva

Honestly, I don't understand the comment about ByteStore.
Cache is important for performance, but information is provided either way, cached or not.
I agree withe the goal of the issue of course - it is better to use one system to get all information.

@scheglov, Flutter tools needs to start tracking sources files that comprise the dart app. This list should be coming from IKG instead of analyzer. Currently we get that list before we do kernel generation, so the thinking is that there should be a way to get list of files known to IKG after we create new instance of IKG.
On other hand, we might say that the list of dart sources will be provided by IKG first time we actually do the kernel generation. I think this is what IKG API currently provides, which probably will be acceptable too, but will require more refactoring on Flutter tools side to support old and new ways of doing things(with and without --preview-dart-2 flag).

@scheglov  to answer your question about the comment on ByteStore we wanted to make sure that IKG will be able to provide us this list of files even in the case when it comes up first by reading the full state from the FileStore (the case of 'flutter build' to 'flutter run' transition).

OK, understood.
Yes, it will.

cc @askeksa-google @kmillikin - this needs to be addressed to remove dependency on analyzer to produce list of files that have to be tracked for hot-reload in Flutter.

This was completed earlier this year


Resolve #2728: Added fontsource usage instead google fonts

[ ] Breaking change? (if so, please describe the impact and migration path for existing application instances)

What changes did you make? (Give an overview)
Is there anything you'd like reviewers to focus on?
How Has This Been Tested? (put an "x" (case-sensitive!) next to an item)

[ ] No need to
[x] Manually (please, describe, if necessary)
[ ] Unit checks
[ ] Integration checks
[ ] Covered by existing automation

Checklist (put an "x" (case-sensitive!) next to all the items, otherwise the build will fail)

[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation (e.g. ENVIRONMENT VARIABLES)
[x] My changes generate no new warnings (e.g. Sonar is happy)
[ ] 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

Check out Contributing and Code of Conduct
Linked issues:
Closes #2728

Hey @0leg53,
Thank you for contribution!
Unfortunately, we cannot merge your changes yet. Due to the technical peculiarities of building and running the application.
This PR is blocked by #2372

@0leg53 I've added a label "hacktoberfest-accepted" to make sure it does count towards the goal if you're participating

@Haarolean
thank you for review.
how exactly you've got this error? I've tried to run app with pnpm preview and font loading looks fine.

@0leg53 you'll have to set a SERVER_SERVLET_CONTEXT_PATH property. This is a result of #2372 as Oleg mentioned :)

@0leg53 hey can you fix the conflicts? I think we're ready to test it out.

Done within #3602


Sonar

Is there a option to access sonar url which is protected by userid/password? I tried adding sonar.username and sonar.apiKey but didnt work. collector able to access the url but failing to pull the data due to authentication issue.

Sonar collector does support userid/password based basic auth. Does not (yet) handle token based. Let me know is basic auth is not working for you. Will be good to have token based auth.

Can we close this @eldojoseph

@tabladrum sorry I missed to update you. Basic auth didnt work. I am yet to dig more on it. please share if someone is using token based auth.

If you have any log to share, it will be helpful.

I am sorry. I cannot share logs from my client's machine.


Fixed triage_stats to avoid passing arguments to the underlying jira_cmd

If eventually it calls
jira_cmd.main(self.args)

shouldn't we want to use the same arg parser? (So --help would work)

If eventually it calls
jira_cmd.main(self.args)

shouldn't we want to use the same arg parser? (So --help would work)

No, this script does not pass user args to underlying jira_cmd tool.
for jira_cmd to work, it needs to build the jira_cmd argparse structure and populate it. That is why it calls parse_args() of jira_cmd without any arguments


FPS Tutorial Sticky Grenades Performance Issue

Godot version:

Godot_v3.1.1-stable_win64
OS/device including version:

NVIDIA GeForce GTX 1050 Ti
AMD Phenom II X6 1100T Processor, 3.30 GHz
16GB RAM
Issue description:

Following the Adding grenades part of the FPS tutorial (https://docs.godotengine.org/en/3.1/tutorials/3d/fps_tutorial/part_five.html):

When firing sticky grenades, FPS performance decreases significantly.
Normal grenades are fine.
Issue occurs on both Ruins & Space level but not in the Testing Area.
Disabling the Sticky_Area/Collision_Shape node in Sticky_Grenade.tscn allows firing sticky grenades without FPS performance decrease.
Issue also occurs from the completed project download link at the bottom of the tutorial page.
Recording of issue can be found here: https://youtu.be/4XLGV4T3H8Q

Steps to reproduce:
Minimal reproduction project:

Godot_FPS_Starter.zip

Sooo I tried the demo in 3.2.3 rc1 and FPS drop is noticeable, but not sure if it's really physics problem or demo problem or what. I'd just close it and only reopen with an actual engine issue.

Closing as per the above, it's not clear whether there's any engine bug or just a project-specific bug.


fix(Page): teach Page.waitFor* function to work with strict CSP

This patch removes function creation from WaitTask, making the
following methods work with strict CSP policy:

frame.waitForFunction
frame.waitForSelector
frame.waitForXPath

Page counterparts of the methods work as well.
References #1229.

This doesn't seem to work when waitForFunction is provided arguments to be passed to the function, i.e.
page.waitForFunction(arg => !!arg, {}, 'some argument')

@simoneb we have a test for this, it passes:
https://github.com/GoogleChrome/puppeteer/blob/dde45faaebd4232ef953622a8e1e07e544cf64a8/test/frame.spec.js#L139-L147

Doesn't for me in a real use case. Also, I see that the test is passing a DOM elementi as an argument, I never got anything except primitive values to work in this way (i.e. passing a regex wouldn't work, a string would), so I'm wondering if this test is running in a sort of special context

Nooooo. I wanted this PR, haha :)

@sean-hill we rolled the upstream fix in the puppeteer,  puppeteer@next should work with waitFor* functions.


Added !meme

Generates a meme based on the input. For instance !meme ants "Top" "Bottom" produces:

Also, running !meme names will send a list of all of the allowable names to the users channel. In future UQCS specific memes could be added.
I don't know why I did this.

also, great work :^)


ODBC access

Is your feature request related to a problem? Please describe.
This request comes from users' wish to connect external applications with datasets managed by data.all.
Describe the solution you'd like
Data.all users get to see what they are allowed to see (thanks to Lakeformation). It'd be nice if there could be a way of easily using ODBC (Athena driver) in a way that would be very consistent with data.all UI. That means:

only data.all users would be able to use ODBC
users should be able to query precisely what they can query from within data.all / Athena. This would include joins between datasets, possibly shared ones, possibly residing indifferent environments.

Also, imagine a setup where you have tenths, or even hundreds of data.all environments. It should be easy to setup and use ODBC. Finally, there should not be a necessity of using static credentials anywhere in the process.

This is a great issue @pmarko1711 and definitely one where we have seen customer interest. Let me connect with internal AWS teams that are currently working on this item. We need to design and document the pattern and share it here in the issue and in the documentation.


".oh-my-zsh/custom/themes/spaceship.zsh-theme:1: command not found: Not" error when trying to apply theme

Hi, i just followed your instruction and installed theme via curl -o - https://raw.githubusercontent.com/denysdovhan/spaceship-zsh-theme/master/install.sh | zsh modified my .zshrc file to use "spaceship" theme, but when i reload zsh, i get error mentioned in the subject. What am i missing ?

get error mentioned in the subject.

Can you show an error message?

Oh, sorry. I've noticed it in title.

Fixed! Try to install now.

~/.oh-my-zsh/custom/themes/spaceship.zsh-theme:1: command not found: spaceship.zsh

I'm also getting this error, and I can't figure out what I'm missing or doing wrong. Anyone who got this and managed to solve it?

same problem

same here

same

any fix for this?


Question about the transformation from grid coordinates to image coordinates?

Thanks for your help on the previous issue.
The depth map is downsampling 4x, but the intrinsic is the same as the original one.
I think the transformation is below that.

When performing the transformation, we utilize normalized coordinates, which are essentially coordinates normalized between [-1, 1]. That way, the transformation works regardless of scale.
What ends up happening exactly is we generate a set of points in the center of each voxel, which we call the sampling grid. We project each point in the sampling grid from 3D space into the camera frustum space of full size (not downsampled by 4). Then, we normalize each point between [-1, 1], forming our frustum sampling grid. We then use the grid_sample function to sample from our frustum grid, which accepts normalized coordinates. Since coordinates are normalized between [-1, 1], the functionality will be the same regardless of scale of image features/depth map.

Thanks a lot! @codyreading


Use of assertions

Hi there,
I am using the module but I am a bit confused how the assertions are used. As I see in the core project, you are using the assertions against the options object. For example, in the c9.core/client.js it is used like that:
assert(options.baseUrl, "Option 'baseUrl' is required")

It is not used against imports though. For example, in the c9.vfs.standalone/standalone.js the preview handler it is imported like that:
var previewHandler = imports["preview.handler"];

What if a developer forget to add this dependency in the consume array? The previewHandler it will be undefined and it will break at runtime in this specific example. Why there is not an assertion like that:
assert(imports["preview.handler"], "preview.handler is required");

Is there something that I am missing?

Adding assertions like that for every used service would make code too verbose/unreadable.
requirement to manually update the list of dependencies in the consumes array is indeed problem, we should either make a eslint rule for it, or automatically infer list of dependencies using toString similar to what require.js does, but in the latter case performance overhead is significant for a large project like cloud9

We start adding assertions and finally the code became too verbose. Finally we god a decision to check the consumes array into the unit tests. The array is exported and we can compare the result with the definition in the unit test. If someone for a reason changes the dependencies (adding or removing a dependency) the unit test will break.
By the way, I saw that you are extending the chai expect library with the setupArchitectTest function (https://github.com/c9/core/blob/b24bf63f9f5a43a9647ab5cd20bee4c3e14d55fa/plugins/c9.vfs.standalone/www/test.js#L543).
Can this abstraction be helpful to check the consume dependencies or in general testing an architect application?
Many thanks!


Continuous repeated CIDRNotAvailable event for one node in cluster.

Environmental Info:
K3s Version:

k3s version v1.26.4+k3s1 (8d0255af)
go version go1.19.8

Node(s) CPU architecture, OS, and Version:

Linux node1 5.10.0-16-amd64 #1 SMP Debian 5.10.127-1 (2022-06-30) x86_64 GNU/Linux
Cluster Configuration:

Total of 3 servers using the embedded etcd.  I am using Calico 3.25 instead of Flannel.
Describe the bug:

While the node is working fine -- all network functionality, pod scheduling, service routing, etc -- it is constantly logging CIDRNotAvailable events. I can't find any mention in the k3s logs of any network issues that could be causing this.  If I didn't see this in the kubectl describe node output, I'd have no idea there was a problem, honestly.
Events:
  Type    Reason            Age                      From           Message
  ----    ------            ----                     ----           -------
  Normal  CIDRNotAvailable  107s (x1025 over 3d14h)  cidrAllocator  Node node1 status is now: CIDRNotAvailable

Steps To Reproduce:

Not sure, but if someone could point me in the direction of troubleshooting further, I'd appreciate it.
Expected behavior:

I expect this event not to be logged :-)
Additional info:
Here's the systemd unit file ExecStart entry, it's the same on all the nodes:
ExecStart=/usr/local/bin/k3s \
    server \
	'--disable-network-policy' \
	'--flannel-backend=none' \
	'--token=<redacted>' \
	'--disable=servicelb' \
	'--cluster-cidr=<IP_ADDRESS>/23' \
	'--cluster-dns=<IP_ADDRESS>' \
	'--service-cidr=<IP_ADDRESS>/24' \
	'--server' \
	'https://<IP_ADDRESS>:6443' \

Also -- I opened an issue with Project Calico, but they don't think this is being caused by the calico software.  See https://github.com/projectcalico/calico/issues/7722
Thanks :-)

	'--cluster-cidr=<IP_ADDRESS>/23' \
	'--cluster-dns=<IP_ADDRESS>' \
	'--service-cidr=<IP_ADDRESS>/24' \

Why the tiny CIDRs? The default node CIDR mask is /24, so with a /23 cluster-cidr you only have enough addresses for two nodes in your cluster. You've also only allocated yourself enough space for 255 ClusterIP services.
You should rebuild your cluster with more reasonable CIDR blocks.


feat(cargo-metadata): add workspace_default_members

What does this PR try to resolve?
Fixes  #8033.
How should we test and review this PR?
I fixed one test "cargo_metadata_simple". Other tests haven't been updated, and potentially additional tests could be added to test the new functionality specifically.
Additional information
More tests would have to be updated. This change adds "workspace_default_members" to the ExportInfo struct which is serialized to json. I would imagine this could break existing testing infrastructure, but existing crates / apps reading this output should presumably expect that additional fields / data could be added.

Pardon my changing it to draft.
@rustbot author

The team just agreed on adding this field 🎉.
@charles-r-earp, could you rebase onto master and update the doc as I mentioned earlier? Thanks in advance!
r? @weihanglo

The rebase seems to be done incorrectly. Could you start over and fix that?

:umbrella: The latest upstream changes (presumably #11840) made this pull request unmergeable. Please resolve the merge conflicts.

:pushpin: Commit 61df6bb41865e3e6ca05da1efac01be0ae3cbea9 has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 61df6bb41865e3e6ca05da1efac01be0ae3cbea9 with merge<PHONE_NUMBER>cb8221a2dc87dc8f5428cc12bd255b...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing<PHONE_NUMBER>cb8221a2dc87dc8f5428cc12bd255b to master...


support for 32 bit systems

you can add support for 32-bit systems?
I would like to use the module from npm "flow-bin" in my 32-bit linux.

https://github.com/facebook/flow/issues/270 has some context on why this is hard. The shared memory implementation assumes 64 bit, and it would be difficult to re-write for 32 bit.

I suggest closing this issue.

Duplicate of https://github.com/facebook/flow/issues/270


GOBBLIN-846: Enhance LogCopier service to handle continuous YARN log …

…aggregation
Dear Gobblin maintainers,
Please accept this PR. I understand that it will not be reviewed until I have checked off all the steps below!
JIRA

[x] My PR addresses the following Gobblin JIRA issues and references them in the PR title. For example, "[GOBBLIN-XXX] My Gobblin PR"

https://issues.apache.org/jira/browse/GOBBLIN-846

Description

[x] Here are some details about my PR, including screenshots (if applicable):
This task enhances LogCopier service to perform continuous log aggregation for long-running Gobblin-on-Yarn applications. It periodically copies rolled container logs to a specified location on HDFS. The "current" log file is copied in the end as part of the service shutdown sequence.

Tests

[x] My PR adds the following unit tests OR does not need testing for this extremely good reason:
Added unit tests in LogCopierTest

Commits

[x] My commits all reference JIRA issues in their subject lines, and I have squashed multiple commits if they address the same issue. In addition, my commits follow the guidelines from "How to write a good git commit message":

Subject is separated from body by a blank line
Subject is limited to 50 characters
Subject does not end with a period
Subject uses the imperative mood ("add", not "adding")
Body wraps at 72 characters
Body explains "what" and "why", not "how"

@autumnust @htran1 Please review the PR


Update sbt-mdoc to 2.0.2

Updates org.scalameta:sbt-mdoc from 1.3.6 to 2.0.2.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.scalameta", artifactId = "sbt-mdoc" } ]

labels: semver-major

Duplicate of #97


Losing lines of text after editing with 'add-next-match-to-selections

Using advanced-cursors:add-next-match-to-selections I have just several times lost some lines of text that should not have been deleted. I don't think it's operator error, but I'm not sure, so I'm going to track my attempts to reproduce it here.

... later on today ... Sorry to leave you with a cliff-hanger!!

Closing issue - I haven't had enough time to reproduce it today... Will re-open if I find it again when I have more time...
Sorry for causing alarm...
For my own info:


Openhab + Grafana + Reverseproxy in Docker

Hi,
I'm really struggling to get the Grafana webview panels to work with Openhab and Grafana behind a reverse proxy in Docker.
I get the following errors (in the Firefox console):

SecurityError: Permission denied to get property "href" on cross-origin object smarthome-grafana.js:350

TypeError: smartHomeSubscriber is undefined

Docker-compose file:
version: '2'

services:
   reverseproxy:
     image: reverseproxy
     ports:
     # openhab
     - 5001:5001
     restart: always

   openhab:
     depends_on:
     - reverseproxy
     image: "openhab/openhab:2.4.0"
     restart: always
     ports:
     - "8080:8080"
     - "8443:8443"
     volumes:
     - "/etc/localtime:/etc/localtime:ro"
     - "/etc/timezone:/etc/timezone:ro"
     - "/opt/openhab/addons:/openhab/addons"
     - "/opt/openhab/conf:/openhab/conf"
     - "/opt/openhab/userdata:/openhab/userdata"
     environment:
       OPENHAB_HTTP_PORT: "8080"
       OPENHAB_HTTPS_PORT: "8443"
       EXTRA_JAVA_OPTS: "-Duser.timezone=Europe/Berlin"
       USER_ID: "999"
       GROUP_ID: "999"

   grafana:
     depends_on:
     - reverseproxy
     image: grafana/grafana:latest
     ports:
       - '3000:3000'
     volumes:
       - grafana-storage:/var/lib/grafana
       - grafana-conf:/etc/grafana
     environment:
       - GF_SECURITY_ADMIN_USER=${GRAFANA_USERNAME}
       - GF_SECURITY_ADMIN_PASSWORD=${GRAFANA_PASSWORD}
       - GF_AUTH_ANONYMOUS_ENABLED=true
       - GF_USERS_ALLOW_SIGN_UP=false
       - GF_SERVER_ROOT_URL=http://localhost/grafana/
       - GF_ALLOW_EMBEDDING=true
volumes:
  grafana-storage:
    driver: local
  grafana-conf:
    driver: local

nginx.conf:
worker_processes 1;

events { worker_connections 1024; }

http {

    sendfile on;

    upstream docker-openhab {
        server openhab:8080;
#       server <IP_ADDRESS>:8080;
    }

    server {
        listen 5001;
        server_name     localhost;
        location / {
#           auth_basic           "Restricted Access!";
#           auth_basic_user_file /etc/nginx/conf.d/.htpasswd;
            proxy_pass           http://docker-openhab;
#           proxy_pass           http://localhost:8080;
#           proxy_redirect       off;
            proxy_buffering      off;
            proxy_set_header     Host $http_host;
#           proxy_set_header     Host $host;
            proxy_set_header     X-Real-IP $remote_addr;
            proxy_set_header     X-Forwarded-For $proxy_add_x_forwarded_for;
#           proxy_set_header     X-Forwarded-Host $server_name;
            proxy_set_header     X-Forwarded-Proto $scheme;
#           add_header           X-Frame-Options  ALLOWALL;
#           add_header         X-Frame-Options SAMEORIGIN;
        }

        location /grafana/ {
            proxy_pass         http://<IP_ADDRESS>:3000/;
#           proxy_pass         http://docker-grafana/;
#           add_header         X-Frame-Options ALLOWALL;
#           add_header         X-Frame-Options SAMEORIGIN;
        }
    }
}

sitemap:
sitemap default label="test"
{
Webview height=9 icon=none
url="http://<IP_ADDRESS>:5001/static/combo-300px.html?dashboardItem=gf_dashboard&fromItem=temp_view&panelItem=gf_panel_temperature&w=000000"
}

// the prefix that is used for each Grafana panel URL
SMARTHOME_GRAFANA_DEFAULTS["urlPrefix"] = "http://<IP_ADDRESS>:5001/grafana";

Openhab can be accessed at:
http://<IP_ADDRESS>:5001
Grafana at:
http://<IP_ADDRESS>:5001/grafana
Your help is much appreciated, thank you!

It should be possible to get it all working with Docker because I use a similar setup.
Since both openHAB and Grafana seem to work correctly on the same port, maybe the library doesn't generate the correct Webview URLs? You can check the generated URLs by enabling the debug mode by appending &debug=true to your browser URL. Firefox might also show the blocked URL requests in the debug view Network panel.

Hi,
Thanks for the quick reply. I managed to get rid of the errors, but an other one showed up:

Load denied by X-Frame-Options: http://<IP_ADDRESS>:5001/grafana/d-solo/FydmKUdZz/home?from=now-1y&to=now-1d&panelId=33&theme=light does not permit framing.

This suggests that the Docker environment variable 'GF_ALLOW_EMBEDDING=true'  for Grafana is not set? But I did, as shown above.
I've cloned your repository again and started with a minimal configuration. Only the static panel is shown on the sitemap and debug mode is on. The URL is correctly generated and works when accessing it in another tab:
http://<IP_ADDRESS>:5001/grafana/dashboard-solo/db/home?from=now-1y&to=now-1d&panelId=33&theme=light
The URL in the error message also works outside openhab.
http://<IP_ADDRESS>:5001/grafana/d-solo/FydmKUdZz/home?from=now-1y&to=now-1d&panelId=33&theme=light
Any ideas?

Looks like the section name is missing from your allow embedding variable, see:
https://grafana.com/docs/installation/configuration/#using-environment-variables
So maybe it works when you use GF_SECURITY_ALLOW_EMBEDDING instead?
I see it's also being used like that in the community.
I'm still using an older Grafana version myself. But it's good to know I need to add this environment variable while upgrading.

I can't believe that I've missed that..! Got everything working now, really appreciate the help!

That's great news! :-)