Update gitpython requirement

gitpython requires gitdb2, but that has removed some things in newer
versions, and 2.11.1 had an open ended dep. So, update gitpython to a
newer version that has more specific version requirements for gitdb2.
This should fix these errors:
https://github.com/gitpython-developers/GitPython/issues/983
https://travis-ci.org/StackStorm/st2/jobs/652088774#L9416
https://circleci.com/gh/StackStorm-Exchange/stackstorm-sumologic/155
Thanks to @blag for tracking down the bug.

This won't fix all of the build errors on master. There are other issues as well, this is just the only one with a clear fix so far.

Other issues include:

something installing wrong idna version (.st2client-install-check in the Lint Checks build; can't find what changed here)
build pack virtualenv fails (in 2.7 Integation Tests build. Maybe due to permissions issue? Build has no details)

Once we figure those issues out, they should probably go in separate PRs. Can we merge this fix even without resolving those other issues?

@cognifloyd If these issues are causing the errors in the CI above, then you have to fix them before we can merge.

NAK - investigating, will edit this comment in a bit

I just cherry-picked the --no-site-packages fix from #4863.
Plus I'm trying to resolve the permissions issue in a nicer way than the xenial workaround to see if that fixes the 2.7 integration tests.
Still stumped on the idna issue.

It's GREEN! :green_heart:

It's arguable pip requirements fix needs that amount of changes. I'd prefer to not mix different changes in one PR. This keeps history clear and straightforward.
Additionally, per previous comment we're missing CHANGELOG record which is required for pip requirements update for st2 core.
Even though, many thanks for fixing master! :heavy_check_mark:

@blag asked me to get rid of the 777 permissions workaround affecting the entire home directory.
I'm not sure why precise started having permissions issues, but I needed to adjust something, so I moved some of the permissions changes from #4863 to this PR to resolve that, only I made sure to do something that would selectively change permissions only where needed.
So, no, this was not just a pip dep update.
Changelog PR coming soon.


ticking order book

I've trying to keep an in memory copy of the order book in a nodes app using the event stream (https://webapi.coinfloorex.com:8090/event-stream).
Which events do I need to listen to in order to be able to keep an accurate representation of the current order book?

There is guidance on this topic in the Implementation Guide. There's no way to (un)subscribe to/from order books in the Event Stream; you're always subscribed to all of them.
Note that the Event Stream will not give you an initial snapshot of the order books. It only provides incremental updates. I'd recommend to connect to the Event Stream first and begin applying the incremental updates to your (initially empty) view, and then subsequently request a snapshot of the order book and merge it into your (possibly nonempty) view. Note that the snapshot could be lagging the stream, so you would want to remember any stream events that didn't match with any order already in your view before you merged the snapshot and replay those events into your view after you merged the snapshot. If done correctly, you'll have a perfectly consistent view of the order book that you can maintain indefinitely.
This is considerably simpler to implement if you use the WebSocket API, which allows you to subscribe to an order book and capture a snapshot of it in one atomic operation.

Thanks @whitslack thats very helpful.
I took a look at the example WS code but struggled to understand it. However, I saw the feed in my browsers networking output and figured out what to do, almost.
I can see how to subscribe to the order book feed, but the parameters are confusing.  What are the magic numbers for base and counter?  And what is tag?

Coinfloor's WebSocket API is documented here. You are specifically asking about the WatchOrders command, which is covered in this section.
The asset codes are enumerated here.


mobile navbar sign up

For some reason the sign up link doesnt work for that

it was a different link just copied and pasted!


node compile issue due to ClientHttp2StreamMock

https://source.cloud.google.com/results/invocations/38d0fdf3-0f01-437f-9094-2acd8d425873/targets/grpc%2Fcore%2Fpull_request%2Flinux%2Fgrpc_interop_tocloud/log
Please decrease priority if appropriate.
><EMAIL_ADDRESS>install /var/local/git/grpc-node/packages/grpc-native-core
> node-pre-gyp install --fallback-to-build --library=static_library
npm notice created a lockfile as package-lock.json. You should commit this file.
added 103 packages in 6.407s
[20:32:36] Finished 'health-check.install' after 7 s
node-pre-gyp WARN Using request for node-pre-gyp https download
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
gyp WARN download NVM_NODEJS_ORG_MIRROR is deprecated and will be removed in node-gyp v4, please use NODEJS_ORG_MIRROR
make: Entering directory '/var/local/git/grpc-node/packages/grpc-native-core/build'
  CXX(target) Release/obj.target/grpc/deps/grpc/src/core/lib/surface/init.o
npm notice created a lockfile as package-lock.json. You should commit this file.
added 192 packages in 9.358s
[20:32:39] Finished 'protobuf.install' after 9.97 s
  CXX(target) Release/obj.target/grpc/deps/grpc/src/core/lib/avl/avl.o
test/test-call-stream.ts:30:7 - error TS2420: Class 'ClientHttp2StreamMock' incorrectly implements interface 'ClientHttp2Stream'.
  Property 'endAfterHeaders' is missing in type 'ClientHttp2StreamMock'.
30 class ClientHttp2StreamMock extends stream.Duplex implements
         ~~~~~~~~~~~~~~~~~~~~~
test/test-call-stream.ts:107:37 - error TS2345: Argument of type 'ClientHttp2StreamMock' is not assignable to parameter of type 'ClientHttp2Stream'.
  Property 'endAfterHeaders' is missing in type 'ClientHttp2StreamMock'.
107        callStream.attachHttp2Stream(http2Stream);
                                        ~~~~~~~~~~~
test/test-call-stream.ts:141:40 - error TS2345: Argument of type 'ClientHttp2StreamMock' is not assignable to parameter of type 'ClientHttp2Stream'.
141           callStream.attachHttp2Stream(http2Stream);
                                           ~~~~~~~~~~~
test/test-call-stream.ts:183:36 - error TS2345: Argument of type 'ClientHttp2StreamMock' is not assignable to parameter of type 'ClientHttp2Stream'.
183       callStream.attachHttp2Stream(http2Stream);
                                       ~~~~~~~~~~~
test/test-call-stream.ts:213:41 - error TS2345: Argument of type 'ClientHttp2StreamMock' is not assignable to parameter of type 'ClientHttp2Stream'.
213            callStream.attachHttp2Stream(http2Stream);
                                            ~~~~~~~~~~~
test/test-call-stream.ts:247:38 - error TS2345: Argument of type 'ClientHttp2StreamMock' is not assignable to parameter of type 'ClientHttp2Stream'.
247         callStream.attachHttp2Stream(http2Stream);
                                         ~~~~~~~~~~~
test/test-call-stream.ts:270:36 - error TS2345: Argument of type 'ClientHttp2StreamMock' is not assignable to parameter of type 'ClientHttp2Stream'.
270       callStream.attachHttp2Stream(http2Stream);
                                       ~~~~~~~~~~~
test/test-call-stream.ts:286:39 - error TS2345: Argument of type 'ClientHttp2StreamMock' is not assignable to parameter of type 'ClientHttp2Stream'.
286          callStream.attachHttp2Stream(http2Stream);
                                          ~~~~~~~~~~~
test/test-call-stream.ts:301:36 - error TS2345: Argument of type 'ClientHttp2StreamMock' is not assignable to parameter of type 'ClientHttp2Stream'.
301       callStream.attachHttp2Stream(http2Stream);
                                       ~~~~~~~~~~~
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>compile: `tsc -p .`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>compile script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
npm ERR!  Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>prepare script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.
  CXX(target) Release/obj.target/grpc/deps/grpc/src/core/lib/backoff/backoff.o
npm ERR! A complete log of this run can be found in:
npm ERR!     /tmp/npm-cache/_logs/2018-09-24T20_32_39_702Z-debug.log
[20:32:40] 'js.core.install' errored after 11 s
[20:32:40] Error: Command failed: npm install --unsafe-perm
    at Promise.all.then.arr (/var/local/git/grpc-node/node_modules/execa/index.js:236:11)
    at process._tickCallback (internal/process/next_tick.js:68:7)
[20:32:40] 'setup' errored after 11 s
[20:32:40] Error in plugin "run-sequence(js.core.install)"
Message:
    Command failed: npm install --unsafe-perm
Details:
    code: 1
    killed: false
    stdout: null
    stderr: null
    failed: true
    signal: null
    cmd: npm install --unsafe-perm
    timedOut: false

ClientHttp2Stream is part of the Node HTTP/2 module. It looks like they added a method, and that broke our mock class. That is impacting us here because we are building our test code as part of our normal build process.

OK, I don't know what's happening here. I can't figure out how to reproduce this failure on my local machine.

Stale.


Slow Queries from Bug Disco

Catch all for slow query reports:
@axch:

The infer with confidence example seems slow.  Didn't time end-to-end; time was dominated by reading the words rather than waiting for the computations, but the computations were not instantaneous.

@axch:
estimate class_of_orbit, type_of_orbit, predictive probability of class_of_orbit as "p(class)", predictive probability of type_of_orbit as "p(type)" from satellites_cc where type_of_orbit is not null order by "p(type)" asc limit 20

surprisingly, annoyingly slow

@tibbetts:
q('DROP TABLE IF EXISTS inferred_class')
q('''
CREATE TEMP TABLE inferred_class AS
INFER EXPLICIT
anticipated_lifetime, perigee_km, period_minutes, type_of_orbit,
PREDICT class_of_orbit AS inferred_orbit_class
CONFIDENCE inferred_orbit_class_conf
FROM satellites_cc;''')
q('SELECT * from inferred_class')

Takes about 45 seconds. Is that slow?

Significant performance improvements since September. @marcoct, can you verify according to sessions, that these are going faster now?


Add ElasticSearch flags to query/collector

Coverage remained the same at 100.0% when pulling 8e1dbeff8ac5433dcd7e0acc2e40240e566fbdc0 on es-flags into 1f670290a10179aa0a18f4e042bb1783ab0c5649 on master.

Coverage remained the same at 100.0% when pulling 4bea9c603bb7036b100dc979ec229185d89d3b94 on es-flags into 8b747554dd3b12edb6b3a1523a6a03a7c9c82961 on master.

Coverage remained the same at 100.0% when pulling 4bea9c603bb7036b100dc979ec229185d89d3b94 on es-flags into 8b747554dd3b12edb6b3a1523a6a03a7c9c82961 on master.


Fix the whitespace below the Login and Create Account page

User Need:
As a document Owner, I need a polished UI that doesn't have empty white spaces that confuse me so that I intuitively know how to navigate the platform
Description:
There is whitespace below the login and Create account web page in the mobile version
URL:
https://formforwarder.xyz:5002/?client_id=t1L0EvTYT-H_xU3oNaR0BBYc&response_type=code&redirect_url=https://mypass-atx.s3.us-east-2.amazonaws.com/index.html&scope=&state=
To Reproduce
Steps to reproduce the behavior

Go to the URL mentioned above(Refer to URL) in mobile version especially Firefox
Scroll down to "Create Account" button
3.Notice the whitespace

Expected behavior
The whitespace has to be removed
Screenshots:
Refer to the comments in here
Device and browser
Mobile
----small task---
Higher purpose(How this task affects the platform?):

Adoption of the platform
How we know that document owners will use and rely on the platform.


chore: Updated to pin to R12 RC1 bits

Description
During R12 development we were pulling latest, but the SDK has moved to R13.  This pins to the R12 RC1 bits for the SDK.
Task Item
#minor
Screenshots
N/A

Coverage increased (+0.01%) to 53.803% when pulling 74f1dc5111fa800fc1b018780acc0dee4de878ac on gcox/move-to-R12-rc into 43355d4889c4c83ec6cfd066ca8e106a1f25d258 on main.

Potential duplicate of #5920

Potential duplicate of #5920

Thanks Soroush, I'll close this one and let STCA update the schema too.


Update README.md to point to android-ndk discussion thread

merging it now: the discussion thread is too useful to wait :-)


