UserId Not Being Persisted in Chrome

We deployed a new app to production on  Monday, and the Application Insights reports are showing we have 350 unique users when in fact we have 5. Our users are using Chrome. It appears that userid is not being persisted between pageviews.
We can reproduce this bug in a new web project as follows.:
Steps to Reproduce:

In VS 2017 update 3, create a new ASP.NET WEb Applicatoni (.NET Framework) project with MVC
Right-click on project and Configure Application Insights
Update SDK from v2.2.0 to v2.4.1
Register a new Application Insights Resource
Start debugging the app
Click through 4 pages in Edge (14.14393)
Click through 4 pages in Chrome (61.0)
Open Application Insights Analytics and run
pageViews | limit 1000

Expected Behavior:
8 rows, with:

the 4 from Edge have the same UserId
the 4 from Chrome have the same UserId

Application Insights Reports will then show 2 unique users.
Observed Behavior:
8 rows, with:

the 4 from Edge have the same UserId
- the 4 from Chrome each have a unique UserId

Application Insights Reports will then show 5 unique users.

I'm unable to repro. The SDK stores a userId in an 'ai_user' cookie. Could you confirm that the cookie is set in the browser? If it is, the same value will be used for all pageviews.

Thank you for getting back to me so quickly. It looks like my issue is being caused by Strict Secure Cookies, a feature enabled by default in Chrome 58. You should now be able to reproduce it by switching from secure connection to a non-secure connection.
Workarounds to this issue appear to be clearing cookies or only accessing the site over a secure connection.
In the steps to reproduce, if you first enable SSL and click through the pages in Chrome, then the cookies for ai_authUser, ai_session, and ai_user are created as secure, and the correct data is sent to App Insights.

If you stop debugging, these 3 cookies are still there; however, you can see they are secure.

If you now disable SSL, and click through the pages in Chrome, the 3 secure cookies are not visible because they are secure cookies now being accessed by insecure origins. The result is that Util.setCookie silently fails to set these 3 cookies, and the data sent to App Insights has a new unique ai.user.id on each page view.

Thank you for providing repro steps and explaining what is causing the issue.
To fix this we will need to make a change to the SDK. It should check if it can set a cookie, and instead of failing silently it should delete the secure cookie and create an insecure cookie for not secure connection.

Closing this issue as switching between secure and insecure is not a supported pattern especially with the coming cookie changes in chrome 80 where secure cookies will be required to have samesite.


Update Elixir parent to 1.7

As of recently Pleroma requires Elixir 1.7.

I can confirm everything is working with Elixir 1.7.4 and Postgres 11.1 😊

Thanks 👍


deploy to PowerBI desktop is not working

when i connect to PowerBI desktop, i can see the model and do modification, trying to deploy the model results in errors.

What error message are you getting, and what kind of changes did you make to the model? Also, which version of PBI Desktop are you using?

I am using PBI Version: 2.41.4581.361 64-bit (November 2016), I did not modify anything, just connect to PowerBI desktop, then click deploy using the same server launched by PBI desktop, i can not copy the error, but it start with Query(269,77) the syntax for "yes" is incorrect.

In general, the Deploy option generates and executes a TMSL script, which I think is currently not supported by Power BI desktop. However, as you noticed, the "Save" option seems to work.
In my experience, it should be possible to do simple changes such as adding display folders and measures to a .pbix file, saving the changes from Tabular Editor, and then saving the .pbix file in Power BI Desktop. But in any case, this is not a feature that is supported in Power BI, so if it doesn't work with the changes you make, I'm afraid there's nothing we can do in Tabular Editor to fix it. I've wrote a mail to the Power BI Team to hopefully add support for TMSL script changes, etc. to models loaded in Power BI, so that this will work flawlessly in the future.

thanks daniel
SSAS in _PowerBi Desktop run in a sharepoint mode, so backup and restore does not work, instead something like this should work https://msdn.microsoft.com/en-us/library/mt577156.aspx.
I know probably you have other priorities, but supporting Power BI desktop will be a "Killer feature"
thanks for adding automatic detection of port ID

Hi Mimoune,
I'm not sure I understand what this feature is supposed to do. I would love to help and improve support for Power BI. Could you please explain a little more detailed what it is you need?
Thanks in advance!

I opened a separate issues, i will provide more information if needed


Added env. variable to support specific HTTPS redirect ports

Will prefer HTTPS_REDIRECT_PORT, but default to 80 if only ENABLE_HTTP_REDIRECT is enabled.

Accidentally put my main branch as the request for the other one, yesterday.


JBDS-4037 Log contains 'setup finished' entries for skipped components

Log 'Setup done' only for selected for installation components.

test this


Typo: URI when it should be URL

Code of Conduct

[X] I have read and agree to the GitHub Docs project's Code of Conduct

What article on docs.github.com is affected?
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/using-query-parameters-to-create-a-pull-request
What part(s) of the article would you like to see updated?
Fix the typo.
Additional information
I've a linked PR for this.
### Tasks
- [ ] https://github.com/github/docs/pull/34813

Closing per comment here 💛

Could you close this as not planned?

Could you close this as not planned?

Of course, thanks for the nudge! 💛


ScriptHookVDotNet Causing Crash with RagePluginHook

Hi, anytime I try to launch GTA5 with RagePluginHook and ScriptHookVDotNet installed it crashes when loading into the game, at the same spot every time. Right when it says loading and populating game world. I can start the game just fine without Rage, and this happens no matter which version of ScriptHookVDotNet I have installed. I've tried reinstalling GTA5 and I have the same problem. I have no scripts installed and my scripts folder is empty. I've checked all the logs and they don't show anything. The only thing I have to go off of, is Windows Event Viewer, which points to MpOav.dll as the faulting module. I've looked it up, and it's a dll file for windows defender. I've tried disabling and reseting Windows Defender to no prevail. I'll attach some screenshots and some logs. Any help would be great, thanks in advance.
AdvancedHookV.log
asiloader.log
RagePluginHook.log
ScriptHookV.log
ScriptHookVDotNet.log

