XLA int8 convolution

1 Allow int8 for cudnnConvolutionForward and cudnnConvolutionBiasActi…
1.1 Add cast instruction to convert int8 bias to float in cudnn_fused_conv_rewriter.
1.2 Add a new transform cudnn_pad_for_integer_convolution to pad input and output
feature maps to multiple of 4 and pad weights, bias, and side inputs accordingly
2 Add sanity checks for configurations according to cudnn document.
2.1 Input/output feature maps must be multiple of 4.
2.2 Only _IMPLICIT_PRECOMP_GEMM is supported.
2.3 All tensor layouts must be NHWC.
3 Set convolution layout constraints to NHWC for integer convolution.
4 Remove checks for same types in convolution shape inference to allow mixing int8.
acitvation with float bias.
5 Refactor cudnn_pad_for_tensor_cores to share code with cudnn_pad_for_integer_convolution.
5.1 Create a pimpl class CudnnConvPadFeatures to host most common code.
5.2 Define callbacks to resolve desired tensor shapes and use CudnnConvPadFeatures in
cudnn_pad_for_tensor_cores.cc and cudnn_pad_for_integer_convolution.cc.
6 Tests
6.1 Add one unit test to cudnn_conv_rewriter_test.cc for integer forward convolution cudnn API replacement.
6.2 Add unit tests for the newly added CudnnPadForIntegerConvolutions.
6.3 Modify tests in cudnn_fused_conv_rewriter_test.cc.
6.3.1 Add S8 to the type list for testing.
6.3.2 Allow integer value scales for S8 tests.
6.3.3 Skip numerical verification for S8 cases till the int8 HLO evaluator visitor has proper semantics.

@timshen91 @jlebar  I have updated the PR with new commits, implementing the in8-to-float convolution semantics and addressing comments from Tim.  Please let me know your new comments.

@timshen91 Hi Tim, I saw Justin dismissed the review a week ago.  Will you be able to review it?  It's been open for a long time.  Thank you.

Sorry for the excessive delay on review. I was distracted last month, and mostly out this month.
First off, thanks for the growing amount of work done here. I have some minor comments, but I haven't done reviewing. The PR is on the right track.
Also, in general we prefer small PRs that are potentially dependent. This PR looks likely to be divided into multiple PRs:

stream_executor change
evaluator change
convolution runner change
pattern matcher change and other changes.

Can you split it if it's relatively easy to do?

Sorry for the excessive delay on review. I was distracted last month, and mostly out this month.
First off, thanks for the growing amount of work done here. I have some minor comments, but I haven't done reviewing. The PR is on the right track.
Also, in general we prefer small PRs that are potentially dependent. This PR looks likely to be divided into multiple PRs:

stream_executor change
evaluator change
convolution runner change
pattern matcher change and other changes.

Can you split it if it's relatively easy to do?

@timshen91 Thank you for the response.  I will try splitting the commit and merging changes with the HEAD in new PRs.  I may have to defer most tests till the last commit.  Meanwhile, please let me know your comments on the current changes.

@timshen91 I have created 4 PRs to replace this one: https://github.com/tensorflow/tensorflow/pull/30761,
https://github.com/tensorflow/tensorflow/pull/30762, https://github.com/tensorflow/tensorflow/pull/30771, and https://github.com/tensorflow/tensorflow/pull/30783.
Most of your comments have been addressed, except one about passing StreamExecutor* to CudnnPadForConvolutions.  Please let me know if you have further comments.  I will close this one, once we both move on to the new PRs.

Can one of the admins verify this patch?

Close this PR, as we have moved the necessary changes to https://github.com/tensorflow/tensorflow/pull/30762, https://github.com/tensorflow/tensorflow/pull/30771, and https://github.com/tensorflow/tensorflow/pull/30783.


Maximum apocalypse v9

Add checkbox for special ability & gear textareas to toggle height between 1 & 6

Character Sheet Info Roll20 Internal Use only.


WIKI URL redirect to a broken page

Problem description
Clicking on the project's WIKI link takes you to a broken page.
Expected action
The correct and real content with metadata, etc.

Hello @pedroarthuralvesdeoliveira
We do not use the wiki page for now in CAMARA working group. Probably better to remove this tab.

Links has been updated (thanks @hdamker)

I suppose with the correction done we can close the issue.


Fix spacing on call list

The call list is very cramped and difficult to read. It needs margins between each column, and some massaging of column widths. Work directly with me to fix this.

@mebates are you working on this?  If not I'd like to take it!

@AlexandraCasser - please do! I'm the designer so I can consult with you as you develop.

Just a thought, @Mebates, but could the "remove" just be a 🚫 or something
similar with a hover over text "Remove from call list"? Might give us a
spare few pixels.
On Fri, Jan 13, 2017 at 11:33 AM, Alexandra Casser<EMAIL_ADDRESS>
wrote:

@mebates https://github.com/mebates Sorry I never got back to you about
this--I'm starting work on it now!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/colinxfleming/dcaf_case_management/issues/781#issuecomment-272482665,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKFqsLpiAXGQ1yJjGK8KtnkV4btjFr71ks5rR6dsgaJpZM4LKyGL
.

@lwaldsc I think that's a really good idea.
@mebates How does this look to you?  I added some more padding to the table cells and thought we could fill in every other column to make it easier to differentiate.

Thanks @AlexandraCasser !

I think the filled columns distract from the rows; if anything I would fill in by row
If you abbreviate "Appointment Date" to "Appt Date" you'll have more space in that column.
Phone should definitely stay on one line; that is a fixed width
LMP also feels like it should be on one line too
Notes column can get narrower so other things can fit on one line
Don't mind if name is two lines
'Remove' can be an X in a circle in red instead of the word "Remove"; that will give you more space too. Would be great if on hover it said "Remove from call list"

[ ] I think the filled columns distract from the rows; if anything I would fill in by row
[ ] If you abbreviate "Appointment Date" to "Appt Date" you'll have more space in that column.
[ ] Phone should definitely stay on one line; that is a fixed width
[ ] LMP also feels like it should be on one line too
[ ] Notes column can get narrower so other things can fit on one line
[ ] Don't mind if name is two lines
[ ] 'Remove' can be an X in a circle in red instead of the word "Remove"; that will give you more space too. Would be great if on hover it said "Remove from call list"

Fixed by #827


Add icon set for IoT

should be a common icon set that  gets used so that iot things become easy to identify

Maybe just start with the ionic icons freebie set, and upgrade to something later.

I will add ioncic.  But the icons that come with the numorphic lib are fine.


support meta restarting and sql scheduling for cq service

Is your feature request related to a problem? Please describe.（如果该特性或者功能和已知某个问题相关，请描述问题是什么）
Get the numbers of cq tasks through the heartbeat of sql->meta. Set up a goroutine for each cq task, the default max processs cq number is 5. If a cq task is stopped, mark it as tombstone and meta will reassign the remaining cq tasks.
Describe the solution you'd like（问题的解决办法是什么）

Meta restart:

Through the heartbeat of sql->meta, we know how many SQLs there are and their IDs.

SQL Stopped:

If Meta cannot detect a certain CQ for more than X cycles, the CQ task will be recycled.
Meta assigns these tasks to other SQL
The ID of this SQL is also deleted from Meta, or marked as a tombstone.

SQL Restart:

SQL ID：If the SQL ID is stored in the Meta memory, it will be returned directly.
CQ Tasks: Communicate with meta and let meta assign tasks.

Describe alternatives you've considered（描述您考虑过的替代方案）
No alternatives.
Additional context（其他补充内容）
No response

I will support it.


Fixes #39 : Document deployment procedure for membrane backend

Issue was called deployment.md but file name changed to MANUAL_GCP_DEPLOYMENT.md

You're not replying to my previous review comments @redat97 . At least with "done" so I can know to expect what to look for.
Also, tacking on the github workflow to the PR for manual documentation is wrong. Put that on a separate PR. Comment on github workflow: where's the lint and test step?


[Suggestion] Dynamic Fog

This should be a toggle (you should be able to enable it with any fog type available). Enabling this lets the fog dynamically densen or lessen depending at the time of day. So for example at 0 there is lots of fog while there is almost no fog at 6000. This should also be configurable.

I would like to add on to this, having more fog during rain and snow, but less fog during clear weather.


attr returning nil

Thank you for this wonderful gem!  I was hoping you could help me figure out this little problem I'm having.  I'm probably just not understanding something or doing it wrong!
Problem
Using attr seems to block getting actual value.
class Community < Flexirest::Base
  extend ActiveModel::Naming
  include ActiveModel::Conversion
  include ActiveModel::Validations

  attr :id

  get :find, '/communities', fake: ->(req) { req.prepare_params; [{id: req.get_params[:id]}] }
end

(My) Expected Result
I expected to be able to access the attr id.
>> Community.find(1).first
=> #<Community id: 1>
>> Community.find(1).first.id
=> 1

Actual Result
Instead, I get nil returned.
>> Community.find(1).first
=> #<Community id: 1>
>> Community.find(1).first.id
=> nil

Why do you have attr in there at all? It's not needed, the gem will automatically respond to any attributes assigned to (either if you manually create an object or after an api response). Let me know what you're trying to do and I'll help more if I can.

Thank you for your time :smile:
I hope this conveys my situation:

The backend API is in heavy development
As such, the actual names of attributes in the response are fluid (unfortunate, I know; but, that is the situation)
When I do Community.new, there are no attributes, which causes an empty form with form_for
In order to provide attributes, my first thought was to use attr

Is there a better way to accomplish this?

the gem will automatically respond to any attributes assigned to (either if you manually create an object or after an api response)

Missed that...  The API is not really fake-able at this point; so, I'm ignoring it.  I want to pretend that the attributes are there in order to create forms, using Community.new and form_for.

