com.cloudant.client.org.lightcouch.CouchDbException: Error retrieving server response

Please include the following information in your ticket.

CloudantClient (java-cloudant) version(s) that are affected by this issue.
  <dependency>
  	<groupId>com.cloudant</groupId>
  	<artifactId>cloudant-client</artifactId>
  	<version>2.2.0</version>
  </dependency>

Java version (including vendor and platform).
/Library/Java/JavaVirtualMachines/jdk1.8.0_101.jdk/
macOS, version: 10.12

If you're using the optional okhttp dependency.
NO

A small code sample that demonstrates the issue.
======================================

I'm able to connect database, and run methods like:

db.info()

Server Version: 1.6.1
All my databases :
_replicator
_users
dash-um-db
example_db
or

db.find(MyClassTO.class, "c947fa06f8a03d90eddd4b3a3b002b36")

are working very well.
But, when I try use methods like:
// Check index
db.createIndex("type", null, null, new IndexField[] {
new IndexField("type",SortOrder.asc)});
or
// Find
List myTOList = db.findByIndex(""selector": {"type": "adoption"}", AdoptionTO.class);
System.out.println("myTOList " + myTOList);
I have this issue:
[err] Caused by: java.net.ProtocolException: Server rejected operation
[err] 	at sun.net.www.protocol.http.HttpURLConnection.expect100Continue(HttpURLConnection.java:1218)
[err] 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream0(HttpURLConnection.java:1297)
[err] 	at sun.net.www.protocol.http.HttpURLConnection.getOutputStream(HttpURLConnection.java:1258)
[err] 	at com.cloudant.http.HttpConnection.execute(HttpConnection.java:233)
[err] 	at com.cloudant.client.org.lightcouch.CouchDbClient.execute(CouchDbClient.java:475)
[err] 	... 82 more
Any idea ?
Thanks.
Sandro

This is basically the same problem as #218 and has been fixed since version 2.4.1.
I recommend using the latest release 2.6.2.

Hi,
I updated versions, now I'm using:
cloudant-client-2.6.2.jar
cloudant-http-2.6.2.jar
commons-codec-1.6.jar
commons-io-2.4.jar gson-2.7.jar
And I'm receiving another ERROR message, looks like PUT commands don't working.
==============================
These commands are working very well:
// Note: for Cloudant Local or Apache CouchDB use:
CloudantClient client = ClientBuilder.url(new URL("http://<IP_ADDRESS>:5984")).username("admin")
.password("xxxx").disableSSLAuthentication().build();
// Show the server version
System.out.println("Server Version: " + client.serverVersion());
// Show databases
System.out.println("Dbs: " + client.getAllDbs());
// Get database
Database db1 = client.database("dash-db", true);
==============================
These commands are NOT working :
=> not working!
db1.createIndex("type", "type", null, new IndexField[]{
new IndexField("type",SortOrder.asc)});
=> not working
List objTOList = db.findByIndex(""selector": {"type": "adoption"}", ObjTO.class);
System.out.println("objTOList " + objTOList);
Exception =>
CouchDbInfo [dbName=dash-um-db, docCount=4, docDelCount=4, updateSeq=16, purgeSeq=0, compactRunning=false, diskSize=65640, instanceStartTime=1477654845132730, diskFormatVersion=6]
[err] com.cloudant.client.org.lightcouch.CouchDbException: 400 Bad Request: bad_request: Referer header required.
[err] 	at com.cloudant.client.org.lightcouch.CouchDbClient.execute(CouchDbClient.java:524)
[err] 	at com.cloudant.client.org.lightcouch.CouchDbClient.executeToInputStream(CouchDbClient.java:572)
[err] 	at com.cloudant.client.api.Database.createIndex(Database.java:305)
[err] 	at com.cloudant.client.api.Database.createIndex(Database.java:288)
Any idea, thanks !

This appears to be the same as #313, discussion will take place there. Let us know if this is not the case.


Better wording for modules_all_together

In here:
https://nodejs.org/api/modules.html#modules_all_together
IMHO,
please change
require(X) from module at path Y
1...
2...
3. If X begins with './' or '/' or '../'
   a. LOAD_AS_FILE(Y + X)
   b. LOAD_AS_DIRECTORY(Y + X)

LOAD_AS_DIRECTORY(X)
1...
2. LOAD_INDEX(X)

into
require(X) from module at path Y
1...
2...
3. If X begins with './' or '/' or '../'
   a. LOAD_AS_FILE(Y + X)
   b. LOAD_AS_DIRECTORY(Y + X)
   c. LOAD_INDEX(Y + X)

LOAD_AS_DIRECTORY(X)
1...

which is less nested thus easier to understand.

@buckle2000 Could you give more details? Why is it more conventional? What do you mean by that?

In current description of this, LOAD_INDEX is nested in LOAD_AS_DIRECTORY, which is unnecessary and seems confusing (at least to me).

Closing as this repository is dormant and likely to be archived soon. If this is still an issue, feel free to open it as an issue on the main node repository.


Using traits ans structures from the standard library

capnproto-rust redefines some traits / structures that seem to exist in the standard library, such as BufferedReader and BufferedWriter and the corresponding wrappers, but with a few changes.
Is there a particular reason to redefine those traits and structures, such as an insufficent API or too much API instability? Or is it there more for legacy reasons?

Thanks to https://github.com/dwrensha/capnproto-rust/pull/41, we now do use the standard traits.


[WIP] Test benches with stats exporter

What does this PR do?
A brief description of the change being made with this pull request.
Motivation
What inspired you to submit this pull request?
Additional Notes
Anything else we should know when reviewing?
How to test the change?
Describe here in detail how the change can be validated.

Codecov Report
Attention: Patch coverage is 90.63963% with 60 lines in your changes missing coverage. Please review.

Project coverage is 73.48%. Comparing base (89f48d4) to head (0b5f57c).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #640      +/-   ##
==========================================
+ Coverage   73.05%   73.48%   +0.43%
==========================================
  Files         252      253       +1
  Lines       36093    36691     +598
==========================================
+ Hits        26366    26961     +595
- Misses       9727     9730       +3

Components
Coverage Δ

crashtracker
20.53% <ø> (ø)

datadog-alloc
98.73% <ø> (ø)

data-pipeline
91.67% <90.35%> (+1.54%)
:arrow_up:

data-pipeline-ffi
0.00% <0.00%> (ø)

ddcommon
83.08% <ø> (ø)

ddcommon-ffi
69.52% <ø> (ø)

ddtelemetry
59.10% <ø> (ø)

ipc
83.63% <ø> (ø)

profiling
84.26% <ø> (ø)

profiling-ffi
77.42% <ø> (ø)

serverless
0.00% <ø> (ø)

sidecar
40.12% <ø> (ø)

sidecar-ffi
0.00% <ø> (ø)

spawn-worker
50.36% <ø> (ø)

tinybytes
91.66% <ø> (ø)

trace-mini-agent
72.49% <ø> (ø)

trace-normalization
98.25% <ø> (ø)

trace-obfuscation
95.73% <ø> (ø)

trace-protobuf
77.67% <ø> (ø)

trace-utils
93.59% <100.00%> (+0.70%)
:arrow_up:


Spelling

This PR corrects misspellings identified by the check-spelling action.
The misspellings have been reported at https://github.com/jsoref/control-flag/commit/b1907620029908ea31e0df30bc3b42a035291d15#commitcomment-67928069
The action reports that the changes in this PR would make it happy: https://github.com/jsoref/control-flag/commit/6a55d47cb21eb8ff3e522b74593448b0a4a0db3a
Note: this PR does not include the action. If you're interested in running a spell check on every PR and push, that can be offered separately.

Thanks for mentioning check-spelling action. It is very useful. I will integrate it with this repository.


refactor: Removes the DASHBOARD_FILTERS_EXPERIMENTAL feature flag

SUMMARY
As part of the 4.0 approved initiatives, this PR removes the DASHBOARD_FILTERS_EXPERIMENTAL feature flag and the associated GroupByFilterPlugin.
TESTING INSTRUCTIONS
CI should be sufficient for merging this PR. We'll do a complete testing of 4.0 after all approved proposals are merged.
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

@michael-s-molina was there broad agreement to remove the groupby Filter? The reason I ask is because I don't think it's been marked as deprecated, and I believe some orgs may be using it. Ping @amitmiran137 @simcha90 @cccs-jc @cccs-rc for heads up and any concerns if you missed the discussion (not sure if this is relevant for your orgs or not).
While I'm sure this should rather be brought up in the town hall, I think there's good use cases for the groupby filter, and cleaning it up and adding full support to the ECharts plugin package could be a fairly low hanging fruit, and one that I could potentially take on if this is still deemed relevant for other users.

@villebro It's a good question. We can submit a specific proposal for lazy consensus for removing the GroupByFilterPlugin and see if someone is using it and is able to support it. If not, then let's remove it.

The drill by feature provides a similar functionality as the GroupByFilterPlugin and for that reason we may choose to remove the plugin.

@michael-s-molina was there broad agreement to remove the groupby Filter? The reason I ask is because I don't think it's been marked as deprecated, and I believe some orgs may be using it. Ping @amitmiran137 @simcha90 @cccs-jc @cccs-rc for heads up and any concerns if you missed the discussion (not sure if this is relevant for your orgs or not).
While I'm sure this should rather be brought up in the town hall, I think there's good use cases for the groupby filter, and cleaning it up and adding full support to the ECharts plugin package could be a fairly low hanging fruit, and one that I could potentially take on if this is still deemed relevant for other users.

Thanks for the heads up @villebro! We're not currently using the Group By filters, but admittedly that's only because I hadn't spotted the feature flag before. I agree there are good use cases for it that aren't entirely covered by the drill by feature.


[MINOR][DOCS] Add spark 3 support matrix

Committer checklist

[ ] Has a corresponding JIRA in PR title & commit

[ ] Commit message is descriptive of the change

[ ] CI is green

[ ] Necessary doc changes done or have another open PR

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

done in https://github.com/apache/hudi/pull/4396


Significant latency regression in both unary and streaming benchmarks on 2/19