MpOav.all is irrelevant to GTA5.exe, this plugin, or RagePluginHook. I guess it comes with Windows Defender, but not relevant to this plug-in’s bug anyway.


checkpointer: handle kubelet API denials and make kubeconfig configurable

This is a requirement for kubelet authorization.
We still force the checkpointer to not check the kubelet's serving cert no matter what's in the kubeconfig, since in our deployments it's self signed.
Updates #648
Closes #625
cc @diegs

coreosbot run e2e checkpointer

As a reminder, kubelet authorization is a blocker for:

Prometheus monitoring - being able to let a service account hit the secure API.
TLS bootstrapping - so every client cert can't do arbitrary things against a kubelet.

This PR updates the checkpointer to

Be okay if it can't contact the kubelet API. e.g. if the API server is down and kubelet authorization fails.
Be able to take a configurable kubeconfig so it can stop using the kubelet's kubeconfig and use its own service account creds to talk to the kubelet in the future.

Tested this locally with the following diff:
$ git diff .
diff --git a/hack/single-node/user-data.sample b/hack/single-node/user-data.sample
index a2f7411a..36543035 100644
--- a/hack/single-node/user-data.sample
+++ b/hack/single-node/user-data.sample
@@ -27,6 +27,8 @@ coreos:
         ExecStart=/usr/lib/coreos/kubelet-wrapper \
           --allow-privileged \
           --anonymous-auth=false \
+          --authorization-mode=Webhook \
+          --authentication-token-webhook=true \
           --client-ca-file=/etc/kubernetes/ca.crt \
           --cluster_dns=<IP_ADDRESS> \
           --cluster_domain=cluster.local \
diff --git a/pkg/asset/images.go b/pkg/asset/images.go
index d22450b6..319a8b23 100644
--- a/pkg/asset/images.go
+++ b/pkg/asset/images.go
@@ -13,5 +13,5 @@ var DefaultImages = ImageVersions{
        KubeDNS:         "gcr.io/google_containers/k8s-dns-kube-dns-amd64:1.14.4",
        KubeDNSMasq:     "gcr.io/google_containers/k8s-dns-dnsmasq-nanny-amd64:1.14.4",
        KubeDNSSidecar:  "gcr.io/google_containers/k8s-dns-sidecar-amd64:1.14.4",
-       PodCheckpointer: "quay.io/coreos/pod-checkpointer:4e7a7dab10bc4d895b66c21656291c6e0b017248",
+       PodCheckpointer: "quay.io/ericchiang/pod-checkpointer:81296cf2833f7b840910dce7e5a770a8b2705146",
 }

Was able to get kubectl exec working with the following role bindings:
kind: ClusterRole
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: kubelet-admin
rules:
- apiGroups: [""]
  verbs: ["*"]
  resources: ["nodes/stats", "nodes/metrics", "nodes/log", "nodes/spec", "nodes/proxy"]
---
kind: ClusterRoleBinding
apiVersion: rbac.authorization.k8s.io/v1beta1
metadata:
  name: kubelet-admin
subjects:
- kind: User
  name: kube-apiserver
roleRef:
  kind: ClusterRole
  name: kubelet-admin
  apiGroup: rbac.authorization.k8s.io

(btw, I'm assigned but don't have merge access to this repo)

coreosbot run e2e checkpointer


Update terms-of-use.html

Including a Cookie Policy section is essential for transparency regarding how user data is collected and used, especially for compliance with regulations like GDPR.

Resolve the conflicts in the mentioned files. Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


Pan:Traffic & Network Traffic CIM

pan:traffic does not match the CIM for Network Traffic:
http://docs.splunk.com/Documentation/CIM/4.8.0/User/NetworkTraffic
protocol expects OSI Layer3, not OSI Layer4. tcp/udp are transport
https://en.wikipedia.org/wiki/List_of_network_protocols_(OSI_model)#Layer_3_.28Network_Layer.29
add an eval to the TA to assume protocol is ip or include instructions to log this field from PA.

Hi @anthonygtellez, thanks for opening this issue.  Agreed, this should be ip, not tcp/udp.  We'll get this fixed in an upcoming release.
Thanks again!

Fixed in 6.0.0


_ Prechecks _

+1 :green_heart:
dupname
0m  0s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

_ master Compile Tests _

+1 :green_heart:
mvninstall
2m 46s
master passed

+1 :green_heart:
compile
0m 21s
master passed

+1 :green_heart:
checkstyle
0m 12s
master passed

+1 :green_heart:
spotless
0m 43s
branch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
0m 27s
master passed

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
2m 32s
the patch passed

+1 :green_heart:
compile
0m 19s
the patch passed

+1 :green_heart:
javac
0m 19s
the patch passed

-0 :warning:
checkstyle
0m 10s
hbase-http: The patch generated 1 new + 0 unchanged - 1 fixed = 1 total (was 1)

+1 :green_heart:
whitespace
0m  0s
The patch has no whitespace issues.

+1 :green_heart:
hadoopcheck
8m 54s
Patch does not cause any errors with Hadoop 3.2.4 3.3.4.

+1 :green_heart:
spotless
0m 40s
patch has no errors when running spotless:check.

+1 :green_heart:
spotbugs
0m 33s
the patch passed

_ Other Tests _

+1 :green_heart:
asflicense
0m 11s
The patch does not generate ASF License warnings.

24m 52s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4879/4/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/4879

Optional Tests
dupname asflicense javac spotbugs hadoopcheck hbaseanti spotless checkstyle compile

uname
Linux f4600bd5634b 5.4.0-124-generic #140-Ubuntu SMP Thu Aug 4 02:23:37 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev-support/hbase-personality.sh

git revision
master / c691091f78

Default Java
Eclipse Adoptium-11.0.17+8

checkstyle
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4879/4/artifact/yetus-general-check/output/diff-checkstyle-hbase-http.txt

Max. process+thread count
78 (vs. ulimit of 30000)

modules
C: hbase-http U: hbase-http

Console output
https://ci-hbase.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-4879/4/console

versions
git=2.34.1 maven=3.8.6 spotbugs=4.7.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Strange Location Marker

Why does the font awesome map marker look strange? It doesn't have a "hole" as it should: https://fontawesome.com/v4.7.0/icon/map-marker

I found a solution to this problem: simply change this line on the author_profile.html by

 {{ author.location }}

This other icon does show the hole as you would expect from a "location" icon

How do I change the color of the map marker?
Thanks!

This might require a new version of the font library, shifting to the next milestone.

Updated to Font Awesome v6 and changed the map icon.


Migrating from 4.4 to 5.4.0

How can we migrate the following code written on the version 4.4 to the version 5.4.0? (This examples uses Kotlin, but a Java solution will be OK)
element().that(isAnnotatedWith<AnnotatedElement>(Id::class.java).or(isAnnotatedWith<AnnotatedElement>(EmbeddedId::class.java))).in(this).value<Any>();

Just replace that with filter and isAnnotatedWith with annotatedWith.
I need to apologize, I'm constantly changing the API without providing migration guides. Right now I'm planning the v6 release with a lot of changes (the value() will be getValue(), for example).
It may sound like the API isn't mature, but since this project started in 2009, I'm constantly improving my skills and trying to reflect it on the framework. But I really need to apologize.
Oh! And thank you for using it. I didn't know people use it (apart from me and a couple of friends).
;)

Hi, thank you about your answer.
The truth is I think your library is a very useful one, it is very handy to work with annotations and find an arbitrary entity primary key, for example. We can create a structure really powerful with this.
To set a value, instead of value .value(myValue), should we use .set(myValue)?
Thanks a lot ;)

Exactly! I think is not a good name, so that's why I renamed both to getValue and setValue in version 6. If you wan't to give v6 a try just clone the branch and do a mvn install. It should be released this week.
I'm planning something more functional in this version. You can, for example, do something like this:
String value = reflect()
  .field("aStringField")
  .from(myInstance)
  .and(getValue());

[ ]'s


Move hardys to emeritus_approvers

My area of focus has changed, so I can no longer commit to being an approver

/approve
/lgtm


Allow the round number to be specified or edited before export

Users should be able to set the round number either when making the new game or through a menu item.

Could be handled by #216?


Uprade gobreaker version to 0.5.0

💸 TL;DR

Update gobreaker version from 0.4.1 to 0.5.0, which adds IsSuccess to Config
📜 Details
We want to be able to customize the default behavior of IsSuccess, which defaults to check: if err is nil then it's successful, if err is non-nill then it's error
Outcome: By exposing IsSuccess to user, user will be able to make more thorough check
🧪 Testing Steps / Validation

✅ Checks

[ ] CI tests (if present) are passing
[ ] Adheres to code style for repo
[ ] Contributor License Agreement (CLA) completed if not a Reddit employee

That's good workaround, it could be useful for this case:
We get validation error, we don't want it to increase error count of Circuit breaker, but still want original err to exit function.
Counter argument might be, if it's validation error then probably resp is nil and we could use that to check? That would be right, but in general IsSuccess looks useful overall )) It's not urgent to merge, but might be included in next release?
cc: @fishy

Have you tested this version in production yet?


nvm install and nvm uninstall freezes

Operating system: Ubuntu 20.04
Using nvm install 16.14.0 or nvm uninstall 16.14.0 causes the terminal to freezes, It just stucks and doesn't go further.

Last lines of set -x;nvm install are:
+ local NVM_USE_OUTPUT
+ NVM_USE_OUTPUT=
+ '[' 0 -ne 1 ']'
+ nvm_is_iojs_version v16.14.0
+ case "${1-}" in
+ return 1
++ nvm_print_npm_version
++ nvm_has npm
++ type npm
+++ npm --version

What does npm --version do by itself?

Glad to hear it; it must be a bug we fixed then.


I tried virtual scroll to display a list but in 3.9.2 its not displaying anything

Thats my code

    <ion-list no-lines [virtualScroll]="my_prg" [approxItemHeight]="'100px'">
        <ion-item ion-item *virtualItem="let item">
            {{item.name}}
        </ion-item>

    </ion-list>
</div>

Hello! While we appreciate you opening an issue with us I am going to close this issue and ask that you open a new one that has the issue template filled out please.
Also, if you could provide a plunker or a simple demo application via a GitHub repo that demonstrates this issue that would be very helpful.
Thanks for using Ionic!


Refactor circuit_build_path logic

Problem
The logic for getting a circuit_build_path or recompiling is duplicated many times throughout nargo_cli. This should be refactored.
Proposed solution
Per @TomAFrench's comment:

I'd like to add a "context" struct at some point which essentially wraps the PackageManifest along with the package's root directory. These sorts of functions would then live as methods on there.

Alternatives considered
No response
Additional context
No response
Submission Checklist

[X] Once I hit submit, I will assign this issue to the Project Board with the appropriate tags.

Hello! would love to work on this issue. is there more context on how I would implement this? Thank you 😄


Question about potential for more optimizations

Hi developers,
First of all, thank you very much for implementing and maintaining libpointmatcher. It's an excellent library for point cloud registration and filtering. Its code quality, number of features and performance are really great.
I'm a power user of pointmatcher, and for the platform that we're using it on we want to explore some performance optimizations. to reduce the load from ICP and point cloud filters. I was wondering about the possibility of evaluating performance and applying optimizations where needed (e.g. by means of intrinsics, compiler flags, OpenCL), to accelerate the rate at which ICP and filters can be run.
In this regards, could you give me any pointers to what has been tried before? And also your opinion about the addition of OpenCL/intrinsics code?
Furthermore, I have read arguments from multiple authors about the possibility of optimizing ICP by means of parallelism. Some are in favor, while some argue that doesn't really make a big difference. What are your thoughts on this?
Thank you very much in advance.

I've seen a couple of people implementing ICP on a GPU and loading the point clouds on the GPU takes a lot of time, which reduces a lot the performance gain.
You could start by having an analysis of which module cost the most in term of computation time. My expectation is that the matching module takes about 80 % of the computation time. We already rely on libnabo, which used OpenMP to deployed multiple threads. I'm not aware of a solution for an approximate kd-tree working on GPU.
That being said, adding some OpenMP preprocessor directive could help for the DataPointFilters too. If you find out something, we will welcome any gain on performance!