So you can either pass default attributes in to .new or. Create a temporary initialiser that assigns them to the @_attributes hash. I'm at a conference at the moment but can reply with code samples later today.

OK, I'm back at home now, so can code up the two suggestions to demonstrate the solutions.  The first one is just to pass in default attributes when creating the object:
class MyController < ApplicationController
  def new
    @community = Community.new(id: nil)
  end
end

The alternative is to define an initializer on Community so all new instances automatically get the correct set of attributes ready for use in form_for:
class Community < Flexirest::Base
  # Mapping methods

  def initialize(fields)
    super {id: nil}.merge(fields)
  end
end

D'oh! /facepalm
I don't know why I was so locked on to attr; but, initialize is exactly what I want.  This completely solves my problem.  Thank you very much for taking the time to help.
Going back to the title of this issue, though, is this the expected behaviour if there were to be an attr?

Yes, I would expect that behaviour. The reason is that Flexirest works by using method_missing to look up the attributes from its internal @attributes hash. If you use attr, that defines methods to store and retrieve values in the specific @id instance variable which none of the rest of Flexirest is expecting (it's expecting them to be in @attributes). So, yes it's expected (and would be a considerable rewrite to work around).
I'll close this issue now that I know your problem is solved. You're welcome for the help.


Update docs and comments to Java 8 as minimum

Since GitHub Actions tests against Java 8 as minimum, the code and docs should also require Java 8 as a minimum version

Thanks, @bennetelli !


JSON tags

Hello, bro. Awesome work that you did here. This is just what I was looking for.
I have a suggestion for you, when working with DDD the entities that we define have to be free of any implementation detail. So, if we have something like:
internal/core/models/entity.go
type Entity struct {
    ID string `json:"id"`
    Name string `gorm:"name"`
}

We are coupling our entities to GORM and JSON details.
I think that this lib should have a rule to that. Something as:
version: 3

components:
  consts:           { in: internal/core/consts/** }
  models:           { in: internal/core/models/** }
  ports:            { in: internal/core/ports/** }
  drivers:          { in: internal/adapters/drivers/** }
  drivens:          { in: internal/adapters/drivens/** }
  implementations:  { in: internal/kycservices } # customizable to each case
  api:              { in: cmd/api/** }

vendors:
  uuid: { in: github.com/google/uuid  }
  chi:
    in:
      - github.com/go-chi/chi/v5
      - github.com/go-chi/chi/v5/middleware

tags: # <<< ADD HERE <<<<<<<<<
  - json
  - gorm

commonComponents:
  - consts
  - models

deps:
  models:
    mayDependOn:
      - consts

  ports:
    mayDependOn:
      - consts

  drivers:
    mayDependOn:
      - ports
      - drivens
      - implementations
    mayUseTags: # <<<< ADD HERE <<<<<<<<<
      - json

  drivens:
    mayDependOn:
      - ports
    canUse:
      - uuid
    mayUseTags: # <<<< ADD HERE <<<<<<<<<
      - gorm

  implementations:
    mayDependOn:
      - ports
      - drivers
      - drivens

  api:
    mayDependOn:
      - ports
      - implementations
      - drivers
      - drivens
    canUse:
      - chi

Hi, good idea.
I think we can disable this feature by default, and user can enable it if they want to (like vendor imports checking).
Raw config contract:
allow:
  - useAnyTags: false # default is true. User should explicitly turn off this, for checking tags.

commonTags: # this tags will be always allowed for all structs
 - json
 - yaml

# all other tags is disallowed, and we need explicitly allow them
deps:
  repositories:
    mayUseTags:
      - db     # allow db for this layer
      - gorm   # allow orm staff

I will implement this in v4 if nobody makes it before.


Document local tools

We have documentation for global tool installation, which also covers tool-path tools. We need to add documentation for local tools and change some titles and look at the tools story.

Meeting with PU on Monday which pushes this to Aug sprint

Here is the "raw" document https://github.com/dotnet/cli/issues/10288

Closing this, as the issues directly related to local tools are done. Two related issues are outstanding:

#16895 (add CLI to dependencies article) will be closed by #17245
#16901 (salvage useful parts of extensibility article) will be addressed when #gewarren adds the content identified as still useful to Customize the build


No space password with regex

Added regex to know if the user has any spaces in their password.If they do they will be met with the validation message from the signup.json file "password cannot contain spaces"
Let me know if I need to make any further changes.
feedback is always appreciated thank you !

Also note, Ignore package.lock.json files those were not meant to be committed

Hello maybe one suggestion :)
Better approach is to force using only specific sets of characters. Let's use regex like this /^[a-zA-Z0-9!@#$%^&*()_+-]+$/, and as error message something similar to "Password contains illegal characters".

Okay will make that change ! 👍

@Ryczko I made a another pull request. I wanted your opinion on the message. I personally feel like its a little long but i also wanted to let the user know what exactly they can use. Let me know if I should go with the current message or try something a little bit more shorter. thanks!

changes were made so that the signup.json file matches the strings inside the t() function to show validation messages.
also @Ryczko sorry for all the commits. I apologize, let me know if you want me to make any further changes
thank you for your time

@MikeProduce I made it a little bit shorter. Thank for the contribution 👏

No problem bro thank you for letting me participate and giving me feedback much appreciated! 👍


How to get video width and height from Local Renderer and Remote Renderer?

Hello,
Thanks for this wonderful work. I've tried the example and got it working, but little confused about how to get specific width / height from the renderer inside RTCVideoView?
What I want to achieve is to make Local Renderer video box appear always on most bottom-right of the screen (the example will have some empty space on the right side because Container has fixed width and not respecting video aspect ratio.

I've fixed my problems by updating flutter_webrtc to version 0.5.6
now they have new properties called videoWidth and videoHeight.

I've fixed my problems by updating flutter_webrtc to version 0.5.6
now they have new properties called videoWidth and videoHeight.


Use formatter API for better integration

I'd recommend to use the languages API to register a formatting edits provider because it will allow for a better integration in VS Code. There is the registerDocumentFormattingEditProvider-function which is the way to introduce a formatter for certain document types. It will integrate you into the Format Code action (context menu, F1) and also into the Format On Save-feature.
It's more or less a matter of calling this code from within DocumentFormattingEditProvider

@jrieken @Dickurt made a pull request for this: https://github.com/Dickurt/vscode-php-formatter/pull/6

Thank you for actually looking at my code guys. I have been meaning to do this, but after the vscode 1.6.0 update came out, I didn't know where to look for the right events to hook into. So you pointed me into the right direction, @jrieken. Unfortunately, my extension is in plain old JS, so I couldn't figure out how to translate the TypeScript to plain JS. I struggled with that for a couple of hours and eventually gave up because I had other things to do.
@maxmatthews I saw your pull request and tested it locally. Unfortunately it doesn't seem to be working. I wrote a review on the pull request.

Anything I can help you guys with?

I will be rewriting the plugin in TypeScript somewhere in the near future. That will help with integrating the new VSCode features more easily.

Resolved with conversion to TypeScript in latest milestone.


Report git repository tag in running head

For those who are developing fonts in a git workflow, it's helpful to know which git commit ID was active when a proof was generated. This adds the latest git commit ID to the running header in the case that the proof is being generated for a font with a given filename and the code is being run from within a git repo. It's obviously not guaranteed that the font was generated by the source file referred to in the commit ID, but if you have a sensible workflow it will be, and in any case, it's better than nothing at all.

Not sure what happened with CI, bit I bet it has to do with SKS dropping off the planet a while back. I'll look into that end of things.

Looks like our Gutenberg urls need fixing.


Toolchain fixes - Update for Angular 4

Tests recently started failing with this stack trace:
yarn test:
ERROR in ./source/tests.entry.ts
Module build failed: TypeError: Cannot set property 'babelOptions' of undefined
    at Object.ngcLoader (/Users/sdavenpo/code/angular-redux/ng2-redux-form/node_modules/@ngtools/webpack/src/loader.js:200:34)
28 01 2017 22:45:11.188:ERROR [karma]: { Error: no such file or directory
    at MemoryFileSystem.readFileSync (/Users/sdavenpo/code/angular-redux/ng2-redux-form/node_modules/memory-fs/lib/MemoryFileSystem.js:107:10)
    at MemoryFileSystem.(anonymous function) [as readFile] (/Users/sdavenpo/code/angular-redux/ng2-redux-form/node_modules/memory-fs/lib/MemoryFileSystem.js:300:34)
    at doRead (/Users/sdavenpo/code/angular-redux/ng2-redux-form/node_modules/karma-webpack/lib/karma-webpack.js:201:29)
    at Plugin.readFile (/Users/sdavenpo/code/angular-redux/ng2-redux-form/node_modules/karma-webpack/lib/karma-webpack.js:205:5)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)
  code: 'ENOENT',

Also, can't run the example: webpack fails with ERROR in Could not resolve "./module" from "./module"

Actually this toolchain is diverging sharply from later angular releases, which is making it increasingly hard to maintain.  @clbond let's see if we can simplify.

Specific items:

[ ] unit tests no longer run
[ ] example all no longer builds
[ ] chai has typing problems that leak out of the package an into people trying to use it
[ ] too many things in deps instead of devDeps; this affects consumers
[ ] no prepublish step

I honestly am not sure it's worth the effort to maintain this library. As far as I know nobody is really using it. @SethDavenport

Updated to work with angular 4<EMAIL_ADDRESS>released with these fixes.


--standalone fails if type names are duplicated

Take this repo and run dotnet build: https://github.com/0x53A/fsc-standalone-test
Result:
FSC : error FS2014: A problem occurred writing the binary 'C:\source\fsc-standalone-test\obj\Debug\net461\fsc-standalone-test.exe': duplicate entry 'System.AssemblyVersionInformation' in type index table [C:\source\fsc-standalone-test\fsc-standalone-test.fsproj]

If I remove <OtherFlags>--standalone</OtherFlags> from the project file, it builds.
The issue is that both this project and a reference (probably Argu) define System.AssemblyVersionInformation (which is autogenerated by FAKE: https://github.com/fsharp/FAKE/issues/1637)

@0x53A As things stand, this is by design.  --standalone doesn't disambiguate type names and requires no duplicates among the assemblies being referenced.  If you want to workaround this, you will need to run some kind of disamibuating tool that does IL-to-IL conversion, or use a different static linker such as ILMerge (though I'm not sure that handles it either)
We could adjust the error message to say that in the case of failed static linking

Yes, that's probably sane. You could hack around it by renaming conflicting types, but as you say, that's probably out of scope for fsc itself and better suited to a dedicated merge tool.

Should we deprecate --standalone technically it really is no problem to have multiple assemblies with the same type. Technically (as far as I know) it is not even a problem to have the same named type in the same assembly (by using multiple "modules"). So this really is a major drawback.


scaling c_{k}_{lambd}

When importances are normalized, i. e. do not change with the uniform scaling of the separate lambda channels, c_{k}_{lambd} doesn't affect anything completely.
Including c_{k}_{lambd} in the iteration would increase computational cost.
c_{k}_{lambd}, where k is l2 is not symmetric with respect to the changing of the order of covariants to contract. Thus it would make single contraction function to loose its general form, where arguments are arbitrary covariants.

This is an interesting issue, but one that needs testing. Scaling diffferent lambda channels might affect model accuracy in real-life scenarios - I have anecdotal evidence that it does.


black block on Wechat wine

Do you mean something like this? @pypeetpy
This happens with wine application menu, when there are shadows. WinSCP for instance. I attached a screenshot.


Release 1.0.0

This big one

Coverage remained the same at 100.0% when pulling 05383d17ba3785de1fc12e3b00fbd7242eb9cfbb on release-canidate into b2ac4f01c3a253b812e200155f4c49ea7d415fb4 on master.

Coverage remained the same at 100.0% when pulling 52e4d4583c3db35028a3f368b651cb2197f873ec on release-canidate into b2ac4f01c3a253b812e200155f4c49ea7d415fb4 on master.

Coverage remained the same at 100.0% when pulling 43b933e0dbf2505a951bc65e86a26dc0b2bc07d0 on release-canidate into b2ac4f01c3a253b812e200155f4c49ea7d415fb4 on master.


Update the document with examples

https://yourbasic.org/golang/package-documentation/
https://blog.golang.org/examples

@AvitalFineRedis notice that we already follow this way of documentation, as exemplified in https://github.com/RediSearch/redisearch-go/blob/master/redisearch/example_client_test.go
Is this issue just to keep track of the extension of examples?

Yes, sure @filipecosta90
I want to add more documentation and more examples :)


MarathonSchedulerActorTest is shaky

On TC I often get:
*** 1 TEST FAILED ***
[18:49:28][Step 3/3] MarathonSchedulerActorTest:
[18:49:28][Step 3/3]
[18:49:28][Step 3/3] - Concurrent reconciliation check is not preventing sequential calls *** FAILED *** (8 milliseconds)
[18:49:28][Step 3/3]   org.mockito.exceptions.verification.TooLittleActualInvocations: schedulerActions.reconcileTasks();
[18:49:28][Step 3/3] Wanted 3 times:
[18:49:28][Step 3/3] -> at mesosphere.marathon.MarathonSchedulerActorTest$$anonfun$14.apply$mcV$sp(MarathonSchedulerActorTest.scala:520)
[18:49:28][Step 3/3] But was 2 times:
[18:49:28][Step 3/3] -> at mesosphere.marathon.MarathonSchedulerActor$$anonfun$started$1.applyOrElse(MarathonSchedulerActor.scala:114)
[18:49:28][Step 3/3]   at mesosphere.marathon.Ma
On my local machine this test is green all the time.

A user reported that the test is still flaky: #3152


GLTF Export Animation Wrong Bone Transforms (Rigify)

Problem

Certain area in exported animation are not correct
Rig generated from Rigify

Relevant bone group: "Dress (Upper)"
Area generated with skin.basic_chain

As far as I can tell, bendy bones in the relavent area have already been disabled (set to 1 segment)

Uses a custom (but not crazy) export script (game-export.py)

export_reset_pose_bones does not appear to affect the issue (#2104)

Looks like the deform bones in the original animation behave similarly to the exported version. The exported version looks more exaggerated. Maybe this is a math error in the baking calculations? Something to do with parenting?

Export operation:
bpy.ops.export_scene.gltf(
        filepath=exportPath,
        export_format="GLTF_SEPARATE",
        export_bake_animation=True,
        # Does not appear to be the issue?
        export_reset_pose_bones=False,
        use_renderable=True,
        export_def_bones=True,
        export_apply=True,
        export_anim_slide_to_zero=True)

Reproducing

Download min-repo.zip and export with export.sh (calls a custom game-export.py script) that outputs to ./export/
Import GLTF file and observe around the armpit area (should only be one action: idle-stretch_hannah-rig)

import-annotated.blend has what I see under the ERROR bone group
Minimum reproduction: min-repo.zip
Expected Behavior
Animations should match
Original:

Exported:

Machine Config

Kubuntu 22.04
GLTF exporter version: 4.0.44
Blender from Snapstore

Blender 4.0.2
Build hash: 9be62e85b727

Looks like setting export_hierarchy_flatten_bones=True fixes the issue, but I am not sure why that is the case.
The rig around that area is pretty simple. Trying to remove the retargeted constraint on sleeve.anchor.B.R and sleeve.anchor.B.L didn't affect anything.

There are multiple things here:

Some non uniform scaling can lead to non decomposable matrices, that cannot be written in glTF files. See #1683, for example, for another case of this issue. Using export_hierarchy_flatten_bones=True avoid this issue by flatten the hierarchy of bones at export.
You have some vertices that are influenced by more than 4 bones. By default at export, only the 4 biggest weights are used. You can change this value, or decide to use all influences at export.

Using these options solve your issues:

Here is repo.blend with reimport of the export, in wire. Seems that everything is ok:

Thanks for the reply!
Looks like my export target (Godot) supports 8 max, but I still have too many influences there. I'll rework the rig and bump up the export maximum instead of allowing unlimited influences.


gadget_serializer: KeyError when fetching events from Contacts calendar

Google Calendar has a built-in calendar called "Contacts" (id<EMAIL_ADDRESS>that syncs with some data like birthdays from Google Contacts, but these events seems to be somewhat special as their gadget-JSON is different from others, as it is missing most paramentes:
{'iconLink': 'https://calendar.google.com/googlecalendar/images/cake.gif', 'preferences': {'goo.contactsGivenName': 'Isabela', 'goo.contactsEventType': 'BIRTHDAY', 'goo.contactsFullName': 'Isabela', 'goo.isGPlusUser': 'false', 'goo.contactsContactId': '123a4b5c6d89efgh', 'goo.contactsIsMyContact': 'true'}}
This difference means GCSA raises an Exception when serializing such events:
  File "C:/Users/eitch/PycharmProjects/gcal2todoist/code/scratch.py", line 11, in <module>
    for event in a:
  File "C:\Users\eitch\PycharmProjects\gcal2todoist\venv\lib\site-packages\gcsa\google_calendar.py", line 183, in get_events
    event = EventSerializer(event_json).get_object()
  File "C:\Users\eitch\PycharmProjects\gcal2todoist\venv\lib\site-packages\gcsa\serializers\base_serializer.py", line 20, in get_object
    return self.to_object(self.data)
  File "C:\Users\eitch\PycharmProjects\gcal2todoist\venv\lib\site-packages\gcsa\serializers\base_serializer.py", line 38, in to_object
    return cls._to_object(json_)
  File "C:\Users\eitch\PycharmProjects\gcal2todoist\venv\lib\site-packages\gcsa\serializers\event_serializer.py", line 94, in _to_object
    gadget = GadgetSerializer.to_object(gadget_json) if gadget_json else None
  File "C:\Users\eitch\PycharmProjects\gcal2todoist\venv\lib\site-packages\gcsa\serializers\base_serializer.py", line 38, in to_object
    return cls._to_object(json_)
  File "C:\Users\eitch\PycharmProjects\gcal2todoist\venv\lib\site-packages\gcsa\serializers\gadget_serializer.py", line 34, in _to_object
    title=json_gadget['title'],
KeyError: 'title'

A simple way to fix this would be to use .get() on all gadget's JSON entries, but the Gadget class checks if some parameters are empty, is there a benefit for this check?
With your help I can prep a quick pull request.

Didn't know about it. Than you for the issue submission.
As this is the case, I think we can use .get() and remove any checks in Gadget. I'd need to check the official docs first. But will be really grateful for a PR

Done. I've decided to build a simple workaround for the gadget_serializer itself, meaning that the empty checks still happens when adding a Gadget to an Event.
Hope you like it. Looking forward to see this patched.


QGIS Plugin

It would be great to create a plugin to make geodiff available to the general user within QGIS

We already have a python client https://github.com/lutraconsulting/mergin-py-client and a plugin https://github.com/lutraconsulting/qgis-mergin-plugin

I was thinking about a plugin or function with in QGIS to specifically use geodiff on local files, not synchronizing with mergin.
Or, at the minimum, adding an example of how to use geodiff from within QGIS (python console).

From QGIS' python console
import Mergin.mergin as mergin
help(mergin.MerginClient)

following with any function you would like to trigger, e.g. download as
https://github.com/lutraconsulting/mergin-py-client#using-python-api
or for geodiff directly
import Mergin.mergin.deps.pygeodiff as pygeodiff

following by any command from here: https://github.com/lutraconsulting/geodiff#using-python-module


FuseBox 4.0.0 - Alpha release

Hey all! Finally FuseBox 4.0 alpha is here.
You can try it out in this repository
New configuration is available for reading here
There are plenty of breaking changes, but this version introduces a much simpler config, most of things are "assumed" therefore there is no need in plugins. In fact most of the configuration is moved to the main config which makes it nicer and easier to configure.
v4 is at least 7x-10x faster than v3
Please start testing, and help out with anything!!! For example documentation  ;-)

What is the new equivalent of the CopyPlugin? I use it, because bundling svg as base64 into bundle.js doesn't seem to work. I'm using styled-components, so I guess I can't use CSSResourcePlugin.

@sentialx CSSResourcePlugin is now a part of the core, and every single preprocessor will respect that.  See stylesheet property

I will add the copyPlugin and include svg as a part of the core (no plugin will be needed)

Thanks, but the CopyPlugin is rather a workaround for me. I would rather like to have my svg and png files bundled as base64 into one js file, but when I was using ImageBase64Plugin the images just didn't show.

I am not sure how bundling png is better than referencing a static image tho. It will be huge

No clear instructions on how to use sparky, it's now a function?

[ ] No ReplacePlugin, is that just a wip right now?
[ ] What's this dependency? https://github.com/fuse-box/fuse-box/blob/v4/package.json#L28

@jpike88 yes, sparky returns an object, every task has a context defined in that function

ReplacePlugin will be added
That's a user error ;-) I will remove it ASAP

What's an example of how to run a sparky call? I just want to define some tasks, and call src a few times, I didn't need any context for that before?

class Context {
  npmTag: 'latest' | 'alpha' | 'next';
  versionBumpType: IBumpVersionType;
}
const { src, rm, task, exec } = sparky(Context);
task('copy-modules', async context => {
  await src('./modules/**/**.*')
    .dest('dist/modules', 'modules')
    .exec();
});

