Can Bagetter be used as application under Default Web Site IIS

Hi ,
Can Bagetter be used as application under Default Web Site IIS?

Hi, you can absolutely host BaGetter on IIS: https://learn.microsoft.com/aspnet/core/host-and-deploy/iis
If not done already, install the hosting bundle: https://dotnet.microsoft.com/permalink/dotnetcore-current-windows-runtime-bundle-installer
Further installation instructions here: https://learn.microsoft.com/en-us/aspnet/core/host-and-deploy/iis/hosting-bundle?view=aspnetcore-8.0
Then download the zip release of BaGetter, it contains the published application. Extract its contents to a directory of your choice.
If you want it to run on Port 80 and you already have the Default Website in IIS, you can either configure that Default Website to host BaGetter, or delete the default website and create a new one.
To have it host BaGetter, you have to set the physical path to the directory you extracted BaGetter to. The directory should contain many files including BaGetter.dll and a web.config file.
That's it, when you start the IIS website you can now visit it in your browser or use it for NuGet operations.

@mubarak0443 Did you get it to run on IIS? Do you have any more questions about that?


multicluster with different cluster domain not discovering remote services correctly

(NOTE: This is used to report product bugs:
To report a security vulnerability, please visit https://istio.io/about/security-vulnerabilities
To ask questions about how to use Istio, please visit https://discuss.istio.io)
I have a multicluster setup consisting of 3 clusters all within the same mesh. Every cluster has a different cluster domain - cluster.central, cluster.berlin and cluster.munich. Istio version 1.8.1 installed in all clusters with instruction from this link - Multi primary on different networks
In the IstioOperator cluster domain is set.
values:
  global:
    proxy:
      clusterDomain: "  "

Istio Meta DNS capture is true and the east-west gateway have "*.berlin" and "*.munich" added to their respective configs.
Deployed the helloworld/sleep sample in the mesh.
Within the cluster when I do a istioctl proxy-config endpoint I can see that the services are all discovered correctly with the correct cluster domain, but only for the ones within the same cluster.  The services in the other clusters are discovered with the wrong cluster domain.
Expected:
helloworld v1 and v2 deployed in cluster 2 and cluster 3 respectively should be reachable as helloworld.sample.svc.cluster.berlin and helloworld.sample.svc.cluster.munich, but it is discovered as helloworld.sample.svc.cluster.central in the central cluster.
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
Expected behavior
Steps to reproduce the bug
Version (include the output of istioctl version --remote and kubectl version --short and helm version --short if you
istioctl version
client version: 1.8.0
control plane version: 1.8.1
data plane version: 1.8.1 (1 proxies)
kubectl version
Client Version: v1.18.12
Server Version: v1.18.10
How was Istio installed?
IstioOperator

Istio does not respect the dns domain of remote clusters before

In this case, svc httpbin.httpbin.svc.kube-01.local and  httpbin.httpbin.svc.kube-02.local both exists, i think there should be two clusters exist.
one named  outbound|80||httpbin.httpbin.svc.kube-01.local
the other  outbound|80||httpbin.httpbin.svc.kube-02.local

Ignore above, my mistake, istiod is not aware of remote k8s domiansuffix.

Is that a desirable Istio feature? I guess that it would have to be implemented in pilot-discovery, right? Any pointer to relevant code sections would be great. Is there a workaround I can setup? I am thinking that maybe an EnvoyFilter to re-write the endpoints might do the trick.


Do you thinking about supporting Right-To-Left

In the future can we see rtl supporting

Duplicate of #24807 and #28797


game crashes when spraying

used to work, but since game got updated for me it just instantly crashes when trying to spray / tag anything.

will look into tomorrow

fixed by 9913f0fb420fdf4d890aad8dbcf3d5677daa86a3


Out of Memory

Hi there,
I have a pretty interesting use case. We are using the themekit tool to deploy a single theme to multiple stores. We have one "dev" store and 22 public stores. All stores use the same theme and settings from the dev store per the requirements.
We used this tool to deploy to all the stores by manipulating the multiple environments for each store (https://shopify.github.io/themekit/configuration/#config-file).
I am finding that the themekit tool crashes when uploading ~300 files to each store.
Granted this is not an intended use for this tool, I wanted to see what you think about the error I am getting.
What I expected to happen
Upload to (n) stores at the same time.
What actually happened
Error:
runtime: out of memory: cannot allocate 524288-byte block<PHONE_NUMBER> in use)
fatal error: out of memory

runtime stack:
runtime.throw(0x784bd4, 0xd)
	/usr/local/Cellar/go/1.8/libexec/src/runtime/panic.go:596 +0x7c
runtime.largeAlloc(0x7dbf8, 0x448c00, 0x41baacb0)
	/usr/local/Cellar/go/1.8/libexec/src/runtime/malloc.go:797 +0xdb
runtime.mallocgc.func1()
	/usr/local/Cellar/go/1.8/libexec/src/runtime/malloc.go:690 +0x31
runtime.systemstack(0x11006000)
	/usr/local/Cellar/go/1.8/libexec/src/runtime/asm_386.s:337 +0x5e
runtime.mstart()
	/usr/local/Cellar/go/1.8/libexec/src/runtime/proc.go:1132

goroutine 273 [running]:
runtime.systemstack_switch()

Steps to reproduce

Setup deployment for 10+ stores
Upload the theme to these stores
See error? :)

My Environment
OS (including version):
Mac OSX 10.12.6 (16G1036)
Macbook Pro 15inch 2015 16gb ram
Also failing on a AWS Windows Jenkins box, but also fails on macbook so its likely just an issue with total memory.
Themekit version:
ThemeKit 0.7.5 darwin/amd64
Ignore Files(if any):
resources
.gitignore
.DS_Store

resources is a folder we use gulp to build into assets.

Wow! Okay this makes sense because I never anticipated running any of these commands on that many shops concurrently. (Actually when themekit started they weren't event concurrent) This will take quite a while for me to come up with a solution for. I know some fast small wins however I cannot say a single fix will solve this for you. I will get back to you on this soon.

Awesome, I meant this to be more information as what I am doing is quite off the intended purpose. But if it could be improved for odd use cases, great! But no rush. I am going to do batches of uploads to solve my immediate needs.
Thank you!

Hey @gregorskii, please try v0.8.0. It handles loading of local assets a bit better. They only get loaded just before being sent to shopify's servers however this is no limit currently to make sure that too many will get loaded at the same time concurrently. So this may help the problem but not quite fix it yet.


FUJI fresh info page

@digijim change "order online" to a link please
@stephenbwood please edit/alter gray market verbiage

@digijim please mimic verbiage + layout of FUJIfresh page on the Order FUJIfresh page (i.e. replace "Price per Pro Pack*" header with this header and description. Also remove "*Each Pro Pack contains 5 rolls" disclaimer currently below table.)
Available in 120 and 135 Pro Packs
Each pro pack includes 5 rolls of #FUJIfresh 400H film.

Replace camera bag image with Noritsu scanned version


Validate resolver types against field types

Current we don't throw errors in cases like this:
def example() -> str:
    ...

@strawberry.type
class Q:
    x: int = strawberry.field(resolver=example)

We should raise an error when this happens. We should also maybe allow to change the error to a warning, to make it easier to upgrade.
We could also prevent this (maybe as opt-in/out behaviour):
def example():  # missing type
    ...

@strawberry.type
class Q:
    x: int = strawberry.field(resolver=example)

I was looking at this a bit. I think I found the place where introduce the change but looking at this question think can be complicated, especially for complex type annotation... as far I can see there isn't a built-in way to do it.
Did we already have an idea about how to check this? Or there are any Strawberry's objects that can help on this?

The good news is that this is a bit easier because we don't need to interact with raw Python types. You can make use of StrawberryType.__eq__. I think the types should exactly match, (i.e. -> int should not satisfy -> float), so __eq__ should be enough.

That would be a nice strategy, but I was trying to put the check here as the TODO suggest, something like: if field_.type != field_.base_resolver.type: but these two types are not StrawbarryType always, because StrawberryField.type returns both StrawberryType and Type... so the check can fail even if when theoretically they are the same... :(
Any idea? :D

I'm generating some of my resolvers dynamically. I don't define the return type or use Any in this case. If you implement this feature please don't forget this case as a resolver might return the right type at runtime but is unknown at the time it's created.

Maybe can you post here a little example? So we can include in the tests :)

In my code it looks somewhat like that:
def create_resolver(**filter):
    def resolver():
        # XXX In the actual code some DB query or similar is issued.
        return []
    return resolver

@strawberry.type
class Foo:
    bars: List['Bar'] = strawberry.field(resolver=create_resolver(type='bar'))

@strawberry.type
class Bar:
   name: str

In #1449 I added a unit test for that. The PR is about resolvers in different modules, but the test also includes the part of a generic resolver (no type annotation).


Validation tests for project scoped and cluster scoped catalog for testing apps

Added 3 additional test cases and modified one existing one
Modified:
test_rbac_app_project_scope_list_deploy

New:
test_rbac_app_cluster_scope_list_deploy
test_rbac_app_project_scope_delete
test_rbac_app_cluster_scope_delete

Closing this as the tests are covered in another PR.


FR - Add the support for transaction messages/comments/memos with onchain metadata (CIP-0020)

Please implement transaction comment/description/memo field in Daedalus via onchain metadata addon that uses the metadata messaging from CIP-0020 ?
https://github.com/cardano-foundation/CIPs/blob/a39c12079f031da9cf20f58f355d45545072e002/CIP-0020/CIP-0020.md
CardanoCommunityWallet and other tools implemented it already.
Yoroi for example has a MEMO field, but only usage is for internal memos. The transaction message is something other blockchains have implemented. We have the code for that since the Allegra fork. Its a method to just send additional information along with your transaction, like your invoice-number for example when you pay for something. I guess you don't make fiat bank transfers for invoices without any additional data in it (invoice-no, customer-no, etc.). Its the same with crypto transactions. When you are the receiver, it helps you to see what the incoming transactions are for. As a sender, you see in your history what the payment was for. We need this little addon to make it more mainstream imo. Why not cardanoscan? Yes, cardanoscan shows the data, but we are talking normal users here. You want that information in your wallet, not on a platform somewhere else. When you are a company f.e. , and you look at your fiat bank account, you see an incoming transfer with the invoice-no for example, you don't want to just see +$125,00 and than you have to guess what that amount was for, who sent it, etc by reaching out to a special banking website.
The message/comment/memo should be displayed as an additional info right beside the transaction history, as a dropdown, as a field, etc. Maybe leave it as it is with the metadata display, but we need an input field for an outgoing transaction. There is no need for all tools to support multiline input fields, if you just implement a single comment line, that would be cool too for the start. But the possibilities for the normal users are big. Others can even build automated reactions to transactions like that including this little metadata json addon, like automated emails "thx, we received your payment for invoice-no xxxxx".

@gitmachtl thanks for submitting this feature request.
I have put it into our backlog. The product team will take care of prioritizing it and getting it ready for implementation. Thanks for the patience!

Thank you very much, also added some additional implementation thoughts into the CIP. Like hiding the comment first under a "show unmoderated comment" button/drop-down like on the cardano explorer. Or to autoremove/autodelete urls, or really limit the character space to a handful of chars to prevent url/html code inception for example.

CIP-0020 has been approved and merged into master

Any plans on integrating this CIP anytime soon? It would become very handy for a project we are working on.

Is this to me?

Any plans on integrating this CIP anytime soon? It would become very handy for a project we are working on.

Not in the next couple of sprints due to Alonzo and other higher priority work.
I will let you know once it gets scheduled for work.
Thanks for the patience!


#98: Ensure consistency with JacksonScalaModule's Either serialization/deserialization

See related issue: https://github.com/javaslang/javaslang-jackson/compare/master...Diagoras:98?expand=1

Current coverage is 97.24% (diff: 76.66%)

Merging #99 into master will decrease coverage by 1.80%

@@             master        #99   diff @@
==========================================
  Files            28         28
  Lines           422        436    +14
  Methods           0          0
  Messages          0          0
  Branches         85         91     +6
==========================================
+ Hits            418        424     +6
- Misses            2          4     +2
- Partials          2          8     +6

Powered by Codecov. Last update 64045ab...1fea37d

thank you


docs(api) document stats asset info object props

Document asset info added in webpack v4..40.0
Closes #3280

Thanks!


[EN] Feedback for: /web/fundamentals/primers/promises/?hl=en

The link https://developers.google.com/web/fundamentals/primers/promises/_code/story.json is not available as of May, 3rd, 2016.
Thanks!

Merging with #3444


Disk drive not working

Issue description:
When i log on my world the disk drive is not working. You can't see the 3D texture of drives sticking out and it doesn't consume any rf/fe. the items that are on the disks don't show up either.
What happens:
Items don't show up in the grid and the 3D texture doesn't show up as well.
What you expected to happen:
Items should show up in the grid and the texture should appear.
Steps to reproduce:

I changed some options in BetterFPS mod.
Restarted game.
Changed options back to normal.
Restarted game (again)
Played some time.
saved and quited the game.

Version (make sure you are on the latest version before reporting):

Minecraft:1.12.2
Forge:1.12.2-<IP_ADDRESS>47
Refined Storage:1.6.15

Does this issue occur on a server? [yes/no]
no

When you open the disk drive do the disks show 0/0 items?

When you open the disk drive do the disks show 0/0 items?

Yes, it says that. I tried new disks and they work normal. I tried disk manipulator to tranfer items but that didn't work either. Can i somehow get my items back?

This happens when the disk file gets corrupted. Due to poweroutage/taskmanager kill and similar.
The only way to get the disks back is to grab the file from a backup.
Remove all the items from the new disks you made.

Thanks for help. Now i know to always make backups.


Deprecate rows() in SQLResponse and add bucket()

This is a breaking change that requires clients to at least upgrade to a
newer version, but rows() is kept for now to not require
any code changes.
The rowCount and includeTypes setters on the SQLResponse are
removed without deprecation as those are very unlikely to have had any
use.

lgtm


Clarify that all these IE11 bugs have been fixed in IE12

Fixes #2.
Source: @gregwhitworth in https://github.com/philipwalton/flexbugs/issues/2#issuecomment-68826905

I definitely agree that we should say if/when bugs are fixed in upcoming browser versions. The reason I didn't originally do this is I wasn't sure how best to present the information, and it didn't seem immediately pressing since none of the bugs are fixed in released browsers (with the exception of bug 6, which I just added today).
I've thought about it some more and here are my two favorite options:

Similar to what this pull request does, we list any fixes directly next to the affected browser, so it'd look like:

Browsers affected

      Chrome 4-41 (fixed in 42+)
      Internet Explorer 10-11 (fixed 12+)

Or we could add a separate column. I can't decide if this would make it more or less clear:

Browsers affected
Browsers fixed

      Chrome 4-41
      Internet Explorer 10-11 (fixed 12+)

      Chrome 42+
      Internet Explorer 12+

What do you guys think?
If we do option 2, we should probably then move the tracking bugs below "Workaround" under their own heading

I slightly favor (1), but either approach seems fine.

I think I do to. I'll merge this in and then make the minor changes myself.


OCPBUGS-42434: Implement Managed Identity for HCP Components

What this PR does / why we need it:
This PR builds upon:

https://github.com/openshift/hypershift/pull/4811

This PR integrates the Microsoft adapter sidecar containers for the deployments of the following HCP components:

CAPZ
Azure cloud provider
Azure KMS
Control plane operater

Which issue(s) this PR fixes:
Fixes OCPBUGS-42434
Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.
[ ] This change includes docs.
[x] This change includes unit tests.

/close
This is not needed since we are not doing the adapter sidecar container thing now


how to debug main process

I found that "Launch VS Code (Main Process)" has been removed
how to debug main process now?

Simply run the VS Code config and you'll be automatically debugging all processes.

@joaomoreno  I set a breakpoint in the main function, but it does not seem to take effect

I believe you can't debug it that early, right @weinand @connor4312 ?

Yea--in our debug setup, the main process is attached to asynchonrously, so the debugger won't be attached for things that happen early in startup.

so I think the launch script should be reserved？ @joaomoreno  @connor4312

@erasermeng You're right, I've added the Main Process target back.


RFC: Options for building from local source

Users iterating on an app often want to deploy from source on their workstation, without having to manually commit each incremental change to source control or upload to object storage and modify their config YAML to build it.
Some options discussed in the latest Build WG meeting:

Client tooling One possibility would be to produce a CLI for uploading local source to a location supported by Build's existing source options, for example:

$ knative build build.yaml src/

For purposes of illustration, this command would bundle up the contents of src/ and upload them to some pre-configured location (object storage or source control), modify build.yaml to specify source pointing to that location, and kubectl apply it. This is just for illustration and is not intended to be a real proposal for such a command, or a knative CLI in general.

Skaffold is a CLI tool that exists precisely to make tight dev loops on Kubernetes less painful, and is planning to integrate with Knative Build as a build provider very soon. This would support uploading the docker source context to object storage and building it on-cluster, and adding support for incremental source upload as supported by Build today could make this even faster.

This effectively encompasses the CLI tooling described above, but with all the existing featureset and infrastructure that Skaffold has today, including continuous dev deployment.

Inline source: Some FaaS products allow users to specify small chunks of function code directly in the config, e.g.:

source:
  inline:
    index.js: |
      var gcd = function(a, b) {
          if ( ! b) {
              return a;
          }
          return gcd(b, a % b);
      };
steps:
  ...

In this example, inline is a map[string]string containing source contents that should be placed into the /workspace and built according to the steps. This is just for illustration and is not a real proposal for such an API.
The benefit here is that users with very small source don't need to upload that source to object storage or source control in order to build it. The source is stored inside the Build config in etcd.
However, etcd imposes a size limit on objects stored within it, and repeated deployment of source in this fashion might cause problems. Additionally, source stored in this fashion is not versioned (unless the YAML config itself is versioned), so users who find that the last working version they deployed from inline source an hour ago is no longer available, or is hard to recover. Describing complex source trees or many files within YAML is also likely to become a pain.
But, allowing users to describe very simple programs inline in their YAML configs could be useful for small apps, and should at least be considered.

Enabling "live development": Whatever we design and implement, we should make sure not to optimize so heavily for the "deploys-per-minute" case that we make "deploys-per-second" infeasible. That's not to say that live development is an explicit goal of this work at this time, but we shouldn't make it harder to implement later.

For large local source, I suggest creating a temporary nginx (or whatever) pod on the cluster, and just use kubectl cp to upload the source, as I'm doing in CBI: https://github.com/containerbuilding/cbi#https-context
( POC for Skaffold integration using nginx: https://github.com/GoogleContainerTools/skaffold/issues/596 )
Also, for Docker and BuildKit builder, the BuildKit session API could be used for incrementally uploading the source without any extra storage.

Another option would be to integrate with the new proposed knctl to upload source (where + how TBD), then create a build that points to it, and even a configuration that points to that build, for full source-to-service smoothness.

We could call it knctl push! (And I really like the idea)

spitballing a bit, I wonder if we might want to have a Source CRD. This would be a bit similar to the custom source type, but would allow folks to define custom sources, which could include things like blobstores, or even a local volume.
That way, you could do something like:
apiVersion: build.knative.dev/v1alpha1
kind: Build
metadata:
  name: example-build
spec:
  source:
    host-volume:
      path: /my/local/source/code
  step:
    ...

which would let local development happen without an upload. Or
apiVersion: build.knative.dev/v1alpha1
kind: Build
metadata:
  name: example-build
spec:
  source:
    blobstore:
      digest: abcef
  step:
    ...

That'd give lots of flexibility for folks to experiment with nice ways to upload and manage source.
With this, we could easily ship a simple blobstore, blobstore Source and an upload command out of the box for easy experimentation. I'm a bit agnostic as to whether we'd want to do that as just a sample in the docs with nginx as the store and rsync as the upload command (as @AkihiroSuda suggests) or whether we might want to develop a first-class component for source upload/sync with bells and whistles (a la the cf resource_match stuff) as a "batteries included" thing. We could quite plausibly start with the former (just a nice sample in docs) and then think about the latter later?
FWIW I quite like the idea of a knctl push (it's hard to have spent time in cf-land and not like the idea of knctl push), but it seems a little difficult to do it in an unopinionated way, because you need some sort of blobstore there, and push would differ a lot depending on what that looked like. I'm instinctively a little dubious about having knctl end up with too much of an opinionated workflow that assumes a particular store -- it seems to cut against the idea of knative being a set of primitives if we ship too many opinions in the 'core' organisation, and also seems a bit too likely to cut off innovation, particularly here where there's a fair few good options.

spitballing a bit, I wonder if we might want to have a Source CRD.

In my head I've been putting off the idea of implementing a Resource CRD (to go with Pipeline). The logic for running a Concourse resource is pretty simple, providing the logic to inject stuff into /opt/resource/in doesn't strike me as a long way off the beaten path.
The Concourse team have rebasing on Kubernetes as their next major epic on the Runtime track, so we might get this for free.

basic implementation for build from source is in knctl v0.0.4 (https://github.com/cppforlife/knctl/releases/tag/v0.0.4). it looks something like this:
$ knctl deploy \
    --service simple-app \
    --directory=$PWD \
    --service-account serv-acct1 \
    --image index.docker.io/<your-username>/<your-repo> \
    --env SIMPLE_MSG=123

basic implementation (nothing fancy) didnt require any changes to knative. it copies over source into source container of the build (uses CustomSource instead of GitSource) [1] and then signals build to continue on with building [2].
[1] https://github.com/cppforlife/knctl/blob/062a4e46af9fce7d6cb9a378bb930598d50e9ee1/pkg/knctl/build/build_spec.go#L73-L84
[2] https://github.com/cppforlife/knctl/blob/062a4e46af9fce7d6cb9a378bb930598d50e9ee1/pkg/knctl/build/cluster_builder_source.go#L90


Some messages from node extension are not translated

Refs: #42324
Linux

Start with vscode with some non enlish locale
Start debugging, notice the yellow message in debug console:
Debugging with inspector protocol because Node.js v8.8.1 was detected. node --inspect-brk=29536 bin/www

It is not translated. I would expect it to be transalted.
Note that some other things coming from that extension are translated (like the title of the Loaded   Scripts view)

Verified by code review, since this is not yet translated by translators.


Missing ENV_DIR argument to compile script to ensure heroku buildpack api compat

Seems the https://www.pivotaltracker.com/n/projects/966314/stories/70246426 was implemented for DEA but not backported to diego ?
I can't see the ENV_DIR argument to the compile script invocation nor related tests covering this case, or traces of ENV_DIR constant in the code base

Hi, Guillaume,
Thanks for asking about this. Are you sure that story was even implemented on the DEA side? I don't see any references to ENV_DIR in the DEA codebase either, or in Cloud Controller. That story also looks like it was essentially archived, since there are no associated commits in the story activity, and the value was set to 0 points before it was accepted.
Thanks,
Eric

Thanks @ematpl for catching this. True, I did not check deeply on whether this was implemented on DEA. I recall the long vcap-dev@ thread and may be the final decision was to post-pone impl until diego was GA.
Seems important though to strive to provide best heroku buildpack API compatibility and reduce the porting effort for cf buildpack authors when reusing heroku buildpacks leveraging ENV_DIR support.

Do you have any examples of useful buildpacks that cannot be used with CF because they depend on ENV_DIR?

Closing this out. @gberche-orange, if you happen to know of specific examples of buildpacks that would benefit from this support in CF, please feel free to re-open discussion about it.
Thanks,
Eric


AB#291 Feature- buttons

Describe pull-request
Add buttons styling
Solving issue
Add which issue this pull-request solves by adding # plus the number of the issue (for example #123)
Fixes: AB#291
How to test

Check styling in Figma > UI Kit (Global) > Buttons
Check different size and types in storybook options

Screenshots

Additional context
Add any other context about the pull-request here.

When pressing a button in Chrome, both text and icon are moving a couple of px along with that the button container grows in width. This doesn't happen in Safari or Firefix.
Chrome version
Version 88.0.4324.96 (Official Build) (x86_64)
Screenshots

When pressing a button in Chrome, both text and icon are moving a couple of px along with that the button container grows in width. This doesn't happen in Safari or Firefix.
Chrome version
Version 88.0.4324.96 (Official Build) (x86_64)
Screenshots

The flickering on focus is now gone, but when I press the button in Chrome the state first correctly shows 'pressed' state and when released it ends up in 'focused' instead of 'default'. I have to click once again outside the button to make the button return to its default state.

The flickering on focus is now gone, but when I press the button in Chrome the state first correctly shows 'pressed' state and when released it ends up in 'focused' instead of 'default'. I have to click once again outside the button to make the button return to its default state.

The flickering on focus is now gone, but when I press the button in Chrome the state first correctly shows 'pressed' state and when released it ends up in 'focused' instead of 'default'. I have to click once again outside the button to make the button return to its default state.

@niklasros  Yeah, that's browser behavior I think, when we have clicked the button it will change the state to focus instead. So focus state is when user focusing on button by tab or by clicking it.

The flickering on focus is now gone, but when I press the button in Chrome the state first correctly shows 'pressed' state and when released it ends up in 'focused' instead of 'default'. I have to click once again outside the button to make the button return to its default state.

@niklasros  Yeah, that's browser behavior I think, when we have clicked the button it will change the state to focus instead. So focus state is when user focusing on button by tab or by clicking it.


laFix: Small dark mode changes

A couple small dark-mode changes.
This was intended to be a fix for the dark mode issues we've been having but they look like they've been fixed on their own.
Portal PR

Once this is in, it might actually be worth a hotfix


adding missing samplesheets

Hey @deyazoubi ,
I wound three samplesheets in /gpfs/project/projects/spike/Input/SampleSheets that are not yet in the repo. I am adding them with this PR. Hope this is OK for you?
Best
Stefan

I also saw Illumina Raw Data for run 201104_NB552271_0024_AHLT5HBGXG, but could not find a sample sheet. Is this work in progress?

Hi @sjanssen2,
yes, that is ok, you can add them
the run 201104_NB552271_0024_AHLT5HBGXG is under progress


All conditions are full filled except the first one??

Challenge Mutations has an issue.
User Agent is: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_3) AppleWebKit/601.4.4 (KHTML, like Gecko) Version/9.0.3 Safari/601.4.4.
Please describe how to reproduce this issue, and include links to screenshots if possible.
My code:

 function mutation(arr) {
  arr[0] = arr[0].toLowerCase();
  arr[1] = arr[1].toLowerCase();

  var ar = arr[1].split("");
  for(var i = 0; i <arr[1].length;i++){
  if(arr[0].indexOf(ar[i]) >= 0 ){

    return true;
   }

    return false;

  }

}

mutation(["hello", "hey"]);

@sinharajatit your code is not sufficient to complete the challenge. I would walk through your for loop logic carefully and make sure it actually checks all the letters in your string. If you get stuck with a challenge, please first ask questions to the Help Room. Happy coding!

@erictleung Help room was not helpful for the code i have written. They have given me some other logic to solve this challenge which was quite helpful. But i don't know what is the problem with my code. Its is working perfectly for similar kinds of conditions.

sinharajatit: I wrote the same code and have the same issue. Did you ever figure out why this code is insufficient? An explanation of logic and the for loop issue would help me clear this up! Thanks!


Nautobot2: Ip version wording

Environment

Nautobot version (Docker tag too if applicable): next.demo.nautobot.com
Python version: next.demo.nautobot.com
Database platform, version: next.demo.nautobot.com
Middleware(s): next.demo.nautobot.com

Steps to Reproduce

Navigate to https://next.demo.nautobot.com/ipam/prefixes/54882e13-e359-462b-8f57-3dbab7595bc8/
See the wording Ip version

Expected Behavior
Should probably be IP version

Observed Behavior
Seeing Ip version

Duplicate: https://github.com/nautobot/nautobot/issues/4014


Incorporating suggested changes for spare-change, and bug fix for running-balance

Github Issue (if applicable): #678, #691
Trello Link (if applicable): N/A
Forum Link (if applicable): N/A
Explanation of Bugfix/Feature/Enhancement:
Incorporating suggested changes for spare-change:

use ynab.convert(To/From)MilliDollars
Use Ember.run.debounce

Fixed running-balance so that it will update after changing a transaction's date.  Before, it would just be $0.00 until you refreshed the page.
Uncategorized transaction total can be colored red: Uncategorized transactions classified as available(positive/negative/zero).
Recommended Release Notes:
Bug fix for running-balance so that it will update after changing a transaction's date.

Thanks!


Overload resolution: Choosing the wrong overload when arguments involve generic wrappers

TypeScript Version:  2.2.0-dev.20161221
Code
function filter<P extends Q[], Q, R extends Q>(values: P, isR: (value: Q) => value is R): R[];
function filter<R>(values: R[], isValid: (value: R) => boolean): R[];
function filter<P extends Q[], Q, R extends Q>(values: P, isR: (value: Q) => value is R): R[] {
    const result: R[] = [];
    values.forEach(q => {
        if (isR(q)) {
            result.push(q);
        }
    });
    return result;
}

interface Foo<T> {
    foo: T;
}
interface Bar<T> {
    bar: T;
}
type FooBar<T> = Foo<T> | Bar<T>;

const foobars: FooBar<{}>[] = [];

function isFoo<T>(foobar: FooBar<T>): foobar is Foo<T> {
    return 'foo' in foobar;
}
filter(foobars, isFoo).map(foo => foo.foo);

filter<FooBar<{}>[], FooBar<{}>, Foo<{}>>(foobars, isFoo).map(foo => foo.foo);

function isFooObject(foobar: FooBar<{}>): foobar is Foo<{}> {
    return isFoo(foobar);
}
filter(foobars, isFooObject).map(foo => foo.foo);

(also on the Playground)
Expected behavior:
Compiles without error.
Actual behavior:
The first invocation of filter, filter(foobars, isFoo).map(foo => foo.foo);, has an error Property 'foo' does not exist on type 'FooBar<{}>'. The second/less-specific overload of filter is being selected, even though (as the second invocation shows) the first/more-specific overload is valid, and also despite the fact (as shown by the third invocation) the correct overload is chosen when the inferred type does not involve a generic.

I believe this example also gets to the crux of the issue:
interface A<T> {
    _a: T;
}
interface B<T> {
    _b: T;
}
type AorB<T> = A<T> | B<T>;

declare function isA1<T>(input: AorB<T>): input is A<T>;
declare function isA2(input: AorB<{}>): input is A<{}>;

declare function overload<T>(fn: (input: AorB<T>) => input is A<T>);
declare function overload<T>(fn: (input: AorB<T>) => boolean);

overload(isA1); // uses 2nd overload
overload(isA2); // uses 1st

If only one overload is declared, both calls still typecheck correctly (so, both declarations are valid for both isA* functions). If both are present, they use the overloads as commented. I'm not sure what causes them to choose different overloads when both are valid.

Yes, exactly that. There should be some way to control which overload is "preferred" when both are valid, and I had thought that was order (first matching overload is chosen), but it seems like TypeScript is... I dunno, shortcutting and/or getting lazy too early on these evaluations when you don't hint them.

related to https://github.com/Microsoft/TypeScript/issues/9366

I have a similar issue while writing definitions for ohanhi/hyperscript-helpers
After passing a function through a generic wrapper it either choses the last overload or it loses type safety completely, depending on how I write the overloads.
Minimal example:
declare function overload(a: number);
declare function overload(b: string);

interface MyFunction<T> {
    (t: T): any
}

declare function wrap<T>(f: MyFunction<T>): MyFunction<T>

const myFunction = wrap(overload);

myFunction('qwerty'); // OK
myFunction(9000); // error TS2345: Argument of type '9000' is not assignable to parameter of type 'string'

This can be fixed by changing the wrap function to below but I haven't gotten this to work in more generic code.
declare function wrap<F extends MyFunction<T>, T>(f: F): F

Actually, that looks more like a question of higher-kinded types, which is the long-standing issue #1213.

@krryan I'm no expert but it seems to me the problem is in the overloads being ignored.

They are, but more fundamentally, TS has no way of passing around something that can go multiple ways like that. When you pass overload to wrap, TS needs to pick one of the overloads—in this case, it seems, the first. Higher-kinded types might help that situation. And my question, ultimately, doesn't have to do with trying to get TS to maintain that flexibility, it's just about choosing the right one in a situation where I want TS to choose one.

Is this the same issue?
interface Foo {

}

interface Bar extends Foo {
    someFn: (arg: string) => void
}
function myFn(obj: Foo);
function myFn(obj: Bar, arg: string);
function myFn(obj: Foo | Bar, arg?: string) {
    if (arg) {
        obj.someFn(arg);  // ERROR
                          // Property 'someFn' does not exist on type 'Foo'
    }
}

Playground Link: https://www.typescriptlang.org/play/#src=interface Foo {

}

interface Bar extends Foo {
    someFn%3A (arg%3A string) %3D> void
}

function myFn(obj%3A Foo)%3B
function myFn(obj%3A Bar%2C arg%3A string)%3B
function myFn(obj%3A Foo | Bar%2C arg%3F%3A string) {
    if (arg) {
        obj.someFn(arg)%3B
    }
}

@Erikvv I don't think typeguards are going to help benneq. Note that he's testing arg but wants TS to infer something about obj. A typeguard is there answer to the second question regarding a workaround, though.
Anyway, @benneq, your first sniper doesn't work for a few reasons, but none of them are directly related to this. First, TS doesn't support the notion of “entangled” variables, so a test against one is not going to lead to inferences about another. Second, function overloads do very minimal type checking—the overloads have to be at least theoretically compatible with the primary signature, but they are never checked against the function body to see if that is hope they are being used.

Appears to be due to generic inference not using all overloads, which is a known limitation


Update exception to concrete type

What this PR does / why we need it:
In order to leverage the global exception handler, throw a specific type instead of RuntimeException to indicate a resource was not found.
Which issue(s) this PR fixes :
Fixes #FLPATH-342
Change type

[ ] New feature
[x] Bug fix
[x] Unit tests
[ ] Integration tests
[ ] CI
[ ] Documentation
[ ] Auto-generated SDK code

Impacted services

[x] Workflow Service
[ ] Notification Service

Checklist

[x] Subject and description added to both, commit and PR.
[x] Relevant issues have been referenced.

/lgtm


'test' target of Makefile now passes all tests.

Updated license file name to LICENCE in epm.list.in
Swapped %copyright lines so latest is read first.  EPM ignores 2nd and
subsequent %copyright lines.

tweaks to epm.list.in to amend license file name and to put jj copyright definition first.


Python GetPropAsDouble should throw ValueError not RuntimeError

It's just more pythonic.  In the example below, the "ACTIVITY" data is recorded as ">6.87" which cannot be converted into a double:
['ACTIVITY']
'>6.87'
  File "test.py", line 18, in <module>
    print repr(m.GetDoubleProp("ACTIVITY"))
RuntimeError: boost::bad_any_cast: failed conversion using boost::any_cast

I'm also going to fix the following bug:
https://github.com/rdkit/rdkit/blob/master/Code/GraphMol/Wrap/props.hpp#L52
should return true not false :)
I'm surprised I didn't notice this, bad regression test choices...

This is now resolved.


fix: Pfe jump links

I fixed the offset attribute to actually change. It was kind of working before, but not reliably and I hunted down the bug. Now you can adjust the distance from the top of the window where the link "flips on".

@Djfaucette any reason this was closed instead of merging?


Add minimal TravisCI configuration file

What are you trying to accomplish with this PR?
Closes #30. Adds a minimal TravisCI build config with the latest LTS version of Node.
Example of working build log from my own fork of this repo.
Potential future tasks

Make CI checks (and reviews) mandatory for PR acceptance.
Update PR template checklist to remind contributors to ensure tests/linting are passing.
Add Build Status badge to README.md.
Add code coverage stats to CI process, since Jest automatically generates code coverage information.

Checklist
For contributors:

[x] I have updated the documentation in the README file to reflect these changes, if applicable.

For maintainers:

[ ] I have :tophat:'d these changes.
[ ] I have bumped the package.json version in a separate PR, if applicable.

Hey @t-kelly, I added the caching to the build configuration, but it seems to actually increase the build times. I triggered a few rebuilds on both commits and it seems to be consistently 15-20 seconds longer with caching. Do you think that it still worth adding at this point?

Lol loading the cache takes longer than downloading the dependencies? Sad...
Yep guess its considered a 'premature optimization'. Toss it.
Good stuff. 🚢

Merged and ready for the CI to be activated!


Distutils: Allow slashes in package names

compile_packages should use '.' separators, however setuptools
allows '/', as seen in package websockets.

There is another use of self.compile_packages[0] that might have to be adapted, not sure though, probably compile_packages should be normalized for use in a local variable. I will clean that up later, I intend to make it use multiple commands anyway for multiple packages.


Translation missing

Found this in the logs:
2019-11-12 00:02:40 ERROR n.t.TemplateEngineFreemarkerAssetsAtMethod:128 - Message key Edit Profile missing. Using key as value inside template - but this is most likely not what you want.

Actually, no translation was missing, but a message key was translated twice by accident.


CanJS Library

If you include the CanJS library (currently version 2.0.3) via the `Add library' dropdown the source link that is added to the header generates a 404.
Demo

Looks like they broke their https support: https://canjs.com/release/2.0.3/can.jquery.min.js - can't do anything about that I'm afraid...


NPE on child class

Hello JakeWharton,
i am using butter knife but it gives me NPE on  view .the actual scenario is following...
i have a base activity all other activities extend this base activity .base activity have a frame layout inside it .
all the child activity layout content is dynamically replace inside this frame layout .no oncreate() method call on child activity so when i run this line of code it gives me NPE(Null pointer exception) on any view of child activity when i go for  binding .can you please tell me how to resolve this.

Provide a failing test case or reproduction sample.

Hii JakeWharton ,
I added a sample plz check and let me know the issue.
https://drive.google.com/open?id=0B1VKsHyU8zWuWkFaY2YxRjJoYXc

please update on this

Hi mohittanwar94 ,
I have tested the issue on your provided sample app. I am able to fix it and run the app successfully.
I think the problem is in the app side. Your MainActivity#onCreate method like this.
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);
    ButterKnife.bind(this);
     …………..
    replaceContentLayout(setUILayout(), R.id.container);
    ……........

}
Here before adding the fragment_splash layout in the main layout you are trying to bind it. So it gets NPE. I just reorder the method calls like this
@Override
protected void onCreate(Bundle savedInstanceState) {
    super.onCreate(savedInstanceState);
    setContentView(R.layout.activity_main);
    replaceContentLayout(setUILayout(), R.id.container);
    ButterKnife.bind(this);
     …………..

}
and it’s run successfully.

What @zakir01913 said. Butter Knife calls findViewById so ensure you view hierarchy is fully set up or bind to multiple objects for partial binding.


JSP Converter - Better c:forEach support

When converting this JSP code into JTE:
<c:forEach var="i" begin="1" end="10" >
   ${i} = ${item}
</c:forEach>

I get
@for(var i : ???)
   ${i}
@endfor

It should be converted into something like this:
@for(var forEachStatus : ForSupport.of(IntStream.rangeClosed(1, 10).boxed().toList()))
    !{var i = forEachStatus.get();}
    ${i}
@endfor

I think that it would be better to hide ForSupport.of(IntStream... behind some custom method like ForSupport.ofIntList(1, 10).
Note: Stream.toList() was introduced in Java 16 only.
Well, maybe better even this one:
@for(int i = 0; i <= 10; ++i)
    ${i}
@endfor

Note <=: JSP c:forEach's end is inclusive.
Although I'm afraid it will be hard to convert this Kotlin since Kotlin doesn't have this kind of for loops (will have to use ranges, like @for(i in 0..10)).

Proper support for all forEach cases is hard. Right now that conversion needs to be done by hand.
@for(i in 0..10) works with jte Kotlin templates as far as I know.
But doing a proper conversion of all foreach possibilities is hard, I think. Would be happy about every PR to improve on it. I currently don't have time to work on it on my own.

I'm closing this for now - JSP conversion is a one time thing. Also, forEach isn't that frequent and should be possible to convert manually once.


method to load yaml from a string

cfn-lint version: cfn-lint 0.4.2
Description of issue.
When consuming cfn-lint as a module there is currently only an interface to load yaml from a file(cfnlint.core.decode.cfn_yaml.load). In our project(taskcat) we have a need to load templates from strings as well.
While we could just do something like below, think it would be useful to others to have a simpler interface for yaml strings:
from cfnlint.decode.cfn_yaml import MarkedLoader, multi_constructor
loader.add_multi_constructor('!', multi_constructor)
loader = MarkedLoader(my_yaml_string, None)
template = loader.get_single_data()

Agree, something like cfnlint.core.decode.cfn_yaml.loads would be a nice add


Add reflinks suport to the vfs storage driver

Is this a BUG REPORT or FEATURE REQUEST?:
kind feature
Description
In order to speed up rootless container creation using the vfs storage driver, it could be possible to use reflinks when available, for example over Btrfs or XFS (with reflink enabled format), when creating the container tree. The speed of container creation is one the drawbacks of the vfs driver, since it has to copy the entire tree, with reflinks this could be reduced significantly.

There is nothing that podman needs to do to support XFS Reflink.  This needs to be configured in the underlying storage at storage creation time.  When you create the mount point for your home dir with XFS you need to specify the mkfs that you want to use reflink.  Then when you run podman it will take advantage.  I sent an email to the xfs storage team a while ago to ask them to turn it on reflink by default but they have not up to this point to the best of my knowledge.
I will ping them again.

https://bugzilla.redhat.com/show_bug.cgi?id=1650453

Enabling reflinks in the file system is not enough, we will need to add support for it to containers/storage to try a clone first then do a raw copy.  AFAICS, we are using "copy with tar" for vfs.

is it possible to move this issue to containers/storage (https://blog.github.com/changelog/2018-10-30-issue-transfer/)?  I am not an admin on libpod so I cannot do it


Paimon.moe export not working

Describe the bug
Not sure if this is just on my end but whenever I export achievements to Paimon.moe, I'll get a message saying successful but when I go over to the achievement section there seems to be a lot missing. I should see 994 achievements but I only see 208 achievements on Paimon.moe. I've tried exporting multiple times and exporting using an existing scan as well as not using any existing scans but still have the same results.
I tried using the same scans and exporting to Seelie.me and I'm able to get it to show 995 achievements. I'm getting an extra one somewhere but at least it does seem to work there.

Hi, i have tested on my end and except for those achievements like Pankration Fonta Cup that does not count multiples, everything seems fine


Build error on FreeBSD due to ThorVG (alloca.h)

Godot version
4.0.alpha (ae2d53cd)
System information
FreeBSD 13.0 on Cirrus CI
Issue description
I get a build error on FreeBSD 13.0:
Compiling thirdparty/thorvg/src/loaders/svg/tvgXmlParser.cpp ...
thirdparty/thorvg/src/loaders/svg/tvgXmlParser.cpp:30:14: fatal error: 'alloca.h' file not found
    #include <alloca.h>
             ^~~~~~~~~~
1 error generated.
scons: *** [thirdparty/thorvg/src/loaders/svg/tvgXmlParser.linuxbsd.opt.tools.64.o] Error 1

Full log: https://cirrus-ci.com/task/5485473287110656
CI setup files: https://github.com/Calinou/godot-ci-freebsd
There's another instance of an alloca.h-related build failure on FreeBSD, which occurred a long time ago: https://github.com/godotengine/godot/issues/6238
This issue doesn't affect 3.x as ThorVG is only used on master.
Steps to reproduce

Build Godot's master branch on FreeBSD. You can use Cirrus CI if you don't want to set up a VM locally.

Minimal reproduction project
N/A

Seems the fix is https://github.com/godotengine/godot/pull/17135/files:
#ifdef __linux__
#include <alloca.h>
#include <alloca.h>
#endif
#if defined(__FreeBSD__) || defined(__OpenBSD__)
#include <stdlib.h>
#define PTHREAD_BSD_SET_NAME
#endif


Associated widget which is docked creating a tabbed panels gets disabled if tab is not visible

Currently if I dock my panel on top of another panel creating tabbed panels and then you switched tab it disables the display. Is there a way to disable this functionality?

I believe this a related issue but the issue shows resolved but this still appears to be happening on noetic version.

Tab Selected

Tab Unselected

Then I can enable the display from the tree and the scene is visible and the tab is not which is the behavior expected.

A current work around is to add the following connection enabling the display on any visibility change to the panel.
connect(getAssociatedWidgetPanel(), SIGNAL( visibilityChanged( bool ) ), this, SLOT( onAssociatedPanelVisibilityChange( bool ) ));

void WorkbenchDisplay::onAssociatedPanelVisibilityChange(bool /*visible*/)
{
  setEnabled(true);
}

Well actually that does not work because now the display cannot be disabled.

Finally was able to create a work around.
I first had to disconnect the following signal.
disconnect(getAssociatedWidgetPanel(), SIGNAL( visibilityChanged(bool) ), this, SLOT( associatedPanelVisibilityChange(bool) ));

Then override the onEnableChanged with the following
void WorkbenchDisplay::onEnableChanged()
{
  QApplication::setOverrideCursor(QCursor(Qt::WaitCursor));
  queueRender();
  /* We get here, by two different routes:
   * - First, we might have disabled the display.
   *   In this case we want to close/hide the associated widget.
   *   But there is an exception: tabbed DockWidgets shouldn't be hidden, because then we would loose the
   * tab.
   * - Second, the corresponding widget changed visibility and we got here via
   * associatedPanelVisibilityChange().
   *   In this case, it's usually counterproductive to show/hide the widget here.
   *   Typical cases are: main window was minimized/unminimized, tab was switched.
   */
  if (isEnabled())
  {
    scene_node_->setVisible(true);

    if (getAssociatedWidgetPanel() != nullptr)
    {
      getAssociatedWidgetPanel()->show();
      getAssociatedWidgetPanel()->setEnabled(true);
    }
    else if (getAssociatedWidget() != nullptr)
    {
      getAssociatedWidget()->show();
      getAssociatedWidgetPanel()->setEnabled(true);
    }

    if (isEnabled()) // status might have changed, e.g. if show() failed
      onEnable();
  }
  else
  {
    onDisable();

    if (getAssociatedWidgetPanel() != nullptr)
      getAssociatedWidgetPanel()->setDisabled(true);
    else if (getAssociatedWidget())
      getAssociatedWidget()->setDisabled(true);

    scene_node_->setVisible(false);
  }
  QApplication::restoreOverrideCursor();
}

This just disables the widget opposed to hiding and showing.

There is a simpler solution: #1739.

There is a simpler solution: #1739.

Thanks for the fix.

Sure, it is under a lot of development at the moment. tesseract_gui


macOS_install.sh script for quick installation of dependancies for MacOS

Is your feature request related to a problem? Please describe.
The macOS install script is designed to address the problem of installing the necessary dependencies for the Niffler application on a macOS system quickly and efficiently. Without this script, users may have difficulty installing and configuring the required dependencies.
Describe the solution you'd like
a clear and concise solution would be to create a macOS equivalent script of the already in place install.sh script(which is for linux OS) that automates the installation process of all the necessary dependencies for the Niffler application on macOS. Additionally, it should create and configure the necessary service files (plist files) to ensure that the Niffler application and its components start automatically on system startup. The end result would be a hassle-free and straightforward installation process for Niffler on macOS.
Describe alternatives you've considered
An alternate solution could be a script that wound create an installable package for macOS as discussed here #374

Merged. Thanks.


Added first draft for restriction and presenter interfaces.

Hi, I pushed a new commit for the presenter service. I would like to get the specs for it done, that I can use it in the client. If you can check the presenter, it would be nice. If it is OK, I'll create a new PR with just the presenter interface

I prefer to use an exception also for 4xx like errors so I can throw it anywhere inside the code and do not have to wrap it once again (the same thing as I do in actions service).

First, you can use exceptions in your code if you want to. E.g. when looping through the presenters, each one can throw some exceptions that are collected in the loop and aggregated into an array of (error) responses.
The difference between the exception and errortype was intentional. If the user does something wrong (e.g. wrong input data) in one presenter, another one must not fail and must be executed. All presenters are independend of each other. An exception means that the current control flow is aborted, so if there is an exception in one presenter, all following ones are not executed. I guess we have two options here:

Just do one presenter at a time. Than you can throw exceptions for user errors and "programming errors" (e.g. some other serivce errors and so on).
Stay at error responses per presenter and keep multiple presenters (my favorite).

I am not finished with this but would like to merge this pull request so that we already have a first draft in our docs.


could I please get a private folder reset!

Hi there! Been using keybase for a long long time. I moved computers about a year ago, and borked something with the private folder permissions. I've never bothered to figure out what until now, and now that encrypted repos are out, i'd love to give that a try (and therefore, need access to the private folder again)! Thanks so much!
my log id: 246f5288be99b7d9f0b3221c

Hi @one19, yes I'm happy to reset the folder for you.  But for security reasons, if you want us to reset your folder, please run this command on a currently-valid keybase device, and substitute the current date and time where indicated:
keybase sign -m "<DATE_AND_TIME>: Please reset folder /keybase/private/werd119 because all the devices that have access have been revoked."

and post the results here.

BEGIN KEYBASE SALTPACK SIGNED MESSAGE. kXR7VktZdyH7rvq v5weRa0zkDKtXYZ POJxDc1Uggxv3EO sfOEEkKO1eRyRyN ULpTukHHwDHqasL Aqg9DrxNXswbauk QJGdtJLj94dKHKs 3GY5v44Evt2E3Qy ZafjlcfTCxogalK lFs6rOeZUE0VRz1 M9O6SWE35qNuXeC KpoDSqxj7IBLVWk x5DSqXldXoATqHx pnVrRwre6x3Wqe9 TAWDmDnXxGYKxlm ija9xuOlBODijmX Cs0E7cYP3apAgTl DepPSx6rEciW1I6 oTd0tbkm74V5mpt a17FvYUCw1NavXu qN6KXf8UvHbJwrB SESYEGdDynMcxm7 k4Gq9T7BtM5mCp1 7QrRBhoVFmoCewR fJunDjmN7m. END KEYBASE SALTPACK SIGNED MESSAGE.

sorry for the tardy reply!

I reset the folder.  Please check it out and close this if everything seems ok.  (Might require a Keybase restart.)

yay thank you!


TimeoutError causes promise to be cancelled, not rejected

What version of bluebird is the issue happening on?
3.4.7

What platform and version? (For example Node.js 0.12 or Google Chrome 32)
Node.js 0.12

Did this issue happen with earlier version of bluebird?
Unknown. It couldn't happen in 2.x, I've not tried earlier 3.x versions.

Here's set of commands I ran at coffee's interactive prompt:
coffee> Promise = require("bluebird")
...
coffee> Promise.config({cancellation: true})
...
coffee> p = new Promise((() ->), (() ->))
...
coffee> p.isCancelled()
false
coffee> p.timeout(100)
<timeout fires>
coffee> p.isCancelled()
true
coffee> p.isRejected()
false

Note that nowhere in the documentation of timeout does it mention that the promise will be cancelled.  It explicitly says the promise is rejected, but that appears not to be the case, according to inspection.
I hit this problem originally because I had code that looked like this (and worked as expected in bluebird 2.x):
p = <create promise>
p.timeout(500).catch(Promise.TimeoutError, () ->
    <do some stuff>
    p.timeout(1000)
)

The second p.timeout was failing w/ a CancellationError("late cancellation observer") failure, which confused me to no end because I wasn't explicitly canceling the promise anywhere. It's also very strange that the promise isn't considered rejected, even though it triggered a catch block.
I'm definitely not an expert on the bluebird source code, but this bit of code looks like it could be the source of my confusion (from src/timers.js):
Promise.prototype.timeout = function (ms, message) {
...
    if (debug.cancellation()) {
        parent = this.then();
        ret = parent._then(successClear, failureClear,
                            undefined, handleWrapper, undefined);
        ret._setOnCancel(handleWrapper);
...
};

p is the promise's parent, the promise itself is not cancelled but rejected like the docs say
in 3.0.0 the additional timeout should be done synchronously:
p = <create promise>
var oneSecond = p.timeout(1000);
p.timeout(500).catch(Promise.TimeoutError, () ->
    <do some stuff>
    oneSecond.then(..., ....)
)


Format on save disabled by default

I think this option really causes confusion because every time I save this goes to top.

This is a proposal, I believe it will get better.

The same for me on OS X Yosemite.


Can't read TDWR level 3 .nids files

I'm getting TDWR files from the thredds server
http://thredds.ucar.edu/thredds/catalog/terminal/level3/catalog.html
And can't seem to read in the file using the Level3File class. TDWR files must need to be decoded differently than NEXRAD files??
Get this error:

FILE = 'Level3_SLC_TV0_20150619_0831'
f = Level3File(FILE)
Traceback (most recent call last):
File "", line 1, in
File "/uufs/chpc.utah.edu/sys/pkg/python/2.7.3_rhel6/lib/python2.7/site-packages/MetPy-0.3.0+50.g3937f51-py2.7.egg/metpy/io/nexrad.py", line 1485, in init
self.header = self._buffer.read_struct(self.header_fmt)
File "/uufs/chpc.utah.edu/sys/pkg/python/2.7.3_rhel6/lib/python2.7/site-packages/MetPy-0.3.0+50.g3937f51-py2.7.egg/metpy/io/tools.py", line 152, in read_struct
struct = struct_class.unpack_from(self._data, self._offset)
File "/uufs/chpc.utah.edu/sys/pkg/python/2.7.3_rhel6/lib/python2.7/site-packages/MetPy-0.3.0+50.g3937f51-py2.7.egg/metpy/io/tools.py", line 45, in unpack_from
return self._create(super(NamedStruct, self).unpack_from(buff, offset))
TypeError: unpack_from() argument 1 must be string or read-only buffer, not bytearray

Can you zip/gzip the data file in question and drag and drop it here? I can't reproduce the exact problem you're getting.
It works for me with TR0 from DEN. I can at least get some kind of failure with TV0 from SLC:
---------------------------------------------------------------------------
IndexError                                Traceback (most recent call last)
<ipython-input-2-436782dc74f3> in <module>()
----> 1 fobj = Level3File('/Users/rmay/Downloads/Level3_SLC_TV0_20160524_2321.nids')

/Users/rmay/repos/MetPy/metpy/io/nexrad.pyc in __init__(self, filename)
   1531         # Now that we have the header, we have everything needed to make tables
   1532         # Store as class that can be called
-> 1533         self.map_data = mapper(self)
   1534
   1535         # Process compression if indicated. We need to fail

/Users/rmay/repos/MetPy/metpy/io/nexrad.pyc in __init__(self, prod)
    846             label = ''
    847             if codes >> 7:
--> 848                 label = self.lut_names[val]
    849                 if label in ('Blank', 'TH', 'ND'):
    850                     val = self.MISSING

IndexError: list index out of range

I'll dig into that, but I'd like to see if your problem is the same.

I can't seem to get any .nids file to be read in. Here is one
Level3_SLC_TV0_20160516_2359.nids.gz
downloaded from:
http://thredds.ucar.edu/thredds/catalog/terminal/level3/TV0/SLC/20160516/catalog.html?dataset=NWS/TDWR3/TV0/SLC/20160516/Level3_SLC_TV0_20160516_2359.nids
Executing this:

from metpy.io.nexrad import Level3File
f_TV0 = Level3File('Level3_SLC_TV0_20160516_2359.nids')

produces this error:
Traceback (most recent call last):
File "MetPy_read_TDWR.py", line 9, in
f_TV0 = Level3File('Level3_SLC_TV0_20160516_2359.nids')
File "/uufs/chpc.utah.edu/sys/pkg/python/2.7.3_rhel6/lib/python2.7/site-packages/MetPy-0.3.0+50.g3937f51-py2.7.egg/metpy/io/nexrad.py", line 1485, in init
self.header = self._buffer.read_struct(self.header_fmt)
File "/uufs/chpc.utah.edu/sys/pkg/python/2.7.3_rhel6/lib/python2.7/site-packages/MetPy-0.3.0+50.g3937f51-py2.7.egg/metpy/io/tools.py", line 152, in read_struct
struct = struct_class.unpack_from(self._data, self._offset)
File "/uufs/chpc.utah.edu/sys/pkg/python/2.7.3_rhel6/lib/python2.7/site-packages/MetPy-0.3.0+50.g3937f51-py2.7.egg/metpy/io/tools.py", line 45, in unpack_from
return self._create(super(NamedStruct, self).unpack_from(buff, offset))
TypeError: unpack_from() argument 1 must be string or read-only buffer, not bytearray
We are using the metpy installed by pip, not a version from git

We are using the metpy installed by pip, not a version from git

I'm not sure I agree:
File "/uufs/chpc.utah.edu/sys/pkg/python/2.7.3_rhel6/lib/python2.7/site-packages/MetPy-0.3.0+50.g3937f51-py2.7.egg/metpy/io/tools.py
Shows a version path of: 0.3.0+50.g3937f51--this reflects a git revision 3937f51 that I've not released yet; also, we only put source and wheels on pypi.python.org, not eggs.
That aside, if I roll back to python 2.7.3 (from 2.7.11), I can reproduce the error. I should be able to get this fixed. I was already planning a bugfix release, and I'll get this in.

Oh, ok. I didn't do the install, so I wasn't sure which version we have.
Thanks for looking into this
http://kbkb-wx.blogspot.com/ Brian
On Wed, May 25, 2016 at 12:13 PM, Ryan May<EMAIL_ADDRESS>wrote:

We are using the metpy installed by pip, not a version from git
I'm not sure I agree:
File "/uufs/
chpc.utah.edu/sys/pkg/python/2.7.3_rhel6/lib/python2.7/site-packages/MetPy-0.3.0+50.g3937f51-py2.7.egg/metpy/io/tools.py
Shows a version path of: 0.3.0+50.g3937f51--this reflects a git revision
3937f51 that I've not released yet; also, we only put source and wheels
on pypi.python.org, not eggs.
That aside, if I roll back to python 2.7.3 (from 2.7.11), I can reproduce
the error. I should be able to get this fixed. I was already planning a
bugfix release, and I'll get this in.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/metpy/MetPy/issues/148#issuecomment-221659322

Just to fill you in, I have a fix for this, I just need to get it committed (along with a few other things).

Great news! Thanks for the quick fix
http://kbkb-wx.blogspot.com/ Brian
On Tue, Jun 14, 2016 at 9:15 AM, Ryan May<EMAIL_ADDRESS>wrote:

Just to fill you in, I have a fix for this, I just need to get it
committed (along with a few other things).
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/metpy/MetPy/issues/148#issuecomment-225914787, or mute
the thread
https://github.com/notifications/unsubscribe/AF9cjXt5NljFXMES3XgInYOcDOMNvq25ks5qLsWDgaJpZM4IltoT
.

TDWR fixes have landed--you may want to ask whoever did your install to re-install from git master. I'll also be cutting a MetPy release (0.3.1) some time today.


Rewrite self-play in more performant language

I've chatted in passing with @amj about this and I wanted to discuss it more formally. Self-play is, as I understand it, the most important part to speed up since more-games-faster means you can train the go-bot faster.
Here are a couple of options that I would consider:

C++
Go
Rust

Some factors:
Currently, we're leaning towards a rewrite in Go (maybe), since we believe that would be simple / easy to follow. Also, I've at least used Go quite a bit on Kubernetes, so there's an experience factor too.

C++ is the best choice I think.

I've made a very early start on a C++ rewrite.

@tommadams can we see the code?

As soon as I have something interesting to show, then yes. I've literally only just started working on it :)

I've just merged in the first stage in the C++ rewrite, under the cc/ subdirectory. It's currently just contains Position logic and some basic testing of the Tensorflow API. I'm in the process of porting the MCTS code now.

C++ implementation is pretty much done!


MNIST example in Google Colab fails with 'LogicError: cuCtxSynchronize failed: an illegal memory access was encountered'

I tried to run the MNIST example verbatim in a GPU-enabled Google Colab notebook; it fails on tm.fit with the following output:
Accuracy over 100 epochs:

---------------------------------------------------------------------------

LogicError                                Traceback (most recent call last)

<ipython-input-6-b93488d43d54> in <module>()
      2 for i in range(100):
      3         start_training = time()
----> 4         tm.fit(X_train, Y_train, epochs=1, incremental=True)
      5         stop_training = time()
      6

/usr/local/lib/python3.6/dist-packages/PyTsetlinMachineCUDA/tm.py in fit(self, X, Y, epochs, incremental, batch_size)
    320                         encoded_Y[:,i] = np.where(Y == i, self.T, -self.T)
    321
--> 322                 self._fit(X, encoded_Y, epochs = epochs, incremental = incremental, batch_size = batch_size)
    323
    324                 return

/usr/local/lib/python3.6/dist-packages/PyTsetlinMachineCUDA/tm.py in _fit(self, X, encoded_Y, epochs, incremental, batch_size)
    224                         for e in range(0, number_of_examples, batch_size):
    225                                 self.update.prepared_call(self.grid, self.block, g.state, self.ta_state_gpu, self.clause_weights_gpu, self.class_sum_gpu, self.clause_output_gpu, self.clause_patch_gpu, self.encoded_X_training_gpu, self.Y_gpu, np.int32(e))
--> 226                                 cuda.Context.synchronize()
    227
    228                 self.ta_state = np.array([])

LogicError: cuCtxSynchronize failed: an illegal memory access was encountered

i.e. similar to this already reported issue.
System info:

Python 3.6.9
pycuda 2019.1.2
PyTsetlinMachineCUDA 0.1.7

with the last two packages installed via pip.

Thanks for reporting, @desertnaut!  Have not found the error yet. It seems like it occurs when there is not enough memory available on the GPU,  but I am not sure. How much memory does your Colab environment provide? Anyway, without enough memory, I guess the memory allocation should fail.

Thanks @olegranmo
The issue seems to have been resolved with the new PyTsetlinMachineCUDA version 0.1.8.


Added warning to ListLayout when options.spacing is non-numeric

The CollectionLayout supports array-based spacing options, and the ListLayout does not.
If an array spacing option is given to ListLayout (after switching from CollectionLayout back to ListLayout for example), it does not warn or throw an exception, but rather doesn't show any renderables without notice. This commit fixes that behaviour by letting the developer know that the spacing should be numeric.

Awesome Tom!
Can you make this pull request on the develop branch, I can only accept pull requests on that branch.

Sure thing: https://github.com/IjzerenHein/famous-flex/pull/115


Fix misleading warning message when a dependency is unused on any platform

The current warning message for a dep with empty platform is misleading/confusing. You see a sort of the below warning when you bundle install,
The dependency tzinfo-data (>= 0) will be unused by any of the platforms Bundler is installing for. Bundler is installing for ruby but the dependency is only for x86-mingw32, x86-mswin32, x64-mingw32, java. To add those platforms to the bundle, run `bundle lock --add-platform mingw, mswin, x64_mingw, jruby`.

However, there two issues exist in this message "run bundle lock --add-platform mingw, mswin, x64_mingw, jruby":

You must not have commma (,) for separators

these commas will be considered as comma itself. see here

mingw, mswin, x64_mingw, jruby are not valid platforms

platforms must be specified as the formats that rubygems can understand, like (x86-mingw32, x86-mswin32, x64-mingw32, java)

This fixes these issues.

Awesome, thanks!

Thanks! @bundlerbot r+


Cache does not work for array driver

Controller:
public function test()
{
    Field::query()->cacheFor(60)->get();
    return view('welcome');
}

This is when using file driver, refreshed twice:

This is when using array driver, refreshed twice:

Apologies, I just realized array driver is simply disabled cache.


Unit tests for app/clients/coin-gecko/client.go

Implement unit tests for app/clients/coin-gecko/client.go


Warning: crossOriginIsolated is null, browser might not support buffer sharing.

When I publish web app to nginx server, I get this warning, and rust function no run correctly

Assuming you have already added the required headers, it could be some quirks with Firefox that disallow buffer sharing. Try configuring nginx so that you can inspect crossOriginIsolated in your web browser and have it be true.

Try configuring nginx so that you can inspect crossOriginIsolated in your web browser and have it be true

thanks,I have already  added the required headers , I found the rust String buffer can't return,  let me try enable crossOriginIsolated


Facebook / twitter not longer available

When the cities / merchants/... broadcast news the facebook & twitter integration is not longer available please add this again and try to add instagram too.

A little bit more context... In the old way of sending out news we could configure that the message was also posted on a facebook page or a twitter account. This facebook page / twitter account can be configured under "Settings > General"
To see the old way of broadcasting set news_enabled=False in src/solutions/flex/handlers.py and reload the dashboard.


why the api is different with the open endpoint?

I am a new guy,I am confused about the DOC
here is the testnet open endpoint,api list is below,it is different from the offical DOC https://node-rpc-docs.celestia.org/?version=v0.14.1，
why they are so different?
where is the DOC about open endpoint?
I am very thankful if someone can give me some advises.
https://celestia-testnet-rpc.blacknodes.net/

that's a celestia core endpoint, openrpc is to communicate with a light node, which you can run here


feat: web app initial commit

Description
Initial code for the web app deployable architecture
Release required?

[ ] No release
[ ] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[x] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

Review completed.

:tada: This issue has been resolved in version 1.0.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[DOCS] improve spark quickstart, info about MT and async services

Change Logs
Improve spark quickstart, add info about table maintenance and async services when metadata table is enabled (one should be aware OCC needs to be enabled even in single writer mode)
I  as a user would like to be informed about this in quick start, since I rarely read pages under "concepts" where this information is provided. It's esp. important since MT is enabled by default starting from 0.11, and misconfiguration can cause data loss since for MoR some async services are also enabled by default.
Fixes spark quickstart from 0.10 to current, bc metadata table was introduced in 0.10.
Impact
None
Risk level (write none, low medium or high below)
Low
Documentation Update
improve spark quickstart, add info about table maintenance and async services when metadata table is enabled (one should be aware OCC needs to be enabled even in single writer mode)
I  as a user would like to be informed about this in quick start, since I rarely read pages under "concepts" where this information is provided. It's esp. important since MT is enabled by default starting from 0.11, and misconfiguration can cause data loss.
Contributor's checklist

[x] Read through contributor's guide
[x] Change Logs and Impact were stated clearly
[x] Adequate tests were added if applicable
[x] CI passed

@bhasudha and @nfarah86 could you review this PR? Or should I close it and wait for your docs refactor?

cc @bhasudha I'm ok merging it-- I can refactor it later on

cc @codope


Windows Issues::Enable Long Path

I have tried with solution provided on this (https://github.com/pact-foundation/pact-js-core#windows-issues)  but still I am not able to execute  with long path however it perfectly working if I short the path,  I have attached the images of an issues for your reference.
#101

Apologies, we should probably remove that section from the documentation (long path support is enabled by default in current versions of windows).
Otherwise, unfortunately this is an upstream issue for us. It will be cleared when the Rust-based core of pact is used.
If you are unable to use a shorter path, you could try the beta version of the next release of pact, but the interface and binaries are currently a little unstable.

@TimothyJones  I have rechecked it by reducing the file path length it successfully executed if length is less than equal to 46 of path length is greater then 46 it throw an error after executing provider. here I am pasting the exact error so that you can provide me a solution for it.
**1) Contact account API Pact verification
validates the expectations of Matching Service:
Error: C:/CmiCode/JarusScrum/ContractTest/ContractConfig/node_modules/@pact-foundation/pact-node/standalone/win32-1.88.80/pact/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.36.1/lib/pact/provider_verifier/app.rb:4:in require': cannot load such file -- pact/provider_verifier/provider_states/remove_provider_states_header_middleware (LoadError)                 from C:/CmiCode/JarusScrum/ContractTest/ContractConfig/node_modules/@pact-foundation/pact-node/standalone/win32-1.88.80/pact/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.36.1/lib/pact/provider_verifier/app.rb:4:in <top (required)>'
    from C:/CmiCode/JarusScrum/ContractTest/ContractConfig/node_modules/@pact-foundation/pact-node/standalone/win32-1.88.80/pact/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.36.1/lib/pact/provider_verifier/cli/verify.rb:45:in `require'
    from C:/CmiCode/JarusScrum/ContractTest/ContractConfig/node_modules/@pact-foundation/pact-node/standalone/win32-1.88.80/pact/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.36.1/lib/pact/provider_verifier/cli/verify.rb:45:in `verify'
    from C:/CmiCode/JarusScrum/ContractTest/ContractConfig/node_modules/@pact-foundation/pact-node/standalone/win32-1.88.80/pact/lib/vendor/ruby/2.2.0/gems/thor-1.1.0/lib/thor/command.rb:27:in `run'
    from C:/CmiCode/JarusScrum/ContractTest/ContractConfig/node_modules/@pact-foundation/pact-node/standalone/win32-1.88.80/pact/lib/vendor/ruby/2.2.0/gems/thor-1.1.0/lib/thor/invocation.rb:127:in `invoke_command'
    from C:/CmiCode/JarusScrum/ContractTest/ContractConfig/node_modules/@pact-foundation/pact-node/standalone/win32-1.88.80/pact/lib/vendor/ruby/2.2.0/gems/thor-1.1.0/lib/thor.rb:392:in `dispatch'
    from C:/CmiCode/JarusScrum/ContractTest/ContractConfig/node_modules/@pact-foundation/pact-node/standalone/win32-1.88.80/pact/lib/vendor/ruby/2.2.0/gems/thor-1.1.0/lib/thor/base.rb:485:in `start'
    from C:/CmiCode/JarusScrum/ContractTest/ContractConfig/node_modules/@pact-foundation/pact-node/standalone/win32-1.88.80/pact/lib/vendor/ruby/2.2.0/gems/pact-provider-verifier-1.36.1/lib/pact/provider_verifier/cli/custom_thor.rb:17:in

start'         from C:/CmiCode/JarusScrum/ContractTest/ContractConfig/node_modules/@pact-foundation/pact-node/standalone/win32-1.88.80/pact/lib/app/pact-provider-verifier.rb:33:in '
  at ChildProcess.<anonymous> (node_modules\@pact-foundation\pact-node\src\verifier.js:185:64)
  at Object.onceWrapper (node:events:510:26)
  at ChildProcess.emit (node:events:402:35)
  at ChildProcess.cp.emit (node_modules\cross-spawn\lib\enoent.js:34:29)
  at maybeClose (node:internal/child_process:1064:16)
  at Process.ChildProcess._handle.onexit (node:internal/child_process:301:5)**

Yes, apologies for the confusion, as stated it's an issue in the current version.
You might like to try the latest beta (https://github.com/pact-foundation/pact-js#pact-js-v3), with the usual warnings around it being a beta

less than equal to 46 of path length is greater then 46

So, this is the base path. Unfortunately, due to the way the tooling of the binary works, the full path length it fails on is much longer. From your error message it is failing on the following 263 character path<EMAIL_ADDRESS>

I'm going to close this issue as the latest version (13.x.x) has removed this issue. We won't be able to fix this is previous versions.


next-sass can't find my sass module

Hi, I'm very new to Next, I'm trying to use Next + Express + Typescript + Sass.
But I got this error when I tried to use Sass.
Can someone help me?
// package.json

"dependencies": {
    "@zeit/next-sass": "^1.0.1",
    "@zeit/next-typescript": "^1.1.1",
    "express": "^4.17.1",
    "next": "^9.0.6",
    "node-sass": "^4.12.0",
    "react": "^16.9.0",
    "react-dom": "^16.9.0",
    "typescript": "^3.6.3"
  },
  "devDependencies": {
    "@types/next": "^8.0.6",
    "@types/react": "^16.9.2"
  }

src
--pages
----index.tsx
----index.scss
--server
----server.js
--typings
----declarations.d.ts

// next.config.js

const path = require("path");
const withTypeScript = require("@zeit/next-typescript");
const withSass = require("@zeit/next-sass");

module.exports = withTypeScript(
  {
    webpack(config) {
      return config;
    }
  },
  withSass({
    cssModules: true
  })
);

This is what I have in my project, when I run npm run dev which is dev: node src/server/server.js, I got this error.
[error] ./pages/index.scss 1:0
Module parse failed: Unexpected token (1:0)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders

// index.scss
.container {
  background: pink;
}

Possibly related issue: https://github.com/webpack-contrib/sass-loader/issues/344#issuecomment-270729267

Sadly, You need to create a definition file.
so for:
// index.scss
.Container {
  background: pink;
}

you create
// index.scss.d.ts
export const Container:string

this is a bit annoying, so I try to find something to generate this files and dropbox has a plugin for webpack that solve this BUT for css files, no scss.
https://github.com/dropbox/typed-css-modules-webpack-plugin
In basically, before compile any css they check if definition already exist or not and create a css.d.ts file using https://github.com/Quramy/typed-css-modules .
Is required to generate the file before to compile because typescript need to be generated correctly.
So the solution to this will require one of this options:

create our own version of typed-css-modules-webpack-plugin that compile each scss file and then pass this temp css file to typed-css-modules to generate the scss.d.ts file. (and handle possible postCSS configs)
ignore all and create a generic definition file

declare module '*.scss' {
  const content: any;
  export = content;
}

not sure if is possible this hacky ways...

babel plugin to capture any styles.* and create the definition or allow to read scss files
some postCSS plugin to generate the definition file on save

Hope this help somehow to someone.

I just try https://github.com/dropbox/typed-css-modules-webpack-plugin and works well with scss.
the processor is postCss and if you not use weird SCSS tricks works without problem. one issue is that is not re generating the files if you add or remove some class from your file.
this is my next.config.js
module.exports = withSass({
  cssModules: true,
  cssLoaderOptions: {
    importLoaders: 2,
    localIdentName: '[local]___[hash:base64:5]'
  },
  webpack: (config, { dev }) => {
    if (!config.plugins) config.plugins = [];
    config.plugins.push(
      new TypedCssModulesPlugin({
        globPattern: 'components/**/*.scss',
      }),
    )
    return config;
  }
});

I just try https://github.com/dropbox/typed-css-modules-webpack-plugin and works well with scss.
the processor is postCss and if you not use weird SCSS tricks works without problem. one issue is that is not re generating the files if you add or remove some class from your file.
this is my next.config.js
module.exports = withSass({
  cssModules: true,
  cssLoaderOptions: {
    importLoaders: 2,
    localIdentName: '[local]___[hash:base64:5]'
  },
  webpack: (config, { dev }) => {
    if (!config.plugins) config.plugins = [];
    config.plugins.push(
      new TypedCssModulesPlugin({
        globPattern: 'components/**/*.scss',
      }),
    )
    return config;
  }
});

Thank you. You - the best!
Best way imho. I tried approximate full day to resolve this build bugs with css-modules + typescript + next js.

Everything is great, except I got this error in console:
You tried to parse SCSS with the standard CSS parser; try again with the postcss-scss parser
The error happens when TypedCssModulesPlugin reaches scss-specified syntax like  // single-line comments or #{$variables}
How can I fix that?

@nathanredblur thanks! Everything is great, except I got this error in console:
You tried to parse SCSS with the standard CSS parser; try again with the postcss-scss parser
The error happens when TypedCssModulesPlugin reaches scss-specified syntax like  // single-line comments or #{$variables}
How can I fix that?
PS: postcss-scss cannot be used as a plugin.

I not remember well now.  I think I had this issue and I give up because require to create a new plugin.
I just not use single-lines or computed variables.  :(
also I not use this plugin in all. so in my next.config I have:
config.plugins.push(
        new TypedCssModulesPlugin({
          globPattern: '{components,style}/**/[!_]*.scss',
        })
      );

In this way I create the definition files only for scss files without dash in the first character.
and in this dash files I have things like _variables.scss or . _mixins.scss
I hope this help. :/

Hi, thanks for creating an issue. We currently recommend using https://nextjs.org/docs/basic-features/built-in-css-support as the plugins have been deprecated in favor of the built-in support.


BlTaskItStatus display Failed queue entries

Extend BlTaskItStatus to display information about failed tasks.

We have
gtStatusFor: aView
	<gtView>

	^aView textEditor
		title: 'Status' translated;
		priority: 1;
		look: BrGlamorousCodeEditorLook;
		text: [ self statusString asRopedText ]

We can open a new one with more specifics if needed.


DJANGO_DEBUG not available for running TRAM as developer.

I am looking to run TRAM as developer to contribute to this project; however when I tried to run TRAM in localhost with DJANGO_DEBUG, my PowerShell and Anaconda could not recognize DJANGO_DEBUG as a part of my command:

I have tried to remove DJANGO_DEBUG, but it forced me to set settings for allowed hosts as well. So could you tell me what should I do to run TRAM in my local server?

Hmm... try this:

Install python-dotenv (with pip)
Create a .env file in the tram folder.
Add: DJANGO_DEBUG=1 in the .env file
At the top of the settings.py file import dotenv
Add: dotenv.load_dotenv() on the next line.
Then run tram runserver without DJANGO_DEBUG=1.

I think this should work.
Cheers.

That DJANGO_DEBUG=1 syntax is for Bash. The goal is to set that variable in the TRAM process environment. I think in Powershell you want to do this:
$env:DJANGO_DEBUG = 1
tram runserver

Thank you @mehaase for your answer, I was able to run the website in debug mode now!
I think as you said, it would be better for me to run the program with WSL and Bash. So I just have another question, for every single time we want to run TRAM in debug mode, do we need to follow all steps, or we just need to run the Machine Learning model and then run the application server?

After initial setup, you only need to do steps 11-13 to start TRAM again.


Graduate logging feature to beta

What would you like to be added:
The logging stack running in the seed clusters responsible for:

logging of the the control plane components
seed system components like gardenlet and gardener extensions

was initially contributed as an alpha feature an year and a half ago https://github.com/gardener/gardener/pull/176. Since then this components is running without major issues and I propose to graduate it to beta, which means:

[ ] The feature gate is enabled by default, ref.
[ ] Deploy the logging component as early as possible in the shoot creation/reconciliation  flow. This is useful when creation is failing and persisted logs are needed for analysis.
[ ] Use OIDC for authentication instead of Basic Authentication.

Why is this needed:

@mvladev for the  task
Use OIDC for authentication instead of Basic Authentication.

I think it can be handled independently of this one. There is already an enhancement proposal #999 about it. What do you think?

With https://github.com/gardener/gardener/issues/918 the logging stack will be completely redesigned, thus it does not make sense to graduate the existing solution to beta.


Gridstack requirements

Hi,
I am not raising an issue but just a clarification on the jQuery\jQuery-ui versions required by gridstack.
In the Requirements paragraph it says that the jQuery versions required are:

jQuery (>= 3.1.0)
jQuery UI (>= 1.12.0). Minimum required components: Core, Widget, Mouse, Draggable, Resizable

but the jQuery\jQuery-UI versions used in all of the examples here are:

jQuery 1.11.1
jQuery-ui 1.11.0

So what are the minimum jQuery\jQuery-UI versions required?
Thanks and keep doing the good work!

Earlier versions of both jQuery and jQuery UI will not break. We don't use advanced features, but we have verified that it works with the newer versions of both.

I want to also add that we plan on removing the jQuery UI dependency in version 1, which will hopefully hit beta next month. You can read more about version 1 at
https://dylandreams.com/2017/04/26/gridstack-10-coming-soon/.
There will be some additional changes, so be sure to subscribe to/follow the blog. I'll post another update when version 1 is more finalized.
Thanks for using gridstack.js!


Travis: Get utility packages from conda-forge

This should get our trvis testing back online and green (he said hopefully). :wink:

Ok, merging....


Project maintenance

I am no longer able or interested in maintaining this project. Is anyone in the community interested in doing so?

As you had no replies, I've cross posted to the bower issues page. Hopefully someone with more JS skills than me will step in.

Well, I have to say that the responses haven't been great!
I'm a user of bower-installer, but my JS skills aren't great.
I'm happy to take over the repo for maintenance/patching, but probably not future development.
That may be enough for a lot of users.
If that is enough, then go for it.

@rquadling it is a great opportunity for you to learn and get involved, I might occasionally be able to give you some feedback if you'd like.

Well, got for it.
I can see Travis-CI can run JS tests. Hopefully there is some code coverage analysis capability. That way I can at least see what is broken or untested.

At least until someone else volunteers.

Granted collaborator access. FYI, @g105b also started helping out a while back. Not sure if he has any interest anymore.

bower-installer was the answer to many bower issues, and I contributed the part that was missing for me, however I have moved on from using bower in projects all together so no longer have this project on my radar.
I'll happily guide/mentor anyone in making their contributions to the project, but I won't be contributing myself anytime soon.

@g105b That has really been my dilemma as well. I have totally moved all of my work to either webpack or JSPM. I have no use anymore for for bower :( I'd be willing to help out with guidance, but I don't think I'm the best one to lead the project given I lack a vested interest. If anyone really wants to take charge of the project, I am more than willing to transfer ownership, but I'd prefer to wait to see if anyone steps up to the plate.

Agreed. This kind of project survives on passion. Do you think a message in the readme advertising a new project owner would be a good idea?

@g105b added :)

I may be able to help, I have used bower-installer on some projects and it helped me a lot. Let me know if there is an active plan or actions that need to be done.

@thinkxl I think generally the project needs the issue list cleaned up as well as it needs to be upgraded to the latest version of bower. Beyond that, it would probably be best for someone to step in and take charge of bower-installer's future direction.

@blittle It sounds fun, I will dig into the issues and see what needs to be done to sync it with current Bower version

@blittle I make a fork of the project and I include a little method to add the minified files, later I will make a pull request, I wanna be a maintainer to contribute to the open-source :)

This is my first day with bower-installer, since mozilla/localforage can't be imported es6-way.
I hope you guys find an amazing path for this great tool. My skills are probably not yet ready to maintain this project, buy I'll put this on my radar. :)

I'd love to take part in this, but I'm not a nodeJs developer.
I really love bower-installer

I love bower-installer but when I run bower-installer, it's auto find files's path to grab, and sometimes It doesn't grab files I want like Bootstrap. ( I need bootstrap.css not .less) .  And I think when it grab jquery.js it should be place to src/vendor/jquery.js so I can maintain source files, not src/vendor/jquery/jquery.js. I prefer do copy those files on my own.

@blittle Is there a new owner for this project? @dezkareid are you the new owner? If so this issues should be closed.
I contributed to this project in the past ('Configurable paths') and I think there's a need to address some of the issues that are reported. Like supporting mapping with glob, this issues already have pull request (see #143) and no action was made. I will be glad to help on this again.

Would be good to see this project alive again at least to accept pull requests. I've forked and added a quick fix for directory copying that we needed, so you can write something such as:
 "jquery-ui" : [
   "bower_components/jquery-ui/jquery-ui.min.js",
   "bower_components/jquery-ui/themes/smoothness/jquery-ui.min.css",
   { "bower_components/jquery-ui/themes/smoothness/images/" : "images/" }
],

which may also be similar to #143. Is there any consensus on 1 or 2 "must have" changes?

@nickion ^ Thats definitely number one for me :)

Who would be willing to take ownership? Like I stated above, I don't have the time nor interest to continue supporting bower-installer.

I'll take it. I am collaborator already and actively work on various PHP based projects. This would be my first JS based one.

Hi.
I have received ownership of this project.
I'd like to thank Bret for the time and energy he put into this project and I promise to look after it!
I'm going to close this issue now.
If anyone has any outstanding points, please open a new issue, referring to this one if necessary.
Thanks,
Richard.


Gatsby Implementation

https://www.gatsbyjs.org

[ ] Understand Gatsby
[ ] Markdown support
[ ] Deployment on Github.io

Completed the basic tutorials on Gatsby. I really liked the simplicity in how the tutorial was written. Along the way I have come to know few more things about the web platform.

- Get to know Gatsby building blocks: Starting new projects, developing, and deploying sites.
- Introduction to using CSS in Gatsby: Explore libraries like Typography.js and CSS Modules.
- Building nested layouts in Gatsby: Layouts are sections of your site that are reused across multiple pages like headers and footers.
Intermediate tutorials
In these intermediate tutorials, you’ll learn how to pull data from almost anywhere into your Gatsby site with GraphQL.

Querying for data in a blog: Create a blog and use a GraphQL query to pull your site title into the blog header.
Source plugins and rendering queried data: Use a source plugin to pull Markdown blog posts into your site and create an index page with a list of blog posts.
Transformer plugins: Use a transformer plugin to transform your Markdown blog posts into a form the blog can render.
Programmatically create pages from data: Learn how to programmatically create a set of pages for your blog posts.
Preparing a site to go live: Learn how to audit your site for performance and best practices for accessibility, SEO, and more.

In the last part to go live, as it lists few things, compared few reference sites and found https://kentcdodds.com to be good enough
The next thing to do is to cover will be about Plug-ins and Themes https://www.gatsbyjs.org/tutorial/plugin-and-theme-tutorials, and implement the blog.

Need to go through https://kentcdodds.com code base further.

Update May 12
Review Kentcdodds.com. Went through gatsby-config.js and skimmed the plugins.
Also went through the tutorials section in very brief.
Wanted to know more about the special files, and it turns out to be a palce holder for the API that Gatsby provides. https://www.gatsbyjs.org/docs/api-reference for further read.
I was looking for a way to manage the static contents or CMS and https://www.gatsbyjs.org/tutorial/blog-netlify-cms-tutorial looks like the solution.
https://www.gatsbyjs.org/docs/api-specification to read.
Need to go through https://www.gatsbyjs.org/tutorial again
https://github.com/gatsbyjs/gatsby/tree/master/examples will be good to go through them.

Issues when running the kentcdodds code on new pc, installed nvm and stable version of nodejs.
"gyp ERR! stack Error: not found: make gyp ERR! stack at getNotFoundError"
Followed https://stackoverflow.com/questions/14772508/npm-failed-to-install-time-with-make-not-found-error, and installed sudo apt-get install build-essential
This solved the error.
Another issue followed up "Fixing npm/node-gyp Error: not found:"
Resolved with sudo apt install build-essential from https://techoverflow.net/2018/06/04/fixing-npm-node-gyp-error-not-found-make-on-ubuntu
Another issue followed up - "Error: Cannot find module './build/Release/sharp'"
Resolved with apt install libvips followed by npm install sharp
Another issue  "WorkerError: Processing image.png failed". There seems to be issue while processing large image file in Gatsby. This is listed in common error
https://www.gatsbyjs.org/docs/troubleshooting-common-errors
https://github.com/gatsbyjs/gatsby/issues/13442
Error: ENOSPC: System limit for number of file watchers reached: https://stackoverflow.com/questions/55763428/react-native-error-enospc-system-limit-for-number-of-file-watchers-reached
There seems to be issue with VSCode as well: https://code.visualstudio.com/docs/setup/linux#_visual-studio-code-is-unable-to-watch-for-file-changes-in-this-large-workspace-error-enospc
Well in the end removing and and reinstalling made the application functional.
rm -rf .cache node_modules public package-lock.json

This is task is done. Understanding of basics is done.