text:
[SPARK-9308] [ML] ml.NaiveBayesModel support predicting class probabilities

Make NaiveBayesModel support predicting class probabilities, inherit from ProbabilisticClassificationModel.

Merged build triggered.

Merged build started.

Test build #38465 has started for   PR 7672 at commit c07e7a2.

Test build #38465 has finished for   PR 7672 at commit c07e7a2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

It looks like a straightforward port of the .mllib code, so LGTM

@jkbradley

That's all for now.  I think you can eliminate a lot of duplicated code, but please say if some code turns out to be hard to reuse.  Thanks!

Merged build triggered.

Merged build started.

Test build #39050 has started for   PR 7672 at commit 3ee56d6.

@jkbradley I have reply your comments inline and update this patch.

Test build #39050 has finished for   PR 7672 at commit 3ee56d6.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

The only real issue I see is that raw2probabilityInPlace should operate in-place. (I missed that before!)

Merged build triggered.

Merged build started.

Test build #39164 has started for   PR 7672 at commit 25e224c.

LGTM, pending tests.  Thank you!

Test build #39164 has finished for   PR 7672 at commit 25e224c.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Merging with master.
@yanboliang Could you please make a JIRA for adding Python support for specifying the rawPrediction and probability cols?  Thanks!

authors: AmplabJenkins SparkQA jkbradley srowen yanboliang


text:
[STORM-2442]modify the Usage Examples in storm-kafka-client's README.md

https://issues.apache.org/jira/browse/STORM-2442
The Usage Example in storm-kafka-client's README.md is Incorrect in some place.For example, This variables ,“kafkaSpoutConfig,kafkaSpoutStreams,kafkaConsumerProps,tuplesBuilder,retryService”, should be defined before it is used.And I think "props" should be named kafkaConsumerProps as there is a Map named kafkaConsumerProps .

+1 Nice catch.

Hello, @HeartSaVioR
Shall you merge this PR?And need I close this PR?

source: gharchive/pull-request

authors: HeartSaVioR liu-zhaokun

repo: apache/storm

license_type: permissive

license_source: github-api


text:
[db specific] Big number aggregations show undefined in Athena

Hi,
While drawing a basic big number chart, I got an undified output although data is a defined number (16 here) . Please see the screenshot below.

I am experiencing this bug with athena datasets, and with all aggregation functions (MAX, SUM, MIN, MAX, AVG, COUNT_DISTINCT). No issues with postgres datasets though.
I am using the current latest image (Digest:sha256:3d9c6413c0d4bf0f11feefbb2636d96cbafd1158dc6fade4a3a0970a69bf1d27), and the version in the front interface is 0.999.0dev.
Thanks

@jafournier thanks for reporting! we currently don't have a good plan to support different drivers in all product aspects. If you have a solution already, we will make sure the PR is reviewed and merged.

source: gharchive/issue

authors: jafournier junlincc

repo: apache/superset


text:
Hash mismatch error during build part of docker installation

Bug description
107.2 E: Failed to fetch http://deb.debian.org/debian/pool/main/l/lame/libmp3lame0_3.100-6_amd64.deb  Hash Sum mismatch
107.2    Hashes of expected file:
107.2     - SHA256:b1292c749172e7623547ecf684da57d3ec6ca22109f08b11bbb9e6be6e6beb95
107.2     - MD5Sum:ab2ccd68809db0713589f90b8ab91e5e [weak]
107.2     - Filesize:364932 [weak]
107.2    Hashes of received file:
107.2     - SHA256:a1329e350ff953cdf5dd4262255fbef935b4f9cbc62afbf9525eb79b6f4716eb
107.2     - MD5Sum:bb2871be1679b04af609fb3b84d83b9d [weak]
107.2     - Filesize:364932 [weak]
107.2    Last modification reported: Wed, 28 Sep 2022 09:20:07 +0000
107.2 E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
107.2 Failed to install browser dependencies
107.2 Error: Installation process exited with code: 100
------
failed to solve: process "/bin/sh -c playwright install-deps" did not complete successfully: exit code: 1

How to reproduce the bug

Follow the instructions at https://superset.apache.org/docs/installation/docker-compose/#installing-superset-locally-using-docker-compose
$:~/superset$ git rev-parse HEAD
6bc85678021c888feecd4b0c44092e833376ddd8
$:~/superset$ git describe --tags
superset-helm-chart-0.12.11-457-g6bc8567802

Screenshots/recordings
No response
Superset version
master / latest-dev
Python version
I don't know
Node version
I don't know
Browser
Not applicable
Additional context
similar https://github.com/apache/superset/issues/28165
Checklist

[ ] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[ ] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Thanks bot, updating did indeed clear the error.


text:
SESSION_REFRESH_EACH_REQUEST parameter is not working with sql queries run in sqllab

SESSION_REFRESH_EACH_REQUEST parameter is not working with sql queries run in sqllab.
We have setup SESSION_REFRESH_EACH_REQUEST in superset config to True to renew PERMANENT_SESSION_LIFETIME after each query in Sqllab.
Expected results
We expect that via setup SESSION_REFRESH_EACH_REQUEST = True , the session lifetime will be renewed with each sql query action in sql lab.
Actual results
At this moment we have configured
PERMANENT_SESSION_LIFETIME = 1800
and SESSION_REFRESH_EACH_REQUEST = True but these two parameters are working together when (in the 30 min time window) we e.g. change the tab in superset. When we are working in SQL Lab the session expires after 30 mins no matter how many queries are executed.
Environment
(please complete the following information):

superset version: [0.28.1]
python version: Python 3.6.8

Checklist
Make sure these boxes are checked before submitting your issue - thank you!

[ X] I have checked the superset logs for python stacktraces and included it here as text if there are any.
[X ] I have reproduced the issue with at least the latest released version of superset.
[X ] I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context
Add any other context about the problem here.

It still doesn't work under superset 1.2.0. expected expiration time for cookie session after using PERMANENT_SESSION_LIFETIME and SESSION_REFRESH_EACH_REQUEST
I saw the code from Flask where it must make session.permanent = True to get expiration time. see https://github.com/pallets/flask/blob/a430c43736ab029b472c9641aa0b6203638391c2/src/flask/sessions.py#L264-L274
So I wonder if this is something can be done in superset codebase

commented in https://github.com/apache/superset/issues/5149#issuecomment-899942147 and please checkout #16286 to see how to setup session.permanent by using FLASK_APP_MUTATOR.


text:
LDAP Connection Superset

Is your feature request related to a problem? Please describe.
I was trying to connect more than one domain on my Superset, but I think Superset does not permit that. When I try to connect more than one LDAP SERVER the Superset doesn't accept because on his source code he just accept one parameter.
Describe the solution you'd like
Ask for a option to add more than one domain on Superset.
Describe alternatives you've considered
Superset just permit us to connect just one LDAP connection with the parameters below:
AUTH_LDAP_SERVER = ""
AUTH_LDAP_USE_TLS = False
AUTH_LDAP_BIND_USER = ""
AUTH_LDAP_BIND_PASSWORD = ""
AUTH_LDAP_SEARCH = ""
AUTH_LDAP_UID_FIELD = ""
AUTH_LDAP_FIRSTNAME_FIELD = ""
AUTH_LDAP_LASTNAME_FIELD = ""
If we can use a separition to connect one more domain, ou many others, separating them with a space or a comma it would be very useful.

Hi @ziusware,
This is more of a FAB question, since the LDAP auth is performed by it. Feel free to open and issue there.

Hi @bharath0208,
I'm having the same problem, ldap is running and can query it from my local machine and docker, however when try from kubernetes cluster, cannot connect to ldap server.
Did you find any solution?

authors: chcsilva0 dpgaspar ziusware


text:
chore: Improves the Select component UI/UX - iteration 2

SUMMARY
Improves the Select component UI/UX - iteration 2.
Storybook changes:
At Every Corner

Adds a text explaining the objective of this panel
Increases the selects width

Async Select

Allows the user to simulate a slower connection
Displays the dispatched requests
Decreases the select width

Interactive Select

Decreases the select width

Select component changes:

Fixes a bug where the paginated scroll keeps requesting data if the user scrolls down and there is no more data available
Moves debounce from handleFetch to handleOnSearch
Renames the select

Improvements/tasks that will be done in the next iterations:
Async Select

Make it more clear that the select is loading while scrolling
Improve the error handling

Interactive Select

Add the remaining properties
Hide the options control
When allowNewOptions is true, showSearch should be true
Show radio group with no header, text header, and ControlHeader

Select component

Check/Discuss whether we need the onPaste and on closeOnScrollOut props
Remove the usage of any from the implementation
Our interface should only expose single and multiple modes
Paginate a few px before the bottom of the scroll for better UX
Investigate why there are two useEffects with very similar dependencies and the same code
Manual testing
RTL tests

@geido @villebro @rusackas @junlincc @kgabryje The component continues to be isolated from the rest of the application. Only available in the Storybook. You don't need to test this PR, this will be done in the final iterations. The idea here is to share the current state of the work and give the opportunity to interact with the component and visualize potential improvements.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
https://user-images.githubusercontent.com/70410625/122447287-f696c300-cf79-11eb-8528-dc1a0e24f53f.mov
https://user-images.githubusercontent.com/70410625/122447300-fa2a4a00-cf79-11eb-951c-4a7892dd4fa5.mov
TESTING INSTRUCTIONS
Use the Select storybook to explore all the available options.
ADDITIONAL INFORMATION

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

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

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

/testenv up

For reference, the prior iteration is here: https://github.com/apache/superset/pull/15121

@villebro About the "Create" when using allowNewOptions... I think @geido had a reason to not add this but I can't remember right now. @geido Do you remember?

Hi @villebro @michael-s-molina . The reason not to have the "Create" is because that would be inconsistent with the defaut Antd behavior which just presents you with the value. Changing the default behavior comes with an implementation cost and we did not see the added benefit for the end user very clearly. As long as the user can create new options, it should not matter whether he is creating one or picking an existing, unless you have a different opinion.

authors: geido michael-s-molina pkdotson rusackas


text:
feat(docker-compose): add TAG option

SUMMARY
This PR adds a new environment variable TAG to both docker-compose configs to make it possible run a specific tag. In addition, the related doc changes from #18196 are copied over to the new docs site (forthcoming) to keep them in sync with the current docs.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

Checkout an old release, e.g. 1.4.0
Apply the changes from this PR to the docker-compose yaml files
run TAG=1.4.0 docker-compose -f docker-compose-non-dev.yml up and watch the 1.4.0 version start up successfully

ADDITIONAL INFORMATION

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

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

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

Much needed enhancement. Loved it..

authors: sujiplr villebro


text:
chore: Convert QueryAutoRefresh to TypeScript functional React component

Convert QueryAutoRefresh to TypeScript functional React component
SUMMARY

This PR converts QueryAutoRefresh from es6 class component to TypeScript functional component as part of bigger effort to migrate frontend code to TypeScript and functional React components defined in: https://github.com/apache/superset/discussions/18388
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