The latest alpha (27) fails whenever I try to use the @material-ui/core library (but based on a larger project this does not seem to be an isolated case). Here's a repro using the tsconfig/fuse.js in the first comment for simplicity.

thanks @Gustorn I will look into it!

@Gustorn<EMAIL_ADDRESS>please keep testing! it has been fixed!

@nchanged Thank you very much, the issue is fixed! Unfortunately I ran into another issue, see the repro in the repository linked above.

@Gustorn thanks, the issue is clear, it's this Babel and _interopRequireDefault should be easy to find a fix. I removed that line and everything is ok! The good news is that it's all bundled correctly

Strange error when using .instructions(' ~ '). to declare a "vendor" bundle.
TypeError [ERR_INVALID_ARG_TYPE]: The "path" argument must be of type string. Received type object
    at validateString (internal/validators.js:107:11)
    at Object.extname (path.js:1223:5)
    at PathMaster.ensureFolderAndExtensions (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/core/PathMaster.js:195:24)
    at PathMaster.getAbsolutePath (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/core/PathMaster.js:120:27)
    at PathMaster.resolve (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/core/PathMaster.js:85:38)
    at PathMaster.init (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/core/PathMaster.js:30:31)
    at ModuleCollection.resolveDepsOnly (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/core/ModuleCollection.js:61:62)
    at ModuleCollection.collectBundle (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/core/ModuleCollection.js:75:24)
    at FuseBox.process (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/core/FuseBox.js:247:32)
    at /Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/core/FuseBox.js:318:25

