cannot work with .easy files

Hi,
I use a mobile EEG from Neuroelectrics and their EEG recordings have a file named .easy as output. I cannot find any support to read this kind of file in your documentation. I also converted it to .edf with EEGLAB in Matlab, but I got the following error when reading it:
Traceback (most recent call last):   File "<stdin>", line 1, in <module>   File "/usr/local/lib/python3.6/site-packages/mne/io/edf/edf.py", line 1235, in read_raw_edf     exclude=exclude, preload=preload, verbose=verbose)   File "<string>", line 2, in __init__   File "/usr/local/lib/python3.6/site-packages/mne/utils.py", line 728, in verbose     return function(*args, **kwargs)   File "/usr/local/lib/python3.6/site-packages/mne/io/edf/edf.py", line 164, in __init__     annotmap, eog, misc, exclude, preload)   File "/usr/local/lib/python3.6/site-packages/mne/io/edf/edf.py", line 416, in _get_info     edf_info = _read_gdf_header(fname, stim_channel, exclude)   File "/usr/local/lib/python3.6/site-packages/mne/io/edf/edf.py", line 710, in _read_gdf_header     edf_info['number'] = float(version[4:]) ValueError: could not convert string to float:
Is there a way to work it out directly with .easy files? Is there a workaround for this string to float conversion error?
Thanks in advance!

try importing the .set file
and use mne.io.read_raw_eeglab

there is not .set file created by Neuroelectrics, only a file called .easy. Do you have a way to convert .easy into .set?

I mean save the eeglab file to .set and not to .edf

okay, thanks. I guess it's not possible to work with .easy files directly, so I will close the ticket since there is a workaround


Add Makefile

Thanks for submitting a PR! Please check the boxes below:

[x] I have run pre-commit to check linting
[x] I have filled in the "Changes" section below?
[x] I have filled in the "How did you test this code" section below?

Changes
Contributes to #2151.
This adds a Makefile along with the default dotenv file to the api project and modifies Python tools' configurations to accommodate for those.
The Makefile has been tested and refined for some time. It has been my personal daily driver for a couple of weeks. I went ahead and migrated the API PR workflow to Makefile.
The following targets are added:

docker-up, docker-logs and docker-down: manage the Docker Compose project to bring up dependencies for Flagsmith API (currently just Postgres defined in docker/db.yaml). Configurable via Compose's default environment variables.
docker-build: build the API image and tag it with the flagsmith-api:local tag. Tag name configurable.
test: Run Pytest. Pytest configuration resides in pyproject.toml now and establishes sane defaults: verbosity level to include full test names and the Django settings module. Additional options may be provided with an opts variable.
django-migrations: Autogenerate migrations. Specify appts with an opts variable.
django-migrate: Identical to run-docker.sh's migrate command.
django-serve: Spin up a gunicorn instance with live-reload enabled.
lint: Runs linters (lint-black, lint-isort and lint-flake8).
install: Installs dependencies (currently just install-packages, which installs dev dependencies too).

How did you test this code?

Ran every Makefile target and observerd the results:

Linter behaviour is identical to pre-commit.
pytest runs with correct Django settings module.
Docker Compose brings up the database with correct credentials and applies the default project name.
make docker-build applies the configured tag.
make django-migrate and make django-migrations wait for the database so i.e. make docker-up django-migrate won't crash.
make django-serve spins up a working API server and the live-reload works.

install, lint and test targets run in CI!

Yep really like this - we need to do the same for the frontend and docs I think!

we need to do the same for the frontend and docs I think!

Agreed. I suggest we merge this first and roll with it for a while. When the target list is settled, we'll be able to write a root Makefile too and document its usage for contributors.

Yep agree. Not sure if its best to have 1 makefile for the monorepo or individual ones in subfolders?

Not sure if its best to have 1 makefile for the monorepo or individual ones in subfolders?

I prefer individual ones with sensible common targets in the root (to be able to e.g. collectstatic after bundling the frontend).


Task86:Whitelist the odata queries for the /api/v2/FindPackagesById b…

…ased on the AppInsights data.

Hi @cristinamanum, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!

In order for us to evaluate and accept your PR, we ask that you sign a contribution license agreement. It's all electronic and will take just minutes. I promise there's no faxing. https://cla2.dotnetfoundation.org.

TTYL, DNFBOT;

@cristinamanum, Thanks for signing the contribution license agreement so quickly! Actual humans will now validate the agreement and then evaluate the PR.
Thanks, DNFBOT;

    public async Task<IHttpActionResult> Get(ODataQueryOptions<V2FeedPackage> options)

to my understanding, this is the method crawlers use, and here we need the whitelisting

Refers to: src/NuGetGallery/Controllers/ODataV2FeedController.cs:50 in 04bf7a2. [](commit_id = 04bf7a2fccfee0f6012b406ecf41f3c80a4fc9b0, deletion_comment = False)


Cell clustering unable to parse updated cell table format from ez_seg update

Describe the bug
The addition of ezSegmenter support now generates a cell table that include both the whole_cell and nuclear mask data, as well as a column, mask_type, specifying which is which.
This cell table format is currently incompatible with cell_cluster_utils.create_c2pc_data, which is required to create the cell-level data needed for clustering. The function requires each label to be unique for each FOV so it can index and assign correctly. That assumption cannot be made for the new cell table format, since each label now appears n times per fov, where n is the number of unique masks in question.
Expected behavior
For Pixie/Nimbus, the user should only be using whole_cell data. To extract the cell tables on an individual mask level, @bryjcannon included a function in the ez_seg_utils submodule that splits the combined cell table by the mask_type column. This should be called in notebook 1 on both the combined size_normalized and arcsinh_transformed tables.
Users can then choose which table (size_normalized or arcsinh_transformed) to input into notebook 3 or Nimbus.
To Reproduce
Run notebook 1, then Pixie/Nimbus, as is.

I created a very similar issue already: https://github.com/angelolab/ark-analysis/issues/1097

@cliu72 thanks for reminding, I'll close this one.


Missing mutation documentation

Hi, I need to run a mutation into shopify but so far I only found in your documentation how to run queries. I didn't find any parameter about mutation into index.ts and neither any mention in your doc. Is that possible?
Thanks.

@offjeff91 Here's an example of a mutation used to populate products on a store from our default template.
In general, using this example from the docs, the following
const response = await client.query({
  data: `{
    products (first: 10) {
      edges {
        node {
          id
          title
          descriptionHtml
        }
      }
    }
  }`,
});

can also be written
const response = await client.query({
  data: `query GetFirstTenProducts {
    products (first: 10) {
      edges {
        node {
          id
          title
          descriptionHtml
        }
      }
    }
  }`,
});

In other words, the query... part can be omitted as it's the default expected in a GraphQL query.  However, a mutation requires the mutation keyword, e.g.,
const response = await client.query({
  data: {
    query: `mutation populateProduct($input: ProductInput!) {
      productCreate(input: $input) {
        product {
          id
        }
      }
    }`,
    variables: {
      input: {
        title: 'My totally cool new product title',
        variants: [{ price: 1000.0 }],
      },
    },
  },
});

I hope this helps get you started on using mutations.

Thanks, @mkevinosullivan! I really appreciate.

client.query
I think the client only has request and fetch and not query.


Avoid possible memleak in X509_policy_check()

When tree_calculate_user_set() fails, a jump to error failed to
deallocate a possibly allocated |auth_nodes|.

Merged.
master: 67f060acefae34d820ccdb2f560d86ed10633500
1.1.0: b066ef30585bdb051f9aae84d3b5a5df402c43b7


Allow transliterate names for non-Latin scripts.

In locales with non-Latin script, the names should be transliterated to be readable.

That needs way more changes, especially for the flathub variable. At least each key needs to be created in the english translation file, but flathub shows up in many places more.
I kept it a static string like this for a reason, still not exactly against you changing it, but it will be more work and likely even more to maintain.

There is https://github.com/flathub-infra/website/pull/3335 for the mastodon part of this, along with upstream discussion, so that part should be removed from here


OpenMaya as the name for the project is conflicting with Autodesk's library

It's pretty confusing to be naming this project the same as Autodesk's internal library:
http://download.autodesk.com/us/maya/2011help/API/group___open_maya.html

Yes, it may confuse a few people, but I decided to ignore it because the project opens maya to other renderers, so why not naming it this way? Unless Autodesk complains about it of course...


Introduced Utils::String#titleize

What
Utils::String#titleize
How does it works?
require 'lotus/utils/string'

string = Lotus::Utils::String.new 'lotus utils'
string.titleize # => "Lotus Utils"

string = Lotus::Utils::String.new 'lotus-utils'
string.titleize # => "Lotus Utils"

string = Lotus::Utils::String.new 'LotusUtils'
string.titleize # => "Lotus Utils"

# etc..

Why?
This is a supporting feature for Lotus::Helpers' form helper.
<%=
  form_for(:book, routes.books_path) do
    label :extended_title
    # ...
  end
%>

That label accepts a symbol that should be titleized to become:
<label for="book-extended-title">Extended Title</label>

Coverage increased (+0.01%) to 98.83% when pulling 2bbd817d72b451621570f7e4ea40bba2cc7dccaa on string-titleize into ceed25d187dd7edb8a9180305ab5f6c4deba109b on master.

:100:


Add code deploy logs to cloudwatch

Coverage increased (+0.5%) to 69.968% when pulling ec60d8b09afc6f36bac783ad059988f4a0f0ad96 on code_deploy_logs into 816f81e624f28a88f3745050bb774f5d2dd4a8c7 on master.

Coverage increased (+0.5%) to 69.968% when pulling bf1b37d89da17294c45d349ca9fbca8160c4ca1b on code_deploy_logs into 816f81e624f28a88f3745050bb774f5d2dd4a8c7 on master.

Coverage increased (+0.5%) to 69.968% when pulling 9cd3258e8eae14f12dd7a5ed745521df7626a331 on code_deploy_logs into 816f81e624f28a88f3745050bb774f5d2dd4a8c7 on master.

Coverage increased (+0.5%) to 69.968% when pulling 9cd3258e8eae14f12dd7a5ed745521df7626a331 on code_deploy_logs into 816f81e624f28a88f3745050bb774f5d2dd4a8c7 on master.

Nova does work with Python 3, it's fully compatible with 2.7 3.4 & 3.5 and needs to be kept that way particularly when it's being run on EC2 instances which can be Python 3...

LGTM 👍


Optional Feature: Rounded BarChart

Need this feature for a project requirement, and may as well offer this up to the source project. Non-breaking change. By default, the corner radius will be 0, so existing users who don't use or even know about this feature won't be affected.
Below is the sample I added:

very nice, thank you for your contribution.


connection stuck on an infinite loop