There should be no visual change to the application
TESTING INSTRUCTIONS

Open SQL Lab / SQL Editor
Click the "RUN" button
Ensure Query runs and updates results with same behavior that existed prior to this PR
Test with both default behavior and asynchronous query execution on for a database

Changes to http requests for getting Query statuses:
If you watch the dev tools network tab you should see less network traffic as the execution now ensures only one outstanding http call to check query status is made at a time to avoid http response race conditions that can lead to incorrect application state and to reduce tandem network calls on slower connections.  If the call fails, the offline state change will be triggered but the interval timer will continue attempting to reconnect and set user online and show results once the connection is restored.  This can be tested by:

Opening the dev tools / Network / set the connection from "No Throttling" to "Offline", 2. Click the "Run" button as described in the initial test steps above
See the network failure and the UI will display an "Offline" pill (this is not new UI behavior)
Set the network back to "No Throttling" and wait a few seconds and the next interval will make a successful query status API call and you will see data results again.

QueryAutoRefresh was separated into two files to separate Redux knowledge from the simple functional component:

QueryAutoRefresh/index.ts - Simple functional component with no knowledge of Redux
QueryAutoRefresh/QueryAutoRefreshContainer.ts - Functional component container with connection to redux state that imports and contains QueryAutoRefresh/index.ts component

IMPORTANT:
When changing QueryAutoRefresh to a functional component the behavior of setInterval no longer worked correctly.  This is a known issue with functional React components using setInterval can provide stale state / props in the interval callback creating undesired, hard to debug / fix behavior.  A new utility hook (SqlLab/utils/useInterval.ts) was introduced in this PR to handle this based on this very helpful article by Dan Abramov (thank you!): https://overreacted.io/making-setinterval-declarative-with-react-hooks/
ADDITIONAL INFORMATION

[X] Has associated issue: https://github.com/apache/superset/discussions/18388
[ ] Required feature flags:
[ ] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

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

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

@eric-briscoe do you have the pre-commit hook installed? We have it in a makefile. The command is make pre-commit

authors: AAfghahi eric-briscoe


text:
feat(helm): update redis version due to critical CVE (HIGH PRIORITY)

redis's container has critical vulnerability:
Note: CVE-2021-46848
Package: libtasn1-6
Package Type: OS
Affected Version: 4.16.0 2
Fixed Version: 4.16.0 2+deb11u1

SUMMARY

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

ADDITIONAL INFORMATION

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

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

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

@justmike1 I believe you need to run helm-docs to update README.md, as that also has a reference to the Redis version.

@villebro correct, I missed that.


text:
THRIFT-5087: Revert PR1995 (commit f8b004081da)

Fix CI problem
[my guess] The original intent of the chaned line is: if $PYTHON is 3.x, there is no need
to search for another 3.x

[ ] Did you create an Apache Jira ticket?  (not required for trivial changes)
[x] If a ticket exists: Does your pull request title follow the pattern "THRIFT-NNNN: describe my issue"?
[x] Did you squash your changes to a single commit?  (not required, but preferred)
[x] Did you do your best to avoid breaking changes?  If one was needed, did you label the Jira ticket with "Breaking-Change"?
[ ] If your change does not involve any code, add  [skip ci] at the end of your pull request to free up build resources.

Mmmh ... ninja: build stopped: subcommand failed.
https://travis-ci.org/github/apache/thrift/jobs/660828704?

[322/326] Building Java library using Gradle Wrapper
FAILED: lib/java/CMakeFiles/ThriftJava
cd /thrift/src/lib/java && /thrift/src/lib/java/gradlew assemble --console=plain --no-daemon -Prelease=true -Pthrift.version=0.14.0 -Pbuild.dir=/thrift/src/cmake_build/lib/java/build
Exception in thread "main" java.lang.RuntimeException: Timeout of 120000 reached waiting for exclusive access to file: /root/.gradle/wrapper/dists/gradle-5.6.4-bin/bxirm19lnfz6nurbatndyydux/gradle-5.6.4-bin.zip
at org.gradle.wrapper.ExclusiveFileAccessManager.access(ExclusiveFileAccessManager.java:65)
at org.gradle.wrapper.Install.createDist(Install.java:48)
at org.gradle.wrapper.WrapperExecutor.execute(WrapperExecutor.java:107)
at org.gradle.wrapper.GradleWrapperMain.main(GradleWrapperMain.java:63)
Seems unrelated.

Now it seems OK. Some netstd tls feature failure.

authors: Jens-G janosvitok

repo: apache/thrift


text:
Documentation change for Digest Authenticator Valve - spell corrected for attribute algorithm

this change is with respect to issue #66662

Many thanks. I'll do the back-port now.

authors: gohilmca markt-asf

repo: apache/tomcat


text:
TOMEE-2786 Spanish translation for vaadin-vxx-simple example

https://issues.apache.org/jira/browse/TOMEE-2786
I noted that this example documentation emphasizes about using the latest vaadin release available, that currently are  alpha: 14.2.0.alpha6  and stable versions: 14.1.18  and  15.0.0
But the pom.xml file is using 14.0.0.rc1 updated about ~9 months ago by  commit 9fd13f96809
Would we update vaadin version for the examples as well at this time?
Ref: https://github.com/vaadin/platform/releases

@cesarhernandezgt may you take a look of this PR?

@emecas
Hi, I agree and I vote +1 on update from vaadin 14.0.0.rc1 to 14.1.18.
Also if there is no braking change, 15.0.0 sounds like a more appealing version to use :).

@cesarhernandezgt @Daniel-Dos  Thank you. I will add soon a new full example using the most recent&compatible Vaadin version available.

very good :  )

authors: Daniel-Dos cesarhernandezgt emecas

repo: apache/tomee


text:
Inconsistent timer view when using quartz persistence

In TomEE timers are stored twice. Once in the TimerStore and once in the quartz scheduler. Quartz itself may use in memory or database storage. It is hard to keep both stores in sync, especially if database persistence is used in quartz and TomEE is restarted. This leads to inconsistencies.
This pull request tries to avoid the inconsistencies by removing one storage location (TimerStore).

I like the idea but think it doesnt work cause we need to handle transactionality there so we need to enhance TimerStore to rely more on quartz outside of transactions, no?

I am not sure if I really understood the question. But I see three cases:

Manipulation of persisted timers within a transaction. This should
be handled perfectly using persistent quartz timers, since the
database connection takes part in the transaction.
Manipulation of persisted timers outside a transaction. This might
fail. But I am not sure what the EJB specification says about this
and if it even makes sense to do so.
Manipulation of non persisted timers. Here my current patch seems to
be overkill (unless if running in a cluster environment), since
timers are persisted and deleted during restart. I like the idea of
an independent Quartz-Scheduler for non-persistent timers.

On 19.05.2017 00:37, Romain Manni-Bucau wrote:

I like the idea but think it doesnt work cause we need to handle
transactionality there so we need to enhance TimerStore to rely more
on quartz outside of transactions, no?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/tomee/pull/64#issuecomment-302560467, or
mute the thread
https://github.com/notifications/unsubscribe-auth/AGZFDmLI-cglUq24UhxL9_JZDDs0Zlohks5r7MgTgaJpZM4MfLod.

You are kind of right except assuming we use a db which will not be the default (memory) so 1 is an issue in this case. Said otherwise i like the move of this pr but it would break ejb spec in most cases (few users rely on jdbc).

OK, I do not remember excatly what I was doing in this pull request. But
it seems that the whole work is still done in
TimerService.transactionComplete(). So the main functionality is left
untouched. And I wonder why it works with
"org.apache.openejb.quartz.impl.jdbcjobstore.JobStoreTX" since the
transaction is already completed.
I think all test cases in container/openejb-core still work. It would be
interesting to find a test case that works in original openejb and not
in the pull request.

A user reported jobstoretx was not working and digging into it i realized it cant work until you hack the container so sounds unsane :s.
We also have some close tests due to oracle licensing so maybe coverage is not great on os side

authors: bodop rmannibucau


text:
Fix grove log fractional seconds

What does this PR (Pull Request) do?
Fix grove log fractional seconds.
They were being dropped and logging .0, this fixes it to match ATS identically, logging the fractional second with trailing zeros to 3 decimal places.
Includes unit tests.
No documentation, no interface change.
Includes Changelog.

[x] This PR is not related to any other Issue

Which Traffic Control components are affected by this PR?

Grove

What is the best way to verify this PR?
go test
Start grove, make a request, check the access log, verify fractional seconds are present in the timestamp (the first field).
If this is a bug fix, what versions of Traffic Ops are affected?

3.0.0
3.0.1

The following criteria are ALL met by this PR

[x] This PR includes tests OR I have explained why tests are unnecessary
[x] This PR includes documentation OR I have explained why documentation is unnecessary
[x] This PR includes an update to CHANGELOG.md OR such an update is not necessary
[x] This PR includes any and all required license headers
[x] This PR ensures that database migration sequence is correct OR this PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4013/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4022/
Test FAILed.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/trafficcontrol-PR/4031/
Test FAILed.

repo: apache/trafficcontrol


text:
Header_Rewrite Plugins   std::__throw_out_of_range

my ats version 5.3.x
https://github.com/apache/trafficserver/blob/5.3.x/plugins/header_rewrite/header_rewrite.cc
gdb message:
(gdb) bt
#0  0x00002b29313b21d7 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#1  0x00002b29313b3a08 in __GI_abort () at abort.c:119
#2  0x00002b2930bbc9d5 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:95
#3  0x00002b2930bba946 in __cxxabiv1::__terminate (handler=) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38
#4  0x00002b2930bba973 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#5  0x00002b2930bbab93 in __cxxabiv1::__cxa_throw (obj=0x2b29e0015030, tinfo=0x2b2930e481f0 , dest=0x2b2930bcf0f0 std::out_of_range::~out_of_range()) at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:87
#6  0x00002b2930c0fa17 in std::__throw_out_of_range (__s=__s@entry=0x2b293f5cadf8 "basic_string::erase") at ../../../../../libstdc++-v3/src/c++11/functexcept.cc:80
#7  0x00002b293f5c2a4c in _M_check (__s=0x2b293f5cadf8 "basic_string::erase", __pos=18446744073709551615, this=0x2b297b212af0) at /usr/include/c++/4.8.2/bits/basic_string.h:324
#8  erase (__n=1, __pos=18446744073709551615, this=0x2b297b212af0) at /usr/include/c++/4.8.2/bits/basic_string.h:1365
#9  RulesConfig::parse_config (this=this@entry=0x2b29e0032fa0, fname="/trafficserver/headerrewrite/cmod.xxxx.fm.hr", default_hook=default_hook@entry=TS_HTTP_LAST_HOOK) at header_rewrite.cc:148
#10 0x00002b293f5c3712 in TSRemapNewInstance (argc=, argv=, ih=) at header_rewrite.cc:295
(gdb) f 9
#9  RulesConfig::parse_config (this=this@entry=0x2b29e0032fa0, fname="/trafficserver/headerrewrite/cmod.xxxx.fm.hr", default_hook=default_hook@entry=TS_HTTP_LAST_HOOK) at header_rewrite.cc:148
warning: Source file is more recent than executable.
148	      line.erase(line.length() - 1, 1);
thank you!

