[Feature] Hidden/private tests

Checklist

[x] I tested all changes and all related features with different users (student, tutor, instructor, admin) on the test server https://artemistest.ase.in.tum.de.
[x] Server: I followed the coding and design guidelines.
[x] Server: I added multiple integration tests (Spring) related to the features (with a high test coverage)
[x] Server: I implemented the changes with a good performance and prevented too many database calls
[x] Server: I documented the Java code using JavaDoc style.
[x] Client: I followed the coding and design guidelines.
[x] Client: I added multiple integration tests (Jest) related to the features (with a high test coverage)
[x] Client: I documented the TypeScript code using JSDoc style.
[x] Client: I added multiple screenshots/screencasts of my UI changes
[x] Client: I translated all the newly inserted strings into German and English

Motivation and Context
Closes #2487.
Motivation described there.
Description
I implemented the solution as outlined in #2487 with Feedback and ProgrammingExerciseTestCase both receiving a visibility-Attribute.
This means that all Feedbacks received are stored and only filtered when queried depending on the individual user.
Additionally, as visibility for Feedbacks marked with after due date depends only on the Due Date of the exercise itself and no longer on Run Tests After Due Date it is always possible to select AfterDueDate as option for test cases.
To update the score after they become visible, now a updateAllResults is triggered for all student participations after the due date has passed.
This only recalculates the result string and score based on values already stored and does not require any Bamboo/Jenkins jobs.
Steps for Testing
There aren’t really specific steps as this affects a lot of the programming exercise grading workflow, but some things you should look out for:

This change should only affect programming exercises.
The only UI-Page that has changed is the programming exercise grading configuration page where the column After Due Date has been changed to Visibility.

Now AfterDueDate should always be selectable in the dropdown independent of the Run Tests After Due Date option for the exercise.

Test cases marked as AfterDueDate should

be invisible to students (e.g. in the Feedback list, but other possible places as well) before the due date has passed,
become visible to students after the due date has passed,
always be visible in the feedback list when teaching assistants/instructors look at a student’s participation in the participations view and show up for the statistics on the Configure Grading page in the column Passed % (if they are actually executed on the CI server),
be considered in the result string (x of y passed) only after the due date has passed.

Test cases marked as Never visible should

always be invisible to students,
be visible in the feedback list when teaching assistants/instructors look at a student’s solution in the participations view and when manually assessing a result,
only be considered in the result string (x of y passed) for the Template and Solution repos; never for student repositories.

When manually assessing a result

feedback for test cases marked as Never visible should be visible to the assessor.
students should not see the automatic feedback for a Never-testcase after a manual result has been created.

Test Coverage

Class
Instruction/Statement Coverage

domain/Result.java
95% (unchanged, all new code covered)

service/ProgrammingExerciseGradingService.java
95% (unchanged, all new code covered)

service/WebsocketMessagingService.java
75% (unchanged, all new code covered)

service/scheduled/ProgrammingExerciseScheduleService.java
74% → 85%

web/rest/ProgrammingExerciseParticipationResource.java
90% → 92%

web/rest/ResultResource.java
87% (unchanged, all new code covered)

programming-exercise-configure-grading.component.ts
88% (unchanged)

Screenshots

Click to expand!
Configure Grading Page (testMergeSort: Hidden, testBubbleSort: After Due Date), it is shown by the green indicator that a student successfully implemented those two tests:

Instructor View of the Solution Repository (hidden tests shown):

Student view before due date (hidden tests and tests after due date not shown):

Student view after due date (hidden tests not shown but tests after due date are visible):

Supersedes #2728

only change: this PR is opened from a feature-branch inside the repository, not from a fork
that should make it easier to run on the testing servers

@JohannesWeiss Thank you, that was an important bug (but with an easy fix)!
@airelawaleria Thank you! Now it should filter properly.
However, when the tutor/instructor is on that page while the Artemis server receives a new result they still are able to see all test feedbacks for that execution until they reload the page. The WebsocketMessagingService that informs the clients about new results uses a broadcast functionality to tell all admins, instructors, and tutors in the course about new student results. Therefore, the message can’t be filtered individually. I can see a few options on how to solve this:

Convert the broadcast into individual messages, then they can be filtered for instructors/tutors that are also students in that course.
Accept that it may become visible until a page reload.
Keep the previous version where it remains always visible to tutors and higher.

If there can be exercises where tutors should definitely not know about those test results before the due date, then variant 1 is the only option out of those three. Question also for other people looking at this: Are there such cases?
Otherwise, I personally slightly prefer variant 3 as it keeps the information displayed in the view consistent between refreshes (though, as the switch between 2 and 3 is a one-line change, I’d be fine with either one).

I personally don't like that the color of "Never" Tests is white as you can't see the square on the background anymore. Maybe make it dark gray, or something like that?

@SimonEntholzer Good idea: I now set the colour to transparent instead of white. That way they are invisible independent of row background colour. Therefore, only tests actually included in the score calculation get a clear visual indicator in the same colour as in the diagram to the right.

@b-fein this feature looks really nice and it would definitely interesting for us too!

Dropdown size does not change with window width. It would be nice if it can be fixed with a follow up PR.

@b-fein we now merged the PR after testing everything again. We found some additional code issue and would kindly ask you to fixe those in a follow-up PR. Thank you!

Thank you everyone for testing! This is a big feature needed for us in Passau to fully replace our old system by Artemis.
The follow-up PR is #3096.


feat(css_parser): introduce grit metavariable

Summary
Part of https://github.com/biomejs/biome/issues/3334
Grammar: https://github.com/getgrit/gritql/blob/main/resources/language-metavariables/tree-sitter-css/grammar.js
Test Plan
Add new tests

Great start!
I'm wondering if we can solve the problem in general. It seems all we need is to have a node that can be anywhere and not raise an invalid syntax error. We already have a bogus node type that can be anywhere in the tree; however, it produces a tree with errors.
What do you think about having something like a bogus type that doesn't break the syntax tree?

What do you think about having something like a bogus type that doesn't break the syntax tree?

Sounds good! However, I am wondering if it will meet the needs of the plugin side, as they would like to know the exact node type of metavariable. @arendjr
https://github.com/biomejs/biome/blob/f663e6b5d1389fe236a8f401456f8b976eb9d482/crates/biome_grit_patterns/src/grit_target_language.rs#L230-L231

However, I am wondering if it will meet the needs of the plugin side, as they would like to know the exact node type of metavariable.

We do need to be able to check for the node type indeed. But as long as it’s a distinct kind that should be covered.
I’m just not entirely sure how I should understand this sentence:

It seems all we need is to have a node that can be anywhere and not raise an invalid syntax error

How does that differ from the current metavariable implementation exactly? We can let it appear anywhere we want and it doesn’t raise an error. I guess the subtlety lies in how we make it appear where we want? I would be fine with an alternative approach to using specialized syntax (like the μ character), but I’m not sure I see a better way?

However, I am wondering if it will meet the needs of the plugin side, as they would like to know the exact node type of metavariable.

We do need to be able to check for the node type indeed. But as long as it’s a distinct kind that should be covered.
I’m just not entirely sure how I should understand this sentence:

It seems all we need is to have a node that can be anywhere and not raise an invalid syntax error

How does that differ from the current metavariable implementation exactly? We can let it appear anywhere we want and it doesn’t raise an error. I guess the subtlety lies in how we make it appear where we want? I would be fine with an alternative approach to using specialized syntax (like the μ character), but I’m not sure I see a better way?

I agree, but I have slight concerns that we would have to adjust the grammar in many places to include CssGritMetavariable because we want to have it almost anywhere in the syntax tree.
I'm trying to understand if it's possible to implement something similar to what we have for the bogus node.

I'm with @denbezrukov on this one. Considering the approach of the metavariables (grit is one, and we will have more too, and they will be sparse across languages), I believe we should strike for a more generic approach using known nodes, very much like the bogus nodes.
We've done this for other nodes, such as Any*, *List, and *Bogus. *Meta could be just one of them.

If I understand correctly, @denbezrukov and @ematipico  are proposing something like the following:
CssMetaValue = CssGritMetavar | AnotherQueryLanguageMetavar
CssMetaSelector = CssGritMetavar | AnotherQueryLanguageMetavar

AnyCssValue =
    ...
    CssMetaValue

AnyCssSelector =
    ...
    CssMetaSelector

Is that correct?

Yes, I think that’s the gist of it. And now I see what  @denbezrukov meant, I agree too. It would be best if we had a more generic way of handling these. Probably the solution indeed is that we should be able to specify in the .ungram where they might occur and then the codegen should pretty much take care of the test.

We can try to improve it in another PR:)


VLP-16 /apollo/sensor/velodyne16/PointCloud2/header Timestamp is not GPS Time

VLP-16 /apollo/sensor/velodyne16/PointCloud2/header Timestamp is not GPS Time
cause
[ WARN] [1534337139.532238124]: Can not find transform frame: velodyne16.<PHONE_NUMBER>.896429 Error info: Lookup would require extrapolation into the future.  Requested time<PHONE_NUMBER>.896429062 but the latest data is at time<PHONE_NUMBER>.200000048, when looking up transform from frame [velodyne16] to frame [map]. canTransform returned after 0.101808 timeout was 0.1
@all2one @mbinna @bigwhite @weidezhang @poutyface

Left is the /apollo/sensor/velodyne16/PointCloud2/header's Time,Right is novatel inspva time

Is the GPS connected to the VLP-16?

Yes, I have checked in the web

I also used the official velodyne driver, the lidar time is correct,same with inspva time

@snehagn @YangHan101 Thx dude,the screenshot is as follows

I really dont know,what could be wrong, the header time is from the packet time?

It seems your gps is working and sending the sync signal to the lidar properly. Have you brought up the GPS driver part of the code?

Any update in this @xinwf

We haven't met this problem any more.
You can do two following things:

Make sure the processing of IMU time is right. Once one of my colleagues treats the us as ms when dealing with IMU's time, it caused this problem.
Make sure the apollo is broadcast extrinsic all the time from velodyne16 to world frame.
Besides these two reasons, if the machine runs very slowly especially the disk has an very high I/O ratio, it will also cause this problem, but this is not the apollo's problem.

Good luck.

Closing this issue as it appears to be resolved. Feel free to reopen if you have additional questions. Thanks!


patch for logging improvement on issue https://github.com/google/iden…

…tity-toolkit-java-client/issues/15
issue https://github.com/google/identity-toolkit-java-client/issues/15

Thanks for the patch. Could you sign Contributor License Agreements https://developers.google.com/open-source/cla/individual so we can accept your pull request?

Thank you. I've just accepted the CLA.
Regards
On Fri, Jun 26, 2015 at 4:07 PM liujin-google<EMAIL_ADDRESS>wrote:

Thanks for the patch. Could you sign Contributor License Agreements
https://developers.google.com/open-source/cla/individual so we can accept
your pull request?
—
Reply to this email directly or view it on GitHub
https://github.com/google/identity-toolkit-java-client/pull/16#issuecomment-115840987
.


Add nonpip ci for arm

Adding a separate pipeline for running non pip tests for arm.

@nitins17 can you take a look at this PR? Currently, there are many tests not building and many tests failing, which we need to investigate. But does the setup look good to you?

Thanks so much for this! I have left my feedback above.

@elfringham can you please review the script for non-pip tests in file tensorflow/tools/ci_build/rel/ubuntu/cpu_arm64_nonpip.sh

@mseth10 That seems mostly OK. You will need a list of tests to exclude, as you do in the cpu_arm64_pip.sh. I would suggest that you move the current list out of cpu_arm64_pip.sh into a new shell script that can then be sourced by both cpu_arm64_pip.sh and cpu_arm64_nonpip.sh into an environment variable. There will be additional tests that fail on the non-pip runs so there should be a second list, in the same new shell script, that is in another environment variable that can be used only by the non-pip run. That should stop any need to duplicate information and keep the maintenance of the exclusion list as simple as possible.
Also the non-pip CI runs so far have failed due to lack of disk space, so that will need to be resolved.

Addressed @elfringham 's comments. @nitins17 can you take another look?

@nitins17 looks like it's missing CLA.. I checked and mine is present, looks like it's missing yours.
Also, after this PR is merged we need to enable more runners to share load. Do you have access to this page? https://github.com/tensorflow/tensorflow/settings/actions/runners/new?arch=arm64&os=linux


bug: signTypedDataAsync TypeError: struct is not iterable

Is there an existing issue for this?

[X] I have searched the existing issues

Package Version
1.0.5
Current Behavior
Getting error TypeError: struct is not iterable when calling signTypedDataAsync
Expected Behavior
Has been working fine with older versions of wagmi / signTypedDataAsync (i.e. when message was value and primaryType wasn't needed). The typeddata i am passing in is being generated through the Lens API and there isn't any errors with this data generated.
Steps To Reproduce
const typedData: any = result.data.createPostTypedData.typedData;
    const signature = await signTypedDataAsync({
      domain: omit(typedData?.domain, ["__typename"]),
      types: omit(typedData?.types, ["__typename"]),
      primaryType: "Mail",
      message: omit(typedData?.value, ["__typename"]),
    });

here is the typed data stringified so it's pasteable here:
{"types":{"PostWithSig":[{"name":"profileId","type":"uint256","__typename":"EIP712TypedDataField"},{"name":"contentURI","type":"string","__typename":"EIP712TypedDataField"},{"name":"collectModule","type":"address","__typename":"EIP712TypedDataField"},{"name":"collectModuleInitData","type":"bytes","__typename":"EIP712TypedDataField"},{"name":"referenceModule","type":"address","__typename":"EIP712TypedDataField"},{"name":"referenceModuleInitData","type":"bytes","__typename":"EIP712TypedDataField"},{"name":"nonce","type":"uint256","__typename":"EIP712TypedDataField"},{"name":"deadline","type":"uint256","__typename":"EIP712TypedDataField"}],"__typename":"CreatePostEIP712TypedDataTypes"},"domain":{"name":"Lens Protocol Profiles","chainId":80001,"version":"1","verifyingContract":"0x60Ae865ee4C725cd04353b5AAb364553f56ceF82","__typename":"EIP712TypedDataDomain"},"value":{"nonce":19,"deadline":1686306946,"profileId":"0x6346","contentURI":"ipfs://QmQh3j8fYUG3ypFKRtfdAuRbChT2oRL3g8CTZpbw3vpv9y","collectModule":"0x99d6C3EaBf05435E851C067d2c3222716f7fCFe5","collectModuleInitData":"0x00000000000000000000000000000000000000000000000000000000000000200000000000000000000000000000000000000000000000008ac7230489e80000000000000000000000000000000000000000000000000000000000000000001e0000000000000000000000009c3c9283d3e44854697cd22d3faa240cfb03288900000000000000000000000000000000000000000000000000000000000003e80000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000e00000000000000000000000000000000000000000000000000000000000000002000000000000000000000000fa3fea500eedaa120f7eec2e4309fe094f854e6100000000000000000000000000000000000000000000000000000000000003e8000000000000000000000000be20d3f61f6995996a5b8dd58b036ada7cf309450000000000000000000000000000000000000000000000000000000000002328","referenceModule":"0x0000000000000000000000000000000000000000","referenceModuleInitData":"0x","__typename":"CreatePostEIP712TypedDataValue"},"__typename":"CreatePostEIP712TypedData"}
Link to Minimal Reproducible Example (StackBlitz, CodeSandbox, GitHub repo etc.)
No response
Anything else?
No response

I moved this issue to the viem repo already! 😊
https://github.com/wagmi-dev/viem/issues/681

oh sorry didnt realise, thought i was going crazy and hallucinating posting it lol 😅


[BUG] - Date / Calender components not updating correctly with locale

NextUI Version
2.4.0
Describe the bug
When updating the locale to use an international calendar, the date and calendar components don't update completely, if at all. This may be related to Next.js, because the CodeSandbox environment for this example seems to work fine, and that uses standard React.
The calendar seems to partially update, this is observable in the stackblitz link below.
Your Example Website or App
https://stackblitz.com/edit/stackblitz-starters-caucmz?file=app%2Fpage.tsx
Steps to Reproduce the Bug or Issue

Open the stackblitz link and wait for the page to compile and load.
Observe that the date picker has not properly updated to use the international calendar.

Expected behavior
Date and calendar components should be updating completely to use the specified locale.
Screenshots or Videos
No response
Operating System Version
Windows 11, developing in WSL Ubuntu 22.04 LTS
Browser
Chrome

Able to reproduce in next / vite app.

Can I work on this issue? :)

@juank1809 assigned. feel free to contact us in Discord if you need any help.

@juank1809 any updates? if not, I'd like to take over it since I'm working on similar issue.

Hi! I have been trying to resolve this issue for weeks but could not accomplish it. I'm sorry. Feel free to take over :) @wingkwong

`'use client';
import { DatePicker } from '@nextui-org/date-picker';
import { DateValue, parseAbsoluteToLocal } from '@internationalized/date';
import { I18nProvider } from '@react-aria/i18n';
import { useState } from 'react';
export default function App() {
const currentDate = new Date(); // Current date and time
let [date, setDate] = useState(
parseAbsoluteToLocal(currentDate.toISOString())
);
return (

);
}`
used the Date object and it's working fine as of now idk what was the issue about since the string itself was passed how can it show the current time?????

is this issue already solved?

@sohan01fw if it is still open and no linked PR, then no

Having the same issue, I18nProvider doesn't change anything for me.

@bebbs-dmt and for those who are having this issue, please check the version of @react-aria/i18n that you are using. NextUI is using a fixed version 3.11.1. If you are using other version, it may cause this issue. From the OP example, you may simply change as follows in your package.json.
-"@react-aria/i18n": "^3.11.1",
+"@react-aria/i18n": "3.11.1",

Here's the result. You may need to remove node_modules before reinstalling. I'll update the docs accordingly.


Basic Authentication Support

Move configuration in its own class in order to reduce the verbosity of index.php
Added authentication mechanism using HTTP auth.
Maybe I should also move the configuration checks (ini and extension) to the new  class ?

It's simple, it works... I like it :grinning:
Who knew it was that easy :man_shrugging:
For single-user environments this is certainly the easiest solution. Maybe in the future we can extend on it if the need arises (matter of time).
Splitting the configuration part into a separate class is also a good idea. index.php was getting to the point of being hard to read and comprehend. Maybe we can split off some more of the features into separate files in the future.

Modified to take your comments in account.

Awesome, thanks!
I suppose this PR can be merged then...


[21.05] Hardened kernels backports

Motivation for this change
Backports missing from 21.05
Fix #138203
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Can you maybe fold #138162 into this? Or maybe we should just merge that and then this.

With #138162 merged, this needs a rebase, apparently.


Small changes

@alokmenghrajani @mcpherrinm @sqshh
Some small changes:

Use TLSv1.2 as default now that we have TLSv1.2 support on Travis-CI
Update some flag descriptions to be more accurate (e.g. mention UNIX sockets)
Upgrade to new kingpin version, provides bash/zsh completion support

To get completion in your shell, e.g. zsh:
eval "$(ghostunnel --completion-script-zsh)"

:+1::shipit:
Not sure about one terminology change, but good either way.

lgtm


cannot hear the vehicles

it was working fine a while ago but there aren't any acceleration sounds or engine sounds anymore. music and sounds settings are default. when driving the automobile, it just sounds like really fast in game walking

nevermind got it


(maint) Refactor handle-request for reuse

This change doesn't have any value for this project on its own, but it
is necessary for downstream consumers (like PE) which will consume this
code directly.

Looks like the Travis failure was due to a transient connection error, so I've restarted it.

