DoctrineDriver - Use UUID instead of autoincrement ID's

We use the DoctrineDriver and every now and then we'll hit a dead lock.
I think the reason for this is that the DoctrineDriver creates a bernard_messages table where the id is autoincrement.
This locks the table every time an insert is executed.
I think we should use UUID's and get rid of the autoincrement ids. The only problem is that we need to sort based on date + microtime.

In a project at work we use something like this http://engineering.custommade.com/simpleflake-distributed-id-generation-for-the-lazy/ for generating integer based ids that is sorteable like auto increments. Cannot share our integration sadly.

Would you be up to work on this? We could make it an external bernard library.

Well, for me, the UUID4 + microtime approach is good enough. Maybe I can submit that as a PR?

Would be amount of time be different for the two implementations?

What do you mean?

Implementing the "snowflake" thing vs. implementing the uuid v4 solution.

Dunno if it makes sense to have the two solutions in parallel. Maybe we can make it configurable? I could do it as part of the driver separation process #256

This might be interesting, performance / lock-wise:

article: https://www.percona.com/blog/2014/12/19/store-uuid-optimized-way/
inspiration implementation: https://github.com/ramsey/uuid-doctrine

not sure if this can adopted/used easily, but might be worth trying to

I would much rather have the simpleflake implementation, as it is sortable by default etc.

In a project at work we use something like this http://engineering.custommade.com/simpleflake-distributed-id-generation-for-the-lazy/

this page seems down 😢

Presentation here: http://akmanalp.com/simpleflake_presentation
PHP implementation here: https://github.com/michaelcontento/simpleflake-php

Cross-linking discussion here: https://github.com/SawdustSoftware/simpleflake/issues/9
I don't know your exact requirements but one alternative approach is to do something like uuid1 (which has machine-id and time bits) and then reordering the bits so that the time stuff comes at the beginning, so it still sorts lexicographically.

Shouldn't we keep this issue open and implement it while doing work on the drivers?


document transformer location

transformer has moved to intl_translation a year ago

Closed in REVID=173178667 (will sync back to github soon)


Add randomization module to utils

What is the purpose of this PR?
Much of ark-analysis requires random sampling, and in light of future requests for random samples of the data, we should create a separate module containing several different randomization methods.
How did you implement your changes
We add rand_utils.py to the utils folder.
Remaining issues
I have written other randomization methods but for now, the only one I've added is a simple one to do a fully random sample.

Should be a pretty easy review, just want to get a sense of:

The current structure
Any other randomization functions related to pixel/cell clustering that we need to add?

Should be a pretty easy review, just want to get a sense of:

The current structure
Any other randomization functions related to pixel/cell clustering that we need to add?


test-branch/execute-job/quoted-authorization/bca3a90f-f791-41ad-ac3d-bb9a76dc5232

PR for testing f16d913388821cf1eee7066f5141994609170af8

/canonical/self-hosted-runners/run-workflows f16d913388821cf1eee7066f5141994609170af8


Implement component-based scss

Description
Right now we only can use scss from src/assets/scss but ideally we want to let a component have it's own .scss file and then use node-sass glob thingies to build everything from src/components/**/*.scss to a css file.
Acceptance criteria

Every component can have it's own scss file
Everything gets bundled into one css file
Works when running a build
Works when running npm run dev so when live server is running etc.

Done 🎉


Disable unnecessary logs

I am using this library firebase-cloud-functions. I just want to delete logs which are defaultly logged into console.

As you can see in above image logs like Response , Conversation, Headers, Request. I have not written those logs in my function.
How can I disable it?

You may be adding a debug flag in your Actions on Google constructor:
const app = dialogflow({ debug: true })
If you don't include this field, the logs won't happen.

@Fleker Yes that worked, Thank you :)


Rename Build.hs to Shakefile.hs

Fixes #582
I fixed the filenames and contents without re-running anything so let
me know if anything looks off or if I should verify anything.

@ndmitchell WDYT?

Thanks for the patch. I've been on holiday for the last two weeks and now catching up. Will take a look this evening with luck, and if not, in the next few days.

Thanks, much appreciated, and sorry for the huge delay in reviewing. Slowly catching up, but still drowning in PR's and emails!


Missing data points for recording rule evaluation result

Thanos, Prometheus and Golang version used:
Thanos version: 0.22
Prometheus version: 2.29.2
Golang version: 1.17

Object Storage Provider: AWS S3
What happened:
We have defined the following recordingrule for thanos ruler:
      - name: foo
        rules:
        - expr: sum(cluster:kube_pod_container_resource_requests:cpu:sum) by (cluster) / sum(kube_node_status_allocatable{resource="cpu"}) by (cluster)
          record: cluster:cpu_requested:ratio

We found that lots of data points are missing in thanos ruler evaluation results, we user default evaluation interval(30s), as you can see from blow chart:

But if we query the original expression directly, we can see all the data points:

What you expected to happen:
Thanos rule evaluation should have the same results with the direct query.
How to reproduce it (as minimally and precisely as possible):
Full logs to relevant components:

Anything else we need to know:
Is this relevant with the prometheus_rule_evaluation_failures_total metrics of thanos rule, I also checked the thanos rule evaluation at the period, see blow chart:

Could it be simply that you need to set the step to be explicitly equal to the evaluation interval which is 1 minute by default? (:

@GiedriusS Prometheus scrape interval is 30s, I didn't set step. As you can see from the original expression query results, there is a data point each 30 seconds. And the recording rule query chart is misleading, I'm sure I saw there is data point after 30 seconds sometimes.

The charts in the description are a little confusing, the data point does not comes every 1 minute for the recording rule query result, it can be 30s, 1 minute or some other time period.
The following two charts are more clear:
Recording Rule Query Result:

Original Expression Query Result:

It seems that  thanos ruler queries the rule expression with partial response, if some of the query component can't return the data in specific time, that part of data will be ignored and not in the rule evaluation result. That's probably the cause of this issue.

What if you enter 60s there?

if I set step to 60s, the data points will be connected, but that will not fix the missing data in our grafana dashboard, in which we use the recording rule to create the dashboard.

@morvencao Could you try to set the grafana datasource scrape interval to 30s?

@hanjm It is indeed 30s.

It seems that this issue is relevant with the lookback-delta of thanos query.
Currently it is 2*scrape_interval, but if I set it to larger value, the original issue would be mitigated.


instructions for docker setup on OSX don't make the UI accessible (port 26527)

You can't access http:\\<docker ip>:26527 because docker ports/networking something something. I think we need more to the docker invocation than what's documented here. I think @tschottdorf would know.
Also we need to figure out the relationship between the installation instructions we have in the README.md and the docs site.

I think we should start exposing our linux nightlies and the brew formula (assuming it works fairly reliably). We can keep the Docker stuff around somewhere, but maybe not at the top.
I'll fix up the README invocation. Should be passing a flag or two, but on OSX there's always some loss of simplicity because of the VM.

Fixed with readme updates: https://github.com/cockroachdb/cockroach/pull/5511. We're now just linking to our install page in the docs.


Docs: Mention B extension in overview page

We don't mention the B extension on https://ibex-core.readthedocs.io/en/latest/introduction.html yet, we should do so.
@ganoam

Thanks @imphil. I have added the B-extension to the ISA extension table in my latest PR #965 .


Basic documentation

Basic API documentation needs to be in place. This has the following subtasks:

[ ] Annotate all public API functions with a docstring
[ ] Setup mkdocs
[ ] Write an introduction with basic usage

For the documentation, i think pDoc could also be a good option


using docker inside gitlab-runner

I am trying to build a setup where my gitlab-runner is using docker for building and pushing an application image as described here in option 2. Everything seems to work fine, till I get to the point, where the docker socket is called.
.gitlab-ci.yml:
myjob:
  script:
  - docker --version #works fine
  - docker info #produces error

When the script tries to get docker info, I get following error message:
$ docker info
Get http:///var/run/docker.sock/v1.19/info: dial unix /var/run/docker.sock: no such file or directory. Are you trying to connect to a TLS-enabled daemon without TLS?

I am starting the runner by calling this script.
#!/usr/bin/env bash
docker rm -f gitlab-runner
sudo docker run -d --name gitlab-runner --restart always -v /var/run/docker.sock:/var/run/docker.sock -v /srv/gitlab-runner/config:/etc/gitlab-runner gitlab/gitlab-runner:alpine
gitlab-runner register -n \
  --url http://ci.mysite.net/ \
  --registration-token $1 \
  --executor docker \
  --description "gitlab builder" \
  --docker-image "gitlab/dind:latest" \
  --docker-privileged

If I change the executor for shell (basically option 1 in the example), it is working. I slightly modified the dind image by copying a ceritficate in Dockerfile.
COPY assets/ca.crt /etc/ssl/certs/ca-certificates.crt

Any ideas where this could originate?
greetz!

Do you run runner in docker image or on host system?

Please also post the head lines of build log. There should be some information about dind image.

I am using the runner in a docker image, although I had to install it on the host system to get it working.
gitlab-ci-multi-runner 0.5.0 (c38415a)
Using Docker executor with image gitlab-build:v1 ...
Running on runner-51cfe3c8-project-2-concurrent-0 via mysite...

Cloning repository...

gitlab-build:v1 is the modified dind image.

Since I discovered some other strange behaviour in docker, I was looking for misconfigurations there. It turns out, that my linux kernel is older than the current requirement. I'll try to update it and let you know.
Thanks for your effort.

Pretty strange problem. Everything should work ok. Feel free to open the issue if you have more questions.

It seems to work now.
I updated my kernel first (from 3.2 to 3.16). That fixed the docker issues, but I still had problems running docker info inside my runner. Then I fixed the docker-runner setup by removing it from the host system and calling it properly inside my runner container:
docker exec -it gitlab-runner gitlab-ci-multi-runner register \
  --non-interactive \
  --url http://ci.mysite.net/ \
  --registration-token $1 \
  --executor docker \
  --description "gitlab builder" \
  --docker-image "gitlab-build:v1" \
  --docker-privileged

Still the same error though. After that I changed the runner configuration inside my containers /etc/gitlab-runner/config.toml to
[[runners]]
  name = "gitlab builder"
  url = "http://ci.mysite.net/"
  token = "aa9f9cce4940d105a5b51858185fa7"
  limit = 1
  executor = "docker"
  [runners.docker]
    image = "gitlab-build:v1"
    privileged = true
    volumes = ["/cache", "/var/run/docker.sock:/var/run/docker.sock:rw"]

Basically adding docker.sock to the volumes by adding this "/var/run/docker.sock:/var/run/docker.sock:rw".
Finally I get this result, when running the initial job:
gitlab-ci-multi-runner 0.5.0 (c38415a)
Using Docker executor with image gitlab-build:v1 ...
Running on runner-aa9f9cce-project-2-concurrent-0 via 31b8230da405...

Cloning repository...
Cloning into '/builds/okoenecke/day-break-frontend'...
Checking out de82973b as ci-config...

$ docker --version
Docker version 1.7.1, build 786b29d
$ docker info
Containers: 15
Images: 45
Storage Driver: aufs
 Root Dir: /var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 75
 Dirperm1 Supported: true
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.16.0-0.bpo.4-amd64
Operating System: Debian GNU/Linux 7 (wheezy)
CPUs: 8
WARNING: No memory limit support
WARNING: No swap limit support
Total Memory: 31.35 GiB
Name: mysite
ID: G5WU:72SB:G5GJ:WNNW:PVWL:DO7X:7IKJ:YVCA:TASY:HNRS:RXS6:SZK7

Build succeeded.

Don't know if it working like intended now, but at least its working for me :)

I have the same issue. Why "/var/run/docker.sock:/var/run/docker.sock:rw" not added by default?

Had the same issue and as @fokoenecke said was worked it around adding "/var/run/docker.sock:/var/run/docker.sock:rw" to the config.toml

Shouldn't be it at least mentioned in documentation??

Glad I stumbled on this, same issue here, added /var/run/docker.sock to volumes and the process ran, documentation is severely lacking in this regard.

Seems like it might also be possible to pass through as a command:
 gitlab-runner register --docker-privileged true --docker-volumes /var/run/docker.sock:/var/run/docker.sock

Just for the info:
This seems to be fixed without using a workaround now. Maybe it's because there is an official docker:dind image. But if you run that as a service like described, it works fine for us.


Pin pandas to last release and update pip lockfile

The CI test failure is due to a new release of pandas requiring lzma.  The standard python containers on CircleCI are missing lzma.  For now, I'm mitigating the issue by pinning pandas to v0.24.
@subdavis This doesn't look like the same error you are having, but maybe it will fix it.

I'll rebase and give it a try, thanks @jbeezley


Could not read all champion data from memory error

I am getting this error it seems that the application works fine but after a bit it crushes and some animation doesn't work properly.

I got kinda the same error
crashlog: https://pastie.io/tqiooi.tex
log: https://pastie.io/rokhin.cs
It was a "spectate game"

same here getting error

Same here, error ingame

Hello, I am having the same error message. How did you guys fix it??


QUESTION: Where put app logic for a simple layout not-routed application?

I have to reimplement a big Symfony2 project, and I decided to use React with Redux for the new front.
But before, I was experimenting with a simple mini game with this starter kit, but for this game I do not need routes. I have a layout idea like this:
<App>
    <Header >
    <Game >
    <Footer >
</App>

Where Header and Footer are static and in Game goes all the logic. But, in the starter kit src/components and src/containers are for "Reusable Components", and the reduers examples are always on a src/route directory.
How could I structure this mini game using this starter kit?

I don't see the problem with puting <Game /> component into src/components

reduers examples are always on a src/route directory

That is not true you have router reducer not tied to any particular route in reducers.js so you can put more reducers here. If you don't need routes then just use indexRoute in which will be just your <Game/> component connected to the store. Fractal structure used in this project doesn't really makes sense for such simple applications as one you described.

Thanks @kolpav
"Fractal structure used in this project doesn't really makes sense for such simple applications as one you described"
That's true, I know. This project is just for practice with a current real little project, then I will have to develop a big project with a real fractal structure.

@aabilio good luck with your game :+1:

@kolpav 's answer is totally correct, thanks!


Fixed #46 -- No longer force the color scheme setting.

Fixes #46.

Merged in dev Branch!
I've merged your contribution directly into the dev branch, bypassing the PR.
I took the liberty of squashing the three commits into a single one, and amend the commit message — you are still mentioned as the original contributor, even after these Git operations.
If you find the time, please do check if my scheme fix in the origin/color-scheme-fix branch works on your PC — even if it will be discarded, it provides us with insight regarding the proper scheme path to suggest in the documentation, for those who'd rather configure it manually.


fix: 🤔 syn-dialog emits syn-close event on click on slotted children

Checklist (for the issue creator)

[x] I have verified the bug exists in the latest version of @synergy-design-system/components (e.g. via pnpm install @synergy-design-system/components).
[x] I can provide a simple, reproducible example of the issue (e.g. via code-sandbox or sample code, ...).
[x] I would be willing to provide a PR for this issue.

Version
The bug occurred with the following version of the component library: 2.4.0
Component
The issue arises when using the following component(s): syn-dialog in combination with any slotted element
Environment
The issue occurred with the following operating system(s): All
The issue occurred in the following browser(s): All
Description
When slotting an element into a <syn-dialog> that uses a click-listener internally (e.g. <syn-detail>, the listeners callback will bubble up and create a syn-close event. For example, the following code (using React) will automatically close the dialog when clicking on one of the provided syn-detail elements:
import { useState } from 'react';
import {
  SynAccordion,
  SynButton,
  SynDetails,
  SynDialog,
} from '@synergy-design-system/react';

export const Settings = () => {
  const [isOpen, setIsOpen] = useState(false);
  return (
    <SynDialog
      onSynHide={() => {
        // Change the listener from onSynHide to onSynRequestClose to make it work
        console.log('hide called!');
        setIsOpen(!isOpen);
      }}
      open={isOpen}
      label="Settings"
    >
      <SynAccordion>

        <SynDetails open summary="Group 1">
          Content 1
        </SynDetails>

        <SynDetails open summary="Group 2">
          Content 2
        </SynDetails>
      </SynAccordion>

      <SynButton
        onClick={() => {
          setIsOpen(false);
        }}
        variant="filled"
        slot="footer"
      >
        Close
      </SynButton>
    </SynDialog>
  );
}

Acceptance criteria

[ ] All DoD items successfully completed
[ ] Internal element listeners should not bubble to call the syn-hide event on the syn-dialog
[ ] Unittests must be provided.
[ ] Provide fix as shoelace PR

Seems to be a problem with event bubbling of elements that are supporting syn-hide, see https://github.com/shoelace-style/shoelace/discussions/2021 and https://github.com/shoelace-style/shoelace/issues/1801.

This may be more of a documentation thing people must be aware of. The same would happen when placing a syn-tooltip into a dialog as the syn-close event of syn-tooltip will bubble up and close the syn-dialog.
Could be added to https://github.com/synergy-design-system/synergy-design-system/issues/449


Add jade-lint

This adds jade-lint, a syntax checker for jade templates.

Thank you.  Merged, with this patch on top: 703287c.
On a side note: column numbers seem to be produced only when requireSpacesInsideAttributeBrackets is true, and they are wrong (the numbers are relative to the end of the preceding token, which is useless).

The column number issue is a known bug in the jade-lexer: https://github.com/benedfit/jade-lint/issues/17


Kernel dieing for iruby notebook

Whenever I try to start a new instance of iruby notebook inside the daru root directory the kernel dies and restarts and this goes on. I am unable to run any commands in the notebook. Here is the screenshot.

This is similar to this stackoverflow question: http://stackoverflow.com/questions/35999925/kernel-dies-when-creating-iruby-notebook
We should include the iruby and ffi-rzmq gems as a dependency in the gemspec file.

We should include the iruby and ffi-rzmq gems as a dependency in the gemspec file.

No, we should not (or maybe in a development group only).
It is iruby's problem that it is hard to run system-wide, not daru's. Adding new hard dependency to solve it is not acceptable.

This could probably be solved with more thorough guides to installing dependencies and getting them working on various systems in a readme or common issues wiki type thing?

@zverok We can add this as an development dependency. Thoughts on this ?

No. This is purely an iruby issue and should be dealt with in the iruby issue tracker.  What's the use of introducing a development dependency in daru?
Check out the iruby issue tracker, many people have posted this problem and offered solutions.


Add debugPrintf-based panic reporting, controlled via spirv_builder::ShaderPanicStrategy.

This is a followup to my earlier PR about panics (and the only thing I want to really get into 0.9):

#1070

There are better docs on spirv_builder::ShaderPanicStrategy, but this is the basic usage example:
    SpirvBuilder::new("examples/shaders/sky-shader", "spirv-unknown-vulkan1.1")
        .shader_panic_strategy(spirv_builder::ShaderPanicStrategy::DebugPrintfThenExit {
            print_inputs: true,
            print_backtrace: true,
        })

(that is, to enable emitting all the information we can right now - print_inputs will show values of entry-point inputs, to identify the invocation, while print_backtrace will collect the static "inlined call frames" information we track for diagnostics, into the message)
And this is what it looks like with an artificially induced panic in sky-shader (plus some extra functions that just call the next one in the chain, to show off a non-trivial backtrace):

If you look at the diff, you may notice most of it is to the inliner: yupp it had more bugs, but not only that, the entire strategy for tracking debuginfo was wrong because it's fundamentally an outside-in inliner, instead of the usual inside-out model (I'm honestly surprised any of the past diagnostics demos worked at all).
The other changes I've made were to the ash runner, hopefully they're not too disruptive (cc @DJMcNab).
This is how I was testing (after sprinkling sky-shader with extra panics):
VK_LAYER_ENABLES=VK_VALIDATION_FEATURE_ENABLE_DEBUG_PRINTF_EXT cargo run -p example-runner-ash --release -- -d

Haven't been able to break anything with it, so I'm relatively confident the inliner changes aren't semantically meaningful (after all, the whole point is to tweak debuginfo to make it more accurate, not to change anything else).

EDIT: also check out this other PR, which further improved the output and figured out how to use it with wgpu:

https://github.com/EmbarkStudios/rust-gpu/pull/1036

(marked as draft to avoid accidentally merging w/o changelog)

For anyone seeing this PR later, the output, wgpu compatibility, and docs, were improved in:

https://github.com/EmbarkStudios/rust-gpu/pull/1036


Do not check imported files.

When running api-linter checkproto a.proto b.proto, the linter should only check a.proto and b.proto, but not their imported files (dependencies). For example, if a.proto imports google/type/date.proto, it is pointless and wrong to lint date.proto.

PR #154 fixed this issue.


Cannot read property 'is' of null

Has anyone got an idea why this is failing? It only started after the update of CSScomb. It seems to be failing on the new comb option of lines-between-rulesets.
Error:
Cannot read property 'is' of null
TypeError: Cannot read property 'is' of null
at Object.insertNewlines (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\options\lines-between-rulesets.js:237:20)
at node.forEach (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\options\lines-between-rulesets.js:124:12)
at Node.forEach (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\gonzales-pe\lib\gonzales.js:175:83)
at Object.processRuleSets (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\options\lines-between-rulesets.js:123:10)
at Object.processBlock (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\options\lines-between-rulesets.js:98:12)
at Object.process (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\options\lines-between-rulesets.js:89:10)
at C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\core.js:380:14
at Array.forEach (native)
at Comb._processTree (C:\Users\Stephen Bull.atom\packages\atom-beautify\node_modules\csscomb\lib\core.js:379:8)
Link to my .csscomb.json:
https://gist.github.com/kinkwilde/7b36f984bfeac75e5daf7e353e6c8071

@kinkwilde can you provide css file that cause the issue?

I created a sample test file to test it on and it does fail on this. It seems to work on one of my header files just fine but others it raise this same error.
I use csscomb through atom-beautify which has just updated to use the latest version of csscomb and the newer gonzales-pe. I've even tried updating the 2 manually. The guys over at atom-beautify told me to come over her to ask as it seems to be a csscomb issue but I am unsure where the fault lies at the moment. I can provide a list of plugins used or a beautify debug file if needed.
/* TEST COMB */
.extend-comb {
	border: 1px solid $white;
}

.test-comb {
	$color: pink;

    @extend .extend-comb;

    @include font-size(22);
    @include clearfix;
    @include position(vertical, absolute);

	background-color: $color;
	color: red;
	display: block;
	height: 100%;
	width: 100%;

	-webkit-font-smoothing: antialiased;
	-moz-osx-font-smoothing: grayscale;

	@include break-min($md-break) {
		color: blue;
	}

    @include break-max($md-break) {
		color: yellow;
	}

    @include break-between($lg-break, $xl-break) {
		color: black;
	}

	@media (min-width: $xx-break) {
		color: green;
	}
}

Got the same issue.
Cannot read property 'is' of null
Hide Stack Trace
TypeError: Cannot read property 'is' of null
    at Object.insertNewlines (/Users/marvinheilemann/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:237:20)
    at node.forEach (/Users/marvinheilemann/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:124:12)
    at Node.forEach (/Users/marvinheilemann/.atom/packages/atom-beautify/node_modules/gonzales-pe/lib/gonzales.js:175:83)
    at Object.processRuleSets (/Users/marvinheilemann/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:123:10)
    at Object.processBlock (/Users/marvinheilemann/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:98:12)
    at Object.process (/Users/marvinheilemann/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:89:10)
    at /Users/marvinheilemann/.atom/packages/atom-beautify/node_modules/csscomb/lib/core.js:380:14
    at Array.forEach (native)
    at Comb._processTree (/Users/marvinheilemann/.atom/packages/atom-beautify/node_modules/csscomb/lib/core.js:379:8)

SCSS
[module="book"]  .container content {
  padding: 7% 30px !important;

  background: rgba($color-dark, .5);

  @include media-breakpoint-up(md) {
    padding: 10% 50px !important;
  }

  p {
    margin: 0;
  }
}

@muuvmuuv  @kinkwilde  I can't reproduce the issue. What version of csscomb are you using? Try 4.1.0

As far as I am aware (last time I checked) it was updated to 4.1.0 - It is happening on all 3 of my machines that I have access to.
When you did your test did you use my .csscomb file? If yes, then do we think it's an issue with atom-beautify?

@kinkwilde Finally... the error was reproduced on Windows. It's actually happening of Windows machines -.- (MacOS, Linux - works fine). Working on issue

I'm seeing a very similar issue But on my mac
TypeError: Cannot read property 'is' of null
    at Plugin.insertNewlines (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:237:20)
    at node.forEach (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:124:12)
    at Node.forEach (/Users/jchappell/.atom/packages/atom-beautify/node_modules/gonzales-pe/lib/gonzales.js:175:83)
    at Plugin.processRuleSets (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:123:10)
    at Plugin.processBlock (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:98:12)
    at Plugin.process (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:89:10)
    at /Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/core.js:384:14
    at Array.forEach (native)
    at Comb._processTree (/Users/jchappell/.atom/packages/atom-beautify/node_modules/csscomb/lib/core.js:383:8)

csscomb.json
{
	"exclude": [
		".git/**",
		"node_modules/**",
		"bower_components/**",
		"dist/**",
		"gulp/**"
	],
	"always-semicolon": true,
	"block-indent": "\t",
	"color-case": "upper",
	"color-shorthand": false,
	"element-case": "lower",
	"leading-zero": true,
	"lines-between-rulesets": 1,
	"quotes": "single",
	"remove-empty-rulesets": true,
	"sort-order-fallback": "abc",
	"space-after-colon": " ",
	"space-after-combinator": " ",
	"space-after-opening-brace": "\n",
	"space-after-selector-delimiter": "\n",
	"space-before-closing-brace": "\n",
	"space-before-colon": "",
	"space-before-combinator": " ",
	"space-before-opening-brace": " ",
	"space-before-selector-delimiter": "",
	"space-between-declarations": "\n",
	"strip-spaces": true,
	"unitless-zero": true,
	"sort-order": []
}

Had the same issue, just removed the comments at the top of my file and it works!
Apparently if it's  starting with any comment, be it line comment with // or block comment with /*, csscomb will give this UnhandledPromiseRejectionWarning error.

Same here for SCSS file with comment on top:
CSScomb error:
(node:23692) UnhandledPromiseRejectionWarning: TypeError: Cannot read property 'is' of null
    at Plugin.insertNewlines (/home/valney/.config/sublime-text-3/Packages/sublime-csscomb/node_modules/csscomb/lib/options/lines-between-rulesets.js:237:21)
    at node.forEach (/home/valney/.config/sublime-text-3/Packages/sublime-csscomb/node_modules/csscomb/lib/options/lines-between-rulesets.js:118:12)
    at Node.forEach (/home/valney/.config/sublime-text-3/Packages/sublime-csscomb/node_modules/csscomb/node_modules/gonzales-pe/lib/gonzales.js:175:83)
    at Plugin.processAtRules (/home/valney/.config/sublime-text-3/Packages/sublime-csscomb/node_modules/csscomb/lib/options/lines-between-rulesets.js:117:10)
    at Plugin.processBlock (/home/valney/.config/sublime-text-3/Packages/sublime-csscomb/node_modules/csscomb/lib/options/lines-between-rulesets.js:95:12)
    at Plugin.process (/home/valney/.config/sublime-text-3/Packages/sublime-csscomb/node_modules/csscomb/lib/options/lines-between-rulesets.js:89:10)
    at /home/valney/.config/sublime-text-3/Packages/sublime-csscomb/node_modules/csscomb/lib/core.js:384:14
    at Array.forEach (<anonymous>)
    at Comb._processTree (/home/valney/.config/sublime-text-3/Packages/sublime-csscomb/node_modules/csscomb/lib/core.js:383:8)
    at <anonymous>
(node:23692) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:23692) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