@pomerlef Thank you very much for your input.
We are quite interested in taking this forward, and have two ideas on feasible optimizations to libpointmatcher:

Some filters seem to random shuffle input point clouds every time they run (Credits to @jsburklund). Have you considered random shuffling only once for a given chain of filters?
We were considering running libpointmatcher and a tool such as Intel Advisor to identify which blocks of code can benefit from vectorization. To which extent has this been explored during the development of libnabo and libpointmatcher?

Filters related to downsampling will change the order of points. They should actually squeeze them by removing deleted points. The ones doing descriptor augmentation should not change the order. If it's the case, then it's a bug.
We did the optimisation manually bit per bit without out a specific tool. We would be happy to have you look through it more systematically. Any gain on computation time will help everybody.

@pomerlef I see.
Regarding point 1, I will take a closer look at the filters we are using very soon.
About point 2, we are planning to do this, but in small pieces and over this year. I will get back to you with results as soon as we have them.
Something else I have been considering, and I wanted to mention as item 3: Have you considered the possibility of using organized point clouds?
Filters like SurfaceNormal could save significant computation time if the point clouds are organized, as you would not have to run K-NN to find neighboring points.
I've noticed that many packages implicitly organize point clouds to extract features (e.g. LOAM), some lidar drivers allow you to get organized point clouds or at least projections nowadays (e.g. Velodyne, Ouster), and there are also multiple benefits on having a flat representation of point clouds that can be traversed in any way and reprojected into other sensors easily.

You're turning every rocks for optimization ;)
So, for organized point clouds, they tend to do a projection on a 2D grid to improve speed. Doing a projection imply loosing information. This work only for a single point cloud from a sensor, not for the map as there is no focal point. When using those solutions, we loose generalization for computation speed (typical engineering challenge).
I see the use of kd-tree and octree as a way to organize point clouds, but they are indeed costly.
We can add those projections, but we then need also to make it explicit to the user that those filter can only work on sensor inputs, not on generic maps.

@pomerlef Thank you for your reply.
Indeed, I'm looking at all the options before starting with any implementation. Regarding the topic of organized point clouds, I will start a separate issue to discuss more in depth how we could represent them, if that's ok for you.
(The following point will diverge from the optimizations discussion, but I think it makes sense to mention it)
About the map representations, I agree that organized point clouds in the form of projections are not usable. But I would also say that keeping unorganized point clouds as map representations is not ideal. You need to discard a lot of data to keep unorganized point cloud maps manageable by an online SLAM system.
I think a better map representation would be something that

Allows fine scale measurements to be registered, so your map density and accuracy is as high as you want.
Allows you to update sections of the map your sensor most likely observed, instead of the whole thing. This way your resource requirements remain feasible for real time operation.
Thus, I think a hybrid between organized and unorganized point clouds is desirable, something like voxels containing point sets, or TSDF.

Part of those were implemented at the application level in ethzasl_icp_mapper.

@pomerlef Thank you for the reference.
An additional question: do you think there could be some way to save and re-use a KD-tree? KNN is used in different places (ICP Matching, Overlap estimation for extending the map, dynamic points detection -from your work with P. Krüsi). Even though libnabo and libpointmatcher are quite fast generally, the KNN step has a fairly large footprint in terms of resources

From what I recall, libnabo only use pointers, so the memory footprint should be small.
I'm not sure of what you have in mind for saving the kd-tree. You want to 1) put it on disk or 2) you want to make the data structure available to other modules? The second one crossed my mind a couple of times, but I couldn't find a solution where we don't lose the modularity of the library. There could be some methods to feed a tree build from outside, but we should be general enough to allow the use of something else than libnabo or a kd-tree.


attempt to fix linker error

I still do not understand the mechanics that lead to that instantiation of insert.. but that change helped.

Closed in bd4b9b82d1e45358eaf27015cd314c574f32a6d4


runtime: removing enable_zone_routing_different_zone_counts

fixes https://github.com/envoyproxy/envoy/issues/33617