https://performance-dot-grpc-testing.appspot.com/explore?dashboard=5685265389584384
On 2/19, there was a ~50% increase in unary benchmark and ~100% in streaming. Same regression didn't seem to occur to internal benchmarks.
@jtattermusch @nicolasnoble

@mhaidrygoog

Re internal regressions: on 2/19, we had a couple of regressions in internal benchmarks as well. It's unclear to me if they are related at all.

I can't run custom queries to access the older data on the dashboard. The data from the current snapshot has been overwritten. @jtattermusch  Please provide access.

@jtattermusch Thanks for the pointers with the dashboard, proceeding ahead

I was able to edit the dashboard data to see the range of starting commit  ids where we start seeing the performance regression. I am going to setup a script to run the last few commits before that and see which commit exactly may have caused the issue

I've run a couple of experiments that suggest that reason for this regression may be the environment the benchmarks are running on and not necessarily any PR within gRPC
The first observation was after modifying the dashboard query to display git the commit id in addition to the latency and display this as a table vs a graph. I saw that the benchmarks ran on the same commit for 3 consecutive days (Feb-17-Feb19) and the change in the performance numbers all occurred on the same commit.

The second experiment was to run unary and streaming scenarios in a separate GCE setup on the las 20 commits before the commit I identified above and see if there is a performance regression because of any particular commit. My analysis didn't pinpoint any particular commit.

The regression is also noticeable for other languages in the multi-language dashboard

link

Based on the analysis up till now I'm ruling out gRPC C++ as the root cause and downgrading this bug to P1


ChaNGa deadlocks due to recent change to QD types

Original author: Thomas Quinn (@trquinn)
Original issue: https://charm.cs.illinois.edu/redmine/issues/1830

I'm getting a deadlock when running ChaNGa with recent versions of charm.  "git bisect" says that the problem commit is:
commit 3137ae773a8af5bd476beafaeee4dabd168062bd
Change-Id: I2aed14aac27ea12b7f5680a602671f95bc78910d
QD: Convert to use more suitable types
Hence I suspect a race condition after moving from ints to CmiUInt8 for the QD counters.
Charm is built with:
./build ChaNGa gni-crayxc hugepages smp -j8 --with-production
using gcc 7.1.0.

Original date: 2018-03-13 03:02:52

Does this patch fix the problem? ~~https://charm.cs.illinois.edu/gerrit/#/c/3844/~~ https://github.com/UIUC-PPL/charm/commit/42ce6c964d9b0bea889e5e18a48b61c383ee60c6

Original author: Thomas Quinn (@trquinn)
Original date: 2018-03-13 20:29:10

I tried changeset 3844, and I still get the hang.

Original date: 2018-03-13 23:49:19

But reverting 2897 makes the problem go away?
~~https://charm.cs.illinois.edu/gerrit/#/c/2897/~~ https://github.com/UIUC-PPL/charm/commit/3137ae773a8af5bd476beafaeee4dabd168062bd

Original author: Thomas Quinn (@trquinn)
Original date: 2018-03-14 04:21:40

The problem goes away if I run with commit 8de6719c613f34a3d6b1baccb9aa4aa8f78c12db, the commit before 2897.

Original date: 2018-03-14 15:33:00

K we can just revert that change for now then, since I'm not sure how that is causing a problem and it's an easy one to revert.

Original date: 2018-03-14 15:35:04

Revert commit: ~~https://charm.cs.illinois.edu/gerrit/#/c/3848/~~ https://github.com/UIUC-PPL/charm/commit/13db845c266960f9428e1e0a32541787a3069727

Original date: 2018-03-14 15:48:08

Could you provide the run command for ChaNGa that reproduces the deadlock? In case we want to pursue the datatype change in the future, we'll need to be able to run this case

Original date: 2018-03-14 20:25:25

Actually, we found another issue in the original patch, I updated this patch to fix that. Can you try ChaNGa on the updated version of this patch? ~~https://charm.cs.illinois.edu/gerrit/#/c/3844/~~ https://github.com/UIUC-PPL/charm/commit/42ce6c964d9b0bea889e5e18a48b61c383ee60c6

Original author: Thomas Quinn (@trquinn)
Original date: 2018-03-15 01:20:58

Commit 6b1b6d708 fixes the problem.


nfs: Enable CSI-NFS for Docker

This patch enables support for CSI-NFS for Docker.

Codecov Report

Merging #1063 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1063      +/-   ##
==========================================
- Coverage   34.19%   34.16%   -0.04%
==========================================
  Files          36       36
  Lines        2901     2901
==========================================
- Hits          992      991       -1
- Misses       1806     1807       +1
  Partials      103      103

Impacted Files
Coverage Δ

libstorage/api/types/types_localdevices.go
84.93% <0%> (-1.37%)
:arrow_down:

Continue to review full report at Codecov.

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

Build and Test in Travis-CI look good.


Additions to .gitignore

Additions to .gitignore that are helpful when working under Git on Windows
The Visual C++ compiler creates *.obj files (which have the same purpose as the *.o files under GNU/Linux). These are ignored. Also added a rule to ignore selfie.exe, too.

@nubok This is also not needed as already stated in #31. But thanks for your interest.


update to config map to make data value hashed

Short description:
More details:
What this PR does / why we need it:
Which issue(s) this PR fixes:
Special notes for reviewer:
Bug:

Summary by CodeRabbit

New Features

Introduced a new ConfigMap class for managing configuration data in Kubernetes.
Added functionality for handling binary data and configuration data with validation.
Implemented a method for converting ConfigMap instances to a dictionary format for API requests.

Deprecation Notice

Removed the old ConfigMap class and issued a deprecation warning for users to transition to the new module.

Report bugs in Issues
The following are automatically added:

Add reviewers from OWNER file (in the root of the repository) under reviewers section.
Set PR size label.
New issue is created for the PR. (Closed when PR is merged/closed)
Run pre-commit if .pre-commit-config.yaml exists in the repo.

Available user actions:

To mark PR as WIP comment /wip to the PR, To remove it from the PR comment /wip cancel to the PR.
To block merging of PR comment /hold, To un-block merging of PR comment /hold cancel.
To mark PR as verified comment /verified to the PR, to un-verify comment /verified cancel to the PR.
verified label removed on each new commit push.
To cherry pick a merged PR comment /cherry-pick <target branch to cherry-pick to> in the PR.

Multiple target branches can be cherry-picked, separated by spaces. (/cherry-pick branch1 branch2)
Cherry-pick will be started when PR is merged

To build and push container image command /build-and-push-container in the PR (tag will be the PR number).

You can add extra args to the Podman build command

Example: /build-and-push-container --build-arg OPENSHIFT_PYTHON_WRAPPER_COMMIT=<commit_hash>

To add a label by comment use /<label name>, to remove, use /<label name> cancel
To assign reviewers based on OWNERS file use /assign-reviewers
To check if PR can be merged use /check-can-merge

Supported /retest check runs

/retest tox: Retest tox
/retest python-module-install: Retest python-module-install

Supported labels

hold
verified
wip
lgtm

/verified

@dbasunag
I don't understand how the title of this PR is related to the content of this PR, can you explain?

@dbasunag I don't understand how the title of this PR is related to the content of this PR, can you explain?

Now I saw this def keys_to_hash(self):  and understand

/verified


fix bug

got a report from customer: https://pinterest.slack.com/archives/CBLQ8DR09/p1729286470537209

Before the fix, if the cluster didn't exist in AWS ASG, the page would display an error:

After the fix, the page opens successfully without any issues:


[feature] #2899: Add multi-instructions subcommand into client_cli

Signed-off-by: Vladimir Pesterev<EMAIL_ADDRESS>

Description of the Change
More details about the suggestion you can find here.
I spent some time trying to reuse GenesisTransactions format (configs/peer/genesis.json) but it's a bad way cause demand depends on iroha_core and a lot of boilerplate code being converted. But I noticed that we can just use Serialize/Deserialize which already implemented for Instructions and use those traits to represent instructions as JSON. As a result, I got a way to make a more convenient and simple implementation of this command.
Issue
Closes #2899
Benefits
Submit multiple instructions using one command
Possible Drawbacks
None
Usage Examples or Tests
Save these instructions into a file:
[
    {
        "Register": {
            "Identifiable": {
                "NewDomain": {
                    "id": "neverland",
                    "logo": null,
                    "metadata": {}
                }
            }
        }
    },
    {
        "Register": {
            "Identifiable": {
                "NewAccount": {
                    "id": "steve@neverland",
                    "signatories": [
                        "ed0120cc25624d62896d3a0bfd8940f928dc2abf27cc57cefeb442aa96d9081aae58a1"
                    ],
                    "metadata": {}
                }
            }
        }
    },
    {
        "Register": {
            "Identifiable": {
                "NewAssetDefinition": {
                    "id": "sapporo#neverland",
                    "value_type": "Quantity",
                    "mintable": "Infinitely",
                    "metadata": {}
                }
            }
        }
    },
    {
        "Mint": {
            "object": {
                "U32": 1010
            },
            "destination_id": {
                "Id": {
                    "AssetId": "sapporo##steve@neverland"
                }
            }
        }
    }
]

And then pass to client_cli like this:
cat ./test.json | ./iroha_client_cli json

Short and sweet. Excellent.


How to use dynamic timelineItems?

I want to use different timelineItems in different positions, I tried to use the following code:
var timelineSlider = L.control.timelineSlider({
                timelineItems: ["Day 1", "The Next Day", "Amazing Event", "1776", "12/22/63", "1984"],
                extraChangeMapParams: {greeting: "Hello World!"},
                changeMap: getDataAddMarkers
              });
    timelineSlider.addTo(map);
... ...

       // Change timelineItems in a callback function
        timelineSlider.remove();
        timelineSlider = L.control.timelineSlider({
                  timelineItems: timelineItems,
                  extraChangeMapParams: {greeting: "Hello World!"},
                  changeMap: getDataAddMarkers
                });
        timelineSlider.addTo(map);

I used the method of removing and adding to update. The user interface display is updated, but the click operation is no longer possible at the time.

What do you mean by the click operation? Can you show me a reprex?

What do you mean by the click operation? Can you show me a reprex?

Click the point on the timeline.