Everything else has worked great! AMAZING SPEED

@patrickmichalina that's not v4, v4 doesn't contain neither of the syntax. See here for reference.
The latest alpha version is<EMAIL_ADDRESS>

@nchanged I think I managed to fix it in #1531.

Thanks ! I took a brief look, but I think it needs to be fixed on the transpiler level (plugin_js) by adding A statement (like ts does)

@Gustorn I've decided that we need that fix too. Please check the comments there;-)

<EMAIL_ADDRESS>

fusebox({
   ...
  output: 'dist/public/js'
  ...
})

this has strange behavior. It only emits the entry bundle, the vendors are not longer emitted when you set the "output" property parameter.

@nchanged Thanks, the issue was fixed again. After getting through this error I found two new ones, please see them in the same repository.
Example: https://github.com/jcmoore0/fuse-box-v4-apollo.
There is an issue importing the zen-observable-ts dependency.
Appreciate any suggestions.
Uncaught TypeError: Object prototype may only be an Object or null: undefined
at setPrototypeOf ()
at Object.__extends (vendor.js.js:28587)
Thanks so much for V4! ... very nice and super fast.

@Gustorn I know what's the issue about, again, custom transpiler isn't simple ;-) I think it's related @jcmoore0
I am at it ;-)

@Gustorn all of your issues are fixed in<EMAIL_ADDRESS>@jcmoore0  you issue is fixed by adding allowSyntheticDefaultImports: true there is nothing FuseBox can do here, there is default module reference to a module that doesn't contain default exports... (and just in case, upgrade to<EMAIL_ADDRESS>

@nchanged Thank you very much! Unfortunately I'm back with a new issue. This time it has to do with the Node shims that fusebox bundles: they fail when they are used on the right hand side of an instanceof (the repro is in the same repository a usual).

@Gustorn thanks a lot ;-) that's not unfortunate! that's fortunate that we can iron out these issues before going further for testing production builds.

@nchanged  - allowSyntheticDefaultImports worked great, thanks!
Do I need to manually copy assets/images (svg, jpg, png) into dist/resource?   or does a plugin take care of this?

@nchanged I don't understand how to define if a bundle should include/exclude packages. In v3, we can use the .instructions() command. Is there an equivalent here?

@patrickmichalina I will add this functionality soon ;-) As of now, you can just include the files you need into your entry point.
Do you do server too?

@Gustorn could you push your changes? there is nothing new

@Gustorn resolved in<EMAIL_ADDRESS>

