[Documentation] : Enhancement Of Readme.md

Wanted to do the following changes :-

Enhance the project structure
Add star our repository section
Add the project structure
Add need help with the basics section
Enhance the pull request steps section
Add additional method of contributing through GitHub desktop section
Add good coding practices section
Add the pull request rules section
Add the issue process section

It is really helpful and makes the contribution more easier for the contributors.

Wanted to do the following changes :-

Enhance the project structure
Add star our repository section
Add the project structure
Add need help with the basics section
Enhance the pull request steps section
Add additional method of contributing through GitHub desktop section
Add good coding practices section
Add the pull request rules section
Add the issue process section

It is really helpful and makes the contribution more easier for the contributors.

not required


Uncraftable Augments

It seems that augments require themselves, in the smithing table to craft, instead of the tier before.

Applies to all tiers, and all augments from thermal extras?

Just a JEI/NEI issue, they are craftable normally.


Unreliable test fix

Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

duplicate


Extension does not work on team pages anymore

Players with steam IDs on the team page should show steam link and faceit link/elo.

https://liga.99damage.de/de/leagues/teams/31507-nochance => https://liga.99damage.de/leagues/teams/31507-nochance 🤦


Improved isHostnameAllowed(String url)

I think that check the end of the domine is better and more efficient :)

Thanks!
Currently, both http:// and https:// are stripped and then the library checks if the URL starts with the supplied hostname. That should work in most cases, but would probably not work with other protocols (which?) or when the URL has HTTP basic authentication, etc.
So replacing the string url with the parsed version Uri.parse(url).getHost() may actually be a good idea.
But why use endsWith instead of startsWith (or equals)?

Because usually you know the end of the domain.
For example for my app (SlimSocial for Facebook), I know that urls end with Facebook.com so it opens also m.facebook.com, touch.facebook.com, 0.facebook.com .. etc solving my need :)

Thanks! You're right, of course. Subdomains should be included as well.
But your solution would match allaboutfacebook.com as well.
What about this improved solution?
String actualHost;
for (String expectedHost : mPermittedexpectedHosts) {
	actualHost = Uri.parse(url).getHost();

	if (actualHost.equals(expectedHost) || actualHost.endsWith("."+expectedHost)) {
		return true;
	}
}

generally could be inaccurate but in my case it's ok.

This should have been implemented in https://github.com/delight-im/Android-AdvancedWebView/commit/da127f967f8dcf0ce5a0297c58e9bef2cc1a5ae8 now.
Can you please check if it's working? You should be able to update the dependency from compile 'com.github.delight-im:Android-AdvancedWebView:v2.1.0' to compile 'com.github.delight-im:Android-AdvancedWebView:da127f967f8dcf0ce5a0297c58e9bef2cc1a5ae8' for this.
Thank you!

It works but as I wrote, it is inaccurate.
Maybe it's better write another method.
You can use addPermittedEndHostname() and after do:
actualHost = Uri.parse(url).getHost();
for (String expectedHost : mPermittedexpectedHosts) {
    if (actualHost.equals(expectedHost)) {
        return true;
    }
}
for (String expectedEndHost : mPermittedexpectedEndHosts) {
    if (actualHost.endsWith(expectedEndHost)) {
        return true;
    }
}

Sorry, why do you think it's in accurate?
It's as accurate as it could be, because it checks if the domain is either a direct match or a subdomain of the permitted hostname. That is exactly what you were asking for, isn't it?
Doesn't it work for you?

If I would for example only facebook.com:
addPermittedHostname("facebook.com"); so actualHost="facebook.com";
with actualHost="m.facebook.com";
actualHost.equals(expectedHost) -> false
actualHost.endsWith(expectedHost) -> true

Did you try it? With the current explanation, adding facebook.com as a permitted hostname should be sufficient to allow all of the following domains:

facebook.com
www.facebook.com
m.facebook.com
en-us.facebook.com
0.facebook.com

That is, all subdomains and the hostname itself. That's what you want, isn't it?

But allfacebook.de would not work as an actual hostname, for example.

I'm telling you that IN MY CASE it works. Because I need to include all subdomains.
BUT if you want to publish it for everyone, you should implement it in a more accurate way. Because someone could want permit ONLY the main domain WITHOUT subdomains.
I hope you understand :)

Thanks, now it's clear :)
The new behavior is really the better way, I agree with you. But I also think it's what most people will need. So we'll leave it until somebody needs it changed again ;)
Thank you!

I can continue  using 'com.github.delight-im:Android-AdvancedWebView:da127f967f8dcf0ce5a0297c58e9bef2cc1a5ae8' ? or it can elapse?

That's fine, that version should continue to be available. But whenever possible, you should use one of the stable versions that include a version number instead of the commit hash. See the example in the README.


phpenv: migrate from php

Goes together with Homebrew/homebrew-php#3815.

Is there anything preventing a merge of this submission ?


add files from m63204. HEIF region tracks. Canon

m63204  contains additional information which will be helpful to finalize this PR

Reviewers needed.

Is this also part of HEIF 2nd edition?


feat(security): Update docker-compose security for Consul ACL Setup

Add ENABLE_REGISTRY_ACL env
tuned volumes

Signed-off-by: Jim Wang<EMAIL_ADDRESS>PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-examples/blob/master/.github/CONTRIBUTING.md.
What is the current behavior?

No Consul ACL enabled yet
Issue Number: #25
What is the new behavior?
Enable Consul ACL in docker
Does this PR introduce a breaking change?

[ ] Yes
[x ] No

New Imports
Are there any new imports or modules? If so, what are they used for and why?
Specific Instructions
Are there any specific instructions or things that should be known prior to reviewing?
Other information

Changes look good, but you need to run make build

yeap, will do once that edgex-go PR is merged.


ARROW-16811: [C++] Remove default exec context from Expression::Bind

Removes the default from the ExecContext argument in Expression::Bind

@westonpace It seems this PR needs updating and conflicts being fixed.

@westonpace, I moved forward with resolving the conflicts.

Looks like the CI failures are unrelated to the changes.

Closing my stale PRs


[HOLD for payment 2023-09-08] Update Transaction type definition

Problem
We added receipt to the transaction Onyx key and we should update its type definition accordingly.
Why is this important
Keeps data types correct
Solution
Update the data type

@sobitneupane you reviewed the PR, do I need to add Bug label to process payment or is the process different for paying through newdot?

For payment in newDot, payment summary will be required. So, Bug label might be required for that.

@NicMendonca could you please assist with paying @sobitneupane for the PR review?

@sobitneupane can you please request payment via Expensify?

closing ^^

Requested payment on newDot.
https://github.com/Expensify/App/issues/25909#issuecomment-1717872568

$1,000 payment approved for @sobitneupane based on BZ summary.


Fix issues of merging v0.3.0 to alt-l1

:clipboard: Add associated issues, tickets, docs URL here.
Overview
Describe what your Pull Request is about in a few sentences.
Fix the problems of merging the new release v0.3.0 to alt-l1 branch
Changes
Describe your changes and implementation choices. More details make PRs easier to review.

Since BOBA token is the native token on Alt L2s, the collection of the exit fee is different from Ethereum L2. The ERC1155Bridge contract is updated for Alt L1s.
Add the token information to tokenInfo.json file for gateway

Testing
Describe how to test your new feature/bug fix and if possible, a step by step guide on how to demo this.

Codecov Report

:exclamation: No coverage uploaded for pull request base (alt-l1@9819c57). Click here to learn what that means.
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##             alt-l1     #453   +/-   ##
=========================================
  Coverage          ?   79.54%
=========================================
  Files             ?       38
  Lines             ?     1305
  Branches          ?      200
=========================================
  Hits              ?     1038
  Misses            ?      267
  Partials          ?        0

Flag
Coverage Δ

contracts
79.54% <0.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


A script to delete gists older than 30 days

Another loose end that I said I'd take care of (but didn't!)
Suggest to add the line
${CMS_BOT_DIR}/cleanup-old-gists

to
https://github.com/Mu2e/codetools/blob/79530e954cf000857233b24473b1e1ab73216e7b/bin/github/jenkins_tests/mu2e-offline-build-test/job.sh#L288
once this is merged.
This would prevent the problematic buildup of many log files on the FNALbuild account by automatically cleaning up logfiles uploaded via Gist older than 30 days.

Hi Ryun,
I hope that your are enjoying Edinburgh and are ramping up on LHC-b.  I did b and c physics for 25 years and still try follow it.
As I read this PR, we need to merge it and then to enable it we need to make  new PR to enable it.  Is that right?

Also, can you tell me a bit about dependabot.  I recommends updating  dependencies.  Does it simply know that a new version is available or does it know more than that?  Does it also automatically install the new dependencies or do we need to do that by hand prior to merging?  Do you know how to test prior to merging that the changes do not break something else?

For example I am a little worried that updating one library might require an update of a different library that is not tracked by dependabot?

Hi Rob,
That's correct, this PR only addresses the change needed to this repository. Another PR needs to be made in Mu2e/codetools to make sure this script runs its checks regularly.
I'd initially added Dependabot to keep awareness about updating dependencies, but I agree with your point on dependency compatibility. I am uncertain as to whether Dependabot or pip has a dependency resolver. In any case it would probably safer to manage them by hand and update them periodically.
On Jenkins, I believe I'd configured it to always install the environment following the content of requirements.txt, so as long as one can run:
python -m venv venv
source venv/bin/activate
pip install -r requirements.txt

without issue in order to check the dependencies are compatible with eachother, it should also work on Jenkins.


Changed to using a local babel runtime, instead of the polyfill.

Using babel's polyfill in a library is very unrecommended, because it pollutes the global namespace, and causes collisions with projects using babel as well. This fork is injecting babel's runtime into the transformed code, instead of using globals.

👍


configure: error: libgmp missing MacOs Bigsur

Hello
I'm get error
brew install cmake automake berkeley-db4 libtool boost miniupnpc openssl pkg-config protobuf qt5 libevent imagemagick librsvg qrencode gmp

git clone --recursive https://github.com/qtumproject/qtum.git --branch=qtuminfo
 cd qtum
./autogen.sh
./configure

configure: error: libgmp missing
I'm try
brew install gmp
Warning: gmp 6.2.1_1 is already installed and up-to-date.
To reinstall 6.2.1_1, run:
brew reinstall gmp

Did you get it fix?

Connect with our  team representatives to help resolve your issue and troubleshooting .
Connect here: direct.lc.chat/14158209/
Hours of Operation
24/7 (Ready to fix issues)


Models parsed via response do not pass isinstance() checks against the original model

Describe the bug
We're parsing objects using MyModel.__response__, then pass the objects as if they were instances of MyModel. This fails because isinstance(obj, MyModel) return False.
To Reproduce
Steps to reproduce the behavior:

Define a model inherited from DualBaseModel
Parse an object using model's __response__.
Call isinstance(). The check fails:

from pydantic_duality import DualBaseModel

class MyModel(DualBaseModel):
    one: str

my_model = MyModel.__response__.parse_obj({"one": "two", "extra": "three"})

print(isinstance(my_model, MyModel))
print(isinstance(my_model, MyModel.__response__))
# False
# True

Expected behavior
I'm not sure if this is intended or not and if it should be considered a bug in pydantic-duality, but such behavior was unexpected – it requires to always check for both isinstance(obj, MyModel) and isinstance(obj, MyModel.__response__) when the code works with objects parsed by MyModel.__response__.
Screenshots
If applicable, add screenshots to help explain your problem.
Operating system
macOS
Additional context
Add any other context about the problem here.

Hm... I remember explicitly adding the feature to make sure this behavior is impossible. I'll take a look.

I looked into it. I did do this for reverse checks ( isinstance(obj, cls.__request__)) but not for the other types of checks. The current architecture is based on building completely different MRO for each object (where cls.__request__ is based on the .__request__ of its parents, and so on) which means that the classes you are trying to compare are completely unrelated.
A completely different architecture seems to be necessary to fix the issue you are referencing. Do you have any ideas?

Fixed in 1.2.3. Please, check.


Add TorchToLinalg lowering for MaxUnpool operation

For the OnnxToTorch lowering added here https://github.com/llvm/torch-mlir/pull/3413, we need the TorchToLinalg lowering for e2e execution.

max_unpool3d is implemented here https://github.com/llvm/torch-mlir/pull/3536

max_unpool2d support is https://github.com/llvm/torch-mlir/pull/3733


support map of type object in swagger

Issue #, if available:
generate swagger schema error if there is any map of type object is defined in rdl
Description of changes:
support map of type object in swagger

I confirm that this contribution is made under the terms of your choice and that I have the authority necessary to make this contribution on behalf of its copyright owner.

Thank you for submitting this pull request, however I do not see a valid CLA on file for you. Before we can merge this request please visit https://yahoocla.herokuapp.com/ and agree to the terms. Thanks! :smile:

I've agree to the CLA


Recommended value not displayed correctly

I tried to run the CIS findings list for Windows Server 2019 and got wrong values for recommended in the log and in the report.
I reduced the findings list to 4 lines to reproduce the error.
findings fist
ID,Category,Name,Method,MethodArgument,RegistryPath,RegistryItem,ClassName,Namespace,Property,DefaultValue,RecommendedValue,Operator,Severity
2.2.19,"User Rights Assignment","Debug programs",accesschk,SeDebugPrivilege,,,,,,BUILTIN\Administrators,BUILTIN\Administrators,=,Medium
2.2.20,"User Rights Assignment","Deny access to this computer from the network (DC)",accesschk,SeDenyNetworkLogonRight,,,,,,"BUILTIN\Guests","BUILTIN\Guests",=,Medium
2.2.21,"User Rights Assignment","Deny access to this computer from the network (Member)",accesschk,SeDenyNetworkLogonRight,,,,,,"BUILTIN\Guests","BUILTIN\Guests",=,Medium

error
In the report and the log the value for recommended is BUILTIN\Administrators instead of BUILTIN\Guests. The actual value for 2.2.20 / 2.2.21 is empty (no groups are denied).

Report output:
"ID","Name","Severity","Result","Recommended"
"2.2.19","Debug programs","Passed","BUILTIN\Administrators"
"2.2.20","Deny access to this computer from the network (DC)","Medium","","BUILTIN\Administrators"
"2.2.21","Deny access to this computer from the network (Member)","Medium","","BUILTIN\Administrators"

HailMary mode seems not to be affected from this error

Thank you for spotting this bug, the very helpful issue description, and test file. The bug is only triggered when the result was empty. Could you please update HardeningKitty and test it again - I pushed a fix to the repo (https://github.com/0x6d69636b/windows_hardening/commit/96717bd8c24cd829cb37af6b61b02ccd79c285fb)

The fix displays the expected results (log and report).
Thanks a lot :-)


build(docker): drop build-essential from Docker image

SUMMARY
This PR practically drops the apt package build-essential (gcc etc.) from the Docker image, by removing it in the same step it got installed. This package is needed solely to install python-ldap and mysqlclient (from requirements/development.txt).
Important: Users building on top of apache/superset would have to install these tools themselves potentially breaking their Dockerfile depending on their usage.

Also removed because not needed:

rm /var/[log,tmp]/*: Both dirs are empty.
rm /tmp/*: Basically empty except for a single file from upstream Python Docker image. Removing this file wouldn't save image size.
apt-get clean: runs automatically for debian-based docker images.

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
This results in a smaller image:

uncompressed: 1.29 GB down to 1.04 GB
compressed: 382 MB down to 311 MB

TESTING INSTRUCTIONS

check if the image builds: docker build . -t test
run docker-compose.yml based on that image and check if all services are running
successfully run integration tests on that docker stack
successfully run unit test
check GitHub CI

ADDITIONAL INFORMATION

[ ] Has associated issue:
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

I follow the idea and it looks nice to reduce the image size and simplify the Dockerfile!
Thanks for flagging the breaking change aspect.  Because of that I wonder if this would be a good candidate for a breaking version.  Maybe something to discuss on the dev@apache email list?  The safest thing would be to insert it into a breaking change window ahead of 4.0.0 but perhaps it's okay to do this before then as it would be a few months out most likely.

@sebastianliebscher hope you are well!  I see this PR just merged  and it reminded me of this one.  Should this now be closed as already accomplished via the other PR?


Feature/create wallet

Summary (Please recap what you changed or fixed)
Checklist (If you won't pass this checklist please comment why)

[ ] I removed all commented or unnecessary code.
[ ] Provide the screenshots due to UI changed or bug fixed
[ ] My code has covered these test cases (please list down your tested cases):

hi @djhahe , @codsay please help me to check the Ledger cases.
When upgrade from 1.0.0 to 1.1.0
https://user-images.githubusercontent.com/4486806/191224504-4e753455-e246-4246-976e-dbd96c85ed10.MP4
New installation of 1.1.0
https://user-images.githubusercontent.com/4486806/191224900-df1a6279-3131-47a2-bb1c-f84472c402cb.MP4
It works normally on 1.0.0
https://user-images.githubusercontent.com/4486806/191224169-4edeb48b-5266-4fb8-8ed2-60501993fe1c.MP4

hi @djhahe , @codsay please help me to check the Ledger cases.
When upgrade from 1.0.0 to 1.1.0 https://user-images.githubusercontent.com/4486806/191224504-4e753455-e246-4246-976e-dbd96c85ed10.MP4
New installation of 1.1.0 https://user-images.githubusercontent.com/4486806/191224900-df1a6279-3131-47a2-bb1c-f84472c402cb.MP4
It works normally on 1.0.0 https://user-images.githubusercontent.com/4486806/191224169-4edeb48b-5266-4fb8-8ed2-60501993fe1c.MP4

It has been resolved on iOS. Will check on Android when new build has been published.

hi @djhahe , there is no Splash Screen when installing new app (version 1.1.0 - build 19). Please help to check again thanks.

hi @djhahe @codsay , please help me to double check it on Android. My ledger got stuck when connecting with my Android via bluetooth. After that, I think we can merge this PR and continue to fix bugs and improvements.


Support TensorFlow conversion

The conversion tools support most popular frameworks - but not the most popular of them all - TensorFlow.
It would be nice to have an easy way to port a TF network to CNNdroid.

I have never use TF ,but  in my project we used the model we defined ourselves,just try to get the weight and bias from TF moedel and send it to CNNdroid layers,it may be faster than get the next version of CNNdroid.(By the way the author is a very nice person)
We will help you whenever you encounter problems.

Here are some questions to ask

Can this project support the TensorFlow model now
Is there any conditional limit: mobile phone system or opengl es version, because only tensorflow-lite is available on TensorFlow and the device should support at least opengl es 3.1
Hope to be able to get help

Unfortunately, we have not developed the TF conversion script. But, if you extract the weights and biases from network and save them in MessagePack binary format, you should be able to run them on CNNdroid. You can have a look at Caffe to CNNdroid conversion script to get an idea about how to save them in MessagePack.
The only system compatibility constraint is to have Android 4.0 and later running on your mobile phone. Other than that, you need to check the supported layers and network configurations. For example, residual connections are not supported.

Thanks

Thanks so much.
It helps a lot.


Fix kubeconfig download file name

What does this PR change?
Fix bug in kubeconfig file name.
Does the PR depend on any other PRs or Issues? If yes, please list them.
None
Checklist
I confirm, that I have...

[X] Read and followed the contributing guide in CONTRIBUTING.md
[ ] Added tests for this PR
[X] Formatted the code using npm run format (if applicable)
[X] Updated documentation on the Paralus docs site (if applicable)
[] Updated CHANGELOG.md

Screenshot:


High Memory usage running Node

Is it normal for nodejs apps (mean.io) to be using alot of memory.
I have managed to run 3 very simple application on a VPS and here is the memory usage according to newrelic
node (root) |  0.5 % (CPU usage) |  1200 MB (Memory Usage) | 8 Running Processes

if i stop one application (Has 1 web and 1 worker process ) i suspect to be using alot of memory  i get the following (This are two running apps)
node (root) |  0.1 % (CPU usage) |  240 MB (Memory Usage) | 4 Running Processes

Secondly should the running Processes be 2 instead of 4, considering that am not running workers only 1 web per application

@lafama this seems to be incomplete ps output. Where are the process command strings? Hard to tell what's what. In any case, depending on how a process is executed and subsequently internally managed you may have multiple processes for a given service. What does you Procfile look like and do you have any dokku plugins installed like supervisord or foreman?

Closing as we haven't had feedback from OP in a month. If this is still an issue, please comment and we'll try to debug more.

Sorry about that.
I figured out what was causing this, its newrelic monitoring plugin and its not related to dokku.
require('newrelic');

i removed that and the memory issues disappeared


Updated structure to support lazy invocation of http requests.

Previous added support for wait method, however wait requires polling same request again and again. There was mistake that this part was actually missing totally and without refactoring structure didn't support it.  Internal clone functionality allows versatile way to write new extensions methods where multiple call functionality is needed.

I will publish this without review (review fixes after) since i am going to holiday and i don't want to left this behind bending.


Restructuration, and bug fix

Great work you've done here!

I've mainly split the code base into files, to make it a little bit easier to build on top of it
I had an issue with handling the files (open, write), so I specified the utf-8 encoding which fixed it

I'll try to work on the optimization side (I've hit the requests wall sooner that I expected 😅)

Thanks a lot for your interest and efforts !!!!!


Unable to catch errors in express middleware

Description
When a validation fails, the library does this:
res.status(400).send(...)
When it should actually do this:
throw new ZodError(...)
If not, there's no way of parsing the errors to match different needs.

@Aquila169 I can help you with the implementation, we just need to change the functions sendError and sendErrors:
export const sendErrors: (errors: Array<ErrorListItem>, res: Response) => void = (errors, res) => {
  const error = new ZodError({
    type: 'RequestValidationError',
    errors: errors.map((error) => ({ path: [error.type], error: error.errors })),
  });
  throw error;
};
export const sendError: (error: ErrorListItem, res: Response) => void = (error, res) => {
  throw new ZodError({ type: error.type, errors: error.errors })
};

I was also having troubles with this approach, my errorHandler was not catching errors and I was constantly getting can not set headers after they are sent to the client errors


Add blue circle and disable button when the textPrep is pressed once

Add blue circle and disable button when the textPrep is pressed once

 New card

 New card


upgrade to<EMAIL_ADDRESS>

Brings in:

Windows binaries this time (unlike v3.1.3 which never got them)
New dot symbolizer for very fast rendering of millions of "enfpoints"
Fixes v3.1.3 regression in drawing some Maki icons (but this never impacted Studio)
Other minor changes: https://github.com/mapnik/node-mapnik/blob/master/CHANGELOG.md#314
Updated mapnik-reference exposing additional Mapnik features (text-transform and text-upright): https://github.com/mapnik/mapnik-reference/blob/master/CHANGELOG.md#700
Updated Carto/mapnik-reference that should be faster to require and help startup times.

holding on this until node-mapnik 3.1.5 is out.

@springmeyer
Is there anything else to put this on hold on merging since node-mapnik is now at 3.2.0 ?

Already using<EMAIL_ADDRESS>


Namespace Models

This pull request includes changes for namespacing models under App\Models. Feel free to commit any additional changes to the shift-61599 branch.
Before merging, you need to:

Checkout the shift-61599 branch
Review all pull request comments for additional changes
Thoroughly test your application

:warning: While Shift updated model references within your application code, you may reference models outside the code. Be sure to review your environment configuration, database, and queues for additional references.

:warning: Shift detected polymorphic relationships within your application. Unless you created custom polymorphic types using morphMap, you will need to update the fully qualified names in the related model table.
Shift found potential instances of polymorphic relationships in:

[ ] app/Models/Comment.php
[ ] app/Models/Paper.php


adding ACR.UserDialogs v 3.0.3 breaks Windows phone project

Hello,
If I add the above nuget package to my Xamarin Forms project (1.3.5 pre-release) it breaks the build on Windows Phone project with an error "An exception of type 'MS.Internal.WrappedException' occurred in System.Windows.ni.dll but was not handled in user code".
As a workaround, if I uninstall the Xamarin Forms & then reinstall it, the above error is gone & WP project builds & works fine.
Now if i use a simple code to open a prompt like below in PCL
var result = await UserDialogs.Instance.PromptAsync("enter a label name and click apply", "apply label", "Apply", "Cancel", "enter label name", InputType.Default);
I get an error when I run the app in Windows phone emulator. Below is the error that I get.
"An exception of type 'System.MissingMethodException' occurred in Acr.UserDialogs.DLL but was not handled in user code
Additional information: Method not found: 'Void Microsoft.Phone.Controls.PhoneTextBox.set_PlaceholderText(System.String)'."
Is this an issue with Acr library or the Toolkit.Kinnara library on which ACR has a dependency on? I will really appreciate if you can look into this when you have some free time.
Thanks again for your time.
Regards
Supreet

Try the latest release

I will. Thanks for the update.

It worked. Thank you very much for your help. Appreciate it :)


OSSM-4059: fix Recursive variable MAISTRA_VERSION references

/test maistra-istio-push-image-2-4

@yxun I'd suggest you to run these targets locally within the builder image, to verify they work.

/cherrypick maistra-2.3


Highlight unloaded and/or hidden buffers differently.

This may or may not be useful. Mock it up and decide.

Nah. There's enough highlighting already. Some may say too much. It's good like it is.


Create tests for turbopy

TurboPy currently lacks tests. We need unit tests and integration tests.

[x] Add folder for tests
[ ] Create tests for the code
[x] Check test coverage
[x] Make sure tests are run as part of CI pipeline

#92 took care of 3rd item on list

Should we say complete at 90% test coverage?

I'd say that we need to get the code coverage up some more. Looking at the report on codecov.io, the main offender is computetools.py. I'm not really sure what to do about that, as most of the code there is in the finite difference helper class. While it would be nice to have test of that code, the code itself is in pretty rough shape.
The other place where we can improve the test coverage is in diagnostics.py. I'm adding an issue now to write a test for the FieldDiagnostic class, which should bring the coverage for that file up substantially.

Regarding computetools.py, I think if we have test of the BorisPush class and the Interpolators class, I'd be satisfied for now. I'll go make issues for those classes.

Completed with #105


The paginated pages in the api are in reverse order to spigot pages

Ok, so my resource AutoPivkup has 5 pages of updates. On spigot page "1" it contains the most recent updates and page "5" has the oldest updates for the plugin. When using &page=1 I get the 5th and oldest page of updates on spigot and when I use &page=5 I get the latest updates. The use of 1 &page=# should be changed to match the content on the same page as if you were viewing it on spigot.
https://api.spigotmc.org/simple/0.2/index.php?action=getResourceUpdates&id=70157&page=5
https://www.spigotmc.org/resources/autopickup-1-18-support.70157/updates?page=5

Fair point.

Otherwise you have to use the number of updates and the expected page size (10) to determine which page to grab. And that's shaky logic.

I am going to be adding pagination information to any paginated response. However, to change the default ordering would be a breaking change and would need a version bump. I will probably instead add a sort argument, but the default will remain as is.


Fix issue with excel sheets

Basically you can take .github/workflows/sheet2rdf.yml and workflow/sheet2xls.py

If you squash and merge then it should fix your fix.


setting uv = f0 = 0 before normalize?

Hey guys, I  found you set uv = f0 = 0 at line 57, what's the intension behind this?
https://github.com/NATSpeech/NATSpeech/blob/aef3aa8899c82e40a28e4f59d559b46b18ba87e8/utils/audio/pitch/utils.py#L52-L58
BTW,  I found same issue in DiffSinger https://github.com/MoonInTheRiver/DiffSinger/issues/47

sorry, I'vs missed the ==


Add a back button once a CRD was rendered

Now, I have to refresh the page to get back which is not nice UX.

The header was also missing from the rendered page.

Ok, I need to figure out how to reset the state. For now, the header will be added back and some other things.

For now, until I figure out how to do this, I added a reload button.

Changed it a bit, so now the title reloads.

I will need to do some refactoring. https://github.com/maxence-charriere/go-app/issues/956

Clicking the title will navigate back now on a fresh page.

Finally I was actually able to add a true navigate back button that is only visible once content is generated.


Add a fallback on annotation validation

Having a malformed annotation on a datapoint (or an annotation that failed to parse, not even malformed) right now leads to the whole loading process failing.
This PR is a hotfix to prevent that.
If an annotation fails to parse, it gets shown to the user in a warning message, and I warn them that they won't be able to interact with them, for example:
Accessing as kirill
Downloading annotation fields ['annotation']...
Warning: The following datapoints had invalid annotations, any annotation-related operations will not work on these:
Field "annotation" in datapoints:
        train2017/000000000009.jpg

I'm not handling these bad annotations in other downstream functions for now properly, if we do want to make it have a nice UX, would probably need to have some kind of BrokenAnnotation class that will shim the regular annotation functions and display a warning.
Not sure if it's worth it to work on this right now

Good catch, I think my autoformatter broke 🥲


cloak: init at 0.2.0

Motivation for this change
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 139296 run on x86_64-linux 1

1 package built:

cloak

Result of nixpkgs-review pr 139296 at e3f9796d run on x86_64-linux 1

1 package built successfully:

cloak

1 suggestion:

warning: unused-argument
Unused argument: stdenv.
Near pkgs/applications/misc/cloak/default.nix:1:8:
  |
1 | { lib, stdenv, rustPlatform, fetchFromGitHub }:
  |        ^

Result of nixpkgs-review pr 139296 run on x86_64-linux 1

1 package built:

cloak


Fixed access to the interface_type property

When trying to access the 'interface_type' property of my opened resource, I got the following error:
    self.resource_name).interface_type
AttributeError: 'tuple' object has no attribute 'interface_type' ```

Indexing the first element of that tuple fixed the problem.

Coverage remained the same at 49.63% when pulling 4e433a70b29a715d3765948652d23f0d4360f95e on mordoror:master into 0ab79b993241c77b241207c15425dbe4b1c5df64 on hgrecco:master.

Thanks!


Unsupported value for conversion into R

Hi,
I seem to have issue running an R script in a snakemake pipelin using script
The error is
Unsupported value for conversion into R  <_frozen_importlib_external.SourceFileLoader object at 0x7f1f4c1ef7f0>
Pipeline uses:
r-base version : 3.5.1
snakemake version: 6.2.1
I make a test rule to call the r script which looks like this:
rule Genome:
    output:
        touch("run_genome")
    conda: my_CONDA_ENV
    threads: 10
    script:
        "../scripts/species.database.genome.R"

I have tested it even with a .R file which only has print('xxx') in it to be sure it is not the content of the file but even that one failed.
It would be great if you could give me any feedback on what went wrong here

I don't think it's possible to answer your question if you don't provide data and code to reproduce the issue, although someone may have a clue. Also, I think this sort of question is better posted on stackoverflow.

This error happens when snakemake tries to encode your rule's keywords to pass to R (accessed via snakemake@input, etc in R) but it seems to be trying to encode an imported library object.
I wasn't able to reproduce this error and whitout further context it's hard to know exactly what caused this. What do you see when you run snakemake with --verbose?

I was actually testing a bit more there, so I am using module inside my pipeline way before calling this rule with script. Something like this:
module fastq_rule:
    snakefile:
        'https://raw.githubusercontent.com/maxplanck-ie/snakepipes/modularization/snakePipes/shared/rules/FASTQ.snakefile'
    config: config

use rule origFASTQ1 from fastq_rule as rna_origFASTQ1 with:
    output:
        "originalFASTQ/{sample}"+config['reads'][0]+".fastq.gz"

use rule origFASTQ2 from fastq_rule as rna_origFASTQ2 with:
    output:
        "originalFASTQ/{sample}"+config['reads'][1]+".fastq.gz"

if I remove those rules and literally copy paste them from the source and not using module it goes true like a charm. It really puzzles me that what could be the relation between them. The input of the rule that failes are not the output of the moduled rules and they are way downstream. I changed no env structure, no version or anything.

IMO the error message is slightly misleading, as the type of the value is unsupported, not the value itself.
The error message might be more informative along the lines of
f"Unsupported type for conversion into R. The type of {value} is {type(value)}, but the only supported types are ..."


Put pins in a separate window.

@Julian I'm coming around on your idea to put pins in their own window, though I don't think each pin should have its own window, since this can get cluttered too quickly I think. This reflects a more general intent to treat the current pin as "sacred" in that it's the only thing you'll see in its window, which for example will help clean up state diffs if you have pinned something.

I'll make some time to look at this in the next few days though I'm prepping for even more than usual this week so will be slow, apologies.
To clarify though -- I don't like pins because I find they complicate the implementation a lot, and provide functionality better served by native vim features. This opinion is of course uninformed, because I don't use them, so I could be talking complete nonsense, but that's where my previous comments have come from.  I bring that up again now because if you're coming around to that, this PR adds lines rather than removes, which worries me. At the minute infoview.lua tops 1000 lines (albeit with long emmy comments which bloat), but it just doesn't feel to me like it should be that large.
I'll try to give this and the other PR an honest objective shot nonetheless, and yeah in case I don't say it enough really do appreciate all of this work you've done!

To clarify though -- I don't like pins because I find they complicate the implementation a lot, and provide functionality better served by native vim features.

There are several features here, and only some of them can be replaced by vim features.  The original pin feature was that you can "pin" a position---instead of tracking the cursor position in the editor, the "pinned" info always shows information for the same "pinned" position.  Then you can also pause the info, so that it doesn't update when you change the file.  These clearly can't be done with native vim features.
The other part is that multiple pins can be shown in the same infoview.  I'm somewhat happy about this because I'm not so good at vim window management.  (But I don't get the extra Info layer in between Infoview and Pin[] either.)
But I think I could live with a different design where Infoview=Info=Pin and you had d, p and u keybindings to pin and disable updates, resp. (and also duplicate the infoview if it's attached to multiple windows).  Then the equivalent of LeanInfoviewAddPin would be :spl<CR>p; and there would finally be an obvious way to clear individual pins, namely :q!

In case it's not clear: having all pins in a second window is the worst of both possible approaches for me.  I need to bother with both vim window management as well as the (limited and lean-specific) commands to manage pins.

But I don't get the extra Info layer in between Infoview and Pin[] either.

Does #211 make this clear? This gives us control of whether pins are shared between tabs.

But I think I could live with a different design where Infoview=Info=Pin and you had d, p and u keybindings...

Not sure I'm understanding this part. Are you saying each pin should have its own split window? I feel like you would run out of space fast if you attempted this. BTW there actually is no way to clear individual pins currently, but it should be very easy to add a Div event for this.

having all pins in a second window is the worst of both possible approaches for me.

I see, perhaps we can allow for the previous way of doing things (i.e. all pins in the same buffer) by having a "compact" mode, but if you're serious about using Lean you should probably have a large display anyways.
The main way I'm planning to use this is to #print a theorem and pin this so it shows in a separate window and I can step through the tactics in the written proof, and correlate things without my view on the pin constantly jumping around as the current pin changes. This also enables a clean state diff.

I definitely don't think vim fully contains all the functionality we want, but I think you managed to lay out at least a concrete example of what I've been trying to say more clearly than I did:

Then the equivalent of LeanInfoviewAddPin would be :splp; and there would finally be an obvious way to clear individual pins, namely :q!

This is precisely the kind of example I was trying to get across -- the existence already of ways to create windows-to-the-same-thing, and close those windows, and yes 100% agree that the missing piece we'd still need to add is related to pausing updates to them. (Actually there's maybe one additional thing which is that splits will be to the same buffer, so we also would need to teach the update code to notice when it has multiple windows to the same buffer with one paused how to handle that, but I believe this would be trivial to do).

The other part is that multiple pins can be shown in the same infoview. I'm somewhat happy about this because I'm not so good at vim window management.

Fair enough, I have to say that in the opposite boat, the few times I've opened a pin to try them out for a PR review or something, it makes me have the reverse experience -- I am good at vim window management, but instead of being able to use what I know, I have to figure out some new way to do things, and worry we're gonna add a whole bunch of unneeded code to support these new ways. If I added 5 pins and I want to reorder them in how they display, are we going to add a bunch of code to do that? Because in vim, reordering windows is an existing thing with code we don't get to support.

If I added 5 pins and I want to reorder them in how they display, are we going to add a bunch of code to do that? Because in vim, reordering windows is an existing thing with code we don't get to support.

I guess it's a matter of which upstream features we want to support. Because in doing this we no longer have the ability to scroll as you normally would in a vim buffer, and we also inherently limit how many pins we can have without things becoming unreadable.

I guess it's a matter of which upstream features we want to support. Because in doing this we no longer have the ability to scroll as you normally would in a vim buffer, and we also inherently limit how many pins we can have without things becoming unreadable.

How many pins do you typically have?  If each pin is a different window, you can also tile them so that they take up less space.
In an earlier comment you mentioned that scrolling is bad because then the pins jump around as you move through the file, or as the pins are being updated.  I've also found this annoying, in vscode as well.  In my eyes, this alone would be reason enough to use one window per pin.

^ actually this may be more trouble than it's worth at the moment. I'll try to see if I can get per-pin windows to work in this PR. I typically only have one or two pins so yeah there shouldn't be much issue with screen space, and we can also eventually find some way to have a "pin-switcher" so we can easily swap out pins in the window without having to delete/re-add them.

Okay @gebner @Julian this now creates one window per pin, also added some detailed tests.

Interop should almost be there in this PR, though we have a similar issue to #173 for the windows not recognizing when their buffer is changed. Plan to fix this in a subsequent PR (with tests, of course) so as to not overwhelm this one.

One more thing I think we'll want to do is distinguish between :close and :quit so that :quit removes the pin from the info, whereas :close just closes the window and leaves the pin associated with the info. Then, we could :close a pin and then open its buffer in a new tab without the buffer being deleted. We could also have telescope integration to select which :close'd pin to replace in the pin window. Again, something for a later PR.

We're still quite far away from each other designwise I think. I'm still hoping pins disappear entirely, and I don't see any benefit in the kind of functionality you're talking about with :close personally, or with say adding new ways to jump to windows, which I see you added now, rather than saying to go use a plugin to jump to windows if you want a better way to pick which window you want to go to. I still expect we'd be able to delete lots of lines if pins were just windows, which just distracts me when you talk about intricate pin functionality that personally I doubt others will use. I still don't have concrete thoughts though, I have to understand what this PR is trying to do and not do.

I absolutely need pins. As far as I understand, you'd like to just copy the infoview text into a new buffer and split. Clearly it's not that simple -- what if I have printed something and want to set_option pp.implicit true? I have to go back to that position and copy it over again? I'm not trying to make this like an IDE, this just seems like the minimum amount of new code for allowing someone to use it with interactive theorem proving on a basic level.

I have to go back to that position and copy it over again?

If I understand the example properly, no that should work functionally the same as now -- I'm not saying we don't need ways to have infoviews pause (not automatically update, just sit there dead) or unpause (as normal), and also have them track the cursor position (normal) or some other position (what a pin does now).

this just seems like the minimum amount of new code for allowing someone to use vim with interactive theorem proving on a basic level.

I think you're drastically overstating this functionality -- I don't think even you think this is basic functionality (pins, let alone each of the incremental pieces of functionality from these PRs). I have only anecdata, but from asking some VSCode users whether they know what pins are, no one said "I use them and they're essential", they either said they hadn't heard of them or use them rarely. Again though -- I'm not saying we shouldn't support the functionality at all though, just that the incremental complexity they add should match, and the design should fit within vim's norms, and I think we can improve on both before adding more functionality on top.
All that being said though, I haven't played with this PR, but if it does what it says on the tin and moves us to separate windows per pin, that's probably a nice improvement and we can merge and simplify later perhaps, so gimme a bit to play with it.

I have only anecdata, but from asking some VSCode users whether they know what pins are, no one said "I use them and they're essential", they either said they hadn't heard of them or use them rarely.

I want this to be usable for people interested in Lean's type-theoretic foundations. Sure if you don't use Lean beyond tactics you might be able to get away without this. So granted, it's not "basic", but certainly essential. Another bias here is that pins are literally unusable in VSCode in their current state beyond trivial applications.

the incremental complexity they add should match, and the design should fit within vim's norms, and I think we can improve on both before adding more functionality on top.

Again, I'm not sure what you mean by "complexity," I'd like to know if there's anything specific, like a function, conditional etc. that you think is more complex than necessary. Having said that, I have been noticing a few such areas while reworking autocmds a bit, so you may want to hold off on reviewing the code until tomorrow. While I'm at it, I think I'll just go ahead and fix #173 and implement what I was talking about with :close so that something like <C-w> T works as expected for pin windows. The goal with this PR is 100% interop :)

While I'm at it, I think I'll just go ahead and fix #173

Please do not fix multiple things in one PR. This PR already does too much, PRs need to do one and only one thing. Simplify whatever is a simplification, but do not add additional fixes or features to one PR.

I'd like to know if there's anything specific, like a function, conditional etc. that you think is more complex than necessary.

I still believe the Pin object should not exist, and that one or both of Infoview and Info should just be Window and Buffer, and that there shouldn't be code that deals with opening and closing infoviews at different positions. That's the complexity I'm referring to -- the re-creation of objects (behavior) that already exist in vim with different names and slightly different behavior, that someone gets to learn. But I'm still not expressing that clearly it seems, even if somewhere Gabriel gave a concrete example that was spot on with part of what I meant, so I'm hoping to try to spend some time just showing what an alternate implementation looks like.

Please do not fix multiple things in one PR. This PR already does too much, PRs need to do one and only one thing. Simplify whatever is a simplification, but do not add additional fixes or features to one PR.

Got it, will branch.

That's the complexity I'm referring to -- the re-creation of objects (behavior) that already exist in vim with different names and slightly different behavior, that someone gets to learn.

No one has to learn anything new. IMO all of our objects should even be private. Let me explain:

A Pin is like an extra cursor, so you don't have to go back to a position if there's a state you want to keep visible, or an elaborated theorem you have printed for example. Each pin corresponds to a buffer.
An Info is just a set of pins, it can have a current pin, diff pin, and extra pins.
The Infoview is simply a set of windows that give you a "view" on an info. Each of its pins has its own window. If you :quit a pin's window it will be deleted, and if you :close it it will be closed but not deleted, so for example if you are sharing it with another infoview (i.e. tab) as in #211, its window there will not be closed. The infoview opens windows in an arrangement you'd probably want, but you can always move the windows around as you please.

These abstractions exist only for our own sake. Perhaps it would be more productive to discuss which aspects of the above you don't agree with?

I've just tried out the PR.  To my surprise the pin was split vertically, i.e. the layout is:
 ------------------
|      |     |     |
| lean | pin | pin |
|      |     |     |
 ------------------

I wanted this instead:
 ------------------
|            | pin |
| lean        -----
|            | pin |
 ------------------

So I tried to do ctrl-w l, :spl, :b lean://pin/123, and ctrl-w l :q to get rid of the extra window.  Unfortunately this broke the infoview: it didn't update anymore.  Toggling the infoview just restores the vertical split that I don't want.  (I think I've mentioned this before but I'm still learning how to manage windows in vim.  I've since figured out that ctrl-w l ctrl-w K ctrl-w j ctrl-w H rearranges the windows without breaking the infoview.)
But it would still be great if :q didn't kill the infoview (if anything I would have expected it to remove that pin).

Unfortunately this broke the infoview: it didn't update anymore.

I can't reproduce this, so I suspect my steps are wrong. Which window did you :q, the current pin or the extra pin? By the sounds of it you quit the current pin (the one without the -- ... header) and were expecting the extra pin to update. Did updates work again when you re-opened? Also :q does mean remove that pin for an extra pin, but it means close the infoview for the current pin.

Unfortunately this broke the infoview: it didn't update anymore.

I can't reproduce this, so I suspect my steps are wrong. Which window did you :q, the current pin or the extra pin? By the sounds of it you quit the current pin (the one without the -- ... header) and were expecting the extra pin to update. Did updates work again when you re-opened?

This is maybe an easier repro: do :spl and then :q in the current pin window.  Then you have a current pin that doesn't update.  Yes, closing and reopening worked.

Also :q does mean remove that pin for an extra pin, but it means close the infoview for the current pin.

I find that a bit confusing.  As Julian says, buffers and windows should behave like normal buffers and windows and not have hidden action-at-a-distance built-in.

Also :q does mean remove that pin for an extra pin, but it means close the infoview for the current pin.

I find that a bit confusing. As Julian says, buffers and windows should behave like normal buffers and windows and not have hidden action-at-a-distance built-in.

This is a pretty old test case from run_spec.lua, it depends on whether you want :q to indicate that the infoview is closed so that reopening works as expected. For interop I plan to make :close work as you would like here.

vim users do not in my experience use both :close and :quit, I'm pretty sure most everyone just uses :quit, so I don't think we should make the two do different things for infoview windows. I know what both do, but yeah I never use :close.
(I don't have a response yet for the rest of the above, though I still find it a problem that you're defining key concepts in terms of pins, functionality I think most users of the plugin will never use, but I recognize you use the term differently than I do, so I can write out how I would define the key concepts sometime later.)

vim users do not in my experience use both :close and :quit, I'm pretty sure most everyone just uses :quit, so I don't think we should make the two do different things for infoview windows. I know what both do, but yeah I never use :close.

The distinction is that :close is automatic and :quit is manual, so for example WinClosed (but not QuitPre) is triggered on <C-w> T. Also there is a mapping for :close, <C-w> c, so I find it hard to believe that vim users don't use :close. In any case do we have a solution to wanting :q to normally indicate that the infoview is closed so that <LocalLeader> i reopens as expected afterwards, but not in this particular case?

I don't know of other plugins where one needs to use one or the other to change behavior, even ones that open windows.

"even ones that open windows" is the limiting factor here. If a plugin doesn't need to open a window, why would it even consider this?

As end-users, the two do the same thing other than some behavior with the last window opened, which is why I believe most users use :q, and I also believe most users type :q rather than using the ^W mappings (or if they do they use ^Wq)

The difference is clear to me, :q means close this window along with any buffer-related side effect that this incurs. For example it's common to have an autocmd on QuitPre that deletes the buffer. :close means just close this window with minimal side-effects.
Your model seems to conflate pins and infoviews. In general it sounds like you only want to have the "pin" layer and simply remove the concept of a set of pins (Info) or view on such a set (Infoview) entirely. Sure we could do that, but the whole point of  these layers is to make window creation/deletion automatic for Lean.
Also a diff pin is indeed nothing special, it's just another pin, there's nothing distinguishing it at the Pin layer. We just store it in a variable called Info.diff_pin on the Info level and happen to open it in a window suitable for diffs on the Infoview level.

This PR now adds the close/quit functionality, functionality I mentioned I don't want to merge, as well as does so wrapped up in this same PR?

Well it was just a few lines after I made some general improvements, and I assumed we wanted it now because of @gebner's comment? But I can revert those lines.

I haven't forgotten about these PRs FWIW -- not ignoring them, will have a look in a few more days when the semester is over and I can breathe a bit.

No worries, take it easy and no rush at all on this! I want to make sure we can all agree on the design before we commit to anything.


adding white cat option

Adds white cat as an option
Created additional cat gifs
Based on my brother's cat, Momo :)

Thanks for adding this :)


Add DRILLDOWN param in URL

DSW supports FILTER url param for widgets.
Please add DRILLDOWN url param with the value being drilldown element

DRILLDOWN:path1~path2

parameter "drilldown" (lower case), contains all drill paths separated by "~" character. parameter value should be escaped.
eg., for:
drilldown=[crimeRegionD].[H1].[crimeRegionL].&[23]~[crimeRegionD].[H1].[crimeRayonL].&[56043]
escaped version is to be:
drilldown=%5BcrimeRegionD%5D.%5BH1%5D.%5BcrimeRegionL%5D.%26%5B23%5D~%5BcrimeRegionD%5D.%5BH1%5D.%5BcrimeRayonL%5D.%26%5B56043%5D

You can omit [] for the sake of visibility.
MDX needs them only to deal with spaces
Чт, 2 сент. 2021 г. в 13:29, Anton Gnibeda @.***>:

parameter "drilldown" (lower case), contains all drill paths separated by
"~" character. parameter value should be escaped.
eg., for:
drilldown=[crimeRegionD].[H1].[crimeRegionL].&[23]~[crimeRegionD].[H1].[crimeRayonL].&[56043]
escaped version is to be:
drilldown=%5BcrimeRegionD%5D.%5BH1%5D.%5BcrimeRegionL%5D.%26%5B23%5D~%5BcrimeRegionD%5D.%5BH1%5D.%5BcrimeRayonL%5D.%26%5B56043%5D
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/intersystems-community/DeepSeeWeb/issues/208#issuecomment-911510356,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVHEP5WDTVF6ZO7MZVT5ZDT75GYXANCNFSM5DDZF53Q
.

done in 3.1.24


Type converter from kotlinx.datetime.Instant to java.time.Instant is not found

Given I have a csv file with the following columns and values:
date,description,notes
2022-07-07T19:53:15.009Z,Some description, Some notes

And kotlin data class:
import java.time.Instant

data class Record(
    val date: Instant,
    val description: String,
    val notes: String,
)

It throws an error:
org.jetbrains.kotlinx.dataframe.exceptions.TypeConverterNotFoundException: Type converter from kotlinx.datetime.Instant to java.time.Instant is not found

When I read the csv:
DataFrame.readCSV("data.csv").convertTo<Record>()

How can I make it working if I don't want to use kotlinx.datetime?

Hi! Thank you for the report. First of all, it's a bug. It makes total sense to have automatic conversion from kotlinx Instant to java Instant :) I'll fix it. As a workaround you can use ConvertSchemaDsl, but you need to import kotlinx.datetime.Instant for it to compile:
df.convertTo<Record> {
            convert<Instant>().with { it.toJavaInstant() }
}

Version with a fix 0.8.1-dev-1064

Hey @koperagen I have a question, why the PRs or commits are not related to their issues?

Yes, I think that mentioning the issue # in the commit message would be sufficient. Thanks. And sorry for bringing a topic not related to the issue.


🐛 [firebase_messaging] Crashes after updating to 14.7.10

Bug report
Describe the bug
After the update to 14.7.10 we started to see new crashes in Crashlytics (production environment).
Fatal Exception: android.os.BadParcelableException: Parcelable protocol requires subclassing from Parcelable on class com.google.firebase.messaging.o0
       at android.os.Parcel.readParcelableCreatorInternal(Parcel.java:4993)
       at android.os.Parcel.readParcelableInternal(Parcel.java:4873)
       at android.os.Parcel.readValue(Parcel.java:4633)
       at android.os.Parcel.readValue(Parcel.java:4402)
       at android.os.Parcel.-$$Nest$mreadValue()
       at android.os.Parcel$LazyValue.apply(Parcel.java:4500)
       at android.os.Parcel$LazyValue.apply(Parcel.java:4459)
       at android.os.BaseBundle.unwrapLazyValueFromMapLocked(BaseBundle.java:415)
       at android.os.BaseBundle.getValueAt(BaseBundle.java:401)
       at android.os.BaseBundle.getValue(BaseBundle.java:381)
       at android.os.BaseBundle.getValue(BaseBundle.java:364)
       at android.os.BaseBundle.getValue(BaseBundle.java:357)
       at android.os.Bundle.getParcelable(Bundle.java:913)
       at android.content.Intent.getParcelableExtra(Intent.java:9769)
       at io.flutter.plugins.firebase.messaging.FlutterFirebaseMessagingBackgroundExecutor.executeDartCallbackInBackgroundIsolate(FlutterFirebaseMessagingBackgroundExecutor.java:247)
       at io.flutter.plugins.firebase.messaging.FlutterFirebaseMessagingBackgroundService.lambda$onHandleWork$0(FlutterFirebaseMessagingBackgroundService.java:149)
       at android.os.Handler.handleCallback(Handler.java:958)
       at android.os.Handler.dispatchMessage(Handler.java:99)
       at android.os.Looper.loopOnce(Looper.java:230)
       at android.os.Looper.loop(Looper.java:319)
       at android.app.ActivityThread.main(ActivityThread.java:8893)
       at java.lang.reflect.Method.invoke(Method.java)
       at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:608)
       at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1103)

Steps to reproduce
Steps to reproduce the behavior:

Upgrade firebase_messaging package version to 14.7.10

Expected behavior
No crashes
Flutter doctor
Run flutter doctor and paste the output below:
Click To Expand
[✓] Flutter (Channel stable, 3.16.8, on macOS 14.2.1 23C71 darwin-x64, locale en-FI)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 15.2)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.2)
[✓] VS Code (version 1.85.2)
[✓] Connected device (3 available)
[✓] Network resources

Flutter dependencies
Run flutter pub deps -- --style=compact and paste the output below:
Click To Expand
Dart SDK 3.2.5
Flutter SDK 3.16.8

dependencies:
- advertising_id 2.6.0 [flutter]
- appsflyer_sdk 6.12.2 [flutter]
- cached_network_image 3.3.1 [cached_network_image_platform_interface cached_network_image_web flutter flutter_cache_manager octo_image]
- camera 0.10.5+9 [camera_android camera_avfoundation camera_platform_interface camera_web flutter flutter_plugin_android_lifecycle]
- cloud_firestore 4.14.0 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cloud_functions 4.6.0 [cloud_functions_platform_interface cloud_functions_web firebase_core firebase_core_platform_interface flutter]
- collection 1.18.0
- connectivity_plus 5.0.2 [flutter flutter_web_plugins connectivity_plus_platform_interface js meta nm]
- cupertino_icons 1.0.6
- device_apps 2.2.0 [flutter]
- device_info_plus 9.1.1 [device_info_plus_platform_interface ffi file flutter flutter_web_plugins meta win32 win32_registry]
- facebook_app_events 0.19.0 [flutter]
- file_picker 6.1.1 [flutter flutter_web_plugins flutter_plugin_android_lifecycle plugin_platform_interface ffi path win32]
- firebase_analytics 10.8.0 [firebase_analytics_platform_interface firebase_analytics_web firebase_core firebase_core_platform_interface flutter]
- firebase_auth 4.16.0 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_crashlytics 3.4.9 [firebase_core firebase_core_platform_interface firebase_crashlytics_platform_interface flutter stack_trace]
- firebase_dynamic_links 5.4.8 [firebase_core firebase_core_platform_interface firebase_dynamic_links_platform_interface flutter meta plugin_platform_interface]
- firebase_in_app_messaging 0.7.4+8 [firebase_core firebase_core_platform_interface firebase_in_app_messaging_platform_interface flutter meta]
- firebase_messaging 14.7.10 [firebase_core firebase_core_platform_interface firebase_messaging_platform_interface firebase_messaging_web flutter meta]
- firebase_remote_config 4.3.8 [firebase_core firebase_core_platform_interface firebase_remote_config_platform_interface firebase_remote_config_web flutter]
- firebase_storage 11.6.0 [firebase_core firebase_core_platform_interface firebase_storage_platform_interface firebase_storage_web flutter]
- fl_chart 0.66.1 [equatable flutter]
- flare_flutter 3.0.2 [collection flutter meta]
- flutter 0.0.0 [characters collection material_color_utilities meta vector_math web sky_engine]
- flutter_facebook_auth 6.0.4 [flutter flutter_facebook_auth_platform_interface flutter_facebook_auth_web]
- flutter_image_compress 2.1.0 [flutter flutter_image_compress_platform_interface flutter_image_compress_common flutter_image_compress_web flutter_image_compress_macos]
- flutter_inappwebview 6.0.0 [flutter flutter_inappwebview_platform_interface flutter_inappwebview_android flutter_inappwebview_ios flutter_inappwebview_macos flutter_inappwebview_web]
- flutter_keyboard_visibility 6.0.0 [meta flutter_keyboard_visibility_platform_interface flutter_keyboard_visibility_linux flutter_keyboard_visibility_macos flutter_keyboard_visibility_web flutter_keyboard_visibility_windows flutter]
- flutter_localizations 0.0.0 [flutter intl characters clock collection material_color_utilities meta path vector_math web]
- flutter_smartlook 4.1.15 [flutter]
- flutter_speed_dial 7.0.0 [flutter]
- flutter_svg 2.0.9 [flutter vector_graphics vector_graphics_codec vector_graphics_compiler]
- flutter_video_info 1.3.1 [flutter path]
- google_sign_in 6.2.1 [flutter google_sign_in_android google_sign_in_ios google_sign_in_platform_interface google_sign_in_web]
- http 1.2.0 [async http_parser meta web]
- image 4.1.4 [archive meta xml]
- image_picker 1.0.7 [flutter image_picker_android image_picker_for_web image_picker_ios image_picker_linux image_picker_macos image_picker_platform_interface image_picker_windows]
- in_app_review 2.0.8 [flutter in_app_review_platform_interface]
- in_app_update 4.2.2 [flutter]
- intl 0.18.1 [clock meta path]
- light_compressor 2.2.0 [flutter]
- mime 1.0.5
- package_info_plus 5.0.1 [ffi flutter flutter_web_plugins http meta path package_info_plus_platform_interface web win32]
- path_provider 2.1.2 [flutter path_provider_android path_provider_foundation path_provider_linux path_provider_platform_interface path_provider_windows]
- permission_handler 11.2.0 [flutter meta permission_handler_android permission_handler_apple permission_handler_html permission_handler_windows permission_handler_platform_interface]
- photo_manager 3.0.0-dev.5 [flutter]
- photo_view 0.14.0 [flutter]
- provider 6.1.1 [collection flutter nested]
- purchases_flutter 6.17.0 [flutter freezed_annotation json_annotation]
- rxdart 0.27.7
- share_plus 7.2.1 [cross_file meta mime flutter flutter_web_plugins share_plus_platform_interface file url_launcher_web url_launcher_windows url_launcher_linux url_launcher_platform_interface ffi win32]
- shared_preferences 2.2.2 [flutter shared_preferences_android shared_preferences_foundation shared_preferences_linux shared_preferences_platform_interface shared_preferences_web shared_preferences_windows]
- sign_in_with_apple 5.0.0 [flutter meta sign_in_with_apple_platform_interface sign_in_with_apple_web]
- table_calendar 3.0.9 [flutter intl simple_gesture_detector]
- unsplash_client 2.2.0 [meta http collection logging]
- url_launcher 6.2.4 [flutter url_launcher_android url_launcher_ios url_launcher_linux url_launcher_macos url_launcher_platform_interface url_launcher_web url_launcher_windows]
- uuid 4.3.3 [crypto sprintf meta fixnum]
- version 3.0.2
- video_player 2.8.2 [flutter html video_player_android video_player_avfoundation video_player_platform_interface video_player_web]
- video_thumbnail 0.5.3 [flutter]

dev dependencies:
- flutter_launcher_icons 0.13.1 [args checked_yaml cli_util image json_annotation path yaml]
- flutter_test 0.0.0 [flutter test_api matcher path fake_async clock stack_trace vector_math async boolean_selector characters collection material_color_utilities meta source_span stream_channel string_scanner term_glyph web]

dependency overrides:
- photo_manager 3.0.0-dev.5 [flutter]

transitive dependencies:
- _flutterfire_internals 1.3.16 [collection firebase_core firebase_core_platform_interface flutter meta]
- archive 3.4.10 [crypto path pointycastle]
- args 2.4.2
- async 2.11.0 [collection meta]
- boolean_selector 2.1.1 [source_span string_scanner]
- cached_network_image_platform_interface 4.0.0 [flutter flutter_cache_manager]
- cached_network_image_web 1.1.1 [cached_network_image_platform_interface flutter flutter_cache_manager]
- camera_android 0.10.8+16 [camera_platform_interface flutter flutter_plugin_android_lifecycle stream_transform]
- camera_avfoundation 0.9.14 [camera_platform_interface flutter stream_transform]
- camera_platform_interface 2.7.2 [cross_file flutter plugin_platform_interface stream_transform]
- camera_web 0.3.2+4 [camera_platform_interface flutter flutter_web_plugins stream_transform]
- characters 1.3.0
- checked_yaml 2.0.3 [json_annotation source_span yaml]
- cli_util 0.4.1 [meta path]
- clock 1.1.1
- cloud_firestore_platform_interface 6.1.0 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- cloud_firestore_web 3.9.0 [_flutterfire_internals cloud_firestore_platform_interface collection firebase_core firebase_core_web flutter flutter_web_plugins js]
- cloud_functions_platform_interface 5.5.11 [firebase_core flutter meta plugin_platform_interface]
- cloud_functions_web 4.6.11 [cloud_functions_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- connectivity_plus_platform_interface 1.2.4 [flutter meta plugin_platform_interface]
- convert 3.1.1 [typed_data]
- cross_file 0.3.3+8 [meta web]
- crypto 3.0.3 [typed_data]
- csslib 1.0.0 [source_span]
- dbus 0.7.10 [args ffi meta xml]
- device_info_plus_platform_interface 7.0.0 [flutter meta plugin_platform_interface]
- equatable 2.0.5 [collection meta]
- fake_async 1.3.1 [clock collection]
- ffi 2.1.0
- file 7.0.0 [meta path]
- file_selector_linux 0.9.2+1 [cross_file file_selector_platform_interface flutter]
- file_selector_macos 0.9.3+3 [cross_file file_selector_platform_interface flutter]
- file_selector_platform_interface 2.6.2 [cross_file flutter http plugin_platform_interface]
- file_selector_windows 0.9.3+1 [cross_file file_selector_platform_interface flutter]
- firebase_analytics_platform_interface 3.9.0 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_analytics_web 0.5.5+12 [_flutterfire_internals firebase_analytics_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins js]
- firebase_auth_platform_interface 7.0.9 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 5.8.13 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser js meta]
- firebase_core 2.24.2 [firebase_core_platform_interface firebase_core_web flutter meta]
- firebase_core_platform_interface 5.0.0 [collection flutter flutter_test meta plugin_platform_interface]
- firebase_core_web 2.10.0 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- firebase_crashlytics_platform_interface 3.6.16 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_dynamic_links_platform_interface 0.2.6+16 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_in_app_messaging_platform_interface 0.2.4+16 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_platform_interface 4.5.18 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_messaging_web 3.5.18 [_flutterfire_internals firebase_core firebase_core_web firebase_messaging_platform_interface flutter flutter_web_plugins js meta]
- firebase_remote_config_platform_interface 1.4.16 [_flutterfire_internals firebase_core flutter meta plugin_platform_interface]
- firebase_remote_config_web 1.4.16 [firebase_core firebase_core_web firebase_remote_config_platform_interface flutter flutter_web_plugins js]
- firebase_storage_platform_interface 5.1.3 [_flutterfire_internals collection firebase_core flutter meta plugin_platform_interface]
- firebase_storage_web 3.6.17 [_flutterfire_internals async firebase_core firebase_core_web firebase_storage_platform_interface flutter flutter_web_plugins http js meta]
- fixnum 1.1.0
- flutter_cache_manager 3.3.1 [clock collection file flutter http path path_provider rxdart sqflite uuid]
- flutter_facebook_auth_platform_interface 5.0.0 [flutter plugin_platform_interface]
- flutter_facebook_auth_web 5.0.0 [flutter flutter_web_plugins js flutter_facebook_auth_platform_interface]
- flutter_image_compress_common 1.0.3 [flutter flutter_image_compress_platform_interface]
- flutter_image_compress_macos 1.0.1 [flutter flutter_image_compress_platform_interface]
- flutter_image_compress_platform_interface 1.0.3 [flutter plugin_platform_interface cross_file]
- flutter_image_compress_web 0.1.3+2 [flutter flutter_web_plugins flutter_image_compress_platform_interface js]
- flutter_inappwebview_android 1.0.12 [flutter flutter_inappwebview_platform_interface]
- flutter_inappwebview_internal_annotations 1.1.1
- flutter_inappwebview_ios 1.0.13 [flutter flutter_inappwebview_platform_interface]
- flutter_inappwebview_macos 1.0.11 [flutter flutter_inappwebview_platform_interface]
- flutter_inappwebview_platform_interface 1.0.10 [flutter flutter_inappwebview_internal_annotations plugin_platform_interface]
- flutter_inappwebview_web 1.0.8 [flutter flutter_web_plugins js flutter_inappwebview_platform_interface]
- flutter_keyboard_visibility_linux 1.0.0 [flutter_keyboard_visibility_platform_interface flutter]
- flutter_keyboard_visibility_macos 1.0.0 [flutter_keyboard_visibility_platform_interface flutter]
- flutter_keyboard_visibility_platform_interface 2.0.0 [flutter meta plugin_platform_interface]
- flutter_keyboard_visibility_web 2.0.0 [flutter_keyboard_visibility_platform_interface flutter_web_plugins flutter]
- flutter_keyboard_visibility_windows 1.0.0 [flutter_keyboard_visibility_platform_interface flutter]
- flutter_plugin_android_lifecycle 2.0.17 [flutter]
- flutter_web_plugins 0.0.0 [flutter characters collection material_color_utilities meta vector_math web]
- freezed_annotation 2.4.1 [collection json_annotation meta]
- google_identity_services_web 0.3.0+2 [meta web]
- google_sign_in_android 6.1.21 [flutter google_sign_in_platform_interface]
- google_sign_in_ios 5.7.3 [flutter google_sign_in_platform_interface]
- google_sign_in_platform_interface 2.4.5 [flutter plugin_platform_interface]
- google_sign_in_web 0.12.3+2 [flutter flutter_web_plugins google_identity_services_web google_sign_in_platform_interface http web]
- html 0.15.4 [csslib source_span]
- http_parser 4.0.2 [collection source_span string_scanner typed_data]
- image_picker_android 0.8.9+3 [flutter flutter_plugin_android_lifecycle image_picker_platform_interface]
- image_picker_for_web 3.0.2 [flutter flutter_web_plugins image_picker_platform_interface mime]
- image_picker_ios 0.8.9+1 [flutter image_picker_platform_interface]
- image_picker_linux 0.2.1+1 [file_selector_linux file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_macos 0.2.1+1 [file_selector_macos file_selector_platform_interface flutter image_picker_platform_interface]
- image_picker_platform_interface 2.9.3 [cross_file flutter http plugin_platform_interface]
- image_picker_windows 0.2.1+1 [file_selector_platform_interface file_selector_windows flutter image_picker_platform_interface]
- in_app_review_platform_interface 2.0.5 [flutter url_launcher plugin_platform_interface platform]
- js 0.6.7 [meta]
- json_annotation 4.8.1 [meta]
- logging 1.2.0
- matcher 0.12.16 [async meta stack_trace term_glyph test_api]
- material_color_utilities 0.5.0 [collection]
- meta 1.10.0
- nested 1.0.0 [flutter]
- nm 0.5.0 [dbus]
- octo_image 2.0.0 [flutter]
- package_info_plus_platform_interface 2.0.1 [flutter meta plugin_platform_interface]
- path 1.8.3
- path_parsing 1.0.1 [vector_math meta]
- path_provider_android 2.2.2 [flutter path_provider_platform_interface]
- path_provider_foundation 2.3.2 [flutter path_provider_platform_interface]
- path_provider_linux 2.2.1 [ffi flutter path path_provider_platform_interface xdg_directories]
- path_provider_platform_interface 2.1.2 [flutter platform plugin_platform_interface]
- path_provider_windows 2.2.1 [ffi flutter path path_provider_platform_interface win32]
- permission_handler_android 12.0.3 [flutter permission_handler_platform_interface]
- permission_handler_apple 9.3.0 [flutter permission_handler_platform_interface]
- permission_handler_html 0.1.1 [flutter flutter_web_plugins permission_handler_platform_interface]
- permission_handler_platform_interface 4.1.0 [flutter meta plugin_platform_interface]
- permission_handler_windows 0.2.1 [flutter permission_handler_platform_interface]
- petitparser 6.0.2 [meta]
- platform 3.1.4
- plugin_platform_interface 2.1.8 [meta]
- pointycastle 3.7.4 [collection convert js]
- share_plus_platform_interface 3.3.1 [cross_file flutter meta mime plugin_platform_interface path_provider uuid]
- shared_preferences_android 2.2.1 [flutter shared_preferences_platform_interface]
- shared_preferences_foundation 2.3.5 [flutter shared_preferences_platform_interface]
- shared_preferences_linux 2.3.2 [file flutter path path_provider_linux path_provider_platform_interface shared_preferences_platform_interface]
- shared_preferences_platform_interface 2.3.2 [flutter plugin_platform_interface]
- shared_preferences_web 2.2.2 [flutter flutter_web_plugins shared_preferences_platform_interface web]
- shared_preferences_windows 2.3.2 [file flutter path path_provider_platform_interface path_provider_windows shared_preferences_platform_interface]
- sign_in_with_apple_platform_interface 1.0.0 [flutter plugin_platform_interface meta]
- sign_in_with_apple_web 1.0.1 [flutter flutter_web_plugins sign_in_with_apple_platform_interface js]
- simple_gesture_detector 0.2.0 [flutter]
- sky_engine 0.0.99
- source_span 1.10.0 [collection path term_glyph]
- sprintf 7.0.0
- sqflite 2.3.1 [flutter sqflite_common path]
- sqflite_common 2.5.3 [synchronized path meta]
- stack_trace 1.11.1 [path]
- stream_channel 2.1.2 [async]
- stream_transform 2.1.0
- string_scanner 1.2.0 [source_span]
- synchronized 3.1.0+1
- term_glyph 1.2.1
- test_api 0.6.1 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph]
- typed_data 1.3.2 [collection]
- url_launcher_android 6.2.2 [flutter url_launcher_platform_interface]
- url_launcher_ios 6.2.4 [flutter url_launcher_platform_interface]
- url_launcher_linux 3.1.1 [flutter url_launcher_platform_interface]
- url_launcher_macos 3.1.0 [flutter url_launcher_platform_interface]
- url_launcher_platform_interface 2.3.1 [flutter plugin_platform_interface]
- url_launcher_web 2.2.3 [flutter flutter_web_plugins url_launcher_platform_interface web]
- url_launcher_windows 3.1.1 [flutter url_launcher_platform_interface]
- vector_graphics 1.1.9+2 [flutter vector_graphics_codec]
- vector_graphics_codec 1.1.9+2
- vector_graphics_compiler 1.1.9+2 [args meta path_parsing xml vector_graphics_codec path]
- vector_math 2.1.4
- video_player_android 2.4.11 [flutter video_player_platform_interface]
- video_player_avfoundation 2.5.6 [flutter video_player_platform_interface]
- video_player_platform_interface 6.2.2 [flutter plugin_platform_interface]
- video_player_web 2.1.3 [flutter flutter_web_plugins video_player_platform_interface]
- web 0.3.0
- win32 5.2.0 [ffi]
- win32_registry 1.1.2 [ffi win32]
- xdg_directories 1.0.4 [meta path]
- xml 6.5.0 [collection meta petitparser]
- yaml 3.1.2 [collection source_span string_scanner]

Hi @pafciu17, are you able to reproduce the crash locally or is it happening only in production?
If you are able to reproduce the crash locally, please provide steps to reproduce the issue so that we can investigate the issue.
Thank you

Hi @danagbemava-nc, thank you for quick reply.
Only in production - unfortunately, so far, I didn't manage to reproduce it myself.

Hi @pafciu17, how are you triggering notifications for your app? Are you using the firebase admin sdk or another service to push the notifications?

Hey @danagbemava-nc, yes, it is being handled with Firebase Admin SDK.

Thanks for the info. One final thing, how many instances of this crash have you experience and how many users are affected by this?

It would be 18 crashes, 12 users affected, within 6 days.

Thanks for the update.
This looks similar to https://github.com/firebase/flutterfire/issues/11901 albeit at a different crash point.
Labeling based on the information provided above.
cc @russellwheatley


Escape keydown handled by modal instead of lightbox

Steps to reproduce the behavior:
Use react-images inside a react-modal
Expected behavior:
ESC button close only the lightbox
Actual behavior:
ESC button close the modal, but the lightbox close event is not fired. Here's a simple reproduction: https://codesandbox.io/s/rrxq8w417q
It seems that the keydown event is handled by the modal because the modal is still in focus (instead of the lightbox). If I click on the lightbox first before pressing ESC, it works as expected.

fixed in v1


Add first version of point data spec (refs #23)

A first crack at internal structure. Simple for now, will need additions as we grow (i.e. additional metadata)

re: our discussion of geojson vs. coordinates/fields, I think that it's likely better to store geojson until it becomes a problem.
Also, do you have any attachment to your load date format? Could we do Unix time?

Yeah date should be Unix time, it isn't for a specific reason in that doc. Will explain at our next standup


Random respring when attempt to open app switcher

Describe the bug
Previous version of unc0ver(4.x.x) give me a random respring a lot, but with 5.0.1 version I experienced better, the random respring is reduced significantly.
but one thing that certain the respring always occurs when I tried to open app switcher. probably this could help devs to find out what causes it.
To Reproduce
Steps to reproduce the behavior:

Open app switcher (the respring randomly occurs)

Screenshots
If applicable, add screenshots to help explain your problem.
Device (please complete the following information):

iOS Version: iOS 13.5
iOS Device: A12 (iPhone XS)
unc0ver Version: 5.0.1

Place an "x" between the brackets if true:

[X] this is a bug others will be able to reproduce
[ ] this issue is present with all tweaks uninstalled(except for default packages) or disabled
[ ] this issue is present after a rootfs restore
[X] this issue is present on the latest version of unc0ver

Logs
If applicable, add logs or error messages here.

Me Too.I use unc0ver 5.0.1 on iPhone X with iOS 13.5

Are you using the tweak "gesto"  or something similar? If so uninstall and see if that fixes it.

nope, probably tweak related to app switcher I'm using QuitAll. I'll try to disable this tweak and let you know if that solves the problem.

Nope，I did not use “ gesto” tweak.

I could confirm, disabling QuitAll is not solve this.

Then you need to go through each and every tweak until you find the one causing the problem.

Since previous version the random respring is oftenly happen, i assume there is no problem with my installed tweaks.


Google.yaml attention

Hello Everyone
and thanks to the team EVILGINX for creating that awesome bypass f2a
I just wanna a Help please with phishlets google
here is the code  : https://github.com/elktarni/google.yaml/blob/master/google
can anyone make some edit for it
I encountered some issue

@ewhitman1 did you managed to finish google phishlet. kindly share. I am a beginner and the documentation for creating the phishlet is not suitable for beginners.

@ewhitman1 tried your txt file and get hung up on my dev terminal with a
WARN: Cannot handshake client ssl.gstatic.com EOF
On my test device it will show me a login page but all links are dead. Any suggestions?

@kgretzky Hi, able to remove timed out issue from google but after tapping yes on my device and matching the number shown , I am unable to submit it

@ewhitman1 were you able to fix this? i'm using your google1.yaml file and have same issue. Google sends prompt to phone but when I tap the number on the screen it doesn't forward me to next page. Or sometimes I get a timeout error. Let me know if there is edit to phishlet which can fix this.

I want to know, at the moment, the work of phishlets for google exists????

[10:09:25] [err] failed to load phishlet 'google.yaml': missing login section
getting this error

The request timed out error happens due to Google's security protection hidden in obfuscated JS code. Only happens for push notifications.

i know its an old message, but i want to know if you have successfully bypassed this then at least i know its doable, looking at it for a while all i could is stop the error. it wont submit

@kgretzky  why does the cookies sessions expire too quickly ? not even up to 30 minute, it you dont use the cookies asap it will expire and wont be able to use it


Roadmap of cdp

We keep this issue open to collect feature requests from users and hear your voice. Our release plan is also available here.
You can either:
Suggest a new feature by leaving a comment.
Vote for a feature request with 👍 or be against with 👎.
Tell us that you would like to help implement one of the features in the list or review the PRs. (This is the greatest things to hear about!:laughing:)

Make the models exportable to: ONNX and TFLite :smile:


Does the readme need updating?

On the readme, the schema is listed as having mappings, and translations (as in cuttlefish), but in the generated schema, there's mappings, transforms, and validators. This leads me to think that the readme is quite a bit out of date - is this correct, or am I reading it wrong? Is there a canonical place for up to date documentation?

@brentonannan You are absolutely correct, I'll push updated documentation today sometime.

Updated the README and some other errors I spotted.

Thanks a lot mate =D

@bitwalker Currently there is example of translation using
case _mapping, val ->
#code
end

Such expressions causes compilation error on Elixir 1.2 (case/3 not defined).

@rafal-radziszewski Fixed, thanks!


Make normalize_whitespace faster

This had significant consequences on a program of mine.
Before:
real	0m5.776s
user	0m4.150s
sys	0m0.077s

After:
real	0m4.261s
user	0m4.130s
sys	0m0.073s

(That's more than a second difference!)
(breadability is called on ± 30 pages during my script execution)
This drops the distinction between \n and whitespaces, but from what I've understood, this distinction is actually not used in the code after.

I think you should look at user time.
And your solution doesn't preserve new lines which may be significant for someone (e.g. for me :). It's great to have code fast but it should work in the first place :)


window.React.createClass is not a function, Cannot read property 'createClass' of undefined

I have what I mentioned earlier here working successfully with the Server integration.
So just refactoring to React.js Element taking your comment onboard.
My code:
import React from 'react'
import ReactDOM from 'react-dom'

;(window as any).React = React
;(window as any).ReactDOM = ReactDOM

export default (window as any).React.createClass({
  render: function() {
    let client = {
      ...
    }

    const payment = async () => {
      ...
    }

    const onAuthorize = async (data, _actions) => {
      ...
    }

    let PayPalButton = (window as any).paypal.Button.driver('react', {
      React,
      ReactDOM,
    })

    return (

          Buy Full Body Lobster Onesie - $24.99 now!

        <PayPalButton
          client={client}
          env={env.ENV === 'local' ? 'sandbox' : 'production'}
          payment={payment}
          commit={true}
          onAuthorize={onAuthorize}
        />

    )
  },
})

But getting:
window.React.createClass is not a function
TypeError: window.React.createClass is not a function at Module../components/paypal/button.tsx (http://localhost:4000/_next/static/chunks/1.js:43:77) at __webpack_require__ (http://localhost:4000/_next/static/runtime/webpack.js:790:31) at fn (http://localhost:4000/_next/static/runtime/webpack.js:151:20)

And if I leave out:
;(window as any).React = React
;(window as any).ReactDOM = ReactDOM

I get:
Cannot read property 'createClass' of undefined
TypeError: Cannot read property 'createClass' of undefined at Module../components/paypal/button.tsx (http://localhost:4000/_next/static/chunks/1.js:53:77) at __webpack_require__ (http://localhost:4000/_next/static/runtime/webpack.js:790:31) at fn (http://localhost:4000/_next/static/runtime/webpack.js:151:20)

Any ideas?
Many thanks,
Leo

Do you have a page where we can repro?

Hey @leotm,
The reason why you are getting Cannot read property 'createClass' of undefined is because you're no longer assigning React to your window object, but you're referencing from there. Can you remove that and try again?

Closing for now. Please feel free to re-open this issue if there's an update from your side.


added docs for azure blob

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: IsharaPannila sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the PR @IsharaPannila! I've added a few comments to improve it from a reading/explanatory perspective.
Would you mind having a look?


Better ide/site build

Sorry to break the current workflow but I think this will benefit in the long term. Please kindly consider this.
Changes

Extract html, css, js from make_ide and make_site to static
npm run build:site is now the replacement for npm run make_ide and npm run make_site
use webpack to bundle site scripts instead of catsrc
Github Pages may not work

Benefits

compiled files will not be included in the repo source (keep the repo clean)
better management of html css js (and syntax highlight for dev)
require will be bundled correctly, no need to use try {...} catch {...} now
able to use Netlify, no more manual build
improve the maintainability for future changes

If you would like to give Netlify a try, here is how (Neltify is free for one user only, sorry I can not do it for you)

Create an account and link to Github

Setup the build command and it's good to go

It will give you a random name for the site, you can change it in the settings

or if you want to bind your custom domain:

Here is the demo I created in Netlify on this branch
Site:
https://wenyan-lang-antfu.netlify.com/
IDE:
https://wenyan-lang-antfu.netlify.com/ide

I guess you're correct, it's time to do the right thing ;) Plus, we can take the opportunity to migrate to wy-lang.org.
I'll setup netlify today.
I think it might be a good idea to still have placeholder html's in /site that simply do a redirect. e.g.

Thanks!

@LingDong- Great! I also added a meta tag for redirecting.

  <meta http-equiv="Refresh" content="0; url=http://wy-lang.org"/>

Please visit http://wy-lang.org instead.

Just migrated to netlify and wy-lang.org. Everything seems to be working :D Let me know if I missed anything.

LGTM👍
A side note, you if are interested enabling https, Netlify can do it by very simple setups. Just under settings>domain management>https.😆

@antfu Just checked, and I think https is already enabled. Didn't notice before. I'll change the readme to reflect that. Thanks!


Remake schedule page

Closes #35.

Great work guys!!
I find a little catch in classes with type O, which I don't know what it means (online?). There is no subtitle for that type in the currently Sigarra. The class is "O"

Whoops, I had never seen that class type before, nice catch! Looking at the course unit info, 'O' seems to stand for "Outra". @toni-santos which color shall we use for it? The default is gray.

Great work guys!!
I find a little catch in classes with type O, which I don't know what it means (online?). There is no subtitle for that type in the currently Sigarra. The class is "O"

Whoops, I had never seen that class type before, nice catch! Looking at the course unit info, 'O' seems to stand for "Outra". @toni-santos which color shall we use for it? The default is gray.

Seeing as this type of class in particular does not fit into any of the established types of classes (Practical, Theoretic, ...) and as such lacks the same semantic meaning there isn't much in terms of color coordination that we are able to do. With this being said, I believe using grey (or similar) would be the best option as it not only keeps with the color that users already know but it also does not take away emphasis from other color combinations we already established.

I have added colors for these classes, please check if it is working :)

I have added colors for these classes, please check if it is working :)

The selector was missing in the code, but it's working now

It appears that O is some kind of a special case. Its content is not inside a div.

That's weird, that should have been fixed with my last commit, are you sure you pulled all the changes?

That's weird, that should have been fixed with my last commit, are you sure you pulled all the changes?

Sorry, its working.
I notice the content-script weren't beeing rebuild.
Great work!!
✅ 🛫


expanding for different types

How would I expand the ffi.rs to allow for more different types, such as 'u8'
Sincerely,
Dallyshalla

pub enum QrsVariantType {
Invalid = 0,
Int64,
String
}
pub fn qmlrs_variant_create() -> *mut QVariant;
pub fn qmlrs_variant_destroy(v: *mut QVariant);
pub fn qmlrs_variant_set_int64(var: *mut QVariant, x: i64);
pub fn qmlrs_variant_set_invalid(var: *mut QVariant);
pub fn qmlrs_variant_set_string(var: *mut QVariant, len: c_uint, data: *const c_char);
pub fn qmlrs_variant_get_type(var: *const QVariant) -> QrsVariantType;
pub fn qmlrs_variant_get_int64(var: *const QVariant, x: *mut i64);
pub fn qmlrs_variant_get_string_length(var: *const QVariant, out: *mut c_uint);
pub fn qmlrs_variant_get_string_data(var: *const QVariant, out: *mut c_char);

I was curious, too and added bool (instead of u8). I modified the factorial example such that it randomly gets true, false as input (and returns it without modification) Have a look at https://github.com/Liamsi/qmlrs/commit/c9356c814b8dd225783e225dd887f21d5617cf8a  to get an idea on howto expand to other types. The diff should be self explanatory.


just: build offline documentation

@xrelkd @jk @adamcstephens I still can't figure when github automatically ping maintainers and when it does not, so I'll do it manually.

Result of nixpkgs-review pr 229591 run on x86_64-linux 1

2 packages failed to build:

dogdns
dogdns.man

4 packages built:

just
just.doc
just.man
kabeljau

dogdns build failure looks unrelated.

@Mic92 did you mean to close this?

Wrong button


Tests stability

Apart from https://github.com/Microsoft/RTVS/issues/2001 All tests pass consistently together on my two machines. Changes:

Make sure editor tree and documents are disposed of. Otherwise they stay attached to idle and throw when called on wrong thread.
Idle event can specify which thread to fire at.
Some tests had hardcoded R 3.2, Now use RInstallation
RInstallation static didn't work well since registry mocks affected tests that expected real registry when running in parallel
Export provider should not be disposed since tests dispose it before WPF window is fully closed and all view and editor components are disposed of.

:+1: