Which Mac models/processors support this app?

I was unable to install the app and I assume that it's because my computer is too old. If it only works on newer macs or a certain type of processor then we should document that on the release notes.

The home page clearly says that this app is not supported on Intel Macs, but that doesn't excuse the need for it. Documentation on how to build the platform applications is critical - should be a separate issue.
I've had some experience in building python executables (see bdrc-bag), if you want to do that.

The home page clearly says that this app is not supported on Intel Macs, but that doesn't excuse the need for it.

That is correct. Sorry, I overlooked it!

The home page clearly says that this app is not supported on Intel Macs, but that doesn't excuse the need for it.

According to Claude we might want to say:
"This application is compatible with Apple Silicon Macs (M1, M2, and M3 processors) only. It is not compatible with Intel-based Macs.
To check your Mac's processor type, click the Apple menu () in the top-left corner and select 'About This Mac.' Your processor type will be listed under 'Processor.'"


Change the format of the expected_output enum

Right now, the expected output format is like number_1_TopAnswer. Do we like this format, or could it just be "TopAnswer"?

That sounds good. The main thing to keep in mind is that we want options within a given column to be mutually exclusive. If people want to add a concept that is not mutually exclusive, it probably merit another existing/new column. @RichardBruskiewich @sandrine-m

we currently have three different representations of "expected result" in three different layers of our new testing infrastructure:

in the spreadsheet we have values like "4_NeverShow" and "1_TopAnswer"
in the formalized TestCases that are generated from the spreadsheet we have values like "number_4_NeverShow" and "number_1_TopAnswer"
in the P/F runner we use values like "NeverShow" and "TopAnswer"

Should we just use the text descriptions for now?
Should we instead break this into two columns?   What do the numbers mean?  From the use cases we have now, it seems like we could use just the text, but I don't want to be short-sighted either.

Second question: does TopAnswer truly mean "the top answer, the first answer returned after all results are in"?  or does it mean "in the top 5% of answers returned when all the results are in"?
If it means "the top answer, the first answer returned after all the results are in" then queries in the P/F test runner that group results based on input_id and query  will fail if all the individuals in the group want to be the "TopAnswer".
e.g.
ARS_Test_Runner --env 'ci' --query_type 'treats_creative' --expected_output '["TopAnswer","TopAnswer"]' --input_curie 'MONDO:0005301' --output_curie  '["PUBCHEM.COMPOUND:107970","UNII:3JB47N2Q2P"]'

will always fail.

I am not sure the numbers have a non redundant information with the value top answer, etc. and I would be ok with removing the numbers. However I defer to @jh111 to give supplementary info on that aspect and decide on the vote.
Regarding the top answer, the way I curated the (little) data in this category has always meant "in the top 5% of answers returned when all the results are in" so if "the top answer, the first answer returned after all results are in" is chosen, we will need to review those results as well.

I'd say simple text is fine, and we can add more columns and/or test case code logic if needed in the future. I has just used numbers out of habit during initial design because it allowed sorting.


Child objects of a mesh exported as bone don't export properly if the mesh doesn't have scale 1.0

Image 1: The yellow cube is a parent of purple cubes and has scale 1.0. Model exports properly

Image 2: Same as the image 1 but yellow cube has scale 3.0. Bad export.

Image 3: In blender the red cube is the parent of the yellow cube and the purple cubes are the children of the yellow cube. No mc_is_bone property so in minecraft the red cube is a bone and all of the other cubes aren't. The model exported properly

Imge 4: Same as image 3 but added is_mc_bone property to the yellow cube. This makes the red and the yellow cube bones. The bug is visible again.

The origin point of the tall purple cuboid is at its bottom so its closer to the yellow cube which mkes the bug less appearent

Bug introduced somewhere between 3.2.0 and 3.2.1

Bug introduced with 1e12fe6 commit


Bug : French automatic translation translated "Stage" as "Étape"

In Azure DevOps, the term "Stage" is translated to French as "Index".
But the Azure DevOps documentation the term "Stage" is translated to French as "Étape".
A other Azure Pipeline concept, "Step", is also translated as "Étape". This is confusing.
Example :
Azure Pipelines Nouveau guide de l’utilisateur-concepts clés - Azure Pipelines | Microsoft Docs
In English :

Stage
A stage is a logical boundary in the pipeline....
Step
A step is the smallest building block of a pipeline...

In French :

Étape
Une étape est une limite logique dans le pipeline....
Étape
Une étape est le plus petit bloc de construction d’un pipeline...

Can you improve the translation by forcing the translation of related terms to Azure DevOps' concepts?
For example, by forcing the bot translator to translate "Stage" by "Index" in French.
The best will be to have a dictionary coherent between Azure DevOps and this documentation.

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

ID: 7f8c8539-89a7-a426-868b-96e961c39e29
Version Independent ID: de260a68-aab7-7c6b-6727-90c92c65b225
Content: Azure Pipelines New User Guide - Key concepts - Azure Pipelines
Content Source: docs/pipelines/get-started/key-pipelines-concepts.md
Product: devops
Technology: devops-cicd-get-started
GitHub Login: @juliakm
Microsoft Alias: jukullam

@vernou Thanks for your feedback; we appreciate it. You can submit issues related to overall site experience, or suggestions for improved site functionality or design, at https://aka.ms/sitefeedback/.


Renaming master branch to "main"

If there's no objection, I'll rename the master branch to "main" next week.

No objection here.

Done.


6 second exposure takes 50+ seconds to capture?

following the low light recipe relatively closely, with a shutter_speed of 6000000 which should be 6 seconds, the camere takex about 50 seconds to return an image.
Interestingly, I actually tried to wait 30 seconds before, and whether or not I wait, the camera always takes the same amount of time, within ~500ms
additional notes: in my specific case, I timed the time from when my command started and when the captured file was finished uploading and it was 56seconds every time, and I estimate 3-5sec overhead from the rest of the command. it did execute at that length within ~500ms. 5 second shutter took about 48 seconds I believe.

Covered many times before in the forums, eg https://www.raspberrypi.org/forums/viewtopic.php?t=164007#p1059785, although 50 seconds sounds a bit high.
The minimum I'm expecting is

expose and read out one invalid viewfinder frame - 6 seconds
expose and read out one valid viewfinder frame - 6 seconds.
stop the sensor and reprogram.
expose and read out one invalid  capture frame - 6 seconds
expose and read out one valid capture frame - 6 seconds

So a minimum of 24 seconds to get one capture frame. I've just confirmed that with raspistill -ss 6000000 -t 1 -ag 1.0 -dg 1.0 -o foo.jpg taking approx 32 seconds to complete, which includes 12 seconds to shut down (it's asked for another preview frame, and has to wait for that to complete).
Seeing as the low light recipe at https://picamera.readthedocs.io/en/latest/recipes1.html#capturing-in-low-light also includes a sleep(30), is that where your extra delay is coming from?

Thanks for the extra info.
That's what stumped me, I get 56 seconds whether or not I wait before or not.
It might be because I'm running the camera in executor since this is in an async application?
I suppose because I'm waiting in async the camera is doing it's 50 second prep work during the wait?
Is there anything to cut down on that time? Fix values or something? seems like a lot of unnecessary work being done.

There isn't much you can do to reduce the initial time.
You can use burst mode to reduce the time between captures. It tells the camera not to switch back to viewfinder mode after each capture, therefore saving the time to complete the unwanted viewfinder frame. It'll still take the 12 seconds per capture though.

12 seconds would be fine but the 56 are kinda insane.

Not much I can do here I'm afraid; running the low light example regularly (no async) without the call to sleep() results in a similar 32 second capture (basically the same as 6by9's raspistill example). I can't say asyncio (or whatever async layer is popular at the moment) is something I have any intention of supporting given picamera is pretty heavily thread based (and has to be, at least partially, as the thread which feeds picamera data is outside of picamera's direct control). You may be best off using a separate process for the picamera portion and feeding things to your async process via a pipe.


fix: partial error correction

The original developer has abandoned the project. The core team does not maintain or develop it. If you want, I can give you write access to this repo.

@or-else Hi, I will be able review it and add the changes

@rxmoein Thanks!

I can give you write access to this repo

Thanks!

I made a mistake, Sorry😄


New App: Movie Night

Description
Displays a marquee for a movie title and a countdown until show time, both based on user input. Shows a fixed headline of "Movie Night" and camera gif effect.
Screenshot

I have read the CLA Document and I hereby sign the CLA

Thanks for the PR!


Nuxt generated project has wrong axios call

Hi guys,
I am using nuxtent to generate static site, here is my issue:
with such nuxtent config:
  content: [
    [
      'project/node/',
      {
        page: 'project/node/_slug',
        permalink: 'project/node/:slug',
        isPost: false,
        generate: ['get', 'getAll']
      }
    ]
  ]

and content folder:
content
  |- project
  | |- node
  | | |- post1.md
  | | |- post2.md

nuxt generatewill create something like
dist
  |- _nuxt
  | |- content
  | | |- project
  | | | |- node
  | | | | |- project.node
  | | | | | |- post1.json
  | | | | | |- post2.json

however, after I host the dist folder and want to check post1, axios will ask resource from https://domainname/_nuxt/content/project/node/project.node.post1.json
and cause an error since the right path should be
https://domainname/_nuxt/content/project/node/project.node/post1.json.
I can make thing work by adding a line in
https://github.com/nuxt-community/nuxtent-module/blob/8f7afaa87706b27b30b927371eadd88b2a2b6ec2/lib/plugins/requestContent.js#L37
to replace the last dot to slash:
const allButFirstSlash = /(?!^\/)(\/)/g
const lastDot = /\.(?=[^.]*$)/
const serializedPermalink = permalink.replace(allButFirstSlash, '.').replace(lastDot,'/');

I think another solution is to rearrange how nuxtent generate nuxt routes in
https://github.com/nuxt-community/nuxtent-module/blob/8f7afaa87706b27b30b927371eadd88b2a2b6ec2/lib/content/build.js#L122
to make nuxt generate based on page path and content name

Is a folder named project.node? If so then yea it uses regex to match routes so we'd need to improve the command but this is a pretty unusual case, not sure if it is even recommended to use periods in file names

Yeah. I don't think it is an unusual case. It seems like if the permalink contains path

in order to inject right path to the nuxt->generate->router config https://github.com/nuxt-community/nuxtent-module/blob/8f7afaa87706b27b30b927371eadd88b2a2b6ec2/lib/content/build.js#L121-L124

then the generated nuxtent content folder in dist will contain periods in file names.
I dislike those periods either but I have no choice. As I said, maybe it's better to leave permalink out of path info, and inject both path and permalink in the code above
Anyway, thank you so much to create this tool, the normal SSR function works pretty well. But I have to use nuxt and nuxtent to generate static site, so...

I'm sorry I'm not fully understanding - is an error only occurring when you generate the content? If so then yes it deals with the build file.
The problem likely lies here:
https://github.com/nuxt-community/nuxtent-module/blob/8f7afaa87706b27b30b927371eadd88b2a2b6ec2/lib/content/build.js#L5-L12
Feel free to do a PR and if you have questions you can ask them in the slack channel

cool, I will give it a try


cmake/tricore/tasking: add cmake build for tasking toolchain