@nchanged anything else you need for the ParseError [SyntaxError]: Illegal character '' (1:0) (i'm still seeing in<EMAIL_ADDRESS>

I will update the lib, I think than @KFlash has fixed it already I just need to update it

@nchanged Yup. Fixed a few days ago. Just use Meriyah from NPM

I found a strange issue.
Problem: When 'var jwks' is first initialized, process is an object not a function.  It should be the function declared 16 lines before.
Could this be scoping / hoisting caused?
I thought I'd share.  It's not easy to share a repo.
This is an exact code snippet from vendor.js  (source code is from auth0-js):
function process(jwks) {
return {
modulus: base64_1.decodeToHEX(jwks.n),
exp: base64_1.decodeToHEX(jwks.e)
};
}
function getJWKS(options, cb) {
var url = options.jwksURI || urlJoin$1(options.iss, ".well-known", "jwks.json");
return client.get(url).end(function (err, data) {
var a, key, matchingKey = null;
if (err) return cb(err);
for (a = 0; a < data.body.keys.length && null === matchingKey; a++) (key = data.body.keys[a]).kid === options.kid && (matchingKey = key);
return cb(null, process(matchingKey));
});
}
var jwks = {
process: process,
getJWKS: getJWKS
};

@chrismcv @jcmoore0 should be fixed here<EMAIL_ADDRESS>

That fixed it nicely, thank you.
I would like to get assets working next.
Sparky copied assets to /dist but the target image files (jpg, png, ico) were corrupted.

@nchanged still seeing the same/similar.
ParseError [SyntaxError]: Illegal character '' (1:0)
/*
^

    at report (/home/chris/code/app/web/node_modules/meriyah/dist/meriyah.umd.js:350:13)
    at scanSingleToken (/home/chris/code/app/web/node_modules/meriyah/dist/meriyah.umd.js:780:15)
    at nextToken (/home/chris/code/app/web/node_modules/meriyah/dist/meriyah.umd.js:489:22)
    at parseparseModuleItemList (/home/chris/code/app/web/node_modules/meriyah/dist/meriyah.umd.js:1834:7)
    at parseSource (/home/chris/code/app/web/node_modules/meriyah/dist/meriyah.umd.js:1802:21)
    at Object.parse (/home/chris/code/app/web/node_modules/meriyah/dist/meriyah.umd.js:5037:14)
    at Object.parseAst (/home/chris/code/app/web/node_modules/fuse-box/transform/fastTransform/fastTransform.js:13:20)
    at Object.fastAstAnalysis (/home/chris/code/app/web/node_modules/fuse-box/analysis/fastAstAnalysis.js:18:33)
    at Object.fastAnalysis (/home/chris/code/app/web/node_modules/fuse-box/analysis/fastAnalysis.js:32:34)
    at processModule (/home/chris/code/app/web/node_modules/fuse-box/main/assemble.js:125:51) {
  index: 0,
  line: 1,
  column: 0,
  description: "Illegal character '' (1:0)\n/*\n^\n"
}

@KFlash could you take a look at this? It looks like an issue with<EMAIL_ADDRESS>

@nchanged I can't do much with that issue when it's already solved, and there exist test cases for it. It's related to ZWJ. Before it didn't see ZWJ as a WS, and that error occured.  Both my own tests and Test262 test suite are agree that there is no such issue anymore.

@chrismcv could you reproduce it in a repository? that would be helpful.

@nchanged - is there a way I can get more debugging info out of this? I'm not sure how I can work out what file is causing this?

@nchanged You told me before that the package react-swipeable-views-core:0.13.1 caused the issue. I used parsed it just fine - both the lib and src folder.
Based on the error reported this "Illegal character" has to be the first char in the source parsed. So I will verify that ZWJ doesn't screw up anything as  the first WS.

@chrismcv @nchanged Use latest version of Meriyah from NPM and see if the issue still exist.

Should be here<EMAIL_ADDRESS>

@nchanged  - I added the image corruption issue to
Repo
The jpeg is increased in size when copied.

HMR closes down randomly on me (Mac OSX)
Error [ERR_IPC_CHANNEL_CLOSED]: Channel closed
    at ChildProcess.target.send (internal/child_process.js:678:16)
    at Object.setText (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/logging/Spinner.js:25:21)
    at log (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/logging/logging.js:43:31)
    at Object.info (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/logging/logging.js:72:13)
    at /Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/plugins/core/plugin_js.js:57:29
    at /Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/interceptor/interceptor.js:34:49
    at Array.map (<anonymous>)
    at Object.sync (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/interceptor/interceptor.js:34:39)
    at processModule (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/main/process_plugins.js:6:9)
    at processPackage (/Users/patrick/Code/fusing-angular-2/node_modules/fuse-box/main/process_plugins.js:11:19)

@patrickmichalina yeah, that's cuz of the spinner. I think I am going to remove that....

@nchanged need help with anything? Maybe tag issues with v4?

@patrickmichalina that would be helpful yes! ;-) I am very busy with production builds (treeshaking and stuff). Don't want to get distracted on anything else just yet.

I tried to convert my project, but in alpha37 the VueComponentPlugin seems to be gone?

@sod v4 doesn't have VUE support just yet. I will try to move it as soon as I am done with production builds

Production builds are here<EMAIL_ADDRESS>fuse.runProd({
    target: 'ES5',
    screwIE: true,
    uglify: true,
  });

#1539

Hi, I am running alpha 39, but I am getting "unknown package tslib". Package is installed, am running with esModuleInterop: true.
I am using the same config as in the demo app. Any idea? What more information you need? Pretty much I changed all import * as React .. to 'import React ...` and added esModuleInterop to tsconfig.json.

You should update to latest alpha (48 I think)

import "tslib" in your entry point. Add only allowSyntheticDefaultImports remove the other one

Ok, will try that! One more thing, is the code splitting via dynamic imports supported? The app broke with undefined imports when I did Used Lazy React component.

@tomitrescak it shouldn't be broken during development. However, production support will come later this month.

btw, inheriting tsconfigs is borked. The following tsconfig:
{
    "extends": "../../tsconfig.json",
}

Will produce the following error on 4.0.0-alpha.56:
tsconfig /home/martaver/prj/smoothteam/smoothteam/typescript/sim/tsconfig.json(node:4051) UnhandledPromiseRejectionWarning: TypeError: Cannot set property 'module' of undefined
    at Object.initTypescriptConfig (/home/martaver/prj/smoothteam/smoothteam/node_modules/fuse-box/tsconfig/configParser.js:67:24)
    at Context.setDevelopment (/home/martaver/prj/smoothteam/smoothteam/node_modules/fuse-box/core/Context.js:45:40)
    at Object.createContext (/home/martaver/prj/smoothteam/smoothteam/node_modules/fuse-box/core/Context.js:85:13)
    at Object.runDev (/home/martaver/prj/smoothteam/smoothteam/node_modules/fuse-box/core/fusebox.js:23:35)
    at Object.<anonymous> (/home/martaver/prj/smoothteam/smoothteam/typescript/sim/fuse.ts:30:16)
    at step (/home/martaver/prj/smoothteam/smoothteam/typescript/sim/fuse.ts:32:23)
    at Object.next (/home/martaver/prj/smoothteam/smoothteam/typescript/sim/fuse.ts:13:53)
    at /home/martaver/prj/smoothteam/smoothteam/typescript/sim/fuse.ts:7:71
    at new Promise (<anonymous>)
    at __awaiter (/home/martaver/prj/smoothteam/smoothteam/typescript/sim/fuse.ts:3:12)
(node:4051) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 2)
(node:4051) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

@Martaver yep, extends doesn't work yet

If anyone is testing v4 with typescript they can also try it with typechecker plugin.
Tslinting have been removed. Its been completly rewriten last days.
npm install<EMAIL_ADDRESS>import {pluginTypeChecker} from 'fuse-box-typechecker';

//under plugins
    plugins:[pluginTypeChecker({
        tsConfig: './src/tsconfig', // optional, uses default if missing
        name: 'Superman' // optional, uses "no-name" if missing
    })]


Allow log delivery from ELBs in different regions

Extended feature

Allow log delivery from ELBs in different regions

added example for multiple regions... missed it on first commit...

@soerenmartius works fine now.. R4R


Documentation Improvement

Surface is an amazing project.
I think it'll be helpful if increased attention is given to its documentation.
Specifically, why are there two alternative documentations? Hexdocs and Suface-UI.org? Are they to serve different purposes?
I suggest that investing effort into an improved hexdocs page will suffice.

That will be very helpful.
With surface-ui.org we can have live examples of Surface components, it works as the catalogue but for showing Surface concepts instead of components.
We'll soon release a blog that will be available in surface-ui.org
After that we'll have 4 sources of documentation:

surface-ui.org
hexdocs.pm/surface
blog in surface-ui.org
catalogue

Each one has it's advantages and disadvantages to different aspects of documentation: tutorial, how-to guide, explanation and reference. We still need to find the right balance on that.
Please contribute in what you find will have the best value to you, it sure will have value to the community.

I think it could be worthwhile slimming down surface-ui.org and having all the non-demo documentation moved to hexdocs guides? Hexdocs is where people expect it, at least that's where I expected it at first. That said, I rarely look at Surface's hexdocs these days, tending to the website and the source, but do find it hard to find some things on the website.

A number of the pages are made up of Markdown components. Would there be an opportunity to use an @external_resource attribute, and extract the content into some .md files in the surface-ui repo that ExDoc can pick up?
Or maybe some iframes on the surface_site to the hexdocs guides😅
Maybe what we need is a kind of rubric or understanding for what we'd want where, or where we'd want people to go for which kind of learning? idk, 😶🌫 just asking questions to see if it helps. Not making suggestions


links outside of Adobe domain are not flagged and do not warn that you are navigating away from adobe.com or that it's an external link. example link : https://www.java.com/en/configure_crypto.html

Issue in /src/pages/before-implement/tls-transport-layer-security-encryption.md

similar example. : For more information about ITP, see Apple Intelligent Tracking Prevention (ITP) 2.x. under "CNAME and Adobe Target" section.

While it is true there is no text or flag, any links that lead to pages outside of the developer doc portal (developer.adobe.com) open in a new tab, to help the user understand they have left the context of the current page (which remains preserved in the original tab). This includes links to experienceleague.adobe.com, as well as links external to Adobe entirely. Only links that stay within the dev doc portal open in the current tab.
That being said, there is another (separate) issue with the second example you listed: "For more information about ITP, see Apple Intelligent Tracking Prevention (ITP) 2.x. under "CNAME and Adobe Target" section." -- This link goes to another page within the dev doc portal, meaning it reloads in the current page as described above; however, the side nav fails to expand to indicate where in the site the user has been taken to. This loss of context is very confusing. I will open a new issue for this, but will close the current issue, as we will be using the context of current v. new tabs to indicate to users when they are being taken outside the dev portal.


Pipelines Agent artfact (with autologon = true) doesn't come online on Win 10

I'm trying to use the Pipelines Agent artifact (windows-vsts-build-agent) to setup a new agent`:

using Azure's Windows 10 Pro image
configured interactively (with autologon = true)
with the goal to run UI Tests on it (through Azure Pipelines).

What's happening:
While the agent configuration succeeds (an entry is created in Agent Pool on Azure Piplines), it shows as offline.
What we have tried so far:
After logging in to this VM manually, I can see this screen:

After confirming this screen and restarting the VM manually, the agent comes up as expected.
Question:
Any ideas/hints what we can do, so the agent comes 'online' without the need for manual intervention?
Thanks,
--Neno

Hi Neno,
I ran into a similar issue and I don't know how to resolve the issue.
However, I have found a workaround that worked for me.
Thanks to confirmation of:

Is your scenario similar?
The workaround works for you

Test scenario:

Provisioning of the VM is successful (through a Release Pipeline)
Registration as Agent in the DG is initially successful (shows "Online" then "Offline")
Machine reboots itself for "autologon" (and readiness for interactive tests)

Expected:

The VM starts, logs in automatically, and stars the agent in a Console

Actual:

The VM is "running" but never registers again

So I suspect the VM is blocked on the screen you have attached

Workaround

In the Pipeline, Stop the VM, and then Start it again

The tests I run have a screen recorder configured where I can see that it works as "Expected"

Best regards,
Chris.

@DeChrist, if we restart the VM after adding the agent, do you think it will solve the issue? It seems from the workaround above, that it should do the trick. Can you please confirm?

Updates have been done to the corresponding artifact. Please retry and re-open, as needed.

Hi @leovms
This issue still happens.
Do you have any workaround for it ?

@Evit15, workaround is described above. If that does not work for you, it may be that there's another issues at play. If so, please open a new request and describe in detail your observations.

Hi @leovms
The workaround does not work both image win 10 1809 and 1903
The step to reproduce and expect as @NenoLoje posted. I think we only need reopen this issue.

@NenoLoje @Evit15 @leovms I am still facing the same issue mentioned in the steps to reproduce. My agent is not coming online and I am seeing the same screen when logged in manually. I even tried the workaround: stop and start the vm, it did not worked out. could any of you please let me know how to fix this?


Fix import

I had to update the import to be able to build the project. The dep was updated in this commit.

Thank you @dirkcuys! Should be fixed now, in PR #113.


Issue solved

This pull request resolves #2

Added color
Aligned subject heading
I have written the code for the colors. You can change the colors if you don't like these ones.

@musaddiq-ashfaq Could you make your changes in a new CSS file, say style2.css? And you need to make changes in script.js to access that CSS file, when the theme is changed.


[BUG] Build command outputs to root folder.

What happened?
When using build command ./build/chrome-mv3-prod folder gets created, yet the whole build gets saved to the root folder. I've ran the build command with both pnpm and npm, also I've also tried specifying --build-path=./build/chrome-mv3-prod but got the same result.

Version
Latest
What OS are you seeing the problem on?
Windows
What browsers are you seeing the problem on?
Chrome
Relevant log output
> plasmo build "--verbose"

🟡 0      | Running command: build
🟣 Plasmo v0.69.2
🔴 The Browser Extension Framework
🔵 INFO   | Prepare to bundle the extension...
🟡 1      | Creating Manifest Factory...
🟡 2      | Ensure exists: C:\Users\ckuka\VS Code Projects\Chrome Extensions\guessthegame\.plasmo
🟡 3      | C:\Users\ckuka\VS Code Projects\Chrome Extensions\guessthegame\assets\icon.png found, creating resized icons
🟡 4      | Creating static templates for popup
🟡 5      | Creating static templates for options
🟡 6      | Creating static templates for newtab
🟡 7      | Creating static templates for devtools
🟡 8      | Parsed config: {
  matches: [ 'https://guessthe.game/', 'https://guessthe.game/?fpg=*' ],
  run_at: 'document_end',
  all_frames: true
}
🟡 9      | Adding content script:  C:\Users\ckuka\VS Code Projects\Chrome Extensions\guessthegame\contents\controls.ts
🟡 10     | Parsed config: {
  matches: [ 'https://guessthe.game/', 'https://guessthe.game/?fpg=*' ],
  run_at: 'document_end',
  all_frames: true
}
🟡 11     | Adding content script:  C:\Users\ckuka\VS Code Projects\Chrome Extensions\guessthegame\contents\topNavigation.tsx
🟡 12     | Creating content script mount for contents
🟡 13     | Parsed config: {
  matches: [ 'https://guessthe.game/', 'https://guessthe.game/?fpg=*' ],
  run_at: 'document_end',
  all_frames: true
}
🟡 14     | Adding content script:  C:\Users\ckuka\VS Code Projects\Chrome Extensions\guessthegame\contents\searchBarResults.ts
🟡 15     | Parsed config: {
  matches: [ 'https://guessthe.game/', 'https://guessthe.game/?fpg=*' ],
  run_at: 'document_end',
  all_frames: true
}
🟡 16     | Adding content script:  C:\Users\ckuka\VS Code Projects\Chrome Extensions\guessthegame\contents\ARIA.ts
🟡 17     | { messageHandlerList: [], portHandlerList: [] }
🟡 18     | Creating BGSW entry
🟡 19     | Hash changed, updating manifest
🔵 INFO   | Loaded environment variables from: []
🟡 0      | @plasmohq/parcel-transformer-manifest
🟡 1      | Adding icons
🟡 2      | Adding default_icon
🟡 3      | Handling background service worker
🟡 0      | @plasmohq/parcel-bundler
🟡 0      | @plasmohq/parcel-packager
🟢 DONE   | Finished in 5420ms!

(OPTIONAL) Contact Details
<EMAIL_ADDRESS>Code of Conduct

[X] I agree to follow this project's Code of Conduct
[X] I checked the current issues for duplicate problems.

This is super weird - do you have a monorepo setup? Also what does your tsconfig looks like?

Also is plasmo build being run within that directory?

This is super weird - do you have a monorepo setup? Also what does your tsconfig looks like?

No, no monorepo.
My tsconfig is
{
  "extends": "plasmo/templates/tsconfig.base",
  "exclude": ["node_modules"],
  "include": [".plasmo/index.d.ts", "./**/*.ts", "./**/*.tsx"],
  "compilerOptions": {
    "paths": {
      "~*": ["./*"]
    },
    "baseUrl": ".",
    // my settings overrides
    "strict": true,
    "isolatedModules": true,
    "allowSyntheticDefaultImports": true
  }
}

