Failures with pgjdbc build

@sehrope - I am getting the following errors when testing with the VM, after my changes in the pull request I submitted. Any ideas on what I can try? The interesting thing is that my VM host is "<IP_ADDRESS>", not "<IP_ADDRESS>".
Tests run: 4324, Failures: 1, Errors: 1, Skipped: 10, Time elapsed: 642.999 sec <<< FAILURE! - in org.postgresql.test.jdbc2.Jdbc2TestSuite
testConcurrentReplace(org.postgresql.test.jdbc2.BlobTransactionTest)  Time elapsed: 0.292 sec  <<< ERROR!
org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "<IP_ADDRESS>", user "postgres", database "test", SSL on
        at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:514)
        at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:141)
        at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:192)
        at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
        at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:195)
        at org.postgresql.Driver.makeConnection(Driver.java:454)
        at org.postgresql.Driver.connect(Driver.java:256)
        at java.sql.DriverManager.getConnection(DriverManager.java:664)
        at java.sql.DriverManager.getConnection(DriverManager.java:208)
        at org.postgresql.test.TestUtil.openPrivilegedDB(TestUtil.java:289)
        at org.postgresql.test.jdbc2.BlobTransactionTest.setUp(BlobTransactionTest.java:53)

testLockReleaseOnCancelFailure(org.postgresql.test.jdbc2.CopyTest)  Time elapsed: 0.522 sec  <<< FAILURE!
java.lang.AssertionError: cancelCopy should have thrown an exception
        at org.junit.Assert.fail(Assert.java:88)
        at org.postgresql.test.jdbc2.CopyTest.testLockReleaseOnCancelFailure(CopyTest.java:377)

@sehrope - thanks for getting me this far. Almost there.
I am getting the following failures:

I used port 100XY on localhost. However, the VM sees my host as "<IP_ADDRESS>". I tried adding host all all <IP_ADDRESS>/0 trust but it did not seem to help. Any ideas? (See details below.)

Please could you give me more information on what user credentials to use in build.local.properties  for org.postgresql.test.jdbc2.CopyTest? That is, can you suggest the contents of build.local.properties?

Tests run: 4324, Failures: 1, Errors: 1, Skipped: 10, Time elapsed: 464.261 sec <<< FAILURE! - in org.postgresql.test.jdbc2.Jdbc2TestSuite
testConcurrentReplace(org.postgresql.test.jdbc2.BlobTransactionTest)  Time elapsed: 0.123 sec  <<< ERROR!
org.postgresql.util.PSQLException: FATAL: no pg_hba.conf entry for host "<IP_ADDRESS>", user "postgres", database "test", SSL on
        at org.postgresql.core.v3.ConnectionFactoryImpl.doAuthentication(ConnectionFactoryImpl.java:514)
        at org.postgresql.core.v3.ConnectionFactoryImpl.tryConnect(ConnectionFactoryImpl.java:141)
        at org.postgresql.core.v3.ConnectionFactoryImpl.openConnectionImpl(ConnectionFactoryImpl.java:192)
        at org.postgresql.core.ConnectionFactory.openConnection(ConnectionFactory.java:49)
        at org.postgresql.jdbc.PgConnection.<init>(PgConnection.java:195)
        at org.postgresql.Driver.makeConnection(Driver.java:454)
        at org.postgresql.Driver.connect(Driver.java:256)
        at java.sql.DriverManager.getConnection(DriverManager.java:664)
        at java.sql.DriverManager.getConnection(DriverManager.java:208)
        at org.postgresql.test.TestUtil.openPrivilegedDB(TestUtil.java:289)
        at org.postgresql.test.jdbc2.BlobTransactionTest.setUp(BlobTransactionTest.java:53)

testLockReleaseOnCancelFailure(org.postgresql.test.jdbc2.CopyTest)  Time elapsed: 0.11 sec  <<< FAILURE!
java.lang.AssertionError: cancelCopy should have thrown an exception
        at org.junit.Assert.fail(Assert.java:88)
        at org.postgresql.test.jdbc2.CopyTest.testLockReleaseOnCancelFailure(CopyTest.java:377)

Results :

Failed tests:
  CopyTest.testLockReleaseOnCancelFailure:377 cancelCopy should have thrown an exception
Tests in error:
  BlobTransactionTest.setUp:53 » PSQL FATAL: no pg_hba.conf entry for host "10.0...

Tests run: 5442, Failures: 1, Errors: 1, Skipped: 48

Try destroying the entire VM (via "vagrant destroy") and rebuilding it from scratch to ensure you have the latest version. It shouldn't require any special manual config after that.
The values for build.local.properties that point to the VM are in the README: https://github.com/jackdb/pgjdbc-test-vm#how-do-i-use-it-to-test-the-jdbc-driver
I've tested locally with a slightly modified version of that which also includes spoofing the replication test servers with the same as the primary (which passes some of the replica tests but not all of them):
#### My build.local.propeties
# Point at PG version 10 on the VM through the localhost port map (username and password etc is the same as build.properties):
server=localhost
port=10010

# This is the super user for the C-language function tests:
privilegedUser=test_super
privilegedPassword=test

# Pretend our primary is also a replica (You can probably ignore this)
secondaryServer=localhost
secondaryPort=10010
secondaryServer2=localhost
secondaryPort2=10010

I'd ignore any replica related test issues. The other ones you mention (CopyTest and the Blob related one) should both pass with the config outlined in the README.

Yay! I got it to work! Thanks, @sehrope!


it looks so cool

I think it looks cool.

I have a problem. When process ids done, and Progress Dialog need to close, it closes background widget, and showing black screen.
Please see attached image below.


fixed: aboutPage margin style

Fixes # .
Changes proposed in this pull request:

There is a problem with the use of the margin style on the about page. The last element should not have a lower margin

before fix:

fixed:

@Qsnh thanks for your contribution. Could you try solving this with https://tailwindcss.com/docs/hover-focus-and-other-states#last-child indead?

ha, I forgot that tailwind has last-child.

I have made the changes. Thank you for your suggestions.Enjoy the code. :smile:


Simplify CONTRIBUTING.md process

Currently the CONTRIBUTING.md process has a lot of manual steps and is tedious.
None of the inputs to this process are secret, so we can commit inputs to the repo as an incremental step towards a broader refactor of the registry. Therefore the proposed implementation here is:

Create a superchain/input/template.toml file that has all the keys needed
Add yq or yj as a dependency. (yq parses TOML directly, yj converts it to json so we can pipe to jq)
Create a scripts/add-chain.sh bash script that contains all the existing code currently in CONTRIBUTING.md, with yq/yj usage as needed

Now to add a chain you would:

cp superchain/input/template.toml superchain/input/{l1ChainName}/{l2ChainName}.toml

Example: cp superchain/input/template.toml superchain/input/sepolia/mode.toml

Fill in the resulting file
Run bash scripts/add-chain.sh [path/to/your/input.toml]

Then to verify new inputs on PRs, CI run the bash script for new input files (or all inputs if its simpler), and verify there is no resulting diff (similar to how our snapshots work in the monorepo)
Alternatively, if we don't want to introduce TOML parsing yet, we can use a .env.example file and just export env vars

Yea that's fair. I do like the idea of using this issue as a step towards a dedicated input directory, and to your point DEPLOYMENTS_DIR is really not the input we care about—the contract addresses it holds are. So perhaps we do use env vars, and use those env vars to also generate the input file.
I'm also ok with keeping it simple and removing the input file approach for now if we think it's too early

Got a straw man implementation here https://github.com/ethereum-optimism/superchain-registry/pull/118
Happy to go after TOML and other refactors too, but that might be best broken up and done in follow ups?

Let's mark this as completed by #118 for now, and we can revisit pending feedback


CExporter stack trace