Summary
cmake/tricore/tasking: add cmake build for tasking toolchain
cmake build for tasking toolchain
Signed-off-by: chao an<EMAIL_ADDRESS>Impact
N/A
Testing
ci-check

[Experimental Bot, please feedback here]
Yes, the PR appears to meet the basic NuttX requirements.
Here's why:

Summary:  Provides a clear description of the change (adding cmake build for the tasking toolchain).
Impact: While marked "N/A," it's likely there's some impact. Even if minimal, it's helpful to be explicit (e.g., "Only impacts Tricore builds by enabling cmake").
Testing: Indicates "ci-check," suggesting CI testing is in place. However, providing snippets of relevant logs (as the template encourages) would greatly strengthen the testing confirmation.

Suggestions for Improvement:

Expand on Impact: Even if small, outlining the specific impact makes it easier for reviewers to assess the change's scope.
Provide Testing Details: Include a brief excerpt of the logs, highlighting the key changes observed before and after your modification.
Consider Cross-Referencing: If this PR fixes a specific issue, adding "Fixes #[Issue Number]" links it directly, making the PR's purpose even clearer.


Choose the size of the input ring buffer based on the stream parameters

This fixes BMO#1725203.
The method discard of ringbuf wasn't available in the version we had.

Rebased and used a constant to implement what I said above.


Add non-goals

Perhaps next to the road map, add a "non-road-map" with the non-goals, i.e. things that sound like nice features but which we do not intend to implement for reasons to be stated in the new section.
Ideas so far:

Rule templating language.
Strings as sample values (and neither ints...).
Support event logging / become a log db.

More?

Supporting JSON as a scrape format
Long term storage in prometheus (hopefully)
Per-host aggregators
SSL and auth for our http frontends (use a reverse proxy)

Retention policies (use remote storage for that)

I personally wouldn't rule out retention policies (deleting certain series completely after a configurable time, not talking about downsampling here). It shouldn't be too hard to add and could be quite useful.

Configurable logging (use a pipe)

A single exporter per machines/service reporting in node exporter

Thinking last night this is probably also the place to list our assumptions about the minimum state of your infrastructure (machine database, service database, configuration management), and that we won't add features solely to workaround the lack of same.

While I strongly disagree with the "no long-term storage" bit, a constraints section which lists design non-goals, anti-patterns, and basic requirements would make sense.

To clarify, the long-term storage part means we do not intend for the storage layer to become one. We do however intend to provide better integrations with existing storage solutions to serve as a LTS for Prometheus data. Compared to what we have now, this especially means read-back support.

Just to make sure: The plan is to put historic data into some other storage engine at a magic cut-off point to maintain performance for near-time metrics while retaining full information for old data?
Sounds good to me :)
As an aside, it might make sense to detect frequently-accessed historical data to keep that in warm storage.

As an aside, it might make sense to detect frequently-accessed historical data to keep that in warm storage.

I was thinking about a simple query cache here. Queries to the LTS backend only have to be repeated if the most recent sample (per timeseries) is now beyond the rentention period of the Prometheus server (or if the query result has been evicted from the cache due to memory constraints).
But note that there a lot of more urgent features to implement before we'll tackle read-back from LTS.

Non-HTTP scraping

Metrics expiry/timeout in pushgateway

Configuration being provided any way other than files on disk

Anomaly detection (besides manually defined rules)

"Anomaly detection" is a very general term. How about "Machine learning, data mining, business intelligence"?

For client libraries: non-blocking APIs for the pushgateway

Anytime to do with timezones (but local time as reported by your browser may be used in places)

Anything that tracks/manages human responses to alerts (Use pagerduty&friends)

Adding math to Prometheus console/alert templates (put it in the expression)

Alertmanager permitting every single alert/resolution being turned into a notification (use alert stream from Prometheus directly)

Non-standard and/or vendor specific authentication mechanisms for scraping

