resolve fsevents to 1.2.9 to fix a build issue

When trying to run yarn on node 12 we get an error:
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2

We don’t directly use fsevent, but chokidar does. Watchpack includes chockider and webpack includes watchpack…
Watchpack in version 2 (still in beta) no longer uses chokidar, but we are stuck with 1.6 - this is what webpack has specified. So to fix the issue with building on node v12 I’ve provided a resolve param in the package.json that specifies that we want to use fsevent 1.2.9 and that version builds properly on node v12

This fails with the message
error<EMAIL_ADDRESS>The platform "linux" is incompatible with this module. error Found incompatible module.
Can you check this?


Shift of data in X and Y direction by 1 pixel while downloading NASADEM data in EPSG:4326

The download function at the following link does not consider crs transformation parameter, which is causing shift in downloaded data.
https://github.com/dugalh/geedim/blob/main/geedim/download.py#L686

@dugalh Thank you.


⚠ ESPN has degraded performance

In 91cbdbe, ESPN (https://espn.com) experienced degraded performance:

HTTP code: 200
Response time: 2615 ms

Resolved: ESPN performance has improved in 97d99b7.


Force segment user id to be a uuid

Description
This makes Airbyte
Type of change

[ ] Bug fix
[ ] New feature
[ ] Breaking change

Related issues

Fix #1

Migration notes

Describe migration notes if any

Extra info

Add any additional information

Great! As long as we hash it - it's all good.


Envoy CPU pprof broken due to tcmalloc

We recently moved to tcmalloc. This breaks Envoy CPU profiling support which is critical for operations. We should revert or bring CPU profiling functionality to tcmalloc in Envoy

System perf should be capable of performing CPU profiling. tcmalloc is a memory allocator and has nothing to do with CPU profiling. @briansonnenberg did you have a chance to try perf to CPU profile Envoy?

https://www.envoyproxy.io/docs/envoy/latest/operations/admin#post--cpuprofiler "Requires compiling with gperftool"
perf is not really equivilent IMO. It requires root access on the node, struggles to get symbols, and doesn't support the standard pprof format unless you jump through hoops (manually building https://github.com/google/perf_data_converter which requires bazel, etc -- note that gLinux comes with this OOTB to hide this pain).
https://github.com/istio/istio/wiki/Analyzing-Istio-Performance#profile has docs on how it works for below 1.22

Linux perf is the preferred long term direction, hence, modern tcmalloc dropped the signal-based CPU profiling. Some features (overload manager) are better integrated with tcmalloc, so sticking with the outdated perftools will make Istio use a build of Envoy inconsistent with the other production usages and prevent the use of those features.
It might be a good idea to change the debug variant to use gperftools if there's a need to debug in production.

Why is perf the preferred long term solution? It seems like everything else is going the opposite direction - Golangs pprof, https://grafana.com/docs/pyroscope/latest/configure-client, most rust apps are using https://github.com/tikv/pprof-rs. I thought Google itself internally as well?

AFAIK Google wide profiler uses perf record and upstream kernel has been getting patches to make it more scalable. The rationale that's documented for removing cpuprofiles from tcmalloc was that ebpf/perf events are more precise since signal interrupts influence the program under test. My feeling was that Linux has finally moved on from the state of disrepair in performance tooling (e.g. removal of frame pointers) back to where it was circa early 2000s :)

Well regardless of Googles internal infrastructure, it still remains that we went from having an easy to access http endpoint that gives reliable profiles in the ideal format, to having to get root into the node, run a program that is probably not on the node and hard to get (need to download the per-kernel version etc), that struggles with symbols due to containerization, and does not output in a readily usable format.
I don't think this is a very good tradeoff for Istio users.

I don't think these are fundamentally hard issues - yes, we should improve the user experience for the narrow set of customers who really need to delve into the Envoy internals. The problems you mentioned are solvable: why can't we use a debug sidecar container to simplify the experience?
Any vendor is free to ship Envoy with gperftools and not have some features from Envoys. We added it to OSS because those features would be blocked completely from development with gperftools.

Documented in https://github.com/istio/istio/wiki/Analyzing-Istio-Performance#istio-122-and-newer. In the future when removing features from Istio it would be good to discuss them with the community and work on updating the documentation.


#276 fix setUserAgent does not setter

if I understand correctly your message my answer: no
Because function setUserAgent is public. I use it. But it does nothing.

I think you misunderstood.
Line 89 is where we initially set $this->userAgent, but this PR now sets it within the setUserAgent() method, so it is getting set twice for no real reason.
Unless i'm misunderstanding something?!


refactor: add logout errors into fallback

Some minor refactors.

Coverage increased (+0.2%) to 85.392% when pulling 6a4653098d43b58a1fa968b54b2519911385a394 on refactor/controller-fallback into d5bb231ee12fc45dfccae34ca145070c2868c74a on master.


Integration compatibility with FCM

Indentation formatting and minor refactoring.

This PR seems to have some problems.

I suggest you to create a new branch from master and add your code there. Then open another PR :-)

I see. Noted. Apologies for my ignorance. The branch I am on is a branch
from 2.18.x. Could this be the reason of the conflict?
Regards, Allan.
Sent from Gmail mobile.
On 27 Oct 2016 21:58, "Andrea Cosentino"<EMAIL_ADDRESS>wrote:

I suggest you to create a new branch from master and add your code there.
Then open another PR :-)
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/camel/pull/1228#issuecomment-256648648, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ADSRE9hefVOt96ofvzzhqoceS7fzCgzVks5q4K4RgaJpZM4KiXMi
.


Pending VMs do not appear to be counted in the usage data provided to the UI by the server.

Pending VMs are those running for less than 15min and still without run id.

The underlying ?media=xml data matched the displayed values.
NB: For reference, the Pending flag in the bottom VMs table is handled directly by the UI module, not be the server. The corresponding Vm is flagged as Pending directly by the UI module (not by the server) and displayed as such.

This is not a bug. It appeared as a bug because of slipstream/SlipStreamUI#579


Function on result / on end?

Hi @penguin86, @danieleguiducci, @
is it possible to run a function after the speech is finished?
Thanks a lot.

HI
you can use:
advtts.speak(' you text');
advtts.onChange(function () {
if (!advtts.speaking()) {
// end
}
});

Hi @danieleguiducci
thank you. this is working on IOS but not on android.
could you take a look on it?

@desmeit @danieleguiducci
Adding send("stopSpeak"); after line 78 in advtts.java should resolve the problem


fix: errors on an avatars

What does this PR change?
Attempts to fix #762
There is a rare case on which the wearable promise result has no value when trying to create the avatar.
Also the task that waits for the avatar preview to be loaded was not being canceled when it was disposed.
Based on the report this errors are fixed:
InvalidOperationException: Nullable object must have a value.
  at System.Nullable`1[T].get_Value () [0x00000] in <00000000000000000000000000000000>:0
  at ECS.StreamableLoading.Common.AssetPromiseExtensions.SafeTryConsume[TAsset,TLoadingIntention] (ECS.StreamableLoading.Common.AssetPromise`2[TAsset,TLoadingIntention]& promise, Arch.Core.World world, ECS.StreamableLoading.Common.Components.StreamableLoadingResult`1[TAsset]& result) [0x00000] in <00000000000000000000000000000000>:0
  at DCL.AvatarRendering.AvatarShape.Systems.AvatarInstantiatorSystem.InstantiateNewAvatar (Arch.Core.Entity& entity, DCL.AvatarRendering.AvatarShape.Components.AvatarShapeComponent& avatarShapeComponent, DCL.Character.Components.CharacterTransform& transformComponent) [0x00000] in <00000000000000000000000000000000>:0
  at Arch.SystemGroups.WorldInjectionExtensions.AddAllSystems (Arch.SystemGroups.ArchSystemsWorldBuilder`1[Arch.Core.World]& worldBuilder, DCL.DebugUtilities.IDebugContainerBuilder debugContainerBuilder, DCL.Web3.Authenticators.IWeb3VerifiedAuthenticator web3Authenticator, MVC.MVCManager mvcManager, ECS.IRealmData realmData) [0x00000] in <00000000000000000000000000000000>:0
  at DCL.AvatarRendering.AvatarShape.Systems.AvatarInstantiatorSystem.Update (System.Single t) [0x00000] in <00000000000000000000000000000000>:0
  at ECS.Abstract.BaseUnityLoopSystem.Update (System.Single& t) [0x00000] in <00000000000000000000000000000000>:0
  at Arch.SystemGroups.ExecutionNode`1[T].Update (T& t, System.Boolean throttle) [0x00000] in <00000000000000000000000000000000>:0
  at Arch.SystemGroups.SystemGroup.Update (Arch.SystemGroups.UnityBridge.TimeProvider+Info& timeInfo) [0x00000] in <00000000000000000000000000000000>:0
  at Arch.SystemGroups.DefaultSystemGroups.PostRenderingSystemGroup.Update () [0x00000] in <00000000000000000000000000000000>:0
  at Arch.SystemGroups.SystemGroupAggregate.TriggerUpdate () [0x00000] in <00000000000000000000000000000000>:0

NullReferenceException: Object reference not set to an instance of an object.
  at DCL.CharacterPreview.CharacterPreviewController.WaitForAvatarInstantiatedAsync (System.Threading.CancellationToken ct) [0x00000] in <00000000000000000000000000000000>:0
  at Cysharp.Threading.Tasks.UniTaskCompletionSourceCore`1[TResult].TrySetResult (TResult result) [0x00000] in <00000000000000000000000000000000>:0
  at Cysharp.Threading.Tasks.UniTask+YieldPromise.MoveNext () [0x00000] in <00000000000000000000000000000000>:0
  at Cysharp.Threading.Tasks.Internal.PlayerLoopRunner.RunCore () [0x00000] in <00000000000000000000000000000000>:0

How to test the changes?

Follow issue steps

Our Code Review Standards
https://github.com/decentraland/unity-renderer/blob/master/docs/code-review-standards.md

When logging in for the second time, this issue keeps taking place after having triggered this with another build and coming back to this one: https://github.com/decentraland/unity-explorer/issues/762
Video showing this issue:
https://github.com/decentraland/unity-explorer/assets/146749313/07f4f442-36f3-4614-b661-9f1619823a22
Logs:
Logs 28% issue.log

🟡 There is an issue now on the build (checked main to confirm) in which, by logging in with a new account and enter the client too fast, it crashes when it starts loading.
Player.log


Upgrade stripe version

Update the Stripe payment integration:

Revert legacy Stripe plugin code.
Upgrade Stripe to version 11.3.
Replace deprecated functions with updated equivalents.
Add Stripe signature verification on webhook

Summary by Sourcery
Upgrade the Stripe integration to version 11.3, refactor payment methods for better maintainability, and enhance security with Stripe signature verification on webhooks. Improve error handling and add documentation for setting up Stripe payment integration.
New Features:

Introduce Stripe signature verification on webhook to enhance security.

Enhancements:

Upgrade Stripe integration to version 11.3, replacing deprecated functions with updated equivalents.
Refactor payment methods to use a more modular and maintainable structure, including the introduction of new classes for different payment methods.
Improve error handling and logging for Stripe-related operations to provide better insights and debugging capabilities.

Documentation:

Add a new document 'Stripe Payment Settings Instruction' to guide users on setting up Stripe payment integration.

Thank you. Please do the following:

Check sourcery comments and fix where applicable.
Provide screenshots in this PR showing the changes you made.
Research online how to make a screenshot of an entire web page not just the visible screen and adjust split screens in the documentation.
Outline where the webhook info needs to be added into the eventyay configuration. I do not see the info in the documentation. Am I missing something?

hi @mariobehling

Pushed commit to resolve that
Attatched a few of screenshots of Stripe plugin. But most of changes at Backend
Updated images and guideline. If you have any example, it is helpfull for me to follow.
You can see step 3 in document

@duong-dsg In the documentation you listed the links you are using. Now I understand why it looks different. You are using Stripe workbench which is a developer tool. It is not intended for production. Please adjust the documentation of webhooks. Use chatgpt to guide you maybe.

@duong-dsg In the documentation you listed the links you are using. Now I understand why it looks different. You are using Stripe workbench which is a developer tool. It is not intended for production. Please adjust the documentation of webhooks. Use chatgpt to guide you maybe.

I'll research more documentation and update guideline soon

Hi @mariobehling
As I see on Stripe documentation:

Workbench replaces the existing Developers Dashboard, and we enable Workbench by default for all new Stripe accounts. Configure the setting from the Developers settings in the Dashboard.

and Stripe blog
Stripe has introduced Workbench, a new tool in the Dashboard that makes it easier for developers to debug, monitor, and streamline their Stripe web development.
It will be released in 2024, chatgpt may not have updated the information yet.
I think Workbench is just a tool to manage and view Stripe integrations (in a dashboard). I haven't found any documentation that says it doesn't work in production. I believe the distinction between test and production environments is the API keys (test/live)


Update CLI extensions available doc

Update CLI extensions available doc.
Triggered by Azure/azure-cli-extensions - TRAVIS_BUILD_ID=417461808
https://github.com/Azure/azure-cli-extensions/commit/18b59950826d699a5b032606e2430395c4bbc4d2

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-ref-conceptual/azure-cli-extensions-list.md
:white_check_mark:Succeeded
View (azure-cli-latest) View (azure-cli-2017-03-09-profile)

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Unify commerce Core

[ ] #429
[ ] https://github.com/vercel/commerce/issues/368

Closing in favor of https://github.com/vercel/commerce/issues/515


JS Optional chaining throws a webpack compilation error

I tried to use https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Optional_chaining in in action but I got a webpack compilation error: unexpected token.
Are there other JS expressions or feature that are currently not supported ?

Hi @icaraps ,
Let's ask the team, cc@purplecabbage @shazron @rajarju .
I feel like this could be more related to webpack itself than to the app plugin, wdyt?


change button size from px to rem

Proposed changes

Screenshots (if appropriate) or codepen:

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to change).

Checklist:

[x] I have read the CONTRIBUTING document.
[x] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

Hi, this project is no longer maintained! The community-managed fork is still being maintained. Please open an issue there instead. Thanks! https://www.github.com/materializecss/materialize


Question about RDG collection sessions

[Enter feedback here]

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

ID: 61df48bb-a963-b1f0-8f64-b55d0bd6904c
Version Independent ID: 677de59f-a222-8905-11c0-a3ac619d8b56
Content: Integrate RDG with Azure MFA NPS extension - Azure Active Directory
Content Source: articles/active-directory/authentication/howto-mfa-nps-extension-rdg.md
Service: active-directory
Sub-service: authentication
GitHub Login: @iainfoulds
Microsoft Alias: iainfou

@elvirk Hope you have self resolved question about RDG collection sessions and hence closed the issue. Thanks for the update.


Few Code Smells

Description
Disclaimer
This are my own opinions, if you don't like it don't use it and move on. This suggestions will probably trigger a refactor, maybe even a huge one. Keep in mind that this are the things that I found while scouting the code. I do not criticize the code or it's writers. However, I will point out stuff I don't like.
Few important notes

I have read the contributing.md file and it was not written as okay or to disregard.
Every point will be discussed in the "Concerned Code" section.
Parts that are minor and don't really affect the code just makes it look worse marked with [MINOR]. These should be semantic changes only meaning they would not affect the running code.
If you find reasons to ignore things listed here. Please tell me why.
I am against this interface driven architecture but due to the project depending on it I would disregard it.

Main Problems

Interfaces with property inside them. This one is a more personal take, but I would definitely use an abstract class here. This just breaks DRY and forces everyone to implement the public property inside the class. I'll provide examples. Another code smell that arises from this is the virtual properties. Also, Why would you need this? An abstract class would have solved it as you wouldn't need to override properties and you could've defined them as protected.
[MINOR] Inconsistencies when defining properties. In some places they are prefixed with public in other they are not. Just adds more text with no value that might even confuse some people. Especially in interfaces, The default access modifier
[MINOR] Weird Naming in some places

Concerned code
Properties inside interfaces
Let's talk about a core interface, The IStorable interface. Located at src/Files.Core.Storage/Storables/IStorable.cs sits the most important core interface of this project. This interface does not contain any methods, but it does contains properties. The reason C# allows properties inside interfaces are because properties are get-set methods behind the scenes. However, there is a better alternative to this. Allow me to introduce, The Abstract Class. Why does it matter?
First off all, properties are required to have a public getter, but no restrictions on it's setter. This means that every class that implements this interface have to define it for itself. Which leads into my second point, Code Repetition. Having properties inside interfaces causes massive code repetition. Every class that implements this interface will have to re-declare the property. This would also solve the virtual properties. Overriding a property seems kinda weird and is also redundant in some cases (like in the FTPStorable).
Access Modifier Inconsistencies [MINOR]
In some places you favor specifying the access modifier explicitly, in some other places you don't. Doesn't really matter what you choose, just pick one and go with it. Keep in mind, that the default access modifier inside interfaces is public (a private interface is kinda useless isnt it?) In the IStorable interface you have properties one with an explicit access modifer, the other - implicit. Both mean the same thing, the only outcome is confusion. It seems like in other interface you chose to remove the access modifier so I suggest to go with that.
IStorable
public interface IStorable
{
    public string Id { get; }
    string Name { get; }
}

Weird Naming [MINOR]
When going over the project I had hard time understanding the naming.  Even some folders have unrelated or misleading names. In the Files.Core.Storage project inside the Storables directory, you have a directory named ExtendableStroage What does that even mean? The interfaces inside it are called IFileExtended. There is a difference between and extendable file and an extended interface for a file. I still don't know which is which.
Gains

Better code readability
Better code clarity
Better practices

Requirements
Going over the code and manually changing stuff. To be honest, might be too hard.
Comments
No response

Thank you for the feedback!
I'm only the person who work on this implementation as of now so let me respond your concerns.
The current implementation has some problems including what you mentioned here. My latest research and idea is in #8974, which is also still under heavy construction and there's still a lot of room to improve but is much better.

Interfaces with property inside them.
Code Repetition

