Integrate with Google Play

Set Up Google Play Services
https://developers.google.com/android/guides/setup
Get Started with Play Games Services for Android
https://developers.google.com/games/services/android/quickstart
Setting Up Google Play Games Services
https://developers.google.com/games/services/console/enabling
Configuring Google Play Games Services
https://developers.google.com/games/services/console/configuring
Testing and Publishing Game Changes
https://developers.google.com/games/services/console/testpub
Public API
public void init()
public String getPlayerID()
public String getPlayerName()
public void setPopupView(final int resourceID)
public void signOut()
public void showLeaderboard()
public void updateLeaderboard(long score)


Fluentd Kafka buffered output plugin credential encryption support

Check CONTRIBUTING guideline first and here is the list to help us investigate the problem.
Is your feature request related to a problem? Please describe.
Current FluentD Kafka buffered output plugin required credentials to be stored in plain text on the disk which pose security risk.
Describe the solution you'd like
We would like to have some encryption mechanism for the credentials to be stored in encrypted form and be decrypted on the fly.
Describe alternatives you've considered
Credentials being fetched from some vault using CURL request.

This is https://github.com/fluent/fluent-plugin-kafka/ issue, right?
could you re-created this issue at fluent-plugin-kafka repo?

if you have a question, please create an issue at https://github.com/fluent/fluent-plugin-kafka/ .
thanks for your corporation


pod failure duration not work

Bug Report
What version of Kubernetes are you using?

v1.12.10
What did you do?

kubectl apply -f pod-failure.yaml
pod-failure.yaml as below
apiVersion: pingcap.com/v1alpha1
kind: PodChaos
metadata:
name: pod-failure
namespace: chaos-testing
spec:
action: pod-failure # the specific chaos action to inject; supported actions: pod-kill/pod-failure
mode: one # the mode to run chaos action; supported modes are one/all/fixed/fixed-percent/random-max-percent
duration: "30s" # duration for the injected chaos experiment
selector: # pods where to inject chaos actions
namespaces:
- default  # the namespace of the system under test (SUT) you've deployed
labelSelectors:
"tier": "frontend" # the label of the pod for chaos injection
scheduler: # scheduler rules for the running time of the chaos experiments about pods.
cron: "@every 1m"
What did you expect to see?
The target pod fails every 1m with duration 30s.
What did you see instead?
The target pod fails every 1m with duration 1s or 2s.

@wwjgit Can you provide more information about the target pod? Chaos Mesh will modify the image of the target pod and make the pod unavailable. If you delete this pod, the pod-failure will recover.

@cwen0
apiVersion: v1
kind: Pod
metadata:
annotations:
chaos-mesh-pod-failure-pod-failure-wordpress-image: repo.jd.local/k8s/wordpress:latest
kubernetes.io/limit-ranger: 'LimitRanger plugin set: cpu, memory request for container
wordpress; cpu, memory limit for container wordpress'
kubernetes.io/psp: restricted-psp
creationTimestamp: 2020-04-24T02:28:41Z
generateName: wordpress-68d4989969-
labels:
app: wordpress
pod-template-hash: "2480545525"
tier: frontend
name: wordpress-68d4989969-8qmrz
namespace: default
ownerReferences:

apiVersion: apps/v1
blockOwnerDeletion: true
controller: true
kind: ReplicaSet
name: wordpress-68d4989969
uid: 1e4d7f36-837a-11ea-bf43-3cfdfe5f325c
resourceVersion: "662383884"
selfLink: /api/v1/namespaces/default/pods/wordpress-68d4989969-8qmrz
uid: 4fb934cb-85d3-11ea-bf43-3cfdfe5f325c
spec:
containers:
env:

name: WORDPRESS_DB_HOST
value: wordpress-mysql
name: WORDPRESS_DB_PASSWORD
valueFrom:
secretKeyRef:
key: password
name: mysql-pass
image: gcr.io/google-containers/pause:latest
imagePullPolicy: Always
name: wordpress
ports:
containerPort: 80
name: wordpress
protocol: TCP
resources:
limits:
cpu: "1"
memory: 1Gi
requests:
cpu: "1"
memory: 1Gi
terminationMessagePath: /dev/termination-log
terminationMessagePolicy: File
volumeMounts:
mountPath: /var/www/html
name: wordpress-persistent-storage
mountPath: /var/run/secrets/kubernetes.io/serviceaccount
name: default-token-52zwl
readOnly: true
dnsPolicy: ClusterFirst
nodeName: kc-bcc-pod24-10-196-108-42.hadoop.jd.local
priority: 0
restartPolicy: Always
schedulerName: default-scheduler
securityContext: {}
serviceAccount: default
serviceAccountName: default
terminationGracePeriodSeconds: 30
tolerations:

effect: NoExecute
key: node.kubernetes.io/not-ready
operator: Exists
tolerationSeconds: 300
effect: NoExecute
key: node.kubernetes.io/unreachable
operator: Exists
tolerationSeconds: 300
volumes:
name: wordpress-persistent-storage
persistentVolumeClaim:
claimName: mywordpress-pv-claim
name: default-token-52zwl
secret:
defaultMode: 420
secretName: default-token-52zwl
status:
conditions:
lastProbeTime: null
lastTransitionTime: 2020-04-24T02:28:41Z
status: "True"
type: Initialized
lastProbeTime: null
lastTransitionTime: 2020-04-24T02:28:42Z
status: "True"
type: Ready
lastProbeTime: null
lastTransitionTime: null
status: "True"
type: ContainersReady
lastProbeTime: null
lastTransitionTime: 2020-04-24T02:28:41Z
status: "True"
type: PodScheduled
containerStatuses:
containerID: docker://38e36ed308e94d414b8981384000a21b19dc760067b0590d009bedfaa41d6c64
image: repo.test.local/k8s/wordpress:latest
imageID: docker-pullable://repo.test.local/k8s/wordpress@sha256:80eb70636cb754584224aa75d4cba92f76d936e914d338d76ddcdebbfb531f76
lastState: {}
name: wordpress
ready: true
restartCount: 0
state:
running:
startedAt: 2020-04-24T02:28:42Z
hostIP: <IP_ADDRESS>
phase: Running
podIP: <IP_ADDRESS>
qosClass: Guaranteed
startTime: 2020-04-24T02:28:41Z

@cwen0 Hi, cwen0, do we have any updates? Or need more information about the issue?

@wwjgit Sorry for the late response. I think it is a bug, some case will make the target pod recreated and make the fake image invalid. I am trying to figure out these cases and fix this.

@wwjgit Hi, I have tested this case, I think the pod-failure have been injected successfully, Although, the status of the pod was running, this pod can't provide service already. You can check the status of your service or check the log of the pod to confirm this. Sometimes, the status of pod changed to running because of gcr.io/google-containers/pause:latest

@cwen0 I see. And thanks a lot for the response.

Hi @wwjgit , any updates on this? Is this problem still reproducible to you?


WIP: update to version 0.2 [ci skip]

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

whoops this is the wrong branch. closing in favor of #4


Poor performance of Android camera demo on arm64

I've been running the Android camera demo on both a Nexus 5 (armeabi-v7a) and Nexus 5X (arm64-v8a).  The older Nexus 5 is able to perform a single recognition in about ~350ms.  The Nexus 5X however performs at around ~750ms.  I wouldn't expect a newer device to perform worse (especially not that much worse) than the older one.
I've tried running the resulting apk from
bazel build //tensorflow/examples/android:tensorflow_demo
as well as
bazel build //tensorflow/examples/android:tensorflow_demo --fat_apk_cpu=arm64-v8a
There's no change in performance for either option on the Nexus 5X.
I know that the -mfpu=neon flag seems to be a problem when building for arm64-v8a so I've had to remove it for those builds.  I suspect the performance issue might be related to the performance benefits of neon.  Is there a different flag that needs to be specified to enable neon support for the arm64-v8a architecture?  Or am I completely off base on the performance expectations on Nexus 5X?
This is related to #1019

I've done some tests of this, and it seems like the Nexus 5X is capable of Nexus 5-comparable performance when the 2 A57 cores help out with the processing. Which, unfortunately, is rarely. The majority of the time the bulk of the processing is done by the slower (but more energy-efficient) A53 cores.
You can see this behavior if you run a systrace while the demo is running and look for the "Recognize" calls. e.g. python $SDK_ROOT/platform-tools/systrace/systrace.py --time=5 -o nexus5x.html sched gfx view wm --app=org.tensorflow.demo
Over 25 runs I saw a min demo inference time of 285ms, a max of 642ms, with an average of 491ms.
I also looked at the per-operation performance (by compiling with -DLOG_DETAILED_STATS), and found the worst offenders for lower performance by far were the convolutions. For example,                    conv2d2_pre_relu/conv took an average of 40ms on the Nexus 5, but a whopping 106ms on the Nexus 5x.

@andrewharp Does that mean there isn't much that can be done to improve the performance on the Nexus 5X?  I haven't run it on the 6P or any other 64-bit device to be able to compare to Nexus 5.

If you can figure out how to force all the cores to activate it should be possible to increase the speed. Though I expect thermal throttling will kick in fairly quickly and it will be impossible to maintain the performance over a sustained duration.

I don't have a Nexus 5x on hand, but I have a suspicion that tensorflow tries to use all the 6 cores and spawns 6 threads for computation. Because of the non-homogeneous setup in 5X this might lead to thrashing. Could you please try using just 1-4 cores and checking how this scales. You can do that in tensorflow_jni.cc set intra_op_parallelism_threads explicitly to 1, 2, 3 or 4 in the ConfigProto.
If this is the case, it means that our current multithreading scheme doesn't handle on demand non-homogeneous cores well.
IIRC neon is turned on by default for Arm64 builds.

average recognition time without setting explicit intra_op_parallelism_threads: 743ms
Results of testing config.set_intra_op_parallelism_threads(size):
size = 1 average recognition time: 1919ms
size = 2 average recognition time: 1064ms
size = 4 average recognition time: 742 ms
size = 6 average recognition time: 704 ms
Seems like it's running with 4 when not setting thread count explicitly.

This seems to be the culprit: https://github.com/tensorflow/tensorflow/blob/master/tensorflow/core/platform/posix/port.cc#L43

When I ran a standalone benchmark of the same model (coming soon), both devices improved their performance considerably.
5 standalone benchmark: 238ms
5x standalone benchmark: 315ms
For reference, here's the performance I saw in my last run of the standard TF Android camera demo:
5: 330ms
5x: 565ms
The standalone runs perform much better than the app version in both cases, but considerably moreso on the 5x. This implies the overhead of running the user-facing Android app differentially affects the 5x, in addition to or magnifying the speed discrepancy caused by the CPU setup.

I just tried setting kDefaultCores to 6 on the 5x, and got 501ms/run in the TF demo app. Surprisingly there was no improvement at all in the standalone benchmark, as it ran in 316ms/run.