Removing comment (or adding a empty line at top) fixes it.

Is this fixed? Currently running into this issue with version 4.3.0 via atom-beautify on OSX.
Cannot read property 'is' of null
TypeError: Cannot read property 'is' of null
    at Plugin.insertNewlines (/Users/zreese/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:237:21)
    at node.forEach (/Users/zreese/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:124:12)
    at Node.forEach (/Users/zreese/.atom/packages/atom-beautify/node_modules/gonzales-pe/lib/gonzales.js:175:83)
    at Plugin.processRuleSets (/Users/zreese/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:123:10)
    at Plugin.processBlock (/Users/zreese/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:98:12)
    at Plugin.process (/Users/zreese/.atom/packages/atom-beautify/node_modules/csscomb/lib/options/lines-between-rulesets.js:89:10)
    at /Users/zreese/.atom/packages/atom-beautify/node_modules/csscomb/lib/core.js:384:14
    at Array.forEach (<anonymous>)
    at Comb._processTree (/Users/zreese/.atom/packages/atom-beautify/node_modules/csscomb/lib/core.js:383:8)


Microoptimize ImageData.combine_chunks

When doing some memory profiling, I noticed that this line was
allocating by far the most memory in my application. Looking for a way
to bring this down a little, I discovered that we can avoid building and
joining our own array here by just pushing onto the stream directly.
Using memory_profiler in my application, this appears to bring memory
allocation down from 1,158,307,467 bytes (499,055 objects) to
1,154,056,455 bytes (498,849 objects), which is a difference of
4,251,012 bytes (roughly 4 MiB). While not the juicy win I'd really like
to see here, it seems like a simple enough change for the payoff.
I did see slightly worse memory usage for the smallest of images due to
the overhead of allocating the memory for instantiating the
Zlib::Inflate class, but I think this is a worthwhile tradeoff.

:balloon: :fireworks:

@wvanbergen I think I'm done hacking on this for a while so it would be an alright time to cut a new version now.

done

On Oct 28, 2015, at 1:51 PM, Joe Lencioni<EMAIL_ADDRESS>wrote:
@wvanbergen https://github.com/wvanbergen I think I'm done hacking on this for a while so it would be an alright time to cut a new version now.
—
Reply to this email directly or view it on GitHub https://github.com/wvanbergen/chunky_png/pull/103#issuecomment-151929555.


Shadows1024 TOTK 1.0.0 @nsobid wrong

Looks like the code at the very top of the patch is incorrect for TOTK 1.0.0 and should be @nsobid-082CE09B06E33A123CB1E2770F5F9147709033DB
?

fixed
https://github.com/HolographicWings/TOTK-Mods-collection/commit/3a7135e47239e215da5ab12c90e84b1510528b9c
thanks you for report


AdaptStaticArraysCoreExt does not have Adapt in its dependencies

