Enhancement: Workfile template builder using publishes instead of direct filepath

Is there an existing issue for this?

[X] I have searched the existing issues.

Please describe the feature you have in mind and explain what the current shortcomings are?
The workfile template builder currently uses just some scene files saved in a specific folder for a particular host for which the path is set in the Studio Settings. I would like to propose to refactor this functionality into using published workfile templates instead.
Pros

Workfile templates are versioned and tracked
Workfile templates could then sync automatically via site-sync
Workfile templates could also easily be "loaded manually" to test a specific workfile template.
Additional studio-specific validators could be deployed upon the generation of workfile templates.
The 'loaded' workfile template could containerise into the workfile as a 'loaded container' and thus a publish from the workfile can then also report which template was used to build that workfile due to "input links"

Cons

It'd require a publish instead of just a "drop a file there" which might be trickier to use a single template across multiple projects (unless maybe it'd be possible to load from another project like library loader too)

How would you imagine the implementation of the feature?
In settings instead of defining a path to the file to load you'd instead pass it the asset > subset to load for particular profile.

Note that the API for the workfile builder should still have an interface through which you could import a particular template builder.import_template and also build the current scene builder.populate_scene_placeholders. It's only the automatic "build workfile for current task" feature which would then find the relevant publish and load it from the filepath.
I'd even argue that the current logic is already failing there since you can't just build the current scene in maya using builder.populate_scene_placeholders but require the import_path to have been triggered so a PLACEHOLDER_SET exists. The only workaround for that currently is:
from openpype.hosts.maya.api.workfile_template_builder import MayaTemplateBuilder, PLACEHOLDER_SET
from openpype.pipeline import registered_host

host = registered_host()
builder = MayaTemplateBuilder(host)
if not cmds.objExists(PLACEHOLDER_SET):
    cmds.sets(name=PLACEHOLDER_SET, empty=True)
builder.populate_scene_placeholders(keep_placeholders=False)

Are there any labels you wish to add?

[X] I have added the relevant labels to the enhancement request.

Describe alternatives you've considered:
An alternative would be to, e.g. for maya, publish a maya scene and have the published path set in the studio settings. However it'd disable some of the cons of not loading an actual representation directly (e.g. site sync, etc).
Additional context:
No response
[cuID:OP-6162]

@fabiaserra @tokejepsen @ClementHector @mre7a @friquette - it seems each of you have been involved with the Workfile Builder templates and might have touched, tested or are even using it in production so I was hoping to get your valuable feedback on this issue from your perspectives.

I would like to propose to refactor this functionality into using published workfile templates instead.

It’s a very good idea, it was one of our goals. Today we have a library project that contains all our templates that we publish.

The 'loaded' workfile template could containerise into the workfile as a 'loaded container' and thus a publish from the workfile can then also report which template was used to build that workfile due to "input links"

Can you expand that?

It'd require a publish instead of just a "drop a file there" which might be trickier to use a single template across multiple projects (unless maybe it'd be possible to load from another project like library loader too)

Since we use the templates of a library project, we should be able to do so. Otherwise it means that we should publish them with each project.
I see another constraint, the ability to stay on a specific version of publish rather than always the latest version.
I speak for @mre7a and @friquette, because we have the same objective, and we’re working together on that part.

Can you expand that?

Like any loaded publish it would then just show up as a loaded container in the manager. The publishing system tends to link the containers returned by ``host.ls()orhost.get_containers()` with the resulting workfile publish which could help track through links in the database what template version was used.

I see another constraint, the ability to stay on a specific version of publish rather than always the latest version.

Yes - an artist would not want to be warned (or maybe they would want to know?) about a template being outdated if the container would show it as not being the latest version. Good point! Maybe having it persist as data in the scene like that isn't the best solution then.

I would argue that we should at least flag it to the artist, so they can make the best decision for the asset/shot. They might have done nothing to the scene since building it so building with a new version would not be a bother. But I don't think the manager is the right place for flagging this since the artist will most likely follow pipeline workflow and just try to update the template, in which case what happens? Might be safer with a pre-flight validation similar to how the FPS in Maya warns the user when launching.

+1, that's how we had it implemented on my old studio, we didn't implement the logic to update the whole workfile template version as there was too many variables to take into account but if they had created the template using other "smaller" published assets we did allow for them to update those through the scene manager (i.e. the template used a Maya renderSetup that's a versioned asset, if someone updated that, they would be able to pull the update)

I suspect updating loaded content is the only reasonable safe feature to implement too - I just don't see how "rebuilding the workfile" including all local changes but with updated content will ever be a viable route in most DCCs. There's just to many cases where local changes will be lost and you're still basically starting new.

Having loaded content in the scene without being in the manager has already come up before with the look family, where you updating through the manager does not make sense but rather needs a completely new assignment, so similar concepts to rebuilding the workfile from a template.

Having loaded content in the scene without being in the manager has already come up before with the look family, where you updating through the manager does not make sense but rather needs a completely new assignment, so similar concepts to rebuilding the workfile from a template.

unrelated to this discussion but I would expect you should be able to update a look family through the manager, doesn't the update version logic provide ways to keep track of where that look has been assigned so you can re-import the look and re-do the same assignments before the update?

Hi   @BigRoy
In your latest comment, you stated this :
This is now implemented in https://github.com/ynput/OpenPype/pull/5380
But I guess you really intended to wrte this : https://github.com/ynput/OpenPype/pull/5830
5380 vs 5830     😉

5380 vs 5830 😉

Thanks, fixed.

Really like the idea and implementation @BigRoy ! We were also thinking on requiring something along these lines and were thinking on using a Library project to host global scene templates just as a means to query it through OP API and then use them in some utility modules we have written (as opposed to hard-code the path on disk)... but adding support for it on the Loader and the rest of the workfile template workflow would be great


More test cases for 'Seek and Destroy'

Now checks for more arguments, completely emptied arrays and string elements.
Fixes #942

@LumenTeun Thanks!


Make -incremental builds also rebuild all the dependent projects

Updating a lower level library which is used as a compile dependency for other projects requires doing a full rebuild to ensure that the dependent projects compile with the new version of the library.
AFAIK -incremental build only builds parts which are missing. I believe it should rebuild all the dependent projects as well.
I tested this by removing slf4j from build/ and running -incremental. Only slf4j was rebuilt.

Agreed, it would be nice to implement this.

@mkoncek PR that addresses your request is available.
Please test if the new behavior is what you expected.


prepareVariables for root queries?

I'm trying to pass a variable to a root query, like this:
const ServiceQueries = {
  service: () => Relay.QL`query { service(id: $serviceId) }`,
};
// ...
<Route name="editService" path="/service/:serviceId" component={ EditServicePage } queries={ ServiceQueries } />

Problem is, my graphQL schema expects serviceId to be an Int, but react-router-relay is passing it as a String.  is there any way to do something like prepareVariables for the root queries so that I can parseInt(serviceId, 10) before sending the query?

Not really - maybe something in an onEnter hook.
I really just try to do as little as possible in my root query FWIW. I feel like it's easier just to use prepareVariables as needed instead of re-inventing everything at the root level.

K.. sounds like your suggestion is: "nest everything under viewer"

@idris this is now fixed on master - fields like service should definitely be top-level fields (only nest connections under viewer), and you can use prepareParams now to convert the types of params.

Will be released as v0.6.2 in a bit.

Thanks!  I'm getting a weird error on 0.6.2 though, after using prepareParams:
Uncaught Error: Invariant Violation: GraphQLFragmentPointer: Value for the argument to `service` on query `AdminQueries` should be a string, but it was set to `1`. Check that the value is a string.

ಠ_ಠ
Not my fault.
Though note that in general, many style-guide like things like JSON API do suggest that IDs be represented as strings, even if they're logically numbers or something.

Definitely not your fault :) I'll just go back to using a String...

@idris Yeah, Relay expects IDs to be strings

@josephsavona this may be the wrong venue for this, but maybe you can point me in the right direction... Is there any way to just create a nodeID on the front-end, so rather than service(id: $serviceId) I can just use node(id: $serviceNodeId) and not have to add a separate root in my schema?

@idris let's move the discussion to stack overflow or facebook/relay


Is it possible to remove the help line at the top

How can I get rid of the "Press ? for help line at the very top of NERDtree? Thanks!

You just need to find that string on plugin.
autoload/nerdtree.vim:260
that leads to "g:NERDTreeMinimalUI"
NERD_tree.txt:671
so, add this to .vimrc
let NERDTreeMinimalUI=1

to remove it

@albfan Thanks so much :sweat_smile:

On the contrary, .. (up a dir) is also handled by the u and U shortcuts. That means you can go up a level no matter where your cursor is, making that line of text very unimportant.

rightyho

F

This also removes .. (up a dir) which is actually useful

Also can be doing in .vimrc:
let NERDTreeMinimalUI=1


Module maintainers

As Stylix grows larger, we should begin using meta.maintainers or some other method to track people interested in maintaining each individual module.
This could be open to automation for things like review requests.

One problem with meta.maintainers is that the list of possible maintainers is part of nixpkgs, so anyone who hasn't contributed there in the past would have to jump through a few hoops to get their name on the list.

Why not just create stylix-local list of maintainers?

Why not just create stylix-local list of maintainers?

We could overlay or overwrite the meta.maintainers list from Nixpkgs with our meta.maintainers list.
Alternatively, nixos-hardware uses a (fairly incomplete) CODEOWNERS file. Personally, I would prefer to use meta.maintainers.

I agree.
CODEOWNERS only requests a review from someone if they have write permissions on the repository.

Cc: @danth

As Stylix grows larger, we should begin using meta.maintainers or some other method to track people interested in maintaining each individual module.

I suggest following Home Manager's approach of merging the internal maintainers list with Nixpkgs's maintainers list:
https://github.com/nix-community/home-manager/blob/2f607e07f3ac7e53541120536708e824acccfaa8/modules/lib/maintainers.nix
Then meta.maintainers can transparently access lib.maintainers as:
https://github.com/nix-community/home-manager/blob/2f607e07f3ac7e53541120536708e824acccfaa8/modules/programs/git.nix#L100
Considering that this would lift some effort from the Stylix core maintainers, I would be willing to drive this functionality forward.
While the implementation should be fairly easy, getting all the maintainers is not very straight forward. Let me know whether the following process is good, considering that we want to minimize noise commits in danth/master and minimize mass pinging as much as possible:

Create a new danth/stylix-maintainers-init branch.

Implement Home Manager's lib.maintainers framework in danth/stylix-maintainers-init.

Create a new mass-pinging GitHub tracking issue containing a table with the following format, where module maintainers are reasonably hand-picked based on git blame <MODULE>:

Potential Maintainer
Modules

@trueNAHO
/modules/hyprland/hm.nix/modules/nixvim/nixvim.nix/modules/qutebrowser/hm.nix

Anyone willing to become a maintainer should submit a PR to the danth/stylix-maintainers-init branch, which adds themselves as a maintainer to the desired modules. Anyone refusing to become a maintainer, can simply ignore this issue as they will not be added as a maintainer without explicit approval through their own PR.
This phase concludes after 21 days, which likely reaches almost everyone that would become a module maintainer.

Squash merge danth/stylix-maintainers-init as one commit into danth/master and close the previous tracking issue.

New modules must have at least one meta.maintainers maintainer.

If I forget to conclude phase (3) 21 days after its start, feel free to ping me in this issue.
Once @danth approves this process, I will currate the table and initiate phases (1), (2), and (3).

Seems like a good plan.
I would suggest that some time before phase (4), we create a documentation page, so we can link to that page when inviting people to become maintainers. The page should describe:

The syntax for meta.maintainers and the maintainer list
The fact that Nixpkgs maintainers are already defined
The differences in responsibility between module maintainers and the core maintainers

It may also be worthwhile pinging people from the main pull request for stylix-maintainers-init, rather than an issue, to make it more clear where to submit changes during the initialisation phase.


update to FCS 26.0.1 to allow FSAC to update as well

Need to update FCS dependency so that FSAC is able to update the FCS dependency.

Thanks!

Hey! Could you push to nuget so I can flow through the rest of the FCS update?

Package released, it should be online after NuGet does it magic


Parsing multiple operations in a file

Hi @sunli829! Hope you are doing well.
Is there a way we can parse multiple GraphQL operations together from one string input?
for example:
query foo {
  foo
}

query bar {
  bar
}

I wish to parse this query and return two query operations. It seems like parse_query does parse the operations successfully but then fails if more than one is found.

I figured after a little bit of debugging that the queries need a name. Thanks!


Creative usage of selector-replace() in 4-wandering-cubes.scss throws error on libsass 3.5.0.beta.2

This issue was already reported as a problem with compass (#88 ).
Compiling with latest version of node-sass on windows 7 . . .
$ node_modules/.bin/node-sass -v
node-sass       4.5.2   (Wrapper)       [JavaScript]
libsass         3.5.0.beta.2    (Sass Compiler) [C/C++]

generates the following error:
$ node_modules/.bin/node-sass node_modules/angular-base-apps/scss/base.scss > blah.css
{
  "status": 1,
  "file": "[SELECTOR]",
  "line": 1,
  "column": 1,
  "message": "Invalid CSS after \"\": expected selector, was \"\"",
  "formatted": "Error: Invalid CSS after \"\": expected selector, was \"\"\n        on line 1 of [SELECTOR]\n>> \n   ^\n"
}

selector-replace method used in 4-wandering-cubes.scss -> @mixin sk-wandering-cubes-animation(...) expects the $replacement parameter to be non-empty.
  $keyframeName: selector-replace("sk-wanderingCube-" + $width + "-" + $height, ".", "");

Is this code trying to find/replace . inside the $width and $height vars? If so, would a custom find/replace method be a better fit?

@chadbrogan is your app using loading symbols?  If not you can disable the component by setting the following variable in your _settings.scss file to false: https://github.com/base-apps/angular-base-apps/blob/master/scss/_settings.scss#L56
If you want to use the loading symbols, you are free to offer up a PR with the desired changes to make it compile.  This code was taken directly from https://github.com/tobiasahlin/SpinKit, so I don't have an immediate answer for how to fix this issue.

@soumak77 An option for disabling the spinkit module was what I was looking for (it's not used in our app). Thank you.
If anyone else runs into this and needs a very hacky workaround, you can also override the selector-replace method. Again very hacky, but it compiled on my machine:
@function selector-replace($string, $search, $replace: '') {
  $index: str-index($string, $search);

  @if $index {
    @return str-slice($string, 1, $index - 1) + $replace + str-replace(str-slice($string, $index + str-length($search)), $search, $replace);
  }

  @return $string;
}

Thanks god I've found this bug reported here. I would've never found this out by my own!
Though, I still don't really get what's going on here and why do I get that weird [SELECTOR] error


Unable to find asterix cat098 in data items cache

any way to skip the Categories that are not found?

Sure, should be fixed in a minute .. :-)
Thanks for the feedback !


changes for k8s redis

remove sealed secrets
add example-aws-resources
rename yml to yaml files
Update Readme

Liveness probe is disabled for now  due to this issue - https://github.com/datakaveri/iudx-deployment/issues/116. if helm upgrade is done, the redis takes long time to load high amount of keys, if it exists.


Microsoft models freezes on load...

It keeps getting to "Adding 59 Microsoft Models" and then not continuing. in the log you see an error:
At line:17205 char:5
+ ...             $OSBuild = ($WindowsBuildHashTable.Item("$OSBuild")).Spli ...
+                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : InvalidOperation: (:) [], RuntimeException
    + FullyQualifiedErrorId : InvokeMethodOnNull

in the other log you don't see any errors, but it doesn't continue...
- Reading Driver Pack URL - https://raw.githubusercontent.com/maurice-daly/DriverAutomationTool/master/Data/OSDCatalogMicrosoftDriverPack.json	DriverAutomationTool	3/28/2023 8:01:54 AM	16464 (0x4050)
- Filtering models based on Windows 10 build 	DriverAutomationTool	3/28/2023 8:01:54 AM	16464 (0x4050)
- Found 59 Microsoft model driver packs for Windows 10 64 bit	DriverAutomationTool	3/28/2023 8:01:55 AM	16464 (0x4050)

Any thoughts on this? It seems like it hangs because of access, but I can browser to the site no issue.


Copilot fails with jsonrpc-error

Whenever I do copilot-login I get the following error:
Copilot agent started.
[jsonrpc] Server exited with status 1
jsonrpc-request: jsonrpc-error: "request id=1 failed:", (jsonrpc-error-code . -1), (jsonrpc-error-message . "Server died"), (jsonrpc-error-data)
Any tips?

emacs-version is 28.1
node --version is v16.15.1
jsonrpc 1.0.17

copilot-diagnose is the same:
Copilot agent started.
[jsonrpc] Server exited with status 1
jsonrpc-request: jsonrpc-error: "request id=1 failed:", (jsonrpc-error-code . -1), (jsonrpc-error-message . "Server died"), (jsonrpc-error-data)

I figured it out. this is a manual install and I had to change copilot--base-dir

what did you set it to and how?


Genre analysis design review

Mostly done by me, with help from @alice-i-cecile

Be careful with merging this, pings in the PR description are dangerous :D
If it makes it in the commit message this can lead to a lot of notifications in the future.


demo.py

Can you provide a demo to test a single image?

Hi, you can modify the dataset part to receive a single image as input by yourself. I think that would not cost you too much time.

Can you provide a demo to test a single image?

Excuse me，have you made the demo to test a single image？


Faceverification isnt working correctly

[x] intro screen design

missing image
text not aligned correctly
cant click on learn more - should also have link pointer

[x] error screen design - button should be longer (take all width)
[x] always timesout with 30 seconds - i was on slow network settings
[x] during upload if user navigates to another tab it terminates - see if it is because of zoom or something we can prevent?
[x] after upload of facemap it keeps showing progress bar until success, the expected behaviour is that it turns into a spinner until result from server
[ ] zoom takes long time load on initial visit

need to preload zoom
this happens on fast network also

[x] faceverification page is empty (ie render returns null). show loadingindicator in middle of page.
[ ] are we gzipping data? make sure so we can support slow networks
[x] user cant leave face verification - if user presses the X on zoom ui he is shown the error screen. he should go back to previous screen
[ ] already enrolled incosistent - i once got success + message that its already enrolled, but now i just success with no message. ** update: **this happens on first time after I delete account so i'm not whitelisted, it shows me the "already enrolled" and later if do FR again if i'm whitelisted it will just show success.
** it should just show success in both cases. **
[x] ** update: we'll think of the correct flow with liav ** user isn't shown failure message. I try to do face verification with a second account, i should be getting a message about duplicate being found in the zoom UI, but i simply get redirect to the error screen (something went wrong on our side).

after upload of facemap it keeps showing progress bar until success - it’s Zoom behavior. we could sent just upload progress (while request is sending). But then verification takes some time on server, but Zoom shows progress bar all this time
There's no way to turn it onto the spinner

There's an option to not display progress while zoom uploads data to server, probably some spinner will be shown - need to investigate this
Also (web only) we could

divide upload progress by 2 (so 0-50% it's uploading)
listen Gun and add 50%/4 = 12.5% for each status change in the session (isLive, isDuplicate, isEnrolled, isWhitelisted)

@sirpy @LiavGut

faceverification page is empty (ie render returns null). show loadingindicator in middle of page.

i need image of the loading indicator to render on the page and to supply it onto ZoomCustomization
or we could try to extract Zoom's loading animation (as no default spinner image provided, i suppose it's CSS animation, so it could be done web-only)

are we gzipping data?

Nope, but it's easy to enable. Just

add compression middleware to the GoodSerever
add { Content-Encoding: gzip, Accept-Encoding: gzip } default axios headers in the DApp. (in src/lib/api/API.js, to the instance working with GoodServer only)

Will be the first thing i'll do tomorrow

@serdiukov-o-nordwhale

we will just keep the progress bar without a custom spinner. can we control the progress of the bar?
for spinner on empty faceverification just use the loading indicator. or any other spinner that we already use (ie in popups)

can we control the progress of the bar?

it's seems while request is sending only
because just after progress reaches 100% Zoom rewinds it to the start then begins slowly increasing until request completes and we'll call .retry() .success() or .cancel()
At this moment we probably loosing control on progress bar. There is a time out for awaiting server response and i suppose here Zoom starts to await for this timeout and show how much time is left using progressbar.
Probably we could do not send 100% once request data was uploaded. Let's try to send 99% max, then send 100% once server returns response and we're ready to call .cancel or .success

Created speparated task about gzipping: https://app.zenhub.com/workspaces/gooddollar-5d50833888a83c6880d3e345/issues/gooddollar/gooddapp/1782

To take control over progress bar we should to pass something to the .uploadProgress()
Then progress bar stops and await till the next .uploadProgress() call and then updates with the new value
So i was able to update progress bar the following way

set 0 at start
set some small value (10%) after some call preparations
set 10-80% during call uploading facemap data
set 100% after call returns response (or throws)

So, after facemap & images was uploaded, progress bar stops on 80% and stucks in this 'almost done' state until server processes verification call. Just after call is processed, progress bar reaches 100%  and we're getting success message


Allow running Scala Steward as GitHub Actions step

That would reduce visibility of how many projects are updated by Steward, but would simplify using it in private repositories.

Could you elaborate what kind of changes this entails? Would Scala Steward need to use a new GitHub API? Is this similar to GitHub Apps? Where would Scala Steward run? On GitHub servers or on your own server for private repos?

Github Actions has a free to use runner(currently bound to listening to 1 repo per runner) you can host on your own server and offers a paid plan to use their runners charged by minutes.  You can configure your repo to use certain runners.  Using a .github/workflows/[workflow-name].yml
https://help.github.com/en/actions/building-actions/about-actions. - according to the documentation it there are Docker container actions and Javascript Actions.

Type
Operating system

Docker container
Linux

JavaScript
Linux, MacOS, Windows

I was just searching for a scala steward github action.

@fthomas I've created a Scala Steward Github Action. It has been placed on a separate repository but I will gladly contribute it to this repository or one under scala-steward-org if you prefer it that way 😸
With this action, anyone can add a new workflow that allows launching Scala Steward on any repository by just adding the following as .github/workflows/scala-steward.yml:
on:
  schedule:
    - cron:  '0 0 * * 0'

jobs:
  scala-steward:
    runs-on: ubuntu-latest
    steps:
      - uses: alejandrohdezma/scala-steward-action@v1
        with:
          github-token: ${{ secrets.ADMIN_GITHUB_TOKEN }}
          gpg-secret-key: ${{ secrets.GPG_SCALA_STEWARD }}

An example of this Github Action being run on a repository can be found here.

This is very interesting, @alejandrohdezma! If you're OK with having it under the scala-steward-org organization, that would be amazing. I'll invite you to the organization, so that you can move it there.
One thing that is unclear to me is if Scala Steward as GitHub Action inevitably means that one Scala Steward instance works only on one repository. One benefit of having one instance running for 1000+ repos is that it only checks for updates of libraries that are used by n repos once in a configured time interval instead of n times. So instead of checking for sbt updates a 1000+ times it does it only once every few hours. It would be great if we wouldn't loose this optimization with GitHub Actions.

The action should be located here now scala-steward-org/scala-steward-action.
Regarding the optimization, maybe we can close this issue and move the conversation as a new issue in the action's repository. What do you think?

Yeah, that makes sense. I'll open an issue in the action's repository.


Fix corner-case off-by-one in RLE sprite unpacking

It's possible that there's enough padding at the end of the data to encode an extra 0 entry if bits_per_pixel is < 7... and one of my sprites in blit kart happens to cause that.
Might be possible to trigger something similar with non-RLE packed data too, but haven't checked.
(Probably wouldn't have caught this if I didn't have ASan enabled!)
=================================================================
==579178==ERROR: AddressSanitizer: heap-buffer-overflow on address 0x62900009a200 at pc 0x555fd9cef633 bp 0x7faffb824ba0 sp 0x7faffb824b90
WRITE of size 1 at 0x62900009a200 thread T3 (Loop)
    #0 0x555fd9cef632 in blit::Surface::load_from_packed(blit::File&, unsigned char*, unsigned long, bool) /home/daftfreak/programs/32blit-beta/32blit/graphics/surface.cpp:710
    #1 0x555fd9ce6548 in blit::Surface::load(blit::packed_image const*, unsigned char*, unsigned long) /home/daftfreak/programs/32blit-beta/32blit/graphics/surface.cpp:70
    #2 0x555fd9c7ffa6 in blit::Surface::load(unsigned char const*) /home/daftfreak/programs/32blit-beta/32blit/graphics/surface.hpp:129
    #3 0x555fd9ca8fd9 in Track::Track(TrackInfo const&) ../track.cpp:147
    #4 0x555fd9cb0844 in TrackSelect::update(unsigned int) ../track-select.cpp:49
    #5 0x555fd9c7347d in Game::update(unsigned int) ../game.cpp:19
    #6 0x555fd9c73691 in update(unsigned int) ../game.cpp:81
    #7 0x555fd9cd37ff in blit::tick(unsigned int) /home/daftfreak/programs/32blit-beta/32blit/engine/engine.cpp:96
    #8 0x555fd9cc5c53 in System::loop() /home/daftfreak/programs/32blit-beta/32blit-sdl/System.cpp:271
    #9 0x555fd9cc572e in System::update_thread() /home/daftfreak/programs/32blit-beta/32blit-sdl/System.cpp:252
    #10 0x555fd9cc3b19 in system_loop_thread /home/daftfreak/programs/32blit-beta/32blit-sdl/System.cpp:139
    #11 0x7fb01c006682 in SDL_RunThread src/thread/SDL_thread.c:275
    #12 0x7fb01c08df8c in RunThread src/thread/pthread/SDL_systhread.c:78
    #13 0x7fb019dd144f in start_thread nptl/pthread_create.c:473
    #14 0x7fb019f08d52 in clone (/lib/x86_64-linux-gnu/libc.so.6+0x117d52)

0x62900009a200 is located 0 bytes to the right of 16384-byte region [0x629000096200,0x62900009a200)
allocated by thread T3 (Loop) here:
    #0 0x7fb01c1be717 in operator new[](unsigned long) ../../../../src/libsanitizer/asan/asan_new_delete.cpp:102
    #1 0x555fd9cef034 in blit::Surface::load_from_packed(blit::File&, unsigned char*, unsigned long, bool) /home/daftfreak/programs/32blit-beta/32blit/graphics/surface.cpp:661
    #2 0x555fd9ce6548 in blit::Surface::load(blit::packed_image const*, unsigned char*, unsigned long) /home/daftfreak/programs/32blit-beta/32blit/graphics/surface.cpp:70
    #3 0x555fd9c7ffa6 in blit::Surface::load(unsigned char const*) /home/daftfreak/programs/32blit-beta/32blit/graphics/surface.hpp:129
    #4 0x555fd9ca8fd9 in Track::Track(TrackInfo const&) ../track.cpp:147
    #5 0x555fd9cb0844 in TrackSelect::update(unsigned int) ../track-select.cpp:49
    #6 0x555fd9c7347d in Game::update(unsigned int) ../game.cpp:19
    #7 0x555fd9c73691 in update(unsigned int) ../game.cpp:81
    #8 0x555fd9cd37ff in blit::tick(unsigned int) /home/daftfreak/programs/32blit-beta/32blit/engine/engine.cpp:96
    #9 0x555fd9cc5c53 in System::loop() /home/daftfreak/programs/32blit-beta/32blit-sdl/System.cpp:271
    #10 0x555fd9cc572e in System::update_thread() /home/daftfreak/programs/32blit-beta/32blit-sdl/System.cpp:252
    #11 0x555fd9cc3b19 in system_loop_thread /home/daftfreak/programs/32blit-beta/32blit-sdl/System.cpp:139
    #12 0x7fb01c006682 in SDL_RunThread src/thread/SDL_thread.c:275

Thread T3 (Loop) created by T0 here:
    #0 0x7fb01c1606d5 in __interceptor_pthread_create ../../../../src/libsanitizer/asan/asan_interceptors.cpp:216
    #1 0x7fb01c08e008 in SDL_SYS_CreateThread src/thread/pthread/SDL_systhread.c:119
...

Ooof, nice catch! Thank you.


Added integration tests for getting blocks.

I added testnet blocks to the mix in a pull request.

the travis build is broken until the pull request with the .travis.yml is merged in.


failed containers with --rm should remove themselves

when starting or running a container that has --rm, if the starting
container fails (like due to an invalid command), the container should
get removed.
Resolves: #1985
Signed-off-by: baude<EMAIL_ADDRESS>

i dont think man pages need to be adjusted.  this is just a parity thing

If we actually support this with start, sure. LGTM

bot, retest this please

@TomSweeneyRedHat @rhatdan @giuseppe @vrothberg Someone else mind dropping an LGTM?

/lgtm

/approve


Add option to set ws protocol

hello daniel,
thanks for you helpful package.
We added the possibility to set the protocol as option parameter.
cheers

Looks good, thanks! :)


adding support for a date-of-death?

Using your David Foster Wallace example, what if you added a date of death, that way it wouldn't show boxes past that date?

Someone had the same thought on Hacker News. I agree it would definitely make sense to include—the only reason I didn't is that it felt too morbid, but maybe that's ok...


admin UI login loop

Deployed admin UI and IDS to staging with SSL (behind traefik reverse proxy), when logging into the admin UI, after the consent screen, the redirect loop starts, it keep bouncing back and forth between signin-oidc and ids until 431 error, which is request header too large. been fighting this for a while, any idea why that happen?
here's the error log
System.Exception: An error was encountered while handling the remote login. ---> System.Net.Http.HttpRequestException: Response status code does not indicate success: 401 (Unauthorized).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.GetUserInformationAsync(OpenIdConnectMessage message, JwtSecurityToken jwt, ClaimsPrincipal principal, AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleRemoteAuthenticateAsync()
--- End of inner exception stack trace ---
at Microsoft.AspNetCore.Authentication.RemoteAuthenticationHandler`1.HandleRequestAsync()
at Microsoft.AspNetCore.Authentication.AuthenticationMiddleware.Invoke(HttpContext context)
at Microsoft.AspNetCore.StaticFiles.StaticFileMiddleware.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.CspMiddleware.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at NWebsec.AspNetCore.Middleware.Middleware.MiddlewareBase.Invoke(HttpContext context)
at Microsoft.AspNetCore.Diagnostics.ExceptionHandlerMiddleware.Invoke(HttpContext context)
System.Net.Http.HttpRequestException: Response status code does not indicate success: 401 (Unauthorized).
at System.Net.Http.HttpResponseMessage.EnsureSuccessStatusCode()
at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.GetUserInformationAsync(OpenIdConnectMessage message, JwtSecurityToken jwt, ClaimsPrincipal principal, AuthenticationProperties properties)
at Microsoft.AspNetCore.Authentication.OpenIdConnect.OpenIdConnectHandler.HandleRemoteAuthenticateAsync()
then after that, the error is:
No access token found.