Commit Message:
Additional Description:
Risk Level:
Testing:
Docs Changes:
Release Notes:
Platform Specific Features:
[Optional Runtime guard:]
[Optional Fixes #Issue]
[Optional Fixes commit #PR or SHA]
[Optional Deprecated:]
[Optional API Considerations:]

/retest

/retest


window management options

on top right i see two tiling modes. max and tile. can we have floating or other options there. with keybind to switch mode for each tag.?

Yeah we could but I want to keep the config the most simple possible and I want it to be very predictible.
The goal of the config here is to avoid the floating mode. That's how I could remove the titles bars without problems.
So it's possible I could add some others options but not the floating mode and for now the only 2 modes I feel usefull is the tileling for multitasking and maximized for focus work.
If you find some other mode usefull don't hesitate to explain me why :)

i dont know using i3gaps i was able to switch modes and make a window floating to resize it or shift to somewhere else. if i get stuck somewhere maybe note down things and will let you know. instead of floating maybe vertical tile like i3 or changing tile orientation on fly makes sense? like where next window will appear horizontal or vertical. i am so new to awesome if what i am asking contradicts to awesome wm way of doing then please ignore.

Something need to be clarifyed. My configuration is not made with AwesomeWM but it's not the whole AwesomeWM. With AwesomeWM you can do almost everything you want like clone i3-gaps.
I have my own vision of how I want my desktop environment to work but you could want something else and change the configuration to make it's work like that.
I locked up my config to only 2 layout: Maximized and Tileable but awesome can do much more https://awesomewm.org/doc/api/libraries/awful.layout.html#Client_layouts

i got that idea. but to make changes to your configuration need to learn alot :) after all its maybe more then 4 months of configuration. thats why asking stupid questions.


Onboarding update - Divisions for PSA

Title of ticket:
Description
After Training, PSA provided an updated list of divisions. Many divisions will remain, with a number to be added and removed.
Dependencies
Are there any dependencies?
DOD
To Add

[ ] HRSS Records
[ ] HR Specialist Case Files
[ ] BCPSA Classifications
[ ] Contact Centre
[ ] Peoplesoft Reports
[ ] Performance Records
[ ] Job Competition Files
[ ] POD - Executive Talent Management
[ ] POD - Corporate Workforce Strategies
[ ] POD - Learning Centre
[ ] PIE - Policy and Research
[ ] PIE - Behavioural Insights Group
[ ] Employee Relations - Workforce Restructuring
[ ] Employee Relations - Investigations
[ ] Labour Relations - Grievances
[ ] Information Technology Services
[ ] Surveys and Measurement
[ ] Corporate Health Programs

REMOVE from existing list

[ ] Business Performance
[ ] Custom Research
[ ] Corporate Health Program
[ ] Employee Relations
[ ] Policy, Innovation & Engagement
[ ] People and Organizational Development

Divisions updated for onboarding activity

Confirmed updates in Test, closing ticket.


Improve GUI Design

The GUI could be more intuitive, with better placement of buttons and clearer descriptions of what some potentially ambiguous actions will do

I've begun work on this. Feedback is very welcome. See this screenshot. This work is currently in a branch on my own fork of this repo, found here.
Things I'm thinking of doing next:

[ ] improve equation canvas
[ ] collapsable toolbar sections
[ ] better styles for toggle-able options (eg multiselect) by making use of the active class from bootstrap

I just saw it, and it looks good! I was thinking that, to keep things organized, the manipulations could be divided into Algebraic and Free editing. The former are only algebraically valid manipulations, while the latter are to give you more flexibility. The current manipulations fit like this:

Algebraic

Change side
Divide by factor
Root by power
Evaluate/Simplify
Move selection
Add to both sides
Split fraction
Distribute in
Factor Out

Free editing

Remove
Unbracket
Replace selection with

These could be subclasified further, but I think that'd make it harder to use, at least with the number of manipulations we have at the moment. In any case, when we have more manipulations I think we should have a way of having the most common ones on top, and more accessible, than the least common ones (in the future, I think it'd be cool that people could have their own custom manipulations, by clicking some "Record" button, doing stuff, and saving that as a custom manipulation, they can in the future invoke)

I was wondering how to categorise them. I like your suggestion above. I don't think they need to be subcategorised further. If more manipulations are added, I think a search led UI would be best, particularly for community contributed manipulations.
I know you raised it in the todo section of the readme, but it'll be cool to have some of the algebraic manipulations unselectable when they don't apply, for example the user shouldn't be able to click "change side" if they've selected a denominator.

Yes I think that'd be a good thing to have (the unselectable manipulations depending on selection). I was also thinking of how useful may it be to have a top toolbar with the most common manipulations appearing as some icons (which we'll have to design or find), leaving the left toolbar for the full name and full list of manipulations.
I was even thinking of making it even easier to manipulate (i.e., less cursor-moving), by making the common manipulations for given selection appear in some bubble above or below the selection, or alternatively, as a custom right-click context menu.

These are all good ideas. I think it'd be best to sketch each and prioritise them. I might have time this evening or this weekend to work more on the UI

Applied some of the ideas in 502b90a11a320357941bf1b4082ce0a8e816b52b


Random Number Generator

What feature or new tool do you think should be added to DevToys?
A simple random number generator that can generates a list of number within the given range.
Why do you think this is needed?
When writing unit test, sometimes there are needs to test against a group of input number. Using random numbers can be a good starting point.
Also when using some tools that require a group of seeding numbers (like... Automatic1111/stable-diffusion-webui), creating a list can be annoying.
Solution/Idea
Create a new generator similar to Password Generator or UUID.
Comments
No response

Here's an idea of what it would look like.  I quickly whip some code changes and got it somewhat working (with quite a few problems).

I am thinking of creating this one, are you guys still interested in this one?

Closing as no upvote/traction on this issue. Can be made as an extension if anyone wants to try our SDK: https://devtoys.app/doc


feat: add alternatives to process execution libraries

Overview
This pull request adds alternative replacements for process execution libraries such as execa and zx.

although zx is fairly big, i think we should leave it out as its a very well maintained/stable project for when you want templated scripts
note to anyone else here: before this can land we need to introduce a new manifest I think too. since execa is useful in some situations (where you heavily rely on its extended features). so it may be that we introduce a new opinionated manifest or something that can somehow conditionally be suggested based on usage
good contribution 🎉

Thanks for the review. zx dropped.
Do you have other alternatives that can be used? I'm thinking of nanoexec but I'm not sure about it.
As for ezspawn (and friends), I don't think it's worth it to include them here considering they're barely used.

I disagree with zx as an alternative as the unpacked size is actually bigger than execa but doesn't provide compelling features that execa doesn't have (cmiiw).
The only benefit of zx is that it doesn't contain any dependencies.
npmgraph for execa
npmgraph for zx

fair point. we shouldn't have it in the replacements list, though, as it is one of the better choices for when you need templating
we can work on reducing the size of zx meanwhile, at least
so i would remove it from the list, and from the replacements list for now


Fix log level in CFStream

Downgraded some log level of some log sites  from ERROR to DEBUG.

Known issues: #19669, #19614


Revert depending on a pre-release of parity-scale-codec

Undoes #137.
Sorry for the churn, we'll go with the approach outlined in https://github.com/paritytech/parity-common/pull/552#issuecomment-872252537 instead.
I'll yank 0.14.2 once this gets merged.

Yanked 0.14.2 - https://crates.io/crates/finality-grandpa/0.14.2

Sorry for no response but I was out 🙏.


Fixing the dependence raising rule for restrictions

The previous iteration of the rule appeared to be the inverse of the associated normalization rule, but was not. Instead, information about the restriction domain was being lost in some cases, resulting in incorrect programs. This was most easily seen when applying dependence raising to a prefix scan equation. A test for this was added to ensure this scenario doesn't occur again.

Looks good!


Export all raws no limit