I'm not sure where to report this, maybe here?
[ Info: Precompiling AdaptStaticArraysExt [e1699a77-9e31-5da8-bb3e-0a796f95f0a0]
ERROR: LoadError: ArgumentError: Package AdaptStaticArraysCoreExt does not have Adapt in its dependencies:
- You may have a partially installed environment. Try `Pkg.instantiate()`
  to ensure all packages in the environment are installed.
- Or, if you have AdaptStaticArraysCoreExt checked out for development and have
  added Adapt as a dependency but haven't updated your primary
  environment's manifest file, try `Pkg.resolve()`.
- Otherwise you may need to report an issue with AdaptStaticArraysCoreExt
Stacktrace:
 [1] macro expansion
   @ ./loading.jl:1599 [inlined]
 [2] macro expansion
   @ ./lock.jl:267 [inlined]
 [3] require(into::Module, mod::Symbol)
   @ Base ./loading.jl:1576
 [4] include
   @ ./Base.jl:457 [inlined]
 [5] include_package_for_output(pkg::Base.PkgId, input::String, depot_path::Vector{String}, dl_load_path::Vector{String}, load_path::Vector{String}, concrete_deps::Vector{Pair{Base.PkgId, UInt128}}, source::String)
   @ Base ./loading.jl:2010
 [6] top-level scope
   @ stdin:2
in expression starting at /home/.../packages/Adapt/Ur60R/ext/AdaptStaticArraysExt.jl:1
in expression starting at stdin:2
┌ Error: Error during loading of extension AdaptStaticArraysExt of Adapt, use `Base.retry_load_extensions()` to retry.
│   exception =
│    1-element ExceptionStack:
│    Failed to precompile AdaptStaticArraysExt [e1699a77-9e31-5da8-bb3e-0a796f95f0a0] to "/home/.../compiled/v1.9/AdaptStaticArraysExt/jl_6dbNzo".
│    Stacktrace:
│      [1] error(s::String)
│        @ Base ./error.jl:35
│      [2] compilecache(pkg::Base.PkgId, path::String, internal_stderr::IO, internal_stdout::IO, keep_loaded_modules::Bool)
│        @ Base ./loading.jl:2260
│      [3] compilecache

It looks like an issue with https://github.com/JuliaGPU/Adapt.jl , so I suggest reporting it there.


[BUG-28] Improve Navbar

Requirements

[x] A styled navbar with the app's theme.
[x] Highlight currently active links and add hover effects on links.

Extra

[x] Responsive Navbar.
[x] Signing in and out options.


Restarting the app causes "login required" issues

OS: Debian 10.
Using the term "login required" as accessing the settings panel is entirely optional (after you logged in the first time) and the app otherwise functions fine.
Clicking the user preferences panel causes an unknown error when playing music. Apple Music will ask for your Apple ID + pass and completely break the app, requiring a restart.
Affects both beta and non-beta AM.
Playing non-preview music and requiring a login:

I am not able to reproduce the error on my Arch system. Are you using the deb release or the AppImage?

I am not able to reproduce the error on my Arch system. Are you using the deb release or the AppImage?

Oh wait I'm not subscribed to Apple Music anymore so I can only listen to previewed music, that's probably why I couldn't reproduce it. Will look into the settings menu code to see if I can find anything that might be causing it.

Oh wait I'm not subscribed to Apple Music anymore so I can only listen to previewed music, that's probably why I couldn't reproduce it. Will look into the settings menu code to see if I can find anything that might be causing it.

I can't seem to reproduce it on my Arch system but I don't have an active Apple Music subscription so I was only able to test the preview music. Are you using the .deb release or the AppImage?

I can't seem to reproduce it on my Arch system but I don't have an active Apple Music subscription so I was only able to test the preview music. Are you using the .deb release or the AppImage?

Managed to reproduce the issue in ubuntu. Seems to happen whether music is playing or not. When the user accesses the settings on app launch it will log them out. For the rest of the session they can go back to the settings menu no problem but upon relaunch it will log them out again if they try to access settings.

I was able to reproduce the issue in ubuntu but I have no idea what's causing it. If anyone can figure out what's causing it I'd be happy to implement a fix but it's not a high priority since the settings menu is entirely optional anyway.


Can you support MongoDB?

Provides high-perfomance data access
Identity.MongoDB
https://github.com/tugberkugurlu/AspNetCore.Identity.MongoDB

What advantage does MongoDB OrchardCMS support it?

https://www.youtube.com/watch?v=D42eK6CJjF4
Orchard harvest 2017 - YesSql
Sebastien discussed MongoDb in this video

Short answer, not possible technically.

@sebastienros @dataangel
Mongodb now supports transactions. Is it possible for Orchard to support mongodb now?

Mongodb now supports transactions. Is it possible for Orchard to support mongodb now?

You can post your question in YesSql repo


fix: include typescript in pkg dependencies

Javascript projects were broken because typescript became a required import from 0.9.6 with scan.js importing it.
Currently, if you try to run a JS project, you'll get the following error:
┃ node:internal/modules/esm/resolve:844
┃   throw new ERR_MODULE_NOT_FOUND(packageName, fileURLToPath(base), null);
┃         ^
┃
┃ Error [ERR_MODULE_NOT_FOUND]: Cannot find package 'typescript' imported from /Users/tomchauveau/Documents/Quartz/playground/js-repro/node_modules/@
┃ dagger.io/dagger/dist/introspector/scanner/scan.js
┃     at packageResolve (node:internal/modules/esm/resolve:844:9)
┃     at moduleResolve (node:internal/modules/esm/resolve:901:20)
┃     at defaultResolve (node:internal/modules/esm/resolve:1121:11)
┃     at ModuleLoader.defaultResolve (node:internal/modules/esm/loader:396:12)
┃     at ModuleLoader.resolve (node:internal/modules/esm/loader:365:25)
┃     at ModuleLoader.getModuleJob (node:internal/modules/esm/loader:240:38)
┃     at ModuleWrap.<anonymous> (node:internal/modules/esm/module_job:85:39)
┃     at link (node:internal/modules/esm/module_job:84:36) {
┃   code: 'ERR_MODULE_NOT_FOUND'

This commit moves typescript from devDependencies to dependencies so it will be part of the deps installed when you installed @dagger.io/dagger

issue reported on Discord

The scan.js file is only needed in modules, but this will make JS users that don't use modules, to have to download typescript, right? How would you separate dependencies from modules vs non-modules?

I think it's because all javascript files are interpreted even if not call when it's executed.
I agree that normally there shouldn't be an issue because scan.js is never used but still, it is exported by index.js that export entrypoint and entrypoint import scan.
Since I need to export entrypoint, so modules can work, the side effect is that typescript is required as an imported package (not as a language)


RS BOT

You can do a normal Bot like the 3 for Real Soccer? Can be the best!
Well your bot's are one of the best!

I have RS Bot level 4 running smooth I’ll publish it in the day I think.
RS Bot level 3 ?

Yeah, i was talking the bot level 3.
Nice work man!

Update : I don't plan on posting the RS Bot for the moment after all. If you wanna do your room, I encourage you to look at http://rshl.eu/pages.php?page=autoreferee

😢


constrained click to known compatible range

Description
Short term resolution for the click incompatibility. Click has released a backwards incompatible minor. This breaks the current stable release (see #4093). This is a short-term response to that incompatibility. I'll cherry-pick this to the iso5 RC.
@wouterdb to respond to your earlier question, dependabot does track this. docstring-parser was constrained to ~=0.10.0 for similar reasons 9 months ago. It is now at >=0.10,<0.14 (see its history).
Should we create a ticket to document how a build master should respond to backwards incompatibilities? We don't have a standard procedure now but I believe it would be good to have a documented procedure that includes managing the setup.py file so that its constraints give a measure of confidence as to stability of our releases.
I'll open a similar pull request for iso4, but constrain it more heavily there because we didn't fix the code there. Does this warrant a patch release for iso4 (RPM install is fine, pip install is probably broken)? What about OSS?
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[ ] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )

Reviewer Checklist:

[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Code is clear and sufficiently documented
[ ] Correct, in line with design

Processing this pull request

Pull request rejected by merge tool. No change entry file found

Processing this pull request

Pull request rejected by merge tool. No change entry file found

Processing this pull request

Merged into branches master in bd179ebbd25b86f8213cf938e37939eb46b89449

Processing #4113.


[Candidate 1v1 Storm Surge ZH v1] Performance drops by about 50% while water rises after dam break

Observed behavior
Performance drops by about 50% while water rises after dam break.
Expected behavior
Performance is stable during water rise.
Screenshots

Newgate says this is technically as good as we can make it.

Tanso has fixed the performance issue. Water raise does not look as good as on other maps - particles are missing, but ok.


Adjust task rating max value to 5

The axis labels could be slightly confusing, as the zero is really outside the grid. Changing that to 1, and moving those labels to the middle of (side of) the corresponding square might be clearer.


PDF render support

Can Imagor support PDF file processing, is it possible to render specific page of a PDF?

Imagor v0.8.18 now supports generating PDF Thumbnail:
http://localhost:8000/unsafe/fit-in/200x200/filters:fill(cyan)/http://www.africau.edu/images/default/sample.pdf


Admin Bro is not working

Admin bro is not working. I keep getting this error in the console.

Are you sure you're not using outdated libraries? We rebranded to AdminJS almost a year ago


Reduce connection timeout

+1

+1 here as well.
I'd pass the socket timeout setting in an options object instead, since it'll allow extend it for other reasons, such as https://github.com/SOHU-Co/kafka-node/pull/261

Should consider writing some unit testing.
I had to deal with the same kind of issue in this PR #262 using fake timers of sinon.js


[BUG] Prometheus output is not parsable by Prometheus common libraries

Describe the bug
KoP generates multiple identical TYPE definitions, which causes the following error:
error parsing MF: text format parsing error in line 780: second TYPE line for metric name "kop_server_REQUEST_LATENCY", or TYPE reported after samples
To Reproduce

You  need to generate some Kafka traffic.
Build and run the following Go test program: promreader.zip

Expected behavior
The attached program should iterate and print all the Pulsar key/values, including those generated by KoP.

Which KoP version and Pulsar version did you use?


Client Allocation Request for: [Voodfy Inc]

Client Allocation Questions
Core Information

Name: Voodfy Inc
Website / Social Media: https://beta.voodfy.com
DataCap Requested: 5TiB
Addresses to be Notarized: f3wfovmet4goxalkks7mobcgeraxy5ln5qfwchx2aqvlb2hsykjsxiufkyjuznlertgjnl4ezmdq2chj3w67ia
Notary Requested: philippbanhardt

Voodfy is professional video hosting for everyone.
@Voodfy / @Leeaandrob Twitter
https://blog.textile.io/video-on-filecoin-using-voodfy-project-and-powergate/
https://filecoin.io/blog/mainnet-liftoff-video-storage/
Four years ago I am working a startup called Paratii where We were building a decentralized video player using IPFS, my first contact with Filecoin happened this year when Eric Tang(Livepeer) present to me all ecosystem and community around Filecoin. with the possibility to store in a decentralized way I realize that I could build a decentralized video platform. I accept the challenge and build the Voodfy using IPFS+Filecoin(Powergate) and the transcoder using Livepeer during the process I received two grants to build an MVP and currently this MVP is possible to access using https://beta.voodfy.com.
All videos are store using IPFS as the hot layer strategy and Filecoin as our cold layer strategy for private and public assets, videos, etc.
Our strategy is to store using redundancy and the best location near for the user that is storing using Voodfy.


Not adding dynamic components to dependencies

Found an issue with detecting variable usage when the components are stored as variables. We use this quite frequently in our app.
Repro
import { useAutoMemo } from 'hooks.macro'
import React from 'react'

const Foo = () => null
const Bar = () => null

export default function MyComponent({ bar }) {
  const Selected = Foo

  if (foo) Selected = Bar

  return useAutoMemo(<Selected />)
}

Output:
import { useMemo as _useMemo } from "react";
import React from 'react';

const Foo = () => null;

const Bar = () => null;

export default function MyComponent({
  bar
}) {
  const Selected = Foo;
  if (bar) Selected = Bar;
  return _useMemo(() => /*#__PURE__*/React.createElement(Selected, null), []);
}

Expected:
import { useMemo as _useMemo } from "react";
import React from 'react';

const Foo = () => null;

const Bar = () => null;

export default function MyComponent({
  bar
}) {
  const Selected = Foo;
  if (bar) Selected = Bar;
  return _useMemo(() => /*#__PURE__*/React.createElement(Selected, null), [Selected]);
}

The test for do-expressions can on the same note be fixed by adding:
      babelOptions: {
        babelrc: true,
        filename: path.join(__dirname, 'do-expressions.js'),
      },

to the test case.

This is indeed a very nasty bug — we actually missed a reference there! Thank you so much for reporting this.
I found a slighlty more succint solution, different from your approach, but will add you as a co-editor since you gave most of the details right.

Fixed in v1.1.2! 🎉 Thank you so much!


train has high top1.avg  but predict has bad result, same data to predict,why?

i use vit_base_patch16_224_in21k model, when i train with pretrained model,it has high top1.avg .about 99 %.
but when i use same data(train data) to predict ,the resutl very bad!!,i dont know why,can you give me some idea?

not really, seems like a bug in your scripts.
try a different model (renset50) to verify.
make sure you are properly loading the model from memory for predictions.

I use latest timm, it will error
  File "/home/wangzf/wzf/lib/python3.6/site-packages/timm/models/vision_transformer.py", line 416, in _create_vision_transformer
    **kwargs)
  File "/home/wangzf/wzf/lib/python3.6/site-packages/timm/models/helpers.py", line 455, in build_model_with_cfg
    strict=pretrained_strict)
  File "/home/wangzf/wzf/lib/python3.6/site-packages/timm/models/helpers.py", line 209, in load_pretrained
    del state_dict[classifier_name + '.weight']
KeyError: 'head.weight

this error relates to timm package, not to 21K pretraining.
see an example for transfer learning code in: https://github.com/Alibaba-MIIL/ImageNet21K/blob/main/Transfer_learning.md
try maybe adding: --nonstrict_checkpoint flag.


Explain how to configure the plugins

How do i configure the plugins that this automatically installs? I need to configure flash.nvim for instance because I use , as my leader key

how is the lazy-lock full of files already after install? the list of plugins in lazy.lua doesn't include flash.nvim but it gets installed...

just curious how to remove stuff if i want to

LazyVim uses lazy.nvim as its plugin manager so I'd start by reading up on it here https://github.com/folke/lazy.nvim and in the documentation you should now have in neovim. This https://github.com/briandipalma/iac/blob/main/dotfiles/nvim/lua/plugins/disabled.lua is an example of how to disable plugins. After you disable a plugin lazy.nvim will give you the option to clean/remove it.

i got it all figured out, thank you for the support. closing the issue but hopefully other people on google will find this :)