jsforce seems to be creating a login loop for some reason for me
`    context.conn = new jsforce.Connection({loginUrl :"https://login.salesforce.com",
instanceUrl: 'https://UM5.salesforce.com'
});
const username = "xxxxxxx";
const securityToken = "xxxxxxxxxxx";
const password = "xxxxxxxxx" + securityToken;

context.conn.login(username, password, function(err, userInfo) {
  if (err) { return $log(err.message); }

  $log(context.conn.accessToken);
  $log(context.conn.instanceUrl);
  $log("User ID: ");
  $log(userInfo.id);
  $log("Org ID: ");
  $log(userInfo.organizationId);

});`

I've tried with and without the instanceUrl, there is no error, the info in the callback gets logged once, but in salesforce I can see hundreds of SUCCESSFUL log ins everytime

Same issue for me

I've noticed this issue can happen when you need to reset your password or log in requires some manual action.

triaging old issues...
this is related to this: https://github.com/jsforce/jsforce/issues/1411
and how jsforce handles 401, closing as dup.


Some improvements in sample-projects

I added method for update tweets so now one can see, how changes are observable.
Moreover removed some minor bugs.

Current coverage is 96.05% (diff: 100%)

Merging #711 into master will not change coverage

@@             master       #711   diff @@
==========================================
  Files            87         87
  Lines          2457       2457
  Methods           0          0
  Messages          0          0
  Branches        329        329
==========================================
  Hits           2360       2360
  Misses           68         68
  Partials         29         29

Powered by Codecov. Last update 2aeaea6...ae8fc3d

@ValeriusGC Thanks!

Ok for me 👍  just minor issue

@artem-zinnatullin, @karlicoss PTAL, please

Linking to #622


Hooks values  originalDoc and previousDoc are badly typed

Bug Report
The values originalDoc and previousDoc passed to functions of type FieldHook, CollectionBeforeChangeHook and CollectionAfterChangeHook do not match.

There is no distinction between beforeChange and afterChange field hooks. This makes in the beforeChange hook, previousDoc is typed as defined when it is not (as mentioned in the documentation)

In most cases, the document has "_id" and "__v" fields instead of simple "id".

Steps to Reproduce
Create this collection config :
import type {
  CollectionConfig,
  CollectionBeforeChangeHook,
  CollectionAfterChangeHook,
  FieldHook,
} from 'payload/types'

/* Result of "payload generate:types" */
interface IDoc {
  id: string
  name?: string
  createdAt: string
  updatedAt: string
}

interface IDocWithNativeFields extends IDoc {
  _id?: string
  __v?: number
}

function testDocType(labels: string[], doc: IDocWithNativeFields) {
  const correct = doc && doc.id && !doc._id && !doc.__v
  console.log(correct ? '✔' : '❌', labels.join('\t'))
}

const fieldBeforeChange: FieldHook<IDoc> = ({ originalDoc, previousDoc }) => {
  testDocType(['field', 'beforeChange', 'previousDoc'], previousDoc)
  testDocType(['field', 'beforeChange', 'originalDoc'], originalDoc)
}

const fieldAfterChange: FieldHook<IDoc> = ({ originalDoc, previousDoc }) => {
  testDocType(['field', 'afterChange', 'previousDoc'], previousDoc)
  testDocType(['field', 'afterChange', 'originalDoc'], originalDoc)
}

const collectionBeforeChange: CollectionBeforeChangeHook<IDoc> = ({
  originalDoc,
}) => {
  testDocType(['collection', 'beforeChange', 'originalDoc'], originalDoc)
}
const collectionAfterChange: CollectionAfterChangeHook<IDoc> = ({
  previousDoc,
}) => {
  testDocType(['collection', 'afterChange', 'originalDoc'], previousDoc)
}

export const Doc: CollectionConfig = {
  slug: 'doc',
  hooks: {
    beforeChange: [collectionBeforeChange],
    afterChange: [collectionAfterChange],
  },
  fields: [
    {
      name: 'name',
      type: 'text',
      hooks: {
        beforeChange: [fieldBeforeChange],
        afterChange: [fieldAfterChange],
      },
    },
  ],
}

See the console output when you create or update a doc:
❌ collection   beforeChange    originalDoc
❌ field        beforeChange    previousDoc
❌ field        beforeChange    originalDoc
❌ field        afterChange     previousDoc
✔ field        afterChange     originalDoc
❌ collection   afterChange     originalDoc

Other Details

payload version: "^1.5.4"

I think this is partly in line with this issue #1563
Thank you for this ambitious and forward-looking project 👏

Hey @peufo — thanks for bringing this up!
Yes, it certainly does overlap with #1563. We have some big TS stuff in the works that I am VERY excited about and this will be resolved alongside that roadmap item as you expected!
In the meantime, I'm going to convert this to a discussion because this is more about improving our type accuracy rather than something explicitly broken, but we can keep the conversation going there.
How's that?


Best way to debug things?

I have things compiled and integrated, however I get an insta crash when I try to add my one node to a scene.
the code is in _physicsProcess()
override func _physicsProcess(delta: Double) {
        if self.isOnFloor() {
            self.currentyYVelocity = 0;
            if Input.shared.isActionJustPressed(action: "jump") {
                self.currentyYVelocity = kJumpVelocity
            } else {
                self.currentyYVelocity = GD.maxf(a: currentyYVelocity - kGravity, b: -2000)
            }
        }

        // Movement
        var movementInputVector = Input.shared.getVector(negativeX: "move_left", positiveX: "move_right",
                                                         negativeY: "move_forward", positiveY: "move_back")
        var lerpedX = GD.lerp(from: movementInputVector.x * kMovementSpeed, to: self.velocity.x, weight: kLerp)
        var lerpedZ = GD.lerp(from: movementInputVector.y * kMovementSpeed, to: self.velocity.z, weight: kLerp)
        self.velocity = Vector3(x: lerpedX, y: Float(self.currentyYVelocity), z: lerpedZ)

        // Set character rotation
        if movementInputVector != Vector2.zero {
            self.character?.setVelocity(velocity: self.velocity, speed: kMovementSpeed, lerpValue: kRotationLerp)
        } else {
            self.character?.stopped()
        }

        self.moveAndSlide()
    }

I can see this code for lerp in the stack trace
Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x1ac3e8724 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x1ac41fc28 pthread_kill + 288
2   libsystem_c.dylib             	       0x1ac32dae8 abort + 180
3   Godot                         	       0x104c25760 0x104848000 + 4052832
4   libsystem_platform.dylib      	       0x1ac44ea84 _sigtramp + 56
5   libswiftCore.dylib            	       0x1bb4af908 bool swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1>>::doDecrementSlow<(swift::PerformDeinit)1>(swift::RefCountBitsT<(swift::RefCountInlinedness)1>, unsigned int) + 132
6   libswiftCore.dylib            	       0x1bb4af908 bool swift::RefCounts<swift::RefCountBitsT<(swift::RefCountInlinedness)1>>::doDecrementSlow<(swift::PerformDeinit)1>(swift::RefCountBitsT<(swift::RefCountInlinedness)1>, unsigned int) + 132
7   libSwiftGodot.dylib           	       0x112406348 specialized Float.init(_:) + 240
8   libSwiftGodot.dylib           	       0x112405e60 Float.init(_:) + 16
9   libPlantQuest.dylib           	       0x11057f9e0 static GD.lerp(from:to:weight:) + 8 (GD+Extension.swift:13) [inlined]
10  libPlantQuest.dylib           	       0x11057f9e0 PlayerCharacter._physicsProcess(delta:) + 752 (PlayerCharacter.swift:37)
11  libSwiftGodot.dylib           	       0x112723a94 specialized _Node_proxy_physics_process(instance:args:retPtr:) + 40 (Node.swift:1626) [inlined]
12  libSwiftGodot.dylib           	       0x112723a94 _Node_proxy_physics_process(instance:args:retPtr:) + 40 [inlined]
13  libSwiftGodot.dylib           	       0x112723a94 @objc _Node_proxy_physics_process(instance:args:retPtr:) + 52 (<compiler-generated>:1622)

I do have a simple wrapper to the GD lerp
extension GD {
    static func lerp(from: Float, to: Float, weight: Float) -> Float {
        return Float(lerp(from: Variant(from), to: Variant(to), weight: Variant(weight))) ?? 0
    }
}

My only guess is that it crashes when trying to allocate the Float which is the return value of the LERP function
As a side note, it seems like the only interface to troubleshooting errors is that it just crashes and you get a tiny amount of a stack trace? Is there a way to troubleshoot this before that? I think in the long run I can try to set up test target for a lot of this I suppose.

Weird I tried to just pipe the Variant result from lerp into GD.print and it crashed even just doing that

Application Specific Information:
abort() called

Thread 0 Crashed::  Dispatch queue: com.apple.main-thread
0   libsystem_kernel.dylib        	       0x1ac3e8724 __pthread_kill + 8
1   libsystem_pthread.dylib       	       0x1ac41fc28 pthread_kill + 288
2   libsystem_c.dylib             	       0x1ac32dae8 abort + 180
3   Godot                         	       0x102fb5760 0x102bd8000 + 4052832
4   libsystem_platform.dylib      	       0x1ac44ea84 _sigtramp + 56
5   libswiftCore.dylib            	       0x1bb4f36a0 swift_getObjectType + 200
6   libswiftCore.dylib            	       0x1bb1dc2d0 _print_unlocked<A, B>(_:_:) + 268
7   libPlantQuest.dylib           	       0x10e90fa68 specialized DefaultStringInterpolation.appendInterpolation<A>(_:) + 44 [inlined]
8   libPlantQuest.dylib           	       0x10e90fa68 PlayerCharacter._physicsProcess(delta:) + 720 (PlayerCharacter.swift:41)
9   libSwiftGodot.dylib           	       0x110ab3a94 specialized _Node_proxy_physics_process(instance:args:retPtr:) + 40 (Node.swift:1626) [inlined]
10  libSwiftGodot.dylib           	       0x110ab3a94 _Node_proxy_physics_process(instance:args:retPtr:) + 40 [inlined]
11  libSwiftGodot.dylib           	       0x110ab3a94 @objc _Node_proxy_physics_process(instance:args:retPtr:) + 52 (<compiler-generated>:1622)

The print line was just
GD.print("Found \(value)")

This is a good topic.
At this stage of the binding where there might be bugs in the marshaling code, I rely on having both an address-sanitized version of Godot and debug builds of Godot - and the same for the plugin.   This way, I can catch some corruption bugs earlier, and when I get a nasty looking crash the address sanitizer has enough hints to assist me.
In the meantime, a minimal repro would help me unblock you.  I think this bug has enough to go by.

Ah this reminded me of one thing: I saw this problem with another GD API using Variant, and when I looked at it, I could not figure out why it was crashing.    I am not sure I will be any luckier until I do some Godot instrumentation on their macros to see what is going on.