Added _limit: -1 so there will be no limit for the number of rows to export
(100: default, -1: unlimited)

Hi everyone.
Sorry for being away from the project, soon I will upload new updates.
Thanks for your patience.


fix(fromEvent): match targets properly; fix result selector type

Description:
This PR fixes some problems with fromEvent:

The interfaces used to match targets need to use methods instead of props. Otherwise, extends behaves in an unintended manner and the types won't match.
There is a signature that takes only the target and the event name, so the optional qualifiers on the other signatures are redundant.
If the resultSelector returns T, the target's type should not be FromEventTarget<T>.

The typing of fromEvent could be improved, but I think the first step is to fix these problems. The next would be to replace the FromEventTarget type with separate signatures.
Related issue (if exists): Nope

The interfaces used to match targets need to use methods instead of props. Otherwise, extends behaves in an unintended manner and the types won't match.

WTF. 🙄 lol


Web site - Fix the community link

Go to the Doc site, open the dropdown, the bottom community link points to a ProdDev Pass Slack channel.

Ooops.


Move data in 64KB blocks when migrating persistent disks

instead of using the default (10KB)
See #107

nice change @CAFxX. will try to review with @tylerschultz tomorrow.

@CAFxX out of curiosity what's the speed up for 600gb test you've done in your deployment?

@cppforlife see https://github.com/cloudfoundry/bosh-agent/issues/107 for the details, copying data happens at ~150MB/s (generating >1000 IOPS especially on the read side), so copying 600GB take over one hour

@cppforlife sorry upon further testing - making sure that the conditions are more realistic - it looks like this is not really giving much benefit. We're going to try some more and report back.

Closing, for now.


Examining functional relationship between tau and u

I've added in a retreat scenario with Schoof's bed. We can see the retreat slow going up the sill, and then accelerate after moving past it. Weaker perturbations lead to a steady state on top of the sill.  Regardless of the scenario, if I run it without coupling and the same initial steady state N (kept static), the uncoupled model halts retreat right away.

Originally posted by @glugeorge in https://github.com/glugeorge/coupled_ice_hydrology/issues/3#issuecomment-1332789720
Using the min/max of u and N, we plot different relationships between a non-dimensionalized tau and N. Based off this profile:

Here is the tau vs u plot:

Now looking at tau as a function of N, u, C, As.

It's quite interesting how both C and As play a role in changing the relationship. C has a big role in changing the order of magnitude of tau, but the general shape of how tau depends on N and u seem to rely on both As and C. These shapes also differ from the nondimensionalized "tau" that I had plotted earlier, so it might make more sense to stick to these dimensional tau plots to think about.