turns out to be the client secret mismatched for the admin UI client.

Thanks for sharing solution. 👍🏼


Update CONTRIBUTING.md to reflect PR merge process

Thanks @gunan!

Nagging Assignee @yifeif: It has been 14 days with no activity and this issue has an assignee. Please update the label and/or status accordingly.

@yifeif @Androbin just checking that this is ready to go?

Thanks @drpngx. It should be ready now.


Create ema_crossover_compact.py

Example of a compact fully working ema crossover strategy

Closing this PR as this PR is merged https://github.com/algobulls/pyalgostrategypool/pull/25


issue235 - [Feature]: Create Separate url links for login vs signup

Please check the following

[x] Do the tests still pass? (see Run the Tests)
[x] Is the code formatted properly? (see Linting (Formatting))
For New Features:

[x] Have tests been added to cover any new features or fixes?
[x] Has the documentation been updated accordingly?

Please describe additional details for testing this change
There is currently no separate route for signup. So, in order to access the sign-up page, you must access the login page first.
I created a new signup path and modified the Login Signup page as required.
Please let me know if there is anything to be revised.
Thank you!
Target Issue
https://github.com/cuttle-cards/cuttle/issues/235

I checked the test file and found that there was an error, so I modified authentication.spec.js.
I passed the e2e test in my local environment.
I also change the patch version number to 3.4.2
Thank you!