Cannot click the point on the timeline after modification.

I'm really sorry for getting back to this so late, other things have come up and I am just getting around to fixing issues for this. Could you go into more detail about how you are changing the timelineItems parameter in a callback? Have you found a resolution for this issue in the meantime?


adding id in container

Is it possible to add id in a container/div via the builder? I am trying to do a collapsible (show/hide) container.

no need, done via classname


Update README.md

Add ArduPilot

Thanks for your Pull Request. This is a good addition.

Thanks for your Pull Request. This is a good addition.


Avoid dependency on REDIS

I understand that with OAuth additions we have made that we have introduced a (optional) dependency on REDIS in apicast?
Can someone confirm/deny/explain it a bit more and the need.
I think it would be great it we could find other ways to solve the same need and keep the simple apicast deployment as simple as possible.

I am not sure, but I believe it's needed when there is more than 1 instance of APIcast. They need to share the cache to store the temporary code used in OAuth, and then retrieve it.
Not sure we can get rid of it completely.
For sure what would be very good is to abstract the cache calls, and make it possible to switch between Redis, local nginx cache or anything else with just adjusting the configuration.

IMO, if we need more than one (live) APIcast needed then maybe they should be deploying XC - or they will be hammering backend.
If there is more than one apicast (for redundancy or other reasons), then no need to ensure cache is shared (and it won't be HA...).

The problem is that in the oauth flow in a subset of the oauth flows the gateway has to maintain state to match the auth code to the access token and client ID. There are basically no single instance gateway deployments in production, so we cannot assume any constraint this dimension.
Options:

manage the oauth dance in a different manner
make all oauth a plugin with redis a dependency if that is enabled
only make redis a dependency for the specific oauth flows which require it

The driver for more than one gateway instance is HA, and usually this is configured in a load balanced active-active mode.

If all this is all true, then the differences between vanilla-apicast and xc are getting smaller and smaller and we should consider that in the roadmap.
More importantly, if I understand things correctly:

dependency on redis was added (by Pili I think) in the docker compose. This is used in some paths of the OAuth code that was added recently?
there no dependency on a redis image in the OpenShift template in apicast.
So, anyone starting apicast (RC1 or HEAD) now in OpenShift will be able to try an OAuth flow that follows a code path that tries to access a non-existent REDIS, and it will all fail.

Is that correct?

@andrewdavidmackenzie I think that's correct.
Probably the easiest way to fix this in short term would be to add REDIS_HOST and REDIS_PORT env vars / params to the OpenShift template, and make it clear in the documentation that having a working instance of Redis running somewhere (REDIS_HOST:REDIS_PORT) is a prerequisite for the OAuth authentication method.

Hello,
Do you know if a single shared Redis between multiple APIcasts is supported?
It seems to be according to this article:
https://stackoverflow.com/questions/27217502/using-redis-as-a-cache-storage-for-for-multiple-application-on-the-same-server
But I would like to confirm with you as well.
Thanks.

@estevaobk that is the point of Redis: to be the shared data store between several instances, so yes.

Redis is only used in the Oauth2.0 flow that's deprecated, so this is no longer an issue.
Redis can also be used in the rate-limit policy, but it's optional, so closing this issue.


Violations are not saved to GCS

After installing RC2, did a forseti notifier run on the client VM, the notifier reports a problem and no violation is found on GCS.

relates to issue #1315 , to get actual useful error messages for debugging

Just running the cloudsql notification will work fine, both email and gcs bucket.

Narrowed this down to the IAP notification.

Want me to look at this?

Yes, please!
On Wed, Mar 28, 2018 at 6:15 AM, Muharem Hrnjadovic <
<EMAIL_ADDRESS>wrote:

Want me to look at this?
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/GoogleCloudPlatform/forseti-security/issues/1316#issuecomment-376882239,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AGp4CAlgR6Mv5FRG5dmqL06pxnjinwAWks5ti4zogaJpZM4S9hyP
.

Testing against
commit aa3f63e0023cddf006cd3818d3f865ee5c16b471
Merge: 39030cd0 db09dfbc
Author: joecheuk<EMAIL_ADDRESS>Date:   Tue Mar 27 20:16:41 2018

    Merge branch '2.0-rc2' into 2.0-dev

IAP email notifications work

server says
server_message: "Retrieved 50 violations for resource \'policy_violations\'"
server_message: "Retrieved 1 violations for resource \'iap_violations\'"
server_message: "Retrieved 1 violations for resource \'instance_network_interface_violations\'"
server_message: "Retrieved 1 violations for resource \'forwarding_rule_violations\'"
server_message: "Running \'email_violations\' notifier for resource \'iap_violations\'"
server_message: "Running \'gcs_violations\' notifier for resource \'iap_violations\'"
server_message: "Notification completed!"

However, I do not see the GCS upload. Looking into that now.

Oops, gsutil ls sorting order threw me off :-P
The GCS upload was actually performed as well. IOW, cannot reproduce this issue on my end.
(fsec) forseti-security $ gsutil ls -l gs://forset-violations/scanner_violations/ | head -n3
      1226  2018-04-02T09:41:55Z  gs://forset-violations/scanner_violations/violations.iap_violations.2018-03-24T00:49:02.891287.20180402T094154Z.csv
      1226  2018-04-02T09:55:18Z  gs://forset-violations/scanner_violations/violations.iap_violations.2018-03-24T00:49:02.891287.20180402T095517Z.csv
     65084  2018-03-20T21:23:08Z  gs://forset-violations/scanner_violations/violations.policy_violations.2018-03-14T14:49:36.101287.20180320T212307Z.json


[WIP] Python Support

Pull Request Checklist

[ ] Testing

Unit test added (prefer not to modify an existing test, otherwise, it's probably a breaking change)
CLI change?: coordinate update of integration tests with team
cdk-init template change?: coordinated update of integration tests with team

[ ] Docs

jsdocs: All public APIs documented
README: README and/or documentation topic updated

[ ] Title and Description

Change type: title prefixed with fix, feat will appear in changelog
Title: use lower-case and doesn't end with a period
Breaking?: last paragraph: "BREAKING CHANGE: <describe what changed + link for details>"
Issues: Indicate issues fixed via: "Fixes #xxx" or "Closes #xxx"

[ ] Sensitive Modules (requires 2 PR approvers)

IAM Policy Document (in @aws-cdk/aws-iam)
EC2 Security Groups and ACLs (in @aws-cdk/aws-ec2)
Grant APIs (only if not based on official documentation with a reference)

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license.

Built everything and installed it into a virtual environment, then ensured everything was importable by running:
import pkgutil
import importlib

import aws_cdk

for pkg in pkgutil.walk_packages(aws_cdk.__path__, "aws_cdk."):
    print(f"Importing {pkg.name}")
    importlib.import_module(pkg.name)

That does not ensure it's functioning, but it is at least importable.

Don't forget to update create-missing-libraries.ts, it will be invoked to bootstrap a new package.

Approved conditional of name changes


Enable isolatedProjectsIntegTest on :enterprise subproject

Follow-up to #29013
Reviewing cheatsheet
Before merging the PR, comments starting with

❌ ❓must be fixed
🤔 💅 should be fixed
💭 may be fixed
🎉 celebrate happy things

@bot-gradle test

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build


Fix check to enable/disable Terrain Ruler coloring/distance

Barely worth a PR.
window.terrainRuler is truthy if it exists, but it should check window.terrainRuler.active to make sure we actually want it on anyway. The check to make sure the variable exists in the first place is probably redundant but I'm being paranoid.
This does have the minor effect of a "desync", where the colors/distance traveled are client-side based on whether the client user has terrain ruler enabled, so they might see something different from the dragger, but that's minimal.

Hi there. Thanks for the PR. I don't think drag ruler should respect the terrain ruler toggle. The toggle makes a lot of sense for the regular ruler, as that one might be used to either measure air-line distance (where terrain doesn't apply) or to measure movement (where the terrain does apply). Since Drag Ruler only ever activates when dragging a token, it only measures movement and as such terrain should always be respected. Are there any notable exceptions to this that I'm missing?

The original reason this came up is for tokens that should ignore difficult terrain for whatever reason - I'm not sure about all systems, but it was brought up for LANCER originally for both flying tokens & tokens that ignore difficult terrain due to a feature they have (player characters with a specific ability or certain npcs). It means that you have to math their movement independently, which is mildly annoying, so I figured this was a minimally intrusive fix (just toggling it on/off before dragging).
(the full context is somebody had asked in the LANCER discord for something like this for use with flying characters so I fiddled around with it for them)


Readability Support

You should add a "read now" button which leverages Readability for formatting the news post. It's quite easy. Info for doing it is on readability's website. I've tested it in chrome's console and it works.

You say that I should, but not why I should. =p What's the higher-level goal/purpose here? Maybe I just don't understand what exactly it does; the page you linked provides zero instruction on how to actually use the code they give you, so I'm not sure how to test it myself.

Just add the div code to the webnews page.
As for why you should, it would be useful for reading those really looong posts like kurtz makes.

Having read Kurtz's walls-o-text in WebNews, I agree with you, but I think this is a simple enough goal that the external service isn't really needed. How about an unobtrusive "reading mode" toggle that defaults to Off when a new post is loaded? It could set a proportional font, increase the font size, and set a maximum line length. Maybe even kill the thread view so the content takes up all vertical space (the way the dashboard currently does).


No Status Bar Icon

TRex runs, but I don't see any status bar icon.

TRex has an option to hide menu bar icon in Preferences, could you have toggled it?
Open this URL trex://showPreferences, this will present TRex Preferences.

Oh, great thx!


Add status command

Fixes: https://github.com/ubuntu/microk8s/issues/155 https://github.com/ubuntu/microk8s/issues/115 https://github.com/ubuntu/microk8s/issues/174

Merging this. Please review at your own pace.


Important increase of size of apache/camel-k Docker image

Between 1.10.1 and 1.10.2 https://hub.docker.com/r/apache/camel-k/tags , the size increased from 367Mo to 601Mo.
Based on commiter @squakez , "it is worth to have a look. I cannot recall anything important that doubled the size of the image"

There is a clear difference in the image layers between 1.10.1 and +1.10.2.
I built the images locally for the v1.10.0, v1.10.1 and v1.10.2 tags from source and that resulted in container images with the sames layers and size range that the v1.10.2 that can be pulled from the official repos. I can't reproduce the original build images result for v1.10.1 and v1.10.0 from the sources.
I don't know how to interpret these observations, but it might be that the origin of the size increase is out of camel-k code (a change in a source image, the way images are built in the releasing process, ...).

Looking at the commit logs between v1.10.1 and v1.10.2, the only notable change made was upgrading Camel K Runtime 1.15.0 -> 1.15.1: https://github.com/apache/camel-k/commit/ba3912b758f01f48ca0c2bd3657029ee7e25293a I haven't looked into the Camel K Runtime side, but is it possible that the upgrade contributed to the size increase?

I think the point made by @gansheer is correct. There is a difference in the base layer we're using. Starting from the mandrel image used in version 1.10.2 there's a quite a lot of more statements. For instance, the following one:
COPY mandrel-java11-linux-amd64-<IP_ADDRESS>-Final.tar.gz /tmp/artifacts/ # buildkit

is used to copy some script and is not removed (it should be transparent to us). Maybe it should be checked directly with the support of Mandrel to see how they can shrink it accordingly.

The difference started in 21.2.x, there is more or less 240M more on recent image.

Do someone know what is the builder of theses quarkus mandrel images ?

I think it is build from here https://github.com/quarkusio/quarkus-images/tree/main/quarkus-mandrel-builder-image

From the information given on the issue open in the quarkus mandrel images repository, I would say we can close this issue. Is this good for you @apupier ?
For anyone having some timeout deploying the operator (typically a Error: ImagePullBackOff after 2 minutes by default kubernetes timeout configuration) the recommended action is to ensure the image is pulled beforehand in the local/dedicated registry to have it available in your kubernetes.

From the information given on the issue open in the quarkus mandrel images repository, I would say we can close this issue. Is this good for you @apupier ?

fine for me. Thanks for the investigation.

For anyone having some timeout deploying the operator (typically a Error: ImagePullBackOff after 2 minutes by default kubernetes timeout configuration) the recommended action is to ensure the image is pulled beforehand in the local/dedicated registry to have it available in your kubernetes.

For convenience providing the information here for instance with minikube, it will be something like that: minikube ssh docker pull apache/camel-k:1.11.0


I have a question about random offset units

Hello Vivek,
@beartype
def get_random_offset(batch_size: int, device) -> RigidTransform:
r1 = torch.distributions.Normal(0, 0.2).sample((batch_size,))
r2 = torch.distributions.Normal(0, 0.1).sample((batch_size,))
r3 = torch.distributions.Normal(0, 0.25).sample((batch_size,))
t1 = torch.distributions.Normal(10, 70).sample((batch_size,))
t2 = torch.distributions.Normal(250, 90).sample((batch_size,))
t3 = torch.distributions.Normal(5, 50).sample((batch_size,))
log_R_vee = torch.stack([r1, r2, r3], dim=1).to(device)
log_t_vee = torch.stack([t1, t2, t3], dim=1).to(device)
return convert(
[log_R_vee, log_t_vee],
"se3_log_map",
"se3_exp_map",
)
In random offset, r1, r2, r3, t1, t2, and t3 were understood as rotation(x, y, z) / translation(x, y, z).
So how do the numbers given in the normal distribution map to angles?
Thank you.

Hi @ryukyungjoon , [r1, r2, r3, t1, t2, t3] are elements of se(3) which are mapped to rigid transformations in SE(3) with the exponential map. I'm not aware of a way to directly interpret [r1, r2, r3] as rotation angles (although such an interpretation very well could exist). Appendix A of the paper discusses this exponential mapping in more detail, which might illuminate something.


datapath: Add flag to specify prefix for interface name of endpoints

This was hardcoded to lxc+ so far, provide a new option to change this. This
enables to use L7 proxy redirection in combination with chaining where the
interface name is picked by the CNI plugin setting up the interface names.

This change is

test-me-please

Coverage decreased (-0.03%) to 41.77% when pulling bd6395fe187430b7eadceaad322922b1897d217d on pr/tgraf/interface-flag into 0f36e6e77cc4b4b0fa9e1bcb0c535e3383cbe060 on master.


Add support to upload folder?

I have error Error: EISDIR
Is it  relevance with upload folder features?
Can I request that feature? if not, could you explain me why?
Thanks

Thanks for your suggestion! I believe we may be able to support such a feature. Something like this might be sufficient:
var opts = { recursive: true, validation: true, resumable: true };
bucket.uploadFolder('./photos', opts, function(errs, files) {
  // errs is null if no errors occur on any files
  // errs is array of errors for every file that fails to upload
  // files is every file that succeeds in uploading
});

The only issue I can see with this is that it will be hard to measure progress of such uploads (which could be long running) without any sort of stream interface. We might be able to do some sort of "progress stream" like:
var progress = bucket.uploadFolder(/* ... */);
progress.on('error', errCallback);
progress.on('fileEnd', aSingleFileDoneCallback);
progress.on('end', allFilesDoneCallback);

Until then you could probably get by with something like this which should in theory upload all files in a particular folder (non-recursively):
var fs = require('fs');
var async = require('async'); // npm install async
var bucket = storage.bucket('my-bucket'); // need to inititialize storage beforehand (see docs)
var contents = fs.readdirSync('./path/to/folder'); // get contents of folder (files and folders)
var files = contents.filter(function(file) {
  return fs.statSync(file).isFile(); // filter out only files
});
async.each(files, function(file, cb) {
  bucket.upload(file, cb);
}, function(err) {
  // all files should be uploaded now assuming there were no errors!
});

I don't mind the idea, though we would just be doing what the user could do in their code (1. get a list of files in a directory, 2. send each file to bucket.upload).
To handle this more easily, we could support glob input to allow more specificity: bucket.upload("backups/*.jpg", ...

The only issue I can see with this is that it will be hard to measure progress of such uploads (which could be long running) without any sort of stream interface.

That example looks good to me, though I would nit-pickingly change fileEnd to file-uploaded.

Yeah, sure! That was just an example :smiley: If it happened that way we might decide to have more events too.

OK. @stephenplusplus I catch the clue. Thanks for such suggestion :+1:

I got it in my head that supporting globs would be a good idea, but after an attempt at an implementation, it felt like more weight than our library should handle. If anyone objects, feel free to discuss!


Add @_spi annotations to reexport decls in cross-import overlays.

This PR attempts to make sure that SPI is reexported from our cross-import overlays. This change is speculative and I'm not actually sure if it'll do what I want.
Checklist:

[ ] Code and documentation should follow the style of the Style Guide.
[ ] If public symbols are renamed or modified, DocC references should be updated.

@swift-ci test

@swift-ci test Linux

@xedin What about this change? It was experimental—but if Vapor is importing Testing and Foundation, perhaps this change hit a corner of cross-import overlays that isn't fully functional?


Linux: context menu runs action under mouse when opened - New in 1.92.0

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

VS Code Version: 1.92.0
OS Version: Linux

So I am aware of https://github.com/microsoft/vscode/issues/113175 - However I only have this problem when using 1.92.0 - Downgrading to 1.92.1 fixes it. I noticed the context-menu now "fades in", whereas before it just appeared (with no animations). Were there some changes in 1.92.0 that could cause this?
Steps to Reproduce:

Use 1.92.0
In file browser, right-click somewhere - It opens the context-menu in such a way, that on release of the right-click it immediately executes the entry that's below the cursor. Optimally, the context-menu would appear with an offset such that this does not happen

I have the same behaviour. Furthermore, right-clicking shortly shows the menu and immediately closes the menu. Probably because releasing the right-click tries to select something. However, I cannot reproduce this on every click, few times it works. I think it depends on where you click.

Same.  I've been using VS Code on Linux without problems for years but as of 1.92.0 it exhibits the very dangerous/disruptive behavior of executing whatever command happens to be under the mouse when I right-click and release.

I have the same Problem with the latest update. Sometimes the menu stays open but most of the time the item directly on the mouse position is selected immediately. Downgrade to 1.91.1 fixes the problem.

Same. Kernel 6.1.0, Debian 12.1, KDE Plasma 5.27.5

Same here. 1.91.1 has no problem.

@sbatten can we add the "new release" label again?

I think this is related to https://github.com/microsoft/vscode/issues/224515, which provides a workaround of changing the setting "Window: Title Bar Style" to "custom" (although that does change the title bar).

Its related, but I think unique. I encounterd this issue previously, but fixed it (dont remember how, IE if I followed the fix mentioned in the other thread) several years ago. I recently upgraded my vscode, and have started encountering it once again.


As a best practice, shouldn't all apps start with at least 2 containers?

Moving from https://github.com/openshift-s2i/s2i-aspnet/issues/19

What is the standard for other RH examples?

I don't know if there is best practices. Looking at the rails-example it seems it's 1 pod. It makes some sense as scaling should be fairly easy to do via the OpenShift webconsole. Either way, this would have to go into the template. I'm not sure this is supported via the image stream example (try it) mechanism.

Closing old issues.


cargo: port to use requests instead of urllib

The main reason for the switch is that requests supports using credentials from .netrc, which would require copying quite some code from downloadablefilesource to achieve using urllib.

It seems to me that it would be desirable to copy the code, and thus avoid adding an external dependency.

This repo already depends on requests even though this specific plugin doesn't, so I don't really see it as a new dependency. But I can rework it.

This repo already depends on requests even though this specific plugin doesn't, so I don't really see it as a new dependency. But I can rework it.

The recommended way to use plugins is via junctions and not with pip, so usage of the repo is selective (using buildstream-plugins does not require the dependencies of every plugin).
IMO it would be better to avoid (and even remove) any external dependencies wherever possible at least in buildstream-plugins.
This is indeed a controversial subject in general, we allow external dependencies in plugins, but I think at least for buildstream-plugins we offer a better experience overall if we can avoid external dependencies as much as possible.
Anecdotally, I am working on a customer project at this moment where a lot of makefile madness and downloading of a whole SDK from their internal artifactory can be avoided from the build, if only the python script they had in place was using urllib instead of the external requests library they have in that SDK.

Done in #57

Since this netrc/urllib functionality might be a recurring theme, maybe it would make sense to provide a utils feature for this to share with downloadablesource ?

It does. I'm copying the code nevertheless in order to avoid having to depend on buildstream 2.2.

Makes sense, maybe we can add something nice to buildstream 2.2 nevertheless, and only depend on buildstream 2.2 a year later.


documentation for templating does not include templateSelection option

The example for templating only shows the usage of templateResult, and it took me a bit to figure out that I needed to use templateSelection, because the example uses templateSelection, but the code snippet does not include templateSelection
the example should probably read (because that's what code the example is running)
$(".js-example-templating").select2({
  templateResult: formatState,
  templateSelection: formatState
});

anyways, thought maybe it would save someone else some time

In the doco, the templateResult isn't mentioned on the options page. The following is displayed twice:
Key: templateSelection
Value: A function taking a selection object
The second instance should reference templateResult


Else not required after if return

the else statement can be remoed from here

Multiple return statements can be confusing
see here
here
here
here
here
here
here


App crashing after adding variables

Works just fine with mixins, but if I try to add some variables it starts crashing after pressing "play" button.
OS: Windows 10

So, I just reinstalled the app and its working now! =)

Are you using the Scout-App v2.0.2 (2016)?
No installation should be required. Just unzip/double-click. It's a portable app.


Add RDMA verbs configuration

RDAM configuration is now possible with the following environment variables:  RDMA_DEVICE, RDMA_DEVICE_PORT, RDMA_GID_INDEX,  RDMA_PKEY, RDMA_QUEUE_DEPTH, RDMA_TIMEOUT, RDMA_RETRY_CNT, RDMA_SL, RDMA_MTU and RDMA_TRAFFIC_CLASS.

Can one of the admins verify this patch?

I signed it!
Regards,
Daria Velikovsky
SW Engineer, SW
Mellanox Technologies
Office: +972-747238531, Mobile: +972-543271181
www.mellanox.comhttp://www.mellanox.com/
Follow us on Facebookhttp://www.facebook.com/pages/Mellanox-Technologies/223164879116 and Twitterhttp://twitter.com/mellanoxtech

From: googlebot<EMAIL_ADDRESS>Sent: Sunday, October 8, 2017 1:14:37 PM
To: tensorflow/tensorflow
Cc: Daria Velikovsky; Author
Subject: Re: [tensorflow/tensorflow] Add RDMA verbs configuration (#13564)
Thanks for your pull request. It looks like this may be your first contribution to a Google open source project. Before we can look at your pull request, you'll need to sign a Contributor License Agreement (CLA).
📝 Please visit https://cla.developers.google.com/https://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcla.developers.google.com%2F&data=02|01|daria%40mellanox.com|dde0ef895b0b433d96db08d50e35631e|a652971c7d2e4d9ba6a4d149256f461b|0|0|636430544819705169&sdata=bUEPhOQ0pFRZdDpqGsTyOedWyHRp2XwXd4xxO2qn7L4%3D&reserved=0 to sign.
Once you've signed, please reply here (e.g. I signed it!) and we'll verify. Thanks.

If you've already signed a CLA, it's possible we don't have your GitHub username or you're using a different email address. Check your existing CLA datahttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcla.developers.google.com%2Fclas&data=02|01|daria%40mellanox.com|dde0ef895b0b433d96db08d50e35631e|a652971c7d2e4d9ba6a4d149256f461b|0|0|636430544819705169&sdata=W5gEvaHw5IVa0%2B%2BlLDS6TnpAcSS%2B1h2IlmTpObi2Gg4%3D&reserved=0 and verify that your email is set on your git commitshttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fhelp.github.com%2Farticles%2Fsetting-your-email-in-git%2F&data=02|01|daria%40mellanox.com|dde0ef895b0b433d96db08d50e35631e|a652971c7d2e4d9ba6a4d149256f461b|0|0|636430544819705169&sdata=0AI%2BD%2Flq2rq8i%2Bfq1BleXV1N1J77AkQeoChhTUCsucI%3D&reserved=0.
If your company signed a CLA, they designated a Point of Contact who decides which employees are authorized to participate. You may need to contact the Point of Contact for your company and ask to be added to the group of authorized contributors. If you don't know who your Point of Contact is, direct the project maintainer to go/cla#troubleshoot.
In order to pass this check, please resolve this problem and have the pull request author add another comment and the bot will run again.

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Ftensorflow%2Ftensorflow%2Fpull%2F13564%23issuecomment-334996331&data=02|01|daria%40mellanox.com|dde0ef895b0b433d96db08d50e35631e|a652971c7d2e4d9ba6a4d149256f461b|0|0|636430544819705169&sdata=GhiLBFuURnprtcnDejVcQtB6CziJndVc9W98wsnD5tE%3D&reserved=0, or mute the threadhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAejJTdl2wKPls45idVNS7ZGsjLbzAonVks5sqKCNgaJpZM4Pxp_k&data=02|01|daria%40mellanox.com|dde0ef895b0b433d96db08d50e35631e|a652971c7d2e4d9ba6a4d149256f461b|0|0|636430544819705169&sdata=7i60CszubAt8mGvsonwvMaUnsUKxhHEEI7wJRFnRRLs%3D&reserved=0.

I signed it!

It looks good to me.

All the authors have signed the CLA.

I'm ok okay with my commits being contributed to this project.

Hi @poxvoculi @jhseu,
Have you add the chance to take a look ?

Thanks @poxvoculi, can we merge this ?

@poxvoculi, we want to rearrange the commits of the PR (all of the commits are duplicated, probably something with the merges got mixed up). We will fix it tomorrow plz do not merge if you see this.

@drpngx @poxvoculi @jhseu - We fixed the duplicated commits and now all looks good.
No change in code since @poxvoculi review.
Thanks @noaezra @dariavel for the great work.

@drpngx ?

Sounds good, let's see if the test suite passes.

Could you pull rebase and push again? The different commits appear to be foiling the CLA bot.

Jenkins, test this please.

Thanks @gunan @drpngx
I guess the cla/google is fooled by - commits were authored by someone other than the pull request submitter ?
If so, rebasing on top master on this PR will help ?
Should we post a new PR with the changes ?

Yes rebase usually works
On Wed, Nov 1, 2017 at 1:28 AM, Ido Shamay<EMAIL_ADDRESS>wrote:

Thanks @gunan https://github.com/gunan @drpngx
https://github.com/drpngx
I guess the cla/google is fooled by - commits were authored by someone
other than the pull request submitter ?
If so, rebasing on top master on this PR will help ?
Should we post a new PR with the changes ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/tensorflow/tensorflow/pull/13564#issuecomment-341032108,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AT_SbVAisThR5OH-VtlhVmFGqJEoS_E7ks5syCuzgaJpZM4Pxp_k
.

Jenkins, test this please.

Looks like all the authors did sign the CLA, but CLA bot is confused because of multiple commits from different authors. Once the tests pass, I can merge this PR.

@gunan , looks like there problem with the CI, not related to this patch.
Can we re-run the jenkins ?

You are right. I think last night we ran out of daily quota on the backend, it should be fixed now.


Add Faker::Restaurant

Add fakes for businesses that sell food and/or beverages.

Hey @vbrazo,
Thanks for the quick review. I don't speak any other languages fluently, and the PR you referenced doesn't appear to have any other locales, so I can't add any additional ones. I think PhraseApp still offers free translation for open source projects, if that's a concern.
I'm adding another commit to add Restaurant#description and Restaurant#review. It seems like the operating hour feature would be better off as a separate addition to Faker::Business, though.

Sounds like a plan. I'll review your PR again once you push new commits 👍

I tested locally and it looks fine 👍

Thanks for the quick merge!


Rebuild for python310 (v2)

This PR is a duplicate of #30 with the extra patch from https://github.com/conda-forge/pyepics-feedstock/pull/30#issuecomment-984504224.

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

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

Looks like we have the same problem with https://github.com/conda-forge/xraylarch-feedstock/pull/4. The setup.py has the same issues with all-platforms package_data.
Thanks for the pointers, @duncanmmacleod, I'll apply a similar patch there :slightly_smiling_face:

By the way, the trick worked for https://github.com/conda-forge/xraylarch-feedstock/pull/4!

@conda-forge/pyepics can this be merged now?

tacaswell, do you have any concerns/comments?

A bit late, but yes.  We should not be including any of the pre-built binaries and instead be using the epics binaries provided by the epics-base package.


Hash/Array/etc#dig? method are too strict regarding its key type

Extracted from #7569
The following examples works currently
h = {"a" => {"b" => [10, 20, 30]}}
h.dig? "a", "b"              # => [10, 20, 30]
h.dig? "a", "x", 0, "d", "e" # => nil
h.dig? "a", "x", 5, "d", "e" # => nil

But this does not
h.dig? "a", "b", "c", "d", "e" # => compile time error

Since the value returned by h.dig? "a", "b" responds to dig? but there is no dig? definition that can handle a String index.
The lack of that definition also prevents the following to work:
h = {"a" => {"b" => [10, 20, 30], "c" => { "d" => { "e" => 40 }}}}
h.dig? "a", "c", "d", "e" # => compile time error

I think that's fine. Why passing a string where an int is expected to silently give nil?
Also, I can't see how this can be implemented without having something like responds_to?(:[], String).

Hash#dig?:
  def dig?(key : K, *subkeys)
    if (value = self[key]?) && value.responds_to?(:dig?)
      value.dig?(*subkeys)
    end
  end

The problem lies in value.responds_to?(:dig) which returns true, even if the types doesn't match, a workaround would be to loosen the types, but a better fix would be #2549 I think.

Hm, this works:
h = {"a" => {"b" => "hello world"}}

h.dig?("a", "b", "c", "d", "e") # => nil

I guess dig? is not type-safe at all. So yeah, if we want that, the only way to implement it (I think) is with #2549


unable to extract html5 player

xxx@xxx:~$ youtube-dl -t -v --restrict-filename https://www.youtube.com/watch?v=iVlZY2Whwgk
[debug] System config: []
[debug] User config: []
[debug] Command-line args: [u'-t', u'-v', u'--restrict-filename', u'https://www.youtube.com/watch?v=iVlZY2Whwgk']
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2015.11.02
[debug] Python version 2.7.6 - Linux-3.19.0-25-generic-i686-with-Ubuntu-14.04-trusty
[debug] exe versions: avconv v12_dev0-1952-gd15368e, avprobe v12_dev0-1952-gd15368e
[debug] Proxy map: {}
[youtube] iVlZY2Whwgk: Downloading webpage
[youtube] iVlZY2Whwgk: Downloading video info webpage
[youtube] iVlZY2Whwgk: Extracting video information
WARNING: unable to extract html5 player; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
[youtube] {22} signature length 40.44, html5 player None
ERROR: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 661, in extract_info
ie_result = ie.extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/common.py", line 290, in extract
return self._real_extract(url)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 1345, in _real_extract
encrypted_sig, video_id, player_url, age_gate)
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 827, in _decrypt_signature
'Signature extraction failed: ' + tb, cause=e)
ExtractorError: Signature extraction failed: Traceback (most recent call last):
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 817, in _decrypt_signature
video_id, player_url, s
File "/usr/local/bin/youtube-dl/youtube_dl/extractor/youtube.py", line 709, in _extract_signature_function
raise ExtractorError('Cannot identify player %r' % player_url)
ExtractorError: Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
(caused by ExtractorError(u"Cannot identify player u'https://s.ytimg.com/yts/jsbin/player-en_US-vfljDEtYP/base.js'; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.",)); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Duplicate of #7413. This will work in the next version.


Amazon Linux 2023 ARM64 incompatibility

Problem
While using Sveltekit for a project with Prisma it builds without any issue however on running node build/index.js the application crashes with this message:
(..)build/server/chunks/prisma-a710fb45.js:46
Please report your experience by creating an issue at
${_t("https://github.com/prisma/prisma/issues")}
so we can add your distro to the list of known supported distros.`),
t==="darwin"&&r==="arm64")return "darwin-arm64";if(t==="darwin")return "darwin";if(t==="win32")
return "windows";if(t==="freebsd")return o;if(t==="openbsd")return "openbsd";if(t==="netbsd")
return "netbsd";if(t==="linux"&&o==="nixos")return "linux-nixos";if(t==="linux"&&r==="arm64")
return `${o==="musl"?"linux-musl-arm64":"linux-arm64"}-openssl-${i||l}`;if(t==="linux"&&r==="arm")
return `linux-arm-openssl-${i||l}`;if(t==="linux"&&o==="musl"){let c="linux-musl";return !i||is(i)?c:`${c}-openssl-${i}`}
return t==="linux"&&o&&i?`${o}-openssl-${i}`:(t!=="linux"&&jt(`Prisma detected unknown OS "${t}" and may not work as
 expected. Defaulting to "linux".`),i?`${u}-openssl-${i}`:o?`${o}-openssl-${l}`:`${u}-openssl-${l}`)}
 async function gc(e){try{return await e()}catch{return}}function Dr(e){return gc(async()=>{let t=await oc(e);
 return fe(`Command "${e}" successfully returned "${t.stdout}"`),t.stdout})}async function yc(){
 return typeof Rr.default.machine=="function"?Rr.default.machine():(await Dr("uname -m"))?.trim()}
 function is(e){return e.startsWith("1.")}var ii=["darwin","darwin-arm64","debian-openssl-1.0.x",
 "debian-openssl-1.1.x","debian-openssl-3.0.x","rhel-openssl-1.0.x","rhel-openssl-1.1.x","rhel-openssl-3.0.x",
 "linux-arm64-openssl-1.1.x","linux-arm64-openssl-1.0.x","linux-arm64-openssl-3.0.x","linux-arm-openssl-1.1.x",
 "linux-arm-openssl-1.0.x","linux-arm-openssl-3.0.x","linux-musl","linux-musl-openssl-3.0.x",
 "linux-musl-arm64-openssl-1.1.x","linux-musl-arm64-openssl-3.0.x","linux-nixos","linux-static-x64",
 "linux-static-arm64","windows","freebsd11","freebsd12","freebsd13","openbsd","netbsd","arm"];F(oi());
 var q=F(require$$4);F(oi());V("prisma:engines");function ss(){
 return q.default.join(__dirname,"../")}q.default.join(__dirname,"../query-engine-darwin");
 q.default.join(__dirname,"../query-engine-darwin-arm64");
 q.default.join(__dirname,"../query-engine-debian-openssl-1.0.x");
 q.default.join(__dirname,"../query-engine-debian-openssl-1.1.x");
 q.default.join(__dirname,"../query-engine-debian-openssl-3.0.x");
 q.default.join(__dirname,"../query-engine-linux-static-x64");
 q.default.join(__dirname,"../query-engine-linux-static-arm64");
 q.default.join(__dirname,"../query-engine-rhel-openssl-1.0.x");
 q.default.join(__dirname,"../query-engine-rhel-openssl-1.1.x");
 q.default.join(__dirname,"../query-engine-rhel-openssl-3.0.x");
 q.default.join(__dirname,"../libquery_engine-darwin.dylib.node");
 q.default.join(__dirname,"../libquery_engine-darwin-arm64.dylib.node");
 q.default.join(__dirname,"../libquery_engine-debian-openssl-1.0.x.so.node");
 q.default.join(__dirname,"../libquery_engine-debian-openssl-1.1.x.so.node");
 q.default.join(__dirname,"../libquery_engine-debian-openssl-3.0.x.so.node");
 q.default.join(__dirname,"../libquery_engine-linux-arm64-openssl-1.0.x.so.node");
 q.default.join(__dirname,"../libquery_engine-linux-arm64-openssl-1.1.x.so.node");
 q.default.join(__dirname,"../libquery_engine-linux-arm64-openssl-3.0.x.so.node");
 q.default.join(__dirname,"../libquery_engine-linux-musl.so.node");
 q.default.join(__dirname,"../libquery_engine-linux-musl-openssl-3.0.x.so.node");
 q.default.join(__dirname,"../libquery_engine-rhel-openssl-1.0.x.so.node");
 q.default.join(__dirname,"../libquery_engine-rhel-openssl-1.1.x.so.node");
 q.default.join(__dirname,"../libquery_engine-rhel-openssl-3.0.x.so.node");
 q.default.join(__dirname,"../query_engine-windows.dll.node");
 var si=F(require$$3),as=V("plusX");function ai(e){let t=si.default.statSync(e),
 r=t.mode|64|8|1;if(t.mode===r){as(`Execution permissions of ${e} are fine`);r
 eturn}let n=r.toString(8).slice(-3);as(`Have to call plusX on ${e}`),
 si.default.chmodSync(e,n);}function li(e){
 let t=e.e,r=a=>`Prisma cannot find the required \`${a}\` system library in your system`,
 n=t.message.includes("cannot open shared object file"),
 i=`Please refer to the documentation about Prisma's system requirements: ${_t("https://pris.ly/d/system-requirements")}`,
 o=`Unable to require(\`${$(e.id)}\`).`,
 s=pt({message:t.message,code:t.code}).with({code:"ENOENT"},()=>"File does not exist.").when(({message:a})=>n&&a.includes("libz"),
 ()=>`${r("libz")}.
 Please install it and try again.`).when(({message:a})=>n&&a.includes("libgcc_s"),
 ()=>`${r("libgcc_s")}.
 Please install it and try again.`).when(({message:a})=>n&&a.includes("libssl"),()=>{let a=e.platformInfo.libssl?`openssl-${e.platformInfo.libssl}`:"openssl";
 return `${r("libssl")}. Please install ${a} and try again.`}).when(({message:a})=>a.includes("GLIBC"),
 ()=>`Prisma has detected an incompatible version of the \`glibc\` C standard library installed in your system.
 This probably means your system may be too old to run Prisma. ${i}`).when(({message:a})=>e.platformInfo.platform==="linux"&&a.includes("symbol not found"),
 ()=>`The Prisma engines are not compatible with your system ${e.platformInfo.originalDistro} on (${e.platformInfo.archFromUname}) which uses the \`${e.platformInfo.binaryTarget}\` binaryTarget by
 default.
 ${i}`).otherwise(()=>`The Prisma engines do not seem to be compatible with your system. ${i}`);return `${o}

Additional context
I do not have the same issue when running the application with these commands:
$ pnpm run dev
$ pnpm build && pnpm preview
Then Prisma runs as expected on this same instance.
Only when running node build/index.js do I get the error and the application then immediately crashes.
Node.js v20.3.1
$ npx prisma -v
Environment variables loaded from .env
prisma                  : 4.16.0
@prisma/client          : 4.16.0
Current platform        : linux-arm64-openssl-3.0.x
Query Engine (Node-API) : libquery-engine b20ead4d3ab9e78ac112966e242ded703f4a052c (at node_modules/.pnpm/@prisma+engines<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli b20ead4d3ab9e78ac112966e242ded703f4a052c (at node_modules/.pnpm/@prisma+engines<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.16.0-66.b20ead4d3ab9e78ac112966e242ded703f4a052c
Default Engines Hash    : b20ead4d3ab9e78ac112966e242ded703f4a052c
Studio                  : 0.484.0
Preview Features        : postgresqlExtensions
$ cat os-release
NAME="Amazon Linux"
VERSION="2023"
ID="amzn"
ID_LIKE="fedora"
VERSION_ID="2023"
PLATFORM_ID="platform:al2023"
PRETTY_NAME="Amazon Linux 2023"
ANSI_COLOR="0;33"
CPE_NAME="cpe:2.3:o:amazon:amazon_linux:2023"
HOME_URL="https://aws.amazon.com/linux/"
BUG_REPORT_URL="https://github.com/amazonlinux/amazon-linux-2023"
SUPPORT_END="2028-03-01"

@desylva This is unexpected to me 🤔
I tried on an AWS Graviton machine (ARM64 with Amazon Linux 2023 image) and it worked as expected.
We also have tests running on Docker testing our arm builds and they are passing like expected.
Could it be that the error is something else and was truncated? Is there anything else in your logs?

Maybe try to switch to Node v18 as it is a stable and LTS version and see if anything changes?

I tried with Node v16 and v18 with same results

@desylva What would be interesting to know is: did it start failing when you upgraded Prisma to 4.16.0 maybe? Was it working before?

It is new project so it never has been working on production. Not an upgrade.

Got it working in the end. It seems I got misled by the error referring to unsupported distro.
The error was caused by something entirely different in the end and the post bellow found on Github helped me to fix it in relation to __dirname which is mentioned in the error message but not as the source of the issue.
https://github.com/prisma/prisma/issues/15614#issuecomment-1491269798
Code pasted here for convenience:
import type { PrismaClient as ImportedPrismaClient } from '@prisma/client'
import { createRequire } from 'module'
const require = createRequire(import.meta.url ?? __filename)
const { PrismaClient: RequiredPrismaClient } = require('@prisma/client')
const _PrismaClient: typeof ImportedPrismaClient = RequiredPrismaClient
export class PrismaClient extends _PrismaClient {}

I am not entirely sure about the intricacies of the issue at this time. Something I will have to dig down when if I get to it.

@desylva Happy you found the issue!
Please check this message:
https://github.com/prisma/prisma/issues/15614#issuecomment-1573497815
Your feedback is very welcome there 💚


[WIP] Provide USBGadget Support

I have added RNDIS and MIDI usb gadget modes and performed a VTS test/

https://01.org/linuxgraphics/gfx-docs/drm/usb/gadget-testing.html
Documentation about usb gadget modes.
@rsglobal

@MaksymPrymierov ,
Thank you for this submission. Please rebase into next (don't forget to do git remote update to download recent changes)
Could you put more info into the commit message for ("common: Update USB init script for working usb gadget through functionfs"), was it copy-pasted/based on similar AOSP file? Could you put a permalink to that file?


Add fd notifications for completion queues

fd_on_read(int fd, grpc_completion_queue* cq, void *tag)
... to allow composing other i/o with grpc

a bit old and no apparent use case  (atleast in the short/mid term). Closing this


Updating with vim-plug is broken

Doing :PlugUpdate with vim-plug has failed for me a couple of times recently, with the following error:
x nvim-ts-rainbow:
    fatal: Not possible to fast-forward, aborting.

When I check my local nvim-ts-rainbow repository, it seems that my copy is behind the GitHub repository by seven commits and ahead by three.
I don't make changes to my local repository, so I'm not sure how this happened. One possible explanation is that history in this repository gets rewritten with git push --force, which makes it impossible to update local remotes with a fast-forward only pull.
If this is what happened, could you please avoid this in the future to avoid breaking updates for your users? If this isn't what happened, it'd be useful to know what did so I can try to fix it. Thanks!

I'm so sorry, I forgot to switch branches and did WIP stuff on master, so I had to force push it back

Please never force push to a branch that others are using. If you need to undo something, revert it properly.

Right, thanks!

Thanks for your work on this plugin!


Uphold logo added

Happy to add the Uphold logo with light and dark options.

You changed the pnpm-lock.yaml file, be careful, you can restore it 👀

I've already restored the pnpm-lock.yaml file. Thanks for the heads-up


Include nightly versions

The Bash script retrieves https://ziglang.org/download/index.json, which lists the current v11.0-dev.* nightly versions. However, when I run asdf list all zig I only see the stable versions (0.1.1 through 0.10.1).
Could this be changed to also include nightly versions?
Unfortunately, I can't really tell where in the script the filtering happens, otherwise I'd change it myself.

When I run the same command (asdf list all zig) I see 0.2.0 through 0.10.1 and master.
asdf install zig master gives me version 0.11.0-dev.1884+2641feb9b.

I am not the maintainer, just a passer-by. It would be nice to have even more versioning options for such a fast moving target but I don't think asdf tracks github commits, just github labels (see comment in https://github.com/cheetah/asdf-zig/issues/5).
As far as I know master is the nightly build.
When i do a asdf plugin list-all | grep zig I get a reference to https://github.com/cheetah/asdf-zig.git. So I'm not sure we are discussing this in the correct repository. Perhaps the repo owner can enlighten us.

yeah i wish master was included in list-all.


One contract with the same tenderer for different lots - problem with totals of contracts values at notice level (BT-118-NoticeResult)

Hello,
We have many situations where contracting authorities conclude one contract for more than one lot if the winner is the same. These situations are mainly in the procurement of pharmaceutical products. There are a lot of lots, usually one per product, but few suppliers.
They make one contract per supplier and not per lot either for framework agreements or for regular contracts.
For example:
See section V:
https://www.e-licitatie.ro/pub/notices/ca-notices/view-c/100374617
or published on TED, for example contract  Contract nr.: 42307
https://ted.europa.eu/udl?uri=TED:NOTICE:294221-2023:TEXT:RO:HTML&src=0#id3-V.
In this case the ”results of lots” in the eForms award goes something like this:
result 1, lot 31:
Contract 42307
estimated value of framework agreement: 1 178 791.20 RON (BT-660-LotResult)
maxim value of framework agreement: 1 078 826.40 RON (BT-709-LotResult)
result 2, lot 8
Contract 42307
estimated value of framework agreement: 1 178 791.20 RON
maxim value of framework agreement: 1 078 826.40 RON
result 3, lot 13:
Contract 42307
estimated value of framework agreement: 1 178 791.20 RON
maxim value of framework agreement: 1 078 826.40 RON
result 4, lot 16
Contract 42307
estimated value of framework agreement: 1 178 791.20 RON
maxim value of framework agreement: 1 078 826.40 RON
In this case there is a problem with the total value of the contracts BT-118-NoticeResult, BT-1118-NoticeResult (framework agreements) because the CVS validator expect the total to be something like: 1 178 791.20 RON+1 178 791.20 RON+1 178 791.20 RON+1 178 791.20 RON. This is not correct because we don't want to sum the same contract many times.
Please give us some ideas how to proceed in this case!
Thank you
Alex Mohora

See the situation in this example


Repeatedly invoking gradle buildGhidra produces broken build/dist zip archive every other time

Download ghidra-master.zip from github, unpack.
gradle -I gradle/support/fetchDependencies.gradle init
gradle buildGhidra
(build/dist zip size: 312,684,032)
gradle buildGhidra
(build/dist zip size: 19,617,529) <-- Obviously broken
gradle buildGhidra
(build/dist zip size: 312,684,061) <-- Probably OK again
gradle buildGhidra
(build/dist zip size: 19,617,534) <-- Whoops
gradle buildGhidra
(build/dist zip size: 312,684,060) <-- And OK again
The built .zip size alternates between completely broken (~19MB) and probably-OK on successive invocations of gradle buildGhidra.
I'm using Gradle 7.3.3, Visual Studio 2022, JDK zulu18.0.65-ea-jdk18.0.0-ea.28-win_x64

I could repro on linux as well, I think looking at logs assembleDistribution and assembleDistribution_linux_x86_64 were marked as UP-TO-DATE in the tiny build.  I don't know enough about gradle to dig further, did it manually, was basically looking at diff -y <(gradle buildGhidra) <(gradle buildGhidra) | grep "> Task"

I've narrowed down the strange behavior to this:
https://github.com/NationalSecurityAgency/ghidra/blob/436bb4873e8571b87a4d785bb828d9bf772b4867/gradle/root/distribution.gradle#L521-L523
After we produce the final zip we delete the pre-zipped directory.  If you comment out the delete and preserve the directory that gets zipped, it works correctly each time.  Someone else on the team is going to investigate this further.


pull request for e2e test at 01/08/2017 02:45:10

:white_check_mark: Validation status: passed
For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Docstrings - specify units / use astropy.units?

In some of the docstrings, "size" is requested without reference to units, e.g. imagesearch:
   *pos*:  a 2-element seqence giving the ICRS RA and DEC in decimal degrees
   *size*: a floating point number or a 2-element tuple giving the size
             of the rectangular region around pos to search for images.

First, units should be specified everywhere (minor but important point).
Second, though - in astroquery, we've decided that all coordinate-based requests need to either be:

a string that can unambiguously be parsed into a coordinate (i.e., there is no ambiguity between "galactic" or "fk5"
an astropy.coordinates instance

I think that approach would be useful for pyvo as well, particularly since it will allow us to present a common user interface between astroquery and pyvo.  Achieving that broad goal will take a bit more work, but at least accepting astropy.coordinates as input is a good first step.

Input parameters are astropy integrated, where possible


[question] model for database table alias

Existing/related issue?
How to represent database table alias
Current Behavior
For Table, we use RelationalTable entity to represent a table.
For View, we use RelationalTable + CalculatedValue Classification to represent a view.
By this we can distinguish table and view by whether has a CalculatedValue attached.
How about table alias? How to represent it and how to distinguish it from table and view?
Expected Behavior
Have a proper way to represent database Table Alias.
Steps To Reproduce
No response
Environment
- Egeria:
- OS:
- Java:
- Browser (for UI issues):
- Additional connectors and integration:

Any Further Information?
No response

Specifically, I understand the question here is about DB2 Aliases https://www.ibm.com/docs/en/db2-for-zos/11?topic=concepts-aliases
The term 'alias' is also used for

temporary use within sql statements (ie select aaa from bbb as ccc)
with connection catalogs (db2, sql server) ie using a name to represent a database endpoint to connect to

@planetf1
Thanks. Yes. The Alias here means An alias is a substitute for the three-part name of a table or view

It's possible a similar question would apply to

Filesystem symbolic links
hostname aliases


Revert #50

This uses the implementations prior to #50.  Those were cleaner, but less performant (#171), and misused the parallel dispatcher (#172).
I find these implementations much harder to reason about correctness, but there is more empirical evidence of correctness.  Or at least no empirical evidence of incorrectness.

Thanks for your hard work on this Ross!

Reopening to see build error.  It works locally.

I don't know why I still see stale builds.  I'm just going to rebase.


selfupdate not change the version?

sdk selfupdate

Updating SDKMAN...
######################################################################## 100.0%
已删除'/home/fengyu/.sdkman/bin/sdkman-init.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-init.sh' -> '/home/fengyu/.sdkman/bin/sdkman-init.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-availability.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-broadcast.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-cache.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-current.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-default.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-env-helpers.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-flush.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-help.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-install.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-list.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-main.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-offline.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-path-helpers.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-selfupdate.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-uninstall.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-update.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-upgrade.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-use.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-utils.sh'
已删除'/home/fengyu/.sdkman/src/sdkman-version.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-availability.sh' -> '/home/fengyu/.sdkman/src/sdkman-availability.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-broadcast.sh' -> '/home/fengyu/.sdkman/src/sdkman-broadcast.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-cache.sh' -> '/home/fengyu/.sdkman/src/sdkman-cache.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-current.sh' -> '/home/fengyu/.sdkman/src/sdkman-current.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-default.sh' -> '/home/fengyu/.sdkman/src/sdkman-default.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-env-helpers.sh' -> '/home/fengyu/.sdkman/src/sdkman-env-helpers.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-flush.sh' -> '/home/fengyu/.sdkman/src/sdkman-flush.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-help.sh' -> '/home/fengyu/.sdkman/src/sdkman-help.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-install.sh' -> '/home/fengyu/.sdkman/src/sdkman-install.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-list.sh' -> '/home/fengyu/.sdkman/src/sdkman-list.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-main.sh' -> '/home/fengyu/.sdkman/src/sdkman-main.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-offline.sh' -> '/home/fengyu/.sdkman/src/sdkman-offline.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-path-helpers.sh' -> '/home/fengyu/.sdkman/src/sdkman-path-helpers.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-selfupdate.sh' -> '/home/fengyu/.sdkman/src/sdkman-selfupdate.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-uninstall.sh' -> '/home/fengyu/.sdkman/src/sdkman-uninstall.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-update.sh' -> '/home/fengyu/.sdkman/src/sdkman-update.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-upgrade.sh' -> '/home/fengyu/.sdkman/src/sdkman-upgrade.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-use.sh' -> '/home/fengyu/.sdkman/src/sdkman-use.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-utils.sh' -> '/home/fengyu/.sdkman/src/sdkman-utils.sh'
'/home/fengyu/.sdkman/tmp/stage/sdkman-version.sh' -> '/home/fengyu/.sdkman/src/sdkman-version.sh'
已删除'/home/fengyu/.sdkman/tmp/sdkman-5.6.4+305.zip'
removed directory '/home/fengyu/.sdkman/tmp'
mkdir: 已创建目录 '/home/fengyu/.sdkman/tmp'

Successfully upgraded SDKMAN!

Open a new terminal to start using SDKMAN 5.6.4+305.

To join our BETA channel, simply follow the instructions on:

   http://sdkman.io/install.html

Enjoy!!!

But when I open a new terminal:
sdk v

SDKMAN 5.6.3+299

The version is still in old. And I can also use selfupdate to upgrade the version continually.

This is a known issue and occurs when using a login shell. Try changing your shell type and this should start working as expected.
In future, please follow the contributor guidelines before opening an issue.

Thanks.

Sorry, but it seems still not working.
bash --login
sdk v
SDKMAN 5.6.3+299

But the ~/.sdkman/var/version is 5.6.4+305
cat ~/.sdkman/var/version
5.6.4+305

I've tried closed all terminals and reopen a new one, the sdk v still shows SDKMAN 5.6.3+299

So the problem is that you are using a login shell. This is usually set in your terminal preferences. You should not use a login shell because it retains state over multiple sessions.


export validation list via export job

Error occurs after 35 seconds, the response takes more time to get full data


support for ort-web

Can you merge main into your branch? It looks like your version is slightly out of sync with main (e.g. enable_GQA_on_CPU is in your branch but it is not in main anymore).

thanks for catching!


BufferedOutputStream not flushing IOStream sink

As reported in JuliaLang/julia#14446, a BufferedOutputStream wrapping an IOStream does not flush the IOStream, even when flush() is called on the BufferedOutputStream. Currently, this example creates an empty file "test.txt" and does not write the output until Julia exits:
using BufferedStreams.BufferedOutputStream
ostream = BufferedOutputStream(open("test.txt", "w"))
write(ostream, "write a new line \n")
flush(ostream)

I added a new writebytes method for IOStreams which calls flush on the IOStream. I guess that if there's a use case for a BufferedOutputStream around any other buffered IO object, then a more flexible solution is needed.
OTOH, maybe it doesn't make sense to wrap any buffered IO object in a BufferedOutputStream, so maybe that should be disallowed. In that case, it might be better to raise an exception when creating a BufferedOutputStream with an IOStream, since the current behavior is unexpected.

Current coverage is 82.08%

Merging #4 into master will increase coverage by +10.91% as of 31f372d

@@            master      #4   diff @@
======================================
  Files            3       3
  Stmts          170     173     +3
  Branches         0       0
  Methods          0       0
======================================
+ Hit            121     142    +21
  Partial          0       0
+ Missed          49      31    -18

Review entire Coverage Diff as of 31f372d

Powered by Codecov. Updated on successful CI builds.

OTOH, maybe it doesn't make sense to wrap any buffered IO object in a BufferedOutputStream, so maybe that should be disallowed. In that case, it might be better to raise an exception when creating a BufferedOutputStream with an IOStream, since the current behavior is unexpected.

BufferedOutputStreams do more aggressive buffering than IOStreams do. Try https://github.com/BioJulia/BufferedStreams.jl/blob/master/perf/output-bench.jl. In my laptop, it runs about 2 times faster than IOStream as you can see below:
~/.j/v/BufferedStreams (master|✚1…) $ julia perf/output-bench.jl
write
  IOStream:  1.6141
  BufferedOutputStream/IOStream:  0.8071
...

Any plan to fix this issue on master?

I'll check it later.

Hi, any update on this issue?  This is still not fixed.
using BufferedStreams.BufferedOutputStream
ostream = BufferedOutputStream(open("test.txt", "w"))
write(ostream, "write a new line \n")
flush(ostream)

Then
cat test.txt

It's still a null file
# even we close it
close(ostream)

It's still a null file
exit()

Now the content is written

@ringw Thank you a lot!
@sfchen Sorry, I forgot this pull request. Thank you for pinging me.


Did 1.7 just break my lights?

Hi
Did 1.7 break my lights which I control from my beoremote. The trace reports an error:
"UndefinedError: 'dict object' has no attribute 'event'"
see full trace here:
trace automation.beoremote_lys 2024-01-18T17_31_44.161231+00_00.json
Kind regards
Frank

It looks like there are some problems with 1.7.0, so I've decided to pull it for now. Please revert to 1.6.2 for the time being.
Kind regards.


Can't deserialize FileOrFolderScopeScopeField

[x] I have checked that the SDK documentation doesn't solve my issue.
[x] I have checked that the API documentation doesn't solve my issue.
[x] I have searched the Box Developer Forums and my issue isn't already reported (or if it has been reported, I have attached a link to it, for reference).
[x] I have searched Issues in this repo and my issue isn't already reported.

Description of the Issue
Downscoping of a token with the scope item_upload causes serialization issues.
Downscoping a token using the base_explorer scope on a resource works as intended:
const token = await client.auth.downscopeToken(
    ['base_explorer'],
    `https://api.box.com/2.0/folders/${folderId}`,
  );