can you show us the contents in /trafficserver/headerrewrite/cmod.xxxx.fm.hr ?

@shukitchan
#-----start------
cond %{READ_RESPONSE_HDR_HOOK}
cond %{PATH} /.(m4a)$/ [NC]
cond %{STATUS} =200 [OR]
cond %{STATUS} =304
rm-header Expires
set-header Cache-Control "max-age=259200, public" [L]
#----end-----
Not included #-----start-----, #----end----

@shukitchan
When i touch remap.conf and traffic_line -x, sometimes traffic_server will reboot;After gdb, can find this line error

If you turn on debug option and use this debug tag - "dbg_header_rewrite",
then I think you can debug and see which line is the problem.
The debug will show the line number because of this line -
https://github.com/apache/trafficserver/blob/5.3.x/plugins/header_rewrite/header_rewrite.cc#L141

I'll try   thank you!

If this is still an issue please reopen.

authors: bryancall shukitchan xieyugui

repo: apache/trafficserver


text:
Loop detection interferes with parent selection

PR#5767 added a check such that a loop is detected if the client IP is the same as the cache IP. This breaks the case where the remap config is:
map http://foo.com http://foo.com
and, one uses parent selection with go_direct=false -- a loop is improperly detected.

#5767 also breaks how we document using the generator plugin.
from https://docs.trafficserver.apache.org/en/9.0.x/admin-guide/plugins/generator.en.html?highlight=generator#examples
map http://workload.example.com/ http://127.0.0.1/ \
  @plugin=generator.so

In progress.

See PR #7069

I didn't realize this wasn't well commented.
After an online discussion, it was decided the root of the problem was the self loop detection was done too early. In particular, it did not make sense to anyone that it was done immediately after the DNS lookup, which can happen before cache read. A bad side effect of this is that it can not only interfere with parent selection, but it fails to detect loops in parent selection precisely because it is done too early. The change to be made is to move the direct loop detection to HttpSM::do_http_server_open which is where the upstream connection is opened. There is already a slew of checks in that method which are done just before connecting, such as checking for an existing session, checking for too many connections, checking remap ACLs, etc. It seems natural that direct self loop detection should also be done in there.

authors: SolidWallOfCode mtorluemke randall


text:
Reverse debug specific check.

debug_flag && diags->on() is almost an atomic operation,
while is_debug_tag_set requires Diags to run a regular expression.
When debug_flag is set to 1, we always want to print the debug log,
regardless of whether the tag is set or not, which makes the
is_debug_tag_set check useless, and expensive.
This change flips the conditional to check if debug_flag is 1 first,
skipping the tag check if it is.

[approve ci]

Cherry-picked to v9.0.x branch.

authors: calavera randall zwoop


text:
TSan: Fix data race of updating current time

Fix below TSan report.
WARNING: ThreadSanitizer: data race (pid=74346)
  Write of size 8 at 0x0000041330f8 by main thread (mutexes: write M0, write M1, write M2, write M3, write M4, write M5, write M6, write M7, write M8, write M9, write M10, write M11, write M12, write M13):
    #0 Thread::get_hrtime_updated() I_Thread.h:194 (traffic_server:x86_64+0x80513a) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #1 PriorityEventQueue::PriorityEventQueue() PQ-List.cc:28 (traffic_server:x86_64+0x849536) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #2 PriorityEventQueue::PriorityEventQueue() PQ-List.cc:27 (traffic_server:x86_64+0x8495e5) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #3 EThread::EThread(ThreadType, Event*) UnixEThread.cc:107 (traffic_server:x86_64+0x84d7cb) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #4 EThread::EThread(ThreadType, Event*) UnixEThread.cc:108 (traffic_server:x86_64+0x84da71) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #5 EventProcessor::spawn_thread(Continuation*, char const*, unsigned long) UnixEventProcessor.cc:534 (traffic_server:x86_64+0x856566) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #6 NetAccept::init_accept_loop() UnixNetAccept.cc:168 (traffic_server:x86_64+0x7dc6bc) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #7 UnixNetProcessor::accept_internal(Continuation*, int, NetProcessor::AcceptOptions const&) UnixNetProcessor.cc:146 (traffic_server:x86_64+0x7e61e6) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #8 NetProcessor::main_accept(Continuation*, int, NetProcessor::AcceptOptions const&) UnixNetProcessor.cc:86 (traffic_server:x86_64+0x7e50ee) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #9 start_HttpProxyServer() HttpProxyServerMain.cc:373 (traffic_server:x86_64+0x174fda) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #10 main traffic_server.cc:2185 (traffic_server:x86_64+0xbc1b8) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)

  Previous write of size 8 at 0x0000041330f8 by thread T12 (mutexes: write M14):
    #0 Thread::get_hrtime_updated() I_Thread.h:194 (traffic_server:x86_64+0x80513a) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #1 AIOThreadInfo::aio_thread_main(AIOThreadInfo*) AIO.cc:529 (traffic_server:x86_64+0x6292c2) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #2 AIOThreadInfo::start(int, Event*) AIO.cc:244 (traffic_server:x86_64+0x62b485) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #3 Continuation::handleEvent(int, void*) I_Continuation.h:227 (traffic_server:x86_64+0x187a0) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #4 EThread::execute() UnixEThread.cc:333 (traffic_server:x86_64+0x84f94e) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)
    #5 spawn_thread_internal(void*) Thread.cc:79 (traffic_server:x86_64+0x84c611) (BuildId: c245d2fe2dd53a87af825d77f24750ba32000000200000000100000000000c00)

  Location is global 'Thread::cur_time' at 0x0000041330f8 (traffic_server+0xad30f8)

[approve ci autest]

@masaori335 agreed to do some performance testing of this patch compared to using chrono::now.


text:
Fixes defines for the version strings

I noticed the version was incorrect in headers so I fixed this in the CMakeLists.txt

[approve ci ubuntu]

authors: bneradt cmcfarlen


text:
[Bug] [Relay][ONNX] Scaler rather than Scale: a bug about Scaler in the onnx frontend

Expected behavior
The Scaler operator has been supported in the TVM ONNX frontend, however, the map has the wrong key name Scale.  I can not find the operator Scale in the ONNX official documentation and ONNXRuntime opset. Thus, I thought the Scale is a typo of Scaler.
https://github.com/apache/tvm/blob/a1a1a7ca033f83315d02411d4b2c475ddacc795e/python/tvm/relay/frontend/onnx.py#L6531
Actual behavior
Traceback (most recent call last):
  File "bug_scaler.py", line 7, in <module>
    irmod, params = relay.frontend.from_onnx(model, {'input': (1, 2, 3, 4)}, freeze_params=True)
  File "/home/shenqingchao/software/tvm/python/tvm/relay/frontend/onnx.py", line 7225, in from_onnx
    mod, params = g.from_onnx(graph, opset)
  File "/home/shenqingchao/software/tvm/python/tvm/relay/frontend/onnx.py", line 6843, in from_onnx
    self._check_for_unsupported_ops(graph)
  File "/home/shenqingchao/software/tvm/python/tvm/relay/frontend/onnx.py", line 6936, in _check_for_unsupported_ops
    raise tvm.error.OpNotImplemented(msg)
tvm.error.OpNotImplemented: The following operators are not supported for frontend ONNX: Scaler

Steps to reproduce
step 1. Download the ONNX model here
import tvm
from tvm import relay

model = onnx.load("scaler_model.onnx")
irmod, params = relay.frontend.from_onnx(model, {'input': (1, 2, 3, 4)}, freeze_params=True)

cc @KJlaccHoeUM9l @shingjan

If the Scale is a typo, the conversion function has another bug. The type of attribute scale in Operator Scaler is a list, while TVM considers it as a float. The conversion will crash under the given ONNX model above.
First of all, I need to confirm if the Scale is a typo. If so, I can provide patches to fix these bugs.

repo: apache/tvm


text:
[AutoScheduler] Accelerate feature extraction for winograd

Compiling Winograd conv2d is very slow. This makes the feature extraction in auto-scheduler very slow.
I found the reason is that simplifying the const matrix expressions in Winograd conv2d takes a lot of time. One example of these expressions is
A(i, j) = select(((floormod(i, 6) == 5) && (floormod(j, 4) == 3)), 1f, select(((floormod(i, 6) == 5) && (floormod(j, 4) == 2)), 0f, select(((floormod(i, 6) == 5) && (floormod(j, 4) == 1)), 0f, select(((floormod(i, 6) == 5) && (floormod(j, 4) == 0)), 0f, select(((floormod(i, 6) == 4) && (floormod(j, 4) == 3)), -8f, select(((floormod(i, 6) == 4) && (floormod(j, 4) == 2)), 4f, select(((floormod(i, 6) == 4) && (floormod(j, 4) == 1)), -2f, select(((floormod(i, 6) == 4) && (floormod(j, 4) == 0)), 1f, select(((floormod(i, 6) == 3) && (floormod(j, 4) == 3)), 0.125f, select(((floormod(i, 6) == 3) && (floormod(j, 4) == 2)), 0.25f, select(((floormod(i, 6) == 3) && (floormod(j, 4) == 1)), 0.5f, select(((floormod(i, 6) == 3) && (floormod(j, 4) == 0)), 1f, select(((floormod(i, 6) == 2) && (floormod(j, 4) == 3)), 1f, select(((floormod(i, 6) == 2) && (floormod(j, 4) == 2)), 1f, select(((floormod(i, 6) == 2) && (floormod(j, 4) == 1)), 1f, select(((floormod(i, 6) == 2) && (floormod(j, 4) == 0)), 1f, select(((floormod(i, 6) == 1) && (floormod(j, 4) == 3)), -1f, select(((floormod(i, 6) == 1) && (floormod(j, 4) == 2)), 1f, select(((floormod(i, 6) == 1) && (floormod(j, 4) == 1)), -1f, select(((floormod(i, 6) == 1) && (floormod(j, 4) == 0)), 1f, select(((floormod(i, 6) == 0) && (floormod(j, 4) == 3)), 0f, select(((floormod(i, 6) == 0) && (floormod(j, 4) == 2)), 0f, select(((floormod(i, 6) == 0) && (floormod(j, 4) == 1)), 0f, select(((floormod(i, 6) == 0) && (floormod(j, 4) == 0)), 1f, 0f))))))))))))))))))))))))

But this part is actually useless for feature extraction. So I added a new flag to replace all accesses to constant matrices by constant value 1.
This flag produces a wrong IR but it is good enough for feature extraction purposes.
This accelerates one round of GA search from 300s to 150s on p3.2xlarge for a Winograd conv2d.

cc @tqchen @FrozenGene @comaniac

I like the idea in general as it may also benefit other workloads that uses selects, but I have some concerns about the new attribute and flag.
For the const_matrix attribute, it might be confusing in the future about what does it mean and why. It might be better to make it more feature extraction specific, such as ignore_feature_extraction.
In addition, the feature_extraction_mode looks a bit ad-hoc. I would rather having a separate API instead of sharing normalize and only use it when extracting feature. This separation can also make sure the extensibility of feature improvements in the future.