Further testing reveals that adding a delay between inference passes of 1 seconds gives an per-inference average of 427ms over 50 runs.
This is compared to a 321ms result on an otherwise identical test with the inter-inference delay set to 0.
I'd speculate that in the Android camera demo, the delay between receiving frames to process is significant enough that the processor scales down, and needs to ramp back up once inference starts again. A busy loop might help with that behavior.

Not sure it's related, but we had a similar difference in performance between standalone benchmark binary and test app on the Nexus 5X for our neural networks, and we tracked it down to the compiler inlining some functions in the binary and not in the .so library. We fixed it by adding linker-time optimization (LD_FLAGS += -flto -O3), that fixed the issue and also reduced the library size.

@andrewharp @petewarden What's the status of this?

The standalone benchmark target tensorflow/tools/benchmark:benchmark_model has been added which will allow users to repeat their own experiments.
We're still evaluating compilation flags to get the best performance out of mobile builds. As far as the 5x in particular, I think we have viable explanations for the performance difference (asymmetric cores, etc) but no simple solution to improve it right now.

@andrewharp Should I leave it assigned to you or Pete, or mark it contributions welcome if there is something specific we could ask others to contribute?  We're trying to avoid leaving nonspecific bugs open.

I don't think we have any specific plans at the moment to improve 5X (relative) performance, so this should probably be closed. Happy to test out any contributions, though.

The native OCR code that I work with runs painfully slow without compiler optimizations on arm64-v8a
Recognizing a default test image was taking ~19 sec on the arm64-v8a Nexus 5x, but only ~7 sec on the considerably weaker armeabi-v7a Moto E2.
As @bissacc0 said, be sure to use:
APP_OPTIM := release
APP_CFLAGS += -O3
LOCAL_LDFLAGS += -flto
In your make files. Using these flags reduced recognition time from 19 s to 4 s (!!!) on the Nexus 5x

@jf-rce   whice file to add the build configure ???
APP_OPTIM := release
APP_CFLAGS += -O3
LOCAL_LDFLAGS += -flto

Hi there - I'm trying to test the demo app as well. One thing I noticed is that only 4 cores of my 8-core phone were used, even if I changed the number of threads by ProtoConfig. I also modified the function NumSchedulableCPUs in port.cc to set kDefaultCores to 8.
Any advice?