Update example, fix null-pointer check, update android build

Hi there - thought you might like the work I did to polish this module up so I could use it in my app
The commit messages have the details but the basics are:

android build system using new versions and updated ext version definition style
fix type error in the sms list null pointer check recently committed #22
refresh the example completely for react-native 0.58.6, incl. RN59 + API28 local bundle workaround for debug builds
integrate permissions check in example so it works out of the box
remove WRITE_SMS from example since Android disallows this for apps that aren't the default SMS app in Android >= KitKat

All of this makes the example current and usable as a demonstrator, with the code working correctly on my API28 / Android Pie/9 device.
Thanks!

Thanks for the contribution, @mikehardy!
I appreciate this a lot. The tests will come in handy - I wasn't sure how to set them up but this will go a long way in ensuring confidence in the code.


Date Handling Errors

We're seeing the error invalid Date-like object: must be a Date, Time, DateTime or Hash in MULTIPARAMETER_KEY format
when inputting invalid dates to our form - both in browser and in tests.
To recreate this - have a 3 field date input and insert incorrect values for example Day: 1 - Month: 1 - Year: 20201
This worked previously in 2.4.0, is this expected in 2.5.0, or are we expected to change our error handling?

Yeah - I believe this is due to you using the GovUkDateFields gem, which looks like it's using this FormDate class to represent dates. It's not responding to #day, #month or #year (instead #dd, #mm, #yyyy) so it's not treated like a Ruby Date object.
The form builder sticks very closely to Rails' defaults, the 1i/2i/3i style params work with the inbuilt multi-parameter attributes to build a Date.
The options to resolve this are:

add a config option to the form builder that also checks the attribute for other accessors (here), so it might be something like config.custom_date_accessors = %i(dd mm yyyy)
patch govuk_uk_date_fields and add some alias_method to point #day at #dd etc
rework your date fields so they're more in-line with Rails - totally appreciate this might be a massive task so I'm more than happy to help with either of the two above if poss 😅

I had a chat with @zheileman and he was surprised people were still using the GovUkDateFields library, especially in conjunction with the form builder. We are of the opinion that moving to the form builder's (i.e. Rails') approach for handling dates and date params will be easiest in the long run.
As I said above - if it's a big task I'm willing to add an extra clause to the if statement linked above that'll allow you to continue using the latest version of the gem while you update your validations; I'll await a response before taking the next step.

Hi Peter - strange as we definitely don't use the GovUkDateFields library - it's definitely not in our yarn packs or gemfile. The issues must be arriving elsewhere?

I think @RoseSAK and I made a bit of progress on this, looks like the issue is around the raising of a YearError here.

v2.5.1b1 contains a new config option that will warn instead of fail when it encounters a date it doesn't like.
If the logs get a bit noisy you can shush them by toggling enable_logger.
I'll leave this option in place for the time being, but it'll remain undocumented.

This appears to have been resolved. The above PR/beta release wasn't necessary in the end. Closing for now.


EFLOW - Cannot select another internal vmswitch other then 'Default switch'