yeah. I also think we create one new api is better than adding one flag to normalize

Hi @merrymercy ,
Very nice improvements! I started studying and using the autoscheduler for the ARM cpu backend, so I am sorry if my comments might be obvious/naive

@comaniac I created a new API for my use case of normalize.
But I leave the attribute const_matrix. This is better than ignore_feature_extraction because const_matrix is a more fundamental attribute. Other analyses (e.g., AccessAnalyzer) can also benefit from this attribute.
@FrozenGene @giuseros Please take another look.

authors: FrozenGene comaniac giuseros merrymercy


text:
Add Python representation for VirtualDevice

This adds a Python class to represent the VirtualDevice so that the behaviour for device_type() can be semi-replicated.
These tests were actually not being ran and were broken so I've added them to the integration script.
CC @mbs-octoml

Thanks @Mousius @electriclilies @mbs-octoml !

authors: Mousius leandron


text:
[ZEPPELIN-429] Replaced explicit types with diamonds

What is this PR for?
Changed all occurrences of explicit types to diamonds in the different modules.
What type of PR is it?
Improvement
Todos

What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-429
How should this be tested?
Run the normal Maven build process.
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

Thank for the contribution. I like this kind of contribution to make code clean. LGTM. I'll merge it.

@jongyoul Quick question regarding the merge conflict: Should I solve it or do you do it during the integration?

@HorizonNet It's better to be handled here. Could you resolve it please?

@minahlee Done.

Merging it there is no more discussion

authors: HorizonNet jongyoul minahlee

repo: apache/zeppelin

license_source: bigquery


text:
[ZEPPELIN-1690] - ZeppelinHubNotebookRepo multy user handling

What is this PR for?
This PR bring multi user handling to ZeppelinHubNotebookRepo.
What type of PR is it?
[Improvement ]
What is the Jira issue?

ZEPPELIN-1690

Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@anthonycorbacho thanks for enhancements! i started looking into this one and first of all CI looks like failing with checkstyle issues. Also some methods seem to be missing, and proper jira ticket would be appreciated :)

@khalidhuseynov as you can see its a wip, i will let you know when its ready for review

CI is green, please review otherwise merging it :)

thanks for the fix, LGTM!

authors: anthonycorbacho khalidhuseynov


text:
[WIP][DOC] 0.7.0 release note

What is this PR for?
Add 0.7.0 release note
What type of PR is it?
Documentation
Todos

[ ] Confirm release date and update list of people who verified release once vote pass.
[ ] Update doap.rdf

How should this be tested?
Open zeppelin-release-0.7.0.md and see if there is missing feature that needs to be mentioned in release note.
Screenshots (if appropriate)
Download page

Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? -

Looks good to me!

great thanks!

Merging it to deploy 0.7.0 document.

authors: Leemoonsoo felixcheung minahlee


text:
fix: oracle failed in GKE due to permission denied

fix: https://github.com/apecloud/kubeblocks/issues/6195

/cherry-pick release-0.8

/cherry-pick release-0.8

repo: apecloud/kubeblocks-addons


text:
Fix Docker command path

Docker command is not valid: cas-overlay/bin/run-cas.sh is relative to /cas-overlay and is being resolved to /cas-overlay/cas-overlay/bin/run-cas.sh file which does not exist.
This should be bin/run-cas.sh (which is resolved to /cas-overlaybin/run-cas.sh).
Steps to reproduce the issue:
docker run -p 8080:8080 apereo/cas
causes:
docker: Error response from daemon: OCI runtime create failed: container_linux.go:296: starting container process caused "exec: \"cas-overlay/bin/run-cas.sh\": stat cas-overlay/bin/run-cas.sh: no such file or directory": unknown.
ERRO[0000] error waiting for container: context canceled

After this fix it works as expected.

 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.

authors: CLAassistant IonBazan

repo: apereo/cas


text:
Add possibility of overriding the value of the "x-frame-options" header using service files [FORWARD PORT]

The service property "httpHeaderEnableXFrameOptions" can control if the
x-frame-options header should be inserted in the HTTP response. However it
make sense to control the value of the x-frame-options using service files.
This commit implements that feature by introducing the property
"httpHeaderXFrameOptions".
Forward-Port: 95dad85

Merging in to follow-up with fixes in https://github.com/apereo/cas/commit/82385f3d90a19da1ed5962089fedc734a8626fd8

authors: bosim mmoayyed


text:
Support configuration of other runtime properties in ProcessorConfigDTO

There are many properties in ProcessorConfigDTO that are useful to be able to specify, particularly as flows move from dev/staging/prod promotions.
concurrentlySchedulableTaskCount is one we particularly want to control.

One thing to look out for is a deployment spec format change. Would now need to have a properties section (what is now called config) as well as the config, which is not supported currently, but houses system settings for the processor. This part is easy, in fact.
Will need to review and update all docs and utilities to account for this swap.

authors: aperepel davetorok

repo: aperepel/nifi-api-deploy


text:
Interface is broken

`⇒  go run cli.go
command-line-arguments
./cli.go:12: cannot use cli.Default (type cli.Handler) as type "github.com/apex/log".Handler in argument to "github.com/apex/log".SetHandler:
cli.Handler does not implement "github.com/apex/log".Handler (wrong type for HandleLog method)
have HandleLog("github.com/apex/log/vendor/github.com/apex/log".Entry) error
want HandleLog("github.com/apex/log".Entry) error`

Can you elaborate? Is this _examples/cli/cli? it works fine for me:
$ go run _examples/cli/cli.go
   • uploading                 file=something.png type=image/png user=tobi
   • upload complete           file=something.png type=image/png user=tobi
   • uploading                 file=something.png type=image/png user=tobi
   • upload complete           file=something.png type=image/png user=tobi

oh I see, you have a vendor and non-vendor version, Go treats them as separate packages

repo: apex/log

license: mit


text:
Scheduled requests

Big maybe, this starts to enter into apex(1) / Serverless territory, not sure I really want to go there, but it would be nice to not use verbose Terraform stuff just to set up scheduled tasks.

Pro feature imo, if it lands.

Think I'll close this one for now, feature-creeping into evented stuff.

Is this possible with CloudWatch > Rules > Targets > Lambda > Input > "Constant (JSON text)" ? Where the JSON text is something like {"method":"GET","path":"/foo/bar"}?

@jpillora yep! I forget what the properties are off-hand but something like that should be fine

Its actually possible to "secure" the schedule request by hijacking the requestId field of requestContext.
ie if you put the following as your JSON text in your cloud watch rule
{"requestContext":{"requestId":"cron","stage":"staging"},"httpMethod":"POST","path":"/api/cron","body":"{}"}

in your code you can then do something like this:
if (request.headers["x-request-id"] !== "cron") return { status: 403 }

Since x-request-id is always overridden by UP from requestContext a malicious request cant send this as a header. Meaning that you can verify that requests legitimately from cloudwatch schedule.
@tj can you see any issues with this approach? 😅

@cloudkite ahaha interesting yeah that sounds like it'd work! Since we'd have the target path with config—something like below—we'd potentially be able to blacklist it for the user too, but that means that path wouldn't be available externally in any case, but it removes the need to check for == "cron" manually
{
  "cron": [
    {
      "path": "/whatever/here",
      "interval": "30m"
    }
  ]
}

I still question if it's even worth adding for HTTP hahah when regular Lambda + Scheduled events is already great for this. I think the better approach might be to do an Apex 2.0 which has this stuff built in for FaaS

@tj yeah totally agree regular lambda and scheduled events are probably a better fit. I just didn’t want to have to have an additional project to deploy. I’ve got this setup as above and seems to work well. More than fine with it being a manual thing and not built in to UP

authors: cloudkite jpillora lukeed tj

repo: apex/up

license: MIT


text:
console.log left in production build

Looks like there's a console.log still around here.

Hey, thanks for reporting, just fixed it.

I will use this plugin to strip console.logs from builds - https://github.com/rollup/rollup-plugin-strip

authors: junedchhipa mikaelkaron


text:
high max value breaks datalabel display

Hello there,
here are all the details about this issue (apex 3.8.4 on my test plateform)
Codepen
https://codepen.io/tcharles/pen/mNLJwR
in this codeopen you have two horizontal bar charts, one using a five digits max with a five digits serie value. Everything work as expected on this one.
The second horizontal bar chart uses a six digits max with a six digits serie value. On this one, the datalabels doesn't show up
Explanation

What is the behavior you expect?
I want my datalabel to be displayed

What is happening instead?
if the max value of the bar is too high (more than five digitis), the datalabel is not going to be displayed

What error message are you getting?
none

Fixed since 3.12.0

authors: junedchhipa tanguyvda


text:
Overlapping columns on datetime x axis

codesandbox
Awesome work with the library!
I'm having a hard time having columns on a datetime x axis and making sure the don't overlap, I'm working on a interactable chart and it ruins the experience. AFAIK there's no way of controlling the widh of collumns with 2 different values like it's proposed here
Is there a work arround to avoid this overlapping? Thanks in advance

This problem happens on last version. on datetime x.axis it is overlapping when in the same date. And with datetime the stack bar doesnt work either? I tried to bypass the overlap issue.

authors: DMOAbove gerardosabetta


text:
Update to golang 1.6

remove Godeps folder
migrate to vendor
using Glide instead Godep
add Dockerfile to test build

@w-vi can you check if upgrade is ok?

@w-vi failed test:
GIN-debug] POST   /                         --> github.com/apiaryio/heroku-datadog-drain-golang.(*ServerCtx).(github.com/apiaryio/heroku-datadog-drain-golang.processLogs)-fm (2 handlers)
--- FAIL: TestFull (1.00s)
	server_test.go:180: Expected: app.metric.request.length:541.000000|h|#source:web.1,route:/parser,request.id:11747467-f4ce-4b06-8c99-92be968a02e3. Actual: app.metric.request.length:541.000000|h|#source:web.1,request.id:11747467-f4ce-4b06-8c99-92be968a02e3,route:/parser
	server_test.go:180: Expected: app.metric.response.length:5163.000000|h|#source:web.1,route:/parser,request.id:11747467-f4ce-4b06-8c99-92be968a02e3. Actual: app.metric.response.length:5163.000000|h|#source:web.1,request.id:11747467-f4ce-4b06-8c99-92be968a02e3,route:/parser
	server_test.go:180: Expected: app.metric.parser.time:5.000000|h|#source:web.1,route:/parser,request.id:11747467-f4ce-4b06-8c99-92be968a02e3. Actual: app.metric.parser.time:5.000000|h|#source:web.1,request.id:11747467-f4ce-4b06-8c99-92be968a02e3,route:/parser
FAIL
exit status 1

it's problem with order to compare tests. Suggestion how fix this?

@abtris I knew that this will blow to our face one day, it was relying on the hash table implementation. I will fix it, have to figure out how though.