Sparse masks for torchvision maskrcnn - useful for training on big images with small objects

🚀 Feature
Hello everyone,
To have more efficient GPU memory management, I propose it's a nice idea to allow for sparse masks in the torchvision mask rcnn implementation.
Motivation
For tasks involving the prediction of many small objects in large images it becomes increasingly painful to a large, extremely sparse mask for each object. For example, I may have images of size 8k x 8k pixels with between 1 and up to 100 objects of interest of size around 40 x 40 pixels. In this case, the current dataloader tutorial  creates by default a dense mask of size 8k x 8k x N_objects, which is extremely sparse <<1% but takes a lot of memory.
Having this feature would facilitate training mask rcnns on much larger images in this scenario.
Pitch
To allow for masks to be defined as torch sparse tensors, in addition to the usual dense tensors.
I think the only thing to be done is to adjust the way the maskrcnn loss is defined and allow it to take both dense or sparse masks, potentially with a if/else depending on the mask instance.
https://github.com/pytorch/vision/blob/7d52be76c8eaf02b12338afe0822396ab3547fe2/torchvision/models/detection/roi_heads.py#L101
Alternatives
The current alternative is to cut a big image into many smaller ones to be inside the GPU memory, but this is suboptimal when the objects of interest are rare, and we want to include as many as possible hard negatives in addition to positives.
Additional context
N/A
cc @datumbox

Thanks for the proposal. Currently the sparse tensors are in beta and not all operators are supported. Definitely worth leaving this issue open once their API becomes more stable.


Which version is current ?

Hello, so i followed the tutorial how to install on Laravel 5.4 and i was thinking that i am gonna use 3.2 Of Crud but i was using 3.1.x. Then i tried to upgrade from 3.1 to 3.2 using this guide https://laravel-backpack.readme.io/v3.0/docs/whats-new-november-2016. Nothing good happened... After that i tried to install it on clean L5.4 using 3.2-dev in composer, this part was OK, Then i tried to publish the configs,langs etc... nothing happened nothing was published. Okay "everything can happen" i tried to copy everything manually -> Elfinder is not working. I said to myself never mind i will make workaround about this. After that i continue and tried to create the News section with translatable models. And guess what... There are no any options about the translations, just plain english that's it. So my question is what we have to do to use 3.2.x with L5.4 and translatable options ? Thank you very much and the project and work is just perfect,awesome etc... This is the most useful Laravel package for me. Keep up the good work.

Hi @petyots ,
3.2 isn't officially launched yet, I'm currently trying to cram in as many breaking changes as possible, because the next chance we get is in 6 months.
3.1.57 does bring Laravel 5.4 compatibility and is an official release, so you can use that. If you want the multi-language functionality, you can use the multilanguage branch, I've just updated it with L5.4 compatibility too.
Cheers!


Use yum & apt LWRPs to set up New Relic repository

A rebase & update of #63
Closes #63
Rather than manually setting up the distro-appropriate repo for installing the NR packages, we can take advantage of the various community cookbooks to install repos, providing a much cleaner, and more idempotent, way to manage these repos.

@djoos got one more for yah!

Thanks for the original work @b0d0nne11 and for the rework @jeffbyrnes!
@jeffbyrnes: I've changed 'repo' to 'repository' though... #nitpicking
Kind regards,
David

@djoos sure thing! I was following @b0d0nne11’s changes closely. Totally cool with that.

:+1:


Coracle Nostur Nostrudel borked profile

client initiating action
unknown
client receiving or observing action (or lack thereof)
Appears borked on Coracle, and Nostur. Not on Damus, and nostrudel.
timestamp
https://njump.me/nevent1qqs89qsthp5epuy2g66t42jl4h40sujxmwm69j5v6txuw9ye9c245fgpr3mhxue69uhkummnw3ezucnfw33k76twv4ezuum0vd5kzmqpr3mhxue69uhkummnw3ezumt4w35ku7thv9kxcet59e3k7mgprpmhxue69uhhyetvv9ujuumwdae8gtnnda3kjctvqy2hwumn8ghj7etyv4hzumn0wd68ytnvv9hxgnw0pzw
what happens

Coracle and Nostur both haved stopped working with my account.
When I use another account, everything works fine. So I make the assumption there is some related data to my account which is breaking things in those clients...it's not fun when you suddenly you can't use two of your favorite Nostr clients anymore. 😢 For now...

I think I've broke Nostr in someway in my case: both Coracle (desktop) and Nostur (iOS) have stopped loading my feed. Damus (iOS) and noStrudel (desktop) seems to work fine.
On Coracle I'm getting a lot of errors which look related to reading out events from relays. When I use an other Nostr account, everything just works fine.

and I already poked @staab  (npub1jlr…ynqn) about this 🤓

Earlier this week I've used https://delete.nostr.com/ to delete some events with short text notes. Could there be a correlation between those actions and the issues I'm facing in Coracle and Nostur?

suggestion
@mikedilger suggests

bug in a library [coracle & nostur] both use

Https://njump.me/nevent1qqsz72nw99lkzn686hsva23tajgk8xrgj34jt9l7aksthe9jxr69mxgpr4mhxue69uhkummnw3ez6ur4vgh8wetvd3hhyer9wghxuet5qyfhwumn8ghj7mmxve3ksctfdch8qatz9uq3wamnwvaz7tmjv4kxz7fwdehhxarj9e3xzmny9uq32amnwvaz7tmjv4kxz7fwv3sk6atn9e5k7tcdscak2

@fabianfabian

@sebastix

@alltheseas It's fixed in Coracle by @staab
Nostur is still broken for me and I've stopped using the app (which is a pity)
noStrudel is also having an issue here loading my following list:
https://nostrudel.ninja/#/u/npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefe/following
Something went wrong: Invalid byte sequence

@hzrd149

The root cause was an empty petname tag (["p"]) getting added to his follow list.

The root cause was an empty petname tag (["p"]) getting added to his follow list.

Was this caused by Coracle, or another app?

Pretty sure it wasn't Coracle, I couldn't say who though.

I'm still not sure what exactly cause is. @Sebastix do you still have the issue now with your current follow list? (id: f36c42a40edacc5606770e3b73be5dd70bf653852051414687726dda6e873db5)

The root cause was an empty petname tag (["p"]) getting added to his follow list.

@staab do you mean the petname field was empty or the entire p tag was literally just ["p"] ?

The whole p-tag was empty, because my code failed when it expected to find a string, but found undefined as the tag value.

@fabianfabian
https://nostrudel.ninja/#/u/npub1qe3e5wrvnsgpggtkytxteaqfprz0rgxr8c3l34kk3a9t7e2l3acslezefe/following the issue has been resolved!

@fabianfabian can you confirm the problem and solution, ser

I wish I could but I think the problem was something else and I don’t know what, at least on the Nostur side. I just tried publishing with an empty “p” and it seems to get rejected by relays ("invalid: unexpected size for fixed-size tag”), which is good. Forcing to handle an empty p on a local test relay just ignores the p and everything still works. Maybe there was something else in the tag that would also cause it to appear undefined on Coracle.
Best would be if we could find the kind 3 event that broke things but that may be difficult to find.

@fabianfabian @alltheseas Sorry, I swapped noStrudel and Nostur here. My bad.
The issue is resolved on noStrudel /cc @hzrd149
I reinstalled Nostur (iOS 17.3.1) from the App Store (1.12.0) and my feed is loading correctly now.

@fabianfabian I still do have issues in Nostur. Afaik I only can see my own events in the feed, events I interacted with or events where I'm tagged at.

@fabianfabian I still do have issues in Nostur. Afaik I only can see my own events in the feed, events I interacted with or events where I'm tagged at.

Does it still show you are following people in the sidebar or 0?

@fabianfabian I have a number of 451 following people there.

@hzrd149 comment:

I'm not sure exactly what the bug was, but I suspect it was similar to coracle in that the app was not expecting an empty "p" tag. its difficult to recreate though

@fabianfabian I switched to Nostur on Testflight and I'm happy to say that version has working again as expected.

@Sebastix are we good to close this issue now?

@alltheseas Sure!


Can I chose the kubernetes version ?

I like to choose to install kubernetes 1.15....there is some easy for this ?

I use this mainly for development - so I always have only the (more-or-less) latest Kubernetes versions and don't have any way to select older Kubernetes version. But you can always checkout an older version from GitHub which was based on older Kubernetes version and use it. For example 1.7.2 (GitHub tag v1.7.2) was based on 1.15.3.

I use this mainly for development - so I always have only the (more-or-less) latest Kubernetes versions and don't have any way to select older Kubernetes version. But you can always checkout an older version from GitHub which was based on older Kubernetes version and use it. For example 1.7.2 (GitHub tag v1.7.2) was based on 1.15.3.

I'm understood. Thank you.


Week numbering with Sunday start of week

The numbering of the week does not change when using Sunday as the start of the week resulting in behavior such as in March in the image below.  Any time there is a week consisting of just a Sunday on a monthly calendar it uses the previous week value instead of the next week as one would expect.  This is also represented on the daily page for that date.

@TK0343 oh I see. Yes, it makes sense to change the week number there.
The reason it happens now is the week number is based on ISO week numbering. Sunday still belongs to week 13, and as there are no more days in the given week, the algorithm picks up the only available day in the week and gets its week number.
Thank you for the report, I'll look into it.


adding more DOM tests

Pull Request Test Coverage Report for Build 18

0 of 0 (NaN%) changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+6.1%) to 85.915%

Totals

Change from base Build 16:
6.1%

Covered Lines:
136

Relevant Lines:
153

💛  - Coveralls


Networks & File Items

This PR consolidates the models changes from #45, which will be rebased on this branch.

Make the FileItem relationship optional (datasets can be created without files)
Add a Network model to consolidate network logic and allow multiple disparate networks on the same dataset
Add rest endpoints for FileItem and Network models
Add a test for the load_roads task
Fix a bug in the charts endpoint for a context

Switching to this branch will require a migration.

Once the linting error is fixed I think this is good to go


Document update needed for jade library

Please update the documentation to remove the jade library dependency as this is deprecated and instead pug is an updated version. Also, the code needs to be updated accordingly to make it work, like, in Step 4. modify app.js :
app.set('view engine', 'jade') need to be replace with app.set('view engine', 'pug')

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

ID: f7ad84a6-f6b6-dd21-e7be-865d922c7ad4
Version Independent ID: 1f5a0315-d7b4-3f8f-3b1d-ae90c807859d
Content: Build a Node.js web app for Azure Cosmos DB
Content Source: articles/cosmos-db/sql-api-nodejs-application.md
Service: cosmos-db
GitHub Login: @SnehaGunda
Microsoft Alias: sngun

@madhavsharmaagra Thanks for the feedback! I have assigned the issue to the content author to evaluate and update as appropriate.

@burkeholland

#please-close

We will now close this issue. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


docs(changelog): fix 3.3.0 issue text

A better fix would be to change how these are being created. Possibly fix this line in the release.md:
git log 0.0.J..HEAD --format="- ([%h](https://github.com/angular/protractor/commit/%H)) %n%w(100,2,2)%B" > /tmp/changes.txt

Agreed, we don't want to manually edit these every time.

Hmm, so looking into it more, the problem is that https://github.com/angular/protractor/commit/6f22d5ade48f0d97990cbe69d956da122f2f8358 's commit message body had just the right amount of characters before the issue number that the git log wrapper (%w(100,2,2)) put it onto a new line. What if we just took out the 100 character wrapper?

@juliemr Just thinking about how these are generated, this change is acceptable since the issue number appears on the second line and markdown assumes it is a header. The issue number does appears in the raw file.
This is either a one-off changelog issue or we could remove the %w(100,2,2)

@cnishina if anyone's really worried about it, this sed addition will fix it:
git log 3.2.2...3.3.0 --format="- ([%h](https://github.com/angular/protractor/commit/%H)) %n%w(100,2,2)%B" | sed 's/^\(\s*\)\#\(.*\)$/\1\\#\2/'

Hah, sorry, I didn't see the original issue. Yeah let's just merge the first part of this.

Using the first part of the commit. Closed with 8ca84507e7a7deb4497a7c64f2e222cec6b80a28.


fix(deps): update terraform-module

This PR contains the following updates:

Package
Type
Update
Change

terraform-ibm-modules/client-to-site-vpn/ibm (source)
module
patch
1.7.18 -> 1.7.19

terraform-ibm-modules/landing-zone/ibm (source)
module
patch
5.31.2 -> 5.31.3

terraform-ibm-modules/secrets-manager/ibm (source)
module
patch
1.18.0 -> 1.18.2

Release Notes

terraform-ibm-modules/terraform-ibm-client-to-site-vpn (terraform-ibm-modules/client-to-site-vpn/ibm)
v1.7.19
Compare Source
Bug Fixes