Thanks for the contribution @Jinyoung-s!

My pleasure!


Mismatch between Python pei-x86-64 and MinGW64 ('pei-i386') arches

Nuitka fails to build the executable with MinGW64 on GitHub Actions (Windows Server 2019) due to the following error:

Error, Mismatch between Python pei-x86-64 and MinGW64 ('pei-i386') arches

Here's the full log. You'll notice there's no pyro.exe referenced in the log after the following command is executed.
Arguments:

pipenv run nuitka --standalone pyro --include-package=pyro --experimental=use_pefile --python-flag=no_site --python-flag=nosite --python-for-scons=C:\hostedtoolcache\windows\Python\3.7.5\x64\python.exe --assume-yes-for-downloads --plugin-enable=multiprocessing --show-progress --file-reference-choice=runtime --mingw64

Other info:

GitHub pre-installs MinGW64 via chocolatey using choco install mingw.
choco install mingw installs MinGW-w64 8.1.0.

The mismatch appears to be real. You seem to ignore the error exit from Nuitka, never a wise thing.
You need the Python and MinGW64 arches to match.  From the link you gave, it looks like the MinGW installed is 32 bits, and thus not usable for 64 bits Python. Either change to x86 Python or x64 MinGW.

Huh, I tried choco install mingw locally. It looks like choco installs both arches, so there must be an environment variable that needs to be set in a GitHub Actions build script to select the x64 arch. Thanks.

Same happened to me under Windows, the arch reported for mingw64 is None when installing the compiler with conda and i386 via the windows installer. Could not bring it to work unfortunately.
VIA CONDA
mingw64 installation was made using miniconda  : conda install m2w64-gcc libpython . The CC env variable was defined by CC=C:\Users\xxx.conda\envs\yyy\Library\mingw-w64\bin\gcc.exe .

Error, mismatch between Python binary ('C:\Users\xxx.conda\envs\yyy\python.exe' -> 'pei-x86-64')
and C compiler ('C:\Users\xxx.conda\envs\yyy\Library\mingw-w64\bin\gcc.exe' -> 'None') arches.

Also tried linking: x86_64-w64-mingw32-gcc.exe instead of gcc.exe, with same error message. Plateform is Windows with python 3.8.5. gcc works well in command window and whereis gcc shows the right version.
VIA WINDOWS INSTALLER
Downloaded from https://sourceforge.net/projects/mingw-w64/files/mingw-w64/, installed for version 7.3.0 with x86_v64 and adjusted CC environment variable. Error message:

Error, mismatch between Python binary ('C:\Users\xxx.conda\envs\yyy\python.exe' -> 'pei-x86-64') and C compiler ('C:\Program Files (x86)\mingw-w64\i686-7.3.0-posix-dwarf-rt_v5-rev0\mingw32\bin\gcc.exe' -> 'pei-i386') arches.


Feature: calibration error estimators

While implementations of standard metrics are scattered, this is certainly the case for L^p calibration error estimators.
Why is it important to measure model calibration?
When fine-tuning a model with cross-entropy loss (or any other strictly proper loss optimizing both accuracy and calibration) there is no guarantee that your model will turn out well-calibrated. Empirically, large NNs were shown to "overfit" on accuracy, leading to sub-optimal calibration.
Additionally, binned estimators typically require setting some arguments such as the binning scheme (equal-range/equal-mass/...), number of bins, and the p-norm. More advanced settings include debiasing ([1] Kumar et al. 2019) or the proxy used for average bin probability (bin center or bin left/right edge).
This library might provide the right standardization and documentation on which arguments are important and how they impact estimation and comparisons.
Without complicating matters from the start, it might already be nice to have a simple calibration error estimator along the lines of ECE ([2] Guo et al. 2017), which (despite some flaws and differing implementations) is commonly used to report top-1 miscalibration.  Some "reasonable" defaults are equal-range binning with 15 bins and p-norm 1, to be discussed :).
With regards to the implementation, there is a clean way to create a hashmap of unique bin assignments which keeps running averages of the conditional expectation and average bin probabilities. In the future, the hashmap can even be created on the validation set and when evaluating on the test set retrieves values by the hash, resulting in unbiased estimates.
I would very much appreciate a discussion on this so that the community is aligned on the approach.
Over the weekend, I will get my hands dirty for a first PR, maybe better to discuss it there :)
First functional code dump here: https://huggingface.co/spaces/jordyvl/ece
[1] Kumar, A., Liang, P.S. and Ma, T., 2019. Verified uncertainty calibration. Advances in Neural Information Processing Systems, 32.
[2]  Guo, C., Pleiss, G., Sun, Y. and Weinberger, K.Q., 2017, July. On calibration of modern neural networks. In International Conference on Machine Learning (pp. 1321-1330). PMLR.

Hi @Jordy-VL that sounds like an interesting addition! Let me know if you need any help with setting up a custom metric. It will be indeed simpler to discuss on a PR.

Hi @lvwerra, I created the first proof of concept demo here (run locally for now).
The space allows calculating ECE with sliders and dropdowns for varying keyword arguments to _compute.
Currently, it gives both the metric and a reliability plot that renders dynamically:

I have not yet touched the evaluate/utils/gradio.py file, but in order to create this demo with the original code, launch_module] needs to accept both new inputs, outputs, function`. I do not know if you would rather want to keep this clean or allow for extensions :)

Closing this for now as the discussion is continuing on hf.co.


docs: fix the incorrect ref file path in the DEPLOY.md

Description
To fix this error
404 - page not found The main branch of kelemetry does not contain the path `docs/charts/kelemetry/values.yaml`

Related issues

Special notes for your reviewer:

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Give user feedback when save is complete.

Use a method similar to the example in https://developer.chrome.com/extensions/options.
Change the button text from Save -> Options saved. for 750ms, then back.

Landed with small tweaks in d1f0dd3b58ab2a6ea1357723132c7eeaa9fc3db3. Thanks!


Is it possible to change the position of the chat output in mpv?

If not, would it be possible to add that as an option in the future?

Yes, it is possible - it is just not obvious how to do so.
As https://syncplay.pl/guide/client/ states:

There are a number of settings which can be changed by modifying the syncplay.ini / .syncplay file. If your change breaks something then you can just delete the entry to restore it to the default, but you might still want to make a backup of your configuration file before making changes. You can figure out what these do by searching for the setting name in the Syncplay source code.
[GUI] options relating to mpv OSD and chat input:
Numeric: chatMaxLines, chatTopMargin, chatLeftMargin, chatBottomMargin, chatOSDMargin, notificationTimeout, alertTimeout, chatTimeout
Boolean (True/False): chatMoveOSD

If you increase the value of chatTopMargin in syncplay.ini it will move the chat further down the mpv window.
If you reduce the value of chatMaxLines in syncplay.ini it will make the output more compact because it won't display as many lines at once.
(From the GUI configuration chat tab you can also change the output style from 'chatroom style' to 'scrolling style', but I'm guessing that is not what you are interested in doing.)

Thank you, I just wanted to move it down.
And I guess I have one more question...Is it possible to make messages appear bottom-top, instead of top-bottom?

I've just done some experimentation, and one way to do that is to modify the \Syncplay\resources\syncplayintf.lua file.
Specifically, you need to change line 170 to:

  		chat_ass = to_add .. chat_ass

If you want the chat output to move upwards as well, you will need to change line 263 to:

  		local ypos = opts['chatTopMargin'] - (#chat_log * 24 * FONT_SIZE_MULTIPLIER)

Note:

The number 24 represents the default font size. If you have a larger different font size then you will need to change this number accordingly.
You will need to re-implement this change whenever you update Syncplay.
If you have Syncplay installed to Program Files then you may need to run your text editor in Administrator mode to be able to modify the file.

Not quite what I had in mind :sweat_smile:. I'm sorry, my explanation wasn't very good.
I was thinking more like how traditional chat works: the new message appears just above the input field, and then the new one pushes the previous message one line above it. So like the chat in the Syncplay window.
But in all honesty, it's not a big deal at all. It's a very minor detail. Thank you for your time. I appreciate your help. I've been using Syncplay for a few days now, and it's awesome.


How to integrate with Laravel artisan server?

@tacnoman 👍

There is an explanation how to in this link: http://dephpugger.com/Configuration/Laravel_Framework.html
You must create a file called .dephpugger.yml in root folder and instead of start server with artisan CLI, you must start with dephpugger, running:
$ dephpugger server


Says CL_OUT_OF_RESOURCES when rendering for second time.

i am having the OpenCL driver API error (code: -5, file:D:\a\1\Luxcore\src\luxrays\devices\ocldevice.cpp, line: 321): CL_OUT_OF_RESOURCES when i render for a second time or change the engine back and forth between PATHOCL and PATHCPU. this is happening too in the blendluxcore implementation.
Bug Replicating Procedure:
Render with the PATHCPU for a time then change the engine to PATHOCL and change it again.
Hardware:
Intel Celeron N4000 @1.10GHZ (dual core)
Intel UHD Graphics 600 (supports opencl 1.2 neo)
Ram: 4gb
Software:
Windows 10 Pro Education 2001
Thanks!

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Intel UHD Graphics 600, is a very limited GPU compared to high-end NVIDIA/AMD for computing task. The Intel OpenCL drivers have been also unable to run any complex code for years (probably because the underlaying hardware is just too limited).
I assume the driver throw a CL_OUT_OF_RESOURCES because it is simply running out of memory/resources/etc.
Does LuxMark work on the same hardware ?

Intel UHD Graphics 600, is a very limited GPU compared to high-end NVIDIA/AMD for computing task. The Intel OpenCL drivers have been also unable to run any complex code for years (probably because the underlaying hardware is just too limited).
I assume the driver throw a CL_OUT_OF_RESOURCES because it is simply running out of memory/resources/etc.
Does LuxMark work on the same hardware ?

I'm going to try, cuz I actually rendered some things but immediately after it opened. But if I rendered a image and I try to render ir again it says that. Thanks for your response

I'm going to try, cuz I actually rendered some things but immediately after it opened. But if I rendered a image and I try to render ir again it says that. Thanks for your response

I rendered this with the GPU+CPU, 256 samples and 20 min render time.

I rendered this with the GPU+CPU, 256 samples and 20 min render time.

Maybe its a bug in the intel driver and not on luxcore OCL.

Maybe its a bug in the intel driver and not on luxcore OCL.

It Works perfectly but with a low score Dade916

It Works perfectly but with a low score Dade916


feat: allow list of files in exclude option

Closes https://github.com/evilmartians/lefthook/issues/717
:zap: Summary

[x] Allow using a list of files in the exclude option
[x] Support regexp too
[x] Update docs
[x] Add integration tests

I am going to release this PR tomorrow with a new lefthook version 1.7.3


Native ESM support

Hi all, I know this is a massive PR and so I'm not necessarily expecting you'll want to merge it but I thought it might be worth pointing out to those who might be interested (https://github.com/Leaflet/Leaflet/issues/8352).

In its current state, Leaflet is REALLY close to working out of the box without any bundling via import * as L from '/node_modules/leaflet/src/Leaflet.js' or even just import * as L from 'leaflet' with an import-map. Personally, I find not having to mess with build tooling makes the development experience just that much more magical. All that's needed is to import real file names (use .js extension) and avoid attempting to import JSON files (which are not ES modules).

Hi @jessetane, we're definitely interested in landing as close as possible support for ESM without the need for bundling. Part of this is adding the .js extensions. Before we land something like this I'd like to enforce this like a configuration for Rollup and ESLint rules, could you look into that?

I'm not super familiar with eslint but it looks like this plugin https://github.com/import-js/eslint-plugin-import/blob/main/docs/rules/extensions.md does what you want, see 0376e85

Oops, that got a little weird due to package-lock being checked in... if you want the lockfile change in a commit I can send it, just lmk

@jonkoops I saw https://github.com/Leaflet/Leaflet/pull/8838 and realized a file server is necessary to demonstrate "native" module loading as I was describing. I just pushed two more commits here as an example.

Happy to trim this PR down if any of the particular commits are useful to you - sounds like just 72da14e and 8a5d712 at this point? Like I say this was mostly about bringing the topic up for discussion!

Yeah, that should pretty much cover it. Thanks @jessetane!

rebased

Thanks @jessetane!


Bin IItemHandler

Adds support for ItemHandler capability, exposing the stored items as a 1 slot inventory.
Like the DSU interface I left it as non-sided, and added simulate parameters to the add/remove functions, in order to not duplicate functionality.
Subclass was used because getStackInSlot works differently.
Benefits: things like AE2 & Refined Storage should be able to work with bins without any external dependencies.

Oh my God thank you!
I wanted to use bins to mass store ingots and such in my RS system but was disappointed that they don't support storage busses.

Lovely PR, thank you very much.


add idea and vscode directory to .gitignore

VScode (rust-analyzer) and Jetbrain IDEs (intellij-rust) are popular development tools in Rust community, and maybe we should exclude .idea and .vscode from eyes of git, since mostly, we should not commit them to the repository.
For myself, there are still other ways to bypass, like global .gitignore file, but it results in duplicate works to other coder.

@DCjanus although it works, I suggest you configure gitignore globally for your local env, which includes:
# $HOME/.gitconfig
[core]
  excludesfile = <path-to-home>/.gitignore

# $HOME/.gitignore
.idea/
.vscode/

The project is possible to share some common config, especially for vscode. Also setting up this config prevent yourself from this issue on other projects.

@tisonkun

I suggest you configure gitignore globally for your local env
Actual I did this on my most devices, but recently got a new laptop and meet this.

The project is possible to share some common config, especially for vscode.
Feel sorry for this, I should discuss with others before open a PR.


fix: Build csv2arrow, csv2parquet, json2arrow and json2parquet from just one codebase

This tool and its companion json2parquet really fill an important niche, thank you so much for figuring this out!  I'd been wanting to try and write this, but been daunted by Rust.
I did however look at the repos, noted all the code duplication, and that didn't sit right with me, so I sat down and stared at unfamiliar Rust error messages for a couple of hours to see if I could figure out a way of making the meat of the code more generic and thus build both executables from the same codebase.  And somehow I did manage to get something working!  There's likely a better way of doing this, but hopefully this at lest serves as a working example.

Ah, I didn't notice at first that there's also a csv2arrow and a json2arrow repo.  I just went ahead and genericized the output format as well, now the PR builds all four tools from the same codebase.

Thank you for your pull request. I am generally very supportive of this effort to combine the repos. I also noticed that I spend a lot of effort redoing work across repos. However, I think it's nice to have separate crates. Would you have an idea for how we could still have separate crates? One option I could imagine is having a single repo with folders for each crate that then use a common shared library. Thoughts?

@domoritz Not something I have much experience with yet. Your ideas on how to achieve that are likely as good as mine.
I will say that one reason I looked into this is because I'm bundling both csv2parquet and json2parquet into a Docker image, and having the separate crates means double of an already very long build time: 19 minutes in GitHub Actions for a multi-architecture build that cross-compiles both Intel and ARM64. Cargo doesn't reuse work within the two same-platform crate compilations; Cargo's docs recommend using this tool called sccache to improve it, but I tried it, it didn't work for me, and then I noticed its docs say it doesn't work with bin crates.

Can you download the builds from GitHub releases? That would be much faster.

closing since we need a different setup


Csslint does not recognize CSS Grid Tags ATOM

does a newer version of csslint recognize CSS Grid Tags?


Add ForwardConfig and fix Subnet/SecurityGroup references

Description of changes:

Add ForwardConfig.TargetGroups.TargetGroupARN references
Update Subnet/SecurityGroup references to point to the resource ID instead of the AWS ARN

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/lgtm


Ordering fields in nested forms

I need to order dynamically added fields on a nested form and finding that the order field is not working within the nested form field options. I wonder if this option can only be specified at the top-level or if I am doing something wrong?
My form configuration looks kinda like this:
let room_fields = t.struct({
  room_size: t.Num
});

if(room.working_heat){
  room_fields = room_fields.extend({
    heat_controlled: t.Bool
  })
}
let Page4 = t.struct({
  // other fields here
  room: room_fields
});

let Page4Options = {
  fields: {
    room: {
      order: ["heat_controlled", "room_size"]
      // ....
    }
  }
}

I wonder if this option can only be specified at the top-level

No, and after a test it does work for me. What do you see in the UI?

In the UI, the order is maintained until I remove the template function:
template: function(locals){
  return <div>
    {React.addons.createFragment(locals.inputs)}
  </div>
}

Only then the order property becomes effective.

Hm, actually, that wasn't a factor. It just doesn't work.

No, wait, it was a factor. Yes, the template function is overriding the order property.

so you are using a custom template...
now it's clear what's happening: in locals.order you'll find your ["heat_controlled", "room_size"] array.
If you write a template is up to you to code the features provided by the default templates (in this case ordering).

Makes sense. Let me see what I can do with that.

The more I work with this library, the more impressed I become. I just wanted to say thank you @gcanti for building this beauty.

I spent countless hours writing this library, what you are saying means a lot to me. Thanks


Create special number.c

What does the program do ?
A number is special if it is possible to remove some digits from it to get a number having 3, 5 or 6 only.
For example, 38597 is special since it is possible to remove digits 8, 9, 7 to get 35. You cannot remove all the digits.
You can remove digits from left, right or middle.
Write a program in C which given a number N, calculate how many divisors of N are special
Input:
An integer N
Output:
Output in a single line the number of divisors which are special.
Constraints:
1 <= N <= 109
In what programming language it is written?
C

Thank you for participating  in hacktoberfest ❣ if you liked working on this repo you can share it with friends and star this project for helping others


Some custom element tests are failing when compiled using dartdevc

I don't know exactly what's going on, but I'm leaving a bug here mainly to reference it in the status file. Here's what I see:

The test calls document.registerElement().
That eventually calls _registerCustomElement() in the SDK.
That calls _interceptors.findInterceptorConstructorForType(type) for the given class.
That returns null.
_registerCustomElement() throws an ArgumentError.

FWIW, these aren't used. So I'd keep this priority pretty low (even post Dart 2 is fine)

Yup, that's the plan. Filing the bug so I can forget about it and make it future-Bob's problem. :)

I think this is covered by https://github.com/dart-lang/sdk/issues/27311


Add npm run help to show some info

This is yet-another-feature that nobody asked for, but I felt was necessary to help new devs, and sometimes me.
npm run help gives the following output:
npm run ...
-----------

lint                     Lint and fix js files.

list-sources             List the SourceIDs for all sources.
                         SEE: docs/getting_started.md/Source IDs

migrate                  Publish cache items that have been migrated with coronadatascraper/tools/generate-v1-cache.js to AWS.

start                    Start the sandbox.

test                     Run all unit and integration tests.
                         SEE: docs/testing.md

test:integration         Run integration tests.  Set TEST_ALL or TEST_ONLY env vars to change behaviour
                         EXAMPLES:
                         To run tests for all sources:
                         TEST_ALL=1 npm run test:integration
                         To run tests for selected sources:
                         TEST_ONLY=gb-sct,gb-eng npm run test:integration
                         SEE: docs/testing

test:unit                Run unit tests.
                         SEE: docs/testing.md

todos                    List all TODOs, FIXMEs, etc, grouped.
                         SEE: TODO

We can add more by modding the detail in tools/show-help.js.

No strong feels, although 99% of folks shouldn't need anything more than npm run start + npm run test. ¯_(ツ)_/¯

Yep :-)  I get it.    I think that's the last one of these things, everything else is should be much more useful.  I know this is kind of cruft-y.  :-|  But it sure is cute, isn't it.

Merging this, b/c it's totally not necessary for project success.  Apologies to the Cruft Police.


Restarting the Game breaks the Game with pCamera.

Issue description
Hello, on the new version i get this error when restarting my game as Godot Docs recommend:
var simultaneous_scene = preload("res://levels/level2.tscn").instantiate()
func _add_a_scene_manually():
# This is like autoloading the scene, only
# it happens after already loading the main scene.
get_tree().root.add_child(simultaneous_scene)
*The error from pCamera: Attempt to call function 'pcam_removed_from_scene' in base 'previously freed' on a null instance.
I had this error before so I was able to fix it by calling is_instance_valid() on an old version of the addon and also queue_free() all the pcamera system. (I guess ill jump back to previous pCamera releases for now) 👍
*Also testing the pixel_perfect camera feature makes my game camera to jitter in a bad way. I managed to get some information and its mostly because im zooming out at Vector2(0.4,0.4) >>also i was able to find that this is a known issue in godot since snap to pixel on settings makes tilemaps not to jitter anymore, but it creates some jitter on the camera itself. So the best is to keep the camera without zooming out. For sprites i found a pixelPerfect shader that works from a video i saw from HeartBeast. (hope this helps in some way, Anyways thanks a lot for the addon!)
Steps to reproduce
Create a level with the pcamera setup.
Using a hotkey: I send a signal that is catched by Core>>
then Core >> Queue_free the level. and instantiate the same level resulting in the error.
(Optional) Minimal reproduction project
No response

It seems to be working again on the new version after doing this:
    await get_tree().create_timer(0.5).timeout
$PanthomCameras.queue_free()
$Camera2D.queue_free()
Globals.mecha_player.queue_free()
Globals.emit_signal("Level_delete", string)

Testing the pixel_perfect camera feature makes my game camera to jitter in a bad way when switching from a pcamera zoom at Vector2(0.4,0.4) to a pcamera zoom at Vector2(4,4). I managed to get some information and its mostly because im zooming out at Vector2(0.4,0.4) >>also i was able to find that this is a known issue in godot since snap to pixel on settings makes tilemaps not to jitter anymore, but it creates some jitter on the camera itself. So the best is to keep the camera without zooming out. For sprites i found a pixelPerfect shader that works from a video i saw from HeartBeast. (hope this helps in some way, Anyways thanks a lot for the addon!)

Have stumbled upon quite a few known issues with pixel perfection for 2D cameras on Godot's Issue board. Though, am not too sure if there's anything that can be done on an addon side of things. Do you feel that there would be a benefit of having a pixel perfect shader option baked into the addon? The property toggle for the PCam2D merely just forces the Camera2D to never sit in-between pixels and cause smearing, as seen in the examples in PR (#156).

await get_tree().create_timer(0.5).timeout
$PanthomCameras.queue_free()
$Camera2D.queue_free()
Globals.mecha_player.queue_free()
Globals.emit_signal("Level_delete", string)

Is this related to the error you mentioned in this discussion thread?
Tried loading a scene from another using the same method from the docs you mention, but can't replicate that error / crash, so am not sure if I'm doing something different from.
Is there a reason why you're calling queue_free() on the Camera2Dwhen you load a new scene, as opposed to having the Camera2D (+ PCamHost) node always be available on a root node, and then only load scenes containing the map + the PCam2Ds?

The shader that toggles a pixel perfect could be a good idea to implement if its for the entire screen, the solution i have for sprites is a shader for each sprite. As for the reason im queueing free instead of having it on a root node its because I have a simple node that is the root of everything(Core) as a child of it i have a 3D scene then when i start the game im removing the 3D scene then I go to the 2D scene that has the pcameras. It might not trigger at your end because i think it only happens to big scenes that take more time to queue_free. I also have a 2D scene with pcameras for the tutorial.. and when i queue free that scene and come back to the 3D scene(The Hub scene) it doesnt trigger the error. It only happened to me when i was queue free the main 2d Game scene and then instantiating the same level.

De: Marcus Skov @.>
Enviado: lunes, 8 de enero de 2024 3:15 p. m.
Para: ramokz/phantom-camera @.>
Cc: Ciso507 @.>; Author @.>
Asunto: Re: [ramokz/phantom-camera] pixel_perfect camera feature makes my game camera to jitter on Zoom out at Vector2(0.4,0.4) (Issue #165)
Testing the pixel_perfect camera feature makes my game camera to jitter in a bad way when switching from a pcamera zoom at Vector2(0.4,0.4) to a pcamera zoom at Vector2(4,4). I managed to get some information and its mostly because im zooming out at Vector2(0.4,0.4) >>also i was able to find that this is a known issue in godot since snap to pixel on settings makes tilemaps not to jitter anymore, but it creates some jitter on the camera itself. So the best is to keep the camera without zooming out. For sprites i found a pixelPerfect shader that works from a video i saw from HeartBeast. (hope this helps in some way, Anyways thanks a lot for the addon!)
Have stumbled upon quite a few known issues with pixel perfection for 2D cameras on Godot's Issue board. Though, am not too sure if there's anything that can be done on an addon side of things. Do you feel that there would be a benefit of having a pixel perfect shader option baked into the addon? The property toggle for the PCam2D merely just forces the Camera2D to never sit in-between pixels and cause smearing, as seen in the examples in PR (#156https://github.com/ramokz/phantom-camera/pull/156).
await get_tree().create_timer(0.5).timeout
$PanthomCameras.queue_free()
$Camera2D.queue_free()
Globals.mecha_player.queue_free()
Globals.emit_signal("Level_delete", string)
Is this related to the error you mentioned in this discussion threadhttps://github.com/ramokz/phantom-camera/discussions/117#discussioncomment-7624249?
Tried loading a scene from another using the same method from the docs you mention, but can't replicate that error / crash, so am not sure if I'm doing something different from.
Is there a reason why you're calling queue_free() on the Camera2Dwhen you load a new scene, as opposed to having the Camera2D (+ PCamHost) node always be available on a root node, and then only load scenes containing the map + the PCam2Ds?
—
Reply to this email directly, view it on GitHubhttps://github.com/ramokz/phantom-camera/issues/165#issuecomment-1881757070, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ASL6XIBABRYMJJXLKVKFCK3YNRHX5AVCNFSM6AAAAABBQTHIC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBRG42TOMBXGA.
You are receiving this because you authored the thread.Message ID: @.***>

I getcha now.
Is there anything you want to get out of this issue then? Am not too sure what is needed to be solved. Can add a null checker for the PCamHost in the PCam2D/3Ds's _exit() function, but since I can't reproduce that particular issue myself, I don't know if that would help solve the error.

That fixed it, my solution also broke but checking for is_instance_valid in the exit_tree works thanks


support for API Resources?

Is support for Eloquent's API Resources planned? We have models that a) have properties only available after a certain date and b) other properties only available to admin users.
With an API resource, we can just do stuff like:
$return = [
    'id' => $this->id,
    'name' => $this->id,
];

if(auth()->user()->isAdmin) {
    $return['answer'] = 'foo';
}

return $return;

Being able to do this would be spectacular:
return Inertia::render('Model')
    ->with('model', new ModelResource($model);

and this:
return Inertia::render('List')
    ->with('models', new ModelResource::collection(Model::all());

Aaaaaand I should've tried it before writing this up.

Hi @ceejayoz!
Have you somehow managed to how pass pagination data alongside models?

@adriandmitrica I have not. It seems to be added to the resource via the toResponse function, which Inertia doesn’t trigger.
Trying to completely confirm before I embarrass myself again with another issue. 🤪

@adriandmitroca I opened #28 about this.

Good one!

This is weird, in my case $this->links() returns null. Are you returning this within toArray method?

I've added support for "Responsable" props: 2b966ac27964534ee3bbe585b0ea0fff8babb53a
I've tested this with both single resource responses and collection resource responses, and it works great. 👍


Atom panes push left when switching files or panes

Description
When jumping around files or switching between panes, the editor appears to push the whole UI to the left, removing the tree from view as well as text in the left pane.

This does not occur every time, but has been happening more frequently since I first encountered the issue back in January. I've tried restarting and updating/removing packages but can't seem to fix itself. I also had to wipe my computer and start the editor from scratch, and it has been happening before and after wiping my HD.
Steps to Reproduce

Split panes (left or right, doesn't matter)
In your tree view, select another file to view
Observe the UI behavior

alt. steps

Split panes
Select the pane you are not currently in
Observe behavior

Expected behavior:
I should be able to freely switch from pane to pane and/or file to file seamlessly.
Actual behavior:
When trying to open a different file, the UI shifts left, most times making the tree inaccessible.
Reproduces how often:
About every other attempt to open a file. I can usually correct it by trying toggle the tree view or selecting the pane that was affected, but the screenshot above can only be resolved by restarting atom.
Versions
apm  1.18.12
npm  3.10.10
node 6.9.5 x64
atom 1.23.3
python 2.7.10
git 2.14.3

Currently on High Sierra 10.13.3

Thanks for the report - I'm unable to reproduce with both sets of repro steps with Atom 1.24.0 on macOS 10.12.6.  Can you reproduce in safe mode (atom --safe)?

I apologize for such the long response time @rsese - I somehow missed this comment.
I have tried reproducing in safemode, but to be perfectly honest, the issue is so sporadic that when trying to reproduce, I can't, but when not trying, it inhibits my entire workflow. You'll notice I do have the IDE terminal open in the screencapture below, but the problem started happening before I even installed that package.
One other thing to note, I recently had to get a new machine altogether and the problem still persists. Is there any additional information I might be able to provide? For a while the problem corrects itself once I click into the terminal or into the try, but it has since stopped doing that. Additionally, the view is pushing further to the left than it ever has before

I apologize for such the long response time @rsese - I somehow missed this comment.

No problem, thanks for all the details :+1:

Is there any additional information I might be able to provide?

Confirming if the issue is reproducible in safe mode is helpful for us because that lets us know that the issue is unrelated to a community package, but I know it's hard to verify in cases like this where the error is sporadic.  Relatedly, specific steps to reproduce is also something we need to take a look.

I see this problem frequently.  The way to get it out of this problem is by restarting the editor but soon it will go back again.  It might be a combination of plugins and the number of files i manage.

Phew I'm glad someone else has the same problem!! @goodusermf I've actually found that if I either select a new file in my tree (given it's not pushed too far over), or hit return in my IDE terminal, it shifts back. That way I don't have to constantly restart. Sometimes just clicking on another pane helps too

Yes, @mirandashort, it has been a problem for me for sometime.  I have also upgraded my OS from el Capitan to high sierra.  Not sure if that has also an impact.

@goodusermf how long ago did you upgrade? I've been on High Sierra for a while now

The upgrade has been for about 3 months.  I kept hitting this problem so frequently that I was ready to switch not notes sadly.  However, I decided to close all my tabs and I realized that it is cause by having too many tabs open.  So when you have too many tabs open and continue opening or switching tabs the shift happens.  I reduced the tabs open and problem goes away.

@goodusermf would you be able to share step-by-step instructions for reproducing?

@goodusermf that's actually really good information. how often are you using split pane though? i seem to have it with happen a lot when i'm using two panes. I also have contemplated going back to sublime...

I use split pane all the time.
How to reproduce the issue:
I manage in average about 50 files open concurrently.

Just open about 50 files and notice the shift happens

I can reproduce with only about 10 open.  It seems to occur once I have enough tabs to go beyond the width of the screen. Now that I know the approximate threshold, I'm no longer constantly about to throw my computer out the window. I keep my tabs at a manageable count and don't encounter the problem anymore! I will admit, though, I would like to be able to have more than 7 tabs open at once... Since I have tree view and minimap enabled, the real estate for tabs is taken up immensely.
If we could have this addressed soon I'd really appreciate it as it is a bit frustrating. Once again, steps to reproduce would be to open up a lot of tabs.

Once again, steps to reproduce would be to open up a lot of tabs.

We're unfortunately still unable to reproduce so what would help is exact step by step instructions to reproduce the behavior.  Based on this new bit of information:

It seems to occur once I have enough tabs to go beyond the width of the screen

This is what I tried with the atom/atom repository:

atom --safe .
Double click the title bar so the Atom window was maximized and spanned the width of my screen
Open enough files so there enough tabs to go beyond the width of the screen.  For this step on my computer, I needed to open 21 files.

At this point the tabs spanned the window and there were enough tabs so that a few tabs were hidden but I didn't see any problem.  I then opened another 20 files so I had 41 tabs open and almost half the tabs weren't visible but wasn't able to reproduce with this setup either.  I did a few other things too like toggling the GitHub package and then splitting panes a couple of times.

Apologies as it was really difficult for me to simplify more the steps to reproduce. I don’t have to do a whole lot for it to happen. My steps are exactly like yours.
I would like to clarify that it can be affected just by window size, not necessarily screen size. It might be worth noting it occurs sometimes after I try to type or click on a pane, but that’s not the behavior every time.
Can you confirm your operating system that you are attempting to reproduce on as well? Once I get back online I can also look through and list all of my packages

Apologies as it was really difficult for me to simplify more the steps to reproduce. I don’t have to do a whole lot for it to happen. My steps are exactly like yours.

No problem, these issues that are hard to reproduce across computers can be tough to pin down :+1:

Can you confirm your operating system that you are attempting to reproduce on as well? Once I get back online I can also look through and list all of my packages

I'm on macOS 10.12.6
Also I realized it sounds like you can reproduce more reliably now than before when the issue was first opened?  If that's the case, can you confirm if running in safe mode so all community packages are disabled still reproduces the issue?

I might have gotten one more piece to the puzzle! I ran in safe mode and was not reproducing, but I did notice that in safe mode, I am able to horizontally scroll the open tabs. When not running safe mode, that ability has been removed. I can still horizontally scroll in tree view whenever the text spans larger than the width of the pane.
With that said, is there anything you can think of that would disable the tab scroll? I feel like it's no coincidence that my window gets shifted to the left whenever I have too many tabs, and i can't get all the tabs without the scroll.

Hmmm that is interesting...my first guess is that it's related to one of your installed packages.  If you don't have a ton of packages, you could disable all packages and then enable them one-by-one until you see the behavior.
Can you share your installed packages list?
apm list --packages --installed

Sure:
`Community Packages (18) /Users/mirandashort/.atom/packages
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>(disabled)
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>(disabled)
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>(disabled)
├──<EMAIL_ADDRESS>├──<EMAIL_ADDRESS>(disabled)
├──<EMAIL_ADDRESS>└──<EMAIL_ADDRESS>I'll give toggling the packages a try tonight when I'm a little freer
@goodusermf can you confirm if you use any of the above packages?


