flashplayer: <IP_ADDRESS> -> <IP_ADDRESS> [Critical security fixes]

Motivation for this change

Critical security fixes
Bug fixes
Other improvements

https://helpx.adobe.com/flash-player/release-note/fp_27_air_27_release_notes.html
https://helpx.adobe.com/security/products/flash-player/apsb17-28.html
Things done

[X] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)

Built on platform(s)

[X] NixOS
[ ] macOS
[ ] Linux

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)

[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"

[X] Tested execution of all binary files (usually in ./result/bin/)

[X] Fits CONTRIBUTING.md.

Built packages

nix-env -i -f . -A pkgs.flashplayer
nix-build -I nixpkgs=. -A pkgsi686Linux.flashplayer
nix-build -I nixpkgs=. -E "(import <nixpkgs> {}).flashplayer.override { debug = true; }"
nix-build -I nixpkgs=. -E "(import <nixpkgs> {}).pkgsi686Linux.flashplayer.override { debug = true; }"
nix-build -I nixpkgs=. -A pkgs.flashplayer-standalone
nix-build -I nixpkgs=. -A pkgs.flashplayer-standalone-debugger
nix-build -I nixpkgs=. -E "(import <nixpkgs> {}).chromium.override { enablePepperFlash = true; }"

Played a video with Firefox (x86_64)

Played a video with Chromium (x86_64)

Played a video with flashplayer-standalone and flashplayer-standalone-debugger (x86_64).

Checked the version with Firefox (x86_64) http://www.adobe.com/software/flash/about/

Checked the version with Chromium (x86_64) http://www.adobe.com/software/flash/about/

Checked the version with with flashplayer-standalone and flashplayer-standalone-debugger (x86_64).

Thank you. Picked to release as well.


Documentation for new features of wagtailforms

We need to move documentation from wagtailsurveys (see README.md) into Wagtail once #2617 will be merged.

Fixed in #3242


Jittery animation data

Describe the bug
Animations in S2V have a slight jitter on some bones. They're read incorrectly, as the same jitter is also present in exported animations (so not just a visual issue).
The issue is present on a lot of animations, but it's not very obvious on most of them.

I've tested three different previous vrf versions and the issue is there, but it's slightly different in all of them, with the oldest looking the best (jitter in torso might just be masked by the entire body jittering up a bit, but the hand clips less at the end too).
v<IP_ADDRESS>7:
https://github.com/ValveResourceFormat/ValveResourceFormat/assets/65136069/c6630b08-6d56-45b1-92e8-62dc120ad452
v<IP_ADDRESS>1:
https://github.com/ValveResourceFormat/ValveResourceFormat/assets/65136069/5e142b60-2c6a-48f0-a475-1a147b3648d1
v6.0.2455:
https://github.com/ValveResourceFormat/ValveResourceFormat/assets/65136069/b1daf884-6073-4e44-9fc6-ebb0c15ff6aa
Relevant log output or exception with stacktrace
No response
What game does this happen in
HLA and CS2, probably every other game too
Reference file in a Source 2 game
CS2:
animset_uiplayer.vmdl_c
animation t_loadout_ump45_spray
(look at head)
https://github.com/ValveResourceFormat/ValveResourceFormat/assets/65136069/5da5601a-cb08-43e0-8272-c0f2747270fa
HLA:
uncombined_vortiguant.vmdl_c
animation @vort_substation_2019_vort_pod_freed
(left is ModelDoc, right is S2V; look at upper torso, and right hand on the last few frames)
https://github.com/ValveResourceFormat/ValveResourceFormat/assets/65136069/5e3c5467-2a4b-4c04-9ec9-75a64849bc82
Skeleton in S2V:
https://github.com/ValveResourceFormat/ValveResourceFormat/assets/65136069/15232ff8-4be7-4ab5-ba6a-a2763a46fbda
Expected behavior
Smooth animations
What version of VRF are you using? On what platform?
7.0, Windows 10

The likely culprit here is CCompressedDeltaVector3 decoder.


Addition of "." as an Option for "Copy Relative Path Separator" in VSCode

Currently, when utilizing the "Copy Relative Path" feature in VSCode, users are limited to choosing between "\" and "/", as separators for relative paths. However, for enhanced flexibility and compatibility across various operating systems, it would be beneficial to include "." as an additional option.
This addition would empower users to tailor their relative path separators according to their specific needs and preferences, ensuring smoother workflow experiences.
This feature is particularly useful in scenarios where there's a need to import a specific Python file from another library and require the file path with "." separators for the import to function correctly. Presently, users have to manually replace the "/" separators with "." when copying a file path using the "Copy as Path" feature.
Therefore, we kindly request the integration of "." as a selectable separator alongside "\" and "/" in the "Copy Relative Path" feature of VSCode.

This issue has been closed automatically because it needs more information and has not had recent activity. See also our issue reporting guidelines.
Happy Coding!


code issue

require(game:GetService("ReplicatedStorage"):WaitForChild("Unified3DInput")):SetUpClient() - this is wrong
require(game:GetService("ReplicatedStorage"):WaitForChild("Unified3DInput")).SetUpClient() - this is correct
(the : is actually an . from what I see in the code of module)

With the current code, both are fine. I cover what . vs : is in an older post on the DevForum.
https://devforum.roblox.com/t/oop-using-self/282376/2


Cross Section problem

If you try to create virtual 4C viewpoint in HiGlass following instructions from docs
you get either observed over expected or inverted 4C-signal, but not proper virtual 4C. E.g. there is no peak on short-range interactions, and there is no difference between cis/trans: http://higlass.io/l/?d=Po-o1DRdSBujGe75EQwTAw

Sorry for replying so late :(
I am looping in @pkerpedjiev who might know what's going on. I've never used this feature myself so I can't say what exactly is going on.


Add BankMsg::Burn to CosmosMsg

A dev wanted to add this as a custom callback, but I think this would be better to add directly to Bank.
#[derive(Serialize, Deserialize, Clone, Debug, PartialEq, JsonSchema)]
#[serde(rename_all = "snake_case")]
pub enum BankMsg {
    Send {
        to_address: HumanAddr,
        amount: Vec<Coin>,
    },
   Burn {
        amount: Vec<Coin>,
    },
}

Where is this implemented in the SDK? The bank module does not seem to have a message type like this: https://github.com/cosmos/cosmos-sdk/blob/v0.42.1/proto/cosmos/bank/v1beta1/tx.proto#L10-L17

No there is no such message. There is also no sdk message equivalent to IbcMsg::SendPacket (we need to call the keepers directly).
However, this has been requested before and the functionality is exposed on the bank keeper: https://docs.cosmos.network/master/modules/bank/02_keepers.html#basekeeper


Add intRVFL to the models module

Add intRVFL to the models module

Thanks for the refactoring, Mike!
I like how the new code looks like.
Functionality-wise, it is all good, I only added a few minor edits.
Few minor edits made:

train_loader in “UCI_benchmark_intRVFL.py” is not needed anymore with the current code. [Fixed].
In “UCI_benchmark_intRVFL.py”, added transform() to data when calling “fit_ridge_regression()” - was affecting performance a lot.
In “models.py”, kappa is not mentioned as a part of description in “Args”. [Fixed]
In “UCI_benchmark_intRVFL.py”, ridge regression was missing (not a big effect on results though) when calling “fit_ridge_regression()”. [Fixed]

Few additional considerations while going through the code:

It could make sense to have alpha as an input to IntRVFLRidge() and then avoid calling it explicitly with “fit_ridge_regression()”.
I would hide “one_hot_targets” under the hood in “fit_ridge_regression” as it is unclear what does it give to the user by explicitly seeing formation of one-hot encodings in “UCI_benchmark_intRVFL.py” but I see the extra hassle with sending in "num_classes".
After refactoring, “fit_ridge_regression()” is a function within IntRVFLRidge() class. Before it was meant to be a separate function just because it is a primitive for a particular type of classifier (like centroids) so it does not have to stay exclusively within IntRVFLRidge(). But perhaps it is not so complicated so one could copy-paste this piece of code every time it is needed in some other place.
All these considerations are not critical and perhaps not worth extra discussion so the final word about them is yours.

Thanks for spotting my bugs!

From what I could tell the alpha parameter is specific to the learning method ridge regression so if we end up adding more methods they could have their own parameters which are independent of the class instance. Let me know if I'm misinterpreting that?
The reason I moved the one-hot encoding outside ridge regression is because you had a comment that said something like you could also have multiple class vectors per class. By letting the user handle the one-hot encoding it could split one class over multiple class vectors. Do you think this makes sense?
I will refactor your last point

I agree that  the alpha is specific to the learning method ridge regression. I was probably assuming that if we have other methods for training the classifier we would create another class instance something like IntRVFLAbc() where "Abc" would refer to the specific classifier used for the model (currently IntRVFLRidge suggests that ridge regression is used as the classifier). Maybe it does not make sense to have multiple class instances and, instead, one should specify different ways of forming the classifier within the existing class so specifying "fit_abc()" method instead.
Okay, that is right. I have not made myself clear enough in that comment. It targeted prototype-based classifiers (like GLVQ) for ridge regression based classier, I am not sure if one could benefit from multiple class vectors per class. So for fit_ridge_regression(), I think we can safely have one-hot encodings inside the function, thus, having less details exposed to the user.
Great!


Support offset pagination for prisma connection

Prisma supports both offset and cursor pagination: https://www.prisma.io/docs/concepts/components/prisma-client/pagination#-cons-of-offset-pagination
As far as I can tell, the Pothos prisma plugin only supports cursor-based pagination.
While I recognize offset-based pagination doesn't scale, I have a small use case where I am ordering by a column that is not unique but I would still like to be able to paginate.

The Prisma plugin can handle offset pagination in a number of different ways.  The issue is there is no good GraphQL standard that is widely adopted enough to be part of the core plugin.
For the most simple approach you can add offset/limit args and use them in a query on any list relation

here is an example of a limit (but offset can work the same way) https://github.com/hayes/pothos/blob/main/packages/plugin-prisma/tests/example/schema/index.ts#L168-L178
You can ignore the resolver there

Some existing discussion around this here as well: https://github.com/hayes/pothos/discussions/333

Thank you for that info and for the links. I wound up with this, which seems to work for my use-case:
const UploadUserComment = builder.prismaObject("UploadUserComment", {
  // ...
});

const UploadRecord = builder.prismaObject("UploadRecord", {
  select: {
    id: true,
  },
  fields: (t) => ({
    // ...
    userComments: t.connection(
      {
        type: UploadUserComment,
        resolve: async (root, args, context, info) => {
          const [res, totalCount] = await Promise.all([
            resolveOffsetConnection({ args }, async ({ offset, limit }) => {
              const query = queryFromInfo({
                context,
                info,
                path: ["edges", "node"],
                typeName: "UploadUserComment",
              });
              return prisma.uploadUserComment.findMany({
                ...query,
                where: { uploadRecordId: root.id, replyingTo: null },
                skip: offset,
                take: limit,
                orderBy: { score: Prisma.SortOrder.desc },
              });
            }),
            prisma.uploadUserComment.count({
              where: { uploadRecordId: root.id },
            }),
          ]);

          return {
            totalCount,
            ...res,
          };
        },
      },
      {
        name: "UploadRecordUserCommentsConnection",
        fields: (t) => ({
          totalCount: t.int({
            resolve: (root) => root.totalCount,
          }),
        }),
      }
    ),
  }),
});


[WIP] Rename the track from ColdFusion to CFML

Before merging this, please merge https://github.com/exercism/cfml/pull/61 - that will minimize the diff in this PR.

You know, I just realized the title of this pull says [WIP].  Should I have waited to merge the pull?

Nope :-) I only put WIP in there because I wanted #61 to be merged first. It's all good!


refactor: remove unnecessary "&" in Filters

Description
$response is an object, so it is passed as an object id.
https://www.php.net/manual/en/language.oop5.references.php
Checklist:

[x] Securely signed commits
[] Component(s) with PHPDoc blocks, only if necessary or adds value
[] Unit testing, with >80% coverage
[] User guide updated
[x] Conforms to style guide

Thank you @kenjis


Integrate shipyard scheduling DVM

Add scheduling to the note options dialog

In the NoteCreate view, add an option to create a DVM request?

Right, and display it in NoteOptions

I need more context for this one issue:
Is the goal just to postpone the posting of a note? In which case I could'nt find a DVM kind or handler for this specific purpose.
Or is the goal creating any kind of DVM request depending on the DVM handlers available from a set of Relays?

Yep, the goal is to do what shipyard.pub does and allow people to postpone the sending of a note. You can find some information about that DVM kind here: https://www.data-vending-machines.org/kinds/5905/

https://www.data-vending-machines.org/kinds/5905/

Everything is clear from this spec expect for the time the note must be dispatched, it's the created_at field that is used?

On review, this feels potentially scope-creepy to me. I'm surveying people to find out if we should go ahead with this: nostr:nevent1qvzqqqqqqypzp978pfzrv6n9xhq5tvenl9e74pklmskh4xw6vxxyp3j8qkke3cezqy88wumn8ghj7mn0wvhxcmmv9uq3camnwvaz7tmgdajxccn0vshxxmmjv93kcefww3hk7mrn9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcpzemhxue69uhkzat5dqhxummnw3erztnrdakj7qfhwaehxw309askgmmjd9hxwcmpwfjxjmnpdscjumrwvf5hguewvdhk6tmwdaehgunjv4kxz7f0w3jhxapdwfjkccteqqswkap3kp6lpq4ddcljranwepwnxznmm3actsvqmk5djn3wt9tks2gg34930

Everything is clear from this spec expect for the time the note must be dispatched, it's the created_at field that is used?

I can confirm, the created_at field defines the time the DVM should publish the note


[BEAM-6103] Enable BQ streaming insert timeouts

Testing has shown that this does not seem to affect performance and memory usage.
In case of timeout, we have found that a transient 400 error may be reported by BQ. In these cases the runner had always retried the bundle successfully.
Also fixes second -> millisecond conversion for flag.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @chamikaramj

LGTM. Thanks.
Does it make sense to hold off merging this till 2.25.0 release branch is cut to observe performance of benchmarks over the long run ?

I guess we can merge this now that the release branch has been cut.

Rebased and moved changes to new 2.26.0 section

Opened a bug for the Java flake: https://issues.apache.org/jira/browse/BEAM-10968


Allow styling of notification icon

theme property is now applied to notification icon so that surrounding components can style this notification icon the way they want to.
Types of Changes
Prerequisites
Please make sure you can check the following two boxes:

[x] I have read the CONTRIBUTING document
[x] My code follows the code style of this project

Contribution Type
What types of changes does your code introduce? Put an x in all the boxes that apply:

[x] Bug fix (non-breaking change which fixes an issue, please reference the issue id)
[ ] New feature (non-breaking change which adds functionality, make sure to open an associated issue first)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] My change requires a change to the documentation
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[x] All new and existing tests passed

Description
Allow styling of notification icon. Before it was not possible to change the style of the icon inside a notification as the theme property was not applied. This is now changed.
Fixes #191

@jotdl Could you resolve conflicts?


[mesh] fix initTrafficGate panic when service not found

When Sidecar is deployed and there is not such mesh service in the system, the initTrafficGate routine will panic due to the missing judgment of the nill pointer.

2021-07-24T09:32:04.611Z	ERROR	worker/worker.go:232	easemesh-controller: recover from: runtime error: invalid memory address or nil pointer dereference, stack trace:
goroutine 242 [running]:
runtime/debug.Stack(0xc000ccbb08, 0x24cd940, 0x3e2b860)
	runtime/debug/stack.go:24 +0x9f
github.com/megaease/easegress/pkg/object/meshcontroller/worker.(*Worker).heartbeat.func1.1(0xc00084e1a0)
	github.com/megaease/easegress/pkg/object/meshcontroller/worker/worker.go:233 +0x9a
panic(0x24cd940, 0x3e2b860)
	runtime/panic.go:965 +0x1b9
github.com/megaease/easegress/pkg/object/meshcontroller/spec.(*Service).IngressPipelineName(...)
	github.com/megaease/easegress/pkg/object/meshcontroller/spec/spec.go:591
github.com/megaease/easegress/pkg/object/meshcontroller/worker.(*IngressServer).InitIngress(0xc000036000, 0x0, 0x2328, 0x0, 0x0)
	github.com/megaease/easegress/pkg/object/meshcontroller/worker/ingress.go:99 +0xb2
github.com/megaease/easegress/pkg/object/meshcontroller/worker.(*Worker).initTrafficGate(0xc00084e1a0, 0x0, 0xc000c82dc0)
	github.com/megaease/easegress/pkg/object/meshcontroller/worker/worker.go:310 +0x79
github.com/megaease/easegress/pkg/object/meshcontroller/worker.(*Worker).heartbeat.func1()
	github.com/megaease/easegress/pkg/object/meshcontroller/worker/worker.go:238 +0x1dd
github.com/megaease/easegress/pkg/object/meshcontroller/worker.(*Worker).heartbeat(0xc00084e1a0)
	github.com/megaease/easegress/pkg/object/meshcontroller/worker/worker.go:268 +0x8e
created by github.com/megaease/easegress/pkg/object/meshcontroller/worker.(*Worker).run
	github.com/megaease/easegress/pkg/object/meshcontroller/worker/worker.go:222 +0x1f9

Codecov Report

Merging #144 (fc179dd) into main (5cb82af) will increase coverage by 0.07%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #144      +/-   ##
==========================================
+ Coverage   58.45%   58.52%   +0.07%
==========================================
  Files          36       35       -1
  Lines        2477     2474       -3
==========================================
  Hits         1448     1448
+ Misses        924      921       -3
  Partials      105      105

Impacted Files
Coverage Δ

pkg/common/sys_proc_linux.go

Continue to review full report at Codecov.

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


Triage workflow update + Contributor guide update

This PR:

removes the add triage-needed label from the workflow
Adds logic to put new PR in ToDo column on the project board.
updates the contributor guide to be more explicit with how you create a new installPlan
Explains the PR review workflow at a high level.

@rudouglas ah-ha! yes, I'll use that. Thanks!


SAA-523: Create history record when marked attendance records are updated

Codecov Report
Patch coverage: 30.00% and project coverage change: -0.19 :warning:

Comparison is base (d998369) 78.54% compared to head (888352f) 78.35%.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #237      +/-   ##
============================================
- Coverage     78.54%   78.35%   -0.19%
- Complexity     1305     1306       +1
============================================
  Files           224      224
  Lines          5555     5572      +17
  Branches        196      197       +1
============================================
+ Hits           4363     4366       +3
- Misses         1071     1082      +11
- Partials        121      124       +3

Impacted Files
Coverage Δ

...tiesmanagementapi/resource/AttendanceController.kt
75.00% <0.00%> (-25.00%)
:arrow_down:

.../hmppsactivitiesmanagementapi/entity/Attendance.kt
67.67% <20.00%> (-8.80%)
:arrow_down:

...ivitiesmanagementapi/service/AttendancesService.kt
95.45% <50.00%> (-2.22%)
:arrow_down:

...gementapi/model/request/AttendanceUpdateRequest.kt
100.00% <100.00%> (ø)

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

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


[UI] Appliction Shell breaks

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When clicking on App Shell button, it will break

Expected Behavior
Should open a shell into the application container
Steps To Reproduce

https://localhost:8005/epinio/c/default/applications
on any deployed app, click the 3 dots and click App Shell

Environment
- OS:
- Architecture:
- Epinio Version:
- Cluster:
  - Provider:
  - Options:
  - Kubernetes Version:

Logs
No response
Anything else?
No response

@scures, I am not sure I can reproduce.
I am able to open App Shell on a deployed app on latest epinio-dev with v1.6.2-42-g1ed97378
https://user-images.githubusercontent.com/37271841/218987982-0ab5a804-fe54-4180-8dad-4c66adea849b.mov
Am I missing perhaps any other step?

Agree, closing and we should monitor over the next week or so.


Forgot password not working?

Forgot password function not working. This is config file:
ADMINS = ['xxxxxxxx']
EMAIL (if not using Mailgun)
CTF_NAME = 'KMA'
MAIL_SERVER = 'smtp.googlemail.com'
MAIL_PORT = 465
MAIL_USE_TLS = False
MAIL_USE_SSL = True
MAIL_USERNAME = 'xxxxxxxxx'
MAIL_PASSWORD = 'yyyyyyyyy'
What wrong? And how to fix it?
Tks!

I feel like this might have been an issue with using Google SMTP servers versus CTFd. If you can give me a stack trace or something or something else actionable I'll gladly take a look into it. Try TLS perhaps?


Provided link to configuration guide