I suspect my recent changes to Variant marshaling fixed this, because I plugged your scenario into a test and it works.

Yes that does seem to be fixed


Add MFA support

Multi Factor Support (MFA) can be a great addition to our security posture when it comes to providing secure access to our end users. It would also reduce the attack surface for users with private repositories. Here's a few kinds of MFA we can add:

Hardware 2FA (like a Ubikey)
Software 2FA (TOTP like Authy)
Maybe also Email/Phone

All configurable from the client's profile settings.

@guacamole this one looks a place-stop-shop for our use case - https://github.com/authelia/authelia


Remove default implicit configuration that sets the concurrency to 1

If the concurrency of an action is not configured, the plugin sets it to 1 by default, because of https://github.com/serverless/serverless-openwhisk/blob/1de03125ab7bcbf2d27d5a3ab2eb17f9b53500b6/compile/functions/index.js#L58
This is a problem because it overrides the default concurrency that can be set by default on the Openwhisk platform itself. So for example, if the platform defines a default concurrency of 200, not setting it in the serverless config "silently" resets this to 1.
I'll provide a PR for that.

@jthomas I'm wondering if we also want to the same removal of the default values for the memory and timeout parameters. WDYT?

@jthomas Gentle ping wrt. the previous comment, thanks.

@cjelger +1 that's good idea.


Move UI example to testbed

Objective
UI example is quite extensive, probably not the best teaching example anymore.
Closes #16230.

It's the same on main, the example and these changes are fine, something else is broken.

@alice-i-cecile the merge failed due to "error: no example target named ui" in the wasm build, FYI.

Yeah, I think that we need to tweak the testing setup somehow. @mockersf or @BD103 may know the answer offhand?

It's the same on main, the example and these changes are fine, something else is broken.

Seems likely that this was broken by #16088 and wasn't noticed before #16151 was merged.
That PR had some other side effects in examples: #16239, #16240. I didn't open an issue for ui because it hasn't actually changed since #16151 was merged, so I didn't notice the problem.

Yeah not surprised, that PR accumulated a lot of changes with different people pushing to it and it got merged before I could check its final state.

Oh whoops, let's see what's going on in the wasm CI :eyes:

Oh, hrm. Interesting! It mentions this particular example as a literal :laughing:
       - name: First Wasm build
        run: |
          cargo build --release --example ui --target wasm32-unknown-unknown

I guess maybe it needs one build with the release flag done initially? Anyway, easy enough fix.

@alice-i-cecile in theory this ought to be OK to go back in the merge queue.


Add SmallVec storage.

SmallVec storage from smallvec crate, for optimized storage of small number of components.
Should it be behind feature flag, since in brings new dependency?

Cannot review properly because I'm using my phone, but isn't this unpractical because as soon as you have more entities it isn't useful anymore? Probably it should rather be some redirection storage.On May 24, 2017 4:04 PM, Dzmitry Malyshau<EMAIL_ADDRESS>wrote:Thank you for the PR!
Anyone familiar with smallvec wants to review the unsafe code?
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or mute the thread.

@torkleyy , yes when placed more items it allocates. Also I can replace smallvec for arrayvec and make it panic instead of allocating when it exceeds inline size limit.

@kvark , smallvec almost exactly repeats standart Vec, so I basically just copied implementation from VecStorage and it seems to work.

@Object905 My main concern here is that I don't see it practical, like @torkleyy said. Our VecStorage may not be using lots of entries, but it surely allocates a lot, so there is no way SmallVec could help replacing it.
A different situation is with DenseVecStorage, where the actual data is packed. I think it would make sense to have smallvec backing it (actual data vector only, while keeping the redirection tables to be regular vectors). Hiding the whole thing (new DenseVecStorage) behind a feature gate also sounds good.
Would you want to rewrite the PR for DenseVecStorage (replacing the current one) instead of Vec?

@Object905 To explain this a bit more:
On insertion, your storage tries to insert a component at an index id. Even though you don't need many components, you need a pretty big Vec, because there's an uninitialized element for every entity without that component.
This means that a SmallVec with 16 elements does not support a component for an entity with id 16 or greater.
The DenseVecStorage works by using two collections; the first one for an entity -> index relation and the second one gives you the component from a given index (the one you got from the first collection).
That being said, I'm not sure if SmallVec does provide any advantage here:

fixed-size
needs more space than Vec
even though it's stored on stack usually, it ends up on the heap because we need to Box it.

