HADOOP-11245. Update NFS gateway to use Netty4 (#2832) (#4997)

Reviewed-by: Tsz-Wo Nicholas Sze<EMAIL_ADDRESS>Co-authored-by: Wei-Chiu Chuang<EMAIL_ADDRESS>(cherry picked from commit 6847ec0647c3063bcbf9cf0315a77e247cae8534)
Conflicts:
hadoop-common-project/hadoop-nfs/src/main/java/org/apache/hadoop/oncrpc/RpcProgram.java

Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

Only conflicts were the guava imports.

:confetti_ball: +1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
6m  3s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s

No case conflicting files found.

+0 :ok:
codespell
0m  0s

codespell was not available.

+0 :ok:
detsecrets
0m  0s

detect-secrets was not available.

+0 :ok:
xmllint
0m  0s

xmllint was not available.

+1 :green_heart:
@author
0m  0s

The patch does not contain any @author tags.

+1 :green_heart:
test4tests
0m  0s

The patch appears to include 5 new or modified test files.

_ branch-3.2 Compile Tests _

+0 :ok:
mvndep
5m  1s

Maven dependency ordering for branch

+1 :green_heart:
mvninstall
28m 22s

branch-3.2 passed

+1 :green_heart:
compile
16m  3s

branch-3.2 passed

+1 :green_heart:
checkstyle
2m 48s

branch-3.2 passed

+1 :green_heart:
mvnsite
1m  5s

branch-3.2 passed

+1 :green_heart:
javadoc
1m  2s

branch-3.2 passed

+1 :green_heart:
spotbugs
1m 52s

branch-3.2 passed

+1 :green_heart:
shadedclient
15m 18s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+0 :ok:
mvndep
0m 23s

Maven dependency ordering for patch

+1 :green_heart:
mvninstall
0m 48s

the patch passed

+1 :green_heart:
compile
15m 24s

the patch passed

+1 :green_heart:
javac
15m 24s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

-0 :warning:
checkstyle
2m 41s
/results-checkstyle-root.txt
root: The patch generated 19 new + 140 unchanged - 7 fixed = 159 total (was 147)

+1 :green_heart:
mvnsite
1m  4s

the patch passed

+1 :green_heart:
javadoc
0m 58s

the patch passed

+1 :green_heart:
spotbugs
1m 55s

the patch passed

+1 :green_heart:
shadedclient
15m 39s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
0m 47s

hadoop-nfs in the patch passed.

+1 :green_heart:
unit
2m 47s

hadoop-hdfs-nfs in the patch passed.

+1 :green_heart:
asflicense
0m 47s

The patch does not generate ASF License warnings.

124m 34s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4999/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/4999

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell detsecrets xmllint spotbugs checkstyle

uname
Linux 2a589af0f5c5 4.15.0-192-generic #203-Ubuntu SMP Wed Aug 10 17:40:03 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/bin/hadoop.sh

git revision
branch-3.2 / 9ecd7aee74efbaa4a139ea2584f2bdea1f472588

Default Java
Private Build-1.8.0_342-8u342-b07-0ubuntu1~18.04-b07

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4999/1/testReport/

Max. process+thread count
375 (vs. ulimit of 5500)

modules
C: hadoop-common-project/hadoop-nfs hadoop-hdfs-project/hadoop-hdfs-nfs U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-4999/1/console

versions
git=2.17.1 maven=3.6.0 spotbugs=4.2.2

Powered by
Apache Yetus 0.14.0 https://yetus.apache.org

This message was automatically generated.


Better handling when things go wrong

Every few weeks something weird happens and one of the connections I am bridging breaks,
Most-often it is gitter.
Now, I don't want this fixed as such.
What I want is for a better way to handle it.
[2018-04-18T20:44:00+08:00] ERROR gitter:       connection with gitter closed for room JuliaLang/julia
[2018-04-18T20:44:00+08:00] ERROR gitter:       connection with gitter closed for room JuliaDiffEq/Lobby
[2018-04-18T20:44:08+08:00] ERROR gitter:       connection with gitter closed for room tbreloff/Plots.jl
[2018-04-18T20:44:25+08:00] ERROR gitter:       connection with gitter closed for room JunoLab/Juno
[2018-04-18T20:44:25+08:00] ERROR gitter:       connection with gitter closed for room JuliaGraphs/LightGraphs.jl
[2018-04-18T20:44:25+08:00] ERROR gitter:       connection with gitter closed for room FluxML/Lobby

This error happens. My gitter connection goes down, but the program keeps running.
However, I am not aware of it, until hours or days later since it takes a while before anyone notices that it isn't bridging (since you have to be in both chatrooms or have to be reading the logs)
I'ld rather any errors just fully crash the program,
I have it running in a script that will restart it if that occurs.
I

Most of the platform libraries (gitter, discord, slack, etc...) don't really have any good method for matterbridge to check the status of the connection and don't maintain anything as simple as a state value.
@42wim just thinking out loud, what if messages triggered something like a heartbeat that the bridge could track. I know that some (most?) of the supported platforms include a "ping" message. Maybe something can be done with that?

@jheiselman Yes, maybe. I'll have to look into this.
Also related to #116

Just logging this information here:
XMPP platforms support an XMPP ping that can be used to determine connection health.
Slack has the periodic LatencyReport event that can be used for the same purpose.
Discord has a heartbeat event with results stored in Session.LastHeartbeat(Sent|Received).
IRC servers usually implement a PING command. Something like "/PING NickServ" may prove to work for most situations. Making the ping command configurable may be a good long term solution.
Telegram has an API endpoint called help.getNearestDc that could be used as a sort of connection check.
I'm unfamiliar with any other platforms, but hope that someone can help build on this.


docs: add info about tailcalls in bpf subprograms

Here is an update to Cilium's documentation in order to reflect the current state of relationship between bpf2bpf calls and tail calls.
I tried to mimic as much as I could the style of provided image so that it follows all of the existing images.
Thanks!

@mfijalko thanks again for the submission :-) I've converted the PR to draft status for now. When you get a chance to address the review feedback, then please force-push the updated branch back here and mark the PR as "Ready for review" using the button at the bottom of the page.

@mfijalko thanks again for the submission :-) I've converted the PR to draft status for now. When you get a chance to address the review feedback, then please force-push the updated branch back here and mark the PR as "Ready for review" using the button at the bottom of the page.

Ugh, sorry, that's embarrassing. Shortly after initial pull request submission I caught covid and totally forgot about that. Thanks for review, I'll try address comments in a day or two.

@mfijalko No worries at all. I hope you're feeling better now :slightly_smiling_face:

Not sure if it's my fault that conformance test failed, but anyway I tried to address all of the review comments. Not sure where should I place versioning in github flow, commit message?
Anyway, hitting the 'ready for review' button.


Selector Timeout Between Steps

For some unknown reason, TestCafe waits for a timeout to expire before clicking on an element.
The user example uses an element whose center is overlapped by another element. However, even if you change the selector to one that is not overlapped by any others, the behavior will not change.
More information in T1116871.

This behavior is correct. There are two clicks at the end and the delay occurs in the last one. It may seem that it occurs in the previous one, because nothing happens. The reason why nothing happens is that the button's event in this action doesn't have sufficient time to be bound to this button. To resolve this issue, you need to add a timeout of approximately 300ms before this action.


Add legend title in TADA_GroupedScatterPlot

Add a legend title for TADA_GroupedScatterPlot
Describe the solution you'd like:
For specifying what groups to plot on the figure, sometimes it could be unclear what groups are being plotted, such as for CountyCode. Adding a legend title would assist those who view the graph to understand what is being plotted.

Attempted to put a legend title in the plot, but it shows up to the left of the legend labels. Did try to spend some time to make it show above, but could not figure out. May be a simple item to address but is not urgent. Will comment the line of code out for now, but can be looked into if anyone wants to try to format it in the future.
legend = list(           title = list(text = paste0('<b>', group_col,'<b>'), x = 0.5, y= 100),           orientation = "h",           xanchor = "center",           x = 0.5         )

@wokenny13 - can you link this to the branch you've been using to work on it?

#504 I believe I pushed that commit through with that small code update to this branch


rbd: log sitestatuses and description

This commit logs sitestatues and description in
GetVolumeReplicationInfo RPC call for better
debuging.
Fixes: #4430

Haven't tested the PR yet, Will request for reviw and add the output log once done.
Thanks

Marking this as Draft for now, please update the PR description with the results of your testing.

Here's the log from rbdplugin pods.
I0215 16:35:19.925403       1 replication.go:804] ID: 24 Req-ID: 0001-0011-openshift-storage-0000000000000001-9dccf869-40a9-4125-9a00-2d2011346d55 GetVolumeReplicationInfo rpc call
I0215 16:35:19.928315       1 omap.go:89] ID: 24 Req-ID: 0001-0011-openshift-storage-0000000000000001-9dccf869-40a9-4125-9a00-2d2011346d55 got omap values: (pool="ocs-storagecluster-cephblockpool", namespace="", name="csi.volume.9dccf869-40a9-4125-9a00-2d2011346d55"): map[csi.imageid:1c8ae58015560 csi.imagename:csi-vol-9dccf869-40a9-4125-9a00-2d2011346d55 csi.volname:pvc-026b0c93-666a-4c14-988c-1a4f013955db csi.volume.owner:appset-busybox-1]

I0215 16:35:19.947049       1 replication.go:920] ID: 22 Req-ID: 0001-0011-openshift-storage-0000000000000001-8d68260e-6e34-4583-aa07-cc57adf8c457 Site Statuses: [{ stopped local image is primary %!s(int64=1708014906) %!s(bool=true)} {741b47ec-4914-4998-98cb-f74c940c9f4e replaying replaying, {"bytes_per_second":60347.73,"bytes_per_snapshot":1839104.0,"last_snapshot_bytes":1810432,"last_snapshot_sync_seconds":0,"local_snapshot_timestamp":1708014905,"remote_snapshot_timestamp":1708014905,"replay_state":"idle"} %!s(int64=1708014914) %!s(bool=true)}]
I0215 16:35:19.947075       1 replication.go:956] ID: 22 Req-ID: 0001-0011-openshift-storage-0000000000000001-8d68260e-6e34-4583-aa07-cc57adf8c457 description="replaying, {\"bytes_per_second\":60347.73,\"bytes_per_snapshot\":1839104.0,\"last_snapshot_bytes\":1810432,\"last_snapshot_sync_seconds\":0,\"local_snapshot_timestamp\":1708014905,\"remote_snapshot_timestamp\":1708014905,\"replay_state\":\"idle\"}"