not support % (ring struct)

smiles not support ring struct
not support %
CN1CC2CC3=C(CCC45CC6C(C=C34)C63CCC4(CC67CCC8C9(C)CCCC8%10C(C6CC4CC7%10)N(C)C9)OC53)C(C)(C2)C1,

I believe the error stems from here:
https://github.com/ECRL/GraphChem/blob/master/graphchem/utils/smiles.py
The custom SMILES parser does not currently recognize the "%" symbol. Additional conditional and logic statements within the parsing loop should enable the correct interpretation of this character.

I believe this is fixed as of https://github.com/ecrl/graphchem/pull/7, now on Master branch with version (Git and PyPI) 1.1.0.


connResertException

Is there an existing issue for this?

[X] I have checked for existing issues https://github.com/getsentry/profiling-node/issues
[X] I have reviewed the documentation https://docs.sentry.io/
[X] I am using the latest SDK release https://github.com/getsentry/profiling-node/releases

How do you use Sentry?
Sentry Saas (sentry.io)
SDK Version
0.2.2
Link to Sentry event
No response
What environment is your node script running in?
https://github.com/getsentry/sentry/issues/46307
How is your code deployed and bundled?
https://github.com/getsentry/sentry/issues/46307
Steps to Reproduce
https://github.com/getsentry/sentry/issues/46307
Expected Result
No errors are thrown
Actual Result
exception is throws