One advantage might be that it is more cache-efficient (because it's more plain), but I'm not sure what impact this has in practice.

Right, @torkleyy, so even if we port DenseVecStorage, we'll not get much speed-up from smallvec...

@torkleyy thanks for explaining this, I just didn't know how's Vec used with indices in VecStorage, i thought that VecStorage behaves like DenseVecStorage and didn't quite understand it. @kvark yes I'd like to rewrite it to use smallvec, but i think that DenseVecStorage is ok as it is now, and SmallVecStorage just needs to be rewritten to use  redirection tables like in DenseVecStorage, and also hidden behind feature flag. I'll work on it soon.

@Object905 Which benefits do you expect when using a SmallVec?

@torkleyy I get the idea after reading this article. Benefits are that elements are stored on the stack. Also there is similar to smallvec data structure from Qt.

@Object905 Okay, let's try it out then. They are not really stored on the stack in this situation, but they allow a flat structures, which is what I meant with

One advantage might be that it is more cache-efficient


edit lock stays, after locking browser was closed before saveing the draft

The edit lock on a tiddler stays, and the edit button is disabled (padlock icon) after the writing/locking browser was closed before saveing the draft. After restarting the server, the lock is gone.
How can this tiddler be unlocked on a running server?

I am running (check any that apply, put an x inside the [ ] to check a box, like this: [x]):

[x] Windows
[ ] OSX
[ ] Linux
[ ] Other

and using

[x] The nodejs version
[ ] The single file executable

Before posting I read issue guidelines and:

[x] I am using the newest version (node LTS), tiddlywiki 5.1.23, bob newest, os win 10 newest updates, firefox/chrome newsest
[x] The answer to my question isn't listed in the documentation or this isn't
a question
[x] This is not a duplicate issue
[?] I have not done anything that required me to set acceptance to
I Will Not Get Tech Support For This

The quick answer to your question is to edit $:/state/Bob/EditingTiddlers. In the list field it has a list of all of the tiddlers currently being edited by anyone on the server. So you can remove the tiddler name from the list field or delete the tiddler and it will remove the lock. Just be careful when you do this to avoid removing a lock from someone else actually editing the tiddler.
I have made some progress toward fixing this problem, but I don't know when the solution will be finished.


Compatibility with laravel 9

Hello,
It is possible to be compatible with laravel 9 ?
When i try to use with it, i have a message : "Problem 1
- Root composer.json requires khadegd/laravel-breeze-bootstrap dev-main -> satisfiable by khadegd/laravel-breeze-bootstrap[dev-main].
- khadegd/laravel-breeze-bootstrap dev-main requires illuminate/filesystem ^8.42 -> found illuminate/filesystem[v8.42.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require."
Thanks,
Charly

Hi, tried installing your package.
laravel new my-app
Installing laravel/laravel (v9.1.7)
Errors as follows:
tried the recommended
composer require khadegd/laravel-breeze-bootstrap --dev
Using version dev-main for khadegd/laravel-breeze-bootstrap
./composer.json has been updated
Running composer update khadegd/laravel-breeze-bootstrap
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires khadegd/laravel-breeze-bootstrap dev-main -> satisfiable by khadegd/laravel-breeze-bootstrap[dev-main].
    - khadegd/laravel-breeze-bootstrap dev-main requires illuminate/filesystem ^8.42 -> found illuminate/filesystem[v8.42.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.

You can also try re-running composer require with an explicit version constraint, e.g. "composer require khadegd/laravel-breeze-bootstrap:*" to figure out if any version is installable, or "composer require khadegd/laravel-breeze-bootstrap:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

composer require khadegd/laravel-breeze-bootstrap
Using version dev-main for khadegd/laravel-breeze-bootstrap
./composer.json has been updated
Running composer update khadegd/laravel-breeze-bootstrap
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Root composer.json requires khadegd/laravel-breeze-bootstrap dev-main -> satisfiable by khadegd/laravel-breeze-bootstrap[dev-main].
    - khadegd/laravel-breeze-bootstrap dev-main requires illuminate/filesystem ^8.42 -> found illuminate/filesystem[v8.42.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.

You can also try re-running composer require with an explicit version constraint, e.g. "composer require khadegd/laravel-breeze-bootstrap:*" to figure out if any version is installable, or "composer require khadegd/laravel-breeze-bootstrap:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.

$ composer require khadegd/laravel-breeze-bootstrap:*
./composer.json has been updated
Running composer update khadegd/laravel-breeze-bootstrap
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - khadegd/laravel-breeze-bootstrap[dev-main, dev-upstream-1.x] require illuminate/filesystem ^8.42 -> found illuminate/filesystem[v8.42.0, ..., 8.x-dev] but these were not loaded, likely because it conflicts with another require.
    - Root composer.json requires khadegd/laravel-breeze-bootstrap * -> satisfiable by khadegd/laravel-breeze-bootstrap[dev-main, dev-upstream-1.x].

Installation failed, reverting ./composer.json and ./composer.lock to their original content.


jdk 1.8 exception

download release version is ok.
use brew install mvnd, mvnd --version
Error: A JNI error has occurred, please check your installation and try again
Exception in thread "main" java.lang.UnsupportedClassVersionError: org/mvndaemon/mvnd/client/DefaultClient has been compiled by a more recent version of the Java Runtime (class file version 55.0), this version of the Java Runtime only recognizes class file versions up to 52.0
at java.lang.ClassLoader.defineClass1(Native Method)
at java.lang.ClassLoader.defineClass(ClassLoader.java:756)
at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:142)
at java.net.URLClassLoader.defineClass(URLClassLoader.java:468)
at java.net.URLClassLoader.access$100(URLClassLoader.java:74)
at java.net.URLClassLoader$1.run(URLClassLoader.java:369)
at java.net.URLClassLoader$1.run(URLClassLoader.java:363)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:362)
at java.lang.ClassLoader.loadClass(ClassLoader.java:418)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:355)
at java.lang.ClassLoader.loadClass(ClassLoader.java:351)
at sun.launcher.LauncherHelper.checkAndLoadMain(LauncherHelper.java:601)

i read release0.7.1 description showing close issue "Different java versions for mvnd and maven #512" , the issue suggest that we can use JDK11 runtime for all and set the --release 8 which produces JDK8 compatible code., such as,
mvnd -Dmaven.compiler.release=8 compile.
as well as , the issue say that the mvnd needs at minimum JDK8 to run......maybe mvnd can run in jdk8 and we need to build mvnd from source in jdk 8 in order to get executable file, which we can see readme .
more: https://github.com/apache/maven-mvnd/issues/512

Build mvnd

You need to use the mvnd compiled to native instead of mvnd.sh, as the java client requires JDK 11.


Is getexcalidraw/excalidraw on DockerHub Your Official Builds?

Hey there, I found getexcalidraw/excalidraw on DockerHub and I was curious whether those were your guys's official builds or whether it was just somebody random hosting them. The build's aren't automated on DockerHub so I can't verify which repo they came from and I wanted to make sure I knew who I was pulling the containers from.

/cc @kbariotis

Apparently yes: https://github.com/excalidraw/excalidraw/blob/master/.github/workflows/publish-docker.yml#L18
But I haven't worked with DockerHub, so best wait for @kbariotis to confirm

@kbariotis: if we renamed the docker org to getexcalidraw, we should update readme to reflect that. (I haven't followed the PRs, so forgive me if it was already discussed.)

Oh I was not aware that we had that in the README, I thought we haven't announced it yet.
@zicklag we are stuck with Docker registry as we are trying to get the excalidraw organization name back. I wouldn't use that image yet in case we rename it. We should be ready very shortly though and I will let you know on this issue. :)
@dwelle I will remove that from the readme.

Thanks for the prompt response!  Try it out and let us know of any feedback. :)

Awesome thanks!


Add chart for EAP 7.4

Signed-off-by: Jeff Mesnil<EMAIL_ADDRESS>

mmhm afaict, the failure in the GH action is not related to the PR commit but to the setup of the action...

@jmesnil we are sunsetting this repo. Can you send your new chart to our new repo https://charts.openshift.io/

send the owners file in an initial PR: https://github.com/openshift-helm-charts/charts/tree/main/docs#preparation
If your chart is for a Red Hat product use the redhat path: https://github.com/openshift-helm-charts/charts/tree/main/charts/redhat/redhat
If your chart is an unsupported project use the community path: https://github.com/openshift-helm-charts/charts/tree/main/charts/community/redhat

@dperaza4dustbit thanks for the info, I've started the process to release EAP Helm charts with https://github.com/openshift-helm-charts/charts/pull/315


Add data assimilation using usgs timeslices

https://github.com/NOAA-OWP/t-route/pull/258#discussion_r584912652 - From this discussion.
RnR file can run with DA, but no matching columns in the parity check. I am wondering what the locations are for the timeslice files for this RnR? RnR had 'feature_id' instead of 'station_id' as well. Currently, this runs, but the parity test is comparing two totally different things essentially.

@jhrehanoaa -- I think this is a merge relic and am closing. Please reopen if this is still a relevant PR.


Add onBytesReceived callback to consolidateHttpClientResponseBytes()

Description
This will allow us to plumb the byte chunks in a chunked
network response up to the higher levels of the framework
to notify interested parties of network loading progress.
Related Issues
https://github.com/flutter/flutter/issues/32374
Tests
I added the following tests:

Verification that the onBytesReceived callback is invoked correctly.
Verification that the method handles the gzip permutations correctly.
Verification that if the callback throws, the error propagates to the future that is returned by the function.

Checklist
Before you create this PR confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I signed the [CLA].
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I updated/added relevant documentation (doc comments with ///).
[x] All existing and new tests are passing.
[x] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[x] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Does your PR require Flutter developers to manually update their apps to accommodate your change?

[ ] Yes, this is a breaking change (Please read [Handling breaking changes]). Replace this with a link to the e-mail where you asked for input on this proposed change.
[x] No, this is not a breaking change.

cc @goderbauer


Attempt a full reference to allow docs.ms documentation to properly render

See title! Going to grab the adjusted artifact, check to see if our docs render, then ship it to the docs team to see if they can render the @{link syntax properly.

The doc team actually came back with a

this is a bug on our side.

@XiaoningLiu you can ignore this :)


gpgfile never retries after decryption failure

If gpgfile fails to decrypt the target file (for example, due to missing gpg keys or something), the exec command fails and causes the puppet run to fail, but because the target file was created, the exec will not be tried again.

Fixed by PR #9, I think.


Query request headers are clobbered by token methods

The token and bearer_token methods of the Query class overwrite any headers that might otherwise be set on a query instance. Any methods that add a header should not completely replace all headers.

@frankinspace, please label this as a bug. Also, I submitted a NAMS request to become a maintainer, as you suggested. Did you see the request?


Can I embed this in my app?

I have an application where users design their own emails. Is it possible to use this project to create an embedded editor in my app?

If you are using React you can use the package to add the editor into your app. Unfortunately, I don’t have plan to add the embedding right now, maybe later.

Hey @arikchakma, is there a way to add text content to the editor without typing. Like for example, I want to add "hello there" by clicking a button, not typing.

Hey @arikchakma, is there a way to add text content without typing. Like, I want to add "hello world" by clicking a button without typing anything on the editor


Fix LessonCard completion badge styles

Closes #1405
This PR force background: transparent declaration to be applied with the !important flag so it overrides bootstrap background styles.
Before:

After:

This new solution is much nicer. Good job!


change prefix of action variables to 'command'

After some discussion we've decided to change the prefix of action variables from 'action' to 'command'.
So something like ${action.pickProcess} will become ${command.pickProcess}
@isidorn please ping @edumunoz after pushing this to master.

Ping @edumunoz this has been pushed to master


Publishing a string in to PubSub topic introduces quotes to the message

Environment details

OS: OS X 10.12.3
Node.js version: v6.10.0
npm version: 3.10.10
@google-cloud/pubsub version: 0.9.0

Steps to reproduce

require @google-cloud/pubsub
publish a message topic.publish('someMessage') (as described in the documentation)
pull the message and it will have "someMessage" as data

I think this is caused because the message data is being stringified if it is not a Buffer here but I do not think it is the intended behaviour? At least the documentation does not make it clear.

This is intended. We consistently publish messages in JSON format so that a JSON parser on the receiving end has a predictable way to handle the messages it receives. When our library returns the messages, we do a JSON.parse to decode it back to its native JS form:
topic.publish('test')

subscription.on('message', function(message) {
  message.data === 'test'
})

Thanks for the explanation @stephenplusplus, that explains a lot. The receiving end in my example was written in Ruby. It seems the Ruby API does not expect this behaviour. An alternate service publishing messages to the same queue was written in Python, no problems here. Shouldn't this inconsistency between the different APIs be documented?

I'm glad that cleared it up, and thank you for bringing it up. I don't know of a precedent or requirement that the client libraries are expected to behave the same way, but the fact that you experienced an annoying delay while you tried to figure it out and move on with your app is a good enough reason to me that we should add this in the docs somewhere. I'll keep the issue open and mark with a help wanted label-- feel free to send us a PR if you're up for it!

Fixed in #2214-- thanks again!

Cool! Thank you too!


Add time cog aliases

Add some commonly mistakenly used aliases to the time command, like !evetime

this uses slash commands now, so with client hints and autofill its not relevant


"google_sign_in" not working on an actual device but work only on emulators

the "google_sign_in" plugin works only my emulator but then gives an error when I try it on an actual device

and this is my code for google_sign_up

my device had active internet connection, as it was connected to my WIFI,
And the version of android on the emulator is android P while the actual device which I tested on was running android 7 (Nougat)
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Diego Velásquez López<EMAIL_ADDRESS>Sent: Wednesday, November 21, 2018 1:27:50 AM
To: flutter/flutter
Cc: kwaku96; Author
Subject: Re: [flutter/flutter] "google_sign_in" not working on an actual device but work only on emulators (#24573)
Could you add more info?

What version of Android Emulator are you testing?
What version of Android has your device?
Are you sure your device has active Internet connection?

—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/flutter/flutter/issues/24573#issuecomment-440451715, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AkWikHsPbzkitRC2eXZ0Sw1cTT1E6Oy0ks5uxIHmgaJpZM4Yryku.

Did you use the same apk file for emulator an device ?  or release mode for device?

Looks like #24378, #22784
Can you please post the console output the error produces?

This is the output when I run flutter doctor -v
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Günter Zöchbauer<EMAIL_ADDRESS>Sent: Wednesday, November 21, 2018 11:28:21 AM
To: flutter/flutter
Cc: kwaku96; Author
Subject: Re: [flutter/flutter] "google_sign_in" not working on an actual device but work only on emulators (#24573)
Please add the output of flutter doctor -v.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/flutter/flutter/issues/24573#issuecomment-440577805, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AkWikPgkHgRLfOqyZ5wcG52dWUHEukoTks5uxQ6lgaJpZM4Yryku.

<EMAIL_ADDRESS>This is the output from the console

From: Günter Zöchbauer<EMAIL_ADDRESS>Sent: Wednesday, November 21, 2018 11:30:28 AM
To: flutter/flutter
Cc: kwaku96; Author
Subject: Re: [flutter/flutter] "google_sign_in" not working on an actual device but work only on emulators (#24573)
Looks like #24378https://github.com/flutter/flutter/issues/24378, #22784https://github.com/flutter/flutter/issues/22784
Can you please post the console output the error produces?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/flutter/flutter/issues/24573#issuecomment-440578405, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AkWikJaMgMZc782Dc97HCo_UoMJRXpAcks5uxQ8kgaJpZM4Yryku.

This when I used the emulator
Sent from Mailhttps://go.microsoft.com/fwlink/?LinkId=550986 for Windows 10

From: Günter Zöchbauer<EMAIL_ADDRESS>Sent: Wednesday, November 21, 2018 11:30:28 AM
To: flutter/flutter
Cc: kwaku96; Author
Subject: Re: [flutter/flutter] "google_sign_in" not working on an actual device but work only on emulators (#24573)
Looks like #24378https://github.com/flutter/flutter/issues/24378, #22784https://github.com/flutter/flutter/issues/22784
Can you please post the console output the error produces?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/flutter/flutter/issues/24573#issuecomment-440578405, or mute the threadhttps://github.com/notifications/unsubscribe-auth/AkWikJaMgMZc782Dc97HCo_UoMJRXpAcks5uxQ8kgaJpZM4Yryku.

@kwaku96 I can't see any actual content in your last 3 comments.
Can you please use the web interface to add the content instead responding to the notification mail?

Without additional information, we are unfortunately not sure how to resolve this issue. We are therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Hard to gather statistics on crashes vs total sessions

In Hockey App it was easy to compare the total number of crashes and sessions for a particular version and timeframe.
In App Center every time I switch between Diagnostics and Analytics it resets the version and  and time selections which makes it extremely painful to gather the statistic that we're looking at which is % of sessions that end in a crash (crashes/sessions * 100)

Hi Steve, thanks for this feedback. I've added the service area owners to the issue and we will keep you updated.

I added a similar feature request! Its a very basic piece of data from crash reporters that's unfortunately missing here! https://github.com/microsoft/appcenter/issues/218


feat(@schematics/angular): add type checking for protractor.conf.js file

add type checking for protractor.conf.js file make edit this file more easily.
related to #13958

@alan-agius4 done.

@dobbydog, thanks for your contribution.

@alan-agius4 I think you tagged the wrong person. 😅


Fix age restricted videos

It's better to completely switch to InnerTube API (this will fix 403 error completely), also will be good create something like YoutubeConstants for containing all payloads and urls for requests to API, if sedmelluq okay with that I will do it

Please merge this PR. This fixes a critical issue we've been having for a long while now.


remove instance overhead

This also fixes instances not being sent when FireAll, FireExcept and FireList are used.

closes #32


Update documentation

Thank you for contributing to naz.
Every contribution to naz is important.
Contributions are under the MIT License.
Answer the following questions,
What(What have you changed?)

Update documentation

Why(Why did you change it?)

In https://github.com/komuw/naz/pull/202, we added support for optional params in submit_sm; this is the PR to update documentation for that previoos PR.

References:

Codecov Report

Merging #207 into master will decrease coverage by 0.24%.
The diff coverage is 67.07%.

@@            Coverage Diff             @@
##           master     #207      +/-   ##
==========================================
- Coverage   84.72%   84.48%   -0.25%
==========================================
  Files          15       15
  Lines        1532     1553      +21
==========================================
+ Hits         1298     1312      +14
- Misses        234      241       +7

Impacted Files
Coverage Δ

naz/codec.py
97.72% <ø> (-0.19%)
:arrow_down:

naz/state.py
87.87% <55.55%> (-12.13%)
:arrow_down:

naz/client.py
80.93% <84.61%> (+0.17%)
:arrow_up:

naz/protocol.py
81.96% <93.33%> (+11.72%)
: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 aafd160...8a8999c. Read the comment docs.


Fixes to stablise PSSessions

Changes the modules to dispose of remote sessions rather than re-use them to address a number of issues in some environments where limits of PSRemoting were being hit. Also made an update to the join farm resource to remove a redundant parameter, and a minor bug fix to the way the distributed cache resource looks up current settings.

Pinging @caadam for a code review

Closing pull request in favour of other changes being made to address PSSession use, subsequent PR to follow


Pip does not support python 2 anymore

Hello I have a problem,
I've installed Kin using the most recent Pip (python3) and when tried to use it I get an error:
Traceback (most recent call last):   File "/usr/local/bin/kin", line 5, in <module>     from kin.kin import main   File "/usr/local/lib/python3.9/site-packages/kin/kin.py", line 5, in <module>     from verifier import Verifier ModuleNotFoundError: No module named 'verifier'
I've read on the forum that Kin is made for python 2.7 only. Is it true? If so, is Kin unusable now since Pip supports only python 3 now?

Hi @maciejkarolczyk !
Yeah, originally Kin was created with Python 2.7 and we just recently updated it to work with Python 3 here (Big kudos to @dnicolson 🙌). However, we didn't release this updated version yet, but will do very soon and will let you know in this issue when that happens 😄.

Sorry for the delay, Kin is now built with Python 3 so we can close the issue 😄


chore: bdd-nh-1585154304 to 0.0.1

chore: Promote bdd-nh-1585154304 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Problem running Karma tests after adding sidebar

This might be my fault when adding sidebar. But the sidebar shows up ok when running the website so it seems to work. The problem is that when running the karma tests I get the error pasted bellow. The problem seems to be that the array _closeDirectives.forEach is undefined for some reason when the test run. I'm new to javavscript and it seems to me like it could be the combination of tools that I use which triggers this issue. But I was thinking that it could be something to look at for stability reasons. I can send you the project that I have to trigger the issue if you are interested.
  Chrome 53.0.2785 (Mac OS X 10.11.6)
Error: Error in /Users/perka124/Documents/dev/Java/StoryTeller/ui/dist/dev/app/app.component.html:0:0 caused by: Cannot read property 'forEach' of undefined
TypeError: Cannot read property 'forEach' of undefined
    at Sidebar.ngOnDestroy (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/ng2-sidebar/lib/sidebar.component.js:58:30)
    at DebugAppView._View_AppComponent0.destroyInternal (AppComponent.ngfactory.js:312:21)
    at DebugAppView.AppView.destroyLocal (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core.umd.js:9402:18)
    at DebugAppView.destroyLocal (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core.umd.js:9565:47)
    at DebugAppView.AppView._destroyRecurse (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core.umd.js:9390:18)
    at DebugAppView.AppView._destroyRecurse (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core.umd.js:9388:29)
    at DebugAppView.AppView._destroyRecurse (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core.umd.js:9388:29)
    at DebugAppView.AppView.destroy (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core.umd.js:9376:18)
    at ComponentRef_.destroy (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core.umd.js:5911:86)
    at ComponentFixture.destroy (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core-testing.umd.js:302:35)
    at eval (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core-testing.umd.js:760:78)
    at Array.forEach (native)
    at TestBed.resetTestingModule (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core-testing.umd.js:760:34)
    at Function.TestBed.resetTestingModule (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core-testing.umd.js:668:26)
    at Object.eval (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/@angular/core/bundles/core-testing.umd.js:994:21)
    at ZoneDelegate.invoke (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/zone.js/dist/zone.js:203:28)
    at ProxyZoneSpec.onInvoke (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/zone.js/dist/proxy.js:72:39)
    at ZoneDelegate.invoke (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/zone.js/dist/zone.js:202:34)
    at Zone.run (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/zone.js/dist/zone.js:96:43)
    at Object.<anonymous> (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/zone.js/dist/jasmine-patch.js:91:50)
    at ZoneQueueRunner.jasmine.QueueRunner.ZoneQueueRunner.execute (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/zone.js/dist/jasmine-patch.js:119:42)
    at ZoneDelegate.invokeTask (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/zone.js/dist/zone.js:236:37)
    at Zone.runTask (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/zone.js/dist/zone.js:136:47)
    at drainMicroTaskQueue (/Users/perka124/Documents/dev/Java/StoryTeller/ui/node_modules/zone.js/dist/zone.js:368:35)
    a

It might be potentially be related to this, but I'll keep looking into it.

Yes, maybe. I'm just thinking that it is strange that the TypeScript array is compiled (or transpiled or what it's called) to a variable with undefined value even if the TypeScript array is empty. I did an ugly hack and added a nullcheck in the js file in my node_modules to be able to continue.

I published v1.6.1 with the null checks, but I'll keep this issue open so that I'll remember to investigate it more.

Thanks! It works.

Thinking back on this, I think it's just because it's how Angular's ContentChildren/Query/QueryList stuff works.


Could not find com.crashlytics.sdk.android:crashlytics:2.5.5

Hello,
I'm on RN=0.32, and I did "rnpm install ..." which seemed to work without a hitch.
Running on Android gives the following error:
FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring project ':app'.
> Could not resolve all dependencies for configuration ':app:_debugCompile'.
   > Could not find com.crashlytics.sdk.android:crashlytics:2.5.5.
     Searched in the following locations:
         file:/usr/local/opt/android-sdk/extras/android/m2repository/com/crashlytics/sdk/android/crashlytics/2.5.5/crashlytics-2.5.5.pom
         file:/usr/local/opt/android-sdk/extras/android/m2repository/com/crashlytics/sdk/android/crashlytics/2.5.5/crashlytics-2.5.5.aar
         file:/usr/local/opt/android-sdk/extras/google/m2repository/com/crashlytics/sdk/android/crashlytics/2.5.5/crashlytics-2.5.5.pom
         file:/usr/local/opt/android-sdk/extras/google/m2repository/com/crashlytics/sdk/android/crashlytics/2.5.5/crashlytics-2.5.5.aar
     Required by:
         Stardust:app:unspecified > Stardust:react-native-fabric:unspecified

Please advise, thanks.

Have you installed Fabric as instructed on the Fabroc website?

Oh, gotcha. I didn't realize that was still necessary, will do.
On Thu, Sep 8, 2016 at 3:49 PM, Cory Smith<EMAIL_ADDRESS>wrote:

Have you installed Fabric as instructed on the Fabroc website?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/corymsmith/react-native-fabric/issues/64#issuecomment-245766005,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAXXZSmRPe5fRCXDclew9o2H0meOnjbIks5qoJDngaJpZM4J3Uw8
.

--
http://www.geoffplitt.com
http://facebook.com/geoffrey.plitt
https://twitter.com/GeoffreyPlitt
773.339.0915

i soved by add repositories {     maven { url 'https://maven.fabric.io/public' } } in app->build.gradle, not in "buildscript".


Fix raster file download problem in Add raster from file

Problem was in #46
See https://github.com/Esri/arcgis-runtime-samples-ios/pull/1036
The problem's behavior is that when the raster file is downloaded for the first time, it would throw a build failure due to the file not found error. In the following builds, the error is gone.
It may be due to the raster file rely on a certain folder structure, and we have to move back to the old raster portal item. See common-samples/issues/3618 for the data change.

Display map from mobile map package may also suffer from this problem.

This could potentially be fixed by #107 , need to test

Try to check the flag instead of the percentage progress here: https://github.com/Esri/arcgis-maps-sdk-swift-samples/blob/main/Shared/Supporting Files/Models/OnDemandResource.swift#L57

This is also an issue with #193. The on-demand image data fails to load the first time the app launches. If the local data isn't cleared, the animated image overlay load correctly the second time the app is launched.

Let's hope the fix in #208 is the root cause.


Calling TagManager::deleteTagging() then TagManager::addTag() re-add deleted tags

Summary
If you use TagManager::deleteTagging() then TagManager::addTag()  addTag() re-add deleted tags because  TagManager::$storage is not cleared .
PR will follow in a few minutes ...
Steps to reproduce
$entity = new Contact();
$oldTagID = 1234
$tag = new Tag();
$tagManager->deleteTagging($entity  , [$oldTagID ]);
$tagManager->addTag($entity , $tag)

Actual Result
OldTag is gone, and `$tag is added
Expected Result
OldTag is still there, with the new $tag
Details about your environment

OroPlatform version: 4.1.9
PHP version: 7.4
Database (MySQL, PostgreSQL) version

Additional information

Hi Samuel,
It's a valid improvement, feel free to create a PR with the fix.


MINOR: Fix javadoc warnings

This commit fixes javadoc warnings caused by missing imports.
Committer Checklist (excluded from commit message)

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation (including upgrade notes)

Call for review: @mjsax @guozhangwang @vvcephei @bbejeck

Ok to test.

Java 11 failed with Caused by: java.lang.OutOfMemoryError: unable to create new native thread

merged #8809 into trunk


Include smart handling of rate limiting when requested

For majority of users, this API will return 429 Too Many Requests once you start to get rate limited. This will last some number of seconds and the limit is generally 50 requests per second.
When creating this Client, with intent to re-use, we should allow you to retry-with-fallback in a standard way that you can configure the delay. For example just wait a second if you get the characteristic error -- 429 Too Many Requests.

Iceboxing this because the interface for substituting out request handling logic in the OpenAPI generator library is pretty obtuse. All class-based and the injectable type is the constructor for an abstract class, so there is very little modifiability.


Missing JSON objects for some components with CUDA major split archives

For example: cuDNN redistrib_<IP_ADDRESS> has both CUDA 11.x and CUDA 12.x tarballs.
The JSON manifest includes references to
"relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda12-archive.tar.xz",

but is missing
"relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda11-archive.tar.xz",

Related to bin-archive v3 format item

Special cases for archive split

NVIDIA driver sub-components
by CUDA Major version (CUDA Minor version compatibility)

I think the cleanest fix is to update the schema ...
For example option A with an array
    "version": "<IP_ADDRESS>",
    "linux-x86_64": [
      {
        "relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda11-archive.tar.xz",
        "sha256": "a6d9887267e28590c9db95ce65cbe96a668df0352338b7d337e0532ded33485c",
        "md5": "56a15f6a9b85b0be2f005a1e3715d506",
        "size": "903887852"
      },
      {
        "relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda12-archive.tar.xz",
        "sha256": "35163c5c542be0c511738b27e25235193cbeedc5e0e006e44b1cdeaf1922e83e",
        "md5": "fe41922f07a13da7b1593639adb0e32c",
        "size": "903519652"
      }
    ],

Or option B with a key
    "version": "<IP_ADDRESS>",
    "linux-x86_64": {
      "cuda11": {
        "relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda11-archive.tar.xz",
        "sha256": "a6d9887267e28590c9db95ce65cbe96a668df0352338b7d337e0532ded33485c",
        "md5": "56a15f6a9b85b0be2f005a1e3715d506",
        "size": "903887852"
      },
      "cuda12": {
        "relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda12-archive.tar.xz",
        "sha256": "35163c5c542be0c511738b27e25235193cbeedc5e0e006e44b1cdeaf1922e83e",
        "md5": "fe41922f07a13da7b1593639adb0e32c",
        "size": "903519652"
      }
    },

Unfortunately updating the schema will break existing scripts, such as the parse_redistrib.py one included in this repo.
Another open question is whether is makes sense to retroactively apply this or only going forward.

Option A, if chosen, definitely needs a discriminator field, e.g.
    "version": "<IP_ADDRESS>",
    "linux-x86_64": [
      {
        "relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda11-archive.tar.xz",
        "cuda": "11",
        ...
      },
      {
        "relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda12-archive.tar.xz",
        "cuda": "12",
        ...
      }
    ],

Otherwise the official interface becomes "parse the URL to infer CUDA version". This applies to strings like "cuda12" to some extent as well
Is there any possibility that cudnn may later impose even more complex constraints?

I have a slight preference over the following approach, by adding an additional top level field cuda_ver (final name TBD) to indicate how many variants one should expect below:
    "version": "<IP_ADDRESS>",
    "cuda_ver": ["11", "12"],  # not sure if minor versions should be allowed here, TBD
    "linux-x86_64": {
      "cuda11": {
        "relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda11-archive.tar.xz",
        ...
      },
      "cuda12": {
        "relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda12-archive.tar.xz",
        ...
      }

then perhaps it is less important to pick between Option A & B. It's easier to parse this IMHO.

I haven't any objections to @leofang's suggestion. As far as nixpkgs is concerned, I think it's equivalent to option B: we have several package set instances, e.g. cudaPackages_11 and cudaPackages_12, which choose a JSON manifest based on the cudatoolkit semver. We already select cudnn releases based on the cudatoolkit minor version, just using some pretty clumsy logic and compatibility tables that are maintained manually (copied over from the cudnn release notes).
With the proposed change I think we'd try to just pick a manifest attribute by name, be that "${cudaMajorVersion}" == "12" or "cuda${cudaMajorVersion}" == "cuda12", likely without looking at "cuda_ver"
Questions about "cuda_ver" I maybe do have is whether the order of the list is significant and, generally, what is the implied contract for the field.
On a related note, @kmittman what range of compatibility guarantees are "cuda11"/"cuda12" keys meant to suggest? The cudnn manual/release notes seem to only make promises about minor versions, not entire major versions. Should the manifests maybe also include explicit compatibility metadata? I'd be happy to delete https://github.com/NixOS/nixpkgs/blob/8f7c43426a2dc5dac9d8aaa4f616c6002ded891d/pkgs/development/libraries/science/math/cudnn/releases.nix if this was an option

Both of you have made really good points, thank you @SomeoneSerge and @leofang very much!
Need some time to ponder about the best option in general for: CMake, Conda, Nixpkgs, Debian, RPM, etc.

Regarding #2 I think I could inject min/max into the template, though TBH an accurate range would be difficult to maintain, each tarball file is tagged with some key-value metadata at creation time, then later parsed to generate the JSON manifests.
As far what that would look like? Here are some proposals

i.   "cuda": { "min": "11.2.0", "max": "11.8.0" },
ii.  "cuda": { "min": "12.0", "max": "12.9999" },
iii. "cuda": { "ge": "12.0.0", "lt": "13" },
iv. "minCudaVersion": "11.0", "maxCudaVersion": "11.8"
v. "cuda_min": "11", "cuda_max": "11"
vi. "depends": { "cuda": "11" },

Combining some of the current suggestions, wondering about something like
{
  "release_date": "2023-05-05",
  "release_label": "8.9.1",
  "cudnn": {
    "name": "NVIDIA CUDA Deep Neural Network library",
    "license": "cudnn",
    "license_path": "cudnn/LICENSE.txt",
    "version": "<IP_ADDRESS>",
    "cuda_ver": [
      "11",
      "12"
    ],
    "linux-x86_64": {
      "11": {
        "cuda_min": "11.2",
        "cuda_max": "11.8",
        "relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda11-archive.tar.xz",
        "sha256": "a6d9887267e28590c9db95ce65cbe96a668df0352338b7d337e0532ded33485c",
        "md5": "56a15f6a9b85b0be2f005a1e3715d506",
        "size": "903887852"
      },
      "12": {
        "cuda_min": "12",
        "cuda_max": "12",
        "relative_path": "cudnn/linux-x86_64/cudnn-linux-x86_64-<IP_ADDRESS>_cuda12-archive.tar.xz",
        "sha256": "35163c5c542be0c511738b27e25235193cbeedc5e0e006e44b1cdeaf1922e83e",
        "md5": "fe41922f07a13da7b1593639adb0e32c",
        "size": "903519652"
      }
    }
  }
}

Just chiming in, I would absolutely love if the manifest included compatible CUDA ranges — saves me from needing to maintain them elsewhere as Serge pointed out.
Is there anything I can do to assist?

Okay, here's what I've got redistrib_1.2.3.json
{
  "release_date": "2023-06-20",
  "release_label": "1.2.3",
  "release_product": "placeholder",
  "libplaceholder": {
    "name": "NVIDIA Placeholder",
    "license": "custom",
    "license_path": "libplaceholder/LICENSE.txt",
    "version": "<IP_ADDRESS>",
    "linux-x86_64": {
      "cuda12": {
        "relative_path": "libplaceholder/linux-x86_64/libplaceholder-linux-x86_64-<IP_ADDRESS>_cuda12-archive.tar.xz",
        "sha256": "e3b0c44298fc1c149afbf4c8996fb92427ae41e4649b934ca495991b7852b855",
        "md5": "d41d8cd98f00b204e9800998ecf8427e",
        "size": "1156992"
      },
      "cuda11": {
        "relative_path": "libplaceholder/linux-x86_64/libplaceholder-linux-x86_64-<IP_ADDRESS>_cuda11-archive.tar.xz",
        "sha256": "01ba4719c80b6fe911b091a7c05124b64eeece964e09c058ef8f9805daca546b",
        "md5": "68b329da9893e34099c7d8ad5cb9c940",
        "size": "1126204"
      }
    },
    "cuda_variant": [
      "12",
      "11"
    ]
  }
}

and non-variant manifest remains mostly intact redistrib_0.1.0.json
{
  "release_date": "2023-06-20",
  "release_label": "0.1.0",
  "release_product": "foobar",
  "libfoobar": {
    "name": "NVIDIA Foo Bar",
    "license": "custom",
    "license_path": "libfoobar/LICENSE.txt",
    "version": "<IP_ADDRESS>",
    "linux-x86_64": {
      "relative_path": "libfoobar/linux-x86_64/libfoobar-linux-x86_64-<IP_ADDRESS>-archive.tar.xz",
      "sha256": "36a9e7f1c95b82ffb99743e0c5c4ce95d83c9a430aac59f84ef3cbfab6145068",
      "md5": "7215ee9c7d9dc229d2921a40e899ec5f",
      "size": "1743028"
    }
  }
}

This has been implemented for awhile for a few releases of cuDNN and cuQuantum.
Also I went back to the old releases and uploaded fixed manifests (new filenames).
Closing.


Touchscreen interface and driver

In implementing support for the touchscreen on the MPS2 board I needed an interface to write the driver to, so I first came up with a simple generic touchscreen API. I don't know if this is suitable or if I should have just made this device specific. Likewise the functions for translating touchscreen values to screen coordinates are generically useful, so I made them so.

On Mon, 2017-05-08 at 08:23 -0700, Paul Sokolovsky wrote:

		 const struct touchscreen_point display[3],

		 const struct touchscreen_point touchscreen[3]);

+/**

@brief Translate touchscreen coordinates into screen coordinates.

Convert a touchscreen X,Y sample into the corresponding display X,Y

coordinates by using the previously initialised translation parameters.

@param xlat		Translation parameters.

@param dislpay_x	Display X coordinate

@param dislpay_x	Display Y coordinate

@param touch_x	Touchscreen X sample

@param touch_y	Touchscreen Y sample

*/
+void touchscreen_translate(struct touchscreen_xlat *xlat,

And here the order of arguments is: input, output, output, input, input. Is this natural and gives a user the least surprise?

I don't know, it seemed natural to me. Guess in my head, the first
parameter is the 'this' pointer if it was C++, i.e. it's the object
being initialise by touchscreen_set_calibration() and the state used by
touchscreen_translate().


fix machine users UIDs across Galaxy VMs

Make UIDs for machine users constant across Galaxy VMs. Loosely divided UIDs into a few ranges for easier management of UID numbers when adding and removing users: infrastructure team, support team, tools team, other.

Cool!  The machine_users dict is repeated in group_vars/dev.yml as a quick-fix for giving mike and tom sudo privileges on dev machines.  So to make this work on dev the IDs would need to be copied into that file too.

requested changes made

added code to remove old machine_user accounts - defined in group_vars/{all.yml,dev.yml}


what is the role of MAX_NUM_BOXES？

Thanks for your work, I would like to know what is the role of MAX_NUM_BOXES, is it because the RoIs may have overlap, causing a point to fall into different RoI?

Yes, that's correct! In the original points_in_boxes_gpu, each point is assigned a single box id. We modify the code to allow for each point to be assigned to up to MAX_NUM_BOXES boxes for accurate point density estimation.


Corrected the FILESEXTRAPATHS_prepend for edge-core imx8 and uz target

This shouldnt be working but it is. Fixing it before our luck runs out.
This fixes PELEDGE19-4335

https://github.com/PelionIoT/meta-mbed-edge/blob/dev/recipes-connectivity/mbed-edge-core/mbed-edge-core-rpi3.bb#L18 seems to be OK already.


Draft Default Email Content after Access is Granted on FAM

Describe the task
Draft a default email message content for notification once access is granted on FAM
Scope should limited to a generic response where personal information should not be included.
Acceptance Criteria

[ ]email content to be provided for implementation of FAM notification.
[ ] See example:

[ ] third

Additional context

Add any other context about the task here.
Or here

Looks good, only recommendation is to change the email signature to the PO/Application Administrator name.

suggestion to update the message to this:
This is an automated email, please do not reply
Dear Olga Liberchuk,
You have been granted access to Seed Planning and Registry Application (SPAR). Click here to login.
Please contact your administrator if you have any issues accessing the application.
Regards,
The Fingerprint Team
FSA Modernization Project


errors while attemptin to install azure cli via "az aks install-cli"

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks install-cli
Errors:
No module named '_cffi_backend'
Traceback (most recent call last):
python3.6/site-packages/knack/cli.py, ln 233, in invoke
    cmd_result = self.invocation.execute(args)
cli/core/commands/__init__.py, ln 559, in execute
    self.commands_loader.load_arguments(command)
azure/cli/core/__init__.py, ln 502, in load_arguments
    self.command_table[command].load_arguments()  # this loads the arguments via reflection
cli/core/commands/__init__.py, ln 316, in load_arguments
    super(AzCliCommand, self).load_arguments()
...
python3.6/site-packages/paramiko/transport.py, ln 90, in <module>
    from paramiko.ed25519key import Ed25519Key
python3.6/site-packages/paramiko/ed25519key.py, ln 17, in <module>
    import bcrypt
python3.6/site-packages/bcrypt/__init__.py, ln 25, in <module>
    from . import _bcrypt
ModuleNotFoundError: No module named '_cffi_backend'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks install-cli

Expected Behavior
Environment Summary
Linux-5.10.22-100.fc32.x86_64-x86_64-with-glibc2.2.5
Python 3.8.7
Installer: RPM

azure-cli 2.20.0

Additional Context

route to appropriate team

Azure CLI's RPM package doesn't work correctly with Python 3.8.7. Please see https://github.com/Azure/azure-cli/issues/18159#issuecomment-888120344 for detailed explanation and workaround.


Update packagist for 3.4.3

Last stable release available in Packagist is 3.4.2, which contains a bug using Math.div in a wrong place and this prevents compiling any project. 3.4.1 uses older math methods and keeps flooding the console with Sass warnings

is there any solution about this issue? When my version was 3.4.1, I was getting this error. I updated the version 3.4.3 and I continue to get the same error.
SassError: Invalid CSS after "...     floor(math": expected expression (e.g. 1px, bold), was ".div($grid-gutter-w"
on line 369 of node_modules/bootstrap-sass/assets/stylesheets/bootstrap/_variables.scss
from line 20 of<EMAIL_ADDRESS>from line 8 of<EMAIL_ADDRESS>from line 8 of<EMAIL_ADDRESS> @AprilArcus

it looks like you might be using an older version of sass. Can you share more of your error?

I think so. I am sharing the log details.
ModuleBuildError: Module build failed .../node_modules/sass-loader/dist/cjs.js):
SassError: Invalid CSS after "...     floor(math": expected expression (e.g. 1px, bold), was ".div($grid-gutter-w"
on line 369 of node_modules/bootstrap-sass/assets/stylesheets/bootstrap/_variables.scss
from line 20 of<EMAIL_ADDRESS>from line 8 of<EMAIL_ADDRESS>from line 20 of ...\src\styles.scss

vbar-padding-horizontal:        floor(math.div($grid-gutter-width, 2)) !defa
------------------------------------------^

at...node_modules\webpack\lib\NormalModule.js:316:20
at ...\node_modules\loader-runner\lib\LoaderRunner.js:367:11
at ...\node_modules\loader-runner\lib\LoaderRunner.js:233:18
at ...\node_modules\loader-runner\lib\LoaderRunner.js:111:13)
at ...\node_modules\sass-loader\dist\index.js:73:7)
at ...\node_modules\neo-async\async.js:8069:18)
at options.error (...\node-sass\lib\index.js:294:32)

Yes, you're using node-sass, where you meed to be using dart-sass for this and future versions. Can you please share the version of sass-loader you're using, and the part of your webpack config where you set up sass-loader?

I am sharing ;
"7.1.0": {
    "name": "sass-loader",
    "description": "Sass loader for webpack",
    "version": "7.1.0",
    "author": {
        "name": "J. Tangelder"
    },
    "homepage": "https://github.com/webpack-contrib/sass-loader",
    "repository": {
        "type": "git",
        "url": "git+https://github.com/webpack-contrib/sass-loader.git"
    },
    "bugs": {
        "url": "https://github.com/webpack-contrib/sass-loader/issues"
    },
    "engines": {
        "node": ">= 6.9.0 || >= 8.9.0"
    },
    "main": "lib/loader.js",
    "dependencies": {
        "clone-deep": "^2.0.1",
        "loader-utils": "^1.0.1",
        "lodash.tail": "^4.1.1",
        "neo-async": "^2.5.0",
        "pify": "^3.0.0",
        "semver": "^5.5.0"
    },
    "devDependencies": {
        "bootstrap-sass": "^3.3.5",
        "css-loader": "^0.28.4",
        "eslint": "^3.16.0",
        "eslint-config-peerigon": "^9.0.0",
        "eslint-plugin-jsdoc": "^2.4.0",
        "file-loader": "^0.11.2",
        "mocha": "^3.0.2",
        "mock-require": "^3.0.1",
        "node-sass": "^4.5.0",
        "nyc": "^11.0.2",
        "raw-loader": "^0.5.1",
        "sass": "^1.3.0",
        "should": "^11.2.0",
        "standard-version": "^4.2.0",
        "style-loader": "^0.18.2",
        "webpack": "^4.5.0",
        "webpack-dev-server": "^2.4.1",
        "webpack-merge": "^4.0.0"
    },
    "peerDependencies": {
        "webpack": "^3.0.0 || ^4.0.0"
    },
    "keywords": [

        "maintainers": [
            ...
        ],
        "directories": {},
        ...
        "_npmVersion": "5.6.0",
        "_id"<EMAIL_ADDRESS>        "dist": {},

        "_nodeVersion": `"8.11.3"`

Can't the problem be solved without updating the version? Normally, we were not getting any errors while our application was being built 1 month ago.

You need to update your "sass" pin to 1.33.

Should this be reverted and make major version change? There are quite a few tools out there that can't update their sass easily

Thank you so much  for detail explanation. @AprilArcus

o


Ambiguous "A user that authenticates multiple times within a given month is counted as one MAU"

This is ambiguous "A user that authenticates multiple times within a given month is counted as one MAU".
What if they authenticate just once in the month? Is that a MAU?
If it is, it should say "A user that authenticates at least once within a given month is counted as one MAU"

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

ID: 10c6698d-da67-a802-3f77-ae8091ea4782
Version Independent ID: b5397a88-c4df-26d2-e9d2-29491d76ea00
Content: Billing model for Azure Active Directory B2C
Content Source: articles/active-directory-b2c/billing.md
Service: active-directory
Sub-service: b2c
GitHub Login: @kengaderdus
Microsoft Alias: kengaderdus

@dombat
Thanks for your feedback! We will investigate and update as appropriate.

@dombat
Thanks for reporting this! We have created a PR for this issue and the changes should go live soon.


archive.json with evcurve workflow upload upload

I can upload an archive.json to the nomad archive. this archive contains an evcurve workflow. the parsing fails with this error:
"root":{
"errors":string"normalizer failed with exception"
"event":string"process failed"
"proc":string"Entry"
"process":string"process_entry"
"process_worker_id":string"GAnRUuJjTBmrzo9f1onk3g"
"parser":string"parsers/archive"
"error":string"ufunc 'multiply' did not contain a loop with signature matching types (dtype('<U11'), dtype('int64')) -> None"
"normalizer":string"ResultsNormalizer"
"step":string"ResultsNormalizer"
"logger":string"nomad.processing"
"exception":string"Traceback (most recent call last): File "/app/nomad/processing/data.py", line 1072, in normalizing normalizer(self._parser_results).normalize(logger=logger) File "/app/nomad/normalizing/results.py", line 100, in normalize self.normalize_run(logger=self.logger) File "/app/nomad/normalizing/results.py", line 196, in normalize_run properties, conv_atoms, wyckoff_sets, spg_number = self.properties(repr_system, repr_symmetry) File "/app/nomad/normalizing/results.py", line 483, in properties energy_volume_curves = self.energy_volume_curves() File "/app/nomad/normalizing/results.py", line 758, in energy_volume_curves volumes = equation_of_state.volumes File "/app/nomad/metainfo/metainfo.py", line 2504, in get value = value * self.unit File "/usr/local/lib/python3.7/site-packages/pint/unit.py", line 291, in array_ufunc **kwargs, File "/usr/local/lib/python3.7/site-packages/pint/quantity.py", line 1655, in array_ufunc return numpy_wrap("ufunc", ufunc, inputs, kwargs, types) File "/usr/local/lib/python3.7/site-packages/pint/numpy_func.py", line 921, in numpy_wrap return handled[name](*args, **kwargs) File "/usr/local/lib/python3.7/site-packages/pint/numpy_func.py", line 303, in implementation result_magnitude = func(*stripped_args, **stripped_kwargs) numpy.core._exceptions._UFuncNoLoopError: ufunc 'multiply' did not contain a loop with signature matching types (dtype('<U11'), dtype('int64')) -> None"
"timestamp":string"2023-02-12 10:24.33"
"level":string"ERROR"
}
Traceback (most recent call last):
File "/app/nomad/processing/data.py", line 1072, in normalizing
normalizer(self._parser_results).normalize(logger=logger)
File "/app/nomad/normalizing/results.py", line 100, in normalize
self.normalize_run(logger=self.logger)
File "/app/nomad/normalizing/results.py", line 196, in normalize_run
properties, conv_atoms, wyckoff_sets, spg_number = self.properties(repr_system, repr_symmetry)
File "/app/nomad/normalizing/results.py", line 483, in properties
energy_volume_curves = self.energy_volume_curves()
File "/app/nomad/normalizing/results.py", line 758, in energy_volume_curves
volumes = equation_of_state.volumes
File "/app/nomad/metainfo/metainfo.py", line 2504, in get
value = value * self.unit
File "/usr/local/lib/python3.7/site-packages/pint/unit.py", line 291, in array_ufunc
**kwargs,
File "/usr/local/lib/python3.7/site-packages/pint/quantity.py", line 1655, in array_ufunc
return numpy_wrap("ufunc", ufunc, inputs, kwargs, types)
File "/usr/local/lib/python3.7/site-packages/pint/numpy_func.py", line 921, in numpy_wrap
return handled[name](*args, **kwargs)
File "/usr/local/lib/python3.7/site-packages/pint/numpy_func.py", line 303, in implementation
result_magnitude = func(*stripped_args, **stripped_kwargs)
numpy.core._exceptions._UFuncNoLoopError: ufunc 'multiply' did not contain a loop with signature matching types (dtype('<U11'), dtype('int64')) -> None
however, I am also running  a docker image with the develop branch, where the archive shows correctly except for the structure_name property.

I tried to parse the archive and it seems to work with no errors. Also the structure info are there.

It results in Failure to me. can you check with the upload ID ?

same error

It results in Failure to me. can you check with the upload ID ?

can you send the upload_id?

the upload fails in https://nomad-lab.eu/prod/v1/gui/user/uploads/upload/id/OeXWjVsMQ4ONwh9uskV5CQ
but it is succsesfull in https://nomad-lab.eu/prod/v1/staging/gui/user/uploads/upload/id/OeXWjVsMQ4ONwh9uskV5CQ.
However, results.material.symmetry.structure_name shows fine in /prod/v1/gui  but not in /prod/v1/staging/gui.

yes it is the staging that contains the newer implementations.

ok, sorry for the misunderstanding

Can this be closed?

yes, I think so.


Add trigger list to advanced filters

aim
Add a 'filter by trigger list' checkbox to the advanced filters on the queue search page. The filter should only return cases that are on the TRIGGER_LIST for nsg_list_type
before

after

waiting on #1017 to be merged on the frontend, and backend work in API

thanks @currycoder @kevincarrogan @depsiatwal ✌ 🚀


Color contrast on side-bar chevrons is too low

Steps to recreate
Install and run an audit using aXe browser extension.
The chevrons in the side-bar have a contrast of 2.49: 1 which is a ratio that doesn't meet AA or AAA WCAG standard.

Good find @dakahn
Gray 70 #565656 is dark enough for a 7.34:1 ratio
It definitely helps the thin chevron stand out a little more


upgrade redis image to version 6.0.9

Reference:
https://hub.docker.com/_/redis

Thanks, but these are test images and there is no point in updating them, as long as they are available.


Prov-Document: Validation

Only validated documents should be saved into the database. We need a mechanism to validate ProvDocument classes (or directly JSON / PROV-N / XML streams?)

I didn't found source code for the ProvValidator.
But some useful resources, which could help to implement a python version.
http://www.orchid.ac.uk/eprints/180/1/validator.pdf
https://dvcs.w3.org/hg/prov/raw-file/default/testcases/process.html
https://github.com/pgroth/prov-check


initial controller-bootstrap empty controller

Signed-off-by: Jay Pipes<EMAIL_ADDRESS>aws-controllers-k8s/community#482
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm

/approve


[/usr/share/dotnet/host/fxr] path not found

Problem encountered on https://dotnet.microsoft.com/en-us/learn/aspnet/hello-world-tutorial/create
Operating System: linux
Provide details about the problem you're experiencing. Include your operating system version, exact error message, code sample, and anything else that is relevant.

please help me with an idea on the issue

What distribution are you using? https://learn.microsoft.com/en-us/dotnet/core/install/linux-package-mixup might have the steps to fix your issue.

Also, how did you install?


[Feature Request]: Add category for feedback

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
In the contact form, adding a dropdown will ease the effort of the users.

When the user clicks on other, the user will be asked to type in the subject.

Use Case
easy for feedback segregation
Benefits
No response
Add ScreenShots
No response
Priority
Medium
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC'24 contributor
[X] I have starred the repository

the contact form is just a dummy form so I don't think this is needed


TPC-DS 99 statement test progress

TPC-DS tests are widely used，are you have the test？if you have the test，whether open it on github？people can refer it.
and which features are not support current？and the next plan？

starrocks supports all TPC-DS SQL, and we are working on some performance optimizations and will open the details later


webpack sourcemaps do not work well with ES6 imports

Do you want to request a feature or report a bug?
Report a bug.
What is the current behavior?
Sourcemaps do not work for ES6 imports
Example: import foo from '../src/fooProvider' will be visible as __WEBPACK_IMPORTED_MODULE_0__src__fooProvider__.a
Using require and module.exports will correctly make foo available in the debugger scope.
If the current behavior is a bug, please provide the steps to reproduce.

Clone minimal project: https://git-r3lab.uni.lu/sascha.herzinger/debugger-bug.git
npm install
run karma to see if everything works
run karma with breakpoint in test/foo-test.js line 6
See messed up scope as shown here:

What is the expected behavior?
being able to inspect foo instead of __WEBPACK_IMPORTED_MODULE_0__src__fooProvider__.a
when using ES6 imports.
I want to see this, but with ES6 imports:

Please mention other relevant information such as the browser version, Node.js version, webpack version and Operating System.
Chrome 56,
node 7.7.1,
webpack (s. package.json)
Webstorm 2017.1
macOS 10.12.3

Yeah, sourcemap doesn't seem to hide stacktrace:

Also you have to do multiple steps for one line, since it uses lookup search for each imported function.

@Vanuan using named imports makes it even worse for me:

Also, do you know if this issue is related to the incorrect line numbers mappings?
A test with 10 LOC, designed to fail, shows me this:

@sherzinger No, this is related to disabling babel ES6 module transform ({modules:false}).
I.e. webpack adds __WEBPACK_IMPORTED_MODULE_... to global namespace but doesn't add corresponding local variables.

@Vanuan I also thought it was babel at first, but if you check my sample project I completely removed babel from it and still get this behaviour.

@sherzinger I'm saying that if you'd use babel for module tranformation the problem would gone

I'm running into this as well. I'd like to avoid adding Babel because it adds 30 seconds to my build.

Same issue with Webpack 3.x. Is this fixed in 4.x or at least going to be fixed?

@the-spyke need test, can you tests this with webpack@4?

I did, it's still not fixed...

@Vanuan As I understand, transforming imports with Babel not just makes your build slower, it removes all useful features that ES Modules give (static checks, tree shaking, concatenation, etc.).

I'm interested in working on this and willing to commit time to it, I'd love if I could get some pointers on where I could get started solving this.
@sokra @bebraw
@sherzinger I wasn't able to open the minimal reproduction case, could you make sure it's public?

@morsdyce thank you for doing this!
I'm afraid the repo fell victim to a cleanup I did some time ago. I'll see if I find some backups or re-create it otherwise.

Here you go: https://github.com/sherzinger/webpack-issue-4560
Unlike the example in the first post this code does not use karma/jasmine to include the bundle.
Instead you run npm run devServer and open foo.html, so you can use your browser dev tools.
I thought that might be a bit more light weight.

Awesome, thanks!

Any update?

Not yet, got caught up with a few things on the way. Still researching some approaches to handle this.

I'm a little bewildered as to why there is such little activity on this issue. Sourcemaps should work. I can only think of a few explanations:

In general people don't use the debugger as much as I do.
People have discovered a workaround that I don't know about :)
There is another issue that describes the same behavior that is more active.

Anyone know which of the above is true, if any? Thanks!

@abirmingham
4. People have lost hope.

Still not working :(

If somebody still have problem please open new issue with reproducible test repo, thanks

New issue created: #9461

@sherzinger I'm saying that if you'd use babel for module tranformation the problem would gone

I'm using babel in my project but not sure how to do this. Can someone please show me how exactly to use babel for module transformation?
This is how my .babelrc looks like
{
  "presets": ["@babel/env", "@babel/react", "@babel/typescript"]
}

and I'm using babel-loader in my webpack configuration file


LinkFix: azure-docs-cli (2022-10)

This PR is the result of running a Link Repair script on the included content. This script is primarily being run to clean up links to function correctly in Air Gapped Clouds (AGC). Here's a breakdown of what the script that generated the changes in this PR fixes:

docs.microsoft.com Fully Qualified Domain Name (FQDN) Links to either Relative (if in same Repo/DocSet/ContentSet) and Site Relative if not

azure.microsoft.com/documentation/articles that reflect to Docs to either Relative (if in same Repo/DocSet/ContentSet) and Site Relative if not

All known flavors of MSDN/TechNet domains (we know of 8 or 9 now) that reflect to Docs to either Relative (if in same Repo/DocSet/ContentSet) and Site Relative if not

This also includes cleanup of the appended query string for MSDN (redirectedfrom=MSDN).

Fixes articles that are redirected in .openpublishing.redirection.json and updates the link to the current final location (this has a lot of customer usability fixes).

Please note the Contributor Guide: Links has been updated with the following link-type preference order:

By order of preference, links hosted on Docs should be Relative if they are in the same repository and docset. If they are in a different docset, even if in the same repository, they should be Site Relative. Links to content hosted on Docs shouldn't use a complete URL, otherwise known as Fully Qualified Domain Names (FQDN). Using a complete URL from Docs to other content on Docs will cause that link to be non-functional in air-gap environments.

#sign-off

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

File
Status
Preview URL
Details

:x:Error

Details

[Error: GitBranchDeletedOrForcePushed]

Cannot sync git repo to specified commit because ref +refs/pull/3352/merge has been deleted or has been force pushed.
 If this is pull request, please ensure it is mergeable (no merge conflict) and open (not closed).

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


no-inferrable-types can recommend uncompilable code

Bug Report

TSLint version: 4.4.2
TypeScript version: 2.1
Running TSLint via: CLI

Details on the problem in https://github.com/Microsoft/TypeScript/issues/14416
TypeScript code being linted
export class Hello {
    readonly foo: boolean = false;
    constructor(foo: boolean|undefined) {
        this.foo = foo || this.foo;
    }
}

with tslint.json configuration:
{
  "rules": {
    "no-inferrable-types": true
  }}

Actual behavior
tslint error: Type boolean trivially inferred from a boolean literal, remove type annotation. But this would cause a compile error.
Expected behavior
There should be no error, since the annotation is required in this case.

@ajafff FYI