update extension DA to make dependant DA as optional (#312) (0b0a47b)

terraform-ibm-modules/terraform-ibm-landing-zone (terraform-ibm-modules/landing-zone/ibm)
v5.31.3
Compare Source
Bug Fixes

deps: update required_provider to latest for the landing zone das (#878) (2aeebc7)

terraform-ibm-modules/terraform-ibm-secrets-manager (terraform-ibm-modules/secrets-manager/ibm)
v1.18.2
Compare Source
Bug Fixes

deps: update terraform-module (#197) (945a308)

v1.18.1
Compare Source
Bug Fixes

deps: update required_provider to latest for the deployable architecture solution (#202) (3426ac7)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline

/run pipeline


Add KEP for multi-cluster support

Adds a KEP describing how to implement multi-cluster tests.
#254

this makes a lot of sense... the core concepts are there... questions:
1. is the intent to have the configured kubeconfig in a step to over ride for the entire step?  It seems so

2. If this is true, then a step is restricted to a cluster and to work with 2 cluster (apply) before an assert.. it would require 2 steps correct?

3. currently all kubectl and commands use the local kubeconfig file that is created at the start kuttl... I assume we don't overwrite this...  and I assume the intention is for a changed step that the change is true for commands and kubectl.   We will need to make sure to capture this.

this /lgtm
it would be great to provide answer in the doc itself to provide additional context to future kep reviewers.
nice work :clap:

Addressed these!

this makes a lot of sense... the core concepts are there... questions:
1. is the intent to have the configured kubeconfig in a step to over ride for the entire step?  It seems so

2. If this is true, then a step is restricted to a cluster and to work with 2 cluster (apply) before an assert.. it would require 2 steps correct?

3. currently all kubectl and commands use the local kubeconfig file that is created at the start kuttl... I assume we don't overwrite this...  and I assume the intention is for a changed step that the change is true for commands and kubectl.   We will need to make sure to capture this.

this /lgtm
it would be great to provide answer in the doc itself to provide additional context to future kep reviewers.
nice work :clap:

Addressed these!


BUG: Puzzle 3 has no solution

I identified 4 letters with correct positions. And tried with all remaining alphabets for the 5th letter, but none of them fit (Note: 5th letter doesn't mean 5th position).

Hi, the solution is HUMPH, like an exclamation used to express slightly scornful doubt or dissatisfaction. What do you have so far?

Aah! Somehow I didn't think about reusing same letter twice ('h'). Thanks


[Popover] fix for warning when passing undefined to anchorEl

[X] I have followed (at least) the PR section of the contributing guide.

This is a fix for a warning when passing undefined to anchorEl explicitly rather than not including it in the props object:
<Popover anchorEl={undefined} .../>
Triggers:
Warning: Failed prop type: Material-UI: the `anchorEl` prop provided to the component is invalid.
It should be a HTMLElement instance but it's `undefined` instead.
    in Popover (created by ForwardRef(Popover))

<Popover ... />
doesn't trigger the warning

this is specially annoying when the logic is like
<Popover anchorEl={someCondition ? someElement : undefined} ... />

@xaviergonz What's your use case for changing the logic?

Basically this
p.anchorElement on a custom component can be either an element or undefined
<Popover
        anchorReference={p.anchorElement ? "anchorEl" : "anchorPosition"}
        anchorEl={p.anchorElement}
        ...

@xaviergonz Thanks, so we have a problem in the logic. We should only warn when anchorReference === 'anchorEl'. Do you confirm?

Yes, I think so, I just made a commit to skip such warnings if anchorEl is not "anchorEl" or undefined

@xaviergonz Thank you.


No answer

Some services that have only a 200 code and no detail as answer, remain looping and do not get the response.
Expected outcome
Should recibe a 200.
Actual outcome
keeps on working.

Versions
App: <IP_ADDRESS>-stable
Chrome: 49.0.2623.112
Platform: Windows (10)
Steps to reproduce

The same issue as #474

This is fixed in develop branch. Soon it will be released as beta.

Thanks Good Job
Pablo Ces
Business Consultant Partner
flexibility + ideas
(+54911) 4022-1303
www.flexibility.com.ar
2016-04-15 11:04 GMT-03:00 Paweł Psztyć<EMAIL_ADDRESS>
This is fixed in develop branch. Soon it will be released as beta.
—
You are receiving this because you authored the thread.
Reply to this email directly or view it on GitHub
https://github.com/jarrodek/ChromeRestClient/issues/471#issuecomment-210475492


[SPARK-28129][SQL][TEST] Port float8.sql

What changes were proposed in this pull request?
This PR is to port float8.sql from PostgreSQL regression tests. https://github.com/postgres/postgres/blob/REL_12_BETA2/src/test/regress/sql/float8.sql
The expected results can be found in the link: https://github.com/postgres/postgres/blob/REL_12_BETA2/src/test/regress/expected/float8.out
When porting the test cases, found six PostgreSQL specific features that do not exist in Spark SQL:
SPARK-28060: Double type can not accept some special inputs
SPARK-28027: Spark SQL does not support prefix operator @ and |/
SPARK-28061: Support for converting float to binary format
SPARK-23906: Support Truncate number
SPARK-28133: Missing hyperbolic functions
SPARK-28134: Missing Trigonometric Functions
Also, found two bug:
SPARK-28024: Incorrect value when out of range
SPARK-28135: ceil/ceiling/floor/power returns incorrect values
Also, found four inconsistent behavior:
SPARK-27923: Spark SQL insert bad inputs to NULL
SPARK-28028: Cast numeric to integral type need round
SPARK-27923: Spark SQL returns NULL when dividing by zero
SPARK-28007:  Caret operator (^) means bitwise XOR in Spark/Hive and exponentiation in Postgres
How was this patch tested?
N/A

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/11987/
Test PASSed.

Test build #106761 has started for PR 24931 at commit 46a300e.

Test build #106761 has finished for PR 24931 at commit 46a300e.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/106761/
Test PASSed.

Test build #107441 has started for PR 24931 at commit 4b4551f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12576/
Test PASSed.

Test build #107441 has finished for PR 24931 at commit 4b4551f.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107441/
Test FAILed.

retest this please

Test build #107444 has started for PR 24931 at commit 4b4551f.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12579/
Test PASSed.

Test build #107444 has finished for PR 24931 at commit 4b4551f.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107444/
Test PASSed.

Hi, @wangyum .
Since #25041 is merged, could you update this PR once more? Thanks!

Thank you @dongjoon-hyun . I will update it later.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12806/
Test PASSed.

Test build #107679 has started for PR 24931 at commit cd5d695.

Test build #107679 has finished for PR 24931 at commit cd5d695.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107679/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12840/
Test PASSed.

Test build #107713 has started for PR 24931 at commit 532486a.

Test build #107713 has finished for PR 24931 at commit 532486a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12848/
Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107713/
Test PASSed.

Test build #107721 has started for PR 24931 at commit f49cf43.

Test build #107721 has finished for PR 24931 at commit f49cf43.

This patch fails due to an unknown error code, -9.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107721/
Test FAILed.

retest this please

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/testing-k8s-prb-make-spark-distribution-unified/12851/
Test PASSed.

Test build #107725 has started for PR 24931 at commit f49cf43.

Test build #107725 has finished for PR 24931 at commit f49cf43.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/107725/
Test PASSed.

Merged to master.


Email notification on new issues and issue updates

Hi,
I don't see any email notifications nor email on issue updates. Is this a bug? Is it already reported?
Greetings,
Rik

Hi, this is something already implemented: https://github.com/gogits/gogs/blob/master/conf/app.ini#L117


Electron and Bytenode: Is there a way to make a stronger encryption?

So, I just learned that I have to compile my .js file to .jsc using my Electron app itself. I did that but there's a slight difference between doing it from the console and the app. The very reason I'm doing this is to hide my database information and when I do it from the app, it's technically still exposed. Is there a way to hide it using V8 Bytenode or my only option is to migrate to NW.js or just use another method?
const bytenode = require('bytenode');
bytenode.runBytecodeFile('./login.jsc');

I don't believe bytenode is intended to be a form of encryption. Though not technically public or documented, the V8 bytenode format is not secret or intentionally obfuscated, and it can be very easily interpreted using a V8 interpreter. You may need to change the architecture of your application so that your database information isn't part of it.

There are a bit of confusion here. When we say that you have to use Electron to generate the .jsc files, what really happens is that the embedded Node inside Electron will generate them. So, in terms of "security" they are the same. In fact, if you have turned off the "sanity checks" from Node.js source code, them you will be able to run any .jsc files given that they have the same format (i.e. the same major v8 version in most cases). But as we want to make bytenode usable with the already-built-binaries, we have not used the previous approach, because no one will prefer using our custom binary. (It is more difficult to maintain too).
That being said, I have to say that even if you are using c or c++, and you will compile your code amd hide your secret information inside the binary compiled program: this is very bad and weak archeticture. Your information is not safe nor secured at all, even if you use the known tricks to hide strings inside the binaries (google them and you will find many).
Bytenode was created mainly to help developers hide their code if they don't feel comfortable with the idea that their client will have the plain source code for whatever reason. Or if they want to make it difficult for their smart client (or competitor) to copy their work. Especially in places and countries that don't have the legal base to prevent such practices.
In other words, Bytenode is an alternative to the correct and sound legal approach to prevent software theft. It is NOT meant to securely protect any information inside the code. Even machine language is NOT safe nor secure for hiding such information.

when I do it from the app, it's technically still exposed

How is it still exposed? Could you explain that please?


feat(docs): add nodeadm wasm targets to call from docs

Issue #, if available:
Description of changes:
It would be helpful to be able to test a NodeConfig straight from the browser without installing any tools.
This PR adds a WebAssembly package containing nodeadm's config parsing hook and provides a minimal editor that users can paste their config into.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Testing Done
deployed to my fork's ghpages: https://ndbaker1.github.io/amazon-eks-ami/nodeadm/doc/playground/
rm -rf ./site
pushd nodeadm
GOOS=js GOARCH=wasm go build -o nodeadm.wasm cmd/nodeadm-wasm/main.go
popd
mkdir -p ./site/assets/javascripts && cp "$(go env GOROOT)/misc/wasm/wasm_exec.js" ./site/assets/javascripts/
mkdir -p site/assets/wasm && cp nodeadm/nodeadm.wasm ./site/assets/wasm
mkdocs gh-deploy -r ndbaker1 --dirty --no-history --force

See this guide for recommended testing for PRs. Some tests may not apply. Completing tests and providing additional validation steps are not required, but it is recommended and may reduce review time and time to merge.

im somewhat happy with the functionality now :)
feel free to take a longer look @cartermckinnon


Add more playground presets

This PR adds presets for:

playground=activitypanel
playground=aerialrotator
playground=bridge
playground=climbingwall
playground=funnel_ball
playground=map
playground=sledding
playground=splash_pad
playground=teenshelter
playground=trampoline
playground=tunnel_tube
playground=water

I also added fields for subject and subject:wikidata since the wiki article for playground=map recommends adding these tags.
Closes #538, related to #533

Just added a preset for gaga ball, another game found near playgrounds

As a follow up, it would be awesome to create separate icons for those new presets. It looks like most are generic or re-used:

file
icon

data/presets/leisure/pitch/funnel_ball.json
"icon": "maki-pitch"

data/presets/leisure/pitch/gaga.json
"icon": "maki-pitch"

data/presets/playground/activitypanel.json
"icon": "maki-playground"

data/presets/playground/aerialrotator.json
"icon": "maki-playground"

data/presets/playground/bridge.json
"icon": "maki-playground"

data/presets/playground/climbingwall.json
"icon": "maki-playground"

data/presets/playground/funnel_ball.json
"icon": "maki-playground"

data/presets/playground/map.json
"icon": "temaki-compass"

data/presets/playground/sledding.json
"icon": "maki-playground"

data/presets/playground/splash_pad.json
"icon": "maki-playground"

data/presets/playground/teenshelter.json
"icon": "maki-playground"

data/presets/playground/tetherball.json
"icon": "maki-playground"

data/presets/playground/trampoline.json
"icon": "maki-playground"

data/presets/playground/tunnel_tube.json
"icon": "maki-playground"

data/presets/playground/water.json
"icon": "maki-playground"


README.md snippet incorrect

README.md shows the import incorrectly. It should be simply import discordv, not quialified with my username.

Fixed by #3 - by accident


How to retreive only items "_key". Is nodata supported in items.iter()?

I found an example with which I can retreive only the specified meta from job items:
https://doc.scrapinghub.com/api/items.html?highlight=metadata#examples
This could be handy to parallelize download and fix the issue with filters, collections (since we cannot properly divide items before download after filter is applied, or for collections which have disordered or duplicated keys) https://github.com/scrapinghub/arche/issues/13 by fetching only keys (I think it should be fast), breaking them on batches and then downloading the data.
Naturally, getting just keys should be much faster to solve the issues above. I tested locally with curl for 13kk keys:
CPU times: user 2.76 s, sys: 1.56 s, total: 4.33 s
Wall time: 9min 55s
That's not really fast, but anyway - is there nodata?

The following example works fine, does it answer your question?
In [11]: for item in job.items.iter(nodata=True, meta=['_key']):
    ...:     print(item)
    ...:
{u'_key': u'123/45/67/0'}

I suppose we should update the docs for the client :thinking:


Cannot verify I am a human (lol)

Seriously, how do I pass this part here? Maybe I am running Wayland, I have to check...

Also, for some reason the extension installs but it is disabled. It would be nice to start it enabled, so the user would not be frustrated trying to find the issue.

Ah, there is somewhere written that it works better navigating with the keyboard. It indeed worked that way. Now I ma seeing the complain that it is running at capacity right now. haha.


Create workflow to automatically update the formula on subo release

Related issue: https://github.com/suborbital/subo/issues/182
The proposed solution is a combination of two workflows. On this repository's side it's a repository dispatch action that creates a new PR based on incoming data.
On subo's side it's an action that sends the required data to the dispatch endpoint of this repository on release.

Fixed by gh repo clone suborbital/docs


error: type of thread-local variable has non-trivial destruction

#include "sole.hpp" produces the following compile error on Linux. Sole version is 1.0.4.
In file included from /home/conan/w/prod/BuildSingleReference/conan-center-index/recipes/sole/all/test_package/test_package.cpp:2:
/home/conan/w/prod/BuildSingleReference/.conan/data/sole/1.0.4/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/sole.hpp:668:78: error: type of thread-local variable has non-trivial destruction
        static $msvc(__declspec(thread)) $melse(__thread) std::random_device rd;
                                                                             ^
/home/conan/w/prod/BuildSingleReference/.conan/data/sole/1.0.4/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/sole.hpp:668:78: note: use 'thread_local' to allow this
/home/conan/w/prod/BuildSingleReference/.conan/data/sole/1.0.4/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/sole.hpp:669:99: error: initializer for thread-local variable must be a constant expression
        static $msvc(__declspec(thread)) $melse(__thread) std::uniform_int_distribution<uint64_t> dist(0, (uint64_t)(~0));
                                                                                ^~~~~~~~~~~~~~~~~~~~~~~
/home/conan/w/prod/BuildSingleReference/.conan/data/sole/1.0.4/_/_/package/5ab84d6acfe1f23c4fae0ab88f26e3a396351ac9/include/sole.hpp:669:99: note: use 'thread_local' to allow this
2 errors generated.

Compiler setup:
CC and CXX: clang, clang++
Found clang 11.1
clang>=8, using the major as version
Default settings
	os=Linux
	os_build=Linux
	arch=x86_64
	arch_build=x86_64
	compiler=clang
	compiler.version=11
	compiler.libcxx=libstdc++
	build_type=Release

Test file:
#include <iostream>
#include "sole.hpp"

int main() {
    sole::uuid u0 = sole::uuid0(), u1 = sole::uuid1(), u4 = sole::uuid4();

    std::cout << "uuid v0 string : " << u0 << std::endl;
    std::cout << "uuid v0 base62 : " << u0.base62() << std::endl;
    std::cout << "uuid v0 pretty : " << u0.pretty() << std::endl << std::endl;

    std::cout << "uuid v1 string : " << u1 << std::endl;
    std::cout << "uuid v1 base62 : " << u1.base62() << std::endl;
    std::cout << "uuid v1 pretty : " << u1.pretty() << std::endl << std::endl;

    std::cout << "uuid v4 string : " << u4 << std::endl;
    std::cout << "uuid v4 base62 : " << u4.base62() << std::endl;
    std::cout << "uuid v4 pretty : " << u4.pretty() << std::endl << std::endl;

    u1 = sole::rebuild("F81D4FAE-7DEC-11D0-A765-00A0C91E6BF6");
    std::cout << "uuid v1 rebuilt: " << u1 << " -> " << u1.pretty()
              << std::endl;

    u4 = sole::rebuild("GITheR4tLlg-BagIW20DGja");
    std::cout << "uuid v4 rebuilt: " << u4 << " -> " << u4.pretty()
              << std::endl;
}

Related: https://github.com/conan-io/conan-center-index/pull/11275

Same on MacOS 12.4

maybe a known leak per invoking thread would be an acceptable tradeoff?
static $msvc(__declspec(thread)) $melse(__thread) std::random_device &rd = *(new std::random_device);
static $msvc(__declspec(thread)) $melse(__thread) std::uniform_int_distribution<uint64_t> &dist = *(new std::uniform_int_distribution<uint64_t>(0, (uint64_t)(~0)));

Ok, looks fine now. On MacOS at least, need to check on Linux but will have to do later on.
Ran 50000 iterations in less than 1.40 min, leak checks are also OK.

Thanks for your quick reaction


Remove March 2023 GDK Update 5 as part of migrating to unified GDK ID.

Remove March 2023 GDK Update 5 as part of migrating to unified GDK ID per #186890.

@microsoft/xbox-developer-experience-toolbox for review.


Restructure hierarchy of PyTorch brains (and brains in general)

Our current brain hierarchy of the PyTorch brains is a little bit cluttered. While the PyTorch implementations of Elman, GRU and LSTM use IPytorchBrain as a base class, the FFNN PyTorch implementation does not. It would be good if we either

Make a base class based on the brain category, for example a FeedForwardBase and then subclasses of it like FeedForwardNumPy and FeedForwardPyTorch or
Make a base class based on how they are implemented, for example a PyTorchBase and NumPyBase and then subclass specific brains from them

I would opt for the first option because it seems more intuitive to me to have brains from a similiar category grouped.
This issue can also be used to sum TODOs for refactoring that fall into this refactoring task:

[ ] When restructuring is done redo the get_activation_function() methods in IBrain as discussed in https://github.com/neuroevolution-ai/NeuroEvolution-CTRNN_new/pull/65#discussion_r573685016

From both options I would also favor the first one.
In addition, maybe we don't even need the PyTorch brains for the neuroevolutionary training at all, since the numpy versions a) are generally significantly faster (I will measure this more in detail) and b) produce the same outputs than the PyTorch networks. I agree that the PyTorch brains are very important for our tests, but maybe we can remove them from the brain classes. At least, I never used PyTorch brains for training. I think, this would help us keeping our brain class structure clean and simple. Nevertheless, we still provide flexibility since users can always implement and use their own brains by just deriving the IBrain class and implementing the corresponding functions.

When we erase the PyTorch brains out of the Project, we also don't need Netwok-specific base classes like FeedForwardBase, because there will only be one subclass of each base class.
So when we remove the PyTorch Brains, option one seems not like a good option.
But even if we keep the PyTorch networks, i prefere option two over one, because it combines way more code, then option one, because as state now there is a lot of code all PyTorch Networks need, but the NumPy and PyTorch versions already differ in many ways (e.g. doubble bias use and layer construction in the config file)
My favorite option would be to chose a network and a package base in the config file and the network would generate itself by combining the methods from the network base class (e.g. how many gates are needed in each neuron) with the methods in the package base class (e.g. how to apply the individual values) But i dont know a suitable way to implement this in the current framework

My favorite option would be to chose a network and a package base in the config file and the network would generate itself by combining the methods from the network base class (e.g. how many gates are needed in each neuron) with the methods in the package base class (e.g. how to apply the individual values) But i dont know a suitable way to implement this in the current framework

This sounds and would be really nice but I don't think the effort would be justified. I think we would need to have a class structure something like NumPy -> Linear / Recurrent -> FFNN / {LSTM, GRU, ...}, and the same for PyTorch. Then we have CTRNN which is not implemented in PyTorch and CNN which is not implemented in NumPy etc.
We could remove the PyTorch brains. I personally used them when I originally implemented the LSTM in NumPy to verify that my implementation is correct and I though I keep it because the PyTorch version could be used to move it to the GPU (at least in theory).
If we remove the PyTorch brains then we could rename ILayerBasedBrain to RecurrentBasedBrain and fuse FeedForwardNumpy into one class called FeedForward. CNN (and CnnCtrnn) would then be the only PyTorch implementations (because of the convolutional implementation), but that is okay because they are derived directly from IBrain and I think we measured at some point that a convolution implemented in NumPy is not realy a performance boost over PyTorch and way to much effort to make things like padding etc. to work in the right way.
If we want to keep the PyTorch brains we could still rename ILayerBasedBrain to RecurrentBasedBrain, make FeedForwardPyTorch a subclass of IPytorchBrain and fuse FeedForward and FeedForwardNumPy into a new class FeedForward directly derived from IBrain. This would be at first counterintuitive but it reduces duplicated code.
I would favor for keeping the PyTorch brains, since we already implemented them they may come in handy sometime. We could introduce new files/sub-directories to better separate brains in the file hierarchy which may help to improve the overview on all brains.

Overview on some possibilities:
Current Structure:

Remove PyTorch brains:

Keep PyTorch brains:


decorate() being called late

I'm having an issue, I think it may be with my code, but I can't seem to find what's wrong with my code.
So I'm retrieving event dates from my server and storing them in an ArrayList. Then I highlight those dates.
Here's my HighlightDecorator.java class:
public class HighlightDecorator implements DayViewDecorator {

    List<CalendarDay> dates;

    public HighlightDecorator(List<CalendarDay> dates){
        this.dates = dates;
    }

    @Override
    public boolean shouldDecorate(CalendarDay calendarDay) {
        return dates.contains(calendarDay);
    }

    @Override
    public void decorate(DayViewFacade dayViewFacade) {
        Log.e("day view", dayViewFacade.getDate().toString());
        dayViewFacade.setBackgroundUnselected(generateBackgroundDrawable());
    }

    private static Drawable generateBackgroundDrawable() {
        final int r = 0;
        final float[] outerR = new float[] {r, r, r, r, r, r, r, r};
        final int color = Color.parseColor("#660033");

        RoundRectShape rr = new RoundRectShape(outerR, null, null);

        ShapeDrawable drawable = new ShapeDrawable(rr);
        drawable.setShaderFactory(new ShapeDrawable.ShaderFactory() {
            @Override
            public Shader resize(int width, int height) {
                return new LinearGradient(0, 0, 0, 0, color, color, Shader.TileMode.REPEAT);
            }
        });
        return drawable;
    }
}

And here is a short excerpt from my fragment, which contains the MaterialCalendarView:
CalendarTab.java
MaterialCalendarView calendarView = (MaterialCalendarView) v.findViewById(R.id.calendarView);
        calendarView.setOnDateChangedListener(this);
        calendarView.setSelectedDate(Calendar.getInstance().getTime());

        JSONObject jsonObject;
        String date;
        String[] dateComponents;
        CalendarDay eventDay;
        events = new ArrayList<CalendarDay>();
        for(int i = 0; i < jsonArray.length(); i++){
            try {
                jsonObject = jsonArray.getJSONObject(i);
                date = jsonObject.getString("startDate").split(" ")[0];
                dateComponents = date.split("-");
                eventDay = new CalendarDay(Integer.parseInt(dateComponents[0]), Integer.parseInt(dateComponents[1])-1, Integer.parseInt(dateComponents[2]));
                events.add(eventDay);
            } catch (JSONException e) {
                e.printStackTrace();
            }
        }
        Log.e("events", events.toString());

        calendarView.addDecorator(new HighlightDecorator(events));
}

So from the log, I see that the ArrayList correctly has all the dates. Now, when I first open the app, the calendar is completely undecorated. When I move to May, I can see from the log that it is decorating the June dates. When I move to June, it is not decorating anything. When I move back to May, it is decorating April and May, but decorations for May are not shown. Then moving back to April, it decorates March.
What's going on?? This isn't happening in the sample that I downloaded, and my code is almost the same as that.

Hi @KPrabs106, I just released version 0.4.0, which has a lot of fixes to decorators. The README has a section on how to migrate, and the decorator sample has also been updated to include a mock API call. Can you update to 0.4.0 and see if this helps?


Regex for email in signup.html not complete

Currently , email adresses like<EMAIL_ADDRESS>etc don't work. The regex pattern used in signup.html(Line 17) is very short and doesn't take account of such email ids.
This regex fixes such issues :
required ng-pattern="/^[-a-z0-9~!$%^&=+}{'?]+(.[-a-z0-9~!$%^&=+}{'?]+)@([a-z0-9]-a-z0-9_*.(aero|arpa|biz|com|coop|edu|gov|info|int|mil|museum|name|net|org|pro|travel|mobi|[a-z][a-z])|([0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}.[0-9]{1,3}))(:[0-9]{1,5})?$/i"
Taken from http://emailregex.com/

@mr-kara Thank you for PR, but I have decided to fix this by removing ng-pattern altogether and just rely on the type="email" validation. I don't want to have that giant regex expression in a demo project, whose main and most important purpose is to showcase the Satellizer module.