@w-vi can be possible using https://golang.org/pkg/reflect/#DeepEqual for compare arrays?

I make more debugging and find problem not only order in testing but order in processing request isn't for tests ideal.
MESSAGE_: app.metric.parser.time:5.000000|h|#source:web.1,request.id:11747467-f4ce-4b06-8c99-92be968a02e3,route:/parser
TESTED__: app.metric.request.length:541.000000|h|#source:web.1,route:/parser,request.id:11747467-f4ce-4b06-8c99-92be968a02e3
TESTED__: app.metric.response.length:5163.000000|h|#source:web.1,route:/parser,request.id:11747467-f4ce-4b06-8c99-92be968a02e3
TESTED__: app.metric.parser.time:5.000000|h|#source:web.1,route:/parser,request.id:11747467-f4ce-4b06-8c99-92be968a02e3

but I'm not sure if is real problem. For statsd isn't problem changing parameters order problem is only string equality in tests.

Cool, I was going to do this, because order doesn't matter. So all is good again :)

authors: abtris w-vi

repo: apiaryio/heroku-datadog-drain-golang


text:
Add option to put contract tests in specific folder

The ability to target specific folders allows us to (for example) only run Integration Tests via Newman.
As a user I'd like to be able to do the same for running Contract Tests only depending on ci/cd workflow.
We can maybe add a contractTestFolder that when present moves operations from the root of the collection to new folder.

Linked to #117

Another great feature delivered by @nicklloyd. Closing this issue since it is part of the 1.6.0 release.

repo: apideck-libraries/portman


text:
TEST: test video

https://user-images.githubusercontent.com/38246758/193250094-d1b7640d-bbb2-4a21-a027-cc80115ec75e.mov

test over

repo: apify/apify-docs


text:
Add max data size validation and chunking to dataset.pushData()

Implements https://github.com/apifytech/apify-js/issues/70
Replaces https://github.com/apifytech/apify-shared-js/pull/5
Minor change in apify-client is necessary to accept pre-serialized values.

Tests pass. Failed check is a lint issue.

Potential issue:
The joining of individual JSONs adds 2 extra bytes for [] and (numOfJSONs - 1) bytes for each ,. In edge cases, this could introduce errors.

Everything seems great, except for the failing tests :)

authors: jancurn mnmkng

repo: apifytech/apify-js


text:
Simplify swagger-ui updates by downloading on install

To simplify updates just download swagger-ui from github.
This currently works for npm. I don't know about bower et al.
It includes a patch so that no modifications on swagger-ui source necessary anymore and
you can just drop in another swagger-ui.
You could even think of always getting the latest swagger during install. But like that you can still check if it is working.

I'll update the testcases if you think this is an idea worth following.

any updates here @whitlockjc? not interesting?

I appreciate the work but I don't agree with the approach.  swagger-ui is included as a convenience and if you want to use a custom version, or a newer version, there is a simple middleware option to point to another swagger-ui location.  I realize the current approach makes it very easy for the swagger-ui shipped with swagger-tools to become very old but the same could happen with this PR because you will only install swagger-ui when you npm install swagger-tool.  So I'm not sure how this fixes the problem.
I'm not sure if you noticed but the middleware/swagger-ui/index.html file is custom to swagger-tools.  It alters the swagger-ui bootstrap process to get the Swagger document URL from swagger-tools via a simple HTTP call.  This PR would break that feature.
I'm all for figuring out a way to make things better so let's continue the conversation.

I thought about the the downloading as well and I'm not quite sure if it is the best idea to handle it that way. Because the environments are probably very different where the download should work. And if there is a way to download the npm package doesn't mean there is also a way to download the ui package as well.
Thats also why i didn't work on the testcases as well. Was more like a PoC. :-)
But there is a patch included that could be interesting anyway, and perhaps that would be a first start.
As you mentioned, the middleware/swagger-ui/index.html is patched. I reverted that patch and patched the way the UI is invoked by automatically adding a URL parameter to pass the swagger.json data. That way there is no need anymore to patch swagger-ui when upgrading.
https://github.com/apigee-127/swagger-tools/pull/416/files#diff-5c8932074d16e6b49a2248910f364c85R156
I could just pick those commits and make a new pull request for that.

I've updated swagger-ui to the latest as part of 9b5131361ec75712a6a0784b2e106d7664eb5b4f.  I kept the original index.html in repository as index.html.orig so if you can figure out some way to automate the downloading/patching of swagger-ui as part of download/install, I'm all ears.  For now, I'm closing this as the new work would likely be a new contribution.

authors: bitcloud whitlockjc


text:
🛑 Gitea is down