Also is plasmo build being run within that directory?

Yeah, from the root directory.

@HugeLetters can you make a simple reproduction of this issue in a repo? I have 3 active projects using the framework and have not experienced this issue...

Interesting... dev works, but prod build's path broke completely?!....

@HugeLetters found the issue - and it's related to how our bundle look for the "root" distribution directory and resolving the package.json. Remove the main field in your package.json and it should be fixed:
Remove these 2 lines:
  "main": "index.js",
  "type": "module",

This is not the specification of the framework (standardization of package.json is... none basically), so I will close this for now.

Also @HugeLetters :
  "manifest": {
    "manifest_version": 3,
    "name": "guessthegame extended"
  },

These are not needed - to control the name of the extension, use the displayName property of package.json <- this maps directly to package.json's commonly used props

Also @HugeLetters :
  "manifest": {
    "manifest_version": 3,
    "name": "guessthegame extended"
  },

These are not needed - to control the name of the extension, use the displayName property of package.json <- this maps directly to package.json's commonly used props

Thank you!


Failed to mount component: template or render function not defined

Use happyPack + vue-loader and get this warning:

Here's my webpack config:
const HappyPack = require('happypack')
const os = require('os')
const happyThreadPool = HappyPack.ThreadPool({ size: os.cpus().length })
...
module: {
    rules: [
    {
        test: /\.vue$/,
        loader: 'happypack/loader?id=vue',
    },
 ...
plugins: [
    new HappyPack({
      id: 'vue',
      threadPool: happyThreadPool,
      cache: true,
      verbose: true,
      loaders: [{
        loader: 'vue-loader',
        options: vueLoaderConfig
      }]
    }),
...

thanks for help

I meet this problem too

Can you show me what's inside vueLoaderConfig?

Here's my  vueLoaderConfig
@amireh
var utils = require('./utils')
var config = require('../config')
var isProduction = process.env.NODE_ENV === 'production'

module.exports = {
  loaders: utils.cssLoaders({
    sourceMap: isProduction
      ? config.build.productionSourceMap
      : config.dev.cssSourceMap,
    extract: isProduction
  }),
  transformToRequire: {
    video: 'src',
    source: 'src',
    img: 'src',
    image: 'xlink:href'
  },
  postcss: [require('postcss-cssnext')()]
}

postcss: [require('postcss-cssnext')()] won't work as stated in many other issues (mostly related to postcss.)
Functions can't be serialized by happypack; your webpack configuration has to be free of functions in any loader configuration. To fix this particular problem, postcss accepts configuration from a file. So pass it a path to a file that has module.exports = [ require('postcss-cssnext')() ] and it should be OK.
I hope that helps.

It works! Thanks for help @amireh


Add video use case block; todo: "coming soon" label might change

Description

Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

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

Checklist:

[ ] I have signed the Adobe Open Source CLA.
[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

TO-DO: the video use case header tag might be "Beta" instead, if so, export image from Figma file


Address fixes pointed out in #419

Add a new unrecognized tag error.

Abstract over NoTypeHint.

Fix class keyword repetition in UnrecognizedClass.

Mark stack as mutable.

Can you review this @jsuereth ?


Image update manual merge request

Summary
I tried to update the image for my token with this image https://raw.githubusercontent.com/GZDragonHead/GZ/main/IMG_3633.jpg in this PR #23710 but it did not auto merge.
commit a9b2d88f1d456f47f0511035a7a0d116261028cd

PR looks to have been closed


Please don’t spam

Hi! I just got spammed in the email on my profile! That’s not nice, please don’t spam people (specially those who specifically opted-out from spam).

Sorry, my fault...

Seriously.  Not nice.

@tonious I am really sorry about this, our program bug caused this problem, I promise that it  will not happen again...

This "bug" still exists because I was just spammed.


For a POST with body taking an array of strings, elements of the array can be improperly coerced into numeric values.

So with schema like:
/vocabulary:
post:
operationId: "vocabularyPOST"
produces:
- "application/json"
parameters:
- $ref: "#/parameters/vocabBody"
....
vocabBody:
in: "body"
name: "body"
description: "JSON array of term codes."
required: true
schema:
$ref: "#/definitions/termCodeList"
...
termCode:
type: "string"
termCodeList:
type: "array"
items:
$ref: "#/definitions/termCode"
A POST with body ["1"] will fail validation.
Internally it seems that the "1" is coerced into an integer, and then the array [1] fails validation.
If I'm understanding the code, the issue is at https://github.com/apigee-127/swagger-tools/blob/master/middleware/helpers.js#L231
where schema can (if it's a request parameter?) need to be dereferenced to schema.schema. Something similar seems to be happening at https://github.com/apigee-127/swagger-tools/blob/master/middleware/helpers.js#L43
But I've not traced it all the way down.

I'll take a peek.

Great!
Looking at it more closely, I think any string in the array that's valid JSON with be JSON.parse()ed.
Workaround I am thinking about in helpers.js:

var iSchema = _.isArray(schema.items) ? schema.items[index] : schema.items;

 // Apparent bug: schema for a parameter is one level down from the passed in schema

 // so iSchema will be undefined, resulting in unwanted conversions.

 // something like this was already being done in getParameterType() q.v.

 var tSchema = schema.schema ? schema.schema : schema;

 var iSchema = _.isArray(tSchema.items) ? tSchema.items[index] : tSchema.items;

@whitlockjc does my workaround seem reasonable? I'd like to land a fix in my own local copy of swagger-tools, at least, but would feel better about it if made sense to you ;)

I think we just need to avoid using JSON.parse on items whenever we're coercing them if the type is string.  That would be the ideal solution.

This also affects responses.
Given this response definition
      "type": "array",
      "items": {
        "type": "string"
      }

and this response
[ '1a', '2b', '3c', '4d', '5e', '987123E456' ]

Swagger errors out with
code: "INVALID_TYPE",
message: "Expected type string but found type unknown-number",
path: [
"5"
]

This is because the string "987123E456" can be parsed into a valid JS number. This is a production-breaking bug for my application right now.

Thanks for the heads up.  I'll be on it soon.

In the meantime, is there a way to tell swagger that any type is valid as item type?

Ok, this works
      "type": "array",
      "items": {}

That was going to be my answer.  ;)

Any news? It's really annoying bug and it's breaking my production env when sending twitter ids. It's just parsed in the wrong way and I am getting different number...

Hi.
We experienced this too in production.
Our swagger.yml file consisting something like:
swagger: '2.0'
paths:
  '/v1/some/api':
    post:
      summary: ...
      operationId: ...
      consumes:
        - application/json
      produces:
        - application/json
      parameters:
        - name: collectionIds
          in: body
          description: 'Collections to retrieve'
          required: true
          schema:
            type: array
            items:
              type: string

for every array of collectionIds it was passing correctly (or did it?) but for the following body ['60000528880e130012727947']
is started returning an error:
Request validation failed: Parameter (collectionIds) failed schema validation",

    "errors": [
        {
            "code": "INVALID_TYPE",
            "message": "Expected type string but found type unknown-number",
            "path": [
                "0"
            ]
        }
    ]

Debugging this project, seems the the issue is swagger-validator.js file, inside the validateValue function.

In case of an array, when this line is triggering:
val = mHelpers.convertValue(val, schema, mHelpers.getParameterType(schema), location);

it will reach this block inside convertValue which will recursive call itself

and iSchema will be for some reason undefined, so it will call convertValue with second and third param of undefined for the items inside the string.
so, convertValue will get the schema and type params with undefined values

and will replace schema with {} (object)
then, it will reach the case object block

which will try to run JSON.parse on the string.
for every string, it will be ok, as JSON.parse will return error,

and then the convertValue function will return the original value which can then be validated against string correctly,
but in our special case, the id was containing only numbers with one 'e' char in the middle...
so JSON.parse consider this string as e-notation number .  the exponent,<PHONE_NUMBER>47, is too large to fit into a 64-bit floating pointing, so it defaults to Infinity,

which then ofcourse can't be validated against string.
for now, we used @diversario solution and replaced the validation with
"type": "array",
"items": {}

but it's not really a solution as we lost the string validation(?).
is there anything we can fix in our swagger.yml file to have convertValue detect iSchema.type correctly as string?
or is this a bug in the code?
Thanks in advance for this helpful project!

Hi.
We experienced this too in production.
Our swagger.yml file consisting something like:
swagger: '2.0'
paths:
  '/v1/some/api':
    post:
      summary: ...
      operationId: ...
      consumes:
        - application/json
      produces:
        - application/json
      parameters:
        - name: collectionIds
          in: body
          description: 'Collections to retrieve'
          required: true
          schema:
            type: array
            items:
              type: string

for every array of collectionIds it was passing correctly (or did it?) but for the following body ['60000528880e130012727947']
is started returning an error:
Request validation failed: Parameter (collectionIds) failed schema validation",

    "errors": [
        {
            "code": "INVALID_TYPE",
            "message": "Expected type string but found type unknown-number",
            "path": [
                "0"
            ]
        }
    ]

Debugging this project, seems the the issue is swagger-validator.js file, inside the validateValue function.

In case of an array, when this line is triggering:
val = mHelpers.convertValue(val, schema, mHelpers.getParameterType(schema), location);

it will reach this block inside convertValue which will recursive call itself

and iSchema will be for some reason undefined, so it will call convertValue with second and third param of undefined for the items inside the string.
so, convertValue will get the schema and type params with undefined values

and will replace schema with {} (object)
then, it will reach the case object block

which will try to run JSON.parse on the string.
for every string, it will be ok, as JSON.parse will return error,

and then the convertValue function will return the original value which can then be validated against string correctly,
but in our special case, the id was containing only numbers with one 'e' char in the middle...
so JSON.parse consider this string as e-notation number .  the exponent,<PHONE_NUMBER>47, is too large to fit into a 64-bit floating pointing, so it defaults to Infinity,

which then ofcourse can't be validated against string.
for now, we used @diversario solution and replaced the validation with
"type": "array",
"items": {}

but it's not really a solution as we lost the string validation(?).
is there anything we can fix in our swagger.yml file to have convertValue detect iSchema.type correctly as string?
or is this a bug in the code?
Thanks in advance for this helpful project!


feat: support strictTemplates for public components

PR Checklist
Please check if your PR fulfills the following requirements:

[x] The commit message follows our guidelines: https://github.com/NG-ZORRO/ng-zorro-antd/blob/master/CONTRIBUTING.md#commit
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] Application (the showcase website) / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: N/A
What is the new behavior?
Does this PR introduce a breaking change?
[ ] Yes
[x] No

Other information

@vthinkxie Strict Property Initialization 要加吗，做这个之前需要完成 WithConfig 的重构哦

@vthinkxie Strict Property Initialization 要加吗，做这个之前需要完成 WithConfig 的重构哦

这个在 9.1 再上吧，今天来不及了


include/exclude for find_namespace_packages doesn't work for sdists

What the title says. Works as expected for bdist_wheel, but for sdist the include and exclude params for find_namespace_packages appear to be completely ignored. This may also effect find_packages(); I didn't test.
This repository https://github.com/kgreav/broken_setuptools has an example project - run either of the setup.py files with sdist and compare with a bdist_wheel

The packages  argument only refers to what gets installed, not what gets included in distributions. If you want to exclude something from an sdist, you do it in MANIFEST.in, though it seems like a rare situation to me to want to only ship a subset of the stuff in your src/ directory.

A bit of background:
My use case is that I want to split a single source repository into several namespace packages. This wasn't previously a problem because they were all in separate repositories, but that was cumbersome and unnecessary so we chose to amalgamate them into a single repo; however I still want to package each namespace separately. I don't really mind that sdist doesn't work because I plan on distributing wheels anyway, but this discrepancy cost me a bit of time debugging. I don't think MANIFEST.in works here, as I'd require a specific MANIFEST.in for each package, which would amount to splitting out everything into separate repositories again anyway.
There are a few problems I can see here, I think, but at a base if we assume everything is working as expected, then at the very least I would argue that include/exclude shouldn't be silently ignored for sdist, and/or documentation should be updated accordingly (I'd even go as far as saying a formal definition of sdist should be documented, which it seems it's currently not).
However, it seems to me that find_[namespace]_packages defines what the package and distribution is and that it's perfectly acceptable to have one source that creates multiple distributions and packages (especially in the context of namespaces).
Given peoples current definition of a source distribution as being "whatever is required to build a wheel and meet the distribution requirements of any included third party code", then having the complete source for all other packages that are potentially built alongside it (but not necessary to build the package itself) in the equivalent source distribution seems excessive.

@kgreav That use case is not really supported. If you want to use setuptools, you have a single setu.cfg and/or setup.py in the repository root. You'll have to come up with your own solutions for unorthodox package configurations.


Add status output to ShouldMigrate

Description
This adds status output to the ShouldMigrate method, and errors appropriately for etcd vs KDD when v1 resource is not present.

Rather than writing logs we write to the StatusWriter (which for the CLI outputs to screen and for KDD outputs to logs)
Messages are reworded a little to (hopefully) make a little more sense for the CLI
Handle the v1 CalicoVersion no present by erroring for etcd (since it indicates the access details are wrong or that the user is running the migration script when they shouldn't), and for kdd indicating that migration is not required.

Todos

[ ] Tests
[ ] Documentation
[ ] Release note

Release Note

None required

Targeting this for a post-3.0 improvement for now.


Check if solrUrlSvc.parseSolrUrl is actually used

in a quick search, I don't think it is used in real code!

Okay, it is used by Splainer, but not by Quepid oddly!


Changing map style changes layering

When I start my map, the layering is how I want it: Simplified: World labels at the top (worldSubLabels layer), polygon icons under that (invalidStockSymbols layer) and polygons at the bottom (polygons layer).

When I change to any other style if the map has already loaded (with the controls in the gui), the map layer order seems to change: World labels at the bottom.

Looking at map.layers, I see no big difference:
Before:

After:

Is this a bug?

Can you provide more information on how you add your layers to the map. Do you provide a layer ID to insert your layers below another layer?

Hi @rbrundritt,
I currently insert the layers below eachother, but I believe that I had the same problem in the past when I was just adding the layers without inserting them before another layer. This is how I currently handle layering:
    // Top Layer: Visualisation of the main world location label
    mainWorldLocationDataSource= new atlas.source.DataSource('worldMainSource');
    mainWorldLocationDataSource.add(new atlas.Shape(new atlas.data.Point(...)));
    map.sources.add(mainWorldLocationDataSource);
    map.layers.add(new atlas.layer.SymbolLayer(mainWorldLocationDataSource, 'worldMainLabel', {...}));

    // Layer before previous layer: Visualisation of the sub world location labels
    worldLocationDataSource = new atlas.source.DataSource('worldSubSource');
    worldLocationDataSource.add(JSON.parse(JSON.stringify(...)));
    map.sources.add(worldLocationDataSource);
    map.layers.add(new atlas.layer.SymbolLayer(worldLocationDataSource, 'worldSubLabels', {...}), 'worldMainLabel');

    // Layer before previous layer
    ....

    // etc.

I'm able to reproduce this issue. Looks like a new bug, most likely related to the new base map styling they added recently. I'll send this over to the Azure Maps team so they can investigate.

@rbrundritt Does azure-maps-control not have a public github repository? I tried using the bouncing marker animation sample using the 'azure-maps-control' npm package and the interface no longer matches what the sample says to do. It's been a real PITA trying to find the code base for this. It'd be bonkers for this not to live in a public github repo when so many of Microsoft's other javascript npm packages are.

This is the first time anyone asked for it to be open source. There were discussions with the MapLibre community about making the Azure Maps source code open source (Azure Maps Web SDK is a wrapper around that control and provides an enhanced API interface and features). That community wasn't that interested in it at the time, and only wanted certain features which the team has shared back with them. As for other open-source Microsoft JavaScript libraries, most are autogenerated REST clients, while most UI based controls are not open source.
As for the issue with the animation module, this is the first time I've heard of that one, and that module has been around for years and is used a lot. I'll see if I can reproduce the issue you are seeing.

Note, if all you want is a bouncing marker, don't bother with the animation library, you would be loading a lot of extra code for nothing. Simply use a CSS animation with the HTML marker. For example:
<!DOCTYPE html>

    <title></title>

    <meta charset="utf-8" />
    <meta name="viewport" content="width=device-width, initial-scale=1, shrink-to-fit=no" />

    <link href="https://atlas.microsoft.com/sdk/javascript/mapcontrol/3/atlas.min.css" rel="stylesheet" />

@rbrundritt Thanks for the bouncing marker. Looks more effective than the sample. So we had to shift from Google Maps to Azure Maps for privacy reasons. Maybe I'll just create an issue in this repository if I come across any bugs or feature requests. I have one to ask how to add a button that will re-center the map to a known marker.
I'm surprised I'm the first to ask about making the azure map related js libs open source. This is a great alternative to Google Maps. I like how you have some separation between the map and the map api (azure-maps-control and azure-maps-rest). I think it's cool you have an actual class that holds your api token that can be used for both the map and the api. The MapControlCredential class. It feels intuitive to have it be open source when you have all the code in front of you anyway.

Glad to hear you like the Azure Maps Web SDK. I designed the original API interface for it and spent a lot of time trying to make things line up seamlessly to make the most sense.
Since you are new to Azure Maps, here are a few key resources:

Technical forums (please use these to ask questions as these are monitored more closely)

https://docs.microsoft.com/en-us/answers/topics/azure-maps.html
https://stackoverflow.com/questions/tagged/azure-maps

Code sample site (this is github repo is the source code for that site): https://samples.azuremaps.com/
For bugs in the platform or SDK, you can start by asking in the forums and the community can help you debug. If it's something more serious, like a service outage or other notable issue, open up a support ticket in the Azure portal (click on your Azure Maps resource in the portal and on the left side panel is a link for support). The Azure support team can be a lot more responsive on these types of issues since it's  monitored 24/7 and they can call people in if needed.
Docs: https://learn.microsoft.com/en-us/azure/azure-maps/

As for your question on using a button to recenter on a marker, there are several ways to do this.
If you simply want to just center the map and don't really need to interact with the mark (e.g. display a popup or start/stop some animation), you can simply have the button pass the markers lat/lon values into a function to center the map. Here is a simple example:
<input type="button" value="Center" onclick="map.setCamera({ center: [45, -110], zoom: 14 })" />

If you need a reference to the marker for some reasons, the tricky part is having a way to cross reference the button to the marker/shape. You could add a click event in code that has direct access to the marker reference, but that isn't that efficient if you have a lot of markers as you would end up with each button having its own click event. Instead, store a unique string value for each marker in each button (assuming you have multiple buttons). Using the rel property of the button to store a string value is pretty common. From there you can grab this value when the button is clicked and then do a look up for the marker/shape in question.  For example:
var marker = new atlas.HtmlMarker(...);

//Store properties in a marker,
marker.properties = { id: 1234 };

//Example of a button that has the marker ID stored in the rel property.
<input type="button" value="Center" onclick="buttonClicked(this)" rel="1234" />

//Function called by button that gets the stored ID value, looks up the marker in question, and centers the map on it.
function buttonClicked(btnElm) {
    var id = btnElm.rel;
    var marker = map.markers.getMarkers().find(m => m.properties.id == id);
    map.setCamera({ center: marker.getOptions().position, zoom: 14 });
}

The Azure Maps Web SDK team has confirmed that this issue has been fixed in latest version of the SDK (released Jan 12th). See the bug fixes section of the 3.1.0 release here: https://learn.microsoft.com/en-us/azure/azure-maps/release-notes-map-control#v3-latest


Segmentation on personal dataset

Hi, your work looks great, and I am tryin to use it to segment my own images. and I am just unsure of how I would go about that. I was thinking of using the pretrained weights and  CLEVRTex, what confuses me is figuring out where to insert my input data. Any suggestions would be helpful, thank you

This is the file we use for evaluating image segmentation. Maybe replace the input image with your images.

Thank you for the reply! I was able to test the model with my own images.
However, I dont know how to get the output data. Like with my input image, I want a segmented image as the output (and maybe masking information) as in your examples but I am unsure of how to generate. I looked at the nerv directory and saw scripts on writing out the image data and was wondering if that was how to get the segmented image output.
Please let me know how I can go about generating the output, and suggestions would be appreciated, thank you.


Garbage symbol instead of bullets

Weird symbol (instead of bullets) before women, men in STI tests
Test tab, Patient/Provider, female/male, 18-150, STI tests, EN
Weird symbol (instead of bullets), in Ultrasound for AAA tests
Test tab, Patient/Provider, male, 65-80, EN

fixed

Special characters in front of Men and Women - STI Tests
Similar issue as above for ultrasound AAA

fixed JSON file... let's re-check it after another update.

i removed the extra garbage icons on JSON(edited existing code,not the json)

Please let me know
I am making a json of the excel file meliks just uploaded

Wait a minute ...why do we have an english tests...when i check in french TEsts

This issue is already fixed by me. Please always try to read the latest comments before start working. I haven't committed it and I updated the JSONs on google drive for production.
So please move forward.
Thanks.
@RISHANGSHARMA

@RISHANGSHARMA and yes unfortunately there was a big issue there for languages. Hopefully I fixed it. But thanks a lot for your attention and bringing it up

ok thanks @melikaeft ...yes i was about the french file..there was no comment on that , so thats why i dragged attention towards it.

should be fixed on the test website update (13-7-2020: 6 PM)
Please consider it in your tests.

Patient Female 55 | Tests | Low dose CT scan | An x-ray machine scans the lungs | Lack of period.
Patient Female 18 | Tests | Rubella and Varicella immunity | if you are non immune you may become infected with rubella during a pregnancy | No capitalization at the beginning of the sentence.
Patient Female 18 | Tests | STI tests | •Women: a pelvic exam or a urine test; and blood tests. | Assume the 'a' that after double quotes should be capitalized.
Patient Female 18 | Tests | STI tests | •Men: a urine test and blood tests | Lack of period. Assume the 'a' that after the colon should be capitalized.
Patient Female 18 | Tests | STI tests | The test done by pelvic exam in women is for Chlamydia and Gonorrhea | Lack of period.
Patient Male 65 | Topics | Be active | while you are active you have enough breath to say a short sentence but not enough to sing | Lack of period. Assume the 'w' that after the colon should be capitalized.
Patient Male 18 | Topics | Bone health | Below age 65: only recommended if: you have [[risk factors; https://www.canada.ca/en/public-health/services/chronic-diseases/osteoporosis.html]] | Extra colon before you. Assume the 'o' that after the colon should be capitalized.
Patient Male 65 | Topics | Bone health | Recommended for everyone 65 or older Your provider will determine when to repeat it | Lack of period.
Patient Female 18 | Topics | COVID-19 | First Nations, Métis, Inuit | The language seems wrong.
Patient Female 18 | Topics | COVID-19 | COVID-19 Español, Arabic, Mandarin and other languages | The language seems wrong.
Provider Female 65 | Topics | Falls in the elderly | The American Geriatrics Society and British Geriatrics Society recommend asking about falls every year | Lack of period.
Patient Female 18 | Topics | Family Planning | •Rubella, Hepatitis B, HIV:can affect your unborn child. | Lack of space after colon and the 'c' should be capitalized.
Patient Female 18 | Topics | Family Planning | •Chicken pox: which can be very serious for you in pregnancy. | Lack of space after colon and the 'w' should be capitalized.
Provider Female 18 | Topics | Family Planning | •Hepatitis B and HIV disease in women of childbearing age, | Should be a period.
Provider Female 18 | Topics | Heart disease | more potent than statins in preventing heart disease | No capitalization at the beginning of the sentence.
Provider Female 18 | Topics | Heart disease | see our physical activity section | No capitalization at the beginning of the sentence.
Patient Female 50 | Topics | Heart disease | or at the age of menopause. | No capitalization at the beginning of the sentence.
Provider Female 75 | Topics | Heart disease | •before 40 in men and 50 in women if risk factors | No capitalization at the beginning of the sentence.
Provider Female 75 | Topics | Heart disease | •for men age 40+:repeat every 3-5 years if N | No capitalization at the beginning of the sentence.
Provider Female 75 | Topics | Heart disease | •for women age 50+ or at menopause:repeat every 3-5 years  if N | No capitalization at the beginning of the sentence.
Provider Female 75 | Topics | Heart disease | •age 75 + healthy: discouraged as have not been validated at this age | No capitalization at the beginning of the sentence.
Provider Female 30 | Topics | Lung | recommended by Canadian Task Force (CTF)for certain patients 55-74 | No capitalization at the beginning of the sentence.
Provider Female 50 | Topics | Physical Exam | •[["at appropriate medical visits" according to CTFPHC; | No capitalization at the beginning of the sentence.
Provider Male 18 | Topics | Sex & Prostate | •offer HIV testing to all: | No capitalization at the beginning of the sentence.
Provider Female 50 | Topics | Substance Abuse | Help available for patients addicted to a substance/gambling: each province or territory has a help line: [[more; https://www.canada.ca/en/health-canada/services/substance-use/get-help/get-help-problematic-substance-use.html]]: Screening and counseling USPSTF I (2018) under review | No capitalization at the beginning of the sentence. And there are two consecutice colons in the same sentences.
Provider Female 18 | Topics | Vision | Consensus only recommendation from Canadian Ophthalmol Society 2007 | No capitalization at the beginning of the sentence.
Provider Female 18 | Topics | Vision | Currently in many provinces this would be done by optometrists | No capitalization at the beginning of the sentence.

The issue tested on iPad Safari, all good now.

Referring to EN content in FR Tests tab, this is fixed.