:+1:

:+1:


Add contributors guide to the website

Source https://docs.google.com/document/d/1pWmEEY-1-WuwBPNy5tDAxVJYQ9Een4hZJM06tQZg8X4/edit?disco=AAAABQ0U5J8&ts=59dba09b

This guide would describe various ways one can contribute to the BIDS ecosystem and how to best do it.

Can I contribute in this? @chrisfilo

Sorry this has already been fixed by #17


Native type Timestampz is not supported for postgresql connector.

Bug description
When defining timestampz type column in Postgres, such bug being occured:
Native type Timestampz is not supported for postgresql connector.

I found same issue on here repo (https://github.com/prisma/prisma/issues/2417), and the issue says that such bug has been fixed.
By the way, the bug is still occuring in my case \o/.
How to reproduce
I've prepared reproducable repo.
https://github.com/samchon/prisma-bug-report-postgres-timestampz
You can reproduce it just by typing below commands:
git clone https://github.com/samchon/prisma-bug-report-postgres-timestampz
cd prisma-bug-report-postgres-timestampz

npm install
npm run build:schema

Also, you can preview the bug message by Github Actions:
https://github.com/samchon/prisma-bug-report-postgres-timestampz/actions/runs/5504205801/jobs/10030183711#step:5:36
Expected behavior
Hope the bug to be fixed
Prisma information
You can see the prisma schema file from below link:

https://github.com/samchon/prisma-bug-report-postgres-timestampz/blob/master/src/schema.prisma

For reference, src/schema.prisma file has lots of comments (///). It's just my style that describing each tables and columns into the prisma schema file. Also, there're some comment tags like @format uuid. It's just for validation of input data before data archiving through typia, not for prisma. Therefore, don't mind about those comments please.
Also, I tried to erase those all comments, but same bug still occurs.
Environment & setup

OS: Windows 11
Database: Postgres
Node.js version: v16.20.0

Prisma Version
prisma                  : 4.16.2
@prisma/client          : 4.16.2
Current platform        : windows
Query Engine (Node-API) : libquery-engine 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81 (at<EMAIL_ADDRESS>Migration Engine        : migration-engine-cli 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81 (at<EMAIL_ADDRESS>Format Wasm             : @prisma/prisma-fmt-wasm 4.16.1-1.4bc8b6e1b66cb932731fb1bdbbc550d1e010de81
Default Engines Hash    : 4bc8b6e1b66cb932731fb1bdbbc550d1e010de81
Studio                  : 0.484.0

Oops, it's just my mistake.

Mistake: @db.Timestampz
Must be: @db.Timestamptz


terracotta 3.3.0 / toolkit 1.0.0 migration

Sergio hello;

per terracotta support answers:
http://forums.terracotta.org/forums/posts/list/3979.page

there is no other way but toward terracotta 3.3.0 / toolkit 1.0.0 migration;

can you please relate if you have a date in mind when will you migrate
terrastore to up to that?

thank you;

Andrei

Original issue reported on code.google.com by Andrei.Pozolotin on 27 Jul 2010 at 3:39

No worries: just let me know if you run into any problems :)

Original comment by<EMAIL_ADDRESS>on 27 Jul 2010 at 2:44

Andrei,

I'm closing this issue because there seem to be no problems.

Original comment by<EMAIL_ADDRESS>on 30 Jul 2010 at 8:19

Changed state: Invalid

ups... I did not take a look on 0.6.0 yet; let me do this now;

Original comment by Andrei.Pozolotin on 27 Jul 2010 at 11:48

Hi Andrei,

Terrastore 0.6.0 is already based on Terracorra 3.3.0 and its toolkit: it's
just still using bytecode instrumentation (based on toolkit classes) rather
than explicit toolkit APIs.
Anyways, this is absolutely transparent for Terrastore users: they don't have
to deal with anything related to Terracotta: they just have to talk to
Terrastore via HTTP.

So what are you trying to accomplish? Are you experiencing any errors?

Original comment by<EMAIL_ADDRESS>on 27 Jul 2010 at 5:53


Not getting output for realtime using webcam

Can anyone please tell me which all options to use to get output using Webcam.
command is : python3 elg_demo.py --help
Mentioned options are:
Demonstration of landmarks localization.
optional arguments:
-h, --help            show this help message and exit
-v {debug,info,warning,error,critical}
logging level
--from_video FROM_VIDEO
Use this video path instead of webcam
--record_video RECORD_VIDEO
Output path of video of demonstration.
--fullscreen
--headless
--fps FPS             Desired sampling rate of webcam
--camera_id CAMERA_ID
ID of webcam to use
Thanks in advance.

I got to know how to give options.
i.e  --camera_id -1
it will work.


Rumble Support not working

Hi,
I'm using a n64 controller wired, which works in Windows 11 fine using the Initial release, but when I flash the Rumble Support release it still shows in Windows but there is no input.

Closing as this is a duplicate of #11


CommitStatsCommand: Redesign

Two of these commits were already in https://github.com/SerenityOS/discord-bot/pull/710, please remove them from this PR?

Two of these commits were already in #710, please remove them from this PR?

Yeah, had to rebase upon master again. Fixed 👍


Canonicalization Error

Hi,
I gave the following link as an input and crawler4j's "URLCanonicalizer.getCanonicalURL()" failed to cannonicalize it.
The link is:
http://dx.doi.org/10.1002/(SICI)1098-2353(2000)13:2<94::AID-CA4>3.0.CO;2-O
Firefox seems to handle it just fine, it canonicalizes it to:
http://dx.doi.org/10.1002/(SICI)1098-2353(2000)13:2<94::AID-CA4>3.0.CO;2-O
and after redirects we reach our final destination:
https://onlinelibrary.wiley.com/doi/abs/10.1002/(SICI)1098-2353(2000)13%3A2<94%3A%3AAID-CA4>3.0.CO%3B2-O

Hi, I just found a new bug.
The url < https://academic.microsoft.com/#/detail/2084896083 > gets broken and becomes < https://academic.microsoft.com/ >.


Add Sparkle to auto-update

Seems like Sparkle 1 doesn't support sandboxed app.
Need to

Switch to Sparkle 2.0 beta
Turn off sandbox
Downloading from a website instead of auto-update https://sparkle-project.org/documentation/publishing/#publishing-an-update

Due to incorrect setting for 0.1.3, we can't get the next version auto-updated either way. 👎
Should use integer for CFBundleVersion.


Kotlin rewrite

Idfk how that works :trollface: sorry

i don't really want the share button replaced, the current position of the copy message link option is already muscle memory

Aw

Well, settings time then ig

Idk if when i have time tho. I'll tell you if i do

that is done and cool

you need to fix some of the package names

also keep the old plugin description and fix the version number

and the link icon should be ic_diag_link_24dp

did do


Placeholder on input file?

Is it possible to define a placeholder for the input file?

For the custom input file, you can use the _input option, e.g.:
echo $this->Form->file('fieldname', [
    '_input' => [
        'placeholder' => 'My placeholder'
    ]
];

There are two special options _input and _button  that can be used to customize the input and the button.
For the standard file input, you will have to check the CakePHP documentation, but I don't think it is a supported HTML feature.

Great, thank's a lot
On sáb., 2 sept. 2017 18:50 Mikaël Capelle<EMAIL_ADDRESS>wrote:

For the custom input file, you can use the _input option, e.g.:
echo $this->Form->file('fieldname', [    '_input' => [        'placeholder' => 'My placeholder'    ]];
There are two special options _input and _button that can be used to
customize the input and the button.
For the standard file input, you will have to check the CakePHP
documentation, but I don't think it is a supported HTML feature.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/Holt59/cakephp3-bootstrap-helpers/issues/137#issuecomment-326755907,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIk1W1Rc3xyneK7mlObdmTH5BueMfsQAks5seYdQgaJpZM4PK8Wn
.


Global search not search by subject

When I try search articles in Global search field, nothing found (by subject).
Also with simple numeric field.
To Reproduce
Seems as Global search by article subject broken in 3.8.x
When i put text string from articles body - search work.
But when I use any string from subject - nothing found
Screenshots
Add screenshots to help explain your problem, if possible.
Please complete the following information:

Vienna version 3.8.1 :d62d4a53: (7830)
OS version: 12.5.1 (21G83) Apple Silicon M1

That was work in old versions (before 3.8).

I cannot reproduce this. Can you provide an example feed and search term?

https://user-images.githubusercontent.com/217520/185752068-31a2d8fb-e96f-43c2-8d8a-d52e64a66fc1.mp4

In screencast feed with saved auth.
I did already Reindex.

What I can do to draw attention to the problem?
Issue still actual, but I not know what I can do for you can reproduce.

I just added any random feed: https://www.liga.net/tech/all/rss.xml
And trying to find any article from this feed (i.e. iPhone 14) and still not found anything.

I just added any random feed: https://www.liga.net/tech/all/rss.xml
And trying to find any article from this feed (i.e. iPhone 14) and still not found anything.

I could not reproduce the problem either.
I suspect your database is somewhat corrupted.

I just added any random feed: https://www.liga.net/tech/all/rss.xml
And trying to find any article from this feed (i.e. iPhone 14) and still not found anything.

I could not reproduce the problem either. I suspect your database is somewhat corrupted.

ok, and how I can restore/recreate database?
As I said before - I was do Reindex Database - it's not help.

Hi,
This can be done in Terminal, using the sqlite3 command.
I'll do a personal test before suggesting some commands.


Navigation Issue on Download page

when on download page, navigation links to zuko, documentation and contact do not work

Fixed


Remove the preview banner

This resolves #83 by removing the preview banner

Docs Build status updates of commit 4d8c880:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/.template.md
:white_check_mark:Succeeded

docs/maui/alerts/index.md
:white_check_mark:Succeeded
View

docs/maui/alerts/snackbar.md
:white_check_mark:Succeeded
View

docs/maui/alerts/toast.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/characters-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/email-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/event-to-command-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/index.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/masked-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/numeric-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/progressbar-animation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/required-string-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/set-focus-when-entry-completed-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/text-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/uri-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/user-stopped-typing-behavior.md
:white_check_mark:Succeeded
View

docs/maui/converters/bool-to-object-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/byte-array-to-image-source-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-black-or-white-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-alpha-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-blue-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-green-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-red-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-cmyk-string-converter.md
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

PRMerger Results

Issue
Description

Deleted File(s)
This PR deletes Markdown or YAML files owned by another author, or json file(s). The pull request must contain a comment from the pull request author confirming that all the file deletions are intentional before the pull request can be merged.

Changed Files
This PR contains more than 10 changed files.

File Change Percent
This PR contains file(s) with more than 20% file change.

Index File
This PR contains a change to the index file.

Just a reminder for the obvious: make sure to include the ones that were just merged today!

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

File
Status
Preview URL
Details

docs/maui/markup/converters/func-multi-converter.md
:x:Error

Details

docs/maui/converters/math-expression-converter.md
:x:Error

Details

docs/maui/converters/multi-math-expression-converter.md
:x:Error

Details

docs/maui/markup/converters/func-converter.md
:x:Error

Details

docs/maui/converters/variable-multi-value-converter.md
:x:Error

Details

docs/maui/behaviors/multi-validation-behavior.md
:x:Error

Details

docs/maui/markup/converters/func-multi-converter.md

Line 10, Column 1: [Error: include-not-found] Invalid include link: '../../includes/preview-note.md'.

docs/maui/converters/math-expression-converter.md

Line 10, Column 1: [Error: include-not-found] Invalid include link: '../includes/preview-note.md'.

docs/maui/converters/multi-math-expression-converter.md

Line 10, Column 1: [Error: include-not-found] Invalid include link: '../includes/preview-note.md'.

docs/maui/markup/converters/func-converter.md

Line 10, Column 1: [Error: include-not-found] Invalid include link: '../../includes/preview-note.md'.

docs/maui/converters/variable-multi-value-converter.md

Line 10, Column 1: [Error: include-not-found] Invalid include link: '../includes/preview-note.md'.

docs/maui/behaviors/multi-validation-behavior.md

Line 10, Column 1: [Error: include-not-found] Invalid include link: '../includes/preview-note.md'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 5d0cb81:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/.template.md
:white_check_mark:Succeeded

docs/maui/alerts/index.md
:white_check_mark:Succeeded
View

docs/maui/alerts/snackbar.md
:white_check_mark:Succeeded
View

docs/maui/alerts/toast.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/characters-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/email-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/event-to-command-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/index.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/masked-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/multi-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/numeric-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/progressbar-animation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/required-string-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/set-focus-when-entry-completed-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/text-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/uri-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/user-stopped-typing-behavior.md
:white_check_mark:Succeeded
View

docs/maui/converters/bool-to-object-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/byte-array-to-image-source-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-black-or-white-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-alpha-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-blue-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-green-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-red-converter.md
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Just a reminder for the obvious: make sure to include the ones that were just merged today!

Thanks @jfversluis! I have removed them so this PR is potentially good to go. I guess we just need to wait until we merge and ship the GA packages?

Docs Build status updates of commit 8d928e2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/.template.md
:white_check_mark:Succeeded

docs/maui/alerts/index.md
:white_check_mark:Succeeded
View

docs/maui/alerts/snackbar.md
:white_check_mark:Succeeded
View

docs/maui/alerts/toast.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/characters-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/email-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/event-to-command-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/index.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/masked-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/multi-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/numeric-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/progressbar-animation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/required-string-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/set-focus-when-entry-completed-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/text-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/uri-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/user-stopped-typing-behavior.md
:white_check_mark:Succeeded
View

docs/maui/converters/bool-to-object-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/byte-array-to-image-source-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-black-or-white-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-alpha-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-blue-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-green-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-red-converter.md
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

PRMerger Results

Issue
Description

Deleted File(s)
This PR deletes Markdown or YAML files owned by another author, or json file(s). The pull request must contain a comment from the pull request author confirming that all the file deletions are intentional before the pull request can be merged.

Changed Files
This PR contains more than 10 changed files.

File Change Percent
This PR contains file(s) with more than 20% file change.

Index File
This PR contains a change to the index file.

Docs Build status updates of commit 4ee3036:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/maui/.template.md
:white_check_mark:Succeeded

docs/maui/alerts/index.md
:white_check_mark:Succeeded
View

docs/maui/alerts/snackbar.md
:white_check_mark:Succeeded
View

docs/maui/alerts/toast.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/characters-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/email-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/event-to-command-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/index.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/masked-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/maximum-length-reached-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/multi-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/numeric-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/progressbar-animation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/required-string-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/set-focus-when-entry-completed-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/text-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/uri-validation-behavior.md
:white_check_mark:Succeeded
View

docs/maui/behaviors/user-stopped-typing-behavior.md
:white_check_mark:Succeeded
View

docs/maui/converters/bool-to-object-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/byte-array-to-image-source-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-black-or-white-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-alpha-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-blue-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-green-converter.md
:white_check_mark:Succeeded
View

docs/maui/converters/color-to-byte-red-converter.md
:white_check_mark:Succeeded
View

This comment lists only the first 25 files in the pull request.
For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


Release v3.0.0

Big shout out @cleitonmarx for his work on this release.
I am far too excited to write about all these recent changes in v2 and v3.
This PR should NOT be merged with squash commit as we want to preserve the history.

Coverage remained the same at 100.0% when pulling fc4279c9eead1a736f56eb361be8d61d34502d8b on v3-changelogfix- into ba42ddae458c0def2bc25a414ff03a6cc449752d on master.


Soul Sacrifice™ Delta [PCSA00152]

App summary

App name: Soul Sacrifice™ Delta
App serial: PCSA00152
App version: 1.00

Vita3K summary

Version: v0.1.6
Build number: 3009
Commit hash: https://github.com/vita3k/vita3k/commit/[commit]
CPU backend:  Dynarmic
GPU backend:  OpenGL

Test environment summary

Tested by: theheromans
OS: Windows 10
CPU: Intel(R) Core(TM) i5-1035G1 CPU @ 1.00GHz   1.19 GHz
GPU: Intel UHD Graphics
RAM: 16 GB

Issues
<Plays, but has a large yellow patch on screen that will not go away.>
Screenshots

Log
Recommended labels

In Game-

repeat issue, check to https://github.com/Vita3K/compatibility/issues/523


Streamlining line number substitutions

Mlog uses line numbers to specify jump destinations, so it's important to get line numbers right, and it's difficult to alter compiled code (e.g., in an optimization pass) without taking great care to avoid messing up jump destinations.  Currently Pyndustric handles this by carefully building the program from beginning to end, with a sort of piecemeal substitution of line-numbers into forward-looking jump statements, once their destinations' line numbers become fixed.
It would be better to have a uniform mechanism for performing line-number substitutions, and probably also to delay making such substitutions until all line numbers have been finalized.  This will make handling of line-numbers much less piecemeal, aid in compiling label() and jump_to() function-calls, and make it much easier for us to implement things like optimization passes that end up changing line-numbers.
Here's the solution I'm currently leaning towards:
Create a new Instruction class, used to store a single mlog instruction.  These will be what are listed in the compiler's ._ins attribute.  Such instructions are currently stored as strings, and some string methods are used on them, so Instruction could be made a subclass of str to preserve those uses.  The main new features that these would have is that they will eventually be assigned a .linenumber attribute indicating what line in the final code an instruction will have, and a .no_op attribute indicating whether this instruction should end up being included in the compiled code.  (This will allow us to put no-op placeholders like jump destination labels in the list of instructions, to mark a location in the code that should remain stable, even if the flanking instructions end up being re-written in an optimization pass.
Create a new Label class, used to store information about a potential jump destination.  Some uses of Labels will be prettier if this is also made to be an str subclass with each label behaving like the string "{labelname}".  The constructor for new Labels will ensure that each label has a unique .name, like "endif_27".  Each label will have a .destination, indicating the destination instruction (usually a no-op placeholder) that that label will be used to jump to.  Instructions that should jump to that destination will initially contain {labelname} but this will eventually be replaced with the line number of that destination, once line numbers are finalized.
Once all optimization passes are through, assign each Instruction a .linenumber corresponding to its position in the finalized list of instructions (not counting no-op instructions).  Then create a label_to_linenumber dictionary mapping each Label's .name to the .linenumber of its .destination.  Once the near-final code is produced by concatenating the (op) instructions together into a single string, all the finalized line numbers can then be substituted into that string at once by using this dictionary as the mapping for Python's str.format().

It would be better to have a uniform mechanism for performing line-number substitutions

Yes, I tried overengineering this solution by using some "instruction" class with jumps that could have "marks" (current's '{}' formatting) that would be filled up later or able to reference other "instructions". But I gave up because I wasn't much in the mood and wasn't necessary.
This approach seems similar to what you describe of instructions/labels.
This is how I see it:

We have that Instruction (naming can change, whether it's a str or not doesn't matter).
Jumps are a special subclass with a "jump location" which is another instruction.
After compilation ends we construct a map {instruction: lineno} and fix-up all those jump locations.

Hmm… but this does break with optimization passes because the instruction reference is lost. So we introduce the label you suggest:

We have that Instruction.
Jumps have a "jump location" which is a label. Labels are special Instruction that don't increment the line number, and are not emitted into mlog.
After compilation ends we construct a map {label: lineno} and fix-up all those jump locations.

Sounds good to me. This will require a few iterations over the entire program, but it's fine because they can be 1000 mlog instructions at most so at worst we'll need 1000 to create the lineno map and another 1000 to fix up the jump locations (map lookup is amortized O(1)).

It would be better to have a uniform mechanism for performing line-number substitutions

Yes, I tried overengineering this solution by using some "instruction" class with jumps that could have "marks" (current's '{}' formatting) that would be filled up later or able to reference other "instructions". But I gave up because I wasn't much in the mood and wasn't necessary.
This approach seems similar to what you describe of instructions/labels.
This is how I see it:

We have that Instruction (naming can change, whether it's a str or not doesn't matter).
Jumps are a special subclass with a "jump location" which is another instruction.
After compilation ends we construct a map {instruction: lineno} and fix-up all those jump locations.

Hmm… but this does break with optimization passes because the instruction reference is lost. So we introduce the label you suggest:

We have that Instruction.
Jumps have a "jump location" which is a label. Labels are special Instruction that don't increment the line number, and are not emitted into mlog.
After compilation ends we construct a map {label: lineno} and fix-up all those jump locations.

Sounds good to me. This will require a few iterations over the entire program, but it's fine because they can be 1000 mlog instructions at most so at worst we'll need 1000 to create the lineno map and another 1000 to fix up the jump locations (map lookup is amortized O(1)).

Yeah, I wouldn't worry about Big-O measures on data-sets this small, unless we end up doing some really weird combinatorics.
Anyway, I've already implemented this along the lines I suggested above, and it works great.  I also used this to rewrite and streamline all the code for conditional jumps in if and while statements.  Using labels for this makes our code for handling these shorter, more uniform, and more intuitive than your more ad hoc substitutions were.  Now while can use comparative tests just like if can, both of these will negate the test to reduce instruction-count, and logical and, logical or, and their negations can all be used, all evaluated greedily as Python coders would expect.
I haven't tried to mess around with black yet, and doing so isn't a high priority for me (since the main impact on me will just be that it reformats my code in a way that is initially unfamiliar to me!) so it may be that you won't be interested in having me share these changes.  But if you are interested, I'd be happy to share them, as I think you'll probably find them to be a strict improvement over what you had, aside perhaps from quibbles with my formatting and/or profuse commentary.

Yeah, I wouldn't worry about Big-O measures on data-sets this small, unless we end up doing some really weird combinatorics.
Anyway, I've already implemented this along the lines I suggested above, and it works great.  I also used this to rewrite and streamline all the code for conditional jumps in if and while statements.  Using labels for this makes our code for handling these shorter, more uniform, and more intuitive than your more ad hoc substitutions were.  Now while can use comparative tests just like if can, both of these will negate the test to reduce instruction-count, and logical and, logical or, and their negations can all be used, all evaluated greedily as Python coders would expect.
I haven't tried to mess around with black yet, and doing so isn't a high priority for me (since the main impact on me will just be that it reformats my code in a way that is initially unfamiliar to me!) so it may be that you won't be interested in having me share these changes.  But if you are interested, I'd be happy to share them, as I think you'll probably find them to be a strict improvement over what you had, aside perhaps from quibbles with my formatting and/or profuse commentary.

Yes, a pull request with the label changes to cleanup line number handling would be appreciated. Just run Black on your code and it'll be good, the CI should complain if you don't (or send the PR as is, I'll run Black, and then I can merge).

Yes, a pull request with the label changes to cleanup line number handling would be appreciated. Just run Black on your code and it'll be good, the CI should complain if you don't (or send the PR as is, I'll run Black, and then I can merge).

Ok, I committed my current version to my fork, and passed that on in a pull-request to you, though I didn't blacken it, and it still contains profuse comments and TODO's that you may not like.  Feel free to take as much or as little as you like...

Ok, I committed my current version to my fork, and passed that on in a pull-request to you, though I didn't blacken it, and it still contains profuse comments and TODO's that you may not like.  Feel free to take as much or as little as you like...

Fixed by https://github.com/Lonami/pyndustric/commit/f8441abbc059241ca3d224d7c0619aaa824384b8.
When a reference to a line needs to be used in a _Jump _Instruction, a new _Label object instance is created. This instance is unique, and a reference to it is stored in the jump.
When generating code, a first pass assigns the correct line numbers to all labels. A second pass iterates over all instructions and represents them as strings, skipping labels. Jumps which reference labels have access to the label's line number at this point, so they can be correctly represented as strings.

Fixed by https://github.com/Lonami/pyndustric/commit/f8441abbc059241ca3d224d7c0619aaa824384b8.
When a reference to a line needs to be used in a _Jump _Instruction, a new _Label object instance is created. This instance is unique, and a reference to it is stored in the jump.
When generating code, a first pass assigns the correct line numbers to all labels. A second pass iterates over all instructions and represents them as strings, skipping labels. Jumps which reference labels have access to the label's line number at this point, so they can be correctly represented as strings.


static javascript content type charset header not set

Description
The charset for the distributed javascript file is not set in the response header, which leads to an error in the browser that implicitly assumes the file is "US-ASCII" encoded.
Current
Content-Type: application/javascript

Expected
Content-Type: application/javascript; charset=UTF-8

The i18n section of the /js/embed.min.js javascript therefore has encoding errors:
"comment-confirm":"ÐŸÐ¾Ñ‚Ð²ÑŠÑ€Ð¶Ð´ÐµÐ½Ð¸Ðµ"

Used configuration
docker-compose.yml
version: '3'

services:
  isso:
    image: wonderfall/isso@sha256:1ec8ce977fa9b68d2b513a93d89abf0bcca250d49781e4e279f2ace85519a767
    environment:
      - GID=1000
      - UID=1000
      - LANG=C.UTF-8
    volumes:
      - ./data/isso/config:/config
      - ./data/isso/db:/db
    ports:
      - 8888:8080

isso.conf
[general]
dbpath = /db/comments.db
host = https://redacted.com
[server]
listen = http://<IP_ADDRESS>:8080/

Curl request
curl -sSL -D - http://localhost:8888/js/embed.min.js -o /dev/null
HTTP/1.1 200 OK
Server: gunicorn/20.0.4
Date: Tue, 31 Dec 2019 10:11:15 GMT
Connection: close
Etag: "wzsdm-1577786490-68688-492700795"
Cache-Control: max-age=43200, public
Expires: Tue, 31 Dec 2019 22:11:15 GMT
Content-Type: application/javascript
Content-Length: 68688
Last-Modified: Tue, 31 Dec 2019 10:01:30 GMT
Access-Control-Allow-Origin: http://invalid.local
Access-Control-Allow-Credentials: true
Access-Control-Allow-Methods: HEAD, GET, POST, PUT, DELETE
Access-Control-Allow-Headers: Origin, Referer, Content-Type
Access-Control-Expose-Headers: X-Set-Cookie, Date

Possible causes
I might be on the wrong path because I never have used any of the libraries, but the Werkzeug documentation says:

Special note for mimetype and content_type: For most mime types mimetype and content_type work the same, the difference affects only ‘text’ mimetypes. If the mimetype passed with mimetype is a mimetype starting with text/, the charset parameter of the response object is appended to it. In contrast the content_type parameter is always added as header unmodified.

Werkzeug's source code suggests that there was a change in this behavior in Version 15.x:
https://github.com/pallets/werkzeug/blob/9844e0447e63366273c8b9f9f2400e19b45532d1/src/werkzeug/utils.py#L306-L316
Setting werkzeug==0.16.0 in setup.py and rebuilding the docker image did not help.

Seems to be an issue with werkzeug (https://github.com/pallets/werkzeug/issues/1689). Closing.


Typo "[Application@ResourceGroup]"→"[**Application@ResourceGroup…

…**]"
Bold with escape characters
https://docs.microsoft.com/en-us/uwp/schemas/appxpackage/uapmanifestschema/what-s-changed-in-windows-10

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hyoshioka0128 Thank you for submitting this fix to add escape characters where needed


Data from json objects and value filter

I have json with multiple objects but the keys aren't the same in each of them.
Let's say I have something like this.
[{ a: "foo",
b: "bar",
val: 20
},
{ b: "car",
c: "bar",
val: 10
}]
When it gets around the lines below, I get an error. Something about my "c" key.
if ((base = axisValues[k])[v] == null) {
base[v] = 0;
}
results.push(axisValues[k][v]++);
I tried to construct a json with "a", "b", "c" on every single object with null value for the ones that don't have value at all, but I can't filter the attributes rows/cols rendered with the name "null".
Any solution for this?
Thanks in advance.

Update: I want a behavior that looks like the exclusions but that removes from the list aswell.
Even with the exclusions for every key the table stops rendering results.

This library doesn't deal very well with "ragged" input like this where individual rows don't have the same keys or are missing keys. I'll take a look to see how hard it is to make it work but I'm skeptical that it will be easy.

OK, I have a PR open #600 which should address this, if you want to test it out.


update contributions

technically I have done a thing as well!

Whoops, merged too soon. There is a guide on how to add contributions here. tl;dr you need to use a CLI command to update the source of truth file, which then spits out the README.
As it stands, this change will get overridden the next time I build the site.
Would you have time to use the CLI to update the contributions? Thanks again!

ah frick. yes, will do.


Dead link

[Enter feedback here]
The page provides a link to https://github.com/mono/linker/tree/master/analyzer - this link returns a 404.

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

ID: aa951c69-0f9f-d6f8-b879-0a3427436e3c
Version Independent ID: 7807523a-115c-5f73-b22a-a914792467a4
Content: Build Process - Xamarin
Content Source: docs/android/deploy-test/building-apps/build-process.md
Product: xamarin
GitHub Login: @conceptdev
Microsoft Alias: crdun

Thanks for the heads-up - fixing now!


Polish the Deployment section and added akka.net

Added the Deployment section to the table of contents and moved the section to it's alphabetically order place.
Added Akka.net to the Distributed computer section

:+1: Thank you


Create a CODEOWNERS file to require a review from the "code owner" before merging changes

@robinv85 brought up this issue earlier.
To prevent contributors from making changes to code that was architected a certain way for a particular reason, and to allow the contributors and the person who implemented the feature (the "code owner") to have a discussion before merging the changes, a CODEOWNERS file can be created to notify the "code owner" that a change is being made to their implementation.
The "code owner"  can choose which file's to subscribe to and remove/add themselves from the CODEOWNERS file whenever they wish.
About CODEOWNERS:
https://help.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners#codeowners-file-location
Enable reviews from CODEOWNERS:
https://help.github.com/en/github/administering-a-repository/enabling-required-reviews-for-pull-requests

@BMariscal interesting suggestion, thanks for bringing this up! I'm not really familiar with this, I wonder what @manualzuru thinks about it?
To me it seems we don't really have much guarantees about which volunteers can spend time to really take ownership of specific parts of the codebase, I do know that some people have more knowledge about some specific parts that they worked on... but I would hope that someone else could also pick up some of those tasks when needed.

we added a codeowners file on iOS, it automatically adds all the codeowners as reviewers everytime someone added a PR
the persons added on the codeowners file are the most active members on the team


Do C# 9.0 Record Types Make ValueObject redundant?

I'm learning about C# 9.0 record type, a little late to the game, and they seem like they accomplish what ValueObject intends to solve.
The only thing it doesn't seem to do, is allow equality comparison when they have properties that are collections. The ValueObject (or at least the version I have) seems to allow for this whereas the record type does not.
Do you have any advice on where ValueObject should be used and should have record as the favored replacement?

Even before record types, valueobject's utility is questionable. I agree with your assessment that with C# 9 record types, those should typically be used rather than value objects. Objects that have collection properties usually aren't good candidates for value objects in my experience, anyway. If you have a case to make for one I'd be interested in hearing it.

I'll defer to your expert judgement on that one. I'll definitely shift to using record for my value objects.


[FR]: Performance support on macOS

Description

Ability to use Firebase Performance on macOS, logging custom and predefined performance metrics.
Currently, Firebase Performance is not available on macOS.
Audit what prevents its usage (I suspect it's something to do with automatically collected metrics, such as screen render performance, depending on UIKit)

API Proposal
No response
Firebase Product(s)
Performance

Is there any way this can be helped by community effort? I really don't want to use Sentry or some other tool for that.


Set xml_attribs=True in OktaApiResponse.build_xml_response

Problem description:
GET on /api/v1/apps/${applicationId}/sso/saml/metadata returns xml with important content in attributes, but method build_xml_response leaves attributes out.
Proposed solution:
https://github.com/okta/okta-sdk-python/blob/master/okta/api_response.py#L97
        self._body = xmltodict.parse(response_body, xml_attribs=True)

Resolved in 2.9.0


Add Filter for NewListForScopePager on RoleManagementPolicyAssignmentsClient

Feature Request

I am creating a Terraform resource to manage RoleManagementPolicies through terraform. I am looking to use the RoleManagementPoliciesClient to list role management policies for a given scope and roleDefinitionId to then load the existing RoleManagementPolicy. However, the NewListForScopePager does not allow specifying a Filter.
There is Filter support on other List methods and you are able to filter directly on the REST method (see: https://docs.microsoft.com/en-us/rest/api/authorization/privileged-role-policy-rest-sample)
https://management.azure.com/providers/Microsoft.Subscription/subscriptions/{{subscription-id}}/providers/Microsoft.Authorization/roleManagementPolicies?api-version=2020-10-01-preview&filter=roleDefinitionId eq '/subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleDefinitions/********-****-****-****-************'
This will return you the roleManagementPolicy for the request subscription and role.
Could support for Filter be added to this method?
EDIT
I had originally quoted the above API call which is incorrect, the correct call is to retreive a RoleManagementPolicyAssignment for a scope/roleDefinitionId, this can be acheived with the following API call
https://management.azure.com/subscriptions/{{subscription-id}}/providers/Microsoft.Authorization/roleManagementPolicyAssignments?api-version=2020-10-01&$filter=roleDefinitionId eq '/subscriptions/********-****-****-****-************/providers/Microsoft.Authorization/roleDefinitions/********-****-****-****-************'
So this applies to the RoleManagementPolicyAssignmentsClient and would request the addition of the Filter property.
Have tested in Postman with the above query and it does return the result for the scope/roleDefinitionId combination.

@StickNitro, could you provide the link of the package you are using?

The package link is https://pkg.go.dev/github.com/Azure/azure-sdk-for-go/sdk/resourcemanager/authorization/armauthorization

@StickNitro One question not related with this issue: Terraform is using our previous version of SDK but you are using our latest version, and I'm a little bit curious about your using scenario, could you help to elaborate? Thanks.

@StickNitro One question not related with this issue: Terraform is using our previous version of SDK but you are using our latest version, and I'm a little bit curious about your using scenario, could you help to elaborate? Thanks.

I assume when you say Terraform you are referring to the AzureRM provider! We have a couple of use cases that are not currently supported by the AzureRM provider, these are:

We automate a significant amount of configuration in Azure and seek to automate the PIM eligibility management through Terraform, in the current AzureRM provider there is no resource that supports the ability to manage PIM Eligible assignments through Terraform

We also are seeking to automate the management of Role settings in PIM, either at Management Group or Subscription scope, again this is not supported in the current AzureRM provider

Adding Service attention label so that Service team can look into this.
@darshanhs90, @AshishGargMicrosoft Please look into this once you get a chance.


Not colourised

    @media (min-width: 1600px) {
      html.naked-theme .pmd-HomepageHead--ads {
        padding-right: 420px;
      }
    }

Yeah, this is [Issue #1], aka the most annoying bug that I've been unable to squash. The reason for this bug can be summarized as "trying to parse with regular expressions." The fix will only come when I rewrite the syntax definition from scratch in the new sublime-syntax format. I likely won't have time to start that for another few months. Until then, I'm sorry for the annoyance. The README shows a couple of ways to mitigate the issue.

Okay thank you. :)


Warp Affine tensor HIP

Adds support for warp affine tensor on hip.
Support for U8/F32/F16/I8, NCHW/NHWC/toggle, Bilinear/NearestNeighbor is added.
Adds corresponding unit tests and performance tests.

@r-abishek failing the code analysis - details

@kiritigowda Yes, actually I checked it out it. It says - Variable 'src_f6.x' is reassigned before using the previous assignment, but I do use using the previous assignment from L1763-L1768 (https://github.com/GPUOpen-ProfessionalCompute-Libraries/rpp/blob/baa063da95b36fb307ccaf71b30ac5f730973048/src/include/hip/rpp_hip_common.hpp#L1763-L1768)
Not sure if codacy understood the pointer cast on L1757

@kiritigowda Yes, actually I checked it out it. It says - Variable 'src_f6.x' is reassigned before using the previous assignment, but I do use using the previous assignment from L1763-L1768 (
https://github.com/GPUOpen-ProfessionalCompute-Libraries/rpp/blob/baa063da95b36fb307ccaf71b30ac5f730973048/src/include/hip/rpp_hip_common.hpp#L1763-L1768
)
Not sure if codacy understood the pointer cast on L1757

Thanks, I will close the issue.

@asalmanp @rrawther @r-abishek
I ran the tests for this PR and everything looks good.
The only possible concern is that some of the images have grey backgrounds instead of black. Other than that, everything looks as it should.

@paveltc Thanks! The grey backgrounds are just for i8 due to the range from -128 to 127, which is usually the case for all rpp functions.

@asalmanp @rrawther I've made the changes for the make_float4 in all applicable cases. I've also added some comments to improve readability - basically in load/store helper functions to indicate which pixel-writes are happening and in what layout (pln3/pkd3) - https://github.com/GPUOpen-ProfessionalCompute-Libraries/rpp/pull/96/commits/789abc016f2a53d7a5f500dd01ad779fdf622023


manage.py command

This python manage.py syncdb should say: python bin/manage.py syncdb

Thanks! Will update.


Dockerize webapp

Things working on:

[ ] MongoDB init script - how to get user/db set up on first pass
[ ] MongoDB SSL setup - good to have locally
[ ] Webapp connection to Mongo - needs to be a bit more robust in terms of timing if DB is not up yet


NYC changes semantics of the program

Description:
Hello, I have an issue that I cannot resolve without your help.
When I use Nodejs to run the following program.js, the test is running OK. e.g: node program.js
When I use  NYC to get the coverage of the program, the test is failing due to timeout. e.g: nyc node program.js
After analyzing, I find that NYC changed the semantics of the program. In program.js, v1 > v0 returns False since the character b > a.  But, after instrumenting, v1 > v0 returns True since the character 1 > 0. And then, the program enters an infinite loop.
Does NYC have an argument to limit program execution time? When the limit is exceeded, the process is killed.
If not, Do you have some ways to break this infinite loop?
program.js:
var v0 = function (v1){
	var b = 1;
};
var v1 = function (v1){
	var a = 1;
};

console.log(v0<v1);

while(v0 < v1){
};

NYC instrument
cov_4ps048zci();
cov_4ps048zci().s[0]++;
var v0=function(v1){
	cov_4ps048zci().f[0]++;
	var b=(cov_4ps048zci().s[1]++,1);
};
cov_4ps048zci().s[2]++;
var v1=function(v1){
	cov_4ps048zci().f[1]++;
	var a=(cov_4ps048zci().s[3]++,1);
};
cov_4ps048zci().s[4]++;
console.log(v0<v1);
cov_4ps048zci().s[5]++;
while(v0<v1){};

nyc does change the output of fn.toString(), restoring the original fn.toString() is out of scope.  If this is a requirement of your project I recommend looking into c8.  Another option if this occurs in limited number of functions you could tell istanbul to ignore those two functions:
/* istanbul ignore next */
var v0 = function (v1){
	var b = 1;
};
/* istanbul ignore next */
var v1 = function (v1){
	var a = 1;
};

console.log(v0<v1);

while(v0 < v1){
};

Does NYC have an argument to limit program execution time? When the limit is exceeded, the process is killed.
If not, Do you have some ways to break this infinite loop?

NYC does not have a feature for limiting program execution time.  I'd suggest looking to your testing framework for this (mocha, tap, etc).  That is where this sort of test timeout would be implemented.


version 5 causes runtime error with Safari 14

Bug Report
Updating deepmerge-ts from v4.3.0 to v5.1.0 in our NextJS app started consistently causing unhandled runtime errors in Safari 14 (but not in newer versions of Safari). Reverting to 4.3.0 resolved the issue.
Expected behavior
Many of our users are still on Safari 14, so it would be nice if newer versions of deepmerge-ts still supported Safari 14.

Actual behavior
On Safari 14, we're consistently seeing an unhandled runtime error, specifically TypeError: values.at is not a function. (In 'values.at(-1)', 'values.at' is undefined).
I've noticed that 'values.at(-1)' relates to changes made to src/defaults/into.ts and src/defaults/vanilla.ts

Steps to reproduce
Run an app that uses deepmerge-ts v5 in Safari 14 (we've been doing our testing in Browserstack).

Proposed changes

Duplicate of #411

Reopening the discussion around this https://github.com/RebeccaStevens/deepmerge-ts/issues/487.


chore: update ciprod images to win-3.1.9 and 3.1.9

What type of PR is this?
/kind
Optionally add one or more of the following kinds if applicable:
/kind api-change
/kind deprecation
/kind failing-test
/kind flake
/kind regression
-->
What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Requirements:

[ ] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
https://github.com/microsoft/Docker-Provider/blob/ci_prod/ReleaseNotes.md

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 61.615%

Totals

Change from base Build<PHONE_NUMBER>:
61.6%

Covered Lines:
2541

Relevant Lines:
4124

💛  - Coveralls


CoreSync Usage

So I want to sync two sqlite databases, one will reside on device ( client ) and one will reside in OneDrive or DropBox.  Have you some usage instructions on how to do this with your library?

Did you look at tests? CoreSync/src/CoreSync.Tests/IntegrationTests.cs contains a couple of tests of synchronization between 2 SQLite databases

Couple of further questions please..

Is it correct that the EntityFramework is not required as only the Tests project is using it?
Am currently using the SQLite-net library  in a new
Xamarin application and would like to continue using this library for SQLite access.
Is the Created or Updated columns in the tables required for proper synchronization in each table?
What is the difference between Test1_Sqlite_Sqlite and Test2_Sqlite_Sqlite for SQLite to SQLite synchronization.

Orgbrat

Yes, it's correct, EF is not required at all: I just used it in tests for convenience as I was not obligated to deal with specific SQL language dialect in each test. Using EF was also an easy choice as I wanted to abstract away from specific database implementations etc.
I assume you refer to Created/Update columns in Users or Posts table: no they are not required, are just dummy columns I've added to that entities/tables.
Test2 is just a more complicated example of insert/update/delete operations. Test1 is easier to follow at first approach.

@Onotseike sorry but I need more context to understand your question, column type varchar(x) seems a SQL Server type while the code refers to Sqlite?

Hey @adospace ,
That is fine. The library the original poster mention https://github.com/praeclarum/sqlite-net treats Guid  as varchar(36) seehttps://github.com/praeclarum/sqlite-net/wiki/Features#features and the result of this means when creating the sqlite database and tables with the library mentioned above, a primary key with datatype Guid will result in a varchar (36)


destroys empty workspace + minor fixes

destroys empty workspaces.
() -> (void), as () takes any number of arguments when it should take none.
int -> bool for handle_command return type.
put free_swayc() into header for destroy_workspace to use
temporary fix to workspace_next_name() as it returned an unfreeable name.
https://github.com/SirCmpwn/sway/issues/11

() -> (void) is not acceptable, revert it.

Meh, fine.

i have no problem changing that back, its just a quick sed -i 's/(void)/()/' *.[ch]
i am curious why it might be a problem though.
but if its fine i guess thats that.


I encountered an error at an unknown location during runtime. Hello

Successfully registered the following environments: ['MetaDrive-validation-v0', 'MetaDrive-10env-v0', 'MetaDrive-100envs-v0', 'MetaDrive-1000envs-v0', 'SafeMetaDrive-validation-v0', 'SafeMetaDrive-10env-v0', 'SafeMetaDrive-100envs-v0', 'SafeMetaDrive-1000envs-v0', 'MARLTollgate-v0', 'MARLBottleneck-v0', 'MARLRoundabout-v0', 'MARLIntersection-v0', 'MARLParkingLot-v0', 'MARLMetaDrive-v0'].
Known pipe types:
wglGraphicsPipe
(all display modules loaded.)

Where is the error?

When running the example folder drive_in_single_agent_env.py
I figured it was engine_utils.py——cls.singleton
def initialize_engine(env_global_config):
cls = BaseEngine
# print(env_global_config)
if cls.singleton is None:
# assert cls.global_config is not None, "Set global config before initialization BaseEngine"
cls.singleton = cls(env_global_config)
else:
raise PermissionError("There should be only one BaseEngine instance in one process")
return cls.singleton
I reinstalled the panda3D

I don’t think you need to reinstall panda. You need to restart the jupyternotebook or the process where you once initialized the MetaDrive environment.
here is the story: you can only create one MetaDrive environment in one process. Unless, you explicitly call the close function of the first environment instance.
env1 = MetaDriveEnv()
env1.close()
env2 = MetaDriveEnv()

Thank you very much.


How can I trim the white spaces at the beginning and at the end of the editor?

This issue is stale because it has been open for 60 days with no activity.

This issue was closed because it has been inactive for 7 days since being marked as stale.


Generalize mp_to_pauli so that it can work with any observable that has a Pauli Rep

Right now mp_to_pauli only works for observables that act only on a single qubit. To improve upon this, we can actually make it so that any observable can be converted to its respective SparsePauliOp. This includes Hamiltonians, LinearCombinations, SProd, Prod, Sum, etc...
This PR also includes some minor refactoring of the converter.py file in general (using f strings, deleting unneeded variables, etc..."

Looking good @austingmhuang, thanks for working on this! I think there are a few small loose ends to wrap up before this is ready to merge.
I left a couple of comments in the code, and I would also like to suggest that a few more "integration" style tests are added, probably in test_base_device tests, using this functionality within an execution. For example maybe adding additional parameterizations in test_process_estimator_job, and adding a test similar to test_estimator_with_different_pauli_obs that checks more complicated observables (you can compare to the results of default.qubit instead of to analytical results).

Yeah that makes sense. I'll have to double check and see what observables default_qubit supports and edit qiskitdevice2 to support the same things before I write these "integration" style tests. This is a good point to bring up though, thanks @lillian542!

[sc-62045]


Editing menus doesnt affect sites pages

Also its unable to insert menus into page content
<respond-menu type="primary"><respond-menu>
transforms into
<respond-menu type="primary"><respond-menu> </respond-menu></respond-menu>

Ok, its ok. I should use
<ul respond-plugin type="menu" menu="footer"></ul>
instead of
<respond-menu type="primary"><respond-menu>


python-wechaty 荣获中国优秀开源优秀项目

Please make sure to check the following boxes creating your pull request, thank you very much!

[ ] Add Blog Header, including title, author, image, categories, tags, etc.
For example:
---
title: Your Great Blog Title
author: your_github_id
categories: project
tags:
  - python
  - padlocal
image: /assets/2021/02-your-blog-slug/teaser.jpg
---

One line bio

Your blog post content Your blog post content
Your blog post content Your blog post content
Your blog post content Your blog post content

It will be easier to start drafting your post by using a existing post file as your template, for example, this one

[ ] Keep all filenames lowercase, and use - to connect words instead of space. e.g. 2017-10-06-wechat-pc-impactor.md instead of 2017-10-06-WeChat PC Impactor.md

[ ] Embed video/pdf from YouTube/Bilibili/local (if there's any) by using {% include iframe.html src="URL_or_PATH" %}. (Learn more about how to embed file/url in the post by reading this blog post

[ ] Save photo to local before publishing, to a folder named by ${MONTH}-${YOUR_BLOG_SLUG}/ under /assets/2021/ directory.

[ ] Select a beautiful and meaningful teaser image for your blog

[ ] Create your contributor profile (if you are a first time contributor)
For excample:

jekyll/_contributors/lijiarui.md

---
name: Jiarui LI (李佳芮)
site: https://lijiarui.github.io
bio: 句子互动创始人 & CEO，微软人工智能最具价值专家 (AI MVP)
avatar: /jekyll/assets/contributors/lijiarui/avatar.png
email<EMAIL_ADDRESS>twitter: https://weibo.com/u/2175505900
---

Here is the example file:

lijiarui.md: https://github.com/wechaty/wechaty.js.org/blob/master/jekyll/_contributors/lijiarui.md
It will shown like this on wechaty website: https://wechaty.js.org/contributors/lijiarui/

To learn more about the contribute guideline, visit: https://wechaty.js.org/docs/contributor-program/

ping @huan @lijiarui

I think it's a little bit too simple....
You should add more info of 中国开源云联盟优秀开源项目 and python-wechaty

It's just an announcement for this great event and result. So I give the simple introduction for 中国开源云联盟优秀开源项目 and python-wechaty.
I prefer to the short introduction. How do you think about ? If you insist on adding more info, I will give commit later.

ping @lijiarui


Adding comments to main.py file

Just comments to the mail file, as the main file is the entry point to this great project and in a way some sort of an "interface" which better be as clear as possible and invite other developers to contribute...

Thanks for trying out aider and for taking the time to put together this pull request.
I think a lot of the comments that have been added are stating fairly obvious things. There are definitely some useful comments in there that clarify some more subtle issues.
But I don't think I can merge this PR, as is.

Thanks for trying out aider and for taking the time to put together this pull request.
I think a lot of the comments that have been added are stating fairly obvious things. There are definitely some useful comments in there that clarify some more subtle issues.
But I don't think I can merge this PR, as is.


[SQL] az sql db replica create: Add --ha-replicas argument

Description
Added an alternate syntax to sql db create and sql db replica create to align customer experience with our rename of ReadReplicaCount database property to HighAvailabiltyReplicaCount.
Testing Guide
Automated tests are updated in this PR
History Notes
[SQL] az sql db create: Add --ha-replicas argument

This checklist is used to make sure that common guidelines for a pull request are followed.

[x ] The PR title and description has followed the guideline in Submitting Pull Requests.

[x ] I adhere to the Command Guidelines.

[x ] I adhere to the Error Handling Guidelines.

SQL


doc: add --break-system-packages

Description
Add --break-system-packages argument for pip in the install doc
Closes #984
Checklist:

[X ] I have read the Contribution Guidelines
[ X] I have performed a self-review of my own code
[ X] I have commented my code, particularly in hard-to-understand areas
[ X] My changes generate no new warnings

Contributor License Agreement
By submitting this pull request, I acknowledge and agree that my contributions will be included in Stirling-PDF and that they can be relicensed in the future under the MPL 2.0 (Mozilla Public License Version 2.0) license.
(This does not change the general open-source nature of Stirling-PDF, simply moving from one license to another license)

The PR only touches a *.md file which is ignored by the build action.


Integrate QMK Driver Installer

We need a driver installed in certain situations. QMK Flasher should use QMK Driver Installer to install this automatically when needed.

Since you assigned this task to yourself; what would be a realistic expected date for a solution of this issue?

I had planned to do that work during my trip to Seattle last month, but ended up not having enough time. It's still on my todo list but I don't have a firm timeline right now. If someone wants to do it sooner I'm happy to hand it off.


Some comments on the installation in an Airgapped environment.

Mr. Smith.
We , my collegue Rob and I had to make some changes to get the installation working in our environment, I wanted to email , but I did not know how.
If there is a better way to inform you, please inform me.

We changed the common.sh :
#function v4m_replace {

if echo "$OSTYPE" | grep 'darwin' > /dev/null 2>&1; then
sed -i '' s/"$1"/"$2"/g  "$3"
else
sed -i  s/"$1"/"$2"/g  "$3"
fi
#}
INTO
function v4m_replace {
sed -i ''s%$1%$2%g'' "$3"
}

In the example yaml user.env here stood AIRGAP_HELM_FORMAT: oci.  we changed : to = → AIRGAP_HELM_FORMAT= tgz
Change in /appl/mon/viya4-monitoring-kubernetes/monitoring/prom-operator_container_image.template the line
#imagePullSecrets: IMAGE_PULL_SECRETS
into
imagePullSecrets: [name: IMAGE_PULL_SECRET]
/appl/mon/viya4-monitoring-kubernetes/monitoring/pushgateway_container_image.template also needs this change.
adding smtp configuration
added these lines in the user-values-prom-operator.yaml(create a kubernets secret kube-prometheus-stack-grafana-secret-mail with MAILUSER + MAILPASSWORD):
This was a struggle, with outlining..so I think to post it.
grafana:
See https://grafana.com/docs/grafana/latest/administration/configuration/#smtp
envFromSecret: kube-prometheus-stack-grafana-secret-mail
"grafana.ini":
smtp:
enabled: "true"
host: mailhost:25
from_address<EMAIL_ADDRESS>from_name: someone
skip_verify: "true"
user: $__env{MAILUSER}
password: $__env{MAILPASSWORD}

@dikpater Thank you for opening this issue to let us know about the problems you ran into and the work-arounds you needed.  I am sorry you had trouble; but it sounds like you were able to get everything working in the end.

The v4m_replace function issue
I am not aware of any other users having problems with this function.  The existing function code has generally worked on Bash 4 on Linux and with the Bash built into the Apple Mac.  But there can always be compatibility issues.  What operating system were you using?  What version of BASH are you using?
The AIRGAP_HELM_FORMAT environment variable
I am glad you found the AIRGAP_HELM_FORMAT environment variable.  We discuss it in the documentation about deploying into an air-gapped environment but some people miss it.
Specifying the imagePullSecret
It is very strange that you needed to make that change.  What value did you specify for the AIRGAP_IMAGE_PULL_SECRET_NAME environment variable?  I have just double-checked the code  and it should have generated the line properly (including the brackets and name:).  Seeing how you set the environment variable will allow us to do additional testing.
Providing SMTP Configuration
I think GitHub markdown formatting may have garbled your sample code a bit, I don't think the proper yaml indentations were preserved.  For future reference, you can include a block of code (or yaml) and have the indentation preserved by clicking on the <> icon in the formatting toolbar after typing your code. (Or, you can put a line with 3 tick marks (`) before and after a block of code.)   For example:

yaml:
  indentations:
    can_be: difficult

In any case, we know providing additional Grafana configuration information can be difficult.  We hope to make things like this easier in the future.
Thank you again for opening this issue and sharing information on the problems you ran into.  Please provide the information I requested so we can make any needed improvements.
Regards,
Greg

@dikpater Sorry, I've been out of office and haven't had a chance to follow-up on this for the last couple of weeks.  It would be very helpful if you could provide more information about your experience so we can address any bugs or needed tweaks to our code or documentation.  I included some questions in my earlier response, but let me list them here:

Please describe the environment in which you were running our deployment scripts (e.g. operating system, BASH versions, etc.)
Please share information on the values you set for the various air-gap related environment variables (e.g. AIRGAP_HELM_FORMAT, AIRGAP_IMAGE_PULL_SECRET_NAME, etc.)

Regards,
Greg

Greg
At this moment I am not working. My wife suffers from Alzheimer’s and is
now in a nursery home. We need time to recover from the situation.
When I am back I will give the requested info.
But this will be half November.
Regards
Dik Pater
Op vr 1 nov 2024 om 22:00 schreef Greg Smith @.***>

@dikpater https://github.com/dikpater Sorry, I've been out of office
and haven't had a chance to follow-up on this for the last couple of weeks.
It would be very helpful if you could provide more information about your
experience so we can address any bugs or needed tweaks to our code or
documentation. I included some questions in my earlier response, but let me
list them here:

Please describe the environment in which you were running our
deployment scripts (e.g. operating system, BASH versions, etc.)
Please share information on the values you set for the various
air-gap related environment variables (e.g. AIRGAP_HELM_FORMAT,
AIRGAP_IMAGE_PULL_SECRET_NAME, etc.)

Regards,
Greg

—
Reply to this email directly, view it on GitHub
https://github.com/sassoftware/viya4-monitoring-kubernetes/issues/689#issuecomment-2452582818,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIKLRVDUWVNHXIUOR3BVNETZ6PTVDAVCNFSM6AAAAABP7B6HYKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDINJSGU4DEOBRHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hi Greg,
I also had an error related to v4m_replace function definition I believe as my deployment was failing with sed error:
./deploy_logging.sh
INFO User directory: /opt/work/deployments/sas-prod-oss/viya4mon/config
INFO Helm client version: 3.16.2
INFO Kubernetes client version: v1.27.9
INFO Kubernetes server version: v1.27.9
INFO Loading user environment file: /opt/work/deployments/sas-prod-oss/viya4mon/config/logging/user.env
INFO Deploying into an 'air-gapped' cluster from private registry [x.x.x.x/monitoring]
Deploying logging components to the [logging] namespace [Tue Nov  5 09:04:06 PM UTC 2024]
sed: -e expression #1, char 44: unknown option to `s'
ERROR Exiting script [deploy_logging.sh] due to an error executing the command [logging/bin/deploy_osd.sh].
After editing the function as per the above, deployment went through... I saw some sed errors from time to time:
sed: can't read : No such file or directory
...but resources were created and pods were Running, however, deployment failed.
INFO Loading Content into OpenSearch
ERROR The OpenSearch REST endpoint has NOT become accessible in the expected time; exiting.
ERROR Review the OpenSearch pod's events and log to identify the issue and resolve it before trying again.
ERROR Exiting script [deploy_logging.sh] due to an error executing the command [logging/bin/deploy_opensearch_content.sh].
export NODE_PORT=$(kubectl get --namespace logging -o jsonpath="{.spec.ports[0].nodePort}" services v4m-osd)
export NODE_IP=$(kubectl get nodes --namespace logging -o jsonpath="{.items[0].status.addresses[0].address}")
echo http://$NODE_IP:$NODE_PORT
http://x.x.x.x:31033
...
x.x.x.x is the IP of the CAS node.
,and indeed I get nothing in the browser.
What am I doing wrong? Is it ok to run this on the CAS node?
Can I take this with SAS Support?
Please describe the environment in which you were running our deployment scripts (e.g. operating system, BASH versions, etc.):
Ubuntu 22.04.1 LTS (GNU/Linux 5.15.0-43-generic x86_64)
GNU bash, version 5.1.16(1)-release (x86_64-pc-linux-gnu)
Please share information on the values you set for the various air-gap related environment variables (e.g. AIRGAP_HELM_FORMAT, AIRGAP_IMAGE_PULL_SECRET_NAME, etc.)
AIRGAP_DEPLOYMENT=true
AIRGAP_REGISTRY=x.x.x.x/monitoring
AIRGAP_IMAGE_PULL_SECRET_NAME=v4m-image-pull-secret
AIRGAP_HELM_FORMAT=tgz
AIRGAP_HELM_REPO=/opt/helm
We are using harbor for private registry.
Thanks a lot!

Based on some testing, I think the issue both @dikpater and @sorin1sima encountered is caused by including a special character, i.e. the "/", in the value of the AIRGAP_REGISTRY environment variable.  We will fix things to handle that better at some point.  But, in the mean-time, I believe this can be addressed by escaping the special character when setting the value of the environment variable.  So, for example, use AIRGAP_REGISTRY="x.x.x.x\/monitoring" instead of a AIRGAP_REGISTRY=x.x.x.x/monitoring.  @sorin1sima will report back after he has had a chance to test this.