Here's the updated log:
Site Statuses: [{ stopped local image is primary %!s(int64=1708321957) %!s(bool=true)} {741b47ec-4914-4998-98cb-f74c940c9f4e replaying replaying, {"bytes_per_second":0.0,"bytes_per_snapshot":0.0,"last_snapshot_bytes":0,"last_snapshot_sync_seconds":0,"local_snapshot_timestamp":1708321800,"remote_snapshot_timestamp":1708321800,"replay_state":"idle"} %!s(int64=1708321967) %!s(bool=true)}]
I0219 05:52:49.392252       1 replication.go:921] ID: 25 Req-ID: 0001-0011-openshift-storage-0000000000000001-4a99c0b1-5ec1-432e-a659-e72e200e1967 Site Statuse: stopped local image is primary<PHONE_NUMBER> true
I0219 05:52:49.392261       1 replication.go:910] ID: 25 Req-ID: 0001-0011-openshift-storage-0000000000000001-4a99c0b1-5ec1-432e-a659-e72e200e1967 Site Statuse of MirrorUUID:741b47ec-4914-4998-98cb-f74c940c9f4e: replaying replaying, {"bytes_per_second":0.0,"bytes_per_snapshot":0.0,"last_snapshot_bytes":0,"last_snapshot_sync_seconds":0,"local_snapshot_timestamp":1708321800,"remote_snapshot_timestamp":1708321800,"replay_state":"idle"}<PHONE_NUMBER> true

%!s(int64=1708321957) %!s(bool=true)}

still log contains %!s

%!s(int64=1708321957) %!s(bool=true)}

still log contains %!s

yeah, that's the older change, kept it to get your reviews. If logging the site statues individually work for you, or it have to be printed as the list too? I will update the PR accordingly.
cc @Madhu-1

Test Output:
I0219 09:39:27.058312       1 replication.go:906] ID: 22 Req-ID: 0001-0011-openshift-storage-0000000000000001-4a99c0b1-5ec1-432e-a659-e72e200e1967 Site Statuse of MirrorUUID:, state: stopped, description: local image is primary, lastUpdate:<PHONE_NUMBER>, up: true
I0219 09:39:27.058325       1 replication.go:906] ID: 22 Req-ID: 0001-0011-openshift-storage-0000000000000001-4a99c0b1-5ec1-432e-a659-e72e200e1967 Site Statuse of MirrorUUID:741b47ec-4914-4998-98cb-f74c940c9f4e, state: replaying, description: replaying, {"bytes_per_second":0.0,"bytes_per_snapshot":0.0,"last_snapshot_bytes":0,"last_snapshot_sync_seconds":0,"local_snapshot_timestamp":1708335300,"remote_snapshot_timestamp":1708335300,"replay_state":"idle"}, lastUpdate:<PHONE_NUMBER>, up: true

@mergifyio rebase

@mergifyio queue

/cherry-pick release-4.15

/cherry-pick release-4.15

@yati1998 cherr-pick to downstream branch doesn't work in this repo and also please take care of backporting https://github.com/ceph/ceph-csi/pull/4429 with this commit

@mergifyio backport release-3.10

@Mergifyio backport release-v3.10


TypeError: Cannot redefine property: default

TypeScript Version:  3.9.3
Code
file1.js
module.exports = {
  default: {
    log() {
    }
  },
}

file2.ts
import file1 from './file1'
file1.log()

Actual behavior:
TypeError: Cannot redefine property: default

Related Issues: #38552

This is likely a duplicate of https://github.com/microsoft/TypeScript/issues/38540

I actually can't reproduce the issue in the OP - @zhinanchendd01 is there more context to this? Or a specific set of compiler options? I've tried both with and without esModuleInterop on, and can't replicate your result.

I just had this with TypeScript 3.9.3. This is my tsconfig.json:
{
  "compilerOptions": {
    "target": "es2018",
    "module": "commonjs",
    "outDir": "./lib",
    "rootDir": "./src",
    "strict": true,
    "esModuleInterop": true
  },
  "exclude": [
    "test"
  ]
}

I found out that this fails:
import sequelize, { Op, Sequelize } from 'sequelize';

But this works:
import { Op, Sequelize } from 'sequelize';
import sequelize from 'sequelize';

I just had this with TypeScript 3.9.3. This is my tsconfig.json:
{
  "compilerOptions": {
    "target": "es2018",
    "module": "commonjs",
    "outDir": "./lib",
    "rootDir": "./src",
    "strict": true,
    "esModuleInterop": true
  },
  "exclude": [
    "test"
  ]
}

I found out that this fails:
import sequelize, { Op, Sequelize } from 'sequelize';

But this works:
import { Op, Sequelize } from 'sequelize';
import sequelize from 'sequelize';

This solved the whole thing.. Thank you

Same exact thing is happening to me with sequelize right after going from 3.8.3 to 3.9.3. Is this expected or is it a regression?

Just saw there's a fix already in #38540

my tsconfig.json
{
	"compileOnSave": true,
	"compilerOptions": {
		"target": "es2018",
		"module": "commonjs",
		"esModuleInterop": true,
		"outDir": "dist",
		"baseUrl": "src",
	},
	"exclude": ["dist", "node_modules"]
}

logger.js
const info = (...args) => {
  console.log(...args)
}

const debug = (...args) => {
  console.debug(...args)
}

module.exports = { info, debug }

module.exports.default = { info, debug }

index.ts
this failed:
import * as logger from './logger'
logger.debug('debug 1')
// TypeError: Cannot redefine property: default

this can work:
import logger from './logger'
logger.debug('debug 1')

@weswigham

logger.js
const info = (...args) => {
  console.log(...args)
}

const debug = (...args) => {
  console.debug(...args)
}

module.exports.default = { info, debug }

index.ts
import logger from './logger'
logger.info('info')
// TypeError: logger_1.default.info is not a function

console.log(logger)
// { default: { info: [Function: info], debug: [Function: debug] } }

This actually appears to be fixed for my code in v3.9.4, but it's not currently published to npm with the latest tag.

But this works:
import { Op, Sequelize } from 'sequelize';
import sequelize from 'sequelize';

I have exactly the same issue – for some reason I cannot write:
import parse, { domToReact } from 'html-react-parser';

I have to split it into two lines.

This helps me.
    "typescript": "3.9.7",
    "tslib": "1.13.0"


Cleanup

The purpose of this PR is to remove all unnecessary bricks for La Patate du Coin and to update the dependencies

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@f06e713). Click here to learn what that means.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff            @@
##             master       #1   +/-   ##
=========================================
  Coverage          ?   78.46%
=========================================
  Files             ?      484
  Lines             ?     6505
  Branches          ?      571
=========================================
  Hits              ?     5104
  Misses            ?      903
  Partials          ?      498

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


feat(csi): csi controller plugin

This commit introduces a new CSI Controller plugin, which uses Control Plane’s new REST API
and is deployed as a separate conainerised application.
Resolves: CAS-1065

bors r+

bors merge

bors merge

bors merge


Registry tool: compute conformance requires exact matches of spec mime types

Currently compute conformance will only run on specs whose mime types exactly match the mime types listed in the style guide. This can make linting fragile -- a style guide might include application/x.openapi+gzip;version=3 in its mime types  and fail to match specs with any of these similar types:

application/x.openapi+gzip;version=3.0.0
application/x.openapi+gzip;version=3.0
application/x.openapi;version=3

I think a reasonable solution to this would be to accept wildcards or regular expressions in the styleguide mime type list, but let's consider both of these possibilities and any other suggestions with mock style guides (in this thread) before making code changes.

https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#filter-pattern-cheat-sheet


What is the recommended alternative to GdsLibrary.extract

I just saw the note regarding the GdsLibrary.extract method being deprecated eventually. Is the cells dictionary the recommended accessor for a cell object?

@ncFoCo GdsLibrary.extract was used only to add a cell from the library to gdspy.current_library, but that is also deprecated now. The better way to manage libraries is to simply use GdsLibrary.add, which, as a bonus, can also handle dependencies.
Instead of:
# Load a GDSII file
imported_lib = gdspy.GdsLibrary(infile="mylib.gds")

# Extract a cell and implicitly add it to gdspy.current_library (without dependencies)
imported_lib.extract("SOME_CELL")

# Implicitly save gdspy.current_library
gdspy.write_gds("newlib.gds")

this is more explicitly and less error-prone:
# Load a GDSII file
imported_lib = gdspy.GdsLibrary(infile="mylib.gds")

# Create a new library and add imported cell (including dependencies)
new_lib = gdspy.GdsLibrary()
new_lib.add(imported_lib.cells["SOME_CELL"])

# Save new library
new_lib.write_gds("newlib.gds")

@heitzmann That answers my question. Thanks for the quick response.


Research for native Unicode Collator

Currently JSONCollator uses java.text.Collator for string. It makes SQLite insertion slow. To improve performance, we need implement native collator.

Non-ICU implementations

http://unicode.org/reports/tr10/Sample/
https://github.com/jtauber/pyuca

NSString uses ICU

https://github.com/timburks/gnustep-base/blob/master/Source/NSString.m#L5087-L5138

This task was done with the issue.


Support jooq 3.19.*

Is your feature request related to a problem? Please describe.
Do you have any plan to support jooq 3.19.*? I have a try, but Caused by: java.lang.NoSuchMethodError: 'org.jooq.Converter org.jooq.Field.getConverter()'.

Thank you for your report. Let me try my best to get back to you as soon as possible.
I assumed you're using v2.0.0-rc1

Hi @yueliangwen
I cannot reproduce your error.
I thought there were some dependency conflicts, please make sure you override Vert.x and jOOQ version in your build descriptor (pom.xml or gradle.build)
I closed this ticket, however, if anything is unclear, please leave a message.
Thanks

jooqx.tar.gz
Steps to Reproduce：
1、Download the jooqx.tar.gz
2、Read the README.adoc, ./gradlew clean run
3、Configure the PostgreSQL instance

4、curl http://localhost:8888/dump, you will see the problem.
Change the jooq version to 3.17.21, there's no problem.

thank you for the reproduction. That helps me a lot to detect a reason:
since jooq >= 3.17 uses java 17 as the default. Not pretty sure why<EMAIL_ADDRESS>is still fine, but jooq >= 3.18.x raises an error. Somehow, jooqx is not compatible anymore with jooq when running java 17, which leads to NoSuchMethodError at runtime.
I reproduced it by unit-test that already re-compiled jooqx on java17, then the error didn't happen
I will find a time this week to make a release to make jooqx lib compatible in java17+

Hi @yueliangwen
Could you pls try jooqx version 2.0.0-rc.1:jdk17?
Unfortunately, something's weird in gradle build, then I cannot keep the previous rc version.
  implementation("io.github.zero88:jooqx:2.0.0-rc.1:jdk17")
  implementation("io.github.zero88:jooqx-spi:2.0.0-rc.1:jdk17")

That is a matrix version

jooqx
jooq
jdk

2.0.0-rc1
< 3.18
any

2.0.0-rc.1:jdk17
>= 3.18
jdk17+

I will upgrade to jdk17 as default in the next release.
Thank you for your patience!!!

Hi @zero88
I rerun some simple examples, it works well. Thanks for your great job.


[FLINK-25351] Introduce FlinkVersion as a global enum

What is the purpose of the change
Rename MigrationVersion to FlinkVersion and move it to
flink-annoations org.apache.flink package so that is available
globally and will facilitate the APIs and SQL/TableAPI versioning
and upgrades.
Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): no
The public API, i.e., is any changed class annotated with @Public(Evolving): yes
The serializers: no
The runtime per-record code paths (performance sensitive): no
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper:no
The S3 file system connector: no