It looks like the c structs are a bit out of date with the csharp source, so I tried building/running your CExporter and got the following:
PS C:\Users\miked\Source\repos\FFXIVClientStructs\ida\CExporter\bin\Debug\net5.0> ./CExporter.exe Unhandled exception. System.ArgumentException: Field passed in is not a marshaled member of the type 'FFXIVClientStructs.FFXIV.Client.UI.AddonEnemyList'. (Parameter 'fieldName')    at System.Runtime.InteropServices.Marshal.OffsetOf(Type t, String fieldName)    at CExporter.FieldInfoExtensions.GetFieldOffset(FieldInfo finfo) in C:\Users\miked\Source\repos\FFXIVClientStructs\ida\CExporter\Program.cs:line 424    at CExporter.Exporter.<>c.<ProcessStruct>b__10_1(FieldInfo finfo) in C:\Users\miked\Source\repos\FFXIVClientStructs\ida\CExporter\Program.cs:line 145    at System.Linq.EnumerableSorter2.ComputeKeys(TElement[] elements, Int32 count)
at System.Linq.EnumerableSorter1.ComputeMap(TElement[] elements, Int32 count)    at System.Linq.EnumerableSorter1.Sort(TElement[] elements, Int32 count)
at System.Linq.OrderedEnumerable1.GetEnumerator()+MoveNext()    at System.Linq.Lookup2.Create(IEnumerable1 source, Func2 keySelector, IEqualityComparer1 comparer)    at System.Linq.GroupedEnumerable2.GetEnumerator()
at CExporter.Exporter.ProcessStruct(Type type, StringBuilder header) in C:\Users\miked\Source\repos\FFXIVClientStructs\ida\CExporter\Program.cs:line 147
at CExporter.Exporter.ProcessType(Type type, StringBuilder header) in C:\Users\miked\Source\repos\FFXIVClientStructs\ida\CExporter\Program.cs:line 105
at CExporter.Exporter.Export(GapStrategy strategy) in C:\Users\miked\Source\repos\FFXIVClientStructs\ida\CExporter\Program.cs:line 84
at CExporter.Program.Main(String[] _) in C:\Users\miked\Source\repos\FFXIVClientStructs\ida\CExporter\Program.cs:line 19`

I actually took a shot at "fixing" this issue, and was able to get past that particular one, but then ran into NUMEROUS other problems with errors due to problems with how the offsets are defined, particularly where different fields defined at the same offsets are translated to C unions, or where generic instantiations are required.   I've been trying to modify the source to get around the issues, but given the sheer number of the issues I've encountered, I'm not sure how this program ever really "worked".   Could that be why the current c header files this program creates are so out of date in the repository?   In any event,  having those files really is quite useful, so if there is any way you could take a whack at brining them up to date, that would be really helpful.

I was able to fix this issue in a local branch I created from a clone of this repository.  Unfortunately, I do not know how to create a pull request that allows you to consider these fixes for inclusion into the main repository.  I tried following the instructions, but it appears I am not able to create the branch for the fixes.  So any help getting this to you would be appreciated.

fork your own, push to it, then in github web you can make a PR and select your branch/fork.

im reviewing this now.


Compatibility with Concoord

Hi, thanks for maintaining dssp!
I recently tried to use dssp with Concoord, but no version from 2. until 4. worked. Older versions of dssp have been shown to have worked, but those are not available anymore.
I just wanted to ask if you happened to know what could cause this.
Dssp 2.2.1 I found on Debian, at least told me it was a bad lexical cast. Every other version just told me "empty protein, or no valid complete residues".
Using any dssp as a standalone worked perfectly fine.
Many thanks
Tom Unterleiter

This has probably something to do with the coordinate files CONCOORD writes out. Could you send us an example coordinate file that causes the issue.

Here is the output of concoord until it crashes, and the files used and outputted are attached as a zip.
Normally dist.dat should have the calculated distance constraints needed for further calculations but it is empty.
Thank you very much
/data/tom/ssptest ]$ dist -p 1pgaohneM.pdb -dssp mkdssp
Select a set of Van der Waals parameters:
1: OPLS-UA (united atoms) parameters
2: OPLS-AA (all atoms) parameters
3: PROLSQ repel parameters
4: Yamber2 parameters
5: Li et al. parameters
6: OPLS-X parameters (recommended for NMR structure determination)
1
Selected parameter set 1
copying /data/tom/CCPBSA/concoord_2.1.2/lib/ATOMS_oplsua.DAT to ATOMS.DAT in current working directory
copying /data/tom/CCPBSA/concoord_2.1.2/lib/MARGINS_oplsua.DAT to MARGINS.DAT in current working directory
Select a set of bond/angle parameters:
1: Concoord default parameters
2: Engh-Huber parameters
1
Selected parameter set 1
copying /data/tom/CCPBSA/concoord_2.1.2/lib/BONDS.DAT.noeh to BONDS.DAT in current working directory
dist.exe - build date: Thu Jan 24 11:26:08 CET 2013
Process started with PID:  2368420
on host: bccb12
in directory: /data/tom/ssptest
on: 27/06/0022 at: 10:15:27
command line options:
pdb input coordinate file...........: 1pgaohneM.pdb
dssp executable.....................: mkdssp
non-bonded cut-off radius...........:   4.00 A + VDW sum
minimal nr. of distances per atom...:     50
output distances....................: dist.dat
output coordinates (PDB)............: dist.pdb
output coordinates (GROMOS87).......: dist.gro
hydrogen atoms (if any) will be removed
non-bonded contacts of starting structure will be preserved
processing input...
total number of atoms       :      428
number of residues          :       55
number of atoms to be used  :      428
starting DSSP calculation...
DSSP could not be created due to an error:
empty protein, or no valid complete residues
Something went wrong during the DSSP calculation!
failed_concoord.zip

The dist.pdb lacks a CRYST1 record which is sort of a minimum requirement for a valid PDB file. The best thing you can do is take this up with the CONCOORD developers. Feel free to CC me in.


Problem with compendium-folders?

I'm using v9.x and I tried for example to cast Misty Step (which has AE flag and came from midi-srd). I notice the following error:
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'folders')
[Detected 2 packages: compendium-folders, sequencer]
    at Function.importFolderData (modules/compendium-folders/fic-folders.js:1469:52)
    at modules/compendium-folders/fic-folders.js:472:34
    at Function._call (foundry.js:294:14)
    at Function.callAll (foundry.js:253:12)
    at ClientDatabaseBackend.callback (foundry.js:10254:13)
    at foundry.js:10193:43
    at Array.map (<anonymous>)
    at ClientDatabaseBackend._handleUpdateDocuments (foundry.js:10193:33)
    at ClientDatabaseBackend._updateDocuments (foundry.js:10074:17)
    at async Function.updateDocuments (common/abstract/document.mjs:373:21)
    at async Scene.update [as __compendium_tools_original_update] (common/abstract/document.mjs:456:21)
    at async Object.<anonymous> (modules/sequencer/scripts/module/flag-manager.js:237:13)

Module is not updated for v9


Workflow streamlined with respect to authenticating and cache updating

If a search finds no result, you're now given the option to update the cache right there, and to repeat the search after.
If no token has ever been set or it is invalid, you can switch over to gh-auth simply by actioning the error message.
gh-auth without an argument now opens https://github.com/settings/tokens/new to facilitate creating a token.

README.md has been updated accordingly, and some copyediting was performed.

Bugfix (fixes #1): the number of repos retrieved is no longer limited to 30.

:+1: Would love to see this (or something akin) merged in. I belong to an organization with over 100 repositories (not to mention all of my forks).
Thanks to @mklement0 and @jenius for their contributions!

Although considering the lack of activity here, I'll be using this as an alternative...
https://github.com/gharlan/alfred-github-workflow

While this PR fixed my issue... it doesn't look like it will be merged let alone maintained in the future so for now https://github.com/gharlan/alfred-github-workflow does indeed resolve my current need.
Thanks @jfairley for the recommendation.
Thanks @mklement0 and @jenius for your contribs.

Thanks, @jfairley  and @michaeltarleton. Bummer that this was abandoned, but I'm glad you found an alternative; I'll take a look myself.

@mklement0 if someone were to fork this and everyone could send their PRs to that fork, I'd still use this one. To me it's fast and does exactly what I need.

@michaeltarleton I'll consider it. Is speed the only issue you have with the alternative?

@mklement0 Well now that I checked again, it does seem to be caching it's very quick now. So I guess the new plugin is prly what I'll stick with. Also, It does seem to be much more active than this one.


Required named parameter 'parseErrorData' must be provided.

Hi, we upgraded to latest flutter and use magic sdk which depends on agent_dart. We ran into the following issue:
../../../../../.pub-cache/hosted/pub.dev/agent_dart-1.0.0-dev.17/lib/bridge/ffi/ffi_bridge.dart:461:57: Error:
Required named parameter 'parseErrorData' must be provided.
This comes from agent_dart which is referenced in the magic sdk. I tried to pinpoint the agent_dart version and this error shows up for the first time in '1.0.0-dev.15' - Also posted within the magic sdk -> https://github.com/magiclabs/magic-flutter/issues/45
agent_dart is v 1.0.0-dev.17
magic is 4.1.3
[✓] Flutter (Channel stable, 3.13.7, on macOS 13.5.1 22G90 darwin-arm64, locale en-US)
[✓] Android toolchain - develop for Android devices (Android SDK version 31.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.2)
[✓] VS Code (version 1.83.0)
[✓] Connected device (3 available)
[✓] Network resources

This is because we haven't upgraded to the latest FRB in our latest released version. We've rolled the version (#69) but got issues when compiling them, still working on it.

cool, thx.


Lists are created with an extra empty line between rows

Hi @souvikinator :)
We noticed an issue with the output of lists. We have the following Notion page (public):
https://www.notion.so/Roadmap-232f99f86aa34383bac5d72e53aa24b7
This is how it looks like on Notion:

We are converting the Notion page to Markdown and then publish it to GitHub as issue/discussion, and this is the result: https://github.com/dotansimha/graphql-yoga/issues/1358

It seems like there is an additional line break between list rows:

Yep! I can reproduce it. Will fix the issue and create a release shortly.
Thanks for reporting.

Thank you! I saw you bumped to 2.5.1 but release is not yet on npm?

Yes! now it's live on NPM as well.
Thanks for the contribution :))

Closing the issue. Make sure to reopen this if the issue still persists.


New version: LibSndFile v2.2.0

Registering package: LibSndFile
Repository: https://github.com/JuliaAudio/LibSndFile.jl
Created by: @ssfrr
Version: v2.2.0
Commit: 30f644fddda278599ef51073902471be827177cf
Reviewed by: @ssfrr
Reference: https://github.com/JuliaAudio/LibSndFile.jl/commit/30f644fddda278599ef51073902471be827177cf#commitcomment-36056952

I'm guessing the issue here is that this release is lower-bounded on Julia 1.3 to take advantage of the new BinaryBuilder/Artifacts stuff. It it OK to merge anyways, as folks with older Julia versions will just get the previous version?

Also a side note - it took me a minute to figure out that I needed to look through the "AutoMerge / build" logs to find the failure even though it looks like a success - would be be possible to have that script exit with an error code on failure so it's a little more obvious which logs to look at?


Fix memory graph legend

@bot-gradle test BD

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

BuildDistributions build

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

BuildDistributions build

@bot-gradle test BD


Shell-operator fails on handling something

Expected behavior (what you expected to happen): Periodically error occurred while shell-operator trying to handle something
Actual behavior (what actually happened): Error does not occur, have enough info about problem
Steps to reproduce:

Deploy shell-operator & crd

Additional info:
Tried to enable debug log level but it doesn't help (only logs which entities are processing, each time error message meets in different places)
Environment:

Shell-operator version: v1.0.10
Kubernetes version: v1.22.12
Installation type (kubectl apply, helm chart, etc.): helm chart

Anything else we should know?:
Hook script
    #!/usr/bin/env bash
set -e

echoerr() {
  printf "ERROR. %s\n" "$*" >&2;
}

##### HOOK #####

if [[ $1 == "--config" ]] ; then
    cat <<EOF
configVersion: v1
onStartup: 1
kubernetes:
  - name: OnDiscoveryEvent
    apiVersion: custom.group/v1
    kind: Discovery
    executeHookOnEvent:
      - Added
      - Deleted
  - name: OnServiceEvent
    apiVersion: ""
    kind: Service
    executeHookOnEvent:
      - Added
      - Modified
      - Deleted
EOF
else
  for context in $(jq -c '.[]' "$BINDING_CONTEXT_PATH"); do
    echo "Just log"
  done
fi

Custom resource definition
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  # name must match the spec fields below, and be in the form: .
  name: discoveries.custom.group
spec:
  # group name to use for REST API: /apis//
  group: custom.group
  # either Namespaced or Cluster
  scope: Namespaced
  names:
    # plural name to be used in the URL: /apis///
    plural: discoveries
    # singular name to be used as an alias on the CLI and for display
    singular: discovery
    # kind is normally the CamelCased singular type. Your resource manifests use this.
    kind: Discovery
  # list of versions supported by this CustomResourceDefinition
  versions:
    - name: v1
      # Each version can be enabled/disabled by Served flag.
      served: true
      # One and only one version must be marked as the storage version.
      storage: true
      # The schema for validating custom objects
      schema:
        openAPIV3Schema:
          type: object

Logs
{"level":"info","msg":"shell-operator v1.0.10","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Listen on <IP_ADDRESS>:9115","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric counter discovery_operator_live_ticks","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric histogram discovery_operator_tasks_queue_action_duration_seconds","operator.component":"metricsStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric gauge discovery_operator_tasks_queue_length","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric gauge discovery_operator_kube_snapshot_objects","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric gauge discovery_operator_kube_snapshot_bytes","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric histogram discovery_operator_kube_jq_filter_duration_seconds","operator.component":"metricsStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric histogram discovery_operator_kube_event_duration_seconds","operator.component":"metricsStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric gauge discovery_operator_hook_enable_kubernetes_bindings_seconds","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric counter discovery_operator_hook_enable_kubernetes_bindings_errors_total","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric gauge discovery_operator_hook_enable_kubernetes_bindings_success","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric histogram discovery_operator_hook_run_seconds","operator.component":"metricsStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric histogram discovery_operator_hook_run_user_cpu_seconds","operator.component":"metricsStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric histogram discovery_operator_hook_run_sys_cpu_seconds","operator.component":"metricsStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric gauge discovery_operator_hook_run_max_rss_bytes","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric counter discovery_operator_hook_run_errors_total","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric counter discovery_operator_hook_run_allowed_errors_total","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric counter discovery_operator_hook_run_success_total","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric counter discovery_operator_task_wait_in_queue_seconds_total","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Hooks dir: /hooks","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Use temporary dir: /tmp/shell-operator","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Debug endpoint listen on /var/run/shell-operator/debug.socket","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric histogram discovery_operator_kubernetes_client_request_latency_seconds","operator.component":"metricsStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Create metric counter discovery_operator_kubernetes_client_request_result_total","operator.component":"metricStorage","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Kubernetes client is configured successfully with 'out-of-cluster' config","operator.component":"KubernetesAPIClient","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Kubernetes client is configured successfully with 'out-of-cluster' config","operator.component":"KubernetesAPIClient","time":"2022-10-05T12:14:24Z"}
{"level":"info","msg":"Initialize hooks manager.  Sorry, I've missed this one for so long. Do you have proper RBAC with rules for the Discovery kind?

I think root cause is that I've forgot to add watch rules for resources


Respond to requests on bucket vhost

I have a situation where I'm testing S3 interaction code as a black box. I can't (or prefer not to) modify the code to point to a special S3 endpoint and force path-style requests. Instead, what I'd like to do is intercept traffic bound for [bucket].s3.amazonaws.com and redirect that traffic to s3rver, e.g. with a rule in /etc/hosts.
This PR has s3rver parse the host header and, if it matches a bucket vhost, then it handles the request for that bucket.
This only changes the behavior when s3rver receives a request with a host like [bucket].s3(-[region])?.amazonaws.com, so normal usage stays the same.

This would be useful to us esp if we were somehow able to configure the custom domain to match ([bucket].s3rver.our.domain), maybe using env or some cli argument...


Normalize API error responses

Updates responses on some API functions, to make it more same across all.

this is reverting work that was done before pretty much because of opposite reasons. not that i care about zig-zagging, but we should at least be consistent as to which kind of internals we'd like to expose on error codes. i believe the #680 was exactly about that

@acud You are right, I did not consider previous changes. This PR was in response to comments from pin/unpin PR changes, where it was the comment was different. I will close this one.


⚠ Orpheus has degraded performance

In 677662a, Orpheus ($OPS) experienced degraded performance:

HTTP code: 504
Response time: 21100 ms

Resolved: Orpheus performance has improved in a99aec8.


MV_FILTER_ONLY may run into Exceptions in case duplicate values were processed

MV_FILTER_ONLY assumed that there are no duplicates in their input; however that may not be true - as if the values are run thru a function (like LOOKUP) - that property may change.
This changeset changes the preallocated output size to be assomptical with the number of inputs instead of clamping at the size of the filtering array.

Fixes #XXXX.

Description

Fixed the bug ...
Renamed the class ...
Added a forbidden-apis entry ...

Release note

Key changed/added classes in this PR

MyFoo
OurBar
TheirBaz

This PR has:

[ ] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] a release note entry in the PR description.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[ ] been tested in a test Druid cluster.

The CI failures were due to the flakiness in some of the IT jobs which are unrelated - repeated rerunning of them didn't let us get pass the setup issue we were running into, hence merging this.


Added ignore default link prefixing

Ability to have mysite.com/mypage defaulting to mysite.com/en/mypage (or whatever is set as the default locale for Translatable)

Hi Leapfrognz,
Guess this didn't work out back then :) In the meantime version v3.0.0 is a lot different internally, and it does support skipping the prefix for the default locale, so I guess I can safely close this one.
Thanks though :)


On the windows7 host, a problem with your license for Remote Desktop

I have a very important and urgent matter that I need your help to solve!
I am currently using windows7 as a remote desktop host. However, after running for some time, you cannot connect to this host.
"There is a problem with your license for Remote Desktop and the session will end in 60 minutes"

Can someone help me in this regard.

🧐


Country-code (flag) simplifications

Flags are made up of two "regional letter" Unicode symbols. e.g. the 2-letter international code for Iceland is IS, so the Iceland flag is  🇮 Regional Indicator Symbol Letter I and 🇸 Regional Indicator Symbol Letter S
The Union Flag is kinda an exception, it's the flag for the UK but it uses the code for GB.
But really, I could do away with the form for defining country flags, and just put IS for Iceland, and translate that to the emoji at runtime.
And we can do multiple countries, I'd just enter "UK US", say, and get "🇬🇧 🇺🇸"
Provided mapping the 'plain' chars to the regional indicators is easy, this will simplify things

^ Code for the union flag is actually based on GB rather than US, i.e. Regional Indicator Symbol Letter G and Regional Indicator Symbol Letter B


Kickstarter recently updated their logo

Updated Nov 2017. See Kickstarter Brand Assets:
https://www.kickstarter.com/help/brand_assets

Wow!


Feature request: Default to Ruff version from project setup

At the moment the action defaults to the latest version of Ruff. In order to match local behaviour, it would be good if the action defaulted to the version matching that inside pyproject.toml / poetry.lock.

My guess is that some mechanism that attempts to pick the Ruff version from the project setup, and fail with an error message if the version can't be determined automatically would satisfy most people. The few projects that have complex setups that use different versions of Ruff for different platform/systems can then set the version in the action instead.
Here's how the black action does it: https://github.com/psf/black/pull/4294. It would be nice if the Ruff action just works without having to add some other action to get Python 3.11 configured first.

I think searching from a pyproject.toml would cover most cases. With the following priority, highest Ruff version match found in:

project.dependencies
project.dependency-groups.dev (new canonical dev dependencies)
project.optional-dependencies.dev (old common dev dependencies)
Any other project.dependency-groups
Any other project.optional-dependencies
(optional) Some (.+?-)?requirements(-.+?)?.txt (maybe only if a requirements file is indicated as the source to find the version?)

https://github.com/astral-sh/ruff-action/pull/30 changes the default behavior to:

Search for a pyproject.toml in the repo root
Search in project.dependencies and dependency-groups.dev for ruff
If none is found use latest

Support for requirements.txt files can be added later


Update the Template Design - City Metro

Update the design of the City Metro template.
Need to check for the A4/Portrait requirement

This is a duplication for the #412


Add vl.xrpl.vision to validators-example.txt

Add the list provider vl.xrpl.vision (xrpl.vision) to validators-example.txt and include the keys.

I recommend waiting until https://github.com/XRPLF/rippled/pull/5112 is merged and released ; without this change, any additional UNL publisher will reduce the security of the UNL system


[FEATURE] Allow setting orjson options in ORJSONResponse

This is a problem and a requested feature.
orjson takes a lot of options for dumping data, such as allowing UUID dumping with option=orjson.OPT_SERIALIZE_UUID. It would be nice if we could use these options when using ORJSONResponse.
As far as I'm aware, with the existing implementation of ORJSONResponse, there is not a way to do this, as orjson cannot be configured globally, and ORJSONResponse does not pass any args except the content to dump to orjson.dumps.

@tiangolo this was also mentioned on #1165, is it something you'd want done? I'm up for it if so :)

@acnebs Do you want to set option, when you define default_response_class?

it's possible and easily by doing this :
https://github.com/tiangolo/fastapi/pull/1846#issuecomment-688553504
You can probably close this issue, thank you

Thanks for the interest @acnebs! And thanks for the pointer @raphaelauv!
I added this section to the docs explaining how to make a custom response: https://fastapi.tiangolo.com/advanced/custom-response/#custom-response-class


Error:Assert failed:in file ../../../../ccmain/tessedit.cpp, line 193

I try to get output from text image using the following command.
tesseract ocrsi1.jpg 'text1' -l eng
I get perfect output. But I tried the following code with Sinhalese but I did not get output.
tesseract ocrsi2.jpg 'text2' -l sin
Error Message:
lstm_recognizer_->DeSerialize(&fp):Error:Assert failed:in file ../../../../ccmain/tessedit.cpp, line 193
How to solve this error?
I am using new v4 with python 3.6.
I also download tessdata and langdata and put into tesseract installed folder.
This is ocrsi2.jpg image file.

How to solve this error? I tried other languages also but I get the same error.

ubuntu@tesseract-ocr:~/TEST$ tesseract sinhala.jpg - -l sin --oem 1 --psm 6
සිංහල
ubuntu@tesseract-ocr:~/TEST$ tesseract sinhala.jpg - -l sin --oem 1 --psm 3
සිංහල
ubuntu@tesseract-ocr:~/TEST$ tesseract sinhala.jpg - -l sin --oem 1 --psm 4
සිංහල
ubuntu@tesseract-ocr:~/TEST$ tesseract sinhala.jpg - -l sin --oem 1 10
read_params_file: Can't open 10
සිංහල
ubuntu@tesseract-ocr:~/TEST$

I tried other languages also but I get the same error.

What is the output of?
tesseract --list-langs

Closing as issue can not be reproduced.

I have the same Issue here so, you should not close this

To anyone getting this error: Please check that you use a supported version of Tesseract (4.1.1 or newer).

See also issues #1680.


chore: Improves the layout of the VizTypeGallery component

SUMMARY
Improves the layout of the VizTypeGallery component.

Vertical aligns selectors to the center
Adds top margin to the search bar
Sets the charts panel scroll to auto
Increases the panel padding
Replaces the Select component
Decreases the width of the select and adds the hint to the same line
Sets a border-radius to match the rest of the application

@junlincc @rusackas @suddjian
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TESTING INSTRUCTIONS

Click on Add chart
Check the changes on the screen

ADDITIONAL INFORMATION

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

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

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

/testenv up

/testenv up


Bug: Pull request showing as open but I merged it

To get into this state, I went through these steps:

Opened GitLight
Clicked on the PR
Merged it on GitHub
Went back to GitLight
After a few refreshes, GitLight is still showing the PR as open

PR: https://github.com/vercel/turbo/pull/5134

Might have found why this happen... Stay tuned!


chore: added commitizen config

:tada: This PR is included in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Change menu wording to remove the word "showcase"

The object that should be changed is in https://github.com/jina-ai/jina-ui/blob/master/packages/showcases/src/components/Sidebar.tsx#L22

I can take a look at this


[Bug] Mariadb-operator  allows me to add a external rwx shared pvc   but ignoreing storaeclass rules

Documentation

[x ] I acknowledge that I have read the relevant documentation.

Describe the bug

Expected behaviour

my pvcs should mount to the correct storage device set by the storage class
Steps to reproduce the bug

...  set a storage class
...   create pvc
...  add pvc to mariadb-operator

Debug information

Related object events:

kubectl get events --field-selector involvedObject.name=<mariadb-resource-name>
kubectl get events --field-selector involvedObject.name=<backup-resource-name>
kubectl get events --field-selector involvedObject.name=<restore-resource-name>

mariadb-operator logs. Set the --log-level to debug if needed.

Environment details:

Kubernetes version:   1.30.0
Kubernetes distribution: k8
mariadb-operator version: latest
Install method: kubectl
Install flavor: unknown

Additional context
longhorn version 1.6.1

i think alot of my text an images  have been removed

storageClasses
kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: longhorn-nfs-ssd
provisioner: driver.longhorn.io
allowVolumeExpansion: true
#mountOptions:
#- /mnt/ssd
volumeBindingMode: WaitForFirstConsumer   #Immediate
parameters:
numberOfReplicas: "1"
dataLocality: "disabled"
#staleReplicaTimeout: "480" # 8 hours in minutes
diskSelector: "ssd"
nodeSelector: "corp,storage"
fsType: "ext4"
#nfsOptions: "soft,timeo=150,retrans=3"

kind: StorageClass
apiVersion: storage.k8s.io/v1
metadata:
name: longhorn-nfs-sas
provisioner: driver.longhorn.io
allowVolumeExpansion: true
#mountOptions:
#- discard # this might enable UNMAP / TRIM at the block storage layer
volumeBindingMode: WaitForFirstConsumer  #Immediate
parameters:
numberOfReplicas: "1"
dataLocality: "disabled"
#staleReplicaTimeout: "480" # 8 hours in minutes
diskSelector: "sas"
nodeSelector: "corp,storage"
fsType: "ext4"
#nfsOptions: "soft,timeo=150,retrans=3"
PVC's  that use this class are made with the following:
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mariadbroot-node2
spec:
accessModes:

ReadWriteMany
storageClassName: longhorn-nfs-ssd
resources:
requests:
storage: 50Mi

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mariadbroot-node1
spec:
accessModes:

ReadWriteMany
storageClassName: longhorn-nfs-ssd
resources:
requests:
storage: 50Mi

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: mariadb-backup
spec:
accessModes:

ReadWriteMany
storageClassName: longhorn-nfs-sas
resources:
requests:
storage: 50Gi

I am also  seeing that besides my external  pvcs  not going to the correct nodes specifies in there storage class,  The  some of the actuall mariadb pods  are trying to map to the   local directly specified by the class..
/mnt/ssd   is only configuired for my new storage class   which mariadb-operator is not setup too use

The only pvcs  that should be mounting with that class is :


JobWithDetails.getAllBuilds() throws Exception with 404

My job has many builds, but I got null when call jenkinsServer.getJob("Folder1/Folder2/jobName").getAllBuilds().
Then I check the source code, and find:
List<Build> builds = client.get(path + "job/" + EncodingUtils.encode(this.getName())
                    + "?tree=allBuilds[number[*],url[*],queueId[*]]", AllBuilds.class).getAllBuilds();

The problem is this.getName(). My job's full path is :
/job/Folder1/job/Folder2/job/jobName
But this.getName() only returns jobName.
So I can get correct results with this:
List<Build> builds = client.get("/job/Folder1/job/Folder2/job/jobName"
                    + "?tree=allBuilds[number[*],url[*],queueId[*]]", AllBuilds.class).getAllBuilds();

we can define our current jobs path in a static or a final variable before instantiating the job.
Once try this approach


File jaspersoft_webserviceds_v1.5.zip does not exist on cloudfround domain.

jasperserver    | --2019-01-05 19:12:14--  https://d2553lapexsdrl.cloudfront.net/sites/default/files/releases/jaspersoft_webserviceds_v1.5.zip
jasperserver    | Resolving d2553lapexsdrl.cloudfront.net (d2553lapexsdrl.cloudfront.net)... failed: Name or service not known.
jasperserver    | wget: unable to resolve host address ‘d2553lapexsdrl.cloudfront.net’

I thing the file url address on entrypoint.sh must me replaced.


Support for Minitest?

yes/no/maybe/already?

I've not used Combustion with Minitest, nor does anything within it exist specifically for that purpose, but patches are very much welcome. It was discussed briefly in #4, but nothing detailed.

Thanks for the reply. I’ll poke at it to explore feasibility and effort when I get a chance! :)

FWIW, I was able to use this with Minitest by creating a test/test_helper.rb file, which I required in each of my tests files...
#file: test/test_helper.rb
require "combustion"
Combustion.path = "test/internal"
Combustion.initialize! :all

Thanks for sharing that Joshua, great to hear it's working for you :)

I did exactly the same, also works flawlessly. I'm doing integration tests, however I'm not using activerecord.


release inkscape-open-symbols

It would be great to have a github release of inkscape-open-symbols. (It would help packaging for Debian)

Thanks for the suggestion. I didn't know this could be useful for packaging!
I guess once its sorted out all the required information from weather icons it would be ok to create a 1.0.0 release. What do you think?
Will I need to include all the svg files zipped so it can be simply unzipped into the inkscape symbols folder? Or maybe only creating the release tag would be enough?
Thanks for your help :wink:

It's easy to create releases on github: https://help.github.com/articles/creating-releases/
You just create the release, github adds the .zip, .tar.gz for you :-).
If it just takes a few days, we can of course do that after #44 is solved. I'll just wait a little bit more to create the Debian package.

It would be simply amazing if this could ship with the final installer/package. It should be enabled when the user selects (at least in Windows) custom or full installation. +1 for this! _o/

@Xaviju, now that #44 is fixed, is there still something preventing a release of inkscape-open-symbols?

Everything seems fine now. Should we create the 1.0.0 release?

sure!

(or whatever numbering you prefer) 1.0 may be OK, too.

https://github.com/Xaviju/inkscape-open-symbols/releases/tag/v1.0

Congrats :)
(Nitpicking follows: for a release, does it make sense to include all those files? I'd only have put the README, LICENSE and the svgs into it, to make it easy for packagers. Neither gitignore, the gulpfile, the template or the subfolder ordering is relevant for a .deb package, I think.)

@Moini no, it doesn't. Only SVG files, readme and license seems perfectly enough. If you create the deb package, please add it to the readme and in the #57 issue to add it to the website.

It doesn't matter too much to have everything in the archive. It's easy to select only /.svg. My debian package is almost ready :)

He is added to the issue recently closed. Thanks @PanderMusubi

Would it be possible to get a new release and updated package? We are already two years down the road.


New version not showing under releases

Version 0.0.5 is not listed under github releases and 0.0.4 is marked as the latest release.

Thanks. Fixed. Need to automate a bit more of the release process...


People without an age don't show up

There are some profiles that don't have ages tied to them, typically it is users that use Grindr on an apple phone.  I'm not sure if this is a glitch, but I know a few of them around me, and they are online but do not show up on the grid or the map.  I looked at the SQLite database and there is no age value even present under the age section of these certain profiles so I think the program automatically won't show them up because the value for age is missing.  If you need me to screen shot the database please let me know.  I did notice if you are not logged in to the Fuckr app they will show up,
While logged in I had one of them message me, and it still won't map them out even when clicking on their profile from the messages.

This app does display profiles without an age value even if you specify filters (I guess for those who have showAge: false). Just in case, and for cleanness, I cleaned up the filter parameters in 351210e.

The map only works for profiles showing distance and that are relatively close btw


Custom hitsounds on valve servers.

Can you make custom hitsounds work on valve servers?

@danielkrupinski

what?🤨

what?🤨

custom hitsounds dont work in matchmaking

everything works fine
1)check hitsound file name
2)check directory (should be in csgo/sound)

u need to bypass sv_pure to use on valve servers.

#1802

#1802

sv_pure bypass doesent work anymore


Unable to locate DNS servers with the steps followed

[Enter feedback here]
The original doc says
Change the primary and secondary DNS address for the Srv-Work network interface
For testing purposes in this tutorial, configure the server's primary and secondary DNS addresses. This isn't a general Azure Firewall requirement.
From the Azure portal, open the Test-FW-RG resource group.
Select the network interface for the Srv-Work virtual machine.
Under Settings, select DNS servers.
Under DNS servers, select Custom.
Type <IP_ADDRESS> in the Add DNS server text box, and <IP_ADDRESS> in the next text box.
Select Save.
Restart the Srv-Work virtual machine.
The above text is partially right. The first half is right.
I couldn't find the DNS Servers under Settings section.
Not sure if this has changed recently. The only way i can add DNS servers is by going to the
Virtual Networks >> select your Vnet >> Settings >> Connected Devices
select the NIC attached to that subnet and then you will see DNS servers under Settings section

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: ac13cbf3-f230-7e85-d57d-cba3196a166c
Version Independent ID: f4f0c94a-5a43-94e2-d8e5-19cf167c188a
Content: Tutorial: Deploy and configure Azure Firewall using the Azure portal
Content Source: articles/firewall/tutorial-firewall-deploy-portal.md
Service: firewall
GitHub Login: @vhorne
Microsoft Alias: victorh

@kumarallamraju Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@kumarallamraju
Sorry, I can't repro your issue. Whether you select the network interface directly from the resource group, and indirectly from via the VNet, it leads you to the same place: the network interface.
So, I'm not sure how you are seeing different settings for a network interface depending on the path you take to access it.

#please-close

@kumarallamraju We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


fix: nix-shell environment for building spdk on arm

This PR documents the changes needed to get the ARM64 build working and running the example hello-world application. Here are some of the issues encountered along the way.

Debugging the ARM Build

I spun up an arm64 machine on Hetzner and debugged the install process step by step.
First tried running nix-shell without SPDK and hit issues with pyelf. Replacing python3.withPackages with pkgs.python3Packages.pyelftools fixed that.

Key Issue

The main problem in a manual build was the -msse4 flag, which is for x86 extended instruction sets and doesn’t work on ARM.
I split the nix-shell compiler flags into configurable strings so we can set optimization flags per architecture.
Then, in the default nix-shell spdk configure and build, Clang was the default compiler, this led to SVE compilation issues. In the "no-spdk-installed" nix environment, I noticed I was getting success w/ GCC, so migrated the nix script to remove Clang and use GCC by default. I don't want to get presumptuous that this is the best solution, very open to feedback on this.

Context

As mentioned in the parent OEP (https://github.com/openebs/openebs/issues/3817), the goal here is just to make ARM builds possible—not optimized.
I have also tested the new changes on an amd64 system and everything went as expected. Not super familiar with what test suite I should be running.

Addresses

Fixes #71

Please let me know if you'd rather me focus on getting the OEP to implementable rather than starting to implement fixes!

Then, in the default nix-shell spdk configure and build, Clang was the default compiler, this led to SVE compilation issues. In the "no-spdk-installed" nix environment, I noticed I was getting success w/ GCC, so migrated the nix script to remove Clang and use GCC by default. I don't want to get presumptuous that this is the best solution, very open to feedback on this.

Changing compiler doesn't sound like something to do lightly, even though it may compile.
I'd rather first try to explore other ways of fixing the SVE compilation, what do you think @dsharma-dc ?

Yeah, I totally understand how that is not ideal. I've been banging at it for a little bit hoping I've been missing something obvious.

Btw I've added github-arm64-2c-8gb runner to this repo, here's an example: https://github.com/openebs/spdk-rs/commit/bb3a764547243c9ecac9af92a2d01e0e4bce57cb
And of course it fails to build...
Maybe you can also integrate this in your PR?

Btw I've added github-arm64-2c-8gb runner to this repo, here's an example: bb3a764 And of course it fails to build... Maybe you can also integrate this in your PR?

This is great, and hahah classic. Sorry that may be on me for not running it in with the --pure flag. I'll dig into it asap. Thanks for all of your help.

Funny enough that it was also to bring aarch64 support :)

Thank you for doing the historical deep-dive to figure out the root of things. ^ This callout made me chuckle, so thanks for that.

So, I think using gcc is a good idea anyway since that's how it used to be, and was probably an unfortunate mistake that ended up changing that during the latest refactoring.

Great!

Also, please try to build mayastor io-engine with your spdk-rs code to ensure that is also working with this.

Yes of course, I'll do that asap. I noticed you guys were talking about merging the repos here #64, the CI for SPDK-rs also being tested downstream alone may be a convincing enough argument for the shift.

I tried building through the release script + just raw cargo build. The nix-shell, built fine as expected. However on the build of the io-engine I'm running into:
error[E0308]: mismatched types
   --> io-engine/src/bdev/ftl.rs:213:25
    |
213 |         ftl_conf.name = ftl_dev_name.as_ptr() as *mut i8;
    |         -------------   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `*mut u8`, found `*mut i8`
    |         |
    |         expected due to the type of this binding
    |
    = note: expected raw pointer `*mut u8`
               found raw pointer `*mut i8`

error[E0308]: mismatched types
   --> io-engine/src/bdev/ftl.rs:214:30
    |
214 |         ftl_conf.base_bdev = base_dev_name.as_ptr() as *mut i8;
    |         ------------------   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `*mut u8`, found `*mut i8`
    |         |
    |         expected due to the type of this binding
    |
    = note: expected raw pointer `*mut u8`
               found raw pointer `*mut i8`

error[E0308]: mismatched types
   --> io-engine/src/bdev/ftl.rs:215:31
    |
215 |         ftl_conf.cache_bdev = cache_dev_name.as_ptr() as *mut i8;
    |         -------------------   ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected `*mut u8`, found `*mut i8`
    |         |
    |         expected due to the type of this binding
    |
    = note: expected raw pointer `*mut u8`
               found raw pointer `*mut i8`

although the bdev/ftl.rs file does import spdk-rs bindings, these are all either String or CString .as_ptr() calls which seems auxilary to the spdk changes.
The docs for CStr do say:

Returns the inner pointer to this C string.
The returned pointer will be valid for as long as self is, and points to a contiguous region of memory terminated with a 0 byte to represent the end of the string.
The type of the returned pointer is [*const c_char], and whether it's an alias for *const i8 or *const u8 is platform-specific.

This may be able to be fixed by casting to std::os::raw::c_char or libc::c_char instead of hard coding i8 or u8

Yes this should work with std::os::raw::c_char.
cc: @MaisenbacherD

Have a full mayastor build working with this mayastor pr branch https://github.com/openebs/mayastor/pull/1796 pointed to this pr's branch of spdk-rs

Awesome, great work @maxwnewcomer !!!

This may be able to be fixed by casting to std::os::raw::c_char or libc::c_char instead of hard coding i8 or u8

Yes this should work with std::os::raw::c_char. cc: @MaisenbacherD

Agree as @maxwnewcomer already addressed this with https://github.com/openebs/mayastor/pull/1796. Thanks! :)


fix(typescript): fix type of component factories created from strings

What:
Fixes dom-tag component factories and also cleans up parameter hints for components created in this style.
Why:
When glamorous component factories are created from strings currently they incorrectly union all Dom Element interfaces.
How:
Extended the Glamorous interface with two new interfaces (DOMTagComponentFactory + SVGTagComponentFactory) which add overloads to the glamorous interface for component factories created with all dom-tag keys.
Checklist:

[ ] Documentation N/A
[x] Tests
[x] Ready to be merged
[x] Added myself to contributors table

Parameter hinting with correct dom-tag component factory typing:

Parameter hinting with current incorrect dom-tag component factory typing:

I'm likely to open a couple of additional PRs this afternoon based off this one which continue the effort started in https://github.com/paypal/glamorous/pull/301 to improve parameter hints.

Codecov Report

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

@@          Coverage Diff          @@
##           master   #310   +/-   ##
=====================================
  Coverage     100%   100%
=====================================
  Files          10     10
  Lines         170    170
  Branches       46     46
=====================================
  Hits          170    170

Continue to review full report at Codecov.

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


istioctl x envoy-stats --output prom-merged

Please provide a description of this PR:
Adds support for pulling Prometheus merged metrics via istioctl x envoy-stats --output prom-merged <pod_name>.<namespace>
https://github.com/istio/istio/issues/39454
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[X] User Experience
[ ] Developer Infrastructure

Please check any characteristics that apply to this pull request.

[ ] Does not have any user-facing changes. This may include CLI changes, API changes, behavior changes, performance improvements, etc.

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0f4c35628efc4fc066e8fbf7e4d087dd2fc4c032
link
true
/test lint_istio

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

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

Test name
Commit
Details
Required
Rerun command

lint_istio
0f4c35628efc4fc066e8fbf7e4d087dd2fc4c032
link
true
/test lint_istio

gencheck_istio
0f4c35628efc4fc066e8fbf7e4d087dd2fc4c032
link
true
/test gencheck_istio

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

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


Role-based requests

Currently users are able to create requests for all available topics. However, this is not favorable in every situation. Imagine a team connects with external partners. The external partners should not be able to create requests for every topic. There might just be some topics which are relevant for the external partners.
Preventing access to every topic helps to solve issue https://github.com/redlink-gmbh/smarti/issues/21 . We could focus on filters there.

@janrudolph should we move this issue to assistify?

Moved to https://github.com/assistify/Rocket.Chat/issues/61


kbfs public documents for 2 (or more) people

Hello Team,
try the following:
cd /keybase/public/<name>,<othername>
echo "some text" > test.txt

Ask othername to check if he sees this
Ask some other guy to check your public space
Is this a file that is public
Is this a file that is private
Should this be visible in /keybase/public/name
Should this be visible in /keybase/public/othername
Is this an expected behaviour

Hi @zeridon -- KBFS paths are global, so everyone sees the same path.  Therefore, if you put a file in /keybase/public/<name>,<othername> on your device, it will be visible in /keybase/public/<name>,<othername> on your friend's device as well.
Anything under /keybase/public can be read by anyone in the world.
If you want to share something privately with your friend, use /keybase/private/<name>,<othername>.  Does that answer your question?

Partially yes. I had the expectation that under public you can publish only under your prefix only. Might be good to explain in the docs that this is not the case

Have you read https://keybase.io/docs/kbfs/understanding_kbfs?

Thank you strib. That explains it quite nicely. I was not aware of this page. Thanks for pointing it out.


MergeSTR can now be run while trimming flanking alleles

Codecov Report

Merging #134 (bedc4a4) into develop (3245d26) will decrease coverage by 0.18%.
The diff coverage is 93.25%.

@@             Coverage Diff             @@
##           develop     #134      +/-   ##
===========================================
- Coverage    93.70%   93.51%   -0.19%
===========================================
  Files           17       17
  Lines         2778     2914     +136
===========================================
+ Hits          2603     2725     +122
- Misses         175      189      +14

Impacted Files
Coverage Δ

trtools/utils/tr_harmonizer.py
91.25% <86.20%> (-0.56%)
:arrow_down:

trtools/mergeSTR/mergeSTR.py
94.64% <94.44%> (-1.05%)
:arrow_down:

trtools/dumpSTR/dumpSTR.py
91.95% <100.00%> (+0.06%)
:arrow_up:

trtools/utils/mergeutils.py
93.25% <0.00%> (-1.13%)
:arrow_down:

Continue to review full report at Codecov.

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


Configurable human logger

The human logger should allow for a configuration struct which lets the developer hide things like the timestamp and file name. We could also allow for forcibly disabling colors through this config struct too.
package sloghuman

type Config struct {
    HideTimestamp bool
    HideFile bool
    ...
}

func MakeConfig(w io.Writer, c Config) slog.Logger {}

The lack of customization was intentional. When would you want to hide timestamps or location stamps?
Location stamps I could see being an IP leak but I would consider that a stretch and outweighed by the debugging benefits.

For example, if you wanted to output to a log file with full output and output to stderr with only the level, message and fields. This could be useful in a CLI app, because the timestamp and filename clutter up every log line.

This could be useful in a CLI app, because the timestamp and filename clutter up every log line.

slog is not a good choice for a CLI app. CLI messages are purely for humans and so log.Printf is likely much better.

That makes sense. Since this was a intentional design choice I'll close this issue.


Deprecation issue with the punycode module in your project

Hello,
I am encountering a deprecation issue with the punycode module in your project. The warning message is as follows:
(node:19880) [DEP0040] DeprecationWarning: The punycode module is deprecated. Please use a userland alternative instead.
Could you consider updating your project to use a more recent version of punycode (e.g., punycode@2.3.1)?
Thank you in advance for your help.
Best regards,
valorisa

Until this bug is fixed, you can import punycode into your app by adding this snippet to package.json . Solved the issue for me with Node 22 and Next.js 14.2
{   "dependencies": {     "punycode": "^2.3"   }, }

I just want to note that node-fetch doesn't depend on punycode.
The latest node-fetch version shouldn't use punycode at all, but 2.x depends on the outdated whatwg-url@5 that uses deprecated punycode module.
So, it should be enough to update whatwg-url in the 2.x branch.

Also, this is a duplicate of https://github.com/node-fetch/node-fetch/issues/1797


uploaded a group project about banks and objects

The objects are fine but they don't use any common methods like total outside both of them. I was hoping to see something like total: sum(dollars, cents).


Due to another issue (see https://github.com/rstudio/helm/issues/355), I've not been able to find out whether CUDA apps would work using the content images from Posit. In the event that they don't, I've prepared a Dockerfile based on NVIDIA's Dockerfile.
The only change I made was to replace:
FROM ubuntu:18.04 as base
with:
FROM rstudio/content-base:r4.1.0-py3.9.2-ubuntu1804 as base
in the hope that it would become an image that works on Posit Connect and can use GPU with the CUDA apps. See below for the full Dockerfile.
I'd be interested to know if this is how Posit team would do it, whether actually the base Posit content images already had CUDA support, or if you would do it differently.
Thank you!
Ben
FROM rstudio/content-base:r4.1.0-py3.9.2-ubuntu1804 as base

FROM base as base-amd64

ENV NVARCH x86_64

ENV NVIDIA_REQUIRE_CUDA "cuda>=11.4 brand=tesla,driver>=418,driver<419 brand=tesla,driver>=450,driver<451"
ENV NV_CUDA_CUDART_VERSION 11.4.148-1
ENV NV_CUDA_COMPAT_PACKAGE cuda-compat-11-4

FROM base as base-arm64

ENV NVARCH sbsa
ENV NVIDIA_REQUIRE_CUDA "cuda>=11.4"
ENV NV_CUDA_CUDART_VERSION 11.4.148-1

FROM base-${TARGETARCH}

ARG TARGETARCH

LABEL maintainer "NVIDIA CORPORATION<EMAIL_ADDRESS>
RUN apt-get update && apt-get install -y --no-install-recommends \
    gnupg2 curl ca-certificates && \
    curl -fsSL https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/${NVARCH}/3bf863cc.pub | apt-key add - && \
    echo "deb https://developer.download.nvidia.com/compute/cuda/repos/ubuntu1804/${NVARCH} /" > /etc/apt/sources.list.d/cuda.list && \
    apt-get purge --autoremove -y curl \
    && rm -rf /var/lib/apt/lists/*

ENV CUDA_VERSION 11.4.3

# For libraries in the cuda-compat-* package: https://docs.nvidia.com/cuda/eula/index.html#attachment-a
RUN apt-get update && apt-get install -y --no-install-recommends \
    cuda-cudart-11-4=${NV_CUDA_CUDART_VERSION} \
    ${NV_CUDA_COMPAT_PACKAGE} \
    && rm -rf /var/lib/apt/lists/*

# Required for nvidia-docker v1
RUN echo "/usr/local/nvidia/lib" >> /etc/ld.so.conf.d/nvidia.conf \
    && echo "/usr/local/nvidia/lib64" >> /etc/ld.so.conf.d/nvidia.conf

ENV PATH /usr/local/nvidia/bin:/usr/local/cuda/bin:${PATH}
ENV LD_LIBRARY_PATH /usr/local/nvidia/lib:/usr/local/nvidia/lib64

COPY NGC-DL-CONTAINER-LICENSE /

# nvidia-container-runtime
ENV NVIDIA_VISIBLE_DEVICES all
ENV NVIDIA_DRIVER_CAPABILITIES compute,utility

It looks like this is certainly possible to support, but might be hard. I think this discussion might belong over at rstudio-docker-products, so I'll move this issue after posting.
I say that this might be hard because it introduces another variable space into an already pretty large space, and also because of image size concerns. To proceed with supporting this, I think it would probably be wise to add an image, say content-base-cuda, with the same build matrix as content-base, but with an additional cuda specifier in the tag. I'm also not sure what we'd be able to do as far as testing goes, since github actions does not have GPUs available.
One concern I have is that it is already difficult to propagate changes from base layers up to other layers. This new image wouldn't fundamentally change the issue, but it would make one more set of build files to update when the base changes. There are some related issues at:
https://github.com/rstudio/rstudio-docker-products/issues/506
https://github.com/rstudio/rstudio-docker-products/issues/505
https://github.com/rstudio/rstudio-docker-products/issues/504
Hopefully this helps clarify things. The fastest way forward is certainly for you to run custom images yourself, as documented at https://docs.posit.co/helm/rstudio-connect/kubernetes-howto/appendices/content_images.html#custom-images. However, it would be nice to make GPU support easier for everyone.


Wip fix ci zhouyuan

What changes were proposed in this pull request?
(Please fill in changes proposed in this fix)
How was this patch tested?
(Please explain how this patch was tested. E.g. unit tests, integration tests, manual tests)
(If this patch involves UI changes, please attach a screenshot; otherwise, remove this)

@zhouyuan
You can refer to this pr.

@zhouyuan
You can refer to this PR.


Release 4.3.4

galaxy_ng Release PR: https://github.com/ansible/galaxy_ng/pull/1193
AAH-396: Fixed content overflow in ImportConsole component
API PRs
UI PRs

(technically this just removes the backported CHANGES/ entries, as we have no changelog nor version info in 4.3 UI)


Tenshi.moe downloading problem

Unable to download anime from tenshi.moe extension. Downloads failing every time.

Try checking via webview if you can visit and watch the anime from in-app browser. If not then the problem is with the source, not the plugin. But well, it works fine for me.


PMTK3 demo or user guide is needed!!

Hi all,
I would like to use PMTK in my project. however, couldn't find a user guide for beginners.
The book demo in this link https://github.com/probml/pmtk3/wiki/Demos should have instructions and explanations but unfortunately when I click on any of the subtitles a message appears stating that the URL is not found!
The same thing applies when I try viewing them from this link: http://code.google.com/p/pmtk3
Is there any user guide or instructions on how to use the toolbox!!
many thanks,
Shaima

Seems like the links to the docs are broken.  Does anyone know where to download them or how to rebuild them?


"gh-pages -d build"   failed

I tried to  deploy  project on github  pages,  but failed, I am the way that "create-react-app" offered .
errors log below
14 verbose lifecycle<EMAIL_ADDRESS>CWD: D:\webstormproject\reactmusic
15 silly lifecycle<EMAIL_ADDRESS>Args: [ '/d /s /c', 'gh-pages -d build' ]
16 silly lifecycle<EMAIL_ADDRESS>Returned: code: 1  signal: null
17 info lifecycle<EMAIL_ADDRESS>Failed to exec deploy script
18 verbose stack Error<EMAIL_ADDRESS>deploy: gh-pages -d build
18 verbose stack Exit status 1
18 verbose stack     at EventEmitter. (D:\software install position\nodejs\node_modules\npm\lib\utils\lifecycle.js:255:16)
18 verbose stack     at emitTwo (events.js:106:13)
18 verbose stack     at EventEmitter.emit (events.js:191:7)
18 verbose stack     at ChildProcess. (D:\software install position\nodejs\node_modules\npm\lib\utils\spawn.js:40:14)
18 verbose stack     at emitTwo (events.js:106:13)
18 verbose stack     at ChildProcess.emit (events.js:191:7)
18 verbose stack     at maybeClose (internal/child_process.js:886:16)
18 verbose stack     at Process.ChildProcess._handle.onexit (internal/child_process.js:226:5)
19 verbose pkgid<EMAIL_ADDRESS>20 verbose cwd D:\webstormproject\reactmusic
21 error Windows_NT 10.0.14393

We'll need more information to help you, but I have a feeling this isn't a problem with CRA.
Please open a new issue with the issue template filled out if you'd like some help!

I'm having this problem too, what was the solution?


ui: self curation - editing drawer

ref: cern-sis/issues-inspire #237

thank you @karolina-siemieniuk-morawska! @michamos is the wording in the drawer ok for you?

@karolina-siemieniuk-morawska we on "Connect" click we should close the drawer, similar to what we do on conference assign :)

thank you @karolina-siemieniuk-morawska! @michamos is the wording in the drawer and button ok for you?

I would change the wording in the drawer to Find the correct reference:


Save composer.lock in the repository

Allows faster dev install and ensures everyone is developing with the same versions of project dependencies. Has no effect on which versions are used when this library is a dependency of something else.

Caused issues with travis - maybe better to leave this alone for now.


Profiler: Failed to start session: Object reference not set to an instance of an object.

20210528T084746.zip

Azure Data Studio Version:
Version: 1.29.0 (system setup)
Commit: 0f5cfdc2c8c2433028842e16dc5ac1a65da24292
Date: 2021-05-15T01:12:11.112Z
VS Code: 1.53.0
Electron: 11.2.2
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

Steps to Reproduce:

Connect to a server
Press "alt+P"
Press "start"

now this error occurs:
Failed to start session: Object reference not set to an instance of an object.
Logs are attached

20210531T081848.zip
console.log

@bart-coppens From the above message, it appears that the issue was resolved (just not closed). I am closing this issue for now. You can open another issue if you hit some other problems with Profiler. Thanks!


remove 'Disconnect' when not connected

There may be a bug in wireless_interface_state or you made a design choice. The menu option "Disconnect" appears when you are connected, but also when you are disconnected. It would be nice if it would disappear when you are already disconnected.

I was unable to reproduce it.Could you please confirm that you are on the most recent commit or that you are truly disconnected?You can check the status, if you see wifi_name~ip_adress, it means you are not.

I can confirm that I am running your latest code, and that I am truly disconnected. If I run "nmcli device status", it reports disconnected.
On a side note, I have modified your code for my own use. If you are interested in receiving some suggestions, I could post them here or send them another way. Let me know.

I will be closing this issue because  you modified the code and I can't figure out why this is happening, but I'm always trying to add new features or make improvements.You may contact me at<EMAIL_ADDRESS>

Oh, I think you misunderstood. I have the issue with your unmodified code. I also am running code I modified, but that is not related.

You are correct.I looked more and discovered that this happened when I had multiple wifi devices connected. Can you replace [grep ${WIRELESS_INTERFACES[WLAN_INT]}] with [grep "^${WIRELESS_INTERFACES[WLAN_INT]}."] and tell me if this fixed it.

The fix you proposed works. Thanks.


0 artifacts in sentry after "File upload complete"

Environment
<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Steps to Reproduce
I configured sentry webpack plugin following the docs.

And ran build, showed "File upload complete" and "Source Map Upload Report".

Expected Result
I thought source maps were uploaded.
Actual Result
But "There are no artifacts in this archive." in sentry.

Please upgrade to the latest self-hosted versions.
Our docs show compatibility requirements: https://docs.sentry.io/platforms/javascript/sourcemaps/troubleshooting_js/


[DNM] Fix reference to latest nightly build yaml

looks like it was renamed from release.yaml to build.yaml

we will also need a third_party/config/build/clusterrole.yaml file to do the builds

we also need a new version of istio-riff-knative-serving-v0-3-0-patch.yaml for 0.4.0 @scothis

Superseded by #1116


Codesign succeeds but triggers "WARNING: Code sign failed; please retry manually" (also notarization fails silently)

[ x] I have read the contribution documentation for this project.
[ x] I agree to follow the code of conduct that this project follows, as appropriate.
[ x] I have searched the issue tracker for a bug that matches the one I want to file, without success.

Issue Details
Using --osx-sign triggers a signing failed warning but codesign -dv on the app indicates the the app was in fact signed. This error also seems to stop the notarization process as using the CLI arguments as per the documentation results in no notarization process (and there is no concise documentation or example of how to use this feature correctly).
The npm command i am using is the following:
"NODE_ENV=production DEBUG=electron-packager electron-packager . --out=build --icon=[my-iconpath] --prune=true --hardenedRuntime --osx-sign --osx-sign.identity='Developer ID Application: [my-id]' --osx-sign.entitlements='./build/entitlements/entitlements.plist' --osx-notarize --osx-notarize.appleId='[my-appleId]' --osx-notarize.appleIdPassword='[my-password]' --overwrite --app-bundle-id=[my-bundleid]"

Electron Packager Version:
15.1.0
Electron Version:
11.0.3
Operating System:
macOS 10.15.7

Expected Behavior
Output indicates code signing was successful and begins notarization process.
Actual Behavior
electron-packager outputs an error about "WARNING: Code sign failed; please retry manually [...] rejected source=Unnotarized Developer ID" (which as far as I can tell doesn't make sense as apps are notarized not developer ID's..). Then the --osx-notarize arguments seem to fail silently as there is no further output and it is unclear whether --osx-notarize has done anything.
Please let me know if there is an error or misunderstanding in my use of these CLI arguments, however I have done my best to read the minimal documentation of these features, and gauge what the expected output should be.
Additional Information
console output (removed app information with []):
electron-packager Running electron-osx-sign with the options {"0":true,"1":{"identity":"Developer ID Application: [my-id]"},"2":{"entitlements":"./build/entitlements/entitlements.plist"},"platform":"darwin","app":"/var/folders/j0/sw3l2jkn2_qgzwrvbsgp8ldh0000gn/T/electron-packager/darwin-x64/[my-app]-x64/[my-app].app","version":"11.0.3"} +12ms
WARNING: Code sign failed; please retry manually. Error: Command failed: spctl --assess --type execute --verbose --ignore-cache --no-cache /var/folders/j0/sw3l2jkn2_qgzwrvbsgp8ldh0000gn/T/electron-packager/darwin-x64/[my-app]-darwin-x64/[my-app].app
/var/folders/j0/sw3l2jkn2_qgzwrvbsgp8ldh0000gn/T/electron-packager/darwin-x64/[my-app]-darwin-x64/[my-app].app: rejected
source=Unnotarized Developer ID

output of codesign -dv on the app:
Executable=[my-path-to-app]
Identifier=[my-app-bundle-id]
Format=app bundle with Mach-O thin (x86_64)
CodeDirectory v=20200 size=1785 flags=0x0(none) hashes=50+3 location=embedded
Signature size=9052
Timestamp=10 Dec 2020 at 13:18:42
Info.plist entries=25
TeamIdentifier=[my-team-id]
Sealed Resources version=2 rules=13 files=13514
Internal requirements count=1 size=188

I have tried several permutations of arguments for the CLI command and now have a message about notarization failing. However it says no appleId was provided when i have provided it as described in the docs. Is there any example of how to use the notarization commands from the command line as it seems impossible to sign and notarize an app with a single CLI command. (if this is impossible it should be made clear in the docs).
WARNING: Failed validation, notarization will not run: No authentication properties provided (e.g. appleId, appleApiKey)

CLI Command:
"pack:macos": "NODE_ENV=production DEBUG=electron-packager electron-packager . --out=build --icon=build/icons/[app].icns --prune=true --osx-sign.hardenedRuntime=true --osx-sign.identity='Developer ID Application: Felix Faire ([my-id])' --osx-sign.entitlements-inherit=./build/entitlements/entitlements.plist --osx-notarize.appleId='[my-apple-id]' --osx-notarize.appleIdPassword='[app-specific-password]' --overwrite --app-bundle-id=[bundle-id]",

If anyone else is having issues with notarization and electron-packager i'd recommend just following this process manually.
http://www.zarkonnen.com/signing_notarizing_catalina

I don't consider this issue closed. The suggested actions and arguments for signing and notarization with electron-packager did not work and i had to use a manual workaround. I used exactly the same apple ids, app-specific-passwords etc with altool and codesign so I presume there is still a bug in electron-packager or electron-notarize resulting in these errors.

Unfortunately, due to the limited amount of time of the maintainers and the limited amount of information present in this issue, we cannot help debug your app at this time. Instead, consider using one of the community forums, as there are more people there available to answer questions.

I understand, and am grateful for all open source efforts on electron-packager and other tools. My application doesn't need debugging, it signed and notarized fine with the apple tools. However I wasted a lot of time trying to get the advertised signing and notarization functionality working with electron-packager, so there should probably be an open issue that the CLI for signing and notarization workflow has problems.

The Electron docs provide a working API example of code signing with Electron Packager which should be fairly straightforward to convert to CLI flags (although I would recommend given the complexity of code signing/notarization, it's better to just write a Node script than try to deal with all of the CLI flags in one very long line).
If you're having an issue with notarization, it's probably better to file an issue with electron-notarize as for the most part, Electron Packager forwards the configuration directly to that module.

That link you showed was my starting point for these required arguments.
"I would recommend given the complexity of code signing/notarization, it's better to just write a Node script than try to deal with all of the CLI flags in one very long line"
A note like this in the docs would have been invaluable at the start of this process. I am primarily a native / graphics developer so less comfortable with the many different ways to get node scripts to do what i need. I will avoid the cli commands approach for more complex tasks like this in the future.
Thanks for your input in any case.


AFHTTPSession manager caching If-Modified-Since

Hi there! I'm totally stuck with caching requests using AF 3.0- absolutely no info in wiki no info in google, no articles... i use Obj-C.
I have a web- service it gives me Last-Modified header for each request, when i send the same request i should add If-Modified-Since with the date from Last-Modified. If no changes i got status code = 304, if any changes- 200 with the corresponding responseObject.
I have been playing with cachingPolicies and NSURLCache subclasses- but no effect( I figured out terrible custom solution to provide needed logic.
But i'm very interested exactly which caching mechanism AFNetworking > 3.0 supports. I assume that it can only support caching with max- age headers.
If u solved the same issue i would appreciate ur comment very much.

What is your issue here exactly?

@skyline75489 setDataTaskWillCacheResponseBlock calls each time, even if I get the HTTP status code 304. As far as I understand it should be called only when I get the status code 200 not 304

AFNetworking does nothing custom here in regards to caching. It uses NSURLSession and NSURLCache by default, and uses the OS caching behavior. You have the hooks exposed to do whatever custom caching you would like to do.


Exclude _build in master branch (but obviously not in gh-pages branch)

...as simple as adding to .gitignore:
_build/**

?

Yes, gitignore does not affect https://github.com/c-w/ghp-import functionality.


HTTP Basic Auth implementation

This PR is based on  #1407 . I have picked up the implementation from #1407  PR and added HTTPServer changes which are required for testing this functionality.
@pushkarnk please review

@swift-ci please test

@pushkarnk  As of now the code is crashing when the header "WWW-Authenticate is not present.So, we can handle this in two ways either throwing the fatalError with a message which will be no different from the earlier crash but with a proper message or invoking the urlProtocol(`protocol`, didFailWithError: delegate . I have implemented the latter way . However the error message relevant to this scenario seems to be unavailable in URLError class. I am not sure whether I can add new errors to this class . Hence I have set the  error code as NSURLErrorUserAuthenticationRequired . Please let me know  if this is acceptable.

@saiHemak Please correct the typo in the commit message as well. Thanks.

@swift-ci please test

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please test and merge

@swift-ci please test and merge


Compiler warnings on High Sierra

I don't recall seeing these before, but I see them as of 7683f13865d04103213a0729.  They don't occur in plain Vim.
mbyte.c:4795:1: warning: unused function 'call_imactivatefunc' [-Wunused-function]
call_imactivatefunc(int active)
^
mbyte.c:4807:1: warning: unused function 'call_imstatusfunc' [-Wunused-function]
call_imstatusfunc(void)
^

fixed 594349b5e7a2512abc7afce1b3c032f2cc298a53


Updating balloon.sys to 0.1.96 results in BSOD crash

I updated my Win 2008R2 system's balloon.sys to 0.1.96 an immediately got a BSOD crash in balloon.sys.  STOP code 0x0000007e and on all subsequent boots.  Disabling the memory balloon device in libvirt for the guest allowed it to boot.
Host is Scientific Linux 6.6, qemu-kvm-<IP_ADDRESS>-2.448.el6_6.4.x86_64.

Hi,
According to Gal (engineer who maintains balloon driver) there were several bugs fixed in the latest build. Please check it - https://fedorapeople.org/groups/virt/virtio-win/direct-downloads/archive-virtio/virtio-win-0.1.105-1/
Thanks,
Yan.

That appears to be working better - no crashes.  Haven't tested resizing memory though.  Thanks.


Update interface.py for Bolt lateral and stop and go

Improve Bolt tuning with better lateral (still a work in progress) and stop and go longitudinal (thanks to Felger).
Not sure if gasMaxBP and gasMaxV are still parameters. They were important for the specific acceleration profile of the Bolt. They might be unnecessary but this requires further research

Thanks @darknight111


can't find show_segmentation_on_image

Thank you so much for your excellent work and sharing it with the community.
I was trying to run your notebook but noticed show_segmentation_on_image  function does not exist anywhere in your repo.
Just wanted to point that out :)

Hi, thanks for pointing out this.
Fixed and pushed


add CI

Would you be amenable to adding CI to this project that runs tests automatically?
Additionally, would you be willing to be explicit about the minimum version of Rust that this crate supports? (e.g., By adding an explicit Rust version to the CI config.)

Sure, those are both great things to do; I just haven't gotten to them yet (PRs welcome!). It's lower priority for me than wrapping up the long-suffering open PRs (pending me having the IRL time availability), but definitely a good idea.
This library isn't particularly demanding about needing the latest rust features (though I plan on adding SIMD support), but I also don't want to end up with a huge test matrix of versions. Is "latest & previous stable" enough? Or even just "latest stable"?

IMO, libraries that are intended to be used in a wide variety of applications should be fairly conservative about their minimum supported Rust version. At this point, I think the trend is that you should test at least a specific pinned version of Rust and not an automatically moving target like stable. The key point here is that it requires a conscious and deliberate change to the CI configuration when the code requires a newer version of Rust. If you don't pin a specific Rust version, then it basically requires users of your crate to perform a research task to figure it out, if they care. (I am someone who cares, because I want to be able to declare in my project's README that you need "at least Rust 1.x to be able to compile this project.")
There are separate questions about whether increasing the minimum supported Rust version is also a semver incompatible change, but there is no widespread consensus on this, so I'm not advocating any specific policy on that front. Mostly, I'm just asking for it to be easily discoverable which version of Rust this crate targets.
I will see about submitting a PR that adds a basic CI config, but you will need to actually enable it on your end, e.g., via Travis CI. Have you done something like that before, or would you like me to help you do it?

I see your point. Is there data available about adoption of new Rust toolchain versions so library authors can make such choices without being quite as much in the dark?
I've avoided Travis in favor of other CI platforms for my own projects because I reflexively avoid things that enforce a technical monoculture (in Travis's case, it's GitHub-only) but given that this project is firmly ensconced in GitHub-land, Travis will do fine.

Is there data available about adoption of new Rust toolchain versions so library authors can make such choices without being quite as much in the dark?

No. Everyone is winging it. Once Rust gets LTS releases, I suspect there will be a stronger push to unify around a specific Rust version.
If you just want to pick something, I selfishly propose 1.23, since it's what ripgrep is targeting, and I know that this crate compiles on 1.23. :-)

I see what you did there. ;) 1.23 sounds fine.
I have a variety of breaking changes brewing in the back of my head and I'll probably bump the version at that time but that will be months from now.


Pytests not running within Docker

Re-opening after reverting changes from main branch.

Closing as this will be tracked on https://github.com/GeoscienceAustralia/nrt-predict


docs: fix incorrect date creation

I think the creation of date objects in the documentation is wrong, because to my knowledge it should be in the order of year, month, day.
Huge shoutout btw for creating this solution, I really enjoy using it!

This pull request also relates with this issue I created also regarding the date objects:
https://github.com/unjs/unhead/issues/384

Good catch, thanks for the fix!


The documentation build failed because downloading the test data was too slow

The documentation build failed because downloading the test data was too slow. Downloading several hundred megabytes of data to build the documentation may not be the fastest solution. Maybe we could build the documentation with smaller test data that we put in a GitHub repository?
Originally posted by @bouweandela in https://github.com/CMIP-REF/cmip-ref/issues/40#issuecomment-2551505646

Perhaps we pick some test data, decimate it and then add it to GitHub. Having a wider set of available data (in terms of experiments, variables and models) is preferable over higher spatial resolution.
So the plan would be to make a separate repo with some scripts to download/decimate the selected data and the decimated data. Then use git submodules to pin a particular commit for our test suite?
Any other ideas @mikapfl?

Your plan sounds solid. Probably not entirely necessary to use a separate repository — I think if you can keep the test data to less than 10 MiB, it is defensible to just put it into this repo.

I once did something similar for ESMValTool, maybe we could use that for inspiration: ESMValTool_sample_data.
How about storing the data in a separate repository and using pooch to retrieve it? That avoids the hassle of having git submodules while still keeping the data separate from the code.


Migrate from custom store implementation to bbolt

https://github.com/etcd-io/bbolt

Decided to stick with a simple map as a store. However, make it thread-safe and get rid of interval-based flushes.

Decided to stick with a simple map as a store. However, make it thread-safe and get rid of interval-based flushes.


ModuleNotFoundError: No module named 'pymongo'

Thanks for making this publicly available.
I was just trying it out and I get the following error message

ModuleNotFoundError: No module named 'pymongo'

when running
conda env create -f environment.yml
source activate nsf
python experiments/images.py with experiments/image_configs/imagenet-64-8bit.json

is this user error on my part, or should pymongo be in the environment.yml?

Yes, pymongo should indeed be in the environment.yml. I've added it now. Thanks for letting us know!


Turn logger into a request monitor

Logger currently stores certain messages when requesting and receiving data.
It might be more useful to show currently open requests and their result state (success, error, warning) + filter the states.

We do actually need a feature that (on demand) logs all REST interactions. Can we provide a turn on / turn off / view logs button?

see #89


[main] Upgrade to latest dependencies

Cron -knative-prow-robot
/cc knative-sandbox/client-writers
/assign knative-sandbox/client-writers
Produced by: knative-sandbox/knobots/actions/update-deps
Details:
bumping knative.dev/client 1bf6c12...28a340c:
  > 28a340c Prepare changelog and version for 0.25 release (# 1423)
  > ce790b4 Adding --tls option to domain create command (# 1419)
  > 4691210 Deprecate `lookup-path` option and updated relevant documentation (# 1422)
  > f8a8284 look up plugins on PATH by default (# 1412)
  > fe9edcc upgrade to latest dependencies (# 1417)
  > fc7e876 Add support for multi-containers (# 1382)

/lgtm
/approve


Three bug fixes

Fix #2927: Provide better error message when machine is unreachable
Fix #2917: Remote HTTP server messages need to be fixed
Fix #2790: Simplifying the connection switching experience (test connection button hidden)

👍


Create virtual SDO server

I want to create a virtual SDO server using CANopenSocket to communicate with my SDO client device.
Is there an example how to do that and use specific eds files related to the server that I want to create ?

duplicate


[FLINK-2034] [docs]  Add vision and roadmap for ML library to docs

We should have a document describing the vision of the Machine Learning library in Flink and an up to date roadmap.
This PR provides that, and the text can also be used in the website.

Pinging @tillrohrmann to take a look.

Thank you for writing this. Finally I get a better understanding of the overall status of the FlinkML stuff ;)
+1 to merge.

Really nice text @thvasilo. I think it's a great introduction.
But I also think that we should change a little bit the outline of our starting page. IMO, it should be governed by what a user expects from such a starting site. If I were a new user, I would expect something along the lines of:

Short introduction (your text is good if we condense the last paragraphs)
List of supported algorithms
Getting started (what dependencies to include etc.)
Tutorial/Example use case
Roadmap

I'm not so sure whether the list of algorithms should be number 2 but that's something to discuss. What do you think?

Yup, as I mentioned in my line comment above a layout like the one you suggest is better for the index of library documentation. So how about this layout:

Short introduction (with links to vision and roadmap)
Getting started (what dependencies to include etc.)
List of supported algorithms
Small example with link to tutorial/quickstart section

How to contribute

Added all the changes we discussed, this should be good to merge now.

LGTM. Will merge it.


Implementation for start/stopLimitedRetry:AzureInstanceConnector

See detailed description in the commit message.
https://jira.cloudera.com/browse/CB-18055#
The start/stop method accepts a list of virtual machines that need to be started/stopped within the timebound specified. Asynchronous calls are made to start/stop the virtual machines along with passing a specific timeout value as one of the parameter.
For each asynchronous call, the behavior of the code is such that if time elapses before the completion of job then we update the status of instance as UNKNOWN, else if there is some other error then we update the status of instance as FAILED and if the job completes within the specified time then we update the instance status as STARTED. Finally, the method returns the statuses of all the virtual machines.

Can one of the admins verify this patch?


Fix deleted preprints

Purpose
A number of preprints with deleted nodes were resurrected
by the NPD. This is because the NPD migration
only set Preprint.deleted for preprints with nodes
that had a project_deleted log. Components will not have
this log, so preprints attached to components will not
have their deleted date set.
Changes
Add a migration that sets deleted to unix time 0 (1970-01-01)
for all preprints created before the NPD migration that are
attached to deleted nodes.
Also, modify tests to prevent probabilistic failures.
Ticket
https://openscience.atlassian.net/browse/PLAT-1276

Was confused that a follow-up migration was needed to add the permissions since that was done here, but it looks like the original had an extra period.


chore(package): update npm-pkgbuild to version 6.11.4

Coverage remained the same at 87.261% when pulling 56d8b7ce91712d697f51535093669a1d77fc642f on greenkeeper/npm-pkgbuild-6.11.4 into 251fdcf49e51b0688e802b7c0b37c80a57369e5d on master.


Closes #139

Decline. Implement proper curator client close which must differentiate between internal and external object.


ask for save before quit

Need to track if changes were made

trains should have a "home" position that has to be actively set, will not be changed by running trains around. Is that the position trains have in "edit" mode?


Improved logging for the Profiler.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
10 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-1.0%) to 92.707%

Files with Coverage Reduction
New Missed Lines
%

src/dlio_profiler/brahma/posix.cpp
10
89.54%

Totals

Change from base Build<PHONE_NUMBER>:
-1.0%

Covered Lines:
928

Relevant Lines:
1001

💛  - Coveralls


Update GKE deployment steps: this is a working version on a brand new GCP project

Set the necessary and minimal IAM roles for service account.
Add resource project to config.yaml, so it will be easy to migrate later.
Separate into multiple small script for incremental update.

thanks for review!


fix(nvmeadm): remove unwrap from disconnect

This removes an unwrap which keeps failing the e2e pipeline.