Every storable item has its unique name to identify. This is not limited just to files and folders but also properties and any other storable objects on file systems. Regarding ID, I think we don't need it and I'd remove in the future.
Regarding the code repetition, IStorable is the greatest farther of any storable objects. And file system classes NativeStorable (natively supported file systems such as NTFS and FAT32), FtpStorable, SftpStorable and ArchiveStorable (example of virtual storage which doesn't exists in file system) implement it. There aren't so many. My preference of using abstract is when I put actual value in abstracted properties from methods in abstract class. I think your concern also can be said to abstract methods and abstract properties that forces descendants to implement.
Regarding storage properties (IStorageProperty/IStorageProperties) such as bitrate and git commit message text, which is still not even implemented. I completely agreed. There're so many properties that I can't force descendants to implement. Therefore, my latest opinion is to just have a method to retrieve either a group of properties or single properties (IStorageProperties.GetProperty, IStorageProperties.GetProperties).

Access Modifier Inconsistencies

I recognize this issue. We should make all public objects internal in Files.App, and public be public in other projects.
All objects have to have explicit modifier and it shouldn't exist in interfaces. Regarding this, everyone can open a PR and we'll review.

Weird Naming

I realize your concerns. I'll think of better names.

Merging with #4180 and #8974.
Our implementation bases on OwlCore.Storage project which can be found on GitHub.

Thank you for your fast reply. I just want to clarify regarding the abstract properties. When I mentioned abstract classes I was talking about an abstract class containing a field, not an abstract property. This would not force the child to re-implement and will define a standard.
abstract class Parent
{
    public string MyProp { get; protected set; }
}

class Child : Parent
{
    // doesn't need to re-declare MyProp
}

interface IBehavior
{
    string MyProp { get; }
}

class BehaviorParticipant : IBehavior
{
    public string MyProp { get; private set; } // Has to re-declare the property AND declare the setter
}

Just hit me up if it's intentional or not.

Actually intentional.

My preference of using abstract is when I put actual value in abstracted properties from methods in abstract class.

Also the most importantly the purpose of IStorable is to provide very very fundamental property - Name.
When you don't want other things but just name, you can just use IStorable instead of INativeStorable. Name is platform independent. Note that the purpose of the project is provide abstracted storage layer to support many file systems in the future.


chore(main): release 0.1.4

:robot: I have created a release beep boop
0.1.4 (2024-05-01)
Bug Fixes

Add HTML component (#243) (0c2932b)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Zero-True/zero-true/releases/tag/v0.1.4 :sunflower:


Fix The spending password is wrong label in Unlock Wallet route

Problem:

The spending password is wrong is displayed on Unlock Wallet route even if user didn't provide a wrong password.

closes: #197
Issue ticket number and link:

Ticket Number: [ 197 ]
Link: [ https://github.com/palladians/pallad/issues/197 ]

Evidence:
https://www.loom.com/share/0499b3a84ed444cda04d904300c4a1f6

Acceptance Criteria

[x]  The label is only visible after user provided a wrong password.

Hi @mrcnk, Please review this PR.


CI: Use 2.4.6, 2.5.5, 2.6.2, jruby-<IP_ADDRESS>

This PR only updates the CI matrix to the latest generally available Ruby versions.
Source for version numbers: https://github.com/rvm/rvm/blob/master/config/known

test is failing with 2.5.5

@olleolleolle I have changed travis so it updates rubygems and bundler, and changed gemfile to use bundler 2, can you rebase?

@scambra Rebased, squashed!

@olleolleolle do you know if it's possible to install openjdk 8 in travis? jruby 9.2 doesn't work with openjdk 7 so test is failing


Add PR labeler

What does this PR do?
Adds a basic labeler that can be extended further

Unfortunately, the labeler has to be committed blindly at first

Merging as is, to be debugged in subsequent PRs


Jbaker/new accordion

Alaska Airlines Pull Request
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
Fixes: #28
Summary:
Complete rebuild of the auro-accordian using the latest version of the generator.
Type of change:
Please delete options that are not relevant.

[x] New capability
[x] Revision of an existing capability
[x] Infrastructure change (automation, etc.)
[ ] Other (please elaborate)

Checklist:

[x] My update follows the CONTRIBUTING guidelines of this project
[x] I have performed a self-review of my own update

By submitting this Pull Request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
Pull Requests will be evaluated by their quality of update and whether it is consistent with the goals and values of this project. Any submission is to be considered a conversation between the submitter and the maintainers of this project and may require changes to your submission.
Thank you for your submission!
-- Auro Design System Team

I am getting this error when running a build

@jason-capsule42 I see this when I run a build locally?
src/style.scss
 1:1  ✖  Unknown word  CssSyntaxError

1 problem (1 error, 0 warnings)

ERROR: "scssLint" exited with 2.

@jason-capsule42 I see this when I run a build locally?
src/style.scss
 1:1  ✖  Unknown word  CssSyntaxError

1 problem (1 error, 0 warnings)

ERROR: "scssLint" exited with 2.

This has been resolved.

I am getting this error when running a build

This has been resolved.

Surge demo deployment succeeded! 🚀🚀🚀
Auro Web Component Generator

@Izook there is an issue with the deployed demo? In the browser I see the following error
Uncaught ReferenceError: initaccordionIndexExamples is not defined
    at (index):50:7

Also, why does the link for the demo say Auro Web Component Generator, can we change that?
Assuming that none of this has anything to do with this repo and we should make an issue in the generator?

Surge demo deployment succeeded! 🚀🚀🚀
Auro Web Component Generator

@Izook there is an issue with the deployed demo? In the browser I see the following error
Uncaught ReferenceError: initaccordionIndexExamples is not defined
    at (index):50:7

Also, why does the link for the demo say Auro Web Component Generator, can we change that?
Assuming that none of this has anything to do with this repo and we should make an issue in the generator?

@blackfalcon The Uncaught ReferenceError I should be able to fix. The Auro Web Component Generator does come from the title tag in the index.html demo file. I can update it here to say something else but it would also make sense to change to say something else in the generator so we can have a consistent message in all our demos.

Other issues found: *npmignore and gitignore files were not updated

stylelintrc was not updated
autoAssign workflow file was not added

Resolved


POST /train?name=my_model trains a model, but can't access with /parse or /status

rasa NLU version:
Bleeding edge / github clone
Used backend / pipeline (mitie, spacy_sklearn, ...):
mitie
Operating system:
Linux Ubuntu 16.04
Issue:
First I start rasa as a python server:
python -m rasa_nlu.server -c config_file.json
Then I start a node.js server, in which I POST to the rasa server: /train?name=my_model
The model is trained successfully, and can be found in the models directory.
However, POST /parse with an extra model:"my_model" param and GET /status can't access the model.
The docs for /train says "If you want to name your model to be able to use it during parse requests later on, you should pass the name /train?name=my_model". So I was expecting /train to load the model so I could use it immediately without restarting the python server. Is this a bug or am I missing something?
Content of configuration file (if used & relevant):
{
  "pipeline": "mitie",
  "path" : "./models",
  "mitie_file": "data/total_word_feature_extractor.dat"
}

Strange, because looking at the corresponding code here is what happens. Once the training is done, the model is created but is not loaded in memory. Then comes a parse request. If it specifies a model name (like you did) it'll look for it in memory, if it cannot be found (which is the case after training) it'll load it from the path made of the path value in your config file and the model name you specified. So it should work just fine.
What error do you have exactly? Do you wait for the training response from the server before doing a parse request?

Weird indeed. It's working now, although I don't believe I changed anything.
Either way - it seems this is a non-issue. Perhaps it makes more sense to load the model on /train though? Just seems more intuitive, and may help with speed on the first call to /parse if the model is large.

Yep this is part of some weirdo's PR

thanks :)


Resize columns, make them manually resizeable

Overview
TSIA
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Refactoring / Documentation
[ ] Version change

Checklist:

[X] My code follows the style guidelines of this project
[X] I have performed a self-review of my own code
[X] I have made corresponding changes to the documentation
[X] New and existing unit tests pass locally with my changes

included in #1924


add all contributors

@all-contributors
please add @juancarlosfarah  for code, test, doc, bug, ideas, review, userTesting, maintenance, design.
please add @eamico for code, ideas, mentoring, review, userTesting.
please add @hannatolle for code, test, doc, bug, ideas, review, userTesting.
please add @ss1913 for userTesting, ideas, bug, promotion.

https://github.com/all-contributors
please add @juancarlosfarah for code, test, doc, bug, ideas, review, userTesting, maintenance, design.
please add @eamico for code, ideas, mentoring, review, userTesting.
please add @hannatolle for code, test, doc, bug, ideas, review, userTesting.
please add @ss1913 for userTesting, bug, promotion.

Retrying:
@all-contributors
please add @juancarlosfarah for code, test, doc, bug, ideas, review, userTesting, maintenance, design.
please add @eamico for code, ideas, mentoring, review, userTesting.
please add @hannatolle for code, test, doc, bug, ideas, review, userTesting.
please add @ss1913 for userTesting, ideas, bug, promotion.

https://github.com/all-contributors
please add @hannatolle for code, test, doc, bug, ideas, review, userTesting.
please add @ss1913 for userTesting, ideas, bug, promotion.

@all-contributors
please add @hannatolle for code, test, doc, bug, ideas, review, userTesting.
please add @ss1913 for userTesting, ideas, bug, promotion.


Add Dockerfile

Add a Dockerfile for using dynalite w/o nodejs.
Unlike #64, this builds from source allowing integration with docker hub by using automated builds.
This would result in having docker hub building and hosting a docker images for each tag and the current latest master/HEAD on each push.
Running dynalite in docker would look like this:
docker run --rm -p 4567:4567 dynalite

Like the real dynalite executable parameters are available:
docker run --rm -p 8123:8123 dynalite --port 8123

I'd be amenable to this, may need a few tweaks though. It's not clear from that Dockerfile how ports are configurable there (although to be honest, I'm no Docker expert). Would def want to see some tests too, and probably something around publishing to Docker Hub (which should be easy enough with GitHub Actions). wdyt?


Demo website broken on Edge

Link to PDF file (or attach file here):
Configuration:

Web browser and its version: Microsoft Edge 40.15063.0.0
Operating system and its version: Windows 10 10.0.15063 Build 15063
PDF.js version: not sure, but it's the version currently used on the demo website
Is an extension: no

Steps to reproduce the problem:

Open Microsoft Edge
Navigate to the demo website : https://mozilla.github.io/pdf.js/web/viewer.html

What is the expected behavior? (add screenshot)
display the sample pdf file as on other brothers
What went wrong? (add screenshot)
An error occurs : Function expected, pdf.worker.js (1144,1)

Link to a viewer (if hosted on a site other than mozilla.github.io/pdf.js or as Firefox/Chrome extension):

I'm wondering if the issue might be that IE Edge is passing this check: https://github.com/mozilla/pdf.js/blob/master/src/shared/streams_polyfill.js#L16, despite not actually implementing proper streams support?
@sandorfr Could you please check, in the console, what typeof ReadableStream returns in Edge?

Thanks a lot for the quick fix.


bug: flickering and jitter due to Refined Github

Testing this out with ViolentMonkey on Firefox, and I'm seeing the following:

I also use the Refined Github extension, which adds various features, and it looks like there might be some conflicts there, that may be worth calling out in the readme and/or script, as I imagine a lot of folks also use Refined Github.
Disabling this specific feature in Refined Github resolves the flickering issues:

Just in case others run into this issue as well!

This is caused by the MutationObserver, which is added so that the feed doesn't get refreshed by GitHub to point to the new feed (it tries every 60 seconds)... could potentially fix it by adding logic in the callback passed to the observer to only do things if there are added nodes, since I suspect Refined GitHub only removes nodes.

Potential fix - could you try changing the observer initialization to this?
    const observer = new MutationObserver((mutations) => {
        if (mutations.some(m => m.addedNodes.length)) {
            fixDashboard();
        }
    });

Tested -- seems to make the jitter worse (the entire feed viewport, not just the bottom portion).

For reference, this is the source for the "hide own stars" feature in Refined Github.

Unfortunate, going to be difficult to debug this one, I can't reproduce, possibly don't have enough other events in my newsfeed... Might be able to do something like this?
    const observer = new MutationObserver(() => {
        if (displayedDashboard.querySelector(".js-feed-item-component")) {
            fixDashboard();
        }
    });

That looks to work perfectly, no more jitter.


A peace of mind...

Properly organize and document HTML and both CSS codes. Comments, comments, comments!

Task Complete.


[WIP] First proposal for a utility to scan cache

Following issue https://github.com/huggingface/huggingface_hub/issues/972.
This is a draft of what the scan of the cache directory could look like. At the moment there is only a scan_cache method that returns structured information about the cache.
I think the most important question is what information do we want in HFCacheInfo, CachedRepoInfo, CachedRevisionInfo and CachedFileInfo objects. In theory, the current content would be enough to make the utils that @sgugger described in the issue. Another information that I have not yet scanned is "last_updated" timestamp. I guess that could be useful to "prune" a repo to keep only the latest downloaded version (to confirm...).
Any suggestion / feedback / comment is very welcomed as this is a draft (ping @osanseviero @sgugger @LysandreJik @mariosasko who showed interest in this feature).

I also made a quick and dirty script (scan.py) to show what a CLI command could display:
(.venv310) ➜  huggingface_hub git:(972-utility-to-list-cache) python scan.py
Datasets:
  glue 113.6KiB (15 files)
    /Users/lucain/.cache/huggingface/hub/datasets--glue
    Revisions:
        9338f7b671827df886678df2bdd7cc7b4f36dffd: 2.4.0, main
          95.4KiB (14 files)
        f021ae41c879fcabcf823648ec685e3fead91fe7: 1.17.0
          95.5KiB (14 files)
  google--fleurs 61.9MiB (6 files)
    /Users/lucain/.cache/huggingface/hub/datasets--google--fleurs
    Revisions:
        129b6e96cf1967cd5d2b9b6aec75ce6cce7c89e8: refs/pr/1
          24.8KiB (3 files)
        24f85a01eb955224ca3946e70050869c56446805: main
          61.8MiB (4 files)

Models:
  bert-base-cased 1.8GiB (13 files)
    /Users/lucain/.cache/huggingface/hub/models--bert-base-cased
    Revisions:
        a8d257ba9925ef39f3036bfc338acf5283c512d9: main
          1.3GiB (9 files)
        378aa1bda6387fd00e824948ebe3488630ad8565: (detached)
          1.4GiB (9 files)
  t5-small 925.8MiB (11 files)
    /Users/lucain/.cache/huggingface/hub/models--t5-small
    Revisions:
        98ffebbb27340ec1b1abd7c45da12c253ee1882a: refs/pr/1
          692.6MiB (6 files)
        d78aea13fa7ecd06c29e3e46195d6341255065d5: main
          925.8MiB (9 files)
        d0a119eedb3718e34c648e594394474cf95e0617: (detached)
          463.3MiB (6 files)

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.

Side note: this only scans the "new" cache layout and makes some assumptions on the expected structure. I am not yet sure all weird cases are handled. Especially:

Is it possible to have a blob that is never referenced (no symlink to it ?)
Is it possible that a symlink refers to a non-existing blob ?
Is it possible that a blob is not fully downloaded ?
Is there a cache lock that I should be aware of ? If someone is scanning + downloading at the same time, results might not be accurate.

@osanseviero If you have time could you try to checkout to this branch and run python scan.py and copy-paste the output ? I'd like to know if you get any errors. I made some tests with my local cache but it's a very recent and tiny cache. Would be good to get feedback from someone that is more likely to have more discrepancies in its cache.
If too complicated, I will update the PR with a proper CLI when I have time.

I got the following error
python scan.py
Error while scanning /home/osanseviero/.cache/huggingface/hub/models--bert-base-cased: Snapshots dir doesn't exist !
Datasets:

Models:
  osanseviero--wine-quality 268.0KiB (5 files)
    /home/osanseviero/.cache/huggingface/hub/models--osanseviero--wine-quality
    Revisions:
        974ee1d10a13d2cb802c5b9c26b504a9c58a09af: main
          268.0KiB (5 files)

@osanseviero Thanks for trying it out !
I am not exactly sure what happened here (surely a cache folder without snapshots folder, but why ?).
I will update the script to make it robust to errors (just log and ignore them) + add better error messages. I'll ping you when I have a better version to test.

About the pruning, IMO we can keep it for later and/or leave it as the user's responsibility. It will be hard to find a single strategy that works well to decide what to prune, so it should maybe be up to the user to implement. For instance, you mention lastModified (of a file on disk?) but i have an old snapshot of gpt2 I use all the time... Or you have a lastFileAccess file stat on some OSes but not sure it's robust either...

@julien-c Yep I talked about lastUpdated date because it's the only robust-enough timestamp that I thought of. I saw it more as an information to display to the user rather than a value to decide if we want to delete the file or not.
In general pruning/cache management will be done separately. My opinion is that we can have an helper to delete a specific revision from a specific repo_id. The helper deletes the blob files that are symlink-ed only to this revision so that other revisions are still valid. In addition it also delete and refs that points to this revision. This helper is generic-enough so that we don't take any decisions on what to delete and the user can define itself about its pruning stategy.
def delete_cached_revision(repo_id: str, revision: str) -> None:
    ...

Another question/comment: maybe the CachedRepoInfo should also expose a dict of refs, or maybe a helper to get a CachedRevisionInfo from a ref

Good idea, I've added a CachedRepoInfo.refs property that computes the mapping "ref -> revision info"

I took the feedback, made some changes and added a proper command to the existing huggingface-cli tool. I also changed printed output to have something more tabular and grep-able. This is most likely the final version of this tool for this PR. If you have any feedback, please tell me.
In the meantime I will write documentation and docstrings for this tool.
➜ huggingface-cli scan-cache --help
usage: huggingface-cli <command> [<args>] scan-cache [-h] [--dir DIR] [-v]

options:
  -h, --help     show this help message and exit
  --dir DIR      cache directory to scan (optional). Default to the default HuggingFace cache.
  -v, --verbose  show a more verbose output

➜ huggingface-cli scan-cache
REPO ID                     REPO TYPE SIZE ON DISK NB FILES REFS                LOCAL PATH
--------------------------- --------- ------------ -------- ------------------- -------------------------------------------------------------------------
glue                        dataset         116.3K       15 2.4.0, main, 1.17.0 /Users/lucain/.cache/huggingface/hub/datasets--glue
google/fleurs               dataset          64.9M        6 refs/pr/1, main     /Users/lucain/.cache/huggingface/hub/datasets--google--fleurs
Jean-Baptiste/camembert-ner model           441.0M        7 main                /Users/lucain/.cache/huggingface/hub/models--Jean-Baptiste--camembert-ner
bert-base-cased             model             1.9G       13 main                /Users/lucain/.cache/huggingface/hub/models--bert-base-cased
t5-base                     model            10.1K        3 main                /Users/lucain/.cache/huggingface/hub/models--t5-base
t5-small                    model           970.7M       11 refs/pr/1, main     /Users/lucain/.cache/huggingface/hub/models--t5-small

Done in 0.0s. Scanned 6 repo(s) for a total of 3.4G.
Got 1 error(s) while scanning. Use -vvv to print details.

➜ huggingface-cli scan-cache -v
REPO ID                     REPO TYPE REVISION                                 SIZE ON DISK NB FILES REFS        LOCAL PATH
--------------------------- --------- ---------------------------------------- ------------ -------- ----------- ----------------------------------------------------------------------------------------------------------------------------
glue                        dataset   9338f7b671827df886678df2bdd7cc7b4f36dffd        97.7K       14 main, 2.4.0 /Users/lucain/.cache/huggingface/hub/datasets--glue/snapshots/9338f7b671827df886678df2bdd7cc7b4f36dffd
glue                        dataset   f021ae41c879fcabcf823648ec685e3fead91fe7        97.8K       14 1.17.0      /Users/lucain/.cache/huggingface/hub/datasets--glue/snapshots/f021ae41c879fcabcf823648ec685e3fead91fe7
google/fleurs               dataset   129b6e96cf1967cd5d2b9b6aec75ce6cce7c89e8        25.4K        3 refs/pr/1   /Users/lucain/.cache/huggingface/hub/datasets--google--fleurs/snapshots/129b6e96cf1967cd5d2b9b6aec75ce6cce7c89e8
google/fleurs               dataset   24f85a01eb955224ca3946e70050869c56446805        64.9M        4 main        /Users/lucain/.cache/huggingface/hub/datasets--google--fleurs/snapshots/24f85a01eb955224ca3946e70050869c56446805
Jean-Baptiste/camembert-ner model     dbec8489a1c44ecad9da8a9185115bccabd799fe       441.0M        7 main        /Users/lucain/.cache/huggingface/hub/models--Jean-Baptiste--camembert-ner/snapshots/dbec8489a1c44ecad9da8a9185115bccabd799fe
bert-base-cased             model     378aa1bda6387fd00e824948ebe3488630ad8565         1.5G        9             /Users/lucain/.cache/huggingface/hub/models--bert-base-cased/snapshots/378aa1bda6387fd00e824948ebe3488630ad8565
bert-base-cased             model     a8d257ba9925ef39f3036bfc338acf5283c512d9         1.4G        9 main        /Users/lucain/.cache/huggingface/hub/models--bert-base-cased/snapshots/a8d257ba9925ef39f3036bfc338acf5283c512d9
t5-base                     model     23aa4f41cb7c08d4b05c8f327b22bfa0eb8c7ad9        10.1K        3 main        /Users/lucain/.cache/huggingface/hub/models--t5-base/snapshots/23aa4f41cb7c08d4b05c8f327b22bfa0eb8c7ad9
t5-small                    model     98ffebbb27340ec1b1abd7c45da12c253ee1882a       726.2M        6 refs/pr/1   /Users/lucain/.cache/huggingface/hub/models--t5-small/snapshots/98ffebbb27340ec1b1abd7c45da12c253ee1882a
t5-small                    model     d0a119eedb3718e34c648e594394474cf95e0617       485.8M        6             /Users/lucain/.cache/huggingface/hub/models--t5-small/snapshots/d0a119eedb3718e34c648e594394474cf95e0617
t5-small                    model     d78aea13fa7ecd06c29e3e46195d6341255065d5       970.7M        9 main        /Users/lucain/.cache/huggingface/hub/models--t5-small/snapshots/d78aea13fa7ecd06c29e3e46195d6341255065d5

Done in 0.0s. Scanned 6 repo(s) for a total of 3.4G.
Got 1 error(s) while scanning. Use -vvv to print details.

➜ huggingface-cli scan-cache -vvv
REPO ID                     REPO TYPE REVISION                                 SIZE ON DISK NB FILES REFS        LOCAL PATH
--------------------------- --------- ---------------------------------------- ------------ -------- ----------- ----------------------------------------------------------------------------------------------------------------------------
glue                        dataset   9338f7b671827df886678df2bdd7cc7b4f36dffd        97.7K       14 main, 2.4.0 /Users/lucain/.cache/huggingface/hub/datasets--glue/snapshots/9338f7b671827df886678df2bdd7cc7b4f36dffd
glue                        dataset   f021ae41c879fcabcf823648ec685e3fead91fe7        97.8K       14 1.17.0      /Users/lucain/.cache/huggingface/hub/datasets--glue/snapshots/f021ae41c879fcabcf823648ec685e3fead91fe7
google/fleurs               dataset   129b6e96cf1967cd5d2b9b6aec75ce6cce7c89e8        25.4K        3 refs/pr/1   /Users/lucain/.cache/huggingface/hub/datasets--google--fleurs/snapshots/129b6e96cf1967cd5d2b9b6aec75ce6cce7c89e8
google/fleurs               dataset   24f85a01eb955224ca3946e70050869c56446805        64.9M        4 main        /Users/lucain/.cache/huggingface/hub/datasets--google--fleurs/snapshots/24f85a01eb955224ca3946e70050869c56446805
Jean-Baptiste/camembert-ner model     dbec8489a1c44ecad9da8a9185115bccabd799fe       441.0M        7 main        /Users/lucain/.cache/huggingface/hub/models--Jean-Baptiste--camembert-ner/snapshots/dbec8489a1c44ecad9da8a9185115bccabd799fe
bert-base-cased             model     378aa1bda6387fd00e824948ebe3488630ad8565         1.5G        9             /Users/lucain/.cache/huggingface/hub/models--bert-base-cased/snapshots/378aa1bda6387fd00e824948ebe3488630ad8565
bert-base-cased             model     a8d257ba9925ef39f3036bfc338acf5283c512d9         1.4G        9 main        /Users/lucain/.cache/huggingface/hub/models--bert-base-cased/snapshots/a8d257ba9925ef39f3036bfc338acf5283c512d9
t5-base                     model     23aa4f41cb7c08d4b05c8f327b22bfa0eb8c7ad9        10.1K        3 main        /Users/lucain/.cache/huggingface/hub/models--t5-base/snapshots/23aa4f41cb7c08d4b05c8f327b22bfa0eb8c7ad9
t5-small                    model     98ffebbb27340ec1b1abd7c45da12c253ee1882a       726.2M        6 refs/pr/1   /Users/lucain/.cache/huggingface/hub/models--t5-small/snapshots/98ffebbb27340ec1b1abd7c45da12c253ee1882a
t5-small                    model     d0a119eedb3718e34c648e594394474cf95e0617       485.8M        6             /Users/lucain/.cache/huggingface/hub/models--t5-small/snapshots/d0a119eedb3718e34c648e594394474cf95e0617
t5-small                    model     d78aea13fa7ecd06c29e3e46195d6341255065d5       970.7M        9 main        /Users/lucain/.cache/huggingface/hub/models--t5-small/snapshots/d78aea13fa7ecd06c29e3e46195d6341255065d5

Done in 0.0s. Scanned 6 repo(s) for a total of 3.4G.
Got 1 error(s) while scanning.
Snapshots dir doesn't exist in cached repo: /Users/lucain/.cache/huggingface/hub/models--tests--fixtures--working_repo_2--FROM_PRETRAINED/snapshots

Thanks @LysandreJik and @osanseviero for your review and feedback!
There are still two small comments left from Lysandre but apart from that I think we are good to merge.


Electron build (windows) not working

Steps to reproduce and a minimal demo of the problem
npm run build.desktop.windows or start.desktop.windows. The app seems to build, executable is in the folder, everything seems fine
What steps should we try in your demo to see the problem?
Launch the executable.
Current behavior
The app is stuck on "Loading..." and doesn't load at all.
Expected/desired behavior
Having angular components loading. Empty page for now.

Fails on mac also, here is the errors in the console
`zone.js?1462934431716:101 GET<EMAIL_ADDRESS>net::ERR_FILE_NOT_FOUND
index.html:98 Error: Error: XHR error loading file:///node_modules/@angular/core/package.json(…) "Report this error at https://github.com/NathanWalker/angular2-seed-advanced/issues"`

Hi @sebfag @nlmueng thanks for pointing this out.
Just pushed up the fix, please pull latest and all will be working for you now.


Add ALPM Metadata to CYCLONEDX and SPDX output formats

What would you like to be added:
ALPM package parsing/identification has been added to Syft as of #943.
The next step is getting the metadata for those packages output into both SPDX and CycloneDX. Currently, the package metadata is only available within the SYFT-JSON format.
Why is this needed:
Information parity across formats.
Additional context:
See #943 for details on how the metadata was constructed for SYFT-JSON

The specific struct in question is https://github.com/anchore/syft/pull/943/files#diff-11846c0455726b6119b5b2e0fb893a6a56af1ed0fd2549e97ab65b0322c05cbbR15

If anyone's interested in tackling this issue, you can start by looking at the structure here: https://github.com/anchore/syft/blob/main/syft/pkg/alpm_metadata.go#L17-L29
Notice that right now there is only one item with a CycloneDX tag in it: Size. Any properties that you expect to be exported to the CycloneDX output will need to have a CycloneDX tag added, like Size.

@wagoodman @tgerla I would like work on this item. One question, I understand how to add CycloneDX  tag to the ALPM Metadata, however how is this done with SPDX? Does it just pick up based on CycloneDX tag? Wondering this as I didn't seem to find a spdx tag like I did for cyclonedx

Would it be something like
Size         int              `mapstructure:"size" json:"size" cyclonedx:"size" spdx: "size"`

or
Size         int              `mapstructure:"size" json:"size" cyclonedx:"size" spdxjson:"size"`

?

@Shanedell the cyclonedx tags define which fields are output as CycloneDX properties. SPDX does not have arbitrary properties, hence does not have any tags. Each property in SPDX needs to map to a specific field in the SPDX spec, it's quite possible much of these do not.


Scan turbine model inspection report from machine shop

Secondary inspection files are in this repo, but the machine shop's report should be added to the CAD file repository.

See RM2-packing-list-inspection.pdf.


[avatar duotone appearance]: additional component appearance

After some research and discussion it was decided that tan additional appearance should be added to the avatar component.
The appearance is used in duotone.
Those are link to the design in Figma.
https://www.figma.com/file/JJNgZvt1qf3ydYmOwbE3Jg/Vivid-UI-Kit---3.0-WIP?node-id=19420%3A158935&t=aevYL5MkqeOU5zho-1

this should not be worked on as it introduces changes in appearance model.
it should be blocked by a ticket that should be opened to apply changes to appearance model.
@AyalaBu please reflect those changes in Figma and open a ticket to apply those changes in dev.
see VIV-844

@AyalaBu
https://vivid-wykt3m55gccg.deno.dev/components/avatar

@rachelbt
Looks great.
Does it mean that there will be no more outline avatar?

@rachelbt Looks great. Does it mean that there will be no more outline avatar?

I'm leaving this to you to make the investigation :)
I understood that it is not needed. but its not me to decide but the designers.

as was discusses - we are keeping the outline:
https://vonage.slack.com/archives/D03KLBB8K5Y/p1679211223715459


Automatic failed test reload

Feature added to reload all previously failing files.

Rather than run the failing tests as a separate test run, there should only be 1 test run on any given modification.  This single run will include all affected files and previously failing tests.
Also, the vigilant test runner was a bear to get working which is why it doesn't have tests.  Since it has gained some stability, it should be possible to add tests for this change.


Tyracraft website not working.

The website buttons don't work, and keep directing you to the main page. I looked in console using inspect element and theres plenty of errors. (errors listed below)

Error: Cannot match any routes.  I'll fix ASAP!

@mrfiguy can you check it after last update?

ill do so (;


[Question] Anything that could be done to avoid "IOException: Stream was too long"?

I started to get an FsPicklerException when trying to serialize a very large object tree, due to an internal IOException indicating that the Stream was too long. Do you know whether there is a chance to influence this, maybe to increase limits when running in a 64bit process? Or do I simply have to split the object tree into smaller pieces?
Thanks,
Christoph

It seems I could solve this by serializing directly to a FileStream, i.e. instead of serializer.Pickle to a byte array and then writing the bytes to a file, I now directly call serializer.Serialize and pass in the file stream.

Pickle and UnPickle are just extension methods that use MemoryStream serialization under the good. I think you can't use it for anything larger than a handful of gigs.


fix #5804: support object value for key attribute

#5804

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] Feature
[ ] Code style update
[ ] Refactor
[ ] Build-related changes
[ ] Other, please describe:

Does this PR introduce a breaking change? (check one)

[ ] Yes
[x] No

First, thanks for the PR and see https://github.com/vuejs/vue/issues/5804#issuecomment-305950427
Regarding the implementation - not sure if it's a good idea to pollute the observed objects like this. Ideally we should Object.defineProperty to make it non-enumerable. But this operation is quite expensive.
One way to work around this might be using native Map when it is available, and fallback to the "secret non-enumerable key" strategy used in this PR. However, I'd like to do some more performance benchmarking before actually adding the changes.

Adding a warning should be a better idea before native map object can be take into consideration.


You can keep pressing "FIND..." while the file menu is already open.

You can keep clicking "FIND" while the file menu is already open
You can still interact with the manager when the "An update is available" prompt is up


I am trying to run the command to process the guardian invitation and i get an error guardianinvite is not a valid argument for "gam create" - anyone have any insight on this?

The issue tracker is for reporting product deficiencies. "How do I?" questions should be posted to the discussion forum at https://groups.google.com/group/google-apps-manager. When in doubt, start at the discussion forum and return here only when instructed to do so.
Please confirm the following:

I have upgraded to the latest GAM release from https://git.io/gamreleases and I still have this issue.
I am typing the command as described in the GAM Wiki at https://github.com/jay0lee/gam/wiki

Full steps to reproduce the issue:
1.
2.
3.
Expected outcome (what are you trying to do?):
Actual outcome (what errors or bad behavior do you see instead?):

Dorothy,
What does this return: gam version
Ross
On Mon, Jul 2, 2018 at 2:34 PM dorothygrissom<EMAIL_ADDRESS>wrote:

[image: image]
https://user-images.githubusercontent.com/40776331/42187463-c2bc761e-7e15-11e8-80ae-2e09121ee835.png
The issue tracker is for reporting product deficiencies. "How do I?"
questions should be posted to the discussion forum at
https://groups.google.com/group/google-apps-manager. When in doubt, start
at the discussion forum and return here only when instructed to do so.
Please confirm the following:

I have upgraded to the latest GAM release from
https://git.io/gamreleases and I still have this issue.
I am typing the command as described in the GAM Wiki at
https://github.com/jay0lee/gam/wiki

Full steps to reproduce the issue:
1.
2.
3.
Expected outcome (what are you trying to do?):
Actual outcome (what errors or bad behavior do you see instead?):
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/jay0lee/GAM/issues/743, or mute the thread
https://github.com/notifications/unsubscribe-auth/AIU8L5jQHUgY6t468f3oHbbC_QhIoN3Bks5uCpHkgaJpZM4U_-Vs
.

--
Ross Scroggs
<EMAIL_ADDRESS>


Mixed content error on Cloud Run when generating Google-signed OAuth ID token

Hi, I'm following the Securing Cloud Run services tutorial, using my own react app deployed to cloud run as the client and chrome is blocking the request to generate an auth token because its expecting the request to be made with HTTPS instead of HTTP. Thanks

I noticed the client in the example repo is using a server rendered node.js express app. I'm guessing this library may not work on client side javascript frameworks like React?
Another part of the cloud run documentation uses a different approach by making a request to a metadataServerTokenURL, I tried this as well but got the same result as its also a HTTP url - here is my code snippet
const handleItemSubmit = () => {
    const receivingServiceURL = process.env.REACT_APP_BACKEND_URL;
    const metadataServerTokenURL = `http://metadata/computeMetadata/v1/instance/service-accounts/default/identity?audience=${receivingServiceURL}`;

    try {
      fetch(metadataServerTokenURL)
        .then(res => res.text())
        .then(token => {
          fetch(receivingServiceURL, {
            method: 'POST',
            headers: {
              'Content-Type': 'application/json',
              Authorization: `Bearer ${token}`
            },
            body: {
              title: item
            },
        }).then(res => res.json())
          .then(json => console.log(json));
        });
    } catch (error) {
      throw Error('Request failed: ', error);
    }
  }

I managed to around this by creating another cloud run service to handle authentication between the React app and the backend API. It would be nice to be able to authenticate directly from the browser though without the added latency

@hom-bahrani it should be possible to make things work in a react-app, using webpack or rollup (see: thread here).
This is something we'd like to make easier in the future.

Thanks @bcoe thats looks useful


Create stub for isogram exercise

This stub is based on the hello world test, so let me know what I need to tweak in the template in order to make it idiomatic.
One thing we haven't yet talked about is the student experience around test failures.
In some language tracks we've tried to use the mechanisms available in the language and tooling to try to simulate Test-Driven Development, either by

using a skipping mechanism so that all but the first test is skipped, and then having the student remove or uncomment the skipping mechanism one test at a time
running tests in the order that they are defined in the file and "failing fast" so that the tests after the first failure are not executed/reported.

Right now if I implement the stub solution to hardcode a return value of true I get the following failure:

Isogram test failure
Compiled 'tests.chpl' successfully
Ran test_empty_string() OK
Ran test_isogram_with_only_lower_case_characters() OK
Ran test_word_with_one_duplicated_character() FAIL
Ran test_word_with_one_duplicated_character_from_the_end_of_the_alphabet() FAIL
Ran test_longest_reported_english_isogram() OK
Ran test_word_with_duplicated_character_in_mixed_case() FAIL
Ran test_word_with_duplicated_character_in_mixed_case_lowercase_first() FAIL
Ran test_hypothetical_isogrammic_word_with_hyphen() OK
Ran test_hypothetical_word_with_duplicated_character_following_hyphen() FAIL
Ran test_isogram_with_duplicated_hyphen() OK
Ran test_made_up_name_that_is_an_isogram() OK
Ran test_duplicated_character_in_the_middle() FAIL
Ran test_same_first_and_last_characters() FAIL
Ran test_word_with_duplicated_character_and_with_two_hyphens() FAIL

======================================================================
FAIL tests.chpl: test_word_with_one_duplicated_character()
----------------------------------------------------------------------
AssertionError: assert failed - 'true' != 'false'

======================================================================
FAIL tests.chpl: test_word_with_one_duplicated_character_from_the_end_of_the_alphabet()
----------------------------------------------------------------------
AssertionError: assert failed - 'true' != 'false'

======================================================================
FAIL tests.chpl: test_word_with_duplicated_character_in_mixed_case()
----------------------------------------------------------------------
AssertionError: assert failed - 'true' != 'false'

======================================================================
FAIL tests.chpl: test_word_with_duplicated_character_in_mixed_case_lowercase_first()
----------------------------------------------------------------------
AssertionError: assert failed - 'true' != 'false'

======================================================================
FAIL tests.chpl: test_hypothetical_word_with_duplicated_character_following_hyphen()
----------------------------------------------------------------------
AssertionError: assert failed - 'true' != 'false'

======================================================================
FAIL tests.chpl: test_duplicated_character_in_the_middle()
----------------------------------------------------------------------
AssertionError: assert failed - 'true' != 'false'

======================================================================
FAIL tests.chpl: test_same_first_and_last_characters()
----------------------------------------------------------------------
AssertionError: assert failed - 'true' != 'false'

======================================================================
FAIL tests.chpl: test_word_with_duplicated_character_and_with_two_hyphens()
----------------------------------------------------------------------
AssertionError: assert failed - 'true' != 'false'

----------------------------------------------------------------------
Ran 14 tests in 7.71508 seconds

FAILED (passed = 6 failures = 8 )

This isn't the end of the world, but in terms of pedagogy it's nice when the next step is clearly indicated by having a failure that is adjacent to the current implementation, if that makes sense.

This isn't the end of the world, but in terms of pedagogy it's nice when the next step is clearly indicated by having a failure that is adjacent to the current implementation, if that makes sense.

I'm not sure I understand what you mean. In general, I agree error messages could be better in Chapel. The good news, is that we are not bound to use UnitTest if we want more control on the printed output, it's not too difficult to setup one's own test framework in Chapel. Can you give a MWE of the output you'd expect to see?

Ah, I didn't mean that the error messages are bad, only that because we've pre-written the entire test suite we get 30 errors all at once instead of getting one error at a time.
When people are doing TDD on their own, they generally just write "the next test", and therefore are able to focus in on just one little thing at a time, but when there are a bunch of errors up front it's hard to know what to focus on next in terms of solving the exercise.

sorry I didn't read carefully your message 😅

using a skipping mechanism so that all but the first test is skipped, and then having the student remove or uncomment the skipping mechanism one test at a time

I think this could be implemented using Chapel skipIf and dependsOn. I can try drafting a quick prototype.
How would this work if students work from the web editor though? I think in that case they couldn't edit the tests themselves.

running tests in the order that they are defined in the file and "failing fast" so that the tests after the first failure are not executed/reported.

yes this should be possible too by setting chapel to halt on error, I'll quickly check with a small demo.
I guess pedagogically this gives the student a more guided workflow, forcing them to focus on one small step at the time, which can be good. A possible downside of fast failures is that if e.g. while working on test 5 I accidentally break test 1, then I don't see if it affects also tests 2,3,4, wouldn't this slow down debugging?

How would this work if students work from the web editor though? I think in that case they couldn't edit the tests themselves.

That is a fantastic question. I think for the webeditor we remove the skips ahead of time, maybe. @ErikSchierboom do you happen to know off the top of your head what the usual approach is to this?

I guess pedagogically this gives the student a more guided workflow, forcing them to focus on one small step at the time, which can be good.

Yeah, exactly. That's the main idea.

A possible downside of fast failures is that if e.g. while working on test 5 I accidentally break test 1, then I don't see if it affects also tests 2,3,4, wouldn't this slow down debugging?

Yeah, fail-fast will slow down debugging. Skipping/unskipping will not, because all the previously "solved" tests will still fail if you make a change that breaks earlier tests, which I think is a better experience.

I think this could be implemented using Chapel skipIf and dependsOn. I can try drafting a quick prototype.

That would be great.
(I should have started this discussion in an issue rather than a random PR /facepalm -- I'll open an issue about it now)

This looks great. I can't hit the approve button since I opened the PR, but I totally do approve :)


Routing traffic from LAN to Tailscale not working

Problem/Motivation

Tailscale addon not routing traffic from LAN to Tailscale

Expected behavior

Since my tailscale on HASS is acting as a subnetrouter, it's routing traffic from Tailscale to my LAN, the other way around should also be possible.

Actual behavior

traceroute <IP_ADDRESS>
traceroute to <IP_ADDRESS> (<IP_ADDRESS>), 64 hops max, 40 byte packets
1  <IP_ADDRESS> (<IP_ADDRESS>)  5.353 ms  2.572 ms  2.309 ms
2  <IP_ADDRESS> (<IP_ADDRESS>)  4.191 ms  2.893 ms  3.061 ms
3  * * *

Steps to reproduce
I configured my hass-tailscale-addon as follows:
advertise_exit_node: true
accept_routes: true
accept_dns: true
userspace_networking: false
snat_subnet_routes: false
advertise_routes:
  - <IP_ADDRESS>/24

I created a static route on my firewall for destination: <IP_ADDRESS>/10 to <IP_ADDRESS> (my HASS IP)
When I ping <IP_ADDRESS> (IP from another client in my Tailscale) from HASS I get a instant connection. When I ping / traceroute that same IP from any other device without Tailscale installed it hangs at <IP_ADDRESS>. (see above for the traceroute)
Proposed changes

N/A

This should work, tested several times.
Do you really need snat_subnet_routes: false This requires much more config everywhere. To access other TS devices, or other subnet devices behind other TS devices, from your LAN, you don't need this. With snat_subnet_routes: true it just works.
If you really want full blown site-to-site networking (ie. using snat_subnet_routes: false), please follow steps from step 3 on [Site-to-site networking][tailscale_info_site_to_site]? - Yeah DOCS.md says steps 2-3, TS changed the docs, DOCS.md will be updated.

I changed snat_subnet_routes to true. Sadly this doesn't make a change:
PING <IP_ADDRESS> (<IP_ADDRESS>): 56 data bytes
Request timeout for icmp_seq 0
92 bytes from <IP_ADDRESS>: Redirect Host(New addr: <IP_ADDRESS>)
Vr HL TOS  Len   ID Flg  off TTL Pro  cks      Src      Dst
 4  5  00 0054 da1e   0 0000  3f  01 4795 <IP_ADDRESS>  <IP_ADDRESS>```

```traceroute <IP_ADDRESS>
traceroute to <IP_ADDRESS> (<IP_ADDRESS>), 64 hops max, 40 byte packets
 1  <IP_ADDRESS> (<IP_ADDRESS>)  6.683 ms  2.521 ms  2.538 ms
 2  <IP_ADDRESS> (<IP_ADDRESS>)  2.686 ms  3.289 ms  2.992 ms
 3  * * *```

OK, questions:

what is your installation type?
did you enable subnet routing on the admin site for the source lan also?

Because it seems that either the OS is missing some feature (forwarding) or the routing is not configured beetween <IP_ADDRESS> and tailscale0. Test it first:

with snat_...: true, and
without your firewall/router, ie. modify the local route table on the source lan device that it sends packages for 100.x.x.x directly to <IP_ADDRESS>. This way you must be able to access from your source lan any tailscale device.
then add the other/destination subnet to the routing on your local/source lan device that it send packages for the other lan (not 192.168.178.x) to <IP_ADDRESS>. This way you must be able to access any other subnet.

This must work. If it doesn't work, it is a config error or a TS bug/breaking change. When it works, you can experiment with snat_...: false and firewalls/routers, this is plain old network config from here.

Thanks @lmagyar

what is your installation type?

HASS OS running in VM with TrueNAS SCALE as hypervisor

did you enable subnet routing on the admin site for the source lan also?

Yes

After a lot of troubleshooting and trial & error I tried spinning up a Ubuntu VM and installed TS with the same properties as I had in my TS addon on HASS. Edited the static route so it pointed to that Ubuntu VM, still same results as described above.
I ended up adding a NAT rule to the iptables configuration in the Ubuntu VM for traffic to  from <IP_ADDRESS>/24 to interface tailscale0.
I guess the last part was not configured / is not configurable in HASS OS.

So you edited the static routes on the non-TS lan devices. What was snat_... (true or false) when you had to add the additional rule for tailscale0? Ie. this extra rule is needed for both snat_...: false and true, or only for false?

So you edited the static routes on the non-TS lan devices. What was snat_... (true or false) when you had to add the additional rule for tailscale0? Ie. this extra rule is needed for both snat_...: false and true, or only for false?

No. I made an NAT-rule on the tailscale enabled device (the Ubuntu VM). Static route is still created to that Ubuntu VM is still at my router/Unifi gateway.
I didn't provide any snat_ flag, and default is true.

Strange. I will repeat my tests (site-to-site with snat=true) in the next weeks, I need some time, my physical test env. is currently used for other stuff. :/

Hi,
I've been having the same issue here.
According to tailscale's subnet router quick guide, were's supposed to execute the following commands:
echo 'net.ipv4.ip_forward = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf echo 'net.ipv6.conf.all.forwarding = 1' | sudo tee -a /etc/sysctl.d/99-tailscale.conf sudo sysctl -p /etc/sysctl.d/99-tailscale.conf
However, it doesn't seem to work on HASS OS. I get the following error:
[core-ssh ~]$ sysctl -p /etc/sysctl.d/99-tailscale.conf sysctl: error setting key 'net.ipv4.ip_forward': Read-only file system sysctl: error setting key 'net.ipv6.conf.all.forwarding': Read-only file system

Please read the docs, it says "follow steps from step 3", because what you want to configure, is already set.

Routing traffic back into Tailscale still doesnt work with the Tailscall Hass container


user with username containing capital letter cannot login

It's possible to create a user with the username containing capital letter. It's not possible to use that username to login to MIQ.
Steps to reproduce:

Login to MIQ as admin
Go to: Administrator -> Configuration -> Access Control -> Users
Select Configuration -> Add a new user
Enter a "Username" with upper case letter, e.g "newUser"
Fill in all other required fields
Click the Add button
=> New user is successfully created, no error message is displayed
Log out
Try to login as "newUser"
=> "Incorrect username or password" message is displayed

It seems that username is converted to lowercase when logging in. It's possible to enter e.g. ADMIN and login without issue.
This behavior is different to e.g. CFME 5.8 where username is case sensitive (user cannot login using e.g. ADMIN) and user can login using username with capital letter.

Looks to be the same as https://bugzilla.redhat.com/show_bug.cgi?id=1486041

@mkoura and @gmcculloug Yes this is the same as the BZ. I already have a fix posted in PR 15904 [1]  for this that is waiting for review.
Should we close this issue and track in the BZ?
[1] https://github.com/ManageIQ/manageiq/pull/15904

@jvlcek I'm ok with closing this issue and tracking the BZ.

@mkoura I do not have the necessary privilege to close it. As the initiator you should be able to. Can you?


Triggering CMake test

Closed tests with CMake bulding tool. Will focus on other simple ways for now.


About Section Spacing

ISSUE - Text in About section is packed close together making it difficult to read.
ACTION - add a line break after each paragraph to make the text more readable.

Spacing adjusted as per ACTION.


Fix/retired version

Fix retired version
Remove required static locations
Update default center to new Mendix office
Improve error messages address lookup

Codecov Report

Merging #33 into master will increase coverage by 0.93%.
The diff coverage is 60%.

@@            Coverage Diff             @@
##           master      #33      +/-   ##
==========================================
+ Coverage    82.5%   83.43%   +0.93%
==========================================
  Files           3        3
  Lines         160      169       +9
  Branches       42       44       +2
==========================================
+ Hits          132      141       +9
  Misses         28       28

Impacted Files
Coverage Δ

src/components/Map.ts
81.69% <60%> (+1.14%)
:arrow_up:

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 b485fb2...7ba48c2. Read the comment docs.


converting strings to timestamps

Hi,
I have a dask dataframe with a 'time' column that in string format. I'm trying to convert it to a pandas Timestamp type as follows:
from pandas.tseries.tools import to_datetime
my_ddf['time'].map_partitions(to_datetime, columns='time').compute()

This conversion takes forever to run (>1min) . Running to_datetime on a pandas dataframe version of the data finishes in about 10 secs. Any suggestions about what's going on and how I can speed it up?

You seem to be doing the correct thing as far as I can see.  Perhaps try out the Profiler to see what is taking up the most time?
http://dask.pydata.org/en/latest/diagnostics.html#profiler

It could be that to_datetime doesn't release the GIL (most things coming from strings don't) and the threads are thrashing performance a bit.  What happens when you use a single thread
my_ddf['time'].map_partitions(to_datetime, columns='time').compute(get=dask.async.get_sync)

The profiler results for the multithreaded version:

The single threaded version is somewhat faster, but still nowhere as fast as doing this on a pandas dataframe:
dask: 3min 26.1s
pandas: 623us.
Any ideas of where the overhead is ?

And, to be clear, if you hover over one of those green bars it says that the function is to_datetime, yes?

If so the next thing I would try is to use the single-threaded scheduler and use a standard Python profiler like the profile module or the %prun magic within IPython
%prun my_ddf['time'].map_partitions(to_datetime, columns='time').compute(get=dask.async.get_sync)

The breakdown from the profiler is as expected:
      158853141 function calls (158852161 primitive calls) in 299.647 seconds

   Ordered by: internal time

   ncalls  tottime  percall  cumtime  percall filename:lineno(function)
        5   42.039    8.408  299.277   59.855 {built-in method array_to_datetime}
  3945396   36.804    0.000   80.065    0.000 _strptime.py:298(_strptime)
  7890792   36.148    0.000   47.709    0.000 parser.py:50(get_token)
   986349   35.967    0.000  138.039    0.000 parser.py:445(_parse)
   986349   12.022    0.000  166.749    0.000 parser.py:343(parse)
   986349   10.858    0.000   72.076    0.000 parser.py:173(split)
 21699788    7.994    0.000    7.994    0.000 {method 'read' of '_io.StringIO' objects}

And presumably something like this is fast?
my_ddf['time'].compute(get=dask.async.get_sync).to_datetime()

Yes - I think that's probably what I'll have to do.
%time to_datetime(dask_df['time'].compute(), format="%Y%m%d %H:%M:%S.%f" )

%time to_datetime(pandas_df.time, format="%Y%m%d %H:%M:%S.%f")

CPU times: user 8.66 s, sys: 128 ms, total: 8.79 s
Wall time: 8.72 s
CPU times: user 8.34 s, sys: 4 ms, total: 8.35 s
Wall time: 8.31 s

Can you give me a reproducible example that I can play with locally?  I'd like to get to the bottom of this.

Can I share an hdf5 file with you ?

from pylab import *
import numpy as np
import matplotlib as npl
from random import sample
from imp import reload

import pandas as pd
from pandas import *
import dask.dataframe as ddf

n = 9e6
lts = date_range( '20150101', periods=n, freq='1D')

mydf = DataFrame(
    dict(
        date=lts.strftime('%Y-%m-%d'),
        ts=lts.astype(int64),
    )#,
    #index=lts
)
mydf['row_num'] = range(len(mydf))

my_ddf = ddf.from_pandas(mydf, npartitions =  10)

my_ddf['date'].map_partitions(to_datetime, columns='date').compute(get=dask.async.get_sync)

I'm not seeing the same performance degredation.  I'd be happy to receive a file that fits within an e-mail at mrocklin with the domain name continuum.io.  Also happy to connect to some other convenient data source somewhere.
In [1]: import dask

In [2]: import numpy as np

In [3]: import pandas as pd

In [4]: n = 9e6

In [5]: lts = pd.date_range( '20150101', periods=n, freq='1D')

In [6]: mydf = pd.DataFrame(
    dict(
        date=lts.strftime('%Y-%m-%d'),
        ts=lts.astype(np.int64),
    ),
)

In [7]: mydf['row_num'] = range(len(mydf))

In [8]: import dask.dataframe as dd

In [9]: my_ddf = dd.from_pandas(mydf, npartitions =  10)

In [10]: %time _ = pd.to_datetime(mydf.date)CPU times: user 11 ms, sys: 3.71 ms, total: 14.7 ms
Wall time: 14.5 ms

In [11]: %time _ = my_ddf.date.map_partitions(pd.to_datetime, columns='date').compute(get=dask.async.get_sync)
CPU times: user 54.4 ms, sys: 678 µs, total: 55.1 ms
Wall time: 53.9 ms

In [12]: %time _ = my_ddf.date.map_partitions(pd.to_datetime, columns='date').compute(get=dask.async.get_sync)
CPU times: user 20.4 ms, sys: 32 µs, total: 20.4 ms
Wall time: 19.9 ms

Is it possible that I was experiencing these delays because the dataframe I was using was backed by a csv file and memoized using joblib's memory package ?

@mrocklin
Regarding my original fix for this problem, I'm running into a new issue. Specifically, this was my approach of converting time-strings in fix_ddf into pandas Timestamp objects by adding a new column :
# fix_ddf is the dataframe with string time stamps
print (fix_ddf.divisions, fix_ddf.npartitions, len(fix_ddf.divisions) )
time_col = to_datetime(fix_ddf['time'].compute(), format="%Y%m%d %H:%M:%S.%f" )
new_ddf = fix_ddf.assign(__datetime__=time_col, __timestamp__=time_col.astype(int64) )
print (new_ddf.divisions, new_ddf.npartitions, len(new_ddf.divisions) )

This the output of the print statements:
(0, 222299, 460136, 694275, 926828, 1159470, 1401018, 1645870, 1896652, 1924537) 9 10
(0, 222299, 460136, 694275, 926828, 1159470, 1401018, 1645870, 1896652, 1924536, 1924537) 10 11

For some reason, the number of partitions has increased by 1. Also, I can no longer index into the last partition ie. any index > 1924535 throws an IndexError.
Any ideas of what's going on ?

Is it possible that I was experiencing these delays because the dataframe I was using was backed by a csv file and memoized using joblib's memory package ?

Perhaps you were including the cost to read the CSV file in your measurement of the dask.dataframe time while, with Pandas, the dataframe was already in memory?

With the divisions problem it will be much easier to diagnose the issue you're seeing if you're able to produce an example that I can reproduce locally.
It's odd to call compute and then assign the pandas dataframe into a dask.dataframe.  It works, it just feels somewhat inefficient.
A simple toy example shows no problem here.
In [1]: import pandas as pd

In [2]: import dask.dataframe as dd

In [3]: df = pd.DataFrame({'x': [1, 2, 3, 4]})

In [4]: ddf = dd.from_pandas(df, npartitions=2)

In [5]: ddf2 = ddf.assign(y = pd.Series([10, 20, 30, 40]))

In [6]: ddf2
Out[6]: dd.DataFrame<elemwise-2a1ff96d6fc0f5d54ff67a316d1b81c0, divisions=(0, 2, 3)>

In [7]: ddf2.compute()
Out[7]:
   x   y
0  1  10
1  2  20
2  3  30
3  4  40

Again, a reproducable example would be highly valuable.

I also don't have any problems when convering pandas dataframes to dask frames.
The problems start to show up when using creating a dask graph for datasets > 30mn rows, with more than 10 partitions.
It's all ok for smaller sizes.
If you recollect from another thread, I was trying read in a streaming data-source via subprocess pipes, but the problem also occurs when I try to read in a sufficiently large CSV file (>20GB). I have a feeling that I'm not creating the graph correctly and if you have any leads - that would be appreciated. In the meanwhile, I'll try to set up a way to transfer my dataset.
import pandas as pd
from joblib import Parallel, delayed, Memory

__memorycache__ = Memory( cachedir='/dev/shm/dask/', verbose=0 )

# dcr.get_pipe() returns an open subprocess pipe object over a particular date range. You can point it to a csv file.
@__memorycache__.cache
def cache_read_csv(pipe, start, end, div):
    if dcr.__verbose__: print('reading from ', start, ' to ', end)
    df = pd.read_csv( dcr.get_pipe(start, end), parse_dates='time' )
    return df;

def __fix__( df , seix):
    '''
    :param dv Take as input a dask action tuple that encapsulates a dataframe.
    :param seix: Tuple of start and end indices
    Use dask imperative to execute that tuple.
    Thunk it's indices based on start and end indices
    '''
    df.index = range( seix[0], seix[1] )
    return df;

raw_dsk = {  ('ddf', i): (cache_read_csv, dcr, start, end, i) for i, (start, end) in enumerate(date_range)   }

ddf_divisions = [0] + [None]*len(date_range)
cols = __diskcache_read_csv__(dcr, date_range[0][0], date_range[0][1], 0 ).columns
raw_ddf = ddf.DataFrame( raw_dsk, 'ddf', cols, ddf_divisions )

# fix the divisions values
partition_len = raw_ddf.map_partitions(len).compute() # has to scan through the data once...
ddf_divisions[1:] = cumsum( partition_len )
raw_ddf.divisions = tuple(ddf_divisions)

# construct a dict of division number and start and end indices
seix_map = dict( zip(range(raw_ddf.npartitions) , zip(ddf_divisions[0:-1], ddf_divisions[1:]) ) )

# 'fix the indices of the dataframe
fix_dsk = dict()
for dk in raw_dsk.keys():
            cdiv = dk[1]; # current division
            fix_dsk[('fix_ddf',cdiv)] = (__fix__, raw_dsk[dk], seix_map[cdiv] )
fix_ddf = ddf.DataFrame(fix_dsk, 'fix_ddf', cols, ddf_divisions);

# convert the string to datetime type. doing something like fix_df['time'].map_partitions(to_datetime) takes over 10 mins for 30mn rows
time_col = to_datetime(fix_ddf['time'].compute(), format="%Y%m%d %H:%M:%S.%f" )

#this assign adds one more division to the output frame and breaks  the dataframe.
return fix_ddf.assign(__datetime__=time_col, __timestamp__=time_col.astype(int64) );

I think I figured out the problem ...
Wrong way to fix the division sizes:
partition_len = raw_ddf.map_partitions(len).compute()
ddf_divisions[1:] = cumsum( partition_len )
raw_ddf.divisions = tuple(ddf_divisions)

Right way to fix the division sizes:
partition_len = raw_ddf.map_partitions(len).compute()
ddf_divisions[1:] = cumsum( partition_len )
ddf_divisions[-1] -= 1 #  the last division is an inclusive index.
raw_ddf.divisions = tuple(ddf_divisions)

Ah ha, nice find!

Yes, that can easily be a gotcha, it's a bit unintuitive

I see your codes, and none of those work for me:
ValueError: Metadata inference failed in `to_datetime`.

You have supplied a custom function and Dask is unable to
determine the type of output that that function returns.

To resolve this please provide a meta= keyword.
The docstring of the Dask function you ran should have more information.

Original error is below:
------------------------
ValueError('to assemble mappings requires at least that [year, month, day] be specified: [day,month,year] is missing')

How are those working without providing a meta= keyword?

This is a very old issue. I recommend opening a new issue with a minimal reproducible example.


epoch keys_gen error: undefined function crypto:hash/2

Behaviour
I follow the Tutorial: Mining AE on Ubuntu 18.04, after finish the installation of all dependencies, I run ./epoch keys_gen PASSWORD, but it reports escript: exception error: undefined function crypto:hash/2.
Specifications
docker image: ubuntu:18.04

I see you said docker image ubuntu 18.04
Are you following the standard installation on an ubuntu docker image?
Wouldn't it be easier to use the official docker image instead?

As @kryztoval suggested it would be easier to run our docker image indeed (it's alpine linux however).
However, if you prefer to follow the tutorial and run the node on ubuntu 18.04, I think you need to install older libssl version: sudo apt-get install libssl1.0.0
Not sure why we're missing that in the tutorial, I'll make sure it's updated.

I think the problem is outdated, because we are on a higher release now.
But it would be great if someone of you update the obsolete tutorial above.

@Zwilla We've updated the guide. Thanks for noticing.


Spec Export shortcut not working

Utilizing Spec export as a shortcut seems to have stopped working (use through the toolbar seems to be fine). I've tried reinstalling and updating both Sketch and the plugin. The other functions seem to be working fine, but not spec Export

May be related to issues reported in #279?...

Now working


Update fog to 1.36.0 for DigitalOcean v2 API support

Backport Gemfile updates from develop for #98

This needs the rubocop changes in #97 to pass CI

:+1: lgtm, pending rebase and green travis


On https://prod-preview.openshift.io - selecting cancel after the new space wizard fails raises a new error

See attached screenshot - to recreate the error, create a new user space, select the wizard option, and then press cancel.

Screencast:
https://drive.google.com/open?id=0B1s-ZoxD8FjUV3RTdTNGRURwelE


Develop

Coverage decreased (-0.008%) to 83.289% when pulling d0ce9b090f457f0e79bbacee8d0781ab9f0f99d0 on develop into a97970d02f2f29e4a5bd60c6d9b6ebd70c850fec on qa.


Add variable to track number of background jobs

Pretty much what it says in the subject, added in a variable to track the number of background jobs.  The most obvious use for something like this is to create a prompt notification about background jobs but it could potentially have other uses as well, such as warning the user if they try to exit the shell with jobs still running in the background.

Ideally this should have some tests, but right now it's kind of hard to test.


Dilato: Core: Linux only: Can't drop & drag a file to the bottom of the file tree if the file tree is large

Steps:

Launch Brackets
Open a folder which has lot of subfolder, it wil cause the directory is too long
Drag a file and hover it down to try to scroll the filetree.

Result: Can't drop & drag a file to the bottom of the file tree if the file tree is large
Expect: The filetree could scroll down

System: Debian 9.1.0, Ununtu 17.10.1-64bit, Ununtu 16.04.3-32bit
Build: 1.13.17668

@Zhanxin This issue happens only when we are not in maximized window. Can you confirm this?

@boopeshmahendran ,
Verified this issue in latest build 1.13.117668
For Debain 64 bit/Ubuntu 64 bit, this issue is also reproduced when we are in maximized window.
For Ubuntu 32 bit, this issue is reproed only when we are not in maximized window.
Please have a review. Thanks!

@boopeshmahendran Can you take a look at the issue for maximised scenario on ubuntu 64bit. Without this the feature will be almost unusable.

@vickramdhawal We were investigating this issue and found that this issue happens even in CefRefApp (2785 – which is the version used by brackets on linux) on Ubuntu 16.04. So we think that this is an cef issue.


No source generation when annotated interface is explicitly internal

Hi Stef,
i wanted to start a similar project today but aborted it since i found this and it perfectly fits the use case i had. It is really awesome, keep it up!
I found a small issue when trying it out:
The source generation only runs when the annotated interface is "public partial" or just "partial", but not when it is "internal partial". In any case it generates a public part for the interface which exposes the proxied class through a property, which means that it can also not generate proxies for internal classes. Then it tries to expose the internal class via the generated public property in the generated public interface which gives a compile error.
For the typical use case this should not be an issue, as proxies are mostly needed for classes from third party libraries, which are public anyway. And since we usually need the interface for mocking in unit tests, it also generally has to be public. Still i though i might let you know about it.
I do much appreciate this library and am thinking about suggesting to use it at work soon. I think stuff like this deserves some more attention, thank you very much for this!

Hello @madp4ul,
If you have time, you can create a PR to support internal.
And if you have more ideas, just create an issue.


Make it easier for CiviForm admin to find newly-created program

When a CiviForm admin creates a new program, their new program goes way to the bottom of the list of programs (or sometimes ends up randomly in the middle of the list). It's quite likely that the admin's next goal is to edit the new program, so having to hunt and find it would be tedious.
Potential improvements:

Offer a way to sort programs (#941) -- and, by default, sort with the newest or most recently edited programs on top.
Show a success message once the new program has been created. And in that success message, placed at the top of the page, add a quick link to edit the newly-created program.

Ideally we'd do both. Focus on the latter here, since the former has its own issue already.

Duplicate with https://github.com/seattle-uat/civiform/issues/1238 so am closing.


python 2 print statement on test files cause exception

the following error occurs at the installation process:
Extracting djangotoolbox-1.6.2-py3.4.egg to /home/vyscond/tartarus/infosae-rest/.venv/lib/python3.4/site-packages
  File "/home/vyscond/tartarus/infosae-rest/.venv/lib/python3.4/site-packages/djangotoolbox-1.6.2-py3.4.egg/djangotoolbox/test.py", line 45
    print "DB state not valid:"
                              ^
SyntaxError: Missing parentheses in call to 'print'

I thinks it's good replace this with a compatible between 2 and 3 python versions? or this project is intent to be only available to version 2?

Fixed in 71c355469de97b1e0d7b97889dc569ec0ef987b3


Obsoletion notice: replicative cell aging and children

Dear all,
The proposal has been made to obsolete GO:0001302 replicative cell aging. The reason for obsoletion is that this represent an assay (how long the cell lives), not a true BP.
There are 80 annotations to these terms:

Group
Number of annotations

CACAO
2

CGD
4

MGI
3

RGD
2

SGD
67

UniProt
2 (fixed)

Annotation review ticket is here: https://github.com/geneontology/go-annotation/issues/3256
There are no mappings; this term is not present in any subsets.
We are opening a comment period for this proposed obsoletion. We’d like to proceed and obsolete this term on September 28th, 2020. Unless objections are received by September 28th, 2020. we will assume that you agree to this change.
Comments may be added to the ticket : https://github.com/geneontology/go-ontology/issues/20007
Thanks, Pascale

Terms to be obsoleted:

GO:0001302 replicative cell aging
GO:0001308 negative regulation of chromatin silencing involved in replicative cell aging
GO:1900062 regulation of replicative cell aging
GO:0001319 inheritance of oxidatively modified proteins involved in replicative cell aging
GO:1900008 negative regulation of extrachromosomal rDNA circle accumulation involved in replicative cell aging

The rest have no annotations:

GO:0001308 	negative regulation of chromatin silencing involved in replicative cell aging
GO:0001307 	extrachromosomal circular DNA accumulation involved in replicative cell aging
GO:0001304 	progressive alteration of chromatin involved in replicative cell aging
GO:0001302 	replicative cell aging
GO:0001310 	extrachromosomal rDNA circle accumulation involved in replicative cell aging
GO:0001319 	inheritance of oxidatively modified proteins involved in replicative cell aging
GO:0001318 	formation of oxidatively modified proteins involved in replicative cell aging
GO:0001317 	accumulation of oxidatively modified proteins involved in replicative cell aging
GO:0001316 	age-dependent response to reactive oxygen species involved in replicative cell aging
GO:0001314 	replication of extrachromosomal circular DNA involved in replicative cell aging
GO:0001313 	formation of extrachromosomal circular DNA involved in replicative cell aging
GO:0001312 	replication of extrachromosomal rDNA circles involved in replicative cell aging
GO:0001311 	formation of extrachromosomal circular rDNA by homologous recombination involved in replicative cell aging
GO:0001321 	age-dependent general metabolic decline involved in replicative cell aging
GO:0001322 	age-dependent response to oxidative stress involved in replicative cell aging
GO:1900007 	regulation of extrachromosomal rDNA circle accumulation involved in replicative cell aging
GO:1900009 	positive regulation of extrachromosomal rDNA circle accumulation involved in replicative cell aging
GO:1900062 	regulation of replicative cell aging

Thanks, Pascale

-[]  GO:0001302 replicative cell aging -> add: consider: replicative senescence


fix(build): import Application and not App from @feathersjs/feathers

First of all thanks for the package @bitflower !
When building my application, I encountered the following error: "Build": node_modules/feathers-agenda/dist/index.d.ts(6,31): error TS2305: Module '"
This is because @feathersjs/feathers exports Application, not App.
Note this only happens after the build (when generating feathers-agenda/dist/index.d.t), locally it works just fine.
It is a small fix indeed, I hope you can release this soon.
Thanks!

Thanks @miguelrk !
I've merged. I have no release pipeline in place though and I'm on vacation. I will release after the 5th of September.
Matthias

Thanks @bitflower ! No worries, enjoy your time off!

Hey @bitflower, just a friendly reminder for the quick release, I'd appreciate it 🙏🏼

Hey @miguelrk ! Thanks for the reminder. Should be out!
https://github.com/bitflower/feathers-agenda/releases/tag/v0.1.4