@jf-rce? Currently our Makefile only targets armeabi-v7a, so it's not surprising there could be improvements there, but do you know if these flags have any affect on the Bazel build as well?
@zhangpao17 You should add them in [tensorflow/contrib/makefile/Makefile] (https://github.com/tensorflow/tensorflow/blob/master/tensorflow/contrib/makefile/Makefile#L213) under the Android section.
@kindloaf #8653 may help with this.

Hi @andrewharp ,
Thanks for the reply. I modified the code in port.cc, and logged the return value of NumSchedulableCPUs, which is 8. Still, my phone is using only 4 cores.
Are there other restrictions on tensorflow framework? Or, maybe 4 cores are the most that the framework can use - the bottleneck is not on computation?


Wrong webview is obtained when inspector is open

If you have the inspector open in your webview you can have 2 subviews, one of them being a WKInspectorWKWebView.  This view should be ignored so messages are sent to the correct webview.

Ah that's a good catch thanks! Can you also do the same change in src/index.js l.321?

Didn't realize it was used elsewhere... oops!  It has been updated.


[Bug] ParseLatinFont function returns minor font

The ParseLatinFont function returns minor font. Its possible that the font on the shape is a major font

From what I could gather, the development can be done by using PlaceHolder Class
https://docs.microsoft.com/en-us/dotnet/api/documentformat.openxml.presentation.placeholdershape?view=openxml-2.8.1
By inspecting the XML of the document, I think that the shape class in this project can keep a mapping of the placeholder values which can then map to the applied Layout xml and pick the major or minor value by reading ListStyle and using the appropriate level LevelXParagraphProperties
https://docs.microsoft.com/en-us/dotnet/api/documentformat.openxml.drawing.liststyle?view=openxml-2.8.1

Yep, I think you are right. Honestly, I am not happy about the current placeholders parsing. BTW, I have not good investigated PlaceholderShape class, but it seems, does not have direct access to the corresponding shape on Slide Layout. Manual searching by PlaceholderShape.Index should be done to get placeholder content from the Slide Layout.
In addition to ListStyle, there is a case when DefaultTextStyle from the presentation level should be parsed to get font data.
Working on the fix...

Yes, the manual searching is the part where I am stuck, thinking about it.

Closed via 0.16.1 release.
Feel free to re-open or create a new one if you find a bug in font data parsing.


build: stop distributing test files

Proposed Changes
Test files are currently compiled and distributed
Potential Breaking Changes
None
Acceptance Criteria

[ ] The proposed changes are covered by unit tests
[ ] The potential breaking changes are clearly identified
[ ] README.md is adjusted to reflect the proposed changes (if relevant)

This change prevents the tests from being compiled, so I will close the PR. Go upvote that issue


Comparisons should show both absolute and relative differences

A percentual change column would be very helpful in cases like

A random thought: Would a bar chart or similar graph be useful to visualize changes? I am not sure how well it scales to lean's massive set of measurements, but it might make such comparisons more intuitive?

Hmm, not sure how that would help on a <1% change like above.

A horizontal bar chart would have a few hundred to thousand pixels and could potentially do show that. In any case it might allow for a better overview than reading 60 lines in a table and trying to find out which changed and if there are any outliers.
The detail graph is providing an overview for a few dimensions over time, the chart here would be an overview over all dimensions for a single comparison. A more visual version of the significance chips basically.
I am not sure if that is truly useful, it was just a random idea while scrolling through the dimensions in the comparison page.


Get always the same color for the same string (with fix - I think can be improved)

If you need to obtain the same image you can replace
let x = Int(arc4random_uniform(UInt32(color1.count)))
with
srandom(UInt32(text.characters.count))
let x = Int(random()%color1.count)
is based on the length of the string, not the content
It can be implement better and add it as an option, no default

@SalvaP
Nice option! Will be proceed it soon.
Thanks bro.

@SalvaP
I placed new option for this issue. You could check it in ReadMe.
Thanks!

Thank you!
I thought I'd calculate the seed taking into account the contents of the string by replacing
srandom(UInt32(text.characters.count))
with
srandom(UInt32(abs(text.hashValue)%1000))
takes the last 3 numbers of the  |hashValue|
.hashValue can be replaced with .hash (should be used the one that takes less resource to be calculate but i don't know which is)
%1000 can be at max  %1000000000 in my tests (but 3 to 5 digits shoud be enough)
always can be simpler/improved


On boarding in console

Sometimes it is difficult to users who got the first time to the ZITADEL console, to find out what they do have to do. We could make kind of a checklist they have to go through to solve the first tasks. The checklist could be shown in the dashboard. And after I have resolved one step I get back to the dashboard and the next point.
Acceptance criteria

[ ] 1. Create a project (step is shown as resolved as soon as projects length > 0)
[ ] 2. Create a client  (step is shown as resolved as soon as applications length > 0)
[ ] 3. Branding (step is shown as resolved as soon as private labeling policy is added)
[ ] 4. SMTP (This we should implement as soon as we have the test email #4504 )
[ ] 5. Add a second user
[ ] 6. Give the user some rights in ZITADEL

related #4298

As discussed with @peintnermax beforehand, here is a first draft of a new starting page in console to improve/encourage onboarding process for new users:

(Picture 1 showing the new starting page (Home))

(Picture 2 shows the omipresent progress bar and the hover state of it with the detail view visible)
The idea behind this is that we want to guide new users with the most essential setup steps as a progress process.
If the user is experienced with ZITADEL or doesn't want to see this progress view, they can opt-out by clicking on the link bottom right of the detail view (see above).
Also once they have completed the progress to 100%, they can "close" the progress (the above mentioned link will change to 'Congratulations! You've done it') and the Home view loses the progress indicators.
Which steps are relevant for a MVP is to discuss (or see above) but I'd go with a min-maxed approach.
Continuation in Issue #4835


CLI Command to Consume and Display Edge Specific Command and Control

Create a CLI command to consume and present status of each scoped process based on state files define for use by Edge and defined in #1404
Respond to async notification of file changes
Based on file content display state and status much like top and the scope dash command

Design approach has been updated such that we are not using a file based status. Different issues are created. Closing this one.


Add slice support for FileRegion.

Motivation:
Let codec such as HTTP/2 can write FileRegion chunk by chunk.
Modifications:
Add a transferIndex which is similar to readerIndex in ByteBuf for FileRegion.
Add two transferBytesTo methods which are similar to readBytes in ByteBuf for FileRegion.
Add slice and transferSlice methods which are similar to slice and readSlice in ByteBuf for FileRegion.
Make the return value of position to be the offset related to the FileChannel returned by channel method. And for DefaultFileRegion, the return value of the original position method is the offset related to the underlying FileChannel, so this does not break compatibility.
The new methods are added to a SliceableFileRegion interface which extends the old FileRegion interface, will move the new methods to FileRegion at the next minor release.
Add a FileChannelBasedFileRegion which makes it easier for implementation file channel related file regions.
Add a FileChannelBasedSlicedFileRegion which is package private.
Add FileChannelBasedSlicedFileRegionTest.
The native transport has not been modified yet so it can not accept the FileChannelBasedSlicedFileRegion right now, will address it in another PR.
Result:
Passed all FileRegion related testsuites.
Fixes
The first step of #3927

The first step of #3927

ping @Scottmitch @nmittler @normanmaurer . Thanks.

@normanmaurer I've modified the code based on your comments. Now the new methods are only in AbstractFileRegion. In the XXXByteStreamChannel implementations I've added a new branch to handle AbstractFileRegion and also added a comment to say that please remove the branch once we release netty 4.2 and move the methods in AbstractFileRegion to FileRegion.

Any other concerns?  @normanmaurer Thanks.

Introduce a new interface called SliceableFileRegion. The new methods are all added to this interface. And also introduce a FileChannelBasedFileRegion class to place the common code. The FileChannel channel() method is marked as protected since in JNI seems we are free to call protected methods.
@normanmaurer  PTAL. Thanks.

Fix checkstyle problem.
Ping @normanmaurer .
Thanks.

@ejona86 @carl-mastrangelo @Scottmitch  PTAL as well

@ejona86 I've added the support for transferTo. PTAL.
And I didn't remove the related code in DefaultFileRegion as we will access the transferred field in native transport. I think we can discuss whether we can remove these code in the follow on native transport PR.
Thanks.

@Scottmitch Filed #7155 for the follow on work. Do not know why I can not reply to the comment directly...

Any other concerns? @Scottmitch @carl-mastrangelo . Thanks.

Any more concerns?  Thanks.

Ping @normanmaurer  @Scottmitch

@Scottmitch  Rebase and squash done.

@normanmaurer - Please pull this in after the next release if you are satisfied.

4.1.16 is out, is it OK to pull in this now? There are several follow on issues, such as adding native transport support, and also need to start trying to add FileRegion support for HTTP/2.
Thanks.

@Apache9 I will try to have a final look this week

Any updates here? @normanmaurer
Thanks.

@Apache9 - sorry for delay ... thanks for your patience ... hang in there we will pull this in soon.

Thanks @Scottmitch  . Wait for your good new.

Ping @Scottmitch @normanmaurer .
Thanks.

@Apache9 sorry I know you wait forever :( Its on my to do list for this week.

Wait for your good news.

@Apache9 sorry if I asked this before but can you please tell me again what exactly you need this for ? Is it "just" so you can write a File in slices without the need to open multiple FileChannels ?

@normanmaurer We need this to add the FileRegion support for HTTP/2. We can not embed a large FileRegion in a single data frame when we actually write it out, we need to split it to several small ones.
Thanks.

@Apache9 ok so its related to what I thought... Now a maybe stupid question but why could you not just open a FileChannel and create multiple new DefaultFileRegion using this FileChannel with different position and count arguments ? The only "problem" I can see here is that you need to ensure you not close the FileChannel under the hood when not all are written yet.

So you mean we should expose an API in HTTP/2 with something like a FileRegion but not a FileRegion? Maybe Http2FileRegion? Which will have the slice support and returns a FileRegion for slice? I'm OK with it. Just want to know your decision.
Thanks.

@Apache9 why you can't just write a FileRegion with the correct size from the beginning ? Or you want to "enqueue" something into the HTTP2 layer and dynamically slice out the correct stuff ?

Oh, maybe I need to say more. For the end users of the HTTP/2 API, it is impossible for them to write a FileRegion with exactly the correct size for a data frame, there are flow controls, and there maybe others writing on the same connection but different streams, so the next data frame available to them will be changed dynamically. In the framework we will do splitting and merging of data frames.
So I think the correct way to do this is to give end users the ability to write a very large FileRegion or something like a FileRegion, and we will split it to several small data frames in the framework.
Thanks.

@Apache9 ok got it...
So I think what I would do is to have another abstraction which basically provides a "Stream" of FileRegion on demand. I think this would minimise the changeset a lot. I am not convinced that we really need the slice stuff on the FileRegion itself.
Let me open a PR that shows the idea... Gimme a few minutes ;)

@Apache9 check https://github.com/netty/netty/pull/7435 ... No unit tests included yet ;)

Let me close this as this is not really something we want to do for 4.1.


Update To Most Recent Pasts

[x] Turn speakers and microphone into notifiers
[ ] Box microphone and speaker ffi as MicrophoneInner and SpeakerInner (soundness)
[ ] Update WebAssembly port
[ ] Doc tests
[ ] Query (default to 0 channels?)

Closes https://github.com/libcala/wavy/pull/43


Something wrong about self.loader_test

Hello, firstly, thank you for your test code.
But I get some errors about self.loader_test when I run the demo code.
At 'MSRN/Test/code/trainer.py' line 111, self.ckp.log[-1, idx_scale] = eval_acc / len(self.loader_test), I get the error which reports that the len(self.loader_test) is zero. I check the self.loader_test which is dataloader.MSDataLoader object, and its length should be zero in python3.6. Maybe the version of something is still different, or the path to somewhere has not been modified. I hope that you can make some suggestions. Thanks.

The root of the problem is the version of scipy. The version of scipy should be < 1.2.0, otherwise some functions can not be used.


add text CNN model for text classification problem

I'd like to add textCNN model for text classification problem.

It's my first time to add new model to tensor2tensor, so please feel free to let me know if you have any concerns.
Most code in this PR comes from this repo, I just did some adaptation work to follow tensor2tensor interface, again please let me know if you have any concerns. @dennybritz
I've done some experiments based on existing problem(sentiment_imdb), see below table in detail, again please let me know if we need more experiment result to add such model.

Problem
Model
Parameters
Metrics

sentiment_imdb
transformer_encoder
hparam = transformer_tiny, train_steps = 2000
accuracy=0.7675

sentiment_imdb
transformer_encoder
hparam = transformer_tiny, train_steps = 10000
accuracy=0.8259

sentiment_imdb
transformer_encoder
hparam = transformer_tiny, train_steps = 20000
accuracy=0.8302

sentiment_imdb
text_cnn
hparam = text_cnn_base, train_steps = 20000
accuracy=0.8357

Thanks for the model, good to know it can get reasonable results :).


Optionally enable kernel logging

Add NewModuleArgs's KernelLogLevel arg option.

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

thanks, updated.

@umanwizard thanks again for your contrib.


Run Without Debug never terminates if uncaught exceptions breakpoint is enabled

When using CTRL+F5 to launch a node app without debugging it, the launched app never exits if either caught or uncaught exceptions breakpoint is enabled.

VS Code Version:
Version: 1.54.3
Commit: 2b9aebd5354a3629c3aba0a5f5df49f43d6689f8
Date: 2021-03-15T11:57:12.728Z (4 days ago)
Electron: 11.3.0
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Darwin x64 19.6.0

Steps to Reproduce:

In a new workspace, create a simple hello.js file that logs hello to the console
Create a launch config for it:

{
  "version": "0.2.0",
  "configurations": [
    {
      "type": "pwa-node",
      "request": "launch",
      "name": "Launch Program",
      "console": "integratedTerminal",
      "skipFiles": [
        "<node_internals>/**"
      ],
      "program": "${workspaceFolder}/hello.js"
    }
  ]
}

CTRL+F5 to launch it, notice it exits normally:

Debugger attached.
hello
Waiting for the debugger to disconnect...

Now check the "Uncaught Exceptions" in the breakpoints view and try again.

The terminal shows only:
Debugger attached.

and the program never runs.  Stop button on the debug toolbar kills it, but VSCode thinks the launch is still active and the toolbar never goes away.

Does this issue occur when all extensions are disabled?: Yes/No

/jsDebugLogs


can we give up getter and setter syntax?

we can do it the same, and koa code size is decreased, for example；
module.exports = {
... some code ...

  get message() {
  },
  set message(msg = null) {
    if (msg) {
      this.res.statusMessage = msg;
    } else {
      return this.res.statusMessage || statuses[this.status];
    }
  },

... some code ...
}

@anlexN

Can we give up getter and setter syntax?

Nope!
Take a look in your code!
You created poor readability and an unnecessary cyclomatic complexity.
By the way, in your example has a bug, it's not possible set 0 or false.

how is this?
module.exports = {
... some code ...

  get message() {
  },
  set message(msg) {
    if (msg != undefined) {
      this.res.statusMessage = msg;
    } else {
      return this.res.statusMessage || statuses[this.status];
    }
  },

... some code ...
}

There's no need to change this unless there's a bug involved.


Copy mistake in Projects section

Planetfall.io and Unkey.dev have the same project description, might want to check that out ;)

Yeah, caching :/
fixed now


nginx worker hangs while logging to the audit log

Hello,
In our company we use ModSecurity in our nginx. We noticed that sometimes nginx workers just hangs and do nothing, however when we strace the process (or attach the gdb), then the worker starts spinning again. This problem happens when we enable audit logging (ex: SecAuditLog /var/log/modsec_audit.log), I have traced the issues to the following line https://github.com/SpiderLabs/ModSecurity/blob/0eb3c123f447b8787ea726ad4d4439018a07ee31/src/utils/shared_files.cc#L236 it appers that proccess is unable to wakeup and acquire the lock for the file and it is just waiting.
backtrace:
#1  0x00007f31debc4714 in __GI___pthread_mutex_lock (mutex=0x7f31debef008) at ../nptl/pthread_mutex_lock.c:80
#2  0x00007f31de95474a in modsecurity::utils::SharedFiles::write(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*) () from /usr/lib/x86_64-linux-gnu/libmodsecurity.so.3
#3  0x00007f31de8dd9a4 in modsecurity::audit_log::writer::Serial::write(modsecurity::Transaction*, int, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*) () from /usr/lib/x86_64-linux-gnu/libmodsecurity.so.3
#4  0x00007f31de8dcc0e in modsecurity::audit_log::AuditLog::saveIfRelevant(modsecurity::Transaction*, int) () from /usr/lib/x86_64-linux-gnu/libmodsecurity.so.3
#5  0x00007f31de8cd966 in modsecurity::Transaction::processLogging() () from /usr/lib/x86_64-linux-gnu/libmodsecurity.so.3
#6  0x0000563cedc9d11c in ngx_http_modsecurity_log_handler (r=<optimized out>) at ../modules/ngx_modsecurity_module/src/ngx_http_modsecurity_log.c:83
#7  0x0000563cedc0b41d in ngx_http_log_request (r=0x563cf1a308e0) at src/http/ngx_http_request.c:3684
#8  ngx_http_free_request (r=r@entry=0x563cf1a308e0, rc=<optimized out>) at src/http/ngx_http_request.c:3630
#9  0x0000563cedc0b4f8 in ngx_http_close_request (rc=0, r=<optimized out>) at src/http/ngx_http_request.c:3576
#10 0x0000563cedc1e90d in ngx_http_upstream_process_request (r=0x563cf1a308e0, u=0x563cf20a8538) at src/http/ngx_http_upstream.c:4122
#11 0x0000563cedc2275b in ngx_http_upstream_send_response (u=0x563cf20a8538, r=0x563cf1a308e0) at src/http/ngx_http_upstream.c:3306
#12 ngx_http_upstream_process_header (r=0x563cf1a308e0, u=0x563cf20a8538) at src/http/ngx_http_upstream.c:2479
#13 0x0000563cedc1dd92 in ngx_http_upstream_handler (ev=<optimized out>) at src/http/ngx_http_upstream.c:1329
#14 0x0000563cedbf6836 in ngx_epoll_process_events (cycle=<optimized out>, timer=<optimized out>, flags=<optimized out>) at src/event/modules/ngx_epoll_module.c:901
#15 0x0000563cedbece76 in ngx_process_events_and_timers (cycle=cycle@entry=0x563cf02d4250) at src/event/ngx_event.c:260
#16 0x0000563cedbf4a18 in ngx_worker_process_cycle (cycle=cycle@entry=0x563cf02d4250, data=data@entry=0x1) at src/os/unix/ngx_process_cycle.c:767
#17 0x0000563cedbf3159 in ngx_spawn_process (cycle=cycle@entry=0x563cf02d4250, proc=proc@entry=0x563cedbf4990 <ngx_worker_process_cycle>, data=data@entry=0x1, name=name@entry=0x563ceded3328 "worker process", respawn=respawn@entry=-3) at src/os/unix/ngx_process.c:203
#18 0x0000563cedbf5366 in ngx_start_worker_processes (cycle=cycle@entry=0x563cf02d4250, n=40, type=type@entry=-3) at src/os/unix/ngx_process_cycle.c:372
#19 0x0000563cedbf581b in ngx_master_process_cycle (cycle=0x563cf02d4250) at src/os/unix/ngx_process_cycle.c:144
#20 0x0000563cedbc8cad in main (argc=<optimized out>, argv=<optimized out>) at src/core/nginx.c:382

We use the following connector
server:

nginx 1.17 - 40 workers
Debian 10 (buster)
libmodsecurity3 (3.0.3)

Is this a bug or this directive cannot be used with multiple processes logging to the same file?

Hi, @wutchzone
That sounds to be a bug. Further investigation is needed. Do you happen to have the audit log in Serial or Parallel mode?

We have set it as SecAuditLogType Serial.
I will try to create a reproducible example on local machine. For now I am able to reproduce this behavior only in production, where we have multiple CPU cores (40+). I will also experiment with other types of locks.

Hi @wutchzone ,
I'm not certain whether this would help your particular situation, but you might want to consider upgrading your libmodsecurity version to v3.0.4.  There were some fixes post-v3.0.3 that might be relevant.  I'm thinking in particular of:
https://github.com/SpiderLabs/ModSecurity/commit/3d2030426c22c41a85cda92289dc284094fba5fd

@wutchzone did you had the chance to test v3.0.4?

Here's the solution:
I was experiencing the same problem, and it would appear that Atomicorp wrote some 'bad rules' which have caused nginx processes to hang.  If you are running ASL or if you are just using atomicorp's modsecurity package, this is why your nginx processes are getting stuck.  They have pushed out an update, so you will need to update your modsecurity package as soon as possible, or you will probably continue getting the same errors.
Good luck.

We wil update the library by the end of the week. I will let you know once I will have the results.
Thank you all for quick response and help.

@zimmerle Sadly updating the package to the latest version did not help either. Workers are still getting stuck as cen bee see on the image below.

@mrwizard64 I am not aware of that we are using rules from Atomicorp. We are using this.

But after the update it stucks less frequent. Once i catch it again I will provide full backtrace.

But after the update it stucks less frequent. Once i catch it again I will provide full backtrace.

thank you. The core flie will lead you to the fullbacktrace. It could help a lot

Thanks buddy
On Mon, Aug 3, 2020 at 7:35 AM Daniel Sedlak<EMAIL_ADDRESS>wrote:

But after the update it stucks less frequent. Once i catch it again I will
provide full backtrace.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SpiderLabs/ModSecurity/issues/2373#issuecomment-667972475,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIL6PLCVD7T5N3XUU5WHM7LR62OGHANCNFSM4PITTMIA
.

It looks like it is stuck on another pthread_mutex_lock(). I am unable to locate pthread_mutex_lock in this function (modsecurity::utils::find_resource), maybe something got inlined.
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103
#1  0x00007fa81d99a714 in __GI___pthread_mutex_lock (mutex=0x7fa81d9c5008) at ../nptl/pthread_mutex_lock.c:80
#2  0x00007fa81d72a74a in modsecurity::utils::find_resource(std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >*)
    () from /usr/lib/x86_64-linux-gnu/libmodsecurity.so.3
#3  0x0000000000000008 in ?? ()
#4  0x384b505942563964 in ?? ()
#5  0x0000292934302100 in ?? ()
#6  0x00007fff254c5710 in ?? ()
#7  0x0000000000000000 in ?? ()

But this time it happens less often. When we turn off Audit Log workers no longer stucks.

Any chance that the server demand of actually writing to the audit log is
draining system resources to the point of collapse?
On Tue, Aug 4, 2020 at 6:07 AM Daniel Sedlak<EMAIL_ADDRESS>wrote:

It looks like it is stuck on another pthread_mutex_lock(). I am unable to
locate pthread_mutex_lock in this function (
modsecurity::utils::find_resource), maybe something got inlined.
#0  __lll_lock_wait () at ../sysdeps/unix/sysv/linux/x86_64/lowlevellock.S:103
#1  0x00007fa81d99a714 in __GI___pthread_mutex_lock (mutex=0x7fa81d9c5008) at ../nptl/pthread_mutex_lock.c:80
#2  0x00007fa81d72a74a in modsecurity::utils::find_resource(std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator > const&, std::__cxx11::basic_string<char, std::char_traits, std::allocator >*)
() from /usr/lib/x86_64-linux-gnu/libmodsecurity.so.3
#3  0x0000000000000008 in ?? ()
#4  0x384b505942563964 in ?? ()
#5  0x0000292934302100 in ?? ()
#6  0x00007fff254c5710 in ?? ()
#7  0x0000000000000000 in ?? ()
But this time it happens less often. When we turn off Audit Log workers
no longer stucks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/SpiderLabs/ModSecurity/issues/2373#issuecomment-668507646,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIL6PLDZOFE2MFNBWL2T5XTR67MXDANCNFSM4PITTMIA
.

Any chance that the server demand of actually writing to the audit log is
draining system resources to the point of collapse?

Not possible. There is over 100 GiB of free RAM, and few TBs of disk space.

Is it possible to see a full backtrace with symbols (like in your original posting) for this new instance?  The stack of function names with line numbers could be helpful.

Our nginx is compiled with Lua support, sometimes in GDB it is not possible to see function names in backtrace due to LuaVM. Dunno why, maybe it was somehow stripped or JITed out. I will check it out more.

@wutchzone  Is this issue already solved?

@wutchzone  Is this issue already solved?

No, issue still not resolved. Using Mainline nginx 1.19 and latest modsec. After enabling module, nginx just hangs out after ~30sec.

I am sorry for the late response. The issue still persists. I am unable to get a better backtrace, but the issue occurs more frequently on machines with more workers.

Hi @wutchzone, are you still facing this problem? I'm using the same spec as yours (ModSecurity V3.0.3 + OWASP CRS),
and we got 4 pods crashed in the production environment yesterday, have no idea what's going on because K8s just deleted those pods so we couldn't check the logs then.
How did you avoid this kind of problem finally? Just by turning off the audit logging?
Pod spec:
limits:
  cpu: 400m
  memory: 800Mi

requests:
  cpu: 100m
  memory: 300Mi

ModSecurity conf:
SecAuditEngine RelevantOnly
SecAuditLogRelevantStatus "^(?:5|4(?!04)(?!01))"
SecAuditLogParts ABIJDEFHKZ
SecAuditLogType Concurrent
SecAuditLog /var/log/modsec_audit.log

# And We include most of OWASP CRS that official recommends
Include /etc/nginx/owasp-modsecurity-crs/crs-setup.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-900-EXCLUSION-RULES-BEFORE-CRS.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-901-INITIALIZATION.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-903.9001-DRUPAL-EXCLUSION-RULES.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-903.9002-WORDPRESS-EXCLUSION-RULES.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-905-COMMON-EXCEPTIONS.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-910-IP-REPUTATION.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-912-DOS-PROTECTION.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-921-PROTOCOL-ATTACK.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-930-APPLICATION-ATTACK-LFI.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-931-APPLICATION-ATTACK-RFI.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-933-APPLICATION-ATTACK-PHP.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-941-APPLICATION-ATTACK-XSS.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-942-APPLICATION-ATTACK-SQLI.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-943-APPLICATION-ATTACK-SESSION-FIXATION.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/REQUEST-949-BLOCKING-EVALUATION.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/RESPONSE-950-DATA-LEAKAGES.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/RESPONSE-951-DATA-LEAKAGES-SQL.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/RESPONSE-952-DATA-LEAKAGES-JAVA.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/RESPONSE-953-DATA-LEAKAGES-PHP.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/RESPONSE-954-DATA-LEAKAGES-IIS.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/RESPONSE-959-BLOCKING-EVALUATION.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/RESPONSE-980-CORRELATION.conf
Include /etc/nginx/owasp-modsecurity-crs/rules/RESPONSE-999-EXCLUSION-RULES-AFTER-CRS.conf

We are using SecAuditLogType Concurrent which the official docs recommended avoiding performance impact.
But after we checked the Nginx ingress deployment resource on GKE.
(the left-side chart is CPU, and the right one is memory)
(blue line is the limit, the orange line is used, and the yellow line is requested)

As you can see, the CPU usage was going up slowly since 8 PM, and after it reached the peak, the health check could not be responded to in 5 seconds, so the pods were terminated, and that's why the CPU usage dropped dramatically, then we were unable to roll out the deployment normally because the health check was still failed even we killed the broken pod. So we disable ModSecurity, rollout the deployment, and everything was being alright.
The pods couldn't respond to any requests when the CPU and Memory usage didn't even reach half of the limit.
If you have any suggestions, please let me know!
Thank you!

I have the same behavior. I've tried logging through the Concurrent and the Serial modes and, in both cases, the system hangs after running for a while. And it seems it is not much related with the load nginx is receiving, as I had issues by the beginning of the day and by the rush hour.
Below is a graph on the server CPU:

Not sure if this matters, but I'm running this is on GCP, on a e2-standard-2 machine (2 CPUs and 8 GB of RAM).


fix(core): change form validity when expressionProperty change.

What kind of change does this PR introduce? Bug fix
fix #582

This change is

Codecov Report

Merging #590 into master will increase coverage by 1.15%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #590      +/-   ##
==========================================
+ Coverage   92.93%   94.09%   +1.15%
==========================================
  Files          16       16
  Lines         736      745       +9
  Branches      212      215       +3
==========================================
+ Hits          684      701      +17
+ Misses         52       44       -8

Impacted Files
Coverage Δ

src/core/src/services/formly.form.builder.ts
97.14% <100%> (+0.08%)
:arrow_up:

src/core/src/utils.ts
96.11% <100%> (+0.03%)
:arrow_up:

src/core/src/components/formly.field.ts
92.42% <100%> (+8.7%)
:arrow_up:

src/core/src/services/formly.config.ts
90.9% <0%> (-3.04%)
:arrow_down:

Continue to review full report at Codecov.

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


⚠ Bofrost.com has degraded performance

In cf3d1b3, Bofrost.com (https://www.bofrost.com) experienced degraded performance:

HTTP code: 200
Response time: 674 ms

Resolved: Bofrost.com performance has improved in 6aeb00f.


Replace internal _Succeed trait with Iterator::try_fold

Thanks to scottmcm for pointing out this is a way to access Try::from_output on stable.

Need to do some extra testing of dependents since I'm not 100% sure that the tests cover all potential inference issues.


irobot_create_msgs: 2.1.0-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository irobot_create_msgs to 2.1.0-1:

upstream repository: https://github.com/iRobotEducation/irobot_create_msgs.git
release repository: https://github.com/ros2-gbp/irobot_create_msgs-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: null

irobot_create_msgs
* rename DockServo action into Dock and Dock msg into DockStatus
* Contributors: Alberto Soragna

@clalancette  Is it required that an entry have a 'status' field? I didn't see it mentioned in the docs.

@clalancette Is it required that an entry have a 'status' field? I didn't see it mentioned in the docs.

Good question.  I think the answer is 'no', as we have at least one example in Humble currently that does not have it: https://github.com/ros/rosdistro/blob/306acc05a8de06b506aaf722670b01911036010c/humble/distribution.yaml#L69-L78


Set up matrix CI tests for both local and GitHub Actions

Python 3.9-3.12, Pytest 6.2.x-8.x.
There are a couple of different ways to do this. See:
https://github.com/pypa/hatch/issues/669
https://github.com/pypa/hatch/issues/858

PR #16 takes care of the local test matrix.


Support Image Uploading

The document processor should support the uploading and embedding of images like PNG, JPEG, and other static formats.
Ideally, this should describe the image and return that text for embedding instead of trying to do a multi-modal embedding which will be impossible to search textually over.

Are you thinking that it should use something like a  BERT or Deepdanbooru to extract info from?

Are you thinking that it should use something like a BERT or Deepdanbooru to extract info from?

Both of these would be an issue to run locally since they require some big resources. Deepdanbooru is also specific to anime-girls image tagging and tends to give more NSFW results so honestly easiest implementation is just using something simple like OpenAIs CLIP which can run on replicate pretty easily (but will still cost money)

If you are calling out to external resources, there’s lots of choices of course.

it return anythingllm File extension .jpg not supported for parsing and cannot be assumed as text file type.

@phicha20224 - that is because we dont support uploading images right now

@phicha20224 - that is because we dont support uploading images right now

what i need to do for the support on images?


Implement "snabb config listen" for snabb-softwire-v1

Following on after #569, we need to implement a persistent listener interface.  When a configuration agent such as sysrepo connects to the config app in the Snabb lwAFTR manager process, that will put the conf app in a mode whereby it does not accept mutations (add/remove/set/listen) commands from other clients.  get and get-state can still proceed though.  The config app can still handle multiple connections; when a socket is ready for I/O the config app will block reading a single JSON or other expression, then handle it, and then check in a nonblocking way whether the fd is still readable or no.
Of course we need to also implement the snabb config listen stub process that talks to the config app as well.

Implementation in #594.

This works as documented here: https://github.com/Igalia/snabb/blob/lwaftr/src/program/config/README.md.
Specifically for the lwAFTR, consider that you have a running lwaftr instance named lwaftr.  If you don't have one, you can run one:
sudo ./snabb lwaftr run --name lwaftr --reconfigurable --cpu 4 --conf program/lwaftr/tests/data/icmp_on_fail.conf --v4 03:00.0 --v6 03:00.1

You have to pass --reconfigurable to the lwaftr, to give it config integration.  Then:
[wingo@snabb2:~/snabb/src]$ sudo ./snabb config listen lwaftr

That opens a listener.


Could not find com.github.umair13adil:RxLogs:1.0.18. Flutter

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:checkDebugAarMetadata'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
   > Could not find com.github.umair13adil:RxLogs:1.0.18.
     Searched in the following locations:
       - https://dl.google.com/dl/android/maven2/com/github/umair13adil/RxLogs/1.0.18/RxLogs-1.0.18.pom
       - https://repo.maven.apache.org/maven2/com/github/umair13adil/RxLogs/1.0.18/RxLogs-1.0.18.pom
       - https://storage.googleapis.com/download.flutter.io/com/github/umair13adil/RxLogs/1.0.18/RxLogs-1.0.18.pom
       - https://jitpack.io/com/github/umair13adil/RxLogs/1.0.18/RxLogs-1.0.18.pom
       - https://jcenter.bintray.com/com/github/umair13adil/RxLogs/1.0.18/RxLogs-1.0.18.pom
       - https://cardinalcommerceprod.jfrog.io/artifactory/android/com/github/umair13adil/RxLogs/1.0.18/RxLogs-1.0.18.pom
       - https://www.jitpack.io/com/github/umair13adil/RxLogs/1.0.18/RxLogs-1.0.18.pom
       - https://storage.zego.im/maven/com/github/umair13adil/RxLogs/1.0.18/RxLogs-1.0.18.pom
       - https://developer.huawei.com/repo/com/github/umair13adil/RxLogs/1.0.18/RxLogs-1.0.18.pom
       - https://maven.columbus.heytapmobi.com/repository/releases/com/github/umair13adil/RxLogs/1.0.18/RxLogs-1.0.18.pom
       -  Required by:
         project :app > project :flutter_logs

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

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

BUILD FAILED in 2m 53s
Exception: Gradle task assembleDebug failed with exit code 1

@ikramakro  i thought i fixed this, what version of flutter_logs are you on please?
see https://github.com/umair13adil/flutter_logs/issues/55
thanks


Some fields are valid to supply when inserting, but are not allowed to be updated.

I ran into this issue when creating an object via Insert and then updating it later via Update. One of the properties is an id pointing to a parent object, and the property cannot be edited after its created (this is just because of a setting on the object in salesforce). Maybe we could add another attribute like SalesforceInsertOnly or something similar to deal with this situation. I don't know if thats the best way to go about it or not. Right now I just set it to null when updating and that works ok for now.

I have been thinking about consolidating the attributes into a single configurable attribute. The individual attributes would still be supported but deprecated.

+1
It becomes difficult with the SalesforceIgnore attribute also affecting the reads.

Yeah I was setting it to null but that broke cuz then the null handling got fixed (setting the salesforce field to null when you pass null) which is obviously good actually.
So I just use different objects for read and write for now.

Currently there is a SalesforceReadonly attribute that might help, but I am currently working on a single attribute that will have configurable options, also making objects cleaner.

is SalesforceIgnore working in the current release? I'm using it, but it isn't ignoring..


Compatiblity With Custom Splash Screen

The early loading screen is looks a bit blank, compatibility with custom splash screen would be crazy good.
"Theres also one called Drippy Loading Screen, but i personally use Custom Splash Screen."

Compatibility with custom loading screen mods isn't very feasible given how fragile the environment the early window runs in.
The ability to use a custom static (or possibly animated) background image is planned though.

Compatibility with custom loading screen mods isn't very feasible given how fragile the environment the early window runs in. The ability to use a custom static (or possibly animated) background image is planned though.

Oh.

Compatibility with custom loading screen mods isn't very feasible given how fragile the environment the early window runs in. The ability to use a custom static (or possibly animated) background image is planned though.

Is this planned FOR 1.20.1 Fabric too?

Is this planned FOR 1.20.1 Fabric too?

It is for all currently supported versions.

Is this planned FOR 1.20.1 Fabric too?

It is for all currently supported versions.

Yay! Is there ETA or is it just planned for now?

Yay! Is there ETA or is it just planned for now?

Just planned for now. It will come when I get time to do so. There's no ETA.

Yay! Is there ETA or is it just planned for now?

Just planned for now. It will come when I get time to do so. There's no ETA.

Got it! Thanks for your timeee :D


#118 LCC metric has impediments

For #118
Problem
LCC metric has impediments. Need to wait for resolving these impediments, add LCC to reports list and cover it by tests.
Work which I did

Added a new class for test IndirectlyRelatedPairs which should work differently on LCC and TCC metrics.
Added new puzzles to fix a bug in LCC.xsl where even number of direct connection calculates wrong.
Fixed title in LCC.xsl.
Fixed a value formatting in TCC.xsl because it doesn't work well with my IndirectlyRelatedPairs.
Recreated the original puzzle about adding to reports list. But without testing part.

P.S.
It is my first PR with PDD.

Job #231 is now in scope, role is REV

Codecov Report

Merging #231 into master will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master     #231   +/-   ##
=========================================
  Coverage     74.56%   74.56%
  Complexity      164      164
=========================================
  Files            31       31
  Lines          1026     1026
  Branches         74       74
=========================================
  Hits            765      765
  Misses          231      231
  Partials         30       30

Impacted Files
Coverage Δ
Complexity Δ

src/main/java/org/jpeek/App.java
93.1% <ø> (ø)
16 <0> (ø)
:arrow_down:

Continue to review full report at Codecov.

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

@yegor256/z everybody who has role REV are banned at #231; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@yegor256/z everybody who has role REV is banned at #231; I won't be able to assign anyone automatically; consider assigning someone manually (as in §19), or invite more people (as in §51), or remove the job from the scope (as in §14)

@SharplEr I believe the branch has problems. Try to run pdd -v -f /dev/null locally.

@yegor256 Try again. Now should work. But looks like @uurl  now works on this task. If my PR no need, I can close it.

This pull request #231 is assigned to @paulodamaso/z, here is why; the budget is 15 minutes, see §4; please, read §27 and when you decide to accept the changes, inform @yegor256/z (the architect) right in this ticket; if you decide that this PR should not be accepted ever, also inform the architect; this blog post will help you understand what is expected from a code reviewercom.zerocracy.Par@3646614d

@rultor merge

@rultor merge

@yegor256 OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 12min)

@elenavolokhova/z please review this job completed by @paulodamaso/z, as in §30; the job will be fully closed and all payments will be made when the quality review is completed

The job #231 is now out of scope

Payment to ARC for a closed pull request, as in §28: +10 point(s) just awarded to @yegor256/z

@llorllale @yegor256 What I'm supposed to review here? The PR has already been merged.

@paulodamaso I'm not the ARC of this project

@llorllale Sorry, I've mixed some projects here.

@0crat quality bad as performer was assigned after PR was already merged and review was not completed as expected.

Quality is low, no payment, see §31

Quality review completed: +8 point(s) just awarded to @elenavolokhova/z


Fixes the contacts 'call button' disappearing on multiresource contacts

This changes the behavior from "last connected resource" or "highest
priority resource" to "most capable resource" regarding the display of
buttons next to this contact. We now check every resource the contact
has connected and we will consider the one with the most capabilities.
This eliminates the very frustrating scenario in which the call
capabilities are disabled on a contact who connected additionally a
non-jingle client, thus resolves #111

I'm going to send in the contributor agreement in the next few days.

Thanks!
How does this behave now for two equally capable resources (e.g. chat)

with the same priority
with different priorities
with different online statuses?

I'm a bit concerned about what happens when e.g. a mobile device resource is online and only chat capable and a desktop resource is call-capable, but away. The contact list shows the highest available online status, thus when you call a contact in this scenario it would ring on the desktop while said callee is potentially not even near his machine.

My intention was to reliably show the call buttons as long as there is such a client connected. This is done by comparing the size of the determined set of capabilities of the resources. The largest one wins. Jitsi/Jitsi-android has 35, while Psi, Adium and ChatSecure have 31. If there are two sets with the exact same size, the first one would win. My assumption here is, that it's most likely the same set. So it shouldn't be affected at all by priorities or statuses, only by resources. The call connects to the highest prioritized call capable resource, even if there is a non-call-capable resource with a higher priority. So the case you described with a lower prioritized call capable resource set on 'away' being 'covered' by a higher prioritized resource set on 'online' is how it would behave. However Jitsi displays the callee's resource which is being called to the caller. And in the extended tool-tips the priority and online status of all resources is listed, so the caller could see the away status of the resource they just called. Then they could send a message which would then be delivered to the callee's mobile device. That should be alright, shouldn't it?
Regarding same priorities and online statuses I noticed a different issue a few days back. I've already posted to jitsi-users [here] (http://lists.jitsi.org/pipermail/users/2015-October/010175.html) (2nd issue). I just noticed this seems to occur only if the two resources use the same priority.
While I was testing your proposed scenario I stumbled upon a certain constellation of resources and priorities in which it doesn't show the buttons, but the mobile indicator. I will look into that as well as in the other issue, but in a different thread.

I can't test and further comment for a couple of days. Please ping me if I don't get back to you by the end of next week. In the meantime, do you think you could make the behavior change optional? I'm not sure yet what would be the default then, but at least it would be configurable.

I can make this optional. I'll introduce a property for this, or did you mean an option in the GUI? I would like to point out, that Pidgin users cannot specify their priorities. Also that Pidgin for Linux implements Jingle.
At the moment I'm still getting some weirdness by Psi on Linux, which I want to iron out.

A GUI option would be ideal. I'm thinking of a checkbox labeled something like "Use all resources when showing a contacts capabilities" in a new advanced configuration section for XMPP (similar to the one for SIP).

I doubled checked the code and tested it thoroughly. However the issue regarding the offline presence on same priority resources caused that weirdness I wanted to iron out. That line here prevents that all caps nodes get removed if a rogue offline presence update comes in. At first I thought of it as a workaround, however after some thought it looks proper to me.
I'm going to look into that presence issue now.
The CLA has been submitted on 17.10.

Seems that presence bug lies here. In case this ends up being exactly 0 again TreeSet will deem them equal and discard one of them.
I will verify this and if true put it into a different pull request.

Okay, thanks, so:

I need to verify the CLA with Emil as I don't have access to Docusign myself.
Please address the inline comments.
Please check your changes for violations of our code convention. There are some lines that are too long, braces on the same line, some missing spaces between operators. (But please don't reformat existing code, so far this PR is exemplar for that!)
Enable your behavior by default. I want to get this into the nightlies to gather feedback.
When you're done, please rebase the PR on master and squash the first three commits into one.
Looking forward to your other PR, it probably shouldn't be a TreeSet<> but rather a SortedList<>. We had some issues with that before when the meaning of Set wasn't really understood.

I'll do all of that.
Regarding the squashing. I haven't done much collaborative work with git as of yet. The purpose of squashing the first three commits is to clean up the commit history since the second and third commit are tiny or should it even all be squashed into one big commit?

The first two commits (151e552f4ee8539f0ac0ba88f1e4a4391f871c44 and 13da0947f8a1a8e7ab9918741c051f51eaa2f7ff) logically belong together, it makes no sense to keep them as separate history on how the code became how it is. The third commit (b121edc96f6db8bf7014058cb8e199317ad1fde6) is a merge. Since this branch is not something other will work on, there's no need to not use rebase.
Same goes for the last commit (ad56640087885f0258a7bb0fad153b8194cc6ab6), you can get rid of that with rebasing (instead of merging).

I've covered every point on the list. However that one inline comment was a tad problematic.

OK. Now everything should be up to code.

Sorry for missing those. This coding style is very different from my own. The next one should be better :)

Merged. Thank you!
Do you want to make an announcement on dev so that people know the difference?

Unfortunately I've missed one test case. This introduced a bug. The offline bug threw me off track here and I falsely blamed it for this (an unhandled exception looks very similar). If a contact actually goes offline, we do not grant him the offline capabilities, which among others is sending offline messages. We can't open the chat window, however we could write, if the window is already open.
I fixed it in this commit https://github.com/459below/jitsi/commit/f393b01befb08b2e974f4e741b3b01d5a30051cb
Annoyingly enough I actually did take it into account [here] (https://github.com/459below/jitsi/blob/f393b01befb08b2e974f4e741b3b01d5a30051cb/src/net/java/sip/communicator/impl/protocol/jabber/OperationSetContactCapabilitiesJabberImpl.java#L574), but not [here] (https://github.com/459below/jitsi/blob/f393b01befb08b2e974f4e741b3b01d5a30051cb/src/net/java/sip/communicator/impl/protocol/jabber/OperationSetContactCapabilitiesJabberImpl.java#L493)

Can you please create a separate PR for that commit?
And please uses a space around operators (and assignments in the future too).


.Net: Rename SKFunction factory methods

The only difference between these two methods should be how the method information is provided, whether it's a single delegate or a combination of a MethodInfo and a target object. This PR thus renames both methods to just be overloads of the same Create method, accepting the same parameters other than the exact ones which specify the method.  It also cleans up the implementation in various ways, removing code duplication, removing extraneous allocation, fixing XML comments, etc.
Fixes https://github.com/microsoft/semantic-kernel/issues/3165
Contribution Checklist

[x] The code builds clean without any errors or warnings
[x] The PR follows the SK Contribution Guidelines and the pre-submission formatting script raises no violations
[x] All unit tests pass, and I have added new tests where possible
[ ] I didn't break anyone :smile:

@stephentoub There are some merge conflicts, can you resolve this and we can get this merged

I've addressed the conflicts.


Apt-vim with fish?

As the title says, I was trying to install apt-vim on WSL using fish shell. I know that we can just adding ~/.vimpkg/bin to our path, but I think adding fish support to the installer would make this project even better.

I would love to support more install environments but am finding myself short or time for ongoing development these days. Would you care to make a PR to include the necessary changes for fish? Thanks!

Oh Im sorry I forgot about this thread :q  Actually If I can devote some time Ill try to make the necesary changes myself (as Its been a long time, I stopped using fish and reverted back to bash but that doesnt really stop me )


Use events to accurately detect swipe start

Use events to accurately detect swipe start.

Added in v0.8


[lc_ctrl] How to structure RndCnst multiplexors

This has been spun out from #10360.

This still has a 1-bit signal to poke (test_tokens_valid[i] == On). What I was suggesting in the meeting was that we'd use the four bits of test_tokens_valid[i] to control the four 64-bit chunks of the signal. That way, a single-bit fault can't flip the token to zero.
Originally posted by @rswarbrick in https://github.com/lowRISC/opentitan/pull/10360#discussion_r792470067

We could slice them, but I am not sure it's needed, and I wanted to avoid introducing another way of consuming the LC signals (after all, we ask that they be consumed with a "strict" comparison in each place where they are needed).
The single bit signal is only combinational at this point, which is difficult to attack with just a glitch.
@cdgori WDYT? Is it worth splitting this into 4 slices that are muxed independently?
Btwy, one thing we could do is make more copies of this valid signal and consume the entire 4bits of the copies to steer, e.g., 2 x 64bit or 4 x 32bit slices of the mux (instead of using the individual bits).
Originally posted by @msfschaffner in https://github.com/lowRISC/opentitan/pull/10360#discussion_r793022820

I think it's okay to leave this one as is.  If someone glitched the valid signal, as you say, they would need to get it to an exact value to have an effect.  If someone were to glitch the mux, they'd still have to attack a few hundred muxes to get the values right.
Even if they did ALL of that, they would still need to find a pre-image value that would then match the new token value.  This all seems very difficult and layered.
let me know if i missed anything.

The thing I'm worried about is that we've got a 1-bit signal that controls 128 1-bit muxes and one input to these muxes is the values that came from OTP. But that's going to be '0 when things haven't been provisioned yet (if I understood Michael correctly). So the attack would be to flip that one bit somehow and then find a SHA-3 pre-image of a single known vector. I don't know how difficult that is, but it doesn't sound completely crazy to me.

Note that the comparison of the token is done three times in different cycles.
Since this is a combo signal, it would therefore have to be glitched in 3 different cycles AND you would have to make sure the glitch propagates to all 128 individual mux cells as @tjaychen pointed out.
However, @rswarbrick is right that the unprovisioned token value is all-zero, which may (?) be easier to find a collision for?
I guess this is a bit of a judgement call. One thing I could do relatively easily is to use two lc signal copies to steer two mux halves separately, for instance.

Ok, in that case, let me add the steering. It should be a minor fix without DV impact.

This issue has been addressed in #10496.

However, @rswarbrick is right that the unprovisioned token value is all-zero, which may (?) be easier to find a collision for?

To my knowledge, I don't think all-zero is easier to collide, though it's possible that more rainbow-table type of things might be available for all-zero output.

Yes what you mentioned is what I was thinking about.
It's probably good to avoid a token value with a nicely aligned value of some sort (all-zero in this case).

i can't completely remember now, but are we running sha3 or kmac when generating the tokens?
I thought it was the latter for some reason...which would mean there's another key to break.
I'm guessing this is only sha3?

We're running cSHAKE128 with a custom function string ('lc_ctrl'). so it is a sha3 variant and does not do any additional authentication. were you referring to the authentication part above?

ah... okay. That's too bad, if we were running kmac I think the collision would be less of a concern since there is yet another constant to break.
If it's actually just cshake it's probably better to not have 0's then.. since i assume the string will be clearly visible in open source.

Yeah right. With the patch above, we're switching the all-zero constant to a RndCnst instead to mitigate that.

Ah, the custom function string basically means no rainbow tables should be pre-generated.  But it's fine to use a RndCnst here to be very safe.


Boto3/botocore lakeformation grant_permissions attribute valid value documentation error.

Describe the bug
https://boto3.amazonaws.com/v1/documentation/api/latest/reference/services/lakeformation.html#LakeFormation.Client.grant_permissions
Issue with Boto3 Lakeformation documentation. grant_permissions "Permissions" parameter valid values are DESCRIBE and ASSOCIATE, which are documented as "DESCRIBE_TAG" and ASSOCIATE_TAG", upon usage causing below error.
Steps to reproduce
import boto3
lfc = boto3.client("lakeformation")
response = lfc.grant_permissions(
CatalogId='**********',
Principal={
'DataLakePrincipalIdentifier': 'arn:aws:iam::***********:role/lake-creator-role'
},
Resource={
    'LFTag': {
        'CatalogId': '='**********',',
        'TagKey': 'security-level',
        'TagValues': [
            'sec-1',
            'sec-2',
            'sec-3'
        ]
    }

},
Permissions=[
    'ASSOCIATE_TAG',
]

)
InvalidInputException: An error occurred (InvalidInputException) when calling the GrantPermissions operation:  Please grant only valid Lake Formation permissions. [ASSOCIATE_TAG] are not all valid Lake Formation permissions.
Expected behavior
Documentation need fix./botocore/botocore/data/lakeformation/2017-03-31/service-2.json

Hi @stthoom,
Thanks for reaching out!  I looked at the lakeformation model and it appears ASSOCIATE_TAG, along with a few other options, were added on 5/7/2021.  I would make sure your boto3 version is 1.17.69 or higher and that your botocore version is at 1.20.69 or higher.  Hope this helps!

If we use Permissions=['ASSOCIATE_TAG'], the grant_permissions fails as above. Able to execute the grant_permissions with Permissions=['ASSOCIATE']
We have been using below.
boto3                               1.17.89
botocore                            1.20.89

Hi @stthoom,
Thanks for clarifying.  And thanks for pointing this out— This is definitely strange behavior, as the permission list contains ASSOCIATE_TAG and not ASSOCIATE as a value.  Would you be able to send debug logs?  If so, just add boto3.set_stream_logger('') to your code and please obscure any sensitive information.  Thanks!

LF_BOTOCORE_ERROR_LOG.txt

P49159160

Hi @stthoom,
Just wanted to give you a heads-up that it appears the Lakeformation team is still working on this and that I'll be moving this to our shared SDKs repository for tracking since this issue is not specific to botocore.  Please let me know if you have any questions!


Add swap button to locality/year of coral cover plot

Add button which swaps the x axis and group of the coral cover plot

Done:
Commit 9b12a991c89f9dd3bd4f6589c0924cdf876cd175


iterating over page.$(selector)?

Hello there,
I'd love to be able to iterate over multiple elementHandles, but cannot fathom how to do so. Are there any plans to extend selector evaluation functionality so that we can iterate over results?
I'm trying to do:
const divs = await page.evaluate(() => {
    return Array.from(document.querySelectorAll('div'));
});

As a workaround, but I cannot find a way to convert the items in divsinto elementHandles, and can't do elementHandle.hover()

This is similar to #302. I'd also would love to have page.$$ for the document.querySelectorAll.

@rcarmo The approach you're taking isn't possible because of the separation between your script and the context in which evaluate is running. evaluate is similar to calling a script in the Chrome console, as such when the result from this function returns, it has to be serialized and sent back to your script as primitive values, or basically anything which JSON can serialize (numbers, strings, booleans, nulls etc) but not Elements and or the DOM.
So for your example, you can do all the work you need on the element inside the evaluate context and return the result to your script:
let content = await page.evaluate(() => {
  let divs = [...document.querySelectorAll('div')];
  return divs.map((div) => div.textContent.trim());
});

@ivanvanderbyl but the result doesn't seem to be an array of elementHandles... well, I'll keep fiddling.

I'm using this solution
it's not elegant, it's not fast, it left a dirty custom attribute on DOM, but allow to use ElementHandle as page.$ does
  async function $$ (page, selector) {
    const ids = await page.evaluate((selector) => {
      const list = document.querySelectorAll(selector)
      const ids = []
      for (const element of list) {
        const id = selector + ids.length
        ids.push(id)
        element.setAttribute('puppeteer', id)
      }
      return ids
    }, selector)
    const getElements = []
    for (const id of ids) {
      getElements.push(page.$(`${selector}[puppeteer=${id}]`))
    }
    return Promise.all(getElements)
  }

// ...

const anchors = await $$(page, 'a')
for (const anchor of anchors) {
  anchor.click()
}

Closing in favor of #382.


Aparapi and Ray Casting (Ray Tracing)

From @macroing on September 17, 2015 9:23
Hello!
I've used Aparapi for a while now and I really like it. The project I've been working on is an open source realtime Ray Caster (Ray Tracer).
But now I'm interested in hearing your input on Aparapi- / OpenCL specific optimizations for a project like this. Would it be a good idea to use the local and / or global buffer annotations? Or do you have any other ideas?
In case you're interested in the project, you can find it here: https://github.com/macroing/OpenRC
Copied from original issue: aparapi/aparapi#11

From @SubaruWRC on September 17, 2015 16:6
I hate to say this, but it really depends on your computation/workload. Have you looked at any of the samples/examples on Github to see if they match your use cases?
On September 17, 2015 2:23:18 AM PDT, macroing<EMAIL_ADDRESS>wrote:

Hello!
I've used Aparapi for a while now and I really like it. The project
I've been working on is an open source realtime Ray Caster (Ray
Tracer).
But now I'm interested in hearing your input on Aparapi- / OpenCL
specific optimizations for a project like this. Would it be a good idea
to use the local and / or global buffer annotations? Or do you have any
other ideas?
In case you're interested in the project, you can find it here:
https://github.com/macroing/OpenRC

Reply to this email directly or view it on GitHub:
https://github.com/aparapi/aparapi/issues/11

--
Sent from my mobile device. Please excuse any typos or autocorrect mistakes.

From @macroing on September 17, 2015 16:35
Okay I see. Yes, I looked at some of the examples. I even based the initial code on the approach used by the Fractal example.
What concerns the computation or workload, then I guess it's quite heavy. The more rays the Ray Tracer "fires" per pixel, the more workload per pixel. Then there's also quite a few pixels to process.


 I don't know if this happens with other animals too.

Going to retest this this weekend.  I think it is fixed in the lastest version but I didn't test for this error in the last release.
It would grow when a player used bonemeal but only flowers.   It was actually crashing if a player does it too but the crash exception is caught for players.

Okay I've confirmed this issue is fixed in the last release.  Thanks for your bug report!

This was fixed but had not closed it.  So I reconfirmed it is still fixed.
Confirming this is fixed.   Ran a 24 hour test with pigs on a mixture of grass and overgrown blocks from BYG.   Grassblocks grew, overgrown blocks got some flowers.   No crashes.
Thanks for your issue report.


Revert "Revert "Created scheduled classes table""

@Hydrohaven @h0ethan04

Our actual PR now is to revert your reversion so that our original changes are reflected
[our current branch is now technically behind dev with no new commits that can be merged]

cascading delete on foreign key should be completed now


Unable to download data having size more that 20mb on IE11

Team,
Good Morning/Evening !
I am using Trusted authentication for my users to  get authenticated, when my users are trying to download data using the Export all Extension(over 20mb file) on IE11, it spins for 2~3 minutes(wont download)and tries to refresh the page with same URL string (throwing an error "Could not locate unexpired trusted ticket error". Would someone please help me if there is way to tweak the code for the application to download larger files on IE.
Thanking you in anticipation.
Please.. Please

Closing out - this would actually be a support question for the authors of the Export All extension.


Encrypt & decrypt does not dynamically take any length strings.

cypher_encrypt() and cypher_decrypt() wants a byte array with a length of 16 (AESbyte input[16];) I want it to take any length of string as an input and not freak-out when it isn't the exact length to fill those 16 bytes.

Fixed as of 1/26/22


Select only date?

is it possible? I want to disable the time selection entirely.. not sure if I should a different library only for this..

I was also confused by the same problem :-) and please allow me to ridicule the instruction.
set the option "minView:'month'" to shutdown the time selection.
like this:
$("#datepicker").datetimepicker({format:'yyyy-mm-dd',language:'zh-CN',startView:'decade',autoclose:true,minView:'month'})
sorry about the auto translation and no proper English :-(

Great, think that'd work :)

Worked for me as well. Thanks.


Outdated documentation about tsvector columns

The section Using tsvector columns in the README seems outdated.
Now you can create an index directly on a function of the column, instead of using triggers:
https://www.postgresql.org/docs/current/textsearch-tables.html#TEXTSEARCH-TABLES-INDEX

Yes, this has always been true. We have documentation in the wiki about creating indexes based on expressions that call functions.
But there are some operations that, even with an index, re-evaluate the tsvector expression. Since this can be slow, many prefer to use tsvector columns.


Trim title before insert/update to database to match the size requirements of database

Fix #32489

I was unable to create a backport for 1.22. @lunny, please send one manually. :tea:
go run ./contrib/backport 32498
...  // fix git conflicts if any
go run ./contrib/backport --continue


Sheet Helpers - sort

Wrote two subs to sort worksheets either ascending or descending, as part of sheet helping.

This look good.  It might be worthwhile to combine the two methods and use a YesNoCancel to decide which direction to go.  I'll bring it in now.


[SPARK-48144][SQL] Fix canPlanAsBroadcastHashJoin to respect shuffle join hints

What changes were proposed in this pull request?

Currently, canPlanAsBroadcastHashJoin incorrectly returns that a join can be planned as a BHJ, even though the join contains a SHJ.
To fix this, add some logic that checks whether the join contains a SHJ hint before checking if the join can be broadcasted.
Also made a small refactor to the JoinSelectionHelperSuite to make it a bit more readable.

Why are the changes needed?

canPlanAsBroadcastHashJoin should be in sync with the join selection in SparkStrategies. Currently, it is not in sync.

Does this PR introduce any user-facing change?

Yes, semi / anti joins that could not have been planned as broadcasts would now not be pushed through aggregates anymore. Generally, this would be a performance improvement.
How was this patch tested?

Added UTs to check that a join with a SHJ hint is not marked as being planned as a BHJ.
Added tests to keep canPlanAsBroadcastHashJoin and the JoinSelection codepath in sync.

Was this patch authored or co-authored using generative AI tooling?

No

Gentle ping, @fred-db .

@dongjoon-hyun created the refactor PR here https://github.com/apache/spark/pull/46525. Let me know what you think! :)

Thank you so much.

I merged the following. Could you rebase once more, @fred-db ?

https://github.com/apache/spark/pull/46525.

Thanks @dongjoon-hyun ! :) Rebased the code.

Merged to master for Apache Spark 4.0.0.
Thank you, @fred-db , @agubichev,  @cloud-fan .


small updates

small updates for quick usability

hey @LayerRadio thank you for the PR. would it be possible to re-apply these changes to the new main branch? it has been updated heavily, so it will probably be easier to do that than resolving merge conflicts.

updated here: https://github.com/d1onys1us/dapp-slaps/pull/5


Added unit test test_truth_game.py

Added unit test test_truth_game.py to test TruthGame class in main.py
Note:

install all the packages in venv before running pytest test_truth_game.py
I am getting one warning because discord.py library, which uses a module called audioop. This module is going to be removed in Python 3.13, but since I'm currently using Python 3.12, the warning doesn't affect the code and can be ignored for now.

Edit: I've put the last two line of main.py:
load_dotenv()
bot.run(os.environ['TOKEN'])

in if __name__ == "__main__": block so that main doesn't run when it is imported in test_truth_game.py

great work it test all the basic game logic but can you look into testing discord bot logic aswell?
Oh! I'll do, I was gonna got it in parts anyway.
add the pycache and .pytest_cache in the .gitignore
that ii gets created while running pytest test_truth_game.py or any other test for that matter, right?
add the required lib in the src/requirement.txt
the only lib that I had to install were discord and python-dotenv, and they are already mentioned.


Fix Telemetry disablement matching

Fixes https://github.com/istio/istio/issues/45292

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-security-multicluster_istio
cedfac9fbd27cca35d16358a54770afa10f3365c
link
unknown
/test integ-security-multicluster

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

In response to a cherrypick label: new issue created for failed cherrypick: #45301

In response to a cherrypick label: new pull request created: #45302

In response to a cherrypick label: new pull request created: #45303


have a error

Can you compatible with node v16 ? thanks
<EMAIL_ADDRESS>The engine "node" is incompatible with this module. Expected version ">= 18.0.0". Got "16.20.0"
error Found incompatible module.

Fixed!


WFLY-13163 Upgrade smallrye-open-api to 1.2.1

https://issues.redhat.com/browse/WFLY-13163

retest this please


Issues with API Key

Hi, I've been following this guide, however I have run into an issue at Step 6 where I am unsure which API Key I am supposed to use in the URL. Do I use the standard API Key provided with the bbox information, or the Rest API Key I noted down in Step 2, or both? And do I just import one of the two blueprints included here? Or make my own? Any help would be greatly appreciated.
Thanks

You should be using the API key you create in Step 2 on the Here.com site, this key is unique to you and should not be shared.
There are four blueprints but you should use only one.
Please Note that the Twitter API has changed and none of them will Tweet without additional work on Twitter (now X), which is not documented in this guide sorry.

I'm also struggling to make this work so the question and answer are helpful.  Can you point to advice on what extra work needs to be done on Twitter?  Thanks

Thanks for your reply, I've put my API Rest Key in now, but it's still not working unfortunately. I think the issue is that it's not interacting with Twitter

I've tried both V6 and V5 of Twitter but it still doesn't work.

I can't get the API call to HERE for the traffic info to work.  My api key will work for the geo data examples in HERE, but not for the traffic calls.  I found a blog here that implies you need to ask especially for access to traffic data. https://www.here.com/learn/blog/traffic-analytics-speed-data
But this wasn't mentioned in the guide for the traffic bot, so I don't know if this really is the problem.  I have sent in a request on the HERE contact formand I will let you know what happens.

This REPO was created 4 years ago and is no longer maintained I'm afraid, so I'm not surprised HERE and Twitter have changed since then.
For twitter (X) you now have to create a specific BOT account with a developer API request for example.
For HERE there is now a newer v7 API as I understand.
This REPO is only for reference as to how it was achieved 4 years ago.

Thanks for the clarification.

I have just had a video call with HERE support.  They said that they can provide data on what the speed limit is on a particular stretch of road.  They do have anonymised data on the actual speed of traffic but that this is only available to large organisations at a cost of hundreds of thousands of pounds.  They also said that they have received about 50 calls from the UK on this exact topic, all stemming from the article in the Times.  Their view is that the article and instructions are a bit misleading as the data is not available to the public.  I can only tell you what they told me.  This would explain why I get an authorisation/access denial when I try the API call.

I have just had a video call with HERE support. They said that they can provide data on what the speed limit is on a particular stretch of road. They do have anonymised data on the actual speed of traffic but that this is only available to large organisations at a cost of hundreds of thousands of pounds. They also said that they have received about 50 calls from the UK on this exact topic, all stemming from the article in the Times. Their view is that the article and instructions are a bit misleading as the data is not available to the public. I can only tell you what they told me. This would explain why I get an authorisation/access denial when I try the API call.

The API call used is not to provide the speed limit but to get the average speed in the area. The users must confirm from the data returned the Road Location and Confidence Level as both have a bearing on the results.

This REPO is many years old now and back when it was first created someone raise issue #1
We contacted HERE to confirm the following https://github.com/BerkshireCar/SpeederBot/issues/1#issuecomment-901182663
I just tested the API call below and it returned results okay.
https://traffic.ls.hereapi.com/traffic/6.1/flow.json?bbox=51.3631,-0.8986;51.3590,-0.8942&apiKey=YOURKEY

Thanks for such a rapid reply. I know that the API call is to get the average speed, and not the speed limit, but when I spoke to HERE support they insisted that average speed data was not available. Which I thought was odd, given that they have examples for getting the average speed.
I have tried the two examples you gave for v6.1 and v7.  The v6.1 gives me the error I have seen before - But the v7 version is returning me
{"sourceUpdated":"2024-10-21T13:26:28Z","results":[{"location":{"description":"B3016/Longwater Road","length":1808.0,"olr":"CCkBEAAlJP9fAySD0gAJBQQCAzwACgUEAo4cAAn9/9YACQUEAgO/ADAAAA=="},"currentFlow":{"speed":13.611112,"speedUncapped":13.611112,"freeFlow":13.888889,"jamFactor":0.2,"confidence":0.7,"traversability":"open"}},{"location":{"description":"A4 at Reading","length":18134.0,"olr":"CCkBEAAlJP9hdiR/ZAAJBQQCA/MACgUEA8cjAPIeHFEACQUEAwNxADAAAA=="},"currentFlow":{"speed":11.388889,"speedUncapped":11.388889,"freeFlow":14.166667,"jamFactor":1.7,"confidence":0.92,"traversability":"open"}},{"location":{"description":"A327","length":21.0,"olr":"CCgBEAAkI/9e+SSD0wAJBQQCBEYACgQDAhUAABX//QAJBQQCBMwAMAAA"},"currentFlow":{"speed":8.055555,"speedUncapped":8.055555,"freeFlow":10.555556,"jamFactor":2.2,"confidence":0.7,"traversability":"open"}},{"location":{"description":"A327","length":1836.0,"olr":"CCkBEAAlJP9jqiSDvgAJBQQCA78ACgUEAo44APXuAC0ACQUEAgRpADAAAA=="},"currentFlow":{"speed":13.055556,"speedUncapped":13.055556,"freeFlow":13.611112,"jamFactor":0.4,"confidence":0.77,"traversability":"open","subSegments":[{"length":1416.0,"speed":13.333334,"speedUncapped":13.333334,"freeFlow":13.333334,"jamFactor":0.1,"confidence":0.77,"traversability":"open"},{"length":420.0,"speed":12.222222,"speedUncapped":12.222222,"freeFlow":14.166667,"jamFactor":1.2,"confidence":0.77,"traversability":"open"}]}},{"location":{"description":"Coopers Hill","length":18048.0,"olr":"CCkBEAAlJP9a7SSMqAAJBQQDBAQACgUEA8hDAA4F44oACQUEAgPzADAAAA=="},"currentFlow":{"speed":12.222222,"speedUncapped":12.222222,"freeFlow":14.166667,"jamFactor":1.2,"confidence":0.92,"traversability":"open"}}]}
which looks a lot like your data above.
So now I have something that works, thank you very much. 😊😊
I don't know why the v6.1 call doesn't work, but it doesn't matter so long as the v7 call works!
Again, thanks for your help.


Native way to send http request in PHP

I was unpleasantly surprised when I've realized that I need composer to install influxdb driver.
influxdb-php depends on external code like Guzzle and uses very little functionality of it.
I believe that drivers should be installed by coping files or with only git clone command.
This PoC implementation based on file_get_contents function for writing and querying data.
Probably I should rewrite this code to allow testing with mocks. Let me know if it nessesary.
Now I suggest only optional driver.
But I suppose it can be default way to use influxdb over http after more testing.
$client = new InfluxDB\Client('<IP_ADDRESS>', 8086);
$client->setDriver(new InfluxDB\Driver\PlainPhpHttp($client->getBaseURI()));

Note that file_get_contents can be disabled by allow_url_fopen in php.ini.
Some sites recommend disabling it http://phpsec.org/projects/phpsecinfo/tests/allow_url_fopen.html as to prevent vulnerabilities.


addpkg: python-ply 3.6-1

Add as dependency in the python-cffi chain, preparing for pyopenssl and other cffi-based packages.

Why not add this packages to mingw instead?

Ah... Actually I don't know when to put into MSYS2 and when for MinGW.

MSYS packages in most cases needed for build tools that helps to build mingw packages. Our primary target is MINGW. MSYS is designed to simplify build process under Windows.

I see, thanks for the info. I'll send another PR to add the packages to MinGW, sorry!


Update openfpga.sh

Motivate of the pull request

[X] To address an existing issue. If so, please provide a link to the issue:
[ ] Breaking new feature. If so, please describe details in the description part.

Describe the technical details
What is currently done? (Provide issue link if applicable)

The create-task command gives the error message "Template project [template_tasks/yosys_vpr_template] does not exist" when no template task is specified. Apparently, the default template for the create-task command has not been updated.
What does this pull request change?

I changed the value of variable template in openfpga.sh to template_tasks/fabric_netlist_gen_template.

Which part of the code base require a change

[ ] VPR
[ ] Tileable routing architecture generator
[ ] OpenFPGA libraries
[ ] FPGA-Verilog
[ ] FPGA-Bitstream
[ ] FPGA-SDC
[ ] FPGA-SPICE
[X] Flow scripts
[ ] Architecture library
[ ] Cell library
[ ] Documentation
[ ] Regression tests
[ ] Continous Integration (CI) scripts

Impact of the pull request

[ ] Require a change on Quality of Results (QoR)
[ ] Break back-compatibility. If so, please list who may be influenced.

@ganeshgore Would you mind to give a code review here since you are the author of the openfpga.sh? Thanks!

looks good by default it will create the fabric_netlist_gen_template task.


Aswathy/Deriv P2P section in help-centre page is not hidden for EU clients

Changes:

Deriv P2P section in help-centre page is not hidden for EU clients

Type of change

[ ] Bug fix
[ ] New feature
[ ] Update feature
[ ] Refactor code
[ ] Translation to code
[ ] Translation to crowdin
[ ] Script configuration
[ ] Improve performance
[ ] Style only
[ ] Dependency update
[ ] Documentation update
[ ] Release

PR is changed to https://github.com/binary-com/deriv-com/pull/2736


Visual mode doesn't go to the opposite direction if start from blank line

I found a rather strange issue when starting visual mode from a blank line. If I move the cursor up and then down pass the starting line, visual mode goes away. Here's an example:

Here's the expected behavior in Vim, which keeps the visual mode when the cursor goes in opposite direction.

I am wondering which software should I use to record my action like this so that I can report my bug conveniently as well.

As stated in the README, this package is no longer maintained and is deprecated. We recommend that people use the vim-mode-plus package instead. Because of this, we are archiving this repository and closing all issues and pull requests. Thanks very much for your support and contributions!