@schankam it seems that connection is being closed and the rejection is unhandled. Does that error you linked consistently happen or is it intermittent?

@schankam it seems that connection is being closed and the rejection is unhandled. Does that error you linked consistently happen or is it intermittent?

It seems intermittent - It does not appear as soon as I start the server but it does happen from time to time (let's say several time during an hour)

@schankam we are not seeing any related errors from other customers about this which leads me to think this could be transient or related to your network setup. Can you share more about how you are using the profiling package or possibly a stack trace that might have been collected with this error?

@schankam, we have some users running on google cloud run, and they have not reported any issues to us. Are you using any specific network configurations for your environment that might be causing connections to be reset?

Closing this due to inactivity


Error - typescript, When I use the Office UI Fabric React components

Category

[x] Question
[ ] Typo
[ ] Additional article idea
[ ] Checked items have no spaces between the [] (delete this line)

Question
The similar issue comes up when I do a test by MSFT Documentation ( https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/use-fabric-react-components ) for testing Office UI Fabric React components.  I got the error as the following:

[02:35:12] Finished subtask 'spfx-serve' after 1.24 s
[02:35:12] Starting subtask 'pre-copy'...
[02:35:12] Finished subtask 'pre-copy' after 35 ms
[02:35:12] Starting subtask 'copy-static-assets'...
[02:35:12] Starting subtask 'sass'...
[02:35:15] Server started https://localhost:4321
[02:35:15] LiveReload started on port 35729
[02:35:16] Opening https://localhost:5432/workbench using the default OS app
[02:35:16] Finished subtask 'sass' after 4.3 s
[02:35:16] Starting subtask 'tslint'...
[02:35:19] Starting subtask 'typescript'...
[02:35:19] [typescript] TypeScript version: 2.4.2
Warning: no-duplicate-case rule is deprecated. Replace your usage with the TSLint no-duplicate-switch-case rule.
Warning: valid-typeof rule is deprecated. Replace your usage with the TSLint typeof-compare rule.
[02:35:20] Finished subtask 'copy-static-assets' after 8.48 s
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(31,37): error TS1005: '=' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(33,38): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,46): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,47): error TS1109: Expression expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,48): error TS1109: Expression expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,75): error TS1109: Expression expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,99): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,102): error TS1109: Expression
expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,118): error TS1109: Expression
expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,143): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,151): error TS1128: Declaration or statement expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,159): error TS1005: ',' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(37,49): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(37,50): error TS1109: Expression expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(37,51): error TS1109: Expression expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(37,68): error TS1005: '(' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(37,70): error TS1128: Declaration
or statement expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(52,29): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(52,53): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(52,56): error TS1109: Expression expected.
[02:35:22] Warning - tslint - src\webparts\documentCardExample\components\DocumentCardExample.tsx(27,1): error no-trailing-whitespace: trailing whitespace
[02:35:22] Warning - tslint - src\webparts\documentCardExample\components\DocumentCardExample.tsx(2,1): error no-unused-variable: All imports are unused.
[02:35:22] Warning - tslint - src\webparts\documentCardExample\components\DocumentCardExample.tsx(4,1): error no-unused-variable: All imports are unused.
[02:35:22] Warning - tslint - src\webparts\documentCardExample\components\DocumentCardExample.tsx(25,8): error trailing-comma: Unnecessary trailing comma
[02:35:22] Finished subtask 'tslint' after 5.94 s
[02:35:22] Error - 'typescript' sub task errored after 3.82 s
TypeScript error(s) occurred.
Request: [::1] '/workbench'
Request: '/temp/workbench.html'
Request: '/temp/manifests.js'
Request<EMAIL_ADDRESS>Request<EMAIL_ADDRESS>
package.json:
the line1 error:

Problems loading reference 'https://schemastore.azurewebsites.net/schemas/json/package.json': Unable to load schema from 'https://schemastore.azurewebsites.net/schemas/json/package.json': getaddrinfo EAI_AGAIN schemastore.azurewebsites.net.(768)

{
"name": "documentcardexample-webpart",
"version": "0.0.1",
"private": true,
"main": "lib/index.js",
"engines": {
"node": ">=0.10.0"
},
"scripts": {
"build": "gulp bundle",
"clean": "gulp clean",
"test": "gulp test"
},
"dependencies": {
"react": "15.6.2",
"react-dom": "15.6.2",
"@types/react": "15.6.6",
"@types/react-dom": "15.5.6",
"@microsoft/sp-core-library": "~1.4.0",
"@microsoft/sp-webpart-base": "~1.4.0",
"@microsoft/sp-lodash-subset": "~1.4.0",
"@microsoft/sp-office-ui-fabric-core": "~1.4.0",
"@types/webpack-env": "1.13.1",
"@types/es6-promise": "0.0.33"
},
"resolutions": {
"@types/react": "15.6.6"
},
"devDependencies": {
"@microsoft/sp-build-web": "~1.4.1",
"@microsoft/sp-module-interfaces": "~1.4.1",
"@microsoft/sp-webpart-workbench": "~1.4.1",
"gulp": "~3.9.1",
"@types/chai": "3.4.34",
"@types/mocha": "2.2.38",
"ajv": "~5.2.2"
}
}

To be honest, I have no idea whether or not it is my environment issue or others, recently almost of every sample cannot work properly.
Thanks

Category

[x]  Question
[ ]  Typo
[ ]  Additional article idea
[ ]  Checked items have no spaces between the [] (delete this line)

Question
The similar issue comes up when I do a test by MSFT Documentation ( https://docs.microsoft.com/en-us/sharepoint/dev/spfx/web-parts/get-started/use-fabric-react-components ) for testing Office UI Fabric React components. I got the error as the following:

[02:35:12] Finished subtask 'spfx-serve' after 1.24 s
[02:35:12] Starting subtask 'pre-copy'...
[02:35:12] Finished subtask 'pre-copy' after 35 ms
[02:35:12] Starting subtask 'copy-static-assets'...
[02:35:12] Starting subtask 'sass'...
[02:35:15] Server started https://localhost:4321
[02:35:15] LiveReload started on port 35729
[02:35:16] Opening https://localhost:5432/workbench using the default OS app
[02:35:16] Finished subtask 'sass' after 4.3 s
[02:35:16] Starting subtask 'tslint'...
[02:35:19] Starting subtask 'typescript'...
[02:35:19] [typescript] TypeScript version: 2.4.2
Warning: no-duplicate-case rule is deprecated. Replace your usage with the TSLint no-duplicate-switch-case rule.
Warning: valid-typeof rule is deprecated. Replace your usage with the TSLint typeof-compare rule.
[02:35:20] Finished subtask 'copy-static-assets' after 8.48 s
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(31,37): error TS1005: '=' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(33,38): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,46): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,47): error TS1109: Expression expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,48): error TS1109: Expression expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,75): error TS1109: Expression expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,99): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,102): error TS1109: Expression
expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,118): error TS1109: Expression
expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,143): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,151): error TS1128: Declaration or statement expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(35,159): error TS1005: ',' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(37,49): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(37,50): error TS1109: Expression expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(37,51): error TS1109: Expression expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(37,68): error TS1005: '(' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(37,70): error TS1128: Declaration
or statement expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(52,29): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(52,53): error TS1005: ';' expected.
[02:35:21] Error - typescript - ........\node_modules@types\prop-types\index.d.ts(52,56): error TS1109: Expression expected.
[02:35:22] Warning - tslint - src\webparts\documentCardExample\components\DocumentCardExample.tsx(27,1): error no-trailing-whitespace: trailing whitespace
[02:35:22] Warning - tslint - src\webparts\documentCardExample\components\DocumentCardExample.tsx(2,1): error no-unused-variable: All imports are unused.
[02:35:22] Warning - tslint - src\webparts\documentCardExample\components\DocumentCardExample.tsx(4,1): error no-unused-variable: All imports are unused.
[02:35:22] Warning - tslint - src\webparts\documentCardExample\components\DocumentCardExample.tsx(25,8): error trailing-comma: Unnecessary trailing comma
[02:35:22] Finished subtask 'tslint' after 5.94 s
[02:35:22] Error - 'typescript' sub task errored after 3.82 s
TypeScript error(s) occurred.
Request: [::1] '/workbench'
Request: '/temp/workbench.html'
Request: '/temp/manifests.js'
Request<EMAIL_ADDRESS>Request<EMAIL_ADDRESS>
package.json:
the line1 error:

Problems loading reference 'https://schemastore.azurewebsites.net/schemas/json/package.json': Unable to load schema from 'https://schemastore.azurewebsites.net/schemas/json/package.json': getaddrinfo EAI_AGAIN schemastore.azurewebsites.net.(768)

{
"name": "documentcardexample-webpart",
"version": "0.0.1",
"private": true,
"main": "lib/index.js",
"engines": {
"node": ">=0.10.0"
},
"scripts": {
"build": "gulp bundle",
"clean": "gulp clean",
"test": "gulp test"
},
"dependencies": {
"react": "15.6.2",
"react-dom": "15.6.2",
"@types/react": "15.6.6",
"@types/react-dom": "15.5.6",
"@microsoft/sp-core-library": "~1.4.0",
"@microsoft/sp-webpart-base": "~1.4.0",
"@microsoft/sp-lodash-subset": "~1.4.0",
"@microsoft/sp-office-ui-fabric-core": "~1.4.0",
"@types/webpack-env": "1.13.1",
"@types/es6-promise": "0.0.33"
},
"resolutions": {
"@types/react": "15.6.6"
},
"devDependencies": {
"@microsoft/sp-build-web": "~1.4.1",
"@microsoft/sp-module-interfaces": "~1.4.1",
"@microsoft/sp-webpart-workbench": "~1.4.1",
"gulp": "~3.9.1",
"@types/chai": "3.4.34",
"@types/mocha": "2.2.38",
"ajv": "~5.2.2"
}
}

To be honest, I have no idea whether or not it is my environment issue or others, recently almost of every sample cannot work properly.
Thanks

Workaround: Installed @types/prop-types to match typescript 2.4.2: npm install -D<EMAIL_ADDRESS>


set custom sound on my app isnt work

Im trying to set custom sound on my project when i use this plugin of notification , i have been read aboutn if i set the sound on res/raw and but not work, im test with gmc node and my code on this section is var message = new gcm.Message({       collapseKey: "applice",       delayWhileIdle: true,       timeToLive: 3,       data: {       score: "4x8",     	contents : "http://www.news-magazine.com/world-week/21659772"       },       notification: { 		title: "Hola amigo", 		sound:"custom",     	alert:"true", 		icon: "ic_launcher", 		body: "This is a notification that will be displayed\r\nif your app is in the background." 	}     });
are there some to help me?

You have to provide all the data requested on the template and as it’s about the sound, also provide information about the custom sound, like format, where did you put the file, etc.