fix: increase timeout when calling Neon public API (#177)

We ask our customers to integrate branch creation into their (customers') github workflows.
We don't want our customers to suffer from flaky github workflows due to Neon timeouts.
So a good developer experience needs to make sure that our documentation, sample and blogs provide instructions that will work (even in case our internal network is unstable for a few seconds).
I suggest to increase the timeout to a value that is more resilient to occasional hiccups.
60 seconds was suggested by subject matter expert based on Neon internal testing.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Monorepo spec provided without "applications" key

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
npm
If applicable, what version of Node.js are you using?
14.16.1
Amplify CLI Version
5.0.1
What operating system are you using?
Ubuntu
Amplify Categories
Not applicable
Amplify Commands
Not applicable
Describe the bug

I have multiple apps configured in a monorepo.
I have each of these apps staged with an environment connected to our master branch
I have preview enabled on each of the apps, targeting the master branch
I do not yet have an amplify.yml in the master branch
Within my pull request I have added the amplify.yml to the root of the repository
Each preview build fails to find the amplify.yml that is included in the pull request

Expected behavior
The monorepo configuration will read the /amplify.yml within the pull request and apply it to the preview build
Reproduction steps

Create a new monorepo repository
Add multiple applications into the monorepo
Use terraform to create the Amplify applications, branch per app, backend environment per branch, domain association per branch, enable previews on the branch
Create a new branch to adds amplify to each of the applications
Use amplify cli to initialize the applications by passing the appId along with the typical initialization parameters
Commit the changes
Open a pull request to the branch that has previews enabled

GraphQL schema(s)
n/a
Log output

AppId: d3127if6i267u2
2021-06-24T02:40:22.407Z [INFO]: Git SSH Key acquired
2021-06-24T02:40:22.485Z [INFO]: # Cloning repository: git@github.com:quantum-sec/platform.git
2021-06-24T02:40:22.528Z [INFO]: Agent pid 132
2021-06-24T02:40:22.553Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2021-06-24T02:40:22.754Z [INFO]: Cloning into 'platform'...
2021-06-24T02:40:23.735Z [INFO]: Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
2021-06-24T02:40:27.642Z [WARNING]: !Error: ENOENT: no such file or directory, open '/codebuild/output/src673194686/src/platform/amplify.yml'
2021-06-24T02:40:27.645Z [INFO]: Agent pid 145
2021-06-24T02:40:27.649Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2021-06-24T02:40:27.732Z [INFO]: # Retrieving environment cache...
2021-06-24T02:40:27.775Z [INFO]: # Retrieved environment cache
2021-06-24T02:40:27.775Z [WARNING]: !Cannot read property 'split' of undefined
2021-06-24T02:40:27.786Z [ERROR]: !!!Monorepo spec provided without "applications" key
2021-06-24T02:40:27.786Z [INFO]: # Starting environment caching...
2021-06-24T02:40:27.786Z [INFO]: # Environment caching completed
Terminating logging...

AppId: d3jyfteqrhguhk
2021-06-24T02:40:26.048Z [INFO]: Git SSH Key acquired
2021-06-24T02:40:26.123Z [INFO]: # Cloning repository: git@github.com:quantum-sec/platform.git
2021-06-24T02:40:26.157Z [INFO]: Agent pid 134
2021-06-24T02:40:26.192Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2021-06-24T02:40:26.460Z [INFO]: Cloning into 'platform'...
2021-06-24T02:40:27.447Z [INFO]: Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
2021-06-24T02:40:31.115Z [WARNING]: !Error: ENOENT: no such file or directory, open '/codebuild/output/src149936278/src/platform/amplify.yml'
2021-06-24T02:40:31.118Z [INFO]: Agent pid 147
2021-06-24T02:40:31.122Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2021-06-24T02:40:31.234Z [INFO]: # Retrieving environment cache...
2021-06-24T02:40:31.274Z [INFO]: # Retrieved environment cache
2021-06-24T02:40:31.275Z [WARNING]: !Cannot read property 'split' of undefined
2021-06-24T02:40:31.283Z [ERROR]: !!!Monorepo spec provided without "applications" key
2021-06-24T02:40:31.284Z [INFO]: # Starting environment caching...
2021-06-24T02:40:31.284Z [INFO]: # Environment caching completed
Terminating logging...

AppId: d1d91c9119qjjz
2021-06-24T02:40:18.197Z [INFO]: Git SSH Key acquired
2021-06-24T02:40:18.269Z [INFO]: # Cloning repository: git@github.com:quantum-sec/platform.git
2021-06-24T02:40:18.303Z [INFO]: Agent pid 131
2021-06-24T02:40:18.329Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2021-06-24T02:40:18.572Z [INFO]: Cloning into 'platform'...
2021-06-24T02:40:19.530Z [INFO]: Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
2021-06-24T02:40:23.378Z [WARNING]: !Error: ENOENT: no such file or directory, open '/codebuild/output/src345629935/src/platform/amplify.yml'
2021-06-24T02:40:23.382Z [INFO]: Agent pid 144
2021-06-24T02:40:23.385Z [INFO]: Identity added: /root/.ssh/git_rsa (/root/.ssh/git_rsa)
2021-06-24T02:40:23.467Z [INFO]: # Retrieving environment cache...
2021-06-24T02:40:23.500Z [INFO]: # Retrieved environment cache
2021-06-24T02:40:23.500Z [WARNING]: !Cannot read property 'split' of undefined
2021-06-24T02:40:23.510Z [ERROR]: !!!Monorepo spec provided without "applications" key
2021-06-24T02:40:23.510Z [INFO]: # Starting environment caching...
2021-06-24T02:40:23.511Z [INFO]: # Environment caching completed
Terminating logging...

Additional information

region
appId

ap-southeast-1
d3127if6i267u2

ap-southeast-1
d3jyfteqrhguhk

ap-southeast-1
d1d91c9119qjjz

No amplify.yml in the target branch.  This is the initial deployment and we would like to validate the previews are working as expected with the ability to update amplify.yml in the pull request, prior to being merged.
The following amplify.yml is being added in the pull request where the preview build fails.  Application names have been changed to example, otherwise each appRoot matches the AMPLIFY_MONOREPO_APP_ROOT that is set in each of the amplify apps.

/amplify.yml
version: 1
applications:
  - appRoot: apps/ngx-example1
    backend:
      phases:
        build:
          commands:
            - '# Execute Amplify CLI with the helper script'
            - amplifyPush --simple
    frontend:
      phases:
        preBuild:
          commands:
            - '# everything should be performed from the base of the monorepo'
            - cd ../../
            - npm config set cache --global .npm
            - bash .tools/build/update-nvm.sh
            - nvm exec npm ci
        build:
          commands:
            - nvm exec npm run build:prod --workspace apps/ngx-example1
      artifacts:
        baseDirectory: ../../dist/apps/ngx-example1/
        files:
          - '**/*'
      cache:
        paths:
          - .npm

    test:
      phases:
        preTest:
          commands:
            - cd ../../
            - npm config set cache --global .npm
            - bash .tools/build/update-nvm.sh || true
            - nvm exec npm ci
        test:
          commands:
            - nvm exec npx --yes<EMAIL_ADDRESS>-- nx run ngx-example1-e2e:e2e
        postTest:
          commands:
            - nvm exec npx --yes<EMAIL_ADDRESS>-- mochawesome-merge -o dist/cypress/apps/ngx-example1-e2e/mochawesome-report/mochawesome.json dist/cypress/apps/ngx-example1-e2e/mochawesome-report/mochawesome*.json
      artifacts:
        baseDirectory: ../../dist/cypress/apps/ngx-example1-e2e
        configFilePath: '**/mochawesome.json'
        files:
          - '**/*.png'
          - '**/*.mp4'
          - '**/*.html'
  - appRoot: apps/ngx-example2
    backend:
      phases:
        build:
          commands:
            - '# Execute Amplify CLI with the helper script'
            - amplifyPush --simple
    frontend:
      phases:
        preBuild:
          commands:
            - '# everything should be performed from the base of the monorepo'
            - cd ../../
            - npm config set cache --global .npm
            - bash .tools/build/update-nvm.sh
            - nvm exec npm ci
        build:
          commands:
            - nvm exec npm run build:prod --workspace apps/ngx-example2
      artifacts:
        baseDirectory: ../../dist/apps/ngx-example2/
        files:
          - '**/*'
      cache:
        paths:
          - .npm

    test:
      phases:
        preTest:
          commands:
            - cd ../../
            - npm config set cache --global .npm
            - bash .tools/build/update-nvm.sh || true
            - nvm exec npm ci
        test:
          commands:
            - nvm exec npx --yes<EMAIL_ADDRESS>-- nx run ngx-example2-e2e:e2e
        postTest:
          commands:
            - nvm exec npx --yes<EMAIL_ADDRESS>-- mochawesome-merge -o dist/cypress/apps/ngx-example2-e2e/mochawesome-report/mochawesome.json dist/cypress/apps/ngx-example2-e2e/mochawesome-report/mochawesome*.json
      artifacts:
        baseDirectory: ../../dist/cypress/apps/ngx-example2-e2e
        configFilePath: '**/mochawesome.json'
        files:
          - '**/*.png'
          - '**/*.mp4'
          - '**/*.html'
  - appRoot: apps/ngx-example3
    backend:
      phases:
        build:
          commands:
            - '# Execute Amplify CLI with the helper script'
            - amplifyPush --simple
    frontend:
      phases:
        preBuild:
          commands:
            - '# everything should be performed from the base of the monorepo'
            - cd ../../
            - npm config set cache --global .npm
            - bash .tools/build/update-nvm.sh
            - nvm exec npm ci
        build:
          commands:
            - nvm exec npm run build:prod --workspace apps/ngx-example3
      artifacts:
        baseDirectory: ../../dist/apps/ngx-example3/
        files:
          - '**/*'
      cache:
        paths:
          - .npm

    test:
      phases:
        preTest:
          commands:
            - cd ../../
            - npm config set cache --global .npm
            - bash .tools/build/update-nvm.sh || true
            - nvm exec npm ci
        test:
          commands:
            - nvm exec npx --yes<EMAIL_ADDRESS>-- nx run ngx-example3-e2e:e2e
        postTest:
          commands:
            - nvm exec npx --yes<EMAIL_ADDRESS>-- mochawesome-merge -o dist/cypress/apps/ngx-example3-e2e/mochawesome-report/mochawesome.json dist/cypress/apps/ngx-example3-e2e/mochawesome-report/mochawesome*.json
      artifacts:
        baseDirectory: ../../dist/cypress/apps/ngx-example3-e2e
        configFilePath: '**/mochawesome.json'
        files:
          - '**/*.png'
          - '**/*.mp4'
          - '**/*.html'

Looks to be related to #1880 and #1955

Should I set the buildSpec on the Amplify App (or even the Amplify App Branch) in order to get around this behavior?

If so then should it be in the monorepo format or the basic format?

Is the amplify.yml from the target branch of the pull request being used for the preview build instead of the amplify.yml from the source branch?

Is this expected behavior?
Is this behavior documented publicly?
If the buildSpec is defined directly on the Amplify App will it use it for the build if there is not an amplify.yml in the target branch?
If the buildSpec is defined directly on the Amplify App Branch will it use it if there is not an amplify.yml in the target branch?
If the buildSpec is defined directly on the Amplify App, on the Amplify App Branch, and there is an amplify.yml in the source branch without an amplify.yml on the target branch will it use the buildSpec that is defined on the Amplify App, the buildSpec defined on the Amplify App Branch or the amplify.yml in the source branch?
If the buildSpec is defined directly on the Amplify App, on the Amplify App Branch, there is an amplify.yml in the source branch, and there is an amplify.yml on the target branch will it use the buildSpec that is defined on the Amplify App, the buildSpec defined on the Amplify App Branch the amplify.yml in the source branch or the amplify.yml in the target branch?

Hi @arledesma , we are sorry to see this. Regarding to your issue,  workaround now is adding amplify.yml directly to your master branch. Our team has noticed and are working on the fix of the issue that PR build doesn't pick up correct buildSpec, it always takes target branch's buildSpec.
For your question, rule of thumb is amplify.yml file in your root folder overrides your App build specification setting in Amplify console. You can have different amplify.yml file for each branch, but if you determine to just use App build specification in console, you will have only one buildSpec for all branches. We recommend to keeping amplify.yml file in your root folder.

@victorccccc

Our team has noticed and are working on the fix of the issue that PR build doesn't pick up correct buildSpec, it always takes target branch's buildSpec.

I'm glad to hear that the issue has been acknowledged.
Could we get any type of insights as to when we may see the behavior corrected (is the issue in the backlog, scheduled for a future sprint, actively being worked?).  I don't need any specifics; I just want to be able to set expectations.

Fix is deployed to ap-southeast-1, please verify the fix.
Feel free to re-open this if issue persists

@victorccccc I am receiving this error in us-east-1. I have also tried your workaround of including amplify.yaml in the master branch.
Error: !!!Monorepo spec provided without "applications" key

Hi Gary, could you try to follow this instruction: https://docs.aws.amazon.com/amplify/latest/userguide/monorepo-configuration.html and add applications in your build spec? Thanks

@victorccccc I am receiving this error in us-east-1. I have also tried your workaround of including amplify.yaml in the master branch.
Error: !!!Monorepo spec provided without "applications" key

Hi Gary, could you try to follow this instruction: https://docs.aws.amazon.com/amplify/latest/userguide/monorepo-configuration.html and add applications in your build spec? Thanks

Here is the build spec that I've been using:
version: 1
applications:
  - appRoot: web_app_build/
    frontend:
      phases:
        build:
          commands: []
      artifacts:
        baseDirectory: /
        files:
          - '**/*'
      cache:
        paths: []

This same build spec was used for previous builds without any issues.

@victorccccc I am receiving this error in us-east-1. I have also tried your workaround of including amplify.yaml in the master branch.
Error: !!!Monorepo spec provided without "applications" key

Hi Gary, could you try to follow this instruction: https://docs.aws.amazon.com/amplify/latest/userguide/monorepo-configuration.html and add applications in your build spec? Thanks

Here is the build spec that I've been using:
version: 1
applications:
  - appRoot: web_app_build/
    frontend:
      phases:
        build:
          commands: []
      artifacts:
        baseDirectory: /
        files:
          - '**/*'
      cache:
        paths: []

This same build spec was used for previous builds without any issues.

Hi, can you share your AppId?

@victorccccc I am receiving this error in us-east-1. I have also tried your workaround of including amplify.yaml in the master branch.
Error: !!!Monorepo spec provided without "applications" key

Hi Gary, could you try to follow this instruction: https://docs.aws.amazon.com/amplify/latest/userguide/monorepo-configuration.html and add applications in your build spec? Thanks

Here is the build spec that I've been using:
version: 1
applications:
  - appRoot: web_app_build/
    frontend:
      phases:
        build:
          commands: []
      artifacts:
        baseDirectory: /
        files:
          - '**/*'
      cache:
        paths: []

This same build spec was used for previous builds without any issues.

Hi, can you share your AppId?

d313d3b5r9k86x

Hi @garysm , I noticed you are using customHttp.yml.  Can you also try to add applications and appRoot by following this instruction: https://docs.aws.amazon.com/amplify/latest/userguide/custom-headers.html#custom-header-YAML-format ?  thanks