Question Summary
I would like to be able to select another internal vmswitch other then 'Default switch'. Whenever I do so, it tells me that the only supported switch is 'Default switch'.
Running
Deploy-Eflow -acceptEula 'yes' -acceptOptionalTelemetry 'no' -enableVtpm -vnetType 'ICS' -vnetName 'IoT EFLOW Nat Switch'
gives me
- C:\iotedge\nodectl.exe  network vnet create --config "C:\iotedge\\yaml\cloudvnet.yaml" failed to execute [Error: rpc error: code = Unknown desc = VMMS only supports the 'Default Switch' ICS network
Unfortunately, for 'reasons', the 'Default switch' doesn't work for me. It is not capable of providing internet access to any of the other vm's in my setup. I've tried a lot of different things, but nothing seems to work. As soon though as I create my own NAT network, (see https://docs.microsoft.com/en-us/virtualization/hyper-v-on-windows/user-guide/setup-nat-network)  and get my windows vm's to use it, it works.
Issue here though is that the 'Default switch' provides DHCP like functionality, and my own NAT network doesn't. That means that I have to open up the vm and manually assign a ip address, gateway address and DNS server.
I see two issues here:

I am having a hard time figuring out how to actually setup the network configuration on the CBL-Mariner vm.
I need this to be automatable. I don't think I can SSH into the vm and then change network configuration, but I don't know how else I can access the vm through powershell and modify those settings, after I figure out how to do so.

I will be attempting to setup a small DHCP server in a seperate vm, and see if that works. If you have any other suggestions, I would really appreciate it.

@ericvruder,
By any chance are you deploying EFLOW to a Windows VM that is hosted in Azure?  There are limitations to the vSwitch options in an Azure VM and it varies by edition of Windows that you are using.  If you are doing this all in Azure VMs, it is my understanding that you will definitely need a DHCP server.
Terry

To add to this issue (i'm collegue of Eric), the DHCP in the default switch in hyper-v is frankly not working(gives us only a IPv6 address not IPv4).

We've been trying this out on both Windows 10 Enterprise, Version 20H2 and 1909, not azure environment.

Bug since 1903

possible workaround (mentioned here: https://borncity.com/win/2019/06/18/windows-10-v1903-ip-resolution-bug-in-hyper-v-switch/) is activating windows feature "Windows Sandbox" and starting this app before hyper-v service, but this appears to only resolve it until the VM is restarted.

We could theoretically as a workaround, setup the "External" vnet ourself, and bridge it with a loopback interface(otherwise host looses network), to allow the "Deploy-EFlow" to continue setup, and afterwards change the VM to our own "Internal" vnet.
Issue with a custom internal vnet, is it requires DHCP, which was included with the default vnet, this adds quite some additional VM's to be managed once this scales up.
Instead i would prefer if in this case we could configure a static ip( as we know the network since we configured the internal vnet ourself) for the VM, does nodectl support this?

Side note: If we we're to experiment a bit more on our end, where can we find the docs on the nodectl.exe tool, primarily in regards to the yaml structures?

Just to itterate exactly what we had to do in order to get it to work:
Whenever the guest was incapable of getting an ip, we would do the following:

shut down the guest
shut down the hyper-v service
close any instances of sandbox we had running
turn on hyper-v
start an instance of sandbox up
start up the guest vm

This would always lead to an ipv4 being assigned to the guest vm, but there is still an issue with dns name resolution. I am not sure what address is being added to /etc/resolv.conf (in my case,<IP_ADDRESS>), but it's not doing anything. We would then SSH into the guest and modify the dns server settings and assign it <IP_ADDRESS> or <IP_ADDRESS> - we now have net access with name resolution.
As soon as the guest is restarted, it looses its ip address and we have to start the dance all over again.
Another issue I see with creating our own internal network, besides the DHCP issue, is that the Deploy-Eflow tool does not support that (remember the original issue, can only use 'Default switch' as an internal switch). This would require us to be able to modify the yaml config files. As @Thacai mentioned, if we could provision it with a predefined network configuration and dns servers, that would be amazing.

This issue does seem to be associated with our current setup. This works if we run it on another computer, or if we create a vm and get it to run there. Closing this issue.

Hi, I landed here since we have a related issue. Maybe someone has a pointer for us: We have EFLOW running on an AzureVM and we can access our .NET-Core website (in an EdgeModule) using Https when logged into the Hyper-V VM via ssh. i.e. It works like a charm in the Hyper-V VM. But, when we open the firewall ports  etc. on the Azure-VM -- the usual stuff -- we can't seem to access the https port on the Hyper-V VM from the web. We've searched for port forwarding help on that... Maybe we are missing something obvious to Azure-VM experts? Or is it an Azure-VM-EFLOW issue that we'll need to sit out? Thanks for any tips.

Hi, @PtwHub  could you please open a new issue with all the detailed information? Also, please add the answer to these questions?

If you RDP to the Azure VM, can you access using the browser to the website?
Are you trying to access the website using directly the Azure VM IP?

Thanks,
Francisco

Will do, now looking at https://github.com/Azure-Solutions/azure-quickstart-templates/tree/6d3229350f6b1e4e75adf26746bd82431989699c/301-nested-vms-in-virtual-network
Answers to your Q:

Yes, at the <IP_ADDRESS>:433 address.
We set up the usual dns hostname to the Azure Windows VM and would like to access the https site via that. ... looking for that forwarding/mapping.

@PtwHub,
Thanks for answering my questions. From my understanding, if you can access the module using the local web browser, then you have some issues with the Azure VM traffic redirection. I would suggest creating an issue in the Azure repo, as they probably will be able to assist you better.
Thanks,
Francisco


Feature: Search Control Styling, Styling Standardization

Current State
Currently, the search icon still uses its own css styling, making it harder to standardize styling for the search control. In addition, there are some minor styling discrepancies between the controls that we could attempt to fix (borders, shadowing, etc.)
TODO

[ ] Whether through tailwind, adding your own styles, or rolling a new control, attempt to standardize styling on the search control to match the existing controls
[ ] Investigate existing controls, determine differences, standardize

@MaxMaeder Harvard actually does have a Communications Guide, which defines Harvard's typography and colors to use. We should bring these new fonts in as part of the map and also reconfigure our tailwind to include these colors for future use.


Firebase Auth does not work with twitter

Steps to Reproduce

To reproduce the problem one would just have to attempt to sign in using Flutter_twitter_login and firebase authentication. The twitter auth portion is working. The problem is with the flutter firebase auth portion.
Logs

I/flutter (32385): PlatformException(ERROR_INVALID_CREDENTIAL, The supplied auth credential is malformed or has expired. [ Failed to fetch resource from https://api.twitter.com/1.1/account/verify_credentials.json?include_email=true, http status: 401, http response: {"errors":[{"code":32,"message":"Could not authenticate you."}]} ], null)

Analyzing _...
No issues found! (ran in 7.7s)

[√] Flutter (Channel stable, v1.2.1, on Microsoft Windows [Version 10.0.17763.379], locale en-US)
    • Flutter version 1.2.1 at C:\Users\dserr\Flutter\flutter
    • Framework revision 8661d8aecd (7 weeks ago), 2019-02-14 19:19:53 -0800
    • Engine revision 3757390fa4
    • Dart version 2.1.2 (build 2.1.2-dev.0.0 0a7dcf17eb)

[√] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
    • Android SDK at C:\Users\dserr\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 33.3.1
    • Dart plugin version 182.5215
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1248-b01)

[√] VS Code (version 1.33.0)
    • VS Code at C:\Users\dserr\AppData\Local\Programs\Microsoft VS Code
    • Flutter extension version 2.25.0

[√] Connected device (1 available)
    • ONEPLUS A3000 • 2846bfa7 • android-arm64 • Android 8.0.0 (API 26)

• No issues found!

Same issue for me.

When I add flutter_twitter_login: ^1.1.0 to my pubspec.yaml dependencies, my build fails with exception: Execution failed for task ':app:transformDexArchiveWithExternalLibsDexMergerForDebug'.
When I comment out the dependency in my pubspec, it builds fine.

I'm fighting the same thing. Has anyone found a fix?

Same issue for me, how is this not fixed?

@koskorya this is another bug. Does it still occur?
If so please file a separate bug.
@KieranSteyn @EmmanuelAmodu @filipppp  Do you relate to the bug of the thread opener or the one of @koskorya ?
I know that this works because I implemented it in one of our apps.
Looking at the error message
I/flutter (32385): PlatformException(ERROR_INVALID_CREDENTIAL, The supplied auth credential is malformed or has expired. [ Failed to fetch resource from https://api.twitter.com/1.1/account/verify_credentials.json?include_email=true, http status: 401, http response: {"errors":[{"code":32,"message":"Could not authenticate you."}]} ], null)

Tells me that there is a problem with the Twitter apikey/secret.
Please ask questions like that on stackoverflow. We are not able to give individual support. Thanks for your understanding.

@escamoteur I'm having the same problem as the thread opener @Bobbyjoness and it's not the keys. I tested everything and tried everything. Someone suggested that the twittersdk is deprecated and not being used anymore.. instead FirebaseOAUTH is used in Android for example.

FirebaseAuth oh yeah, just checked now FirebaseAuth comes with https://pub.dev/documentation/firebase_auth/latest/firebase_auth/TwitterAuthProvider-class.html
So I guess you should use that

FirebaseAuth oh yeah, just checked now FirebaseAuth comes with https://pub.dev/documentation/firebase_auth/latest/firebase_auth/TwitterAuthProvider-class.html
So I guess you should use that

Yes I'm using that as shown in my issue #138

But https://pub.dev/packages/flutter_twitter should work too at least I have used it in the past successfully

I tried that library too. Tried all of them to be precise. It isn't a problem with the library, it's more likely there's something with firebase_auth since this function throws the error after getting passed the correct keys.

I opened this again to give this issue more attention

@Bobbyjoness
This issue has been moved to https://github.com/FirebaseExtended/flutterfire/issues/1113. Any further collaboration will be done there.


[RESTEASY-2620] added SSE support and testcases

@rsearls  This looks good to me. Just one minor thing, we can probably improve:

Looks like InboundSseEventProvider is redundant and it reads the InboundSseEvent for twice. I removed it and merge it's functionality to PublisherRxInvokerImpl and it works: https://github.com/resteasy/Resteasy/pull/2491
I also improved the InboundSseEventTest a bit along with this change. Feel free to cherry-pick from this pull request or close it.

I assume this is not needed anymore (due to https://github.com/resteasy/Resteasy/pull/2574 )


Support Pretrained Model from on-prem or different cloud provider

Is your feature request related to a problem?
Today, pre-trained model endpoints and model meta list endpoint are hardcoded and point to openearch artifactory. When OpenSerach is deployed on prem on in different cloud provider, opensearch artifactory endpoint is not reachable and pre-trained model won't be able to used.
What solution would you like?

Other cloud provider will mirror opensearch artifactory and host it in their artifactory
Add a setting to customize the model endpoint and model meta list endpoint

What alternatives have you considered?

Expose internet connection so that other provider can reach to opensearch artifactory. However it is not security since some time cluster requires OpenSearch cluster deployed in private subnet.

Do you have any additional context?
Add any other context or screenshots about the feature request here.

PR to address this issue
https://github.com/opensearch-project/ml-commons/pull/2119


Possible issue with Ingress rules not routing?

Running on K8s 1.8.4 + RBAC through OpenStack, LoadBalancer support (I think..), I re-deployed Contour just now to make sure I was on a new version of Contour too. Testing out a simple rule.
This Ingress definition works, confirmed with curl -i http://<LB IP>:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: hello
  labels:
    app: hello
spec:
  backend:
    serviceName: hello
    servicePort: 80

This however does not, giving instead a 404 when I curl -i http://<LB IP>/hello:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: hello
  labels:
    app: nelson
spec:
  rules:
    - http:
        paths:
          - path: /hello
            backend:
              serviceName: hello
              servicePort: 80

Here are the Deployment and Service objects I'm using:
kind: Deployment
apiVersion: apps/v1beta1
metadata:
  labels:
    app: hello
    version: v1
  name: hello
spec:
  replicas: 1
  selector:
    matchLabels:
      app: hello
  template:
    metadata:
      labels:
        app: hello
        version: v1
      name: hello
    spec:
      containers:
        - name: hello
          image: gcr.io/hightowerlabs/server:0.0.1
          imagePullPolicy: Always
          args:
            - "-name=istio-test-v1"

apiVersion: v1
kind: Service
metadata:
  name: hello
  labels:
    app: hello
spec:
  ports:
  - port: 80
    name: http
    targetPort: 80
    protocol: TCP
  selector:
    app: hello
  type: ClusterIP

@adelbertc thanks for raising the issue. I have a feeling I know what it is.
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
  name: hello
  labels:
    app: nelson
spec:
  rules:
    - http:
        paths:

Doesn't specify a hostname. https://kubernetes.io/docs/api-reference/v1.8/#ingressrule-v1beta1-extensions (the host: field).
Contour expects this field to be mandatory, but I'll check the api definitions for 1.8 and confirm this.
In the meantime the workaround would be to add a host: field to your ingress object.

Yup, this was my misunderstanding. The spec says

If the host is unspecified, the Ingress routes all traffic based on the specified IngressRuleValue.

So it should become the default vhost as in your first example.

@davecheney Ah gotcha - where can I find what the default vhost value is to test this?

Something like this should do it
% kubectl -n heptio-contour get svc -o yaml | grep hostname
      - hostname: a4d1766f6ce1611e7b27f023b7e83d33-1465548734.ap-southeast-2.elb.amazonaws.com

Hm I don't seem to have that, I assume this is vendor specific since I am running in OpenStack.
Is the host value intended to be a hostname through which outside clients can reach the LoadBalancer, with the idea being hitting difference hostnames can trigger different rules, e.g. host1.foo.com/bar can trigger a different rule than host2.foo.com/bar ?

Ah sweet, thank you!

Does the latest tag for the Docker images build automatically? eg can I
pull latest again and expect the fix?
On Dec 13, 2017 18:30, "Dave Cheney"<EMAIL_ADDRESS>wrote:

Closed #101 https://github.com/heptio/contour/issues/101 via #102
https://github.com/heptio/contour/pull/102.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heptio/contour/issues/101#event-1386887798, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABRW9BMYmayHXgHNskHrrbHwSC_I8sJiks5tAIg9gaJpZM4RBWIu
.

The :master tag updates automatically on commit.
https://github.com/heptio/contour/blob/master/docs/tagging.md
If you do something like
kubectl -n heptio-contour delete po -l app=contour
You'll pull the new image and you should be in business.
On Thu, Dec 14, 2017 at 1:32 PM, Adelbert Chang<EMAIL_ADDRESS>wrote:

Does the latest tag for the Docker images build automatically? eg can I
pull latest again and expect the fix?
On Dec 13, 2017 18:30, "Dave Cheney"<EMAIL_ADDRESS>wrote:

Closed #101 https://github.com/heptio/contour/issues/101 via #102
https://github.com/heptio/contour/pull/102.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/heptio/contour/issues/101#event-1386887798, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/
ABRW9BMYmayHXgHNskHrrbHwSC_I8sJiks5tAIg9gaJpZM4RBWIu>
.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/heptio/contour/issues/101#issuecomment-351590278, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcAxazjP86rIb103s7OHovzyTOR8swks5tAIjXgaJpZM4RBWIu
.

Just tried it, looks like it works - thank you for such a quick response!

np, thanks for trying contour.
On Thu, Dec 14, 2017 at 1:57 PM, Adelbert Chang<EMAIL_ADDRESS>wrote:

Just tried it, looks like it works - thank you for such a quick response!
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/heptio/contour/issues/101#issuecomment-351593914, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAAcAz7KHWdmwGRtC9reUSQKxgr6Xfz2ks5tAI6VgaJpZM4RBWIu
.


Add the ability to specify a lock file

I came around the issue in the old repo: https://github.com/roboll/helmfile/issues/779 while trying to achieve exactly the same thing. So I would like to be able to apply updates in one environment first and then rollout the same changes to the rest of the environments.
So would you accept this kind of change? What else would be good to have in terms of testing / documentation?

@lassizci Please fix DCO issue.

@lassizci need more e2e test.

@lassizci need more e2e test.

Allright! Which aspects would you recommend? Looking at the current ones, there doesn't seem to be lock file related e2e tests, but I could perhaps try to craft something together, if that's what we are looking for.

@lassizci need more e2e test.

Allright! Which aspects would you recommend? Looking at the current ones, there doesn't seem to be lock file related e2e tests, but I could perhaps try to craft something together, if that's what we are looking for.

yes. that's true.

@lassizci please fix DCO issue.

@lassizci please squash your commits.

Now, with a e2e test.

@lassizci I  have a question.
there is a raw chart in chart dir. why add raw-0.0.1? Thanks very much.

@lassizci I have a question.
there is a raw chart in chart dir. why add raw-0.0.1? Thanks very much.

The purpose of lock file is to freeze a chart to a specific version. To be able to test the lock file is effective, I thought multiple versions of the same chart would be needed. Would there be some other way to provide multiple versions of the same chart via local chart repo, than duplicating the chart?

@lassizci ok. I see.
I think moving raw to raw-0.1.0 will be more clear.
@mumoshu WDYT?

@lassizci ok. I see. I think moving raw to raw-0.1.0 will be more clear.
Done.

@mumoshu do you need me to do something?

@yxxhero If you could update code to use lockFilePath instead in favor of me, that would be awesome- I'll review the update asap and can approve/merge this earlier!

@mumoshu ok. I will see this PR later.

@lassizci @mumoshu lassizci:configurable-lockfile is not helmfile branch. It's not very convenient to change the code.
@lassizci could you update the code?

@yxxhero  @mumoshu Thanks for the feedback, sounds like reasonable thing, so lockFile now renamed to lockFilePath.

@yxxhero In case you missed that, maintainers of pull request base branches should be able to push and even force-push heads of pull requests, even though heads are in other repositories. FWIW, I usually use gh pr checkout $PR_NUM, make commits, then run git push without args to push commits to the pull request head.

@mumoshu got it. Thanks very much. great idea.


Increase test timeout to 30 minutes.

This increases timeout on tests from default 10 minutes, to 30 minutes.
This was observed at least once in #159, where integration tests build
failed because no output was received for 10 minutes.
More details: https://docs.travis-ci.com/user/common-build-problems/#build-times-out-because-no-output-was-received
Possible solution to #163

I'm closing it for now as this wouldn't solve the possible root cause.


Custom start page to display errors when all connection fails

In case the mobile device and computer can't connect to each each other, it would be great to have a custom start page that displays a message to users, instead of a 404 we currently get.

This issue has already been resolved.


Persist actors using redis / postgres / etc

While going through documentation I did found out key to persist actors but was unable to find out anything other than that. No documents or event tried to find code but was unable to do so. Is that feature already implemented or yet to implement?

@kunjee17 Persistance is currently not implemented. See: https://github.com/riker-rs/riker/pull/118

Thanks closing the issue for now.


vendor: update go-iscsi-helper

Longhorn/longhorn#5383
Signed-off-by: Derek Su<EMAIL_ADDRESS>

Just noticed go-iscsi-helper gets diverse based on different release branches like right now, we have master/1.3.x/1.2.x. The reason for that is because some feature-specific changes for different releases with coupling into this library, especially LonghornDevice like trim, expansion, etc.
However, ideally, it will be better to keep the library compatible w/o any branches to support all sustainable releases. For any changes based on interface, we should leverage the inheritance of OO to override the contract implementation instead of changing the underlining implementation. For example, for the newly added SetLunThinProvisioning in 1.4, we should have another device implementation like LonghornDevice2 to override the Start implementation instead of changing CreateTarget method directly which caused the branch diverse due to new things introduced to this common library.


JKNS-539: Add EC Required Labels

Override required labels to pass Enterprise Contract inherited labels check.

/retest


bugfix: failed to create 'volumefrom' container

Ⅰ. Describe what this PR did
old container has bind directory into container, such as "-v /tmp:/tmp",
when use 'volumefrom' to create new container, it will be failed when
setup volumes.
Ⅱ. Does this pull request fix one issue?

NONE
Ⅲ. Describe how you did it
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews
Signed-off-by: Rudy Zhang<EMAIL_ADDRESS>

Codecov Report

Merging #1161 into master will increase coverage by 0.02%.
The diff coverage is 0%.

@@            Coverage Diff             @@
##           master    #1161      +/-   ##
==========================================
+ Coverage   16.03%   16.06%   +0.02%
==========================================
  Files         174      173       -1
  Lines        9995     9929      -66
==========================================
- Hits         1603     1595       -8
+ Misses       8275     8217      -58
  Partials      117      117

Impacted Files
Coverage Δ

daemon/mgr/container.go
0% <0%> (ø)
:arrow_up:

pkg/utils/utils.go
78.22% <0%> (-0.35%)
:arrow_down:

daemon/mgr/cri.go
0% <0%> (ø)
:arrow_up:

daemon/config/config.go

I still suggest that add an integration test to cover this. @rudyfly

LGTM


Expand tests to all platforms

Currently we only test linux/amd64.

See https://github.com/devpow112/docker-base-ubuntu/pull/872 for PoC


Add functionality to support ArrayType(),Vector columns as well in normalizer function

This PR contains the support for ArrayType() columns of DataFrame in Normalizer function.
1). arr_to_vec function converts ArrayType() columns to DenseVectors.
2). Then I have created a user-defined function udf_arr_to_vec to turn Python function into PySpark function.
3). Finally search for all the columns from input_cols, which are not of Type of DenseVector. So convert all those columns into DenseVectors first and then do the normalization.
Note: After normalization, it will return Vector type as the column's type.

Coverage remained the same at 82.62% when pulling d3a59a4a4c0063cd36a48e7e5db5d3d5b05536e5 on deepakjangid123:master into 877657e3e82f5d7a7fcc90c4671baab1e4134f06 on ironmussa:master.

Great work! Thanks @deepakjangid123


Firebase Cloud Messaging

Hi,
we added new channel to be able to send push notifications to our mobile app with Firebase Messaging, would you be interested adding this as a built-in feature so we could plan a PR in the near future?
Thanks
Davor

Hi @davorpeic I'd like to keep the core clean, you're free to release a plugin just like I did for a Telegram notification channel: https://github.com/rias500/craft-telegram-notification-channel

Sorry for late answer
that sounds awesome and yes, you are right, its better not to fill it


AO-8242 Let APPOPTICS_DEBUG_LEVEL support string values

This PR is the fix of issue Go: APPOPTICS_DEBUG_LEVEL docs and implementation are different on Jira.
Now with this fix it supports both integers(for backward compatibility) and string values (case-insensitive, e.g., debug, INFO or Error).
[WIP] A test case fails in Go 1.9 (but works well in 1.7/1.8), which seems not to be related to the code changes made, but I need to take a look into it...

Codecov Report

Merging #27 into master will increase coverage by 0.17%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master      #27      +/-   ##
==========================================
+ Coverage   76.24%   76.42%   +0.17%
==========================================
  Files          21       21
  Lines        2303     2312       +9
==========================================
+ Hits         1756     1767      +11
+ Misses        496      495       -1
+ Partials       51       50       -1

Impacted Files
Coverage Δ

v1/ao/internal/reporter/oboe.go
89.07% <100%> (+1.36%)
:arrow_up:

v1/ao/internal/reporter/utils.go
63.63% <100%> (+1.93%)
:arrow_up:

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 29389e1...7f956f7. Read the comment docs.

[Update]
The (occasionally) failed test case is TestGRPCReporter , in which the second event (layer2) is sent (intentionally?) via the reportStatus channel. Theoretically two ConnectionInit events are sent out when the gRPC reporter is initialized, so the layer2 event generally will be the third one in the array. However, the order is not guaranteed by nature.
A short sleep before layer2 event fixes this issue.


pcli cannot deserialize AppParameters from testnet-preview

Describe the bug
pcli cannot deserialize AppParameters from testnet-preview
To Reproduce
Steps to reproduce the behavior:

git checkout main
PENUMBRA_NODE_PD_URL="https://grpc.testnet-preview.penumbra.zone/" cargo run --release --bin pcli v list-tx-hashes
see error

Expected behavior
pcli should be able to interact with grpc
Screenshots

Additional context
web clients are also unable to deserialize https://github.com/penumbra-zone/web/pull/443

FYI preview deploys were stuck today:

As of https://github.com/penumbra-zone/penumbra/pull/3717 that should be resolved, and we'll correctly be serving latest main again. However, at a glance I expect the problem to persist, because the intervening PRs don't seem to touch the logic in question. Will test after latest deploy finishes and confirm.

Indeed, still a problem:
❯ cargo run --release --bin pcli -- --home ~/.local/share/pcli-preview view sync
    Finished release [optimized] target(s) in 0.26s
     Running `target/release/pcli --home /home/conor/.local/share/pcli-preview view sync`
Error: status: Internal, message: "protocol error: received message with invalid compression flag: 52 (valid flags are 0 and 1) while receiving response with status: 404 Not Found", details: [], metadata: MetadataMap { headers: {"content-type": "text/plain; charset=utf-8", "x-content-type-options": "nosniff", "content-length": "19", "date": "Thu, 01 Feb 2024 00:14:20 GMT"} }

❯ git rev-parse HEAD
66b13e98643b8af8285238c62657ded81e8824f1

We can rule out these PRs as the cause of the problem:

https://github.com/penumbra-zone/penumbra/pull/3711
https://github.com/penumbra-zone/penumbra/pull/3714
https://github.com/penumbra-zone/penumbra/pull/3715
https://github.com/penumbra-zone/penumbra/pull/3703

because they hadn't been deployed at the time this issue was reported.

it seems to be working for me, now.

status: 404 Not Found - I think you're window manager setup made you so fast you frontran the deployment

For me too:
❯ cargo run --release --bin pcli -- --home ~/.local/share/pcli-preview view balance
    Finished release [optimized] target(s) in 0.27s
     Running `target/release/pcli --home /home/conor/.local/share/pcli-preview view balance`
Scanning blocks from last sync height 72 to latest height 72
[0s] ██████████████████████████████████████████████████       0/0       0/s ETA: 0s
 Account  Amount
 # 0      20000gm
 # 0      500000test_usd
 # 0      100cube
 # 0      10000pizza
 # 0      1000000penumbra
 # 0      20000gn

I think I hadn't waited long enough for the public endpoints to update. I'll think more about how we can catch this more proactively: we should have pcli view sync pass post-deploy at the least.

thanks!


camera only back press crash fixed

when every i open the camera and back press it crash the app

Nice one @shamsshykh


include a utility in-tree for generating "real" test minidumps

It would be nice to have some private crate that basically exists to crash and generate a minidump, to be added to testdata. Then if you want to check what a "real" minidump looks like for a certain situation you can just edit it locally and make a Fun New Crash. Presumably only written to use the native windows generator to start.
I have a feeling some of the others already have a version of this written for their own personal use?

Oh actually I wonder if Sentry/Symbolic has something like this already.

This would be interesting to do. For minidumps generated using Microsoft libraries there's a million different options which can be enabled. For macOS and Linux we'd have to use Breakpad or Crashpad. In mozilla-central we have nsTestCrasher.cpp to induce crashes with both regular and special reason. We might also need something like that.

#349 demonstrates that we can use synth-minidump to build up a minidump and write it to disk in tests. This eliminates some of my desire for this feature, but there's still some value in being able to generate "real" minidumps that we aren't circularly defining.

We've seen new streams and changes being introduced when writing minidumps with "default" options on Windows - such as the variable-size contexts. The way we discovered it was a useless signature on Socorro because it couldn't process the new minidumps properly, but we only noticed after it had gained a significant volume. If we could catch these changes in advance by just running tests on our machines we'd avoid these nasty surprises.

@Jake-Shadle wrote a sadness-generator crate to crash in various ways for testing his minidump-writing crates:
https://docs.rs/sadness-generator/latest/sadness_generator/


Can create issue without it'syouonline auth

Steps

sign out
try to create Issue in public repo

Issue

will direct you to sign in page with username and password without going to it'syouonline auth

Software Version
iyo_cleanup
f76784f3c51474c9dca3e5bf3ed3b5a1a3baba2e

Software Version
33648f9a0b9b41fc2f2bda0638ac783a96ebbdc4


DBZ-4156 DBZ-703 Remove deprecated code from PostgreSQL connector

https://issues.redhat.com/browse/DBZ-4156
https://issues.redhat.com/browse/DBZ-703

Test failure tracked via https://issues.redhat.com/browse/DBZ-4966


Introduce default var bitbucket_download_directory

Changes:
Introduce default var bitbucket_download_directory to support overriding the download path at role usage level.

Why don't just simply customize your bitbucket_download in case don't like the ~/.ansible/tmp?
Sorry for asking this because I keep synchronize all Ansible Roles under https://github.com/alvistack with similar setting, in case accepting this PR I need to ensure also benefit for other else use cases.

Thanks for your question. I thought about customizing bitbucket_download first, but it would be a maintenance nightmare for me to take care for the three components (url, dest and checksum) of each version.
By just extracting the download path I have no additional effort in the future when you update _bitbucket_download (and the other _***_download vars) for new versions.
But maybe I misunderstood your question?

After taking another look at the code I realize, that it would be cleaner to introduce three vars: bitbucket_download_directory, mysql_jdbc_download_directory and postgresql_jdbc_download_directory.
When you agree to this kind of change I would extend the pull request.

From my point of view, I hope to fetch the remote_tmp variable (see https://github.com/ansible/ansible/blob/devel/examples/ansible.cfg#L17) from playbook/task therefore you just need to set it up in a single place.

I understand. But changing remote_tmp won't meet my requirements.
I am using your role(s) to provision several vagrant boxes. I don't want to download the atlassian files over and over again after destroying and re-provisioning vagrant boxes (for development and testing purposes, sometimes multiple times per day).
The introduced var bitbucket_download_directory enables me to store the downloaded files (and only these) outside of the vagrant box. So these files can be reused later. Using and changing remote_tmp would store much more files in my "caching" directory.

@mrtwnklr First of all let's review the initial requirement for download assets into ~/.ansible/tmp/ with current logic:

We need a way to handle initial install or upgrade. If the target file assets not exists, we assume for a new install or upgrade, so purge existing data and do the extract/install/compile/etc
We need a way to skip duplicated install. If the target file assets already exists with expected checksum, we assume initial installation done so skip it
We need a way to manually trigger reinstall. Similar as case above, just simply remove the existing file assets and rerun the role/playbook will trigger the reinstallation

Therefore we need to download the file assets from network. If you reuse the cache folder across multiple newly-cleanly-started vagrant boxes, the remaining boxes will simply skip the installation as file assets already exists...
P.S. From the other point of view, with vagrant you could use sync folder + rsync (see https://www.vagrantup.com/docs/synced-folders/rsync.html). In this case you could always sync the ~/.ansible/tmp/ if you truly understand this role's logic.

Thank you for your fast response. I understand the current logic. I did not do a deep dive into the role before. Now I see that my change will not meet my requirements in the long run. I have to think about it.

Thank you for your understanding. Let's reopen this PR again, e.g. if we could find a way to centralize the target path into remote_tmp.


make package fails after merging with dev branch

Hi, I saw that you posted a pull request with some changes that looked important, so I decided to pull them by doing this:
git pull origin dev

After this I executed make install Carla.. ... and then make pythonAPI and make launch, all of which ran succesfully.
However make package give me the following error:
 LogInit: Display: Warning/Error Summary (Unique only)
  LogInit: Display: -----------------------------------
  LogInit: Display: LogDReyeVR: Error: [ConfigFile.h::ReadFile:184] Unable to open the config file "C:/CarlaDReyeVR/carla/Unreal/CarlaUE4/Config/EgoVehicles/model3.ini"
  LogInit: Display: LogConsoleManager: Warning: Setting the console variable 'r.Streaming.PoolSize' with 'SetByScalability' was ignored as it is lower priority than the previous 'SetByProjectSetting'. Value remains '4000'
  LogInit: Display: LogModuleManager: Warning: ModuleManager: Unable to load module 'ExampleDeviceProfileSelector'  - 0 instances of that module name found.
  LogInit: Display: LogScript: Warning: Script Msg: A null object was passed as a world context object to UEngine::GetWorldFromContextObject().
  LogInit: Display: LogTemp: Warning: LogitechWheelPlugin initiated!
  LogInit: Display:
  LogInit: Display: Failure - 3 error(s), 9 warning(s)
  LogInit: Display:

  Execution of commandlet took:  159.75 seconds
  LogShaderCompilers: Display: Shaders left to compile 0
  LogTemp: Warning: LogitechWheelPlugin shut down!
  LogHttp: Display: cleaning up 0 outstanding Http requests.
  LogContentStreaming: Display: There are 1 unreleased StreamingManagers
Took<PHONE_NUMBER>s to run UE4Editor-Cmd.exe, ExitCode=1
ERROR: Cook failed.
       (see C:\CarlaDReyeVR\UnrealEngine\Engine\Programs\AutomationTool\Saved\Logs\Log.txt for full exception trace)
AutomationTool exiting with ExitCode=25 (Error_UnknownCookFailure)
BUILD FAILED

-[Package]: [ERROR] There was a problem while packaging Unreal project.
          [ERROR] Please read the screen log for more information.
make: *** [package] Error 1

The problem lies with the model3.ini file, which is actually called TeslaM3.ini . I tried to change the name of the file, but that interfered with other commands and gave more errors. I am not sure how to edit the command that requires model3.ini file to change it to TeslaM3.ini .
Should I revert back to the previous state? Or could you help me fix this issue if the issue isn't too complicated?
I am also including the log file:
Log.txt
@GustavoSilvera

Hi, please don't rename the files. Everything is working as intended and the old file is model3.ini while the new file is TeslaM3.ini (since this pr includes the ability to use more than just one ego vehicle).
This error is happening because of a conflict between old files (that haven't yet been deleted) and new files that you just installed, specifically the old model3 blueprint directory has been revamped in the new version. You should first check out the "Upgrading DReyeVR" to run a make clean and then reinstall.

Thanks, that worked.


Update Documentation

https://github.com/Azure/EasyAuthForK8s/blob/master/docs/detailed-architecture.md is currently empty

https://github.com/Azure/EasyAuthForK8s/blob/master/docs/setup-instructions.md is currently outdated with deprecation errors.


[Communication] - Phone Numbers - Added async samples

Added missing async samples and fixed the syntax for search and list numbers samples.

/azp run python - communication - tests


adjusted configmap template

I'm deleting this PR, I'm working on the Template, I just wanted to get a test on the argocd scripts. I don't want it all to look different.


config directory is not created on first launch

on first launch directory $HOME/.config/geektray is not created when not existing so configuration file cannot be written to
Error: write config file

Caused by:
    No such file or directory (os error 2)

so I had to manually create it

This is fixed in https://github.com/emonkak/geektray/commit/fdfb3d198f30ead408cf5225620d32322e2772f1. Thanks for the report.


?? i have userscript running and i'm in a game

do you have server and UUID inserted into config?

and yes i have my uuid inserted

Userscript edited and installed correctly?

yea i fixed it now thanks easy rider :)

How did you fix it?

i screwed up one of the files when editing it so i redownloaded orig and replaced some of the files :)


Can not re-login and refresh after revoke from GitHub

I am not live in Kuala lumpur nor Malaysia.
I want to reload but I misclicked app revoke from GitHub.
I can not refresh info and can not re-login to git-award. :(

Screenshot:

got same problem

Thanks for reporting this. it should be fixed now


Update VtR

Signed-off-by: Alessandro Comodi<EMAIL_ADDRESS>This PR updates VTR to the latest conda version.

Looks like CI failed?

@mithro Yes, Travis CI failed to find the latest conda-package of VTR which was correctly compiled in the latest update: https://travis-ci.com/SymbiFlow/conda-packages/jobs/238131054. I am trying to see what could cause this behavior.

Here there's the error message:
WARNING: The --force flag will be removed in a future conda release.
         See 'conda install --help' for details about the --force-reinstall
         and --clobber flags.

Collecting package metadata (current_repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.
Collecting package metadata (repodata.json): done
Solving environment: failed with initial frozen solve. Retrying with flexible solve.

PackagesNotFoundError: The following packages are not available from current channels:

  - vtr==7.0.5_8325_g46b95c7e9=20190923_110951

Current channels:

  - https://conda.anaconda.org/symbiflow/linux-64
  - https://conda.anaconda.org/symbiflow/noarch
  - https://conda.anaconda.org/pkgw-forge/linux-64
  - https://conda.anaconda.org/pkgw-forge/noarch
  - https://conda.anaconda.org/conda-forge/linux-64
  - https://conda.anaconda.org/conda-forge/noarch
  - https://conda.anaconda.org/m-labs/linux-64
  - https://conda.anaconda.org/m-labs/noarch
  - https://repo.anaconda.com/pkgs/main/linux-64
  - https://repo.anaconda.com/pkgs/main/noarch
  - https://repo.anaconda.com/pkgs/r/linux-64
  - https://repo.anaconda.com/pkgs/r/noarch

To search for alternate channels that may provide the conda package you're
looking for, navigate to

    https://anaconda.org

and use the search bar at the top of the page.

@acomodi That revision doesn't appear in the repo @ https://conda.anaconda.org/symbiflow/linux-64 - where did you get the value from?

@mithro From the Travis CI build of conda: https://travis-ci.com/SymbiFlow/conda-packages/jobs/238131054

Closing this PR as it needs the tile tags to successfully build. Including VtR update in: https://github.com/SymbiFlow/symbiflow-arch-defs/pull/1017


Fix issue with bad table prefix

Questions
Answers

Description?
I changed the prefix in the SQL query, so the extra underscore was removed.

Type?
bug fix

BC breaks?
no

Deprecations?
no

Fixed ticket?
Fixes #31219 https://github.com/PrestaShop/PrestaShop/issues/31219

Sponsor company
Prestaworks AB

How to test?
Follow instruction in issue

Just to be sure, I checked https://github.com/PrestaShop/PrestaShop/blob/<IP_ADDRESS>/install-dev/sql/db.sql if it was not due to some old typo, but all good. ✅

Hi @Prestaworks @Hlavtox,
I added the Blocked label because the issues have not been verified by the QA team.
As soon as the "Verified" label has been applied by the QA on this issue, we will test this PR.
Thanks!

Hi @Prestaworks
as said in this comment https://github.com/PrestaShop/PrestaShop/issues/31219#issuecomment-1432316736
this one will be tested by a dev, ping @PrestaShop/prestashop-core-developers
Thanks

I wanted to try your PR but I have same issue than https://github.com/PrestaShop/PrestaShop/issues/30761

I confirm this change is definitely needed

thank you @Prestaworks !


[WIP] Tree generation

[x] Implement a Schematic type for storing structures and writing parts of them which overlap with a chunk to the chunk
[ ] Implement tree schematic generators
[ ] Implement a tree finisher, with tree types/density based on biomes

I noticed a severe performance impact from adding this, and noticed a rather peculiar cause when investigating:

bitvec is for some reason the main overhead for worldgen, which seems somewhat odd...


Ability to limit commands to certain channels

As suggested by @SaintPeter. Could also lead to confusion about what features are available where, so this is a feature we may want to approach with caution, but it's worth putting up for discussion.

I'm thinking that if there are particularly spammy commands we would limit them.  The command could be replaced with a message like:

Command commandName is not available in this channel due to the volume of its output.

Or something simple like that.  We wouldn't fail silently.
Thinking about how to do this:
var disableCommands = {
  'roomName' = [
    "commandName1",
    "commandName2",
    "commandName3"
  ]
}

We could also use that with:
var spammyCommands = [
    "commandName1",
    "commandName2",
    "commandName3"
  ]

To assign them quickly to many rooms.
Then it's just a matter of checking the object for the room name and doing an indexOf on the array.

It took a little digging... Looks like Gbot.findAnyReply is a good place to start.


Expose accessory port to the local network only

Exposed docker ports are publicly accessible since Docker bypasses UFW rules
This change exposes port 4567 from the accessory only to the local, "kamal" network so the proxy can access it but the public can't

Thanks a ton for your contribution! 🙌


Add missing types for ImageJ

This pull request was created from branch, so that needs to happens first.
This addresses https://github.com/clEsperanto/clesperantoj_prototype/issues/60

This pull request adds the missing data types int8, int16, int32 and uint32 to the imageplus converter.
It also contains the corresponding push and pull tests for imageplus.
@StRigaud

No more error on my side after a quick test running this:
https://github.com/clEsperanto/clij3/blob/a0b80e70ad2a3ab59047d4af8783a1885915cfde/src/main/java/net/clesperanto/test/YetAnotherPlayground.java#L12-L31
I have the correct output.
Simple question though is it normal the output is of type 8-bit for FIJI ?

my bad, the return is 32-bit

One remark is that the tests might fail at some point if many actions are running in parallel and the runners run out of memory.


I can't install any extension

Issue Type: Bug
when installing an extension I get the error
Error installing extension. See the [log] (command:workbench.action.showWindowLog) for more details.
VS Code version: Code 1.69.2 (3b889b090b5ad5793f524b5d1d39fda662b96a2a, 2022-07-18T16:12:52.460Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: Yes

Hi @JoseLuisUicab can you please share more details about this issue, if it is related to VS Code
Please create your issue here https://github.com/microsoft/vscode/issues

Since we haven't heard back from you in a while, we assume the issue is resolved. Feel free to create a new ticket if you have any other issues.


Branching out

Checklist

[x] I ran npm test locally and it passed without errors.

[x] I only edited the _data/pixels.json file.

[x] I entered the username in the pixels.json that I'm also using to create this pull request.
[x] I acknowledge that all my contributions will be made under the project's license.

Trying to get the old one to work.


TrayIcon not supported ?

Hi,
I just tried "Material.Avalonia" version 2.5.1 and i must say that i like it. That said, since i moved to it i noticed that right clicking the icon does not show the "NativeMenu" anymore. Is it a problem on my side ?
Thanks!

Hello
Maybe you need to add additional styles. For example NativeMenuBar style from Avalonia UI repo to you application

Hi @SKProCH , thanks for the fast reply. I'm new to wpf/ava so I was not sure in which direction to look. I'll report my findings here, probably next week.
Thanks again,
David.

Hi,
I tried to include the NativeMenuBar style but it seems it's not enough (the menu doesn't open).
For information here is my App.axaml :
<Application xmlns="https://github.com/avaloniaui"
             xmlns:x="http://schemas.microsoft.com/winfx/2006/xaml"
             xmlns:themes="clr-namespace:Material.Styles.Themes;assembly=Material.Styles"
             xmlns:local="clr-namespace:LanClient"
             x:Class="LanClient.App">
  <!-- Avalonia 11.0.0-preview4 -->
  <!--
    <Application.Styles>
        <themes:MaterialTheme BaseTheme="Dark" PrimaryColor="Blue" SecondaryColor="Orange" />
        <StyleInclude Source="avares://Material.DataGrid/DataGrid.xaml" />
        <materialIcons:MaterialIconStyles />
    </Application.Styles>
    -->
  <!-- Avalonia 11.0.0-preview4 -->
  <Application.Resources>
    <themes:BundledTheme BaseTheme="Dark" PrimaryColor="Blue" SecondaryColor="Orange" />
  </Application.Resources>
  <Application.Styles>
    <StyleInclude Source="avares://Material.Avalonia/Material.Avalonia.Templates.xaml" />
    <StyleInclude Source="avares://Material.DataGrid/DataGrid.xaml" />
    <StyleInclude Source="avares://Avalonia.Themes.Fluent/Controls/NativeMenuBar.xaml" />
  </Application.Styles>
  <Application.DataContext>
    <local:AppViewModel />
  </Application.DataContext>
  <TrayIcon.Icons>
    <TrayIcons>
      <TrayIcon Icon="/Assets/lan.ico" ToolTipText="LanManager" Clicked="OnTrayIconClicked">
        <!-- TODO: https://github.com/AvaloniaCommunity/Material.Avalonia/issues/211 -->
        <TrayIcon.Menu>
          <NativeMenu>
            <NativeMenuItem Header="Open" Command="{Binding  OpenCommand}" />
            <NativeMenuItemSeparator />
            <NativeMenuItem Header="Exit" Command="{Binding ExitCommand}" />
          </NativeMenu>
        </TrayIcon.Menu>
      </TrayIcon>
    </TrayIcons>
  </TrayIcon.Icons>
</Application>

Ok, I'll try to look at this

Hi,
There's no urgency on my side, so take your time :)
For information I also tested with latest versions (avaui 11.x, etc) with the same problem.

Seems like this is implemented already at this moment:


breaks if gitolite user is not 'git'

Hello
So im about to use this plugin now but I can't get it working
my gitolite runs under the user 'redmine' so I changed
:gitolite_user                  => 'redmine',
whenever I try to configure the package I get internal error
The logfile prints:
2015-10-22 05:20:34 +0200 [ERROR] Error while getting Gitolite infos, check your SSH keys (path, permissions) or your Git user.
2015-10-22 05:20:34 +0200 [INFO] Testing if Redmine user 'redmine' can sudo to Gitolite user 'git'...
2015-10-22 05:20:34 +0200 [ERROR] Error while testing can_redmine_sudo_to_gitolite_user
2015-10-22 05:20:45 +0200 [ERROR] Error while getting Gitolite infos, check your SSH keys (path, permissions) or your Git user.
I've done a lots of reloading and checked the changes of init.rb apply - they do. but it still breaks on this part.
Why does it need to sudo into 'git'... its not used! where does this git-user come from?
--
are the default-settings from init.rb are cached/stored somewhere?
--
nevermind - its stored in the database after migration I think. You should mention to check the init.rb config-settings before installation in your 'Get started'!
Thanks

I also bumped into this problem, but, after while, I found this: http://redmine-git-hosting.io/how-to/maintain/ , "To restore/update your plugin settings" section.

My user 'gitolite' differs from default 'git', that's why I try to change the plugin parameter for gitolite_user as well.
Unlike nightreaver I don't get the plugin to recognize my modifications (*1):

2016-08-20 18:59:25 +0200 [ERROR] Error while getting Gitolite infos, check your SSH keys (path, permissions) or your Git user.
2016-08-20 18:59:25 +0200 [INFO] Testing if Redmine user 'redmine' can sudo to Gitolite user 'git'...
2016-08-20 18:59:25 +0200 [ERROR] Error while testing can_redmine_sudo_to_gitolite_user
2016-08-20 18:59:25 +0200 [ERROR] Error while getting Gitolite infos, check your SSH keys (path, permissions) or your Git user.

I've followed two approaches as described in the docs (*2).
(a) Utilize redmine_git_hosting/settings.yml
I first tried to adapt the default_settings.yml and saved it to plugin's main folder as settings.yml. After updating the database it became obvious that the change of gitolite_user didn't seem to have any effect (*3). The correction might be valid, cause chaging a string is all it needs. The plugin was still looking for 'git', not 'gitolite'.
Did I miss a step to set up the settings.yml?
While restoring the default settings the command line signals that it's processing updates in init.rb.
(b) Changing redmine_git_hosting/init.rb
Google didn't bring up an example init-ruby-file. This is what I ended up as a plausible solution.
settings({ partial: 'settings/redmine_git_hosting', default: RedmineGitHosting.settings, gitolite_user: 'gitolite' })

After updating the database it became obvious that appending gitolite_user isn't a solution here.
Is the variable gitolite_user expected to be a subordinate of default?
Redmine 3.2 is running on Apache Passenger with Redmine Git Hosting (1.2.0) and Gitolite3.
Great appreciation for redmine_git_hosting! :) I'm just starting to get familiar with the concepts of ruby, gems and bundler.
Thanks in advance for your valuable hints and support.
References for other readers looking for a solution:
*1: Docs: Configuration variables
*2: Docs: Configuration notes
*3: Docs: Restore/update plugin settings

Hi! Thanks for your report! Actually there is a bug with the settings.yml file feature. I'm investigating.

@cschlusche about the init.rb file :
Before RGH 1.2, default settings was stored in plugin's init.rb file : example.
Now default settings are stored in lib/default_settings.yml. This file must not be edited by users.
Instead copy the settings you want to override in redmine_git_hosting/settings.yml then do a
 RAILS_ENV=production rake redmine_git_hosting:restore_default_settings
Explained here : http://redmine-git-hosting.io/configuration/notes/#a-note-about-the-path-variable


Choice of SVD gradient

Can you give me some insights on your choice of SVD derivative vs Tensorflow implementation (https://people.maths.ox.ac.uk/gilesm/files/NA-08-01.pdf) and Pytorch implementation(https://j-towns.github.io/papers/svd-derivative.pdf)?
Are those three comparable or replacable? Sorry I am not a linear algebra guy so my question may sound weird.

Basically, three derivative functions are based on paper.
"Ionescu, Catalin, Orestis Vantzos, and Cristian Sminchisescu. "Training
deep networks with structured layers by matrix backpropagation." arXiv
preprint arXiv:1509.07838 (2015)."
Tensorflow implementation is same with the paper. But in some cases, it has
redundancy and may occur Nan value.
So, I implemented new derivative function which problems are solved.
I don't know Pytorch's derivative function but I think that it is same with
Tensorflow's.
If you want detail of my implementation, check my paper.
Best regards,
Seunghyun Lee
On Wed, Aug 21, 2019 at 3:56 AM jonkoi<EMAIL_ADDRESS>wrote:

Can you give me some insights on your choice of SVD derivative vs
Tensorflow implementation (
https://people.maths.ox.ac.uk/gilesm/files/NA-08-01.pdf) and Pytorch
implementation(https://j-towns.github.io/papers/svd-derivative.pdf)?
Are those three comparable or replacable? Sorry I am not a linear algebra
guy so my question may sound weird.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/sseung0703/KD_methods_with_TF/issues/15?email_source=notifications&email_token=AGGUU26PYHFFOWSLS33T4H3QFQ44LA5CNFSM4IN3NXP2YY3PNVWWK3TUL52HS4DFUVEXG43VMWVGG33NNVSW45C7NFSM4HGKNAKA,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGGUU2YHVDYRIFO6CDPI2ULQFQ44LANCNFSM4IN3NXPQ
.

Basically, three derivative functions are based on paper.
Ionescu, Catalin, Orestis Vantzos, and Cristian Sminchisescu. "Training deep networks with structured layers by matrix backpropagation." arXiv preprint arXiv:1509.07838 (2015).

Tensorflow implementation is same with the paper. But in some cases, it has
redundancy and may occur Nan value.
So, I implemented new derivative function which problems are solved.
I don't know Pytorch's derivative function but I think that it is same with
Tensorflow's.
If you want detail of my implementation, check my paper.


clearFilters() will cause crash due to non-nullable type

Hi @pedroSG94 , my program was crashing when using clearFilters() and I believe I found a bug due to Kotlin and null "safety" features.
https://github.com/pedroSG94/RootEncoder/blob/a4ab764acc90f5b54161700bc76aef65eae144a3/encoder/src/main/java/com/pedro/encoder/input/gl/render/MainRender.kt#L143
1) In MainRender.kt, baseFilterRender is declared non-nullable
fun setFilterAction(filterAction: FilterAction?, position: Int, baseFilterRender: BaseFilterRender) {

2) In GlStreamInterface.kt and OpenGlView.java clearFilters() will set filter position 0 to null
  override fun clearFilters() {
    filterQueue.add(Filter(FilterAction.CLEAR, 0, null))
  }

This will set baseFilterRender to null within the Filter instance
3) In GlStreamInterface.kt and OpenGlView.java draw() functions when it reaches the following line that calls mainRender.setFilterAction it will crash since baseFilterRender is null, and the field is non-nullable
if (!filterQueue.isEmpty() && mainRender.isReady) {
      try {
        val filter = filterQueue.take()
        mainRender.setFilterAction(filter.filterAction, filter.position, filter.baseFilterRender)
      } catch (e: InterruptedException) {
        Thread.currentThread().interrupt()
      }
}

Log Message
E/AndroidRuntime(10351): java.lang.NullPointerException: getBaseFilterRender(...) must not be null
E/AndroidRuntime(10351):        at com.pedro.library.view.GlStreamInterface.draw(GlStreamInterface.kt:165)
E/AndroidRuntime(10351):        at com.pedro.library.view.GlStreamInterface.onFrameAvailable$lambda$0(GlStreamInterface.kt:208)
E/AndroidRuntime(10351):        at com.pedro.library.view.GlStreamInterface.$r8$lambda$F3uPVoonfZHixlk2XWkWc7gH68U(Unknown Source:0)
E/AndroidRuntime(10351):        at com.pedro.library.view.GlStreamInterface$$ExternalSyntheticLambda0.run(Unknown Source:2)
E/AndroidRuntime(10351):        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
E/AndroidRuntime(10351):        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:644)
E/AndroidRuntime(10351):        at java.lang.Thread.run(Thread.java:1012)

The Possible Fix
In MainRender.kt, set baseFilterRender to be nullable
fun setFilterAction(filterAction: FilterAction?, position: Int, baseFilterRender: BaseFilterRender?) {

And this is why I'm not the biggest fan of some of these new null-safety languages.  They allow you to compile that code, but during run-time it will crash due to type mismatch.

Hello,
Thank you for the report. Fixed here:
https://github.com/pedroSG94/RootEncoder/commit/0459e74e85c9e199074faa21f48b948d4b1dde06#diff-6efae85175ec84932391ca387cfe4ec3e708b70dac3c36613daac656c4b561ea
You can use it with this gradle while I upload a new version:
  implementation 'com.github.pedroSG94.RootEncoder:library:0459e74e85'
``

Thank you @pedroSG94

Closing as fixed


How can I change metallic or roughness factor in runtime?

Hi, i'm already read issue #41, but it hasn't enough information.
How can I change metallic or roughness factor in runtime?
For example, in sample project hellosceneform, I want to change Andy's metallic factor "0" to "1" in runtime.

Get the material from a  node and set properties defined in the MaterialFactory.
see:
https://developers.google.com/ar/reference/java/com/google/ar/sceneform/rendering/Material
https://developers.google.com/ar/reference/java/com/google/ar/sceneform/rendering/MaterialFactory
Material material = node.getRenderable().getMaterial();
material.setFloat(MaterialFactory.MATERIAL_METALLIC,  /* 0 or 1 for metallic / );
material.setFloat(MaterialFactory.MATERIAL_ROUGHNESS, / 0 to 1 */);

You save my day! thanks a lot.

@malik-at-work I have imported my models but textures are not applied properly. I think the issue is with these metallic and roughness factors. Why we can't get these values from model?


facility decls w/ name matching enclosing-module-name causes codegen problems...

Here's an interesting problem I stumbled into today. Look at this:
Facility Priorit_Fac;
        uses Standard_Integers, Standard_Booleans, Basic_Integer_Theory;
    Definition LEQV(x, y : Z) : B is x <= y;

    Operation Are_Ordered (restores i, j : Std_Integer_Fac :: Integer) :
            Std_Boolean_Fac :: Boolean;
        Procedure
            Are_Ordered := (i<=j);
    end Are_Ordered;

    Facility Priorit_Fac is Prioritizer_Template
            <Std_Integer_Fac :: Integer>(4, LEQV)
        implemented by Priorit_Heap_Impl(Are_Ordered);
...

attempting to generate code for this produces the following error:
cannot find symbol   symbol:   method Are_Ordered(RType,RType)   location: variable Priorit_Fac of type Prioritizer_Template

Generated code for the facility decl looks like this:
    public static final Prioritizer_Template Priorit_Fac = new Priorit_Heap_Impl(((Integer_Template)Standard_Integers.INSTANCE).initInteger(),
     ((Integer_Template)Standard_Integers.INSTANCE).initInteger(4),
     new BaseOperationParameter() {
            @Override public RType op(RType... e) {
                                return Priorit_Fac.Are_Ordered(e[0], e[1]);
            }
        });

the problem occurs at return Priorit_Fac.Are_Ordered(e[0], e[1]);. Confused? Well, turns out the name of the enclosing module is also Priorit_Fac (imagine that..). Anyways, we might need to restrict this. Not sure yet if something should change in codegen or the with semantic analysis..

Here's a potentially simple solution for this:
Add a 'dummy' symbol to module scope with the same name as the module. This way when someone tries to declare an operation, facility, etc matching the name of the module, it will trip a duplicate symbol exception...
This is all well and good, but I have concerns about the quality of the outgoing error message from this. It would be nice to simply special case the logic somewhere reliable: that is, somewhere where we can print a special duplicate symbol exception message informing people that they shouldn't name their things the same as the outmost module (really this is for codegen reasons primarily but I'm sure there's other places within actual resolve sourcecode that could create issues)..

Fixed (I think) as of cadf2fd4e9f89aea5ffe510b31e3c4e5a067f0b6. Reopen if needed.


Design feedback on lazy_load_blob

I think the idea of enabling middleware to just receive the head of a request, and forward it, and only have the final recipient return a response (link) is a great idea (out of curiosity, did you come up with that or did you get it from somewhere else?)
However, I see an issue with the current implementation: AFAICT, only the last lazy_load_blob received by a process is remembered by the kernel. So what if the middleware needs to make another request before forwarding that lazy_load_blob to the next destination, e.g. to fetch some info?

Each request could have a unique ID, and you could fetch a particular lazy_load_blob via that ID?

We have unique IDs for every message, but currently don't expose that to the process. The thought is that processes should use state of some kind to manage their data rather than keep track of a bunch of request IDs. I'm hesitant to change this property because it's been nice, so far, to treat messages as nothing more, and build state machines that react to them.
With regards to fetching, we've so far been able to avoid the issue of memory leakage by only tracking outgoing requests that expect a response (which must be associated with a timeout). If we added functionality to retrieve arbitrary data from past messages, wouldn't we need to start baking in some logic around expiry, which becomes difficult to mentally model as a process developer?

So this most recent proposal of hanging onto the last blob is similar to something I was considering recently: holding onto last prompting_message until one with er != None or rsvp != None comes in. The downside here is that it can lead to unexpected behaviors if you have a lot of er == None && rsvp == None Requests, because I have this very long-lived state that is no longer relevant to me.
The one-only is really nice for expiry, as you say above.

One way you can do the specific case asked about above right now is:

Middleware A receives msg with blob; final destination is Process F
Middleware A makes request to Process B to get add'l info; it attached blob via inherit = true
Middleware A receives response from Process B which also inherit = true to pass the same blob back along with the information
Middleware A passes info + blob via inherit = true to Process F

I think in our system as currently implemented this will involve a fair amount of copying that blob around; in principle it should involve no copying of the blob and so should be efficient.
In practice, this is p fragile and annoying and requires that Process B be controlled by the dev of Middleware A since it has to cooperate to pass the blob back.
I think the general question still stands and it would be nice if this were easier.

One idea would be to have some sort of stack discipline: when making the additional request, the middleware tells the kernel "this new request is nested within the current request [the one with the lazy_load_blob]".
So the kernel knows that that lazy_load_blob must be kept around until the response to the nested request arrives (or a timeout occurs).

Yeah nesting is good. We have a field called inherit that marks whether a message "inherits" the ID, context, and blob of the previous message. We could alter the logic of inheritance to build a stack (would just look like stacking instead of replacing when you inherit and assign a blob at the same time?).. then we just need a way to "pop" from it to consume the stack...

Man, I wrote a long thing out here that I liked, but closed the window and lost the text. The second time I write it will be better anyways...

Looking at all the logic below, which I've drafted a few times, I'm convincing myself not to add a stack. It's a layer of mental overhead we've been very productive without, so far. I'd like to explore other avenues for performance, rather than introduce this complexity just for the sake of blobs. They are cool, but the simplicity of handling a message stream directly is even cooler. Lastly, we can address the specific use-case in discussion here (and others) with @hosted-fornet's idea to "hang on to the last blob". We should definitely not toss away our single-frame until it gets replaced by something newer.
To be clear I think there are many stack-based solutions that can work, I'd just prefer to have processes handle this task in-house until we're certain that the kernel should provide such a thing. The performance cost can be addressed in entirely different ways in the future--we've been super lazy about optimizing around the Wasm boundary, preferring to get the userspace semantics right first...

We can add a stack for incoming messages. The main question is how to, as a process, choose between operating on incoming responses or the current "outstanding request" stack frame when inheriting blobs and context.
You must always be able to respond to all requests that expect a response. I'm happy with enforcing that they must be responded to in LIFO order. In general I think it's optimal for processes to respond to requests as they are received, and although the stack has utility for advanced use-cases, the majority of processes will only ever require the most recent message. Since processes are usually stateful, they store any necessary information about historical messages in their state rather than in their stack.
Incoming requests are added to the stack. Each request in the stack retains all of its information including blob. When a response is sent, requests are popped off the stack until one expects_response. The response is paired to that request, which is also removed. If the incoming request stack is empty, or does not contain any which expect a response, the response is dropped (matches current behavior).
Incoming responses are not added to the stack. Instead, they are matched against the outstanding request table. This is the current machinery in place and it works well.
The only issue now is inheritance in the case where a response has just been received and there are request(s) in the incoming request stack. The next message sent could either inherit the blob from the response, or the stack.
I think this is best resolved by having get_blob() act as a pop instead of just a fetch, but only on responses. Meaning: when you call get_blob(), if your most recent inbound message was a response, you get its Option<LazyLoadBlob>. But if you call it again, you fetch from top of request stack.

I think it's very powerful for a process to be able to respond to requests in an arbitrary order. I wouldn't easily give that up. (And you probably mean FIFO? The first received request must be the first for which a response is sent?)
Here's how I would do it:
If a request Req1 comes in, the process may make another request Req2, and mark that as nested within Req1.
For the kernel, this means, it will keep Req1 around (including its lazy_load_blob) until a response for Req2 is received or a timeout occurs. (This is the "stack" idea, but it's not really a stack - it never grows beyond one remembered request for a nested request.)
Any other requests or responses that are received in the meantime can be handled by the process as it wishes. It may make other nested requests for received requests - the kernel will keep them around, too.
Once the response for Req2 is received, the process may now retrieve the lazy_load_blob from Req1 or forward it (inherit).
But what if a middleware needs to make 2 or more requests before forwarding a request? It could be possible to send a nested request also on receipt of a response. So when the response for Req2 is received, the process can make another nested request Req3 for Req1, and the kernel will continue to keep it around, until a response for Req3 is received. This way, a process may make any number of requests (serially) during the handling of an original request.
In summary, there is not really a stack. A request will be kept around if during handling it, the process makes a nested request. It will also be kept around if the process makes another nested request during handling of a response to a nested request.
Of course, I am not familiar with your code, but this sounds quite simple and powerful to me.
The kernel would need a map request ID -> request for any requests for which a nested request was made and a second map request ID -> timestamp to handle timeouts.

Ah yes I meant FIFO. Thanks for explaining the depth=1 nature of the "stack" idea here, it makes things easier for sure.
I'm wondering if it's possible for the kernel to nest automatically rather than make the process "mark" nested requests. If you receive a request that expects a response, is every subsequent message you send, until you make a response, nested? You can only ever issue a response to the last request you received--FIFO.
process calls `receive()`

1. process receives request(A)
    the context of the process is now entirely centered around (A), meaning that's the blob fetched, request ID etc
         a. process sends a response
            this response is issued to request(A), clearing it from kernel.
         b. process sends a request(B)
            request(A) is saved as it nests, and will be retained
            (A) is still the context until `receive()` gets called
            (A) will become the nested context if response(B) is received (see below)
         c. process does nothing (calls `receive()` again without sending any messages)
            request(A) is dropped from kernel and forgotten

2. process receives response(Z)
     the context of the process is centered around (Z), but if (Z) is nested under a request(Y), context(Y) is accessible
         a. process sends a response
             this response is issued to request(Y) if it exists and is dropped otherwise
         b. process sends a request(X)
             if request(Y) exists, it is saved as the nested request
             response(Z) is forgotten
         c. process does nothing until next `receive()`
             response(Z) and request(Y), if it exists, are both forgotten

Mostly writing this out for my own understanding--it seems good to me.
Now the last "problem", in case 2: if request(Y) exists, it's nested under (Z), which means calling get_blob() will give you (Z)'s blob. That means we need a new function to get_nested_blob() -- same function signature, returns option<lazy_load_blob>. Could this be the solution? Will this "just work"?

I'm implementing the above now and (perhaps selfishly) wondering if get_nested_blob() even makes sense to add. If you want to seamlessly inherit it, that works fine as described above. If you actually want to ingest it, it's not unreasonable to tell the developer that they should ingest it when they first get the request.

Another thing that's come up during implementation is that it's not possible to inherit a blob from a response.
The previous design allowed it, because it just used whatever message was received last. But if you properly leverage request inheritance, meaning that responses are always routed exactly where they are intended to end up (at the originating request) it should be the case that responses should always go to their final destination, meaning that it would never make sense to inherit a blob from one anyways.
I think the overarching trade-off here is one of simplicity vs. optionality. Of course we could enable more general use by adding more fields, flags, etc, but it seems like we're already at the boundary where more choice would lead to an overcomplicated mental model... I'm inclined to say that more complex protocols should achieve their complexity by storing more information in their request and response bodies.


Tool to show security.txt file

Add a tool which detects a security.txt file (as per https://securitytxt.org/).
This could be a standard side tool which is enabled when the file is present on a site (with suitable icon change) and when clicked shows the relevant info, providing clickable links.
This will make it easier for researchers to find the relevant bug bounty program that they should submit any issues with the site to.

While this could use a ZAP ascan rule I think in this case it would be better if the tool just tried to access the security.txt file directly (if enabled) so that users wouldnt need to run the ZAP spider/active scanner in order to detect it.

Should probably be a bit more generic, eg to also support https://www.contributejson.org/ and any other similar schemes


cannot add foreign key constaint

Illuminate\Database\QueryException  : SQLSTATE[HY000]: General error: 1215 Cannot add foreign key constraint (SQL: alter table role_user add constraint role_ user_user_id_foreign foreign key (user_id) references users (id) on delete cascade on update cascade)

check #941

I think you should edit $table->integer('user_id')->unsigned(); by $table->bigInteger('user_id')->unsigned();. Because on user's migration file use $table->bigIncrements('id');


MapView: Drawable with IsClickable=false blocks MapClicked event

Mapsui Version
4.0.0-rc.2
Mapsui Platform
Xamarin.Forms
Device
iOS 16 (probably also Android and others)
Describe the bug
I have a MapView with several Drawables. The IsClickable property is true for some and false for others. The clickable Drawables receive Clicked events as expected. The unclickable ones do no receive such events (also expected), but they seem to block the MapClicked event, which is actually not what I expected.
Expected behavior
If the Drawable at the clicked position is not clickable, i.e. does not handle the click event, I'd expect that the event is handed down to the map itself and the MapView emits that MapClicked event, as if there was no drawable at the position.
If there is another (clickable) Drawable at the same position, it should be able to handle the click event (which also does not seem to work).

That is also what I would expect. @charlenni Do you also consider this a bug?

I think I found the place in the code which breaks this (am about to submit a PR) ...

The unclickable ones do no receive such events (also expected), but they seem to block the MapClicked event, which is actually not what I expected.

This is fixed by #2043 (with little effort).

If there is another (clickable) Drawable at the same position, it should be able to handle the click event (which also does not seem to work).

I verified once more that this problem indeed exists as well. It is not fixed by #2043 (will probably require some more effort).

IFeature.IsClickable

If possible I would like to avoid adding this to the interface. A lot of scenarios can be solved by using custom IFeature types which could be cast back to that type in user code. So you could add ClickablePointFeature: PointFeature. with a IsClickable field, and in the MapInfo event cast back to that type to check the IsClickable.
btw, there is a MapInfo.MapInfoRecords field with a list of all the clicked items. The MapInfo.Feature is the top one, but in fact the MapInfo.Feature could be removed entirely if it causes confusion.

IFeature.IsClickable

If possible I would like to avoid adding this to the interface. A lot of scenarios can be solved by using custom IFeature types which could be cast back to that type in user code. So you could add ClickablePointFeature: PointFeature, with a IsClickable field, and in the MapInfo event cast back to that type to check the IsClickable.

Hm, so maybe not in IFeature itself, but one of its descendants? GeometryFeature might be a good candidate, since Drawable is based on this. Would it be ok to have an IsClickable property in the GeometryFeature itself, or would you prefer a subclass ClickableGeometryFeature?
In general, I would avoid making the IFeature inheritance tree too complicated. Probably most (all?) features could be clickable in principle. I guess the IsClickable property will need to be handled in Mapsui.Rendering.Skia.MapRenderer.GetMapInfo or similar.

I need to dig into this further to come up with a better proposal. I want to push hard for the simplest solution. I did not do this enough in the past and promised myself to do it more in new code. If we could avoid an IClickable field altogether this would be the best option.

First thing is to make sure your scenario is possible at all.
Second thing is to make your scenario easier. But still, my approach would be not to add specific solutions to specific scenarios, but to provide the building blocks to compose the desired functionalty.

About the first point. What if you use the Info event instead of MapClicked and check a field in the IFeature. You could set a property like this myFeature["isClickable"] = true and check for if (clickedFeature["isClickable"] == true)? (you might need a cast).
A related thing I am thinking about is to make it possible to add any kind of class to a feature  without having to use inheritance (because you are definitely right the inheritance tree should not be too complicated). Perhaps IFeature should have a Data field of type T.

I would think clickable/non-clickable could be solved by putting those two in different layers. The MapView has it's own layers which is why this work different there, but at some point the same kind of layers will need to be used.

@janusw Was this now fixed with your workaround?

Yes, I think this issue is fully fixed by now (with v4.0.0), the first part via #2043, the second via #2060.


Offerer must use actpass value for setup attribute

When the call is coming into asterisk ,after accepting call by sipjs client (v0.7.2) on chrome (v47.0.2 and v48.0.2) , I ask asterisk to execute REFER between the end points , I got below exception. (It's working well on FireFox 44.0.2)
Tue Feb 16 2016 17:49:22 GMT-0500 (EST) | sip.invitecontext.mediahandler | Failed to set local answer sdp: Failed to push down transport description: Offerer must use actpass value for setup attribute.
sip.js (2957,28)

Hi @shadmehr,
This most likely identifies that sdp on another endpoint is being generated in such a way that Chrome can not interpret it properly. If you were able to determine where the sdp is being generated 'improperly,' a hack could be added to our hacks file if it was proven to fix your issue.
Otherwise, this is either a problem with Chrome directly, or with your Asterisk config, so I'm going to close the issue. If you can properly identify the necessary hack, we would certainly accept a PR.
Thanks,
James

Hi,
I think that these issues should help you to understand the situation:

https://github.com/versatica/JsSIP/issues/311
https://issues.asterisk.org/jira/browse/ASTERISK-25864