Typescript errors appearing out of nowhere, changing language mode back and forth makes them disappear

VSCode Version: Code 1.13.1 (379d2efb5539b09112c793d3d9a413017d736f89, 2017-06-14T18:21:47.485Z)
OS Version: Windows_NT ia32 6.3.9600
Extensions:

Extension
Author
Version

html-snippets
abusaidm
0.1.0

vscode-css-formatter
aeschli
0.0.2

vscode-angular2-files
alexiv
1.3.8

Angular2
johnpapa
2.3.3

tsimporter
pmneo
1.2.14

vscode-icons
robertohuertasm
7.9.0

Steps to Reproduce:

Code
Errors suddenly appear even if there are none
How to fix temporarily:
Change language mode to something else
Switch back to Typescript and they will be gone
Keep coding and they will appear again
Go to Step 4 and repeat

This started happening 3 days ago not sure if update broke it

A few questions to help investigate:

What error are you seeing?
Can you share that code you are working with and some repo steps?
Does this repo in all projects or just a specific one?
Does this happen if you disable all extensions? Start code with the --disable-extensions command line flag to check this

Thanks

I realized It happened while working on exactly two files of my project. These files were at first created using the following names: Something.dynamic.ts and Something.dynamic.quadtree.ts. They were later renamed to something.dynamic.ts and something.dynamic.ts.
Things I noticed:

The integrated Git Source control did not notice the change.
I was importing using import { Dynamic } from '.....Something.dynamic' instead of the new 'something.dynamic';
Sometimes a second tab would open, one with 'something...' and the other one using 'Something....' which appeared as unsaved showing a grey dot on it.
I managed to fix it by renaming the files back to Something.dynamic, etc...

Hope this helps

Please try out the latest VSCode insiders and VSCode 1.15 once it comes out later this week. There was a bug that could have been causing this but I have not been able to reproduce it reliably on my own


Restructure Personal settings > notifications section.

#19717

GIFs or screenshots:

@alya @timabbott any feedback on the GIF added above?

Great, thanks!
I was thinking "Email message notifications" and "Other emails" as top-level headings (without the "Email") heading, since it feels more consistent with the headings above. Gut I don't have strong feelings on this.

I also think that would be better, made the changes.

Great, thanks!

This is awesome, merged, thanks @sahil839!
We should do a quick check for whether any of our /help/ articles around notifications need tweaks following this merge.

Opened #19736 for updating help pages.


added cookiesFile config param

What do you think, is it a bad or good idea to parse output of './phantomjs -h' and detect params automatically?

I'd say for now I'd like to continue doing it manually but I'm going to go ahead and just add a bunch of the PhantomJS options now in another PR. Figure I may as well add as many as possible that would apply to this project.

For future reference, PR #38 adds the rest of the PhantomJS CLI options


Improve load-balancer health monitor tests

When a cluster only has one worker node, the pods get scheduled
in this worker node by default. In the case of ETP:local test
the requested two Pods were scheduled in the same worker node,
consequently only one LB member had ACTIVE state due to health monitors
and the test expected for two ACTIVE members. This commit fixes the issue by
ensuring that the amount of worker nodes is taken into consideration
when defining the amount of Pod replicas.

Hey @MaysaMacedo, shouldn't be two members if the svc is backed by two pods (even in one master node deployment)?

@rlobillo even if the cluster does not have only one worker node, it's possible that the two Pods gets scheduled in the same worker node. We need to add protection for this case, which is missing in this PR, so I will add hold until I fix it.
/hold

@MaysaMacedo ack, it makes sense yep, as the LB monitors the nodeports and not the pods

/hold cancel


Cannot run script

Hello,
I am getting an error.
087692009900
Looking up the product_id
404
Traceback (most recent call last):
File "./barcode_reader.py", line 309, in
decrease_inventory(upc)
File "./barcode_reader.py", line 69, in decrease_inventory
product_id_lookup(upc)
File "./barcode_reader.py", line 114, in product_id_lookup
j = r.json()
File "/usr/local/lib/python2.7/dist-packages/requests/models.py", line 898, in                                                                                json
return complexjson.loads(self.text, **kwargs)
File "/usr/lib/python2.7/json/init.py", line 339, in loads
return _default_decoder.decode(s)
File "/usr/lib/python2.7/json/decoder.py", line 367, in decode
raise ValueError(errmsg("Extra data", s, end, len(s)))
ValueError: Extra data: line 1 column 4 - line 1 column 15 (char 3 - 14)
Exception TypeError: TypeError('super() takes at least 1 argument (0 given)',) i                                                                                n <bound method InputDevice.del of InputDevice('/dev/input/event0')> ignored
I am running it on a raspberrypi 4.
Also, what value am I supposed to enter by "UPC_DATABASE_API=?
Thank you

For the UPC database Api you'll have to register an account there and request it.  Not sure if the pi model is an issue or not but all I have access to is just 3's at the moment.
I'm not entirely sure whats causing this error to throw but I"ll take a look here and see what I can figure out.

Can the problem be that I am using SSL?
Is there a way for me to get it to work over SSL?
Thank you


startTime and duration not working

There is no difference on iOS when using
starttime: 2
duration: 4
in compressVideo()
I still get full length of compressed video. No errors, just same length (full video length of the original file).

Same issue for me as well, any solution?

Same


Move poshspec plugins to a separate module

Grouping similar specs

Http , WebSite, and AppPool = Web
TcpPort, Interface, DnsHost and Firewall = Network

Additional parameters for specs
Many of the specs (such as Service) don't provide access to all of the properties of the object under test

Duplicate of #98


fixes issue #227 (WIP)

Fixes #227
Removed JSONB type and created scanners/valuers per struct.
Testing
Needs tests

Closing as we had some conflicts and I had to push in a new branch as I already fixed the issues that @stanimirdim92 encountered. See #248


Add page showing supported terraform versions

Addresses https://github.com/gruntwork-io/terragrunt/issues/1359
This creates a new page that shows users which terraform versions have been officially tested with our terragrunt releases. But includes a caveat to highlight that members of the community have tried and confirmed the version scope is not rigid.

Thanks for review! Merging now.


Add dark mode on HTML test report

Issue: #12103
Signed-off-by: Philippe FICHET<EMAIL_ADDRESS>Context
Add dark mode for HTML test report based on media queries level 5 and prefers-color-scheme
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[-] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[ ] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:check

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

This is how it looks like on my machine with dark mode:

@philippefichet is this correct?

Thanks @philippefichet @rlucha !

@big-guy why was this reverted ?


Remove vscode-uri bundler workaround

Microsoft has finally released a node (and bundler) compatible ESM version of vscode-uri (3.0.8). See also https://github.com/microsoft/vscode-uri/pull/39.
This change removes the workaround that was needed in Langium to use the values exported by vscode-uri.

cc @kaisalmen please retest with your vite config to ensure that the bundling behavior is correct in vite.

Thanks, will double check.


Scaladoc hygiene for base package

As more stuff gets moved directly under io.finch, its API docs are getting a little unwieldy. It'd be nice to make prioritization traits private[finch] so they don't show up in the docs (their methods still will, though), and possibly even to organize the definitions using Scaladoc groups (see e.g. how I'm using them in circe).

Great idea!

I'd like to take this one.

This is great @lukewyman! Let us know if you need any help with that.

Thanks, @vkostyukov. I've been picking through the code and I can't quite find a case of (or might not understand completely) a prioritaztion trait. Can you possibly provide me with a place in the code as an example so that I can pick up the pattern? @travisbrown

Perhaps io.finch.internal.Mapper is an example? object Mapper would be the public level, and then the traits lower in the chain in that file (HighPriorityMapperConversions and LowPriorityMapperConversions) would get the private[finch] ?

I'm going to move that to the next milestone so we can revisit that later and see what's left here.


recyclerview的子布局没有被适配

Environment

[x] Autosize Version:
[x] Target Android Version:
[x] Device Model:
[x] Device Resolution:
[x] Design Size On AndroidManifest:

Bug Description:

Log:

Screenshot

Related Code:

Others:

https://github.com/JessYanCoding/AndroidAutoSize/issues/59


Added data-cargo-features attribute for rust asset type

Adds data-cargo-features attribute for rust asset type. This pull request partially fixes issue #60.
The implementation is still missing --all-features and --no-default-features flags. I did not need these flags.

Also, if you don't mind rebasing that would be awesome. If not, I'm happy to do a quick update merge.

My plan is to merge this once CI is green. Then I'm going to make the aforementioned example updates, verification, and then get this shipped out as part of the 0.11.0 release.

@davewarn just reporting back here. Everything appears to be working quite nicely! Using the space separated values seems to work perfectly well. I also tested out what would happen if an invalid feature is passed along.
In the index.html:
<link data-trunk rel="rust" [...] data-cargo-features="demo-does-not-exist"/>

Output from invoking a trunk build (as expected):
error: Package `yew-example v0.1.0 (/Users/doddzilla/src/github.com/thedodd/trunk/examples/yew)` does not have the feature `demo-does-not-exist`
Apr 13 19:58:10.032 ERROR ❌ error
error from HTML pipeline

Caused by:
    0: failed to spawn assets finalization
    1: error during cargo build execution
    2: cargo call returned a bad status

@thedodd That is great news. You beat me to the testing. Thank you so much!
btw, i am really enjoying using trunk, it is so convenient and easy to use. You guys are doing a great job!

Awesome! Happy to hear it. Thanks for contributing!


[stable/redis-ha] server-0 failure can result in split-brain

Is this a request for help?: No

Is this a BUG REPORT or FEATURE REQUEST? (choose one): BUG REPORT

Version of Helm and Kubernetes:
Helm version:
Client: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.11.0", GitCommit:"2e55dbe1fdb5fdb96b75ff144a339489417b146b", GitTreeState:"clean"}

Kubernetes version:
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.2", GitCommit:"17c77c7898218073f14c8d573582e8d2313dc740", GitTreeState:"clean", BuildDate:"2018-10-24T06:54:59Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"11+", GitVersion:"v1.11.2-gke.18", GitCommit:"5796233393d7bc034428de15191ad3d2eaff95fb", GitTreeState:"clean", BuildDate:"2018-11-08T20:49:08Z", GoVersion:"go1.10.3b4", Compiler:"gc", Platform:"linux/amd64"}

