Customise default lint rules

Based on the following line in the documentation:

The linting is easily configurable with remark-lint.

That implies to me that I should be using a .remarkrc file. What is unclear to me is where that file lives in relation to atom.io. I assumed it would be somewhere under ~/.atom (on Mac) and wouldn't rely on an external instance of remark-lint and a ~/.remarkrc file.
Let me know if I'm completely off base.

Like most configuration files it should be project based and live at the root of each project. That way everyone working on the project gets the same configuration.
If for some reason that doesn't work for you, usually you can put a configuration file in your home directory (assuming all projects are within that), or some other parent folder for all your projects. @wooorm can confirm as he is the author of the linter as well as the maintainer of this package :wink:.

Yes, it is as @Arcanemagus mentioned. The third and fourth items on the Cascade docs for .remarkrc apply here.
I can imagine that being a bit hard to find out though, do you have suggestions regarding what we could do to get this information across more easily?

@speedRS Ping!

As I mention here on the main linter repo (#1056)…

While I agree that when working on large/r projects, config files should be kept with the project; I think it’s good to have a global config for each linter as a fallback if one doesn’t exist. Also what if I have a bunch of smaller/private projects which I want to share a common config?

As it stands, some linter- packages have this option and others don’t. This inconsistency leads to this seemingly unnecessary “meta" configuration headache. Often the suggestion is to further pollute the HOME directory with yet another . file, which I don’t want to do.

This linter- package currently doesn’t have a setting to specify a custom config. In this case, looking at the remark -help, it could be done by passing -c ~/path/to/default/config.json to the underlying remark binary.
linter-sass-lint is a good example of having these options.

@danielbayley What you are talking about is overriding the configuration automatically found by the linter, not where to place the configuration for proper detection in the first place, which is what this issue is about.
(Though a PR for that functionality would be nice, as there are people that use that for some reason :wink:)

Agreed, as that’s a different issue, I’d suggest opening a separate report.
However, I’m not interested in building it. PRs are welcome though.


Fit Context Menu Height to Menu

Resolves
Resolves LLK/scratch-gui#111
Proposed Changes
Calculate div height from as the sum of the heights of all the menu items instead of passing the window height.
Reason for Changes
Making the menu fit the content prevents scroll bar creation. Possible exception at the very bottom of the screen, but that should be fixed by limiting x & y in a different pull request.
Test Coverage
None added.

@SillyInventor I think I might be misunderstanding the intent, but this seems to behave the same way as before. Which part of #111 did this intend to solve? Is it a browser-specific fix?

Closing pending feedback from @SillyInventor


Result file changes

The following modifications to the result file (formerly known as 'done' file) are needed:

[x] Add key name profile containing the profile name as the value
Referenced from: https://github.com/TheAcharya/MarkerData/issues/9
[x] Add key name exportFolder containing the final output path of the extracted files
[x] Change --done-filename CLI option (MarkersExtractor.doneFilename) to --result-file-path (MarkersExtractor.resultFilePath) which can accept a full path.
That way shell tools can know where to find the done file and in turn it can tell them where the final output folder is.
Referenced from: https://github.com/TheAcharya/MarkerData/issues/16
[x] Remove --create-done-file flag as it will be redundant with the --result-file-path option. If --result-file-path is provided, it implicitly means that a done file should be created. If not supplied, no done file is created.

I'm going to change 'Done File' nomenclature to 'Export Result'. It's more descriptive.
Some of the key names will change to be more consistent and descriptive as well.

This is done and will be in 0.2.6.

Will close this for now.


Need to handle publishing AssessmentProfile and LearningOpportunityProfile

We had talked about the probable need to be able to publish assessments ctdl:AssessmentProfile and learning opportunities ctdl:LearningOpportunitProfile as separate top level documents. We have the latter in our json classes, and schema.
I tried to publish an assessment profile and received the following error:
Cannot load json-schema. The property '@type' has an invalid value 'ctdl:AssessmentProfile'
What changes are necessary to enable publishing these objects?

Please excuse if I am off base. I am still in Europe and only checking intermittently. I am confused by this, Mike, because you seem to use "assessments" and "learning opportunities" and their profiles interchangeably.  We have both ctdl:Assessment [1] and ctdl:AssessmentProfile [2] as well as ctdl:LearningOpportunity [3] and ctdl:LearningOpportunitProfile [4]. I assume here that you are talking only about [2] and [4]. Correct?
[1] http://www.credreg.net/page/propertiesviewer#Assessment
[2] http://www.credreg.net/page/propertiesviewer#AssessmentProfile
[3] http://www.credreg.net/page/propertiesviewer#LearningOpportunity
[4] http://www.credreg.net/page/propertiesviewer#LearningOpportunityProfile

Yes, I am referring to the AssessmentProfile and LearningOpportunityProfile.
I sometimes guilty of lazy typing (ie skipping the profile suffix), and will try to be more accurate in these discussions.

@mparsons1953  do you have some samples (json raw metadata) for AssessmentProfile?
I tried to grab them from http://ctitest.siuccwd.com/Search/V2?keywords=&searchType=assessment&autosearch=true
but I'm getting "Error. An error occurred while processing your request."
For LearningOpportunityProfile it worked

Anderson
We have been remiss in updating our test site. I will do an update shortly.
However, I think you have access to the production site. So you can depend on the site (usually) being error free.
https://credentialfinder.org
Michael Parsons
Illinois workNet (TM)
Southern Illinois University Carbondale
Direct Phone #:<PHONE_NUMBER>
General Phone #<PHONE_NUMBER> x5858
Toll Free: 1-800-252-4822 x5858
From: Anderson Pierre Cardoso<EMAIL_ADDRESS>Sent: Wednesday, October 19, 2016 12:06 PM
To: learningtapestry/metadataregistry
Subject: Re: [learningtapestry/metadataregistry] Need to handle publishing AssessmentProfile and LearningOpportunityProfile (#78)
@mparsons1953https://github.com/mparsons1953 do you have some samples (json raw metadata) for AssessmentProfile?
I tried to grab them from http://ctitest.siuccwd.com/Search/V2?keywords=&searchType=assessment&autosearch=true
but I'm getting "Error. An error occurred while processing your request."
For LearningOpportunityProfile it worked
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/learningtapestry/metadataregistry/issues/78#issuecomment-254877072, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGkzLpXlIWj7B7FEdKCLlIkjpQVdk2Mhks5q1k3_gaJpZM4KaH-P.

@mparsons1953 another question:
for the schema.org  properties, such as name and description, which is the correct form: schema:name or ctdl:name. Because the serialization schema says that the ctdl:name is required, but the data samples have schema:name.

Anderson
I have updated our test server. However our office (where our test server is located) is having internet issues, so you may not be able to access the site for now.
As noted previously, the user id used for the test server also has access to the production site.
Sent from my Verizon, Samsung Galaxy smartphone so
-------- Original message --------
From: Anderson Pierre Cardoso<EMAIL_ADDRESS>Date: 10/19/16 12:06 PM (GMT-06:00)
To: learningtapestry/metadataregistry<EMAIL_ADDRESS>Subject: Re: [learningtapestry/metadataregistry] Need to handle publishing AssessmentProfile and LearningOpportunityProfile (#78)
@mparsons1953https://github.com/mparsons1953 do you have some samples (json raw metadata) for AssessmentProfile?
I tried to grab them from http://ctitest.siuccwd.com/Search/V2?keywords=&searchType=assessment&autosearch=true
but I'm getting "Error. An error occurred while processing your request."
For LearningOpportunityProfile it worked

You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://github.com/learningtapestry/metadataregistry/issues/78#issuecomment-254877072, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AGkzLpXlIWj7B7FEdKCLlIkjpQVdk2Mhks5q1k3_gaJpZM4KaH-P.

sorry, I forgot to mention. I grabbed some samples on https://credentialfinder.org
they are being use as (real case) fixtures for our testing suite.
The server is up to date with these changes, so you can add and search assessment_profiles and learning_opportunity_profiles already.


Get popup whenever i add new node in list

Hello all,
How i can get to know that whenever i add new node i want some popup box or may be some message.
thanks.!

Look at the callbacks in the README.md file, you can use things like the dropped event


Reset button in Replay window does not work as expected.

Reset of the replay needs two clicks on the reset button.

The trackedobjects prefab had to many empty emelemts, this is fixed since the first release.


Use consistently bytes and strings

Hello @matteobachetti! Thanks for submitting the PR.

In the file srttools/core/calibration.py, following are the PEP8 issues :

Line 31:1: E722 do not use bare except'
Line 253:17: E722 do not use bare except'
Line 440:9: E722 do not use bare except'
Line 491:9: E722 do not use bare except'

In the file srttools/core/inspect_observations.py, following are the PEP8 issues :

Line 51:13: E722 do not use bare except'

In the file srttools/core/utils.py, following are the PEP8 issues :

Line 5:1: E302 expected 2 blank lines, found 1


remove 'wrench' articles that have been ported

Fixes #962
Fixes #490
Fixes #492
Several not-yet-written articles have been covered by the port of the
C# content from MSDN.  These still need to be reviewed and updated, but
they are all now present.
The TOC contains links to these topics in both locations. (That’s a temporary condition until more content gets reviewed.)
/cc @mairaw @cartermp

LGTM

I know that customers are not pointing to those, but to be on the safe side I'd just keep them with the redirect metadata to make sure we don't start creating SEO issues. Khairun was explaining to me that if a page is in our site map which search engines then crawl and then it starts to give 404s, it gives a bad signal to search and affects quality metrics for the site in search engine.

@mairaw I updated and put in the redirects.

When you removed the files, a couple of the links were broken (see build report). Preferably the topics would link to the final destination since redirect doesn't work on GH.

closing and reopening to start the build again.

@mairaw: The build now passes, with the redirects working.

Cool. Yes, since the files were added back the links are no longer broken. But I still think the best would be to fix those links to go directly to their destination. Like if you go here and click on the generic link, you land here: https://github.com/BillWagner/docs/blob/clean-wrench-nodes/docs/csharp/generics.md. But for docs, it's ok to merge as-is.

@mairaw I understand now. I updated the links that were pointing to those topics that now have redirects.


about this sorting shader

shouldn't you be able to add the location of the pixels to the calculated value that you later sort by, then sort the whole columns with those tuples at once, and then in the next pass you collect the slices like you do now with this spawn for every pixel but every surviving thread can now do a linear scan over the presorted column, filtering the ones it is not interrested in out (it knows what it's interrested in as of now: start and length, in the scan just ignore values which position lies outside, the remainder stays sorted)
sorry, i dont have the game and no idea to run this stuff on linux, otherwise i would probably try to cobble together a pull request.

i dunno implement it and find out


Update farming skill calculator with Sq'irk fruits and POH garden plants

closes #11262

Need to check about bonus XP

Both sq'irks and garden plants XP is affected by farming outfit


PHP Tests: outputs the tests uuids

The PHP SKD already provided the capability to set your own UUID (and provide it as parameter). Alls this does is output it while testing, so we can check tracing for these uuids.

Put a bit more work into it. Because the Functions did not return the uuid so the customer had no chance to compare the it to its requests. Therefore I split up into to function one that returns the verdictResponse object and one that just calls that funtion and only returns the verdict as string.

I keept the old ones mostly for compatibility reasons.


Make different versions of MeiliSearch available on the DO Marketplace

Following this discussion here: https://github.com/meilisearch/MeiliSearch/discussions/2102#discussioncomment-2036706
Currently, only one version of MeiliSearch (often the latest) is available on the DO marketplace. This is not always convenient for our users because they might need to use an older version of MeiliSearch, for some reason.

I am just curious why would you want to be able to select a different version than current? I would think you would want the latest version for stability.
Have you considered once you have a droplet properly configured, create an image you can redeploy then on each new droplet run setup again.
(Note: I am just an engineer and developer looking at deploying MS)

Hi @ams-ryanolson,
Thank you for your interest in Meilisearch! You are right, while waiting for version 1 it is always better to use the last version of Meilisearch which is the most stable. But we also had a lot of users who use Meilisearch and it could be complicated for them if they want to redeploy if they need a specific version of Meilisearch and we would like to offer this only to them.
However, we will probably need this feature once we get past version 1.

@alallema Again, what you can do is one you spin up the droplet and configure it as needed, you can create a snapshot of it and name it something like (client-name-version-number) then store it in your or their DO account. If there is ever an issue, you can spin up a new instance of that droplet from the snapshot then repoint your DNS record to the new droplet or just change the IP in the app.
I hope this helps you fix your issue for now at least.

@ams-ryanolson, thank you for your advice 😊  ! Yes, for now, we will leave things as they are, it's not really a priority but it could have been practical

Closing this issue due to the depreciation of this repository


.hdll decompilation doesn't work

I want to decompile dead cells source code, but when I write .\hlbc.exe '.\Dead Cells\discord.hdll', I get Error: Invalid magic bytes (expected [72, 76, 66], found [77, 90, 144]). The same with ui.hdll Error: Invalid magic bytes (expected [72, 76, 66], found [77, 90, 144])

hlbc is not for decompiling native code contained in .hdll files. You should launch hlbc-gui and then load hlboot.dat or whatever the bytecode file is named.

hlboot.dat isn't included as a separate file in Dead Cells... but it is embedded in the main executable. Here's a small Python script I wrote to extract it:
import warnings
import os

MAGIC_HEADER = b"\x48\x4C\x42" # "HLB" for hashlink bytecode
END_PADDING = b"\x58\x50\x41\x44\x44\x49\x4e\x47\x50\x41\x44\x44\x49\x4e\x47\x58" # "XPADDINGPADDINGX"

# region Configuration
OUTPUT = "boot.dat"       # Output filename
OUTPUT_IN_GAMEDIR = False # Save output in the original game dir?
###### CHANGEME #####
EXE_PATH = "D:\SteamLibrary\steamapps\common\Dead Cells\deadcells.exe"
GAME_PATH = "D:\SteamLibrary\steamapps\common\Dead Cells"
# endregion

def extract_bytecode():
    with open(EXE_PATH, "rb") as f:
        exe_data = f.read()
    hlb_start = exe_data.find(MAGIC_HEADER)
    if hlb_start == -1:
        raise ValueError("Hashlink bytecode not found in executable.")
    hlb_data = exe_data[hlb_start:]
    hlb_end = hlb_data.find(END_PADDING)
    if hlb_end == -1:
        warnings.warn("End padding not found in hashlink bytecode.")
        hlb_end = len(hlb_data)
    hlb_data = hlb_data[:hlb_end]
    return hlb_data

if __name__ == "__main__":
    hlb_data = extract_bytecode()
    with open(OUTPUT, "wb") as f:
        f.write(hlb_data)
    if OUTPUT_IN_GAMEDIR:
        with open(os.path.join(GAME_PATH, OUTPUT), "wb") as f:
            f.write(hlb_data)
    print("Hashlink bytecode extracted and saved to \"{}\".".format(OUTPUT))

.hdll files can be partially decompiled with IDA or Ghidra just like any other .dll, but the PDB files are only included with alpha releases, which you can opt-in to from Steam.

I figure it would not be that difficult to make hlbc load bytecode hidden inside another file. I'll implement that scan for HLB.


Charm in blocked status with Missing parameters: [] message

Steps to reproduce
I'm not sure how to reproduce this, or how it's even possible from looking at the code.
Expected behavior
Charm isn't in blocked status if you set access-key and secret-key or is if you don't.
Actual behavior
Charm is in blocked status even though access-key and secret-key are set.
Versions

Operating system: 22.04

Juju CLI: 2.9.44

Juju agent: 2.9.44

Charm revision: 13 (latest/stable)
Log output

Juju debug log:
2024-03-01 15:43:26 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 15:49:08 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 15:49:08 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 15:49:09 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 15:54:21 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 15:54:21 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 15:54:22 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 15:59:27 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 15:59:27 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 15:59:27 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 16:02:31 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:02:31 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event sync_s3_credentials_action.
2024-03-01 16:02:32 DEBUG unit.s3-integrator/0.juju-log server.go:316 Updated S3 connection info: {'access-key': 'REDACTED'}
2024-03-01 16:02:32 DEBUG unit.s3-integrator/0.juju-log server.go:316 Updated S3 connection info: {'secret-key': 'REDACTED'}
2024-03-01 16:04:14 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:04:14 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 16:04:14 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 16:08:28 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:08:28 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 16:08:28 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 16:13:26 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:13:26 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 16:13:27 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 16:18:31 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:18:31 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.
2024-03-01 16:18:31 INFO juju.worker.uniter.operation runhook.go:159 ran "update-status" hook (via hook dispatching script: dispatch)
2024-03-01 16:22:48 DEBUG unit.s3-integrator/0.juju-log server.go:316 Operator Framework 2.3.0 up and running.
2024-03-01 16:22:48 DEBUG unit.s3-integrator/0.juju-log server.go:316 Emitting Juju event update_status.

Worth mentioning that this application was deployed a while ago, possibly before https://github.com/canonical/s3-integrator/issues/8 was solved, so it's possible it got into this state, but now can't get out of it unless a peer-relation-changed or start event fires.

@delgod I think you have addressed this already in https://github.com/canonical/s3-integrator/commit/16d8b7eedd1b13310551523f89166facf8c66ebb
Resolved?

We saw the similar issue:

message in log Missing parameters: []
constant maintenance state (due to the newer charm revision 27, stay in maintenance even after refresh to rev 31 the latest/stable)

It has happened after the K8s pod eviction. @gtato can you please dump here the logs from our investigation.
I am pretty sure this is the same issue.

P.S. regarding initial bugreport:
2024-03-01 16:02:32 DEBUG unit.s3-integrator/0.juju-log server.go:316 Updated S3 connection info: {'access-key': 'REDACTED'}
2024-03-01 16:02:32 DEBUG unit.s3-integrator/0.juju-log server.go:316 Updated S3 connection info: {'secret-key': 'REDACTED'}

Those debug information has been removed from s3-integrator. Should be no longer topical.

It has happened after the K8s pod eviction. @gtato can you please dump here the logs from our investigation. I am pretty sure this is the same issue.

Was it #44?

here you go:
unit-s3-integrator-0: 2024-08-14 19:30:30 INFO juju.worker.upgradesteps upgrade steps for 3.4.4 have already been run.
unit-s3-integrator-0: 2024-08-14 19:30:30 INFO juju.worker.probehttpserver starting http server on <IP_ADDRESS>:65301
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.api connection established to "wss://<IP_ADDRESS>:17070/model/2b923556-aaed-46fc-8a99-26f07cf21b26/api"
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.worker.apicaller [2b9235] "unit-s3-integrator-0" successfully connected to "<IP_ADDRESS>:17070"
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.api connection established to "wss://<IP_ADDRESS>:17070/model/2b923556-aaed-46fc-8a99-26f07cf21b26/api"
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.worker.apicaller [2b9235] "unit-s3-integrator-0" successfully connected to "<IP_ADDRESS>:17070"
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.worker.migrationminion migration migration phase is now: NONE
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.worker.logger logger worker started
unit-s3-integrator-0: 2024-08-14 19:30:31 WARNING juju.worker.proxyupdater unable to set snap core settings [proxy.http= proxy.https= proxy.store=]: exec: "snap": executable file not found in $PATH, output: ""
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.worker.leadership s3-integrator/0 promoted to leadership of s3-integrator
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.agent.tools ensure jujuc symlinks in /var/lib/juju/tools/unit-s3-integrator-0
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.worker.caasupgrader abort check blocked until version event received
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.worker.caasupgrader unblocking abort check
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.worker.uniter unit "s3-integrator/0" started
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.worker.uniter hooks are retried true
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.worker.uniter.charm downloading ch:amd64/jammy/s3-integrator-27 from API server
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.downloader downloading from ch:amd64/jammy/s3-integrator-27
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.downloader download complete ("ch:amd64/jammy/s3-integrator-27")
unit-s3-integrator-0: 2024-08-14 19:30:31 INFO juju.downloader download verified ("ch:amd64/jammy/s3-integrator-27")
unit-s3-integrator-0: 2024-08-14 19:30:44 INFO juju.worker.uniter found queued "upgrade-charm" hook
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log ops 2.14.1 up and running.
unit-s3-integrator-0: 2024-08-14 19:30:44 INFO unit.s3-integrator/0.juju-log Running legacy hooks/upgrade-charm.
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log ops 2.14.1 up and running.
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log Charm called itself via hooks/upgrade-charm.
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log Legacy hooks/upgrade-charm exited with status 0.
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log Using local storage: not a Kubernetes podspec charm
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log Initializing SQLite local storage: /var/lib/juju/agents/unit-s3-integrator-0/charm/.unit-state.db.
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event upgrade_charm.
unit-s3-integrator-0: 2024-08-14 19:30:44 INFO juju.worker.uniter.operation ran "upgrade-charm" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 2024-08-14 19:30:44 INFO juju.worker.uniter found queued "config-changed" hook
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log ops 2.14.1 up and running.
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event config_changed.
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log Current configuration: {'attributes': '', 'bucket': 'redacted', 'endpoint': 'redacted', 'path': 'redacted', 'region': 'default', 's3-api-version': '', 's3-uri-style': 'path', 'storage-class': '', 'tls-ca-chain': ''}
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log Secret parameter access-key not stored inside config.
unit-s3-integrator-0: 2024-08-14 19:30:44 DEBUG unit.s3-integrator/0.juju-log Secret parameter secret-key not stored inside config.
unit-s3-integrator-0: 2024-08-14 19:30:45 DEBUG unit.s3-integrator/0.juju-log Updated S3 connection info: {'region': 'default', 'bucket': 'redacted', 'endpoint': 'redacted, 'path': 'redacted', 's3-uri-style': 'path'}
unit-s3-integrator-0: 2024-08-14 19:30:45 INFO juju.worker.uniter.operation ran "config-changed" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 2024-08-14 19:30:45 INFO juju.worker.uniter reboot detected; triggering implicit start hook to notify charm
unit-s3-integrator-0: 2024-08-14 19:30:45 DEBUG unit.s3-integrator/0.juju-log ops 2.14.1 up and running.
unit-s3-integrator-0: 2024-08-14 19:30:45 INFO unit.s3-integrator/0.juju-log Running legacy hooks/start.
unit-s3-integrator-0: 2024-08-14 19:30:45 DEBUG unit.s3-integrator/0.juju-log ops 2.14.1 up and running.
unit-s3-integrator-0: 2024-08-14 19:30:45 DEBUG unit.s3-integrator/0.juju-log Charm called itself via hooks/start.
unit-s3-integrator-0: 2024-08-14 19:30:45 DEBUG unit.s3-integrator/0.juju-log Legacy hooks/start exited with status 0.
unit-s3-integrator-0: 2024-08-14 19:30:45 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event start.
unit-s3-integrator-0: 2024-08-14 19:30:45 INFO unit.s3-integrator/0.juju-log Missing options: []
unit-s3-integrator-0: 2024-08-14 19:30:45 INFO juju.worker.uniter.operation ran "start" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 2024-08-14 19:36:47 DEBUG unit.s3-integrator/0.juju-log ops 2.14.1 up and running.
unit-s3-integrator-0: 2024-08-14 19:36:47 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event update_status.
unit-s3-integrator-0: 2024-08-14 19:36:48 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 2024-08-14 19:40:52 DEBUG unit.s3-integrator/0.juju-log ops 2.14.1 up and running.
unit-s3-integrator-0: 2024-08-14 19:40:52 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event update_status.
unit-s3-integrator-0: 2024-08-14 19:40:52 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 2024-08-14 19:45:11 DEBUG unit.s3-integrator/0.juju-log ops 2.14.1 up and running.
unit-s3-integrator-0: 2024-08-14 19:45:11 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event update_status.
unit-s3-integrator-0: 2024-08-14 19:45:11 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 2024-08-14 19:50:58 DEBUG unit.s3-integrator/0.juju-log ops 2.14.1 up and running.
unit-s3-integrator-0: 2024-08-14 19:50:58 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event update_status.
unit-s3-integrator-0: 2024-08-14 19:50:58 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)
unit-s3-integrator-0: 2024-08-14 19:56:24 DEBUG unit.s3-integrator/0.juju-log ops 2.14.1 up and running.
unit-s3-integrator-0: 2024-08-14 19:56:24 DEBUG unit.s3-integrator/0.juju-log Emitting Juju event update_status.
unit-s3-integrator-0: 2024-08-14 19:56:26 INFO juju.worker.uniter.operation ran "update-status" hook (via hook dispatching script: dispatch)

@dragomirp these logs are from the same deployment, but I didn't paste them in that issue.

@dragomirp yes, I think we can close this as duplicate for #44 . I didn't find those bugreport as you have closed it instantly! :-D
Resolved as duplicate. Tnx!


proxyWithComputed and subscribeKey

Should we be able to use subscribeKey on a computed value? This test currently fails
describe('proxyWithComputed and subscribeKey', () => {
  it('should call subscribeKey subscription when computed value changes?', async () => {
    const state = proxyWithComputed({
      count: 1,
    }, {
      doubled: snap => snap.count * 2
    })
    const handler = jest.fn()
    subscribeKey(state, 'doubled', handler)
    state.count = 2
    await Promise.resolve()
    expect(handler).toBeCalledTimes(1)
  })
})

Good point. Does subscribe work as expected with proxyWithComputed?

Yes, subscribe works and subscribeKey works with the regular properties,
just not the computed ones
On Wed, 2 Feb 2022, 14:56 Daishi Kato, @.***> wrote:

Good point. Does subscribe work as expected with proxyWithComputed?
—
Reply to this email directly, view it on GitHub
https://github.com/pmndrs/valtio/issues/350#issuecomment-1028023606, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEP4NB2Y2GPA22ZNU6KTRTUZFA3JANCNFSM5NMIPSPQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ah, now I get it.
It's because how subscribeKey is implemented now. So, it can be said, it works so by design.
We used to have a different implementation, which is changed in #177.
The old one is this:
export const subscribeKey = <T extends object>(
  proxyObject: T,
  key: keyof T,
  callback: (value: T[typeof key]) => void,
  notifyInSync?: boolean
) => {
  let prevValue = proxyObject[key]
  return subscribe(
    proxyObject,
    () => {
      const nextValue = proxyObject[key]
      if (!Object.is(prevValue, nextValue)) {
        callback((prevValue = nextValue))
      }
    },
    notifyInSync
  )
}

The old one passes your test.
I wonder if we should revert it, or accept the limitation (the proxyWithComputed and subscribeKey combo doesn't work.)

It's because how subscribeKey is implemented now. So, it can be said, it works so by design.
We used to have a different implementation, which is changed in #177. The old one is this:

Can you clarify why the new version isn't compatible?

The new version of subscribeKey checks what key is changed in the "operation"s, so it doesn't "read" the computed value.
The old version checks if the new value is changed from the previous value using Object.is, so it triggers the computation inside the callback function.

I leave it to you guys to decide which version you want, but I can explain I have a specific use case which I was trying to implement which lead to finding this issue. Essentially I have two calculated properties, one which triggers heavy updating of the UI when it changes and another which triggers a lighter update. They depend on different properties of the object, so update at different times. In order to make the UI responsive, I need to be able to detect the changes to the two calculated properties independently.
I have also tried with derived, but came across #349 .
I'm sure I can figure out a workaround, but proxyWithComputed seems like it would be the most elegant and readable solution, so I think it would be cool if it worked.

Implementation-wise, I would like to keep the newer version, because the older version can easily be implemented by a user.
So, in your use case, what is the real problem with proxyWithComputed and subscribe combo?
If that really needs it, can you define this on your end?
const subscribeKey = <T extends object, K extends keyof T>(
  proxyObject: T,
  key: K,
  callback: (value: T[K]) => void
) => {
  let prevValue = proxyObject[key]
  return subscribe(
    proxyObject,
    () => {
      const nextValue = proxyObject[key]
      if (prevValue !== nextValue) {
        callback(prevValue = nextValue)
      }
    }
  )
}

Okay, that will work. Thanks

I will leave the current implementation just because it's harder for library users to implement (which uses ops).
I think we should cover this limitation and workaround in docs eventually, but closing this for now.

This is definitely a bug, given that subscribeKey is typed on the second parameter, which offers the calculated fields, and it's a lie. Either the typing should be updated (at least dumbed down to string, if not possible to separate the calculated/non-calculated fields on the type level), or the older, more capable version should be kept in the library.
IMO, from the output of the proxy creation, whether a key is calculated or not should be irrelevant at the consumption side. If I had a dilemma of which one of competing implementations to keep in the lib as default, I'd definitely set my preference along the feature/capability aspect, rather than whether how hard users could potentially re-implement them. Users hardly care about that. On the other side, I, as a developer in a team who's responsible for recommending coding practices, have a much harder case to justify this state library when they see that I have to locally patch the lib.
I understand the technical concern. Isn't there a way to include the old one as well in the lib? I would leave the old one, and add the new one under an experimental import namespace with a dumbed down typing on the key.

Totally valid comment. Thanks for raising it again. Hm, yeah, I think we can revert to the original one, as new one doesn't provide any capabilities.


[BUG] TrackTotalHits does not allow integer input

What is the bug?
When searching, the TrackTotalHits only allows a true / false input, rather than a integer as per Rest Api document.
The opensearch dashboard allows a integer input
How can one reproduce the bug?
Enter an integer into the TrackTotalHits field within a Search method.
What is the expected behavior?
A explicit value is able to be set on TrackTotalHits
What is your host/environment?
N/A
Do you have any screenshots?

Do you have any additional context?
N/A

The fix for this bug was included in release v1.3.0.


Bridge: Reword Integrations Page

Is your feature request related to a problem? Please describe.
The bridge integrations page could be better. Currently, if a new user saw this page, they'd leave with the impression that:

Keptn only integrates with 3 tools (Azure Dev Ops, Gitlab and Jenkins)
Only the keptn-sandbox repo exists

The page could load all integrations from artifacthub, it could at least point to the integrations page. It could offer a submission box for users to suggest tooling integrations that automatically generates a Github issue in the integrations repo.
Taking it one step further, it could act like a marketplace for integrations with one-click installs.

https://github.com/keptn/keptn/issues/7378

Hi @agardnerIT
totally agree with you and luckily this happened already with Keptn 0.15 - please see screenshot:

The current "Integration" page is not that prominent anymore
A renaming happened to Common use cases
Part of the support category

https://github.com/keptn/keptn/issues/7378 is still valid (i.e., removing this button) because at this point a call to an external resource is performed that causes more troubles than value.

https://github.com/keptn/keptn/issues/5830 covers the same idea of pulling integrations from ArtifactHub to have a kind of in-product marketplace.

Closing this as the integration page was removed in #8344. Also, it's no longer planned to show the integration from ArtifactHub inside the Bridge. They'll stay at https://keptn.sh/docs/integrations/.


Failed to parse header

Hi i got this problem
Set the "Effective Caller ID Name" or  "effective_caller_id_name" = "Nakata"
Make Call from that Extension to another
No error  with English name
Set the "Effective Caller ID Name" or  "effective_caller_id_name" = "田中"
Error with Japanese name
Chrome console output:
Failed to parse header: From: "田中" sip:100@domain.com;tag=Ka23r25pFSHNm
tsk_utils_log_error @ SIPml-api.js:1
tsip_header_NameAddr.Parse @ SIPml-api.js:1
tsip_header_parse @ SIPml-api.js:1
tsip_message_parser_execute @ SIPml-api.js:1
tsip_message.Parse @ SIPml-api.js:1
__tsip_transport_ws_onmessage @ SIPml-api.js:1
SIPml-api.js:1
Uncaught TypeError: Cannot read property 's_tag' of null
at tsip_dialog_layer.handle_incoming_message (SIPml-api.js:1)
at tsip_transport_layer.handle_incoming_message (SIPml-api.js:1)
at WebSocket.__tsip_transport_ws_onmessage (SIPml-api.js:1)

Yes, this issue exists. Because ragel-js cannot handle 2bytes non ascii character right now, but the author of ragel-js did not update it since 8 years ago.


webdriver_factory issue - build_firefox raises exception when using GeckoDriverManager

Hi, we found an issue with webdriver_factory that has been introduced in 1.14.0 by this commit:
https://github.com/ElSnoMan/pyleniumio/commit/737a6f17a447bc8290374c6a2c41275b26d51756#diff-a0691ef19635b2f2655886d510eb28feefd3b797e34a732384df81386f67e303R267
GeckoDriverManager's install method returns the driver path (e.g. /Users/mariuszrusiniak/.wdm/drivers/geckodriver/macos/v0.30.0/geckodriver) which is the passed to webdriver.Firefox as  positional argument which lands in firefox_profile keyword argument.

        If exception(s) occur, an Error is raised with a list of reasons.

        If the optional symlinks flag is true, symbolic links in the
        source tree result in symbolic links in the destination tree; if
        it is false, the contents of the files pointed to by symbolic
        links are copied. If the file pointed by the symlink doesn't
        exist, an exception will be added in the list of errors raised in
        an Error exception at the end of the copy process.

        You can set the optional ignore_dangling_symlinks flag to true if you
        want to silence this exception. Notice that this has no effect on
        platforms that don't support os.symlink.

        The optional ignore argument is a callable. If given, it
        is called with the `src` parameter, which is the directory
        being visited by copytree(), and `names` which is the list of
        `src` contents, as returned by os.listdir():

            callable(src, names) -> ignored_names

        Since copytree() is called recursively, the callable will be
        called once for each directory that is copied. It returns a
        list of names relative to the `src` directory that should
        not be copied.

        The optional copy_function argument is a callable that will be used
        to copy each file. It will be called with the source path and the
        destination path as arguments. By default, copy2() is used, but any
        function that supports the same signature (like copy()) can be used.

        """
        sys.audit("shutil.copytree", src, dst)
>       with os.scandir(src) as itr:
E       NotADirectoryError: [Errno 20] Not a directory: '/Users/mariuszrusiniak/.wdm/drivers/geckodriver/macos/v0.30.0/geckodriver'

../../.pyenv/versions/3.9.9/lib/python3.9/shutil.py:564: NotADirectoryError

The fix here would be to revert this line to become:
return webdriver.Firefox(executable_path=GeckoDriverManager(version=version).install(), options=options, **(webdriver_kwargs or {}))

As this is basically a oneliner let me know if you want me to open a PR for this one. Thanks!

Nice catch! Could you make a PR for this, please?
On Fri, Jan 28, 2022, 5:51 AM Mariusz Rusiniak @.***>
wrote:

Hi, we found an issue with webdriver_factory that has been introduced in
1.14.0 by this commit:
737a6f1
#diff-a0691ef19635b2f2655886d510eb28feefd3b797e34a732384df81386f67e303R267
https://github.com/ElSnoMan/pyleniumio/commit/737a6f17a447bc8290374c6a2c41275b26d51756#diff-a0691ef19635b2f2655886d510eb28feefd3b797e34a732384df81386f67e303R267
GeckoDriverManager's install method returns the driver path (e.g.
/Users/mariuszrusiniak/.wdm/drivers/geckodriver/macos/v0.30.0/geckodriver)
which is the passed to webdriver.Firefox as positional argument which
lands in firefox_profile keyword argument. It is later on checked if it
is a directory and raises an Exception like below:
venv/lib/python3.9/site-packages/pylenium/driver.py:265: in visit
self.webdriver.get(url)
venv/lib/python3.9/site-packages/pylenium/driver.py:233: in webdriver
return self.init_webdriver() if self._webdriver is None else self._webdriver
venv/lib/python3.9/site-packages/pylenium/driver.py:203: in init_webdriver
self._webdriver = webdriver_factory.build_from_config(self.config)
venv/lib/python3.9/site-packages/pylenium/webdriver_factory.py:133: in build_from_config
return build_firefox(
venv/lib/python3.9/site-packages/pylenium/webdriver_factory.py:278: in build_firefox
return webdriver.Firefox(GeckoDriverManager(version=version).install(), options=options, **(webdriver_kwargs or {}))
venv/lib/python3.9/site-packages/selenium/webdriver/firefox/webdriver.py:126: in init
self.binary = None
venv/lib/python3.9/site-packages/selenium/webdriver/firefox/firefox_profile.py:82: in init
shutil.copytree(

src = '/Users/mariuszrusiniak/.wdm/drivers/geckodriver/macos/v0.30.0/geckodriver', dst = '/var/folders/0k/d1yrv3sx1ldb_dv2dpzcwkxw0000gn/T/tmp7jfodd7e/webdriver-py-profilecopy', symlinks = False
ignore = <function ignore_patterns.._ignore_patterns at 0x12457d3a0>, copy_function = <function copy2 at 0x102e2c1f0>, ignore_dangling_symlinks = False, dirs_exist_ok = False
def copytree(src, dst, symlinks=False, ignore=None, copy_function=copy2,
             ignore_dangling_symlinks=False, dirs_exist_ok=False):
    """Recursively copy a directory tree and return the destination directory.

    dirs_exist_ok dictates whether to raise an exception in case dst or any
    missing parent directory already exists.

    If exception(s) occur, an Error is raised with a list of reasons.

    If the optional symlinks flag is true, symbolic links in the
    source tree result in symbolic links in the destination tree; if
    it is false, the contents of the files pointed to by symbolic
    links are copied. If the file pointed by the symlink doesn't
    exist, an exception will be added in the list of errors raised in
    an Error exception at the end of the copy process.

    You can set the optional ignore_dangling_symlinks flag to true if you
    want to silence this exception. Notice that this has no effect on
    platforms that don't support os.symlink.

    The optional ignore argument is a callable. If given, it
    is called with the `src` parameter, which is the directory
    being visited by copytree(), and `names` which is the list of
    `src` contents, as returned by os.listdir():

        callable(src, names) -> ignored_names

    Since copytree() is called recursively, the callable will be
    called once for each directory that is copied. It returns a
    list of names relative to the `src` directory that should
    not be copied.

    The optional copy_function argument is a callable that will be used
    to copy each file. It will be called with the source path and the
    destination path as arguments. By default, copy2() is used, but any
    function that supports the same signature (like copy()) can be used.

    """
    sys.audit("shutil.copytree", src, dst)

  with os.scandir(src) as itr:

E       NotADirectoryError: [Errno 20] Not a directory: '/Users/mariuszrusiniak/.wdm/drivers/geckodriver/macos/v0.30.0/geckodriver'
../../.pyenv/versions/3.9.9/lib/python3.9/shutil.py:564: NotADirectoryError
The fix here would be to revert this line to become:
return webdriver.Firefox(executable_path=GeckoDriverManager(version=version).install(), options=options, **(webdriver_kwargs or {}))
As this is basically a oneliner let me know if you want me to open a PR
for this one. Thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/ElSnoMan/pyleniumio/issues/235, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFQDCPI4YFSZF7U4PAWEUVTUYKGO7ANCNFSM5NAVRPLA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Sure, I'm on it!


@conda-forge-admin, please add user @IAlibay

Additional comment:
No response

Hi! This is the friendly automated conda-forge-webservice.
I just wanted to let you know that I added user @IAlibay in conda-forge/griddataformats-feedstock#15.


[#137] Fixed by avoiding acos for getting arcTo points. We know it's…

… 90 degrees, so can instead do projections to find center. (+1 squashed commit)

do not merge


Force correct Isso embed character encoding

When Isso is included from a webpage that does not use UTF-8 encoding, the spacer character in embed.min.js (originally from https://github.com/posativ/isso/blob/master/isso/js/app/text/comment.jade#L13) gets interpreted in the wrong encoding which results in Mojibake.

Should be fixed by replacing it with •.


Remove functions

As was discussed, I have removed functions that we don't use. (in total, -9000 lines of code)
It took longer than I anticipated. :( I slightly changed the API to make it simpler and to allow to remove even more code.
I have also added "default" flow export so we don't need to write the flowtype "shim" everywhere
I have changed the tests so they actually work again. However, the tests do not include zcash, so the coverage fails (since the zcash code is not at all covered).
I have changed other Javascript projects to use this slightly changed API. I will make PRs where appropriate. (I have made changes in hd-wallet, trezor-link, trezor.js, mytrezor, I will now make the PRs)
edit: I forgot the mention, I have gone through all usages of all the functions here in Trezor JS libraries and added comments about which function is used where. So it can be perhaps more easily refactored some day :)

I have made this PR to zcash branch and not master branch, since master branch is behind

we can turn on travis on this, but it will fail because of the zcash coverage

nice!

cool. I will force push this to master


run setup.py segmentation fault

 hello,I use "sudo python3 setup.py  install"  to setup trt_pose. but ,then it stopped. on the screen,it only show me "segmentation fault".
  I do not know what's wrong with it. please help me!

Hi, I am finding same problem by running sudo python3 setup.py  install command, please help.

I found thar，when you import torch ,it show  "segmentation fault" .so the problem is pytorch.

Im having the same issue. I installed pytorch from  nvidia forums  version 1.7 in my jetson nano. When I call import torch there is no error like segmentation falut. Is there any fix for this issue?


Clean-up fixes before 2022-Dec release

LGTM

@mariobaldi Please take a look when you get a chance.  Some of this is minor typo fixes, some is more substantive changes that enable the example P4 programs to compile without errors (e.g. see the changes to the SelectByDirection extern function definition and how it is used in the examples).


Can I pull who is mentioned in a story or story text?

Is the text written on a story and mentions included in the StoryItem class? Is there a way I can extract just the mentions or text from a story?
Thanks

Yes, If you download the metadata of StoryIteam ( .json.xz file) and then search through it, there will be one attribute "tappable_objects" and you can find the username and full name.
It will be something like "tappable_objects":[{"__typename":"GraphTappableMention","x":0.766702320031161,"y":0.290679397209822,"width":0.15329453253219602,"height":0.019888166601669,"rotation":0.0,"custom_title":null,"attribution":null,**"username":"abcxyz","full_name":"ABC XYZ"**,"is_private":true}],   so from there you can find out who is mentioned in the story.
Not sure about the text written on a story though.


Add distribution

Via EASIN API (https://easin.jrc.ec.europa.eu/api/cat/euconcern/) we get Introductions information which we can map to distribution extension.

For Myriophyllum heterophyllum we get the following:
Year | Country | Notes | SpeciesName | Reference.Name | IsDeleted | ...
1800 | Austria | 1800, 1973 | Myriophyllum heterophyllum | NOBANIS | FALSE | ...
@timadriaens: what do they mean with "1800, 1973"?

No idea, the first record in Austria was 1945 (link) so that doesn't make much sense to me. Also the NOBANIS database gives other dates (1885 as first date for Austria for instance).

Thanks. I think this issus can be set to "On hold" until #9 and #6 are solved.


update codecov version

Update to v2 of codecov action.

Codecov Report

Merging #744 (3bf7e35) into master (1a1ecde) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #744   +/-   ##
=======================================
  Coverage   84.61%   84.61%
=======================================
  Files          19       19
  Lines        3355     3355
=======================================
  Hits         2839     2839
  Misses        516      516

Flag
Coverage Δ

unittests
84.61% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.


jaeger operator fails to pull image for 1.17.5

Hello
On openshift, the jaeger operator tried to update itself 1.17.5 provided by Red Hat but is failing to do so because of the following error:
Failed to pull image "registry.redhat.io/distributed-tracing/jaeger-rhel7-operator@sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50": rpc error: code = Unknown desc = Error reading manifest sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50 in registry.redhat.io/distributed-tracing/jaeger-rhel7-operator: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<TITLE>Error</TITLE>\nAn error occurred while processing your request.
\nReference #132.eb161002.1595400530.9465762\n\n"
I tried to pull it form a bastion but get the same error:
$ podman pull registry.redhat.io/distributed-tracing/jaeger-rhel7-operator@sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50  Trying to pull registry.redhat.io/distributed-tracing/jaeger-rhel7-operator@sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50...ERRO[0004] Error pulling image ref //registry.redhat.io/distributed-tracing/jaeger-rhel7-operator@sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50: Error initializing source docker://registry.redhat.io/distributed-tracing/jaeger-rhel7-operator@sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50: Error reading manifest sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50 in registry.redhat.io/distributed-tracing/jaeger-rhel7-operator: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<TITLE>Error</TITLE>\nAn error occurred while processing your request.
\nReference #132.c3161002.1595401950.910bdf80\n\n" Failed Error: error pulling image "registry.redhat.io/distributed-tracing/jaeger-rhel7-operator@sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50": unable to pull registry.redhat.io/distributed-tracing/jaeger-rhel7-operator@sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50: unable to pull image: Error initializing source docker://registry.redhat.io/distributed-tracing/jaeger-rhel7-operator@sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50: Error reading manifest sha256:3eeed89119c20386161bc464136ccdeb98e99b2c40883f70d6cd2e6c742c0a50 in registry.redhat.io/distributed-tracing/jaeger-rhel7-operator: error parsing HTTP 404 response body: invalid character '<' looking for beginning of value: "<TITLE>Error</TITLE>\nAn error occurred while processing your request.
\nReference #132.c3161002.1595401950.910bdf80\n\n"
Is the operator bad configured ?
Thanks
Regards
Sydney

@daufinsyd Thanks for reporting this - the issue is being addressed. However, Red Hat operator issues should be raised through the Red Hat support channels as this is the open source community project repo.


Refactor MAISI tutorial, migrate GenerativeAI import

Fixes #1772 .
Description
Refactor MAISI tutorial, migrate GenerativeAI import to monai core.
Add inference script.
Correct logging format.
VAE training notebook tested.
Diffusion training notebook tested.
ControlNet training notebook tested.
Inference notebook tested.
Checks

[x] Avoid including large-size files in the PR.
[ ] Clean up long text outputs from code cells in the notebook.
[x] For security purposes, please check the contents and remove any sensitive info such as user names and private key.
[x] Ensure (1) hyperlinks and markdown anchors are working (2) use relative paths for tutorial repo files (3) put figure and graphs in the ./figure folder
[x] Notebook runs automatically ./runner.sh -t <path to .ipynb file>

To pass CI, it requires monai core controlnet_maisi to remove generative dependency first.

To pass CI, it requires monai core ControlNetMaisi to remove generative dependency first.

It seems we can re-run it after this PR is merged:
https://github.com/Project-MONAI/MONAI/pull/8005

Hi @Can-Zhao, I find there is still one place need to be updated in the maisi: https://github.com/Project-MONAI/tutorials/blob/main/generation/maisi/configs/config_maisi_diff_model.json#L3

Hi @Can-Zhao, I find there is still one place need to be updated in the maisi: https://github.com/Project-MONAI/tutorials/blob/main/generation/maisi/configs/config_maisi_diff_model.json#L3

Submitted a PR for it https://github.com/Project-MONAI/tutorials/pull/1786


cargo-bitbake build failed on yocto due to openssl3 native!!!

Hi,
We tried to build cargo-bitbake as part of yocto.
Yocto is upgraded to openssl-3.0 so cargo-bitbake recipe fails while building openssl-sys v0.9.54 which is dependent for carg-bitbake.
Recipe(.bb) and build failure log is attached,
Below patch resolves the issue
https://github.com/sfackler/rust-openssl/pull/1264/commits/b4c735e8af546dee49b54679f63bcfec16c15a0f
But the patch is not mainlined :(.
build_failure.txt
cargo-bitbake_0.3.16-alpha.0.bb.txt
Any plan on supporting openssl3  for cargo-bitbake?

Can you just update this in the toml file to have a newer version of openssl-sys, say version openssl-sys-v0.9.72?
Openssl-3.0 support was added initially by:
https://github.com/sfackler/rust-openssl/commit/e5999ccf4a203fcbe41723923334ba18eaf1e159
and:
$ git tag --contains e5999ccf4a203fcbe41723923334ba18eaf1e159
openssl-sys-v0.9.69
openssl-sys-v0.9.70
openssl-sys-v0.9.71
openssl-sys-v0.9.72
openssl-v0.10.38

There’s nothing we can do here. This isn’t a dependency of this package. It’s not even a dependency of our depends. It’s a depend of cargo via git2 via libgit2 via libgit2-sys via libssh2-sys.

There’s nothing we can do here. This isn’t a dependency of this package. It’s not even a dependency of our depends. It’s a depend of cargo via git2 via libgit2 via libgit2-sys via libssh2-sys.
Thanks cardoe. We updated git2 and its dependencies to latest.

Can you just update this in the toml file to have a newer version of openssl-sys, say version openssl-sys-v0.9.72? Openssl-3.0 support was added initially by: sfackler/rust-openssl@e5999cc and: $ git tag --contains e5999ccf4a203fcbe41723923334ba18eaf1e159 openssl-sys-v0.9.69 openssl-sys-v0.9.70 openssl-sys-v0.9.71 openssl-sys-v0.9.72 openssl-v0.10.38

Thanks Randy. After updating  git2 and its dependencies in Cargo.toml and recipe,  cargo-bitbake builds without issue in yocto.
Regards
Chandra


skip eviction when replica count is below evictor minReplicas threshold setting

alternate implementation to #1152
Closes #1058
/cc @jiangxiaobin96

@ingvagabund and @knelasevero what are your thoughts on this PR?

I think this makes sense. However I want to test somethings I just thought about.

Do we want to backport this and also make this available in v1alpha1 while we still maintain it? Since this is additive it shouldn't be too hard

@knelasevero I would prefer to encourage users to migrate to v1alpha2. Adding new functionality is one way to do it. But if you feel that we should support both, I'm happy to add it.

I actually agree. Just asking so the decision is explicit in this PR

/lgtm

@a7i can you please rebase the PR? 🙏

@a7i can you please rebase the PR? 🙏

there hasn't been much traction from other maintainers, but happy to rebase just in case

@knelasevero can you please give it a new look? Thank you

/retest

/lgtm

/approve
/hold
feel free to unhold, leaving here in case someone else wants to review.

/hold cancel

/lgtm


Added hover animations on Blog Cards

Closes - #110

Added on hover animations which zoom up when mouse is hovered on it.
Image for reference:

Hey @AKD-01..
Thank you for accepting the contribution..
Can you please add the GSSoC'23 label for this PR?

Hey @AKD-01  Can you please add the gssoc label and the level of difficulty for this PR?
Please do add it.


[Terminal]: Screen Reader does not announce Pop-up name when its focus first jump inside pop-up.

Windows Terminal version
1.12.3472.0
Windows build number
10.0.22504.1010
Other Software
Test Environment:
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: Narrator
Steps to reproduce
Repro Steps:

Open Windows Terminal.
Open Narrator using 'Win + Ctrl + Enter' keys.
Press 'Ctrl + Shift + space' keys to open new tab Dropdown pop-up, Observe the issues.
Press 'Ctrl + Shift + r' keys to open Set tab color pop-up, Observe the issues.

User Experience:
Screen Reader users UX will not be good as they will not be able to know the purpose pop-ups.
Guideline Reference:
https://www.w3.org/WAI/WCAG21/Understanding/info-and-relationships
Attachments:
Screen Reader does not announce Pop-up name when its focus first jump inside pop-up.zip
Expected Behavior
Screen Reader announces Pop-up name when its focus first jumps inside 'New Tab Dropdown' & 'Set tab color' pop-up.
i.e. When user open 'New Tab Dropdown' using 'Ctrl + Shift + space' using Screen Reader should announce 'New Tab Dropdown pop-up window ....' and When user open 'Reset tab color' using 'Ctrl + Shift + r' using Screen Reader should announce 'Set tab Color pop-up window....'
Actual Behavior
Screen Reader does not announce Pop-up name when its focus first jumps inside 'New Tab Dropdown' & 'Set tab color' pop-up.
Observation: Same issue repro with NVDA and JAWS Screen Reader.

In TerminalPage.cpp, if we just give the newTabFlyout an AutoProp name, we might be good?


Upgrading to tf 0.15.x

Updating tf and other versions to keep things up-to-date.

I don't see a change in the readme text to indicate the new required version of terraform is 15.4.

Docs are not complete at this time. Looking for functional testing. Terraform 0.15.4 is the only change that the end user will notice.

Dev testing is completed and passed. Noted customer facing doc isn't ready yet.


Dark mode

I want to add a toggler which toggles between dark and light mode

and rest changes of dark mode?

background to black and text to white

okay

Hi Kritika, I would like to work on this issue if available.

Please assign this issue to me

@Manideep711  Are you working on this?

Can you please assign me this issue

yes iam working on it

yes iam working on it

okay


Websocket logging cleanup

Would be nice if some of the logging could be cleaned up.
It would be great if you either setup a public *log.Logger so the user can tweak the settings without messing with their own log or at least only log when the Slack struct has debug on.

this should be possible using set logger. closing due to age. but I agree in the future logging could use some additional work.


Ionic 3 - IonicPage Deeplinking - navPush directive not setting correct href

Ionic version:  (check one with "x")
[ ] 1.x
[ ] 2.x
[x] 3.x
I'm submitting a ...  (check one with "x")
[x] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:

Found a small bug with the new IonicPage Deeplinking:
When setting a link from the navPush directive About, the generated link always shows the current page About
Expected behavior:

Behaviour without IonicPage: About
Ionic info: (run ionic info from a terminal/cmd prompt and paste output below):

Cordova CLI: 6.5.0
Ionic Framework Version: 3.0.0
Ionic CLI Version: 2.2.2
Ionic App Lib Version: 2.2.1
Ionic App Scripts Version: 1.3.0
ios-deploy version: 1.9.1
ios-sim version: 5.0.13
OS: macOS Sierra
Node Version: v7.8.0
Xcode version: Xcode 8.3.1 Build version 8E1000a

Hello, thanks for opening an issue with us, we will look into this.

@vandres Are you still experiencing this issue? I am not able to replicate it as of Ionic 3.3.0.

@TanayParikh Yes, tested it with our current 3.3.0 app. Setting a link wit navPush and lazy loading shows the wrong link:
I am on ListPage and in the template is the following
Home -> Home

Also seeing this
    @ionic/cli-utils : 1.3.0
    Cordova CLI      : 7.0.1
    Ionic CLI        : 3.3.0
    @ionic/app-scripts              : 1.3.7
    @ionic/cli-plugin-cordova       : 1.3.0
    @ionic/cli-plugin-ionic-angular : 1.3.0
    Cordova Platforms               : ios 4.4.0
    Ionic Framework                 : ionic-angular 3.3.0
    Node       : v6.10.2
    OS         : macOS Sierra
    Xcode      : Xcode 8.3.2 Build version 8E2002
    ios-deploy : 1.9.1
    ios-sim    : 5.0.8

Exactly the same issue as @tommybananas described:
cli packages: (C:\Development\latestnews-ionic\node_modules)

    @ionic/cli-plugin-cordova       : 1.5.0
    @ionic/cli-plugin-ionic-angular : 1.4.0
    @ionic/cli-utils                : 1.7.0
    ionic (Ionic CLI)               : 3.7.0

global packages:

    Cordova CLI : 7.0.1

local packages:

    @ionic/app-scripts : 2.1.3
    Cordova Platforms  : android 6.2.3
    Ionic Framework    : ionic-angular 3.6.0

System:

    Android SDK Tools : 26.0.2
    Node              : v6.11.0
    OS                : Windows 10
    npm               : 5.3.0

@tommybananas @lordgreg I think you have to use [navPush]="'NewPage'" as you are not using a variable but a string. This should not be related to the bug I reported

I can confirm this bug. Very annoying with locationstrategy path. Navpush is not usable in a pwa

@jgw96 Thank you for your talk on PWAs. Maybe you can push this issue a bit?!

That issue is still not fixed...  Here is a workaround:
html:
[attr.href]="'/'+someLink" (click)="openPage(someLink)"
ts:
  openPage(page) {     event.preventDefault();     event.stopPropagation();     this.nav.push(page);   }


Usage with swoole - ExpressivePage should be stateless

@froschdesign
Good morning,
I'm switching to swoole. When using swoole, services must be stateless.
This isn't the case of your ExpressivePage implementation  which is bound to the navigation service. While I can understand that the navigation service must be created only once, including page containers, the pages for which state is derivated from the current request shouldn't keep their state throughout subsequent requests. Basically put, state of pages should be recalculated on each requests.
Keeping the state of the pages with swoole produce wrong behavior (pages with unexpected active state). One way to workaround the  issue is to reset the active state when the RouteResult object is set, that is:
    /**
     * @param RouteResult $routeResult
     */
    public function setRouteResult(RouteResult $routeResult) : void
    {
        $this->active = false; // Make sure that active state will be based on current request
        $this->routeResult = $routeResult;
    }

instead of
    /**
     * @param RouteResult $routeResult
     */
    public function setRouteResult(RouteResult $routeResult) : void
    {
        $this->routeResult = $routeResult;
    }

I'm pretty sure that there are other issues like this with current implementation (such as the hrefCache property) but solving this one would be a good starting point.
Thank you.

@froschdesign My solution above is bad in regard of usage in async context... We should think about a contextual state...

The support of Swoole is not one of the current goals. The current development includes only the support of zend-expressive itself. The integration of Swoole can be added later, after the transfer to the zendframework organisation.


Added SharePoint List Provider

Added a sharepoint list provider
Added logic to use mock for local dev, and new provider for online.
Fixed typo in 'Service' classname

Q
A

Bug fix?
no

New feature?
yes

New sample?
no

Related issues?
fixes #X, partially #Y, mentioned in #Z

What's in this Pull Request?
This adds a SharePoint List provider to the sample, and associated logic to use Mock for local workbench development, and the new provider for live
Guidance

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.:x: cberon sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

thx @cberon, appreciated.


server, schedule: check region epoch before adding operators.

The Schedulers/Checkers are run by selecting a Region from the Cluster, generating operator by some sort of calculation and adding it to the coordinator.
There is a flaw in this process: if the region is changed after being selected out, wrong operator may be added and executed.
This PR fixes the problem by checking the region's epoch is unchanged before adding the operator.

/run-all-tests


Integration test router?

In my integration tests I have many common 'routes'.
For example, I want to test adding transport feature that situated in user profile. For that, I go to user profile and then tap 'add transport' button and do some stuff. After that, I start next test that restarts app and testing user passport editing feature and goes to user profile again.
That time I created file named integration_test_routes.dart and defined here a function:
import 'package:myapp/pages/pages_keys.dart';
import 'package:patrol/patrol.dart';

Future<void> goFromStartPageToUserProfilePage(PatrolTester $) async {
  await $(PK.mainMenuButton).tap();
  await $(PK.mainMenuDrawerProfileButton).tap();
}

Now I can just paste goFromStartPageToUserProfilePage function everywhere I need and don't make code dublicates.
But I think that more complex router is possible.
Like… lets define routes of application as "chains": "mainPage->userProfile", "mainPage->userProfile->userProfileEditPage", etc.
And our "go" function will be something like go(from: 'mainPage', to: 'userProfile') or go(from: 'mainPage', to: 'userProfileEditPage'), etc.
So… Intention of this issue is to find out if there are better options than mine and, maybe, to propose to implement a routing system in patrol library in the future.

Hi again :)
If I understand correctly, you're testing many features of your app in a single patrolTest()? If yes, then we consider it an antipattern (it breaks test reporting, makes tests flaky, etc.)
I think what you're after is described here: patrol.leancode.pl/tips-and-tricks#bundling-many-tests-into-a-single-app-binary.
We discussed a somewhat similar topic here: https://github.com/leancodepl/patrol/discussions/511
Apps are very different and I doubt we can create a generic "test router" solution.


localIndentName hash Name changed (Webpack To v5 from v4)

Bug report

What is the current behavior?

We have upgraded webpack 4 to webpack 5 and everything works fine except localIndentName has changed in CSS bundle files

we are using css-loader v6.6.0 for webpack 5  and configuration for the css loader is as follows

{
loader: 'css-loader',
options: {
modules: {
localIdentName: ${packageName}-[local]--[hash:base64:8]
},
sourceMap: false
}
}

packageName is separate variable name for each css-module
previously className (webpack 4) - .${packageName}-${local}--2sQngLez
now with webpack 5 the last hash version is changed to  - .${packageName}-${local}--pWmRUIaV

If the current behavior is a bug, please provide the steps to reproduce.

What is the expected behavior?
Expectation should be webpack 5 build should generate CSS build ( hash ) with the same name

Other relevant information:
webpack version:   5.68.0
Node.js version: 14.19.1
Operating System:
Additional tools:

@webpack-bot move to webpack-contrin/css-loader


Isolate loader to start on click

Experiencing loader delays between clicking a button for a task and waiting for the tx to start. With the intro to Cartridge and session keys the loader should trigger on click rather than tx submission.
Current:
  await handleSubmitCalls(writeAsync).then((tx: any) => {
    if (tx) {
      startLoading(
        "Explore",
        tx.transaction_hash,
        "Exploring",
        "discoveryByTxHashQuery",
        adventurer?.id
      );
      addTransaction({
        hash: tx.transaction_hash,
        metadata: {
          method: `Explore with ${adventurer?.name}`,
        },
      });
    }

Proposed:
startLoading(...) //NEW CODE
await handleSubmitCalls(writeAsync).then((tx: any) => {
 if (tx) {
   setLoadTxHash(tx.transaction_hash) //NEW CODE
   addTransaction({
     hash: tx.transaction_hash,
     metadata: {
       method: `Explore with ${adventurer?.name}`,
     },
   });
 }

perfect!

Fixed in #107


Document development process for appmetrics

This should describe the use of branches, tags and milestones/versions in the package.json and any license files.

I think this is covered in https://github.com/RuntimeTools/appmetrics/wiki/Developing. If you agree, please close the issue.

I think the wiki page could do with a bit more description of the generate flow/decision process of developing and releasing code, particularly with a view to encouraging engagement and contributions.

Probably not going to do any more on this for now unless anyone wants to provide a PR, or we get a lot of people asking for it.  Adding the ice box label.


Optimized icons filesize.

PNG image is visually identical. SVG image optimized for more smaller size and faster rendering, visually is the same.

Which tools did you use to optimize the files? Both pngcrush and optipng say that the png is already optimized.

The app is really helpful broh. Bring it to the store.

Which tools did you use to optimize the files? Both pngcrush and optipng say that the png is already optimized.

Pngcrush + OptiPNG+ ECT + AdvanceCOMP + DeflOpt + defluff + pingo + pngwolf + TruePNG + ZopfliPNG and 1 day of IDAT chunk brute-forcing to find the best compression.


WIP New tracing infrastructure

This is the new tracing infrastructure, that is intended as replacement for iohk-monitoring-framework and the related integration code in cardano-node.
The documentation is at https://github.com/input-output-hk/cardano-node/tree/tracing-master/trace-dispatcher/docs/trace-dispatcher.md
TODO
Library trace-dispatcher

[X] Add frequency limiting

[X] Testen

[x] Add continued message to frequency limiting

[x] Testen

[X] Add queue size trace forwarder to config

[X] Testen

[X] Add color arg to backend config?

[x] Testen

[X] Formatting optimization

[X] Testen

[x] Add check code for configuration and wiring

[x] Framework functionality tests !!!

[X] Privacy
[ ] DetailLevel
[x] Backend routing
[ ] Backend formatting
[x] Severity filtering
[ ] Freuqency limiting

[X] Comment library code

[X] Document configuration
nix/workbench/profiles/node-services.nix
scripts/lite/configuration/shelley-*.yaml
./scripts/lite/shelley-testnet.sh

Integration

[x] Ensure completeness of set of Metrics

[x] Add aggregation cases

[x] Ressource stat tracers

[X] Linux
[x] Windows and Mac testing

[X] Basic info tracers

[X] Rebase on latest master

[x] Fix privacy for all tracers!

[ ] Fix namespaces for all tracers

[ ]  External changes:

[ ] Reconfigure call.
[X] Reconfigure and forwarder? (Dont do)
[ ] Document call (with fileName).
[x] No strictness annotations for: Mempool

[x]  Solution for: cardano-tracer does not see start of traces, because always connect after start of node

[x] One possible solution: Have big queue in the node at startup
[x] Implement
[x] Test

Next steps

[ ] Benchmark trace-dispatcher in comparison to old tracers

[ ] Test forwarder cache performance

[ ] Test forwarder cache overflow

[ ] Second phase

[ ] Remove old tracers

The first PR for the new tracing infrastructure is open: https://github.com/input-output-hk/cardano-node/pull/2960

Our second PR is open: https://github.com/input-output-hk/cardano-node/pull/3073

The next PR: https://github.com/input-output-hk/cardano-node/pull/3337

The next PR: https://github.com/input-output-hk/cardano-node/pull/3342

The next PR, integration in the node: https://github.com/input-output-hk/cardano-node/pull/3450

The next PR: https://github.com/input-output-hk/cardano-node/pull/3496

The next PR: https://github.com/input-output-hk/cardano-node/pull/3498

The tracing system integration PR was merged, so this no longer has purpose of serving as integration.


Pagination test is flaky

For some reason the pagination system test is failing for me in CI, but not locally.
This line is failing for me:
refute page.has_content?("Test #{Pagy::DEFAULT[:items] + 1}")

The page size is 20, so that line is looking for the string "Test 21" in the page content, and is finding it even though it should not be found.
After much head scratching and debugging I finally figured out that for some reason the sort order in CI is backwards. (I have no idea why that might be the case.)
So "Test 21" is actually on the page, but the first item "Test 1" is missing.
But there's actually a test to check for "Test 1" that is passing when it shouldn't pass. And that's because we're doing simple substring matching and "Test 1" also matches "Test 11", "Test 12", etc...

But there's actually a test to check for "Test 1" that is passing when it shouldn't pass. And that's because we're doing simple substring matching and "Test 1" also matches "Test 11", "Test 12", etc...

Good point, I think this would be a better check:
page.text.scan(/Test \d+/).include?("Test 1")

After much head scratching and debugging I finally figured out that for some reason the sort order in CI is backwards. (I have no idea why that might be the case.)

I wonder why it's getting displayed backwards? I'm not sure if this is something on Bullet Train's side.

Probably related to https://github.com/bullet-train-co/bullet_train-core/issues/408


Create new wallet tab for purchases/rentals

We recently renamed the fiat one > Tips, but it has all the stripe transactions.
We can pass the type as tips/rental/purchase, gotta see if we can pass multiple here on the backend to suppor this.
At the same time, these would be nice, both on sender/receiver: https://github.com/OdyseeTeam/odysee-frontend/issues/2390 /
https://github.com/OdyseeTeam/odysee-frontend/issues/1744

Closed by #2437


#adding a preview button in the Free E-books webpag

Describe the feature
we can add a preview button below each of the books which on being clickes open up a iframe through which users can a small preview of the entire book.Please assign me this under gssoc'24.
Add ScreenShots

Record

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

Assigned!
Make sure to attach before & after screenshots in your PR and include the issue number.
Also, please star the repo before working on it. Happy open-source contributing!


Can we have the Jackson dependency removed?

Also, It looks like ClickHouseResponse Isn't even used anymore.  It's only referenced in 1 test.

can't agree more

That is not truth.

@alex-krash Yes it is.  Those are transitively unused if you remove the test.

Since it is part of public contract for ClickhouseStatement interface, we can not drop it, unless declared deprecated, and stopped being used by clients.

Since it is part of public contract for ClickhouseStatement interface, we can not drop it, unless declared deprecated, and stopped being used by clients.

then can we have the Jackson dependency update to the lastest version?

@BernieJiangDL If you're using maven you can specify exclusions in dependencies.

@BernieJiangDL If you're using maven you can specify exclusions in dependencies.

But the lastest version is incompatible with 2.7.3 version

@BernieJiangDL If you're using maven you can specify exclusions in dependencies.

But the lastest version is incompatible with 2.7.3 version

Adding the exclusion to the pom dependency will remove 2.7.3.

@jcdang @BernieJiangDL we just released yesterday an alternative with all unnecessary dependencies removed (jar size now 860kb only). Please check it here - https://github.com/blynkkk/clickhouse4j.


select_field: allow an array of selected values

Note: Had to add Array(String) to OptionsHash to make it work.

@anamba I was going to add a comment here but I see it's already been merged. Could you open also add Int32 to the array to make it easy to work with id's from DB? Feel free to open a new PR.

Had to read that one a couple times to get what you meant. Sure, I think that makes sense.

Sorry I'll edit it. I typed that on my phone.


[Enhancement]: Pointer as cursor

Do you want to have the enhancement of existing game ? 😀 Describe yourself..
Game enhancement
The pointer does not appear when we play so add cursor.
Describe the solution you'd like
Solution steps

When we add the cursor pointer, make it know the where pointer to make it good.
Adding a new feature pointer or other that can make it attractive.
Please assign @pa

Select program in which you are contributing
No response
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

If you have any doubt you can directly send message on our discord (https://discord.gg/rZb46cCMmK), we have created seprate chennals for all projects...
Thank you :)

can you please assign me under GSSOC.'24 .


Package pdfpc-extractor for NixOS users

This PR will add a NixOS flake, which builds the pdfpc-extractor and exposes it as a package.
Usage

Add the flake to your own flake.nix as input
Use the package inputs.polylux.defaultPackage.${pkgs.system} (under the assumption that the flake was named polylux in your inputs), which will build pdfpc-extractor

Dev env
Either run

nix build to build the package into the result directory
or run
nix develop to enter a dev env where you should be able to run cargo build commands as usual

Cool! Can you add a note to the installation section in this file? https://github.com/andreasKroepelin/polylux/blob/main/book/src/external/pdfpc.md
Also, I don't really know much about Nix, so it's hard for me to review... @drupol, can you have a look maybe?

Sure, will do that tomorrow!
I'm using the pdfpc extractor in a presentation, with its own nix file. I'll let you know what I think of this PR tomorrow.

I slightly restructured the installation instruction section to streamline instructions for different OS, so we now have 3 subtitles for

Source
Arch Linux
NixOS

On another note, it could be that the package is build without the release flag:
https://github.com/nix-community/naersk#buildpackages-parameters
That might need to change

Dear @data-niklas,
Here's my take on this:

{
  description = "Polylux packages";

  inputs = {
    nixpkgs.url = "github:NixOS/nixpkgs/nixpkgs-unstable";
    systems.url = "github:nix-systems/default";
  };

  outputs = inputs @ { self, flake-parts, ... }: flake-parts.lib.mkFlake { inherit inputs; } {
    systems = import inputs.systems;

    perSystem = { config, self', inputs', pkgs, system, lib, ... }:
      let
        pdfpc-extractor = pkgs.rustPlatform.buildRustPackage {
          pname = "pdfpc-extractor";
          version = "dev";

          src = ./pdfpc-extractor;

          cargoHash = "sha256-VTJRfDFprKIrwfw5lU9/RnDuGLQ7nXBEc/dms5YVupM=";

          meta.mainProgram = "polylux2pdfpc";
        };
      in
      {
        formatter = pkgs.nixpkgs-fmt;

        packages = {
          pdfpc-extractor = pdfpc-extractor;
          default = pdfpc-extractor;
        };

        apps = {
          default = {
            type = "program";
            program = lib.getExec self'.packages.pdfpc-extractor;
          };
        };

        devShells.default = pkgs.mkShell {
          name = "polylux-devshell";
          buildInputs = with pkgs; [
            cargo
            rustc
          ];
        };
      };
  };
}

When I have to add a flake to a project, I try to limit to the maximum the external dependencies it depends on to avoid bad surprises. Therefore, I don't think using the contrib project naersk is needed here since we can build pdfpc-extractor with just the nixpkgs repository.
Moreover, I don't think requiring flake-utils is needed as well since we can use flake-parts which is already in nixpkgs and it has a better design (check NixOS Discourse about this).
I also expose pdfpc-extractor in the packages but also as an app that we can just run by doing: nix run github:andreaskroepelin/polylux#pdfpdf-extractor
I don't use the old flake syntax defaultPackages either and there's a default formatter which is set as well.
Let me know what you think of all of this.

Awesome! I reused the naersk Rust template from another template, as I was not so familiar withe the other methods to package Rust programs. If your version works and is more minimal, great.
How will the cargoHash work between updates? I tried to use your flake locally and got mismatched cargoHashes, as my local version is slightly different. Does it only base the hash on the cargo dependencies?
I think we then need to at least document somewhere, that the cargoHash needs to be updated, when the Rust dependencies change.

Else I would just more or less replace the flake with your more minimal flake

Package has been merged in Nix today @ https://github.com/NixOS/nixpkgs/pull/280525

Great! In that case I can and will close this PR.


add server.js for production

a server.js for running the application on-premise.
I didn't push changes to telefunc\pnpm-lock.yaml because I wasn't sure I should do it (new to pnpm).
for newcomers (like me), this was missing- it took me more that I wish, to figure this up :)

Makes sense!


Manage SCSB Update/Delete files via S3

The contractor hosting SCSB is moving away from using a SFTP server and will utilize an S3 bucket to make this daily changelog data (and other reports/logs generated by SSCSB) available to us. Will have more details on this soon. Will update the ticket when they are available.

[ ] Download Daily Partner Updates/Adds
[ ] Download Daily Partner Deletes
[ ] Upload Daily Princeton Update Records (SCSB's "SubmitCollection" API)
[ ] All files submitted to the SCSB server via submitCollection or transfer API need to prefixed with the string "scsb_" with the rest of the filename unchanged.

I put the environment variable out on staging.
Here is some example code for accessing a file (there is only data in the test bucket).  Assumes aws-sdk-s3 gem is installed
credentials = Aws::Credentials.new(ENV['SCSB_S3_ACCESS_KEY'], ENV['SCSB_S3_SECRET_ACCESS_KEY'])
s3 = Aws::S3::Client.new(region: 'us-east-1', credentials: credentials)
resp = s3.get_object(bucket: ENV['SCSB_S3_BUCKET_NAME'], key:'data-feed/submitcollections/PUL/cgd_protection/')
string_io = resp.body

Current path for incremental partner updates: /scsb-test/data-exports/PUL/MarcXML/Incremental
Current path for incremental partner deletes: /scsb-test/data-exports/PUL/Json/Incremental
Current path for full partner updates: /scsb-test/data-exports/PUL/MarcXML/Full

@kevinreiss Is this change rolling out at the same time as alma? Or is it on its own timeline?

If we want to update this now on main we first need to fix https://github.com/pulibrary/voyager_helpers/issues/120#issue-718133894.

From conversation with Mark: deadlines here have shifted, but they're deploying their new code in March so presumably we won't be able to retrieve the files in their current location anymore at that point.

There is a meeting on Monday that will discuss the release cycle for the
next SCSB deployment to production, we should know the planned date then.
On Thu, Feb 4, 2021 at 3:47 PM hackartisan<EMAIL_ADDRESS>wrote:

From conversation with Mark: deadlines here have shifted, but they're
deploying their new code in March so presumably we won't be able to
retrieve the files in their current location anymore at that point.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/pulibrary/marc_liberation/issues/909#issuecomment-773624965,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACECKKMU5OKURJB6FDIJG3S5MIXVANCNFSM4UKU7HHQ
.

@kevinreiss are files available in both locations for some period of time? It would be helpful to know what that window looks like.

This used to work with SFTP, but at the end of March we need to move to using the S3 buckets.
We need to confirm that we can use the data by the end of February.
Upload Daily Princeton Update Records:

You can submit as many files as you want in a day in a chunk.
You put the files into the S3 bucket and then then scsb will pick them up automatically.
Download Daily Partner Updates/Adds:
Current path for incremental partner updates: /scsb-test/data-exports/PUL/MarcXML/Incremental
Current path for incremental partner deletes: /scsb-test/data-exports/PUL/Json/Incremental
Current path for full partner updates: /scsb-test/data-exports/PUL/MarcXML/Full

Upload Daily Princeton Update Records: (SFTP is currently broken)
The princeton updates are paused. @mzelesky added a fix in voyager helpers but we haven't created a new release of the gem to update mar_liberation. To resume the job, we first need to test if @mzelesky's new fix in voyager helpers uploads the valid princeton marc records to scsb.

@christinach is this ticketed?

Upload Daily Princeton Update Records: (SFTP is currently broken)
The princeton updates are paused. @mzelesky added a fix in voyager helpers but we haven't created a new release of the gem to update marc_liberation. To resume the job, we first need to test that @mzelesky's new fix in voyager helpers uploads the valid Princeton marc records to scsb.

@carolyncole I did a quick look. No it is not. It was added only in comments. Feel free to open a ticket.

The planned end for SFTP to be used in production is March 19th at the moment. The SFTP server will remain around for approximately a month as any archive but any new partner record updates/reports will only be posted on S3 and any updates we want to submit about our own records should go there.

Per @christinach for submitCollection we still have to the following
1 Setting up the S3 connection in the RecapDump job
2. run the job with a timestamp going back to February 17th
3. resume the daily cron job.

@kevinreiss I'm referencing https://github.com/pulibrary/bibdata/issues/1049#issue-801651985 because I describe it in the comment. The cron job is currently paused and can be resumed to upload from current production Princeton records to SCSB when the AWS connection to SCSB is set and tested (#909 Third checkbox 'Upload Daily Princeton Update Records (SCSB's "SubmitCollection" API)'). As of today 03-10-2021, data were last updated manually by @mzelesky on February 17th; with that said, the job should also run with a timestamp of 02-17-2021 to upload the Princeton records starting 02-17-2021 until the time we resume the job again.

The new files need to be named "scsb_*"

Today we uploaded our Princeton records since 2021-02-17.


httpcore.ReadTimeout: The read operation timed out

Hi. I'm getting frequent read time out errors. This is my code:
transcription_model = "nova-2-general"
# sometimes we also use "whisper-medium"

#download the video from s3
# convert the video to mp3 audio

with open(audio_efs_path, "rb") as file:
            buffer_data = file.read()

payload: FileSource = {
        "buffer": buffer_data,
}

options = PrerecordedOptions(
                    model=transcription_model,
                    smart_format=True,
                    detect_language=True,
                )
response = deepgram.listen.prerecorded.v("1").transcribe_file(
            payload, options, timeout=httpx.Timeout(300.0, connect=10.0)
        )

I've my video files stored on s3 buckets. I first download the file and then I'm converting it to mp3. Then I use the above code to transcibe it. I still occasionally get timeout issues. We get timeout issues with nova-2-general, so model changing doesnt work.
What do you recommend here:
1- Re-trying with Exponentional backoff
2- I should upload the audio to s3 bucket and use the presigned url to get the transcipt
Thanks!
There are the error logs:

2024-06-24T13:12:34.175Z | [INFO] 2024-06-24T13:12:34.175Z 619e77ea-ea1b-4947-9b55-248653553619 Traceback (most recent call last):
-- | --
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpx/_transports/default.py", line 69, in map_httpcore_exceptions
  | 2024-06-24T13:12:34.175Z | yield
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpx/_transports/default.py", line 233, in handle_request
  | 2024-06-24T13:12:34.175Z | resp = self._pool.handle_request(req)
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpcore/_sync/connection_pool.py", line 216, in handle_request
  | 2024-06-24T13:12:34.175Z | raise exc from None
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpcore/_sync/connection_pool.py", line 196, in handle_request
  | 2024-06-24T13:12:34.175Z | response = connection.handle_request(
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpcore/_sync/connection.py", line 101, in handle_request
  | 2024-06-24T13:12:34.175Z | return self._connection.handle_request(request)
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpcore/_sync/http11.py", line 143, in handle_request
  | 2024-06-24T13:12:34.175Z | raise exc
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpcore/_sync/http11.py", line 113, in handle_request
  | 2024-06-24T13:12:34.175Z | ) = self._receive_response_headers(**kwargs)
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpcore/_sync/http11.py", line 186, in _receive_response_headers
  | 2024-06-24T13:12:34.175Z | event = self._receive_event(timeout=timeout)
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpcore/_sync/http11.py", line 224, in _receive_event
  | 2024-06-24T13:12:34.175Z | data = self._network_stream.read(
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpcore/_backends/sync.py", line 124, in read
  | 2024-06-24T13:12:34.175Z | with map_exceptions(exc_map):
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/contextlib.py", line 153, in __exit__
  | 2024-06-24T13:12:34.175Z | self.gen.throw(typ, value, traceback)
  | 2024-06-24T13:12:34.175Z | File "/var/lang/lib/python3.10/site-packages/httpcore/_exceptions.py", line 14, in map_exceptions
  | 2024-06-24T13:12:34.175Z | raise to_exc(exc) from exc
  | 2024-06-24T13:12:34.175Z | httpcore.ReadTimeout: The read operation timed out
  | 2024-06-24T13:12:34.175Z | The above exception was the direct cause of the following exception:
  | 2024-06-24T13:12:34.175Z | Traceback (most recent call last):

hi @osamabinsaleem
If you need to increase the timeout because the file is larger, you can follow the docs here:
https://developers.deepgram.com/docs/python-sdk-pre-recorded-transcription#increasing-the-timeout-for-processing-larger-files

I'm doing the same thing. Can I increase it to more than 300 as well? @dvonthenen

of course! that's the point of that timeout field! we have a default (don't need to specify the timeout parameter at all), but if you need something other than default, you provide the timeout parameter plus whatever values you want.


Bump log4j to 2.17.1

Is your feature request related to a problem? Please describe.
Coming from https://github.com/opensearch-project/opensearch-build/issues/1417, Log4j 2.17.1 is available with CVE-2021-44832.
Describe the solution you'd like
Bump log4j to 2.17.1.

Closed with #1551


Failed to install V2

D:\data\node2-react\react-auth-box>npm i @zk-kit/identity @zk-kit/protocols @semaphore/contracts --save
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/@semaphore%2Fcontracts - Not found
npm ERR! 404
npm ERR! 404  '@semaphore/contracts@latest' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
npm ERR!      C:\Users\twj\AppData\Roaming\npm-cache_logs\2022-02-11T06_59_08_499Z-debug.log

获取不到 这个@semaphore/contracts

Hi @twjjw , the contracts' package is @appliedzkp/semaphore-contracts now. Sorry we are updating documentation and packages very frequently, soon they will be more stable


Problem in using same Channel for multiple RPC concurrently

Should this be an issue in the gRPC issue tracker?
Yes
What version of gRPC and what language are you using?
GRPC 1.3.6
What operating system (Linux, Windows, …) and version?
Windows
What runtime / compiler are you using (e.g. python version or version of gcc)
VS 2017
What did you do?
I was streaming a call through Channel. Then made another Single RPC using the same channel. There is lot of delay in getting the result of Single RPC.
What did you expect to see?
Immediate result of Single RPC.
What did you see instead?
Single RPC took lot of time and only got result when I get Streaming RPC Result.

If 2 streams are using the channel. Both reply come at same time irrespective of Sent Time

When streaming is done using a channel, other calls made through that channel gets Delayed.

This issue occurs only in C#.

@varshanbp this needs to be qualified a bit more, otherwise it looks hard to say if there's an issue (is this a performance related?). RPC's on the same channel are meant to be concurrent on the same connection.

This must be Performance related.
When streaming, if another RPC is made then it takes lot of time. This happens only when using C# as server. This does not happen on Java Server.


untrack in/out files; convert to template repository; make 'release'

Once dev complete, will want to make a 'release' of this, probably with Zenodo DOI?
Make sure it doesn't have any lingering files from dev

closing, this is already addressed in template repo


fix(Form): fix getValibotError to avoid importing safeParseAsync

Ref: #617

Thanks for the fix! 😊


Publish to Github & login fails "...Please upgrade VS Code..."

Azure Data Studio Version:1.37.0 ( vscode 1.59.0)
OS Version: Win10 20H2

Steps to Reproduce:

Publish to Github
2.it routes to login via Edge to https://vscode-auth.github.com/ and gives the message

I have upgraded VSCode and rebooted my laptop, still I cannot publish to github

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

Strange thing is when I start VSCode, it shows following information: !!!
Version: 1.69.1 (user setup)
Commit: b06ae3b2d2dbfe28bca3134cc6be65935cdfea6a
Date: 2022-07-12T08:21:24.514Z
Electron: 18.3.5
Chromium: 100.0.4896.160
Node.js: 16.13.2
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19042

Duplicate of https://github.com/microsoft/azuredatastudio/issues/19979
As a workaround you can try publishing the branch using the git CLI and authenticating through that, after which you should be able to push commits through ADS again.

Azure Data Studio Version:1.37.0 ( vscode 1.59.0)

OS Version: Win10 20H2

Steps to Reproduce:
1. Publish to Github
   2.it routes to login via Edge to https://vscode-auth.github.com/ and gives the message

I have upgraded VSCode and rebooted my laptop, still I cannot publish to github
Does this issue occur when all extensions are disabled?: Yes/No

The reason for my problems was, I wasn't presented a "personal account" to use during the login process.
Hence devops got mixedup because or the login failed (password) or the login succeeded but the userid no longer matched ( in the background), resulting in failed login.
I managed to correct this and now ads seems to remember the account to use.