text:
The component must be tolerant to certificate chains without a newline

If the certificate chain openshift4-ingress/wildcard-certificate/cert does not contain a newline, the deployment on the OpenShift 4 cluster fails, because chain and key are concatenated  -----END CERTIFICATE----------BEGIN PRIVATE KEY-----,.
Steps to Reproduce the Problem

Inject a certificate chain WITHOUT a newline at the end -----END CERTIFICATE-----

    secrets:
      customer-apps-tls:
        stringData:
          tls.crt: ?{vaultkv:${cluster:tenant}/${cluster:name}/openshift4-ingress/wildcard-certificate/cert}

Check the OpenShift cluster router secrets

oc -n openshift-ingress get secret router-apps-tls -o jsonpath="{.data.tls\.crt}" | base64 -d
oc -n openshift-authentication get secret v4-0-config-system-router-certs -o jsonpath="{.data.apps\.cluster\.domain\.ch}" | base64 -d | grep "BEGIN PRIVATE KEY"

Actual Behavior
Without a newline this result in -----END CERTIFICATE----------BEGIN PRIVATE KEY-----, which causes several base components not starting or even crashing.
Expected Behavior
The component must either check for a newline at the end of the injected certificate chain and add one if not there.
Or potentially just add always a newline to the chain (untested).
Test the certificate chain ahead could be an other solution to it, but would potentially cause downtime.
It's not acceptable that the user has to check for a newline, because it is high likely this is happening very often and we can't ensure component users read the documentation at such low level.

Why does it end up in -----END CERTIFICATE----------BEGIN PRIVATE KEY----- in the first place? Do you configure a secret with both tls.crt and tls.key? (You aren't supposed to put the private key into tls.crt field) see https://kubernetes.io/docs/concepts/configuration/secret/#tls-secrets

It's not the case that the key is added to the tls.crt but this happens on the cluster via the operators.
$ oc -n openshift-authentication get secret v4-0-config-system-router-certs -o yaml
apiVersion: v1
data:
  apps.cluster.cluster.ch: LS0...
kind: Secret
metadata:
...
  name: v4-0-config-system-router-certs
  namespace: openshift-authentication
...
type: Opaque

ah, that's how it works...
I'm not sure the component can help here. The secret value is retrieved when ArgoCD deploys the manifest. The component compilation can't retrieve the value from Vault, add a newline and update it back in Vault...

The component must either check for a newline at the end of the injected certificate chain and add one if not there.

Please note that it's impossible for the component to do that, as either the certificate or key may be provided from Vault and the component can't check values stored in Vault by design.
The proposed solution in #32 unconditionally appends a newline to all present fields in the secrets, a quick manual test shows that extra newlines in the concatenated data don't matter to openshift-authentication.

authors: ccremer megian simu


text:
Consider timezones

It's not necessarily the case that the server's timezone is the timezone the user wants to use when deriving a date from a post's full creation timestamp. There should be some consideration around which timezone to use for the purposes of formatting the creation date.
For instance, if the server is on UTC and it's Feb 2nd at 3am, someone hitting publish in EST might wish for the date to be shown as Feb 1st. Unfortunately what isn't obvious here is what happens when this timezone changes. Do previous posts that might jump date lines get changed over?

YAGNI.

source: gharchive/issue

repo: aprescott/serif

license: mit

license_type: permissive

license_source: bigquery


text:
Amazing Obsidian Plugin - one of the best! ❤

(Discussions Tab not activated yet; when activated, move this "Issue" there)
Super Easy to use
While the documentation on the README page seems a bit daunting, this plugin is actually really very simple to use.
Obsidian writing now similar to MS Word

Using a simple MS Word macro (found on YouTube), I got the list of AutoCorrect word options in my MS Word.
Copied them into Excel
Using Excel's simple Concatenate, I converted those 1000 words into the requisite format and pasted this long list into the Plugin settings.
And that's it!
Now, I can use the power of MS Word in Obsidian.

Highly customizable
I even added some customized words based on the chat language, e.g., by simply typing whr r u, I get where are you. (did this by adding these lines in the settings
' u |' -> ' you |'
' r |' -> ' are |'

The best thing about this Plugin is that you are in total control. E.g., by simply typing u, if you came, then it would not be good. But, if you are adding a space, you can be absolutely sure that you want to treat u like a whole word, and so convert it. Also, converting every small i to I is not desirable, because it will convert even this to thIs. So, you can add a rule that
' i |' -> ' I |'

Also, by simply placing | anywhere we want, we can get the cursor anywhere we want. This is so easy to understand even for non-coders.
'==|' -> '==|==' #highlight text

Here the mark-up is added, and the cursor is placed in between the mark-up for to you continue writing seamlessly, without needing to go manually back to the middle.
Improved typing speed
How Google keyboard on Android mobile handles our errors and makes our typing speed so so fast just by swiping here and there, similarly you can type absolutely any typo on now Desktop now and be rest assured that this plugin will take care of all the errors. Just invest some time in knowing your common typo, and add them to the Plugin.
This plugin have added another amazing cherry on the cake of Obsidian.
Stay Blessed ❤

Whoa, I am so glad the Plugin can help you! I didn't even think that the Plugin can be used in a way like AutoCorrect, that's cool.
And I feel your post is more clear and readable, maybe there should be fewer tech details and more user cases in the README…… If you are interested, please feel free to create a PR for the README ☺ .
Another little question, did you notice an obvious CPU usage increase working with those 1000+ rules? If so I probably need to do some optimization. The discussion tab is enabled now, maybe you could share your auto-correct settings there, then I can have a test on my machine.
Thanks for your feedback, appreciate it~

I didn't notice the CPU usage, but yes, adding thousands of words made the Obsidian typing a bit janky, so yesterday, I trimmed them to only my own custom Autocorrect list (50--100), instead of having the huge default MS Word list. This has made the typing more predictable and still super fast.
So, yes, as of now, adding 1000+ list is not advisable unless optimization is done in the plugin. You are most welcome.

Hi @ManasMadrecha, I have optimized the lookup process for a rule in version 0.2.1, theoretically, the experience should be significantly improved.  So you can give it a try, let me know if any problems

authors: ManasMadrecha aptend

repo: aptend/typing-transformer-obsidian

license: MIT

license_source: github-api


text:
Salute & Query

Hello, congratulate for your work in AAAI 2022, and could you offer the code of "STDEN: Towards Physics-guided Neural Networks for Traffic Flow Prediction" because i want to use the newest state-of-art work to be the baseline of the future work. I will appreciate it very much if it can be offered.

Sorry for the late reply, we are collating the code and will get back to you with the link after the open source. You can follow the first author of the paper Echo-Ji .


text:
add faq in tindog website

Title and Issue number

Title :add faq in tindog website
Issue No. :#1013
Code Stack : htm css
Close #1013

Video (mandatory)

https://github.com/user-attachments/assets/4e134363-9596-4c73-bf72-6694dd874650
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md
[X] I have gone through the  contributing.md file before contributing

Additional context (Mandatory )
Are you contributing under any Open-source programme?

[X] I'm a GSSOC'24 contributor
[ ] I'm a SSOC'24 contributor

@apu52 please review once and merge my pr

@apu52 done

source: gharchive/pull-request


text:
BUG : broken links in footer of checkout page

Describe the bug

broken links in footer of checkout page
Expected behavior

must be linked with their respective  pages
Screenshots (Mandatory)

Additional Context (Mandatory )
Are you contributing under any open-source program ?

jwoc'24

@PranavBarthwal  Can you assign this ticket to me, please

@PranavBarthwal Can you assign this ticket to me, please

This issue is already assigned. You can make a new issue on which you want to work on after going through the existing issues


text:
feat: add fastly/cli

https://github.com/aquaproj/aqua-registry/pull/5387 fastly/cli: A CLI for interacting with the Fastly platform
$ aqua g -i fastly/cli

Thank you for your contribution!

Released. https://github.com/aquaproj/aqua-registry/releases/tag/v3.26.0

authors: ponkio-o suzuki-shunsuke

repo: aquaproj/aqua-registry


text:
Update README.md

Adding simple numbers to make the install documentation easier

Hi @franciosi
Thanks for your contribution!
However, I don't see how adding numbers in the readme makes difference in understanding it better..
I encourage you to add a contribution in the code :)

Hi @franciosi
Thanks for your contribution!
However, I don't see how adding numbers in the readme makes difference in understanding it better..
I encourage you to add a contribution in the code :)

Hi @danielsagi
OK, it was just a simple improve. This is how normal we do with documentation, like https://www.freebsd.org/doc/handbook/. About code, yes, I plan to do it, as soon as I have more time. Very much involved with FOSS documentation and translations for now.

Hi @danielsagi
OK, it was just a simple improve. This is how normal we do with documentation, like https://www.freebsd.org/doc/handbook/. About code, yes, I plan to do it, as soon as I have more time. Very much involved with FOSS documentation and translations for now.

authors: danielsagi franciosi

repo: aquasecurity/kube-hunter


text:
chore: release v1.0.8

Cutting a separate release for v1.0.8

:tada: This PR is included in version 1.0.8 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.1.0-alpha.2 :tada:
The release is available on:

npm package (@alpha dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

repo: ar-io/ar-io-sdk


text:
Rate exceeded error

When trying to open any abstract, I'm getting a "Rate exceeded." error. I am accessing without VPN from the university network with IP 130.82.170.100. Can you white-list our IP please? Or is there another way to avoid this error?

This was due to high server load during this week, should be better now.

authors: dginev tomhsg


text:
Display of ohms when current set to zero

Sorry for blurrycam, but this is how it looks if display is set tho show ohms and current is set to zero. Probably because of noise in current measurement it jumps between no resistance and something small.

I already posted nearly the same bug plus some others related to the Ohms readout. See #72

Duplicate of #72

authors: knarfS raivisr

repo: arachnidlabs/reload-pro


text:
Odd enum value in SoftwareSubclass

The SoftwareSubclass has the enum value "Smail" which has not a defined SoftwareSubclass element.
This is the only enum value without an corresponding element.

"Smail" will be removed from definition list

authors: fotto p-a-x

repo: arago/MARS-Schema


text:
Add security audits

Closes #484
Small typo fix
Remove reference to deleted documentation

@sohkai yes please go ahead. Having links to them all in one place will be helpful.

@john-light I've added them and moved them to be under a different subsection from the aragonOS audits.

authors: john-light sohkai

repo: aragon/aragon-wiki


text:
🛑 Sintesys is down

In b449652, Sintesys (https://app.sintesys.id/core/dashboard/default/login) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Sintesys is back up in 91ce533.

repo: arakdraja/upptime


text:
AQL Query on documents with high number of characters triggers OOM killer

My Environment

ArangoDB Version:  3.5.1
Storage Engine: RocksDB
Deployment Mode: Single Server
Deployment Strategy: Manual Start
Configuration:  Stock, no changes
Infrastructure: VmWare Workstation VM
Operating System:  Ubuntu 18.04
Total RAM in your machine:  8192mb
Disks in use:  SSD
Used Package:  Ubuntu .deb

Component, Query & Data
Affected feature:
AQL, arangosh query.
AQL query (if applicable):
FOR doc IN events
        FOR object IN 1..3 OUTBOUND doc origin
            FILTER object
            INSERT {
                _from: doc._id,
                _to: object._id,
                schema_version: 2
            } INTO belongs

Dataset:
Dataset TLDR:
event -> origin (edge) -> sub_event (x2000)

I have provided a Python script (below) as a POC of the problem. The script will delete the database "test" and re-create it. It will then insert a single document into the "events" collection like the one below:
{
"_id": "events/1",
"long_string": "a 10 million character string"
}

The next step is to create 2000 sub_events in a similar format, but with a long_string character value of 500K.
The edge collection origin is created and all 2000 sub_events are connected to the single event. The provided AQL query is then executed against the dataset.
Size of your Dataset on disk:
arangodb:/var/lib/arangodb3# du --max-depth=5 -h
4.0K	./engine-rocksdb/journals/archive
189M	./engine-rocksdb/journals
1.3G	./engine-rocksdb

Steps to reproduce

Run the provided python3 script

Problem:
Arango crashes, we can see that the memory usage shoots up when the AQL query is executed. The memory consumption will continue to grow until all swap is used. The kernel OOM will then kill Arango.
If we minimize the char length for each long_string key in each document the query performs like expected in about 1-10s.
Expected result:
The query to complete, and a new edge between events/1 to all sub-events should exists in the belongs collection.
POC:
import arango
import random
import string

from arango import ArangoClient

number_of_events = 1
number_of_sub_events = 2000

# Initialize the ArangoDB client.
client = ArangoClient(host='0.0.0.0')
db = client.db('_system')

if db.has_database('test'):
    db.delete_database('test')

if not db.has_database('test'):
    db.create_database('test')

client = ArangoClient(host='0.0.0.0')
db = client.db('test')

def random_string(length):
    return ''.join(random.choices(string.ascii_lowercase + string.digits, k=length))

parent = {
    '_key': '1',
    '_id' : 'events/1',
    'long_string': random_string(10000000)

}

db.create_collection('events')
db.collection('events').insert(parent)
db.create_collection('sub_events')

sub_events = []
sub_event = {
    'long_string': random_string(500000),
}

for i in range(1, number_of_sub_events + 1):
    sub_events.append({
        **sub_event,
        '_id': f'sub_events/{i + 1}',
    })

print('Inserting sub-events')

chunks = (len(sub_events) - 1) // 100 + 1
for i in range(chunks):
    batch = sub_events[i*100:(i+1)*100]
    db.collection('sub_events').import_bulk(batch)
    print('Inserted chunk %s / %s' % (i+1, chunks) )

edges = []

db.create_collection('origin', edge=True)

for i in range(number_of_sub_events):
    edges.append({
        '_id': f'origin/{i + 1}',
        '_from': 'events/1',
        '_to': f'sub_events/{i + 1}'
    })

db.collection('origin').import_bulk(edges)

db.create_collection('belongs', edge=True)

db.aql.execute('''
    FOR doc IN events
        FOR object IN 1..3 OUTBOUND doc origin
            FILTER object
            INSERT {
                _from: doc._id,
                _to: object._id,
                schema_version: 2
            } INTO belongs''')

I used python-arango==4.4.0, but the problem is perfectly reproducible directly in arangosh.

Hi @chriskvik,
Could you please try to use the RocksDB query options intermediateCommitSize or intermediateCommitCount? This should limit the memory growth caused by your query.
The default values for these options are as follows:
  --rocksdb.intermediate-commit-count <uint64>                 an intermediate commit will be performed automatically when this number of operations is reached in a transaction
                                                               (default: 1000000)
  --rocksdb.intermediate-commit-size <uint64>                  an intermediate commit will be performed automatically when a transaction has accumulated operations of this size (in
                                                               bytes) (default: 536870912)

Hi, I posted the following on the discussion with @goedderz on Slack.

Everything from 1, 100,1000 all fails at the same point. I'm observing memory consumption going up and down for 10 seconds, then it maxes out, eats all swap and dies.

After he suggested the same.
For context and examples: https://app.slack.com/client/T07NV0TD4/C07NV9NAH/thread/C07NV9NAH-1572267851.183600

authors: chriskvik maxkernbach

repo: arangodb/arangodb


text:
document update: ignoreRevs parameter ignored

My Environment

ArangoDB Version:        3.3.16
Storage Engine:             RocksDB
Deployment Mode:       Single Server
Deployment Strategy:   ArangoDB Starter in Docker
Configuration:
Infrastructure:               own
Operating System:        Ubuntu 16.04
Used Package:              Docker - official Docker library

Component, Query & Data
Affected feature:
Document update via Java driver (Collection::updateDocument)
Steps to reproduce

create a document
update a document
update a second time, with ignoreRevs(false) and the first revision.

Problem:
Document update goes through:
Example data from execute:147, VstCommunicationSync (com.arangodb.internal.velocystream),
which should be the very last layer before sending the message (data refers to point 3. above):
Message requestMessage.head:
[1,1,"test-database",5,"\/_api\/document\/mydocs\/1",{"keepNull":"false","mergeObjects":"true","returnNew":"true","ignoreRevs":"false"},{}]
requestMessage.body:
{"_rev":"_Xje4cm---_","description":"newDescription","updatedAt":"2018-10-09T09:50:10.363000000Z"}
Message responseMessage.head:
[1,2,202,{"Location":"\/_db\/test-database\/_api\/document\/mydocs\/1","Etag":"\"_XjfDeMC--_\""}]
responseMessage.body:
{"_id":"mydocs\/1","_key":"1","_oldRev":"_Xje5UDO--_","_rev":"_XjfDeMC--_","new":{"_id":"mydocs\/1","_key":"1","_rev":"_XjfDeMC--_","description":"newDescription","updatedAt":"2018-10-09T09:50:10.363000000Z"}}
Expected result:
Document update should fail

@dvd7587 : I just verified that the ignoreRevs parameters is actually honored on the server side when trying to send isolated requests to the server.
As this issue only shows a single request and the server's response, I am wondering if you could provide the code fragment that does the entire 3 requests (insertDocument, updateDocument w/o ignoreRevs and updateDocument w/ ignoreRevs). That may help shed some light on this.
Thanks!

I'll come back with a minimal example

I can add that, when I use the ifMatch("revision") method instead, document update breaks as expected

https://github.com/arangodb/arangodb/pull/6854

Hi,
Thanks again for opening this issue
Versions 3.3.19 has been released and it includes a fix for this problem (note that there was no public 3.3.18 - the next release after 3.3.17 is 3.3.19)
I am closing this ticket now. Please feel free to comment if the issue persists
Many thanks,

authors: dvd7587 graetzer jsteemann sleto-it


text:
Bug fix/read write connect error retry

Scope & Purpose
Forward port of https://github.com/arangodb/arangodb/pull/19363

Errors unrelated.


text:
[3.4] Version/Engine Cluster Health

Export Version and Engine in Cluster Health

http://jenkins01.arangodb.biz:8080/job/arangodb-matrix-pr/2232/ HIALGTJ


text:
is.edge() added

Added is.edge() method for edge browser under the issue #161
Also updated README accordingly.

Thanks @ironmaniiith Appreciate it.

authors: arasatasaygin ironmaniiith


text:
run error

Hello Professor, I am missing order data 1--5 when I run prepared--data with the original dataset, how do I get this part of the data, also, the dataset you provided are processed data but I can't run this data successfully in run.py (due to the lack of some pickle operations and parameters in the previous data prepared--data), can you please give me some guidance?

Hello, you can run the files as follows: (1) go to the google drive with the datasets (link in the readme file), and download the "datasets" folder. Move this downloaded folder to the data folder, so it should be data/datasets/...  (for example data/datasets/Brooklyn/...). (2) run the prepare_data.py file in the conda environment specified in the readme file. This will create generations files. You can specify the details of the generations file you want to create via the prepare_data.py file (for example, which city to utilize, etc.). (3) go to src folder and run the run.py file. Again you can specify the details of the simulation run (such as city, delay time, etc.). Let me know if you have any further questions.

authors: arash-dehghan kkkkkkkwwwwwww

repo: arash-dehghan/NeurADP-Order-Dispatching


text:
Merge v1.0 code into master branch

This commit will merge the code written for version 1.0 into the master branch. I'll take the master branch to be the branch that stores the full version history of the project so far, and so this will occupy the first place as an initial release! 🙌

Apologies for the failed checks — I was about to run them when I remembered that these projects relied on Firebase, and therefore I needed a .plist file from Firebase. In this repository, such file is stripped.

repo: arashnrim/Upgrade


text:
🛑 ipfs web is down

In 59d3987, ipfs web (https://ipfs.io/ipns/k51qzi5uqu5dicjkm8zerzc187wessd8ibgwqscv3qx80shm53k9qivmfjmznr) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ipfs web is back up in 760a89e.

repo: aratan/Monitorizaci-n


text:
[Snyk] Upgrade @babel/runtime from 7.17.2 to 7.19.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @babel/runtime from 7.17.2 to 7.19.0.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 9 versions ahead of your current version.
The recommended version was released a month ago, on 2022-09-05.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

Codecov Report
Base: 94.02% // Head: 94.02% // No change to project coverage :thumbsup:

Coverage data is based on head (59ec601) compared to base (7db429a).
Patch has no changes to coverable lines.

Additional details and impacted files
@@            Coverage Diff            @@
##               main     #228   +/-   ##
=========================================
  Coverage     94.02%   94.02%
  Complexity      475      475
=========================================
  Files            96       96
  Lines          1607     1607
  Branches        122      122
=========================================
  Hits           1511     1511
  Misses           56       56
  Partials         40       40

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

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

repo: arbindo/mimock


text:
Changing the rate on a schedule does not change the CloudWatch Event

Describe the bug
After creating a scheduled function in the .arc file, given the same name with a different rate, the schedule is neither updated in AWS nor does it throw an error.
To Reproduce
Steps to reproduce the behavior:

Create a scheduled lambda with any given rate.
Create the resource with npx create
Update the rate
Run npx create again

Expected behavior
Either an error describing the issue (remove and remake) or the CloudWatch event to be updated with the new schedule.
Additional context
Maybe an npx update is the best way to go here, or an explicit npx taint/purge? 🤷🏻♂Obviously some resources/fields in AWS can't be changed on an existing resource.

Yuck, gross. Should prob look at fixing this along with https://github.com/arc-repos/architect/issues/148 while we're in @scheduled functions.

authors: gerred ryanblock

repo: arc-repos/architect


text:
Does it work at runtime?

I want to use Arcadia for runtime scripting capabilities for my game's modding facilities, but I need to know if it can compile/interpret at runtime (sans Unity Editor). I also need to know if there are facilities to add/remove functionalities to sandbox the environment and add stuff specific to my game.

Arcadia works great outside of the Unity editor on the following platforms:

Desktop (Windows, Linux, macOS)
Android

Other platforms are either known to not work or will likely have problems. More details and links are on the wiki.
Closing as this isn't an issue per se, but I am happy to keep talking on the Gitter channel if you'd like.

authors: darkhog nasser

repo: arcadia-unity/Arcadia


text:
🛑 ARCaptcha is down

In cac07e8, ARCaptcha (https://arcaptcha.co/fa) was down:

HTTP code: 0
Response time: 0 ms

Resolved: ARCaptcha is back up in d1a98eb.

repo: arcaptcha/ARCaptcha-monitoring


text:
"Authentication failed" when trying to access PoS Options on captive portal on iOS

Prerequisites

[x] I am running esp32 board version 1.0.4
[x] I checked the documentation and found no answer
[x] I checked to make sure that this issue has not already been filed
[x] I checked to make sure I'm running the latest build

Expected Behavior
Upon tapping on "PoS Options" in the captive portal menu, I want to be able to see input boxes where I can fill in info on my wallet id, lnurlPOS string, etc.
Current Behavior
Upon tapping on "PoS Options", after a couple of seconds I get a response saying "authentication failed".
If I attempt to access it from my browser and not the captive portal, I am asked to enter a username and password upon tapping on the "PoS Options" option in the menu.
Failure Information (for bugs)
Gathering from this thread iOS (and Android 10 onwards) considers this AutoConnect request to be insecure (because HTTP) and thus disallows it.
The following pages might help with finding a solution:

Unauthorize error without prompting the login dialog.
Turn on the debug log options
AutoConnectConfig API

Steps to Reproduce

Launch the AP from ESP32 board by pressing * within 2 seconds of starting
On an iPhone, tap on Settings > Wi-Fi > PoS-xxxxxxxx (under Other Networks)
Enter password ToTheMoon1 (subject to change based on build)
Tap on the hamburger menu on top right
Tap on PoS Options

You can also access the portal on a browser after cancelling out of the captive portal by selecting "Use Without Internet" and then navigating to http://172.217.28.1
It may ask you for a username and password if accessed via a browser.
Context
This issue is only relevant for those attempting to access the portal on any Apple devices.
Failure Logs

I also get exactly the same error and have not figured out a solution.

I have the same issue.

This issue has been resolved with https://github.com/arcbtc/bitcoinPoS/commit/31272a6419ede1eedaef3efa52c06058592d8282, thanks for the report.

I'm still getting this issue on iOS and Mac.

authors: Boldeen CandleHater LightRider5 Smithrich mrugakshee

repo: arcbtc/bitcoinPoS


text:
Generate View does not add Connection to Connections

Version of Archi, Operating System

Archi 4.0.2. All OS.
Expected Behaviour

When selecting "Generate View For..." an element that connects to other elements via a connection to connection, all elements should be added.
Actual Behaviour

Some elements are missing.
Steps to Reproduce the Behaviour
See http://forum.archimatetool.com/index.php?topic=415.0

Created branch:
https://github.com/archimatetool/archi/tree/generate_view_fix
Started a fix. If anyone would like to contribute the full fix please do so...

Fixed for next release

repo: archimatetool/archi


text:
I9 new radiation engine daysim by paul

#9 here it is again with some fixes

@shanshanhsieh would you mind taking a look at this PR ? i.e., testing it?.
To test it
run first create_gml, then run radiation_main in resources/radiation_daysim
@daren-thomas would you mind poiting me to a guide to create the unit tests or whatever is needed for jenkings?

@JIMENOFONSECA I suggest looking into the file cea/tests/test_sensible_loads.py for an easy introduction to unit tests.
If you add a file starting with test_ into that folder and have a test class inside you're good to go. See https://pymotw.com/2/unittest/ for more information on implementing unit tests. I will hold a presentation on testing philosophy later on, right now I totally need to be on CISBAT...

@JIMENOFONSECA which numpy version do you have? mine is 1.9.2
Here's the error i get:
C:\Users\fcl2\Anaconda2\envs\esri104\python.exe "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py"
RuntimeError: module compiled against API version 0xa but this version of numpy is 0x9
Traceback (most recent call last):
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 143, in
create_citygml(input_buildings_shapefile, input_terrain_raster, output_folder)
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 121, in create_citygml
terrain_face_list = terrain2d23d(citygml_writer, input_terrain)
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 94, in terrain2d23d
raster_points = raster_reader(input_terrain_raster)
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 108, in raster_reader
a = band.ReadAsArray(0, 0, raster_dataset.RasterXSize, raster_dataset.RasterYSize)
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\osgeo\gdal.py", line 1328, in ReadAsArray
import gdalnumeric
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\osgeo\gdalnumeric.py", line 1, in
from osgeo.gdal_array import *
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\osgeo\gdal_array.py", line 21, in
_gdal_array = swig_import_helper()
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\osgeo\gdal_array.py", line 20, in swig_import_helper
return importlib.import_module('gdal_array')
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\importlib_init.py", line 37, in import_module
import(name)
ImportError: No module named _gdal_array
Process finished with exit code 1

So it might be that you have a version of gdal lacking that.
Check how it was installed and reinstall it..
http://gis.stackexchange.com/questions/82977/is-it-possible-to-use-gdal-without-admin-rights/83297#83297
Best, Jimeno
On 4 Apr 2017, at 18:07, shanshanhsieh <notifications@github.commailto:notifications@github.com> wrote:
@JIMENOFONSECAhttps://github.com/JIMENOFONSECA which numpy version do you have? mine is 1.9.2
Here's the error i get:
C:\Users\fcl2\Anaconda2\envs\esri104\python.exe "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py"
RuntimeError: module compiled against API version 0xa but this version of numpy is 0x9
Traceback (most recent call last):
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 143, in
create_citygml(input_buildings_shapefile, input_terrain_raster, output_folder)
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 121, in create_citygml
terrain_face_list = terrain2d23d(citygml_writer, input_terrain)
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 94, in terrain2d23d
raster_points = raster_reader(input_terrain_raster)
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 108, in raster_reader
a = band.ReadAsArray(0, 0, raster_dataset.RasterXSize, raster_dataset.RasterYSize)
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\osgeo\gdal.py", line 1328, in ReadAsArray
import gdalnumeric
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\osgeo\gdalnumeric.py", line 1, in
from osgeo.gdal_array import *
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\osgeo\gdal_array.py", line 21, in
_gdal_array = swig_import_helper()
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\osgeo\gdal_array.py", line 20, in swig_import_helper
return importlib.import_module('gdal_array')
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\importlib_init.py", line 37, in import_module
import(name)
ImportError: No module named _gdal_array
Process finished with exit code 1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/architecture-building-systems/CEAforArcGIS/pull/567#issuecomment-291455107, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIjrgsmpido8bxWnEbo_kf18_1A91acKks5rshZagaJpZM4MrCdM.

@JIMENOFONSECA  The previous error was solved by re-install the packages to the following:  GDAL 2.1.3, numpy 1.12.1 and matplolib 2.0.0
Now I am having error with OCC package:
ERROR:OCC.Display.backend:wx could not be loaded
None
Traceback (most recent call last):
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 143, in
create_citygml(input_buildings_shapefile, input_terrain_raster, output_folder)
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 127, in create_citygml
construct.visualise([terrain_face_list,bsolid_list], ["GREEN","WHITE"],backend = "wx")
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\pyliburo\py3dmodel\construct.py", line 496, in visualise
display, start_display, add_menu, add_function_to_menu = init_display(backend_str = backend)
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\OCC\Display\SimpleGui.py", line 92, in init_display
used_backend = load_backend(backend_str)
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\OCC\Display\backend.py", line 209, in load_backend
raise ValueError(msg)
ValueError: wx could not be loaded
Process finished with exit code 1

no idea... check python occ, you might be missing something in the installation.

From: shanshanhsieh [notifications@github.com]
Sent: Wednesday, April 05, 2017 2:46 PM
To: architecture-building-systems/CEAforArcGIS
Cc: Jimeno Fonseca; Mention
Subject: Re: [architecture-building-systems/CEAforArcGIS] I9 new radiation engine daysim by paul (#567)
@JIMENOFONSECAhttps://github.com/JIMENOFONSECA The previous error was solved by re-install the packages to the following: GDAL 2.1.3, numpy 1.12.1 and matplolib 2.0.0
Now I am having error with OCC package:
ERROR:OCC.Display.backend:wx could not be loaded
None
Traceback (most recent call last):
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 143, in
create_citygml(input_buildings_shapefile, input_terrain_raster, output_folder)
File "C:/Users/fcl2/AppData/Roaming/ESRI/Desktop10.4/ArcToolbox/My Toolboxes/cea/resources/radiation_daysim/create_gml.py", line 127, in create_citygml
construct.visualise([terrain_face_list,bsolid_list], ["GREEN","WHITE"],backend = "wx")
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\pyliburo\py3dmodel\construct.py", line 496, in visualise
display, start_display, add_menu, add_function_to_menu = init_display(backend_str = backend)
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\OCC\Display\SimpleGui.py", line 92, in init_display
used_backend = load_backend(backend_str)
File "C:\Users\fcl2\Anaconda2\envs\esri104\lib\site-packages\OCC\Display\backend.py", line 209, in load_backend
raise ValueError(msg)
ValueError: wx could not be loaded
Process finished with exit code 1
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/architecture-building-systems/CEAforArcGIS/pull/567#issuecomment-291769803, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AIjrgu_GQChqZbXLtvF4z3Sw-BSx7dIqks5rszjjgaJpZM4MrCdM.

@daren-thomas the last commit erased the new case study from examples!

I moved it back to cea/examples where it was (on master) - this makes it easier to distribute with setuptools... It is not lost, @JIMENOFONSECA!

(I'm trying to run all the stuff on my computer, including installing all the dependencies in order to merge this - we're not going back to the old stuff again, right?)

Yes, moving it is fine, just I checked the branch this morning and the folder cea/example was empty. maybe it works now :-)

@daren-thomas  the folder cea/example seems empty from my side as well (in branch #567

@daren-thomas i think this came back to be urgent now, any chance we could help from here?

cea radiation-daysim works on my PC:
starting Daysim radiation simulation
=======================================================
= gen_dc: calculate direct daylight coefficients      =
= (this simulation may take several minutes to hours) =
=======================================================
calculate 65 direct daylight coefficients for variant static_system...
=======================================================
= gen_dc: calculate diffuse daylight coefficients     =
= (ignore WARNING: no light sources found)            =
= (this simulation may take several minutes to hours) =
=======================================================
calculate diffuse daylight coefficients for variant static_system...
rtrace_dc: warning - no light sources found
ds_illum WARNING: climate file units differ in climate and project header files.
Daysim radiation finished - proceed to save results
execute daysim done
TIME TAKEN:  5.95026666721

BUT: The following things did pop up:

the installation guide is not updated to include how to install it (I have updated the setup.py file to reflect the pip installable stuff and added the conda install magic to the developer's installation section for pythonocc-core, but DAYSIM still needs to be downloaded and installed and I think the guide should explain that)
the code uses a lot of abbreviations for no purpose whatsoever (bldng - seriously? did we run out of bytes??) and what is a rad_mat? a radiation matrix? or materials?? I tried to check the docstrings for info but there weren't any.

So. To conclude. We could merge this now. I'm fine with that. Well. I still have to fix the Jenkins... But I would prefer it if we got the code nice and pretty first or at least updated the installation guide.

@daren-thomas when running, it requires to install several libraries. among them OCCUtils, there is an error as conda cannot find it.

do conda install -c pythonocc -c oce pythonocc-core==0.17.3 does not work :-(

i checked this, and apperently the problem is with the new version of python 0cc
https://github.com/tpaviot/pythonocc-core/issues/413

maybe. hard to say, as they are using different versions (python 3, 64bit as opposed to python2.7, 32bit) but i'll check. I did my testing with miniconda (i like it better as it doesn't add so much stuff to the computer) - i'll also do a check on anaconda. this could take a while: hold yer horses! :)

I fixed it by including another version of python OCC which is the one kianwee refers to in his readme
v 0.16. now it works good

I think I figured out how to install the pythonocc. Also pyliburo doesn't need to be installed seperately. I am currently running the daysim radiation in a vm. This could take a while...

I have just tested the current installation script in a vm with miniconda. I believe it should also work for anaconda. The following cea commands were tested:

cea extract-reference-case
cd  reference-case-open\baseline
cea data-helper
cea radiation-daysim
cea demand

These commands all ran through in a brand-new conda env created with the installation script in my last commit. I needed to track down the os-level loading of dll files using procmon.exe to figure out that the problem I was having had to do with tbb being installed from conda-forge. It needs to be installed from dlr-sc as well as freeimageplus and gl2ps. Next, the pythonocc can be installed from the channels oce and pythonocc at version 0.17.3. the python setup.py install call now installs pyliburo and pythonocc-utils so those do not need to be installed separately.

The installation works fine now, in terms of running the cea test command, i come across the next issues, @daren-thomas any idea how to solve it?


text:
Click to open url

I cant click to open url. How can I implement function class openURL ?
Thanks for your help

const html =
Kichi-Kichi toàn quốc, xem danh sách  tại đây .
;

Also when font-size is 0.75rem it not show. Maybe "rem" isn't support

@vinhtran6921 As per your questions:

To implement custom renderers, you can use renderers prop, see Creating custom renderers;
rem are not supported in the v4 and v5, but is supported in v6, which first prerelease will be available today, see #430

I am closing because this report does not follow our guidelines. Feel free to comment here or on Discord for assistance.

repo: archriss/react-native-render-html


text:
docs(list): add usage demo & enhan responsive grid

Types of changes

[ ] New feature
[ ] Bug fix
[x] Enhancement
[ ] Component style change
[ ] Typescript definition change
[x] Documentation change
[ ] Coding style change
[ ] Refactoring
[ ] Test cases
[ ] Continuous integration
[ ] Breaking change
[ ] Others

Background and context

Solution

How is the change tested?

Changelog

Type
Component
Changelog(CN)
Changelog(EN)
Related issues

docs
list
新增使用案例
add usage demo
-

feat
list
支持响应式网格布局参数
support responsive grid props
-

Checklist:

[ ] Test suite passes (npm run test)
[ ] Provide changelog for relevant changes (e.g. bug fixes and new features) if applicable.
[ ] Changes are submitted to the appropriate branch (e.g. features should be submitted to feature branch and others
should be submitted to main branch)

Other information

🤔 响应式网格没有任何结构修改，仅算是一直使用增强

更新到2.37.0 a-list组件不能使用了，   最基本的 123123 不显示，只显示一条横线

authors: hehehai itlanjing

repo: arco-design/arco-design-vue


text:
Strange look when breakpoint enabled

I think It's not a proper solution, doesn't look great

Duplicate of #162

Hi @bmarvinb :wave:, thanks for your contribution :+1:
This is a known problem tracked in issue #162 and #55. Please see my comment about the plans to refactor the current line styles for the debug mode and general selections in the editor an subscribe to the issue for further updates and discussions.

authors: bmarvinb svengreb

repo: arcticicestudio/nord-jetbrains


text:
Add some color to Clojure keywords to help distinguish them

Keywords in clojure (like atoms in Erlang/Elixir or symbols in Ruby, e.x. :name) are constants and often used as keys in maps.
It's helpful to differentiate them from identifiers, so this patch colors them with the same color used for HTML attribute names.
Everything else looked good out of the box.

Nord rocks, I discovered this scheme yesterday and have nord-ified mulitple machines :)

After looking at some other nord themes, I'm going to close this and spend more time refining it to match other editors/languages in the nord system.
It seems that using #D8DEE9 and bold is what you are doing for Elixir atoms, which would be appropriate for keywords I'm thinking.


text:
Add embed formatting for main/supporting characters

Add embed formatting for main/supporting characters. Problem is currently, main character lists can be pretty long, and supporting characters even longer, so need a way to display that or even advance without it getting tedious to advance through the whole list.

COMPLETELY DONE!!! Although for some supporting character casts it would be extremely tedious to scroll through, I like the functionality as it is now since it uses a single embed function for main, supporting, and specific character calls. Only fixes now are to implement a last embed message as to prevent arrow scrolls from affecting every single embed.

Completely fixed. Reactions will no longer affect previous embeds.

repo: arescrimson/Lytro


text:
Added the Rewards page

Related Issue
Closes #1069
Description
The rewards page for a dummy user has been added.
Type of PR

[ ] Bug fix
[x] Feature enhancement
[ ] Documentation update
[ ] Other (specify): _______________

Screenshots / videos (if applicable)

Checklist:

[x] I have performed a self-review of my code
[x] I have read and followed the Contribution Guidelines.
[x] I have tested the changes thoroughly before submitting this pull request.
[x] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[x] I have commented my code, particularly in hard-to-understand areas.

Additional context:
[Include any additional information or context that might be helpful for reviewers.]

Please look into this.


text:
dataset pagination only allows to show first 10K records

Describe the bug
I uploaded 21K records to a dataset and it only show 10K within the UI. Also, it doesn't allow me to paginate past the first 10K records without adding queries.
To Reproduce
Steps to reproduce the behavior:

Upload more than 10K records
Go to the dataset in the UI
Try to go past 10K record in pagination

Expected behavior
I would expect the record to be available or at least get a reference on why not all records are shown.
Screenshots

Environment (please complete the following information):

OS [e.g. iOS]: iOS
Browser [e.g. chrome, safari]: Firefeox
Argilla Version [e.g. 1.0.0]: 1.1.1
ElasticSearch Version [e.g. 7.10.2]:7.10.2
Docker Image (optional) [e.g. argilla:v1.0.0]: 1.1.1

Additional context
N.A.

@leiyre @Amelie-V  we need to take into account this use case after removing the Records count in the filters header.

Given that we can get the total number of records via Elastic, is seeing only 1000 pages a UI memory issue or something? If so, wouldn´t we be able to lazy-load only a part of the pages? The X surrounding pages for each one of the pages that we can directly click on?
In the example above, we can directly click 1,2,3 and 1000, with X=3 we could load 1,2,3,4,5,6, 997,998,999,1000.

repo: argilla-io/argilla


text:
Argon shows up every single time I launch a place in studio or play a game

Should be a configuration option or something like that

Could you dock your window and see if it solves the issue? Also, could you confirm that other plugins e.g. Rojo don't have the same problem? Last time I checked it was a Roblox issue as some of my other plugins did the the same thing.

Could you dock your window and see if it solves the issue? Also, could you confirm that other plugins e.g. Rojo don't have the same problem? Last time I checked it was a Roblox issue as some of my other plugins did the the same thing.

Closing it doesn't solve it and it seems to be a plugin issue as some plugins have it and others don't
rojo only makes a notification if the place previously used rojo
I will try to look into it more

Could you send a quick recording showcasing this issue? Right now the widget just uses its previous state which I think works correctly:
https://github.com/user-attachments/assets/6512c961-7541-4f67-b221-dc9a6fcb1650

It will always come back if i were to close it and even if i close it
https://github.com/user-attachments/assets/6424ef23-6a75-414f-a102-9866def26c27

ok i dont know how thats even possible
thanks github
https://github.com/user-attachments/assets/096c84e3-a22c-4135-a49b-793d42d938a6

It might be a Windows only issue. I don’t think I can do anything to fix this problem at the moment as Argon doesn’t even handle widget position or docking state. Let's leave this issue open for now

authors: DervexDev EasternBloxxer

repo: argon-rbx/argon-roblox


text:
Retrying workflows have short deadline ignoring activeDeadlineSeconds

Pre-requisites

[X] I have double-checked my configuration
[X] I have tested with the :latest image tag (i.e. quay.io/argoproj/workflow-controller:latest) and can confirm the issue still exists on :latest. If not, I have explained why, in detail, in my description below.
[X] I have searched existing issues and could not find a match for this bug
[x] I'd like to contribute the fix myself (see contributing guide)

What happened/what did you expect to happen?
I expect that the activeDeadlineSeconds parameter should also apply to retrying workflow pod containers. However, it appears that the retrying container has a short deadline of approximately 1 minute.
Additionally, when I set the activeDeadlineSeconds at the template level, the deadline for the first workflow's wait container is set to 0001-01-01 00:00:00 +0000 UTC, while the second workflow's wait container has a deadline of about 1 minute.
Is this behavior intentional?
Below are the logs resulting from setting the workflow level activeDeadlineSeconds.
Name:                retry-sample-knssl
Namespace:           argo
ServiceAccount:      unset (will run with the default ServiceAccount)
Status:              Failed
Message:             Max duration limit exceeded
Conditions:
 PodRunning          False
 Completed           True
Created:             Mon May 13 11:42:44 +0900 (3 minutes ago)
Started:             Mon May 13 11:42:44 +0900 (3 minutes ago)
Finished:            Mon May 13 11:45:55 +0900 (now)
Duration:            3 minutes 11 seconds
Progress:            0/2
ResourcesDuration:   17s*(1 cpu),4m29s*(100Mi memory)

STEP                        TEMPLATE       PODNAME                                      DURATION  MESSAGE
 ✖ retry-sample-knssl       retry-example                                                         Max duration limit exceeded
 ├─✖ retry-sample-knssl(0)  retry-example  retry-sample-knssl-retry-example-2352189541  2m        Error (exit code 10)
 └─✖ retry-sample-knssl(1)  retry-example  retry-sample-knssl-retry-example-2151005208  47s       Error (exit code 143)

Version
latest
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  generateName: retry-sample-
spec:
  activeDeadlineSeconds: 3600
  entrypoint: retry-example
  templates:
    - name: retry-example
      retryStrategy:
        limit: 2
        backoff:
          duration: 10s
          factor: 2
          maxDuration: 3m
      container:
        image: alpine
        command: [sh, -c]
        args: ["sleep 120; exit 10"]

Logs from the workflow controller
time="2024-05-13T02:42:44.653Z" level=info msg="Processing workflow" Phase= ResourceVersion=1899 namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:44.661Z" level=info msg="Task-result reconciliation" namespace=argo numObjs=0 workflow=retry-sample-knssl
time="2024-05-13T02:42:44.661Z" level=info msg="Updated phase  -> Running" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:44.661Z" level=warning msg="Node was nil, will be initialized as type Skipped" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:44.662Z" level=info msg="was unable to obtain node for , letting display name to be nodeName" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:44.662Z" level=info msg="Retry node retry-sample-knssl initialized Running" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:44.662Z" level=info msg="was unable to obtain node for , letting display name to be nodeName" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:44.662Z" level=info msg="Pod node retry-sample-knssl-2352189541 initialized Pending" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:44.686Z" level=info msg="Created pod: retry-sample-knssl(0) (retry-sample-knssl-retry-example-2352189541)" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:44.686Z" level=info msg="TaskSet Reconciliation" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:44.686Z" level=info msg=reconcileAgentPod namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:44.694Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=1902 workflow=retry-sample-knssl
time="2024-05-13T02:42:54.659Z" level=info msg="Processing workflow" Phase=Running ResourceVersion=1902 namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:54.660Z" level=info msg="Task-result reconciliation" namespace=argo numObjs=1 workflow=retry-sample-knssl
time="2024-05-13T02:42:54.660Z" level=info msg="task-result changed" namespace=argo nodeID=retry-sample-knssl-2352189541 workflow=retry-sample-knssl
time="2024-05-13T02:42:54.661Z" level=info msg="node changed" namespace=argo new.message= new.phase=Running new.progress=0/1 nodeID=retry-sample-knssl-2352189541 old.message= old.phase=Pending old.progress=0/1 workflow=retry-sample-knssl
time="2024-05-13T02:42:54.661Z" level=info msg="TaskSet Reconciliation" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:54.661Z" level=info msg=reconcileAgentPod namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:42:54.687Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=1928 workflow=retry-sample-knssl
time="2024-05-13T02:43:04.695Z" level=info msg="Processing workflow" Phase=Running ResourceVersion=1928 namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:43:04.697Z" level=info msg="Task-result reconciliation" namespace=argo numObjs=1 workflow=retry-sample-knssl
time="2024-05-13T02:43:04.697Z" level=info msg="task-result changed" namespace=argo nodeID=retry-sample-knssl-2352189541 workflow=retry-sample-knssl
time="2024-05-13T02:43:04.698Z" level=info msg="node unchanged" namespace=argo nodeID=retry-sample-knssl-2352189541 workflow=retry-sample-knssl
time="2024-05-13T02:43:04.701Z" level=info msg="TaskSet Reconciliation" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:43:04.701Z" level=info msg=reconcileAgentPod namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:43:04.728Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=1935 workflow=retry-sample-knssl
time="2024-05-13T02:43:27.542Z" level=info msg="Processing workflow" Phase=Running ResourceVersion=1935 namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:43:27.544Z" level=info msg="Task-result reconciliation" namespace=argo numObjs=1 workflow=retry-sample-knssl
time="2024-05-13T02:43:27.544Z" level=info msg="task-result changed" namespace=argo nodeID=retry-sample-knssl-2352189541 workflow=retry-sample-knssl
time="2024-05-13T02:43:27.545Z" level=info msg="node unchanged" namespace=argo nodeID=retry-sample-knssl-2352189541 workflow=retry-sample-knssl
time="2024-05-13T02:43:27.552Z" level=info msg="TaskSet Reconciliation" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:43:27.552Z" level=info msg=reconcileAgentPod namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:43:27.578Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=1935 workflow=retry-sample-knssl
time="2024-05-13T02:44:58.808Z" level=info msg="Processing workflow" Phase=Running ResourceVersion=1935 namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:44:58.809Z" level=info msg="Task-result reconciliation" namespace=argo numObjs=1 workflow=retry-sample-knssl
time="2024-05-13T02:44:58.809Z" level=info msg="task-result changed" namespace=argo nodeID=retry-sample-knssl-2352189541 workflow=retry-sample-knssl
time="2024-05-13T02:44:58.810Z" level=info msg="Pod failed: Error (exit code 10)" displayName="retry-sample-knssl(0)" namespace=argo pod=retry-sample-knssl-retry-example-2352189541 templateName=retry-example workflow=retry-sample-knssl
time="2024-05-13T02:44:58.810Z" level=info msg="node changed" namespace=argo new.message="Error (exit code 10)" new.phase=Failed new.progress=0/1 nodeID=retry-sample-knssl-2352189541 old.message= old.phase=Running old.progress=0/1 workflow=retry-sample-knssl
time="2024-05-13T02:44:58.811Z" level=info msg="node has maxDuration set, setting executionDeadline to: Mon May 13 02:45:44 +0000 (45 seconds from now)" namespace=argo node=retry-sample-knssl workflow=retry-sample-knssl
time="2024-05-13T02:44:58.811Z" level=info msg="Retry Policy: OnFailure (onFailed: true, onError false)" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:44:58.812Z" level=info msg="1 child nodes of retry-sample-knssl failed. Trying again..." namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:44:58.812Z" level=info msg="was unable to obtain node for , letting display name to be nodeName" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:44:58.812Z" level=info msg="Pod node retry-sample-knssl-2151005208 initialized Pending" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:44:58.856Z" level=info msg="Created pod: retry-sample-knssl(1) (retry-sample-knssl-retry-example-2151005208)" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:44:58.856Z" level=info msg="TaskSet Reconciliation" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:44:58.857Z" level=info msg=reconcileAgentPod namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:44:58.890Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=1999 workflow=retry-sample-knssl
time="2024-05-13T02:44:58.897Z" level=info msg="cleaning up pod" action=labelPodCompleted key=argo/retry-sample-knssl-retry-example-2352189541/labelPodCompleted
time="2024-05-13T02:45:08.863Z" level=info msg="Processing workflow" Phase=Running ResourceVersion=1999 namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:08.864Z" level=info msg="Task-result reconciliation" namespace=argo numObjs=2 workflow=retry-sample-knssl
time="2024-05-13T02:45:08.865Z" level=info msg="task-result changed" namespace=argo nodeID=retry-sample-knssl-2352189541 workflow=retry-sample-knssl
time="2024-05-13T02:45:08.865Z" level=info msg="task-result changed" namespace=argo nodeID=retry-sample-knssl-2151005208 workflow=retry-sample-knssl
time="2024-05-13T02:45:08.866Z" level=info msg="node changed" namespace=argo new.message= new.phase=Running new.progress=0/1 nodeID=retry-sample-knssl-2151005208 old.message= old.phase=Pending old.progress=0/1 workflow=retry-sample-knssl
time="2024-05-13T02:45:08.868Z" level=info msg="TaskSet Reconciliation" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:08.868Z" level=info msg=reconcileAgentPod namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:08.892Z" level=info msg="Workflow update successful" namespace=argo phase=Running resourceVersion=2022 workflow=retry-sample-knssl
time="2024-05-13T02:45:55.935Z" level=info msg="Processing workflow" Phase=Running ResourceVersion=2022 namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:55.938Z" level=info msg="Task-result reconciliation" namespace=argo numObjs=2 workflow=retry-sample-knssl
time="2024-05-13T02:45:55.938Z" level=info msg="task-result changed" namespace=argo nodeID=retry-sample-knssl-2352189541 workflow=retry-sample-knssl
time="2024-05-13T02:45:55.939Z" level=info msg="task-result changed" namespace=argo nodeID=retry-sample-knssl-2151005208 workflow=retry-sample-knssl
time="2024-05-13T02:45:55.940Z" level=info msg="Pod failed: Error (exit code 143)" displayName="retry-sample-knssl(1)" namespace=argo pod=retry-sample-knssl-retry-example-2151005208 templateName=retry-example workflow=retry-sample-knssl
time="2024-05-13T02:45:55.940Z" level=info msg="node changed" namespace=argo new.message="Error (exit code 143)" new.phase=Failed new.progress=0/1 nodeID=retry-sample-knssl-2151005208 old.message= old.phase=Running old.progress=0/1 workflow=retry-sample-knssl
time="2024-05-13T02:45:55.941Z" level=info msg="Max duration limit exceeded. Failing..." namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:55.941Z" level=info msg="node retry-sample-knssl phase Running -> Failed" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:55.941Z" level=info msg="node retry-sample-knssl message: Max duration limit exceeded" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:55.941Z" level=info msg="node retry-sample-knssl finished: 2024-05-13 02:45:55.941690803 +0000 UTC" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:55.941Z" level=info msg="TaskSet Reconciliation" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:55.942Z" level=info msg=reconcileAgentPod namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:55.942Z" level=info msg="Updated phase Running -> Failed" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:55.942Z" level=info msg="Updated message  -> Max duration limit exceeded" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:55.942Z" level=info msg="Marking workflow completed" namespace=argo workflow=retry-sample-knssl
time="2024-05-13T02:45:55.948Z" level=info msg="cleaning up pod" action=deletePod key=argo/retry-sample-knssl-1340600742-agent/deletePod
time="2024-05-13T02:45:55.966Z" level=info msg="Workflow update successful" namespace=argo phase=Failed resourceVersion=2054 workflow=retry-sample-knssl
time="2024-05-13T02:45:55.994Z" level=info msg="cleaning up pod" action=labelPodCompleted key=argo/retry-sample-knssl-retry-example-2151005208/labelPodCompleted

Logs from in your workflow's wait container
* first workflow (has deadline with 1 hour)
time="2024-05-13T02:44:48.780Z" level=info msg="No Script output reference in workflow. Capturing script output ignored"
time="2024-05-13T02:44:48.780Z" level=info msg="No output parameters"
time="2024-05-13T02:44:48.780Z" level=info msg="No output artifacts"
time="2024-05-13T02:44:48.781Z" level=info msg="S3 Save path: /tmp/argo/outputs/logs/main.log, key: retry-sample-knssl/retry-sample-knssl-retry-example-2352189541/main.log"
time="2024-05-13T02:44:48.781Z" level=info msg="Creating minio client using static credentials" endpoint="minio:9000"
time="2024-05-13T02:44:48.781Z" level=info msg="Saving file to s3" bucket=my-bucket endpoint="minio:9000" key=retry-sample-knssl/retry-sample-knssl-retry-example-2352189541/main.log path=/tmp/argo/outputs/logs/main.log
time="2024-05-13T02:44:48.791Z" level=info msg="Save artifact" artifactName=main-logs duration=10.050083ms error="<nil>" key=retry-sample-knssl/retry-sample-knssl-retry-example-2352189541/main.log
time="2024-05-13T02:44:48.791Z" level=info msg="not deleting local artifact" localArtPath=/tmp/argo/outputs/logs/main.log
time="2024-05-13T02:44:48.791Z" level=info msg="Successfully saved file: /tmp/argo/outputs/logs/main.log"
time="2024-05-13T02:44:48.803Z" level=info msg="Alloc=7730 TotalAlloc=13965 Sys=23909 NumGC=5 Goroutines=10"

* second workflow(has short deadline less than 1 minute)
time="2024-05-13T02:45:00.792Z" level=info msg="Starting Workflow Executor" version=v3.5.6
time="2024-05-13T02:45:00.795Z" level=info msg="Using executor retry strategy" Duration=1s Factor=1.6 Jitter=0.5 Steps=5
time="2024-05-13T02:45:00.795Z" level=info msg="Executor initialized" deadline="2024-05-13 02:45:44 +0000 UTC" includeScriptOutput=false namespace=argo podName=retry-sample-knssl-retry-example-2151005208 templateName=retry-example version="&Version{Version:v3.5.6,BuildDate:2024-04-19T20:56:53Z,GitCommit:555030053825dd61689a086cb3c2da329419325a,GitTag:v3.5.6,GitTreeState:clean,GoVersion:go1.21.9,Compiler:gc,Platform:linux/arm64,}"
time="2024-05-13T02:45:00.806Z" level=info msg="Starting deadline monitor"
time="2024-05-13T02:45:44.001Z" level=info msg="Step exceeded its deadline"
time="2024-05-13T02:45:44.004Z" level=info msg="Killing containers"
time="2024-05-13T02:45:45.866Z" level=info msg="Main container completed" error="<nil>"
time="2024-05-13T02:45:45.866Z" level=info msg="No Script output reference in workflow. Capturing script output ignored"
time="2024-05-13T02:45:45.866Z" level=info msg="No output parameters"
time="2024-05-13T02:45:45.866Z" level=info msg="No output artifacts"
time="2024-05-13T02:45:45.867Z" level=info msg="S3 Save path: /tmp/argo/outputs/logs/main.log, key: retry-sample-knssl/retry-sample-knssl-retry-example-2151005208/main.log"

I want to confirm if I am misunderstanding the maxDuration parameter.
In the documentation, it states, "maxDuration is the maximum amount of time allowed for a workflow in the backoff strategy." Based on this, I thought that maxDuration only affects the backoff process.
However, in the code, I noticed that opts.executionDeadline is overridden by maxDurationDeadline.
https://github.com/argoproj/argo-workflows/blob/9cacef302bca869da1700b72bede1afad0e9526d/workflow/controller/operator.go#L1054
Is this intentional?
If so, I don't think this is a bug.
If not, I believe some tests should also be updated. (ex, func TestPropagateMaxDurationProcess in workflow/controller/operator_test.go)

We may want to reconsider this later within the context of #10341, i.e. if pending and active time are split in two. The backoff maxDuration may make more sense for the pending state / pendingTimeout only, while activeDeadlineSeconds may make more sense to only apply to the active state.

repo: argoproj/argo-workflows


text:
Java client fails to deserialize WorkflowTemplate

Checklist

[x] Double-checked my configuration.
[x] Tested using the latest version.
[x] Used the Emissary executor.

Summary
What happened/what you expected to happen?
I'm using the java-client to get a WorkflowTemplate (any) form the server. This results in an IllegalStateException.
java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 165 path $.metadata.creationTimestamp
	at com.google.gson.stream.JsonReader.beginObject(JsonReader.java:385) ~[gson-2.9.0.jar:na]

the server returns a valid JSON with the following metadata (double checked that via cURL):
  "metadata": {
    "name": "********",
    "namespace": "argo",
    "uid": "9b1039c0-f710-458e-b510-945337dd4bac",
    "resourceVersion": "15460",
    "generation": 1,
    "creationTimestamp": "2022-06-21T12:57:34Z",
    "labels": {
      "kustomize.toolkit.fluxcd.io/name": "argo-pipelines",
      "kustomize.toolkit.fluxcd.io/namespace": "flux-system"
    }

I also checked the schema.json
"creationTimestamp": {
"$ref": "#/definitions/io.k8s.apimachinery.pkg.apis.meta.v1.Time",
"description": "CreationTimestamp is a timestamp representing the server time when this object was created. It is not guaranteed to be set in happens-before order across separate operations. Clients may not set this value. It is represented in RFC3339 form and is in UTC.\n\nPopulated by the system. Read-only. Null for lists. More info: https://git.k8s.io/community/contributors/devel/sig-architecture/api-conventions.md#metadata"
}

"io.k8s.apimachinery.pkg.apis.meta.v1.Time": {
"description": "Time is a wrapper around time.Time which supports correct marshaling to YAML and JSON.  Wrappers are provided for many of the factory methods that the time package offers.",
"format": "date-time",
"type": "string"
}

So GSON understandably expects a BEGIN_OBJECT for the creationTimestamp value.
How can I solve this issue?
What version are you running?
Server: v3.3.1
Java Client: v3.3.8
Diagnostics
Paste the smallest workflow that reproduces the bug. We must be able to run the workflow.
not applicable, relates to the client.

# Logs from the workflow controller:
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}

# If the workflow's pods have not been created, you can skip the rest of the diagnostics.

# The workflow's pods that are problematic:
kubectl get pod -o yaml -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

# Logs from in your workflow's wait container, something like:
kubectl logs -c wait -l workflows.argoproj.io/workflow=${workflow},workflow.argoproj.io/phase!=Succeeded

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

I also encountered this problem, looking forward to the official solution to it

I also faced this issue.
An easy way to reproduce it is to mock the response from a server and pass it through io.argoproj.workflow.JSON
My example:
import com.google.gson.reflect.TypeToken;
import com.google.gson.stream.JsonReader;
import io.argoproj.workflow.JSON;
import io.argoproj.workflow.models.IoArgoprojWorkflowV1alpha1Workflow;

import java.io.StringReader;
import java.lang.reflect.Type;

public class Main {

    public static void main(String[] args) {
        JSON json = new JSON();
        String mockResponseBody = "{\"metadata\":{\"name\":\"test\",\"creationTimestamp\":\"2022-08-01T07:51:04Z\"}}";

        JsonReader jsonReader = new JsonReader(new StringReader(mockResponseBody));
        Type localVarReturnType = new TypeToken<IoArgoprojWorkflowV1alpha1Workflow>(){}.getType();

        json.getGson().fromJson(jsonReader, localVarReturnType);
    }
}

Despite the json is valid, the result is:
Caused by: java.lang.IllegalStateException: Expected BEGIN_OBJECT but was STRING at line 1 column 49 path $.metadata.creationTimestamp

Just wondering which version this issue occurs from? Is there any working 3.3.x Argo Workflows Java SDK?

I have the issue with 3.3.8 java SDK

Can you try latest?

It is maybe not the same case for me. I was migrated from an old argoproj-lab SDK client and no 3.x version works for me in fact.
I have: Failed making field 'java.time.Instant#seconds' accessible; either change its visibility or write a custom TypeAdapter for its declaring type
So it is related to Gson parsing and basic java type protection.
I got the same error with "Expected BEGIN_OBJECT but was STRING" after an ugly patch to the jvm:
"--add-opens",
"java.base/java.time=ALL-UNNAMED",
But I don't know if it is the same issue I don't want to change this issue target.
For information my server is version 3.3.8 if it helps.

io.argoproj.workflow.models.IoArgoprojWorkflowV1alpha1Workflow has an attribute metadata which is an object of io.kubernetes.client.openapi.models.V1ObjectMeta
In turn, V1ObjectMeta has creationTimestamp which is custom DateTime format org.joda.time.DateTime.
So, the reason of the error is that io.argoproj.workflow.JSON can't deserialize this joda creationTimestamp, since there is no proper type adapter registered for it.
Proposing fix taken from here https://stackoverflow.com/questions/15972856/json-using-gson-library-error-expected-begin-object-but-was-string:
In io.argoproj.workflow.JSON in constructor:
public JSON() {
    gson = createGson()
            .registerTypeAdapter(Date.class, dateTypeAdapter)
            .registerTypeAdapter(java.sql.Date.class, sqlDateTypeAdapter)
            .registerTypeAdapter(OffsetDateTime.class, offsetDateTimeTypeAdapter)
            .registerTypeAdapter(LocalDate.class, localDateTypeAdapter)
            .registerTypeAdapter(byte[].class, byteArrayAdapter)
            .registerTypeAdapter(DateTime.class, new JsonDeserializer<DateTime>() {
                @Override
                public DateTime deserialize(JsonElement json, Type typeOfT, JsonDeserializationContext context)
                        throws JsonParseException {
                    return new DateTime(json.getAsString());
                }
            }).create();
}

Version 3.3.9 solves the issue for me.

It seems that it was fixed after I moved to v3.3.9 but I still have to use --add-opens java.base/java.time=ALL-UNNAMED Is there a way around that? I'm using Java 17.

After I used v3.3.9, I found that there was still a serialization problem. It was not the original DateTime problem but the java.time.Instant problem. I created a new package io.argoproj.workflow in my project, which added JSON.java, then copy io.argoproj.workflow.JSON in the sdk source code and modify it in my JSON.java, and modify the JSON constructor as follows:
public class JSON {
//add
private InstantTypeAdapter instantTypeAdapter = new InstantTypeAdapter();
//edit
public JSON() {
        gson = createGson()
                .registerTypeAdapter(Date.class, dateTypeAdapter)
                .registerTypeAdapter(Instant.class, instantTypeAdapter)
                .registerTypeAdapter(java.sql.Date.class, sqlDateTypeAdapter)
                .registerTypeAdapter(OffsetDateTime.class, offsetDateTimeTypeAdapter)
                .registerTypeAdapter(LocalDate.class, localDateTypeAdapter)
                .registerTypeAdapter(byte[].class, byteArrayAdapter)
                .create();
    }
//add
public static class InstantTypeAdapter extends TypeAdapter<Instant> {

        private Instant dateFormat;

        public InstantTypeAdapter() {
        }

        public InstantTypeAdapter(Instant instant) {
            this.dateFormat = dateFormat;
        }

        public void setFormat(Instant instant) {
            this.dateFormat = dateFormat;
        }

        @Override
        public void write(JsonWriter out, Instant date) throws IOException {
            if (date == null) {
                out.nullValue();
            } else {
                out.value(FORMATTER.format(date));
            }
        }

        @Override
        public Instant read(JsonReader in) throws IOException {
            try {
                switch (in.peek()) {
                    case NULL:
                        in.nextNull();
                        return null;
                    default:
                        String date = in.nextString();
                        if (date == null) {
                            return null;
                        }
                        return FORMATTER.parse(date, Instant::from);

                }
            } catch (IllegalArgumentException e) {
                throw new JsonParseException(e);
            }
        }
    }

}

}

@alexec could the fix described by @sanqiuli  be included in the next release? I can also open a new issue if needed.

authors: alexec jkldrr kodjo-anipah kulinskyvs mortemate sanqiuli sunheng vcarluer


text:
chore: remove unused pods/exec role

Fixes #13307
Motivation

pods/exec was used for legacy executors (e.g. k8sapi),
these legacy executors are removed since v3.4.0, thus removing the role
(we are currently using emissary executor)
Modifications

Verification

not applicable,
controller signalling pod termination due timeout is done through exec
https://github.com/argoproj/argo-workflows/blob/a929c8f4dd03460d0f1e5ab2937dd2990a659d81/workflow/common/util.go#L62


text:
SSO with RBAC fails when using email addresses (works on latest)

Summary
What happened/what you expected to happen?

After enabling SSO the next step was to enable Google Auth and with it authorization based on the email address. This feature already had a PR #4644 already merged into master. The issue is that the feature works properly using the latest tag, but doesn't work with the latest release.
Any plans to include the PR #4644 in the next release?

Diagnostics
What Kubernetes provider are you using?

AWS EKS 1.16

What version of Argo Workflows are you running?

2.12.5

Message from the maintainers:
Impacted by this bug? Give it a 👍. We prioritise the issues with the most 👍.

I’ve had at least 3 requests to back port this feature to 2.12.
Hopefully this will happen, maybe even this week @simster7

I’ve had at least 3 requests to back port this feature to 2.12.
Hopefully this will happen, maybe even this week @simster7

This is out on https://github.com/argoproj/argo/releases/tag/v2.12.6

This is out on https://github.com/argoproj/argo/releases/tag/v2.12.6

authors: alexec covidium simster7

repo: argoproj/argo


text:
Error: slug must be lowercase alphanumeric and may contain /.-_

Hello,
I was attempting to migrate to the new CI/CD workflows and noticed a bug in ariga/atlas-action/migrate/lint@v1.
The error was provided: Error: slug must be lowercase alphanumeric and may contain /.-_
From what I can gather, my dir-name unfortunately has uppercase characters, and is causing the linting action to fail.

Use your dir slug , you should be able to find it in the project page, the part or the URL after atlas://

Hello @xbreid, please try to rename your directory on the Setting page. Convert its name to only lowercase character and try again. If it doesn't help, please let me know with more detail (tenant / dir's name via) - privately. So, I can help you on our side.

@giautm thanks! reached out to you on Discord.

authors: giautm rotemtam xbreid

repo: ariga/atlas-action


text:
🛑 arillo.net is down

In dc95e6b, arillo.net (https://www.arillo.net) was down:

HTTP code: 0
Response time: 0 ms

Resolved: arillo.net is back up in 73b3ac8 after 11 minutes.

repo: arillo/upptime


text:
Capybara::Poltergeist::DeadClient

Hai Team,
I built PhantomJs 2.01 by compiling from source.  I built it on my Gentoo Linux machine with the following
commands
git clone git://github.com/ariya/phantomjs.git
cd phantomjs
git checkout 2.0
./build.sh
while building I got the error
cc1plus: error: -Werror=unused-but-set-variable: No option -Wunused-but-set-variable
make[2]: *** [.obj/db/builder.o] Error 1
make[2]: Leaving directory /data/phantomjs/src/qt/qtwebkit/Source/ThirdParty/leveldb' make[1]: *** [sub-Target-pri-make_first] Error 2 make[1]: Leaving directory /data/phantomjs/src/qt/qtwebkit/Source/ThirdParty/leveldb'
make: *** [sub-Source-ThirdParty-leveldb-leveldb-pro-make_first-ordered] Error 2
which I overcome by commenting out below 2 lines in src/qt/qtwebkit/Source/ThirdParty/leveldb/Target.pri;
QMAKE_CXXFLAGS_WARN_ON += -Wno-error=unused-but-set-variable
QMAKE_CXXFLAGS += -Wno-error=unused-but-set-variable
( as suggested in https://github.com/ariya/phantomjs/issues/12623 )
My build was successful but when I try to visit a page I get the  below error,
page.visit("http://phantomjs.org/quick-start.html")
{"name":"visit","args":["http://phantomjs.org/quick-start.html"]}
1   0x7ffd0ecbee27 /usr/local/bin/phantomjs(+0x1c3fe27) [0x7ffd0ecbee27]
2   0x7ffd0ea08f07 /usr/local/bin/phantomjs(+0x1989f07) [0x7ffd0ea08f07]
3   0x7ffd0ea0a817 /usr/local/bin/phantomjs(+0x198b817) [0x7ffd0ea0a817]
4   0x7ffd0ea188d4 /usr/local/bin/phantomjs(+0x19998d4) [0x7ffd0ea188d4]
5   0x7ffd0ebfbebd /usr/local/bin/phantomjs(+0x1b7cebd) [0x7ffd0ebfbebd]
6   0x7ffd0ebf7d39 /usr/local/bin/phantomjs(+0x1b78d39) [0x7ffd0ebf7d39]
7   0x7ffd0eb0b7f0 /usr/local/bin/phantomjs(+0x1a8c7f0) [0x7ffd0eb0b7f0]
8   0x7ffcc7d62c9a [0x7ffcc7d62c9a]
PhantomJS has crashed. Please read the crash reporting guide at
http://phantomjs.org/crash-reporting.html and file a bug report at
https://github.com/ariya/phantomjs/issues/new.
Please attach the crash dump file:
/tmp/2f89d147-4885-a5f2-3e245e49-2580b12f.dmp
{"name":"set_debug","args":[true]}
{"response":true}
Capybara::Poltergeist::DeadClient: Capybara::Poltergeist::DeadClient
from /data/Automation/shared/bundled_gems/ruby/1.9.1/gems/poltergeist-1.6.0/lib/capybara/poltergeist/server.rb:33:in send' 	from /data/Automation/shared/bundled_gems/ruby/1.9.1/gems/poltergeist-1.6.0/lib/capybara/poltergeist/browser.rb:316:in command'
from /data/Automation/shared/bundled_gems/ruby/1.9.1/gems/poltergeist-1.6.0/lib/capybara/poltergeist/browser.rb:31:in visit' 	from /data/Automation/shared/bundled_gems/ruby/1.9.1/gems/poltergeist-1.6.0/lib/capybara/poltergeist/driver.rb:95:in visit'
from /data/Automation/shared/bundled_gems/ruby/1.9.1/gems/capybara-2.4.4/lib/capybara/session.rb:227:in visit' 	from (irb):4 	from /data/Automation/shared/bundled_gems/ruby/1.9.1/gems/railties-3.2.9/lib/rails/commands/console.rb:47:in start'
from /data/Automation/shared/bundled_gems/ruby/1.9.1/gems/railties-3.2.9/lib/rails/commands/console.rb:8:in start' 	from /data/Automation/shared/bundled_gems/ruby/1.9.1/gems/railties-3.2.9/lib/rails/commands.rb:41:in <top (required)>'
from script/rails:6:in require' 	from script/rails:6:in '
Could you guys help me to solve this issue ?

Is this happening every time you use it? Generally DeadClient errors are intermittent and don't persist.

This solve our problems until now
page.execute_script('if(localStorage && localStorage.clear) localStorage.clear()')

authors: IDragonfire acconrad madhuA14

repo: ariya/phantomjs


text:
Modernizing

Standardizing for portability,  Modernizing to improve the maintainability of the code, and
making old code work because it contains old extensions or removed features all overlap
but have unique issues.  One resource to draw on or perhaps to update and expand is
https://fortranwiki.org/fortran/show/Modernizing+Old+Fortran

Thanks, I will check it, the main goal was to document idioms that have
been used in the past and are still being found in source code. But some
guidance as how to modernise things is certainly within scope.
Regards,
Arjen
Op wo 28 jun 2023 om 10:35 schreef urbanjost @.***>:

Standardizing for portability, Modernizing to improve the maintainability
of the code, and
making old code work because it contains old extensions or removed
features all overlap
but have unique issues. One resource to draw on or perhaps to update and
expand is
https://fortranwiki.org/fortran/show/Modernizing+Old+Fortran
—
Reply to this email directly, view it on GitHub
https://github.com/arjenmarkus/old-programming-idioms/issues/2, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAN6YRYAC6PWVXTPPTZ2H3LXNPUEDANCNFSM6AAAAAAZWWADEI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have added a reference to the Wiki page. And added one somewhat obscure feature regarding I/O that I found there.

Looks good. Nice examples.  Would make an interesting set of test cases or examples for modernizing tools like SPAG.

authors: arjenmarkus urbanjost

repo: arjenmarkus/old-programming-idioms


text:
fix(deps): bump

Applied mkpr on undefined
/tmp/mkpr.sh

:tada: This PR is included in version 10.0.35 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
merge package from arlac77/npm-package-template

.travis.yml

chore(travis): remove node versions 10
chore(travis): add node versions 10.1

:tada: This PR is included in version 1.0.6 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
merge package from arlac77/npm-package-template

package.json

chore(package): rollup@^1.9.0
chore(scripts): cover@#overwrite c8 --temp-directory build/coverage ava && c8 report -r lcov --temp-directory build/coverage
chore(package): add nyc from template
chore(package): set $.ava.require='esm' as in template
chore(package): set $.ava.files='tests/-test.js,tests/-test.mjs' as in template
chore(package): set $.ava.extensions='js,mjs' as in template

:tada: This PR is included in version 2.1.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


text:
NaN Values on some JVM metrics

Seeing NaN reported for several metric values...
Example:
`

Element
Value

jvm_memory_used{app_kubernetes_io_name="clouddriver",armSpinSvcVer="2.22.11",container="clouddriver",customerEnvName="testing",customerName="jasonmcintosh",endpoint="7002",id="CodeHeap 'non-nmethods'",instance="10.1.15.14:7002",job="clouddriver",lib="aop",libVer="v1.1.3",memtype="NON_HEAP",namespace="spinnaker",ossSpinSvcVer="6.11.1-20201012160101",pod="spin-clouddriver-8878c977b-nnxjm",spinSvc="clouddriver",spinnakerRelease="1.22.2",version="6.11.1-20201012160101"}
NaN

`

I'm pretty strongly suspicious that this is something in micrometer:
https://github.com/micrometer-metrics/micrometer/issues/2279
SO I think this may be just because there are different metric names for JVM memory and some that are referenced and then GC'd.

Apparently what happens is micrometer uses jvm.memory.used, but SPRING uses jvm.memory.used.bytes from the research done thus far.  I'd THINK we should actually filter out jvm_memory_used (e.g. jvm.memory.used by id) in favor of the spring native ones.  I'd suspect we see this as a result of ACTUALLY integrating more fully with micrometer & spring vs. the monitoring daemon translating spectator.  FYI @kskewes
this likely would affect other dashboards/usage.  Wondering if this is consistent across all the services.

Apparently what happens is micrometer uses jvm.memory.used, but SPRING uses jvm.memory.used.bytes from the research done thus far.  I'd THINK we should actually filter out jvm_memory_used (e.g. jvm.memory.used by id) in favor of the spring native ones.  I'd suspect we see this as a result of ACTUALLY integrating more fully with micrometer & spring vs. the monitoring daemon translating spectator.  FYI @kskewes
this likely would affect other dashboards/usage.  Wondering if this is consistent across all the services.

Note, still digging - Orca DOES still use jvm_memory_used.  I need to see if there's a library mismatch or something else goofy going on.  I think this might be a case where some services are mis-matched on library versions.

Note, still digging - Orca DOES still use jvm_memory_used.  I need to see if there's a library mismatch or something else goofy going on.  I think this might be a case where some services are mis-matched on library versions.

Nice sleuthing.
IIRC it's only Orca that seems to be doing something different. Away from computer but can check next week..

Nice sleuthing.
IIRC it's only Orca that seems to be doing something different. Away from computer but can check next week..

Meh, not sure it's great sleuthing YET... still digging into what's going on.  LOCALLY, at least core metrics don't seem duplicated, but I need to actually trigger some behavior to see what's going on - I've got a pretty solid idea what's up but need to get tracing going ;)

Meh, not sure it's great sleuthing YET... still digging into what's going on.  LOCALLY, at least core metrics don't seem duplicated, but I need to actually trigger some behavior to see what's going on - I've got a pretty solid idea what's up but need to get tracing going ;)

Anyone been able to pin down what needs to change on Orca for jvm metrics?

Started to looking into this:
% curl -s spin-orca.spinnaker:8083/aop-prometheus | grep jvm | grep TYPE | sort
# TYPE jvm_buffer_count gauge
# TYPE jvm_buffer_memoryUsed gauge
# TYPE jvm_gc_allocationRate_total counter
# TYPE jvm_gc_liveDataSize gauge
# TYPE jvm_gc_maxDataSize gauge
# TYPE jvm_gc_pause_seconds summary
# TYPE jvm_gc_pause_seconds_max gauge
# TYPE jvm_gc_promotionRate_total counter
# TYPE jvm_memory_committed gauge
# TYPE jvm_memory_max gauge
# TYPE jvm_memory_used gauge

% curl -s spin-clouddriver.spinnaker:7002/aop-prometheus | grep jvm  | grep TYPE | sort
# TYPE jvm_buffer_count_buffers gauge
# TYPE jvm_buffer_memoryUsed gauge
# TYPE jvm_buffer_memory_used_bytes gauge
# TYPE jvm_buffer_total_capacity_bytes gauge
# TYPE jvm_classes_loaded_classes gauge
# TYPE jvm_classes_unloaded_classes_total counter
# TYPE jvm_gc_allocationRate_total counter
# TYPE jvm_gc_liveDataSize gauge
# TYPE jvm_gc_live_data_size_bytes gauge
# TYPE jvm_gc_maxDataSize gauge
# TYPE jvm_gc_max_data_size_bytes gauge
# TYPE jvm_gc_memory_allocated_bytes_total counter
# TYPE jvm_gc_memory_promoted_bytes_total counter
# TYPE jvm_gc_pause_seconds summary
# TYPE jvm_gc_pause_seconds_max gauge
# TYPE jvm_gc_promotionRate_total counter
# TYPE jvm_memory_committed gauge
# TYPE jvm_memory_committed_bytes gauge
# TYPE jvm_memory_max gauge
# TYPE jvm_memory_max_bytes gauge
# TYPE jvm_memory_used gauge
# TYPE jvm_memory_used_bytes gauge
# TYPE jvm_threads_daemon_threads gauge
# TYPE jvm_threads_live_threads gauge
# TYPE jvm_threads_peak_threads gauge
# TYPE jvm_threads_states_threads gauge

carvanitis@Christoss-MacBook-Pro armory-observability-plugin % curl -s spin-front50.spinnaker:8080/aop-prometheus | grep jvm  | grep TYPE | sort
# TYPE jvm_buffer_count_buffers gauge
# TYPE jvm_buffer_memoryUsed gauge
# TYPE jvm_buffer_memory_used_bytes gauge
# TYPE jvm_buffer_total_capacity_bytes gauge
# TYPE jvm_classes_loaded_classes gauge
# TYPE jvm_classes_unloaded_classes_total counter
# TYPE jvm_gc_allocationRate_total counter
# TYPE jvm_gc_liveDataSize gauge
# TYPE jvm_gc_live_data_size_bytes gauge
# TYPE jvm_gc_maxDataSize gauge
# TYPE jvm_gc_max_data_size_bytes gauge
# TYPE jvm_gc_memory_allocated_bytes_total counter
# TYPE jvm_gc_memory_promoted_bytes_total counter
# TYPE jvm_gc_pause_seconds summary
# TYPE jvm_gc_pause_seconds_max gauge
# TYPE jvm_gc_promotionRate_total counter
# TYPE jvm_memory_committed gauge
# TYPE jvm_memory_committed_bytes gauge
# TYPE jvm_memory_max gauge
# TYPE jvm_memory_max_bytes gauge
# TYPE jvm_memory_used gauge
# TYPE jvm_memory_used_bytes gauge
# TYPE jvm_threads_daemon_threads gauge
# TYPE jvm_threads_live_threads gauge
# TYPE jvm_threads_peak_threads gauge
# TYPE jvm_threads_states_threads gauge

NaN values appear on for all services:

jvm_memory_max
jvm_memory_committed
jvm_memory_used
jvm_buffer_count
jvm_buffer_memoryUsed

At the same time Orca doesnt report the same JVM metrics as the rest of services. I think we may have 2 issues here?

Orca doesnt report the same JVM metrics as the rest of the services (missing metrics)
And the micrometer issue @jasonmcintosh mentioned above

@jasonmcintosh @kskewes Managed to track down the bug(?) in Orca. So coming from here.
The Orca sql pool stats for spectator is using the Hikari library which requires PrometheusMeterRegistry. So there is an early instantiated of the Bean causing the Observability plugin not to register the metrics.
Seems a poor implementation on Orca side but will try to see if we can handle a fix in the Observability plugin. This will resolve also https://github.com/armory-plugins/armory-observability-plugin/issues/33

I think there are 2 issues which are mixed up here:

Spectator metrics result in NaN cause holding weak references and being GCed
Micrometer metrics (e.g. JVM, logback,etc are NOT exported)

1 is a common issue across all the spinnaker services, which we fixed for some relevant cases (e.g Igor)
2 instead, as mentioned above, is limited to Orca, and we noticed cause some of our common dashboards were empty.
The most visible example of 2 for me was the JVM metrics ones:

jvm_memory_used --> NaN
jvm_memory_used_bytes (micrometer) was just not there

I manage to fix the issue on Orca in our fork: as @christosarvanitis correctly mentioned, the child classes of AbstractMetricsPostProcessor are preventing ArmoryObservabilityCompositeRegistry to be processed by Spring MeterRegistryPostProcessor: these means no micrometer binders are attached to the registry.
There's a warning log which describe the issue:
'io.armory.plugin.observability.registry.ArmoryObservabilityCompositeRegistry' of type [io.armory.plugin.observability.registry.ArmoryObservabilityCompositeRegistry] is not eligible for getting processed by all BeanPostProcessors (for example: not eligible for auto-proxying)

The culprit is the @Autowired the child classes: https://github.com/spinnaker/orca/blob/master/orca-core/src/main/java/com/netflix/spinnaker/orca/telemetry/ThreadPoolMetricsPostProcessor.java#L34
As per Spring Autowired doc:
Note that actual injection is performed through a BeanPostProcessor which in turn means that you cannot use @Autowired to inject references into BeanPostProcessor or BeanFactoryPostProcessor types.

So, without changing the design (e.g. moving away from a BeanPostProcessor or from an abstract class), a simple @Lazy on all the 3 child classes will make the trick.
Example:
  @Autowired
  @Lazy
  public ThreadPoolMetricsPostProcessor(Registry registry) {
    super(ThreadPoolTaskExecutor.class, registry);
  }

I can submit a PR on orca with the fix as well, cause I think Orca is abusing of the dependency injection in this scenario 😄
But if you have a fork, try it out.

@dbyron-sf here it is: https://github.com/spinnaker/orca/pull/4224
As you can see, it might need Kayenta to be bumped too.

@massimo-pacher-tw HUGE thank you for fixing these :) We'd known about it, but we run APM agents for most core JVM metrics, so we'd not spent much time trying to fix OSS other than "Yep it's something in the bean handling" layer.

More thanks for @massimo-pacher-tw here as well!  This is a very big help!

This is great, thanks @massimo-pacher-tw
Also closes out: https://github.com/armory-plugins/armory-observability-plugin/issues/33

authors: battlecow christosarvanitis dbyron-sf jasonmcintosh kskewes kskewes-sf massimo-pacher-tw


text:
Document how to exclude the jOOQ Open Source Edition as a transitive dependency, when needed

Currently, it seems that SimpleFlatMapper has a transitive compile time dependency on some version of the jOOQ Open Source Edition, which is nice for new projects, but can get in the way when:

People want to use newer versions of SimpleFlatMapper
People use the commercial distributions of jOOQ (see https://stackoverflow.com/q/56546414/521799)

Perhaps it would be useful to either:

Make the jOOQ dependency provided
Explain in the docs how to exclude the transitive dependency, to make people aware of how it works: https://simpleflatmapper.org/0106-getting-started-jooq.html

I think provided makes sense

Indeed, especially since in the case of SimpleFlatMapper, the two dependencies (SFM and jOOQ) are both quite independent of one another and can both live without the other, so it is likely the user will want to depend on both explicitly...

also you are more likely to already have jooq, spring jdbc or any other
I meant to do that at some point just never got to tidy that up ...

authors: arnaudroger lukaseder

repo: arnaudroger/SimpleFlatMapper


text:
🛑 NWTFV is down

In 9f71788, NWTFV (https://nwtfv.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NWTFV is back up in 56753fc.

repo: arnef/status


text:
🛑 NWTFV is down

In 9dfad7d, NWTFV (https://nwtfv.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: NWTFV is back up in fe26ad3.


text:
Portfolio: Add-DesktopVersion

I created a branch for adding Desktop Version
I used media queries to add Desktop Version.
Fixed Style linter errors, and ensured no linter errors were left.

I made the adjustments as suggested by the reviewer

Hey @Nemwel-Boniface  thank you for your consideration, it means a lot to me, I had lost hope in the program because of the sequence of the reviews. I will correct the work as suggested and thank you for the Guidance. Meanwhile we are approaching the deadline and am not yet at 100% . Thank You

repo: arnoldnekemiah/portfolio-m


text:
Type Writer Effect

Issue Type:

[x] Feature Request

Describe the bug

Create a Type writer effect

Screenshots

@arpit456jain , please assign me

Do enhance the UI


text:
multiple uses of requeue with GetReconcileResyncPeriod - defaults to 10hours

There are about 10 references to GetReconcileResyncPeriod, which has a default of 10hrs, I think this is being used in error. Either we don't requeue in this case or use a more sensible shorter value. In any event this needs a revisit.

resolved with https://github.com/artemiscloud/activemq-artemis-operator/commit/ad2e7220dc756f55a763b3387a5fc5b1413a1fef
via: https://github.com/artemiscloud/activemq-artemis-operator/pull/331

repo: artemiscloud/activemq-artemis-operator


text:
🛑 CryptPad is down

In 2055715, CryptPad (https://pad.artemislena.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CryptPad is back up in f6d4c64.

repo: artemislena/upptime


text:
🛑 Matrix (server) is down

In 11aac51, Matrix (server) (https://matrix.artemislena.eu:8448/_matrix/static) was down:

HTTP code: 502
Response time: 3416 ms

Resolved: Matrix (server) is back up in 41a0da7.


text:
🛑 Nitter is down

In 2f091b2, Nitter (https://tw.artemislena.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: Nitter is back up in f8f60e5.


text:
🛑 Invidious is down

In 3f96e1b, Invidious (https://yt.artemislena.eu) was down:

HTTP code: 502
Response time: 5603 ms

Resolved: Invidious is back up in ebfee1b after 9 minutes.


text:
🛑 CryptPad is down

In 15ec891, CryptPad (https://pad.artemislena.eu) was down:

HTTP code: 0
Response time: 0 ms

Resolved: CryptPad is back up in 9ff9691 after 11 minutes.


text:
gnd-import for Persons

paste a gnd-uri to create a new Person

closed with https://github.com/acdh-oeaw/pmb-service/commit/60e821140b711a1f290464e775f3644619e7bbae

repo: arthur-schnitzler/pmb-service


text:
Feature: added stale flag in request return object

This PR is an attempt to add the request response "stale" flag that is present in the axios-cache-adapter. This flag says whether or not the response is from staled cache. This would be returned along with the "cached" flag. Please let me know if there's anything that I'm missing.

please also add tests

Ci is failing

@arthurfiorette, I added some tests and fixed the failing ones. I also added some comments as replies above that may have been missed. If you could review those, that would be great.

thanks for your work!

authors: MerryCello arthurfiorette

repo: arthurfiorette/axios-cache-interceptor