Documentation

Does this pull request introduce a new feature? yes
If yes, how is the feature documented? update release guide

@tillrohrmann @twalthr Thank you! Moved to flink-annotations please check again.


getting error: RuntimeError: main thread is not in main loop

29-Jan-17 18:39:08 ERROR     Exception in message dispatch.  Handler '__on_tick_event' for 'tickPrice'
Traceback (most recent call last):
File "/hft/High-Frequency-Trading-Model-with-IB/envz/lib/python2.7/site-packages/ib/opt/dispatcher.py", line 44, in call
results.append(listener(message))
File "hft/High-Frequency-Trading-Model-with-IB/models/hft_model.py", line 323, in __on_tick_event
self.__update_charts()
File "/hft/High-Frequency-Trading-Model-with-IB/models/hft_model.py", line 334, in __update_charts
self.strategy_params.indicators)
File "/hft/High-Frequency-Trading-Model-with-IB/classes/chart.py", line 28, in display_chart
plt.pause(0.01)
File "/hft/High-Frequency-Trading-Model-with-IB/envz/lib/python2.7/site-packages/matplotlib/pyplot.py", line 298, in pause
canvas.draw()
File "/hft/High-Frequency-Trading-Model-with-IB/envz/lib/python2.7/site-packages/matplotlib/backends/backend_tkagg.py", line 352, in draw
tkagg.blit(self._tkphoto, self.renderer._renderer, colormode=2)
File "/hft/High-Frequency-Trading-Model-with-IB/envz/lib/python2.7/site-packages/matplotlib/backends/tkagg.py", line 22, in blit
id(data), colormode, id(bbox_array))
RuntimeError: main thread is not in main loop

i have added the below lines to the chart.py. I can see the chat created by matplotlib but i get this error: "RuntimeError: main thread is not in main loop."
import matplotlib as mpl
mpl.use('TKAgg')

When i replace the above line to the lines given below then it works without an error but no chart is shown:
import matplotlib as mpl
mpl.use('Agg')

the error is on the chart.py file on this command:
plt.pause(0.01)
please reply.

This is a matplotlib issue, Be sure to run your program in a main loop.
https://www.google.com.sg/search?q=matplotlib+main+thread+is+not+in+main+loop&ie=utf-8&oe=utf-8&client=firefox-b-ab&gfe_rd=cr&ei=2OHoWJLZLJDx8Af-xJbYDg


Error while running Tensor-Flow examples using Bazel build

Please go to Stack Overflow for help and support:
https://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug or a feature request.
The form below must be filled out.
It shouldn't be a TensorBoard issue. Those go here.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

**Ubuntu 16.04:
**TensorFlow installed from source:
**TensorFlow version 1.4.0:
**Python 3.5.2:
**Bazel version 0.8.1:
gcc version 5.4.1:
CUDA/cuDNN version:
GeForce GTX 980M  and 8GB:
bazel build tensorflow/examples/label_image/...:

I am trying to run this by using the command bazel build tensorflow/examples/label_image/...
but i am getting the following error:
In file included from ./tensorflow/core/platform/default/logging.h:24:0,
                 from ./tensorflow/core/platform/logging.h:25,
                 from ./tensorflow/core/lib/core/status.h:25,
                 from ./tensorflow/core/kernels/range_sampler.h:21,
                 from tensorflow/core/kernels/range_sampler.cc:16:
./tensorflow/core/platform/default/logging.h: In instantiation of 'std::__cxx11::string* tensorflow::internal::Check_LEImpl(const T1&, const T2&, const char*) [with T1 = long unsigned int; T2 = long long int; std::__cxx11::string = std::__cxx11::basic_string<char>]':
tensorflow/core/kernels/range_sampler.cc:86:5:   required from here
./tensorflow/core/platform/default/logging.h:230:35: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
 TF_DEFINE_CHECK_OP_IMPL(Check_LE, <= )
                                   ^
./tensorflow/core/platform/macros.h:79:29: note: in definition of macro 'TF_PREDICT_TRUE'
 #define TF_PREDICT_TRUE(x) (x)
                             ^
./tensorflow/core/platform/default/logging.h:230:1: note: in expansion of macro 'TF_DEFINE_CHECK_OP_IMPL'
 TF_DEFINE_CHECK_OP_IMPL(Check_LE, <= )
 ^
./tensorflow/core/platform/default/logging.h: In instantiation of 'std::__cxx11::string* tensorflow::internal::Check_EQImpl(const T1&, const T2&, const char*) [with T1 = long long int; T2 = long unsigned int; std::__cxx11::string = std::__cxx11::basic_string<char>]':
tensorflow/core/kernels/range_sampler.cc:244:3:   required from here
./tensorflow/core/platform/default/logging.h:228:25: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
                         == )  // Compilation error with CHECK_EQ(NULL, x)?
                         ^
./tensorflow/core/platform/macros.h:79:29: note: in definition of macro 'TF_PREDICT_TRUE'
 #define TF_PREDICT_TRUE(x) (x)
                             ^