However, once the item_upload scope is added a deserialization error is thrown:
const token = await client.auth.downscopeToken(
    ['base_explorer', 'item_upload'],
    `https://api.box.com/2.0/folders/${folderId}`,
  );

Error:
BoxSDKError: {
  "message": "Can't deserialize FileOrFolderScopeScopeField"
}

I believe this scope is missing in the deserializeFileOrFolderScopeScopeField function.
https://github.com/box/box-typescript-sdk-gen/blob/20d347d956db05bc2e87f771dc1cab1308915f59/src/schemas/fileOrFolderScope.generated.ts#L34
Steps to Reproduce
Call the downscopeToken function with item_upload included in the scope:
const token = await client.auth.downscopeToken(
    ['base_explorer', 'item_upload'],
    `https://api.box.com/2.0/folders/${folderId}`,
  );

Expected Behavior
I expect a valid token to be returned to allow the App User to upload files and create folders.
Error Message, Including Stack Trace
{
  "message": "Can't deserialize FileOrFolderScopeScopeField"
}
at deserializeFileOrFolderScopeScopeField (/app/node_modules/box-typescript-sdk-gen/src/schemas/fileOrFolderScope.generated.ts:73:9)
at y8u (/app/node_modules/box-typescript-sdk-gen/src/schemas/fileOrFolderScope.generated.ts:100:9)
at <anonymous> (/app/node_modules/box-typescript-sdk-gen/src/schemas/accessToken.generated.ts:110:18)
at Array.map (<anonymous>)
at x8u (/app/node_modules/box-typescript-sdk-gen/src/schemas/accessToken.generated.ts:107:28)
at jvr.<anonymous> (/app/node_modules/box-typescript-sdk-gen/src/managers/authorization.generated.ts:294:12)
at Generator.next (<anonymous>)
at a (/app/node_modules/box-typescript-sdk-gen/src/networking/fetch.ts:380:1)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Screenshots
Not applicable
Versions Used
Typescript SDK: 1.2.0
Platform: Node
Node.js (if applicable): v20.11.0

It looks like I am able to get the desired functionality using the base_upload scope. Regardless, it seems like this missing scope is still a bug in the SDK.

Looks like item_upload scope is missing from the spec and we heavily rely on it during SDK generation - https://developer.box.com/reference/resources/access-token/#param-restricted_to-scope. I'll let the team know about the issue

Should be fixed by #281 and will be released with the next version of the SDK.


/participants : allow creations of list of participants via text area with csv

See also JSON format in #1
------------------------------------------------------
[ text area                                      ( i )]
[                                                     ]
------------------------------------------------------
[ Table Preview here                                  ]
|                 |                 |                 |
|                 |                 |                 |
|                 |                 |                 |
-------------------------------------------------------

[x] Convert sample to html
[x] Record line of error, affect html's css
[x] Allow re-editing
[x] Confirm format is valid
[x] Display html with CRUD buttons
[x] Test POST, PUT, DELETE

to be check but every point has been taking care of