Hey :wave:. I've been following the conversation on Product Hunt and see people don't know how to use the tool (and I experienced that myself).
The PR links to the blog post explaining how to configure it. Decided not to copy the text over to GitHub since I imagine you want people to explore your website (it's the least we can do as a thank you for this cool project!)
Thanks again.

 I don't have merge rights, so feel free to merge the PR when you're ready 👍


Correct way to detect the need to use tl.updateReleaseName

Azure DevOps Server 2020 introduced the requirement to use the special logging command to set the release name, prior to that a simple setvariable would do the trick.
In preparation of releasing:
https://github.com/jessehouwing/azure-pipelines-variable-tasks/commit/c003a638af6e2793a9818a9c9eaa2583a06cf720
How can my task know when to use the old method and when to rely on the new one?
I see that the updateReleaseName asserts the agent version, so it will throw if I call it without prior verification. Since my tasks are used in TFS 2015 all the way up to 2018 still, which won't be shipping with that agent, how can my task detect which method to use?
I could bump the major version of the task and call it quits, but that would saw confusion among my existing customers.

I'd recommend checking the agent version yourself.
let useReleaseCommand = false;
try {
  tl.assertAgent("2.165.0"); // I don't recall which agent version we shipped with 2020, this is an example
  useReleaseCommand = true;
} catch (e) { }

I think the agent supported the command before the server did, so that won't be foolproof... The service already required the command.

It looks like UpdateReleaseName was introduced here:
2.132
That's way before Azure DevOps Server shipped. Meaning that function won't work on Azure DevOps Server 2019 and below, but is required on Azure DevOps Server 2020. And it's now always needed with Azure Pipelines in the service.
Looking at the agent, there are no provisions in the agent's handling of the command to detect the server's capabilities for the command.
I could always try the command in a try/catch, and if it fails try setting the variable in by issuing a setVariable instead. But then again, so could the task lib on my behalf. I think, even if people update their agents to >2.132, this issue won't go away on Azure DevOps Server 2019 and below.

😞

@jessehouwing The set variable approach should still work to update the local job scoped variable.

I know, but my extension is available on the marketplace and can be installed on 2015 to 2020. The extension doesn't know what server it's installed on and who it talks to.
If it were a private extension, that would be no issue, I'd know the server I'd be running against, since it's mine. But the public extensions don't have that luxury.
The task lib nor the agent keep this in mind. The task lib could decode to issue the old command for backwards compact if the agent or server version is below the threshold.

Still open.

Still open.

Still open


Errore getting epg

Hello Roger,
I’m sorry but I don’t know how to contact you in other way. This is not an issue but an help request : I’m trying to call the epg with iOS shortcuts using get data from url but I got an ero or on data format that for me seem ok
In attach the screenshot of request and the error, could you kindly help me ?? Many thanks

Yep, it is 3/4 digits

Many Thanks I have found my mistake. And thank for your work for community

How close the issue ?


Trestle control ID validation regex fails on legitimate control IDs that start with a number

Describe the bug
Trestle control ID validation regex expects all control IDs to begin with a letter. It possible for control overlays to use control IDs that begin with a number.
To Reproduce
Import or validate a component that has a control id that begins with a number such as 3.1.2 in NIST 800-171 controls.
Expected behavior
Control IDS starting with a number should be acceptable.
Screenshots

Suspect code block trestle/oscal/assessment_plan.py
class SelectControlById(OscalBaseModel):
    control_id: constr(
        regex=
        r'^[_A-Za-z\u00C0-\u00D6\u00D8-\u00F6\u00F8-\u02FF\u0370-\u037D\u037F-\u1FFF\u200C-\u200D\u2070-\u218F\u2C00-\u2FEF\u3001-\uD7FF\uF900-\uFDCF\uFDF0-\uFFFD][_A-Za-z\u00C0-\u00D6\u00D8-\u00F6\u00F8-\u02FF\u0370-\u037D\u037F-\u1FFF\u200C-\u200D\u2070-\u218F\u2C00-\u2FEF\u3001-\uD7FF\uF900-\uFDCF\uFDF0-\uFFFD\-\.0-9\u00B7\u0300-\u036F\u203F-\u2040]*$'
    ) = Field(
        ...,
        alias='control-id',
        description='A reference to a control with a corresponding id value.',
        title='Control Identifier Reference',
    )
    statement_ids: Optional[List[common.StatementId]] = Field(None, alias='statement-ids')

Unfortunately, that's part of the OSCAL standard. usnistgov/OSCAL#1002 for more details.

Here I think we are explicitly constrained by OSCAL which expects id's to be NCName' objects (e.g. https://stackoverflow.com/questions/1631396/what-is-an-xsncname-type-and-when-should-it-be-used#1631480)
For us I believe this is a 'won't fix' until OSCAL update their schema.

@xee5ch @butler54 Thanks for information.


[Feature] Whether the plug-in function can be developed

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

In plan #763


Online Example with detection

It would be fine if you could have an online example. Because my ip detecting as UTC, but maybe it localhost (<IP_ADDRESS>).

I have the same problem. So I can't tell if this will work in production.

Plus one.

Spoofed my IP with curl --header "X-Forwarded-For: <<my external IP>>" localhost:8000 and a look at the response shows the correct timezone! Nice.


[docs] Fix Venafi link

What this PR does / why we need it:
Fixes the Venafi link on https://docs.cert-manager.io/en/latest/

Thanks 😄
/lgtm
/approve
/ok-to-test
/release-note-none
/cherrypick release-0.7


Add Fetches.NumRecords(), Fetches.Empty()

https://github.com/twmb/franz-go/issues/188#issuecomment-1208129136
Following pattern allocates a new slice under the hood.
if len(fetches.Records()) == 0 {
		return nil
}

Add helper methods which calculates total fetch size without allocation.
@twmb

Update on where I'm at, I'm going to try to solve #190 before preparing for the next release and merging this, but that issue has proven to be quite complicated.

This has been released in v1.7.0


Move BMFont parser code from importer to the FontData to allow loading bitmap fonts in the runtime (without importing).

Adds FontData.load_???_font functions, that were missed during font importer implementation, to load fonts directly from the file in the runtime.

Thanks!


Create Character “eurydice-coldwyn”

Automatically generated by Netlify CMS

👷 Deploy Preview for dynamic-cheesecake-5fbd8b processing.

Name
Link

🔨 Latest commit
33590ae5e12217d5cbea17513ab8f9daf077ecbe

🔍 Latest deploy log
https://app.netlify.com/sites/dynamic-cheesecake-5fbd8b/deploys/63372b46b8c72900091aadc6


Voting power warmup and cooldown

Feature description

Currently the voting power of a validator increases 2 blocks after the delegation has been processed. This open a possible attack vector if a network start with low voting power from each validator (which suppose to be more safe as not much assets are at stake), a delegator can suddenly bond relatively large amount of stake and start censorship immediately.
The same concern applies to unbonding as well. If there are two high stake delegations, one of them unbond most of the stake, the total voting power of the network drops and making the other high delegation validator have the opportunity to censor other validators.
Implementation proposal

A possible solution is to apply voting power with warmup and cooldown period. Solana has implemented this logic in delegation. The change of delegation is control by a warmup rate which is related to the total stake of the network. The delegation increase and decrease in epoch until it reaches the destination amount. This mechanism worth studying. Although we don't have epoch, we can apply this with block height.
https://docs.solana.com/cluster/stake-delegation-and-rewards#stake-warmup-cooldown-withdrawal

@kwunyeung Should we propose this to be integrated directly into the Cosmos SDK?

Never seen it in this way! I will take a look at Solana's solution

@RiccardoM I think it was mentioned somewhere sometime ago. At least I believe some validators should have similar concern on the sudden change voting power issue on Cosmos Hub. We definitely can upstream code back to the SDK but I don't want to wait for the typical ADR process in Tendermint/Cosmos-SDK. I prefer we make the changes on our requirements and propose upstreaming the code when it's stable.


Implement edit user profile request / response.

Related issues:

#306
#242
#106

Hi @saniaky,  how soon can this functionality be made available . I am in urgent need of this

Hi @techlinesolutions. As you can see, I already made a pull request with this feature. Now we need to wait for the @brunocvcunha to approve/disapprove it or you can use my branch if you need this feature right away.

Thanks for your prompt response @saniaky https://github.com/saniaky,
Kindly share the link to your branch
I kinda need it  right away
Thanks again
On Sun, Apr 28, 2019 at 7:50 PM Alexander Kohonovsky <
<EMAIL_ADDRESS>wrote:

Hi @techlinesolutions https://github.com/techlinesolutions. As you can
see, I already made a pull request with this feature. Now we need to wait
for the @brunocvcunha https://github.com/brunocvcunha to
approve/disapprove it or you can use my branch if you need this feature
right away.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/brunocvcunha/instagram4j/pull/313#issuecomment-487405640,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIX22FWJ7RAVRPY4N55HEUTPSXWWFANCNFSM4HI7BJ7Q
.

Awesome, thank you!

Hello there
I can't update the profile photo. Can you help me? I would appreciate it if you explain with examples.


Ensures Kafka callback has span in scope

Callbacks should have a span in scope so that log IDs are assigned.

cc @ImFlog @jeqo


Rename type label

There's an overly generic type label on the events output that should probably be renamed. I would suggest event or event_name.

I have added a label for 1.x release, don't want to break people dashboards if they use labels with a minor release.


ARROW-14932: [CI] Prefer mamba over conda

Mamba should provide quicker image builds compared to conda.

@github-actions crossbow submit test-conda-*

Perhaps you can also make the same changes for AppVeyor?

@github-actions crossbow submit test-conda-*

@github-actions crossbow submit test-conda-*


Key mapping on Main Menu for easy navigation

Is it possible to add j(down),k(up) to navigate options available at Main Menu prompt?

@khanchi97 - I don't know if we can assign more than one key for an action with the underlying library called tty-prompt. If so, we can do it.
If it's not possible, probably we need to introduce pry-shell.profile(similar to bash-profile) which can be edited by users to configure pry-shell the way they want.
Either case, I am a little bit busy at the moment so probably I won't be able to pick this up soon, however, any contribution is more than welcome on this :)

Turned out that tty-prompt has support to add key bindings :tada:
I've created an MR, please check out #5


Network stress test

Have OS and BMC share ethernet port, run htx network stress in OS, heavily utilize BMC network (code image uploads, REST queries, ...) and validate BMC/OS stay running, no errors, and no dropped messages

Pre-req:

[x]   System setup configuration needed
[x]   HTX network test case exerciser
[x]   Network data in case of failure ( To discuss )

Closing as this is completed..


Round the price to less decimals to prevent beancount from loading failure

The price retrieved from CoinMarketCap have more decimals than necessary for some currency. If the number is not rounded, beancount will fail to load. Though I'm not sure the precision beancount supported, I think four decimals should be sufficient for most recording purpose.

I personally track my crypto assets with 6 decimals of precision for the quantity and that seems to work fine. However, for prices I don't have any issues with tracking at 4 decimals if you find that more convenient. I have merged it.


Crash in iOS

I'm submitting a ...  (check one with "x")

[ ] question
[x] any problem or bug report

OS:  (check one with "x")

[ ] Android
[x] iOS
[ ] Browser

cordova information:  (run $> cordova plugin list)
cordova-android-firebase-gradle-release 3.0.0 "cordova-android-firebase-gradle-release"
cordova-android-play-services-gradle-release 3.0.0 "cordova-android-play-services-gradle-release"
cordova-android-support-gradle-release 3.0.1 "cordova-android-support-gradle-release"
cordova-open-native-settings 1.5.2 "Native settings"
cordova-plugin-actionsheet 2.3.3 "ActionSheet"
cordova-plugin-advanced-http 2.1.1 "Advanced HTTP plugin"
cordova-plugin-camera 4.0.3 "Camera"
cordova-plugin-core-android-extensions 2.0.0 "CoreAndroidExtensions"
cordova-plugin-device 2.0.3 "Device"
cordova-plugin-dialogs 2.0.2 "Notification"
cordova-plugin-file 6.0.1 "File"
cordova-plugin-file-transfer 1.7.1 "File Transfer"
cordova-plugin-filepath 1.5.5 "cordova-plugin-filepath"
cordova-plugin-geolocation 4.0.1 "Geolocation"
cordova-plugin-googlemaps 2.6.2 "cordova-plugin-googlemaps"
cordova-plugin-headercolor 1.0 "HeaderColor"
cordova-plugin-inappbrowser 3.0.0 "InAppBrowser"
cordova-plugin-ionic-webview 1.1.16 "cordova-plugin-ionic-webview"
cordova-plugin-localization-strings 3.1.0 "Localization"
cordova-plugin-nativeaudio 3.0.9 "Cordova Native Audio"
cordova-plugin-network-information 2.0.3-dev "Network Information"
cordova-plugin-screen-orientation 3.0.2 "Screen Orientation"
cordova-plugin-splashscreen 5.0.2 "Splashscreen"
cordova-plugin-statusbar 2.4.3 "StatusBar"
cordova-plugin-transparent-status-bar 1.0.1 "Transparent status bar"
cordova-plugin-whitelist 1.3.4 "Whitelist"
cordova-sqlite-storage 3.3.0 "Cordova sqlite storage plugin - cordova-sqlite-storage plugin version"
cordova-support-android-plugin 1.0.1 "cordova-support-android-plugin"
cordova-support-google-services 1.1.0 "cordova-support-google-services"
cordova.plugins.diagnostic 5.0.0 "Diagnostic"
es6-promise-plugin 4.2.2 "Promise"
ionic-plugin-deeplinks 1.0.20 "Ionic Deeplink Plugin"
ionic-plugin-keyboard 2.2.1 "Keyboard"
phonegap-plugin-mobile-accessibility 1.0.5-dev "Mobile Accessibility"
phonegap-plugin-multidex 1.0.0 "Multidex"
phonegap-plugin-push 2.2.3 "PushPlugin"

If you use @ionic-native/google-maps, please tell the package.json (only @ionic-native/core and @ionic-native/google-maps are fine mostly)
@ionic-native/core : 4.4.0
@ionic-native/google-maps : 4.4.2

Current behavior:
Sometimes only in one of our apps in iOS the app is crashed. And we get next error:
2019-11-13 11:45:50.662662 Joinup driver[297:8978] -[UIView mapType]: unrecognized selector sent to instance 0x102559780
2019-11-13 11:45:50.667154 Joinup driver[297:8978] Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '-[UIView mapType]: unrecognized selector sent to instance 0x102559780' First throw call stack:

([pluginViewCtrl.overlayId hasPrefix:@"panorama"] ||
([pluginViewCtrl.overlayId hasPrefix:@"map"] &&
((GMSMapView *)pluginViewCtrl.view).mapType != kGMSTypeSatellite &&

Expected behavior:
Does not crash
Related code, data or error log (please format your code or data):
We have fixed it with these commit:
https://github.com/we-are-Joinup/cordova-plugin-googlemaps/commit/3aace62aa6cd389f20c74a63e16f5678145d8417
https://github.com/we-are-Joinup/cordova-plugin-googlemaps/commit/612618c0dbde6f3b8d765847502fa03ed43621e1
We know there is not a good solution, but we don't use Satellite map or Hybrid map, so for us it is a good solution. But sometimes pluginViewCtrl.view is not a GMSMapView. It is very very strange error.

Hi!, I am a mate of @zarelint. We had update our app 2 weeks ago. And in the way we have found several bugs or details.
We had updated our apps (Android and iOS) from version 2.1.1 forked to last version forked: 2.6.2
Thanks a lot for this maravellous project! We can grow up thanks of you.
Links of our apps, if you want test or something (please move to Spain, France or Portugal):

https://play.google.com/store/apps/details?id=com.joinuptaxi.passenger&hl=es
https://apps.apple.com/es/app/joinup-pedir-y-reservar-taxi/id554668455

Thank you for debugging.
How often does this error occurred?

We have two apps, something like Uber. One for passenger and one for taxi drivers.
We get this error, only when taxi cancel a service. 1 or 2 for every 10 services the taxi driver cancel.
So, 10-20% of the cases but only in a use case

We get this error, only when taxi cancel a service.
I don't want to debug inside your app.
Please create a reproduce code, and share it on GitHub.

Please create a reproduce code, and share it on GitHub.

I understand perfectly. We can create something to reproduce them. But please, give us time...
The most of these issues have a commit to fix them :-) So, they don't need share anything and the others... we will try to have a little public project (or projects) to detect them.

Pablo, I also have users reporting crashes on IOS but I am struggling to reproduce it in the emulator or on my IPhone7. I have seen random crashes on IPhone 6 and IPhone XS but they were intermittent issues, I never got to reproduce them. Do you have any hint how to reproduce these IOS crashes? I am not sure if I understand the fix (or workaround) you are proposing in the pull request.

Hi @battika, I'm sorry but I only get this error in a use case (one of 20-30 use cases with maps). Our use case is something like this:

Enter in a page with map
Click on a button with a pop action
Crash on iOS in this use case 1 or 2 times of 10

We reproduce this in real devices and emulators. But we don't understand because only 1 or 2 times of 10 and only in this use case.
We have removed a feature for Satellite map or Hybrid map. So, how we don't use this type map we have removed this comparation. And we are happy, but we understand this is not the way.

I'm not sure this plugin catches native crash logs also, but try this one.
https://ionicframework.com/docs/native/firebase-crashlytics
At least, original Firebase Crashlytics is able to catch crashes in native side, and report it to your dashboard.


Fix for issue #307

Fairly straightforward, this adds a overriding method to greater than expressions to look for statements like (x > null) to rewrite them as x != null. Seems to address the issue of documentation (xml documents no longer have !(x <= null) as the source code).

@ndykman Before we got appveyor support, could you please confirm that all the tests are passing.
Except from that, fix looks good to me.

Can do.


[jsx] Needed PreTeXt Tags

[x] Fragments/tests
[x] Implementation as component

<abstract>

[ ] Fragments/tests
[ ] Implementation as component

<acknowledgement>

[ ] Fragments/tests
[ ] Implementation as component

<acro>

[x] Fragments/tests
[x] Implementation as component

<activity>

[ ] Fragments/tests
[ ] Implementation as component

<ad>

[x] Fragments/tests
[ ] Implementation as component

<address>

[ ] Fragments/tests
[ ] Implementation as component

<alert>

[ ] Fragments/tests
[ ] Implementation as component

<algorithm>

[ ] Fragments/tests
[ ] Implementation as component

<alteration>

[ ] Fragments/tests
[ ] Implementation as component

<am>

[x] Fragments/tests
[ ] Implementation as component

<angles>

[ ] Fragments/tests
[ ] Implementation as component

<answer>

[ ] Fragments/tests
[ ] Implementation as component

<appendix>

[ ] Fragments/tests
[ ] Implementation as component

<archive>

[ ] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

<articletitle>

[ ] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

<assemblage>

[ ] Fragments/tests
[ ] Implementation as component

<assumption>

[ ] Fragments/tests
[ ] Implementation as component

<asymptote>

[ ] Fragments/tests
[ ] Implementation as component

<asymptote-preamble>

[ ] Fragments/tests
[ ] Implementation as component

<attr>

[ ] Fragments/tests
[ ] Implementation as component

<attribution>

[ ] Fragments/tests
[ ] Implementation as component

<author>

[ ] Fragments/tests
[ ] Implementation as component

<author-biographies>

[ ] Fragments/tests
[ ] Implementation as component

<axiom>

[ ] Fragments/tests
[ ] Implementation as component

<backmatter>

[ ] Fragments/tests
[ ] Implementation as component

<bc>

[x] Fragments/tests
[ ] Implementation as component

<biblio>

[ ] Fragments/tests
[ ] Implementation as component

<biographical>

[ ] Fragments/tests
[ ] Implementation as component

<biography>

[ ] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

<book>

[ ] Fragments/tests
[ ] Implementation as component

<brandlogo>

[ ] Fragments/tests
[ ] Implementation as component

<c>

[ ] Fragments/tests
[ ] Implementation as component

<ca>

[x] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

<case>

[x] Fragments/tests
[ ] Implementation as component

<cd>

[x] Fragments/tests
[ ] Implementation as component

<cell>

[x] Fragments/tests
[ ] Implementation as component

<chapter>

[ ] Fragments/tests
[ ] Implementation as component

<chord>

[ ] Fragments/tests
[ ] Implementation as component

<claim>

[ ] Fragments/tests
[ ] Implementation as component

<cline>

[x] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

<col>

[x] Fragments/tests
[ ] Implementation as component

<colophon>

[ ] Fragments/tests
[ ] Implementation as component

<commentary>

[ ] Fragments/tests
[ ] Implementation as component

<computation>

[ ] Fragments/tests
[ ] Implementation as component

<conclusion>

[ ] Fragments/tests
[ ] Implementation as component

<conjecture>

[ ] Fragments/tests
[ ] Implementation as component

<console>

[x] Fragments/tests
[ ] Implementation as component

<contributor>

[ ] Fragments/tests
[ ] Implementation as component

<contributors>

[ ] Fragments/tests
[ ] Implementation as component

<convention>

[ ] Fragments/tests
[ ] Implementation as component

<copyright>

[x] Fragments/tests
[ ] Implementation as component

<corollary>

[ ] Fragments/tests
[ ] Implementation as component

<creator>

[ ] Fragments/tests
[ ] Implementation as component

<credit>

[ ] Fragments/tests
[ ] Implementation as component

<cross-references>

[ ] Fragments/tests
[ ] Implementation as component

<data>

[ ] Fragments/tests
[ ] Implementation as component

<date>

[x] Fragments/tests
[ ] Implementation as component

<dblbrackets>

[ ] Fragments/tests
[ ] Implementation as component

<dblprime>

[ ] Fragments/tests
[ ] Implementation as component

<dedication>

[ ] Fragments/tests
[ ] Implementation as component

<definition>

[ ] Fragments/tests
[ ] Implementation as component

<degree>

[ ] Fragments/tests
[ ] Implementation as component

<delete>

[ ] Fragments/tests
[ ] Implementation as component

<demonstration>

[ ] Fragments/tests
[ ] Implementation as component

<department>

[ ] Fragments/tests
[ ] Implementation as component

<description>

[ ] Fragments/tests
[ ] Implementation as component

<division>

[ ] Fragments/tests
[ ] Implementation as component

[x] Fragments/tests
[ ] Implementation as component

<docinfo>

[ ] Fragments/tests
[ ] Implementation as component

<doubleflat>

[ ] Fragments/tests
[ ] Implementation as component

<doublesharp>

[ ] Fragments/tests
[ ] Implementation as component

<edition>

[ ] Fragments/tests
[ ] Implementation as component

<editor>

[ ] Fragments/tests
[ ] Implementation as component

<eg>

[x] Fragments/tests
[ ] Implementation as component

<ellipsis>

[x] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

<email>

[ ] Fragments/tests
[ ] Implementation as component

<entity>

[ ] Fragments/tests
[ ] Implementation as component

<etal>

[x] Fragments/tests
[ ] Implementation as component

<etc>

[ ] Fragments/tests
[ ] Implementation as component

<example>

[ ] Fragments/tests
[ ] Implementation as component

<exercise>

[ ] Fragments/tests
[ ] Implementation as component

<exercisegroup>

[ ] Fragments/tests
[ ] Implementation as component

<exercises>

[ ] Fragments/tests
[ ] Implementation as component

<exploration>

[ ] Fragments/tests
[ ] Implementation as component

<fact>

[ ] Fragments/tests
[ ] Implementation as component

<feedback>

[ ] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

<fillin>

[ ] Fragments/tests
[ ] Implementation as component

<flat>

[ ] Fragments/tests
[ ] Implementation as component

<fn>

[ ] Fragments/tests
[ ] Implementation as component

<foreign>

[ ] Fragments/tests
[ ] Implementation as component

<fragment>

[ ] Fragments/tests
[ ] Implementation as component

<fragref>

[ ] Fragments/tests
[ ] Implementation as component

<frontmatter>

[ ] Fragments/tests
[ ] Implementation as component

<genus>

[ ] Fragments/tests
[ ] Implementation as component

<gi>

[ ] Fragments/tests
[ ] Implementation as component

<glossary>

[ ] Fragments/tests
[ ] Implementation as component

<h>

[ ] Fragments/tests
[ ] Implementation as component

<headnote>

[ ] Fragments/tests
[ ] Implementation as component

<heuristic>

[ ] Fragments/tests
[ ] Implementation as component

<hint>

[ ] Fragments/tests
[ ] Implementation as component

<historical>

[ ] Fragments/tests
[ ] Implementation as component

<holder>

[ ] Fragments/tests
[ ] Implementation as component

<hypothesis>

[ ] Fragments/tests
[ ] Implementation as component

<ibid>

[ ] Fragments/tests
[ ] Implementation as component

<icon>

[ ] Fragments/tests
[ ] Implementation as component

<identity>

[ ] Fragments/tests
[ ] Implementation as component

<idx>

[ ] Fragments/tests
[ ] Implementation as component

<ie>

[x] Fragments/tests
[ ] Implementation as component

<image>

[ ] Fragments/tests
[ ] Implementation as component

<images>

[ ] Fragments/tests
[ ] Implementation as component

<index>

[ ] Fragments/tests
[ ] Implementation as component

<index-list>

[ ] Fragments/tests
[ ] Implementation as component

<init>

[x] Fragments/tests
[x] Implementation as component

<initialism>

[ ] Fragments/tests
[ ] Implementation as component

<input>

[ ] Fragments/tests
[ ] Implementation as component

<insert>

[ ] Fragments/tests
[ ] Implementation as component

<insight>

[ ] Fragments/tests
[ ] Implementation as component

<institution>

[ ] Fragments/tests
[ ] Implementation as component

<instruction>

[ ] Fragments/tests
[ ] Implementation as component

<intertext>

[ ] Fragments/tests
[ ] Implementation as component

<introduction>

[ ] Fragments/tests
[ ] Implementation as component

<investigation>

[ ] Fragments/tests
[ ] Implementation as component

<journal>

[ ] Fragments/tests
[ ] Implementation as component

[x] Fragments/tests
[ ] Implementation as component

<langle>

[ ] Fragments/tests
[ ] Implementation as component

<latex>

[x] Fragments/tests
[ ] Implementation as component

<latex-image>

[ ] Fragments/tests
[ ] Implementation as component

<latex-image-preamble>

[ ] Fragments/tests
[ ] Implementation as component

<latex-preamble>

[ ] Fragments/tests
[ ] Implementation as component

<lemma>

[ ] Fragments/tests
[ ] Implementation as component

<letter>

[ ] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

<line>

[ ] Fragments/tests
[ ] Implementation as component

<list>

[ ] Fragments/tests
[ ] Implementation as component

<list-of>

[ ] Fragments/tests
[ ] Implementation as component

<listing>

[ ] Fragments/tests
[ ] Implementation as component

<location>

[ ] Fragments/tests
[ ] Implementation as component

<lq>

[ ] Fragments/tests
[ ] Implementation as component

<lsq>

[ ] Fragments/tests
[ ] Implementation as component

<m>

[ ] Fragments/tests
[ ] Implementation as component

<macro-file>

[ ] Fragments/tests
[ ] Implementation as component

<macros>

[ ] Fragments/tests
[ ] Implementation as component

<mag>

[x] Fragments/tests
[ ] Implementation as component

<md>

[ ] Fragments/tests
[ ] Implementation as component

<mdash>

[x] Fragments/tests
[ ] Implementation as component

<mdn>

[ ] Fragments/tests
[ ] Implementation as component

<me>

[ ] Fragments/tests
[ ] Implementation as component

<memo>

[ ] Fragments/tests
[ ] Implementation as component

<men>

[ ] Fragments/tests
[ ] Implementation as component

<midpoint>

[x] Fragments/tests
[ ] Implementation as component

<minilicense>

[ ] Fragments/tests
[ ] Implementation as component

<minus>

[x] Fragments/tests
[ ] Implementation as component

<mrow>

[ ] Fragments/tests
[ ] Implementation as component

<n>

[ ] Fragments/tests
[ ] Implementation as component

<name>

[ ] Fragments/tests
[ ] Implementation as component

<natural>

[ ] Fragments/tests
[ ] Implementation as component

<nb>

[x] Fragments/tests
[ ] Implementation as component

<nbsp>

[x] Fragments/tests
[ ] Implementation as component

<ndash>

[x] Fragments/tests
[ ] Implementation as component

<notation>

[ ] Fragments/tests
[ ] Implementation as component

<notation-list>

[ ] Fragments/tests
[ ] Implementation as component

<note>

[ ] Fragments/tests
[ ] Implementation as component

<number>

[ ] Fragments/tests
[ ] Implementation as component

<numbering>

[ ] Fragments/tests
[ ] Implementation as component

<obelus>

[x] Fragments/tests
[ ] Implementation as component

<objectives>

[ ] Fragments/tests
[ ] Implementation as component

<observation>

[ ] Fragments/tests
[ ] Implementation as component

[x] Fragments/tests
[ ] Implementation as component

<outcomes>

[ ] Fragments/tests
[ ] Implementation as component

<output>

[x] Fragments/tests
[ ] Implementation as component

[x] Fragments/tests
[ ] Implementation as component

<package>

[ ] Fragments/tests
[ ] Implementation as component

<pages>

[ ] Fragments/tests
[ ] Implementation as component

<paragraphs>

[ ] Fragments/tests
[ ] Implementation as component

<part>

[ ] Fragments/tests
[ ] Implementation as component

<per>

[ ] Fragments/tests
[ ] Implementation as component

<permille>

[x] Fragments/tests
[ ] Implementation as component

<personname>

[ ] Fragments/tests
[ ] Implementation as component

<pg-code>

[ ] Fragments/tests
[ ] Implementation as component

<pg-macros>

[ ] Fragments/tests
[ ] Implementation as component

<phonomark>

[x] Fragments/tests
[ ] Implementation as component

<pilcrow>

[x] Fragments/tests
[ ] Implementation as component

<plaintitle>

[ ] Fragments/tests
[ ] Implementation as component

<plusminus>

[x] Fragments/tests
[ ] Implementation as component

<pm>

[x] Fragments/tests
[ ] Implementation as component

<poem>

[ ] Fragments/tests
[ ] Implementation as component

<postlude>

[ ] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

<preface>

[ ] Fragments/tests
[ ] Implementation as component

<prelude>

[ ] Fragments/tests
[ ] Implementation as component

<pretext>

[ ] Fragments/tests
[ ] Implementation as component

<prime>

[ ] Fragments/tests
[ ] Implementation as component

<principle>

[ ] Fragments/tests
[ ] Implementation as component

<problem>

[ ] Fragments/tests
[ ] Implementation as component

<program>

[ ] Fragments/tests
[ ] Implementation as component

<project>

[ ] Fragments/tests
[ ] Implementation as component

<prompt>

[ ] Fragments/tests
[ ] Implementation as component

<proof>

[ ] Fragments/tests
[ ] Implementation as component

<proposition>

[ ] Fragments/tests
[ ] Implementation as component

<ps>

[x] Fragments/tests
[ ] Implementation as component

<publisher>

[ ] Fragments/tests
[ ] Implementation as component

<pubtitle>

[ ] Fragments/tests
[ ] Implementation as component

<q>

[ ] Fragments/tests
[ ] Implementation as component

<quantity>

[x] Fragments/tests
[ ] Implementation as component

<question>

[ ] Fragments/tests
[ ] Implementation as component

<rangle>

[ ] Fragments/tests
[ ] Implementation as component

<reading-questions>

[ ] Fragments/tests
[ ] Implementation as component

<references>

[ ] Fragments/tests
[ ] Implementation as component

<registered>

[x] Fragments/tests
[ ] Implementation as component

<remark>

[ ] Fragments/tests
[ ] Implementation as component

<rename>

[ ] Fragments/tests
[ ] Implementation as component

<role>

[ ] Fragments/tests
[ ] Implementation as component

<row>

[x] Fragments/tests
[ ] Implementation as component

<rq>

[ ] Fragments/tests
[ ] Implementation as component

<rsq>

[ ] Fragments/tests
[ ] Implementation as component

<sage>

[ ] Fragments/tests
[ ] Implementation as component

<sageplot>

[ ] Fragments/tests
[ ] Implementation as component

<sbsgroup>

[ ] Fragments/tests
[ ] Implementation as component

<scaledeg>

[ ] Fragments/tests
[ ] Implementation as component

<score>

[ ] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

[x] Fragments/tests
[ ] Implementation as component

<see>

[ ] Fragments/tests
[ ] Implementation as component

<seealso>

[ ] Fragments/tests
[ ] Implementation as component

<series>

[ ] Fragments/tests
[ ] Implementation as component

<servicemark>

[x] Fragments/tests
[ ] Implementation as component

<sharp>

[ ] Fragments/tests
[ ] Implementation as component

<shortlicense>

[ ] Fragments/tests
[ ] Implementation as component

<shorttitle>

[ ] Fragments/tests
[ ] Implementation as component

<sidebyside>

[ ] Fragments/tests
[ ] Implementation as component

<solidus>

[x] Fragments/tests
[ ] Implementation as component

<solution>

[ ] Fragments/tests
[ ] Implementation as component

<solutions>

[ ] Fragments/tests
[ ] Implementation as component

<species>

[ ] Fragments/tests
[ ] Implementation as component

<sq>

[ ] Fragments/tests
[ ] Implementation as component

<stack>

[ ] Fragments/tests
[ ] Implementation as component

<stale>

[ ] Fragments/tests
[ ] Implementation as component

<stanza>

[ ] Fragments/tests
[ ] Implementation as component

<statement>

[ ] Fragments/tests
[ ] Implementation as component

<subexercises>

[ ] Fragments/tests
[ ] Implementation as component

<subsection>

[ ] Fragments/tests
[ ] Implementation as component

<subsubsection>

[ ] Fragments/tests
[ ] Implementation as component

<subtitle>

[ ] Fragments/tests
[ ] Implementation as component

<swungdash>

[x] Fragments/tests
[ ] Implementation as component

[ ] Fragments/tests
[ ] Implementation as component

<tabular>

[x] Fragments/tests
[ ] Implementation as component

<tag>

[ ] Fragments/tests
[ ] Implementation as component

<tage>

[ ] Fragments/tests
[ ] Implementation as component

<task>

[ ] Fragments/tests
[ ] Implementation as component

<taxon>

[ ] Fragments/tests
[ ] Implementation as component

<technology>

[ ] Fragments/tests
[ ] Implementation as component

<term>

[ ] Fragments/tests
[ ] Implementation as component

<tex>

[x] Fragments/tests
[ ] Implementation as component

<theorem>

[ ] Fragments/tests
[ ] Implementation as component

<timeofday>

[ ] Fragments/tests
[ ] Implementation as component

<times>

[ ] Fragments/tests
[ ] Implementation as component

<timesignature>

[ ] Fragments/tests
[ ] Implementation as component

<title>

[ ] Fragments/tests
[ ] Implementation as component

<titlepage>

[ ] Fragments/tests
[ ] Implementation as component

<today>

[ ] Fragments/tests
[ ] Implementation as component

<trademark>

[ ] Fragments/tests
[ ] Implementation as component

[x] Fragments/tests
[ ] Implementation as component

<unit>

[x] Fragments/tests
[ ] Implementation as component

<url>

[x] Fragments/tests
[ ] Implementation as component

<usage>

[ ] Fragments/tests
[ ] Implementation as component

<var>

[ ] Fragments/tests
[ ] Implementation as component

<video>

[ ] Fragments/tests
[ ] Implementation as component

<viz>

[x] Fragments/tests
[ ] Implementation as component

<volume>

[ ] Fragments/tests
[ ] Implementation as component

<vs>

[x] Fragments/tests
[ ] Implementation as component

<warning>

[ ] Fragments/tests
[ ] Implementation as component

<website>

[ ] Fragments/tests
[ ] Implementation as component

<webwork>

[ ] Fragments/tests
[ ] Implementation as component

<xelatex>

[ ] Fragments/tests
[ ] Implementation as component

<xetex>

[ ] Fragments/tests
[ ] Implementation as component

<xref>

[ ] Fragments/tests
[ ] Implementation as component

<year>

[ ] Fragments/tests
[ ] Implementation as component

Frequency of tag occurance, courtesy of Brad:
<m> 35192

 25572
<c> 12248
<cell> 10342

 10255
<statement> 5133
<title> 4064
<exercise> 3940
<input> 2743
<row> 2736

 2585
<term> 2542
 2301
<mrow> 2153
<program> 2057
<h> 1846
<idx> 1612
<me> 1600
<image> 1532
<sidebyside> 1438
<var> 1267
<answer> 1204
<description> 1134
<xref> 1107
<q> 1026
<subsection> 1016
<md> 935
<solution> 805
<xi:include> 717
<sage> 710
<introduction> 665
<output> 663
<feedback> 642
<choice> 628
<tabular> 621

 601
<example> 556
<mdash/> 514
<latex-image> 480

 478
<webwork> 461
<pg-code> 461

 451
<exercisegroup> 353
<nbsp/> 343
<principle> 299
<ndash/> 254
<hint> 249

 239
<gi> 221
<proof> 210
<col/> 206
<col> 201
 190
<assemblage> 188
<line> 183
<choices> 177
<exercises> 161
<acro> 151
<subexercises> 144

 144
<theorem> 136

 133
<cline> 133
<note> 129
<url> 119
<biblio> 117
<notation> 100
<usage> 100
<title_reference> 94

 91
<paragraphs> 83
<chapter> 78
<book> 70
<cell/> 69
<mathbook> 66
<block> 63
<warning> 59
<instruction> 59
<stack> 58
<proposition> 55
<conclusion> 54
<substitute> 50


Add flat_settings parameter to /_cluster/settings

This output becomes a lot more readable to a human and potentially easier to search when flat_settings is specified.

I just use the flatten json plugin for atom.io. You can flatten and unflatten no problem.


hashid issue

Hi
We use Laravel 5.7 and "vinkla/hashids": "^5.1"
I added hashid in my model
class Listing extends Model {
use Hashidable;
protected $appends = ['hashid'];
public function getHashidAttribute() {
return \Vinkla\Hashids\Facades\Hashids::encode($this->attributes['id']);
}
In blade  I try to use href="{{ route('listings.detail', $listing->hashid) }}"
But I get this error :
Undefined property: stdClass::$hashid (View: E:\Walky\walky\resources\views\listings\index.blade.php)
Any idea ?
Thanks

Not sure. Try clearing the view cache.


Handle backticks before decoding JSON

Since LLM models often do not remove backticks in their suggesting responses, particularly with smaller models, I have implemented backtick handling in the code. Please let me know your thoughts.

Very helpful! Thank you!


Reduce unnecessary asserts

We need to define where to use asserts and where to omit them. For example, asserting every parameter to every method as not null may be unnecessary.

Official java guide on assertions: http://docs.oracle.com/javase/8/docs/technotes/guides/language/assert.html
In particular, I found this interesting:

Do not use assertions for argument checking in public methods.
Argument checking is typically part of the published specifications (or contract) of a method, and these specifications must be obeyed whether assertions are enabled or disabled. Another problem with using assertions for argument checking is that erroneous arguments should result in an appropriate runtime exception (such as IllegalArgumentException, IndexOutOfBoundsException, or NullPointerException). An assertion failure will not throw an appropriate exception.

which hints that we should not be doing assert someArgument != null; in our public methods, but rather throwing NullPointerException instead.

@pyokagan

Argument checking is typically part of the published specifications (or contract) of a method, and these specifications must be obeyed whether assertions are enabled or disabled.

In practice, are we able to do proper argument checking in all public methods? It's one thing to check arguments to a really public API such as a component API (e.g. Model, Storage) but argument checking in all public methods in classes inside a component can be messy. So in practice, we could end up not doing any argument checking at all in those classes which is worse than using asserts?.

I've done some research on this and found out Google Guava's Preconditions
The nice thing about Preconditions is that it will throw the necessary exceptions like NullPointerException for null checks (instead of a very generic assertion failure) and its method names like checkNotNull makes it very clear what we are trying to do.
As an added bonus, checkNotNull (and any other methods in the Preconditions package) will return the validated value if it is not null so we can always do something like this
public void fooMethod(Foo args) {
    return Bar(checkNotNull(args))
}

This ensures that the args passed to Bar() is not null - if it is then a NullPointerException is thrown. This is compliant with the official java guide for assertions (that is to throw a null pointer for null values) without having to mess the code up too much.

Related PR https://github.com/oss-generic/process/pull/38


docs: fix architecture doc link

Signed-off-by: Tiexin Guo<EMAIL_ADDRESS>Description
Thanks @SuperAayush, for raising this issue: https://github.com/devstream-io/devstream/issues/1256
The link "https://docs.devstream.io/en/latest/development/architecture/" is mentioned in a few places, so changing it would cause readers some confusion.
Related Issues
Solves https://github.com/devstream-io/devstream/issues/1256.

Tested locally, link checker passed. Merging now.


make "annotation constructors" actual constructors

[@gavinking] Now that we have the notion of a constructor, and they happen to have lowercase names, it would make more sense if annotation constructors were constructors.
shared final annotation class Doc {
    shared String text;
    shared new doc(String text) {
        this.text = text;
    }
}

The only thing that doesn't quite fit here is that it looks like you would have to import the doc annotation like this:
import ceylon.language { Doc { doc } }

That would be quite inconvenient, and not backward compatible. So we would need to have a special rule that says you can import an annotation constructor like this:
import ceylon.language { doc }

I don't think that's too offensive a notion.
[Migrated from ceylon/ceylon-spec#1428]

Somewhat related to this issue: annotation types look like a lot like value types defined in #6188, together with some additional restrictions. So when we get to this issue, I think we should say that annotation types are structures, and annotation constructors are their constructors.


Support Objective-C

Closing out this issue as Conche is deprecated for the Swift Package Manager (SPM). Instead you can use SPM (https://github.com/Conche/Conche/commit/78708a9556b00d602de4c3e518a7f201b55a519b).

😢


istiod: improve error message when values.yaml is invalid

Fixes https://github.com/istio/istio/issues/51071
Not ideal fix, longer term is in https://github.com/istio/istio/issues/48991

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

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
5ab5c187312d3dd22ffb9e9327caa392becfbc39
link
true
/test unit-tests-arm64

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
5ab5c187312d3dd22ffb9e9327caa392becfbc39
link
true
/test unit-tests-arm64

gencheck_istio
5ab5c187312d3dd22ffb9e9327caa392becfbc39
link
true
/test gencheck

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
5ab5c187312d3dd22ffb9e9327caa392becfbc39
link
true
/test unit-tests-arm64

unit-tests_istio
5ab5c187312d3dd22ffb9e9327caa392becfbc39
link
true
/test unit-tests

gencheck_istio
52daf1eceba1cc398a25ba2fc4b0afcb31c73fdc
link
true
/test gencheck

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

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

Test name
Commit
Details
Required
Rerun command

unit-tests-arm64_istio
5ab5c187312d3dd22ffb9e9327caa392becfbc39
link
true
/test unit-tests-arm64

unit-tests_istio
5ab5c187312d3dd22ffb9e9327caa392becfbc39
link
true
/test unit-tests

gencheck_istio
52daf1eceba1cc398a25ba2fc4b0afcb31c73fdc
link
true
/test gencheck

lint_istio
52daf1eceba1cc398a25ba2fc4b0afcb31c73fdc
link
true
/test lint

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


Add new module: Time

https://github.com/the-vision/jarvis-telegram/wiki

Please assign it to me. I am a GSSOC'20 participate

@darkmatter18 Go ahead and see about core also when the core issue


Fixes #16192: Extracted getCacheKey() protected method from queryInternal() protected method

Q
A

Is bugfix?
no

New feature?
no

Breaks BC?
no

Tests pass?
yes

Fixed issues
#16192

Merged. Thanks!


Tooltips on IOS PWA don't appear

Describe the bug
Tooltips don't show on IOS PWA, but work fine on Safari. Usually to trigger a tooltip on mobile browser you have to tap and then it'll appear, this however doesn't seem to work when trying via a PWA on IOS. To reiterate, everything works as intended on Safari, just not their pwa webview.
To Reproduce
Click to view tooltip on ios pwa
Steps to reproduce the behavior:
Install app as a pwa on ios (add to homescreen)
Attempt to view a tooltip
Expected behavior
Tooltip should appear like it does on chrome / safari
Context:

OS: iOS
Browser: PWA WebView (Safari?)

Do you have a repo to test? Does it work if you add a mouseenter and focus listener manually, instead of useHover?
useEffect(() => {
  refs.domReference.current.addEventListener('mouseenter', () => {
    setOpen(true);
  });
  // + `focus`
}, []);

Just made a quick Vite React repo with vite-plugin-pwa and deployed to Netlify, added to iOS (16.3) homescreen. The floating element shows when tapping the reference element as expected (v0.22.2).
There may be some other code you have causing an issue, and without a reproduction, this ticket isn't actionable atm.
https://user-images.githubusercontent.com/22450188/229262557-c798dda0-0270-4252-aff5-5b010f540551.MP4

  View config and App.jsx

import { defineConfig } from "vite";
import react from "@vitejs/plugin-react";
import { VitePWA } from "vite-plugin-pwa";

// https://vitejs.dev/config/
export default defineConfig({
  plugins: [react(), VitePWA()],
  server: {
    host: true,
  },
});

import { useState } from "react";
import reactLogo from "./assets/react.svg";
import viteLogo from "/vite.svg";
import "./App.css";
import { useFloating, useHover, useInteractions } from "@floating-ui/react";

function App() {
  const [isOpen, setIsOpen] = useState(false);

  const { x, y, refs, context } = useFloating({
    open: isOpen,
    onOpenChange: setIsOpen,
  });

  const hover = useHover(context);
  const interactions = useInteractions([hover]);

  return (

Vite + React

          Reference

        {isOpen && (

            Floating

        )}

          Edit src/App.jsx and save to test HMR

        Click on the Vite and React logos to learn more

  );
}

export default App;

I also added all the other relevant hooks (dismiss, focus, etc), and disabled move in useHover and it continues to work fine.
What might be the problem, I noticed, is that pointerdown dismissal (e.g. when touch-moving to scroll) won't allow mouseenter to fire again unless you explicitly tapped somewhere else. In this case, you can change outsidePressEvent: 'mousedown' in the useDismiss hook so the tooltip won't close unless there was an intentional tap to begin with. But it still works fine on the first open.


Config exists API endpoint

What does this PR do?
Added a config/exists API to return if a config exists, same as get config but without any data being returned.
Type of change

[ ] New feature (non-breaking change which adds functionality)
[ ] This change requires a documentation update

How should this be tested?

[ ] Unit Tests

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code and corrected any misspellings
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes

LGTM


Regression: intersection of a generic type bound to a discriminated union with one of the union constituencies reduces to never

TypeScript Version:  3.9.2
Search Terms: Generic union intersection
Code
interface A {
  kind: "A";
  a: number;
}

interface B {
  kind: "B";
  b: number;
}

declare const shouldBeB: (A | B) & B;
const b: B = shouldBeB; // works

function inGeneric<T extends A | B>(alsoShouldBeB: T & B) {
  const b: B = alsoShouldBeB;
  //    ~ TS2739: Type 'T & B' is missing the following properties from type 'B': kind, b
}

Expected behavior:
No errors (were no errors on 3.8)
Actual behavior:
TS2739: Type 'T & B' is missing the following properties from type 'B': kind, b

Playground Link: link
Related Issues:
It seems to be related to #36696

This is basically a duplicate of #38542, but the repro is simpler here.

This is basically a duplicate of #38542, but the repro is simpler here.

I saw it and couldn't recognize whether it was the same issue or not.

I had some similar problems at the intersection of properties with different values:
type T01 = { a: "a" } & { a: "b" }; // never, expects { a: "a"|"b" }
type T02 = { a: "a" } & { a: null }; // never, expects { a: "a"|null }
type T04 = { a: "a" } & { a: undefined }; // never, expects { a: "a"|undefined }
type T03 = { a: string } & { a: null }; // never, expects { a: string|null }
type T05 = { a: string } & { a: undefined }; // never, expects { a: string|undefined }
type T06 = { a?: string } & { a: undefined }; // { a: undefined }, { a?: string|undefined }

Does this issue cover that too?


Blackboard selection session is broken in new UI

Describe the bug
The final call to ltireturn.do (generally Blackboard) in a selection session loses it's parameters, thus keeping the user in oEQ and not creating the LTI link in the calling LTI consumer (Blackboard).
To Reproduce
Steps to reproduce the behavior:

Setting an LTI Tool Provider for oEQ in Bb
In Blackboard, access the 'Build content' > oEQ LTI launch
Select a piece of content
Return the selection
Note how you get a relatively blank oEQ page and the link isn't created in Bb

Expected behavior
The link should be created in Bb and either the selection session should disappear or a notification appear that the link was created
Screenshots

Platform:

OpenEquella Version: 2020.1.0
Browser: Confirmed in Chrome and Firefox

Additional context
Switching to the old UI allows the Bb selection session to work.
No errors are thrown in the logs

Heya @cbeach47
As per @SammyIsConfused 's comment over in the PR for Hotfix 2020.1.2 (#1738), we possibly have a fix in this which we needed to do for Canvas (#1744). If you're able to test against Bb that'd be great. :+1:

Cool, I'll take a look Tuesday / Wednesday of next week

Once the PR for Hotfix 2020.1.2 ( #1738 ) is complete and merged up into develop, this should be resolved.  Testing notes in the #1738 comments.  Leaving in 'Ready for Testing' until then.


update to space v2 api

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

12 of 12 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+1.9%) to 97.778%

Totals

Change from base Build<PHONE_NUMBER>:
1.9%

Covered Lines:
118

Relevant Lines:
119

💛  - Coveralls


As a Product Owner I would like to have  all React Components needed to style our EDS Store Front.

[x] Identify the components needed (equinor/design-system#106)
[ ] Create Github Issues for these components
[ ] Create the React Components
[ ] Use the components to style EDS Store Front

outdated as storefront is deprecated


Choose side when spinning

Could be useful to choose side when the robot is spinning on hitself.
eg: go to 20° to 60° turning in the negative side.

Resolved in #56
To choose spinning side, and not the shortest angle, do a relative movement, and not a global movement (see "setTarget()" function)


Dynamic Field creation

Is there a way to compile a dynamically built html template that customizes the aa-field attribute?
We have various JSON data layouts and need display / edit forms.
We're using ui-router.  Thx!

Hey, you should be able to do this with the $injector that is provided to you as part of the method signature. Example here: https://github.com/AngularAgility/AngularAgility/blob/master/src/formExtensions/provider.js#L32
Let me know if that doesn't work and I can try to add something/ re-open the issue. Thanks!


Add SMP option to nix, enable SMP for selected tests, add ccache option for tests.

test.sh: Add env var to enable ccache, default to off.
Add smp parameter to nix default, shell, and overlay. Enable with --arg smp true.
Added multiple cores to paging, UDP and exceptions tests, add them to an SMP test set.
Enable boot logger to tests make it easier toverify that multiple cores come up.
Disable SMP for chainloader. It would be nice to test 32 bit multicore, but not in there.

Looks great - thanks for the rebase :)


Nodejs debugging problems

Hi, my current working project are using bazel. the project is using nodejs_binary as the entry point, thing is I can click the green run button in intellij to use bazel to start the program, but the debug button is disabled, is there any way to enable debugging or it just don't support nodejs debug yet?

There's no support for nodejs in the plugin, and no plans to add it unfortunately.


feat: Add nat gateway ips in the module output

Description
This adds the public ips of the nat gateways created to the output of the module, which can be used somewhere else in the terraform config like setting up ingress rules.

Thanks for the PR, @ynaim94 .
No need to change the README in the autogenerated part, just providing the description in the .tf file would have been sufficient.
But all good, we will take care of it and also fix the doc generation itself (probably move it to the release build).

Hi @ynaim94 , can you rebase or recreate your PR please without making any changes to the README file?

Working on it... need to get the GitHub workflows straight.


[Docs] Fix typo on filter name

Hi everyone!
I was studying Jinja and Flask with @JefersonViana , and noticed a typo in the docs about custom filters.
I hope there is no need for creating an issue for this.
Let me know if you think that there is a better solution.

The typo would be in the use, not the registration. Always prefer separated words, so |datetime_filter. (Yes, "datetime" itself doesn't follow this, but it's the built-in name.)

Be sure to make docs fixes against the latest feature branch (3.1.x) rather than main so that it gets into the current docs. You'll need to rebase and force push to fix that:
$ git rebase --onto origin/3.0.x origin/main
$ git push -f

Be sure to make docs fixes against the latest feature branch (3.1.x)

Thanks @davidism ! I did not pay attention to that, sorry. Done ✅

The typo would be in the use, not the registration. Always prefer separated words, so |datetime_filter. (Yes, "datetime" itself doesn't follow this, but it's the built-in name.)

I also prefer naming separating words with _, but I think it is better if the filter function and the register in environment.filters have different names. Someone (mainly beginners) may wonder

"is it necessary to keep the same name?"
or even "which should be used inside the template? the function's name or the string registered in environment.filters"

What if we rename the datetime_format function to datetime_format_filter, and keep the filter's name as datetime_format?

datetime_format everywhere please.

datetime_format everywhere please.

@davidism done ✅

The pre-commit.ci failure has nothing to do with my changes, right? Do I need to do something about it?


Production integrator key returning 0 login accounts

My integrator key was working fine in demo environment and I managed to shift the key to production successfully. (When I go to production admin console, the key is listed under APIs and Keys section)
Problem is when I try to create the apiClient object with the production properties, I get an IndexOutOfBoundsException since loginInfo.getLoginAccounts() collection is empty. I use the service integration code segment which has given in the ReadMe of java sdk repository.
`AuthenticationApi authApi = new AuthenticationApi();
LoginInformation loginInfo = authApi.login();
    // parse first account ID (user might belong to multiple accounts) and baseUrl
    String accountBaseUrl = loginInfo.getLoginAccounts().get(0).getBaseUrl();
    String[] accountDomain = accountBaseUrl.split("/v2");`

Any idea to resolve this issue? I am days behind to go live my project. So appreciate a quick response on this. Thanks

Sorry for the extremely slow response. Good news is that we have re-organized to provide better response times to issues. I will close this ticket since it is old and there has been no recent activity on it. If the issue is still current, please re-open. Thank you, Larry


Remove automatic connection to AWS service on import

@jdrake
When using .get, the second argument is always evaluated, even if it doesn't get assigned. This means that whenever this module is imported, we will attempt to establish a connection.
I noticed this when my internet died and I got a connection error trying to run unit tests in some code that had this as a distantly nested dependency somewhere. This change makes it so that if you do have the AWS_ACCOUNT_ID env var set, that doesn't happen.

LGTM after tests pass

Tests failed!

@jdrake tests fail here, but they fail the same way on master, so I think there is some CCI configuration that is wrong, rather than this PR?

(See eg https://github.com/NarrativeScience/sfn-workflow-client/pull/7 which is just an empty commit off of master)

Yup, probably from the aws account migration. I'll update the project settings and retest.

Also in preparation for a new release, bump the version in __init__.py

@jdrake updated


Add global signal handler for Interrupt signal

What type of PR is this?
/kind bug
/sig node
What this PR does / why we need it:
Fixes ctrl+c not working on "logs" command.
Switch to the global signal handler in "port-forward" command.
Which issue(s) this PR fixes:
Fixes #673
Special notes for your reviewer:
This PR also introduces a global Interrupt signal handling mechanism for long-running commands.
When programmer calls SetupInterruptSignalHandler(), a global read-only stopCh is returned.
Behind the scene:

It setups a global signal handler monitoring Interrupt signals.
The stopCh will be closed when Interrupt signal received.
The current program exits immediately on receiving the Interrupt signal twice.
No behavior change if SetupInterruptSignalHandler() is not called.

Does this PR introduce a user-facing change?
crictl logs command now can be stopped with Ctrl+C

Just new to crictl, remind me if I am missing other long-running commands which also require signal handling.

/cc @feiskyer @saschagrunert

/auto-cc


JavaScript heap out of memory

 Environment data

Language Server version: 2021.6.0 (also fails on 2021.6.1)
OS and version: win32 x64
Python version (and distribution if applicable, e.g. Anaconda): 3.8.8; with Anaconda
python.analysis.indexing: undefined
python.analysis.typeCheckingMode: off

 Expected behaviour
No crashes
 Actual behaviour
The server crashes with the error FATAL ERROR: invalid array length Allocation failed - JavaScript heap out of memory.
Logs are attached below.
 Logs

Python Language Server Log
 Code Snippet / Additional information

Because my project is so large (over 11k line written by me and just under 5 million autogenerated by Qt) and is proprietary, I can't provide code that would help. So instead, I will try to give you a description of the project:

The project's primary dependencies include: PyQt5, opencv, numpy, pillow, loguru, and a couple other smaller ones.
The project is well over 11k lines with nearly 5 million extra being auto-generated by PyQt's pyrcc5 utility (images, gifs, etc). That file is basically bytecode, but is a python file. It is required that I load it in at the launch of the application, but I seldom open it in VS Code. This file I expect to be the culprit. I can upload if it is asked for.
The language server only fails with this project. I have other, smaller projects that do not encounter this issue.

This file is 335.6MB in size and has 4.9M lines.

My bad! I meant MB not KB lol
But excellent. Thanks for putting in the PR. I wonder if there should be some sort of notification from VS Code noting that the file size limit was exceeded? That would be preferable to nothing at all. I can open an issue there for that if you think it would be worth the time?
Thanks again

This file is 335.6MB in size and has 4.9M lines.
My bad! I meant MB not KB lol
But excellent. Thanks for putting in the PR.

This issue has been fixed in version 2021.6.2, which we've just released. You can find the changelog here: https://github.com/microsoft/pylance-release/blob/main/CHANGELOG.md#202162-16-june-2021

Can confirm this has been fixed; thanks a ton for doing so. Pylance is so much more polished that Jedi.


Add external-module-format.md

Does this flow better?

Looks good, just some grammar and nitpicks.

Added my 2 cents.  Overall it's pretty good!

Thank you for all the input. I agree to them all and will update accordingly.

Please ignore last commit. Still re-writing.


Preprocess/postprocess should support generators

As a follow up to #1107 the preprocess and postprocess functions for middleware should also support generators

Will revisit when we start the middleware project.


can we replace the default summary ?

Hello , thank you for the project , it's amazing you saved us alot of time
I saw that in the project the default summary is   private readonly defaultRunName = [${new Date().toUTCString()}] - Automated run;
i add my own summary like this  [       'playwright-xray',       {         jira: {           url: 'https://waykonect.atlassian.net',           type: 'cloud',           apiVersion: '1.0',         },         cloud: {           client_id: clientId,           client_secret: clientSecret,         },         summary: [${new Date().toLocaleString('fr-FR', { timeZone: 'Europe/Paris' })}] - Automated ,         projectKey: projectKey,         testPlan: testPlan,         debug: false,         testEnvironments: process.env.ENV,       }, but when i test , it always take the default summary name

Added summary option in playwright.config.ts

cool, waiting for the next release ^^ thanks

@Niklas-Back  Hello again is it possible to import Label for test excution also ?

maybe i can already with the current config but dont know which key point to that

As I understand the custom fields are per test case. I have to investigate if it is possible to do it the same way as they do it in the playwright-junit-reporter with e.g. testInfo.annotations.push({ type: 'test_id', description: '1234' });

yes , in fact i m using junit report before using this library

Adding it on the same level as info shouldn't be a big issue. I wonder if it should be in the playwright config file or in an external file. What would be more convenient?  E.g. customFields: './myCustomFields.json'

i think in config is more desired , but i can work with json files also , but to be more elegant i think it should something like this [       'playwright-xray',       {         jira: {           url: 'https://waykonect.atlassian.net',           type: 'cloud',           apiVersion: '1.0',         },         cloud: {           client_id: clientId,           client_secret: clientSecret,         },         summary: [${new Date().toLocaleString('fr-FR', { timeZone: 'Europe/Paris' })}] - Automated `,
projectKey: projectKey,
testPlan: testPlan,
debug: false,
testEnvironments: process.env.ENV,
customFields:[ "Label" : exampleLabel , "priority" : high]
  },
],`

i would like to move this discussion to another request so we can close default summary one since it was done but i dont know how

I can try

Created new issue "Is it possible to import Label for test execution"


Fix 1593

Overview
Adds a parseThreshold function and cleans up some other minor naming conventions.
closes #1593, with the understanding that some additional work in widgets will be needed after associated rbm-viz updates are final.
I branched off of fix-1457, and had some minor conflict resolution to deal with, so merge this after #1594, with some attention to the version of rbm-viz being used ...
Test Notes/Sample Code

Notes:

Core functionality has been addressed in other PRs.


MethodAccessException

Please fill in the following fields:
Unity editor version: 2018.3.8f1
Firebase Unity SDK version: 6.1.1
Firebase plugins in use (Auth, Database, etc.): Messaging
Platform you are using the Unity editor on (Mac, Windows, or Linux): Windows 10
Platform you are targeting (iOS, Android, and/or desktop): iOS, Android
Please describe the issue here:
MethodAccessException: Method `Google.RunOnMainThread.Run(System.Action,bool)' is inaccessible from method `Firebase.Editor.NetSDKChecker..cctor()'
Firebase.Editor.NetSDKChecker..cctor () (at <02ccfbc47d26479eba09972331d0433d>:0)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.Editor.NetSDKChecker' threw an exception.

MethodAccessException: Method `Google.RunOnMainThread.Run(System.Action,bool)' is inaccessible from method `Firebase.Editor.GenerateXmlFromGoogleServicesJson..cctor()'
Firebase.Editor.GenerateXmlFromGoogleServicesJson..cctor () (at <02ccfbc47d26479eba09972331d0433d>:0)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.Editor.GenerateXmlFromGoogleServicesJson' threw an exception.

MethodAccessException: Method `Google.RunOnMainThread.Run(System.Action,bool)' is inaccessible from method `Firebase.Editor.XcodeProjectPatcher..cctor()'
Firebase.Editor.XcodeProjectPatcher..cctor () (at <02ccfbc47d26479eba09972331d0433d>:0)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.Editor.XcodeProjectPatcher' threw an exception.

MethodAccessException: Method `Google.RunOnMainThread.Run(System.Action,bool)' is inaccessible from method `Firebase.Editor.GenerateXmlFromGoogleServicesJson..cctor()'
Firebase.Editor.GenerateXmlFromGoogleServicesJson..cctor () (at <02ccfbc47d26479eba09972331d0433d>:0)
Rethrow as TypeInitializationException: The type initializer for 'Firebase.Editor.GenerateXmlFromGoogleServicesJson' threw an exception.

a lot of exceptions like these
Unity 2018.3.14
The latest firebase analytics sdk

The Firebase Unity SDK depends upon the patch in https://github.com/googlesamples/unity-jar-resolver/commit/cea8035e3cec7551779f2b0e8a2ee56dec2de17d
Sounds like you should upgrade the Play Services Resolver to latest.

Most recent release is https://github.com/googlesamples/unity-jar-resolver/releases/tag/v1.2.117


Unable to chain rewrites

1. What version of Caddy are you using (caddy -version)?
Caddy 0.10.10 (unofficial)
2. What are you trying to do?
I am trying to chain rewrites such that rewrites affect the path pattern-matching aspects of subsequent rewrites. For example, I'd like to rewrite /bar/* to /foo/* and have subsequent rewrites be able to focus on /foo/* (since /bar/* becomes "unreachable"); for example, to protect files in that directory from being accessed directly. Unfortunately, it seems as though subsequent rewrites always use the original path, even when I explicitly use the {rewrite_path} placeholder.
3. What is your entire Caddyfile?
<IP_ADDRESS>

tls off

rewrite /bar {
  regexp (.*)
  to /foo{1}
}

rewrite /foo {
  ext .txt
  to /
}

# This also doesn't work:
#rewrite {
  #ext .txt
  #if {rewrite_path} starts_with /foo
  #to /
#}

4.  Please paste any relevant HTTP request(s) here.
 What did you expect to see?
$ curl localhost:2015
Index
$ curl localhost:2015/foo/test.txt
Index
$ curl localhost:2015/bar/test.txt
Index

7. What did you see instead (give full error messages and/or log)?
$ curl localhost:2015
Index
$ curl localhost:2015/foo/test.txt
Index
$ curl localhost:2015/bar/test.txt
Test

8. How can someone who is starting from scratch reproduce the bug as minimally as possible?

Copy the above Caddyfile

Create the directory structure:
$ mkdir foo
$ echo Index >index.html
$ echo Test >foo/test.txt

Start Caddy (doesn't have to be through Docker)

Execute the above cURL commands

Thanks for filling out the issue template!
The rewrite directive simply chooses the first matching configuration and applies that. Instead, make a single rewrite that goes directly to what you want:
rewrite {
    regexp /bar/(.*)
    to /foo/{1}
}

(Something like that, anyway.)
Since what can be done by multiple rewrites can also be done with one rewrite, and is simpler, I don't think we're going to make rewrites an optimization function that runs until they converge. We tend to like the simplicity of just "one rule to bind them all." :wink:


Support YAML Output in CLI

The web client allows switching between JSON and YAML, let's add a --format flag for the shell + query commands

Hey there! I decided to give this issue a try.
Please let me know if there is anything to change or fix.

Hey there! I decided to give this issue a try.
Please let me know if there is anything to change or fix.

Hey!
Thanks for wanting to contribute, we appreciate it a lot 🔥
I'm reviewing the code now 😎


Fixing precision not holding on a marking-definition during parsing and serialization

Codecov Report

Merging #287 into master will decrease coverage by <.01%.
The diff coverage is 94.11%.

@@            Coverage Diff             @@
##           master     #287      +/-   ##
==========================================
- Coverage   98.63%   98.63%   -0.01%
==========================================
  Files         119      119
  Lines       12845    12855      +10
==========================================
+ Hits        12670    12679       +9
- Misses        175      176       +1

Impacted Files
Coverage Δ

stix2/v21/common.py
100% <ø> (ø)
:arrow_up:

stix2/test/v21/test_markings.py
100% <ø> (ø)
:arrow_up:

stix2/v20/common.py
98.7% <94.11%> (-1.3%)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks @zrush-mitre!


Improve SceneKit lighting for navigational nodes

There’s some work going on on the /feature/mapkit branch which involves adding navigational nodes. Right now, because my knowledge of SceneKit and lighting is lacking, I’ve added a number of lights to each of these. This may be the cause of some slowness once you add a certain amount of them, and is also the cause of some side effects such as over lighting of other elements.
Perhaps we just need either a few lights for the entire scene? The goal is just to create some shadowing so you can differentiate the different sides, where if we don’t have lights then each side is equally lit and thus you just see the whole 3D shape as the same colour.
If someone with knowledge of SceneKit and lighting could contribute to this then that’d be great.

Removing this as an Issue


migrate to humble (minor breaking changes)

Add missing find_package calls
Add package.xml dependencies
Fix template mess with Client Async Send Requests

@Hermanoid ready for review. Writing this before github action inevitably fails (driverstation_gui) does not exist in this branch so i expect it to fail. Can just ignore the check as the fact that it gets past the first step (docker pull) is the whole point of this branch.

Also don't know if you've used github actions before, but I'd like some input on those files aswell.