Which chart:
redis-ha
What happened:
A single node failure (out of 3) resulted in a redis outage due to bad logic in redis-ha chart.

Server 0 crashed / had a network partition with the other nodes
Server 0 rebooted
Server 0 could not reach the other nodes while it was starting up so it decided it was the master (https://github.com/helm/charts/blob/master/stable/redis-ha/templates/redis-ha-configmap.yaml#L57)
Server 0 thinks it's master indefinitely and is waiting for other nodes to connect to it; it cannot learn about the other nodes at this point because it thought it was the first to start up and is just waiting for others to connect to it
Servers 1 and 2 marked server 0 as down and correctly failed over and are both in agreement about the new master (Server 1)
Our Rails pods never learn about the failover because they are configured to ask the Sentinel on Server 0 who the master is first; since Sentinel on Server 0 keeps replying successfully that it is the master, the Rails pods never bother to ask Sentinel 1 or Sentinel 2
Rails tries to write to Server 0
Writes fail because Server 0 has no slaves to replicate to and rejects the write
System was stuck in this state indefinitely until we manually rebooted Server 0 and it initialized itself correctly as a slave

What you expected to happen:
I expected Server 0 not to believe that it is the master indefinitely when it isn't connected to any of the other nodes. I expected Sentinel on Server 0 to report that it doesn't know who the master is and to eventually report the correct master.
How to reproduce it (as minimally and precisely as possible):

Cut off network connectivity from the node that hosts the server-0 pod to the nodes hosting server-1 and server-2.
Restart the server-0 pod.
Restore network connectivity

server-1 or server-2 will be the new master but the sentinel on server-0 is reporting that server-0 is the master and that it is up.
Anything else we need to know:
Two possible solutions off the top of my head:

Have a helm config value to indicate a new cluster vs. an existing cluster so that a redis-ha statefulset pod rebooting in an existing cluster will never initialize itself as the master

Have a liveness check that eventually kills (and restarts) a statefulset pod that doesn't know about {quorum - 1}  other pods.

@aianus What chart version are you using?
Regardless, I can easily see how this can happen. I think your first solution would work fine for this specific issue but I worry it might open up other edge cases where manually initializing a master would be necessary. I'll try it out and see how it goes.
Honestly the livenesss check would be a good as well. I've been trying to think of a way to improve the checks since they are very basic as is.

I'm on 3.0.0

@aianus The above issues aside, going back over your description, it seems like you may want to switch your Rails pods to point to all the sentinels:

Our Rails pods never learn about the failover because they are configured to ask the Sentinel on Server 0 who the master is first; since Sentinel on Server 0 keeps replying successfully that it is the master, the Rails pods never bother to ask Sentinel 1 or Sentinel 2

You really shouldn't rely on any one Sentinel because even with no chart bugs, a single sentinel pod can go down/restart/update/etc shouldn't be the single point of failure for your app.  If you pass in all the sentinels the library you're using should simply attempt to contact in the case of a down Sentinel. Once this issue is fixed you could also simply point to the redis-ha service name and will pass through to an available endpoint.

However it seems like it prevents the pods from starting back up after shutting down and restarting all nodes.

Yes, but I think manual intervention in the case where you lose quorum is an acceptable limitation. Other distributed HA stores exhibit this limitation too (consul, etc.).

it seems like you may want to switch your Rails pods to point to all the sentinels:

Our Rails pods are pointed at all the sentinels.
However, the way the ruby client for redis is written, it will ask the sentinels one-by-one who the master is and stop once a single sentinel replies that it knows who the master is.
In the outage I described, sentinel 0 was asked first and replied successfully (albeit incorrectly) that it was the master. Therefore the Rails pods did not continue to iterate through the rest of the sentinels.
This matches the algorithm described in the official redis sentinel client guidelines: https://redis.io/topics/sentinel-clients

Yes, but I think manual intervention in the case where you lose quorum is an acceptable limitation. Other distributed HA stores exhibit this limitation too (consul, etc.).

I agree. Updating the probe seems to work out the best as it leaves the partitioned master in a CrashLoopBackoff until the pod is deleted/recreated.

Our Rails pods are pointed at all the sentinels.

Ahh my bad, I misunderstood the description then.
Another option (in addition to the probe) could be to setup the init script as the entry point script. This way when the probe fails and the container is restarted, the pod could attempt to find the other sentinels. Any thoughts on this @aianus ?

Another option (in addition to the probe) could be to setup the init script as the entry point script.

I'm worried that if you make it part of the entry point script instead, it could cause bugs where the sentinel container thinks it's in one cluster and the redis container thinks it's in another.
I think config value for existing vs. new cluster plus a liveness check is sufficient.
The liveness check alone sort of works, but it can cause bouts of downtime between server-0 booting and then getting terminated a little while later when it realizes nobody is connecting to it. In that in-between time it would still be advertising itself as the live master.
We already have alerting and monitoring for pods being down so I'm totally fine with manually intervening (in the morning!) if a pod goes down but the service stays up.
Let me know what you think, @ssalaues

I'm worried that if you make it part of the entry point script instead, it could cause bugs where the sentinel container thinks it's in one cluster and the redis container thinks it's in another.

Yeah I think you're right.

I think config value for existing vs. new cluster plus a liveness check is sufficient.

So I'm not 100% clear on the config value. Are you suggesting this should be like a value.yml option to disable/enable the init process?

Hmm ok I'll try something like this out and open a PR.

Bump to leave the discussion open until at least the PR is resolved.


False Positive Problem??

Userscript worked really well until it didnt, that's okay.  The userscript is off, I turn off any other youtube extensions and ABP to check if that's the problem. STILL have the message. Youtube is completely unusable now??? WHAT??

nvm. just had to restart the browser. didnt consider it first cause i had a ton of tabs open and i didnt want to close it all at once


Ingress snippet: replace "http" with "- http"

Ingress didn't worked for me as expected, resulting in nginx "404" error, changing http to - http solved the problem for me.

Hi @Persistent13 @markszente, I'm not very familiar with the ingress snippet but I see you folks have both contributed to it - would you mind taking a look at this PR please?  Thanks!

I am getting much sure that this PR may be incorrect cause this snippet is correct according to kubernetes sources, cause I am a beginner and got this issue while learning ingress cause I am learning it on headless server and accessing localhost is somewhat difficult.

@vital987 Thanks for closing the loop on that!  And thanks for taking the time to create the PR - we appreciate it.


Feat: History Management

This PR contains the following-

Authenticated users can watch a video which gets added to the history
Users can clear their watch history
Users can also delete a previously watched video from their watch history
If Users watch an previously watched video, history gets updated with the latest video shown at the top.

Nice UI Clean code and folder structure

Thank you for your review.

The overall logic and the ui looks amazingly good. Need to be merged.

Thank you for your review.


Fix a NullPointerException being thrown when an entity teleports through an end portal in the overworld

Fixes #106

Closing in favor of #109


Confirmation prompts

Some scripts can modify the user's environment without privilege escalation. Adding a confirmation prompt make unrecoverable, unintended changes less likely.
See https://github.com/ChrisTitusTech/linutil/pull/683#issuecomment-2379736118

/label rust

/label 'rust'

/label 'UI/UX'

lmao why is the actions bot adding labels unprompted???


Color modifications: hue, saturation, lightness and more

Added a way to apply color modifications to images. Most of modifications are done through TinyColor, which is a small open source color manipulation library. However, I have added few of my custom modifiers as well.
Instead of having image.hue(), image.saturate() etc. as separate methods, I decided to have just one image.color() method which handles multiple modifications at once:
var output = new Jimp('dice.png', function (err, image) {
  this.resize(600, Jimp.AUTO).color([
    { apply: 'hue', params: [ -90 ] },
    { apply: 'lighten', params: [ 50 ] },
    { apply: 'xor', params: [ '#06D' ] }
  ]).write(filePath.replace('.png', 'dice--out.png'));
});

Below is the list of available modifiers:

modifier
description

lighten {amount}
Lighten the color a given amount, from 0 to 100. Providing 100 will always return white (works through TinyColor)

brighten {amount}
Brighten the color a given amount, from 0 to 100 (works through TinyColor)

darken {amount}
Darken the color a given amount, from 0 to 100. Providing 100 will always return black (works through TinyColor)

desaturate {amount}
Desaturate the color a given amount, from 0 to 100. Providing 100 will is the same as calling greyscale (works through TinyColor)

saturate {amount}
Saturate the color a given amount, from 0 to 100 (works through TinyColor)

greyscale {amount}
Completely desaturates a color into greyscale (works through TinyColor)

spin {degree}
Spin the hue a given amount, from -360 to 360. Calling with 0, 360, or -360 will do nothing - since it sets the hue back to what it was before. (works through TinyColor)

hue {degree}
Alias for spin

mix {color, amount}
Mixes colors by their RGB component values. Amount is opacity of overlaying color

tint {amount}
Same as applying mix with white color

shade {amount}
Same as applying mix with black color

xor {color}
Treats the two colors as bitfields and applies an XOR operation to the red, green, and blue components

red {amount}
Modify Red component by a given amount

green {amount}
Modify Green component by a given amount

blue {amount}
Modify Blue component by a given amount

Sounds great! Loads of cool stuff there. I've pulled it in. Thanks a lot!
I might add a small number of short-cut methods like image.darken() etc. just because we can get them for free now!
Thanks so much! It's awesome.

Thanks for merging @oliver-moran
Regarding short-cut methods there is something to consider:
Running multiple modifiers with single image.color() call would be better for performance than running short-cuts separately (e.g. image.hue(60).darken(40)), because changes would happen inside single image.scan() in one go. As long as we make it clear on documentation, short-cut methods should be fine. A way to solve this would be to collect all modifiers and apply them together before image.write calls, but not sure if it is worth it

I agree on all points.
I suggest in the documentation that we document the main color method first. Then mention that shortcuts exist to perform these functions one at a time.

sounds good :+1:

:+1: this is great indeed. thanks

This is published on NPM. Thanks for the great work!


Fix .devcontainer

Why are these changes needed?
devcontainer needs an update on the dependencies to run the coverage and parallel test execution with pytest
Related issue number
#55
Checks

[ ] I've included any doc changes needed for https://autogen-ai.github.io/autogen/. See https://autogen-ai.github.io/autogen/docs/Contribute#documentation to build and test documentation locally.
[ ] I've added tests (if relevant) corresponding to the changes introduced in this PR.
[x] I've made sure all auto checks have passed.

Fixes #55


Small fixes in request samples

add the Content-Type header to all curl samples
updates the names of gradle tasks to start and stop Nakadi

It seems that my text editor decided to remove a lot of white space at the end of lines. Hopefully this isnt' a problem?

:shipit:

@lmontrieux  I don't think it's a problem. Actually, we should all configure our editors to do the same.


Extend enum text serialisation

Description
Extend the structured serialisation and the XML to/from SDObject serialisation to support enums which are not 4-byte's in size.
Before this change enums were assumed to be 4-bytes in size which led to incorrect serialisation from RDC to XML to RDC on chunks which contained non 4-byte enums.
Extended an existing StructuredFile serialisation test to include basic support for 1/2/8 byte enums (the test already covers 4 byte enums).
Added new SDObject -> XML -> SDObject round trip tests directly to xml_codecs.cpp to verify the XML serialisation changes.

https://github.com/baldurk/renderdoc/pull/2796


Add Eclipse IoT web page

Adding the Eclipse Foundation IoT top level project and working group page.

Thanks!


Fix small language mistakes in RigidBody2D documentation

Fixes issue #12225

Updated the commits based on feedback given by @cbscribe

Would you mind squashing the two commits together? We're not that atomic in our commits usually in Godot :) (and if I squash them manually the commit signing would be lost I guess).

Have squashed the commits now, @akien-mga


Add badge to chat header

See https://keybase.atlassian.net/browse/DESKTOP-3896

@keybase/react-hackers

The commits 0e9011185456...f5d552e575b9 introduce visual changes on linux. :mag_right: 1 new

Added: Chat_Header-Badged

The commits 0e9011185456...0f3a625e3152 introduce visual changes on linux. :mag_right: 1 new

Added: Chat_Header-Badged


Cannot add Zer0 card to deck

Hi,
I'm trying to add Zer0 to my deck, but the editor only shows the 0 selector.
No other cards are affected by this bug, at least in my collection.
Any thoughts?

Zer0 is a banned card from MWL 2.2 through the current MWL.  If you have one of those MWL versions selected, you will only see the 0 option.  If you choose casual play or an earlier MWL you will be able to add 0-3 copies to your deck.
Would you please double-check if that explains your issue and let me know if that explains it for you?

You're correct. Sorry for the inconvenient, keep up the good work!

It's no inconvenience at all!  Thanks for the report.  Happy running!


fix(txpool): proper nonce ordering in parked pools

Recap
Parked pools are pools with transactions that are parked waiting for external changes (e.g. basefee, ancestors, balance).
Problem Statement & Solution
The Ord trait requires total order and makes it impossible to reliably build an ordered list with transactions from different senders and/or different nonces. This PR introduces grouping transactions by sender and keeping in the ordered list only one transaction per sender at any given point.
Example
Previously, if we called pop_worst function on the parked pool with default ordering (by cost; see #1704), we would evict the transaction with the lowest transaction cost. It is wrong to consider it the worst transaction, since it might have a low nonce and get unlocked sooner than other higher cost transactions in the parked pool.
The behavior of pop_worst function for parked pools was changed to evict the transaction with the highest nonce for the sender whose lowest nonce transaction has the worst cost.
cc @mattsse open for discussion

Codecov Report

Merging #1705 (25adf35) into main (ad5f9aa) will decrease coverage by 55.07%.
The diff coverage is 46.15%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #1705       +/-   ##
===========================================
- Coverage   73.87%   18.81%   -55.07%
===========================================
  Files         386      388        +2
  Lines       46354    46438       +84
===========================================
- Hits        34243     8735    -25508
- Misses      12111    37703    +25592

Flag
Coverage Δ

integration-tests
18.81% <46.15%> (-2.34%)
:arrow_down:

unit-tests
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

crates/transaction-pool/src/pool/parked.rs
37.19% <46.15%> (-20.39%)
:arrow_down:

... and 284 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@rkrasiuk recommend we don't spend time on the txpool right now and reprioritize once we're past the sync controller

@mattsse is this still relevant? or should we close?

I'm not a fan of the nested sets, need to reevaluate this

closing this because not a fan of this design nested lists will break a lot of the underlying design assumptions


Cannot import name 'Softmax'

I am trying to use this package in a Jupiter notebook but I am getting the following error shown below:
ImportError                               Traceback (most recent call last)
<ipython-input-27-fc833231e89c> in <module>()
----> 1 import mtcnn
      2
      3 print(mtcnn.__version__)

/opt/conda/lib/python3.6/site-packages/mtcnn/__init__.py in <module>()
     24 # SOFTWARE.
     25
---> 26 from mtcnn.mtcnn import MTCNN
     27
     28

/opt/conda/lib/python3.6/site-packages/mtcnn/mtcnn.py in <module>()
     35
     36 from mtcnn.exceptions.invalid_image import InvalidImage
---> 37 from mtcnn.network.factory import NetworkFactory
     38
     39

/opt/conda/lib/python3.6/site-packages/mtcnn/network/factory.py in <module>()
     24 # SOFTWARE.
     25
---> 26 from keras.layers import Input, Dense, Conv2D, MaxPooling2D, PReLU, Flatten, Softmax
     27 from keras.models import Model
     28

ImportError: cannot import name 'Softmax'

What is your keras version, Softmax added in version 2.1.3. Try upgrading your keras version to 2.1.3 or higher

I had a same issue. (keras -2.4.3)
I changed "from keras.layers" to "from tensorflow.keras.layers" on factory.py file and the error is gone.


[DisplayServer] Add error messages and descriptions to callbacks.

Fixes https://github.com/godotengine/godot/issues/89022
Adds error messages to the system theme change, status indicator and drop files callbacks.

Poke for rebase.


Interpolate to a value higher than max value of XS

It is possible to interpolate to lower values than the XS range, but not higher? Is this correct?
const xs = [1, 2, 3, 4, 5];
const ys = [9, 3, 6, 2, 4];

// new a Spline object
const spline = new Spline(xs, ys);

// This returns is ok
console.log(spline.at(-100));
// This returns NaN
console.log(spline.at(5.5));

I think the algorithm should return the 1st ys value, if x <= the 1st xs
and the last of ys, if x >= the last xs (as lines 83-89 of Spline.ts).
if (x <= this.xs[0]) {
return this.ys[0];
}
if (x >= this.xs[this.xs.length - 1]) {
return this.ys[this.ys.length - 1];
}
If this is not the behavior, then there's a bug.
I will check...
On Thu, Sep 15, 2022 at 8:33 PM bergmorten @.***> wrote:

It is possible to interpolate to lower values than the XS range, but not
higher? Is this correct?
const xs = [1, 2, 3, 4, 5];
const ys = [9, 3, 6, 2, 4];
// new a Spline object
const spline = new Spline(xs, ys);
// This returns NaN
console.log(spline.at(5.5));
—
Reply to this email directly, view it on GitHub
https://github.com/starnutoditopo/typescript-cubic-spline/issues/2, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAK3JPKZZ46TUA7E3J7IDNLV6NTXHANCNFSM6AAAAAAQNU5UC4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Well... in principle, there's already a test case for that. It's at Spline.teast.ts, lines 82-92.
I added new tests explicitly for your case in Spline.teast.ts, lines 93-112.
The behavior looks correct, though.
I'd suggest using some other algorithm to predict values outside the xs range, anyway.

Well... in principle, there's already a test case for that. It's at
Spline.teast.ts, lines 82-92.
I added new tests explicitly for your case in Spline.teast.ts, lines 93-112.
The behavior looks correct, though.
I'd suggest using some other algorithm to predict values outside the xs
range, anyway.
On Sat, Sep 17, 2022 at 6:05 PM Starnuto di topo @.***>
wrote:

I think the algorithm should return the 1st ys value, if x <= the 1st xs
and the last of ys, if x >= the last xs (as lines 83-89 of Spline.ts).
if (x <= this.xs[0]) {
return this.ys[0];
}
if (x >= this.xs[this.xs.length - 1]) {
return this.ys[this.ys.length - 1];
}
If this is not the behavior, then there's a bug.
I will check...
On Thu, Sep 15, 2022 at 8:33 PM bergmorten @.***>
wrote:

It is possible to interpolate to lower values than the XS range, but not
higher? Is this correct?
const xs = [1, 2, 3, 4, 5];
const ys = [9, 3, 6, 2, 4];
// new a Spline object
const spline = new Spline(xs, ys);
// This returns NaN
console.log(spline.at(5.5));
—
Reply to this email directly, view it on GitHub
https://github.com/starnutoditopo/typescript-cubic-spline/issues/2, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAK3JPKZZ46TUA7E3J7IDNLV6NTXHANCNFSM6AAAAAAQNU5UC4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


tcal (from gcal package): gcal: No such file or directory

Describe the bug
Running tcal fails.
Steps To Reproduce

Install gcal
Run tcal
Error:

tcal: error during program execution of `gcal'
gcal: No such file or directory

Expected behavior
No error, it should work.
gcal works fine:
      July 2024
 Su Mo Tu We Th Fr Sa
     1  2  3  4  5  6
  7  8  9 10 11 12 13
 14 15 16 17 18 19 20
 21 22 23 24 25 26 27
 28 29 30 31

Screenshots
n/a
Additional context
n/a
Notify maintainers
@romildo

Metadata
Built on commit 2527c6de5cf5d0131cdb15312576999dd1c09a5c
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
output here

Add a :+1: reaction to issues you find important.

It works for me on unstable.
The code documentation says:

The program first tries to use the `gcal' executable which is specified in the environment variable $GCALPROG if it is set, otherwise it will be searched using the $PATH environment variable.

Sor you can make sure that the gcal directory is in $PATH or it is set in $GCALPROG.
If you installed with environment.systemPackages in the system configuration, it should be in $PATH.

Thanks, I was inexact in how I originally described it - I was specifically using it via nix-shell.
I missed the docs on this originally, but would it be reasonable if I tried to send a PR with a fallback? (i.e. it would respect PATH or GCALPROG first if set, but if not, it'd fall back to the gcal part of the same packaage)

Thanks, I was inexact in how I originally described it - I was specifically using it via nix-shell. I missed the docs on this originally, but would it be reasonable if I tried to send a PR with a fallback? (i.e. it would respect PATH or GCALPROG first if set, but if not, it'd fall back to the gcal part of the same package)

Yes, you can do a PR.


Bump multi-json dependency to newer version

This currently fails only the Ruby 2.2 path of the build matrix, bundler 2 needs 2.3 or higher. If we leave bundler at 1.17, it seems to fail the Ruby 2.3 & 2.4 paths, as it looks like the Travis image for those rubies come with bundler 2, and it doesn't want to downgrade. With Ruby 2.6 out, would you be up for adjusting the build matrix?


Replace Flowbite JS with Native Blazor Features

I propose replacing Flowbite JS with native Blazor features to improve the performance and maintainability of the project. The reasons for my proposal are:
Code Consistency: Using standard .NET C# to manage components instead of JavaScript will make the code more consistent and easier to maintain.
Maintainability: Flowbite JS requires additional maintenance and updates. By using native Blazor features, we can simplify the maintenance of the project.
The steps to replace Flowbite JS with native Blazor features are:
Identify the Flowbite JS components used in the project.
Replace each Flowbite JS component with its native Blazor equivalent.
Remove the Flowbite JS library from the project.
Please let me know if you have any questions or concerns regarding this proposal.

@babakhani
Yes it would be great. I am agree

https://github.com/fluentcms/FluentCMS/issues/373


!reputation reset

is there a way to have a !reputation reset that resets everyones rep

Will have to figure out how to do but sure why not ^^


Log rotation problem

Hi,
I have a problem with log rotation for application logs. I'm using following settings:
logging:
 level: INFO
 loggers:
  com.hortonworks.registry: INFO
 appenders:
   - type: file
     threshold: INFO
     logFormat: "%-6level [%d{yyyy-MM-dd HH:mm:ss.SSS}] [%t] %logger{5} - %X{code} %msg %n"
     currentLogFilename: /var/log/registry/registry.log
     archivedLogFilenamePattern: /var/log/registry/registry-%d{yyyy-MM-dd}-%i.log.gz
     archivedFileCount: 5
     maxFileSize: 128MB

Above settings will keep archived logs for last 5 days not last 5 files. If I have lot of queries I'm suffering from log flooding.
When I've tried to change the line to:  archivedLogFilenamePattern: /var/log/registry/registry-%i.log.gz it doesn't log at all.
Is there a way to tweak configuration in order to use both: archivedFileCount and maxFileSize ?

Hey,
I've tried exactly that and I don't have registry.log. It's not being created at all. I've cleared /var/log/registry/* but it hasn't helped as well.
Here is my new config(copy-pasted):
logging:

 # The default level of all loggers. Can be OFF, ERROR, WARN, INFO, DEBUG, TRACE, or ALL.
 level: INFO
 # Logger-specific levels.
 loggers:
  # Sets the level for 'com.example.app' to DEBUG.
  com.hortonworks.registry: INFO
 appenders:
   - type: file
     threshold: DEBUG
     logFormat: "%-6level [%d{yyyy-MM-dd HH:mm:ss.SSS}] [%t] %logger{5} - %X{code} %msg %n"
     currentLogFilename: /var/log/registry/registry.log
     archivedLogFilenamePattern: /var/log/registry/registry-%i.log.gz
     archivedFileCount: 3
     timeZone: UTC
     maxFileSize: 1MB

I've tried 0.5.1 from github release as well as 0.5.0 from HDF 3.1.2. They problem is the same for me.
thanks,
Marek

This issue doesn't exists in 0.5.4. Able to reproduce it in v0.5.1.

Great, thanks for info.
I will wait with the upgrade until a release which will also include fix for ISSUE-486.
Thanks very much for confirm it. I guess it has been fixed in the meanwhile.

I've checked 0.5.4 and can confirm this problem is solved there.
Closing the issue.


[LocationLayerPlugin] Navigation puck chop / disappears while navigating

Original ticket: https://github.com/mapbox/mapbox-navigation-android/issues/581
Greetings, I have noticed a bug related to the location layer plugin while in navigation. For now at least we have determined that this bug is on all Vodafone Smart Prime 6 devices (over one thousand devices).
At all times: the location layer does not animate fluidly on the map.
While in navigation: the location layer sometimes dissapears (it's still there if you zoom in or out) or gets left behind going off-screen even if the navigation camera animates and moves accordingly to the device's location.
I am posting a video recording of the bug, maybe it will be of more help visually in determining the problem.
Video found here

cc @tobrun @cammace

I got the same issue in locationLayerPlugin = '0.2.0' (snapshot version as well) and the issue only occurs when the camera tilt > 0. Do you have any suggestion?

+1 we're getting quite a few reports signaling this issue as well, any updates on this?

+1 i`m also having issues with this. any updates?

Thanks for reporting everyone. @tobrun is exploring new ways to handle the navigation puck, especially when tilted, in https://github.com/mapbox/mapbox-plugins-android/pull/220. I'm moving this to the 0.4.0 milestone since the PR hasn't been completed yet.

Hi guys, I'm sorry to insist but for my client's business this bug is currently critical due to the majority of the userbase having devices on which it reproduces.
Is there any possible workaround or quick fix to prevent this from happening until 0.4.0 is released ?

Interested about a quickfix also, we're having this issue on around ~4000 devices with a major impact on user experience.

We noticed that the bugs reproduce at the same time on different devices. Recently, with the dynamic camera update, whenever a zoom transition occurs they snap back into position immediately.
I uploaded 2 videos where you can see how the bug happens always in sync across devices.
Any updates on this issue ?
https://youtu.be/OAwmpHWj0gE
https://youtu.be/XOg8zyb0hH0

Hey everyone 👋 thank you for your patience here!  With the latest release of the LocationLayerPlugin Maps SDK 6.x is included with updates to help reduce the chop seen in this ticket or dropping frames on lower powered devices.  Please try it out and see if you're able to recreate on the devices that previously were causing these issues.  I'm going to close this ticket, let's open a new one if we find the issue persists.  Thanks!


Move from gorilla/mux

Is your feature request related to a problem? Please describe.
gorilla/mux toolkit is now archived https://github.com/gorilla#gorilla-toolkit and no longer maintained.
Describe the solution you'd like
We should move to another toolkit. We should talk about some possibilities.
To make some minor changes to the code, we should move to a toolkit based on the http package, like echo or gin-gonic.
Otherwise, we can also choose to switch to fasthttp with something like fiber.
Additional context
The gorilla toolkit remains available, so there is not hurry to do the change.
What do you prefer about the alternatives?

Maybe moving to fiber could be nice since it's supposed to be faster it may help increasing the proxy throughput, however we have to make sure it is feature complete for what we currently need (here a non-complete list):

path parameters
oas definition (for standalone mode)
transparent proxy out-of-the-box with response body access (without we may have to rethink how response policies are evaluated)
Middleware management

Gorilla has now been taken by a new team, shall we keep this issue open or try and stay with the lib?

Yes, I think we could close this issue at the moment.


Mux with MPRS causes operations after sharding_round_robin_dispatcher to run on the same worker

📚 The doc issue
This doesn't seem to be mentioned in the docs, but if you have two datapipes that use sharding_round_robin_dispatcher and then mux them together:

Any steps between sharding_round_robin_dispatcher and mux will take place on the same worker process.
Only the steps after the mux will take place on separate workers.

For example, with the below graph, the Mapper nodes in between the ShardingRoundRobinDispatcher nodes and Multiplexer run on the same worker process. The Mapper node after Multiplexer will run across multiple processes as they're fed data in a round-robin fashion.

My incorrect expectation was that the dispatching process would distribute data to worker processes immediately after sharding_round_robin_dispatch as usual, and then everything after mux would take place on either one or multiple worker processes.
Suggest a potential alternative/fix
The documentation for Multiplexer, ShardingRoundRobinDispatcher, and/or MultiProcessingReadingService should be updated to clarify what the intended behavior is here.

I think that's worth putting in the docs -- I just looked and couldn't find a mention of that limitation.

I am sorry that I think we currently don't support two ShardingRoundRobinDispatcher

This should potentially be taken into consideration as a usecase for https://github.com/pytorch/data/issues/1174


Changes in Homepage - page 3

increased jumbotron opacity and made text more readable
Changes are visible in the image below
You can also check my deployment

The changes that you asked for in the screenshot, that screenshot wasn't visible to me


Update dependencies

Updated dependencies (but not babel-core and babel-loader and such).
Updated code to handle deprecations and api changes.
Add example.env file for slightly easier setup.
Add compile_requirements command (wrapper for dep and prod pip-compiles)

Works on my machine :smile:

Tests not running :( out of index :(

https://github.com/webkom/committee-admissions/issues/161 @cherrybeans

Closed as fixed in other PRs in a more clear way. This branch was difficult to debug. (Turns out webpack update in frontend was the problem but for some reason I failed to see the fix on this branch).


Embedded modal not centered

I couldn't find the proper style css element or the inherited one to center the embed modal which seems to be misaligned from the timeline feed (the panel itself which is behind the modal, not the actual modal)
Is this an issue with panel width size?
Non-BirdUI theme using default Mastodon theme:

On mementomori.social:

On everythingbagel.social similar to mementomori.social:

Hmm, this definitely has some regression to it. See this.
I'm not sure why the width is like that, it most probably comes from the Mastodon core, this PR or after it. Have to investigate this furter when I have time. All help appreciated.

Ok, I don't think you are alone. Tangerine UI also have its issue as well, just sightly to the right.


Add show_diff set to false for files storing passwords or private keys

For security reason. Currently, when changes are made, puppet stores in reports and logs mcollective passwords and private keys.

thanks!


Question about adding CDATA section using pl.xml

I want to build an XML document with CDATA using pl.xml Lua module. CDATA section must start with "<![CDATA[" and ends with "]]". When I do something like this:
testcase_node:addtag(status)
testcase_node:text('<![CDATA[\n' .. 'XXXXXXXXXX' .. '\n]]>')

I get <failure><![CDATA[  XXXXXXXXXX ]]></failure> in a final XML document and '&lt' and '&gt' confused me. What is a right way to add CDATA section to a document?

@Tieske, could you please help?

I just took over maintenance, and haven't worked with the xml code before, so unfortunately I won't be of any help.
Your best shot might be to see if there is anything in the test files: https://github.com/Tieske/Penlight/blob/master/tests/test-xml.lua

I can say (as the original author) that this is a pretty basic XML implementation which doesn't cover CDATA. (You can see that it's trying to escape the CDATA section)

What does pl.xml provide that is not done better by other dedicated XML libraries? There are quite a few out there. Don't get me wrong I love Penlight and keep its toolbox handy in almost all my Lua projects — but I'm wording if this is not a case of trying to do too many things. If I need XML parsing why would I not want to use one of the various dedicated libraries. I see there are native ones, C based ones, fast ones, fuatureful ones, etc. What's the justification for this one?

@alerque good point. A common one seems to be expat; https://luarocks.org/modules/tomasguisasola/luaexpat
That said; it probably means we should either deprecate modules like this, or fix them...
In the latter case; PR welcome @ligurio !

I agree, that's where I was going with this. Unless there is some criteria met by this and only this implementation, I would think it would be better to mark it as deprecated with some recommendations based on needs (speed, features, pure Lua). That would save precious developer energy from trying to fix and develop something that is broken that is already better served by other tools. There are plenty of things Penlight does better (or only Penlight does at all!) that we can concentrate on without writing an XML handler (or a JSON) handler or whatever.
If there is any motion not to deprecate the xml module it would be interesting to hear the rational.

Yes, what seemed like a Good Idea at the time (simple pure Lua XML for basic uses) may not survive the test of time. I certainly find lua-expat full featured and it is definitely going to be faster than a pure Lua solution.  But I was thinking about CDATA - you can always put arbitrary stuff in a text element and it will be escaped properly.  CDATA seems to me more a convenience for human readability?  (Not that I have done any XML in years)

My inclination is (still) to completely deprecate the XML module, similar to the discussion about the Date module in #285.
@daurnimator I see you must use the XML module (guessing from #134). Do you have any input on this?

@daurnimator I see you must use the XML module (guessing from #134).

nope.

I'm with @alerque in this. Deprecate it imo.

Yes, it's an over-optimistic piece of code, trying to do a specialized task better handled elsewhere. Which I think is not the point of general purpose libraries


add the homomorphic comparison and sorting functions

complete comparison and sorting functions
The comparison funtion works as following：

Subtract LWE(a) and LWE(b), get LWE(a-b)
Then put LWE(a-b) into the FHEW bootstrapping procedure which output a cipher LWE(sign(a-b)).
Decrypt LWE(sign(a-b)) and get the comparsion result betwen a and b.

Sorting funcion is bubbling sorting algorithm using comparison function above.


Add UndoDropRange to Node interface

In cases where PrepareDropRange was successfully called on the src placement, but AddRange is failing on the dest placement, we should be able to undo the PDR quickly, rather than create a whole new dest placement. This was partially implemented previously as the untake RPC.

This is obsoleted by #12. Now there is no difference between serve and "untake", it's just activate/deactivate, and clients are expected to do that quickly. They can still take as long as they like to prepare and drop ranges.


Error displayed on home page

Going to download-directory.github.io shows:
⚠ Cannot set properties of null (setting 'value')
I'm grateful for this tool and use it often!

Thank you for the report!

Thanks for your quick fix!


Wip file fetcher

We've changed a lot on this branch and it is no longer really a file-fetcher branch, so it makes sense to merge it into master at this point. We are currently passing all specs and have a successful autobump pipeline on a test branch of p-runtime.

Wrong main branch, sorry.


BUG, DOC: signal: fix missing doc link, missing window functions, wrong needed arg info, and argument passing issue for get_window()

Reference issue
fix #13158
What does this implement/fix?
I fixed several issues of signal.get_window() function related codes.

fix missing and wrong window func docs
fix wrong flag settings that additional parameters are needed or not.
fix argument passing issue for window functions which has optional arguments.
fix test for above change

I forget to follow up this PR. I think we should close this PR onse, and split some PRs to fix #13158 from scratch.


[rcore] Provide FLAG_WINDOW_UNFOCUSED functionality for SDL backend

Please, before submitting a new issue verify and check:

[x] I tested it on latest raylib version from master branch
[x] I checked there is no similar issue already reported
[x] I checked the documentation on the wiki
[x] My code has no errors or misuse of raylib

Issue description
I find FLAG_WINDOW_UNFOCUSED to be quite helpful during development. Especially when I am tweaking a value to see its affect on the output,  FLAG_WINDOW_UNFOCUSED ensures that my editor doesn't lose focus every time I make a change. This helps me avoid unnecessary Alt+Tab or Escape presses.
This becomes even more helpful when I am following a tutorial using a web browser, otherwise I have to do Alt+Tab switching between three windows.
Environment
Platform: Desktop Linux
OS: Fedora 40 with Gnome on Wayland

Hello,
I believe this should be requested at SDL instead. AFAIK, at the moment, it doesn't have the mechanism to allow it. So, implementing it cross-platform from scratch would require quite a bit of engineering.
For development on Linux, the same effect is usually achievable with the help of the Window Manager. E.g.: on Fluxbox there's [FocusNewWindow] {bool} (doc). You'd have to check the documentation of the WM you're using to see if there's something similar available there.
Best regards.

@asdqwe As per my understanding this feature is out of raylib domain at the moment and should be reported to SDL. Closing the issue here.


Error when getting relationships

/{ct}/{id}/{relatedtype} works only one way.
Example I have ct pages and ct categories
i choose relationship when creating new page.
it works when i make request /pages/1/categories
but when i try to use it the other way:
categories/1pages/
i get the error:
Uncaught Exception: StorageException .
StorageException in Relations.php line 205:
Unable to load collection values. Ensure that EntityManager is set on Bolt\Storage\Collection\Relations

Have you explicitly defined both relationships in contenttypes.yml? As in, does the contenttype categories have a relation to pages (and vice versa)?

yes I have under categories:
relations:
pages:
multiple: true
label: Sisuleht
order: -id
under pages:
relations:
categories:
multiple: false
label: Kategooria
order: -id
I have a discovered when i delete relation under categories and add it there again, then it works...
But default it apperars under categories.

the following table structure

"id","from_contenttype","from_id","to_contenttype","to_id"
2,"sections",1,"pages",1
3,"pages",2,"sections",1
4,"pages",3,"sections",1

gives me this response in API
{
    "links": {
        "self": "http:\/\/localhost\/json\/sections\/1",
        "sections": {
            "href": "http:\/\/localhost\/json\/sections\/2\/sections",
            "meta": {
                "count": 1
            }
        },
        "pages": {
            "href": "http:\/\/localhost\/json\/sections\/3\/pages",
            "meta": {
                "count": 1
            }
        }
    },

Hi,
As of right now it seems as though Bolt is not getting the relationship properly, or I am using it incorrectly. The error lies with the code - https://github.com/xiaohutai/jsonapi/blob/master/src/Action/SingleAction.php#L49
When attempting to get related content, it calls the internal Bolt method getRelation() and only attempts to checks the to_contenttype. At this time there is no way to set bidirectional to true. This is the line in question - https://github.com/bolt/bolt/blob/c3ead6d48cc2431d72ae7f81947df7fa5fefa92b/src/Storage/Collection/Relations.php#L224
@rossriley  - Are the Bolt internals functioning correctly, or is there a problem with the my code? getRelation($contentType)->count() is always returning 0 on inverse relationships. Shouldn't bi-drecirectional relationships always default to true since all Bolt relationships are supposed to be  that? Here is what my relationship looks like in Bolt -


BelongsTo relation in BREAD form has different form name than the generated name in VoyagerBaseController

Version information

Laravel: v5.6.29
Voyager: v1.1.3
PHP: 7.1
Database: MySQL 5.7.16

Description
When I want to save a new entry of a model with a BelongsTo relationship, I get an SQL error that the foreign key is not included in the INSERT query and that no default value for the foreign key is set:
SQLSTATE[HY000]: General error: 1364 Field 'faq_category_id' doesn't have a default value (SQL: insert into `frequently_asked_questions` (`question`, `answer`, `updated_at`, `created_at`) values (ksdjkdj,
skdjlsjdjskl ;kjsdldksdjklsjdkljs
, 2018-07-30 18:36:38, 2018-07-30 18:36:38))
This is something that happened after I upgraded from Voyager 1.1.2 to 1.1.3. I did not change anything on my BREAD. I removed the relationship once and then reset it but the same occurs again.
I have been debugging this a bit and found out the following. When a model has a BelongsTo relationship, it appears my blade view generates a different name for the field in the BREAD form than the VoyagerBaseController expects. For example, in the BREAD form and hence also in the request, the field name for the foreign key is faq_category_id (which is also the column name in the database table). However the $row->field variable in the function insertUpdateData has the value frequently_asked_question_belongsto_faq_category_relationship. I am wondering where the difference comes from. Could anyone shed some light on this? Thank you very much!
Could it be related to the Voyager upgrade from 1.1.1 to 1.1.2 to 1.1.3 that my project went through? Do some new assets or views need to be published? Or some command run? I check the installation command but it does much more than what I need (e.g. run database migrations).

It appears the BREAD field of the foreign key should also have the visibility Add, Edit and Delete...
This is quite illogical/counterintuitive, since to me the visibility of the foreign key field means that the foreign key field would be shown as a text box (or whatever widget) in the create and edit forms of the BREAD.
Here is a screenshot of my BREAD configuration for a frequently_asked_questions model with relationship to a faq_category model:

If all visibilities of faq_category_id are disabled, you get an SQL insert error. This is easily reproducable. I just reinstalled laravel & voyager to test this


Input Special Characters & Emojis

Use case
Input validation testing, special characters and emojis
Proposal
Expanding on the - inputText command, allowing the use of special characters & emojis e.g. £ & 💰
Anything else?
No response

Is this #146 ?

Looks so! I'll close this.

Closing as issue raised here


Semyon1104/feature8 readme

fix #37

Please, do not include other branches here. Start from main branch, create new branch, add changes, commit


Fix : Tield map assets located in sub folders cannot be load.

First time to try to create pull request, thanks for Kenneth Pouncey's help.

Thanks @gdwneo.  It is kind of confusing at the beginning but great job.

Hey @gdwneo you should probably post this on the forum in the discussion you started on this.  Let them know that it was fixed and reference the PR.  Again thanks.

Got it, thanks for mentioning me.

@gdwneo this looks like it broke the tilemap tests could you take a look again and make sure that the change also works with our tests.

@kjpou1 because in the test solution the picture url in tmx file contains the subfolder but actually they are under the same folder, that tmx file cannot open in the tiled map editor. Btw today I found another issue is cannot load multiple assets in one tmx file, trying to fix that...

@kjpou1 sorry the root cause is the line 445 in CCTileMapInfo.cs is unneeded, remove it then everything works well.


ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()

Error shows up when executing
pix2tex --gui
Output:
Sandboxing disabled by user.
Path override failed for key base::DIR_APP_DICTIONARIES and path '/home/espacio/.conda/envs/machine-learning/bin/qtwebengine_dictionaries'
Path override failed for key base::DIR_APP_DICTIONARIES and path '/home/espacio/.conda/envs/machine-learning/lib/python3.12/site-packages/PyQt6/Qt6/libexec/qtwebengine_dictionaries'
Path override failed for key base::DIR_APP_DICTIONARIES and path '/home/espacio/.conda/envs/machine-learning/lib/python3.12/site-packages/PyQt6/Qt6/libexec/qtwebengine_dictionaries'
The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
Traceback (most recent call last):
File "/home/espacio/.conda/envs/machine-learning/lib/python3.12/site-packages/pix2tex/gui.py", line 227, in run
prediction = self.model(self.img)
^^^^^^^^^^^^^^^^^^^^
File "/home/espacio/.conda/envs/machine-learning/lib/python3.12/contextlib.py", line 81, in inner
return func(*args, **kwds)
^^^^^^^^^^^^^^^^^^^
File "/home/espacio/.conda/envs/machine-learning/lib/python3.12/site-packages/pix2tex/cli.py", line 115, in call
img = minmax_size(pad(img), self.args.max_dimensions, self.args.min_dimensions)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/espacio/.conda/envs/machine-learning/lib/python3.12/site-packages/pix2tex/cli.py", line 47, in minmax_size
img = img.resize(size.astype(int), Image.BILINEAR)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "/home/espacio/.conda/envs/machine-learning/lib/python3.12/site-packages/PIL/Image.py", line 2297, in resize
if self.size == size and box == (0, 0) + self.size:
^^^^^^^^^^^^^^^^^
ValueError: The truth value of an array with more than one element is ambiguous. Use a.any() or a.all()
The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
The cached device pixel ratio value was stale on window update.  Please file a QTBUG which explains how to reproduce.
OS:
Arch Linux + Hyprland (wayland)

Hi, I think you've got the package name wrong, the package name is pix2text and the package you've got wrong is pix2tex.


Prevent ANR during SDK initialization

Description
When initializing the OpenTelemetry Android SDK with disk buffering enabled, we discovered that synchronous disk space checks were causing ANRs in production. These checks occur during the creation of disk buffering exporters, specifically in DiskManager.getMaxFolderSize(), which makes blocking IPC calls through StorageManager.getAllocatableBytes() on the main thread. The issue manifests in the following ANR stacktrace:
android.os.BinderProxy.transact (BinderProxy.java:662)
android.os.storage.IStorageManager$Stub$Proxy.getAllocatableBytes (IStorageManager.java:2837)
android.os.storage.StorageManager.getAllocatableBytes (StorageManager.java:2414)
android.os.storage.StorageManager.getAllocatableBytes (StorageManager.java:2404)
io.opentelemetry.android.internal.services.CacheStorage.getAvailableSpace (CacheStorage.java:66)
io.opentelemetry.android.internal.services.CacheStorage.ensureCacheSpaceAvailable (CacheStorage.java:50)
io.opentelemetry.android.internal.features.persistence.DiskManager.getMaxFolderSize (DiskManager.kt:58)
io.opentelemetry.android.OpenTelemetryRumBuilder.createStorageConfiguration (OpenTelemetryRumBuilder.java:338)
io.opentelemetry.android.OpenTelemetryRumBuilder.build (OpenTelemetryRumBuilder.java:286)

Solution
To fix this we moved initialization to run on a background executor and buffer the data in memory until it completes.
The process works like this:

Initialize the SDK with BufferDelegatingExporter instances that can immediately accept telemetry data.
Move exporter initialization off the main thread.
Once async initialization completes, flush buffered signals to initialized exporters and delegate all future signals.

The primary goal of this solution is to be unobtrusive and prevent ANRs caused by initialization of disk exporters, while preventing signals from being dropped.
Testing
We have added unit tests to cover the buffering, delevation, and RUM building. We've also verified this with both disk enabled and disk disabled.

FYI we are working on getting the CLA signed.

@breedx-splk CLA signed

I've updated the PR with the feedback and everything except the logging has been addressed.
In addition the returned result will not be success any longer but rather resolve when the delegate is set.


Make Cheerio optional

Importing enzyme in an react native application results in this error at build time:
error: bundling failed: UnableToResolveError: Unable to resolve module `events` from `some/path/to/node_modules/enzyme/node_modules/htmlparser2/lib/Parser.js`: Module does not exist in the module map

This seems to be coming from the various cheerio imports in the enzyme package.  It would be great if we made cheerio optional or perhaps lazy load cheerio inside the various render functions that use it:
render() {
   const html = this.html();
   const cheerio = require('cheerio');
   return html === null ? cheerio() : cheerio.load('')(html);
}

I'm not sure what the issue would be; what is "the module map"? require should Just Work with everything that's on disk.

Apologies, I was able to fix this by npm install --save-dev events 👍

Always make sure npm ls exits zero, otherwise nothing can be expected to work :-)

Looks like I spoke too soon.  After installing events, buffer, and stream, (and making sure npm ls exists with zero), I am getting the following error:
o.prototype is undefined
Digging through the callstack,

Error is thrown here in the inherits module
inherits is called in parse5/lib/parser/parser_stream.js.  When the error is thrown, WritableStream is undefined
It's undefined because on this line require('stream') doesn't export a Writable object.  See stream

Unfortunately, this puts me back to my original problem where I can't load enzyme.  As a workaround, I can fork enzyme, remove calls to cheerio or stub it via babel-plugin-module-rewrite, but I'd rather not do that if possible.

I'm a bit confused; the problem you're describing is a dependency graph problem, which either 100% or 0% of enzyme users would be running into.
What version of node and npm are you using? Is this only occurring when browserifying or webpacking enzyme? Do your tests pass in node itself, which is the primary use case of enzyme?

Apologies for the confusion.  We're building an integration test framework that runs as a react-native application on an actual device (non-node environment).  For this, we're using mocha and enzyme with our custom enzyme adapter, and hence why we are importing enzyme inside a react-native application.  It works great, as long as I remove cheerio imports in enzyme.
This is obviously not an intended use case for enzyme, but it would be great if we can come to some sort of solution.  We do have a workaround (see above), but it requires forking enzyme, which we'd like to avoid.
To answer your questions:

What version of node and npm are you using?

node: 8.6.0
npm: 5.3.0

Is this only occurring when browserifying or webpacking enzyme

This occurs only when used with the react native packager.

Do your tests pass in node itself

If:

We run in node instead of on an actual device
Stub out native dependencies
Use enzyme-adapter-react-16 instead of our custom adapter

Then, yes, it does run 👍
Again though, our intended goal isn't to run on node, but on an actual device.

Since you can stub out native dependencies, can you not stub out cheerio in the RNP, and simply not use render?

Good point.  I did initially try stubbing cheerio using the stubbing mechanism used in react-native-mock, but it turns out react-native-mock is a run-time mock that relies on the require cache being exposed.  Unfortunately, the error thrown when importing enzyme in RN is a build-time issue.  The require cache isn't exposed either.
However, I recently stumbled upon https://github.com/philikon/ReactNativify, which aims to address this exact issue.  It turns out babel-plugin-rewrite-require works:
In .babelrc:
{
  "plugins": [
    ["babel-plugin-rewrite-require", {
      "aliases": {
        "cheerio": "my-framework/cheerio-stub"
      }
    }]
  ]
}

Where my-framework/cheerio-stub is just module.exports = {};
This is much better than having to fork enzyme 👍 .   If there was a browserified cheerio, we could use that instead as well.
It would still be great if cheerio was optional so that all consumers of our framework didn't need to install this plugin + modify their .babelrc, but this will be sufficient for us.  Actually now that I think about it, I think what I'm really requesting for is for enzyme to support browserify, webpack, and RN's metro bundler. 😄
Thanks for your help @ljharb!


Fix incorrect application of factors in raster.resample

Here is my new pull request.

Looks good, thanks!


br: storage cannot be stopped or started successfully during the restoration process

After restoration, the message reads the process is successful. But when I check the status of the Nebula Graph services, the storage is not started.

Hi, can you give some more detailed information such as the storage logs.


General Grievance: Watch smhdiamondclean.com.au

General Grievance requests the watch of the watch_keyword smhdiamondclean\.com\.au. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

smhdiamondclean\.com\.au has been seen in 0 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Unable to tap the drawn text in Flutter driver test.

Hi Team,
   1. I have drawn some text on the canvas and trying to tap on the text in flutter text but it doesn't work
   2. I have implemented accessibility using semanticsBuilder of custom painter
   3. And I have tried to find the element by using find.text('string') and find.bySemanticsLabel('Label') and the element is not null, but the tapping doesn't occur.

The error we got is following by:
VMServiceFlutterDriver: tap message is taking a long time to complete...
We have prepared the sample for the same. Please find the sample from the following link.
Sample link:
flutter_app_testbed.zip
Regards,
Indumathi R

It doesn't tap on drawn widgets that are implemented using Paint. Not sure if Flutter driver supports it though.

flutter doctor -v
Flutter 1.20.2 • channel stable • https://github.com/flutter/flutter.git
Framework • revision bbfbf1770c (15 hours ago) • 2020-08-13 08:33:09 -0700
Engine • revision 9d5b21729f
Tools • Dart 2.9.1

Running flutter doctor...
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 1.20.2, on Mac OS X 10.15.2 19C57, locale en-US)
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    ✗ Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit https://flutter.dev/docs/get-started/install/macos#android-setup for detailed instructions.
[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
[✓] Android Studio (version 3.6)
[✓] Connected device (1 available)

! Doctor found issues in 1 category.

FlutterDriver team, can I please get an update on this?
This will help raise quality of our software.
Thanks
Ajay

Hi Team,
Any update on this?
Regards,
Indumathi R

Hi Team,
Any update on this?
Regards,
Indumathi R

Stuff that you draw on a canvas is basically opaque to the testing framework. You can, however, find the CustomPainter and use tapAt to tap at the desired offset within that painter.
https://master-api.flutter.dev/flutter/flutter_test/WidgetController/tapAt.html


Create two unit tests for the 'h3' cli app

Not adding any extra functionality to the app until we have tests for it. Wanted to put this approach in front of you guys to see what you think.
I can't figure out how to do coverage tests on the CLI app, but I don't think that's too big of a problem?

Coverage remained the same at 98.2% when pulling 36d53ee2208e109ff2c1826e9a1057b79e996e55 on dfellis:master into cd470158dc499e9bd5e6c6ec1a7e9a2373bfb1f3 on uber:master.

Not a huge fan of this approach - seems like it will bloat the CMakeLists.txt file, and I don't like the idea that we're expanding the purpose of that file beyond build tasks.
Other options:

Put all tests in a shell script
Put all input/output in some text file, and make a test via CMake that reads the file, runs commands from input, and asserts output
Use a unit testing framework in other language, e.g. Node or Python

@nrabinowitz Another option would be to define the tests in a separate CMake file but still in that framework.

@nrabinowitz Another option would be to define the tests in a separate CMake file but still in that framework.

I personally like this compromise. The CMakeLists file does already handle a lot of stuff, and this would help us organize not just the test logic but other things like the fuzzers.

@nrabinowitz Another option would be to define the tests in a separate CMake file but still in that framework.

I personally like this compromise. The CMakeLists file does already handle a lot of stuff, and this would help us organize not just the test logic but other things like the fuzzers.

That seems okay by me. The main issue for me is just that the rest of the CMake file doesn't have actual data or need the kind of review that test cases do, whereas this does. Separating it, ideally with a header comment, should be fine (and I agree that other parts could be separated out as well).


file arranged

Files arranged please review
Issue #50

@harshitjain156 those r some node.cl errors of the github bot no need to worry


Added isInKeychain

Added a new method called isInKeychain(key: String) which verifies whether the provided key is present in the keychain or not.
Some simple use cases for this could be, to execute a certain action if the key is present/absent or to prompt the user before overwriting the existing key.

Thanks for the commit, but I don't think this method is necessary, since it is just as easy to check getData("key") != nil in the code. Sorry :)


raftstore: Recurring the tilt between apply threads

What have you changed? (mandatory)
Add a test for recurring the tilt between apply threads.
What are the type of changes? (mandatory)
The currently defined types are listed below, please pick one of the types for this PR by removing the others:

Engineering (engineering change which doesn't change any feature or fix any issue)

How has this PR been tested? (mandatory)
run command:  cargo test test_apply_tilt -- --nocapture
Does this PR affect documentation (docs) or release note? (mandatory)
no
Does this PR affect tidb-ansible update? (mandatory)
no

TODO ： Found a little problem


Make eventFromException handle recursively wrapped errors

Currently, client.eventFromException only calls the Cause method on the exception once.
Using github.com/pkg/errors, if we use the errors.Wrap function to wrap our error (let's say of type TestError), this gives us the following chain:
errors.WithStack -> errors.WithMessage -> TestError
and since the Cause method returns the direct cause, not the underlying one, we end up with type errors.WithMessage being reported to Sentry. (Instead of TestError.)
I believe the underlying cause should be reported to sentry, i.e. eventFromException should determine cause in the same way github.com/pingcap/errors and github.com/pkg/errors do (both call the Cause method repeatedly, the first recursively, the second iteratively).
The proposed change of this part:
for exception != nil {
	if ex, ok := exception.(interface{ Cause() error }); ok {
		exception = ex.Cause()
	} else {
		break
	}
}
cause := exception

Let me know what you think and whether I can open a PR to fix this :)

Hi @inesmersak! Thanks for the report, I acknowledge it.
A solution needs to take into account:

Careful unwrapping / cause traversal for compatibility with #137.
Careful handling of nil values (see #160).
Avoid infinite loop.
We can do better than github.com/pingcap/errors.Cause and github.com/pkg/errors.Cause because instead of reporting a single error we can report all errors in the chain.

Pending a clarification on the Sentry API for how best to implement the last point. There are at least two possibilities:

Multiple exceptions (errors): https://github.com/getsentry/relay/blob/master/relay-general/src/protocol/event.rs#L320-L324
Multiple values in single exception (error): https://github.com/getsentry/relay/blob/master/relay-general/src/protocol/exception.rs#L4-L41

I'm reaching out for help from other folks in the team to decide on the above.
Since there is some ambiguity here, please let's flesh out the details first before working on a PR.


4 add support for kafka

Thanks for you review @JulienPeloton , I plan to add a high level tool to help running the whole stack. So I propose not to document the kafka integration for now in the README, because it should become simpler in the short term.


Custom ingress labels (Example: for external-dns)

Added an option to enable ingress labels.

Hello @gnom4ik,
Thanks for your pull request! A Core Committer will review your pull request soon. For code contributions, you can learn more about the review process here.

This PR has been automatically labelled "stale" because it hasn't had recent activity.
A core team member will check in on the status of the PR to help with questions.
Thank you for your contribution!

Hi there! any updates?


There's currently noway to identify a Cython Coroutine Function.

Python's asyncio.coroutines uses an object (_is_coroutine) to tag objects as coroutine functions.
On this diff, we read _is_coroutine and use it to tag Cython functions and methods where appropriate.
I tried to keep all changes inside a transform, that way it becomes simple to remove/replace with the protocol once CPython folks decide on one. I'm not sure about the pipeline order, so will gladly move if needed.
It also includes tests to make sure asyncio.iscoroutinefunction() works as expected. Please let me know if I need to move those to a specific place.
This doesn't fix inspect.iscouroutinefunction() (which uses a flag that can trigger
undesirable behavior for cython functions).
Closes #2273

Yeah, I wasn't sure about the transform thing either. The idea was just to self-contain due to the comments mentioning moving to a protocol once cpython establishes one.
First time working with cython, but I'll try to change it to C and address all the comments. Thanks for the input. :)

COVID started and this flew completely under my radar, sorry. Took sometime to recover context now. I reverted the tree transform, and tried to use the C-API now. Doing a preliminary submission just to check if that's what you wanted @scoder.
I decided to create my own flags, instead of using the "_is_coroutine" object, because that one will eventually go away when old-style coroutines are fully removed (the object is theoretically only used by the @coroutine based ones).
With my own flag, I can patch the inspect module directly, and cover more usecases.
I still don't fully grasp when the patching for inspect and asyncio trigger, but I'll try to figure it out. I can get it to trigger on local tests, but not for the ones I included.

Okay... I finally understood how patching works, and why it wouldn't work here (it would only work for imports inside cythonized files, but not on regular python files just importing cython modules). Now I finally realized why the suggestion was to just add the _is_coroutine object while we wait for the protocol to be defined.
On the diff, I already added the flags for Async Generators too, so in the future we just need to add the code for the protocol.
As suggested, I'm using a getter to only import the object when needed and requested.

As for caching, I thought about it too, but couldn't figure out where to store the reference. Would putting this on globals work?

As for caching, I thought about it too, but couldn't figure out where to store the reference.

We could store it as a new struct field in CyFunction and initialise it at first use. That's a tiny bit wasteful (one reference per function instance), but seems good enough to me for now. It needs to be added to the traverse, clear and dealloc functions as well then, since it's a Python object field.

Sounds good to me. Storing on CyFunction means it's a potential import flow for each coroutine function (which is better than one for each access of _is_coroutine). Is there someplace I could store the first import and just read the reference for other functions? That would be less wasteful. I don't know cython enough if such a place exists. :)

If we use a global, then there's no use in storing the reference in the function. :)
Let's keep it in the function for now, and see if it's good enough.

@scoder, addressed the comments... FYI, thanks for the review and comments. Learning a lot.

Personally I'd rather put the cached asyncio.coroutines._is_coroutine somewhere like the CyFunction type-object dictionary rather than a per-instance attribute. However, I'm not sure if it'd be possible for users to modify it there (it's bad if they could!).
It isn't a strong preference though (especially since the current version looks like it's working)

@da-woods, where can I access the CyFunction type-object dictionary? I can do a quick change.

@da-woods, where can I access the CyFunction type-object dictionary? I can do a quick change.

It'll be something close to ((PyTypeObject*)Py_TYPE(op))->tp_dict. I think you may have to call PyType_Modified on the type afterwards.
(For reference this is an example of somewhere else Cython sets the tp_dict for a type.)
There may be something else that I'm missing that makes it a bad idea though.

put the cached asyncio.coroutines._is_coroutine somewhere like the CyFunction type-object dictionary rather than a per-instance attribute.

That would also work. Not sure which is really better here. We already pay a couple of indirections to get to this code at all, so a couple more probably won't make a visible difference. I don't care about users changing that value, because they can also change asyncio.coroutines._is_coroutine quite easily.
It's yet to be proven that caching the value is necessary at all, though. Looking up tp_dict requires some fallback code for non-CPython's, and I think less code is better here. Maybe no code at all is the perfect solution already, we didn't validate that.

Yeah, if this will add more code, and cause problems for other implementations, I suppose it's worth paying the price per function.

Hey folks... Is anything else left for me to do here?

Looks good to me. Thanks!

Would it be possible to backport this to 0.29. Happy to make a PR if that would be helpful

Would it be possible to backport this to 0.29.

Hmm. Doesn't really feel like an 0.29 feature to me. And there need to be reasons for users to switch to 3.0 as well. :)

Hi, I was testing out this patch for some application. I am using the Master branch code. While testing I was faced with "Key Error" after a fixed number of asyncio.iscoroutinefunction() calls on distinct coroutine functions. The following minimal code example can be used to reproduce the above issue:
import asyncio

async def cb1(msg):
   print("cb1")
async def cb2(msg):
   print("cb2")
async def cb3(msg):
   print("cb3")
async def cb4(msg):
   print("cb4")
async def cb5(msg):
   print("cb5")
async def cb6(msg):
   print("cb6")
async def cb7(msg):
   print("cb7")
async def cb8(msg):
   print("cb8")
async def cb9(msg):
   print("cb9")
async def cb10(msg):
   print("cb10")
async def cb11(msg):
   print("cb11")
async def cb12(msg):
   print("cb12")
async def cb13(msg):
   print("cb13")
async def cb14(msg):
   print("cb14")

def main():
    #asyncio.iscoroutinefunction(cb1)
    #asyncio.iscoroutinefunction(cb1)
    #asyncio.iscoroutinefunction(cb1)
    #asyncio.iscoroutinefunction(cb1)
    asyncio.iscoroutinefunction(cb1)
    asyncio.iscoroutinefunction(cb2)
    asyncio.iscoroutinefunction(cb3)
    asyncio.iscoroutinefunction(cb4)
    asyncio.iscoroutinefunction(cb5)
    asyncio.iscoroutinefunction(cb6)
    asyncio.iscoroutinefunction(cb7)
    asyncio.iscoroutinefunction(cb8)
    asyncio.iscoroutinefunction(cb9)
    asyncio.iscoroutinefunction(cb10)
    asyncio.iscoroutinefunction(cb11)
    asyncio.iscoroutinefunction(cb12)

    asyncio.iscoroutinefunction(cb13)

if __name__ == '__main__':
    main()

The compilation was done as follows on Debian Buster with Python 3.7 and gcc (Debian 8.3.0-6) 8.3.0:
cython -3 cython_bug.py --embed && gcc -ggdb -Os -I /usr/include/python3.7m/ -o cython_bug.o cython_bug.c -lpython3.7m -lpthread -lm -lutil -ldl && ./cython_bug.o

The number of checks performed on distinct coroutine functions is 13 which causes the crash. If the last line asyncio.iscoroutinefunction(cb13) is commented out, there is no error.
Further, if the last line is commented out and the first few commented checks are uncommented, I'm faced with Seg faults sometimes.
Please review the same and suggest what could have gone wrong.

To simplify tracking, could you please file this as an issue, @HVP1621?

To simplify tracking, could you please file this as an issue, @HVP1621?

Done. Tracking here: https://github.com/cython/cython/issues/4182

Great thank you 😄


parse_example is awfully slow

@skearnes
you have indicated in this post of yours https://github.com/tensorflow/tensorflow/issues/390 way back in 2015 that parse_example is about 30 times faster than parse_single_example.
I have tried different options to modify my simple training script which only prints about 100000 tfrecords batched in 1000 and just does a print of feature and label after session.run(feature, label). Feature is a sparseTensor BTW.
Can you please put a test sample which proved that parse_example was that fast. parse_single_example was taking ~320 secs, now parse_example takes ~240 secs.
@Admin, please do not close this issue and refer to stackoverflow, as I don't think this is something to do with API usage or wrong parameters.
This is to do with the performance of queues (enqueue, dequeue) & threads

It's possible there was performance regression in parse_example
For this to get resource there needs to be at minimum a reproducible example, and ideally, some investigation of the cause of the slowness

It takes 240 secs, how much do you expect it to take? Is it possible that it's as as fast as it can be? Similar discussion with parse_csv slow
https://github.com/tensorflow/tensorflow/issues/11713

gperftools profile to show where time is spent is useful, like here
https://github.com/tensorflow/tensorflow/issues/3009#issuecomment-228867287

just to add more information to debug, here is my lscpu
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                4
On-line CPU(s) list:   0-3
Thread(s) per core:    1
Core(s) per socket:    2
Socket(s):             2
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 79
Model name:            Intel(R) Xeon(R) CPU E5-2683 v4 @ 2.10GHz
Stepping:              1
CPU MHz:               2095.148
BogoMIPS:              4190.29
Hypervisor vendor:     VMware
Virtualization type:   full
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              40960K
NUMA node0 CPU(s):     0-3

Each TFRecord is a sparse structure of feature shape  1000 222215 viz. basically I am making batches of 1000 features. TFRecordWriter works faster as compared to burning a 1000 examples of (1x222215)  . My labels are on one-hot with 58565 labels and 1000 rows again to match 1000 labels.
Using SparseFeature and parse_example is faster compared to using parse_single_example and/or VarLenFeature. But not significantly fast. (I didn't do decode_csv, it would have been worse anyway.)
With this structure, I am able to train 400000 examples trained in batches of 1000 (each TFRecord) and 5 epochs in 861-900 secs. Is this the best I can get. I am ONLY printing the tensors. No matmuls, no optimizers.

That was the story with 1.2.1. I thought I should upgrade to 1.3 and now I did a bazel build hoping for better. Unfortunately, it's got worse. Same run above, now takes 1184 secs.
Does Tensorflow require some minimum hardware to show it's muscles.

I think the input pipeline is getting slower. I am sure if I do away with TFRecords and queues and feed the sparse matrix directly, processing using scipy or some other python library, it's been running faster earlier, though it was single threaded and may not be using all the logical cores though.

There are many ways to get slow performance that is not a bug in TensorFlow (ie, wrong choice of threads, wrong data format, wrong design of pipeline etc). Stackoverflow can help with that with tag "tensorflow". It could be a bug in parse_example op. If you think it's a bug in parse_example, it would help with extra details I mentioned above (reproducible example + performance profile)

I reduced the number of labels in the training examples from about 70000, which is the super set to about 1500 which is the number labels that's in the training set. Now the dry run, (WITHOUT matmuls, cost optimizers etc.) runs very fast. About 0.5 mn training examples pipelined and get enqueued/dequeued in about 17 secs and 5 epochs. That's about 1 million training examples in about 8-9 secs. I am not sure how & why this correlates internally, the features are SparseFeature and label is FixedLenFeature.
Now the big question, if I have to train with all the 70000 labels, will the performance again take a beating.

Update: I think the slowness has nothing to do with the number of labels. I removed one-hot dense vector and made it one-hot sparse and it's as fast as otherwise viz., its just a fixedLenFeature with the batch of numbers.
What helped me is to write a batch of say 1000 rows into tfrecords and read it as a single_example (though I know its a sparse-batch example) and treat it accordingly. Writing a batch of examples into tfrecords is definitely faster than writing each feature row/matrix, vector.
But parse_example is nowhere faster than parse_single_example as claimed here #390.

@balaji-in-git ,I think parse_example is much faster than parse_single_example. in my case , speed change from 25000 sample/second to 32000 sample/second

@balaji-in-git, can you provide code to verify this regression? Something that used to be fast but is now slow?

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

Nagging Awaiting Response: It has been 14 days with no activityand the awaiting response label was assigned. Is this still an issue?

It has been 14 days with no activity and the awaiting response label was assigned. Is this still an issue?

Closing due to lack of activity but please reopen if there's new information.


database启动失败

Error: failed to start container "mysql": Error response from daemon: OCI runtime create failed: container_linux.go:380: starting container process caused: process_linux.go:545: container init caused: rootfs_linux.go:76: mounting "/var/lib/kubelet/pods/c5fcbc47-810e-4e1b-8423-35c41840151c/volumes/kubernetes.io~configmap/database-config" to rootfs at "/etc/my.cnf" caused: mount through procfd: not a directory: unknown: Are you trying to mount a directory onto a file (or vice-versa)? Check if the specified host path exists and is the expected type
database:
  type: internal
  internal:
    serviceAccountName: ""
    automountServiceAccountToken: false
    image:
      repository: docker.io/library/mysql
      tag: 5.7
    username: "root"
    password: "1234"
    shmSizeLimit: 512Mi
    nodeSelector: {}
    resources: {}
    tolerations: []
    affinity: {}
    priorityClassName:
    initContainer:
      migrator: {}
      permissions: {}
  maxIdleConns: 100
  maxOpenConns: 900
  podAnnotations: {}

https://github.com/flashcatcloud/n9e-helm/pull/60


Make the first EB 5.8 release candidate 5.7 compatible for rolling upgrade support.54

This issue is imported from pivotal - Originaly created at Aug 23, 2018 by Michiel Kodde
EB 5.8 drops several columns from the entity metadata database schema (sso_provider_roles_eb5) this is troublesome when performing a rolling upgrade from 5.7 to 5.8.
The running 5.7 nodes should not crash down due to schema changes required for EB 5.8. This is a complex problem as the EB 5.8 schema changes require a Manage Metadata push (filling a new column with detailed consent settings and #158145547 ). This only makes this challenge more complex as this new metadata should be pushed into the 5.7 and 5.8 schemas.
Some solutions have been discussed:

Leave the dropped columns in place until the rollover has been completed and verified to work correctly. And somehow sync the newly pushed metadata to all of the correct columns.
Temporarily provide two versions of the sso_provider_roles_eb5 and ensure the MetadataPushAssembler fills both of the tables with the correct data.
Upgrade all nodes to 5.8 at the same time and accept some downtime if a rollback is required (probably not an option!)

This ticket will be discussed at the next sprint planning/refinement session that's scheduled at the beginning of September 2018

https://github.com/OpenConext/OpenConext-engineblock/pull/593 (bstrooband - Sep 7, 2018)

I've created a PR with a proposal. Only the removal of the attribute_aggregation_required field should be an issue. The creation of the requesterid_required field shouldn't be a problem at all, if the data is only pushed to the 5.8 EB instance.
https://github.com/OpenConext/OpenConext-engineblock/pull/540 requesterid_required
https://github.com/OpenConext/OpenConext-engineblock/pull/572 attribute_aggregation_required (bstrooband - Sep 7, 2018)

@michielkodde I\'ve added also support for the `consent_settings` BC changes. Now I have two commits, one for 5.8.3 and one for the cleanup in 5.8.4.  I did ask @thijskh how we should handle the faulty 5.8<5.8.3 releases and it should be sufficient to only add documentation about the changes We should leave the old releases.

If you would like to test it you could add the first commit at the end of a new 5.8.3 release and the latter in a new 5.8.4 release. If you think this should work I'll add two separate PR's. (bstrooband - Sep 10, 2018)

I've tested the steps but I wasn't able to test the metadata:coin:requesterid_required with Manage. When I mocked the push data from manage and pushed it to my local dev EB, it proved it was working. But this is something I couldn't test myself.
I did understand from @pmeulen that the metadata:coin:requesterid_required should be added in Manage. (bstrooband - Sep 12, 2018)

If you would like to go from <5.8.3 to 5.8.3 you will encounter a bc change in a migration. This is because a column was renamed and thus break the rolling updates. In order to fix this you could revert the<PHONE_NUMBER>5453 migration before upgrading.
https://github.com/OpenConext/OpenConext-engineblock/blob/d3737ab112ee602f746ed2c584ed7569a78cfa47/database/DoctrineMigrations/Version20180724175453.php (bstrooband - Sep 13, 2018)