./tensorflow/core/platform/default/logging.h:227:1: note: in expansion of macro 'TF_DEFINE_CHECK_OP_IMPL'
 TF_DEFINE_CHECK_OP_IMPL(Check_EQ,
 ^
ERROR: /home/hassaan/Downloads/tensorflow/tensorflow/core/BUILD:1739:1: C++ compilation of rule '//tensorflow/core:framework_internal_impl' failed (Exit 1)
In file included from ./tensorflow/core/framework/allocator.h:23:0,
                 from ./tensorflow/core/framework/tensor.h:20,
                 from ./tensorflow/core/util/strided_slice_op.h:18,
                 from tensorflow/core/util/strided_slice_op.cc:16:
./tensorflow/core/framework/numeric_types.h: In constructor 'tensorflow::bfloat16::bfloat16(float)':
./tensorflow/core/framework/numeric_types.h:49:16: error: 'isnan' was not declared in this scope
     if (isnan(v)) {
                ^
./tensorflow/core/framework/numeric_types.h:49:16: note: suggested alternatives:
In file included from /usr/include/c++/5/complex:44:0,
                 from external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/Core:99,
                 from external/eigen_archive/unsupported/Eigen/CXX11/Tensor:14,
                 from ./third_party/eigen3/unsupported/Eigen/CXX11/Tensor:1,
                 from ./tensorflow/core/framework/tensor.h:19,
                 from ./tensorflow/core/util/strided_slice_op.h:18,
                 from tensorflow/core/util/strided_slice_op.cc:16:
/usr/include/c++/5/cmath:641:5: note:   'std::isnan'
     isnan(_Tp __x)
     ^
In file included from external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/Core:558:0,
                 from external/eigen_archive/unsupported/Eigen/CXX11/Tensor:14,
                 from ./third_party/eigen3/unsupported/Eigen/CXX11/Tensor:1,
                 from ./tensorflow/core/framework/tensor.h:19,
                 from ./tensorflow/core/util/strided_slice_op.h:18,
                 from tensorflow/core/util/strided_slice_op.cc:16:
external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/GlobalFunctions.h:88:3: note:   'Eigen::isnan'
   EIGEN_ARRAY_DECLARE_GLOBAL_UNARY(isnan,scalar_isnan_op,not-a-number test,\sa Eigen::isinf DOXCOMMA Eigen::isfinite DOXCOMMA ArrayBase::isnan)
   ^
In file included from external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/Core:392:0,
                 from external/eigen_archive/unsupported/Eigen/CXX11/Tensor:14,
                 from ./third_party/eigen3/unsupported/Eigen/CXX11/Tensor:1,
                 from ./tensorflow/core/framework/tensor.h:19,
                 from ./tensorflow/core/util/strided_slice_op.h:18,
                 from tensorflow/core/util/strided_slice_op.cc:16:
external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/MathFunctions.h:1111:46: note:   'Eigen::numext::isnan'
 template<typename T> EIGEN_DEVICE_FUNC bool (isnan)   (const T &x) { return internal::isnan_impl(x); }
                                              ^
In file included from external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/Core:433:0,
                 from external/eigen_archive/unsupported/Eigen/CXX11/Tensor:14,
                 from ./third_party/eigen3/unsupported/Eigen/CXX11/Tensor:1,
                 from ./tensorflow/core/framework/tensor.h:19,
                 from ./tensorflow/core/util/strided_slice_op.h:18,
                 from tensorflow/core/util/strided_slice_op.cc:16:
external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/arch/CUDA/Half.h:380:45: note:   'Eigen::half_impl::isnan'
 EIGEN_STRONG_INLINE EIGEN_DEVICE_FUNC bool (isnan)(const half& a) {

What options did you specify in your configure step, and are you specifying a --config in your build command?

It looks like isnan is missing in both allocator.h and Eigen/Core. The correct identifier and place to get it in C++11 is <cmath>. Would you mind checking if it's properly included, and if not, send a PR?

@drpngx  - looks like this was addressed in a PR a few days ago: https://github.com/tensorflow/tensorflow/pull/15189

Thanks @quaeler ! @hassaanseeker can you confirm?

Thanks a lot guys yes the issue was resolved by replacing if (isnan(v)) with if (Eigen::numext::isnan(v)) on line 49 in tesnorflow/core/framework/numeric_types.h.

This should be closed then


Login Issue - No Redirect

Can't Login.
After logging in the credentials, The app just redirects to Udemy Website
it does not shows Udeler UI Anymore ( No Courses)
Only showing Udemy Webpage in App itself
Please check

I am getting the same issue as well. Please HELP!!!

I am getting the same issue as well. Please HELP!!!

I have the same issue here as well. Please help out.

I have the same issue

The problem is already being verified, for now it is possible to connect only with access_token

https://github.com/heliomarpm/udemy-downloader-gui/issues/5


Add more auto-generated conan files to .gitignore

New or update
Select the appropriate check box for this pull request. This helps when merging to ensure there are no conflicts with other templates or misunderstandings of how thee template list works.
New

[ ] Template - New .gitignore template
[ ] Composition - Template made from smaller templates
[ ] Inheritance - Template similar to an existing template
[x] Patch - Template extending functionality of existing template

Details
Add more auto-generated conan files created by cmake_find_package, cmake_paths and virtualenv generators.

May I ask, what's the motivation behind ignoring these files? Commonly, with C/C++ and CMake project as well as with Conan all generated files end up in an out-of-tree build folder, e.g. using --install-folder with Conan. See also the relevant section from the pitchfork layout about the build folder. It's then only necessary to ignore the build folder to also ignore all files generated by Conan.
On the other hand (even when using Conan), projects sometimes do want to ship custom Find*.cmake files (e.g. not all dependencies are handled by Conan, but some other CMake toolchains).


How to avoid big % Dropped

Hello i want to scan all collection
I read that to improve accuracy, you need to increase the density. I increased the Desity parameter from 20 to 100 and the result is a higher % Dropped. (for example YOUTUBE 01 D2.pklz (79.70% dropped)) Some of the records became less recognizable than with standard Density = 20
How can I increase the output file and decrease the % Dropped to increase the overall recognition accuracy. I take as a basis the material I want to recognize low quality audio from tapes from the early 90's, so accuracy is important. It doesn't matter how much space the database of fingerprints will take up.

“% dropped” comes from buckets overflowing in the database. You can
increase the database size with the bucketsize flag; the default is 100.
The database in memory will grow in proportion, and at some point you’ll
run out of RAM.
DAn.
On Wed, Mar 6, 2024 at 07:27 lightcomc @.***> wrote:

Hello i want to scan all collection
I read that to improve accuracy, you need to increase the density. I
increased the Desity parameter from 20 to 100 and the result is a higher %
Dropped. (for example YOUTUBE 01 D2.pklz (79.70% dropped)) Some of the
records became less recognizable than with standard Density = 20
How can I increase the output file and decrease the % Dropped to increase
the overall recognition accuracy. I take as a basis the material I want to
recognize low quality audio from tapes from the early 90's, so accuracy is
important. It doesn't matter how much space the database of fingerprints
will take up.
—
Reply to this email directly, view it on GitHub
https://github.com/dpwe/audfprint/issues/94, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEGZUKBROI5XN6CAC73KYLYW4DRZAVCNFSM6AAAAABEI6VCB6VHI2DSMVQWIX3LMV43ASLTON2WKOZSGE3TCMZYHE3TKMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thank you i'll check thatt parameter to find optimal size and memory comsumption in process, speed is not critical.

You can try to use my fork with some minor changes. Recognition speed is increased and memory consumption is reduced. - https://github.com/ZhymabekRoman/audfprint-enhanced

You can try to use my fork with some minor changes. Recognition speed is increased and memory consumption is reduced. - https://github.com/ZhymabekRoman/audfprint-enhanced

Are you doing any active commits anymore?

You can try to use my fork with some minor changes. Recognition speed is increased and memory consumption is reduced. - ZhymabekRoman/audfprint-enhanced

Are you doing any active commits anymore?

Yeap


remove support for EOL python 3.7

explicitly remove support for py3.7 from setup.py and requirements.txt. build examples/environment.yml with py3.10
re issue #309

n.b. I am @aleks-sch who opened #309, I just had to make changes on personal device bc I couldn't test creating the conda env from inside Schroders network

Thanks for that. But shouldn't the version number be 2.0.0 if we follow SemVer? Also, we need to update the version number in pyproject.toml as well. But I think we can do this within a few days.

good catch! yes v2.0.9 an oversight, will push change when I am back on personal PC (can't now due to corporate personal GH restrictions)

Please also update the version number in pyproject.toml to 2.0.0. Thanks


Configure dependabot to auto-merge PRs with minor updates

Fully automatic auto-merge is not possible. Auto-merge is only available if the review of at least 1 contributor is available.


Remoting: Support for camera-dependent modes

In my case, support for at least Active Observation Mode during remoting would definitely be helpful.

[...] as far as AOA Remoting support goes, there are a couple of caveats - specifically, features which require camera access do currently not work with Remoting. This includes "Active Observation Mode" and "High Accuracy High Latency" tracking mode. However, basic object detection and tracking should work well in the Editor. We may add support for camera-dependent modes in the future; please file a feature request if this is something that would be valuable for your workflow.

Originally posted by @dfields-msft in https://github.com/Azure/azure-object-anchors/issues/22#issuecomment-1078522290

@dfields-msft on this one as well.

This corresponds to internal reference number 38630868.


Feature Request: Auto refill

A feature request to have the item that breaks in a swapper auto refill with another one from user inventory

I'm not sure if this should be a separate enhancement request or not, but it would be nice if the replacing broken tool behavior was extended to items like cobble/torches in the right-click slot. Thanks.

I had the same issue when i removed a mod. I removed those items as in removed the mod and readd it. So whast items do you see/have that are blanked out?

It's not items being blanked out. If you have a stack of standard cobblestone in the rclick slot, and use all 64 the slot doesn't attempt to refill from your inventory. Though it does from cobblestone being picked up. What I'm asking for is if the rclick slot is emptied, check the players inventory for more of that item and refill. That way I don't have to constantly reopen the swapper to add a new stack of cobblestone/torches once I've emptied it when I'm building/caving.

I think inventory tweaks is able to do that

Inventory Tweaks doesn't support altering the items inside of the Swapper at all. And yes, I do have both mods installed.


Target PHP 5.5

I think everyone agrees that this should be the version we support, right?

Solving this issue is pretty easy: Delete composer.lock and patch the composer.json:
diff --git a/composer.json b/composer.json
index e1137d0..877e4c8 100644
--- a/composer.json
+++ b/composer.json
@@ -2,8 +2,8 @@
     "name": "klaussilveira/gitlist",
     "description": "An elegant git repository viewer",
     "require": {
-        "silex/silex": "~2.2",
-        "twig/twig": "~2.4",
+        "silex/silex": "~2.0",
+        "twig/twig": "*",
         "symfony/twig-bridge": "~3.0",
         "symfony/filesystem": "~3.0",
         "klaussilveira/gitter": "0.2.*"

Although I hate this lock-file in the repository, it is recommended to be kept inside the repository. What's your opinion on it @klaussilveira?

i wnat to use also php 5.4 or at leas 5.5! php 7 are not supported by my vendor provider!

Silex 2 requieres at least PHP 5.5.9, so 5.4 isn't possible at all. How to achieve a maximum supported platforms needs to be discussed (composer.lock).

ok, silex2 are since that specified commit and due for what?
i mean, why was updated silex 2?
and i now understand the deletion of comment..

Dependencies will be updated on a regular basis, e.g. for performance- and security-updates. In addition the new API of Silex was required for other features like additional services that may be registered (see #739).

@klaussilveira I think some of the features recent versions of the dependencies are using could be very useful. E.g. recent versions of Twig use more type hinting which is good for type safety. So generally disabling all PHP 7 stuff might be no good idea.
I think we shouldn't use the composer.lock file for a maximum flexibility and get recent versions of the dependencies for recent versions of PHP, but also pack a separate tarball of GitList for PHP 5.x with older versions of the dependencies for backwards compatibility. Without the composer.lock, this could be done automatically in Travis CI on new releases.

I'm not keeping up with the technical conversation above. Is gitlist ver 0.6.0 supported for PHP 5.6.30-0+deb8u1.netgear1?
When I installed 0.6.0 I got the error message:

PHP Catchable fatal error: Argument 1 passed to Twig_Filter::__construct() must be an instance of string, string given, called in /data/website/gitlist/src/Application.php on line 70 and defined in /data/website/gitlist/vendor/twig/twig/lib/Twig/Filter.php on line 35

Searching the web indicated I had to upgrade to PHP ver 7 for Twig v2+. Whilst probably possible, that's going to entail a whole host of grief, so I've rolled back to the 0.5.0 tarball. The text above seemed to suggest you were still aiming for PHP 5.5.

I've been thinking of switching the router to nikic's: https://github.com/nikic/FastRoute. Combined with Pimple, that would reduce our min target to 5.4.

oh dear...
Issue can be closed.
After I looked at it again now I realized 'repositories' folder was lacking rw for www-data user...
I am so sorry for wasting time.

@tobi-the-fraggel wrong issue? ;)

I realized shortly after and deleted my post. I was so shocked by my discovery.^^

1.0.0 now targets 5.3 for maximum compatibility.


⚠ Bofrost.de has degraded performance

In edd5ada, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 2320 ms

Resolved: Bofrost.de performance has improved in dc0e60f after 6 minutes.


Polymer.Base.splice doesn't properly update the underlying collection's keyMap correctly

When processing a splice, a new key is generated. That key is not the correct index position of the item within the array. Its whatever comes after the last index. This in turn messes up any future calls to Polymer.Base.set for a property of an item of that array.
You'd call this.set('items.55.prop', false), and internally, the path would change from 'items.55.prop' to 'items.237.prop' or something like that. And when you get to any changed observer for 'items.*', the record contains the new messed up path, and ultimately you can't do anything with it.

I ran into a similar (if not the same) issue while building a polymer element which renders a form from a JSON Schema.
deep breath
The element is used by specifying the schema on the element and it recurses specifying the child property's schema and its path for this.set it all works fine up to and including adding items to an 'array' type property. There is an observer on formData.* that watches for updates to values from form elements. All works fine and dandy until you splice an item out of an array and then change values in the form at which point the set() function will look like this.set('formData.pets.1.type', 'dog'); (correct) but the observer will be notified with {path: 'formData.pets.2.type'} because set() internally uses Polymer.Collection.get(array).getKey(prop); which will return 2 for formData.pets.1 because the map does not get updated on splice.
My workaround is the following:
// this gets called on-value-changed of form elements
this.set(this.schemaPath, e.target.value);
// workaround (both lines required)
this.notifyPath(this.schemaPath, e.target.value);

because notifyPath does not try to resolve a path to its Collection equivalent like set() does it will (thankfully) blindly accept that this is the correct path and will update the value appropriately. Now, interestingly enough this does not break if you push() an item to the array after splicing because of the aforementioned "bug". The new item will be at Collection index 3, not Collection index 2 which would break the notifyPath() workaround.
This was "fun" to debug

I think I'm encountering an issue related to this one -- the problem seems to originate in Polymer.Collection.prototype._arraySplices (I intend to follow up tomorrow with a simple test case).  I may be fundamentally misunderstanding what Polymer.Collection has to do, but I'm interested in drafting a PR with some recommendations.  However, I am having some trouble understanding exactly what is expected to be in each of the keySplices.  Can someone enlighten me (perhaps you @kevinpschaaf )?
As far as I can tell, for an array of indexSplices:
keySplices = indexSplices.map(function (iSplice) {
  return {
    added:
  };
});

function numArray (length) {

}

Here's a jsbin I hope should help illuminate the problematic conditions I'm seeing -- https://jsbin.com/retujemaqi/3/edit?html,output

I tried to reproduce this problem in Polymer 2 (http://jsbin.com/durajuciqu/edit?html,console,output) and it seems that all paths are correct. Therefore I am closing this issue. If you can modify my JSBin to again show the error, we can reopen this issue and debug further 😄


Hotspot Shield VPN Cracked APK v6.9.7 for Android

Hotspot Shield VPN Cracked APK v6.9.7 for Android
Hotspot Shield VPN Cracked APK is a virtual private network or VPN that is used to encrypt user traffic and exchange data securely and anonymously. It gives you true online freedom-bypass geo-restrictions with one click and access the world’s content from anywhere.

Download Link


The rabbitmq-broker.rabbitmq.ssl job property is not used

Hi there,
Deploying RabbitMQ with TLS enabled, I saw that the rabbitmq-broker.rabbitmq.ssl property from the rabbitmq-broker job spec is actually never used by the job.
It would be nice from you to remove it so that people deploying this BOSH release don't get confused.
Thank you.
Best

Hi @bgandon,
We think that this property is used here.
In our template here we take all the properties of the rabbitmq-broker and pass them to the job. So, it's passed implicitly.
Please, feel free to ping us if you have any doubts.
@mkuratczyk and @nodo


egressgateway: Allow several CENPs with same egress IP

In commit a783f7c5 ("k8s/cilium Event handlers and processing logic for egress nat policy"), having several CENPs with the same egress IP was explicitly disallowed. As explained in https://github.com/cilium/cilium/issues/17678, the rationale was that those egress IPs are sometimes associated with security identities in external applications. However, this limitation is also preventing legitimate use cases. Users who would like to prevent this can implement it on top of Cilium.
This pull request removes the restriction.
Fixes: https://github.com/cilium/cilium/pull/15134.
Fixes: https://github.com/cilium/cilium/issues/17678.

/test

Tests are passing. Janitor review was only required because of missing CODEOWNER (fixed in https://github.com/cilium/cilium/pull/17774). Marking ready to merge.

Thanks @nathanjsweet to make the change.


neonvm/vm-builder: Add --enable-file-cache flag (default: off)

Previous to this, there was no way to enable the vm-informant's file cache integration in vm-builder (needed to use vm-builder-generic instead).
Resolves #264.
Remaining items

[ ] Test that this works as expected ("off" handled by e2e tests, "on" needs to be done manually)

Checked this locally by modifying the makefile and vm-deploy.yaml:
Patch
diff --git a/Makefile b/Makefile
index 293e64e..6431a25 100644
--- a/Makefile
+++ b/Makefile
@@ -191,7 +191,7 @@ docker-build-scheduler: ## Build docker image for (autoscaling) scheduler

 .PHONY: docker-build-examples
 docker-build-examples: vm-informant bin/vm-builder ## Build docker images for testing VMs
-	./bin/vm-builder -src postgres:15-bullseye -dst $(E2E_TESTS_VM_IMG)
+	./bin/vm-builder --enable-file-cache -src postgres:15-bullseye -dst $(E2E_TESTS_VM_IMG)

 .PHONY: docker-build-pg14-disk-test
 docker-build-pg14-disk-test: vm-informant bin/vm-builder-generic ## Build a VM image for testing
diff --git a/vm-deploy.yaml b/vm-deploy.yaml
index d7a6940..454952b 100644
--- a/vm-deploy.yaml
+++ b/vm-deploy.yaml
@@ -17,7 +17,7 @@ spec:
     memorySlotSize: 1Gi
     memorySlots: { min: 1, use: 1, max: 5 }
     rootDisk:
-      image: pg14-disk-test:dev
+      image: vm-postgres:15-bullseye
       size: 8Gi
     ports:
       - port: 22   # ssh

In the vm-informant's logs, got the "postgres file cache" bit as expected
I0515 17:56:59.783543     183 main.go:108] Selected postgres file cache, connstr = "dbname=neondb user=cloud_admin sslmode=disable" and config = {InMemory:true ResourceMultiplier:0.75 MinRemainingAfterCache:671088640 SpreadFactor:0.1}

Note: "dbname=neondb" here needs fixing. Will change that to "dbname=postgres" (ref https://github.com/neondatabase/neon/pull/4046) and then merge.


Fixes issue #8

https://github.com/saulmm/Material-Movies/issues/8

Just out of curiosity, am I the only one using a recent version of Android Studio or just the only one running into that issue? :-)


Check if user already claimed free trial

📝 Changed routes:

…board/settings/billing
/pricing

(view full size)
(view full size)

Commit 39a68eab4f8cb0ef6765f82724a33e106805d502 (https://thirdweb-re9mos65g.thirdweb-preview.com).


TcpSocketClient-UnhandledException when I try read a response that not arrived yet

Hi, I'm using this library to communicate with a TCP Server, that sends me when a event was generated, then, I have to verify all the time if the TCP Server sent to me a event, but if I try read anything before the TCP Server sends me, it's thrown the UnhandledException, but it only happens if I read inside a Task, in the main thread it thrown a timeout exception, the exception that I expected to happen in Task. Someone can help me? Thanks. below is my code.
"04-11 13:32:24.490 E/mono    ( 4201): Unhandled Exception:
04-11 13:32:24.490 E/mono    ( 4201): System.NullReferenceException: Object reference not set to an instance of an object."
I put a try/catch block to handle the exception, but it didn't work, someone can help me? Thanks.
`public class CentralTcpService
{
public async void ConnectTcpAsync()
{
try
{
_sockecClient = new TcpSocketClient();
await _sockecClient.ConnectAsync(Central.Ip, Central.Port);
_writter = new ExtendedBinaryWriter(_sockecClient.WriteStream);
_reader = new ExtendedBinaryReader(_sockecClient.ReadStream);
_writter.WriteString(EvenNotProtocol.MobileReceiverCommand);
_sockecClient.ReadStream.ReadTimeout = int.MaxValue;
            EnableTcpService();
        }
        catch (Exception e)
        {
            throw new Exception(e.Message);
        }
    }

    private void EnableTcpService()
    {
        _cancelationTcpService = new CancellationTokenSource();

         new Task(StartService, _cancelationTcpService.Token, TaskCreationOptions.LongRunning).Start();

    }

    private void StartService()
    {
        while (!_cancelationTcpService.Token.IsCancellationRequested)
        {
            var ev = EvenNotProtocol.DeserializeEvent(_reader);

            if (ev == null) continue;

            _writter.WriteString(EvenNotProtocol.MobileOkCommand);

            EventReceived?.Invoke(this, new CentralTcpEventArgs(ev));

        }
    }
}

 public class EvenNotProtocol
 {

    public static Event DeserializeEvent(ExtendedBinaryReader reader)
    {
        try
        {
            reader.SkipBytes(1);
            .....
       }
       catch (IOException e)
       {
            return null;
       }
    }
 }`

I was testing more, and I realized that this only happens if I read inside a Task.

This is a late response but I suppose may be caused by the async void method, you can read here for an idea of why you should remove that https://haacked.com/archive/2014/11/11/async-void-methods/


Using Admission Controllers: too old content (for v1.9 or earlier) could be removed

The paragraph below contains too old content.
"For Kubernetes version 1.10 and later, " and contents after "Notes" could be removed.
The shorter, the easier to understand.
https://kubernetes.io/docs/reference/access-authn-authz/admission-controllers/#is-there-a-recommended-set-of-admission-controllers-to-use

/language en

/language en

/triage accepted
/good-first-issue

/triage accepted
/good-first-issue

/assign

/assign

/close
Address in PR #25966

/close
Address in PR #25966


[RESOLVED] Interface eth0(): High error rate (>2 for 5m)

Problem started at 09:06:29 on 2023.07.31
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Operational data: errors in: 4, errors out: 0
Original problem ID: 34456
Event details in Zabbix: http://<IP_ADDRESS>/tr_events.php?triggerid=23483&eventid=34456

Problem has been resolved in 15m 0s at 09:21:29 on 2023.07.31
Problem name: Interface eth0(): High error rate (>2 for 5m)
Host: S100-Primario
Severity: Warning
Original problem ID: 34456


vim like gg and G keybindings

I recently discover this repo and I've been liking it a lot so far, but the lack of vim-like gg and G keybindings bothered me. I decided to see how I could add those to the repo and these seem to work fairly well. My keyboard doesn't actually have an End or a Home key, so these are useful to me.
Testing Done
make build
I tried a few interesting combinations outside of the normal gg and G and no awkward behavior stood out to me. However, this does cause jam to crash when I use it on a playlist of 500+ songs. However, after using using xmodmap to simulate an End key input, that caused jam to fail as well, so my change hasn't introduced that bug.
A better solution to this would be to allow for more customizable keybindings, which I am considering doing.

why overcomplicate things? g is bound to no action at the moment, you can bind it to home

How do you mean bind g to home, exactly? Do you mean to stop tracking gg and just have g map to scrollUp()? I only really chose gg because that's how it is in Vim, but making it just g is reasonable.

yeah, just do this
			case 'G':
 				app.scrollDown()
 			case 'g':
 				app.scrollUp()`

Ah yes, of course, that simplifies things.
I've added the new commit, still builds, still works.

Thanks:)


Fix elevation min for watershed characteristics

We can deal with incorrect elevations immediately after wshds object  is called in the tables.R script. Otherwise it needs to be done in multiple places. When we have so few sites we can look at google earth and add the actual Elev Min by clicking on the mouth of the stream on google earth  to get the elev and fixing it
(ex. https://github.com/NewGraphEnvironment/fish_passage_bulkley_2022_reporting/blob/0e016dc5e4a8c705dc033bab3325bedb33553d62/scripts/tables.R#L67 )

aha - remnant with all chunks currently turned off.  ok. to do

maybe we just leave it out


demangle not working on my symbols

Maybe I'm doing something wrong, but here's an example of a symbol I can't seem to demangle:
__ZN3pco25latent_batch_decompressor32LatentBatchDecompressor$LT$U$GT$18decompress_offsets17h254da28dd89d69cbE
I just get this back:
__ZN3pco25latent_batch_decompressor32LatentBatchDecompressordecompress_offsets17h254da28dd89d69cbE
I know this function was compiled with a const generic, and I'd like to know what the value of that generic was. I produced this symbol by running cargo build --release -- --emit=asm and reading the .s file.
target: darwin aarch64
version: 0.1.23

The const generic value is not recoverable from the symbol in the default mangling scheme. You'd need to build with RUSTFLAGS='-C symbol-mangling-version=v0' to get more information in the symbols.

That's good to know, but shouldn't the rest of the symbol demangle? How come it still starts with __Z...?

On my machine, that works as I would expect.
fn main() {
    let mangled = "__ZN3pco25latent_batch_decompressor32LatentBatchDecompressor$LT$U$GT$18decompress_offsets17h254da28dd89d69cbE";
    let expected = "pco::latent_batch_decompressor::LatentBatchDecompressor<U>::decompress_offsets::h254da28dd89d69cb";
    assert_eq!(rustc_demangle::demangle(mangled).to_string(), expected);
}


Feat: I want to change in romentic gateway page

Describe the feature
In the romentic gateway page there is only map picture, i want to add map feature in place of picture.
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Please assign this issue to me


Support single file MRFs, with compact index

Copying MRFs is tricky, especially the ones with very large bounding boxes.
The canned index format helps, but it has to be uncanned before use.
It should be possible to make the canned index an alternative to the array version, which would make the MRF easier to transfer.
A side-effect will be that the resulting MRF will be read-only.  Another side-effect is that cloning of such a file gets harder.
A related feature would be to combine all three components of an MRF into a single one, also enhancing transferabillity.

Maybe storing the MRF as is, inside of a tar file is the solution.  It doesn't invent a new format, and it could be made to work transparently in GDAL, at least for reading. Writing would be only a bit trickier, it would require first to write the MRF as normal, then do a gdal_translate mrf to mrf with some special options. It could be done in a virtual single pass, using temporary files.

Implemented as mrf-in-tar


bare soil site

Purpose
Add a test with data for a bare soil fluxnet site.
To-do
[]clean up sim scripts
[] verify plots
Content
Add experiment to buildkite
Review checklist
I have:

followed the codebase contribution guide: https://clima.github.io/ClimateMachine.jl/latest/Contributing/
followed the style guide: https://clima.github.io/ClimateMachine.jl/latest/DevDocs/CodeStyle/
followed the documentation policy: https://github.com/CliMA/policies/wiki/Documentation-Policy
checked that this PR does not duplicate an open PR.

In the Content, I have included

relevant unit tests, and integration tests,
appropriate docstrings on all functions, structs, and modules, and included relevant documentation.

[ ] I have read and checked the items on the review checklist.

Closing, because we are now using this to test the snow/soil model, branch kd/snow_soil


Support for rebalancing?

Does this gem support the failover options from the broker like updateClusterClients, updateClusterClients, and updateClusterClients?  We're using version 1.3.2 with mCollective and are noticing that the clients never rebalance.

Short answer: no.
Those look like broker specific options.  The gem attempts in all most
all cases to be broker agnostic.
What broker are you using?
Please define "rebalance".
On 07/24/2015 12:19 PM, Jason Hane wrote:

Does this gem support the failover options from the broker like
updateClusterClients, updateClusterClients, and updateClusterClients?
We're using version 1.3.2 with mCollective and are noticing that the
clients never rebalance.
—
Reply to this email directly or view it on GitHub
https://github.com/stompgem/stomp/issues/112.

I was looking to be able to use the "broker side options for failover" in ActiveMQ as seen on http://activemq.apache.org/failover-transport-reference.html.  This gem is used in mCollective and as far as I can tell is the only thing responsible the connections to ActiveMQ.  We have a few thousand nodes and was looking to better balance them out across the brokers.

When a hashed login us used, with reliable => true, the gem provides a failover logic and semantics.
Ar you aware of that ?  That functionality is not broker specific, but is very close to what AMQ provides.
See the README.

It looks like the mCollective activemq.rb uses a reliable connection.  I was more looking to ensure that 90% of clients don't get loaded onto the same broker and instead get fanned out somewhat evenly across the pool.  I understand you can't put broker specific features into this package.  This belongs on the mCollective side.  Thanks!

Apologies for the late questions, but I got curious.
Are you using the mcollective-client gem ?
If so, is that what triggered posting of this issue?
Regards, Guy
On 04/20/2016 05:00 PM, Jason Hane wrote:

It looks like the mCollective activemq.rb uses a reliable connection.
I was more looking to ensure that 90% of clients don't get loaded onto
the same broker and instead get fanned out somewhat evenly across the
pool. I understand you can't put broker specific features into this
package. This belongs on the mCollective side. Thanks!
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/stompgem/stomp/issues/112#issuecomment-212604378

Yes we are.  It doesn't have support for rebalancing but it wouldn't be hard to add it in.

I guessed that you were.
I installed version 2.8.4 of that gem so I could look at the source code
a bit.
It seems to that the MCollective::Connector::Rabbitmq#connect method
attempts to provide/wrap all of the fail-over options that the stomp gem
provides.
It is not clear to me that the mentioned method actually does provide
all that is currently supported by the stomp gem.
I would think that the maintainers of the mcollective-client gem need to
take a look at that.
I'll also take this opportunity to say the maintainers need to think
about support of all STOMP Protocol levels.  It appears to me that the
mcollective client gem supports only protocol levels 1.0 and 1.1.  The
1.2 protocol was published a few years back, and the stomp gem fully
supports it.
Best of luck in your efforts.
Regards, Guy

The mcollective-client gem is pretty lacking. I'm going to see if I can enhance the ActiveMQ portion a bit and get it merged back in.  It should also be more customizable than what it is.

On Apr 20, 2016, at 10:19 PM, Guy M. Allard<EMAIL_ADDRESS>wrote:
I guessed that you were.
I installed version 2.8.4 of that gem so I could look at the source code
a bit.
It seems to that the MCollective::Connector::Rabbitmq#connect method
attempts to provide/wrap all of the fail-over options that the stomp gem
provides.
It is not clear to me that the mentioned method actually does provide
all that is currently supported by the stomp gem.
I would think that the maintainers of the mcollective-client gem need to
take a look at that.
I'll also take this opportunity to say the maintainers need to think
about support of all STOMP Protocol levels. It appears to me that the
mcollective client gem supports only protocol levels 1.0 and 1.1. The
1.2 protocol was published a few years back, and the stomp gem fully
supports it.
Best of luck in your efforts.
Regards, Guy
―
You are receiving this because you modified the open/close state.
Reply to this email directly or view it on GitHub


Cannot lazy load providers specified in configuration file correctly

Hi All
I have raised this discussion as a bug:
https://github.com/openssl/openssl/discussions/23731
because it seems that expectation does not match behavior correctly. Here is the problem.
I'm trying to define an entry inside openssl.cnf and lazy load it later. So I wrote a config file like this:
...
[openssl_init]
providers = provider_sect

# List of providers to load
[provider_sect]
# default = default_sect
# The fips section name should match the section name inside the
# included fipsmodule.cnf.
base = base_sect
fips = fips_sect
myprovider= myprovider_sect

[myprovider_sect]
module = /data/myprovider.so
additional_info = test
...

As you see I have added entry without activate=1 to my config file. I'm also only using fips and base provider and disabled default provider. Now, I was expecting that if I try to load config file and then use OSSL_PROVIDER_load(), I should be able to load my provider. So I wrote a code like this:
int func(OSSL_PROVIDER *provider, void *cbdata) {
        std::cout << "provider: " << OSSL_PROVIDER_get0_name(provider) << "\n";
        return 1;
}

int main(int argc, char** argv) {
    if (OSSL_LIB_CTX_load_config(NULL, "openssl.cnf") <= 0) {
        std::cout<< "FATAL: error loading configuration file\n";
        ERR_print_errors_fp(stderr);
        exit(1);
    }

    int ret = -1;
    OSSL_PROVIDER *ctx;
    ctx= OSSL_PROVIDER_load(NULL, "myprovider");
    if (ctx== NULL) {
        std::cout << "Failed to load Default provider\n";
        ERR_print_errors_fp(stderr);
        return -1;
    }
    std::cout << "load done\n";
    OSSL_PROVIDER_do_all(NULL, func, NULL);
    OSSL_PROVIDER_unload(ctx);
}

But this code does not work as expected. I traced openssl codes to some extend and I noticed that an entry for non-activated provider is added to internal structures, but it seems it is not searched and activated by calling OSSL_PROVIDER_load().
One major problem is the fact that module path will not be set if we try to load module in this way. template.path should have module path here and it is need to be set after this line:
https://github.com/openssl/openssl/blob/5677992679b38950c6a0c3775fd57378e1879ba5/crypto/provider_core.c#L575
similar to what happens here:
https://github.com/openssl/openssl/blob/5677992679b38950c6a0c3775fd57378e1879ba5/crypto/provider_conf.c#L237-L238
but module path is not set. I try to add this myself and test things out, but module still does not load correctly.
I have yet to test if I'm missing something or not, but I always to load provider like this.
I'm using version 3.0.13 right now, but this code is similar in all version. And as you see in my config file, I'm using FIPS module and have disabled default provider.

FWIW, The activate setting has changed somewhat between 3.0 and the head of the tree (and in 3.3).  In 3.0 the activate setting was an implied boolean whos presence meant activate if it was present (i.e. you could set activate=no and that would still activate the provider).  In 3.3 it was updated such that activate was a positively asserted boolean (i.e. activate=[1|yes|true] means activate, 0|no|false means don't activate.  Omitting the parameter is an error.  you might need to check that.
But I don't think thats whats going on here.  I think whats happening is that we're expressly forgetting to set the path when creating a provider.  When we call provider_conf_load, if its not going to be activated, we create a template in which we do wet the path in the OSSL_PROVIDER_INFO struct, but unlike the activate path we don't call ossl_provider_set_module_path (which makes sense, as we don't have an OSSL_PROVIDER struct yet).  However, in the provider_new call which we make during a manual call to OSSL_PROVIDER_load, we get the template, but we never set the allocated provider path with a call to ossl_provider_set_module_path.  I think we probably need to.  Can you augment thee ossl_provider_new code to add a call to that function prior to the call to provider_new call there passing the value of template.path as the argument?

Can you attempt to run your reproducer with the referenced PR and see if the problem is fixed please?

@nhorman
Hi
I have tested this PR and it works well. It loads provider as expected.
Will this PR be merged into 3.0 branch as well?

Thank you, I've marked it for inclusion in all the 3.x branches.  It will take.a.bit though as we're about to freeze for the final 3.3 release

Omitting the parameter is an error. you might need to check that.

@nhorman I would strongly disagree with that. Omitting the parameter completely must be supported for backwards compatibility and the default value must be not to activate.

Yeah, you're right, omitting the parameter still defaults to don't activate, which is correct.  It's adding the parameter key without a value that generates.ab error

Still present on 3.0 and 3.1

backport to 3.0:
https://github.com/openssl/openssl/pull/24197


Revert "Code Quality: Improved app startup routine 2"

Reverts files-community/Files#12951

Hopefully we can add it back soon


Wavefront prevents main thread from exiting

With wavefront configured, open a django shell:
python manage.py shell then Exit the shell with exit()
start the django development server like  python manage.py runserver, then type ctrl-c to stop the server.
In both of these cases the process hangs indefinitely, and does not exit.
The autoreload on file changes for the development server also does not work with wavefront configured.

This appears to be caused by the use of threading.Time() in both the HeartbeaterService and the WavefrontDirectReporter. In the case of the HeartbeaterService the interval is 5 minutes, which will cause the main thread to block for that long if it tries to exit without closing the heartbeater first.

This issue is going to prevent us from moving this into production. I have observed this currently with both runserver and shell, but it appears it will impact server processes as well, which are expected to exit or restart based on signals.

It looks like this could be addressed by setting _timer.daemon = True everywhere a timer is used.
This does have the implication of losing pending messages before they are sent if the client is not properly closed. Personally I would consider that a seperate issue, and it could either be left to the application developer to implement handlers to properly close connections, or the SDK could listen for SIGINT and cleanly close the clients/reporters.

Is this now fixed with https://github.com/wavefrontHQ/wavefront-sdk-python/pull/48 ?


New P97: Embeddable in the real line

Add new property P97: Embeddable in $\mathbb R$
New theorems to accompany this:

(T231) embeddable in R ==> embeddable in Euclidean space
(T232) totally path disconnected + embeddable in R ==> zero dimensional
(T233) connected + embeddable in R ==> locally path connected
(updated T462) separable + metrizable + zero dimensional ==> embeddable in R
(updated T463) LOTS + second countable ==> embeddable in R

These theorems allow to determine whether P97 holds or not for many spaces.  For all the remaining spaces known as "embeddable in Euclidean space" with P97 undetermined, added some explicit trait files as needed.
And more updates for S121 (Bernstein's connected set), S147 (Luzin set), S148 (Luzin set).

Taking a look here and I have a quick question. This PR asserts P65 for S121, which is automatically deduced currently. I would assume that the change in asserted properties for S121 in this PR makes the automatic deduction of P65 impossible. Without taking an in depth look at the deduction tree (https://topology.pi-base.org/spaces/S000121/properties/P000065), is there another way to check why P65 isn't deduced for S121 with the content of this PR?

Maybe this was mentioned in our last community call, but I've gotten a couple of 404s using "open link in new tab" for theorems and asserted properties in this PR while browsing. When I don't use the "open link in new tab" and just click directly, they seem to work fine and I can see no difference in the displayed URLs.

So the 404 is triggering based upon the pages that exist in the main branch, when visited directly. As pointed out this is only when a page is loaded from scratch - internal routing works fine.
This is a wontfix for now as it only affects reviewers of non-main branches, as annoying as it is.

I've checked over everything except for T463 in detail since it references a new mathse post which is involved. If no one else beats me to it, I'll think it about in more detail a bit later.
In the meantime, I believe what's written for T233, but would anyone think it beneficial to throw in some basic reference?

Taking a look here and I have a quick question. This PR asserts P65 for S121, which is automatically deduced currently. I would assume that the change in asserted properties for S121 in this PR makes the automatic deduction of P65 impossible. Without taking an in depth look at the deduction tree (https://topology.pi-base.org/spaces/S000121/properties/P000065), is there another way to check why P65 isn't deduced for S121 with the content of this PR?

The previous justification for S121/P65 (https://topology.pi-base.org/spaces/S000121/properties/P000065) seemed extremely long, and depended on the asserted P129 (indiscrete) = false.  It seems simpler to assert P65 directly, as it's pretty immediate from the construction of the space, and make P129 deduced instead.
(Many spaces assert P129 directly, and don't need to.  I think it's a holdover of some old PR where the property was asserted for nearly all spaces.)

temporarily converted to Draft while I add a reference

I believe what's written for T233, but would anyone think it beneficial to throw in some basic reference?

Not sure what to add, but feel free to modify T233 as you see fit.

Another general question (not specific to this PR, but affects it also).
In the browser the reference names are not expanded for latex/mathjax.  See for example "mathbb R" in https://topology.pi-base.org/spaces/S000140/references.
Do you think it could be expanded at some point in the future?

Another general question (not specific to this PR, but affects it also). In the browser the reference names are not expanded for latex/mathjax. See for example "mathbb R" in https://topology.pi-base.org/spaces/S000140/references.
Do you think it could be expanded at some point in the future?

The issue is that when you write {{mr:123456}}, the component that renders it to a link is unaware of any reference data provided elsewhere in that text file or otherwise.
I'd prefer some kind of solution that allows us to only provide ids, and then some external API provides the title, e.g. https://api.zbmath.org/v1/

The issue is that when you write {{mr:123456}}, the component that renders it to a link is unaware of any reference data provided elsewhere in that text file or otherwise.

I was not talking about the expansion of something like {{mr:123456}}, but instead about this list of references in a "References" page.  The contents of that page is constructed from the name: fields from the metadata.

The issue is that when you write {{mr:123456}}, the component that renders it to a link is unaware of any reference data provided elsewhere in that text file or otherwise.

I was not talking about the expansion of something like {{mr:123456}}, but instead about the list of references in a "References" page. The contents of that list is constructed from the name: fields in the refs: section from the metadata.

Oh gotcha. Open an issue in /web and assign me and I can maybe take a crack at this.

Approved - make any discussed tweaks then merge when you're ready.

@StevenClontz Why did you approve?  I was still going to add the few things you suggested.

Hmm, thanks for approving.  But I think it would have been better to let Chris do it, as he was planning to do it.  Also, when there is still work going on, seems better for that to be complete.

Assigning to @ccaruvana

Haha I didn't mean to claim ownership over approving, but thanks for keeping me in on the loop. Based on the conversation, this PR seems ready to go and the GO space will be added later (go GO).

As for a converse of LOTS + second countable ==> embeddable in $\mathbb{R}$, we need a space embeddable in $\mathbb{R}$ that is not a LOTS.
I propose the space $X$ that is the disjoint union of $\mathbb{R}$ and an extra point $\infty$. It is clearly embeddable in $\mathbb{R}$ as $(0,1)\cup\{2\}$. To show that it is not a LOTS, note that in the opposite situation $\infty$ must be either the largest or the smallest element of $X$, otherwise $(\left,\infty)$ and $(\infty,\right)$ is an open partition of $X\setminus]{\infty\}$ which is connected, impossible.
Suppose WLOG that $\infty$ is the largest element, then ${\infty}$ is open implies that $\mathbb{R}$ contains a largest element ${a}$. But then $\mathbb{R}\setminus\{a\}$ is still connected in the new order topology (removing the largest element of a connected LOTS leaves a connected space, since for LOTS connectedness <=> dense order + every $[a,b]$ is compact; also we can see that the least-upper-bound property is preserved because a set with LUB $\{a\}$ is now unbounded in $\mathbb{R}\setminus\{a\}$), and removing any point from $\mathbb{R}$ results in a disconnected space in the usual topology.

@Jianing-Song Good example to have, with great justification here.
One minor thing.  It's true that for a connected LOTS with a maximum element, removing that maximum still gives a connected space.  But connected LOTS is not exactly that same as order-dense + order-complete.  Order-complete means every subset has a supremum.  But we need instead: every subset with an upper bound has a least upper bound.  It's what the wikipedia article calls "bounded complete" (not sure how common that terminology is though).

@Jianing-Song Good example to have, with great justification here.
One minor thing. It's true that for a connected LOTS with a maximum element, removing that maximum still gives a connected space. But connected LOTS is not exactly that same as order-dense + order-complete. Order-complete means every subset has a supremum. But we need instead: every subset with an upper bound has a least upper bound. It's what the wikipedia article calls "bounded complete" (not sure how common that terminology is though).

OK, but then being order-complete is just the same thing as being compact. Strange enough!

Yes, order-complete is the same as being compact.

I missed one detail.  The "bounded complete" property, more commonly called "least upper bound property" it seems, should be:
Every nonempty subset with an upper bound has a least upper bound.
(Seems wikipedia is missing this nonempty qualifications in a few places)


Add create many

Adds a create many mutation type, and associated tests.
Closes #106

Needs rebase

The requested changes should be good to go, and it's rebased onto your main branch.

Excellent, thanks!


Add a Gitter chat badge to README.md

jmquigs/greycrypt now has a Chat Room on Gitter
@jmquigs has just created a chat room. You can visit it here: https://gitter.im/jmquigs/greycrypt.
This pull-request adds this badge to your README.md:

If my aim is a little off, please let me know.
Happy chatting.
PS: Click here if you would prefer not to receive automatic pull-requests from Gitter in future.

I beat you to it, bot.


Record PipelineRun and TaskRun results

Feature request
PipelineRuns and TaskRuns can emit results. For example, the git-clone Task produces the commit result with "the precise commit SHA that was fetched". It would be great to store this information in the corresponding records.
Use case
I have a task that takes as a parameter an image reference, provides various assessments on it, then creates a summary report. This report is made available outside the Task via a Task result. I want to use Tekton Results to persist these reports, so I can have a historical view of this data.

@dibyom @wlynch looks like this issue can be closed as fixed?

/close


Move availability badge for horizontal cell layout

Motivation and Context
When media list is displayed verticality, the cell layout is horizontal, with a small image height than in grid or swimlane.
UX tests reported some readying difficulty with availability badge is display above the image in this case.
Availability badge should me on right side, with description texts.
Description
Move availability badge for horizontal cell layout from image to right description texts.
Availability badge and livestream badges.
As VisualMediaView is used also for download cell, update both.
Checklist

[x] The branch has been rebased onto the develop branch.
The code followed the code style:

[x] swiftlint has run to ensure the Swift code style is valid.
[x] rubocop -a has run to ensure the Ruby code style is valid.

[x] Remote configuration properties have been properly documented (if relevant).
[x] The documentation has been updated (if relevant).
[x] Issues are linked to the PR, if any.

SwiftUI previews are also added.


Bot commented saying PR was closed unmerged when it wasn't

Hi - thank you for a great tool!
The renovate bot just commented on a PR with the "As this PR has been closed unmerged, Renovate will ignore this upgrade ..." message:
https://github.com/mozilla-neutrino/neutrino-dev/pull/401#issuecomment-345926689
...however the PR had in fact been merged after all (from the commit message I'm guessing the GitHub "squash and merge" feature was used).
Is this expected?
Many thanks :-)

Thanks for the report. I've figured out what happened. Renovate had the PR opened updating 24 package files. Around the time it was merged, https://github.com/mozilla-neutrino/neutrino-dev/commit/39599a410d250148172f82047e7b1929a1c6ed21 was also merged, which added in another 1.x deepmerge which then was missed out. Race condition etc etc.
Renovate tries to be smart and not recreate any of its PRs where you already had the same branch name/title before and closed it. Eg if you had closed the PR instead of merging it as you wanted to stick to 1.x.
Renovate needs to be a little smarter and not block "identical" PRs if the first one was merged and not closed. I will fix this soon, but in the meantime you can unblock the new PR by renaming the existing PR in any way at all (eg add a ! to the end).

Ah makes sense - thank you for taking a look. I can see this being a problem space where there is a significant amount of complexity around the edges! :-)


Drivers: Add Bosch bmp180 pressure sensor [v2]

Version 2 Pull request for Bosch bmp180 pressure sensor.

merge multiple commits
fixed code style if() {}
fixed camel case
use k_sleep() not k_wait_busy()
i2c.dtsi tests/../sensors/ add the device tree information on the tail with increment number
add comment to make clear why use the custom byte swap for int16_t in bmp180.h

Thank you for your review.

There is already #73218 that is about ready to get in. I would suggest you check it out and maybe provide feedback there if you feel there are things that could be improved . Thanks!

BMP180 is the newer version of BMP085 and they use the same registers.
Unfortunately, it got blocked and noone replied although all the issues were addressed.
https://github.com/zephyrproject-rtos/zephyr/pull/67612

I apply the changes , rebase and force update the branch.

Follow the advice to reopen this branch, rebase the fixups.

@faxe1008 I'm very sorry - but I synced the branch here i the web interface cause of unresolved issue in the i2c.dtsi, now I rebased and push forced to where I started. But the workflow test will still fail for the one bad 0x8e not my commit. Lets see how I can fix this up later.

@faxe1008 I stuck with the build process because
tests/drivers/build_all/sensor/i2c.dtsi has conflict with this branch.
I can rebase and delete the commit for i2c.dtsi only for now.

A rebase with conflict resolution should just do the trick for you.
Also there are issue marked by checkpatch, those need to be fixed in the respective commit that introduced them.
You can also run the checkpatch locally btw. git diff HEAD^^ | ./scripts/checkpatch.pl - (assuming you are inside of ZEPHYR_BASE dir)

@faxe1008

A rebase with conflict resolution should just do the trick for you. Also there are issues marked by checkpatch, those need to be fixed in the respective commit that introduced them.
You can also run the checkpatch locally btw. git diff HEAD^^ | ./scripts/checkpatch.pl - (assuming you are inside of ZEPHYR_BASE dir)

I checked the problematic i2c.dtsi in test with git blame
26be1da3e7e9 tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez          2024-04-24 16:53:06 +0200 1070)
26be1da3e7e9 tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez          2024-04-24 16:53:06 +0200 1071) test_i2c_lsm9ds1: lsm9ds1@91 {
26be1da3e7e9 tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez          2024-04-24 16:53:06 +0200 1072)   compatible = "st,lsm9ds1";
26be1da3e7e9 tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez          2024-04-24 16:53:06 +0200 1073)   reg = <0x8e>;
26be1da3e7e9 tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez          2024-04-24 16:53:06 +0200 1074) };
0x8e of this commit should be 0x91.

Regarding the TEMPERATURE or DIE_TEMP CHANNEL. The Datasheet said bmp180 is a pressure sensor. Not a Temperature sensor. It needs the temperature of the IC to compensate. Have this in mind, I will apply changes to the code and have DIE_TEMP only.

@faxe1008

A rebase with conflict resolution should just do the trick for you. Also there are issues marked by checkpatch, those need to be fixed in the respective commit that introduced them.
You can also run the checkpatch locally btw. git diff HEAD^^ | ./scripts/checkpatch.pl - (assuming you are inside of ZEPHYR_BASE dir)

I checked the problematic i2c.dtsi in test with git blame 26be1da tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez 2024-04-24 16:53:06 +0200 1070) 26be1da tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez 2024-04-24 16:53:06 +0200 1071) test_i2c_lsm9ds1: lsm9ds1@91 { 26be1da tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez 2024-04-24 16:53:06 +0200 1072) compatible = "st,lsm9ds1"; 26be1da tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez 2024-04-24 16:53:06 +0200 1073) reg = <0x8e>; 26be1da tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez 2024-04-24 16:53:06 +0200 1074) };
0x8e of this commit should be 0x91.

I checked the main branch, it had been fixed 14h ago.

@faxe1008

A rebase with conflict resolution should just do the trick for you. Also there are issues marked by checkpatch, those need to be fixed in the respective commit that introduced them.
You can also run the checkpatch locally btw. git diff HEAD^^ | ./scripts/checkpatch.pl - (assuming you are inside of ZEPHYR_BASE dir)

I checked the problematic i2c.dtsi in test with git blame 26be1da tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez 2024-04-24 16:53:06 +0200 1070) 26be1da tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez 2024-04-24 16:53:06 +0200 1071) test_i2c_lsm9ds1: lsm9ds1@91 { 26be1da tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez 2024-04-24 16:53:06 +0200 1072) compatible = "st,lsm9ds1"; 26be1da tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez 2024-04-24 16:53:06 +0200 1073) reg = <0x8e>; 26be1da tests/drivers/build_all/sensor/i2c.dtsi (Miguel Gazquez 2024-04-24 16:53:06 +0200 1074) };
0x8e of this commit should be 0x91.

I checked the main branch, it had been fixed 14h ago. And introduced a new problem with a double "92" numbering in i2c.dtsi

@faxe1008 I need a little advice on this,
if I in my branch and not yet apply changes to i2c.dtsi, can I do a
git checkout --patch main -- tests/drivers/build_all/sensors/i2c.dtsi
then apply my changes make a rebase and push it in?
Not sure if it permit to merge into my pull-request.

Unless I misunderstand what you are trying to do:

You need to update your forks main branch to the zephyr current main. Either through cli or web UI.
pull your fork to get the newest main
rebase your feature onto the main branch
force push your changes

Unless I misunderstand what you are trying to do:

You need to update your forks main branch to the zephyr current main. Either through cli or web UI.
pull your fork to get the newest main
rebase your feature onto the main branch
force push your changes

I tested it first with
git checkout main
git pull
git checkout bmpv2 - b test_merge
git merge main
git rebase -i
looks ok to me.
c5b5daf4081 (HEAD -> test_merge) Drivers: Bosch bmp180 dts bindings
39193b866e0 Drivers: Add support for Bosch bmp180 sensor
143b14bb4fb (origin/main, origin/HEAD, main) shell: modules: kernel: print cpu_mask when available
2e95ac8fbe3 boards: dts: esp_rust: enable bluetooth peripheral
179c85aa06d tests: net: socket: udp: clear control data buffer before recvmsg

just a note about the i2c.dtsi
there is a @92 twice, that needs to resolved which will move 2 other test cases upfront mine to @93 and @94
that is why I added my with @95 to be on the right numbering when it is cleaned up.

I don't know why with 0707f96 the i2c.dtsi commit text got lost. But I used the chance to fix some of the clang "warnings" and pushed it again. Sorry for the noise.

Received a bmp390l today and run side to side test, realized that the bmp180 has the pressure in Pa, and the kPa conversion was wrong. Fixed it.

Tested the bmp180 against the new arrived bmp390 and the accuracy wasn't great. Find the problem in an
int32_t overrun in my optimized conversion formula. Fixed it and push the fix.

@faxe1008 thank you for your reviews! It was very helpful. Have send an other pull request for merge bmp390 into bmp388 driver. You might have a look if you have time. #77724


[Mono] Stacktraces of marshalling errors could be better

Godot version: 463123a
Debugging marshalling issues can be difficult because the resulting stacktraces do not really display any useful information.

As it's often calls from the message queue, we don't have much information to hand out to the end user but context about what the call is, where it emanates from or more readable type names would already be a huge step forward.
cc @neikeq as we discussed this a bit earlier.

Same thing happens when an error occurs while creating a scene (either through GetTree().ChangeScene() or by .Instance()ing a packed scene). No stack trace and no feedback at all. Makes it really hard to track down the issue, especially if the project is getting larger (in our case, around 100 different _Ready() functions).

What's the status on this issue in 3.4.2 / 3.5-beta1 or later?

3.5-beta1: the stacktrace is better now. We can see the original point of the error at the bottom. Looks good to me.

Thanks, closing.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-archive-test-target/pull/50 is merged into live branch.
Auto archive content to https://github.com/OPS-E2E-PPE/docs-archive-test-target.git

Docs Build status updates of commit 85bd2ed:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

:x:Error

Details

[Error]

Cannot sync git repo to specified commit because branch Archive_master_2019-09-25-10-35-39 has been deleted or has been force pushed: fatal: Couldn't find remote ref Archive_master_2019-09-25-10-35-39

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.


pinning AMQP to version without event emitter leak

copy of #155 for the 1.2 release branch

@johren @rolandpoulter @brianparry @hohene @RackHD/corecommitters

Jenkins build will likely fail due to new tests just added that required a minor Jenkins change.
test this please

*** BUILD #626 ***

*** BUILD #628 ***

+1


Simplify table fallback constructor logic

While I agree in principle, I think this is a pretty poor example; checking isfile seems like pretty obvious argument validation before ever calling table

checking isfile seems like pretty obvious argument validation before ever calling table

Not in a lazy loading scenario that the queryverse file IO packages implement: you can check whether a file exists during the load call, but whether that is the case or not is quite irrelevant. The actual file opening and loading only happens once the data is requested, and that is triggered from inside the table call, so that is when the error will be raised.

Should we just remove the try ... catch block? If iter is a complex iterator with some error inside, it will just error the first time it is collected with an unhelpful "can't convert input to a table".

Yes, I think that would probably resolve this problem.

PR to remove try-catch #253


Favicon on FifthTry

Require to put favicon on FifthTry

This is implemented: https://fpm.dev/favicon/.


mirroring

no mirroring allowed?
also get issues a lot of the times needs to be updated to run on swift 2.3 or swift 3

can i get this to allow mirroring for viewing other devices this would help me a lot


Added shortest path calculator

Fixes Issue🛠
closes #671
Description👨💻
Added a nice graph generator with options to add nodes and edges with weights and then we can calculate the shortest path when we we select source and destination nodes of the graph
Type of change📄

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)

How this has been tested✅
I tested some tricky configurations (one of them are displayed in the video) and confirmed that its working
Checklist✅

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added demonstration in the form of GIF/video file
[x] I am an Open Source Contributor

Screenshots/GIF📷
https://github.com/Rakesh9100/CalcDiverse/assets/112798996/20a2964a-fd7d-4f7e-81b5-a76a1f580e23

Add a Readme file for your calculator in your folder!
Also, center the body content and enhance the UI @nagamukesh


Adsk Contrib - Change the version of the master branch

Signed-off-by: Patrick Hodoul<EMAIL_ADDRESS>As agreed at the TSC meeting, here is the change for the version of the master branch i.e. to highlight that it prepares the next release.

Friendly reminder that the pull request can now be merged.


use std.mem.copyForward

Refactoring repeat to use std.mem.copyForward().

Nice work! Thank you for the contribution!


Use subheaders for events on example pages

Suggested by @ben-norton. List table of contents on example pages as:

Deployment

Location
...

Events

Event 8f5ffbf2
Event ...

Fixed in #334.


Img tag to be replaced by image tag

 tag is used instead of  tag.
Replace it for better performance.

completed!!!


Unable do override CSS

Still about #21 .
Im trying the workaround solution by overriding the CSS, but been unable to successfully override it.
Could you be more clear about the overriding process, maybe by showing a step-by-step?

Hi @NewtonJoaquim! It's already fixed with the PR #31 It's still yet to be uploaded to NPM. I'll try to bump the version tomorrow :smile: Sorry for the inconvenience!


chore(docs): don't use bower for docs dependencies

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
chore
What is the current behavior? (You can also link to an open issue here)
Docs app uses bower
What is the new behavior (if this is a feature change)?
No use of bower in the docs application
Does this PR introduce a breaking change?
No
Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines: https://github.com/angular/angular.js/blob/master/CONTRIBUTING.md#commit-message-format
[x] Tests for the changes have been added (for bug fixes / features)
[x] Docs have been added / updated (for bug fixes / features)

Other information:

Looks pretty straightforward. Did you test that the docs app works as expected with the library updates?

@Narretz - yes I tested it manually and also we have a small handful of e2e tests for the docs app.

@petebacondarwin LGTM


how can i implements landmark image layer in caffe

the title is my question ，thank you for your reply.

Hi, I never used caffe, so it is hard for me to help with the implementation itself.
I advise that you take the look at the implementation in LandmarkImageLayer.py and try to reproduce it. Since this is fully deterministic the results you will get should be very similar to what this layer produces.
I will be more than happy to answer any specific questions as well.
Marek

As I can see, the landmark image layer generate the heatmap for the outupt layer, to enhance the information of predicted position (landmark) from previous stage. It is generally a forward process, this park shuold be easily implemented in caffe, my question is how can i implement the backward process, from heatmap to landmark. Can you give some advise?Thank you.

Hi, I am not sure by what you mean in "from heatmap to landmark".
The heatmap is used as an input to a convolutional neural network which infers the updates to the landmark locations based on the heatmap and other data, there is no single "heatmap to landmark" procedure.
Marek


Configurable Scaling for the HPA

This PR is a follow-up to the PR which added functionality to customise the scaling behavior of the HPA. The various configuration values and the defaults are explained in the documentation.

Assigning @tengqm since he is already heavily reviewing this.
/assign @tengqm

/lgtm


v0 of metric toolbox

minor refactor of the code

given that this is an initial commit, I am bypassing the 2nd review


User Profile Example: Cancel and Done buttons does not work

Tested on TestFlight.
Nothing happens when tap on Cancel/Done button.

The example has been redesigned. There are no Cancel and Done buttons now. And it is totally awesome.