In 76abe9b, Gitea (https://gitea.openstorage.xyz) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Gitea is back up in dcd0662.

repo: apinter/OSC-mon


text:
Build for Jazzy with mavros from source

Per blue!169, an official image for Jazzy is blocked by the lack of a Jazzy package for Mavros
Changes Made

Install Mavros and Mavlink from source (Rolling release) directly into the blue workspace.

Updates to Gazebo "Harmonic"

This also required bashing through issues related to Ubuntu 24.04:

Ubuntu 24.04 now has a "externally managed installation" of Python, which discourages "pip install"ing packages outside of virtualenv.   Create virtual env ~/.venv/blue and activate by default both within the build and when running in the docker.   This leads to rosdep installing some pip dependencies into the venv.

Testing
Please provide a clear and concise description of the testing performed.

There's some additional information regarding the move away from global Python package installations in PEP 668. From what I understand, Ubuntu will be keeping the marker file present in the base image, and because the ROS images use Ubuntu as their base image, this problem will persist. I haven't tried this yet, but you could try removing the marker file from the base image:
rm -rf /usr/lib/python3.12/EXTERNALLY_MANAGED

You might need to updated the system path afterwards as well. Using a virtual environment seems like the best approach moving forward though.

@evan-palmer  (finally), I believe this branch is complete.  Multi-platform builds are time consuming.
Starting on testing.

This PR has been split up:

blue PR 223 contains the migration from Gazebo Garden to Harmonic (for all releasese)
blue PR 220 handles the migration of rolling to ubuntu "Noble", which requires handling the "ubuntu" user and python venv.    Once merged it should be propagated to jazzy

Once those two are merged, the jazzy branch then needs to be updated to build Mavros from source (there are binary packages for rolling)

authors: amarburg evan-palmer

repo: apl-ocean-engineering/blue


text:
安装了Apollo，可以正常运行但是后面想添加多个环境，就在数据库里添加fat,uat,pro三个环境，但是启动之后发现还是只有一个dev环境，因为什么问题？

参考 3.1.2 apollo.portal.meta.servers - 各环境Meta Service列表
你需要把 FAT,UAT,PRO 对应的apollo.meta地址填上
将 apollo.portal.meta.servers

改成
{
    "DEV":"http://1.1.1.1:8080",
    "FAT":"http://apollo.fat.xxx.com",
    "UAT":"http://apollo.uat.xxx.com",
    "PRO":"http://apollo.xxx.com"
}

authors: Anilople lmz-json

repo: apolloconfig/apollo


text:
chore(deps): update dependency @rollup/plugin-typescript to v11

This PR contains the following updates:

Package
Change
Age
Adoption
Passing
Confidence

@rollup/plugin-typescript (source)
8.5.0 -> 11.1.5

Release Notes

rollup/plugins (@rollup/plugin-typescript)
v11.1.5
Compare Source
2023-10-05
Bugfixes

fix: ensure rollup 4 compatibility #https://github.com/rollup/plugins/pull/1595l/1595)

v11.1.4
Compare Source
2023-09-25
Bugfixes

fix: fix sourcemap sourcecontent referencing non-existent files #https://github.com/rollup/plugins/pull/1571l/1571)

v11.1.3
Compare Source
2023-08-26
Bugfixes

fix: emit declaration files for type-only source files that are not explicitly included #https://github.com/rollup/plugins/pull/1555l/1555)

v11.1.2
Compare Source
2023-06-28
Bugfixes

fix: change the value of isExternalLibraryImport to false if the resolvedModule should be compiled #https://github.com/rollup/plugins/pull/1521l/1521)

v11.1.1
Compare Source
2023-05-12
Bugfixes

fix: Allow for using compilerOptions.moduleResolution #https://github.com/rollup/plugins/pull/1453l/1453)

v11.1.0
Compare Source
2023-04-04
Features

feat: write declaration files in configured directory for output.file #https://github.com/rollup/plugins/pull/1378l/1378)

v11.0.0
Compare Source
2023-01-06
Breaking Changes

fix: don't resolve filtered files #https://github.com/rollup/plugins/pull/1267l/1267) (#&https://github.com/rollup/plugins/issues/1310/issues/1310))

v10.0.1
Compare Source
2022-11-28
Bugfixes

fix: emit assets when watchMode is false. fixes #https://github.com/rollup/plugins/issues/1354s/1354) (5c88274)

v10.0.0
Compare Source
2022-11-27
Breaking Changes

fix: incorrect declarations directory (a5c90d1)

v9.0.2
Compare Source
2022-10-21
Updates

chore: update rollup dependencies (3038271)

v9.0.1
Compare Source
2022-10-11
Bugfixes

fix: fix ESM build #https://github.com/rollup/plugins/pull/1311l/1311)

v9.0.0
Compare Source
2022-10-10
Breaking Changes

fix: prepare for Rollup 3 #https://github.com/rollup/plugins/pull/1282l/1282)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - "after 8am and before 4pm on tuesday" in timezone Etc/UTC.
🚦 Automerge: Enabled.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Rolled up into https://github.com/apollographql/apollo-ios-dev/pull/170.

authors: calvincestari svc-secops

repo: apollographql/apollo-ios-dev


text:
Runtime Exception: java.io.EOFException: source exhausted prematurely

Summary
We have run into production exceptions in different queries but with similar stacktraces java.io.EOFException: source exhausted prematurely. This exception is happening at the rate of 1k/day for our applications.
Version
2.5.14
Steps to reproduce the behavior

The query itself is probably 500 lines when fully expanded.

The response size is at the scale of 100KB+.

We are seeing a different exception for the same query for our iOS counterpart.

We are thinking if this exception is just due to the fact that

Either the response is too long and our vanilla graphql server cannot handle
The client application times out when parsing the response from server
In either case, the exception message was not clear and could be a lower-level issue.

Logs
java.io.EOFException: source exhausted prematurely
    at okio.InflaterSource.read(InflaterSource.kt:184)
    at okio.GzipSource.read(GzipSource.kt:319)
    at okio.RealBufferedSource.indexOfElement(RealBufferedSource.kt:35)
    at com.apollographql.apollo.api.internal.json.BufferedSourceJsonReader.nextQuotedValue(BufferedSourceJsonReader.kt:4)
    at com.apollographql.apollo.api.internal.json.BufferedSourceJsonReader.nextString(BufferedSourceJsonReader.kt:118)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextString(ResponseJsonStreamReader.kt:24)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextScalar(ResponseJsonStreamReader.kt:162)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.toMap(ResponseJsonStreamReader.kt:120)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader$readObject$1.read(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextObject(ResponseJsonStreamReader.kt:26)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.readObject(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.toMap(ResponseJsonStreamReader.kt:84)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader$readObject$1.read(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextObject(ResponseJsonStreamReader.kt:26)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.readObject(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.toMap(ResponseJsonStreamReader.kt:84)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader$readObject$1.read(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextObject(ResponseJsonStreamReader.kt:26)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.readObject(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.toMap(ResponseJsonStreamReader.kt:84)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader$readObject$1.read(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextObject(ResponseJsonStreamReader.kt:26)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.readObject(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader$readList$1.read(ResponseJsonStreamReader.kt:59)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextList(ResponseJsonStreamReader.kt:39)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.toMap(ResponseJsonStreamReader.kt:112)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader$readObject$1.read(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextObject(ResponseJsonStreamReader.kt:26)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.readObject(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.toMap(ResponseJsonStreamReader.kt:84)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader$readObject$1.read(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextObject(ResponseJsonStreamReader.kt:26)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.readObject(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader$readList$1.read(ResponseJsonStreamReader.kt:59)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextList(ResponseJsonStreamReader.kt:39)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.toMap(ResponseJsonStreamReader.kt:112)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader$readObject$1.read(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextObject(ResponseJsonStreamReader.kt:26)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.readObject(ResponseJsonStreamReader.kt:7)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.toMap(ResponseJsonStreamReader.kt:84)
    at com.apollographql.apollo.response.OperationResponseParser$1.read(OperationResponseParser.java:1)
    at com.apollographql.apollo.api.internal.json.ResponseJsonStreamReader.nextObject(ResponseJsonStreamReader.kt:26)
    at com.apollographql.apollo.response.OperationResponseParser.parse(OperationResponseParser.java:55)
    at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor.parse(ApolloParseInterceptor.java:40)
    at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor$1.onResponse(ApolloParseInterceptor.java:22)
    at com.apollographql.apollo.internal.interceptor.ApolloServerInterceptor$executeHttpCall$1.onResponse(ApolloServerInterceptor.kt:44)
    at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:58)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
    at java.lang.Thread.run(Thread.java:920)
com.apollographql.apollo.exception.ApolloParseException: Failed to parse http response
    at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor.parse(ApolloParseInterceptor.java:117)
    at com.apollographql.apollo.internal.interceptor.ApolloParseInterceptor$1.onResponse(ApolloParseInterceptor.java:22)
    at com.apollographql.apollo.internal.interceptor.ApolloServerInterceptor$executeHttpCall$1.onResponse(ApolloServerInterceptor.kt:44)
    at okhttp3.internal.connection.RealCall$AsyncCall.run(RealCall.kt:58)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
    at java.lang.Thread.run(Thread.java:920)
java.lang.RuntimeException: SearchResultsPlacementsQuery: Failed to parse http response
    at com.instacart.client.apollo.ICApolloErrorLogger.<init>(ICApolloErrorLogger.kt:1)
    at com.instacart.client.apollo.ICApolloDelegate.applyResponseHandling(ICApolloDelegate.kt:3)
    at com.instacart.client.apollo.ICApolloDelegate.query(ICApolloDelegate.kt:65)
    at com.instacart.client.apollo.ICApolloApiImpl.query(ICApolloApiImpl.kt:13)
    at com.instacart.client.search.ICSearchPlacementsRepo$fetchResults$1.invoke(ICSearchPlacementsRepo.kt:46)
    at com.instacart.client.search.ICSearchPlacementsRepo$fetchResults$1.invoke(ICSearchPlacementsRepo.kt:1)
    at com.instacart.client.lce.utils.ICLceUtils$retryEvent$1.invoke(ICLceUtils.kt:2)
    at com.instacart.client.lce.utils.ICLceUtils$retryEvent$1.invoke(ICLceUtils.kt:1)
    at com.instacart.client.lce.utils.ICLceUtils$$ExternalSyntheticLambda1.apply(R8$$SyntheticClass:26)
    at io.reactivex.rxjava3.internal.operators.observable.ObservableSwitchMap$SwitchMapObserver.onNext(ObservableSwitchMap.java:23)
    at io.reactivex.rxjava3.internal.operators.observable.ObservableConcatMap$ConcatMapDelayErrorObserver$DelayErrorInnerObserver.onNext(ObservableConcatMap.java:3)
    at com.jakewharton.rxrelay3.PublishRelay$PublishDisposable.onNext(PublishRelay.java:9)
    at com.jakewharton.rxrelay3.PublishRelay.accept(PublishRelay.java:17)
    at com.jakewharton.rxrelay3.SerializedRelay.accept(SerializedRelay.java:51)
    at com.instacart.client.lce.utils.ICLceUtils$retryEvent$1$1$1.invoke(ICLceUtils.kt:2)
    at com.instacart.client.lce.utils.ICLceUtils$retryEvent$1$1$1.invoke(ICLceUtils.kt:1)
    at com.instacart.client.ui.lce.ICLoadingErrorScreen$toOnClickListener$1.onClick(ICLoadingErrorScreen.kt:16)
    at android.view.View.performClick(View.java:7792)
    at android.widget.TextView.performClick(TextView.java:16112)
    at android.view.View.performClickInternal(View.java:7769)
    at android.view.View.access$3800(View.java:910)
    at android.view.View$PerformClick.run(View.java:30218)
    at android.os.Handler.handleCallback(Handler.java:938)
    at android.os.Handler.dispatchMessage(Handler.java:99)
    at android.os.Looper.loopOnce(Looper.java:226)
    at android.os.Looper.loop(Looper.java:313)
    at android.app.ActivityThread.main(ActivityThread.java:8663)
    at java.lang.reflect.Method.invoke(Method.java)
    at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:567)
    at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1135)

Anything else?
Posting this issue here for posterity (We have tried searching elsewhere and didn't find valuable clues), and this repository seems the best to start the conversation

@Jawnnypoo @bohan-v @huangc10

Thanks for opening this @chao2zhang. Searching for the OkHttp issue links to two OkHttp issues (https://github.com/square/okhttp/issues/4277, https://github.com/square/okhttp/issues/2193) that points to two possible explanations:

trailer bytes at the end of the compressed stream are missing.
content-length returned is the one of the original response, not the content-length of the compressed response.

Did you want Apollo Kotlin to handle things differently here?

Closing this one as it's unclear what can be done from Apollo's side. Feel free to leave a comment if you want me to reopen.

Thanks Martin, we are investigating further on our end - we suspect it may be a timeout issue or something server related.

authors: Jawnnypoo chao2zhang martinbonnin

repo: apollographql/apollo-kotlin


text:
generic options resolve function

will be taken out of #308
TODO:

[ ] Update CHANGELOG.md with your change (include reference to issue & this PR) - not needed i assume?
[X] Make sure all of the significant new logic is covered by tests
[X] Rebase your changes on master so that they can be merged easily
[X] Make sure all tests and linter rules pass

@helfer / @stubailo ?

Looks good to me @DxCx! Is this so it can be used with subscriptions more easily?

Yep

@helfer?

authors: DxCx helfer

repo: apollographql/graphql-server


text:
Enhanced Error Handling - SweetAlert Integration and Automatic Redirect 🍬🔗

Related Issue

Closes: #284
Description of Changes
This PR replaces the standard error message with a more visually appealing and user-friendly SweetAlert popup for security vulnerabilities. It also includes an automatic redirect to the user panel page upon clicking "OK" on the SweetAlert. These changes significantly enhance the user experience and improve security measures.
Your review and feedback are appreciated as we strive to deliver a more polished and secure application. 🌟🚀
Checklist:

[x] My code adheres to the established style guidelines of this project.
[x] I have conducted a self-review of my code.
[x] I have included comments in areas that may be difficult to understand.
[] I have made corresponding updates to the project documentation.
[x] My changes have not introduced any new warnings.

Screenshots
https://github.com/apoorvaron/Shorty/assets/85815172/3a97e724-7357-47f1-8684-9581d324a01e
Please provide any necessary screenshots to illustrate the changes made.

@apoorvaron Please Review this PR

@Nishitbaria

For this test case, like when user remove the link number from url
Solution : Don't show below error message , just redirect user to user panel (/user/index.php)

For the error, that "link does not exist" , just show unauthorised access error msz because we don't have to tell user that this link is not existing.

Don't show below error message , just redirect user to user panel (/user/index.php)

for this point , removing the link number from url was just a example. This error is for any other error from sql database errors like cant connect or any error from database side

make your call ?

For the error, that "link does not exist" , just show unauthorised access error msz because we don't have to tell user that this link is not existing.
for this i will remove extra layer which check link exists or not

moving the link number from url was just a example. This error is for any other er

Ok Cool...
Noted

Don't show below error message , just redirect user to user panel (/user/index.php)

for this point , removing the link number from url was just a example. This error is for any other error from sql database errors like cant connect or any error from database side

make your call ?

Can we show the error text as?
"Internal Server Error : 500"

Ok Cool!! Noted

Sure, here's the updated code with the condition removed:
<?php

$database = new Database();
$link = $database->connect();

$checkValidity =  // Check if the uniqueNo and linkID combination is valid
if ($CheckResult = mysqli_query($link, $checkValidity)) {
    if (mysqli_num_rows($CheckResult) > 0) {
        $sql = //Get Data
        if ($result = mysqli_query($link, $sql)) {
            if (mysqli_num_rows($result) > 0) {
                $row = mysqli_fetch_array($result);

                // Output the form with the fetched data
                echo "

                ";

                mysqli_free_result($result);
            } else {
                echo "
No Record Found.
";
            }
        } else {
            echo "";
        }
    } else {
        echo "";
    }
} else {
    echo "";
}
?>

I removed the $LinkIDExist condition as requested. The code will now directly check for the validity of the uniqueNo and linkID combination. If the combination is valid, it will proceed to fetch and display the form. Otherwise, it will display an error message and redirect the user back to the index page.

@apoorvaron Check man

authors: Nishitbaria apoorvaron

repo: apoorvaron/Shorty


text:
lib/internal: do not compare tag when pulling by digest

This commit fixes docker2aci pull-by-digest in order to avoid an
improper fallback to "latest" tag and a wrong comparison when no
tags have been specified.
Reference: https://github.com/coreos/rkt/issues/2313#issuecomment-245455406

This should have been spotted by TestFetchingByDigestV22, so there is probably another bug to be chased in the testsuite.
/cc @dgonyeo

nice catch, lgtm

authors: jonboulle lucab


text:
nomachine 6.6.8

Broken link
Downloading installer from https://download.nomachine.com/download/6.6/Windows/nomachine_6.6.8_5.exe
Invalid download URL https://download.nomachine.com/download/6.6/Windows/nomachine_6.6.8_5.exe. [ContentType=text/html]

Thanks for reporting it.

authors: erwinkendo kayone


text:
searchBar component now has ability to have placeholder prop

fixes #81

+1

repo: appitierre/aptr-uikit


text:
Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.
Will APPIUM support the CDP function supported by Selenium?

@jlipps @mykola-mokhnach, is this a client thing or more related to server side?
Anayway I don't see a point putting the effort into it while selenium already mentioned they are favoring the BiDi protocol https://w3c.github.io/webdriver-bidi/
You can also read more about it here https://www.selenium.dev/documentation/webdriver/bidirectional/

cdp endpoint for HTTP request, I think this dotnet also should work. https://github.com/search?q=repo%3ASeleniumHQ%2Fselenium+executeCdp+language%3AC%23&type=code&l=C%23
it sends a cdp command, and appium proxies the request to the chromedriver.
Other driver does not support the cdp endpoint.
In terms of over websocket stuff, possibly https://github.com/appium/appium/pull/19404 ?
But I'm not sure if C# in selenium has the functionality to speak websocket.
https://github.com/mykola-mokhnach/appium-devtools-plugin may also be helpful if you're interested in attaching to devtools protocol.

@DongMongppp did you tried https://github.com/mykola-mokhnach/appium-devtools-plugin?

@DongMongppp, Let us know if the above is what you were looking for before I close this issue.

Closed due to no response.

Closed due to no response.

authors: DongMongppp Dor-bl KazuCocoa

repo: appium/dotnet-client


text:
LCM scheduler

Hello,
I really like this repo, thank you to all the contributors!
I was wondering if there are plans to add the LCM scheduler to this repo. From my understanding, it wouldn't require major modifications in the code, and it would allow much faster inference.
I already started working on it, but I think both my understanding of the scheduler and my Swift skills are too low to complete the task all by myself.
Below is my current code. Although it is not working, I think it could be a good starting point for anyone wanting to contribute.
// MARK: - LCMScheduler

///  This implementation matches:
///  [Hugging Face Diffusers LCMScheduler](https://github.com/huggingface/diffusers/blob/v0.26.3/src/diffusers/schedulers/scheduling_lcm.py)
@available(iOS 16.2, macOS 13.1, *)
public final class LCMScheduler: Scheduler {
    public var trainStepCount: Int
    public var inferenceStepCount: Int
    public var origStepCount: Int
    public var timeStepScaling: Int
    public var clipSampleRange: Int
    public var betas: [Float]
    public var alphas: [Float]
    public var alphasCumProd: [Float]
    public var timeSteps: [Int]

    // Internal state
    var currentSample: MLShapedArray<Float32>?
    var stepIndex: Int?
    // var finalAlphaCumProd: Float
    // var initNoiseSigma: Float = 1.0
    // var customTimesteps: Bool = false

    // Initialize with similar parameters as in Python
    public init(
        stepCount: Int = 4,
        trainStepCount: Int = 1000,
        betaSchedule: BetaSchedule = .scaledLinear,
        betaStart: Float = 0.00085,
        betaEnd: Float = 0.012,
        origStepCount: Int = 50,
        timeStepScaling: Int = 10
    ) {
        self.trainStepCount = trainStepCount
        self.inferenceStepCount = stepCount
        self.origStepCount = origStepCount
        self.timeStepScaling = timeStepScaling

        self.clipSampleRange = 1

        switch betaSchedule {
        case .linear:
            self.betas = linspace(betaStart, betaEnd, trainStepCount)
        case .scaledLinear:
            self.betas = linspace(pow(betaStart, 0.5), pow(betaEnd, 0.5), trainStepCount).map({ $0 * $0 })
        }

        // // Optionally rescale betas for zero terminal SNR
        // if rescaleBetasZeroSNR {
        //     // TODO: implement rescale_zero_terminal_snr equivalent in Swift
        //     self.betas = rescaleBetasForZeroSNR(betas: self.betas)
        // }

        self.alphas = betas.map({ 1.0 - $0 })
        var alphasCumProd = self.alphas
        for i in 1..<alphasCumProd.count {
            alphasCumProd[i] *= alphasCumProd[i -  1]
        }
        self.alphasCumProd = alphasCumProd
        let stepsOffset = 1 // For stable diffusion
        let stepRatio = Float(trainStepCount / stepCount )
        let forwardSteps = (0..<stepCount).map {
            Int((Float($0) * stepRatio).rounded()) + stepsOffset
        }

        // Initialize timeSteps to an empty array; it will be populated by setTimesteps
        self.timeSteps = []
        // Call setTimesteps to initialize the timeSteps property based on the provided parameters
        self.setTimesteps(stepCount: stepCount, origStepCount: origStepCount)

        self.currentSample = nil
    }
}

@available(iOS 16.2, macOS 13.1, *)
extension LCMScheduler {
    func setTimesteps(
        stepCount: Int? = nil,
        origStepCount: Int? = nil,
        strength: Float = 1.0
    ) {
        let origSteps = origStepCount ?? self.origStepCount

        guard origSteps <= self.trainStepCount else {
            fatalError("`origSteps`: \(origSteps) cannot be larger than `trainStepCount`: \(self.trainStepCount).")
        }

        let k = self.trainStepCount / origSteps
        let lcmOriginTimesteps = (1...Int(Float(origSteps) * strength)).map { $0 * k - 1 }

        let finalStepCount = stepCount ?? self.inferenceStepCount
        guard finalStepCount <= self.trainStepCount else {
            fatalError("`stepCount`: \(finalStepCount) cannot be larger than `trainStepCount`: \(self.trainStepCount).")
        }

        let skippingStep = lcmOriginTimesteps.count / finalStepCount
        guard skippingStep >= 1 else {
            fatalError("The combination of `origSteps x strength`: \(origSteps) x \(strength) is smaller than `stepCount`: \(finalStepCount).")
        }

        guard finalStepCount <= origSteps else {
            fatalError("`stepCount`: \(finalStepCount) cannot be larger than `origStepCount`: \(origSteps).")
        }

        self.inferenceStepCount = finalStepCount

        // Calculate the actual timesteps to use for inference
        let inferenceIndices = stride(from: 0, to: lcmOriginTimesteps.count, by: skippingStep).map { lcmOriginTimesteps[$0] }
        self.timeSteps = Array(inferenceIndices.prefix(finalStepCount))

        // Reset internal state related to timestep tracking
        self.stepIndex = nil
    }
}

@available(iOS 16.2, macOS 13.1, *)
extension LCMScheduler {
    /// Compute  sample (denoised image) at previous step given a current time step
    ///
    /// - Parameters:
    ///   - sample: The current input to the model x_t
    ///   - timeStep: The current time step t
    ///   - prevStep: The previous time step t−δ
    ///   - modelOutput: Predicted noise residual the current time step e_θ(x_t, t)
    /// - Returns: Computes previous sample x_(t−δ)
    public func step(
        output: MLShapedArray<Float32>,
        timeStep t: Int,
        sample s: MLShapedArray<Float32>
    ) -> MLShapedArray<Float32> {

        // Check if inferenceStepCount has been initialized
        guard inferenceStepCount != nil else {
            fatalError("Number of inference steps is 'nil', you need to run 'setTimesteps' after creating the scheduler")
        }

        // Initialize stepIndex if it hasn't been set
        if self.stepIndex == nil {
            // Find the index(es) in timeSteps that match the current timeStep
            let indexCandidates = self.timeSteps.enumerated().filter { $0.element == t }.map { $0.offset }

            // Determine the step_index based on indexCandidates
            if indexCandidates.count > 1 {
                self.stepIndex = indexCandidates[1]
            } else if let firstIndex = indexCandidates.first {
                self.stepIndex = firstIndex
            } else {
                fatalError("Current timeStep not found in timeSteps")
            }
        }

        // 1. Compute the index for the previous timestep based on the current step index.
        let prevStepIndex = stepIndex! + 1
        let prevTimeStep = prevStepIndex < self.timeSteps.count ? self.timeSteps[prevStepIndex] : t

        // 2. compute alphas, betas
        let alphaProdT = self.alphasCumProd[t]
        let alphaProdTPrev = self.alphasCumProd[max(0, prevTimeStep)]
        let betaProdT = 1 - alphaProdT
        let betaProdTPrev = 1 - alphaProdTPrev

        // 3. Get scalings for boundary conditions
        let scaledTimeStep = Float32(t) * Float32(self.timeStepScaling)
        let sigmaDataSquared = Float32(0.5 * 0.5) // Assuming sigma_data is always 0.5 as per your setup
        let cSkip = sigmaDataSquared / (scaledTimeStep * scaledTimeStep + sigmaDataSquared)
        let cOut = scaledTimeStep / sqrt(scaledTimeStep * scaledTimeStep + sigmaDataSquared)

        // 4. Compute predicted original sample x_0 based on the model parameterization + apply clamping
        let betaProdTSqrt = sqrt(betaProdT)
        let alphaProdTSqrt = sqrt(alphaProdT)
        let predictedOrigSampleElements = zip(s.scalars, output.scalars).map { sampleElement, outputElement in
            (sampleElement - outputElement * betaProdTSqrt) / alphaProdTSqrt
        }.map { element in
            // Clamping each element
            min(max(element, -self.clipSampleRange), self.clipSampleRange)
        }
        let predictedOrigSample = try! MLShapedArray<Float32>(shape: s.shape, scalars: predictedOrigSampleElements)

        // 6. Denoise model output using boundary conditions
        var denoised = clampedPredictedOrigSampleArray * cOut + s * cSkip

        // 7. Sample and inject noise z ~ N(0, I) for MultiStep Inference, if not the final timestep
        if stepIndex != self.inferenceStepCount - 1 {
            let noise = MLShapedArray<Float32>(randomNormalShape: output.shape, mean: 0, stddev: 1)
            let prevSample = denoised.multiplying(by: sqrt(alphaProdTPrev)).adding(noise.multiplying(by: sqrt(betaProdTPrev)))
            denoised = prevSample
        }

        // Update the step index for the next call to `step`
        self.stepIndex = stepIndex + 1

        return denoised
    }
}

Any help is welcome! Thank you 😃

@GuiyeC has an implementation over on the https://github.com/guernikacore/schedulers repo which may help
https://github.com/GuernikaCore/Schedulers/blob/main/Sources/Schedulers/LCMScheduler.swift

Oh that's great, I did not find any implementation when I looked for it. Thank you!

authors: JustinMeans ThibaultCastells

repo: apple/ml-stable-diffusion


text:
Windows extension over Collections doesn't work

I was playing around with your package and decided to take a look at a Windows example. After setting a very simple playground and trying this example, I can not build it. Instead of building it, it throws the next error:
/path/to/playground/main.swift:5:32: error: value of type 'String' has no member 'windows'
let windowed: [String] = swift.windows(ofCount: 2)

First of all, I thought that there is something on my end, however, other examples work fine(I've tried this and this)
Swift Algorithms version: 0.0.2
Swift version: Apple Swift version 5.3.2 (swiftlang-1200.0.45 clang-1200.0.32.28) Target: x86_64-apple-darwin20.3.0
Checklist

[x] If possible, I've reproduced the issue using the main branch of this package
[x] I've searched for existing GitHub issues

Steps to Reproduce
Here is my Package.swift:
import PackageDescription

let package = Package(
    name: "playground",
    dependencies: [
        .package(url: "https://github.com/apple/swift-algorithms", from: "0.0.2"),
    ],
    targets: [
        .target(
            name: "playground",
            dependencies: [
                .product(name: "Algorithms", package: "swift-algorithms"),
            ],
            path: "Sources/playground"
            ),
    ]
)

and main.swift:
import Foundation
import Algorithms
let swift = "swift"

let windowed: [String] = swift.windows(ofCount: 2)
print(windowed)

Expected behavior
I expected to see the next result: ["sw", "wi", "if", "ft"]
Actual behavior
I get the error after running swift build:
/path/to/playground/main.swift:5:32: error: value of type 'String' has no member 'windows'
let windowed: [String] = swift.windows(ofCount: 2)

Version 0.0.2 was released in October, and it did not yet include the windows(ofCount:) method. It will be included in the upcoming 0.0.3 release, and if you'd like to start using it right now, you can already depend on the main branch instead:
.package(url: "http://github.com/apple/swift-algorithms", .branch("main"))

Thanks for the clarification, it makes sense.

repo: apple/swift-algorithms


text:
validate() is not called on parent commands even though their arguments are required

When a subcommand is parsed and executed, its parent command arguments are parsed but validate() is never called.  It seems odd that the arguments are required for the command to be accepted, but are not validated.
ArgumentParser version: master
Swift version: Apple Swift version 5.2
Checklist

[x] If possible, I've reproduced the issue using the master branch of this package
[x] I've searched for existing GitHub issues

Steps to Reproduce
private struct BaseCommand: ParsableCommand {
  static var configuration = CommandConfiguration(
    commandName: "base",
    subcommands: [SubCommand.self]
  )

  @Option()
  var baseFlag: String

  mutating func validate() throws {
    throw HelpRequested
  }
}

extension BaseCommand {
  struct SubCommand : ParsableCommand {
    static var configuration = CommandConfiguration(commandName: "sub")

    @Flag()
    var subFlag: Bool

    mutating func validate() throws {
      print("Validated SubCommand")
    }
  }
}

Expected behavior
Because --base-flag is required for the command to run, I would expect at the least that BaseCommand.validate() be called.
Actual behavior
BaseCommand.validate() is never called when invoking SubCommand

Fixed by #104! Thanks @kennyyork!

repo: apple/swift-argument-parser


text:
[SR-2509] Add tests to assure that the issue is fixed

It seems like SR-2509 is already fixed. I added a couple of additional tests to make sure that the CharacterSet.union() works as expected.
I tested it on macOS 10.12.6 + Xcode 9.0 + Swift 4.0 and also on Ubuntu 14.04 + swift-4.0.2-RELEASE-ubuntu14.04

Great, thanks for the work.
@swift-ci please test and merge

Thanks!

authors: alblue parkera sashabelonogov

repo: apple/swift-corelibs-foundation


text:
Foundation: repair the Windows build

Unwrap the optional type before accessing the member.

@swift-ci please test


text:
bugfix in Linux wrapper: DispatchGroup.leave should call leave, not e…

…nter!

wow, we need this for swift-3.0
@mwwa do we have the same bug in the compiler?

@MadCoder No, the compiler uses APINotes to rename dispatch_group_leave -> DispatchGroup.leave(self:)

I'm pretty sure it was my own stupid cut & paste error when writing the wrapper.  Scary.  We really need to get some tests of the Swift API.    I found this while debugging a disabled test case in TestNSOperationQueue from the Foundation test suite (test_OperationPriorities was hanging because leave wasn't wired correctly).

authors: MadCoder dgrove-oss mwwa

repo: apple/swift-corelibs-libdispatch


text:
Add Dockerfile for Debian 10 plus changes for Debian 9

Same dependencies for Debian 10 as Ubuntu 20.04

Please advice how I test this. Locally and in CI?

@swift-ci Please test

n

n

CC @shahmishal

@swift-ci test

PASSED_swift-ci_master_debian_10.log
PASSED_swift-ci_master_debian_9.log

-- Looking for os_signpost_interval_begin - not found
CMake Error at /home/build-user/cmake/Modules/FindPackageHandleStandardArgs.cmake:146 (message):
  Could NOT find Python3 (missing: Python3_EXECUTABLE Interpreter)
Call Stack (most recent call first):
  /home/build-user/cmake/Modules/FindPackageHandleStandardArgs.cmake:393 (_FPHSA_FAILURE_MESSAGE)
  /home/build-user/cmake/Modules/FindPython/Support.cmake:2261 (find_package_handle_standard_args)
  /home/build-user/cmake/Modules/FindPython3.cmake:300 (include)
  CMakeLists.txt:711 (find_package)

-- Configuring incomplete, errors occurred!
See also "/home/build-user/build/buildbot_linux/llvm-linux-x86_64/CMakeFiles/CMakeOutput.log".
See also "/home/build-user/build/buildbot_linux/llvm-linux-x86_64/CMakeFiles/CMakeError.log".
Building the standard library for: swift-stdlib-linux-x86_64
Running Swift tests for: check-swift-all-linux-x86_64 check-swift-all-optimize-linux-x86_64
ERROR: command terminated with a non-zero exit status 1, aborting

ERROR: command terminated with a non-zero exit status 1, aborting

Debian 9 is missing python3.

Is debian 9 interesting? I know it's not EOL yet (June 30, 2022).

Sounds good, we can focus on getting Debian 10 configured.

/usr/bin/ld: lib/hwasan/CMakeFiles/RTHwasan_dynamic.x86_64.dir/hwasan.cpp.o: relocation R_X86_64_PC32 against undefined symbol `__ehdr_start' can not be used when making a shared object; recompile with -fPIC
/usr/bin/ld: final link failed: nonrepresentable section on output
clang-10: error: linker command failed with exit code 1 (use -v to see invocation)

Debian 10 failure - https://ci.swift.org/job/oss-swift-package-debian-10/2/console

hmm I would love to help, but I am not sure how I can. It is building on x86_64 which I also have..  and still failing..
This is happening in a Debian 10 virtual machine?

I can build on a real machine (but that won't be clean) and in a docker Debian (as clean as you have), but it seems that I am missing a bit of the puzzle.

authors: jianjun1121 schafdog shahmishal weissi

repo: apple/swift-docker


text:
FoundationEssentials: use named constants for characters

Use more named constants when checking for matching constants in the string.

@swift-ci please test

@swift-ci please test

repo: apple/swift-foundation


text:
[CMake] Cherry-pick upstream LLVMDistributionSupport.cmake

This extracts the LLVM distribution target handling into a support module.
Extraction will enable us to restructure the builds to support multiple
distribution configurations (e.g. developer and user) to permit us to build the
development package and the user package at once.
git-svn-id: https://llvm.org/svn/llvm-project/llvm/trunk@363440 91177308-0d34-0410-b5e6-96231b3b80d8

@weliveindetail - could you please rebase this branch?  The change should be made against the wift-5.1-branch.  Once that is verified it will flow into stable.

The change should be made against the wift-5.1-branch. Once that is verified it will flow into stable.

Not sure we want a change like this in swift-5.1-branch on this point.

This won't work. I will temporarily add LLVMDistributionSupport.cmake to the CMake modules on swift-lldb:stable instead.

authors: compnerd weliveindetail

repo: apple/swift-llvm


text:
analyse what we do when getting close/over the fd limits and make sure we don't fatal error when hitting limits

currently we fatalError when we hit a maximum number of file descriptors. We should let the application code handle that.

@weissi can you tell me where exactly you see this ? As far as I can tell we allow the user to handle it when accepting connections.

@normanmaurer that was feedback from @vlm that I wrote up badly during a meeting :)

we do, I have seen this in some unit tests.
Fatal error: 'try!' expression unexpectedly raised an error: kqueue() failed: Too many open files (errno: 24): file /tmp/.nio-release-tools_pVH7Q0/swift-nio/Sources/NIO/EventLoop.swift, line 1097
Exited with signal code 4

authors: normanmaurer weissi

repo: apple/swift-nio


text:
Add RelativePath validating init

Validating RelativePath checks first symbols not to be "/" or "~" and throws PathValidationError.invalidRelativePath otherwise

@swift-ci please smoke test

LGTM, thanks!!!!

@swift-ci please smoke test

@swift-ci please smoke test

repo: apple/swift-package-manager


text:
Process stats evaluate and lit diagnostics docs

This adds a new mode to process-stats-dir.py that handles evaluating expressions over specific
stats-dir values. Also includes mention of a lit.py mode I had to employ today, as per @gottesmm's
request.

@swift-ci please test and merge

@swift-ci please test Linux platform

@graydon Thanks for adding the docs!

authors: gottesmm graydon

repo: apple/swift


text:
[ClangImporter] Handle subscript getters redeclared in subclasses

Explanation: Swift accidentally assumed that whenever an Objective-C subscript getter method and setter method were declared in different places, the setter was always going to be in a subclass (turning a read-only subscript into a read/write one). That's not true if there are redeclarations involved. The fix is to check if the two methods are in different classes and prefer the accessor we started with.
Scope: Affects how Objective-C subscripts are imported if the getter and setter are declared in different places.
Issue: rdar://problem/36033356
Reviewed by: @DougGregor
Risk: Medium-low. This kind of change for Objective-C subscripts isn't super common.
Testing: Added compiler regression tests.

@swift-ci Please test


text:
[Parse] Small cleanups in parseBraceItems()

Reorder if ... else if branches to simplify conditions.
Use SmallVectorImpl::append() instead of for { push_back() }
Inline skipExtraTopLevelRBraces().  Removed it from parseTopLevel(). There's no particular reason to diagnose it in parseTopLevel().

@swift-ci Please test

@DougGregor Please post-commit review this if you have chance.


text:
SILGen Tests

Replace this paragraph with a description of your changes and rationale. Provide links to external references/discussions if appropriate.

Resolves SR-NNNN.

@swift-ci please test

Build failed
Swift Test Linux Platform
Git Sha - 0e194a942692f402c8f458a10bbf6fc892962852

Build failed
Swift Test OS X Platform
Git Sha - 0e194a942692f402c8f458a10bbf6fc892962852

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - b246040e73a6d619d228fdafa7e1029feec0dffe

Build failed
Swift Test Linux Platform
Git Sha - b246040e73a6d619d228fdafa7e1029feec0dffe

CC: @aschwaighofer @jrose-apple suggestions as to why there are differences between the platforms here?

@swift-ci please smoke test macOS platform

Darwin Failing Tests:
Swift(macosx-x86_64).SILGen.without_actually_escaping_block.swift
Swift(macosx-x86_64).SILGen.metatype_in_init_delegation.swift
Swift(macosx-x86_64).SILGen.objc_bridging.swift
Swift(macosx-x86_64).IRGen.newtype.swift
Swift(macosx-x86_64).IDE.newtype.swift

@swift-ci please smoke test macOS platform

@swift-ci please smoke test macOS platform

@swift-ci please smoke test macOS platform

@swift-ci please smoke test

@swift-ci please smoke test

authors: compnerd swift-ci