TLS and authentication in HTTP serving endpoints should delete from roadmap docs (https://prometheus.io/docs/introduction/roadmap/)?

It's the other way round. The roadmap is more up to date than this.


Better UI of Create Your Resume Page

I would like to improve the UI of Create Your Resume Page, Can I work on this?

i would like to implement it


Remove isolated storage and temporarily disable replays

As part of our redesign for Quark v2, we decided to scrap isolated storage to simplify the flows for executing a Quark operation and lower the gas overhead.
By removing isolated storage, we can remove the callback (setActiveNonceAndCallback) from the QuarkStateManager to the QuarkWallet. We can also remove the codepaths related to activeNonceScript, nonceScriptAddress, and walletStorage. This leaves only the nonce tracking logic in the QuarkStateManager.
We are also temporarily disabling replay functionality in this PR.  I've commented any tests that have to do with replays, leaving a TODO (// TODO: Uncomment when replay tokens are supported) to revisit once they are supported again.
There are also some TODOs to switch from sstore/ssload to tstore/tload. To use tstore/tload, we need to bump up our version of Solidity to >0.8.24. I plan to do that in a separate PR.

We should remove nonce bucketing, nextNonce, etc. since we're all-in on random nonces.

Yeah, that is done in 👨🍳's PR. This PR only removes isolated storage and leaves nonces alone.

QuarkStateManager will no longer make much sense as a name, I think at this point it would be cool to rename to QuarkNonceManager when we're ready.

Similarly, this will be done in a separate PR to keep the changes smaller.


updated seed file with new data - Man

Naming Rules
Name your PR like this: ISSUENUMBER-TITLE-YOURNAME
Description

updated seed file with new rhythms and rhythm codes data provided by Greg and Deirdre
included dot ID's for the new data
updated rhythms table to include images data column
updated api call to include images in the database query

Note: the images data is not currently being used in the website at the moment, potentially implemented in a future release
Related to
Make sure you include the issue number with a hash sign # so Github can link this PR to the right issue, like this:
Fixes #1
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have carefully reviewed my own code
[ ] I have commented my code
[ ] I have updated any documentation


handle non-String onchainMetadata fields

Changed the type of onchainMetadata from Map<String, String> to Map<String, Object>  to allow for deserialization of complex object values
Added an IT against a testnet asset that has an onchainMetadata field ("files") which is of type List<Map<String, String>>

I need to update the PR, I think the ITs fail because it uses Java 8 and I used Map.entry which is since Java 9.

@bentaye Thanks. IT build is successful but some IT tests are failing which are not related to your change. I am merging this PR for now.


Will copy and paste my tagui folder to my friend's laptop work?

pre-emptive query for visual automation release #386

Typically yes. However, if you are using visual automation, your friend have to download from the packaged installation from below link, instead of copying your tagui folder.
https://github.com/kelaberetiv/TagUI#set-up
This is because while the packaged installation comes with SikuliX binary and Jython binary, during the first use, SikuliX will move the Jython binary to an appropriate Java files location on your computer.
That means if you copy tagui folder to your friend's laptop, the Jython binary would already be missing and would not let TagUI visual automation work. Thus it is recommended to download directly from above packaged installation.


Complete assoc. items on type parameters

This is fairly messy and seems to leak a lot through the ra_hir abstraction (TypeNs, AssocItemId, ...), so I'd be glad for any advise for how to improve this.

Thanks for the review, I've pushed a new version that's much cleaner.

LGTM otherwise.
bors d+

bors r+


Documentation overhaul

Fixes:
#207
#220
The structure of the documentation has been reworked extensively:

The landing page gives more information
The left navigation bar is divided in two parts: User / Developer
The former intro was turned into a larger Getting Started section with multiple pages (providers, product types, ...)
Most of the tutorials were turned into an API User Guide section with multiple pages (configure, search, filter, ...). Each page describe how to use the main features of EODAG.
The remaining tutorials were kept in a tutorials section
A section is dedicated to STAC support with a Client page (the original tutorial) and a REST Server page (also the original one)
The former Python reference has become an API reference (user-oriented) and a Plugins reference (developer) oriented

Since it felt like a new website, it required a new theme! I've found the sphinx-book-theme very easy to set (good and concise documentation).
Regarding how the docs are built:

I setup nbsphinx to run some notebooks (3 currently). I believe it's easier to maintain a documentation in sync with the code if the notebooks are run. However I didn't want to have nbsphinx run the notebooks that search for data or download data, that would just make building the docs too long, if that would even be possible.
I pinned the docs dependencies (e.g. sphinx), I believe this can only help us. Let's update them from time to time.
I added a configuration file for readthedocs (readthedocs.yml). I'd like to set readthedocs to fail whenever there is a warning, this should help to keep the docs well maintained.

Notebooks:
They are all in docs/notebooks and divided under tutorials and api_user_guide. There is a simple markdown page in this folder that links to the notebooks. Its aim is to be the landing page of the Binder badge in the README and on the index page. This structure would also make it quite easy for a user to save the notebooks and run them locally, or to give a live tutorial session.
Some additional changes:

CS website updated
Cleaned up conf.py and .gitignore
Update the contribution guideline
Removed the burnt area detection tutorial with gpt (kept the one with snappy)
Preferred folium over ipywidgets for plotting the products in the API user guide (it gave me some ideas for a .plot_map() method for SearchResult)

To complete this PR:

[x] Fix the post-process notebook

Note for a next PR:

Rerun some of the notebooks to save their widget state (I'd like to wait until I have a better internet connection, possibly next Tuesday). I wrote the notebooks with VS Code, it doesn't look as nice as with Jupyter Notebook or Lab but it's quite nice to have them open right next to the code. There is no way however to save the widget states. => I think this is really fine by now.

I fixed the issue with the post-process notebook. I was passing an extent (i.e. crop window) to get_data that I believe was not fully contained within the product's extent.
I also addressed the comments that were made yesterday in our chat group.

Recent updates:

Add a note about installing pyproj with a too old version of pip (#220). A note here, if pyproj isn't necessary we should try to get rid of it, having it as a dependency can lead to lots of problems if one day eodag is used in a QGIS plugin
Re-run the notebooks that required to save their state and widget


QNAP sensor component fails to initialize

Home Assistant release with the issue:

0.86.4
Last working Home Assistant release (if known):
Operating environment (Hass.io/Docker/Windows/etc.):

Hass.io in Raspberry Pi 3
Component/platform:

QNAP Sensor
Description of problem:
Cannot retrieve Qnap sensor information. It can establish connection correctly (I can see it at QTS logs), so it is not a problem with credentials.
Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):
- platform: qnap
  host: !secret qnapip
  port: 443
  username: !secret qnapuser
  password: !secret qnappass
  ssl: true
  verify_ssl: false
  monitored_conditions:
    - status
    - cpu_usage
    - memory_percent_used
    - network_tx
    - volume_percentage_used

Traceback (if applicable):
2019-02-02 11:31:03 ERROR (SyncWorker_0) [homeassistant.components.sensor.qnap] Failed to fetch QNAP stats from the NAS
Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/homeassistant/components/sensor/qnap.py", line 186, in update
    self.data["system_stats"] = self._api.get_system_stats()
  File "/usr/local/lib/python3.6/site-packages/qnapstats/qnap_stats.py", line 207, in get_system_stats
    force_list=("DNS_LIST")
  File "/usr/local/lib/python3.6/site-packages/qnapstats/qnap_stats.py", line 69, in _get_url
    result = self._execute_get_url(url, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/qnapstats/qnap_stats.py", line 82, in _execute_get_url
    self._debuglog("Appending access_token (SID: " + self._sid + ") to url")
TypeError: must be str, not NoneType

Additional information:
QNAP TS-453mini running QTS <IP_ADDRESS>5.
My first configuration was throwing another error in the log. I solved it changing the credentials in secrets.yaml to the admin ones. It seems that the user has to be the administrator for the component to work.

Adding more information:
with HA 0.90.1 the error message is different, I think it is due to the new version of python:
Failed to fetch QNAP stats from the NAS
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/homeassistant/components/sensor/qnap.py", line 186, in update
    self.data["system_stats"] = self._api.get_system_stats()
  File "/usr/local/lib/python3.7/site-packages/qnapstats/qnap_stats.py", line 207, in get_system_stats
    force_list=("DNS_LIST")
  File "/usr/local/lib/python3.7/site-packages/qnapstats/qnap_stats.py", line 69, in _get_url
    result = self._execute_get_url(url, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/qnapstats/qnap_stats.py", line 82, in _execute_get_url
    self._debuglog("Appending access_token (SID: " + self._sid + ") to url")
TypeError: can only concatenate str (not "NoneType") to str


WebApp - AirDrop Tracking

Is your feature request related to a problem? Please describe.
Implement feature airdrop tracking for product web app
https://twitter.com/leap_cosmos/status/1669381891596902400
List task:

[x] Organize information on Strapi: @anhntk54

Link doc: https://www.notion.so/subwallet/Li-t-k-c-c-th-ng-tin-v-danh-s-ch-mission-pool-cho-t-nh-n-ng-Airdrop-0577e14e5b624eb4b2924ba5865946db?pvs=4#813965137f82454ab029c2f831a95fb9

[x] Implement Mission Pool: @lw-cdm

Link design: https://www.figma.com/file/2nYhrm0rlJtfJoMwrT51Ep/SubWallet-Apps?type=design&node-id=11173-199586&mode=design&t=jGgnQcwtDo6Fh63K-4

Version test: https://9f2b9230.subwallet-yield.pages.dev/mission-pools

[ ] Handle case scrolling

Version test: https://edbeb6c4.subwallet-webapp.pages.dev/

[ ] Show Rewards = $NaN even though Total rewards > 0

Version test: https://45bc2cca.subwallet-webapp.pages.dev/

[ ] Handle case multi network


NavBar /[lesson]/ path display

At the moment the filesystem in our app is designed such that /chapters/[slug]/[lesson] this limits us to having only a single introduction page, specifically on /chapters/chapter-1 before it moves on to the lesson content. Adding multiple introduction pages creates problems based on the 2 possible paths.

Create a new dynamic path such that /chapters/[slug]/[intro] OR [lesson]. however, this is not possible according to @vinayaksh42 research on it in #259
[current method] Simply add any introduction page beyond the second one to the [lesson] path. However, this causes the site to treat the introduction pages following the first one AS a lesson, creating some confusion or at least it leaves us with a poorly optimized NavBar tracking; being incorrect most of the time.

Paths forward:

Allow the copy in each page be custom set in the NavBar and thus allow us to make it whatever we want but we would have to make it every time
Find a way to redesign the [lesson] path to become a [page] path in which the layout is organized as follows:

Intro
-Will not display Challenge numbers in the NavBar

Challenges
-Will display Challenge numbers based on the lesson content in the NavBar

Outro
-Again will not display Challenge info in the NavBar

our problem is that the intro and outro can be only one page each

We should refactor how this chapter metadata is being utilized:
export const metadata = {
  position: 0,
  slug: 'chapter-1',
  intro: 'reaping-rewards',
  title: 'chapter_one.title',
  image: '/assets/images/chapter-1-cover.jpg',
  lessons: [
    'genesis-1',
    'genesis-2',
    'genesis-3',
    'transacting-1',
    'transacting-2',
    'transacting-3',
    'done',
  ],
  challenges: ['genesis-1', 'transacting-1'],
}

The intro could be named intros (or something similar) and its value should become an array similar to how lessons currently work. That would allow us to still only have a single intro page, but would also allow for more if necessary.
Is this required for the demo? If yes, I'll pick this up.

Your call on if you think its necessary for the demo!

Kevin how big is the lift? I'm optimistic about including this for demo as we currently only have 1 pending issue.


HLS Media Manifest wrong display (bionary instead of text)

Description
The body of a media manifest in HLS (video streaming) is displayed the wrong way in proxyman.
Steps to Reproduce
check how body of such request is displayed on Windows version of proxyman
https://streamsky.broadpeak.io/dtv-tv/hls_live_3538/live_3538-audio_72882_por=72400.m3u8?mm_sp&bpkio_sessionid=10e0c37b110-3f5c8b20-9af6-4729-aef6-4fcd0d818869&bpkio_serviceid=f9028faec74be6ec96e51487cac14033&category=all
Current Behavior
Wrong display of request body
Expected Behavior
have it displayed in text
Environment

App version: 2.10.0
Windows11 - build 22621.3007

Additionnal comment : I'm working with Fabre Lambeau, who talked to you few days ago, he told me your tool was wonderful and I wish I could be as happy as him :)

@SimonOliveau as this feature is implemented on the macOS (https://github.com/ProxymanApp/Proxyman/issues/1926), we will support it and send you a Beta build 👍


tagged type members should have their own scope

typedef unsigned char UC;
union {
        UC UC[1];
} data;
<stdin>:3:8: error: expected variable name or '(', got '['

Found while preprocessing https://github.com/jsoftware/jsource/blob/master/jsrc/vgsp.c.
Thanks for @memoryruins for pointing it out!

This is actually not a typedef issue, it's because tag members should have their own  scope. Compare the following programs:
▶ run_clang
typedef unsigned char UC;
UC UC;
<stdin>:2:4: error: redefinition of 'UC' as different kind of symbol
UC UC;
   ^
<stdin>:1:23: note: previous definition is here
typedef unsigned char UC;
▶ run_clang
typedef unsigned char UC;
union {
        UC UC[1];
} data;
int main() {
        return data.UC[0];
}

This is uncovering all sorts of bugs!
struct s {
        int f();
}
<stdin>:1:1: error: cannot take `alignof` function

More bugs:
typedef int I;
I I; // should be an error
<stdin>:2:5: warning: declaration does not declare anything

typedef int I;
int main() {
        I I; // should declare a variable of type int with name 'I'
}
<stdin>:4:2: warning: declaration does not declare anything

Hard cases to consider:
long const long i;

typedef long L;
int main() {
        long long ll;
        L L ll2;
}


Rename to rand-unique?

Would explain the key feature of this crate a little more clearly.

I spent a lot of time looking for a crate that provides this exact functionality, so I think your SEO could improve.

Okay, I'll take a look at doing so later this week, thanks!


Bulk user creation for every account in LDAP

I didn't see this mentioned in any of the documentation, but was wondering if there is a function to automatically create WordPress accounts for every user in LDAP.  I understand that the normal behavior is to create the WordPress account (and update it) whenever a user logs in.
However, I would like to be able to force account creation (or account updating) in a single process.  This process could be either a button to force the "sync", or could be setup as a cron job.
My use case for this is that I want to use a WordPress "newsletter" plugin for sending email notifications to various LDAP user groups.  The plugin allows sending to WordPress members according to "Role".  And authLdap allows to map LDAP Group Membership to WordPress Roles.  So I think this would allow me to automatically turn LDAP Groups into separate email subscriber lists.
However, I need to make sure that the WordPress user accounts are complete and up to date before sending the email.  In my case, I'm looking at about 1000-2000 user accounts, with users belonging to 1-6 groups each.  I can't expect that every user will have logged into WordPress, but I need their account to exist in WordPress whether they have logged in or not.
It would not be necessary to cache the password during this process since I don't need the password data.  But I would need to "sync" things like uid, group membership, and a display name.
Does this ability already exist in authLdap?  Or would it be possible to add it?
Thank you for the information and consideration!

Hi @bhotrock.
That's a great idea! But as far as I see it it's outside the scope of this plugin. This plugin handles authentication and authorization of users.
But I think there is a place for a different plugin that handles syncronization of users between LDAP and Wordpress. But that's not something that will be finished tomorrow! I will have to think through how it's possible to fetch all users from LDAP according to what criteria. Currently it's easy as I check whether the logging in user exists in the LDAP and is allowed to log in. For the sync I need to check for ALL users that are member of one of the allowed groups and fetch their information en block. That takes a bit thinking ;)

Thanks @heiglandreas for the quick response.  I can understand how it might be outside the scope of this plugin.  I just wanted to make sure I wasn't missing something that already existed.
  I think it's better to "do one thing, and do it well" as opposed to trying to be everything to all people.
Let me know if I can provide any more information or do testing for you.  I'm not in a rush for this as I'm just in the design phase right now.  Thanks for your awesome plugin!


Correct parsing of functions in namespaces in C++

Furthermore, this tries to mitigate the problem that types used within such a function could refer to a namespaced entity but are referred with its local name. Since this requires resolving of symbols in a frontend, we introduce a new annotaiton @ResolveInFrontend to warn developers.
Fixes #1070

@konradweiss Once this is merged, a 6.1 release would be nice


support background job

introduce Job type.
Job type has wait method for waiting process termination.
string representation of Job object is pid.
$ ping -c <IP_ADDRESS> &
(Async) 5678
$ var a = echo hoge &
$ $a
(Async) 5679
$ (echo huga &).wait()     # wait termination

when called destructor, not wait process termination (explicitly call wait method)
Job object maintain FD object (in, out, err)
normally, maintains dummy FD object
$a.in()
$a.out()
$a.err()
$a[0] # equivalent to $a.in()

if specify '&!', exclude job table, so shell dose not control job (if terminated, not send SIGHUP to job)

add syntax support in commit af11582b54cf8a734b5ed77e71eb8bd7be3f50c5

support disowned background job in commit e4a6582723bacbb3b85b0d2d0c33321bfd3a7b25

add basic support in commit 75b14f08043486079eb25e22ce053971807967d9


When sending commit's tags as object  not a literally string - posts are no accessible and  no errors in code

From @sleshJdev on April 22, 2018 6:27

Expected behavior
The code should validate json_metadata.tags field and raise an error if format is incorrent. Now the posts is created successfully.

Actual behavior
When send comment with tags like object, not simle literall string, there is no any error, but "Блог" page is no accessable by direct link, and posts are not displayed if navigate to the page using user interface.

How to reproduce
This is code sample:
golos.config.set('websocket', 'wss://ws.testnet.golos.io');
golos.config.set('chain_id', '5876894a41e6361bde2e73278f07340f2eb8b41c2facd29099de9deef6cdb679');

var username = 'comment-issue-1';
var password = 'P5JE51WedwSk8MKCtv2hHKHZZZGX8s66b6s6xSyrfqBHpk8JhnvG';
var keys = golos.auth.getPrivateKeys(username, password, ['posting']);
var wif = keys.posting;

var appName = 'comment-issue'
var parentAuthor = '';
var parentPermlink = 'username';
var author = username;
var permlink = appName+Date.now();
var title = appName;
var body = 'comment-isser';
var jsonMetadata = JSON.stringify({
  //pay attention a line below
  tags: [{ id: 1, itemName: "value" }]
});
golos.broadcast.comment(wif, parentAuthor, parentPermlink, author, permlink, title, body, jsonMetadata, function (err, result) {
  //console.log(err, result);
  if (!err) {
  	alert(JSON.stringify(result));
    return console.log('comment', result);
  } else {
  	alert(JSON.stringify(err));
  	console.error(err);
  }
});

Here is JSFiddle code snippet that reproduces the issue.
This one works correct

Befor run the code, create account and user his username/password to run this code.
Way 1
When it finished without error, try follow the link https://testnet.golos.io/@your-user-name in the browser.
Actual result:
Sorry! This page doesn't exist. Not to worry. You can head back to our homepage, or check out some great posts.
Expected result: created post should be displayed.
Way 2
Open "Блог" page thru user interface
Actual result: snipper is displayed, but posts are not loading
Expected result: posts should be displayed
My username on Golos.io: sleshjdev
Copied from original issue: GolosChain/golos-js#44

This issue was moved to GolosChain/tolstoy#648


convertFromRaw does not correctly check the size for arrays of structs

Related to https://github.com/jisotalo/ads-client/issues/53
Looks like it was fixed for arrays of basic types, but not for arrays of complex types.
Error:
ClientException: Given data buffer and data type sizes mismatch: Buffer is 16192 bytes and data type is 2484 bytes

Symbol Info:
{
  indexGroup: 16448,
  indexOffset: 841576,
  size: 16192,
  adsDataType: 65,
  adsDataTypeStr: 'ADST_BIGTYPE',
  flags: 8,
  flagsStr: [ 'TypeGuid' ],
  arrayDimension: 0,
  nameLength: 25,
  typeLength: 39,
  commentLength: 0,
  name: 'GVL_Var.TestArrayStruct40',
  type: 'ARRAY [0..10,15..30] OF DUT_Structure_1',
  comment: '',
  arrayData: [],
  typeGuid: 'efa3486981b90e95fbbf485c484d6131',
  attributes: [],
  reserved: <Buffer 00 00 00 00 00 00 00>
}

Result from readRawMulti:
{
  success: true,
  errorInfo: { error: false, errorCode: 0, errorStr: 'No error' },
  target: { indexGroup: 16448, indexOffset: 841576 },
  data: <Buffer 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 ... 16142 more bytes>
}

Output of getDataType from within convertFromRaw:
{
  name: '',
  type: 'DUT_Structure_1',
  size: 92,
  offset: 0,
  adsDataType: 65,
  adsDataTypeStr: 'ADST_BIGTYPE',
  comment: '',
  attributes: [],
  rpcMethods: [],
  arrayData: [ { startIndex: 0, length: 11 }, { startIndex: 15, length: 16 } ],
  subItems: [
    {
      name: 'TestInt',
      type: 'INT',
      size: 2,
      offset: 0,
      adsDataType: 2,
      adsDataTypeStr: 'ADST_INT16',
      comment: '',
      attributes: [Array],
      rpcMethods: [],
      arrayData: [],
      subItems: []
    },
    {
      name: 'TestReal',
      type: 'REAL',
      size: 4,
      offset: 4,
      adsDataType: 4,
      adsDataTypeStr: 'ADST_REAL32',
      comment: '',
      attributes: [Array],
      rpcMethods: [],
      arrayData: [],
      subItems: []
    },
    {
      name: 'TestString',
      type: 'STRING(80)',
      size: 81,
      offset: 8,
      adsDataType: 30,
      adsDataTypeStr: 'ADST_STRING',
      comment: '',
      attributes: [],
      rpcMethods: [],
      arrayData: [],
      subItems: []
    }
  ]
}

We can see the raw data's length matches the symbol's size, but the check errors. Using readSymbol or commenting out the check does result in successfully parsing the result.

I also encountered an issue with arrays of structs. I believe it is fixed in the upcoming v2.0, in case you'd like to give that a try:
 "ads-client": "^2.0.0-beta.3"

Migration guide: https://github.com/jisotalo/ads-client/blob/2.0.0-beta.3/MIGRATION.md

I can confirm that v2 does work.

Thanks for reporting! If everything works in v2, then I might not look into this.

Happy to wait for the v2 release. Closing this issue.


add front end, controllers and class dependencies for inverted index

Changes Unknown when pulling eebf12f2cfacdebc0152cac9b3835877d6c3ff09 on development into ** on master**.

Changes Unknown when pulling 465c26e3da1735607f3841a83e568a40c708b95a on development into ** on master**.

Changes Unknown when pulling 5eeec3c4ef07e180dd888d04f8bc36591c01babe on development into ** on master**.

Changes Unknown when pulling 0721905b118be63aa86cafdad57853a29ffb2a8a on development into ** on master**.

Changes Unknown when pulling 59c8bd0b8b8c92aa00acd7829897e66985df04a4 on development into ** on master**.

Changes Unknown when pulling 09ea4dd94ae67e8c723e172b0a465673a5edad90 on development into ** on master**.

Changes Unknown when pulling c607cd52670bd241f392e1a5b0a9850e71545215 on development into ** on master**.

Changes Unknown when pulling c607cd52670bd241f392e1a5b0a9850e71545215 on development into ** on master**.

Changes Unknown when pulling f32d7a3273fc639532e7e2cf679bcb88b8787a0e on development into ** on master**.

Changes Unknown when pulling f32d7a3273fc639532e7e2cf679bcb88b8787a0e on development into ** on master**.

Changes Unknown when pulling 407b09a1d0796e29766f8a888e4533759a28bbc2 on development into ** on master**.


More details regarding TPM device attestation issue

Regarding "issues with TPM device attestation in Windows 10, version 1809." please provide references for the issue and/or more description of the problem. Customers have been impacted by this and are asking for more details.

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

ID: 6867cc8c-868d-d472-8aa5-1ed5b94ced2c
Version Independent ID: 6822e12d-7474-9e49-1e8b-88f7eec3b22c
Content: Windows Autopilot Self-Deploying mode
Content Source: windows/deployment/windows-autopilot/self-deploying.md
Product: w10
Technology: windows
GitHub Login: @greg-lindsay
Microsoft Alias: greglin

@officedocsbot assign @mypil

@aaronstackpole - Thank you for submitting feedback.
I will get this issue over to the Win10 ITPro writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@aaronstackpole . More information about TPM  key device attestation .
https://docs.microsoft.com/en-us/windows-server/identity/ad-ds/manage/component-updates/tpm-key-attestation

I appreciate the link which describes what TPM Device Attestation is, note that this article does not explain why Windows 10 LTSC is no longer supported due to an issue with TPM Device Attestation. Please provide a link that describes the issue which makes this feature only work with the latest version of Windows 10 (1903) and will TPM Device Attestation work with this edition in six months?

@aaronstackpole . Reason is simple, win 10 LTSC might does not have the TPM device attestation policy.
Moreover device must be joined with intune or azure subscription.
I seen same policy in v1809 and 1903.

Correct, however that was changed about three weeks ago and it threw a three month process out a week before deployment and we want to know what changed because now we have to pay an extra $25,000 a year to use an edition of Windows 10 that supports this feature. Additionally we want to know if we select this edition will it still work in three months?
Sent from mobile

From: VARADHARAJAN K<EMAIL_ADDRESS>Sent: Monday, July 8, 2019 12:58:48 AM
To: MicrosoftDocs/windows-itpro-docs
Cc: Aaron Stackpole; Mention
Subject: Re: [MicrosoftDocs/windows-itpro-docs] More details regarding TPM device attestation issue (#4310)
@aaronstackpolehttps://github.com/aaronstackpole . Reason is simple, win 10 LTSC might does not have the TPM device attestation policy.
Moreover device must be joined with intune or azure subscription.
I seen same policy in v1809 and 1903.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/MicrosoftDocs/windows-itpro-docs/issues/4310?email_source=notifications&email_token=AB6JOAJD6FSHHMWF5Y5ZQTTP6LJRRA5CNFSM4H4UGQ52YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZMBPBA#issuecomment-509089668, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AB6JOAMFLGQQVNJRLBAHIODP6LJRRANCNFSM4H4UGQ5Q.

@aaronstackpole . For your current question, only article author and practical experienced users can give answer . Let wait for few days.

Hello @greg-lindsay , Can you please share your insight on the query by @aaronstackpole .
@aaronstackpole Can you please share what issues you are facing?

We have no link or other description available.  The problem is exactly as stated. There are issues. In other words, it doesn't work some of the time. It's a bug in how device attestation works in 1809, and it's fixed in 1903.


Add HCX Appliance healthcheck process before initiate Migration! in www.avshub.io portal

Hi Team,
It's glad to share feedback here. I reviewed the steps and documents provided in https://www.avshub.io/ . Its clear to understand end to end HCX configuration. I would like to add one missing part in this particular portal.
It would be really great if we amend HCX appliance basic health check procedure/ ccli commands before initiating migrations (like probe check/perftest /communication etc.,).

This is a great suggestion. I added a reference to this troubleshooting step in Module 2 Task 13. However, I will plan into adding more specific steps in the near future. Thank you so much @kambamchanu  for your contribution.
Please see: https://www.avshub.io/workshop-guide/module-2/module-2-task-13/


Certification readiness overview

Good information to track, what do you think about using the wiki for stuff like this?  On one hand it'd be nice to have updates tied to source...    So more casual maintenance via wiki might make sense.
Could of course check in now and revisit once we see how we do.

Another option could be to open a few topic issues with task lists.

Sure, this was just to have one place as overview. Then I would say two options
1.) We create a new discussion type (like the feature requests now) like "certification relevant todos"
2.) We use the project in github we have and create all these as entries there and label them with "cert" relevant
I did not really found a good way to make todos and status transparent (we also have the TODO.md basically) ... in fact we right now have 2 devs actively working ... you (@lauckhart) and me :-) Me on the core side, and you on generation right now ... so it is more about how we organize work here... (and for future ith more devs)

Converted to Project entries


Test fails thus no installation

Hi, first of all, thanks for the module.
Unfortunately, I cannot install it, because a test fails:
% zef install File::Directory::Tree
===> Searching for: File::Directory::Tree
===> Testing: File::Directory::Tree:auth('labster')
No such method 'child' for invocant of type 'Bool'
in block  at t/basic.t line 32
in block  at t/basic.t line 30
Looks like you planned 9 tests, but ran 7
===> Testing [FAIL]: File::Directory::Tree:auth('labster')

Which version of Rakudo and what operating system?

Ups. Sorry. Old rakudo version. 2016. I updated to the most recent one and installation works just fine. Sorry for the noise.

No problem at all.


Update kamon-core, kamon-prometheus to 2.1.17

Updates

io.kamon:kamon-core
io.kamon:kamon-prometheus

from 2.1.10 to 2.1.17.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.kamon" } ]

labels: library-update, semver-patch

Superseded by #669.


s/EnumMap/Map/

PR incase there is a reason no one has done this yet :)

err I didn't get them all. need case sensitive search.


Remove the requirement of virtualenv package on remote by using venv

Summary
@yahoo/ychaos-dev
Currently, ychaos requires virtualenv package to be installed on the target hosts.
With these changes, we should be able to remove that requirement by using venv which comes with python3

Fixes: #7
Checklist
Checklist (Developer)
Prerequisites

[x] I have read the contribution guidelines

Code Analysis

[x] Covered by Unittests
[ ] Security warnings ignored (Why?!)

Project related

[ ] Schema changed and is backward compatible.
[ ] Introduces a new sub-command for ychaos CLI

Autogenerated Files

[ ] Auto generated schema

Pre-Merge Checklist

[ ] All the build jobs are passing

Checklist (Reviewer 1)

[ ] Reviewed Source Code
[ ] Reviewed Tests (If applicable)
[ ] Reviewed Documentation (If applicable)

Checklist (Reviewer 2)

[ ] Reviewed Source Code
[ ] Reviewed Tests (If applicable)
[ ] Reviewed Documentation (If applicable)

All testing was done on a newly sprung-up host which just had python3 freshly installed
I noticed that the virtual env we created was using an older version of pip which were causing issues installing one of the dependencies
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-2z_fpzk0/cryptography/
You are using pip version 9.0.3, however version 21.1.3 is available.

Hence I had to mention to install a later version(20.2.3) of pip
Once that was fixed,
the next issue was while running
*** You may need to add PYTHONIOENCODING=utf-8 to your environment ***

Hence I had to include to export command while running ychaos on host

Can you please add a UT for MachineTargetExecutor that fails when and if the playbook tasks are changed?

Test on a host after I uninstall virtualenv
[asthomas@weighedmaid ~]$ sudo pip uninstall virtualenv
Found existing installation: virtualenv 20.4.3
Uninstalling virtualenv-20.4.3:
  Would remove:
    /opt/vz/1.0/bin/virtualenv
    /opt/vz/1.0/lib/python3.9/site-packages/virtualenv-20.4.3.dist-info/*
    /opt/vz/1.0/lib/python3.9/site-packages/virtualenv/*
Proceed (y/n)? y
  Successfully uninstalled virtualenv-20.4.3

[asthomas@weighedmaid ~]$ pip list
Package    Version
---------- -------
appdirs    1.4.4
distlib    0.3.1
filelock   3.0.12
pip        20.2.3
setuptools 54.2.0
six        1.15.0
wheel      0.36.2
WARNING: You are using pip version 20.2.3; however, version 21.2.1 is available.
You should consider upgrading via the '/opt/vz/1.0/bin/python3.9 -m pip install --upgrade pip' command.

ychaos_env has latest pip version
(ychaos_env) [asthomas@weighedmaid ~]$ pip --version
pip 21.2.1 from /home/asthomas/ychaos_env/lib/python3.9/site-packages/pip (python 3.9)

ychaos ran cpu_burn successfullly
─────────────────── YChaos, The resilience testing framework ───────────────────

                 YChaos CLI configuration
┏━━━━━━━━━━━━━━━┳━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┓
┃ Configuration ┃ Value                                   ┃
┡━━━━━━━━━━━━━━━╇━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━┩
│ _command_     │ ychaos ➡ execute                        │
│ config        │ prod                                    │
│ debug         │ False                                   │
│ no_color      │ False                                   │
│ testplan      │ /Users/asthomas/Test/Resilience/TP.yaml │
│ verbose       │ 0                                       │
└───────────────┴─────────────────────────────────────────┘

[11:02:02] Starting app                                              main.py:185
           Getting Test plan                                      __init__.py:88

           Starting attack. executor=machine                       execute.py:48

[11:06:07] Exiting with exitcode=0                                   main.py:279
────────────────────────────────────── ☀ ───────────────────────────────────────

Process finished with exit code 0

Please add an entry in docs/releases.md under Next release 0.2.0

I just tested the change on a VM. Works like a charm. Can you please do these changes to the documentation to remove virtualenv as a requirement.

https://github.com/yahoo/ychaos/blob/1cf3a0cb0de542544dff476e64b7bfeef4b04279/docs/get_started.md#L8
https://github.com/yahoo/ychaos/blob/1cf3a0cb0de542544dff476e64b7bfeef4b04279/docs/index.md#L71

I will approve once these above doc is updated. Thanks for this PR


ci: run tests on Python 3.10

The current error:
SolverProblemError

  The current project's Python requirement (3.10.0rc2) is not compatible with some of the required packages Python requirement:
    - dataclasses requires Python >=3.6, <3.7, so it will not be satisfied for Python 3.10.0rc2

  Because dataclasses (0.8) requires Python >=3.6, <3.7
   and no versions of dataclasses match >=0.6.0,<0.8 || >0.8, dataclasses is forbidden.
  So, because django-codemod depends on libcst (==0.3.20) which depends on dataclasses (>=0.6.0), version solving failed.

Which seems rather strange, because dataclasses is only required by libCST for Python<3.7. This is because poetry detects 3.10 as 3.1: https://github.com/python-poetry/poetry/issues/4354
It will be fixed in the next release of Poetry.

On 1.1.8, I'm getting this error: https://github.com/python-poetry/poetry/issues/4210
It's fixed on 1.2.0a2, but the SolverProblemError with dataclasses is not. It's backported to master, but not yet released.


Ability to specify chmod of file copied via provision file

Shouldn't provision mechanisms such as Ansible, Puppet or shell be able to set a files mode? I know they do; so, I'm curious what a use case for this is.

We use vagrant file provision for example to copy ssh keys from host to guest machine. It works nice on UNIX host systems, but when host is on windows then file has 0777 permissions after copying and ssh rejects unsecure key. I'm not sure how this option will be done. Maybe just by chmod via scriptlets.

That’s interesting if using the config object in Vagrant.

https://docs.vagrantup.com/v2/provisioning/file.html
At the moment I'll set this issue as won't fix because since i've added inline shell it can be done by just issuing normal chmod command.


thangs

thangs

This pull request will make the image slightly smaller and make a space between the text and the image


FIT-20894 Fix scanner dark preview

https://fitatu.atlassian.net/browse/FIT-20894

[x] disable CONTROL_AE_EXPOSURE_COMPENSATION option due to dark camera preview and stack effect on motorola phone

base na release


BUG feedback on page.window_frameless

Hello, there may be some problems with page.window_frameless. I can't hide the frame.
windows: Windows 10 22H2
python: 3.11
flet: 0.10.3
code:
`
import flet as ft
from flet import *
def main(page: Page):
page.window_max_height = 520
page.window_max_width = 400
page.window_frameless = True
page.spacing = 0
page.padding = 0
widthscr = page.window_width

page.add(
    ResponsiveRow(
        [WindowDragArea(
            Container(
                width=widthscr,
                bgcolor="blue",
                padding=15,
                content=Row([
                    Text(
                        "You Home",
                        size=30,
                        color="white"
                    )
                ])
            )
        )]
    )
)

ft.app(target=main)
`

I think what you need to hide is the window title bar, so you need to use the window_title_bar_hidden attribute. The following is how I do it in my personal project.
It should be noted that the three buttons in the upper right corner are all buttons I implemented myself, not the ones that come with it.

I think what you need to hide is the window title bar, so you need to use the window_title_bar_hidden attribute. The following is how I do it in my personal project. It should be noted that the three buttons in the upper right corner are all buttons I implemented myself, not the ones that come with it. !

 I read this out-of-date tutorial 10 months ago and caused this misuse, but he did use it successfully in his video demo, probably the updated "window_title_bar_hidden" later. Thank you very much for your correction! 比心哦~


cardiodynamics, assures

This pull request was generated by the 'mq' tool
[test]
flake rate: 0.2
logical conflict every: 1000
sleep for: 2100s
close stale after: 24 hours
[pullrequest]
requests per hour: 120
deps=[a,c]

/trunk merge


Remove support ember olds version

I want update addon ember-cp-validations removing support ember version < 2 for resolve build fail
Anyone know if they have someone using the old versions?
How long will they support these versions?
I would like to open a PR and update. But I would like your opinion?

We now support only Ember 3.28+


Added return lines as array

Added return data as array in function deline

Added with 361a2f1dbfbeda3d63fa00acf6c0e4513f908870. Thanks.


ci: temporarily disable snap release builds

Description
Disables snap release builds temporarily until we can fix it.
Screenshot (if UI-related)
To-Dos

[ ] Successful build yarn build
[ ] Translation keys yarn i18n:extract
[ ] Database migration (if required)

Issues Fixed or Closed

Fixes #XXXX

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

v1.9.1
GitHub release

Your semantic-release bot :package::rocket:


Unittests for auth-server?

Hi!
Thank you for your interesting crates!
But how do you start unittests for  auth-server?
cargo test --color=always --bin auth-server
test result: ok. 0 passed; 0 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.00s
cargo test --lib -- --list
Running unittests src/lib.rs (chat-grpc/target/debug/deps/auth-24863828a93cbefb)
server::validation::types::email::tests::email_missing_at_symbol_is_rejected: test
server::validation::types::email::tests::email_no_subject_is_rejected: test
server::validation::types::email::tests::empty_string_is_rejected: test
server::validation::types::email::tests::valid_emails_are_parsed_successfully: test
server::validation::types::firstname::tests::a_255_grapheme_name_is_parsed: test
server::validation::types::firstname::tests::a_empty_firstname_is_rejected: test
server::validation::types::firstname::tests::a_whitespace_only_firstname_is_rejected: test
server::validation::types::firstname::tests::firstname_consist_of_numbers_only_is_rejected: test
server::validation::types::firstname::tests::firstname_contains_numbers_is_rejected: test
server::validation::types::firstname::tests::firstname_longer_than_255_grapeheme_is_rejected: test
server::validation::types::firstname::tests::valid_firstname_is_parsed: test
server::validation::types::lastname::tests::a_255_grapheme_name_is_parsed: test
server::validation::types::lastname::tests::a_empty_lastname_is_rejected: test
server::validation::types::lastname::tests::a_whitespace_only_lastname_is_rejected: test
server::validation::types::lastname::tests::lastname_consist_of_numbers_only_is_rejected: test
server::validation::types::lastname::tests::lastname_contains_numbers_is_rejected: test
server::validation::types::lastname::tests::lastname_longer_than_255_grapeheme_is_rejected: test
server::validation::types::lastname::tests::valid_lastname_is_parsed: test
server::validation::types::password::tests::a_255_grapheme_password_is_parsed: test
server::validation::types::password::tests::empty_password_is_rejected: test
server::validation::types::password::tests::password_longer_than_255_grapehemes_is_rejected: test
server::validation::types::password::tests::valid_password_is_parsed: test
server::validation::types::password::tests::whitespace_only_password_is_rejected: test
server::validation::types::username::tests::a_255_grapheme_long_username_is_valid: test
server::validation::types::username::tests::a_username_longer_than_255_graphemes_is_rejected: test
server::validation::types::username::tests::a_valid_username_is_parsed_successfully: test
server::validation::types::username::tests::empty_username_is_rejected: test
server::validation::types::username::tests::username_containing_a_forbidden_character: test
server::validation::types::username::tests::whitespace_only_username_is_rejected: test

29 tests, 0 benchmarks  //   All tests for chat server only

cargo test --bin auth-server -- --list
Running unittests src/bin/server.rs (chat-grpc/target/debug/deps/auth_server-22599d13ee860ee9)
0 tests, 0 benchmarks

Thank you!

Hello and thank you for taking interest in the repo.
In order to run the test you have make sure that a redis and postgres instance is running on your machine, this can easily be achieved by running the bash scripts init_db.sh and init_redis.sh  (they use docker to setup a local instance, so make sure docker is installed on your machine). Note it's important that you execute the script from the root of the project folder , for instance like this ./auth/scripts/init_db.sh
prerequisites for init_db.sh
There are some further prerequisites that are need for running init_db.sh

The script internally uses psql command to make sure the db is up, so make sure it's installed on your machine
sqlx command is used to run the migrations, you can download it via cargo using the following link

After the instances for PostgreSQL and Redis are up and running use the following command to run the tests cargo test -- --test-threads=1 in /auth
Extra Clarification on the testing procedure
There is unit tests which is what you are seeing when running cargo test --lib -- --list but there is also integration tests which is in a separate folder called  tests in /auth. The command I provided above it will actually run 1 test at a time by default rust runs multiple tests at the same time, there was issues with flakey test if one runs multiple integration tests at the same time hence we only run 1 test at a time.
Feel free to ask me anything :)

Excellent work!


Convert CollectsEventsFromEntities to listener

This fixes the following deprecation in Symfony 6.3:
Since symfony/doctrine-bridge 6.3: Registering "SimpleBus\DoctrineORMBridge\EventListener\CollectsEventsFromEntities" as a Doctrine subscriber is deprecated. Register it as a listener instead, using e.g. the #[AsDoctrineListener] attribute.

In this case we should also remove the EventSubscriber interface and the getSubscribedEvents from the CollectsEventsFromEntities class to not have any confusions that they are still used

Thanks, fixed.

CI Issues do not seem related to this issue.

Handled in #180


On recursive get, skip directories when writing files.

When using get with recursive=True, I was getting errors on the directory nodes because it was trying to write to them as a files. This fixes the problem.

Fixes https://github.com/dask/gcsfs/issues/248 ?

Yes, it should. As https://github.com/vincentlepage said, it appears it
would happen on any recursive copy.
On Fri, Apr 17, 2020 at 4:57 PM Martin Durant<EMAIL_ADDRESS>wrote:

Fixes dask/gcsfs#248 https://github.com/dask/gcsfs/issues/248 ?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/intake/filesystem_spec/pull/279#issuecomment-615460146,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAVIZYXIS3KA3WWF5VLAQSDRNC7EDANCNFSM4MLBAIFA
.

Actually this probably needs a more comprehensive look. While it fixes the recursive get, I'm not sure what the behavior should be for all the other the combinations of lpath and rpath: dir or file, top-level lpath exists or doesn't exist. This may break other behavior.


Pass AWS and stream link arguments in docker run

How can I pass the:
AWS_ACCESS_KEY_ID=<AWS_ACCESS_KEY_ID> AWS_SECRET_ACCESS_KEY=<AWS_SECRET_ACCESS_KEY> ./kvs_gstreamer_sample <STREAM_NAME> <RTSP_URL>
Directly in the docker run?

I'm also curious and having this issue.

docker exec -it <image_id> /bin/bash -c "<CREDENTIALS> ./kvs_gstreamer_sample <StreamName> <RtspUrl>"

Reference: https://docs.docker.com/engine/reference/commandline/exec/

We've updated the documentation to include instructions for this: https://docs.aws.amazon.com/kinesisvideostreams/latest/dg/examples-rtsp.html


nw.js: document is not defined

I'm a bit new to all this so it's probably an issue with my (lack of) understanding of nw.js or JS in general but any pointers are appreciated!
I tried require()ing in the normal way and upon running my app I am told:
"Uncaught ReferenceError: document is not defined".
I have also tried linking to the dragdrop.bundle.js as the src of a script element but I am a little unsure what the line "This exports a DragDrop function on window" means and so I'm not sure I have tried to use it properly. The error I am getting reads:
"Uncaught TypeError: Cannot read property 'addEventListener' of null".
I would really like to use your module rather than the clunky offerings from HTML5 (which do seem to be working for me)! Thanks for any help you can offer.

I think that in nw.js you always need to refer to things as either on window (browser context) or global (node.js context). So, inside this module we use document instead of window.document.
I just attempted to fix that for you. Can you try updating to the latest drag-drop v2.3.1 and try again?
npm install drag-drop

Also, if you still want to go with the script tag approach, "This exports a DragDrop function on window" just means that you can use DragDrop by referencing it on the window object.
<script src="/path/to/dragdrop.bundle.js"></script>
<script>
window.DragDrop() // use it like documented in the readme
</script>

That was an insanely fast response, thanks! Just updated my initial comment with the error message when using the script tag approach (in the way you mention).
"Uncaught TypeError: Cannot read property 'addEventListener' of null".
Will try the updated drag-drop now, thanks again.

Have just updated 2.3.1 and now I'm getting the same error message for both require() and script element methods:
TypeError: Cannot read property 'addEventListener' of null
at r (./node_modules/drag-drop/dragdrop.bundle.js:1:4489)
Thanks

@PimpShanti Glad you got this working!


Add label to created issue

Is it possible to add a label to the created issue using the manual-approval Github Action?
Currently, the created issues are showing up in our project Kanban view and I would like to filter them out by adding a label like hidden to the issue automatically when it is created.

I need the same feature


Allow running init SQL script for in-memory databases

Often, in-memory databases are used for unit testing, and therefore the database needs to already have a certain schema.
You can argue that I can run the SQL script to create the schema after loading the datasource and before running the tests. This case would require the code to know what kind of DataSource it is, and run the appropriate SQL schema creation scripts (i test my code against a few database types, H2, MySql and SQLite).
I would like a way to allow the JDBC connection string to also specify a resource sql to load, so that all the changes needed to run the test against a different database type is limited to the configuration.
An example will be H2's JDBC string:
jdbc:h2:mem:FooDB;MODE=MYSQL;IGNORECASE=TRUE;INIT=RUNSCRIPT FROM 'classpath:h2-database-schema-create.sql'

POC: https://github.com/xerial/sqlite-jdbc/pull/345

This sure would be nice to have! Sadly looks like it's been sitting idea for 3 years 😢

I am using Flyway too, works like a charm on in-memory database.
Is this still necessary in 2022 ?

Closing this as no feedback was received.


Trying to use Lean Copilot to develop the std library but hitting a build dependency cycle

@yangky11 @semorrison @tydeu I'd like to use Lean Copilot to develop std library proofs but the normal install instructions fail. Copilot depends on std, so std can't depend on copilot.
Should it be possible to use Lean Copilot to develop std? If so, what do you recommend?
Thanks.

I tried to hack this by renaming my local instance of std to be std4 but I couldn't get it working. That said, I don't know Lean's build system. If it's useful, here's what I tried:
-- lakefile.lean
-package std where
+package std4 where

-- I also added the moreLinkArgs and require LeanCopilot lines

# alias Std/ as Std4/ and create Std4.lean
ln -s Std Std4
cp Std.lean Std4.lean

# rename Std references to Std4 in both Std4.lean and all *.lean files within Std/
sed -i '' -e 's/Std/Std4/g' Std4.lean
pushd Std
for f in `find . -iname '*.lean'`; do
  sed -i '' -e 's/Std/Std4/g' $f
  sed -i '' -e 's/Std4in/Stdin/g' $f
done
popd

Running lake clean; lake build makes progress for awhile but eventually hits this:
...

[126/307] Building Std4.Lean.Meta.Simp
[127/307] Building Std4.Lean.Format
error: > LEAN_PATH=./.lake/packages/std/.lake/build/lib:./.lake/packages/aesop/.lake/build/lib:./.lake/packages/LeanCopilot/.lake/build/lib:./.lake/build/lib DYLD_LIBRARY_PATH=./.lake/build/lib /Users/atlas/.elan/toolchains/leanprover--lean4---v4.5.0-rc1/bin/lean -Dlinter.missingDocs=true ./././Std4/Tactic/CoeExt.lean -R ././. -o ./.lake/build/lib/Std4/Tactic/CoeExt.olean -i ./.lake/build/lib/Std4/Tactic/CoeExt.ilean -c ./.lake/build/ir/Std4/Tactic/CoeExt.c
error: stdout:
./././Std4/Tactic/CoeExt.lean:8:25: error: unknown namespace 'Std4'
./././Std4/Tactic/CoeExt.lean:31:10: error: unknown identifier 'elabTerm'
./././Std4/Tactic/CoeExt.lean:32:19: error: unknown identifier 'coerceToFunction?'
./././Std4/Tactic/CoeExt.lean:35:42: error: unknown identifier 'indentExpr'
./././Std4/Tactic/CoeExt.lean:39:10: error: unknown identifier 'elabTerm'
./././Std4/Tactic/CoeExt.lean:40:19: error: unknown identifier 'coerceToSort?'
./././Std4/Tactic/CoeExt.lean:43:38: error: unknown identifier 'indentExpr'
./././Std4/Tactic/CoeExt.lean:55:11: error: function expected at
  ToExpr
term has type
  ?m.2380
./././Std4/Tactic/CoeExt.lean:72:11: error: function expected at
  ToExpr
term has type
  ?m.4293
./././Std4/Tactic/CoeExt.lean:77:20: error: function expected at
  SimpleScopedEnvExtension
term has type
  ?m.4326
./././Std4/Tactic/CoeExt.lean:78:2: error: unknown identifier 'registerSimpleScopedEnvExtension'
./././Std4/Tactic/CoeExt.lean:77:20: error: function expected at
  SimpleScopedEnvExtension
term has type
  ?m.4370
./././Std4/Tactic/CoeExt.lean:76:0: error: initialization function<EMAIL_ADDRESS>must have type of the form `IO <type>`
./././Std4/Tactic/CoeExt.lean:84:32: error: function expected at
  CoreM
term has type
  ?m.4428
./././Std4/Tactic/CoeExt.lean:87:5: error: unknown namespace 'PrettyPrinter.Delaborator'
./././Std4/Tactic/CoeExt.lean:94:49: error: unknown identifier 'whenPPOption'
./././Std4/Tactic/CoeExt.lean:107:57: error: function expected at
  MetaM
term has type
  ?m.4492
./././Std4/Tactic/CoeExt.lean:121:71: error: function expected at
  MetaM
term has type
  ?m.4549
./././Std4/Tactic/CoeExt.lean:137:11: error: unknown identifier 'registerBuiltinAttribute'
error: external command `/Users/atlas/.elan/toolchains/leanprover--lean4---v4.5.0-rc1/bin/lean` exited with code 1
[127/307] Building Std4.Tactic.NoMatch
[128/307] Compiling Std.Linter.UnreachableTactic
error: > LEAN_PATH=./.lake/packages/std/.lake/build/lib:./.lake/packages/aesop/.lake/build/lib:./.lake/packages/LeanCopilot/.lake/build/lib:./.lake/build/lib DYLD_LIBRARY_PATH=./.lake/build/lib /Users/atlas/.elan/toolchains/leanprover--lean4---v4.5.0-rc1/bin/lean -Dlinter.missingDocs=true ./././Std4/Lean/Format.lean -R ././. -o ./.lake/build/lib/Std4/Lean/Format.olean -i ./.lake/build/lib/Std4/Lean/Format.ilean -c ./.lake/build/ir/Std4/Lean/Format.c
error: stdout:
./././Std4/Lean/Format.lean:18:33: error: unknown identifier 'prettyM'
error: external command `/Users/atlas/.elan/toolchains/leanprover--lean4---v4.5.0-rc1/bin/lean` exited with code 1

I'm not aware of a good solution.

Why does Lean copilot need to be built with the Lean project it's being used on?

It uses HashMap in Std and some tactics for displaying suggestions.

I see. That makes sense. The current status of Lean Copilot is more like a library instead of a standalone developer tool.

Fair enough - it is a research project after all 😉.
Do you know if making copilot a standard dev tool would run into any issues with how lake is designed? I.e. is it just a matter of engineering on Lean copilot, or is there a deeper issue with lake?
I've been curious about warnings that a lean project needs to be at the top level of a git repository - building and version control should not be coupled! - so I'm wondering if there are dragons lurking in the build system.

Regarding Lake, @tydeu is the expert.

@tenedor

I've been curious about warnings that a lean project needs to be at the top level of a git repository - building and version control should not be coupled! - so I'm wondering if there are dragons lurking in the build system.

There is no hard requirement that a Lean/Lake package be at the top-level of a Git repository (or in one at all). However, certain package management features do depend on Git/GitHub. Lake uses Git to download remote dependencies and Lake makes use of GitHub for cloud releases.

@tenedor, @tydeu, I think the real concern here is that we are missing lake install still, so that we can install developer tools and then use them without having to add them as a dependency to the project in which we want to use them.
@tydeu, is there an issue tracking lake install so we can point people to that as the blocker for issue like this one? I couldn't see one.

@semorrison thanks that sounds like the issue. Contributors to a shared project should be able to install their own personal developer tools without infecting the shared state of the project.
@tydeu thanks for the context on Lake.

@semorrison / others - do you have recommendations on how I can nonetheless try using Lean Copilot with the std library? My guess is that the best path forward is to make a new repo MyStdLib that depends on both std and lean copilot, and then use MyStdLib to develop incremental additions to std which I then port to std.
This will be limited to add-only changes, but my hunch is that's all Lean Copilot will be helpful for anyway.

@semorrison

@tydeu, is there an issue tracking lake install so we can point people to that as the blocker for issue like this one? I couldn't see one.

No, not yet. I don't think anyone needed it enough yet to make an issue.

🤷♀  Okay, I've made the issue: https://github.com/leanprover/lean4/issues/3423


Fix Farm LastAttemptedProof - Changed sort sign from "-" to "+"

The last attempted proof list is updating the rows from bottom. Should be the reverse order, like the others. Please double check the change if it works.
Thank you

The records of last attempted proof are saved at packags/api/src/services/Farmer.ts.
I think you don't need to sort every time the component gets rendered.
I'll close this PR as it is too old to be merged, but if you're still interested in this issue, please re-open this issue.
I'll add more advice.


Add type hints to params and returns

Basically just the title, add typing support for params and returns

closed in a549c3992d354b52461b2ea5b2b88d0d00774f7b


feat: add webhook validation

What this PR does / why we need it:
Validation webhooks will make sure that mandatory parameters are set before reconciliation so that users can catch errors much earlier.
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #55

unit tests
?       github.com/oracle/cluster-api-provider-oci      [no test files]
ok      github.com/oracle/cluster-api-provider-oci/api/v1beta1  0.301s  coverage: 7.5% of statements
?       github.com/oracle/cluster-api-provider-oci/cloud/config [no test files]
ok      github.com/oracle/cluster-api-provider-oci/cloud/ociutil        0.579s  coverage: 30.3% of statements
ok      github.com/oracle/cluster-api-provider-oci/cloud/scope  176.018s        coverage: 81.9% of statements
?       github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks    [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/compute       [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/identity      [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity        [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer   [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/vcn   [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn  [no test files]
ok      github.com/oracle/cluster-api-provider-oci/controllers  26.312s coverage: 70.3% of statements

e2e tests
Summarizing 2 Failures:

[Fail] Workload cluster creation [It] Cloud Provider OCI testing
/Users/jkratzat/projects/cluster-api-provider-oci-joekr/vendor/sigs.k8s.io/cluster-api/test/framework/machinedeployment_helpers.go:121

[Fail] Workload cluster creation [It] ClusterClass - with 1 control-plane nodes and 1 worker nodes
/Users/jkratzat/projects/cluster-api-provider-oci-joekr/vendor/sigs.k8s.io/cluster-api/test/framework/clusterctl/clusterctl_helpers.go:273

Ran 9 of 20 Specs in 14805.275 seconds
FAIL! -- 7 Passed | 2 Failed | 0 Pending | 11 Skipped
--- FAIL: TestE2E (14805.28s)
FAIL

updated tests after rebase and changes
?       github.com/oracle/cluster-api-provider-oci      [no test files]
ok      github.com/oracle/cluster-api-provider-oci/api/v1beta1  0.305s  coverage: 7.6% of statements
?       github.com/oracle/cluster-api-provider-oci/cloud/config [no test files]
ok      github.com/oracle/cluster-api-provider-oci/cloud/ociutil        0.602s  coverage: 30.3% of statements
ok      github.com/oracle/cluster-api-provider-oci/cloud/scope  176.026s        coverage: 81.9% of statements
?       github.com/oracle/cluster-api-provider-oci/cloud/scope/mocks    [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/compute       [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/compute/mock_compute  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/identity      [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/identity/mock_identity        [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer   [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/networkloadbalancer/mock_nlb  [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/vcn   [no test files]
?       github.com/oracle/cluster-api-provider-oci/cloud/services/vcn/mock_vcn  [no test files]
ok      github.com/oracle/cluster-api-provider-oci/controllers  26.240s coverage: 70.7% of statements

Summarizing 1 Failure:

[Fail] Workload cluster creation [It] Cloud Provider OCI testing [PRBlocking]
/home/ubuntu/projects/cluster-api-provider-oci/test/e2e/ccm_helpers.go:83

Ran 5 of 21 Specs in 1872.951 seconds
FAIL! -- 4 Passed | 1 Failed | 0 Pending | 16 Skipped

testing in SYD for CCM
• [SLOW TEST:1075.668 seconds]
Workload cluster creation
/home/ubuntu/projects/cluster-api-provider-oci/test/e2e/cluster_test.go:49
  Cloud Provider OCI testing [PRBlocking]
  /home/ubuntu/projects/cluster-api-provider-oci/test/e2e/cluster_test.go:201
------------------------------
STEP: Tearing down the management cluster

Ran 1 of 21 Specs in 1160.600 seconds
SUCCESS! -- 1 Passed | 0 Failed | 0 Pending | 20 Skipped


[wip] Report product and product version to telemetry

Description
This draft PR send a new type of payload app_integrations_change to Telemetry v2. This new payload allows use know which product/integration is using the Tracer.

Each of our "integrations" will need separate consideration for how the designation will make it into dd-trace-cpp.
Here are the ones that come to mind:

nginx-datadog we can do what we want, since we control the code. A TracerConfig field will work just fine.
envoy we also have programmatic control over, so we can use TracerConfig, but we have to think of how to handle
istio, which uses envoy via a special envoy build called istio/proxy, which then gets rolled into images and mentioned in kubernetes YAML configs by istio proper. Not sure how best to get the "istio-ness" into dd-trace-cpp, since Istio isn't handling the TracerConfig like envoy. Perhaps it's best to add an optional configuration parameter to Envoy's YAML, and have Istio setups default the value when Datadog tracing is mentioned. Tricky.
ingress-nginx, which previously used dd-opentracing-cpp but now is OpenTelemetry-over-Datadog-Agent-only, until I finish the "OpenTelemetry API" projects. If a customer is using the OpenTelemetry way, then we don't have to worry about "integration," because dd-trace-cpp is not involved. If a customer is using a version with dd-opentracing-cpp, then same thing. The question is how ingress-nginx will tell its OpenTelemetry nginx module that the Datadog implementation ought to designate itself as ingress-nginx :thinking: . That's a tough one.
Your Apache POC can use TracerConfig, no problem.
Kong doesn't use dd-trace-cpp.

Maybe an environment variable. Doesn't feel right, though.
Have a think about it.

Maybe an environment variable. Doesn't feel right, though.

Agree, it's a nice workaround but it does not feel appropriate to use an environment environment. It raises concerns about relying on a value that can be changed arbitrarily and depending on users to set it accurately.
Back to our integration challenges, the underlying issue is essentially about propagating the value from X to dd-trace-cpp. As a former colleague used to say, there are no problems we can't solve without another level of indirection.
istio integration
I had a quick look on the relationship between envoy and istio. I started my journey on a naive thought, at some point istio needs to inform envoy which tracer to use.
I stumbled upon istio/pilot/pkg/networking/core/v1alpha3/tracing.go, it can return a datadogConfig. This DatadogConfig is then used to set up our Tracer.
A potential solution might involve adding a field to datadog.proto and seting that field in istio code.
ingress-nginx
No idea 🤷♂ Further investigation is required.


Add memory and performance tests

Description of issue
Add tests to check the memory and performance by benchmarking these metrics and making sure future changes don't affect them

Performance tests are being developed in porting-assistant-dotnet-client which will cover this case. PA Client already has memory tests


Show Advanced Button Not working

Under Properties, for a string based property, when I select "Show Advanced", no menu opens up as it does in the tutorial. I tried this on Chrome and Firefox on mac book pro.

Thx, cpalm3. I experienced a similar issue and have noted this in Issue #49.


Default random agent Out of Bound Error

When I ran Randomagent for BuildMarines, I got this error from time to time
Exception in thread Renderer:
Traceback (most recent call last):
  File "/home/jay/miniconda2/lib/python2.7/threading.py", line 801, in __bootstrap_inner
    self.run()
  File "/home/jay/miniconda2/lib/python2.7/threading.py", line 754, in run
    self.__target(*self.__args, **self.__kwargs)
  File "/home/jay/miniconda2/lib/python2.7/site-packages/pysc2/lib/renderer_human.py", line 878, in render_thread
    self.render_obs(obs)
  File "/home/jay/miniconda2/lib/python2.7/site-packages/pysc2/lib/renderer_human.py", line 56, in _with_lock
    return func(*args, **kwargs)
  File "/home/jay/miniconda2/lib/python2.7/site-packages/pysc2/lib/stopwatch.py", line 197, in _stopwatch
    return func(*args, **kwargs)
  File "/home/jay/miniconda2/lib/python2.7/site-packages/pysc2/lib/renderer_human.py", line 894, in render_obs
    surf.draw(surf)
  File "/home/jay/miniconda2/lib/python2.7/site-packages/pysc2/lib/renderer_human.py", line 352, in <lambda>
    lambda surf: self.draw_feature_layer(surf, feature))
  File "/home/jay/miniconda2/lib/python2.7/site-packages/pysc2/lib/stopwatch.py", line 197, in _stopwatch
    return func(*args, **kwargs)
  File "/home/jay/miniconda2/lib/python2.7/site-packages/pysc2/lib/renderer_human.py", line 849, in draw_feature_layer
    surf.blit_np_array(feature.color(feature.unpack(self._obs.observation)))
  File "/home/jay/miniconda2/lib/python2.7/site-packages/pysc2/lib/stopwatch.py", line 197, in _stopwatch
    return func(*args, **kwargs)
  File "/home/jay/miniconda2/lib/python2.7/site-packages/pysc2/lib/features.py", line 94, in color
    return self.palette[plane]
IndexError: index 16 is out of bounds for axis 0 with size 16

Same error here.
Please fix it.

i think this issue is fixed already

I think b594ad7 already fixed this. Please reopen if you can show that a different plane that needs to be clipped.


Fix gradio UI initialization

Description

Fix gradio UI initialization
Logging w/o f-strings
Logging history lentgth

Type of change

[x] Refactor
[ ] New feature
[x] Bug fix
[ ] CVE fix
[ ] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library
[ ] Bump-up library or tool used for development (does not change the final image)
[ ] CI configuration change
[ ] Konflux configuration change

Codecov Report
Attention: Patch coverage is 87.50000% with 1 line in your changes missing coverage. Please review.

Project coverage is 94.91%. Comparing base (b6cc49b) to head (e9dddb1).
Report is 22 commits behind head on main.

Files with missing lines
Patch %
Lines

ols/src/ui/gradio_ui.py
87.50%
1 Missing :warning:

Additional details and impacted files

@@           Coverage Diff           @@
##             main    #1744   +/-   ##
=======================================
  Coverage   94.90%   94.91%
=======================================
  Files          60       60
  Lines        2689     2693    +4
=======================================
+ Hits         2552     2556    +4
  Misses        137      137

Files with missing lines
Coverage Δ

ols/src/ui/gradio_ui.py
97.95% <87.50%> (+0.04%)
:arrow_up:

/retest

/approve
/override "Red Hat Konflux / ols-enterprise-contract / lightspeed-service"

/lgtm


Reach consensus on transaction and enrollment set

The enrollments to be included in a block must first
be voted on by the consensus protocol.
Changed the Nominator class to reach consensus on
a structure which includes both transactions
and the enrollment set.
@AndrejMitrovic ref https://github.com/AndrejMitrovic/agora/commit/999e03196020621476f71c025e8f18e2f0bfbf0c
Relates to #565

core.exception.AssertError@source/agora/consensus/protocol/Nominator.d(410): Assertion failure
??:? _d_assertp [0x108d078c9]
/usr/local/opt/dmd/include/dlang/dmd/core/internal/array/equality.d:33 _ZN9Nominator17valueExternalizedEyRKN3xdr7xvectorIhLj4294967292EEE [0x1088f54fc]
??:? ZN7stellar14BallotProtocol16setConfirmCommitERKNS_9SCPBallotES3 [0x1089e79d8]
??:? _ZN7stellar14BallotProtocol20attemptConfirmCommitERKNS_12SCPStatementE [0x1089e746f]
??:? _ZN7stellar14BallotProtocol11advanceSlotERKNS_12SCPStatementE [0x1089def75]
??:? _ZN7stellar14BallotProtocol15processEnvelopeERKNS_11SCPEnvelopeEb [0x1089dd7bf]
??:? _ZN7stellar4Slot15processEnvelopeERKNS_11SCPEnvelopeEb [0x108a72e6e]
??:? _ZN7stellar14BallotProtocol25emitCurrentStateStatementEv [0x1089e04ba]
??:? _ZN7stellar14BallotProtocol17setPreparedAcceptERKNS_9SCPBallotE [0x1089e40c8]
??:? _ZN7stellar14BallotProtocol21attemptPreparedAcceptERKNS_12SCPStatementE [0x1089e35fe]
??:? _ZN7stellar14BallotProtocol11advanceSlotERKNS_12SCPStatementE [0x1089deec7]
??:? _ZN7stellar14BallotProtocol15processEnvelopeERKNS_11SCPEnvelopeEb [0x1089dd7bf]
??:? _ZN7stellar4Slot15processEnvelopeERKNS_11SCPEnvelopeEb [0x108a72e6e]
??:? _ZN7stellar14BallotProtocol25emitCurrentStateStatementEv [0x1089e04ba]
??:? ZN7stellar14BallotProtocol15setAcceptCommitERKNS_9SCPBallotES3 [0x1089e692d]
??:? _ZN7stellar14BallotProtocol19attemptAcceptCommitERKNS_12SCPStatementE [0x1089e619d]
??:? _ZN7stellar14BallotProtocol11advanceSlotERKNS_12SCPStatementE [0x1089def3b]
??:? _ZN7stellar14BallotProtocol15processEnvelopeERKNS_11SCPEnvelopeEb [0x1089dd7bf]
??:? _ZN7stellar4Slot15processEnvelopeERKNS_11SCPEnvelopeEb [0x108a72e6e]
??:? _ZN7stellar3SCP15receiveEnvelopeERKNS_11SCPEnvelopeE [0x108a5ab8c]
/usr/local/opt/dmd/include/dlang/dmd/core/internal/array/equality.d:33 @trusted bool agora.consensus.protocol.Nominator.Nominator.receiveEnvelope(scpd.types.Stellar_SCP.SCPEnvelope) [0x1088f51bf]
/usr/local/opt/dmd/include/dlang/dmd/core/internal/array/equality.d:33 @safe bool agora.node.Node.Node.receiveEnvelope(scpd.types.Stellar_SCP.SCPEnvelope) [0x10890d776]
/usr/local/opt/dmd/include/dlang/dmd/core/internal/array/equality.d:33 void geod24.LocalRest.RemoteAPI!(agora.test.Base.TestAPI).RemoteAPI.handleCommand(geod24.LocalRest.Command, agora.test.Base.TestAPI, geod24.LocalRest.FilterAPI) [0x108911998]
/usr/local/opt/dmd/include/dlang/dmd/core/internal/array/equality.d:33 void geod24.LocalRest.RemoteAPI!(agora.test.Base.TestAPI).RemoteAPI.spawned!(agora.test.Base.TestNode).spawned(geod24.concurrency.Tid, agora.common.Config.Config, shared(geod24.Registry.Registry)*).handle!(geod24.LocalRest.Command).handle(geod24.LocalRest.Command).__lambda2() [0x10891dc25]
submodules/localrest/source/geod24/concurrency.d:1021 void geod24.concurrency.FiberScheduler.create(void delegate()).wrap() [0x108b3b4b4]
??:? void core.thread.fiber.Fiber.run() [0x108d0e27d]
??:? fiber_entryPoint [0x108d0db23]
??:? 0x0 [0xffffffffffffffff]
Program exited with code -6
dub test  11.11s user 1.50s system 93% cpu 13.521 total

It would help if you caught the exception and printed it out, wouldn't it?
So replace scope (failure) assert(0); with a try/catch and print out the message. It will tell you what went wrong.

Exception: core.exception.AssertError@source/agora/consensus/protocol/Nominator.d(420): Transaction set empty

I was curious too.
It looks like either the transaction set is not properly set, or it's not properly serialized / deserialized.

Exception: core.exception.AssertError@source/agora/consensus/protocol/Nominator.d(420): Transaction set empty

I was curious too.
It looks like either the transaction set is not properly set, or it's not properly serialized / deserialized.

um..... I passed the ConsensusData serialized / serialized test.
I think SCP is doing something...

Yes it is strange, because the byte array passed to externalize is actually empty..

Yes it is strange, because the byte array passed to externalize is actually empty..

Yes, empty.

This is the issue:
+        this.nominate(slot_idx, data, ConsensusData.init);

The order of the arguments need to be swapped. The data argument goes last.
@TrustHenry I suggest we remove the prev parameter from the nominate function so this bug doesn't happen again.

This is the issue:
+        this.nominate(slot_idx, data, ConsensusData.init);

The order of the arguments need to be swapped. The data argument goes last.
@TrustHenry I suggest we remove the prev parameter from the nominate function so this bug doesn't happen again.

        Params:
            slot_idx = the index of the slot to nominate for
            prev = the data set of the previous slot
            next = the proposed data set for the provided slot index

    ***************************************************************************/

    private void nominate (ulong slot_idx, ConsensusData prev,
        ConsensusData next) @trusted

    // Submit a value to consider for slotIndex
    // previousValue is the value from slotIndex-1
    bool nominate(uint64_t slotIndex, ref const(Value) value,
                        ref const(Value) previousValue);

Really?

Something like this:
diff --git a/source/agora/consensus/protocol/Nominator.d b/source/agora/consensus/protocol/Nominator.d
index 694ff98..e584a36 100644
--- a/source/agora/consensus/protocol/Nominator.d
+++ b/source/agora/consensus/protocol/Nominator.d
@@ -163,7 +163,7 @@ extern(D):
         // note: we are not passing the previous tx set as we don't really
         // need it at this point (might later be necessary for chain upgrades)
         auto slot_idx = this.ledger.getBlockHeight() + 1;
-        this.nominate(slot_idx, ConsensusData.init, data);
+        this.nominate(slot_idx, data);
     }

     /***************************************************************************
@@ -244,17 +244,15 @@ extern(D):

         Params:
             slot_idx = the index of the slot to nominate for
-            prev = the data set of the previous slot
             next = the proposed data set for the provided slot index

     ***************************************************************************/

-    protected void nominate (ulong slot_idx, ConsensusData prev,
-        ConsensusData next) @trusted
+    protected void nominate (ulong slot_idx, ConsensusData next) @trusted
     {
         log.info("{}(): Proposing tx set for slot {}", __FUNCTION__, slot_idx);

-        auto prev_value = prev.serializeFull().toVec();
+        auto prev_value = ConsensusData.init.serializeFull().toVec();
         auto next_value = next.serializeFull().toVec();
         if (this.scp.nominate(slot_idx, next_value, prev_value))
         {

@Geod24 @AndrejMitrovic Ready for review

By the way, do you have sourcegraph installed @TrustHenry ?
Using it, you can see what path is covered and what is not. For example this is what I see:

The green number is the number of hits on a line (number of time the line is executed).
A red 0 means the code is never executed. We use coverage reports from both unittests and integration tests, so there is really no reason a line should not be covered (unless it's an assert(0) ;) ).
In case you missed it, we have instructions here


impl(docfx): skip duplicate deprecated sections

Namespaces can have multiple xrefsect marking them as deprecated. This skips all but the first such section.
Fixes #11614

This change is

PTAL


feat(io-stream): add getStream() method to access underlying stream

Signed-off-by: azjezz<EMAIL_ADDRESS>

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 2 (0.0%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.06%) to 99.938%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/Psl/File/Internal/AbstractHandleWrapper.php
0
2
0.0%

Totals

Change from base Build<PHONE_NUMBER>:
-0.06%

Covered Lines:
3209

Relevant Lines:
3211

💛  - Coveralls


WIP: Finalizing numerical linear algebra

@ajozefiak  Edit for grammar, layout, content, etc.  Ensure the code works (activating as the latest manifest/project in julia).


Add a new test test_csi_expansion_canceling()

longhorn/longhorn#978

As long as the PVC spec.size is expanded, we cannot shrink it anymore. Hence the expansion canceling cannot be triggered via PVC/CSI.
If users choose PVC to expand the volume then try to use Longhorn API to cancel the expansion, it would lead to the inconsistency between PVC and Longhorn volume.

Hence expansion canceling feature is mainly for the users using the Longhorn API to expand volumes. And we need to add a tip for the API on the UI page.

@shuo-wu How about one replica failure when expansion? The expansion should succeed, right? That's something we should test with CSI as well.

Yes. That's pretty similar to the 2nd test in this PR. Do we still need to retain the 2nd test after adding the CSI test you mentioned?

It's better to do it through the CSI if we only want to keep one case.